[dhcwg] RFC 4702 on The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option

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

        RFC 4702

        Title:      The Dynamic Host Configuration Protocol 
                    (DHCP) Client Fully Qualified Domain Name 
                    (FQDN) Option 
        Author:     M. Stapp, B. Volz,
                    Y. Rekhter
        Status:     Standards Track
        Date:       October 2006
        Mailbox:    mjs@cisco.com, 
                    volz@cisco.com, 
                    yakov@juniper.net
        Pages:      17
        Characters: 37534
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-fqdn-option-13.txt

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

This document describes a Dynamic Host Configuration Protocol for
IPv4 (DHCPv4) option that can be used to exchange information about a
DHCPv4 client's fully qualified domain name and about responsibility
for updating the DNS RR related to the client's address assignment.  
[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

...

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg