[dhcwg] RFC 4242 on Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

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

        RFC 4242

        Title:      Information Refresh Time Option for
                    Dynamic Host Configuration Protocol for IPv6
                    (DHCPv6)
        Author(s):  S. Venaas, T. Chown, B. Volz
        Status:     Standards Track
        Date:       November 2005
        Mailbox:    venaas@uninett.no, tjc@ecs.soton.ac.uk,
                    volz@cisco.com
        Pages:      8
        Characters: 14759
        Updates/Obsoletes/SeeAlso:    None

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

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

This document describes a Dynamic Host Configuration Protocol for IPv6
(DHCPv6) option for specifying an upper bound for how long a client
should wait before refreshing information retrieved from DHCPv6.  It
is used with stateless DHCPv6 as there are no addresses or other
entities with lifetimes that can tell the client when to contact the
DHCPv6 server to refresh its configuration.

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.