Michael; Can you revert these changes please, these are necessary based on the way the document is generated via the Makefile - there is a pre-processing step to convert the XML snippets. Thanks; -jason On 6/14/10 5:34 PM, svn@ogf.org wrote:
Author: mbischoff Date: 2010-06-14 16:34:16 -0500 (Mon, 14 Jun 2010) New Revision: 25
Modified: nmc-base.tex Log: Added first version of security considerations
Modified: nmc-base.tex =================================================================== --- nmc-base.tex 2010-05-27 18:15:38 UTC (rev 24) +++ nmc-base.tex 2010-06-14 21:34:16 UTC (rev 25) @@ -102,17 +102,17 @@
\newpage
-\input{introduction_new} +\input{introduction}
-\input{motivation_new} +\input{motivation}
-\input{messages_new} +\input{messages}
-\input{chaining_new} +\input{chaining}
-\input{result_codes_new} +\input{result_codes}
-\input{extension_new} +\input{extension}
\input{conclusion}
@@ -122,17 +122,8 @@
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.
-\section{Security Considerations} -% XXX jz - 1/28/2010 -% -% A comment from Michael: -% -% Security considerations seem to be absent, like the transport layer that soap -% uses should provide integrity and privacy protection to avoid MITM-attacks -% etc. +\input{security_considerations}
-There are no security considerations. - \section{Contributors}
\textbf{Jason Zurawski} \\
_______________________________________________ Nmc-wg mailing list Nmc-wg@ogf.org http://www.ogf.org/mailman/listinfo/nmc-wg