Requirements for the Conversion Between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network Internet Draft Diego Caviglia - Ericsson Dino Bramanti - Ericsson Dan Li – Huawei Technologies

Traditional Transport Network Control trough Network Management System NMS Client A Client B TNE 1 TNE 2 TNE 3 TNE 4 TNE 5 TNE 6 Generic Transport Links Transport Links w/ resources statically allocated to client A-client B circuit NMS-TNE Control Communication Transport connections over data plane are managed by NMS acting on each of the relevant TNEs No Control Plane is in place, all resources are owned by Management Plane

Transport Network Control trough Management and Control Plane Management Plane A pool of transport resources are managed by NMS acting directly on each of the relevant TNEs Another pool of data plane resources are managed trough a distributed - GMPLS based - Control Plane Client A Client B TNE 1 TNE 2 TNE 3 TNE 4 TNE 5 TNE 6 Generic Transport Links Transport resources statically allocated by NMS NMS-TNE Control Communication Transport resources dynamically allocated trough Control Plane Control Plane (Routing+Signaling) entities Control Plane

Management Plane Transport/Data Plane Transport resources ownership means that related data records describing transport circuits reside within the owning entity Management Plane and Control Plane relationship Control Plane Both control entities (MP and CP) own only their partition of networks resources and can only setup/tear down their own circuits

PC to SC Conversion There are mainly two possible scenarios: The CP is at initial stage of deployment and thus all the network connections are already set up as PCs and are owned by the Management Plane; A network is partially controlled by the Management Plane and partially controlled by the Control Plane (PCs and SCs coexist), and an upgrade or coverage extension of the Control Plane is required. SC to PC Conversion An example of a scenario where the "SPC to PC" procedure may be used is when a Control Plane failure happens in a certain area of the network, and the ability of the Control Plane to control the connections is partially lost. In such a case, according to the configured policy at each node, the Data Plane connections which are owned by the Control Plane could be smoothly switched over to Management Plane. Typical Use Cases

Requirements 1.Data Plane LSP Consistency 2.No Disruption of User Traffic 3.Transfer from Management Plane to Control Plane 4.Transfer from Control Plane to Management 5.Synchronization of state among nodes during migration 6.Support of Soft Permanent Connections 7.Failure of Transfer 8.Backward Compatibility 9.Re-Use of Protocol Mechanisms

Comments on the List and request The ID has received positive comments from some of the major carrier. Comments from other guys have been addressed in the this (01) version of the ID Latest comments from Dimitri and Adrian will be addressed in the 02 version that is ready to be posted. Seems that the 02 version address all the comments received from the list so far. Proposal go out with the 02 and move it to WG document.