1 / 4

IETF ENUM WG Guide for IANA Enumservices Registrations

This document provides a guide and template for the creation of new IANA registrations of Enumservices, aiming to clarify the required sections and capture best current practices. It addresses open questions regarding subtypes and registration format.

junitaj
Télécharger la présentation

IETF ENUM WG Guide for IANA Enumservices Registrations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF 65 – ENUM WGGuide and Template for IANA Registrations of Enumservices <draft-ietf-enum-enumservices-guide-00>20 March 2006Co-Authors:Bernie HoeneisenJason Livingood

  2. History of the Draft • -00 Released Feb. 2006, after WG discussion going back several months. • Attempts to fulfill a need to provide a template for the creation of new Enumservices, as well as clear explanations of the various recommended and required sections. …provides a guide to and template for the creation of new IANA registrations of Enumservices. This document aims to enhance section 3 of RFC 3761, where the registration procedure for Enumservices was initially documented at a high level. However, the IETF's ENUM Working Group has encountered an unnecessary amount of variation in the format of Enumservice drafts presented to the group. The ENUM Working Group's view of what particular fields and information are required and/or recommended has also evolved, and capturing these best current practices is helpful in both the creation of new registrations, as well as the revision or refinement of existing registrations.

  3. Requests for Input The authors request suggested content for: • Section 3.2, explanatory text for “Intended Usage: COMMON” section. • Section 3.6, explanatory text for “IANA Considerations.”

  4. Open Questions Section 3.2: Discussion & Questions Current Text:3.2. Enumservice Registration for "foo" with Subtype "bar" (MANDATORY) This section MUST be included in an Enumservice registration. In addition, where a given registration type has multiple subtypes, there MUST be a separate registration section for each subtype. The following lists the sections and order of an Enumservice Registration section. All types and subtypes SHOULD be listed in lower-case. Questions: 1 – Should a sub-type always be specified? 2 – Should there be a separate registration for each sub-type? 3 – Should there be a separate sub-type for each URI scheme? 4 – Should there by any statement on the use of non-terminal NAPTRs?

More Related