perfsonar-dev - nmwg: r265 - in trunk/nmwg/doc: . nm-schema-base nm-topo

Subject: perfsonar development work

List archive

nmwg: r265 - in trunk/nmwg/doc: . nm-schema-base nm-topo

From:
To: ,
Subject: nmwg: r265 - in trunk/nmwg/doc: . nm-schema-base nm-topo
Date: Thu, 13 Sep 2007 19:24:25 -0400

Author: swany
Date: 2007-09-13 19:24:25 -0400 (Thu, 13 Sep 2007)
New Revision: 265

Added:
trunk/nmwg/doc/nm-topo/
trunk/nmwg/doc/nm-topo/fop.jar
trunk/nmwg/doc/nm-topo/inline.pl
trunk/nmwg/doc/nm-topo/make.sh
trunk/nmwg/doc/nm-topo/nm-topo.fo
trunk/nmwg/doc/nm-topo/nm-topo.html
trunk/nmwg/doc/nm-topo/nm-topo.pdf
trunk/nmwg/doc/nm-topo/nm-topo.xml
trunk/nmwg/doc/nm-topo/post.pl
trunk/nmwg/doc/nm-topo/rfc2629-other.ent
trunk/nmwg/doc/nm-topo/rfc2629-xhtml.ent
trunk/nmwg/doc/nm-topo/rfc2629.dtd
trunk/nmwg/doc/nm-topo/rfc2629.xslt
trunk/nmwg/doc/nm-topo/rfc2629toFO.xslt
trunk/nmwg/doc/nm-topo/saxon8.jar
trunk/nmwg/doc/nm-topo/schema
trunk/nmwg/doc/nm-topo/tmp.nm-topo.xml
Modified:
trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo
trunk/nmwg/doc/nm-schema-base/nm-schema-base.html
trunk/nmwg/doc/nm-schema-base/nm-schema-base.pdf
trunk/nmwg/doc/nm-schema-base/nm-schema-base.xml
Log:
current document status, more changes pending

Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo
===================================================================
--- trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo 2007-09-08 03:07:54
UTC (rev 264)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo 2007-09-13 23:24:25
UTC (rev 265)
@@ -1,6 +1,6 @@
-<?xml version="1.0" encoding="UTF-8"?><fo:root
xmlns:fo="http://www.w3.org/1999/XSL/Format"; font-family="serif"
font-size="10pt"><meta-info
xmlns="http://www.renderx.com/XSL/Extensions";><meta-field name="title"
value="
	An Extensible Schema for Network Measurement and Performance
Data
 "/><meta-field name="author"
value="Swany"/></meta-info><fo:layout-master-set><fo:simple-page-master
master-name="first-page" margin-left="1in" margin-right="1in"
page-height="11in" page-width="8.5in"><fo:region-body margin-bottom="1in"
margin-top="1in"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:simple-page-master
master-name="other-pages" margin-left="1in" margin-right="1in"
page-height="11in" page-width="8.5in"><fo:region-body margin-bottom="1in"
margin-top="1in"/><fo:region-before extent="1cm"
region-name="header"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:simple-page-master
master-name="other-pages-dc"
margin-left="1in" margin-right="1in" page-height="11in"
page-width="8.5in"><fo:region-body margin-bottom="1in" margin-top="1in"
column-count="2"/><fo:region-before extent="1cm"
region-name="header"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:page-sequence-master
master-name="sequence"><fo:single-page-master-reference
master-reference="first-page"/><fo:repeatable-page-master-reference
master-reference="other-pages"/></fo:page-sequence-master></fo:layout-master-set><fo:bookmark-tree><fo:bookmark
internal-destination="rfc.status"><fo:bookmark-title>Status of this
Memo</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.copyrightnotice"><fo:bookmark-title>Copyright
Notice</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.1"><fo:bookmark-title>1
Introduction</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.1.1"><fo:bookmark-title>1.1
Goals</fo:bookmark-title></fo:bookmark></fo
:bookmark><fo:bookmark internal-destination="rfc.section.2">!
<fo:book
mark-title>2 Design Philosophy</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3"><fo:bookmark-title>3 Basic
Elements</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.1"><fo:bookmark-title>3.1
Metadata</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.1.1"><fo:bookmark-title>3.1.1
Subject</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.1.2"><fo:bookmark-title>3.1.2 Event
Type</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.1.3"><fo:bookmark-title>3.1.3
Parameters</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.2"><fo:bookmark-title>3.2
Data</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.2.1"><fo:bookmark-title>3.2.1
Datum</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.3"><fo:bookmark-title>3.3 Container
Elements</fo:bookmark-
title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.4"><fo:bookmark-title>4 XML
Namespaces</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.5"><fo:bookmark-title>5 Extending the
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.6"><fo:bookmark-title>6
Versioning</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.7"><fo:bookmark-title>7 Metadata
Chaining</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.8"><fo:bookmark-title>8 Operation
Metadata</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.9"><fo:bookmark-title>9 Base
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.10"><fo:bookmark-title>10 Time
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.11"><fo:bookmark-title>11 Topology
Schema</fo:bookmark-title></fo:book
mark><fo:bookmark internal-destination="rfc.section.12"><fo:!
bookmark
-title>12 Examples</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.12.1"><fo:bookmark-title>12.1 Schema for
ping</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.12.2"><fo:bookmark-title>12.2 Instance
document for ping</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.13"><fo:bookmark-title>13 Security
Concerns</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.14"><fo:bookmark-title>14
Appendices</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.14.1"><fo:bookmark-title>14.1
Acknowledgements</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.references"><fo:bookmark-title>15
References</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.authors"><fo:bookmark-title>Author's
Address</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.ipr"><fo:bookmark-title>Intellectu
al Property and Copyright
Statements</fo:bookmark-title></fo:bookmark></fo:bookmark-tree><fo:page-sequence
master-reference="sequence" language="en"><fo:static-content
flow-name="header"><fo:table width="100%" text-align="center"
space-before=".2cm" table-layout="fixed"><fo:table-column
column-width="proportional-column-width(6)"/><fo:table-column
column-width="proportional-column-width(70)"/><fo:table-column
column-width="proportional-column-width(6)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block
text-align="start">RFC </fo:block></fo:table-cell><fo:table-cell
text-align="center"><fo:block>
+<?xml version="1.0" encoding="UTF-8"?><fo:root
xmlns:fo="http://www.w3.org/1999/XSL/Format"; font-family="serif"
font-size="10pt"><meta-info
xmlns="http://www.renderx.com/XSL/Extensions";><meta-field name="title"
value="
	An Extensible Schema for Network Measurement and Performance
