perfsonar-dev - nmwg: r227 - trunk/nmwg/doc/nm-schema-base
Subject: perfsonar development work
List archive
- From:
- To: ,
- Subject: nmwg: r227 - trunk/nmwg/doc/nm-schema-base
- Date: Sun, 6 May 2007 12:45:28 -0400
Author: swany
Date: 2007-05-06 12:45:28 -0400 (Sun, 06 May 2007)
New Revision: 227
Added:
trunk/nmwg/doc/nm-schema-base/make.sh
Removed:
trunk/nmwg/doc/nm-schema-base/stuff.sh
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:
Pass through the text (hopefully keeping all Susan's edits.)
We still need to describe the basic Id attributes in the text.
This would be a good time to use some auto-generation from
<documentation> tags in the schema (which, of course, aren't
there....)
Copied: trunk/nmwg/doc/nm-schema-base/make.sh (from rev 201,
trunk/nmwg/doc/nm-schema-base/stuff.sh)
Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo
===================================================================
--- trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo 2007-05-02 18:25:36
UTC (rev 226)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.fo 2007-05-06 16:45:28
UTC (rev 227)
@@ -1,4 +1,4 @@
-<?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></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
Versioning</fo:bookma
rk-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.6"><fo:bookmark-title>6 Metadata
Chaining</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.7"><fo:bookmark-title>7 Operation
Metadata</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.8"><fo:bookmark-title>8 Base
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.9"><fo:bookmark-title>9 Time
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.10"><fo:bookmark-title>10 Security
Concerns</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.references"><fo:bookmark-title>11
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>Intellectual Property and
Copyright Statements</fo:bookmark-title></
fo:bookmark></fo:bookmark-tree><fo:page-sequence master-refe!
rence="s
equence" 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
Versioning</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.6"><fo:bookmark-title>6 Metadata
Chaining</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.7"><fo:bookmark-title>7 Operation
Metadata</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.8"><fo:bookmark-title>8 Base
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.9"><fo:bookmark-title>9 Time
Schema</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.10"><fo:bookmark-title>10 Security
Concerns</fo:bookmark-title></fo:bookmark><fo:bookmark
internal-destination="rfc.section.11"><fo:bookmark-title>11
Appendices</fo:bookmark-title><fo:bookmark inte
rnal-destination="rfc.section.11.1"><fo:bookmark-title>11.1 !
Acknowle
dgements</fo:bookmark-title></fo:bookmark></fo:bookmark><fo:bookmark
internal-destination="rfc.references"><fo:bookmark-title>12
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>Intellectual 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>
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">
An Extensible Schema for Network Measurement and Performance Data
@@ -71,21 +71,55 @@
</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
+ </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 (i.e. "characteristic") being
sought.</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.3">3.1.3 Parameters</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">The "Parameters"
describe the exact
- way in which a particular measurement was gathered.
</fo:block><fo:block font-weight="bold" font-size="12pt"
keep-with-next="always" space-before="12pt" space-after="6pt"
id="rfc.section.3.2">3.2 Data</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">The "Data" element refers to the
"Metadata" that describes
- it. It contains some number of "Datum" elements, which hold
- the actual timestamp and value of the measurement or value
- of the event. </fo:block><fo:block font-weight="bold"
font-size="14pt" keep-with-next="always" space-after="7pt"
page-break-before="always" id="rfc.section.4">4. XML
Namespaces</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">We have adopted XML namespaces to vary the schema of the
- basic elements for various different types of measurements.
</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">We envision there being two major classes of namespace
URIs.
+
</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
+ (i.e. "characteristic") being reported.</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.3">3.1.3 Parameters</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">The "Parameters"
describe the exact way in which a
+ particular measurement was gathered. These can include
+ parameters to active measurement tools. Essentially,
+ anything needed to determine which measurements are fungible
+ should be included here.</fo:block><fo:block font-weight="bold"
font-size="12pt" keep-with-next="always" space-before="12pt"
space-after="6pt" id="rfc.section.3.2">3.2 Data</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
+ The "Data" element has an Identifier and an Identifier
+ Reference that refers to the "Metadata" that describes it. It
+ contains some number of "Datum" elements.
+ </fo:block><fo:block font-weight="bold" font-size="11pt"
keep-with-next="always" space-before="11pt" space-after="3pt"
id="rfc.section.3.2.1">3.2.1 Datum</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
+ The "Datum" elements hold the timestamp and value of
the
+ measurement or value of the event. For many network
+ measurement data sources, this can be a time-series of
+ timestamp, value pairs. For other measurement types,
the
+ result value may be a vector.
+ </fo:block><fo:block font-weight="bold" font-size="12pt"
keep-with-next="always" space-before="12pt" space-after="6pt"
id="rfc.section.3.3">3.3 Container Elements</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
+ The above-named elements are currently contained in two types
+ of outer elements, "Message" and "Store". They have exactly
+ the same structure, i.e. containing "Metadata" and "Data"
+ elements. Each may have an attribute called "Type" to
+ indicate its type. Each may also contain one "Parameters"
+ element to indicate Message- or Store-level parameters and
+ options. This allows for a great deal of customization.
+ </fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.4">4. XML Namespaces</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">
+ A key facet in this schema is the observation that the above
+ elements can be used to describe any network measurement, but
+ the exact content of the each will vary with the measurement
+ type. We have adopted XML namespaces to allow reuse of these
+ same basic element names, but to vary the contents of the basic
+ elements for each different type of data.
+ </fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
+ In this way, some superficial examination of the structure of a
+ message or information store can take place without looking at
+ the details of the contents. Some processing functionality
+ should be able to consume new data types with no modificiation.
+ </fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
+ We envision there being two major classes of namespace URIs.
The first is a canonical name based on the Hierarchy of Network
- Measurements (cite). The second is based on an organization's
- domain name and allows for autonomous extension.</fo:block><fo:block
font-weight="bold" font-size="14pt" keep-with-next="always" space-after="7pt"
page-break-before="always"
id="rfc.section.5">5. Versioning</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">While the working group has made every
effort to completely
+ Measurements from this working group. (cite). The second is
+ based on an organization's domain name and allows for autonomous
+ extension in much the same way as the Enterprise branch of the
+ OID space (cite) allows.
+ </fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.5">5. Versioning</fo:block><fo:block space-before=".5em"
space-after=".5em" start-indent="2em">While the working group has made every
effort to completely
describe a few measurement types, we are well aware that tools,
and ideas about how to represent them, may change. For this
reason, each of the schema areas must have a version
number.</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
@@ -93,22 +127,36 @@
namespaces end in a version number. TBD, conforming to recent
GFD on namespaces.
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.6">6. Metadata Chaining</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
- While a complete Metadata block can be used to describe,
- unambiguously, a data block, it is often desirable to
- combine multiple, partial Metadata blocks together. The
- main reason for this is reuse of information. Using the
- "metadataIdRef" attribute of a Metadata block allows us
- to form a "chain" of Metadata blocks.
+ While a complete Metadata block can be used to unambiguously
+ describe a data block, it is often desirable to combine
+ multiple, partial Metadata blocks together. The main reason for
+ this is reuse of information. Using the "metadataIdRef"
+ attribute of a Metadata block allows us to form a "chain" of
+ Metadata blocks. This means that not all Metadata blocks will
+ have an associated eventType. At the end of the chain, however,
+ there MUST be an event type.
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.7">7. Operation Metadata</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
- In addition to describing sets of raw data, Metadata blocks
- can also be used to describe transformations performed on a
- dataset. Thus, a list of Metadata blocks, including origin
- and transformations, can be used to describe, unambiguously,
- the provenance of any network data.
+ In addition to describing sets of raw data, Metadata blocks can
+ also be used to describe transformation operations performed on
+ a set of data. Thus, a list of Metadata blocks, including origin
+ and transformations, can be used to unambiguously describe the
+ provenance of any network data. This can also be used in cases
+ where the transformation is "internal" and the original data is
+ not available. This can be thought of as describing set
+ operations on the original set as it passes through a list of
+ operators.
+
</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
- This relationship between Metadata blocks is expressed by
- having the Subject metadataIdRef refer to another Metadata,
- which denotes having it be input to an operation.
+ One example of this is the selection of a subset of data from a
+ a set, based on time or value. A "select" metadata block can be
+ used to describe this filtering operation independent of the
+ source. Formally, we can think of this as as an operation on
+ one set that produces another set. This metadata block must
+ unambiguously defining that set operation.
+ </fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
+ This relationship between Metadata blocks is expressed by having
+ the Subject metadataIdRef refer to another Metadata, which
+ denotes having it be input to an operation.
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-after="7pt" page-break-before="always"
id="rfc.section.8">8. 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">#
##############################################################
#
@@ -661,8 +709,18 @@
or consume noticeable amounts of resources should be taken
carefully, and the distribution of information to other sites
that cannot be obtained readily by other users at those sites
- should be considered carefully. </fo:block><fo:block
font-weight="bold" font-size="14pt" keep-with-next="always" space-after="7pt"
page-break-before="always" id="rfc.authors">Author's
Address</fo:block><fo:block space-before="1em"><fo:wrapper
font-weight="bold">Martin Swany</fo:wrapper><fo:wrapper>
(Editor)</fo:wrapper></fo:block><fo:block>
+ should be considered carefully. </fo:block><fo:block
font-weight="bold" font-size="14pt" keep-with-next="always" space-after="7pt"
page-break-before="always"
id="rfc.section.11">11. Appendices</fo:block><fo:block font-weight="bold"
font-size="12pt" keep-with-next="always" space-before="12pt"
space-after="6pt" id="rfc.section.11.1">11.1 Acknowledgements</fo:block>
+ We gratefully acknowledge the contributions of: Jeff Boote, Eric
+ Boyd, Dan Gunter, and Jason Zurawski and (who else??) the other
+ members of the Network Measurements Working Group.<fo:block
font-weight="bold" font-size="14pt" keep-with-next="always"
space-before="0pt" space-after="7pt" id="rfc.references"
page-break-before="always">12
+ References</fo:block><fo:list-block
provisional-distance-between-starts="3em"><fo:list-item
space-after=".5em"><fo:list-item-label end-indent="label-end()"><fo:block
id="tridentcom">[1]</fo:block></fo:list-item-label><fo:list-item-body
start-indent="body-start()"><fo:block>Zurawski, J., Swany, M., and D. Gunter,
"A Scalable Framework for Representation and Exchange of
+ Network Measurements", In Proceedings of 2nd International
IEEE/Create-Net
+ Conference on Testbeds and Research Infrastructures for the
+ Development of Networks and Communities (Tridentcom
+
2006).</fo:block></fo:list-item-body></fo:list-item></fo:list-block><fo:block
font-weight="bold" font-size="14pt" keep-with-next="always" space-after="7pt"
page-break-before="always" id="rfc.authors">Author's
Address</fo:block><fo:block space-before="1em"><fo:wrapper
font-weight="bold">D. Martin Swany</fo:wrapper><fo:wrapper>
(Editor)</fo:wrapper></fo:block><fo:block>
University of Delaware
+ Department of Computer and Information Sciences
+ Newark, DE 19716
</fo:block><fo:block font-weight="bold" font-size="14pt"
keep-with-next="always" space-before="14pt" space-after="7pt"><fo:block
id="rfc.copyright"/>Full Copyright Statement</fo:block><fo:block
space-before=".5em" space-after=".5em" start-indent="2em">
Copyright © The Open Grid Forum (2007). All Rights Reserved.
</fo:block><fo:block space-before=".5em" space-after=".5em"
start-indent="2em">
Modified: trunk/nmwg/doc/nm-schema-base/nm-schema-base.html
===================================================================
--- trunk/nmwg/doc/nm-schema-base/nm-schema-base.html 2007-05-02 18:25:36
UTC (rev 226)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.html 2007-05-06 16:45:28
UTC (rev 227)
@@ -293,7 +293,7 @@
content: normal;
}
}
-</style><link rel="Author" href="#rfc.authors"><link rel="Copyright"
href="#rfc.copyright"><link rel="Chapter" title="1 Introduction"
href="#rfc.section.1"><link rel="Chapter" title="2 Design Philosophy"
href="#rfc.section.2"><link rel="Chapter" title="3 Basic Elements"
href="#rfc.section.3"><link rel="Chapter" title="4 XML Namespaces"
href="#rfc.section.4"><link rel="Chapter" title="5 Versioning"
href="#rfc.section.5"><link rel="Chapter" title="6 Metadata Chaining"
href="#rfc.section.6"><link rel="Chapter" title="7 Operation Metadata"
href="#rfc.section.7"><link rel="Chapter" title="8 Base Schema"
href="#rfc.section.8"><link rel="Chapter" title="9 Time Schema"
href="#rfc.section.9"><link rel="Chapter" title="10 Security Concerns"
href="#rfc.section.10"><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"></head><body><table
summary="header information" class="header" border="0" cellpadding="1"
cellspacing="1"><tr><td class="front left">Network Measurement Working
Group</td><td class="front right">M Swany, Editor</td></tr><tr><td
class="front left"></td><td class="front right">UDel</td></tr><tr><td
class="front left">Intended status: Informational</td><td class="front
right">May 2007</td></tr></table><p class="title">An Extensible Schema for
Network Measurement and Performance Data</p><h1><a id="rfc.status"
href="#rfc.status">Status of this Memo</a></h1><p>This memo provides
information for the Grid community. It does not specify any standards or
technical recommendations. Distribution is unlimited.</p><h1><a
id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright
Notice</a></h1><p>Copyright � The Open Grid Forum (2007). All Rights
Reserved.</p><hr
class="noprint"><h1 id="rfc.section.1" class="np"><a href="#!
rfc.sect
ion.1">1.</a> <a id="intro" href="#intro">Introduction</a></h1><p
id="rfc.section.1.p.1">This document presents an extensible encoding standard
for network measurement and performance data. Uniform encoding of this class
of information is a key problem for federated network management, and
multi-domain dynamic provisioning of network circuits, as well as in advanced
distributed computing environments, such as Grid computing.</p><p
id="rfc.section.1.p.2">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 co
mmon, general framework for representation and exchange.</p><p
id="rfc.section.1.p.3">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.</p><h2
id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> Goals</h2><p
id="rfc.section.1.1.p.1">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.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a
href="#rfc.section.2">2.</a> Design Philosophy</h1><p
id="rfc.section.2.p.1">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 observa
tion that network measurement data can be divided into two m!
ajor cla
sses. The first class is the Metadata, which describes the type of
measurement data, the entity or entities being measured and the particular
parameters of the measurement. The second class is the data itself, which is,
at its simplest, a timestamp and a value, or vector of values. This division
of Metadata and Data is present throughout the system. This structure is
present both in the "Messages" sent between various data elements and in data
"Stores" -- persistent storage of XML documents representing system
state.</p><hr class="noprint"><h1 id="rfc.section.3" class="np"><a
href="#rfc.section.3">3.</a> Basic Elements</h1><p
id="rfc.section.3.p.1">This schema defines the basic elements that can be
used to represent performance data. The first distinction is between the
"Metadata", the relatively static information regarding the data, and the
"Data" itself, which generally changes over time. The key idea is that, for
repeated measurements, which is a common case for perf
ormance data in networks and Grids, the Metadata need not be passed
repeatedly, saving space and effort.</p><h2 id="rfc.section.3.1"><a
href="#rfc.section.3.1">3.1</a> Metadata</h2><p
id="rfc.section.3.1.p.1">The Metadata must describe the Data unambiguously.
To accomplish this, the Metadata must include three key things:</p><dl
class="empty"><dd>"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.</dd><dd>"EventType" -- The EventType identifies
exactly what sort of measurement Event occurred.</dd><dd>"Parameters" -- The
Parameters describe the details of the measurement.</dd></dl><h3
id="rfc.section.3.1.1"><a
href="#rfc.section.3.1.1">3.1.1</a> Subject</h3><p
id="rfc.section.3.1.1.p.1">The "Subject" identifies the measured entity. For
networks, this may represent a path between two hosts
or an interface on a network device.</p><h3 id="rfc.section.!
3.1.2"><
a href="#rfc.section.3.1.2">3.1.2</a> Event Type</h3><p
id="rfc.section.3.1.2.p.1">The "Event Type" is the canonical name of the
aspect of the subject being measured, or the actual event (i.e.
"characteristic") being sought.</p><h3 id="rfc.section.3.1.3"><a
href="#rfc.section.3.1.3">3.1.3</a> Parameters</h3><p
id="rfc.section.3.1.3.p.1">The "Parameters" describe the exact way in which a
particular measurement was gathered.</p><h2 id="rfc.section.3.2"><a
href="#rfc.section.3.2">3.2</a> Data</h2><p id="rfc.section.3.2.p.1">The
"Data" element refers to the "Metadata" that describes it. It contains some
number of "Datum" elements, which hold the actual timestamp and value of the
measurement or value of the event.</p><hr class="noprint"><h1
id="rfc.section.4" class="np"><a href="#rfc.section.4">4.</a> XML
Namespaces</h1><p id="rfc.section.4.p.1">We have adopted XML namespaces to
vary the schema of the basic elements for various different types of
measurements.<
/p><p id="rfc.section.4.p.2">We envision there being two major classes of
namespace URIs. The first is a canonical name based on the Hierarchy of
Network Measurements (cite). The second is based on an organization's domain
name and allows for autonomous extension.</p><hr class="noprint"><h1
id="rfc.section.5" class="np"><a
href="#rfc.section.5">5.</a> Versioning</h1><p
id="rfc.section.5.p.1">While the working group has made every effort to
completely describe a few measurement types, we are well aware that tools,
and ideas about how to represent them, may change. For this reason, each of
the schema areas must have a version number.</p><p id="rfc.section.5.p.2">To
accomplish this, each of the URIs that comprise the namespaces end in a
version number. TBD, conforming to recent GFD on namespaces.</p><hr
class="noprint"><h1 id="rfc.section.6" class="np"><a
href="#rfc.section.6">6.</a> Metadata Chaining</h1><p
id="rfc.section.6.p.1">While a complete Metadata block can b
e used to describe, unambiguously, a data block, it is often!
desirab
le to combine multiple, partial Metadata blocks together. The main reason for
this is reuse of information. Using the "metadataIdRef" attribute of a
Metadata block allows us to form a "chain" of Metadata blocks.</p><hr
class="noprint"><h1 id="rfc.section.7" class="np"><a
href="#rfc.section.7">7.</a> Operation Metadata</h1><p
id="rfc.section.7.p.1">In addition to describing sets of raw data, Metadata
blocks can also be used to describe transformations performed on a dataset.
Thus, a list of Metadata blocks, including origin and transformations, can be
used to describe, unambiguously, the provenance of any network data.</p><p
id="rfc.section.7.p.2">This relationship between Metadata blocks is expressed
by having the Subject metadataIdRef refer to another Metadata, which denotes
having it be input to an operation.</p><hr class="noprint"><h1
id="rfc.section.8" class="np"><a href="#rfc.section.8">8.</a> Base
Schema</h1><p id="rfc.section.8.p.1"> <pre>
+</style><link rel="Author" href="#rfc.authors"><link rel="Copyright"
href="#rfc.copyright"><link rel="Chapter" title="1 Introduction"
href="#rfc.section.1"><link rel="Chapter" title="2 Design Philosophy"
href="#rfc.section.2"><link rel="Chapter" title="3 Basic Elements"
href="#rfc.section.3"><link rel="Chapter" title="4 XML Namespaces"
href="#rfc.section.4"><link rel="Chapter" title="5 Versioning"
href="#rfc.section.5"><link rel="Chapter" title="6 Metadata Chaining"
href="#rfc.section.6"><link rel="Chapter" title="7 Operation Metadata"
href="#rfc.section.7"><link rel="Chapter" title="8 Base Schema"
href="#rfc.section.8"><link rel="Chapter" title="9 Time Schema"
href="#rfc.section.9"><link rel="Chapter" title="10 Security Concerns"
href="#rfc.section.10"><link rel="Chapter" title="11 Appendices"
href="#rfc.section.11"><link rel="Chapter" href="#rfc.section.12" title="12
References"><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"></head><body><table summary="header information"
class="header" border="0" cellpadding="1" cellspacing="1"><tr><td
class="front left">Network Measurement Working Group</td><td class="front
right">M Swany, Editor</td></tr><tr><td class="front left"></td><td
class="front right">UDel</td></tr><tr><td class="front left">Intended status:
Informational</td><td class="front right">May 2007</td></tr></table><p
class="title">An Extensible Schema for Network Measurement and Performance
Data</p><h1><a id="rfc.status" href="#rfc.status">Status of this
Memo</a></h1><p>This memo provides information for the Grid community. It
does not specify any standards or technical recommendations. Distribution is
unlimited.</p><h1><a id="rfc.copyrightno
tice" href="#rfc.copyrightnotice">Copyright Notice</a></h1><!
p>Copyri
ght � The Open Grid Forum (2007). All Rights Reserved.</p><hr
class="noprint"><h1 id="rfc.section.1" class="np"><a
href="#rfc.section.1">1.</a> <a id="intro"
href="#intro">Introduction</a></h1><p id="rfc.section.1.p.1">This document
presents an extensible encoding standard for network measurement and
performance data. Uniform encoding of this class of information is a key
problem for federated network management, and multi-domain dynamic
provisioning of network circuits, as well as in advanced distributed
computing environments, such as Grid computing.</p><p
id="rfc.section.1.p.2">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 o
ften 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.</p><p id="rfc.section.1.p.3">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.</p><h2 id="rfc.section.1.1"><a
href="#rfc.section.1.1">1.1</a> Goals</h2><p
id="rfc.section.1.1.p.1">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.</p><hr class="noprint"><h1 id="rfc.section.2" class="np"><a
href="#rfc.section.2">2.</a> Design Philosophy</h1><p
id="rfc.section.2.p.1">One of the high-level goals of this representation is
to "normalize" the data representation by removing as much r!
edundanc
y as possible. The basic schema design is based on the observation that
network measurement data can be divided into two major classes. The first
class is the Metadata, which describes the type of measurement data, the
entity or entities being measured and the particular parameters of the
measurement. The second class is the data itself, which is, at its simplest,
a timestamp and a value, or vector of values. This division of Metadata and
Data is present throughout the system. This structure is present both in the
"Messages" sent between various data elements and in data "Stores" --
persistent storage of XML documents representing system state.</p><hr
class="noprint"><h1 id="rfc.section.3" class="np"><a
href="#rfc.section.3">3.</a> Basic Elements</h1><p
id="rfc.section.3.p.1">This schema defines the basic elements that can be
used to represent performance data. The first distinction is between the
"Metadata", the relatively static information regarding the data, and the
"Data" itself, which generally changes over time. The key idea is that, for
repeated measurements, which is a common case for performance data in
networks and Grids, the Metadata need not be passed repeatedly, saving space
and effort.</p><h2 id="rfc.section.3.1"><a
href="#rfc.section.3.1">3.1</a> Metadata</h2><p
id="rfc.section.3.1.p.1">The Metadata must describe the Data unambiguously.
To accomplish this, the Metadata must include three key things:</p><dl
class="empty"><dd>"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.</dd><dd>"EventType" -- The EventType identifies
exactly what sort of measurement Event occurred.</dd><dd>"Parameters" -- The
Parameters describe the details of the measurement.</dd></dl><h3
id="rfc.section.3.1.1"><a
href="#rfc.section.3.1.1">3.1.1</a> Subject</h3><p i
d="rfc.section.3.1.1.p.1">The "Subject" identifies the measu!
red enti
ty. For networks, this may represent a path between two hosts or an interface
on a network device.</p><h3 id="rfc.section.3.1.2"><a
href="#rfc.section.3.1.2">3.1.2</a> Event Type</h3><p
id="rfc.section.3.1.2.p.1">The "Event Type" is the canonical name of the
aspect of the subject being measured, or the actual event (i.e.
"characteristic") being reported.</p><h3 id="rfc.section.3.1.3"><a
href="#rfc.section.3.1.3">3.1.3</a> Parameters</h3><p
id="rfc.section.3.1.3.p.1">The "Parameters" describe the exact way in which a
particular measurement was gathered. These can include parameters to active
measurement tools. Essentially, anything needed to determine which
measurements are fungible should be included here.</p><h2
id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> Data</h2><p
id="rfc.section.3.2.p.1">The "Data" element has an Identifier and an
Identifier Reference that refers to the "Metadata" that describes it. It
contains some number of "Datum" elements.<
/p><h3 id="rfc.section.3.2.1"><a
href="#rfc.section.3.2.1">3.2.1</a> Datum</h3><p
id="rfc.section.3.2.1.p.1">The "Datum" elements hold the timestamp and value
of the measurement or value of the event. For many network measurement data
sources, this can be a time-series of timestamp, value pairs. For other
measurement types, the result value may be a vector.</p><h2
id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> Container
Elements</h2><p id="rfc.section.3.3.p.1">The above-named elements are
currently contained in two types of outer elements, "Message" and "Store".
They have exactly the same structure, i.e. containing "Metadata" and "Data"
elements. Each may have an attribute called "Type" to indicate its type. Each
may also contain one "Parameters" element to indicate Message- or Store-level
parameters and options. This allows for a great deal of customization.</p><hr
class="noprint"><h1 id="rfc.section.4" class="np"><a
href="#rfc.section.4">4.</a> XML
Namespaces</h1><p id="rfc.section.4.p.1">A key facet in this!
schema
is the observation that the above elements can be used to describe any
network measurement, but the exact content of the each will vary with the
measurement type. We have adopted XML namespaces to allow reuse of these same
basic element names, but to vary the contents of the basic elements for each
different type of data.</p><p id="rfc.section.4.p.2">In this way, some
superficial examination of the structure of a message or information store
can take place without looking at the details of the contents. Some
processing functionality should be able to consume new data types with no
modificiation.</p><p id="rfc.section.4.p.3">We envision there being two major
classes of namespace URIs. The first is a canonical name based on the
Hierarchy of Network Measurements from this working group. (cite). The second
is based on an organization's domain name and allows for autonomous extension
in much the same way as the Enterprise branch of the OID space (cite)
allows.</p><hr class="noprin
t"><h1 id="rfc.section.5" class="np"><a
href="#rfc.section.5">5.</a> Versioning</h1><p
id="rfc.section.5.p.1">While the working group has made every effort to
completely describe a few measurement types, we are well aware that tools,
and ideas about how to represent them, may change. For this reason, each of
the schema areas must have a version number.</p><p id="rfc.section.5.p.2">To
accomplish this, each of the URIs that comprise the namespaces end in a
version number. TBD, conforming to recent GFD on namespaces.</p><hr
class="noprint"><h1 id="rfc.section.6" class="np"><a
href="#rfc.section.6">6.</a> Metadata Chaining</h1><p
id="rfc.section.6.p.1">While a complete Metadata block can be used to
unambiguously describe a data block, it is often desirable to combine
multiple, partial Metadata blocks together. The main reason for this is reuse
of information. Using the "metadataIdRef" attribute of a Metadata block
allows us to form a "chain" of Metadata blocks. This me
ans that not all Metadata blocks will have an associated eve!
ntType.
At the end of the chain, however, there MUST be an event type.</p><hr
class="noprint"><h1 id="rfc.section.7" class="np"><a
href="#rfc.section.7">7.</a> Operation Metadata</h1><p
id="rfc.section.7.p.1">In addition to describing sets of raw data, Metadata
blocks can also be used to describe transformation operations performed on a
set of data. Thus, a list of Metadata blocks, including origin and
transformations, can be used to unambiguously describe the provenance of any
network data. This can also be used in cases where the transformation is
"internal" and the original data is not available. This can be thought of as
describing set operations on the original set as it passes through a list of
operators. </p><p id="rfc.section.7.p.2">One example of this is the selection
of a subset of data from a a set, based on time or value. A "select" metadata
block can be used to describe this filtering operation independent of the
source. Formally, we can think of this as as an opera
tion on one set that produces another set. This metadata block must
unambiguously defining that set operation.</p><p id="rfc.section.7.p.3">This
relationship between Metadata blocks is expressed by having the Subject
metadataIdRef refer to another Metadata, which denotes having it be input to
an operation.</p><hr class="noprint"><h1 id="rfc.section.8" class="np"><a
href="#rfc.section.8">8.</a> Base Schema</h1><p id="rfc.section.8.p.1">
<pre>
# ##############################################################
#
# File: nmbase.rnc - Main schema definition
@@ -818,8 +818,14 @@
element nmtm:end {
TimeContent
}
- </pre> </p><hr class="noprint"><h1 id="rfc.section.10"
class="np"><a href="#rfc.section.10">10.</a> Security Concerns</h1><p
id="rfc.section.10.p.1">There are important security concerns associated with
the generation and distribution of network measurement information. For
example, ISPs frequently consider network configuration and performance
information to be proprietary. Furthermore, observing traffic, and, in
particular, collecting packet headers, is frequently considered a violation
of the presumption of privacy on the network. Systems that collect the
measurements described here are sometimes regarded as invasive, and, indeed,
poorly designed or configured monitoring tools can consume a disproportionate
amount of network bandwidth. Port blocking, protocol blocking, and traffic
shaping can impact many measurement tools. Tools, such as traceroute, that
send UDP probes to increasing port numbers can appear to be port scans and
raise security alerts.</p><p id="r
fc.section.10.p.2">We do not address those concerns in this document, but
implementers are encouraged to consider the security implications of
generating and distributing measurement information. While distribution of
end-to-end application-level measurements is generally accepted, measurements
that identify individual users or consume noticeable amounts of resources
should be taken carefully, and the distribution of information to other sites
that cannot be obtained readily by other users at those sites should be
considered carefully.</p><hr class="noprint"><h1 id="rfc.authors"
class="np">Author's Address</h1><address class="vcard"><span
class="vcardline"><span class="fn">Martin Swany</span>
+ </pre> </p><hr class="noprint"><h1 id="rfc.section.10"
class="np"><a href="#rfc.section.10">10.</a> Security Concerns</h1><p
id="rfc.section.10.p.1">There are important security concerns associated with
the generation and distribution of network measurement information. For
example, ISPs frequently consider network configuration and performance
information to be proprietary. Furthermore, observing traffic, and, in
particular, collecting packet headers, is frequently considered a violation
of the presumption of privacy on the network. Systems that collect the
measurements described here are sometimes regarded as invasive, and, indeed,
poorly designed or configured monitoring tools can consume a disproportionate
amount of network bandwidth. Port blocking, protocol blocking, and traffic
shaping can impact many measurement tools. Tools, such as traceroute, that
send UDP probes to increasing port numbers can appear to be port scans and
raise security alerts.</p><p id="r
fc.section.10.p.2">We do not address those concerns in this document, but
implementers are encouraged to consider the security implications of
generating and distributing measurement information. While distribution of
end-to-end application-level measurements is generally accepted, measurements
that identify individual users or consume noticeable amounts of resources
should be taken carefully, and the distribution of information to other sites
that cannot be obtained readily by other users at those sites should be
considered carefully.</p><hr class="noprint"><h1 id="rfc.section.11"
class="np"><a href="#rfc.section.11">11.</a> Appendices</h1><h2
id="rfc.section.11.1"><a
href="#rfc.section.11.1">11.1</a> Acknowledgements</h2><h1 class="np"
id="rfc.references"><a href="#rfc.section.12">12.</a> References</h1><table
summary="References" border="0" cellpadding="2"><tr><td class="topnowrap"><b
id="tridentcom">[1]</b></td><td class="top">Zurawski, J., Swany, M., and D. Gu
nter, “A Scalable Framework for Representation and Exc!
hange of
+ Network Measurements”, In Proceedings of 2nd
International IEEE/Create-Net
+ Conference on Testbeds and Research Infrastructures for the
+ Development of Networks and Communities (Tridentcom
+ 2006).</td></tr></table><hr class="noprint"><h1 id="rfc.authors"
class="np">Author's Address</h1><address class="vcard"><span
class="vcardline"><span class="fn">D. Martin Swany</span>
(Editor)
- <span class="n hidden"><span class="family-name">Swany</span><span
class="given-name">Martin</span></span></span><span class="org vcardline">
+ <span class="n hidden"><span class="family-name">Swany</span><span
class="given-name">D. Martin</span></span></span><span class="org vcardline">
University of Delaware
+ Department of Computer and Information Sciences
+ Newark, DE 19716
</span></address><h1><a id="rfc.copyright" href="#rfc.copyright">Full
Copyright Statement</a></h1><p>Copyright � The Open Grid Forum (2007). All
Rights Reserved.</p><p>This document and translations of it may be copied and
furnished to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included on
all such copies and derivative works. However, this document itself may not
be modified in any way, such as by removing the copyright notice or
references to the OGF or other organizations, except as needed for the
purpose of developing Grid Recommendations in which case the procedures for
copyrights defined in the OGF Document process must be followed, or as
required to translate it into languages other than English.</p><p>The limited
permissions granted above
are perpetual and will not be revoked by the OGF or its successors or
assignees.</p><p>This document and the information contained herein is
provided on an “As Is” basis and the OGF disclaims all
warranties, express or implied, including but not limited to any warranty
that the use of the information herein will not infringe any rights or any
implied warranties of merchantability or fitness for a particular
purpose.</p><hr class="noprint"><h1 class="np"><a id="rfc.ipr"
href="#rfc.ipr">Intellectual Property</a></h1><p>The OGF takes no position
regarding the validity or scope of any intellectual property or other rights
that might be claimed to pertain to the implementation or use of the
technology described in this document or the extent to which any license
under such rights might or might not be available; neither does it represent
that it has made any effort to identify any such rights. Copies of claims of
rights made available for publication and any assurance
s of licenses to be made available, or the result of an atte!
mpt made
to obtain a general license or permission for the use of such proprietary
rights by implementers or users of this specification can be obtained from
the OGF Secretariat.</p><p>The OGF invites any interested party to bring to
its attention any copyrights, patents or patent applications, or other
proprietary rights, which may cover technology that may be required to
practice this recommendation. Please address the information to the OGF
Executive Director.</p></body></html>
\ No newline at end of file
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-05-02 18:25:36
UTC (rev 226)
+++ trunk/nmwg/doc/nm-schema-base/nm-schema-base.xml 2007-05-06 16:45:28
UTC (rev 227)
@@ -18,10 +18,12 @@
An Extensible Schema for Network Measurement and Performance Data
</title>
<author initials='M' surname='Swany'
- fullname='Martin Swany'
+ fullname='D. Martin Swany'
role='Editor'>
<organization abbrev='UDel'>
University of Delaware
+ Department of Computer and Information Sciences
+ Newark, DE 19716
</organization>
</author>
<date month="May" year="2007"/>
@@ -124,48 +126,93 @@
"EventType" -- The EventType identifies exactly what
sort
of measurement Event occurred.
</t>
- <t>"Parameters" -- The Parameters describe the details of
+ <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>
+ <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 (i.e. "characteristic") being sought.</t>
+ <t>The "Event Type" is the canonical name of the aspect of the
+ subject being measured, or the actual event
+ (i.e. "characteristic") being reported.</t>
</section>
<section id="parameters" title="Parameters">
- <t>The "Parameters" describe the exact
- way in which a particular measurement was gathered. </t>
+ <t>The "Parameters" describe the exact way in which a
+ particular measurement was gathered. These can include
+ parameters to active measurement tools. Essentially,
+ anything needed to determine which measurements are fungible
+ should be included here.</t>
</section>
</section>
<section id="data" title="Data">
- <t>The "Data" element refers to the "Metadata" that describes
- it. It contains some number of "Datum" elements, which hold
- the actual timestamp and value of the measurement or value
- of the event. </t>
+ <t>
+ The "Data" element has an Identifier and an Identifier
+ Reference that refers to the "Metadata" that describes it. It
+ contains some number of "Datum" elements.
+ </t>
+
+
+ <section id="datum" title="Datum">
+ <t>
+ The "Datum" elements hold the timestamp and value of
the
+ measurement or value of the event. For many network
+ measurement data sources, this can be a time-series of
+ timestamp, value pairs. For other measurement types,
the
+ result value may be a vector.
+ </t>
+ </section>
</section>
+
+ <section id="containers" title="Container Elements">
+ <t>
+ The above-named elements are currently contained in two types
+ of outer elements, "Message" and "Store". They have exactly
+ the same structure, i.e. containing "Metadata" and "Data"
+ elements. Each may have an attribute called "Type" to
+ indicate its type. Each may also contain one "Parameters"
+ element to indicate Message- or Store-level parameters and
+ options. This allows for a great deal of customization.
+ </t>
+ </section>
</section>
<section id="xml_namespace" title="XML Namespaces">
- <t>We have adopted XML namespaces to vary the schema of the
- basic elements for various different types of measurements. </t>
+ <t>
+ A key facet in this schema is the observation that the above
+ elements can be used to describe any network measurement, but
+ the exact content of the each will vary with the measurement
+ type. We have adopted XML namespaces to allow reuse of these
+ same basic element names, but to vary the contents of the basic
+ elements for each different type of data.
+ </t>
- <t>We envision there being two major classes of namespace URIs.
+ <t>
+ In this way, some superficial examination of the structure of a
+ message or information store can take place without looking at
+ the details of the contents. Some processing functionality
+ should be able to consume new data types with no modificiation.
+ </t>
+
+ <t>
+ We envision there being two major classes of namespace URIs.
The first is a canonical name based on the Hierarchy of Network
- Measurements (cite). The second is based on an organization's
- domain name and allows for autonomous extension.</t>
+ Measurements from this working group. (cite). The second is
+ based on an organization's domain name and allows for autonomous
+ extension in much the same way as the Enterprise branch of the
+ OID space (cite) allows.
+ </t>
</section>
@@ -185,29 +232,45 @@
<section id="metadata_chaining" title="Metadata Chaining">
<t>
- While a complete Metadata block can be used to describe,
- unambiguously, a data block, it is often desirable to
- combine multiple, partial Metadata blocks together. The
- main reason for this is reuse of information. Using the
- "metadataIdRef" attribute of a Metadata block allows us
- to form a "chain" of Metadata blocks.
+ While a complete Metadata block can be used to unambiguously
+ describe a data block, it is often desirable to combine
+ multiple, partial Metadata blocks together. The main reason for
+ this is reuse of information. Using the "metadataIdRef"
+ attribute of a Metadata block allows us to form a "chain" of
+ Metadata blocks. This means that not all Metadata blocks will
+ have an associated eventType. At the end of the chain, however,
+ there MUST be an event type.
</t>
</section>
<section id="operation_metadata" title="Operation Metadata">
<t>
- In addition to describing sets of raw data, Metadata blocks
- can also be used to describe transformations performed on a
- dataset. Thus, a list of Metadata blocks, including origin
- and transformations, can be used to describe, unambiguously,
- the provenance of any network data.
+ In addition to describing sets of raw data, Metadata blocks can
+ also be used to describe transformation operations performed on
+ a set of data. Thus, a list of Metadata blocks, including origin
+ and transformations, can be used to unambiguously describe the
+ provenance of any network data. This can also be used in cases
+ where the transformation is "internal" and the original data is
+ not available. This can be thought of as describing set
+ operations on the original set as it passes through a list of
+ operators.
+ <!-- give example of nfdump or rrdtool ? -->
</t>
<t>
- This relationship between Metadata blocks is expressed by
- having the Subject metadataIdRef refer to another Metadata,
- which denotes having it be input to an operation.
+ One example of this is the selection of a subset of data from a
+ a set, based on time or value. A "select" metadata block can be
+ used to describe this filtering operation independent of the
+ source. Formally, we can think of this as as an operation on
+ one set that produces another set. This metadata block must
+ unambiguously defining that set operation.
</t>
+
+ <t>
+ This relationship between Metadata blocks is expressed by having
+ the Subject metadataIdRef refer to another Metadata, which
+ denotes having it be input to an operation.
+ </t>
</section>
@@ -274,10 +337,44 @@
</section>
+
+ <section title="Appendices">
+ <section title="Acknowledgements">
+ We gratefully acknowledge the contributions of: Jeff Boote, Eric
+ Boyd, Dan Gunter, and Jason Zurawski and (who else??) the other
+ members of the Network Measurements Working Group.
+ </section>
+ </section>
-
</middle>
-<back></back>
+<back>
+ <references>
+ <reference anchor="tridentcom">
+ <front>
+ <title>A Scalable Framework for Representation and Exchange of
+ Network Measurements</title>
+ <author initials="J." surname="Zurawski" fullname="Jason
Zurawski">
+
<email></email>
+ </author>
+ <author initials="M." surname="Swany">
+ </author>
+ <author initials="D." surname="Gunter">
+ </author>
+ </front>
+ <seriesInfo>In Proceedings of 2nd International IEEE/Create-Net
+ Conference on Testbeds and Research Infrastructures for the
+ Development of Networks and Communities (Tridentcom
+ 2006)</seriesInfo>
+ <year>2006</year>
+ </reference>
+ <!--
+B. Lowekamp, B. Tierney, Les Cottrell, R. Hughes-Jones, T. Kielmann, M.
Swany, Enabling Network Measurement Portability Through a Hierarchy of
Characteristics, 4th International Workshop on Grid Computing (Grid2003),
November, 2003.
+
+-->
+
+ </references>
+</back>
+
</rfc>
Deleted: trunk/nmwg/doc/nm-schema-base/stuff.sh
- nmwg: r227 - trunk/nmwg/doc/nm-schema-base, svnlog, 05/06/2007
Archive powered by MHonArc 2.6.16.