Re: [Tsvwg] WGLC for draft-ietf-tsvwg-quickstart-04 NOW

Sally Floyd <floyd@icir.org> Fri, 14 July 2006 14:33 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1Oji-00074R-16; Fri, 14 Jul 2006 10:33:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1Ojh-00074M-H1 for tsvwg@ietf.org; Fri, 14 Jul 2006 10:33:45 -0400
Received: from cougar.icir.org ([192.150.187.76]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1Ojf-0007Ci-6M for tsvwg@ietf.org; Fri, 14 Jul 2006 10:33:45 -0400
Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.12.11/8.12.11) with ESMTP id k6EEXXQg011893; Fri, 14 Jul 2006 07:33:33 -0700 (PDT) (envelope-from floyd@cougar.icir.org)
Message-Id: <200607141433.k6EEXXQg011893@cougar.icir.org>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
From: Sally Floyd <floyd@icir.org>
Subject: Re: [Tsvwg] WGLC for draft-ietf-tsvwg-quickstart-04 NOW
Date: Fri, 14 Jul 2006 07:33:33 -0700
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg <tsvwg@ietf.org>, mallman@icir.org, Lars Eggert <lars.eggert@netlab.nec.de>, Pasi Sarolahti <pasi.sarolahti@iki.fi>, "James M. Polk" <jmpolk@cisco.com>
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>
Errors-To: tsvwg-bounces@ietf.org

Dan -

>An editorial nit: 
>
>References in the MIB module do not follow the same convention as the
>References section (e.g. [RFC791]) which leads to idnits tools to
>complain about un-used references. It is worth fixing whenever a new
>version occurs. 

Will do.  (Though perhaps one day the idnits tool will learn that
"[RFC2581, RFC3390]" in the text in fact qualifies as two valid
references.  My memory is that this was the problem.)

- Sally
http://www.icir.org/floyd/