I am sorry, I referred a wrong RFC Number. It was the draft on IPv6 Scoped
Architecture.
Regards
Narsi
>>> "Narsimharao Nagampalli" <[EMAIL PROTECTED]> 07/18/00 05:21PM >>>
Hi,
In the RFC (2710) on the scoped address architecture, we seem to consider scenarios
where source address can be smaller scope than the destination address. I have two
concerns regarding the same and also would be interested to know of scenarios where
such a feature is useful.
Fragmentation
One concern is regarding IPv6 fragmentation. There we use the source address followed
by a unique ID generated at the source to define a fragmentation sequence. Now,
consider the case where two link local addressed sources are sending fragments to a
site-local address and happen to use the same ID's. I can not see a way in which the
destination can re-assemble these two train of fragments properly.
Flow Label
Same issue like fragment ID. Flow label ID and Src address again are used together to
identify a flow. In the above scenario again, there could be issues in distinguishing
across flows.
Any comments/Insights?
Thanks and Regards
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]
--------------------------------------------------------------------
