From: Patrick Kelly <kameo76890@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Are we ready for DNSSEC ?
Date: Wed, 20 Jan 2010 11:39:05 -0500 [thread overview]
Message-ID: <41CF4DC9-7F76-4902-8F8A-28A477A798DE@gmail.com> (raw)
In-Reply-To: <9c614339d11833003968916e4dff66bb@coraid.com>
On Jan 20, 2010, at 10:33 AM, erik quanstrom <quanstro@coraid.com>
wrote:
>>> one would likely need to start with a different structure
>>> than ndb/dns currently has to get dnssec. but i think that
>>> the most of the query logic could be reused.
>> As I understand it; It is an extension, the base DNS stuff should not
>> change.
>> What would need to be changed in ndb, or would looking at the source
>> be better?
>
> i think your understanding ma be incomplete. dnssec
> requires that the rrs be chained together in a particular
> order. and any change to a rr triggers resigning. it
> may be doable, but i think it would be easier to start
> with dnssec in mind.
That makes their use of the word extension wrong, but in that case
starting over would seem (and probably is) best.
Thanks.
>
> - erik
>
next prev parent reply other threads:[~2010-01-20 16:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 13:26 maht
2010-01-20 13:42 ` erik quanstrom
2010-01-20 15:14 ` Patrick Kelly
2010-01-20 15:33 ` erik quanstrom
2010-01-20 16:39 ` Patrick Kelly [this message]
2010-01-20 16:49 ` erik quanstrom
2010-01-20 17:29 ` Patrick Kelly
2010-01-20 17:47 ` Russ Cox
2010-01-20 18:17 ` erik quanstrom
2010-01-20 20:11 ` Russ Cox
2010-01-20 19:13 ` Patrick Kelly
2010-01-23 23:59 ` John Barham
2010-01-24 0:42 ` erik quanstrom
2010-01-24 0:52 ` Russ Cox
2010-01-24 1:01 ` erik quanstrom
2010-01-24 1:11 ` Russ Cox
2010-01-24 1:18 ` erik quanstrom
2010-01-24 13:19 ` hiro
2010-01-24 14:57 ` erik quanstrom
2010-01-24 21:49 ` Russ Cox
2010-01-24 22:12 ` Tim Newsham
2010-01-24 22:20 ` erik quanstrom
2010-01-24 18:14 ` Tim Newsham
2010-01-25 20:45 ` Wes Kussmaul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41CF4DC9-7F76-4902-8F8A-28A477A798DE@gmail.com \
--to=kameo76890@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).