
From root@core3.amsl.com  Fri Jul  2 11:00:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7B3963A6933; Fri,  2 Jul 2010 11:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100702180002.7B3963A6933@core3.amsl.com>
Date: Fri,  2 Jul 2010 11:00:02 -0700 (PDT)
Cc: xcon@ietf.org
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-09.txt
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: Fri, 02 Jul 2010 18:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Centralized Conferencing Working Group of the IETF.


	Title           : Centralized Conferencing Manipulation Protocol
	Author(s)       : M. Barnes, et al.
	Filename        : draft-ietf-xcon-ccmp-09.txt
	Pages           : 109
	Date            : 2010-07-02

The Centralized Conferencing Manipulation Protocol (CCMP) allows an
XCON conferencing system client to create, retrieve, change, and
delete objects that describe a centralized conference.  CCMP is a
means to control basic and advanced conference features such as
conference state and capabilities, participants, relative roles, and
details.  CCMP is a state-less, XML-based, client server protocol
that carries, in its request and response messages, conference
information in the form of XML documents and fragments conforming to
the centralized conferencing data model schema.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-ccmp-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xcon-ccmp-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-02105151.I-D@ietf.org>


--NextPart--

From spromano@unina.it  Fri Jul  2 11:05:56 2010
Return-Path: <spromano@unina.it>
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 BC65B3A6813 for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 11:05:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.425
X-Spam-Level: *
X-Spam-Status: No, score=1.425 tagged_above=-999 required=5 tests=[AWL=-0.456,  BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 dmhFfFfp6ZPY for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 11:05:55 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 77D073A6843 for <xcon@ietf.org>; Fri,  2 Jul 2010 11:05:55 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o62I65Lj014802 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 2 Jul 2010 20:06:05 +0200
Message-ID: <4C2E2A89.90604@unina.it>
Date: Fri, 02 Jul 2010 20:06:01 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: xcon@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [XCON] New version of the CCMP draft
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: Fri, 02 Jul 2010 18:05:56 -0000

Dear all,

I just uploaded a brand new version of the CCMP draft, containing the 
following new items:

    1.  Added a section on the extendedRequest/extendedResponse message
        pair.
    2.  Added a section on the optionsRequest/optionsResponse message
        pair.
    3.  Added an example sub-section about the use of the optionsRequest/
        optionsResponse message pair.
    4.  Added an example sub-section about the use of the
        extendedRequest/extendedResponse message pair.
    5.  Updated the schema in order to reflect the latest modifications
        and add-ons.
    6.  Misc editorial nits...

As far as we are concerned, the draft is now complete!

Cheers,

Simon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From spromano@unina.it  Fri Jul  2 11:10:04 2010
Return-Path: <spromano@unina.it>
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 F1A3F28C14D for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 11:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.182
X-Spam-Level: 
X-Spam-Status: No, score=0.182 tagged_above=-999 required=5 tests=[AWL=0.901,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 nx47ZbmlwKGE for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 11:10:02 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by core3.amsl.com (Postfix) with ESMTP id 787B93A67B5 for <xcon@ietf.org>; Fri,  2 Jul 2010 11:10:01 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.0/8.14.0) with ESMTP id o62IACh2014890 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 2 Jul 2010 20:10:12 +0200
Message-ID: <4C2E2B80.3060404@unina.it>
Date: Fri, 02 Jul 2010 20:10:08 +0200
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: xcon@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [XCON] New version of the XCON call flows draft
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: Fri, 02 Jul 2010 18:10:04 -0000

Dear all,

the latest version of the XCON call flows draft has just been submitted. 
It is 100% aligned with the CCMP draft, version -09.

We are done with this work item, too!

It would be great if the WG were able to dedicate some cycles to the 
fast review of this document (and of the CCMP draft as well), so to 
arrive at a successful completion of its mandate as soon as possible.

Cheers,

Simon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



From root@core3.amsl.com  Fri Jul  2 11:15:24 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C947428C14C; Fri,  2 Jul 2010 11:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100702181516.C947428C14C@core3.amsl.com>
Date: Fri,  2 Jul 2010 11:15:02 -0700 (PDT)
Cc: xcon@ietf.org
Subject: [XCON] I-D Action:draft-ietf-xcon-examples-05.txt
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: Fri, 02 Jul 2010 18:15:25 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Centralized Conferencing Working Group of the IETF.


	Title           : Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
	Author(s)       : M. Barnes, et al.
	Filename        : draft-ietf-xcon-examples-05.txt
	Pages           : 86
	Date            : 2010-07-02

This document provides detailed call flows for the scenarios
documented in the Centralized Conferencing (XCON) Framework and the
XCON Scenarios.  The call flows document the use of the interface
between a conference control client and a conference control server
using the Centralized Conferencing Manipulation Protocol (CCMP).  The
objective is to provide a base reference for both protocol
researchers and developers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-examples-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xcon-examples-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-02110116.I-D@ietf.org>


--NextPart--

From rbarnes@bbn.com  Fri Jul  2 12:13:46 2010
Return-Path: <rbarnes@bbn.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 ECAB03A690C for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 12:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.859
X-Spam-Level: 
X-Spam-Status: No, score=-1.859 tagged_above=-999 required=5 tests=[AWL=0.740,  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 w68f+TThASnP for <xcon@core3.amsl.com>; Fri,  2 Jul 2010 12:13:44 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 8E4B63A690B for <xcon@ietf.org>; Fri,  2 Jul 2010 12:13:44 -0700 (PDT)
Received: from ros-dhcp192-1-51-71.bbn.com ([192.1.51.71]:52755) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1OUlgS-000Fas-8X; Fri, 02 Jul 2010 15:13:56 -0400
Message-Id: <47C07157-CB10-4F25-9986-3CA46E4DD285@bbn.com>
From: "Richard L. Barnes" <rbarnes@bbn.com>
To: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <4C2E2A89.90604@unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 2 Jul 2010 15:13:54 -0400
References: <4C2E2A89.90604@unina.it>
X-Mailer: Apple Mail (2.936)
Cc: xcon@ietf.org
Subject: Re: [XCON] New version of the CCMP draft
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: Fri, 02 Jul 2010 19:13:46 -0000

Thanks Simon for all your work.  We'll try to get this to the IESG as =20=

soon as possible.
--Richard


On Jul 2, 2010, at 2:06 PM, Simon Pietro Romano wrote:

> Dear all,
>
> I just uploaded a brand new version of the CCMP draft, containing =20
> the following new items:
>
>   1.  Added a section on the extendedRequest/extendedResponse message
>       pair.
>   2.  Added a section on the optionsRequest/optionsResponse message
>       pair.
>   3.  Added an example sub-section about the use of the =20
> optionsRequest/
>       optionsResponse message pair.
>   4.  Added an example sub-section about the use of the
>       extendedRequest/extendedResponse message pair.
>   5.  Updated the schema in order to reflect the latest modifications
>       and add-ons.
>   6.  Misc editorial nits...
>
> As far as we are concerned, the draft is now complete!
>
> Cheers,
>
> Simon
>
> --=20
>                            _\\|//_
>                            ( O-O )
>   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>                    Simon Pietro Romano
>              Universita' di Napoli Federico II
>                 Computer Science Department
>        Phone: +39 081 7683823 -- Fax: +39 081 7684219
>                e-mail: spromano@unina.it
>          http://www.comics.unina.it/simonpietro.romano
>
>    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi degli
>   idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                         oooO
>   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>                          \ (    (   )
>                           \_)    ) /
>                                 (_/
>
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon


From tom.kristensen@tandberg.com  Sat Jul  3 00:41:04 2010
Return-Path: <tom.kristensen@tandberg.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 A2F353A6970 for <xcon@core3.amsl.com>; Sat,  3 Jul 2010 00:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.938
X-Spam-Level: 
X-Spam-Status: No, score=-4.938 tagged_above=-999 required=5 tests=[AWL=1.661,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ExrP-ed7Ylee for <xcon@core3.amsl.com>; Sat,  3 Jul 2010 00:41:02 -0700 (PDT)
Received: from mail194.messagelabs.com (mail194.messagelabs.com [85.158.140.211]) by core3.amsl.com (Postfix) with SMTP id 8A0393A6956 for <xcon@ietf.org>; Sat,  3 Jul 2010 00:41:01 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tom.kristensen@tandberg.com
X-Msg-Ref: server-5.tower-194.messagelabs.com!1278142872!25147811!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [62.70.2.252]
Received: (qmail 1330 invoked from network); 3 Jul 2010 07:41:12 -0000
Received: from unknown (HELO OSLEXCP11.eu.tandberg.int) (62.70.2.252) by server-5.tower-194.messagelabs.com with SMTP; 3 Jul 2010 07:41:12 -0000
Received: from oslexcp2.eu.tandberg.int ([10.47.136.30]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Sat, 3 Jul 2010 09:41:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 3 Jul 2010 09:41:03 +0200
Message-ID: <C67BCA34F23E804199B464EAF3BE55DF07B5158B@oslexcp2.eu.tandberg.int>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
thread-index: AcsXfyV988VHTRxGQJuzVoxQSsELtADA/E5r
References: <1271757479.26184.8.camel@localhost>	<1273653780.2694.11.camel@localhost>	<1275916958.17477.9.camel@localhost>	<4C0E7332.6080402@gmail.com>	<4c0e8de6.df0ce30a.7e58.ffffa795@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49A05@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<AANLkTikXJAWyUBtMGShlnKnz2wjmE89x35o3mTAt-s1x@mail.gmail.com>	<59F4E573-56DA-4966-BF21-E5E36ED2E389@bbn.com>	<4c0f8c0f.9becd80a.55da.0fe2@mx.google.com>	<EDC0A1AE77C57744B664A310A0B23AE213E49BE7@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>	<4c107733.df0ce30a.21ca.15cc@mx.google.com>	<20100610130009.1f1fbb03.lorenzo@meetecho.com>	<0655E3C8-3B52-4428-B7F7-EA234E5E74F0@bbn.com>	<AANLkTimUNoLIVI9cLt4cyz2VFIN7m5auZ0kkn1DyThec@mail.gmail.com> <4c236e60.9d90d80a.1d25.6b10@mx.google.com> <4C29DA1F.1050408@gmail.com>
From: "Tom Kristensen" <tom.kristensen@tandberg.com>
To: "Gonzalo Camarillo" <gcamaril@gmail.com>, "Roni Even" <ron.even.tlv@gmail.com>
X-OriginalArrivalTime: 03 Jul 2010 07:41:12.0131 (UTC) FILETIME=[1BE65930:01CB1A83]
Cc: Mark Thompson <mark.thompson@tandberg.com>, Alan Johnston <alan.b.johnston@gmail.com>, "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
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: Sat, 03 Jul 2010 07:41:04 -0000

The momentum should be stronger this time, cf. the expressed support and =
need for this solution from various vendors. Also, the IMTC consortium =
has based it's best current practice document on the UDP/BFCP solution =
and sees a immediate need for it in order to deploy BFCP based solutions =
in the videoconferencing industry.

We'll contact the XCON chairs directly to find a way to proceed. I can =
understand the desire to close XCON as the CCMP drafts are now "last =
called", here's where Mary Barnes' AD sponsored draft path forward seems =
tempting.

Cheers,
-- Tom

-----Original Message-----
From: Gonzalo Camarillo [mailto:gcamaril@gmail.com]
Sent: Tue 2010-06-29 13:33
To: Roni Even
Cc: 'Mary Barnes'; 'Richard L. Barnes'; 'Alan Johnston'; Tom Kristensen; =
Mark Thompson; 'DRAGE, Keith (Keith)'; xcon@ietf.org
Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
=20
Hi,

yes, I had even the draft sources ready to start working on my hard
disk... but, unfortunately, all the energy around it suddenly
disappeared (for a number of reasons)... and I decided not to push this
by myself.

I hope the momentum around resolving this issue is stronger this time...

Cheers,

Gonzalo


On 24/06/2010 5:40 PM, Roni Even wrote:
> Mary,
> I think that in the discussion in the past, Gonzalo suggested to do a =
bis
> draft to RFC 4582. I think he mentioned other issues he wanted to =
update.
> Roni Even
>=20
>> -----Original Message-----
>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf =
Of
>> Mary Barnes
>> Sent: Wednesday, June 23, 2010 7:26 PM
>> To: Richard L. Barnes
>> Cc: Tom Kristensen; DRAGE, Keith (Keith); xcon@ietf.org; Mark =
Thompson;
>> Alan Johnston
>> Subject: Re: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-02
>>
>> I have reviewed the draft in question and while I agree that this
>> could be viewed as a workaround for some more general problems that
>> need to be solved, there is a current industry need for the solution
>> in this draft.   If the general problems described go to DISPATCH
>> (which is the appropriate thing to do rather than bringing this
>> specific document), the timeframe for getting agreement on the =
problem
>> to be solved and for the solutions to be agreed would be far longer
>> IMHO than if this document were progressed. If XCON would prefer to
>> close the WG without progressing this document (in this form or as a
>> -bis to RFC  4582), my suggestion would be to do as was done for the
>> remaining SIP and SIPPING documents and progress this item as an
>> individual AD sponsored.
>>
>> Mary.
>>
>> On Thu, Jun 10, 2010 at 8:18 AM, Richard L. Barnes <rbarnes@bbn.com>
>> wrote:
>>> <hat type=3D"individual"/>
>>>
>>> I tend to agree with Lorenzo that DISPATCH would be a better place =
to
>> have
>>> these discussions, especially given that, as far as I can tell from
>> this
>>> thread, the problem seems to be a general one of NAT traversal for
>> TCP.
>>>
>>>
>>>
>>> On Jun 10, 2010, at 7:00 AM, Lorenzo Miniero wrote:
>>>
>>>> Hi all,
>>>>
>>>> with respect to this topic, I think there are many issues
>> implementers
>>>> have to face when bringing IETF solutions to the real world. We
>> found
>>>> ourselves many times in a situation in which some kind of work-
>> around
>>>> had to be devised in order to let things work properly. Just to =
cite
>> a
>>>> couple of examples, with BFCP we had to find a way to let it work =
in
>> a
>>>> distributed conferencing scenario (which is far from easy, given =
the
>>>> intrinsic centralized model behind such protocol). In such case, we
>>>> decided to encapsulate BFCP messages in the body of XMPP
>>>> server-to-server packets (see the XCON-DCON Synchronization =
Protocol
>> in
>>>> draft-romano-dcon-xdsp-reqs-06 for the details) and then even
>> devised
>>>> a BFCP-XMPP gateway for such a purpose. With respect to the NAT
>>>> traversal issue, we also implemented an HTTP encapsulation. Moving
>>>> further we even conceived a DTMF-based frontend to BFCP ;) and also
>>>> almost thought about a BFCP-over-RTP approach.
>>>>
>>>> That said, I nevertheless agree with Keith on the discussion. Those
>>>> problems may be common to other TCP-based protocols as well, and as
>> such
>>>> a generic solution (generic TCP over UDP, for instance, or anything
>>>> else) may be a much better approach than doing a protocol specific
>>>> patch. Besides, whatever the solution, it should also take care of
>> how
>>>> the negotiation of such channels would be affected (as is the
>>>> case of RFC4583 for BFCP, which the proposed draft actually does).
>>>>
>>>> As Keith already suggested, DISPATCH may be a much better place to
>>>> discuss this issue: DISPATCH is where we'll also propose the above
>>>> mentioned DCON work.
>>>>
>>>> Lorenzo
>>>>
>>>>
>>>>
>>>> On Thu, 10 Jun 2010 08:22:55 +0300
>>>> "Roni Even" <ron.even.tlv@gmail.com> wrote:
>>>>
>>>>> Hi  Keith,
>>>>>
>>>>> I think that the IETF is trying to design protocols that will work
>> over
>>>>> the
>>>>> Internet and also to enable interoperability between independent
>>>>> implementations.
>>>>>
>>>>> In the BFCP case the shipping implementations support TCP as the
>>>>> transport
>>>>> protocol but they encountered issues when running over the =
Internet
>> due
>>>>> to
>>>>> devices like SBCs and due to lack of support for TCP media relay =
or
>>>>> ICE-TCP
>>>>> [I-D.ietf-mmusic-ice-tcp].
>>>>> When implementations looked at how to address the issue, the
>>>>> interoperability went away since there is no fall back solution =
for
>> this
>>>>> real life case. Some did a fall back to HTTP and some did to UDP
>> but not
>>>>> in
>>>>> an interoperable way.
>>>>>
>>>>> In order to achieve interoperability, this draft is trying to
>> extend the
>>>>> current BFCP. It is not suggesting to replace TCP but to keep TCP
>> as the
>>>>> mandatory transport and use UDP as fallback if unable to establish
>> TCP
>>>>> connection.
>>>>>
>>>>> As for security, if the topic will be adopted the solution will be
>>>>> updated
>>>>> to use DTLS as the transport for BFCP.
>>>>>
>>>>> I hope that people will read the draft and look at the objectives
>> and the
>>>>> proposed solution.
>>>>>
>>>>>
>>>>> BTW: This is a problem for client to client media connections over
>> TCP
>>>>> and
>>>>> my understanding is that RTSP offers to use both TCP and UDP since
>> both
>>>>> are
>>>>> specified. Since BFCP is not a payload but is running in parallel
>> to the
>>>>> RTP
>>>>> payload (for the point to point calls or MCU based multipoint) it
>> needs
>>>>> similar transport options.
>>>>>
>>>>> Thanks
>>>>> Roni Even
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: DRAGE, Keith (Keith) =
[mailto:keith.drage@alcatel-lucent.com]
>>>>>> Sent: Thursday, June 10, 2010 1:54 AM
>>>>>> To: Roni Even; 'Richard L. Barnes'; 'Tom Kristensen'
>>>>>> Cc: 'Mark Thompson'; 'Alan Johnston'; 'Tom Kristensen';
>> xcon@ietf.org
>>>>>> Subject: RE: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-02
>>>>>>
>>>>>> What you are essentially saying is that all protocols in the
>> future
>>>>>> that need reliable transport, as BFCP does, have to design in
>> their own
>>>>>> reliable transport element so they can use UDP. This is not a =
BFCP
>>>>>> specific issue.
>>>>>>
>>>>>> I find that an unacceptable direction for IETF to be heading in.
>>>>>>
>>>>>> I would also note that you are also asking for adoption of a
>> document
>>>>>> that cannot in its current form meet the security requirements of
>> the
>>>>>> original RFC.
>>>>>>
>>>>>> regards
>>>>>>
>>>>>> Keith
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>>>> Sent: Wednesday, June 09, 2010 1:40 PM
>>>>>>> To: 'Richard L. Barnes'; 'Tom Kristensen'
>>>>>>> Cc: 'Mark Thompson'; DRAGE, Keith (Keith); 'Alan Johnston';
>>>>>>> 'Tom Kristensen'; xcon@ietf.org
>>>>>>> Subject: RE: [XCON] WG Adoption? draft-sandbakken-xcon-bfcp-udp-
>> 02
>>>>>>>
>>>>>>> Richard,
>>>>>>> The BFCP I used as a presentation token for video
>>>>>>> conferencing. What the implementers found out that TCP does
>>>>>>> not work in real networks due to Session border controllers
>>>>>>> not supporting TCP as used in BFCP.
>>>>>>> This is why in products they try to establish TCP connection
>>>>>>> and if fails tries UDP.
>>>>>>> The video conferencing vendors participating in the IMTC sip
>>>>>>> parity activity group defined an interoperability profile
>>>>>>> that references this option Roni Even
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>
>>>>>>> On Behalf
>>>>>>>>
>>>>>>>> Of Richard L. Barnes
>>>>>>>> Sent: Wednesday, June 09, 2010 3:34 PM
>>>>>>>> To: Tom Kristensen
>>>>>>>> Cc: Mark Thompson; DRAGE, Keith (Keith); Alan Johnston; Tom
>>>>>>>> Kristensen; xcon@ietf.org
>>>>>>>> Subject: Re: [XCON] WG Adoption? =
draft-sandbakken-xcon-bfcp-udp-
>> 02
>>>>>>>>
>>>>>>>> Tom and others who are interested in this draft:
>>>>>>>>
>>>>>>>> For those who are relatively new here: Could you summarize why
>> you
>>>>>>>> think this draft is needed?  What requirement does it meet
>>>>>>>
>>>>>>> that BFCP
>>>>>>>>
>>>>>>>> doesn't right now?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> --Richard
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Jun 9, 2010, at 7:37 AM, Tom Kristensen wrote:
>>>>>>>>
>>>>>>>>> The UDP/BFCP draft has been presented and discussed in
>>>>>>>
>>>>>>> two or three
>>>>>>>>>
>>>>>>>>> IETF XCON sessions. No objection to the work being
>>>>>>>
>>>>>>> carried on, just
>>>>>>>>>
>>>>>>>>> that adoption as WG item was postponed until the draft was =
more
>>>>>>>>> complete. (This has been delayed of various reasons, but
>>>>>>>
>>>>>>> the authors
>>>>>>>>>
>>>>>>>>> believe the -02 version in question here should be ready for
>>>>>>>>> adoption).
>>>>>>>>>
>>>>>>>>> The "current status of consensus" might be valid for some, but
>>>>>>>>> participants in the XCON sessions and the minutes of meeting
>> show
>>>>>>>>> progress away from that initial consensus.
>>>>>>>>>
>>>>>>>>> I believe Ott's concerns are either dealt with or at
>>>>>>>
>>>>>>> least mentioned
>>>>>>>>>
>>>>>>>>> in the draft. Arrest me if I'm wrong.
>>>>>>>>>
>>>>>>>>> -- Tom
>>>>>>>>>
>>>>>>>>> On 9 June 2010 13:20, DRAGE, Keith (Keith)
>>>>>>>>> <keith.drage@alcatel-lucent.com> wrote:
>>>>>>>>>>
>>>>>>>>>> We made an explicit decision in the original draft that
>>>>>>>
>>>>>>> UDP was not
>>>>>>>>>>
>>>>>>>>>> required, not that we would do it later. That as far as I am
>>>>>>>>>> concerned represents the current status of consensus.
>>>>>>>>>>
>>>>>>>>>> This was done on the basis that we had all seen how UDP
>>>>>>>
>>>>>>> support had
>>>>>>>>>>
>>>>>>>>>> complicated SIP, and we did not want to repeat that issue.
>>>>>>>>>>
>>>>>>>>>> So this is not continuing the work. The status is an
>>>>>>>
>>>>>>> author draft
>>>>>>>>>>
>>>>>>>>>> which goes against a WG consensus position.
>>>>>>>>>>
>>>>>>>>>> I believe Georg Ott also expressed some concerns which I did
>> not
>>>>>>>>>> see answered on list at all.
>>>>>>>>>>
>>>>>>>>>> regards
>>>>>>>>>>
>>>>>>>>>> Keith
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] =
On
>>>>>>>>>>> Behalf Of Roni Even
>>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:35 PM
>>>>>>>>>>> To: 'Alan Johnston'; 'Tom Kristensen'
>>>>>>>>>>> Cc: 'Mark Thompson'; xcon@ietf.org
>>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>
>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>>
>>>>>>>>>>> Hi Alan,
>>>>>>>>>>> I support this work and think it is urgent to finish it.
>>>>>>>>>>> I think that updating BFCP with UDP support is very
>>>>>>>
>>>>>>> important. I
>>>>>>>>>>>
>>>>>>>>>>> would like to mention that BFCP is being used in video
>>>>>>>>>>> conferencing application and since the implementers
>> encountered
>>>>>>>>>>> problems with TCP they use a fall back to UDP.
>>>>>>>>>>> We discussed this work in previous IETF meeting and
>>>>>>>
>>>>>>> Gonzalo as far
>>>>>>>>>>>
>>>>>>>>>>> as I remember suggested to add it to a BFCP bis draft.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>> Roni Even
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]
>>>>>>>>>>>
>>>>>>>>>>> On Behalf
>>>>>>>>>>>>
>>>>>>>>>>>> Of Alan Johnston
>>>>>>>>>>>> Sent: Tuesday, June 08, 2010 7:44 PM
>>>>>>>>>>>> To: Tom Kristensen
>>>>>>>>>>>> Cc: Mark Thompson; xcon@ietf.org
>>>>>>>>>>>> Subject: Re: [XCON] WG Adoption?
>>>>>>>>>>>> draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>>>>>>
>>>>>>>>>>>> Tom,
>>>>>>>>>>>>
>>>>>>>>>>>> Apologies for the delay in replying.  As you know, the
>>>>>>>>>>>
>>>>>>>>>>> working group
>>>>>>>>>>>>
>>>>>>>>>>>> is in the process of completing its final milestones.
>>>>>>>>>>>> Publication requests will be issued in the next few
>>>>>>>
>>>>>>> days for the
>>>>>>>>>>>>
>>>>>>>>>>>> data
>>>>>>>>>>>
>>>>>>>>>>> model, CCMP,
>>>>>>>>>>>>
>>>>>>>>>>>> and the Examples drafts.
>>>>>>>>>>>>
>>>>>>>>>>>> Taking on any new milestones for the working group
>>>>>>>
>>>>>>> would require:
>>>>>>>>>>>>
>>>>>>>>>>>> 1. Strong support and interest from working group
>>>>>>>
>>>>>>> participants 2.
>>>>>>>>>>>>
>>>>>>>>>>>> Approval of our ADs.
>>>>>>>>>>>>
>>>>>>>>>>>> I haven't seen evidence of either of these at this stage.
>>>>>>>>>>>>
>>>>>>>>>>>> A possible option is to take this work to DISPATCH, get an
>>>>>>>>>>>
>>>>>>>>>>> indication
>>>>>>>>>>>>
>>>>>>>>>>>> of interests, and get feedback on the best way to move
>>>>>>>
>>>>>>> this work
>>>>>>>>>>>>
>>>>>>>>>>>> forward.
>>>>>>>>>>>>
>>>>>>>>>>>> - Alan -
>>>>>>>>>>>> co-chair XCON
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 6/7/10 8:22 AM, Tom Kristensen wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> The draft draft-sandbakken-xcon-bfcp-udp-02 was submitted
>>>>>>>>>>>
>>>>>>>>>>> early in
>>>>>>>>>>>>>
>>>>>>>>>>>>> March. No comments received since.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We'd like guidance on the next steps. First we ask for
>>>>>>>>>>>
>>>>>>>>>>> adoption as
>>>>>>>>>>>>>
>>>>>>>>>>>>> WG item. Next step would include the merging process with
>> bis
>>>>>>>>>>>>> versions
>>>>>>>>>>>>
>>>>>>>>>>>> of
>>>>>>>>>>>>>
>>>>>>>>>>>>> RFC 4582 and RFC 4583.
>>>>>>>>>>>>>
>>>>>>>>>>>>> We'd like to point out that interested parties for this
>>>>>>>>>>>
>>>>>>>>>>> work indeed
>>>>>>>>>>>>>
>>>>>>>>>>>>> exist.
>>>>>>>>>>>>>
>>>>>>>>>>>>> (For the record: Questions was sent to XCON chairs in
>>>>>>>>>>>
>>>>>>>>>>> April and May.
>>>>>>>>>>>>
>>>>>>>>>>>> See
>>>>>>>>>>>>>
>>>>>>>>>>>>> below. No response given. Therefore, this request on
>>>>>>>
>>>>>>> the list.)
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, 2010-05-12 at 10:43 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Chairs,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Any thoughts or decision on this matter?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, 2010-04-20 at 11:58 +0200, Tom Kristensen wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> XCON chairs,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We submitted draft-sandbakken-xcon-bfcp-udp-02
>>>>>>>
>>>>>>> early in March
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -
>>>>>>>>>>>>
>>>>>>>>>>>> well in
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> advance of IETF-77.
>>>>>>>>>>>>>>>  http://tools.ietf.org/html/draft-sandbakken-xcon-bfcp-
>>>>>>
>>>>>> udp
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No comments received. Neither on XCON WG list, nor
>>>>>>>>>>>
>>>>>>>>>>> directly to the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> authors. Therefore, we ask for adoption of this draft
>>>>>>>>>>>
>>>>>>>>>>> as an XCON
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> WG item.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -- Tom
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> XCON mailing list
>>>>>>>>>>>> XCON@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> XCON mailing list
>>>>>>>>>>> XCON@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> XCON mailing list
>>>>>>>>>> XCON@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> # TANDBERG R&D
>>>>>>>>> ## http://www.tandberg.com
>>>>>>>>> ### http://folk.uio.no/tomkri/
>>>>>>>>> _______________________________________________
>>>>>>>>> XCON mailing list
>>>>>>>>> XCON@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> XCON mailing list
>>>>>>>> XCON@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>>>
>>>>>>> =3D
>>>>>
>>>>> _______________________________________________
>>>>> XCON mailing list
>>>>> XCON@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/xcon
>>>>>
>>>>
>>>>
>>>> --
>>>> Lorenzo Miniero
>>>> Meetecho s.r.l.
>>>> http://www.meetecho.com/
>>>
>>> _______________________________________________
>>> XCON mailing list
>>> XCON@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xcon
>>>
>> _______________________________________________
>> XCON mailing list
>> XCON@ietf.org
>> https://www.ietf.org/mailman/listinfo/xcon
>=20
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>=20


From root@core3.amsl.com  Mon Jul 12 12:15:07 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 3897B3A6C41; Mon, 12 Jul 2010 12:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100712191504.3897B3A6C41@core3.amsl.com>
Date: Mon, 12 Jul 2010 12:15:01 -0700 (PDT)
Cc: xcon@ietf.org
Subject: [XCON] I-D Action:draft-ietf-xcon-examples-06.txt
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, 12 Jul 2010 19:15:07 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Centralized Conferencing Working Group of the IETF.


	Title           : Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
	Author(s)       : M. Barnes, et al.
	Filename        : draft-ietf-xcon-examples-06.txt
	Pages           : 86
	Date            : 2010-07-12

This document provides detailed call flows for the scenarios
documented in the Centralized Conferencing (XCON) Framework and the
XCON Scenarios.  The call flows document the use of the interface
between a conference control client and a conference control server
using the Centralized Conferencing Manipulation Protocol (CCMP).  The
objective is to provide a base reference for both protocol
researchers and developers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-examples-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xcon-examples-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-12120114.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Mon Jul 12 12:15:07 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 518913A6C40; Mon, 12 Jul 2010 12:15:05 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100712191507.518913A6C40@core3.amsl.com>
Date: Mon, 12 Jul 2010 12:15:05 -0700 (PDT)
Cc: xcon@ietf.org
Subject: [XCON] I-D Action:draft-ietf-xcon-ccmp-10.txt
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, 12 Jul 2010 19:15:07 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Centralized Conferencing Working Group of the IETF.


	Title           : Centralized Conferencing Manipulation Protocol
	Author(s)       : M. Barnes, et al.
	Filename        : draft-ietf-xcon-ccmp-10.txt
	Pages           : 109
	Date            : 2010-07-12

The Centralized Conferencing Manipulation Protocol (CCMP) allows an
XCON conferencing system client to create, retrieve, change, and
delete objects that describe a centralized conference.  CCMP is a
means to control basic and advanced conference features such as
conference state and capabilities, participants, relative roles, and
details.  CCMP is a state-less, XML-based, client server protocol
that carries, in its request and response messages, conference
information in the form of XML documents and fragments conforming to
the centralized conferencing data model schema.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-ccmp-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-xcon-ccmp-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-07-12120425.I-D@ietf.org>


--NextPart--

From gonzalo.camarillo@ericsson.com  Mon Jul 19 05:01:52 2010
Return-Path: <gonzalo.camarillo@ericsson.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 9A3753A6AF3 for <xcon@core3.amsl.com>; Mon, 19 Jul 2010 05:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.721
X-Spam-Level: 
X-Spam-Status: No, score=-105.721 tagged_above=-999 required=5 tests=[AWL=0.878, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 bvzu-eAS1m8M for <xcon@core3.amsl.com>; Mon, 19 Jul 2010 05:01:51 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 61DC23A6AF2 for <xcon@ietf.org>; Mon, 19 Jul 2010 05:01:51 -0700 (PDT)
X-AuditID: c1b4fb3d-b7b90ae00000278d-62-4c443ebd74be
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 17.DE.10125.DBE344C4; Mon, 19 Jul 2010 14:02:05 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Jul 2010 14:02:04 +0200
Received: from [131.160.126.163] ([131.160.126.163]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Jul 2010 14:02:04 +0200
Message-ID: <4C443EBC.4040603@ericsson.com>
Date: Mon, 19 Jul 2010 15:02:04 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: XCON <xcon@ietf.org>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2010 12:02:04.0728 (UTC) FILETIME=[342F1B80:01CB273A]
X-Brightmail-Tracker: AAAAAA==
Subject: [XCON] Fwd: How to transport BFCP in the presence of NATs
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, 19 Jul 2010 12:01:52 -0000

Hi,

I have requested feedback on the BFCP over UDP issue to the transport
community (see email below). Please, follow the discussions on the TSV
area mailing list.

Cheers,

Gonzalo


-------- Original Message --------
Subject: How to transport BFCP in the presence of NATs
Date: Mon, 19 Jul 2010 14:00:37 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
To: tsv-area@ietf.org <tsv-area@ietf.org>

Folks,

BFCP (Binary Floor Control Protocol), defined in RFC 4582, runs between
a client and a floor control server. Generally, the floor control server
has a public IP address. The client establishes a TCP connection towards
the floor control server so that, even if the client is behind a NAT,
everything works.

However, in some existing deployment scenarios the floor control server
functionality is implemented in an endpoint, which may be behind a NAT.
A typical session between two endpoints in these scenarios consist of a
BFCP connection and one or more media streams (e.g., audio and video)
between them. In this type of scenario, NAT traversal becomes a problem.

Existing deployments implement different approaches to address the fact
that the floor control server is not directly reachable. One of these
approaches consists of transporting BFCP over UDP instead of over TCP
(this approach is documented in the draft below). In this way, the
endpoints can use ICE to find connectivity between them.

https://datatracker.ietf.org/doc/draft-sandbakken-xcon-bfcp-udp/

An alternative approach would be to still use TCP as a transport and use
ICE TCP. However, the success rate of ICE TCP is not high enough at this
point. Yet another alternative would be to tunnel BFCP over TCP over UDP.

The XCON WG is aware of the guidelines given in RFC 5405 but would like
to ask the transport community for further guidance on this issue.

Note that this is actually a general issue that will affect any protocol
for which TCP would be the natural transport but that would need to run
between endpoints in NATted environments. RELOAD
(draft-ietf-p2psip-base) would be an example of a similar protocol
(which currently intends to use ICE TCP).

Given that this issue appear to be more general than BFCP and may affect
other protocols, we would appreciate to get input on how to proceed.

Thanks,

Gonzalo


From mary.ietf.barnes@gmail.com  Mon Jul 19 08:42:17 2010
Return-Path: <mary.ietf.barnes@gmail.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 537FC3A6937 for <xcon@core3.amsl.com>; Mon, 19 Jul 2010 08:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.371,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 jvi1Y55Dm9fv for <xcon@core3.amsl.com>; Mon, 19 Jul 2010 08:42:16 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 064833A6B24 for <xcon@ietf.org>; Mon, 19 Jul 2010 08:42:15 -0700 (PDT)
Received: by iwn38 with SMTP id 38so5212003iwn.31 for <xcon@ietf.org>; Mon, 19 Jul 2010 08:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=QzxiZ8j2UG7i4/WypQ7YSkGPISnrAp1nKlWTKFO40sc=; b=I6vl1i1SHpGXsITHcONszqJafoY+OrJkjRVyHRNnzWryCVDRKICf1tWvj3uWHyyMlS OiCHki7LCib721dQyxHGVqlgCuOZk/k3EBZifyd0mCXD1NgPqxRCwIs3RjU1XBJ2el85 bPWBh6fmfUyeGeGqpUysGNO770ko1jJCREdfk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kJboeXo1pRSEqiRS+9dfiqNQz2g22SCXNf9TggSaq71OzPjDGuPofpkKiU4q5d0wle sJlXBF+xIzDeM/3tBkR/9z5BjIA3PBr5jjzv1sMtkf4sniNebvGW62+eURc9Yf6ghXTV QauZ6vGafeeDWMPZiLgSIgSW8WCYR9FwEayas=
MIME-Version: 1.0
Received: by 10.231.193.135 with SMTP id du7mr4348003ibb.176.1279554150431;  Mon, 19 Jul 2010 08:42:30 -0700 (PDT)
Received: by 10.231.169.14 with HTTP; Mon, 19 Jul 2010 08:42:30 -0700 (PDT)
In-Reply-To: <4C443EBC.4040603@ericsson.com>
References: <4C443EBC.4040603@ericsson.com>
Date: Mon, 19 Jul 2010 10:42:30 -0500
Message-ID: <AANLkTilwa3JNzjeyagpVw0AyYEld45nKgLKZn8Qphxyo@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: multipart/alternative; boundary=0050450175199b7b6e048bbf6ae6
Cc: XCON <xcon@ietf.org>
Subject: Re: [XCON] Fwd: How to transport BFCP in the presence of NATs
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, 19 Jul 2010 15:42:17 -0000

--0050450175199b7b6e048bbf6ae6
Content-Type: text/plain; charset=ISO-8859-1

Just an FYI that this is the Transport Area mailing list:
http://www.ietf.org/mail-archive/web/tsv-area/current/maillist.html

And, not the TSV Area WG mailing list.

The Transport Area ML seems to have a fairly light load, so shouldn't be too
painful if you want to subscribe to follow the discussion.

Mary.

On Mon, Jul 19, 2010 at 7:02 AM, Gonzalo Camarillo <
Gonzalo.Camarillo@ericsson.com> wrote:

> Hi,
>
> I have requested feedback on the BFCP over UDP issue to the transport
> community (see email below). Please, follow the discussions on the TSV
> area mailing list.
>
> Cheers,
>
> Gonzalo
>
>
> -------- Original Message --------
> Subject: How to transport BFCP in the presence of NATs
> Date: Mon, 19 Jul 2010 14:00:37 +0200
> From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
> To: tsv-area@ietf.org <tsv-area@ietf.org>
>
> Folks,
>
> BFCP (Binary Floor Control Protocol), defined in RFC 4582, runs between
> a client and a floor control server. Generally, the floor control server
> has a public IP address. The client establishes a TCP connection towards
> the floor control server so that, even if the client is behind a NAT,
> everything works.
>
> However, in some existing deployment scenarios the floor control server
> functionality is implemented in an endpoint, which may be behind a NAT.
> A typical session between two endpoints in these scenarios consist of a
> BFCP connection and one or more media streams (e.g., audio and video)
> between them. In this type of scenario, NAT traversal becomes a problem.
>
> Existing deployments implement different approaches to address the fact
> that the floor control server is not directly reachable. One of these
> approaches consists of transporting BFCP over UDP instead of over TCP
> (this approach is documented in the draft below). In this way, the
> endpoints can use ICE to find connectivity between them.
>
> https://datatracker.ietf.org/doc/draft-sandbakken-xcon-bfcp-udp/
>
> An alternative approach would be to still use TCP as a transport and use
> ICE TCP. However, the success rate of ICE TCP is not high enough at this
> point. Yet another alternative would be to tunnel BFCP over TCP over UDP.
>
> The XCON WG is aware of the guidelines given in RFC 5405 but would like
> to ask the transport community for further guidance on this issue.
>
> Note that this is actually a general issue that will affect any protocol
> for which TCP would be the natural transport but that would need to run
> between endpoints in NATted environments. RELOAD
> (draft-ietf-p2psip-base) would be an example of a similar protocol
> (which currently intends to use ICE TCP).
>
> Given that this issue appear to be more general than BFCP and may affect
> other protocols, we would appreciate to get input on how to proceed.
>
> Thanks,
>
> Gonzalo
>
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www.ietf.org/mailman/listinfo/xcon
>

--0050450175199b7b6e048bbf6ae6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just an FYI that this is the Transport Area mailing list:<div><a href=3D"ht=
tp://www.ietf.org/mail-archive/web/tsv-area/current/maillist.html">http://w=
ww.ietf.org/mail-archive/web/tsv-area/current/maillist.html</a></div><div>
<br></div><div>And, not the TSV Area WG mailing list.</div><div><br></div><=
div>The Transport Area ML seems to have a fairly light load, so shouldn&#39=
;t be too painful if you want to subscribe to follow the discussion.</div>
<div><br></div><div>Mary.=A0<br><br><div class=3D"gmail_quote">On Mon, Jul =
19, 2010 at 7:02 AM, Gonzalo Camarillo <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:Gonzalo.Camarillo@ericsson.com">Gonzalo.Camarillo@ericsson.com</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi,<br>
<br>
I have requested feedback on the BFCP over UDP issue to the transport<br>
community (see email below). Please, follow the discussions on the TSV<br>
area mailing list.<br>
<br>
Cheers,<br>
<br>
Gonzalo<br>
<br>
<br>
-------- Original Message --------<br>
Subject: How to transport BFCP in the presence of NATs<br>
Date: Mon, 19 Jul 2010 14:00:37 +0200<br>
From: Gonzalo Camarillo &lt;<a href=3D"mailto:Gonzalo.Camarillo@ericsson.co=
m">Gonzalo.Camarillo@ericsson.com</a>&gt;<br>
To: <a href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a> &lt;<a href=
=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a>&gt;<br>
<br>
Folks,<br>
<br>
BFCP (Binary Floor Control Protocol), defined in RFC 4582, runs between<br>
a client and a floor control server. Generally, the floor control server<br=
>
has a public IP address. The client establishes a TCP connection towards<br=
>
the floor control server so that, even if the client is behind a NAT,<br>
everything works.<br>
<br>
However, in some existing deployment scenarios the floor control server<br>
functionality is implemented in an endpoint, which may be behind a NAT.<br>
A typical session between two endpoints in these scenarios consist of a<br>
BFCP connection and one or more media streams (e.g., audio and video)<br>
between them. In this type of scenario, NAT traversal becomes a problem.<br=
>
<br>
Existing deployments implement different approaches to address the fact<br>
that the floor control server is not directly reachable. One of these<br>
approaches consists of transporting BFCP over UDP instead of over TCP<br>
(this approach is documented in the draft below). In this way, the<br>
endpoints can use ICE to find connectivity between them.<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-sandbakken-xcon-bfcp-udp/=
" target=3D"_blank">https://datatracker.ietf.org/doc/draft-sandbakken-xcon-=
bfcp-udp/</a><br>
<br>
An alternative approach would be to still use TCP as a transport and use<br=
>
ICE TCP. However, the success rate of ICE TCP is not high enough at this<br=
>
point. Yet another alternative would be to tunnel BFCP over TCP over UDP.<b=
r>
<br>
The XCON WG is aware of the guidelines given in RFC 5405 but would like<br>
to ask the transport community for further guidance on this issue.<br>
<br>
Note that this is actually a general issue that will affect any protocol<br=
>
for which TCP would be the natural transport but that would need to run<br>
between endpoints in NATted environments. RELOAD<br>
(draft-ietf-p2psip-base) would be an example of a similar protocol<br>
(which currently intends to use ICE TCP).<br>
<br>
Given that this issue appear to be more general than BFCP and may affect<br=
>
other protocols, we would appreciate to get input on how to proceed.<br>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<br>
_______________________________________________<br>
XCON mailing list<br>
<a href=3D"mailto:XCON@ietf.org">XCON@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/xcon" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/xcon</a><br>
</blockquote></div><br></div>

--0050450175199b7b6e048bbf6ae6--
