Hi Matthijs, On Wed, Mar 28, 2018 at 03:31:57PM +0200, Matthijs Mekking wrote: > All, > > It's been a while, but I have put up a new version of the MIXFR draft: > > https://tools.ietf.org/html/draft-mekking-mixfr-02 > > The IETF 101 Hackathon lead to the revival of this draft. > > Changes after the three year sleep: > > - I removed the IXFR Gone Wild section. This document should focus in > the in-band transfer improvements. I know there are others who like to > see and work on a new DNS transfer protocol, but one does not exclude > the other. > - Intended status: Standards track. > - Added a clarification from Bob Harold about class ANY (from 2015). > - Remove ambiguous "Delete All RRsets of a Type". > - Affiliation changes. >
Thanks for bringing this back. I like the simplification with the removal of the wild section. One comment, [3.1] As section 3 states that MIXFR is DNSSEC aware we need text regarding NSEC3PARAM update as well. For that I suggest to change 3.1 section name and include an extra paragraph. 3.1 Implicit DNSSEC deletions When an NSEC3PARAM is modified, the MIXFR client MUST also remove all existing NSEC3 records on the zone. One clarification question, At 3.6, last paragraph, what is the practical case that a updated record has an RDLENGTH of zero bytes? > Who would like to contribute, review, and all that great fun? > > Github is here: https://github.com/matje/mixfr > > Best regards, > Matthijs Fred _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
