A new Request for Comments is now available in online RFC libraries.
RFC 5001
Title: DNS Name Server Identifier (NSID)
Option
Author: R. Austein
Status: Standards Track
Date: August 2007
Mailbox: [EMAIL PROTECTED]
Pages: 11
Characters: 23754
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dnsext-nsid-02.txt
URL: http://www.rfc-editor.org/rfc/rfc5001.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. While existing ad-hoc
mechanisms allow an operator to send follow-up queries when it is
necessary to debug such a configuration, the only completely reliable
way to obtain the identity of the name server that responded is to
have the name server include this information in the response itself.
This note defines a protocol extension to support this functionality.
[STANDARDS TRACK]
This document is a product of the DNS Extensions
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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 [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
[EMAIL PROTECTED]
https://www1.ietf.org/mailman/listinfo/ietf-announce
--
[email protected] mailing list
Send administrative requests (subscribe, unsubscribe, change options) to:
[EMAIL PROTECTED]
(use "help" in the Subject line for a summary of common options)
You can also use the web interface at:
https://sabahattin-gucukoglu.com/cgi-bin/lsg2.cgi
For assistance, contact:
[EMAIL PROTECTED]
