Issues and Recommendations with Multiple Stateful DHCPv6 Options
RFC 7550
|
| Document |
Type |
|
RFC - Proposed Standard
(May 2015; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-troan-dhc-dhcpv6-stateful-issues
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Tomek Mrugalski
|
|
Shepherd write-up |
|
Show
(last changed 2015-02-18)
|
| IESG |
IESG state |
|
RFC 7550 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Ted Lemon
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA OK - No Actions Needed
|
|
IANA action state |
|
No IANA Actions
|
Internet Engineering Task Force (IETF) O. Troan
Request for Comments: 7550 B. Volz
Updates: 3315, 3633 Cisco Systems, Inc.
Category: Standards Track M. Siodelski
ISSN: 2070-1721 ISC
May 2015
Issues and Recommendations with Multiple Stateful DHCPv6 Options
Abstract
The Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
specification defined two stateful options, IA_NA and IA_TA, but did
not anticipate the development of additional stateful options.
DHCPv6 Prefix Delegation added the IA_PD option, which is stateful.
Applications that use IA_NA and IA_PD together have revealed issues
that need to be addressed. This document updates RFCs 3315 and 3633
to address these issues.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7550.
Troan, et al. Standards Track [Page 1]
RFC 7550 Multiple Stateful Options May 2015
Copyright Notice
Copyright (c) 2015 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
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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Troan, et al. Standards Track [Page 2]
RFC 7550 Multiple Stateful Options May 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Handling of Multiple IA Option Types . . . . . . . . . . . . 4
4.1. Placement of Status Codes in an Advertise Message . . . . 6
4.2. Advertise Message Processing by a Client . . . . . . . . 8
4.3. T1/T2 Timers . . . . . . . . . . . . . . . . . . . . . . 9
4.4. Renew and Rebind Messages . . . . . . . . . . . . . . . . 10
4.4.1. Renew Message . . . . . . . . . . . . . . . . . . . . 10
4.4.2. Rebind Message . . . . . . . . . . . . . . . . . . . 11
4.4.3. Updates to Section 18.1.3 of RFC 3315 . . . . . . . . 11
4.4.4. Updates to Section 18.1.4 of RFC 3315 . . . . . . . . 13
4.4.5. Updates to Section 18.1.8 of RFC 3315 . . . . . . . . 14
4.4.6. Updates to Section 18.2.3 of RFC 3315 . . . . . . . . 16
4.4.7. Updates to Section 18.2.4 of RFC 3315 . . . . . . . . 18
4.4.8. Updates to RFC 3633 . . . . . . . . . . . . . . . . . 20
4.5. Confirm Message . . . . . . . . . . . . . . . . . . . . . 21
4.6. Decline Should Not Necessarily Trigger a Release . . . . 22
4.7. Multiple Provisioning Domains . . . . . . . . . . . . . . 22
5. Security Considerations . . . . . . . . . . . . . . . . . . . 22
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Normative References . . . . . . . . . . . . . . . . . . 22
6.2. Informative References . . . . . . . . . . . . . . . . . 23
Show full document text