Re: NSEC++ (Example code broken)

["Scott Rose" <scottr@nist.gov>]

I thought it looked okay.  I noticed the trailing 0x00 octet after the 0x03
in the example below.  Isn't that a trailing null octet in the first window?
Is that necessary?

Scott
----- Original Message ----- 
From: "Olaf M. Kolkman" <olaf@ripe.net>
To: <namedroppers@ops.ietf.org>
Sent: Tuesday, December 09, 2003 10:13 AM
Subject: NSEC++ (Example code broken)


>
> WRT: draft-ietf-ndsext-nsec-rdata-01.
>
> While testing some code; I think the example in section 3 should read:
>
> 0x04 'h'  'o'  's'  't'
> 0x07 'e'  'x'  'a'  'm'  'p'  'l'  'e'
> 0x03 'c'  'o'  'm'  0x00
> 0x00 0x07 0x40 0x01 0x00 0x00 0x00 0x03
> 0x00 0x04 0x1b 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00 0x00 0x00 0x00 0x20
>
> Can somebody confirm that?
>
>
> -- Olaf
>    namedropper.
>
> ---------------------------------| Olaf M. Kolkman
> ---------------------------------| RIPE NCC
>
>
> --
> 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/>
>


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