In general I think this is good stuff, but I do not think the document can be
published yet. What I ask for I hope should be easy to fix though.
1. I see, specifically at the end, some confusion (I think) between use of
"parent" and "parental agent". I.e. I think the term "parent" is in use for
example when discussing out-of-balliwick NS records.
2. It is not described in detail enough how the actual queries should be sent,
and allowing the parental agent to do just however they want seems kind of
crazy. Either this is built upon the fact a direct query to a server is sent
(i.e. not only must the response be signed and validated, but also AA flag must
be set on the response) or not. If not, I want some discussion about caching
implications.
3. Regarding caching, I specifically want a scenario described when a zone is
moving from one DNS provider (one child) to another, and the loosing DNS
provider is not cooperating.
4. A step by step example of how a child is changing NS records
5. A step by step example of how a child is changing glue
6. A step by step example of how out-of-balliwick NS records are thought to be
treated (just saying they are problematic is not enough for me)
I.e. a lot of what I ask for is to clarify with examples a lot of the text
around 4.3. Having such text, together with a SHOULD and not MUST, will
definitely not lead to interoperability.
Patrik
On 8 aug 2014, at 17:16, The IESG <iesg-secretary(_at_)ietf(_dot_)org> wrote:
The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document:
- 'Child To Parent Synchronization in DNS'
<draft-ietf-dnsop-child-syncronization-02.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2014-08-22. Exceptionally, comments
may be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
This document specifies how a child zone in the DNS can publish a
record to indicate to a parental agent that it may copy and process
certain records from the child zone. The existence of and value
change of the record may be monitored by a parental agent and acted
on as appropriate.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dnsop-child-syncronization/ballot/
No IPR declarations have been submitted directly on this I-D.
signature.asc
Description: Message signed with OpenPGP using GPGMail