> On 30 Jul 2018, at 10:23 am, Evan Hunt <[email protected]> wrote:
>
> On Sun, Jul 29, 2018 at 05:42:04PM -0400, Joe Abley wrote:
>> I also agree with Tim's observation the other day that if this is just a
>> new RRType, then expert review is all that is procedurally required and
>> it'd be a generous extension of what is required to document the
>> implementation and use of the new RRType in the RFC series.
>
> A good point. Technically, I don't think there's anything in ZONEMD that
> couldn't be implemented with TXT; using a dedicated rrtype for the purpose
> is mere convenience.
Actually it needs to be a type code. How do you hash the TXT RRset and
RRSIG(TXT) RRset when you need to modify both of them after computing the
hash? You need to be able to cleanly exclude the records from the ZONEMD /
XHASH calculations but have a indication that it is present in the zone
(NSEC/NSEC3 bit map).
> --
> Evan Hunt -- [email protected]
> Internet Systems Consortium, Inc.
>
> _______________________________________________
> DNSOP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsop
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [email protected]
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
