> -----Original Message----- > From: Christian Vogt [mailto:[email protected]] > Sent: 30 June 2009 20:51 > To: Krug,AL,Louise,CXR9 R > Cc: [email protected]; [email protected] > Subject: Re: [rrg] Next topic: properties of identifiers > > > Is host identification most useful for fault finding? > > > Louise - > > Absolutely. In fact, there is a richness of purposes for > which one may need identifiers. What I claim is that most of > those purposes are application-specific and not essential to > an Internet architecture. For example, fault finding is the > purpose of a debugging application. > > An Internet architecture must be versatile enough to enable > applications to use their own identifiers. But to do this, > the Internet architecture itself must incorporate identifiers > for only two purposes: to identify a peer service for > contact establishment, and to identify a session instantiated > during contact establishment. On top of that, applications > can do what they want, such as providing a means to identify > hosts for fault finding. Does this make sense? > > - Christian > > > It makes sense in the abstract, but I am still mulling the question "if a lot of applications would need something such as a host ID, and the network does not provide it will we end up with a lot of different ways of providing it, and possibly some very nasty ways (like IP addresses got overused). I guess then you might say that you have the core architecture and a set of extras that need to be standardised but you should not expect them to be gloablly available?
Do you think the session need to have a globally unique identifier or locally agreed between the endpoints during the contact establishment? Louise _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
