RFC 8231, "Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE", September 2017Source of RFC: pce (rtg)
Errata ID: 5796
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Hillol
Date Reported: 2019-07-29
Held for Document Update by: Deborah Brungard
Date Held: 2020-07-13
Section 7.3.3 says:
Value Description ----- ------------------------------------- 1 Unknown reason 2 Limit reached for PCE-controlled LSPs 3 Too many pending LSP Update Requests 4 Unacceptable parameters 5 Internal error 6 LSP administratively brought down 7 LSP preempted 8 RSVP signaling error
It should say:
Remove Value 2 2 Limit reached for PCE-controlled LSPs
Value 2 "Limit reached for PCE-controlled LSPs" can occur when an PC update message comes for either PCInitiated or PCDelegated LSP. But since the lsp is already created or delegated, it means the resource is available and allocated. Also RFC 8281 (section 5.3) states that if LSP provisioned exceeds the limit, an LSP error message should be sent with Error-type=19 (Invalid Operation) and
Error-value=6 (PCE-initiated LSP limit reached). So, I believe there is no scenario where LSP Error code TLV "Limit reached for PCE-controlled LSPs" would be used.
Please let me know if there is some scenario which can trigger the same.