diff --git a/xep-0373.xml b/xep-0373.xml index 92884b68..4cad2eed 100644 --- a/xep-0373.xml +++ b/xep-0373.xml @@ -18,7 +18,7 @@ devices. &LEGALNOTICE; 0373 - Deferred + Experimental Standards Track Standards Council @@ -46,6 +46,18 @@ look@my.amazin.horse valodim@stratum0.org + + 0.5.0 + 2020-06-19 + fs + + + + 0.4.0 2018-07-30 @@ -161,8 +173,9 @@
Public-Key metadata node ("metadata node")
A PEP node containing metadata of the entity's public OpenPGP key.
Public-Key data node ("data node")
A PEP node containing an entity's public OpenPGP key.
Secret-Key node
A PEP node containing an entity's encrypted secret OpenPGP key.
 -
OpenPGP v4 Fingerprint String
A String representing the OpenPGP v4 fingerprint of a key. If the key consists of a master key and subkeys, this is the fingerprint of the -master key.
 +
OpenPGP v4 Fingerprint String
A String representing the OpenPGP v4 fingerprint + of a key. If the key consists of a primary key and subkeys, this is the fingerprint of the + primary key.
 @@ -318,17 +331,19 @@ master key. encoded as a hexadecimal string using upper case charactersThis matches the representation used by GnuPG minus the SPACE separation..

+

The publishing entity SHOULD set the PubSub item ID to the time the item is published encoded + as DateTime format specified in XEP-0082.

+

The data node MUST contain an <pubkey/> element qualified by the 'urn:xmpp:openpgp:0' - namespace. An optional 'date' attribute holds the information about the last modification of the - key as DateTime format of XEP-0082. The element MUST include a <data/> - element which contains the data of the key Base64 encoded.

+ namespace. The element MUST include a <data/> element which contains the data of the key + Base64 encoded.

- - + + BASE64_OPENPGP_PUBLIC_KEY @@ -377,8 +392,9 @@ master key. -

In order to discover the OpenPGP public keys, the interested entity first queries a remote - entities metadata note to learn about its currently annouced OpenPGP keys.

+

In order to discover the OpenPGP public keys of a remote entity, the interested entity first + queries the remote entity's metadata note to learn about the currently annouced OpenPGP + keys.

id='getpub'> - + BASE64_OPENPGP_PUBLIC_KEY @@ -466,9 +482,14 @@ master key. +

Entities creating PEP nodes defined herein SHOULD configure the nodes as notification-only + nodes by setting 'pubsub#deliver_payloads" configuration field to 'false'.

+

Entities which are subscribed to the metadata node or advertise the - "urn:xmpp:openpgp:0:public-keys+notify" feature via &xep0115; (see XEP-0060 § 9.2) - receive a notification upon a node update.

+ "urn:xmpp:openpgp:0:public-keys+notify" feature via &xep0030; (see XEP-0060 § 9.2) receive a + notification upon a node update. Entities subscribed to PEP nodes defined herein MUST be prepared + that PubSub notifications may be without the payload and only contain the published item's ID.

 @@ -659,7 +680,11 @@ master key. be concatenated in their transferable key format (RFC 4880 § - 11.2). + 11.1). The octet indicating string-to-key usage conventions + MUST be set to zero in the corresponding Secret-Key Packet(s) + (RFC 4880 § 5.5.3). + The secret key material will be encrypted in step 4 using a + Symmetric-Key Encrypted Session Key Packet.
  • A backup code is generated from secure random: The backup code consists of 24 upper case characters from the Latin @@ -936,7 +961,8 @@ master key.

    Thanks to Emmanuel Gil Peyrot, Sergei Golovan, Marc Laporte, Georg - Lukas, Adithya Abraham Philip, Brian Cully, fiaxh and Paul Schaub for their feedback.

    + Lukas, Adithya Abraham Philip, Brian Cully, fiaxh, Paul Schaub, + Philipp Hörist and Stefan Kropp for their feedback.

    The first draft of this specification was worked out and written on the wall of the 'Kymera' room in one of Google's buildings by the