Using an Exclusive OR function on the two StarGate values means that the bit difference is carried across the IPv4 transport. Either end knows itself and can derive the other side by doing another Exclusive OR. This is similar to using Exclusive OR values in linked lists where only one address is stored. When one knows the location of the node, and a node where they came from, they can compute where they are going.
http://www.dot-biz.com/RepliGate/ Jim Fleming http://www.RepliGate.net ----- Original Message ----- From: "Jim Bound" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, January 12, 2002 10:22 PM Subject: Re: Update: Proposed update to RFC 2460 [was Re: Flow Label] > I agree. The triplet is necessary and will avoid state deadlocks for > sure. This is what I thought I agreed to at SLC as you suggest. I support > your change. > > regards, > > > /jim > > > -------------------------------------------------------------------- > IETF IPng Working Group Mailing List > IPng Home Page: http://playground.sun.com/ipng > FTP archive: ftp://playground.sun.com/pub/ipng > Direct all administrative requests to [EMAIL PROTECTED] > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
