- Nmc-wg - lists.ogf.org

Scope op NML
by Freek Dijkstra 21 Jan '10

21 Jan '10

Hi all, I'm cross-posting to NMC. Please reply to NML. The NML is currently defining a few subtopics for network description: domain/topology; adaptation/layer; and identifiers. What is not covered yet is the description of cross connects. My question to the group: to what extend do we want to define cross connect details in NML as well? If we're going to do that, we will bump into problems on labels (VLAN, timeslot, wavelength, ...), multi-cast, broadcast, backup/protected cross-connects, etc. I these details are required. Now we can either dive into this topic as well or leave it up to other standards. In particular, I was wondering if it would be useful to look at NETMOD [1], and have the following scopes: * NETMOD: focus on configuration in a device. * NML: focus on topology between devices and domains. * NM/NMC: focus on monitoring information. So link status, packet loss, bit error rate, etc. are in scope of NM; cross connects are in scope of NETMOD; link description is in scope of NML. The advantage of relying on other work is that we avoid duplicate work, and NML is more likely to be picked up elsewhere. The disadvantage is that it requires more work to cooperate. I suspect problems for topics which overlap. For example, identifiers in NETMOD and NML are different; path description (needed for NSI) relies on both link and cross connect descriptions; I have some doubt that adaptations and/or capabilities are clearly described in NETMOD, so we should either push that group or add that in NML after all. So what's your opinion? I like to speed up the NML, and wondered if we can gain speed by a bit more focus. Regards, Freek Dijkstra (with my co-chair hat off) [1] FYI: NETCONF is a replacement protocol for SNMP. While NETCONF describes the protocol, NETMOD describes the data model. NETMOD is still in development in the IETF.

1 0

[ogf nmc-base svn commit] r9 - /
by svn＠ogf.org 15 Jan '10

15 Jan '10

Author: zurawski Date: 2010-01-15 07:20:22 -0600 (Fri, 15 Jan 2010) New Revision: 9 Modified: extension.tex nmc-base.pdf Log: Fixing a 'bug' where the line was not being broken properly by tex. -jason Modified: extension.tex =================================================================== --- extension.tex 2010-01-13 15:26:40 UTC (rev 8) +++ extension.tex 2010-01-15 13:20:22 UTC (rev 9) @@ -462,7 +462,7 @@ \paragraph{eventType Extension} \label{s:echo_protocol_extension_eventtype} -The current accepted eventType for the \textit{Echo Protocol}'s \textbf{EchoRequest} message is \textbf{http://schemas.perfsonar.net/tools/admin/echo/2.0}. This \textit{action} \textbf{MUST} be accepted by all services. By adding additional eventTypes with the same format it is possible to extract additional information via a service. +The current accepted eventType for the \textit{Echo Protocol}'s \textbf{EchoRequest} message is \\ \textbf{http://schemas.perfsonar.net/tools/admin/echo/2.0}. This \textit{action} \textbf{MUST} be accepted by all services. By adding additional eventTypes with the same format it is possible to extract additional information via a service. Consider simple service X. The designer of this service wishes to create a special behaviour for specific eventTypes. The following new eventTypes are added to her service code (and to her implementation of the schema): Modified: nmc-base.pdf =================================================================== (Binary files differ)

1 0

Base doc
by Roman Lapacz 15 Jan '10

15 Jan '10

Hi, some first comments/observations: - I think the structure of namespace could be explained - example of status response in 4.1 does not explain too much (looks the same as earlier response example) - in 4.3.2.6 the concept of key could be explained more (for me the key represents some bigger information structure; reasons: performance, simplicity) - in 4.3.2.7 the reference to "Characteristic" document is missing - I'm wondering whether we can say in 4.3.3 that the request with more data triggers includes logical independent sub-requests - 4.4.1: typo "request schema" - I would remove parameter elements "supportedEventType" from all message examples. I understand that it's supported by the implementations but it's agreed to use eventType element - I think we have to rebuild Result Code section and finish the discussion on new ideas proposed by Slawek and Jeff. That's very important and must be done. Roman

6 15

Call tomorrow - 1/14 @ 16:00 UTC
by Jason Zurawski 14 Jan '10

14 Jan '10

All; A reminder that we will have a call tomorrow, agenda and coordinates are posted: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.nmc-wg/wiki/201001… Another reminder that if you have not done so, please: 1) review the current documents and have any comments or suggestions ready to discuss or mail before the meeting 2) review the result code document, it linked on the wiki page above Thanks; -jason

2 2

[Fwd: Re: [Fwd: Re: Call tomorrow - 1/14 @ 16:00 UTC]]
by Roman Lapacz 14 Jan '10

14 Jan '10

-------- Original Message -------- Subject: Re: [Fwd: Re: [Nmc-wg] Call tomorrow - 1/14 @ 16:00 UTC] Date: Thu, 14 Jan 2010 14:46:13 +0100 From: Szymon Trocha <szymon.trocha(a)man.poznan.pl> Organization: PCSS To: Roman Lapacz <romradz(a)man.poznan.pl> CC: GN3 SA2 Task3 <Gn3-sa2-t3(a)geant.net> References: <4B4F1EF5.4070905(a)man.poznan.pl> Hi Roman, Roman Lapacz pisze: > Hi, > > could someone check it (or forward to the right person)? > > thank, > Roman > > -------- Original Message -------- > Subject: Re: [Nmc-wg] Call tomorrow - 1/14 @ 16:00 UTC > Date: Thu, 14 Jan 2010 15:28:02 +0200 > From: Nina Jeliazkova <nina(a)acad.bg> > Reply-To: jeliazkova.nina(a)gmail.com > To: Roman Lapacz <romradz(a)man.poznan.pl> > References: <4B4DC397.6020508(a)internet2.edu> > <4B4EFAB9.40302(a)man.poznan.pl> > > > > Roman, > > Just to tell you the URL > https://wiki.man.poznan.pl/perfsonarmdm/index.php/Result_codes , cited > in the event types hierarchy document is not working. > > Strona nie została znaleziona > Strona o podanym adresie nie istnieje. Sprawdź poprawność adresu URL. Small difference :-) https://wiki.man.poznan.pl/perfsonar-mdm/index.php/Result_codes -- Szymon Trocha Poznan Supercomputing & Netw. Center ::: NETWORK OPERATION CENTER Tel. +48 618582022 ::: http://noc.man.poznan.pl

2 1

[Fwd: Re: Call tomorrow - 1/14 @ 16:00 UTC]
by Roman Lapacz 14 Jan '10

14 Jan '10

I'll forward this problem to Geant 3 SA2 T3 team. Thanks Nina. Roman -------- Original Message -------- Subject: Re: [Nmc-wg] Call tomorrow - 1/14 @ 16:00 UTC Date: Thu, 14 Jan 2010 15:28:02 +0200 From: Nina Jeliazkova <nina(a)acad.bg> Reply-To: jeliazkova.nina(a)gmail.com To: Roman Lapacz <romradz(a)man.poznan.pl> References: <4B4DC397.6020508(a)internet2.edu> <4B4EFAB9.40302(a)man.poznan.pl> Roman, Just to tell you the URL https://wiki.man.poznan.pl/perfsonarmdm/index.php/Result_codes , cited in the event types hierarchy document is not working. Strona nie została znaleziona Strona o podanym adresie nie istnieje. Sprawdź poprawność adresu URL. Best regards, Nina Roman Lapacz wrote: > Unfortunately, I will be able to participate the call only about 35 min > - 40 min so it would be great for me if we could start without delay. > > Roman > > Jason Zurawski wrote: > >> All; >> >> A reminder that we will have a call tomorrow, agenda and coordinates are >> posted: >> >> https://forge.gridforum.org/sf/wiki/do/viewPage/projects.nmc-wg/wiki/201001… >> >> Another reminder that if you have not done so, please: >> >> 1) review the current documents and have any comments or suggestions >> ready to discuss or mail before the meeting >> 2) review the result code document, it linked on the wiki page above >> >> Thanks; >> >> -jason >> _______________________________________________ >> Nmc-wg mailing list >> Nmc-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/nmc-wg >> >> > > _______________________________________________ > Nmc-wg mailing list > Nmc-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/nmc-wg >

1 0

[ogf nmc-base svn commit] r8 - /
by svn＠ogf.org 13 Jan '10

13 Jan '10

Author: zurawski Date: 2010-01-13 09:26:40 -0600 (Wed, 13 Jan 2010) New Revision: 8 Modified: chaining.tex nmc-base.pdf Log: Adding a comment to the chaining section - need to clarify why the example chains will or will not work. -jason Modified: chaining.tex =================================================================== --- chaining.tex 2010-01-13 12:37:45 UTC (rev 7) +++ chaining.tex 2010-01-13 15:26:40 UTC (rev 8) @@ -475,6 +475,15 @@ \end{verbatim} \normalsize + + +% XXX jz - 1/13/2010 +% +% This example needs to be ammended - some confusion regarding the use of +% multiple eventTypes and not enough explanation on why it may or may not work + + + Some services will still guess ``general'' and convert to the \textit{nmwg} namespace. The resulting data set will take on an interesting look: \tiny Modified: nmc-base.pdf =================================================================== (Binary files differ)

1 0

[ogf nmc-base svn commit] r7 - /
by svn＠ogf.org 13 Jan '10

13 Jan '10

Author: zurawski Date: 2010-01-13 06:37:45 -0600 (Wed, 13 Jan 2010) New Revision: 7 Modified: acknowledgements.tex chaining.tex conclusion.tex introduction.tex messages.tex motivation.tex nmc-base.bib nmc-base.pdf nmc-base.tex result_codes.tex Log: Summary of changes: - Update cp information/title page - Add a note regarding the status of namespace explanation - Add a note for someone to update a response message example - Add more clarification for the key element - Correct a reference to GFD.23 (char doc) - Typo in 4.4.1 - Remove supportedEventType examples from chaining section - Add a note regarding the enhancement of the result codes - misc. word changes (nothing structural) -jason Modified: acknowledgements.tex =================================================================== --- acknowledgements.tex 2010-01-12 13:16:39 UTC (rev 6) +++ acknowledgements.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -1,4 +1,4 @@ \section{Acknowledgements} \label{s:acknowledgements} -The authors gratefully acknowledge the contributions of the perfSONAR consortium to this work. Specifically staff and member institutions from ESnet, Geant, Internet2, and RNP have provided extensive input and feedback into the implementation of this and all NMC protocols. +The authors gratefully acknowledge the contributions of the perfSONAR consortium to this work. Specifically staff and member institutions from ESnet, Geant, Internet2, and RNP have provided extensive input and feedback into the implementation of this and all NMC-WG protocols. Modified: chaining.tex =================================================================== --- chaining.tex 2010-01-12 13:16:39 UTC (rev 6) +++ chaining.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -34,7 +34,7 @@ \item Elements sharing the same (or ``similar'') eventType \end{itemize} -When this first criteria is met, we \textbf{SHOULD} recurse downward and keep trying until we reach the bottom of the structure. How far should we venture into the XML structure looking for similarities or differences? This question does not have a definite answer such as \textit{stop at the grandchild of the current element}. While this \textbf{MAY} be frustrating, domain knowledge \textbf{MAY} help you make a passable decision especially with regards to topology based elements. +When this first criteria is met, we \textbf{SHOULD} traverse the chain \textit{downward}, recursively. A clear question to answer is ``How far should we venture into the XML structure looking for similarities or differences''? This question does not have a definite answer such as ``Stop at the grandchild of the current element''. While this \textbf{MAY} be frustrating, domain knowledge \textbf{MAY} help you make a passable decision especially with regards to topology based elements. \textit{Like} elements that do not share a common namespace \textbf{SHALL} require special rules that \textbf{MAY} differ from service to service. Depending on the level of protection or speed we wish to attain, these rules \textbf{MAY} vary. Service and protocol documentation \textbf{SHALL} fill in details beyond the scope of this work. @@ -67,10 +67,6 @@ </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> @@ -92,8 +88,16 @@ \end{verbatim} \normalsize -Note that the chaining is performed via the use of the \textit{metadataIdRef} tag in the metadata element. This is a signal for services (specifically the SNMP MA or RRD MA) to keep looking deeper in an effort to resolve the chains. The Figure~\ref{fig:chain} demonstrates the linking between the metadata elements. The resulting XML structure after chaining is also listed below. + +% XXX jz - 1/13/2010 +% +% Need references for the services. + + + +Note that the chaining is performed via the use of the \textit{metadataIdRef} tag in the metadata element. This is a signal for services (specifically perfSONAR services such as the SNMP MA or RRD MA) to keep looking deeper in an effort to resolve the chains. The Figure~\ref{fig:chain} demonstrates the linking between the metadata elements. The resulting XML structure after chaining is also listed below. + \begin{figure}[h!] \centering \includegraphics[width=1.5in]{chain.eps} @@ -116,10 +120,6 @@ </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> @@ -135,10 +135,6 @@ </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m3" metadataIdRef="m1"> @@ -154,10 +150,6 @@ </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -180,23 +172,14 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m3" metadataIdRef="m2"> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -226,9 +209,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> @@ -244,10 +224,6 @@ </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m3" metadataIdRef="m2"> @@ -264,11 +240,6 @@ <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -291,9 +262,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> @@ -325,9 +293,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="m1"> @@ -342,9 +307,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -366,9 +328,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -380,9 +339,6 @@ </nmwgt:interface> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -402,9 +358,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -423,9 +376,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -445,9 +395,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -462,9 +409,6 @@ </nmwgt:interface> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -486,9 +430,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -503,9 +444,6 @@ </nmwgt:interface> </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -523,9 +461,6 @@ </nmwgt:interface> </neterr:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -535,9 +470,6 @@ </nmwgt:interface> </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -555,9 +487,6 @@ </nmwgt:interface> </neterr:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2" metadataIdRef="1"> @@ -569,10 +498,6 @@ </nmwg:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> \end{verbatim} @@ -628,10 +553,6 @@ </netutil:subject> <nmwg:eventType>http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:eventType> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType> - <nmwg:parameters id="p1"> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/tools/snmp/2.0</nmwg:parameter> - <nmwg:parameter name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:parameter> - </nmwg:parameters> </nmwg:metadata> <nmwg:metadata xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/" id="m2"> Modified: conclusion.tex =================================================================== --- conclusion.tex 2010-01-12 13:16:39 UTC (rev 6) +++ conclusion.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -1,4 +1,8 @@ \section{Conclusion} \label{s:conclusion} +% XXX: jz - 1/13/2010 +% +% Conclusion is weak, this needs to be two paragraphs and sum up the work. + The preceding work has described a simple protocol that will form the basis of communication for software exchanging both network measurements and topological information. This protocol is both minimal and flexible --- extension to specific use cases is possible and expected. This work has been careful to retain the concepts described in other working groups including \textbf{NM-WG} and \textbf{NML-WG} in an effort to remain compatible with the primary data types. Modified: introduction.tex =================================================================== --- introduction.tex 2010-01-12 13:16:39 UTC (rev 6) +++ introduction.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -1,7 +1,7 @@ \section{Introduction} \label{s:introduction} -This document describes a \textit{protocol} designed to manage the interaction between systems focused on the \textit{collection}, \textit{storage}, and eventual \textit{exchange} of network performance information. This protocol becomes relevant in an incarnation of a performance measurement framework; said construct consists of a set of services, each acting as an intermediate layer, between the performance measurement tools and the diagnostic or visualization applications all within a federated environment. The proposed architecture \textbf{SHOULD} make this functionality available via \textit{Web Services} (WS) and to use a service-oriented design style, implying that a set of elementary functions has been isolated and can be delivered by potentially different software entities. In this model, all services \textbf{MUST} communicate using well-defined protocols. +This document describes a \textit{protocol} designed to manage the interaction between systems focused on the \textit{collection}, \textit{storage}, and eventual \textit{exchange} of network performance information. This protocol becomes relevant in an incarnation of a performance measurement framework; consisting of a set of services, each acting as an intermediate layer, between the performance measurement tools and the diagnostic or visualization applications all within a federated environment. The proposed architecture \textbf{SHOULD} make this functionality available via \textit{Web Services} (WS) and to use a service-oriented design style, implying that a set of elementary functions has been isolated and can be delivered by potentially different software entities. In this model, all services \textbf{MUST} communicate using well-defined protocols. The work presented here builds upon the output of other working groups focused on the accurate description of network measurements \cite{nmwg} and topological representation of network elements \cite{nmlwg}. When applicable, we will directly cite terminology and ideas from these working groups. We do not describe a particular system currently in use, although several prototypes exist that implement messaging similar to this work. Modified: messages.tex =================================================================== --- messages.tex 2010-01-12 13:16:39 UTC (rev 6) +++ messages.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -3,6 +3,26 @@ As described in Section~\ref{s:motivation}, the communication protocol is simple and based on the notion of \textit{Request} and \textit{Response} messages. The construction of the \textit{message} itself takes advantage of work produced in the \textbf{NM-WG} by re-using several key constructs. Both message types are fundamentally the same: a series of \textit{metadata} and \textit{data} units linked via identifying attributes (e.g. \textit{id} and \textit{idRef} attribute values). These concepts, shown in \cite{nmwg-base,zurawski06scalable}, observe the same rules with regards to splitting both measurement and communication. + + +% XXX jz - 1/13/2010 +% +% A comment from Roman: "I think the structure of namespace could be explained" +% +% The original thinking was the NM-WG document, "An Extensible Schema for +% Network Measurement and Performance Data", would contain the entire +% explanation of namespaces (the idea itself coming from another OGF WG). +% +% Any future documents from related projects (NMC, NML, others?) would reference +% this and only note caveats to the original rule. The NM-WG doc is here: +% +% https://forge.gridforum.org/sf/go/doc15649?nav=1 +% +% Namespaces are in section 4. Regardless, we need to discuss this and provide +% the reference somewhere before we discuss the message structure. + + + \subsection{Preliminary Example} \label{s:preliminary_example} @@ -77,6 +97,17 @@ The general format of a status message is as follows, parallels between the previous response as well as the request can easily be drawn. + + +% XXX jz - 1/13/2010 +% +% Comment from Roman: "example of status response in 4.1 does not explain too +% much (looks the same as earlier response example)" +% +% This example should be clarified to make it different from the previous. + + + \tiny \begin{verbatim} <message type="response"> @@ -357,6 +388,20 @@ \paragraph{Key} \label{s:request_message_analysis_key} +example of status response in 4.1 does not explain too much (looks the +> same as earlier response example) + +% XXX jz - 1/13/2010 +% +% Comment from Roman: "the concept of key could be explained more (for me +% the key represents some bigger information structure; reasons: performance, +% simplicity)" +% +% I have added a comparison to a hash function (pretty much the reason for the +% key if my memory of 5 years ago is correct) but can use more work. + + + \tiny \begin{verbatim} @@ -385,6 +430,8 @@ \end{table} \label{t:request_key} +The key element is rooted in the concept of a \textit{hash function} --- a function or process designed to convert a variable amount of information into a single value or \textit{index}. Once converted this single value can then be used a shorthanded notation to reference the original entity, imparting a performance increase for computational tasks. + The key structure \textbf{SHALL} used to convey sensitive or private information to and from the service. For this reason the contents of the key \textbf{SHOULD} be viewed as ``opaque'', and \textbf{MUST NOT} be dissected. The key \textbf{SHOULD} contain a \textit{Parameters} (see Section~\ref{s:request_message_analysis_parameters}) element. There is only one attributes possible: \textit{id}. This \textbf{MAY} used to track state. A detailed description follows: \begin{itemize} @@ -418,7 +465,7 @@ \end{table} \label{t:request_eventtype} -The eventType element \textbf{SHOULD} used to describe a measurement's specific data type (e.g. closely matching the definitions from the \textbf{NM-WG}'s ``Characteristic'' document) or \textbf{MAY} be used to trigger an internal event within the service. This element contains no attributes, and \textbf{MUST} only contain text, normally in the form of a \textit{URI}. There \textbf{MAY} be \textit{many} eventType elements in a single metadata. +The eventType element \textbf{SHOULD} used to describe a measurement's specific data type (e.g. closely matching the definitions described in \cite{chardoc} and \cite{chargrid03}) or \textbf{MAY} be used to trigger an internal event within the service. This element contains no attributes, and \textbf{MUST} only contain text, normally in the form of a \textit{URI}. There \textbf{MAY} be \textit{many} eventType elements in a single metadata. \paragraph{Data} \label{s:request_message_analysis_data} @@ -515,7 +562,7 @@ \subsection{Response Message} \label{s:response_message} -The response message is a container filled with the results of a \textit{Request Message} from a capable service. Enclosed in this simple envelope \textbf{SHALL} be a series of metadata and data pairs containing the results of actions performed by a service. We first present a very simple schema in Section~\ref{s:response_message_schema} along with an analysis of the elements in Section~\ref{s:response_message_analysis}. We conclude with examples in Section~\ref{s:response_message_example}. +The response message is a container filled with the results of a \textit{Response Message} from a capable service. Enclosed in this simple envelope \textbf{SHALL} be a series of metadata and data pairs containing the results of actions performed by a service. We first present a very simple schema in Section~\ref{s:response_message_schema} along with an analysis of the elements in Section~\ref{s:response_message_analysis}. We conclude with examples in Section~\ref{s:response_message_example}. \subsubsection{Response Message Schema} \label{s:response_message_schema} Modified: motivation.tex =================================================================== --- motivation.tex 2010-01-12 13:16:39 UTC (rev 6) +++ motivation.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -1,7 +1,7 @@ \section{Motivation} \label{s:motivation} -A common message exchange pattern for web services in general is a \textit{Request} followed by a \textit{Response}. This particular communication pattern is important and involves two actors for the general case. Consider the example in Figure~\ref{fig:exchange} of a \textit{client} application interacting with some \textit{measurement service} in search of data. This exchange assumes that both the client and the service speak a common dialect of communication protocol. +A common message exchange pattern for Web Services (WS) is a \textit{Request} followed by a \textit{Response}. This particular communication pattern is important and involves two actors for the general case. Consider the example in Figure~\ref{fig:exchange} of a \textit{client} application interacting with some service, in this case a \textit{measurement service}. This exchange assumes that both the client and the service speak a common dialect of some communication protocol. \begin{figure}[h!] \centering @@ -19,7 +19,7 @@ \label{fig:exchange2} \end{figure} -A less common interaction is the notion of a \textit{Subscription}, \textit{Notification} or other form of ``one-sided'' exchange. Services may use this to perform tasks such as subscribing to status updates from a service, or otherwise alerting a service or client about the existence of some key piece of information. Figure~\ref{fig:exchange3} describes this exchange in detail. +Another interaction is the notion of a \textit{Subscription}, \textit{Notification} or other form of ``one-sided'' exchange. Services may use this to perform tasks such as subscribing to status updates from a service, or otherwise alerting a service or client about the existence of some key piece of information. Figure~\ref{fig:exchange3} describes this exchange in detail. \begin{figure}[h!] \centering Modified: nmc-base.bib =================================================================== --- nmc-base.bib 2010-01-12 13:16:39 UTC (rev 6) +++ nmc-base.bib 2010-01-13 12:37:45 UTC (rev 7) @@ -80,3 +80,19 @@ howpublished = "\url{https://wiki.man.poznan.pl/perfsonar-mdm/index.php/Result_codes}" } +@TechReport{chardoc, + Title = "{A Hierarchy of Network Performance Characteristics for Grid Applications and Services}", + Author = "B. Lowekamp and B. Tierney and L. Cottrell and R. Hughes-Jones and T. Kielmann and M. Swany", + institution = "Global Grid Forum", + year = "2003", howpublished = {GWD-C}, + type = "Community Practice", + month = "June" +} + +@inproceedings{chargrid03, + Title = "{Enabling Network Measurement Portability Through a Hierarchy of Characteristics}", + Author = "B. Lowekamp and B. Tierney and L. Cottrell and R. Hughes-Jones and T. Kielmann and M. Swany", + booktitle = {4th International Workshop on Grid Computing (Grid2003)}, + year = "2003" +} + Modified: nmc-base.pdf =================================================================== (Binary files differ) Modified: nmc-base.tex =================================================================== --- nmc-base.tex 2010-01-12 13:16:39 UTC (rev 6) +++ nmc-base.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -68,7 +68,7 @@ \begin{minipage}[t]{2.5in} \raggedleft Jason Zurawski, Internet2\\ -Martin Swany, UDel\\ +Martin Swany, University of Delaware\\ \today \end{minipage} } @@ -83,7 +83,7 @@ {\noindent\bf Copyright Notice} \\ -{\noindent Copyright \copyright \ Open Grid Forum (2008-2009). All Rights Reserved.} +{\noindent Copyright \copyright \ Open Grid Forum (2008-2010). All Rights Reserved.} \section{Abstract} @@ -151,7 +151,7 @@ \section{Full Copyright Notice} -Copyright \copyright \ Open Grid Forum (2008-2009). All Rights Reserved. \\ +Copyright \copyright \ Open Grid Forum (2008-2010). All Rights Reserved. \\ {\noindent 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.} \\ Modified: result_codes.tex =================================================================== --- result_codes.tex 2010-01-12 13:16:39 UTC (rev 6) +++ result_codes.tex 2010-01-13 12:37:45 UTC (rev 7) @@ -1,8 +1,18 @@ \section{Result Codes} \label{s:result_codes} -There are currently two hierarchical systems that \textbf{MAY} be used to return status information about services. Each of these approaches takes into account the facts that there are many diverse services as well as different status messages that \textbf{MAY} be returned. The later system also allows for versioning and backwards compatibility that the original attempt did not consider. Either system will accomplish the goal of providing a scalable and readable result code tree. It is recommended that the latter approach be adopted as it contains superior features. + +% XXX jz - 1/13/2010 +% +% Comment from Roman: "I think we have to rebuild Result Code section and finish +% the discussion on new ideas proposed by Slawek and Jeff. That's very important +% and must be done." + + + +There are currently two hierarchical systems that \textbf{MAY} be used to return status information about services. Each of these approaches takes into account the facts that there are many diverse services as well as different status messages that \textbf{MAY} be returned. The later system also allows for version control and backwards compatibility that the original attempt did not consider. Either system will accomplish the goal of providing a scalable and readable result code tree. It is recommended that the latter approach be adopted as it contains superior features. + The original idea for result codes comes from the perfSONAR\cite{perfsonar} framework and is explained in \cite{psresult}. This approach relies on a static tree of status information that is branched first by general features (i.e. success, error) and later by more specific characteristics such as service and error type. This hierarchy is missing the ability to offer versions of different codes that could become forward or backwards compatible (seen now in the \textit{eventType} system that takes the form of \textit{URI} strings). \begin{tabular}{lll}

1 0

NMC-Base document on Gridforge
by Jason Zurawski 12 Jan '10

12 Jan '10

All; The NMC-Base document is now on the gridforge svn: https://forge.gridforum.org/sf/scm/do/listRepositories/projects.nmc-wg/scm I am still waiting for the other document repos to be created. I do not think there is a way to get notifications sent to our mailing list by default (everyone may set up their own monitoring via the web site) but I have an email out to the admin just to check. -jason

1 1

[ogf nmc-is svn commit] r1 - / util
by svn＠ogf.org 12 Jan '10

12 Jan '10

Author: zurawski Date: 2010-01-12 07:45:15 -0600 (Tue, 12 Jan 2010) New Revision: 1 Added: Makefile citesort.sty deregister.tex discovery.tex examples/ fancyheadings.sty introduction.tex keepalive.tex key.tex nmc-is.bib nmc-is.pdf nmc-is.tex query.tex register.tex resultcodes.tex schema/ util/ util/inline.pl Log: First commit of NMC IS document. -jason Added: Makefile =================================================================== --- Makefile (rev 0) +++ Makefile 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,26 @@ +NAME=nmc-is + +GRAPHS=$(wildcard *.eps) +FILES=$(wildcard *.tex) +REFS=$(wildcard *.bib) + +all: ${NAME}.pdf + +${NAME}.pdf: ${NAME}.tex ${GRAPHS} ${FILES} ${REFS} + latex ${NAME} + bibtex ${NAME} + latex ${NAME} + latex ${NAME} + dvips ${NAME}.dvi -o ${NAME}.ps + ps2pdf ${NAME}.ps ${NAME}.pdf + +${NAME}.ps: + latex ${NAME}.tex + bibtex ${NAME} + dvips ${NAME}.dvi -o ${NAME}.ps +# ps2pdf ${NAME}.ps + +.PHONY: ${NAME}.ps +clean: + rm -f ${NAME}.ps ${NAME}.dvi *.bbl *.aux \ + *.log *.blg *.ascii *.out *.toc Property changes on: Makefile ___________________________________________________________________ Name: svn:mime-type + text/plain Name: svn:keywords + "Author Date Id Rev URL" Name: svn:eol-style + native Added: citesort.sty =================================================================== --- citesort.sty (rev 0) +++ citesort.sty 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,56 @@ +%NAME: citesort.sty +% A replacement for \@citex which sorts citation numbers as well as +% compressing and allowing breaks. Based on cite.sty by Donald +% Arseneau. +% +% for use in LaTeX say, \documentstyle[...,citesort,...]{...} +% +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% +% Allow, but strongly discourage, line breaks within a long +% series of citations. Compress lists of successive numbers +% to one number range, e.g., 5,6,7,8,9 --> 5--9. Compatible +% with versions of \@cite that use exponents. +% -- Donald Arseneau 1989 +% +% Modified to sort the numbers so they come out in increasing order, +% regardless of the way they appear in the source. O(N^2) sort! +% Ian Green, CUED, 10-Dec-1991. Improvements to img(a)eng.cam.ac.uk +% please. Version 1 + +\newcount\@minsofar +\newcount\@min +\newcount\@cite@temp +\def\@citex[#1]#2{% +\if@filesw \immediate \write \@auxout {\string \citation {#2}}\fi +\@tempcntb\m@ne \let\@h@ld\relax \def\@citea{}% +\@min\m@ne% +\@cite{% + \@for \@citeb:=#2\do {\@ifundefined {b@\@citeb}% + {\@h@ld\@citea\@tempcntb\m@ne{\bf ?}% + \@warning {Citation `\@citeb ' on page \thepage \space undefined}}% +{\@minsofar\z@ \@for \@scan@cites:=#2\do {% + \@ifundefined{b@\@scan@cites}% + {\@cite@temp\m@ne} + {\@cite@temp\number\csname b@\@scan@cites \endcsname \relax}% +\ifnum\@cite@temp > \@min% select the next one to list + \ifnum\@minsofar = \z@ + \@minsofar\number\@cite@temp + \edef\@scan@copy{\@scan@cites}\else + \ifnum\@cite@temp < \@minsofar + \@minsofar\number\@cite@temp + \edef\@scan@copy{\@scan@cites}\fi\fi\fi}\@tempcnta\@min + \ifnum\@minsofar > \z@ % some more + \advance\@tempcnta\@ne + \@min\@minsofar + \ifnum\@tempcnta=\@minsofar % Number follows previous--hold on to it + \ifx\@h@ld\relax + \edef \@h@ld{\@citea\csname b@\@scan@copy\endcsname}% + \else \edef\@h@ld{\ifmmode{-}\else--\fi\csname b@\@scan@copy\endcsname}% + \fi + \else \@h@ld\@citea\csname b@\@scan@copy\endcsname + \let\@h@ld\relax + \fi % no more +\fi}% +\def\@citea{,\penalty\@highpenalty\,}}\@h@ld}{#1}} + +% end of citesort.sty Added: deregister.tex =================================================================== --- deregister.tex (rev 0) +++ deregister.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Deregister} +\label{s:deregister} + +\subsection{DeregisterRequest Message} +\label{s:deregister_request} + +\subsubsection{DeregisterRequest Message Schema} +\label{s:deregister_request_schema} + +\subsubsection{DeregisterRequest Message Analysis} +\label{s:deregister_request_analysis} + +\paragraph{Message} +\label{s:deregister_request_analysis_message} + +\paragraph{Parameters} +\label{s:deregister_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:deregister_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:deregister_request_analysis_metadata} + +\paragraph{Data} +\label{s:deregister_request_analysis_data} + +\subsubsection{DeregisterRequest Message Example} +\label{s:deregister_request_example} + +\subsection{DeregisterResponse Message} +\label{s:deregister_response} + +\subsubsection{DeregisterResponse Message Schema} +\label{s:deregister_response_schema} + +\subsubsection{DeregisterResponse Message Analysis} +\label{s:deregister_response_analysis} + +\paragraph{Message} +\label{s:deregister_response_analysis_message} + +\paragraph{Parameters} +\label{s:deregister_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:deregister_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:deregister_response_analysis_metadata} + +\paragraph{Data} +\label{s:deregister_response_analysis_data} + +\paragraph{Key} +\label{s:deregister_response_analysis_key} + +\paragraph{Datum} +\label{s:deregister_response_analysis_datum} + +\subsubsection{DeregisterResponse Message Example} +\label{s:deregister_response_example} Added: discovery.tex =================================================================== --- discovery.tex (rev 0) +++ discovery.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Discovery} +\label{s:discovery} + +\subsection{DiscoveryRequest Message} +\label{s:discovery_request} + +\subsubsection{DiscoveryRequest Message Schema} +\label{s:discovery_request_schema} + +\subsubsection{DiscoveryRequest Message Analysis} +\label{s:discovery_request_analysis} + +\paragraph{Message} +\label{s:discovery_request_analysis_message} + +\paragraph{Parameters} +\label{s:discovery_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:discovery_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:discovery_request_analysis_metadata} + +\paragraph{Data} +\label{s:discovery_request_analysis_data} + +\subsubsection{DiscoveryRequest Message Example} +\label{s:discovery_request_example} + +\subsection{DiscoveryResponse Message} +\label{s:discovery_response} + +\subsubsection{DiscoveryResponse Message Schema} +\label{s:discovery_response_schema} + +\subsubsection{DiscoveryResponse Message Analysis} +\label{s:discovery_response_analysis} + +\paragraph{Message} +\label{s:discovery_response_analysis_message} + +\paragraph{Parameters} +\label{s:discovery_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:discovery_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:discovery_response_analysis_metadata} + +\paragraph{Data} +\label{s:discovery_response_analysis_data} + +\paragraph{Key} +\label{s:discovery_response_analysis_key} + +\paragraph{Datum} +\label{s:discovery_response_analysis_datum} + +\subsubsection{DiscoveryResponse Message Example} +\label{s:discovery_response_example} Added: fancyheadings.sty =================================================================== --- fancyheadings.sty (rev 0) +++ fancyheadings.sty 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,205 @@ +% fancyheadings.sty version 1.98 +% Fancy headers and footers. +% Piet van Oostrum, Dept of Computer Science, University of Utrecht +% Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands +% Telephone: +31 30 2531806. Email: piet(a)cs.ruu.nl +% Sep 16, 1994 +% version 1.4: Correction for use with \reversemargin +% Sep 29, 1994: +% version 1.5: Added the \iftopfloat, \ifbotfloat and \iffloatpage commands +% Oct 4, 1994: +% version 1.6: Reset single spacing in headers/footers for use with +% setspace.sty or doublespace.sty +% Oct 4, 1994: +% version 1.7: changed \let\@mkboth\markboth to +% \def\@mkboth{\protect\markboth} to make it more robust +% Dec 5, 1994: +% version 1.8: corrections for amsbook/amsart: define \@chapapp and (more +% importantly) use the \chapter/sectionmark definitions from ps@headings if +% they exist (which should be true for all standard classes). +% May 31, 1995: +% version 1.9: The proposed \renewcommand{\headrulewidth}{\iffloatpage... +% construction in the doc did not work properly with the fancyplain style. +% June 1, 1995: +% version 1.91: The definition of \@mkboth wasn't restored on subsequent +% \pagestyle{fancy}'s. +% June 1, 1995: +% version 1.92: The sequence \pagestyle{fancyplain} \pagestyle{plain} +% \pagestyle{fancy} would erroneously select the plain version. +% June 1, 1995: +% version 1.93: \fancypagestyle command added. +% Dec 11, 1995: +% version 1.94: suggested by Conrad Hughes <chughes(a)maths.tcd.ie> +% CJCH, Dec 11, 1995: added \footruleskip to allow control over footrule +% position (old hardcoded value of .3\normalbaselineskip is far too high +% when used with very small footer fonts). +% Jan 31, 1996: +% version 1.95: call \@normalsize in the reset code if that is defined, +% otherwise \normalsize. +% this is to solve a problem with ucthesis.cls, as this doesn't +% define \@currsize. Unfortunately for latex209 calling \normalsize doesn't +% work as this is optimized to do very little, so there \@normalsize should +% be called. Hopefully this code works for all versions of LaTeX known to +% mankind. +% April 25, 1996: +% version 1.96: initialize \headwidth to a magic (negative) value to catch +% most common cases that people change it before calling \pagestyle{fancy}. +% Note it can't be initialized when reading in this file, because +% \textwidth could be changed afterwards. This is quite probable. +% We also switch to \MakeUppercase rather than \uppercase and introduce a +% \nouppercase command for use in headers. and footers. +% May 3, 1996: +% version 1.97: Two changes: +% 1. Undo the change in version 1.8 (using the pagestyle{headings} defaults +% for the chapter and section marks. The current version of amsbook and +% amsart classes don't seem to need them anymore. Moreover the standard +% latex classes don't use \markboth if twoside isn't selected, and this is +% confusing as \leftmark doesn't work as expected. +% 2. include a call to \ps@empty in ps@@fancy. This is to solve a problem +% in the amsbook and amsart classes, that make global changes to \topskip, +% which are reset in \ps@empty. Hopefully this doesn't break other things. +% May 7, 1996: +% version 1.98: +% Added % after the line \def\nouppercase +% BY THE WAY, THIS IS THE LAST RELEASE OF VERSION 1. + +\let\fancy@def\gdef +\def\lhead{\@ifnextchar[{\@xlhead}{\@ylhead}} +\def\@xlhead[#1]#2{\fancy@def\@elhead{#1}\fancy@def\@olhead{#2}} +\def\@ylhead#1{\fancy@def\@elhead{#1}\fancy@def\@olhead{#1}} + +\def\chead{\@ifnextchar[{\@xchead}{\@ychead}} +\def\@xchead[#1]#2{\fancy@def\@echead{#1}\fancy@def\@ochead{#2}} +\def\@ychead#1{\fancy@def\@echead{#1}\fancy@def\@ochead{#1}} + +\def\rhead{\@ifnextchar[{\@xrhead}{\@yrhead}} +\def\@xrhead[#1]#2{\fancy@def\@erhead{#1}\fancy@def\@orhead{#2}} +\def\@yrhead#1{\fancy@def\@erhead{#1}\fancy@def\@orhead{#1}} + +\def\lfoot{\@ifnextchar[{\@xlfoot}{\@ylfoot}} +\def\@xlfoot[#1]#2{\fancy@def\@elfoot{#1}\fancy@def\@olfoot{#2}} +\def\@ylfoot#1{\fancy@def\@elfoot{#1}\fancy@def\@olfoot{#1}} + +\def\cfoot{\@ifnextchar[{\@xcfoot}{\@ycfoot}} +\def\@xcfoot[#1]#2{\fancy@def\@ecfoot{#1}\fancy@def\@ocfoot{#2}} +\def\@ycfoot#1{\fancy@def\@ecfoot{#1}\fancy@def\@ocfoot{#1}} + +\def\rfoot{\@ifnextchar[{\@xrfoot}{\@yrfoot}} +\def\@xrfoot[#1]#2{\fancy@def\@erfoot{#1}\fancy@def\@orfoot{#2}} +\def\@yrfoot#1{\fancy@def\@erfoot{#1}\fancy@def\@orfoot{#1}} + +\newdimen\headrulewidth +\newdimen\footrulewidth +\newdimen\plainheadrulewidth +\newdimen\plainfootrulewidth +\newdimen\headwidth +\newdimen\footruleskip +\newif\if@fancyplain \@fancyplainfalse +\def\fancyplain#1#2{\if@fancyplain#1\else#2\fi} +\headwidth=-123456789sp %magic constant + +% Command to reset various things in the headers: +% a.o. single spacing (taken from setspace.sty) +% and the catcode of ^^M (so that epsf files in the header work if a +% verbatim crosses a page boundary) +% It also defines a \nouppercase command that disables \uppercase and +% \Makeuppercase. It can only be used in the headers and footers. +\def\fancy@reset{\restorecr + \def\baselinestretch{1}% + \def\nouppercase##1{{\let\uppercase\relax\let\MakeUppercase\relax##1}}% + \ifx\undefined\@newbaseline% NFSS not present; 2.09 or 2e + \ifx\@normalsize\undefined \normalsize % for ucthesis.cls + \else \@normalsize \fi + \else% NFSS (2.09) present + \@newbaseline% + \fi} + +% Initialization of the head and foot text. + +\headrulewidth 0.4pt +\footrulewidth\z@ +\plainheadrulewidth\z@ +\plainfootrulewidth\z@ +\footruleskip .3\normalbaselineskip + +\lhead[\fancyplain{}{\sl\rightmark}]{\fancyplain{}{\sl\leftmark}} +% i.e. empty on ``plain'' pages, \rightmark on even, \leftmark on odd pages +\chead{} +\rhead[\fancyplain{}{\sl\leftmark}]{\fancyplain{}{\sl\rightmark}} +% i.e. empty on ``plain'' pages, \leftmark on even, \rightmark on odd pages +\lfoot{} +\cfoot{\rm\thepage} % page number +\rfoot{} + +% Put together a header or footer given the left, center and +% right text, fillers at left and right and a rule. +% The \lap commands put the text into an hbox of zero size, +% so overlapping text does not generate an errormessage. + +\def\@fancyhead#1#2#3#4#5{#1\hbox to\headwidth{\fancy@reset\vbox{\hbox +{\rlap{\parbox[b]{\headwidth}{\raggedright#2\strut}}\hfill +\parbox[b]{\headwidth}{\centering#3\strut}\hfill +\llap{\parbox[b]{\headwidth}{\raggedleft#4\strut}}}\headrule}}#5} + +\def\@fancyfoot#1#2#3#4#5{#1\hbox to\headwidth{\fancy@reset\vbox{\footrule +\hbox{\rlap{\parbox[t]{\headwidth}{\raggedright#2\strut}}\hfill +\parbox[t]{\headwidth}{\centering#3\strut}\hfill +\llap{\parbox[t]{\headwidth}{\raggedleft#4\strut}}}}}#5} + +\def\headrule{{\if@fancyplain\let\headrulewidth\plainheadrulewidth\fi +\hrule\@height\headrulewidth\@width\headwidth \vskip-\headrulewidth}} + +\def\footrule{{\if@fancyplain\let\footrulewidth\plainfootrulewidth\fi +\vskip-\footruleskip\vskip-\footrulewidth +\hrule\@width\headwidth\@height\footrulewidth\vskip\footruleskip}} + +\def\ps@fancy{% +\@ifundefined{@chapapp}{\let\@chapapp\chaptername}{}%for amsbook +% Define \MakeUppercase for old LaTeXen. +% Note: we used \def rather than \let, so that \let\uppercase\relax (from +% the original documentation) will still work. +\@ifundefined{MakeUppercase}{\def\MakeUppercase{\uppercase}}{} +\@ifundefined{chapter}{\def\sectionmark##1{\markboth +{\MakeUppercase{\ifnum \c@secnumdepth>\z@ + \thesection\hskip 1em\relax \fi ##1}}{}}% +\def\subsectionmark##1{\markright {\ifnum \c@secnumdepth >\@ne + \thesubsection\hskip 1em\relax \fi ##1}}}% +{\def\chaptermark##1{\markboth {\MakeUppercase{\ifnum \c@secnumdepth>\m@ne + \@chapapp\ \thechapter. \ \fi ##1}}{}} +\def\sectionmark##1{\markright{\MakeUppercase{\ifnum \c@secnumdepth >\z@ + \thesection. \ \fi ##1}}}}% +%\csname ps@headings\endcsname % use \ps@headings defaults if they exist +\ps@@fancy +\gdef\ps@fancy{\@fancyplainfalse\ps@@fancy}% +% Initialize \headwidth if the user didn't +\ifdim\headwidth<0sp +% This catches the case that \headwidth hasn't been initialized and the +% case that the user added something to \headwidth in the expectation that +% it was initialized to \textwidth. We compensate this now. This loses if +% the user intended to multiply it by a factor. But that case is more +% likely done by saying something like \headwidth=1.2\textwidth The doc +% says you have to change \headwidth after the first call to, +% \pagestyle{fancy}. This code is just to catch the most common cases were +% that requirement is violated. + \advance\headwidth123456789sp\advance\headwidth\textwidth\fi} +\def\ps@fancyplain{\ps@fancy \let\ps@plain\ps@plain@fancy} +\def\ps@plain@fancy{\@fancyplaintrue\ps@@fancy} +\def\ps@@fancy{% +\ps@empty % This is for amsbook/amsart, which do strange things with \topskip +\def\@mkboth{\protect\markboth}% +\def\@oddhead{\@fancyhead\@lodd\@olhead\@ochead\@orhead\@rodd}% +\def\@oddfoot{\@fancyfoot\@lodd\@olfoot\@ocfoot\@orfoot\@rodd}% +\def\@evenhead{\@fancyhead\@rodd\@elhead\@echead\@erhead\@lodd}% +\def\@evenfoot{\@fancyfoot\@rodd\@elfoot\@ecfoot\@erfoot\@lodd}% +} +\def\@lodd{\if@reversemargin\hss\else\relax\fi} +\def\@rodd{\if@reversemargin\relax\else\hss\fi} + +\let\latex@makecol\@makecol +\def\@makecol{\let\topfloat\@toplist\let\botfloat\@botlist\latex@makecol} +\def\iftopfloat#1#2{\ifx\topfloat\empty #2\else #1\fi} +\def\ifbotfloat#1#2{\ifx\botfloat\empty #2\else #1\fi} +\def\iffloatpage#1#2{\if@fcolmade #1\else #2\fi} + +\newcommand{\fancypagestyle}[2]{% + \@namedef{ps@#1}{\let\fancy@def\def#2\relax\ps@fancy}} Added: introduction.tex =================================================================== --- introduction.tex (rev 0) +++ introduction.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,4 @@ +\section{Introduction} +\label{s:introduction} + +TBD Added: keepalive.tex =================================================================== --- keepalive.tex (rev 0) +++ keepalive.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Keepalive} +\label{s:keepalive} + +\subsection{KeepaliveRequest Message} +\label{s:keepalive_request} + +\subsubsection{KeepaliveRequest Message Schema} +\label{s:keepalive_request_schema} + +\subsubsection{KeepaliveRequest Message Analysis} +\label{s:keepalive_request_analysis} + +\paragraph{Message} +\label{s:keepalive_request_analysis_message} + +\paragraph{Parameters} +\label{s:keepalive_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:keepalive_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:keepalive_request_analysis_metadata} + +\paragraph{Data} +\label{s:keepalive_request_analysis_data} + +\subsubsection{KeepaliveRequest Message Example} +\label{s:keepalive_request_example} + +\subsection{KeepaliveResponse Message} +\label{s:keepalive_response} + +\subsubsection{KeepaliveResponse Message Schema} +\label{s:keepalive_response_schema} + +\subsubsection{KeepaliveResponse Message Analysis} +\label{s:keepalive_response_analysis} + +\paragraph{Message} +\label{s:keepalive_response_analysis_message} + +\paragraph{Parameters} +\label{s:keepalive_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:keepalive_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:keepalive_response_analysis_metadata} + +\paragraph{Data} +\label{s:keepalive_response_analysis_data} + +\paragraph{Key} +\label{s:keepalive_response_analysis_key} + +\paragraph{Datum} +\label{s:keepalive_response_analysis_datum} + +\subsubsection{KeepaliveResponse Message Example} +\label{s:keepalive_response_example} Added: key.tex =================================================================== --- key.tex (rev 0) +++ key.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Key} +\label{s:key} + +\subsection{KeyRequest Message} +\label{s:key_request} + +\subsubsection{KeyRequest Message Schema} +\label{s:key_request_schema} + +\subsubsection{KeyRequest Message Analysis} +\label{s:key_request_analysis} + +\paragraph{Message} +\label{s:key_request_analysis_message} + +\paragraph{Parameters} +\label{s:key_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:key_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:key_request_analysis_metadata} + +\paragraph{Data} +\label{s:key_request_analysis_data} + +\subsubsection{KeyRequest Message Example} +\label{s:key_request_example} + +\subsection{KeyResponse Message} +\label{s:key_response} + +\subsubsection{KeyResponse Message Schema} +\label{s:key_response_schema} + +\subsubsection{KeyResponse Message Analysis} +\label{s:key_response_analysis} + +\paragraph{Message} +\label{s:key_response_analysis_message} + +\paragraph{Parameters} +\label{s:key_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:key_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:key_response_analysis_metadata} + +\paragraph{Data} +\label{s:key_response_analysis_data} + +\paragraph{Key} +\label{s:key_response_analysis_key} + +\paragraph{Datum} +\label{s:key_response_analysis_datum} + +\subsubsection{KeyResponse Message Example} +\label{s:key_response_example} Added: nmc-is.bib =================================================================== --- nmc-is.bib (rev 0) +++ nmc-is.bib 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,29 @@ +@Misc{rfc2119, + author = {S. Bradner}, + title = {{K}ey {W}ords for {U}se in {RFC}s to {I}ndicate {R}equirement {L}evels}, + howpublished = {RFC 2119}, + month = {March}, + year = 1997, + url = "http://www.ietf.org/rfc/rfc2119.txt", +} + +@TechReport{nmbase, + Title = "{An Extensible Schema for Network Measurement and Performance Data}", + Author = "M. Swany", + institution = "Open Grid Forum", + year = "2009", + type = "Network Measurements Working Group Document", + month = "May", + note = "https://forge.gridforum.org/projects/nm-wg" +} + +@TechReport{nmcbase, + Title = "{An Extensible Protocol for Network Measurement and Control}", + Author = "J. Zurawski and M. Swany", + institution = "Open Grid Forum", + year = "2009", + type = "Network Measurement Control Working Group Document", + month = "May", + note = "https://forge.gridforum.org/projects/nmc-wg" +} + Added: nmc-is.pdf =================================================================== (Binary files differ) Property changes on: nmc-is.pdf ___________________________________________________________________ Name: svn:mime-type + application/pdf Added: nmc-is.tex =================================================================== --- nmc-is.tex (rev 0) +++ nmc-is.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,156 @@ +\documentclass[11pt]{article} +\usepackage{times} +\usepackage{fullpage} +\usepackage{citesort} +\usepackage{fancyheadings} +\usepackage{epsfig} +\usepackage{graphicx} +\usepackage{color} +\usepackage{url} +\usepackage{caption} +\usepackage[outermarks]{titlesec} + +\titleformat{\section} + {\normalfont\Large\bfseries}{\thesection}{1em}{} +\titleformat{\subsection} + {\normalfont\large\bfseries}{\thesubsection}{1em}{} +\titleformat{\subsubsection} + {\normalfont\normalsize\bfseries}{\thesubsubsection}{1em}{} +\titleformat{\paragraph} + {\normalfont\normalsize\bfseries}{\theparagraph}{1em}{} +\titleformat{\subparagraph} + {\normalfont\normalsize\bfseries}{\thesubparagraph}{1em}{} + +\titlespacing*{\section} {0pt}{3.5ex plus 1ex minus .2ex} {2.3ex plus .2ex} +\titlespacing*{\subsection} {0pt}{3.25ex plus 1ex minus .2ex}{1.5ex plus .2ex} +\titlespacing*{\subsubsection} {0pt}{3.25ex plus 1ex minus .2ex}{1.5ex plus .2ex} +\titlespacing*{\paragraph} {0pt}{3.25ex plus 1ex minus .2ex}{1.5ex plus .2ex} +\titlespacing*{\subparagraph} {0pt}{3.25ex plus 1ex minus .2ex}{1.5ex plus .2ex} + +\setcounter{secnumdepth}{6} +\setcounter{tocdepth}{6} + +\widowpenalty10000% +\clubpenalty10000% + +\tolerance=1000 + +\addtolength{\headheight}{30pt} + +\setlength{\captionmargin}{0.5in} +\renewcommand{\captionlabelfont}{\bfseries} +\setlength{\textfloatsep}{30pt plus 4pt minus 30pt} + +\lhead{\fancyplain{}{GWD-I}} +\chead{} +\rhead{\fancyplain{}{\today}} +\lfoot{\fancyplain{nmc-wg@ogf.org}{nmc-wg@ogf.org}} +\cfoot{} +\rfoot{\fancyplain{\thepage}{\thepage}} +\setlength{\headrulewidth}{0pt} + +\pagestyle{fancyplain} +\thispagestyle{plain} + +\begin{document} +%\maketitle +\bibliographystyle{plain} + +{ +\noindent +\begin{minipage}[t]{3.5in} +GWD-I\\ +Network Measurement Control Working Group\\ +https://forge.gridforum.org/projects/nmc-wg\\ +\end{minipage} +\hfill +\raggedleft +\begin{minipage}[t]{2.5in} +\raggedleft +Jason Zurawski, Internet2\\ +Martin Swany, UDel\\ +\today +\end{minipage} +} +\begin{center} +\Large\bf NMC Information Services\\ +\end{center} + +{\noindent\bf Status of This Document} \\ + +{\noindent This memo provides information for the Grid community. It does not specify any standards or technical recommendations. Distribution is unlimited.} \\ + +{\noindent\bf Copyright Notice} \\ + +{\noindent Copyright \copyright \ Open Grid Forum (2008-2009). All Rights Reserved.} \\ + +\section{Abstract} + +{\noindent ...} + +\tableofcontents + +\newpage + +\input{introduction} + +\input{register} + +\input{deregister} + +\input{keepalive} + +\input{key} + +\input{query} + +\input{discovery} + +\input{resultcodes} + +\section{Notational Conventions} + +The key words ``MUST'' ``MUST NOT'', ``REQUIRED'', ``SHALL'', ``SHALL NOT'', ``SHOULD'', ``SHOULD NOT'', ``RECOMMENDED'', ``MAY'', and ``OPTIONAL'' are to be interpreted as described in RFC 2119 \cite{rfc2119} + +\section{Security Considerations} + +There are no security considerations. + +\section{Contributors} + +\textbf{Jason Zurawski} \\ +Internet2 \\ +1150 18th Street, NW \\ +Suite 1020 \\ +Washington, DC 20036 \\ +\\ +\textbf{D. Martin Swany} (editor) \\ +University of Delaware \\ +Department of Computer and Information Sciences \\ +Newark, DE 19716 \\ + +\section{Glossary} + +{\noindent ...} + +\section{Intellectual Property Statement} + +{\noindent 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 assurances of licenses to be made available, or the result of an attempt 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.} \\ + +{\noindent 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.} + +\section{Disclaimer} + +{\noindent 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. } + +\section{Full Copyright Notice} + +Copyright \copyright \ Open Grid Forum (2008-2009). All Rights Reserved. \\ + +{\noindent 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.} \\ + +{\noindent The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees.} + +\bibliography{nmc-is} + +\end{document} Added: query.tex =================================================================== --- query.tex (rev 0) +++ query.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Query} +\label{s:query} + +\subsection{QueryRequest Message} +\label{s:query_request} + +\subsubsection{QueryRequest Message Schema} +\label{s:query_request_schema} + +\subsubsection{QueryRequest Message Analysis} +\label{s:query_request_analysis} + +\paragraph{Message} +\label{s:query_request_analysis_message} + +\paragraph{Parameters} +\label{s:query_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:query_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:query_request_analysis_metadata} + +\paragraph{Data} +\label{s:query_request_analysis_data} + +\subsubsection{QueryRequest Message Example} +\label{s:query_request_example} + +\subsection{QueryResponse Message} +\label{s:query_response} + +\subsubsection{QueryResponse Message Schema} +\label{s:query_response_schema} + +\subsubsection{QueryResponse Message Analysis} +\label{s:query_response_analysis} + +\paragraph{Message} +\label{s:query_response_analysis_message} + +\paragraph{Parameters} +\label{s:query_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:query_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:query_response_analysis_metadata} + +\paragraph{Data} +\label{s:query_response_analysis_data} + +\paragraph{Key} +\label{s:query_response_analysis_key} + +\paragraph{Datum} +\label{s:query_response_analysis_datum} + +\subsubsection{QueryResponse Message Example} +\label{s:query_response_example} Added: register.tex =================================================================== --- register.tex (rev 0) +++ register.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,62 @@ +\section{Register} +\label{s:register} + +\subsection{RegisterRequest Message} +\label{s:register_request} + +\subsubsection{RegisterRequest Message Schema} +\label{s:register_request_schema} + +\subsubsection{RegisterRequest Message Analysis} +\label{s:register_request_analysis} + +\paragraph{Message} +\label{s:register_request_analysis_message} + +\paragraph{Parameters} +\label{s:register_request_analysis_parameters} + +\paragraph{Parameter} +\label{s:register_request_analysis_parameter} + +\paragraph{Metadata} +\label{s:register_request_analysis_metadata} + +\paragraph{Data} +\label{s:register_request_analysis_data} + +\subsubsection{RegisterRequest Message Example} +\label{s:register_request_example} + +\subsection{RegisterResponse Message} +\label{s:register_response} + +\subsubsection{RegisterResponse Message Schema} +\label{s:register_response_schema} + +\subsubsection{RegisterResponse Message Analysis} +\label{s:register_response_analysis} + +\paragraph{Message} +\label{s:register_response_analysis_message} + +\paragraph{Parameters} +\label{s:register_response_analysis_parameters} + +\paragraph{Parameter} +\label{s:register_response_analysis_paramter} + +\paragraph{Metadata} +\label{s:register_response_analysis_metadata} + +\paragraph{Data} +\label{s:register_response_analysis_data} + +\paragraph{Key} +\label{s:register_response_analysis_key} + +\paragraph{Datum} +\label{s:register_response_analysis_datum} + +\subsubsection{RegisterResponse Message Example} +\label{s:register_response_example} Added: resultcodes.tex =================================================================== --- resultcodes.tex (rev 0) +++ resultcodes.tex 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,27 @@ +\section{Result Codes} +\label{s:resultcodes} + +The following new result codes can be incorporated into this extension based on the work in the \textit{NMC Protocol} \cite{nmcbase}. We will introduce these into both styles to allow for backwards compatibility. The original style is presented first: + +\begin{tabular}{lll} +\\ +success. & & \\ + & is. & \\ +\\ +error. & & \\ + & is. & \\ +\\ +\end{tabular} + +We can express the same information using the new URI style: + +\begin{tabular}{lllll} +\\ +http://schemas.perfsonar.net/status/ & & & & \\ + & success/ & & & \\ + & & is/ & & \\ + & error/ & & & \\ + & & is/ & & \\ + +\\ +\end{tabular} Added: util/inline.pl =================================================================== --- util/inline.pl (rev 0) +++ util/inline.pl 2010-01-12 13:45:15 UTC (rev 1) @@ -0,0 +1,39 @@ +#!/usr/bin/perl -w + +use strict; +use warnings; + +while(<>) { + chop; + if ($_ =~ m/^\%\s+INLINESCHEMA=.*/) { + my ($fn) = m/"(.*)"/; + open F, "< $fn"; + print "\# Begin Schema\n\n"; + while(<F>) { + print $_; + } + print "\n\# End Schema\n"; + } + if ($_ =~ m/^\%\s+INLINEXML=.*/) { + my ($fn) = m/"(.*)"/; + open F, "< $fn"; + print "\n\n"; + while(<F>) { + print $_; + } + print "\n\n"; + } + if ($_ =~ m/^\%\s+INLINE=.*/) { + my ($fn) = m/"(.*)"/; + open F, "< $fn"; + print "\# Begin \n\n"; + while(<F>) { + print $_; + } + print "\n\# End \n"; + } + else { + print "$_\n"; + } +} + Property changes on: util/inline.pl ___________________________________________________________________ Name: svn:executable + * Name: svn:mime-type + text/x-perl Name: svn:keywords + "Author Date Id Rev URL" Name: svn:eol-style + native

1 0