From enum-bounces@ietf.org Tue May 01 11:25:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiuEI-0005qu-8k; Tue, 01 May 2007 11:25:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HiuEG-0005qo-C4 for enum@ietf.org; Tue, 01 May 2007 11:25:24 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiuEF-0007WO-03 for enum@ietf.org; Tue, 01 May 2007 11:25:24 -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 l41FPDTm030583 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 1 May 2007 08:25:14 -0700 From: "Richard Shockey" To: Date: Tue, 1 May 2007 11:24:23 -0400 Message-ID: <01fc01c78c04$cd1e95c0$675bc140$@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: AceMBMw5/zWzDgqwTciNqcscT/qWNw== 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: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [Enum] Are we ready to go to WGLC on this? 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 Speak now or ..you know.. Title : IANA Registration for IAX Enumservice Author(s) : E. Guy Filename : draft-ietf-enum-iax-02.txt Pages : 14 Date : 2007-4-18 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 Wed May 02 03:15:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hj93Y-0004Zx-ER; Wed, 02 May 2007 03:15:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hj93X-0004Zp-6W for enum@ietf.org; Wed, 02 May 2007 03:15:19 -0400 Received: from smtp.denic.de ([81.91.161.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hj93U-0006xS-N1 for enum@ietf.org; Wed, 02 May 2007 03:15:19 -0400 Received: from mail-int1.denic.de (mail-int1.denic.de [192.168.0.45]) by smtp.denic.de with esmtp id 1Hj93T-00053z-1m; Wed, 02 May 2007 09:15:15 +0200 Received: from localhost by mail-int1.denic.de with local id 1Hj93L-0003x8-00; Wed, 02 May 2007 09:15:07 +0200 Date: Wed, 2 May 2007 09:15:07 +0200 From: Peter Koch To: IETF ENUM WG Subject: Re: [Enum] Are we ready to go to WGLC on this? Message-ID: <20070502071507.GA11659@denics7.denic.de> Mail-Followup-To: IETF ENUM WG References: <01fc01c78c04$cd1e95c0$675bc140$@us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01fc01c78c04$cd1e95c0$675bc140$@us> User-Agent: Mutt/1.4i X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On Tue, May 01, 2007, Richard Shockey wrote: > Speak now or ..you know.. > > Title : IANA Registration for IAX Enumservice > Filename : draft-ietf-enum-iax-02.txt I've reviewed draft-ietf-enum-iax-02.txt and here are some remarks before it goes to LC: The boilerplate text in section 1, terminology isn't necessary since no normative language is used in the document. Actually, ``'' might save even more space. > 3. IAX Service Registration > > A client selecting this NAPTR will have support for originating a > call utilizing the IAX2 protocol [ID-IAX]. Is "will have support" meant to read "needs to be able to support"? In the service description, there is only one subtype defined. Our draft guide- lines for ENUM service registrations, "draft-ietf-enum-enumservices-guide-03", suggest that there be at least two or subtypes should not be defined. In the change history it says "* Added the 'iax2' subtype at WG request." and the introduction states about IAX2: "In addition, its open nature permits new payload types additions needed to support additional services." Now, if there is a reason to deviate from the guidelines, it would be good to state that explicitly. The normative reference to [ID-IAX] is definitely necessary. The I-D tracker lists it as "ID exists" only, so what is the status of that document? Is this ENUM service registration aimed at Proposed or Informational? > 4.1. Simple IAX Registration > $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > > @ IN NAPTR 10 100 "u" "E2U+iax:iax2" "!^.*$!iax2:example.com/ > charlie!" NIT: whitespace in URIs ought to be ignored, but that's not necessarily true for the regexp field. Better split the RR over two lines using the '(' ')' RR convention. NIT: the final "." is missing, also with some other NAPTR RRs NIT: a reference to OFCOM's daram numbers might be advised > This contact information indicates that the domain > 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX2 > protocol at domain 'example.com' with the identifier 'charlie'. While I realize the wording is copied from RFC 3761, I don't buy the idea of a domain being contacted. Instead, say that "+442079460148" can be accessed (or contacted, for that matter) via IAX2 or offers service with IAX2 or the like. > 4.2. Registration with Preference Order > > The next example demonstrates that the domain > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. is preferably contacted by IAX2, > secondly via SIP, and then H.323 for voice, and lastly by SMTP for > messaging. Note that the tokens "iax", "sip", "h323", and "msg" are > Types registered (or to be registered) with IANA, and they have no > implicit connection with the protocols or URI schemes with the same > names. Again I understand this is copied from RFC 3761, but see above for the language. Also, I'm not sure what additional insight this example provides, given that the general Preference mechanism is already explained in RFC 3761. Anyway, the subject heading "Preference Order" is a bit misleading since the two fields' names labeled "Preference" and "Order". If the example is going to stay, say, e.g., "Variable Preferences". Ceterum censeo, "msg" should go away. For "sip" and "h323" informative references to RFC 3764 and RFC 3762 could be added. > In each case, the next step in the resolution process is to use the > resolution mechanism appropriate to each of the protocols, (specified > by the URI schemes iax, sip, h323 and mailto). NIT: s/iax/iax2/ > 4.4. IPv6 Registration > > The following is an example of the use of the enumservice registered > by this document in a NAPTR resource record that contains a > destination 'context'. Change introduction to emphasize v6. However, what's the particular point in this example? It appears not even the '[' and ']' characters on the regexp's RHS would need special attention. > $ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > @ IN NAPTR 10 100 "u" "E2U+iax:iax2" "!^.*$!iax2:[2001:db8::1]:4569/ > alice?friends!" NIT: "." as the NAPTR's final element is missing > This contact information indicates that the domain > 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX2 > protocol at IPv6 address [2001:db8::1], port 4569with the identifier > 'alice' in the context (or user partition) 'friends'. NIT: s/port 4569with the/port 4569 with the/ Maybe add a reference to RFC 3849 for the use of 2001:DB8::1. > 5. Security Considerations This section lacks a reference to the basic ENUM security considerations. The reference to RFC 2535 is outdated and needs to be replaced by one to the DNSSECbis trilogy (see, e.g., RFC 4769). This section also should explain what kind of privacy relevant information might be disclosed by publishing NAPTR RRs with the IAX scheme. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed May 02 10:32:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjFsd-0000Qd-Fs; Wed, 02 May 2007 10:32:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjFsc-0000Pn-51 for enum@ietf.org; Wed, 02 May 2007 10:32:30 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjFsb-00067x-Lx for enum@ietf.org; Wed, 02 May 2007 10:32:30 -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 l42EVsER027534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 May 2007 07:31:56 -0700 From: "Richard Shockey" To: "'Peter Koch'" , "'IETF ENUM WG'" References: <01fc01c78c04$cd1e95c0$675bc140$@us> <20070502071507.GA11659@denics7.denic.de> In-Reply-To: <20070502071507.GA11659@denics7.denic.de> Subject: RE: [Enum] Are we ready to go to WGLC on this? Date: Wed, 2 May 2007 10:31:01 -0400 Message-ID: <026601c78cc6$83485f40$89d91dc0$@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: AceMiaRn6t3vAcKQR4mojj0mN8H7NQAPHLHw 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: 42e3ed3f10a1d8bef690f09da16f507a Cc: 'Ed Guy' 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 First thanks for taking the time to review this .. 2 comments in line. -----Original Message----- From: Peter Koch [mailto:pk@DENIC.DE] Sent: Wednesday, May 02, 2007 3:15 AM To: IETF ENUM WG Subject: Re: [Enum] Are we ready to go to WGLC on this? On Tue, May 01, 2007, Richard Shockey wrote: > Speak now or ..you know.. > > Title : IANA Registration for IAX Enumservice > Filename : draft-ietf-enum-iax-02.txt I've reviewed draft-ietf-enum-iax-02.txt and here are some remarks before it goes to LC: The boilerplate text in section 1, terminology isn't necessary since no normative language is used in the document. Actually, ``'' might save even more space. > 3. IAX Service Registration > > A client selecting this NAPTR will have support for originating a > call utilizing the IAX2 protocol [ID-IAX]. Is "will have support" meant to read "needs to be able to support"? In the service description, there is only one subtype defined. Our draft guide- lines for ENUM service registrations, "draft-ietf-enum-enumservices-guide-03", suggest that there be at least two or subtypes should not be defined. In the change history it says "* Added the 'iax2' subtype at WG request." and the introduction states about IAX2: "In addition, its open nature permits new payload types additions needed to support additional services." Now, if there is a reason to deviate from the guidelines, it would be good to state that explicitly. The normative reference to [ID-IAX] is definitely necessary. The I-D tracker lists it as "ID exists" only, so what is the status of that document? RS> it has to go in as a individual submission and yes that is the obvious normative reference. Is this ENUM service registration aimed at Proposed or Informational? RS> Proposed ..all registration documents are Proposed > 4.1. Simple IAX Registration > $ORIGIN 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > > @ IN NAPTR 10 100 "u" "E2U+iax:iax2" "!^.*$!iax2:example.com/ > charlie!" NIT: whitespace in URIs ought to be ignored, but that's not necessarily true for the regexp field. Better split the RR over two lines using the '(' ')' RR convention. NIT: the final "." is missing, also with some other NAPTR RRs NIT: a reference to OFCOM's daram numbers might be advised > This contact information indicates that the domain > 8.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX2 > protocol at domain 'example.com' with the identifier 'charlie'. While I realize the wording is copied from RFC 3761, I don't buy the idea of a domain being contacted. Instead, say that "+442079460148" can be accessed (or contacted, for that matter) via IAX2 or offers service with IAX2 or the like. > 4.2. Registration with Preference Order > > The next example demonstrates that the domain > 3.8.0.0.6.9.2.3.6.1.4.4.e164.arpa. is preferably contacted by IAX2, > secondly via SIP, and then H.323 for voice, and lastly by SMTP for > messaging. Note that the tokens "iax", "sip", "h323", and "msg" are > Types registered (or to be registered) with IANA, and they have no > implicit connection with the protocols or URI schemes with the same > names. Again I understand this is copied from RFC 3761, but see above for the language. Also, I'm not sure what additional insight this example provides, given that the general Preference mechanism is already explained in RFC 3761. Anyway, the subject heading "Preference Order" is a bit misleading since the two fields' names labeled "Preference" and "Order". If the example is going to stay, say, e.g., "Variable Preferences". Ceterum censeo, "msg" should go away. For "sip" and "h323" informative references to RFC 3764 and RFC 3762 could be added. > In each case, the next step in the resolution process is to use the > resolution mechanism appropriate to each of the protocols, (specified > by the URI schemes iax, sip, h323 and mailto). NIT: s/iax/iax2/ > 4.4. IPv6 Registration > > The following is an example of the use of the enumservice registered > by this document in a NAPTR resource record that contains a > destination 'context'. Change introduction to emphasize v6. However, what's the particular point in this example? It appears not even the '[' and ']' characters on the regexp's RHS would need special attention. > $ORIGIN 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. > @ IN NAPTR 10 100 "u" "E2U+iax:iax2" "!^.*$!iax2:[2001:db8::1]:4569/ > alice?friends!" NIT: "." as the NAPTR's final element is missing > This contact information indicates that the domain > 9.4.1.0.6.4.9.7.0.2.4.4.e164.arpa. may be contacted by using the IAX2 > protocol at IPv6 address [2001:db8::1], port 4569with the identifier > 'alice' in the context (or user partition) 'friends'. NIT: s/port 4569with the/port 4569 with the/ Maybe add a reference to RFC 3849 for the use of 2001:DB8::1. > 5. Security Considerations This section lacks a reference to the basic ENUM security considerations. The reference to RFC 2535 is outdated and needs to be replaced by one to the DNSSECbis trilogy (see, e.g., RFC 4769). This section also should explain what kind of privacy relevant information might be disclosed by publishing NAPTR RRs with the IAX scheme. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed May 02 11:51:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjH6x-00026f-0n; Wed, 02 May 2007 11:51:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjH6v-00024M-7h for enum@ietf.org; Wed, 02 May 2007 11:51:21 -0400 Received: from fw-d-whp.denic.de ([81.91.160.27] helo=denic.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjH6t-0004NU-Tg for enum@ietf.org; Wed, 02 May 2007 11:51:21 -0400 Received: by unknown.office.denic.de (Postfix, from userid 501) id BAD454921B9; Wed, 2 May 2007 17:51:16 +0200 (CEST) Date: Wed, 2 May 2007 17:51:16 +0200 From: Peter Koch To: Richard Shockey Subject: Re: [Enum] Are we ready to go to WGLC on this? Message-ID: <20070502155116.GG866@unknown.office.denic.de> Mail-Followup-To: Richard Shockey , 'IETF ENUM WG' , 'Ed Guy' References: <01fc01c78c04$cd1e95c0$675bc140$@us> <20070502071507.GA11659@denics7.denic.de> <026601c78cc6$83485f40$89d91dc0$@us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <026601c78cc6$83485f40$89d91dc0$@us> User-Agent: Mutt/1.4.2.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: 'IETF ENUM WG' , 'Ed Guy' X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Thanks, Richard, for responding to my questions. > Is this ENUM service registration aimed at Proposed or Informational? > > RS> Proposed ..all registration documents are Proposed I understand that this happened in the past, but now that we're considering an easier method for registering ENUM services, there might no longer be an immediate need for Standards Track. By the way, I just overlooked that the draft's header says "Intended status: Informational". In this particular case, there's an additional argument for "Informational": The base IAX spec appears as a normative reference and the draft does not give the IETF change control (see boilerplate): This document may not be modified, and derivative works of it may not be created. So, my understanding is it is unlikely this will be published as anything else but Informational. As a corollary, the ENUM services document can only be Informational as well. Whether or not an ENUM service is "derivative works" is for somebody else to decide. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed May 02 12:19: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 1HjHXu-0000Nw-Gf; Wed, 02 May 2007 12:19:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjHXt-0000Np-Ri for enum@ietf.org; Wed, 02 May 2007 12:19:13 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjHXs-00019B-Gv for enum@ietf.org; Wed, 02 May 2007 12:19: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 l42GIuhU015211 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 May 2007 09:18:58 -0700 From: "Richard Shockey" To: "'Peter Koch'" References: <01fc01c78c04$cd1e95c0$675bc140$@us> <20070502071507.GA11659@denics7.denic.de> <026601c78cc6$83485f40$89d91dc0$@us> <20070502155116.GG866@unknown.office.denic.de> In-Reply-To: <20070502155116.GG866@unknown.office.denic.de> Subject: RE: [Enum] Are we ready to go to WGLC on this? Date: Wed, 2 May 2007 12:18:01 -0400 Message-ID: <02cc01c78cd5$77320d00$65962700$@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: AceM0b2Uo4LrhY7iQJWlxhtMA67Y4gAA4Fng 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: 97adf591118a232206bdb5a27b217034 Cc: 'IETF ENUM WG' X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Again Peter ..many thanks for pointing out the status issue out ..you are totally correct. -----Original Message----- From: Peter Koch [mailto:pk@DENIC.DE] Sent: Wednesday, May 02, 2007 11:51 AM To: Richard Shockey Cc: 'IETF ENUM WG'; 'Ed Guy' Subject: Re: [Enum] Are we ready to go to WGLC on this? Thanks, Richard, for responding to my questions. > Is this ENUM service registration aimed at Proposed or Informational? > > RS> Proposed ..all registration documents are Proposed I understand that this happened in the past, but now that we're considering an easier method for registering ENUM services, there might no longer be an immediate need for Standards Track. By the way, I just overlooked that the draft's header says "Intended status: Informational". In this particular case, there's an additional argument for "Informational": The base IAX spec appears as a normative reference and the draft does not give the IETF change control (see boilerplate): This document may not be modified, and derivative works of it may not be created. So, my understanding is it is unlikely this will be published as anything else but Informational. As a corollary, the ENUM services document can only be Informational as well. Whether or not an ENUM service is "derivative works" is for somebody else to decide. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed May 02 14:23:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjJUC-0003MI-Ng; Wed, 02 May 2007 14:23:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjJUB-0003M8-IC for enum@ietf.org; Wed, 02 May 2007 14:23:31 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjJUA-0006qI-5q for enum@ietf.org; Wed, 02 May 2007 14:23:31 -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 l42IN3K2006910 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 May 2007 11:23:04 -0700 From: "Richard Shockey" To: "'Peter Koch'" References: <01fc01c78c04$cd1e95c0$675bc140$@us> <20070502071507.GA11659@denics7.denic.de> <026601c78cc6$83485f40$89d91dc0$@us> <20070502155116.GG866@unknown.office.denic.de> <02cc01c78cd5$77320d00$65962700$@us> In-Reply-To: <02cc01c78cd5$77320d00$65962700$@us> Subject: RE: [Enum] Are we ready to go to WGLC on this? Date: Wed, 2 May 2007 14:22:09 -0400 Message-ID: <004701c78ce6$cce90b20$66bb2160$@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: AceM0b2Uo4LrhY7iQJWlxhtMA67Y4gAA4FngAARCjqA= 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: 7aafa0432175920a4b3e118e16c5cb64 Cc: 'IETF ENUM WG' X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org But on second thought .. H.323 IETF has no change control over that either. That does establish some precedent. ON the issue of derivative works from a Informational standard .. I think I'll submit it as Proposed Standard and let the IESG sort out the issue, unless there is strong objection -----Original Message----- From: Richard Shockey [mailto:richard@shockey.us] Sent: Wednesday, May 02, 2007 12:18 PM To: 'Peter Koch' Cc: 'IETF ENUM WG' Subject: RE: [Enum] Are we ready to go to WGLC on this? Again Peter ..many thanks for pointing out the status issue out ..you are totally correct. -----Original Message----- From: Peter Koch [mailto:pk@DENIC.DE] Sent: Wednesday, May 02, 2007 11:51 AM To: Richard Shockey Cc: 'IETF ENUM WG'; 'Ed Guy' Subject: Re: [Enum] Are we ready to go to WGLC on this? Thanks, Richard, for responding to my questions. > Is this ENUM service registration aimed at Proposed or Informational? > > RS> Proposed ..all registration documents are Proposed I understand that this happened in the past, but now that we're considering an easier method for registering ENUM services, there might no longer be an immediate need for Standards Track. By the way, I just overlooked that the draft's header says "Intended status: Informational". In this particular case, there's an additional argument for "Informational": The base IAX spec appears as a normative reference and the draft does not give the IETF change control (see boilerplate): This document may not be modified, and derivative works of it may not be created. So, my understanding is it is unlikely this will be published as anything else but Informational. As a corollary, the ENUM services document can only be Informational as well. Whether or not an ENUM service is "derivative works" is for somebody else to decide. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed May 02 14:41:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjJlO-0001z1-Uu; Wed, 02 May 2007 14:41:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjJlN-0001yw-Rr for enum@ietf.org; Wed, 02 May 2007 14:41:17 -0400 Received: from fw-d-whp.denic.de ([81.91.160.27] helo=denic.de) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjJlM-0000x9-Ia for enum@ietf.org; Wed, 02 May 2007 14:41:17 -0400 Received: by unknown.office.denic.de (Postfix, from userid 501) id CFE784925E7; Wed, 2 May 2007 20:41:11 +0200 (CEST) Date: Wed, 2 May 2007 20:41:11 +0200 From: Peter Koch To: Richard Shockey Subject: Re: [Enum] Are we ready to go to WGLC on this? Message-ID: <20070502184111.GM866@unknown.office.denic.de> Mail-Followup-To: Richard Shockey , 'IETF ENUM WG' References: <01fc01c78c04$cd1e95c0$675bc140$@us> <20070502071507.GA11659@denics7.denic.de> <026601c78cc6$83485f40$89d91dc0$@us> <20070502155116.GG866@unknown.office.denic.de> <02cc01c78cd5$77320d00$65962700$@us> <004701c78ce6$cce90b20$66bb2160$@us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004701c78ce6$cce90b20$66bb2160$@us> User-Agent: Mutt/1.4.2.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: 'IETF ENUM WG' X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Hi Richard, > But on second thought .. H.323 IETF has no change control over that either. > That does establish some precedent. sorry, that was misleading. My issue was a downref one, i.e., a spec that is available as Informational RFC only (concluded from the current boilerplate) would not allow the referencing document to advance past that. H.323 is available as an ITU-T document and there's some formal liaison between the IETF and ITU-T about references to documents. > ON the issue of derivative works from a Informational standard .. I think > I'll submit it as Proposed Standard and let the IESG sort out the issue, > unless there is strong objection Not here. And I agree some process advice might be helpful. -Peter _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri May 04 15:50: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 1Hk3n1-0007Eq-Nz; Fri, 04 May 2007 15:50:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk3n0-0007EK-PD; Fri, 04 May 2007 15:50:02 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hk3n0-0004eg-GY; Fri, 04 May 2007 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 61B1A26F15; Fri, 4 May 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hk3n0-0006BO-9T; Fri, 04 May 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: Fri, 04 May 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-xmpp-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : IANA Registration for Enumservice 'XMPP' Author(s) : A. Mayrhofer Filename : draft-ietf-enum-xmpp-02.txt Pages : 8 Date : 2007-5-4 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). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-xmpp-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-xmpp-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-xmpp-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-5-4142222.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-xmpp-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-xmpp-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-4142222.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Mon May 07 08:44: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 1Hl2ZZ-0006Tc-Ch; Mon, 07 May 2007 08:44:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hl2ZY-0006TV-67 for enum@ietf.org; Mon, 07 May 2007 08:44:12 -0400 Received: from emcsw.com ([69.28.242.167] helo=www.eguy.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hl2ZX-0008W6-03 for enum@ietf.org; Mon, 07 May 2007 08:44:12 -0400 Received: from host-24-225-134-24.patmedia.net ([24.225.134.24]:4266 helo=[192.168.1.4]) by www.eguy.org with esmtpsa (SSL 3.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1Hl2ZW-0004bw-1K for enum@ietf.org; Mon, 07 May 2007 08:44:10 -0400 Message-ID: <463F1E82.6050206@eGuy.org> Date: Mon, 07 May 2007 08:41:38 -0400 From: Ed Guy User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: enum@ietf.org Subject: [Fwd: Re: [Enum] Are we ready to go to WGLC on this?] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 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 [sent to peter last week, but the working group was mistakenly not cc'd] Peter, Thank you for the detailed comments! Peter Koch wrote: ... > The normative reference to [ID-IAX] is definitely necessary. The I-D tracker > lists it as "ID exists" only, so what is the status of that document? > This document is back to "ISR = Independent Submission Review by the RFC Editor" in the RFC editor's queue. (it was previously ISR-AUTH) It has only been in this state for a couple weeks. ... > Is this ENUM service registration aimed at Proposed or Informational? > Even though the underlying protocol is informational, there is at least one other example where the referenced protocol is not on the IETF Standards track: H.323. IMHO, it does makes sense to have a standardized mechanism to reference a non-standardized protocol. Hence, in addition to following your other suggestions, I'll fix the ID to remove the "informational" and replace it with "Standards Track" (unless directed or convinced otherwise...) Best Regards Ed Guy _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue May 08 18:50: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 1HlYVw-0001mo-Se; Tue, 08 May 2007 18:50:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlYVR-0008R5-Fq; Tue, 08 May 2007 18:50:05 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlYVR-0002YM-0V; Tue, 08 May 2007 18:50:05 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 943CC26EBA; Tue, 8 May 2007 22:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HlYVO-0002Fn-NY; Tue, 08 May 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: Tue, 08 May 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-validation-token-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 : ENUM Validation Token Format Definition Author(s) : O. Lendl Filename : draft-ietf-enum-validation-token-03.txt Pages : 17 Date : 2007-5-8 An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes an signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-token-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-validation-token-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-validation-token-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-5-8162220.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-validation-token-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-validation-token-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-8162220.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Tue May 08 22:27:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlbtz-0001pb-Sm; Tue, 08 May 2007 22:27:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hlbty-0001pW-TF for enum@ietf.org; Tue, 08 May 2007 22:27:38 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hlbtx-0005Hw-Gt for enum@ietf.org; Tue, 08 May 2007 22:27:38 -0400 Received: from rshockeyPC (h-68-165-240-38.mclnva23.covad.net [68.165.240.38]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l492REoc029748 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 8 May 2007 19:27:16 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Tue, 8 May 2007 22:26:12 -0400 Message-ID: <002e01c791e1$6b496630$41dc3290$@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: AceR4WlpMZifA2wdQhOv4kbpiClWQg== 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: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [Enum] Chicago is rapidly approaching .. 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 We are winding down but we do have several important items on the plate that need to be resolved. The revision of RFC 3761 will be ongoing but the single most important task is defining a standard methodology for creating ENUMserivces. http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-03.tx t I would ask the list to take some time and offer comments and suggestions on the current draft consistent with what we discussed in Prague and hopefully defining a common security definition as well as what is and what is not appropriate for registration. This is important. Lets do the work now. 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 Sat May 12 13:23:51 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmvJg-00008q-Hd; Sat, 12 May 2007 13:23:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmvJe-0008W1-OQ; Sat, 12 May 2007 13:23:34 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HmvJd-00087E-Nd; Sat, 12 May 2007 13:23:34 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm414646570c; Sun, 13 May 2007 01:34:37 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm4846417118; Wed, 09 May 2007 07:03:48 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Wed, 09 May 2007 07:03:48 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlYVy-0001n3-Q0; Tue, 08 May 2007 18:50:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HlYVR-0008R5-Fq; Tue, 08 May 2007 18:50:05 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HlYVR-0002YM-0V; Tue, 08 May 2007 18:50:05 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 943CC26EBA; Tue, 8 May 2007 22:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HlYVO-0002Fn-NY; Tue, 08 May 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: Tue, 08 May 2007 18:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Archive: X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Spam-Score: 2.2 (++) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-validation-token-03.txt X-BeenThere: enum@ietf.org Reply-To: internet-drafts@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : ENUM Validation Token Format Definition Author(s) : O. Lendl Filename : draft-ietf-enum-validation-token-03.txt Pages : 17 Date : 2007-5-8 An ENUM domain name is tightly coupled with the underlying E.164 number. The process of verifying whether the Registrant of an ENUM domain name is identical to the Assignee of the corresponding E.164 number is commonly called "validation". This document describes an signed XML data format -- the Validation Token -- with which Validation Entities can convey successful completion of a validation procedure in a secure fashion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-token-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-validation-token-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-validation-token-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-5-8162220.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-validation-token-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-validation-token-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-8162220.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Thu May 17 09:15:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HofpU-0007k8-3f; Thu, 17 May 2007 09:15:40 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HofpS-0007jr-5i; Thu, 17 May 2007 09:15:38 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HofpP-0005PJ-Rc; Thu, 17 May 2007 09:15:38 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id C5AF52AC64; Thu, 17 May 2007 13:15:05 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hofov-0001dK-Ec; Thu, 17 May 2007 09:15:05 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 17 May 2007 09:15:05 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: enum@ietf.org Subject: [Enum] Last Call: draft-ietf-enum-validation-token (ENUM Validation Token Format Definition) to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has received a request from the Telephone Number Mapping WG (enum) to consider the following document: - 'ENUM Validation Token Format Definition ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-05-31. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-token-03.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13754&rfc_flag=0 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu May 17 14:47:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hol0S-0004J6-4V; Thu, 17 May 2007 14:47:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hol0Q-0004Iy-8e; Thu, 17 May 2007 14:47:18 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hol0P-0001wJ-2S; Thu, 17 May 2007 14:47:18 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 0D49F32948; Thu, 17 May 2007 18:47:17 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hol0O-0001Yh-Ul; Thu, 17 May 2007 14:47:16 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 17 May 2007 14:47:16 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: enum@ietf.org Subject: [Enum] Last Call: draft-ietf-enum-validation-epp (ENUM Validation Information Mapping for the Extensible Provisioning Protocol) to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has received a request from the Telephone Number Mapping WG (enum) to consider the following document: - 'ENUM Validation Information Mapping for the Extensible Provisioning Protocol ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-05-31. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-epp-05.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13637&rfc_flag=0 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri May 18 08:54:33 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp1yY-0006IJ-1u; Fri, 18 May 2007 08:54:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hp1yX-0006IB-LZ; Fri, 18 May 2007 08:54:29 -0400 Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hp1yW-0000aj-Ff; Fri, 18 May 2007 08:54:29 -0400 Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id l4ICrXKR021438; Fri, 18 May 2007 08:53:33 -0400 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 May 2007 08:54:28 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] Last Call: draft-ietf-enum-validation-epp (ENUM Validation Information Mapping for the Extensible Provisioning Protocol) to Proposed Standard X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 18 May 2007 08:54:49 -0400 Message-ID: <046F43A8D79C794FA4733814869CDF0701D6BE61@dul1wnexmb01.vcorp.ad.vrsn.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Last Call: draft-ietf-enum-validation-epp (ENUM Validation Information Mapping for the Extensible Provisioning Protocol) to Proposed Standard Thread-Index: AceYs90hwj7FYKl7Tlqdt4cJoc5ELgAl3eEA From: "Hollenbeck, Scott" To: X-OriginalArrivalTime: 18 May 2007 12:54:28.0131 (UTC) FILETIME=[AB71D730:01C7994B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > -----Original Message----- > From: The IESG [mailto:iesg-secretary@ietf.org]=20 > Sent: Thursday, May 17, 2007 2:47 PM > To: IETF-Announce > Cc: enum@ietf.org > Subject: [Enum] Last Call: draft-ietf-enum-validation-epp=20 > (ENUM Validation Information Mapping for the Extensible=20 > Provisioning Protocol) to Proposed Standard=20 >=20 > The IESG has received a request from the Telephone Number Mapping WG=20 > (enum) to consider the following document: >=20 > - 'ENUM Validation Information Mapping for the Extensible=20 > Provisioning=20 > Protocol ' > as a Proposed Standard I support approval of this document. I checked the schemas and several of the examples using the core EPP schemas and all looks fine syntactically. -Scott- _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon May 21 15:50:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqDtS-0007X4-NL; Mon, 21 May 2007 15:50:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqDtL-0007Ud-Qj; Mon, 21 May 2007 15:50:03 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqDtK-000660-NS; Mon, 21 May 2007 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 9D48F32932; Mon, 21 May 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HqDtK-0002XY-H8; Mon, 21 May 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: Mon, 21 May 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-infrastructure-enum-reqs-04.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 : Infrastructure ENUM Requirements Author(s) : S. Lind, P. Pfautz Filename : draft-ietf-enum-infrastructure-enum-reqs-04.txt Pages : 8 Date : 2007-5-21 This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-04.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-infrastructure-enum-reqs-04.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-infrastructure-enum-reqs-04.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-5-21134150.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-infrastructure-enum-reqs-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-21134150.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 May 23 14:54:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqvyO-0007tX-6G; Wed, 23 May 2007 14:54:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HqvyM-0007tS-UV for enum@ietf.org; Wed, 23 May 2007 14:54:10 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HqvyL-0000gS-IX for enum@ietf.org; Wed, 23 May 2007 14:54:10 -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 l4NIrqXf029815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 23 May 2007 11:53:54 -0700 From: "Richard Shockey" To: "'IETF ENUM WG'" Date: Wed, 23 May 2007 14:53:23 -0400 Message-ID: <001c01c79d6b$a5fc37e0$f1f4a7a0$@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: Aceda6HQM8wIsBmISMiozLNGO8F11Q== 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: bb8f917bb6b8da28fc948aeffb74aa17 Subject: [Enum] CALL for WG agenda items ... 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 Its that time again. If you have any agenda items now is the time to let the chairs know. The schedule is preliminary but it looks like we have a Monday slot again for those of you making travel plans. This is NOT the final schedule but a good indication. MONDAY, July 23, 2007 0800-1800 IETF Registration - 0800-0900 Morning Beverages - 0900-1130 Morning Session I 1500-1520 Afternoon Beverage Break I - 1520-1720 Afternoon Session II Breakout 1 APP sieve Sieve Mail Filtering Language WG Breakout 5 INT intarea Internet Area Open Meeting Breakout 6 RAI avt Audio/Video Transport WG Breakout 7 RAI enum Telephone Number Mapping WG Breakout 4 RTG pce Path Computation Element WG Breakout 2 RTG sidr Secure Inter-Domain Routing WG Breakout 3 SEC nea Network Endpoint Assessment WG 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 Thu May 24 05:19: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 1Hr9Tb-00046s-I8; Thu, 24 May 2007 05:19:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hr9TZ-00046k-Ao for enum@ietf.org; Thu, 24 May 2007 05:19:17 -0400 Received: from cellgate.btcellnet.net ([158.230.100.102] helo=uksthmsw005.uk.pri.o2.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hr9TY-0002K0-RG for enum@ietf.org; Thu, 24 May 2007 05:19:17 -0400 Received: from uksthims002.uk.pri.o2.com (uksthims002.uk.pri.o2.com) by uksthmsw005.uk.pri.o2.com (Clearswift SMTPRS 5.1.7) with ESMTP id ; Thu, 24 May 2007 10:19:13 +0100 Received: from UKSTHMSX007.uk.pri.o2.com ([172.17.62.169]) by uksthims002.uk.pri.o2.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 May 2007 10:19:13 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 24 May 2007 10:19:12 +0100 Message-ID: <42986C4138E81A4494E4BDEA0978CB5501F41E90@UKSTHMSX007.uk.pri.o2.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comments on "e212" enumservice and "e212" parameters for Tel URI Thread-Index: Aced44X1ZXZCG16rQI63cZgrLUsz1g== From: "Fullbrook Kim (UK)" To: , "Richard Shockey" , =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= X-OriginalArrivalTime: 24 May 2007 09:19:13.0170 (UTC) FILETIME=[9801AF20:01C79DE4] X-Spam-Score: 0.1 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: Subject: [Enum] Comments on "e212" enumservice and "e212" parameters for Tel URI 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 INTRODUCTION The ENUM Group within the GSM Association is a technical working group dedi= cated to the discussion and agreement of ENUM-related issues that affect GS= M operators. The GSM Association represents the interests of GSM operators = worldwide. Some ENUM group members became aware of certain draft proposals from the IE= TF ENUM group and were concerned about their content. These proposals have = been discussed within the GSMA ENUM group and the results are summarised in= this email. PROPOSALS The IETF has published two recent draft proposals: 1) E.212 ENUMService Type Definition draft-lewis-enum-enumservice-e212-00.t= xt 2) E.212 Parameters for the "tel" URI draft-lewis-enum-teluri-e212-00.txt GSMA ENUM Group members have serious concerns about these proposals.=20 ENUM GROUP COMMENTS - PROPOSAL 1 Firstly it is described as potentially providing, for example, the ability = to identify the service provider for a telephone number for billing purpose= s by using the "Mobile network code" (MNC) and "mobile country code" (MCC) = parameters. The MNC does not identify a service provider. In many GSM networks there ar= e multiple service providers providing service to customers, each sharing t= he single MNC used by the Network Operator. It is therefore not possible to= identify the service provider based on MNC. Secondly an additional parameter has been included in the definition - Mobi= le Subscriber Identification Number (MSIN). Together MNC, MCC and MSIN defi= ne the IMSI (International Mobile Subscriber Identity).=20 Divulging IMSIs facilitates fraud or abuse at the expense of mobile operato= rs' customers. The design of GSM systems has therefore included special mea= sures to protect an IMSI from being revealed unintentionally by using tempo= rary identities such as TMSIs and P-TMSIs. GSM operators have been consulte= d about this proposal and unanimously declared that they: - do not want to see IMSI held in a DNS=20 - wish to see MSIN and IMSI removed from this ENUMservice Type Definition. ENUM GROUP COMMENTS - PROPOSAL 2 Comments on proposal 2) GSM operators have similar comments to proposal 1). They have declared unan= imously that they do not want the ability to store IMSI in a DNS because of= security concerns. There are no security concerns around storage of MNC an= d MCC. However GSM operators are unconvinced about the value of storing the= m in a Tel URI and wish to see some use cases as a justification. As in the= previous section they have noted that MNC cannot be used to indicate a bil= ling relationship for an E.164 number. WAY FORWARD The GSMA ENUM group recommends the IETF to: i) abandon these proposals in their present form due to the short-falls det= ailed above; ii) Provide rationale, along with examples, to support any future ENUM-rela= ted proposals that include Mobile Network Code and Mobile Country Code. Kim Fullbrook,=20 O2 UK,=20 Chair GSMA ENUM Group This electronic message contains information from O2 which may be privilege= d or confidential. The information is intended to be for the use of the ind= ividual(s) or entity named above. If you are not the intended recipient be = aware that any disclosure, copying distribution or use of the contents of t= his information is prohibited. If you have received this electronic message= in error, please notify us by telephone or email (to the numbers or addres= s below) immediately. Switchboard: +44(0)1753 565000 O2 (UK) Limited 260 Bath Road, Slough, Berkshire SL1 4DX Registered in Engl= and and Wales: 1743099. VAT number: GB 778 6037 85 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon May 28 14:48:33 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HskGV-0001e8-8e; Mon, 28 May 2007 14:48:23 -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 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 X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has 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. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue May 29 15:50:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht7i9-00011F-Oj; Tue, 29 May 2007 15:50:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ht7hj-0000Y4-AL; Tue, 29 May 2007 15:50:03 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ht7hj-0006hy-1Y; Tue, 29 May 2007 15:50:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DFEED3293F; Tue, 29 May 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Ht7hi-0007NX-NY; Tue, 29 May 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, 29 May 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-cnam-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 : IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for Media type "application/cnam" Author(s) : R. Shockey, et al. Filename : draft-ietf-enum-cnam-05.txt Pages : 13 Date : 2007-5-29 This document registers the Enumservice "pstn" and subtype "cnam" using the URI scheme "data:" as per the IANA registration process defined in the ENUM specification, RFC 3761[1] and registers a new media type application/cnam [17]. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the Public Switched Telephone Network (PSTN) that may be displayed on VoIP or other Real-time Client User Agents (CUA). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-cnam-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-cnam-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-cnam-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-5-29132948.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-cnam-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-cnam-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-5-29132948.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--