From xcon-bounces@ietf.org  Thu May  8 13:42:51 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 957FE3A6E4F;
	Thu,  8 May 2008 13:42:51 -0700 (PDT)
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id 3EF983A68BA; Thu,  8 May 2008 13:42:50 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20080508204250.3EF983A68BA@core3.amsl.com>
Date: Thu,  8 May 2008 13:42:50 -0700 (PDT)
Cc: Internet Architecture Board <iab@iab.org>,
	xcon mailing list <xcon@ietf.org>, xcon chair <xcon-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [XCON] Protocol Action: 'A Framework for Centralized Conferencing'
 to Proposed Standard
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-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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

The IESG has approved the following document:

- 'A Framework for Centralized Conferencing '
   <draft-ietf-xcon-framework-11.txt> as a Proposed Standard

This document is the product of the Centralized Conferencing Working 
Group. 

The IESG contact persons are Cullen Jennings and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-11.txt

          Technical Summary

	     This document defines the framework for Centralized
	     Conferencing.  The framework allows participants using
	     various call signaling protocols, such as SIP, H.323,
	     Jabber and various protocols used in the PSTN, to
	     exchange media in a centralized unicast conference.
	     The Centralized Conferencing Framework defines logical
	     entities and naming conventions, along with a high
	     level conferencing data model.  The framework also
	     outlines a set of conferencing protocols, which are
	     complementary to the call signaling protocols, for
	     building advanced conferencing applications.  The
	     framework binds all the defined components together
	     for the benefit of builders of conferencing systems.

          Working Group Summary

             This document is a product of the XCON working group.
             It captures some of the most important consensus decisions
             in the working group's history, and forms the foundation
             of the conference control protocol that XCON will ultimately
             publish.

          Document Quality

             The document has been reviewed for technical quality
             by Adam Roach.

             The document specifies a framework and important
             concepts, but does not define an implementable protocol
             (which is a separate deliverable of the XCON working
             group). A group of students at Universita' di Napoli
             Federico II (Naples University) have implemented their
             own protocol based on the concepts in the XCON framework;
             however, because no protocol has been formally defined
             by XCON yet, interoperability isn't possible.  See
             https://sourceforge.net/projects/confiance/ for details.

             The document itself underwent a detailed review by assigned
             reviewers in September of 2005. Detailed reviewers included
             David Morgan, Oscar Novo, Roni Even, and Umesh Chandra.


Note to RFC Editor


OLD
Today, users often have passwords containing up to 30 bits
NEW
Today, users often have passwords containing up to 30 bits of entropy 

OLD
 users' visibility (including "anonymous" and "hidden") may be
NEW
 users' identity (including "anonymous" and "hidden") may be

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon


From xcon-bounces@ietf.org  Tue May 13 06:53:17 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A136D3A6C13;
	Tue, 13 May 2008 06:53:17 -0700 (PDT)
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 65534)
	id C407F3A6C13; Tue, 13 May 2008 06:53:14 -0700 (PDT)
X-Original-To: xcon@core3.amsl.com
Old-Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D1A2B28C2EC
	for <xcon@core3.amsl.com>; Tue, 13 May 2008 06:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.962
X-Spam-Level: *
X-Spam-Status: No, score=1.962 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001,
	RCVD_IN_BL_SPAMCOP_NET=1.96]
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 bKnWV9nijGpi for <xcon@core3.amsl.com>;
	Tue, 13 May 2008 06:48:36 -0700 (PDT)
Received: from bay0-omc2-s9.bay0.hotmail.com (bay0-omc2-s9.bay0.hotmail.com
	[65.54.246.145])
	by core3.amsl.com (Postfix) with ESMTP id 36CCB28C2E3
	for <xcon@ietf.org>; Tue, 13 May 2008 06:48:36 -0700 (PDT)
Received: from BAY142-W38 ([65.55.153.73]) by bay0-omc2-s9.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 13 May 2008 06:48:09 -0700
Message-ID: <BAY142-W381BB6FC12EFCF26814935B9CF0@phx.gbl>
X-Originating-IP: [212.118.140.8]
From: mohammad alkathery <alkathrey1983@hotmail.com>
To: <xcon@ietf.org>
Date: Tue, 13 May 2008 16:48:09 +0300
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 13 May 2008 13:48:09.0983 (UTC)
	FILETIME=[FAF130F0:01C8B4FF]
X-TMDA-Confirmed: Tue, 13 May 2008 06:53:14 -0700
Subject: [XCON] my mail
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: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============0423743378=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

--===============0423743378==
Content-Type: multipart/alternative;
	boundary="_c928f9f7-4a1e-4b11-8011-370a74467dce_"

--_c928f9f7-4a1e-4b11-8011-370a74467dce_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: 8bit

alkathrey1983@hotmail.com
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--_c928f9f7-4a1e-4b11-8011-370a74467dce_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: 8bit

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'><A href="mailto:alkathrey1983@hotmail.com"><FONT color=#993300>alkathrey1983@hotmail.com</FONT></A><br /><hr />Express yourself instantly with MSN Messenger! <a href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'>MSN Messenger</a></body>
</html>
--_c928f9f7-4a1e-4b11-8011-370a74467dce_--

--===============0423743378==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon

--===============0423743378==--


From xcon-bounces@ietf.org  Tue May 13 11:45:53 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A6DCA3A6847;
	Tue, 13 May 2008 11:45:53 -0700 (PDT)
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 CA0E53A6809
	for <xcon@core3.amsl.com>; Tue, 13 May 2008 11:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SPF_PASS=-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 LYyQlDcGBOeM for <xcon@core3.amsl.com>;
	Tue, 13 May 2008 11:45:50 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 7F2513A6847
	for <xcon@ietf.org>; Tue, 13 May 2008 11:45:50 -0700 (PDT)
Received: from sparc108.santera.com (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.2/8.14.1) with ESMTP id m4DIjlU8059946
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 13 May 2008 13:45:48 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <4829E1DE.8000307@nostrum.com>
Date: Tue, 13 May 2008 13:45:50 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: XCON-IETF <xcon@ietf.org>
References: <48188FC8.4080909@nostrum.com>
In-Reply-To: <48188FC8.4080909@nostrum.com>
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.93/6802/Wed Apr 16 12:35:44 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: Alan Johnston <alan@sipstation.com>,
	draft-ietf-xcon-common-data-model@tools.ietf.org
Subject: Re: [XCON] WGLC: draft-ietf-xcon-common-data-model-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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

As a reminder: there are only two days left on this last call. No one 
has any comments remaining?

/a

On 4/30/08 10:27 AM, Adam Roach wrote:
> [as chair]
>
> The chairs would like to announce a two-week working group last call for 
> the XCON common data model, so that we can submit it to the IESG for 
> publication. I encourage all working group participants to give the 
> document one final read. In particular, please ensure that the document 
> contains the data elements necessary for any conferencing applications 
> you may be aware of.
>
> The most recent version of the document may be retrieved here:
>   
> http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-10.txt
>
> This last call period runs until Thursday, May 15th.
>
> /a
> _______________________________________________
> 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


From xcon-bounces@ietf.org  Thu May 15 10:41:35 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E347F3A684E;
	Thu, 15 May 2008 10:41:35 -0700 (PDT)
X-Original-To: xcon@ietf.org
Delivered-To: xcon@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 65534)
	id C7C143A6927; Thu, 15 May 2008 10:41:34 -0700 (PDT)
X-Original-To: xcon@core3.amsl.com
Old-Delivered-To: xcon@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DAA483A67F5
	for <xcon@core3.amsl.com>; Thu, 15 May 2008 09:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[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 yOt6k07CRSLj for <xcon@core3.amsl.com>;
	Thu, 15 May 2008 09:07:05 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com
	(de307622-de-outbound.net.avaya.com [198.152.71.100])
	by core3.amsl.com (Postfix) with ESMTP id 1C2433A67B6
	for <xcon@ietf.org>; Thu, 15 May 2008 09:07:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,492,1204520400"; 
	d="scan'208,217";a="107411368"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	15 May 2008 12:05:29 -0400
X-IronPort-AV: E=Sophos;i="4.27,492,1204520400"; 
	d="scan'208,217";a="202496255"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.152])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	15 May 2008 12:05:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 May 2008 17:05:27 +0100
Message-ID: <A139B044B5D6B047BB8E0ADDD891820A603978@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] WGLC: draft-ietf-xcon-common-data-model-10.txt
Thread-Index: Aci2pX1zXKPyvEozQ6uYHv3345DdDw==
From: "Connolly, Stephen (Stephen)" <connollys@avaya.com>
To: "XCON-IETF" <xcon@ietf.org>
X-TMDA-Confirmed: Thu, 15 May 2008 10:41:34 -0700
Subject: [XCON]  WGLC: draft-ietf-xcon-common-data-model-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: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============0042682780=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0042682780==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B6A5.7DC0B0C5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B6A5.7DC0B0C5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
A group of us here at Avaya have a number of comments (with our "Avaya"
hats on) in relation to gaps between this proposed data model and the
Avaya MeetingExchange conferencing application.
=20
We are in the process of consolidating our issues and had hoped to have
a response by now.  However, at this stage it looks likely to be
tomorrow before we can get our comments consolidated.
=20
I hope tomorrow's late response will be acceptable.
=20
-Stephen

------_=_NextPart_001_01C8B6A5.7DC0B0C5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D255300116-15052008>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D255300116-15052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D255300116-15052008>A =
group of us here=20
at Avaya have a number of comments (with our "Avaya" hats on) in =
relation to=20
gaps between this proposed data model and the Avaya MeetingExchange =
conferencing=20
application.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D255300116-15052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D255300116-15052008>We are =
in the=20
process of consolidating our issues and had hoped to have a response by=20
now.&nbsp; However, at this stage it looks likely to be tomorrow before =
we can=20
get our comments consolidated.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D255300116-15052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D255300116-15052008>I hope =
tomorrow's=20
late response will be acceptable.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D255300116-15052008></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN =
class=3D255300116-15052008></SPAN></FONT>&nbsp;</DIV>
<DIV align=3Dleft><FONT face=3DArial =
size=3D2>-Stephen</FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C8B6A5.7DC0B0C5--

--===============0042682780==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon

--===============0042682780==--


From xcon-bounces@ietf.org  Thu May 15 12:32:05 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0E663A6888;
	Thu, 15 May 2008 12:32:05 -0700 (PDT)
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 8037D3A6824
	for <xcon@core3.amsl.com>; Thu, 15 May 2008 12:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	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 3zHOlFL6lWGc for <xcon@core3.amsl.com>;
	Thu, 15 May 2008 12:32:01 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id 6B5773A67FB
	for <xcon@ietf.org>; Thu, 15 May 2008 12:32:01 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m4FJUm109012; Thu, 15 May 2008 19:30:48 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 May 2008 14:29:12 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE037B9207@zrc2hxm1.corp.nortel.com>
In-Reply-To: <4829E1DE.8000307@nostrum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [XCON] WGLC: draft-ietf-xcon-common-data-model-10.txt
Thread-Index: Aci1KcI/CJ5VIqPmSRmB0qP6hcoP8ABkoLKg
References: <48188FC8.4080909@nostrum.com> <4829E1DE.8000307@nostrum.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "XCON-IETF" <xcon@ietf.org>
Cc: draft-ietf-xcon-common-data-model@tools.ietf.org
Subject: Re: [XCON] WGLC: draft-ietf-xcon-common-data-model-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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

I have reviewed the diff of the -10 against the last version I reviewed
in detail (-08) and have just one general question,  a few comments and
one nit. Overall, I think the document is ready to progress.

Regards,
Mary.   

Question:
----------
I did have one general question as to whether this version incorporates
the additional media fields that were identified by the MEDIACTRL folks?


Comments:
---------

S4 and S5: While working on the details for the protocol, I realized we
need a couple more elements added to <conference-description> including
an element to reflect if this conference is a "parent" and/or a "child"
and the "parent" of a "child" conference and the "child"ren of the
"parent" conferences  and whether the "child" is "independent" from the
"parent".   I think we can do that by defining the following:  
- "parent" element that can hold the XCON-URI for the parent and a
boolean as to whether the child is "independent" of the parent. 
- "child" attribute that contains a set of XCON-URIs, one for each child
obviously. 

S4.1/p13, 3rd sentence. For some reason, it is no longer clear to me why
we wouldn't want "state" and "version" as part of the <conference-info>,
as XCON will also support notifications, if I understand this sentence
correctly:
   "Note that the
   <conference-info> element does not have the attributes 'state' and
   'version' defined in [RFC4575] for this element because these
   attributes only applies to notification mechanisms."
   (also note the NIT in that sentence below)

S.4.6.5/p24, 3rd sentence. Same point as above wrt "state". 
   

Nits:
-----

S4.1/p13, 3rd sentence: "applies" -> "apply" 
_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon


From xcon-bounces@ietf.org  Fri May 16 08:20:06 2008
Return-Path: <xcon-bounces@ietf.org>
X-Original-To: xcon-archive@megatron.ietf.org
Delivered-To: ietfarch-xcon-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A237428C1C8;
	Fri, 16 May 2008 08:20:06 -0700 (PDT)
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 986A63A6B3C
	for <xcon@core3.amsl.com>; Fri, 16 May 2008 08:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, 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 00TI5ivLtnh6 for <xcon@core3.amsl.com>;
	Fri, 16 May 2008 08:20:03 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 1573128C21B
	for <xcon@ietf.org>; Fri, 16 May 2008 08:19:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,498,1204520400"; 
	d="scan'208,217";a="119244474"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 16 May 2008 11:19:49 -0400
X-IronPort-AV: E=Sophos;i="4.27,498,1204520400"; 
	d="scan'208,217";a="196294556"
Received: from unknown (HELO 306900ANEX2.global.avaya.com) ([135.64.148.152])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	16 May 2008 11:19:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 May 2008 16:19:49 +0100
Message-ID: <A139B044B5D6B047BB8E0ADDD891820A603AF0@306900ANEX2.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [XCON] WGLC: draft-ietf-xcon-common-data-model-10.txt
Thread-Index: Aci3aEfQHyiMj9+RT2KCNQo7uQ38/w==
From: "Connolly, Stephen (Stephen)" <connollys@avaya.com>
To: "XCON-IETF" <xcon@ietf.org>
Cc: "Johnston, Alan B \(Alan\)" <abjohnston@avaya.com>,
	draft-ietf-xcon-common-data-model@tools.ietf.org
Subject: Re: [XCON] WGLC: draft-ietf-xcon-common-data-model-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: <https://www.ietf.org/mailman/private/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>
Content-Type: multipart/mixed; boundary="===============1542619577=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1542619577==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B768.474B16FB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B768.474B16FB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,
=20
Here are our consolidated comments while wearing our "Avaya" hats.
=20
pg13, Figure 3 & pg 14, S4.2
*    Where do generic / proprietary conference attributes fit in e.g.
pin-list, recording, billing, call flow type , biometric , data, video ,
annunicator msgs?
=20
=20
pg14, S4.2.1=20
*    this assumes only a specific language is available, what about
country variants and fallback e.g. en, en_gb
=20
pg 15, S4.2.6=20
*    Does this imply a default of false if not specified ? What about
size of sidebars, number of sidebars
=20
pg 15, S4.2.7=20
*    Does their need to be anything about demand / scheduled / adhoc
(tui)
=20
*    Mandate all date times in UTC. It's up to a client application to
convert to / from local time as appropriate. How to handle timezones and
variation in dst rules or is this a problem for the OS and main
userspace runtime library?
=20
*    Should there be a way of linking via a uri to the ical object the
base element under conference-time\entry.=20
=20
*    I'm not familiar enough with ical rfc, but can it specify perpetual
conferences, recurring series with odd exceptions ? Tz / dst changes
that are outside normal rules due to political changes.
=20
*    required-participant attribute under mixing-start-offset has no
apparent definitions of the various roles
=20
*    can-join-after-offset doesn't mention DTSTART and signed integer
=20
*    allowed-extend-mixing-end-offset has no apparent limits on size,
duration , number of extension periods
=20
*    Would there be a requirement for accessing current time and tz on
server. How would one handle a distributed / dispersed server
deployment?
=20
*    In the Schema, the *-offset elements are dates, while in this
section they are described as integer offsets
=20
pg 16, S4.2.8=20
*    Must be able to repesent multiple access numbers to same logical
conference e.g. international, toll free, local access for PSTN users.
Howto represent a conference which spans multiple dispersed bridges
=20
*    There is only one <conference-password> element.  We have at least
two levels of password and can have multiple passwords for the same
level. How would this be represented?
=20
pg17, S4.2.10
*    would S4.2.10 depend on S4.2.11, and is there a way to capture that
dependency
=20
*    Does this maximum user count refer to the maximum users supported
by the media mixing servers, or the limit for the conference?
=20
*    Is there any way to indicate that the maximum-user-count can be
increased on demand if necessary?
=20
pg 18, S4.2.11=20
*    No mention of data, whileboarding. Need a way to indicate
bandwidth, preferred audio / image formats.
=20
*    What type of <mute> does <mute> provide.  We differentiate two
types of mute: "mute" is a mute that can be applied by a moderator or by
yourself.  It can only be removed by yourself. "silence" is a mute that
can only be applied or removed by a moderator.
=20
*    How can other controls be exposed?=20
=20
pg19, S4.3=20
*    Failover scenario - tcp-ip possibly changes
=20
pg 19, S4.4=20
*    Is this data model only concerned with runtime info? If not need a
way to indicate cancelled, billed, aborted, confirmed and possibly other
states
=20
pg 22, S4.6=20
*    Presumably user can have multiple roles simultaneously.=20
=20
pg23, S4.6.3=20
*    No definition of roles, format of uris
=20
pg 24, S4.6.4=20
*    No definition of roles, format of uris
=20
pg 24, S4.5.0
*    How are user PINs represented, i.e. the number unique to each user
that allows them to identify themselves via the TUI after entering the
conference password
=20
pg 27, S4.6.5.10
*    Can multiple users hold the floor in the same floor at the same
time? Can a user hold multiple floors at the same time? An example of
these would be good.
=20
pg28, S4.6.5.10=20
*    Data, whiteboarding in the from mixer element
=20
pg28, S5=20
*    This section duplicates Appendix A., shouldn't the schema be
defined in one location only in order to reduce the posibility of
synchronization errors
=20
pg29, conference-description-type
*    Extend to allow multiple conference-password child elements
=20
pg33, Conference-floor-policy
*    Should begin with a "c" not a "C"
=20
*    Need the ability to have multiple moderator-id's controlling the
floor.
=20
=20

