[dhcwg] RFC 4030 on The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option

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

        RFC 4030

        Title:      The Authentication Suboption for the
                    Dynamic Host Configuration Protocol (DHCP)
                    Relay Agent Option
        Author(s):  M. Stapp, T. Lemon
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    mjs@cisco.com, Ted.Lemon@nominum.com
        Pages:      15
        Characters: 34332
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-auth-suboption-05.txt

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

The Dynamic Host Configuration Protocol (DHCP) Relay Agent Information
Option (RFC 3046) conveys information between a DHCP Relay Agent and a
DHCP server.  This specification defines an authentication suboption
for that option, containing a keyed hash in its payload.  The
suboption supports data integrity and replay protection for relayed
DHCP messages.

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@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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.