draft-ietf-dhc-pd-exclude-02.txt   draft-ietf-dhc-pd-exclude-03.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: December 22, 2011 S. Krishnan Expires: February 6, 2012 S. Krishnan
Ericsson Ericsson
O. Troan O. Troan
Cisco Systems, Inc Cisco Systems, Inc
June 20, 2011 August 5, 2011
Prefix Exclude Option for DHCPv6-based Prefix Delegation Prefix Exclude Option for DHCPv6-based Prefix Delegation
draft-ietf-dhc-pd-exclude-02.txt draft-ietf-dhc-pd-exclude-03.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 December 22, 2011. This Internet-Draft will expire on February 6, 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 6, line 48 skipping to change at page 6, line 48
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 uses the Once receiving Advertise message, the requesting router MAY use 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 to respond to. advertised prefixes to choose the delegating router. If Advertise
If Advertise message did not include OPTION_PD_EXCLUDE option, then message did not include OPTION_PD_EXCLUDE option, then the requesting
the requesting router MUST fall back to normal [RFC3633] Section 11.1 router MUST fall back to normal [RFC3633] Section 11.1 behavior.
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 42 skipping to change at page 8, line 41
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 Tomek Behcet Sarikaya, Jyrki Soini, Deng Hui, Stephen Jacob and Tomasz
Mrugalski for their valuable comments and discussions. 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
 End of changes. 7 change blocks. 
10 lines changed or deleted 9 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/