Alfred Hönes | 25 Apr 2012 18:58
Picon

an editorial review of draft-ietf-dnsop-respsize-13

It has been pointed out that the DNS Referral Response Size Issues
I-D should not be left going to final expiry, and I have performed
a new review of the last version, draft-ietf-dnsop-respsize-13.

I only found a small number of remaining editorial nits -- either
formerly overlooked or newly introduced.  You might want to take
the opportunity of the notes below to refresh the draft.

(1)  Section 1

(1.1)  1st paragraph

a) The object of the first sentence lacks an article; "the" should be
   supplied.

b) In a few places, the draft uses very terse forms of precise
   citations, which better should be expanded a bit for readability;
   the first occurrence of this is here as well:
   "(see [RFC1035] 4.2.1)"            should say
   "(see [RFC1035], Section 4.2.1)"   or even better
   "(see Section 4.2.1 of [RFC1035])" .

Chosing the latter form, the corrections will accumulate to:

|  The original DNS standard limited UDP message size to 512 octets (see
|  [RFC1035] 4.2.1).  Even though this limitation was due to the
   required minimum IP reassembly limit for IPv4, it became a hard DNS
   protocol limit and is not implicitly relaxed by changes in a network
   layer protocol, for example to IPv6.
---                                 vvvvv
(Continue reading)

paul vixie | 25 Apr 2012 19:13
Favicon

Re: an editorial review of draft-ietf-dnsop-respsize-13

On 4/25/2012 4:58 PM, Alfred � wrote:
> It has been pointed out that the DNS Referral Response Size Issues
> I-D should not be left going to final expiry, and I have performed
> a new review of the last version, draft-ietf-dnsop-respsize-13.
>
> I only found a small number of remaining editorial nits -- either
> formerly overlooked or newly introduced.  You might want to take
> the opportunity of the notes below to refresh the draft.

thanks.

see below.

> (1)  Section 1
>
> (1.1)  1st paragraph
>
> a) The object of the first sentence lacks an article; "the" should be
>    supplied.

ok.

> b) In a few places, the draft uses very terse forms of precise
>    citations, which better should be expanded a bit for readability;
>    the first occurrence of this is here as well:
>    "(see [RFC1035] 4.2.1)"            should say
>    "(see [RFC1035], Section 4.2.1)"   or even better
>    "(see Section 4.2.1 of [RFC1035])" .

i don't agree. we'll make the change, since we're not going to stand on
(Continue reading)

Alfred Hönes | 25 Apr 2012 20:07
Picon

Re: an editorial review of draft-ietf-dnsop-respsize-13

Paul,
thanks for your expedite response to my review comments.

Please see a few inline follow-up remarks below.
I have deleted all parts that don't need further elaboration.

>> (1)  Section 1
>>
>> (1.1)  1st paragraph
>>
>> [...]
>
>> b) In a few places, the draft uses very terse forms of precise
>>    citations, which better should be expanded a bit for readability;
>>    the first occurrence of this is here as well:
>>    "(see [RFC1035] 4.2.1)"            should say
>>    "(see [RFC1035], Section 4.2.1)"   or even better
>>    "(see Section 4.2.1 of [RFC1035])" .
>
> i don't agree. we'll make the change, since we're not going to stand on
> minutiae, but for the record this is your personal style preference not
> an objective style guide reference. i would actually prefer [RFC1035
> 4.2.1] since terseness is to me virtuous. again: you're over reaching
> here, but, we'll make the change for you anyway.

I have observed various instances of the RFC Editor changing
"RFC xxxx, Section yy" to "Section yy of RFC xxxx", and
accommodating the preferred style helps to minimize changes of
a document at the RFC Editor and thereby to speed up RFC Editor
processing of a draft (and less changes for the authors to review
(Continue reading)


Gmane