Hi Anjanish,
There is no contradiction. The intermediate nodes which are to be traversed
will be listed as the destination address in the IPv6 datagram in the repsective
segments and hence they can process the Routing header.
Say H1 wants to talk to H2 using the route H1->R1->R2->R3->H2. In the segment between
H1 and R1 the IPv6 source address will be H1 and the IPv6 dest address will be R1 (and
not H2) the segments left would be 3 and the addresses in the type 0 routing header
will be R2,R3 and H2. As this datagram is addressed to R1 it will examine the Routing
Header. The same procedure is followed between R1 and R2 and so on until the segments
left becomes 0.
Regards
Suresh
-----Original Message-----
From: Anjanish P [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 7:27 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Routing Header in IPv6
Hi All,
One statment in RFC 2460 Looks contradictory, to the behaviour of Routing
Header processing.
One Page 05. Sections 4. The below para says :
---------------------------------------------
"With one exception, extension headers are not examined or processed
by any node along a packet's delivery path, until the packet reaches
the node (or each of the set of nodes, in the case of multicast)
identified in the Destination Address field of the IPv6 header."
Followed by para as below:
" The exception referred to in the preceding paragraph is the Hop-by-
Hop Options header, which carries information that must be examined
and processed by every node along a packet's delivery path, including
the source and destination nodes. "
------------------------------------------------
Section 4.4 of the RFC specifies that Routing header, need to be processed
by the intermediate nodes.
Since, section 4.4 is correct, how can statement of section of 4.0 be
correct ???
Please clarify.
Thanks in advance for your response.
Regards,
Anjanish
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