Data
 "/><meta-field name="author"
value="Swany"/></meta-info><fo:layout-master-set><fo:simple-page-master
master-name="first-page" margin-left="1in" margin-right="1in"
page-height="11in" page-width="8.5in"><fo:region-body margin-bottom="1in"
margin-top="1in"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:simple-page-master
master-name="other-pages" margin-left="1in" margin-right="1in"
page-height="11in" page-width="8.5in"><fo:region-body margin-bottom="1in"
margin-top="1in"/><fo:region-before extent="1cm"
region-name="header"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:simple-page-master
master-name="other-pages-dc"
margin-left="1in" margin-right="1in" page-height="11in"
page-width="8.5in"><fo:region-body margin-bottom="1in" margin-top="1in"
column-count="2"/><fo:region-before extent="1cm"
region-name="header"/><fo:region-after extent="1cm"
region-name="footer"/></fo:simple-page-master><fo:page-sequence-master
master-name="sequence"><fo:single-page-master-reference
master-reference="first-page"/><fo:repeatable-page-master-reference
master-reference="other-pages"/></fo:page-sequence-master></fo:layout-master-set><fo:bookmark-tree><fo:bookmark
internal-destination="rfc.status"><fo:bookmark-title>Status of this
Memo</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.copyrightnotice"><fo:bookmark-title>Copyright
Notice</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.1"><fo:bookmark-title>1
Introduction</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.1.1"><fo:bookmark-title>1.1
Goals</fo:bookmark-title></fo:bookmark></fo
:bookmark><fo:bookmark internal-destination="rfc.section.2">!
<fo:book
mark-title>2 Design Philosophy</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3"><fo:bookmark-title>3 Basic
Elements</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.1"><fo:bookmark-title>3.1
Metadata</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.1.1"><fo:bookmark-title>3.1.1
Subject</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.1.2"><fo:bookmark-title>3.1.2 Event
Type</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.1.3"><fo:bookmark-title>3.1.3
Parameters</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.2"><fo:bookmark-title>3.2
Data</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.3.2.1"><fo:bookmark-title>3.2.1
Datum</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.3.3"><fo:bookmark-title>3.3 Container
Elements</fo:bookmark-
title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.4"><fo:bookmark-title>4 XML
Namespaces</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.5"><fo:bookmark-title>5 Extending the
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.6"><fo:bookmark-title>6
Versioning</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.7"><fo:bookmark-title>7 Metadata
Chaining</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.8"><fo:bookmark-title>8 Operation
Metadata</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.9"><fo:bookmark-title>9 Base
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.10"><fo:bookmark-title>10 Time
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.11"><fo:bookmark-title>11 Topology
Schema</fo:bookmark-title></fo:book
mark><fo:bookmark internal-destination="rfc.section.12"><fo:!
bookmark
-title>12 Examples</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.12.1"><fo:bookmark-title>12.1 Schema for
ping</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.12.2"><fo:bookmark-title>12.2 Instance
document for ping</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.section.13"><fo:bookmark-title>13 Security
Concerns</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.14"><fo:bookmark-title>14
Appendices</fo:bookmark-title><fo:bookmark
internal-destination="rfc.section.14.1"><fo:bookmark-title>14.1
Acknowledgements</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.references"><fo:bookmark-title>15
References</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.authors"><fo:bookmark-title>Author's
Address</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.ipr"><fo:bookmark-title>Intellectu
al Property and Copyright
Statements</fo:bookmark-title></fo:bookmark></fo:bookmark-tree><fo:page-sequence
master-reference="sequence" language="en"><fo:static-content
flow-name="header"><fo:table width="100%" text-align="center"
space-before=".2cm" table-layout="fixed"><fo:table-column
column-width="proportional-column-width(9)"/><fo:table-column
column-width="proportional-column-width(70)"/><fo:table-column
column-width="proportional-column-width(9)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block
text-align="start">RFC </fo:block></fo:table-cell><fo:table-cell
text-align="center"><fo:block>
An Extensible Schema for Network Measurement and Performance Data
- </fo:block></fo:table-cell><fo:table-cell text-align="end"><fo:block>May
2007</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table></fo:static-content><fo:static-content
flow-name="footer"><fo:table text-align="center" width="100%"
table-layout="fixed"><fo:table-column
column-width="proportional-column-width(7.5)"/><fo:table-column
column-width="proportional-column-width(13)"/><fo:table-column
column-width="proportional-column-width(7.5)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block
text-align="start">Swany</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="center">Informational</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="end">[Page
<fo:page-number/>]</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table></fo:static-content><fo:flow
flow-name="xsl-region-body"><fo:table width="100%"
table-layout="fixed"><fo:table-column
column-width="proportional-column-width(1)"/><fo:table-column
column-width="proportio

nal-column-width(1)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block>Network
Measurement Working Group</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="right">M Swany,
Editor</fo:block></fo:table-cell></fo:table-row><fo:table-row><fo:table-cell><fo:block/></fo:table-cell><fo:table-cell><fo:block

text-align="right">UDel</fo:block></fo:table-cell></fo:table-row><fo:table-row><fo:table-cell><fo:block>Intended
status: Informational</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="right">May
2007</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table><fo:block
text-align="center" font-weight="bold" font-size="18pt" space-before="3em"
space-after="3em">
+ </fo:block></fo:table-cell><fo:table-cell
text-align="end"><fo:block>September
2007</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table></fo:static-content><fo:static-content
flow-name="footer"><fo:table text-align="center" width="100%"
table-layout="fixed"><fo:table-column
column-width="proportional-column-width(7.5)"/><fo:table-column
column-width="proportional-column-width(13)"/><fo:table-column
column-width="proportional-column-width(7.5)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block
text-align="start">Swany</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="center">Informational</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="end">[Page
<fo:page-number/>]</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table></fo:static-content><fo:flow
flow-name="xsl-region-body"><fo:table width="100%"
table-layout="fixed"><fo:table-column
column-width="proportional-column-width(1)"/><fo:table-column
column-width="pro

portional-column-width(1)"/><fo:table-body><fo:table-row><fo:table-cell><fo:block>Network
Measurement Working Group</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="right">M Swany,
Editor</fo:block></fo:table-cell></fo:table-row><fo:table-row><fo:table-cell><fo:block/></fo:table-cell><fo:table-cell><fo:block

text-align="right">UDel</fo:block></fo:table-cell></fo:table-row><fo:table-row><fo:table-cell><fo:block>Intended
status: Informational</fo:block></fo:table-cell><fo:table-cell><fo:block
text-align="right">September
2007</fo:block></fo:table-cell></fo:table-row></fo:table-body></fo:table><fo:block
text-align="center" font-weight="bold" font-size="18pt" space-before="3em"
space-after="3em">
An Extensible Schema for Network Measurement and Performance Data
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-before="14pt" space-after="7pt"><fo:block
id="rfc.status"/>Status of this Memo</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
This memo provides information for the Grid community.
@@ -16,27 +16,27 @@
circuits, as well as in advanced distributed computing
environments, such as Grid computing.
</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
- This work is born of the need for a common mechanism for the
- exchange of network measurement and performance data. In the
- case of research-oriented networks, parties often want to
- exchange network performance data with neighbors for debugging
- purposes. In general, however, there is no single system that is
- in use. In the Grid community, the need to exchange network
- metrics of various sorts is often highlighted. In short it is
- highly desirable to have an extensible schema for network
- performance information that gives a common, general framework
- for representation and exchange.
- </fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
- This document builds on previous versions of the network
- measurement schemata. This document describes Version 2 of the
- Grid Forum's Network Measurement Working Group (NM-WG) schema.
- </fo:block><fo:block font-weight="bold" font-size="12pt"
keep-with-next="always" space-before="12pt" space-after="6pt"
id="rfc.section.1.1">1.1 Goals</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
- The goal is to define a neutral representation for network
- measurements that can be easily extended to support new types
- of data. This representation should identify forms of network
- performance data as well as to create standardized mechanism
- to both describe and publish these metrics.
- </fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.2">2. Design Philosophy</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
+ This work is born of the need for a common mechanism for the
+ exchange of network measurement and performance data. In the
+ case of research-oriented networks, parties often want to
+ exchange network performance data with neighbors for debugging
+ purposes. In general, however, there is no single system that is
+ in use. In the Grid community, the need to exchange network
+ metrics of various sorts is often highlighted. In short it is
+ highly desirable to have an extensible schema for network
+ performance information that gives a common, general framework
+ for representation and exchange.
+ </fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
+ This document builds on previous versions of the network
+ measurement schemata. This document describes Version 2 of the
+ Grid Forum's Network Measurement Working Group (NM-WG) schema.
+ </fo:block><fo:block font-weight="bold" font-size="12pt"
keep-with-next="always" space-before="12pt" space-after="6pt"
id="rfc.section.1.1">1.1 Goals</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
+ The goal is to define a neutral representation for network
+ measurements that can be easily extended to support new types
+ of data. This representation should identify forms of network
+ performance data as well as to create standardized mechanism
+ to both describe and publish these metrics.
+ </fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.2">2. Design Philosophy</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
One of the high-level goals of this representation is to
"normalize" the data representation by removing as much
redundancy as possible. The basic schema design is based on the
@@ -75,18 +75,18 @@
accomplish this, the Metadata must include three key
things:
</fo:block><fo:list-block
provisional-distance-between-starts="2em"><fo:list-item space-before=".25em"
space-after=".25em"><fo:list-item-label
end-indent="label-end()"><fo:block/></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>
- "Subject" -- The Subject identifies the entity being
- measured. This could include the network path
between a
- pair of hosts, an interface on a router, or a specific
- location on the network from which flow or packet
data is
- captured.
- </fo:block></fo:list-item-body></fo:list-item><fo:list-item
space-before=".25em" space-after=".25em"><fo:list-item-label
end-indent="label-end()"><fo:block/></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>
- "EventType" -- The EventType identifies exactly what
sort
- of measurement Event occurred.
- </fo:block></fo:list-item-body></fo:list-item><fo:list-item
space-before=".25em" space-after=".25em"><fo:list-item-label
end-indent="label-end()"><fo:block/></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>
- "Parameters" -- The Parameters describe the details of
- the measurement.
-
</fo:block></fo:list-item-body></fo:list-item></fo:list-block><fo:block
font-weight="bold" font-size="11pt" keep-with-next="always"
space-before="11pt" space-after="3pt"
id="rfc.section.3.1.1">3.1.1 Subject</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">The "Subject" identifies the measured
entity. For networks,
+ "Subject" -- The Subject identifies the entity being
+ measured. This could include the network path between a
+ pair of hosts, an interface on a router, or a specific
+ location on the network from which flow or packet data is
+ captured.
+ </fo:block></fo:list-item-body></fo:list-item><fo:list-item
space-before=".25em" space-after=".25em"><fo:list-item-label
end-indent="label-end()"><fo:block/></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>
+ "EventType" -- The EventType identifies exactly what sort
+ of measurement Event occurred.
+ </fo:block></fo:list-item-body></fo:list-item><fo:list-item
space-before=".25em" space-after=".25em"><fo:list-item-label
end-indent="label-end()"><fo:block/></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>
+ "Parameters" -- The Parameters describe the details of
+ the measurement.
+
</fo:block></fo:list-item-body></fo:list-item></fo:list-block><fo:block
font-weight="bold" font-size="11pt" keep-with-next="always"
space-before="11pt" space-after="3pt"
id="rfc.section.3.1.1">3.1.1 Subject</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">The "Subject" identifies the measured
entity. For networks,
this may represent a path between two hosts or an interface
on a network device.</fo:block><fo:block font-weight="bold"
font-size="11pt" keep-with-next="always" space-before="11pt"
space-after="3pt" id="rfc.section.3.1.2">3.1.2 Event
Type</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">The "Event Type" is the canonical name of the aspect of the
subject being measured, or the actual event
@@ -180,11 +180,10 @@
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.9">9. Base Schema</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
<fo:block font-family="monospace" font-size="9pt"
background-color="#dddddd" white-space-treatment="preserve"
linefeed-treatment="preserve" white-space-collapse="false">#
##############################################################
#
-# File: nmbase.rnc - Main schema definition
-# Version: $Id: nmbase.rnc 225 2007-05-02 18:16:45Z zurawski $
-# Purpose: This is the main relax schema file, it defines
-# the general makeup of an NMWG structured message.
-# Reference: http://books.xmlschemata.org/relaxng/page2.html
+# File: nmbase.rnc - Main schema definition
+# Version: $Id: nmbase.rnc 230 2007-05-07 13:12:03Z swany $
+# Purpose: This is the main schema file, it defines the
+# general structure of an NMWG message or store
#
# ##############################################################

@@ -202,8 +201,8 @@
include "filter.rnc"

# ##############################################################
-# Every suitable NMWG document should begin with either a
-# 'store' or 'message' element, in the appropriate namespace.
+# Every NMWG document should begin with either a 'store' or
+# 'message' element
# Patterns are defined for the content of each element.
#
# Example (using message):
@@ -213,11 +212,11 @@
# type="REQUIRED_TYPE"
# xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
#
-# 
+# 
#
-# 
+# 
#
-# 
+# 
#
# </nmwg:message>
#
@@ -256,13 +255,10 @@

# ##############################################################
-# Metadata is the 'data' that describes physical measurements.
-# Metadata can be a physical address or a geographical location;
-# any form of static, re-usable designation. It is important to
-# note that the subject namespace and parameters namespace MUST
-# match (or the parameters can be a generic NMWG) or bad things
-# will occur.
+# Metadata is the information that describes data. This
+# information doesn't change over time
#
+#
# Example:
#
# <nmwg:metadata id="REQUIRED_ID"
@@ -492,12 +488,15 @@
}

# ##############################################################
-# CommonTime is used as a shortcut that is able to 'factor out'
-# a frequently occurring time range that a bunch of datum (or
-# other) elements might share, thus reducing complexity of XML
-# representation. CommonTime is similar to the other NMWG time
+# CommonTime is used as a shortcut that is able to 'factor out'
+# a frequently occurring time range that a group of datum (or
+# other) elements might share, thus reducing the verbosity of the
+# XML representation. CommonTime is similar to the other NMWG time
# stamps (from nmtime.rnc) in its potential time representations.
#
+# It is unfortunate that it needs to be in this file and not
+# nmtime.rnc, but as it occurs outside the datum, it is here.
+#
# Example:
#
# <nmwg:commonTime type="REQUIRED_TYPE" value="OPTIONAL_VALUE"
@@ -505,11 +504,13 @@
# inclusive="OPTIONAL_INCLUSIVE_FLAG"
# xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
#
-# 
+# 
#
# 
#
-# 
+# 
#
# 
#
@@ -623,12 +624,10 @@

<fo:block font-family="monospace" font-size="9pt"
background-color="#dddddd" white-space-treatment="preserve"
linefeed-treatment="preserve" white-space-collapse="false">#
##############################################################
#
-# File: nmtime.rnc - NMWG Time definitions
-# Version: $Id: nmtime.rnc 225 2007-05-02 18:16:45Z zurawski $
-# Purpose: This describes a general time format for
-# representing measurements. It is far from complete,
-# and may be best represented by other methods.
-# Reference: http://books.xmlschemata.org/relaxng/page2.html
+# File: nmtime.rnc - NMWG Time definitions
+# Version: $Id: nmtime.rnc 230 2007-05-07 13:12:03Z swany $
+# Purpose: This describes a set of time formats for
+# representing measurements.
#
# ##############################################################

@@ -709,13 +708,9 @@

<fo:block font-family="monospace" font-size="9pt"
background-color="#dddddd" white-space-treatment="preserve"
linefeed-treatment="preserve" white-space-collapse="false">#
##############################################################
#
-# File: nmtopo.rnc - Schema to describe topological
-# features to be used in subject
+# File: nmtopo.rnc - Schema to describe topological
# elements.
-# Version: $Id: nmtopo.rnc 209 2007-02-15 17:20:25Z zurawski $
-# Purpose: This file lays out some major network topologies
-# used in measurement.
-# Reference: http://books.xmlschemata.org/relaxng/page2.html
+# Version: $Id: nmtopo.rnc 230 2007-05-07 13:12:03Z swany $
#
# ##############################################################

@@ -860,11 +855,9 @@
#
# File: ping.rnc - Specialized schema for the ping
# tool
-# Version: $Id: ping.rnc 205 2007-02-05 17:33:00Z zurawski $
-# Purpose: Describes specific elements to be used in the
-# representation and handling of ping
-# measurements.
-# Reference: http://books.xmlschemata.org/relaxng/page2.html
+# Version: $Id: ping.rnc 230 2007-05-07 13:12:03Z swany $
+# Purpose: Defines elements to be used in the representation
+# of ping measurements.
#
# ##############################################################

@@ -890,31 +883,7 @@

# ##############################################################
-# Metadata is the 'data' that describes physical measurements.
-# Metadata can be something such as a physical address, or
-# a geographical location; any form of static, re-usable
-# designation. It is important to note that the subject
-# namespace and parameters namespace MUST match (or the parameters
-# can be a generic NMWG) or bad things will occur.
-#
-# Example:
-#
-# <nmwg:metadata id="REQUIRED_ID"
-# metadataIdRef="OPTIONAL_REFERENCE_ID"
-# xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
-#
-# 
-#
-# 
-#
-# 
-#
-# 
-#
-# 
-#
-# </nmwg:metadata>
-#
+# Metadata
# ##############################################################

PingMetadata =
@@ -1078,30 +1047,7 @@

# ##############################################################
-# CommonTime is used a a shortcut able to 'factor out' a frequently
-# occurring time range that a bunch of datum (or other) elements
-# might share, thus reducing complexity of XML representation.
-# CommonTime is similar to the other NMWG time stamps (from
-# nmtime.rnc) in its potential time representations.
-#
-# Example:
-#
-# <nmwg:commonTime type="REQUIRED_TYPE" value="OPTIONAL_VALUE"
-# duration="OPTIONAL_DURATION"
-# inclusive="OPTIONAL_INCLUSIVE_FLAG"
-# xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
-#
-# 
-#
-# 
-#
-# 
-#
-# 
-#
-# 
-# </nmwg:commonTime>
-#
+# CommonTime
# ##############################################################

PingCommonTime =

Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.html
===================================================================
--- trunk/nmwg/doc/nm-schema-base/nm-schema-base.html 2007-09-08 03:07:54
UTC (rev 264)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.html 2007-09-13 23:24:25
UTC (rev 265)
@@ -268,7 +268,7 @@
content: "RFC ";
}
@top-right {
- content: "May 2007";
+ content: "September 2007";
}
@top-center {
content: "
@@ -318,7 +318,7 @@
<meta name="generator"
content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.291,
2006/10/29 09:03:19, XSLT vendor: SAXON 8.8 from Saxonica
http://www.saxonica.com/";>
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/";>
<meta name="DC.Creator" content="Swany, M">
-<meta name="DC.Date.Issued" scheme="ISO8601" content="2007-05">
+<meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09">
</head>
<body>
<table summary="header information" class="header" border="0"
cellpadding="1" cellspacing="1">
@@ -333,7 +333,7 @@
</tr>
<tr>
<td class="front left">Intended status: Informational</td>
-<td class="front right">May 2007</td>
+<td class="front right">September 2007</td>
</tr>
</table>
An Extensible Schema for Network Measurement and
Performance Data
@@ -423,11 +423,10 @@
<pre>
#
##############################################################
# 
-# File: nmbase.rnc - Main schema definition
-# Version: $Id: nmbase.rnc 225 2007-05-02 18:16:45Z
zurawski $
-# Purpose: This is the main relax schema file, it
defines 
-# the general makeup of an NMWG structured
message.
-# Reference:
http://books.xmlschemata.org/relaxng/page2.html
+# File: nmbase.rnc - Main schema definition
+# Version: $Id: nmbase.rnc 230 2007-05-07 13:12:03Z swany
$
+# Purpose: This is the main schema file, it defines
the
+# general structure of an NMWG message or
store
# 
#
##############################################################

@@ -445,8 +444,8 @@
include "filter.rnc"

#
##############################################################
-# Every suitable NMWG document should begin with either a

-# 'store' or 'message' element, in the appropriate
namespace.
+# Every NMWG document should begin with either a 'store' or

+# 'message' element
# Patterns are defined for the content of each
element.
# 
# Example (using message):
@@ -456,11 +455,11 @@
# type="REQUIRED_TYPE"
#
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
# 
-# 
+# 
#
-# 
+# 
# 
-# 
+# 
# 
# </nmwg:message>
# 
@@ -499,13 +498,10 @@

#
##############################################################
-# Metadata is the 'data' that describes physical
measurements.
-# Metadata can be a physical address or a geographical
location;
-# any form of static, re-usable designation. It is important
to
-# note that the subject namespace and parameters namespace
MUST
-# match (or the parameters can be a generic NMWG) or bad
things
-# will occur.
+# Metadata is the information that describes data.
This
+# information doesn't change over time
#
+#
# Example: 
# 
# <nmwg:metadata id="REQUIRED_ID" 
@@ -735,12 +731,15 @@
}

#
##############################################################
-# CommonTime is used as a shortcut that is able to 'factor
out' 
-# a frequently occurring time range that a bunch of datum
(or 
-# other) elements might share, thus reducing complexity of
XML 
-# representation. CommonTime is similar to the other NMWG
time 
+# CommonTime is used as a shortcut that is able to 'factor
out' 
+# a frequently occurring time range that a group of datum
(or 
+# other) elements might share, thus reducing the verbosity
of the 
+# XML representation. CommonTime is similar to the other
NMWG time 
# stamps (from nmtime.rnc) in its potential time
representations.
#
+# It is unfortunate that it needs to be in this file and
not
+# nmtime.rnc, but as it occurs outside the datum, it is
here.
+#
# Example: 
# 
# <nmwg:commonTime type="REQUIRED_TYPE"
value="OPTIONAL_VALUE"
@@ -748,11 +747,13 @@
# inclusive="OPTIONAL_INCLUSIVE_FLAG"
#
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
# 
-# 
+# 
# 
# 
# 
-# 
+# 
# 
# 
# 
@@ -870,12 +871,10 @@
<pre>
#
##############################################################
# 
-# File: nmtime.rnc - NMWG Time definitions
-# Version: $Id: nmtime.rnc 225 2007-05-02 18:16:45Z
zurawski $
-# Purpose: This describes a general time format for

-# representing measurements. It is far from
complete, 
-# and may be best represented by other
methods.
-# Reference:
http://books.xmlschemata.org/relaxng/page2.html
+# File: nmtime.rnc - NMWG Time definitions
+# Version: $Id: nmtime.rnc 230 2007-05-07 13:12:03Z swany
$
+# Purpose: This describes a set of time formats for 
+# representing measurements. 
# 
#
##############################################################

@@ -960,13 +959,9 @@
<pre>
#
##############################################################
# 
-# File: nmtopo.rnc - Schema to describe topological

-# features to be used in subject

+# File: nmtopo.rnc - Schema to describe
topological
# elements.
-# Version: $Id: nmtopo.rnc 209 2007-02-15 17:20:25Z
zurawski $
-# Purpose: This file lays out some major network
topologies
-# used in measurement. 
-# Reference:
http://books.xmlschemata.org/relaxng/page2.html
+# Version: $Id: nmtopo.rnc 230 2007-05-07 13:12:03Z swany
$
# 
#
##############################################################

@@ -1117,11 +1112,9 @@
# 
# File: ping.rnc - Specialized schema for the ping

# tool
-# Version: $Id: ping.rnc 205 2007-02-05 17:33:00Z
zurawski $
-# Purpose: Describes specific elements to be used in
the
-# representation and handling of ping
-# measurements.
-# Reference:
http://books.xmlschemata.org/relaxng/page2.html
+# Version: $Id: ping.rnc 230 2007-05-07 13:12:03Z swany
$
+# Purpose: Defines elements to be used in the
representation 
+# of ping measurements.
# 
#
##############################################################

@@ -1147,31 +1140,7 @@

#
##############################################################
-# Metadata is the 'data' that describes physical
measurements. 
-# Metadata can be something such as a physical address, or

-# a geographical location; any form of static, re-usable

-# designation. It is important to note that the
subject
-# namespace and parameters namespace MUST match (or the
parameters
-# can be a generic NMWG) or bad things will occur.
-#
-# Example: 
-# 
-# <nmwg:metadata id="REQUIRED_ID" 
-# metadataIdRef="OPTIONAL_REFERENCE_ID"
-#
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
-# 
-# 
-# 
-# 
-#
-# 
-# 
-# 
-# 
-#  
-#
-# </nmwg:metadata>
-# 
+# Metadata 
#
##############################################################

PingMetadata = 
@@ -1335,30 +1304,7 @@

#
##############################################################
-# CommonTime is used a a shortcut able to 'factor out' a
frequently
-# occurring time range that a bunch of datum (or other)
elements
-# might share, thus reducing complexity of XML
representation. 
-# CommonTime is similar to the other NMWG time stamps (from

-# nmtime.rnc) in its potential time representations.
-#
-# Example: 
-# 
-# <nmwg:commonTime type="REQUIRED_TYPE"
value="OPTIONAL_VALUE"
-# duration="OPTIONAL_DURATION" 
-# inclusive="OPTIONAL_INCLUSIVE_FLAG"
-#
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/">
-# 
-# 
-# 
-# 
-# 
-# 
-# 
-# 
-# 
-# 
-# </nmwg:commonTime>
-# 
+# CommonTime 
#
##############################################################

PingCommonTime = 

Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.pdf
===================================================================
(Binary files differ)

Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.xml
===================================================================
--- trunk/nmwg/doc/nm-schema-base/nm-schema-base.xml 2007-09-08 03:07:54
UTC (rev 264)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.xml 2007-09-13 23:24:25
UTC (rev 265)
@@ -26,7 +26,7 @@
Newark, DE 19716
</organization>
</author>
- <date month="May" year="2007"/>
+ <date month="September" year="2007"/>
</front>

<middle>
@@ -41,39 +41,39 @@
environments, such as Grid computing.
</t>

- <t>
- This work is born of the need for a common mechanism for the
- exchange of network measurement and performance data. In the
- case of research-oriented networks, parties often want to
- exchange network performance data with neighbors for debugging
- purposes. In general, however, there is no single system that is
- in use. In the Grid community, the need to exchange network
- metrics of various sorts is often highlighted. In short it is
- highly desirable to have an extensible schema for network
- performance information that gives a common, general framework
- for representation and exchange.
- </t>
+ <t>
+ This work is born of the need for a common mechanism for the
+ exchange of network measurement and performance data. In the
+ case of research-oriented networks, parties often want to
+ exchange network performance data with neighbors for debugging
+ purposes. In general, however, there is no single system that is
+ in use. In the Grid community, the need to exchange network
+ metrics of various sorts is often highlighted. In short it is
+ highly desirable to have an extensible schema for network
+ performance information that gives a common, general framework
+ for representation and exchange.
+ </t>

- <t>
- This document builds on previous versions of the network
- measurement schemata. This document describes Version 2 of the
- Grid Forum's Network Measurement Working Group (NM-WG) schema.
- </t>
+ <t>
+ This document builds on previous versions of the network
+ measurement schemata. This document describes Version 2 of the
+ Grid Forum's Network Measurement Working Group (NM-WG) schema.
+ </t>

- <section id="goals" title="Goals">
- <t>
- The goal is to define a neutral representation for network
- measurements that can be easily extended to support new types
- of data. This representation should identify forms of network
- performance data as well as to create standardized mechanism
- to both describe and publish these metrics.
- </t>
- </section>
+ <section id="goals" title="Goals">
+ <t>
+ The goal is to define a neutral representation for network
+ measurements that can be easily extended to support new types
+ of data. This representation should identify forms of network
+ performance data as well as to create standardized mechanism
+ to both describe and publish these metrics.
+ </t>
+ </section>

</section>
-
+
<section id="design_philosophy" title="Design Philosophy">

<t>
@@ -91,7 +91,6 @@
between various data elements and in data "Stores" -- persistent
storage of XML documents representing system state.
</t>
-

</section>
@@ -129,30 +128,30 @@
</t>

<list>
- <t>
- "Subject" -- The Subject identifies the entity being
- measured. This could include the network path
between a
- pair of hosts, an interface on a router, or a specific
- location on the network from which flow or packet
data is
- captured.
- </t>
- <t>
- "EventType" -- The EventType identifies exactly what
sort
- of measurement Event occurred.
- </t>
- <t>
- "Parameters" -- The Parameters describe the details of
- the measurement.
- </t>
+ <t>
+ "Subject" -- The Subject identifies the entity being
+ measured. This could include the network path between a
+ pair of hosts, an interface on a router, or a specific
+ location on the network from which flow or packet data is
+ captured.
+ </t>
+ <t>
+ "EventType" -- The EventType identifies exactly what sort
+ of measurement Event occurred.
+ </t>
+ <t>
+ "Parameters" -- The Parameters describe the details of
+ the measurement.
+ </t>
</list>
+

-
<section id="subject" title="Subject">
<t>The "Subject" identifies the measured entity. For networks,
this may represent a path between two hosts or an interface
on a network device.</t>
</section>
-
+
<section id="eventtype" title="Event Type">
<t>The "Event Type" is the canonical name of the aspect of the
subject being measured, or the actual event
@@ -168,9 +167,9 @@
value pairs. The value of a parameter can itself be a
complex XML element.</t>
</section>
-
+
</section>
-
+
<section id="data" title="Data">
<t>
The "Data" element has an Identifier (Id) and an Identifier

Added: trunk/nmwg/doc/nm-topo/fop.jar

Property changes on: trunk/nmwg/doc/nm-topo/fop.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream

Added: trunk/nmwg/doc/nm-topo/inline.pl

Property changes on: trunk/nmwg/doc/nm-topo/inline.pl
___________________________________________________________________
Name: svn:executable
+ *

Added: trunk/nmwg/doc/nm-topo/make.sh

Property changes on: trunk/nmwg/doc/nm-topo/make.sh
___________________________________________________________________
Name: svn:executable
+ *

Added: trunk/nmwg/doc/nm-topo/nm-topo.fo

Added: trunk/nmwg/doc/nm-topo/nm-topo.html

Added: trunk/nmwg/doc/nm-topo/nm-topo.pdf

Property changes on: trunk/nmwg/doc/nm-topo/nm-topo.pdf
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream

Added: trunk/nmwg/doc/nm-topo/nm-topo.xml

Added: trunk/nmwg/doc/nm-topo/post.pl

Property changes on: trunk/nmwg/doc/nm-topo/post.pl
___________________________________________________________________
Name: svn:executable
+ *

Added: trunk/nmwg/doc/nm-topo/rfc2629-other.ent

Added: trunk/nmwg/doc/nm-topo/rfc2629-xhtml.ent

Added: trunk/nmwg/doc/nm-topo/rfc2629.dtd

Added: trunk/nmwg/doc/nm-topo/rfc2629.xslt

Added: trunk/nmwg/doc/nm-topo/rfc2629toFO.xslt

Added: trunk/nmwg/doc/nm-topo/saxon8.jar

Property changes on: trunk/nmwg/doc/nm-topo/saxon8.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream

Added: trunk/nmwg/doc/nm-topo/schema

Property changes on: trunk/nmwg/doc/nm-topo/schema
___________________________________________________________________
Name: svn:special
+ *

Added: trunk/nmwg/doc/nm-topo/tmp.nm-topo.xml

nmwg: r265 - in trunk/nmwg/doc: . nm-schema-base nm-topo, svnlog, 09/13/2007

List archive

nmwg: r265 - in trunk/nmwg/doc: . nm-schema-base nm-topo