RFC 4892 on Requirements for a Mechanism Identifying a Name Server Instance

[rfc-editor at rfc-editor.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 at isc.org, 

                    david.conrad at 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 at IETFC in question, or to RFC-Manager at 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 at 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 at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce