RFC on Extension Mechanisms for DNS (EDNS0)

RFC Editor <rfc-ed@ISI.EDU> Thu, 26 August 1999 00:35 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15938; Wed, 25 Aug 1999 20:35:32 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA14706 for ietf-123-outbound.10@ietf.org; Wed, 25 Aug 1999 20:35:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA14606 for <all-ietf@loki.ietf.org>; Wed, 25 Aug 1999 20:23:16 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15551 for <all-ietf@ietf.org>; Wed, 25 Aug 1999 20:17:53 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA06471; Wed, 25 Aug 1999 17:17:54 -0700 (PDT)
Message-Id: <199908260017.RAA06471@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC on Extension Mechanisms for DNS (EDNS0)
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 25 Aug 1999 17:17:54 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2671:

        Title:	    Extension Mechanisms for DNS (EDNS0)
        Author(s):  P. Vixie
        Status:     Standards Track
	Date:       August 1999
        Mailbox:    vixie@isc.org
        Pages:      7
        Characters: 15257
	Updates:    
        I-D Tag:    draft-ietf-dnsind-edns0-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2671.txt


This document describes backward compatible mechanisms for allowing 
the protocol to grow.

This document is a product of the DNS IXFR, Notification, and Dynamic
Update 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.
ftp://ftp.isi.edu/in-notes/rfc2671.txt"><ftp://ftp.isi.edu/in-notes/rfc2671.txt>