Hi Tom:
Rafa
Another separate thought. The references you have for algorithms are to both IANA and RFC. It seems to me that the IANA pages will be more up-to-date and can be updated by Expert Review which may take place before there is an RFC available while the RFC provide more detail that a user might want. I am uncertain which is best so I raised this on the ipsecme WG list, which is responsible for IKEv2 maintenance, and I got the following. The question is mine, the response from Tero Kivinen.
============================================================
> So, question. What references should draft i2nsf-sdn point readers to
> for up-to-date information on algorithms (assuming that they do not
> track the IETF WG that updates information on IKEv2 ie like me)?
It should use IANA registry for the mapping between numbers,
algorithms and references; and then for algoritm implementation
requirements and usage guidance it should point to RFC8247 for IKEv2,
and to RFC8221 for ESP.
> Currently that is both a reference to the IANA registry and to an RFC;
> is that your best advice?
Yes.
=============================================================
Yes, we are following this conversation as well.
So do as you are currently doing and I shall stop thinking about it.
Thank you very much for all your effort with this.
Best Regards. Tom Petch On 28/10/2020 10:42, Rafa Marin-Lopez wrote: Hi Tom:
<snip> _______________________________________________ I2nsf mailing list I2nsf@xxxxxxxxhttps://www.ietf.org/mailman/listinfo/i2nsf
------------------------------------------------------- Rafa Marin-Lopez, PhD Dept. Information and Communications Engineering (DIIC) Faculty of Computer Science-University of Murcia 30100 Murcia - Spain Telf: +34868888501 Fax: +34868884151 e-mail: rafa@xxxxx-------------------------------------------------------
|
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
