RFC 4243 on Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

RFC 4243 on Vendor-Specific Information Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option

RFC Errata System

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


        RFC 4243

        Title:      Vendor-Specific Information Suboption for the
                    Dynamic Host Configuration Protocol (DHCP) Relay
                    Agent Option
        Author(s):  M. Stapp, R. Johnson, T. Palaniappan
        Status:     Standards Track
        Date:       December 2005
        Mailbox:    [hidden email], [hidden email], [hidden email]
        Pages:      7
        Characters: 14342
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-vendor-suboption-00.txt

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


This memo defines a new Vendor-Specific Information suboption for the
Dynamic Host Configuration Protocol's (DHCP) relay agent information
option.  The suboption allows a DHCP relay agent to include
vendor-specific information in the DHCP messages it forwards, as
configured by its administrator.

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 [hidden email].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [hidden email].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [hidden email] with the message body
help: ways_to_get_rfcs.  For example:

        To: [hidden email]
        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 [hidden email].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[hidden email].  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.

_______________________________________________
IETF-Announce mailing list
[hidden email]
https://www1.ietf.org/mailman/listinfo/ietf-announce

attachment0 (107 bytes) Download Attachment
rfc4243.txt (75 bytes) Download Attachment