On Tue, 29 Jan 2019, Tero Kivinen wrote:
Requirement for what? I don't think the IANA reader will know these
are vendor build support requirements, and not default case runtime
requirements ?
Iana registry is only for vendors, normal users should ever need to
check them ever.
Fair enough.
Sure. Write draft-ietf-ipsecme-ikev2-des-md5-die-die-die and we can
use that RFC number for them.
Or we can change the reference column for those to point to
RFC8221/RFC8247 for those where they say it is MUST NOT.
That is something that is easy to do with just sending request to
iana.
Either works, that was what we were trying to do :)
Earlier I understood that you wanted to add some new column there
which would add new information that is copied from RFC8221/8247.
No, just having the registry confirm which things you should not
implement is what I was looking for. Although there is one important
difference with 8221/8246, which is what to do with MAY algorithms
that we found no strong reason for to MUST NOT, but which should really
be retired too. Like CAST for example. But I guess formally, a bis
document should move those MAY's to MUST NOT.
Paul
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec
