That is a very specific kind of identifier. It sounds to me like the
definition of session identifier.
Scott and I have been known to discuss whether that is the only
identifier the protocol needs. But it is certainly not the only
identifier that the architecture needs to be able to discuss.
Yours,
Joel
William Herrin wrote:
Briefly:
Identifier: Any element in the ongoing communication between a user
and a network service he uses which is statically bound to the
function of correlating the communication's data packets with the
communication as a whole.
_______________________________________________
rrg mailing list
[email protected]
http://www.irtf.org/mailman/listinfo/rrg
