1 / 9

GELS Report

This report addresses the problem statement of GMPLS controlled Ethernet, aiming to streamline control plane operations such as source routing and traffic engineering in a single operator environment. It proposes a GELS approach to control Ethernet without affecting the data plane. Contrasts between SONET/SDH and Ethernet approaches are discussed, focusing on label encoding and maturity aspects. The current status includes active mailing lists, discussions, and carrier involvement in defining the framework. The document outlines domain-wide and link-local label encoding for Ethernet, signaling, and routing impacts to be completed in ongoing work. Next steps involve respinning, aligning GMPLS protocols, and finalizing the control plane impact analysis.

rlonnie
Download Presentation

GELS Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  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 • <draft-dimitri-gels-framework-00.txt> • Decoder Ring • <draft-dimitri-gels-solution-eval-00.txt> • complete GMPLS control plane impact

More Related