pwe3-6----Page:1
1
|
T-MPLS Forwarding component using RFC3031, RFC3032,etc. PHP switched off, no merging, no ECMP support Label space per-platform/interface with downstream label assignment context-specific with upstream label assignment for P2MP T-MPLS not only Ethernet PW over a MPLS PSN Ethernet PW – current standard Proposals to add support of ATM, FR clients etc. as per PWE3 WG RFCs Interoperability with IP/MPLS Using Ethernet – current standard Proposal for MPLS level Proposal for PW (multi-segment) level OAM different from IETF (no IP forwarding = LS) T-MPLS OAM identified using label 14 assigned by IETF to ITU-T Protection – data plane driven only (based on T-MPLS OAM) Control plane Option to work without control plane (label distribution) – current std Work starting for T-MPLS CP On-going work is a good opportunity to have ITU-T and IETF cooperating each other |