[NSIS] Comment on draft-bradner-nsis-bof-00.txt

john.loughney@nokia.com Tue, 27 November 2001 12:51 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24022 for <nsis-archive@odin.ietf.org>; Tue, 27 Nov 2001 07:51:29 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA00184 for nsis-archive@odin.ietf.org; Tue, 27 Nov 2001 07:51:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00138; Tue, 27 Nov 2001 07:44:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA00102 for <nsis@optimus.ietf.org>; Tue, 27 Nov 2001 07:44:32 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23644 for <nsis@ietf.org>; Tue, 27 Nov 2001 07:44:24 -0500 (EST)
From: john.loughney@nokia.com
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id fARCj7A05952 for <nsis@ietf.org>; Tue, 27 Nov 2001 14:45:07 +0200 (EET)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T577aac1aa5ac158f23134@esvir03nok.nokia.com>; Tue, 27 Nov 2001 14:44:14 +0200
Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <XP21ZQGV>; Tue, 27 Nov 2001 14:44:12 +0200
Message-ID: <0C1353ABB1DEB74DB067ADFF749C4EEF09BC34@esebe004.NOE.Nokia.com>
To: sob@harvard.edu, mankin@isi.edu
Cc: nsis@ietf.org
Date: Tue, 27 Nov 2001 14:44:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [NSIS] Comment on draft-bradner-nsis-bof-00.txt
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Next Steps in Signaling <nsis.ietf.org>
X-BeenThere: nsis@ietf.org

Hi Scott & Allison,

Here are my promised comments on your document.

The first comment is on the Abstract:

   The Transport Area Directors held a Next Steps in Signaling birds of
   a feather session during the 50th IETF meeting in Minneapolis,
   Minnesota.  The aim of the session was to garner an initial set of
   requirements for a next generation Internet signaling protocol.  This
   memo is a summary of the input we received during that session.

It might be useful to put a disclaimer in here (or in the body of
the draft).  The disclaimer should state that the requirements 
contained in the draft are simply input from the speakers.  There
is no intention to fufill all of the requirements, as that would
be attempting to 'boil the ocean.'

Section 2 - typo:

   - RSVP Core & children for DiffServe

-> should be DiffServ

I won't comment on Section 6,7 and 8 - as these are people's
opinions & I for one, do not want to put words in anyone's 
mouth.

The biggest comment I have on the document is after reading it,
I am left with a feeling of 'And?' - would it be useful to
put a section titled 'Next Steps in NSIS' or should this document
simply a record of what happened at the meeting.  Documenting
the meeting is useful in itself.  Perhaps, we (the NSIS mailing
list) should take all of the requirements contained in the 
document and discuss what is applicable and what is not for 
our requirements work.

Final questions - do either one of you wish to present this
at Salt Lake City?

best regards,
John

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