{
  "draft": "draft-ietf-pce-vendor-constraints-11",
  "doc_id": "RFC7150",
  "title": "Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol",
  "authors": [
    "F. Zhang",
    "A. Farrel"
  ],
  "format": [
    "TEXT",
    "HTML"
  ],
  "page_count": "12",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Path Computation Element",
  "abstract": "The Path Computation Element Communication Protocol (PCEP) is used to convey path computation requests and responses both between Path Computation Clients (PCCs) and Path Computation Elements (PCEs) and between 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.\n\n This document defines a facility to carry vendor-specific information in PCEP using a dedicated object and a new Type-Length-Variable that can be carried in any existing PCEP object.",
  "pub_date": "March 2014",
  "keywords": [],
  "obsoletes": [],
  "obsoleted_by": [
    "RFC7470"
  ],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC7150",
  "errata_url": null
}