From mailman-owner@ietf.org Sat Apr 1 05:15:35 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07873 for ; Sat, 1 Apr 2000 05:15:35 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA28021 for ; Sat, 1 Apr 2000 05:13:16 -0500 (EST) Date: Sat, 1 Apr 2000 05:13:16 -0500 (EST) From: mailman-owner@ietf.org Message-Id: <200004011013.FAA28021@optimus.ietf.org> Subject: ietf.org mailing list memberships reminder To: enum-web-archive@ns.ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.0 Precedence: bulk List-Id: Diffserv Discussion List This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, enum-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for enum-web-archive@www.ietf.org: List Password // URL ---- -------- enum@ietf.org aUvt http://www.ietf.org/mailman/options/enum/enum-web-archive@www.ietf.org From enum-admin@ietf.org Mon Apr 3 03:21:14 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14116 for ; Mon, 3 Apr 2000 03:21:13 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29913; Mon, 3 Apr 2000 03:17:51 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29884 for ; Mon, 3 Apr 2000 03:17:49 -0400 (EDT) Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14112 for ; Mon, 3 Apr 2000 03:20:09 -0400 (EDT) Received: from laptop.ix.netcom.com (tfx-us15-247.ix.netcom.com [207.94.236.247]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id DAA03214 for ; Mon, 3 Apr 2000 03:20:05 -0400 (EDT) Message-Id: <4.3.2.20000402210402.00be2550@127.0.0.1> X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Sun, 02 Apr 2000 21:09:15 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] The naming of ENUM domain in future ID's Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org It was brought up in the WG meeting in Oz that the use of TLD's for administrative or database functions is being discussed at higher levels within the IESG and IAB. Consequently, in future ENUM ID's or discussions on this list we should refer to e164.foo or foo.foo, for that matter. ID authors please take note. Your Co-Chair.... >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey Shockey Consulting LLC 8045 Big Bend Blvd. Suite 110 St. Louis, MO 63119 Voice 314.918.9020 eFAX Fax to EMail 815.333.1237 (Preferred for Fax) INTERNET Mail & IFAX : rshockey@ix.netcom.com GSTN Fax 314.918.9015 MediaGate iPost VoiceMail and Fax 800.260.4464 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org http://www.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Thu Apr 6 15:00:15 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13029 for ; Thu, 6 Apr 2000 15:00:15 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08343; Thu, 6 Apr 2000 14:55:58 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08285 for ; Thu, 6 Apr 2000 14:55:55 -0400 (EDT) Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12986; Thu, 6 Apr 2000 14:58:17 -0400 (EDT) Received: from laptop.ix.netcom.com ([209.138.159.143]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id OAA11077; Thu, 6 Apr 2000 14:58:14 -0400 (EDT) Message-Id: <4.3.2.20000403181446.00c842d0@127.0.0.1> X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Thu, 06 Apr 2000 13:58:31 -0500 To: to-tamura@kdd.co.jp, itu+ietf@ietf.org From: Richard Shockey Cc: enum@ietf.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Re: [ITU+IETF] NNAR Workshop Issues 4 and 5 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org I'd like to take the opportunity to note that the existence of these documents was discussed at the ENUM WG meeting during IETF 47 in Adelaide, Australia last week. ENUM ID authors and WG participants were asked to thoroughly read these documents and keep in mind the valuable information they contain. I specifically asked our Area Director Scott Bradner ( and IETF-ITU liaison ) how we should treat these documents during our work process. It was suggested that these documents ( and any others the Workshop deems relevant to IETF WG items) be made part of the IETF RFC series so that the larger Internet community has access to them. If these documents can be reformatted in the appropriate IETF manner they can be submitted to the IETF RFC editor for publication. If you need any assistance on the process by which documents are submitted to the RFC Editor ..please let me know. http://www.rfc-editor.org/howtopub.html At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote: >Participants in Question 1 (Numbering) of ITU-T Study Group 2 have put >together >some information relevant to E.164-DNS interworking (for Issue 4) during >their recent meeting, and I am providing an ASCII text version of the Carrier >Selection supplement to E.164 (for Issue 5). > >These files may be found at the following URLs: > > http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-info.txt and > http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt > >-Toshiyuki Tamura > KDD > Japan > > >_______________________________________________ >ITU+IETF mailing list >ITU+IETF@ietf.org >http://www.ietf.org/mailman/listinfo/itu+ietf Sincerely, ENUM -WG co-chair >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey Shockey Consulting LLC 8045 Big Bend Blvd. Suite 110 St. Louis, MO 63119 Voice 314.918.9020 eFAX Fax to EMail 815.333.1237 (Preferred for Fax) INTERNET Mail & IFAX : rshockey@ix.netcom.com GSTN Fax 314.918.9015 MediaGate iPost VoiceMail and Fax 800.260.4464 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Thu Apr 6 17:36:51 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15356 for ; Thu, 6 Apr 2000 17:36:51 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10916; Thu, 6 Apr 2000 17:30:33 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10851 for ; Thu, 6 Apr 2000 17:30:30 -0400 (EDT) Received: from mailgate.fore.com (mailgate.fore.com [169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15274; Thu, 6 Apr 2000 17:32:52 -0400 (EDT) Received: from mailman.fore.com (mailman.fore.com [169.144.2.12]) by mailgate.fore.com (8.9.3/8.9.3) with ESMTP id RAA04786; Thu, 6 Apr 2000 17:32:18 -0400 (EDT) Received: from whq-msgrtr-01.fore.com (whq-msgrtr-01.fore.com [169.144.2.221]) by mailman.fore.com (8.9.3/8.9.3) with ESMTP id RAA22581; Thu, 6 Apr 2000 17:32:21 -0400 (EDT) Received: by whq-msgrtr-01.fore.com with Internet Mail Service (5.5.2650.21) id <2MSFTDNX>; Thu, 6 Apr 2000 17:27:27 -0400 Message-ID: <4FBEA8857476D311A03300204840E1CF678136@whq-msgusr-02.fore.com> From: "Rosen, Brian" To: "'Richard Shockey'" , to-tamura@kdd.co.jp, itu+ietf@ietf.org Cc: enum@ietf.org Subject: RE: [Enum] Re: [ITU+IETF] NNAR Workshop Issues 4 and 5 Date: Thu, 6 Apr 2000 17:32:19 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org I could probably manage the reformatting if no one else steps up to the plate. First there has to be a decision by ITU to allow this. Brian > -----Original Message----- > From: Richard Shockey [mailto:rshockey@ix.netcom.com] > Sent: Thursday, April 06, 2000 2:59 PM > To: to-tamura@kdd.co.jp; itu+ietf@ietf.org > Cc: enum@ietf.org > Subject: [Enum] Re: [ITU+IETF] NNAR Workshop Issues 4 and 5 > > > I'd like to take the opportunity to note that the existence of these > documents was discussed at the ENUM WG meeting during IETF 47 > in Adelaide, > Australia last week. > > ENUM ID authors and WG participants were asked to thoroughly > read these > documents and keep in mind the valuable information they contain. > > I specifically asked our Area Director Scott Bradner ( and > IETF-ITU liaison > ) how we should treat these documents during our work process. > > It was suggested that these documents ( and any others the > Workshop deems > relevant to IETF WG items) be made part of the IETF RFC > series so that the > larger Internet community has access to them. > > If these documents can be reformatted in the appropriate IETF > manner they > can be submitted to the IETF RFC editor for publication. > > If you need any assistance on the process by which documents > are submitted > to the RFC Editor ..please let me know. > > http://www.rfc-editor.org/howtopub.html > > > > > At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote: > > >Participants in Question 1 (Numbering) of ITU-T Study Group > 2 have put > >together > >some information relevant to E.164-DNS interworking (for > Issue 4) during > >their recent meeting, and I am providing an ASCII text > version of the Carrier > >Selection supplement to E.164 (for Issue 5). > > > >These files may be found at the following URLs: > > > > > http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-inf o.txt and > http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt > >-Toshiyuki Tamura > KDD > Japan > > >_______________________________________________ >ITU+IETF mailing list >ITU+IETF@ietf.org >http://www.ietf.org/mailman/listinfo/itu+ietf Sincerely, ENUM -WG co-chair >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey Shockey Consulting LLC 8045 Big Bend Blvd. Suite 110 St. Louis, MO 63119 Voice 314.918.9020 eFAX Fax to EMail 815.333.1237 (Preferred for Fax) INTERNET Mail & IFAX : rshockey@ix.netcom.com GSTN Fax 314.918.9015 MediaGate iPost VoiceMail and Fax 800.260.4464 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Thu Apr 6 20:52:14 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17654 for ; Thu, 6 Apr 2000 20:52:13 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13506; Thu, 6 Apr 2000 20:49:19 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA13438 for ; Thu, 6 Apr 2000 20:49:17 -0400 (EDT) Received: from venus.kdd.co.jp (venus.kdd.co.jp [211.4.169.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17626; Thu, 6 Apr 2000 20:51:37 -0400 (EDT) From: to-tamura@kdd.co.jp Received: by venus.kdd.co.jp; id JAA01939; Fri, 7 Apr 2000 09:51:06 +0900 (JST) Received: from em01sjk.kdd.co.jp (localhost [127.0.0.1]) by jupiter.kdd.co.jp (8.8.8/3.6W) with ESMTP id JAA32200; Fri, 7 Apr 2000 09:51:05 +0900 (JST) Received: from localhost (root@localhost) by kdd.co.jp (8.8.6) with SMTP id JAA18539; Fri, 7 Apr 2000 09:51:04 +0900 (JST) X-OpenMail-Hops: 1 Date: Fri, 7 Apr 2000 09:50:57 +0900 Message-Id: In-Reply-To: <4.3.2.20000403181446.00c842d0@127.0.0.1> MIME-Version: 1.0 TO: rshockey@ix.netcom.com, itu+ietf@ietf.org CC: enum@ietf.org Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Subject: [Enum] Re:Re: [ITU+IETF] NNAR Workshop Issues 4 and 5 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org Thank you and IETF for your kind proposal. I will discuss this with WP1/2 management team and come back. Toshi >I'd like to take the opportunity to note that the existence of these >documents was discussed at the ENUM WG meeting during IETF 47 in Adelaide, >Australia last week. > >ENUM ID authors and WG participants were asked to thoroughly read these >documents and keep in mind the valuable information they contain. > >I specifically asked our Area Director Scott Bradner ( and IETF-ITU liaison >) how we should treat these documents during our work process. > >It was suggested that these documents ( and any others the Workshop deems >relevant to IETF WG items) be made part of the IETF RFC series so that the >larger Internet community has access to them. > >If these documents can be reformatted in the appropriate IETF manner they >can be submitted to the IETF RFC editor for publication. > >If you need any assistance on the process by which documents are submitted >to the RFC Editor ..please let me know. > >http://www.rfc-editor.org/howtopub.html > > > > >At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote: > >>Participants in Question 1 (Numbering) of ITU-T Study Group 2 have put >>together >>some information relevant to E.164-DNS interworking (for Issue 4) during >>their recent meeting, and I am providing an ASCII text version of the Carrier >>Selection supplement to E.164 (for Issue 5). >> >>These files may be found at the following URLs: >> >> http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-info.txt and >> http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt >> >>-Toshiyuki Tamura >> KDD >> Japan >> >> >>_______________________________________________ >>ITU+IETF mailing list >>ITU+IETF@ietf.org >>http://www.ietf.org/mailman/listinfo/itu+ietf > > >Sincerely, ENUM -WG co-chair > > > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >Richard Shockey >Shockey Consulting LLC >8045 Big Bend Blvd. Suite 110 >St. Louis, MO 63119 >Voice 314.918.9020 >eFAX Fax to EMail 815.333.1237 (Preferred for Fax) >INTERNET Mail & IFAX : rshockey@ix.netcom.com >GSTN Fax 314.918.9015 >MediaGate iPost VoiceMail and Fax 800.260.4464 ><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Tue Apr 11 20:57:06 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25346 for ; Tue, 11 Apr 2000 20:57:06 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA10965; Tue, 11 Apr 2000 20:53:20 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA10901 for ; Tue, 11 Apr 2000 20:53:17 -0400 (EDT) Received: from venus.kdd.co.jp (venus.kdd.co.jp [211.4.169.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25287; Tue, 11 Apr 2000 20:55:43 -0400 (EDT) From: to-tamura@kdd.co.jp Received: by venus.kdd.co.jp; id JAA27734; Wed, 12 Apr 2000 09:55:10 +0900 (JST) Received: from em01sjk.kdd.co.jp (localhost [127.0.0.1]) by jupiter.kdd.co.jp (8.8.8/3.6W) with ESMTP id JAA04634; Wed, 12 Apr 2000 09:55:10 +0900 (JST) Received: from localhost (root@localhost) by kdd.co.jp (8.8.6) with SMTP id JAA08711; Wed, 12 Apr 2000 09:55:09 +0900 (JST) X-OpenMail-Hops: 1 Date: Wed, 12 Apr 2000 09:55:00 +0900 Message-Id: In-Reply-To: <4.3.2.20000403181446.00c842d0@127.0.0.1> MIME-Version: 1.0 TO: rshockey@ix.netcom.com, itu+ietf@ietf.org CC: enum@ietf.org Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Subject: [Enum] Re:Re: [ITU+IETF] NNAR Workshop Issues 4 and 5 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org ITU-T WP1/2 management team agreed to submit the documents to make them be part of the IETF RFC series to share the information with the larger Internet community. Format of those documents can be changed and the necessary addition of info should be made in conformance to the IETF process. However, please understand that the contents cannot easily be changed because they have a level of official status in ITU. I appreciate Brian's very kind offer to reformat the documents. Toshi >I'd like to take the opportunity to note that the existence of these >documents was discussed at the ENUM WG meeting during IETF 47 in Adelaide, >Australia last week. > >ENUM ID authors and WG participants were asked to thoroughly read these >documents and keep in mind the valuable information they contain. > >I specifically asked our Area Director Scott Bradner ( and IETF-ITU liaison >) how we should treat these documents during our work process. > >It was suggested that these documents ( and any others the Workshop deems >relevant to IETF WG items) be made part of the IETF RFC series so that the >larger Internet community has access to them. > >If these documents can be reformatted in the appropriate IETF manner they >can be submitted to the IETF RFC editor for publication. > >If you need any assistance on the process by which documents are submitted >to the RFC Editor ..please let me know. > >http://www.rfc-editor.org/howtopub.html > > > > >At 05:09 PM 3/21/2000 +0900, to-tamura@kdd.co.jp wrote: > >>Participants in Question 1 (Numbering) of ITU-T Study Group 2 have put >>together >>some information relevant to E.164-DNS interworking (for Issue 4) during >>their recent meeting, and I am providing an ASCII text version of the Carrier >>Selection supplement to E.164 (for Issue 5). >> >>These files may be found at the following URLs: >> >> http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-e164-dns-iw-info.txt and >> http://www.itu.int/ITU-T/ip-telecoms/nnar/nnar-carrier-sel-supp.txt >> >>-Toshiyuki Tamura >> KDD >> Japan >> >> >>_______________________________________________ >>ITU+IETF mailing list >>ITU+IETF@ietf.org >>http://www.ietf.org/mailman/listinfo/itu+ietf > > >Sincerely, ENUM -WG co-chair > > > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >Richard Shockey >Shockey Consulting LLC >8045 Big Bend Blvd. Suite 110 >St. Louis, MO 63119 >Voice 314.918.9020 >eFAX Fax to EMail 815.333.1237 (Preferred for Fax) >INTERNET Mail & IFAX : rshockey@ix.netcom.com >GSTN Fax 314.918.9015 >MediaGate iPost VoiceMail and Fax 800.260.4464 ><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Wed Apr 12 10:37:19 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22504 for ; Wed, 12 Apr 2000 10:37:18 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24820; Wed, 12 Apr 2000 10:33:41 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24790 for ; Wed, 12 Apr 2000 10:33:39 -0400 (EDT) Received: from hoemlsrv.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22484 for ; Wed, 12 Apr 2000 10:36:09 -0400 (EDT) Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA22562 for ; Wed, 12 Apr 2000 10:36:10 -0400 (EDT) Received: from horh1.emsr.lucent.com (h135-17-1-40.lucent.com [135.17.1.40]) by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id KAA22547 for ; Wed, 12 Apr 2000 10:36:10 -0400 (EDT) Received: from buzz.ons.octel.com by horh1.emsr.lucent.com (8.9.3+Sun/EMS-1.5 Solaris/emsr) id KAA08395 for ; Wed, 12 Apr 2000 10:36:08 -0400 (EDT) Received: from exdal1.ons.octel.com (exdal1 [155.184.13.201]) by buzz.ons.octel.com (8.8.8+Sun/8.8.6) with ESMTP id JAA16993 for ; Wed, 12 Apr 2000 09:36:08 -0500 (CDT) Received: by exdal1.ons.octel.com with Internet Mail Service (5.5.2448.0) id ; Wed, 12 Apr 2000 09:34:26 -0500 Message-ID: <6B57F36F4FF9D111B30A0008C7F4133703704683@exdal1.ons.octel.com> From: "Vaudreuil, Greg M (Greg)" To: enum@ietf.org Date: Wed, 12 Apr 2000 09:34:25 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Subject: [Enum] ENUM Requirements comments Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org The following are specific comments on the requirements document, some of which I presented at the working group meeting in Adelaide. Net-new Requirement Interoperability Goals This solution SHOULD work with the common, deployed DNS resolver libraries in the most common operating systems. It is understood that application clients will have to be created that understand the specific "schema" for ENUM address resolution. Requiring a new generation of resolvers or DNS servers will impose an excessive barrier to widespread adoption of this service. Suggested Revised Requirements 3.1 Endpoint address lookup I do not believe the solution must return a URL for a specific service. While this may be useful for a particular service using ENUM, other services such as email routing or service location simply need a domain name. I suggest the following revised text: "The system SHALL provide a service for the retrieval of service specific endpoint addresses (e.g., email address, IP address, SIP address, URL, etc. ) or the retreival of the addresses of servers, if available, which may contain this endpoint information." 3.5 Provisioning The ENUM service clearly has to be provisionable in the real world. Given that telephone numbers are delegated top-down in a hierarchical manner with existing administrative structure, I believe we have a requirement to make the system work within that structure. It may also support many other administrative models, but at at minimum, it must meet this existing one. Further, because in the real world, the authorities to which telephone numbers are delegated are not involved with specific service registratration or arbitration (remember slaming?), at a minimum, it must be possible for the server that provides telephone number delegation information to be separate from the one that provides service specific information. To this end, it must be possible to redirect the query from the E.164.foo domain into the domain of the assignee of a given telephone number. I suggest the following revised text: "The architecture and protocol MUST support at least the existing administrative model as the current E.164 telephone number delegation system. It SHOULD NOT require an additional centralized administrator beyond that required for the existing telephone number system. Further, it must be possible for the authority to which a telephone number has been delegated to redirect the query to a different entity which provides service-specific information for that number." 3.8 Scaleability The ENUM service must support the return of service-specific information based telephone number ranges on digit boundaries. While local number portability is expected to imposes a per-user provisioning requirement for some countries in the near future, most of the billions of phone numbers in use today and most for the forseable future will be delegated and served in blocks. At the current time, most numbers within these blocks have identical sets of available services. A requirement that per-number provisioning is required for the initial ENUM service to be deployed is unacceptably high. I suggest the following revised text: "The system MUST scale to handle quantities of telephone numbers and queries comparable to current and expected future PSTN usage. Further, because most phone numbers are assigned in blocks to entities with homogenous service profiles, it must be possible to operate the system based on telephone number blocks defined at the digit boundaries. The system SHOULD NOT require, but MUST support explicit per-number configuration." 3.9 Query Performance It must be possible to administer the ENUM service such that the current user expectations for latency in telecommunications services can be met. This latency expectation is currently for a 2 second response 95% of the time and a 5 second response 99% of the time. Given that ENUM is only part of the lookup required to fufil many service, and that SIP, LDAP, or others will also be needed, the performance budget for ENUM is tight. In particluar, if the protocol is designed such that it is not possible to administer the system to a 1 second response 95% of the time, the system will not have met this requirement. I suggest the following revised text: "It SHOULD be possible to administer the ENUM service using the selected protocols and structures such that the current user expectations for latency in telecommunications services can be met. In particular, it SHOULD be possible to operate the system in such a manner that an ENUM query for a service-specific record can be satisfied within one second 95% of the time and that within two seconds, the query can be satisfied 99% of the time." 3.10 Other PSTN numbering services We have discussed at length that the resolution of non-e164 based telephone numbers is outside the scope of this work item. The clarity from those discussions should be reflected in this requirement. I suggest the following revised text: "Other PSTN type services such as Emergency 911, directory assistance 411, and other carrier codes for services accessible via non-E164 (or subset) telephone number service access codes are outside the scope of ENUM." 2.12 Competition I disagree that this requirement as stated is real, and further assert that it cannot be met as stated. There can only be one authorative source for information about a given phone number, the single authority to which it has been delegated. If this is not true, there is no possiblity for a client to authenticating the validity of the response without extensive out-of-band configuration information, additional service specific information, and interactive end-user selection. I suggest the following replacement requirement: "The solution should permit competing service providers to offer telecommunications service for a given number. Competing telecomunications services should be enabled where the ENUM entry is administered by the single entity to which the number is delegated." Greg V. gregv@lucent.com _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum From enum-admin@ietf.org Mon Apr 24 06:42:54 2000 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29744 for ; Mon, 24 Apr 2000 06:42:54 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28990; Mon, 24 Apr 2000 06:39:48 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA28959 for ; Mon, 24 Apr 2000 06:39:47 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29653; Mon, 24 Apr 2000 06:39:51 -0400 (EDT) Message-Id: <200004241039.GAA29653@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: enum@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 24 Apr 2000 06:39:50 -0400 Subject: [Enum] I-D ACTION:draft-peek-enum-itd-00.txt Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: Enum Discussion List X-BeenThere: enum@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Internet-Telephony Directory for Mapping E.164 to Internet Addresses Author(s) : D. Peek, R. Walters, D. Ranalli Filename : draft-peek-enum-itd-00.txt Pages : 17 Date : 21-Apr-00 A holistic directory system is described which translates a standard E.164 telephone number into the Internet address information required to support IP-enabled communications applications such as real-time voice, voice-messaging, fax or unified-messaging. The proposed system utilizes two logical control tiers to implement the translation. The first logical control tier is patterned after a Top Level Domain (TLD) of the Internet Domain Name System (DNS). This first-tier provides a mechanism for locating the appropriate directory within the second logical tier of the Internet-Telephony directory system where authoritative Internet address information is stored for a given E.164 number. This first-tier is expected to conform to the regulatory and operational standards defined by the Internet Corporation for the Assignment of Names and Numbers (ICANN) for the operation of top-level domains. The second logical control tier provides a mechanism for accessing and managing authoritative Internet address information associated with an E.164 number. This tier consists of widely distributed DNS servers controlled by service providers, and corporate network operators. Distributed ownership of the second tier directories allows organizations to control the Internet address information associated with the E.164 numbers under their day-to-day control. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-peek-enum-itd-00.txt 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-peek-enum-itd-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-peek-enum-itd-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: <20000421084411.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-peek-enum-itd-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-peek-enum-itd-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000421084411.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ enum mailing list enum@ietf.org http://www1.ietf.org/mailman/listinfo/enum