Re: Call for WG Adoption of draft-polk-tsvwg-intserv-multiple-tspec-06

Bruce Davie <bdavie@cisco.com> Mon, 20 June 2011 12:24 UTC

Return-Path: <bdavie@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 1E4029E8021 for <tsvwg@ietfa.amsl.com>; Mon, 20 Jun 2011 05:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 rQ6Au6pB2Q6W for <tsvwg@ietfa.amsl.com>; Mon, 20 Jun 2011 05:24:39 -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 00F5B9E8020 for <tsvwg@ietf.org>; Mon, 20 Jun 2011 05:24:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bdavie@cisco.com; l=1596; q=dns/txt; s=iport; t=1308572679; x=1309782279; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=aHOwrkzxhvLHBH7Kc8hHjjRp+ESfyGsfAy3N9wpg52g=; b=PxMKt06H0hfKwp6ISoKzoSTrZQtF7aNFVo2cQO6esSon9X60bttTpacm 82CxrLWir1NlegYfoqC2N03xE25IP9ZHS31d3h8SM4jxbxwMUzlNkYkCk glrYv5NPqFLM8f8IVEVxK+kIMfb8ymuPPLJntVTNb2Ca4tJRbwn/w493J s=;
X-IronPort-AV: E=Sophos;i="4.65,394,1304294400"; d="scan'208";a="36053075"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-2.cisco.com with ESMTP; 20 Jun 2011 12:24:35 +0000
Received: from [10.32.241.77] ([10.32.241.77]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p5KCOVIQ024846; Mon, 20 Jun 2011 12:24:32 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: text/plain; charset="us-ascii"
From: Bruce Davie <bdavie@cisco.com>
In-Reply-To: <4DFF058D.1010309@erg.abdn.ac.uk>
Date: Mon, 20 Jun 2011 08:24:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A85F10E-9A41-4901-A0F1-9F654B20C213@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 <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 12:24:40 -0000

On Jun 20, 2011, at 4:32 AM, 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.

Good idea (I'm sure my view will come as a shock)

> 
> * 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 will provide (another) review.

Bruce