Re: [alto] Proto writeup for ALTO deployment draft

"Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia.com> Wed, 06 April 2016 20:03 UTC

Return-Path: <sabine.randriamasy@nokia.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C1112D73A for <alto@ietfa.amsl.com>; Wed, 6 Apr 2016 13:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLLJ_HAee2yW for <alto@ietfa.amsl.com>; Wed, 6 Apr 2016 13:03:17 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF5B112D608 for <alto@ietf.org>; Wed, 6 Apr 2016 13:03:16 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id E3EFB36129271 for <alto@ietf.org>; Wed, 6 Apr 2016 20:03:11 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u36K3FaW019949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 6 Apr 2016 20:03:15 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u36K3CmW004915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Apr 2016 22:03:14 +0200
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.125]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Wed, 6 Apr 2016 22:03:12 +0200
From: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia.com>
To: "Gurbani, Vijay (Nokia - US)" <vijay.gurbani@nokia.com>, IETF ALTO <alto@ietf.org>
Thread-Topic: [alto] Proto writeup for ALTO deployment draft
Thread-Index: AQHRkDD6UlY2BmdejEKEFZTZ2pnsr599XgPg
Date: Wed, 06 Apr 2016 20:03:12 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A017F87A381@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <57055352.7070104@bell-labs.com>
In-Reply-To: <57055352.7070104@bell-labs.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/Kd5asLhBFVbn3qs2yteIK4chQ0o>
Subject: Re: [alto] Proto writeup for ALTO deployment draft
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2016 20:03:19 -0000

Hi Vijay,

The current writeup is perfectly fine with me.
Thanks, 
Sabine


>>-----Message d'origine-----
>>De : alto [mailto:alto-bounces@ietf.org] De la part de EXT Vijay K.
>>Gurbani
>>Envoyé : mercredi 6 avril 2016 20:20
>>À : IETF ALTO
>>Objet : [alto] Proto writeup for ALTO deployment draft
>>
>>All: I am the shepherd for the ALTO deployment draft.  The draft is
>>close to being done and the working group is awaiting the release of
>>version -14.
>>
>>In preparation of moving the draft ahead when version -14 becomes
>>available, I have filled in the proto-writeup as indicated below.
>>Let me know of any issues and concerns with the writeup.
>>
>>Thanks.
>>
>>1. Summary.
>>
>>Vijay K. Gurbani is the document shepherd for draft-alto-deployments
>>draft.
>>Spencer Dawkins was the responsible AD throughout the last few versions
>>of the draft, however, that benefit transferred to Mirja Kuhlewind
>>around IETF 95 (Buenos Aires).
>>
>>The document itself has a long and varied history, having started life
>>off as a -00 document targeted to the ALTO WG as an individual
>>(original authors:
>>Martin Stiemerling and Sebsatian Kiesel, March 1, 2010).  It
>>transitioned to a WG document in February 2011 with the original two
>>authors and continued on revision trajectory until version -04 when new
>>authors were added.
>>
>>The document distills and prescribes recommendations for network
>>administrators and application designers planning to deploy ALTO,
>>including recommendations on how to generate the ALTO map information
>>and known limitations of the ALTO protocol (rfc7285).  Furthermore, the
>>document provides guidance for the use of ALTO in diverse environments,
>>including P2P traffic optimization, CDN considerations, application
>>guidance in VPNs, to name a few examples.
>>
>>The working group is targeting this document as an Informational, which
>>is the appropriate track the document should be on based on the nature
>>of its prescriptions and recommendations.  The document does not
>>introduce any new protocol elements, nor does it subvert --- positively
>>or negatively --- the usage of the protocol in any given particular
>>environment (i.e., CDNs, VPNs, or P2P environments).
>>
>>2. Review and Consensus.
>>
>>The draft has consensus from the WG and has been well-reviewed.  There
>>have been two WGLCs for this draft: Version -11 of the draft was last-
>>called between the time period of April 28, 2015 to May 17, 2015.
>>During this period, the draft was reviewed in detail by Wendy Roome.
>>Wendy found several minor issues and nits and a couple of major issues,
>>all of which were readily addressed in version -12 (June 2015).
>>
>>Pursuant to an ALTO virtual meeting held on October 27, 2015, it became
>>apparent that draft-siedel-alto-map-calculation could inform draft-
>>ietf-alto-deployments.  The authors of the two drafts were requested to
>>make a determination whether portions of the former could be included
>>in the latter.  By November 2015, a determination was made that
>>relevant portions from the map-calculation draft could be put into the
>>deployment-considerations draft.  The issue at hand after this was done
>>was whether the changes percolated widely enough to have a second WGLC.
>>By Jan 2016, it was decided that a second WGLC was likely, and thus a
>>second one was issued that ended on February 3, 2016.  The second WGLC
>>was reviewed by Sabine Randriamasy, resulting in version -14 that
>>addressed her review.
>>
>>In summary, the deployment draft has had excellent support from the
>>working group, has been reviewed on multiple occasions by various
>>members of the working group and has been last-called twice to account
>>for the expanded role it took on as the working group became aware of
>>the growing deployment of the ALTO protocol.
>>
>>3. Intellectual Property.
>>
>>The shepherd confirms that each author has stated to him (and ALTO
>>co-chairs)
>>their direct, personal knowledge that the authors are not aware of any
>>IPR related to this document.
>>
>>To the best of the shepherd's knoweldge, there has not been any
>>discussions on IPR related to this document on the ALTO WG mailing
>>list.
>>
>>4. Other Points.
>><To be enumerated when -14 becomes available.>
>>
>>Thanks,
>>
>>- vijay
>>--
>>Vijay K. Gurbani, Bell Laboratories, Nokia Networks 1960 Lucent Lane,
>>Rm. 9C-533, Naperville, Illinois 60563 (USA)
>>Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@nokia.com
>>Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq
>>
>>_______________________________________________
>>alto mailing list
>>alto@ietf.org
>>https://www.ietf.org/mailman/listinfo/alto