On Wed, Oct 24, 2018 at 5:49 AM Wessels, Duane <dwess...@verisign.com> wrote:
> > > On Oct 22, 2018, at 6:53 PM, Bob Harold <rharo...@umich.edu> wrote: > > > > Just my opinions: > > > > Keep the Reserved field > > > > Include occluded data - it is part of the zone, even if never served. > (Similar to glue data when a server has both a parent and child zone.) > > > > If you might have multiple zonemd records not at the apex later, why not > allow them now? Otherwise, your choice whether to restrict them. (Someone > will find a use for them, like verifying glue records. Everyone else can > ignore them.) > > > > Thanks for the feedback, Bob. > > My thought about non-apex ZONEMD records is that ZONEMD has some > similarities to SOA. They both say something about the zone has a whole, > and I know some software at least rejects zones with a non-apex SOA > record. OTOH, I don't want to make things unnecessarily complex... > > DW Having since read more discussions on whether to keep the Reserved field, I would say that if the Reserved field is removed, then we should only allow one ZONEMD record, and it should be at the apex. If we keep the Reserved field, then let's allow ZONEMD records in other places for future use. -- Bob Harold
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
