[NSIS] QSPEC Comments
"Tschofenig, Hannes" <hannes.tschofenig@siemens.com> Fri, 12 May 2006 09:09 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeTe8-000818-VM; Fri, 12 May 2006 05:09:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeTe7-000813-Iy for nsis@ietf.org; Fri, 12 May 2006 05:09:15 -0400
Received: from lizzard.sbs.de ([194.138.37.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeTe6-0006y9-1C for nsis@ietf.org; Fri, 12 May 2006 05:09:15 -0400
Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id k4C99DF2026780 for <nsis@ietf.org>; Fri, 12 May 2006 11:09:13 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net [157.163.133.222]) by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id k4C99DQn009040 for <nsis@ietf.org>; Fri, 12 May 2006 11:09:13 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 May 2006 11:09:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 12 May 2006 11:09:07 +0200
Message-ID: <A5D2BD54850CCA4AA3B93227205D8A30614DC0@MCHP7IEA.ww002.siemens.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: QSPEC Comments
Thread-Index: AcZ1odRCtn6HIQz5SteZEa5CaDorsw==
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: nsis <nsis@ietf.org>
X-OriginalArrivalTime: 12 May 2006 09:09:12.0781 (UTC) FILETIME=[BC69D7D0:01C675A3]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [NSIS] QSPEC Comments
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org
Hi all I have a few minor comments for the QSPEC draft: - Use either 'QoS NSLP' or 'QoS-NSLP' terminology. The QoS NSLP draft uses 'QoS NSLP' - Don't use RFC 2119 language in examples (e.g., Section 4.3). The same is true for RFC 2119 language in the appendix. - Review RFC 2119 language in the text. Example: First sentence in Section 4.6: MAY is inappropriate there. - Ability to define mandatory QoS parameters in QOSMs no clear - Reference to [NSIS-EXTENSIBILITY] in the IANA consideration section is not a good idea. It also needs to be removed from the normative reference since otherwise this document will be blocked. - You shouldn't request IANA to allocate value for QOSMs in the QSPEC template document. - Why do you need information of the type of QoS signaling in the QSPEC template (e.g., sender-initiated, receiver-oriented QoS signaling)? - Is the idea of the tunneled parameter flag inline with the QoS NSLP understanding of tunneling? - Use capitalized words in captions and headlines. The RFC editor will thank you. Other comments have been posted by Andrew already (e.g., definition of mandatory parameters). Ciao Hannes _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] QSPEC Comments Tschofenig, Hannes
- RE: [NSIS] QSPEC Comments Ash, Gerald R (Jerry), ALABS