RFC 4892 on Requirements for a Mechanism Identifying a Name Server Instance
rfc-editor@rfc-editor.org Thu, 21 June 2007 00:30 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1AZJ-0000Ii-D4; Wed, 20 Jun 2007 20:30:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1AZG-0000Cg-Up; Wed, 20 Jun 2007 20:30:34 -0400
Received: from bosco.isi.edu ([128.9.168.207]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1AZE-0002mY-KU; Wed, 20 Jun 2007 20:30:34 -0400
Received: by bosco.isi.edu (Postfix, from userid 70) id 7EF27D6BB6; Wed, 20 Jun 2007 17:29:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20070621002915.7EF27D6BB6@bosco.isi.edu>
Date: Wed, 20 Jun 2007 17:29:15 -0700
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: dnsop@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4892 on Requirements for a Mechanism Identifying a Name Server Instance
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 4892
Title: Requirements for a Mechanism Identifying
a Name Server Instance
Author: S. Woolf, D. Conrad
Status: Informational
Date: June 2007
Mailbox: woolf@isc.org,
david.conrad@icann.org
Pages: 8
Characters: 17605
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsop-serverid-08.txt
URL: http://www.rfc-editor.org/rfc/rfc4892.txt
With the increased use of DNS anycast, load balancing, and other
mechanisms allowing more than one DNS name server to share a single
IP address, it is sometimes difficult to tell which of a pool of name
servers has answered a particular query. A standardized mechanism to
determine the identity of a name server responding to a particular
query would be useful, particularly as a diagnostic aid for
administrators. Existing ad hoc mechanisms for addressing this need
have some shortcomings, not the least of which is the lack of prior
analysis of exactly how such a mechanism should be designed and
deployed. This document describes the existing convention used in
some widely deployed implementations of the DNS protocol, including
advantages and disadvantages, and discusses some attributes of an
improved mechanism. This memo provides information for the Internet
community.
This document is a product of the Domain Name System Operations
Working Group of the IETF.
INFORMATIONAL: 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.
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.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce