While it would be useful to update 3542, I don't think it is necessary. It is out-of-date given that it says the Type 0 routing header is the only one defined (it isn't). However, I don't see the benefit of revising that spec *just* for this.
Perhaps we should simply add a statement to the errata page for 3542 pointing to the deprecation document. Regards, Brian Vlad Yasevich wrote: > As part of the deprecation effort, does it also make sense to > update RFC 3542 (Advanced API) to remove the references to Type 0 > routing header? > > Thanks > -vlad > > -------------------------------------------------------------------- > 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 --------------------------------------------------------------------
