Re: [dnsext] Fwd: I-D Action: draft-ietf-dnsext-dnssec-algo-signal-02.txt

On Jul 6, 2011, at 10:00 AM, Scott Rose wrote:

> An updated version of the algo-signal draft to address the issues in WGLC.  Specific changes:
> 
> 1.  Changed the wording in 3.4.1 to remove the RFC2119 wording on setting the DO bit.  
> 
> 2. Changed section 4 wording to indicate DNS proxy systems and added a ref to RFC 5625.
> 
> 3. fixed some typos and minor wording changes to stress that the DAU option is for signaling only and does not specify any change to how servers construct a response.
> 
> Scott

Oooh, I like this version....

Some simple nits:

Section1: Introduction:

O: "for use with DNSSEC (see . "
C: Somethings missing here :-P

O: "by which a client query can signal a set of algorithms it implements."
P: "by which a client query can signal a set of algorithms which it implements.
C: or "that" or something ?

Section 2
O: "for the DNSSEC Algorithm Understood (DAU)"
P: for the DNSSEC Algorithms Understood (DAU)"
C: Plural?

O: "DNSSEC algorithm codes are 1 octet long so this value is the number of octets."
P: ""
C: Is this sentence needed? I don't have proposed text, but I found it broke the flow of the text...

Section 3.1:
O: "So optimal setting of the DAU"
P: "Optimal setting of the DAU"

Section 3.2:
O: "This way thee validating stub resolver"
P: "This way the validating stub resolver"
C: 'thee" is *so* last century...

Section 3.4.1:
O: "A validating recursive resolver sets..."
C: It *might* be interesting to somewhere also include a flag saying if the DAU was included because the client did so, or if the recursive did so because of local policy... 

Section 6:
O: "Zone administrators that are planning"
P: "Zone administrators who are planning"
C: Just sounds better (IMO).

W

> 
> Begin forwarded message:
> 
>> From: internet-drafts@ietf.org
>> Date: July 6, 2011 9:50:12 AM EDT
>> To: i-d-announce@ietf.org
>> Cc: dnsext@ietf.org
>> Subject: [dnsext] I-D Action: draft-ietf-dnsext-dnssec-algo-signal-02.txt
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the DNS Extensions Working Group of the IETF.
>> 
>> 	Title           : Signaling Cryptographic Algorithm Understanding in DNSSEC
>> 	Author(s)       : Steve Crocker
>>                         Scott Rose
>> 	Filename        : draft-ietf-dnsext-dnssec-algo-signal-02.txt
>> 	Pages           : 8
>> 	Date            : 2011-07-06
>> 
>>  The DNS Security Extensions (DNSSEC) were developed to provide origin
>>  authentication and integrity protection for DNS data by using digital
>>  signatures.  These digital signatures can be generated using
>>  different algorithms.  This draft sets out to specify a way for
>>  validating end-system resolvers to signal to a server which
>>  cryptographic algorithms they support.
>> 
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-dnsext-dnssec-algo-signal-02.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsext-dnssec-algo-signal-02.txt
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext
> 
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext
> 