Escolar Documentos
Profissional Documentos
Cultura Documentos
Wes Doonan
OFC/NFOEC March 2012
ORD
LAX
ATL
DIA PHX
DFW
O-PCE
P-PCE
Layering Concept
Client layer network
= client connection
Purpose: Abstraction
Purpose: Adaptation
Represent server layer network capabilities in client layer network
Example: expose a lambda connection as a link in a packet topology
Purpose: Activation
Coordination activation of capabilities across layers, domains
Example: server layer connection activated during client layer signaling
= client connection
= virtual link
Workflow
1. Plan Connectivity
Real or Virtual?
R
Enough Topology?
Y
Enough Topology?
Y
PCE
Links Creation
Purpose: Identify potential or dedicated connectivity
Optical domain to provide connectivity across domain
Dedicated: DFW->ORD Potential: 2 x LAX->DFW, LAX->ORD Connections provisioned in optical domain, resources activated, etc Links advertised to packet domain, paths computed in optical domain Optical domain resources not activated until client link is used
Packet TEDB
ORD LAX
DIA
ATL
PHX
DFW
= Packet
= Optical
2012 ADVA Optical Networking. All rights reserved.
ORD LAX
DIA
ATL
PHX
DFW
= Packet
= Optical
2012 ADVA Optical Networking. All rights reserved.
Packet TEDB
P-PCE
ORD LAX
DIA
ATL
PHX
DFW
= Packet
= Optical
2012 ADVA Optical Networking. All rights reserved.
GMPLS Overlay
Mechanism for building multi-technology overlay networks
Uses existing technologies as building blocks
Multi-Layer operation Virtual Links, Virtual Nodes, Virtual Topologies PCEs paired with domains and/or layers Allows definition of policies at domain/layer boundaries
What path should a connection take in a server network? How should clients be notified of server network activation? Etc ...
Packet TEDB
UNI
ORD
UNI
LAX DIA
UNI
ATL
PHX
DFW
= Packet
= Optical
UNI
UNI
10
GMPLS Overlay
GMPLS User to Network Interface
Interoperable service activation across layers and domains
Defines the overlay network model, concepts Outlines multiple scenarios, options, mechanisms Initially issued in 2005, considerable experience since then Presents "best current practice" profile of RFC4208 Derived from specific experiences, lessons learned
Multi-layer activation, use of virtual topologies Label signaling across technologies Coordinating administrative status Routing updates to support virtual nodes Handling of generic constraints
Origin: RFC4208
Update: draft-beeram-ccamp-gmpls-uni-bcp
11
Fate Sharing
Virtual Links must reflect diversity of server network
Different approaches
Sharing
Client Layer
12
Client network will need to know if switching constraints exist Outlines mechanism for advertising constraints between links
Informs PCEs which links can be cross-connected at a node Client network PCEs take as input to constraint calculations
draft-ietf-ccamp-general-constraint-encode
{ A x B; A ! C; A x D } A
D 13
2012 ADVA Optical Networking. All rights reserved.
Summary
Multi-layer, multi-domain networks are a Reality
Packet + Optical, other network technology mixes
UNI
ORD
UNI
LAX DIA
UNI
ATL
PHX
DFW
UNI 14
UNI
Thank you
wdoonan@advaoptical.com
IMPORTANT NOTICE The content of this presentation is strictly confidential. ADVA Optical Networking is the exclusive owner or licensee of the content, material, and information in this presentation. Any reproduction, publication or reprint, in whole or in part, is strictly prohibited. The information in this presentation may not be accurate, complete or up to date, and is provided without warranties or representations of any kind, either express or implied. ADVA Optical Networking shall not be responsible for and disclaims any liability for any loss or damages, including without limitation, direct, indirect, incidental, consequential and special damages, alleged to have been caused by or in connection with using and/or relying on the information contained in this presentation.
Copyright for the entire content of this presentation: ADVA Optical Networking.