From sumanth@cablelabs.com Tue Jan 25 18:33:48 2011 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFB023A6916 for ; Tue, 25 Jan 2011 18:33:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.342 X-Spam-Level: X-Spam-Status: No, score=-0.342 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XSMB8IMX3-81 for ; Tue, 25 Jan 2011 18:33:48 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id C87173A6912 for ; Tue, 25 Jan 2011 18:33:43 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id p0Q2af2m021737 for ; Tue, 25 Jan 2011 19:36:41 -0700 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 25 Jan 2011 19:36:41 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Tue, 25 Jan 2011 19:36:41 -0700 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Tue, 25 Jan 2011 19:37:43 -0700 Thread-Topic: Rough Notes and AI list from the call on 1/20 Thread-Index: ActQMdwXrcsFb0LURMebPnHWJtIGmQQyesrgAVBYIVABXfP+AAFjMzQwCD37uiAKsf+lcA== Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D20A09B51@srvxchg> References: <76AC5FEF83F1E64491446437EA81A61F7D203155ED@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D20452EC0@srvxchg> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D20452EC0@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Rough Notes and AI list from the call on 1/20 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 02:33:48 -0000 Sorry about the delay in sending this out.=20 Volunteer reviewers, Please send across any comments you have so far on the protocol document. T= he authors are in the process of incorporating any comments prior to reques= ting WGLC once they address all of the current comments). Thanks! - S IETF DRINKS DESIGN TEAM CALL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 1/20/2011, 10:00a-10:40a (Eastern)/8:00a-8:40a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - David Schwartz - Ken Cartwright - Manjul Maharishi - Syed Ali - Sumanth Channabasappa=20 =20 ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Syed, by 11/24?] to make his set of updates and handover the updated docum= ent to Ken for further changes. AGENDA =3D=3D=3D=3D=3D=3D 1. Update from the protocol authors regarding recent updates 2. Plans for the next IETF 3. Other topics NOTES =3D=3D=3D=3D=3D 1. Update from the protocol authors regarding recent updates - [Syed] provided an overview of the updates he has made so far; he will= share this on the DRINKS mailing list. (Please see his email for details.) - Syed plans to handover the document to Ken for further changes - We had some discussions around the need to validate data types; Sumant= h had previously volunteered to assist with this - We also had some discussions around the need to document our assumptio= ns within this protocol, esp. for cases where it may be relevant for data d= istribution (e.g., the format of the identifier) 2. Plans for the next IETF - We need to update the use cases document, based on the WGLC comments - We also need to prepare the protocol document for WGLC =20 3. Other topics - We had some general discussions = From syed.ali@neustar.biz Wed Jan 26 09:15:32 2011 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79A2D3A69C5 for ; Wed, 26 Jan 2011 09:15:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDJ7thnxXjeA for ; Wed, 26 Jan 2011 09:15:31 -0800 (PST) Received: from neustar.com (mx1.neustar.com [156.154.17.104]) by core3.amsl.com (Postfix) with ESMTP id EFFFE3A69DD for ; Wed, 26 Jan 2011 09:15:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1296062301; x=1611413926; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=Dk3eK3ShdF5LBLYHgjbrt ubnaKxYzVFij0pAySjitqA=; b=CMsJDQiPkT8sBAcmmbGCp3y7KC3GWfof5yukY t0SVfopKVcP6sNnytsA87SYpyXhi0ZrlvFem1hIwM9dObqsiw== Received: from ([10.31.13.228]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.19136672; Wed, 26 Jan 2011 12:18:20 -0500 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT01.cis.neustar.com ([::1]) with mapi; Wed, 26 Jan 2011 12:18:20 -0500 From: "Ali, Syed Wasim" To: "drinks@ietf.org" Date: Wed, 26 Jan 2011 12:18:16 -0500 Thread-Topic: Updates to the protocol document... Thread-Index: Acu9fQcuLeQX3E2eQs6lHPTknoJ7pw== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.0.0.100825 acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: 7dZ/+OIlSP5o675vt+Rf0Q== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [drinks] Updates to the protocol document... X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2011 17:15:32 -0000 Hi, Manjul thanks for reviewing the protocol document and pointing out areas that require fixes or updates in the email back on Nov 29. The following list of comments have been addressed. -S-Sect 6.11, page 47: third line =AD typo, should be =B3serve=B2 instead= of =B3server=B2. -S-Sect 7.1, page 55: Mismatch in clientTransId values between the query and response. -S-Sect 7.3, page 57: Namespace usage for the elements is shown inconsistently =AD it is not shown for rantId and rarId, but is shown for rrName, ete and uri. -S-Sect 7.6, page 61: =B3rantId0=B2 and =B3rarId0=B2 should be replaced w= ith =B3iana-en:222=B2. -S-Sect 7.16, page 72: Same example =AD should be =B3iana-en:111=B2 inste= ad of =B3ssp1=B2. -S-Sect 7.17, page 72: Typo in heading =AD should be =B3Egress=B2. -S-Sect 8.1, page 79: Typo =AD should be =B3the=B2 instead of =B3te=B2. -S-Sect 7.5, page 60: CorDateTime is shown as prior to the Creation date time. Is this an oversight, or there is additional implication behind this =AD ie the Registry can return back the Date Time when the Regulatory body actually affirmed the COR claim of the Registrant? IMO, that imposes unnecessary requirement on the Registry and so the COR date time should be at or after the Creation date time. =3D=3D=3D=3D=3D=3D=3D[SYED] The date in XML message has been fixed -S-Sect 6.9, page 41: Layout and description of the attributes in TNType (such as corInfo) is inconsistent with the way it is defined in other places. Rest of the doc has the XSD definition first, and then the explanation of the parameters/attributes. Accordingly, this definition should go after the XSD specification on top of page 42. -S-Sect 7.6, page 61: IMO, the rn parameter should be in E.164 format. Having said that, we haven=B9t made any statement in the doc wrt E.164 nature of the TN/TNR/TNP/RN parameters =AD the question is should we? I think it should be left to the local policy of the Registry on how to handle non-E.164 elements being provisioned (e.g.: use some other rules to determine how to normalize such data prior to storage and/or further distribution). However, that does add avoidable complications, and it might be preferable to simply store everything as E.164 objects. =3D=3D=3D=3D[SYED] We discussed this aspect in the last design team meeting= and I think the general consensus is to let the local policy exercise the Registry preferences. -Syed From sumanth@cablelabs.com Thu Jan 27 09:15:11 2011 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CE7428C15A for ; Thu, 27 Jan 2011 09:15:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.353 X-Spam-Level: X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOOndIq+Mf9n for ; Thu, 27 Jan 2011 09:15:10 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id BC47828C14F for ; Thu, 27 Jan 2011 09:15:10 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id p0RHIDG9032102 for ; Thu, 27 Jan 2011 10:18:13 -0700 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 27 Jan 2011 10:18:14 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com) Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Thu, 27 Jan 2011 10:18:14 -0700 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 27 Jan 2011 10:19:17 -0700 Thread-Topic: Rough Notes and AI list from the call on 1/27 Thread-Index: ActQMdwXrcsFb0LURMebPnHWJtIGmQQyesrgAVBYIVABXfP+AAFjMzQwCD37uiAKsf+lcABRJHmw Message-ID: <76AC5FEF83F1E64491446437EA81A61F7D20A09C76@srvxchg> References: <76AC5FEF83F1E64491446437EA81A61F7D203155ED@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D20452EC0@srvxchg> <76AC5FEF83F1E64491446437EA81A61F7D20A09B51@srvxchg> In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7D20A09B51@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Rough Notes and AI list from the call on 1/27 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Jan 2011 17:15:11 -0000 IETF DRINKS DESIGN TEAM CALL=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 1/27/2011, 10:00a-10:30a (Eastern)/8:00a-8:30a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Ken Cartwright - Syed Ali - Sumanth Channabasappa=20 =20 ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Syed, 11/27] Will be handing over the token to Ken. [Ken, 2/3] Will be completing his updates (e.g., changes to fix WSDL and XS= D) AGENDA =3D=3D=3D=3D=3D=3D 1. Status update from the authors (use cases, protocol I-Ds)=20 2. TBD for the next IETF NOTES =3D=3D=3D=3D=3D 1. Status update from the authors (use cases, protocol I-Ds)=20 - Syed provided a quick update on further changes. We had a discussion arou= nd the text related to the expansion of the TN Range w.r.t. the open number= ing plan. Ken suggested alternative text. Further, Sumanth recommended that= 'range' may not make sense with an 'open numbering plan'. Syed plans to ch= eck previous discussion around this and get back to the mailing list with a= proposal. - Ken indicated that he found a couple of minor issues with the WSDL and XS= D, which he will be correcting, along with any other final changes. 2. TBD for the next IETF - No further comments have been received on the I-Ds. The last set of comme= nts from Manjul will be addressed. There were also comments from Otmar (12/= 10) that need to be verified. - Sumanth has also pinged additional volunteers (e.g., Jon P) - If we don't receive any additional comments and the authors get done with= the current set of planned I-D updates, they plan to request WGLC by the e= nd of next week.