Re: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06
"Mcdysan, David E" <dave.mcdysan@verizon.com> Tue, 21 June 2011 14:03 UTC
Return-Path: <dave.mcdysan@verizon.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 C6D5411E814F for <tsvwg@ietfa.amsl.com>; Tue, 21 Jun 2011 07:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level:
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 1zt2uTuHkhxA for <tsvwg@ietfa.amsl.com>; Tue, 21 Jun 2011 07:03:29 -0700 (PDT)
Received: from sacmail2.verizon.com (sacmail2.verizon.com [192.76.84.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA2211E80B8 for <tsvwg@ietf.org>; Tue, 21 Jun 2011 07:03:26 -0700 (PDT)
Received: from fldsmtpi03.verizon.com (fldsmtpi03.verizon.com [166.68.71.145]) by sacmail2.verizon.com (8.13.7+Sun/8.13.3) with ESMTP id p5LE3N7u016792 for <tsvwg@ietf.org>; Tue, 21 Jun 2011 10:03:23 -0400 (EDT)
From: "Mcdysan, David E" <dave.mcdysan@verizon.com>
X-IronPort-AV: E=Sophos;i="4.65,401,1304294400"; d="scan'208";a="77096429"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi03.verizon.com with ESMTP; 21 Jun 2011 14:03:23 +0000
Received: from fhdp1lumxc7v11.us.one.verizon.com ([169.254.1.164]) by FHDP1LUMXC7HB04.us.one.verizon.com ([166.68.59.191]) with mapi; Tue, 21 Jun 2011 10:03:23 -0400
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Date: Tue, 21 Jun 2011 10:03:21 -0400
Subject: Re: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06
Thread-Topic: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06
Thread-Index: AcwwG/ta7YuDJQFiQVWeeKz//yko8g==
Message-ID: <CA261C89.19FC2%dave.mcdysan@one.verizon.com>
In-Reply-To: <4DFF058D.1010309@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.1.0.101012
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Jun 2011 09:54:10 -0700
Cc: "James M. Polk" <jmpolk@cisco.com>
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: Tue, 21 Jun 2011 14:03:30 -0000
On Monday6/20/11 4:32 AM, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk> 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. I think this is a good idea. It is a potential solution to some requirements for composite links soon to be published by the rtgwg. These extensions could be used in RSVP-TE to meet these requirements. > > >* 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! I can be a reviewer. > > >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