No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0218.xml 5.2KB

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Bootstrapping Implementation of Encrypted Sessions</title>
  10. <abstract>This document provides guidelines to client and library developers for bootstrapping implementation of the encrypted sessions technology.</abstract>
  12. <number>0218</number>
  13. <status>Deferred</status>
  14. <type>Informational</type>
  15. <sig>Standards</sig>
  16. <approver>Council</approver>
  17. <dependencies>
  18. <spec>XMPP Core</spec>
  19. <spec>XEP-0116</spec>
  20. <spec>XEP-0155</spec>
  21. <spec>XEP-0200</spec>
  22. <spec>XEP-0201</spec>
  23. </dependencies>
  24. <supersedes/>
  25. <supersededby/>
  26. <shortname>N/A</shortname>
  27. &stpeter;
  28. &ianpaterson;
  29. <revision>
  30. <version>0.1</version>
  31. <date>2007-05-30</date>
  32. <initials>psa</initials>
  33. <remark><p>Initial published version.</p></remark>
  34. </revision>
  35. <revision>
  36. <version>0.0.1</version>
  37. <date>2007-05-29</date>
  38. <initials>psa/ip</initials>
  39. <remark><p>First draft.</p></remark>
  40. </revision>
  41. </header>
  42. <section1 topic='Introduction' anchor='intro'>
  43. <p>The &XSF; has defined a technology for end-to-end encryption of XMPP communications, called "Encrypted Sessions" (ESessions). This document describes ways for client and library developers to approach the task of implementing ESessions.</p>
  44. <p>In essence, implementation of ESessions proceeds in two directions:</p>
  45. <ol>
  46. <li>From the client/interface level down.</li>
  47. <li>From the library/API level up.</li>
  48. </ol>
  49. <p>If client developers implement the "frontend" specifications, they should be able to integrate the "backend" code developed by library developers, enabling the two sets of developers to "meet in the middle" and offer complete implementations.</p>
  50. </section1>
  51. <section1 topic='Approach' anchor='approach'>
  52. <p>When working from the client/interface level down to the library/API level, it makes sense to implement the relevant specifications in the following order:</p>
  53. <ol>
  54. <li>
  55. <p>&xep0201;</p>
  56. <p>This document describes what a "stanza session" is, i.e., it is defined by the life of a message thread. Clients that implement this specification are well on their way to implementing encrypted sessions, since it is necessary to have a clear session "object" in a client before implementing an encrypted version of such a session.</p>
  57. </li>
  58. <li>
  59. <p>&xep0155;</p>
  60. <p>Because this document describes how to negotiate a stanza session, it is a building block for developing how to negotiate an encrypted stanza session.</p>
  61. </li>
  62. <li>
  63. <p>&xep0200;</p>
  64. <p>By hardcoding the initial parameters during an early phase of development, implementors can use this specification as a starting point for testing of encrypted sessions. A later phase would address rekeying (Section 9) and negotiation of the initial parameters (see below).</p>
  65. </li>
  66. <li>
  67. <p>&xep0217;</p>
  68. <p>This specification (to be published concurrently) defines a simple subset of the process for negotiating the initial parameters used in an encrypted session.</p>
  69. </li>
  70. <li>
  71. <p>&xep0116;</p>
  72. <p>This specification defines the "heavy lifting" involved in going from a cleartext state to an encrypted state, i.e., it specifies how to the initial parameters for an encrypted session.</p>
  73. </li>
  74. <li>
  75. <p>&xep0188;</p>
  76. <p>Strictly speaking, a developer does not implement this specification, since it describes the theory behind the process of upgrading from cleartext to encryption that is defined in <cite>XEP-0116</cite>. However it is useful background knowledge for developers who implement <cite>XEP-0116</cite>.</p>
  77. </li>
  78. </ol>
  79. <p>Naturally, when developing from the library/API level up to the client/interface level, the order should be (roughly) reversed.</p>
  80. </section1>
  81. <section1 topic='Optional Add-Ons' anchor='addons'>
  82. <p>Once a library or client has implemented the specifications listed above, it may choose to implement the following additional specifications, which supplemented the core encrypted sessions specifications.</p>
  83. <ol>
  84. <li>
  85. <p>&xep0189;</p>
  86. <p>This specification defines a precondition for implementation of the specifications that follow.</p>
  87. </li>
  88. <li>
  89. <p>&xep0187;</p>
  90. <p>We should be able to encrypt so-called "offline messages" (see &xep0160;) using the same basic principles used to encrypted messages sent while online.</p>
  91. </li>
  92. <li>
  93. <p>&xep0136;</p>
  94. <p>This specification enables secure archiving of the messages sent and received in an encrypted session.</p>
  95. </li>
  96. </ol>
  97. </section1>
  98. <section1 topic='Security Considerations' anchor='security'>
  99. <p>Incomplete implementations of the Encrypted Sessions technology will not have the same security properties as complete implementations.</p>
  100. </section1>
  101. <section1 topic='IANA Considerations' anchor='iana'>
  102. <p>This document requires no interaction with &IANA;.</p>
  103. </section1>
  104. <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
  105. <p>This document requires no interaction with the &REGISTRAR;.</p>
  106. </section1>
  107. </xep>