[dhcwg] RFC 3442 on The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4

rfc-editor@rfc-editor.org Sat, 14 December 2002 01:20 UTC

Message-Id: <200212140119.gBE1JoD29750@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, dhcwg@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 13 Dec 2002 17:19:50 -0800
Subject: [dhcwg] RFC 3442 on The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
Precedence: bulk

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


        RFC 3442
                                    
        Title:      The Classless Static Route Option for Dynamic Host
                    Configuration Protocol (DHCP) version 4
        Author(s):  T. Lemon, S. Cheshire, B. Volz
        Status:     Standards Track
        Date:       December 2002
        Mailbox:    Ted.Lemon@nominum.com, rfc@stuartcheshire.org,
                    bernie.volz@ericsson.com
        Pages:      9
        Characters: 19370
        Updates:    2132
                                    
        I-D Tag:    draft-ietf-dhc-csr-07.txt

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


This document defines a new Dynamic Host Configuration Protocol (DHCP)
option which is passed from the DHCP Server to the DHCP Client to
configure a list of static routes in the client.  The network
destinations in these routes are classless - each routing table entry
includes a subnet mask.

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

This is now a Proposed Standard Working Group of the IETF.

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.echo 
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.

ftp://ftp.isi.edu/in-notes/rfc3442.txt"><ftp://ftp.isi.edu/in-notes/rfc3442.txt>

[dhcwg] RFC 3442 on The Classless Static Route Op… rfc-editor