Re: nsec++

[Miek Gieben <miekg@atoom.net>]

[On 27 Nov, @16:21, Jakob wrote in "nsec++ ..."]
> my initial version of the draft respecifying the rdata format for nsec has
> been submitted to the drafts editor and can also be found at the following
> address:
> 
>   http://www.rfc.se/~jakob/ietf/draft-ietf-dnsext-nsec-rdata-00.txt

i'm looking at the draft from:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-nsec-rdata-00.txt

I have made the following observations:

1. Introduction:

   amount of space it uses for the common case of a few types with an
   owner name; that it can represent owner names with all possible type
   present in packets of approximately 8.5 kilobytes; that the
   representation is simple to implement. Efficient searching of the
 
I didn't closely follow the NSEC discussion...but where is this 8.5 kilobytes
coming from?


2.1.2 The List of Type Bit Map(s) Field:

   the bitmap MUST be removed. Blocks is presented in increasing
   numerical order.

   "|" denotes concatenation
   
   NSEC RDATA = ( Window Block # | Bitmap Length | Bitmap ) +

Shouldn't that be:

Type Bit Map = ( Window Block # | Bitmap Length | Bitmap )

or

Type Bit Maps = ( Window Block # | Bitmap Length | Bitmap ) +

Also I only now notice the '+', more that can be made more explicit.


I'm also missing some text on how to calculate the type from the
bitmap (although that would not be difficult).

I assume something like: Window Block # * 256 + Bit # (in Bitmap).


2.3 NSEC RR Example:

Maybe it is an idea to also include the NSEC RR with integers instead
of RRtypes, thus:

alfa.example.com. 86400 IN NSEC host.example.com. A MX RRSIG NSEC
or
alfa.example.com. 86400 IN NSEC host.example.com. 1 23 47 48 
(i'm too lazy to lookup the correct typecodes for the types)

This integer stuff, was that already in the NXT record? If not,
why is it here? (unknown RRs probably). Can I mix integers and
real types in a NSEC RR?

grtz Miek


--
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/>