Re: Some Comments on ID/Loc Separation Proposals

[Dave Crocker <dhc@dcrocker.net>]

Folks,

draft-crocker-mast-analysis (which will be
draft-crocker-multiaddr-analysis in its next version) has a section
for defining some terms.  The section has been prompted by exactly the
kind of vagueness that the current thread is also trying to fix.

My primary interest is in having precise definitions that we all find
useful and use consistently. Some of the current versions of
definitions in the draft are:

   Endpoint

           refers to "the fundamental entity of and end-end
           communication" [EID]. It is an end-system that participates
           in an association. Endpoints are distinguished from
           intermediate, infrastructure nodes and from hosts.

   Identifier

           refers to a unique label for an endpoint. The label is used
           simply for distinguishing one endpoint from another.
           Because a locator is usually globally unique, it might be
           able to serve as an identifier. However this use will often
           suffer administrative and referential limitations as a
           global identifier for mobile endpoints. This is exemplified
           by the current problems experienced with the dual role of
           IP Addresses.

Suggestions for improving the text are eagerly sought.
           
As with others, I do not think it is useful to have ID refer to an
interface.  Stack, endpoint or process all seem more helpful.

Speaking of 'stack', what definition text would folks like.  The NSRG
paper introduces the construct nicely, but I'm not sure the text there
is what we should live with.

For that matter, what is the difference between endpoint and stack?

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>