From enum-bounces@ietf.org Mon Oct 02 11:26:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUPf7-0005Hm-Pa; Mon, 02 Oct 2006 11:24:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUPf6-0005G8-DQ for enum@ietf.org; Mon, 02 Oct 2006 11:24:56 -0400 Received: from s-utl01-ffpop.stsn.net ([62.50.216.201]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GUPf3-000882-Uq for enum@ietf.org; Mon, 02 Oct 2006 11:24:56 -0400 Received: from s-utl01-ffpop.stsn.net ([127.0.0.1]) by s-utl01-ffpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2006100217245200808 for ; Mon, 02 Oct 2006 17:24:52 +0200 X-Spam-Status: No, hits=0.0 required=9.9 tests=ALL_TRUSTED: -2.4,AWL: 0.899,SARE_RECV_ADDR: 0.027 X-Spam-Level: Received: from RSHOCKEYLTXP ([10.72.27.238]) by s-utl01-ffpop.stsn.net for enum@ietf.org; Mon, 2 Oct 2006 17:24:50 +0200 From: "Richard Shockey" To: Date: Mon, 2 Oct 2006 11:24:27 -0400 Message-ID: <02b101c6e636$e33a7780$ee1b480a@cis.neustar.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_02B2_01C6E615.5C28D780" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 thread-index: AcbmMjZG79XOB56wQUuXB6CcE7FoNAABJfBA X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Subject: [Enum] FW: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. ------=_NextPart_000_02B2_01C6E615.5C28D780 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Monday, October 02, 2006 10:50 AM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : IANA Registration for Enumservice 'XMPP' > Author(s) : A. Mayrhofer > Filename : draft-mayrhofer-enum-xmpp-00.txt > Pages : 7 > Date : 2006-10-2 > > This document requests IANA registration of an Enumservice for > Extensible Messaging and Presence Protocol (XMPP) Uniform Resource > Identifiers (URIs) according to the registration procedure outlined > in RFC 3761. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@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-mayrhofer-enum-xmpp-00.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@ietf.org. > In the body type: > "FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.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. ------=_NextPart_000_02B2_01C6E615.5C28D780 Content-Type: Message/External-body; name="ATT00620.dat" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00620.dat" Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.txt ------=_NextPart_000_02B2_01C6E615.5C28D780 Content-Type: Message/External-body; name="draft-mayrhofer-enum-xmpp-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-mayrhofer-enum-xmpp-00.txt" Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> ------=_NextPart_000_02B2_01C6E615.5C28D780 Content-Type: text/plain; name="ATT00623.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00623.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------=_NextPart_000_02B2_01C6E615.5C28D780 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_02B2_01C6E615.5C28D780-- From enum-bounces@ietf.org Mon Oct 02 12:24:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQZg-0005Gv-9C; Mon, 02 Oct 2006 12:23:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUQZe-0005Cw-KX for enum@ietf.org; Mon, 02 Oct 2006 12:23:22 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUPNu-0005lS-8J for enum@ietf.org; Mon, 02 Oct 2006 11:07:10 -0400 Received: from s-utl02-ffpop.stsn.net ([62.50.216.202]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1GUPCN-0005bk-M6 for enum@ietf.org; Mon, 02 Oct 2006 10:55:22 -0400 Received: from s-utl02-ffpop.stsn.net ([127.0.0.1]) by s-utl02-ffpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2006100216551300966 for ; Mon, 02 Oct 2006 16:55:13 +0200 X-Spam-Status: No, hits=0.0 required=9.9 tests=ALL_TRUSTED: -2.4,AWL: -1.084,BIZ_TLD: 2.167, SARE_RECV_ADDR: 0.027 X-Spam-Level: Received: from RSHOCKEYLTXP ([10.72.27.238]) by s-utl02-ffpop.stsn.net for enum@ietf.org; Mon, 2 Oct 2006 16:55:13 +0200 From: "Richard Shockey" To: Date: Mon, 2 Oct 2006 10:54:47 -0400 Message-ID: <029801c6e632$bb5e71c0$ee1b480a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 thread-index: AcbmMrRBCroXWbGAR9uc2edPgjInfw== X-Spam-Score: 0.3 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Subject: [Enum] Draft Meeting Agenda... X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org It looks like Monday again but I would not plan your travel on this data. http://www.ietf.org/meetings/67-agenda.txt DRAFT Agenda of the Sixty-Seventh IETF November 5-10, 2006 Updated October 1, 2006 SUNDAY, November 5, 2006 1000-1230 IEPG Meeting - 1200-1900 Registration - 1300-1445 Newcomers' Training - 1300-1445 Editing an RFC Tutorial - 1300-1445 What MIB Document Editors Need to Know - 1500-1645 Bringing New Work to the IETF - 1500-1645 Working Group Leadership Tutorial - 1500-1645 Security Tutorial - 1700-1900 Welcome Reception - MONDAY, November 6, 2006 0800-1800 IETF Registration - 0800-0900 Continental Breakfast - 0900-1130 Morning Session I APP apparea Applications Area Open Meeting INT pana Protocol for carrying Authentication for Network Access WG OPS v6ops IPv6 Operations WG RAI sipping Session Initiation Proposal Investigation WG RTG ccamp Common Control and Measurement Plane WG RTG manet Mobile Ad-hoc Networks WG SEC spkm NFSv4 and Low Infrastructure Public Key Based GSS Security Mechanisms BOF TSV ippm IP Performance Metrics WG 1130-1300 Break 1300-1500 Afternoon Session I APP calsify Calendaring and Scheduling Standards Simplification WG GEN eduteam Edu Team INT l2vpn Layer 2 Virtual Private Networks WG INT mip6 Mobility for IPv6 WG RAI enum Telephone Number Mapping WG SEC emu EAP Method Update WG TSV dccp Datagram Congestion Control Protocol WG 1500-1520 Afternoon Beverage Break - 1520-1720 Afternoon Session II APP sieve Sieve Mail Filtering Language WG INT intarea Internet Area Open Meeting OPS capwap Control And Provisioning of Wireless Access Points WG RAI p2psip Peer to Peer Session Initiation Protocol BOF RTG forces Forwarding and Control Element Separation WG TSV nfsv4 Network File System Version 4 WG TSV rohc Robust Header Compression WG 1720-1740 Afternoon Snack and Beverage Break - 1740-1840 Afternoon Session III INT autoconf Ad-Hoc Network Autoconfiguration WG OPS netconf Network Configuration WG RAI geopriv Geographic Location/Privacy WG RTG pim Protocol Independent Multicast WG SEC btns Better-Than-Nothing Security WG TSV tsvarea Transport Area Open Meeting 1850-1950 Afternoon Session IV INT autoconf Ad-Hoc Network Autoconfiguration WG OPS netconf Network Configuration WG RAI geopriv Geographic Location/Privacy WG RTG pim Protocol Independent Multicast WG SEC btns Better-Than-Nothing Security WG TSV tsvarea Transport Area Open Meeting Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 02 13:11:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURJP-0005zz-Sc; Mon, 02 Oct 2006 13:10:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURJO-0005zu-Hc for enum@ietf.org; Mon, 02 Oct 2006 13:10:38 -0400 Received: from s-utl02-ffpop.stsn.net ([62.50.216.202]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GURJN-000490-9H for enum@ietf.org; Mon, 02 Oct 2006 13:10:38 -0400 Received: from s-utl02-ffpop.stsn.net ([127.0.0.1]) by s-utl02-ffpop.stsn.net (SMSSMTP 4.1.2.20) with SMTP id M2006100219103601336 for ; Mon, 02 Oct 2006 19:10:36 +0200 X-Spam-Status: No, hits=0.0 required=9.9 tests=ALL_TRUSTED: -2.4,AWL: -0.418,BIZ_TLD: 2.167, SARE_RECV_ADDR: 0.027 X-Spam-Level: Received: from RSHOCKEYLTXP ([10.72.27.238]) by s-utl02-ffpop.stsn.net for enum@ietf.org; Mon, 2 Oct 2006 19:10:34 +0200 From: "Richard Shockey" To: Subject: SECOND REMINDER [Enum] Its that time again to start thinking about San Diego Date: Mon, 2 Oct 2006 13:10:18 -0400 Message-ID: <02ef01c6e645$a9a17320$ee1b480a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 thread-index: Acbe+zysU/md/nLMRmijdVg/cFT28wHSkFKw In-Reply-To: <000501c6defb$452fdcc0$22dd100a@cis.neustar.com> X-Spam-Score: 0.5 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > Its agenda planning time again! > > If you plan on making a presentation for discussion you should get your > drafts in ASAP and let the chairs know how much time you need etc. > > > Richard Shockey > Director, Member of the Technical Staff > NeuStar > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org > sip:5651(at)neustarlab.biz > PSTN Office +1 571.434.5651 > PSTN Mobile: +1 703.593.2683 > > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUF-0004GH-Td; Fri, 06 Oct 2006 10:15:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVU6b-0001Fz-29 for enum@ietf.org; Thu, 05 Oct 2006 10:21:45 -0400 Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVU6Y-0002bM-9D for enum@ietf.org; Thu, 05 Oct 2006 10:21:45 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id 21EF21A36D; Thu, 5 Oct 2006 16:21:40 +0200 (CEST) Date: Thu, 5 Oct 2006 16:21:40 +0200 From: Otmar Lendl To: Patrik =?iso-8859-15?B?RuRsdHN0cvZt?= Subject: Re: [Enum] draft-ietf-enum-uri-00.txt Message-ID: <20061005142140.GC12719@nic.at> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Cc: IETF ENUM WG X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org [There seems to be a problem with enum@ietf.org, an earlier mail from me didn't make it back to my mailbox.] On 2006/09/28 11:09, Patrik F=E4ltstr=F6m wrote: > This document was requested to be published the other day, but =20 > publication seems to take some time. Thanks for the document, here are some question: >=20 > 1. =20 > Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 > 2. Applicability =20 > Statement . . . . . . . . . . . . . . . . . . . 3 The formatting is a bit off (not only here, but also in the=20 rfc-editor repository), could you please submit a version without unwanted line-breaks, and with page breaks? Concerning this example: > 6.2. Different providers for services for the same E.164 >=20 > An organisation have the E.164 +442079460148, but different > organisations handle routing of calls for the number on the Internet > (with the help of SIP) and traditional PSTN. More specifically, the > two providers want to run DNS for the record(s) that refer to the > services they provide. I think I understand the pure DNS mechanics you propose. What I can't see right now is how this proposal fits into the Tier0/Tier1/ITSP/end-user scheme of actors. Where are the=20 zone cuts and who is operating which zone? > The ENUM provider for the +44 country code in this case not only do > delegations on the full E.164 number, but delegations on the service > parameter values, as can be seen below: >=20 > In this example we also include the NAPTR records that with the help > of the 'D' flag refer to the URI records. We also include NAPTR > records according to RFC 3761 [RFC3761] that give backward > compatibility. >=20 > In zone 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa.: Who do you propose should run that zone? > $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. >=20 > ;; NAPTR records that refer to URI records > IN NAPTR 1 1 "D" "E2U:sip" ( ; service > "" ; regexp > _sip._e2u ; replacement > ) >=20 > IN NAPTR 1 1 "D" "E2U:tel" ( ;service > "" ;regexp > _tel._e2u ;replacement > ) This record is *important* to the telco running the phone service for this number. They won't want to live with the possibility that users can mess up the telco internal routing. >=20 > ;; NAPTR records for RFC 3761 compatibility > IN NAPTR 1 1 "U" "E2U:sip" ( ;service > "!.*!sip:+442079460148@sipprovider.net!" ; regexp > . ; replacement > ) In the current model, this record is supposed to be hosted on a user-controlled server. This puts us into a bind:=20 > IN NAPTR 1 1 "U" "E2U:tel" ( ;service > "!.*!sip:+442079460148@sipprovider.net!" ; regexp > . ; replacement > ) >=20 > ;; Delegations to child zones > _sip._e2u IN NS ns1.example.net. > _tel._e2u IN NS ns1.example.com. Once again, the I-ENUM records are dependent on the management of the pure ENUM zone 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > In zone _sip._e2u.8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa: >=20 >=20 > $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > _sip._e2u IN URI "sip:+442079460148@example.net" Shouldn't that be=20 $ORIGIN _sip._e2u.8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. @ IN URI "sip:+442079460148@example.net" to indicate where the zone-cut is? ----------------------------- To summarize: If I were to start an ENUM deployment from scratch, this proposal fine (except, see below). In this case, I'd put the IN NAPTR 1 1 "D" records in the Tier1 zone (autocreated based on *._e2u entries) and just delegate (optionally) the _sip._e2u subdomains to subscribers or ITSPs. That way, the DNS infrastructure of one application can be kept independent from the one of another application. The problem is the legacy 3761 support: For all the delegated domains out there, it is not acceptable for the carriers to go to their subscribers and asks them for a delegation of _tel._e2u. That ain't going to fly. In order to make the transition, current ENUM users need to provision their existing NAPTRs into the registry. That's going to be a headache for everybody who managed to get a 3761-based system up and running. ----------------------------- The showstopper: And then there is the issue of open numbering plans. I can't see how this scheme is supposed to work in a country where PBX operators are free to define their own variable-length dialplan behind their pilot number. Consider the example of enum.at's Vienna office: Our pilot number is +43 1 5056416. That's a normal (i.e. not shortened) V= ienna number. We use 2-digit extension, e.g. -33 is my phone. A common scheme is to use prefixes for FAX to Email services. In our case -933 is supposed to deliver an incoming FAX to my mailbox. Our carrier (Telekom Austria) doesn't know or even care about these arrangements. In ENUM terms, right now we have a delegation for 6.1.4.5.0.5.1.3.4.e164.arpa and simply add new extensions to our zone file and be done with it. In I-ENUM, Telekom Austria (were they to take part in our trial) would use wildcards to direct calls to their ingress point, e.g. by 6.1.4.5.0.5.1.3.4.e164.arpa NAPTR ... "!(.*)!\\1@sip.telekom.at! *.6.1.4.5.0.5.1.3.4.e164.arpa NAPTR ... "!(.*)!\\1@sip.telekom.at! Which records should Telekom Austria provision under your scheme? /ol --=20 < Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUF-0004G7-A2; Fri, 06 Oct 2006 10:15:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVR2O-0003G8-0v for enum@ietf.org; Thu, 05 Oct 2006 07:05:12 -0400 Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVR2J-00008g-OA for enum@ietf.org; Thu, 05 Oct 2006 07:05:12 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id D887C1A36D; Thu, 5 Oct 2006 13:04:57 +0200 (CEST) Date: Thu, 5 Oct 2006 13:04:57 +0200 From: Otmar Lendl To: enum@ietf.org Message-ID: <20061005110457.GB12719@nic.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Enum] Infrastructure ENUM implementations X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org FYI, we've implemented now the interim solution for I-ENUM (branching off the default tree) within both OpenSer and Asterisk. You are invited to have a look and to testdrive the code. OpenSer: http://www.enum.at/index.php?id=338&L=9 Asterisk: http://bugs.digium.com/view.php?id=8089 Share and Enjoy! /ol -- < Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUF-0004GC-JM; Fri, 06 Oct 2006 10:15:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVTcT-000620-R0 for enum@ietf.org; Thu, 05 Oct 2006 09:50:37 -0400 Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVTcS-0003pu-2M for enum@ietf.org; Thu, 05 Oct 2006 09:50:37 -0400 Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id k95DoZKN011452 for ; Thu, 5 Oct 2006 06:50:35 -0700 Received: from OVE1WNEXCB02.vcorp.ad.vrsn.com ([10.60.13.34]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Oct 2006 06:49:14 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: FW: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Date: Thu, 5 Oct 2006 08:49:14 -0500 Message-ID: <122A5731B827474C99ED552C6BFE23ED3FA6C7@OVE1WNEXCB02.vcorp.ad.vrsn.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Thread-Index: AcbidRrsdNW+DQs8QJaqMDsmeXxplwFbwK2QACg4sqA= From: "McCandless, Kevin" To: X-OriginalArrivalTime: 05 Oct 2006 13:49:14.0222 (UTC) FILETIME=[0B29C8E0:01C6E885] X-Spam-Score: 0.6 (/) X-Scan-Signature: 8353da2fde044920180672209f5bf8a0 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1526681551==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============1526681551== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6E885.0AE10643" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6E885.0AE10643 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Richard: =20 Section 8 has some wording that should be taken out or redone. Caching = for CNAM queries is a big concern among telecom providers. It might = help to removing the caching words as shown below. =20 Old text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their internal cached ENUM=20 databases, which is only able to be queried by trusted elements of=20 their network, such as soft switches and SIP proxy servers. =20 New Text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their databases, which is only=20 able to be queried by trusted elements of their network, such as=20 soft switches and SIP proxy servers. =20 Thoughts? =20 -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: Wednesday, September 27, 2006 3:40 PM To: iesg-secretary@ietf.org; enum@ietf.org Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, Jon' Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt =20 =20 =20 Title : IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA=20 Registration for Media type 'application/cnam' Author(s) : R. Shockey, et al. Filename : draft-ietf-enum-cnam-04.txt Pages : 13 Date : 2006-9-27 =20 This document registers the Enumservice 'pstn' and subtype 'cnam'=20 using the URI scheme 'data:' as per the IANA registration process = defined in the ENUM specification, RFC 3761 and registers a new media=20 type application/cnam. =20 =20 This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client = User Agents (CUA). =20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt =20 =20 This is a request for publication for one IETF ENUM WG working group document. =20 A one month WG last call on this document concluded on September = 25,2006. =20 The document listed below is being proposed for Proposed Standard. =20 This document incorporates numerous comments from the last call. =20 Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org=20 sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651=20 PSTN Mobile: +1 703.593.2683 =20 =20 =20 =20 =20 =20 =20 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum =20 ------_=_NextPart_001_01C6E885.0AE10643 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Richard:

 

Section 8 has some wording that should be taken out or redone.  Caching for CNAM queries is a big concern among telecom = providers.  It might help to removing the caching words as shown = below.

 

Old text:

  Carriers, service providers, or other organizations that originate

  Calling Name data may choose not to publish such = information in a

  globally visible DNS tree for reasons of personal privacy protection.

  Service providers and other organizations may choose to privately

  exchange and publish this data in their internal cached = ENUM

  databases, which is only able to be queried by trusted = elements of

their network, such as soft switches and SIP = proxy servers.

 

New Text:

  Carriers, service providers, or other =
organizations that originate 
  Calling Name data may choose not =
to publish such information in a =

  globally visible DNS tree for =
reasons of personal privacy protection. =

  Service providers and other =
organizations may choose to privately =

exchange and publish this data in their =
databases, which is only 
able to be queried by trusted elements of =
their network, such as 
soft switches and SIP proxy =
servers.

 

Thoughts?

 

-----Original Message-----
From: Richard Shockey [mailto:richard@shockey.us]
Sent: Wednesday, September 27, 2006 3:40 PM
To: iesg-secretary@ietf.org; enum@ietf.org
Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, = Jon'
Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt

 

 

 

Title       : IANA Registration = for an Enumservice Calling

           = ;            =    Name Delivery (CNAM) Information and IANA

           = ;            =    Registration for Media type = 'application/cnam'

      Author(s)   : R. = Shockey, et al.

      Filename    : draft-ietf-enum-cnam-04.txt

      Pages       : = 13

      Date        : = 2006-9-27

   &From enum-bounces@ietf.org Fri Oct 06 10:17:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUF-0004G7-A2; Fri, 06 Oct 2006 10:15:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVR2O-0003G8-0v for enum@ietf.org; Thu, 05 Oct 2006 07:05:12 -0400 Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVR2J-00008g-OA for enum@ietf.org; Thu, 05 Oct 2006 07:05:12 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id D887C1A36D; Thu, 5 Oct 2006 13:04:57 +0200 (CEST) Date: Thu, 5 Oct 2006 13:04:57 +0200 From: Otmar Lendl To: enum@ietf.org Message-ID: <20061005110457.GB12719@nic.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Enum] Infrastructure ENUM implementations X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org FYI, we've implemented now the interim solution for I-ENUM (branching off the default tree) within both OpenSer and Asterisk. You are invited to have a look and to testdrive the code. OpenSer: http://www.enum.at/index.php?id=338&L=9 Asterisk: http://bugs.digium.com/view.php?id=8089 Share and Enjoy! /ol -- < Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUF-0004GC-JM; Fri, 06 Oct 2006 10:15:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVTcT-000620-R0 for enum@ietf.org; Thu, 05 Oct 2006 09:50:37 -0400 Received: from colibri.verisign.com ([65.205.251.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVTcS-0003pu-2M for enum@ietf.org; Thu, 05 Oct 2006 09:50:37 -0400 Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id k95DoZKN011452 for ; Thu, 5 Oct 2006 06:50:35 -0700 Received: from OVE1WNEXCB02.vcorp.ad.vrsn.com ([10.60.13.34]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Oct 2006 06:49:14 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: FW: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Date: Thu, 5 Oct 2006 08:49:14 -0500 Message-ID: <122A5731B827474C99ED552C6BFE23ED3FA6C7@OVE1WNEXCB02.vcorp.ad.vrsn.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Thread-Index: AcbidRrsdNW+DQs8QJaqMDsmeXxplwFbwK2QACg4sqA= From: "McCandless, Kevin" To: X-OriginalArrivalTime: 05 Oct 2006 13:49:14.0222 (UTC) FILETIME=[0B29C8E0:01C6E885] X-Spam-Score: 0.6 (/) X-Scan-Signature: 8353da2fde044920180672209f5bf8a0 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: ,

This document registers the Enumservice 'pstn' and subtype = 'cnam'

using the URI scheme 'data:' as per the IANA registration = process defined in

the ENUM specification, RFC 3761 and registers a new media =

type application/cnam.  

  

This data is used to facilitate the transfer of Calling Name = Delivery

(CNAM) data for calls that originate on the Public Switched = Telephone

Network (PSTN) that may be displayed on VoIP or other Real-time = Client User

Agents (CUA).

 

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt

 

 

This is a request for publication for one IETF ENUM WG working = group

document.

 

A one month WG last call on this document concluded on September 25,2006.

 

The document listed below is being proposed for Proposed = Standard.

 

This document incorporates numerous comments from the last = call.

 

Richard Shockey

Content-Type: multipart/mixed; boundary="===============1526681551==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============1526681551== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6E885.0AE10643" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6E885.0AE10643 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Richard: =20 Section 8 has some wording that should be taken out or redone. Caching = for CNAM queries is a big concern among telecom providers. It might = help to removing the caching words as shown below. =20 Old text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their internal cached ENUM=20 databases, which is only able to be queried by trusted elements of=20 their network, such as soft switches and SIP proxy servers. =20 New Text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their databases, which is only=20 able to be queried by trusted elements of their network, such as=20 soft switches and SIP proxy servers. =20 Thoughts? =20 -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: Wednesday, September 27, 2006 3:40 PM To: iesg-secretary@ietf.org; enum@ietf.org Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, Jon' Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt =20 =20 =20 Title : IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA=20 Registration for Media type 'application/cnam' Author(s) : R. Shockey, et al. Filename : draft-ietf-enum-cnam-04.txt Pages : 13 Date : 2006-9-27 =20 This document registers the Enumservice 'pstn' and subtype 'cnam'=20 using the URI scheme 'data:' as per the IANA registration process = defined in the ENUM specification, RFC 3761 and registers a new media=20 type application/cnam. =20 =20 This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client = User Agents (CUA). =20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt =20 =20 This is a request for publication for one IETF ENUM WG working group document. =20 A one month WG last call on this document concluded on September = 25,2006. =20 The document listed below is being proposed for Proposed Standard. =20 This document incorporates numerous comments from the last call. =20 Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org=20 sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651=20 PSTN Mobile: +1 703.593.2683 =20 =20 =20 =20 =20 =20 =20 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum =20 ------_=_NextPart_001_01C6E885.0AE10643 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Director, Member of the Technical = Staff

NeuStar

46000 Center Oak Plaza - Sterling, VA = 20166

sip:rshockey(at)iptel.org

sip:5651(at)neustarlab.biz

PSTN Office +1 571.434.5651

PSTN Mobile: +1 703.593.2683

<mailto:richard(at)shockey.us> =

<mailto:richard.shockey(at)neustar.biz>

 

 

 

 

 

 

_______________________________________________=

enum mailing list

enum@ietf.org

https://www1.ietf.org/mailman/listinfo/enum

 

------_=_NextPart_001_01C6E885.0AE10643-- --===============1526681551== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============1526681551==-- EC-html40">

Richard:

 

Section 8 has some wording that should be taken out or redone.  Caching for CNAM queries is a big concern among telecom = providers.  It might help to removing the caching words as shown = below.

 

Old text:

  Carriers, service providers, or other organizations that originate

  Calling Name data may choose not to publish such = information in a

  globally visible DNS tree for reasons of personal privacy protection.

  Service providers and other organizations may choose to privately

  exchange and publish this data in their internal cached = ENUM

  databases, which is only able to be queried by trusted = elements of

their network, such as soft switches and SIP = proxy servers.

 

New Text:

  Carriers, service providers, or other =
organizations that originate 
  Calling Name data may choose not =
to publish such information in a =

  globally visible DNS tree for =
reasons of personal privacy protection. =

  Service providers and other =
organizations may choose to privately =

exchange and publish this data in their =
databases, which is only 
able to be queried by trusted elements of =
their network, such as 
soft switches and SIP proxy =
servers.

 

Thoughts?

 

-----Original Message-----
From: Richard Shockey [mailto:richard@shockey.us]
Sent: Wednesday, September 27, 2006 3:40 PM
To: iesg-secretary@ietf.org; enum@ietf.org
Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, = Jon'
Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt

 

 

 

Title       : IANA Registration = for an Enumservice Calling

           = ;            =    Name Delivery (CNAM) Information and IANA

           = ;            =    Registration for Media type = 'application/cnam'

      Author(s)   : R. = Shockey, et al.

      Filename    : draft-ietf-enum-cnam-04.txt

      Pages       : = 13

      Date        : = 2006-9-27

     

This document registers the Enumservice 'pstn' and subtype = 'cnam'

using the URI scheme 'data:' as per the IANA registration = process defined in

the ENUM specification, RFC 3761 and registers a new media =

type application/cnam.  

  

This data is used to facilitate the transfer of Calling Name = Delivery

(CNAM) data for calls that originate on the Public Switched = Telephone

Network (PSTN) that may be displayed on VoIP or other Real-time = Client User

Agents (CUA).

 

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt

 

 

This is a request for publication for one IETF ENUM WG working = group

document.

 

A one month WG last call on this document concluded on September 25,2006.

 

The document listed below is being proposed for Proposed = Standard.

 

This document incorporates numerous comments from the last = call.

 

Richard Shockey

Director, Member of the Technical = Staff

NeuStar

46000 Center Oak Plaza - Sterling, VA = 20166

sip:rshockey(at)iptel.org

sip:5651(at)neustarlab.biz

PSTN Office +1 571.434.5651

PSTN Mobile: +1 703.593.2683

<mailto:richard(at)shockey.us> =

<mailto:richard.shockey(at)neustar.biz>

 

 

 

 

 

 

_______________________________________________=

enum mailing list

enum@ietf.org

https://www1.ietf.org/mailman/listinfo/enum

 

------_=_NextPart_001_01C6E885.0AE10643-- --===============1526681551== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============1526681551==-- From enum-bounces@ietf.org Fri Oct 06 10:17:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUE-0004Fx-A8; Fri, 06 Oct 2006 10:15:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUpJo-0002vz-G1 for enum@ietf.org; Tue, 03 Oct 2006 14:48:40 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUpJm-0004lJ-UU for enum@ietf.org; Tue, 03 Oct 2006 14:48:40 -0400 Received: from [192.168.1.206] (85-124-83-222.dynamic.xdsl-line.inode.at [::ffff:85.124.83.222]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Tue, 03 Oct 2006 20:48:32 +0200 id 0007C0ED.4522B080.00002C55 Message-ID: <4522B00F.6090309@enum.at> Date: Tue, 03 Oct 2006 20:46:39 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: enum@ietf.org Content-Type: multipart/mixed; boundary="------------040801050309080702020709" X-Spam-Score: 0.1 (/) X-Scan-Signature: 25eb6223a37c19d53ede858176b14339 Subject: [Enum] [Fwd: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --------------040801050309080702020709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit fyi. Alex --------------040801050309080702020709 Content-Type: message/rfc822; name="I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt" Received: from megatron.ietf.org (www1.ietf.org [::ffff:156.154.16.145]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Mon, 02 Oct 2006 16:55:37 +0200 id 0007C0E2.4521286A.000007B2 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP8C-0004fJ-LL; Mon, 02 Oct 2006 10:50:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP7t-0003yL-CF for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUP7t-0002ur-9y for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GUP7o-0005Db-8f for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id EF1EF175BA for ; Mon, 2 Oct 2006 14:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GUP7J-0005xL-IF for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:01 -0400 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_pahula-1970-1159800938-0001-2" To: i-d-announce@ietf.org Cc: From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 02 Oct 2006 10:50:01 -0400 X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Subject: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: i-d-announce-bounces@ietf.org X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on pahula X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,NO_REAL_NAME autolearn=no version=3.0.3 This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_pahula-1970-1159800938-0001-2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-xmpp-00.txt Pages : 7 Date : 2006-10-2 This document requests IANA registration of an Enumservice for Extensible Messaging and Presence Protocol (XMPP) Uniform Resource Identifiers (URIs) according to the registration procedure outlined in RFC 3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-mayrhofer-enum-xmpp-00.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@ietf.org. In the body type: "FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.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. --=_pahula-1970-1159800938-0001-2 Content-Type: multipart/alternative; boundary="=_pahula-1970-1159800938-0001-3" This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_pahula-1970-1159800938-0001-3 Content-Type: message/external-body; access-type=mail-server; server="mailserv@ietf.org" Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.txt --=_pahula-1970-1159800938-0001-3 Content-Type: message/external-body; name="draft-mayrhofer-enum-xmpp-00.txt"; site="ftp.ietf.org"; access-type=anon-ftp; directory=internet-drafts Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> --=_pahula-1970-1159800938-0001-3-- --=_pahula-1970-1159800938-0001-2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --=_pahula-1970-1159800938-0001-2-- --------------040801050309080702020709 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --------------040801050309080702020709-- From enum-bounces@ietf.org Fri Oct 06 10:17:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUG-0004HF-CU; Fri, 06 Oct 2006 10:15:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVnOK-0000cS-6r for enum@ietf.org; Fri, 06 Oct 2006 06:57:20 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVnOI-0001zg-N3 for enum@ietf.org; Fri, 06 Oct 2006 06:57:20 -0400 Received: from [10.10.0.64] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Fri, 06 Oct 2006 12:57:12 +0200 id 0007C1EF.45263688.00000BBB Message-ID: <45263613.6030909@enum.at> Date: Fri, 06 Oct 2006 12:55:15 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "'enum@ietf.org'" , Stastny Richard , Michael Haberler Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Cc: Subject: [Enum] Review of draft-ietf-enum-combined X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi, i've reviewed draft-ietf-enum-combined for NITS (and more) - here are my comments to the current version: - idnits checker: The automatic check found no NITS - good - The draft refers to RFC2119 in the terminology section - however, subsequent text does not contain any such references. Please do either actually use those normative key words, or remove the paragraph (plus the related reference) from the document. - Terminology: please expand "WG" to "working group" - 2. Introduction: please expand "NS" (first para) and "URI" (third para). I'd put "DDDS" (last para) in parentheses. - The introduction section talks about a "proper" solution, while the subsequent section "Interim solution" mentions a "right" solution. I'd prefer unified terminology. - 4. Introducing a branch into the e164.arpa tree: There is a typo in the headline ("164.arpa") The first paragraph seems not to reflect what is needed, but rather already presents a solution (which is repeated in the last para of the smae section), and might be a bit confusing without background knowledge. I'll think about some text - please stay tuned. Please expand NRA, NPA, ITU - Section 5.: The first bullet on page 5 is not completely clear to me. It's unclear what the "proper" means, and how "at the country code level" and "into a subdomain in the country code zone" interact. probably something like "at a defined label directly below the domain name corresponding to a country code" or something similar is clearer. The "insertion position" leaves out such trivial things like: - Do we start counting the "insertion position" at 0 or 1? (i assume, it is the number of digits to be skipped, so the "position" of 1 would indicate to put the label between the first and second digit. - From which side of a number do we count? I assume it's "top down" (so, from left to right in an E.164 number), but that's not entirely clear. Apex: - can that be an empty string? Since it's about "replacement", an empty string could make sense the last bullet leaves it open whether those operations are applied to the output of RFC3761 (which would actually lead to a fqdn ending in e164.arpa.e164.arpa), or which steps are to be followed/skipped. Since this is actually ome of the most important parts of this draft (because it updates RFC3761 in respect of the transformation of E.164 to FQDN), i'd appreciate to have this flesed out like section 2.4 of RFC3761 - it must be completely clear how the FQDN is being constructed. eg. That bullet also says the apex from the EBL is to be "appended", while the "apex" bullet above says that it should be "replaced". Perhaps making a dedicated subsection of the "transformation" logic would be good, because it could then be referenced from section 7. - Section 6. I'm missing "Figure 1" - the draft just contains the bullet list of country codes types. - Section 7 1st bullet: The number might not be the "called" number - eg. for CNAM, it might be the originating number for which a lookup is performed. I suggest to change that into "The E.164 number in fully qualified (international) format". 2nd bullet: typo - "wether". resolver behaviour: the second bullet indicates that some "cache table" is being used. I'm missing how this correlates to the DNS based caching of the resolver itself. The third star bullet roughly describes the "iteration" algorithm to find an EBL - maybe that behaviour should be fleshed out in section 6, and just referenced from here. "iterate over the number up to five digits" could be interpreted in a few ways. 4th star: "inserting a label" into a fqdn automatically adds a dot, because a fqdn by definition consists of labels which are seperated by dots. The last sentence mentions "EBL values" as well as "EBL parameters". I suggeset to change that into "It is assumed that parameters already discovered from EBL records for a certain country coded are stored in a cache table" - 8. Security considerations I'd change the 5th para by putting a full stop after "... the identity of the end-user.", and change the subsequent sentence into ".... recommended to use either anonymized UserIDs or the E.164 number itself in the user-part of the SIP URI, such as..." (BTW: "SIP" needs to be expanded/referenced here). - 9. IANA considerations It's unclear to me whether the label where the EBL resides ("infrastructure") is of concern to IANA. It definitely is when more applications are being deployed. cheers Alex _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUE-0004Fx-A8; Fri, 06 Oct 2006 10:15:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUpJo-0002vz-G1 for enum@ietf.org; Tue, 03 Oct 2006 14:48:40 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUpJm-0004lJ-UU for enum@ietf.org; Tue, 03 Oct 2006 14:48:40 -0400 Received: from [192.168.1.206] (85-124-83-222.dynamic.xdsl-line.inode.at [::ffff:85.124.83.222]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Tue, 03 Oct 2006 20:48:32 +0200 id 0007C0ED.4522B080.00002C55 Message-ID: <4522B00F.6090309@enum.at> Date: Tue, 03 Oct 2006 20:46:39 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: enum@ietf.org Content-Type: multipart/mixed; boundary="------------040801050309080702020709" X-Spam-Score: 0.1 (/) X-Scan-Signature: 25eb6223a37c19d53ede858176b14339 Subject: [Enum] [Fwd: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --------------040801050309080702020709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit fyi. Alex --------------040801050309080702020709 Content-Type: message/rfc822; name="I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt" Received: from megatron.ietf.org (www1.ietf.org [::ffff:156.154.16.145]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Mon, 02 Oct 2006 16:55:37 +0200 id 0007C0E2.4521286A.000007B2 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP8C-0004fJ-LL; Mon, 02 Oct 2006 10:50:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUP7t-0003yL-CF for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUP7t-0002ur-9y for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GUP7o-0005Db-8f for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id EF1EF175BA for ; Mon, 2 Oct 2006 14:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GUP7J-0005xL-IF for i-d-announce@ietf.org; Mon, 02 Oct 2006 10:50:01 -0400 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_pahula-1970-1159800938-0001-2" To: i-d-announce@ietf.org Cc: From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 02 Oct 2006 10:50:01 -0400 X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Subject: I-D ACTION:draft-mayrhofer-enum-xmpp-00.txt X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: internet-drafts@ietf.org List-Id: i-d-announce.ietf.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: i-d-announce-bounces@ietf.org X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on pahula X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,NO_REAL_NAME autolearn=no version=3.0.3 This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_pahula-1970-1159800938-0001-2 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-xmpp-00.txt Pages : 7 Date : 2006-10-2 This document requests IANA registration of an Enumservice for Extensible Messaging and Presence Protocol (XMPP) Uniform Resource Identifiers (URIs) according to the registration procedure outlined in RFC 3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-mayrhofer-enum-xmpp-00.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@ietf.org. In the body type: "FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.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. --=_pahula-1970-1159800938-0001-2 Content-Type: multipart/alternative; boundary="=_pahula-1970-1159800938-0001-3" This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_pahula-1970-1159800938-0001-3 Content-Type: message/external-body; access-type=mail-server; server="mailserv@ietf.org" Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-mayrhofer-enum-xmpp-00.txt --=_pahula-1970-1159800938-0001-3 Content-Type: message/external-body; name="draft-mayrhofer-enum-xmpp-00.txt"; site="ftp.ietf.org"; access-type=anon-ftp; directory=internet-drafts Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2006-10-2083207.I-D@ietf.org> --=_pahula-1970-1159800938-0001-3-- --=_pahula-1970-1159800938-0001-2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --=_pahula-1970-1159800938-0001-2-- --------------040801050309080702020709 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --------------040801050309080702020709-- From enum-bounces@ietf.org Fri Oct 06 10:17:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUG-0004HF-CU; Fri, 06 Oct 2006 10:15:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVnOK-0000cS-6r for enum@ietf.org; Fri, 06 Oct 2006 06:57:20 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVnOI-0001zg-N3 for enum@ietf.org; Fri, 06 Oct 2006 06:57:20 -0400 Received: from [10.10.0.64] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Fri, 06 Oct 2006 12:57:12 +0200 id 0007C1EF.45263688.00000BBB Message-ID: <45263613.6030909@enum.at> Date: Fri, 06 Oct 2006 12:55:15 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "'enum@ietf.org'" , Stastny Richard , Michael Haberler Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Cc: Subject: [Enum] Review of draft-ietf-enum-combined X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi, i've reviewed draft-ietf-enum-combined for NITS (and more) - here are my comments to the current version: - idnits checker: The automatic check found no NITS - good - The draft refers to RFC2119 in the terminology section - however, subsequent text does not contain any such references. Please do either actually use those normative key words, or remove the paragraph (plus the related reference) from the document. - Terminology: please expand "WG" to "working group" - 2. Introduction: please expand "NS" (first para) and "URI" (third para). I'd put "DDDS" (last para) in parentheses. - The introduction section talks about a "proper" solution, while the subsequent section "Interim solution" mentions a "right" solution. I'd prefer unified terminology. - 4. Introducing a branch into the e164.arpa tree: There is a typo in the headline ("164.arpa") The first paragraph seems not to reflect what is needed, but rather already presents a solution (which is repeated in the last para of the smae section), and might be a bit confusing without background knowledge. I'll think about some text - please stay tuned. Please expand NRA, NPA, ITU - Section 5.: The first bullet on page 5 is not completely clear to me. It's unclear what the "proper" means, and how "at the country code level" and "into a subdomain in the country code zone" interact. probably something like "at a defined label directly below the domain name corresponding to a country code" or something similar is clearer. The "insertion position" leaves out such trivial things like: - Do we start counting the "insertion position" at 0 or 1? (i assume, it is the number of digits to be skipped, so the "position" of 1 would indicate to put the label between the first and second digit. - From which side of a number do we count? I assume it's "top down" (so, from left to right in an E.164 number), but that's not entirely clear. Apex: - can that be an empty string? Since it's about "replacement", an empty string could make sense the last bullet leaves it open whether those operations are applied to the output of RFC3761 (which would actually lead to a fqdn ending in e164.arpa.e164.arpa), or which steps are to be followed/skipped. Since this is actually ome of the most important parts of this draft (because it updates RFC3761 in respect of the transformation of E.164 to FQDN), i'd appreciate to have this flesed out like section 2.4 of RFC3761 - it must be completely clear how the FQDN is being constructed. eg. That bullet also says the apex from the EBL is to be "appended", while the "apex" bullet above says that it should be "replaced". Perhaps making a dedicated subsection of the "transformation" logic would be good, because it could then be referenced from section 7. - Section 6. I'm missing "Figure 1" - the draft just contains the bullet list of country codes types. - Section 7 1st bullet: The number might not be the "called" number - eg. for CNAM, it might be the originating number for which a lookup is performed. I suggest to change that into "The E.164 number in fully qualified (international) format". 2nd bullet: typo - "wether". resolver behaviour: the second bullet indicates that some "cache table" is being used. I'm missing how this correlates to the DNS based caching of the resolver itself. The third star bullet roughly describes the "iteration" algorithm to find an EBL - maybe that behaviour should be fleshed out in section 6, and just referenced from here. "iterate over the number up to five digits" could be interpreted in a few ways. 4th star: "inserting a label" into a fqdn automatically adds a dot, because a fqdn by definition consists of labels which are seperated by dots. The last sentence mentions "EBL values" as well as "EBL parameters". I suggeset to change that into "It is assumed that parameters already discovered from EBL records for a certain country coded are stored in a cache table" - 8. Security considerations I'd change the 5th para by putting a full stop after "... the identity of the end-user.", and change the subsequent sentence into ".... recommended to use either anonymized UserIDs or the E.164 number itself in the user-part of the SIP URI, such as..." (BTW: "SIP" needs to be expanded/referenced here). - 9. IANA considerations It's unclear to me whether the label where the EBL resides ("infrastructure") is of concern to IANA. It definitely is when more applications are being deployed. cheers Alex _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 06 10:17:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVqUE-0004G2-Rc; Fri, 06 Oct 2006 10:15:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVBwv-0001hX-HG for enum@ietf.org; Wed, 04 Oct 2006 14:58:33 -0400 Received: from robin.verisign.com ([65.205.251.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVBhr-0006PE-4z for enum@ietf.org; Wed, 04 Oct 2006 14:43:00 -0400 Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id k94IgviK015182; Wed, 4 Oct 2006 11:42:58 -0700 Received: from OVE1WNEXCB02.vcorp.ad.vrsn.com ([10.60.13.34]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Oct 2006 11:41:37 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Date: Wed, 4 Oct 2006 13:41:42 -0500 Message-ID: <122A5731B827474C99ED552C6BFE23ED3FA691@OVE1WNEXCB02.vcorp.ad.vrsn.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] ENUM WG Request for Publication - draft-ietf-enum-cnam-04.txt Thread-Index: AcbidRrsdNW+DQs8QJaqMDsmeXxplwFbwK2Q From: "McCandless, Kevin" To: , X-OriginalArrivalTime: 04 Oct 2006 18:41:37.0798 (UTC) FILETIME=[B9894A60:01C6E7E4] X-Spam-Score: 0.6 (/) X-Scan-Signature: 6ce9c9805f9fd7f2a8e6eb8268c6b0fc Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0442096962==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============0442096962== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6E7E4.B90579DA" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6E7E4.B90579DA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Richard: =20 Section 8 has some wording that should be taken out or redone. Caching = for CNAM queries is a big concern among telecom providers. It might = help to removing the caching words as shown below. =20 Old text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their internal cached ENUM=20 databases, which is only able to be queried by trusted elements of=20 their network, such as soft switches and SIP proxy servers. =20 New Text: Carriers, service providers, or other organizations that originate=20 Calling Name data may choose not to publish such information in a=20 globally visible DNS tree for reasons of personal privacy protection.=20 Service providers and other organizations may choose to privately=20 exchange and publish this data in their databases, which is only=20 able to be queried by trusted elements of their network, such as=20 soft switches and SIP proxy servers. =20 Thoughts? =20 -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: Wednesday, September 27, 2006 3:40 PM To: iesg-secretary@ietf.org; enum@ietf.org Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, Jon' Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt =20 =20 =20 Title : IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA=20 Registration for Media type 'application/cnam' Author(s) : R. Shockey, et al. Filename : draft-ietf-enum-cnam-04.txt Pages : 13 Date : 2006-9-27 =20 This document registers the Enumservice 'pstn' and subtype 'cnam'=20 using the URI scheme 'data:' as per the IANA registration process = defined in the ENUM specification, RFC 3761 and registers a new media=20 type application/cnam. =20 =20 This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client = User Agents (CUA). =20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt =20 =20 This is a request for publication for one IETF ENUM WG working group document. =20 A one month WG last call on this document concluded on September = 25,2006. =20 The document listed below is being proposed for Proposed Standard. =20 This document incorporates numerous comments from the last call. =20 Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org=20 sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651=20 PSTN Mobile: +1 703.593.2683 =20 =20 =20 =20 =20 =20 =20 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum =20 ------_=_NextPart_001_01C6E7E4.B90579DA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Richard:

 

Section 8 has some wording that should be taken out or redone. = =A0Caching for CNAM queries is a big concern among telecom providers.=A0 It might = help to removing the caching words as shown below.

 

Old text:

=A0 Carriers, service providers, or other organizations that = originate

=A0 Calling Name data may choose not to publish such information = in a

=A0 globally visible DNS tree for reasons of personal privacy = protection.

=A0 Service providers and other organizations may choose to = privately

=A0 exchange and publish this data in their internal cached ENUM =

=A0 databases, which is only able to be queried by trusted = elements of

their network, such as soft switches and SIP = proxy servers.

 

New Text:

=A0 Carriers, service providers, or other =
organizations that originate 
=A0=A0Calling Name data may choose not to =
publish such information in a 
=A0=A0globally visible DNS tree for reasons =
of personal privacy protection. =

=A0=A0Service providers and other =
organizations may choose to privately =

exchange and publish this data in their =
databases, which is only 
able to be queried by trusted elements of =
their network, such as 
soft switches and SIP proxy =
servers.

 

Thoughts?

 

-----Original Message-----
From: Richard Shockey [mailto:richard@shockey.us]
Sent: Wednesday, September 27, 2006 3:40 PM
To: iesg-secretary@ietf.org; enum@ietf.org
Cc: 'Cullen Jennings'; '"Patrik F=E4ltstr=F6m"'; 'Peterson, = Jon'
Subject: [Enum] ENUM WG Request for Publication - = draft-ietf-enum-cnam-04.txt

 

 

 

Title=A0=A0=A0=A0=A0=A0 : IANA Registration for an Enumservice = Calling

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 Name Delivery (CNAM) Information and IANA =

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0 Registration for Media type 'application/cnam'

=A0=A0=A0=A0=A0 Author(s)=A0=A0 : R. Shockey, et = al.

=A0=A0=A0=A0=A0 Filename=A0=A0=A0 : = draft-ietf-enum-cnam-04.txt

=A0=A0=A0=A0=A0 Pages=A0=A0=A0=A0=A0=A0 : = 13

=A0=A0=A0=A0=A0 Date=A0=A0=A0=A0=A0=A0=A0 : = 2006-9-27

=A0=A0=A0=A0=A0

This document registers the Enumservice 'pstn' and subtype = 'cnam'

using the URI scheme 'data:' as per the IANA registration = process defined in

the ENUM specification, RFC 3761 and registers a new media =

type application/cnam.=A0=A0

=A0=A0

This data is used to facilitate the transfer of Calling Name = Delivery

(CNAM) data for calls that originate on the Public Switched = Telephone

Network (PSTN) that may be displayed on VoIP or other Real-time = Client User

Agents (CUA).

 

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-04.txt

 

 

This is a request for publication for one IETF ENUM WG working = group

document.

 

A one month WG last call on this document concluded on September = 25,2006.

 

The document listed below is being proposed for Proposed = Standard.

 

This document incorporates numerous comments from the last = call.

 

Richard Shockey

Director, Member of the Technical = Staff

NeuStar

46000 Center Oak Plaza - Sterling, VA = 20166

sip:rshockey(at)iptel.org

sip:5651(at)neustarlab.biz

PSTN Office +1 571.434.5651

PSTN Mobile: +1 703.593.2683

<mailto:richard(at)shockey.us> =

<mailto:richard.shockey(at)neustar.biz>

 

 

 

 

 

 

_______________________________________________=

enum mailing list

enum@ietf.org

https://www1.ietf.org/mailman/listinfo/enum

 

------_=_NextPart_001_01C6E7E4.B90579DA-- --===============0442096962== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============0442096962==-- From enum-bounces@ietf.org Sun Oct 08 15:16:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWe5Q-0000PY-Aa; Sun, 08 Oct 2006 15:13:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWe5O-0000Oz-7Q for enum@ietf.org; Sun, 08 Oct 2006 15:13:18 -0400 Received: from nf-out-0910.google.com ([64.233.182.188]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GWe5J-0003rn-SL for enum@ietf.org; Sun, 08 Oct 2006 15:13:18 -0400 Received: by nf-out-0910.google.com with SMTP id l23so1783989nfc for ; Sun, 08 Oct 2006 12:13:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N5l+LWtkCG4QkaQ8AYE8cuiUCR1sRNz31PfyyivYYXbmVgLWz4k4nI2bgsIfqTmEG6T2VyUtrGQJBr0Zd5V+aMVRf+yagb+cHl3PH00OKC1rXkHK3oJFWsYMwxL1yrBWjNZkboS/I831TJqhh04bCJjtu/n7ls4xYiB1v2YgYPI= Received: by 10.78.183.15 with SMTP id g15mr4398087huf; Sun, 08 Oct 2006 12:13:12 -0700 (PDT) Received: by 10.78.140.5 with HTTP; Sun, 8 Oct 2006 12:13:12 -0700 (PDT) Message-ID: Date: Sun, 8 Oct 2006 20:13:12 +0100 From: "Lee Dryburgh" To: enum@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [Enum] GrandCentral X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I sent the email below to the list but due to list problems it never was posted. I was just going to leave it, but I am soon preparing a slide pack on telco services which never lived up to promises (ISDN, WAP, MMS, IN, ATM, 3G). I am considering adding in User ENUM. For this reason, I've dug the mail out and wonder if anybody really sees User ENUM taking off particularly in light of such services? --> ---------- Forwarded message ---------- From: Lee Dryburgh Date: 28-Sep-2006 19:04 Subject: GrandCentral To: "enum@ietf.org" I thought the members of this list would be interested in the following which recently launched: http://www.grandcentral.com/ The blogosphere has been very positive about it. In short from http://www.lifehacker.com/software/telephone/one-phone-number-to-rule-them-all-203629.php "GrandCentral is a brilliant new web app that lets you consolidate all of your phone numbers into one number, meaning someone can call you on your GrandCentral phone number and all of your phones (cell phone, work phone, home phone) will ring. And then it gets interesting." Regards Lee _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Oct 08 16:41:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWfQn-0002Q6-Ij; Sun, 08 Oct 2006 16:39:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GWfQm-0002Pw-Er for enum@ietf.org; Sun, 08 Oct 2006 16:39:28 -0400 Received: from smtpout11-02.prod.mesa1.secureserver.net ([68.178.232.2]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GWfQk-00010F-V4 for enum@ietf.org; Sun, 08 Oct 2006 16:39:28 -0400 Received: (qmail 3620 invoked from network); 8 Oct 2006 20:39:19 -0000 Received: from unknown (HELO gem-wbe03.mesa1.secureserver.net) (64.202.189.35) by smtpout11-02.prod.mesa1.secureserver.net with SMTP; 8 Oct 2006 20:39:19 -0000 Received: (qmail 9555 invoked by uid 99); 8 Oct 2006 20:39:19 -0000 Date: Sun, 08 Oct 2006 13:39:19 -0700 From: Tim Ruiz Subject: RE: [Enum] GrandCentral To: Lee Dryburgh Message-ID: <20061008133919.4a871ae7d05d2c98d9abb595d392cd69.3bb58daa50.wbe@email.secureserver.net> MIME-Version: 1.0 User-Agent: Web-Based Email 4.8.5 X-Originating-IP: 12.215.195.100 X-Spam-Score: 1.6 (+) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tim Ruiz List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1378721044==" Errors-To: enum-bounces@ietf.org --===============1378721044== Content-Type: TEXT/html; CHARSET=US-ASCII
Lee, I can only give my humble opinion from a US perspective. I think it will be some time before user ENUM sees signficant adoption in the US. The primary reason is that it requires ENUM aware devices in the hands of callers to really work. The US is usually slower to adopt new technologies like this, compared to Europe for example.
 

Tim


-------- Original Message --------
Subject: [Enum] GrandCentral
From: "Lee Dryburgh" <dryburghl@gmail.com>
Date: Sun, October 08, 2006 2:13 pm
To: enum@ietf.org

I sent the email below to the list but due to list problems it never
was posted. I was just going to leave it, but I am soon preparing a
slide pack on telco services which never lived up to promises (ISDN,
WAP, MMS, IN, ATM, 3G). I am considering adding in User ENUM. For this
reason, I've dug the mail out and wonder if anybody really sees User
ENUM taking off particularly in light of such services? -->

---------- Forwarded message ----------
From: Lee Dryburgh <dryburghl@gmail.com>
Date: 28-Sep-2006 19:04
Subject: GrandCentral
To: "enum@ietf.org" <enum@ietf.org>


I thought the members of this list would be interested in the
following which recently launched:

http://www.grandcentral.com/

The blogosphere has been very positive about it.

In short from
http://www.lifehacker.com/software/telephone/one-phone-number-to-rule-them-all-203629.php

"GrandCentral is a brilliant new web app that lets you consolidate all
of your phone numbers into one number, meaning someone can call you on
your GrandCentral phone number and all of your phones (cell phone,
work phone, home phone) will ring. And then it gets interesting."

Regards

Lee

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
--===============1378721044== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============1378721044==-- From enum-bounces@ietf.org Thu Oct 12 11:47:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY2kL-0005g0-4C; Thu, 12 Oct 2006 11:45:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY2kK-0005fv-0p for enum@ietf.org; Thu, 12 Oct 2006 11:45:20 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY2kH-0000ic-KD for enum@ietf.org; Thu, 12 Oct 2006 11:45:20 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9CFjDqZ029189; Thu, 12 Oct 2006 08:45:18 -0700 From: "Richard Shockey" To: "'Egbert, Brian G [CTO]'" , Subject: RE: [Enum] Its that time again to start thinking about San Diego Date: Thu, 12 Oct 2006 11:44:59 -0400 Message-ID: <005501c6ee15$605f9ac0$4a201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acbe+zysU/md/nLMRmijdVg/cFT28wBsP2HAA1pGirA= In-Reply-To: <92FFCF194CB9FF4CBA28EE5D5A89C15008B95CE5@PDAWB15C.ad.sprint.com> X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org At this point I'd say a 70% probability of Monday. > -----Original Message----- > From: Egbert, Brian G [CTO] [mailto:Brian.G.Egbert@sprint.com] > Sent: Monday, September 25, 2006 10:13 AM > To: richard@shockey.us; enum@ietf.org > Subject: RE: [Enum] Its that time again to start thinking about San Diego > > > Hi Richard, > > I don't know about anyone else but I have an adjacent conference to the > meeting. Can/will you tell me what days of the week we will plan on > meeting? This will make a big impact on my travel plans. > > Thanks, > > Brian > > Brian G Egbert > Technology Development Specialist III > Global Technology Standards > 6220 Sprint Parkway > Overland Park, KS 66215-6118 > Office: (913) 794-4289 > Wireless: (913) 226-6719 > Brian.G.Egbert@sprint.com > > > > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us] > Sent: Saturday, September 23, 2006 5:30 AM > To: enum@ietf.org > Subject: [Enum] Its that time again to start thinking about San Diego > > > > Its agenda planning time again! > > If you plan on making a presentation for discussion you should get your > drafts in ASAP and let the chairs know how much time you need etc. > > > Richard Shockey > Director, Member of the Technical Staff > NeuStar > 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org > sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 > 703.593.2683 > > > > > > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 11:56:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY2u1-00012K-Cr; Thu, 12 Oct 2006 11:55:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY2u0-00012D-5b for enum@ietf.org; Thu, 12 Oct 2006 11:55:20 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY2ty-0003PP-NL for enum@ietf.org; Thu, 12 Oct 2006 11:55:20 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9CFtNtZ030752 for ; Thu, 12 Oct 2006 08:55:29 -0700 From: "Richard Shockey" To: Date: Thu, 12 Oct 2006 11:55:05 -0400 Message-ID: <005a01c6ee16$ca208d60$4a201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AcbuFsjNowLhX8ExTqiKMinFKC5u9Q== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Subject: [Enum] Preliminary ENUM agenda ... X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Let me know if there are any additions or corrections here. Agenda of the 67th IETF Meeting Probably Monday PRELIMINARY: IETF 67 San Diego Telephone Number Mapping (ENUM) WG Agenda Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alexander Mayrhofer RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com RAI Area Advisor: Jon Peterson Review of Agenda Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary Experience draft finalization? Enumservices Guide? draft-ietf-enum-3761bis-00.txt draft-ietf-enum-uri-00.txt 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 : The Uniform Resource Identifier (URI) DNS Resource Record Author(s) : P. Faltstrom, O. Kolkman Filename : draft-ietf-enum-uri-00.txt Pages : 11 Date : 2006-9-28 This document defines a new DNS resource record, called the Uniform Resource Identifier (URI) RR, for publishing mappings from hostnames to URIs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-uri-00.txt Title : The ENUM Branch Location Record Author(s) : O. Lendl Filename : draft-lendl-enum-branch-location-record-02.txt Pages : 7 Date : 2006-6-26 This documents defines the ENUM Branch Location record which is used to indicate where the ENUM tree for special ENUM application is located. The primary application for the EBL is to enable a temporary solution for the infrastructure ENUM tree. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lendl-enum-branch-location-record- 02.txt Title : Authentication Scheme for Public ENUM Applications Author(s) : C. Hui, et al. Filename : draft-chenh-enum-app-auth-00.txt Pages : 15 Date : 2006-10-9 ENUM possesses the feature of E.164 number authenticity, therefore by being carried with initiation signal of application services, ENUM number can be used to identify originer. The service initiation signal includes sender's (originer's) un- encrypted ENUM number and encrypted ENUM number, or some other information needed by specific applications, then receiver decrypts encrypted ENUM number and compares decrypted result with the un- encrypted ENUM number to authenticate the originer's identity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chenh-enum-app-auth-00.txt Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-xmpp-00.txt Pages : 7 Date : 2006-10-2 This document requests IANA registration of an Enumservice for Extensible Messaging and Presence Protocol (XMPP) Uniform Resource Identifiers (URIs) according to the registration procedure outlined in RFC 3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt Title : IANA Registration for Enumservice foaf Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-01.txt Pages : 8 Date : 2006-8-17 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). Information collected from FOAF can be used before, during or after a communication is established. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-01.txt Infrastructure ENUM root discussion ???? Open Session ?. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 13:55:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4kk-00085M-NC; Thu, 12 Oct 2006 13:53:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY4kj-000845-DN for enum@ietf.org; Thu, 12 Oct 2006 13:53:53 -0400 Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GY4kg-0007EE-RQ for enum@ietf.org; Thu, 12 Oct 2006 13:53:53 -0400 X-VirusChecked: Checked X-Env-Sender: ppfautz@att.com X-Msg-Ref: server-6.tower-121.messagelabs.com!1160675629!9867518!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 1282 invoked from network); 12 Oct 2006 17:53:49 -0000 Received: from unknown (HELO attrh0i.attrh.att.com) (134.24.146.4) by server-6.tower-121.messagelabs.com with SMTP; 12 Oct 2006 17:53:49 -0000 Received: from attrh.att.com (localhost [127.0.0.1]) by attrh0i.attrh.att.com (8.13.7/8.13.7) with ESMTP id k9CHrmTw018194 for ; Thu, 12 Oct 2006 13:53:48 -0400 (EDT) Received: from attrh2i.attrh.att.com (attrh2i.attrh.att.com [135.37.94.56]) by attrh0i.attrh.att.com (8.13.7/8.13.7) with ESMTP id k9CHqNGl017643 for ; Thu, 12 Oct 2006 13:53:43 -0400 (EDT) Received: from ACCLUST02EVS1.ugd.att.com (135.37.16.8) by attrh2i.attrh.att.com (7.2.052) id 450D72320046A638 for enum@ietf.org; Thu, 12 Oct 2006 13:53:43 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] Preliminary ENUM agenda ...draft-chenh-enum-app-auth-00.txt Date: Thu, 12 Oct 2006 13:53:42 -0400 Message-ID: <34DA635B184A644DA4588E260EC0A25A0DDCA045@ACCLUST02EVS1.ugd.att.com> In-Reply-To: <005a01c6ee16$ca208d60$4a201f0a@cis.neustar.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Preliminary ENUM agenda ...draft-chenh-enum-app-auth-00.txt Thread-Index: AcbuFsjNowLhX8ExTqiKMinFKC5u9QADswVw From: "Pfautz, Penn L, GBLAM" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I assume the announcement for this I-D is coming but some comments anyway... I think the use of ENUM to support end-to-end authentication is an interesting possibility. It might even turn out to be the killer app for user ENUM :-) Am I right in assuming that the E.164 number registered in ENUM must be combined with a timestamp or call-ID or other information specific to the session being initiated before being encrypted in order to prevent replay attacks? Penn Pfautz -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us]=20 Sent: Thursday, October 12, 2006 11:55 AM To: enum@ietf.org Subject: [Enum] Preliminary ENUM agenda ... Title : Authentication Scheme for Public ENUM Applications Author(s) : C. Hui, et al. Filename : draft-chenh-enum-app-auth-00.txt Pages : 15 Date : 2006-10-9 =09 ENUM possesses the feature of E.164 number authenticity, therefore by being carried with initiation signal of application services, ENUM number can be used to identify originer. The service initiation signal includes sender's (originer's) un- encrypted ENUM number and encrypted ENUM number, or some other information needed by specific applications, then receiver decrypts encrypted ENUM number and compares decrypted result with the un- encrypted ENUM number to authenticate the originer's identity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chenh-enum-app-auth-00.txt _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 14:54:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY5fy-000486-3c; Thu, 12 Oct 2006 14:53:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY5fx-000481-IZ for enum@ietf.org; Thu, 12 Oct 2006 14:53:01 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY5fw-0004lW-4y for enum@ietf.org; Thu, 12 Oct 2006 14:53:01 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9CIr5XS000725 for ; Thu, 12 Oct 2006 11:53:11 -0700 From: "Richard Shockey" To: Date: Thu, 12 Oct 2006 14:52:52 -0400 Message-ID: <013201c6ee2f$a096f880$4a201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0133_01C6EE0E.19855880" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acbr3F/Y5RHTzyrmRNCSjHXS20islQCUzMpQ X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 2.0 (++) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Subject: [Enum] FW: I-D ACTION:draft-yu-tel-dai-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. ------=_NextPart_000_0133_01C6EE0E.19855880 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable OF interest to some ... > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Monday, October 09, 2006 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-yu-tel-dai-00.txt >=20 > A New Internet-Draft is available from the on-line Internet-Drafts > directories. >=20 >=20 > Title : DAI Parameter for the ^tel^ URI > Author(s) : J. Yu > Filename : draft-yu-tel-dai-00.txt > Pages : 15 > Date : 2006-10-9 >=20 > This document defines a =13dai=14 parameter for the ""tel"" Uniform > Resource Identifier (URI) to support the Dial Around Indicator > (DAI). The ""dai"" parameter is associated with the ""cic"" = parameter > and indicates how the carrier identified in the ""cic"" parameter = is > chosen to handle the call. >=20 >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-yu-tel-dai-00.txt >=20 > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@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. >=20 > 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-yu-tel-dai-00.txt". >=20 > 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 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-yu-tel-dai-00.txt". >=20 > 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. >=20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. ------=_NextPart_000_0133_01C6EE0E.19855880 Content-Type: Message/External-body; name="ATT00435.dat" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00435.dat" Content-Type: text/plain Content-ID: <2006-10-9124535.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-yu-tel-dai-00.txt ------=_NextPart_000_0133_01C6EE0E.19855880 Content-Type: Message/External-body; name="draft-yu-tel-dai-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-yu-tel-dai-00.txt" Content-Type: text/plain Content-ID: <2006-10-9124535.I-D@ietf.org> ------=_NextPart_000_0133_01C6EE0E.19855880 Content-Type: text/plain; name="ATT00438.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00438.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------=_NextPart_000_0133_01C6EE0E.19855880 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_0133_01C6EE0E.19855880-- From enum-bounces@ietf.org Thu Oct 12 15:00:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY5mA-000222-81; Thu, 12 Oct 2006 14:59:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY5m9-00021x-H6 for enum@ietf.org; Thu, 12 Oct 2006 14:59:25 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY5m8-0005yV-3q for enum@ietf.org; Thu, 12 Oct 2006 14:59:25 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9CIxN8n002156 for ; Thu, 12 Oct 2006 11:59:28 -0700 From: "Richard Shockey" To: Date: Thu, 12 Oct 2006 14:59:03 -0400 Message-ID: <013c01c6ee30$7d109f00$4a201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acbr3DiBz+RmIK8kRL6j9GFHIAf1iACVDaaw X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Subject: [Enum] FW: I-D ACTION:draft-chenh-enum-app-auth-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Monday, October 09, 2006 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-chenh-enum-app-auth-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Authentication Scheme for Public ENUM Applications > Author(s) : C. Hui, et al. > Filename : draft-chenh-enum-app-auth-00.txt > Pages : 15 > Date : 2006-10-9 > > > ENUM possesses the feature of E.164 number authenticity, therefore by > being carried with initiation signal of application services, ENUM > number can be used to identify originer. > > The service initiation signal includes sender's (originer's) un- > encrypted ENUM number and encrypted ENUM number, or some other > information needed by specific applications, then receiver decrypts > encrypted ENUM number and compares decrypted result with the un- > encrypted ENUM number to authenticate the originer's identity. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-chenh-enum-app-auth-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@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-chenh-enum-app-auth-00.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@ietf.org. > In the body type: > "FILE /internet-drafts/draft-chenh-enum-app-auth-00.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@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 15:40:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY6OT-0006ob-Qk; Thu, 12 Oct 2006 15:39:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY6OS-0006lf-1z for enum@ietf.org; Thu, 12 Oct 2006 15:39:00 -0400 Received: from rwcrmhc14.comcast.net ([204.127.192.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY6IX-0003NI-BZ for enum@ietf.org; Thu, 12 Oct 2006 15:32:54 -0400 Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (rwcrmhc14) with ESMTP id <20061012193251m14003qnlme>; Thu, 12 Oct 2006 19:32:52 +0000 Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id k9CJWoUm027935 for ; Thu, 12 Oct 2006 15:32:50 -0400 Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id k9CJWoMi027931; Thu, 12 Oct 2006 15:32:50 -0400 Date: Thu, 12 Oct 2006 15:32:50 -0400 Message-Id: <200610121932.k9CJWoMi027931@dragon.ariadne.com> To: enum@ietf.org From: Dale.Worley@comcast.net In-reply-to: <34DA635B184A644DA4588E260EC0A25A0DDCA045@ACCLUST02EVS1.ugd.att.com> (ppfautz@att.com) References: <34DA635B184A644DA4588E260EC0A25A0DDCA045@ACCLUST02EVS1.ugd.att.com> X-Spam-Score: 0.2 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: [Enum] Test numbers X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I am new in working with ENUM, and I'd like to test out our ENUM resolver. Are there any "test numbers" with known ENUM resolutions that I can use? Unfortunately, it's hard to search a sparse DNS space to find the valid entries. Thanks, Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 17:10:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY7nD-0005Xj-Kp; Thu, 12 Oct 2006 17:08:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GY7nC-0005S9-BJ for enum@ietf.org; Thu, 12 Oct 2006 17:08:38 -0400 Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GY7n8-000248-26 for enum@ietf.org; Thu, 12 Oct 2006 17:08:38 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id 507E41A36C; Thu, 12 Oct 2006 23:08:22 +0200 (CEST) Date: Thu, 12 Oct 2006 23:08:22 +0200 From: Otmar Lendl To: enum@ietf.org Subject: Re: [Enum] Test numbers Message-ID: <20061012210822.GA22675@nic.at> References: <34DA635B184A644DA4588E260EC0A25A0DDCA045@ACCLUST02EVS1.ugd.att.com> <200610121932.k9CJWoMi027931@dragon.ariadne.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200610121932.k9CJWoMi027931@dragon.ariadne.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On 2006/10/12 21:10, Dale.Worley@comcast.net wrote: > I am new in working with ENUM, and I'd like to test out our ENUM > resolver. Are there any "test numbers" with known ENUM resolutions > that I can use? Unfortunately, it's hard to search a sparse DNS space > to find the valid entries. See http://enum-test.at/index_en.html for some numbers with which you can test ENUM call routing implementations. /ol -- < Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 12 20:42:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYB54-0002Yl-03; Thu, 12 Oct 2006 20:39:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYB52-0002YS-4q for enum@ietf.org; Thu, 12 Oct 2006 20:39:16 -0400 Received: from mailgw.nic.or.kr ([202.30.50.169] helo=nida.or.kr) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GYB4v-0005bQ-NO for enum@ietf.org; Thu, 12 Oct 2006 20:39:16 -0400 X-HELO: ehlo mail.nic.or.kr X-RECEIVED-IP: 202.30.50.51 Received: from 202.30.50.51(202.30.50.51) at Fri, 13 Oct 2006 09:39:49 +0900 by nida.or.kr with ESMTP CrediShield X-MAIL-FROM: ssw@nic.or.kr Received: from SSWMain (localhost [127.0.0.1]) by mail.nic.or.kr (v3smtp 8.11.6.9/8.11.0) with SMTP id k9D0cRi24689 for ; Fri, 13 Oct 2006 09:38:27 +0900 (KST) Message-ID: <005801c6ee5f$e5ea5000$bdb4fea9@SSWMain> From: "Sungwoo Shin" To: Date: Fri, 13 Oct 2006 09:38:26 +0900 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0056_01C6EEAB.5585ACC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: 0.2 (/) X-Scan-Signature: 715d0e6950aaebd45af78ef9318d0186 Subject: [Enum] Idea of call rotung using ENUM-based softswitch X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. ------=_NextPart_000_0056_01C6EEAB.5585ACC0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 RGVhciBXRyBtZW1iZXJzDQoNCkluIGNvbmR1Y3RpbmcgdHJpYWwgYmFzZWQgb24gSW5mcmFzdHJ1 Y3R1cmUgRU5VTSB0cmlhbCwgbXkgY29sbGVhZ3VlIGFuZCANCkkgaGF2ZSBmb3VuZCBzb21lIGlz c3VlIG9mIGNhbGwgcm91dGluZy4gDQoNClRoaXMgeWVhciwgaW4gSW5mcmEgRU5VTSB0cmlhbChw cmUtY29tbWVyY2lhbCBzdGFnZSkgYmVpbmcgbGVkIGJ5IE5hdGlvbmFsDQpJbnRlcm5ldCBEZXZl bG9wZW1lbnQgQWdlbmN5LCAyIG1ham9yIGtvcmVhbiBWb0lQIHNlcnZpY2UgcHJvdmlkZXJzDQpq b2luIHRoZSBwcm9qZWN0LCB0aGUgbWFpbiBpZGVhIGlzIFZvSVAgY2FsbCBpbnRlcmNvbm5lY3Rp b24gdGhyb3VnaCANCkVOVU0gRE5TIGxvb2t1cCAgIA0KDQpJbiB0aGUgdHJpYWwsIGZvciBxdWVy eWluZyBFTlVNIEROUyBhbmQgbG9vay11cCwgc3BlY2lmaWMgbW9kdWxlIGZvciBlbWJlZGRpbmcg DQp0byBTb2Z0U3dpdGNoIHdhcyBuZWVkZWQgdG8gYmUgZGV2ZWxvcGVkLiANCg0KVGhlcmUgYXJl IG5vdCBtYW55IFZvSVAgc2VydmljZSBwcm92aWRlcnMgaW4gdGhlIHRyaWFsIGJ1dCB0d28sIEVO VU0gRE5TDQpoYXMgbm90IG11Y2ggc3VmZmljaWVudCBkYXRhIGZvciBjYWxsLXJvdXRpbmcgaW4g dHJpYWwgYmFzaXMgDQpUaGlzIHNvZnRzd2l0Y2ggY2Fubm90IG1ha2UgIHByb3BlciBjYWxsIHJv dXRpbmcgaWYgaXQgZmFpbHMgdG8gZmluZCByZWxldmFudCANCmRhdGEgaW4gdGhlIEVOVU0gRE5T LiANCiANClRoZXJlZm9yZSBzb2Z0c3dpaXRjaCBtb2R1bGUgd2FzIGRldmVsb3BlZC0gaWYgdGhp cyBtb2R1bGUgY2FuJ3QgZmluZCBkYXRhICANCmZyb20gRU5VTSBETlMgdGhlbiBhdXRvbWF0aWNh bGx5IGl0IGdvZXMgYmFjayB0byB0aGUgIm9sZCB3YXkiLGxpa2UgdGhlIHdheQ0Kb2YgcHJlZml4 LWJhc2VkIGNhbGwgcm91aW5nLiANCg0KV2l0aCB0aGlzIGV4cGVyaWVuY2UsIG15IGNvbGxlZ3Vl cyBhbmQgSSB0cnkgdG8gd3JpdGUgZHJhZnQgZm9yIGJlc3QgcHJhY3RpY2UuIA0KVGhpcyBpcyB2 ZXJ5IGRyYWZ0IGFuZCB3ZSBhcmUgZXhwZWN0aW5nIGFueSBjb21tZW50IGFuZCBvcGluaW9uDQpm b3IgcmVmbGVjdGluZyBvbiB0aGUgZHJhZnQgYmVmb3JlIHVwY29taW5nIG1lZXRpbmcsIA0KDQpU aGFua3MgZm9yIHJlYWRpbmcNCg0KUmVnYXJkcyANCg0KU3VuZ3dvbyBTaGluIA0KSm9vbkh5dW5n IExpbQ0K ------=_NextPart_000_0056_01C6EEAB.5585ACC0 Content-Type: text/plain; name="draft-lim-kim-enum-based-softswitch-00.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="draft-lim-kim-enum-based-softswitch-00.txt" =20 =20 =20 ENUM JoonHyung Lim=20 Internet Draft Weon Kim=20 Expires: NIDA=20 October 2006=20 =20 =20 ENUM-based Softswitch Requirement=20 =20 =20 Status of this Memo=20 =20 By submitting this Internet-Draft, each author represents that any =20 applicable patent or other IPR claims of which he or she is aware =20 have been or will be disclosed, and any of which he or she becomes =20 aware will be disclosed, in accordance with Section 6 of BCP 79. =20 =20 Internet-Drafts are working documents of the Internet Engineering =20 Task Force (IETF), its areas, and its working groups. Note that =20 other groups may also distribute working documents as Internet-=20 Drafts. =20 =20 Internet-Drafts are draft documents valid for a maximum of six =20 months and may be updated, replaced, or obsoleted by other documents = at any time. It is inappropriate to use Internet-Drafts as =20 reference material or to cite them other than as "work in progress". = =20 =20 The list of current Internet-Drafts can be accessed at =20 http://www.ietf.org/ietf/1id-abstracts.txt. =20 =20 The list of Internet-Draft Shadow Directories can be accessed at =20 http://www.ietf.org/shadow.html. =20 =20 This Internet-Draft will expire on=20 =20 Abstract=20 =20 This document describes simple requirement for softswitch, which use=20 ENUM DNS to route a call on VoIP service. This requirement is one of=20 interim solution to maintain stability of on-going commercial=20 softswitch system while initial stage of ENUM service that does not=20 have sufficient data.=20 =20 Table of Contents=20 =20 1. Introduction...................................................2=20 2. Terminology....................................................2=20 3. Call-Routing of Softswitch.....................................2=20 4. Requirement for ENUM-based Softswitch..........................3=20 5. 'e164.arpa' consideration......................................4 =20 =20 Lim & Kim Expires - [Page 1]=20 =0C ENUM-based Softswitch Requirement October 2006=20 =20 =20 6. Security Considerations........................................4=20 7. IANA Consideration.............................................4=20 8. References.....................................................4=20 Author's Addresses................................................5=20 Intellectual Property and Copyright Statements ...................5=20 =20 =20 1. Introduction =20 ENUM[1] is a mapping system based on DNS[3] that converts from=20 E.164[2] number to domain name using 'Naming Authority=20 Pointer(NAPTR)' resource record, which is able to store different=20 service types such as fax, email, homepage, and etc., for every E.164 = number. It originally focused on how end-user could access to other=20 end-user's information through the Internet. =20 =20 Recently, various discussions are needed about RFC3761[1], because = infrastructure ENUM that provides routing information between=20 carriers.=20 =20 Specially, In case of VoIP service, VoIP carrier that wants to=20 integrate various protocols uses softswitch. However, It is=20 inefficient for interconnection and number portability between=20 carriers because softswitch does not have all numbers that carriers=20 dealing with and it has its own number translation method for E.164=20 that is not compatible to others. Therefore, carriers expect many=20 benefits If they use a ENUM for routing purpose on softswitch.=20 =20 However, it is too difficult to establish complete ENUM system all = over the world simultaneously. Interim period, which fills up the=20 data to ENUM DNS and make sure regulation of each country with=20 NRA(National Regulatory Authority) is necessary. =20 =20 During the interim period, a group of carriers, which willing to=20 gather their own call-routing data to one ENUM DNS are also needed to = route a call that can not find a answer on ENUM DNS. =20 =20 So, this document introduces simple requirement about call-routing = on ENUM-based softswitch that operated by VoIP carriers. =20 =20 2. Terminology =20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this=20 document are to be interpreted as described in BCP 14, RFC 2119 [6].=20 =20 3. Call-Routing of Softswitch =20 =20 =20 Lim & Kim Expires - [Page 2]=20 =0C ENUM-based Softswitch Requirement October 2006=20 =20 =20 In the PSTN(Public Switched Telephone Network), Only hardware-typed=20 switch rules the network. Softswitch is the switch implemented on=20 computer system by software. It usually controls various signaling=20 protocols which are SIP[7], H.323[8], MGCP[9], and etc., to make call = connections for VoIP service on the boundary point between circuit=20 and packet network. =20 =20 To make call routing, first of all, Softswitch translate the=20 number as vendor specific method to routing information, which can=20 find destination. Today, prefix-based number translation has not only = used in legacy PSTN switch, but also used in softswitch very widely.=20 =20 This kind of vendor specific call routing is only reference to=20 their own routing information, so if there is a carrier wants to get=20 out or get in, rest of carriers make some change routing information=20 on their softswitch. It is not efficient on the aspect of number=20 management.=20 =20 Today, many carriers dealing with VoIP for several years, faces same=20 difficulties of inefficiency. For example, carriers process various=20 signaling protocols, and interconnect to multiple carriers without=20 any centralized point. Therefore, if softswitches are able to=20 transform E.164 number to routing information by using ENUM DNS, it=20 will be more efficient on call routing.=20 =20 4. Requirement for ENUM-based Softswitch =20 To use ENUM DNS, softswitch need to have ENUM module that converts=20 from E.164 number to ENUM domain name defined in RFC3761 and process=20 a query to ENUM DNS. ENUM module MUST follow the RFC3761.=20 =20 However, initial stage of ENUM DNS shares call routing information=20 from limited carriers, so It makes problem that softswitch can't find = all of call routing information on ENUM DNS. To solve this problem,=20 ENUM-based softswitch MUST follow the below. =20 =20 1. ENUM module of softswitch converts E.164 number comes from the = VoIP subscriber to domain name defined RFC3761.=20 =20 2. ENUM module of softswitch as a stub resolver, send a query to=20 recursive name server with domain name described above.=20 =20 3. If the 'Rcode' field is '3', which means 'non-existence=20 domain' in answer section of DNS message defined RCF1035[4],=20 softswitch MUST translate the number with its vendor specific=20 prefix-based translation subsequently. =20 =20 Even if the interim period, carriers can use ENUM DNS for number=20 translation without any affect on their on-going commercial service.=20 =20 =20 Lim & Kim Expires - [Page 3]=20 =0C ENUM-based Softswitch Requirement October 2006=20 =20 =20 At the first time, most of calls queried to ENUM DNS is almost hard=20 to get the answer in case of small group of carriers, however it will = be getting more answer from ENUM DNS if group of carriers is getting=20 more bigger.=20 =20 It seems like inefficient because administrator maintains two=20 management points of numbers which is ENUM DNS and softswitch itself. = However it will be able to minimize failure ratio of call routing=20 from transition period of ENUM, and hereafter if ENUM comes to fill,=20 there is single management point on ENUM without any major changes on = softswitch.=20 =20 5. e164.arpa' consideration=20 =20 Today, some discussions about Infrastructure ENUM consideration based = on RFC3761, is related to new 'e164.arpa' tree. ENUM module embeded=20 on softswitch MUST follow the new e164.arpa tree when new branch=20 method of e164.arpa for Infrastructue ENUM is set.=20 =20 6. Security Considerations=20 =20 If the recursive DNS handles ENUM queries from softswitch is=20 compromised by attacker, It will be able to make wrong call routing=20 or occur delay to call. Therefore, recursive DNS MAY lets in the=20 local network as same as softswitch, and restrict access from outside = with proper access-list policy.=20 =20 7. IANA Consideration=20 This document is only advisory, and does not include any IANA=20 considerations.=20 =20 8. References=20 8.1. Normative References=20 =20 [1] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource = Identifiers (URI) Dynamic Delegation Discovery System (DDDS)=20 Application (ENUM)", RFC 3761, April 2004.=20 =20 [2] International Telecommunication Union-Telecommunication=20 Standardization Sector, "The International Public=20 Telecommunication Numbering Plan", Recommendation E.164",=20 February 2005.=20 =20 [3] P. Mockapetris, "DOMAIN NAMES - CONCEPTS AND FACILITIES", =20 RFC 1034, November 1987.=20 =20 [4] P. Mockapetris, "DOMAIN NAMES - IMPLEMENTATION AND=20 SPECIFICATION", RFC 1035, November 1987.=20 =20 =20 =20 Lim & Kim Expires - [Page 4]=20 =0C ENUM-based Softswitch Requirement October 2006=20 =20 =20 [5] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform=20 Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, = January 2005.=20 =20 [6] Bradner, S., "Key words for use in RFCs to Indicate=20 Requirement Levels", BCP 14, RFC 2119, March 1997.=20 =20 8.2. Informative References=20 =20 [7] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J.=20 Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: = Session=20 Initiation Protocol", RFC 2119, June 2002.=20 =20 [8] "Packet-based multimedia communications systems", ITU-T=20 Recommendation H.323, 2003.=20 =20 [9] F. Andreasen, B. Foster, "Media Gateway Control Protocol=20 (MGCP) Version 1.0", RFC 3435, January 2003=20 =20 Authors' Addresses=20 =20 JoonHyung Lim=20 National Internet Develompment Agency of Korea=20 3F. KTF B/D 1321-11, Seocho-dong, Seocho-gu, Seoul=20 Korea=20 Phone: +82-2-2186-4548=20 Email: jhlim@nida.or.kr=20 URI: http://www.nida.or.kr =20 Weon Kim=20 National Internet Develompment Agency of Korea=20 3F. KTF B/D 1321-11, Seocho-dong, Seocho-gu, Seoul=20 Korea=20 Phone: +82-2-2186-4502=20 Email: wkim@nida.or.kr=20 URI: http://www.nida.or.kr =20 Intellectual Property Statement=20 =20 The IETF takes no position regarding the validity or scope of any=20 Intellectual Property Rights or other rights that might be claimed to = pertain to the implementation or use of the technology described in=20 this document or the extent to which any license under such rights=20 might or might not be available; nor does it represent that it has=20 made any independent effort to identify any such rights. Information = on the procedures with respect to rights in RFC documents can be=20 found in BCP 78 and BCP 79.=20 =20 =20 Lim & Kim Expires - [Page 5]=20 =0C ENUM-based Softswitch Requirement October 2006=20 =20 =20 =20 Copies of IPR disclosures made to the IETF Secretariat and any=20 assurances of licenses to be made available, or the result of an=20 attempt made to obtain a general license or permission for the use of = such proprietary rights by implementers or users of this=20 specification can be obtained from the IETF on-line IPR repository at = http://www.ietf.org/ipr.=20 =20 The IETF invites any interested party to bring to its attention any=20 copyrights, patents or patent applications, or other proprietary=20 rights that may cover technology that may be required to implement=20 this standard. Please address the information to the IETF at=20 ietf-ipr@ietf.org.=20 =20 Disclaimer of Validity=20 =20 This document and the information contained herein are provided on an = "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS = OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET=20 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,=20 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE=20 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED=20 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=20 =20 Copyright Statement=20 =20 Copyright (C) The Internet Society (2006). This document is subject=20 to the rights, licenses and restrictions contained in BCP 78, and=20 except as set forth therein, the authors retain all their rights.=20 =20 Acknowledgment=20 =20 Funding for the RFC Editor function is currently provided by the=20 Internet Society.=20 =20 =20 Lim & Kim Expires - [Page 6]=20 =0C ------=_NextPart_000_0056_01C6EEAB.5585ACC0 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_0056_01C6EEAB.5585ACC0-- From enum-bounces@ietf.org Mon Oct 16 21:59:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZeCX-00057l-Ef; Mon, 16 Oct 2006 21:57:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZeCW-00057X-D5 for enum@ietf.org; Mon, 16 Oct 2006 21:57:04 -0400 Received: from smtp.cnnic.cn ([159.226.7.146] helo=cnnic.cn) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GZeCU-00009g-D6 for enum@ietf.org; Mon, 16 Oct 2006 21:57:04 -0400 Received: (eyou send program); Tue, 17 Oct 2006 09:56:54 +0800 Message-ID: <361050214.12848@cnnic.cn> X-EYOUMAIL-SMTPAUTH: chenhui@cnnic.cn Received: from unknown (HELO cnnicchenh) (159.226.6.99) by 159.226.7.146 with SMTP; Tue, 17 Oct 2006 09:56:54 +0800 Message-ID: <00a601c6f18f$876e7be0$6306e29f@cnnicchenh> From: "chenhui" To: "Pfautz, Penn L, GBLAM" , References: <360675854.09860@cnnic.cn> Subject: Re: [Enum] Preliminary ENUM agenda ...draft-chenh-enum-app-auth-00.txt Date: Tue, 17 Oct 2006 09:56:57 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Score: 0.9 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: =?utf-8?B?J+eOiyDls7An?= , lee@cnnic.cn X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1219689734==" Errors-To: enum-bounces@ietf.org --===============1219689734== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RGVhciBQZW5uIFBmYXV0eiwNCg0KVGhhbmsgeW91IGZvciB5b3VyIGNvbW1lbnRzLg0KWW91ciBh c3N1bXB0aW9uIGlzIHRoZSBhY3R1YWwgbWV0aG9kIGZvciBpbXBsZW1lbnRhdGlvbiBvZiBhcHBs aWNhdGlvbiBhdXRoZW50aWNhdGlvbi4gQW5kIEkgYWxzbyB0aGluayB0aGUgaW5mb3JtYXRpb24g c3VjaCBhcyB0aW1lc3RhbXAgb3IgY2FsbC1pZCBpcyBuZWNlc3NhcnkgdG8gYmUgdXNlZC4NCg0K VGhpcyBJLUQgaXMgdG8gcHJvdmlkZSBhbiBhdXRoZW50aWNhdGlvbiBzY2hlbWUgZm9yIEVOVU0g YXBwbGljYXRpb24gYnkgbG9hZGluZyBfb3JpZ2luZXInc18gRU5VTSBudW1iZXIgaW4gdGhlIHNl c3Npb24uIA0KQXMgd2Uga25vdywgdGhlIEVOVU0gc3Vic2NyaWJlciBoYXMgc3VibWl0dGVkIGhp cyByZWFsIGluZm9ybWF0aW9uLCBzbyBFTlVNIG51bWJlciBjYW4gYmUgY29uc2lkZXJlZCB0aGUg dXNlcidzIGlkZW50aWZpZXIgb2YgaGlzIHJlYWxpdHkuIFRodXMgdGhlIHNlc3Npb24gd2l0aCBv cmlnaW5lcidzIEVOVU0gbnVtYmVyIGNhbiBiZSBhdXRoZW50aWNhdGVkIGJ5IHRoZSByZWNpZXZl ci4NCg0KQ2hlbmh1aQ0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlBm YXV0eiwgUGVubiBMLCBHQkxBTSIgPHBwZmF1dHpAYXR0LmNvbT4NClRvOiA8ZW51bUBpZXRmLm9y Zz4NClNlbnQ6IEZyaWRheSwgT2N0b2JlciAxMywgMjAwNiAxOjUzIEFNDQpTdWJqZWN0OiBSRTog W0VudW1dIFByZWxpbWluYXJ5IEVOVU0gYWdlbmRhIC4uLmRyYWZ0LWNoZW5oLWVudW0tYXBwLWF1 dGgtMDAudHh0DQoNCg0KSSBhc3N1bWUgdGhlIGFubm91bmNlbWVudCBmb3IgdGhpcyBJLUQgaXMg Y29taW5nIGJ1dCBzb21lIGNvbW1lbnRzDQphbnl3YXkuLi4NCg0KSSB0aGluayB0aGUgdXNlIG9m IEVOVU0gdG8gc3VwcG9ydCBlbmQtdG8tZW5kIGF1dGhlbnRpY2F0aW9uIGlzIGFuDQppbnRlcmVz dGluZyBwb3NzaWJpbGl0eS4NCkl0IG1pZ2h0IGV2ZW4gdHVybiBvdXQgdG8gYmUgdGhlIGtpbGxl ciBhcHAgZm9yIHVzZXIgRU5VTSA6LSkNCg0KQW0gSSByaWdodCBpbiBhc3N1bWluZyB0aGF0IHRo ZSBFLjE2NCBudW1iZXIgcmVnaXN0ZXJlZCBpbiBFTlVNIG11c3QgYmUNCmNvbWJpbmVkIHdpdGgg YSB0aW1lc3RhbXAgb3IgY2FsbC1JRCBvciBvdGhlciBpbmZvcm1hdGlvbiBzcGVjaWZpYyB0bw0K dGhlIHNlc3Npb24gYmVpbmcgaW5pdGlhdGVkIGJlZm9yZSBiZWluZyBlbmNyeXB0ZWQgaW4gb3Jk ZXIgdG8gcHJldmVudA0KcmVwbGF5IGF0dGFja3M/DQoNClBlbm4gUGZhdXR6DQoNCi0tLS0tT3Jp Z2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBSaWNoYXJkIFNob2NrZXkgW21haWx0bzpyaWNoYXJk QHNob2NrZXkudXNdIA0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMTIsIDIwMDYgMTE6NTUgQU0N ClRvOiBlbnVtQGlldGYub3JnDQpTdWJqZWN0OiBbRW51bV0gUHJlbGltaW5hcnkgRU5VTSBhZ2Vu ZGEgLi4uDQoNCg0KDQoNClRpdGxlIDogQXV0aGVudGljYXRpb24gU2NoZW1lIGZvciBQdWJsaWMg RU5VTSBBcHBsaWNhdGlvbnMNCkF1dGhvcihzKSA6IEMuIEh1aSwgZXQgYWwuDQpGaWxlbmFtZSA6 IGRyYWZ0LWNoZW5oLWVudW0tYXBwLWF1dGgtMDAudHh0DQpQYWdlcyA6IDE1DQpEYXRlIDogMjAw Ni0xMC05DQoNCg0KICAgRU5VTSBwb3NzZXNzZXMgdGhlIGZlYXR1cmUgb2YgRS4xNjQgbnVtYmVy IGF1dGhlbnRpY2l0eSwgdGhlcmVmb3JlIGJ5DQogICBiZWluZyBjYXJyaWVkIHdpdGggaW5pdGlh dGlvbiBzaWduYWwgb2YgYXBwbGljYXRpb24gc2VydmljZXMsIEVOVU0NCiAgIG51bWJlciBjYW4g YmUgdXNlZCB0byBpZGVudGlmeSBvcmlnaW5lci4NCg0KICAgVGhlIHNlcnZpY2UgaW5pdGlhdGlv biBzaWduYWwgaW5jbHVkZXMgc2VuZGVyJ3MgKG9yaWdpbmVyJ3MpIHVuLQ0KICAgZW5jcnlwdGVk IEVOVU0gbnVtYmVyIGFuZCBlbmNyeXB0ZWQgRU5VTSBudW1iZXIsIG9yIHNvbWUgb3RoZXINCiAg IGluZm9ybWF0aW9uIG5lZWRlZCBieSBzcGVjaWZpYyBhcHBsaWNhdGlvbnMsIHRoZW4gcmVjZWl2 ZXIgZGVjcnlwdHMNCiAgIGVuY3J5cHRlZCBFTlVNIG51bWJlciBhbmQgY29tcGFyZXMgZGVjcnlw dGVkIHJlc3VsdCB3aXRoIHRoZSB1bi0NCiAgIGVuY3J5cHRlZCBFTlVNIG51bWJlciB0byBhdXRo ZW50aWNhdGUgdGhlIG9yaWdpbmVyJ3MgaWRlbnRpdHkuDQoNCg0KQSBVUkwgZm9yIHRoaXMgSW50 ZXJuZXQtRHJhZnQgaXM6DQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFm dC1jaGVuaC1lbnVtLWFwcC1hdXRoLTAwLnR4dA0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18NCmVudW0gbWFpbGluZyBsaXN0DQplbnVtQGlldGYu b3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9lbnVtDQo= --===============1219689734== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --===============1219689734==-- From enum-bounces@ietf.org Tue Oct 17 10:24:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZpqe-0008EH-Vh; Tue, 17 Oct 2006 10:23:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZpqZ-0007yv-QX for enum@ietf.org; Tue, 17 Oct 2006 10:23:11 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZpdN-0004QO-Af for enum@ietf.org; Tue, 17 Oct 2006 10:09:37 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9HE9Sn7030489 for ; Tue, 17 Oct 2006 07:09:34 -0700 From: "Richard Shockey" To: Date: Tue, 17 Oct 2006 10:09:08 -0400 Message-ID: <026801c6f1f5$d0f5a980$50201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acbx9c+9PnjquObORsCr+YHtgwZcnw== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Enum] 95% probability ENUM mtg on monday. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The final agenda can be found at: http://www3.ietf.org/meetings/agenda_67.txt Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 18 15:54:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaHSy-0004M2-PG; Wed, 18 Oct 2006 15:52:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaHRt-0002pn-8s; Wed, 18 Oct 2006 15:51:33 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaHRt-0003yF-4R; Wed, 18 Oct 2006 15:51:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GaHRs-0001qu-Or; Wed, 18 Oct 2006 15:51:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 58DF12ACFB; Wed, 18 Oct 2006 19:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GaHQR-0001V3-3M; Wed, 18 Oct 2006 15:50:03 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 18 Oct 2006 15:50:03 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-3761bis-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart 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 : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) Author(s) : P. Faltstrom Filename : draft-ietf-enum-3761bis-00.txt Pages : 18 Date : 2006-10-18 This document discusses the use of the Domain Name System (DNS) for storage of E.164 [E164] numbers, and resolving those to URIs that can be used for (for example) call setup. This include how DNS can be used for identifying available services connected to one E.164 number. It obsoletes RFC 3761 [RFC3761]. This version of the document (00) is not more than the start of a discussion for detailed changes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-3761bis-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-3761bis-00.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-3761bis-00.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-18143739.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-3761bis-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-3761bis-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-18143739.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Wed Oct 18 17:44:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJBq-0002dS-DK; Wed, 18 Oct 2006 17:43:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJBn-0002c5-Oi; Wed, 18 Oct 2006 17:43:03 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaJBl-00087x-QH; Wed, 18 Oct 2006 17:43:03 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 18 Oct 2006 14:43:01 -0700 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9ILh1el004662; Wed, 18 Oct 2006 17:43:01 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9ILh1YJ028785; Wed, 18 Oct 2006 17:43:01 -0400 (EDT) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 17:43:01 -0400 Received: from [161.44.55.215] ([161.44.55.215]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Oct 2006 17:43:01 -0400 Message-ID: <45369FE5.8060106@cisco.com> Date: Wed, 18 Oct 2006 17:43:01 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: IETF SIP List , IETF Sipping List , enum@ietf.org, list iptel Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2006 21:43:01.0078 (UTC) FILETIME=[62428760:01C6F2FE] DKIM-Signature: a=rsa-sha1; q=dns; l=1111; t=1161207781; x=1162071781; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:New=20I-D=20on=20usage=20of=20phone=20numbers=20in=20SIP=20[DO=20NOT=20R EPLY!] |To:IETF=20SIP=20List=20, =20IETF=20Sipping=20List=20, =0A=20=20=20=20=20=20=20=20enum@ietf.org, =20list=20iptel=20; X=v=3Dcisco.com=3B=20h=3Dx2VOK/URLoBX55duy//nU8RGxVg=3D; b=da0NjqSIGQtGuiwGOXjONOa6aUAwrwZSmZOqSCxt3+Vss4JjLFj4CTOARm5Va36WBUULCSwv Du9ADHrxWyf1Zx1TUlM2QENvD+jUexS0AgOOIjV61V7+3zMeYe5nKs/4; Authentication-Results: rtp-dkim-2.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: Subject: [Enum] New I-D on usage of phone numbers in SIP [DO NOT REPLY!] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org PLEASE DO NOT REPLY TO THIS POST. My apologies for the cross post. I have submitted the following I-D: http://www.ietf.org/internet-drafts/draft-rosenberg-rai-phone-names-numbers-00.txt I gave it a -rai moniker since it touches on issues central to at least four working groups. If you are interested in discussion this document, please let us do so only on sipping@ietf.org. The document proposes a framework and architecture for the usage of phone numbers with SIP. It tries to answer questions like the difference between a tel URI and SIP URI with user=phone, when to use each, what the meaning of concepts like LNP and freephone are in a pure-SIP world, the architectural role of ENUM, and impacts on PSTN interoperability, and so on. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 18 19:46:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaL6Q-0003Qy-JO; Wed, 18 Oct 2006 19:45:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaJ5q-0001ZM-Mc for enum@ietf.org; Wed, 18 Oct 2006 17:36:54 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaI1P-0000F2-2o for enum@ietf.org; Wed, 18 Oct 2006 16:28:25 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9IK2P4A019902 for ; Wed, 18 Oct 2006 13:02:31 -0700 From: "Richard Shockey" To: Date: Wed, 18 Oct 2006 16:02:03 -0400 Message-ID: <03e401c6f2f0$48af7910$50201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acby8Ec42mo6uzQ0RFCBYT8G29IGOg== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff Subject: [Enum] Preliminary ENUM Agenda #2 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Agenda of the 67th IETF Meeting PRELIMINARY #2 : IETF 67 San Diego Telephone Number Mapping (ENUM) WG Agenda MONDAY, November 6, 2006 0800-1800 IETF Registration - Harbor Island Foyer 0800-0900 Continental Breakfast - Grande Ballroom Foyer 1130-1300 Break 1300-1500 Afternoon Session I Grande RAI enum Telephone Number Mapping WG Ballroom A Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alexander Mayrhofer RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com RAI Area Advisor: Jon Peterson Review of Agenda 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 2. Experience draft finalization? 3. Title : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) Author(s) : P. Faltstrom Filename : draft-ietf-enum-3761bis-00.txt Pages : 18 Date : 2006-10-18 This document discusses the use of the Domain Name System (DNS) for storage of E.164 [E164] numbers, and resolving those to URIs that can be used for (for example) call setup. This include how DNS can be used for identifying available services connected to one E.164 number. It obsoletes RFC 3761 [RFC3761]. This version of the document (00) is not more than the start of a discussion for detailed changes 4. Title : The Uniform Resource Identifier (URI) DNS Resource Record Author(s) : P. Faltstrom, O. Kolkman Filename : draft-ietf-enum-uri-00.txt Pages : 11 Date : 2006-9-28 This document defines a new DNS resource record, called the Uniform Resource Identifier (URI) RR, for publishing mappings from hostnames to URIs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-uri-00.txt 5. Title : The ENUM Branch Location Record Author(s) : O. Lendl Filename : draft-lendl-enum-branch-location-record-02.txt Pages : 7 Date : 2006-6-26 This documents defines the ENUM Branch Location record which is used to indicate where the ENUM tree for special ENUM application is located. The primary application for the EBL is to enable a temporary solution for the infrastructure ENUM tree. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lendl-enum-branch-location-record- 02.txt 6. Title : Authentication Scheme for Public ENUM Applications Author(s) : C. Hui, et al. Filename : draft-chenh-enum-app-auth-00.txt Pages : 15 Date : 2006-10-9 ENUM possesses the feature of E.164 number authenticity, therefore by being carried with initiation signal of application services, ENUM number can be used to identify originer. The service initiation signal includes sender's (originer's) un- encrypted ENUM number and encrypted ENUM number, or some other information needed by specific applications, then receiver decrypts encrypted ENUM number and compares decrypted result with the un- encrypted ENUM number to authenticate the originer's identity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chenh-enum-app-auth-00.txt 7. Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-xmpp-00.txt Pages : 7 Date : 2006-10-2 This document requests IANA registration of an Enumservice for Extensible Messaging and Presence Protocol (XMPP) Uniform Resource Identifiers (URIs) according to the registration procedure outlined in RFC 3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt 8. Title : IANA Registration for Enumservice foaf Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-01.txt Pages : 8 Date : 2006-8-17 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). Information collected from FOAF can be used before, during or after a communication is established. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-01.txt 9. Enumservices Guide? 10. Infrastructure ENUM root discussion ???? Open Session . Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 19 14:56:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gad3R-0007Rv-4J; Thu, 19 Oct 2006 14:55:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gad3P-0007Rl-Q4 for enum@ietf.org; Thu, 19 Oct 2006 14:55:43 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gad3O-0007kx-Cs for enum@ietf.org; Thu, 19 Oct 2006 14:55:43 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9JItc4x029515 for ; Thu, 19 Oct 2006 11:55:44 -0700 From: "Richard Shockey" To: Date: Thu, 19 Oct 2006 14:55:16 -0400 Message-ID: <164d01c6f3b0$215ca070$50201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AcbzBcmkJHKx/ECCRt+JiOrYlbas/QAqkMow X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Subject: [Enum] FW: I-D ACTION:draft-lim-kim-enum-based-softswitch-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Wednesday, October 18, 2006 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-lim-kim-enum-based-softswitch-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : ENUM-based Softswitch Requirement > Author(s) : J. Lim, W. Kim > Filename : draft-lim-kim-enum-based-softswitch-00.txt > Pages : 6 > Date : 2006-10-18 > > This document describes simple requirement for softswitch, which use > ENUM DNS to route a call on VoIP service. This requirement is one of > interim solution to maintain stability of on-going commercial > softswitch system while initial stage of ENUM service that does not > have sufficient data. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-lim-kim-enum-based-softswitch- > 00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@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-lim-kim-enum-based-softswitch-00.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@ietf.org. > In the body type: > "FILE /internet-drafts/draft-lim-kim-enum-based-softswitch-00.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@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 19 15:24:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadUf-0005Rg-Gy; Thu, 19 Oct 2006 15:23:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadUe-0005Na-6P; Thu, 19 Oct 2006 15:23:52 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GadUc-0003xD-RP; Thu, 19 Oct 2006 15:23:52 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Oct 2006 12:23:51 -0700 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JJNotj004329; Thu, 19 Oct 2006 15:23:50 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k9JJNlYP028366; Thu, 19 Oct 2006 15:23:50 -0400 (EDT) Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:23:49 -0400 Received: from [161.44.55.227] ([161.44.55.227]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:23:48 -0400 Message-ID: <4537D0C4.5020105@cisco.com> Date: Thu, 19 Oct 2006 15:23:48 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: avt@ietf.org, ecrit@ietf.org, enum@ietf.org, geopriv@ietf.org, ieprep@ietf.org, iptel@ietf.org, mmusic@ietf.org, sigtran@ietf.org, simple@ietf.org, sip@ietf.org, sipping@ietf.org, speechsc@ietf.org, speermint@ietf.org, xcon@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2006 19:23:48.0914 (UTC) FILETIME=[1A653120:01C6F3B4] DKIM-Signature: a=rsa-sha1; q=dns; l=1561; t=1161285830; x=1162149830; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:ICE=20Tutorial=20during=20IETF=2067!=20[DO=20NOT=20REPLY] |To:avt@ietf.org, =20ecrit@ietf.org, =20enum@ietf.org, =20geopriv@ietf.org, =0A= 20=20=20=20=20=20=20=20ieprep@ietf.org, =20iptel@ietf.org, =20mmusic@ietf.org , =20sigtran@ietf.org, =0A=20=20=20=20=20=20=20=20simple@ietf.org, =20sip@ietf .org, =20sipping@ietf.org, =20speechsc@ietf.org, =0A=20=20=20=20=20=20=20=20sp eermint@ietf.org,=20xcon@ietf.org; X=v=3Dcisco.com=3B=20h=3DIVH9amnYVaV4pfzKKjl/WmQt0Lg=3D; b=KrOzK3fR06ATri/gT7YJZroJcol7TSpMYe5BZE33gFcC/1PSyZC+oxmWK+oIC+fJQIbVoFL+ nf48uscnxvpV77HTZ0nnFeZmJMX4MuuOimxi0aG7+C8ixmvrHWsG0fmT; Authentication-Results: rtp-dkim-1.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 1.2 (+) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: Subject: [Enum] ICE Tutorial during IETF 67! [DO NOT REPLY] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org (Apologies to multiple recipients) (DO NOT REPLY) WHAT: Tutorial on Interactive Connectivity Establishment (ICE) (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt) WHEN: Tuesday, November 7 1130-1300 (lunch logistics are in progress and will be announced ASAP) WHERE: Grande Ballroom A WHO: Anyone with an interest in RAI work that would like to learn more about ICE. WHY: ICE is one of the 'core' SIP specifications (according to the SIP hitchhikers guide) and seeing some good adoption. It's the IETF tool for NAT traversal for SIP-based media. However, it's a complex specification. The tutorial will assume only basic familiarity with SIP, SDP and NAT, and explain the rest. Participants will emerge with a high level understanding of the operation of ICE. The tutorial will be based on the pending -12 version. RSVP: Please send a note to me with the Subject line "ice-is-nice" (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a count of the number of participants for lunch purposes. !DO NOT REPLY TO THIS NOTE! -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 19 15:30:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadbM-0007rB-DN; Thu, 19 Oct 2006 15:30:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GadbL-0007r1-LR for enum@ietf.org; Thu, 19 Oct 2006 15:30:47 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GadbK-00059c-BK for enum@ietf.org; Thu, 19 Oct 2006 15:30:47 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Oct 2006 12:30:47 -0700 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JJUk2M006590 for ; Thu, 19 Oct 2006 15:30:46 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9JJUkDM006881 for ; Thu, 19 Oct 2006 15:30:46 -0400 (EDT) Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:30:45 -0400 Received: from [161.44.55.227] ([161.44.55.227]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 15:30:45 -0400 Message-ID: <4537D265.6050802@cisco.com> Date: Thu, 19 Oct 2006 15:30:45 -0400 From: Jonathan Rosenberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: enum@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2006 19:30:45.0792 (UTC) FILETIME=[12DFBA00:01C6F3B5] DKIM-Signature: a=rsa-sha1; q=dns; l=1561; t=1161286246; x=1162150246; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:Jonathan=20Rosenberg=20 |Subject:ICE=20Tutorial=20during=20IETF=2067!=20[DO=20NOT=20REPLY] |To:enum@ietf.org; X=v=3Dcisco.com=3B=20h=3DIVH9amnYVaV4pfzKKjl/WmQt0Lg=3D; b=iXuV3fnFVWOoZxudgpo0AbHmqw03BRr+Mj8mGARHB2US1hpp1uK6GE7CXUr4hBUZNJ8zYFWM fdS1r0pRz2rCrwvHFvCDY+SImLPnDmpBgclXWPg5jJCPVQYZceLoZIqr; Authentication-Results: rtp-dkim-1.cisco.com; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Subject: [Enum] ICE Tutorial during IETF 67! [DO NOT REPLY] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org (Apologies to multiple recipients) (DO NOT REPLY) WHAT: Tutorial on Interactive Connectivity Establishment (ICE) (http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-11.txt) WHEN: Tuesday, November 7 1130-1300 (lunch logistics are in progress and will be announced ASAP) WHERE: Grande Ballroom A WHO: Anyone with an interest in RAI work that would like to learn more about ICE. WHY: ICE is one of the 'core' SIP specifications (according to the SIP hitchhikers guide) and seeing some good adoption. It's the IETF tool for NAT traversal for SIP-based media. However, it's a complex specification. The tutorial will assume only basic familiarity with SIP, SDP and NAT, and explain the rest. Participants will emerge with a high level understanding of the operation of ICE. The tutorial will be based on the pending -12 version. RSVP: Please send a note to me with the Subject line "ice-is-nice" (mailto:jdrosen@cisco.com?Subject=ice-is-nice) so I can get a count of the number of participants for lunch purposes. !DO NOT REPLY TO THIS NOTE! -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Cisco Fellow Parsippany, NJ 07054-2711 Cisco Systems jdrosen@cisco.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 19 16:57:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gaew6-0000pH-RW; Thu, 19 Oct 2006 16:56:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gaew4-0000aE-VA for enum@ietf.org; Thu, 19 Oct 2006 16:56:17 -0400 Received: from pb94.dyndns.org ([213.239.207.29]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaWWy-00043x-22 for enum@ietf.org; Thu, 19 Oct 2006 07:57:49 -0400 Received: from [10.10.0.50] (nat.labs.nic.at [83.136.33.3]) by pb94.dyndns.org (Postfix) with ESMTP id CE313210019 for ; Thu, 19 Oct 2006 13:57:29 +0200 (CEST) Message-ID: <4537682A.9010502@pernau.at> Date: Thu, 19 Oct 2006 13:57:30 +0200 From: Klaus Darilion User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: enum@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Subject: [Enum] comments on draft-ietf-enum-3761bis-00 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Patrik! It would be great if the draft would be correct formated - that would ease reading a lot. Now to the draft: > 1.2. Use for these mechanisms for private dialing plans > > This document describes the operation of these mechanisms in the > context of numbers allocated according to the ITU-T recommendation > E.164. The same mechanisms might be used for private dialing plans. > If these mechanisms are re-used, the suffix used for the private > dialing plan MUST NOT be e164.arpa, to avoid conflict with this > specification. Parties to the private dialing plan will need to the > suffix used by their private dialing plan for correct operation of > these mechanisms. Further, the application unique string used SHOULD > be the full number as specified, but without the leading '+', and > such private use MUST NOT be called "ENUM". To me it is not clear what this section addresses. Does it address "private ENUM" too? Private ENUM is usually used to have the official dialing plans in private scenarios. Thus removing the '+' is IMO not good. Further, I'm not sure if an RFC should dictate usage of ENUM in private scenarios. A private scenario is private - it could use the RFC suggestions or not. >2. The ENUM Application Specifications > ... > the risk that collisions between E.164 numbers and non-E.164 numbers > can occur. To mitigate this risk, the E2U portion of the service > field MUST NOT be used for non-E.164 numbers. I do not understand what this means. If an application incorrectly translates a dial string into an E.164 number, there is no difference than if the user would have typed a wrong number. Further, this draft is about ENUM - E.164 to .... Thus, I always thought per definition there can not be non E.164 numbers in e164.arpa. > 4.1. Example Really nice formated :-| > $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. > > NAPTR 10 100 ( > "u" ^^^^ I guess you mean "d" ? > "E2U+sip" > "" > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. ) > > NAPTR 10 101 ( > "u" ^^^^ I guess you mean "d" ? > "E2U+h323" > "" > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. ^^^^ missing closing parenthesis > > NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@example.com!" . > > _sip._e2u IN URI 10 10 "sip:info@example.com" > _h323._e2u IN URI 10 10 "h323:info@example.com" > _msg._e2u IN URI 10 10 "mailto:info@example.com" IMO this example is very bad. It does not work with RFC3761 compliant resolvers. There should be also "u" NAPTRs to be compatible with old ENUM resolvers. Further, the whole draft does not mention compatibility with RFC 3761. Using "d" NAPTRs breaks all existing ENUM applications as resolvers don't understand it. I expect a least a section which discusses the compatibility issues, and reflect this discussion in the examples (similar the compatibility issues in RFC 3263). I further miss a discussion about the difference of "u" and "d", and suggestion when they should be used. And why Another important thing is that URI RRs can't be used with open dialing plans. Currently open dialing plans require the usage of wildcard NAPTRs. Introducing URI RRs will not allow to use wildcard NAPTRs. IMO this is an important aspect and should be mentioned in the draft. regards klaus _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 19 17:16:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GafFG-0003Zm-CN; Thu, 19 Oct 2006 17:16:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GafFF-0003Yn-Ru for enum@ietf.org; Thu, 19 Oct 2006 17:16:05 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GafFE-0003uK-GO for enum@ietf.org; Thu, 19 Oct 2006 17:16:05 -0400 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 19 Oct 2006 14:16:04 -0700 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9JLG4EJ014795; Thu, 19 Oct 2006 17:16:04 -0400 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9JLG3DM005682; Thu, 19 Oct 2006 17:16:03 -0400 (EDT) Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Oct 2006 17:16:03 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] comments on draft-ietf-enum-3761bis-00 Date: Thu, 19 Oct 2006 17:16:00 -0400 Message-ID: <072C5B76F7CEAB488172C6F64B30B5E30211FC2F@xmb-rtp-20b.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] comments on draft-ietf-enum-3761bis-00 Thread-Index: AcbzwUCU62JXKTaUSm65ypHqHzOpcwAAertw From: "Michael Hammer \(mhammer\)" To: "Klaus Darilion" , X-OriginalArrivalTime: 19 Oct 2006 21:16:03.0682 (UTC) FILETIME=[C8A13C20:01C6F3C3] DKIM-Signature: a=rsa-sha1; q=dns; l=4618; t=1161292564; x=1162156564; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mhammer@cisco.com; z=From:=22Michael=20Hammer=20\(mhammer\)=22=20 |Subject:RE=3A=20[Enum]=20comments=20on=20draft-ietf-enum-3761bis-00 |To:=22Klaus=20Darilion=22=20, =20; X=v=3Dcisco.com=3B=20h=3DU3uubL5BjAAxYyhPZ11uIniaVMU=3D; b=XTN/NeVXtH++GDajpekLtJvjnYDE30vHJaIpsppKTO3zrbwJVIcmGPFqFy6hnJfT6KGazF7Q 9h6aQ/NiqeWI3nHwPK9dwmjl8MXeYf9c5xDW19bmesETRzuPOcKaOLrN; Authentication-Results: rtp-dkim-1.cisco.com; header.From=mhammer@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Klaus, If one uses e164.arpa as domain suffix, then you must use only E.164 numbers as input. If one wants other than E.164 number as input, then use another domain suffix and don't use "+" as private number prefix. If one violates the above, collisions and bad things happen. :) Mike =20 > -----Original Message----- > From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at]=20 > Sent: Thursday, October 19, 2006 7:58 AM > To: enum@ietf.org > Subject: [Enum] comments on draft-ietf-enum-3761bis-00 >=20 > Hi Patrik! >=20 > It would be great if the draft would be correct formated -=20 > that would ease reading a lot. >=20 > Now to the draft: >=20 >=20 > > 1.2. Use for these mechanisms for private dialing plans > >=20 > > This document describes the operation of these mechanisms in the=20 > > context of numbers allocated according to the ITU-T recommendation=20 > > E.164. The same mechanisms might be used for private dialing plans. > > If these mechanisms are re-used, the suffix used for the private=20 > > dialing plan MUST NOT be e164.arpa, to avoid conflict with this=20 > > specification. Parties to the private dialing plan will need to the=20 > > suffix used by their private dialing plan for correct operation of=20 > > these mechanisms. Further, the application unique string=20 > used SHOULD=20 > > be the full number as specified, but without the leading=20 > '+', and such=20 > > private use MUST NOT be called "ENUM". >=20 > To me it is not clear what this section addresses. Does it=20 > address "private ENUM" too? Private ENUM is usually used to=20 > have the official dialing plans in private scenarios. Thus=20 > removing the '+' is IMO not good. >=20 > Further, I'm not sure if an RFC should dictate usage of ENUM=20 > in private scenarios. A private scenario is private - it=20 > could use the RFC suggestions or not. >=20 > >2. The ENUM Application Specifications > >=20 > ... > > the risk that collisions between E.164 numbers and=20 > non-E.164 numbers=20 > > can occur. To mitigate this risk, the E2U portion of the=20 > service field=20 > > MUST NOT be used for non-E.164 numbers. >=20 > I do not understand what this means. If an application=20 > incorrectly translates a dial string into an E.164 number,=20 > there is no difference than if the user would have typed a=20 > wrong number. >=20 > Further, this draft is about ENUM - E.164 to .... > Thus, I always thought per definition there can not be non=20 > E.164 numbers in e164.arpa. >=20 > > 4.1. Example >=20 > Really nice formated :-| >=20 > > $ORIGIN 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. > >=20 > > NAPTR 10 100 ( > > "u" >=20 > ^^^^ > I guess you mean "d" ? >=20 > > "E2U+sip" > > "" > > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. ) > >=20 > > NAPTR 10 101 ( > > "u" > ^^^^ > I guess you mean "d" ? >=20 > > "E2U+h323" > > "" > > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. >=20 > ^^^^ > missing closing parenthesis > >=20 > > NAPTR 10 102 "u" "E2U+msg"=20 > "!^.*$!mailto:info@example.com!" . > > > > _sip._e2u IN URI 10 10 "sip:info@example.com" > > _h323._e2u IN URI 10 10 "h323:info@example.com" > > _msg._e2u IN URI 10 10 "mailto:info@example.com" >=20 >=20 > IMO this example is very bad. It does not work with RFC3761=20 > compliant resolvers. There should be also "u" NAPTRs to be=20 > compatible with old ENUM resolvers. >=20 > Further, the whole draft does not mention compatibility with=20 > RFC 3761.=20 > Using "d" NAPTRs breaks all existing ENUM applications as=20 > resolvers don't understand it. >=20 > I expect a least a section which discusses the compatibility=20 > issues, and reflect this discussion in the examples (similar=20 > the compatibility issues in RFC 3263). >=20 > I further miss a discussion about the difference of "u" and=20 > "d", and suggestion when they should be used. And why >=20 > Another important thing is that URI RRs can't be used with=20 > open dialing plans. Currently open dialing plans require the=20 > usage of wildcard NAPTRs. Introducing URI RRs will not allow=20 > to use wildcard NAPTRs. IMO this is an important aspect and=20 > should be mentioned in the draft. >=20 > regards > klaus >=20 > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum >=20 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 20 10:23:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GavGW-00079L-Ft; Fri, 20 Oct 2006 10:22:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GavGV-00078O-1z for enum@ietf.org; Fri, 20 Oct 2006 10:22:27 -0400 Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GavGQ-0007xh-Qe for enum@ietf.org; Fri, 20 Oct 2006 10:22:27 -0400 Received: from [172.16.10.86] ([::ffff:208.50.38.5]) (AUTH: PLAIN anewton, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Fri, 20 Oct 2006 10:21:44 -0400 id 01588116.4538DB78.0000598D Message-ID: <4538DB84.4060106@hxr.us> Date: Fri, 20 Oct 2006 10:21:56 -0400 From: Andrew Newton User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Klaus Darilion Subject: Re: [Enum] comments on draft-ietf-enum-3761bis-00 References: <4537682A.9010502@pernau.at> In-Reply-To: <4537682A.9010502@pernau.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Klaus Darilion wrote: > To me it is not clear what this section addresses. Does it address > "private ENUM" too? Private ENUM is usually used to have the official > dialing plans in private scenarios. Thus removing the '+' is IMO not good. I think it is saying "don't expect to see private dialing plans in e164.arpa." That seems right to me. I don't think it saying anything about using private dialing plans in private ENUM trees or even E.164 numbers in private ENUM trees (or does the FCC have jurisdiction over that!!! :) ). > Another important thing is that URI RRs can't be used with open dialing > plans. Currently open dialing plans require the usage of wildcard > NAPTRs. Introducing URI RRs will not allow to use wildcard NAPTRs. IMO > this is an important aspect and should be mentioned in the draft. Agreed. A DNS wildcard for the NAPTR way and a DNS wildcard for the URI way do very different things here (from an ENUM perspective). And then there's the .* that can be done in the NAPTR regex. I'm curious about backwards compatibility too. Many of us are already vexed with having to query multiple ENUM trees. Issuing two queries per tree, one for NAPTR and one for URI, makes that problem twice as expensive. Am I missing something? -andy _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 23 03:06:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gbtsr-0000qZ-0f; Mon, 23 Oct 2006 03:06:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GbtsK-0008NB-GV; Mon, 23 Oct 2006 03:05:32 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GbtdK-0005wL-LS; Mon, 23 Oct 2006 02:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 9AFC026E5C; Mon, 23 Oct 2006 06:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GbtdK-0006Rr-GV; Mon, 23 Oct 2006 02:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 23 Oct 2006 02:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-combined-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart 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 : Combined User and Infrastructure ENUM in the e164.arpa tree Author(s) : M. Haberler, R. Stastny Filename : draft-ietf-enum-combined-01.txt Pages : 11 Date : 2006-10-22 This memo defines an interim solution for Infrastructure ENUM to allow a combined User and Infrastructure ENUM implementation in e164.arpa as a national choice until the long-term solution is approved. This interim solution will be deprecated after deployment of the long-term solution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-combined-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-combined-01.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-combined-01.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-22181226.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-combined-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-combined-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-22181226.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon Oct 23 14:51:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc4t5-0000fp-4F; Mon, 23 Oct 2006 14:51:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc4t3-0000dr-PH for enum@ietf.org; Mon, 23 Oct 2006 14:51:01 -0400 Received: from central.switch.ch ([130.59.11.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc4sn-0002aD-5S for enum@ietf.org; Mon, 23 Oct 2006 14:51:01 -0400 Received: from machb.switch.ch ([130.59.6.129]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1Gc4sJ-0003Y3-00; Mon, 23 Oct 2006 20:50:15 +0200 Date: Mon, 23 Oct 2006 20:50:08 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: Richard Shockey Subject: Re: [Enum] Preliminary ENUM agenda ... In-Reply-To: <005a01c6ee16$ca208d60$4a201f0a@cis.neustar.com> Message-ID: References: <005a01c6ee16$ca208d60$4a201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Rich! On Thu, 12 Oct 2006, Richard Shockey wrote: > Agenda of the 67th IETF Meeting > > [...] > > Enumservices Guide? We have just submitted an updated version. It still contains quite a bit of open issues. I think we should solve at least some of those during the ENUM meeting in San Diego. cheers, Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 23 16:26:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc6Lx-000639-2q; Mon, 23 Oct 2006 16:24:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gc6Lw-00062U-9r for enum@ietf.org; Mon, 23 Oct 2006 16:24:56 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gc6Le-0008Ow-MI for enum@ietf.org; Mon, 23 Oct 2006 16:24:56 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9NKOeYi005454; Mon, 23 Oct 2006 13:24:45 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" Subject: RE: [Enum] Preliminary ENUM agenda ... Date: Mon, 23 Oct 2006 16:24:23 -0400 Message-ID: <018b01c6f6e1$3b5ec960$75201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: Thread-Index: Acb21DsA6GYkErM3R0aDgwI8EuwwHwADOUOw X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > -----Original Message----- > From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] > Sent: Monday, October 23, 2006 2:50 PM > To: Richard Shockey > Cc: enum@ietf.org > Subject: Re: [Enum] Preliminary ENUM agenda ... > > Hi Rich! > > On Thu, 12 Oct 2006, Richard Shockey wrote: > > > Agenda of the 67th IETF Meeting > > > > [...] > > > > Enumservices Guide? > > We have just submitted an updated version. It still contains quite > a bit of open issues. I think we should solve at least some of those > during the ENUM meeting in San Diego. So do I .... send a note to the list on what you think the open issues really are .. > > cheers, > Bernie > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Oct 25 15:51:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcom7-0004h1-Es; Wed, 25 Oct 2006 15:50:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcolH-0003nf-OZ; Wed, 25 Oct 2006 15:50:03 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcolG-0007or-Rj; Wed, 25 Oct 2006 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 9038826E4E; Wed, 25 Oct 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GcolG-0004oS-AA; Wed, 25 Oct 2006 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 25 Oct 2006 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-iax-01.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart 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 : IANA Registration for IAX Enumservice Author(s) : E. Guy Filename : draft-ietf-enum-iax-01.txt Pages : 14 Date : 2006-10-25 This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' 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-ietf-enum-iax-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-iax-01.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-iax-01.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-25111416.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-iax-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-iax-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-25111416.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Thu Oct 26 04:50:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0v4-0001Rh-DD; Thu, 26 Oct 2006 04:48:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd0v2-0001QS-Vg for enum@ietf.org; Thu, 26 Oct 2006 04:48:56 -0400 Received: from central.switch.ch ([130.59.11.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd0uy-0008Vi-LO for enum@ietf.org; Thu, 26 Oct 2006 04:48:56 -0400 Received: from machb.switch.ch ([130.59.6.129]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1Gd0uU-0006xm-00; Thu, 26 Oct 2006 10:48:22 +0200 Date: Thu, 26 Oct 2006 10:48:18 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: Richard Shockey In-Reply-To: <018b01c6f6e1$3b5ec960$75201f0a@cis.neustar.com> Message-ID: References: <018b01c6f6e1$3b5ec960$75201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Cc: enum@ietf.org Subject: [Enum] Open Issues draft-ietf-enum-enumservices-guide-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Rich et al. On Mon, 23 Oct 2006, Richard Shockey wrote: >>> Enumservices Guide? >> >> We have just submitted an updated version. It still contains quite >> a bit of open issues. I think we should solve at least some of those >> during the ENUM meeting in San Diego. > > > So do I .... send a note to the list on what you think the open issues > really are .. We have listed the Open Issues (and ToDo's) in an appendix session of the latest version, which is in the I-D queue to be published. In the meantime you can download it from: http://ietf.hoeneisen.ch/draft-ietf-enum-enumservices-guide-02.txt http://ietf.hoeneisen.ch/draft-ietf-enum-enumservices-guide-02.html In the following some of the open issues for the WG to think about: i1) Document status and dependencies: o Clarify Status of document. Is BCP adequate? o Clarify dependencies and collisions with RFC 3761. Should this document update RFC 3761? o Clarify dependencies of general security and privacy considerations (which apply to all Enumservices) and write them down. i2) Type / Subtype / URI schemes o Write more about how to choose type/subtype/etc. o More about Subtype applicability. o Clarify Relation between Subtypes and URI schemes o Clarify mixing subtyped / non subtyped for a type o Extension of an existing Enumservice. i3) IANA impact o Clarify IANA impact of this document. i4) Experimental Enumservices o Clarify whether experimental Enumservices should be described herein. More detailed descriptions will follow, either shortly before San Diego or during the ENUM WG there. Have fun! cheers, Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Oct 26 07:35:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd3VY-0006Er-PF; Thu, 26 Oct 2006 07:34:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd3VX-0006EP-DS; Thu, 26 Oct 2006 07:34:47 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcq3y-0005I1-Rf; Wed, 25 Oct 2006 17:13:26 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gcpjy-0004ng-7z; Wed, 25 Oct 2006 16:52:46 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 11F9C175D1; Wed, 25 Oct 2006 19:50:04 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GcolH-0004qz-KX; Wed, 25 Oct 2006 15:50:03 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 25 Oct 2006 15:50:03 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-enumservices-guide-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart 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 : Guide and Template for IANA Registrations of Enumervices Author(s) : J. Livingood, et al. Filename : draft-ietf-enum-enumservices-guide-02.txt Pages : 16 Date : 2006-10-25 This document provides a guide to and template for the creation of new IANA registration of ENUM services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@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-enumservices-guide-02.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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-enumservices-guide-02.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-10-25122306.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-enumservices-guide-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-enumservices-guide-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-25122306.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Thu Oct 26 10:04:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd5q6-0000Ra-1H; Thu, 26 Oct 2006 10:04:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gd5q4-0000ID-9r for enum@ietf.org; Thu, 26 Oct 2006 10:04:08 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gd5q0-0000QN-LV for enum@ietf.org; Thu, 26 Oct 2006 10:04:08 -0400 Received: from RSHOCKEYLTXP (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k9QE42gQ014079 for ; Thu, 26 Oct 2006 07:04:09 -0700 From: "Richard Shockey" To: Date: Thu, 26 Oct 2006 10:03:40 -0400 Message-ID: <037301c6f907$8e512e10$75201f0a@cis.neustar.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: Acb5B4m1ftbPtmA/SA6qK5mwdOn+HA== X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 6907f330301e69261fa73bed91449a20 Subject: [Enum] ALMOST Final Agenda ENUM WG IETF 67 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org FINAL : IETF 67 San Diego Telephone Number Mapping (ENUM) WG Agenda MONDAY, November 6, 2006 0800-1800 IETF Registration - Harbor Island Foyer 0800-0900 Continental Breakfast - Grande Ballroom Foyer 1130-1300 Break 1300-1500 Afternoon Session I Grande RAI enum Telephone Number Mapping WG Ballroom A Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alexander Mayrhofer RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com RAI Area Advisor: Jon Peterson Review of Agenda 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 2. Experience draft finalization? CORE PROTOCOL DISCUSSION 15+ 3. Title : The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) Author(s) : P. Faltstrom Filename : draft-ietf-enum-3761bis-00.txt Pages : 18 Date : 2006-10-18 This document discusses the use of the Domain Name System (DNS) for storage of E.164 [E164] numbers, and resolving those to URIs that can be used for (for example) call setup. This include how DNS can be used for identifying available services connected to one E.164 number. It obsoletes RFC 3761 [RFC3761]. This version of the document (00) is not more than the start of a discussion for detailed changes 4. Title : The Uniform Resource Identifier (URI) DNS Resource Record Author(s) : P. Faltstrom, O. Kolkman Filename : draft-ietf-enum-uri-00.txt Pages : 11 Date : 2006-9-28 This document defines a new DNS resource record, called the Uniform Resource Identifier (URI) RR, for publishing mappings from hostnames to URIs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-uri-00.txt NEW BUSINESS 5. Title : ENUM-based Softswitch Requirement Author(s) : J. Lim, W. Kim Filename : draft-lim-kim-enum-based-softswitch-00.txt Pages : 6 Date : 2006-10-18 This document describes simple requirement for softswitch, which use ENUM DNS to route a call on VoIP service. This requirement is one of interim solution to maintain stability of on-going commercial softswitch system while initial stage of ENUM service that does not have sufficient data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lim-kim-enum-based-softswitch-00.t xt 6. Title : Authentication Scheme for Public ENUM Applications Author(s) : C. Hui, et al. Filename : draft-chenh-enum-app-auth-00.txt Pages : 15 Date : 2006-10-9 ENUM possesses the feature of E.164 number authenticity, therefore by being carried with initiation signal of application services, ENUM number can be used to identify originer. The service initiation signal includes sender's (originer's) un- encrypted ENUM number and encrypted ENUM number, or some other information needed by specific applications, then receiver decrypts encrypted ENUM number and compares decrypted result with the un- encrypted ENUM number to authenticate the originer's identity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chenh-enum-app-auth-00.txt 7. Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-xmpp-00.txt Pages : 7 Date : 2006-10-2 This document requests IANA registration of an Enumservice for Extensible Messaging and Presence Protocol (XMPP) Uniform Resource Identifiers (URIs) according to the registration procedure outlined in RFC 3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-xmpp-00.txt 8. Title : The ENUM Branch Location Record Author(s) : O. Lendl Filename : draft-lendl-enum-branch-location-record-02.txt Pages : 7 Date : 2006-6-26 This documents defines the ENUM Branch Location record which is used to indicate where the ENUM tree for special ENUM application is located. The primary application for the EBL is to enable a temporary solution for the infrastructure ENUM tree. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lendl-enum-branch-location-record- 02.txt 9. Title : IANA Registration for Enumservice foaf Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-01.txt Pages : 8 Date : 2006-8-17 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). Information collected from FOAF can be used before, during or after a communication is established. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-01.txt STATUS REPORT ??? 10. Title : IANA Registration for IAX Enumservice Author(s) : E. Guy Filename : draft-ietf-enum-iax-01.txt Pages : 14 Date : 2006-10-25 This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' 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-ietf-enum-iax-01.txt 11 . STATUS REPORT ISSUES DISCUSSION Enumservices Guide 10 M Title : Guide and Template for IANA Registrations of Enumervices Author(s) : J. Livingood, et al. Filename : draft-ietf-enum-enumservices-guide-02.txt Pages : 16 Date : 2006-10-25 This document provides a guide to and template for the creation of new IANA registration of ENUM services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-02.tx t 11. Infrastructure ENUM root discussion 10-20 M 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 : Combined User and Infrastructure ENUM in the e164.arpa tree Author(s) : M. Haberler, R. Stastny Filename : draft-ietf-enum-combined-01.txt Pages : 11 Date : 2006-10-22 This memo defines an interim solution for Infrastructure ENUM to allow a combined User and Infrastructure ENUM implementation in e164.arpa as a national choice until the long-term solution is approved. This interim solution will be deprecated after deployment of the long-term solution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-combined-01.txt Open Session . Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 27 04:29:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdN4X-00076N-3l; Fri, 27 Oct 2006 04:28:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdN4W-00076I-Au for enum@ietf.org; Fri, 27 Oct 2006 04:28:12 -0400 Received: from arachne.bofh.priv.at ([193.154.150.108] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdN4U-0000HV-0R for enum@ietf.org; Fri, 27 Oct 2006 04:28:12 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id 54BE31A378; Fri, 27 Oct 2006 10:28:04 +0200 (CEST) Date: Fri, 27 Oct 2006 10:28:04 +0200 From: Otmar Lendl To: Richard Shockey Subject: Re: [Enum] ALMOST Final Agenda ENUM WG IETF 67 Message-ID: <20061027082803.GA30734@nic.at> References: <037301c6f907$8e512e10$75201f0a@cis.neustar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <037301c6f907$8e512e10$75201f0a@cis.neustar.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On 2006/10/26 16:10, Richard Shockey wrote: > > 8. Title : The ENUM Branch Location Record > Author(s) : O. Lendl > Filename : draft-lendl-enum-branch-location-record-02.txt > Pages : 7 > Date : 2006-6-26 > > This documents defines the ENUM Branch Location record which is used > to indicate where the ENUM tree for special ENUM application is > located. The primary application for the EBL is to enable a > temporary solution for the infrastructure ENUM tree. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-lendl-enum-branch-location-record- > 02.txt The current version is draft-ietf-enum-branch-location-record-00.txt, from August 2, 2006, located at http://www.ietf.org/internet-drafts/draft-ietf-enum-branch-location-record-00.txt /ol -- < Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Oct 27 04:49:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNPE-0007Nd-IJ; Fri, 27 Oct 2006 04:49:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdNPD-0007NF-2P; Fri, 27 Oct 2006 04:49:35 -0400 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdNPB-00045u-EH; Fri, 27 Oct 2006 04:49:35 -0400 Received: from [10.10.0.63] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Fri, 27 Oct 2006 10:49:25 +0200 id 0007C0C1.4541C815.00004C09 Message-ID: <4541C78C.7060102@enum.at> Date: Fri, 27 Oct 2006 10:47:08 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: "'enum@ietf.org'" , speermint Content-Type: multipart/mixed; boundary="------------090300090303010705030003" X-Spam-Score: 0.2 (/) X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41 Cc: Subject: [Enum] [Fwd: Update to Internet-Draft and RFC Boilerplate] X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --------------090300090303010705030003 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit administrivia: there is a new boilerplate to be used for Internet Drafts. Draft authors might want to check their versions of xml2rfc and idnits. Alex --------------090300090303010705030003 Content-Type: message/rfc822; name="Update to Internet-Draft and RFC Boilerplate" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Update to Internet-Draft and RFC Boilerplate" Received: from megatron.ietf.org (stiedprmman1.ietf.ORG [::ffff:156.154.16.145]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Fri, 27 Oct 2006 03:27:02 +0200 id 0007C393.45416067.00001331 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdGOd-0002A4-Ez; Thu, 26 Oct 2006 21:20:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GdGOc-00029y-KL for ietf-announce@ietf.org; Thu, 26 Oct 2006 21:20:30 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GdGOc-0002Ag-I1 for ietf-announce@ietf.org; Thu, 26 Oct 2006 21:20:30 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GdGOc-0000MD-7H for ietf-announce@ietf.org; Thu, 26 Oct 2006 21:20:30 -0400 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id E68FF175E1 for ; Fri, 27 Oct 2006 01:19:59 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GdGO7-0007vB-Go for ietf-announce@ietf.org; Thu, 26 Oct 2006 21:19:59 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: IETF Announcement list Cc: From: IETF Chair Message-Id: Date: Thu, 26 Oct 2006 21:19:59 -0400 X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Subject: Update to Internet-Draft and RFC Boilerplate X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on pahula X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL, BAYES_00, UPPERCASE_25_50 autolearn=no version=3.0.3 A small update to BCP 78 was recently approved by the IESG as RFC 4748, to update the boilerplate (i.e., standard legal text) in RFCs and Internet-Drafts to recognize the IETF Trust as a rights holder, instead of ISOC. The actual boilerplate changes are given below this message. Starting as soon as reasonably possible, all authors of Internet-Drafts are requested to use the new boilerplate. The RFC Editor will in any case be inserting it in all RFCs issued from 2006-11-01. (The rights held by ISOC in older RFCs will be administratively transferred to the IETF Trust.) The public ID Nits checker already accepts I-Ds with old or new boilerplate. The Secretariat has started accepting I-Ds with old or new boilerplate XML2RFC version 1.32 will generate the new boilerplate. Users of I-D templates are requested to update them appropriately. http://www.ietf.org/ID-Checklist.html and http://www.ietf.org/ietf/1id-guidelines.html are being updated. Starting December, the public ID Nits checker will issue warnings for old boilerplate. Starting February 2007, the Secretariat will refuse the old boilerplate in Internet-Drafts. We are sorry for the inconvenience, but this change cannot be avoided. IETF Chair IETF Secretariat TOOLS Team -------- Copyright Notice (required for all IETF Documents) (Normally placed at the end of the IETF Document.) NOTE: by convention, the first line of the copyright statement is usually placed near the beginning of each document. This must also be updated. OLD "Copyright (C) The Internet Society (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. NEW "Copyright (C) The IETF Trust (year). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Disclaimer (required in all IETF Documents) (Normally placed at the end of the IETF Document after the copyright notice.) OLD "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." NEW "This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Exceptions In MIB modules, PIB modules and similar material commonly extracted from IETF Documents, except for material that is being placed under IANA maintenance, the following abbreviated notice shall be included in the body of the material that will be extracted in lieu of the notices otherwise required by Section 5: OLD "Copyright (C) The Internet Society . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." NEW "Copyright (C) The IETF Trust . This version of this MIB module is part of RFC XXXX; see the RFC itself for full legal notices." When the MIB or PIB module is the initial version of a module that is to be maintained by the IANA, the following abbreviated notice shall be included: OLD "Copyright (C) The Internet Society . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." NEW "Copyright (C) The IETF Trust . The initial version of this MIB module was published in RFC XXXX; for full legal notices see the RFC itself. Supplementary information may be available at: http://www.ietf.org/copyrights/ianamib.html." _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce --------------090300090303010705030003 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --------------090300090303010705030003-- From enum-bounces@ietf.org Sun Oct 29 15:40:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeHPd-0007wm-Cy; Sun, 29 Oct 2006 15:37:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeHPc-0007wh-7D for enum@ietf.org; Sun, 29 Oct 2006 15:37:44 -0500 Received: from sccrmhc11.comcast.net ([204.127.200.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeHPb-000762-1A for enum@ietf.org; Sun, 29 Oct 2006 15:37:44 -0500 Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc11) with ESMTP id <2006102920374001100ch3cfe>; Sun, 29 Oct 2006 20:37:40 +0000 Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id k9TKbcQg028361 for ; Sun, 29 Oct 2006 15:37:38 -0500 Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id k9TKbcJP028357; Sun, 29 Oct 2006 15:37:38 -0500 Date: Sun, 29 Oct 2006 15:37:38 -0500 Message-Id: <200610292037.k9TKbcJP028357@dragon.ariadne.com> To: enum@ietf.org From: Dale.Worley@comcast.net X-Spam-Score: 0.2 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [Enum] draft-ietf-enum-combined-01 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I was wondering about the example in section 7 of draft-ietf-enum-combined-01 -- the E.164 number is +44..., but the EBL record shown has domain name "infrastructure.3.4.e164.arpa", which would be for country code +43. Also, it occurs to me that the infrastructure ENUM records could be grouped under, say, "(country code).infrastructure.e164.arpa". That would require an additional DNS delegation for each country code with infrastructure ENUM, but the delegation would be authenticated the same way that user ENUM subtrees are currently delegated. Presumably there is a reason that this scheme is inferior to what is presented in the I-D, but I don't see any discussion of alternatives in the I-D. Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Oct 29 16:56:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeIcZ-0003uJ-Jc; Sun, 29 Oct 2006 16:55:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeIc5-00034U-T6 for enum@ietf.org; Sun, 29 Oct 2006 16:54:41 -0500 Received: from norman.insensate.co.uk ([213.152.49.123] helo=insensate.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeIc4-00038t-FM for enum@ietf.org; Sun, 29 Oct 2006 16:54:41 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id CD184809D4; Sun, 29 Oct 2006 21:54:39 +0000 (GMT) In-Reply-To: <200610292037.k9TKbcJP028357@dragon.ariadne.com> References: <200610292037.k9TKbcJP028357@dragon.ariadne.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5D696E74-B96B-4FFA-A8B2-31AA004EB278@insensate.co.uk> Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] draft-ietf-enum-combined-01 Date: Sun, 29 Oct 2006 21:54:38 +0000 To: Dale.Worley@comcast.net X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.1 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Dale, folks, Re. the examples - Yup - the EBL needs to be changed from +43 to +44 This is a reflection of a current issue with example telephone numbers: Ofcom has defined ranges of "telephone numbers for drama use" reserved in the U.K., so these tend to turn up in I-Ds/RFCs. Not all Countries have had the forethought to institute such ranges, so the Ofcom ones tend to turn up in I-Ds/RFCs as they will not be in service. [Whether International call attempts to these numbers work quite as expected is left as an exercise for the terminally bored - however, no-one will answer] (apologies in advance for lax description below - I hope you all get the point) ---- AFAICT, there is an IAB agreement for e164.arpa. with the ITU The ITU has defined (interim) procedures in place to delegate /assign control of .e164.arpa. to the appropriate member (i.e. the Country associated with the ). Defining the procedures for ..e164.arpa. will undoubtedly involve ITU study group 2, many trips to Geneva, and a great deal of time. Isn't dealing with the FCC hard enough? That's why the process of doing just that IS referenced in the I-D (as the "long term solution" [9]). Don't expect it to happen overnight, though. ---- all the best, Lawrence On 29 Oct 2006, at 20:37, Dale.Worley@comcast.net wrote: > I was wondering about the example in section 7 of > draft-ietf-enum-combined-01 -- the E.164 number is +44..., but the EBL > record shown has domain name "infrastructure.3.4.e164.arpa", which > would be for country code +43. > > Also, it occurs to me that the infrastructure ENUM records could be > grouped under, say, "(country code).infrastructure.e164.arpa". That > would require an additional DNS delegation for each country code with > infrastructure ENUM, but the delegation would be authenticated the > same way that user ENUM subtrees are currently delegated. Presumably > there is a reason that this scheme is inferior to what is presented in > the I-D, but I don't see any discussion of alternatives in the I-D. > > Dale > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Oct 29 17:50:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeJTt-0003nJ-0s; Sun, 29 Oct 2006 17:50:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeJOu-00066D-SM for enum@ietf.org; Sun, 29 Oct 2006 17:45:08 -0500 Received: from sccrmhc11.comcast.net ([204.127.200.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeJBH-0005lT-51 for enum@ietf.org; Sun, 29 Oct 2006 17:31:04 -0500 Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc11) with ESMTP id <2006102922310201100chjure>; Sun, 29 Oct 2006 22:31:02 +0000 Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id k9TMV2Qg031824 for ; Sun, 29 Oct 2006 17:31:02 -0500 Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id k9TMUqCj031817; Sun, 29 Oct 2006 17:30:52 -0500 Date: Sun, 29 Oct 2006 17:30:52 -0500 Message-Id: <200610292230.k9TMUqCj031817@dragon.ariadne.com> To: enum@ietf.org From: Dale.Worley@comcast.net In-reply-to: <5D696E74-B96B-4FFA-A8B2-31AA004EB278@insensate.co.uk> (lconroy@insensate.co.uk) Subject: Re: [Enum] draft-ietf-enum-combined-01 References: <200610292037.k9TKbcJP028357@dragon.ariadne.com> <5D696E74-B96B-4FFA-A8B2-31AA004EB278@insensate.co.uk> X-Spam-Score: 0.2 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org From: lconroy Defining the procedures for ..e164.arpa. will undoubtedly involve ITU study group 2, many trips to Geneva, and a great deal of time. Isn't dealing with the FCC hard enough? You're saying that doing such a delegation would require a further agreement with the ITU? That's why the process of doing just that IS referenced in the I-D (as the "long term solution" [9]). Perhaps the significance of "long term solution" could be spelled out in a bit more detail? Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Oct 29 18:28:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeK4Q-0000BU-RQ; Sun, 29 Oct 2006 18:28:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeK4P-0000BP-Gr for enum@ietf.org; Sun, 29 Oct 2006 18:28:01 -0500 Received: from shaun.rfc1035.com ([195.54.233.68]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GeK4O-0004HF-6H for enum@ietf.org; Sun, 29 Oct 2006 18:28:01 -0500 Received: from [195.54.233.69] (HELO [195.54.233.69]) by shaun.rfc1035.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 91085; Sun, 29 Oct 2006 23:27:48 +0000 In-Reply-To: <200610292230.k9TMUqCj031817@dragon.ariadne.com> References: <200610292037.k9TKbcJP028357@dragon.ariadne.com> <5D696E74-B96B-4FFA-A8B2-31AA004EB278@insensate.co.uk> <200610292230.k9TMUqCj031817@dragon.ariadne.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jim Reid Subject: Re: [Enum] draft-ietf-enum-combined-01 Date: Sun, 29 Oct 2006 23:27:47 +0000 To: Dale.Worley@comcast.net X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On Oct 29, 2006, at 22:30, Dale.Worley@comcast.net wrote: > Defining the procedures for > ..e164.arpa. will undoubtedly involve > ITU study group 2, many trips to Geneva, and a great deal of > time. Isn't dealing with the FCC hard enough? > > You're saying that doing such a delegation would require a further > agreement with the ITU? Yes, he surely is. Please look at the IANA Considerations Section of RFC3761. Then review the liaison statements and other documents between ITU-T, IAB and RIPE NCC. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Oct 30 04:36:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeTYC-0004jo-F1; Mon, 30 Oct 2006 04:35:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GeTMB-0003y5-Ee for enum@ietf.org; Mon, 30 Oct 2006 04:22:59 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GeT9v-0006r6-Ah for enum@ietf.org; Mon, 30 Oct 2006 04:10:22 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] draft-ietf-enum-combined-01 Date: Mon, 30 Oct 2006 10:09:27 +0100 Message-ID: <32755D354E6B65498C3BD9FD496C7D463C5212@oefeg-s04.oefeg.loc> In-Reply-To: <200610292230.k9TMUqCj031817@dragon.ariadne.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] draft-ietf-enum-combined-01 thread-index: Acb7rJcG9BDfTklHR7WZGPGMMiMesgAVcItQ From: "Stastny Richard" To: , X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Dale, thanx for detecting the typo, of course the entry should be infrastructure.4.4.e164.arpa > Perhaps the significance of "long term solution" could be spelled out > in a bit more detail? IMO the significance is spelled out enough in the last two paragraphs of the Introduction and the reason for introducing the interim solution in section 3. Regards Richard > -----Original Message----- > From: Dale.Worley@comcast.net [mailto:Dale.Worley@comcast.net] > Sent: Sunday, October 29, 2006 11:31 PM > To: enum@ietf.org > Subject: Re: [Enum] draft-ietf-enum-combined-01 >=20 > From: lconroy >=20 > Defining the procedures for > ..e164.arpa. will undoubtedly involve > ITU study group 2, many trips to Geneva, and a great deal of > time. Isn't dealing with the FCC hard enough? >=20 > You're saying that doing such a delegation would require a further > agreement with the ITU? >=20 > That's why the process of doing just that IS referenced in the I-D > (as the "long term solution" [9]). >=20 > Perhaps the significance of "long term solution" could be spelled out > in a bit more detail? >=20 > Dale >=20 > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Oct 31 10:24:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GevSO-0008WM-QA; Tue, 31 Oct 2006 10:23:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GevSI-0008No-4G; Tue, 31 Oct 2006 10:23:11 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GevSI-0006qZ-2K; Tue, 31 Oct 2006 10:23:10 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GevSG-0001wf-Nn; Tue, 31 Oct 2006 10:23:09 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id A93BC2AC80; Tue, 31 Oct 2006 15:22:38 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GevRm-0007s1-Ew; Tue, 31 Oct 2006 10:22:38 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Tue, 31 Oct 2006 10:22:38 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: enum@ietf.org Subject: [Enum] Last Call: 'Infrastrucure ENUM Requirements' to Informational RFC (draft-ietf-enum-infrastructure-enum-reqs) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has received a request from the Telephone Number Mapping WG to consider the following document: - 'Infrastrucure ENUM Requirements ' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-11-30. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-03.txt _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum