Reconfigure Triggered by DHCPv6 Relay Agents
draft-ietf-dhc-triggered-reconfigure-05
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (dhc WG) | |
Last updated | 2013-05-06 (latest revision 2013-03-21) | ||
Replaces | draft-boucadair-dhc-triggered-reconfigure | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text pdf html bibtex | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Bernie Volz | ||
Shepherd write-up | Show (last changed 2013-04-05) | ||
IESG | IESG state | Waiting for AD Go-Ahead | |
Consensus Boilerplate | Unknown | ||
Telechat date |
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Ted Lemon | ||
IESG note | Bernie Volz is the document shepherd (volz@cisco.com). | ||
Send notices to | dhc-chairs@tools.ietf.org, draft-ietf-dhc-triggered-reconfigure@tools.ietf.org | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | None |
DHC Working Group M. Boucadair Internet-Draft X. Pougnard Updates: 3315, 6422 (if approved) France Telecom Intended status: Standards Track March 21, 2013 Expires: September 22, 2013 Reconfigure Triggered by DHCPv6 Relay Agents draft-ietf-dhc-triggered-reconfigure-05 Abstract This document defines new DHCPv6 messages: Reconfigure-Request and Reconfigure-Reply. Reconfigure-Request message is sent by a DHCPv6 relay agent to notify a DHCPv6 server about a configuration information change, so that the DHCPv6 server can send a Reconfigure message accordingly. Reconfigure-Reply message is used by the server to acknowledge the receipt of Reconfigure-Request. This document updates RFC 3315 and RFC 6422. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 22, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect Boucadair & Pougnard Expires September 22, 2013 [Page 1] Internet-Draft Relay Triggered Reconfigure March 2013 to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 3. Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Proposed Solution . . . . . . . . . . . . . . . . . . . . . . 4 5. Link Address Option . . . . . . . . . . . . . . . . . . . . . 6 6. Detailed Specification . . . . . . . . . . . . . . . . . . . 6 6.1. Messages Format . . . . . . . . . . . . . . . . . . . . . 7 6.2. Messages Validation . . . . . . . . . . . . . . . . . . . 7 6.2.1. RECONFIGURE-REQUEST . . . . . . . . . . . . . . . . . 7 6.2.2. RECONFIGURE-REPLY . . . . . . . . . . . . . . . . . . 7 6.3. Creation and Transmission of RECONFIGURE-REQUEST . . . . 7 6.4. Intermediate Relay Agents Behaviour . . . . . . . . . . . 9 6.5. Server Behaviour . . . . . . . . . . . . . . . . . . . . 9 6.6. Receipt of RECONFIGURE-REPLY . . . . . . . . . . . . . . 10 7. Rate Limiting Considerations . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 11 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . 12 11.2. Informative References . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction This document specifies two new DHCPv6 messages [RFC3315]: Reconfigure-Request and Reconfigure-Reply. Section 3 describes a typical problem encountered to trigger the DHCPv6 server to issue a Reconfigure message when the configuration data is supplied by the relay agent. This problem may be encountered in other contexts. It is out of scope of this document to list all these cases. Section 4 describes the proposed solution which relies on the use of Reconfigure-Request and Reconfigure-Reply messages. Reconfigure- Request message is sent by a DHCPv6 relay agent to notify a DHCPv6 server about a configuration information change, so that the DHCPv6 server can send a Reconfigure message accordingly. Reconfigure-Reply message is used by the server to acknowledge the receipt ofShow full document text