perfsonar development work

[Roman Łapacz <>]

 W dniu 2010-09-06 23:51, Freek Dijkstra pisze:
> > > - It is possible to describe multiple channels over a single physical
> > > interface by describing each channel with a different logical name. For
> > > example, assume that the above link between NETHERLIGHT-AMS and
> > > CANARIE-CHCG1OME2 carries 2 channels, the link logical names could be
> > > 5004LE-asd001a_ome13-1-13-2-channel-1 and
> > > 5004LE-asd001a_ome13-1-13-2-channel-2. In this case, the peering domain
> > > must also describe each channel with the same end-to-end path name
> > > (globalName) and node names.
> > mmm, I'd understand better the observation if you make some examples.
> > What do you mean with channel?
> > (If you mean for example a vlan, you could describe the vlan as an e2e...)
> - Wavelength over a fiber
> - VC-4 channel over an OC-192
> - VLAN over an Ethernet link connection
>
> (In ITU G.800 terminology: any forwarding port in a link port)

pS already allows to include the information about  ports (E2EMon does 
not support it as I guess there was no requirement to do it)

Example:

<nmwg:message
  id="msg1"
  type="SetupDataRequest"
  xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
  xmlns:nmtb = "http://ogf.org/schema/network/topology/base/20070707/";
  xmlns:nmtl2 = "http://ogf.org/schema/network/topology/l2/20070707/";>

  [...]

<nmwg:metadata id="meta1">
<nmwg:subject id="sub1">

<nmtb:node id="urn:geant.net:node=POZ:port=Gig1/0/11:vlan=100">
<nmtb:name>POZ</nmtb:name>
<nmtb:location>
<nmtb:country>Poland</nmtb:country>
<nmtb:city>Poznan</nmtb:city>
</nmtb:location>
<nmtl2:port>
<nmtl2:address>Gig1/0/11</nmtl2:address>
<nmtl2:vlan>100</nmtl2:vlan>
</nmtl2:port>
</nmtb:node>

<nmtb:node id="urn:geant.net:node=WAR:port=Gig1/0/2:vlan=100">
<nmtb:name>WAR</nmtb:name>
<nmtb:location>
<nmtb:country>Poland</nmtb:country>
<nmtb:city>Warsaw</nmtb:city>
</nmtb:location>
<nmtl2:port>
<nmtl2:address>Gig1/0/2</nmtl2:address>
<nmtl2:vlan>100</nmtl2:vlan>
</nmtl2:port>
</nmtb:node>

<nmtl2:link>
<nmtb:name>POZ-WAR</nmtb:name>
<nmtb:relation type="over">
<nmtb:nodeIdRef>urn:geant.net:node=POZ:port=Gig1/0/11:vlan=100</nmtb:nodeIdRef>
<nmtb:nodeIdRef>urn:geant.net:node=WAR:port=Gig1/0/2:vlan=100</nmtb:nodeIdRef>
</nmtb:relation>
</nmtl2:link>

</nmwg:subject>

    [...]

</nmwg:metadata>

  [...]

</nmwg:message>

(this is an example taken from the specification of AutoBAHN and pS 
integration; hope to distribute the version 1 of it very soon)

Port element could be extended (use of a new namespace; depends on the 
technology) if needed.

regards,
Roman