From enum-bounces@ietf.org Fri Jun 01 09:15:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu6y7-0005nP-Sc; Fri, 01 Jun 2007 09:15:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hu6y6-0005nD-QZ; Fri, 01 Jun 2007 09:15:02 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hu6y5-0002vq-0F; Fri, 01 Jun 2007 09:15:02 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm64466095ba; Fri, 01 Jun 2007 21:25:46 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm9d465b8379; Tue, 29 May 2007 03:24:37 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Tue, 29 May 2007 03:24:37 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HskGX-0001ew-0X; Mon, 28 May 2007 14:48:25 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HskGT-0001ds-QQ; Mon, 28 May 2007 14:48:21 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HskGS-0003Gs-Hh; Mon, 28 May 2007 14:48:21 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 71BB82AC61; Mon, 28 May 2007 18:47:50 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HskFy-0007n8-7A; Mon, 28 May 2007 14:47:50 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 28 May 2007 14:47:50 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-AIMC-AUTH: (null) X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: iesg-secretary@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 1.9 (+) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: enum mailing list , enum chair , Internet Architecture Board , RFC Editor Subject: [Enum] Protocol Action: 'IANA Registration for Enumservice 'XMPP'' to Proposed Standard X-BeenThere: enum@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has approved the following document: - 'IANA Registration for Enumservice 'XMPP' ' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Jon Peterson and Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-xmpp-02.txt Technical Summary This document requests IANA registration of an Enumservice for XMPP, the Extensible Messaging and Presence Protocol. This Enumservice specifically allows the use of 'xmpp' Uniform Resource Identifiers (URIs) in the context of E.164 Number Mapping (ENUM). Working Group Summary The ENUM working group supports the advancement of this specification. Protocol Quality This document was reviewed for the IESG by Jon Peterson. Richard Shockey was the PROTO shepherd. Security Directorate review was provided by Charles Clancy. Gen-ART review was provided by Miguel Garcia. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Jun 10 05:30:53 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HxJkr-0002q2-W6; Sun, 10 Jun 2007 05:30:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HxJkq-0002kx-8w for enum@ietf.org; Sun, 10 Jun 2007 05:30:36 -0400 Received: from zinal.switch.ch ([2001:620:0:14:203:baff:fe37:d138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxJko-000499-PC for enum@ietf.org; Sun, 10 Jun 2007 05:30:36 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by zinal.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1HxJkl-0004Rs-U0; Sun, 10 Jun 2007 11:30:32 +0200 Date: Sun, 10 Jun 2007 11:28:45 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: -2.8 (--) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: enum@ietf.org, Alfred Hoenes Subject: [Enum] draft-ietf-enum-validation-epp-05 LC comments (fwd) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernie Hoeneisen List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Scott I got some LC comments about enum-validation-epp to my personal email and would like to ask you for an opinion about those issues related to XML and requirements language (quoted below). In particular the 2nd bullet point refers to something, which I did the same way as you did earlier in RFC 4114. c.u. in Chicago! cheers, Bernie ---------- Forwarded message ---------- Date: Mon, 28 May 2007 17:41:00 +0200 (MESZ) From: "Alfred Hoenes" [...] (1) Document structure [...] It remains unclear whether the 'e164valex' namespace is a normative part of the document or presented there strictly as an example. >From Sections 4 and 5, it appears as a pure example, but it is apparently handled with rank equal to 'e164val' in Sections 6 and 7. I strongly recommend - to introduce the 'e164valex' namespace and clarify its intended status early in the text, - to integrate the text above with that in Sections 4.5 and 4.5.* (as far as still deemed necessary), and [...] (2) Specification of requirements in Sections 5.2.* AFAICS, the application of EPP in the ENUM context may make use of other EPP extensions, and it will comprise transactions (EPP commands and responses) that do not comprise the exchange of validation data. In the second paragraph of sections 5.1.2, 5.2.1, 5.2.3, 5.2.4, and 5.2.5, the draft repeatedly specifies, using this pattern: [...]. In addition to the EPP command elements described in the EPP domain mapping [4], | the <_____> command MUST contain an element. The | element MUST contain an element that identifies the extension namespace. The element | contains one or more elements ... Both occurrences of "MUST" are inappropriate, IMHO. a) In the context of ENUM, some EPP transactions will not need making use of any extensions. Therefore, the first "MUST" should be replaced by a "MAY" in (almost?) all instances quoted above. b) In the context of ENUM, some EPP transactions might feasibly make use of EPP extensions other than the Validation Mapping extension. Therefore, the second "MUST" should be closely reconsidered for replacement by a "MAY" in all instances quoted above. Otherwise, if it is really intended to make the use of the new extension MANDATORY in every case, transactions (e.g., a transfer reject) must be made possible by changing the requirements on the content of the top level e164val elements to allow '*zero* or more' subelements, not "*one* or more". [...] _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Jun 11 07:27:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxi3B-0005L3-Lj; Mon, 11 Jun 2007 07:27:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxi3A-0005Fj-1L for enum@ietf.org; Mon, 11 Jun 2007 07:27:08 -0400 Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxi38-00083v-PI for enum@ietf.org; Mon, 11 Jun 2007 07:27:08 -0400 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id l5BBPQfc011920; Mon, 11 Jun 2007 07:25:26 -0400 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 07:27:05 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 11 Jun 2007 07:27:26 -0400 Message-ID: <046F43A8D79C794FA4733814869CDF0701DE4EFC@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-enum-validation-epp-05 LC comments (fwd) Thread-Index: AcerQgEGUE+GdC8vRxKz/TY4EORehgA1/CVw From: "Hollenbeck, Scott" To: "Bernie Hoeneisen" X-OriginalArrivalTime: 11 Jun 2007 11:27:05.0919 (UTC) FILETIME=[70C1C4F0:01C7AC1B] X-Spam-Score: 0.0 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Cc: enum@ietf.org, Alfred Hoenes Subject: [Enum] RE: draft-ietf-enum-validation-epp-05 LC comments (fwd) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > -----Original Message----- > From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch]=20 > Sent: Sunday, June 10, 2007 5:29 AM > To: Hollenbeck, Scott > Cc: enum@ietf.org; Alfred Hoenes > Subject: draft-ietf-enum-validation-epp-05 LC comments (fwd) >=20 > Hi Scott >=20 > I got some LC comments about enum-validation-epp to my=20 > personal email and=20 > would like to ask you for an opinion about those issues=20 > related to XML and=20 > requirements language (quoted below). In particular the 2nd=20 > bullet point=20 > refers to something, which I did the same way as you did=20 > earlier in RFC=20 > 4114. >=20 > c.u. in Chicago! >=20 > cheers, > Bernie >=20 > ---------- Forwarded message ---------- > Date: Mon, 28 May 2007 17:41:00 +0200 (MESZ) > From: "Alfred Hoenes" >=20 > [...] >=20 > (1) Document structure >=20 > [...] >=20 > It remains unclear whether the 'e164valex' namespace is a normative > part of the document or presented there strictly as an example. > >From Sections 4 and 5, it appears as a pure example, but it is > apparently handled with rank equal to 'e164val' in Sections 6 and 7. >=20 > I strongly recommend > - to introduce the 'e164valex' namespace and clarify its intended > status early in the text, > - to integrate the text above with that in Sections 4.5 and 4.5.* > (as far as still deemed necessary), and >=20 > [...] I don't have a strong feeling about this. It does appear in examples without explanation, though, so maybe it makes sense to describe it before it's used. > (2) Specification of requirements in Sections 5.2.* >=20 > AFAICS, the application of EPP in the ENUM context may make use > of other EPP extensions, and it will comprise transactions (EPP > commands and responses) that do not comprise the exchange of > validation data. >=20 > In the second paragraph of sections 5.1.2, 5.2.1, 5.2.3, 5.2.4, > and 5.2.5, the draft repeatedly specifies, using this pattern: >=20 > [...]. =20 > In addition > to the EPP command elements described in the EPP domain=20 > mapping [4], > | the <_____> command MUST contain an element. The > | element MUST contain an element that > identifies the extension namespace. The element > | contains one or more elements ... >=20 > Both occurrences of "MUST" are inappropriate, IMHO. >=20 > a) In the context of ENUM, some EPP transactions will not need > making use of any extensions. >=20 > Therefore, the first "MUST" should be replaced by a "MAY" > in (almost?) all instances quoted above. >=20 > b) In the context of ENUM, some EPP transactions might feasibly > make use of EPP extensions other than the Validation Mapping > extension. >=20 > Therefore, the second "MUST" should be closely reconsidered > for replacement by a "MAY" in all instances quoted above. >=20 > Otherwise, if it is really intended to make the use of the new > extension MANDATORY in every case, transactions (e.g., a transfer > reject) must be made possible by changing the requirements on the > content of the top level e164val elements to allow '*zero* or more' > subelements, not "*one* or more". I disagree with this assessment. The text in this document is describing requirements for *this specific extension* alone, in which case the element and its children must (or perhaps MUST ;-)) be present as described. I don't see anything in the document that says that use of the extension is mandatory in every case. -Scott- _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Jun 12 15:50:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCNc-0007Gg-9r; Tue, 12 Jun 2007 15:50:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCNP-0006oJ-C0; Tue, 12 Jun 2007 15:50:03 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCNP-0004ie-1W; Tue, 12 Jun 2007 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id C638F26EC8; Tue, 12 Jun 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HyCNO-0005li-DS; Tue, 12 Jun 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 12 Jun 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-branch-location-record-03.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : The ENUM Branch Location Record Author(s) : O. Lendl Filename : draft-ietf-enum-branch-location-record-03.txt Pages : 10 Date : 2007-6-12 This documents defines an extension to the E.164 Number Mapping (ENUM) algorithm by adding a mapping step which indicates where the ENUM tree for a specific ENUM application is located. A new DNS record (IEBL, the Infrastructure ENUM Branch Location record) is defined which provides an interim solution for the Infrastructure ENUM tree location. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-branch-location-record-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-branch-location-record-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-branch-location-record-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-6-12131447.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-branch-location-record-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-branch-location-record-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-12131447.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Wed Jun 13 03:36:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyNOu-00072n-I9; Wed, 13 Jun 2007 03:36:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyNOs-0006Zx-G3 for enum@ietf.org; Wed, 13 Jun 2007 03:36:18 -0400 Received: from fardach.bofh.priv.at ([88.198.34.164] helo=mail.bofh.priv.at) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyNOs-0000N3-5E for enum@ietf.org; Wed, 13 Jun 2007 03:36:18 -0400 Received: by mail.bofh.priv.at (Postfix, from userid 1000) id A6E8F4CDED; Wed, 13 Jun 2007 09:36:17 +0200 (CEST) Date: Wed, 13 Jun 2007 09:36:17 +0200 From: Otmar Lendl To: enum@ietf.org Message-ID: <20070613073617.GA2942@nic.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [Enum] Fwd: I-D ACTION:draft-ietf-enum-branch-location-record-03.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org ----- Forwarded message from Internet-Drafts@ietf.org ----- A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : The ENUM Branch Location Record Author(s) : O. Lendl Filename : draft-ietf-enum-branch-location-record-03.txt Pages : 10 Date : 2007-6-12 This documents defines an extension to the E.164 Number Mapping (ENUM) algorithm by adding a mapping step which indicates where the ENUM tree for a specific ENUM application is located. A new DNS record (IEBL, the Infrastructure ENUM Branch Location record) is defined which provides an interim solution for the Infrastructure ENUM tree location. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-branch-location-record-03.txt ----- End forwarded message ----- This is an update based on extensive discussion with experts from the dnsext WG concerning the branch location record setup. The main changes are: * Record directly at the country code, not on a special label * RRTYPE allocation is I-ENUM specific * No tree walking whatsoever * no fallback to user-enum /ol -- / Otmar Lendl , T: +43 1 5056416 - 33, F: - 933 \ | nic.at Internet Verwaltungs- und Betriebsgesellschaft m.b.H | \ http://www.nic.at/ LG Salzburg, FN 172568b, Sitz: Salzburg / _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Jun 14 18:51:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyy9X-0007Mx-JO; Thu, 14 Jun 2007 18:50:55 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyy9C-0006fa-2G; Thu, 14 Jun 2007 18:50:34 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hyy9A-0004Hs-LK; Thu, 14 Jun 2007 18:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 8B9882AC7E; Thu, 14 Jun 2007 22:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hyy8g-0005Hc-AH; Thu, 14 Jun 2007 18:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 14 Jun 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-combined-05.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : Combined User and Infrastructure ENUM in the e164.arpa tree Author(s) : M. Haberler, R. Stastny Filename : draft-ietf-enum-combined-05.txt Pages : 11 Date : 2007-6-14 This memo defines an interim solution for Infrastructure ENUM to allow a combined User and Infrastructure ENUM implementation in e164.arpa as a national choice until the long-term solution is approved. This interim solution will be deprecated after approval of the long-term solution. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-combined-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-combined-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-combined-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-6-14150624.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-combined-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-combined-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-6-14150624.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Fri Jun 15 19:56:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzLdq-0004qr-QS; Fri, 15 Jun 2007 19:55:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzLdp-0004nx-GE for enum@ietf.org; Fri, 15 Jun 2007 19:55:45 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzLRT-0003B8-BO for enum@ietf.org; Fri, 15 Jun 2007 19:43:00 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5FNgcKq027515 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 15 Jun 2007 16:42:45 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Fri, 15 Jun 2007 19:42:35 -0400 Message-ID: <044c01c7afa6$ddd53d40$997fb7c0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcevptmyF+wfeuPcTn6eHCINnfnhyQ== Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [Enum] A reminder that if you have agenda items for Chicago .. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The chairs want to know about any new business or old business updates as soon as possible.. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 22 09:25:16 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1j8T-0003VU-JD; Fri, 22 Jun 2007 09:25:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1j8S-0003VP-Mb for enum@ietf.org; Fri, 22 Jun 2007 09:25:12 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1j8Q-0007Bt-Tm for enum@ietf.org; Fri, 22 Jun 2007 09:25:12 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5MDOr50005708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 22 Jun 2007 06:24:55 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Fri, 22 Jun 2007 09:24:27 -0400 Message-ID: <042401c7b4d0$a9d5d930$fd818b90$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace0ge/IWJnM1exXRvGD9o+kCFWBiQATqy2Q Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Subject: [Enum] FW: Internet-Drafts Submission Cutoff Dates for the 69th IETF Meeting in Chicago, IL, USA X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Reminder -----Original Message----- From: ietf-secretariat@ietf.org [mailto:ietf-secretariat@ietf.org]=20 Sent: Friday, June 22, 2007 12:00 AM To: ietf-announce@ietf.org Subject: Internet-Drafts Submission Cutoff Dates for the 69th IETF = Meeting in Chicago, IL, USA There are two (2) Internet-Draft cutoff dates for the 69th=20 IETF Meeting in Chicago, IL, USA: July 2nd: Cutoff Date for Initial (i.e., version -00)=20 Internet-Draft Submissions=20 All initial Internet-Drafts (version -00) must be submitted by Monday,=20 July 2nd at 9:00 AM ET. As always, all initial submissions with a=20 filename beginning with "draft-ietf" must be approved by the=20 appropriate WG Chair before they can be processed or announced. The=20 Secretariat would appreciate receiving WG Chair approval by Monday,=20 June 25th at 9:00 AM ET. July 9th: Cutoff Date for Revised (i.e., version -01 and higher)=20 Internet-Draft Submissions=20 All revised Internet-Drafts (version -01 and higher) must be submitted=20 by Monday, July 9th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective=20 cutoff dates will not be made available in the Internet-Drafts=20 directory or announced until on or after Monday, July 23rd at 9:00=20 AM ET, when Internet-Draft posting resumes. Please do not wait until=20 the last minute to submit. Thank you for your understanding and cooperation. If you have any=20 questions or concerns, then please send a message to=20 internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 69th IETF Meeting can be found at = http://www.ietf.org/meetings/cutoff_dates_69.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Jun 26 18:01:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3J68-0007ep-T7; Tue, 26 Jun 2007 18:01:20 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3J68-0007ej-0k for enum@ietf.org; Tue, 26 Jun 2007 18:01:20 -0400 Received: from rwcrmhc13.comcast.net ([204.127.192.83]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3J67-0000Fe-Nb for enum@ietf.org; Tue, 26 Jun 2007 18:01:19 -0400 Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (rwcrmhc13) with ESMTP id <20070626220038m1300516dee>; Tue, 26 Jun 2007 22:00:38 +0000 Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l5QM0b8t006421 for ; Tue, 26 Jun 2007 18:00:37 -0400 Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l5QM0bFg006417; Tue, 26 Jun 2007 18:00:37 -0400 Date: Tue, 26 Jun 2007 18:00:37 -0400 Message-Id: <200706262200.l5QM0bFg006417@dragon.ariadne.com> To: enum@ietf.org From: Dale.Worley@comcast.net X-Spam-Score: 0.2 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Enum] Routing through both ENUM and PSTN X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I'm taking another look at the problem of routing a call via ENUM and falling back to a PSTN gateway. As far as I can tell, the problem of knowing when to retry a failed ENUM call through the PSTN hasn't been solved, and it's going to be important for customers beyond the early-adopters. It looks like the problem can be solved with more careful definition of when to use various response codes. I've written up my current thinking as an Internet Draft (http://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-sip-redundancy-response-01.txt until it gets into the official directories). If anyone has further information on this, I'd be glad to hear it. Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Jun 28 11:39:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3w5Y-0006wV-FA; Thu, 28 Jun 2007 11:39:20 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3w5X-0006wO-QS for enum@ietf.org; Thu, 28 Jun 2007 11:39:19 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3w5X-0000IR-DF for enum@ietf.org; Thu, 28 Jun 2007 11:39:19 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5SFcbut006993 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 28 Jun 2007 08:38:38 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Thu, 28 Jun 2007 11:37:39 -0400 Message-ID: <00bd01c7b99a$44c26080$ce472180$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace5mkHVlAJy0WOpTP6hFM3wSaTzcQ== Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Subject: [Enum] ENUM Agenda so far. X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org PRELIMINARY IETF 69 Chicago Telephone Number Mapping (ENUM) WG Agenda Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alexander Mayrhofer RAI Director(s): Jon Peterson jon.peterson@neustar.biz Cullen Jennings fluffy@cisco.com RAI Area Advisor: Jon Peterson jon.peterson@neustar.biz MONDAY 1500-1520 Afternoon Beverage and Snack Break I - Fourth Floor Exhibition Hall 1520-1720 Afternoon Session II Monroe INT intarea Internet Area Open Meeting Salon 2 IRTF eme End Middle End Research Group Crystal OPS nee Netconf Extensions and Evolution BOF Grand Ballroom RAI enum Telephone Number Mapping WG Adams RAI avt Audio/Video Transport WG State Ballroom RTG pce Path Computation Element WG Salon 3 SEC dkim Review of Agenda 1. Status of Drafts and in Drafts the Queue Overview - Alexander Mayhofer WG Secretary 2. Review status RFC 3761 update. 3. Review Status of existing Drafts Title : Guide and Template for IANA Registrations of Enumservices Author(s) : J. Livingood, et al. Filename : draft-ietf-enum-enumservices-guide-03.txt Pages : 19 Date : 2007-3-7 This document provides a guide to and template for the creation of new IANA registration of ENUM (E.164 Number Mapping) services. i It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.tx t Title : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-00.txt Pages : 17 Date : 2007-4-30 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. 4. So long and thanks for all the fish?? Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 29 10:02:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4H31-0000nD-GC; Fri, 29 Jun 2007 10:02:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4H2x-0000hF-Bp for enum@ietf.org; Fri, 29 Jun 2007 10:02:03 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Gzy-0000Ur-ON for enum@ietf.org; Fri, 29 Jun 2007 09:59:48 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5TDwgSi006061 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 29 Jun 2007 06:58:44 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Fri, 29 Jun 2007 09:57:42 -0400 Message-ID: <029c01c7ba55$777a2ab0$666e8010$@us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_029D_01C7BA33.F0688AB0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace5zeVPCboRjSyyRqOFrtJuvj6S/QAh4u7A Content-Language: en-us x-cr-hashedpuzzle: AuMT BP/g BsLL Bvwo DZP+ EdzG FPME FUgk HEFp IwXZ JZJ4 JnmI KJ5f Kuaz LOE5 LW6i; 1; ZQBuAHUAbQBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {D13E3EED-4BC7-430D-A66E-5C42628CFC9D}; cgBpAGMAaABhAHIAZABAAHMAaABvAGMAawBlAHkALgB1AHMA; Fri, 29 Jun 2007 13:57:38 GMT; RgBXADoAIABJAC0ARAAgAEEAQwBUAEkATwBOADoAZAByAGEAZgB0AC0AYwBoAGUAbgBiAG8ALQBlAG4AdQBtAC0AbQBnAGMAcAAtADAAMAAuAHQAeAB0AA== x-cr-puzzleid: {D13E3EED-4BC7-430D-A66E-5C42628CFC9D} X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [Enum] FW: I-D ACTION:draft-chenbo-enum-mgcp-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multipart message in MIME format. ------=_NextPart_000_029D_01C7BA33.F0688AB0 Content-Type: Message/External-body; name="ATT00426.dat" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00426.dat" Content-Type: text/plain Content-ID: <2007-6-28131134.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-chenbo-enum-mgcp-00.txt ------=_NextPart_000_029D_01C7BA33.F0688AB0 Content-Type: Message/External-body; name="draft-chenbo-enum-mgcp-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-chenbo-enum-mgcp-00.txt" Content-Type: text/plain Content-ID: <2007-6-28131134.I-D@ietf.org> ------=_NextPart_000_029D_01C7BA33.F0688AB0 Content-Type: text/plain; name="ATT00429.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00429.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------=_NextPart_000_029D_01C7BA33.F0688AB0 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_029D_01C7BA33.F0688AB0-- From enum-bounces@ietf.org Fri Jun 29 10:05:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4H68-0003kH-UO; Fri, 29 Jun 2007 10:05:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4H68-0003jz-0U for enum@ietf.org; Fri, 29 Jun 2007 10:05:20 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4H5J-0002Id-8i for enum@ietf.org; Fri, 29 Jun 2007 10:05:19 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5TE4B6D007491 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 29 Jun 2007 07:04:13 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Fri, 29 Jun 2007 10:03:11 -0400 Message-ID: <02a401c7ba56$3ba5bda0$b2f138e0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace5zeVPCboRjSyyRqOFrtJuvj6S/QAiEZZA Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Subject: [Enum] FW: I-D ACTION:draft-chenbo-enum-mgcp-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Thursday, June 28, 2007 3:50 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-chenbo-enum-mgcp-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Telephone Number Mapping (ENUM) Service Registration for MGCP Author(s) : C. Bo, et al. Filename : draft-chenbo-enum-mgcp-00.txt Pages : 13 Date : 2007-6-28 MGCP decomposes a multimedia gateway into two parts, a call agent and a media gateway,thus brings greater extensibility and makes it easy to construct a large-scale VoIP network. This document registers the MGCP Enumservice according to the guidelines given in RFC 3761 [3].This kind of Enumservice is mainly applied in Carrier Networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chenbo-enum-mgcp-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chenbo-enum-mgcp-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-chenbo-enum-mgcp-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 29 10:42:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Hfr-0005Qs-0B; Fri, 29 Jun 2007 10:42:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Hfp-0005QT-PW for enum@ietf.org; Fri, 29 Jun 2007 10:42:13 -0400 Received: from zinal.switch.ch ([2001:620:0:14:203:baff:fe37:d138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4HfP-0005gq-S3 for enum@ietf.org; Fri, 29 Jun 2007 10:42:12 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by zinal.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1I4HfP-0004VJ-6b for enum@ietf.org; Fri, 29 Jun 2007 16:41:47 +0200 Date: Fri, 29 Jun 2007 16:39:15 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: enum@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: -2.8 (--) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Subject: [Enum] Future ENUMservice registration process; your feedback is appeciated! X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernie Hoeneisen List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi members of the ENUM Working Group! On request of our AD (Jon) in Prague we've been looking into the options of performing ENUMservice registrations after the ENUM working group has been shut down or changed into a dormant state. Text below is a *very rough* sketch of the issues and ideas around this, and we'd definitely appreciate feedback on this. The sketch is split in two parts - a potential process flow for Enumservice registrations, and questions which need to be answered before a process is agreed. It probably makes more sense to answer the questions first. If anybody has more questions, or entirely different ideas, *please* step forward and post them. Rough idea for a future ENUMservice registration process -------------------------------------------------------- The process should perform the function of Enumservice registration, under the aspect that no responsible WG exists ("standalone Registration"?) without curtailing the requirements from RFC3761 regarding the registration process. A rough outline could look like: 1) Write a new Internet-Draft, according to the principles set out in RFC3761 and draft-ietf-enum-enumservices-guide. 2) announce the draft on the enum@ietf.org list (which will survive the working group) [option - make an "enumservices-review@ietf.org" mailing list] 3) ask for feedback/review on the list 4) submit the draft as an individual submission to the RFC editor || IESG || IANA. 5) At least one expert from a pool of Enumservices experts to review the document/service. 6) If the experts agree that this is a useful service (or, can be developed into one), the document proceeds directly to IESG evaluation (or directly to RFC Editor?) Open Questions: --------------- 1) Which process applies ("normal" Submission or independent submission)? To whom the I-D is submitted ( IESG || IANA || RFC-Editor )? Who is in charge of the process? Who is the contact to the author(s)? 2) Independent submission or RAI area WG submission (or similar) or sleeping WG? Are there similar cases of the same problem (e.g. 2929bis)? (According to RFC3761 an Enumservice registrations needs to be Standards Track) 3) Do we want to have an expert review in the process? If yes, at which state in the process the Expert review is performed? What is the exact task of the expert (just syntax, completeness, or also appropriateness and similar)? Is expert review cunsultance or deciding? Who decides at the end? IESG? IANA? Is the Expert review needed in every case? 4) As an alternative to experts, a directorate could perform reviews by request of the IESG. There are potentially two options for that: a) create a dedicated ENUM directorate b) approach the DNS directorate whether they could/would do the ENUMservices reviews Actual question: Is the concept of a directorate viable for reviewing Enumservice registrations? Links: - http://www.rfc-editor.org/indsubs.html - ftp://ftp.rfc-editor.org/internet-drafts/draft-iab-rfc-independent-00.txt - ftp://ftp.rfc-editor.org/in-notes/rfc-editor/rfc-editor-process.gif - https://datatracker.ietf.org/images/state_diagram.gif - http://www.ietf.org/rfc/rfc3761.txt - http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.txt Looking forward to your feedback and answers! Alex & Bernie PS: Thanks to Andy Newton for reviewing and contributing to our ideas! _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 29 11:05:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4I2c-0008Pm-2x; Fri, 29 Jun 2007 11:05:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4I2b-0008Pg-6E for enum@ietf.org; Fri, 29 Jun 2007 11:05:45 -0400 Received: from zinal.switch.ch ([2001:620:0:14:203:baff:fe37:d128]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4I2A-0002GB-A3 for enum@ietf.org; Fri, 29 Jun 2007 11:05:45 -0400 Received: from [130.59.6.129] (helo=machb.switch.ch) by zinal.switch.ch with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1I4I28-0005We-Tm for enum@ietf.org; Fri, 29 Jun 2007 17:05:16 +0200 Date: Fri, 29 Jun 2007 17:02:46 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: 'IETF ENUM WG' In-Reply-To: <02a401c7ba56$3ba5bda0$b2f138e0$@us> Message-ID: References: <02a401c7ba56$3ba5bda0$b2f138e0$@us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SWITCH-SCANNER: bypassed X-Spam-Score: -2.8 (--) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Subject: [Enum] Re: I-D ACTION:draft-chenbo-enum-mgcp-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bernie Hoeneisen List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Dear authors of draft-chenbo-enum-mgcp-00.txt! This is an interesting document. I especially like the comprehesive examples section. Could you please consider to use the "Guide and Template for IANA Registrations of Enumservices" http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.txt (or soon http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-04.txt) as a guideline for future revisions of your Internet-Draft, so that all the chapters required for a ENUMservice registrations are coverered. cheers, Bernie On Fri, 29 Jun 2007, Richard Shockey wrote: > > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Thursday, June 28, 2007 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-chenbo-enum-mgcp-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Telephone Number Mapping (ENUM) Service > Registration for MGCP > Author(s) : C. Bo, et al. > Filename : draft-chenbo-enum-mgcp-00.txt > Pages : 13 > Date : 2007-6-28 > > MGCP decomposes a multimedia gateway into two parts, a call agent and > a media gateway,thus brings greater extensibility and makes it easy > to construct a large-scale VoIP network. This document registers the > MGCP Enumservice according to the guidelines given in RFC 3761 > [3].This kind of Enumservice is mainly applied in Carrier Networks. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-chenbo-enum-mgcp-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > Internet-Drafts are also available by anonymous FTP. Login with the > username "anonymous" and a password of your e-mail address. After > logging in, type "cd internet-drafts" and then > "get draft-chenbo-enum-mgcp-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-chenbo-enum-mgcp-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 29 11:17:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4IE5-0005E4-AS; Fri, 29 Jun 2007 11:17:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4IE4-0005CN-3C for enum@ietf.org; Fri, 29 Jun 2007 11:17:36 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4IDQ-0005mJ-G4 for enum@ietf.org; Fri, 29 Jun 2007 11:17:35 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5TFGdj9025611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Jun 2007 08:16:40 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" , "'IETF ENUM WG'" References: <02a401c7ba56$3ba5bda0$b2f138e0$@us> In-Reply-To: Subject: RE: [Enum] Re: I-D ACTION:draft-chenbo-enum-mgcp-00.txt Date: Fri, 29 Jun 2007 11:15:39 -0400 Message-ID: <031f01c7ba60$5ae803d0$10b80b70$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace6XvQynhrrbdiLQPmNHjzcJO3RJwAAGrnA Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 Cc: X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Bernie ... thanks for bringing this up. I was just about to write a similar message. I agree this is clearly an interesting document and well within the scope of what we have been doing with ENUMservice registrations. As for the status of this document .. Its clear that after Chicago we are going into a somewhat dormant phase. The WG will not close down..yet. The list will remain open, after all there is still work to finish, but realistically we cant take on any new work. This document clearly needs to be the "poster child" or test case for the ENUMservice registration process. Which is why your earlier notes were very timely. I have asked Jon Peterson to offer up his thoughts on what are the proper tests for the process and we should nag him in Chicago to let us know what he is looking for. -----Original Message----- From: Bernie Hoeneisen [mailto:bhoeneis@switch.ch] Sent: Friday, June 29, 2007 11:03 AM To: 'IETF ENUM WG' Subject: [Enum] Re: I-D ACTION:draft-chenbo-enum-mgcp-00.txt Dear authors of draft-chenbo-enum-mgcp-00.txt! This is an interesting document. I especially like the comprehesive examples section. Could you please consider to use the "Guide and Template for IANA Registrations of Enumservices" http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.tx t (or soon http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-04.tx t) as a guideline for future revisions of your Internet-Draft, so that all the chapters required for a ENUMservice registrations are coverered. cheers, Bernie On Fri, 29 Jun 2007, Richard Shockey wrote: > > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Thursday, June 28, 2007 3:50 PM > To: i-d-announce@ietf.org > Subject: I-D ACTION:draft-chenbo-enum-mgcp-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Telephone Number Mapping (ENUM) Service > Registration for MGCP > Author(s) : C. Bo, et al. > Filename : draft-chenbo-enum-mgcp-00.txt > Pages : 13 > Date : 2007-6-28 > > MGCP decomposes a multimedia gateway into two parts, a call agent and > a media gateway,thus brings greater extensibility and makes it easy > to construct a large-scale VoIP network. This document registers the > MGCP Enumservice according to the guidelines given in RFC 3761 > [3].This kind of Enumservice is mainly applied in Carrier Networks. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-chenbo-enum-mgcp-00.txt > > To remove yourself from the I-D Announcement list, send a message to > i-d-announce-request@ietf.org with the word unsubscribe in the body of > the message. > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. > > Internet-Drafts are also available by anonymous FTP. Login with the > username "anonymous" and a password of your e-mail address. After > logging in, type "cd internet-drafts" and then > "get draft-chenbo-enum-mgcp-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-chenbo-enum-mgcp-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Jun 29 11:32:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4ISE-0003O8-8i; Fri, 29 Jun 2007 11:32:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4ISD-0003Ny-Am for enum@ietf.org; Fri, 29 Jun 2007 11:32:13 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4IRg-00010s-V8 for enum@ietf.org; Fri, 29 Jun 2007 11:32:13 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l5TFVFB0028890 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Jun 2007 08:31:16 -0700 From: "Richard Shockey" To: "'Bernie Hoeneisen'" , References: In-Reply-To: Subject: RE: [Enum] Future ENUMservice registration process; your feedback is appeciated! Date: Fri, 29 Jun 2007 11:30:14 -0400 Message-ID: <032001c7ba62$64ff4200$2efdc600$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ace6W6stiHmRjgYrTDWQp3FFMW2GpgABLTlA Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: 'Cullen Jennings' , "'Peterson, Jon'" X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org A few personal notes here but Bernie again you are right again.. there needs to be a little AD guidance here. The process should perform the function of Enumservice registration, under the aspect that no responsible WG exists ("standalone Registration"?) without curtailing the requirements from RFC3761 regarding the registration process. A rough outline could look like: 1) Write a new Internet-Draft, according to the principles set out in RFC3761 and draft-ietf-enum-enumservices-guide. The key here if I recall Jon's ideas were that we were to be very explicit on what are the appropriate criterion necessary for registration and state the general case of security considerations for all enumservices. Document both use case and examples in the registration template etc. 2) announce the draft on the enum@ietf.org list (which will survive the working group) [option - make an "enumservices-review@ietf.org" mailing list] I think the proper place to start is looking at the process for registering MIME media types. Creation of a new list is probably a good idea but typically the IESG appoints a committee or a "master" that reviews this stuff outside the general scope of direct IESG review. Certainly an AD is appointed to oversee the process but individual RFC are not required. Again the AD are going to have to deliver some guidance here. 3) ask for feedback/review on the list 4) submit the draft as an individual submission to the RFC editor || IESG || IANA. IMHO Expert review > IESG > IANA Open Questions: --------------- 1) Which process applies ("normal" Submission or independent submission)? To whom the I-D is submitted ( IESG || IANA || RFC-Editor )? Who is in charge of the process? Who is the contact to the author(s)? Expert review board or individual, I would guess. That would require as you point out a new mail list. 3) Do we want to have an expert review in the process? If yes, at which state in the process the Expert review is performed? What is the exact task of the expert (just syntax, completeness, or also appropriateness and similar)? IMHO all of the above. Is expert review cunsultance or deciding? Who decides at the end? IESG? IANA? Yep good question. But it will probably be the supervising AD of the expert review committee. Is the Expert review needed in every case? IMHO YES 4) As an alternative to experts, a directorate could perform reviews by request of the IESG. There are potentially two options for that: a) create a dedicated ENUM directorate b) approach the DNS directorate whether they could/would do the ENUMservices reviews Actual question: Is the concept of a directorate viable for reviewing Enumservice registrations? Maybe ... Links: - http://www.rfc-editor.org/indsubs.html - ftp://ftp.rfc-editor.org/internet-drafts/draft-iab-rfc-independent-00.txt - ftp://ftp.rfc-editor.org/in-notes/rfc-editor/rfc-editor-process.gif - https://datatracker.ietf.org/images/state_diagram.gif - http://www.ietf.org/rfc/rfc3761.txt - http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.tx t Looking forward to your feedback and answers! Alex & Bernie PS: Thanks to Andy Newton for reviewing and contributing to our ideas! _______________________________________________ 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