GMPLS Control of Ethernet PBB-TE

Download Report

Transcript GMPLS Control of Ethernet PBB-TE

GMPLS Control of
Ethernet Forwarding
Don Fedyk [email protected]
Loa Andersson [email protected]
IETF68 CCAMP
1
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
2
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
3
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
4
Configured Ethernet Bridging
Management Plane
Provisioning
(Components)
OAM
Bi-directional Data Plane
Remove CP dependency
IETF68 CCAMP
5
GMPLS control of Ethernet
Forwarding
Management Plane
Provisioning
(Components)
Provisioning
(Connections)
OAM
Bi-directional Data Plane
GMPLS Signaling
IP Control Plane
GMPLS Signaling
GMPLS Routing
What we want to do is add GMPLS
IETF68 CCAMP
6
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
7
GMPLS Components

Signaling


IP Control plane


Maintain IP control plane and TE information
LMP


Limited IP functionality for control plane only
Routing


GMPLS with extensions for Ethernet Bridging
Extends the 802.1AB capability
Path Computation

On-net/off-net path computations
GMPLS Requirements: Small delta from existing GMPLS specifications
IETF68 CCAMP
8
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
9
Types of LSPs





P2P
MP2P
P2MP
MP2MP
Some terminology differences between
the drafts (to be sorted out)
IETF68 CCAMP
10
Proposed Generalized Label
Request



Encoding Type Ethernet
LSP Switching Type Specific to
Switching Paradigm
GPID set to Unknown
IETF68 CCAMP
11
Traffic Parameters

The traffic parameters (T-spec) defined
in
draft-ietf-ccamp-ethernet-trafficparameters-01.txt
is a good starting point
IETF68 CCAMP
12
Where is Configured Ethernet
applicable ?
Backbone
Edge Bridge
(BEB)
A native
Ethernet
TE
Technology
Backbone
Core Bridge
(BCB)
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
13
Where is Configured Ethernet
applicable ?
MPLS enabled
Access device
S-PE
MPLS
WAN
Ethernet
MAN
Pure
Ethernet
devices
As an native Ethernet Aggregation technology
IETF68 CCAMP
14
L2SC NE
SwitchCore
OSPF-TE
RSVP-TE
Router NE
Three Layer GMPLS Network
OSPF-TE
RSVP-TE
Dragon/Linux PC
Dragon/Linux PC
OSPF-TE
RSVP-TE
Dragon/Linux PC
OSPF-TE
RSVP-TE
OSPF-TE
RSVP-TE
Dragon/Linux PC
Router NE
Dragon/Linux PC
OSPF-TE
RSVP-TE
Dragon/Linux PC
SwitchCore
OSPF-TE
RSVP-TE
Dragon/Linux PC
SwitchCore
L2SC NE
L2SC NE
Router NE
L2SC NE
SwitchCore
Router NE
OSPF-TE
RSVP-TE
Dragon/Linux PC
L2SC NE
Router NE
SwitchCore
OSPF-TE
RSVP-TE
Dragon/Linux PC
IETF68 CCAMP
OSPF-TE
RSVP-TE
Dragon/Linux PC
15
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
16
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
17
Backup
IETF68 CCAMP
18
802.1 ah (PBB) Header
1
2
3
2
Backbone Destination Address (B-DMAC)
6
Backbone Source Address (B-SMAC)
10
14
18
22
4
.1ad Ethertype
.1ad B-TAG TCI/VID
.1ah Ethertype
.1ah I-TAG TCI/SID
Destination Address (C-DMAC)
26
30
34
Source Address (C-SMAC)
Encap Ethertype
IETF68 CCAMP
19