Information Services, Topology and Discovery Working Group

IS-WG

Winter Joint TechsFebruary 1st, 2010

Agenda

• WG Purpose• Current Status and Deployment• Use-case review• Topology Document• IS Architecture– IP Summarization– Query models– Database technology– Trust models

WG Purpose• Various network services use a common "Information Services plane" that allows users

to discover network topology and the location and capabilities of network services within that topology. As global federation of network services occurs, the standardization and flexibility of the network-centric Information Services becomes even more critical

• Currently, the same infrastructure is used by– DCN/ION– perfSONAR– Phoebus data movement service

• In order to help catalyze and focus the development of these common information services, the Internet2 Network Advisory Committee (NTAC) has commissioned the creation of this working group

• The group will work to – further define the role and functionality of Information Services– drive design and development– Interface with standards and community organizations (IETF, OGF, GLIF)

Ongoing Tasks

• Discuss and “publish” topology schema document – Consistent with DCN 0.5+ and perfSONAR-PS 3.1– Identifying differences– Formalize terminology

Current Status

• As part of perfSONAR, we have defined a common IS for network services

• What are the requirements?– Represent services with network context

• We have a topology schema that helps address this

Deployment

• http://www.perfsonar.net/activeServices• http://www.perfsonar.net/activeServices/IS

Use cases• Control Plane– Host discovery– Service discovery– Pathfinding

• Performance Measurement– Archived data discovery– Measurement point discovery

• Network topology abstractions– “What is close?”– This includes proximity to the querier, proximity to a path,

proximity to another resource

Use cases• Control Plane– Host discovery– Service discovery– Pathfinding

• Performance Measurement– Archived data discovery– Measurement point discovery

• Network topology abstractions– “What is close?”– This includes proximity to the querier, proximity to a path,

proximity to another resource

IP Summarization

IP Summarization

IP Summarization Status

• Ongoing work on the algorithm• Tension between “close” summarization and

broad summarizations• Can we augment the IS model with CIDR-style

queries– Longest match– All matches– Exact macheshttp://code.google.com/p/perfsonar-ps/wiki/IPSummarization

Discussion: Trust

• Topology elements and services are registered at the edges

• What is the trust model? • What is necessary?

Trust Issues

• Hypothesis: Information is more valuable if it is signed by whomever registers it– “Who says?”

• We might add “Authority” to Authentication, Authorization

• If topology is signed, how can it be validated?• Is a chain of agents sufficient?

Authority

topo