RFC 3633 on IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
rfc-editor@rfc-editor.org Fri, 19 December 2003 00:42 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02193 for <ietf-announce-web-archive@odin.ietf.org>; Thu, 18 Dec 2003 19:42:18 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AX8Z6-0001jo-GN for ietf-announce-list@asgard.ietf.org; Thu, 18 Dec 2003 19:32:24 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AX8WS-0001ia-6X for all-ietf@asgard.ietf.org; Thu, 18 Dec 2003 19:29:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01388 for <all-ietf@ietf.org>; Thu, 18 Dec 2003 19:29:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AX8WL-0002g8-00 for all-ietf@ietf.org; Thu, 18 Dec 2003 19:29:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AX8Vv-0002fu-00 for all-ietf@ietf.org; Thu, 18 Dec 2003 19:29:08 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AX8Vu-0002fc-00 for all-ietf@ietf.org; Thu, 18 Dec 2003 19:29:07 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hBJ0Sps20454; Thu, 18 Dec 2003 16:28:51 -0800 (PST)
Message-Id: <200312190028.hBJ0Sps20454@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3633 on IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6
Cc: rfc-editor@rfc-editor.org, dhcw@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 18 Dec 2003 16:28:51 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3633 Title: IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6 Author(s): O. Troan, R. Droms Status: Standards Track Date: December 2003 Mailbox: ot@cisco.com, rdroms@cisco.com Pages: 19 Characters: 45308 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-dhcpv6-opt-prefix-delegation-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3633.txt The Prefix Delegation options provide a mechanism for automated delegation of IPv6 prefixes using the Dynamic Host Configuration Protocol (DHCP). This mechanism is intended for delegating a long-lived prefix from a delegating router to a requesting router, across an administrative boundary, where the delegating router does not require knowledge about the topology of the links in the network to which the prefixes will be assigned. 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.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.