Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface: Concepts and Architecture Inder Monga Guy.

Slides:



Advertisements
Similar presentations
Research Challenges in the Emerging Hybrid Network World Tom Lehman University of Southern California Information Sciences Institute (USC/ISI)
Advertisements

© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
NSI/NML Resource and Topology Issues OGF Munich March 2010.
NSI wg Architecture Elements John Vollbrecht Internet2.
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface (NSI) Inder Monga Co-chair, Network Services.
© 2006 Open Grid Forum Network Service Interface in a Nut Shell GEC 19, Atlanta, GA Presenter: Chin Guok (ESnet) Contributors: Tomohiro Kudoh (AIST), John.
Chapter 17 Networking Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and Design Principles, 6/E William.
Implementing Inter-VLAN Routing
NORDUnet Nordic infrastructure for Research & Education LHCONE “Point-to-Point Connection Service” Service Definition Jerry Sobieski.
COS 461 Fall 1997 Networks and Protocols u networks and protocols –definitions –motivation –history u protocol hierarchy –reasons for layering –quick tour.
Grant agreement n° SDN architectures for orchestration of mobile cloud services with converged control of wireless access and optical transport network.
An evolutionary approach to G-MPLS ensuring a smooth migration of legacy networks Ben Martens Alcatel USA.
Protocols and the TCP/IP Suite Chapter 4 (Stallings Book)
ESnet On-demand Secure Circuits and Advance Reservation System (OSCARS) Chin Guok Network Engineering Group Thomas Ndousse Visit February Energy.
Abstraction and Control of Transport Networks (ACTN) BoF
Evolved from ARPANET (Advanced Research Projects Agency of the U.S. Department of Defense) Was the first operational packet-switching network Began.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
Circuit Services - IPTV Christian Todorov Internet2 Fall Member Meeting October 9, 2007.
National Science Foundation Arlington, Virginia January 7-8, 2013 Tom Lehman University of Maryland Mid-Atlantic Crossroads.
Layered Protocol. 2 Types of Networks by Logical Connectivity Peer to Peer and Client-Server Peer-to-peer Networks  Every computer can communicate directly.
1 High-Level Carrier Requirements for Cross Layer Optimization Dave McDysan Verizon.
Rick Summerhill Chief Technology Officer, Internet2 Internet2 Fall Member Meeting 9 October 2007 San Diego, CA The Dynamic Circuit.
Routing in Optical Networks Markus Isomäki IP and MPLS in Optical Domain.
A Framework for Internetworking Heterogeneous High-Performance Networks via GMPLS and Web Services Xi Yang, Tom Lehman Information Sciences Institute (ISI)
Hybrid MLN DOE Office of Science DRAGON Hybrid Network Control Plane Interoperation Between Internet2 and ESnet Tom Lehman Information Sciences Institute.
Delivering Circuit Services to Researchers: The HOPI Testbed Rick Summerhill Director, Network Research, Architecture, and Technologies, Internet2 Joint.
Department of Energy Office of Science ESCC & Internet2 Joint Techs Workshop Madison, Wisconsin.July 16-20, 2006 Network Virtualization & Hybridization.
What is Bandwidth on Demand ? Bandwidth on Demand (BoD) is based on a technology that employs a new way of managing and controlling SONET-based equipment.
Connect communicate collaborate GÉANT3 Services Connectivity and Monitoring Services by and for NRENs Ann Harding, SWITCH TNC 2010.
ASCR/ESnet Network Requirements an Internet2 Perspective 2009 ASCR/ESnet Network Requirements Workshop April 15/16, 2009 Richard Carlson -- Internet2.
TeraPaths TeraPaths: Establishing End-to-End QoS Paths through L2 and L3 WAN Connections Presented by Presented by Dimitrios Katramatos, BNL Dimitrios.
Connect. Communicate. Collaborate BANDWIDTH-ON-DEMAND SYSTEM CASE-STUDY BASED ON GN2 PROJECT EXPERIENCES Radosław Krzywania (speaker) PSNC Mauro Campanella.
OGF DMNR BoF Dynamic Management of Network Resources Documents available at: Guy Roberts, John Vollbrecht.
BGP L3VPN Virtual CE draft-fang-l3vpn-virtual-ce-01 Luyuan Fang Cisco John Evans Cisco David Ward Cisco Rex Fernando Cisco John Mullooly Cisco Ning So.
Lucy Yong Young Lee IETF CCAMP WG GMPLS Extension for Reservation and Time based Bandwidth Service.
Dynamic Lightpath Services on the Internet2 Network Rick Summerhill Director, Network Research, Architecture, Technologies, Internet2 TERENA May.
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science On Time Inder Monga, ESnet.
Copyright © Genetic Computer School 2008 Computer Systems Architecture SA Lesson 12 The TCP/IP Protocol Suite.
1 | © 2015 Infinera Open SDN in Metro P-OTS Networks Sten Nordell CTO Metro Business Group
OSCARS Roadmap Chin Guok Feb 6, 2009 Energy Sciences Network Lawrence Berkeley National Laboratory Networking for the Future of.
NSI Aggregator: Joint SURFnet/ESnet effort LHCONE Workshop CERN (Geneva, CH) Feb 10-11, 2014 NSI PCE Development Team.
© 2006 Open Grid Forum Network Services Interface Document roadmap, April 2014 Guy Roberts, Chin Guok, Tomohiro Kudoh.
Strawman LHCONE Point to Point Experiment Plan LHCONE meeting Paris, June 17-18, 2013.
IDCP and NSI: Lessons Learned, Deployments and Gap Analysis Chin Guok, Inder Monga OGF 34 Oxford, UK.
1 Network Services Interface Connection Service v2.0 Tomohiro Kudoh (AIST) (OGF NSI-WG)
Supporting Advanced Scientific Computing Research Basic Energy Sciences Biological and Environmental Research Fusion Energy Sciences High Energy Physics.
NSI Service Definition Federation of providers A group of network providers get together and decide that they wish to offer a multi-domain connection services.
1 Network Services Interface An Interface for Requesting Dynamic Inter- datacenter Networks Tomohiro Kudoh (AIST) Guy Roberts (DANTE) Inder Monga (ESnet)
ESnet’s Use of OpenFlow To Facilitate Science Data Mobility Chin Guok Inder Monga, and Eric Pouyoul OGF 36 OpenFlow Workshop Chicago, Il Oct 8, 2012.
Network No network resources exist outside a network Transport resources inside network –Link, Nodes, ports – are used to create connections between network.
NSI Topology v2.0 Version 1.2 John MacAuley, ESNET September 22, 2014 Uppsala.
© 2006 Open Grid Forum The Network Services Interface An Overview of the NSI Framework and the GLIF Automated GOLE dynamic network provisioning demonstration.
SDN controllers App Network elements has two components: OpenFlow client, forwarding hardware with flow tables. The SDN controller must implement the network.
An evolutionary approach to G-MPLS ensuring a smooth migration of legacy networks Ben Martens Alcatel USA.
Inter-Domain Network Provisioning Technology for LHC data transfer
Lifecycle Service Orchestration (LSO) Models in context
Multi-layer software defined networking in GÉANT
Dynamic Circuit Networks Topology Description Issues
(OGF NSI-WG co-chairs)
GÉANT Multi-Domain Bandwidth-on-Demand Service
NSI wg Architecture Elements
NSI Service Definition
Grid Network Services: Lessons from SC04 draft-ggf-bas-sc04demo-0.doc
Integration of Network Services Interface version 2 with the JUNOS Space SDK
Network Services Interface gateway for future network services
Evolved from ARPANET (Advanced Research Projects Agency of the U.S. Department of Defense) Was the first operational packet-switching network Began.
Network Services Interface
ECEN “Internet Protocols and Modeling”
Software interoperability in the NGN Service layer
Karthik Sethuraman, NEC
Presentation transcript:

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface: Concepts and Architecture Inder Monga Guy Roberts Tomohiro Kudoh Co-chairs, Network Services Interface-WG, OGF

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Abstraction Presentation of a simple concept to the external world

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science The Unix Socket Interface: Most Successful Data Plane Abstraction Client Process Server Process result = socket (af, type, protocol) Intresult = bind( result, addr., len) Protocol Layer Device Layer Protocol Layer Device Layer Socket Layer Socket Layer MPLS BGP OSPF IS-IS Carrier Ethernet OTN..and many more Complexity: IETF RFCs ITU-T IEEE GSM Others… Gives file system like abstraction to the capabilities of the network Hides the complexity of the network and its operation

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Abstracting Complex Network Capabilities Example: Desired Network Service = An end-to-end, multi-domain, (dynamic) circuit with (bandwidth) guarantees ESnet JGN2 I2 USLHC net MANLA N CERN NORDU net NORDU net Starlight Nether light Nether light What is the right abstraction to setup this circuit for an application/user? What are the right abstractions to view this multi-domain topology?

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Architecture: Motivation Basis for Abstraction and virtualization of the network capabilities provided to the user “Service” concept - Connection Service, Monitoring Service, Measurement Service… Per User/Domain interface - Requestor Agent makes a “Service Request” to the network Abstracts the capabilities of the network into simple to understand service requests - Connection Service Request: “Guaranteed 10Gbps Ethernet connection from A to Z, 10am - 12 pm” “Cloud” world is moving to a similar direction “Give me 5 servers for 2 days with 100TB attached storage and database capabilities” Vision much larger than multi-domain Bandwidth on Demand!

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Control PlaneManagement Plane Concept of Service Plane Inter-Network topology model is used in Service Plane. TF- Transfer Function Intra-Network topology modelled in control/Management plane using OGF NML or other model Service Plane NSA NRM NSI Transport Plane Switch Example of Physical instance of transport equipment residing on the Transport Plane STP a Network STP c STP b STP d TF Requestor Provider

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Service Plane Network Service Framework concepts Service Requestor Service Provider Network Services Interface (NSI) NSI Requestor Agent (RA) NSI Provider Agent (PA) NSA Network Service A Network Service B Network Service A Network Service B NSA = Network Services Agent NRM = Network Resource Manager Local Resources NRM Local Resources Transport Plane * Slides contain animation, does not show in pdf

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Three important concepts Recursive Framework of “requestor” and “provider” agents Abstraction of multi-layer physical topology into “service topology” “Composable” Services Model

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Recursive Framework scales over multiple Network Service Agents (NSA) Service Plane Transport Plane A B C D 7 8 Chain model Tree model Chain model Tree model ML K J I H G FE M L K J I H G F E C D B Ultimate Requestor

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Service Termination Points (STP) and Service Demarcation Points (SDP) STPs represent the external interfaces of the network domain An STP is a symbolic reference: - a Network identifier string in the higher order portion - a local STP identifier in the lower order portion SDP = interconnected STPs Abstracts the connectivity between two STPs Transfer Function (TF) indicates the internal network capabilities STP a Network STP c STP b STP d TF TF- Transfer Function N1/a N1/ b N2/ X N2/ y SDP STP a = Network + ‘a’ (local identifier)

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Service Plane Topology: Service Termination Points Service Plane represents the topological interconnects with STPs

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Multiple combinable services over the same interface (future) Basis for composable application-network service interactions Congruent with the end-to-end networking vision, and bringing campus  WAN together RARA PA Connection Service Topology Service Monitoring Service Measurement Service Protection Service …. Composable Service NSI Ex. Automated GOLE service = Connection + Verification + Topology + Monitoring Basic Network Services The Base NSI protocol has the right elements to stir innovation at the service layer

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science First NSI Service: Connection Service Connection Service = creation, management and removal of Connections (“connection lifecycle”) Connection Service Protocol = set of messages exchanged over the NSI interface to manage the connection service Leverages the recursive architecture of Network Service Agents to setup an end-to-end connection

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Connection Service Protocol Behavior of the following set of messages nailed down: Reserve Provision Release Cancel Query Major difference from existing protocols Explicit provision expected from Requestor - Provision can be before start time Duration of reservation separated from “actual use” of resources RequestorProvider reserve provision confirm Start time confirm In service Reserved period release confirm provision confirm In service

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Cancel Message Cancel message is used to remove the connection as well as the reservation Cancel message can be sent by the Ultimate Requestor (prime mover) at any time during the lifecycle of the connection Query Message Gives information about the connection service to the Requestor Agent throughout the lifecycle Works only RA  PA

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science NSI documents GFD.173 Network Services Framework The NSF is a framework to support Network Services Supports many services – initial service is Connection Service Possible future services, e.g.: Network Topology Exchange Service Published: GFD.XXX Connection Service Protocol Allows an application or network provider to request and automatically reserve and provision circuits from other network providers Designed to support circuits that transit multiple service providers Status – draft Looking for developers to implement the pre-standard 1.0 specification 16

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Thanks to the hard-working NSI contributors Very active group, worldwide contributors Conference call every week for 1.5 hours Off-line discussions (both Skype and face to face) Interim face-to-face meetings between regularly scheduled OGF meetings (3 per year)

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Why does NSI matter? DICE IDCP protocol implemented by a few networks, not all Demonstrated the power when capability is operationalized “Hybrid networks: lessons learned and future challenges based on ESnet4 experience”, IEEE Communications Magazine, May Service plane concepts and NSI architecture transcend underlying infrastructure and capability changes Optical TDM circuits, MPLS TE circuits, VLANs, E-Line, Openflow etc. Right abstractions should lead to multiple constituent services and adoption by R&E applications Not an easy challenge Can be the basis for an R&E programmable platform

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Services Interface: Summary Service Plane Abstraction of multi-layer, multi-domain, network capabilities for Users, Applications, Network Administrators Network Services Interface Base interface between requestor agent and provider agent to request and get network services Composable Services Ability to create a higher-layer, customized service with multiple network services to meet an application need. Connection Service First network service being defined carried by NSI Topology Service Candidate for the next NSI service

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Thank you! Questions? imonga at es.net, guy.roberts at dante.net, t.kudoh at aist.go.jp

Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science The Unix Socket Interface: Most Successful Data Plane Abstraction Gives file system like abstraction to the capabilities of the network Each protocol offers a set of services - the socket API provides the abstraction to access those services Hides the complexity of the network and its operation For example, a socket with af=AF_INET; type = SOCK_STREAM - Serviced by TCP/IP (default) - Application does not deal with the complexity of network, routing, TCP/IP etc. result = socket (af, type, protocol)