[XCON] RFC 6502 on Conference Event Package Data Format Extension for Centralized Conferencing (XCON)

rfc-editor@rfc-editor.org Sat, 24 March 2012 18:14 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xcon@ietfa.amsl.com
Delivered-To: xcon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469C421F85EE; Sat, 24 Mar 2012 11:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.159
X-Spam-Level:
X-Spam-Status: No, score=-102.159 tagged_above=-999 required=5 tests=[AWL=-0.159, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCFAWuIiSaqJ; Sat, 24 Mar 2012 11:14:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id CD0C121F85E0; Sat, 24 Mar 2012 11:14:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 247B072ECEA; Sat, 24 Mar 2012 11:13:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120324181323.247B072ECEA@rfc-editor.org>
Date: Sat, 24 Mar 2012 11:13:23 -0700 (PDT)
Cc: xcon@ietf.org, rfc-editor@rfc-editor.org
Subject: [XCON] RFC 6502 on Conference Event Package Data Format Extension for Centralized Conferencing (XCON)
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xcon>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2012 18:14:34 -0000

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

        
        RFC 6502

        Title:      Conference Event Package Data Format 
                    Extension for Centralized Conferencing (XCON) 
        Author:     G. Camarillo, S. Srinivasan,
                    R. Even, J. Urpalainen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2012
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    srivatsa.srinivasan@gmail.com, 
                    ron.even.tlv@gmail.com,  jari.urpalainen@nokia.com
        Pages:      14
        Characters: 26245
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xcon-event-package-01.txt

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

   This document specifies the notification mechanism for XCON
   (centralized conferencing).  This mechanism reuses the SIP (Session
   Initiation Protocol) event package for conference state.
   Additionally, the notification mechanism includes support for the
   XCON data model and for partial notifications.


This document is a product of the Centralized Conferencing 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