1. GELS Report Loa & Dimitri

2. Problem Statement GMPLS controlled Ethernet GMPLS control plane for Ethernet.1ad environment (with S-VID support) Single operator environment Base objectives: Source routing Traffic engineering (P2P and P2MP TE LSPs) Recovery

3. GELS Approach Like CCAMP for SONET/SDH leave data plane untouched => no impact on the Ethernet data plane and define GMPLS-based control plane

4. GELS Approach Differences b/w SONET/SDH and Ethernet approach Technology Ethernet: frame forwarding SONET/SDH: circuit switched Label Ethernet label: “encoded” in data plane and distributed using control plane SONET/SDH: label control plane only (timeslot) Maturity Ethernet: evolution in parallel with // Ethernet evolutions at IEEE SONET/SDH: foundation (~80-90) present ten years before starting GMPLS work (~00)

5. Status Active mailing list (200+ subscriptions) Active DT discussion (unofficial meetings + social) Carrier involvement and interest Slowly converging on “What needs to be done”!

6. Status Problem Statement Label encoding GMPLS impact GMPLS controlled Ethernet unify CP operations (source routing, TE) 1. Domain-wide label: DA MAC+S-VID (IVL fwd’ing) 2. Link-local label: S-VID translation (swapping) Signaling and related Routing and related Framework doc. draft-dimitri-gels-framework-00.txt Decoder Ring doc. To be completed Re-spin ongoing

7. Status Problem Statement Label encoding Common (profiles) Common (are we solving the same problem ?) Different solutions to the same problem 12 or GMPLS control 12 …

8. Approach Complete GMPLS CP impact Label scheme (domain vs link local) impact on GMPLS protocols’ operations Signaling: RSVP-TE Routing: IGP (IS-IS, OSPF) Alignment OK: we’re done (common trunk w/ profile) NOK: see how far we can go (from initial objectives)

9. Next Steps (documents) Re-spin Carrier requirement Framework Decoder Ring complete GMPLS control plane impact