RSVP-TE Extensions to Realize Dynamic Binding of Associated Bidirectional LSP CCAMP/MPLS WG, IETF 79th, Beijing, China draft-zhang-mpls-tp-rsvpte-ext-associated-lsp-01 Fei Zhang (editor) Fan Yang ZTE Corporation

Changes from Version 00  Keep in parallel with the document [ccamp-assoc-info]  Upstream initialized association (the association is base on Path state) Tunnel ID LSP ID Tunnel sender address  Association (peer mode) is deleted  Increasing the blocking probability to setup associated bidirectional LSP successfully (the ingress nodes do not know which tunnel/LSP ID is practicable in the fields of egress nodes) Associated bidirectional LSP

Changes from Version 00  Add one section to address the association of asymmetric bandwidth LSPs  Requirements: 14 MPLS-TP MUST support bidirectional transport paths with asymmetric bandwidth requirements, i.e., the amount of reserved bandwidth differs between the forward and backward directions [RFC5654]. Bidirectional transport paths include co-routed and associated bidirectional LSPs.  Scenarios: 1.Internet service, the bandwidths of upstream and downstream direction are different. 2.The return path of OAM message which needs smaller bandwidths compared to the forward direction.  Operations: 1.UPSTREAM_TSPEC object (defined in RFC5467) MUST be carried in the initializing LSP’s Path message to trigger the egress node to setup the reverse LSP with corresponding asymmetric bandwidth. 2. Association object MUST be treated in the same rules

Next Steps  Solicit feedback and comments from the WG  Adopted as a WG document