Re: TSVWG Status Sept 2011

"James M. Polk" <jmpolk@cisco.com> Wed, 07 September 2011 18:27 UTC

Return-Path: <jmpolk@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 AA75321F8C52 for <tsvwg@ietfa.amsl.com>; Wed, 7 Sep 2011 11:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.348
X-Spam-Level:
X-Spam-Status: No, score=-103.348 tagged_above=-999 required=5 tests=[AWL=-0.749, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id coe79q1KQOVS for <tsvwg@ietfa.amsl.com>; Wed, 7 Sep 2011 11:27:35 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 199D421F8C4A for <tsvwg@ietf.org>; Wed, 7 Sep 2011 11:27:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1296; q=dns/txt; s=iport; t=1315420165; x=1316629765; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=TR1ey4Pq6hCQJkWRwqZezmPYEOYtZvY6o1WH+B28PEo=; b=HtieDPfBHcoIm+Ss875P0m1cd/j12lZPOQJeHz8RqnxyWs1feoTr3mNB 6SUZU6j7kdoZLoFFFT8fgGp8zzJz2thc1vpFRQ1fAyVFpM98/KqkpMEqB 3VLwbK/JWn5xSxfjRhCzl8uuhjg6HsaYxJ0WRrYwDSfhFJU6yUbe2r1nC 4=;
X-IronPort-AV: E=Sophos;i="4.68,346,1312156800"; d="scan'208";a="724223"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 07 Sep 2011 18:29:25 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p87ITOOw025754; Wed, 7 Sep 2011 18:29:24 GMT
Message-Id: <201109071829.p87ITOOw025754@mtv-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 07 Sep 2011 13:29:18 -0500
To: Francois Le Faucheur <flefauch@cisco.com>, "James Polk M." <jmpolk@cisco.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: TSVWG Status Sept 2011
In-Reply-To: <BF647AC9-2AA9-4BF3-A539-B9C7D89F664E@cisco.com>
References: <4E671F4E.5000200@erg.abdn.ac.uk> <BF647AC9-2AA9-4BF3-A539-B9C7D89F664E@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, 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: Wed, 07 Sep 2011 18:27:35 -0000

As an editor of both efforts, I'd say wait for the proposal from me a 
Lou to materialize, then comment on that (thumbs up or down on that), 
then do a review of what the WG is moving forward with.

My co-chair might have a different take though.

James

At 03:44 AM 9/7/2011, Francois Le Faucheur wrote:
>Hi James,
>
>On 7 Sep 2011, at 09:37, Gorry Fairhurst wrote:
>>
>>draft-ietf-tsvwg-intserv-multiple-tspec
>>      WG interest in this topic recorded at IETF-78.
>>     Charter update would be needed to progress this work.
>>     5 Reviews needed to determine energy/technical direction.
>>     Version -05 (presented in Beijing, IETF-79)
>>     Version -06 (presented in Prague, IETF-80)
>>     RSVP directorate was consulted.
>>        2 reviews from RSVP-DIR received (Bruce Davie, ?).
>>        2 additional reviews promised (Ken Carlberg, Francois LeF).
>
>You have been looking into a potential restructuring of the encoding 
>based on Lou's suggestion. If you're going to do this, I'd rather do 
>the review on the updated document. If not, I can review the current 
>version. I'm not arguing you should, or should not do that change, 
>but can you let us know if/when you see that happening, so I plan 
>the review accordingly?
>
>Thanks
>
>Francois