May 22 2007 - TNC2007 Network Description Language - Semantic Web for Hybrid Networks Network...

Network Description Language - Semantic Web for Hybrid Networks May 22 2007 - TNC2007

Network Description Language:

Semantic Web for Hybrid NetworksPaola Grosso

Universiteit van AmsterdamSNE group


Outline of presentation

• Hybrid networks and lightpaths

• Semantic Web and RDF

• NDL - Network Description LanguageCurrent status:

• The schemas• The applications

• Future work


Hybrid networks

In the NREN world we see:

Hybrid networks:IP services and dedicated optical connections on the same

infrastructure;Suited for the new e-Science applications in need of

guaranteed network services (think of Tier structure for CERN/LHC experiments).

Lightpaths:Dedicated optical connections;Static or dynamic;User-controlled.

Provisioning:Development of control plane and management planes.


SURFnet6 and StarPlane

Example of lighpaths close to us:• CPL - Common Photonic Layer - in SURFnet6;• StarPlane network

Dordrecht1

Breda1

Tilburg1

DenHaag

NLR

BT

BT NLR

BT

Zutphen1

Lelystad1

Subnetwork 4:Blue Azur

Subnetwork 3:Red

Subnetwork 1:Green

Subnetwork 2:Dark blue

Subnetwork 5:Grey

Emmeloord

Zwolle1

Venlo1

Enschede1

Groningen1

LeeuwardenHarlingen

Den Helder

Alkmaar1

Haarlem1

Leiden1

Assen1

Beilen1

Meppel1

Emmen1

Arnhem

Apeldoorn1

Bergen-op-ZoomZierikzee

Middelburg

Vlissingen Krabbendijke

Breukelen1

Ede

Heerlen2Geleen1

DLO

Schiphol-Rijk

Wageningen1 Nijmegen1

Hilversum1

Hoogeveen1

Lelystad2

Amsterdam1

Dwingeloo1

Amsterdam2

Den Bosch1

Utrecht1

Beilen1

Nieuwegein1Rotterdam1

Delft1

Heerlen1

Heerlen1

Maastricht1

Eindhoven1

Maasbracht1

Rotterdam4

3XLSOP

IBG1 & IBG2Middenmeer1

On StarPlane see Cees de Laat talk tomorrow

Which (level of) topology overview does an application need?


GLIF

The Global Lambda Integrated Facility (www.glif.is):Multi-domain, multi-vendor international lightpaths.

How do domains exchange information on network topologies?

Which topology?


A common network description

Topology information is needed to provision lightpaths:

By user/applications to describe the type of lightpaths suiting their needs, to understand what are the possible connections

By control plane and provisioning systems to exchange information at domain’s boundaries to extend paths

The idea: NDL - Network Description Language - an RDF based network description provides the common vocabulary to users/applications and providers/control planes.


Semantic Web and RDF

Semantic Web organizes data so that is contains ‘meaning’ that can be understood by machines and applications.

RDF - Resource Description Framework - provides a way to categorize information:- resources are described by URIs;- triplets define the relations between resources:

ObjectSubjectPredicate


RDF in hybrid networksConcept of indendently maintained distributed information

fits the hybrid networking world and its different administrative domains.

References between resources, both internally to a document and externally with the use of URIs.

Leverage existing RDF tools.

Domain ANDL

Domain BNDL

seeAlso()


NDL schemas• Topology schema

describes devices, interfaces, links and connections between them on a single layer.

• Layer schemadescribes specific network technologies and the relation

between network layers.• Capability schema

describes device capabilities.• Domain schema

describes administrative domains, services within a domain and how to give an abstracted view of the network in a domain.

• Physical schemadescribes the physical aspects of network elements.

• Plus nine technology schemata.


Topology schema

A vocabulary for defining network topology on a single layer.


Layer schema

The multilayer problem

A vocabulary for defining network layers and interrelations between layer networks.


Domain schema

A vocabulary for defining administrative network domains, and abstracted views of devices in a domain.


Tools

<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#” xmlns:ndl="http://www.science.uva.nl/research/sne/ndl#” xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"><ndl:Location rdf:about="#Amsterdam1.netherlight.net"> <ndl:name>Netherlight Optical Exchange</ndl:name> <geo:lat>52.3561</geo:lat> <geo:long>4.9527</geo:long></ndl:Location><ndl:Device rdf:about="#tdm3.amsterdam1.netherlight.net"> <ndl:name>tdm3.amsterdam1.netherlight.net</ndl:name> <ndl:locatedAt rdf:resource="#Amsterdam1.netherlight.net"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/1"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/2"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/3"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:501/4"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:502/1"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:502/2"/> <ndl:hasInterface rdf:resource="#tdm3.amsterdam1.netherlight.net:502/3"/>>

NDL file

<ndl:Interface rdf:about="#tdm3.amsterdam1.netherlight.net:501/3"> <ndl:name>tdm3.amsterdam1.netherlight.net:501/3</ndl:name> <ndl:connectedTo rdf:resource="http://networks.internet2.edu/manlan/manlan.rdf#manlan:if1"/> <ndl:capacity rdf:datatype="http://www.w3.org/2001/XMLSchema#float">1.244E+9</ndl:capacity></ndl:Interface><ndl:Interface rdf:about="http://networks.internet2.edu/manlan/manlan.rdf#manlan:if1"> <rdfs:seeAlso rdf:resource="http://networks.internet2.edu/manlan/manlan.rdf"/>


Applications: maps


Applications: path finding


Applications: monitoring


Future work

Policy integrationEach lightpath needs to be authorized.Provide pointers from NDL to AAA policies for each

hybrid domain

Domain abstractionsWhich level of insight into topology is needed when

crossing domain boundaries?Provide abstractions of domain, collapsed views of

internal


NML-WG

To exchange ideas with other group developing similar schemas and to work toward a a common/standardized schema:

Network Markup Language Working Group in OGF.Chairs: Paola Grosso (UvA) and Martin Swany (U

Delaware)

https://forge.gridforum.org/sf/projects/nml-wg


The bigger picture

The advantage of a semantic approach: an answer to the end2end problem where service integration requires multiple resources coordination.

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

Orchestration of ontologies: distribution of on-demand video.


Conclusions

Lightpath finding, provisioning and troubleshooting are central issues in hybrid networks.

NDL provides solutions for:

- Interdomain topology exchange

- Network maps

- Lightpath monitoring

- Lightpath provisioning

Based on RDF, NDL is extensible and integrates with other independent ontologies.


ReferencesDetailed information available on NDL web page:http://www.science.uva.nl/research/sne/ndl/

NDL mailing list:ndlt <at> science.uva.nl(contact vdham <at> science.uva.nl>

We thank our colleagues Andree Toonk and Ronald van der Pol from SARA and Franco Travostino from eBay (formerly NORTEL).

This work is supported by SURFnet, the BSIK GigaPort project and TNO.

Questions?

May 22 2007 - TNC2007 Network Description Language - Semantic Web for Hybrid Networks Network...

Documents

Transcript of May 22 2007 - TNC2007 Network Description Language - Semantic Web for Hybrid Networks Network...