From exim@www1.ietf.org Wed Oct 1 04:06:44 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02250 for ; Wed, 1 Oct 2003 04:06:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4c04-0007io-51 for enum-archive@odin.ietf.org; Wed, 01 Oct 2003 04:06:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9186Jxf029624 for enum-archive@odin.ietf.org; Wed, 1 Oct 2003 04:06:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4bzl-0007gl-Sj; Wed, 01 Oct 2003 04:06:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A4bys-0007f9-PT for enum@optimus.ietf.org; Wed, 01 Oct 2003 04:05:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02220 for ; Wed, 1 Oct 2003 04:05:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A4byq-0003iL-00 for enum@ietf.org; Wed, 01 Oct 2003 04:05:04 -0400 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx with smtp (Exim 4.12) id 1A4byp-0003hs-00 for enum@ietf.org; Wed, 01 Oct 2003 04:05:03 -0400 content-class: urn:content-classes:message Subject: RE: [Enum] I'm looking for ideas on the Agenda for Minneapolis MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 1 Oct 2003 10:09:28 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: <06CF906FE3998C4E944213062009F162233898@oefeg-s02.oefeg.loc> Thread-Topic: [Enum] I'm looking for ideas on the Agenda for Minneapolis Thread-Index: AcOGlkuqp/z3QP8wTwiBJaBr9KJT9ABWo5Fw From: "Stastny Richard" To: "Richard Shockey" , Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Hi folks, being relatively new to IETF and not knowing the inner procedures of IETF and IAB well enough, a status report of the IDs in the queue would be nice, eventually by one of the responsible area directors. I would be interested eg in getting answers to questions like: Why is rfc2916bis not released yet as RFC? What is the problem, if any? How can it be solved? When is the release planned? From my working in other not so advanced bodies I am used to get milestones for release dates and reasons if a date is shifted, not the other way round (no dates and no reasons), but as I said above: I am new here. So maybe you could set aside 5 minutes? Richard > -----Original Message----- > From: Richard Shockey [mailto:richard@shockey.us]=20 > Sent: Monday, September 29, 2003 4:20 PM > To: enum@ietf.org > Subject: [Enum] I'm looking for ideas on the Agenda for Minneapolis.. >=20 >=20 >=20 > What new ID's should we anticipate? >=20 > What interest is there in provisioning issues etc? >=20 > I'd like to start planning as soon as reasonably possible. >=20 >=20 > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Senior Manager, Strategic Technology=20 > Initiatives NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, =20 > Fax: +1 815.333.1237 or=20 ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 3 09:35:54 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06505 for ; Fri, 3 Oct 2003 09:35:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5Q5k-0005wO-Ez for enum-archive@odin.ietf.org; Fri, 03 Oct 2003 09:35:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93DZWvE022832 for enum-archive@odin.ietf.org; Fri, 3 Oct 2003 09:35:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5Q5G-0005tU-QN; Fri, 03 Oct 2003 09:35:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5Q4S-0005sv-FZ for enum@optimus.ietf.org; Fri, 03 Oct 2003 09:34:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06458 for ; Fri, 3 Oct 2003 09:34:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5Q4Q-0000r7-00 for enum@ietf.org; Fri, 03 Oct 2003 09:34:10 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A5Q4P-0000qW-00 for enum@ietf.org; Fri, 03 Oct 2003 09:34:09 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 03 Oct 2003 15:32:03 +0200 Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h93DXXHR026404; Fri, 3 Oct 2003 15:33:34 +0200 (MET DST) Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 15:33:37 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 15:33:36 +0200 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> Content-Transfer-Encoding: 7bit Cc: Jon Peterson , rich.shockey@neustar.biz, Michael Mealling , enum@ietf.org From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Fri, 3 Oct 2003 15:33:35 +0200 To: Ted Hardie , Allison Mankin X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 03 Oct 2003 13:33:36.0610 (UTC) FILETIME=[F2BC0C20:01C389B2] Content-Transfer-Encoding: 7bit Subject: [Enum] Re: refresh: IESG review of rfc2916bis Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Suggested RFC-Editor notes, which if ok should make it possible to have 2916bis become an RFC. paf > Ted Hardie's Discuss comments: > > I went back forth as to whether these were serious nits > or a mild discuss. The tired lady mentioned in the nit > related to section 2.1 was the deciding factor. In other > words, I think these should be fixed, but pushback is > welcome. > > > In the introduction: > > "like delegation through NS records and NAPTR records, one can > look up > what services are available for a specific domain name" > > Would it not make more sense to say, "what services are associated > with a > specific E.164 number"? This is not general to all domain names. Comment: I think it is ok to make this change. The reason it talks about domain names in the second part of this very long sentence is because ENUM really is a two-step process. But, of course the whole algorithm doesn't work if the input is an E.164 number. [1] In the introduction: OLD: Through transformation of International Public Telecommunication Numbers in the international format [4], called within this document E.164 numbers, into DNS names and the use of existing DNS services like delegation through NS records and NAPTR records, one can look up what services are available for a specific domain name in a decentralized way with distributed management of the different levels in the lookup process. NEW: Through transformation of International Public Telecommunication Numbers in the international format [4], called within this document E.164 numbers, into DNS names and the use of existing DNS services like delegation through NS records and NAPTR records, one can look up what services are available for a specific E.164 in a decentralized way with distributed management of the different levels in the lookup process. > For Section 1.2, the language seems less than clear. How about: > > This document describes the operation of these mechanisms in the > context > of numbers allocated according to the ITU-T recommendation E.164. > The > same mechanisms might be used for private dialing plans. If the > mechanisms are re-used, the suffix used for the private dialing > plan > MUST NOT be e164.arpa, to avoid conflict with this specification. > Parties to the private dialing plan will need to know the the > suffix > used by their private dialing plan for correct operation of these > mechanisms. Further, the application unique string used SHOULD be > the full number as specified, but without the leading '+' Comment: It is important it is explicitly stated that the mechanism using e164.arpa is called "ENUM". I think this is lost in the suggested text. I therefore suggest using the suggested text plus an addition at the end about use of the term "ENUM". In section 1.2: OLD: This document specifies how "ENUM" works, that is how to handle numbers allocated according to the ITU-T recommendation E.164. But, a similar mechanism can be used also for other numbers, such as private dialing plans. To implement that (a) the suffix MUST be selected, MUST NOT be e164.arpa, MUST be known for all parties using the same dialing plan (b) the application unique string SHOULD be the full number as specified but without the leading '+'. NEW: This document describes the operation of these mechanisms in the context of numbers allocated according to the ITU-T recommendation E.164. The same mechanisms might be used for private dialing plans. If the mechanisms are re-used, the suffix used for the private dialing plan MUST NOT be e164.arpa, to avoid conflict with this specification. Parties to the private dialing plan will need to know the the suffix used by their private dialing plan for correct operation of these mechanisms. Further, the application unique string used SHOULD be the full number as specified, but without the leading '+', and such private use MUST NOT be called "ENUM". > In Section 2.1, the draft says: > > > For example, the E.164 number could start out as "+1-770-923-9595". > To ensure that no syntactic sugar is allowed into the AUS, all > non-digits except for "+" are removed, yielding "+17709239595". > > I'm not sure "syntactic sugar" is clear. Is the AUS a gas tank? :) > Frankly, I'd suggest deleting the second paragraph, as I don't think > it adds > anything, but if it's kept, I'd suggest updating it to "the E.164 > number could > be represented to a user as". I'd also suggest using a known-to-be > invalid > number. A tired lady answer this number when I called it, > and she didn't know anything about this draft. The telephone number is changed to the one of the IETF Secretariat. Section 2.1: OLD: For example, the E.164 number could start out as "+1-770-923-9595". To ensure that no syntactic sugar is allowed into the AUS, all non-digits except for "+" are removed, yielding "+17709239595". NEW: For example, the E.164 number could start out as "+1-703-620-8990". All non-digits except for "+" are removed, yielding "+17036208990". > In section 2.4.2.1, the draft says: > > The mapping, if any, have > to be made explicit in the specification for the Enumservice > itself. > A registration of a specific Type also have to specify the Subtypes > allowed. > > I think the grammar is off there. how about: "the mapping, if any, > must be made explicit"? Section 2.4.2.1: OLD: Enumservice specifications contain the functional specification (i.e. what it can be used for), the valid protocols, and the URI schemes that may be returned. Note that there is no implicit mapping between the textual string "type" or "subtype" in the grammar for the Enumservice and URI schemes or protocols. The mapping, if any, have to be made explicit in the specification for the Enumservice itself. A registration of a specific Type also have to specify the Subtypes allowed. NEW: Enumservice specifications contain the functional specification (i.e. what it can be used for), the valid protocols, and the URI schemes that may be returned. Note that there is no implicit mapping between the textual string "type" or "subtype" in the grammar for the Enumservice and URI schemes or protocols. The mapping, if any, must be made explicit in the specification for the Enumservice itself. A registration of a specific Type also have to specify the Subtypes allowed. > For the IANA consideration, the work requested by the first two > paragraphs > is done. I think that it would be better to change it to note that > the obsoleted RFC requested these, and to give a pointer to the current > IAB/ITU-T agreement. Comment: The 2nd paragraph is added relative to RFC 2916, and is what I think a proper addition. The first can be changed though. Section 5: OLD: This memo requests that the IANA delegate the E164.ARPA domain following instructions to be provided by the IAB. Names within this zone are to be delegated to parties according to the ITU-T Recommendation E.164. The names allocated should be hierarchic in accordance with ITU-T Recommendation E.164, and the codes should assigned in accordance with that Recommendation. NEW: RFC 2916 (which this document replaces) requested IANA to delegate the E164.ARPA domain following instructions to be provided by the IAB. The domain was delegated according to those instructions. Names within this zone are to be delegated to parties according to the ITU-T Recommendation E.164. The names allocated should be hierarchic in accordance with ITU-T Recommendation E.164, and the codes should assigned in accordance with that Recommendation. > P.S. Here is what Ted said about Section 2.5 but I believe we should > leave > it as is: > > I'm concerned that section 2.5 might cause as much confusion as it > prevents. How about replacing the whole thing with "The ENUM algorithm > always returns a single rule. Specific applications may have > application-specific knowledge or facilities that allow them to > present multiple results or speed selection, but these should > never change the operation of the algorithm." Good idea. Section 2.5: OLD: There has been some confusion over what exactly an ENUM Resolver returns and what relation that has to the 'Note 1' section in RFC 3402. On first reading it seems as though it might be possible for an ENUM Resolver to return two Rules. The answer to that depends on which of two possible definitions you use for an ENUM Resolver: The first type of resolver can be called an 'intelligent' resolver. It understands its target application very well. In that case the test done at the beginning of Step 4 in the algorithm is a very complex one. It can include call backs to the calling thread, GUI events, etc. Its at this point that a client can be presented with the idea of "multiple Rules" because its at this step that Order is understood relative to the other ordered records. In this case the ENUM Resolver still returns one Rule to the calling application but its smart enough internally that it can apply application specific knowledge to the Rule selection test. The other type of resolver can be called a 'dumb' or 'driven' resolver. It is generic in the sense that there is no internal application knowledge. It is run from the 'outside' by a smart application that changes the selection criteria that are fed to the ENUM Resolver before it starts its resolution task. It returns one Rule only and the caller has to determine if that Rule is OK or not. If it isn't then it re-runs the resolver with a new set of selection criteria. Some might consider the combination of this dumb resolver and the application that's driving it as some uber-ENUM-Resolver. In that case it can "return more than one Rule" because it can simply re-run the algorithm several times to collect an appropriate set of Rules. But that uber-ENUM-Resolver is stretching the definition of an ENUM Resolver to the point of being unrecognizable. The key point is that the Algorithm only returns one Rule. NEW: There has been some confusion over what exactly an ENUM Resolver returns and what relation that has to the 'Note 1' section in RFC 3402. On first reading it seems as though it might be possible for an ENUM Resolver to return two Rules. The ENUM algorithm always returns a single rule. Specific applications may have application-specific knowledge or facilities that allow them to present multiple results or speed selection, but these should never change the operation of the algorithm. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 3 09:53:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07029 for ; Fri, 3 Oct 2003 09:53:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5QMi-0006mA-Cm for enum-archive@odin.ietf.org; Fri, 03 Oct 2003 09:53:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93Dr4bZ026046 for enum-archive@odin.ietf.org; Fri, 3 Oct 2003 09:53:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5QMe-0006l3-Cv; Fri, 03 Oct 2003 09:53:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5QM5-0006iJ-Kl for enum@optimus.ietf.org; Fri, 03 Oct 2003 09:52:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06994 for ; Fri, 3 Oct 2003 09:52:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5QM3-00012u-00 for enum@ietf.org; Fri, 03 Oct 2003 09:52:23 -0400 Received: from [209.10.143.221] (helo=neonym.net) by ietf-mx with esmtp (Exim 4.12) id 1A5QM2-00012r-00 for enum@ietf.org; Fri, 03 Oct 2003 09:52:23 -0400 Received: from [207.120.28.115] ([::ffff:207.120.28.115]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Thu, 02 Oct 2003 19:37:25 -0400 From: Michael Mealling To: "Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?=" Cc: Ted Hardie , Allison Mankin , Jon Peterson , rich.shockey@neustar.biz, enum@ietf.org In-Reply-To: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> Organization: Harriman Heavy Industries, Inc. Message-Id: <1065189091.14758.104.camel@blackdell.neonym.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.2.2 Date: 03 Oct 2003 09:51:31 -0400 X-Mime-Autoconverted: from 8bit to quoted-printable by courier 0.39.3 Content-Transfer-Encoding: quoted-printable Subject: [Enum] Re: refresh: IESG review of rfc2916bis Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable On Fri, 2003-10-03 at 09:33, Patrik F=E4ltstr=F6m wrote: > Suggested RFC-Editor notes, which if ok should make it possible to hav= e > 2916bis become an RFC. I've looked these over and see no problems with any of the changes from my end. Do you want to incorporate them and submit the new version? -MM > > Ted Hardie's Discuss comments: > > > > I went back forth as to whether these were serious nits > > or a mild discuss. The tired lady mentioned in the nit > > related to section 2.1 was the deciding factor. In other > > words, I think these should be fixed, but pushback is > > welcome. > > > > > > In the introduction: > > > > "like delegation through NS records and NAPTR records, one can > > look up > > what services are available for a specific domain name" > > > > Would it not make more sense to say, "what services are associated > > with a > > specific E.164 number"? This is not general to all domain names. > > Comment: I think it is ok to make this change. The reason it talks > about domain names in the second part of this very long sentence is > because ENUM really is a two-step process. But, of course the whole > algorithm doesn't work if the input is an E.164 number. > > [1] In the introduction: > > OLD: > > Through transformation of International Public Telecommunication > Numbers in the international format [4], called within this docume= nt > E.164 numbers, into DNS names and the use of existing DNS services > like delegation through NS records and NAPTR records, one can look= up > what services are available for a specific domain name in a > decentralized way with distributed management of the different lev= els > in the lookup process. > > NEW: > > Through transformation of International Public Telecommunication > Numbers in the international format [4], called within this docume= nt > E.164 numbers, into DNS names and the use of existing DNS services > like delegation through NS records and NAPTR records, one can look= up > what services are available for a specific E.164 in a > decentralized way with distributed management of the different lev= els > in the lookup process. > > > For Section 1.2, the language seems less than clear. How about: > > > > This document describes the operation of these mechanisms in th= e > > context > > of numbers allocated according to the ITU-T recommendation E.16= 4. > > The > > same mechanisms might be used for private dialing plans. If th= e > > mechanisms are re-used, the suffix used for the private dialing= > > plan > > MUST NOT be e164.arpa, to avoid conflict with this specificatio= n. > > Parties to the private dialing plan will need to know the the > > suffix > > used by their private dialing plan for correct operation of the= se > > mechanisms. Further, the application unique string used SHOULD= be > > the full number as specified, but without the leading '+' > > Comment: It is important it is explicitly stated that the mechanism > using e164.arpa is called "ENUM". I think this is lost in the suggeste= d > text. I therefore suggest using the suggested text plus an addition at= > the end about use of the term "ENUM". > > In section 1.2: > > OLD: > > This document specifies how "ENUM" works, that is how to handle > numbers allocated according to the ITU-T recommendation E.164. But= , a > similar mechanism can be used also for other numbers, such as priv= ate > dialing plans. To implement that (a) the suffix MUST be selected, > MUST NOT be e164.arpa, MUST be known for all parties using the sam= e > dialing plan (b) the application unique string SHOULD be the full > number as specified but without the leading '+'. > > NEW: > > This document describes the operation of these mechanisms in the > context > of numbers allocated according to the ITU-T recommendation E.164. = > The > same mechanisms might be used for private dialing plans. If the > mechanisms are re-used, the suffix used for the private dialing pl= an > MUST NOT be e164.arpa, to avoid conflict with this specification. > Parties to the private dialing plan will need to know the the suff= ix > used by their private dialing plan for correct operation of these > mechanisms. Further, the application unique string used SHOULD be > the full number as specified, but without the leading '+', and suc= h > private use MUST NOT be called "ENUM". > > > In Section 2.1, the draft says: > > > > > > For example, the E.164 number could start out as "+1-770-923-959= 5". > > To ensure that no syntactic sugar is allowed into the AUS, all > > non-digits except for "+" are removed, yielding "+17709239595". > > > > I'm not sure "syntactic sugar" is clear. Is the AUS a gas tank? :) > > Frankly, I'd suggest deleting the second paragraph, as I don't think= > > it adds > > anything, but if it's kept, I'd suggest updating it to "the E.164 > > number could > > be represented to a user as". I'd also suggest using a known-to-be > > invalid > > number. A tired lady answer this number when I called it, > > and she didn't know anything about this draft. > > The telephone number is changed to the one of the IETF Secretariat. > > Section 2.1: > > OLD: > > For example, the E.164 number could start out as "+1-770-923-9595"= . > To ensure that no syntactic sugar is allowed into the AUS, all > non-digits except for "+" are removed, yielding "+17709239595". > > NEW: > > For example, the E.164 number could start out as "+1-703-620-8990"= . > All non-digits except for "+" are removed, yielding "+17036208990"= . > > > > In section 2.4.2.1, the draft says: > > > > The mapping, if any, have > > to be made explicit in the specification for the Enumservice > > itself. > > A registration of a specific Type also have to specify the Subty= pes > > allowed. > > > > I think the grammar is off there. how about: "the mapping, if any, > > must be made explicit"? > > Section 2.4.2.1: > > OLD: > > Enumservice specifications contain the functional specification (i= .e. > what it can be used for), the valid protocols, and the URI schemes > that may be returned. Note that there is no implicit mapping betwe= en > the textual string "type" or "subtype" in the grammar for the > Enumservice and URI schemes or protocols. The mapping, if any, hav= e > to be made explicit in the specification for the Enumservice itsel= f. > A registration of a specific Type also have to specify the Subtype= s > allowed. > > NEW: > > Enumservice specifications contain the functional specification (i= .e. > what it can be used for), the valid protocols, and the URI schemes > that may be returned. Note that there is no implicit mapping betwe= en > the textual string "type" or "subtype" in the grammar for the > Enumservice and URI schemes or protocols. The mapping, if any, mus= t > be made explicit in the specification for the Enumservice itself. > A registration of a specific Type also have to specify the Subtype= s > allowed. > > > > For the IANA consideration, the work requested by the first two > > paragraphs > > is done. I think that it would be better to change it to note that > > the obsoleted RFC requested these, and to give a pointer to the curr= ent > > IAB/ITU-T agreement. > > Comment: The 2nd paragraph is added relative to RFC 2916, and is what = I > think a proper addition. The first can be changed though. > > Section 5: > > OLD: > > This memo requests that the IANA delegate the E164.ARPA domain > following instructions to be provided by the IAB. Names within th= is > zone are to be delegated to parties according to the ITU-T > Recommendation E.164. The names allocated should be hierarchic in > accordance with ITU-T Recommendation E.164, and the codes should > assigned in accordance with that Recommendation. > > NEW: > > RFC 2916 (which this document replaces) requested IANA to delegate= > the > E164.ARPA domain following instructions to be provided by the IAB.= > The > domain was delegated according to those instructions. Names within > this zone are to be delegated to parties according to the ITU-T > Recommendation E.164. The names allocated should be hierarchic in > accordance with ITU-T Recommendation E.164, and the codes should > assigned in accordance with that Recommendation. > > > > P.S. Here is what Ted said about Section 2.5 but I believe we shoul= d > > leave > > it as is: > > > > I'm concerned that section 2.5 might cause as much confusion as it > > prevents. How about replacing the whole thing with "The ENUM algori= thm > > always returns a single rule. Specific applications may have > > application-specific knowledge or facilities that allow them to > > present multiple results or speed selection, but these should > > never change the operation of the algorithm." > > Good idea. > > Section 2.5: > > OLD: > > There has been some confusion over what exactly an ENUM Resolver > returns and what relation that has to the 'Note 1' section in RFC > 3402. On first reading it seems as though it might be possible for= an > ENUM Resolver to return two Rules. The answer to that depends on > which of two possible definitions you use for an ENUM Resolver: > > The first type of resolver can be called an 'intelligent' resolver= . > It understands its target application very well. In that case the > test done at the beginning of Step 4 in the algorithm is a very > complex one. It can include call backs to the calling thread, GUI > events, etc. Its at this point that a client can be presented with > the idea of "multiple Rules" because its at this step that Order i= s > understood relative to the other ordered records. In this case the > ENUM Resolver still returns one Rule to the calling application bu= t > its smart enough internally that it can apply application specific > knowledge to the Rule selection test. > > The other type of resolver can be called a 'dumb' or 'driven' > resolver. It is generic in the sense that there is no internal > application knowledge. It is run from the 'outside' by a smart > application that changes the selection criteria that are fed to th= e > ENUM Resolver before it starts its resolution task. It returns one > Rule only and the caller has to determine if that Rule is OK or no= t. > If it isn't then it re-runs the resolver with a new set of selecti= on > criteria. Some might consider the combination of this dumb resolve= r > and the application that's driving it as some uber-ENUM-Resolver. = In > that case it can "return more than one Rule" because it can simply > re-run the algorithm several times to collect an appropriate set o= f > Rules. But that uber-ENUM-Resolver is stretching the definition of= an > ENUM Resolver to the point of being unrecognizable. > > The key point is that the Algorithm only returns one Rule. > > NEW: > > There has been some confusion over what exactly an ENUM Resolver > returns and what relation that has to the 'Note 1' section in RFC > 3402. On first reading it seems as though it might be possible for= an > ENUM Resolver to return two Rules. > > The ENUM algorithm always returns a single rule. Specific > applications may have application-specific knowledge or > facilities that allow them to present multiple results or > speed selection, but these should never change the > operation of the algorithm. > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 3 11:02:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11203 for ; Fri, 3 Oct 2003 11:02:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5RRb-0001bL-4D for enum-archive@odin.ietf.org; Fri, 03 Oct 2003 11:02:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93F2BkL006151 for enum-archive@odin.ietf.org; Fri, 3 Oct 2003 11:02:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5RRR-0001ak-BE; Fri, 03 Oct 2003 11:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5RRE-0001Zl-PK for enum@optimus.ietf.org; Fri, 03 Oct 2003 11:01:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11171 for ; Fri, 3 Oct 2003 11:01:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5RRC-0001sb-00 for enum@ietf.org; Fri, 03 Oct 2003 11:01:46 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A5RRB-0001sI-00 for enum@ietf.org; Fri, 03 Oct 2003 11:01:45 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 03 Oct 2003 16:59:39 +0200 Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h93F0uAM016084; Fri, 3 Oct 2003 17:01:10 +0200 (MET DST) Received: from xfe-ams-311.cisco.com ([144.254.228.204]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 17:01:11 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-311.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 17:01:09 +0200 In-Reply-To: <1065189091.14758.104.camel@blackdell.neonym.net> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <1065189091.14758.104.camel@blackdell.neonym.net> Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> Content-Transfer-Encoding: quoted-printable Cc: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Allison Mankin , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Fri, 3 Oct 2003 17:00:56 +0200 To: Michael Mealling X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 03 Oct 2003 15:01:10.0094 (UTC) FILETIME=[2E0E16E0:01C389BF] Content-Transfer-Encoding: quoted-printable Subject: [Enum] Re: refresh: IESG review of rfc2916bis Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable On 2003-okt-03, at 15:51, Michael Mealling wrote: > On Fri, 2003-10-03 at 09:33, Patrik F=E4ltstr=F6m wrote: >> Suggested RFC-Editor notes, which if ok should make it possible to=20 >> have >> 2916bis become an RFC. > > I've looked these over and see no problems with any of the changes = from > my end. Do you want to incorporate them and submit the new version? I wrote them as RFC-Editor notes. I feel it is up to the AD whether=20 they take them as RFC-Editor notes, or if they want a new version of=20 the I-D. paf > > -MM > >>> Ted Hardie's Discuss comments: >>> >>> I went back forth as to whether these were serious nits >>> or a mild discuss. The tired lady mentioned in the nit >>> related to section 2.1 was the deciding factor. In other >>> words, I think these should be fixed, but pushback is >>> welcome. >>> >>> >>> In the introduction: >>> >>> "like delegation through NS records and NAPTR records, one can >>> look up >>> what services are available for a specific domain name" >>> >>> Would it not make more sense to say, "what services are associated >>> with a >>> specific E.164 number"? This is not general to all domain names. >> >> Comment: I think it is ok to make this change. The reason it talks >> about domain names in the second part of this very long sentence is >> because ENUM really is a two-step process. But, of course the whole >> algorithm doesn't work if the input is an E.164 number. >> >> [1] In the introduction: >> >> OLD: >> >> Through transformation of International Public Telecommunication >> Numbers in the international format [4], called within this=20 >> document >> E.164 numbers, into DNS names and the use of existing DNS = services >> like delegation through NS records and NAPTR records, one can=20 >> look up >> what services are available for a specific domain name in a >> decentralized way with distributed management of the different=20 >> levels >> in the lookup process. >> >> NEW: >> >> Through transformation of International Public Telecommunication >> Numbers in the international format [4], called within this=20 >> document >> E.164 numbers, into DNS names and the use of existing DNS = services >> like delegation through NS records and NAPTR records, one can=20 >> look up >> what services are available for a specific E.164 in a >> decentralized way with distributed management of the different=20 >> levels >> in the lookup process. >> >>> For Section 1.2, the language seems less than clear. How about: >>> >>> This document describes the operation of these mechanisms in = the >>> context >>> of numbers allocated according to the ITU-T recommendation=20 >>> E.164. >>> The >>> same mechanisms might be used for private dialing plans. If = the >>> mechanisms are re-used, the suffix used for the private dialing >>> plan >>> MUST NOT be e164.arpa, to avoid conflict with this=20 >>> specification. >>> Parties to the private dialing plan will need to know the the >>> suffix >>> used by their private dialing plan for correct operation of=20 >>> these >>> mechanisms. Further, the application unique string used SHOULD=20= >>> be >>> the full number as specified, but without the leading '+' >> >> Comment: It is important it is explicitly stated that the mechanism >> using e164.arpa is called "ENUM". I think this is lost in the=20 >> suggested >> text. I therefore suggest using the suggested text plus an addition = at >> the end about use of the term "ENUM". >> >> In section 1.2: >> >> OLD: >> >> This document specifies how "ENUM" works, that is how to handle >> numbers allocated according to the ITU-T recommendation E.164.=20 >> But, a >> similar mechanism can be used also for other numbers, such as=20 >> private >> dialing plans. To implement that (a) the suffix MUST be = selected, >> MUST NOT be e164.arpa, MUST be known for all parties using the=20 >> same >> dialing plan (b) the application unique string SHOULD be the full >> number as specified but without the leading '+'. >> >> NEW: >> >> This document describes the operation of these mechanisms in the >> context >> of numbers allocated according to the ITU-T recommendation E.164. >> The >> same mechanisms might be used for private dialing plans. If the >> mechanisms are re-used, the suffix used for the private dialing=20= >> plan >> MUST NOT be e164.arpa, to avoid conflict with this specification. >> Parties to the private dialing plan will need to know the the=20 >> suffix >> used by their private dialing plan for correct operation of these >> mechanisms. Further, the application unique string used SHOULD = be >> the full number as specified, but without the leading '+', and=20 >> such >> private use MUST NOT be called "ENUM". >> >>> In Section 2.1, the draft says: >>> >>> >>> For example, the E.164 number could start out as=20 >>> "+1-770-923-9595". >>> To ensure that no syntactic sugar is allowed into the AUS, all >>> non-digits except for "+" are removed, yielding "+17709239595". >>> >>> I'm not sure "syntactic sugar" is clear. Is the AUS a gas tank? :) >>> Frankly, I'd suggest deleting the second paragraph, as I don't think >>> it adds >>> anything, but if it's kept, I'd suggest updating it to "the E.164 >>> number could >>> be represented to a user as". I'd also suggest using a known-to-be >>> invalid >>> number. A tired lady answer this number when I called it, >>> and she didn't know anything about this draft. >> >> The telephone number is changed to the one of the IETF Secretariat. >> >> Section 2.1: >> >> OLD: >> >> For example, the E.164 number could start out as=20 >> "+1-770-923-9595". >> To ensure that no syntactic sugar is allowed into the AUS, all >> non-digits except for "+" are removed, yielding "+17709239595". >> >> NEW: >> >> For example, the E.164 number could start out as=20 >> "+1-703-620-8990". >> All non-digits except for "+" are removed, yielding=20 >> "+17036208990". >> >> >>> In section 2.4.2.1, the draft says: >>> >>> The mapping, if any, have >>> to be made explicit in the specification for the Enumservice >>> itself. >>> A registration of a specific Type also have to specify the=20 >>> Subtypes >>> allowed. >>> >>> I think the grammar is off there. how about: "the mapping, if any, >>> must be made explicit"? >> >> Section 2.4.2.1: >> >> OLD: >> >> Enumservice specifications contain the functional specification=20= >> (i.e. >> what it can be used for), the valid protocols, and the URI = schemes >> that may be returned. Note that there is no implicit mapping=20 >> between >> the textual string "type" or "subtype" in the grammar for the >> Enumservice and URI schemes or protocols. The mapping, if any,=20 >> have >> to be made explicit in the specification for the Enumservice=20 >> itself. >> A registration of a specific Type also have to specify the=20 >> Subtypes >> allowed. >> >> NEW: >> >> Enumservice specifications contain the functional specification=20= >> (i.e. >> what it can be used for), the valid protocols, and the URI = schemes >> that may be returned. Note that there is no implicit mapping=20 >> between >> the textual string "type" or "subtype" in the grammar for the >> Enumservice and URI schemes or protocols. The mapping, if any,=20 >> must >> be made explicit in the specification for the Enumservice itself. >> A registration of a specific Type also have to specify the=20 >> Subtypes >> allowed. >> >> >>> For the IANA consideration, the work requested by the first two >>> paragraphs >>> is done. I think that it would be better to change it to note that >>> the obsoleted RFC requested these, and to give a pointer to the=20 >>> current >>> IAB/ITU-T agreement. >> >> Comment: The 2nd paragraph is added relative to RFC 2916, and is what=20= >> I >> think a proper addition. The first can be changed though. >> >> Section 5: >> >> OLD: >> >> This memo requests that the IANA delegate the E164.ARPA domain >> following instructions to be provided by the IAB. Names within=20= >> this >> zone are to be delegated to parties according to the ITU-T >> Recommendation E.164. The names allocated should be hierarchic = in >> accordance with ITU-T Recommendation E.164, and the codes should >> assigned in accordance with that Recommendation. >> >> NEW: >> >> RFC 2916 (which this document replaces) requested IANA to = delegate >> the >> E164.ARPA domain following instructions to be provided by the = IAB. >> The >> domain was delegated according to those instructions. Names = within >> this zone are to be delegated to parties according to the ITU-T >> Recommendation E.164. The names allocated should be hierarchic = in >> accordance with ITU-T Recommendation E.164, and the codes should >> assigned in accordance with that Recommendation. >> >> >>> P.S. Here is what Ted said about Section 2.5 but I believe we = should >>> leave >>> it as is: >>> >>> I'm concerned that section 2.5 might cause as much confusion as it >>> prevents. How about replacing the whole thing with "The ENUM=20 >>> algorithm >>> always returns a single rule. Specific applications may have >>> application-specific knowledge or facilities that allow them to >>> present multiple results or speed selection, but these should >>> never change the operation of the algorithm." >> >> Good idea. >> >> Section 2.5: >> >> OLD: >> >> There has been some confusion over what exactly an ENUM Resolver >> returns and what relation that has to the 'Note 1' section in RFC >> 3402. On first reading it seems as though it might be possible=20 >> for an >> ENUM Resolver to return two Rules. The answer to that depends on >> which of two possible definitions you use for an ENUM Resolver: >> >> The first type of resolver can be called an 'intelligent'=20 >> resolver. >> It understands its target application very well. In that case the >> test done at the beginning of Step 4 in the algorithm is a very >> complex one. It can include call backs to the calling thread, GUI >> events, etc. Its at this point that a client can be presented = with >> the idea of "multiple Rules" because its at this step that Order=20= >> is >> understood relative to the other ordered records. In this case = the >> ENUM Resolver still returns one Rule to the calling application=20= >> but >> its smart enough internally that it can apply application = specific >> knowledge to the Rule selection test. >> >> The other type of resolver can be called a 'dumb' or 'driven' >> resolver. It is generic in the sense that there is no internal >> application knowledge. It is run from the 'outside' by a smart >> application that changes the selection criteria that are fed to=20= >> the >> ENUM Resolver before it starts its resolution task. It returns = one >> Rule only and the caller has to determine if that Rule is OK or=20= >> not. >> If it isn't then it re-runs the resolver with a new set of=20 >> selection >> criteria. Some might consider the combination of this dumb=20 >> resolver >> and the application that's driving it as some uber-ENUM-Resolver.=20= >> In >> that case it can "return more than one Rule" because it can = simply >> re-run the algorithm several times to collect an appropriate set=20= >> of >> Rules. But that uber-ENUM-Resolver is stretching the definition=20= >> of an >> ENUM Resolver to the point of being unrecognizable. >> >> The key point is that the Algorithm only returns one Rule. >> >> NEW: >> >> There has been some confusion over what exactly an ENUM Resolver >> returns and what relation that has to the 'Note 1' section in RFC >> 3402. On first reading it seems as though it might be possible=20 >> for an >> ENUM Resolver to return two Rules. >> >> The ENUM algorithm always returns a single rule. Specific >> applications may have application-specific knowledge or >> facilities that allow them to present multiple results or >> speed selection, but these should never change the >> operation of the algorithm. >> > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 3 16:17:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25152 for ; Fri, 3 Oct 2003 16:17:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5WMS-0001F5-BP for enum-archive@odin.ietf.org; Fri, 03 Oct 2003 16:17:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93KHCBF004725 for enum-archive@odin.ietf.org; Fri, 3 Oct 2003 16:17:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5WMG-0001Cp-IX; Fri, 03 Oct 2003 16:17:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5WLi-0001Bx-C6 for enum@optimus.ietf.org; Fri, 03 Oct 2003 16:16:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25006 for ; Fri, 3 Oct 2003 16:16:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5WLg-0005qT-00 for enum@ietf.org; Fri, 03 Oct 2003 16:16:24 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A5WLf-0005pb-00 for enum@ietf.org; Fri, 03 Oct 2003 16:16:23 -0400 Received: from shockey-family.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h93KKff21731; Fri, 3 Oct 2003 13:20:41 -0700 Message-Id: <6.0.0.22.2.20031003161326.02afa958@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 03 Oct 2003 16:14:58 -0400 To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= , Michael Mealling From: Richard Shockey Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Cc: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Allison Mankin , Ted Hardie In-Reply-To: <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <1065189091.14758.104.camel@blackdell.neonym.net> <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable At 11:00 AM 10/3/2003, Patrik F=E4ltstr=F6m wrote: >On 2003-okt-03, at 15:51, Michael Mealling wrote: > >>On Fri, 2003-10-03 at 09:33, Patrik F=E4ltstr=F6m wrote: >>>Suggested RFC-Editor notes, which if ok should make it possible to have >>>2916bis become an RFC. >> >>I've looked these over and see no problems with any of the changes from >>my end. Do you want to incorporate them and submit the new version? > >I wrote them as RFC-Editor notes. I feel it is up to the AD whether they=20 >take them as RFC-Editor notes, or if they want a new version of the I-D. > > paf > Was the language on what type of RFC the enumservice field registrations=20 could be ammended ?..the consensus was all ENUM service fields=20 registrations must be either proposed, draft, or experimental but not=20 Informational. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1= 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 3 17:56:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00870 for ; Fri, 3 Oct 2003 17:56:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5XuC-0007BG-RW for enum-archive@odin.ietf.org; Fri, 03 Oct 2003 17:56:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93Lu8rv027552 for enum-archive@odin.ietf.org; Fri, 3 Oct 2003 17:56:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5Xu5-00079p-UT; Fri, 03 Oct 2003 17:56:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5Xtt-00079Z-U7 for enum@optimus.ietf.org; Fri, 03 Oct 2003 17:55:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00852 for ; Fri, 3 Oct 2003 17:55:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5Xtr-0007ea-00 for enum@ietf.org; Fri, 03 Oct 2003 17:55:47 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A5Xtq-0007e3-00 for enum@ietf.org; Fri, 03 Oct 2003 17:55:46 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 03 Oct 2003 23:53:41 +0200 Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h93LtB9P016901; Fri, 3 Oct 2003 23:55:12 +0200 (MET DST) Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 23:55:15 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 3 Oct 2003 23:55:14 +0200 In-Reply-To: <6.0.0.22.2.20031003161326.02afa958@shockey.us> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <1065189091.14758.104.camel@blackdell.neonym.net> <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> <6.0.0.22.2.20031003161326.02afa958@shockey.us> Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <45073800-F5EC-11D7-B19E-000A959CF516@cisco.com> Content-Transfer-Encoding: 7bit Cc: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Michael Mealling , Allison Mankin , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Fri, 3 Oct 2003 23:55:14 +0200 To: Richard Shockey X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 03 Oct 2003 21:55:14.0766 (UTC) FILETIME=[06A22EE0:01C389F9] Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit On 2003-okt-03, at 22:14, Richard Shockey wrote: > Was the language on what type of RFC the enumservice field > registrations could be ammended ?..the consensus was all ENUM service > fields registrations must be either proposed, draft, or experimental > but not Informational. The diff was on version -06. I don't have it in front of me now, and I need to go to sleep. The clock is almost midnight here in Sweden. I will have a look tomorrow, if noone else has looked before that. paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sat Oct 4 22:21:57 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21797 for ; Sat, 4 Oct 2003 22:21:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5yWe-0004qo-Bd for enum-archive@odin.ietf.org; Sat, 04 Oct 2003 22:21:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h952Latq018596 for enum-archive@odin.ietf.org; Sat, 4 Oct 2003 22:21:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5yW5-0004pa-Lp; Sat, 04 Oct 2003 22:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5yVj-0004pE-R6 for enum@optimus.ietf.org; Sat, 04 Oct 2003 22:20:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21758 for ; Sat, 4 Oct 2003 22:20:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5yVg-0005OH-00 for enum@ietf.org; Sat, 04 Oct 2003 22:20:36 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx with esmtp (Exim 4.12) id 1A5yVg-0005OC-00 for enum@ietf.org; Sat, 04 Oct 2003 22:20:36 -0400 Received: from chiimc01.npac.com ([10.32.90.4]) by willow.neustar.com (8.11.6/8.11.6) with ESMTP id h952JL009401; Sun, 5 Oct 2003 02:19:21 GMT Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19) id ; Sat, 4 Oct 2003 21:20:05 -0500 Message-ID: From: "Peterson, Jon" To: "'Richard Shockey'" , =?iso-8859-1?Q?Patrik_F=E4l?= =?iso-8859-1?Q?tstr=F6m?= , Michael Mealling Cc: "Shockey, Richard" , enum@ietf.org, Allison Mankin , Ted Hardie Subject: RE: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sat, 4 Oct 2003 21:20:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , > > Was the language on what type of RFC the enumservice field registrations > could be ammended ?..the consensus was all ENUM service fields > registrations must be either proposed, draft, or experimental but not > Informational. > I thought it was supposed to be standards-track, BCP or experimental (and yes, not Informational). Jon Peterson NeuStar, Inc. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 06:22:41 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11793 for ; Sun, 5 Oct 2003 06:22:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A661r-0004cK-4L for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 06:22:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95AMJi7017698 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 06:22:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A661Z-0004aq-Hy; Sun, 05 Oct 2003 06:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6610-0004aL-0J for enum@optimus.ietf.org; Sun, 05 Oct 2003 06:21:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11782 for ; Sun, 5 Oct 2003 06:21:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A660v-0000gf-00 for enum@ietf.org; Sun, 05 Oct 2003 06:21:21 -0400 Received: from rsys001a.roke.co.uk ([193.118.192.110]) by ietf-mx with esmtp (Exim 4.12) id 1A660v-0000g6-00 for enum@ietf.org; Sun, 05 Oct 2003 06:21:21 -0400 Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19) id ; Sun, 5 Oct 2003 11:20:23 +0100 Received: from orion.roke.co.uk ([193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TNNBSCFS; Sun, 5 Oct 2003 11:20:19 +0100 From: "Conroy, Lawrence (SMTP)" To: "Peterson, Jon" , "'Richard Shockey'" , =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= , Michael Mealling Cc: enum@ietf.org, Allison Mankin , Ted Hardie Mime-Version: 1.0 X-Sender: lwc@127.0.0.1 Message-Id: In-Reply-To: References: Date: Sun, 5 Oct 2003 11:20:15 +0100 Subject: RE: [Enum] Re: refresh: IESG review of rfc2916bis Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , At 9:20 pm -0500 4/10/03, Peterson, Jon wrote: > > >> Was the language on what type of RFC the enumservice field registrations >> could be ammended ?..the consensus was all ENUM service fields >> registrations must be either proposed, draft, or experimental but not >> Informational. >> > >I thought it was supposed to be standards-track, BCP or experimental (and >yes, not Informational). > Hi folks, (BCP is not standards track :). Many thanks to Jon for the reminder - someone with a memory. IIRC, the discussion went - Earlier drafts said ENUM service field registrations 'must be defined in a standards track RFC'. * "need to include Experimental for trials, and that isn't Standards track" * "just say 'must be defined in an RFC'" * "don't want to include Informational" * "just say 'must be defined in a standards track or experimental RFC'" * "may well want to include BCP" * "say 'must be defined in a standards track or experimental RFC, or in a BCP'" All agreed. This sentence revision fell in the bit bucket during final draft prep, hence the "please put it back in as agreed" a few months back. all the best, Lawrence -- ----------------------------------------------------------------------- Roke Manor Research : This information is provided "as is" and is not : intended to create any contractual or legal : relationship. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 06:28:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11927 for ; Sun, 5 Oct 2003 06:28:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A667N-0004pv-Vu for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 06:28:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95AS1t5018568 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 06:28:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A667N-0004om-1w; Sun, 05 Oct 2003 06:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A666P-0004lh-RL for enum@optimus.ietf.org; Sun, 05 Oct 2003 06:27:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11892 for ; Sun, 5 Oct 2003 06:26:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A666L-0000jA-00 for enum@ietf.org; Sun, 05 Oct 2003 06:26:57 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A666L-0000is-00 for enum@ietf.org; Sun, 05 Oct 2003 06:26:57 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 05 Oct 2003 12:24:50 +0200 Received: from XBE-AMS-302.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h95AQLSl021035; Sun, 5 Oct 2003 12:26:21 +0200 (MET DST) Received: from xfe-ams-301.cisco.com ([144.254.75.88]) by XBE-AMS-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 12:23:12 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-301.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 12:26:24 +0200 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Content-Transfer-Encoding: 7bit Cc: enum@ietf.org, "'Richard Shockey'" , Allison Mankin , Michael Mealling , "Peterson, Jon" , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sun, 5 Oct 2003 12:26:27 +0200 To: "Conroy, Lawrence (SMTP)" X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 05 Oct 2003 10:26:24.0284 (UTC) FILETIME=[20929DC0:01C38B2B] Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Lawrence, others... The quickest way this can be resolved is by having you look at version -06, and propose a OLD/NEW text. Can one of you do that please? paf On 2003-okt-05, at 12:20, Conroy, Lawrence (SMTP) wrote: > At 9:20 pm -0500 4/10/03, Peterson, Jon wrote: >> > >>> Was the language on what type of RFC the enumservice field >>> registrations >>> could be ammended ?..the consensus was all ENUM service fields >>> registrations must be either proposed, draft, or experimental but >>> not >>> Informational. >>> >> >> I thought it was supposed to be standards-track, BCP or experimental >> (and >> yes, not Informational). >> > > Hi folks, > (BCP is not standards track :). > Many thanks to Jon for the reminder - someone with a memory. > > IIRC, the discussion went - > Earlier drafts said ENUM service field registrations 'must be defined > in a standards track RFC'. > * "need to include Experimental for trials, and that isn't Standards > track" > * "just say 'must be defined in an RFC'" > * "don't want to include Informational" > * "just say 'must be defined in a standards track or experimental > RFC'" > * "may well want to include BCP" > * "say 'must be defined in a standards track or experimental RFC, or > in a BCP'" > All agreed. > > This sentence revision fell in the bit bucket during final draft prep, > hence > the "please put it back in as agreed" a few months back. > > all the best, > Lawrence > -- > ----------------------------------------------------------------------- > Roke Manor Research : This information is provided "as is" and is > not > : intended to create any contractual or legal > : relationship. > > -- > Registered Office: Roke Manor Research Ltd, Siemens House, Oldbury, > Bracknell, > Berkshire. RG12 8FZ > > The information contained in this e-mail and any attachments is > confidential to > Roke Manor Research Ltd and must not be passed to any third party > without > permission. This communication is for information only and shall not > create or > change any contractual relationship. > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 06:59:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12573 for ; Sun, 5 Oct 2003 06:59:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A66bP-0005gp-ER for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 06:59:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95Ax3cX021870 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 06:59:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A66bN-0005gO-3f; Sun, 05 Oct 2003 06:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A66b7-0005gC-OB for enum@optimus.ietf.org; Sun, 05 Oct 2003 06:58:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12520 for ; Sun, 5 Oct 2003 06:58:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A66b2-0000w6-00 for enum@ietf.org; Sun, 05 Oct 2003 06:58:40 -0400 Received: from rsys001a.roke.co.uk ([193.118.192.110]) by ietf-mx with esmtp (Exim 4.12) id 1A66b2-0000vg-00 for enum@ietf.org; Sun, 05 Oct 2003 06:58:40 -0400 Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19) id ; Sun, 5 Oct 2003 11:58:08 +0100 Received: from orion.roke.co.uk ([193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TNNBSCGB; Sun, 5 Oct 2003 11:58:06 +0100 From: "Conroy, Lawrence (SMTP)" To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= Cc: enum@ietf.org, "'Richard Shockey'" , Allison Mankin , Michael Mealling , "Peterson, Jon" , Ted Hardie Mime-Version: 1.0 X-Sender: lwc@127.0.0.1 Message-Id: In-Reply-To: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Date: Sun, 5 Oct 2003 11:58:00 +0100 Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable At 12:26 pm +0200 5/10/03, Patrik F=E4ltstr=F6m wrote: >Lawrence, others... > >The quickest way this can be resolved is by having you look at=20 >version -06, and propose a OLD/NEW text. > >Can one of you do that please? > > paf > Hi Patrik, folks, First, the irresistible comment about drafts in XML format - I could give the .txt line numbers but the are no use to the=20 authors Hence, please look through the XML source for a matching section title. Now that's out the way... I've tried to re-structure the sentence concerned (1st sentence in section 3.1.4) so that it's a bit easier to read in its extended form. BTW, one could put either 'in' or 'as' in that sentence. To me, 'as' implies that the document has the sole purpose of registration; 'in' may be more appropriate, particularly for a BCP. However, this may be a nit too far, hence it's left as in the OLD. OLD: 3.1.4 Publication Requirements Proposals for Enumservices registered must be published as RFCs on the Standards Track or as a BCP. IANA will retain copies of all Enumservice registration proposals and "publish" them as part of = the ENUM Enumservice Registration tree itself. NEW: 3.1.4 Publication Requirements Proposals for Enumservices registrations MUST be published as one = of the following documents; RFC on the Standards Track, Experimental RFC, or as a BCP. IANA will retain copies of all Enumservice registration proposals and "publish" them as part of the ENUM Enumservice Registration = tree itself. all the best, Lawrence --=20 ----------------------------------------------------------------------- Roke Manor Research : This information is provided "as is" and is = not : intended to create any contractual or legal : relationship. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 09:23:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15198 for ; Sun, 5 Oct 2003 09:23:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A68qq-0001H2-W8 for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 09:23:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95DN8VU004890 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 09:23:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A68qj-0001GU-5f; Sun, 05 Oct 2003 09:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A68qf-0001GJ-JO for enum@optimus.ietf.org; Sun, 05 Oct 2003 09:22:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15191 for ; Sun, 5 Oct 2003 09:22:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A68qd-0001uy-00 for enum@ietf.org; Sun, 05 Oct 2003 09:22:55 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A68qd-0001ur-00 for enum@ietf.org; Sun, 05 Oct 2003 09:22:55 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 05 Oct 2003 15:20:46 +0200 Received: from XBE-AMS-302.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h95DMHkM005562; Sun, 5 Oct 2003 15:22:19 +0200 (MET DST) Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by XBE-AMS-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 15:19:08 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 15:22:20 +0200 In-Reply-To: References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable Cc: enum@ietf.org, "'Richard Shockey'" , Allison Mankin , Michael Mealling , "Peterson, Jon" , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sun, 5 Oct 2003 15:22:23 +0200 To: "Conroy, Lawrence (SMTP)" X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 05 Oct 2003 13:22:20.0549 (UTC) FILETIME=[B498D350:01C38B43] Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable I think we definitely are where we need a new version of the I-D. Michael, can you take my proposed changes and the text below and create=20= a new I-D? paf On 2003-okt-05, at 12:58, Conroy, Lawrence (SMTP) wrote: > At 12:26 pm +0200 5/10/03, Patrik F=E4ltstr=F6m wrote: >> Lawrence, others... >> >> The quickest way this can be resolved is by having you look at=20 >> version -06, and propose a OLD/NEW text. >> >> Can one of you do that please? >> >> paf >> > > Hi Patrik, folks, > > First, the irresistible comment about drafts in XML format - > I could give the .txt line numbers but the are no use to the=20= > authors > Hence, please look through the XML source for a matching section = title. > Now that's out the way... > > I've tried to re-structure the sentence concerned (1st sentence > in section 3.1.4) so that it's a bit easier to read in its > extended form. > BTW, one could put either 'in' or 'as' in that sentence. To me, > 'as' implies that the document has the sole purpose of registration; > 'in' may be more appropriate, particularly for a BCP. However, this > may be a nit too far, hence it's left as in the OLD. > > OLD: > 3.1.4 Publication Requirements > > Proposals for Enumservices registered must be published as RFCs on > the Standards Track or as a BCP. IANA will retain copies of all > Enumservice registration proposals and "publish" them as part of = the > ENUM Enumservice Registration tree itself. > > NEW: > 3.1.4 Publication Requirements > > Proposals for Enumservices registrations MUST be published as one = of > the following documents; RFC on the Standards Track, Experimental > RFC, or as a BCP. > > IANA will retain copies of all Enumservice registration proposals > and "publish" them as part of the ENUM Enumservice Registration = tree > itself. > > > all the best, > Lawrence > --=20 > = ----------------------------------------------------------------------- > Roke Manor Research : This information is provided "as is" and is=20= > not > : intended to create any contractual or legal > : relationship. > > -- > Registered Office: Roke Manor Research Ltd, Siemens House, Oldbury,=20 > Bracknell, > Berkshire. RG12 8FZ > > The information contained in this e-mail and any attachments is=20 > confidential to > Roke Manor Research Ltd and must not be passed to any third party=20 > without > permission. This communication is for information only and shall not=20= > create or > change any contractual relationship. > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 11:25:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18157 for ; Sun, 5 Oct 2003 11:25:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6AlA-0004fK-I3 for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 11:25:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95FPO0f017833 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 11:25:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Ako-0004cq-Gs; Sun, 05 Oct 2003 11:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Akc-0004cF-Ll for enum@optimus.ietf.org; Sun, 05 Oct 2003 11:24:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18141 for ; Sun, 5 Oct 2003 11:24:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Akb-0002iA-00 for enum@ietf.org; Sun, 05 Oct 2003 11:24:49 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A6Aka-0002i0-00 for enum@ietf.org; Sun, 05 Oct 2003 11:24:49 -0400 Received: from shockey-family.shockey.us (h-68-165-240-34.MCLNVA23.covad.net [68.165.240.34]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h95FTjf16213; Sun, 5 Oct 2003 08:29:45 -0700 Message-Id: <6.0.0.22.2.20031005112023.036886e0@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sun, 05 Oct 2003 11:22:28 -0400 To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= , "Conroy, Lawrence (SMTP)" From: Richard Shockey Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Cc: enum@ietf.org, Allison Mankin , Michael Mealling , "Peterson, Jon" , Ted Hardie In-Reply-To: References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable At 09:22 AM 10/5/2003, Patrik F=E4ltstr=F6m wrote: >I think we definitely are where we need a new version of the I-D. > >Michael, can you take my proposed changes and the text below and create a= =20 >new I-D? are you sure we need to revise the ID and resubmit to the WG ...this is=20 going to open up a whole can of worms but if we need to do so then we can=20 go to last call at the moment of issuance. Is this the consensus opinion of IETF Management as well? because I'm going= =20 to have to send a note to the list explaining this. > paf >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1= 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 11:29:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18206 for ; Sun, 5 Oct 2003 11:29:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Aof-0004po-KI for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 11:29:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95FT1IA018533 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 11:29:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Aoe-0004oo-KS; Sun, 05 Oct 2003 11:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6AoL-0004oY-9R for enum@optimus.ietf.org; Sun, 05 Oct 2003 11:28:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18202 for ; Sun, 5 Oct 2003 11:28:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6AoK-0002jd-00 for enum@ietf.org; Sun, 05 Oct 2003 11:28:40 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A6AoJ-0002jZ-00 for enum@ietf.org; Sun, 05 Oct 2003 11:28:39 -0400 Received: from shockey-family.shockey.us (h-68-165-240-34.MCLNVA23.covad.net [68.165.240.34]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h95FXcf16425; Sun, 5 Oct 2003 08:33:39 -0700 Message-Id: <6.0.0.22.2.20031005112417.03667170@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sun, 05 Oct 2003 11:27:49 -0400 To: "Stastny Richard" , From: Richard Shockey Subject: RE: [Enum] I'm looking for ideas on the Agenda for Minneapolis In-Reply-To: <06CF906FE3998C4E944213062009F162233898@oefeg-s02.oefeg.loc > References: <06CF906FE3998C4E944213062009F162233898@oefeg-s02.oefeg.loc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , At 04:09 AM 10/1/2003, Stastny Richard wrote: >Hi folks, > >being relatively new to IETF and not knowing the inner procedures >of IETF and IAB well enough, a status report of the IDs in the queue >would be >nice, eventually by one of the responsible area directors. > >I would be interested eg in getting answers to questions like: >Why is rfc2916bis not released yet as RFC? >What is the problem, if any? >How can it be solved? >When is the release planned? This is being discussed among the authors , myself as the non author chair and the IESG as we speak. We are dealing with IESG requests for clarification and language changes that may or may not require another ID to be issued. film at 11 > >From my working in other not so advanced bodies I am used to get >milestones for release dates and reasons if a date is shifted, not >the other way round (no dates and no reasons), but as I said above: >I am new here. > >So maybe you could set aside 5 minutes? hopefully this will not be necessary .. and this can be clarified or completed before Minneapolis. >Richard >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 11:43:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18409 for ; Sun, 5 Oct 2003 11:43:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B2E-0005To-HF for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 11:43:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95Fh2Zn021039 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 11:43:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B2C-0005Sz-V3; Sun, 05 Oct 2003 11:43:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B1g-0005QM-Mp for enum@optimus.ietf.org; Sun, 05 Oct 2003 11:42:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18397 for ; Sun, 5 Oct 2003 11:42:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6B1f-0002ol-00 for enum@ietf.org; Sun, 05 Oct 2003 11:42:27 -0400 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx with smtp (Exim 4.12) id 1A6B1e-0002oY-00 for enum@ietf.org; Sun, 05 Oct 2003 11:42:27 -0400 content-class: urn:content-classes:message Subject: AW: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sun, 5 Oct 2003 17:46:48 +0200 Message-ID: <06CF906FE3998C4E944213062009F1622338AB@oefeg-s02.oefeg.loc> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Thread-Topic: [Enum] Re: refresh: IESG review of rfc2916bis Thread-Index: AcOLVabRYEY5xWAjQ+qnoT5SzcitVQAASPew X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 From: "Stastny Richard" To: "Richard Shockey" , =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= , "Conroy, Lawrence (SMTP)" Cc: , "Allison Mankin" , "Michael Mealling" , "Peterson, Jon" , "Ted Hardie" Content-Transfer-Encoding: base64 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 SSBhZ3JlZSB3aXRoIFJpY2ggYW5kIEkgZG8gbm90IHRoaW5rIHdlIG5lZWQgYSBuZXcgSUQuDQpO b2JvZHkgY29tcGxhaW5lZCBhYm91dCB0aGUgdGhyZWUgTkVXIHRleHQgcHJvcG9zYWxzLA0KYW5k IHRoZXJlIGlzIG9ubHkgb25lIG1pbm9yIGlzc3VlIGxlZnQgcmVsYXRlZCB0byBzZWN0aW9uIDMu MS40Lg0KIA0KSGVyZSBJIHN1cHBvcnQgTGF3cmVuY2UncyBwcm9wb3NhbCwgYmVjYXVzZSB0aGF0 IGlzIHdoYXQgd2FzIGFncmVlZA0KYXQgdGhlIG1lZXRpbmcuDQogDQpyZWdhcmRzDQpSaWNoYXJk DQoNCgktLS0tLVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tIA0KCVZvbjogUmljaGFyZCBT aG9ja2V5IFttYWlsdG86cmljaGFyZEBzaG9ja2V5LnVzXSANCglHZXNlbmRldDogU28gMDUuMTAu MjAwMyAxNzoyMiANCglBbjogUGF0cmlrIEbDpGx0c3Ryw7ZtOyBDb25yb3ksIExhd3JlbmNlIChT TVRQKSANCglDYzogZW51bUBpZXRmLm9yZzsgQWxsaXNvbiBNYW5raW47IE1pY2hhZWwgTWVhbGxp bmc7IFBldGVyc29uLCBKb247IFRlZCBIYXJkaWUgDQoJQmV0cmVmZjogUmU6IFtFbnVtXSBSZTog cmVmcmVzaDogSUVTRyByZXZpZXcgb2YgcmZjMjkxNmJpcw0KCQ0KCQ0KDQoJQXQgMDk6MjIgQU0g MTAvNS8yMDAzLCBQYXRyaWsgRsOkbHRzdHLDtm0gd3JvdGU6DQoJDQoJPkkgdGhpbmsgd2UgZGVm aW5pdGVseSBhcmUgd2hlcmUgd2UgbmVlZCBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBJLUQuDQoJPg0K CT5NaWNoYWVsLCBjYW4geW91IHRha2UgbXkgcHJvcG9zZWQgY2hhbmdlcyBhbmQgdGhlIHRleHQg YmVsb3cgYW5kIGNyZWF0ZSBhDQoJPm5ldyBJLUQ/DQoJDQoJYXJlIHlvdSBzdXJlIHdlIG5lZWQg dG8gcmV2aXNlIHRoZSBJRCBhbmQgcmVzdWJtaXQgdG8gdGhlIFdHIC4uLnRoaXMgaXMNCglnb2lu ZyB0byBvcGVuIHVwIGEgd2hvbGUgY2FuIG9mIHdvcm1zIGJ1dCBpZiB3ZSBuZWVkIHRvIGRvIHNv IHRoZW4gd2UgY2FuDQoJZ28gdG8gbGFzdCBjYWxsIGF0IHRoZSBtb21lbnQgb2YgaXNzdWFuY2Uu DQoJDQoJSXMgdGhpcyB0aGUgY29uc2Vuc3VzIG9waW5pb24gb2YgSUVURiBNYW5hZ2VtZW50IGFz IHdlbGw/IGJlY2F1c2UgSSdtIGdvaW5nDQoJdG8gaGF2ZSB0byBzZW5kIGEgbm90ZSB0byB0aGUg bGlzdCBleHBsYWluaW5nIHRoaXMuDQoJDQoJDQoJPiAgICBwYWYNCgkNCgkNCgkgPj4+Pj4+Pj4+ Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4NCglSaWNoYXJkIFNo b2NrZXksIFNlbmlvciBNYW5hZ2VyLCBTdHJhdGVnaWMgVGVjaG5vbG9neSBJbml0aWF0aXZlcw0K CU5ldVN0YXIgSW5jLg0KCTQ2MDAwIENlbnRlciBPYWsgUGxhemEgIC0gICBTdGVybGluZywgVkEg IDIwMTY2DQoJc2lwOnJzaG9ja2V5KGF0KWlwdGVsLm9yZyAgIEVOVU0gKzg3ODEwLTEzMzEzLTMx MzMxDQoJUFNUTiBPZmZpY2UgKzEgNTcxLjQzNC41NjUxIFBTVE4gTW9iaWxlOiArMSA3MDMuNTkz LjI2ODMsICBGYXg6ICsxIDgxNS4zMzMuMTIzNw0KCTxtYWlsdG86cmljaGFyZChhdClzaG9ja2V5 LnVzPiBvciA8bWFpbHRvOnJpY2hhcmQuc2hvY2tleShhdCluZXVzdGFyLmJpej4NCgk8aHR0cDov L3d3dy5uZXVzdGFyLmJpej4gOyA8aHR0cDovL3d3dy5lbnVtLm9yZz4NCgk8PDw8PDw8PDw8PDw8 PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PA0KCQ0KCQ0KCV9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJZW51bSBtYWlsaW5nIGxp c3QNCgllbnVtQGlldGYub3JnDQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGlu Zm8vZW51bQ0KCQ0KDQo= _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 11:49:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18522 for ; Sun, 5 Oct 2003 11:49:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B82-0005dQ-4s for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 11:49:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95Fn2Ql021644 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 11:49:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B81-0005ce-CC; Sun, 05 Oct 2003 11:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6B7C-0005b7-6N for enum@optimus.ietf.org; Sun, 05 Oct 2003 11:48:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18498 for ; Sun, 5 Oct 2003 11:48:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6B7B-0002rU-00 for enum@ietf.org; Sun, 05 Oct 2003 11:48:09 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A6B7A-0002r2-00 for enum@ietf.org; Sun, 05 Oct 2003 11:48:08 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 05 Oct 2003 17:46:00 +0200 Received: from XBE-AMS-302.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h95FlWc1016059; Sun, 5 Oct 2003 17:47:33 +0200 (MET DST) Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by XBE-AMS-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 17:44:23 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 17:47:36 +0200 In-Reply-To: <6.0.0.22.2.20031005112023.036886e0@shockey.us> References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> <6.0.0.22.2.20031005112023.036886e0@shockey.us> Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <3CD5A637-F74B-11D7-B19E-000A959CF516@cisco.com> Content-Transfer-Encoding: quoted-printable Cc: "Conroy, Lawrence (SMTP)" , enum@ietf.org, Michael Mealling , Allison Mankin , "Peterson, Jon" , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sun, 5 Oct 2003 17:47:34 +0200 To: Richard Shockey X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 05 Oct 2003 15:47:36.0221 (UTC) FILETIME=[FF8AD4D0:01C38B57] Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable On 2003-okt-05, at 17:22, Richard Shockey wrote: > At 09:22 AM 10/5/2003, Patrik F=E4ltstr=F6m wrote: > >> I think we definitely are where we need a new version of the I-D. >> >> Michael, can you take my proposed changes and the text below and=20 >> create a new I-D? > > are you sure we need to revise the ID and resubmit to the WG ... No, not resubmit to the wg. Just create a new I-D so the work for the=20 rfc-editor becomes easier. paf > this is going to open up a whole can of worms but if we need to do so=20= > then we can go to last call at the moment of issuance. > > Is this the consensus opinion of IETF Management as well? because I'm=20= > going to have to send a note to the list explaining this. > > >> paf > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Senior Manager, Strategic Technology Initiatives > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1=20 > 815.333.1237 > or=20 > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 12:15:13 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18158 for ; Sun, 5 Oct 2003 11:25:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6AlA-0004fL-IN for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 11:25:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95FPO0c017837 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 11:25:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Ako-0004cy-WE; Sun, 05 Oct 2003 11:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Akd-0004cK-K8 for enum@optimus.ietf.org; Sun, 05 Oct 2003 11:24:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18144 for ; Sun, 5 Oct 2003 11:24:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Akc-0002iL-00 for enum@ietf.org; Sun, 05 Oct 2003 11:24:50 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A6Akc-0002i1-00 for enum@ietf.org; Sun, 05 Oct 2003 11:24:50 -0400 Received: from shockey-family.shockey.us (h-68-165-240-34.MCLNVA23.covad.net [68.165.240.34]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h95FTkf16216; Sun, 5 Oct 2003 08:29:47 -0700 Message-Id: <6.0.0.22.2.20031005112241.03667478@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sun, 05 Oct 2003 11:23:59 -0400 To: "Conroy, Lawrence (SMTP)" , Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= From: Richard Shockey Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Cc: enum@ietf.org, Allison Mankin , Michael Mealling , "Peterson, Jon" , Ted Hardie In-Reply-To: References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , At . >NEW: >3.1.4 Publication Requirements > > Proposals for Enumservices registrations MUST be published as one of > the following documents; RFC on the Standards Track, Experimental > RFC, or as a BCP. > > IANA will retain copies of all Enumservice registration proposals > and "publish" them as part of the ENUM Enumservice Registration tree > itself. > no BCP that is not necessary.. standards track, proposed draft or actual standard and Experimental. BCP's are for other things >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 16:44:37 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24982 for ; Sun, 5 Oct 2003 16:44:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Fji-0005ca-QJ for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 16:44:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95KiEKF021560 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 16:44:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6FjV-0005bG-6l; Sun, 05 Oct 2003 16:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Fiv-0005am-Bm for enum@optimus.ietf.org; Sun, 05 Oct 2003 16:43:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24963 for ; Sun, 5 Oct 2003 16:43:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Fit-00051U-00 for enum@ietf.org; Sun, 05 Oct 2003 16:43:23 -0400 Received: from internal.mail.demon.net ([193.195.224.3]) by ietf-mx with esmtp (Exim 4.12) id 1A6Fis-00050R-00 for enum@ietf.org; Sun, 05 Oct 2003 16:43:22 -0400 Received: from finch-staff-1.server.demon.net (finch-staff-1.server.demon.net [193.195.224.1]) by internal.mail.demon.net with ESMTP id h95KhZm21169; Sun, 5 Oct 2003 20:43:35 GMT Received: from clive by finch-staff-1.server.demon.net with local (Exim 3.36 #1) id 1A6FhY-000JZ3-00; Sun, 05 Oct 2003 21:42:00 +0100 Date: Sun, 5 Oct 2003 21:42:00 +0100 From: "Clive D.W. Feather" To: Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= Cc: Ted Hardie , Allison Mankin , Jon Peterson , rich.shockey@neustar.biz, Michael Mealling , enum@ietf.org Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Message-ID: <20031005204200.GA15222@finch-staff-1.thus.net> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> User-Agent: Mutt/1.5.3i Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Patrik F=E4ltstr=F6m said: > The telephone number is changed to the one of the IETF Secretariat. >=20 > Section 2.1: >=20 > OLD: >=20 > For example, the E.164 number could start out as "+1-770-923-9595". > To ensure that no syntactic sugar is allowed into the AUS, all > non-digits except for "+" are removed, yielding "+17709239595". >=20 > NEW: >=20 > For example, the E.164 number could start out as "+1-703-620-8990". > All non-digits except for "+" are removed, yielding "+17036208990". The UK has official "numbers reserved for drama" which can be used in TV and films with a guarantee that they are syntactically correct but will never be allocated. Would you like one of those instead? --=20 Clive D.W. Feather | Work: | Tel: +44 20 8495 6138 Internet Expert | Home: | *** NOTE CHANGE *** Demon Internet | WWW: http://www.davros.org | Fax: +44 870 051 9937 Thus plc | | Mobile: +44 7973 377646 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sun Oct 5 16:57:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25256 for ; Sun, 5 Oct 2003 16:57:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Fw6-0005qY-Ky for enum-archive@odin.ietf.org; Sun, 05 Oct 2003 16:57:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h95Kv2tc022448 for enum-archive@odin.ietf.org; Sun, 5 Oct 2003 16:57:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Fw5-0005pi-OO; Sun, 05 Oct 2003 16:57:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Fvc-0005pN-Va for enum@optimus.ietf.org; Sun, 05 Oct 2003 16:56:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25244 for ; Sun, 5 Oct 2003 16:56:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Fva-00057L-00 for enum@ietf.org; Sun, 05 Oct 2003 16:56:30 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A6Fva-00057I-00 for enum@ietf.org; Sun, 05 Oct 2003 16:56:30 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 05 Oct 2003 22:54:22 +0200 Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h95KttGM012451; Sun, 5 Oct 2003 22:55:55 +0200 (MET DST) Received: from xfe-ams-311.cisco.com ([144.254.228.204]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 22:55:59 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-311.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Sun, 5 Oct 2003 22:55:58 +0200 In-Reply-To: <20031005204200.GA15222@finch-staff-1.thus.net> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <20031005204200.GA15222@finch-staff-1.thus.net> Mime-Version: 1.0 (Apple Message framework v591) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <51353780-F776-11D7-B519-000A959CF516@cisco.com> Content-Transfer-Encoding: 7bit Cc: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Allison Mankin , Michael Mealling , Ted Hardie From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Sun, 5 Oct 2003 22:55:57 +0200 To: "Clive D.W. Feather" X-Mailer: Apple Mail (2.591) X-OriginalArrivalTime: 05 Oct 2003 20:55:58.0737 (UTC) FILETIME=[13E6B810:01C38B83] Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit On 2003-okt-05, at 22:42, Clive D.W. Feather wrote: > The UK has official "numbers reserved for drama" which can be used in > TV > and films with a guarantee that they are syntactically correct but will > never be allocated. Would you like one of those instead? Yes please! I checked with the Swedish regulator Friday last week if they had such numbers, but they didn't. Michael, the numbers then need to change both in the text and in the examples. paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 6 01:28:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06171 for ; Mon, 6 Oct 2003 01:28:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Nuz-0003s2-Kn for enum-archive@odin.ietf.org; Mon, 06 Oct 2003 01:28:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h965SPUF014828 for enum-archive@odin.ietf.org; Mon, 6 Oct 2003 01:28:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Nua-0003qc-MC; Mon, 06 Oct 2003 01:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Nte-0003ns-2k for enum@optimus.ietf.org; Mon, 06 Oct 2003 01:27:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06126 for ; Mon, 6 Oct 2003 01:26:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Nta-00012d-00 for enum@ietf.org; Mon, 06 Oct 2003 01:26:58 -0400 Received: from internal.mail.demon.net ([193.195.224.3]) by ietf-mx with esmtp (Exim 4.12) id 1A6Nta-00012U-00 for enum@ietf.org; Mon, 06 Oct 2003 01:26:58 -0400 Received: from finch-staff-1.server.demon.net (finch-staff-1.server.demon.net [193.195.224.1]) by internal.mail.demon.net with ESMTP id h965Rkm20208; Mon, 6 Oct 2003 05:27:46 GMT Received: from clive by finch-staff-1.server.demon.net with local (Exim 3.36 #1) id 1A6Nsp-0001G7-00; Mon, 06 Oct 2003 06:26:11 +0100 Date: Mon, 6 Oct 2003 06:26:11 +0100 From: "Clive D.W. Feather" To: Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= Cc: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Allison Mankin , Michael Mealling , Ted Hardie Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Message-ID: <20031006052611.GG99655@finch-staff-1.thus.net> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <20031005204200.GA15222@finch-staff-1.thus.net> <51353780-F776-11D7-B519-000A959CF516@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <51353780-F776-11D7-B519-000A959CF516@cisco.com> User-Agent: Mutt/1.5.3i Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Patrik F=E4ltstr=F6m said: >> The UK has official "numbers reserved for drama" which can be used in=20 > Yes please! Here's some: +44-116-496-0348 (Leicester) +44-1632-960083 (random place) +44-20-7946-0148 (London) +44-7700-900454 (mobile) +44-808-1570-983 (free) --=20 Clive D.W. Feather | Work: | Tel: +44 20 8495 6138 Internet Expert | Home: | *** NOTE CHANGE *** Demon Internet | WWW: http://www.davros.org | Fax: +44 870 051 9937 Thus plc | | Mobile: +44 7973 377646 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 6 10:13:16 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02414 for ; Mon, 6 Oct 2003 10:13:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6W6Y-0007ks-V7 for enum-archive@odin.ietf.org; Mon, 06 Oct 2003 10:12:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96ECsog029761 for enum-archive@odin.ietf.org; Mon, 6 Oct 2003 10:12:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6W5g-0007e2-HO; Mon, 06 Oct 2003 10:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6W5L-0007dO-2J for enum@optimus.ietf.org; Mon, 06 Oct 2003 10:11:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02212 for ; Mon, 6 Oct 2003 10:11:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6W5I-0005og-00 for enum@ietf.org; Mon, 06 Oct 2003 10:11:36 -0400 Received: from [209.10.143.221] (helo=neonym.net) by ietf-mx with esmtp (Exim 4.12) id 1A6W5I-0005od-00 for enum@ietf.org; Mon, 06 Oct 2003 10:11:36 -0400 Received: from [207.120.28.115] (softdnserr [::ffff:207.120.28.115]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Sun, 05 Oct 2003 19:56:47 -0400 Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis From: Michael Mealling To: "Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?=" Cc: "Conroy, Lawrence (SMTP)" , enum@ietf.org, "'Richard Shockey'" , Allison Mankin , "Peterson, Jon" , Ted Hardie In-Reply-To: References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> Organization: Harriman Heavy Industries, Inc. Message-Id: <1065449442.6122.8.camel@blackdell.neonym.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.2.2 Date: 06 Oct 2003 10:10:42 -0400 X-Mime-Autoconverted: from 8bit to quoted-printable by courier 0.39.3 Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable On Sun, 2003-10-05 at 09:22, Patrik F=E4ltstr=F6m wrote: > I think we definitely are where we need a new version of the I-D. > > Michael, can you take my proposed changes and the text below and creat= e > a new I-D? > I've made these changes plus the phone number changes plus the original changes. If you go here: http://neonym.net/enum/ you can find the -07 document plus a diff between 06 and 07. I'll send it in once I get three people to review it.... -MM _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 6 14:00:11 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14919 for ; Mon, 6 Oct 2003 14:00:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Ze9-00023P-LH for enum-archive@odin.ietf.org; Mon, 06 Oct 2003 13:59:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96Hxnos007894 for enum-archive@odin.ietf.org; Mon, 6 Oct 2003 13:59:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ZdN-0001yI-3t; Mon, 06 Oct 2003 13:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Zca-0001xY-K8 for enum@optimus.ietf.org; Mon, 06 Oct 2003 13:58:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14802 for ; Mon, 6 Oct 2003 13:58:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6ZcY-0001gb-00 for enum@ietf.org; Mon, 06 Oct 2003 13:58:10 -0400 Received: from rsys001a.roke.co.uk ([193.118.192.110]) by ietf-mx with esmtp (Exim 4.12) id 1A6ZcX-0001fc-00 for enum@ietf.org; Mon, 06 Oct 2003 13:58:09 -0400 Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19) id ; Mon, 6 Oct 2003 18:57:36 +0100 Received: from orion.roke.co.uk ([193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id TNNBSDB4; Mon, 6 Oct 2003 18:57:26 +0100 From: "Conroy, Lawrence (SMTP)" To: Michael Mealling , =?iso-8859-1?Q?Patrik_F=E4lt?= =?iso-8859-1?Q?str=F6m?= Cc: enum@ietf.org, "'Richard Shockey'" , Allison Mankin , "Peterson, Jon" , Ted Hardie Mime-Version: 1.0 X-Sender: lwc@127.0.0.1 Message-Id: In-Reply-To: <1065449442.6122.8.camel@blackdell.neonym.net> References: <6104053A-F71E-11D7-B19E-000A959CF516@cisco.com> <1065449442.6122.8.camel@blackdell.neonym.net> Date: Mon, 6 Oct 2003 18:57:29 +0100 Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable At 10:10 am -0400 6/10/03, Michael Mealling wrote: >On Sun, 2003-10-05 at 09:22, Patrik F=E4ltstr=F6m wrote: >> I think we definitely are where we need a new version of the I-D. >> >> Michael, can you take my proposed changes and the text below and = create >> a new I-D? >> > >I've made these changes plus the phone number changes plus the = original >changes. If you go here: http://neonym.net/enum/ you can find the -07 >document plus a diff between 06 and 07. I'll send it in once I get = three >people to review it.... > >-MM Hi Michael, all, Herewith my reading of the draft on your site. Please could these be applied before it goes out? ------------------------------------------------------------------- I knew there was a reason I prefer text...in the following, the line numbers are the ones I got using VI on a CURL of the text file. The ones labelled "o " are pure typos. The others labelled "* " should really be changed. I think that the references were mangled (and are still mangled). Thus:: - I believe that [6] rfc3402 (DDDS - Algorithm) should be a normative reference. One of the goals of this update is that ENUM uses the DDDS algorithm, so IMHO it's normative. - I'm not sure if the reference in SS2, sentence 1 is to [6] (i.e. to RFC3402) or [1] (i.e. to RFC3403). This is shown in the following list as ??. Many thanks for the change to Drama Numbers. (No one need hear from Ted in the dead of night again :) I've checked from inside the U.K. (both main wireline Operators) and they all give NU. Could someone check from outside the UK? However:: - The example in SS2.2 states that it takes the previous example, but doesn't. I'm assuming that it was meant to do this. (Also, note that the "input" in S2.2 is an AUS, so there isn't any punctuation, hence the dashes in the first number need to go). -------------------- * SS1.2 (para 1, sentence 3) on line 153 - c/mechanisms/If these mechanisms/ ?? S2 (para 1, sentence 1) on line 231 - c/[1]/[6]/ * S2 (para 1, sentence 2) on line 232 - c/[2]/[1]/ * S2.2 (para 2, sentence 1) on line 269 - c/"+44-7700-900454"/"+441164960348"/ * S2.2 (para 2, sentence 2) on line 271 - c/"+447700900454"/"+441164960348"/ * SS2.4 (para 1, sentence 2) on line 291 - c/[2]/[1]/ o S2.4.2.1 (para 1, sentence 4) on line 410 - c/have/has/ o SS3.1.3 (para 2, sentence 2) on line 524 - c/associates/associated/ o S5 (para 1, sentence 3) on line 736 - c/.Names/. Names/ * S5 (para 1, sentence 4) on line 739 - c/should/should be/ * S6.1 (para 4, sentence 2) on line 821 - c/brut/brute/ -------------------- (Finally nit-on-a-nit-on-a-nit): SS 4 (para 1, sentence 1) on line 678 - c/which uses/that use/ -------------------- Those are all the typos I could find. Apart from that, it's fine, IMHO. Good work. all the best, Lawrence --=20 ----------------------------------------------------------------------- Roke Manor Research : This information is provided "as is" and is = not : intended to create any contractual or legal : relationship. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Fri Oct 10 11:25:55 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03419 for ; Fri, 10 Oct 2003 11:25:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7z93-0002HZ-3i for enum-archive@odin.ietf.org; Fri, 10 Oct 2003 11:25:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AFPWhI008723 for enum-archive@odin.ietf.org; Fri, 10 Oct 2003 11:25:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7z8Y-0002Fa-Ae; Fri, 10 Oct 2003 11:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7z8S-0002FD-Ih for enum@optimus.ietf.org; Fri, 10 Oct 2003 11:24:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03390 for ; Fri, 10 Oct 2003 11:24:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7z8R-00052d-00 for enum@ietf.org; Fri, 10 Oct 2003 11:24:55 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A7z8Q-00052B-00 for enum@ietf.org; Fri, 10 Oct 2003 11:24:54 -0400 Received: from shockey-family.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9AFTxf15817; Fri, 10 Oct 2003 08:29:59 -0700 Message-Id: <6.0.0.22.2.20031010111236.03755aa0@popd.ix.netcom.com> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 10 Oct 2003 11:24:07 -0400 To: enum@ietf.org From: Richard Shockey Cc: paf@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] agenda for Minneapolis Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Given the lack of current agenda items for Minneapolis I'm considering reducing the slot we have to a 1 hour session. What drafts should we anticipate coming forward ? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 13 14:58:58 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20245 for ; Mon, 13 Oct 2003 14:58:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A97tu-0001f4-4N for enum-archive@odin.ietf.org; Mon, 13 Oct 2003 14:58:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DIwcFS006335 for enum-archive@odin.ietf.org; Mon, 13 Oct 2003 14:58:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A97tJ-0001dN-9L; Mon, 13 Oct 2003 14:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A97tC-0001d0-Ka for enum@optimus.ietf.org; Mon, 13 Oct 2003 14:57:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20204 for ; Mon, 13 Oct 2003 14:57:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A97t9-0006mM-00 for enum@ietf.org; Mon, 13 Oct 2003 14:57:51 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A97t8-0006m3-00 for enum@ietf.org; Mon, 13 Oct 2003 14:57:51 -0400 Received: from shockey-family.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9DJ32f06387; Mon, 13 Oct 2003 12:03:02 -0700 Message-Id: <6.0.0.22.2.20031013145218.03166690@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 13 Oct 2003 14:55:04 -0400 To: enum@ietf.org From: Richard Shockey Subject: [Enum] agenda for Minneapolis Part 2 Cc: paf@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , We have reduced the slot for ENUM to at IETF 58 to 1 hour. I am taking a open call for agenda items now I must submit the preliminary agenda by Nov 5. I'm assuming that there has been review of the 07 refresh of 2916bis and there are no more issue here correct? #### from MM I've made these changes plus the phone number changes plus the original changes. If you go here: http://neonym.net/enum/ you can find the -07 document plus a diff between 06 and 07. I'll send it in once I get three people to review it.... -MM ######### >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Tue Oct 14 16:12:58 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29320 for ; Tue, 14 Oct 2003 16:12:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9VX2-0006vJ-D9 for enum-archive@odin.ietf.org; Tue, 14 Oct 2003 16:12:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EKCaWQ026609 for enum-archive@odin.ietf.org; Tue, 14 Oct 2003 16:12:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9VWS-0006tR-CY; Tue, 14 Oct 2003 16:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9VWR-0006t8-9D for enum@optimus.ietf.org; Tue, 14 Oct 2003 16:11:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29211 for ; Tue, 14 Oct 2003 16:11:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9VWP-0007iG-00 for enum@ietf.org; Tue, 14 Oct 2003 16:11:57 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1A9VWO-0007hj-00 for enum@ietf.org; Tue, 14 Oct 2003 16:11:56 -0400 Received: from shockey-family.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9EKH0f08360 for ; Tue, 14 Oct 2003 13:17:00 -0700 Message-Id: <6.0.0.22.2.20031014161050.02f14808@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 14 Oct 2003 16:10:58 -0400 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Fwd: Internet-Draft Cutoff Dates for Minneapolis, MN, USA Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , >From: Internet-Drafts Administrator >To: IETF-Announce: ; >Subject: Internet-Draft Cutoff Dates for Minneapolis, MN, USA >Date: Tue, 14 Oct 2003 10:15:11 -0400 >Sender: owner-ietf-announce@ietf.org > > >NOTE: There are two (2) Internet-Draft Cutoff dates. > >October 20th: Cutoff for Initial Submissions (new documents). > >All initial submissions(-00) must be submitted by Monday, October 20th, >at 09:00 ET. Initial submissions received after this time will NOT be >made available in the Internet-Drafts directory, and will have to be >resubmitted. > >As before, all initial submissions (-00.txt) with a filename beginning >with a draft-ietf MUST be approved by the appropriate WG Chair prior to >processing and announcing. WG Chair approval must be received by >Wednesday, October 15th. > >Please do NOT wait until the last minute to submit. > >Be advised: NO placeholders. Updates to initial submissions received > the week of October 20th will NOT be accepted. > >October 27th: FINAL Internet-Draft Cutoff > >All revised Internet-Draft submissions must be submitted by Monday, >October 27th, 2003 at 09:00 ET. Internet-Drafts received after this >time will NOT be announced NOR made available in the Internet-Drafts >Directories. > >We will begin accepting Internet-Draft submissions starting Monday, >November 10th. > >Thank you for your understanding and cooperation. Please do not hesitate >to contact us if you have any questions or concerns. > >FYI: These and other significant dates can be found at > http://www.ietf.org/meetings/cutoff_dates_58.html >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Tue Oct 14 16:29:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00533 for ; Tue, 14 Oct 2003 16:29:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Vmz-0007ye-C7 for enum-archive@odin.ietf.org; Tue, 14 Oct 2003 16:29:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EKT5ZU030640 for enum-archive@odin.ietf.org; Tue, 14 Oct 2003 16:29:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Vmu-0007y5-PM; Tue, 14 Oct 2003 16:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Vmk-0007x4-MG for enum@optimus.ietf.org; Tue, 14 Oct 2003 16:28:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00313 for ; Tue, 14 Oct 2003 16:28:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9Vmi-0000J3-00 for enum@ietf.org; Tue, 14 Oct 2003 16:28:48 -0400 Received: from ams-iport-1.cisco.com ([144.254.74.5]) by ietf-mx with esmtp (Exim 4.12) id 1A9Vmi-0000Gn-00 for enum@ietf.org; Tue, 14 Oct 2003 16:28:48 -0400 Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 14 Oct 2003 22:26:28 +0200 Received: from xbe-ams-312.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h9EKSBDo029871; Tue, 14 Oct 2003 22:28:11 +0200 (MET DST) Received: from xfe-ams-311.cisco.com ([144.254.228.204]) by xbe-ams-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 14 Oct 2003 22:28:16 +0200 Received: from [127.0.0.1] ([144.254.74.55]) by xfe-ams-311.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 14 Oct 2003 22:28:16 +0200 Mime-Version: 1.0 (Apple Message framework v604) In-Reply-To: <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> References: <300A34EE-F5A6-11D7-9C4D-000A959CF516@cisco.com> <1065189091.14758.104.camel@blackdell.neonym.net> <63EF2B4F-F5B2-11D7-9C4D-000A959CF516@cisco.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] Re: refresh: IESG review of rfc2916bis Date: Tue, 14 Oct 2003 22:28:13 +0200 To: rich.shockey@neustar.biz, enum@ietf.org, Jon Peterson , Michael Mealling , Allison Mankin , Ted Hardie X-Mailer: Apple Mail (2.604) X-OriginalArrivalTime: 14 Oct 2003 20:28:16.0208 (UTC) FILETIME=[B2ACAD00:01C39291] Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Michael, I have checked the draft you created: > Section 2.1: > > OLD: > > For example, the E.164 number could start out as "+1-770-923-9595". > To ensure that no syntactic sugar is allowed into the AUS, all > non-digits except for "+" are removed, yielding "+17709239595". > > NEW: > > For example, the E.164 number could start out as "+1-703-620-8990". > All non-digits except for "+" are removed, yielding "+17036208990". This change is not made. Part from this, it is ok. paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Thu Oct 16 14:06:49 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13992 for ; Thu, 16 Oct 2003 14:06:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACW4-0000ah-S3 for enum-archive@odin.ietf.org; Thu, 16 Oct 2003 14:06:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GI6S2N002219 for enum-archive@odin.ietf.org; Thu, 16 Oct 2003 14:06:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACVc-0000YY-OD; Thu, 16 Oct 2003 14:06:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACUg-0000Un-SO for enum@optimus.ietf.org; Thu, 16 Oct 2003 14:05:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13926 for ; Thu, 16 Oct 2003 14:04:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AACUe-00004d-00 for enum@ietf.org; Thu, 16 Oct 2003 14:05:00 -0400 Received: from zak.ecotroph.net ([216.93.164.123]) by ietf-mx with esmtp (Exim 4.12) id 1AACUe-00004a-00 for enum@ietf.org; Thu, 16 Oct 2003 14:05:00 -0400 Received: from ecotroph.net ([::ffff:216.168.239.87]) (AUTH: LOGIN anewton) by zak.ecotroph.net with esmtp; Thu, 16 Oct 2003 14:04:58 -0400 Message-ID: <3F8EE5C6.8070907@ecotroph.net> Date: Thu, 16 Oct 2003 14:39:02 -0400 From: Andrew Newton User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Shockey CC: enum@ietf.org, paf@cisco.com Subject: Re: [Enum] agenda for Minneapolis Part 2 References: <6.0.0.22.2.20031013145218.03166690@shockey.us> In-Reply-To: <6.0.0.22.2.20031013145218.03166690@shockey.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Richard Shockey wrote: > > We have reduced the slot for ENUM to at IETF 58 to 1 hour. > > I am taking a open call for agenda items now I must submit the > preliminary agenda by Nov 5. Richard, Can you give me a slot for iris-ereg? -andy _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Thu Oct 16 14:12:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14334 for ; Thu, 16 Oct 2003 14:12:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACbT-00017V-1G for enum-archive@odin.ietf.org; Thu, 16 Oct 2003 14:12:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GIC2Oe004257 for enum-archive@odin.ietf.org; Thu, 16 Oct 2003 14:12:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACbQ-00016J-Se; Thu, 16 Oct 2003 14:12:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AACaa-00015C-53 for enum@optimus.ietf.org; Thu, 16 Oct 2003 14:11:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14267 for ; Thu, 16 Oct 2003 14:10:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AACaX-00007d-00 for enum@ietf.org; Thu, 16 Oct 2003 14:11:05 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1AACaW-00006v-00 for enum@ietf.org; Thu, 16 Oct 2003 14:11:05 -0400 Received: from shockey-family.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9GIGJf28383; Thu, 16 Oct 2003 11:16:19 -0700 Message-Id: <6.0.0.22.2.20031016140808.03105340@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 16 Oct 2003 14:10:23 -0400 To: Andrew Newton From: Richard Shockey Subject: Re: [Enum] agenda for Minneapolis Part 2 Cc: enum@ietf.org, paf@cisco.com In-Reply-To: <3F8EE5C6.8070907@ecotroph.net> References: <6.0.0.22.2.20031013145218.03166690@shockey.us> <3F8EE5C6.8070907@ecotroph.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , At 02:39 PM 10/16/2003, Andrew Newton wrote: >Richard Shockey wrote: >>We have reduced the slot for ENUM to at IETF 58 to 1 hour. >>I am taking a open call for agenda items now I must submit the >>preliminary agenda by Nov 5. > >Richard, > >Can you give me a slot for iris-ereg? I'd be delighted ... I want to emphasize to the list that issues of ENUM provisioning and the use of IRIS for WHOIS like date in the ENUM context is IN SCOPE for the WG to consider. With global ENUM trials proceeding I'm hoping to see more presentations like this. >-andy >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sat Oct 18 20:44:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14561 for ; Sat, 18 Oct 2003 20:44:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB1fw-0008Pj-Ko for enum-archive@odin.ietf.org; Sat, 18 Oct 2003 20:44:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9J0i4iq032292 for enum-archive@odin.ietf.org; Sat, 18 Oct 2003 20:44:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB1eu-0007rC-Sa; Sat, 18 Oct 2003 20:43:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AB1eC-0007Yv-OQ for enum@optimus.ietf.org; Sat, 18 Oct 2003 20:42:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14548 for ; Sat, 18 Oct 2003 20:42:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AB1eA-0000Yo-00 for enum@ietf.org; Sat, 18 Oct 2003 20:42:14 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1AB1e9-0000Yf-00 for enum@ietf.org; Sat, 18 Oct 2003 20:42:13 -0400 Received: from shockey-family.shockey.us (ZZ2106096160239202003.gwrev.kddi.ne.jp [202.239.160.99]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9J0lWf32466; Sat, 18 Oct 2003 17:47:33 -0700 Message-Id: <6.0.0.22.2.20031018202938.03b29c38@popd.ix.netcom.com> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sat, 18 Oct 2003 20:39:58 -0400 To: enum@ietf.org From: Richard Shockey Cc: paf@cisco.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] The schedule for Minneapolis and nominations for ENUM WG Secretary Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , The collective of the WG chairs in consultation with the IESG is considering adoption of a new permanant position for all IETF Working Groups that would recognized on the WG page etc. The position is that of WG Secretary..the fundamental function of the WG Secretary is to assist the Chairs in taking the minutes of the meeting in a more comprehensive manner than we have all seen in the past., seeing they are properly posted, document tracking and other duties the Chairs deem useful. The position serves at the pleasure of the chairs of the respective WG. Now we really dont have that much on our plate these days however that could quickly change over time and it my feeling that the IETF needs to formally expand the recognition people make in the WG as well as broaden the base of individuals who may be asked to take additional responsibilities in the IETF in the future. If you are willing to serve in such a capacity..please contact Patrick and myself. 1130-1300 Break 1300-1400 Afternoon Sessions I APP ldapbis LDAP (v3) Revsion WG Open Trading Protocol WG INT send Securing Neighbor Discovery WG OPS dnsop Domain Name System Operations WG OPS ipcdn IP over Cable Data Network WG RTG pim Protocol Independent Multicast WG SEC enroll Credential and Provisioning BOF TSV enum Telephone Number Mapping WG >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 20 18:36:45 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11743 for ; Mon, 20 Oct 2003 18:36:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABidV-0003eB-Td for enum-archive@odin.ietf.org; Mon, 20 Oct 2003 18:36:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KMaPj1014013 for enum-archive@odin.ietf.org; Mon, 20 Oct 2003 18:36:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABid6-0003Rd-Nf; Mon, 20 Oct 2003 18:36:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABics-0003NP-8s for enum@optimus.ietf.org; Mon, 20 Oct 2003 18:35:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11672 for ; Mon, 20 Oct 2003 18:35:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABicn-0002Zc-00 for enum@ietf.org; Mon, 20 Oct 2003 18:35:41 -0400 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1ABich-0002YK-00 for enum@ietf.org; Mon, 20 Oct 2003 18:35:35 -0400 Received: from shockey-family.shockey.us (ZZ2106096160239202003.gwrev.kddi.ne.jp [202.239.160.99]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9KMeff22935 for ; Mon, 20 Oct 2003 15:40:41 -0700 Message-Id: <6.0.0.22.2.20031020183209.038e6778@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 20 Oct 2003 18:32:15 -0400 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Fwd: I-D ACTION:draft-stastny-enum-numbering-voip-00.txt Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , We'll have this document and further discussion of IRIS and other provisioning issues on the agenda in Minneapolis >To: IETF-Announce: ; >From: Internet-Drafts@ietf.org >Reply-to: Internet-Drafts@ietf.org >Subject: I-D ACTION:draft-stastny-enum-numbering-voip-00.txt >Date: Mon, 20 Oct 2003 15:41:58 -0400 >Sender: owner-ietf-announce@ietf.org > > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > > > Title : Numbering for VoIP and other IP Communications > Author(s) : R. Stastny > Filename : draft-stastny-enum-numbering-voip-00.txt > Pages : 43 > Date : 2003-10-20 > >This document gives advice in setting up E.164 compatible numbering >and dialing plans in administrative domains set up for IP >Communications in general and VoIP applications in detail. After >explaining numbering and dialing plans in principle, it discusses >which types of E.164 numbers should be used for IP based terminals, >to achieve proper routing of calls and other communications on the >PSTN/ISDN and also on the Internet, using ENUM technology. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-stastny-enum-numbering-voip-00.txt > >To remove yourself from the IETF Announcement list, send a message to >ietf-announce-request with the word unsubscribe in the body of the message. > >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-stastny-enum-numbering-voip-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-stastny-enum-numbering-voip-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. >Content-Type: text/plain >Content-ID: <2003-10-20144818.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-stastny-enum-numbering-voip-00.txt > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Sat Oct 25 10:55:43 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07479 for ; Sat, 25 Oct 2003 10:55:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADPp6-0005cy-JJ for enum-archive@odin.ietf.org; Sat, 25 Oct 2003 10:55:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PEtOKX021580 for enum-archive@odin.ietf.org; Sat, 25 Oct 2003 10:55:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADPok-0005ac-1s; Sat, 25 Oct 2003 10:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADPof-0005aB-3g for enum@optimus.ietf.org; Sat, 25 Oct 2003 10:54:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07467 for ; Sat, 25 Oct 2003 10:54:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADPoc-0005k9-00 for enum@ietf.org; Sat, 25 Oct 2003 10:54:54 -0400 Received: from rsys001a.roke.co.uk ([193.118.192.110]) by ietf-mx with esmtp (Exim 4.12) id 1ADPoc-0005jg-00 for enum@ietf.org; Sat, 25 Oct 2003 10:54:54 -0400 Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2653.19) id ; Sat, 25 Oct 2003 15:54:22 +0100 Received: from orion.roke.co.uk ([193.118.192.66]) by rsys002a.roke.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VCQ7CAHT; Sat, 25 Oct 2003 15:54:20 +0100 From: "Conroy, Lawrence (SMTP)" To: enum@ietf.org Mime-Version: 1.0 X-Sender: lwc@127.0.0.1 Message-Id: Date: Sat, 25 Oct 2003 15:54:15 +0100 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: [Enum] Has 2916bis fallen on the floor again? Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Hi Folks, AFAICT, Patrik and myself have put in a review of 2916bis onto the list, as requested by Michael. Michael DID say he'd put up the latest version when it had three reviewers, so if that's causing a delay, could someone review this fine document? Looks like silence is not taken as a sign of agreement in this case, but merely sleep. atb, Lawrence -- ----------------------------------------------------------------------- Roke Manor Research : This information is provided "as is" and is not : intended to create any contractual or legal : relationship. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 27 08:14:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11328 for ; Mon, 27 Oct 2003 08:14:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE7CH-0000Sd-Hm for enum-archive@odin.ietf.org; Mon, 27 Oct 2003 08:14:16 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RDED6K001767 for enum-archive@odin.ietf.org; Mon, 27 Oct 2003 08:14:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE7C4-0000OX-UE; Mon, 27 Oct 2003 08:14:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE7BM-0000Jj-04 for enum@optimus.ietf.org; Mon, 27 Oct 2003 08:13:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11298 for ; Mon, 27 Oct 2003 08:13:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE7BK-0004hI-00 for enum@ietf.org; Mon, 27 Oct 2003 08:13:14 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx with smtp (Exim 4.12) id 1AE7BJ-0004h4-00 for enum@ietf.org; Mon, 27 Oct 2003 08:13:14 -0500 Content-class: urn:content-classes:message Subject: AW: [Enum] Re: refresh: IESG review of rfc2916bis Date: Mon, 27 Oct 2003 14:17:49 +0100 Message-ID: <06CF906FE3998C4E944213062009F162233914@oefeg-s02.oefeg.loc> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Thread-Topic: [Enum] Re: refresh: IESG review of rfc2916bis Thread-Index: AcOMNFHMstovJkzSQlueq95QVLPREwQVmdU3 From: "Stastny Richard" To: "Conroy, Lawrence (SMTP)" , "Michael Mealling" , =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= Cc: , "Richard Shockey" , "Allison Mankin" , "Peterson, Jon" , "Ted Hardie" Content-Transfer-Encoding: base64 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 SGkgZm9sa3MsDQp0byBnZXQgZmluYWxseSBhIDNyZCByZXZpZXcgOy0pLCB0byBwaWNrIGl0IHVw IGZyb20gdGhlIGZsb29yLg0KIA0KRmlyc3QgSSBhZ3JlZSBvbiBhbGwgY2hhbmdlcyBwcm9wb3Nl ZCBieSBMYXdyZW5jZSBhbmQgUGF0cmlrLg0KIA0KSSBmb3VuZCBpbiBhZGRpdGlvbiBzb21lIG1v cmUgdHlwb3M6DQogDQpTIDIuNC4yLjEgKHBhcmEgMSwgc2VudGVuY2UgMykNCmRlbGV0ZSB0aGUg c2Vjb25kICdiZScNCiANClMgMy4xLjEgKHBhcmEgMiwgc2VudGVuY2UgMSkNCmMvdHJhbnNmZXJl ZC90cmFuc2ZlcnJlZC8NCiANClMgMy4xLjMgKHBhcmEgMywgc2VudGVuY2UgMikNCmFuIEVudW1z ZXJ2aWNlDQogDQpTIDMuMS4zIChwYXJhIDUsIHNlbnRlbmNlIDEpDQphbiBFbnVtc2VydmljZQ0K IA0KUyAzLjEuMiAocGFyYSA4ID0gcG9pbnQgMywgc2VudGVuY2UgMg0KYW4gRW51bXNlcnZpY2UN CiANClMgNCAocGFyYSAxLCBzZW50ZW5jZSAyKQ0KcmVtb3ZlIHRoZSBzZWNvbmQgJ3RoZScNCiAN ClMgNCAocGFyYSAxLCBzZW50ZW5jZSAzKQ0KYW4gRW51bXNlcnZpY2UNCiANClMgNSAocGFyYSA0 LCBzZW50ZW5jZSAxKQ0KaXMgaXQgaW50ZW50ZWQgdG8gdXNlIHRoZSB0ZXJtICdFTlVNIGVudW1z ZXJ2aWNlJz8gKDJ4KQ0KSSB3b3VsZCBzdWdnZXN0IHRvIGVpdGhlciByZW1vdmUgdGhlIEVOVU0g b3IgdXNlIHRoZQ0KdGVybSBjb25zaXN0ZW50bHkgaW4gdGhlIGRvY3VtZW50IChhbGwgb3ZlciB0 aGUgcGxhY2UpDQogDQpTIDYuNCAocGFyYSAxLCBzZW50ZW5jZSAyKQ0KYWdhaW4gRU5VTSBFbnVt c2VydmljZQ0KIA0KSSBjb25zaWRlciB0aGUgZG9jdW1lbnQgbm93IGEgcmVsZWFzYWJsZQ0KQ29u Z3JhdHMgdG8gdGhlIGF1dGhvcnMNCiANCnJlZ2FyZHMNClJpY2hhcmQNCiANCiANCiANCiANCg0K CS0tLS0tVXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0gDQoJVm9uOiBDb25yb3ksIExhd3Jl bmNlIChTTVRQKSBbbWFpbHRvOmx3Y0Byb2tlLmNvLnVrXSANCglHZXNlbmRldDogTW8gMDYuMTAu MjAwMyAxOTo1NyANCglBbjogTWljaGFlbCBNZWFsbGluZzsgUGF0cmlrIEbDpGx0c3Ryw7ZtIA0K CUNjOiBlbnVtQGlldGYub3JnOyAnUmljaGFyZCBTaG9ja2V5JzsgQWxsaXNvbiBNYW5raW47IFBl dGVyc29uLCBKb247IFRlZCBIYXJkaWUgDQoJQmV0cmVmZjogUmU6IFtFbnVtXSBSZTogcmVmcmVz aDogSUVTRyByZXZpZXcgb2YgcmZjMjkxNmJpcw0KCQ0KCQ0KDQoJQXQgMTA6MTAgYW0gLTA0MDAg Ni8xMC8wMywgTWljaGFlbCBNZWFsbGluZyB3cm90ZToNCgk+T24gU3VuLCAyMDAzLTEwLTA1IGF0 IDA5OjIyLCBQYXRyaWsgRsOkbHRzdHLDtm0gd3JvdGU6DQoJPj4gIEkgdGhpbmsgd2UgZGVmaW5p dGVseSBhcmUgd2hlcmUgd2UgbmVlZCBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBJLUQuDQoJPj4NCgk+ PiAgTWljaGFlbCwgY2FuIHlvdSB0YWtlIG15IHByb3Bvc2VkIGNoYW5nZXMgYW5kIHRoZSB0ZXh0 IGJlbG93IGFuZCBjcmVhdGUNCgk+PiAgYSBuZXcgSS1EPw0KCT4+DQoJPg0KCT5JJ3ZlIG1hZGUg dGhlc2UgY2hhbmdlcyBwbHVzIHRoZSBwaG9uZSBudW1iZXIgY2hhbmdlcyBwbHVzIHRoZSBvcmln aW5hbA0KCT5jaGFuZ2VzLiBJZiB5b3UgZ28gaGVyZTogaHR0cDovL25lb255bS5uZXQvZW51bS8g eW91IGNhbiBmaW5kIHRoZSAtMDcNCgk+ZG9jdW1lbnQgcGx1cyBhIGRpZmYgYmV0d2VlbiAwNiBh bmQgMDcuIEknbGwgc2VuZCBpdCBpbiBvbmNlIEkgZ2V0IHRocmVlDQoJPnBlb3BsZSB0byByZXZp ZXcgaXQuLi4uDQoJPg0KCT4tTU0NCgkNCglIaSBNaWNoYWVsLCBhbGwsDQoJDQoJSGVyZXdpdGgg bXkgcmVhZGluZyBvZiB0aGUgZHJhZnQgb24geW91ciBzaXRlLg0KCQ0KCVBsZWFzZSBjb3VsZCB0 aGVzZSBiZSBhcHBsaWVkIGJlZm9yZSBpdCBnb2VzIG91dD8NCgkNCgktLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoJDQoJ SSBrbmV3IHRoZXJlIHdhcyBhIHJlYXNvbiBJIHByZWZlciB0ZXh0Li4uaW4gdGhlIGZvbGxvd2lu ZywgdGhlIGxpbmUNCgludW1iZXJzIGFyZSB0aGUgb25lcyBJIGdvdCB1c2luZyBWSSBvbiBhIENV Ukwgb2YgdGhlIHRleHQgZmlsZS4NCglUaGUgb25lcyBsYWJlbGxlZCAibyAgIiBhcmUgcHVyZSB0 eXBvcy4gVGhlIG90aGVycyBsYWJlbGxlZCAiKiAgIg0KCXNob3VsZCByZWFsbHkgYmUgY2hhbmdl ZC4NCgkNCgkNCglJIHRoaW5rIHRoYXQgdGhlIHJlZmVyZW5jZXMgd2VyZSBtYW5nbGVkIChhbmQg YXJlIHN0aWxsIG1hbmdsZWQpLg0KCVRodXM6Og0KCS0gIEkgYmVsaWV2ZSB0aGF0IFs2XSByZmMz NDAyIChERERTIC0gQWxnb3JpdGhtKQ0KCSAgICBzaG91bGQgYmUgYSBub3JtYXRpdmUgcmVmZXJl bmNlLiBPbmUgb2YgdGhlIGdvYWxzIG9mIHRoaXMgdXBkYXRlDQoJICAgIGlzIHRoYXQgRU5VTSB1 c2VzIHRoZSBERERTIGFsZ29yaXRobSwgc28gSU1ITyBpdCdzIG5vcm1hdGl2ZS4NCgkNCgktICBJ J20gbm90IHN1cmUgaWYgdGhlIHJlZmVyZW5jZSBpbiBTUzIsIHNlbnRlbmNlIDENCgkgICAgaXMg dG8gWzZdIChpLmUuIHRvIFJGQzM0MDIpIG9yIFsxXSAoaS5lLiB0byBSRkMzNDAzKS4gVGhpcyBp cw0KCSAgICBzaG93biBpbiB0aGUgZm9sbG93aW5nIGxpc3QgYXMgPz8uDQoJDQoJTWFueSB0aGFu a3MgZm9yIHRoZSBjaGFuZ2UgdG8gRHJhbWEgTnVtYmVycy4NCgkoTm8gb25lIG5lZWQgaGVhciBm cm9tIFRlZCBpbiB0aGUgZGVhZCBvZiBuaWdodCBhZ2FpbiA6KQ0KCUkndmUgY2hlY2tlZCBmcm9t IGluc2lkZSB0aGUgVS5LLiAoYm90aCBtYWluIHdpcmVsaW5lIE9wZXJhdG9ycykNCglhbmQgdGhl eSBhbGwgZ2l2ZSBOVS4NCglDb3VsZCBzb21lb25lIGNoZWNrIGZyb20gb3V0c2lkZSB0aGUgVUs/ DQoJDQoJSG93ZXZlcjo6DQoJLSAgVGhlIGV4YW1wbGUgaW4gU1MyLjIgc3RhdGVzIHRoYXQgaXQg dGFrZXMgdGhlIHByZXZpb3VzDQoJICAgIGV4YW1wbGUsIGJ1dCBkb2Vzbid0LiBJJ20gYXNzdW1p bmcgdGhhdCBpdCB3YXMgbWVhbnQgdG8gZG8gdGhpcy4NCgkNCgkoQWxzbywgbm90ZSB0aGF0IHRo ZSAiaW5wdXQiIGluIFMyLjIgaXMgYW4gQVVTLCBzbyB0aGVyZSBpc24ndCBhbnkNCglwdW5jdHVh dGlvbiwgaGVuY2UgdGhlIGRhc2hlcyBpbiB0aGUgZmlyc3QgbnVtYmVyIG5lZWQgdG8gZ28pLg0K CQ0KCS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoJKiAgIFNTMS4yIChwYXJhIDEsIHNlbnRlbmNlIDMp IG9uIGxpbmUgMTUzIC0NCgljL21lY2hhbmlzbXMvSWYgdGhlc2UgbWVjaGFuaXNtcy8NCgkNCgk/ PyAgUzIgKHBhcmEgMSwgc2VudGVuY2UgMSkgb24gbGluZSAyMzEgLQ0KCWMvWzFdL1s2XS8NCgkN CgkqICAgUzIgKHBhcmEgMSwgc2VudGVuY2UgMikgb24gbGluZSAyMzIgLQ0KCWMvWzJdL1sxXS8N CgkNCgkqICAgUzIuMiAocGFyYSAyLCBzZW50ZW5jZSAxKSBvbiBsaW5lIDI2OSAtDQoJYy8iKzQ0 LTc3MDAtOTAwNDU0Ii8iKzQ0MTE2NDk2MDM0OCIvDQoJDQoJKiAgIFMyLjIgKHBhcmEgMiwgc2Vu dGVuY2UgMikgb24gbGluZSAyNzEgLQ0KCWMvIis0NDc3MDA5MDA0NTQiLyIrNDQxMTY0OTYwMzQ4 Ii8NCgkNCgkqICAgU1MyLjQgKHBhcmEgMSwgc2VudGVuY2UgMikgb24gbGluZSAyOTEgLQ0KCWMv WzJdL1sxXS8NCgkNCglvICAgUzIuNC4yLjEgKHBhcmEgMSwgc2VudGVuY2UgNCkgb24gbGluZSA0 MTAgLQ0KCWMvaGF2ZS9oYXMvDQoJDQoJbyAgIFNTMy4xLjMgKHBhcmEgMiwgc2VudGVuY2UgMikg b24gbGluZSA1MjQgLQ0KCWMvYXNzb2NpYXRlcy9hc3NvY2lhdGVkLw0KCQ0KCW8gICBTNSAocGFy YSAxLCBzZW50ZW5jZSAzKSBvbiBsaW5lIDczNiAtDQoJYy8uTmFtZXMvLiBOYW1lcy8NCgkNCgkq ICAgUzUgKHBhcmEgMSwgc2VudGVuY2UgNCkgb24gbGluZSA3MzkgLQ0KCWMvc2hvdWxkL3Nob3Vs ZCBiZS8NCgkNCgkqICAgUzYuMSAocGFyYSA0LCBzZW50ZW5jZSAyKSBvbiBsaW5lIDgyMSAtDQoJ Yy9icnV0L2JydXRlLw0KCQ0KCS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoJKEZpbmFsbHkgbml0LW9u LWEtbml0LW9uLWEtbml0KToNCglTUyA0IChwYXJhIDEsIHNlbnRlbmNlIDEpIG9uIGxpbmUgNjc4 IC0NCgljL3doaWNoIHVzZXMvdGhhdCB1c2UvDQoJLS0tLS0tLS0tLS0tLS0tLS0tLS0NCgkNCglU aG9zZSBhcmUgYWxsIHRoZSB0eXBvcyBJIGNvdWxkIGZpbmQuIEFwYXJ0IGZyb20gdGhhdCwgaXQn cyBmaW5lLCBJTUhPLg0KCUdvb2Qgd29yay4NCgkNCglhbGwgdGhlIGJlc3QsDQoJICAgTGF3cmVu Y2UNCgkNCgktLQ0KCS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoJUm9rZSBNYW5vciBSZXNlYXJjaCAgICA6IFRo aXMgaW5mb3JtYXRpb24gaXMgcHJvdmlkZWQgImFzIGlzIiBhbmQgaXMgbm90DQoJPG1haWx0bzps d2NAcm9rZS5jby51az46IGludGVuZGVkIHRvIGNyZWF0ZSBhbnkgY29udHJhY3R1YWwgb3IgbGVn YWwNCgk8dGVsOis0NDE3OTQ4MzM2NjY+ICAgIDogcmVsYXRpb25zaGlwLg0KCQ0KCV9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJZW51bSBtYWlsaW5nIGxp c3QNCgllbnVtQGlldGYub3JnDQoJaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGlu Zm8vZW51bQ0KCQ0KDQo= _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Mon Oct 27 18:13:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27049 for ; Mon, 27 Oct 2003 18:13:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGY4-0006OL-RN for enum-archive@odin.ietf.org; Mon, 27 Oct 2003 18:13:21 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RNDKkk024516 for enum-archive@odin.ietf.org; Mon, 27 Oct 2003 18:13:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGXk-0006Ls-CP; Mon, 27 Oct 2003 18:13:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGWt-0006HP-RX for enum@optimus.ietf.org; Mon, 27 Oct 2003 18:12:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26868 for ; Mon, 27 Oct 2003 18:11:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEGWq-0001XG-00 for enum@ietf.org; Mon, 27 Oct 2003 18:12:04 -0500 Received: from [209.10.143.221] (helo=neonym.net) by ietf-mx with esmtp (Exim 4.12) id 1AEGWq-0001XD-00 for enum@ietf.org; Mon, 27 Oct 2003 18:12:04 -0500 Received: from h009037.203112.miinet.jp (h009037.203112.miinet.jp [::ffff:203.112.9.37]) (AUTH: PLAIN michael, ) by neonym.net with esmtp; Mon, 27 Oct 2003 09:51:33 -0500 Subject: comments incorporated (was Re: [Enum] Has 2916bis fallen on the floor again?) From: Michael Mealling To: "Conroy, Lawrence (SMTP)" Cc: enum@ietf.org In-Reply-To: References: X-Mailer: Ximian Evolution 1.0.8-3mdk Date: 27 Oct 2003 14:12:01 -0500 Message-Id: <1067281924.1914.15.camel@h009037.203112.miinet.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I apologize for missing the draft deadline. I'm in Tokyo and the time zones plus daylight savings time in the US messed me up. I've incorporated all of the comments and updated the web page with the latest version: http://neonym.net/enum/ There is a diff file there between the last -07 and this -07 so those with comments can easily see the results. I'll be sending this in as soon as the repository opens back up. I don't think this will affect our process at all since this version is simply to help the RFC Editor. -MM On Sat, 2003-10-25 at 10:54, Conroy, Lawrence (SMTP) wrote: > Hi Folks, > AFAICT, Patrik and myself have put in a review of 2916bis onto the > list, as requested by Michael. > Michael DID say he'd put up the latest version when it had three > reviewers, so if that's causing > a delay, could someone review this fine document? > > Looks like silence is not taken as a sign of agreement in this case, > but merely sleep. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Tue Oct 28 10:35:40 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00499 for ; Tue, 28 Oct 2003 10:35:40 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEVsQ-00045i-8c for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 10:35:22 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SFZMOZ015726 for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 10:35:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEVs5-00043m-6k; Tue, 28 Oct 2003 10:35:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEVrl-00042P-Ro for enum@optimus.ietf.org; Tue, 28 Oct 2003 10:34:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00404 for ; Tue, 28 Oct 2003 10:34:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEVrj-0005y1-00 for enum@ietf.org; Tue, 28 Oct 2003 10:34:39 -0500 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1AEVri-0005xF-00 for enum@ietf.org; Tue, 28 Oct 2003 10:34:38 -0500 Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9SFe8f02392 for ; Tue, 28 Oct 2003 07:40:08 -0800 Message-Id: <6.0.0.22.2.20031028102103.03094f28@shockey.us> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 28 Oct 2003 10:21:09 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Fwd: I-D ACTION:draft-newton-iris-ereg-01.txt Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , >To: IETF-Announce: ; >From: Internet-Drafts@ietf.org >Reply-to: Internet-Drafts@ietf.org >Subject: I-D ACTION:draft-newton-iris-ereg-01.txt >Date: Mon, 27 Oct 2003 17:09:28 -0500 >Sender: owner-ietf-announce@ietf.org > > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > > > Title : IRIS - An ENUM Registry (ereg) Type for the > Internet Registry Information Service > Author(s) : A. Newton > Filename : draft-newton-iris-ereg-01.txt > Pages : 33 > Date : 2003-10-24 > >This document describes an IRIS (draft-ietf-crisp-iris-core-02.txt ) >registry schema for ENUM administrative information. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-newton-iris-ereg-01.txt > >To remove yourself from the IETF Announcement list, send a message to >ietf-announce-request with the word unsubscribe in the body of the message. > >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-newton-iris-ereg-01.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv@ietf.org. >In the body type: > "FILE /internet-drafts/draft-newton-iris-ereg-01.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. >Content-Type: text/plain >Content-ID: <2003-10-27171138.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-newton-iris-ereg-01.txt > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Tue Oct 28 11:28:45 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05589 for ; Tue, 28 Oct 2003 11:28:45 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWhk-00016u-Vz for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 11:28:26 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SGSO9W004208 for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 11:28:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWhM-00012y-Mz; Tue, 28 Oct 2003 11:28:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWgg-0000xN-Dd for enum@optimus.ietf.org; Tue, 28 Oct 2003 11:27:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05305 for ; Tue, 28 Oct 2003 11:27:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEWgf-000018-00 for enum@ietf.org; Tue, 28 Oct 2003 11:27:17 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx with smtp (Exim 4.12) id 1AEWga-0007ma-00 for enum@ietf.org; Tue, 28 Oct 2003 11:27:12 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Content-class: urn:content-classes:message Subject: AW: comments incorporated (was Re: [Enum] Has 2916bis fallen on thefloor again?) Date: Tue, 28 Oct 2003 17:31:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Message-ID: <06CF906FE3998C4E944213062009F162233923@oefeg-s02.oefeg.loc> Thread-Topic: comments incorporated (was Re: [Enum] Has 2916bis fallen on thefloor again?) Thread-Index: AcOc4KTrCMdZv2WXT8qUlg0TIDIuTQAj6KcU From: "Stastny Richard" To: "Michael Mealling" , "Conroy, Lawrence (SMTP)" Cc: Content-Transfer-Encoding: base64 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 SGkgTU0sDQogDQpuZWFybHkgcGVyZmVjdCA7LSkNCiANCkp1c3QgdHdvIHNtYWxsIHR5cG9zOg0K IA0KaW4gUyAxLjIsIHBhcmEgMSwgc2VudGVuY2UgNDoNCnRoZSBkb3VibGUgX3RoZV8gaXMgIHN0 aWxsIHRoZXJlDQogDQphbmQgaW4gUzQsIHBhcmEgMSwgc2VudGVuY2UgMzoNCiANCnRoZXJlIGlz IHN0aWxsIF9hIEVudW1zZXJ2aWNlXw0KIA0KYmVzdCByZWdhcmRzDQpSaWNoYXJkDQoNCgktLS0t LVVyc3Byw7xuZ2xpY2hlIE5hY2hyaWNodC0tLS0tIA0KCVZvbjogTWljaGFlbCBNZWFsbGluZyBb bWFpbHRvOm1pY2hhZWxAbmVvbnltLm5ldF0gDQoJR2VzZW5kZXQ6IE1vIDI3LjEwLjIwMDMgMjA6 MTIgDQoJQW46IENvbnJveSwgTGF3cmVuY2UgKFNNVFApIA0KCUNjOiBlbnVtQGlldGYub3JnIA0K CUJldHJlZmY6IGNvbW1lbnRzIGluY29ycG9yYXRlZCAod2FzIFJlOiBbRW51bV0gSGFzIDI5MTZi aXMgZmFsbGVuIG9uIHRoZWZsb29yIGFnYWluPykNCgkNCgkNCg0KCUkgYXBvbG9naXplIGZvciBt aXNzaW5nIHRoZSBkcmFmdCBkZWFkbGluZS4gSSdtIGluIFRva3lvIGFuZCB0aGUgdGltZQ0KCXpv bmVzIHBsdXMgZGF5bGlnaHQgc2F2aW5ncyB0aW1lIGluIHRoZSBVUyBtZXNzZWQgbWUgdXAuIEkn dmUNCglpbmNvcnBvcmF0ZWQgYWxsIG9mIHRoZSBjb21tZW50cyBhbmQgdXBkYXRlZCB0aGUgd2Vi IHBhZ2Ugd2l0aCB0aGUNCglsYXRlc3QgdmVyc2lvbjoNCgkNCglodHRwOi8vbmVvbnltLm5ldC9l bnVtLw0KCQ0KCVRoZXJlIGlzIGEgZGlmZiBmaWxlIHRoZXJlIGJldHdlZW4gdGhlIGxhc3QgLTA3 IGFuZCB0aGlzIC0wNyBzbyB0aG9zZQ0KCXdpdGggY29tbWVudHMgY2FuIGVhc2lseSBzZWUgdGhl IHJlc3VsdHMuIEknbGwgYmUgc2VuZGluZyB0aGlzIGluIGFzDQoJc29vbiBhcyB0aGUgcmVwb3Np dG9yeSBvcGVucyBiYWNrIHVwLiBJIGRvbid0IHRoaW5rIHRoaXMgd2lsbCBhZmZlY3Qgb3VyDQoJ cHJvY2VzcyBhdCBhbGwgc2luY2UgdGhpcyB2ZXJzaW9uIGlzIHNpbXBseSB0byBoZWxwIHRoZSBS RkMgRWRpdG9yLg0KCQ0KCS1NTQ0KCQ0KCU9uIFNhdCwgMjAwMy0xMC0yNSBhdCAxMDo1NCwgQ29u cm95LCBMYXdyZW5jZSAoU01UUCkgd3JvdGU6DQoJPiBIaSBGb2xrcywNCgk+ICAgIEFGQUlDVCwg UGF0cmlrIGFuZCBteXNlbGYgaGF2ZSBwdXQgaW4gYSByZXZpZXcgb2YgMjkxNmJpcyBvbnRvIHRo ZQ0KCT4gbGlzdCwgYXMgcmVxdWVzdGVkIGJ5IE1pY2hhZWwuDQoJPiBNaWNoYWVsIERJRCBzYXkg aGUnZCBwdXQgdXAgdGhlIGxhdGVzdCB2ZXJzaW9uIHdoZW4gaXQgaGFkIHRocmVlDQoJPiByZXZp ZXdlcnMsIHNvIGlmIHRoYXQncyBjYXVzaW5nDQoJPiBhIGRlbGF5LCBjb3VsZCBzb21lb25lIHJl dmlldyB0aGlzIGZpbmUgZG9jdW1lbnQ/DQoJPg0KCT4gTG9va3MgbGlrZSBzaWxlbmNlIGlzIG5v dCB0YWtlbiBhcyBhIHNpZ24gb2YgYWdyZWVtZW50IGluIHRoaXMgY2FzZSwNCgk+IGJ1dCBtZXJl bHkgc2xlZXAuDQoJDQoJDQoJDQoJX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX18NCgllbnVtIG1haWxpbmcgbGlzdA0KCWVudW1AaWV0Zi5vcmcNCglodHRwczov L3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9lbnVtDQoJDQoNCg== _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From exim@www1.ietf.org Tue Oct 28 11:47:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07290 for ; Tue, 28 Oct 2003 11:47:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWzp-00030g-Sr for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 11:47:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SGl5pM011569 for enum-archive@odin.ietf.org; Tue, 28 Oct 2003 11:47:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWzk-000301-OK; Tue, 28 Oct 2003 11:47:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEWyx-0002vr-GJ for enum@optimus.ietf.org; Tue, 28 Oct 2003 11:46:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07189 for ; Tue, 28 Oct 2003 11:45:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEWyw-0000n5-00 for enum@ietf.org; Tue, 28 Oct 2003 11:46:10 -0500 Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1AEWyv-0000mP-00 for enum@ietf.org; Tue, 28 Oct 2003 11:46:09 -0500 Received: from ibm-eyjgx9r6nqt.shockey.us (neustargw.va.neustar.com [209.173.53.233]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id h9SGpdf09465 for ; Tue, 28 Oct 2003 08:51:39 -0800 Message-Id: <6.0.0.22.2.20031027204232.02fb6df8@popd.ix.netcom.com> X-Sender: richard@shockey.us X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Tue, 28 Oct 2003 11:43:01 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Draft Agenda for IETF 58 Minneapolis Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Any other Items? TUESDAY, November 11, 2003 0800-1800 IETF Registration - Ballroom Foyer, 3rd Floor 0800-0900 Continental Breakfast - Ballroom Foyer, 3rd Floor 1130-1300 Break 1300-1400 Afternoon Sessions I APP ldapbis LDAP (v3) Revsion WG INT send Securing Neighbor Discovery WG OPS dnsop Domain Name System Operations WG OPS ipcdn IP over Cable Data Network WG RTG pim Protocol Independent Multicast WG SEC enroll Credential and Provisioning BOF TSV enum Telephone Number Mapping WG IETF 58 Minneapolis Telephone Number Mapping (ENUM) WG Agenda Chair(s): Patrik Faltstrom Richard Shockey Transport Area Advisor: Allison Mankin Mailing Lists: General Discussion:enum@ietf.org To Subscribe: enum-request@ietf.org In Body: subscribe Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/ AGENDA BASHING (5 min) We are still taking nominations for WG Secretary. 1. Applicability Statement of CRISP work to ENUM - 15 Min Title : IRIS - An ENUM Registry (ereg) Type for the Internet Registry Information Service Author(s) : A. Newton Filename : draft-newton-iris-ereg-01.txt Pages : 33 Date : 2003-10-24 This document describes an IRIS (draft-ietf-crisp-iris-core-02.txt ) registry schema for ENUM administrative information. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-newton-iris-ereg-01.txt 2. Potential Informational Document 15 min Title : Numbering for VoIP and other IP Communications > Author(s) : R. Stastny > Filename : draft-stastny-enum-numbering-voip-00.txt > Pages : 43 > Date : 2003-10-20 > >This document gives advice in setting up E.164 compatible numbering >and dialing plans in administrative domains set up for IP >Communications in general and VoIP applications in detail. After >explaining numbering and dialing plans in principle, it discusses >which types of E.164 numbers should be used for IP based terminals, >to achieve proper routing of calls and other communications on the >PSTN/ISDN and also on the Internet, using ENUM technology. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-stastny-enum-numbering-voip-00.txt 3. Trial Updates Korea 5 min +... 4. WG next steps 5. General Discussion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum