The registration process itself is in section 7. There's a small form you have to fill out and email to iana@iana.org. The form is small because there also needs to be a formal definition of the scheme somewhere else.
It looks like we could define the opds: scheme as part of the OPDS spec (or a related spec), and then register it mainly based on a reference to that spec. We just need to make sure the spec covers all the items RFC7595 wants to be covered.
Since we are not going through the IETF standardization process for OPDS, I don't know if we can get a 'permanent' registration. All the 'permanent' registrations I see on https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml have RFCs as their reference specs. And to get 'permanent' status we'd need to ask the relevant IETF mailing lists for comments.
I spoke to Eric Wilde about this, who pointed me to an RFC he worked on for the sms: URI scheme. We could use this as a reference point to make sure we cover everything.
RFC 7595 covers scheme registration.
The registration process itself is in section 7. There's a small form you have to fill out and email to iana@iana.org. The form is small because there also needs to be a formal definition of the scheme somewhere else.
It looks like we could define the opds: scheme as part of the OPDS spec (or a related spec), and then register it mainly based on a reference to that spec. We just need to make sure the spec covers all the items RFC7595 wants to be covered.
Since we are not going through the IETF standardization process for OPDS, I don't know if we can get a 'permanent' registration. All the 'permanent' registrations I see on https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml have RFCs as their reference specs. And to get 'permanent' status we'd need to ask the relevant IETF mailing lists for comments.
I spoke to Eric Wilde about this, who pointed me to an RFC he worked on for the sms: URI scheme. We could use this as a reference point to make sure we cover everything.