Hi Mrinmoy,
On Mon, Jul 3, 2023 at 2:34 PM Mrinmoy Das <[email protected]> wrote: > Hello Team, > > Could anybody please clarify my doubt? > > Thanks & Regards, > Mrinmoy > > On Fri, Jun 30, 2023 at 3:22 PM Mrinmoy Das <[email protected]> > wrote: > >> Hello Team, >> >> I found below highlighted text in RFC 8231: >> >> *6.2 <https://datatracker.ietf.org/doc/html/rfc8231#section-6.2>. The PCUpd >> Message, page- 29* >> >> >> >> The PCC SHOULD minimize the traffic interruption and MAY use the >> >> make-before-break procedures described in [RFC3209 >> <https://datatracker.ietf.org/doc/html/rfc3209>] in order to >> >> achieve this goal. If the make-before-break procedures are used, two >> >> paths will briefly coexist. The PCC MUST send separate PCRpt >> >> messages for each, identified by the LSP-IDENTIFIERS TLV. When the >> >> old path is torn down after the head end switches over the traffic, >> >> this event MUST be reported by sending a PCRpt message with the >> >> LSP-IDENTIFIERS-TLV of the old path and the R bit set. The >> >> SRP-ID-number that the PCC associates with this PCRpt MUST be >> >> 0x00000000. Thus, a make-before-break operation will typically >> >> result in at least two PCRpt messages, one for the new path and one >> >> for the removal of the old path (more messages may be possible if >> >> intermediate states are reported). >> >> >> So, as per the highlighted text above, *in case of MBB, the 2nd >> PCRpt(old path) that is torn down needs to set SRP-ID to 0.* >> Does this behavior apply to both RSVP-TE and SR-TE LSP? >> >> If the make-before-break technique is being used, then yes the procedure from RFC 8231 applies. The PCRpt that signifies "break" is considered unsolicited and thus SRP-ID is 0x0. Unless explicitly told, this should apply to all path setup types. Note that MBB is not mandatory. Thanks! Dhruv > Thanks & Regards, >> Mrinmoy >> > _______________________________________________ > Pce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/pce >
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
