[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3011 on Subnet Selection Option
- To: IETF-Announce: ;
- Subject: RFC 3011 on Subnet Selection Option
- From: RFC Editor <rfc-ed@ISI.EDU>
- Date: Thu, 30 Nov 2000 17:24:19 -0800
- Cc: rfc-ed@ISI.EDU, firstname.lastname@example.org
- Delivery-date: Fri, 01 Dec 2000 03:55:55 +0200
- Envelope-to: email@example.com
A new Request for Comments is now available in online RFC libraries.
Title: The IPv4 Subnet Selection Option for DHCP
Author(s): G. Waters
Status: Standards Track
Date: November 2000
I-D Tag: draft-ietf-dhc-subnet-option-07.txt
This memo defines a new Dynamic Host Configuration Protocol (DHCP)
option for selecting the subnet on which to allocate an address. This
option would override a DHCP server's normal methods of selecting the
subnet on which to allocate an address for a client.
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:
Subject: getting 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
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.