1 / 10

Extensions to PCEP for Backup Ingress and Egress of LSP

Extensions to PCEP for Backup Ingress and Egress of LSP. draft-chen-pce-compute-backup-ingress-00 draft-chen-pce-compute-backup-egress-00. Huaimo Chen ( huaimochen @huawei.com ). P2MP LSP Ingress & Egress Local Protection. Multicast Receiver.

dreama
Download Presentation

Extensions to PCEP for Backup Ingress and Egress of LSP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extensions to PCEP for Backup Ingress and Egress of LSP draft-chen-pce-compute-backup-ingress-00 draft-chen-pce-compute-backup-egress-00 Huaimo Chen (huaimochen@huawei.com) 79th IETF @ Beijing

  2. P2MP LSP Ingress & Egress Local Protection Multicast Receiver Existing scenario:double ingress and every egress Create two global P2MP LSP from each ingress to egresses, carrying data at same time BFD P2MP PE1 Multicast Source Data CE1 CE1 (S,G)Join PE2 PE5 CE3 Backup Egress Node CE4 PE6 PE3 Data CE2 External Source Node Backup Ingress Node PE4 External Destination Node One P2MP LSP for all: Every part locally protected Big resource saving, Faster failure recovery P2MP LSP 79th IETF @ Beijing Backup LSP

  3. Overview • Backup Ingress & Egress Capability Advertisement • Capability TLV in PCE Discovery • Open Message Extension • Request and Reply Message Extension • RP Object Extension • External Source Node Object • External Destination Nodes Object 79th IETF @ Beijing

  4. Capability TLV in PCE Discovery Type (5) Length (4) Capability Flags • Two flags for backup ingress: one bit for backup ingress of P2MP LSP, another for backup of P2P LSP bit 11 Backup ingress computation for P2MP LSP • Backup ingress computation for P2P LSP • Two flags for backup egress 13 Backup egress computation for P2MP LSP 14 Backup egress computation for P2P LSP 79th IETF @ Beijing

  5. Open Message Extension • A new optional TLV: Type (8) Length (4) • Two flags for backup ingress: one bit for backup ingress of P2MP LSP, another for backup of P2P LSP bit 0 Backup ingress computation for P2MP LSP • Backup ingress computation for P2P LSP • Two flags for backup egress 2 Backup egress computation for P2MP LSP 3 Backup egress computation for P2P LSP Capability Flags 79th IETF @ Beijing

  6. RP Object Extension • RP Object Body: Flags I N I (backup Ingress) bit is added in flags: 0: Not PCReq/PCRep for backup ingress 1: PCReq/PCRep for backup ingress I withN: I=1& N=1: PCReq/PCRep for backup ingress of P2MP LSP I=1 & N=0: PCReq/PCRep for backup ingress of P2P LSP Request ID number Optional TLVs 79th IETF @ Beijing

  7. RP Object Extension - cont • RP Object Body: Flags T N T (backup Egress/Tail) bit is added in flags: 0: Not PCReq/PCRep for backup egress 1: PCReq/PCRep for backup egress T withN: T=1& N=1: PCReq/PCRep for backup egress of P2MP LSP T=1 & N=0: PCReq/PCRep for backup egress of P2P LSP Request ID number Optional TLVs 79th IETF @ Beijing

  8. External Source Node (ESN) Object • ESN Object Body (object-type 1 for IPv4) External source node IPv4 address (4 bytes) • ESN Object Body (object-type 2 for IPv6) IPv6 address (16 bytes) IPv6 address (continued) IPv6 address (continued) IPv6 address (continued) 79th IETF @ Beijing

  9. External Destination Nodes (EDN) Object • EDN Object body (object-type 1) for IPv4 Encode of External Destination Nodes (2) Egress IPv4 address External Destination IPv4 address Egress IPv4 address External Destination IPv4 address …… Egress IPv4 address External Destination IPv4 address 79th IETF @ Beijing

  10. Next Step • Welcome comments • Request to make it into a working group document 79th IETF @ Beijing

More Related