1. 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

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

3. 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: 6000+ 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

4. 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?

5. 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!

6. 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

7. 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

8. 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

9. Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Recursive Framework scales over multiple Network Service Agents (NSA) Service Plane Transport Plane 34 5 6 1 2 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

10. 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)

11. 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

12. 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

13. 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

14. 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

15. 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

16. 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: http://www.ogf.org/documents/GFD.173.pdf: http://www.ogf.org/documents/GFD.173.pdf 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

17. 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)

18. 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 2011 - http://goo.gl/Lc3u4 http://goo.gl/Lc3u4 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

19. 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

20. 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 http://www.gridforum.org/gf/group_info/view.php?group=nsi-wg

21. 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)