RFC 6120 on Extensible Messaging and Presence Protocol (XMPP): Core

rfc-editor@rfc-editor.org Wed, 30 March 2011 22:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 720EC3A6BE0; Wed, 30 Mar 2011 15:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.107
X-Spam-Level:
X-Spam-Status: No, score=-102.107 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PowTb6Q38rWV; Wed, 30 Mar 2011 15:31:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C8C2C3A67EE; Wed, 30 Mar 2011 15:31:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 30908E0763; Wed, 30 Mar 2011 15:32:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6120 on Extensible Messaging and Presence Protocol (XMPP): Core
From: rfc-editor@rfc-editor.org
Message-Id: <20110330223249.30908E0763@rfc-editor.org>
Date: Wed, 30 Mar 2011 15:32:49 -0700
Cc: xmpp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 22:31:20 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6120

        Title:      Extensible Messaging and Presence Protocol 
                    (XMPP): Core 
        Author:     P. Saint-Andre
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    psaintan@cisco.com
        Pages:      211
        Characters: 451942
        Obsoletes:  RFC3920

        I-D Tag:    draft-ietf-xmpp-3920bis-22.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6120.txt

The Extensible Messaging and Presence Protocol (XMPP) is an
application profile of the Extensible Markup Language (XML) that
enables the near-real-time exchange of structured yet extensible data
between any two or more network entities.  This document defines
XMPP's core protocol methods: setup and teardown of XML streams,
channel encryption, authentication, error handling, and communication
primitives for messaging, network availability ("presence"), and
request-response interactions.  This document obsoletes RFC 3920. 
[STANDARDS-TRACK]

This document is a product of the Extensible Messaging and Presence Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC