Yes, you need to do this in order to support link-local (and also
site-local) addresses properly. To be more general, it is best to tag
incoming packets with appropriate scope id values based upon their arrival
interface and address scopes. And then add those to the connection lookup
criteria. This is what we do in our implementation.
--Brian
> -----Original Message-----
> From: Narsimharao Nagampalli [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 17 July, 2000 04:36
> To: [EMAIL PROTECTED]
> Subject: TCP Connection Identifiers in IPv6
>
>
> Hi,
>
> In IPv4 a TCP connection was uniquely distinguished with the
> help of the 4 tuple. Does this hold good with IPv6? I can
> think of the following scenario caused by scoping, where such
> a identification might fail.
>
> In IPv6 scenario, if a node with multiple links having same
> link local addresses on both the interfaces exists, then it
> is possible that the 4 tuple is no longer sufficient to
> determine a connection uniquely. There has to be an interface
> identifier added as the 5th element to now distinguish across
> connections.
>
> Any comments/suggestions?
>
> Thanks,
> Narsi
>
> --------------------------------------------------------------------
> 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]
--------------------------------------------------------------------
