From alexander.mayrhofer@nic.at Mon Sep 28 01:21:00 2009 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E3443A679C for ; Mon, 28 Sep 2009 01:21:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.721 X-Spam-Level: X-Spam-Status: No, score=-7.721 tagged_above=-999 required=5 tests=[AWL=-0.891, BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1lLbctyJ5IB for ; Mon, 28 Sep 2009 01:20:59 -0700 (PDT) Received: from mail.sbg.nic.at (mail.sbg.nic.at [192.174.68.200]) by core3.amsl.com (Postfix) with ESMTP id DB5E83A66B4 for ; Mon, 28 Sep 2009 01:20:57 -0700 (PDT) Received: from localhost [127.0.0.1] by mail.sbg.nic.at with XWall v3.44 ; Mon, 28 Sep 2009 10:22:13 +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: Mon, 28 Sep 2009 10:22:12 +0200 Message-ID: <8BC845943058D844ABFC73D2220D466508946F13@nics-mail.sbg.nic.at> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Hiroshima, Virtual Interim & Milestones Proposal Thread-Index: AcpACY8iRB3eElkxTgOWxO+X1w6vSA== From: "Alexander Mayrhofer" To: X-XWALL-BCKS: auto Subject: [drinks] Hiroshima, Virtual Interim & Milestones Proposal X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2009 08:21:00 -0000 All, Richard and me had a lengthy discussion about whether or not to hold a session in Hiroshima. Unfortunately it is now fixed that neither of the co-chairs can attend the meeting in person. In addition, a poll that we have performed about attendance (http://doodle.com/8xgg5g9bnzrhaka8) in addition to private messages have indicated that interest among the main contributors is very low.=20 Therefore, we have decided to NOT have a session in Hiroshima.=20 However, to proceed with work efficiently, we are looking into holding a Virtual Interim Meeting for DRINKS. We're currently sorting out potential dates for that, and will come up with a proposal very soon. It will likely be a longer meeting than a typical "physical" session slot. One action item to be followed up from the Stockholm session is the Milestones Update for the group. Our current Milestones are horribly outdated, and are as follows: Sep 2008: Requirements for Session Establishment Data (SED) Exchanges Nov 2008: Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners. Feb 2009: Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases We have already proposed updated milestones in the Stockholm session, with the major change (besides shifting all Milestones by 1.5 years) being the split between protocol and transport documents. Please consider the following as a first rough "strawman proposal" up for discussion: April 2010: Submitting a document about Requirements and Use Cases for Session Establishment Data (SED) Exchanges to the IESG as Proposed Standard. July 2010: Submitting the Protocol Document about Exchange of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners to the IESG as Proposed Standard. July 2010: Sumitting a Transport mapping document for the Exchange of Session Establishment Data (SED) to the IESG as Proposed Standard. Nov 2010: Submitting a document about Exchanging Session Establishment Data (SED) from registries to Location Routing Function Databases as Proposed Standard to the IESG. Please comment on the above proposed milestones (timeframe, scope realistic?) - also, if you have other work that you would like the WG to achieve in the near future, please bring it forward now (and note that we would also expect you to contribute on that work!) Thanks Alex & Richard From kcartwright@tnsi.com Mon Sep 28 06:39:44 2009 Return-Path: X-Original-To: drinks@core3.amsl.com Delivered-To: drinks@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D8F13A689E for ; Mon, 28 Sep 2009 06:39:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.311 X-Spam-Level: X-Spam-Status: No, score=-2.311 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWmarMFlr2E5 for ; Mon, 28 Sep 2009 06:39:42 -0700 (PDT) Received: from tnsi.com (relayus.tnsi.com [208.224.248.44]) by core3.amsl.com (Postfix) with ESMTP id 5A5E83A6818 for ; Mon, 28 Sep 2009 06:39:41 -0700 (PDT) Received: from ([172.17.7.231]) by relayus.tnsi.com with ESMTP with TLS id 4440551.34313966; Mon, 28 Sep 2009 09:43:02 -0400 Received: from TNS-MAIL-NA.win2k.corp.tnsi.com ([172.17.7.214]) by MAIL-HUB-NA.win2k.corp.tnsi.com ([172.17.7.231]) with mapi; Mon, 28 Sep 2009 09:40:48 -0400 From: "Cartwright, Kenneth" To: Alexander Mayrhofer , "drinks@ietf.org" Date: Mon, 28 Sep 2009 09:40:45 -0400 Thread-Topic: Hiroshima, Virtual Interim & Milestones Proposal Thread-Index: AcpACY8iRB3eElkxTgOWxO+X1w6vSAAN7CBw Message-ID: <754963199212404AB8E9CFCA6C3D0CDA08FB15436B@TNS-MAIL-NA.win2k.corp.tnsi.com> References: <8BC845943058D844ABFC73D2220D466508946F13@nics-mail.sbg.nic.at> In-Reply-To: <8BC845943058D844ABFC73D2220D466508946F13@nics-mail.sbg.nic.at> 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] Hiroshima, Virtual Interim & Milestones Proposal X-BeenThere: drinks@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF DRINKS WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Sep 2009 13:39:44 -0000 Those dates look fine to me. With respect to the protocol I see the major = feedback from Stockholm as: 1) Do not use NAPTRs as the provisioning data structure. This is a signifi= cant, but good, change to the current protocol design that will take some t= ime. 2) Not going to design extremes to allow the use of classic REST is perfect= ly fine, even desirable. Focus on XML based "protocol" data structures and= a SOAP based "transport". 3) Need to separate the LUF protocol out from the LRF protocol to allow, bu= t not require, the logical and/or physical separation of the provisioning a= ctivities related to these two functions in cases where that is appropriate= . This is a significant change to the current protocol design that will tak= e some time. Ken -----Original Message----- From: drinks-bounces@ietf.org [mailto:drinks-bounces@ietf.org] On Behalf Of= Alexander Mayrhofer Sent: Monday, September 28, 2009 4:22 AM To: drinks@ietf.org Subject: [drinks] Hiroshima, Virtual Interim & Milestones Proposal All, Richard and me had a lengthy discussion about whether or not to hold a session in Hiroshima. Unfortunately it is now fixed that neither of the co-chairs can attend the meeting in person. In addition, a poll that we have performed about attendance (http://doodle.com/8xgg5g9bnzrhaka8) in addition to private messages have indicated that interest among the main contributors is very low. Therefore, we have decided to NOT have a session in Hiroshima. However, to proceed with work efficiently, we are looking into holding a Virtual Interim Meeting for DRINKS. We're currently sorting out potential dates for that, and will come up with a proposal very soon. It will likely be a longer meeting than a typical "physical" session slot. One action item to be followed up from the Stockholm session is the Milestones Update for the group. Our current Milestones are horribly outdated, and are as follows: Sep 2008: Requirements for Session Establishment Data (SED) Exchanges Nov 2008: Exchanging of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners. Feb 2009: Exchange of Session Establishment Data (SED) from registries to Location Routing Function databases We have already proposed updated milestones in the Stockholm session, with the major change (besides shifting all Milestones by 1.5 years) being the split between protocol and transport documents. Please consider the following as a first rough "strawman proposal" up for discussion: April 2010: Submitting a document about Requirements and Use Cases for Session Establishment Data (SED) Exchanges to the IESG as Proposed Standard. July 2010: Submitting the Protocol Document about Exchange of Session Establishment Data (SED) from data providers to registries or between bi/multi-lateral partners to the IESG as Proposed Standard. July 2010: Sumitting a Transport mapping document for the Exchange of Session Establishment Data (SED) to the IESG as Proposed Standard. Nov 2010: Submitting a document about Exchanging Session Establishment Data (SED) from registries to Location Routing Function Databases as Proposed Standard to the IESG. Please comment on the above proposed milestones (timeframe, scope realistic?) - also, if you have other work that you would like the WG to achieve in the near future, please bring it forward now (and note that we would also expect you to contribute on that work!) Thanks Alex & Richard _______________________________________________ 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.