[rfc-dist] RFC 4703 on Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) Clients

[rfc-editor@rfc-editor.org]

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

        
        RFC 4703

        Title:      Resolution of Fully Qualified Domain 
                    Name (FQDN) Conflicts among Dynamic Host 
                    Configuration Protocol (DHCP) Clients 
        Author:     M. Stapp, B. Volz
        Status:     Standards Track
        Date:       October 2006
        Mailbox:    mjs at cisco.com, 
                    volz at cisco.com
        Pages:      13
        Characters: 29690
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-ddns-resolution-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4703.txt

The Dynamic Host Configuration Protocol (DHCP) provides a mechanism
for host configuration that includes dynamic assignment of IP
addresses and fully qualified domain names.  To maintain accurate
name-to-IP-address and IP-address-to-name mappings in the DNS, these
dynamically assigned addresses and fully qualified domain names
(FQDNs) require updates to the DNS.  This document identifies
situations in which conflicts in the use of fully qualified domain
names may arise among DHCP clients and servers, and it describes a
strategy for the use of the DHCID DNS resource record (RR) in
resolving those conflicts.  [STANDARDS TRACK]

This document is a product of the Dynamic Host Configuration
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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 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.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...