draft-ietf-dhc-pd-exclude-03.txt   draft-ietf-dhc-pd-exclude-04.txt 
Dynamic Host Configuration (DHC) J. Korhonen, Ed. Dynamic Host Configuration (DHC) J. Korhonen, Ed.
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Updates: 3633 (if approved) T. Savolainen Updates: 3633 (if approved) T. Savolainen
Intended status: Standards Track Nokia Intended status: Standards Track Nokia
Expires: February 6, 2012 S. Krishnan Expires: June 22, 2012 S. Krishnan
Ericsson Ericsson
O. Troan O. Troan
Cisco Systems, Inc Cisco Systems, Inc
August 5, 2011 December 20, 2011
Prefix Exclude Option for DHCPv6-based Prefix Delegation Prefix Exclude Option for DHCPv6-based Prefix Delegation
draft-ietf-dhc-pd-exclude-03.txt draft-ietf-dhc-pd-exclude-04.txt
Abstract Abstract
This specification defines an optional mechanism to allow exclusion This specification defines an optional mechanism to allow exclusion
of one specific prefix from a delegated prefix set when using DHCPv6- of one specific prefix from a delegated prefix set when using DHCPv6-
based prefix delegation. The new mechanism updates RFC 3633. based prefix delegation. The new mechanism updates RFC 3633.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 6, 2012. This Internet-Draft will expire on June 22, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 13 skipping to change at page 2, line 13
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements and Terminology . . . . . . . . . . . . . . . . . 3 2. Requirements and Terminology . . . . . . . . . . . . . . . . . 3
3. Problem Background . . . . . . . . . . . . . . . . . . . . . . 3 3. Problem Background . . . . . . . . . . . . . . . . . . . . . . 3
4. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Prefix Delegation with Excluded Prefixes . . . . . . . . . 4 4.1. Prefix Delegation with Excluded Prefixes . . . . . . . . . 4
4.2. Prefix Exclude Option . . . . . . . . . . . . . . . . . . . 4 4.2. Prefix Exclude Option . . . . . . . . . . . . . . . . . . . 4
5. Delegating Router Solicitation . . . . . . . . . . . . . . . . 6 5. Delegating Router Solicitation . . . . . . . . . . . . . . . . 6
5.1. Requesting Router . . . . . . . . . . . . . . . . . . . . . 6 5.1. Requesting Router . . . . . . . . . . . . . . . . . . . . . 6
5.2. Delegating Router . . . . . . . . . . . . . . . . . . . . . 7 5.2. Delegating Router . . . . . . . . . . . . . . . . . . . . . 7
6. Requesting Router Initiated Prefix Delegation . . . . . . . . . 7 6. Requesting Router Initiated Prefix Delegation . . . . . . . . . 7
6.1. Requesting Router . . . . . . . . . . . . . . . . . . . . . 7 6.1. Requesting Router . . . . . . . . . . . . . . . . . . . . . 7
6.2. Delegating Router . . . . . . . . . . . . . . . . . . . . . 8 6.2. Delegating Router . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 3, line 12 skipping to change at page 3, line 12
10.2. Informative References . . . . . . . . . . . . . . . . . . 9 10.2. Informative References . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
This specification defines an optional mechanism and the related This specification defines an optional mechanism and the related
DHCPv6 option to allow exclusion of one specific prefix from a DHCPv6 option to allow exclusion of one specific prefix from a
delegated prefix set when using DHCPv6-based prefix delegation. delegated prefix set when using DHCPv6-based prefix delegation.
The prefix exclusion mechanism is targeted to deployments where The prefix exclusion mechanism is targeted to deployments where
DHCPv6-based prefix delegation is used but a single aggregatable DHCPv6-based prefix delegation is used but a single aggregated route/
route/prefix has to represent one customer, instead of using one prefix has to represent one customer, instead of using one prefix for
prefix for the link between the delegating router and the requesting the link between the delegating router and the requesting router and
router and another prefix for the customer network. The mechanism another prefix for the customer network. The mechanism defined in
defined in this specification allows a delegating router to use a this specification allows a delegating router to use a prefix out of
prefix out of the delegated prefix set on the link through which it the delegated prefix set on the link through which it exchanges
exchanges DHCPv6 messages with the requesting router. DHCPv6 messages with the requesting router, and is intended for use
in networks where each requesting router is on its own layer 2
domain.
2. Requirements and Terminology 2. Requirements and Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Problem Background 3. Problem Background
DHCPv6 Prefix Delegation (DHCPv6-PD) [RFC3633] has an explicit DHCPv6 Prefix Delegation (DHCPv6-PD) [RFC3633] has an explicit
skipping to change at page 4, line 17 skipping to change at page 4, line 20
(TBD1), that is used to exclude exactly one prefix from a delegated (TBD1), that is used to exclude exactly one prefix from a delegated
prefix. The OPTION_PD_EXCLUDE is included in the OPTION_IAPREFIX prefix. The OPTION_PD_EXCLUDE is included in the OPTION_IAPREFIX
IAprefix-options field. There can be at most one OPTION_PD_EXCLUDE IAprefix-options field. There can be at most one OPTION_PD_EXCLUDE
option in one OPTION_IAPREFIX option. The OPTION_PD_EXCLUDE option option in one OPTION_IAPREFIX option. The OPTION_PD_EXCLUDE option
allows prefix delegation where a requesting router is delegated a allows prefix delegation where a requesting router is delegated a
prefix (e.g. /56) and the delegating router uses one prefix (e.g. prefix (e.g. /56) and the delegating router uses one prefix (e.g.
/64) on the link through which it exchanges DHCPv6 messages with the /64) on the link through which it exchanges DHCPv6 messages with the
requesting router with a prefix out of the same delegated prefix set. requesting router with a prefix out of the same delegated prefix set.
A requesting router includes an OPTION_ORO option with the A requesting router includes an OPTION_ORO option with the
OPTION_PD_EXCLUDE option code in a Solicit, Request, Renew, Rebind or OPTION_PD_EXCLUDE option code in a Solicit, Request, Renew, or Rebind
Confirm message to inform the delegating router about the support for message to inform the delegating router about the support for the
the prefix delegation functionality defined in this specification. A prefix delegation functionality defined in this specification. A
delegating router may include the OPTION_PD_EXCLUDE option code in an delegating router may include the OPTION_PD_EXCLUDE option code in an
OPTION_ORO option in a Reconfigure message for indicating that the OPTION_ORO option in a Reconfigure message for indicating that the
requesting router should request OPTION_PD_EXCLUDE from the requesting router should request OPTION_PD_EXCLUDE from the
delegating router. delegating router.
The delegating router includes the prefix in the OPTION_PD_EXCLUDE The delegating router includes the prefix in the OPTION_PD_EXCLUDE
option that is excluded from the delegated prefix set. The option that is excluded from the delegated prefix set. The
requesting router MUST NOT assign the excluded prefix to any of its requesting router MUST NOT assign the excluded prefix to any of its
downstream interfaces. downstream interfaces.
skipping to change at page 6, line 48 skipping to change at page 6, line 49
only describes the additional steps required by the use of only describes the additional steps required by the use of
OPTION_PD_EXCLUDE option. OPTION_PD_EXCLUDE option.
5.1. Requesting Router 5.1. Requesting Router
If the requesting router implements the solution described in If the requesting router implements the solution described in
Section 4.1 then the requesting router SHOULD include the Section 4.1 then the requesting router SHOULD include the
OPTION_PD_EXCLUDE option code in the OPTION_ORO option in Solicit OPTION_PD_EXCLUDE option code in the OPTION_ORO option in Solicit
messages. messages.
Once receiving Advertise message, the requesting router MAY use the Once receiving Advertise message, the requesting router uses the
prefix(es) received in OPTION_PD_EXCLUDE in addition to the prefix(es) received in OPTION_PD_EXCLUDE in addition to the
advertised prefixes to choose the delegating router. If Advertise advertised prefixes to choose the delegating router. Requesting
message did not include OPTION_PD_EXCLUDE option, then the requesting router MUST proceed to Prefix Delegation procedure described in
router MUST fall back to normal [RFC3633] Section 11.1 behavior. Section 6.1. If Advertise message did not include OPTION_PD_EXCLUDE
option, then the requesting router MUST fall back to normal [RFC3633]
Section 11.1 behavior.
5.2. Delegating Router 5.2. Delegating Router
If the OPTION_ORO option in the Solicit message includes the If the OPTION_ORO option in the Solicit message includes the
OPTION_PD_EXCLUDE option code, then the delegating router knows that OPTION_PD_EXCLUDE option code, then the delegating router knows that
the requesting router supports the solution defined in this the requesting router supports the solution defined in this
specification. If the Solicit message also contains an IA_PD option, specification. If the Solicit message also contains an IA_PD option,
the delegating router can delegate to the requesting router a prefix the delegating router can delegate to the requesting router a prefix
which includes the prefix already assigned to the requesting router's which includes the prefix already assigned to the requesting router's
uplink interface. The delegating router includes the prefix uplink interface. The delegating router includes the prefix
skipping to change at page 8, line 41 skipping to change at page 8, line 45
A new DHCPv6 Option Code is reserved from DHCPv6 registry for DHCP A new DHCPv6 Option Code is reserved from DHCPv6 registry for DHCP
Option Codes. Option Codes.
OPTION_PD_EXCLUDE is set to TBD1 OPTION_PD_EXCLUDE is set to TBD1
9. Acknowledgements 9. Acknowledgements
Authors would like to thank Ralph Droms, Frank Brockners, Ted Lemon, Authors would like to thank Ralph Droms, Frank Brockners, Ted Lemon,
Julien Laganier, Fredrik Garneij, Sri Gundavelli, Mikael Abrahamsson, Julien Laganier, Fredrik Garneij, Sri Gundavelli, Mikael Abrahamsson,
Behcet Sarikaya, Jyrki Soini, Deng Hui, Stephen Jacob and Tomasz Behcet Sarikaya, Jyrki Soini, Deng Hui, Stephen Jacob, Hemant Singh,
Mrugalski for their valuable comments and discussions. Gaurav Halwasia, Lorenzo Colitti and Tomasz Mrugalski for their
valuable comments and discussions.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
 End of changes. 11 change blocks. 
21 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/