John, Thanks for the review you are spot on, I should not edit while watching a soccer game :-(
I will post an updated version in the next few days. how about for section 4.1: I was trying to cover the case where the RRSET selected has Multiple RRSIG's not About 4.2. Implementation may choose this when it can, if it can not for a zone then fall back on 4.1 as for the guidance, I tried, but there are strong opinions out there and ..... Olafur On Thu, Feb 9, 2017 at 12:53 AM, Woodworth, John R < john.woodwo...@centurylink.com> wrote: > Olafur, > > This is my first draft review so apologies if it seems harsh, I > really like the concept of this draft. > > > Comments: > > -- > Section 4.1 "Select one RRSet mode" - > > The section including "...choose a small one(s) to..." seems > confusing, a single RRSet is expected why the possibility of > multiple RRsets? > > > -- > Section 4.2 "Synthesised HINFO RRset" - > > I do not follow the section including "...query includes DO=1...". > Should the implementation fall back to the one-RRSet-mode? If the > only RRSet returned is a synthesized HINFO one, what does the > returned RRSIG correspond to? > > > -- > General - > > I would personally like to see more direction for implementers > provided in the draft, e.g. expected configurable features. > I realize this is a matter of personal taste. > > > Thanks and good luck, > John > > -- THESE ARE THE DROIDS TO WHOM I REFER: > This communication is the property of CenturyLink and may contain > confidential or privileged information. Unauthorized use of this > communication is strictly prohibited and may be unlawful. If you have > received this communication in error, please immediately notify the sender > by reply e-mail and destroy all copies of the communication and any > attachments. >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
