Last Modified: 2005-05-20
Done | Initial draft of Service ENUM Requirements | |
Done | Initial draft of ENUM Protocol | |
Done | Revised draft of ENUM Protocol | |
Done | Submit ENUM Protocol document to IESG for publication as Proposed | |
Done | Revise and update RFC 2916 appropriate to DDDS (revision of 2915) | |
Done | ENUM service registrations for SIP and H.323 | |
Aug 03 | Document appropriate ENUM Security and Privacy Issues (Informational) | |
Nov 03 | Document appropriate ENUM Registration and Provisioning Procedures (Informational) |
RFC | Status | Title |
---|---|---|
RFC2916 | PS | E.164 number and DNS |
RFC3482 | I | Number Portability in the Global Switched Telephone Network (GSTN): An Overview |
RFC3761 | Standard | The E.164 to URI DDDS Application (ENUM) |
RFC3762 | Standard | ENUM Service Registration for H.323 URL |
RFC3764 | Standard | enumservice registration for SIP Addresses-of-Record |
RFC3953 | Standard | Enumservice Registration for Presence Services |
RFC4002 | Standard | IANA Registration for ENUMservices web and ft |
RFC4114 | Standard | E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) |
IETF 63 Telephone Number Mapping (ENUM) WG Meeting Minutes
Chair(s): Patrik Faltstrom <paf@cisco.com> Richard Shockey <rich.shockey@neustar.biz> Transport Area Advisor: Allison Mankin <mankin@psg.com> Friday, August 6 2005 9:AM to 12:30 PM AGENDA BASHING (5 min) 1. Review of the existing drafts - Ready to go top Last call ( 5-10 M ? ) Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-02.txt Pages : 29 Date : 2005-7-1This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is informational only, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-02.txt WG ACTION : After some minor discussion agreement that the document should go through one more iteratina and then take directly to WGLC. 2. Final disposition of IRIS EREG, hopefully to last call. ( 5 Min? ) A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-newton-iris-ereg-00.txt WG ACTION : Put this document into WGLC after one more revision by author. DISCUSSION Some concerns whether this document is mature enough for even WG last call, response is that the document will see another revision and pushing towards last call is only meant to spur document forward. 3. New/old work on enumservice registrations ( 20 M ) 3.1 Title : IANA Registration for Enumservice Voice Author(s) : R. Brandner, et al. Filename : draft-brandner-enum-voice-00.txt Pages : 12 Date : 2005-7-7This document registers the ENUMservice ^voice^ (which has a defined sub-type ^tel^), as per the IANA registration process defined in the ENUM specification RFC3761. This service indicates that the contact held in the generated URI can be used to initiate an interactive voice (audio) call. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-brandner-enum-voice-00.txt WG ACTION : WG humm agrees to draft as ENUM WG work item. Given the straightforward nature of this draft it is probable that it can go to WGLC after one iteration. DISCUSSION: Document is a simplification of a larger ENUM service registration document on voice services. The document only specifies the concept of voice:tel. 3.2 Title : IANA Registration for an Enumservice Containing Number Portability and PSTN Signaling Information Author(s) : J. Livingood, R. Shockey Filename : draft-livingood-shockey-enum-npd-00.txt Pages : 8 Date : 2005-7-8This document registers the Enumservice "npd" and subtype "tel" using the URI scheme 'tel:' as per the IANA registration process defined in the ENUM specification, RFC 3761. This data is used to facilitate the routing of telephone calls in those countries where Number Portability exists. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-livingood-shockey-enum-npd-00.txt WG ACTION : WG humm agrees to draft as ENUM WG work item. DISCUSSION : Comments include:
3.3 Title : IANA Registration for ENUMservice Mobile Webpage Author(s) : J. Ra, et al. Filename : draft-ra-shin-enum-mobileweb-00.txt Pages : Date : 2005-7-7This document registers the ENUMservice "mobweb" using the URI schemes 'http:' and 'https:' as per the IANA registration process defined in the ENUM specification RFC3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ra-shin-enum-mobileweb-00.txt WG ACTION: Considerable disagreement on the nature and scope that this document ultimately has. WG decision NOT to make WG item at this time. DISCUSSION: Discussion dove into issue of DNS vs. Application layer indication of protocol stack capabilities.
4. ENUM Validation Issues. 3 Drafts 15 -20 4.1 ENUM Validation Architecture draft-mayrhofer-enum-validation-arch-00 Title : ENUM Validation Architecture Author(s) : A. Mayrhofer, B. Hoeneisen Filename : draft-mayrhofer-enum-validation-arch-00.txt Pages : 16 Date : 2005-7-11An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether or not the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called ^validation^. This document describes validation requirements and a high level architecture for an ENUM validation infrastructure. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-validation-arch-00.txt WG ACTION : WG humm agrees to draft as ENUM WG work item. 4.2 "ENUM Validation Token Format Definition" - draft-lendl-enum-validation-token-00.txt Title : ENUM Validation Token Format Definition Author(s) : O. Lendl Filename : draft-lendl-enum-validation-token-00.txt Pages : 16 Date : 2005-7-11An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called ^validation^. This document describes an signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lendl-enum-validation-token-00.txt WG ACTION : WG humm agrees to draft as ENUM WG work item. 4.3 Bernie Hoeneisen http://ietf.hoeneisen.ch/draft-ietf-enum-validation-epp-00.txt http://ietf.hoeneisen.ch/draft-ietf-enum-validation-epp-00.html WG ACTION : WG humm agrees to draft as ENUM WG work item. DISCUSSION: Very little technical discussion of the above 3 documents. ################# 5. PART 2 1/2 hours. 3 Items WG AGENDA: Terms and Conditions of discussion. The first order of business is to attempt to create some very basic common ground on what is the problem Carrier/Infrastructure/Private ENUM is trying to solve based on what we generally understand are the orthogonal interests of A. the E.164 number holder vs B. the carrier of record for that number. In addition try to place this problem statement in the over all context of converged carrier networks and the desire for interconnection and peering. We are NOT going to solve the Carrier ENUM definition and problem statement in Paris but there needs to be some baseline before we can generally review the drafts at hand. ################# 5.1 Discussion of drafts on Carrier ENUM - Requirements ? Title : Infrastructure ENUM Requirements Author(s) : S. Lind Filename : draft-lind-infrastructure-enum-reqs-00.txt Pages : 8 Date : 2005-7-15There has been much discussion in various industries about the concept of infrastructure (or carrier) ENUM. Some of this discussion has been has been reflected within the ENUM WG mailing list and some within other organizations, including ETSI, the US ENUM Forum and the Country Code 1 ENUM LLC. While there has been consensus within some pockets of individual efforts, there has been little consensus industry-wide on even what infrastructure ENUM is, why it seems to be important, or what the requirements for implementing it are. At the request of the WG co-chairs, this document attempts to gather together the bits and pieces from those discussions (i.e., I stole the words shamelessly from the various sources) and, with an absolute minimum of editing, present them in some sort of cohesive manner that will enable enlightened discussion and hopefully achieve consensus. Some items listed below may be duplicative and suggest alternative wordings for similar and other contradictory issues. As such, this list is very raw and should not be viewed as complete, cohesive or correct. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lind-infrastructure-enum-reqs-00.txt WG ACTION: This document is now a WG item and is a requirement for any other protocol drafts concerning carrier/infrastructure ENUM. Steve Lind thanked for putting such a document together on such short notice. Penn Pfautz agrees to collaborate with Steve Lind on future drafts. 5.2 Title : IANA Carrier/User enumservice Registration Author(s) : P. Pfautz, et al. Filename : draft-pfautz-lind-enum-carrier-user-00.txt Pages : 10 Date : 2005-6-6This document registers, pursuant to the guidelines in RFC 3761, tElephone NUmber Mapping (ENUM) services to allow a single registry to support end user and carrier services with independent name servers holding the terminal NAPTR (Naming Authority Pointer) records identifying the communication services for each. The to-be- registered enumservices make use of non-terminal NAPTR records and DDDS (Dynamic Delegation Discovery System) replacement to achieve this end. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-pfautz-lind-enum-carrier-user-00.txt 5.3 Title : Combined User and Carrier ENUM in the e164.arpa tree Author(s) : M. Haberler, R. Stastny Filename : draft-haberler-carrier-enum-00.txt Pages : 10 Date : 2005-7-11ENUM as defined now in RFC3761 is not well suited for the purpose of interconnection by carriers, as can be seen by the use of various private tree arrangements based on ENUM mechanisms. A combined end- user and carrier ENUM tree solution would leverage the ENUM infrastructure in e164.arpa, increase resolution rates, and decrease the cost per registered telephone number. This document describes aminimally invasive scheme to provide both end-user and carrier data in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-haberler-carrier-enum-00.txt DISCUSSION: Pfautz and Haberler Carrier ENUM drafts were discussed together. As opposed to end user, opt-in ENUM, this is registration of information in DNS for carriers. Service provider of record as opposed to the number holder is considered the effective registrant. Three approaches were mentioned but only two seem "obvious". Non-terminal NAPTR records Records are placed in e164.arpa domain, at the tel number. One record for end user other for carrier. Differentiation is inside NAPTR record with the use of the NAPTR substititution field to indicate different re-write rules to generate the next lookup. Separated branches of the DNS tree
Requirements/Desired results
DISCUSSION:
WG ACTION : Chair asks for a show of hands whether the WG should accept the general concept of Carrier ENUM as a WG item. There was a large show of hands that Carrier ENUM is of interest as a work topic no dissentions. Further Discussion on Next Steps
WG ACTION: Requirements document added as WG item.
The Chair also asked for a non binding "straw poll" based on the three approaches on which is preferred "at this time". 3 Options
Further Discussion: Division of labor with VOIPEER BoF effort required 6.0 Title : Non-Terminal NAPTR Processing: A Modest Proposal Author(s) : L. Conroy Filename : draft-conroy-enum-modestproposal-00.txt Pages : 12 Date : 2005-7-6 Recent Discussions within the IETF and in other fora have highlighted differences in interpretation of the set of standards associated with ENUM and DDDS, on which it relies. Specifically, the operation and semantics surrounding support for non-terminal NAPTRs has led to some confusion. This document is n attempt to add clarification to non- terminal NAPTR processing. In this, it clarifies RFC3403. A subsequent document will build on this one to extend FC3761 further, permitting registration of non-terminal Enumservices. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-conroy-enum-modestproposal-0.txt WG ACTION : No action taken. Document may be incorporated into revision of RFC 3761 since it is clear there are a number of changes that have to be made before it could become Draft Standard. Meeting Concludes. |