> "a locally configured communication endpoint of a DNCP node, such
> as a network socket. An endpoint may be bound to a set of
> predefined unicast Addresses representing remote DNCP nodes to
> individually connect to or to accept connections from whereby
> communication with each node is separated (e.g., an individual
> unicast UDP message flow per remote node). An endpoint may also
> be bound to a whole network interface, then multicast
> communication is used (in addition to individual unicast flows) to
> send certain messages to all DNCP nodes connected therewith at
> once as well as to automatically discover new DNCP nodes."
I'm not sure I understand this paragraph. It uses words with many
syllables.
It is my (possibly mistaken) understanding that the nature of an
"endpoint" depends on the mode of operation. So why not use a more
concrete definition?
* in both multicast modes of operation, an endpoint is just a local
interface;
* in both unicast modes of operation, an endpoint is a connected socket,
or, equivalently, a pair of a local socket and a remote socket (or
perhaps a pair of a local socket and one or more remote sockets, I'm
not sure).
In all modes, an endpoint identifier is an arbitrary non-zero integer
that, at any given time, MUST uniquely identify a particular endpoint.
Endpoint identifiers SHOULD NOT be reused too soon after a given endpoint
ceases to exist, but if that happens, DNCP will reconverge after a short
period of chaos.
(I don't think that DNCP requires endpoint identifiers to be non-zero, but
HNCP does, so you might as well make that a requirement of DNCP.)
-- Juliusz
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
