From 2d5f923432b8101444669d974180499ed76d58ad Mon Sep 17 00:00:00 2001
From: Guus der Kinderen <guus.der.kinderen@gmail.com>
Date: Thu, 15 Sep 2022 10:34:22 +0200
Subject: [PATCH 1/2] XEP-0029: Use RFC 7622 instead of RFC 6122 to supersede

RFC 7622 obsoletes RFC 6122. It stands to reason that XEPs that are marked as being superseded by the former should be updated to be superseded by the latter.
---
 xep-0029.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/xep-0029.xml b/xep-0029.xml
index 8c0a3dcd..98543e97 100644
--- a/xep-0029.xml
+++ b/xep-0029.xml
@@ -7,7 +7,7 @@
 <xep>
     <header>
         <title>Definition of Jabber Identifiers (JIDs)</title>
-        <abstract>Note well: this document was superseded by RFC 3920, which in turn has been superseded by RFC 6122. This document defines the exact nature of a Jabber Identifier (JID).</abstract>
+        <abstract>Note well: this document was superseded by RFC 3920 and RFC 6122, which in turn have been superseded by RFC 7622. This document defines the exact nature of a Jabber Identifier (JID).</abstract>
         &LEGALNOTICE;
         <number>0029</number>
         <status>Retracted</status>
@@ -15,7 +15,7 @@
         <sig>Standards</sig>
         <dependencies/>
         <supersedes/>
-        <supersededby><spec>RFC 6122</spec></supersededby>
+        <supersededby><spec>RFC 7622</spec></supersededby>
         <shortname>N/A</shortname>
         <author>
             <firstname>Craig</firstname>
@@ -51,7 +51,7 @@
         </revision>
     </header>
     <section1 topic='Introduction'>
-        <p class='box'>Note: This document was superseded by &rfc3920;, which in turn has been superseded by &rfc6122;.</p>
+        <p class='box'>Note: This document was superseded by &rfc3920; and &rfc6122;, which in turn have been superseded by &rfc7622;.</p>
         <p>Jabber Identifiers (JIDs) uniquely identify individual entities in the Jabber network. To date, their syntax has been defined by convention, existing implementations, and available documentation. As it exists, certain characters that are allowed in JIDs cause ambiguity, and the lack of a size limit on resources defies database schemas and causes some trivial JID operations to require dynamic memory allocation. This document seeks to both define and improve the existing JID syntax. This document will not explain the general usage or nature of JIDs, instead focusing on syntax.</p>
     </section1>
     <section1 topic='JIDs'>

From 6aa697d34d718238631ad68d5504e0977d7d6ade Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= <j.wielicki@sotecware.net>
Date: Fri, 23 Sep 2022 17:33:48 +0200
Subject: [PATCH 2/2] XEP-0029: add revision block

---
 xep-0029.xml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/xep-0029.xml b/xep-0029.xml
index 98543e97..d74a7070 100644
--- a/xep-0029.xml
+++ b/xep-0029.xml
@@ -23,6 +23,12 @@
             <email>craigk@jabber.com</email>
             <jid>craigk@jabber.com</jid>
         </author>
+        <revision>
+            <version>1.1.1</version>
+            <date>2022-09-23</date>
+            <initials>gk</initials>
+            <remark>Add references to RFC 7622, which has superseded RFC 6122.</remark>
+        </revision>
         <revision>
             <version>1.1</version>
             <date>2003-10-03</date>