> On Dec 1, 2014, at 4:31 PM, Wes Hardaker <wjh...@hardakers.net> wrote:
> 
> 神明達哉 <jin...@wide.ad.jp> writes:
> 
>> From a quick check some of them still seem to be open.  And, as far as
>> I remember there has been no response to my comments, so I'm not sure
>> if they were considered/discussed but dismissed or simply overlooked.
> 
> First, apologies again for missing these comments during last call.
> Multiple people missed it for some reason.
> 
> Here's a summary of your comments and what I've done to address them.
> My comments/actions are prefixed by "WJH:"
> 
> 
> 
> * DONE Section 1 (introduction), the first paragraph:
> 
>    This document specifies how a child zone in the DNS ([RFC1034],
>    [RFC1035]) 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.
> 
>  I vaguely remember someone already pointed this out, but anyway: I'm
>  afraid the term "parental agent" is not so widely shared that we can
>  safely use it without first giving the definition.  One easy way to
>  address this would be to add a forward reference to Section 1.1 at
>  the first occurrence of the term.  If possible, it would be even
>  nicer if we can avoid using this term until the definition is given
>  in Section 1.1.  For the same reason, it would be safer to avoid
>  using it in the abstract.
> 
>  WJH: I've put in a forward reference in the introduction.  I'm
>  not worried about the abstract as much, as any serious reader
>  will likely read on anyway.  And the point of the term was to
>  make sure we don't say something confusing like "parent" when
>  there is more than one.  There is no standard term, and the best
>  that the WG came up with (thanks to Olafur) is the new term.
>  But a forward reference in the introduction definitely makes
>  sense.
> 
See RFC7344 as definition of Parental Agent


>      This document specifies how a child zone in the DNS ([RFC1034],
>  -   [RFC1035]) can publish a record to indicate to a parental agent that
>  -   it can copy and process certain records from the child zone.  The
>  -   existence of the record and any change in its value can be monitored
>  -   by a parental agent and acted on depending on local policy.
>  +   [RFC1035]) can publish a record to indicate to a parental agent (see
>  +   section Section 2 for a definition of "parental agent") that it can
>  +   copy and process certain records from the child zone.  The existence
>  +   of the record and any change in its value can be monitored by a
>  +   parental agent and acted on depending on local policy.
> 

Olafur


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to