datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

Supporting Explicit Inclusion or Exclusion of Abstract Nodes for a Subset of P2MP Destinations in Path Computation Element Communication Protocol (PCEP).
draft-dhody-pce-pcep-p2mp-per-destination-07

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-09-29
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

PCE Working Group                                               D. Dhody
Internet-Draft                                                  U. Palle
Intended status: Experimental                               V. Kondreddy
Expires: April 2, 2015                               Huawei Technologies
                                                      September 29, 2014

   Supporting Explicit Inclusion or Exclusion of Abstract Nodes for a
 Subset of P2MP Destinations in Path Computation Element Communication
                            Protocol (PCEP).
              draft-dhody-pce-pcep-p2mp-per-destination-07

Abstract

   The ability to determine paths of point-to-multipoint (P2MP)
   Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
   Traffic Engineering Label Switched Paths (TE LSPs) is one the key
   requirements for Path Computation Element (PCE).  The RFC 6006 and
   RFC 7334 describes these mechanisms for intra and inter domain path
   computation via PCE(s).

   This document describes the motivation and PCEP extension for
   explicitly specifying abstract nodes for inclusion or exclusion for a
   subset of destinations during P2MP path computation via PCE(s).

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 April 2, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Dhody, et al.             Expires April 2, 2015                 [Page 1]
Internet-Draft       EXPLICIT-INC-EXC-ABSTRACT-NODES      September 2014

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Domain Sequence Tree in Inter Domain P2MP Path
           Computation . . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.1.  PCE-sequence  . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Explicit inclusion or exclusion of abstract nodes . . . .   5
   4.  Detailed Description  . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Objective . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Request Message Format  . . . . . . . . . . . . . . . . .   6
     4.3.  Backward Compatibility  . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Manageability Considerations  . . . . . . . . . . . . . . . .   8
     7.1.  Control of Function and Policy  . . . . . . . . . . . . .   8
     7.2.  Information and Data Models . . . . . . . . . . . . . . .   8
     7.3.  Liveness Detection and Monitoring . . . . . . . . . . . .   8
     7.4.  Verify Correct Operations . . . . . . . . . . . . . . . .   8
     7.5.  Requirements On Other Protocols . . . . . . . . . . . . .   9
     7.6.  Impact On Network Operations  . . . . . . . . . . . . . .   9
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The PCE architecture is defined in [RFC4655].  [RFC5862] lay out the
   requirements for PCEP to support P2MP path computation.  [RFC6006]
   describe an extension to PCEP to compute optimal constrained intra-

[include full document text]