[NSIS] yet another terminology proposal

"Hancock, Robert" <robert.hancock@roke.co.uk> Mon, 28 October 2002 13:43 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08764 for <nsis-archive@odin.ietf.org>; Mon, 28 Oct 2002 08:43:28 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SDjKn23976 for nsis-archive@odin.ietf.org; Mon, 28 Oct 2002 08:45:20 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SDjIv23969; Mon, 28 Oct 2002 08:45:18 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SDiTv23914 for <nsis@optimus.ietf.org>; Mon, 28 Oct 2002 08:44:29 -0500
Received: from rsys002a.roke.co.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08752 for <nsis@ietf.org>; Mon, 28 Oct 2002 08:42:06 -0500 (EST)
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19) id <VRKGSA89>; Mon, 28 Oct 2002 13:44:25 -0000
Message-ID: <76C92FBBFB58D411AE760090271ED4181EA648@rsys002a.roke.co.uk>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: nsis@ietf.org
Date: Mon, 28 Oct 2002 13:44:24 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [NSIS] yet another terminology proposal
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
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>

hi all,

I suppose it's best to get these firmly settled before the real work starts...

I believe we have general consensus to look at a 2 layer (or 'level') architecture for NSIS signalling, as prefigured in draft-braden-2level-signal-arch-00.txt, and reflected (I hope) in the 00 framework draft (e.g. section 4.3.1), and some other protocol proposals.

However, we don't have good names for these layers. The framework avoided using terms from any existing work, to ensure there was no danger that we were prejudging the protocol choice or even prejudging the inter-layer split. If you accept this argument, we need new terms.

The following have been proposed (for framework use, and "what role is protocol XXXP supposed to perform?" type discussions):

NSIS Transport Layer Protocol (NTLP): the lower layer, responsible for moving messages around, for which we hope there will be a single protocol (at least in any network type); may or may not be based on or include underlying 'standard' transport protocols; independent of the signalling application.

NSIS Signalling Layer Protocol (NSLP): the upper layer, which defines messages (and maybe states or message sequences) which are specific to a particular signalling application. We therefore expect there to be several of these (e.g. 1 or even >1 per signalling application).

Comments? Objections?

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