On Fri, Dec 4, 2009 at 6:43 AM, William Herrin <[email protected]> wrote:
> On Thu, Dec 3, 2009 at 4:30 PM, Dae Young KIM <[email protected]> wrote: > > What every packet has to carry is the node address(IP address), but not > the > > session ID. Session ID is a property of the layer up. In the current > > Internet model, socket could be considered as session ID, which, however, > > need not be visible in the packet header where the main job is routing. > > DY, > > The consequence of that choice is a constraint on the routing system: > because the socket's ID isn't carried in the packet, the IP addresses > carried in the packet must match what the transport protocol expects > or the packet can't be associated with the correct socket. If an > identity for the socket was explicitly included in the packet, that > association function would operate independent of the IP addresses > present... Just as IP routing operates independent of the MAC > addresses attached to the packet. > Oh, here, we're misunderstanding each other. Sure, the session ID should be somewhere deep in the data part of the packet. But what I meant to say was that this session ID need not be visible at the network layer who's function is routing. All network layer needs, or should work on, is the network address (or in my term node address.) -- Regards, DY http://cnu.kr/~dykim
_______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
