Existing signers and validators won't know the internal format of future rr
types.
On December 8, 2015 10:09:06 AM EST, Paul Wouters <[email protected]> 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")
>b) What should be done with new RRtypes like OPENPGPKEY or SMIMA?
>c) Why the hell - hardcoded lists and not IANA registry?
>d) Does this need updating or an errata?
>
>Paul
>
>_______________________________________________
>DNSOP mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/dnsop
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
