Presentation on theme: "Segment Protection Scaling Bob Sultan Deng Zhusheng."— Presentation transcript:
Segment Protection Scaling Bob Sultan (firstname.lastname@example.org) Deng Zhusheng
TESI Segment Protection Requirement PBB-TE supports end-to-end TESI protection Requirement to protect a TESI ‘segment’ See Vinod Kumar Service Provider Requirements AL K J H G F C B D
TESI Segment Protection Segment endpoints are MEPs CCM detects connectivity state of W/P Switch achieved by FDB update at endpoints Simple scheme based on existing 802.1ag End-to-end TESI protection/CCM as usual AL K J H G F C B D
Segment Protection Scaling Issue Many TESIs can use same set of links for W/P Requires W/P CCMs per TESI segment Can be scaling problem in some cases AL K J H G F C B D
Scaling Segment Protection with ‘Cycle’ Observe that W+P segments always form a cycle Observe that many paths may use the same cycle Replace CCM per segment (many) with one fault notification per cycle Please note: this use of the word ‘cycle’ has absolutely nothing to do with ‘p-cycles’. A cycle is just a closed loop of links. AL K J H G F C B D cycle X
Summary We support CCM-based segment protection We propose cycle-based notification for scaling purposes for cases in which many segments use the same cycle (cycle is provisioned) Notification mechanism could re-use G.8032 or ring/cycle mechanism developed in 802.1 (see Norm Finn proposal).