Hi Dave,
The text for processing an unknown Routing Header is attached from
RFC2460. It is another matter that a new header may not be able to
traverse the Firewall and such packets may be dropped.
If, while processing a received packet, a node encounters a Routing
header with an unrecognized Routing Type value, the required behavior
of the node depends on the value of the Segments Left field, as
follows:
If Segments Left is zero, the node must ignore the Routing header
and proceed to process the next header in the packet, whose type
is identified by the Next Header field in the Routing header.
If Segments Left is non-zero, the node must discard the packet and
send an ICMP Parameter Problem, Code 0, message to the packet's
Source Address, pointing to the unrecognized Routing Type.
If, after processing a Routing header of a received packet, an
intermediate node determines that the packet is to be forwarded onto
a link whose link MTU is less than the size of the packet, the node
must discard the packet and send an ICMP Packet Too Big message to
the packet's Source Address.
Thanks,
Vishwas
On 8/30/07, David Conrad <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Aug 29, 2007, at 1:04 PM, Brian E Carpenter wrote:
> > On 2007-08-30 02:08, Thomas Narten wrote:
> >> Can we please _first_ identify a user/customer for a proposed RH,
> > I agree. A use case draft should be the first step.
>
> I'm not sure it matters since:
>
> > Incidentally, RFC 2460 is clear that unknown headers should cause the
> > packet to be dropped, so the transition strategy is tricky in any
> > case.
>
> Water under the bridge and all that, but I'm curious: what was the
> rationale for this? It would seem to imply it is impossible to do
> incremental deployment of new headers, and thus essentially freezes
> routing header development for the lifetime of IPv6.
>
> Am I misunderstanding?
>
> Thanks,
> -drc
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
