idnits 2.17.1 draft-ietf-dhc-dhcpv6-28.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3315 5 Title: Dynamic Host Configuration Protocol for IPv6 6 (DHCPv6) 7 Author(s): R. Droms, Ed., J. Bound, B. Volz, T. Lemon, 8 C. Perkins, M. Carney 9 Status: Standards Track 10 Date: July 2003 11 Mailbox: rdroms@cisco.com, Jim.Bound@hp.com, 12 volz@metrocast.net, Ted.Lemon@nominum.com, 13 charliep@iprg.nokia.com, michael.carney@sun.com 14 Pages: 101 15 Characters: 231402 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-dhc-dhcpv6-28.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3315.txt 22 The Dynamic Host Configuration Protocol for IPv6 (DHCP) enables 23 DHCP servers to pass configuration parameters such as IPv6 network 24 addresses to IPv6 nodes. It offers the capability of automatic 25 allocation of reusable network addresses and additional configuration 26 flexibility. This protocol is a stateful counterpart to "IPv6 27 Stateless Address Autoconfiguration" (RFC 2462), and can be used 28 separately or concurrently with the latter to obtain configuration 29 parameters. 31 This document is a product of the Dynamic Host Configuration Working 32 Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.