Yes, changed in my sources. /js
On Wed, Jul 24, 2019 at 10:18:32AM +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)" > > On Wed, 24 Jul 2019 at 08:01, Juergen Schoenwaelder < > j.schoenwael...@jacobs-university.de> 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 > > > > -- > > Juergen Schoenwaelder Jacobs University Bremen gGmbH > > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > > Fax: +49 421 200 3103 <https://www.jacobs-university.de/> > > > > _______________________________________________ > > netmod mailing list > > netmod@ietf.org > > https://www.ietf.org/mailman/listinfo/netmod > > -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod