From enum-bounces@ietf.org Thu Mar 02 14:46:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEtkK-0002wU-BS; Thu, 02 Mar 2006 14:45:56 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEtkJ-0002wP-FA for enum@ietf.org; Thu, 02 Mar 2006 14:45:55 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEtkI-0004t4-2z for enum@ietf.org; Thu, 02 Mar 2006 14:45:55 -0500 Received: from [10.31.13.105] (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k22JkStc009282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 2 Mar 2006 11:46:29 -0800 Message-ID: <44074B6D.20800@shockey.us> Date: Thu, 02 Mar 2006 14:45:49 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Enum] FYI ENUM and Speermint look solid for Monday. 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 For those of you dealing with flights etc. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 07 02:50:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGWxc-00050I-Li; Tue, 07 Mar 2006 02:50:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGWxK-0004Qr-Lt; Tue, 07 Mar 2006 02:50:06 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=pine.neustar.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGWxG-0005Ib-8K; Tue, 07 Mar 2006 02:50:06 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k277o1vP017075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Mar 2006 07:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FGWxF-0002jk-Pg; Tue, 07 Mar 2006 02:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 07 Mar 2006 02:50:01 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-infrastructure-enum-reqs-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : Infrastrucure ENUM Requirements Author(s) : S. Lind, P. Pfautz Filename : draft-ietf-enum-infrastructure-enum-reqs-00.txt Pages : 7 Date : 2006-3-6 This document provides requirements for "infrastructure" or "carrier" ENUM, 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-infrastructure-enum-reqs-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-3-6195212.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-infrastructure-enum-reqs-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-6195212.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 Mar 07 10:28:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGe6w-0005ip-1e; Tue, 07 Mar 2006 10:28:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGe6u-0005hz-IK for enum@ietf.org; Tue, 07 Mar 2006 10:28:28 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGe6s-0006Yt-WA for enum@ietf.org; Tue, 07 Mar 2006 10:28:28 -0500 Received: from [10.31.13.237] (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k27FSs9Y025709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Mar 2006 07:28:55 -0800 Message-ID: <440DA690.7080109@shockey.us> Date: Tue, 07 Mar 2006 10:28:16 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186 Subject: [Enum] Almost complete Agenda for IETF 65 Dallas 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 IETF 65 Dallas Telephone Number Mapping (ENUM) WG Agenda Preliminary Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alex Mayrhofer Real Time Applications Infrastructure Area Director(s): Cullen Jennings Jon Peterson Real Time Applications Infrastructure Area Advisor: Cullen Jennings MONDAY, March 20, 2006 0800-1800 IETF Registration - 0800-0900 Continental Breakfast - 0900-1130 Morning Session I APP apparea Applications Area Open Meeting INT dna Detecting Network Attachment WG OPS netconf Network Configuration WG RAI enum Telephone Number Mapping WG RAI mmusic Multiparty Multimedia Session Control WG RTG mpls Multiprotocol Label Switching WG SEC krb-wg Kerberos WG AGENDA BASHING (5 min) ENUM Implementers Draft: (Final Version) 5 MIN Title : ENUM Implementation Issues and Experiences Title : ENUM Requirement for EDNS0 Support ( ??? ) Title : Guide and Template for IANA Registrations of Enumervices [ 15 M ] Author(s) : J. Livingood, B. Hoeneisen Filename : draft-ietf-enum-enumservices-guide-00.txt Pages : 12 Date : 2006-2-27 This document provides a guide to and template for the creation of new IANA registration of ENUM services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-00.txt Title : IANA Registration for an Enumservice and "tel" [ 20 Min ] Parameter for Calling Name Delivery(CNAM) Information Author(s) : R. Shockey, J. Livingood Filename : draft-shockey-enum-cnam-00.txt Pages : 10 Date : 2006-1-13 This document registers the Enumservice "cnam" and subtype "tel" using the URI scheme 'tel:', as per the IANA registration process defined in the ENUM specification, RFC 3761. In addition this document registers the parameter "cnam" in the IANA "tel" Parameter Registry defined in RFCXXX. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the 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-shockey-enum-cnam-00.txt Title : IANA Registration for IAX Enumservice [ 15 M ] Author(s) : E. Guy Filename : draft-ietf-enum-iax-00.txt Pages : 13 Date : 2006-2-22 This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' as per the IANA registration process defined in the ENUM specification RFC3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-iax-00.txt Title : Telephone Number Mapping and Domain Keys as a Distributed Identity Infrastructure [ 15 M ] Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-domainkeys-00.txt Pages : 10 Date : 2006-2-23 This document creates a decentralized indentity infrastructure by combining technology from E.164 Number Mapping (ENUM) and DomainKeys Identified Mail (DKIM). This infrastructure uses E.164 numbers as identities, ENUM DNS for key distribution, and leverages the trust relations from ENUM validation to actual messages signed by the number holder. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-domainkeys-00.txt Title : IANA Registration for Enumservice foaf [ 15 Min ] Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-00.txt Pages : 9 Date : 2006-2-15 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-00.txt Title : A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-im-service-00.txt Pages : 5 Date : 2006-2-22 This document registers a Telephone Number Mapping (ENUM) service for Instant Messaging (IM). Specifically, this document focuses on provisioning im: URIs in ENUM. Title : A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-calendar-service-00.txt Pages : 5 Date : 2006-2-23 This document registers a Telephone Number Mapping (ENUM) service for Internet Calendaring Services. Specifically, this document focuses on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mahy-enum-calendar-service-00.txt Title : Infrastrucure ENUM Requirements Author(s) : S. Lind, P. Pfautz [ 20 M ] Filename : draft-ietf-enum-infrastructure-enum-reqs-00.txt Pages : 7 Date : 2006-3-6 This document provides requirements for "infrastructure" or "carrier" ENUM, 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 07 13:01:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGgUl-0005WN-VL; Tue, 07 Mar 2006 13:01:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGgUk-0005Vn-Gs for enum@ietf.org; Tue, 07 Mar 2006 13:01:14 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FGgUg-0004im-L5 for enum@ietf.org; Tue, 07 Mar 2006 13:01:14 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Enum] Almost complete Agenda for IETF 65 Dallas Date: Tue, 7 Mar 2006 19:05:04 +0100 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C48B7@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Almost complete Agenda for IETF 65 Dallas Thread-Index: AcZB/GF/HqG/RDySS4uWijNddzoa+AAE1En9 From: "Stastny Richard" To: "Richard Shockey" , X-Spam-Score: 0.5 (/) X-Scan-Signature: 40161b1d86420e0807d771943d981d25 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 Dear Co-chair, I requested some time ago some time on the agenda for the up issue of our I-D : =20 "Combined User and Carrier ENUM in the e164.arpa tree" - draft-haberler-carrier-enum-02.txt . Abstract: ENUM as defined now in RFC3761 is not well suited for the purpose of interconnection by carriers, as can be seen by the use of various private tree arrangements based on ENUM mechanisms. A combined end-user and carrier ENUM tree solution would leverage the ENUM infrastructure in e164.arpa, increase resolution rates, and decrease the cost per registered telephone number. This document describes a minimally invasive scheme to provide both end-user and carrier data in = ENUM. =20 until it comes out of the queue, the I-D is available at: http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.txt http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.html =20 and the=20 =20 >General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] Adding the proposed agenda times together, only 10 minutes are left for these two items. I am also getting the slight impression that our = esteemed co-chair is taking this issue not really seriois. =20 Since I am preparing also a presentation (to be submitted soon), I request at least 10-20 Min =20 Eventually 5 minuntes could be spared from agenda item CNAM and another 5 from IAX =20 best regards Richard =20 =20 ________________________________ Von: Richard Shockey [mailto:richard@shockey.us] Gesendet: Di 07.03.2006 16:28 An: 'enum@ietf.org' Betreff: [Enum] Almost complete Agenda for IETF 65 Dallas IETF 65 Dallas Telephone Number Mapping (ENUM) WG Agenda Preliminary Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alex Mayrhofer Real Time Applications Infrastructure Area Director(s): Cullen Jennings Jon Peterson Real Time Applications Infrastructure Area Advisor: Cullen Jennings MONDAY, March 20, 2006 0800-1800 IETF Registration - 0800-0900 Continental Breakfast - 0900-1130 Morning Session I APP apparea Applications Area Open Meeting INT dna Detecting Network Attachment WG OPS netconf Network Configuration WG RAI enum Telephone Number Mapping WG RAI mmusic Multiparty Multimedia Session Control WG RTG mpls Multiprotocol Label Switching WG SEC krb-wg Kerberos WG AGENDA BASHING (5 min) ENUM Implementers Draft: (Final Version) 5 MIN Title : ENUM Implementation Issues and Experiences =20 Title : ENUM Requirement for EDNS0 Support ( ??? ) =20 Title : Guide and Template for IANA Registrations of Enumervices [ 15 M ] Author(s) : J. Livingood, B. Hoeneisen Filename : draft-ietf-enum-enumservices-guide-00.txt Pages : 12 Date : 2006-2-27 =20 This document provides a guide to and template for the creation of new IANA registration of ENUM services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-00= .txt Title : IANA Registration for an Enumservice and "tel" [ 20 Min = ] Parameter for Calling Name Delivery(CNAM) Information Author(s) : R. Shockey, J. Livingood Filename : draft-shockey-enum-cnam-00.txt Pages : 10 Date : 2006-1-13 This document registers the Enumservice "cnam" and subtype "tel" using the URI scheme 'tel:', as per the IANA registration process defined in the ENUM specification, RFC 3761. In addition this document registers the parameter "cnam" in the IANA "tel" Parameter Registry defined in RFCXXX. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the 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-shockey-enum-cnam-00.txt Title : IANA Registration for IAX Enumservice [ 15 = M ] Author(s) : E. Guy Filename : draft-ietf-enum-iax-00.txt Pages : 13 Date : 2006-2-22 =20 This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' as per the IANA registration process defined in the ENUM specification RFC3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-iax-00.txt Title : Telephone Number Mapping and Domain Keys as a = Distributed Identity Infrastructure [ 15 M ] Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-domainkeys-00.txt Pages : 10 Date : 2006-2-23 =20 This document creates a decentralized indentity infrastructure by combining technology from E.164 Number Mapping (ENUM) and DomainKeys Identified Mail (DKIM). This infrastructure uses E.164 numbers as identities, ENUM DNS for key distribution, and leverages the trust relations from ENUM validation to actual messages signed by the number holder. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-domainkeys-00.tx= t Title : IANA Registration for Enumservice foaf [ 15 Min ] Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-00.txt Pages : 9 Date : 2006-2-15 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-00.txt Title : A Telephone Number Mapping (ENUM) Service Registration = for Instant Messaging (IM) Services = [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-im-service-00.txt Pages : 5 Date : 2006-2-22 =20 This document registers a Telephone Number Mapping (ENUM) service for Instant Messaging (IM). Specifically, this document focuses on provisioning im: URIs in ENUM. Title : A Telephone Number Mapping (ENUM) Service Registration = for Internet Calendaring Services = [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-calendar-service-00.txt Pages : 5 Date : 2006-2-23 =20 This document registers a Telephone Number Mapping (ENUM) service for Internet Calendaring Services. Specifically, this document focuses on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mahy-enum-calendar-service-00.t= xt Title : Infrastrucure ENUM Requirements Author(s) : S. Lind, P. Pfautz [ 20 M ] Filename : = draft-ietf-enum-infrastructure-enum-reqs-00.txt Pages : 7 Date : 2006-3-6 =20 This document provides requirements for "infrastructure" or "carrier" ENUM, 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-r= eqs-00.txt General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 07 13:57:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGhNP-0000yp-Id; Tue, 07 Mar 2006 13:57:43 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGhNO-0000yY-FU for enum@ietf.org; Tue, 07 Mar 2006 13:57:42 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGhKb-0006cB-Qm for enum@ietf.org; Tue, 07 Mar 2006 13:54:49 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FGhKZ-00082e-St for enum@ietf.org; Tue, 07 Mar 2006 13:54:49 -0500 Received: from [10.31.13.237] (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k27ItLO0024501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Mar 2006 10:55:22 -0800 Message-ID: <440DD6F0.30301@shockey.us> Date: Tue, 07 Mar 2006 13:54:40 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Stastny Richard Subject: Re: [Enum] Almost complete Agenda for IETF 65 Dallas References: <32755D354E6B65498C3BD9FD496C7D462C48B7@oefeg-s04.oefeg.loc> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C48B7@oefeg-s04.oefeg.loc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: richard@shockey.us X-Spam-Score: -0.3 (/) X-Scan-Signature: 918f4bd8440e8de4700bcf6d658bc801 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 Stastny Richard wrote: > Dear Co-chair, > > I requested some time ago some time on the agenda for the up issue of > our I-D : > > "Combined User and Carrier ENUM in the e164.arpa tree" - > draft-haberler-carrier-enum-02.txt . > > Abstract: > > ENUM as defined now in RFC3761 is not well suited for the purpose of > interconnection by carriers, as can be seen by the use of various > private tree arrangements based on ENUM mechanisms. A combined > end-user and carrier ENUM tree solution would leverage the ENUM > infrastructure in e164.arpa, increase resolution rates, and decrease > the cost per registered telephone number. This document describes a > minimally invasive scheme to provide both end-user and carrier data in ENUM. > > until it comes out of the queue, the I-D is available at: > > http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.txt > http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.html I havent seen the 02 draft come across the announce wire but thats not a problem .. > > > and the > >> General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] > > Adding the proposed agenda times together, only 10 minutes are left for > these two items. I am also getting the slight impression that our esteemed co-chair > is taking this issue not really seriois. Its still a tentative schedule. Don't we have any sense of humor left :-) > > Since I am preparing also a presentation (to be submitted soon), > I request at least 10-20 Min you are already there after the requirements > > Eventually 5 minuntes could be spared from agenda item CNAM > and another 5 from IAX Well we'll probably shaving a lot of time off the Registration document discussion those time allocations were just preliminary . We hope to move most of those through pretty quickly but we do need to clear up what is the appropriate URI for CNAM etc. OK? > > best regards > Richard > > > > ________________________________ > > Von: Richard Shockey [mailto:richard@shockey.us] > Gesendet: Di 07.03.2006 16:28 > An: 'enum@ietf.org' > Betreff: [Enum] Almost complete Agenda for IETF 65 Dallas > > > > IETF 65 Dallas Telephone Number Mapping (ENUM) WG Agenda Preliminary > > Chair(s): > Patrik Faltstrom > Richard Shockey > > > WG Secretary: > Alex Mayrhofer > > > Real Time Applications Infrastructure Area Director(s): > Cullen Jennings > Jon Peterson > > Real Time Applications Infrastructure Area Advisor: > Cullen Jennings > > MONDAY, March 20, 2006 > 0800-1800 IETF Registration - > 0800-0900 Continental Breakfast - > 0900-1130 Morning Session I > APP apparea Applications Area Open Meeting > INT dna Detecting Network Attachment WG > OPS netconf Network Configuration WG > RAI enum Telephone Number Mapping WG > RAI mmusic Multiparty Multimedia Session Control WG > RTG mpls Multiprotocol Label Switching WG > SEC krb-wg Kerberos WG > > > AGENDA BASHING (5 min) > > > ENUM Implementers Draft: (Final Version) 5 MIN > > > Title : ENUM Implementation Issues and Experiences > > > Title : ENUM Requirement for EDNS0 Support ( ??? ) > > > > Title : Guide and Template for IANA Registrations of > Enumervices [ 15 M ] > Author(s) : J. Livingood, B. Hoeneisen > Filename : draft-ietf-enum-enumservices-guide-00.txt > Pages : 12 > Date : 2006-2-27 > > This document provides a guide to and template for the creation of > new IANA registration of ENUM services. It is also to be used for > updates of existing IANA registrations. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-00.txt > > > > Title : IANA Registration for an Enumservice and "tel" [ 20 Min ] > Parameter for Calling Name Delivery(CNAM) Information > Author(s) : R. Shockey, J. Livingood > Filename : draft-shockey-enum-cnam-00.txt > Pages : 10 > Date : 2006-1-13 > > This document registers the Enumservice "cnam" and subtype "tel" > using the URI scheme 'tel:', as per the IANA registration process > defined in the ENUM specification, RFC 3761. > > In addition this document registers the parameter "cnam" in the IANA > "tel" Parameter Registry defined in RFCXXX. This data is used to > facilitate the transfer of Calling Name Delivery (CNAM) data for > calls that originate on the 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-shockey-enum-cnam-00.txt > > > Title : IANA Registration for IAX Enumservice [ 15 M ] > Author(s) : E. Guy > Filename : draft-ietf-enum-iax-00.txt > Pages : 13 > Date : 2006-2-22 > > This document registers the IAX2 (Inter-Asterisk eXchange Version 2) > Enumservice using the URI scheme 'iax2:' as per the IANA registration > process defined in the ENUM specification RFC3761. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-iax-00.txt > > > Title : Telephone Number Mapping and Domain Keys as a Distributed > Identity Infrastructure [ 15 M ] > > Author(s) : A. Mayrhofer > Filename : draft-mayrhofer-enum-domainkeys-00.txt > Pages : 10 > Date : 2006-2-23 > > This document creates a decentralized indentity infrastructure by > combining technology from E.164 Number Mapping (ENUM) and DomainKeys > Identified Mail (DKIM). This infrastructure uses E.164 numbers as > identities, ENUM DNS for key distribution, and leverages the trust > relations from ENUM validation to actual messages signed by the > number holder. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-domainkeys-00.txt > > > Title : IANA Registration for Enumservice foaf [ 15 Min ] > > Author(s) : K. Reichinger > Filename : draft-reichinger-enum-foaf-00.txt > Pages : 9 > Date : 2006-2-15 > > This memo registers the Enumservice "foaf" using the URI schemes > "http" and "https" according to the IANA Enumservice registration > process defined in RFC3671. The Enumservice "foaf" is to be used to > refer from an ENUM domain name to the location of a FOAF RDF file > using the corresponding E.164 telephone number. > > Clients may use data retrieved from a FOAF RDF file to provide caller > or callee with information available within the Friend-Of-A-Friend > (FOAF) Semantic Web application. For example, the caller might be > presented with personal information on the callee (e.g. name, gender > and various online attributes) as well as information on the callee's > social context (e.g. relations to friends or colleagues). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-00.txt > > > > Title : A Telephone Number Mapping (ENUM) Service Registration for > Instant Messaging (IM) Services > [ 15 M ] > Author(s) : R. Mahy > Filename : draft-mahy-enum-im-service-00.txt > Pages : 5 > Date : 2006-2-22 > > This document registers a Telephone Number Mapping (ENUM) service for > Instant Messaging (IM). Specifically, this document focuses on > provisioning im: URIs in ENUM. > > > > Title : A Telephone Number Mapping (ENUM) Service Registration for > Internet Calendaring Services [ 15 M ] > > Author(s) : R. Mahy > Filename : draft-mahy-enum-calendar-service-00.txt > Pages : 5 > Date : 2006-2-23 > > This document registers a Telephone Number Mapping (ENUM) service for > Internet Calendaring Services. Specifically, this document focuses > on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-mahy-enum-calendar-service-00.txt > > Title : Infrastrucure ENUM Requirements > Author(s) : S. Lind, P. Pfautz [ 20 M ] > Filename : draft-ietf-enum-infrastructure-enum-reqs-00.txt > Pages : 7 > Date : 2006-3-6 > > This document provides requirements for "infrastructure" or "carrier" > ENUM, 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. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt > > > General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] > > > -- > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Director - Member of Technical Staff > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 > Fax: +1 815.333.1237 > or > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > > > > -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 07 14:15:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGheO-0007aL-23; Tue, 07 Mar 2006 14:15:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGheM-0007Yp-Md for enum@ietf.org; Tue, 07 Mar 2006 14:15:14 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FGheL-0007j2-KI for enum@ietf.org; Tue, 07 Mar 2006 14:15:14 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Enum] Almost complete Agenda for IETF 65 Dallas Date: Tue, 7 Mar 2006 20:14:31 +0100 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C48B8@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Almost complete Agenda for IETF 65 Dallas Thread-Index: AcZCGS0wgeRFO+RnQpeKZR4zSgJteAAAi/nj From: "Stastny Richard" To: "Richard Shockey" X-Spam-Score: 0.5 (/) X-Scan-Signature: 96e0f8497f38c15fbfc8f6f315bcdecb 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 >I havent seen the 02 draft come across the announce wire but thats not = a >problem .. but you got it direct ;-) >OK? =20 OK =20 Richard ________________________________ Von: Richard Shockey [mailto:richard@shockey.us] Gesendet: Di 07.03.2006 19:54 An: Stastny Richard Cc: enum@ietf.org Betreff: Re: [Enum] Almost complete Agenda for IETF 65 Dallas Stastny Richard wrote: > Dear Co-chair, > > I requested some time ago some time on the agenda for the up issue of > our I-D : >=20 > "Combined User and Carrier ENUM in the e164.arpa tree" - > draft-haberler-carrier-enum-02.txt . > > Abstract: > > ENUM as defined now in RFC3761 is not well suited for the purpose of > interconnection by carriers, as can be seen by the use of various > private tree arrangements based on ENUM mechanisms. A combined > end-user and carrier ENUM tree solution would leverage the ENUM > infrastructure in e164.arpa, increase resolution rates, and decrease > the cost per registered telephone number. This document describes a > minimally invasive scheme to provide both end-user and carrier data in = ENUM. >=20 > until it comes out of the queue, the I-D is available at: > > http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.txt > http://mah.priv.at/i-d/draft-haberler-carrier-enum-02.html I havent seen the 02 draft come across the announce wire but thats not a problem .. > >=20 > and the >=20 >> General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] > > Adding the proposed agenda times together, only 10 minutes are left = for > these two items. I am also getting the slight impression that our = esteemed co-chair > is taking this issue not really seriois. Its still a tentative schedule. Don't we have any sense of humor left = :-) >=20 > Since I am preparing also a presentation (to be submitted soon), > I request at least 10-20 Min you are already there after the requirements >=20 > Eventually 5 minuntes could be spared from agenda item CNAM > and another 5 from IAX Well we'll probably shaving a lot of time off the Registration document discussion those time allocations were just preliminary . We hope to move most of those through pretty quickly but we do need to clear up what is the appropriate URI for CNAM etc. OK? >=20 > best regards > Richard >=20 >=20 > > ________________________________ > > Von: Richard Shockey [mailto:richard@shockey.us] > Gesendet: Di 07.03.2006 16:28 > An: 'enum@ietf.org' > Betreff: [Enum] Almost complete Agenda for IETF 65 Dallas > > > > IETF 65 Dallas Telephone Number Mapping (ENUM) WG Agenda Preliminary > > Chair(s): > Patrik Faltstrom > Richard Shockey > > > WG Secretary: > Alex Mayrhofer > > > Real Time Applications Infrastructure Area Director(s): > Cullen Jennings > Jon Peterson > > Real Time Applications Infrastructure Area Advisor: > Cullen Jennings > > MONDAY, March 20, 2006 > 0800-1800 IETF Registration - > 0800-0900 Continental Breakfast - > 0900-1130 Morning Session I > APP apparea Applications Area Open Meeting > INT dna Detecting Network Attachment WG > OPS netconf Network Configuration WG > RAI enum Telephone Number Mapping WG > RAI mmusic Multiparty Multimedia Session Control WG > RTG mpls Multiprotocol Label Switching WG > SEC krb-wg Kerberos WG > > > AGENDA BASHING (5 min) > > > ENUM Implementers Draft: (Final Version) 5 MIN > > > Title : ENUM Implementation Issues and Experiences > =20 > > Title : ENUM Requirement for EDNS0 Support ( ??? ) > =20 > > > Title : Guide and Template for IANA Registrations of > Enumervices [ 15 M = ] > Author(s) : J. Livingood, B. Hoeneisen > Filename : draft-ietf-enum-enumservices-guide-00.txt > Pages : 12 > Date : 2006-2-27 > =20 > This document provides a guide to and template for the creation of > new IANA registration of ENUM services. It is also to be used for > updates of existing IANA registrations. > > > A URL for this Internet-Draft is: > = http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-00= .txt > > > > Title : IANA Registration for an Enumservice and "tel" [ 20 = Min ] > Parameter for Calling Name Delivery(CNAM) Information > Author(s) : R. Shockey, J. Livingood > Filename : draft-shockey-enum-cnam-00.txt > Pages : 10 > Date : 2006-1-13 > > This document registers the Enumservice "cnam" and subtype "tel" > using the URI scheme 'tel:', as per the IANA registration process > defined in the ENUM specification, RFC 3761. > > In addition this document registers the parameter "cnam" in the = IANA > "tel" Parameter Registry defined in RFCXXX. This data is used to > facilitate the transfer of Calling Name Delivery (CNAM) data for > calls that originate on the 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-shockey-enum-cnam-00.txt > > > Title : IANA Registration for IAX Enumservice [ = 15 M ] > Author(s) : E. Guy > Filename : draft-ietf-enum-iax-00.txt > Pages : 13 > Date : 2006-2-22 > =20 > This document registers the IAX2 (Inter-Asterisk eXchange Version 2) > Enumservice using the URI scheme 'iax2:' as per the IANA registration > process defined in the ENUM specification RFC3761. > > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-enum-iax-00.txt > > > Title : Telephone Number Mapping and Domain Keys as a = Distributed > Identity Infrastructure [ 15 M ] > > Author(s) : A. Mayrhofer > Filename : draft-mayrhofer-enum-domainkeys-00.txt > Pages : 10 > Date : 2006-2-23 > =20 > This document creates a decentralized indentity infrastructure by > combining technology from E.164 Number Mapping (ENUM) and = DomainKeys > Identified Mail (DKIM). This infrastructure uses E.164 numbers as > identities, ENUM DNS for key distribution, and leverages the trust > relations from ENUM validation to actual messages signed by the > number holder. > > > A URL for this Internet-Draft is: > = http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-domainkeys-00.tx= t > > > Title : IANA Registration for Enumservice foaf [ 15 Min ] > > Author(s) : K. Reichinger > Filename : draft-reichinger-enum-foaf-00.txt > Pages : 9 > Date : 2006-2-15 > > This memo registers the Enumservice "foaf" using the URI schemes > "http" and "https" according to the IANA Enumservice registration > process defined in RFC3671. The Enumservice "foaf" is to be used to > refer from an ENUM domain name to the location of a FOAF RDF file > using the corresponding E.164 telephone number. > > Clients may use data retrieved from a FOAF RDF file to provide caller > or callee with information available within the Friend-Of-A-Friend > (FOAF) Semantic Web application. For example, the caller might be > presented with personal information on the callee (e.g. name, gender > and various online attributes) as well as information on the callee's > social context (e.g. relations to friends or colleagues). > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-00.txt > > > > Title : A Telephone Number Mapping (ENUM) Service = Registration for > Instant Messaging (IM) Services > = [ 15 M ] > Author(s) : R. Mahy > Filename : draft-mahy-enum-im-service-00.txt > Pages : 5 > Date : 2006-2-22 > =20 > This document registers a Telephone Number Mapping (ENUM) service for > Instant Messaging (IM). Specifically, this document focuses on > provisioning im: URIs in ENUM. > > > > Title : A Telephone Number Mapping (ENUM) Service = Registration for > Internet Calendaring Services = [ 15 M ] > > Author(s) : R. Mahy > Filename : draft-mahy-enum-calendar-service-00.txt > Pages : 5 > Date : 2006-2-23 > =20 > This document registers a Telephone Number Mapping (ENUM) service for > Internet Calendaring Services. Specifically, this document focuses > on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. > > > A URL for this Internet-Draft is: > = http://www.ietf.org/internet-drafts/draft-mahy-enum-calendar-service-00.t= xt > > Title : Infrastrucure ENUM Requirements > Author(s) : S. Lind, P. Pfautz [ 20 M ] > Filename : = draft-ietf-enum-infrastructure-enum-reqs-00.txt > Pages : 7 > Date : 2006-3-6 > =20 > This document provides requirements for "infrastructure" or "carrier" > ENUM, 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. > > > A URL for this Internet-Draft is: > = http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-r= eqs-00.txt > > > General Discussion of Infrastructure ENUM Apex [ 2 years + minimum ] > > > -- > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Director - Member of Technical Staff > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 > Fax: +1 815.333.1237 > or > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > > > > -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Mar 08 14:40:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH4WT-0000fB-Bm; Wed, 08 Mar 2006 14:40:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FH4WR-0000cY-Qi for enum@ietf.org; Wed, 08 Mar 2006 14:40:35 -0500 Received: from osprey.verisign.com ([216.168.239.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FH4WQ-0005MJ-Hw for enum@ietf.org; Wed, 08 Mar 2006 14:40:35 -0500 Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [10.170.12.139]) by osprey.verisign.com (8.13.1/8.13.4) with ESMTP id k28JoIPP030315 for ; Wed, 8 Mar 2006 14:50:18 -0500 Received: from dul1trutkow-l1.verisign.com ([10.131.161.113]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Mar 2006 14:40:34 -0500 Message-Id: <7.0.1.0.2.20060308141717.02ac5250@verisign.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 08 Mar 2006 14:37:40 -0500 To: enum@ietf.org From: Tony Rutkowski In-Reply-To: <440DD6F0.30301@shockey.us> References: <32755D354E6B65498C3BD9FD496C7D462C48B7@oefeg-s04.oefeg.loc> <440DD6F0.30301@shockey.us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-OriginalArrivalTime: 08 Mar 2006 19:40:34.0311 (UTC) FILETIME=[2AB6D970:01C642E8] X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Enum] carrier-of-record 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 subject term seems to have crept into some of the ENUM related documents. It is not clear, however, that the term is one that is actually defined in a legal sense, and it is imbued with significant collateral baggage. The term seems unneeded in the context of ENUM specifications. In the IETF "simple is better" vein, perhaps just "responsible provider" might suffice. It would also comport with the recent regulatory actions such as last year's FCC SBC IS Order. --tony _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Mar 08 21:43:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHB7O-0001ra-E6; Wed, 08 Mar 2006 21:43:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHB7N-0001rQ-Ky for enum@ietf.org; Wed, 08 Mar 2006 21:43:09 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHB7L-00079v-6E for enum@ietf.org; Wed, 08 Mar 2006 21:43:09 -0500 Received: from [68.165.240.35] (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k292hf39002452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Mar 2006 18:43:42 -0800 Message-ID: <440F9636.3050902@shockey.us> Date: Wed, 08 Mar 2006 21:43:02 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: multipart/mixed; boundary="------------040307050701090302060204" X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8 Subject: [Enum] [Fwd: I-D ACTION:draft-haberler-carrier-enum-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 This is a multi-part message in MIME format. --------------040307050701090302060204 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit -------- Original Message -------- Subject: I-D ACTION:draft-haberler-carrier-enum-02.txt Date: Wed, 08 Mar 2006 18:50:01 -0500 From: Internet-Drafts@ietf.org Reply-To: internet-drafts@ietf.org To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Combined User and Carrier ENUM in the e164.arpa tree Author(s) : M. Haberler, R. Stastny Filename : draft-haberler-carrier-enum-02.txt Pages : 18 Date : 2006-3-8 ENUM as defined in RFC3761 [1] is not well suited for the purpose of interconnection by carriers, as can be seen by the use of various private tree arrangements based on ENUM mechanisms. A combined end- user and carrier ENUM tree solution would leverage the ENUM infrastructure in e164.arpa, increase resolution rates, and decrease the cost per registered telephone number. This document describes a minimally invasive scheme to provide both end-user and carrier data in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-haberler-carrier-enum-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-haberler-carrier-enum-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-haberler-carrier-enum-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. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< --------------040307050701090302060204 Content-Type: Message/External-body; name="draft-haberler-carrier-enum-02.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="draft-haberler-carrier-enum-02.txt" Content-Type: text/plain Content-ID: <2006-3-8151234.I-D@ietf.org> --------------040307050701090302060204 Content-Type: text/plain; name*0="file:///C|/DOCUME%7E1/RICHAR%7E1/LOCALS%7E1/TEMP/nsmail.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename*0="file:///C|/DOCUME%7E1/RICHAR%7E1/LOCALS%7E1/TEMP/nsmail.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --------------040307050701090302060204 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 --------------040307050701090302060204-- From enum-bounces@ietf.org Thu Mar 09 06:20:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHJBj-00053d-JG; Thu, 09 Mar 2006 06:20:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHJBh-00053Y-Og for enum@ietf.org; Thu, 09 Mar 2006 06:20:09 -0500 Received: from central.switch.ch ([130.59.11.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHJBh-0006LG-Dp for enum@ietf.org; Thu, 09 Mar 2006 06:20:09 -0500 Received: from machb.switch.ch ([130.59.6.129]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1FHJBf-0000lL-00 for enum@ietf.org; Thu, 09 Mar 2006 12:20:07 +0100 Date: Thu, 9 Mar 2006 12:20:03 +0100 (CET) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: enum@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Subject: [Enum] Ready for WG Last Call: I-D ACTION:draft-ietf-enum-validation-epp-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 draft-ietf-enum-validation-epp-03.txt has been reviewed by the WG secretary and found to be o.k. I'd say this document is ready for ENUM WG Last Call. cheers, Bernie ---------- Forwarded message ---------- Date: Wed, 15 Feb 2006 18:50:01 -0500 From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-validation-epp-03.txt 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 Information Mapping for the Extensible Provisioning Protocol Author(s) : B. Hoeneisen Filename : draft-ietf-enum-validation-epp-03.txt Pages : 26 Date : 2006-2-15 This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range), which the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM domain names. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-epp-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-epp-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-epp-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. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Mar 09 15:50:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHS5S-0001dD-Ol; Thu, 09 Mar 2006 15:50:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHS5C-0000v1-MW; Thu, 09 Mar 2006 15:50:02 -0500 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHS5C-0007Dc-1l; Thu, 09 Mar 2006 15:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k29Ko19W015526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2006 20:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FHS5B-0008W0-Op; Thu, 09 Mar 2006 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 09 Mar 2006 15:50:01 -0500 X-Spam-Score: 0.3 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-experiences-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 : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-04.txt Pages : 37 Date : 2006-3-9 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-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-experiences-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-experiences-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: <2006-3-9105114.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-experiences-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-experiences-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-9105114.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 Thu Mar 09 17:21:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHTVH-0007dh-7V; Thu, 09 Mar 2006 17:21:03 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHTVF-0007cO-HG for enum@ietf.org; Thu, 09 Mar 2006 17:21:01 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHSrl-0006IX-DO for enum@ietf.org; Thu, 09 Mar 2006 16:40:13 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FHSil-0000Ik-Jt for enum@ietf.org; Thu, 09 Mar 2006 16:30:57 -0500 Received: from [10.31.13.105] (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k29LUOSR031763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 9 Mar 2006 13:30:40 -0800 Message-ID: <44109E3D.3070900@shockey.us> Date: Thu, 09 Mar 2006 16:29:33 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SongbirdInformation: support@songbird.com for more information X-Songbird: Found to be clean X-Songbird-From: richard@shockey.us X-Spam-Score: 1.0 (+) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: [Enum] FINAL AGENDA ENUM WG IETF 65 Dallas 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 http://www3.ietf.org/proceedings/06mar/agenda/enum.txt -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Mar 10 09:32:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHif9-0004OU-8Z; Fri, 10 Mar 2006 09:32:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHif7-0004Nq-PD for enum@ietf.org; Fri, 10 Mar 2006 09:32:13 -0500 Received: from norman.insensate.co.uk ([213.152.49.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHif5-0000CL-S6 for enum@ietf.org; Fri, 10 Mar 2006 09:32:13 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by norman.insensate.co.uk (Postfix) with ESMTP id 5D2FB7F6EA; Fri, 10 Mar 2006 14:32:05 +0000 (GMT) In-Reply-To: <440F9636.3050902@shockey.us> References: <440F9636.3050902@shockey.us> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <463B0DB5-5935-4F4F-B334-CD532ED2CE27@insensate.co.uk> Content-Transfer-Encoding: 7bit From: lconroy Subject: Re: [Enum] [Fwd: I-D ACTION:draft-haberler-carrier-enum-02.txt] Date: Fri, 10 Mar 2006 14:32:03 +0000 To: Richard Stastny , Michael Haberler X-Mailer: Apple Mail (2.746.2) X-Spam-Score: 0.5 (/) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a Cc: IETF ENUM WG , Richard Shockey 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 Richards, Michael, folks, I like this document. I do, however, think that there's a typo in section 7 (specifically in example 2). At present, example 2 shows: ------------- $ORIGIN 7.e164.arpa. @ IN NS ns1.enum.ru. @ IN NS ns2.enum.ru. ; Branch location record at CC level @ IN BLR 0 "carrier" "e164.arpa" carrier IN NS ns1-ce.enum.ru. carrier IN NS ns2-ce.enum.ru. ------------- I think that these last two lines are wrong. Shouldn't these be replaced by...: ------------- $ORIGIN carrier.e164.arpa. 7 IN NS ns1-ce.enum.ru. 7 IN NS ns2-ce.enum.ru. ------------- This highlights the main complication you mention in section 4 (in the discussion of your option 1) - it requires IAB, RIPE, and no doubt ITU to be involved. Perhaps tag on a note to this example?: ------------- Note that the NS records for the delegated name servers ns1- ce.enum.ru. and ns2-ce.enum.ru. are within the "parent" carrier zone maintained by RIPE, and so will require approval from IAB and ITU for these records to be inserted. ------------- Does this make sense, and/or am I misunderstanding the scheme? all the best, Lawrence On 9 Mar 2006, at 02:43, Richard Shockey wrote: > -------- Original Message -------- > Subject: I-D ACTION:draft-haberler-carrier-enum-02.txt > Date: Wed, 08 Mar 2006 18:50:01 -0500 > From: Internet-Drafts@ietf.org > Reply-To: internet-drafts@ietf.org > To: i-d-announce@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Combined User and Carrier ENUM in the e164.arpa tree > Author(s) : M. Haberler, R. Stastny > Filename : draft-haberler-carrier-enum-02.txt > Pages : 18 > Date : 2006-3-8 > > ENUM as defined in RFC3761 [1] is not well suited for the purpose of > interconnection by carriers, as can be seen by the use of various > private tree arrangements based on ENUM mechanisms. A combined > end- > user and carrier ENUM tree solution would leverage the ENUM > infrastructure in e164.arpa, increase resolution rates, and > decrease > the cost per registered telephone number. This document > describes a > minimally invasive scheme to provide both end-user and carrier data > in ENUM. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-haberler-carrier-enum-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-haberler-carrier-enum-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-haberler-carrier-enum-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. > > > -- > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Director - Member of Technical Staff > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 > Fax: +1 815.333.1237 > or > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > Content-Type: text/plain > Content-ID: <2006-3-8151234.I-D@ietf.org> > > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce > > _______________________________________________ > 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 Mar 10 11:06:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHk8A-0001Z2-9I; Fri, 10 Mar 2006 11:06:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHk89-0001Xy-Jf for enum@ietf.org; Fri, 10 Mar 2006 11:06:17 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FHk87-0003Db-Ur for enum@ietf.org; Fri, 10 Mar 2006 11:06:17 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Enum] [Fwd: I-D ACTION:draft-haberler-carrier-enum-02.txt] Date: Fri, 10 Mar 2006 17:10:13 +0100 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C48CA@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] [Fwd: I-D ACTION:draft-haberler-carrier-enum-02.txt] Thread-Index: AcZET/qtpRyS0NmJSaKZNZCi/Kh7JAAC+s5L From: "Stastny Richard" To: "lconroy" , "Michael Haberler" X-Spam-Score: 0.5 (/) X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176 Cc: IETF ENUM WG , Richard Shockey 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 Lawrence, =20 thank you for reading the draft and also for finding this "typo", as you politely say ;-) =20 The error is especially diconcerting because it shows that option 1 in incorporated in option 2 =20 >Does this make sense, and/or am I misunderstanding the scheme? =20 Of course this makes sense, and we will correct example 2 in the next up-issue of the document =20 cheers Richard ________________________________ Von: lconroy [mailto:lconroy@insensate.co.uk] Gesendet: Fr 10.03.2006 15:32 An: Stastny Richard; Michael Haberler Cc: IETF ENUM WG; Richard Shockey Betreff: Re: [Enum] [Fwd: I-D ACTION:draft-haberler-carrier-enum-02.txt] Hi Richards, Michael, folks, I like this document. I do, however, think that there's a typo in section 7 (specifically in example 2). At present, example 2 shows: ------------- $ORIGIN 7.e164.arpa. @ IN NS ns1.enum.ru. @ IN NS ns2.enum.ru. ; Branch location record at CC level @ IN BLR 0 "carrier" "e164.arpa" carrier IN NS ns1-ce.enum.ru. carrier IN NS ns2-ce.enum.ru. ------------- I think that these last two lines are wrong. Shouldn't these be replaced by...: ------------- $ORIGIN carrier.e164.arpa. 7 IN NS ns1-ce.enum.ru. 7 IN NS ns2-ce.enum.ru. ------------- This highlights the main complication you mention in section 4 (in the discussion of your option 1) - it requires IAB, RIPE, and no doubt ITU to be involved. Perhaps tag on a note to this example?: ------------- Note that the NS records for the delegated name servers ns1- ce.enum.ru. and ns2-ce.enum.ru. are within the "parent" carrier zone=20 maintained by RIPE, and so will require approval from IAB and ITU for these=20 records to be inserted. ------------- Does this make sense, and/or am I misunderstanding the scheme? all the best, Lawrence On 9 Mar 2006, at 02:43, Richard Shockey wrote: > -------- Original Message -------- > Subject: I-D ACTION:draft-haberler-carrier-enum-02.txt > Date: Wed, 08 Mar 2006 18:50:01 -0500 > From: Internet-Drafts@ietf.org > Reply-To: internet-drafts@ietf.org > To: i-d-announce@ietf.org > > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. > > > Title : Combined User and Carrier ENUM in the = e164.arpa tree > Author(s) : M. Haberler, R. Stastny > Filename : draft-haberler-carrier-enum-02.txt > Pages : 18 > Date : 2006-3-8 > =20 > ENUM as defined in RFC3761 [1] is not well suited for the purpose of > interconnection by carriers, as can be seen by the use of various > private tree arrangements based on ENUM mechanisms. A combined=20 > end- > user and carrier ENUM tree solution would leverage the ENUM > infrastructure in e164.arpa, increase resolution rates, and=20 > decrease > the cost per registered telephone number. This document=20 > describes a > minimally invasive scheme to provide both end-user and carrier data > in ENUM. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-haberler-carrier-enum-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=20 > 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=20 > username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-haberler-carrier-enum-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-haberler-carrier-enum-02.txt". > =20 > 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. > =20 > =20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > > > -- > > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Director - Member of Technical Staff > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 > Fax: +1 815.333.1237 > or > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > Content-Type: text/plain > Content-ID: <2006-3-8151234.I-D@ietf.org> > > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce > > _______________________________________________ > 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 Mar 15 06:27:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJU9s-0000qO-J9; Wed, 15 Mar 2006 06:27:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJU9r-0000qJ-E5 for enum@ietf.org; Wed, 15 Mar 2006 06:27:15 -0500 Received: from smartmx-09.inode.at ([213.229.60.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJU9n-0005yY-P7 for enum@ietf.org; Wed, 15 Mar 2006 06:27:15 -0500 Received: from [81.223.16.194] (port=1689 helo=mah9.inode.at) by smartmx-09.inode.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FJU9m-0001LM-D0 for enum@ietf.org; Wed, 15 Mar 2006 12:27:10 +0100 Message-Id: <7.0.1.0.2.20060315122604.0a522b40@inode.at> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 15 Mar 2006 12:27:07 +0100 To: enum@ietf.org From: Michael Haberler Subject: [Enum] combined user/infrastucture ENUM proposal - proof of concept implementation - updated to draft-haberler-carrier-enum-02 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; x-avg-checked=avg-ok-124F7387 X-Spam-Score: 1.2 (+) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 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've updated the the proof-of-concept C implementation of our draft http://www.enum.at/ietf/draft-haberler-carrier-enum-00.html . Files for perusal: http://mah.priv.at/enum/dist/ The tarball is at: http://mah.priv.at/enum/c-enum-dist.tar.gz -Michael --- dist/README : Combined Carrier and User ENUM under e164.arpa ---------------------------------------------- This is my example implementation of our I-D as outlined in http://www.enum.at/ietf/draft-haberler-carrier-enum-00.html . Beyond the described table-driven method this program experimentally uses the DNS to announce the carrier subdomain location in the relevant zone itself - for now by an integer value carried in a TXT RR named 'subdomainlocation' by default. I've set up a e164.mah.priv.at 'miniworld' under e164.mah.priv.at, which is publically accessible. If you want to play with your own DNS setup: the zone files and named.conf fragment used for this are in the 'bind' subdirectory. The zones under mah.priv.at are open also for zone transfer. To compile and run the demo (see shell script demo.sh), type make demo The expected output is in 'demo.out'. The demo script executes 4 scenarios, with sample user and carrier NAPTR records; the latter's location either determined through the subdomain location table or the DNS TXT RR as described above. [c.]3.4.e164.mah.priv.at ('c' for 'carrier') [c.]1.7.5.1.e164.mah.priv.at [c.]0.1.8.7.8.e164.mah.priv.at 7.[c.]e164.mah.priv.at Installation notes ------------------ Compiles ok under Linux and cygwin32. Cygwin binary for Windows supplied, I assume you need to have cygwin32 environment set up for the DLL's to be present. I've neither tried to be most efficient, nor are error scenarios thoroughly checked - this is a proof-of-concept. An example subdomain location table is compiled in, in real use there would be some other mechanism to import the table. The only source file specific to the I-D is c-enum.c, the rest is support routines mostly for DNS. I've liberally reused code for DNS resolution from the iptel.org SIP Express Router distribution - thanks, guys. Suggestions/feedback welcome. Michael Haberler mah@inode.at 12-7-2005 _______________________________________________ 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 Mar 15 06:30:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJUDB-0002V2-Hz; Wed, 15 Mar 2006 06:30:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJUDA-0002Ux-Sw for enum@ietf.org; Wed, 15 Mar 2006 06:30:40 -0500 Received: from smartmx-02.inode.at ([213.229.60.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJUDA-000632-E0 for enum@ietf.org; Wed, 15 Mar 2006 06:30:40 -0500 Received: from [81.223.16.194] (port=1696 helo=mah9.inode.at) by smartmx-02.inode.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FJUD9-0007ib-Hs for enum@ietf.org; Wed, 15 Mar 2006 12:30:40 +0100 Message-Id: <7.0.1.0.2.20060315122736.0a5211b8@inode.at> Message-Id: <7.0.1.0.2.20060315122604.0a522b40@inode.at> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 15 Mar 2006 12:30:36 +0100 To: enum@ietf.org From: Michael Haberler Subject: [Enum] combined user/infrastucture ENUM proposal - proof of concept implementation - updated to draft-haberler-carrier-enum-02 - CORRECTED Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.1 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 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 [sorry, hit the wrong button - please disregard my last message -mah] I've updated the the proof-of-concept C implementation of our draft to reflect -02 (see http://www.enum.at/ietf/draft-haberler-carrier-enum-02.html ). Files for perusal: http://mah.priv.at/enum/dash-02/ The tarball is at: http://mah.priv.at/enum/dash-02.tgz -Michael --- dash-02/README : Combined Carrier and User ENUM under e164.arpa ---------------------------------------------- updated 13-3-2006 This is my example implementation of our I-D as upgraded to the semantics outlined in http://www.enum.at/ietf/draft-haberler-carrier-enum-02.html . We propose to have a 'branch location record' at the country code level under e164.arpa which specifies the name of the label to be inserted, the position in the number, and now also the apex under which the carrier subtree is located. This permits us to specifiy an arbitrary location for the carrier tree, i.e. also completely outside e164.arpa. There is an example for +49 where the whole carrier subtree is referred to resolution through e164.org . Both label insertion and apex are independent parameters now - a zero length label implies no branch insertion, and the apex parameter allows to point to an arbitrary location. Thus this is a mechanism to integrate arbitrary ENUM trees into e164.arpa if one would want to do so, for instance to shortcut ITU politics at a national or NPA level. We expect to introduce, in the next revision of the draft, a minor change which changes the BLR (branch location record) to have a label (currently it sits directly at .e164.arpa). This label we will call 'resolution context' and could be 'carrier', 'user', or in fact any arbitrary name. This way several different resolution contexts - and this independent trees - could be specified; even the standard user ENUM behaviour can be described by such a context in a backwards compatible way - by specifying a zero-length label (meaning no label insertion) and e164.arpa as apex. Thus resolvers would only need to implement the semantics as per draft-03 and still work with exisiting user ENUM trees without special-casing in the resolver code. Examples for this named resolution context is already in the code, the zone files, the DNS (see below) although we havent publised this yet. I've updated the e164.mah.priv.at 'miniworld' under e164.mah.priv.at, which is publically accessible. If you want to play with your own DNS setup: the zone files and named.conf fragment used for this are in the 'bind' subdirectory. The zones under mah.priv.at are open also for zone transfer. To compile and run the demo (see shell script demo.sh), type make demo The expected output is in 'demo.out'. The demo script executes 5 scenarios, with sample user and carrier NAPTR records; the latter's location either determined through the subdomain location table or the DNS TXT RR as described above. [c.]3.4.e164.mah.priv.at ('c' for 'carrier') [c.]1.7.5.1.e164.mah.priv.at [c.]0.1.8.7.8.e164.mah.priv.at 7.[c.]e164.mah.priv.at 9.4.e164.mah.priv.at or 9.4.e164.org for the carrier tree. Installation notes ------------------ Compiles ok under Linux. I've neither tried to be most efficient, nor are error scenarios thoroughly checked - this is a proof-of-concept. The only source file specific to the I-D is c-enum.c, the rest is support routines mostly for DNS. I've liberally reused code for DNS resolution from the iptel.org SIP Express Router distribution - thanks, guys. Suggestions/feedback welcome. Michael Haberler mah@inode.at 13-3-2006 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sat Mar 18 13:52:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKgWl-0005FL-GO; Sat, 18 Mar 2006 13:51:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FKgWk-0005FG-H0 for enum@ietf.org; Sat, 18 Mar 2006 13:51:50 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FKgWj-0003BD-4h for enum@ietf.org; Sat, 18 Mar 2006 13:51:50 -0500 Received: from [68.165.240.35] (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k2IIqHbS007940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 18 Mar 2006 10:52:19 -0800 Message-ID: <441C56BD.4070306@shockey.us> Date: Sat, 18 Mar 2006 13:51:41 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Enum] Submit presentations materials to either myself or Alex.. 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 ASAP .. we would like to have these available on line before Monday. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:37:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLR8S-0007XG-Ts; Mon, 20 Mar 2006 15:37:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLR8R-0007XB-6K for enum@ietf.org; Mon, 20 Mar 2006 15:37:51 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLR8P-000280-IZ for enum@ietf.org; Mon, 20 Mar 2006 15:37:50 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKblQ4037074; Mon, 20 Mar 2006 21:37:47 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKblEt037073; Mon, 20 Mar 2006 21:37:47 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:37:47 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: paf@frobbit.se Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: [Enum] [ticket.frobbit.se #821] This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Mon Mar 20 21:37:46 2006: Request 821 was acted upon. Transaction: Ticket created by paf@frobbit.se Queue: 3761bis Subject: This is a test of the ticket system for RFC 3761 bis Owner: Nobody Requestors: paf@frobbit.se Status: new Ticket Please ignore this.... paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:42:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRD5-0003WN-IN; Mon, 20 Mar 2006 15:42:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRD4-0003WI-4e for enum@ietf.org; Mon, 20 Mar 2006 15:42:38 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRD2-0002E0-Sy for enum@ietf.org; Mon, 20 Mar 2006 15:42:38 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 20 Mar 2006 12:42:36 -0800 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k2KKga7T025725; Mon, 20 Mar 2006 12:42:36 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2KKhdLr013167; Mon, 20 Mar 2006 12:43:40 -0800 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] [ticket.frobbit.se #821] This is a test of the ticket system for RFC 3761 bis Date: Mon, 20 Mar 2006 14:42:32 -0600 To: 3761bis@frobbit.se X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=241; t=1142887420; x=1143319620; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Re=3A=20[Enum]=20[ticket.frobbit.se=20#821]=20This=20is=20a=20test=20of= 20the=20ticket=20system=20for=20RFC=203761=20bis=20 |To:3761bis@frobbit.se; X=v=3Dmtcc.com=3B=20h=3DC28Qf+aWCz+t8yzymmT5hf05ZiY=3D; b=K7/EA+9XLyl0iV1nffklUO7vBerw2rjOtDCM55KEOK9Jlg7aMryMj32X9PI7aJEHfRbBR7fF UaP1orbB0BWSIlfZwUaWbXhJ9HLWGROZX20ADHzv58XuxyGRlOistJjZrvZ1oRkPDPbkbt9aTNi WYMCRGgJqDptxH+gYafwjWQs=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea 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 Here I am updating the ticket, via a reply-all, that will send both to the mailing list and the ticket system. Probably a bad idea... Should give two copies to the mailing list. If only one is produced, we are lucky. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:42:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDI-0003jO-UR; Mon, 20 Mar 2006 15:42:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDI-0003jE-9u for enum@ietf.org; Mon, 20 Mar 2006 15:42:52 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRDH-0002EZ-Tm for enum@ietf.org; Mon, 20 Mar 2006 15:42:52 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKgmoI037098; Mon, 20 Mar 2006 21:42:48 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKgmGH037097; Mon, 20 Mar 2006 21:42:48 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:42:48 +0100 (CET) Subject: Re: [Enum] [ticket.frobbit.se #821] This is a test of the ticket system for RFC 3761 bis From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: paf@cisco.com To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Here I am updating the ticket, via a reply-all, that will send both to the mailing list and the ticket system. Probably a bad idea... Should give two copies to the mailing list. If only one is produced, we are lucky. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:43:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDo-00045A-4p; Mon, 20 Mar 2006 15:43:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRDm-00043Y-8H for enum@ietf.org; Mon, 20 Mar 2006 15:43:22 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRDk-0002Ft-PS for enum@ietf.org; Mon, 20 Mar 2006 15:43:22 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKhJeH037106; Mon, 20 Mar 2006 21:43:19 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKhJaI037105; Mon, 20 Mar 2006 21:43:19 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:43:19 +0100 (CET) From: "MAILER-DAEMON@ktf.com via RT" <3761bis@frobbit.se> In-Reply-To: <200603202042.FAA19987@ktf.com> References: <200603202042.FAA19987@ktf.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #822 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: MAILER-DAEMON@ktf.com Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1142887399-32765-0" X-Spam-Score: 2.6 (++) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Subject: [Enum] [ticket.frobbit.se #822] Returned Mail: Message Could Not Be Delivered X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1142887399-32765-0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Mon Mar 20 21:43:18 2006: Request 822 was acted upon. Transaction: Ticket created by MAILER-DAEMON@ktf.com Queue: 3761bis Subject: Returned Mail: Message Could Not Be Delivered Owner: Nobody Requestors: MAILER-DAEMON@ktf.com Status: new Ticket To:mo/////////RFC-822/mo@contact1 550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table. ------------=_1142887399-32765-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 822/7034/4681 Original-Envelope-ID: rt-3.4.4-32760-1142887367-212.821-5-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:42:28 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887399-32765-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 822/7034/4683 


Here I am updating the ticket, via a reply-all, that will send both  
to the mailing list and the ticket system. Probably a bad idea...  
Should give two copies to the mailing list. If only one is produced,  
we are lucky.

    Patrik


_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887399-32765-0 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 ------------=_1142887399-32765-0-- From enum-bounces@ietf.org Mon Mar 20 15:43:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLREL-0004ie-Vz; Mon, 20 Mar 2006 15:43:57 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLREL-0004iZ-4k for enum@ietf.org; Mon, 20 Mar 2006 15:43:57 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLREJ-0002Hy-Kv for enum@ietf.org; Mon, 20 Mar 2006 15:43:57 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKhsRl037118; Mon, 20 Mar 2006 21:43:54 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKhs7t037117; Mon, 20 Mar 2006 21:43:54 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:43:54 +0100 (CET) From: "MAILER-DAEMON@ktf.com via RT" <3761bis@frobbit.se> In-Reply-To: <200603202043.FAA20332@ktf.com> References: <200603202043.FAA20332@ktf.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #823 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: MAILER-DAEMON@ktf.com Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1142887434-32763-0" X-Spam-Score: 3.4 (+++) X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7 Subject: [Enum] [ticket.frobbit.se #823] Returned Mail: Message Could Not Be Delivered X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1142887434-32763-0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Mon Mar 20 21:43:53 2006: Request 823 was acted upon. Transaction: Ticket created by MAILER-DAEMON@ktf.com Queue: 3761bis Subject: Returned Mail: Message Could Not Be Delivered Owner: Nobody Requestors: MAILER-DAEMON@ktf.com Status: new Ticket To:mo/////////RFC-822/mo@contact1 550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table. ------------=_1142887434-32763-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 823/7042/4688 Original-Envelope-ID: rt-3.4.4-32765-1142887399-523.822-3-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:43:06 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887434-32763-0 Content-Type: text/html; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 823/7042/4691 


Mon Mar 20 21:43:18 2006: Request 822 was acted upon.
Transaction: Ticket created by MAILER-DAEMON@ktf.com
       Queue: 3761bis
     Subject: Returned Mail: Message Could Not Be Delivered
       Owner: Nobody
  Requestors: MAILER-DAEMON@ktf.com
      Status: new


To:mo/////////RFC-822/mo@contact1
550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table.
------------=_1142887434-32763-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 823/7042/4692 Original-Envelope-ID: rt-3.4.4-32760-1142887367-212.821-5-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:42:28 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887434-32763-0 Content-Type: text/html; charset="ascii"; name="[Enum] [ticket.frobbit.se #822] Returned Mail: Message Could Not Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #822] Returned Mail: Message Could Not Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 823/7042/4693 


Here I am updating the ticket, via a reply-all, that will send both  
to the mailing list and the ticket system. Probably a bad idea...  
Should give two copies to the mailing list. If only one is produced,  
we are lucky.

    Patrik


_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887434-32763-0 Content-Type: text/html; charset="us-ascii"; name="[Enum] [ticket.frobbit.se #822] Retur ned Mail: Message Could Not Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #822] Retur ned Mail: Message Could Not Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 823/7042/4694 

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887434-32763-0 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 ------------=_1142887434-32763-0-- From enum-bounces@ietf.org Mon Mar 20 15:44:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLREj-0005ER-Mh; Mon, 20 Mar 2006 15:44:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLREh-00058n-Hb for enum@ietf.org; Mon, 20 Mar 2006 15:44:19 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLREg-0002Is-Vp for enum@ietf.org; Mon, 20 Mar 2006 15:44:19 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKiHbV037143; Mon, 20 Mar 2006 21:44:17 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKiHhJ037142; Mon, 20 Mar 2006 21:44:17 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:44:17 +0100 (CET) From: "MAILER-DAEMON@ktf.com via RT" <3761bis@frobbit.se> In-Reply-To: <200603202043.FAA20518@ktf.com> References: <200603202043.FAA20518@ktf.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #824 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: MAILER-DAEMON@ktf.com Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1142887457-32759-0" X-Spam-Score: 3.4 (+++) X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1 Subject: [Enum] [ticket.frobbit.se #824] Returned Mail: Message Could Not Be Delivered X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1142887457-32759-0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Mon Mar 20 21:44:16 2006: Request 824 was acted upon. Transaction: Ticket created by MAILER-DAEMON@ktf.com Queue: 3761bis Subject: Returned Mail: Message Could Not Be Delivered Owner: Nobody Requestors: MAILER-DAEMON@ktf.com Status: new Ticket To:mo/////////RFC-822/mo@contact1 550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table. ------------=_1142887457-32759-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4699 Original-Envelope-ID: rt-3.4.4-32763-1142887433-1524.823-3-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:43:29 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887457-32759-0 Content-Type: text/html; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4702 


Mon Mar 20 21:43:53 2006: Request 823 was acted upon.
Transaction: Ticket created by MAILER-DAEMON@ktf.com
       Queue: 3761bis
     Subject: Returned Mail: Message Could Not Be Delivered
       Owner: Nobody
  Requestors: MAILER-DAEMON@ktf.com
      Status: new


To:mo/////////RFC-822/mo@contact1
550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table.
------------=_1142887457-32759-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4703 Original-Envelope-ID: rt-3.4.4-32765-1142887399-523.822-3-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:43:06 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887457-32759-0 Content-Type: text/html; charset="US-ASCII"; name="[Enum] [ticket.frobbit.se #823] Returned Mail: Message Could Not Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #823] Returned Mail: Message Could Not Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4704 


Mon Mar 20 21:43:18 2006: Request 822 was acted upon.
Transaction: Ticket created by MAILER-DAEMON@ktf.com
       Queue: 3761bis
     Subject: Returned Mail: Message Could Not Be Delivered
       Owner: Nobody
  Requestors: MAILER-DAEMON@ktf.com
      Status: new


To:mo/////////RFC-822/mo@contact1
550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table.
------------=_1142887457-32759-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4705 Original-Envelope-ID: rt-3.4.4-32760-1142887367-212.821-5-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:42:28 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887457-32759-0 Content-Type: text/html; charset="ascii"; name="[Enum] [ticket.frobbit.se #822] Returned Mail: Message CouldNot Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #822] Returned Mail: Message CouldNot Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4706 


Here I am updating the ticket, via a reply-all, that will send both  
to the mailing list and the ticket system. Probably a bad idea...  
Should give two copies to the mailing list. If only one is produced,  
we are lucky.

    Patrik


_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887457-32759-0 Content-Type: text/html; charset="us-ascii"; name="[Enum] [ticket.frobbit.se #822] Retur ned Mail: Message CouldNot Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #822] Retur ned Mail: Message CouldNot Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4707 

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887457-32759-0 Content-Type: text/html; charset="us-ascii"; name="[Enum] [ticket.frobbit.se #823] Retur ned Mail: Message Could Not Be Delivered" Content-Disposition: inline; filename="[Enum] [ticket.frobbit.se #823] Retur ned Mail: Message Could Not Be Delivered" Content-Transfer-Encoding: 7bit RT-Attachment: 824/7050/4708 

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887457-32759-0 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 ------------=_1142887457-32759-0-- From enum-bounces@ietf.org Mon Mar 20 15:45:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFd-0005od-R5; Mon, 20 Mar 2006 15:45:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0005jq-Qn for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0002Ku-Ck for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKjB70037158; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKjBrY037157; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:45:11 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #821] Resolved: This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:45:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFd-0005n4-GQ; Mon, 20 Mar 2006 15:45:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0005jp-Qj for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0002Kr-Ck for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKjB7f037154; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKjBHn037153; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:45:11 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #821] This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Test is over. Thanks for your patience. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:45:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFd-0005od-R5; Mon, 20 Mar 2006 15:45:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0005jq-Qn for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0002Ku-Ck for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKjB70037158; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKjBrY037157; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:45:11 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #821] Resolved: This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:45:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFd-0005n4-GQ; Mon, 20 Mar 2006 15:45:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0005jp-Qj for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRFb-0002Kr-Ck for enum@ietf.org; Mon, 20 Mar 2006 15:45:15 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKjB7f037154; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKjBHn037153; Mon, 20 Mar 2006 21:45:11 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:45:11 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #821] This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Test is over. Thanks for your patience. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:45:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRG0-00063T-9a; Mon, 20 Mar 2006 15:45:40 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRFy-00063F-Q9 for enum@ietf.org; Mon, 20 Mar 2006 15:45:38 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRFy-0002Lq-9r for enum@ietf.org; Mon, 20 Mar 2006 15:45:38 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKjbsn037167; Mon, 20 Mar 2006 21:45:37 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKjbPa037166; Mon, 20 Mar 2006 21:45:37 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:45:37 +0100 (CET) From: "MAILER-DAEMON@ktf.com via RT" <3761bis@frobbit.se> In-Reply-To: <200603202044.FAA21727@ktf.com> References: <200603202044.FAA21727@ktf.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #825 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: MAILER-DAEMON@ktf.com Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1142887536-32758-0" X-Spam-Score: 3.3 (+++) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Subject: [Enum] [ticket.frobbit.se #825] Returned Mail: Message Could Not Be Delivered X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1142887536-32758-0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Mon Mar 20 21:45:36 2006: Request 825 was acted upon. Transaction: Ticket created by MAILER-DAEMON@ktf.com Queue: 3761bis Subject: Returned Mail: Message Could Not Be Delivered Owner: Nobody Requestors: MAILER-DAEMON@ktf.com Status: new Ticket To:mo/////////RFC-822/mo@contact1 550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table. ------------=_1142887536-32758-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 825/7063/4717 Original-Envelope-ID: rt-3.4.4-32760-1142887511-1756.821-9-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:44:49 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887536-32758-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 825/7063/4719 


According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887536-32758-0 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 ------------=_1142887536-32758-0-- From enum-bounces@ietf.org Mon Mar 20 15:46:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRGb-0006U8-MW; Mon, 20 Mar 2006 15:46:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRGZ-0006U3-MO for enum@ietf.org; Mon, 20 Mar 2006 15:46:15 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRGZ-0002MZ-8j for enum@ietf.org; Mon, 20 Mar 2006 15:46:15 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKkE3r037183; Mon, 20 Mar 2006 21:46:14 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKkEV2037182; Mon, 20 Mar 2006 21:46:14 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:46:14 +0100 (CET) Subject: SV: [Enum] [ticket.frobbit.se #821] This is a test of the ticketsystem for RFC 3761 bis From: "Joakim.Stralmark@pts.se via RT" <3761bis@frobbit.se> In-Reply-To: <1050E7CDAF4ED042BA2096CC187A79A7026C6E82@safir.pts.ad> References: <1050E7CDAF4ED042BA2096CC187A79A7026C6E82@safir.pts.ad> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: Joakim.Stralmark@pts.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by charles.frobbit.se id k2KKkE3r037183 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org F=C3=B6r mig som inte =C3=A4r s=C3=A5 bevandrad i IETF - skall man h=C3=A4= mt hem RFC3761bis n=C3=A5gonstans eller kommer den i nytt mail? H=C3=A4ls. Joakim -----Ursprungligt meddelande----- Fr=C3=A5n: Patrik F=C3=A4ltstr=C3=B6m via RT [mailto:3761bis@frobbit.se]=20 Skickat: den 20 mars 2006 21:43 Till: paf@frobbit.se Kopia: enum@ietf.org =C3=84mne: Re: [Enum] [ticket.frobbit.se #821] This is a test of the tick= etsystem for RFC 3761 bis=20 Here I am updating the ticket, via a reply-all, that will send both =20 to the mailing list and the ticket system. Probably a bad idea... =20 Should give two copies to the mailing list. If only one is produced, =20 we are lucky. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:46:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRGt-0006cn-09; Mon, 20 Mar 2006 15:46:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRGr-0006cI-MX for enum@ietf.org; Mon, 20 Mar 2006 15:46:33 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRGq-0002Mz-8O for enum@ietf.org; Mon, 20 Mar 2006 15:46:33 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKkV4Y037187 for ; Mon, 20 Mar 2006 21:46:31 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKkVBb037186; Mon, 20 Mar 2006 21:46:31 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:46:31 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #819 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Subject: [Enum] [ticket.frobbit.se #819] Resolved: This is a test - please ignore X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:47:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRHV-00080N-Hf; Mon, 20 Mar 2006 15:47:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRHV-00080I-3I for enum@ietf.org; Mon, 20 Mar 2006 15:47:13 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRHU-0002OR-Ll for enum@ietf.org; Mon, 20 Mar 2006 15:47:13 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKlBE5037191; Mon, 20 Mar 2006 21:47:11 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKlB4F037190; Mon, 20 Mar 2006 21:47:11 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:47:11 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #821 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: paf@frobbit.se MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #821] Resolved: This is a test of the ticket system for RFC 3761 bis X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 20 15:47:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRHu-0008Ds-1I; Mon, 20 Mar 2006 15:47:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRHt-0008Dk-83 for enum@ietf.org; Mon, 20 Mar 2006 15:47:37 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRHs-0002P6-Og for enum@ietf.org; Mon, 20 Mar 2006 15:47:37 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2KKlZK5037199; Mon, 20 Mar 2006 21:47:35 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2KKlZa8037198; Mon, 20 Mar 2006 21:47:35 +0100 (CET) (envelope-from www) Date: Mon, 20 Mar 2006 21:47:35 +0100 (CET) From: "MAILER-DAEMON@ktf.com via RT" <3761bis@frobbit.se> In-Reply-To: <200603202046.FAA23209@ktf.com> References: <200603202046.FAA23209@ktf.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #826 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: MAILER-DAEMON@ktf.com Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1142887655-32760-0" X-Spam-Score: 3.3 (+++) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Subject: [Enum] [ticket.frobbit.se #826] Returned Mail: Message Could Not Be Delivered X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1142887655-32760-0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Mon Mar 20 21:47:34 2006: Request 826 was acted upon. Transaction: Ticket created by MAILER-DAEMON@ktf.com Queue: 3761bis Subject: Returned Mail: Message Could Not Be Delivered Owner: Nobody Requestors: MAILER-DAEMON@ktf.com Status: new Ticket To:mo/////////RFC-822/mo@contact1 550 mo/////////RFC-822/mo@contact1 .... OM.UX 1015 Can't find mailnode in the routing table. ------------=_1142887655-32760-0 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 826/7090/4734 Original-Envelope-ID: rt-3.4.4-32763-1142887631-520.821-9-0@example.com Reporting-MTA: smtp; contact1 DSN-Gateway: dns; contact1 Arrival-Date: Tue, 21 Mar 2006 05:46:47 +0900 Final-Recipient: rfc822;mo/////////RFC-822/mo@contact1 Action: failed Status: 5.4.4 X-OpenMail-Reason-Code: 101 ------------=_1142887655-32760-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit RT-Attachment: 826/7090/4736 


According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.

_______________________________________________
enum mailing list
enum@ietf.org
https://www1.ietf.org/mailman/listinfo/enum
------------=_1142887655-32760-0 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 ------------=_1142887655-32760-0-- From enum-bounces@ietf.org Mon Mar 20 16:07:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRb0-0006I9-NN; Mon, 20 Mar 2006 16:07:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLRaz-0006HS-Hl for enum@ietf.org; Mon, 20 Mar 2006 16:07:21 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLRay-0003hB-9f for enum@ietf.org; Mon, 20 Mar 2006 16:07:21 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 20 Mar 2006 13:07:12 -0800 X-IronPort-AV: i="4.03,112,1141632000"; d="scan'208"; a="418423144:sNHT685622902" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k2KL7Bw1015477 for ; Mon, 20 Mar 2006 13:07:11 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2KL7eVw013419 for ; Mon, 20 Mar 2006 13:08:15 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: IETF ENUM WG From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Mon, 20 Mar 2006 15:07:08 -0600 X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=227; t=1142888896; x=1143321096; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Bounces... |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3DDPV4t/EH9hDxo+kkLPd8xeXvnyw=3D; b=CS2/4tZBBqGsrsEp8FlV7sGi1Jkv6Mn/ym4HP2Z12nHrFrSQBXZ6MVpcD7g00HedALxMnZSt bOCp4UaxEzvqoQVa1jy4UEsNLZH0Ov9whRCjenjcRazTAyr4DLRbUyC5UAfXnZ+1nAZVjRUupOo 6ViBnF8f/aW2usnSbkK7GzxY=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [Enum] Bounces... 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 Someone on this list have a broken mailer, so we got some bounces. That should be over now. I hope. I have added a filter that should kill mail from Mailer- daemon@*....and hope that should do the trick. paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 00:54:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZpN-0003IL-EV; Tue, 21 Mar 2006 00:54:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZpM-0003IG-8h for enum@ietf.org; Tue, 21 Mar 2006 00:54:44 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLZpK-00078o-SM for enum@ietf.org; Tue, 21 Mar 2006 00:54:44 -0500 Received: from [130.129.133.160] (DHCP-Wireless-133-160.ietf65.org [130.129.133.160]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k2L5t4bH005790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Mar 2006 21:55:05 -0800 Message-ID: <441F9512.5000304@shockey.us> Date: Tue, 21 Mar 2006 00:54:26 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: enum@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: Cullen Jennings , =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= , "Peterson, Jon" , Allison Mankin Subject: [Enum] ENUM Working Group Last call on ENUM Validation Mapping for EPP 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 Title : ENUM Validation Information Mapping for the Extensible Provisioning Protocol Author(s) : B. Hoeneisen Filename : draft-ietf-enum-validation-epp-03.txt Pages : 26 Date : 2006-2-15 This document describes an Extensible Provisioning Protocol (EPP) extension framework for mapping information about the validation process that has been applied for the E.164 number (or number range), which the E.164 Number Mapping (ENUM) domain name is based on. Specified in the Extensible Markup Language (XML), this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of ENUM domain names. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-validation-epp-03.txt The intent of the last call is to solicit comments before submitting the ID to the IESG as a Proposed Standard. This document has been under discussion since early 2005. The purpose of a working group Last Call is in the style of "speak now or forever hold your peace" in case there are fundamental objections which have not gotten previous or adequate discussion, or minor errors which need correction. Work group last call will extend for 3 weeks or so from today Mar 21 until at least April 11 though we can modify that if new issues come up. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 01:04:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZz4-0007uk-7T; Tue, 21 Mar 2006 01:04:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLZz2-0007uQ-9M for enum@ietf.org; Tue, 21 Mar 2006 01:04:44 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLZz0-0007WC-R8 for enum@ietf.org; Tue, 21 Mar 2006 01:04:44 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2L64eY2039022; Tue, 21 Mar 2006 07:04:40 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2L64et4039021; Tue, 21 Mar 2006 07:04:40 +0100 (CET) (envelope-from www) Date: Tue, 21 Mar 2006 07:04:40 +0100 (CET) From: "Richard Shockey via RT" <3761bis@frobbit.se> In-Reply-To: <441F9756.3030800@shockey.us> References: <441F9756.3030800@shockey.us> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #828 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: richard@shockey.us Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.5 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal NAPTR records clarification) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Tue Mar 21 07:04:40 2006: Request 828 was acted upon. Transaction: Ticket created by richard@shockey.us Queue: 3761bis Subject: Use of NTN ( Non terminal NAPTR records clarification) Owner: Nobody Requestors: richard@shockey.us Status: new Ticket Test -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 07:11:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLfhj-0006yN-Jz; Tue, 21 Mar 2006 07:11:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLfhi-0006yI-PT for enum@ietf.org; Tue, 21 Mar 2006 07:11:14 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLfhg-0004tJ-99 for enum@ietf.org; Tue, 21 Mar 2006 07:11:14 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2LCBAlq040089; Tue, 21 Mar 2006 13:11:10 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2LCB9Yw040088; Tue, 21 Mar 2006 13:11:09 +0100 (CET) (envelope-from www) Date: Tue, 21 Mar 2006 13:11:09 +0100 (CET) Subject: RE: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal NAPTRrecords clarification) From: "Pfautz, Penn L, NEO via RT" <3761bis@frobbit.se> In-Reply-To: <34DA635B184A644DA4588E260EC0A25A0C68231A@ACCLUST02EVS1.ugd.att.com> References: <34DA635B184A644DA4588E260EC0A25A0C68231A@ACCLUST02EVS1.ugd.att.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #828 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: ppfautz@att.com To: richard@shockey.us MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.5 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Rich What's the username and password? Did I miss them in Patrik's earlier mails? Thanks, Penn -----Original Message----- From: Richard Shockey via RT [mailto:3761bis@frobbit.se] Sent: Tuesday, March 21, 2006 1:05 AM Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal NAPTRrecords clarification) Tue Mar 21 07:04:40 2006: Request 828 was acted upon. Transaction: Ticket created by richard@shockey.us Queue: 3761bis Subject: Use of NTN ( Non terminal NAPTR records clarification) Owner: Nobody Requestors: richard@shockey.us Status: new Ticket Test -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 08:18:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLgki-0006g9-NR; Tue, 21 Mar 2006 08:18:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLgki-0006du-04 for enum@ietf.org; Tue, 21 Mar 2006 08:18:24 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLgkg-0007Bp-GY for enum@ietf.org; Tue, 21 Mar 2006 08:18:23 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2LDIKvE040238; Tue, 21 Mar 2006 14:18:20 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2LDIKvb040237; Tue, 21 Mar 2006 14:18:20 +0100 (CET) (envelope-from www) Date: Tue, 21 Mar 2006 14:18:20 +0100 (CET) Subject: Re: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal NAPTRrecords clarification) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: <34DA635B184A644DA4588E260EC0A25A0C68231A@ACCLUST02EVS1.ugd.att.com> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #828 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: richard@shockey.us MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.5 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On 21 mar 2006, at 06.11, Pfautz, Penn L, NEO via RT wrote: > > > Rich > What's the username and password? Did I miss them in Patrik's earlier > mails? Not released yet. I'll be back with instructions. paf > Thanks, > Penn > > -----Original Message----- > From: Richard Shockey via RT [mailto:3761bis@frobbit.se] > Sent: Tuesday, March 21, 2006 1:05 AM > Cc: enum@ietf.org > Subject: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal > NAPTRrecords clarification) > > > Tue Mar 21 07:04:40 2006: Request 828 was acted upon. > Transaction: Ticket created by richard@shockey.us > Queue: 3761bis > Subject: Use of NTN ( Non terminal NAPTR records clarification) > Owner: Nobody > Requestors: richard@shockey.us > Status: new > Ticket > > > > Test > > -- > > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Richard Shockey, Director - Member of Technical Staff > NeuStar Inc. > 46000 Center Oak Plaza - Sterling, VA 20166 > sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com > ENUM +87810-13313-31331 > PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 > Fax: +1 815.333.1237 > or > > ; > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > > _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 12:13:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLkQV-0004va-53; Tue, 21 Mar 2006 12:13:47 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLkQU-0004uT-Ct for enum@ietf.org; Tue, 21 Mar 2006 12:13:46 -0500 Received: from norman.insensate.co.uk ([213.152.49.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLkQT-00005w-0w for enum@ietf.org; Tue, 21 Mar 2006 12:13:46 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by norman.insensate.co.uk (Postfix) with ESMTP id 0870A809CC; Tue, 21 Mar 2006 17:13:40 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v746.3) Content-Transfer-Encoding: 7bit Message-Id: <914C8EC3-16D4-435D-8545-05EF1691A622@insensate.co.uk> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: IETF ENUM WG , Richard Shockey , =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= From: lconroy Date: Tue, 21 Mar 2006 11:13:40 -0600 X-Mailer: Apple Mail (2.746.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: Subject: [Enum] Tickets - NTNs is too broad 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 Patrik, Richard, folks, I was going to slam in several tickets on NTNs and their clarification, but Richard beat me too it with a single ticket for all clarifications. IMHO there are a set of different issues to do with NTNs - they go all through the Experiences document. Initial items - note that IMHO, points (v) and particularly (vi) are quite complex, and I'm unsure whether adding this functionality would mean a re-cycle rather than moving to draft standard. (i) ORDER and PRIORITY is significant only within the current domain (ii) On detecting a loop (or an unacceptably long chain of NTN references), the client should "back out" and continue processing with any other NAPTRs in the referring zone. [i.e. it should not simply abort the whole ENUM query] (iii) the absence of a flag indicates a Non-Terminal NAPTR. In this case, the services field is also empty, as is the REGEXP field, with the replacement field holding the target FQDN (Fully Qualified Domain Name). (iv) Clarify that the Enumservice registration process is appropriate only where the flags field contains the 'u' flag. (v) Consider creating a new non-terminal flag, with a new separate Registration process for non-terminal-enumservices. (vi) Consider creating a new non-terminal flag that uses teh REGEXP field to generate a target FQDN, and how that target FQDN is generated from the REGEXP Given that there's a ticket already, can I just push these into the system? all the best, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 17:55:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLplG-0004p9-Rm; Tue, 21 Mar 2006 17:55:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLplF-0004p4-9H for enum@ietf.org; Tue, 21 Mar 2006 17:55:33 -0500 Received: from test-iport-1.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLplD-0008E3-0T for enum@ietf.org; Tue, 21 Mar 2006 17:55:33 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by test-iport-1.cisco.com with ESMTP; 21 Mar 2006 14:55:30 -0800 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k2LMtU7T021598 for ; Tue, 21 Mar 2006 14:55:30 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2LMuTVM023865 for ; Tue, 21 Mar 2006 14:56:30 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: <207E2A83-1896-4178-917F-CA6ED019FBE0@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: IETF ENUM WG From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Tue, 21 Mar 2006 16:55:27 -0600 X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=548; t=1142981790; x=1143413990; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Instructions=20for=20the=20ticket=20system=20for=203761bis |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3DxakNi/fWUXANSdYLaP+oD6x6reM=3D; b=M4lJ4iCdlmNtSNEOb72mhefuCJ1HKT2uxeerBjoJpOqfBP/rAiG1u1wMn1rqT6g06IbdCQbw OTsn9rpS9IF4W+CGw2VwQqDDHf0cBJlx8mncAe0MPLLM1xjSrFA9eMU9tndHH00x844p6R8OGCb LtMTHPytIijwlUeSsHB6rhOw=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.5 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: [Enum] Instructions for the ticket system for 3761bis 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 Here are the instructions. (1) Only one ticket per topic (2) Send the email to 3761bis@frobbit.se (3) If you reply to an email with a ticket, make sure the subject line is not changed, and that the mail is sent to 3761bis@frobbit.se (4) You can access the ticket system by going to http:// ticket.frobbit.se/ (or using SSL to https://dav.frobbit.se:445/), log in with the username "3761bis" and password "ietf-enum" I will over time close tickets when I have added them to 3761bis document. Have fun! Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 17:57:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpnU-0005ud-HB; Tue, 21 Mar 2006 17:57:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpnT-0005uW-E7 for enum@ietf.org; Tue, 21 Mar 2006 17:57:51 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLpnS-0008Mo-6M for enum@ietf.org; Tue, 21 Mar 2006 17:57:51 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 21 Mar 2006 14:56:07 -0800 X-IronPort-AV: i="4.03,116,1141632000"; d="scan'208"; a="263307706:sNHT9694830196" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k2LMu3w1010314; Tue, 21 Mar 2006 14:56:05 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2LMuTVN023865; Tue, 21 Mar 2006 14:57:02 -0800 In-Reply-To: <914C8EC3-16D4-435D-8545-05EF1691A622@insensate.co.uk> References: <914C8EC3-16D4-435D-8545-05EF1691A622@insensate.co.uk> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <854D90EA-913D-4A09-98B4-73C8A05587B7@cisco.com> Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Tue, 21 Mar 2006 16:56:00 -0600 To: lconroy X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=166; t=1142981824; x=1143414024; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Re=3A=20Tickets=20-=20NTNs=20is=20too=20broad |To:lconroy=20; X=v=3Dmtcc.com=3B=20h=3DhFlk4ueyavjb7XBkxqsaeCG80zo=3D; b=kZnhjqr3DRijcYs3W0bceCN0CM3SbNXZTsPHVeGdxmLuSHnN7/v65mIQOZvJuJ9jqoVFk8I5 1+1CpMLXf/oHTgSCjwfUYoOW1SA/284QMj8nLjqsRXcTgEkiayCRc1/fAp9dPCfcJQiHBZxnahL 6/L3ViQgmnkoviAGFhMrDaLY=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: IETF ENUM WG , Richard Shockey Subject: [Enum] Re: Tickets - NTNs is too broad 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 21 mar 2006, at 11.13, lconroy wrote: > Given that there's a ticket already, can I just push these into the > system? One issue per ticket. paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 17:58:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpnn-0006LW-2J; Tue, 21 Mar 2006 17:58:11 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpnl-0006LN-Vw for enum@ietf.org; Tue, 21 Mar 2006 17:58:09 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLpnk-0008Nc-Bd for enum@ietf.org; Tue, 21 Mar 2006 17:58:09 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2LMw6fi042521; Tue, 21 Mar 2006 23:58:06 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2LMw65S042520; Tue, 21 Mar 2006 23:58:06 +0100 (CET) (envelope-from www) Date: Tue, 21 Mar 2006 23:58:06 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #828 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: richard@shockey.us MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( Non terminal NAPTR records clarification) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 17:58:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpno-0006My-63; Tue, 21 Mar 2006 17:58:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLpnl-0006LM-Vw for enum@ietf.org; Tue, 21 Mar 2006 17:58:09 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLpnk-0008Nd-Bd for enum@ietf.org; Tue, 21 Mar 2006 17:58:09 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2LMw6EN042517; Tue, 21 Mar 2006 23:58:06 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2LMw5vA042516; Tue, 21 Mar 2006 23:58:05 +0100 (CET) (envelope-from www) Date: Tue, 21 Mar 2006 23:58:05 +0100 (CET) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: <441F9756.3030800@shockey.us> References: <441F9756.3030800@shockey.us> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #828 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se To: richard@shockey.us MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Cc: enum@ietf.org Subject: [Enum] [ticket.frobbit.se #828] Use of NTN ( Non terminal NAPTR records clarification) X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I want more specification in an issue than just the subject. Also, this ticket is "poisoned" by questions about the ticket system. Please resubmit with clarification of the issues. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 18:14:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLq3G-0005xk-Dc; Tue, 21 Mar 2006 18:14:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLq3F-0005xe-V1 for enum@ietf.org; Tue, 21 Mar 2006 18:14:09 -0500 Received: from norman.insensate.co.uk ([213.152.49.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLq3E-0000IS-LQ for enum@ietf.org; Tue, 21 Mar 2006 18:14:09 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by norman.insensate.co.uk (Postfix) with ESMTP id 7C55A80AB4; Tue, 21 Mar 2006 23:14:05 +0000 (GMT) In-Reply-To: <854D90EA-913D-4A09-98B4-73C8A05587B7@cisco.com> References: <914C8EC3-16D4-435D-8545-05EF1691A622@insensate.co.uk> <854D90EA-913D-4A09-98B4-73C8A05587B7@cisco.com> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <2F10F488-A17E-460D-B768-45A08270EE1F@insensate.co.uk> Content-Transfer-Encoding: quoted-printable From: lconroy Subject: Re: [Enum] Re: Tickets - NTNs is too broad Date: Tue, 21 Mar 2006 17:14:05 -0600 To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= X-Mailer: Apple Mail (2.746.3) X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: IETF ENUM WG , Richard Shockey 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 Patrik, folks, I can't decode the answer... I guess that this is a yes, and apologies if it was a no. Incoming! all the best, Lawrence On 21 Mar 2006, at 16:56, Patrik F=E4ltstr=F6m wrote: > On 21 mar 2006, at 11.13, lconroy wrote: >> Given that there's a ticket already, can I just push these into =20 >> the system? > One issue per ticket. > > paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 18:30:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqJB-0001kS-OH; Tue, 21 Mar 2006 18:30:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqJB-0001kN-7r for enum@ietf.org; Tue, 21 Mar 2006 18:30:37 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLqJ9-0000yo-PV for enum@ietf.org; Tue, 21 Mar 2006 18:30:37 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2LNUX0S042607; Wed, 22 Mar 2006 00:30:33 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2LNUXv4042606; Wed, 22 Mar 2006 00:30:33 +0100 (CET) (envelope-from www) Date: Wed, 22 Mar 2006 00:30:33 +0100 (CET) From: "lconroy via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #838 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: lconroy@insensate.co.uk Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [Enum] [ticket.frobbit.se #838] ORDER/PRIORITY locality X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Wed Mar 22 00:30:32 2006: Request 838 was acted upon. Transaction: Ticket created by lconroy@insensate.co.uk Queue: 3761bis Subject: ORDER/PRIORITY locality Owner: Nobody Requestors: lconroy@insensate.co.uk Status: new Ticket Hi Patrik, ORDER and PRIORITY is significant only within the current domain. This is not clear in RFC 3761. This matters for NTN processing, where the ORDER and PRIORITY values are only considered within a single zone. The ORDER and PRIORITY value for a NTN and is not relevant in the zone targeted by that NTN. atb, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 18:45:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqXa-0003mZ-Hc; Tue, 21 Mar 2006 18:45:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqXZ-0003mU-AW for enum@ietf.org; Tue, 21 Mar 2006 18:45:29 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLqXY-0001XZ-2m for enum@ietf.org; Tue, 21 Mar 2006 18:45:29 -0500 Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 21 Mar 2006 15:45:27 -0800 X-IronPort-AV: i="4.03,116,1141632000"; d="scan'208"; a="263332840:sNHT1283990780" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k2LNjQ7T018240 for ; Tue, 21 Mar 2006 15:45:26 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2LNkPp5024291 for ; Tue, 21 Mar 2006 15:46:26 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( Non terminal NAPTR records clarification) Date: Tue, 21 Mar 2006 17:45:24 -0600 To: IETF ENUM WG X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=352; t=1142984787; x=1143416987; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Re=3A=20[Enum]=20[ticket.frobbit.se=20#828]=20Resolved=3A=20Use=20of=20N TN=20(=20Non=20terminal=20NAPTR=20records=20clarification)=20 |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3DkaF435RPSDM0HH/vP/1cQQhXixw=3D; b=b+BtXJfW4O0PE8VmR7feRFAVHBxuAk4Iysqvg/KXuWtAfdd4QcDm18uV+IWHnaNaiRdSZymu yZrvkYOdsV60Ch4DkGeMgJlBqWeWXmgaOCzYpPplFraGukeejyZlW+99muxZnK4ofur8bNkhpjz 1kndqLydXZvF4UuJhA9li7ak=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 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 21 mar 2006, at 16.58, Patrik F=E4ltstr=F6m via RT wrote: > According to our records, your request has been resolved. If you =20 > have any > further questions or concerns, please respond to this message. These message about a closed issue will in the future only be sent to =20= the requestor, not this ENUM mailing list. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 18:53:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqfD-0005d1-VY; Tue, 21 Mar 2006 18:53:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLqfC-0005ck-50 for enum@ietf.org; Tue, 21 Mar 2006 18:53:22 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FLqfA-00022k-PR for enum@ietf.org; Tue, 21 Mar 2006 18:53:22 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( Nonterminal NAPTR records clarification) Date: Wed, 22 Mar 2006 00:55:12 +0100 Message-ID: <32755D354E6B65498C3BD9FD496C7D462C490D@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( Nonterminal NAPTR records clarification) Thread-Index: AcZNQh2n1nZQ8yBOQSeaB5xRPCzgKwAAMbuk From: "Stastny Richard" To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= , "IETF ENUM WG" X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 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 >These message about a closed issue will in the future only be sent to=20 >the requestor, not this ENUM mailing list. Why? IMHO it is interesting for everbody if an issue is closed BTW, when is an issue closed? there should go a reason with the message, eg taken into RFC3761bis or rejected or whatever Richard=20 ________________________________ Von: Patrik F=E4ltstr=F6m [mailto:paf@cisco.com] Gesendet: Mi 22.03.2006 00:45 An: IETF ENUM WG Betreff: Re: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( = Nonterminal NAPTR records clarification)=20 On 21 mar 2006, at 16.58, Patrik F=E4ltstr=F6m via RT wrote: > According to our records, your request has been resolved. If you=20 > have any > further questions or concerns, please respond to this message. These message about a closed issue will in the future only be sent to=20 the requestor, not this ENUM mailing list. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 19:47:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrVa-0001MP-74; Tue, 21 Mar 2006 19:47:30 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrVY-0001C9-FW for enum@ietf.org; Tue, 21 Mar 2006 19:47:28 -0500 Received: from test-iport-1.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLrVX-0004Jl-6O for enum@ietf.org; Tue, 21 Mar 2006 19:47:28 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by test-iport-1.cisco.com with ESMTP; 21 Mar 2006 16:47:26 -0800 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k2M0lQGv023047 for ; Tue, 21 Mar 2006 16:47:26 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2M0mPXI024837 for ; Tue, 21 Mar 2006 16:48:26 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: <906B70CC-957D-4215-889A-889A6E102825@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: IETF ENUM WG From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Tue, 21 Mar 2006 18:47:23 -0600 X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=1317; t=1142988506; x=1143420706; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Why=20ticket=20system? |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3D7QLfPMo+j8g6VZ+ZDPvp6WqciP0=3D; b=HuYGeMIan4Pq4dby/o0pKqickeorchABbZgO5wKcODEe8M3TRwvTt3blY2fwYxxcfboLI6GB npnKVktVaMnxdElnEqfZeFFmSWczP7uIoNcDqe+foLbWWGJ95U3b4+2Eb6x+mWVO8BGwEK/zUtU whU9gGj6V2ubntibhgVZaABE=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Subject: [Enum] Why ticket system? X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I have rightfully got private email from people that was not in Dallas, and that ask "what is happening". I send sincere apologies as the one introducing the ticket system without explaining more than at the meeting in Dallas. The ticket system was requested by me, as editor of RFC3761 that promised to now start work on RFC 3761bis. To be able to do this, I want as editor to know what issues I have to look at before creating new versions of the draft. The ticket system is as you all see accessible, which imply you will be able to see all input that people have given to the new version of the document. It is supposed to help to get an open transparent process. Yes, as document editor I will close the tickets. I decide why, when and how. Just like any editing of a draft. Difference now is that you will see all comments, you will be able to see all decisions, etc etc. I am in coordination with Henrik that do the tools for the IETF, and this is a test... It has been tested before, but then (if I understand correctly) as a separate ticket system, without announcements to the main mailing list. If it doesn't work, I will turn it off asap! (And only use it for me personally...) Patrik, Editor of RFC3761bis, NOT speaking as wg co-chair _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 21 19:50:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrYA-0002Ks-Rn; Tue, 21 Mar 2006 19:50:10 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLrY9-0002Km-JR for enum@ietf.org; Tue, 21 Mar 2006 19:50:09 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLrY8-0004Nt-9g for enum@ietf.org; Tue, 21 Mar 2006 19:50:09 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-3.cisco.com with ESMTP; 21 Mar 2006 16:50:08 -0800 X-IronPort-AV: i="4.03,116,1141632000"; d="scan'208"; a="419063960:sNHT31563132" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k2M0o7w1010147; Tue, 21 Mar 2006 16:50:07 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2M0p6Mb024868; Tue, 21 Mar 2006 16:51:07 -0800 In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C490D@oefeg-s04.oefeg.loc> References: <32755D354E6B65498C3BD9FD496C7D462C490D@oefeg-s04.oefeg.loc> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <3E2FAA19-DD38-4BD4-B107-EBD6DAFA7EA5@cisco.com> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN ( Nonterminal NAPTR records clarification) Date: Tue, 21 Mar 2006 18:50:04 -0600 To: Stastny Richard X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=1945; t=1142988667; x=1143420867; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Re=3A=20[Enum]=20[ticket.frobbit.se=20#828]=20Resolved=3A=20Use=20of=20N TN=20(=20Nonterminal=20NAPTR=20records=20clarification)=20 |To:Stastny=20Richard=20; X=v=3Dmtcc.com=3B=20h=3D1+Q67lpwu3may7yDIqnWI/zNgUE=3D; b=pA5ehLn2mldUKGFcK7RtZxX3R7h6PNsRfbqc0aAOZHUhi7G0Npz4F8nQWORLtU/HkuIDLZ1J 8bNZgLfSlt2DOiHGTE4hC3nXb9XrFHDzAG9e7QKvu56HxLXGIe+ACfwo959T0Kr9+XhHPwaJAej iXLUjpym7B9wzHHqbVI4R9mA=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da 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 On 21 mar 2006, at 17.55, Stastny Richard wrote: >> These message about a closed issue will in the future only be sent to >> the requestor, not this ENUM mailing list. > > Why? > IMHO it is interesting for everbody if an issue is closed Ok, if that is interesting. No problem at all. > BTW, when is an issue closed? I decide myself. As document editor. Just like when we do not have a =20 ticket system. Difference now is that you can log into the website =20 and see what I write, reopen ticket and complain!!! > there should go a reason with the message, eg taken into RFC3761bis or > rejected or whatever This turn a bit technical, but let me tell you the short version: =20 When closing a ticket, two events are generated. One that attaches =20 the last text message (like when a ticket is updated) and one that =20 closes the ticket. You will always see the text message, but not when =20= the ticket is closed. The latter is just(!) an event notification. Patrik > > Richard > > > ________________________________ > > Von: Patrik F=E4ltstr=F6m [mailto:paf@cisco.com] > Gesendet: Mi 22.03.2006 00:45 > An: IETF ENUM WG > Betreff: Re: [Enum] [ticket.frobbit.se #828] Resolved: Use of NTN =20 > ( Nonterminal NAPTR records clarification) > > > > On 21 mar 2006, at 16.58, Patrik F=E4ltstr=F6m via RT wrote: > >> According to our records, your request has been resolved. If you >> have any >> further questions or concerns, please respond to this message. > > These message about a closed issue will in the future only be sent to > the requestor, not this ENUM mailing list. > > Patrik > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum > > > > > _______________________________________________ > enum mailing list > enum@ietf.org > https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Mar 22 10:14:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM52k-0006Zf-By; Wed, 22 Mar 2006 10:14:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FM52j-0006ZX-6L for enum@ietf.org; Wed, 22 Mar 2006 10:14:37 -0500 Received: from smartmx-08.inode.at ([213.229.60.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FM52h-00035p-Sb for enum@ietf.org; Wed, 22 Mar 2006 10:14:37 -0500 Received: from [130.129.130.148] (port=2034 helo=mah9.inode.at) by smartmx-08.inode.at with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FM52b-0006Vp-Nj; Wed, 22 Mar 2006 16:14:30 +0100 Message-Id: <7.0.1.0.2.20060322161205.06119df0@inode.at> Message-Id: <7.0.1.0.2.20060322161034.066c3668@inode.at> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 22 Mar 2006 16:14:15 +0100 To: enum-wg@ripe.net,enum@ietf.org From: Michael Haberler Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed; x-avg-checked=avg-ok-73693FDA X-Spam-Score: 0.1 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Cc: Subject: [Enum] +353 ENUM bid 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 http://www.comreg.ie/publications/default.asp?ctype=5&nid=102304 -Michael _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Mar 23 11:13:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMSQl-0008P9-58; Thu, 23 Mar 2006 11:12:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMSQj-0008P4-1m for enum@ietf.org; Thu, 23 Mar 2006 11:12:57 -0500 Received: from peregrine.verisign.com ([216.168.239.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMSQh-0001bY-SW for enum@ietf.org; Thu, 23 Mar 2006 11:12:57 -0500 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by peregrine.verisign.com (8.13.1/8.13.4) with ESMTP id k2NGO31C011270 for ; Thu, 23 Mar 2006 11:24:03 -0500 Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Mar 2006 11:12:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Mar 2006 11:12:54 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Suggestion for draft-ietf-enum-enumservices-guide-00 Thread-Index: AcZOlKQkn6NfT+FwRFqGXwOjWwfD0g== From: "Walker, Charles" To: X-OriginalArrivalTime: 23 Mar 2006 16:12:55.0558 (UTC) FILETIME=[A4EA4260:01C64E94] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Enum] Suggestion for draft-ietf-enum-enumservices-guide-00 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org I'm new to the ENUM WG, having attended my first IETF in Dallas this week. One of the things that I work on is implementing ENUM. I like the Guide and Template for IANA Registrations of Enumervices (draft-ietf-enum-enumservices-guide-00). It is a good idea. Some ENUM services, one example being the Calling Name service (draft-shockey-enum-cnam-00) register new URI parameters. Or, maybe a particular new ENUM service requires a URI parameter which has already defined to be in the URI returned in the NAPTR record. So my suggestion would be to add two things: 1. A section on new URI parameters being defined. 2. URI parameters which MUST, MUST NOT, or SHOULD be present in the URI returned in the NAPTR record for this service. Regards, Charles Walker _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Mar 23 18:50:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMZZH-00012Q-1t; Thu, 23 Mar 2006 18:50:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMZZ5-0000yN-IP; Thu, 23 Mar 2006 18:50:03 -0500 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMZZ5-0004wy-GH; Thu, 23 Mar 2006 18:50:03 -0500 Received: from cypress.neustar.com ([209.173.57.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FMZZ4-0007GY-0i; Thu, 23 Mar 2006 18:50:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k2NNo10e014723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Mar 2006 23:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FMZZ3-0001Cf-Ks; Thu, 23 Mar 2006 18:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 23 Mar 2006 18:50:01 -0500 X-Spam-Score: -2.6 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-calendar-service-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services Author(s) : R. Mahy Filename : draft-ietf-enum-calendar-service-00.txt Pages : 5 Date : 2006-3-23 This document registers a Telephone Number Mapping (ENUM) service for Internet Calendaring Services. Specifically, this document focuses on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-calendar-service-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-calendar-service-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-calendar-service-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-3-23160631.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-calendar-service-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-calendar-service-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-23160631.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 Thu Mar 23 18:50:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMZZ8-0000zI-8w; Thu, 23 Mar 2006 18:50:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMZZ4-0000xq-R0; Thu, 23 Mar 2006 18:50:02 -0500 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMZZ3-0004wi-Un; Thu, 23 Mar 2006 18:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k2NNo1BX005408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Mar 2006 23:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FMZZ3-0001Ck-LW; Thu, 23 Mar 2006 18:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 23 Mar 2006 18:50:01 -0500 X-Spam-Score: 0.3 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-infrastructure-enum-reqs-01.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 : Infrastrucure ENUM Requirements Author(s) : S. Lind, P. Pfautz Filename : draft-ietf-enum-infrastructure-enum-reqs-01.txt Pages : 8 Date : 2006-3-23 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-01.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-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2006-3-23161128.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-infrastructure-enum-reqs-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-3-23161128.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 Mar 24 04:33:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMift-0004XX-Eq; Fri, 24 Mar 2006 04:33:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMifs-0004XP-Qd for enum@ietf.org; Fri, 24 Mar 2006 04:33:40 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMifr-0006yh-Cs for enum@ietf.org; Fri, 24 Mar 2006 04:33:40 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2O9XbRn070061; Fri, 24 Mar 2006 10:33:37 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2O9XaRU070060; Fri, 24 Mar 2006 10:33:36 +0100 (CET) (envelope-from www) Date: Fri, 24 Mar 2006 10:33:36 +0100 (CET) From: "Daniel Isaksson via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #850 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: daniel.isaksson@adamobredband.com Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by charles.frobbit.se id k2O9XbRn070061 X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [Enum] [ticket.frobbit.se #850] IAN-02E / 207059 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Fri Mar 24 10:33:36 2006: Request 850 was acted upon. Transaction: Ticket created by daniel Queue: 3761bis Subject: IAN-02E / 207059 Owner: eva Requestors: daniel.isaksson@adamobredband.com Status: new Ticket Content removed by IETF Exec Dir // daniel i. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Mar 24 06:55:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMktS-0003xP-5c; Fri, 24 Mar 2006 06:55:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMktL-0002tB-0h for enum@ietf.org; Fri, 24 Mar 2006 06:55:43 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMkdT-0002kx-LN for enum@ietf.org; Fri, 24 Mar 2006 06:39:21 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2OBdHMA070344; Fri, 24 Mar 2006 12:39:17 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2OBdHFt070343; Fri, 24 Mar 2006 12:39:17 +0100 (CET) (envelope-from www) Date: Fri, 24 Mar 2006 12:39:17 +0100 (CET) From: "Daniel Isaksson via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #851 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: daniel.isaksson@adamobredband.com Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by charles.frobbit.se id k2OBdHMA070344 X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [Enum] [ticket.frobbit.se #851] IAN-02E / 206682 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Fri Mar 24 12:39:16 2006: Request 851 was acted upon. Transaction: Ticket created by daniel Queue: 3761bis Subject: IAN-02E / 206682 Owner: eva Requestors: daniel.isaksson@adamobredband.com Status: new Ticket Content removed by IETF Exec Dir // daniel i. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Mar 24 15:53:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMtI2-0000SE-SI; Fri, 24 Mar 2006 15:53:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FMtI1-0000RH-SS for enum@ietf.org; Fri, 24 Mar 2006 15:53:45 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMtI0-0002Ru-CU for enum@ietf.org; Fri, 24 Mar 2006 15:53:45 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2OKrfZZ071730; Fri, 24 Mar 2006 21:53:42 +0100 (CET) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2OKrfT8071729; Fri, 24 Mar 2006 21:53:41 +0100 (CET) (envelope-from www) Date: Fri, 24 Mar 2006 21:53:41 +0100 (CET) From: "Stastny Richard via RT" <3761bis@frobbit.se> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C492E@oefeg-s04.oefeg.loc> References: <32755D354E6B65498C3BD9FD496C7D462C492E@oefeg-s04.oefeg.loc> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #861 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: Richard.Stastny@oefeg.at Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Subject: [Enum] [ticket.frobbit.se #861] Fast lane for Enumservice IANA registration X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Fri Mar 24 21:53:41 2006: Request 861 was acted upon. Transaction: Ticket created by Richard.Stastny@oefeg.at Queue: 3761bis Subject: Fast lane for Enumservice IANA registration Owner: Nobody Requestors: Richard.Stastny@oefeg.at Status: new Ticket It is proposed to establish a fast lane for rIANA egistration of non-essential Enumservices using only expert review and not the full RFC cycle. This is derived from a similar approach proposed in draft-ietf-dnsext-2929bis-02.txt "DNS IANA Considerations) for registration of DNS RR. If this can be done for DNS RR, it also is feasible for Enumservices within this I-D the following is proposed: 3.1.1 DNS TYPE Allocation Policy Parameter values specified above as assigned based on DNS TYPE Allocation Policy are allocated by Expert Review if they meet the two requirements listed below. If they do not meet these requirements, they are allocated by IETF Standards Action as modified by [RFC 4020]. 1. A complete template as specified in Section 3.1.2 has been posted for three weeks to the namedroppers@ops.ietf.org mailing list before the Expert Review. Note that partially completed or draft templates may be posted for comment. 2. The RR for which a TYPE code is being requested must be either (a) a data TYPE which can be handled as an Unknown RR as described in [RFC 3597] or (b) a Meta TYPE who processing is optional, i.e., which it is safe to simply discard. Note that such RRs may include additional section processing provided such processing is optional. The wording has to be changed appropriate, especially item 2. It is proposed to implement such a procedure for Enumservices directed to the use of a specific limited community (e.g foaf), to provent the usaage of x- Enumservices with the potential of name clashes. Until 3761bis is finalized, the procedure could already be implemented via draft-ietf-enum-enumservices-guide Richard Stastny _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sat Mar 25 15:52:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNFk4-0000tH-N3; Sat, 25 Mar 2006 15:52:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNFk3-0000tC-4B for enum@ietf.org; Sat, 25 Mar 2006 15:52:11 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNFk2-0008Ca-OH for enum@ietf.org; Sat, 25 Mar 2006 15:52:11 -0500 Received: from [68.165.240.35] (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k2PKqUXr009244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Mar 2006 12:52:34 -0800 Message-ID: <4425AD81.1090805@shockey.us> Date: Sat, 25 Mar 2006 15:52:17 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: enum@ietf.org Subject: [Enum] ENUM Working Group Last call on Infrastructure ENUM Requirements Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 02ec665d00de228c50c93ed6b5e4fc1a Cc: Cullen Jennings , =?ISO-8859-1?Q?Patrik_F=E4ltstr?=, =?ISO-8859-1?Q?=F6m?= , "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 Title : Infrastructure ENUM Requirements Author(s) : S. Lind, P. Pfautz Filename : draft-ietf-enum-infrastructure-enum-reqs-01.txt Pages : 8 Date : 2006-3-23 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-01.txt The intent of the last call is to solicit comments before submitting the ID to the IESG as a Proposed Standard. This document has been under extensive discussion since early 2005. The purpose of a working group Last Call is in the style of "speak now or forever hold your peace" in case there are fundamental objections which have not gotten previous or adequate discussion, or minor errors which need correction. Work group last call will extend for 3 weeks or so from Monday Mar 27 until at least April 17 though we can modify that if new issues come up. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 07:52:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNUh4-0005l8-2H; Sun, 26 Mar 2006 07:50:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNUh1-0005jj-NE for enum@ietf.org; Sun, 26 Mar 2006 07:50:03 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNUh0-000722-9d for enum@ietf.org; Sun, 26 Mar 2006 07:50:03 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QCo0gB078720 for ; Sun, 26 Mar 2006 14:50:00 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QCo0Xs078716; Sun, 26 Mar 2006 14:50:00 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 14:50:00 +0200 (CEST) From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #869 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: patrik@frobbit.se Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [Enum] [ticket.frobbit.se #869] Test of approval of tickets X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 14:49:59 2006: Request 869 was acted upon. Transaction: Ticket created by paf Queue: 3761bis Subject: Test of approval of tickets Owner: Nobody Requestors: patrik@frobbit.se Status: new Ticket now I am testing _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 08:17:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNV7N-0005no-Ey; Sun, 26 Mar 2006 08:17:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNV7M-0005nb-H0 for enum@ietf.org; Sun, 26 Mar 2006 08:17:16 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNV7L-0008CA-2q for enum@ietf.org; Sun, 26 Mar 2006 08:17:16 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QDHC7Z078797; Sun, 26 Mar 2006 15:17:12 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QDHC1Q078796; Sun, 26 Mar 2006 15:17:12 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 15:17:12 +0200 (CEST) From: "lconroy via RT" <3761bis@frobbit.se> In-Reply-To: <2F728229-B895-4EA7-A548-9CE33F0089CD@insensate.co.uk> References: <2F728229-B895-4EA7-A548-9CE33F0089CD@insensate.co.uk> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #870 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: lconroy@insensate.co.uk Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Subject: [Enum] [ticket.frobbit.se #870] DDDS - RFC3404 reserves ALL flag characters X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 15:17:11 2006: Request 870 was acted upon. Transaction: Ticket created by lconroy@insensate.co.uk Queue: 3761bis Subject: DDDS - RFC3404 reserves ALL flag characters Owner: Nobody Requestors: lconroy@insensate.co.uk Status: new Ticket RFC 3404 specifies that all flag characters are reserved "for future versions of this document". This is wrong, IMHO. It reflects a problem with the way flag characters (and the expected output these imply) are specified. [i.e. within DDDS Applications, with behaviour that must not be redefined in other DDDS Application documents] Options: (i) simply remove the single sentence that reserves all flags - this is ignored by other DDDS Application specifications. This can be done as an erratum to RFC3404. (ii) remove this sentence and request an IANA registry for flags (as suggested for future use in RFC3404). i.e. have a separate small document to update RFC3404, listing the flag characters that have been defined and requesting a registry for them. (iii) note that all RFCs that define a new flag must indicate that they update RFC3404. (because they change the current RFC3404 reservation). atb, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 08:17:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNV7f-0006Dg-Q8; Sun, 26 Mar 2006 08:17:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNV7e-0006A9-Ap for enum@ietf.org; Sun, 26 Mar 2006 08:17:34 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNV7d-0008Cz-T3 for enum@ietf.org; Sun, 26 Mar 2006 08:17:34 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QDHWB7078809; Sun, 26 Mar 2006 15:17:32 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QDHWEQ078808; Sun, 26 Mar 2006 15:17:32 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 15:17:32 +0200 (CEST) From: "lconroy via RT" <3761bis@frobbit.se> In-Reply-To: <77097D39-C8A3-4A4A-9674-BB0BB9F6A6F5@insensate.co.uk> References: <77097D39-C8A3-4A4A-9674-BB0BB9F6A6F5@insensate.co.uk> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #871 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: lconroy@insensate.co.uk Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [Enum] [ticket.frobbit.se #871] DDDS - RFC3403/RFC3404 generation of target FQDN for Non-Terminal NAPTR X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 15:17:32 2006: Request 871 was acted upon. Transaction: Ticket created by lconroy@insensate.co.uk Queue: 3761bis Subject: DDDS - RFC3403/RFC3404 generation of target FQDN for Non-Terminal NAPTR Owner: Nobody Requestors: lconroy@insensate.co.uk Status: new Ticket RFC 3403 section 4.1 (and RFC 3404) imply that the REGEXP field can be used to generate a FQDN as the target for a non-terminal rule. RFC 3404 in particular suggests that one can choose which to use, and that one should look in both fields to see which one is not empty. I have problems with this "look at both and then use whatever is there" policy. AFAICT, the only ENUM clients that DO handle NTNs expect the target FQDN only to be in the replacement field. The other DDDS Applications that use non-terminal NAPTRs ALL put the target FQDN in the replacement field. I also have problems with the basic mechanism for generating a FQDN from the REGEXP field. How does one do this, when each DDDS Application works on its own kind of Application Unique String? Options: (i) Clarify in RFC3403 (and in RFC3404) that the target FQDN in a Non-Terminal NAPTR MUST be in the replacement field always. (ii) Clarify in RFC3403 that with an empty flags field (i.e. the absence of a flag), a target FQDN MUST be in the replacement field. If a DDDS Application wants to generate a target FQDN from the REGEXP field content, then it must define a specific flag to do this (and define how the AUS and REGEXP is used to generate a FQDN). [I prefer the latter option, as it means that we do not have to change RFC3404, and it gives more flexibility] Note: We could also spell out (in RFC3403) that an empty flags field ALWAYS means that this is a non-terminal NAPTR. atb, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 09:13:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNVzF-00046b-Ot; Sun, 26 Mar 2006 09:12:57 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNVzF-00046T-0a for enum@ietf.org; Sun, 26 Mar 2006 09:12:57 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNVzD-0001dk-Gq for enum@ietf.org; Sun, 26 Mar 2006 09:12:56 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QECrbn078981; Sun, 26 Mar 2006 16:12:53 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QECqql078980; Sun, 26 Mar 2006 16:12:52 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 16:12:52 +0200 (CEST) From: "lconroy via RT" <3761bis@frobbit.se> In-Reply-To: <81C8F573-708C-4279-9D75-0736AF0F5E25@insensate.co.uk> References: <81C8F573-708C-4279-9D75-0736AF0F5E25@insensate.co.uk> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #873 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: lconroy@insensate.co.uk Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Subject: [Enum] [ticket.frobbit.se #873] Character Set, Case Sensitivity, and NAPTR fields X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 16:12:52 2006: Request 873 was acted upon. Transaction: Ticket created by lconroy@insensate.co.uk Queue: 3761bis Subject: Character Set, Case Sensitivity, and NAPTR fields Owner: Nobody Requestors: lconroy@insensate.co.uk Status: new Ticket Character Set, Case Sensitivity, and NAPTR fields. NOTE - This is really three inter-related topics. As they are so closely tied together I have requested a single ticket. [a] use of non-ASCII (and non-printable characters) in SED/POSIX REGEXP field. I18N has been specified for DDDS, with UTF-8 encoding. However, there is no guidance on how this fits with SED/POSIX REGEXP and the characters that can be used. - All of the string fields can have valid characters that are not printable. Some may be 'difficult' or 'dangerous', such as NULL (0x00). Guidance or even prohibition would be useful. - Even when generating an IRI from the REGEXP field, there is a risk that the IRI, if presented to the end user (or used to open a web page, for example) can risk the end user being sent to a web page that is not the same as the one he or she expects. For example, the IRI may look like www.paypal.com but actually be constructed using some Cyrillic characters (e.g. www.xn-- pypal-4ve.com). This is a similar problem to the one raised for IDNs and domain registration, and works with punycode as well as standard UTF-8 encoding. At least advice on the presentation of mixed character IRIs should be covered in the security section. [b] Does allowing characters with multi-byte UTF-8 encoding in the services and flags fields help? For the services (and flags) field contents, permitting strings that are not in the US-ASCII equivalent range adds a requirement for multi-byte string matching to implementations with no obvious benefit. - We often have to register these strings with IANA (potentially for flags, and definitely for DDDS Application tags and for Enumservices). Non-ASCII registry data with IANA is not easy/possible. [c] Case Sensitivity is unclear for the flags and service field. We have **Assumed** that the flags and services field content is US-ASCII equivalent, and so we can choose whether or not these fields are case sensitive or not. However, if characters that are not in the US-ASCII equivalent range are used, it is unclear what exactly case sensitivity means - some of the mapped character sets do not have a concept of case sensitivity (what does case sensitivity mean in Klingon?) Options/Suggestions: (i-1) Add a Clear security issue stating that IRIs that contain mixed character sets SHOULD be indicated as such to end users when presented and used. (This one is a 'can of worms', but if we are to permit IRIs then we have exactly the same troubles as ICANN with IDN registrations). - Give guidance that if non-ASCII equivalent characters are used in the match sub-field of the REGEXP, then this MAY not work with some implementations of REGEXP processing. - Finally, state that only US-ASCII equivalent 'printable' characters should be used as delimiters and/or escape characters within the REGEXP. or (i-2) Remove reference to UTF-8 and require everything to be US- ASCII only, within the 'printable' range, and bar the use of IRIs (specifically the use of punycode). and (ii) Require that all characters in the flags and services fields MUST be US-ASCII only, and SHOULD be within the 'printable' range. I would suggest that NULL (0x00) be barred from use. and (iii) State Explicitly that the flags and services field contents are case insensitive. Of the first options, I hope that we can avoid the second one. Barring anything that is not ASCII would be a severe limitation. See also separate ticket for the REGEXP 'i' flag. all the best, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 09:26:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNWCG-0003W3-Il; Sun, 26 Mar 2006 09:26:24 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNWCF-0003Tq-N6 for enum@ietf.org; Sun, 26 Mar 2006 09:26:23 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNWCF-00029S-7b for enum@ietf.org; Sun, 26 Mar 2006 09:26:23 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QEQL6h079034; Sun, 26 Mar 2006 16:26:21 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QEQLnd079033; Sun, 26 Mar 2006 16:26:21 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 16:26:21 +0200 (CEST) From: "lconroy via RT" <3761bis@frobbit.se> In-Reply-To: <6BC21F6F-381F-4092-B2B4-C6F9E94B83EA@insensate.co.uk> References: <6BC21F6F-381F-4092-B2B4-C6F9E94B83EA@insensate.co.uk> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #874 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: lconroy@insensate.co.uk Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [Enum] [ticket.frobbit.se #874] REGEXP 'i' flag considered harmful X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 16:26:21 2006: Request 874 was acted upon. Transaction: Ticket created by lconroy@insensate.co.uk Queue: 3761bis Subject: REGEXP 'i' flag considered harmful Owner: Nobody Requestors: lconroy@insensate.co.uk Status: new Ticket RFC 3402 specifies an 'i' flag that can be applied to the REGEXP field. This flag is intended to make AUS matching case insensitive. For ENUM, this is not appropriate, as the allowed characters within an AUS are all case insensitive. However, the definition of the 'i' flag also states that the client MAY convert the generated output to lower case. Such optional behaviour is non-trivial where URI/IRIs are case sensitive (e.g. email addresses). [i.e. it is prone to mis-configuration] Also, for characters not in the US-ASCII equivalent range, case sensitivity may not make sense. For the match sub-field, this can cause confusion, but as mentioned this is irrelevant for ENUM as all characters in the match sub-field should be US-ASCII, and case insensitive already. Some languages have the concept of 'lower case', whilst others don't, and adding a suggestion that an IRI may be converted to lower case is not helpful in all cases. Finally, it is optional behaviour, and so the result from client to client is indeterminate. Option/Suggestion: At least for ENUM, state explicitly that the 'i' flag SHOULD NOT be used. atb, Lawrence _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 12:13:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNYo2-0000nx-5T; Sun, 26 Mar 2006 12:13:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNYo0-0000na-JJ for enum@ietf.org; Sun, 26 Mar 2006 12:13:32 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNYo0-0007sO-1Q for enum@ietf.org; Sun, 26 Mar 2006 12:13:32 -0500 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 26 Mar 2006 09:13:31 -0800 X-IronPort-AV: i="4.03,130,1141632000"; d="rtf'212?scan'212,208,212"; a="317576590:sNHT52876826" Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k2QHDVw1003056 for ; Sun, 26 Mar 2006 09:13:31 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2QHEC0j000784 for ; Sun, 26 Mar 2006 09:14:13 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) To: IETF ENUM WG Message-Id: Content-Type: multipart/mixed; boundary=Apple-Mail-55--270233488 References: <6EEEACD9D7F52940BEE26F5467C02C7302A3A6E8@PACDCEXCMB01.cable.comcast.com> From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Sun, 26 Mar 2006 19:13:27 +0200 X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=19504; t=1143393253; x=1143825453; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Final=20Rev=3A=20Attempt=20at=20Consensus=20on=20Carrier=20ENUM=20Questi ons |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3DeaTJdL7SifrPqMM/G/8F/dzoAG4=3D; b=kdKjb+8kJqzNVI0/ngZLGTIkKjQnJdjJeN0284IxC9YESMqGFCSs/OOIYwrytNuGJdo8oEuX 4yUqAvBxs/qsP6UWqMjmOnc2CZEfPiD18s9ixJRySL2Us2aW0yC9bwxfo8SZ8pNt8/O7Ne+JL4z Se8h1vvgb4ebFHv6z8yCGXD4=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( 36 extraneous bytes; message from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 96e0f8497f38c15fbfc8f6f315bcdecb Subject: [Enum] Final Rev: Attempt at Consensus on Carrier ENUM Questions 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 --Apple-Mail-55--270233488 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed FYI: The result of hard work by enthusiastic people in Dalls! Comments to the ENUM list. Patrik Begin forwarded message: > From: "Livingood, Jason" > Date: 23 mar 2006 21.57.47 GMT+01:00 > To: "Alexander Mayrhofer" > Cc: "Stastny Richard" , "Otmar Lendl" =20 > , "Richard Shockey" , Patrik =20 > F=E4ltstr=F6m , "Pfautz, Penn L, NEO" = , =20 > "Michael Haberler" , , =20 > > Subject: RE: Final Rev: Attempt at Consensus on Carrier ENUM Questions > > Here is a final copy of the Treaty of Dallas. Text below or RTF =20 > file attached. > > I will leave it up to our WG co-chairs or secretary to decide what =20 > to post to the list and minutes regarding this. > > Regards and safe travels, > > Jason > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Carrier/Infrastructure ENUM Points of Agreement -- 22 March 2006 > > 1. There will be a long-term solution that does things "right" as =20 > well as an interim solution that can be used by individual =20 > countries to implement an interoperable carrier ENUM tree ASAP. > > 2. In order to project a unified approach to the "right" long-term =20 > solution with other standards bodies and NRAs, there will be =20 > explicit statements in the affected I-Ds that make it clear that =20 > the interim solution will be deprecated upon achievement of the =20 > long-term solution. > > 3. There will be a new I-D documenting the carrier ENUM apex. This =20= > will be done in such a way that the location of the infrastructure =20 > designator shall not vary by country code; it will be the same for =20 > the entire domain and in every country code. The apex "e164i.arpa" =20= > was suggested, but that is tentative only. Everyone felt .arpa was =20= > certainly the correct TLD. This process will begin ASAP. > > 4. There will be an interim solution that will move ahead as an =20 > ENUM working group item ASAP, following the BLR logic and wording =20 > of the Michael Haberler's current I-D on this subject. However, =20 > some of the content which relates to DNS RRs in that draft will be =20 > split out into a different, new draft. > > 5. This interim solution will state prominently in the I-D, that =20 > this is in fact an interim solution that will be deprecated upon =20 > approval (loosely timed) of the "right" long-term solution. This =20 > will be at or near the beginning of such an I-D in a special =20 > section so that it can easily be located and will be noticed by =20 > readers. > > 6. This interim solution will not use a TXT RR, but a new RR type =20 > that will be moved ahead in the ENUM WG, with review and =20 > consultation from the appropriate DNS WG. > > 7. In summary, three I-Ds, all in the ENUM WG: document the long-=20 > term solution in a carrier-ENUM I-D in the ENUM WG with specifics =20 > around the new apex and solution, interim solution I-D in ENUM WG, =20 > other BLR/RR-related I-D in the ENUM WG. > > 8. Timing on new apex carrier ENUM I-D: create -00 ASAP as a WG =20 > item. Jason Livingood volunteers as document editor along with =20 > Penn Pfautz and Richard Stastny as co-authors. It should be noted =20 > that this I-D does not necessarily describe carrier ENUM =20 > requirements per se; it describes how to implement it in a specific =20= > domain apex. > > 9. Penn Pfautz's requirements I-D, already in process, should =20 > continue as-is and move to WGLC soon. > > 10. Timing on interim-solution I-D: add changes in updated =20 > haberler-03 I-D, then adopt as WG item and restart as -00. Move to =20= > WGLC at or before IETF 67. > > 11. Timing on BLR/RR-related I-D and new apex I-D: create new I-D =20= > ASAP. Move to WGLC at or before IETF 67. > > 12. All parties to this agreement will support this in good faith, =20= > in its entirety. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= --Apple-Mail-55--270233488 Content-Transfer-Encoding: quoted-printable Content-Type: application/rtf; x-unix-mode=0666; name="IETF 65 - Consensus Attempt - v5.rtf" Content-Disposition: attachment; filename="IETF 65 - Consensus Attempt - v5.rtf" {= \rtf1\ansi\ansicpg1252\uc1\deff0\stshfdbch0\stshfloch0\stshfhich0\stshfbi0= \deflang1033\deflangfe1033{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose=20= 02020603050405020304}Times=20New=20= Roman;}{\f1\fswiss\fcharset0\fprq2{\*\panose=20= 020b0604020202020204}Arial;}=0D=0A{\f37\froman\fcharset238\fprq2=20Times=20= New=20Roman=20CE;}{\f38\froman\fcharset204\fprq2=20Times=20New=20Roman=20= Cyr;}{\f40\froman\fcharset161\fprq2=20Times=20New=20Roman=20= Greek;}{\f41\froman\fcharset162\fprq2=20Times=20New=20Roman=20Tur;}=0D=0A= {\f42\froman\fcharset177\fprq2=20Times=20New=20Roman=20= (Hebrew);}{\f43\froman\fcharset178\fprq2=20Times=20New=20Roman=20= (Arabic);}{\f44\froman\fcharset186\fprq2=20Times=20New=20Roman=20= Baltic;}{\f45\froman\fcharset163\fprq2=20Times=20New=20Roman=20= (Vietnamese);}=0D=0A{\f47\fswiss\fcharset238\fprq2=20Arial=20= CE;}{\f48\fswiss\fcharset204\fprq2=20Arial=20= Cyr;}{\f50\fswiss\fcharset161\fprq2=20Arial=20= Greek;}{\f51\fswiss\fcharset162\fprq2=20Arial=20= Tur;}{\f52\fswiss\fcharset177\fprq2=20Arial=20(Hebrew);}=0D=0A= {\f53\fswiss\fcharset178\fprq2=20Arial=20= (Arabic);}{\f54\fswiss\fcharset186\fprq2=20Arial=20= Baltic;}{\f55\fswiss\fcharset163\fprq2=20Arial=20= (Vietnamese);}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\gr= een255\blue255;\red0\green255\blue0;=0D=0A= \red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255= \green255\blue255;\red0\green0\blue128;\red0\green128\blue128;\red0\green1= 28\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue= 0;\red128\green128\blue128;=0D=0A= \red192\green192\blue192;}{\stylesheet{\ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20\snext0=20= Normal;}{\*\cs10=20\additive=20\ssemihidden=20Default=20Paragraph=20= Font;}{\*=0D=0A= \ts11\tsrowd\trftsWidthB3\trpaddl108\trpaddr108\trpaddfl3\trpaddft3\trpadd= fb3\trpaddfr3\trcbpat1\trcfpat1\tscellwidthfts0\tsvertalt\tsbrdrt\tsbrdrl\= tsbrdrb\tsbrdrr\tsbrdrdgl\tsbrdrdgr\tsbrdrh\tsbrdrv=20=0D=0A\ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs20\lang1024\langfe1024\cgrid\langnp1024\langfenp1024=20\snext11=20= \ssemihidden=20Normal=20Table;}{\s15\ql=20\li0\ri0\widctlpar=0D=0A= \tqc\tx4320\tqr\tx8640\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20\sbasedon0=20= \snext15=20\styrsid12864632=20header;}{\s16\ql=20\li0\ri0\widctlpar=0D=0A= \tqc\tx4320\tqr\tx8640\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20\sbasedon0=20= \snext16=20\styrsid12864632=20= footer;}}{\*\latentstyles\lsdstimax156\lsdlockeddef0}{\*\rsidtbl=20= \rsid795888\rsid1136832=0D=0A= \rsid2252328\rsid2365517\rsid2574165\rsid2637038\rsid2843994\rsid3302557\r= sid3895842\rsid4654411\rsid4720324\rsid6493746\rsid7147699\rsid7888282\rsi= d9255124\rsid9388652\rsid9438505\rsid10879120\rsid11421389\rsid11565633\rs= id12206269\rsid12864632=0D=0A= \rsid13778387\rsid14116147\rsid14953292\rsid15039315}{\*\generator=20= Microsoft=20Word=2011.0.6359;}{\info{\title=20Carrier/Infrastructure=20= ENUM=20Points=20of=20Agreement=20}{\author=20Jason=20= Livingood}{\operator=20Jason=20= Livingood}{\creatim\yr2006\mo3\dy22\hr10\min43}=0D=0A= {\revtim\yr2006\mo3\dy22\hr17\min45}{\version22}{\edmins25}{\nofpages1}{\n= ofwords414}{\nofchars2360}{\*\company=20Comcast=20= Cable}{\nofcharsws2769}{\vern24703}}=0D=0A= \widowctrl\ftnbj\aenddoc\noxlattoyen\expshrtn\noultrlspc\dntblnsbdb\nospac= eforul\hyphcaps0\horzdoc\dghspace120\dgvspace120\dghorigin1701\dgvorigin19= 84\dghshow0\dgvshow3\jcompress\viewkind1\viewscale100\nolnhtadjtbl\rsidroo= t15039315=20\fet0{\*\ftnsep=20=0D=0A\pard\plain=20\ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\insrsid12864632=20\chftnsep=20=0D=0A\par=20}}{\*\ftnsepc=20\pard\plain=20= \ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\insrsid12864632=20\chftnsepc=20=0D=0A\par=20}}{\*\aftnsep=20= \pard\plain=20\ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\insrsid12864632=20\chftnsep=20=0D=0A\par=20}}{\*\aftnsepc=20= \pard\plain=20\ql=20= \li0\ri0\widctlpar\aspalpha\aspnum\faauto\adjustright\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\insrsid12864632=20\chftnsepc=20=0D=0A\par=20}}\sectd=20= \linex0\sectdefaultcl\sftnbj=20{\header=20\pard\plain=20\s15\ql=20= \li0\ri0\widctlpar\tqc\tx4320\tqr\tx8640\aspalpha\aspnum\faauto\adjustrigh= t\rin0\lin0\itap0=20= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\insrsid12864632=20IETF=2065=20\endash=20=0D=0A=20Dallas\tab=20\tab=20= ENUM=20WG=20Carrier=20ENUM=20Resolution=0D=0A\par=20= }}{\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang=20{\pntxta=20= .}}{\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang=20{\pntxta=20= .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang=20{\pntxta=20= .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang=20{\pntxta=20)}}=0D=0A= {\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang=20{\pntxtb=20(}{\pntxta=20= )}}{\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang=20{\pntxtb=20= (}{\pntxta=20)}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang=20= {\pntxtb=20(}{\pntxta=20)}}{\*\pnseclvl8=0D=0A= \pnlcltr\pnstart1\pnindent720\pnhang=20{\pntxtb=20(}{\pntxta=20= )}}{\*\pnseclvl9\pnlcrm\pnstart1\pnindent720\pnhang=20{\pntxtb=20= (}{\pntxta=20)}}\pard\plain=20\ql=20= \li0\ri0\sb100\sa100\nowidctlpar\faauto\rin0\lin0\itap0=20=0D=0A= \fs24\lang1033\langfe1033\cgrid\langnp1033\langfenp1033=20= {\f1\fs20\insrsid15039315\charrsid9255124=20Carrier/Infrastructure=20= ENUM=20Points=20of=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= Agreement=20--}{\f1\fs20\insrsid9255124\charrsid9255124=20=2022=20March=20= 2006}{=0D=0A\f1\fs20\insrsid15039315\charrsid9255124=20=0D=0A\par=201.=20= There=20}{\f1\fs20\insrsid11421389\charrsid9255124=20= will}{\f1\fs20\insrsid15039315\charrsid9255124=20=20be=20a=20long-term=20= solution=20that=20does=20things=20"right"=20as=20well=20as=20an=20= interim=20solution=20that=20can=20= }{\f1\fs20\insrsid13778387\charrsid9255124=20=0D=0Abe=20used=20by=20= individual=20countries=20to=20implement=20an=20interoperable=20carrier=20= ENUM=20tree=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= ASAP}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=0D=0A\par=202.=20= In=20order=20to=20project=20a=20unified=20approach=20to=20the=20"right"=20= long-term=20solution=20with=20other=20standards=20bodies=20and=20NRAs,=20= there=20}{\f1\fs20\insrsid11421389\charrsid9255124=20= will}{\f1\fs20\insrsid15039315\charrsid9255124=20=20be=20explicit=20s=0D=0A= tatements=20in=20the=20affected=20I-Ds=20that=20make=20it=20clear=20that=20= the=20interim=20solution=20will=20be=20deprecated=20upon=20achievement=20= of=20the=20long-term=20solution.=20=0D=0A\par=203.=20= }{\f1\fs20\insrsid4720324\charrsid9255124=20There=20will=20be=20a=20new=20= I-D=20documenting=20the=20carrier=20= }{\f1\fs20\insrsid2365517\charrsid9255124=20= ENUM}{\f1\fs20\insrsid4720324\charrsid9255124=20=20apex.=20=20= }{\f1\fs20\insrsid15039315\charrsid9255124=20=0D=0AThis=20will=20be=20= done=20in=20such=20a=20way=20that=20the=20location=20of=20the=20= infrastructure=20designator=20shall=20not=20vary=20by=20country=20code;=20= it=20will=20be=20the=20same=20for=20the=20entire=20domain=20and=20in=20= every=20country=20code}{\f1\fs20\insrsid2365517\charrsid9255124=20.=20=20= }{=0D=0A\f1\fs20\insrsid15039315\charrsid9255124=20The=20apex=20= "e164i.arpa"=20was=20suggest}{\f1\fs20\insrsid10879120\charrsid9255124=20= ed,=20but=20that=20is=20tentative=20= only}{\f1\fs20\insrsid2365517\charrsid9255124=20.=20=20= }{\f1\fs20\insrsid15039315\charrsid9255124=20=0D=0AEveryone=20felt=20= .arpa=20was=20certainly=20the=20correct=20= TLD}{\f1\fs20\insrsid2365517\charrsid9255124=20.=20=20= }{\f1\fs20\insrsid15039315\charrsid9255124=20This=20process=20will=20= begin=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= ASAP}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=0D=0A=0D=0A\par=20= 4.=20There=20will=20be=20an=20interim=20solution=20that=20will=20move=20= ahead=20as=20}{\f1\fs20\insrsid4654411\charrsid9255124=20an=20= ENUM}{\f1\fs20\insrsid15039315\charrsid9255124=20=20working=20group=20= item=20}{\f1\fs20\insrsid2365517\charrsid9255124=20ASAP}{=0D=0A= \f1\fs20\insrsid15039315\charrsid9255124=20,=20following=20the=20BLR=20= logic=20and=20}{\f1\fs20\insrsid9388652\charrsid9255124=20= wording}{\f1\fs20\insrsid15039315\charrsid9255124=20=20of=20the=20= Michael}{\f1\fs20\insrsid4654411\charrsid9255124=20=20Haberler}{=0D=0A= \f1\fs20\insrsid15039315\charrsid9255124=20's=20current=20I-D=20on=20= this=20subject}{\f1\fs20\insrsid2365517\charrsid9255124=20.=20=20= }{\f1\fs20\insrsid15039315\charrsid9255124=20However,=20some=20of=20the=20= content}{\f1\fs20\insrsid4654411\charrsid9255124=20=20which=20relates=20= to=20DNS=20RRs}=0D=0A{\f1\fs20\insrsid15039315\charrsid9255124=20=20in=20= that=20draft=20will=20be=20split=20out=20into=20a=20= different}{\f1\fs20\insrsid4654411\charrsid9255124=20,=20= new}{\f1\fs20\insrsid15039315\charrsid9255124=20=20draft.=20=0D=0A\par=20= 5.=20This=20interim=20solution=20will=20state=20prominently=20in=20the=20= I-D,=20that=20this=20is=20in=20fact=20an=20interim=20solution=20that=20= will=20be=20deprecated=20upon=20approval=20(loosely=20timed)=20of=20the=20= "right"=20long-term=20solution}{\f1\fs20\insrsid2365517\charrsid9255124=20= .=20=20}{=0D=0A\f1\fs20\insrsid15039315\charrsid9255124=20This=20= }{\f1\fs20\insrsid3302557\charrsid9255124=20= will}{\f1\fs20\insrsid15039315\charrsid9255124=20=0D=0A=20be=20at=20or=20= near=20the=20beginning=20of=20such=20an=20I-D=20in=20a=20special=20= section=20so=20that=20it=20can=20easily=20be=20located=20and=20will=20be=20= noticed=20by=20readers.=20=0D=0A\par=206.=20This=20interim=20solution=20= will=20not=20use=20a=20TXT=20RR,=20but=20a=20new=20RR=20type=20that=20= will=20be=20moved=20ahead=20in=20= }{\f1\fs20\insrsid3895842\charrsid9255124=20the=20ENUM=20= WG}{\f1\fs20\insrsid12206269\charrsid9255124=20,=20with=20review=20and=20= consultation=20}{=0D=0A\f1\fs20\insrsid3895842\charrsid9255124=20from=20= the=20appropriate=20DNS=20WG}{\f1\fs20\insrsid15039315\charrsid9255124=20= .=0D=0A\par=207.=20=20In=20summary,=20= }{\f1\fs20\insrsid2574165\charrsid9255124=20= three}{\f1\fs20\insrsid15039315\charrsid9255124=20=20= I-Ds}{\f1\fs20\insrsid14953292\charrsid9255124=20,=20all=20in=20the=20= ENUM=20WG}{\f1\fs20\insrsid15039315\charrsid9255124=20:=20}{=0D=0A= \f1\fs20\insrsid4720324\charrsid9255124=20document=20= the}{\f1\fs20\insrsid15039315\charrsid9255124=20=20long-term=20solution=20= }{\f1\fs20\insrsid4720324\charrsid9255124=20in=20= a}{\f1\fs20\insrsid15039315\charrsid9255124=20=20= carrier-}{\f1\fs20\insrsid2365517\charrsid9255124=20=0D=0A= ENUM}{\f1\fs20\insrsid15039315\charrsid9255124=20=20I-D=20in=20the=20= ENUM=20WG=20with=20specifics=20around=20the=20new=20apex=20and=20= solution,=20interim=20solution=20I-D=20in=20ENUM=20WG,=20other=20= BLR/RR-related=20I-D=20}{\f1\fs20\insrsid2637038\charrsid9255124=20in=20= }{=0D=0A\f1\fs20\insrsid15039315\charrsid9255124=20the=20ENUM=20WG.=0D=0A= \par=20}{\f1\fs20\insrsid4720324\charrsid9255124=20= 8}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=20Timing=20on=20new=20= apex=20carrier=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= ENUM}{\f1\fs20\insrsid15039315\charrsid9255124=20=20I-D:=20create=20-00=20= }{=0D=0A\f1\fs20\insrsid2365517\charrsid9255124=20= ASAP}{\f1\fs20\insrsid15039315\charrsid9255124=20=20as=20a=20WG=20item.=20= =20}{\f1\fs20\insrsid14953292\charrsid9255124=20Jason=20= Livingood}{\f1\fs20\insrsid15039315\charrsid9255124=20=20volunteer}{=0D=0A= \f1\fs20\insrsid14953292\charrsid9255124=20= s}{\f1\fs20\insrsid15039315\charrsid9255124=20=20as=20document=20editor=20= along=20with=20Penn=20}{\f1\fs20\insrsid14953292\charrsid9255124=20= Pfautz=20and=20Richard=20= Stastny}{\f1\fs20\insrsid11565633\charrsid9255124=20=20as=20co-authors}{=0D= =0A\f1\fs20\insrsid15039315\charrsid9255124=20.=20=20It=20should=20be=20= noted=20that=20this=20I-D=20does=20not=20necessarily=20describe=20= carrier=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= ENUM}{\f1\fs20\insrsid15039315\charrsid9255124=20=20requirements=20per=20= se;=20it=20describes=20how=20to=20implement=0D=0A= }{\f1\fs20\insrsid2252328\charrsid9255124=20=20it=20in=20a=20specific=20= domain=20apex.=0D=0A\par=209.=20=20Penn=20Pfautz's=20= }{\f1\fs20\insrsid15039315\charrsid9255124=20requirements=20= I-D}{\f1\fs20\insrsid1136832\charrsid9255124=20= ,}{\f1\fs20\insrsid15039315\charrsid9255124=20=20already=20in=20= process}{\f1\fs20\insrsid1136832\charrsid9255124=20,}{=0D=0A= \f1\fs20\insrsid15039315\charrsid9255124=20=20should=20= continue}{\f1\fs20\insrsid2252328\charrsid9255124=20=20as-is=20and=20= move=20to=20WGLC=20soon}{\f1\fs20\insrsid15039315\charrsid9255124=20.=0D=0A= \par=20}{\f1\fs20\insrsid2252328\charrsid9255124=20= 10}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=20Timing=20on=20= interim-solution=20I-D:=20add=20changes=20in=20updated=20haberler-03=20= I-D,=20then=20adopt=20as=20WG=20item=20and=20restart=20as=20-00.=20=20= Move=20to=20WGLC=20at=20or=20before=20IETF=2067.=0D=0A\par=20}\pard=20= \ql=20= \li0\ri0\sb100\sa100\nowidctlpar\faauto\rin0\lin0\itap0\pararsid7147699=20= {\f1\fs20\insrsid2252328\charrsid9255124=20= 11}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=20Timing=20on=20= BLR/RR-related=20I-D}{\f1\fs20\insrsid7147699\charrsid9255124=20=0D=0A=20= and=20new=20apex=20I-D}{\f1\fs20\insrsid15039315\charrsid9255124=20:=20=20= create=20new=20I-D=20}{\f1\fs20\insrsid2365517\charrsid9255124=20= ASAP}{\f1\fs20\insrsid15039315\charrsid9255124=20.=20=20= Move}{\f1\fs20\insrsid7147699\charrsid9255124=20=20to=20WGLC=20at=20or=20= before=20IETF=2067.=0D=0A\par=20}\pard=20\ql=20= \li0\ri0\sb100\sa100\nowidctlpar\faauto\rin0\lin0\itap0=20= {\f1\fs20\insrsid7147699\charrsid9255124=20= 12}{\f1\fs20\insrsid2843994\charrsid9255124=20.=20=20All=20parties=20to=20= this=20agreement=20will=20support=20this=20in=20good=20faith,=20in=20its=20= entirety.=0D=0A\par=20}\pard=20\ql=20= \li0\ri0\nowidctlpar\faauto\rin0\lin0\itap0=20{\f1\fs20\insrsid15039315=20= =0D=0A\par=20}{\f1\fs20\insrsid9255124=20Signed=20and=20Agreed,=20= }{\f1\fs20\insrsid9255124\charrsid9255124=20=0D=0A\par=20}}= --Apple-Mail-55--270233488 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed --Apple-Mail-55--270233488 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 --Apple-Mail-55--270233488-- From enum-bounces@ietf.org Sun Mar 26 14:57:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNbMo-0002Ie-S5; Sun, 26 Mar 2006 14:57:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNbMm-0002IS-MZ for enum@ietf.org; Sun, 26 Mar 2006 14:57:36 -0500 Received: from test-iport-1.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNbMk-00065r-Di for enum@ietf.org; Sun, 26 Mar 2006 14:57:36 -0500 Received: from sj-core-2.cisco.com ([171.71.177.254]) by test-iport-1.cisco.com with ESMTP; 26 Mar 2006 11:57:34 -0800 Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k2QJvXGv011981 for ; Sun, 26 Mar 2006 11:57:33 -0800 (PST) Received: from [127.0.0.1] (ssh-ams-1.cisco.com [144.254.226.40]) by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k2QJwFfk001325 for ; Sun, 26 Mar 2006 11:58:15 -0800 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: <44E2D438-488D-480B-B3AC-FCF335A4E5E6@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: IETF ENUM WG From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Date: Sun, 26 Mar 2006 21:57:30 +0200 X-Mailer: Apple Mail (2.749.3) DKIM-Signature: a=rsa-sha1; q=dns; l=1216; t=1143403096; x=1143835296; c=relaxed/simple; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding:Mime-Version; d=cisco.com; i=paf@cisco.com; z=From:=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:Instructions=20for=20how=20to=20help=20with=20RFC=203761bis |To:IETF=20ENUM=20WG=20; X=v=3Dmtcc.com=3B=20h=3Da+VNybPp5UqVBxjLGqYV1ip5nqk=3D; b=MYl8qrbdVWnCeclhlNlubetCrbgNAJ0DjgszCu1OO5jLXBUYXO0RREtkDmOB7TORo/F7sqW5 ZrLErWlczErwdXcw8FmEf+Mqb/n5eZ34Npf9G2pNk4WiqreiHOBFBiwveqbnHQo+Y3zJ43XV7J8 77u9rTu66ZNtGxALIom8J4t4=; Authentication-Results: imail.cisco.com; header.From=paf@cisco.com; dkim=pass ( message from cisco.com verified; ); X-Spam-Score: 0.5 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Subject: [Enum] Instructions for how to help with RFC 3761bis 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 People have privately sent me questions on this "ticket system". Question one: Where can I get a copy of RFC3761bis? Answer: It doesn't exist yet. I am collecting "issues" that we need to solve. Question two: If there is something I think should be added, how do I make sure you remember it? Answer: Write a note in english, and send it to the address 3761bis@frobbit.se. A ticket will automatically be created, and a notification sent to the ENUM mailing list. Question 3: If I don't agree with an issue, or want to add comments, how do I do? Answer: Either go to the website, and add information about the ticket, or reply to the mail sent to the ENUM mailing list. The response only have to be sent to 3761bis@frobbit.se. It is very important the subject line is not changed. It includes the ticket number. Question 4: Can I see all issues that are not yet taken care of? Answer: Go to the website and look at the tickets. Question 5: What was the URI, login etc? Answer: You can access the web via http://ticket.frobbit.se/ (or using SSL to https://dav.frobbit.se:445/), log in with the username "3761bis" and password "ietf-enum". Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Sun Mar 26 15:09:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNbYB-00089a-M2; Sun, 26 Mar 2006 15:09:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNbYA-00088E-1H for enum@ietf.org; Sun, 26 Mar 2006 15:09:22 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNbY6-0006Zm-Ic for enum@ietf.org; Sun, 26 Mar 2006 15:09:22 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2QK9G2L079898; Sun, 26 Mar 2006 22:09:16 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2QK9Fdc079897; Sun, 26 Mar 2006 22:09:15 +0200 (CEST) (envelope-from www) Date: Sun, 26 Mar 2006 22:09:15 +0200 (CEST) From: "Stastny Richard via RT" <3761bis@frobbit.se> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C4938@oefeg-s04.oefeg.loc> References: <32755D354E6B65498C3BD9FD496C7D462C4938@oefeg-s04.oefeg.loc> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #875 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: Richard.Stastny@oefeg.at Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [Enum] [ticket.frobbit.se #875] Only one Enumservice per NAPTR X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Sun Mar 26 22:09:15 2006: Request 875 was acted upon. Transaction: Ticket created by Richard.Stastny@oefeg.at Queue: 3761bis Subject: Only one Enumservice per NAPTR Owner: Nobody Requestors: Richard.Stastny@oefeg.at Status: new Ticket the syntax for Enumservices given in RFC3761 allows for more then one Enumservice to be given, by addiing them with a '+' (i) this function is rareley used at all (ii) it is feasable only for Enumservices resulting in the same URI, so it may even be used wrongly It is therefor proposed to use only one Enumservice per NAPTR Richard _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 27 06:12:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNpeQ-0001Io-R3; Mon, 27 Mar 2006 06:12:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNpeP-0001HB-FO for enum@ietf.org; Mon, 27 Mar 2006 06:12:45 -0500 Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FNpeO-0000hh-Ub for enum@ietf.org; Mon, 27 Mar 2006 06:12:45 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Enum] Final Rev: Attempt at Consensus on Carrier ENUM Questions Date: Mon, 27 Mar 2006 13:16:42 +0200 Message-ID: <32755D354E6B65498C3BD9FD496C7D463C4E72@oefeg-s04.oefeg.loc> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Enum] Final Rev: Attempt at Consensus on Carrier ENUM Questions Thread-Index: AcZQ+UD0zX+C9oOSTnugXBCbMVXKjwAlmx8Q From: "Stastny Richard" To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= , "IETF ENUM WG" X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f 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 Patrik and all, Thank you very much and I apologize by everybody for any insults made. Regards Richard Stastny > -----Original Message----- > From: Patrik F=E4ltstr=F6m [mailto:paf@cisco.com] > Sent: Sunday, March 26, 2006 7:13 PM > To: IETF ENUM WG > Subject: [Enum] Final Rev: Attempt at Consensus on Carrier ENUM = Questions >=20 > FYI: The result of hard work by enthusiastic people in Dalls! >=20 > Comments to the ENUM list. >=20 > Patrik >=20 > Begin forwarded message: >=20 > > From: "Livingood, Jason" > > Date: 23 mar 2006 21.57.47 GMT+01:00 > > To: "Alexander Mayrhofer" > > Cc: "Stastny Richard" , "Otmar Lendl" > > , "Richard Shockey" , Patrik > > F=E4ltstr=F6m , "Pfautz, Penn L, NEO" = , > > "Michael Haberler" , , > > > > Subject: RE: Final Rev: Attempt at Consensus on Carrier ENUM = Questions > > > > Here is a final copy of the Treaty of Dallas. Text below or RTF > > file attached. > > > > I will leave it up to our WG co-chairs or secretary to decide what > > to post to the list and minutes regarding this. > > > > Regards and safe travels, > > > > Jason > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Carrier/Infrastructure ENUM Points of Agreement -- 22 March 2006 > > > > 1. There will be a long-term solution that does things "right" as > > well as an interim solution that can be used by individual > > countries to implement an interoperable carrier ENUM tree ASAP. > > > > 2. In order to project a unified approach to the "right" long-term > > solution with other standards bodies and NRAs, there will be > > explicit statements in the affected I-Ds that make it clear that > > the interim solution will be deprecated upon achievement of the > > long-term solution. > > > > 3. There will be a new I-D documenting the carrier ENUM apex. This > > will be done in such a way that the location of the infrastructure > > designator shall not vary by country code; it will be the same for > > the entire domain and in every country code. The apex "e164i.arpa" > > was suggested, but that is tentative only. Everyone felt .arpa was > > certainly the correct TLD. This process will begin ASAP. > > > > 4. There will be an interim solution that will move ahead as an > > ENUM working group item ASAP, following the BLR logic and wording > > of the Michael Haberler's current I-D on this subject. However, > > some of the content which relates to DNS RRs in that draft will be > > split out into a different, new draft. > > > > 5. This interim solution will state prominently in the I-D, that > > this is in fact an interim solution that will be deprecated upon > > approval (loosely timed) of the "right" long-term solution. This > > will be at or near the beginning of such an I-D in a special > > section so that it can easily be located and will be noticed by > > readers. > > > > 6. This interim solution will not use a TXT RR, but a new RR type > > that will be moved ahead in the ENUM WG, with review and > > consultation from the appropriate DNS WG. > > > > 7. In summary, three I-Ds, all in the ENUM WG: document the long- > > term solution in a carrier-ENUM I-D in the ENUM WG with specifics > > around the new apex and solution, interim solution I-D in ENUM WG, > > other BLR/RR-related I-D in the ENUM WG. > > > > 8. Timing on new apex carrier ENUM I-D: create -00 ASAP as a WG > > item. Jason Livingood volunteers as document editor along with > > Penn Pfautz and Richard Stastny as co-authors. It should be noted > > that this I-D does not necessarily describe carrier ENUM > > requirements per se; it describes how to implement it in a specific > > domain apex. > > > > 9. Penn Pfautz's requirements I-D, already in process, should > > continue as-is and move to WGLC soon. > > > > 10. Timing on interim-solution I-D: add changes in updated > > haberler-03 I-D, then adopt as WG item and restart as -00. Move to > > WGLC at or before IETF 67. > > > > 11. Timing on BLR/RR-related I-D and new apex I-D: create new I-D > > ASAP. Move to WGLC at or before IETF 67. > > > > 12. All parties to this agreement will support this in good faith, > > in its entirety. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Mar 27 09:37:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNspv-0005qJ-4s; Mon, 27 Mar 2006 09:36:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNspt-0005qE-CM for enum@ietf.org; Mon, 27 Mar 2006 09:36:49 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNspr-0000wA-Q2 for enum@ietf.org; Mon, 27 Mar 2006 09:36:49 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2REajo0083750 for ; Mon, 27 Mar 2006 16:36:45 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2REajpc083749; Mon, 27 Mar 2006 16:36:45 +0200 (CEST) (envelope-from www) Date: Mon, 27 Mar 2006 16:36:45 +0200 (CEST) From: "Stastny Richard via RT" <3761bis@frobbit.se> In-Reply-To: <32755D354E6B65498C3BD9FD496C7D462C493C@oefeg-s04.oefeg.loc> References: <32755D354E6B65498C3BD9FD496C7D462C493C@oefeg-s04.oefeg.loc> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #875 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: Richard.Stastny@oefeg.at Cc: enum@ietf.org MIME-Version: 1.0 X-RT-Original-Encoding: utf-8 Content-type: multipart/mixed; boundary="----------=_1143470204-74253-2" X-Spam-Score: 0.0 (/) X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365 Subject: [Enum] Re: [ticket.frobbit.se #875] Only one Enumservice per NAPTR X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format... ------------=_1143470204-74253-2 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Ok, I was not aware of this. This was only a proposal for discussion, so the ticket may be closed Richard ________________________________ Von: via RT [mailto:3761bis@frobbit.se] Gesendet: Mo 27.03.2006 01:06 Cc: Stastny Richard Betreff: [ticket.frobbit.se #875] Only one Enumservice per NAPTR > (i) this function is rareley used at all > (ii) it is feasable only for Enumservices resulting in the same URI, so it may even be used wrongly > > It is therefor proposed to use only one Enumservice per NAPTR To which I counter-propose: over my dead and smoking body! Seriously, folks, we already use complex NAPTRs in our provisioning systems and clients. Mobile phones are a natural for this - voice:tel+sms:tel. If people don't want to use complex NAPTRs, they don't have to do this, but it is convenient for handyphones. ------------=_1143470204-74253-2 Content-Type: application/ms-tnef; name="winmail.dat" Content-Disposition: inline; filename="winmail.dat" Content-Transfer-Encoding: base64 RT-Attachment: 875/7734/4978 eJ8+Ih8OAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNyb3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEE gAEAPQAAAFJlOiBbdGlja2V0LmZyb2JiaXQuc2UgIzg3NV0gT25seSBvbmUg RW51bXNlcnZpY2UgcGVyIE5BUFRSIABGFAEFgAMADgAAANYHAwAbABAAJwAO AAEAQQEBIIADAA4AAADWBwMAGwAQACgAHgABAFIBAQmAAQAhAAAAREY2RjY4 RkQ2M0ExQ0Y0MkE2NTFBMEFGNDYzNDExNkUASwcBA5AGAAQOAAA3AAAAAwA2 AAAAAABAADkARWJwOKxRxgEeAD0AAQAAAAUAAABSZTogAAAAAAIBRwABAAAA MAAAAGM9dXM7YT0gO3A9T0VGRUc7bD1PRUZFRy1TMDQtMDYwMzI3MTQ0MDMw Wi0yMzg2AB4ASQABAAAAOQAAAFt0aWNrZXQuZnJvYmJpdC5zZSAjODc1XSBP bmx5IG9uZSBFbnVtc2VydmljZSBwZXIgTkFQVFIgAAAAAEAATgCAdU/rKVHG AR4AWgABAAAACAAAACB2aWEgUlQAAgFbAAEAAAA4AAAAAAAAAIErH6S+oxAZ nW4A3QEPVAIAAAAAIHZpYSBSVABTTVRQADM3NjFiaXNAZnJvYmJpdC5zZQAC AVwAAQAAABgAAABTTVRQOjM3NjFCSVNARlJPQkJJVC5TRQAeAF0AAQAAAAgA AAAgdmlhIFJUAAIBXgABAAAAOAAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAA ACB2aWEgUlQAU01UUAAzNzYxYmlzQGZyb2JiaXQuc2UAAgFfAAEAAAAYAAAA U01UUDozNzYxQklTQEZST0JCSVQuU0UAHgBmAAEAAAAFAAAAU01UUAAAAAAe AGcAAQAAABMAAAAzNzYxYmlzQGZyb2JiaXQuc2UAAB4AaAABAAAABQAAAFNN VFAAAAAAHgBpAAEAAAATAAAAMzc2MWJpc0Bmcm9iYml0LnNlAAAeAHAAAQAA ADkAAABbdGlja2V0LmZyb2JiaXQuc2UgIzg3NV0gT25seSBvbmUgRW51bXNl cnZpY2UgcGVyIE5BUFRSIAAAAAACAXEAAQAAABsAAAABxlEqfFihyo4JpUtN 8I1jlxEV/VxnACBvBvgAHgBzAAEAAAAQAAAAU3Rhc3RueSBSaWNoYXJkAB4A GgwBAAAAEAAAAFN0YXN0bnkgUmljaGFyZAAeAB0OAQAAADkAAABbdGlja2V0 LmZyb2JiaXQuc2UgIzg3NV0gT25seSBvbmUgRW51bXNlcnZpY2UgcGVyIE5B UFRSIAAAAAACAQkQAQAAAEEHAAA9BwAAvhcAAExaRnUIQ7d9AwAKAHJjcGcx MjWCMgNDaHRtbDEDMD8BAwH3CoACpAPjAgBjaMEKwHNldDAgBxMCgP8QAwBQ BFYIVQeyEdUOUQMB3RDXMgYABsMR1TMERhDZWRLvZjQDxhGKNQPGVHxhaANx AoAR4wjvCfc7ext/DjA1HJ8ccRHhDGBjZwBQCwkBZDM2EWALpTSyIBACKlwO sgGQZxTwFwqjEeMhyDQU8DwhRABPQ1RZUEUgSABUTUwgUFVCTABJQyAiLS8v V0QzQyVgRFREJHQzhC4yJWBFTiI+Is3zIm8noTE4I9AkgibvJ/+NKnAzIWAp UEVBRCmtLw7xKs8tTyjUNg7wPE0oRVRBB7BBMEA9IqZHCfAEkGF0BbAiFxBo T05UJrBUMNAF4UWieBDxbmdlBlJ2EzEHMyEAkAIgIDYuNS51AcAyM+AwJt4u ryjjN4I3I9BUSVRMRSmuUjQO8Ft0DeBrEUAuMQNRYmJpOQARMCAjADg3NV0g T25sDHkgAiAy0EVudW0vETAzEA3gMtBwEzJBUNRUUig/NSPQLzcvNV+/KiU4 cT1ALC8qf0EUNRFg4DxCT0RZQI0g0UGvCGc5NiPQRElWIAhpZD1GAE9XQVIC ZQtQeVRleHQ3CDMyMxFgZGlyPd1BMHJAgEDzACEgAABHsecKsUiiEPBccQMh SBURYH9Db0R/RYZHf0iPSZpAyTauNE16Sc8o1DQpMUYxsaQgZgDQZT0HEyAa 86g9IzBUgyAAkHpTkO4yTWsYMAMwYxPwA7IB0AFJqU9rLCBJIHfSYQQgbm8F QGFYAB4ATzpwTfA/LEs1dGgEAC71KFw1RZEvUxJNaU13T7u/AcBNdwqiXNgK gChcMCvx/yXARdBcL1GvSx9ML00/Tk//XQ9Qb2IvUo9TllT/VgRWvS9av1vP Yf9BBTghYCZuGGJzcAKAZddcJ2H/AUBnn14PXx9gL2E/cT9jX/9kb2V/Zo9z 72iveQ9qz2vfe2zvVttUWnFX8wIgOlFh4ztwA2Bwb3NT4QIQBcA7fDAE8HUE EDOhV8Bzb29ZD1oVMtA4tCAAwDpgYu0y0GMbEBEwZG7Pb99c3/9033Xvdv94 D4C/ei97P3xP/31ffm9/f4CPgZ+Cr4O/bd//i2+Mf57Pch9zL43fju+P//+R D6EPky+UP5VPll+Xb5h/v5mPqe+br5y/nc+xRlIN4P8RAYs/oF+NX6Vfpm+n f6iP/7E/vG+9f6oPqx+sL60/rk/vwR8OEA4gQuFSxHkKogqBN8Zfwe/C+0g8 AAGRSW5hAQB4PS0xtEwAUHGJAOBxagxgbGRiAzB4fiBfzvLOscUwC4Bl/7rj yR/KLq+vsL+xz7LZGiT/s99V8j0gnl+iPULwxHvOobXYR1YCIDrLLCPBL9nq f7jZM1AHMAfwU0CIf8riW8cAwAMQMVA6MzcwADlg9HNAOShdxu1FkcgMz4J/ 0B/ZL9o/5JIw8BEwzKF0l9u/3M/d102IUDI3NGAfJmFUgEWQ3t/K4jAxOn/r YOHf4u/j/+UP5h/v1EMuY+gP6R/d11MBkHN0/m46YLZP7d/u7+//8Q/au/5C EUAeAAEg8w/0H93XOK//Obbrn8riOj87TPav97/4z/+277f/Bs8E3wXvuT+6 T7tf/78vCO/Qv8rPRWfEexGvEr/70kkj0FDILxWIFO8J77KnT9Z/zcHX/6Jc Z3SjeT4x3bkoaSmJ8IXCZnV8bmP/gDOxhdExMPyAbD5l9hCHwIsgWHBYYWxs /wofCy8Gbx9PIF8hZSHBAEDnIsIBDxcyZmVYEMxwI0D/hjSHQgLpIuHnkM5w /4AysC9F8DPAicKHAG0y0FVS7kmIIyohinJlMyAzwIqx9yODKo8XMneGwC4w hmAkP/8lTyZfJ28ofzVvov+kDjKv3zO/NM813zbv3hNJKjOJwf/8gYdRhrQj oeBwI3KGNAKi/zDvFzIC7wPyOx88Lz0/Rg/rRx9IKVSIUHdacPZQV9GrVBAi UHQDMC1BpToCkNswIAPAbfYQ59BhI7HMoENDLxcjc21vay4iYvBvZHkhSN9J 70f/UP/7Ug9TGVMDMCKQh8CGYIgg0YdAbGtziCB3LwCHEE/8gE4wI2NMcW1w I0B4/wPUhiAuYUyQA8BOrxcyhrGn3mCH4i4ic3n14GVEsItOU4rgaeewdHMu U8/fVN9S7Oqw4WAsMXDWIAKw91yx/ICGgW4j0FoAhxUh86YtWi8XI3ZvA2E6 TMD0bCtP8HNkol2PXp9S3V5JxQADoIbQLDFkIqAn/yowhgBMsEImWNyIIInB TfH/aSNjDxcy9mAwIEIiaRAh47mIIGJ1KjEqM0yAbjAh310yhzNr72z0zKB5 YQRlb/9mf1Lfcg9zH3QvB58Irxns/w5+GL93bw2E/cEYgQ9/EI9vfS8Wn4IP F2w1srH94E+8RFl+/f2whB+GoTf9wVBIVE1MdiB9iNAAAAAeADUQAQAAAD0A AAA8MzI3NTVEMzU0RTZCNjU0OThDM0JEOUZENDk2QzdENDYyQzQ5M0NAb2Vm ZWctczA0Lm9lZmVnLmxvYz4AAAAAHgBHEAEAAAAPAAAAbWVzc2FnZS9yZmM4 MjIAAAsA8hABAAAAHwDzEAEAAACIAAAAUgBlACUAMwBBACAAWwB0AGkAYwBr AGUAdAAuAGYAcgBvAGIAYgBpAHQALgBzAGUAIAAlADIAMwA4ADcANQBdACAA TwBuAGwAeQAgAG8AbgBlACAARQBuAHUAbQBzAGUAcgB2AGkAYwBlACAAcABl AHIAIABOAEEAUABUAFIALgBFAE0ATAAAAAsA9hAAAAAAQAAHMEVicDisUcYB QAAIMKXqlmWsUcYBAwDeP69vAAADAPE/BwwAAB4A+D8BAAAAEAAAAFN0YXN0 bnkgUmljaGFyZAACAfk/AQAAAFkAAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEA AAAAAAAAL089T0VGRUcvT1U9RVJTVEUgQURNSU5JU1RSQVRJVkUgR1JVUFBF L0NOPVJFQ0lQSUVOVFMvQ049U1RBAAAAAB4A+j8BAAAAFQAAAFN5c3RlbSBB ZG1pbmlzdHJhdG9yAAAAAAIB+z8BAAAAHgAAAAAAAADcp0DIwEIQGrS5CAAr L+GCAQAAAAAAAAAuAAAAAwD9P+QEAAADABlAAAAAAAMAGkAAAAAAAwAdQAAA AAADAB5AAAAAAB4AMEABAAAABAAAAFNUQQAeADFAAQAAAAQAAABTVEEAHgAy QAEAAAATAAAAMzc2MWJpc0Bmcm9iYml0LnNlAAAeADNAAQAAABMAAAAzNzYx YmlzQGZyb2JiaXQuc2UAAB4AOEABAAAABAAAAFNUQQAeADlAAQAAAAIAAAAu AAAAAwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAGEKoIwOQDAAcQegIAAAMA EBAAAAAAAwAREAEAAAAeAAgQAQAAAGUAAABPSyxJV0FTTk9UQVdBUkVPRlRI SVNUSElTV0FTT05MWUFQUk9QT1NBTEZPUkRJU0NVU1NJT04sU09USEVUSUNL RVRNQVlCRUNMT1NFRFJJQ0hBUkRWT046VklBUlRNQUlMVE86AAAAAAIBfwAB AAAAPQAAADwzMjc1NUQzNTRFNkI2NTQ5OEMzQkQ5RkQ0OTZDN0Q0NjJDNDkz Q0BvZWZlZy1zMDQub2VmZWcubG9jPgAAAADkXw== ------------=_1143470204-74253-2 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 ------------=_1143470204-74253-2-- From enum-bounces@ietf.org Mon Mar 27 14:44:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNxcr-0007JS-Sz; Mon, 27 Mar 2006 14:43:41 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNxcq-0007JN-Sn for enum@ietf.org; Mon, 27 Mar 2006 14:43:40 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNxcp-0005zL-D9 for enum@ietf.org; Mon, 27 Mar 2006 14:43:40 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2RJhbNo084913; Mon, 27 Mar 2006 21:43:37 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2RJhakb084912; Mon, 27 Mar 2006 21:43:36 +0200 (CEST) (envelope-from www) Date: Mon, 27 Mar 2006 21:43:36 +0200 (CEST) Subject: Re: [Enum] Re: [ticket.frobbit.se #875] Only one Enumservice per NAPTR From: "=?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= via RT" <3761bis@frobbit.se> In-Reply-To: References: <32755D354E6B65498C3BD9FD496C7D462C493C@oefeg-s04.oefeg.loc> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #875 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: paf@cisco.com To: Richard.Stastny@oefeg.at MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On 27 mar 2006, at 16.36, Stastny Richard via RT wrote: > Ok, I was not aware of this. > > This was only a proposal for discussion, so the ticket may be closed As you didn't know about this, I will let the ticket stay open. Possibly some clarifying words / examples are needed in 3761bis. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Tue Mar 28 03:15:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FO9M1-00044k-SG; Tue, 28 Mar 2006 03:15:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FO9L6-0002Xf-KQ for enum@ietf.org; Tue, 28 Mar 2006 03:14:08 -0500 Received: from charles.frobbit.se ([85.30.129.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FO96h-0004l3-9m for enum@ietf.org; Tue, 28 Mar 2006 02:59:18 -0500 Received: from charles.frobbit.se (localhost [127.0.0.1]) by charles.frobbit.se (8.13.4/8.13.4) with ESMTP id k2S7xClF087242; Tue, 28 Mar 2006 09:59:13 +0200 (CEST) (envelope-from www@charles.frobbit.se) Received: (from www@localhost) by charles.frobbit.se (8.13.4/8.12.10/Submit) id k2S7xCdc087241; Tue, 28 Mar 2006 09:59:12 +0200 (CEST) (envelope-from www) Date: Tue, 28 Mar 2006 09:59:12 +0200 (CEST) From: "Alexander Mayrhofer via RT" <3761bis@frobbit.se> In-Reply-To: <4428ECB8.6010802@enum.at> References: <4428ECB8.6010802@enum.at> Message-ID: Precedence: bulk X-RT-Loop-Prevention: ticket.frobbit.se RT-Ticket: ticket.frobbit.se #878 Managed-by: RT 3.4.4 (http://www.bestpractical.com/rt/) RT-Originator: alexander.mayrhofer@enum.at Cc: enum@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-RT-Original-Encoding: utf-8 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [Enum] [ticket.frobbit.se #878] experimental ENUM services - clash prevention X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Reply-To: 3761bis@frobbit.se List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Tue Mar 28 09:59:12 2006: Request 878 was acted upon. Transaction: Ticket created by alexander.mayrhofer@enum.at Queue: 3761bis Subject: experimental ENUM services - clash prevention Owner: Nobody Requestors: alexander.mayrhofer@enum.at Status: new Ticket because of the cumbersome process of ENUMservice registration, more and more experimental services are popping up. Contrary to it's intended purpose, more and more of those services are used "de facto" not only internally, but between different parties. This increases the risk of collisions between several different implementations of "experimental" ENUMservices, hence creating the need for preventing collisions between those services. I'm envisaging a process where the name and service of such experimental services (or probably a new class of "draft services") would be registered in a very lightweight way, just for preventing clashes between them, eg. like: - Post a description of the service to the ENUM WG mailing list, including: - experimental service type name - proposed subtypes name - proposed URI types - short usage description if there are no substantial objections posted on the list (eg. like using "x-skype" for sip URIs ;), the usage of the experimental service name is recorded in some list (IANA?). That experimental label may then be used for the purpose described. If usage picks up, it is strongly recommended that the common ENUMService registration process is started. I am aware that this is a difficile issue - we don't want to lure people away from registering "real" ENUMservices, but we need to provide a way to prevent clashes. That could obviously go into the "guide" draft, but would probably affect 3761bis as well. cheers Alex _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Mar 29 09:38:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOboG-0002Xx-Ry; Wed, 29 Mar 2006 09:38:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOboE-0002Xp-PV for enum@ietf.org; Wed, 29 Mar 2006 09:38:07 -0500 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOboD-0007Ne-CT for enum@ietf.org; Wed, 29 Mar 2006 09:38:06 -0500 Received: from [10.0.2.7] (h87.s239.verisign.com [216.168.239.87]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id k2TEcUXO007198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Mar 2006 06:38:31 -0800 Message-ID: <442A9BC1.7090606@shockey.us> Date: Wed, 29 Mar 2006 09:37:53 -0500 From: Richard Shockey User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: enum@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: Cullen Jennings , =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= , "Peterson, Jon" Subject: [Enum] ENUM Working Group Last call on ENUM Implementation Experiences 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 Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-04.txt Pages : 37 Date : 2006-3-9 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-04.txt The intent of the last call is to solicit comments before submitting the ID to the IESG as a Proposed Standard. This document has been under discussion since 2004. The purpose of a working group Last Call is in the style of "speak now or forever hold your peace" in case there are fundamental objections which have not gotten previous or adequate discussion, or minor errors which need correction. Work group last call will extend for 2 weeks or so from today Mar 29 until at least April 13 though we can modify that if new issues come up. -- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Director - Member of Technical Staff NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141(at)fwd.pulver.com ENUM +87810-13313-31331 PSTN Office +1 571.434.5651 PSTN Mobile +1 703.593.2683 Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Fri Mar 31 02:32:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPE6E-00064l-FH; Fri, 31 Mar 2006 02:31:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FPE6C-00063a-ED for enum@ietf.org; Fri, 31 Mar 2006 02:31:13 -0500 Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FPE6A-0001fd-9o for enum@ietf.org; Fri, 31 Mar 2006 02:31:12 -0500 Received: from [10.10.0.63] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Fri, 31 Mar 2006 09:31:06 +0200 id 0000804D.442CDABB.000027F6 Message-ID: <442CDAAC.7000106@enum.at> Date: Fri, 31 Mar 2006 09:30:52 +0200 From: Alexander Mayrhofer Organization: enum.at GmbH User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "'enum@ietf.org'" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.5 (/) X-Scan-Signature: 9b157e6e8a3799aef911c0bc37fc93a6 Subject: [Enum] IETF65 ENUM session minutes 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 minutes are below - thanks to Spencer and Bernie for serving as scribes. ---- IETF65 (Dallas, TX) ENUM meeting minutes Chair(s): Patrik Faltstrom Richard Shockey WG Secretary: Alex Mayrhofer Scribes: Spencer Dawkins Alex Mayrhofer Jabber Scribe: Bernie Hoeneisen Real Time Applications Infrastructure Area Director(s): Cullen Jennings Jon Peterson AGENDA BASHING (5 min) ====================== Slight change to agenda - Patrik talks about 3761bis planned works first: RFC3761bis ========== Patrik is not upping for IAB, so has time to update RFC3761 (3761bis), which is in line with WG milestone. A RT tracker system is set up for work on this document, issues should be opened as tickets in the system. One ticket per issue should be opened, there will be shared username/password for access to the system. Patrik will work on the individual issues, and resolve corresponding tickets once an issue is resolve. When all issues are resolved, the document should be ready. 3761bis does not exist as an draft yet - RT stuff will provide input for this. Patrik will do the editing. More info: http://www1.ietf.org/mail-archive/web/enum/current/msg04849.html Tickets could also affect other documents (conroy asks for DDDS issues). Shockey asks if guidance on non-terminals should go in there as well. Conroy suggests to put hints in 3761bis. patrik: operational experience stuff could go in seperate section or even document. ENUM Implementers Draft: (Final Version) 5 MIN ============================================== Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-04.txt Pages : 37 Date : 2006-3-9 This document captures experience in implementing systems based on the ENUM protocol, and experience of ENUM data that have been created by others. As such, it is advisory, and produced as a help to others in reporting what is "out there" and the potential pitfalls in interpreting the set of documents that specify the protocol. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-experiences-04.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-8.ppt * Changes include section 6 (general DNS issues), request publication - Section 6 is biggest source of changes (others mostly editorial, seeking clarity, please give feedback for continued improvements). * Added size recommendations for EDNS0, intermediate system guidance, TTL and ANY (255) queries (this is a general DNS issue, but has been a problem in ENUM deployment - NAPTRs appear/disappear, etc.). * Please read and review - think we are finished, publish and update later if we need to. * Tim - "Non-terminal NAPTRs SHOULD NOT be used" - can't go quite this far - if you're gonna do this, it will take a long time - one third of the code on mobile clients deals with this. EDNS0 doesn't work with TCP, etc. - lots of things break. We'll talk offline, and this is a good WGLC comment. * EDNS0 is recommended here. May be spun off as separate document and just referenced here (if we can avoid dependencies). Still discussing MUST capitalization with DNSOPS reviewers. * Peter Koch: Implementation and OPS side is too much in one document - advocate separation. Having normative language for firewalls isn't appropriate in this standards track document. EDNS0 is a precondition for anything that uses DDDS - make a recommendation for minimum size in general, TCP, etc. * Conroy: Firewalls break DNS over TCP all by themselves, without any ENUM involved. Enumservices Guide ================== Title : Guide and Template for IANA Registrations of Enumervices [ 15 M ] Author(s) : J. Livingood, B. Hoeneisen Filename : draft-ietf-enum-enumservices-guide-00.txt Pages : 12 Date : 2006-2-27 This document provides a guide to and template for the creation of new IANA registration of ENUM services. It is also to be used for updates of existing IANA registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-enumservices-guide-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-4.ppt History: People filling out over and over again same sections with same content when doing Enumservice registrations. Standard template desired. request input for 3.2 ("Intended usage: COMMON") and 3.6 ("IANA Considerations"). Please post text or email privately. Section 3.2 - should a subtype always be given? should seperate subtypes have seperate registrations? for each URI scheme seperate? Statement on non-terminal NAPTRs? suggested answer: yes/yes/yes/no (with warning on non-terminals) Penn: didn't get a lot of guidance - would like template that includes cautions. cautions ok, but should actually tell you how to do this. Stastny: Usage of non-terminals need to be clarified before usage of them is advocated. shockey: should the behaviour regarding non terminals be in registration document itself? conroy: could imaging 2 ways to non-terminals. currently, missing flag indicates "non terminal", which is outside DDDS. If no flag is given, we can't do registrations, so seperate flag and seperate registration? no final conclusion about the four questions. CNAM ==== Title : IANA Registration for an Enumservice and "tel" [ 15 Min ] Parameter for Calling Name Delivery(CNAM) Information Author(s) : R. Shockey, J. Livingood Filename : draft-shockey-enum-cnam-00.txt Pages : 10 Date : 2006-1-13 This document registers the Enumservice "cnam" and subtype "tel" using the URI scheme 'tel:', as per the IANA registration process defined in the ENUM specification, RFC 3761. In addition this document registers the parameter "cnam" in the IANA "tel" Parameter Registry defined in RFCXXX. This data is used to facilitate the transfer of Calling Name Delivery (CNAM) data for calls that originate on the 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-shockey-enum-cnam-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-6.ppt is about caller name display. info is requested in the US before callees phone rings. service assumes a private tree, with info not public. discussion about tel uri parameter vs. data uri. draft proposes tel parameter, but not sure about this (list discussions). What character set being used? No ultimate restriction, but PSTN limits to 15 characters in ASCII. How to interpret contents? DDDS says UTF-8, but there should be wording about this in there. Need to be aware what is about to being parsed (security considerations should point that out). List of CNAM specs to point people to is requested. Group agrees to adopt this as WG item - no "no" hums in room. tel or data URI? Paul primary objector, but not in the room. "tel" because this is a classic PSTN thing? Jon: don't compete with SIP caller name - what happens if both present? This needs to be interopable with normal SIP stuff. Jason: What if other providers don't have SIP URIs in their network, and are trying to limit the number of bits they are paying to store? Lawrence: Could have "network provided" and "user provided" numbers as well. this is for "network provided" - we use TXT in trials now. Jon: If network provided, don't we prefer to render that? Display name could be present in from tel or sip. data would never show up in SIP, but the servers or user agents would fetch it. depends all on call flows and use cases. don't couple with tel - would never appear in request. Jason/Richard: No preference, will dig deeper into data URI. IAX2 Enumservice: ================= Title : IANA Registration for IAX Enumservice [ 15 M ] Author(s) : E. Guy Filename : draft-ietf-enum-iax-00.txt Pages : 13 Date : 2006-2-22 This document registers the IAX2 (Inter-Asterisk eXchange Version 2) Enumservice using the URI scheme 'iax2:' as per the IANA registration process defined in the ENUM specification RFC3761. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-iax-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-7.pdf Need IAX2 URI registration, and a new template has shown up since last time. Some minor tech changes. Currently requested IESG review of protocol itself, will submit URI request using new template. Enumservice would need to go after URI registration (because RFC editors would need to perform edits otherwise). ENUM & Domainkeys ================= Title : Telephone Number Mapping and Domain Keys as a Distributed Identity Infrastructure [ 15 M ] Author(s) : A. Mayrhofer Filename : draft-mayrhofer-enum-domainkeys-00.txt Pages : 10 Date : 2006-2-23 This document creates a decentralized indentity infrastructure by combining technology from E.164 Number Mapping (ENUM) and DomainKeys Identified Mail (DKIM). This infrastructure uses E.164 numbers as identities, ENUM DNS for key distribution, and leverages the trust relations from ENUM validation to actual messages signed by the number holder. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mayrhofer-enum-domainkeys-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-2.ppt # Not a full DDDS app, not a full Domain Keys app, so ... # Validation is most expensive part of ENUM provisioning - validation takes the identity to Internet domain - make use of this expense! # ENUM, not full DDDS # Domainkeys, but just key/storage # Validate that Sender has the same identiry as number holder # Available to any ENUM domain holder, no prior knowledge about sender required, any node on Internet can do this, domain internationally agreed, common validity. # Applications - signin to P2P networks, CLI signalling to PSTN, SPIT prevention. # Disconnected nodes could do authentication (with cached public keys) # Looking for opinions/feedback # Looking for crypto-PKI clue on co-authors # Steve Kent - you're going down to individual devices, right? form of identifier needs to be appropriate for applications. Going to this granularity needs to scale bigger than the DKIM application today, so think about scaling. (and why not DNSsec?) # Koch: How much do you want to trust DNS? You need DNSsec to trust this anyway, and if you do have DNSsec, maybe this would be enough. Cool ideas with deployment problems, probably premature, keep thinking. # David Schwartz - concerned about relying on PKI for individual certificates with no challenges, etc. E.164 numbers have geographic content, and this opens us up to some additional issues (beyond e-mail addresses). May need additional controls, may need to know who is verifying the numbers, etc. # SIP has made different tradeoffs, because of things like lack of huge installed base, etc. - have you looked at SIP Identity? There's a gap here that needs to be filled. # Penn Pfautz: Interesting idea, could be investigate further for usage even in carrier scenarios. Enumservice FOAF ================ Title : IANA Registration for Enumservice foaf [ 15 Min ] Author(s) : K. Reichinger Filename : draft-reichinger-enum-foaf-00.txt Pages : 9 Date : 2006-2-15 This memo registers the Enumservice "foaf" using the URI schemes "http" and "https" according to the IANA Enumservice registration process defined in RFC3671. The Enumservice "foaf" is to be used to refer from an ENUM domain name to the location of a FOAF RDF file using the corresponding E.164 telephone number. Clients may use data retrieved from a FOAF RDF file to provide caller or callee with information available within the Friend-Of-A-Friend (FOAF) Semantic Web application. For example, the caller might be presented with personal information on the callee (e.g. name, gender and various online attributes) as well as information on the callee's social context (e.g. relations to friends or colleagues). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-reichinger-enum-foaf-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-3.ppt * FOAF is "Friend of a Friend" * Part of Semantic Web Project * Lots of terms defined already (in presentation) * Data is RDF-based and can be published anywhere on the web * Want to link FOAF data to phone number * Allows FOAF/ENUM spidering * Introduces ENUM to Semantic Web * Rohan - how do you find my FOAF data if I don't have a phone number today? Could be published on website, could appear as FOAF data under a related friend. * Richard Shockey - privacy issues seem astounding - how granular is privacy? File-by-file, so all-or-nothing. This is vCard-equivalent privacy - no, it's also other people's data in your profile, so it's more than vCard privacy issues. * Is this voluntary, like blogging? Yes. What applications read this information today? Don't think so, at the moment (but it's RDF-based). * Alex: Privacy question comes up for every service we talk about. Jason/Bernie - please point out that securing the underlying data isn't part of the ENUM service registration template, only the additional security issues of linking it to ENUM. * Rohan - there is a vCard security considerations list now - that's understood. What are we doing in ENUM if we make E.164 addresses more useful than other identifiers? Make a service discovery service, instead? * E.164 numbers are simply keys, period. * Patrik is concerned that the E.164 number becomes the FOAF identifier and should not be tied directly to the URI, which may move, etc. Lots of people are looking in this area (IRIS, Rohan, etc.). ENUM gives you URIs, not URNs. * What should we do with this document? The underlying protocols are experimental, so this should be, too. Need to publish something, so people know about the string - X-dash, for example? * Jon - don't actually know how to distinguish ENUM applications that use the same protocols (http) - need to figure out how to do this. * Rohan - if you have someone's web page and can't find their FOAF information, that's a Semantic Web issue that needs to be solved independently. (web page address could come from ENUM, FOAF to be discovered from there) * Rohan - need to come up with a generic way to do these registrations. Don't need to do much here except avoid conflicts. * Richard Shockey - would like to see one more spin of this document with updated registration template (draft previously discussed), but this is very interesting. IM Enumservice & Calendering Enumservice ======================================== Title : A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) Services [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-im-service-00.txt Pages : 5 Date : 2006-2-22 This document registers a Telephone Number Mapping (ENUM) service for Instant Messaging (IM). Specifically, this document focuses on provisioning im: URIs in ENUM. Title : A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services [ 15 M ] Author(s) : R. Mahy Filename : draft-mahy-enum-calendar-service-00.txt Pages : 5 Date : 2006-2-23 This document registers a Telephone Number Mapping (ENUM) service for Internet Calendaring Services. Specifically, this document focuses on provisioning mailto: (iMIP) and http: (CalDAV) URIs in ENUM. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mahy-enum-calendar-service-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-5.ppt IM: --- * Was surprized that IM enumservice didn't exist, but it didn't exist. * Like pres URI, can only return IM URIs, and have a 3861 mechanism to discover correct/preferred protocol. * Comments? * Lawrence - this is fine. Not sure who will use this, because most IM users won't have SRV records. But no problem with the draft. * Room hummed to make thsi a WG draft Adopted as WG item. Calendar: --------- * Used to discover mailto and http(s) URIs for Internet calendaring services * Actually several subservices (manipulate calendar, check busy/free), including subservices that you can support in iCal, but not with IMAP. * Could this be merged with vCard transport? CALDEV doesn't really have a working group home (Calify has the right people) - but this isn't a generic vCard service. * Is this just traditional calendar events? There are a lot of possible calendars, which may be overlapping. Would this be better for the IETF Agenda? Rohan prefers to point to services with well-defined services. * Are we rolling too much stuff into ENUM? * Is this a WG item? Some number of hums in favor, fewer opposed. Adopted as WG item. Infrastructure Requirements =========================== Title : Infrastrucure ENUM Requirements Author(s) : S. Lind, P. Pfautz [ 20 M ] Filename : draft-ietf-enum-infrastructure-enum-reqs-00.txt Pages : 7 Date : 2006-3-6 This document provides requirements for "infrastructure" or "carrier" ENUM, 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-infrastructure-enum-reqs-00.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-1.ppt * Lawrence - UK experience is that your "SHALL" should be "SHALL NOT" - anything that is public must not be able to identify the serving CSP... - this is the difference between "must have the capability" and "must turn the capability on". Have used cut-outs in the US for information like carrier-of-record. * If we're allowed to return anything, it would be carrier of record. * Richard Shockey - if you're going to do something like this, you have to have a WHOIS. * Next steps with this document? WGLC? Consensus to go for it. Combined User and Carrier ENUM ============================== "Combined User and Carrier ENUM in the e164.arpa tree" - draft-haberler-carrier-enum-02.txt . [20 M] Abstract: ENUM as defined now in RFC3761 is not well suited for the purpose of interconnection by carriers, as can be seen by the use of various private tree arrangements based on ENUM mechanisms. A combined end-user and carrier ENUM tree solution would leverage the ENUM infrastructure in e164.arpa, increase resolution rates, and decrease the cost per registered telephone number. This document describes a minimally invasive scheme to provide both end-user and carrier data in ENUM. until it comes out of the queue, the I-D is available at: http://www.ietf.org/internet-drafts/draft-haberler-carrier-enum-02.txt slides: http://www3.ietf.org/proceedings/06mar/slides/enum-0.ppt # Consensus is to have one tree. In .arpa? IETF, IAB, RIPE, ITU-T involvement all needed, and existing policies/procedures can be reused. No time to come up with a new governing body and get agreement. # Above the country code, or below the country code? (or both places in parallel? - but would meet the requirements no matter where it is). # Above country code is most straight-forward solution (everything works), but has some constraints on timing for ITU-T concurrence. # Below country code is a national matter and can be implemented now. # Uses Branch Location Records (BLR). # Proposed to pursue both options in parallel, to allow trials using below country code. # Need RFC 3761bis to accomplish this. # Is BLR at the country level? No, location is a national matter ("below the zone cut"). # Lawrence - don't like TXT records. new RR is strongly recommended. Use TXT records for trials? # Richard Shockey - have never liked BLR (and never will). IAB isn't the decision-maker, it's IESG. # Patrik - ITU-T will be involved even if it's below the country code. # Lars - problem with TXT records. Can't stop you from using them for trials, but please make sure there are no collisions. # Richard Shockey - ITU-T will be involved, get used to it. # Patrik - in all the choices, so ITU-T involvement isn't a reason to pick one choice. # Richard Shockey - we need to expect 3GPP interest in carrier ENUM, too. # There are only about 300 records - why update millions of clients to recognize them? # May ITU-T meeting - need to do something about this very soon. # Patrik - do we disagree about above/below because we are missing requirements from the requirement documents? Should we have had more requirements? # Jon - remember that the IESG doesn't make decisions in a vacuum - IAB is part of the community that will be involved in any community decision. # Need to describe what's in DNS (label the boxes or your filing system will break down). Can't assume that all TXT records will "really" be BLRs. # There is a Draft Standard on handling unknown RR types (one of our few). # We all prefer option one, but what do we do in the interim? Alternative is that carriers will pick something, hopefully in the public parts of DNS, and then we'll TRY to tie things together. # Should this draft be a working group item? Richard Shockey doesn't think so - are we talking about having a separate domain for infrastructure ENUM? That's a separate document. Does not see BLR moving forward (unusual use of DNS). # Lawrence - don't like this, I'm worried about this, but the way ENUM is set up in the world, a global standard isn't going to happen quickly without something like this. # Richard Shockey - are BLRs a viable option? We took a hum, and lots of people said "yes". # Patrik - Some individuals violently disagree - can they go off to the bar and report back to the working group? On the Mailing list, this week. The outcome of bar discussions was later posted as the "Dallas Treaty": http://www1.ietf.org/mail-archive/web/enum/current/msg04848.html AOB === Koch: worried about potential size of DNS responses, number of ENUM services rising could lead to lots of TCP queries... meeting concluded. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum