diff --git a/xep-0032.xml b/xep-0032.xml
index 692bb896..673ee54d 100644
--- a/xep-0032.xml
+++ b/xep-0032.xml
@@ -15,7 +15,7 @@
   <sig>Standards</sig>
   <dependencies>None</dependencies>
   <supersedes>None</supersedes>
-  <supersededby><spec>RFC 4622</spec></supersededby>
+  <supersededby><spec>RFC 5122</spec></supersededby>
   &stpeter;
   &pgmillard;
   <revision>
@@ -44,7 +44,7 @@
   </revision>
 </header>
 <section1 topic='Introduction'>
-  <p><em>Note: This document has been superseded by &rfc4622;.</em></p>
+  <p><em>Note: This document has been superseded by &rfc5122;.</em></p>
   <p>It is widely acknowledged that it would be good to be able to express a Jabber Identifier (JID) (see &xep0029;) as a Uniform Resource Identifier (see &rfc3986;). In addition, there would be value in being able to interact with a JID through a URI scheme (e.g., by sending a message or a presence update).</p>
   <p>Although XMPP enables a wide range of functionality, the authors propose that a Jabber URI scheme needs to support only a limited subset of the possible Jabber functionality. In particular, we see the following as core functions that need to be supported:</p>
   <ul>