RFC 4701 on A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)

rfc-editor@rfc-editor.org Thu, 26 October 2006 02:19 UTC

Date: Wed, 25 Oct 2006 19:10:17 -0700
Message-Id: <200610260210.k9Q2AHiq029787@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 4701 on A DNS Resource Record (RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID RR)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, namedroppers@ops.ietf.org
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

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

        
        RFC 4701

        Title:      A DNS Resource Record (RR) 
                    for Encoding Dynamic Host Configuration Protocol 
                    (DHCP) Information (DHCID RR) 
        Author:     M. Stapp, T. Lemon,
                    A. Gustafsson
        Status:     Standards Track
        Date:       October 2006
        Mailbox:    mjs@cisco.com, 
                    mellon@nominum.com, 
                    gson@araneus.fi
        Pages:      12
        Characters: 24570
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsext-dhcid-rr-13.txt

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

It is possible for Dynamic Host Configuration Protocol (DHCP) clients
to attempt to update the same DNS Fully Qualified Domain Name (FQDN)
or to update a DNS FQDN that has been added to the DNS for another
purpose as they obtain DHCP leases.  Whether the DHCP server or the
clients themselves perform the DNS updates, conflicts can arise.  To
resolve such conflicts, RFC 4703 proposes storing client identifiers
in the DNS to unambiguously associate domain names with the DHCP
clients to which they refer.  This memo defines a distinct Resource
Record (RR) type for this purpose for use by DHCP clients and servers:
the "DHCID" RR.  [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@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.


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

...



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

RFC 4701 on A DNS Resource Record (RR) for Encodi… rfc-editor