Re: [DNSOP] Question on RRtypes in RFC 4034 Section 6.2

[Ólafur Guðmundsson <[e-mail]>]

The reasoning is in https://tools.ietf.org/html/rfc3597

On Tue, Dec 8, 2015 at 10:09 AM, Paul Wouters <[e-mail]> wrote:

>
> Hi,
>
> Section 6.2 of 4034 talks about canonicalization of the RR Form
>
> Item 3 states:
>
> 3.  if the type of the RR is NS, MD, MF, CNAME, SOA, MB, MG, MR, PTR,
>        HINFO, MINFO, MX, HINFO, RP, AFSDB, RT, SIG, PX, NXT, NAPTR, KX,
>        SRV, DNAME, A6, RRSIG, or NSEC, all uppercase US-ASCII letters in
>        the DNS names contained within the RDATA are replaced by the
>        corresponding lowercase US-ASCII letters;
>
> My questions:
>
> a) What was the purpose of listening these and not all RRtypes?
>    (It seems perhaps it wanted to say "All except A/AAAA")
>
All these types contain "domain names" as a field, and name compression is
allowed in the RDATA.
After the publication of RFC3597 no name compression is allowed in new
types.

b) What should be done with new RRtypes like OPENPGPKEY or SMIMA?
> c) Why the hell - hardcoded lists and not IANA registry?
>

Finite list as 3597 outlawed name-compression in new types


> d) Does this need updating or an errata?
>
HINFO and TXT is a mistake and there is errata on that
https://www.rfc-editor.org/errata_search.php?rfc=3597

Olafur