9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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 12:29:18 -0500	[thread overview]
Message-ID: <9D2057F2-1DC9-4D85-A1EB-C26630634C33@gmail.com> (raw)
In-Reply-To: <dd57a1d33587e2be68c04f23ccdccdbc@coraid.com>


>
>> That makes their use of the word extension wrong, but in that case
>> starting over would seem (and probably is) best.
>
> i think it fits the definition of extension.  the protocol is
> compatable with dnssec-unaware implementations.
Since part of the base was modified, but it's still backwards
compatable extension isn't the right term, I can not think of the
proper word; I am being anal.

At any rate, was there a date this would be implimented? I'm looking
forewards to seeing how much this actually fixes.
> - erik
>



  reply	other threads:[~2010-01-20 17:29 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
2010-01-20 16:49         ` erik quanstrom
2010-01-20 17:29           ` Patrick Kelly [this message]
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=9D2057F2-1DC9-4D85-A1EB-C26630634C33@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).