remove all traces of E-D keysync

lamps-header-protection/draft-luck-lamps-pep-header-protection.mkd

@@ -43,7 +43,7 @@ informative:
 #  I-D.marques-pep-handshake:
 #  I-D.birk-pep-trustwords:
 #  I-D.marques-pep-rating:
-# {::include ../shared/references/ed-keysync.mkd}
+#  I-D.hoeneisen-pep-keysync:
 # {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 

medup-requirements/draft-symeonidis-medup-requirements.mkd

@@ -29,6 +29,7 @@ informative:
   I-D.birk-pep-trustwords:
 #  I-D.marques-pep-rating:
 #  I-D.marques-pep-handshake:
+#  I-D.hoeneisen-pep-keysync:
 
 {::include ../shared/references/unger-sok.mkd}
 {::include ../shared/references/pfitzmann-terminology-privacy.mkd}
@@ -37,7 +38,6 @@ informative:
 {::include ../shared/references/ermoshina-end2end-enc.mkd}
 {::include ../shared/references/clark-seuring-email.mkd}
 
-# {::include ../shared/references/ed-keysync.mkd}
 # {::include ../shared/references/isoc-btn.mkd}
 # {::include ../shared/references/implementation-status.mkd}
 

pep-email/draft-marques-pep-email.mkd

@@ -39,6 +39,8 @@ informative:
 #  I-D.marques-pep-email:
   I-D.birk-pep-trustwords:
   I-D.melnikov-lamps-header-protection:
+  I-D.hoeneisen-pep-keysync:
+
   usenix.defective-sgn-enc:
     target: https://www.usenix.org/legacy/publications/library/proceedings/usenix01/full_papers/davis/davis_html/index.html
     title: "Defective Sign Encrypt in S/MIME, PKCS7, MOSS, PEM, PGP, and XML. 65-78"
@@ -49,7 +51,6 @@ informative:
     date: 2001    
 
 
-{::include ../shared/references/ed-keysync.mkd}
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 
@@ -114,7 +115,7 @@ Email). While defining the specifics for pEp Email, it builds on top
 of {{I-D.birk-pep}} that describes the general concept of pEp as well
 as on other document defining pEp helper functions such as pEp
 Handshake {{I-D.marques-pep-handshake}}) or pEp Rating
-{{I-D.marques-pep-rating}}. <!-- or pEp Sync {{E-D.birk-pep-keysync}}
+{{I-D.marques-pep-rating}}. <!-- or pEp Sync {{I-D.hoeneisen-pep-keysync}}
 -->
 
 A fair understanding of {{I-D.birk-pep}} is needed to comprehend this document, 
@@ -1318,7 +1319,7 @@ messages to/from this identity.
 
 # Synchronization
 
-As per {{E-D.birk-pep-keysync}}...
+As per {{I-D.hoeneisen-pep-keysync}}...
 
 \[\[ TODO: Add here what is specific to email \]\] 
 

pep-handshake/draft-marques-pep-handshake.mkd

@@ -30,6 +30,7 @@ informative:
 #   I-D.marques-pep-email:
   I-D.marques-pep-rating:
 #   I-D.marques-pep-handshake:
+  I-D.hoeneisen-pep-keysync:
   signal:
     target: https://signal.org/
     title: Signal
@@ -43,7 +44,6 @@ informative:
     title: PGP word list
     date: 2017-11
 
-{::include ../shared/references/ed-keysync.mkd}
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 
@@ -135,7 +135,7 @@ Such a verification process is useful in at least two scenarios:
 * Verify channels between own devices (in multi-device contexts),
   e.g., for the purpose of importing and synchronizing keys among
   different devices belonging to the same user
-  (cf. {{E-D.birk-pep-keysync}}). This scenario is comparable to
+  (cf. {{I-D.hoeneisen-pep-keysync}}). This scenario is comparable to
   Bluetooth pairing before starting data transfers.
 
 ## Existing Solutions

pep-keyreset/draft-marques-pep-keyreset.mkd

@@ -30,8 +30,8 @@ informative:
 #  I-D.luck-lamps-pep-header-protection:
 #  I-D.marques-pep-email:
   I-D.birk-pep-trustwords:
+#  I-D.hoeneisen-pep-keysync:
 
