datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
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-04

Active Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2013-04-15
Intended RFC status: (None)
Other versions: plain text, xml, pdf, html

Document shepherd:(None)
Shepherd writeup

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: October 18, 2013                  Huawei Technologies India Pvt
                                                                     Ltd
                                                          April 16, 2013

   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-04

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).  [RFC6006] and
   [PCE-P2MP-PROCEDURES] describes these mechanisms for intra and inter
   domain path computation via PCE.

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

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 October 18, 2013.

Copyright Notice

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

Dhody, et al.           Expires October 18, 2013                [Page 1]
Internet-Draft       EXPLICIT-INC-EXC-ABSTRACT-NODES          April 2013

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

Dhody, et al.           Expires October 18, 2013                [Page 2]
Internet-Draft       EXPLICIT-INC-EXC-ABSTRACT-NODES          April 2013