Hi Chris,

I think the general view was that RH0, can be deprecated and a new
more secure Routing Header can be used to get the functionality for
required.

I have put a draft for the checks required, in any such header. I
intend to modify the draft to take care of introducing the new Routing
Header. It would be great to hear of use cases from the operators
where the functionality is required.

Thanks,
Vishwas

On 7/5/07, Christopher Morrow <[EMAIL PROTECTED]> wrote:
On 7/2/07, Rémi Denis-Courmont <[EMAIL PROTECTED]> wrote:
> Le jeudi 28 juin 2007, ext Bob Hinden a écrit :
> > This starts a two week IPv6 working group last call on advancing
> >
> >       Title           : Deprecation of Type 0 Routing Headers in IPv6
> >       Author(s)       : J. Abley, et al.
> >       Filename        : draft-ietf-ipv6-deprecate-rh0-01.txt
> >       Pages           : 9
> >       Date            : 2007-6-28
> >
> > to Proposed Standard.  Please send substantive comments to the IPv6
> > mailing list. Editorial comments can be sent to the authors.
>
> Document is fine with me. But what are the consequences with regards to
> RFC3542? Should implementations stop parsing RH0 at that level as well?

I fear that deprecating a part of the spec is going to lead to some
confusion (as is shown above) and probably isn't the only option... I
had wanted to send some longer feedback to jabley/ipv6@ but missed out
it seems :(

In short, I think that deprecation removes some functionality that
people may want  to use (perhaps even for a good reason). There are
other issues with removing this from the spec, like making another set
of corner cases implementors will have to check for, ala cisco's
'protocols' bug of 2 years ago (just picking an example not picking on
a vendor). Giving the network the option to ignore RH0 headers would
have skipped us past this problem, and left the spec in good standing
for the cases that might want to use it for good.

-Chris


--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to