From richard@shockey.us Thu, 02 Dec 2004 16:56:14 -0500 From: Richard Shockey Date: Thu, 02 Dec 2004 16:56:14 -0500 To: enum at ietf.org Subject: [Enum] FYI - CC1 ENUM LLC Technical Advisory Committee Meeting. Message-ID: <6.2.0.14.2.20041202153139.05640a70@sb7.songbird.com> MIME-Version: 1.0 Content-Type: text/plain Status: R CC1 ENUM LLC announces the creation of a Technical Advisory Committee (TAC) The TAC will prepare technical requirements recommendations for the Country Code 1 ENUM LLC to take into account when preparing the CC1 Tier 1 RFP. The TAC is open to all interested parties from North American Numbering Plan (NANP) countries who wish to participate. Kick-Off meeting - December 8, 2004 Time: 9 am to 5 pm Central Location: MCI AV Room 2400 N. Glenville Dr. Richardson TX Information Contact: Karen Mulberry MCI 972-729-7914 Scope of the TAC · To provide advice to the LLC on the CC1 Tier 1 A and Tier 1 B technical requirements. · To provide technical input on the standard interfaces between the different tiers/entities in the CC1 ENUM architecture. · To contemplate a minimum set of Tier 2 Provider and Registrar requirements The TAC will use existing industry documents and standards (e.g. ENUM Forum Tier 1 Requirements; CSCN documents; CC1 trial documents) as a baseline for developing their documents. The TAC output document(s) will be considered by the CC1 ENUM LLC in its development of the CC1 Tier 1 RFP. The TAC will provide its document(s) to the LLC by no later than April 4, 2005. Conference Bridge: Bridge Number: 203-607-2778 Passcode: 713148# DIRECTIONS FROM DFW AIRPORT TO MCI's CAMPBELL CREEK FACILITY RICHARDSON TX =============================================================== Use North exit from DFW terminal roadway. Go NORTH to Interstate Highway 635 EAST exit (AKA LBJ Freeway). Continue on Interstate Highway 635 EAST to U.S. Highway 75 NORTH (aka Central Expressway) approximately 15 miles. Get to your far RIGHT for the U.S. Highway 75 exit. Go North on U.S. Highway 75. Go north to the Campbell exit off U.S. Highway 75 approximately 5 miles. From the exit ramp turn RIGHT onto Campbell. Proceed on Campbell about 1/2 mile and turn LEFT onto Glenville Drive. The MCI building is on the right side (2400 Glenville Dr.). Turn right into complex. There are parking spaces close to the building for visitors. The Marriot Courtyard and Residence Inn are the closest hotels to the meeting location. List of hotels in the area: Marriott Residence Inn 1040 Waterwood Dr. 972-669-5888 Courtyard Dallas Richardson at Campbell 2191 N. Greenville Ave (972) 994-9933 Richardson 701 East Campbell Rd (972) 231-9600 Radisson Dallas North 1981 N. Central Expressway (972) 644-4000 Bradford Homesuites 2301 N. Central Expressway (972) 671-8080 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141 at fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From Internet-Drafts@ietf.org Fri, 03 Dec 2004 08:25:50 -0500 From: Internet-Drafts@ietf.org Date: Fri, 03 Dec 2004 08:25:50 -0500 To: i-d-announce at ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-epp-e164-08.txt Message-ID: <200412031215.HAA27956@ietf.org> MIME-Version: 1.0 Content-Type: text/plain Status: R A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : E.164 Number Mapping for the Extensible Provisioning Protocol Author(s) : S. Hollenbeck Filename : draft-ietf-enum-epp-e164-08.txt Pages : 17 Date : 2004-12-2 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-08.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-epp-e164-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv at ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-epp-e164-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From richard@shockey.us Fri, 03 Dec 2004 15:38:40 -0500 From: Richard Shockey Date: Fri, 03 Dec 2004 15:38:40 -0500 To: enum at ietf.org Subject: [Enum] FYI - ADDITIONAL INFORMATION - CC1 ENUM LLC Technical Advisory Committee Meeting. Message-ID: <6.2.0.14.2.20041203153405.05f7a070@sb7.songbird.com> MIME-Version: 1.0 Content-Type: text/plain Status: R _______________ Country Code 1 ENUM Limited Liability Company (CC1 ENUM LLC) Technical Advisory Committee (TAC) Organizational Meeting December 8, 2004 -- 9am to 5pm CST MCI AV Room 2400 N. Glenville Dr. Richardson, TX Conference Bridge: Bridge Number: 203-607-2778 Passcode: 713148# All persons planning to participate in the TAC meeting should send an email to the meeting host stating whether they will participate in person or via the conference bridge. The host for this session is MCI. (email: karen.mulberry at mci.com) TAC Chairman: Jim Baskin, Verizon TAC Vice-Chairman: Mir Islam, Sprint _____________ AGENDA 1. Welcome and Meeting Logistics [15 min] 2. Introduction/Roll Call of Participants [5 min] 3. TAC Mission/Scope and Relationship to the CC1 ENUM LLC [15 min] 4. Guidelines and Assumptions [20 min] 5. TAC Organization and Procedures [30 min] Break [20 min] 6. Baseline Architecture [120 min]* *Lunch [90 min - Starting around Noon [after the first 60 minutes of the Architecture discussion] 7. Deliverables [60 min] Break [15 min] 8. Timeline/Schedule [30 min] 9. Next meetings/conference calls [20 min] 10. Adjourn PLEASE NOTE: - No submissions marked confidential or proprietary will be accepted. - There will be no non-disclosure agreements. - All submissions will be considered "public" -- with unlimited right to use given to the LLC. - If a company's IPR is included in any submission they plan to make to the TAC, they should state that in writing in the introduction to the submission. Submissions containing company-specific IPR may not be considered by the TAC. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141 at fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From Patrick.Guillemin@etsi.org Tue, 07 Dec 2004 04:58:13 -0500 From: =?iso-8859-1?Q?Patrick_Ren=E9_Guillemin?= Date: Tue, 07 Dec 2004 04:58:13 -0500 To: Subject: [Enum] ENUM products for interop testing ? Message-ID: <4091553999CBE4409CC2B562152B5A33049541A1@email10.etsihq.org> MIME-Version: 1.0 Content-Type: text/plain Status: R Dear All, Please review, comment and extend this ENUM list as needed ;-) Scope - What are the existing ENUM products (*) on the market today Dec 2004? - Who would like to come and test ENUM in may/june 2005 ? - What tools are available to test ENUM ENUM Products on the market (to be commpleted as needed) SIP Gateway - Asterisk IP PBX: www.asterisk.org - Cisco SIP Proxy - IPTEL SIP Express Router: www.iptel.org/ser - Hardware SIP Phones: SNOM Phones www.snom.com (*) First face-to-face and remote ENUM tests organized by ETSI Plugtests In coordination with maximum of ENUM parties will focus on User ENUM. Carrier ENUM, Infrastructure ENUM or Enterprise ENUM will be considered later. Other - PowerDNS: www.powerdns.com - BIND from ISC: www.isc.org - SIP soft-phone X-lite X-Ten Networks: www.xten.com - Hardware Routers IX66 from Intertew: www.intertex.se - Nominum DNS products with management APIs: www.nominum.com - Internet Foundation Austria Open Source: www.enum.at - Managed DNS: secure.dns-hosting.info - NASK Registrar interface for ENUM (including billing) - NASK ENUM Phonebook (Personal Java) for mobile phones - JPRS ENUM Software LIbraries in Perl: jprs.co.jp/enum/software/software.html ... implementations of ENUM Registry system based on EPP www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-08.txt - OpenREG (EPP) from ISC: www.isc.org - NASK -EPP registry development ... Companies or Organizations where to find participants & resources for the 1st ENUM tests on User ENUM Update and comment as needed - Verisign - NetNumber - Neustar http://www.enum.org/information/resources.cfm http://www.cybertelecom.org/dns/enum.htm - Cisco http://www.cisco.com/en/US/about/ ac123/ac147/ac174/ac179/about_cisco_ipj_archive_article09186a00800e55d4.html - Ficora http://www.ficora.fi/englanti/tele/enum.htm - Telcordia - THEVPF: www.thevpf.com ... ENUM Resources ITU-T http://www.itu.int/osg/spu/enum/ IETF http://www.ietf.org/html.charters/enum-charter.html RIPE-NCC http://www.ripe.net/rs/enum/ ETSI TC TISPAN, ENUM Workshop, ENUM Plugtests + Task Force (EPTF) http://portal.etsi.org/tispan/WG4_Tor.asp http://www.etsi.org/plugtests ETSI ENUM: http://pda.etsi.org/pda/queryform.asp - ETSI TS 102 051 ENUM Administration in Europe - ETSI TS 102 172 Minimun requirements for interoperability of European ENUM trials http://portal.etsi.org/docbox/tispan/open/ENUM-Workshop-20041130-Sophia/ http://portal.etsi.org/docbox/tispan/open/ENUM-Workshop-20040224-Sophia/ (EPTF) ICANN http://www.icann.net/ http://www.icann.org/committees/adhoc/mcfadden-holmes-report-08mar01.htm 3GPP http://www.3gpp.org/ftp/tsg_cn/WG1_mm-cc-sm/ VON and Pulver.com ENUM Forum http://www.enum-forum.org/ All ENUM Trials http://www.centr.org/kim/enum/index.html APEET : www.apenum.org Asia Pacific ENUM Engineering Team ... BR Thanks in advance ENUM product list, Modified on 6 December 2004 Patrick.GUILLEMIN at ETSI.ORG www.etsi.org/plugtests _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From jwkckid1@ix.netcom.com Wed, 15 Dec 2004 09:37:48 -0500 From: Jeff Williams Date: Wed, 15 Dec 2004 09:37:48 -0500 To: "J-F C. (Jefsey) Morfin" Subject: [Enum] Re: [ga] Sir Berners-Lee on specific problems with .mobi In-Reply-To: <41BFB842.4060702@hermesnetwork.com> Message-ID: <41C0654D.DF5324E9@ix.netcom.com> MIME-Version: 1.0 Content-Type: text/plain Status: R Jefsey and all former DNSO GA members or other interested stakeholders/users, FWIW, .mph or .mphn would have made allot more sense. As to ENUM and the IETF, that situation has gone bonkers for some time now.. J-F C. (Jefsey) Morfin wrote: > Please let stop this confusion. Either Joop is right and ICANN looks for > money even if they kill the net. > > Or the .mobi TLD has per se nothing to do with mobiles but with mobile > owners (this is why I quoted gangsters). The last quote of BL by Sotiris > then applies. I do not know what BL realy meant by "portal" in Sotiris > first quote as the document was not explicit, but I registered the TM > "tipi" for a "telephone internet personal interface" as a portal of the > services a user could get/offer and the info and service I could put on > line about my telephone/mobile. The image of a Tipi being "my personal > mobile home" and because I had made a deal with the now frozen ".top" > ccTLD. For example jefsey.tipi would be for me the place to control my > mobile/telephone menu, for people to drop me a short mail, to know where I > am, etc. > > We would need to review the ".mobi" application (where is it?). If it is > meant to be domain names for mobiles, they already are one: anyone's > existing domain name used with a telephone scheme. http://ibm.com is IBM > web site and tel://ibm.com is the IBM telephone desk. A domain name shoud > not be used to replace a missing RR. If the IETF is unable to deliver > (where are IDNs, where is IPv6, where > is ENUM, who defined NATs, VoIP, P2P, ICQ, etc.) then the IETF must be > replaced. > > The correct db.file should read. > > domain.name. SOA ............ > A IP of the web site > MX IP of the mail server > TEL IP of the telephone exchange > > and NOT: > > domain.name. SOA ............ > A IP of the web site > MX IP of the mail server > > domain.mobi > A IP of the telephone exchange > > Also a major problem at not resolving ENUM properly is the IP of the > telephone number. If I register 33142928100.mobi what will happen? This is > a non TM protected name. I like its symbolic a lot because it sums as 33, > it has 11 digit, it ends in 00, starts in 33 and the sum divided by 11 is 3 > while the central digit is 3 by 3 = 9, with the first segment 142 adding to > 7 and starting with 1 and the end of the second segment 81 (starting with > 2) subtracting to 7 while the two side digits of the central digits are > equal a 2. So I have good grounds to show I am a bona fide registrant for > a bingo site, all the more than no one can object to my owning of > 33142928100.com etc. > > Yet this is the phone number of Jacques Chirac. > jfc Regards, -- Jeffrey A. Williams Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!) "Be precise in the use of words and expect precision from others" - Pierre Abelard "If the probability be called P; the injury, L; and the burden, B; liability depends upon whether B is less than L multiplied by P: i.e., whether B is less than PL." United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947] =============================================================== Updated 1/26/04 CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS. div. of Information Network Eng. INEG. INC. E-Mail jwkckid1 at ix.netcom.com Registered Email addr with the USPS Contact Number: 214-244-4827 _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From iesg-secretary@ietf.org Thu, 23 Dec 2004 10:27:03 -0500 From: The IESG Date: Thu, 23 Dec 2004 10:27:03 -0500 To: IETF-Announce Subject: [Enum] Protocol Action: 'E.164 Number Mapping for the Extensible Provisioning Protocol' to Proposed Standard Message-ID: MIME-Version: 1.0 Content-Type: text/plain Status: R The IESG has approved the following document: - 'E.164 Number Mapping for the Extensible Provisioning Protocol ' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. Technical Summary ENUM (RFC 3761) describes how the Domain Name System (DNS) can be used to identify services associated with an E.164 number. The EPP (RFC 3730) mapping described in this document specifies a mechanism for the provisioning and management of E.164 numbers stored in a shared central repository. Information exchanged via this mapping can be extracted from the repository and used to publish DNS resource records as described in ENUM. Examples used in this document were chosen specifically to illustrate provisioning concepts for the example resource records described in the ENUM specification. Working Group Summary The working group strongly supported this work. At the time of development, there was no longer a working group for EPP, but the principle of extensions for EPP has been for them to be developed in their subject working groups. There was one Last Call comment with a concern about a capability, but this concern was well addressed by discussion on the IETF mailing list, and the commenter withdrew the concern. Protocol Quality The document was reviewed for the IESG by Allison Mankin. This specification has been prototyped. IESG review required a small revision to improve the alignment of the document with RFC 3761. _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From iesg-secretary@ietf.org Fri, 24 Dec 2004 06:52:36 -0500 From: "IETF-IESG-Support via RT" Date: Fri, 24 Dec 2004 06:52:36 -0500 To: enum at ietf.org Subject: [Enum] [Inquiry #28743] AutoReply: In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain Status: R Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #28743] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #28743] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary at ietf.org ------------------------------------------------------------------------- _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum From iesg-secretary@ietf.org Tue, 28 Dec 2004 05:22:52 -0500 From: "Markou Kleoniki via RT" Date: Tue, 28 Dec 2004 05:22:52 -0500 To: enum at ietf.org Subject: RE: [Enum] [Inquiry #28743] AutoReply: In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain Status: R -----Original Message----- From: IETF-IESG-Support via RT [mailto:iesg-secretary at ietf.org] Sent: Friday, December 24, 2004 1:53 PM To: enum at ietf.org Subject: [Enum] [Inquiry #28743] AutoReply: Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #28743] in the queue: IETF-IESG-Support. Please include the string: [Inquiry #28743] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, iesg-secretary at ietf.org ------------------------------------------------------------------------- _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum at ietf.org https://www1.ietf.org/mailman/listinfo/enum