My motivation for each vote:

A1) A "node" is either a host or a router.

Not OK. I consider "host" a service related term.

A2) A "router" is any device that forwards packets at the 
  Network Layer (e.g. IPv4, IPv6) of the Internet Architecture.  

Not OK. Since it forwards packets, "forwarder" is a better term. I profess 
Role-Based Architecture, not layering.

A3) A "host" is a device that can send/receive packets 
  to/from the network, but does not forward packets.  

Not OK. I consider "host" a service related term.

A4) A "bridge" is a device that forwards packets at the 
  Link Layer (e.g. Ethernet) of the Internet Architecture.  
  An Ethernet switch or Ethernet hub are examples of bridges.

Not OK. I profess Role-Based Architecture, not layering.

B) An "Address" is an object that combines aspects of identity 
  with topological location.  IPv4 and IPv6 addresses are 
  current examples.

Not OK. An "address" is a (legacy) name, not an object. 

C) A "Locator" is a structured topology-dependent name that 
  is not used for node identification, and is not a path.  
  Two related meanings are current, depending on the class 
  of things being named:
        1) The topology-dependent name of a node's interface.
        2) The topology-dependent name of a single subnetwork
           OR topology-dependent name of a group of related 
           subnetworks that share a single aggregate.   An 
           IP routing prefix is a current example of this last.

Not OK. A "locator" is a structured topology-dependent name of a node. It is 
used to determine the topological location of the node.

D) An "Identifier" is a topology-independent name for a logical 
  node. Depending upon instantiation, a "logical node" might be 
  a single physical device, a cluster of devices acting as a 
  single node, or a single virtual partition of a single physical 
  device.  An OSI End System Identifier (ESID) is an example of 
  an identifier.  A Fully-Qualified Domain Name that precisely 
  names one logical node is another example. (Note well that not 
  all FQDNs meet this definition.)

Not OK. A fully-qualified domain name that precisely names one logical node is 
a human-readable name of the node. We must not impose irrelevant meaning upon 
terms.

E) Various other names (i.e. other than addresses, locators, 
  or identifiers), each of which has the sole purpose of 
  identifying a component of a logical system or physical device, 
  might exist at various protocol layers in the Internet Architecture.

Not OK. I profess Role-Based Architecture, not layering. It saves redundant 
terminology.

Thanks for asking.
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg

Reply via email to