xmpp 之Jabber
Contents
翻译注意事项
xmpp 的协议是非常宠大的，为了使多个人同时参加，请在你想要翻译的章或节上写下自已的名字，格式为名字，如果该章或节上有人 打上标记了请不要再翻译了，当你翻译后，请将自已的名字去掉。每个人参与翻译的人请在该文章的翻译者栏下写下自已的名字。谢谢。
- run mei
这个计划很长时间，没有动过了，我会在10月份后，继续下去，有路过的希望加入，我有英文不好，看到错误请不要发笑，请你改正它吧！
- run mei
好长时间没有来了，本来说要在10月份继续的，可等到今天才开始。
- run mei
翻译者
run mei
shhgs
Jabber :: Protocols
The Jabber/XMPP protocols have evolved through an open design process within the Jabber and broader Internet communities since 1999. The base protocols have been approved by the Internet Engineering Task Force (IETF) under the name Extensible Messaging and Presence Protocol (XMPP), and various XMPP extensions continue to be defined in the Jabber Software Foundation's JEP series.
Base Protocols (XMPP RFCs)
The base XML protocols developed by the Jabber community in 1999 were contributed by the Jabber Software Foundation to the Internet Standards Process in 2002. After work by the XMPP WG in the areas of privacy, security, and internationalization, these protocols were approved by the IETF in October 2004 as RFCs 3920 and 3921:
RFC_3920草稿: Extensible Messaging and Presence Protocol (XMPP): Core -- The core XML streaming technology that powers Jabber applications, including advanced security and internationalization support
RFC_3921未开始: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence -- Basic IM and presence extensions, including contact lists, presence subscriptions, and whitelisting/blacklisting
In addition, the XMPP WG independently developed the following two RFCs:
RFC_3922未开始: Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM) -- A mapping of XMPP to the IETF's abstract syntax for IM and presence
RFC_3923未开始: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) -- An extension for interoperable, end-to-end security
More complete information about XMPP, including online versions of the XML schemas, is available at xmpp.org.
2.0 XMPP Extensions (JEPs)
Since mid-2001, the JSF has managed the Jabber protocols through an open standards process focused on the discussion and approval of Jabber Enhancement Proposals (JEPs). Standards Track JEPs may be considered XMPP extensions (though they are not part of XMPP itself, which is all and only the specifications produced by the IETF's XMPP WG).
The remainder of this page summarizes the JEPs that have advanced beyond a status of Experimental within the JSF.
2.1 Final JEPs
The protocols defined in the following Standards Track JEPs have been approved as Final standards by the Jabber Software Foundation:
JEP-0004: Data Forms
JEP-0009: Jabber-RPC
JEP-0030: Service Discovery
JEP-0077: In-Band Registration
JEP-0078: Non-SASL Authentication
2.2 Draft JEPs
The protocols defined in the following Standards Track JEPs have been approved as Draft standards by the Jabber Software Foundation, but have not yet received final approval:
JEP-0013: Flexible Offline Message Retrieval
JEP-0020: Feature Negotiation
JEP-0033: Extended Stanza Addressing
JEP-0045: Multi-User Chat
JEP-0047: In-Band Bytestreams
JEP-0050: Ad-Hoc Commands
JEP-0060: Publish-Subscribe
JEP-0065: SOCKS5 Bytestreams
JEP-0071: XHTML-IM
JEP-0073: Basic IM Protocol Suite
JEP-0079: Advanced Message Processing
JEP-0080: User Geolocation
JEP-0095: Stream Initiation
JEP-0096: File Transfer
JEP-0106: JID Escaping
JEP-0107: User Mood
JEP-0108: User Activity
JEP-0112: User Physical Location
JEP-0115: Entity Capabilities
JEP-0118: User Tune
JEP-0122: Data Forms Validation
JEP-0124: HTTP Binding
JEP-0131: Stanza Headers and Internet Metadata (SHIM)
JEP-0138: Stream Compression
JEP-0141: Data Forms Layout
2.3 Informational JEPs
The following Informational JEPs define protocol best practices and protocol usage profiles:
JEP-0068: Field Standardization for Data Forms
JEP-0082: Jabber Date and Time Profiles
JEP-0083: Nested Roster Groups
JEP-0086: Error Condition Mappings
JEP-0126: Invisibility
JEP-0127: Common Alerting Protocol (CAP) Over XMPP
JEP-0128: Service Discovery Extensions
JEP-0133: Service Administration
JEP-0134: Protocol Design Guidelines
2.4 Historical JEPs
The following Historical JEPs describe protocols that are in wide use within the Jabber community but that are not official Jabber protocols. Although these documents have a status of Active, they are not standards track within the JSF and may be superseded by standards-track protocols or converted to standards track by the Jabber Council.
JEP-0003: Proxy Accept Socket Service (PASS)
JEP-0012: Last Activity
JEP-0022: Message Events
JEP-0023: Message Expiration
JEP-0025: Jabber HTTP Polling
JEP-0027: Current OpenPGP Usage
JEP-0048: Bookmark Storage
JEP-0049: Private XML Storage
JEP-0054: vcard-temp
JEP-0055: Jabber Search
JEP-0066: Out of Band Data
JEP-0090: Entity Time
JEP-0091: Delayed Delivery
JEP-0092: Software Version
JEP-0093: Roster Item Exchange
JEP-0114: Jabber Component Protocol
2.5 Procedural JEPs
The following Procedural JEPs define organizational procedures and activities of the Jabber Software Foundation:
JEP-0001: Jabber Enhancement Proposals
JEP-0002: Jabber Interest Groups
JEP-0053: Jabber Registrar
JEP-0143: Guidelines for JEP Authors
2.6 Humorous JEPs
The following JEPs have been published on April Fool's Day. They may provide amusement but should not be taken seriously.
JEP-0076: Malicious Stanzas
JEP-0132: Presence Obtained via Kinesthetic Excitation (POKE)
JEP-0148: Instant Messaging Intelligence Quotient (IM IQ)
反馈
::-- ZoomQuiet [2005-07-05 02:01:22]