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

[Dick Franks <[e-mail]>]

Scott & Steve,


[2, para 4]

   ALG-CODE is the list of assigned values of DNSSEC zone signing
   algorithms, DS hash algorithms, or NSEC3 hash algorithms (depending
   on the OPTION-CODE in use) that the client declares to be supported.
   The order of the code values can be arbitrary and SHOULD NOT be used
   to infer preference.

WG seems to agree that there is no information to be gleaned from the
order in which codes appear in the list. The requirement can therefore
be strengthened from SHOULD to MUST.

The present wording implies that the order will remain the same from
one occasion to another, i.e. sorted using some (arbitrary) ordering
relation.  There is no requirement that it should.

Suggest:
   ...
   The list of algorithm codes is unordered and MUST NOT be used
   to infer preference.


[3, para 1]

   A validating end-system resolver sets the DAU, DHU and/or N3U option,
   or combination thereof in the OPT meta-RR when sending a query.  The
   validating end-system resolver sets the value(s) in any arbitrary
   order.  The validating end-system resolver MUST also set the
   DNSSEC-OK bit [RFC4035] to indicate that it wishes to receive DNSSEC
   RRs in the response.

Second sentence is redundant, covered by section 2.


[3.1.2]

 The DAU, DHU and N3U EDNS options are NOT RECOMMENDED for non-
   validating stub resolvers.

As non-validating stub implements no algorithms at all, why does this
say "are NOT RECOMMENDED" instead of "MUST NOT be used"?


Dick


On 14 August 2012 18:29, Scott Rose <[e-mail]> wrote:
> New version that addresses the comments received from the -07 version.
>