Telephone Number Mapping WG (enum) WEDNESDAY, August 4 at 1300-1500 ================================ CHAIRS: Patrik Faltstrom Richard Shockey Transport Area Advisor: Allison Mankin Mailing Lists: General Discussion:enum@ietf.org To Subscribe: enum-request@ietf.org In Body: subscribe Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/ AGENDA: AGENDA BASHING (5 min) ( appointment of scribe etc) Ok who wants to volunteer? # 1 Review of the ENUM Operations Document [ 10 Min] Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-00.txt Pages : 0 Date : 2004-7-12 This 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-00.txt # 2 Overview of the cost optimization of telecommunication connections based on ENUM as described in the ID "draft-bartosiewicz-enterprise-enum-00.txt".[ 10 Min] # 3 Disposition of [ 10 Min] Title : E.164 Number Mapping for the Extensible Provisioning Protocol Author(s) : S. Hollenbeck Filename : draft-ietf-enum-epp-e164-04.txt Pages : 17 Date : 2004-6-8 This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of E.164 numbers representing domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of E.164 numbers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-04.txt I'd very much like to come to some conclusion on how this document should progress. IMHO it is an extremely valuable addition to the work effort but it has not had much discussion on the list. Perhaps Experimental. I dont know. As we see deployments progressing the entire issue of provisioning has not IMHO received sufficient attention. #4 ENUM VOID [ 10 Min] Title : IANA Registration for enumservice void Author(s) : R. Stastny, L. Conroy Filename : draft-stastny-enum-void-00.txt Pages : 7 Date : 2004-7-13 This document registers the 'ENUMservice' 'void' using the URI scheme 'mailto:' as per the IANA registration process defined in the ENUM specification RFC3761 [2]. This 'ENUMservice' SHALL be used to indicate that the E.164 number or E.164 number range connected to the domain used in DNS as described in [2] is not assigned to an end-user in case of an E.164 number or to a communication service provider in case of an E.164 number range. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-stastny-enum-void-00.txt Carrier - Infrastructure ENUM Mini-BOF [ 1 hour ] R. Stastny J. Seng co-chairs A. Introduction to the problem statement ( R. Shockey) NOTE to participants. The chairs wish to remind the list that the discussion of this topic in San Diego should follow the following guidelines. 1 What is the Problem Statement here 2. What are the Requirements that address the Problem. 3. Discussion of specific approaches to a solution are out of scope. This is what IETF BOF's do : define problems, scope requirements decide on next steps if any. To that end in mind we would appreciate if Penn Pfauts & Steve Lind could discuss their draft for 10min or so in that specifically and narrowly defined context. Title : A Combined User/Carrier ENUM Author(s) : P. Pfautz, S. Lind Filename : draft-pfautz-lind-enum-carrier-00.txt Pages : 5 Date : 2004-7-8 This document considers how so-called "carrier" or "infrastructure" ENUM and "end user" or "public" ENUM can share a single Tier 1 registry yet have independent Tier 2 providers. This approach allows the common cooperative infrastructure required by ENUM to be shared by end users and carriers reducing costs and facilitating adoption of ENUM generally. The essence of the proposal is to populate the Tier 1 registry with non-terminal NAPTRs rather than NS records and use different ENUM service fields for carrier and end user records. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-pfautz-lind-enum-carrier-00.txt