[RRG] application endpoint identifiers in map-and-encaps schemes

["Templin, Fred L" <Fred.L.Templin@boeing.com>]

During the RRG meeting on Saturday, Lixia presented a slide
suggesting that not only locators and identifiers are desired,
but also a possible separation in the identifer in terms of
what the physical interface of the end node sees and what the
*application endpoint* within the end node sees. I interpret
this as follows:

 - let locators be assigned to the tunnel interfaces of
   ingress/egress tunnel routers
 - let *node* identifiers be assigned to the physical
   interfaces of end systems
 - let *application* identifiers be assigned to virtual
   interfaces (e.g., loopback interfaces) within end
   systems

This could allow for the Ethernet-to-WiFi handoff Lixia referred
to in her slide with no need to readdress the application endpoint
identifiers, since only the node identifier changes.

The following text from (IPvLX, Section 3) speaks to this:

"3.  Addressing and Routing Assumptions

   While IPv4 addresses in the current Internet are typically assigned
   to devices, IPvLX assumes that IPv6 addresses will also be assigned
   to application endpoints and data objects [NAME].  This new model
   would provide greater flexibility such that each end-node might host
   many different IPv6 application endpoints and data objects, and that
   those entities could migrate to other end-nodes.  In this model, each
   IPv6 addressable entity would access other endpoints via an IPv6
   router."

Fred
fred.l.templin@boeing.com

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg