Subject: [NSIS] framework update

From: "Hancock, Robert" <[email-masked]>
Date: Sun, 3 Nov 2002 01:42:20 -0000

dear all,

i've been trying to put together a framework update before the official atlanta deadline. basically, the aim is to clarify terminology issues and eliminate some ambiguities of scope/emphasis that comments on the mailing list have thrown up, and *not* to make any substantive technical changes. 

with any luck, this should make it easier to progress on the real subjects.

i've listed the changes in extremely abbreviated form below (in fact, it's the change log from my working version). if any of these ring alarm bells with people, let me know and i'll try to back them out before the submission. however, i've not seen continuing objections to any of them (except that there will never be enthusiastic agreement on terminology, but that's life...)

cheers,

robert h.

=========================================================================

1.	Editorial fix in 'classifier' definition (section 2).
2.	Added definition of 'peer determination' (finding the right peer for a given flow) (section 2).
3.	Added definitions for 'sender' and 'receiver' refers to role relative to data packets always (section 2, and minor fixes in sections 3.2.6 and 3.2.7).
4.	Updated references.
5.	Replaced 'peer session' with 'peer relationship' and 'peer session addressing' with 'peer-peer addressing' (throughout), and attempted redraw of Figure 1 to make it less session-like (corresponding changes in Figure 4, Figure 7, Figure 8, and Figure 9).
6.	Added terms for transport and signaling layer protocols (NTLP/NSLP) and explanation in new section 3.1.3. New terms used throughout (significant rewrites to section 4, although this should be at most a change of emphasis rather than technical content).
7.	Clarified that section 3.2 is about possible modes of operation (listing alternatives, not all to be supported).
8.	Clarified 'local object' definition in 3.2.4.
9.	Added working assumption in 3.3.1 that end-to-end routing is done by sequentially determining the right peer in the NTLP, and no-one discovers or uses global topology information for this.
10.	Added working assumption in 3.3.3 that NTLP operates only locally.
11.	Slightly trimmed 3.3.5 in preparation for turning it into a discussion about NSIS layering boundaries.
12.	Clarified in section 4.2 that peer determination doesn't have to be a separate capability, just that it could additionally be done separately.
13.	Fixed some flow identification terminology inconsistencies in section 5.3.1.

========================================================================
_______________________________________________
nsis mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/nsis