internet2 network tutorial:
DESCRIPTION
Control Plane and Dynamic Services. Internet2 Network Tutorial:. Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN. Collaborations with Other Networks High Level Overview: What are we trying to do? - PowerPoint PPT PresentationTRANSCRIPT
Internet2 Network Tutorial:
Rick Summerhill, Matt Zekauskas, Russ HobbyInternet2
Joint TechsUniversity of Minnesota
11 February 2007Minneapolis, MN
Control Plane and Dynamic Services
Control Plane Deployment
• Collaborations with Other Networks• High Level Overview:
• What are we trying to do?• Review of Higher Level Objectives
• HOPI Testbed Overview• Deployment on the Internet2 Network• The DRAGON GMPLS Control Plane
Collaboration with Other Networks
• Working closely with Dante, Canarie, and ESnet on Inter-domain Interoperability
• Meetings in December and January, to continue in May
• Much ongoing work to utilize existing technologies• Will meet in May after TERENA 2007
• Also participating in the OGF working groups to insure standards compatibility
• For example, integrate existing topology disccovery efforts
Overview
• Support Applications that demand capabilities that are hard to support in a shared packet infrastructure
• Large bandwidth applications• Applications that benefit from circuit characteristics, and that may be
low bandwidth in nature
• Dynamically create data paths that look like circuits, often called ”lightpaths”
• Russ Hobby will talk more about this
• Networks taking different approaches:• ESnet is taking an MPLS over Ethernet approach• Internet2 (HOPI) taking an Ethernet VLAN approach• Internet2 (Ciena) taking a SONET approach• GEANT is taking a SONET approach
HOPI Testbed Overview
• Nodes located in 5 major cities on the Internet2 DWDM platform
• Dynamically create VLANS across the infrastructure• Completely independent of the DWDM infrasturcture• Likely to become more experimental as services are
migrated to the Internet2 Network• Discussions about a completely new approach at this
meeting• Overview of Control Plane Ideas:
Development Team for DCS
• Team created to bring dynamic services to the Internet2 Network using the Ciena Platform
• Tom Lehman - lead• Jerry Sobieski• Xi Yang• Chris Tracy• Jarda Flidr• Additional developer to be named later
• Develop services over the next two years incorporating the entire network
• Workshops in preparation, more later
Overview of Basic Control Plane Ideas
• Intra-domain• Inter-domain• Basic Ideas:
• Topology• Path Computation• Signaling
• Additional components• Scheduling• AAA
Client “Service” View
User Identification (certificate)Source AddressDestination AddressBandwidth (50 Mbps increments)VLAN TAG (None | Any | Number)Schedule
Client A
Client B
Service Request
CSA
CSA
Ethernet Mapped SONET or
SONET Circuits
Dynamically Provisioned Dedicated Resource Path (“Circuit”)
Internet2 DCS
Domain Controller
1
b
a
2CSA can run on the client or in a separate machine (proxy mode)
Intra-Domain
Internet2 DCS Ethernet Mapped SONET or SONET Circuits
User Identification (certificate)Source AddressDestination AddressBandwidth (50 Mbps increments)VLAN TAG (None | Any | Number)Schedule
Client A
Client B
Service Request
Switch Fabric
VLSR
CSA
CSA
1 b
a
2
Domain Controller
RON Dynamic Infrastructure Ethernet VLAN
RON Dynamic Infrastructure Ethernet VLAN
Internet2 DCS Ethernet Mapped SONET
CSA
CSA
Domain Controller
Domain Controller
Domain Controller
Inter-DomainInter-Domain
DRAGON Control Plane
Status and Adaptation to Internet2 Network
Slides bySlides by
Tom LehmanTom LehmanUniversity of Southern California
Information Sciences Institute (USC ISI)
And
Others from the Development Team
Topics
DRAGON Control Plane StatusDRAGON Control Plane StatusThoughts/Considerations regarding Thoughts/Considerations regarding
Evolution to Internet2 Control PlaneEvolution to Internet2 Control PlaneAdvanced Topics: Web Services, Advanced Topics: Web Services,
AAA, SchedulingAAA, SchedulingNext Steps and TimelinesNext Steps and Timelines
DRAGON Control PlaneKey Components
Network Aware Resource Broker – Network Aware Resource Broker – NARBNARB Intradomain listener, Path Computation, Interdomain RoutingIntradomain listener, Path Computation, Interdomain Routing
Virtual Label Swapping Router – Virtual Label Swapping Router – VLSRVLSR Open source protocols running on PC act as GMPLS network Open source protocols running on PC act as GMPLS network
element (OSPF-TE, RSVP-TE)element (OSPF-TE, RSVP-TE) Control PCs participate in protocol exchanges and provisions Control PCs participate in protocol exchanges and provisions
covered switch according to protocol events (PATH setup, PATH covered switch according to protocol events (PATH setup, PATH tear down, state query, etc) tear down, state query, etc)
Client System Agent – Client System Agent – CSACSA End system or client software for signaling into network (UNI or End system or client software for signaling into network (UNI or
peer mode)peer mode) Application Specific Topology Builder – Application Specific Topology Builder – ASTBASTB
User Interface and processing which build topologies on behalf User Interface and processing which build topologies on behalf of usersof users
Topologies are a user specific configuration of multiple LSPsTopologies are a user specific configuration of multiple LSPs
Multi-Domain Control PlaneThe (near-term) big picture
RONRON
Internet2 Network
ESNet
Dynamic Ethernet Dynamic EthernetTDM
GEANT
IP Network (MPLS, L2VPN)
Ethernet
Router
SONET Switch
Ctrl Element
Domain Controller
LSP
Data Plane
Control Plane Adjacency
Multi-Domain ProvisioningMulti-Domain Provisioning Interdomain ENNI (Web Service and OIF/GMPLS)Interdomain ENNI (Web Service and OIF/GMPLS) Multi-domain, multi-stage path computation processMulti-domain, multi-stage path computation process AAAAAA SchedulingScheduling
DRAGON/HOPI Control Plane Provisioning Environment
GMPLS Multi-layer, Multi-DomainGMPLS Multi-layer, Multi-Domain Ethernet Service ProvisioningEthernet Service Provisioning Dynamic dedicated VLAN based Dynamic dedicated VLAN based
connectionsconnections
Ethernet Layer
Switched WDM Optical Layer
DRAGONMulti-Layer GMPLS Network
HOPIDynamic Ethernet Network
Domain Boundary
GMPLS Provisioned LSP Dedicated Ethernet VLAN “Circuit”
GWU CLPK
LA
SEADC
CHI
Static Optical Layer
MCLNARLG DCNE
NY
HOUEthernet Layer
ENNI
IGP-TE IGP-TE
UNIUNI
Heterogeneous Network Technologies
Complex End to End Paths
End Syste
m
AS 1AS 2 AS 3
VLSR
Ethernet SegmentVLSR Established VLAN
Ethernet over WDM
Ethernet over SONET
End Syste
m
Ethernet SegmentVLSR Established VLAN
VLSR
Router MPLS LSP
IP Control Plane
IP Control Plane
IP Control Plane
Ethernet
Router
Lambda Switch
SONET Switch
“horizontal” multi-layer adaptations for multi-domain
DRAGON Control Plane Interoperation with Ciena Domain
Three OptionsThree Options All have one NARB per Ciena Domain, receives topology information All have one NARB per Ciena Domain, receives topology information
from Ciena Domain (ENNI, CORBA, static configuration ?)from Ciena Domain (ENNI, CORBA, static configuration ?) GMPLSGMPLS
One VLSR per Core Director; front end for signalingOne VLSR per Core Director; front end for signaling Handles AAA, any special purpose configuration not handled by current Handles AAA, any special purpose configuration not handled by current
GMPLS protocols (edge VLAN mapping adjustment for instance), other GMPLS protocols (edge VLAN mapping adjustment for instance), other unique processing associated with peer entitiesunique processing associated with peer entities
GMPLS Wrapper over Management PlaneGMPLS Wrapper over Management Plane One VLSR per Core Director DomainOne VLSR per Core Director Domain Presents GMPLS to the outside world (probably as single opaque Presents GMPLS to the outside world (probably as single opaque
network with multiple external connections)network with multiple external connections) Use CORBA for Core Director ProvisioningUse CORBA for Core Director Provisioning
GMPLS Wrapper over Management Plane (Option 2)GMPLS Wrapper over Management Plane (Option 2) Same as above but use a “management style” system which talks to Same as above but use a “management style” system which talks to
Ciena Domain via UNI or ENNICiena Domain via UNI or ENNI
Ongoing Ciena Testing
Resource Partitioning. Can resources be partitioned such that Resource Partitioning. Can resources be partitioned such that control plane (OSRP) provisioned resources and manually control plane (OSRP) provisioned resources and manually (management system) can be isolated from each other? We (management system) can be isolated from each other? We believe this is possiblebelieve this is possible
Is it possible to police VLANS? Can each VLAN be policed and rate Is it possible to police VLANS? Can each VLAN be policed and rate limited independently? We believe this is also possible!limited independently? We believe this is also possible!
Looking forward to UNI2.0 and ENNI availabilityLooking forward to UNI2.0 and ENNI availability VCAT/LCAS interoperability with other vendors?VCAT/LCAS interoperability with other vendors? Will GFP encapsulated ethernet frames be interoperable with other Will GFP encapsulated ethernet frames be interoperable with other
vendors?vendors?
VLSR(Virtual Label Switching Router)
GMPLS ProxyGMPLS Proxy (OSPF-TE, RSVP-TE)(OSPF-TE, RSVP-TE)
Local control channelLocal control channel CLI,TL1, SNMP, othersCLI,TL1, SNMP, others
Used primarily for ethernet Used primarily for ethernet switchesswitches
Web page
XML Interface ASTB
CLI Interface One NARB per Domain
Provisioning Provisioning requests via CLI, requests via CLI, XML, or ASTBXML, or ASTB
VLSR(Virtual Label Switching Router)
RSVP Signaling moduleRSVP Signaling module Originated from Martin Karsten’s C++ KOM-RSVPOriginated from Martin Karsten’s C++ KOM-RSVP Extended to support RSVP-TE (RFC 3209)Extended to support RSVP-TE (RFC 3209) Extended to support GMPLS (RFC 3473)Extended to support GMPLS (RFC 3473) Extended to support Q-Bridge MIB (RFC 2674)Extended to support Q-Bridge MIB (RFC 2674) For manipulation of VLANs via SNMP (cross-connect)For manipulation of VLANs via SNMP (cross-connect) Extended to support VLAN control through CLIExtended to support VLAN control through CLI
OSPF Routing moduleOSPF Routing module Originated from GNU ZebraOriginated from GNU Zebra Extended to support OSPF-TE (RFC 3630)Extended to support OSPF-TE (RFC 3630) Extended to support GMPLS (RFC 4203)Extended to support GMPLS (RFC 4203)
Ethernet switches tested to dateEthernet switches tested to date Dell PowerConnect, Extreme, Intel, Raptor, Force10Dell PowerConnect, Extreme, Intel, Raptor, Force10
NARBNetwork Aware Resource Broker
Interdomain RoutingInterdomain Routing hierarchical link statehierarchical link state
Carries a modified TEDB that can support Carries a modified TEDB that can support AAAAAA SchedulingScheduling
Path Computation Element and ERO (loose and strict) generation Path Computation Element and ERO (loose and strict) generation
NARB
End Syste
m
NARB
NARB
End System
AS 1AS 2
AS 3
InterDomain Exchange
NARB(Network Aware Resource Broker)
NARB is an agent that represents a domainNARB is an agent that represents a domain Intra-domain ListenerIntra-domain Listener
Listens to OSPF-TE to acquire intra-domain topologyListens to OSPF-TE to acquire intra-domain topology Builds an abstracted view of internal domain topologyBuilds an abstracted view of internal domain topology
Inter-domain routingInter-domain routing Peers with NARBs in adjacent domainsPeers with NARBs in adjacent domains Exchanges (abstracted) topology informationExchanges (abstracted) topology information Maintains an inter-domain link state databaseMaintains an inter-domain link state database
Path ComputationPath Computation Performs intra-domain (strict hop) TE path computation Performs intra-domain (strict hop) TE path computation Performs inter-domain (loose hop) TE path computationPerforms inter-domain (loose hop) TE path computation Expands loose hop specified paths as requested by domain boundary (V)LSRs.Expands loose hop specified paths as requested by domain boundary (V)LSRs.
Hooks for incorporation of AAA and scheduling into path computation via a Hooks for incorporation of AAA and scheduling into path computation via a “3 Dimensional Resource Computation Engine (3D RCE)”“3 Dimensional Resource Computation Engine (3D RCE)” The Traffic Engineering DataBase (TEDB) and Constrained Shortest Path The Traffic Engineering DataBase (TEDB) and Constrained Shortest Path
Computation (CSPF) are extended to include dimensions of GMPLS TE Computation (CSPF) are extended to include dimensions of GMPLS TE parameters, AAA constraints, and Scheduling constraints.parameters, AAA constraints, and Scheduling constraints.
3D RCE is the combination of 3D TEDB and 3D CSPF3D RCE is the combination of 3D TEDB and 3D CSPF http://dragon.east.isi.edu/data/dragon/documents/dragon-infocom-APBM-http://dragon.east.isi.edu/data/dragon/documents/dragon-infocom-APBM-
workshop-apr282006.pdfworkshop-apr282006.pdf
What is the HOPI Service?
Physical Connection:Physical Connection: 1 or 10 Gigabit Ethernet1 or 10 Gigabit Ethernet
Circuit Service:Circuit Service: Point to Point Ethernet VLAN CircuitPoint to Point Ethernet VLAN Circuit Tagged or Untagged VLANs availableTagged or Untagged VLANs available Bandwidth provisioning available in 100 Mbps incrementsBandwidth provisioning available in 100 Mbps increments
How do Clients Request?How do Clients Request? Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST
Address, BandwidthAddress, Bandwidth Request mechanism options are GMPLS Peer Mode, GMPLS UNI Request mechanism options are GMPLS Peer Mode, GMPLS UNI
Mode, Web Services, phone call, emailMode, Web Services, phone call, email Application Specific Topology is a user specific instantiation of multiple Application Specific Topology is a user specific instantiation of multiple
individual circuitsindividual circuits What is the definition of a Client?What is the definition of a Client?
Anyone who connects to an ethernet port on an HOPI Force 10 Switch; Anyone who connects to an ethernet port on an HOPI Force 10 Switch; could be RONS, GIgaPops, other wide area networks, end systems could be RONS, GIgaPops, other wide area networks, end systems
GMPLS ProvisionedEthernet Services
Multiple Ethernet Provisioning OptionsMultiple Ethernet Provisioning Options Point to Point Ethernet VLAN based LSPsPoint to Point Ethernet VLAN based LSPs Ethernet switch (vendor specific) features applied to guarantee LSP Ethernet switch (vendor specific) features applied to guarantee LSP
bandwidth in increments of 100 Mbit/sbandwidth in increments of 100 Mbit/s Edge connection flexibility provided by use of “Local ID” feature which Edge connection flexibility provided by use of “Local ID” feature which
allows flexible combinations of one port, multiple ports, tagged ports, and allows flexible combinations of one port, multiple ports, tagged ports, and untagged ports to be glued on to end of LSP. Can be dynamically adjusted.untagged ports to be glued on to end of LSP. Can be dynamically adjusted.
Users can request services via Peer to Peer GMPLS, UNI style GMPLS, or Users can request services via Peer to Peer GMPLS, UNI style GMPLS, or via an XML application interfacevia an XML application interface
Ethernet VLAN space is “flat” across provisioned space. Constrained based Ethernet VLAN space is “flat” across provisioned space. Constrained based path computation utilized to find available VLAN Tags.path computation utilized to find available VLAN Tags.
VLAN tags treated in a similar manner to wavelengthsVLAN tags treated in a similar manner to wavelengths
“Local ID” for Egress Control
Ethernetswitch
VLSR PC
Ethernetswitch
VLSR PC Ethernetswitch
VLSR PC
Ethernetswitch
VLSR PC
Ethernetswitch
VLSR PCEthernetswitch
VLSR PCVLAN XX LSPVLAN YY LSP
User Requests: •Peer to Peer•UNI •XML API
Ethernet VLAN based Provisioning
Local ID defines the VLAN tag/edge port mappingLocal ID defines the VLAN tag/edge port mapping Several options; tagged, untagged, single port, port groups, automaticSeveral options; tagged, untagged, single port, port groups, automatic Local ID definitions can be adjusted dynamicallyLocal ID definitions can be adjusted dynamically
OSPFOSPF configure vlans on each interfaceconfigure vlans on each interface advertise out in IfSwCap Descriptor TLV inside a TE Link LSAadvertise out in IfSwCap Descriptor TLV inside a TE Link LSA update vlans availability and bandwidth in response to provisioningupdate vlans availability and bandwidth in response to provisioning similar to the existing ifswcap-specific-psc and ifswcap-specific-tdmsimilar to the existing ifswcap-specific-psc and ifswcap-specific-tdm
RSVP ERORSVP ERO proprietary Unnumbered Interface ID Subobjects (UnNumIfID) used to encode proprietary Unnumbered Interface ID Subobjects (UnNumIfID) used to encode
VLAN information in EROVLAN information in ERO 32-bit UnNumbered Interface ID: type(1byte):value(24bits, vlan tag info)32-bit UnNumbered Interface ID: type(1byte):value(24bits, vlan tag info)
NARB/RCENARB/RCE listen to OSPFlisten to OSPF path computation with bandwidth and vlan constraintspath computation with bandwidth and vlan constraints create EROs with UnNumIFID objectscreate EROs with UnNumIFID objects
Driven by need to provision across HOPI (10 gigabit interfaces)Driven by need to provision across HOPI (10 gigabit interfaces)
DRAGON Provisioning Web Page
Web Page Interface
Application Specific Topologies using XML
<topology> <topology> <resource> <resource>
<resource_type> eVLBI.Mark5a </resource_type> <resource_type> eVLBI.Mark5a </resource_type> <name> Haystack.muk1 </name> <name> Haystack.muk1 </name> <ip_addr> muk1.haystack.mit.edu </ip_addr> <ip_addr> muk1.haystack.mit.edu </ip_addr> <te_addr> muk1-ge0.haystack.mit.edu </te_addr><te_addr> muk1-ge0.haystack.mit.edu </te_addr><appl> /usr/local/evlbi_script </appl><appl> /usr/local/evlbi_script </appl>
</resource> </resource> <resource> <resource>
<resource_type> eVLBI.Mark5a </resource_type> <resource_type> eVLBI.Mark5a </resource_type> <name> Westford1 </name> <name> Westford1 </name> <ip_addr> wstf.haystack.mit.edu </ip_addr> <ip_addr> wstf.haystack.mit.edu </ip_addr> <te_addr> wstf-ge0.haystack.mit.edu </te_addr><te_addr> wstf-ge0.haystack.mit.edu </te_addr><appl> /usr/local/evlbi_script </appl><appl> /usr/local/evlbi_script </appl>
</resource> </resource> <resource> <resource>
<resource_type> EtherPipeBasic </resource_type> <resource_type> EtherPipeBasic </resource_type> <src> Haystack.muk1 </src> <src> Haystack.muk1 </src> <dest> Westford.muk1 </dest> <dest> Westford.muk1 </dest> <datarate> 1 Gbs </datarate><datarate> 1 Gbs </datarate>
</resource> </resource> </topology> </topology>
A BC
A
B
C
Application Specific Topologies
Live demonstration at Internet2 Spring Member Meeting (April 2006, Live demonstration at Internet2 Spring Member Meeting (April 2006, Washington DC)Washington DC) See www.internet2.edu for webcast of “HOPI update” presentation. See www.internet2.edu for webcast of “HOPI update” presentation.
Set up global multi-link topologies Set up global multi-link topologies ~30 seconds~30 seconds
Switched WDM Optical Layer
Provisioned Topologies
Internet2 Network: Infrastructure with Multiple Services
“ Routed IP Network”
“SONET Switched Network”
“Ethernet VLAN Switched Network (i.e., HOPI)”
Switched SONET Layer (vcat, lcas)
Ethernet Layer
Switched WDM Optical Layer
Switched SONET Layer (vcat, lcas)
Multi-Layer GMPLS Networks
Ethernet Layer
Router Layer
Separate (Peering) Control Plane Instantiations for each of the above
Dynamic Circuit Service
Physical Connection:Physical Connection: 1 or 10 Gigabit Ethernet1 or 10 Gigabit Ethernet OC-3, OC-12, OC-48, OC192 SONETOC-3, OC-12, OC-48, OC192 SONET
Circuit Service:Circuit Service: Point to Point Ethernet VLAN CircuitPoint to Point Ethernet VLAN Circuit Point to Point Ethernet Framed SONET CircuitPoint to Point Ethernet Framed SONET Circuit Point to Point SONET CircuitPoint to Point SONET Circuit Bandwidth provisioning available in 50 Mbps increments (STS-1 Bandwidth provisioning available in 50 Mbps increments (STS-1
granularity)granularity) How do Clients Request?How do Clients Request?
Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Address, BandwidthAddress, Bandwidth
Request mechanism options are GMPLS Peer Mode, GMPLS UNI Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, emailMode, Web Services, phone call, email
Application Specific Topology is a user specific instantiation of multiple Application Specific Topology is a user specific instantiation of multiple individual circuitsindividual circuits
What is the definition of a Client?What is the definition of a Client? A Device on the network requesting a circuit connectionA Device on the network requesting a circuit connection
Control Plane Objectives Multi-Service, Multi-Domain, Multi-Layer, Multi-Service, Multi-Domain, Multi-Layer,
Multi-Vendor ProvisioningMulti-Vendor Provisioning Basic capability is the provision of a “circuit” in Basic capability is the provision of a “circuit” in
above environmentabove environment In addition, need control plane features for:In addition, need control plane features for:
AAAAAA SchedulingScheduling Easy APIs which combine multiple individual Easy APIs which combine multiple individual
control plane actions into an application specific control plane actions into an application specific configuration (i.e., application specific configuration (i.e., application specific topologies)topologies)
Key Control Plane Features(for Connection Control)
RoutingRouting distribution of "data" between networks. The data that needs to distribution of "data" between networks. The data that needs to
be distributed includes reachability information, resource be distributed includes reachability information, resource usages, etc usages, etc
Path computationPath computation the processing of information received via routing data to the processing of information received via routing data to
determining how to provision an end-to-end path. This is determining how to provision an end-to-end path. This is typically a Constrained Shortest Path First (CSPF) type typically a Constrained Shortest Path First (CSPF) type algorithm for the GMPLS control planes. Web services based algorithm for the GMPLS control planes. Web services based exchanges might employ a modified version of this technique or exchanges might employ a modified version of this technique or something entirely different.something entirely different.
SignalingSignaling the exchange of messages to instantiate specific provisioning the exchange of messages to instantiate specific provisioning
requests based upon the above routing and path computation requests based upon the above routing and path computation functions. This is typically a RVSP-TE exchange for the GMPLS functions. This is typically a RVSP-TE exchange for the GMPLS control planes. Web services based exchanges might employ a control planes. Web services based exchanges might employ a modified version of this technique or something entirely different.modified version of this technique or something entirely different.
Key Control Plane Key Capabilities
Domain SummarizationDomain Summarization Ability to generate abstract representations of your domain for making Ability to generate abstract representations of your domain for making
available to othersavailable to others The type and amount of information (constraints) needed to be included The type and amount of information (constraints) needed to be included
in this abstraction requires discussion. in this abstraction requires discussion. Ability to quickly update this representation based on provisioning Ability to quickly update this representation based on provisioning
actions and other changes actions and other changes Multi-layer “Techniques”Multi-layer “Techniques”
Stitching: some network elements will need to map one layer into Stitching: some network elements will need to map one layer into others, i.e., multi-layer adaptationothers, i.e., multi-layer adaptation
In this context the layers are: PSC, L2SC, TDM, LSC, FSCIn this context the layers are: PSC, L2SC, TDM, LSC, FSC Hierarchical techniques. Provision a circuit at one layer, then treat it as a Hierarchical techniques. Provision a circuit at one layer, then treat it as a
resource at another layer. (i.e., Forward Adjacency concept)resource at another layer. (i.e., Forward Adjacency concept) Multi-Layer, Multi-Domain Path Computation AlgorithmsMulti-Layer, Multi-Domain Path Computation Algorithms
Algorithms which allow processing on network graphs with multiple Algorithms which allow processing on network graphs with multiple constraintsconstraints
Coordination between per domain Path Computation ElementsCoordination between per domain Path Computation Elements
Inter-Domain Topology Summarization
Full Topology
Semi-topo (edge nodes only)
Maximum Summarization
- User defined summarization level maintains privacy- Summarization impacts optimal path computation but allows the domain to choose (and reserve) an internal path
Integration Core Director Domain into the End-to-End Signaling
VLSR uni-subnet
CoreDirector CoreDirector
Ciena Subnet
LSRdownstream
LSRupstream
data flow signaling flow
subnet signaling flow
uni uni
CD_a CD_z
• Signaling is performed in contiguous mode.• Single RSVP signaling session (main session) for end-to-end circuit.• Subnet path is created via a separate RSVP-UNI session (subnet session),
similar to using SNMP/CLI to create VLAN on an Ethernet switch.
• The simplest case: one VLSR covers the whole UNI subnet.• VLSR is both the source and destination UNI clients.• This VLSR is control-plane ‘home VLSR’ for both CD_a and CD_z.• UNI client is implemented as embedded module using KOM-RSVP API.
I2 DCS Development Lab
Bloomington Indianapolis
LocalNetwork
LocalNetwork
Control PC (VLSR)
Client System
Control PC (VLSR)
Client System
routednetwork
An Example of How to Connect to HOPI and the Internet2 Network - Phase 1
• Campus connects through RON using static VLANs and deploys VLSR on PC connected to switch (GMPLS control plane)
• Ethernet based• Connect to HOPI control plane
Phase 2
• Add NARB (could be same PC)• Separates the campus domain from HOPI
domain• Now have separate control planes
Phase 3
• When ready, RON implements GMPLS control plane
Phase 4
• Move to the Multiservice Switching Infrastructure on the Internet2 Network
• There are many other possible alternatives
Workshops
• Two day workshop• Provide a working knowledge of how to
design and deploy a GMPLS based dynamic services network
• Overview of GMPLS architecture• RSVP and OSPF protocols
• Basic Control Plane Concepts• Routing, Path Computation, Signaling
Workshops, continued
• Hands-on workshop, attendees will:• Implement a dynamic services test-bed (Ethernet
based), using the DRAGON GMPLS Software Suite• Schedule:
• First day will focus on concepts and basic control plane design and implementation
• Second day will explore inter-domain dynamic services and provisioning
• Target Audience: Senior Network Engineers familiar with current R&E network infrastructure, IP architectures, and ethernet switching.
• See http://add this in
Additional Slides
Interdomain Path Computation A Hierarchical Architecture
NARB summarizes individual domain topology and advertises it globally using link-state routing NARB summarizes individual domain topology and advertises it globally using link-state routing protocol, generating an abstract topology.protocol, generating an abstract topology.
RCE computes partial paths by combining the abstract global topology and detailed local topology. RCE computes partial paths by combining the abstract global topology and detailed local topology. NARB’s assemble the partial paths into a full path by speaking to one another across domains.NARB’s assemble the partial paths into a full path by speaking to one another across domains.
NARB
w/RCE
NARB
w/RCE
NARB
w/RCE
Summarized/Abstract InterDomain Topoloy (A single link state flooding area)
IntraDomain Topoloy - Area 1
IntraDomain Topoloy - Area 2
IntraDomain Topoloy - Area 3
E2E Multi-Domain Path Computation Scheme
DRAGON mainly uses Recursive Per-Domain (RPD) interdomain path computation
Full explicit path is obtained before signaling.Full explicit path is obtained before signaling. Other supported schemes include Centralized path computation and Other supported schemes include Centralized path computation and
Forward Per-Domain (FPD) path computation.Forward Per-Domain (FPD) path computation.
NARB
w/RCE
NARB
w/RCE
NARB
w/RCE
Domain 1
Domain 2
Domain 3
SourceDestination
Strict Hops
Strict Hops
Strict Hops Loose Hops
Loose Hops
1
request
2request
3request
5expand
6full path
4expand
DRAGON CSPF Path Computation Heuristics
A breadth first search based CSPF heuristic in A breadth first search based CSPF heuristic in deploymentdeployment Takes flexible combination of various constraints, such as Takes flexible combination of various constraints, such as
bandwidth, switch cap., wavelength, VLAN tag and add-on bandwidth, switch cap., wavelength, VLAN tag and add-on policy constraints.policy constraints.
Supports multi-region networks using configurable region-Supports multi-region networks using configurable region-crossing criteriacrossing criteria
Reliable results; probably time-consuming in large networks Reliable results; probably time-consuming in large networks (~30ms in the 12-node HOPI+DRAGON network)(~30ms in the 12-node HOPI+DRAGON network)
Other heuristics under research; one is based on Other heuristics under research; one is based on a channel-graph model in combination with K-a channel-graph model in combination with K-shortest path routing.shortest path routing.
Three Policy Dimensions in GMPLS Service Provisioning
Resource dimensionResource dimension Link availability, bandwidth Link availability, bandwidth
capability & resource capability & resource interdependenceinterdependence
TE constraints, e.g. switching cap.TE constraints, e.g. switching cap.
AAA policy dimensionAAA policy dimension User privilegesUser privileges App. specific requirements (SLA)App. specific requirements (SLA) Administration policiesAdministration policies
Time schedule dimensionTime schedule dimension
Resources
AAA Rules
T im eSchedule
Solution Space
Feasible Solution (LSP)
Integrate and translate network resource states and policies into Integrate and translate network resource states and policies into shared control plane intelligence.shared control plane intelligence.
Synergize AAA policy decision with TE based provisioning Synergize AAA policy decision with TE based provisioning decision, resulting in fast, precise and simplified control process.decision, resulting in fast, precise and simplified control process.
3 Dimensional (3D) Resource Computation Model
Resource states, time schedule and AAA policiesare exchanged among control-plane entities in both intradomain and interdomain scopes.
Three dimensions of constraints are used in joint to compute which resource to allocate
and generate policy decisions.
Actual service provisioning:resource allocation and policy enforcement.
GMPLS routing,path computation
GMPLS signaling
Resources
AAA Rules
T im eSchedule
Solution Space
Feasible Solution (LSP)
DRAGON Resource Computation Engine (RCE)
Support
Interdomain E2E path computation
Advance scheduled service provisioning
AAA based provisioning and admission control
RCE is the element in GMPLS control-plane to perform the RCE is the element in GMPLS control-plane to perform the computation intensive resource management & policy decision tasks.computation intensive resource management & policy decision tasks.
RCE can be used as a standalone server or as an integrated NARB RCE can be used as a standalone server or as an integrated NARB module.module.
3D Constraint Based Path Computation
LSP Request AAA Rul esTabl e
TEDB
Check OutAf fecti ng
Rul es
User Speci f i edRul es
AAARul e
Fi l ter
Rul e Parser
Rul e Parser
Ti meWi ndowFi l ter
User Schedul e Constrai nts
Reduced Topol ogy
CSPF Routi ngAl gori thm
LSP Path
LSPSchedul e
Exi st i ngResource
Reservati ons
Network and Domai nPol i ci es
Data source (raw link states from intra- and inter-domain flooding) and 3D constraints
Snapshot of topology reduced by policy filters
Constraint based path computation algorithm - CSPF heuristics
AAA Based Provisioning
Type = TBD Length = Vari abl e0 8 16 24 31
AAA pol i cy rul e sub-TLV(s)
AAA pol i cy refence I D sub-TLV(s)
Type = 1 Length = 12
User I D
Rul e (Acti on/ Restri ct i on)
Local Resource I D
Type = 2 Length = 4Pol i cy Reference I D
AAA Policy TE Link TLVAAA Policy TE Link TLV Allows a AAA information to be included as part of path Allows a AAA information to be included as part of path
computationcomputation Path Computation understanding/interpretation of rules Path Computation understanding/interpretation of rules
very simplevery simple Much work needed in this areaMuch work needed in this area
Time Based Provisioning
Schedule TE Link TLVSchedule TE Link TLVAllows a time constraint to be included Allows a time constraint to be included
as part of path computationas part of path computation
Type = TBD Length = N*5
0 8 16 24 31
Resv 1 – Start time Resv 1 -Duration Resv 2 – Start time
Resv 2 - Duration Resv 3 ...
Repeated N times (N ≤ 40)
Continuing WorkKey Focus Areas
GMPLS Control PlaneGMPLS Control Plane Inter-domain routing and signaling agreementsInter-domain routing and signaling agreements
R&E community should make this a priority R&E community should make this a priority Advanced path computation techniquesAdvanced path computation techniques Inter-operability with vendor stacksInter-operability with vendor stacks Multi-layer stitching Multi-layer stitching
AAA and Scheduling Control Plane FeaturesAAA and Scheduling Control Plane Features Web Service based control planesWeb Service based control planes Application Specific TopologiesApplication Specific Topologies
Integration/reconciliation of AST, Network Description Integration/reconciliation of AST, Network Description Language, Common Service Definition specsLanguage, Common Service Definition specs
Integration with applications Integration with applications
Multi-Layer GMPLS Networks
“vertical” multi-layer adaptations for traffic grooming, multiple services, multiple “virtual” networks
Ethernet Layer
Switched WDM Optical Layer
Switched SONET Layer (vcat, lcas)
Ethernet Layer
Switched WDM Optical Layer
Ethernet Layer
Switched SONET Layer (vcat, lcas)
Ethernet Layer
Switched WDM Optical Layer
Multi-Layer GMPLS Networks
Provisioned Topologies
The Vision: One Infrastructure
Multiple Topologies/Services“ Ethernet Framed Lambda”
“Basic Ethernet Service”
“Dedicated VLAN Connection over Ethernet”
Ethernet Layer
Switched WDM Optical Layer
Switched SONET Layer (vcat, lcas)
Heterogeneous Network Technologies
Complex End to End Paths
End Syste
m
AS 1AS 2 AS 3
VLSR
Ethernet SegmentVLSR Established VLAN
Ethernet over WDM
Ethernet over SONET
End Syste
m
Ethernet SegmentVLSR Established VLAN
VLSR
Router MPLS LSP
IP Control Plane
IP Control Plane
IP Control Plane
Ethernet
Router
Lambda Switch
SONET Switch
“horizontal” multi-layer adaptations for multi-domain
InterDomain (G)MPLS and Web Services
Currently working on interdomain virtual circuit Currently working on interdomain virtual circuit provisioning between:provisioning between: ESnetESnet AbileneAbilene HOPIHOPI UltraScience NetUltraScience Net
Focusing on how to accomplish routing, Focusing on how to accomplish routing, signaling, path computation in a mixed (G)MPLS signaling, path computation in a mixed (G)MPLS and Web Service environmentand Web Service environment
DRAGON Control PlaneR&E “Hybrid” Networks
Multi-Service, Multi-Level, Multi-Domain Multi-Service, Multi-Level, Multi-Domain One “infrastructure” which provides basic IP routed One “infrastructure” which provides basic IP routed
service as well services at lower layerservice as well services at lower layer i.e., connectionless and connection oriented services i.e., connectionless and connection oriented services
Services could be point to point circuits or application Services could be point to point circuits or application specific layer2 multipoint broadcast domainsspecific layer2 multipoint broadcast domains
Interoperable architectures & control planes neededInteroperable architectures & control planes needed Integration challenges (control, data, management Integration challenges (control, data, management
planes)planes) Multi-layer adaptations “horizontal” for multi-domainMulti-layer adaptations “horizontal” for multi-domain Multi-layer adaptations “vertically” for traffic groomingMulti-layer adaptations “vertically” for traffic grooming Key control plane functions: routing, signaling, path Key control plane functions: routing, signaling, path
computationcomputation Scheduling and AAA functions also neededScheduling and AAA functions also needed Integration of (G)MPLS and Web ServicesIntegration of (G)MPLS and Web Services
R&E “Hybrid” Networks
One “infrastructure” which provides basic IP routed One “infrastructure” which provides basic IP routed service as well deterministic services at lower layerservice as well deterministic services at lower layer Services could be point to point circuits or application specific Services could be point to point circuits or application specific
layer2 multipoint broadcast domainslayer2 multipoint broadcast domains Multi-Service, Multi-Layer, Multi-DomainMulti-Service, Multi-Layer, Multi-Domain
Emerging Hybrid Network environment is driving a new Emerging Hybrid Network environment is driving a new service model: service model: Dedicated end-to-end services will be available at the wide area Dedicated end-to-end services will be available at the wide area
edgeedge Challenge for GigaPoPs, Regional Optical Networks (RONs), Challenge for GigaPoPs, Regional Optical Networks (RONs),
and campuses is how to extend these services from the wide and campuses is how to extend these services from the wide area edge across the regional networks, campus infrastructure, area edge across the regional networks, campus infrastructure, and to the user location. and to the user location.
Techniques will depend on the details of the service offerings Techniques will depend on the details of the service offerings from the wide area R&E networks, the particular needs of the from the wide area R&E networks, the particular needs of the local user community, and the nature of the available regional local user community, and the nature of the available regional infrastructures. infrastructures.
“Hybrid” Network Service Provisioning
Multiple technology options:Multiple technology options: MPLS, Ethernet, SONET, WDM, FiberMPLS, Ethernet, SONET, WDM, Fiber
Many solutions will use combinations of the above (i.e., multi-Many solutions will use combinations of the above (i.e., multi-layer)layer)
Service Interface (user connection) likely to be:Service Interface (user connection) likely to be: Ethernet Port (possibly with specific VLANs)Ethernet Port (possibly with specific VLANs) SONET/SDH port (more often for network to network)SONET/SDH port (more often for network to network)
Multiple provisioning optionsMultiple provisioning options Manual, Management Plane, Control PlaneManual, Management Plane, Control Plane
Many issues including AAA, Scheduling, Service Many issues including AAA, Scheduling, Service Level Agreements, Common Service Level Agreements, Common Service Agreements, user requirements Agreements, user requirements
What About Web Services?
There is value to capturing some of these control There is value to capturing some of these control plane functions in the form of Web Servicesplane functions in the form of Web Services
For DRAGON, that would mean putting a Web For DRAGON, that would mean putting a Web Service interface into our GMPLS control planeService interface into our GMPLS control plane Automatically processing of routing protocols Automatically processing of routing protocols
The most basic web service needed is The most basic web service needed is (abstracted) topology representation(abstracted) topology representation Network Description Language (NDL) seems like a Network Description Language (NDL) seems like a
good method for topology (network graph) good method for topology (network graph) representationsrepresentations
Community needs to agree on a schemaCommunity needs to agree on a schema
GMPLS and WS Control Plane Overlap
Idea – All participating control planes must have a common Idea – All participating control planes must have a common set of topology discovery, routing, path computation and set of topology discovery, routing, path computation and signaling functionality.signaling functionality.
Methodology – Translate the “key” GMPLS-CP functions into Methodology – Translate the “key” GMPLS-CP functions into WS-CP counterparts in web services notationsWS-CP counterparts in web services notations
GMPLS-CP
GMPLS Signaling Protocols
WS Provisioning and Scheduling Services
GMPLS Path Computation Algorithms & Protocols
WS Path Computation Services
GMPLS Routing Protocols WS Routing Services
Secure Messaging Mutual Trust Policy Exchange
WS-CP
Topology Description Advertisement & Routing
Multi-Layer Inter-Network Path Computation
Inter-Network Signaling
Common Internetworking Infrastructure Services
Context ManagementRegistration and Discovery
WS-CP StructureWeb Service Wrappers
<wsdl:operation name="createPathReservation">
Network Description Language
Network Controller Core Functions
Topology Description &
Discovery Service
Multi-Layer PCE
TEDB Signaling & Management
Scheduling
Inter-Network Path Computation Logic
Topology Summrization
Intra-Network Path Computation
Service Inter-Network Path Computation
Collaboration Service
Inter-Network Signaling Service
Inter-Network Scheduling
Service
Web Services Wrappers
CIIS Services
UDDI
<wsdl:operation name="getNetworkTopology">
<wsdl:operation name="getAdjacentNetworkList">
<wsdl:operation name="createInternetworkPathComputationSession">
<wsdl:operation name="createAdaptationCrossConnect">
<wsdl:operation name="getRecursivePathComputationResult">
<wsdl:operation name="getPathComputationResult">
Conclusions
Any control plane will have to address routing, Any control plane will have to address routing, path computation, and signalingpath computation, and signaling
GMPLS represents the most advanced set of GMPLS represents the most advanced set of thinking, concepts, and capabilities in this areathinking, concepts, and capabilities in this area Need to track and leverage these concepts, standards Need to track and leverage these concepts, standards
activities, and vendor implementations to the activities, and vendor implementations to the maximum extent possiblemaximum extent possible
There is value in capturing some of these There is value in capturing some of these functions via web servicesfunctions via web services Particularly topology descriptionsParticularly topology descriptions Need to agree on a schema (i.e., NDL)Need to agree on a schema (i.e., NDL)
Conclusions Expect a future environment where some peering Expect a future environment where some peering
networks will use GMPLS and some use Web Servicesnetworks will use GMPLS and some use Web Services Should be able to accomplish multi-domain provisioning in this Should be able to accomplish multi-domain provisioning in this
environmentenvironment This will allow interoperation between GMPLS and non-GMPLS This will allow interoperation between GMPLS and non-GMPLS
networks (or Web Service and non-Web Service networks networks (or Web Service and non-Web Service networks depending on your viewpoint)depending on your viewpoint)
Most participants in this community have a per domain Most participants in this community have a per domain controller/managercontroller/manager We should strive to define the InterDomain communications We should strive to define the InterDomain communications
required for both:required for both: GMPLS style control planeGMPLS style control plane Web Service style control planeWeb Service style control plane
Future will likely be mixture of bothFuture will likely be mixture of both
Control Plane Standards Activities
GMPLS Interdomain Routing and Signaling SolutionDRAGON comparison to OIF
Similar in overall concept in terms ofSimilar in overall concept in terms of use of hierarchical link state (OSPF derived) for routinguse of hierarchical link state (OSPF derived) for routing RSVP for signalingRSVP for signaling
Many differences in the detailsMany differences in the details Domain/Routing ControllersDomain/Routing Controllers
OIF OSPF daemons are called Routing Controllers (RC); RC ID = Router IDOIF OSPF daemons are called Routing Controllers (RC); RC ID = Router ID One or more RC in each routing domain as routing speakers for the domainOne or more RC in each routing domain as routing speakers for the domain
DRAGON has the Network Area resource Broker (NARB) as RC, which has no DRAGON has the Network Area resource Broker (NARB) as RC, which has no corresponding router and operates a dedicated instance of OSPF in a separate address corresponding router and operates a dedicated instance of OSPF in a separate address spacespace
Both have adjacency via IP tunnels and control communications via separate tunnel Both have adjacency via IP tunnels and control communications via separate tunnel addressesaddresses
OIF introduces Local/Remote Node ID sub-TLV for separation of data plane from control OIF introduces Local/Remote Node ID sub-TLV for separation of data plane from control pane (each RC can correspond to multiple routers (nodes)) and Hierarchy List sub-TLV to pane (each RC can correspond to multiple routers (nodes)) and Hierarchy List sub-TLV to add vertical hierarchies to TE topology.add vertical hierarchies to TE topology.
Connection End PointsConnection End Points OIF UNI uses TNA w/ Node ID addresses, which introduces Reachable TNA Opaque LSA OIF UNI uses TNA w/ Node ID addresses, which introduces Reachable TNA Opaque LSA
and Node ID sub-TLV into OSPF-TE advertisementand Node ID sub-TLV into OSPF-TE advertisement DRAGON uses edge router loopback IP with Local-ID, which introduces Local-ID to end DRAGON uses edge router loopback IP with Local-ID, which introduces Local-ID to end
users but does not add anything into the OSPF-TEusers but does not add anything into the OSPF-TE The plan is for DRAGON be become standards compliant as they mature The plan is for DRAGON be become standards compliant as they mature
(with hopefully interoperation with other domains providing specific (with hopefully interoperation with other domains providing specific requirements) requirements)
Multi-Layer Infrastructures
Layer 3IPv4, IPv6,MPLS
Layer 2Ethernet, ATM
Layer 1.5SONET, GFP,VCAT, LCAS
Layer 1DWDM
Diversified “Cyber-Infrastructures”
DRAGONDRAGONDRAGONDRAGON
ESNetESNet+ OSCARS+ OSCARS
ESNetESNet+ OSCARS+ OSCARS
DRAGONDRAGONDRAGONDRAGON
UltraUltraScienceScience
NetNet
UltraUltraScienceScience
NetNetCHEETAHCHEETAHCHEETAHCHEETAH
NewNetNewNetNewNetNewNet
AbileneAbilene+ BRUW+ BRUWAbileneAbilene+ BRUW+ BRUW
Application Layers
Multi-media (VoIP, HDTV)
E-science, grid, virtualization Virtual reality, data
fusion / visualizationStorage, data archive, mirroring, peer-peer
Multi-Layer / Multi-Domain Focus
Scale Services Across Layers
Resource DiscoveryResource Discovery
• Hierarchical routing• Multi-layer database• Legacy domain (proxy)• Temporal state
Path Comp, Scheduling
Path Comp, Scheduling
• Distd / centralized• Domain controllers• Path composition• Adv. scheduling
Signaling & Recovery
Signaling & Recovery
• Multi-layer LSP: Stitching, merging• Multi-layer recovery• Signaling extensions
Security, AAA
Security, AAA
• Encryption• Integrity• Client validation
Need R&D, new standards, Need R&D, new standards, vendor supportvendor support
Need R&D, new standards, Need R&D, new standards, vendor supportvendor support
Unified Inter-Layer ArchitectureUnified Inter-Layer ArchitectureUnified Inter-Layer ArchitectureUnified Inter-Layer Architecture
OIF Networking WG’sOIF Networking WG’sUNI, NNI specificationsUNI, NNI specificationsOIF Networking WG’sOIF Networking WG’s
UNI, NNI specificationsUNI, NNI specificationsITU-T SG-15, SG-13 WGArchitectures, L1 VPN
ITU-T SG-15, SG-13 WGArchitectures, L1 VPN
IETF WG’sArchitectures, protocols,
L1 VPN
IETF WG’sArchitectures, protocols,
L1 VPN
Multi-Layer / Multi-Domain Activities
Liaison ActivitiesLiaison Activities
Standards Tracking
Optical Internetworking Optical Internetworking ForumForum
User Network Interface (UNI) 2.0
• Multi-vendor interoperable client provisioning
Automated end-pt & service discovery, signaling (parameters)
• Improved resiliency, control security, Eth support (IETF, ITU-T inputs)
• UNI-N side supports multi-layer call/connections (VCAT)
Network to Node Interface (Internal – NNI, External - NNI)
• Decouple intra & inter-domain mechanisms (protocols, algorithms)
• Signaling protocol: parameter negotiation, protection/diversity
• Hierarchical routing: topology / resource discovery
• Generally lacks provisions for advance scheduling
IEC Supercomm interoperability trials
• Interim UNI 1.0 (2001): End-pt discovery, setup/teardown, full λrates
• UNI 2.0, E-NNI 1.0 (2005):
13 vendors, 7 service providers (focus on EoS services)
International Telecom Union International Telecom Union (ITU-T)(ITU-T)
Automatically-Switched Optical Network (SG - 15, G.8080)
• Multi-level hierarchical link-state routing (G.7715.x):
Horizontal (areas), vertical (leaders), inter-level state exchange
• Distd call / connection management (G.7713.x, SN controllers):
Recently addressing protection/restoration, no crankback yet
Layer 1 VPN (SG - 13)
• Req & architecture documents (Y.1312 / 2003, Y.1313 / 2004)
• Close liason w. IETF (routing area) on suitability of IETF protocols
Other liason activities to evolve “ASON compliant” protocols
• Signaling:
IETF RSVP-TE drafts for ASON, OIF UNI 2.0 & NNI 1.0 alignment
• Link-state routing:
- Reqs RFC 4258, OSPF-TE and IS-IS drafts for ASON (G.7715.1)
- OIF NNI 1.0 routing
Internet Engineering Internet Engineering TaskforceTaskforce
CCAMP working group (GMPLS)
• GMPLS control for SONET/SDH (RFC 4257)
• GFP/LCAS interface discovery (OSPF-TE, RSVP-TE implications)
• Multi-layer/multi-region (MRN) networks drafts:
Interface switching capability (ISC), unified TE database
• Drafts on multi-domain routing (OSPF-TE, O-BGP), no temporal state
• Other drafts on multi-domain/AS signaling & recovery:
Crankback, inter-AS exclude routes, etc
Path computation element (PCE) working group (TE)
• Path composition for TE-LSP paths:
Centralized / distributed, loose-domain / hop-by-hop
• Inter-area / AS / layer considerations (virtual topology management)
• New PCEP signaling protocol, possibly one for PCE discovery
• No PCE considerations for advance scheduling
• Various requirements drafts (2004-5), no RFC yet
IETF Multi-Layer NetworkIETF Multi-Layer Network
• Networks w. multiple domains,, nodes w. multiple layers• Run single GMPLS instance (routing, signaling): - Multiple links in TE database (TED) w. FA-LSP, ISC - Node-internal links for multi-layer nodes• Path-computation can use ISC to qualify links• Virtual network topology (VNT) via TE links @ lower layers• Inter-domain aspects not addressed in drafts
Overview
Vertical link
Mixed IP,MSPPIP/MPLS
DWDM, TDM
Horizontal link
L1 VPN service interfaces
Distributed GMPLS Control
Centralized Management Control
Provider network
P node
PE node
CE node
Customer networksCustomer networks
CMN interface CMN interface
Carrier OSS
Customer OSS
Customer OSS
Provider network
P node
PE node
CE node
Customer networksCustomer networks
IETF L1 VPN FrameworkIETF L1 VPN FrameworkLayer 1 VPN working group
• “Infrastructure virtualization”: DWDM lighpath, SONET circuit• Basic and enhanced modes: signaling only vs. distd signaling & routing• Drafts on BGP & OSPF PE discovery (opaque LSA), single AS focus for now• Proposal to extend RSVP-TE signaling (per VPN instances)• Framework draft (near last call), no RFC yet
IETF L1 VPN Service IETF L1 VPN Service ModelsModels
Differing Levels of CE-PE Functionality / Exchange
