diff --git a/xep-0136.xml b/xep-0136.xml index 1af52707..ddc5e88e 100644 --- a/xep-0136.xml +++ b/xep-0136.xml @@ -16,6 +16,7 @@ XMPP Core XMPP IM + XEP-0004 XEP-0030 XEP-0059 XEP-0060 @@ -36,6 +37,12 @@ &stpeter; &infiniti; + + 0.12 + 2006-11-23 + ip +

All modes allow multiple body children of to and from elements; changed namespace and collection element name to chat; renamed all value of save attribute to message; added stream value of the save attribute, thread attribute, save wrapper element, and Linking Collections and Associating Attributes sections

 + 0.11 2006-11-06 @@ -121,17 +128,17 @@ ]]> -

For each feature defined herein, if the server supports that feature it MUST return a <feature/> element with the 'var' attribute set to 'http://jabber.org/protocol/archive#name', where 'name' is 'auto' for the Automated Archiving feature, 'encrypt' for the server-side encryption feature (see Automated Archiving), 'manage' for the Archive Management feature, 'manual' for the Manual Archiving feature, or 'pref' for the Archiving Preferences feature.

+

For each feature defined herein, if the server supports that feature it MUST return a <feature/> element with the 'var' attribute set to 'urn:xmpp:archive#name', where 'name' is 'auto' for the Automated Archiving feature, 'encrypt' for the server-side encryption feature (see Automated Archiving), 'manage' for the Archive Management feature, 'manual' for the Manual Archiving feature, or 'pref' for the Archiving Preferences feature.

... - - - - - + + + + + ... @@ -153,12 +160,12 @@

In order to determine its user's current Save Mode(s) and OTR Mode(s), a client sends an empty <pref/> element to its server:

- + ]]>

The server responds with the default Save Mode and OTR Mode (a single <default/> element) and any specific Save Modes and OTR Modes for individual contacts (zero or more <item/> elements).

-

Each <default/> or <item/> element in the response MUST include a 'save' attribute, whose value MAY be 'false' (the client MUST save no messages), 'body' (the client SHOULD save only <body/> elements) or 'all' (the client SHOULD save the full XML content of each &MESSAGE; element).

-

Note: Support for the 'all' value is optional and, to conserve bandwidth and storage space, it is RECOMMENDED that client implementations do not specify the 'all' value.

+

Each <default/> or <item/> element in the response MUST include a 'save' attribute, whose value MAY be 'false' (the saving entity MUST save nothing), 'body' (the saving entity SHOULD save only &BODY; elements), 'message' (the saving entity SHOULD save the full XML content of each &MESSAGE; element) or 'stream' (the saving entity SHOULD save every byte that passes over the stream in either direction). Note: The upload, retrieval and management of 'stream' archives is currently beyond the scope of this document.

+

Note: Support for the 'message' value is optional and, to conserve bandwidth and storage space, it is RECOMMENDED that client implementations do not specify the 'message' value. Stream compression typically does not mitigate bandwidth and storage issues since collections SHOULD be encrypted, and since clients running in constrained runtime environments typically cannot take advantage of stream compression (no binary data, only XML, may be transfered).

Note: When archiving locally a client MAY save the full XML content of each &MESSAGE; element even if the Save Mode is 'body'.

Each <default/> or <item/> element in the response whose 'save' attribute is not set to 'false' is RECOMMENDED to also include an 'expire' attribute which indicates how many seconds after messages are archived that the server SHOULD delete them.

Each <default/> or <item/> element in the response MUST include an 'otr' attribute, whose value MAY be 'require', 'prefer', 'approve', 'concede', 'oppose' or 'forbid'. The client MUST be guided by the specified 'otr' attribute value when negotiating (see &xep0155;) whether or not all messages exchanged with a contact will be Off The Record. Note: If the OTR Mode is 'require' then the Save Mode MUST be 'false'.

@@ -166,10 +173,10 @@

The server MUST also include an <auto/> element reflecting the current Automated Archiving settings for this stream.

- + - + @@ -180,7 +187,7 @@

If the user has never set the default Modes, the 'save' and 'otr' attributes SHOULD specify the server's default settings, and the 'unset' attribute SHOULD be set to 'true'. Note: The 'unset' attribute defaults to 'false'.

- + @@ -195,7 +202,7 @@

A client may set the default Modes:

- + @@ -207,28 +214,28 @@

The server then MUST inform all of the user's connected resources that have previously requested the user's archiving preferences:

- + - + ]]>

The server MAY be configured to return a <feature-not-implemented/> error in the following cases:

    -

  • If it does not allow the saving of full message stanza content, and the client set the value of the 'save' attribute to 'all', and any of the user's connected resources have Automated Archiving enabled.

    • -

  • If administrator policies require that at least the <body/> (or the full content) of every message is logged automatically, and the client sets the value of the 'save' attribute to 'false' (or 'body').

    • +

  • If it does not allow the saving of full message stanza content, and the client set the value of the 'save' attribute to 'message' or 'stream', and any of the user's connected resources have Automated Archiving enabled.

    • +

  • If administrator policies require that at least the <body/> elements (or the full content) of every message are logged automatically, and the client sets the value of the 'save' attribute to 'false' (or 'body').

A client may use a similar protocol to set the Modes for a particular contact or domain of contacts (bare JID, full JID or domain). Note: It is STRONGLY RECOMMENDED for the value of the 'jid' attribute to be a bare JID (&BAREJID;).

- + @@ -238,13 +245,13 @@ ]]> - + - + @@ -254,7 +261,7 @@ - + @@ -266,7 +273,7 @@ ]]> - + @@ -274,7 +281,7 @@ - + @@ -393,34 +400,39 @@
  • A client wants to maintain a unified archive for messages that were transmitted both in and out-of-band (e.g. SMS or email)
  • A client wants to append private notes to a conversation
    • -

    Therefore, often a client will want to send or receive a sequence of messages, optionally add private notes to the sequence, optionally encrypt the sequence, and then ask the server to store it. Such messages and notes SHOULD be stored on the server in the form of a "collection".

    +

    Therefore, often a client will want to send or receive a sequence of messages, optionally add private notes to the sequence, optionally encrypt the sequence, and then ask the server to archive it. Such messages and notes SHOULD be stored on the server in the form of a "collection".

    A "collection" is a set of messages to/from the same user that are received near each other in time or as part of the same conversation thread. A collection is intended to mimic the natural flow of human conversations, which in instant messaging (IM) systems tend to occur in bursts (e.g., a five-minute conversation one day, followed by a ten-minute conversation the next).

    +

    Each collection of messages and notes is encapsulated in a <chat/> element.

    The client uniquely specifies a collection using a pair of attributes:

    • 'with' (the full JID with which the messages were exchanged)
    • 'start' (the UTC start time of the conversation thread, which MUST be UTC and adhere to the DateTime format specified in &xep0082;)

    A friendly name for the collection MAY be specified with a 'subject' attribute. Note the Security Considerations regarding the subject attribute.

    +

    The opaque thread ID of the conversation (found in the &THREAD; children of the &MESSAGE; elements whose content is stored in the collection) MAY be specified with a 'thread' attribute.

    +

    Note: The content of &MESSAGE; elements that have different thread IDs SHOULD be archived in separate collections. The content of &MESSAGE; elements that have the same thread IDs SHOULD be archived in the same collection. The thread attribute SHOULD NOT be set to any value other than the exact content of the &THREAD; elements. If no &THREAD; elements appeared in the conversation the <chat/> element SHOULD have no thread attribute. Implementations SHOULD use the thread attribute for cross-referencing purposes only, within the archive each collection MUST be uniquely identified by the combination of its 'with' and 'start' attributes.

    Each collection MAY contain <note/>, <to/> or <from/> elements (or <EncryptedData/> and <EncryptedKey/> elements - see Encryption).

    The text of each individual private note MUST be encapsulated in a <note/> element. The absolute time the note was created SHOULD be specified with a 'utc' attribute (which MUST be UTC and adhere to the DateTime format specified in Jabber Date and Time Profiles).

    The content of each individual message MUST be encapsulated in a <to/> or <from/> element. The time in whole seconds of the message relative to the previous message in the collection (or, for the first message, relative to the start of the collection) SHOULD be specified with a 'secs' attribute. Note: When deciding whether to round up or down to a number of whole seconds, entities MUST ensure that the sum of the 'secs' attribute and the 'secs' attributes of the preceeding messages will accurately reflect the absolute time of the message. (e.g., if a sequence of messages occur at exactly 0.51-second intervals then the 'secs' attributes should generally alternate between '0' or '1'.)

    -

    The content of each <to/> or <from/> element SHOULD include a &BODY; element. Note: Other elements MAY be included, but they are NOT RECOMMENDED. To conserve bandwidth and storage space Stream compression typically does not mitigate bandwidth and storage issues since collections SHOULD be encrypted, and since clients running in constrained runtime environments typically cannot take advantage of stream compression (no binary data, only XML, may be transfered)., elements qualified by the 'http://jabber.org/protocol/xhtml-im' namespace SHOULD NOT be included. &THREAD; elements and elements qualified by the 'jabber:x:delay', 'jabber:x:event' and 'http://jabber.org/protocol/chatstates' namespaces MUST NOT be included. The server MAY be configured to return a <feature-not-implemented/> error if any <to/> or <from/> element contains anything other than a single &BODY; element.

    +

    The content of each <to/> or <from/> element SHOULD depend on the user's Archiving Preferences. <to/> or <from/> elements MUST NOT be empty. Note: A server MAY be configured to return a <feature-not-implemented/> error if any <to/> or <from/> element contains anything other than &BODY; elements.

     -

    The collection of messages and notes to be uploaded are encapsulated in the <store/> element.

    +

    A collection of messages and notes is uploaded to the server encapsulated in a <save/> element.

    - - Art thou not Romeo, and a Montague? - Neither, fair saint, if either thee dislike. - How cam'st thou hither, tell me, and wherefore? - I think she might fancy me. - + + + Art thou not Romeo, and a Montague? + Neither, fair saint, if either thee dislike. + How cam'st thou hither, tell me, and wherefore? + I think she might fancy me. + + ]]>

    If the collection does not exist then the server MUST create a new collection. If the collection already exists then the server MUST append the messages to the existing collection.

    @@ -428,12 +440,24 @@ ]]> -

    If the server cannot service a store request because the collection is too large then it MUST return a ¬acceptable; error:

    +

    If the server cannot service an upload request because the collection is too large then it MUST return a ¬acceptable; error:

    + + ]]> +     + +

    If the client specifies a new value for the 'subject' attribute of any existing collection then the server MUST update the existing value. Note: The client cannot specify new values for the 'with' or 'start' attributes. The only way to change these values is to delete the collection (see Removing a Collection) and then create a new one.

    + + + + ]]>     @@ -441,14 +465,15 @@

    The client MAY specify an absolute time for any message by providing a longer 'utc' attribute (which MUST be UTC and adhere to the DateTime format specified in Jabber Date and Time Profiles) instead of a 'secs' attribute. The absolute time MAY be before the start time of the collection:

    - - Art thou not Romeo, and a Montague? - Neither, fair saint, if either thee dislike. - How cam'st thou hither, tell me, and wherefore? - + + + Art thou not Romeo, and a Montague? + Neither, fair saint, if either thee dislike. + How cam'st thou hither, tell me, and wherefore? + + ]]>     @@ -456,24 +481,116 @@

    A client MAY archive messages that it receives from &xep0045; rooms. The 'with' attribute MUST be the bare JID of the room. The client MUST include a 'name' attribute for each <from/> element to specify the room nickname of the message sender:

    - - She will indite him to some supper. - A bawd, a bawd, a bawd! So ho! - What hast thou found? - + + + She will invite him to some supper. + A bawd, a bawd, a bawd! So ho! + What hast thou found? + + ]]> - -

    If the client specifies a new value for the 'subject' attribute of any existing collection then the server MUST update the existing value. Note: The client cannot specify new values for the 'with' or 'start' attributes. The only way to change these values is to delete the collection (see Removing a Collection) and then create a new one.

    - - + +

    Collections MAY be linked together by including a <previous/> and/or <next/> element. Each such element MUST include both a 'with' and a 'start' element to identify the other collection to which the collection is linked. For example, the <previous/> and <next/> elements in the two examples below are being used to link a groupchat between Romeo, Benvolio and Mercutio to a private chat that Romeo was having with Benvolio before they invited Mercutio to join them. Note: Collections MAY be linked in only one direction, they are not required to be double-linked in the way the examples below are.

    + + + + + O, I am fortune's fool! + Why dost thou stay? + + + + ]]> + + + + + She will invite him to some supper. + A bawd, a bawd, a bawd! So ho! + What hast thou found? + + + + ]]> +

    A collection MUST NOT contain more than one <previous/> and one <next/> element. If a <previous/> element is uploaded to a collection that already contains one then the older <previous/> element MUST be discarded. The same requirement applies for <next/> elements.

    +

    When a collection is retrieved (see Retrieving a Collection) the <previous/> and <next/> elements MUST appear as the first elements in the collection, whatever order they were uploaded in.

    +

    <previous/> and <next/> elements MAY be removed from a collection simply by uploading a <previous/> and/or <next/> element without any 'with' or 'start' attributes. Note: The server SHOULD NOT return an error if it finds that a link to be deleted does not exist.

    + + + + + + + + + ]]> +     + +

    A client MAY append attributes to a collection by including an x:data form of type 'submit' (see &xep0004;) when it uploads to a collection.

    +

    A collection MUST NOT contain more than one x:data form. If a form is uploaded to a collection that already contains one then the older form element MUST be discarded. When a collection is retrieved (see Retrieving a Collection) the x:data form MUST appear as the first element in the collection after any <previous/> or <next/> elements, whatever order it was uploaded in. Upon retrieval the 'type' attribute of the form MAY be 'submit' or 'form'.

    + + + + + urn:xmpp:archive + 1 + 1 + 1469-07-29T12:00:00Z + + O, I am fortune's fool! + Why dost thou stay? + + + + ]]> +

    The content of the uploaded x:data form MAY be encrypted (see Encryption).

    + + + + + + + + dataKey1 + + +OGQ0SR+ysraP6LnD43m77VkIVni5c7yPeIbkFdicZ + + + + dataKey1 + + + romeoPublicKey1fingerprint + + E5Qbvfa2gI5lBZMAHryv4g + + + + + ]]> +

    The x:data form MAY be removed from a collection simply by uploading an empty form. Note: The server SHOULD NOT return an error if it finds that the form to be deleted does not exist.

    + + + + + + ]]>     @@ -488,35 +605,36 @@

    Note: A collection that contains <EncryptedData/> or <EncryptedKey/> elements MUST NOT contain <to/> or <from/> or <note/> elements.

    - - - - - dataKey1 - - +OGQ0SR+ysraP6LnD43m77VkIVni5c7yPeIbkFdicZ - - - dataKey1 - - - romeoPublicKey1fingerprint - - E5Qbvfa2gI5lBZMAHryv4g - - - dataKey1 - - - romeoPublicKey2fingerprint - - E5Qbvfa2gI5lBZMAHryv4g - - + + + + + + dataKey1 + + +OGQ0SR+ysraP6LnD43m77VkIVni5c7yPeIbkFdicZ + + + dataKey1 + + + romeoPublicKey1fingerprint + + E5Qbvfa2gI5lBZMAHryv4g + + + dataKey1 + + + romeoPublicKey2fingerprint + + E5Qbvfa2gI5lBZMAHryv4g + + + ]]>

    The <CipherData/> child of each <EncryptedData/> element contains the base64-encoded symmetric-encrypted messages. The <EncryptionMethod/> and <KeyInfo/> children specify the symmetric encryption algorithm and the name of the symmetric key used to encrypt the messages.

    @@ -540,13 +658,13 @@

    Otherwise:

    • Automatic archiving MUST default to disabled when each stream is opened.
      • -
    • A client MAY enable or disable automatic archiving for messages sent over its stream at any time. Note: If the client switches off all auto-archiving then the server MUST close and store all active collections.
      • +
    • A client MAY enable or disable automatic archiving for messages sent over its stream at any time. Note: If the client switches off all auto-archiving then the server MUST close and archive all active collections.
    • Once automatic archiving is switched on then the server MUST automatically archive messages only according to the user's Archiving Preferences.
    • Note: Both parties to an ESession (see &xep0116;) SHOULD either disable archiving or use an archiving method other than automatic, since ESession decryption keys are short-lived - making it impossible to decrypt automatically archived messages.
    - + ]]>     @@ -558,7 +676,7 @@ + xmlns='urn:xmpp:archive'> romeoPublicKey3fingerprint @@ -574,12 +692,12 @@ ]]>     -

    As soon as the server has finished storing a collection, it MUST securely destroy all copies of the symmetric key it used to encrypt the messages. Note: If the security of the server is compromised, then only the collections being recorded during the attack will be revealed (i.e. only those messages that would have been compromised even if they had not been stored).

    +

    As soon as the server has finished archiving a collection, it MUST securely destroy all copies of the symmetric key it used to encrypt the messages. Note: If the security of the server is compromised, then only the collections being recorded during the attack will be revealed (i.e. only those messages that would have been compromised even if they had not been archived).

    The server MUST return a <feature-not-implemented/> error in the following cases:

      -

    • If the client is trying to enable automatic archiving, but the server does not allow the saving of full message stanza content, and the user has specified the 'all' Save Mode in one of its Archiving Preferences.

      • +

    • If the client is trying to enable automatic archiving, but the server does not allow the saving of full message stanza content, and the user has specified the 'message' Save Mode in one of its Archiving Preferences.

    • If administrator policies require that every message is logged automatically, and the client is trying to disable automatic archiving.

    • If the client is trying to enable encryption, but the server does not support encryption or the user did not specify a public key and is not publishing any keys using Public Key Publishing.

    @@ -599,7 +717,7 @@

    The client SHOULD use Result Set Management to limit the number of collections returned by the server in a single stanza, taking care not to request a page of collections that is so big it might exceed karma limits.

    - 30 @@ -609,7 +727,7 @@ ]]> - @@ -621,7 +739,7 @@ ]]> - 30 @@ -629,19 +747,19 @@ ]]> -

    The server MUST list the collections (empty <store/> elements including all attributes) in chronological order when responding to any request. If the collection contains <EncryptedData/> or <EncryptedKey/> elements then the 'crypt' attribute of the <store/> element MUST be set to 'true':

    +

    The server MUST list the collections (empty <chat/> elements including all attributes) in chronological order when responding to any request. If the collection contains <EncryptedData/> or <EncryptedKey/> elements then the 'crypt' attribute of the <chat/> element MUST be set to 'true':

    - - + + . [28 more collections] . - + 1469-07-21T02:56:15Zjuliet@capulet.com 1469-07-21T03:16:37Zbalcony@house.capulet.com @@ -654,12 +772,12 @@

    If no collections correspond to the request the server MUST return an empty <list/> element:

    - + ]]> - 30 @@ -675,7 +793,7 @@

    The client SHOULD use Result Set Management to limit the number of messages returned by the server in a single stanza, taking care not to request a page of messages that is so big it might exceed karma limits.

    - @@ -686,10 +804,10 @@ ]]> - + Art thou not Romeo, and a Montague? Neither, fair saint, if either thee dislike. . @@ -701,14 +819,14 @@ 99 217     -     +     ]]>

    Note: In accordance with Result Set Management, the client MUST assume the unique IDs it receives in the <first/> and <last/> elements are opaque. Servers MAY adopt a unique ID format other than the one suggested in the example above.

    If the specified collection does not exist then the server MUST return an ¬found; error:

    - @@ -720,18 +838,18 @@ ]]> -

    If the requested collection is empty the server MUST return an empty <store/> element:

    +

    If the requested collection is empty the server MUST return an empty <chat/> element:

    - + ]]> - @@ -744,7 +862,7 @@

    The items in encrypted collections are typically larger - since each <EncryptedData/> element typically contains many messages. So the client SHOULD take even more care not to request a page of <EncryptedData/> elements that is so big it might exceed karma limits.

    - @@ -756,10 +874,10 @@

    In addition to the requested <EncryptedData/> elements, the server MUST return all the <EncryptedKey/> elements that it possesses for the user whose symmetric key name (wrapped in its <CarriedKeyName/> child) is referenced by the <KeyName/> child of the <KeyInfo/> child of any of the <EncryptedData/> elements in the returned page.

    - + @@ -816,13 +934,13 @@ 4 7     - + ]]>

    The client MAY limit the number of <EncryptedKey/> elements that it receives by specifying the name of one or more public keys for which it holds the associated private keys. The name of each public key MUST be wrapped in a <KeyName/> element.

    - romeoPublicKey1fingerprint @@ -839,7 +957,7 @@

    To request the removal of a single collection the client sends an empty <remove/> element. The 'with' (full JID) and 'start' attributes MUST be included to uniquely identify the collection.

    - @@ -847,7 +965,7 @@

    The client may remove several collections at once. The 'start' and 'end' elements MAY be specified to indicate a date range. The 'with' attribute MAY be a full JID, bare JID or domain.

    - @@ -857,7 +975,7 @@

    If the end date is in the future then then all collections after the start date are removed.

    - @@ -865,34 +983,34 @@

    If the start date is before all the collections in the archive then all collections prior to the end date are removed.

    - ]]> - + ]]>

    If the value of the optional 'open' attribute is set to 'true' then only collections that are currently being recorded automatically by the server (see Automated Archiving) are removed.

    - ]]> - ]]>

    If the specified collection (or collections) do not exist then the server MUST return an ¬found; error:

    - @@ -907,7 +1025,7 @@

    The client first requests a list of the affected <EncryptedKey/> elements from all collections by sending a <keys/> element to the server:

    - + romeoPublicKey1fingerprint 50 @@ -918,9 +1036,9 @@

    The server MUST return only <EncryptedKey/> elements whose symmetric encryption key is encrypted with the obsolete public key specified in the <KeyName/> child of the request:

    - - + + dataKey1 @@ -937,7 +1055,7 @@ E5Qbvfa2gI5lBZMAHryv4g - + . [49 more sets of collection keys] . @@ -949,29 +1067,30 @@ ]]> -

    The client decrypts each symmetric key with the obsolete private key and encrypts it again with the new public key. The client then wraps each symmetric key in an <EncryptedKey/> element and asks the server to store it in its associated collection on the server (see Encryption):

    +

    The client decrypts each symmetric key with the obsolete private key and encrypts it again with the new public key. The client then wraps each symmetric key in an <EncryptedKey/> element and asks the server to archive it in its associated collection on the server (see Encryption):

    - - - dataKey1 - - - romeoPublicKey2fingerprint - - E5Qbvfa2gI5lBZMAHryv4g - - - dataKey2 - - - romeoPublicKey2fingerprint - - E5Qbvfa2gI5lBZMAHryv4g - - + + + + dataKey1 + + + romeoPublicKey2fingerprint + + E5Qbvfa2gI5lBZMAHryv4g + + + dataKey2 + + + romeoPublicKey2fingerprint + + E5Qbvfa2gI5lBZMAHryv4g + + + . [49 more sets of collection keys] @@ -980,9 +1099,9 @@

    Finally, the client asks the server to delete from each collection all <EncryptedKey/> elements whose symmetric encryption key is encrypted with the obsolete public key:

    - + romeoPublicKey1fingerprint @@ -998,7 +1117,7 @@ - + 50 1469-07-21T01:14:47Z @@ -1009,9 +1128,9 @@

    The server MUST return the changed collections in the chronological order that they were changed (most recent last). If a collection has been modified, created or removed after the time specified by the <after/> element then the server MUST include it in the returned result set page of collections (unless the specified maximum page size would be exceeded). Each <changed/> or <removed/> collection element (for modified/created, or removed collections respectively) in the returned list MUST include only 'with' and 'start' attribues. The server MUST set the content of the <last/> element to the UTC time (see Jabber Date and Time Profiles) that the last collection on the page was modified.

    - + + start='1469-07-21T02:56:15Z'/> . [up to 48 more collections] . @@ -1025,31 +1144,31 @@ ]]>

    Note: The server should remember the 'with' and 'start' attribues and the time of removal of all deleted collections. If this 'state' cannot be maintained indefinitely, then unless all the user's clients replicate before the server deletes its memory of a removal then it will not be reflected in all the local copies of the archive.

    -

    Note: Along with its copy of the archive the client SHOULD store the most recent <last/> time that it received from the server. The next time it synchronizes with the server it SHOULD specify that time when requesting the first result set page (see above).

    +

    Note: Along with its copy of the archive the client SHOULD save the most recent <last/> time that it received from the server. The next time it synchronizes with the server it SHOULD specify that time when requesting the first result set page (see above).

    After receiving each result set page the client SHOULD delete from its local archive any collections that have been removed from the master archive. The client should also retrieve from the server the content of each collection that has been modified (see Retrieving a Collection) and add it to its local copy of the archive (deleting any older version of the same collection that it may already have).

    Note the file format specified in this section is likely to be deprecated once a standards-based format has been published in a separate specification.

    -

    So that clients can share archived messages, this document specifies a common format for storage on disk (similar to email formats like mbox and Maildir). The file format uses the same XML constructs as the protocol. Each file may contain messages exchanged with a single JID. Any number of items may be stored in an archive file.

    +

    So that clients can share archived messages, this document specifies a common format for storage on disk (similar to email formats like mbox and Maildir). The file format uses the same XML constructs as the protocol. Each file may contain messages exchanged with a single JID. Any number of <chat/> elements may be stored in an archive file.

    - - + Art thou not Romeo, and a Montague? Neither, fair saint, if either thee dislike. How cam'st thou hither, tell me, and wherefore? - + ]]>     -

    When creating a new collection, it is RECOMMENDED that the client synchronizes the collection start time that it sends to the server with server time. This is important since the user may subsequently retrieve the stored collection using client machines whose UTC clocks are not synchronized with the client machine that stored the collection. (i.e. Either or both of the clients' UTC clocks may be wrong.) The client can achieve this synchronization with server time by using &xep0090; to estimate the difference between the server and client UTC clocks.

    +

    When creating a new collection, it is RECOMMENDED that the client synchronizes the collection start time that it sends to the server with server time. This is important since the user may subsequently retrieve the archived collection using client machines whose UTC clocks are not synchronized with the client machine that uploaded the collection. (i.e. Either or both of the clients' UTC clocks may be wrong.) The client can achieve this synchronization with server time by using &xep0090; to estimate the difference between the server and client UTC clocks.

    When retrieving collections, it is RECOMMENDED that the client adjusts the start times of the collections it receives from server to be synchronized with the clock of the client machine.

     -

    When uploading messages using manual archiving, a client SHOULD NOT store one message at a time on the server since this increases both bandwidth consumption and the total number of transactions. It is instead RECOMMENDED that clients store messages only when the conversation thread appears to be terminated, e.g. when the user closes the chat window. If the user reopens the window and the thread continues then the client should append the new messages to the collection when the user closes the window again.

    +

    When uploading messages using manual archiving, a client SHOULD NOT upload one message at a time on the server since this increases both bandwidth consumption and the total number of transactions. It is instead RECOMMENDED that clients upload messages only when the conversation thread appears to be terminated, e.g. when the user closes the chat window. If the user reopens the window and the thread continues then the client should append the new messages to the collection when the user closes the window again.

    Server implementations SHOULD give system administrators the option to disable support for both automated and manual archiving, since archived conversations can consume significant storage space.

    @@ -1073,18 +1192,43 @@     -

    The ®ISTRAR; shall include 'http://jabber.org/protocol/archive' in its registry of protocol namespaces (see &NAMESPACES;):

    +

    The ®ISTRAR; shall include 'urn:xmpp:archive' in its registry of protocol namespaces (see &NAMESPACES;):

    The XMPP Registrar shall include the following features in its registry of service discovery features (see &DISCOFEATURES;):

      -
    • http://jabber.org/protocol/archive#auto
      • -
    • http://jabber.org/protocol/archive#encrypt
      • -
    • http://jabber.org/protocol/archive#manage
      • -
    • http://jabber.org/protocol/archive#manual
      • -
    • http://jabber.org/protocol/archive#pref
      • +
    • urn:xmpp:archive#auto
      • +
    • urn:xmpp:archive#encrypt
      • +
    • urn:xmpp:archive#manage
      • +
    • urn:xmpp:archive#manual
      • +
    • urn:xmpp:archive#pref
     + +

    &xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace. The following fields shall be registered for use in Message Archiving:

    + + urn:xmpp:archive + XEP-0136 + Attributes of a message collection + + + + + ]]> +     @@ -1102,6 +1246,7 @@ herein are: - archive - auto + - chat - delete - keys - list @@ -1109,14 +1254,14 @@ - pref - remove - retrieve - - store + - save - + @@ -1143,6 +1288,42 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -1163,9 +1344,10 @@ - + + @@ -1206,9 +1388,10 @@ - + + @@ -1220,7 +1403,7 @@ - + @@ -1229,7 +1412,7 @@ - + @@ -1322,30 +1505,14 @@ - + - - - - - - - - - - + + + - - - - - - - - -