datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

Prefix Exclude Option for DHCPv6-based Prefix Delegation
RFC 6603

Internet Engineering Task Force (IETF)                  J. Korhonen, Ed.
Request for Comments: 6603                        Nokia Siemens Networks
Updates: 3633                                              T. Savolainen
Category: Standards Track                                          Nokia
ISSN: 2070-1721                                              S. Krishnan
                                                                Ericsson
                                                                O. Troan
                                                      Cisco Systems, Inc
                                                                May 2012

        Prefix Exclude Option for DHCPv6-based Prefix Delegation

Abstract

   This specification defines an optional mechanism to allow exclusion
   of one specific prefix from a delegated prefix set when using
   DHCPv6-based prefix delegation.  The new mechanism updates RFC 3633.

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/rfc6603.

Copyright Notice

   Copyright (c) 2012 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.

Korhonen, et al.             Standards Track                    [Page 1]
RFC 6603                    PD Exclude Option                   May 2012

Table of Contents

   1. Introduction ....................................................2
   2. Requirements and Terminology ....................................2
   3. Problem Background ..............................................3
   4. Solution ........................................................3
      4.1. Prefix Delegation with Excluded Prefixes ...................3
      4.2. Prefix Exclude Option ......................................4
   5. Delegating Router Solicitation ..................................6
      5.1. Requesting Router ..........................................6
      5.2. Delegating Router ..........................................6
   6. Requesting Router Initiated Prefix Delegation ...................7
      6.1. Requesting Router ..........................................7
      6.2. Delegating Router ..........................................8
   7. Security Considerations .........................................8
   8. IANA Considerations .............................................8
   9. Acknowledgements ................................................8
   10. References .....................................................9
      10.1. Normative References ......................................9
      10.2. Informative References ....................................9

1.  Introduction

   This specification defines an optional mechanism and the related
   DHCPv6 option to allow exclusion of one specific prefix from a
   delegated prefix set when using DHCPv6-based prefix delegation.

   The prefix exclusion mechanism is targeted at deployments where
   DHCPv6-based prefix delegation is used, but a single aggregated
   route/prefix has to represent one customer, instead of using one
   prefix for the link between the delegating router and the requesting
   router and another prefix for the customer network.  The mechanism
   defined in this specification allows a delegating router to use a
   prefix out of the delegated prefix set on the link through which it
   exchanges 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

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

[include full document text]