From dschwartz@xconnect.net Mon Jul 4 22:23:57 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7BA721F86CE for ; Mon, 4 Jul 2011 22:23:57 -0700 (PDT) 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3c6QVwSda+1t for ; Mon, 4 Jul 2011 22:23:56 -0700 (PDT) Received: from outlook.xconnect.net (outlook.xconnect.net [212.25.92.170]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF7921F85AA for ; Mon, 4 Jul 2011 22:23:56 -0700 (PDT) Received: from ISR-JLM-MAIL1.xconnect.co.il ([172.16.100.8]) by ISR-JLM-MAIL1.xconnect.co.il ([172.16.100.8]) with mapi; Tue, 5 Jul 2011 08:23:55 +0300 From: David Schwartz To: IETF DRINKS WG Date: Tue, 5 Jul 2011 08:23:53 +0300 Thread-Topic: http://www.ietf.org/id/draft-schwartz-drinks-spdist-00.txt Thread-Index: Acw607uOC6ICu+dGQju2aTxc+TcNyA== Message-ID: <1E4F8DC4-C3B1-41DE-9AF1-8BD9D5CDA2D6@xconnect.net> 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 Subject: [drinks] http://www.ietf.org/id/draft-schwartz-drinks-spdist-00.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2011 05:23:57 -0000 In an attempt to start the discussion on the possible need for a distributi= on protocol I have posted an individual draft on the topic. While this draft is sparse, my intention is to post a 01 version before nex= t week with some more discussion points. :D= From jf.mule@cablelabs.com Wed Jul 6 10:32:07 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FF921F88CC for ; Wed, 6 Jul 2011 10:32:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.463 X-Spam-Level: X-Spam-Status: No, score=-100.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMB2s+n-qw7Q for ; Wed, 6 Jul 2011 10:32:06 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 3D89621F86E6 for ; Wed, 6 Jul 2011 10:32:06 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p66HW466005775; Wed, 6 Jul 2011 11:32:05 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Wed, 6 Jul 2011 11:32:04 -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; Wed, 6 Jul 2011 11:32:05 -0600 From: Jean-Francois Mule To: Dean Willis Date: Wed, 6 Jul 2011 11:31:25 -0600 Thread-Topic: [drinks] Review of draft-ietf-drinks-spprov-07 Thread-Index: Acw8Ap928ewxhIWsTYCq38ZaxNP3Rg== Message-ID: In-Reply-To: <648D3997-FA3A-4FED-9855-2B4668D8809E@softarmor.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.10.0.110310 acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Cc: "drinks@ietf.org" Subject: Re: [drinks] Review of draft-ietf-drinks-spprov-07 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 17:32:07 -0000 Dean, Thank you for your comments. See some of my inputs inline. Jean-Francois. On 05/25/2011 21:27, "Dean Willis" wrote: [snip] >As I seem to recall Sumanth asking me to do so, I've just done a read >through of draft-ietf-drinks-spprov-07. > >It's a pretty solid document with a couple of nits that may need fixing. >I'm also thinking that the security considerations and related discussion >around authentication and authorization issues are a bit light and are >likely to draw fire from the IESG. Based on multiple vendor implementations of SPPP like protocols for the same kind of data provisioning, we the authors had decided to leave each Registry implementation free to choose whatever data authorization model they wanted to implement on top of the data provisioning protocol. Therefore, we pulled back from doing anything on how one client user gets authorized to access some data or not. All we say is that the protocol should provide the means for a user to authenticate with the server. >I'll discuss my points in the order I noted them while going through the >document, since I'm too lazy to actually organize by priority or in any >more meaningful way. > >4.1/4.2 NIT: We have some inconsistent capitalization oddities relating >to words like "client", "server", "request" and "response", which are >sometimes capitalized and sometimes aren't. There may be some sort of >not-obvious--to-me rule in play about where they are being used as proper >nouns vs. ordinary nouns, but it was a bit distracting and is likely to >get changed by the RFC editor anyhow. I suggest quoting the word in its >definition, then just using lower case everywhere else: For example, a >"special term" may be defined in the text, but once it has been so >defined, it's a just a special term. fixed. >4.4 Discusses authentication, which section 3.1 says is mostly out of >scope for this document. We think it is. >However, there are some subtleties that it seems like the core spprov >document needs to think about. Is there a requirement for selective >authorization?=20 If you can authenticate a client based on some credentials, the server can decide whether the client has access to these resources. It is no different that an HTTP client requesting access to a given URL with some credentials and the HTTP server using its own data model to validate whether or not data access can be granted. >Given that SPPP intro and 3.2 seems to describe a registry as being >provisioned by multiple SSPs, this could be important. Do we need the >request to model to 1) carry a subset specifier, We had tried to model a Registrar ID rar in earlier versions of the document. We realized we could really do without this and implementers did not want to carry that extra identifier in the msging. >or 2) provision selective access capabilities? It can be done with what we have. >Do we need the response model to discuss authorization failures in a >useful way, for example saying "This part of your request failed, but >that part would have succeeded?" I prefer the yes | no answer to an authorization failure. Adding more info only helps if you want the client to then replay some messages with some deltas in the data being provisioned. >Indeed, spprov 4.4 talks about "authentication of the Client by the >Server is expected to be used to identify and further authorize the >Client to certain resources on the Server." Does the protocol have a need >to allow a client to specify which other clients can change the data it >submitted? This was the concept we had in Registrar Ids in the beginning. See http://tools.ietf.org/wg/drinks/minutes?item=3Dminutes80.html (section 2) for some of the discussions > >What is the relationship, if any, of the of orgId data element to >authentication and authorization? Depends on the registry implementation. In the protocol draft 07, the orgId is for the registrant ID (entity that owns/serves these TNs/PUIs). It could be that the registry implementation allows a tight coupling between the registrant and registrar entities or that it allows them to be decoupled and separate. > > >4.5 Confidentiality and Integrity. Requirement for confidentiality and >integrity protection is good, but "by providing encryption capabilities" >is an unsatisfying follow-on, either insufficient to assure the >requirements, or restrictive of techniques that might alternately assure >confidentiality and integrity protection. Easiest fix is to truncate the >sentence short of the quoted text. EKR has many times told me that >encryption is not a magic hammer and that, in a requirements sentence, >it's better to declare that which must be protected than to claim >everything is fixed by encryption. Fixed. Truncated the sentence but added an example. From internet-drafts@ietf.org Wed Jul 6 10:51:05 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D32D21F8A06; Wed, 6 Jul 2011 10:51:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.582 X-Spam-Level: X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nmy6Klye+Cu; Wed, 6 Jul 2011 10:51:04 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC07B21F89F0; Wed, 6 Jul 2011 10:51:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.55 Message-ID: <20110706175104.24305.34301.idtracker@ietfa.amsl.com> Date: Wed, 06 Jul 2011 10:51:04 -0700 Cc: drinks@ietf.org Subject: [drinks] I-D Action: draft-ietf-drinks-sppp-over-soap-04.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 17:51:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Data for Reachability of Inter/tra-Ne= tworK SIP Working Group of the IETF. Title : SPPP Over SOAP and HTTP Author(s) : Kenneth Cartwright Filename : draft-ietf-drinks-sppp-over-soap-04.txt Pages : 16 Date : 2011-07-06 The Session Peering Provisioning Protocol (SPPP) is an XML protocol that exists to enable the provisioning of session establishment data into Session Data Registries or SIP Service Provider data stores. Sending XML data structures over Simple Object Access Protocol (SOAP) and HTTP(s) is a widely used, de-facto standard for messaging between elements of provisioning systems. Therefore the combination of SOAP and HTTP(s) as a transport for SPPP is a natural fit. The obvious benefits include leveraging existing industry expertise, leveraging existing standards, and a higher probability that existing provisioning systems can be more easily integrated with this protocol. This document describes the specification for transporting SPPP XML structures over SOAP and HTTP(s). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-sppp-over-soap-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-sppp-over-soap-04.txt From kcartwright@tnsi.com Wed Jul 6 11:00:38 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB0221F8749 for ; Wed, 6 Jul 2011 11:00:38 -0700 (PDT) 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S47RObqrPrgh for ; Wed, 6 Jul 2011 11:00:35 -0700 (PDT) Received: from tnsi.com (relayus.tnsi.com [208.224.248.44]) by ietfa.amsl.com (Postfix) with ESMTP id 316E521F8739 for ; Wed, 6 Jul 2011 11:00:34 -0700 (PDT) Received: from ([172.17.7.231]) by relayus.tnsi.com with ESMTP with TLS id 4440551.55296530; Wed, 06 Jul 2011 14:00:18 -0400 Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.219]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Wed, 6 Jul 2011 14:00:17 -0400 From: "Cartwright, Ken" To: "drinks@ietf.org" Date: Wed, 6 Jul 2011 13:59:41 -0400 Thread-Topic: [drinks] I-D Action: draft-ietf-drinks-sppp-over-soap-04.txt Thread-Index: Acw8BYgLx35fN8d2RyqUXxTHwHpZvgAAGxAg Message-ID: <754963199212404AB8E9CFCA6C3D0CDA37ACA602E6@TNS-MAIL-NA.win2k.corp.tnsi.com> References: <20110706175104.24305.34301.idtracker@ietfa.amsl.com> In-Reply-To: <20110706175104.24305.34301.idtracker@ietfa.amsl.com> 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 Subject: Re: [drinks] I-D Action: draft-ietf-drinks-sppp-over-soap-04.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2011 18:00:38 -0000 I've submitted the following update to the SPPP transport document to addre= ss the comments received from WG LC. Those comments were as follows, and t= he changes I made... 1. Section 1: Introduction: The opening para states that "SPPP is bes= t supported by ....". It might be helpful to state the rationale why these = "features" are necessary for SPPP. However, this is more of a nit than a ne= cessity - as the expectation is that whoever is reading this document is fa= miliar with SPPP and its needs. KJC: Added a sentence or two about the rationale, which partially reflects= what was in the use case document and the protocol document. 2. Section 3:, 3rd para: "Document Literal Wrapped style......is generally regarded as an optimal approach that....". It will be g= ood to provide some reference(s) that support this. Not sure if it is accep= table practice to have any non-standard bodies URLs be listed in the refere= nce section (other standards organizations documents are ok - such as ITU-T= etc). KJC: Given that this is a best practice, there was not a single authoritat= ive reference to be used. So what I did was describe what the phrase "Docu= ment Literal Wrapped" means. 3. Section 3, page 6 - last sentence: SOAP and WSDL are referenced, b= ut not present in the Reference section. KJC: Added the references. 4. Section 4, page 7 - last sentence: HTTP is reference, but not pres= ent in the Reference section. KJC: Added the reference. 5. (nit) Section 7.1 - last sentence of first para: Typo - "Thes" sho= uld be "These". KJC: Fixed 6. (nit) Section 7.2 - last sentence of second para: Typo - "reasonab= l" should be "reasonable". KJC: Fixed. -----Original Message----- From: drinks-bounces@ietf.org [mailto:drinks-bounces@ietf.org] On Behalf Of= internet-drafts@ietf.org Sent: Wednesday, July 06, 2011 1:51 PM To: i-d-announce@ietf.org Cc: drinks@ietf.org Subject: [drinks] I-D Action: draft-ietf-drinks-sppp-over-soap-04.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Data for Reachability of Inter/tra-Ne= tworK SIP Working Group of the IETF. Title : SPPP Over SOAP and HTTP Author(s) : Kenneth Cartwright Filename : draft-ietf-drinks-sppp-over-soap-04.txt Pages : 16 Date : 2011-07-06 The Session Peering Provisioning Protocol (SPPP) is an XML protocol that exists to enable the provisioning of session establishment data into Session Data Registries or SIP Service Provider data stores. Sending XML data structures over Simple Object Access Protocol (SOAP) and HTTP(s) is a widely used, de-facto standard for messaging between elements of provisioning systems. Therefore the combination of SOAP and HTTP(s) as a transport for SPPP is a natural fit. The obvious benefits include leveraging existing industry expertise, leveraging existing standards, and a higher probability that existing provisioning systems can be more easily integrated with this protocol. This document describes the specification for transporting SPPP XML structures over SOAP and HTTP(s). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-sppp-over-soap-04.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-sppp-over-soap-04.txt _______________________________________________ drinks mailing list drinks@ietf.org https://www.ietf.org/mailman/listinfo/drinks This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Serv= ices. Any unauthorised review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply e-mail a= nd destroy all copies of the original message. From dean.willis@softarmor.com Thu Jul 7 07:00:35 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 449441F0C45 for ; Thu, 7 Jul 2011 07:00:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASMTZnnGOOiR for ; Thu, 7 Jul 2011 07:00:32 -0700 (PDT) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id C4C9A1F0C41 for ; Thu, 7 Jul 2011 07:00:31 -0700 (PDT) Received: by pwj5 with SMTP id 5so920773pwj.31 for ; Thu, 07 Jul 2011 07:00:31 -0700 (PDT) Received: by 10.68.50.163 with SMTP id d3mr1143945pbo.446.1310047231248; Thu, 07 Jul 2011 07:00:31 -0700 (PDT) Received: from [192.168.1.160] ([189.176.163.193]) by mx.google.com with ESMTPS id p5sm5634413pbd.60.2011.07.07.07.00.28 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jul 2011 07:00:30 -0700 (PDT) From: Dean Willis Content-Type: text/plain; charset=us-ascii Message-Id: <40CD7364-FBAA-40CD-96F9-195309E418D9@softarmor.com> Date: Thu, 7 Jul 2011 09:00:27 -0500 To: Ken Cartwright , drinks@ietf.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [drinks] Very Minor nit in draft-ietf-drinks-spprov-07 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2011 14:00:35 -0000 in 6.3. Add Public Identifier Operation: Text has: "A Public Identifier may provisioned as a member of a Destination Group = or provisioned outside of a Destination Group." This probably needs a "be" between "may" and "provisioned". -- dean From syed.ali@neustar.biz Thu Jul 7 07:30:13 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 713AF228011 for ; Thu, 7 Jul 2011 07:30:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.046 X-Spam-Level: X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PnQXLkpdeRT0 for ; Thu, 7 Jul 2011 07:30:12 -0700 (PDT) Received: from neustar.com (keys.neustar.biz [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0CD22800F for ; Thu, 7 Jul 2011 07:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1310049010; x=1625395367; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=dAJDkdpW9zh9pc12bRKcx oXY28uAE0e55JiBrjACQwQ=; b=InpeekIzWQAhbnf6Z7Pc2jdtCIlyl01fLd06M ujDO27IZbet5Y646xxFN35pmfB3J1RXlRJMZeR2tHFW09ngXQ== Received: from ([10.31.13.242]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.24633444; Thu, 07 Jul 2011 10:30:08 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT03.cis.neustar.com ([::1]) with mapi; Thu, 7 Jul 2011 10:30:08 -0400 From: "Ali, Syed Wasim" To: Dean Willis , Ken Cartwright , "drinks@ietf.org" Date: Thu, 7 Jul 2011 10:30:06 -0400 Thread-Topic: [drinks] Very Minor nit in draft-ietf-drinks-spprov-07 Thread-Index: Acw8sl6auSx5DFbcQ3+IuXrLD3I41Q== Message-ID: In-Reply-To: <40CD7364-FBAA-40CD-96F9-195309E418D9@softarmor.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.101115 acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: ri6O/tOQIzj3upRtKajvQA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] Very Minor nit in draft-ietf-drinks-spprov-07 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2011 14:30:13 -0000 Dean, Thanks for catching the typo. It was fixed as part of a recent review and should be available shortly. -Syed On 7/7/11 10:00 AM, "Dean Willis" wrote: >in 6.3. Add Public Identifier Operation: > >Text has: > >"A Public Identifier may provisioned as a member of a Destination Group >or provisioned outside of a Destination Group." > >This probably needs a "be" between "may" and "provisioned". > >-- >dean > >_______________________________________________ >drinks mailing list >drinks@ietf.org >https://www.ietf.org/mailman/listinfo/drinks From sumanth@cablelabs.com Thu Jul 7 19:39:08 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E27121F869A for ; Thu, 7 Jul 2011 19:39:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.462 X-Spam-Level: X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1urJxzuRHv0 for ; Thu, 7 Jul 2011 19:39:08 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 1494921F8690 for ; Thu, 7 Jul 2011 19:39:04 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p682d3lh005201 for ; Thu, 7 Jul 2011 20:39:03 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 7 Jul 2011 20:39:03 -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, 7 Jul 2011 20:39:04 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 7 Jul 2011 20:39:01 -0600 Thread-Topic: Update regarding DRINKS Thread-Index: Acw9GCW3lt9i4up3Tfa1Qn8dNtFo4Q== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE1671@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F818AFE1671srvxchg_" MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Update regarding DRINKS X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 02:39:08 -0000 --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1671srvxchg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, In preparation for Quebec, we wanted to give you an update regarding where = we stand. + Use Cases Document - WGLC was completed in Nov, 2010. - As you may recall from the last IETF, we decided to hold off on public= ation till we were near completion of the protocol and transport documents = to make sure we did not miss anything. No comments have been received so fa= r. - Proposal: Once we complete updates for protocol and transport document= s we will request publication. + Protocol Document - WGLC completed recently; Dean Willis provided expert review comments. - Authors (Jean-Francois M., Syed A., Ken C.) are working to address and= resolve the comments. - Proposal: See if we need further reviews, or request publication. + Transport Document - WGLC completed recently; Manjul Maharishi provided expert review comm= ents. - Author (Ken C.) just presented an update to address those comments. - Proposal: Need review from IETF WSDL and XSD experts; have requested = Peter Saint-Andre who plans to review. + The open source implementation for sppp is coming along. Updates will be = provided in Quebec. - Alex and Sumanth --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1671srvxchg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Folks,

 

In preparation for Quebec, we wanted to give you an update regarding wher= e we stand.

 

+ Use Cases Document

   - WGLC was completed in Nov, 2010.

   - As you may recall from the last IETF, we dec= ided to hold off on publication till we were near completion of the protoco= l and transport documents to make sure we did not miss anything. No comment= s have been received so far.

 &= nbsp; - Proposal: Once we complete updates for protocol and transport = documents we will request publication.

 

+ Protocol Document

   - WGLC completed recently; Dean = Willis provided expert review comments.

   - Authors (Jean-Francois M., Syed A., Ken C.) are wor= king to address and resolve the comments.

   - Proposal: See if we need further reviews, or request pu= blication.

 

+ Transport Document

    - WGLC completed recently; Manjul Maharishi provided = expert review comments.

  &= nbsp; - Author (Ken C.) just presented an update to address those comments.=

    - Proposal:= Need review from IETF WSDL and XSD experts; have requested Peter Saint-And= re who plans to review.

 

+ The open source implementation for sppp i= s coming along. Updates will be provided in Quebec.

 

 

- Alex and Sumanth

= --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1671srvxchg_-- From sumanth@cablelabs.com Thu Jul 7 19:39:11 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EBF921F86C8 for ; Thu, 7 Jul 2011 19:39:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.462 X-Spam-Level: X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdgeYr31jm8X for ; Thu, 7 Jul 2011 19:39:10 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id A0C7B21F86B4 for ; Thu, 7 Jul 2011 19:39:10 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p682d90c005209 for ; Thu, 7 Jul 2011 20:39:09 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 7 Jul 2011 20:39:09 -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, 7 Jul 2011 20:39:09 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 7 Jul 2011 20:39:07 -0600 Thread-Topic: Agenda for the DRINKS WG meeting in Quebec Thread-Index: Acw9FRhCzXT3n330TRm1XwepYNM2Yw== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE1672@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F818AFE1672srvxchg_" MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Agenda for the DRINKS WG meeting in Quebec X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 02:39:11 -0000 --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1672srvxchg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, Here is the proposed agenda, based on discussions with the design team. Pl= ease feel free to suggest changes or request additional items. - Alex & Sumanth DRINKS WG meeting - TUESDAY, July 26, 2011, 1520-1700pm 1) WG Session Welcome & Administrivia (Chairs, 5m) - Scribes - Blue Sheets - Scribe(s) - Jabber Scribe(s) 2) WG Status Chairs (10m) - Document status of WG items -- this will also cover use case I-D upda= tes 3) Protocol Document (Authors, 30m) - Open issues from WGLC, and resolutions - Next steps 4) Transport Document (Author, 10m) - Open Issues from WGLC, and resolutions - Next steps 5) Open source project (project participants, 10m) - Status and Update 6) Discussion around the possible need for a distribution protocol (Draft A= uthors, 10m) - Link: http://www.ietf.org/id/draft-schwartz-drinks-spdist-00.txt 7) Next Steps (15m) - Upcoming work? - Related work (e.g., Global )? - WG shutdown before Taipei possible? --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1672srvxchg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Folks,

 

Here is the proposed agenda, based on discussions with the design team. &= nbsp;Please feel free to suggest changes or request additional items. =

 

- Alex & Sumanth

 <= /o:p>

 

DRINKS WG meeting - TUESDAY, July 26, 2011, 1520-1700pm

 

1) WG Se= ssion Welcome & Administrivia (Chairs, 5m)

    - Scribes

    - Blue Sheets

&n= bsp;   - Scribe(s)

 &n= bsp;  - Jabber Scribe(s)

&n= bsp;

2) WG Status Chairs (10m)<= /p>

    - Document status of WG items= -- this will also cover use case I-D updates

 

3) Protocol Document = (Authors, 30m)

    - O= pen issues from WGLC, and resolutions

    - Next steps

 

4) Transport Document (Author, 10m= )

    - Open Issues fr= om WGLC, and resolutions

  =   - Next steps

 =

5) Open source project (project participants, 1= 0m)

    - Status and U= pdate

 

6) Discussion around the possible need for a distribution p= rotocol (Draft Authors, 10m)

 &n= bsp;  - Link: http://www.ietf.org/id/draft-schwartz-drinks-spdist-00.t= xt

 

7) Next Steps (15m)

 =    - Upcoming work?

 &= nbsp;  - Related work (e.g., Global )?

    - WG shutdown before Taipei possible?

= --_000_76AC5FEF83F1E64491446437EA81A61F818AFE1672srvxchg_-- From sumanth@cablelabs.com Thu Jul 7 19:43:36 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F193A21F8826 for ; Thu, 7 Jul 2011 19:43:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEYgZrvy66sA for ; Thu, 7 Jul 2011 19:43:36 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 52C9D21F880D for ; Thu, 7 Jul 2011 19:43:36 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p682dF4q005243 for ; Thu, 7 Jul 2011 20:39:15 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Thu, 7 Jul 2011 20:39:15 -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, 7 Jul 2011 20:39:15 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Thu, 7 Jul 2011 20:39:13 -0600 Thread-Topic: Rough Notes and AI list from the design team call on 6/7 Thread-Index: Acw9FUzMJryrEimxRw2DR7WlMr/ljg== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE1673@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 design team call on 6/7 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 02:43:37 -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 3/7/2011, 10:00a-10:35a (Eastern)/8:00a-8:35a (Mountain) =20 Participants =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - David Schwartz - Syed Ali - Sumanth Channabasappa=20 (Alex tried to join, but encountered issues.) ACTION ITEMS=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [Protocol Authors] Complete updates to the protocol document; specifically= =20 - Syed will (in collaboration with David) work on updates to the securit= y-related comments today and tomorrow [Design Team] Discuss and finalize any updates to the protocol document - We will have a call on Monday at 9a Eastern AGENDA =3D=3D=3D=3D=3D=3D 1. Updates related to the protocol document 2. Agenda NOTES =3D=3D=3D=3D=3D 1. Updates related to the protocol document - The authors (Jean-Francois, Syed and Ken) are working on updates to ad= dress Dean's expert review comments - Most updates have been made, as discussed on the mailing list - Today's call primarily focused on changes to the security-related comm= ents.=20 > We discussed, and agreed, that we should clarify authentication and= authorization requirements - Authentication deals with the verification of the identity (i.e.= , "Client X is indeed Client X") - Authorization deals with the verification of proper authority (i= .e., permission) to perform an action > As Dean indicated, we need to clarify what these two mean within th= e protocol. We don't necessarily need to specify the "how" (i.e., protocols= ), which is dealt with in the transport document - Syed will work on the first set of changes; David volunteered to help.= We will discuss changes on the mailing list.=20 2. Agenda - Alex had sent across a draft agenda, and we made further changes as=20 DRINKS WG meeting - TUESDAY, July 26, 2011, 1520-1700pm 1) WG Session Welcome & Administrivia (Chairs, 5m) - Scribes - Blue Sheets - Scribe(s) - Jabber Scribe(s) 2) WG Status Chairs (10m) - Document status of WG items -- this will also cover use case I-D upda= tes 3) Protocol Document (Authors, 30m) - Open issues from WGLC, and resolutions - Next steps 4) Transport Document (Author, 10m) - Open Issues from WGLC, and resolutions - Next steps 5) Open source project (project participants, 10m) - Status and Update 6) Discussion around the possible need for a distribution protocol (Draft A= uthors, 10m) - Link: http://www.ietf.org/id/draft-schwartz-drinks-spdist-00.txt 7) Next Steps (15m) - Upcoming work? - Related work (e.g., Global )? - WG shutdown before Taipei possible? From internet-drafts@ietf.org Mon Jul 11 16:24:01 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B74D11E838D; Mon, 11 Jul 2011 16:24:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.588 X-Spam-Level: X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6aGXNpM8fI7; Mon, 11 Jul 2011 16:24:01 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB6C11E83A2; Mon, 11 Jul 2011 16:23:59 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.55 Message-ID: <20110711232359.17381.93368.idtracker@ietfa.amsl.com> Date: Mon, 11 Jul 2011 16:23:59 -0700 Cc: drinks@ietf.org Subject: [drinks] I-D Action: draft-ietf-drinks-spprov-08.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 23:24:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Data for Reachability of Inter/tra-Ne= tworK SIP Working Group of the IETF. Title : Session Peering Provisioning Protocol Author(s) : Jean-Francois Mule Kenneth Cartwright Syed Wasim Ali Alexander Mayrhofer Filename : draft-ietf-drinks-spprov-08.txt Pages : 96 Date : 2011-07-11 This document defines a protocol for provisioning session establishment data into Session Data Registries and SIP Service Provider data stores. The provisioned data is typically used by various network elements for session peering. This document describes the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol including extensibility and independent transport definitions, a basic data model and an XML Schema Document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-spprov-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-spprov-08.txt From internet-drafts@ietf.org Mon Jul 11 18:01:09 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6919D11E80E1; Mon, 11 Jul 2011 18:01:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.59 X-Spam-Level: X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c428UVc7aOXY; Mon, 11 Jul 2011 18:01:08 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFF1A11E80C1; Mon, 11 Jul 2011 18:01:08 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.55 Message-ID: <20110712010108.17123.94519.idtracker@ietfa.amsl.com> Date: Mon, 11 Jul 2011 18:01:08 -0700 Cc: drinks@ietf.org Subject: [drinks] I-D Action: draft-ietf-drinks-spprov-09.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 01:01:09 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Data for Reachability of Inter/tra-Ne= tworK SIP Working Group of the IETF. Title : Session Peering Provisioning Protocol Author(s) : Jean-Francois Mule Kenneth Cartwright Syed Wasim Ali Alexander Mayrhofer Filename : draft-ietf-drinks-spprov-09.txt Pages : 96 Date : 2011-07-11 This document defines a protocol for provisioning session establishment data into Session Data Registries and SIP Service Provider data stores. The provisioned data is typically used by various network elements for session peering. This document describes the Session Peering Provisioning Protocol used by clients to provision registries. The document provides a set of guiding principles for the design of this protocol including extensibility and independent transport definitions, a basic data model and an XML Schema Document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-drinks-spprov-09.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-drinks-spprov-09.txt From syed.ali@neustar.biz Mon Jul 11 18:18:27 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79B111E83E7 for ; Mon, 11 Jul 2011 18:18:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.322 X-Spam-Level: X-Spam-Status: No, score=-6.322 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogEVqKWiOylL for ; Mon, 11 Jul 2011 18:18:27 -0700 (PDT) Received: from neustar.com (smartmail.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 02CE611E83E0 for ; Mon, 11 Jul 2011 18:18:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1310433504; x=1625784600; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=UqxTtgL/SLqtEy8MreBbW Gf8vk9u9Q92DhgZr2WvjuA=; b=YSAdEV/2xN0BbGan6RvIJe3tDcQWnNhCJKyxU 1aqIjFZUpiXCGR7YPPr4e/oXFsDFNRWTFbBW69yad3ebqrdVw== Received: from ([10.31.13.242]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.24786480; Mon, 11 Jul 2011 21:18:23 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT03.cis.neustar.com ([::1]) with mapi; Mon, 11 Jul 2011 21:18:23 -0400 From: "Ali, Syed Wasim" To: "drinks@ietf.org" Date: Mon, 11 Jul 2011 21:18:21 -0400 Thread-Topic: New Version Notification for draft-ietf-drinks-spprov-09.txt Thread-Index: AcxAMZdzyGa+tStHS/OsIMO1e4Yn3Q== Message-ID: In-Reply-To: <20110712010108.17123.29355.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.101115 acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: 1pMuir6HQiwstkNGqZuhaA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [drinks] FW: New Version Notification for draft-ietf-drinks-spprov-09.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 01:18:28 -0000 Fyi. The latest draft for SPPP has now been published. Many thanks for David Schwartz and Ken C. for making the last minute reviews and contributions. This draft also has contributions from Jean Francois Mule who continue to provide the needed support to help push things through. -Syed On 7/11/11 9:01 PM, "internet-drafts@ietf.org" wrote: >A new version of I-D, draft-ietf-drinks-spprov-09.txt has been >successfully submitted by Syed Ali and posted to the IETF repository. > >Filename: draft-ietf-drinks-spprov >Revision: 09 >Title: Session Peering Provisioning Protocol >Creation date: 2011-07-12 >WG ID: drinks >Number of pages: 96 > >Abstract: > This document defines a protocol for provisioning session > establishment data into Session Data Registries and SIP Service > Provider data stores. The provisioned data is typically used by > various network elements for session peering. > > This document describes the Session Peering Provisioning Protocol > used by clients to provision registries. The document provides a set > of guiding principles for the design of this protocol including > extensibility and independent transport definitions, a basic data > model and an XML Schema Document. > > =20 > =20 > > >The IETF Secretariat From syed.ali@neustar.biz Mon Jul 11 18:42:04 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C70621F8F1F for ; Mon, 11 Jul 2011 18:42:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.461 X-Spam-Level: X-Spam-Status: No, score=-6.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAsTc4G4H3vk for ; Mon, 11 Jul 2011 18:42:03 -0700 (PDT) Received: from neustar.com (smartmail.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE2A21F8F1C for ; Mon, 11 Jul 2011 18:41:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1310434916; x=1625784600; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=9Au0emM5Ow9FB7McgZwa8 S4PQX4Qh6YIN8lyXT73m3Q=; b=al2SRDxnUVV71YsQuevFXDxSTm4IuMh4MR6y+ X2z+rawYclArEAjFYetw0hKaddsNj3h+FT4zfM2lv5EUL0GAg== Received: from ([10.31.13.228]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.24786910; Mon, 11 Jul 2011 21:41:54 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT01.cis.neustar.com ([::1]) with mapi; Mon, 11 Jul 2011 21:41:54 -0400 From: "Ali, Syed Wasim" To: "drinks@ietf.org" Date: Mon, 11 Jul 2011 21:41:52 -0400 Thread-Topic: [drinks] FW: New Version Notification for draft-ietf-drinks-spprov-09.txt Thread-Index: AcxANOCutHyqdfU7RIqoVkNwDl2tjg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.101115 acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: pMBMr/rBVwvCuiurw/3wZw== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] FW: New Version Notification for draft-ietf-drinks-spprov-09.txt X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 01:42:04 -0000 While the diff tool provides a more accurate comparison of what is new in the latest draft, here str some of the things that changed in comparison to the version -07. - spelling errors and other language fixes - Capitalization inconsistencies - Introduction section has been updated - Time values are now required to be UTC - transport reqt. section was updated for clarity - revised Fig 1. to tightly couple it with the text in the intro section - revised Fig 2. Revised for better formatting - some definitions were amended for clarity and at least one new term was added to this section - provisioning query section now has added text for clarity -Syed On 7/11/11 9:18 PM, "Ali, Syed Wasim" wrote: > >Fyi. The latest draft for SPPP has now been published. Many thanks for >David Schwartz and Ken C. for making the last minute reviews and >contributions. This draft also has contributions from Jean Francois Mule >who continue to provide the needed support to help push things through. > > >-Syed > > >On 7/11/11 9:01 PM, "internet-drafts@ietf.org" >wrote: > >>A new version of I-D, draft-ietf-drinks-spprov-09.txt has been >>successfully submitted by Syed Ali and posted to the IETF repository. >> >>Filename: draft-ietf-drinks-spprov >>Revision: 09 >>Title: Session Peering Provisioning Protocol >>Creation date: 2011-07-12 >>WG ID: drinks >>Number of pages: 96 >> >>Abstract: >> This document defines a protocol for provisioning session >> establishment data into Session Data Registries and SIP Service >> Provider data stores. The provisioned data is typically used by >> various network elements for session peering. >> >> This document describes the Session Peering Provisioning Protocol >> used by clients to provision registries. The document provides a set >> of guiding principles for the design of this protocol including >> extensibility and independent transport definitions, a basic data >> model and an XML Schema Document. >> >> =20 >> =20 >> >> >>The IETF Secretariat > >_______________________________________________ >drinks mailing list >drinks@ietf.org >https://www.ietf.org/mailman/listinfo/drinks From dean.willis@softarmor.com Tue Jul 12 06:37:08 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB9521F8CBC for ; Tue, 12 Jul 2011 06:37:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GpMaUVJip-Vt for ; Tue, 12 Jul 2011 06:37:07 -0700 (PDT) Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC9521F8C80 for ; Tue, 12 Jul 2011 06:37:07 -0700 (PDT) Received: by yie30 with SMTP id 30so2332406yie.31 for ; Tue, 12 Jul 2011 06:37:07 -0700 (PDT) Received: by 10.147.130.10 with SMTP id h10mr1776441yan.38.1310477826904; Tue, 12 Jul 2011 06:37:06 -0700 (PDT) Received: from [192.168.2.143] (cpe-66-25-15-110.tx.res.rr.com [66.25.15.110]) by mx.google.com with ESMTPS id c63sm20304yhe.74.2011.07.12.06.37.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Jul 2011 06:37:06 -0700 (PDT) From: Dean Willis Content-Type: text/plain; charset=us-ascii Message-Id: Date: Tue, 12 Jul 2011 08:37:04 -0500 To: drinks@ietf.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [drinks] Comments on sppp draft in general X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 13:37:08 -0000 This from a developer who has been looking at SPPP: ----- The spec is deep in XML. A simple API table of inputs, kind of response = output and errors and exceptions without the XML would be a very helpful = summary, and it would be a sanity check against the SOAP draft. We are = relying on the SOAP draft WSDL as authoritative. ----- -- Dean= From syed.ali@neustar.biz Tue Jul 12 07:32:44 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C9421F86E8 for ; Tue, 12 Jul 2011 07:32:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.507 X-Spam-Level: X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SllgYJgH1H31 for ; Tue, 12 Jul 2011 07:32:40 -0700 (PDT) Received: from neustar.com (mx2.neustar.com [156.154.25.104]) by ietfa.amsl.com (Postfix) with ESMTP id DDACC21F86D0 for ; Tue, 12 Jul 2011 07:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1310481156; x=1625833252; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=6sl5XTTIAIv47VBEBUZhJ eaGprkqsJPeyw4flceWArQ=; b=d1jKJU3K2aN+Diy/FYpkxgj/SOY2XjZVqzB7F yIXCkGK0xTZjTAS6TVb5AC4afY4XU52e5iA3oeHf+6eVhQQZg== Received: from ([10.31.13.229]) by chihiron2.nc.neustar.com with ESMTP with TLS id 5202415.39357534; Tue, 12 Jul 2011 10:32:35 -0400 Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT02.cis.neustar.com ([::1]) with mapi; Tue, 12 Jul 2011 10:32:35 -0400 From: "Ali, Syed Wasim" To: Dean Willis , "drinks@ietf.org" Date: Tue, 12 Jul 2011 10:32:33 -0400 Thread-Topic: [drinks] Comments on sppp draft in general Thread-Index: AcxAoIoiUgWYoLtGTeG4g8O5qIt7bA== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.101115 acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: PZMkP/wWMO61FlYvTwjZoQ== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] Comments on sppp draft in general X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2011 14:32:44 -0000 Thanks for the feedback. I admit that the domain knowledge weighs in heavily for developers to be able to envision the various possibilities when it comes to input to the API. SPPP XML schema attempts to limit what can and cannot be a valid API construct. At the moment, an SPPP implementation will have little choice but to consider all these possibilities. In a typical real world implementation, I can imagine over-riding rules that will limit the input to what is and isn't applicable for a given implementation. SOAP draft is identified in the latest SPPP draft as mandatory transport protocol so I think the developers made the right choice. Hope this helps. -Syed On 7/12/11 9:37 AM, "Dean Willis" wrote: > >This from a developer who has been looking at SPPP: > >----- > >The spec is deep in XML. A simple API table of inputs, kind of response >output and errors and exceptions without the XML would be a very helpful >summary, and it would be a sanity check against the SOAP draft. We are >relying on the SOAP draft WSDL as authoritative. > >----- > >-- >Dean >_______________________________________________ >drinks mailing list >drinks@ietf.org >https://www.ietf.org/mailman/listinfo/drinks From sumanth@cablelabs.com Tue Jul 19 15:06:47 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E29595E8007 for ; Tue, 19 Jul 2011 15:06:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.282 X-Spam-Level: X-Spam-Status: No, score=0.282 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Ny+iY+o7hJU for ; Tue, 19 Jul 2011 15:06:44 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id F3F955E8008 for ; Tue, 19 Jul 2011 15:06:40 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p6JM6dLj021292 for ; Tue, 19 Jul 2011 16:06:40 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 19 Jul 2011 16:06:40 -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, 19 Jul 2011 16:06:40 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Tue, 19 Jul 2011 16:06:38 -0600 Thread-Topic: DRINKS agenda and remote participation information Thread-Index: AcxGYCHJbIBwjUZQTAKxGod63UvGmQ== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE1E4C@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] DRINKS agenda and remote participation information X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2011 22:06:48 -0000 Folks, As another update, here are some links as you prepare for IETF#81 next week= . WHEN =3D=3D=3D=3D=3D TUESDAY, July 26, 2011, 1520-1700pm WHERE =3D=3D=3D=3D=3D=3D http://tools.ietf.org/agenda/81/venue/?room=3D2103=20 AGENDA =3D=3D=3D=3D=3D=3D http://www.ietf.org/proceedings/81/agenda/drinks.txt =20 REMOTE PARTICIPATION =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - We are going to use Meetecho. For more details, see:=20 http://www.ietf.org/meeting/81/remote-participation.html#Meetecho=20 (Choose the link for DRINKS.) Meetecho info: http://ietf81.conf.meetecho.com/=20 CURRENT STATUS =3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D http://www.ietf.org/mail-archive/web/drinks/current/msg00932.html =20 See you there! - Chairs! From alexander.mayrhofer@nic.at Wed Jul 20 08:23:31 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DD021F865F for ; Wed, 20 Jul 2011 08:23:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.12 X-Spam-Level: X-Spam-Status: No, score=-9.12 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KTqAc2TjCfa for ; Wed, 20 Jul 2011 08:23:30 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by ietfa.amsl.com (Postfix) with ESMTP id 28DA921F85A8 for ; Wed, 20 Jul 2011 08:23:29 -0700 (PDT) Received: from nics-exch.sbg.nic.at ([10.17.175.3]) by mail.sbg.nic.at over TLS secured channel (TLSv1/SSLv3:AES128-SHA:128) with XWall v3.47 ; Wed, 20 Jul 2011 17:23:27 +0200 Received: from nics-mail.sbg.nic.at (10.17.175.2) by NICS-EXCH.sbg.nic.at (10.17.175.3) with Microsoft SMTP Server id 14.1.218.12; Wed, 20 Jul 2011 17:23:21 +0200 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 20 Jul 2011 17:23:19 +0200 Message-ID: <8BC845943058D844ABFC73D2220D46650A9F99C5@nics-mail.sbg.nic.at> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Milestones updated... Thread-Index: AcxG8I5t+IG3xft3TLi5kdcnyeN7Hw== From: Alexander Mayrhofer To: X-XWALL-BCKS: auto Subject: [drinks] Milestones updated... X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2011 15:23:31 -0000 FYI, as agreed with our AD, we have updated our (long overdue) WG milestones. The current milestones for the group are as follows: Aug 2011 Request publication of Use Cases and Protocol Requirements document Sep 2011 Request publication of protocol specification Sep 2011 Request publication of protocol specification and a protocol transport mapping --- DRINKS Chairs Alex & Sumanth From stpeter@stpeter.im Wed Jul 20 15:52:29 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630D521F8888 for ; Wed, 20 Jul 2011 15:52:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.46 X-Spam-Level: X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXDIKwnK3Owj for ; Wed, 20 Jul 2011 15:52:25 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 33CCC21F8AF0 for ; Wed, 20 Jul 2011 15:52:25 -0700 (PDT) Received: from leavealone.cisco.com (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id CEF994005A for ; Wed, 20 Jul 2011 16:53:07 -0600 (MDT) Message-ID: <4E275C25.1050105@stpeter.im> Date: Wed, 20 Jul 2011 16:52:21 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: drinks@ietf.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2011 22:52:29 -0000 I've been asked to take a look at draft-ietf-drinks-sppp-over-soap. Overall I think it is in fine shape. Here are a few comments. 1. The document needs to be edited for clarity. For example, some of the sentences don't parse (e.g., the third sentence of Section 1). 2. There's a normative reference to W3C Note NOTE-wsdl-20010315, which says "This document is a NOTE made available by the W3C for discussion only. Publication of this Note by W3C indicates no endorsement by W3C or the W3C Team, or any W3C Members. W3C has had no editorial control over the preparation of this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time." Thus the phrase "WSDL is a widely standardized and adopted technology" in this I-D is not accurate, at least with regard to standarization. Furthermore, no published RFCs contain a normative reference to the WSDL document, which also is not in the downref registry. This will need to be called out during IETF Last Call. 3. Section 3 states "SOAP faults are not used by the SPPP SOAP mapping." It would be good to define how an application is supposed to handle SOAP faults if they occur for other reasons, or reference the SOAP specification on this point. 4. Transport security is a bit unclear to me. The spec says: All SOAP and HTTP SPPP Clients and Servers MUST support Transport Layer Security (TLS) as defined in [RFC5246] as the secure transport mechanism. Does that mean supporting HTTP Over TLS (RFC 2818) except using the most up-to-date version of TLS, or using TLS directly over TCP? 5. I am not a WSDL expert, but the definition looks fine to me (even if hard to read). This seems a bit odd: xmlns:sppps="urn:ietf:params:xml:ns:sppp:soap:1" targetNamespace="urn:ietf:params:xml:ns:sppp:soap:1" Why define the same namespace in two ways? 6. Section 7 says "The identity of the server should also be authenticated by the client." However, no guidance is provided about how to do that. A reference to RFC 2818 seems necessary. 7. Section 7.3 states: Some deployments of SPPP over SOAP may choose to use transports without encryption. This presents vulnerabilities but may be selected for deployments involving closed networks or debugging scenarios. Do you mean "MAY"? Is encryption truly optional? Please clarify that you mean MUST-implement and SHOULD-deploy or somesuch (where your "may" here really means "here's why a deployment might have a good reason to violate the SHOULD-deploy"). 8. The IANA considerations seem a bit thin. Please see RFC 3688 for the template. I know there are a few examples in Section 14 of RFC 6120, so feel free to borrow from there. :) Peter -- Peter Saint-Andre https://stpeter.im/ From kcartwright@tnsi.com Thu Jul 21 06:41:59 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FAED21F85D9 for ; Thu, 21 Jul 2011 06:41:59 -0700 (PDT) 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUfoYju10J2h for ; Thu, 21 Jul 2011 06:41:55 -0700 (PDT) Received: from tnsi.com (relayus.tnsi.com [208.224.248.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEE021F8AB8 for ; Thu, 21 Jul 2011 06:41:54 -0700 (PDT) Received: from ([172.17.7.231]) by relayus.tnsi.com with ESMTP with TLS id 4440551.55508270; Thu, 21 Jul 2011 09:41:50 -0400 Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.219]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Thu, 21 Jul 2011 09:41:49 -0400 From: "Cartwright, Ken" To: Peter Saint-Andre , "drinks@ietf.org" Date: Thu, 21 Jul 2011 09:41:46 -0400 Thread-Topic: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 Thread-Index: AcxHL7hYeVR4uLhzTQGn4wmKqZXE9wAfBV8g Message-ID: <754963199212404AB8E9CFCA6C3D0CDA37AD2CB920@TNS-MAIL-NA.win2k.corp.tnsi.com> References: <4E275C25.1050105@stpeter.im> In-Reply-To: <4E275C25.1050105@stpeter.im> 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 Subject: Re: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2011 13:41:59 -0000 Thank you for the review. We will evaluate and incorporate your comments a= nd send a follow up to the list. Ken -----Original Message----- From: drinks-bounces@ietf.org [mailto:drinks-bounces@ietf.org] On Behalf Of= Peter Saint-Andre Sent: Wednesday, July 20, 2011 6:52 PM To: drinks@ietf.org Subject: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 I've been asked to take a look at draft-ietf-drinks-sppp-over-soap. Overall I think it is in fine shape. Here are a few comments. 1. The document needs to be edited for clarity. For example, some of the sentences don't parse (e.g., the third sentence of Section 1). 2. There's a normative reference to W3C Note NOTE-wsdl-20010315, which says "This document is a NOTE made available by the W3C for discussion only. Publication of this Note by W3C indicates no endorsement by W3C or the W3C Team, or any W3C Members. W3C has had no editorial control over the preparation of this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time." Thus the phrase "WSDL is a widely standardized and adopted technology" in this I-D is not accurate, at least with regard to standarization. Furthermore, no published RFCs contain a normative reference to the WSDL document, which also is not in the downref registry. This will need to be called out during IETF Last Call. 3. Section 3 states "SOAP faults are not used by the SPPP SOAP mapping." It would be good to define how an application is supposed to handle SOAP faults if they occur for other reasons, or reference the SOAP specification on this point. 4. Transport security is a bit unclear to me. The spec says: All SOAP and HTTP SPPP Clients and Servers MUST support Transport Layer Security (TLS) as defined in [RFC5246] as the secure transport mechanism. Does that mean supporting HTTP Over TLS (RFC 2818) except using the most up-to-date version of TLS, or using TLS directly over TCP? 5. I am not a WSDL expert, but the definition looks fine to me (even if hard to read). This seems a bit odd: xmlns:sppps=3D"urn:ietf:params:xml:ns:sppp:soap:1" targetNamespace=3D"urn:ietf:params:xml:ns:sppp:soap:1" Why define the same namespace in two ways? 6. Section 7 says "The identity of the server should also be authenticated by the client." However, no guidance is provided about how to do that. A reference to RFC 2818 seems necessary. 7. Section 7.3 states: Some deployments of SPPP over SOAP may choose to use transports without encryption. This presents vulnerabilities but may be selected for deployments involving closed networks or debugging scenarios. Do you mean "MAY"? Is encryption truly optional? Please clarify that you mean MUST-implement and SHOULD-deploy or somesuch (where your "may" here really means "here's why a deployment might have a good reason to violate the SHOULD-deploy"). 8. The IANA considerations seem a bit thin. Please see RFC 3688 for the template. I know there are a few examples in Section 14 of RFC 6120, so feel free to borrow from there. :) Peter -- Peter Saint-Andre https://stpeter.im/ _______________________________________________ drinks mailing list drinks@ietf.org https://www.ietf.org/mailman/listinfo/drinks This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Serv= ices. Any unauthorised review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply e-mail a= nd destroy all copies of the original message. From sumanth@cablelabs.com Tue Jul 26 07:19:34 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DED221F8C3D for ; Tue, 26 Jul 2011 07:19:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.277 X-Spam-Level: X-Spam-Status: No, score=-0.277 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Np523TkQByLK for ; Tue, 26 Jul 2011 07:19:33 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id D236121F8C19 for ; Tue, 26 Jul 2011 07:19:30 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p6QEJTRJ014522 for ; Tue, 26 Jul 2011 08:19:29 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 26 Jul 2011 08:19:29 -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, 26 Jul 2011 08:19:30 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Importance: high X-Priority: 1 Date: Tue, 26 Jul 2011 08:19:28 -0600 Thread-Topic: Meeting slides for TODAY, and remote participation details Thread-Index: AcxLnhcI0Lz8+YSqShGY2oskqL9Q4w== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE21EC@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] Meeting slides for TODAY, and remote participation details X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 14:19:34 -0000 Folks, We hope to see those interested in DRINKS (the WG!) in room 2103 from 3:20p= -5p local time later today. We are getting close to completing the work and= would appreciate input and thoughts from interested experts.=20 -- Also, if you wish to volunteer as the note-taker or the Jabber scribe, plea= se let us know (a beer on us if you volunteer before the meeting :) ). -- AGENDA and SLIDES? http://tools.ietf.org/wg/drinks/agenda?item=3Dagenda81.html=20 (If you don't see all the slide decks, please refresh or give it a few minu= tes.) WHERE? http://tools.ietf.org/agenda/81/venue/?room=3D2103 =20 REMOTE PARTICIPATION? - We are planning to use Meetecho. For more details, see:=20 http://www.ietf.org/meeting/81/remote-participation.html#Meetecho =20 (Choose the link for DRINKS.) Meetecho info: http://ietf81.conf.meetecho.com/ =20 - Alex and Sumanth (as WG Chairs) From ietf@meetecho.com Tue Jul 26 09:14:23 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AE421F8B7A for ; Tue, 26 Jul 2011 09:14:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.669 X-Spam-Level: X-Spam-Status: No, score=-0.669 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2m9-3RQZAfT for ; Tue, 26 Jul 2011 09:14:22 -0700 (PDT) Received: from smtplqs02.aruba.it (smtplqs-out48.aruba.it [62.149.158.88]) by ietfa.amsl.com (Postfix) with SMTP id 3D7AA21F8B81 for ; Tue, 26 Jul 2011 09:14:22 -0700 (PDT) Received: (qmail 31477 invoked by uid 89); 26 Jul 2011 16:14:20 -0000 Received: from unknown (HELO smtpw1.aruba.it) (62.149.128.188) by smtplqs02.aruba.it with SMTP; 26 Jul 2011 16:14:20 -0000 Received: (qmail 937 invoked by uid 89); 26 Jul 2011 16:14:20 -0000 Received: from unknown (HELO aruba.it) (62.149.158.90) by smtpw1.ad.aruba.it with SMTP; 26 Jul 2011 16:14:20 -0000 Date: Tue, 26 Jul 2011 18:14:20 +0200 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "Meetecho IETF support" To: drinks@ietf.org X-XaM3-API-Version: V3(R2) X-SenderIP: 130.129.21.177 X-Spam-Rating: smtpw1.ad.aruba.it 1.6.2 0/1000/N X-Spam-Rating: smtplqs02.aruba.it 1.6.2 0/1000/N Subject: [drinks] Meetecho support for DRINKS WG meeting session X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 16:14:23 -0000 Hi all,=0A=0Aa virtual room has been reserved on the Meetecho system. =0A= =0AAccess to the on-line session (including audio and video streams) will= be available from 15:10 at:=0Ahttp://www.meetecho.com/ietf81/drinks=0A=0A= The Meetecho session automatically logs you into the standard IETF jabber= room. So, from there, you can have an integrated experience involving al= l media and allowing you to interact with the room.=0A=0AA tutorial of in= teractivity features of the tool can be found at:=0Ahttp://www.meetecho.c= om/ietf81/tutorials=0A=0AFor further information you can contact us at ie= tf-support@meetecho.com.=0A=0ACheers,=0Athe Meetecho Team From ning.zhang@neustar.biz Tue Jul 26 10:04:31 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC68711E80C9 for ; Tue, 26 Jul 2011 10:04:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.461 X-Spam-Level: X-Spam-Status: No, score=-6.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I+osOcFkKmnt for ; Tue, 26 Jul 2011 10:04:31 -0700 (PDT) Received: from neustar.com (mx1.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id EF6E511E8075 for ; Tue, 26 Jul 2011 10:04:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1311699869; x=1627041051; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=OwBin0w3J0fQD/uwTEg0U CnBfi5Rj7RxxS++R+oQEig=; b=F+vE5UYaKi/waqKHHo1iVRHM2Ly/6OT3i15AU PbE60eIlMoS8nLKLyn4nyKBZ3O9lOfO1Ushh8urzm+8MmfrGQ== Received: from ([10.31.13.228]) by stihiron2.va.neustar.com with ESMTP with TLS id 5202732.47831616; Tue, 26 Jul 2011 13:04:28 -0400 Received: from STNTEXCH02.cis.neustar.com ([fe80::f828:7b2d:14aa:84b7]) by STNTEXCHHT01.cis.neustar.com ([::1]) with mapi; Tue, 26 Jul 2011 13:04:28 -0400 From: "Zhang, Ning" To: "drinks@ietf.org" Date: Tue, 26 Jul 2011 13:04:27 -0400 Thread-Topic: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 Thread-Index: AcxHL7kHXobjBnM5S0GGEgpe7RkyugEhU6kA Message-ID: <38CC7FDA6EE9B24C992FA3CC8F26FC051E922920EE@STNTEXCH02.cis.neustar.com> References: <4E275C25.1050105@stpeter.im> In-Reply-To: <4E275C25.1050105@stpeter.im> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: sxYQyIsmwPmWshgzym0EXA== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 17:04:31 -0000 As a practitioner, I was asked to take a look at this draft. IMHO, it is in= a good shape. The following are a few comments: 1. I extracted the base SPPP schema as well as the WSDL from the drafts and= run various checking tools, including my own, and no issues were found. 2. I run CXF java code generator and construct a dummy server and it works = as expected. 3. Section 5 or Section 7 should mention RFC 2716 for Digest authentication= (Section 4) related security issues. =20 4. Some actual SOAP message examples and a separate zip package including X= SD/WSDL/XML messages would be very helpful. Thanks, -Ning From kcartwright@tnsi.com Tue Jul 26 12:59:30 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C3A721F8869 for ; Tue, 26 Jul 2011 12:59:30 -0700 (PDT) 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MhKQj+6TuM3 for ; Tue, 26 Jul 2011 12:59:30 -0700 (PDT) Received: from tnsi.com (relayus.tnsi.com [208.224.248.44]) by ietfa.amsl.com (Postfix) with ESMTP id D9DA221F885E for ; Tue, 26 Jul 2011 12:59:29 -0700 (PDT) Received: from ([172.17.7.231]) by relayus.tnsi.com with ESMTP with TLS id 4440551.55544205; Tue, 26 Jul 2011 15:59:25 -0400 Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.219]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Tue, 26 Jul 2011 15:59:25 -0400 From: "Cartwright, Ken" To: "Zhang, Ning" , "drinks@ietf.org" Date: Tue, 26 Jul 2011 15:58:59 -0400 Thread-Topic: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 Thread-Index: AcxHL7kHXobjBnM5S0GGEgpe7RkyugEhU6kAAAZbiQA= Message-ID: <754963199212404AB8E9CFCA6C3D0CDA37AD46F78D@TNS-MAIL-NA.win2k.corp.tnsi.com> References: <4E275C25.1050105@stpeter.im>, <38CC7FDA6EE9B24C992FA3CC8F26FC051E922920EE@STNTEXCH02.cis.neustar.com> In-Reply-To: <38CC7FDA6EE9B24C992FA3CC8F26FC051E922920EE@STNTEXCH02.cis.neustar.com> 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 Subject: Re: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 19:59:30 -0000 Thanks for these comments Ning. We will address these. ken ________________________________________ From: drinks-bounces@ietf.org [drinks-bounces@ietf.org] On Behalf Of Zhang,= Ning [Ning.Zhang@Neustar.biz] Sent: Tuesday, July 26, 2011 1:04 PM To: drinks@ietf.org Subject: Re: [drinks] review of draft-ietf-drinks-sppp-over-soap-04 As a practitioner, I was asked to take a look at this draft. IMHO, it is in= a good shape. The following are a few comments: 1. I extracted the base SPPP schema as well as the WSDL from the drafts and= run various checking tools, including my own, and no issues were found. 2. I run CXF java code generator and construct a dummy server and it works = as expected. 3. Section 5 or Section 7 should mention RFC 2716 for Digest authentication= (Section 4) related security issues. 4. Some actual SOAP message examples and a separate zip package including X= SD/WSDL/XML messages would be very helpful. Thanks, -Ning _______________________________________________ drinks mailing list drinks@ietf.org https://www.ietf.org/mailman/listinfo/drinks This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Serv= ices. Any unauthorised review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply e-mail a= nd destroy all copies of the original message. From sumanth@cablelabs.com Tue Jul 26 19:04:48 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B561B11E8090 for ; Tue, 26 Jul 2011 19:04:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.313 X-Spam-Level: X-Spam-Status: No, score=-0.313 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vr9plbAdfalj for ; Tue, 26 Jul 2011 19:04:47 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id B4F1A11E8086 for ; Tue, 26 Jul 2011 19:04:47 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id p6R24kol003447 for ; Tue, 26 Jul 2011 20:04:46 -0600 Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 26 Jul 2011 20:04:46 -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, 26 Jul 2011 20:04:46 -0600 From: Sumanth Channabasappa To: "Drinks@ietf.org" Date: Tue, 26 Jul 2011 20:04:43 -0600 Thread-Topic: Poll to pick a day for the proposed interim meeting Thread-Index: AcxMAYzgUnLtCLbCTuSu58FBY6dgTQ== Message-ID: <76AC5FEF83F1E64491446437EA81A61F818AFE22B9@srvxchg> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F818AFE22B9srvxchg_" MIME-Version: 1.0 X-Approved: ondar Subject: [drinks] Poll to pick a day for the proposed interim meeting X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 02:04:48 -0000 --_000_76AC5FEF83F1E64491446437EA81A61F818AFE22B9srvxchg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, Thanks again for a productive DRINKS WG meeting earlier today! During the m= eeting we proposed that we have an interim meeting to complete and validate= the changes to the protocol document (and if required, the transport docum= ent). A few participants volunteered to participate. As a follow-up, here's a poll to pick a day that would work best for most o= f the interested parties. The dates are based on offline suggestions. If no= ne of the proposed days are feasible, please feel free to suggest alternati= ve dates (via email). Link to the poll: http://www.doodle.com/zur2gmqygwyxbia9#table (Pick the timezone from the drop-down.) If you are interested in attending, please provide your responses by the en= d of this week. Thanks! - Alex and Sumanth (as WG Chairs) --_000_76AC5FEF83F1E64491446437EA81A61F818AFE22B9srvxchg_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Folks,

 

