Re: [rsvp-dir] Getting RSVP Directorate Feedback into TSVWG

Bruce Davie <bdavie@cisco.com> Mon, 01 November 2010 22:56 UTC

Return-Path: <bdavie@cisco.com>
X-Original-To: rsvp-dir@core3.amsl.com
Delivered-To: rsvp-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8C543A69CA for <rsvp-dir@core3.amsl.com>; Mon, 1 Nov 2010 15:56:09 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00fu86nZrGv4 for <rsvp-dir@core3.amsl.com>; Mon, 1 Nov 2010 15:56:06 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id D538E3A69C9 for <rsvp-dir@ietf.org>; Mon, 1 Nov 2010 15:56:05 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,277,1286150400"; d="scan'208";a="279246839"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 01 Nov 2010 22:56:07 +0000
Received: from [10.32.241.75] ([10.32.241.75]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id oA1MtxwY001800; Mon, 1 Nov 2010 22:55:59 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Bruce Davie <bdavie@cisco.com>
In-Reply-To: <201011012250.oA1MoRUu007129@sj-core-3.cisco.com>
Date: Mon, 1 Nov 2010 18:55:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD7CFB5D-9E65-45B5-A93E-59F4B6752624@cisco.com>
References: <201011012250.oA1MoRUu007129@sj-core-3.cisco.com>
To: "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: rsvp-dir@ietf.org
Subject: Re: [rsvp-dir] Getting RSVP Directorate Feedback into TSVWG
X-BeenThere: rsvp-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: RSVP directorate <rsvp-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rsvp-dir>, <mailto:rsvp-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rsvp-dir>
List-Post: <mailto:rsvp-dir@ietf.org>
List-Help: <mailto:rsvp-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rsvp-dir>, <mailto:rsvp-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2010 22:56:10 -0000

James,
 I have reviewed the multiple tspec draft and I am in favor of its adoption (as I think I have said before, and, IIRC, I provided details as to why). I think Lixia is also on record as supporting that draft.

 I have asked the directorate for feedback a couple of times, and Bob Briscoe gave some feedback, which led to me gather more info from you as to why these drafts were worthy of consideration. I have provided that info to the directorate.

 I will craft a more publicly acceptable email for the TSVWG list. But I can't speak much more for the directorate than I have done here.

Bruce


On Nov 1, 2010, at 6:50 PM, James M. Polk wrote:

> All
> 
> This is written as both the TSVWG chair and as an individual author of several active IDs into TSVWG.
> 
> As an individual, I didn't think I needed to request this, but I am anyway - because I haven't received any feedback from the RSVP Directorate to date, and we're 5 days away from the next IETF meeting.
> 
> I am requesting that the RSVP Directorate review these two IDs
> 
> http://www.ietf.org/internet-drafts/draft-polk-tsvwg-intserv-multiple-tspec-05.txt and
> http://www.ietf.org/internet-drafts/draft-polk-tsvwg-rsvp-app-id-vv-profiles-01.txt
> 
> Are either or both of these IDs worth the effort of the TSVWG to take on a WG items (or not)?
> 
> Lars freely admits that he considers IntServ to be joined with RSVP wrt the TSVWG charter. We chairs are crafting text for a charter update to reflect that explicitly.
> 
> The MULTI_TSPEC ID has been presented at every IETF, in TSVWG, since San Francisco -- and really was the reason this Directorate formed (because the ADs chose to punt the ball wrt whether to allow the adoption of this WG item by TSVWG).  This Directorate had a BoF of sorts in Anaheim, which was well attended and included a lot of energy.  At issue is that no one from the Directorate provided an ounce of input into TSVWG for the next IETF (in Maastricht), and I - as chair - haven't heard from any of you since Maastricht on either of the documents listed above one way or the other.
> 
> This is where I put my WG chair hat on, as ask - rather bluntly - why there has been zero input into TSVWG even though the Directorate charter (if you will) clearly states reviewing RSVP based IDs is the purpose of the Directorate, and the fact that there are now two IDs sitting in completely limbo awaiting WG input from the Directorate.
> 
> I realize everyone's time here is quite busy, but these IDs need feedback from those chartered to give said feedback.
> 
> Please response on to this nudge on the TSVWG list.
> 
> James
>