On Fri, Dec 4, 2009 at 5:41 AM, Scott Brim <[email protected]> wrote:
> > I guess I should have phrased my question differently. What I wanted to > stress was "Do you think ROUTING AND ADDRESSING requires a session ID" > etc. That is, is this something that must be in a routing and > addressing architecture recommendation? > I believe not. Session ID should reside somewhere between the Transport and the Application layer. (And I think what people mean by session here is something that doesn't break even if the transport connection breaks temporarily.) And I'm not sure whether current port-id is enough for the purpose of session ID. Or we need combination of port-id and socket to come up with a meaningful session ID. -- Regards, DY http://cnu.kr/~dykim
_______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
