See inline. On 4/8/22, 1:59 PM, "netmod on behalf of Randy Presuhn" <netmod-boun...@ietf.org on behalf of randy_pres...@alumni.stanford.edu> wrote:
Hi - On 2022-04-08 5:11 AM, Christian Hopps wrote: .. > Instead, Acee (I'm not sure I'd call him WG B :) is asserting that > *nobody* actually wanted the current type, and it has been misused > everywhere and all over. The vast majority of implementations in > operation probably can't even handle the actual type (Andy's point). So, > Acee is just the messenger of bad news here. Please note that the AD in > charge of all this agreed with Acee as well. That's not the impression one gets from modules like https://www.ietf.org/archive/id/draft-ietf-mpls-mldp-yang-10.txt which employs both types. So, regardless of whether one is willing to respect YANG's compatibility rules, it's no longer a matter of speculation whether a name change would cause actual damage - it clearly would. Furthermore, my recollection is that the WG *did* discuss whether the "zonable" property was needed, so any argument based on the assertion that "*nobody* actually wanted the current type" seems to me to based on a false premise. If you look at the existing YANG RFCs rather than drafts that are confirming to the error, you'll notice that they don't use the no-zone types: https://datatracker.ietf.org/doc/rfc8344/ https://datatracker.ietf.org/doc/rfc8349/ https://datatracker.ietf.org/doc/rfc8519/ https://datatracker.ietf.org/doc/rfc9067/ Also, if you look at the SNMP RFC 4001, you'll note that the base types do not include the zone index and RFC8344 references the MIB types using the base types (see snippet below). Clearly, it was wrong to make the IP addresses including the zone the default and I'm not sure why there is all this effort not to just admit, fix the RFC 6991 BIS version, and be done with it. InetAddressIPv4 ::= TEXTUAL-CONVENTION DISPLAY-HINT "1d.1d.1d.1d" STATUS current DESCRIPTION "Represents an IPv4 network address: Octets Contents Encoding 1-4 IPv4 address network-byte order The corresponding InetAddressType value is ipv4(1). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (4)) InetAddressIPv6 ::= TEXTUAL-CONVENTION DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x" STATUS current DESCRIPTION "Represents an IPv6 network address: Octets Contents Encoding 1-16 IPv6 address network-byte order The corresponding InetAddressType value is ipv6(2). This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (16)) InetAddressIPv4z ::= TEXTUAL-CONVENTION DISPLAY-HINT "1d.1d.1d.1d%4d" STATUS current DESCRIPTION "Represents a non-global IPv4 network address, together with its zone index: Octets Contents Encoding 1-4 IPv4 address network-byte order 5-8 zone index network-byte order The corresponding InetAddressType value is ipv4z(3). The zone index (bytes 5-8) is used to disambiguate identical address values on nodes that have interfaces attached to different zones of the same scope. The zone index may contain the special value 0, which refers to the default zone for each scope. This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (8)) InetAddressIPv6z ::= TEXTUAL-CONVENTION DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x%4d" STATUS current DESCRIPTION "Represents a non-global IPv6 network address, together with its zone index: Octets Contents Encoding 1-16 IPv6 address network-byte order 17-20 zone index network-byte order The corresponding InetAddressType value is ipv6z(4). The zone index (bytes 17-20) is used to disambiguate identical address values on nodes that have interfaces attached to different zones of the same scope. The zone index may contain the special value 0, which refers to the default zone for each scope. This textual convention SHOULD NOT be used directly in object definitions, as it restricts addresses to a specific format. However, if it is used, it MAY be used either on its own or in conjunction with InetAddressType, as a pair." SYNTAX OCTET STRING (SIZE (20)) Acee Randy _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod