1 / 15

NSI Architecture Document Status and Work to be done: A view from a chair

NSI Architecture Document Status and Work to be done: A view from a chair. Inder Monga inder@es.net 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)

carol
Download Presentation

NSI Architecture Document Status and Work to be done: A view from a chair

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NSI Architecture DocumentStatus and Work to be done:A view from a chair Inder Monga inder@es.net ESNet

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

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

  4. Table of Contents (existing doc) Context and motivation 2.1Background 2.2Introducing the Service Plane 2.2.1 OGF Working Groups and documents 2.2.2 Other Standards Groups Needs description of Service plane and how it fits in with current understanding of Mangement, Control and Data/Transport Plane

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

  6. Service Plane cv cv cv

  7. Service Plane and NSILarger than just connections • Capability Service • Reservation Service • On-demand Service • Topology Service • Measurement Service • PCE Service • Multi-domain Agent PCE Service(Agent finding service) • Protection Service • …. NSI Server Module Capability Advertisement M. Agent Selection M. Aggregation Module Local RMM NSI CM NSI CM DB Service Plane NSA Agent

  8. NSA Block Architecture NSA NSI Server Module Capability Advertisement M. AFS Agent Selection M. Aggregation Module Local RMM NSI CM NSI CM DB NSI NSI NSI Network (CP, TP) 8

  9. Standards Bodies and where do they fit!

  10. Terminology and Concepts section Introduction and Overview 5 3.1Service Plane Concepts 5 3.1.1 Transport Resource 5 3.1.2 Network Service Agent 6 3.1.3 Network Resource 6 3.1.4 Requestor Agent 6 3.1.5 Network Service Interface (NSI) 6 3.2Infrastructure terminology and description 7 3.3Transport 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

  11. Architecture NSI operations 21 5.1Basic operations. 21 5.1.1 Operations of reservation service 21 5.1.2 Operations of on-demand service 22 5.2Reservation parameters 22 5.3Support of preemption 24 5.4Support of policy 24 5.5Resources 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.

  12. Architecture (contd) • 6Network Service capabilities used from other standards 25 • 6.1security 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.2resource scheduling 25 • 6.3charging, authorizing, allocating 25 • 6.4policy capabilities 25 • 6.5path computation 25 • 6.6monitoring 25 • 6.7accounting 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

  13. Architecture (contd.) • 8Fault handling 27 • 8.1Protection 27 • 8.1.1 Common Redundancy Strategies 27 • 8.1.2 Technology dependence 32 • 8.2 32 • 8.3Inter-domain (End-to-End) Protection 32 • 8.4Connection Restoration 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.

  14. Implementation and Deployment Use-Cases 9Examples and use cases [appendix?] 34 9.1GMPLS intradomain with NS agents 34 9.2Single layer networks 34 9.3Multi-layer technology networks 34 9.4Multi-layer technology with multiplexing 34 9.5Recursive 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.

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

More Related