Re: draft-ietf-ipv6-node-requirements-11.txt

They should be updated. By the way I noticed recently
that the RFC Editor does not necessarily do "obsoleted by"
updates to references automatically. This stuff needs to
be done by the authors in AUTH48. And in this particular
case we have even text changes, as you point out.

By the way, there are also substantive changes in the
new IPsec documents. For instance, AH support is no
longer a MUST. I think this should be reflected in the
node requirements document too, as that currently
says "AH [RFC-2402] MUST be supported.".

There's probably an impact in the algorithms and key
management sections, too...

--Jari

Dave Thaler wrote:

>The draft in the RFC-editors queue now references obsoleted (as of last
>month) RFCs. Specifically:
>  RFC2401 is now obsoleted by RFC4301
>  RFC2402 is now obsoleted by RFC4302
>  RFC2404 is now obsoleted by RFC4305
>  RFC2406 is now obsoleted by RFC4303, RFC4305
>  RFC2407,2408,2409 are now obsoleted by RFC4306
>
>Also two statements in section 8 are now obsolete as a result:
>  "RFC-2401 is being updated by the IPsec Working Group."
>  "RFC-2406 and RFC 2402 are being updated by the IPsec Working Group."
>
>Can these be updated?
>
>-Dave
>
>--------------------------------------------------------------------
>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
--------------------------------------------------------------------