Spec: add credits and move to end

doc/of-spec/credits.tex

@@ -0,0 +1,22 @@
+\section{Appendix B: Credits}
+
+Current Maintainer: Brandon Heller (brandonh@stanford.edu).
+\\\\
+Spec contributions, in alphabetical order:
+\\\\
+Ben Pfaff,
+Brandon Heller,
+Dan Talayco,
+David Erickson,
+Glen Gibb,
+Guido Appenzeller,
+Jean Tourrilhes,
+Justin Pettit,
+KK Yap,
+Martin Casado,
+Masayoshi Kobayashi,
+Nick McKeown,
+Peter Balland,
+Reid Price,
+Rob Sherwood,
+Yiannis Yiakoumis.

doc/of-spec/openflow-spec-v1.0.0.tex

@@ -35,10 +35,6 @@
 \date{\today}
 \maketitle
 
-\begin{center}
-Current Maintainer: Brandon Heller (brandonh@stanford.edu)
-\end{center}
-
 \section{Introduction}
 This document describes the requirements of an OpenFlow Switch.  We recommend that you read the latest version of the OpenFlow whitepaper before reading this specification. The whitepaper is available on the  OpenFlow Consortium website (\url{http://OpenFlowSwitch.org}). This specification covers the components and the basic functions of the switch, and the OpenFlow protocol to manage an OpenFlow switch from a remote controller.
 \\\\
@@ -416,5 +412,7 @@ Emergency flow mod messages must have timeout values set to zero.  Otherwise, th
 Each flow entry has an \verb|idle_timeout| and a \verb|hard_timeout| associated with it.  If no packet has matched the rule in the last \verb|idle_timeout| seconds, or it has been \verb|hard_timeout| seconds since the flow was inserted, the switch removes the entry and sends a flow removed message.  In addition, the controller is able to actively remove entries by sending a flow message with the \verb|DELETE| or \verb|DELETE_STRICT| command.  Like the message used to add the entry, a removal message contains a description, which may include wild cards.
 
 \input{appendix}
+
+\input{credits}
  
 \end{document}