Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN.

Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, 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 Address Destination Address Bandwidth (50 Mbps increments) VLAN TAG (None | Any | Number) Schedule Client A Client B Service Request CSA Ethernet Mapped SONET or SONET Circuits Dynamically Provisioned Dedicated Resource Path (“Circuit”) Internet2 DCS Domain Controller 1 b a 2 CSA 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 Address Destination Address Bandwidth (50 Mbps increments) VLAN TAG (None | Any | Number) Schedule Client A Client B Service Request Switch Fabric VLSR CSA 1 b a 2 Domain Controller

Inter-Domain

DRAGON Control Plane Status and Adaptation to Internet2 Network Slides by Tom Lehman University of Southern California Information Sciences Institute (USC ISI) And Others from the Development Team

Topics DRAGON Control Plane Status DRAGON Control Plane Status Thoughts/Considerations regarding Evolution to Internet2 Control Plane Thoughts/Considerations regarding Evolution to Internet2 Control Plane Advanced Topics: Web Services, AAA, Scheduling Advanced Topics: Web Services, AAA, Scheduling Next Steps and Timelines Next Steps and Timelines

DRAGON Control Plane Key Components Network Aware Resource Broker – NARB Network Aware Resource Broker – NARB Intradomain listener, Path Computation, Interdomain Routing Intradomain listener, Path Computation, Interdomain Routing Virtual Label Swapping Router – VLSR Virtual Label Swapping Router – VLSR Open source protocols running on PC act as GMPLS network element (OSPF-TE, RSVP-TE) Open source protocols running on PC act as GMPLS network element (OSPF-TE, RSVP-TE) Control PCs participate in protocol exchanges and provisions covered switch according to protocol events (PATH setup, PATH tear down, state query, etc) Control PCs participate in protocol exchanges and provisions covered switch according to protocol events (PATH setup, PATH tear down, state query, etc) Client System Agent – CSA Client System Agent – CSA End system or client software for signaling into network (UNI or peer mode) End system or client software for signaling into network (UNI or peer mode) Application Specific Topology Builder – ASTB Application Specific Topology Builder – ASTB User Interface and processing which build topologies on behalf of users User Interface and processing which build topologies on behalf of users Topologies are a user specific configuration of multiple LSPs Topologies are a user specific configuration of multiple LSPs

Multi-Domain Control Plane The (near-term) big picture RON Internet2 Network ESNet Dynamic Ethernet TDM GEANT IP Network (MPLS, L2VPN) Ethernet Router SONET Switch Ctrl Element Domain Controller LSP Data Plane Control Plane Adjacency Multi-Domain Provisioning Multi-Domain Provisioning Interdomain ENNI (Web Service and OIF/GMPLS) Interdomain ENNI (Web Service and OIF/GMPLS) Multi-domain, multi-stage path computation process Multi-domain, multi-stage path computation process AAA AAA Scheduling Scheduling

DRAGON/HOPI Control Plane Provisioning Environment GMPLS Multi-layer, Multi-Domain GMPLS Multi-layer, Multi-Domain Ethernet Service Provisioning Ethernet Service Provisioning Dynamic dedicated VLAN based connections Dynamic dedicated VLAN based connections Ethernet Layer Switched WDM Optical Layer DRAGON Multi-Layer GMPLS Network HOPI Dynamic Ethernet Network Domain Boundary GMPLS Provisioned LSP Dedicated Ethernet VLAN “Circuit” GWU CLPK LA SEA DCCHI Static Optical Layer MCLN ARLG DCNE NY HOU Ethernet Layer ENNI IGP-TE UNI

Heterogeneous Network Technologies Complex End to End Paths “horizontal” multi-layer adaptations for multi-domain

DRAGON Control Plane Interoperation with Ciena Domain Three Options Three Options All have one NARB per Ciena Domain, receives topology information from Ciena Domain (ENNI, CORBA, static configuration ?) All have one NARB per Ciena Domain, receives topology information from Ciena Domain (ENNI, CORBA, static configuration ?) GMPLS GMPLS One VLSR per Core Director; front end for signaling One VLSR per Core Director; front end for signaling Handles AAA, any special purpose configuration not handled by current GMPLS protocols (edge VLAN mapping adjustment for instance), other unique processing associated with peer entities Handles AAA, any special purpose configuration not handled by current GMPLS protocols (edge VLAN mapping adjustment for instance), other unique processing associated with peer entities GMPLS Wrapper over Management Plane GMPLS Wrapper over Management Plane One VLSR per Core Director Domain One VLSR per Core Director Domain Presents GMPLS to the outside world (probably as single opaque network with multiple external connections) Presents GMPLS to the outside world (probably as single opaque network with multiple external connections) Use CORBA for Core Director Provisioning Use 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 Ciena Domain via UNI or ENNI Same as above but use a “management style” system which talks to Ciena Domain via UNI or ENNI

