[rfc-dist] RFC 3925 on Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Oct 22 14:38:35 PDT 2004


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


        RFC 3925

        Title:      Vendor-Identifying Vendor Options for
                    Dynamic Host Configuration Protocol version 4
                    (DHCPv4)
        Author(s):  J. Littlefield
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    joshl at cisco.com
        Pages:      9
        Characters: 17999
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-vendor-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3925.txt


The Dynamic Host Configuration Protocol (DHCP) options for Vendor
Class and Vendor-Specific Information can be limiting or ambiguous
when a DHCP client represents multiple vendors.  This document defines
two new options, modeled on the IPv6 options for vendor class and
vendor-specific information, that contain Enterprise Numbers to
remove ambiguity.

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list