[e2e] a means to an end

Fred Baker fred at cisco.com
Fri Nov 7 16:00:23 PST 2008

On Nov 7, 2008, at 3:33 PM, Lloyd Wood wrote:
> On 6 Nov 2008, at 21:18, Fred Baker wrote:
>> It's kind of hard to get a message to a destination, fixed or  
>> mobile, without giving the network an idea of where it is to go.  
>> That's kind of the point of the locator.
>> That said, the point of the endpoint ID is to identify the  
>> application on the system, the transport connection endpoint,  
>> independent of its location. If the application moves from one  
>> system to another, the transport connection needs to be able to  
>> follow it.
> can anyone explain how that clear explanation of the endpoint ID  
> matches with the definition of endpoint ID given in RFC5050, section  
> 4.4?

About the same way the description maps to the endpoint ID found in  
RFC 5201-5201 and 5338. Like HIP's Endpoint ID, DTN's Bundle ID lacks  
any way for a system, given knowledge of what instance of an  
application it wants to talk with or what data object it wants to  
find, to determine the locator of that object. Given the locator we  
can establish whether we are talking to the right system, but not the  
other way around.

David is postulating that the only thing we need is a name for the  
object we want to look at, and we can determine everything else we  
need to know. It's wonderful theory, and on an isolated LAN it might  
even make sense.

More information about the end2end-interest mailing list