------_=_NextPart_001_01C8B768.474B16FB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>All,</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>Here are our consolidated comments while =
wearing our=20
"Avaya" hats.</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>pg13, </SPAN>Figure 3&nbsp;<SPAN=20
class=3D190593214-16052008>&amp; pg 14, =
S4.2</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008></SPAN><SPAN =
class=3D831292813-16052008><FONT=20
face=3DArial size=3D2><SPAN =
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
W</SPAN></FONT></SPAN><SPAN class=3D831292813-16052008><FONT =
face=3DArial=20
size=3D2>here do generic&nbsp;/ proprietary conference attributes fit in =
e.g.=20
pin-list, recording, billing, call flow type , biometric , data, video , =

annunicator msgs?</FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>pg14, S</SPAN>4.2.1 =
</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>this assumes only =
a specific=20
language is available, what about country variants and fallback e.g. en, =

en_gb</FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 15, S</SPAN>4.2.6</SPAN><SPAN=20
class=3D831292813-16052008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Does this imply a =
default of=20
false if not specified ? What about size of sidebars, number of=20
sidebars</FONT></FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 15, S</SPAN>4.2.7</SPAN><SPAN=20
class=3D831292813-16052008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Does their need to =
be=20
anything about demand / scheduled / adhoc=20
(tui)</FONT></FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Mandate all date =
times in=20
UTC. It's up to a client application to convert to / from&nbsp;local =
time as=20
appropriate. How to handle timezones and variation in dst rules or is =
this a=20
problem for the OS and main&nbsp;userspace runtime=20
library?</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Should there be a =
way of=20
linking via a uri to the ical object the base element under=20
conference-time\entry. </FONT></FONT></SPAN></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008></SPAN><SPAN=20
class=3D831292813-16052008></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>I'm not familiar =
enough with=20
ical rfc, but can it specify perpetual conferences, recurring series =
with odd=20
exceptions ? Tz / dst changes that are outside normal rules due to =
political=20
changes.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; =
</SPAN>required-participant=20
attribute under mixing-start-offset has no apparent definitions of the =
various=20
roles</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; =
</SPAN>can-join-after-offset=20
doesn't mention DTSTART and signed integer</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
</SPAN>allowed-extend-mixing-end-offset has no apparent limits on size, =
duration=20
, number of extension periods</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Would there be a =
requirement=20
for accessing current time and tz on server. How would one handle a =
distributed=20
/ dispersed server deployment?</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2>*&nbsp;&nbsp;&nbsp; In the Schema, the *-offset =
elements are=20
dates, while in this section they are described as integer=20
offsets</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 16, S</SPAN>4.2.8 =
</SPAN></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>M</SPAN><SPAN=20
class=3D831292813-16052008>ust be able to repesent multiple access =
numbers to same=20
logical conference e.g. international, toll free, local access for PSTN =
users.=20
Howto represent a conference which spans multiple dispersed=20
bridges</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D831292813-16052008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; There is only one=20
&lt;conference-password&gt; element.&nbsp; We have at least two levels =
of=20
password and can have multiple passwords for the same level. How would =
this be=20
represented?</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2>pg17, S4.2.10</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2>*&nbsp;&nbsp;&nbsp; would S4.2.10 depend on =
S4.2.11, and is=20
there a way to capture that dependency</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2>*&nbsp;&nbsp;&nbsp; Does this maximum user count =
refer to the=20
maximum users supported by the media mixing servers, or the limit for =
the=20
conference?</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2>*&nbsp;&nbsp;&nbsp; Is there any way to indicate =
that the=20
maximum-user-count can be increased on demand if=20
necessary?</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><SPAN =
class=3D190593214-16052008><FONT=20
face=3DArial size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 18, S</SPAN>4.2.11</SPAN><SPAN=20
class=3D831292813-16052008>&nbsp;</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>No mention of =
data,=20
whileboarding. Need a way to indicate bandwidth, preferred audio / image =

