From enum-bounces@ietf.org Mon Apr 02 13:01:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYPtC-0005mA-SS; Mon, 02 Apr 2007 13:00:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYPtC-0005lI-4W for enum@ietf.org; Mon, 02 Apr 2007 13:00:18 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYPtA-0007sB-OM for enum@ietf.org; Mon, 02 Apr 2007 13:00:18 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l32H03sB016392; Mon, 2 Apr 2007 10:00:08 -0700 From: "Richard Shockey" To: Date: Mon, 2 Apr 2007 12:54:50 -0400 Message-ID: <009201c77547$a199fda0$e4cdf8e0$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 thread-index: Aca3xY1iIc3tIYqQTKyYngbYZG9Jtg== Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" Subject: [Enum] ENUM Working Group Last Call draft-ietf-enum-experiences-07.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-07.txt Pages : 32 Date : 2007-3-22 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-07.txt The intent of the last call is to solicit comments before submitting the ID to the IESG as an Informational Document. 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 April 2 until at least April 16 though we can modify that if new issues come up. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:57141@fwd.pulver.com PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 02 14:42:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYRTE-0004Ue-Ec; Mon, 02 Apr 2007 14:41:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYRTD-0004UW-Dx for enum@ietf.org; Mon, 02 Apr 2007 14:41:35 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYRTA-0004Ge-SF for enum@ietf.org; Mon, 02 Apr 2007 14:41:35 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l32IfFdK005261 for ; Mon, 2 Apr 2007 11:41:18 -0700 From: "Richard Shockey" To: Date: Mon, 2 Apr 2007 14:36:01 -0400 Message-ID: <00f501c77555$c406abf0$4c1403d0$@us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00F6_01C77534.3CF50BF0" X-Mailer: Microsoft Office Outlook 12.0 thread-index: AcdxS9VkBtfFWV0mR3mrU0RBzkk2tgECeqeg Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Subject: [Enum] FW: I-D ACTION:draft-hoeneisen-enum-x-service-regs-00.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multipart message in MIME format. ------=_NextPart_000_00F6_01C77534.3CF50BF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, March 28, 2007 10:50 AM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-hoeneisen-enum-x-service-regs-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Registration of Enumservices for experimental, private or trial use Author(s) : B. Hoeneisen Filename : draft-hoeneisen-enum-x-service-regs-00.txt Pages : 7 Date : 2007-3-28 This document provides a guide to the creation of new IANA registrations of experimental ENUM (E.164 Number Mapping) services. It is also to be used for updates of those experimental Enumservice registrations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoeneisen-enum-x-service-regs-00.t xt 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-hoeneisen-enum-x-service-regs-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-hoeneisen-enum-x-service-regs-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------=_NextPart_000_00F6_01C77534.3CF50BF0 Content-Type: Message/External-body; name="ATT16410.dat" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT16410.dat" Content-Type: text/plain Content-ID: <2007-3-28095532.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-hoeneisen-enum-x-service-regs-00.txt ------=_NextPart_000_00F6_01C77534.3CF50BF0 Content-Type: Message/External-body; name="draft-hoeneisen-enum-x-service-regs-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-hoeneisen-enum-x-service-regs-00.txt" Content-Type: text/plain Content-ID: <2007-3-28095532.I-D@ietf.org> ------=_NextPart_000_00F6_01C77534.3CF50BF0 Content-Type: text/plain; name="ATT16413.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT16413.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------=_NextPart_000_00F6_01C77534.3CF50BF0 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_00F6_01C77534.3CF50BF0-- From enum-bounces@ietf.org Wed Apr 04 15:51:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZBV6-0004eA-D6; Wed, 04 Apr 2007 15:50:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZBUc-0004K0-RV; Wed, 04 Apr 2007 15:50:06 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZBUb-0000yd-Pl; Wed, 04 Apr 2007 15:50:06 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 3918926EF7; Wed, 4 Apr 2007 19:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HZBUY-0001hG-L2; Wed, 04 Apr 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 04 Apr 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-validation-epp-05.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : ENUM Validation Information Mapping for the Extensible Provisioning Protocol Author(s) : B. Hoeneisen Filename : draft-ietf-enum-validation-epp-05.txt Pages : 25 Date : 2007-4-4 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-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-validation-epp-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-validation-epp-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-4-4141603.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-validation-epp-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-validation-epp-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-4-4141603.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Wed Apr 18 08:56:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1He9i4-0006we-4M; Wed, 18 Apr 2007 08:56:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1He9i2-0006wY-BT; Wed, 18 Apr 2007 08:56:30 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1He9hy-0002Qk-Tw; Wed, 18 Apr 2007 08:56:30 -0400 Received: from rshockeyPC (h-68-165-240-35.mclnva23.covad.net [68.165.240.35]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l3ICbpBK010245; Wed, 18 Apr 2007 05:37:55 -0700 From: "Richard Shockey" To: , Date: Wed, 18 Apr 2007 08:31:18 -0400 Message-ID: <00f501c781b5$77881860$66984920$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcbidRrsdNW+DQs8QJaqMDsmeXxplw== Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Cc: 'Cullen Jennings' , =?iso-8859-1?Q?'=22Patrik_F=E4ltstr=F6m=22'?= , "'Peterson, Jon'" Subject: [Enum] ENUM WG Request for Publication - draft-ietf-enum-experiences-07.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: richard@shockey.us List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a request for publication on one ENUM WG document. Title : ENUM Implementation Issues and Experiences Author(s) : L. Conroy, K. Fujiwara Filename : draft-ietf-enum-experiences-07.txt Pages : 32 Date : 2007-3-22 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-07.txt This is a request for publication for one IETF ENUM WG working group document. A two week WG last call on this document concluded on April 16. The document listed above is being proposed for Informational. This document has been extensively discussed during 2005-2007. Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org sip:5651(at)neustarlab.biz PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Apr 18 16:21:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeGeh-00011H-6f; Wed, 18 Apr 2007 16:21:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeGea-0000gP-VN; Wed, 18 Apr 2007 16:21:24 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeGeZ-0001KL-KD; Wed, 18 Apr 2007 16:21:24 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id D1C7B329B4; Wed, 18 Apr 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HeGAE-0002Eu-OI; Wed, 18 Apr 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 18 Apr 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-iax-02.txt X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telephone Number Mapping Working Group of the IETF. Title : IANA Registration for IAX Enumservice Author(s) : E. Guy Filename : draft-ietf-enum-iax-02.txt Pages : 14 Date : 2007-4-18 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-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-iax-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-iax-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-4-18122334.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-iax-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-iax-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-4-18122334.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum --NextPart-- From enum-bounces@ietf.org Wed Apr 18 16:48:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeH4T-0005gq-LG; Wed, 18 Apr 2007 16:48:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HeH4S-0005gi-Fy for enum@ietf.org; Wed, 18 Apr 2007 16:48:08 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeH4S-0004Ym-1E for enum@ietf.org; Wed, 18 Apr 2007 16:48:08 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l3IKlpUq022776 for ; Wed, 18 Apr 2007 13:47:55 -0700 From: "Richard Shockey" To: References: In-Reply-To: Subject: RE: [Enum] I-D ACTION:draft-ietf-enum-iax-02.txt - Comments Wanted ! Date: Wed, 18 Apr 2007 16:41:16 -0400 Message-ID: <039b01c781f9$e9d3a530$bd7aef90$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceB9yfrHQM6CqXpQzeqc5hBpIA/6AAAoSrw Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da 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 Folks .. I'd like to move forward with this to WGLC. If interested parties could give the document a through overview and comment to the list it would be appreciated. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, April 18, 2007 3:50 PM To: i-d-announce@ietf.org Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-iax-02.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 : IANA Registration for IAX Enumservice Author(s) : E. Guy Filename : draft-ietf-enum-iax-02.txt Pages : 14 Date : 2007-4-18 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-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-enum-iax-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-enum-iax-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. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Apr 19 14:17:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HebAu-0003DK-3H; Thu, 19 Apr 2007 14:16:08 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HebAt-0003DE-AY for enum@ietf.org; Thu, 19 Apr 2007 14:16:07 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HebAr-0006t3-Sa for enum@ietf.org; Thu, 19 Apr 2007 14:16:07 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l3JIFnhL024371 for ; Thu, 19 Apr 2007 11:15:53 -0700 From: "Richard Shockey" To: Date: Thu, 19 Apr 2007 14:15:48 -0400 Message-ID: <016d01c782ae$c1766270$44632750$@us> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceCrsEXVTtQtxzgTVqgzbNgyMvyMg== Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.5 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [Enum] Apologies for the delay 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 Alex has posted the meeting minutes from Prague. If there are any comments post to the list ASAP. http://www3.ietf.org/proceedings/07mar/minutes/enum.txt Richard Shockey Director, Member of the Technical Staff NeuStar 46000 Center Oak Plaza - Sterling, VA 20166 sip:rshockey(at)iptel.org PSTN Office +1 571.434.5651 PSTN Mobile: +1 703.593.2683 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 23 09:22:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyUN-00006y-T2; Mon, 23 Apr 2007 09:21:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfuVt-0006KV-Tf for enum@ietf.org; Mon, 23 Apr 2007 05:07:13 -0400 Received: from smtp25.orange.fr ([193.252.22.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfuVq-0004TG-Qp for enum@ietf.org; Mon, 23 Apr 2007 05:07:13 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id DA5511C0009D for ; Mon, 23 Apr 2007 11:07:09 +0200 (CEST) Received: from HARNON (APoitiers-156-1-5-204.w86-207.abo.wanadoo.fr [86.207.164.204]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id 0FA4C1C0009C for ; Mon, 23 Apr 2007 11:07:09 +0200 (CEST) X-ME-UUID: 20070423090709647.0FA4C1C0009C@mwinf2502.orange.fr From: "Philippe Verdy" To: Date: Mon, 23 Apr 2007 11:07:03 +0200 Organization: Ordinateur Personnel Message-ID: <008901c78586$c29bf0e0$0a01a8c0@rodage.dyndns.org> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceFhsGOcMlU0m/TRpKKYOIQSLZ/yw== X-Spam-Score: 0.0 (/) X-Scan-Signature: d7967c711acf4eec6f9b62d49dcc5a34 X-Mailman-Approved-At: Mon, 23 Apr 2007 09:21:54 -0400 Subject: [Enum] My prior art published in august 2000 to abusive US Patent 6, 347, 085 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: verdy_p@wanadoo.fr List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0535922622==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============0535922622== Content-Type: multipart/alternative; boundary="----=_NextPart_000_008A_01C78597.8624C0E0" This is a multi-part message in MIME format. ------=_NextPart_000_008A_01C78597.8624C0E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was the personal author of a discussion we had on the ICANN discussion list (during its reform in its =93At Large study=94 and election = process) about the convergence of telephone and Internet =20 You (IETF, and ITU) seem to have problems with US Patent 6,347,085 that = was disclosed in 2002. =20 But the basic concept behind the claimed apparatus, and the way ENUM was finally adopted in 2002 was exactly what I proposed in the public ICANN discussion list in 2000. =20 Proof: =20 If people are making money from my idea that I filed in a public = discussion at ICANN for free, then they are abusing my right. I want to give you a possible proof that the claims in this patent against the whole ENUM = project that was really finalized in a working model in 2002 may be wrong, = because it covers prior art. =20 I described an example with a French phone number like +33.1.23456789 = that would be simply managed by: * Creating a root subzone (I just gave .phone as an example, but the = IETF proposed .e164.arpa, which is equivalent) * giving the authority of this zone to the ITU who is in charge of the portable international phone numbering plan. * making sure that the phone number is written in international form, = and removing + and all separators. * reversing the digits * separating each digit by dots, so creating as many zubzones as = necessary to match the numbering plan delegations * and having each country manage its own registry for the numbers they = have in charge, with the ITU=85 =20 My proposal was simpler thanFrom enum-bounces@ietf.org Mon Apr 23 09:22:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyUN-00006y-T2; Mon, 23 Apr 2007 09:21:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfuVt-0006KV-Tf for enum@ietf.org; Mon, 23 Apr 2007 05:07:13 -0400 Received: from smtp25.orange.fr ([193.252.22.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfuVq-0004TG-Qp for enum@ietf.org; Mon, 23 Apr 2007 05:07:13 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id DA5511C0009D for ; Mon, 23 Apr 2007 11:07:09 +0200 (CEST) Received: from HARNON (APoitiers-156-1-5-204.w86-207.abo.wanadoo.fr [86.207.164.204]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id 0FA4C1C0009C for ; Mon, 23 Apr 2007 11:07:09 +0200 (CEST) X-ME-UUID: 20070423090709647.0FA4C1C0009C@mwinf2502.orange.fr From: "Philippe Verdy" To: Date: Mon, 23 Apr 2007 11:07:03 +0200 Organization: Ordinateur Personnel Message-ID: <008901c78586$c29bf0e0$0a01a8c0@rodage.dyndns.org> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceFhsGOcMlU0m/TRpKKYOIQSLZ/yw== X-Spam-Score: 0.0 (/) X-Scan-Signature: d7967c711acf4eec6f9b62d49dcc5a34 X-Mailman-Approved-At: Mon, 23 Apr 2007 09:21:54 -0400 Subject: [Enum] My prior art published in august 2000 to abusive US Patent 6, 347, 085 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: verdy_p@wanadoo.fr List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0535922622==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============0535922622== Content-Type: multipart/alternative; boundary="----=_NextPart_000_008A_01C78597.8624C0E0" This is a multi-part message in MIME format. ------=_NextPart_000_008A_01C78597.8624C0E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was the personal author of a discussion we had on the ICANN discussion list (during its reform in its =93At Large study=94 and election = process) about the convergence of telephone and Internet =20 You (IETF, and ITU) seem to have problems with US Patent 6,347,085 that = was disclosed in 2002. =20 But the basic concept behind the claimed apparatus, and the way ENUM was finally adopted in 2002 was exactly what I proposed in the public ICANN discussion list in 2000. =20 Proof: =20 If people are making money from my idea that I filed in a public = discussion at ICANN for free, then they are abusing my right. I want to give you a possible proof that the claims in this patent against the whole ENUM = project that was really finalized in a working model in 2002 may be wrong, = because it covers prior art. =20 I described an example with a French phone number like +33.1.23456789 = that would be simply managed by: * Creating a root subzone (I just gave .phone as an example, but the = IETF proposed .e164.arpa, which is equivalent) * giving the authority of this zone to the ITU who is in charge of the portable international phone numbering plan. * making sure that the phone number is written in international form, = and removing + and all separators. * reversing the digits * separating each digit by dots, so creating as many zubzones as = necessary to match the numbering plan delegations * and having each country manage its own registry for the numbers they = have in charge, with the ITU=85 =20 My proposal was simpler than having to parse phone numbers and = discovering howmany digits are needed to route a call to any network, because the = DNS is flexible enough. I also proposed using dynamic DNS. =20 Although my message was short, and not the complete document that would = make the policy needed to run the ENUM registry. All the core concepts were exposed in my message. In fact, even the simplified alternative (without reversing the whole number and with less dots) was also described. I = gave the choice=85 =20 See ICANN discussion archives (my message is signed there, by my name = and my (still valid) personal email address, and I was registered at ICANN as a valid subscriber at this time, for the ongoing ICANN reform): =20 http://forum.icann.org/adhoc/ =20 More precisely this message: http://forum.icann.org/adhoc/39948C41000000DA.html posted on August 11, 2000 (so weeks before the US Patent was filed in September 2000) =20 Username:=20 verdy_p =20 Date/Time:=20 Fri, August 11, 2000 at 11:29 PM GMT Browser:=20 Microsoft Internet Explorer V5.01 using Windows 98=20 Score:=20 5 Subject:=20 Convergence can be done within a DNS Message:=20 =20 =20 =20 Assume you want to translate a phone number to an IP address (chould it = be IPv4 or IPv6), this can already be done using DNS: Example: you want to translate a phone number in France, say: +33.1.23456789 You could think it can be done by requesting a domain name like: 123456789.33.phone (This assumes that phone is a TLD, in which each international phone = code is registered and operated as a sub-TLD, and then the number is solved appropriately within that country registry.) However there are issues, such that renumbering schemes (how many digits have to be searched ?) Another solution is to use the reversed phone number and cutting phone number in individual digits: 9.8.7.6.5.4.3.2.1.3.3.phone That way, you do not have to parse the phone number to find the minimum = set of digits that successfully resolves a domain name, and the numering = plan can be changed by distributing sub-DNS in each country. Because this = domain name is algorithmicly implement, it lacks of readability. So each = country could decide on the usual format to give to phone numbers so that they = can be easily parsed. Requesting the DNS could then return additional information, such that = the kind of information that can be returned by reversed phone number = searchs, however there are some privacy issues that should restrict the = information returned by DNS requests.=20 What I mean here, is that converging numbering plans to IP is not = necessary, because this process can be automated within dynamic DNS servers = operated by country phone registries and ITU.=20 =20 =20 So it seems that the US Patent applicant just copied exactly what I said = in the ICANN discussion list, and secretly filed a patent with many abusive verbose claims, and that patent that was only disclosed in 2002 when the ENUM project was made concrete, and they want to make money with an idea that they did not have and was publicly disclosed to ICANN before them. =20 I won=92t claim a patent myself (I can=92t pay an advocate for that to = defend in US), but at least us Patent 6,347,085 can be proven invalid ! =20 Philippe Verdy. verdy_p@wanadoo.fr =20 At the time of publishing I was living at this address: 17 rue Jean Dussourd, 92600 Asni=E8res-sur-Seine, France Now I live here : 15 rue Jean Perrin, Appt. 7 79000 Niort France My current phone number: +33(0)5 47 73 67 12 =20 ------=_NextPart_000_008A_01C78597.8624C0E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I was the personal author of a discussion we = had on the ICANN discussion list (during its reform in its “At Large = study” and election process) about the convergence of telephone and = Internet

 

You (IETF, and ITU) seem to have problems with = US Patent 6,347,085 that was disclosed in = 2002.

 

But the basic concept behind the claimed = apparatus, and the way ENUM was finally adopted in 2002 was exactly what I proposed = in the public ICANN discussion list in 2000.

 

Proof:

 

If people are making money from my idea that I = filed in a public discussion at ICANN for free, then they are abusing my = right. I want to give you a possible proof that the claims in this patent against = the whole ENUM project that was really finalized in a working model in 2002 = may be wrong, because it covers prior art.

 

I described an example with a French phone = number like +33.1.23456789 that would be simply managed = by:

* Creating a root subzone (I just gave .phone = as an example, but the IETF proposed .e164.arpa, which is = equivalent)

* giving the authority of this zone to the ITU = who is in charge of the portable international phone numbering = plan.

* making sure that the phone number is written = in international form, and removing + and all = separators.

I was the personal author of a discussion we = had on the ICANN discussion list (during its reform in its “At Large = study” and election process) about the convergence of telephone and = Internet

 

You (IETF, and ITU) seem to have problems with = US Patent 6,347,085 that was disclosed in = 2002.

 

But the basic concept behind the claimed = apparatus, and the way ENUM was finally adopted in 2002 was exactly what I proposed = in the public ICANN discussion list in 2000.

 

Proof:

 

If people are making money from my idea that I = filed in a public discussion at ICANN for free, then they are abusing my = right. I want to give you a possible proof that the claims in this patent against = the whole ENUM project that was really finalized in a working model in 2002 = may be wrong, because it covers prior art.

 

I described an example with a French phone = number like +33.1.23456789 that would be simply managed = by:

* Creating a root subzone (I just gave .phone = as an example, but the IETF proposed .e164.arpa, which is = equivalent)

* giving the authority of this zone to the ITU = who is in charge of the portable international phone numbering = plan.

* making sure that the phone number is written = in international form, and removing + and all = separators.

* reversing the = digits

* separating each digit by dots, so creating = as many zubzones as necessary to match the numbering plan = delegations

* and having each country manage its own = registry for the numbers they have in charge, with the = ITU…

 

My proposal was simpler than having to parse = phone numbers and discovering howmany digits are needed to route a call to any network, because the DNS is flexible enough. I also proposed using = dynamic DNS.

 

Although my message was short, and not the = complete document that would make the policy needed to run the ENUM registry. All = the core concepts were exposed in my message. In fact, even the simplified = alternative (without reversing the whole number and with less dots) was also = described. I gave the choice…

 

See ICANN discussion archives (my message is = signed there, by my name and my (still valid) personal email address, and I was registered at ICANN as a valid subscriber at this time, for the ongoing = ICANN reform):

 

http://forum.icann.org/adhoc/<= o:p>

 

More precisely this = message:

http://forum.= icann.org/adhoc/39948C41000000DA.html

posted on August 11, 2000 (so weeks before the = US Patent was filed in September 2000)

 

* reversing the = digits

* separating each digit by dots, so creating = as many zubzones as necessary to match the numbering plan = delegations

* and having each country manage its own = registry for the numbers they have in charge, with the = ITU…

 

My proposal was simpler than having to parse = phone numbers and discovering howmany digits are needed to route a call to any network, because the DNS is flexible enough. I also proposed using = dynamic DNS.

 

Although my message was short, and not the = complete document that would make the policy needed to run the ENUM registry. All = the core concepts were exposed in my message. In fact, even the simplified = alternative (without reversing the whole number and with less dots) was also = described. I gave the choice…

 

See ICANN discussion archives (my message is = signed there, by my name and my (still valid) personal email address, and I was registered at ICANN as a valid subscriber at this time, for the ongoing = ICANN reform):

 

http://forum.icann.org/adhoc/<= o:p>

 

More precisely this = message:

http://forum.= icann.org/adhoc/39948C41000000DA.html

posted on August 11, 2000 (so weeks before the = US Patent was filed in September 2000)

 

Username:

verdy_p

Date/Time:<= /span>

Fri, August 11, 2000 at 11:29 PM GMT

Browser:

Microsoft Internet Explorer V5.01 using = Windows 98

Score:

5

Subject:

Convergence can be done within a DNS


Username:

verdy_p

Date/Time:<= /span>

Fri, August 11, 2000 at 11:29 PM GMT

Browser:

Microsoft Internet Explorer V5.01 using = Windows 98

Score:

5

Subject:

Convergence can be done within a DNS


Message:

 

 

 

Assume you want to translate a phone = number to an IP address (chould it be IPv4 or IPv6), this can already be = done using DNS:
Example: you want to translate a phone number in France, say:
  +33.1.23456789
You could think it can be done by requesting a domain name = like:
  123456789.33.phone
(This assumes that phone is a TLD, in which each international = phone code is registered and operated as a sub-TLD, and then the number is = solved appropriately within that country registry.)
However there are issues, such that renumbering schemes (how many = digits have to be searched ?)
Another solution is to use the reversed phone number and cutting = phone number in individual digits:
  9.8.7.6.5.4.3.2.1.3.3.phone
That way, you do not have to parse the phone number to find the = minimum set of digits that successfully resolves a domain name, and the = numering plan can be changed by distributing sub-DNS in each country. = Because this domain name is algorithmicly implement, it lacks of readability. = So each country could decide on the usual format to give to phone numbers = so that they can be easily parsed.
Requesting the DNS could then return additional information, such = that the kind of information that can be returned by reversed phone = number searchs, however there are some privacy issues that should = restrict the information returned by DNS requests. =

What I mean here, is that converging = numbering plans to IP is not necessary, because this process can be = automated within dynamic DNS servers operated by country phone registries = and ITU.

 b>Message:

 

 

 

Assume you want to translate a phone = number to an IP address (chould it be IPv4 or IPv6), this can already be = done using DNS:
Example: you want to translate a phone number in France, say:
  +33.1.23456789
You could think it can be done by requesting a domain name = like:
  123456789.33.phone
(This assumes that phone is a TLD, in which each international = phone code is registered and operated as a sub-TLD, and then the number is = solved appropriately within that country registry.)
However there are issues, such that renumbering schemes (how many = digits have to be searched ?)
Another solution is to use the reversed phone number and cutting = phone number in individual digits:
  9.8.7.6.5.4.3.2.1.3.3.phone
That way, you do not have to parse the phone number to find the = minimum set of digits that successfully resolves a domain name, and the = numering plan can be changed by distributing sub-DNS in each country. = Because this domain name is algorithmicly implement, it lacks of readability. = So each country could decide on the usual format to give to phone numbers = so that they can be easily parsed.
Requesting the DNS could then return additional information, such = that the kind of information that can be returned by reversed phone = number searchs, however there are some privacy issues that should = restrict the information returned by DNS requests. =

What I mean here, is that converging = numbering plans to IP is not necessary, because this process can be = automated within dynamic DNS servers operated by country phone registries = and ITU.

 

 

So it seems that the US Patent applicant just = copied exactly what I said in the ICANN discussion list, and secretly filed a = patent with many abusive verbose claims, and that patent that was only = disclosed in 2002 when the ENUM project was made concrete, and they want to make = money with an idea that they did not have and was publicly disclosed to ICANN = before them.

 

I won’t claim a patent myself (I = can’t pay an advocate for that to defend in US), but at least us Patent = 6,347,085 can be proven invalid !

 

Philippe Verdy.

verdy_p@wanadoo.fr

 

At the time of publishing I was living at this address:

17 rue Jean = Dussourd,

92600 = Asnières-sur-Seine,

France

Now I live = here :

15 rue Jean = Perrin, Appt. 7

79000 = Niort

France

My current phone number: +33(0)5 47 73 67 = 12

 

------=_NextPart_000_008A_01C78597.8624C0E0-- --===============0535922622== 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 --===============0535922622==-- From enum-bounces@ietf.org Mon Apr 23 09:22:06 2007 Return-path:

 

So it seems that the US Patent applicant just = copied exactly what I said in the ICANN discussion list, and secretly filed a = patent with many abusive verbose claims, and that patent that was only = disclosed in 2002 when the ENUM project was made concrete, and they want to make = money with an idea that they did not have and was publicly disclosed to ICANN = before them.

 

I won’t claim a patent myself (I = can’t pay an advocate for that to defend in US), but at least us Patent = 6,347,085 can be proven invalid !

 

Philippe Verdy.

verdy_p@wanadoo.fr

 

At the time of publishing I was living at this address:

17 rue Jean = Dussourd,

92600 = Asnières-sur-Seine,

France

Now I live = here :

15 rue Jean = Perrin, Appt. 7

79000 = Niort

France

My current phone number: +33(0)5 47 73 67 = 12

 

------=_NextPart_000_008A_01C78597.8624C0E0-- --===============0535922622== 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 --===============0535922622==-- From enum-bounces@ietf.org Mon Apr 23 09:22:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyUO-000073-5E; Mon, 23 Apr 2007 09:21:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfukK-0002LG-Si for enum@ietf.org; Mon, 23 Apr 2007 05:22:08 -0400 Received: from smtp25.orange.fr ([193.252.22.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfukJ-00082Q-Fe for enum@ietf.org; Mon, 23 Apr 2007 05:22:08 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id CED851C00098 for ; Mon, 23 Apr 2007 11:22:06 +0200 (CEST) Received: from HARNON (APoitiers-156-1-5-204.w86-207.abo.wanadoo.fr [86.207.164.204]) by mwinf2502.orange.fr (SMTP Server) with ESMTP id 97D0E1C0008A for ; Mon, 23 Apr 2007 11:22:06 +0200 (CEST) X-ME-UUID: 20070423092206621.97D0E1C0008A@mwinf2502.orange.fr From: "Philippe Verdy" To: , References: Date: Mon, 23 Apr 2007 11:22:01 +0200 Organization: Ordinateur Personnel Message-ID: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 In-Reply-To: Thread-Index: AceFhsGOcMlU0m/TRpKKYOIQSLZ/ywAAVGsA X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 X-Mailman-Approved-At: Mon, 23 Apr 2007 09:21:54 -0400 Cc: Subject: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: verdy_p@wanadoo.fr List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1911760729==" Errors-To: enum-bounces@ietf.org This is a multi-part message in MIME format. --===============1911760729== Content-Type: multipart/alternative; boundary="----=_NextPart_000_008F_01C78599.9D13A7B0" This is a multi-part message in MIME format. ------=_NextPart_000_008F_01C78599.9D13A7B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Note that my message in the ICANN discussion list even predates RFC 2916 which was the first document published in a standard track in September 2000 by the IETF, and this old RFC is exactly what I described in August 2000. It's strange that I was not referenced in that RFC. Just before that, the last RFC was 2806 in April 2000 (URLs for telephone calls). But it did not describe the DNS registration system, only the syntax for several URI schemes ("tel:", "modem:", "fax:") using the standard E.164 syntax for specifying the phone number part. Philippe Verdy. ------=_NextPart_000_008F_01C78599.9D13A7B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Note that my = message in the ICANN discussion list even predates RFC 2916 which was the first = document published in a standard track in September 2000 by the IETF, and this = old RFC is exactly what I described in August 2000. It’s strange that I = was not referenced in that RFC… Just before that, the last RFC was 2806 in April 2000 = (URLs for telephone calls). But it did not describe the DNS registration = system, only the syntax for several URI schemes (“tel:”, = “modem:”, “fax:”) using the standard E.164 syntax for specifying the phone number = part.

 =

Philippe = Verdy.

------=_NextPart_000_008F_01C78599.9D13A7B0-- --===============1911760729== 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 --===============1911760729==-- l; color:windowtext;} span.EmailStyle19 {mso-style-type:personal-reply; font-family:Arial; color:navy;} @page Section1 {size:595.3pt 841.9pt; margin:70.85pt 70.85pt 70.85pt 70.85pt;} div.Section1 {page:Section1;} -->

Note that my = message in the ICANN discussion list even predates RFC 2916 which was the first = document published in a standard track in September 2000 by the IETF, and this = old RFC is exactly what I described in August 2000. It’s strange that I = was not referenced in that RFC… Just before that, the last RFC was 2806 in April 2000 = (URLs for telephone calls). But it did not describe the DNS registration = system, only the syntax for several URI schemes (“tel:”, = “modem:”, “fax:”) using the standard E.164 syntax for specifying the phone number = part.

 =

Philippe = Verdy.

------=_NextPart_000_008F_01C78599.9D13A7B0-- --===============1911760729== 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 --===============1911760729==-- From enum-bounces@ietf.org Mon Apr 23 10:04:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hfz9W-0004LF-D4; Mon, 23 Apr 2007 10:04:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hfz9U-0004Kl-Jy for enum@ietf.org; Mon, 23 Apr 2007 10:04:24 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hfz9U-0007E4-7W for enum@ietf.org; Mon, 23 Apr 2007 10:04:24 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 23 Apr 2007 16:04:24 +0200 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3NE4NXO027827; Mon, 23 Apr 2007 16:04:23 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3NE4Mlf020261; Mon, 23 Apr 2007 14:04:23 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 16:04:23 +0200 Received: from [127.0.0.1] ([144.254.226.40]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 16:04:22 +0200 In-Reply-To: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 Date: Mon, 23 Apr 2007 16:04:21 +0200 To: verdy_p@wanadoo.fr X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 23 Apr 2007 14:04:22.0721 (UTC) FILETIME=[4B49BB10:01C785B0] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1177; t=1177337063; x=1178201063; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paf@cisco.com; z=From:=20=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:=20Re=3A=20[Enum]=20RE=3A=20My=20prior=20art=20published=20in=20 august=202000=20to=20abusive=20US=20Patent=206,=20347,=20085 |Sender:=20; bh=ShV5fe92SgppnuKeGBL0GKKC+yMicgELgws9O654Qng=; b=RlhezcvFvVDijphr0+lFKl3k8B0zrw301O5JEORKitw0ECsWGqtYj+30aknOP0m4bheiS4VJ P43IuUatIJZDjxrQjAEF1bNwbkgZEsHGGRTeqo/+RGPWrT/yoG3fxh4F; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass (si g from cisco.com/amsdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 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 The first draft was released in 1998, under the name draft-faltstrom- e164-00.txt. I am sorry if you feel I forgot to mention you as someone that gave input to RFC 2916, but we must (simply) have talked beside each other. I.e. the first published IETF document on the matter was draft- faltstrom-e164-00.txt released December 1998. Patrik On 23 apr 2007, at 11.22, Philippe Verdy wrote: > Note that my message in the ICANN discussion list even predates RFC > 2916 > which was the first document published in a standard track in > September 2000 > by the IETF, and this old RFC is exactly what I described in August > 2000. > It's strange that I was not referenced in that RFC. Just before > that, the > last RFC was 2806 in April 2000 (URLs for telephone calls). But it > did not > describe the DNS registration system, only the syntax for several URI > schemes ("tel:", "modem:", "fax:") using the standard E.164 syntax for > specifying the phone number part. > > > > Philippe Verdy. > > _______________________________________________ > 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 Apr 23 10:26:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfzUg-0006lC-Vg; Mon, 23 Apr 2007 10:26:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HfzUf-0006kp-1h for enum@ietf.org; Mon, 23 Apr 2007 10:26:17 -0400 Received: from peregrine.verisign.com ([216.168.239.74]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfzUb-00075U-RP for enum@ietf.org; Mon, 23 Apr 2007 10:26:17 -0400 Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [10.170.12.113]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id l3NEctnv019054; Mon, 23 Apr 2007 10:38:55 -0400 Received: from dul1trutkow-l1.verisign.com ([10.26.0.226]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 10:26:06 -0400 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 23 Apr 2007 16:25:59 +0200 To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= , verdy_p@wanadoo.fr From: Tony Rutkowski Subject: Re: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 In-Reply-To: <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Message-ID: X-OriginalArrivalTime: 23 Apr 2007 14:26:08.0144 (UTC) FILETIME=[55617900:01C785B3] X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 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 At 04:04 PM 4/23/2007, Patrik F=E4ltstr=F6m wrote: >The first draft was released in 1998, under the=20 >name draft-faltstrom- e164-00.txt. I am Actually the prior art goes back to the drafts developed by Karl Malamud and Marshall T Rose in 1993. See RFC 1530 et seq. It was instantiatiated on tpc.int and has been in continuous use ever since. This is were the real innovation and "art" first arose. Malamad-Rose created the "art" and placed it in the public domain at that time. The art here is the use of a IP-based DNS resolver mechanism for E.164 numbers to reach a network terminal device. --tony=20 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 23 11:06:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg07C-0006q0-Vs; Mon, 23 Apr 2007 11:06:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg07C-0006pv-6N for enum@ietf.org; Mon, 23 Apr 2007 11:06:06 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg078-00053x-VP for enum@ietf.org; Mon, 23 Apr 2007 11:06:05 -0400 Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 23 Apr 2007 17:06:03 +0200 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l3NF62Le016799; Mon, 23 Apr 2007 17:06:02 +0200 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3NF61lb011104; Mon, 23 Apr 2007 15:06:01 GMT Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 17:06:01 +0200 Received: from [127.0.0.1] ([144.254.226.40]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 17:06:01 +0200 In-Reply-To: References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <872603D3-2544-4681-B2FF-69B7A374084F@cisco.com> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Subject: Re: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 Date: Mon, 23 Apr 2007 17:06:00 +0200 To: Tony Rutkowski X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 23 Apr 2007 15:06:01.0536 (UTC) FILETIME=[E7F41C00:01C785B8] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=972; t=1177340762; x=1178204762; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paf@cisco.com; z=From:=20=3D?ISO-8859-1?Q?Patrik_F=3DE4ltstr=3DF6m?=3D=20 |Subject:=20Re=3A=20[Enum]=20RE=3A=20My=20prior=20art=20published=20in=20 august=202000=20to=20abusive=20US=20Patent=206,=20347,=20085 |Sender:=20; bh=p4ow+Nn2E6+wHBW4kWNvywRuyDrGuud2BKYALRLvFRI=; b=u+VQU5wno/pgMYrUs2iRT5n3pwzca+0DxfxUpPN/p5hDSLMaPsPLGCvO/r0JTfTSNHCQf7WY RzUKRnMJLnhQEQwU53btFL+hpuS/EjCEdRZ8QgEVcdH9Yy/87PDp8zQt; Authentication-Results: ams-dkim-2; header.From=paf@cisco.com; dkim=pass (si g from cisco.com/amsdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: verdy_p@wanadoo.fr, enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org On 23 apr 2007, at 16.25, Tony Rutkowski wrote: > At 04:04 PM 4/23/2007, Patrik F=E4ltstr=F6m wrote: >> The first draft was released in 1998, under the name draft-=20 >> faltstrom- e164-00.txt. I am > > Actually the prior art goes back to the drafts developed by Karl =20 > Malamud > and Marshall T Rose in 1993. See RFC 1530 et seq. It was =20 > instantiatiated > on tpc.int and has been in continuous use ever since. This is were > the real innovation and "art" first arose. Malamad-Rose created the > "art" and placed it in the public domain at that time. The art =20 > here is the > use of a IP-based DNS resolver mechanism for E.164 numbers to reach > a network terminal device. Correct. I was "just" pointing out the history of RFC2916, without =20 talking about prior art to that RFC. Many documents where written =20 about E-164 and DNS. This tpc.int was probably the first =20 implementation that was live world-wide. Patrik _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 23 11:15:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0Gb-0007D7-0n; Mon, 23 Apr 2007 11:15:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0GZ-0007CY-8T for enum@ietf.org; Mon, 23 Apr 2007 11:15:47 -0400 Received: from vacation.karoshi.com ([198.32.6.68]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg0GX-000700-P1 for enum@ietf.org; Mon, 23 Apr 2007 11:15:47 -0400 Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id l3NFBkce017140; Mon, 23 Apr 2007 15:12:06 GMT Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id l3NFAY74017125; Mon, 23 Apr 2007 15:10:34 GMT Date: Mon, 23 Apr 2007 15:10:34 +0000 From: bmanning@karoshi.com To: Tony Rutkowski Subject: Re: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 Message-ID: <20070423151034.GC16827@vacation.karoshi.com.> References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by vacation.karoshi.com id l3NFBkce017140 X-Spam-Score: 1.1 (+) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: verdy_p@wanadoo.fr, enum@ietf.org, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= 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 Mon, Apr 23, 2007 at 04:25:59PM +0200, Tony Rutkowski wrote: > At 04:04 PM 4/23/2007, Patrik F=E4ltstr=F6m wrote: > >The first draft was released in 1998, under the=20 > >name draft-faltstrom- e164-00.txt. I am >=20 > Actually the prior art goes back to the drafts developed by Karl Malamu= d > and Marshall T Rose in 1993. See RFC 1530 et seq. It was instantiati= ated > on tpc.int and has been in continuous use ever since. This is were > the real innovation and "art" first arose. Malamad-Rose created the > "art" and placed it in the public domain at that time. The art here i= s the > use of a IP-based DNS resolver mechanism for E.164 numbers to reach > a network terminal device. >=20 > --tony=20 One might consider RFC 1183... =20 that work was key to the development of the TPC.INT idea that Carl and Marshall built. --bill _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 23 11:26:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0Qj-0007jS-8q; Mon, 23 Apr 2007 11:26:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0Kk-0000GF-Cs for enum@ietf.org; Mon, 23 Apr 2007 11:20:06 -0400 Received: from smtp24.orange.fr ([193.252.22.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg0Kj-0008P3-03 for enum@ietf.org; Mon, 23 Apr 2007 11:20:06 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2436.orange.fr (SMTP Server) with ESMTP id 388AC1C00097; Mon, 23 Apr 2007 17:20:04 +0200 (CEST) Received: from HARNON (APoitiers-156-1-5-204.w86-207.abo.wanadoo.fr [86.207.164.204]) by mwinf2436.orange.fr (SMTP Server) with ESMTP id D6FDA1C0008A; Mon, 23 Apr 2007 17:20:03 +0200 (CEST) X-ME-UUID: 20070423152003880.D6FDA1C0008A@mwinf2436.orange.fr From: "Philippe Verdy" To: =?iso-8859-1?Q?'Patrik_F=E4ltstr=F6m'?= , "'Tony Rutkowski'" References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> <733EF05A-F24A-4D5D-8371-FD61576D054F@cisco.com> <872603D3-2544-4681-B2FF-69B7A374084F@cisco.com> Subject: RE: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 Date: Mon, 23 Apr 2007 17:19:57 +0200 Organization: Ordinateur Personnel Message-ID: <000901c785ba$dad2ae40$0a01a8c0@rodage.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <872603D3-2544-4681-B2FF-69B7A374084F@cisco.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AceFuOjT/JDmRY4ZQHCX9g09iYdXHQAAM58g X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe X-Mailman-Approved-At: Mon, 23 Apr 2007 11:26:16 -0400 Cc: enum@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: verdy_p@wanadoo.fr List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org > De=A0: Patrik F=E4ltstr=F6m [mailto:paf@cisco.com] > Cc=A0: verdy_p@wanadoo.fr; enum@ietf.org > Objet=A0: Re: [Enum] RE: My prior art published in august 2000 to = abusive US > Patent 6, 347, 085 >=20 > On 23 apr 2007, at 16.25, Tony Rutkowski wrote: >=20 > > At 04:04 PM 4/23/2007, Patrik F=E4ltstr=F6m wrote: > >> The first draft was released in 1998, under the name draft- > >> faltstrom- e164-00.txt. I am > > > > Actually the prior art goes back to the drafts developed by Karl > > Malamud > > and Marshall T Rose in 1993. See RFC 1530 et seq. It was > > instantiatiated > > on tpc.int and has been in continuous use ever since. This is were > > the real innovation and "art" first arose. Malamad-Rose created = the > > "art" and placed it in the public domain at that time. The art > > here is the > > use of a IP-based DNS resolver mechanism for E.164 numbers to reach > > a network terminal device. >=20 > Correct. I was "just" pointing out the history of RFC2916, without > talking about prior art to that RFC. Many documents where written > about E-164 and DNS. This tpc.int was probably the first > implementation that was live world-wide. I didnot want to make money with this. Because I really thought that = what I gave online on the ICANN mailing list was quite basic, and correctly describing what was finally published by the IETF in its RFC. Regarding filing dates, it's possible, because I don't know much about = the US patent system, I only swathe publication date. Is it what you = callafull disclosure or IP rights? I also note the signature of the Patent: it was an IETF participant at = least at end of 1999, and probably in mid-2000 as well, so theirs is real = doubt about his honesty (but this is difficult to judge now, given that the disclosure of IP rights assignments were secured only in the last few years.) If I come so late on this issue, it's only because I rediscovered my old message archived on ICANN server along with the patent claim, using a = google search on my own name. Thanks for your reply. I hop that my message will not cause you more = legal harassment with this Patent, and this was really disturbing for me, to = see that you were abused, for something that I discussed before the patent = was disclosed publicly in late 2006. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Apr 25 10:38:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgidJ-0005YY-5k; Wed, 25 Apr 2007 10:38:13 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HgidH-0005Wa-V8; Wed, 25 Apr 2007 10:38:11 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HgidG-0006AE-Mw; Wed, 25 Apr 2007 10:38:11 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9B73B2AC79; Wed, 25 Apr 2007 14:37:40 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hgicm-0000DA-DJ; Wed, 25 Apr 2007 10:37:40 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 25 Apr 2007 10:37:40 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: enum@ietf.org Subject: [Enum] Last Call: draft-ietf-enum-xmpp (IANA Registration for Enumservice 'XMPP') to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has received a request from the Telephone Number Mapping WG (enum) to consider the following document: - 'IANA Registration for Enumservice 'XMPP' ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-05-09. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-enum-xmpp-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15492&rfc_flag=0 _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Wed Apr 25 15:56:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgnbe-0004QH-7i; Wed, 25 Apr 2007 15:56:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgnba-0004Nt-LL for enum@ietf.org; Wed, 25 Apr 2007 15:56:46 -0400 Received: from sccrmhc11.comcast.net ([204.127.200.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgnbY-00045a-C1 for enum@ietf.org; Wed, 25 Apr 2007 15:56:46 -0400 Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (sccrmhc11) with ESMTP id <2007042519564301100fjtsce>; Wed, 25 Apr 2007 19:56:43 +0000 Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l3PJuhUA025277 for ; Wed, 25 Apr 2007 15:56:43 -0400 Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l3PJuhPn025273; Wed, 25 Apr 2007 15:56:43 -0400 Date: Wed, 25 Apr 2007 15:56:43 -0400 Message-Id: <200704251956.l3PJuhPn025273@dragon.ariadne.com> To: enum@ietf.org From: Dale.Worley@comcast.net In-reply-to: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> (verdy_p@wanadoo.fr) Subject: Re: [Enum] RE: My prior art published in august 2000 to abusive US Patent 6, 347, 085 References: <008e01c78588$d98ad7b0$0a01a8c0@rodage.dyndns.org> X-Spam-Score: 0.2 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 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 From: "Philippe Verdy" Note that my message in the ICANN discussion list even predates RFC 2916 which was the first document published in a standard track in September 2000 by the IETF, and this old RFC is exactly what I described in August 2000. It's strange that I was not referenced in that RFC. Just before that, the last RFC was 2806 in April 2000 (URLs for telephone calls). But it did not describe the DNS registration system, only the syntax for several URI schemes ("tel:", "modem:", "fax:") using the standard E.164 syntax for specifying the phone number part. Looking at the Patent Office's copy of the patent http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PTXT&s1=6347085.PN.&OS=PN/6347085&RS=PN/6347085 I see that the filing date is 14-August-1997. If I remember correctly, US law uses a "first to invent" system, and the inventor has 1 year after the first public disclosure of the invention to submit the patent application. So basically anyone who can prove they invented the same thing before August 1996 can invalidate this patent. Anything after August 1997 is irrelevant. The best proof of a prior invention is some sort of archived publication. At a first glance, RFC 1530 does not directly invalidate the patent because the patent is rather narrow: Claim 1: In a process [...] telephone numbers having area code, exchange, and subscriber segments, each segment comprising a sequence of numbers, the method comprising: A. generating a telephone number domain name identifying a telephone number by reversing the order in which the segments of the telephone number were received without modifying the sequence of numbers within each segment; That is, RFC 1530 turns +1 800 555 1234 into 4.3.2.1.5.5.5.0.0.8.1.tpc.in., the patent turns it into 1234.555.800.1.example.com., which is not precisely the same. (Though at least claim 1 doesn't even address country codes.) At this point, it doesn't look like the patent applies to ENUM resolution. (Of course, I am not a lawyer, and I haven't even read all the claims in the patent.) Dale _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Thu Apr 26 10:28:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh4wx-000845-Q6; Thu, 26 Apr 2007 10:27:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh4ww-00083j-Aw; Thu, 26 Apr 2007 10:27:58 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh4wv-0006VX-PZ; Thu, 26 Apr 2007 10:27:58 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5A23226EC0; Thu, 26 Apr 2007 14:27:57 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hh4wv-0003AG-8P; Thu, 26 Apr 2007 10:27:57 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Thu, 26 Apr 2007 10:27:57 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: enum mailing list , enum chair , Internet Architecture Board , RFC Editor Subject: [Enum] Protocol Action: 'IANA Registration for vCard Enumservice' to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org The IESG has approved the following document: - 'IANA Registration for vCard Enumservice ' as a Proposed Standard This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Jon Peterson and Cullen Jennings. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-vcard-06.txt Technical Summary The document proposes an Enumservice to refer from an E.164 number to URIs addressing "vCards" (electronic business cards). The document considers 3 different formats for those vCards, and uses http/https URIs to access those cards. Working Group Summary Generally, this document is part of a series of straightforward Enumservice registrations which are handled by the ENUM WG according to the registration process in RFC 3761. The document was on the schedule of two ENUM WG sessions, and has generally enjoyed the appreciation of the group. Most concerns were related to the potential issues of publishing PII data - subsequent revisions of the document addressed those concerns. Protocol Quality This document was reviewed for the IESG by Jon Peterson. An experimental implementation based on the Asterisk soft-PBX is currently under development by the author. _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From enum-bounces@ietf.org Mon Apr 30 13:53:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hia4H-0005NJ-AM; Mon, 30 Apr 2007 13:53:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hia4F-0005NE-Oz for enum@ietf.org; Mon, 30 Apr 2007 13:53:43 -0400 Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hia4E-0007Kd-6R for enum@ietf.org; Mon, 30 Apr 2007 13:53:43 -0400 Received: from rshockeyPC (neustargw.va.neustar.com [209.173.53.233]) (authenticated bits=0) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id l3UHrRc3018152 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 30 Apr 2007 10:53:28 -0700 From: "Richard Shockey" To: Date: Mon, 30 Apr 2007 13:52:41 -0400 Message-ID: <010a01c78b50$59fa2a00$0dee7e00$@us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_010B_01C78B2E.D2E88A00" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceLS2/t2mTH2d0eTZycCT6IH4pZvQABOSHw Content-Language: en-us X-SongbirdInformation: support@songbird.com for more information X-Songbird: Clean X-Songbird-From: richard@shockey.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Subject: [Enum] FW: Last Call: draft-ietf-enum-xmpp (IANA Registration for Enumservice 'XMPP') to Proposed Standard X-BeenThere: enum@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enum Discussion List List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: enum-bounces@ietf.org This is a multipart message in MIME format. ------=_NextPart_000_010B_01C78B2E.D2E88A00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit -----Original Message----- From: Peter Saint-Andre [mailto:stpeter@jabber.org] Sent: Monday, April 30, 2007 1:18 PM To: ietf@ietf.org Subject: Re: Last Call: draft-ietf-enum-xmpp (IANA Registration for Enumservice 'XMPP') to Proposed Standard The IESG wrote: > The IESG has received a request from the Telephone Number Mapping WG > (enum) to consider the following document: > > - 'IANA Registration for Enumservice 'XMPP' ' > as a Proposed Standard In the Introduction, this I-D says: RFC 4622 [6] registers an Internationalized Resource Identifier (IRI) [5] and Uniform Resource Identifier (URI) scheme for identifying XMPP entities. There is no such thing as an IRI scheme, so the author may want to correct the text; here is suggested wording: RFC 4622 [6] registers a Uniform Resource Identifier (URI) scheme for identifying an XMPP entity as a URI or as an Internationalized Resource Identifier (IRI) [5]. There are some errors in RFC 4622, which I have attempted to correct in draft-saintandre-rfc4622bis: http://www.ietf.org/internet-drafts/draft-saintandre-rfc4622bis-00.txt However, I don't think those corrections materially affect the ENUM registration in draft-ietf-enum-xmpp. To verify that statement, refer to the following diff: http://tools.ietf.org/rfcdiff?url1=http%3A%2F%2Ftools.ietf.org%2Frfc%2Frfc46 22.txt&url2=http%3A%2F%2Fwww.xmpp.org%2Finternet-drafts%2Fdraft-saintandre-r fc4622bis-00.txt&difftype=--hwdiff Peter -- Peter Saint-Andre XMPP Standards Foundation http://www.xmpp.org/xsf/people/stpeter.shtml ------=_NextPart_000_010B_01C78B2E.D2E88A00 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIYVDCCB3Aw ggbZoAMCAQICAQkwDQYJKoZIhvcNAQEEBQAwgbAxCzAJBgNVBAYTAklMMQ8wDQYDVQQIEwZJc3Jh ZWwxDjAMBgNVBAcTBUVpbGF0MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMRowGAYDVQQLExFDQSBB dXRob3JpdHkgRGVwLjEpMCcGA1UEAxMgRnJlZSBTU0wgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkx ITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZzAeFw0wNTA0MDUxNDUxMDNaFw0xMDA0 MDQxNDUxMDNaMIGvMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFy dENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2VydGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMm U3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVtYWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFk bWluQHN0YXJ0Y29tLm9yZzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOOY75tn3Yhi COsNXQn9/4WfpNrX8HLIUlBTLrGtMINvcYJ03Nlr9kJyOF5Z8g+2G9Zg+zN8iWGBEpl37bgjYdea 3q0AaO9uyZOMLa0rztjFeo7Uw8AjdDmWkaJQU1c6q9OoieOT6Tf4MvHMGqtbnaOL3Xvz4o6XnH+E k9h8zPgYgiUw2tIF0ueLayTGiInHdWM5eYMoz7OnVlUeIurDweT4C9V1TtwplnhWZ7bilcuN4w3/ 8hndqryqqflbCMlLZWn+1uaT21d12cdpjBOaqtg6hqiTY4S4+wVAmGrAiOPQ3Z574gljhUKf5ehz 7p9xtsb+mjvM1I4yPP8/vjKZoRUCAwEAAaOCBBMwggQPMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0P BAQDAgHmMB0GA1UdDgQWBBS4Zr17owi6irSy+USIcU+li0GzUTCB3QYDVR0jBIHVMIHSgBQcicOW zL3+MtUNjIExtpidjShkjaGBtqSBszCBsDELMAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEO MAwGA1UEBxMFRWlsYXQxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xGjAYBgNVBAsTEUNBIEF1dGhv cml0eSBEZXAuMSkwJwYDVQQDEyBGcmVlIFNTTCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEhMB8G CSqGSIb3DQEJARYSYWRtaW5Ac3RhcnRjb20ub3JnggEAMB0GA1UdEQQWMBSBEmFkbWluQHN0YXJ0 Y29tLm9yZzAdBgNVHRIEFjAUgRJhZG1pbkBzdGFydGNvbS5vcmcwYgYDVR0fBFswWTApoCegJYYj aHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NhLWNybC5jcmwwLKAqoCiGJmh0dHA6Ly9jcmwuc3Rh cnRjb20ub3JnL2NybC9jYS1jcmwuY3JsMIIBSgYDVR0gBIIBQTCCAT0wggE5BgsrBgEEAYG1NwEB ATCCASgwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUG CCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCBvQYI KwYBBQUHAgIwgbAwFBYNU3RhcnRDb20gTHRkLjADAgEBGoGXTGltaXRlZCBMaWFiaWxpdHksIHJl YWQgdGhlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRDb20gQ2VydGlm aWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8vY2VydC5zdGFydGNv bS5vcmcvcG9saWN5LnBkZjARBglghkgBhvhCAQEEBAMCAAcwUAYJYIZIAYb4QgENBEMWQVN0YXJ0 Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgRnJlZSBTU0wgRW1haWwgQ2VydGlmaWNh dGVzMDIGCWCGSAGG+EIBBAQlFiNodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDAz BglghkgBhvhCAQMEJhYkaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydC1jcmwuY3JsMDIGCWCG SAGG+EIBCAQlFiNodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjANBgkqhkiG9w0B AQQFAAOBgQDss9KKFx/bCifYjAQTmBtRoHFsdR5ZQ1nlagXKoyJ+IwmdGdiYqAKeaDfjT6bTXHfQ vK8kp5xSoz0IPcpSwztY7UKtylgJwplu1q6vjj4BGB621sD60qzirAhLSqxmpBgjl8HMMMoiM28D CLsshihlg7wG7Oi/rPIuR8dawiaDejCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCB rzELMAkGA1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEj MCEGA1UECxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29tIENs YXNzIDIgUHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNv bS5vcmcwHhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBTb2Z0d2FyZSBGb3Vu ZGF0aW9uMS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQGphYmJlci5v cmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCrzNmM5bxrSxV81PynU608wdGBJaKs 0I7Y93//cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6KozXDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaG ANVRexbuxToFF0q3YoO/NLIQXiuIu8BbNl0BHmZzBHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RI RZJwnflJF50VJi8rxYpL6H9W5q9zYtLurjAd0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubd pmCVJMy6X2zGtKoPfo7LdoOEWbTSCEVubA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/d YDnuUaQpAgMBAAGjggR+MIIEejAMBgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAU BggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNV HSMEgdUwgdKAFLhmvXujCLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0G A1UECBMGSXNyYWVsMQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgG A1UECxMRQ0EgQXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24g QXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAE ggE3MIIBMzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3Rh cnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0 Y29tLm9yZy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQuMAMCAQEa gY1MaW1pdGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMq IG9mIHRoZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDov L2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAsoCqgKIYmaHR0cDovL2Nl cnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRjb20u b3JnL2NydHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3BggrBgEFBQcwAYYraHR0cDovL29j c3Auc3RhcnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9jYTA7BggrBgEFBQcwAoYvaHR0cDovL2Nl cnQuc3RhcnRjb20ub3JnL3N1Yi5jbGFzczIudXNlci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWg MDcGCWCGSAGG+EIBDQQqFihTdGFydENvbSBBdXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRl MDIGCWCGSAGG+EIBBAQlFiNodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1Bglg hkgBhvhCAQMEKBYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZI AYb4QgEIBCUWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqG GGh0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm /7dSnbT+613ejmlbDG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4 /aPJpgm4bxJn0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zL rAv0CVxhBOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+ UPKMLTSSQfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZ uYJCLgc0S5jgHntNU6X/STCCCGwwggdUoAMCAQICAwDocDANBgkqhkiG9w0BAQUFADCBrzELMAkG A1UEBhMCSUwxDzANBgNVBAgTBklzcmFlbDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEjMCEGA1UE CxMaU2VjdXJlIENlcnRpZmljYXRlIFNpZ25pbmcxLzAtBgNVBAMTJlN0YXJ0Q29tIENsYXNzIDIg UHJpbWFyeSBFbWFpbCBGcmVlIENBMSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmcw HhcNMDYwNzA3MTYwNTAwWhcNMDcwNzA3MTYwNTAwWjCBvjELMAkGA1UEBhMCVVMxCzAJBgNVBAgT AkNPMQ8wDQYDVQQHEwZEZW52ZXIxIzAhBgNVBAoTGkphYmJlciBTb2Z0d2FyZSBGb3VuZGF0aW9u MS0wKwYDVQQLEyRTdGFydENvbSBWZXJpZmllZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMT EVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQGphYmJlci5vcmcwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCrzNmM5bxrSxV81PynU608wdGBJaKs0I7Y93// cyNPaooH0M1P20FAkmVjNZ2DhHsb4J4H6KozXDJWVpY04lIS7JIhcmy1pL2Aac0ZvPaGANVRexbu xToFF0q3YoO/NLIQXiuIu8BbNl0BHmZzBHKgsofvKlsLDTQjen85U5GY2Rgg0yRd5/RIRZJwnflJ F50VJi8rxYpL6H9W5q9zYtLurjAd0SSdtCY98YG73vYJyZ5V0ARBUAkc4tg50/XJvubdpmCVJMy6 X2zGtKoPfo7LdoOEWbTSCEVubA0EQSTlybkGnnkG97Kn44lqm7UGpMWx76IGZQ3IrM/dYDnuUaQp AgMBAAGjggR+MIIEejAMBgNVHRMEBTADAgEAMAsGA1UdDwQEAwIE8DAdBgNVHSUEFjAUBggrBgEF BQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFGvThDnN4P4ucEfDmnKw2an31COrMIHdBgNVHSMEgdUw gdKAFLhmvXujCLqKtLL5RIhxT6WLQbNRoYG2pIGzMIGwMQswCQYDVQQGEwJJTDEPMA0GA1UECBMG SXNyYWVsMQ4wDAYDVQQHEwVFaWxhdDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEaMBgGA1UECxMR Q0EgQXV0aG9yaXR5IERlcC4xKTAnBgNVBAMTIEZyZWUgU1NMIENlcnRpZmljYXRpb24gQXV0aG9y aXR5MSEwHwYJKoZIhvcNAQkBFhJhZG1pbkBzdGFydGNvbS5vcmeCAQkwggFABgNVHSAEggE3MIIB MzCCAS8GCysGAQQBgbU3AQECMIIBHjA1BggrBgEFBQcCARYpaHR0cDovL2NlcnQuc3RhcnRjb20u b3JnL2ludGVybWVkaWF0ZS5wZGYwLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9y Zy9wb2xpY3kucGRmMIGzBggrBgEFBQcCAjCBpjAUFg1TdGFydENvbSBMdGQuMAMCAQEagY1MaW1p dGVkIExpYWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRo ZSBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwZAYDVR0fBF0wWzAsoCqgKIYmaHR0cDovL2NlcnQuc3Rh cnRjb20ub3JnL2NydHUyLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRjb20ub3JnL2Ny dHUyLWNybC5jcmwwgYQGCCsGAQUFBwEBBHgwdjA3BggrBgEFBQcwAYYraHR0cDovL29jc3Auc3Rh cnRjb20ub3JnL3N1Yi9jbGFzczIvdXNlci9jYTA7BggrBgEFBQcwAoYvaHR0cDovL2NlcnQuc3Rh cnRjb20ub3JnL3N1Yi5jbGFzczIudXNlci5jYS5jcnQwEQYJYIZIAYb4QgEBBAQDAgWgMDcGCWCG SAGG+EIBDQQqFihTdGFydENvbSBBdXRoZW50aWNhdGVkIEVtYWlsIENlcnRpZmljYXRlMDIGCWCG SAGG+EIBBAQlFiNodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvY2EtY3JsLmNybDA1BglghkgBhvhC AQMEKBYmaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL2NydHUyLWNybC5jcmwwMgYJYIZIAYb4QgEI BCUWI2h0dHA6Ly9jZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMCMGA1UdEgQcMBqGGGh0dHA6 Ly9jZXJ0LnN0YXJ0Y29tLm9yZzANBgkqhkiG9w0BAQUFAAOCAQEAi8Q3OPqmaAnBgIBm/7dSnbT+ 613ejmlbDG6f00pgf+PVLyidelTcCbZckHJvH/Q2tQweEtMVluY5NhELU/gwL9VD0Yn4/aPJpgm4 bxJn0/GeWmqcASfcBwb1XgrZDe17rD22YniJdSP4E6VXWxcS2elHdD08yTPlX+Cab9zLrAv0CVxh BOYdDX6aNqY5/YxIfdaJKWClkAz+/GRUI24HSMly9SLEz2Lhvz2WitBflWE4+aOIJx7+UPKMLTSS Qfk4WjwTOrQgpc9kjja0q7RdNXOPzOV7WehZo9sUncrIDDg5RkcoclifwOWXe66l6HKZuYJCLgc0 S5jgHntNU6X/STGCBCwwggQoAgEBMIG3MIGvMQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVs MRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMwIQYDVQQLExpTZWN1cmUgQ2VydGlmaWNhdGUgU2ln bmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEVtYWlsIEZyZWUgQ0ExITAf BgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29tLm9yZwIDAOhwMAkGBSsOAwIaBQCgggJJMBgGCSqG SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA3MDQzMDE3MTgxNlowIwYJKoZI hvcNAQkEMRYEFDitTU+r/dqD8B5VdDJPuKtVMq/MMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEo MIHIBgkrBgEEAYI3EAQxgbowgbcwga8xCzAJBgNVBAYTAklMMQ8wDQYDVQQIEwZJc3JhZWwxFjAU BgNVBAoTDVN0YXJ0Q29tIEx0ZC4xIzAhBgNVBAsTGlNlY3VyZSBDZXJ0aWZpY2F0ZSBTaWduaW5n MS8wLQYDVQQDEyZTdGFydENvbSBDbGFzcyAyIFByaW1hcnkgRW1haWwgRnJlZSBDQTEhMB8GCSqG SIb3DQEJARYSYWRtaW5Ac3RhcnRjb20ub3JnAgMA6HAwgcoGCyqGSIb3DQEJEAILMYG6oIG3MIGv MQswCQYDVQQGEwJJTDEPMA0GA1UECBMGSXNyYWVsMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSMw IQYDVQQLExpTZWN1cmUgQ2VydGlmaWNhdGUgU2lnbmluZzEvMC0GA1UEAxMmU3RhcnRDb20gQ2xh c3MgMiBQcmltYXJ5IEVtYWlsIEZyZWUgQ0ExITAfBgkqhkiG9w0BCQEWEmFkbWluQHN0YXJ0Y29t Lm9yZwIDAOhwMA0GCSqGSIb3DQEBAQUABIIBAKCGEG1rlYCEx5rwVpdQ2cVLE9da/F+ZCiaJjD1J c/vTjEt+0VP2cymeAPVtNnTdGSZxFS5tCiDFCp0x4LpT7UkszzjpZYI6pjRP0UFXEgLPMRylCQNw Gm6Y3gwhAzQ5ewr+VO6BgDrxShmFDs//ykKgGyhw5gVyMfCX5af/RTtL5cPt4yjcKuWFI53v3G7C soISgWFYnrTfCaxMnY4oYkyb+QqltZLzT4byZB3omb15Lhm/gRrsWydP6tQyJZp6sJFYwPmZWDUO b2NMBzV8qKBi6n4zSdDFtjOrpFjk762vLKWgO38FMt8VvBC9d7knrOhM7kjHWaKq+X3eHp4UsT0A AAAAAAA= ------=_NextPart_000_010B_01C78B2E.D2E88A00 Content-Type: text/plain; name="ATT00224.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00224.txt" _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf ------=_NextPart_000_010B_01C78B2E.D2E88A00 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum ------=_NextPart_000_010B_01C78B2E.D2E88A00-- From enum-bounces@ietf.org Mon Apr 30 15:50:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hibsq-0004B9-83; Mon, 30 Apr 2007 15:50:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hibso-0004Ar-Qn; Mon, 30 Apr 2007 15:50:02 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hibso-0003cT-IC; Mon, 30 Apr 2007 15:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8449B328F6; Mon, 30 Apr 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hibso-0001ky-CM; Mon, 30 Apr 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 30 Apr 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: enum@ietf.org Subject: [Enum] I-D ACTION:draft-ietf-enum-softswitch-req-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 : ENUM-based Softswitch Requirement Author(s) : J. Lim, et al. Filename : draft-ietf-enum-softswitch-req-00.txt Pages : 17 Date : 2007-4-30 This document describes experiences of operational requirements and several considerations for ENUM-based softswitches concerning call routing between two Korean VoIP carriers, gained during the ENUM pre- commercial trial hosted by National Internet Development Agency of Korea (NIDA) in 2006. These experiences show that an interim solution can maintain the stability of on-going commercial softswitch system operations during the initial stage of ENUM service, where the DNS does not have sufficient data for the majority of calls. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-enum-softswitch-req-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-softswitch-req-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-softswitch-req-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-4-30142344.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-enum-softswitch-req-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-enum-softswitch-req-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-4-30142344.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--