View
216
Download
3
Category
Preview:
Citation preview
PB & PBB models / 2006-10-10
Page 1
802.1ad Provider & Provider Edge Bridges
S-VLAN
1
C-VLAN
C-VLAN
CNP
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
port basedsrvc i/f
C-taggedsrvc i/f
C-taggedsrvc i/f
S-taggedsrvc i/f
Provider Edge BridgeCustomer Systems
1
1
1
1
n
n
n
n
n
n
1|n
1|n
1|n
1|n
S-VLAN
PNP
PNP
PNP
PNP
PNP
PNP
Provider Bridge
n
n
nn
n
n
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
PB & PBB models / 2006-10-10
Page 2
802.1ad Provider & Provider Edge BridgesS-VLAN MEP & MIP function locations
S-VLANComp.
C-VLAN
C-VLAN
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
CNP
port basedsrvc i/f
C-taggedsrvc i/f
C-taggedsrvc i/f
S-taggedsrvc i/f
Provider Edge BridgeCustomer Systems
1
1
1
1
n
n
n
n
n
n
1|n
1|n
1|n
1|n
S-VLAN
PNP
PNP
PNP
PNP
PNP
PNP
Provider Bridge
n
n
nn
n
n
S-VLAN instance end pointwith S-VLAN MEP function
S-VLAN instance interm. pointwith S-VLAN MIP function
S-VLAN instance interm. pointwith S-VLAN-MIP & S-VLAN-MEP functions
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
1
PB & PBB models / 2006-10-10
Page 3
802.1ah Backbone Edge & Core Bridges
I-SIComp.
PBBS-VLAN
PBBC-VLAN
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
nCNP
port basedsrvc i/f
S-taggedsrvc i/f
C-taggedsrvc i/f
I-taggedsrvc i/f
Backbone Edge BridgeCustomer Systems
1
1
1
1
1
1|n
1|n
1|n
n
n
1|n
1|n
1|n
1|n
B(S)-VLANComp.
1CNP
CNP
CNP
CNP
VIP
VIP
VIP
1
1
n
n
n
n
Customer MACaddress domain
Backbone MACaddress domain
Backbone-MACService Boundary
Backbone-MAC ClientBackbone-MAC Provider
n
to/from peerPBBN BEB
N/C
CNP
B(S)-VLAN
PNP
PNP
PNP
PNP
PNP
PNP
Provider Bridge &Backbone Core Bridge
n
n
nn
n
n
I-taggedpeer PBBN i/f
B(S)-taggedi/f
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
PB & PBB models / 2006-10-10
Page 4
802.1ah Backbone Edge & Core BridgesI-SI and B(S)-VLAN MEP & MIP function locations
I-SIComp.
PBBS-VLAN
PBBC-VLAN
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
nCNP
port basedsrvc i/f
S-taggedsrvc i/f
C-taggedsrvc i/f
I-taggedsrvc i/f
Backbone Edge BridgeCustomer Systems
1
1
1
1
1
1|n
1|n
1|n
n
n
1|n
1|n
1|n
1|n
B(S)-VLANComp.
1CNP
CNP
CNP
CNP
VIP
VIP
VIP
1
1
n
n
n
n
Backbone-MACService Boundary
n
to/from peerPBBN BEB
N/C
CNP
B(S)-VLAN
PNP
PNP
PNP
PNP
PNP
PNP
Provider Bridge &Backbone Core Bridge
n
n
nn
n
n
I-taggedpeer PBBN i/f
B(S)-taggedi/f
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
Service Instance end pointwith SI-MEP function(s)
B(S)-VLAN instance end pointwith B(S)-VLAN MEP function
B(S)-VLAN instance interm. pointwith B(S)-VLAN MIP function
Srvc Instance interm. pointwith SI-MIP function
Srvc Instance interm. pointwith SI-MIP & SI-MEP functions
PB & PBB models / 2006-10-10
Page 5
Hybrid 802.1ah/MPLS Backbone Edge Bridge & MPLS Backbone Core Switch
(H)VPLS combines MPLS PW (i.e. service instance) and Tunnel layers with an Ethernet Service Instance layerTo scale HVPLS the Ethernet Service Instance layer should be thePBB Service Instance layerPBB and MPLS Backbone Edge Bridges have same architecture
main difference are– B-VLAN component is replaced by MPLS Tunnel component – I-SID and PCP/DE are replaced by MPLS PW label and EXP I.e. I-SI
component translates in its VIP* port its Relay VID into PW label (instead into I-SID)
– B-VID and PCP/DE are replaced by MPLS Tunnel label and EXP
PB & PBB models / 2006-10-10
Page 6
Hybrid 802.1ah/MPLS Backbone Edge Bridge & MPLS Backbone Core Switch
I-SIComp.
PBBS-VLAN
PBBC-VLAN
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
nCNP
port basedsrvc i/f
S-taggedsrvc i/f
C-taggedsrvc i/f
I-taggedsrvc i/f
MPLS Backbone Edge BridgeCustomer Systems
1
1
1
1
1
1|n
1|n
1|n
n
n
1|n
1|n
1|n
1|n
MPLSTunnelComp.
1CNP
CNP
CNP
CNP
VIP*
VIP*
VIP*
1
1
n
n
n
n
Customer MACaddress domain
Backbone MACaddress domain
Backbone-MACService Boundary
Backbone-MAC ClientBackbone-MAC Provider
n
to/from peerPBBN BEB
N/C
CNP
MPLSTunnel
PNP
PNP
PNP
PNP
PNP
PNP
MPLSBackbone Core Switch
n
n
nn
n
n
I-taggedpeer PBBN i/f
B(S)-taggedi/f
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
PB & PBB models / 2006-10-10
Page 7
Hybrid 802.1ah/MPLS Backbone Edge Bridge & MPLS Backbone Core Switch
I-SIComp.
PBBS-VLAN
PBBC-VLAN
CNP
CNP
CNP
CNP
CNP
PNP
PNP
PNP
PEP
PEP
PEP
PEP
CEP
CEP
nCNP
port basedsrvc i/f
S-taggedsrvc i/f
C-taggedsrvc i/f
I-taggedsrvc i/f
MPLS Backbone Edge BridgeCustomer Systems
1
1
1
1
1
1|n
1|n
1|n
n
n
1|n
1|n
1|n
1|n
MPLSTunnelComp.
1CNP
CNP
CNP
CNP
VIP
VIP
VIP
1
1
n
n
n
n
Backbone-MACService Boundary
n
to/from peerPBBN BEB
N/C
CNP
MPLSTunnel
PNP
PNP
PNP
PNP
PNP
PNP
MPLSBackbone Core Switch
n
n
nn
n
n
I-taggedpeer PBBN i/f
B(S)-taggedi/f
N/C
1|n bundling/multiplexing n client entities into 1 server entity
1 single instance/entities port n n instance/entities port
Service Instance end pointwith SI-MEP function(s)
Tunnel instance end pointwith Tunnel MEP function
Tunnel instance interm. pointwith Tunnel MIP function
Srvc Instance interm. pointwith SI-MIP function
Srvc Instance interm. pointwith SI-MIP & SI-MEP functions
PB & PBB models / 2006-10-10
Page 8
PBB provides B-MAC Services
MAC Service Boundary
B-MAC Service Boundary
B-MAC Service Boundary
PBB Network
Ethernet/PB Network
PBB Network
PB & PBB models / 2006-10-10
Page 9
Customer Instance Service Instance (PBB S-VLAN) Component
Proposed new “PBB S-VLAN Component” maps “Customer Instances” onto “Service Instances”PBB Service Instances provide B-MAC Service to customerPBB S-VLAN Component’s PEPs include B-MAC SAPs and “ISS SAP into B-MAC SAP mapping”
ISS SAP B-MAC SAP mapping process to be defined in new clause 6.x (refer to slide 11)
802.1ad’s Relay VID (RVID) should be used as generic ISS SAP identifier
associated with both B-VLAN (trunk) instances and I-Service instancesVID translation function converts bridge-internal RVID into externally observable C-VID, S-VID, B-VID, I-SID, or other technology label format
PB & PBB models / 2006-10-10
Page 10
6.x (see next slide)
2/802.3 or 6.1/802.1D8.5.2/802.1Q
Customer Instance Service Instance Component
8.5.1 8.5.1
4k Relay
B-MAC SAPs ( ) …..…… ( )
EISS SAPs ( ) …… ( ) (
) E
ISS SAP
ISS SAPs ( ) ... ( ) ( ) ..……… ( ) ( ) ( ) ( ) ISS SAPs
MAC SAPs ( ) … ( )
6.7(b)
6.5
( ) ISS SAP
8.5.2 8.5.26.7(b)
( ) ( ) MAC SAPs
ISS SAPs ( ) ..……… ( )
802.3
EISS (ISS SAPs ( ) ..……… ( ))
PBB S-VLAN Component
M(A)_(UNIT)DATA.request (DA,MSDU,P,DE)M(A)_(UNIT)DATA.indication (DA,SA,MSDU,P,DE)
optional ISS SAP ( )
802.1ag Down MPs
EISS (ISS SAPs ( ) ..……… ( ))
Each ISS SAP instance is identified by means of a Relay VID (RVID, 6.7/802.1ad)
PB & PBB models / 2006-10-10
Page 11
New clause 6.x/ 802.1ah
DA SA MSD
UFC
S
DA SA MSD
UFC
SR
S
MA_DATA.indication
MA_DATA.request
( )D
A SA MSD
UP D
A SA MSD
UP
M_UNITDATA.indication
M_UNITDATA.request
( )ISSSAP FC
S
FCS
ME
MO
DA SA MSD
UP D
A SA MSD
UP
MA-UNITDATA.indication
MA-UNITDATA.request
( )MACSAP
DA SA MSD
UP D
A SA MSD
UP
M_UNITDATA.indication
M_UNITDATA.request
( )ISSSAP FC
S
FCS
ME
MO
EType Etype? EType Etype?
Alternative A: 6.1/802.1D Alternative B: 2.3/802.3
Learning& Aging
mcast mcast
Configuration
ucast
Learning& Aging
Configuration
ucastucast Table ucast Table
mcast Table mcast Table
Missing parameters MA_DATA: P & DEMissing parameter MA-UNITDATA: DE
PB & PBB models / 2006-10-10
Page 12
Resources
Following slides present considerations on resources in the bridge
fabric unitinterface port unit
and illustrate on which resources customer instancesservice instancestrunk instances andphysical link instances
start/end
PB & PBB models / 2006-10-10
Page 13
Resources
Functional model of PEB, PB, BEB, BCB must be mapped onto Resource model, consisting of
Fabric UnitsInterface Port Units
Fabric unit supportsBridge Relay Entity
Typical Relay Port bandwidths: 1G, 2.5G, 10G, 40G (and in the future: 100G) Interface Port unit may support
Physical Media (PHY)Multiplexing/Demultiplexing ((DE)MUX)MEP and MIP functions (OAM)Mapping/Demapping ((DE)MAP) including bundling
Two types of equipment (ignoring service definition relays)Single Relay: PEB, PB, BCB, I-BEB, B-BEBDual Relay: IB-BEB
PB & PBB models / 2006-10-10
Page 14
ResourcesSingle Relay equipment
I/FPortUnit
Fabric Unit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
USER/CUSTOMER SIDE
NETWORK SIDE
multiplexing of one or more Customer Instances into one or more Service/Trunk Instances
termination of one or more Service/Trunk Instances
Service/Trunk Instance grooming & switching/bridging
multiplexing of one or more Service/Trunk Instances into one or more PHY Instances
termination of one or more PHY InstancesServ
ice/
Trun
k In
stan
ce
PHY
Inst
ance
Server Side
Client Side
Cus
tom
er In
stan
ce
PB & PBB models / 2006-10-10
Page 15
ResourcesDual Relay equipment
I/FPortUnit
Fabric Unit (Service Instance)
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
USER/CUSTOMER SIDE
NETWORK SIDE
I/FPortUnit
Fabric Unit (Trunk Instance)
I/FPortUnit
I/FPortUnit
I/FPortUnit
I/FPortUnit
bundling of one or more Customer Instances into one or more Service Instances
termination of one or more Service Instances
Serv
ice
Inst
ance
Service Instance grooming & switching/bridging
multiplexing of one or more Service Instances into one or more Trunk Instances
termination of one or more Trunk Instances
Trunk Instance grooming & switching/bridging
multiplexing of one or more Trunk Instances into one or more PHY Instances
termination of one or more PHY Instances
Trun
k In
stan
ce
PHY
Inst
ance
Server Side
Client Side
Server Side
Client Side
Cus
tom
er In
stan
ce
PB & PBB models / 2006-10-10
Page 16
Relay Resources
4k Relay
Port 0
Port k
Server Side
Client Side
Port 1 Port 2 Port k-1
Port k+1 Port n
16M Relay
Port 0
Port k
Server Side
Client Side
Port 1 Port 2 Port k-1
Port k+1 Port n
Two Relay types in 802.14k relay (≤ 4094 instances)16M relay (≤ 16,777,214 instances)
4k Relay (802.1Q, .1ad, .1ah)12-bit Relay VID (R12VID)0 ≤ R12VID ≤ 4094
16M Relay (802.1ah)24-bit Relay VID (R24VID)0 ≤ R24VID ≤ 16,777,215
Relay PortsContain one or more Instance PortsInstance Port identified by RVID
a b zInstance Port identified
by a RVID value
Relay Port
Relay Port
PB & PBB models / 2006-10-10
Page 17
Interface Port Resources
to be added
PB & PBB models / 2006-10-10
Page 18
Relay VID Translation
Relay VID (RVID)bridge internal instance identifier
External presentation asC-VIDS-VID/B-VIDI-SIDPW label (PW)Time slot (TS)…
RVID translation functionC-VID=RVID, RVID=C-VIDS-VID =f[RVID], RVID = f-1[S-VID]I-SID = f[RVID], RVID = f-1[I-SID]PW = f[RVID], RVID = f-1[PW]TS = f[RVID], RVID = f-1[TS]
Relay
Port 0
Port k
Server Side
Client Side
Port 1 Port 2 Port k-1
Port k+1 Port n
a b zInstance Port identified
by a RVID value
a b z
A B Z
(DE)MUX
Externally observableInstance identifier
a
A
C-VIDS-VIDI-SIDPWTS
RVI
Da
A
PB & PBB models / 2006-10-10
Page 19
EISS SAP
EISS SAP represents a set of “client-ISS SAPs”each client-ISS SAP is identified by its VID (to be replaced by RVID)
It seems that when deploying RVID in 802.1ah, current EISS SAP definitions can be maintained without extensions
PB & PBB models / 2006-10-10
Page 20
IEEE 802.1Q-2005EISS SAP represents set of client ISS SAPs
EISS SAP may support between 1 and 4094 Client-ISS SAPsD
A SA MSD
UP D
A SA MSD
UPFC
S
ME
MO
FCS
( )EISS SAPClient
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )
( )
ClientISS SAP{VID=A}
DA SA MSD
UP D
A SA MSD
UPFC
S
ME
MO
FCS
( )
ClientISS SAP{VID=Z}
DA SA MSD
UP D
A SA MSD
UP
EM_UNITDATA.indicationEM_UNITDATA.request
( )EISS SAP FCS
VID
ME
MO
VID
FCS
M_UNITDATA.indication
M_UNITDATA.request
M_UNITDATA.indication
M_UNITDATA.request
PB & PBB models / 2006-10-10
Page 21
IEEE 802.1ad-2005EISS SAP represents set of client ISS SAPs
EISS SAP may support between 1 and 4094 Client-ISS SAPsD
A SA MSD
UP D
A SA MSD
UPFC
SM
EM
O
FCS
( )EISS SAPClient
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )
( )
ClientISS SAP{VID=A}
ClientISS SAP{VID=Z}
M_UNITDATA.indication
M_UNITDATA.request
M_UNITDATA.indication
M_UNITDATA.request
DA SA MSD
UP D
A SA MSD
UP
EM_UNITDATA.indicationEM_UNITDATA.request
( )EISS SAP FCS
VID
ME
MO
VID
FCS
DE
DE
DE
DE
DA SA MSD
UP D
A SA MSD
UPFC
SM
EM
O
FCS
( )
DE
DE
Note: ISS SAP (6.4/802.1Q) should get drop_eligibility
PB & PBB models / 2006-10-10
Page 22
p802.1ahEISS SAP represents set of client ISS SAPs
Trunk Instances: EISS SAP may support between 1 and 4094 Client-ISS SAPsService Instances: EISS SAP may support between 1 and 16777214 Client-ISS SAPs
DA SA MSD
UP D
A SA MSD
UPFC
SM
EM
O
FCS
( )EISS SAPClient
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )Client
ISS SAP( )
( )
ClientISS SAP{RVID=A}
ClientISS SAP{RVID=Z}
M_UNITDATA.indication
M_UNITDATA.request
M_UNITDATA.indication
M_UNITDATA.request
DA SA MSD
UP D
A SA MSD
UP
EM_UNITDATA.indicationEM_UNITDATA.request
( )EISS SAP FCS
RVI
D
ME
MO
RVI
D
FCS
DE
DE
DE
DE
DA SA MSD
UP D
A SA MSD
UPFC
SM
EM
O
FCS
( )
DE
DE
Note: ISS SAP (6.4/802.1Q) should get drop_eligibility
Recommended