So this is "too late" and thus can be disregarded if desired, but here's some comments you may or may want to consider while still working on it:
- Overall, this is a well crafted document. Nice work! - intro: "not egation" is a type -- you probably have caught this by now - intro: suggest: s/questions arise/questions arise which this document addresses/ - intro: I think the document is doing more than "minimiz[ing] user surprise". It's preventing problems if the advice is followed too. - 2.2 but also in general: an example diagram and scenario might be helpful for the reader to better understand the somewhat complex timing of potential events. - 3.1, bullet 1: In general most of your bullets don't require reading the analysis -- this is an exception. Why not list the DS updates specifically here rather than (normatively) require reading the follow on section? - 3.1, bullet 2: s/first notified/notified first/ (slightly more normal phrasing) - 5.1, bullet 3: s/SHOULD be suspended,/SHOULD be suspended until a non-empty DS record set has been provisioned/ (they may get this from the next bullet, but it's better to be clear here (IMHO)) - 5.2.3: I wonder if there is a case (IE, I haven't plotted all the cases out on my whiteboard yet) where a resolver switches to an old DS because of a disconnected authoritative server causes it to, then the primary removes the old key and the resolver can no longer switch back to the properly administrated authoritative server? I'm not sure you can follow that, and I'm not yet sure it's a real problem :-/ Documenting my brain storming though... - 5.2.3, last sentence: I wouldn't say that only the parent view is within scope of the document. Certainly you're considering the child timing in this, and it's been crafted to minimize the impact as much as possible. So I'd say something like "and thus cannot be handled with only parent-side changes" rather saying "it's out of scope". Mostly a tone issue. -- Wes Hardaker Google _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
