[XCON] Conference Focus Indicating CCMP Support

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Mon, 24 January 2011 19:34 UTC

Return-Path: <rifatyu@avaya.com>
X-Original-To: xcon@core3.amsl.com
Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 371AA3A6B35 for <xcon@core3.amsl.com>; Mon, 24 Jan 2011 11:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 9ypc-V1GL+Ef for <xcon@core3.amsl.com>; Mon, 24 Jan 2011 11:34:58 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 4E3B53A6B24 for <xcon@ietf.org>; Mon, 24 Jan 2011 11:34:58 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAG9jPU2HCzI1/2dsb2JhbACEE59ra3OiegKIM5BAgSSDOHQEhHCJcIJe
X-IronPort-AV: E=Sophos;i="4.60,371,1291611600"; d="scan'208";a="55817806"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 24 Jan 2011 14:37:53 -0500
X-IronPort-AV: E=Sophos;i="4.60,371,1291611600"; d="scan'208";a="587735980"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Jan 2011 14:37:23 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 24 Jan 2011 14:37:22 -0500
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "xcon@ietf.org" <xcon@ietf.org>
Date: Mon, 24 Jan 2011 14:37:22 -0500
Thread-Topic: Conference Focus Indicating CCMP Support
Thread-Index: Acu76WqZ1OEMYg6gTpaCQx/prArkhQAE59RA
Message-ID: <6369CB70BFD88942B9705AC1E639A33822090708DA@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Alan Johnston <alan.b.johnston@gmail.com>
Subject: [XCON] Conference Focus Indicating CCMP Support
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 24 Jan 2011 19:34:59 -0000

Hi Alan, Richard,

Mary and I have submitted the following draft that deals with a conference focus indicating support for CCMP.
https://datatracker.ietf.org/doc/draft-yusef-xcon-ccmp-indication/

Can this work be discussed in the XCON or do we have to go to the DISPATCH for this?

We would appreciate any comments on this document.

Regards,
 Rifaat



> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Monday, January 24, 2011 12:05 PM
> To: Shekh-Yusef, Rifaat (Rifaat)
> Cc: mary.ietf.barnes@gmail.com
> Subject: New Version Notification for draft-yusef-xcon-ccmp-indication-00
> 
> 
> A new version of I-D, draft-yusef-xcon-ccmp-indication-00.txt has been
> successfully submitted by Rifaat Shekh-Yusef and posted to the IETF
> repository.
> 
> Filename:	 draft-yusef-xcon-ccmp-indication
> Revision:	 00
> Title:		 Conference Focus Indicating CCMP Support
> Creation_date:	 2011-01-24
> WG ID:		 Independent Submission
> Number_of_pages: 8
> 
> Abstract:
> The Centralized Conferencing Manipulation Protocol document defines a
> way for a client to discover a conference control server that
> supports CCMP. However, it does not define a way for a client to
> discover if a conference focus supports CCMP.
> 
> This draft describes few options to address the above limitation with
> the pros and cons for each approach.
> 
> 
> 
> The IETF Secretariat.
>