From 622ea091446836d5dd5b5b6b9b002189e673ea82 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= <j.wielicki@sotecware.net>
Date: Tue, 28 Jan 2020 18:53:40 +0100
Subject: [PATCH] Accept inbox/sige2ee.xml as XEP-0429

---
 xep-0429.xml | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100644 xep-0429.xml

diff --git a/xep-0429.xml b/xep-0429.xml
new file mode 100644
index 00000000..e301cc71
--- /dev/null
+++ b/xep-0429.xml
@@ -0,0 +1,60 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE xep SYSTEM 'xep.dtd' [
+  <!ENTITY % ents SYSTEM "xep.ent">
+%ents;
+]>
+<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
+<xep>
+<header>
+  <title>Special Interests Group End to End Encryption</title>
+  <abstract>This document proposes the formation of a Special Interest Group (SIG) within the XSF devoted to the development of end-to-end encryption within the context of XMPP.</abstract>
+  &LEGALNOTICE;
+  <number>0429</number>
+  <status>Experimental</status>
+  <type>Procedural</type>
+  <sig>None</sig>
+  <approver>Council</approver>
+  <dependencies/>
+  <supersedes/>
+  <supersededby/>
+  <shortname>SIG-E2EE</shortname>
+  &paulschaub;
+  <revision>
+    <version>0.1.0</version>
+    <date>2020-01-28</date>
+    <initials>XEP Editor (jsc)</initials>
+    <remark>Accepted by vote of Council on 2020-01-08.</remark>
+  </revision>
+  <revision>
+    <version>0.0.1</version>
+    <date>2019-12-30</date>
+    <initials>ps</initials>
+    <remark>Initial published version.</remark>
+  </revision>
+</header>
+<section1 topic='Introduction' anchor='intro'>
+  <p>End-to-end encryption presents a vital tool for users to protect their communications against third parties. To ensure a good user experience it is important to agree on shared standards which are widely rolled out and adopted by implementations.</p>
+  <p>There already exists a number of encryption protocols with different properties and scopes. It is necessary to coordinate the efforts of further improving those standards to identify and unify common problems and patterns.</p>
+</section1>
+<section1 topic='Scope and Role' anchor='scope'>
+  <p>The role of the SIG shall be as follows:</p>
+  <ul>
+    <li>Produce, or coordinate the production and maintenance of relevant XMPP Extension Protocol (XEP) documents as described below under Deliverables.</li>
+    <li>Represent the interests and requirements of the XMPP community during the development of end-to-end encryption protocols that are non-exclusive to XMPP.</li>
+    <li>Provide recommendations for implementers.</li>
+  </ul>
+  <p>The SIG-E2EE shall not itself approve XMPP extension protocols (XEPs), which tasks shall remain under the purview of the XMPP Council.</p>
+  <p>The scope of the SIG is limited to end-to-end encryption in contexts which are useful for instant messaging.</p>
+</section1>
+<section1 topic='Membership' anchor='membership'>
+  <p>The SIG-E2EE shall be open to the public and shall not be limited to elected members of the XMPP Standards Foundation. Anyone who works with, or is interested in encryption protocols is invited to take part.</p>
+  <p>Discussions shall be conducted in a dedicated openly accessible mailing list.</p>
+</section1>
+<section1 topic='Lifetime' anchor='lifetime'>
+  <p>The SIG-E2EE shall be a standing SIG, and shall exist as long as the XMPP Council deems it useful.</p>
+</section1>
+<section1 topic='Deliverables' anchor='deliverables'>
+  <p>The SIG-E2EE should maintain active existing end-to-end encryption specifications and keep them up to date.</p>
+  <p>It should also coordinate the production of future end-to-end encryption specifications to keep up with the state of the art.</p>
+</section1>
+</xep>