Ongoing Ciena Testing Resource Partitioning. Can resources be partitioned such that control plane (OSRP) provisioned resources and manually (management system) can be isolated from each other? We believe this is possible Resource Partitioning. Can resources be partitioned such that control plane (OSRP) provisioned resources and manually (management system) can be isolated from each other? We believe this is possible Is it possible to police VLANS? Can each VLAN be policed and rate limited independently? We believe this is also possible! Is it possible to police VLANS? Can each VLAN be policed and rate limited independently? We believe this is also possible! Looking forward to UNI2.0 and ENNI availability Looking 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 vendors? Will GFP encapsulated ethernet frames be interoperable with other vendors?

VLSR (Virtual Label Switching Router) GMPLS Proxy GMPLS Proxy (OSPF-TE, RSVP-TE) (OSPF-TE, RSVP-TE) Local control channel Local control channel CLI,TL1, SNMP, others CLI,TL1, SNMP, others Used primarily for ethernet switches Used primarily for ethernet switches Web page XML Interface ASTB CLI Interface One NARB per Domain Provisioning requests via CLI, XML, or ASTB Provisioning requests via CLI, XML, or ASTB

VLSR (Virtual Label Switching Router) RSVP Signaling module RSVP Signaling module Originated from Martin Karsten’s C++ KOM-RSVP Originated 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 CLI Extended to support VLAN control through CLI OSPF Routing module OSPF Routing module Originated from GNU Zebra Originated 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 date Ethernet switches tested to date Dell PowerConnect, Extreme, Intel, Raptor, Force10 Dell PowerConnect, Extreme, Intel, Raptor, Force10

NARB Network Aware Resource Broker Interdomain Routing Interdomain Routing hierarchical link state hierarchical link state Carries a modified TEDB that can support Carries a modified TEDB that can support AAA AAA Scheduling Scheduling Path Computation Element and ERO (loose and strict) generation Path Computation Element and ERO (loose and strict) generation NARB End System NARB End System AS 1 AS 2 AS 3 InterDomain Exchange

NARB (Network Aware Resource Broker) NARB is an agent that represents a domain NARB is an agent that represents a domain Intra-domain Listener Intra-domain Listener Listens to OSPF-TE to acquire intra-domain topology Listens to OSPF-TE to acquire intra-domain topology Builds an abstracted view of internal domain topology Builds an abstracted view of internal domain topology Inter-domain routing Inter-domain routing Peers with NARBs in adjacent domains Peers with NARBs in adjacent domains Exchanges (abstracted) topology information Exchanges (abstracted) topology information Maintains an inter-domain link state database Maintains an inter-domain link state database Path Computation Path Computation Performs intra-domain (strict hop) TE path computation Performs intra-domain (strict hop) TE path computation Performs inter-domain (loose hop) TE path computation Performs 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 “3 Dimensional Resource Computation Engine (3D RCE)” Hooks for incorporation of AAA and scheduling into path computation via a “3 Dimensional Resource Computation Engine (3D RCE)” The Traffic Engineering DataBase (TEDB) and Constrained Shortest Path Computation (CSPF) are extended to include dimensions of GMPLS TE parameters, AAA constraints, and Scheduling constraints. The Traffic Engineering DataBase (TEDB) and Constrained Shortest Path Computation (CSPF) are extended to include dimensions of GMPLS TE parameters, AAA constraints, and Scheduling constraints. 3D RCE is the combination of 3D TEDB and 3D CSPF 3D RCE is the combination of 3D TEDB and 3D CSPF http://dragon.east.isi.edu/data/dragon/documents/dragon-infocom-APBM- workshop-apr282006.pdf http://dragon.east.isi.edu/data/dragon/documents/dragon-infocom-APBM- workshop-apr282006.pdf

What is the HOPI Service? Physical Connection: Physical Connection: 1 or 10 Gigabit Ethernet 1 or 10 Gigabit Ethernet Circuit Service: Circuit Service: Point to Point Ethernet VLAN Circuit Point to Point Ethernet VLAN Circuit Tagged or Untagged VLANs available Tagged or Untagged VLANs available Bandwidth provisioning available in 100 Mbps increments Bandwidth 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 Address, Bandwidth Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Address, Bandwidth Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, email Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, email Application Specific Topology is a user specific instantiation of multiple individual circuits Application Specific Topology is a user specific instantiation of multiple individual 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; could be RONS, GIgaPops, other wide area networks, end systems Anyone who connects to an ethernet port on an HOPI Force 10 Switch; could be RONS, GIgaPops, other wide area networks, end systems

GMPLS Provisioned Ethernet Services Multiple Ethernet Provisioning Options Multiple Ethernet Provisioning Options Point to Point Ethernet VLAN based LSPs Point to Point Ethernet VLAN based LSPs Ethernet switch (vendor specific) features applied to guarantee LSP bandwidth in increments of 100 Mbit/s Ethernet switch (vendor specific) features applied to guarantee LSP bandwidth in increments of 100 Mbit/s Edge connection flexibility provided by use of “Local ID” feature which 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. Edge connection flexibility provided by use of “Local ID” feature which 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. Users can request services via Peer to Peer GMPLS, UNI style GMPLS, or via an XML application interface Users can request services via Peer to Peer GMPLS, UNI style GMPLS, or via an XML application interface Ethernet VLAN space is “flat” across provisioned space. Constrained based path computation utilized to find available VLAN Tags. Ethernet VLAN space is “flat” across provisioned space. Constrained based path computation utilized to find available VLAN Tags. VLAN tags treated in a similar manner to wavelengths VLAN tags treated in a similar manner to wavelengths “Local ID” for Egress Control Ethernet switch VLSR PC Ethernet switch VLSR PC Ethernet switch VLSR PC Ethernet switch VLSR PC Ethernet switch VLSR PC Ethernet switch VLSR PC VLAN XX LSP VLAN YY LSP User Requests: Peer to Peer UNI XML API

Ethernet VLAN based Provisioning Local ID defines the VLAN tag/edge port mapping Local ID defines the VLAN tag/edge port mapping Several options; tagged, untagged, single port, port groups, automatic Several options; tagged, untagged, single port, port groups, automatic Local ID definitions can be adjusted dynamically Local ID definitions can be adjusted dynamically OSPF OSPF configure vlans on each interface configure vlans on each interface advertise out in IfSwCap Descriptor TLV inside a TE Link LSA advertise out in IfSwCap Descriptor TLV inside a TE Link LSA update vlans availability and bandwidth in response to provisioning update vlans availability and bandwidth in response to provisioning similar to the existing ifswcap-specific-psc and ifswcap-specific-tdm similar to the existing ifswcap-specific-psc and ifswcap-specific-tdm RSVP ERO RSVP ERO proprietary Unnumbered Interface ID Subobjects (UnNumIfID) used to encode VLAN information in ERO proprietary Unnumbered Interface ID Subobjects (UnNumIfID) used to encode VLAN 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/RCE NARB/RCE listen to OSPF listen to OSPF path computation with bandwidth and vlan constraints path computation with bandwidth and vlan constraints create EROs with UnNumIFID objects create 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><resource> eVLBI.Mark5a eVLBI.Mark5a Haystack.muk1 Haystack.muk1 muk1.haystack.mit.edu muk1.haystack.mit.edu muk1-ge0.haystack.mit.edu muk1-ge0.haystack.mit.edu /usr/local/evlbi_script /usr/local/evlbi_script <resource> eVLBI.Mark5a eVLBI.Mark5a Westford1 Westford1 wstf.haystack.mit.edu wstf.haystack.mit.edu wstf-ge0.haystack.mit.edu wstf-ge0.haystack.mit.edu /usr/local/evlbi_script /usr/local/evlbi_script <resource> EtherPipeBasic EtherPipeBasic Haystack.muk1 Haystack.muk1 Westford.muk1 Westford.muk1 1 Gbs 1 Gbs </topology> AB C A B C

