xmpp 之Jabber

2007-10-30可愛的Py 图书工程重启倡议; 2008-03-30可爱的Python编辑约定


{o} DiP

(!) Py食谱

{*} OBP/列表

(!) 博文出版>可爱Py

{*} CDBE

090827ZoomQuiet 关闭主要内部的浏览权限,开始半年期的图书发售沉默期!重开日期:100227



xmpp 的协议是非常宠大的,为了使多个人同时参加,请在你想要翻译的章或节上写下自已的名字,格式为名字,如果该章或节上有人 打上标记了请不要再翻译了,当你翻译后,请将自已的名字去掉。每个人参与翻译的人请在该文章的翻译者栏下写下自已的名字。谢谢。




run mei


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:

In addition, the XMPP WG independently developed the following two RFCs:

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:

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:

2.3 Informational JEPs

The following Informational JEPs define protocol best practices and protocol usage profiles:

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.

2.5 Procedural JEPs

The following Procedural JEPs define organizational procedures and activities of the Jabber Software Foundation:

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.


::-- ZoomQuiet [2005-07-05 02:01:22]


JabberOrg (last edited 2009-12-25 07:14:33 by localhost)