[Tsvwg] draft-ietf-tsvwg-bw-reduction - WGLC end /IETF Last Call

Allison Mankin <mankin@psg.com> Thu, 12 January 2006 23:27 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExBqS-0001iX-TN; Thu, 12 Jan 2006 18:27:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ExBqR-0001iR-EB for tsvwg@megatron.ietf.org; Thu, 12 Jan 2006 18:27:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05256 for <tsvwg@ietf.org>; Thu, 12 Jan 2006 18:25:42 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ExBxd-0008HC-4t for tsvwg@ietf.org; Thu, 12 Jan 2006 18:34:30 -0500
Received: from mankin by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <mankin@psg.com>) id 1ExBqP-000BX5-Bc for tsvwg@ietf.org; Thu, 12 Jan 2006 23:27:01 +0000
To: tsvwg@ietf.org
Message-Id: <E1ExBqP-000BX5-Bc@psg.com>
From: Allison Mankin <mankin@psg.com>
Date: Thu, 12 Jan 2006 23:27:01 +0000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [Tsvwg] draft-ietf-tsvwg-bw-reduction - WGLC end /IETF Last Call
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org

Hi, all,

draft-ietf-tsvwg-bw-reduction ended its WGLC with a small exchange
of comments back in September.  I gave it a detailed AD reading
and found only one small concern, a need for the securit
considerations to mention spoofing of bandwidth reduction
actions.  Otherwise with the WGLC so long done, and reviews
long in, it seemed ready for IETF LC, so that has started, but
we're still open for WG comments of any kind as well.

We'll be ready to WGLC some of the more complex RSVP documents
soon, and will IETF Last Call them as promptly!

Allison

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg