perfsonar development work

Author: hans.trompert
Date: 2007-08-08 07:27:01 -0400 (Wed, 08 Aug 2007)
New Revision: 2602

Modified:
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-flowStatistics.xml
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-rawFlows.xml
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-topFlows.xml
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-flowStatistics.xml
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-rawFlows.xml
   
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-topFlows.xml
Log:
Updated all sample messages to match the recent changes to FlowsaMA.rnc

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-flowStatistics.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-flowStatistics.xml
     2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-flowStatistics.xml
     2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,4 +1,5 @@
 <!-- 
+
 FlowSA SetupDataRequest-flowStatistics (Client -> Service Request)
 
 version 0.0, 14 March 2007, Jason Zurawski, initial proposal
@@ -12,88 +13,49 @@
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos
+version 0.11, 27 July 2007, Hans Trompert, changed flowVersion and 
sampleRate parameters into router properties, allowed for multiple nodes in 
flow subject
+version 0.12, 27 July 2007, Jason Zurawski, Both changes should be reversed; 
you can accomplish multiple routers with chaining, and the flow properties 
you havbe added describe software of a node, not the node itself.  
+version 0.13, 07 Aug 2007, Hans Trompert, reversed changes made in version 
11, now using RouterGroup (== BaseNetwork) as a subject, cleanup
+version 0.14, 08 Aug 2007, Hans Trompert, minor edit
 
 This request will return statistical information about the selected
-flows from the given router(s).  For the moment, more information can be
-found at:
+flows from the given router(s).
 
-       
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_flow_statistics
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-       - hostName: the name of the router for which we are holding flow
-         information. This is preferably the official name of the
-         router, usually this is the DNS name that is associated with
-         the loopback0 interface.
-
-       - description: description of the router (optional)
-
-       - operSys: operating system running on the router (optional)
-
-       - institution: institution this routers belongs to (optional)
-       
-       - city, country, latitude and longitude: location of the router
-         (optional)
-        
-       - flowVersion: the flow information export format used by the
-         router, for now we support the following versions:
-               - netflow_v5
-               - netflow_v9
-               - ipfix
-               - sflow
-                
-       - sampleRate: the packet sample rate, if any, that is being used
-         by the router before flow accounting is done, for example:
-               - sampleRate = 100 if only 1 out of every 100 packets is
-                 sent to the router internal accounting process
-               - sampleRate = 1 if every 1 out of 1 packets is sent to
-                 the router internal accounting process (all packets
-                 are accounted for)
-
-       The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can
-       be used to specify a startTime and endTime to limit the number
-       of flows to a specific time range.
-
-Data:
-
-       The response of this request will contain the requested
-       information, see SetupDataResponse-flowStatistics.
-
 -->
-
 <nmwg:message type="SetupDataRequest" id="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
   xmlns:flow="http://ggf.org/ns/nmwg/tools/flow/2.0/";
+  xmlns:stat="http://ggf.org/ns/nmwg/tools/flow/stat/2.0/";
   xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";
   xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";
   xmlns:nmtm="http://ggf.org/ns/nmwg/time/2.0/";>
 
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
-    <nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
-      <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
-      <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
+    
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/stat/2.0/</nmwg:eventType>
   </nmwg:metadata>
 
   <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
+    <stat:subject id="statsub1" metadataIdRef="meta1"/>
+    <stat:parameters id="statparamid1"/>
+  </nmwg:metadata>
+
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
     <select:parameters id="selectparamid1">
       <nmwg:parameter name="startTime">
         <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
@@ -104,6 +66,6 @@
     </select:parameters>
   </nmwg:metadata>
 
-  <nmwg:data id="data1" metadataIdRef="meta2"/>
+  <nmwg:data id="data1" metadataIdRef="meta3"/>
 
 </nmwg:message>

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-rawFlows.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-rawFlows.xml
   2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-rawFlows.xml
   2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,4 +1,5 @@
 <!-- 
+
 FlowSA SetupDataRequest-rawFlows (Client -> Service Request)
 
 version 0.5, 30 May 2007, Hans Trompert, initial proposal, modelled after 
FlowS&A-SetupDataRequest-flowStatistics-v0.5.xml
@@ -8,101 +9,18 @@
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos, added 
subnamespace raw
+version 0.11, 07 Aug 2007, Hans Trompert, now using RouterGroup (== 
BaseNetwork) as a subject, cleanup
+version 0.12, 08 Aug 2007, Hans Trompert, fixed eventType
 
 This request will return information about all flows whithin the specified
 time range from the given router(s), the flows are optionally filtered on
-the basis of there content or aggregated as specified.  For the moment, more
-information can be found at:
+the basis of there content or aggregated as specified.
 
-        
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_raw_flows
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-        - hostName: the name of the router for which we are holding flow
-          information. This is preferably the official name of the router,
-          usually this is the DNS name that is associated with the loopback0
-          interface.
-
-        - description: description of the router (optional)
-
-        - operSys: operating system running on the router (optional)
-
-        - institution: institution this routers belongs to (optional)
-
-        - city, country, latitude and longitude: location of the router
-          (optional)
-
-        - flowVersion: the flow information export format used by the
-          router, for now we support the following versions:
-                - netflow_v5
-                - netflow_v9
-                - ipfix
-                - sflow
-
-        - sampleRate: the packet sample rate, if any, that is being used by
-          the router before flow accounting is done, for example:
-                - sampleRate = 100 if only 1 out of every 100 packets is
-                  sent to the router internal accounting process
-                - sampleRate = 1 if every 1 out of 1 packets is sent to the
-                  router internal accounting process (all packets are
-                  accounted for)
-
-        The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can be
-        used to specify a startTime and endTime to limit the number of flows
-        to a specific time range.
-
-        The folowing parameters can be used to filter and/or aggregate the
-        flows:
-
-        - aggregationRule: any valid Nfdump style aggregation rule, for
-          example:
-                - aggregate source IP address and destination port:
-                  'srcip,dstport'
-                - aggregate flows from the same /24 IPv4 source IP and
-                  destination port: 'srcip4/24,dstport'
-
-        - filterRule: any valid Nfdump style filter rule, for example:
-                - 'tcp and ( src ip 172.16.17.18 or dst ip 172.16.17.19 )' 
-                - 'in if 5 and net 10.0.0.0/24 and not host 10.0.0.1 and bps 
> 10k and duration < 100 and dst port 1433' 
-        
-        The parameters below specify which flow information fields are
-        returned, this is mainly intended to reduce the amount of data that
-        has to be returned, so please specify only those fields you really
-        need. One or more can of the folowing parameters can be selected:
-
-        - showFieldAddressFamily   PF_INET or PF_INET6
-        - showFieldTimeFirstSeen   UNIX time seconds
-        - showFieldMsecFirstSeen   Mili seconds first seen
-        - showFieldTimeLastSeen    UNIX time seconds
-        - showFieldMsecLastSeen    Mili seconds first seen
-        - showFieldProtocol        Protocol
-        - showFieldSrcAddress      Src address as 4 consecutive 32bit 
numbers.
-        - showFieldSrcPort         Src port
-        - showFieldDstAddress      Dst address as 4 consecutive 32bit 
numbers.
-        - showFieldDstPort         Dst port
-        - showFieldSrcAS           Src AS number
-        - showFieldDstAS           Dst AS number
-        - showFieldInputIF         Input Interface
-        - showFieldOutputIF        Output Interface
-        - showFieldTcpFlags        TCP Flags
-                                   000001 FIN.
-                                   000010 SYN
-                                   000100 RESET
-                                   001000 PUSH
-                                   010000 ACK
-                                   100000 URGENT
-                                   e.g. 6 => SYN + RESET
-        - showFieldTos             Type of Service
-        - showFieldPackets         Number of packets
-        - showFieldBytes           Number of bytes
-
-Data:
-
-        The response of this request will contain the specified fields of
-        the flows that matched the query, see SetupDataResponse-rawFlows.
-
 -->
 <nmwg:message type="SetupDataRequest" id="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
@@ -114,40 +32,20 @@
 
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
     
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/raw/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
-      <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
-      <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
   </nmwg:metadata>
 
   <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
-    <select:parameters id="selectparamid1">
-      <nmwg:parameter name="startTime">
-        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
-      </nmwg:parameter>
-      <nmwg:parameter name="endTime">
-        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
-      </nmwg:parameter>
-    </select:parameters>
-  </nmwg:metadata>
-
-  <nmwg:metadata id="meta3">
-    <raw:subject id="rawsub1" metadataIdRef="meta2"/>
+    <raw:subject id="rawsub1" metadataIdRef="meta1"/>
     <raw:parameters id="rawparamid1">
       <nmwg:parameter name="aggregationRule">srcip,dstport</nmwg:parameter>
       <nmwg:parameter name="filterRule">port = 80</nmwg:parameter>
@@ -172,6 +70,18 @@
     </raw:parameters>
   </nmwg:metadata>
 
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
+    <select:parameters id="selectparamid1">
+      <nmwg:parameter name="startTime">
+        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
+      </nmwg:parameter>
+      <nmwg:parameter name="endTime">
+        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
+      </nmwg:parameter>
+    </select:parameters>
+  </nmwg:metadata>
+
   <nmwg:data id="data1" metadataIdRef="meta3"/>
 
 </nmwg:message>

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-topFlows.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-topFlows.xml
   2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataRequest-topFlows.xml
   2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,4 +1,5 @@
 <!-- 
+
 FlowSA SetupDataRequest-topFlows (Client -> Service Request)
 
 version 0.5, 30 May 2007, Hans Trompert, initial proposal, modelled after 
FlowS&A-SetupDataRequest-rawFlows-v0.5.xml
@@ -7,87 +8,16 @@
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos, updated 
Metadata explanation to match message, added subnamespace top to namespace 
flow and updated the subject of the metadata block containing the paramters 
that are specific to this request accordingly.
+version 0.11, 07 Aug 2007, Hans Trompert, now using RouterGroup (== 
BaseNetwork) as a subject, cleanup
+version 0.12, 08 Aug 2007, Hans Trompert, fixed eventType, matched query 
interval to data in response message
 
 This request will return the Top N flow or flow element statistics.
-For the moment, more information can be found at:
 
-       
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_top_flow_information
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-        - hostName: the name of the router for which we are holding flow
-          information. This is preferably the official name of the
-          router, usually this is the DNS name that is associated with
-          the loopback0 interface.
-
-        - description: description of the router (optional)
-
-        - operSys: operating system running on the router (optional)
-
-        - institution: institution this routers belongs to (optional)
-
-        - city, country, latitude and longitude: location of the router
-          (optional)
-
-        - flowVersion: the flow information export format used by the
-          router, for now we support the following versions:
-                - netflow_v5
-                - netflow_v9
-                - ipfix
-                - sflow
-
-        - sampleRate: the packet sample rate, if any, that is being used
-          by the router before flow accounting is done, for example:
-                - sampleRate = 100 if only 1 out of every 100 packets is
-                  sent to the router internal accounting process
-                - sampleRate = 1 if every 1 out of 1 packets is sent to
-                  the router internal accounting process (all packets
-                  are accounted for)
-
-        The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can
-        be used to specify a startTime and endTime to limit the number
-        of flows to a specific time range.
-
-Below are fields that are specific to this request:
-
-        - topStatistic: generate the Top N flow or flow element statistic.
-          Statistic can be (only one can be specified at a time):
-                  record  Statistic about arregated netflow records.
-                  srcip   Statistic about source IP addresses
-                  dstip   Statistic about destination IP addresses
-                  ip      Statistic about any (source or destination) IP 
addresses
-                  srcport Statistic about source ports
-                  dstport Statistic about destination ports
-                  port    Statistic about any (source or destination) ports
-                  srcas   Statistic about source AS numbers
-                  dstas   Statistic about destination AS numbers
-                  as      Statistic about any (source or destination) AS 
numbers
-                  inif    Statistic about input interface
-                  outif   Statistic about output interface
-                  proto   Statistic about IP protocols
-
-          - orderBy: specify the order by which the statistics are ordered
-            (only one can be specified at a time):
-                 flows
-                 packets
-                 bytes
-                 pps
-                 bps
-                 bpp
-
-        - splitProtocol: the resulting statistics are splitted up into
-          transport layer protocols. Default is transport protocol 
independant
-          statistics. Possible values: yes, no (default).
-
-        - topN: Define the number for the Top N statistics. Defaults to 10. 
If
-          0 is specified the number is unlimited. 
-
-Data:
-
-        The response of this request will contain the requested Top N 
information.
-
 -->
 <nmwg:message type="SetupDataRequest" id="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
@@ -99,40 +29,20 @@
 
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
     
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/top/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
-      <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
-      <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
   </nmwg:metadata>
 
   <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
-    <select:parameters id="selectparamid1">
-      <nmwg:parameter name="startTime">
-        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
-      </nmwg:parameter>
-      <nmwg:parameter name="endTime">
-        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
-      </nmwg:parameter>
-    </select:parameters>
-  </nmwg:metadata>
-
-  <nmwg:metadata id="meta3">
-    <top:subject id="topsub1" metadataIdRef="meta2"/>
+    <top:subject id="topsub1" metadataIdRef="meta1"/>
     <top:parameters id="topparamid1">
       <nmwg:parameter name="topStatistic">ip</nmwg:parameter>
       <nmwg:parameter name="orderBy">flows</nmwg:parameter>
@@ -141,6 +51,18 @@
     </top:parameters>
   </nmwg:metadata>
 
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
+    <select:parameters id="selectparamid1">
+      <nmwg:parameter name="startTime">
+        <nmtm:time type="ISO" value="2007-06-01T14:54:00Z"/>
+      </nmwg:parameter>
+      <nmwg:parameter name="endTime">
+        <nmtm:time type="ISO" value="2007-06-01T15:54:00Z"/>
+      </nmwg:parameter>
+    </select:parameters>
+  </nmwg:metadata>
+
   <nmwg:data id="data1" metadataIdRef="meta3"/>
 
 </nmwg:message>

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-flowStatistics.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-flowStatistics.xml
    2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-flowStatistics.xml
    2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,4 +1,5 @@
 <!-- 
+
 FlowSA SetupDataResponse-flowStatistics (Service -> Client Response)
 
 version 0.3, 21 May 2007, Hans Trompert, modelled after 
FlowS&A-SetupDataRespone-flowStatistics-v0.3.xml
@@ -9,76 +10,19 @@
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos, added 
subnamespace stat to flow namespace to make datum elements unique.
+version 0.11, 27 July 2007, Jason Zurawski, added example of multiple 
subjects with corresponding data blocks
+version 0.12, 30 July 2007, Hans Trompert, moved flowVersion and sampleRate 
into seperate metadatablock, changed node into a network containing one ore 
more nodes
+version 0.13, 07 Aug 2007, Hans Trompert, reversed changes made in version 
12, now using RouterGroup (== BaseNetwork) as a subject, cleanup
 
+
 This is the response of the request for statistical information about
-the selected flows from the given router(s).  For the moment, more
-information can be found at:
+the selected flows from the given router(s).
 
-        
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_flow_statistics
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-        - hostName: the name of the router for which we are holding flow
-          information. This is preferably the official name of the
-          router, usually this is the DNS name that is associated with
-          the loopback0 interface.
-
-        - description: description of the router (optional)
-
-        - operSys: operating system running on the router (optional)
-
-        - institution: institution this routers belongs to (optional)
-
-        - city, country, latitude and longitude: location of the router
-          (optional)
-
-        - flowVersion: the flow information export format used by the
-          router, for now we support the following versions:
-                - netflow_v5
-                - netflow_v9
-                - ipfix
-                - sflow
-
-        - sampleRate: the packet sample rate, if any, that is being used
-          by the router before flow accounting is done, for example:
-                - sampleRate = 100 if only 1 out of every 100 packets is
-                  sent to the router internal accounting process
-                - sampleRate = 1 if every 1 out of 1 packets is sent to
-                  the router internal accounting process (all packets
-                  are accounted for)
-
-        The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can
-        be used to specify a startTime and endTime to limit the number
-        of flows to a specific time range.
-
-Data:
-
-        The response of this request will contain the following
-        information:
-
-        flows:            total number of flows
-        flowsTcp:         number of TCP flows
-        flowsUdp:         number of UDP flows
-        flowsIcmp:        number of ICMP flows
-        flowsOther:       number of other flows
-        packets:          total number of packets
-        packetsTcp:       number of TCP packets
-        packetsUdp:       number of UDP packets
-        packetsIcmp       number of ICMP packets
-        packetsOther:     number of other packets
-        bytes:            total number of bytes
-        bytesTcp:         number of TCP bytes
-        bytesUdp:         number of UDP bytes
-        bytesIcmp:        number of ICMP bytes
-        bytesOther:       number of other bytes
-        first:            start of first flow (seconds part of timestamp)
-        last:             end of last flow (seconds part of timestamp)
-        msecFirst:        start of first flow (milliseconds part of 
timestamp)
-        msecLast:         end of last flow (milliseconds part of timestamp)
-        SequenceFailures: number of sequence failures while receiving flow 
information packets
-
 -->
 <nmwg:message type="SetupDataRespone" id="msg2" messageIdRef="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
@@ -90,28 +34,46 @@
 
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR router 2 in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.2</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
     
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/stat/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
+  </nmwg:metadata>
+
+  <nmwg:metadata id="meta2">
+    <stat:subject id="statsub1" metadataIdRef="meta1"/>
+    <stat:parameters id="statparamid1">
       <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
       <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
+    </stat:parameters>
   </nmwg:metadata>
 
-  <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
     <select:parameters id="selectparamid1">
       <nmwg:parameter name="startTime">
         <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
@@ -122,15 +84,15 @@
     </select:parameters>
   </nmwg:metadata>
 
-  <nmwg:data id="data1" metadataIdRef="meta2">
-    <stat:datum flows="2743934" flowsTcp="28855797" flowsUdp="3640646"
+  <nmwg:data id="data1" metadataIdRef="meta3">
+    <stat:datum
+      flows="2743934" flowsTcp="28855797" flowsUdp="3640646"
       flowsIcmp="166385" flowsOther="81106" packets="145371187"
       packetsTcp="131640619" packetsUdp="8769174" packetsIcmp="215350"
       packetsOther="4746044" bytes="107316849515"
-      bytesTcp="101866880996" bytesUdp="2048101988"
-      bytesIcmp="15996576" bytesOther="3385869955" first="1170162779"
-      last="1170171099" msecFirst="166" msecLast="0"
-      sequenceFailures="139">
+      bytesTcp="101866880996" bytesUdp="2048101988" bytesIcmp="15996576"
+      bytesOther="3385869955" first="1170162779" last="1170171099"
+      msecFirst="166" msecLast="0" sequenceFailures="139">
       <nmtm:time type="range">
         <nmtm:start type="ISO" value="2005-07-16T00:00:00Z"/>
         <nmtm:end type="ISO" value="2005-07-21T00:00:00Z"/>

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-rawFlows.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-rawFlows.xml
  2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-rawFlows.xml
  2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,110 +1,25 @@
 <!-- 
+
 FlowSA SetupDataResponse-rawFlows (Service -> Client Response)
 
 version 0.5, 01 June 2007, Hans Trompert, initial proposal, modelled after 
FlowS&A-SetupDataRequest-rawFlows-v0.5.xml
-version 0.6, 5 June 2007, Jason Zurawski, fixed subject namespace issue, 
suggesting new abstraction gof subject.  Asking
-                                          question about parameter name 
assignment.
+version 0.6, 5 June 2007, Jason Zurawski, fixed subject namespace issue, 
suggesting new abstraction gof subject. Asking question about parameter name 
assignment.
 version 0.7, 6 June 2007, Hans Trompert, subject now uses nmwgtopo3:node, 
changed the way the showField parameters are specified.
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos, added 
subnamespace raw
+version 0.11, 07 Aug 2007, Hans Trompert, now using RouterGroup (== 
BaseNetwork) as a subject, cleanup
+version 0.12, 08 Aug 2007, Hans Trompert, fixed eventType
 
 This response will return information about all flows whithin the specified
 time range from the given router(s), the flows are optionally filtered on
-the basis of there content or aggregated as specified.  For the moment, more
-information can be found at:
+the basis of there content or aggregated as specified.
 
-       
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_raw_flows
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-        - hostName: the name of the router for which we are holding flow
-          information. This is preferably the official name of the router,
-          usually this is the DNS name that is associated with the loopback0
-          interface.
-
-        - description: description of the router (optional)
-
-        - operSys: operating system running on the router (optional)
-
-        - institution: institution this routers belongs to (optional)
-
-        - city, country, latitude and longitude: location of the router
-          (optional)
-
-        - flowVersion: the flow information export format used by the
-          router, for now we support the following versions:
-                - netflow_v5
-                - netflow_v9
-                - ipfix
-                - sflow
-
-        - sampleRate: the packet sample rate, if any, that is being used by
-          the router before flow accounting is done, for example:
-                - sampleRate = 100 if only 1 out of every 100 packets is
-                  sent to the router internal accounting process
-                - sampleRate = 1 if every 1 out of 1 packets is sent to the
-                  router internal accounting process (all packets are
-                  accounted for)
-
-        The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can be
-        used to specify a startTime and endTime to limit the number of flows
-        to a specific time range.
-
-        The folowing parameters can be used to filter and/or aggregate the
-        flows:
-
-        - aggregationRule: any valid Nfdump style aggregation rule, for
-          example:
-                - aggregate source IP address and destination port:
-                  'srcip,dstport'
-                - aggregate flows from the same /24 IPv4 source IP and
-                  destination port: 'srcip4/24,dstport'
-
-        - filterRule: any valid Nfdump style filter rule, for example:
-                - 'tcp and ( src ip 172.16.17.18 or dst ip 172.16.17.19 )'
-                - 'in if 5 and net 10.0.0.0/24 and not host 10.0.0.1 and bps 
> 10k and duration < 100 and dst port 1433'
-
-        The parameters below specify which flow information fields are
-        returned, this is mainly intended to reduce the amount of data that
-        has to be returned, so please specify only those fields you really
-        need. One or more can of the folowing parameters can be selected:
-
-        - showFieldAddressFamily   PF_INET or PF_INET6
-        - showFieldTimeFirstSeen   UNIX time seconds
-        - showFieldMsecFirstSeen   Mili seconds first seen
-        - showFieldTimeLastSeen    UNIX time seconds
-        - showFieldMsecLastSeen    Mili seconds first seen
-        - showFieldProtocol        Protocol
-        - showFieldSrcAddress      Src address as 4 consecutive 32bit 
numbers.
-        - showFieldSrcPort         Src port
-        - showFieldDstAddress      Dst address as 4 consecutive 32bit 
numbers.
-        - showFieldDstPort         Dst port
-        - showFieldSrcAS           Src AS number
-        - showFieldDstAS           Dst AS number
-        - showFieldInputIF         Input Interface
-        - showFieldOutputIF        Output Interface
-        - showFieldTcpFlags        TCP Flags
-                                   000001 FIN.
-                                   000010 SYN
-                                   000100 RESET
-                                   001000 PUSH
-                                   010000 ACK
-                                   100000 URGENT
-                                   e.g. 6 => SYN + RESET
-        - showFieldTos             Type of Service
-        - showFieldPackets         Number of packets
-        - showFieldBytes           Number of bytes
-
-Data:
-
-       The response will consist of zero, one or more datum fields, one for
-       every flow that matched the criteria (aggregationRule, filterRule,
-       startTime and endTime) from the request message.  Only the
-       attributes as specified by showField are returned.
-
 -->
 <nmwg:message type="SetupDataResponse" id="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
@@ -116,41 +31,41 @@
 
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR router 2 in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.2</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
     
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/raw/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
-      <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
-      <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
   </nmwg:metadata>
 
   <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
-    <select:parameters id="selectparamid1">
-      <nmwg:parameter name="startTime">
-        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
-      </nmwg:parameter>
-      <nmwg:parameter name="endTime">
-        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
-      </nmwg:parameter>
-    </select:parameters>
-  </nmwg:metadata>
-
-  <nmwg:metadata id="meta3">
-    <raw:subject id="rawsub1" metadataIdRef="meta2"/>
+    <raw:subject id="rawsub1" metadataIdRef="meta1"/>
     <raw:parameters id="rawparamid1">
+      <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
+      <nmwg:parameter name="sampleRate">100</nmwg:parameter>
       <nmwg:parameter name="aggregationRule">srcip,dstport</nmwg:parameter>
       <nmwg:parameter name="filterRule">ip 10.101.102.103 and port = 
443</nmwg:parameter>
       <nmwg:parameter name="showFieldAddressFamily"/>
@@ -174,6 +89,18 @@
     </raw:parameters>
   </nmwg:metadata>
 
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
+    <select:parameters id="selectparamid1">
+      <nmwg:parameter name="startTime">
+        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
+      </nmwg:parameter>
+      <nmwg:parameter name="endTime">
+        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
+      </nmwg:parameter>
+    </select:parameters>
+  </nmwg:metadata>
+
   <nmwg:data id="data1" metadataIdRef="meta3">
     <raw:datum addressFamily="2" timeFirstSeen="1180697264"
       msecFirstSeen="945" timeLastSeen="1180697276" msecLastSeen="3"

Modified: 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-topFlows.xml
===================================================================
--- 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-topFlows.xml
  2007-08-08 10:58:37 UTC (rev 2601)
+++ 
trunk/perfsonar/schema/example-instances/perfSONAR/FlowsaMA/SetupDataResponse-topFlows.xml
  2007-08-08 11:27:01 UTC (rev 2602)
@@ -1,4 +1,5 @@
 <!-- 
+
 FlowSA SetupDataResponse-topFlows (Service -> Client Reponse)
 
 version 0.5, 30 May 2007, Hans Trompert, initial proposal, modelled after 
FlowS&A-SetupDataRequest-topFlows-v0.5.xml
@@ -7,112 +8,16 @@
 version 0.8, 12 June 2007, Martin Swany, Added location data
 version 0.9, 13 June 2007, Jason Zurawski, Final cleanup
 version 0.10, 24 July 2007, Hans Trompert, fixed some typos, updated 
metadata explanation to match message, added top subnamespace to flow 
namespace to make top parameter subject and top datum elements unique.
+version 0.11, 07 Aug 2007, Hans Trompert, now using RouterGroup (== 
BaseNetwork) as a subject, cleanup
+version 0.12, 08 Aug 2007, Hans Trompert, fixed eventType, matched query 
interval to data
 
 This request will return the Top N flow or flow element statistics.
-For the moment, more information can be found at:
 
-       
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA#Query_top_flow_information
+A more detailed description can be found on the Flow Selection and
+Aggregation MA pages on the perfSONAR WiKi:
 
-Metadata:
+  
http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA
 
-        Information on the router that exported the flow information:
-
-        - hostName: the name of the router for which we are holding flow
-          information. This is preferably the official name of the
-          router, usually this is the DNS name that is associated with
-          the loopback0 interface.
-
-        - description: description of the router (optional)
-
-        - operSys: operating system running on the router (optional)
-
-        - institution: institution this routers belongs to (optional)
-
-        - city, country, latitude and longitude: location of the router
-          (optional)
-
-        - flowVersion: the flow information export format used by the
-          router, for now we support the following versions:
-                - netflow_v5
-                - netflow_v9
-                - ipfix
-                - sflow
-
-        - sampleRate: the packet sample rate, if any, that is being used
-          by the router before flow accounting is done, for example:
-                - sampleRate = 100 if only 1 out of every 100 packets is
-                  sent to the router internal accounting process
-                - sampleRate = 1 if every 1 out of 1 packets is sent to
-                  the router internal accounting process (all packets
-                  are accounted for)
-
-        Below are fields that are specific to this request:
-
-        - topStatistic: generate the Top N flow or flow element statistic.
-          Statistic can be (only one can be specified at a time):
-                  record  Statistic about arregated netflow records.
-                  srcip   Statistic about source IP addresses
-                  dstip   Statistic about destination IP addresses
-                  ip      Statistic about any (source or destination) IP 
addresses
-                  srcport Statistic about source ports
-                  dstport Statistic about destination ports
-                  port    Statistic about any (source or destination) ports
-                  srcas   Statistic about source AS numbers
-                  dstas   Statistic about destination AS numbers
-                  as      Statistic about any (source or destination) AS 
numbers
-                  inif    Statistic about input interface
-                  outif   Statistic about output interface
-                  proto   Statistic about IP protocols
-
-          - orderBy: specify the order by which the statistics are ordered
-            (only one can be specified at a time):
-                 flows
-                 packets
-                 bytes
-                 pps
-                 bps
-                 bpp
-
-        - splitProtocol: the resulting statistics are splitted up into
-          transport layer protocols. Default is transport protocol 
independant
-          statistics. Possible values: yes, no (default).
-
-        - topN: Define the number for the Top N statistics. Defaults to 10. 
If
-          0 is specified the number is unlimited. 
-
-        The filtering namespace http://ggf.org/ns/nmwg/ops/select/ can
-        be used to specify a startTime and endTime to limit the number
-        of flows to a specific time range.
-
-Data:
-
-        The response of this request will contain the requested Top N 
information.
-        De datum record contains the following information:
-
-        - dateFirstSeen: Start time of flow first seen. ISO 8601 format
-          including miliseconds.
-
-        - duration: Duration of the flow in seconds and miliseconds. Duration
-          is the  time  span  over  the  entire periode of time from first 
seen
-          to last seen.
-
-        - proto: Protocol used.
-
-        - topStatistic: The topStatistic that was requested.
-
-        - Flows: Number of flows.
-
-        - Packets: The number of packets.
-
-        - Bytes: The number of bytes.
-
-        - pps: The calculated packets per second: number of packets / 
duration.
-
-        - bps: The calculated bits per second: 8 * number of bytes / 
duration.
-
-        - bpp:  The calculated bytes per packet: number of bytes / number of
-          packets.
-
 -->
 <nmwg:message type="SetupDataRequest" id="msg1"
   xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
