1 / 17

Information Services, Topology and Discovery Working Group IS- WG

Information Services, Topology and Discovery Working Group IS- WG . Spring Member Meeting April 28th, 2009. Agenda. WG Purpose Current Status and Deployment Use-case review IP Summarization Trust models. WG Purpose.

peigi
Download Presentation

Information Services, Topology and Discovery Working Group IS- WG

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. Information Services, Topology and Discovery Working GroupIS-WG Spring Member Meeting April 28th, 2009

  2. Agenda • WG Purpose • Current Status and Deployment • Use-case review • IP Summarization • Trust models

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

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

  5. Deployment • http://dc211.internet2.edu/cgi-bin/perfAdmin/directory.cgi • http://dc211.internet2.edu/cgi-bin/perfAdmin/tree.cgi

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

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

  8. IP Summarization

  9. IP Summarization

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

  11. Discussion: Trust • Topology elements and services are registered at the edges • What is the trust model? • What is necessary?

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

  13. Authority topo

More Related