Updated tests, see issue #125

 - Legacy-Id: 867

cli/tests/valid/rfc6787.html

@@ -628,10 +628,9 @@
 <link href="#rfc.references.2" rel="Chapter" title="17.2 Informative References"/>
 <link href="#rfc.appendix.A" rel="Chapter" title="A Contributors"/>
 <link href="#rfc.appendix.B" rel="Chapter" title="B Acknowledgements"/>
-<link href="#rfc.authors" rel="Chapter"/>
 
 
-  <meta name="generator" content="xml2rfc version 2.3.12.dev - http://tools.ietf.org/tools/xml2rfc" />
+  <meta name="generator" content="xml2rfc version 2.4.1 - http://tools.ietf.org/tools/xml2rfc" />
   <link rel="schema.dct" href="http://purl.org/dc/terms/" />
 
   <meta name="dct.creator" content="Burnett, D. and S. Shanmugham" />
@@ -973,7 +972,6 @@ <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
 <li>17.2.   <a href="#rfc.references.2">Informative References</a></li>
 <li>Appendix A.   <a href="#rfc.appendix.A">Contributors</a></li>
 <li>Appendix B.   <a href="#rfc.appendix.B">Acknowledgements</a></li>
-<li><a href="#rfc.authors">Authors' Addresses</a></li>
 
 
   </ul>

cli/tests/valid/rfc6787.nroff

@@ -1,4 +1,4 @@
-.\" automatically generated by xml2rfc v2.4.1 on 2013-05-24T18:40:12Z
+.\" automatically generated by xml2rfc v2.4.1 on 2013-05-25T18:12:07Z
 
 .pl 10.0i
 .po 0
@@ -378,7 +378,6 @@ Table of Contents
      17.2.  Informative References . . . . . . . . . . . . . . . . . 232
    Appendix A.  Contributors . . . . . . . . . . . . . . . . . . . . 234
    Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . . 234
-   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 235
 .fi
 .in 3
 
@@ -418,10 +417,9 @@ cause backward-compatibility problems, something forbidden by
 Section\03.2 of [RFC4313].  This is the reason why MRCPv2 does not
 run over RTSP.
 
-
-.bp
 MRCPv2 leverages these capabilities by building upon SIP and the
 Session Description Protocol (SDP) [RFC4566].  MRCPv2 uses SIP to set
+.bp
 up and tear down media and control sessions with the server.  In
 addition, the client can use a SIP re-INVITE method (an INVITE dialog
 sent within an existing SIP session) to change the characteristics of
@@ -469,6 +467,8 @@ All the mechanisms specified in this document are described in both
 prose and an augmented Backus-Naur form (ABNF [RFC5234]).
 
 
+
+
 .bp
 The complete message format in ABNF form is provided in Section\015
 and is the normative format definition.  Note that productions may be

cli/tests/valid/rfc6787.raw.txt

@@ -351,7 +351,6 @@ Table of Contents
      17.2.  Informative References
    Appendix A.  Contributors
    Appendix B.  Acknowledgements
-   Authors' Addresses
 
 
 Internet Engineering Task Force (IETF)                        D. Burnett