Re: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06
Francois Le Faucheur <flefauch@cisco.com> Mon, 20 June 2011 13:54 UTC
Return-Path: <flefauch@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90FE111E8150 for <tsvwg@ietfa.amsl.com>; Mon, 20 Jun 2011 06:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.371
X-Spam-Level:
X-Spam-Status: No, score=-9.371 tagged_above=-999 required=5 tests=[AWL=1.227, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 l6afkaq0KWI8 for <tsvwg@ietfa.amsl.com>; Mon, 20 Jun 2011 06:54:31 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id DF01D11E808A for <tsvwg@ietf.org>; Mon, 20 Jun 2011 06:54:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=flefauch@cisco.com; l=4628; q=dns/txt; s=iport; t=1308578071; x=1309787671; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=wBaUS4wnlxEg1ItNqnpqM4C0kZwB2/FwcuYo6oGOt6A=; b=UnNO4mU1sHwZVyB4qZj6cjUWRnwgcRId36Z7HxSJNPsVd7yN06MwgXPj dRE2l59J9D2fU08STSeLzBDnEolhKy4/ETd9Mhvmoj5/yTJjvg3xZDJH/ Cstw8MyijCxfyrKfZDChgshb6yK5ObsZ6a5Clf4yc8i0RSX1Fg1NuFqJF A=;
X-IronPort-AV: E=Sophos; i="4.65,394,1304294400"; d="scan'208,217"; a="36072402"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 20 Jun 2011 13:54:30 +0000
Received: from ams-flefauch-8718.cisco.com (ams-flefauch-8718.cisco.com [10.55.161.201]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5KDsT41007616; Mon, 20 Jun 2011 13:54:29 GMT
Subject: Re: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-622--441491285"
From: Francois Le Faucheur <flefauch@cisco.com>
In-Reply-To: <4DFF058D.1010309@erg.abdn.ac.uk>
Date: Mon, 20 Jun 2011 15:56:30 +0200
Message-Id: <6A077FD4-9847-4663-AA9B-CDC66E68CBEE@cisco.com>
References: <4DFF058D.1010309@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1084)
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg WG <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2011 13:54:32 -0000
Hello Gorry, It is a good idea. As you know I already provided comments on this doc, but I will review it again during its development. In fact, it is on my ToDo list before Quebec City meeting. Thanks Francois On 20 Jun 2011, at 10:32, Gorry Fairhurst wrote: > The authors of "IntServ Extension to Allow Signaling of Multiple Traffic Specifications and Multiple Flow Specifications in RSVPv1" (draft-polk-tsvwg-intserv-multiple-tspec) requests that this is adopted as WG item. > > This draft defines extensions to Integrated Services (IntServ) > allowing multiple traffic specifications and multiple flow > specifications to be conveyed in the same Resource Reservation > Protocol (RSVPv1) reservation message exchange. This ability helps > optimize an agreeable bandwidth through a network between endpoints > in a single round trip > > There was hum indicating general WG support for this at the last IETF in Prague. I applied to the AD to amend our Charter to allow this work, which was approved. So we are now ready to make a formal decision and this email is to allow people to confirm that there is sufficient energy to complete this work in TSVWG. > > > * PLEASE send an email to this list if you think adopting this document in TSVWG is a good or bad idea. > > * Please also indicate if you are willing to REVIEW such a document during its development - our AD has indicated that we expect to have at least 4 people who commit to review this within the WG, perform a detailed review in WGLC and provide appropriate comments if called upon during the IESG review. If you can promise to do this please say! > > > Please provide any comments at the latest by Wednesday 29th June 2011. > > > Best regards > > Gorry Fairhurst > (TSVWG Co-Chair) > >
- Call for WG Adoption of draft-polk-tsvwg-intserv-… Gorry Fairhurst
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Bruce Davie
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Lou Berger
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Francois Le Faucheur
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… ken carlberg
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Janet P Gunn
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Scott O. Bradner
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Mcdysan, David E
- Re: Call for WG Adoption of draft-polk-tsvwg-ints… Randy Stewart