Conveying Vendor-Specific Constraints in the Path Computation Element Protocol
draft-ietf-pce-vendor-constraints-06

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2012-07-08
Replaces draft-farrel-pce-vendor-constraints
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       Fatai Zhang 
Internet-Draft                                                   Huawei 
Intended status: Standards Track                              A. Farrel 
                                                     Old Dog Consulting 
                                                           G. Bernstein 
                                                      Grotto Networking 
Expires: January 9, 2013                                   July 9, 2012 
                                      

                                    
            Conveying Vendor-Specific Constraints in the Path 
                      Computation Element Protocol 
                                      
                 draft-ietf-pce-vendor-constraints-06.txt 

Status of this Memo 

   This Internet-Draft is submitted to IETF in full conformance with   
   the provisions of BCP 78 and BCP 79. 

   Internet-Drafts are working documents of the Internet Engineering   
   Task Force (IETF), its areas, and its working groups.  Note that   
   other groups may also distribute working documents as Internet-   
   Drafts. 

   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." 

   The list of current Internet-Drafts can be accessed at   
   http://www.ietf.org/ietf/1id-abstracts.txt. 

   The list of Internet-Draft Shadow Directories can be accessed at   
   http://www.ietf.org/shadow.html. 

   This Internet-Draft will expire on January 9, 2013. 

    

Abstract 

   The Path Computation Element Protocol (PCEP) is used to convey path 
   computation requests and responses between Path Computation Clients 
   (PCCs) and Path Computation Elements (PCEs), and also between 
 
 
 
Farrel & Zhang           Expires January 2013                  [Page 1] 


draft-ietf-pce-vendor-constraints-06.txt                      July 2012 
    

   cooperating PCEs. In PCEP the path computation requests carry 
   details of the constraints and objective functions that the PCC 
   wishes the PCE to apply in its computation.  

   The mechanisms defined for indicating objective functions include 
   the capability to convey vendor-specific objective functions. This 
   document defines a facility to carry vendor-specific constraints in 
   PCEP.  

Conventions used in this document 

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC-2119 [RFC2119]. 

Table of Contents 

    
   1. Introduction ................................................ .2 
   2. Procedures .................................................. .4 
   3. Protocol Elements ........................................... .6 
   4. IANA Considerations ......................................... .7 
   5. Management Considerations  .................................. .7 
      5.1. Control of Function and Policy ......................... .8 
      5.2. Information and Data Models............................. .8 
      5.3. Liveness Detection and Monitoring ...................... .8 
      5.4. Verifying Correct Operation.............................. 8 
      5.5. Requirements on Other Protocols and Functional Components 8 
      5.6. Impact on Network Operation.............................. 9 
   6. Security Considerations ...................................... 9 
   7. References ................................................... 9 
      7.1. Normative References .................................... 9 
      7.2. Informative References  ................................. 10 
   8. Acknowledgements ............................................. 11 
   9. Authors' Addresses ........................................... 11 
    
    

1. Introduction 

   A Path Computation Element (PCE) is an entity (component, 
   application or network node) that is capable of computing a network 
   path or route based on a network graph and applying computational 
   constraints. An architecture for the use of PCEs is defined in 
   [RFC4655]. 

 
 
Farrel & Zhang           Expires January 2013                  [Page 2] 


draft-ietf-pce-vendor-constraints-06.txt                      July 2012 
    

   The Path Computation Element Protocol (PCEP) is defined in [RFC5440] 
   to exchange path computation requests and responses between Path 
   Computation Clients (PCCs) and PCEs. It is also used between 
   cooperating PCEs. 

   Path computations performed by a PCE depend on a set of constraints 
Show full document text