How are BSIDs used to reduce MSD?
Reducing MSD with BSIDs
The NSP supports draft-ietf-pce-binding-label-sid for the advertisement of binding segment identifiers (BSIDs) for both PCC-initiated and PCE-initiated SR-TE LSPs in order to avoid exceeding their maximum stack depth (MSD). If and how this is accomplished is determined by the configuration of the path profile policy associated with a given LSP. See Path profile policy parameters for more information.
The NSP is able to discover LSPs with pre-existing BSIDs, and can use these BSIDs when attempting to reduce MSD. Alternatively, BSIDs can be created during either PCE-initiated LSP creation, or SR policy creation. See How do I create PCE-initiated LSPs? or How do I create an SR policy? for more information.
The NSP is also capable of auto-generating BSIDs of either type (PCEP LSP or BGP SR policy) when the configuration of a path profile policy indicates that they are required but none are available. Whether or not BSIDs can be auto-generated - and which type will be auto-generated - is specified via API. Visit the Network Developer Portal for more information.
© 2024 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.