Application Specific Topologies Live demonstration at Internet2 Spring Member Meeting (April 2006, Washington DC) Live demonstration at Internet2 Spring Member Meeting (April 2006, 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 Ethernet 1 or 10 Gigabit Ethernet OC-3, OC-12, OC-48, OC192 SONET OC-3, OC-12, OC-48, OC192 SONET Circuit Service: Circuit Service: Point to Point Ethernet VLAN Circuit Point to Point Ethernet VLAN Circuit Point to Point Ethernet Framed SONET Circuit Point to Point Ethernet Framed SONET Circuit Point to Point SONET Circuit Point to Point SONET Circuit Bandwidth provisioning available in 50 Mbps increments (STS-1 granularity) Bandwidth provisioning available in 50 Mbps increments (STS-1 granularity) How do Clients Request? How do Clients Request? Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Address, Bandwidth Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Address, Bandwidth Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, email Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, email Application Specific Topology is a user specific instantiation of multiple individual circuits Application Specific Topology is a user specific instantiation of multiple individual circuits What is the definition of a Client? What is the definition of a Client? A Device on the network requesting a circuit connection A Device on the network requesting a circuit connection

Control Plane Objectives Multi-Service, Multi-Domain, Multi-Layer, Multi-Vendor Provisioning Multi-Service, Multi-Domain, Multi-Layer, Multi-Vendor Provisioning Basic capability is the provision of a “circuit” in above environment Basic capability is the provision of a “circuit” in above environment In addition, need control plane features for: In addition, need control plane features for: AAA AAA Scheduling Scheduling Easy APIs which combine multiple individual control plane actions into an application specific configuration (i.e., application specific topologies) Easy APIs which combine multiple individual control plane actions into an application specific configuration (i.e., application specific topologies)

Key Control Plane Features ( for Connection Control ) Routing Routing distribution of "data" between networks. The data that needs to be distributed includes reachability information, resource usages, etc distribution of "data" between networks. The data that needs to be distributed includes reachability information, resource usages, etc Path computation Path computation the processing of information received via routing data to determining how to provision an end-to-end path. This is typically a Constrained Shortest Path First (CSPF) type algorithm for the GMPLS control planes. Web services based exchanges might employ a modified version of this technique or something entirely different. the processing of information received via routing data to determining how to provision an end-to-end path. This is typically a Constrained Shortest Path First (CSPF) type algorithm for the GMPLS control planes. Web services based exchanges might employ a modified version of this technique or something entirely different. Signaling Signaling the exchange of messages to instantiate specific provisioning requests based upon the above routing and path computation functions. This is typically a RVSP-TE exchange for the GMPLS control planes. Web services based exchanges might employ a modified version of this technique or something entirely different. the exchange of messages to instantiate specific provisioning requests based upon the above routing and path computation functions. This is typically a RVSP-TE exchange for the GMPLS control planes. Web services based exchanges might employ a modified version of this technique or something entirely different.

Key Control Plane Key Capabilities Domain Summarization Domain Summarization Ability to generate abstract representations of your domain for making available to others Ability to generate abstract representations of your domain for making available to others The type and amount of information (constraints) needed to be included in this abstraction requires discussion. The type and amount of information (constraints) needed to be included in this abstraction requires discussion. Ability to quickly update this representation based on provisioning actions and other changes Ability to quickly update this representation based on provisioning actions and other changes Multi-layer “Techniques” Multi-layer “Techniques” Stitching: some network elements will need to map one layer into others, i.e., multi-layer adaptation Stitching: some network elements will need to map one layer into others, i.e., multi-layer adaptation In this context the layers are: PSC, L2SC, TDM, LSC, FSC In this context the layers are: PSC, L2SC, TDM, LSC, FSC Hierarchical techniques. Provision a circuit at one layer, then treat it as a resource at another layer. (i.e., Forward Adjacency concept) Hierarchical techniques. Provision a circuit at one layer, then treat it as a resource at another layer. (i.e., Forward Adjacency concept) Multi-Layer, Multi-Domain Path Computation Algorithms Multi-Layer, Multi-Domain Path Computation Algorithms Algorithms which allow processing on network graphs with multiple constraints Algorithms which allow processing on network graphs with multiple constraints Coordination between per domain Path Computation Elements Coordination 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 Ciena Subnet LSR downstream LSR upstream data flow signaling flow subnet signaling flow 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 Local Network Local Network Control PC (VLSR) Client System Control PC (VLSR) Client System routed network

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 inhttp://add

Additional Slides

Interdomain Path Computation A Hierarchical Architecture NARB summarizes individual domain topology and advertises it globally using link-state routing protocol, generating an abstract topology. NARB summarizes individual domain topology and advertises it globally using link-state routing 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.

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 Forward Per-Domain (FPD) path computation. Other supported schemes include Centralized path computation and Forward Per-Domain (FPD) path computation.

DRAGON CSPF Path Computation Heuristics A breadth first search based CSPF heuristic in deployment A breadth first search based CSPF heuristic in deployment Takes flexible combination of various constraints, such as bandwidth, switch cap., wavelength, VLAN tag and add-on policy constraints. Takes flexible combination of various constraints, such as bandwidth, switch cap., wavelength, VLAN tag and add-on policy constraints. Supports multi-region networks using configurable region- crossing criteria Supports multi-region networks using configurable region- crossing criteria Reliable results; probably time-consuming in large networks (~30ms in the 12-node HOPI+DRAGON network) Reliable results; probably time-consuming in large networks (~30ms in the 12-node HOPI+DRAGON network) Other heuristics under research; one is based on a channel-graph model in combination with K- shortest path routing. Other heuristics under research; one is based on a channel-graph model in combination with K- shortest path routing.

Three Policy Dimensions in GMPLS Service Provisioning Resource dimension Resource dimension Link availability, bandwidth capability & resource interdependence Link availability, bandwidth capability & resource interdependence TE constraints, e.g. switching cap. TE constraints, e.g. switching cap. AAA policy dimension AAA policy dimension User privileges User privileges App. specific requirements (SLA) App. specific requirements (SLA) Administration policies Administration policies Time schedule dimension Time schedule dimension Integrate and translate network resource states and policies into shared control plane intelligence. Integrate and translate network resource states and policies into shared control plane intelligence. Synergize AAA policy decision with TE based provisioning decision, resulting in fast, precise and simplified control process. Synergize AAA policy decision with TE based provisioning decision, resulting in fast, precise and simplified control process.

3 Dimensional (3D) Resource Computation Model Resource states, time schedule and AAA policies are 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

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 computation intensive resource management & policy decision tasks. RCE is the element in GMPLS control-plane to perform the computation intensive resource management & policy decision tasks. RCE can be used as a standalone server or as an integrated NARB module. RCE can be used as a standalone server or as an integrated NARB module.

3D Constraint Based Path Computation 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 AAA Policy TE Link TLV AAA Policy TE Link TLV Allows a AAA information to be included as part of path computation Allows a AAA information to be included as part of path computation Path Computation understanding/interpretation of rules very simple Path Computation understanding/interpretation of rules very simple Much work needed in this area Much work needed in this area

Time Based Provisioning Schedule TE Link TLV Schedule TE Link TLV Allows a time constraint to be included as part of path computation Allows a time constraint to be included as part of path computation

Continuing Work Key Focus Areas GMPLS Control Plane GMPLS Control Plane Inter-domain routing and signaling agreements Inter-domain routing and signaling agreements R&E community should make this a priority R&E community should make this a priority Advanced path computation techniques Advanced path computation techniques Inter-operability with vendor stacks Inter-operability with vendor stacks Multi-layer stitching Multi-layer stitching AAA and Scheduling Control Plane Features AAA and Scheduling Control Plane Features Web Service based control planes Web Service based control planes Application Specific Topologies Application Specific Topologies Integration/reconciliation of AST, Network Description Language, Common Service Definition specs Integration/reconciliation of AST, Network Description Language, 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 “horizontal” multi-layer adaptations for multi-domain

InterDomain (G)MPLS and Web Services Currently working on interdomain virtual circuit provisioning between: Currently working on interdomain virtual circuit provisioning between: ESnet ESnet Abilene Abilene HOPI HOPI UltraScience Net UltraScience Net Focusing on how to accomplish routing, signaling, path computation in a mixed (G)MPLS and Web Service environment Focusing on how to accomplish routing, signaling, path computation in a mixed (G)MPLS and Web Service environment

DRAGON Control Plane R&E “Hybrid” Networks Multi-Service, Multi-Level, Multi-Domain Multi-Service, Multi-Level, Multi-Domain One “infrastructure” which provides basic IP routed service as well services at lower layer One “infrastructure” which provides basic IP routed service 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 specific layer2 multipoint broadcast domains Services could be point to point circuits or application specific layer2 multipoint broadcast domains Interoperable architectures & control planes needed Interoperable architectures & control planes needed Integration challenges (control, data, management planes) Integration challenges (control, data, management planes) Multi-layer adaptations “horizontal” for multi-domain Multi-layer adaptations “horizontal” for multi-domain Multi-layer adaptations “vertically” for traffic grooming Multi-layer adaptations “vertically” for traffic grooming Key control plane functions: routing, signaling, path computation Key control plane functions: routing, signaling, path computation Scheduling and AAA functions also needed Scheduling and AAA functions also needed Integration of (G)MPLS and Web Services Integration of (G)MPLS and Web Services

R&E “Hybrid” Networks One “infrastructure” which provides basic IP routed service as well deterministic services at lower layer One “infrastructure” which provides basic IP routed service as well deterministic services at lower layer Services could be point to point circuits or application specific layer2 multipoint broadcast domains Services could be point to point circuits or application specific layer2 multipoint broadcast domains Multi-Service, Multi-Layer, Multi-Domain Multi-Service, Multi-Layer, Multi-Domain Emerging Hybrid Network environment is driving a new service model: Emerging Hybrid Network environment is driving a new service model: Dedicated end-to-end services will be available at the wide area edge Dedicated end-to-end services will be available at the wide area edge Challenge for GigaPoPs, Regional Optical Networks (RONs), and campuses is how to extend these services from the wide area edge across the regional networks, campus infrastructure, and to the user location. Challenge for GigaPoPs, Regional Optical Networks (RONs), and campuses is how to extend these services from the wide area edge across the regional networks, campus infrastructure, and to the user location. Techniques will depend on the details of the service offerings from the wide area R&E networks, the particular needs of the local user community, and the nature of the available regional infrastructures. Techniques will depend on the details of the service offerings from the wide area R&E networks, the particular needs of the local user community, and the nature of the available regional infrastructures.

“Hybrid” Network Service Provisioning Multiple technology options: Multiple technology options: MPLS, Ethernet, SONET, WDM, Fiber MPLS, Ethernet, SONET, WDM, Fiber Many solutions will use combinations of the above (i.e., multi- layer) Many solutions will use combinations of the above (i.e., multi- 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 options Multiple provisioning options Manual, Management Plane, Control Plane Manual, Management Plane, Control Plane Many issues including AAA, Scheduling, Service Level Agreements, Common Service Agreements, user requirements Many issues including AAA, Scheduling, Service Level Agreements, Common Service Agreements, user requirements

What About Web Services? There is value to capturing some of these control plane functions in the form of Web Services There is value to capturing some of these control plane functions in the form of Web Services For DRAGON, that would mean putting a Web Service interface into our GMPLS control plane For DRAGON, that would mean putting a Web Service interface into our GMPLS control plane Automatically processing of routing protocols Automatically processing of routing protocols The most basic web service needed is (abstracted) topology representation The most basic web service needed is (abstracted) topology representation Network Description Language (NDL) seems like a good method for topology (network graph) representations Network Description Language (NDL) seems like a good method for topology (network graph) representations Community needs to agree on a schema Community needs to agree on a schema

GMPLS and WS Control Plane Overlap Idea – All participating control planes must have a common set of topology discovery, routing, path computation and signaling functionality. Idea – All participating control planes must have a common set of topology discovery, routing, path computation and signaling functionality. Methodology – Translate the “key” GMPLS-CP functions into WS-CP counterparts in web services notations Methodology – Translate the “key” GMPLS-CP functions into WS-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 ProtocolsWS Routing Services Secure MessagingMutual TrustPolicy 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 Structure Web Service Wrappers 70

Conclusions Any control plane will have to address routing, path computation, and signaling Any control plane will have to address routing, path computation, and signaling GMPLS represents the most advanced set of thinking, concepts, and capabilities in this area GMPLS represents the most advanced set of thinking, concepts, and capabilities in this area Need to track and leverage these concepts, standards activities, and vendor implementations to the maximum extent possible Need to track and leverage these concepts, standards activities, and vendor implementations to the maximum extent possible There is value in capturing some of these functions via web services There is value in capturing some of these functions via web services Particularly topology descriptions Particularly 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 networks will use GMPLS and some use Web Services Expect a future environment where some peering networks will use GMPLS and some use Web Services Should be able to accomplish multi-domain provisioning in this environment Should be able to accomplish multi-domain provisioning in this environment This will allow interoperation between GMPLS and non-GMPLS networks (or Web Service and non-Web Service networks depending on your viewpoint) This will allow interoperation between GMPLS and non-GMPLS networks (or Web Service and non-Web Service networks depending on your viewpoint) Most participants in this community have a per domain controller/manager Most participants in this community have a per domain controller/manager We should strive to define the InterDomain communications required for both: We should strive to define the InterDomain communications required for both: GMPLS style control plane GMPLS style control plane Web Service style control plane Web Service style control plane Future will likely be mixture of both Future will likely be mixture of both

Control Plane Standards Activities

GMPLS Interdomain Routing and Signaling Solution DRAGON comparison to OIF Similar in overall concept in terms of Similar in overall concept in terms of use of hierarchical link state (OSPF derived) for routing use of hierarchical link state (OSPF derived) for routing RSVP for signaling RSVP for signaling Many differences in the details Many differences in the details Domain/Routing Controllers Domain/Routing Controllers OIF OSPF daemons are called Routing Controllers (RC); RC ID = Router ID OIF OSPF daemons are called Routing Controllers (RC); RC ID = Router ID One or more RC in each routing domain as routing speakers for the domain One 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 corresponding router and operates a dedicated instance of OSPF in a separate address space 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 space Both have adjacency via IP tunnels and control communications via separate tunnel addresses Both have adjacency via IP tunnels and control communications via separate tunnel addresses 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 add vertical hierarchies to TE topology. 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 add vertical hierarchies to TE topology. Connection End Points Connection End Points OIF UNI uses TNA w/ Node ID addresses, which introduces Reachable TNA Opaque LSA and Node ID sub-TLV into OSPF-TE advertisement OIF UNI uses TNA w/ Node ID addresses, which introduces Reachable TNA Opaque LSA and Node ID sub-TLV into OSPF-TE advertisement DRAGON uses edge router loopback IP with Local-ID, which introduces Local-ID to end users but does not add anything into the OSPF-TE DRAGON uses edge router loopback IP with Local-ID, which introduces Local-ID to end users but does not add anything into the OSPF-TE The plan is for DRAGON be become standards compliant as they mature (with hopefully interoperation with other domains providing specific requirements) The plan is for DRAGON be become standards compliant as they mature (with hopefully interoperation with other domains providing specific requirements)

Multi-Layer Infrastructures Layer 3 IPv4, IPv6, MPLS Layer 2 Ethernet, ATM Layer 1.5 SONET, GFP, VCAT, LCAS Layer 1 DWDM Diversified “Cyber-Infrastructures” DRAGONDRAGON ESNet + OSCARS ESNet DRAGONDRAGON UltraScienceNetUltraScienceNet CHEETAHCHEETAH NewNetNewNet Abilene + BRUW Abilene Application Layers Multi-media (VoIP, HDTV) E-science, grid, virtualization Virtual reality, data fusion / visualization Storage, data archive, mirroring, peer-peer

Multi-Layer / Multi-Domain Focus Scale Services Across Layers Resource Discovery Resource Discovery Hierarchical routing Multi-layer database Legacy domain (proxy) Temporal state Path Comp, Scheduling Path Comp, Scheduling Dist d / 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, vendor support Unified Inter-Layer Architecture

OIF Networking WG’s UNI, NNI specifications ITU-T SG-15, SG-13 WG Architectures, L1 VPN IETF WG’s Architectures, protocols, L1 VPN Multi-Layer / Multi-Domain Activities Liaison Activities Standards Tracking

Optical Internetworking Forum 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 (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 Dist d 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 Taskforce 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 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,MSPP IP/MPLS DWDM, TDM Horizontal link

IETF L1 VPN Framework Layer 1 VPN working group “Infrastructure virtualization”: DWDM lighpath, SONET circuit Basic and enhanced modes: signaling only vs. dist d 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 Models Differing Levels of CE-PE Functionality / Exchange

Questions? network@internet2.edu

Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN.

Similar presentations

Presentation on theme: "Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN.

Similar presentations

Presentation on theme: "Internet2 Network Tutorial: Rick Summerhill, Matt Zekauskas, Russ Hobby Internet2 Joint Techs University of Minnesota 11 February 2007 Minneapolis, MN."— Presentation transcript:

Similar presentations

About project

Feedback