1 / 19

GMPLS Control of Ethernet Forwarding

GMPLS Control of Ethernet Forwarding. Don Fedyk dwfedyk@nortel.com Loa Andersson loa@pi.se. References. draft-fedyk-gmpls-ethernet-pbb-te-00.txt draft-andersson-gels-exp-rsvp-te-01.txt Draft-fedyk tracking IEEE Data Plane Adds TE to a PBB network Draft-andersson

lacey-allison
Download Presentation

GMPLS Control of Ethernet Forwarding

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. GMPLS Control of Ethernet Forwarding Don Fedyk dwfedyk@nortel.com Loa Andersson loa@pi.se IETF68 CCAMP

  2. References • draft-fedyk-gmpls-ethernet-pbb-te-00.txt • draft-andersson-gels-exp-rsvp-te-01.txt • Draft-fedyk • tracking IEEE Data Plane • Adds TE to a PBB network • Draft-andersson • experimental implementation • Uses GMPLS for all modes of connection types • Multiple label types IETF68 CCAMP

  3. Background • GMPLS Control of Ethernet Forwarding (GELS) concluded that before we adapt GMPLS to Ethernet bridging we need an IEEE compliant data plane. • One data plane that is emerging is Provider Backbone Bridges Traffic Engineering (IEEE802.1Qay). • The Acreo implementation references only IEEE802.1Q standard • Other IEEE Ethernet Switching paradigms may be defined in the future. • IEEE802.1Qay is what we initially propose to control remaining flexible for other paradigms. IETF68 CCAMP

  4. Conventional Ethernet Bridging Management Plane Provisioning (Policy, etc) Provisioning (Components) OAM Bi-directional Data Plane Ethernet Control Plane Spanning Tree, Learning, Filtering Strong Correlation between MP & DP or DP & CP IETF68 CCAMP

  5. Configured Ethernet Bridging Management Plane Provisioning (Components) OAM Bi-directional Data Plane Remove CP dependency IETF68 CCAMP

  6. GMPLS control of Ethernet Forwarding Management Plane Provisioning (Components) Provisioning (Connections) OAM Bi-directional Data Plane IP Control Plane GMPLS SignalingGMPLS Routing GMPLS Signaling What we want to do is add GMPLS IETF68 CCAMP

  7. GELS Motives • Automates Configuration of Ethernet bridging • Improvement in the coordination required to establish and maintain an ETH-LSP • Provides Automatic reaction to network changes • Dynamic connections for P2P TE and P2MP TE • May be Ships-in-the-night mode with Ethernet Control Plane • Helps interwork Configured Ethernet services with MPLS services • Helps interwork with GMPLS enabled Optical Networks • Enables Inter-layer signaling capability IETF68 CCAMP

  8. GMPLS Components • Signaling • GMPLS with extensions for Ethernet Bridging • IP Control plane • Limited IP functionality for control plane only • Routing • Maintain IP control plane and TE information • LMP • Extends the 802.1AB capability • Path Computation • On-net/off-net path computations GMPLS Requirements: Small delta from existing GMPLS specifications IETF68 CCAMP

  9. GELS Axioms • Native Labels properties • Bidirectional fate shared data plane • Bandwidth reservation • Symmetric, Asymmetric • Fully Exploits the Ethernet Data Plane • VID configuration • MAC + VID configuration IETF68 CCAMP

  10. Types of LSPs • P2P • MP2P • P2MP • MP2MP • Some terminology differences between the drafts (to be sorted out) IETF68 CCAMP

  11. Proposed Generalized Label Request • Encoding Type Ethernet • LSP Switching Type Specific to Switching Paradigm • GPID set to Unknown IETF68 CCAMP

  12. Traffic Parameters • The traffic parameters (T-spec) defined in draft-ietf-ccamp-ethernet-traffic-parameters-01.txtis a good starting point IETF68 CCAMP

  13. Where is Configured Ethernet applicable ? Backbone Core Bridge (BCB) Backbone Edge Bridge (BEB) A native Ethernet TE Technology Ethernet MAN Encapsulation keep C-MAC learning to BEBs that are directly attached to the Ethernet CE device. Scales Carrier Ethernet Metro networks. IETF68 CCAMP

  14. MPLS enabled Access device S-PE MPLS WAN Ethernet MAN Pure Ethernet devices Where is Configured Ethernet applicable ? As an native Ethernet Aggregation technology IETF68 CCAMP

  15. Three Layer GMPLS Network IETF68 CCAMP

  16. What do we need to add to GMPLS? • Code Points for Switching Paradigm • Label Encoding per Switching Type • Allow non Label-swapped LSPs • Coding procedures for the technology • Rules for Labels • Rules for Protection Overall Not a Lot IETF68 CCAMP

  17. Next step • Add a milestone to the working charter to develop a Experimental GELS specification • Add a milestone to the working groups charter to develop a specification of the generic aspects of GELS signaling and routing IETF68 CCAMP

  18. Backup IETF68 CCAMP

  19. 802.1 ah (PBB) Header 1 2 3 4 2 Backbone Destination Address (B-DMAC) 6 Backbone Source Address (B-SMAC) 10 .1ad Ethertype 14 .1ad B-TAG TCI/VID .1ah Ethertype 18 .1ah I-TAG TCI/SID 22 Destination Address (C-DMAC) 26 30 Source Address (C-SMAC) 34 Encap Ethertype IETF68 CCAMP

More Related