{"draft":"draft-ietf-pce-binding-label-sid-16","doc_id":"RFC9604","title":"Carrying Binding Label\/SID in PCE-Based Networks","authors":["S. Sivabalan","C. Filsfils","J. Tantsura","S. Previdi","C. Li, Ed."],"format":["HTML","TEXT","PDF","XML"],"page_count":"19","pub_status":"PROPOSED STANDARD","status":"PROPOSED STANDARD","source":"Path Computation Element","abstract":"In order to provide greater scalability, network confidentiality, and\r\nservice independence, Segment Routing (SR) utilizes a Binding Segment\r\nIdentifier (BSID), as described in RFC 8402. It is possible to\r\nassociate a BSID to an RSVP-TE-signaled Traffic Engineering (TE)\r\nLabel Switched Path (LSP) or an SR TE path. The BSID can be used by\r\nan upstream node for steering traffic into the appropriate TE path to\r\nenforce SR policies. This document specifies the concept of binding\r\nvalue, which can be either an MPLS label or a Segment Identifier\r\n(SID). It further specifies an extension to Path Computation Element\r\nCommunication Protocol (PCEP) for reporting the binding value by a\r\nPath Computation Client (PCC) to the Path Computation Element (PCE)\r\nto support PCE-based TE policies.","pub_date":"August 2024","keywords":[],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":["RFC9756"],"see_also":[],"doi":"10.17487\/RFC9604","errata_url":null}