-#{::include ../shared/references/ed-keysync.mkd}
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 

pep-keysync/draft-hoeneisen-pep-keysync.mkd

@@ -32,7 +32,7 @@ informative:
   I-D.marques-pep-handshake:
 #  I-D.luck-lamps-pep-header-protection:
 
-# {::include ../shared/references/ed-keysync.mkd}
+#   I-D.hoeneisen-pep-keysync:
 {::include ../shared/references/isoc-btn.mkd}
 # {::include ../shared/references/implementation-status.mkd}
 

pep-rating/draft-marques-pep-rating.mkd

@@ -36,7 +36,7 @@ informative:
       ins: C. Grothoff
     date: 2017-10-07
 
-# {::include ../shared/references/ed-keysync.mkd}
+#   I-D.hoeneisen-pep-keysync:
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 

pep-trustwords/draft-birk-pep-trustwords.mkd

@@ -35,6 +35,7 @@ informative:
 #   I-D.birk-pep-trustwords:
 #   I-D.marques-pep-rating:
   I-D.marques-pep-handshake:
+  I-D.hoeneisen-pep-keysync:
   PGP.wl:
     target: https://en.wikipedia.org/w/index.php?title=PGP_word_list&oldid=749481933
     title: PGP word list
@@ -47,7 +48,6 @@ informative:
     target: https://www.iso.org/iso-639-language-codes.html
     title: "Language codes - ISO 639"
 
-{::include ../shared/references/ed-keysync.mkd}
 {::include ../shared/references/isoc-btn.mkd}
 # {::include ../shared/references/implementation-status.mkd}
 
@@ -95,7 +95,7 @@ other purposes, such as Human-Readable 128-bit Keys {{RFC1751}}, One
 Time Passwords (OTP) {{RFC1760}} {{RFC2289}}, SSH host-key
 verification, VPN Server certificate verification, and to import or
 synchronize secret key across different devices of the same user
-{{E-D.birk-pep-keysync}}.  Further ideas include to use Trustwords for
+{{I-D.hoeneisen-pep-keysync}}.  Further ideas include to use Trustwords for
 contact verification in Extensible Messaging and Presence Protocol
 (XMPP) {{RFC6120}}, for X.509 {{RFC3647}} certificate verification in
 browsers or in block chain applications for crypto currencies.

pep/draft-birk-pep.mkd

@@ -34,12 +34,13 @@ informative:
   I-D.birk-pep-trustwords:
   I-D.marques-pep-rating:
   I-D.marques-pep-handshake:
+  I-D.hoeneisen-pep-keysync:
+
   SRC.pepcore:
     target: https://pep.foundation/dev/
     title: Core source code and reference implementation of pEp (engine and adapters)
     date: 2018-07
 
-{::include ../shared/references/ed-keysync.mkd}
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 
@@ -202,7 +203,7 @@ and understanding cryptographic parts that he/she needs to be aware
 of.
 
 1. Helper functions for interactions between a user's own devices
-(e.g., pEp Key Sync {{E-D.birk-pep-keysync}}) that assist the user
+(e.g., pEp Key Sync {{I-D.hoeneisen-pep-keysync}}) that assist the user
 to run pEp applications on different devices (such as computer,
 mobile phone or tables) at the same time.
 
@@ -1507,7 +1508,7 @@ devices.
 ## Private Key Synchronization
 
 A decentralized proposition -- the pEp Key Synchronization
-protocol. {{E-D.birk-pep-keysync}} -- defines how pEp users can distribute
+protocol. {{I-D.hoeneisen-pep-keysync}} -- defines how pEp users can distribute
 their private keys among different devices in a user-authenticated
 manner: this allows users to read their messages across their
 different devices, when sharing a common address (e.g., the same email

shared/references/ed-keysync.mkd

@@ -1,12 +0,0 @@
-  E-D.birk-pep-keysync:
-    target: https://pep.foundation/dev/repos/internet-drafts/file/tip/pep-keysync/draft-birk-pep-keysync-NN.txt
-    title: "pretty Easy privacy (pEp): Key Synchronization Protocol"
-    author:
-      -
-        name: Volker Birk
-        ins: V. Birk
-      -
-        name: Hernani Marques
-        ins: H. Marques
-    date: 2018-06
-    ann: Early draft