@@ -122,51 +27,62 @@
   xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";
   xmlns:nmtm="http://ggf.org/ns/nmwg/time/2.0/";>
 
-
   <nmwg:metadata id="meta1">
     <flow:subject id="flowsub1">
-      <nmwgtopo3:node>
-        <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
-        <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
-        <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
-        <nmwgtopo3:location>
-          <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
-          <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
-          <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
-          <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
-          <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
-        </nmwgtopo3:location>
-      </nmwgtopo3:node>
+      <nmwgtopo3:network id="network1">
+        <nmwgtopo3:node id="router1">
+          <nmwgtopo3:hostName>test-router.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.3</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+        <nmwgtopo3:node id="router2">
+          <nmwgtopo3:hostName>test-router-2.lab.test-net</nmwgtopo3:hostName>
+          <nmwgtopo3:description>Avici Systems TSR router 2 in test 
lab</nmwgtopo3:description>
+          <nmwgtopo3:operSys>IPriori Operational Image 
6.5.3.2</nmwgtopo3:operSys>
+          <nmwgtopo3:location>
+            <nmwgtopo3:institution>SURFnet</nmwgtopo3:institution>
+            <nmwgtopo3:city>Amsterdam</nmwgtopo3:city>
+            <nmwgtopo3:country>The Netherlands</nmwgtopo3:country>
+            <nmwgtopo3:latitude>52.212212</nmwgtopo3:latitude>
+            <nmwgtopo3:longitude>04.571003</nmwgtopo3:longitude>
+          </nmwgtopo3:location>
+        </nmwgtopo3:node>
+      </nmwgtopo3:network>
     </flow:subject>
-    <nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/2.0/</nmwg:eventType>
-    <flow:parameters id="flowparamid1">
+    
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/flow/top/2.0/</nmwg:eventType>
+  </nmwg:metadata>
+
+  <nmwg:metadata id="meta2">
+    <top:subject id="topsub1" metadataIdRef="meta1"/>
+    <top:parameters id="topparamid1">
       <nmwg:parameter name="flowVersion">netflow_v9</nmwg:parameter>
       <nmwg:parameter name="sampleRate">100</nmwg:parameter>
-    </flow:parameters>
+      <nmwg:parameter name="topStatistic">ip</nmwg:parameter>
+      <nmwg:parameter name="orderBy">flows</nmwg:parameter>
+      <nmwg:parameter name="splitProtocol">yes</nmwg:parameter>
+      <nmwg:parameter name="topN">2</nmwg:parameter>
+    </top:parameters>
   </nmwg:metadata>
 
-  <nmwg:metadata id="meta2">
-    <select:subject id="selectsub1" metadataIdRef="meta1"/>
+  <nmwg:metadata id="meta3">
+    <select:subject id="selectsub1" metadataIdRef="meta2"/>
     <select:parameters id="selectparamid1">
       <nmwg:parameter name="startTime">
-        <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
+        <nmtm:time type="ISO" value="2007-06-01T14:54:00Z"/>
       </nmwg:parameter>
       <nmwg:parameter name="endTime">
-        <nmtm:time type="ISO" value="2005-07-21T00:00:00Z"/>
+        <nmtm:time type="ISO" value="2007-06-01T15:54:00Z"/>
       </nmwg:parameter>
     </select:parameters>
   </nmwg:metadata>
 
-  <nmwg:metadata id="meta3">
-    <top:subject id="topsub1" metadataIdRef="meta2"/>
-    <top:parameters id="topparamid1">
-      <nmwg:parameter name="topStatistic">ip</nmwg:parameter>
-      <nmwg:parameter name="orderBy">flows</nmwg:parameter>
-      <nmwg:parameter name="splitProtocol">yes</nmwg:parameter>
-      <nmwg:parameter name="topN">2</nmwg:parameter>
-    </top:parameters>
-  </nmwg:metadata>
-
   <nmwg:data id="data1" metadataIdRef="meta3">
     <top:datum dateFirstSeen="2007-06-01 14:54:39.479"
       duration="2119.521" proto="TCP" topStatistic="10.9.8.7"