From enum-bounces@ietf.org Fri Nov 02 08:48:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Invr9-0006Vt-UJ; Fri, 02 Nov 2007 08:42:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Invr8-0006B8-Jt for enum@ietf.org; Fri, 02 Nov 2007 08:42:34 -0400 Received: from medel.switch.ch ([2001:620:0:14:214:4fff:fe75:4775]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Invqe-0004NF-PD for enum@ietf.org; Fri, 02 Nov 2007 08:42:15 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by medel.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1InvqZ-00011D-Sn for enum@ietf.org; Fri, 02 Nov 2007 13:41:59 +0100 Date: Fri, 2 Nov 2007 13:41:35 +0100 (CET) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: enum@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: 0.1 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Subject: [Enum] Future Enumservice Registration Process 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 all *** Please comment until Wednesday, Nov 05 *** One major issue in draft-ietf-enum-enumservices-guide-05.txt seems to be, which process to apply for future Enum service registrations. I went through existing similar IANA processes and found at least four variants, how a registration document can be processed: A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication B) Author -> Expert Review -> IESG -> IANA -> Publication C) Author -> IANA -> Expert Review -> IANA -> Publication D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication In the current revision of draft-ietf-enum-enumservices-guide-05.txt process B) is documented, however I am tending to replace it by process A), as this way the responsibilities are much more clear. In case registrations should be made without IESG looking at it, C) could be the choice. Maybe for experimental Enumservice registrations this makes sense. If we want to apply such a simple process for normal Enumservice registrations, a major change in RFC 3761 is needed, as RFC 3761 states: "Enumservice registrations needs to be Standards Track, Experimental or BCP" What do you think about? In case there it no major opposition within the next 5 days, I'll rewrite draft-ietf-enum-enumservices-guide-06.txt in favour of process A) and submit it for the Vancouver meeting. cheers, Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Nov 02 11:59:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Inyqu-0001DV-KG; Fri, 02 Nov 2007 11:54:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Inyqt-0001CK-AE for enum@ietf.org; Fri, 02 Nov 2007 11:54:31 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Inyqn-00030X-RH for enum@ietf.org; Fri, 02 Nov 2007 11:54:31 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA2Frwoa027346 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Nov 2007 07:54:01 -0800 From: "Richard Shockey" To: "'Bernie Hoeneisen'" , References: In-Reply-To: Subject: RE: [Enum] Future Enumservice Registration Process Date: Fri, 2 Nov 2007 11:54:08 -0400 Message-ID: <0a0701c81d68$9c8b7a90$d5a26fb0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgdTefgazq0gEs9Q32O9wf8Eyr0oAAGjuIA Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 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 Bernie this is a excellent summary of the options. Chair hat off ... I lean toward Plan B. The registration proceeds directly to the expert review via a special email list like we see with URI's. The expert review deals with it in a "reasonable" time frame and forwards its report to the IESG for ultimate approval. > -----Original Message----- > From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] > Sent: Friday, November 02, 2007 8:42 AM > To: enum@ietf.org > Subject: [Enum] Future Enumservice Registration Process > > Hi all > > *** Please comment until Wednesday, Nov 05 *** > > One major issue in draft-ietf-enum-enumservices-guide-05.txt seems to > be, > which process to apply for future Enum service registrations. I went > through existing similar IANA processes and found at least four > variants, > how a registration document can be processed: > > A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication > > B) Author -> Expert Review -> IESG -> IANA -> Publication > > C) Author -> IANA -> Expert Review -> IANA -> Publication > > D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication > > > In the current revision of draft-ietf-enum-enumservices-guide-05.txt > process B) is documented, however I am tending to replace it by > process > A), as this way the responsibilities are much more clear. > > In case registrations should be made without IESG looking at it, C) > could be the choice. Maybe for experimental Enumservice registrations > this > makes sense. If we want to apply such a simple process for normal > Enumservice registrations, a major change in RFC 3761 is needed, as > RFC 3761 states: "Enumservice registrations needs to be Standards > Track, > Experimental or BCP" > > What do you think about? In case there it no major opposition within > the > next 5 days, I'll rewrite draft-ietf-enum-enumservices-guide-06.txt in > favour of process A) and submit it for the Vancouver meeting. > > 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 Fri Nov 02 13:33:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Io0MB-0007ML-8Y; Fri, 02 Nov 2007 13:30:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Io0M8-0007Ls-VW; Fri, 02 Nov 2007 13:30:52 -0400 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Io0M7-0006Vf-MB; Fri, 02 Nov 2007 13:30:52 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA2HUQrH023882 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Nov 2007 09:30:27 -0800 From: "Richard Shockey" To: , Date: Fri, 2 Nov 2007 13:30:36 -0400 Message-ID: <0ab801c81d76$1512f710$3f38e530$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgdBvbwvFuQjleESTaRQ7z3MMqf+wAbxbwA Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: Subject: [Enum] FW: Internet-Drafts Submission Cutoff Dates for the 70th IETF Meeting in Vancouver, BC, Canada 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 -----Original Message----- From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org]=20 Sent: Friday, November 02, 2007 12:00 AM To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 70th IETF = Meeting in Vancouver, BC, Canada=20 There are two (2) Internet-Draft cutoff dates for the 70th=20 IETF Meeting in Vancouver, BC, Canada: November 12th: Cutoff Date for Initial (i.e., version -00)=20 Internet-Draft Submissions=20 All initial Internet-Drafts (version -00) must be submitted by Monday,=20 November 12th at 9:00 AM ET (14:00 UTC/GMT). As always, all initial = submissions with a=20 filename beginning with "draft-ietf" must be approved by the=20 appropriate WG Chair before they can be processed or announced. The=20 Secretariat would appreciate receiving WG Chair approval by Monday,=20 November 5th at 9:00 AM ET (14:00 UTC/GMT). November (14:00 UTC/GMT): Cutoff Date for Revised (i.e., version -01 = and higher)=20 Internet-Draft Submissions=20 All revised Internet-Drafts (version -01 and higher) must be submitted=20 by Monday, November 19th at 9:00 AM ET (14:00 UTC/GMT). Initial and revised Internet-Drafts received after their respective=20 cutoff dates will not be made available in the Internet-Drafts=20 directory or announced until on or after Monday, December 3rd at 9:00=20 AM ET (14:00 UTC/GMT), when Internet-Draft posting resumes. Please do = not wait until=20 the last minute to submit. The Secretariat encourages you to submit your Internet-Drafts via the=20 Internet-Draft Submission Tool (IDST) = https://datatracker.ietf.org/idst/upload.cgi.=20 If you are unable to do so, then you may still submit your Internet- Drafts manually by sending them to internet-drafts@ietf.org. If you=20 are submitting a version -00 WG draft that replaces non-WG draft, then=20 you must submit it manually as the current IDST cannot handle=20 replacements. Please be sure to state that one draft replaces another=20 in the cover note that accompanies your submission. Also, please note=20 that the IDST will not accept drafts submitted after their respective=20 cutoff dates. Thank you for your understanding and cooperation. If you have any=20 questions or concerns, then please send a message to=20 internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 70th IETF Meeting can be found at = http://www.ietf.org/meetings/cutoff_dates_70.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sat Nov 03 06:16:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IoFwj-0004S1-WF; Sat, 03 Nov 2007 06:09:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IoFwi-0004Px-Bf for enum@ietf.org; Sat, 03 Nov 2007 06:09:40 -0400 Received: from medel.switch.ch ([2001:620:0:14:214:4fff:fe75:4775]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IoFwV-000762-26 for enum@ietf.org; Sat, 03 Nov 2007 06:09:38 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by medel.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1IoFw3-000102-JS; Sat, 03 Nov 2007 11:08:59 +0100 Date: Sat, 3 Nov 2007 11:08:32 +0100 (CET) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: Romek Szczesniak Subject: Re: [Enum] Re: I-D Action:draft-hoeneisen-enum-x-service-regs-02.txt In-Reply-To: <4720B567.8060809@spikyblackcat.co.uk> Message-ID: References: <4720B567.8060809@spikyblackcat.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: 0.1 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 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 Romek On Thu, 25 Oct 2007, Romek Szczesniak wrote: > draft-hoeneisen-enum-x-service-regs-02.txt. I haven't seen any discussion on > it here so I thought I would. Nice idea! Inline some questions for clarification. > (iii) when a client does not wish a service type to be evaluated by a > standards-based ENUM clients. I do not understand the use case you describe here. Could you please enlighten this a bit? > I suggest that: > > 1. We specify that X- services SHOULD follow the same syntax as other > registered services (so that ENUM clients do not break on receipt of such > rules). For what reason do you think ENUM clients would break? Do you mean the "-" char, which is not allowed as per RFC3761? > 2. Provide a standardised mechanism for service types (if needed for public > use) to be appended to the list of Enum service types after review. This > review period should be at most about 6 months (to prevent all service types > remaining as X- ). Do you mean any X-Enumservice should expire latest after 6 months and be removed from the IANA registry? cheers, Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Nov 04 12:57:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iojip-00080l-Sz; Sun, 04 Nov 2007 12:57:19 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iojin-0007vV-Sc for enum@ietf.org; Sun, 04 Nov 2007 12:57:17 -0500 Received: from nat.labs.nic.at ([83.136.33.3] helo=labs.nic.at) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iojin-0007zi-Br for enum@ietf.org; Sun, 04 Nov 2007 12:57:17 -0500 Received: from lendl by labs.nic.at with local (Exim 3.36 #1 (Debian)) id 1Iojil-00010M-00 for ; Sun, 04 Nov 2007 18:57:15 +0100 Date: Sun, 4 Nov 2007 18:57:15 +0100 From: Otmar Lendl To: enum@ietf.org Subject: Re: [Enum] Future Enumservice Registration Process Message-ID: <20071104175715.GA2785@nic.at> Mail-Followup-To: Otmar Lendl , enum@ietf.org References: <0a0701c81d68$9c8b7a90$d5a26fb0$@us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0a0701c81d68$9c8b7a90$d5a26fb0$@us> User-Agent: Mutt/1.5.9i X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 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 2007/11/02 16:11, Richard Shockey wrote: > Bernie this is a excellent summary of the options. > > Chair hat off ... I lean toward Plan B. > > The registration proceeds directly to the expert review via a special email > list like we see with URI's. The expert review deals with it in a > "reasonable" time frame and forwards its report to the IESG for ultimate > approval. As I had the pleasure of test-driving 2929bis, I don't like B. The reason is that hard to guarantee SLAs from experts. In that case, what happens if the exports don't react in the given time frame? What happens in that case? When everything works as planned, all four processes are fine. The things we should have an eye on are the faultlines. What happens if something doesn't go according to plan? /ol -- / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Nov 04 18:42:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iop6V-0001Vb-M7; Sun, 04 Nov 2007 18:42:07 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iop6V-0001Qp-0U for enum@ietf.org; Sun, 04 Nov 2007 18:42:07 -0500 Received: from norman.insensate.co.uk ([213.152.49.123] helo=insensate.co.uk) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iop6U-0004Ve-7C for enum@ietf.org; Sun, 04 Nov 2007 18:42:06 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id D2D2F5E16F; Sun, 4 Nov 2007 23:42:04 +0000 (GMT) In-Reply-To: <20071104175715.GA2785@nic.at> References: <0a0701c81d68$9c8b7a90$d5a26fb0$@us> <20071104175715.GA2785@nic.at> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <386E8CDD-7065-4C17-899F-A315B2BB1F45@insensate.co.uk> Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] Future Enumservice Registration Process Date: Sun, 4 Nov 2007 23:42:03 +0000 To: Otmar Lendl X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 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 Folks, (i) Remember that the IESG decides who is to be designated as an expert. Thus they set up the pool of experts before any reviews even take place. Do they also have to assign an expert for each review as well before things begin? I think that options A & D assume that the IESG has too much time on its hands. Ha! (ii) I *hope* that your experience was a teething problem - looking at the comments, it seemed that a fair chunk of the early questions were asked for clarification from the WG that set up the 2929bis process rather being aimed at the draft authors. In effect, you were caught in the crossfire, and your expert couldn't progress until *those* questions were answered. That MAY be the price one pays for a less rigid process - it's initially chaotic. I would HOPE that we can learn from that. (iii) Getting the expert's attention: bribery may work - it usually does. Have you considered employing said expert, or sponsoring an IETF meeting? Seriously, folks ... What do we expect of volunteers, especially ones who are assigned by someone else (based on that expert's availability) to review a draft? The expert so assigned may not have a lot of domain knowledge, and frankly may not all that interested in the environment that has driven a need for this registration. (iv) IMHO, there *has* to be a ML, and someone (who has close understanding of the kind of things that will come up in registrations) with the responsibility to select an appropriate sucker//////volunteer expert to review work when it is ready to be considered. The trick is - when is something "ready", who gets to decide, and how are they anointed so that they can convince one of a pool of designated experts to spend his or her own time on document review? Whoever it is, please don't upset him/her - your urgent bright idea may never get through the process. all the best, Lawrence On 4 Nov 2007, at 17:57, Otmar Lendl wrote: > On 2007/11/02 16:11, Richard Shockey wrote: >> Bernie this is a excellent summary of the options. >> >> Chair hat off ... I lean toward Plan B. >> >> The registration proceeds directly to the expert review via a >> special email >> list like we see with URI's. The expert review deals with it in a >> "reasonable" time frame and forwards its report to the IESG for >> ultimate >> approval. > > As I had the pleasure of test-driving 2929bis, I don't like B. > > The reason is that hard to guarantee SLAs from experts. In that > case, what happens if the exports don't react in the given time frame? > What happens in that case? > > When everything works as planned, all four processes are fine. > The things we should have an eye on are the faultlines. What > happens if something doesn't go according to plan? > > /ol > -- > / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ > | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | > \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / > > _______________________________________________ > 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 Mon Nov 05 09:40:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip37G-0001G0-UG; Mon, 05 Nov 2007 09:39:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip37F-0001BE-UU for enum@ietf.org; Mon, 05 Nov 2007 09:39:49 -0500 Received: from 77-99-145-183.cable.ubr06.hari.blueyonder.co.uk ([77.99.145.183] helo=romek-szczesniaks-computer.local) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ip37C-00007v-Vl for enum@ietf.org; Mon, 05 Nov 2007 09:39:49 -0500 Received: from romek-szczesniaks-computer.local (localhost [127.0.0.1]) by romek-szczesniaks-computer.local (Postfix) with ESMTP id A50344DDB98; Mon, 5 Nov 2007 14:39:41 +0000 (GMT) Message-ID: <472F2B2D.5080008@spikyblackcat.co.uk> Date: Mon, 05 Nov 2007 14:39:41 +0000 From: Romek Szczesniak User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Bernie Hoeneisen References: <4720B567.8060809@spikyblackcat.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.7 (+) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: enum@ietf.org Subject: [Enum] Re: I-D Action:draft-hoeneisen-enum-x-service-regs-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 Thanks for the comments, Bernie. My responses are inline. Comments appreciated, Romek. Bernie Hoeneisen wrote: > Hi Romek > > On Thu, 25 Oct 2007, Romek Szczesniak wrote: > >> draft-hoeneisen-enum-x-service-regs-02.txt. I haven't seen any >> discussion on it here so I thought I would. > > Nice idea! > > Inline some questions for clarification. > >> (iii) when a client does not wish a service type to be evaluated by a >> standards-based ENUM clients. > > I do not understand the use case you describe here. Could you please > enlighten this a bit? > Currently someone who crafts an X-service has no specific reason to publish how my experimental service works. It can therefore be proprietary, defined for a specific client for a special yet to be defined usecase. For example, most ENUM clients will not interpret E2U+x-rss it has not been defined or published it to the list as a service to be reviewed, Instead, they will either show it as an unrecognised service type or (more likely) ignore it completely. And yet, "E2U+X-rss:http" "!^.*$!http://!" . could be valid (as RFC 3761, Sect. 2.4.2.1 states) "with the active agreement of the parties exchanging them". >> I suggest that: >> >> 1. We specify that X- services SHOULD follow the same syntax as other >> registered services (so that ENUM clients do not break on receipt of >> such rules). > > For what reason do you think ENUM clients would break? > Do you mean the "-" char, which is not allowed as per RFC3761? > I meant that a proprietary X-service which has not been approved may still be read by a standards-based ENUM client. As X-services need not follow RFC3761 to the letter, they have the capability to break them too using the regexp and replacement fields. On further thought, I am not sure that this is a problem. By following the ENUM Experiences draft here, perhaps with an extra note for drawing up X-services, these should be reasonably well formed. >> 2. Provide a standardised mechanism for service types (if needed for >> public use) to be appended to the list of Enum service types after >> review. This review period should be at most about 6 months (to >> prevent all service types remaining as X- ). > > Do you mean any X-Enumservice should expire latest after 6 months and be > removed from the IANA registry? > I state here that most implementors will lose interest in registration (or forget what they had registered) if the process takes too long. For me, this would be roughly 6 months. The registration process has to be relatively quick to prevent implementors ignoring the registered E2U service types and only using X-service types. > cheers, > Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 05 17:41:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpAdi-0007ey-MR; Mon, 05 Nov 2007 17:41:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpAdi-0007da-0d for enum@ietf.org; Mon, 05 Nov 2007 17:41:50 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpAdg-00061U-8W for enum@ietf.org; Mon, 05 Nov 2007 17:41:50 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id 3B049328BD; Mon, 5 Nov 2007 22:41:18 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IpAdC-0001lT-4r; Mon, 05 Nov 2007 17:41:18 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: hoeneisen@switch.ch From: IETF I-D Submission Tool Message-Id: Date: Mon, 05 Nov 2007 17:41:18 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: enum@ietf.org Subject: [Enum] New Version Notification for draft-ietf-enum-x-service-regs-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 A new version of I-D, draft-ietf-enum-x-service-regs-00.txt has been successfuly submitted by Bernie Hoeneisen and posted to the IETF repository. Filename: draft-ietf-enum-x-service-regs Revision: 00 Title: Registration of Enumservices for experimental, private or trial use Creation_date: 2007-11-05 WG ID: enum Number_of_pages: 13 Abstract: This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 05 17:50:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpAlg-0000Da-OX; Mon, 05 Nov 2007 17:50:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpAle-0000Al-Qc; Mon, 05 Nov 2007 17:50:02 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpAle-0006Cl-F6; Mon, 05 Nov 2007 17:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 54E1826EBD; Mon, 5 Nov 2007 22:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IpAle-0001oD-7e; Mon, 05 Nov 2007 17:50:02 -0500 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, 05 Nov 2007 17:50:02 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-x-service-regs-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 : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-ietf-enum-x-service-regs-00.txt Pages : 13 Date : 2007-11-05 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-x-service-regs-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-x-service-regs-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-x-service-regs-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: <2007-11-05174115.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-x-service-regs-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-x-service-regs-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-05174115.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 Tue Nov 06 11:09:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpQzk-0000Sg-Rf; Tue, 06 Nov 2007 11:09:40 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpQzj-0000Ro-7Z for enum@ietf.org; Tue, 06 Nov 2007 11:09:39 -0500 Received: from nat.labs.nic.at ([83.136.33.3] helo=labs.nic.at) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpQzi-0003LQ-A7 for enum@ietf.org; Tue, 06 Nov 2007 11:09:38 -0500 Received: from lendl by labs.nic.at with local (Exim 3.36 #1 (Debian)) id 1IpQzf-0001Xq-00; Tue, 06 Nov 2007 17:09:35 +0100 Date: Tue, 6 Nov 2007 17:09:35 +0100 From: Otmar Lendl To: lconroy Subject: Re: [Enum] Future Enumservice Registration Process Message-ID: <20071106160935.GA5903@nic.at> Mail-Followup-To: Otmar Lendl , lconroy , enum@ietf.org References: <0a0701c81d68$9c8b7a90$d5a26fb0$@us> <20071104175715.GA2785@nic.at> <386E8CDD-7065-4C17-899F-A315B2BB1F45@insensate.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <386E8CDD-7065-4C17-899F-A315B2BB1F45@insensate.co.uk> User-Agent: Mutt/1.5.9i X-Spam-Score: 0.0 (/) 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 On 2007/11/05 00:11, lconroy wrote: > Hi Folks, > > (i) Remember that the IESG decides who is to be designated as an > expert. Thus they set up the pool of experts before any reviews even > take place. Do they also have to assign an expert for each review as > well before things begin? I think that options A & D assume that the > IESG has too much time on its hands. Ha! IMHO you need someone whose daily business is to shepherd processes. Bug people into responsing, keeping track of procedures and deadlines, in other words, be a bloody (but functional) bureaucracy. I don't think the IESG is setup for such a job. Let them approve the process and appoint the expert, but keep them off the critical path for the actual process as far as possible. The IANA sounds like a better choice to me, i.e. option C. > (ii) I *hope* that your experience was a teething problem - looking at > the comments, it seemed that a fair chunk of the early questions were > asked for clarification from the WG that set up the 2929bis process > rather being aimed at the draft authors. In effect, you were caught > in the crossfire, and your expert couldn't progress until *those* > questions were answered. That MAY be the price one pays for a less > rigid process - it's initially chaotic. I would HOPE that we can learn > from that. I don't complain about my experience. It just exposed one design criterium: Don't just plan how the process works when everybody cooperates, but also what happens when someone is not doing his job. > (iii) Seriously, folks ... What do we expect of > volunteers, especially ones who are assigned by someone else (based > on that expert's availability) to review a draft? The expert so > assigned may not have a lot of domain knowledge, and frankly may not > all that interested in the environment that has driven a need for this > registration. Yep: that's why the registration procedure needs to contain more than * A submits proposal to X * X does Y within Z days * If Y approves, B will publish * ... Like any good programming, we need to check for error conditions when designing the algorithm: * A submits proposal to X * X does Y within Z days. On timeout, X can appeal to ... * If Y approves, B will publish * ... /ol -- / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Nov 06 11:38:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpRRt-0004O3-Iv; Tue, 06 Nov 2007 11:38:45 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpRRs-0004Nv-7X for enum@ietf.org; Tue, 06 Nov 2007 11:38:44 -0500 Received: from fw-d-whp.denic.de ([81.91.160.27] helo=denic.de) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpRRr-0003yM-Nt for enum@ietf.org; Tue, 06 Nov 2007 11:38:44 -0500 Received: by unknown.office.denic.de (Postfix, from userid 501) id 32DBC55CF29; Tue, 6 Nov 2007 17:38:42 +0100 (CET) Date: Tue, 6 Nov 2007 17:38:41 +0100 From: Peter Koch To: IETF ENUM WG Subject: Re: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-05.txt Message-ID: <20071106163841.GE1828@unknown.office.denic.de> Mail-Followup-To: IETF ENUM WG References: <20071022213311.GE679@denics7.denic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 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 Bernie, On Tue, Oct 23, 2007 at 01:02:03PM +0200, Bernie Hoeneisen wrote: apologies for the late response. > >It also might produce strange corner cases, e.g. where it > >demands the proposed service be submitted as "individual submission", > >which could even exclude a WG from the proposing a new service (well, > >there's a solution to that, but why not get it right in the first place). > > What exactly do you mean here? _if_ the registration procedure would involve an I-D, why require the "individual submission" path? Imagine some WG came up with a new ENUM service, so they should be allowed to work on that as a WG document. Of course, I understand the desire to relieve the ENUM WG from processing all services, but that should be achieved differently. > I am aware of the mixing part, which certainly needs to be sorted out. > There is also the open issue at which time in the process the expert comes > into action. As far as IANA is concerned, RFC 2434 and its successor should be clear. > >by maintaining the requirement that any ENUMservice be published as a > >BCP, Standards Track or Experimental RFC. The draft in question would > >be an excellent opportunity to relax that. > > What would be your concrete proposal for relaxing? It seems the WG feels that registration of ENUM services should be easier, while at the same time maintaining some review. Since in contrast to, say, port numbers, the space for service identifiers isn't really scarce, there needs to be some rationale behind a regime on the registration: 1) Avoid confusion by identical or similar services offered under different service names to assist correct use 2) Avoid the use of ENUM services in a way that is incompatible with the ENUM model or has other indesired side effects 3) While the identifier space is huge, space in the NAPTR RRSet probably isn't, so there is some pressure to avoid the "1000 flowers". If one accepts this reasoning, then there are two issues. First, access to the specification needs to be permanently secured and second, the specification must be reviewed, desirably short of full standrads track. This seems to suggest relaxing the Standards/Experimental requirement towards, e.g., "RFC published", which explicitly includes Informational and also "Expert Review (Designated Expert)" to take load off the IESG. Richard in a later thraed suggested a closer look at RFC 4395 and I think that's an excellent idea. URI schemes are probably closer to ENUM services than MIME types. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Nov 06 11:55:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpRhe-0007Iu-7S; Tue, 06 Nov 2007 11:55:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpRhc-0007HV-L2 for enum@ietf.org; Tue, 06 Nov 2007 11:55:00 -0500 Received: from fw-d-whp.denic.de ([81.91.160.27] helo=denic.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpRhZ-0000vU-6L for enum@ietf.org; Tue, 06 Nov 2007 11:55:00 -0500 Received: by unknown.office.denic.de (Postfix, from userid 501) id 003C755CF5D; Tue, 6 Nov 2007 17:54:55 +0100 (CET) Date: Tue, 6 Nov 2007 17:54:55 +0100 From: Peter Koch To: IETF ENUM WG Subject: Re: [Enum] Future Enumservice Registration Process Message-ID: <20071106165455.GF1828@unknown.office.denic.de> Mail-Followup-To: IETF ENUM WG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 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 Bernie, {sorry, missed the subject change} > *** Please comment until Wednesday, Nov 05 *** oh, what happened to the Swiss clock/calendar? > A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication > B) Author -> Expert Review -> IESG -> IANA -> Publication > C) Author -> IANA -> Expert Review -> IANA -> Publication > D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication Since "Expert Review" is to appear in IANA considerations kind of to avoid the standards track, of the four options only (C) makes sense to me. Of course, the IESG is free to consult "Experts" (well, that's also what Last Calls are for), but requiring this approach doesn't fit our usual processes. > In case registrations should be made without IESG looking at it, C) > could be the choice. Maybe for experimental Enumservice registrations this > makes sense. If we want to apply such a simple process for normal > Enumservice registrations, a major change in RFC 3761 is needed, as > RFC 3761 states: "Enumservice registrations needs to be Standards Track, > Experimental or BCP" Yes, but that's what these guidelines are all about. Get rid of standards track, otherwise the whole "Expert Review" design isn't upon the WG to decide. And, as Lawrence said, the IESG selects the expert(s) and 2434bis also contains text to deal with expert overload, timeouts and the like. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Nov 06 15:48:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpVLr-0007aH-7R; Tue, 06 Nov 2007 15:48:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpVLq-0007Zv-SM for enum@ietf.org; Tue, 06 Nov 2007 15:48:46 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpVLm-0007KB-Sz for enum@ietf.org; Tue, 06 Nov 2007 15:48:46 -0500 Received: from rshockeyPC (62-50-219-48.client.stsn.net [62.50.219.48]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA6KlvDs009614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 6 Nov 2007 12:48:08 -0800 From: "Richard Shockey" To: "'Peter Koch'" , "'IETF ENUM WG'" References: <20071106165455.GF1828@unknown.office.denic.de> In-Reply-To: <20071106165455.GF1828@unknown.office.denic.de> Subject: RE: [Enum] Future Enumservice Registration Process Date: Tue, 6 Nov 2007 15:47:55 -0500 Message-ID: <000501c820b6$563f39e0$02bdada0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgglbnUbc7lu13SStmyT/2afdEKgwAC3zSw Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 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 C would work for me as well. > -----Original Message----- > From: Peter Koch [mailto:pk@DENIC.DE] > Sent: Tuesday, November 06, 2007 11:55 AM > To: IETF ENUM WG > Subject: Re: [Enum] Future Enumservice Registration Process > > Bernie, > > {sorry, missed the subject change} > > > *** Please comment until Wednesday, Nov 05 *** > > oh, what happened to the Swiss clock/calendar? > > > A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication > > B) Author -> Expert Review -> IESG -> IANA -> Publication > > C) Author -> IANA -> Expert Review -> IANA -> Publication > > D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication > > Since "Expert Review" is to appear in IANA considerations kind of to > avoid the > standards track, of the four options only (C) makes sense to me. Of > course, > the IESG is free to consult "Experts" (well, that's also what Last > Calls are > for), but requiring this approach doesn't fit our usual processes. > > > In case registrations should be made without IESG looking at it, C) > > could be the choice. Maybe for experimental Enumservice > registrations this > > makes sense. If we want to apply such a simple process for normal > > Enumservice registrations, a major change in RFC 3761 is needed, as > > RFC 3761 states: "Enumservice registrations needs to be Standards > Track, > > Experimental or BCP" > > Yes, but that's what these guidelines are all about. Get rid of > standards > track, otherwise the whole "Expert Review" design isn't upon the WG to > decide. > > And, as Lawrence said, the IESG selects the expert(s) and 2434bis also > contains text to deal with expert overload, timeouts and the like. > > -Peter > > _______________________________________________ > 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 Nov 07 05:19:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipi0R-0000UO-Q8; Wed, 07 Nov 2007 05:19:31 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipi0R-0000TQ-B5 for enum@ietf.org; Wed, 07 Nov 2007 05:19:31 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ipi0O-0001dq-0y for enum@ietf.org; Wed, 07 Nov 2007 05:19:31 -0500 Received: from rshockeyPC (62-50-217-140.client.stsn.net [62.50.217.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA7AJ0K7027886 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 7 Nov 2007 02:19:03 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Wed, 7 Nov 2007 05:18:53 -0500 Message-ID: <022401c82127$9af137c0$d0d3a740$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acgg2YYbMS7qR1h0R+eH9AfGdoFmuAATf94w Content-Language: en-us X-Spam-Score: 1.9 (+) X-Scan-Signature: bb8eae9af85e4fcfe76f325e38493bf4 Subject: [Enum] FW: I-D Action:draft-shockey-enum-trunkgroup-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 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Nov 07 05:39:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpiJc-0003eh-Tk; Wed, 07 Nov 2007 05:39:20 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpiJb-0003cL-DU; Wed, 07 Nov 2007 05:39:19 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IpiJX-0002Es-IC; Wed, 07 Nov 2007 05:39:19 -0500 Received: from rshockeyPC (62-50-217-140.client.stsn.net [62.50.217.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA7Aclrr002124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 7 Nov 2007 02:38:50 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" , References: <022401c82127$9af137c0$d0d3a740$@us> In-Reply-To: <022401c82127$9af137c0$d0d3a740$@us> Subject: RE: [Enum] FW: I-D Action:draft-shockey-enum-trunkgroup-00.txt Date: Wed, 7 Nov 2007 05:38:40 -0500 Message-ID: <071c01c8212a$5ecdfc80$1c69f580$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acgg2YYbMS7qR1h0R+eH9AfGdoFmuAATf94wAACw7MA= Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab 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 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IANA Registration for an Enumservice Trunkgroup Author(s) : R. Shockey, T. Creighton Filename : draft-shockey-enum-trunkgroup-00.txt Pages : 10 Date : 2007-11-06 This document registers the Enumservice 'trunk' and subtypes 'sip' and 'tel' using the URI schemes 'sip:' and 'tel:' as per the IANA registration process defined in the ENUM specification RFC 3761 [RFC7761]. RFC 4904 [RFC4904] defines a technique for the conveyance of carrying trunking information in SIP [RFC3261] and or TEL [RFC3966] URI's. This Enumservice provides a mechanism for ENUM databases residing in service provider networks a mechanism to query for that data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shockey-enum-trunkgroup-00.txt _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Nov 07 18:13:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipu5P-0002XA-81; Wed, 07 Nov 2007 18:13:27 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipu5N-0002X0-Pi for enum@ietf.org; Wed, 07 Nov 2007 18:13:25 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ipu5N-0006XM-2S for enum@ietf.org; Wed, 07 Nov 2007 18:13:25 -0500 Received: from rshockeyPC (62-50-220-133.client.stsn.net [62.50.220.133]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lA7NCop2011353 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 7 Nov 2007 15:13:03 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Wed, 7 Nov 2007 18:12:43 -0500 Message-ID: <113e01c82193$bb3bd9b0$31b38d10$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acghk7JdkyMPxE9xTIqsZHlh26Qm4w== Content-Language: en-us X-Spam-Score: 1.8 (+) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Subject: [Enum] PRELIMINARY ENUM WG AGENDA... 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 Did I miss anything?? *********** November 6 PRELIMINARY PRELIMINARY IETF 70 Vancouver Telephone Number Mapping (ENUM) WG Agenda Tuesday... 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 jon.peterson@neustar.biz Agenda Bashing. 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 10 2. Review status RFC 3761bis update. Scott Bradner ( Discussion of work plan.) 15- 20 3. Bernie Hoeneisen - Leading Discussion 20+++++ ( we want to close the issues here) Title : Guide and Template for IANA Registrations of Enumservices Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-05.txt Pages : 23 Date : 2007-10-22 This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) 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-05.tx t 4. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-ietf-enum-x-service-regs-00.txt Pages : 13 Date : 2007-11-05 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-x-service-regs-00.txt 5. IANA Registration for an Enumservice Trunkgroup Author(s) : R. Shockey, T. Creighton Filename : draft-shockey-enum-trunkgroup-00.txt Pages : 10 Date : 2007-11-06 This document registers the Enumservice 'trunk' and subtypes 'sip' and 'tel' using the URI schemes 'sip:' and 'tel:' as per the IANA registration process defined in the ENUM specification RFC 3761 [RFC7761]. RFC 4904 [RFC4904] defines a technique for the conveyance of carrying trunking information in SIP [RFC3261] and or TEL [RFC3966] URI's. This Enumservice provides a mechanism for ENUM databases residing in service provider networks a mechanism to query for that data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shockey-enum-trunkgroup-00.txt 6. Livingood [NEW VERSIONS COMING] Title : IANA Registration for an Enumservice for Video Messaging Author(s) : J. Livingood, et al. Filename : draft-livingood-enum-videomsg-00.txt Pages : 11 Date : 2007-8-30 This document registers the Enumservice type "videomsg" and subtype "sip" using the URI scheme sip, as well as the subtype "tel" using the URI scheme 'tel' as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice is used to facilitate the real-time routing of video communications to a video messaging system. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-livingood-enum-videomsg-00.txt 7. Title : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-01.txt Pages : 17 Date : 2007-10-24 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-softswitch-req-01.txt Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 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 Nov 09 10:29:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqVnH-0006ND-8v; Fri, 09 Nov 2007 10:29:15 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqVnF-0006Gk-Up; Fri, 09 Nov 2007 10:29:13 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqVnF-0006Le-MS; Fri, 09 Nov 2007 10:29:13 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9E5B62AC69; Fri, 9 Nov 2007 15:29:13 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IqVnF-0002yG-DC; Fri, 09 Nov 2007 10:29:13 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 09 Nov 2007 10:29:13 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: enum@ietf.org Subject: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstndata' URI type 'pstn') to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@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 (enum) to consider the following document: - 'IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstndata' URI type 'pstn' ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-11-23. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-07.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14636&rfc_flag=0 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 04:27:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrVZQ-0003Vt-3F; Mon, 12 Nov 2007 04:27:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrVZP-0003Ur-Bd for enum@ietf.org; Mon, 12 Nov 2007 04:27:03 -0500 Received: from anchor-internal-1.mail.demon.net ([195.173.56.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrVZM-0002GB-08 for enum@ietf.org; Mon, 12 Nov 2007 04:27:03 -0500 Received: from finch-staff-1.server.demon.net (finch-staff-1.server.demon.net [193.195.224.1]) by anchor-internal-1.mail.demon.net with ESMTP id lAC9QxQo013623; Mon, 12 Nov 2007 09:26:59 GMT Received: from clive by finch-staff-1.server.demon.net with local (Exim 3.36 #1) id 1IrVZK-00025r-00 for enum@ietf.org; Mon, 12 Nov 2007 09:26:58 +0000 Date: Mon, 12 Nov 2007 09:26:58 +0000 From: "Clive D.W. Feather" To: enum@ietf.org Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstndata' URI type 'pstn') to Proposed Standard Message-ID: <20071112092658.GQ508@finch-staff-1.thus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i X-Spam-Score: 2.2 (++) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 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 > The IESG has received a request from the Telephone Number Mapping WG > (enum) to consider the following document: > - 'IANA Registration for an Enumservice Calling Name Delivery (CNAM) > Information and IANA Registration for URI type 'pstndata' URI type > 'pstn' ' > as a Proposed Standard I don't seem to have seen much discussion on this, but it's clear to me that it is nowhere near ready. * Is the URI type 'pstndata' or 'pstn'? Both are used in the document. * Why is there a need for a new URI type rather than just having a data: URI with appropriate contents? * What are the semantics of in a URI? The examples in section 7 leave it completely confusing. * I believe the 15 character limit may be a North American one - has anyone checked this specification against ETSI standards? [Don't ask me: I'm not familiar enough with them.] * Several parts of the document misspell "available" (including, more than once, spelling it "unavailable"). * Normative reference required to RFC 4234. * In 5.1, cnam is not a media type. * Section 6 paragraph 2: delete the words "in such a way that it may not pass over that country's national borders". That is just one example of a restriction and is not worthy of being separated out. * Section 7: the first two examples cannot be generated from the ABNF. * The examples use an unregistered enumservice type. * Do you have permission from the assignee of +1 505 212 1111 to use it in these documents? [Not a petty comment: see the document's own discussions of privacy.] * Section 8 paragraph 1: this is a North-American-centric comment. Such data is delivered before the first ring. [Plus: "first silent interval" is an ambiguous term with ringing cadences other than those used in NA.] * Sections 6 and 9 are inconsistent in their treatment of e164.arpa. In the former case, should "should not" be "SHOULD NOT"? -- Clive D.W. Feather | Work: | Tel: +44 20 8495 6138 Internet Expert | Home: | Fax: +44 870 051 9937 Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646 THUS plc | | _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 06:08:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrX9W-0002MH-R4; Mon, 12 Nov 2007 06:08:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrX9V-0002Lf-AX for enum@ietf.org; Mon, 12 Nov 2007 06:08:25 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrX9V-0005rU-4g for enum@ietf.org; Mon, 12 Nov 2007 06:08:25 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id F3C4C26E7A; Mon, 12 Nov 2007 11:08:24 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IrX9U-0003JZ-Sj; Mon, 12 Nov 2007 06:08:24 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: lconroy@insensate.co.uk From: IETF I-D Submission Tool Message-Id: Date: Mon, 12 Nov 2007 06:08:24 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: enum@ietf.org, fujiwara@jprs.co.jp Subject: [Enum] New Version Notification for draft-ietf-enum-experiences-08 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 A new version of I-D, draft-ietf-enum-experiences-08.txt has been successfuly submitted by Lawrence Conroy and posted to the IETF repository. Filename: draft-ietf-enum-experiences Revision: 08 Title: ENUM Implementation Issues and Experiences Creation_date: 2007-11-11 WG ID: enum Number_of_pages: 32 Abstract: This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 06:10:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrXB9-0003MR-0a; Mon, 12 Nov 2007 06:10:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrXB6-0003J8-Le; Mon, 12 Nov 2007 06:10:04 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrXB3-0005uP-Vx; Mon, 12 Nov 2007 06:10:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DE79D26E7A; Mon, 12 Nov 2007 11:10:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IrXB3-00072o-QN; Mon, 12 Nov 2007 06:10:01 -0500 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, 12 Nov 2007 06:10:01 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-experiences-08.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 : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-08.txt Pages : 32 Date : 2007-11-12 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-08.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-experiences-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-experiences-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-11-12060821.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-experiences-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-experiences-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-12060821.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 Nov 12 07:59:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrYsT-00018t-Co; Mon, 12 Nov 2007 07:58:57 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrYsS-00018n-Dv for enum@ietf.org; Mon, 12 Nov 2007 07:58:56 -0500 Received: from peregrine.verisign.com ([216.168.239.74]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrYsR-0005SX-Vf for enum@ietf.org; Mon, 12 Nov 2007 07:58:56 -0500 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id lACCq0uV008729; Mon, 12 Nov 2007 07:52:00 -0500 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 Nov 2007 07:58:07 -0500 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] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Date: Mon, 12 Nov 2007 07:58:07 -0500 Message-ID: <046F43A8D79C794FA4733814869CDF07020FD346@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: <20071112092658.GQ508@finch-staff-1.thus.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Thread-Index: AcglDiIH6P6DQw5YTj+KVfMpiI324wAGnv7Q From: "Hollenbeck, Scott" To: "Clive D.W. Feather" , X-OriginalArrivalTime: 12 Nov 2007 12:58:07.0745 (UTC) FILETIME=[ABDFC710:01C8252B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 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 > -----Original Message----- > From: Clive D.W. Feather [mailto:clive@demon.net]=20 > Sent: Monday, November 12, 2007 4:27 AM > To: enum@ietf.org > Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA=20 > Registration for anEnumservice Calling Name Delivery (CNAM)=20 > Information and IANARegistration for URI type 'pstndata' URI=20 > type 'pstn') toProposed Standard >=20 > > The IESG has received a request from the Telephone Number Mapping WG > > (enum) to consider the following document: >=20 > > - 'IANA Registration for an Enumservice Calling Name=20 > Delivery (CNAM)=20 > > Information and IANA Registration for URI type=20 > 'pstndata' URI type=20 > > 'pstn' ' > > as a Proposed Standard >=20 > I don't seem to have seen much discussion on this, but it's=20 > clear to me that it is nowhere near ready. >=20 > * Is the URI type 'pstndata' or 'pstn'? Both are used in the document. I'll have to let one of the other authors answer some of your questions. I produced the ABNF for the URI scheme, though, so I can answer questions about that. In several cases it looks the document editor and the authors got their lines crossed. The ENUM service type is "pstn". The URI scheme name is "pstndata". It looks like the examples need to be fixed to correct the service type. > * Why is there a need for a new URI type rather than just=20 > having a data: > URI with appropriate contents? The data: URI was the original proposal. The reviewing AD (Jon) mandated a change. Apparently there is some desire within the IESG to deprecate use of the data: URI. > * What are the semantics of in a URI?=20 > The examples in section 7 leave it completely confusing. Section 11.2 describes where it came from. The ABNF spec in section 5 should probably be removed and replaced with a forward reference to section 11. > * I believe the 15 character limit may be a North American=20 > one - has anyone checked this specification against ETSI=20 > standards? [Don't ask me: I'm not familiar enough with them.] That's not a North American limit. It's described in ITU-T spec E.164. > * Several parts of the document misspell "available"=20 > (including, more than once, spelling it "unavailable"). That's not always a misspelling, it's occasionally multi-version confusion that should be cleared up with a consistency check. The ABNF is correct. [snip] > * Section 7: the first two examples cannot be generated from the ABNF. Looking at them again I believe there's a ";" missing: pstndata:cnam/+15052121111;;charset=3Dus-ascii,Francois%20Audet should be syntactically valid. content =3D ;charset=3Dus-ascii,Francois%20Audet (mediatype type/subtype is optional and not provided. = ;charset=3Dus-ascii is a parameter, but it needs to be preceded with a ";"). -Scott- _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 12:05:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ircic-0002i9-0B; Mon, 12 Nov 2007 12:05:02 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ircib-0002i0-4P for enum@ietf.org; Mon, 12 Nov 2007 12:05:01 -0500 Received: from anchor-internal-1.mail.demon.net ([195.173.56.100]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ircia-0000QJ-KS for enum@ietf.org; Mon, 12 Nov 2007 12:05:01 -0500 Received: from finch-staff-1.server.demon.net (finch-staff-1.server.demon.net [193.195.224.1]) by anchor-internal-1.mail.demon.net with ESMTP id lACH4wrm029638Mon, 12 Nov 2007 17:04:58 GMT Received: from clive by finch-staff-1.server.demon.net with local (Exim 3.36 #1) id 1IrciX-0009ql-00; Mon, 12 Nov 2007 17:04:57 +0000 Date: Mon, 12 Nov 2007 17:04:57 +0000 From: "Clive D.W. Feather" To: "Hollenbeck, Scott" Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Message-ID: <20071112170457.GT508@finch-staff-1.thus.net> References: <20071112092658.GQ508@finch-staff-1.thus.net> <046F43A8D79C794FA4733814869CDF07020FD346@dul1wnexmb01.vcorp.ad.vrsn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <046F43A8D79C794FA4733814869CDF07020FD346@dul1wnexmb01.vcorp.ad.vrsn.com> User-Agent: Mutt/1.5.3i X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 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 Hollenbeck, Scott said: >> * Why is there a need for a new URI type rather than just >> having a data: >> URI with appropriate contents? > > The data: URI was the original proposal. The reviewing AD (Jon) > mandated a change. Apparently there is some desire within the IESG to > deprecate use of the data: URI. Hmm. Can you point me at any documentation for this? [I've been looking at the data: URI in other contexts.] >> * What are the semantics of in a URI? >> The examples in section 7 leave it completely confusing. > Section 11.2 describes where it came from. That gives me the syntax. But why would I provide one? Why is the caller name for +1 703 555 0100 tied to a URI mentioning +1 505 212 1111? What is going on? >> * I believe the 15 character limit may be a North American >> one - has anyone checked this specification against ETSI >> standards? [Don't ask me: I'm not familiar enough with them.] > That's not a North American limit. It's described in ITU-T spec E.164. Um, aren't you confusing it with the 15 digit limit for numbers (excluding the international access code)? >> * Section 7: the first two examples cannot be generated from the ABNF. > Looking at them again I believe there's a ";" missing: > > pstndata:cnam/+15052121111;;charset=us-ascii,Francois%20Audet > > should be syntactically valid. content = > ;charset=us-ascii,Francois%20Audet Yes, that would seem to be correct. -- Clive D.W. Feather | Work: | Tel: +44 20 8495 6138 Internet Expert | Home: | Fax: +44 870 051 9937 Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646 THUS plc | | _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 12:06:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irck8-0003wj-Pp; Mon, 12 Nov 2007 12:06:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irck7-0003we-SR for enum@ietf.org; Mon, 12 Nov 2007 12:06:35 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Irck7-0000TT-9H for enum@ietf.org; Mon, 12 Nov 2007 12:06:35 -0500 Received: from rshockeyPC ([12.149.74.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lACH69mv005713 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 12 Nov 2007 09:06:11 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Mon, 12 Nov 2007 12:05:56 -0500 Message-ID: <1fa601c8254e$4cdc9360$e695ba20$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcglTgWRHJpnpUPXRLyvDz76ekEqNw== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Subject: [Enum] new ID 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 -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Monday, November 12, 2007 7:30 AM To: i-d-announce@ietf.org Subject: I-D Action:draft-timms-encrypt-naptr-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IANA Registration for Encrypted ENUM Author(s) : B. Timms, et al. Filename : draft-timms-encrypt-naptr-00.txt Pages : 18 Date : 2007-11-12 This document requests IANA registration of the "X-Crypto" Enumservice. This Enumservice indicates that its NAPTR holds a Uniform Resource Identifier that carries encrypted content from the fields of another (unpublished) Protected NAPTR, for use in E.164 Number Mapping (ENUM). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-timms-encrypt-naptr-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-timms-encrypt-naptr-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-timms-encrypt-naptr-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. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 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 Nov 12 12:39:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdFP-0000S8-Ua; Mon, 12 Nov 2007 12:38:55 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdFO-0000Qu-Fk for enum@ietf.org; Mon, 12 Nov 2007 12:38:54 -0500 Received: from osprey.verisign.com ([216.168.239.75]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrdFO-000275-1G for enum@ietf.org; Mon, 12 Nov 2007 12:38:54 -0500 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id lACHWJgJ012832; Mon, 12 Nov 2007 12:32:19 -0500 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 Nov 2007 12:38:05 -0500 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] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Date: Mon, 12 Nov 2007 12:38:08 -0500 Message-ID: <046F43A8D79C794FA4733814869CDF07020FD38E@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: <20071112170457.GT508@finch-staff-1.thus.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Thread-Index: AcglThCjBeyIAcgESlCeTfMMWI82KAAAxu1g From: "Hollenbeck, Scott" To: "Clive D.W. Feather" X-OriginalArrivalTime: 12 Nov 2007 17:38:05.0540 (UTC) FILETIME=[C823E240:01C82552] X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca 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 > -----Original Message----- > From: Clive D.W. Feather [mailto:clive@demon.net]=20 > Sent: Monday, November 12, 2007 12:05 PM > To: Hollenbeck, Scott > Cc: enum@ietf.org > Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA=20 > Registration for anEnumservice Calling Name Delivery (CNAM)=20 > Information and IANARegistration for URI type 'pstndata' URI=20 > type 'pstn') toProposed Standard >=20 > Hollenbeck, Scott said: > >> * Why is there a need for a new URI type rather than just having a=20 > >> data: > >> URI with appropriate contents? > >=20 > > The data: URI was the original proposal. The reviewing AD (Jon)=20 > > mandated a change. Apparently there is some desire within=20 > the IESG to=20 > > deprecate use of the data: URI. >=20 > Hmm. Can you point me at any documentation for this? [I've=20 > been looking at the data: URI in other contexts.] Rich had the exchange with Jon. He'll have to provide that info. Older versions of the ID (available in the usual places) will confirm the change over time, though. > >> * What are the semantics of in a URI?=20 > >> The examples in section 7 leave it completely confusing. > > Section 11.2 describes where it came from. >=20 > That gives me the syntax. But why would I provide one? Why is=20 > the caller name for +1 703 555 0100 tied to a URI mentioning=20 > +1 505 212 1111? What is going on? More for Rich et al. I just devised the syntax. ;-) > >> * I believe the 15 character limit may be a North American=20 > one - has=20 > >> anyone checked this specification against ETSI standards?=20 > [Don't ask=20 > >> me: I'm not familiar enough with them.] > > That's not a North American limit. It's described in ITU-T=20 > spec E.164. >=20 > Um, aren't you confusing it with the 15 digit limit for=20 > numbers (excluding the international access code)? Could be. I always thought that the text in section 5 was referring to E.164's limit, but I could be wrong. -Scott- _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Nov 12 13:49:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IreLV-0007bF-57; Mon, 12 Nov 2007 13:49:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IreLT-0007aK-IG for enum@ietf.org; Mon, 12 Nov 2007 13:49:15 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IreLQ-0008Sy-3K for enum@ietf.org; Mon, 12 Nov 2007 13:49:15 -0500 X-IronPort-AV: E=Sophos;i="4.21,406,1188802800"; d="scan'208";a="415211984" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-2.cisco.com with ESMTP; 12 Nov 2007 10:49:11 -0800 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id lACInBds019293; Mon, 12 Nov 2007 10:49:11 -0800 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id lACImhQQ009559; Mon, 12 Nov 2007 18:49:11 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Nov 2007 13:48:21 -0500 Received: from [161.44.174.244] ([161.44.174.244]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Nov 2007 13:48:21 -0500 Message-ID: <47389FF2.9050009@cisco.com> Date: Mon, 12 Nov 2007 13:48:18 -0500 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Clive D.W. Feather" Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard References: <20071112092658.GQ508@finch-staff-1.thus.net> <046F43A8D79C794FA4733814869CDF07020FD346@dul1wnexmb01.vcorp.ad.vrsn.com> <20071112170457.GT508@finch-staff-1.thus.net> In-Reply-To: <20071112170457.GT508@finch-staff-1.thus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Nov 2007 18:48:21.0163 (UTC) FILETIME=[98D8E7B0:01C8255C] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1023-15540.002 X-TM-AS-Result: No--10.929800-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=555; t=1194893351; x=1195757351; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20 |Subject:=20Re=3A=20[Enum]=20Last=20Call=3A=20draft-ietf-enum-cnam=20(IAN A=20Registration=20for=0A=20anEnumservice=20Calling=20Name=20Delivery=20(C NAM)=20Information=20and=09IANARegistration=0A=20for=20URI=20type=20'pstnd ata'=20URI=20type=20'pstn')=09toProposed=20Standard |Sender:=20; bh=an4pl0YJZsW0zfML4w0w85n93vpZU1VgQcN39ga2xGo=; b=Alwj6pUu2//TVy+erQ9kfTwqxZK9Pqen/UjIfCf/0ELKDRXGjoe6hcpvcQ/xaiviYpUwheBI jY+HF4BF0OtyK0CvW0UVcGHk4Cd99gnGK1cfSi8Y+6PQr+31k0s1e3nELcaj52zRVhA0fC5DKd xNVjtNkatU21T9z8MsTbQXgS8=; Authentication-Results: sj-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: enum@ietf.org, "Hollenbeck, Scott" , Jon Peterson 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 Clive D.W. Feather wrote: > Hollenbeck, Scott said: >>> * Why is there a need for a new URI type rather than just >>> having a data: >>> URI with appropriate contents? >> The data: URI was the original proposal. The reviewing AD (Jon) >> mandated a change. Apparently there is some desire within the IESG to >> deprecate use of the data: URI. > > Hmm. Can you point me at any documentation for this? [I've been looking at > the data: URI in other contexts.] Yes, I would also like info on that. What is the story? Thanks, Paul _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Nov 13 10:15:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrxUS-0002Wq-KL; Tue, 13 Nov 2007 10:15:48 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrxUG-0001ss-AQ; Tue, 13 Nov 2007 10:15:36 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrxUC-0005hR-Gg; Tue, 13 Nov 2007 10:15:36 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 78FA33290A; Tue, 13 Nov 2007 15:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IrxTi-00020y-Cx; Tue, 13 Nov 2007 10:15:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 13 Nov 2007 10:15:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-vmsg-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 : IANA Registration of Enumservices for Voice Messaging and Video Messaging Author(s) : J. Livingood, D. Troshynski Filename : draft-ietf-enum-vmsg-00.txt Pages : 26 Date : 2007-11-13 This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice and/or video communications to a messaging system. This vmsg Enumservice registers three Enumservice types; "voicemsg", "videomsg", and "unifmsg". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-vmsg-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-vmsg-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-vmsg-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: <2007-11-13095519.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-vmsg-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-vmsg-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-13095519.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 Tue Nov 13 11:31:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iryfm-0003VW-CQ; Tue, 13 Nov 2007 11:31:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iryfk-0003VG-BH for enum@ietf.org; Tue, 13 Nov 2007 11:31:32 -0500 Received: from fardach.bofh.priv.at ([88.198.34.164] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iryff-0002kX-Q2 for enum@ietf.org; Tue, 13 Nov 2007 11:31:32 -0500 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id F3D2E4D140; Tue, 13 Nov 2007 17:31:26 +0100 (CET) Date: Tue, 13 Nov 2007 17:31:26 +0100 From: Otmar Lendl To: enum@ietf.org Message-ID: <20071113163126.GB5539@bofh.priv.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Spam-Score: -1.0 (-) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Subject: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-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 I have no idea why this wasn't directly submitted to the ENUM WG. /ol (who is not involved in this proposal) ----- Forwarded message from Internet-Drafts@ietf.org ----- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IANA Registration for Encrypted ENUM Author(s) : B. Timms, et al. Filename : draft-timms-encrypt-naptr-00.txt Pages : 18 Date : 2007-11-12 This document requests IANA registration of the "X-Crypto" Enumservice. This Enumservice indicates that its NAPTR holds a Uniform Resource Identifier that carries encrypted content from the fields of another (unpublished) Protected NAPTR, for use in E.164 Number Mapping (ENUM). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-timms-encrypt-naptr-00.txt ----- End forwarded message ----- _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Nov 13 13:27:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is0Tt-0004lO-Eq; Tue, 13 Nov 2007 13:27:25 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is0Ts-0004lE-5n; Tue, 13 Nov 2007 13:27:24 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is0Tr-0001NS-N1; Tue, 13 Nov 2007 13:27:24 -0500 Received: from rshockeyPC ([12.149.74.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lADIQxx8026471 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Nov 2007 10:27:00 -0800 From: "Richard Shockey" To: , Date: Tue, 13 Nov 2007 13:27:20 -0500 Message-ID: <000201c82622$d522f280$7f68d780$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbidRrsdNW+DQs8QJaqMDsmeXxplw== Content-Language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" Subject: [Enum] ENUM WG Request for Publication - draft-ietf-enum-unused-03.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 request for publication on one ENUM WG document. Title : IANA Registration for Enumservice UNUSED Author(s) : R. Stastny, et al. Filename : draft-ietf-enum-unused-03.txt Pages : 16 Date : 2007-10-29 This document registers the Enumservice "unused" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice may be used to indicate that the E.164 number (or E.164 number range) tied to the domain in which the enclosing NAPTR is published is not allocated or assigned for communications service. When such an indication is provided, an ENUM client can detect calls that will fail "early". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-unused-03.txt A two week WG last call on this document concluded on November 12 2007 The document listed above is being proposed for Proposed Standard This document has been extensively discussed during 2005-2007. 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 From enum-bounces@ietf.org Tue Nov 13 13:32:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is0YR-0001qr-W4; Tue, 13 Nov 2007 13:32:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is0YQ-0001n7-Q5 for enum@ietf.org; Tue, 13 Nov 2007 13:32:06 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is0YN-00073K-4y for enum@ietf.org; Tue, 13 Nov 2007 13:32:06 -0500 Received: from rshockeyPC ([12.149.74.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lADIVKai028181 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Nov 2007 10:31:24 -0800 From: "Richard Shockey" To: "'Paul Kyzivat'" , "'Clive D.W. Feather'" References: <20071112092658.GQ508@finch-staff-1.thus.net> <046F43A8D79C794FA4733814869CDF07020FD346@dul1wnexmb01.vcorp.ad.vrsn.com> <20071112170457.GT508@finch-staff-1.thus.net> <47389FF2.9050009@cisco.com> In-Reply-To: <47389FF2.9050009@cisco.com> Subject: RE: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration for anEnumservice Calling Name Delivery (CNAM) Information and IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed Standard Date: Tue, 13 Nov 2007 13:31:41 -0500 Message-ID: <00d901c82623$765175a0$62f460e0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcglXK2caA+G/m8TRHS0bMR98qtt1QAxnwsg Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: enum@ietf.org, "'Hollenbeck, Scott'" , 'Jon Peterson' 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 Don't ask us, ask the AD's we are just poor working stiffs doing what we're told... The new URI scheme was the path of least resistance for everyone concerned. > -----Original Message----- > From: Paul Kyzivat [mailto:pkyzivat@cisco.com] > Sent: Monday, November 12, 2007 1:48 PM > To: Clive D.W. Feather > Cc: enum@ietf.org; Hollenbeck, Scott; Jon Peterson > Subject: Re: [Enum] Last Call: draft-ietf-enum-cnam (IANA Registration > for anEnumservice Calling Name Delivery (CNAM) Information and > IANARegistration for URI type 'pstndata' URI type 'pstn') toProposed > Standard > > > > Clive D.W. Feather wrote: > > Hollenbeck, Scott said: > >>> * Why is there a need for a new URI type rather than just > >>> having a data: > >>> URI with appropriate contents? > >> The data: URI was the original proposal. The reviewing AD (Jon) > >> mandated a change. Apparently there is some desire within the IESG > to > >> deprecate use of the data: URI. > > > > Hmm. Can you point me at any documentation for this? [I've been > looking at > > the data: URI in other contexts.] > > Yes, I would also like info on that. What is the story? > > Thanks, > Paul > > _______________________________________________ > 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 Nov 13 15:16:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is2Ay-00021a-6f; Tue, 13 Nov 2007 15:16:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is2Aw-0001uM-4e for enum@ietf.org; Tue, 13 Nov 2007 15:15:58 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Is2As-0002ap-Vq for enum@ietf.org; Tue, 13 Nov 2007 15:15:57 -0500 Received: from rshockeyPC ([12.149.74.140]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lADKFR9x024391 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Nov 2007 12:15:29 -0800 From: "Richard Shockey" To: "'Otmar Lendl'" , References: <20071113163126.GB5539@bofh.priv.at> In-Reply-To: <20071113163126.GB5539@bofh.priv.at> Subject: RE: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt Date: Tue, 13 Nov 2007 15:15:48 -0500 Message-ID: <125c01c82631$fc3ae3f0$f4b0abd0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcgmEpt9t5nDR+krSZqRp3s4Ts8BLwAHz/fw Content-Language: en-us X-Spam-Score: -1.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 The chairs have received no request to present this document ..at this point. It's the first we have seen it as well. > -----Original Message----- > From: Otmar Lendl [mailto:lendl@nic.at] > Sent: Tuesday, November 13, 2007 11:31 AM > To: enum@ietf.org > Subject: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt > > > I have no idea why this wasn't directly submitted to the ENUM WG. > > /ol (who is not involved in this proposal) > > ----- Forwarded message from Internet-Drafts@ietf.org ----- > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title : IANA Registration for Encrypted ENUM > Author(s) : B. Timms, et al. > Filename : draft-timms-encrypt-naptr-00.txt > Pages : 18 > Date : 2007-11-12 > > This document requests IANA registration of the "X-Crypto" > Enumservice. This Enumservice indicates that its NAPTR holds a > Uniform Resource Identifier that carries encrypted content from the > fields of another (unpublished) Protected NAPTR, for use in E.164 > Number Mapping (ENUM). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-timms-encrypt-naptr-00.txt > > ----- End forwarded message ----- > > > _______________________________________________ > 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 Nov 13 17:22:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is48n-0003xW-Hp; Tue, 13 Nov 2007 17:21:53 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is48m-0003t8-Fl for enum@ietf.org; Tue, 13 Nov 2007 17:21:52 -0500 Received: from norman.insensate.co.uk ([213.152.49.123] helo=insensate.co.uk) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is48l-0001t5-Vz for enum@ietf.org; Tue, 13 Nov 2007 17:21:52 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id 40DCA63CB0; Tue, 13 Nov 2007 22:21:50 +0000 (GMT) In-Reply-To: <20071113163126.GB5539@bofh.priv.at> References: <20071113163126.GB5539@bofh.priv.at> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2ED8E181-5A5E-43FB-B34E-AB31337C70A5@insensate.co.uk> Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt Date: Tue, 13 Nov 2007 22:21:40 +0000 To: Otmar Lendl X-Mailer: Apple Mail (2.752.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 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 Otmar, folks, I suspect this was shipped using the ID sumbission tool. Having shipped the next version of Experiences using the tool, I noticed that there was no way to put in a cover note to ID Editor, and there seemed to be no way to indicate any WG. Experiences is a WG draft, so this MAY have been because the tool Assumed it knew at which WG to aim this. However, I certainly didn't see any way to tell the tool to target a draft at any WG (or WGs). Given that Richard looks to have had to trawl through all the IDs to post ones of interest to the WG (for which MANY THANKS), this might be a tool issue - it doesn't know where to send 'em. all the best, Lawrence On 13 Nov 2007, at 16:31, Otmar Lendl wrote: > > I have no idea why this wasn't directly submitted to the ENUM WG. > > /ol (who is not involved in this proposal) > > ----- Forwarded message from Internet-Drafts@ietf.org ----- > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title : IANA Registration for Encrypted ENUM > Author(s) : B. Timms, et al. > Filename : draft-timms-encrypt-naptr-00.txt > Pages : 18 > Date : 2007-11-12 > > This document requests IANA registration of the "X-Crypto" > Enumservice. This Enumservice indicates that its NAPTR holds a > Uniform Resource Identifier that carries encrypted content from the > fields of another (unpublished) Protected NAPTR, for use in E.164 > Number Mapping (ENUM). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-timms-encrypt-naptr-00.txt > > ----- End forwarded message ----- > > > _______________________________________________ > 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 Nov 13 17:29:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is4GD-00038q-I2; Tue, 13 Nov 2007 17:29:33 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is4GC-00038S-82 for enum@ietf.org; Tue, 13 Nov 2007 17:29:32 -0500 Received: from ebru.winwebhosting.com ([74.52.236.50]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is4GB-00022j-OZ for enum@ietf.org; Tue, 13 Nov 2007 17:29:32 -0500 Received: from [209.173.53.233] (helo=BROSLT41xp) by ebru.winwebhosting.com with esmtpa (Exim 4.68) (envelope-from ) id 1Is4G2-0008Hb-0u; Tue, 13 Nov 2007 16:29:22 -0600 From: "Brian Rosen" To: "'lconroy'" , "'Otmar Lendl'" References: <20071113163126.GB5539@bofh.priv.at> <2ED8E181-5A5E-43FB-B34E-AB31337C70A5@insensate.co.uk> Subject: RE: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt Date: Tue, 13 Nov 2007 17:29:25 -0500 Message-ID: <010c01c82644$a709ad40$640fa8c0@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.3198 In-Reply-To: <2ED8E181-5A5E-43FB-B34E-AB31337C70A5@insensate.co.uk> Thread-Index: AcgmQ591qe/aOxI2THi8Q6+FIJp1BAAAM/Mg X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ebru.winwebhosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brianrosen.net X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 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 Neither did the ID-Editor. An individual draft never was announced to the work group. The author has to do that. Only drafts starting with draft-ietf-enum would ever have been announced by the ID-Editor. The tool duplicates that practice. Brian > -----Original Message----- > From: lconroy [mailto:lconroy@insensate.co.uk] > Sent: Tuesday, November 13, 2007 5:22 PM > To: Otmar Lendl > Cc: enum@ietf.org > Subject: Re: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt > > Hi Otmar, folks, > I suspect this was shipped using the ID sumbission tool. > > Having shipped the next version of Experiences using the tool, > I noticed that there was no way to put in a cover note to > ID Editor, and there seemed to be no way to indicate any WG. > > Experiences is a WG draft, so this MAY have been because the > tool Assumed it knew at which WG to aim this. > However, I certainly didn't see any way to tell the tool to > target a draft at any WG (or WGs). > > Given that Richard looks to have had to trawl through all the > IDs to post ones of interest to the WG (for which MANY THANKS), > this might be a tool issue - it doesn't know where to send 'em. > > all the best, > Lawrence > > > On 13 Nov 2007, at 16:31, Otmar Lendl wrote: > > > > > I have no idea why this wasn't directly submitted to the ENUM WG. > > > > /ol (who is not involved in this proposal) > > > > ----- Forwarded message from Internet-Drafts@ietf.org ----- > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > directories. > > > > Title : IANA Registration for Encrypted ENUM > > Author(s) : B. Timms, et al. > > Filename : draft-timms-encrypt-naptr-00.txt > > Pages : 18 > > Date : 2007-11-12 > > > > This document requests IANA registration of the "X-Crypto" > > Enumservice. This Enumservice indicates that its NAPTR holds a > > Uniform Resource Identifier that carries encrypted content from the > > fields of another (unpublished) Protected NAPTR, for use in E.164 > > Number Mapping (ENUM). > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-timms-encrypt-naptr-00.txt > > > > ----- End forwarded message ----- > > > > > > _______________________________________________ > > 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 Wed Nov 14 10:45:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKQn-0008Ap-9H; Wed, 14 Nov 2007 10:45:33 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKQl-00088N-L8 for enum@ietf.org; Wed, 14 Nov 2007 10:45:31 -0500 Received: from smtp.telnic.org.uk ([195.54.244.3] helo=telnic.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsKQi-0007Nc-8y for enum@ietf.org; Wed, 14 Nov 2007 10:45:31 -0500 Received: from host128.telnic.org (account btimms [172.16.1.128] verified) by telnic.org (CommuniGate Pro SMTP 5.0.9) with ESMTPSA id 374209; Wed, 14 Nov 2007 15:45:27 +0000 Message-Id: From: Ben Timms To: lendl@nic.at, Lawrence Conroy , br@brianrosen.net, richard@shockey.us Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: RE: [Enum] FYI: I-D Action:draft-timms-encrypt-naptr-00.txt Date: Wed, 14 Nov 2007 15:45:27 +0000 X-Mailer: Apple Mail (2.912) 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 Richard, Otmar, Brian, folks, This is indeed intended for this list. Apologies for not realising I had to manually announce it. This is an experimental system that we're using in-house and I assumed it will be part of the updated enumservice registration process, am I correct? Jim Reid will be in Vancouver, but we assume this will wait for the new process to be in place. Kind regards, Ben Timms _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Nov 14 10:53:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKYE-0002H0-8A; Wed, 14 Nov 2007 10:53:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKYD-0002GL-OV for enum@ietf.org; Wed, 14 Nov 2007 10:53:13 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsKYA-0008AQ-Iz for enum@ietf.org; Wed, 14 Nov 2007 10:53:13 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns0.neustar.com (Postfix) with ESMTP id 6E81C32987; Wed, 14 Nov 2007 15:52:40 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IsKXg-0003lb-Be; Wed, 14 Nov 2007 10:52:40 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: alexander.mayrhofer@enum.at From: IETF I-D Submission Tool Message-Id: Date: Wed, 14 Nov 2007 10:52:40 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: enum@ietf.org, jason_livingood@cable.comcast.com, bernhard.hoeneisen@switch.ch Subject: [Enum] New Version Notification for draft-ietf-enum-enumservices-guide-06 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 A new version of I-D, draft-ietf-enum-enumservices-guide-06.txt has been successfuly submitted by Alexander Mayrhofer and posted to the IETF repository. Filename: draft-ietf-enum-enumservices-guide Revision: 06 Title: Guide and Template for IANA Registrations of Enumservices Creation_date: 2007-11-14 WG ID: enum Number_of_pages: 29 Abstract: This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) services. It is also to be used for updates of existing IANA registrations. The IETF Secretariat. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Nov 14 11:00:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKfM-0003jw-I4; Wed, 14 Nov 2007 11:00:36 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsKfK-0003f3-KT; Wed, 14 Nov 2007 11:00:34 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsKfI-0000Vk-9G; Wed, 14 Nov 2007 11:00:34 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 3B9D132987; Wed, 14 Nov 2007 16:00:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IsKeo-00083H-4O; Wed, 14 Nov 2007 11:00:02 -0500 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, 14 Nov 2007 11:00:02 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: enum@ietf.org Subject: [Enum] I-D Action:draft-ietf-enum-enumservices-guide-06.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 Enumservices Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-06.txt Pages : 29 Date : 2007-11-14 This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) 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-06.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-06.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-06.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: <2007-11-14105238.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-enumservices-guide-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-enumservices-guide-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-14105238.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 Nov 14 11:54:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsLVO-00055x-A6; Wed, 14 Nov 2007 11:54:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsLVN-00055n-60 for enum@ietf.org; Wed, 14 Nov 2007 11:54:21 -0500 Received: from mail.songbird.com ([208.184.79.10]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsLVK-0007Tc-Dt for enum@ietf.org; Wed, 14 Nov 2007 11:54:21 -0500 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lAEGrqgg031860 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 14 Nov 2007 08:53:53 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Wed, 14 Nov 2007 11:54:10 -0500 Message-ID: <0dfa01c826de$fb16f4c0$f144de40$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acgm3vorYPd6+ctwRDGfzjj0Xcssog== Content-Language: en-us X-Spam-Score: -1.0 (-) X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56 Subject: [Enum] Current AGANDA Draft ... 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 review and comment etc. PRELIMINARY PRELIMINARY 14 NOV 07 IETF 70 Vancouver Telephone Number Mapping (ENUM) WG Agenda 1130-1300 Break 1300-1500 Afternoon Session I Salon D/E RAI enum Telephone Number Mapping WG 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 jon.peterson@neustar.biz Agenda Bashing. 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 10 2. Review status RFC 3761bis update. Scott Bradner ( Discussion of work plan.) 15- 20 3. Bernie Hoeneisen - Leading Discussion 20+ Title : Guide and Template for IANA Registrations of Enumservices Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-06.txt Pages : 29 Date : 2007-11-14 This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) 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-06.tx t 4. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-ietf-enum-x-service-regs-00.txt Pages : 13 Date : 2007-11-05 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-x-service-regs-00.txt 5. IANA Registration for an Enumservice Trunkgroup Author(s) : R. Shockey, T. Creighton Filename : draft-shockey-enum-trunkgroup-00.txt Pages : 10 Date : 2007-11-06 This document registers the Enumservice 'trunk' and subtypes 'sip' and 'tel' using the URI schemes 'sip:' and 'tel:' as per the IANA registration process defined in the ENUM specification RFC 3761 [RFC7761]. RFC 4904 [RFC4904] defines a technique for the conveyance of carrying trunking information in SIP [RFC3261] and or TEL [RFC3966] URI's. This Enumservice provides a mechanism for ENUM databases residing in service provider networks a mechanism to query for that data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shockey-enum-trunkgroup-00.txt 6. Title : IANA Registration of Enumservices for Voice Messaging and Video Messaging Author(s) : J. Livingood, D. Troshynski Filename : draft-ietf-enum-vmsg-00.txt Pages : 26 Date : 2007-11-13 This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice and/or video communications to a messaging system. This vmsg Enumservice registers three Enumservice types; "voicemsg", "videomsg", and "unifmsg". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-vmsg-00.txt 7. Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-08.txt Pages : 32 Date : 2007-11-12 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-08.txt 8. Title : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-01.txt Pages : 17 Date : 2007-10-24 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-softswitch-req-01.txt Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 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 Nov 19 20:50:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEv-0000p1-De; Mon, 19 Nov 2007 20:49:25 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEu-0000om-3S; Mon, 19 Nov 2007 20:49:24 -0500 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuIEq-0002r0-MV; Mon, 19 Nov 2007 20:49:24 -0500 Received: by bosco.isi.edu (Postfix, from userid 70) id 59C99F5C4A; Mon, 19 Nov 2007 17:49:20 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20071120014920.59C99F5C4A@bosco.isi.edu> Date: Mon, 19 Nov 2007 17:49:20 -0800 (PST) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: enum@ietf.org, rfc-editor@rfc-editor.org Subject: [Enum] RFC 5067 on Infrastructure ENUM Requirements 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 A new Request for Comments is now available in online RFC libraries. RFC 5067 Title: Infrastructure ENUM Requirements Author: S. Lind, P. Pfautz Status: Informational Date: November 2007 Mailbox: sdlind@att.com, ppfautz@att.com Pages: 7 Characters: 14311 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-infrastructure-enum-reqs-04.txt URL: http://www.rfc-editor.org/rfc/rfc5067.txt This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) This memo provides information for the Internet community. This document is a product of the Telephone Number Mapping Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Nov 23 10:45:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvaiV-0008BI-U4; Fri, 23 Nov 2007 10:45:19 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvaiU-000834-Du for enum@ietf.org; Fri, 23 Nov 2007 10:45:18 -0500 Received: from mail.songbird.com ([208.184.79.10]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IvaiT-00051C-My for enum@ietf.org; Fri, 23 Nov 2007 10:45:18 -0500 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by mail.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id lANFifcr000324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 23 Nov 2007 07:44:53 -0800 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Fri, 23 Nov 2007 10:44:36 -0500 Message-ID: <0cca01c82de7$c77a1060$566e3120$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acgt57/8zVZJlr8kR7OCaptsyCaASw== Content-language: en-us X-Spam-Score: 0.0 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 Subject: [Enum] FINAL Agenda ENUM WG IETF 70 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 FINAL FINAL IETF 70 Vancouver Telephone Number Mapping (ENUM) WG Agenda 1130-1300 Break 1300-1500 Afternoon Session I Salon D/E RAI enum Telephone Number Mapping WG 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 jon.peterson@neustar.biz Agenda Bashing. 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 10 2. Review status RFC 3761bis update. Scott Bradner ( Discussion of work plan.) 15- 20 3. Bernie Hoeneisen - Leading Discussion 20+ Title : Guide and Template for IANA Registrations of Enumservices Author(s) : B. Hoeneisen, et al. Filename : draft-ietf-enum-enumservices-guide-06.txt Pages : 29 Date : 2007-11-14 This document provides a guide to and template for the creation of new IANA registrations of ENUM (E.164 Number Mapping) 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-06.tx t 4. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-ietf-enum-x-service-regs-00.txt Pages : 13 Date : 2007-11-05 This document provides a guide to the creation of new IANA registrations of experimental, private or trial ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental, private or trial Enumservice (X-Enumservice) registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-x-service-regs-00.txt 5. IANA Registration for an Enumservice Trunkgroup Author(s) : R. Shockey, T. Creighton Filename : draft-shockey-enum-trunkgroup-00.txt Pages : 10 Date : 2007-11-06 This document registers the Enumservice 'trunk' and subtypes 'sip' and 'tel' using the URI schemes 'sip:' and 'tel:' as per the IANA registration process defined in the ENUM specification RFC 3761 [RFC7761]. RFC 4904 [RFC4904] defines a technique for the conveyance of carrying trunking information in SIP [RFC3261] and or TEL [RFC3966] URI's. This Enumservice provides a mechanism for ENUM databases residing in service provider networks a mechanism to query for that data. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shockey-enum-trunkgroup-00.txt 6. Title : IANA Registration of Enumservices for Voice Messaging and Video Messaging Author(s) : J. Livingood, D. Troshynski Filename : draft-ietf-enum-vmsg-00.txt Pages : 26 Date : 2007-11-13 This document registers the Enumservice named "vmsg", which is used to facilitate the real-time routing of voice and/or video communications to a messaging system. This vmsg Enumservice registers three Enumservice types; "voicemsg", "videomsg", and "unifmsg". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-vmsg-00.txt 7. Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-08.txt Pages : 32 Date : 2007-11-12 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-08.txt 8. Title : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-01.txt Pages : 17 Date : 2007-10-24 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-softswitch-req-01.txt Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 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 Sat Nov 24 06:38:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvtKn-00019I-2M; Sat, 24 Nov 2007 06:38:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvtKl-000195-KS; Sat, 24 Nov 2007 06:38:03 -0500 Received: from [202.99.23.227] (helo=people.com.cn) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IvtKi-00073b-Ir; Sat, 24 Nov 2007 06:38:03 -0500 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm34747481af9; Sat, 24 Nov 2007 19:50:54 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm113474264c0; Tue, 20 Nov 2007 10:05:43 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 20 Nov 2007 10:05:43 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEx-0000po-18; Mon, 19 Nov 2007 20:49:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuIEu-0000om-3S; Mon, 19 Nov 2007 20:49:24 -0500 Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuIEq-0002r0-MV; Mon, 19 Nov 2007 20:49:24 -0500 Received: by bosco.isi.edu (Postfix, from userid 70) id 59C99F5C4A; Mon, 19 Nov 2007 17:49:20 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20071120014920.59C99F5C4A@bosco.isi.edu> Date: Mon, 19 Nov 2007 17:49:20 -0800 (PST) X-Spam-Score: -15.0 (---------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: rfc-editor@rfc-editor.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: enum@ietf.org, rfc-editor@rfc-editor.org Subject: [Enum] RFC 5067 on Infrastructure ENUM Requirements X-BeenThere: enum@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 5067 Title: Infrastructure ENUM Requirements Author: S. Lind, P. Pfautz Status: Informational Date: November 2007 Mailbox: sdlind@att.com, ppfautz@att.com Pages: 7 Characters: 14311 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-enum-infrastructure-enum-reqs-04.txt URL: http://www.rfc-editor.org/rfc/rfc5067.txt This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) This memo provides information for the Internet community. This document is a product of the Telephone Number Mapping Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Nov 30 04:06:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iy1ol-0003AT-FW; Fri, 30 Nov 2007 04:05:51 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iy1ok-0003A0-1w for enum@ietf.org; Fri, 30 Nov 2007 04:05:50 -0500 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iy1oj-00069c-7k for enum@ietf.org; Fri, 30 Nov 2007 04:05:49 -0500 Received: from [192.168.0.130] ([::ffff:86.59.59.32]) (AUTH: LOGIN axelm) by pahula with esmtp; Fri, 30 Nov 2007 10:05:45 +0100 id 0000C0AA.474FD26A.00004306 Message-ID: <474FD21E.4040309@enum.at> Date: Fri, 30 Nov 2007 10:04:30 +0100 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) 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: 14582b0692e7f70ce7111d04db3781c8 Subject: [Enum] preperation for Enumservices guide discussion 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 Dear ENUM WG This is to prepare yourself for the discussion and decision making about draft-ietf-enum-enumservices-guide-06 during the meeting in Vancouver. We have 3 questions that we want a FINAL decision about before the end of the ENUM WG session in Vancouver (Or, at least after a couple of pints over the course of the week). * * * Issue 1) Which is the process we are gone specify for future ENUM service registrations? A) Author -> IESG -> Expert Review -> IESG -> IANA -> Publication B) Author -> Expert Review -> IESG -> IANA -> Publication C) Author -> IANA -> Expert Review -> IANA -> Publication D) Author -> IESG -> IANA -> Expert Review -> IANA -> Publication A) would require the least changes from well defined processes in the IETF and it does not require major changes of RFC 3761. The responsibilities are rather clear. But it puts more burden on the IESG. B) is the one documented in the current revision of draft-ietf-enum-enumservices-guide-06.txt. This is a new process, not spread in the IETF. Responsibilities are anything but clear. C) If we want to apply such a simple process for Enumservice registrations, a major change in RFC 3761 is needed, as RFC 3761 states: "Enumservice registrations needs to be Standards Track, Experimental or BCP". But this process would be the most lightweiht one. D) At the moment I do not see any compelling reason to use such a process. * * * Issue 2) Subtypes and URI schemes The question here is how URI schemes and Enumservice type/subypes may be combined when defining an Enumservice. We have the following options (if you have other ideas, speak up NOW): a) Only one URI scheme per subtype? b) Only allow more than one URI scheme per subtype, if one is the normal and the other the secure variant (e.g. sip and sips). c) Allow any number of URI schemes with and subtype? d) Allow only those URI schemes to be combined in one subtype that are mandatory to implement for all clients? Details: The problem with combining URI schemes and subtypes is that clients must not "look at the URI scheme" before they select a NAPTR - they can only look at type/subtype. So in case we allow the mixture of URI schemes into subtype, and not all of them are mandatory, a client can end up choosing the "wrong" NAPTR, because it doesn't support the URI scheme. For example, consider the following situation: - The protocol/service itself can use URI schemes "fooA", "fooB", "fooC", with "fooC" not mandatory to implement. - Client supports URI schemes "fooA", "fooB". - The Enumservice defines the type "x-service" to allow all three URI schemes. - There are two NAPTRs, one with "better" preferrence has "x-service -> fooC", and the other one has "x-service -> fooA". - The client now somehow plays "russian roulette" - because it can't look at the URI schemes in the records, and once it has chosen one record, it can't "go back". So if it chooses the first record, it can't make use of the service, because fooC is not supported. Currently, we have option b) in the draft. None of those solutions is perfect, as some might require revising existing Enumservices. * * * Issue 3) Are we going to include the Enumservice classification in the IANA template for ENUM service registrations? That is the classification of "procotol" / "data format" / "application" Enumservice. * * * Please think about it and comment latest at the ENUM WG in vancouver or hold peace forever... cheers, Alex and Bernie _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum