[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSEC++ (Example code broken)

To: "Scott Rose" <scottr@nist.gov>
Subject: Re: NSEC++ (Example code broken)
From: Olaf Kolkman <OKolkman@ripe.net>
Date: Tue, 09 Dec 2003 21:40:57 +0100
Cc: namedroppers@ops.ietf.org
In-reply-to: Your message of Tue, 09 Dec 2003 13:27:01 EST. <00a601c3be82$0a1b40d0$b9370681@barnacle>
References: <00a601c3be82$0a1b40d0$b9370681@barnacle>

 "Scott Rose" <scottr@nist.gov> writes:
 * 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?
 * 

No it is not... I do not understand why I did not catch that in the first place. Hex-diziness I am affraid.

--Olaf



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

References:
- Re: NSEC++ (Example code broken)
  - From: "Scott Rose" <scottr@nist.gov>

Prev by Date: Re: NSEC++ (Example code broken)
Next by Date: Fingerprinting DNS implementations.
Previous by thread: Re: NSEC++ (Example code broken)
Next by thread: Fingerprinting DNS implementations.
Index(es):
- Date
- Thread