Re: version -01 of draft-ietf-dnsext-dns-protocol-profile sent

[Stephane Bortzmeyer <bortzmeyer@nic.fr>]

On Sun, Jan 20, 2008 at 05:14:18PM +1000,
 George Michaelson <ggm@apnic.net> wrote 
 a message of 94 lines which said:

> I have just submitted a 01 revision of
> draft-ietf-dnsext-dns-protocol- profile,

Remarks on the content:

>   {non normative} The zone file format as specified in [RFC 1035
>   (5.1)] is optional.  It is used as a common presentation format
>   only.

I suggest:

The zone file format as partially specified in [RFC 1035 (5.1)] is
optional.  It is used as a common presentation format only.

Rationale:
http://www.psg.com/lists/namedroppers/namedroppers.2006/msg01025.html

> If delegations are present and glue information is required [...]
> [RFC 2181 (Section 5.2 para 2)]

"Required" is not well defined (think of loops between two TLD, for
instance, as in
http://www.ops.ietf.org/lists/namedroppers/namedroppers.199x/msg03693.html). (And
the reference to RFC 2181 is not clear for me, it does not talk about
glues at this place.)

>      *  OPCODE 1 (IQUERY) MUST result in RCODE=4 NOTIMPL [RFC 3425].
>         {has this actually been deprecated?}

It seems so. The RFC 3425 says "Therefore IQUERY is now obsolete, and
name servers SHOULD return a "Not Implemented" error when an IQUERY
request is received." Is is acceptable to change the SHOULD in a MUST?
The RFC is five years old so anyone should have upgraded since :-)

>      *  QDCOUNT!=1 SHOULD result in RCODE=1 FORMERR

A reference to
http://www3.tools.ietf.org/html/draft-ietf-dnsext-edns1 ;? 



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>