Thanks again for a productive DRINKS WG meet= ing earlier today! During the meeting we proposed that we have an interim m= eeting to complete and validate the changes to the protocol document (and i= f required, the transport document). A few participants volunteered to part= icipate.

 

As a follow-up, here’s a poll to pick a day that wou= ld work best for most of the interested parties. The dates are based on off= line suggestions. If none of the proposed days are feasible, please feel fr= ee to suggest alternative dates (via email).

 

<= p class=3DMsoNormal>Link to the poll:=

http://www.doodle.com/= zur2gmqygwyxbia9#table

(Pick the timezone from the drop-down.)

&n= bsp;

= If you are interested in attending, please provide your responses by the en= d of this week.

 

Thanks!

- Alex and Sumanth (as WG Chairs)=

 = ;

 

= --_000_76AC5FEF83F1E64491446437EA81A61F818AFE22B9srvxchg_-- From dean.willis@softarmor.com Wed Jul 27 06:20:13 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31ED321F8BA8 for ; Wed, 27 Jul 2011 06:20:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FWsxsDdbZjtU for ; Wed, 27 Jul 2011 06:20:12 -0700 (PDT) Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com [209.85.210.53]) by ietfa.amsl.com (Postfix) with ESMTP id A511521F8B8F for ; Wed, 27 Jul 2011 06:20:12 -0700 (PDT) Received: by pzk6 with SMTP id 6so2538546pzk.26 for ; Wed, 27 Jul 2011 06:20:12 -0700 (PDT) Received: by 10.68.54.4 with SMTP id f4mr93647pbp.14.1311772812330; Wed, 27 Jul 2011 06:20:12 -0700 (PDT) Received: from dhcp-678f.meeting.ietf.org (dhcp-678f.meeting.ietf.org [130.129.103.143]) by mx.google.com with ESMTPS id d3sm107988pbh.21.2011.07.27.06.20.10 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jul 2011 06:20:10 -0700 (PDT) From: Dean Willis Content-Type: text/plain; charset=us-ascii Message-Id: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> Date: Wed, 27 Jul 2011 09:20:08 -0400 To: drinks@ietf.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [drinks] Discussion on UETF-8 from CORE working group X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 13:20:13 -0000 One of the open questions in SPPP is relay a meta-question about = language encoding. What textual representation shall we use? We could = stay with plain old 7-bit ASCII (which would be my preference), but I'm = expecting international users to not like that idea very much. The "obvious alternative" is to say UTF-8. But I'm learning that thee's = a lot more to do than just say "use UTF-8". The CORE working group (Constrained Restful Environments) is close to = publishing the Constrained Application Protocol: = http://www.ietf.org/id/draft-ietf-core-coap-07.txt Zach Shelby, lead author of CoAP, said during today's CORE meeting that = the UTF-8 discussion had proven to be much harder to get right than he = had expected, but that it's pretty much done in CoAP. Perhaps we could re-use the approach (and possibly even the text) from = CoAP? -- Dean From alexander.mayrhofer@nic.at Wed Jul 27 06:33:12 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9850F21F8AEE for ; Wed, 27 Jul 2011 06:33:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.275 X-Spam-Level: X-Spam-Status: No, score=-9.275 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8qCT08iLtuc for ; Wed, 27 Jul 2011 06:33:12 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by ietfa.amsl.com (Postfix) with ESMTP id 7259021F8531 for ; Wed, 27 Jul 2011 06:33:11 -0700 (PDT) Received: from nics-exch.sbg.nic.at ([10.17.175.3]) by mail.sbg.nic.at over TLS secured channel (TLSv1/SSLv3:AES128-SHA:128) with XWall v3.47 ; Wed, 27 Jul 2011 15:33:10 +0200 Received: from nics-mail.sbg.nic.at (10.17.175.2) by NICS-EXCH.sbg.nic.at (10.17.175.3) with Microsoft SMTP Server id 14.1.218.12; Wed, 27 Jul 2011 15:33:06 +0200 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 27 Jul 2011 15:33:02 +0200 Message-ID: <8BC845943058D844ABFC73D2220D46650A9F9FB4@nics-mail.sbg.nic.at> In-Reply-To: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [drinks] Discussion on UETF-8 from CORE working group Thread-Index: AcxMX/BPu+EMgoyATPCJlXg69ue5IAAAXjxQ References: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> From: Alexander Mayrhofer To: Dean Willis , X-XWALL-BCKS: auto Subject: Re: [drinks] Discussion on UETF-8 from CORE working group X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 13:33:12 -0000 > The "obvious alternative" is to say UTF-8. But I'm learning that thee's a lot > more to do than just say "use UTF-8". >=20 > The CORE working group (Constrained Restful Environments) is close to > publishing the Constrained Application Protocol: > http://www.ietf.org/id/draft-ietf-core-coap-07.txt >=20 > Zach Shelby, lead author of CoAP, said during today's CORE meeting that the > UTF-8 discussion had proven to be much harder to get right than he had > expected, but that it's pretty much done in CoAP. >=20 > Perhaps we could re-use the approach (and possibly even the text) from > CoAP? I think we should definitely look at this, particularly because it *could* be a base protocol for another transport mapping of DRINKS. However, i think that by using the SOAP-XML-HTTP stack, we have a big advantage compared to CoAP, since character encoding etc. is "done" for that stack, while the CoAP folks essentially had to start from zero. Do you see any action item on either the protocol or transport document out of what your heard in CORE? Alex From ietf@meetecho.com Wed Jul 27 08:08:23 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A619F21F8BA7 for ; Wed, 27 Jul 2011 08:08:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.719 X-Spam-Level: X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBvp7zzTCOMO for ; Wed, 27 Jul 2011 08:08:23 -0700 (PDT) Received: from smtplqs01.aruba.it (smtplqs-out17.aruba.it [62.149.158.57]) by ietfa.amsl.com (Postfix) with SMTP id 51EF621F84E9 for ; Wed, 27 Jul 2011 08:08:21 -0700 (PDT) Received: (qmail 18773 invoked by uid 89); 27 Jul 2011 15:08:19 -0000 Received: from unknown (HELO smtpw2.aruba.it) (62.149.128.188) by smtplqs01.aruba.it with SMTP; 27 Jul 2011 15:08:19 -0000 Received: (qmail 24254 invoked by uid 89); 27 Jul 2011 15:08:19 -0000 Received: from unknown (HELO aruba.it) (62.149.158.90) by smtpw2.ad.aruba.it with SMTP; 27 Jul 2011 15:08:19 -0000 Date: Wed, 27 Jul 2011 17:08:18 +0200 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: "Meetecho IETF support" To: drinks@ietf.org X-XaM3-API-Version: V3(R2) X-SenderIP: 70.81.226.194 X-Spam-Rating: smtpw2.ad.aruba.it 1.6.2 0/1000/N X-Spam-Rating: smtplqs01.aruba.it 1.6.2 0/1000/N Subject: [drinks] DRINKS recording available X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 15:08:23 -0000 Dear all,=0A=0Athe full recording (synchronized video, audio, slides and = jabber room) =0Aof yesterday's DRINKS session is available at the followi= ng URL:=0A=0Ahttp://www.meetecho.com/ietf81/recordings=0A=0AThere is a sh= ort blackout in the last part, due to the WiFi network that suddenly went= down.=0A=0AFor the chair(s): please feel free to put the link to the rec= ording in the minutes, if you think this might be useful.=0A=0AIn case of= problems with the playout, just drop an e-mail to =0Aietf-support@meetec= ho.com.=0A=0ACheers,=0Athe Meetecho Team From dean.willis@softarmor.com Fri Jul 29 07:08:11 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8596A21F8B99 for ; Fri, 29 Jul 2011 07:08:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zssq6Df-1s+M for ; Fri, 29 Jul 2011 07:08:11 -0700 (PDT) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id C349221F8B96 for ; Fri, 29 Jul 2011 07:08:10 -0700 (PDT) Received: by qwc23 with SMTP id 23so2447588qwc.31 for ; Fri, 29 Jul 2011 07:08:10 -0700 (PDT) Received: by 10.229.68.215 with SMTP id w23mr1017714qci.58.1311948490194; Fri, 29 Jul 2011 07:08:10 -0700 (PDT) Received: from dhcp-678f.meeting.ietf.org (dhcp-678f.meeting.ietf.org [130.129.103.143]) by mx.google.com with ESMTPS id b6sm1394874qcb.11.2011.07.29.07.08.08 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 07:08:09 -0700 (PDT) References: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> <8BC845943058D844ABFC73D2220D46650A9F9FB4@nics-mail.sbg.nic.at> In-Reply-To: <8BC845943058D844ABFC73D2220D46650A9F9FB4@nics-mail.sbg.nic.at> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Message-Id: <43EC21B1-6D00-4578-869B-8C6CD0144141@softarmor.com> Content-Transfer-Encoding: quoted-printable From: Dean Willis Date: Fri, 29 Jul 2011 10:08:06 -0400 To: Alexander Mayrhofer X-Mailer: Apple Mail (2.1084) Cc: drinks@ietf.org Subject: Re: [drinks] Discussion on UETF-8 from CORE working group X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2011 14:08:11 -0000 On Jul 27, 2011, at 9:33 AM, Alexander Mayrhofer wrote: >=20 > Do you see any action item on either the protocol or transport = document > out of what your heard in CORE? >=20 well, I'm not an internationalization expert. I might even be described = as internationalization-phobic (If it's not written in Tejano, it's = foreign!). All I know about it is that for every protocol I've worked = on, it's been much harder than anybody expected. While our WSDL is described in UTF-8, I don't see anything else in the = spec that tells us what kind of encoding the registry data is in. Four = OpenSPP, we've made no real effort to support internationalization. All = the hard string matching is being done inside MySQL, so we sort of have = a "whatever the database does" model going on. Or at least I haven't = seen any string-prep code being invoked. Note that this means I probably = need to add internationalized test-cases to the product backlog. So, unless I'm mistaken and we inherited something from one of the other = specs, I don't know that we have a complete specification on whether or = not we're using UTF-8 or UTF-16 or 7-bit ASCII or ASCII plus a codepage = or multiple codepages (or whatever) and what the comparison rules, etc. = are supposed to be.=20 -- Dean= From alexander.mayrhofer@nic.at Fri Jul 29 07:11:27 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB8321F8BA9 for ; Fri, 29 Jul 2011 07:11:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.297 X-Spam-Level: X-Spam-Status: No, score=-9.297 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v3y3B8otEt9J for ; Fri, 29 Jul 2011 07:11:26 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by ietfa.amsl.com (Postfix) with ESMTP id 1070E21F8BA4 for ; Fri, 29 Jul 2011 07:11:26 -0700 (PDT) Received: from nics-exch.sbg.nic.at ([10.17.175.3]) by mail.sbg.nic.at over TLS secured channel (TLSv1/SSLv3:AES128-SHA:128) with XWall v3.47 ; Fri, 29 Jul 2011 16:11:24 +0200 Received: from nics-mail.sbg.nic.at (10.17.175.2) by NICS-EXCH.sbg.nic.at (10.17.175.3) with Microsoft SMTP Server id 14.1.218.12; Fri, 29 Jul 2011 16:11:17 +0200 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 29 Jul 2011 16:11:12 +0200 Message-ID: <8BC845943058D844ABFC73D2220D46650A9FA1FD@nics-mail.sbg.nic.at> In-Reply-To: <43EC21B1-6D00-4578-869B-8C6CD0144141@softarmor.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AW: [drinks] Discussion on UETF-8 from CORE working group Thread-Index: AcxN+PYOLmXT6a1PSR6mYyFz/v5ABwAAD3BQ References: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> <8BC845943058D844ABFC73D2220D46650A9F9FB4@nics-mail.sbg.nic.at> <43EC21B1-6D00-4578-869B-8C6CD0144141@softarmor.com> From: Alexander Mayrhofer To: Dean Willis X-XWALL-BCKS: auto Cc: drinks@ietf.org Subject: Re: [drinks] Discussion on UETF-8 from CORE working group X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2011 14:11:27 -0000 =20 > So, unless I'm mistaken and we inherited something from one of the other > specs, I don't know that we have a complete specification on whether or not > we're using UTF-8 or UTF-16 or 7-bit ASCII or ASCII plus a codepage or > multiple codepages (or whatever) and what the comparison rules, etc. are > supposed to be. We certainly have open issues here. I'm currently looking at the "Data Validation" issue, and collecting a list of fields and what their constraints might be. I will include internationalization considerations in that list, and look for what other similar procotols do with regards to Internationalization. Alex From ning.zhang@neustar.biz Fri Jul 29 08:21:09 2011 Return-Path: X-Original-To: drinks@ietfa.amsl.com Delivered-To: drinks@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4906A21F866A for ; Fri, 29 Jul 2011 08:21:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.507 X-Spam-Level: X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xG+w1jAZSEz4 for ; Fri, 29 Jul 2011 08:21:08 -0700 (PDT) Received: from neustar.com (mx1.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 4A4DF21F85B1 for ; Fri, 29 Jul 2011 08:21:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1311952864; x=1627312073; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=pynDVtdrce+M3K9ggSx/v YDkmqZhEa9xtjPPrrrF/6c=; b=MtBCbtTWXwfKuKViJi0xdFkW6BYerJ56K2twa q8zceNhYKVDLpTjK6i6oJz+QjXfSios0wEmhO4WOxoK3tshCw== Received: from ([10.31.13.228]) by stihiron1.va.neustar.com with ESMTP with TLS id G6K7MJ1.25338469; Fri, 29 Jul 2011 11:21:03 -0400 Received: from STNTEXCH02.cis.neustar.com ([fe80::f828:7b2d:14aa:84b7]) by STNTEXCHHT01.cis.neustar.com ([::1]) with mapi; Fri, 29 Jul 2011 11:21:02 -0400 From: "Zhang, Ning" To: 'Dean Willis' , Alexander Mayrhofer Date: Fri, 29 Jul 2011 11:21:02 -0400 Thread-Topic: [drinks] Discussion on UETF-8 from CORE working group Thread-Index: AcxN+PYu8DFtrasTSp63HafdyiCEXAABphIQ Message-ID: <38CC7FDA6EE9B24C992FA3CC8F26FC051E922920F1@STNTEXCH02.cis.neustar.com> References: <9343F740-152E-4AFA-8140-C17F009D94C2@softarmor.com> <8BC845943058D844ABFC73D2220D46650A9F9FB4@nics-mail.sbg.nic.at> <43EC21B1-6D00-4578-869B-8C6CD0144141@softarmor.com> In-Reply-To: <43EC21B1-6D00-4578-869B-8C6CD0144141@softarmor.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA== x-ems-stamp: jGXJFFDcuKxaH0WHMxVoXQ== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "drinks@ietf.org" Subject: Re: [drinks] Discussion on UETF-8 from CORE working group X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2011 15:21:09 -0000 For the protocol, UTF-8 encoding is fine for I18N. The issues are mainly to be dealt in the implementation. I had some experience on UTF-8 with C++/Java, Oracle/Postgres/MySQL before. The XML parser such as Xerces in C++/Java would always store strings extrac= ted from XML messages in Unicode. Depending on the database support and setup, the underlying C/Java code may= need to do some translations before putting a string data into the databas= e, or after getting data from the database. For example, if the db set up is UTF-8, and the db driver does not support = Unicode to UTF-8 conversion automatically, the application code would need = to convert the string in UTF-8. Additionally, there is an issue related to table column length. For example= , a Unicode string of 16 chars may be translated into a UTF-8 string of 20 = chars. This would require the application code for performing string length= validations. If required, one may need to perform IDN validations based on RFC 5891. -----Original Message----- From: drinks-bounces@ietf.org [mailto:drinks-bounces@ietf.org] On Behalf Of= Dean Willis Sent: Friday, July 29, 2011 10:08 AM To: Alexander Mayrhofer Cc: drinks@ietf.org Subject: Re: [drinks] Discussion on UETF-8 from CORE working group On Jul 27, 2011, at 9:33 AM, Alexander Mayrhofer wrote: >=20 > Do you see any action item on either the protocol or transport document > out of what your heard in CORE? >=20 well, I'm not an internationalization expert. I might even be described as = internationalization-phobic (If it's not written in Tejano, it's foreign!).= All I know about it is that for every protocol I've worked on, it's been m= uch harder than anybody expected. While our WSDL is described in UTF-8, I don't see anything else in the spec= that tells us what kind of encoding the registry data is in. Four OpenSPP,= we've made no real effort to support internationalization. All the hard st= ring matching is being done inside MySQL, so we sort of have a "whatever th= e database does" model going on. Or at least I haven't seen any string-prep= code being invoked. Note that this means I probably need to add internatio= nalized test-cases to the product backlog. So, unless I'm mistaken and we inherited something from one of the other sp= ecs, I don't know that we have a complete specification on whether or not w= e're using UTF-8 or UTF-16 or 7-bit ASCII or ASCII plus a codepage or multi= ple codepages (or whatever) and what the comparison rules, etc. are suppose= d to be.=20 -- Dean _______________________________________________ drinks mailing list drinks@ietf.org https://www.ietf.org/mailman/listinfo/drinks