Fwd: I-D ACTION:draft-ietf-dnsext-delegation-signer-00.txt

[Olafur Gudmundsson <ogud@ogud.com>]

Just in case anyone did not see this one, here are my .02 SKR solution to
the problem of keysets at apex.
Please read and comment as I would like do figure out real soon
if this is better or worse than Sigs at parent.
If there is no consensus on either this or Sigs at parent then sigs at
child wins.

         Olafur

>To: IETF-Announce: ;
>Cc: namedroppers@ops.ietf.org
>From: Internet-Drafts@ietf.org
>Reply-to: Internet-Drafts@ietf.org
>Subject: I-D ACTION:draft-ietf-dnsext-delegation-signer-00.txt
>Date: Thu, 31 May 2001 06:58:17 -0400
>Sender: owner-namedroppers@ops.ietf.org
>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the DNS Extensions Working Group of the IETF.
>
>         Title           : Delegation Signer record in parent
>         Author(s)       : O. Gudmundsson
>         Filename        : draft-ietf-dnsext-delegation-signer-00.txt
>         Pages           : 10
>         Date            : 30-May-01
>
>One of the biggest problems in DNS occur when records of the same type
>can appear on both sides of an delegation. If the contents of these
>sets differs clients can get confused.  RFC2535 KEY records follows
>the same model as for NS records, parent is responsible for the
>records but the child is responsible for the contents.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-dnsext-delegation-signer-00.txt
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
>         "get draft-ietf-dnsext-delegation-signer-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>         mailserv@ietf.org.
>In the body type:
>         "FILE /internet-drafts/draft-ietf-dnsext-delegation-signer-00.txt".
>
>NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <20010530130247.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-dnsext-delegation-signer-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-dnsext-delegation-signer-00.txt>