CCAMP WG Meeting IETF 58 - Minneapolis - Nov’03 GMPLS-based Recovery draft-ietf-ccamp-gmpls-recovery-terminology-02.txt draft-ietf-ccamp-gmpls-recovery-analysis-02.txt draft-ietf-ccamp-gmpls-recovery-functional-01.txt draft-lang-ccamp-gmpls-recovery-e2e-signaling-02.txt CCAMP WG Meeting IETF 58 - Minneapolis - Nov’03

Thanks… Deborah Brungard (dbrungard@att.com) Sudheer Dharanikota (sudheer@ieee.org) Jonathan Lang (jplang@ieee.org) Guangzhi Li (gli@att.com) Eric Mannie (eric_mannie@hotmail.com) Dimitri Papadimitriou (dimitri.papadimitriou@alcatel.be) Bala Rajagopalan (braja@tellium.com) Yakov Rekhter (yakov@juniper.net) … and also ccamp’ers (mailing list)

Effort Positioning, Status and Timing… Terminology draft-ietf-ccamp-gmpls-recovery-terminology-02.txt March’02 March’02 (closed) ~ PS for July’03 (closed) Analysis draft-ietf-ccamp-gmpls-recovery-analysis-02.txt April’02 Jan’03 (closed) ~ Info for June’03 (closed) Functional Specification draft-ietf-ccamp-gmpls-recovery-functional-01.txt July’02 Jan’03 (closed) ~ PS for April’03 (closed) Aug’02 GMPLS RSVP-TE Specification draft-lang-ccamp-gmpls-recovery-e2e-signalling-02 Mar’03 (closed) ~ PS for July’03 (tbd)

Mechanisms covered by the Signaling I-d Recovery Scope: end-2-end Coverage: (failure detection => sd or sf) LSP Protection: full LSP signalling (cross-connection) b/f failure occurrence (Pre-planned) Re-routing(w/ shared re-routing as particular case): pre-signalling b/f failure + LSP activation after failure - allows for low priority LSP Dynamic Re-routing (a.k.a restoration): full LSP signalling after failure occurrence Notification message (and objects) <= from RFC 3473 Two objects described: Protection Object (C-Type 2) <= extends RFC 3473 Primary Path Route Object (New object): shared recovery

Issues on e2e signaling I-d Editorial revision (thanks to the reviewers) P-bit processing at edge-points (backward compatibility) PPR object (PPRO) detailed processing is addressed in v02.txt Precision added since does not to cover M:N end-to-end LSP protection w/ or w/o extra-traffic - note: signaling mechanisms applicable to 1:N protection w/ extra-traffic

Extra-Traffic LSP issue Advertisement: To make bandwidth pre-reserved for protecting (not activate) LSP(s) available for extra-traffic => this bandwidth may be included in the Unreserved Bandwidth sub-TLV at priority lower than the protecting LSP Setup Priority Note: Max LSP Bandwidth in Interface Switching Capability Descriptor sub-TLV should reflect that bandwidth pre-reserved for protecting LSP(s) is available for extra-traffic Signaling: LSPs for extra traffic established using bandwidth pre-reserved for protecting LSP(s) by setting SESSION_ ATTRIBUTE Setup Priority = X (Setup Priority of the protecting LSP) Holding Priority = at least to X+1 Note: if resources pre-reserved for the protecting LSP are used by lower priority LSPs, these LSPs MUST be preempted when the protecting LSP is activated

Functional Specification GMPLS RSVP-TE Specification What is the Next Step ? Commit the Signaling I-d as a WG document Perform thorough revision of the document(s) Dec’03 submit documents to IESG Terminology draft-ietf-ccamp-gmpls-recovery-terminology-02.txt Analysis draft-ietf-ccamp-gmpls-recovery-analysis-02.txt Functional Specification draft-ietf-ccamp-gmpls-recovery-functional-01.txt GMPLS RSVP-TE Specification 3q’03 (first phase closed)