Operating Framework of Connection Networks

Slides:



Advertisements
Similar presentations
Authentication Authorization Accounting and Auditing
Advertisements

© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
© 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.
Organizational Governance
Internal Control–Integrated Framework
Lawrence Berkeley National LaboratoryU.S. Department of Energy | Office of Science Network Service Interface (NSI) Inder Monga Co-chair, Network Services.
Chapter 14 Fraud Risk Assessment.
© 2006 Open Grid Forum Network Service Interface in a Nut Shell GEC 19, Atlanta, GA Presenter: Chin Guok (ESnet) Contributors: Tomohiro Kudoh (AIST), John.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Unit 1: Introductions and Course Overview Administrative Information  Daily schedule  Restroom locations  Breaks and lunch  Emergency exit routes 
<<replace with Customer Logo>>
Public Private Partnerships MUNICIPAL PPP CONFERENCE Date: 18 February 2010.
OASIS Reference Model for Service Oriented Architecture 1.0
A credit union authority to invest in derivatives is limited to and has been granted exclusively for the purpose of reducing interest rate risk exposure.
Trust Framework for Multi-Domain Authorization Internet2 Spring Meeting Arlington April 25 th 2012 Leon Gommans:
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Introduction to Internal Control Systems
Information Assurance The Coordinated Approach To Improving Enterprise Data Quality.
Introduction In 1992, the Committee Of Sponsoring Organizations of the Treadway Commission (COSO) published Internal Control-Integrated Framework (1992.
Roles and Responsibilities
D u k e S y s t e m s A Tale of Two Federations Jeff Chase Duke University.
DRAFT – For Discussion Only HHSC IT Governance Executive Briefing Materials DRAFT April 2013.
Maintaining Network Health. Active Directory Certificate Services Public Key Infrastructure (PKI) Provides assurance that you are communicating with the.
OGF DMNR BoF Dynamic Management of Network Resources Documents available at: Guy Roberts, John Vollbrecht.
Introduction to Semantic Web Service Architecture ► The vision of the Semantic Web ► Ontologies as the basic building block ► Semantic Web Service Architecture.
© 2006 Open Grid Forum Network Services Interface OGF 32, Salt Lake City Guy Roberts, Inder Monga, Tomohiro Kudoh 16 th July 2011.
Chapter 3 Governance.
Internal Control Systems
Authorization GGF-6 Grid Authorization Concepts Proposed work item of Authorization WG Chicago, IL - Oct 15 th 2002 Leon Gommans Advanced Internet.
HIT Policy Committee NHIN Workgroup HIE Trust Framework: HIE Trust Framework: Essential Components for Trust April 21, 2010 David Lansky, Chair Farzad.
Company: Cincinnati Insurance Company Position: IT Governance Risk & Compliance Service Manager Location: Fairfield, OH About the Company : The Cincinnati.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Dynamic Network Services In Internet2 John Vollbrecht /Dec. 4, 2006 Fall Members Meeting.
Copyright © 2007 Pearson Education Canada 9-1 Chapter 9: Internal Controls and Control Risk.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Operating Framework of Connection Networks OGF/NSI Working Group Chicago Oct. 10, 2012 John Vollbrecht & Leon Gommans University of Amsterdam.
GEANT OpenCall – NSI CONTEST NSI CONTEST – Demonstrator Giacomo Bernini Nextworks GENI Networking Conference 22, March 2015, Washington DC.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
ONAP SD-WAN Use Case Proposal.
Implementation Plan I want to plan a project
Chapter 6: Interoperability
Managing the Delivery of Information Services
Authority Recognition GGF9
Dynamic Network Services In Internet2
Understanding the Principles and Their Effect on the Audit
NSI wg Architecture Elements
Grid Resource Allocation Agreement Protocol Working Group
Grid Network Services: Lessons from SC04 draft-ggf-bas-sc04demo-0.doc
Network Services Interface Working Group
Measuring Outcomes of GEO and GEOSS: A Proposed Framework for Performance Measurement and Evaluation Ed Washburn, US EPA.
Network Services Interface
Brief Introduction to IEEE P802.1CF
Chapter 12 Implementing strategy through organization
Internal control - the IA perspective
Brief Introduction to OmniRAN P802.1CF
UNDERSTANDING….. THE GRC FRAMEWORK.
Update - Security Policies
Network Services Interface Working Group
IEEE 802 Scope of OmniRAN Abstract
Chapter 12 Implementing strategy through organization
An overview of Internal Controls Structure & Mechanism
Introduction to SOA Part II: SOA in the enterprise
Hyperledger Fabric 소개 및 튜토리얼
Ponder policy toolkit Jovana Balkoski, Rashid Mijumbi
Presentation transcript:

Operating Framework of Connection Networks OGF/NSI Working Group Chicago Oct. 10, 2012 John Vollbrecht Leon Gommans

Quick Introduction This presentation is intended to help provide a basis for defining AA requirements for NSI We would like feedback about whether this helps promote NSI AA and what could be improved or explained better This presentation uses the Network Provider Group [NPG] Framework to describe the organization of a group of provider networks collaborating to create connections between edgepoints of the networks NPG is an instance of Service Provider Group [SPG] Framework which has been developed by examining services provided by groups of autonomous organizations The NPG Framework describes how a group of network organizations can collaborate to provide connections between edge points

Network Provider Group Basics NPG is a group of network providers organized to offer connections to users NPG has two dimensions User view Provider view Three functional levels + oversight Enterprise (managerial) Policy operational

NPG Dimensions User view – Provider view User gets connedtion from NPG Includes provider nets, service providers such as topology, pathfinding, monitoring. Policy

NPG User Dimension

NPG Provider View NPG is overlay on set of Providers NPG coordinates agents to provide service Provider org may be part of more than one NPG Mapping to NSI terms Admin – provider org Policy – NSA NOC – NRM Actions may be human or automated or combination

NPG Provider Dimension Mapping to NSI Conn. Service Topology Service Discover Service Monitor Service NPG Service NSI Framework NSA CS State Mach. TS State Mach. MS State Mach. NPG State Mach NPG Policies TSDB Blue is addition to Inder’s slide NSA NRM Modified from Inder’s slides from Delft Blue boxes show NPG services – Green services coordinated by NPG

NPG Levels Enterprise level - management Policy level – NSA level Defines, builds and monitors business architecture of collaborating providers Includes managers of each network and service providers as well as NPG manager Each enterprise actor reports to the principal of its organization Policy level – NSA level executes policy using infrastructure and rules defined at Enterprise level Monitors Policy level for compliance with Enterprise rules Each policy actor reports to its enterprise owner Policy actors specify connections to participating operation level Operation control level – NRM level Provides connection specified by Policy level using infrastructure defined by Enterprise Level Operates using infrastructure and rules defined at Enterprise level Instantiates Connections specified by Policy level Monitors and reports on connection compliance with policy and enterprise rules Infrastructure could be all computerized, all human or some combination

NPG Assumptions Provider preconditions Organization of NPG A set of interconnected networks- potential provider networks Each provider net has an operation level NOC/ NRM Each provider network has a Policy Agent / NSA Each network has a business manager agent at enterprise level NPG coordinates a group of networks and service providers Each organization, including NPG, has a principal and associated Directorate which is accountable for its activities NPG has agents that enable and monitor functions at all levels NPG uses Service providers [e.g. topology server] are used by NPG to enable NPG functions

Principal/Directorate and Accountability Every organization has a principal that is accountable to other principals The Principal may have a “Directorate” that acts at an executive level for the Principal A principal may act alone, or may have an organization to whom it delegates functional responsibility Principals of organizations are ultimately responsible for defining and executing policy and are accountable for the results of policy. Principals of organizations participating in an NPG delegate authority to enterprise agents who in turn delegate some of their authority to policy and operation agents When acting for a principal, an agent must be demonstrate that it has been delegated the authority from the principal. Principal is the head of the authority chain for the organization NPG Agents report on performance of functional activity so that Principal can take corrective action as needed Is this slide needed?

Mutiple Networks and Multiple NPGs NPGs can be created using the same Provider networks Having a number of networks with standard agents means they are able to join different NPGs as appropriate

NPG Principal/Directorate An NPG Principal is created when an NPG is created An NPG Principal is ultimately accountable for commitments the NPG makes to users and for enforcing agreements among members NPG Principal could be a corporation operating the way MasterCard and Visa coordinates CC services for banks Could be an executive group formed by a set of networks – perhaps formed by GLIF Could an executive from a group of National networks who interconnect to provide service to other nets NPG Principal creates NPG Directorate with agents NPG delegates authority to its agents Raci matrix – responsible, accountable, consulted, informed See wikipedia

Service Agreements Principals risk/reward The Principal of each organization is responsible for service performance, and accepts risks with associated rewards and penalties. In a small business it might be the owner In a corporation it is the board of directors The principal delegates responsibility to agents, is accountable for agent actions Service agreements are between principals Service agreements define how costs and benefits are allocated An agent must be able to prove it is acting for (authorized by) a particular principal to participate in protocol between agents Principal of group is accountable to the group use to lead into what the principal of NPG does

Authorization and Responsibility

Risks and Rewards For the principal of an NPG two basic types of risk exist - it is accountable to user for both, allocates partial responsibility and liability to providers Business Risk e.g. Use may not be as high as expected or may use some feature more than expect This is a Risk evaluated at Enterprise level Operational Risk e.g Infrastructure may refuse valid requests or may not be able to handle the volume of requests or may accept fraudulent requests This is a risk of infrastructure and protocol Infrastructure and protocol can limit cost of risk Enforcement of operational requirements can limit cost of risk

Summary Multiple networks collaborating to provide connections to users - need an NPG to define and oversee how they collaborate NPG agents are in all three levels NPG Principal is accountable for connections provided by NPG NPG functional infrastructure is protocol based, but may be all human, all automated or some combination evolving

Thanks for listening Questions? Some that might be good to discuss Is it really necessary for NPG to have its own principal Can the same topology service be used by multiple NPGs? is it possible to define authority chain needed in Policy level messages in PKI terminology? What does the above mean? What does the Enterprise level really do?