--NextPart


A new Request for Comments is now available in online RFC libraries.


RFC 3845

Title: DNS Security (DNSSEC) NextSECure (NSEC) RDATA
Format
Author(s): J. Schlyter, Ed.
Status: Standards Track
Date: August 2004
Mailbox: jakob@nic.se
Pages: 7
Characters: 14793
Updates: 3755, 2535

I-D Tag: draft-ietf-dnsext-nsec-rdata-06.txt

URL: ftp://ftp.rfc-editor.org/in-notes/rfc3845.txt


This document redefines the wire format of the "Type Bit Map" field
in the DNS NextSECure (NSEC) resource record RDATA format to cover the
full resource record (RR) type space.

This document is a product of the DNS Extensions Working Group of the
IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:

To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs

help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

....

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <040817171625.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3845

--OtherAccess
Content-Type: Message/External-body;
name="rfc3845.txt";
site="ftp.isi.edu";
access-type="anon-ftp";
directory="in-notes"

Content-Type: text/plain
Content-ID: <040817171625.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

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