formats.</FONT></FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D831292813-16052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; What type of &lt;mute&gt; =
does=20
&lt;mute&gt; provide.&nbsp; We differentiate two types of mute: "mute" =
is a mute=20
that can be applied by a moderator or by yourself.&nbsp; It can only be =
removed=20
by yourself. "silence" is a mute that can only be applied or removed by =
a=20
moderator.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; How can&nbsp;other =
controls be=20
exposed?&nbsp;</SPAN></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg19, S</SPAN>4.3 </SPAN></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>F</SPAN><SPAN=20
class=3D831292813-16052008>ailover scenario - tcp-ip possibly=20
changes</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 19, S</SPAN>4.4 =
</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008></SPAN><SPAN=20
class=3D831292813-16052008><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Is this data model =
only=20
concerned with runtime info? If not need a way to indicate cancelled, =
billed,=20
aborted, confirmed and possibly other =
states</FONT></FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 22, S</SPAN>4.6 =
</SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008></SPAN><SPAN=20
class=3D831292813-16052008><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Presumably user =
can have=20
multiple roles simultaneously. </FONT></FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg23, S</SPAN>4.6.3 =
</SPAN></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>N</SPAN><SPAN=20
class=3D831292813-16052008>o definition of roles, format of=20
uris</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>pg 24, S</SPAN>4.6.4 =
</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
</SPAN>N</FONT></FONT></FONT></SPAN><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D831292813-16052008><FONT face=3DArial size=3D2>o definition of =
roles, format=20
of uris</FONT></SPAN></DIV>
<DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008></SPAN><SPAN=20
class=3D831292813-16052008></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT><FONT face=3DArial size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 24, =
S4.5.0</SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; How are user PINs =
represented, i.e.=20
the number unique to each user that allows them to identify themselves =
via the=20
TUI after entering the conference =
password</SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D831292813-16052008></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT><FONT face=3DArial size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg 27, =
S4.6.5.10</SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT><FONT face=3DArial size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; Can multiple users hold =
the floor=20
in the same floor at the same time? =
</SPAN></SPAN></FONT></FONT><FONT><FONT=20
face=3DArial size=3D2><SPAN class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>Can a user hold multiple floors at the same =
time? An=20
example of these would be good.</SPAN></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D831292813-16052008></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D831292813-16052008><SPAN=20
class=3D190593214-16052008>pg28, S</SPAN>4.6.5<SPAN=20
class=3D190593214-16052008>.</SPAN>10 </SPAN></FONT></FONT></DIV>
<DIV><FONT><SPAN class=3D831292813-16052008></SPAN><SPAN=20
class=3D831292813-16052008><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; </SPAN>Data, =
whiteboarding in the=20
from mixer element</FONT></FONT></SPAN></FONT></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>pg28, =
S</SPAN>5&nbsp;</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp; This section =
</SPAN>duplicates=20
Appendix A., should<SPAN class=3D190593214-16052008>n't</SPAN> the =
schema be=20
defined in one location only<SPAN class=3D190593214-16052008> in order =
to reduce=20
the posibility of synchronization=20
errors</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D831292813-16052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV></SPAN></DIV></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D190593214-16052008>pg29,=20
conference-description-type</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
Extend to allow multiple conference-password child =
elements</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D190593214-16052008>pg33,=20
Conference-floor-policy</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
Should begin with a "c" not a "C"</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D190593214-16052008>*&nbsp;&nbsp;&nbsp;=20
Need the ability to have multiple moderator-id's controlling the=20
floor.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D190593214-16052008></SPAN></FONT>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C8B768.474B16FB--

--===============1542619577==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www.ietf.org/mailman/listinfo/xcon

--===============1542619577==--


