Author: zurawski Date: 2010-06-15 06:04:09 -0500 (Tue, 15 Jun 2010) New Revision: 31 Modified: acknowledgements.tex conclusion.tex nmc-base.pdf nmc-base.tex Log: Movin the security section before the notational conventions. Minor cleanups to ack/conc that were left out of a commit. -jason Modified: acknowledgements.tex =================================================================== --- acknowledgements.tex 2010-06-15 00:17:13 UTC (rev 30) +++ acknowledgements.tex 2010-06-15 11:04:09 UTC (rev 31) @@ -1,4 +1,8 @@ \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-WG protocols. +The authors gratefully acknowledge the contributions of the perfSONAR consortium +to this work. Specifically staff and member institutions from ESnet, G\'{E}ANT, +Internet2, and RNP have provided extensive input and feedback into the +implementation of this and all NMC-WG protocols. + Modified: conclusion.tex =================================================================== --- conclusion.tex 2010-06-15 00:17:13 UTC (rev 30) +++ conclusion.tex 2010-06-15 11:04:09 UTC (rev 31) @@ -5,4 +5,11 @@ % % 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. +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: nmc-base.pdf =================================================================== (Binary files differ) Modified: nmc-base.tex =================================================================== --- nmc-base.tex 2010-06-15 00:17:13 UTC (rev 30) +++ nmc-base.tex 2010-06-15 11:04:09 UTC (rev 31) @@ -118,12 +118,12 @@ \input{acknowledgements} +\input{security_considerations} + \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}, except that the words do not appear in uppercase. -\input{security_considerations} - \section{Contributors} \textbf{Jason Zurawski} \\