s/hoeneisen-pep-keysync/pep-keysync/g

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:
-#  I-D.hoeneisen-pep-keysync:
+#  I-D.pep-keysync:
 # {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 

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

@@ -29,7 +29,7 @@ informative:
   I-D.birk-pep-trustwords:
 #  I-D.marques-pep-rating:
 #  I-D.marques-pep-handshake:
-#  I-D.hoeneisen-pep-keysync:
+#  I-D.pep-keysync:
 I-D.draft-symeonidis-pearg-private-messaging-threat-analysis:
  
 {::include ../shared/references/unger-sok.mkd}

medup-ux-considerations/draft-lenzini-medup-ux-considerations.mkd

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

pearg-analysis/draft-symeonidis-pearg-private-messaging-threats.mkd

@@ -30,7 +30,7 @@ informative:
 #  I-D.birk-pep-trustwords:
 #  I-D.marques-pep-rating:
 #  I-D.marques-pep-handshake:
-#  I-D.hoeneisen-pep-keysync:
+#  I-D.pep-keysync:
 
 {::include ../shared/references/clark-seuring-email.mkd}
 {::include ../shared/references/diaz-measuring-anonymity.mkd}

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

@@ -40,7 +40,7 @@ informative:
 #  I-D.marques-pep-email:
   I-D.birk-pep-trustwords:
   I-D.melnikov-lamps-header-protection:
-#  I-D.hoeneisen-pep-keysync:
+#  I-D.pep-keysync:
 
   usenix.defective-sgn-enc:
     target: https://www.usenix.org/legacy/publications/library/proceedings/usenix01/full_papers/davis/davis_html/index.html
@@ -126,7 +126,7 @@ defining the specifics for pEp Email, it builds on top of
 as on other documents defining pEp helper functions such as pEp
 Handshake {{I-D.marques-pep-handshake}}) and pEp Rating
 {{I-D.marques-pep-rating}}<!-- or pEp Sync
-{{I-D.hoeneisen-pep-keysync}} -->.
+{{I-D.pep-keysync}} -->.
 
 A fair understanding of {{I-D.birk-pep}} is helpful to understand the 
 pEp principles this document relies on, as this document tries to avoid 
@@ -1707,7 +1707,7 @@ Messages to/from this identity.
 
 # Synchronization
 
-As per <!-- {{I-D.hoeneisen-pep-keysync}}... -->
+As per <!-- {{I-D.pep-keysync}}... -->
 
 \[\[ TODO: Add here what is specific to email \]\] 
 

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

@@ -30,7 +30,7 @@ informative:
 #   I-D.marques-pep-email:
   I-D.marques-pep-rating:
 #   I-D.marques-pep-handshake:
-  I-D.hoeneisen-pep-keysync:
+  I-D.pep-keysync:
   signal:
     target: https://signal.org/
     title: Signal
@@ -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. {{I-D.hoeneisen-pep-keysync}}). This scenario is comparable to
+  (cf. {{I-D.pep-keysync}}). This scenario is comparable to
   Bluetooth pairing before starting data transfers.
 
 ## Existing Solutions

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

@@ -30,7 +30,7 @@ informative:
 #  I-D.luck-lamps-pep-header-protection:
 #  I-D.marques-pep-email:
   I-D.birk-pep-trustwords:
-#  I-D.hoeneisen-pep-keysync:
+#  I-D.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
 
-#   I-D.hoeneisen-pep-keysync:
+#   I-D.pep-keysync:
 {::include ../shared/references/isoc-btn.mkd}
 {::include ../shared/references/implementation-status.mkd}
 

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

@@ -35,7 +35,7 @@ informative:
 #   I-D.birk-pep-trustwords:
 #   I-D.marques-pep-rating:
   I-D.marques-pep-handshake:
-  I-D.hoeneisen-pep-keysync:
+  I-D.pep-keysync:
   PGP.wl:
     target: https://en.wikipedia.org/w/index.php?title=PGP_word_list&oldid=749481933
     title: PGP word list
@@ -93,7 +93,7 @@ Time Passwords (OTP) {{RFC1760}} {{RFC2289}}, SSH host-key
 verification, VPN server certificate verification, deriving private
 keys in blockchain applications for cryptocurrencies, and to import or
 synchronize secret keys across multiple devices owned by a single user
-{{I-D.hoeneisen-pep-keysync}}.  Further ideas include the use of
+{{I-D.pep-keysync}}.  Further ideas include the use of
 Trustwords for private key recovery in case of loss, contact
 verification in Extensible Messaging and Presence Protocol (XMPP)
 {{RFC6120}}, or for X.509 certificate verification in browsers

pep/draft-birk-pep.mkd

@@ -32,7 +32,7 @@ informative:
   I-D.birk-pep-trustwords:
   I-D.marques-pep-rating:
   I-D.marques-pep-handshake:
-  I-D.hoeneisen-pep-keysync:
+  I-D.pep-keysync:
 
   SRC.pepcore:
     target: https://pep.foundation/dev/
@@ -201,7 +201,7 @@ users (e.g., pEp Handshake {{I-D.marques-pep-handshake}}).
 1. Helper functions for interactions between a user's own devices, which give 
 the user the ability to run pEp applications on different devices at the same 
 time, such as a computer, mobile phone, or tablets (e.g., pEp KeySync
-{{I-D.hoeneisen-pep-keysync}}).
+{{I-D.pep-keysync}}).
 
 In addition, there are documents that do not directly depend on this
 one, but provide generic functions needed in pEp, e.g., IANA
@@ -1531,7 +1531,7 @@ devices.
 
 ## Private Key Synchronization
 
-The pEp KeySync protocol (cf. {{I-D.hoeneisen-pep-keysync}}) is a 
+The pEp KeySync protocol (cf. {{I-D.pep-keysync}}) is a 
 decentralized proposition which defines how pEp users can distribute their
 private keys among their different devices in a user-authenticated manner.
 This allows users to read their messages across their various devices, as long