Paul Wouters writes:
> > In the section 1 there is text saying:
> >
> > IKEv1 has been moved to Historic status.
> >
> > I think it is supposed to say "This document moves IKEv1 to Historic
> > status".
>
> We used the text because RFCs do not make documents Historic, it is IESG
> actions.
On Tue, 7 Jun 2022, Tero Kivinen wrote:
but the RFC8223 is completely unrelated to the matter in hand:
I assume it should be RFC8221 (i.e. replace the text in section 1 and
the reference).
Yes, fixed.
This document says it updates 7296, 8221, and 8247. I am not
completely sure what it is
In the introduction there is text:
Algorithm implementation requirements and usage guidelines for IKEv2
[RFC8247] and ESP/AH [RFC8223] gives guidance to implementors but
limits that guidance to avoid broken or weak algorithms.
but the RFC8223 is completely unrelated to the matter in
