draft-ietf-dnsext-2929bis-07

[Alfred Hönes <[e-mail]>]

[ Moderators note: Post was moderated, either because it was posted by
   a non-subscriber, or because it was over 20K.  
   With the massive amount of spam, it is easy to miss and therefore 
   delete relevant posts by non-subscribers. 
   Please fix your subscription addresses. ]

Hello all,
eventually I found the time to also (and once more) closely study
the latest version of the DNS IANA Considerations draft,
     draft-ietf-dnsext-2929bis-07.

I apologize for being very late, but ...

Beyond a few nits [[ see section (B) below ]] that should be
addressed before publication as an RFC, I arrived at considerations
[[ see (A) below ]] that might motivate a small change in the RCODE
assignments.


(A)  Section 2.3 -- RCODE

The current draft "reserves" RCODE 65,535 (0xFFFF) for future
IETF Standards Action -- see below.

Also, in the first paragraph of Section 2.3, the draft says:

   It would appear from the DNS header above that only four bits of
   RCODE, or response/error code are available. However, RCODEs can
   appear not only at the top level of a DNS response but also inside
|  OPT RRs [RFC2671], TSIG RRs [RFC2845], and TKEY RRs [RFC2930]. The
|  OPT RR provides an eight-bit extension resulting in a 12-bit RCODE
|  field and the TSIG and TKEY RRs have a 16-bit RCODE field.

This means that the extensibility envisioned by reserving
RCODE 0xFFFF will not work for the restricted 12-bit RCODE
sub-namespace in the OPT RR.

Perhaps, it would be a good idea to also reserve one RCODE code
point in this 12-bit sub-namespace for future extensibility within
the framework of the EDNS0 OPT RR.

The draft tabulates in Section 2.3 :

        RCODE   Name    Description                        Reference
        Decimal
          Hexadecimal

        ...

|       23 - 3,840
|         0x0017 - 0x0F00   Available for assignment

        3,841 - 4,095
          0x0F01 - 0x0FFF   Private Use

        4,096 - 65,534
          0x1000 - 0xFFFE   Available for assignment

!       65,535
!         0xFFFF            Reserved, can only be allocated by an IETF
!                           Standards Action.


The code point 0x0FFF would be the natural analogon in the 12-bit
sub-namespace to the role of 0xFFFF in the 16-bit namespace.
But since the above assignment of 0x0FFF for Private Use is
inherited from RFC 2929 and should not be changed without very
significant reasons, the natural choice will perhaps be 0x0F00.

Therefore, to keep a reserved path for extensibility within the
12-bit RCODE sub-namespace for the OPT RR, I suggest to reserve
0x0F00 for future IETF Standards Action.

To this end, the above snippit of the table in Section 2.3 of the
draft needs to be changed to:

        ...

|       23 - 3,839
                ^^    vvv
|         0x0017 - 0x0EFF   Available for assignment
|
|       3,840
|         0x0F00            Reserved, can only be allocated by an IETF
|                           Standards Action.

        3,841 - 4,095
          0x0F01 - 0x0FFF   Private Use

        ...


(B)  Further nits

(1)  Section 2, 1st paragraph below the diagram:

The draft says:

   The ID field identifies the query and is echoed in the response so
|  they can be matched.
   ^^^^
I suggest to   s/they/it/  :

   The ID field identifies the query and is echoed in the response so
|  it can be matched.
   ^^

(2)  Section 2.2

The columnar alignment within the table in 2.2 should be improved,
to make it more pleasant and readable, by shifting most of the
References to the right by 8 character positions :

|         OpCode Name                      Reference

|          0     Query                     [RFC1035]
           1     IQuery  (Inverse Query, Obsolete) [RFC3425]
|          2     Status                    [RFC1035]
           3     available for assignment
|          4     Notify                    [RFC1996]
|          5     Update                    [RFC2136]
          6-15   available for assignment

---                                        ^^^^^^^^

|         OpCode Name                              Reference

|          0     Query                             [RFC1035]
           1     IQuery  (Inverse Query, Obsolete) [RFC3425]
|          2     Status                            [RFC1035]
           3     available for assignment
|          4     Notify                            [RFC1996]
|          5     Update                            [RFC2136]
          6-15   available for assignment


Kind regards,
  Alfred Hönes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: [phone], Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  [e-mail]                     |
+------------------------+--------------------------------------------+


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