From mailnull@www1.ietf.org Sun Dec 1 10:45:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08264 for ; Sun, 1 Dec 2002 10:45:24 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB1Fli512182 for enum-archive@odin.ietf.org; Sun, 1 Dec 2002 10:47:44 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB1FlZv12169; Sun, 1 Dec 2002 10:47:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB1Fkbv12150 for ; Sun, 1 Dec 2002 10:46:37 -0500 Received: from ams-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08251 for ; Sun, 1 Dec 2002 10:43:46 -0500 (EST) Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB1Fiq8v017189; Sun, 1 Dec 2002 16:44:52 +0100 (MET) Received: from xfe-ams-302.cisco.com ([144.254.75.89]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Sun, 1 Dec 2002 16:46:12 +0100 Received: from cisco.com ([144.254.74.55]) by xfe-ams-302.cisco.com with Microsoft SMTPSVC(5.0.2195.4453); Sun, 1 Dec 2002 16:46:10 +0100 Date: Sun, 1 Dec 2002 16:46:10 +0100 Subject: Re: [Enum] New version of rfc2916bis Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v548) Cc: Stastny Richard , enum@ietf.org To: Michael Mealling From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= In-Reply-To: <1038236289.21972.122.camel@blackdell.neonym.net> Message-Id: <0387104A-0544-11D7-A024-0003934B2128@cisco.com> X-Mailer: Apple Mail (2.548) X-OriginalArrivalTime: 01 Dec 2002 15:46:11.0914 (UTC) FILETIME=[C60F9AA0:01C29950] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gB1Fkcv12151 Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit On måndag, nov 25, 2002, at 15:58 Europe/Stockholm, Michael Mealling wrote: > I actually like the previous version of the example. I would like some > text discussing the fact that the h323 service subtypes based on > function class while the last record defines function classes as > services and then subtypes based on how that service is expressed. This is a message to all people on this mailing list. I get complaints on the examples, but not any text I can use. If you just send me text, I am happy to create a new document with better examples and more/better text. Please... paf _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Tue Dec 3 14:35:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12380 for ; Tue, 3 Dec 2002 14:35:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB3Jc9W08518 for enum-archive@odin.ietf.org; Tue, 3 Dec 2002 14:38:09 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB3Jc2v08513; Tue, 3 Dec 2002 14:38:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB3JaNv07809 for ; Tue, 3 Dec 2002 14:36:23 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12223; Tue, 3 Dec 2002 14:33:28 -0500 (EST) Message-Id: <200212031933.OAA12223@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , enum@ietf.org From: The IESG Date: Tue, 03 Dec 2002 14:33:28 -0500 Subject: [Enum] Document Action: Number Portability in the GSTN: An Overview to Informational Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , The IESG has approved 'Number Portability in the GSTN: An Overview' as an Informational RFC. This document is the product of the Telephone Number Mapping Working Group. The IESG contact persons are Scott Bradner and Allison Mankin. Note to RFC Editor: Please replace the current text in the Security Conserations section with the following: "In the PSTN, the NPDB queries are generated by the PSTN switches and carried over the SS7 networks to reach the NPDBs and back to the switches. The SS7 networks are operated by telecommunications operators and signaling transport service providers in such a closed environment that make them difficult for the hackers to penetrate. However, when VoIP operators need the NP information and have to launch the NP queries from their softswitches, media gateway controllers or call managers, there would be security concerns if the NP queries and responses are transported over Internet. If the routing number or routing prefix in the response is altered during the message transport, the call will be routed to the wrong place. It is recommended that the NPDB queries be transported via a secure transport layer or with added security mechanisms to ensure the data integrity." _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Wed Dec 11 14:12:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16950 for ; Wed, 11 Dec 2002 14:12:44 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBBJFCv15406 for enum-archive@odin.ietf.org; Wed, 11 Dec 2002 14:15:12 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBJEtv15389; Wed, 11 Dec 2002 14:14:56 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBGxwv07491 for ; Wed, 11 Dec 2002 11:59:58 -0500 Received: from msr.hinet.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12515 for ; Wed, 11 Dec 2002 11:56:58 -0500 (EST) Received: from clevonote (61-231-9-60.HINET-IP.hinet.net [61.231.9.60]) by msr.hinet.net (8.9.3/8.9.3) with SMTP id AAA07999 for ; Thu, 12 Dec 2002 00:59:52 +0800 (CST) From: "sheng-wang" To: Date: Thu, 12 Dec 2002 01:10:42 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id gBBGxwv07492 Subject: [Enum] Question for ENUM supporting VoIP service Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hello, ENUM porvide a directory-like mechanism to support many services. VoIP is expected to be the first potential application currently. If we use ENUM to support VOIP service, I am concerned about two issues: 1. Is it necessary to make a enum DNS query for each call ? If it is true, there will be call set up delay-time performance issues, especially when you make a call that will be destined to international domain, there will be many tiers DNS query . How to handle this ? 2. Is it necessary to allocatte special number for users who wants VoIP with ENUM service? Any response or pointer will be appreciated. Simon Yu _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Wed Dec 11 14:12:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16963 for ; Wed, 11 Dec 2002 14:12:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBBJFGU15435 for enum-archive@odin.ietf.org; Wed, 11 Dec 2002 14:15:16 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBJFGv15428; Wed, 11 Dec 2002 14:15:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBH7vv08799 for ; Wed, 11 Dec 2002 12:07:57 -0500 Received: from msr.hinet.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12764 for ; Wed, 11 Dec 2002 12:04:58 -0500 (EST) Received: from clevonote (61-231-9-60.HINET-IP.hinet.net [61.231.9.60]) by msr.hinet.net (8.9.3/8.9.3) with SMTP id BAA05253 for ; Thu, 12 Dec 2002 01:07:50 +0800 (CST) From: "sheng-wang" To: Date: Thu, 12 Dec 2002 01:18:41 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id gBBH7vv08800 Subject: [Enum] RE: Question for ENUM supporting VoIP service Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit -----Original Message----- From: sheng-wang [mailto:swyu@cht.com.tw] Sent: Thursday, December 12, 2002 1:11 AM To: enum@ietf.org Subject: Question for ENUM supporting VoIP service Hello, ENUM porvide a directory-like mechanism to support many services. VoIP is expected to be the first potential application currently. If we use ENUM to support VOIP service, I am concerned about two issues: 1. Is it necessary to make a enum DNS query for each call ? If it is true, there will be call set up delay-time performance issues, especially when you make a call that will be destined to international domain, there will be many tiers DNS query . How to handle this ? 2. Is it necessary to allocatte special number for users who wants VoIP with ENUM service? Any response or pointer will be appreciated. Simon Yu _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Thu Dec 12 11:04:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28914 for ; Thu, 12 Dec 2002 11:04:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBCG73U28535 for enum-archive@odin.ietf.org; Thu, 12 Dec 2002 11:07:03 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCG6wv28482; Thu, 12 Dec 2002 11:06:58 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCG50v28388 for ; Thu, 12 Dec 2002 11:05:00 -0500 Received: from oak.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28805 for ; Thu, 12 Dec 2002 11:02:00 -0500 (EST) Received: from dick.neustar.com (stih650b-eth-s1p2c0.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id gBCG4tZ26145 for ; Thu, 12 Dec 2002 16:04:55 GMT Message-Id: <5.2.0.9.2.20021212100804.02523620@popd.ix.netcom.com> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 12 Dec 2002 11:06:30 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Revised ENUM milestones and directions. Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Based on some of the work in Atlanta we will need to update our Goals and Milestones to reflect this. What we currently have is this .... Goals and Milestones: Done Initial draft of Service ENUM Requirements Done Initial draft of ENUM Protocol Done Revised draft of ENUM Protocol Done Submit ENUM Protocol document to IESG for publication as Proposed JUN 02 Revise and update RFC 2916 appropriate to DDDS (revision of 2915) and advance to Draft Standard JUL 02 Document appropriate ENUM Registration and Provisioning Procedures (Informational) AUG 02 Document appropriate ENUM Operational Security, Privacy Issues and Procedures (Informational) What I'd like to propose is this: In particular I'd like the WG and especially the authors of 2916bis to commit to a full discussion of the relevant issues so we can bring this document to last call well in advance of San Francisco. We now have 2 other WG dependant on 2916bis FAX and VPIM and our own documents on enum service registration for SIP and H.323. There are clear issues on how NAPTR records are processed etc. Goals and Milestones: Done Initial draft of Service ENUM Requirements Done Initial draft of ENUM Protocol Done Revised draft of ENUM Protocol Done Submit ENUM Protocol document to IESG for publication as Proposed APR 03 Revise and update RFC 2916 appropriate to DDDS (revision of 2915) JUNE 03 ENUM service registrations for SIP and H.323 AUG 03 Document appropriate ENUM Security and Privacy Issues (Informational) NOV 03 Document appropriate ENUM Registration and Provisioning Procedures (Informational) Thoughts and comments... >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Thu Dec 12 15:38:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11680 for ; Thu, 12 Dec 2002 15:38:25 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBCKeuu14874 for enum-archive@odin.ietf.org; Thu, 12 Dec 2002 15:40:56 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCKecv14862; Thu, 12 Dec 2002 15:40:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBCKahv14081 for ; Thu, 12 Dec 2002 15:36:43 -0500 Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11458 for ; Thu, 12 Dec 2002 15:33:40 -0500 (EST) Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id gBCKaCjS003466; Thu, 12 Dec 2002 12:36:12 -0800 (PST) Received: from DWINGW2K4 (mgy-w2k1.cisco.com [128.107.139.124]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with SMTP id ACM28958; Thu, 12 Dec 2002 12:35:43 -0800 (PST) From: "Dan Wing" To: "sheng-wang" , Subject: RE: [Enum] Question for ENUM supporting VoIP service Date: Thu, 12 Dec 2002 12:36:33 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="BIG5" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: Importance: Normal Content-Transfer-Encoding: 7bit Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit > 1. Is it necessary to make a enum DNS query for each call ? If it > is true, there will be call set up delay-time performance > issues, especially when you make a call that will be destined to > international domain, there will be many tiers DNS query . How to > handle this ? Today, on the Internet, all hostname lookups (www.cnn.com) require a DNS query. DNS names are usually resolved in less than 50ms. Today, on the PSTN, with local number portability, there is also per-call lookup overhead. > 2. Is it necessary to allocatte special number for users who > wants VoIP with ENUM service? There is no requirement in ENUM itself. However, there may be government requirements or user expectations for such assignments. For example, GSM cellular phones are billed so that the caller pays for airtime. Because of this, GSM cellular phone numbers are assigned numbers to allow knowledgable individuals to identify the called party is on a cellular phone. However, GSM itself doesn't require such assignments. Similarly, ENUM itself doesn't require such assignments. -d _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Tue Dec 17 15:48:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23244 for ; Tue, 17 Dec 2002 15:48:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBHKpLJ03211 for enum-archive@odin.ietf.org; Tue, 17 Dec 2002 15:51:21 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBHKpCv03204; Tue, 17 Dec 2002 15:51:12 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBHKlFv03080 for ; Tue, 17 Dec 2002 15:47:15 -0500 Received: from oak.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23179 for ; Tue, 17 Dec 2002 15:44:09 -0500 (EST) Received: from dick.neustar.com (stih650b-eth-s1p2c0.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id gBHKl9Z18928 for ; Tue, 17 Dec 2002 20:47:09 GMT Message-Id: <5.2.0.9.2.20021217154654.02347e78@popd.ix.netcom.com> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 17 Dec 2002 15:48:52 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Revised Goals and Milestones Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , I have not heard any comments on my posting on revised goals and milestones ... I'm going to assume that if I have not heard anything in a week or so that silence is consent and I will modify the information accordingly. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum From mailnull@www1.ietf.org Tue Dec 17 15:59:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23530 for ; Tue, 17 Dec 2002 15:59:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBHL2V203652 for enum-archive@odin.ietf.org; Tue, 17 Dec 2002 16:02:31 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBHL2Vv03647; Tue, 17 Dec 2002 16:02:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBHKwwv03471 for ; Tue, 17 Dec 2002 15:58:58 -0500 Received: from oak.neustar.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23453 for ; Tue, 17 Dec 2002 15:55:52 -0500 (EST) Received: from dick.neustar.com (stih650b-eth-s1p2c0.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id gBHKwqZ19196 for ; Tue, 17 Dec 2002 20:58:52 GMT Message-Id: <5.2.0.9.2.20021217112115.02317e90@popd.ix.netcom.com> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 17 Dec 2002 16:00:35 -0500 To: enum@ietf.org From: Richard Shockey Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Enum] Meeting Minutes of IETF ENUM WG - IETF 55 Atlanta Sender: enum-admin@ietf.org Errors-To: enum-admin@ietf.org X-BeenThere: enum@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Enum Discussion List List-Post: List-Help: List-Subscribe: , Sorry about this being late ..if there any comments or revisions to this let me know ASAP. Telephone Number Mapping WG (enum) Monday, November 18 at 1300-1500 ================================= Chair(s): Patrik Faltstrom Richard Shockey Transport Area Advisor: Scott Bradner Mailing Lists: General Discussion:enum@ietf.org To Subscribe: enum-request@ietf.org In Body: subscribe Archive: ftp://ftp.ietf.org/ietf-mail-archive/enum/ AGENDA BASHING (5 min) Agenda NOTE: The unresolved issues in the WG all relate in one way or another to the structure of the enumservice field and what information should or should not be included and in which order. MEETING NOTES The chairs opened the meeting at 1300: Welcome comments from Richard Shockey , introduction of scribe.( Mark.Enzmann@cingular.com ) Lawrence Convoy asked to rearrange agenda for privacy and security following status of RFC2916bis and drop consideration of ENUM URI document which will move to IPTEL WG. Change accepted. 1. Patrik Faltstrom presenting status of RFC2916bis: Outstanding issues: A. IAB is to coordinate with the ITU-T TSB if the technical contact for the domain e164.arpa is to change and delegations within the zone e164.arpa B. ENUM servicefield What should the the RFC say: E2U+(foo:bar)?? Jon Peterson - comment - felt that Yokahama had defined this and there would not be a need for further discussion. Lawrence Conroy - comment - concern that list discussion was caused by misconceptions of what enumservices compendium draft was meant to accomplish Micheal Mealling comments that the ENUM entry is but a pointer. If the service is unknown then go to IANA for instructions. Enumservicefield = 'E2U' * Extended discussion of structure, following are valid. * E2U+voice * E2U+sip * E2U+sip:voice * E2U+voice:sip * Expected format = E2U+foo+foo Stress that this is a work in progress. 2. Shockey - Privacy and Security Considerations Shockey noted that many of the discussions over enumservice syntax centered on perceptions of what is ENUM and what it is not. A. Is it a service control point? Roughly analogous to a SCP in the PSTN that does nothing but number translation B. Is it Calling party control of communications? More information in entered into the DNS about the endpoint in order for calling party to make a specific selection before call setup is initiated. C. Is it Called party control of communications? Less information displayed (personal information obscured) and SIP proxy or Gatekeeper controlls the course and progress of the session. Called party control assumes greater privacy, but all models are valid. ENUM security is an issue that needs additional work. Suggestions or text welcome Discussion immediately centers on the attempt to resolve the enumservice field ABNF syntax. Major Item: Chairs ask for consensus. Patrik Faltstrom suggests the following ABNF syntax. Servicefield Service_field = "E2U" 1*(enumservice) Enumservice = "+" type 0*(subtype) Type = 1*32(alpha/digit) Subtype = ":" 1*32(alpha/digit) This is proposed syntax. Chairs call for consensus Hum of acceptance. 1346 18-Nov-02 Type and therefore subtype is registered with IANA and the registration itself specify what to expect If we register "A: and "B:C", can we implicitly to "A:C"? answer: NO! 3. Presentation: Jon Peterson SIP Registration document Presentation focus on use of only SIP address of record in the regexp Looking for direction as to proceed or not. Chairs ask for consensus. This is now going to be an official ENUM WG document. Hum consensus for. Additional documentation to be provided in SIPPING WG. 4.Presentation Orit Levin H.323 Registration Document Considerable presentation of the time lines and contingent dependencies on H.323 ENUM service document in both ITU and IPTEL WGs. Comment from the floor: The presentation seems to exceed the charter of ENUM and it is believed core documents should be discussed in IPTEL WG. H.323 ENUM registration document will stay with ENUM WGB. Chairs ask for consensus. Hum consensus for ..document now official WG document 5. Presentation L. Convoy Calling Party control scheme: Contends that during lookup originator will scan NAPTRs for terminating entity. First presented service is "Electronic Business Card" This has spurred discussion as this is an available service and is not following the core use of ENUM. Extended discussion of document and noted problems of complexity in what is valid and what is not. Chairs note: This document does not appear to have consensus as a work group document. Chairs call for consensus Rejected by hum. 6. Addition to agenda: Presentation: IFAX Service of ENUM - http://www.ietf.org/internet-drafts/draft-toyoda-enum-faxservice-00.txt Claudio Allocchio the co-chair of the IETF FAX WG gives a brief presentation on ENUM servicefield registration document for FAX. Consensus and agreement among both WG chairs that this document remains with the FAX WG. Meeting Ends ############################################# DOCUMENTS DISCUSSED AT THIS MEETING 1. RFC2916bis -0x REV - Faltstrom/Mealing 2. J.Peterson enumservice registration for SIP Addresses-of-Record A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-peterson-enum-sip-00.txt 3. O. Levin ENUM Service Registration for H.323 URL A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-levin-enum-h323-00.txt 4. R. Stastny & Co on behalf of R. Brandner enumservices compendium A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-brandner-enumservices-compendium-00.txt 5. R. Shockey Privacy and Security Considerations in ENUM A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-shockey-enum-privacy-security-00.txt >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 46000 Center Oak Plaza - Sterling, VA 20166 Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237 or ; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< _______________________________________________ enum mailing list enum@ietf.org https://www1.ietf.org/mailman/listinfo/enum