On Wed, 2019-07-24 at 10:18 +0100, William Lupton wrote: > I think that "or" is slightly better here: > > "...does not support wildcards (see RFC 4592) or classless in-addr.arpa > delegations (see RFC 2317)"
I agree, thanks. Lada > > On Wed, 24 Jul 2019 at 08:01, Juergen Schoenwaelder < > [email protected]> wrote: > > On Mon, Jul 22, 2019 at 06:41:42PM -0400, Ladislav Lhotka wrote: > > > > > > But these two unsupported cases only make sense in the context of DNS zone > > data. > > > I would suggest instead > > > > > > NEW: > > > > > > "The domain-name type represents a DNS domain name. The > > > name SHOULD be fully qualified whenever possible. > > > This type is not intended for modeling DNS zone data, as > > > it does not support wildcards [RFC 4592] and classless > > > in-addr.arpa delegations [RFC 2317]." > > > > > > > Yes, this is better. I will put the following in the next revision: > > > > "The domain-name type represents a DNS domain name. The > > name SHOULD be fully qualified whenever possible. This > > type does not support wildcards (see RFC 4592) and > > classless in-addr.arpa delegations (see RFC 2317). > > > > And I will remove the sentence you wanted to remove since the above > > more clearly explains when to use / not to use this type. > > > > /js > > -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
