Editing Список расширений/0001—0049
From JaWiki (Jabber/XMPP wiki)
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: MediaWiki upgrading
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 33: | Line 33: | ||
{{XepListItem|0029|Definition of Jabber Identifiers (JIDs)|This document defines the exact nature of a Jabber Identifier (JID). |||Standards_Track|Retracted}} | {{XepListItem|0029|Definition of Jabber Identifiers (JIDs)|This document defines the exact nature of a Jabber Identifier (JID). |||Standards_Track|Retracted}} | ||
{{XepListItem|0030|Service Discovery|This specification defines an XMPP protocol extension for discovering information about other XMPP entities. Two kinds of information can be discovered: (1) the identity and capabilities of an entity, including the protocols and features it supports; and (2) the items associated with an entity, such as the list of rooms hosted at a multi-user chat service.|||Standards_Track|Final}} | {{XepListItem|0030|Service Discovery|This specification defines an XMPP protocol extension for discovering information about other XMPP entities. Two kinds of information can be discovered: (1) the identity and capabilities of an entity, including the protocols and features it supports; and (2) the items associated with an entity, such as the list of rooms hosted at a multi-user chat service.|||Standards_Track|Final}} | ||
| − | {{XepListItem|0031|A Framework For Securing Jabber Conversations|Although the value and utility of contemporary instant messaging systems, like Jabber, are now indisputable, current security features to protect message data are generally inadequate for many deployments; this is particularly true in security conscious environments like large, commercial enterprises and government agencies. These current features suffer from issues of scalability, usability, and supported features. Furthermore, there is a lack of standardization. | + | {{XepListItem|0031|A Framework For Securing Jabber Conversations| |
| + | Although the value and utility of contemporary instant messaging | ||
| + | systems, like Jabber, are now indisputable, current security | ||
| + | features to protect message data are generally inadequate for | ||
| + | many deployments; this is particularly true in security conscious | ||
| + | environments like large, commercial enterprises and government | ||
| + | agencies. These current features suffer from issues of | ||
| + | scalability, usability, and supported features. Furthermore, there is a | ||
| + | lack of standardization. | ||
| + | |||
| + | We present a protocol to allow communities of Jabber users to | ||
| + | apply cryptographic protection to selected conversation data. | ||
| + | |||Standards_Track|Deferred}} | ||
{{XepListItem|0032|Jabber URI Scheme|A URI scheme for Jabber communications.|||Standards_Track|Retracted}} | {{XepListItem|0032|Jabber URI Scheme|A URI scheme for Jabber communications.|||Standards_Track|Retracted}} | ||
{{XepListItem|0033|Extended Stanza Addressing|This specification defines an XMPP protocol extension that enables entities to include RFC822-style address headers within XMPP stanzas in order to specify multiple recipients or sub-addresses.|||Standards_Track|Draft}} | {{XepListItem|0033|Extended Stanza Addressing|This specification defines an XMPP protocol extension that enables entities to include RFC822-style address headers within XMPP stanzas in order to specify multiple recipients or sub-addresses.|||Standards_Track|Draft}} | ||
