Presentation on theme: "NSI Architecture Document Status and Work to be done: A view from a chair Inder Monga ESNet."— Presentation transcript:
NSI Architecture Document Status and Work to be done: A view from a chair Inder Monga email@example.com ESNet
Goal of the Architecture Doc. Promote uniform understanding of the motivations behind the NSI interface within OGF and beyond OGF (within other standard bodies) Requirements that drive formation of consistent protocols/service interface specifications.
NSI Architecture Specification Four high-level sections – Context and Motivation Why NSI? How does it fit in with the rest of the well-established network concepts? – Terminology and Concepts New language to discuss architecture and interactions – Architecture – Lots of stuff here NSA Block Diagram and interactions Service interactions with other network services Requirements on provisionable services Security, Fault tolerance, Multi-domain.. – Implementation and Deployment Use Cases Case studies on possible deployments of NSI interface and NSA. Application examples using NSI
Needs description of Service plane and how it fits in with current understanding of Mangement, Control and Data/Transport Plane Table of Contents (existing doc) CONTEXT AND MOTIVATION 2.1B ACKGROUND 2.2I NTRODUCING THE S ERVICE P LANE 2.2.1OGF W ORKING G ROUPS AND DOCUMENTS 2.2.2O THER S TANDARDS G ROUPS
Service Plane The ServicePlane refers to the set of systems and processes that are geared towards providing services to users and maintaining state on those services. The Service plane will generally rely on the functions of the ControlPlane and/or ManagementPlane to effect actual changes on the DataPlane. In addition, the ServicePlane will typically maintain databases on current and future service instantiations and coordinate associated workflow processes.
Service Plane and NSI Larger than just connections NSA Agent NSA Agent NSI CM NSI CM Local RMM Capability Advertisement M. DBDB Agent Selection M. Aggregation Module NSI Server Module Capability Service Reservation Service On-demand Service Topology Service Measurement Service PCE Service Multi-domain Agent PCE Service (Agent finding service) Protection Service …. Service Plane
NSA Block Architecture 8 NSI CM NSI CM Local RMM Network (CP, TP) Capability Advertisement M. NSI NSA AFS DB Agent Selection M. Aggregation Module NSI Server Module
Terminology and Concepts section INTRODUCTION AND OVERVIEW5 3.1S ERVICE P LANE C ONCEPTS 5 3.1.1T RANSPORT R ESOURCE 5 3.1.2N ETWORK S ERVICE A GENT 6 3.1.3N ETWORK R ESOURCE 6 3.1.4R EQUESTOR A GENT 6 3.1.5N ETWORK S ERVICE I NTERFACE (NSI)6 3.2I NFRASTRUCTURE TERMINOLOGY AND DESCRIPTION 7 3.3T RANSPORT PLANE OVERVIEW AND NAMING DESCRIPTION 11 3.4Use NML model and naming where possible Need to nail down the terminology ASAP based on working group at OGF 27 NSI create the terminology and take it to NML Need to nail down the terminology ASAP based on working group at OGF 27 NSI create the terminology and take it to NML
Architecture NSI OPERATIONS21 5.1B ASIC OPERATIONS.21 5.1.1O PERATIONS OF RESERVATION SERVICE 21 5.1.2O PERATIONS OF ON - DEMAND SERVICE 22 5.2R ESERVATION PARAMETERS 22 5.3S UPPORT OF PREEMPTION 24 5.4S UPPORT OF POLICY 24 5.5R ESOURCES VS CONNECTIONS 24 Needs to be significantly modified. It should have Services offered, impact of that service on NSI operations, and block diagram/other dependencies in the network.
Architecture (contd) 6NETWORK SERVICE CAPABILITIES USED FROM OTHER STANDARDS25 6.1 SECURITY AND TRUST 25 6.1.1 TRANSPORT LAYER SECURITY 25 6.1.2 SERVICE LAYER SECURITY 25 6.1.3 ATTRIBUTE AUTHENTICATION AND AUTHORIZATION 25 6.2 RESOURCE SCHEDULING 25 6.3 CHARGING, AUTHORIZING, ALLOCATING 25 6.4 POLICY CAPABILITIES 25 6.5 PATH COMPUTATION 25 6.6 MONITORING 25 6.7 ACCOUNTING 25 Security Considerations section should be a dedicated section Dependent services like Path Computation, if not in scope, should be discussed in the previous section Security Considerations section should be a dedicated section Dependent services like Path Computation, if not in scope, should be discussed in the previous section
Architecture (contd.) 8FAULT HANDLING27 8.1P ROTECTION 27 8.1.1C OMMON R EDUNDANCY S TRATEGIES 27 8.1.2T ECHNOLOGY DEPENDENCE 32 8.232 8.3I NTER - DOMAIN (E ND - TO -E ND ) P ROTECTION 32 8.4C ONNECTION R ESTORATION 33 The contents of this section needs to move to appendix or integrated with operational issues. The failure implications of the agents themselves need to be discussed in this section.
Implementation and Deployment Use- Cases 9EXAMPLES AND USE CASES [APPENDIX?]34 9.1GMPLS INTRADOMAIN WITH NS AGENTS 34 9.2S INGLE LAYER NETWORKS 34 9.3M ULTI - LAYER TECHNOLOGY NETWORKS 34 9.4M ULTI - LAYER TECHNOLOGY WITH MULTIPLEXING 34 9.5R ECURSIVE NS AGENTS 34 Use-cases utilizing the NSI interface should be discussed here to provide a case- study based mechanism for people to understand an instantiation of the architecture.
Proposed Timeline Architecture Doc By OGF28 – final draft document, ready to go to GFD editors. No open discussion items – GHPN hosts any researchy architecture discussions like best way to implement a agent path-finding service Final first draft by end December 2009?