Re: Beating an Old Horse, but....

--0016e642db8c86108c0491d50678
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2010/10/4 Colm MacC=E1rthaigh <[email protected]>

>
> A preprocessor wouldn't do. The name-server would need to support EDNS0,
> and the smarts to include DS and RRSIG records correctly. Additionally, i=
n
> order to support NSEC and NSEC3 there would need to be a lexicographicall=
y
> ordered index available - a CDB backend won't do. It's a fairly large
> undertaking.
>

For those not familiar with the guts of the various RFCs, could you perhaps
expand on that statement a little?  Note that I'm not disagreeing with you,
I just don't understand the details enough to follow from your premise to
your conclusion.

--0016e642db8c86108c0491d50678
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2010/10/4 Colm MacC=E1rthaigh <span dir=3D"ltr">&lt;<a href=3D"mailto:colm@=
allcosts.net">[email protected]</a>&gt;</span><br><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bor=
der-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><br></div><div>A preprocessor wouldn&#39;t do. The name-server would n=
eed to support EDNS0, and the smarts to include DS and RRSIG records correc=
tly. Additionally, in order to support NSEC and NSEC3 there would need to b=
e a lexicographically ordered index available - a CDB backend won&#39;t do.=
 It&#39;s a fairly large undertaking.</div>
</blockquote><div><br>For those not familiar with the guts of the various R=
FCs, could you perhaps expand on that statement a little?=A0 Note that I&#3=
9;m not disagreeing with you, I just don&#39;t understand the details enoug=
h to follow from your premise to your conclusion. =A0 <br>
</div></div>

--0016e642db8c86108c0491d50678--