RFC numbers

xep-0073.xml

@@ -111,7 +111,7 @@
 <section1 topic='Introduction' anchor='intro'>
   <p><em>Note: This protocol suite is obsolete. For updated protocol suites, refer to &xep0211; and &xep0212;.</em></p>
   <p>Given the large number of Jabber/XMPP protocols, 
-    <note>The protocols developed by the Jabber community have matured considerably since 1999. The core protocols were originally created by a small group of developers who worked on early Jabber-related open-source software projects such as the &jabberd; server, the Winjab, Gabber, and Jarl clients, the Net::Jabber and Jabberbeans libraries, and gateways to consumer IM services. In the summer of 2001, the &XSF; was founded to institute a formal standards process within the growing Jabber community (codified in &xep0001;). In late 2002, the &IETF; formed the &XMPPWG;, which formalized the core Jabber protocols under the name Extensible Messaging and Presence Protocol (XMPP). In early 2004, the IETF approved the main XMPP specifications as Proposed Standards within the Internet Standards Process defined by &rfc2026;, resulting in publication of <cite>RFC 3920</cite> (&xmppcore;) and <cite>RFC 3921</cite> (&xmppim;). In the meantime, the XSF has continued to develop additional protocols on top of XMPP in order to address functionality areas that are too application-specific for consideration within the IETF.</note>
+    <note>The protocols developed by the Jabber community have matured considerably since 1999. The core protocols were originally created by a small group of developers who worked on early Jabber-related open-source software projects such as the &jabberd; server, the Winjab, Gabber, and Jarl clients, the Net::Jabber and Jabberbeans libraries, and gateways to consumer IM services. In the summer of 2001, the &XSF; was founded to institute a formal standards process within the growing Jabber community (codified in &xep0001;). In late 2002, the &IETF; formed the &XMPPWG;, which formalized the core Jabber protocols under the name Extensible Messaging and Presence Protocol (XMPP). In early 2004, the IETF approved the main XMPP specifications as Proposed Standards within the Internet Standards Process defined by &rfc2026;, resulting in publication of &rfc3920; and &rfc3921;. In the meantime, the XSF has continued to develop additional protocols on top of XMPP in order to address functionality areas that are too application-specific for consideration within the IETF.</note>
   it is not always clear to developers exactly which protocols they need to implement in order to interoperate over Jabber/XMPP networks. This document attempts to assist developers by defining a protocol suite for basic instant messaging and presence.</p>
 </section1>
 <section1 topic='Requirements and Approach' anchor='reqs'>

xep-0242.xml

@@ -59,8 +59,8 @@
 <section1 topic='XMPP Core Client 2009' anchor='core'>
   <p>The XMPP Core Client 2009 certification level is defined as follows:</p>
   <ul>
-    <li>&rfc6120;</li>
+    <li>&rfc3920;</li>
-    <li>&rfc6121;</li>
+    <li>&rfc3921;</li>
     <li>&xep0030;</li>
     <li>&xep0115;</li>
   </ul>

xep-0243.xml

@@ -67,8 +67,8 @@
 <section1 topic='XMPP Core Server 2009' anchor='core'>
   <p>The XMPP Core Server 2009 certification level is defined below. Support for these specifications is REQUIRED for compliance purposes.</p>
   <ul>
-    <li>&rfc6120;</li>
+    <li>&rfc3920;</li>
-    <li>&rfc6121;</li>
+    <li>&rfc3921;</li>
     <li>&xep0030;</li>
   </ul>
 </section1>

xep-0270.xml

@@ -59,14 +59,14 @@
       <th>Advanced Client</th>
     </tr>
     <tr>
-      <td>&rfc6120;</td>
+      <td>&rfc3920;</td>
       <td align='center'>&#10003;</td>
       <td align='center'>&#10003;</td>
       <td align='center'>&#10003;</td>
       <td align='center'>&#10003;</td>
     </tr>
     <tr>
-      <td>&rfc6121;</td>
+      <td>&rfc3921;</td>
       <td align='center'>&#10003;</td>
       <td align='center'>&#10003;</td>
       <td align='center'>&#10003;</td>