60 likes | 189 Views
This draft by Bernie Hoeneisen addresses the need for a clearer registration process for experimental and trial ENUM services under the new X-Enumservices category. Currently, many of these services don't meet the criteria for standard registration due to undefined URIs. The proposal suggests creating an additional IANA registry specifically for X-Enumservices to facilitate low-barrier registrations. This approach aims to ensure clarity for ENUM implementors, promote the publication of experimental services, and gather valuable community feedback while aligning with existing ENUM service guidelines.
E N D
IANA Registration of Experimental and Trial Enumservices(X-Enumservices) Bernie Hoeneisen draft-ietf-enum-x-service-regs-01
Problem Statement • RFC 3761 and bis contain text about X- Enumservices • There is demand for trial and experimental Enumservices • Most of those services do not qualify even for the new registration process • E.g. if URI Scheme has not been defined yet • Why a registry? • Clash prevention • Information for ENUM implementors • Way to publish “X-” Enumservice work and gather feedback
Goals • Provide a simpler mechanism to register Enumservices for purpose of: • Trial • Experimental • Separate productive and experimental in terms of requirements for IANA registrations
Approach • Create (additional) IANA Registryfor X- Enumservices • Keeping barriers for registration low • Should those even be lower? • Re-use ordinary registration process (enumservice-guide) descriptions where applicable • Skip those parts not needed for 'X-'
Progress • Was hold up until IETF-71 (Philadelphia) • Reason: Major changes in enumservice-guide • Revision -01 published two months ago • Complete rewrite • Back in line with enumservice-guide • No feedback to revision -01 on the list • Personal feedback received during IETF-72 • Barriers for registration still to be lowered