Page th IETF Vancouver, B.C., Canada Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with GMPLS Greg Bernstein Grotto Authors: D. Caviglia (Ericsson), R. Rabbat (Google), H. van Helvoort (Huawei). Contributors: Wataru Imajuku (NTT), Julien Meuric (France Telecom), Lyndon Ong (Ciena). draft-ietf-ccamp-gmpls-vcat-lcas-04.txt

Page th IETF Vancouver, B.C., Canada Status Changes from 03 text: –Added requirements on pre-existing members. –Slightly modified solution for member sharing to constrain calls to a maximum of one VCG. –Introduced the CALL_DATA object. –Detailed coding of new TLV for VCAT to be included in the CALL_DATA object. –Modified and expanded procedures to deal with new requirements and modified solution methodology. –Added a list of error conditions.

Page th IETF Vancouver, B.C., Canada Added Requirements Section 3.4 VCGs and VCG Members –VCG members (server layer connections) may be set up prior to their use in a VCG. –VCG members (server layer connections) may exist after their corresponding VCG has been removed. –The signaling solution SHOULD provide a mechanism to support the previous scenarios. However, it is not required that arbitrarily created server layer connections be supported in the above scenarios.

Page th IETF Vancouver, B.C., Canada Modified Call Based Solution VCG Call information –Signal type –Number of VCG members –LCAS requirement –VCG Identifier Used to identify a particular VCG separately from the call ID so that call members can be reused with different VCGs per the requirements for member sharing and the requirements of section 3.4. VCG Calls are now restricted to applying to only one VCG at a time.

Page th IETF Vancouver, B.C., Canada Procedures (multiple co-signaled case) Setting up a VCAT call and VCG –Single call & VCG, multiple LSPs Setting up a VCAT call + LSPs with no VCG –Allows pre-establishment of LSPs prior to VCG, also used in member sharing Associating an existing VCAT call with a VCG –Allows pre-establishment of LSPs prior to VCG, also used in member sharing Removing the association between a call and VCG –Allows LSPs to exist after VCG is removed, also used in member sharing

Page th IETF Vancouver, B.C., Canada Call Data Object –In RFC4974 the general mechanism for communicating call information via notify messages is given. In general different types of calls will need to convey call related information during call establishment and updates. We define a general CALL_DATA object for inclusion in call related notify messages and define a specific class type (C- Type) for VCAT calls.

Page th IETF Vancouver, B.C., Canada VCAT TLV Previous Information –Signal Type, Number of Members, LCAS req New information –VCG ID –Action: Indicates the association (if any) of the VCG ID with the call. 0 = None, 1 = new VCG ID for call, 2 = no change in VCG ID, 3 = remove VCG from call | Signal Type | Number of Members | | LCAS Req | Action | VCG ID |

Page th IETF Vancouver, B.C., Canada Error codes VCG signal type not Supported1 LCAS option not supported2 Max number of VCGs exceeded3 Max number of VCG members exceeded4 LSP Type incompatible with VCAT call5

Page th IETF Vancouver, B.C., Canada Next Steps Verify the protocol details, engage implementers Polish up the document Continue liaisons with OIF and ITU