RFC 3258 on Distributing Authoritative Name Servers
RFC Editor <rfc-ed@ISI.EDU> Wed, 17 April 2002 00:15 UTC
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09256 for <dnsop-archive@odin.ietf.org>; Tue, 16 Apr 2002 20:15:55 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.3/8.12.3) with ESMTP id g3GNn2TB018223 for <dnsop-outgoing@nic.cafax.se>; Wed, 17 Apr 2002 01:49:02 +0200 (MEST)
Received: by nic.cafax.se (8.12.3/8.12.3/Submit) id g3GNn2kC018222 for dnsop-outgoing; Wed, 17 Apr 2002 01:49:02 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-dnsop@cafax.se using -f
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by nic.cafax.se (8.12.3/8.12.3) with ESMTP id g3GNn1TB018217 for <dnsop@cafax.se>; Wed, 17 Apr 2002 01:49:01 +0200 (MEST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g3GNmsm02386; Tue, 16 Apr 2002 16:48:54 -0700 (PDT)
Message-Id: <200204162348.g3GNmsm02386@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3258 on Distributing Authoritative Name Servers
Cc: rfc-editor@rfc-editor.org, dnsop@cafax.se
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 16 Apr 2002 16:48:54 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-dnsop@cafax.se
Precedence: bulk
A new Request for Comments is now available in online RFC libraries.
RFC 3258
Title: Distributing Authoritative Name Servers via Shared
Unicast Addresses
Author(s): T. Hardie
Status: Informational
Date: April 2002
Mailbox: Ted.Hardie@nominum.com
Pages: 11
Characters: 22195
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsop-hardie-shared-root-server-07.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3258.txt
This memo describes a set of practices intended to enable an
authoritative name server operator to provide access to a single named
server in multiple locations. The primary motivation for the
development and deployment of these practices is to increase the
distribution of Domain Name System (DNS) servers to previously
under-served areas of the network topology and to reduce the latency
for DNS query responses in those areas.
This document is a product of the Domain Name Server Operations
Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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.