See also: https://marc.info/?l=ietf&m=154416657729620&w=2
An example of using IANA registries:
https://tools.ietf.org/html/draft-ietf-i2nsf-sdn-ipsec-flow-protection-05
eg:
typedef encryption-algorithm-type {
type uint32;
description
"The encryption algorithm is specified with a 32-bit
number extracted from IANA Registry. The acceptable
values MUST follow the requirement levels for
encryption algorithms for ESP and IKEv2.";
reference
"IANA Registry- Transform Type 1 - Encryption
Algorithm Transform IDs. RFC 8221 - Cryptographic
Algorithm Implementation Requirements and Usage
Guidance for Encapsulating Security Payload (ESP)
and Authentication Header (AH) and RFC 8247 -
Algorithm Implementation Requirements and Usage
Guidance for the Internet Key Exchange Protocol
Version 2 (IKEv2).";
}
This prevents an incomplete enumeration and prevents obsolete/deprecated
items to be specified in yang RFCs. Since we have quite a number of dead
RRtypes, it is really important to not to create new RFCs that enumerate
things like MD, MF, A6, etc etc
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
