> On 31 Oct 2020, at 15:12, tom petch wrote:
>
> On 30/10/2020 22:42, Tero Kivinen wrote:
>> Roman Danyliw writes:
>> It seems to me that the IANA entries for IKEv2 are incomplete.
>> RFC8247 does a fine job of specifying algorithms and adding
>> information such as status (MUST/SHO
Hi Tom,
we discussed with the chairs the usefulness of adding "Recommended/Not
recommended" column
(as TLS WG did) into the IKEv2 algorithm registries back in 2018 in Bangkok
and I was one who
of those who initially suggested this. However, Tero made a very good point
that
IANA doesn't have any
On 30/10/2020 22:42, Tero Kivinen wrote:
Roman Danyliw writes:
It seems to me that the IANA entries for IKEv2 are incomplete.
RFC8247 does a fine job of specifying algorithms and adding
information such as status (MUST/SHOULD+), IoT, AEAD and so on,
information which is not present on IANA. The
