From xcon-bounces@ietf.org Thu Sep 08 18:50:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDVDq-0000FF-6C; Thu, 08 Sep 2005 18:50:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EDVDX-00007P-HQ; Thu, 08 Sep 2005 18:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23580;
	Thu, 8 Sep 2005 18:49:59 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EDVGz-0002MM-97; Thu, 08 Sep 2005 18:53:38 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EDVDV-00034C-Hu; Thu, 08 Sep 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EDVDV-00034C-Hu@newodin.ietf.org>
Date: Thu, 08 Sep 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: xcon@ietf.org
Subject: [XCON] I-D ACTION:draft-ietf-xcon-conference-scenarios-05.txt 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

--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		: Conferencing Scenarios
	Author(s)	: R. Even, N. Ismail
	Filename	: draft-ietf-xcon-conference-scenarios-05.txt
	Pages		: 16
	Date		: 2005-9-8
	
This document describes multimedia conferencing scenarios.  It
   describes both basic and advanced conferencing scenarios involving
   voice, video, text and interactive text sessions.  These conferencing
   scenarios will help with the definition and evaluation of the
   protocols being developed in the centralized conferencing XCON
   working group.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-xcon-conference-scenarios-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-xcon-conference-scenarios-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-9-8155314.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-xcon-conference-scenarios-05.txt

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

Content-Type: text/plain
Content-ID: <2005-9-8155314.I-D@ietf.org>


--OtherAccess--

--NextPart
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://www1.ietf.org/mailman/listinfo/xcon

--NextPart--





From xcon-bounces@ietf.org Mon Sep 12 14:36:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EEtAB-0006yV-Tr; Mon, 12 Sep 2005 14:36:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EEtA9-0006xe-LQ
	for xcon@megatron.ietf.org; Mon, 12 Sep 2005 14:36:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06541
	for <XCON@ietf.org>; Mon, 12 Sep 2005 14:36:08 -0400 (EDT)
From: Umesh.Chandra@nokia.com
Received: from mgw-ext02.nokia.com ([131.228.20.94])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEtEF-00051g-O0
	for XCON@ietf.org; Mon, 12 Sep 2005 14:40:33 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j8CIa53X016514 for <XCON@ietf.org>; Mon, 12 Sep 2005 21:36:06 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 21:36:05 +0300
Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 13:36:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Sep 2005 13:36:01 -0500
Message-ID: <815E2AF6A087FF45A68EF2F310ADE111937C8D@daebe102.NOE.Nokia.com>
Thread-Topic: Comments on draft-ietf-xcon-framework-01.txt - templates VS
	blueprints
Thread-Index: AcWSJB6UcoV4MVLWSSavryDRfvFKogcCm5wwAmW8L7A=
To: <XCON@ietf.org>
X-OriginalArrivalTime: 12 Sep 2005 18:36:01.0256 (UTC)
	FILETIME=[D313CE80:01C5B7C8]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt - templates VS
	blueprints
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hello,
=20
As part of the review of framwork document i wanted to raise some issue
relating to blueprint and template definition and use in the draft. I am
not sure if this issues have been raised before (I know Dave had sent
some comments regarding blueprints and templates), but if it has accept
my apologies. I am just trying to understand clearly the definition and
difference between templates and blueprint.
=20
On page 7 (section 3, 3 paragraph), it says "For conference creation, a
Conference  Object provides a "blueprint" representing the System
Capabilities". By system capabilities does it mean what types of media
is allowed, how many participants can participate in the conference,
what types of media control are available to the participants, etc" If
that is so, then how different it is from conference template (which is
part of the conference object).? So my question is what is System
capabilties and how are they indicated in the blueprint which is
different from the way they are indicated in the conference template.
=20
On page 19 section 6.2 last paragraph), the draft says "The selected
blueprint with its default values is copied by the server into a newly
created Conference Object, referred to as an 'Active Conference'. Do we
mean blueprint or conference tempalate here ? Does the blueprint has
default values and if so what types of default values does it assume. I
know the templates have default values (like the MUTE control by default
is disabled). This is a little confusing to me since in section 6.3
(second paragraph) the drafts says "Firstly, a client would query a
Conferencing System for its capabilities.  This can be done by
requesting a list of the Conference Object "blueprints" (or templates)
the system supports". Clearly here it means conference templates since
conference templates defines what the conference server supports in
terms of media, control, participant roles etc (which you mention later
in the paragraph). So why distinguish between 2 different scenrios,
unless blueprint and templates means the same.
=20
Finally an example of an blueprint (may be XML) would really aid in
understanding how the conference server uses it to create a conference
object.
=20
=20
BR
=20
Umesh
=20
=20

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



From xcon-bounces@ietf.org Mon Sep 12 16:20:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EEunI-0003nv-EM; Mon, 12 Sep 2005 16:20:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EEunF-0003nN-Vx
	for xcon@megatron.ietf.org; Mon, 12 Sep 2005 16:20:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16723
	for <xcon@ietf.org>; Mon, 12 Sep 2005 16:20:43 -0400 (EDT)
From: Umesh.Chandra@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEurU-0000ts-5a
	for xcon@ietf.org; Mon, 12 Sep 2005 16:25:09 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j8CKIxTu003442 for <xcon@ietf.org>; Mon, 12 Sep 2005 23:19:05 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 23:20:41 +0300
Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 15:20:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Sep 2005 15:20:37 -0500
Message-ID: <815E2AF6A087FF45A68EF2F310ADE111937D1C@daebe102.NOE.Nokia.com>
Thread-Topic: Comments on draft-ietf-xcon-framework-01.txt
Thread-Index: AcW313Ax6MoFJLfbRh6jecopiuN31w==
To: <xcon@ietf.org>
X-OriginalArrivalTime: 12 Sep 2005 20:20:38.0369 (UTC)
	FILETIME=[70873D10:01C5B7D7]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hello,

I reviewed the draft and it looks in a good shape to me, though I felt
some more detailed examples would aid in understanding it more clearly.
My comments besides the blueprint and templates which I sent in the
earlier email are as follows

1) In section 4.2 - is the conference template is used only to describe
the mixer or media related functionality only meaning - the media
controls available to end points to customize the media they receive
from the server, the ability to mute somebody in the conference based on
some privilages etc.=20

2) Editoral comment. In section 4.2 (3 paragraph) the sentence " This
information would allow authorized clients to manipulate mixer's
behavior and the resultant distribution of the media to all or
individual participants" should be changed to "This information would
allow authorized clients to manipulate mixer's behavior via focus, and
the resultant distribution of the media to all or individual
participants". The present sentence gives an impression that clients can
communicate directly with the mixer to change the media.
3)  In section 4.3, where are the permission and limits are specified in
the conference object - in the template or in the common conference
information section.
4) In section 5.3, (2 paragraph) the draft says " The Conference Object
is identified by a single or a set of call signaling Conference
Identifiers, with a one-to-one mapping, as shown in the figure".  Is the
conference object identified by conference identifier (for example the
SIP URL of a SIP conference) or an conference object identifier. ?
5) Editorial comment. There is no definition for conference user
identifier in section 2 (convention and terminology). For consistency
sake it would be good to define it.
6) In section 6.1 (page 18), how does the parent object enforce a
different policy by marking certain data elements as "parent
enforceable". Are these markings done in the conference template ?
7) In section 6.2, it would really help if you can provide an example as
to how an conference factory  select one of the system supported
conference object blueprint based on the privileges and media lines in
SDP. It would be good to see an SDP example with audio and video media,
how the blue print would look like to get an clear picture.=20
8)  Section 7.3.4 - Do we still leave the section regarding NETCONF as a
possible protocol option ?
9)  In section 8.1, where an example is provided as to how an
participant is added to the conference using the conference control
protocol, it woul d be a good idea to extend the example depicting how
the new participant "Bob" gets the information from the conference
server as to what type of blueprint is being used for this conference.
Basically from a system point of view it would be good to know how when
a participant joins the conference (when an authorized participant sends
CCP request to add it to the conferene) it gets to know about the
capabilities (conference and media) of the conference. I thought it was
not obvious from the present example in section 8.1

Some Nits and Typos
1) In section 3, page 7 remove the word and from the first line.
2)  In section 6.1 page 18 (4 paragrpah) you have reference to section
5.3.1 describing how an unique conference object URI is assigned. There
is no description of it in section 5.3.1, instead there is an reference
in 5.3.1 to TBD. So I guess instead of refering section 5.3.1 it should
refer to the correct reference.
3)  In section 8.3 page 35, terminate the line with a full stop. " A
Sidebar is created using the same mechanisms employed for a standard
conference as described in Section 6.1."

BR
Umesh









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



From xcon-bounces@ietf.org Mon Sep 12 18:57:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EExEr-0007wO-3J; Mon, 12 Sep 2005 18:57:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EEw5y-0006Mb-Mz
	for xcon@megatron.ietf.org; Mon, 12 Sep 2005 17:44:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03486
	for <XCON@ietf.org>; Mon, 12 Sep 2005 17:44:08 -0400 (EDT)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EEwAC-0007Qb-Bd
	for XCON@ietf.org; Mon, 12 Sep 2005 17:48:35 -0400
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 14:43:57 -0700
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Sep 2005 14:43:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] Comments on draft-ietf-xcon-framework-01.txt - templates
	VSblueprints
Date: Mon, 12 Sep 2005 14:43:51 -0700
Message-ID: <DD07841287D0AD428833021705E0D14E062BE385@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [XCON] Comments on draft-ietf-xcon-framework-01.txt - templates
	VSblueprints
thread-index: AcWSJB6UcoV4MVLWSSavryDRfvFKogcCm5wwAmW8L7AABwXMkA==
From: "Orit Levin" <oritl@microsoft.com>
To: <Umesh.Chandra@nokia.com>, <XCON@ietf.org>
X-OriginalArrivalTime: 12 Sep 2005 21:43:56.0915 (UTC)
	FILETIME=[13E4D430:01C5B7E3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Umesh,

The conceptual difference between the two is that
- Template is the definition (in .xsd) of how a conference capabilities
can be expressed using XML.
- Blueprint is the instance (in .xml) of a template kept in a system and
describing what the initial capabilities/state of a conference created
from the blueprint are going to be.

Orit.=20

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20
> Behalf Of Umesh.Chandra@nokia.com
> Sent: Monday, September 12, 2005 11:36 AM
> To: XCON@ietf.org
> Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt=20
> - templates VSblueprints
>=20
> Hello,
> =20
> As part of the review of framwork document i wanted to raise=20
> some issue relating to blueprint and template definition and=20
> use in the draft. I am not sure if this issues have been=20
> raised before (I know Dave had sent some comments regarding=20
> blueprints and templates), but if it has accept my apologies.=20
> I am just trying to understand clearly the definition and=20
> difference between templates and blueprint.
> =20
> On page 7 (section 3, 3 paragraph), it says "For conference=20
> creation, a Conference  Object provides a "blueprint"=20
> representing the System Capabilities". By system capabilities=20
> does it mean what types of media is allowed, how many=20
> participants can participate in the conference, what types of=20
> media control are available to the participants, etc" If that=20
> is so, then how different it is from conference template=20
> (which is part of the conference object).? So my question is=20
> what is System capabilties and how are they indicated in the=20
> blueprint which is different from the way they are indicated=20
> in the conference template.
> =20
> On page 19 section 6.2 last paragraph), the draft says "The=20
> selected blueprint with its default values is copied by the=20
> server into a newly created Conference Object, referred to as=20
> an 'Active Conference'. Do we mean blueprint or conference=20
> tempalate here ? Does the blueprint has default values and if=20
> so what types of default values does it assume. I know the=20
> templates have default values (like the MUTE control by=20
> default is disabled). This is a little confusing to me since=20
> in section 6.3 (second paragraph) the drafts says "Firstly, a=20
> client would query a Conferencing System for its=20
> capabilities.  This can be done by requesting a list of the=20
> Conference Object "blueprints" (or templates) the system=20
> supports". Clearly here it means conference templates since=20
> conference templates defines what the conference server=20
> supports in terms of media, control, participant roles etc=20
> (which you mention later in the paragraph). So why=20
> distinguish between 2 different scenrios, unless blueprint=20
> and templates means the same.
> =20
> Finally an example of an blueprint (may be XML) would really=20
> aid in understanding how the conference server uses it to=20
> create a conference object.
> =20
> =20
> BR
> =20
> Umesh
> =20
> =20
>=20
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www1.ietf.org/mailman/listinfo/xcon
>=20

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



From xcon-bounces@ietf.org Thu Sep 22 09:41:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIRKn-0000kf-DZ; Thu, 22 Sep 2005 09:41:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIRKl-0000kN-5W
	for xcon@megatron.ietf.org; Thu, 22 Sep 2005 09:41:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29997
	for <xcon@ietf.org>; Thu, 22 Sep 2005 09:41:53 -0400 (EDT)
Received: from jalapeno.cc.columbia.edu ([128.59.29.5] ident=cu41754)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIRR0-0001Kn-Dl
	for xcon@ietf.org; Thu, 22 Sep 2005 09:48:22 -0400
Received: from [192.168.0.37] (pool-141-153-174-94.mad.east.verizon.net
	[141.153.174.94]) (user=hgs10 mech=PLAIN bits=0)
	by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id
	j8MDfFmQ013372
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <xcon@ietf.org>; Thu, 22 Sep 2005 09:41:54 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v733)
Content-Transfer-Encoding: 7bit
Message-Id: <E459B497-F821-4B0C-85E3-07F940016859@cs.columbia.edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: xcon@ietf.org
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Wed, 21 Sep 2005 21:23:26 -0400
X-Mailer: Apple Mail (2.733)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Subject: [XCON] framework-01, 7.3
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Given the audience of the document, I would drop Section 7.3  
(Conference Control Protocol). Once the protocol has been decided on,  
it would only be of historical interest and would be more likely to  
confuse implementors that would go hunting for long-expired I-Ds and  
faint echos of these protocols in dusty mailing list archives.

Henning

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



From xcon-bounces@ietf.org Thu Sep 22 10:10:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIRm8-0000m7-0k; Thu, 22 Sep 2005 10:10:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIRm4-0000lR-AD
	for xcon@megatron.ietf.org; Thu, 22 Sep 2005 10:10:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02094
	for <xcon@ietf.org>; Thu, 22 Sep 2005 10:10:06 -0400 (EDT)
Received: from cluster-b.mailcontrol.com ([217.68.146.190]
	helo=rly16b.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIRsG-00029E-Cr
	for xcon@ietf.org; Thu, 22 Sep 2005 10:16:36 -0400
Received: from GBNEWP0758M.eu.ubiquity.net ([62.172.205.164])
	by rly16b.srv.mailcontrol.com (MailControl) with ESMTP id
	j8ME9Vw5021074; Thu, 22 Sep 2005 15:09:32 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] framework-01, 7.3
Date: Thu, 22 Sep 2005 15:09:32 +0100
Message-ID: <45730E094814E44488F789C1CDED27AE02BDFFCB@gbnewp0758m.eu.ubiquity.net>
Thread-Topic: [XCON] framework-01, 7.3
Thread-Index: AcW/e44bq8Xjo45wT4OpicHaLsTkwwAA0pFw
From: "Chris Boulton" <cboulton@ubiquity.net>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, <xcon@ietf.org>
X-Scanned-By: MailControl A-05-40-00 (www.mailcontrol.com) on 10.66.0.126
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Henning,

	The ultimate intention of this section is to detail the chosen
mechanism for the Framework.  The text that currently exists there is
only temporary until the decision is made and was meant to provide info
and stimulate discussion - it will then be replaced with appropriate
text relating to 'the chosen one'.  We can certainly remove text if
required and leave a placeholder if it is deemed necessary.

Chris.


-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Henning Schulzrinne
Sent: 22 September 2005 02:23
To: xcon@ietf.org
Subject: [XCON] framework-01, 7.3

Given the audience of the document, I would drop Section 7.3=20=20
(Conference Control Protocol). Once the protocol has been decided on,=20=20
it would only be of historical interest and would be more likely to=20=20
confuse implementors that would go hunting for long-expired I-Ds and=20=20
faint echos of these protocols in dusty mailing list archives.

Henning

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


Information contained in this e-mail and any attachments are intended for t=
he use of the addressee only, and may contain confidential information of U=
biquity Software Corporation.  All unauthorized use, disclosure or distribu=
tion is strictly prohibited.  If you are not the addressee, please notify t=
he sender immediately and destroy all copies of this email.  Unless otherwi=
se expressly agreed in writing signed by an officer of Ubiquity Software Co=
rporation, nothing in this communication shall be deemed to be legally bind=
ing.  Thank you.


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



From xcon-bounces@ietf.org Thu Sep 22 12:13:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EITh1-0002bB-Lq; Thu, 22 Sep 2005 12:13:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EITgx-0002aO-TV; Thu, 22 Sep 2005 12:12:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09082;
	Thu, 22 Sep 2005 12:12:57 -0400 (EDT)
Received: from mail1.followap.com ([194.90.96.46] helo=mail.followap.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EITnA-0005MA-HF; Thu, 22 Sep 2005 12:19:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 Sep 2005 19:04:59 +0300
Message-ID: <8E5AB0A04458904BB9B079055261033C0104E1D7@mail.followap.com>
Thread-Topic: http://www.ietf.org/internet-drafts/draft-sriram-sipping-poc-lip-02.txt
Thread-Index: AcW/jzk7CrGP2si2SaqQTHKj2/OdJg==
From: "Fridy Sharon-Fridman" <Fridy.Sharon-Fridman@followap.com>
To: <sriram.s@motorola.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c2e58d9873012c90703822e287241385
Cc: sipping@ietf.org, xcon@ietf.org
Subject: [XCON] 
	http://www.ietf.org/internet-drafts/draft-sriram-sipping-poc-lip-02.txt
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0856934377=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0856934377==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5BF90.0AB55B81"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5BF90.0AB55B81
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

As the intercept is based on SIP INVITE with SDP, why isn't it
applicable to intercept conference (xcon conference) where he media is
MSRP instead of RTP etc.?

Can this I/D be generalized to handle session interception and cover PoC
demands but be less tightly coupled to it, as once was the mission
statement of IETF (internet Task Force...)?

=20

I suggest using the needed headers and terms slightly changed:

Mode-of-Tapping
Direction
User-to-be-Tapped

=20

The PoC server procedures are clearly defined in the OMA PoC
specification. PoC usage scenario can be given as an illustrated
example.

It will provide OMA PoC group with a sufficient solution for their
demands, but not tighten the mechanism to PoC alone.

=20

Cheers,

--Fridy / Followap


------_=_NextPart_001_01C5BF90.0AB55B81
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:1.3in;
	text-indent:-.3in;
	page-break-before:always;
	page-break-after:avoid;
	mso-list:l0 level1 lfo4;
	font-size:20.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1672835366;
	mso-list-template-ids:-912073916;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-suffix:space;
	mso-level-text:%1;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:1.4in;
	mso-level-number-position:left;
	margin-left:1.4in;
	text-indent:-.4in;
	mso-ansi-font-style:normal;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.5in;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:1.6in;
	mso-level-number-position:left;
	margin-left:1.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:1.7in;
	mso-level-number-position:left;
	margin-left:1.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:1.8in;
	mso-level-number-position:left;
	margin-left:1.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:1.9in;
	mso-level-number-position:left;
	margin-left:1.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	margin-left:2.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:2.1in;
	mso-level-number-position:left;
	margin-left:2.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As the intercept is based on SIP INVITE with SDP, why
isn&#8217;t it applicable to intercept conference (xcon conference) =
where he
media is MSRP instead of RTP etc.?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can this I/D be generalized to handle session =
interception
and cover PoC demands but be less tightly coupled to it, as once was the
mission statement of IETF (internet Task =
Force&#8230;)?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I suggest using the needed headers and terms slightly
changed:<o:p></o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Mode-of-Tapping<o:p></o:p></span></font></pre>=
<pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Direction<o:p></o:p></span></font></pre><pre><=
font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>User-to-be-Tapped<o:p></o:p></span></font></pr=
e>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The PoC server procedures are clearly defined in the =
OMA PoC
specification. PoC usage scenario can be given as an illustrated =
example.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It will provide OMA PoC group with a sufficient =
solution for
their demands, but not tighten the mechanism to PoC =
alone.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Cheers,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>--Fridy / Followap<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C5BF90.0AB55B81--


--===============0856934377==
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://www1.ietf.org/mailman/listinfo/xcon

--===============0856934377==--




From xcon-bounces@ietf.org Thu Sep 22 13:00:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIUQx-0002jn-Mu; Thu, 22 Sep 2005 13:00:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EIUQv-0002h0-R7
	for xcon@megatron.ietf.org; Thu, 22 Sep 2005 13:00:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11018
	for <xcon@ietf.org>; Thu, 22 Sep 2005 13:00:27 -0400 (EDT)
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIUXB-0006Uu-PG
	for xcon@ietf.org; Thu, 22 Sep 2005 13:06:59 -0400
Received: from [128.59.16.206] (chairpc.win.cs.columbia.edu [128.59.16.206])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id j8MH0OWk013173
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Thu, 22 Sep 2005 13:00:25 -0400 (EDT)
Message-ID: <4332E304.40003@cs.columbia.edu>
Date: Thu, 22 Sep 2005 12:59:48 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Chris Boulton <cboulton@ubiquity.net>
Subject: Re: [XCON] framework-01, 7.3
References: <45730E094814E44488F789C1CDED27AE02BDFFCB@gbnewp0758m.eu.ubiquity.net>
In-Reply-To: <45730E094814E44488F789C1CDED27AE02BDFFCB@gbnewp0758m.eu.ubiquity.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0,
	__CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0,
	__MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0'
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: xcon@ietf.org
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Chris,

I guess this raises the issue of timing. My assumption, given the 
informal "last call", was that this document would be headed out the WG 
door within a few weeks, i.e., well before a decision on the conference 
control protocol(s) is likely to have been made, let alone its design 
has been finalized and vetted.

At least from my limited experience with framework documents, such as 
the one in the NSIS WG, these documents are finished before the protocol 
  design. If this is meant more of a "document roadmap" or "IETF 
centralized conferencing architecture", we should probably wait with a 
final review until almost all of the details have been worked out.

Henning

Chris Boulton wrote:
> Henning,
> 
> 	The ultimate intention of this section is to detail the chosen
> mechanism for the Framework.  The text that currently exists there is
> only temporary until the decision is made and was meant to provide info
> and stimulate discussion - it will then be replaced with appropriate
> text relating to 'the chosen one'.  We can certainly remove text if
> required and leave a placeholder if it is deemed necessary.
> 
> Chris.
> 

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



From xcon-bounces@ietf.org Fri Sep 23 08:12:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EImQ2-0002PB-5H; Fri, 23 Sep 2005 08:12:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EImPz-0002Ou-KB
	for xcon@megatron.ietf.org; Fri, 23 Sep 2005 08:12:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10859
	for <xcon@ietf.org>; Fri, 23 Sep 2005 08:12:42 -0400 (EDT)
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EImWQ-0004r7-Dl
	for xcon@ietf.org; Fri, 23 Sep 2005 08:19:22 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	43BC94F0001; Fri, 23 Sep 2005 14:12:33 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Sep 2005 14:09:55 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 23 Sep 2005 14:09:55 +0200
Received: from [131.160.36.106] (EGIUM000L5C5TEU.lmf.ericsson.se
	[131.160.36.106])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 738552715;
	Fri, 23 Sep 2005 15:09:55 +0300 (EEST)
Message-ID: <4333F093.7050601@ericsson.com>
Date: Fri, 23 Sep 2005 15:09:55 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: XCON <xcon@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 23 Sep 2005 12:09:55.0540 (UTC)
	FILETIME=[B5C75140:01C5C037]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: Dave.Morgan@fmr.com
Subject: [XCON] Draft defining a Common Data Model for XCON
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Folks,

we have just submitted a draft defining a common data model for XCON.
Until it appears in the archives, you can fetch it from:

http://users.piuha.net/gonzalo/temp/draft-novo-xcon-common-data-model-00.txt

We have taken a stab at defining the XML schema of a common data model
for XCON. The idea would be that whichever conference policy protocol we
define, it uses this data model.

You comments are appreciated. We hope to have discussions on this topic
on the mailing list.

The following is the abstract of the draft:

    This document collects, organizes, and describes the conference
    variables that have been introduced in various protocol drafts of the
    XCON and SIPPING working groups.  The goal of this document is to
    allow the conference control protocols to use a unified common
    conference information data model for XCON.  This document formally
    defines an Extensible Markup Language (XML) Schema that represents
    the common conference information in a conferencing server.  The
    information is modeled as a series of elements, each of which
    contains a set of children and attributes.


Cheers,

Gonzalo


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



From xcon-bounces@ietf.org Mon Sep 26 22:25:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EK5A9-0001Bg-L5; Mon, 26 Sep 2005 22:25:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EK5A8-0001Bb-HQ
	for xcon@megatron.ietf.org; Mon, 26 Sep 2005 22:25:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25851
	for <xcon@ietf.org>; Mon, 26 Sep 2005 22:25:42 -0400 (EDT)
Received: from brinza.cc.columbia.edu ([128.59.29.8] ident=cu41754)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EK5HI-0006M2-1M
	for xcon@ietf.org; Mon, 26 Sep 2005 22:33:09 -0400
Received: from [192.168.0.31] (pool-141-153-174-94.mad.east.verizon.net
	[141.153.174.94]) (user=hgs10 mech=PLAIN bits=0)
	by brinza.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j8R2Pdma026918
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <xcon@ietf.org>; Mon, 26 Sep 2005 22:25:40 -0400 (EDT)
Message-ID: <4338ADCC.603@cs.columbia.edu>
Date: Mon, 26 Sep 2005 22:26:20 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xcon@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Subject: [XCON] Comments on xcon-framework-01
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

My basic concern with the document is that it suffers from metaphor 
overload. The document uses, at various times, terminology from 
object-oriented programming and data structures, architecture 
("blueprints"), XML schema, biology (cloning), Seattle haute couture 
("umbrella") and protocols (state) to refer to somewhat overlapping 
concepts. In passing, it introduces various one-time-use terms such as 
"umbrella". I was trying to read this from the perspective of an 
implementor that is conversant with object-oriented terminology (but not 
XCON discussions), but found the experience somewhat vertigo-inducing.

In the spirit of "send text", I'll shortly be sending text that (I hope) 
summarizes the intent of the framework, while trying to provide a 
shorter description that quickly gives the reader an overview of the 
basic ideas.

That text leaves out some of the details and examples, but for those the 
framework-01 document already has pretty good material.

In terms of document structure, it is difficult to read the document in 
sequence as the definitions make very little sense, given that they come 
in alphabetical order, before one has read most of the remainder of the 
document. I would suggest moving most of these definitions either into a 
glossary at the end of the document or at least after the overview.

I will be sending more detailed editorial comments to the authors.

Henning

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



From xcon-bounces@ietf.org Mon Sep 26 22:32:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EK5Gv-00027d-JD; Mon, 26 Sep 2005 22:32:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EK5Gu-00027X-Pf
	for xcon@megatron.ietf.org; Mon, 26 Sep 2005 22:32:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26136
	for <xcon@ietf.org>; Mon, 26 Sep 2005 22:32:42 -0400 (EDT)
Received: from serrano.cc.columbia.edu ([128.59.29.6] ident=cu41754)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EK5O4-0006W1-6s
	for xcon@ietf.org; Mon, 26 Sep 2005 22:40:09 -0400
Received: from [192.168.0.31] (pool-141-153-174-94.mad.east.verizon.net
	[141.153.174.94]) (user=hgs10 mech=PLAIN bits=0)
	by serrano.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j8R2WcPW003004
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <xcon@ietf.org>; Mon, 26 Sep 2005 22:32:41 -0400 (EDT)
Message-ID: <4338AF6F.8040306@cs.columbia.edu>
Date: Mon, 26 Sep 2005 22:33:19 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: xcon@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Subject: [XCON] framework-01 5.4 (user)
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

I think the user concept in Section 5.4 is more confusing than helpful. 
We have several kinds of identifiers that only make sense within their 
respective protocols:
- a signaling identity (SIP, H.323 or tel URI, but maybe XMPP, too)
- a BFCP identity (hopefully, referring to a SIP or tel URI), which 
isn't precisely identified, but presumably means USER-URI (BFCP 5.2.15)
- authentication identities, which may or may not resemble those URIs 
and may differ between different protocols, including the conference 
control protocol

The signaling identity may or may not be asserted by Digest authentication.

I think this needs to be made more precise to avoid confusion.

Henning

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



From xcon-bounces@ietf.org Tue Sep 27 11:27:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKHMq-0005Nc-1R; Tue, 27 Sep 2005 11:27:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKHMl-0005NM-7b
	for xcon@megatron.ietf.org; Tue, 27 Sep 2005 11:27:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19129
	for <XCON@ietf.org>; Tue, 27 Sep 2005 11:27:33 -0400 (EDT)
From: Umesh.Chandra@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKHU1-0000UF-Cr
	for XCON@ietf.org; Tue, 27 Sep 2005 11:35:06 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j8RFPtMq013226; Tue, 27 Sep 2005 18:25:59 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Sep 2005 18:27:25 +0300
Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Sep 2005 10:27:23 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] Comments on Media Policy Templates 
Date: Tue, 27 Sep 2005 10:27:22 -0500
Message-ID: <815E2AF6A087FF45A68EF2F310ADE1119C36C4@daebe102.NOE.Nokia.com>
Thread-Topic: [XCON] Comments on Media Policy Templates 
Thread-Index: AcWelYRVWtQvSnhoS/abrU/qa09Fygk4Znjw
To: <Dave.Morgan@FMR.COM>, <XCON@ietf.org>
X-OriginalArrivalTime: 27 Sep 2005 15:27:23.0265 (UTC)
	FILETIME=[F539AF10:01C5C377]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hello Dave
=20
Thanks for reviewing and giving your comments regarding the template
draft.=20
=20
As you have realized this draft is still under heavy development stage
and we are trying to come up the client control capabilities of very
basic conferences. But i feel that the common conference information
schema and the template can be done simulatenously, since for the
protocol  (conference and media control) development the client
capabilities are required. I feel both the schemas (templates and common
conference) are mutually exclusive and can be done together. The
templates defines the capabiltiies that are being offered by the
conference server and it would be important to define the different
conference scenarios initially so as to aid the development of protocol.
Any other opinion and thoughts ?
=20
BR
=20
Umesh


	I see that the draft is currently under major revision, and that
we should be thinking about the client controls, but first I think we
need to do two things, so let me put this to the list for discussion.
The first is to specify a common (grand unified) conference object data
model that all the protocols can operate on.  What we are doing in XCON
is specifying the necessary XML definitions piecemeal with each draft.
I think we should pull together the existing pieces into one data model
and let the authors of the protocols use that model and request it to be
extended as necessary.  Once the data model and protocols are specified,
then I think the client capabilities can be finalized.  To me the client
capabilities are like the capstone in the XCon WG, it should be the last
thing to be finalized.   I'm interested in other people's thoughts. =20
	=20


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



From xcon-bounces@ietf.org Tue Sep 27 16:17:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKLss-0000gk-N3; Tue, 27 Sep 2005 16:17:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKLsr-0000a8-Rl
	for xcon@megatron.ietf.org; Tue, 27 Sep 2005 16:17:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13142
	for <xcon@ietf.org>; Tue, 27 Sep 2005 16:16:57 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKM05-0002Nd-8Q
	for xcon@ietf.org; Tue, 27 Sep 2005 16:24:32 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j8RKGdF23543; Tue, 27 Sep 2005 16:16:39 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] Comments on xcon-framework-01
Date: Tue, 27 Sep 2005 15:16:38 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D264@zrc2hxm1.corp.nortel.com>
Thread-Topic: [XCON] Comments on xcon-framework-01
Thread-Index: AcXDCwgzCwyqzQdwRq60cmhQ6AJ79wAlLPdA
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>, <xcon@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hi Henning,

Thank you for taking time to review the document and provide us this
high level feedback. I do agree that the flow of the document and the
order of the presentation of the information could be improved, with
perhaps a high level overview of the object model approach upfront
(which sounds like the detailed text you're proposing to send?).   It
would definitely be better to have the terminology at least after the
Overview section.  I think we need some basic terminology upfront (as
opposed to a glossary at the end), but perhaps we've overloaded the
definitions themselves by including too much detail upfront.   And, we
are certainly open to some changes in terminology and reducing the
number of metaphors, although in some cases the usage is quite accurate
(e.g. "cloning" is a common OO term and quite applicable to the model
proposed). =20

We would certainly appreciate your further detailed comments.=20

And, just a note to the other reviewers, whose comments we also very
much appreciate.  I think we have now received comments from the
majority of reviewers and we will be responding to the detailed
comments, with proposed resolution over the next several days. We'll
post individual emails for any issues requiring additional WG feedback.=20

Thanks,
Mary.


-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Henning Schulzrinne
Sent: Monday, September 26, 2005 9:26 PM
To: xcon@ietf.org
Subject: [XCON] Comments on xcon-framework-01


My basic concern with the document is that it suffers from metaphor=20
overload. The document uses, at various times, terminology from=20
object-oriented programming and data structures, architecture=20
("blueprints"), XML schema, biology (cloning), Seattle haute couture=20
("umbrella") and protocols (state) to refer to somewhat overlapping=20
concepts. In passing, it introduces various one-time-use terms such as=20
"umbrella". I was trying to read this from the perspective of an=20
implementor that is conversant with object-oriented terminology (but not

XCON discussions), but found the experience somewhat vertigo-inducing.

In the spirit of "send text", I'll shortly be sending text that (I hope)

summarizes the intent of the framework, while trying to provide a=20
shorter description that quickly gives the reader an overview of the=20
basic ideas.

That text leaves out some of the details and examples, but for those the

framework-01 document already has pretty good material.

In terms of document structure, it is difficult to read the document in=20
sequence as the definitions make very little sense, given that they come

in alphabetical order, before one has read most of the remainder of the=20
document. I would suggest moving most of these definitions either into a

glossary at the end of the document or at least after the overview.

I will be sending more detailed editorial comments to the authors.

Henning

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


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



From xcon-bounces@ietf.org Wed Sep 28 17:14:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKjGL-0006Zd-0J; Wed, 28 Sep 2005 17:14:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKjGF-0006Z0-HG
	for xcon@megatron.ietf.org; Wed, 28 Sep 2005 17:14:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12958
	for <xcon@ietf.org>; Wed, 28 Sep 2005 17:14:41 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKjNl-0003vl-WF
	for xcon@ietf.org; Wed, 28 Sep 2005 17:22:30 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.2499); 
	Wed, 28 Sep 2005 14:14:28 -0700
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.14]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 28 Sep 2005 14:14:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] Draft defining a Common Data Model for XCON
Date: Wed, 28 Sep 2005 14:14:28 -0700
Message-ID: <DD07841287D0AD428833021705E0D14E0656B45D@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [XCON] Draft defining a Common Data Model for XCON
Thread-Index: AcXAOH2cELP+jbmbQZarFQaGAmdXFwDdwS7g
From: "Orit Levin" <oritl@microsoft.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>,
	"XCON" <xcon@ietf.org>
X-OriginalArrivalTime: 28 Sep 2005 21:14:28.0283 (UTC)
	FILETIME=[9C5100B0:01C5C471]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable
Cc: Dave.Morgan@fmr.com
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hi guys,

It's really good that we have more people who have the cycles to invest
into this work. I am still working on the next CCCP draft which will
incorporate the lessons that we learned internally. One of these is, for
example, the extensibility mechanism that I will include in the upcoming
CCCP draft and will be relevant to this discussion as well.

These are my thoughts about the draft:

1. Although in the Introduction the draft says that it is compliant with
the Conference Event Package, it is not clear whether the draft aims at
expanding the 'conference-type' defined in the package or it aims at
redefining most of the information in a new namespace (as hinted by the
xmlns:tns=3D"urn:ietf:params:xml:ns:common-conference-schema" in the
Example).

2. If the intention is the latter, I think that we need to understand
what the practical usage of the new common-conference-schema  namespace
is. I guess that you had in mind a data manipulation protocol that
operates on a conference object of that type. I went though a similar
exercise in CCCP. My conclusion is that you don't necessarily need or
want to schematize all this information under a single XML tree
belonging to a new namespace. For example, in CCCP we are referring to
the Conference Event Package definitions without redefining any of them.
Along the same lines - it is really not a good practice to redefine the
XML definitions with their semantics in multiple documents.

3. That being said, I am sure that many new elements in the draft are
good candidates for the conference package extensions. Any information
that potentially needs to be distributed to the conference subscribers
would fall under this category. I suggest to start working together on
the Conference Package Extensions draft in parallel to any other
efforts. Just to note, the way the current draft "extends" (in case this
was the intention) the conference package schema in the Example - is not
XML compliant with the conference event package schema itself. According
to the Conference Event Package schema - any extension MUST come from
"other" namespace with all the syntactic implications.
=20
4. In the past, the main debate/disconnect around the "conference data
model" was not so much about the common information, but about the
template: what it is, how it looks like and, not less importantly, how
the template fits into or lives side-by-side with the conference-type of
the Conference Event Package. Your draft seems to suggest (under all the
disclaimers above ;-) that the templates are included (as extensions)
inside the conference-type. I personally like this approach because it
automatically allows for distribution of any included information
through the conference package notifications. (Of cause, only the
information complying with the local policies will be included.) To
rephrase, any information that is not defined as the Conference Event
Package extension will require a separate mechanism (or at least a
different event package) to be communicated to the interested parties.

5. Still we desperately need to conclude how a template relates to the
conference data definition (and capture this in the framework)...

Orit.=20

> -----Original Message-----
> From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20
> Behalf Of Gonzalo Camarillo
> Sent: Friday, September 23, 2005 5:10 AM
> To: XCON
> Cc: Dave.Morgan@fmr.com
> Subject: [XCON] Draft defining a Common Data Model for XCON
>=20
> Folks,
>=20
> we have just submitted a draft defining a common data model for XCON.
> Until it appears in the archives, you can fetch it from:
>=20
> http://users.piuha.net/gonzalo/temp/draft-novo-xcon-common-dat
> a-model-00.txt
>=20
> We have taken a stab at defining the XML schema of a common=20
> data model for XCON. The idea would be that whichever=20
> conference policy protocol we define, it uses this data model.
>=20
> You comments are appreciated. We hope to have discussions on=20
> this topic on the mailing list.
>=20
> The following is the abstract of the draft:
>=20
>     This document collects, organizes, and describes the conference
>     variables that have been introduced in various protocol=20
> drafts of the
>     XCON and SIPPING working groups.  The goal of this document is to
>     allow the conference control protocols to use a unified common
>     conference information data model for XCON.  This=20
> document formally
>     defines an Extensible Markup Language (XML) Schema that represents
>     the common conference information in a conferencing server.  The
>     information is modeled as a series of elements, each of which
>     contains a set of children and attributes.
>=20
>=20
> Cheers,
>=20
> Gonzalo
>=20
>=20
> _______________________________________________
> XCON mailing list
> XCON@ietf.org
> https://www1.ietf.org/mailman/listinfo/xcon
>=20

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



From xcon-bounces@ietf.org Thu Sep 29 08:38:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKxg1-0003Bu-T6; Thu, 29 Sep 2005 08:38:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKxg0-00039H-5E
	for xcon@megatron.ietf.org; Thu, 29 Sep 2005 08:38:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08319
	for <xcon@ietf.org>; Thu, 29 Sep 2005 08:38:14 -0400 (EDT)
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKxne-0000nY-Nj
	for xcon@ietf.org; Thu, 29 Sep 2005 08:46:11 -0400
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 80BF351D; 
	Thu, 29 Sep 2005 14:38:07 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 29 Sep 2005 14:37:53 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 29 Sep 2005 14:37:52 +0200
Received: from [131.160.36.106] (EGIUM000L5C5TEU.lmf.ericsson.se
	[131.160.36.106])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 5AC3F256E;
	Thu, 29 Sep 2005 15:37:52 +0300 (EEST)
Message-ID: <433BE01F.8010606@ericsson.com>
Date: Thu, 29 Sep 2005 15:37:51 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Orit Levin <oritl@microsoft.com>
Subject: Re: [XCON] Draft defining a Common Data Model for XCON
References: <DD07841287D0AD428833021705E0D14E0656B45D@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <DD07841287D0AD428833021705E0D14E0656B45D@RED-MSG-52.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Sep 2005 12:37:52.0589 (UTC)
	FILETIME=[9BDB2FD0:01C5C4F2]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: 7bit
Cc: Dave.Morgan@fmr.com, XCON <xcon@ietf.org>
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hi Orit,

thanks for your comments.

Regarding the content type to use for the common conference schema, 
there are two possibilities, as you suggest. The first one would be to 
define a brand new schema importing elements from different existing 
namespaces. The other possibility would be to take conference-info as a 
base, and extend it using elements from other namespaces.

If any case, we would need to define a few extensions to the conference 
package to define some new elements that have not been defined so far. 
We currently define those elements in the draft, but you are right that 
they probably belong to different drafts.

We lean towards the second alternative. That is, using conference-info 
as a base, and extend it using elements from other namescapes.

Now, the question is whether or not it is useful to have a document like 
this draft stating the the common conference schema consists of 
extensions to conference-info and describing the extensions that have 
been defined so far.

The documents defining the new elements that have not been defined so 
far (e.g., floor control stuff) are, of course, needed. Once we agree on 
how to proceed we will move their definitions to different documents.

Thanks,

Gonzalo


Orit Levin wrote:
> Hi guys,
> 
> It's really good that we have more people who have the cycles to invest
> into this work. I am still working on the next CCCP draft which will
> incorporate the lessons that we learned internally. One of these is, for
> example, the extensibility mechanism that I will include in the upcoming
> CCCP draft and will be relevant to this discussion as well.
> 
> These are my thoughts about the draft:
> 
> 1. Although in the Introduction the draft says that it is compliant with
> the Conference Event Package, it is not clear whether the draft aims at
> expanding the 'conference-type' defined in the package or it aims at
> redefining most of the information in a new namespace (as hinted by the
> xmlns:tns="urn:ietf:params:xml:ns:common-conference-schema" in the
> Example).
> 
> 2. If the intention is the latter, I think that we need to understand
> what the practical usage of the new common-conference-schema  namespace
> is. I guess that you had in mind a data manipulation protocol that
> operates on a conference object of that type. I went though a similar
> exercise in CCCP. My conclusion is that you don't necessarily need or
> want to schematize all this information under a single XML tree
> belonging to a new namespace. For example, in CCCP we are referring to
> the Conference Event Package definitions without redefining any of them.
> Along the same lines - it is really not a good practice to redefine the
> XML definitions with their semantics in multiple documents.
> 
> 3. That being said, I am sure that many new elements in the draft are
> good candidates for the conference package extensions. Any information
> that potentially needs to be distributed to the conference subscribers
> would fall under this category. I suggest to start working together on
> the Conference Package Extensions draft in parallel to any other
> efforts. Just to note, the way the current draft "extends" (in case this
> was the intention) the conference package schema in the Example - is not
> XML compliant with the conference event package schema itself. According
> to the Conference Event Package schema - any extension MUST come from
> "other" namespace with all the syntactic implications.
>  
> 4. In the past, the main debate/disconnect around the "conference data
> model" was not so much about the common information, but about the
> template: what it is, how it looks like and, not less importantly, how
> the template fits into or lives side-by-side with the conference-type of
> the Conference Event Package. Your draft seems to suggest (under all the
> disclaimers above ;-) that the templates are included (as extensions)
> inside the conference-type. I personally like this approach because it
> automatically allows for distribution of any included information
> through the conference package notifications. (Of cause, only the
> information complying with the local policies will be included.) To
> rephrase, any information that is not defined as the Conference Event
> Package extension will require a separate mechanism (or at least a
> different event package) to be communicated to the interested parties.
> 
> 5. Still we desperately need to conclude how a template relates to the
> conference data definition (and capture this in the framework)...
> 
> Orit. 
> 
> 
>>-----Original Message-----
>>From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On 
>>Behalf Of Gonzalo Camarillo
>>Sent: Friday, September 23, 2005 5:10 AM
>>To: XCON
>>Cc: Dave.Morgan@fmr.com
>>Subject: [XCON] Draft defining a Common Data Model for XCON
>>
>>Folks,
>>
>>we have just submitted a draft defining a common data model for XCON.
>>Until it appears in the archives, you can fetch it from:
>>
>>http://users.piuha.net/gonzalo/temp/draft-novo-xcon-common-dat
>>a-model-00.txt
>>
>>We have taken a stab at defining the XML schema of a common 
>>data model for XCON. The idea would be that whichever 
>>conference policy protocol we define, it uses this data model.
>>
>>You comments are appreciated. We hope to have discussions on 
>>this topic on the mailing list.
>>
>>The following is the abstract of the draft:
>>
>>    This document collects, organizes, and describes the conference
>>    variables that have been introduced in various protocol 
>>drafts of the
>>    XCON and SIPPING working groups.  The goal of this document is to
>>    allow the conference control protocols to use a unified common
>>    conference information data model for XCON.  This 
>>document formally
>>    defines an Extensible Markup Language (XML) Schema that represents
>>    the common conference information in a conferencing server.  The
>>    information is modeled as a series of elements, each of which
>>    contains a set of children and attributes.
>>
>>
>>Cheers,
>>
>>Gonzalo
>>

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



From xcon-bounces@ietf.org Thu Sep 29 10:20:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzGi-0006RT-04; Thu, 29 Sep 2005 10:20:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzGg-0006RO-RU
	for xcon@megatron.ietf.org; Thu, 29 Sep 2005 10:20:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14137
	for <xcon@ietf.org>; Thu, 29 Sep 2005 10:20:12 -0400 (EDT)
Received: from mtagate3.de.ibm.com ([195.212.29.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKzOJ-0003R6-6B
	for xcon@ietf.org; Thu, 29 Sep 2005 10:28:11 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate3.de.ibm.com (8.12.10/8.12.10) with ESMTP id j8TEJlTZ165438
	for <xcon@ietf.org>; Thu, 29 Sep 2005 14:19:47 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com
	[9.149.165.228])
	by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP
	id j8TEJk9P178760
	for <xcon@ietf.org>; Thu, 29 Sep 2005 16:19:46 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id
	j8TEJktA001957 for <xcon@ietf.org>; Thu, 29 Sep 2005 16:19:46 +0200
Received: from [9.149.167.114] (d12mc102.megacenter.de.ibm.com [9.149.167.114])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id
	j8TEJkch001954 for <xcon@ietf.org>; Thu, 29 Sep 2005 16:19:46 +0200
To: xcon@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Build V70_07192005NP July 19, 2005
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Message-ID: <OFFCBABC6F.79968A4C-ON4325708B.004D47C9-4325708B.004ECC4A@il.ibm.com>
Date: Thu, 29 Sep 2005 17:19:45 +0300
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Build V70_M6_06302005
	Beta 4 SP0805|June 30, 2005) at 29/09/2005 17:19:46,
	Serialize complete at 29/09/2005 17:19:46
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [XCON] Comments on xcon-framework-01
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0821998639=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multipart message in MIME format.
--===============0821998639==
Content-Type: multipart/alternative;
	boundary="=_alternative 004EACF94325708B_="

This is a multipart message in MIME format.
--=_alternative 004EACF94325708B_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

I like the general direction of the document.

I think that we need to simplify the model. For example I do not 
understand the concept of conference object.
It seems very similar to conference state and it is more  what a program 
that implements the model will do
rather then general model.

--Avshalom



--=_alternative 004EACF94325708B_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I like the general direction of the
document.</font>
<br>
<br><font size=2 face="sans-serif">I think that we need to simplify the
model. For example I do not understand the concept of conference object.</font>
<br><font size=2 face="sans-serif">It seems very similar to conference
state and it is more &nbsp;what a program that implements the model will
do</font>
<br><font size=2 face="sans-serif">rather then general model.</font>
<br>
<br><font size=2 face="sans-serif">--Avshalom<br>
<br>
<br>
</font>
--=_alternative 004EACF94325708B_=--


--===============0821998639==
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://www1.ietf.org/mailman/listinfo/xcon

--===============0821998639==--




From xcon-bounces@ietf.org Thu Sep 29 10:49:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKzij-0006et-D7; Thu, 29 Sep 2005 10:49:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EKzig-0006ea-Vu
	for xcon@megatron.ietf.org; Thu, 29 Sep 2005 10:49:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16769
	for <xcon@ietf.org>; Thu, 29 Sep 2005 10:49:08 -0400 (EDT)
Received: from cluster-b.mailcontrol.com ([217.68.146.190]
	helo=rly09b.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKzqJ-0004JG-IW
	for xcon@ietf.org; Thu, 29 Sep 2005 10:57:07 -0400
Received: from GBNEWP0758M.eu.ubiquity.net ([62.172.205.164])
	by rly09b.srv.mailcontrol.com (MailControl) with ESMTP id
	j8TEmrff002018; Thu, 29 Sep 2005 15:48:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 29 Sep 2005 15:48:53 +0100
Message-ID: <45730E094814E44488F789C1CDED27AE031187DE@gbnewp0758m.eu.ubiquity.net>
Thread-Topic: MSRP Conferencing
Thread-Index: AcXFBOkI58MvTIfuTJi6BUs/pl1Ijg==
From: "Chris Boulton" <cboulton@ubiquity.net>
To: <xcon@ietf.org>
X-Scanned-By: MailControl A-05-40-00 (www.mailcontrol.com) on 10.66.0.119
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: 
Subject: [XCON] MSRP Conferencing
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2106085180=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2106085180==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5C504.E90937F7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5C504.E90937F7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

=20

            A new version of the 'MSRP Conferencing' draft has been
submitted to the IETF archives and can be retrieved from the following
link:-

=20

http://www.ietf.org/internet-drafts/draft-boulton-xcon-msrp-conferencing
-02

=20

All feedback greatly received.

=20

Best Regards,

=20

Chris.

=20



Information contained in this e-mail and any attachments are intended for t=
he use of the addressee only, and may contain confidential information of U=
biquity Software Corporation.  All unauthorized use, disclosure or distribu=
tion is strictly prohibited.  If you are not the addressee, please notify t=
he sender immediately and destroy all copies of this email.  Unless otherwi=
se expressly agreed in writing signed by an officer of Ubiquity Software Co=
rporation, nothing in this communication shall be deemed to be legally bind=
ing.  Thank you.


------_=_NextPart_001_01C5C504.E90937F7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>Hi All,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; A
new version of the &#8216;MSRP Conferencing&#8217; draft has been submitted=
 to
the IETF archives and can be retrieved from the following link:-</span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'><a
href=3D"http://www.ietf.org/internet-drafts/draft-boulton-xcon-msrp-confere=
ncing-02">http://www.ietf.org/internet-drafts/draft-boulton-xcon-msrp-confe=
rencing-02</a></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>All feedback greatly received.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>Best Regards,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>Chris.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB style=
=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;</span></font></p>

</div>

<br><br>
<FONT face=3DVerdana size=3D1 colour=3D"#cccccc">Information contained in t=
his e-mail and any attachments are intended for the use of the addressee on=
ly, and may contain confidential information of Ubiquity Software Corporati=
on. All unauthorized use, disclosure or distribution is strictly prohibited=
.&nbsp; If you are not the addressee, please notify the sender immediately =
and destroy all copies of this email.&nbsp; Unless otherwise expressly agre=
ed in writing signed by an officer of Ubiquity Software Corporation, nothin=
g in this communication shall be deemed to be legally binding. Thank-you</F=
ONT>
</body>

</html>

------_=_NextPart_001_01C5C504.E90937F7--


--===============2106085180==
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://www1.ietf.org/mailman/listinfo/xcon

--===============2106085180==--




From xcon-bounces@ietf.org Thu Sep 29 18:36:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EL70X-000655-E5; Thu, 29 Sep 2005 18:36:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EL70V-000650-Hm
	for xcon@megatron.ietf.org; Thu, 29 Sep 2005 18:36:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20153
	for <xcon@ietf.org>; Thu, 29 Sep 2005 18:36:00 -0400 (EDT)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56]
	helo=zcars04e.ca.nortel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL78F-0002NQ-0G
	for xcon@ietf.org; Thu, 29 Sep 2005 18:44:03 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	j8TMXL109416; Thu, 29 Sep 2005 18:33:21 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [XCON] Dave's Comments on draft-ietf-xcon-framework-01.txt
Date: Thu, 29 Sep 2005 17:35:01 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D27E@zrc2hxm1.corp.nortel.com>
Thread-Topic: [XCON] Dave's Comments on draft-ietf-xcon-framework-01.txt
Thread-Index: AcWSJB6UcoV4MVLWSSavryDRfvFKogxfMZdg
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Morgan, Dave" <Dave.Morgan@FMR.COM>
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 8f9ac37b081a3249085c4867ee1404d4
Cc: xcon@ietf.org
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0392723995=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0392723995==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5C546.0780879A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5C546.0780879A
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Dave,
=20
Thanks for your eagle-eye review.  Responses embedded below [MB] as to
how I'm incorporating your suggestions into the=20
-02 version.=20
=20
Mary=20

	-----Original Message-----
	From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
Behalf Of Morgan, Dave
	Sent: Tuesday, July 26, 2005 3:54 PM
	To: XCON@ietf.org
	Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt
=09
=09

	Mary, Chris, and Orit:=20

	The framework-01 doc seems to be in very good shape and
hopefully we can use our time productively next week to close out the
TBDs.  I have several nits and some general comments - more along the
lines of impressions, after reading the document.  Hopefully posting
something to the discussion list will help us start thinking about what
we have to accomplish next week.

	Page 11, Section 4.3.  That fact that we refer to conference
policies but don't include them anywhere in our data model is bothering
me.  You say on page 8:

	   "A Conference Object is of type 'Conference Object Type'
which is=20
	   comprised of two distinct components: the 'Common Conference=20
	   Information Type' and the 'Conference Template Type', as
illustrated=20
	   in Figure 2.  Each of these types is a placeholder for
including=20
	   potentially multiple sub-types."=20
	You say in 4.3 that policies =3D rights, permissions and
limitations and that they apply to the Conference Object as a whole.  So
I'm thinking these policies are outside the data model.  Then in
paragraph 3 you state that "The permissions and limits are specified as
an integral part of the Conference Object Type."  In Figures 6, 7, and
8, the conference policies are "attached" to the side of the Conference
Object.  These policies also appear to be cloned!  So I am relieved when
you say:

	 "A more general rule mechanism, beyond the functionality
provided by=20
	   the permissions and limits, is an item for future study for
the XCON=20
	   WG."=20
	We do need to decide if the policies will be part of the
Conference Object, or if the policies will be external to the Conference
Object, but will be able to read/write to the Conference Object.  In
looking at draft-ietf-sipping-conferencing-framework-05.txt there is a
Conference Policy Server explicitly described.=20

	[MB] I see why you have concerns, but we did explicitly agree at
the Interim in Jan (and confirmed on the mailing list) that this
framework was not defining a separate Conference Policy server, but
rather having the policies as an integral part of the conference object.
What we're missing is more detailed discussion of that within this
framework document and a good way to show them in the diagram of the
data model, without the implication that they're separate. We have put
in a placeholder for more detailed discussions in a separate document,
but it's clear from your concerns and a similar one raised by Umesh that
this is something that needs resoluton in this document. I'll post a
separate item on the list to discuss this point.=20

	Page 21, Section 6.3. In previous discussions (along the lines
of DP4) I believe we tried to distinguish between "Blueprint" and
template so that they mean two different things.  The template
explicitly refers to the Conference Template Type or its' current
parameters.  The "blueprint" is the Conference Object that will be
cloned to create a conference object for reservation.  So I was a bit
uncomfortable when you said (in paragraph 2) "a list of the Conference
Object 'blueprints' (or templates) the system supports."   =20

	[MB]  Agreed.  I'll remove that text in parenthesis. Related to
this is a general issue on whether we need the two distinct terms
"template" and "blueprint" - we've debated this before and we need to
resolve this.  I'll post a separate email on this.=20

	Later on, in paragraph 4, it says:=20
	   "The selected blueprint with its default values is copied by
the=20
	   client into a newly created Conference  Object, ..."=20
	Can we say its "cloned" instead of "copied" by the client.  I'm
not even sure we should specify who exactly is doing the cloning.  It's
probably more likely that the client communicates via CPP to the
Conference Control Server, which clones the parent.  =20

	[MB] Agreed.  Quite interesting, Oscar made the opposite
comment, but I think by clarifying the terminology overall, based on the
mark-ups I have from Henning and some WG discussion (separate email), we
should be able to resolve this inconsistency.=20

	Page 27, Section 7.3. I hope we spend more time discussing (and
agreeing on) the mechanism for CCP next week.  In the first sentence of
this paragraph you say:

	   "The XCON working group charter includes the development of a
protocol=20
	   or a set of protocols for controlling the state of a
Conference=20
	   Object and for retrieving its state."=20
	I would add to that the ability to create and manipulate
conference parameters, in fact any parameters of the Conference Object
Type.  Section 7.3.5 (SOAP), paragraph 3 states it fairly well:

	    " _____ is proposed as the mechanism for object content
manipulation and=20
	   state retrieval for the XCON data (model)." =20

	[MB] Agreed.  I'll reword similar to what you suggest.=20

	Page 31, Section 7.4. I would agree with bullet 5, the
discussion related to BFCP is still too detailed.  In particular the
lengthy authentication paragraph which ends this section is not
necessary as authentication and security should be covered in Section
10.=20

	[MB] I agree; this isn't consistent with security discussions in
the rest of the document and I've worked this into section 10.=20

	Page 37, Section 9.  After reading this section on the
relationship between the SIPPING and XCON frameworks, I had to ask
myself why we don't supersede the SIPPING framework [9].  I glanced at
draft-ietf-sipping-conferencing-framework-05.txt (posted on May 27th)
and even with a quick read I can see there are some significant
differences as noted here.  We can probably tolerate some differences
because these are just framework docs.  But shouldn't the respective
authors attempt to iron out the major differences?=20

	[MB]  Both the sipping-conferencing-framework and this XCON FW
match in terms of the protocol and other normative aspects that are
required for SIP based conferencing.  So, although, the high level
models don't match (e.g. Policy models),  the XCON FW does not change
any of the fundamental SIP based protocol aspects.  I think we have to
view this situation as "water under the bridge".  Ideally, it would have
been nice to have a single framework, but clearly having two separate
documents was the right decision since the SIPPING documents are in the
RFC Editor's Queue, thus providing stability to developers and other
SDOs with dependencies on those docs and from a process perspective,
it's not possible to make significant changes to those docs.   We did
decide way long ago that the SIPPING conferencing framework was not the
ideal starting point for the XCON FW (i.e. I think we have agreed as a
WG  that there is a reason for the differences, but I'll let the chairs
step in if that's not so).    Certainly, we'd love this document to not
be too far behind the SIPPING docs in getting published, so that
developer's have a common baseline for the more advanced functionality
that this FW enables, while still being compatible with what they've
developed for SIP.  If this concept isn't clear in the text, we need to
make sure that it is.=20

	Page 39, Section 10. At the end of the Security Consideration
section there's a discussion of hidden and anonymous parties.  I would
like to request that call recording be added to the last sentence so
that it reads:

	  " 'Hidden' status is often used by robot participants of a
conference, for example for call =20
	     recording, and is also used in many call center
conferencing situations." =20

	[MB] Agreed.

=09
	Thanks=20

	NITs  =20

	=20
	1. Page 6, Section 3, paragraph 5, ends with unmatched
parenthesis =20

	 [MB] Replaced that sentence with the following:

	 "  A Conference Object is accessible using the protocols,
identified  in Figure 1."

=09
	2. Page 13, Section 5.3, paragraph 3, "stages are addressing
using CCP" should read "addressed"   [MB] Fixed.=20
	3. Page 17, Section 5.4, Figure 5 should be titled "Conference
User Identifier Mapping" [MB] Fixed.=20
	4. Page 18, Section 6.1, Figure 6 is described but not
explicitly referenced in Section 6.1  [MB] Added a paragraph and deleted
the sentence referencing future XCON specs.

	5. Page 30, Section 7.4, bullets are not numbered in sequence
[MB] Fixed by removing and rearranging the notes (4 moved to 1st
paragraph, where any such discussion would need to be and have moved the
security discussion to section 10.  I think this section is no longer so
overloaded or detailed and that any remaining changes would be based on
changes earlier in the doc that might ripple down to this section (eg.
identifiers).=20

=09
	6. Page 36, Section 8.3, paragraph 3, ends with unmatched
parenthesis    [MB] Fixed.=20
	7. Page 39, Section 10, paragraph 7, "to enter a PIN makes is
fairly hard" should read "makes it" [MB] Fixed.
=09
=09

=09
------------------------------------------------------------------------

	David P. Morgan, PhD=20
	VP, Architecture & Planning=20
	Fidelity Investments Systems Company - Telecom=20
	Phone:  617 563-2178=20
	Fax:      617 385 2122=20
	Mailing: 82 Devonshire St, MZ V8C=20
	            Boston, MA 02109-3614=20
	Office:   245 Summer Street, 8th Floor=20




------_=_NextPart_001_01C5C546.0780879A
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D333252020-27092005>Dave,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D333252020-27092005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D333252020-27092005>Thanks=20
for your eagle-eye review.&nbsp; Responses embedded below [MB] as to how =
I'm=20
incorporating your suggestions into the </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D333252020-27092005>-02=20
version. </SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>Mary</FONT></SPAN> </FONT></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] <B>On Behalf Of=20
  </B>Morgan, Dave<BR><B>Sent:</B> Tuesday, July 26, 2005 3:54 =
PM<BR><B>To:</B>=20
  XCON@ietf.org<BR><B>Subject:</B> [XCON] Comments on=20
  draft-ietf-xcon-framework-01.txt<BR><BR></FONT></DIV><!-- Converted =
from text/rtf format -->
  <P><FONT face=3D"Times New Roman">Mary, Chris, and Orit:</FONT> </P>
  <P><FONT face=3D"Times New Roman">The framework-01 doc seems to be in =
very good=20
  shape and hopefully we can use our time productively next week to =
close out=20
  the TBDs.&nbsp; I have several nits and some general comments &#8211; =
more along the=20
  lines of impressions, after reading the document.&nbsp; Hopefully =
posting=20
  something to the discussion list will help us start thinking about =
what we=20
  have to accomplish next week.</FONT></P>
  <P><FONT face=3D"Times New Roman">Page 11, Section 4.3.&nbsp; That =
fact that we=20
  refer to conference policies but don&#8217;t include them anywhere in =
our data model=20
  is bothering me.&nbsp; You say on page 8:</FONT></P>
  <P><FONT face=3D"Times New Roman">&nbsp;&nbsp; &#8220;A Conference =
Object is of type=20
  'Conference Object Type' which is</FONT> <BR><FONT=20
  face=3D"Times New Roman">&nbsp;&nbsp; comprised of two distinct =
components: the=20
  'Common Conference</FONT> <BR><FONT face=3D"Times New =
Roman">&nbsp;&nbsp;=20
  Information Type' and the 'Conference Template Type', as =
illustrated</FONT>=20
  <BR><FONT face=3D"Times New Roman">&nbsp;&nbsp; in Figure 2.&nbsp; =
Each of these=20
  types is a placeholder for including</FONT> <BR><FONT=20
  face=3D"Times New Roman">&nbsp;&nbsp; potentially multiple =
sub-types.&#8221;</FONT>=20
  <BR><FONT face=3D"Times New Roman">You say in 4.3 that policies =3D =
rights,=20
  permissions and limitations and that they apply to the Conference =
Object as a=20
  whole.&nbsp; So I&#8217;m thinking these policies are outside the data =
model.&nbsp;=20
  Then in paragraph 3 you state that &#8220;The permissions and limits =
are specified=20
  as an integral part of the Conference Object Type.&#8221;&nbsp; In =
Figures 6, 7, and=20
  8, the conference policies are &#8220;attached&#8221; to the side of =
the Conference=20
  Object.&nbsp; These policies also appear to be cloned!&nbsp; So I am =
relieved=20
  when you say:</FONT></P>
  <P><FONT face=3D"Times New Roman">&nbsp;&#8220;A more general rule =
mechanism, beyond=20
  the functionality provided by</FONT> <BR><FONT=20
  face=3D"Times New Roman">&nbsp;&nbsp; the permissions and limits, is =
an item for=20
  future study for the XCON</FONT> <BR><FONT face=3D"Times New =
Roman">&nbsp;&nbsp;=20
  WG.&#8221;</FONT> <BR><FONT face=3D"Times New Roman">We do need to =
decide if the=20
  policies will be part of the Conference Object, or if the policies =
will be=20
  external to the Conference Object, but will be able to read/write to =
the=20
  Conference Object.&nbsp; In looking at=20
  draft-ietf-sipping-conferencing-framework-05.txt there is a Conference =
Policy=20
  Server explicitly described.</FONT><FONT face=3DArial size=3D2><SPAN=20
  class=3D333252020-27092005>&nbsp;</SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2><SPAN class=3D333252020-27092005><FONT=20
  color=3D#0000ff>[MB]</FONT>&nbsp;<FONT color=3D#0000ff>I see why you =
have=20
  concerns, but we did explicitly agree at the Interim in Jan (and =
confirmed on=20
  the mailing list) that this framework was not defining a separate =
Conference=20
  Policy server, but rather having the policies as an integral part of =
the=20
  conference object.&nbsp; What we're missing is more detailed =
discussion of=20
  that within this framework document and a good way to show them in the =
diagram=20
  of the data model, without the implication that they're separate. We =
have put=20
  in a placeholder for more detailed discussions in a separate document, =
but=20
  it's clear from your concerns and a similar one raised by Umesh that =
this is=20
  something that needs resoluton in this document. I'll post a separate =
item on=20
  the list to discuss this point. </FONT></SPAN></FONT></P>
  <P><FONT face=3D"Times New Roman">Page 21, Section 6.3. In previous =
discussions=20
  (along the lines of DP4) I believe we tried to distinguish between =
&#8220;Blueprint&#8221;=20
  and template so that they mean two different things.&nbsp; The =
template=20
  explicitly refers to the Conference Template Type or its&#8217; =
current=20
  parameters.&nbsp; The &#8220;blueprint&#8221; is the Conference Object =
that will be cloned=20
  to create a conference object for reservation.&nbsp; So I was a bit=20
  uncomfortable when you said (in paragraph 2) &#8220;a list of the =
Conference Object=20
  &#8216;blueprints&#8217; (or templates) the system=20
  supports.&#8221;&nbsp;&nbsp;&nbsp;</FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D333252020-27092005>&nbsp;</SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2><SPAN class=3D333252020-27092005><FONT=20
  color=3D#0000ff>[MB]</FONT>&nbsp;<FONT color=3D#0000ff> Agreed.&nbsp; =
I'll remove=20
  that text in parenthesis. Related to this is a general issue on =
whether we=20
  need the two distinct terms "template" and "blueprint" - we've debated =
this=20
  before and we need to resolve this.&nbsp; I'll post a separate email =
on this.=20
  </FONT></SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2><SPAN =
class=3D333252020-27092005></SPAN></FONT>Later=20
  on, in paragraph 4, it says: <BR>&nbsp;&nbsp; &#8220;The selected =
blueprint with its=20
  default values is copied by the <BR>&nbsp;&nbsp; client into a newly =
created=20
  Conference&nbsp; Object, &#8230;&#8221; <BR>Can we say its =
&#8220;cloned&#8221; instead of &#8220;copied&#8221; by=20
  the client.&nbsp; I&#8217;m not even sure we should specify who =
exactly is doing the=20
  cloning.&nbsp; It&#8217;s probably more likely that the client =
communicates via CPP=20
  to the Conference Control Server, which clones the =
parent.&nbsp;&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT color=3D#0000ff><FONT =
face=3DArial=20
  size=3D2>[MB] Agreed.&nbsp; Quite interesting, Oscar made the opposite =
comment,=20
  but I think by clarifying the terminology overall, based on the =
mark-ups I=20
  have from Henning and some WG discussion (separate email), we should =
be able=20
  to resolve this inconsistency. </FONT></FONT></SPAN></P>
  <P>Page 27, Section 7.3. I hope we spend more time discussing (and =
agreeing=20
  on) the mechanism for CCP next week.&nbsp; In the first sentence of =
this=20
  paragraph you say:</P>
  <P>&nbsp;&nbsp; &#8220;The XCON working group charter includes the =
development of a=20
  protocol <BR>&nbsp;&nbsp; or a set of protocols for controlling the =
state of a=20
  Conference <BR>&nbsp;&nbsp; Object and for retrieving its =
state.&#8221; <BR>I would=20
  add to that the ability to create and manipulate conference =
parameters, in=20
  fact any parameters of the Conference Object Type.&nbsp; Section 7.3.5 =
(SOAP),=20
  paragraph 3 states it fairly well:</P>
  <P>&nbsp;&nbsp;&nbsp; &#8220; _____ is proposed as the mechanism for =
object content=20
  manipulation and <BR>&nbsp;&nbsp; state retrieval for the XCON data=20
  (model).&#8221;&nbsp;<SPAN class=3D333252020-27092005><FONT =
face=3DArial=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB]=20
  Agreed.</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff size=3D2> I'll =
reword similar=20
  to what you suggest. </FONT></SPAN></P>
  <P>Page 31, Section 7.4. I would agree with bullet 5, the discussion =
related=20
  to BFCP is still too detailed.&nbsp; In particular the lengthy =
authentication=20
  paragraph which ends this section is not necessary as authentication =
and=20
  security should be covered in Section 10.<SPAN =
class=3D333252020-27092005><FONT=20
  face=3DArial size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB] I=20
  agree; this isn't consistent with&nbsp;security discussions in the =
rest of the=20
  document and I've worked this into section 10.</FONT>&nbsp;</SPAN></P>
  <P>Page 37, Section 9.&nbsp; After reading this section on the =
relationship=20
  between the SIPPING and XCON frameworks, I had to ask myself why we =
don&#8217;t=20
  supersede the SIPPING framework [9].&nbsp; I glanced at=20
  draft-ietf-sipping-conferencing-framework-05.txt (posted on May=20
  27<SUP>th</SUP>) and even with a quick read I can see there are some=20
  significant differences as noted here.&nbsp; We can probably tolerate =
some=20
  differences because these are just framework docs.&nbsp; But =
shouldn&#8217;t the=20
  respective authors attempt to iron out the major differences?<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff =

  size=3D2>[MB]</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff size=3D2> =
Both the=20
  sipping-conferencing-framework and this XCON FW&nbsp;match in terms=20
  of&nbsp;the protocol&nbsp;and other normative aspects that are =
required for=20
  SIP based conferencing.&nbsp; So, although, the high level models =
don't match=20
  (e.g. Policy models),&nbsp;&nbsp;the XCON&nbsp;FW does not change any =
of the=20
  fundamental SIP based protocol aspects. &nbsp;I think we have to view =
this=20
  situation as "water under the bridge".&nbsp; Ideally, it would have =
been nice=20
  to have a single framework, but clearly having two separate documents =
was the=20
  right decision since the SIPPING documents&nbsp;are in the RFC =
Editor's Queue,=20
  thus providing stability to developers and other SDOs with =
dependencies on=20
  those docs and from a process perspective, it's not possible to make=20
  significant changes to those docs.&nbsp;&nbsp;&nbsp;We did decide way =
long ago=20
  that the SIPPING&nbsp;conferencing framework was not the ideal =
starting point=20
  for the XCON FW (i.e. I think we have agreed as a WG&nbsp; that there =
is a=20
  reason for the differences, but I'll let the chairs step in if that's =
not so).=20
  &nbsp;&nbsp; Certainly, we'd love this document to not be too far =
behind the=20
  SIPPING docs in getting published, so that developer's have=20
  a&nbsp;common&nbsp;baseline for the more advanced functionality that =
this FW=20
  enables, while still being compatible with what they've developed for=20
  SIP.&nbsp; If this concept isn't clear in the text, we need to make =
sure that=20
  it is. </FONT></SPAN></P>
  <P>Page 39, Section 10. At the end of the Security Consideration =
section=20
  there&#8217;s a discussion of hidden and anonymous parties.&nbsp; I =
would like to=20
  request that call recording be added to the last sentence so that it=20
reads:</P>
  <P>&nbsp; &#8220; &#8216;Hidden&#8217; status is often used by robot =
participants of a=20
  conference, for example for call&nbsp; <BR>&nbsp;&nbsp;&nbsp;&nbsp; =
recording,=20
  and is also used in many call center conferencing =
situations.&#8221;&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB]=20
  Agreed.</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005></SPAN><BR><FONT=20
  face=3D"Times New Roman">Thanks</FONT> </P>
  <P><FONT face=3D"Times New Roman">NITs</FONT>&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN><SPAN=20
  class=3D333252020-27092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005>&nbsp;</SPAN><BR><FONT=20
  face=3D"Times New Roman">1. Page 6, Section 3, paragraph 5, ends with =
unmatched=20
  parenthesis</FONT>&nbsp;<SPAN class=3D333252020-27092005><FONT =
face=3DArial=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT color=3D#0000ff>&nbsp;<FONT =
face=3DArial=20
  size=3D2>[MB] Replaced that sentence with the=20
  following:</FONT></FONT></SPAN></P><SPAN class=3D333252020-27092005>
  <P><FONT color=3D#0000ff><SPAN class=3D333252020-27092005><FONT =
face=3DArial=20
  size=3D2>&nbsp;" &nbsp;</FONT></SPAN>A Conference Object is accessible =
using the=20
  protocols, identified&nbsp;<FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D333252020-27092005>&nbsp;in Figure=20
  1."</SPAN></FONT></FONT></FONT></P><FONT face=3DArial><FONT =
size=3D2><SPAN=20
  class=3D333252020-27092005></SPAN></FONT></FONT><FONT face=3DArial=20
  size=3D2></FONT></SPAN>
  <P><BR><FONT face=3D"Times New Roman">2. Page 13, Section 5.3, =
paragraph 3,=20
  &#8220;stages are addressing using CCP&#8221; should read =
&#8220;addressed&#8221;</FONT>&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial size=3D2>&nbsp; <FONT=20
  color=3D#0000ff>[MB] Fixed.&nbsp;</FONT></FONT></SPAN><BR><FONT=20
  face=3D"Times New Roman">3. Page 17, Section 5.4, Figure 5 should be =
titled=20
  &#8220;Conference User Identifier Mapping&#8221;</FONT><FONT =
color=3D#0000ff> <FONT=20
  size=3D2><FONT face=3DArial>[MB] =
Fixed.&nbsp;</FONT></FONT><BR></FONT><FONT=20
  face=3D"Times New Roman">4. Page 18, Section 6.1, Figure 6 is =
described but not=20
  explicitly referenced in Section 6.1</FONT>&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial size=3D2>&nbsp;<FONT=20
  color=3D#0000ff>[MB]&nbsp;Added a paragraph and deleted the sentence =
referencing=20
  future XCON specs.</FONT></FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005></SPAN><FONT face=3D"Times New =
Roman">5. Page=20
  30, Section 7.4, bullets are not numbered in =
sequence</FONT>&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial size=3D2><FONT=20
  color=3D#0000ff>&nbsp;[MB] Fixed by removing and rearranging the notes =
(4 moved=20
  to 1st paragraph, where any such discussion would need to be and have =
moved=20
  the security discussion to section 10.&nbsp; I think this section is =
no longer=20
  so overloaded or detailed and that any remaining changes would be =
based on=20
  changes earlier in the doc that might ripple down to this section (eg. =

  identifiers). </FONT></FONT></SPAN></P>
  <P><SPAN class=3D333252020-27092005><FONT face=3DArial color=3D#0000ff =

  size=3D2></FONT></SPAN><BR><FONT face=3D"Times New Roman">6. Page 36, =
Section 8.3,=20
  paragraph 3, ends with unmatched parenthesis</FONT>&nbsp;<SPAN=20
  class=3D333252020-27092005><FONT face=3DArial =
size=3D2>&nbsp;&nbsp;&nbsp;<FONT=20
  color=3D#0000ff>[MB] Fixed.&nbsp;</FONT></FONT></SPAN><BR><FONT=20
  face=3D"Times New Roman">7. Page 39, Section 10, paragraph 7, =
&#8220;to enter a PIN=20
  makes is fairly hard&#8221; should read &#8220;makes it&#8221;</FONT> =
<FONT face=3DArial=20
  color=3D#0000ff size=3D2>[MB] Fixed.</FONT><BR><BR></P>
  <P><FONT face=3DArial=20
  =
size=3D2>----------------------------------------------------------------=
--------</FONT>=20
  <BR><FONT face=3DArial size=3D2>David P. Morgan, PhD</FONT> <BR><FONT =
face=3DArial=20
  color=3D#008000 size=3D2>VP, Architecture &amp; Planning</FONT> =
<BR><FONT=20
  face=3DArial color=3D#008000 size=3D2>Fidelity Investments Systems =
Company -=20
  Telecom</FONT> <BR><FONT face=3DArial color=3D#008000 =
size=3D2>Phone:&nbsp; 617=20
  563-2178</FONT> <BR><FONT face=3DArial color=3D#008000=20
  size=3D2>Fax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 617 385 2122</FONT> =
<BR><FONT=20
  face=3DArial color=3D#008000 size=3D2>Mailing: 82 Devonshire St, MZ =
V8C</FONT>=20
  <BR><FONT face=3DArial color=3D#008000=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
  Boston, MA 02109-3614</FONT> <BR><FONT face=3DArial color=3D#008000=20
  size=3D2>Office:&nbsp;&nbsp; 245 Summer Street, 8th Floor</FONT>=20
</P><BR><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C5C546.0780879A--


--===============0392723995==
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://www1.ietf.org/mailman/listinfo/xcon

--===============0392723995==--




From xcon-bounces@ietf.org Thu Sep 29 18:46:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EL7AU-00013P-K5; Thu, 29 Sep 2005 18:46:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EL7AS-00011y-Ue
	for xcon@megatron.ietf.org; Thu, 29 Sep 2005 18:46:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20694
	for <XCON@ietf.org>; Thu, 29 Sep 2005 18:46:17 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EL7IC-0002cE-Up
	for XCON@ietf.org; Thu, 29 Sep 2005 18:54:21 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j8TMjxj18618; Thu, 29 Sep 2005 18:46:00 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [XCON] Oscar's Comments on draft-ietf-xcon-framework-01.txt
Date: Thu, 29 Sep 2005 17:45:44 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D27F@zrc2hxm1.corp.nortel.com>
Thread-Topic: [XCON] Oscar's Comments on draft-ietf-xcon-framework-01.txt
Thread-Index: AcWSJB6UcoV4MVLWSSavryDRfvFKogF6o8WQC03efsA=
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Oscar Novo \(JO/LMF\)" <oscar.novo@ericsson.com>,
	"Morgan, Dave" <Dave.Morgan@FMR.COM>, <XCON@ietf.org>
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 76c7db407a166e4c39f35d8215d8dd32
Cc: 
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0996742994=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0996742994==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5C547.86DA629E"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5C547.86DA629E
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Oscar,
=20
Thanks for reviewing the document (and your subsequent common data
model).  Responses are embedded below [MB].
=20
Mary=20

	-----Original Message-----
	From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
Behalf Of Oscar Novo (JO/LMF)
	Sent: Wednesday, August 03, 2005 4:36 AM
	To: Morgan, Dave; XCON@ietf.org
	Subject: RE: [XCON] Comments on draft-ietf-xcon-framework-01.txt
=09
=09

	Hi David,

	I think your comments about the framework-01 doc are really good
and I would like to give my opinion about some of them. In my case, I am
doing my Master's thesis in Conferencing and I have had some of these
questions during the last weeks.

	First of all, I agree with you about the different of
"Blueprint" and Template. They mean two different things and the
framework is mixing both terms. The definition of Template is well
defined in the Section 2, Conventions and Terminology, but Blueprint
term is not well defined in any part of the framework.=20

	[MB] Per my response to Dave, we do need further WG discussion
of this topic as there is some inconsistency right now and I'll start a
separate thread on that. If we keep both terms, we do need to not use
them interchangeably.  We do introduce the term "blueprint" in the 5th
paragraph of section 3, but it's not in the basic terminology section.=20

	About the proposes to change in Section 6.2 "Ad-hoc Example" the
word "copied" for "cloned" in the next paragraph:

=09

	"The selected blueprint with its default values is copied by the
client into a newly created Conference Object, ..."=20

	I think is very important to understand the different between
clone and copy. As I understand (at least in programming is like that),
clone does a shallow copy, not a deep copy. So it just returns a
reference to the original copy unlike in Deep copy where a duplicate
instance is created. Any changes made to the clone will be reflected in
the original copy and vice versa.=20

	So, if you decide to write "cloned" instead of "copied" I think
it is very important to specify what exactly is doing the cloning and
how it works in the conference framework.=20

	[MB] We seem to have varying views on what term is more
appropriate.  In the more general sense cloning is used to refer to a
creation of something new that is an exact copy of an existing entity.
Per my response to Dave, we'll start a separate thread to resolve this.


	I also agree with David about the big different between the
SIPPING and the XCON frameworks. One of the big different is the
conference object entity, looking to the
draft-ietf-sipping-conferencing-framework-05.txt no conference object is
described at all. It would be nice if the authors of the frameworks iron
out the major different between both frameworks.=20

	[MB] I did have a detailed response to Dave on this point as
well that I won't repeat in it's entirety here, but I don't think we can
make many changes to align the two, particularly since the conference
object is key to the XCON FW model and the addition of it to the SIPPING
conferencing framework at this time is likely not possible, given that
doc is in the RFC Editor's Q. =20

	Thanks

	Oscar Novo=20


------_=_NextPart_001_01C5C547.86DA629E
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D329553522-29092005>Hi=20
Oscar,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D329553522-29092005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D329553522-29092005>Thanks=20
for reviewing the document (and your subsequent common data =
model).&nbsp;=20
Responses are embedded below [MB].</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><SPAN lang=3Den-us><FONT face=3DArial color=3D#0000ff =
size=3D2>Mary</FONT></SPAN>=20
</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] <B>On Behalf Of =
</B>Oscar=20
  Novo (JO/LMF)<BR><B>Sent:</B> Wednesday, August 03, 2005 4:36 =
AM<BR><B>To:</B>=20
  Morgan, Dave; XCON@ietf.org<BR><B>Subject:</B> RE: [XCON] Comments on=20
  draft-ietf-xcon-framework-01.txt<BR><BR></FONT></DIV>
  <DIV>
  <P><FONT size=3D2>Hi David,</FONT></P>
  <P><FONT size=3D2>I think your comments about the framework-01 doc are =
really=20
  good and I would like to give my opinion about some of them. In my =
case, I am=20
  doing my Master&#8217;s thesis in Conferencing and I have had some of =
these=20
  questions during the last weeks.</FONT></P>
  <P><FONT size=3D2>First of all, I agree with you about the different =
of=20
  "Blueprint" and Template. They mean two different things and the =
framework is=20
  mixing both terms. The definition of Template is well defined in the =
Section=20
  2, Conventions and Terminology, but Blueprint term is not well defined =
in any=20
  part of the framework.<SPAN class=3D329553522-29092005><FONT =
face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D329553522-29092005><FONT face=3DArial=20
  color=3D#0000ff>[MB] Per my response to Dave, we do need further WG =
discussion=20
  of this topic as there is some inconsistency right now and I'll start =
a=20
  separate thread on that. If we keep both terms, we do need to not use =
them=20
  interchangeably.&nbsp; We do introduce the term "blueprint" in the 5th =

  paragraph of section 3, but it's not in the basic terminology section. =

  </FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D329553522-29092005></SPAN></FONT><FONT =

  size=3D2>About the proposes to change in Section 6.2 "Ad-hoc Example" =
the word=20
  "copied" for "cloned" in the next paragraph:</FONT></P>
  <P><FONT size=3D2></FONT></P>
  <P><FONT size=3D2>"The selected blueprint with its default values is =
copied by=20
  the client into a newly created Conference Object, &#8230;" =
</FONT></P>
  <P><FONT size=3D2>I think is very important to understand the =
different between=20
  clone and copy. As I understand (at least in programming is like =
that), clone=20
  does a shallow copy, not a deep copy. So it just returns a reference =
to the=20
  original copy unlike in Deep copy where a duplicate instance is =
created. Any=20
  changes made to the clone will be reflected in the original copy and =
vice=20
  versa. </FONT></P>
  <P><FONT size=3D2>So, if you decide to write "cloned" instead of =
"copied" I=20
  think it is very important to specify what exactly is doing the =
cloning and=20
  how it works in the conference framework.<SPAN =
class=3D329553522-29092005><FONT=20
  face=3DArial color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D329553522-29092005><FONT face=3DArial=20
  color=3D#0000ff>[MB] We seem to have varying views on what term is =
more=20
  appropriate.&nbsp; In the more general sense cloning is used to refer =
to a=20
  creation of something new that is an exact copy of an existing entity. =
Per my=20
  response to Dave, we'll start a separate thread to resolve this.=20
  </FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=3D2>I also agree with David about the big different =
between the=20
  SIPPING and the XCON frameworks. One of the big different is the =
conference=20
  object entity, looking to the =
draft-ietf-sipping-conferencing-framework-05.txt=20
  no conference object is described at all. It would be nice if the =
authors of=20
  the frameworks iron out the major different between both =
frameworks.<SPAN=20
  class=3D329553522-29092005><FONT face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D329553522-29092005><FONT face=3DArial=20
  color=3D#0000ff>[MB] I did have a detailed response to Dave on this =
point as=20
  well that I won't repeat in it's entirety here, but I don't think we =
can make=20
  many changes to align the two, particularly since the conference =
object is key=20
  to the XCON FW model and the addition of it to the SIPPING =
conferencing=20
  framework at this time is likely not possible, given that doc is in =
the RFC=20
  Editor's Q. </FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=3D2>Thanks</FONT></P>
  <P><FONT size=3D2>Osc<SPAN class=3D051263509-03082005>ar =
Novo</SPAN><SPAN=20
  class=3D051263509-03082005><FONT face=3DArial=20
  =
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY>=
</HTML>

------_=_NextPart_001_01C5C547.86DA629E--


--===============0996742994==
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://www1.ietf.org/mailman/listinfo/xcon

--===============0996742994==--




From xcon-bounces@ietf.org Fri Sep 30 13:43:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELOur-0007RC-PW; Fri, 30 Sep 2005 13:43:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELOuo-0007Qv-SG
	for xcon@megatron.ietf.org; Fri, 30 Sep 2005 13:43:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22802
	for <xcon@ietf.org>; Fri, 30 Sep 2005 13:43:21 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELP2i-0003BA-LH
	for xcon@ietf.org; Fri, 30 Sep 2005 13:51:33 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j8UHgo112055; Fri, 30 Sep 2005 13:42:51 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [XCON] Roni's Comments on draft-ietf-xcon-framework-01.txt
Date: Fri, 30 Sep 2005 12:42:49 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D289@zrc2hxm1.corp.nortel.com>
Thread-Topic: [XCON] Roni's Comments on draft-ietf-xcon-framework-01.txt
Thread-Index: AcWSJB6UcoV4MVLWSSavryDRfvFKogcCm5wwBb+7A+A=
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <roni.even@polycom.co.il>
X-Spam-Score: 0.9 (/)
X-Scan-Signature: d094b18a574860cb9e2fe5fedfbcc179
Cc: cboulton@ubiquity.net, xcon@ietf.org
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1759975641=="
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1759975641==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5C5E6.6034FBD2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5C5E6.6034FBD2
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Roni,
=20
Thanks for the detailed review.  Responses are embedded below [MB]. =20
=20
Mary=20

	-----Original Message-----
	From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On
Behalf Of Even, Roni
	Sent: Wednesday, August 31, 2005 8:23 AM
	To: XCON@ietf.org
	Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt
=09
=09
	Hi,
	I read the document and find in good shape that will enable to
finish the open issues.
	My comments are more on editorial so I will have them as a one
list. If any of them will need to be discussed, I can create a separate
email.
	=20
	=20
	1. In the document you are using in some places call control
signaling and in others call signaling.=20

	      My suggestion is to use call signaling.=20

	 [MB] My preference would be to keep the word "control", but I
know that gets long, which is why we got lazy and dropped it in some
cases.  So, I will go ahead and make this change unless someone objects.


	=20

	2. In figure 1 there is call control client - suggest call
signaling client.=20

	[MB] For consistency with the previous comment, I'll make this
change.   And, I'll also modify Figure 1 for consistency and change that
arrow that's labeled with protocols to be the "Call Signaling Protocol".


	=20

	3. In figure 1 suggest changing conference control client to
conference and media control client.=20

	[MB] Agreed.=20

	=20

	4. In section 4.1 "The basic common conference information can
be represented using the

	   conference-info-type schema as defined in" should be
"conference-info type"=20

	[MB] Agreed. =20

	=20

	5. In section 4.1, I suggest to add to the conference common
information also the media semantics and refer to
draft-hautakorpi-mmusic-sdp-media-content-01.=20

	[MB]  I agree that this document would be a good reference to
add in general, but I'm not sure it needs to be discussed or brought
into this section of the document. I think this does highlight some
things that should naturally be included in the Common Conference
Information and thus implies some extensions to the conference-info-type
(or whatever is agreed based upon current discussions on
draft-novo-xcon-common-data-model-00.txt.   I think this brings us to
the more general issue of how much detail we want in this doc as to the
detailed schema.=20

	=20

	6.  Section 5.1 discuss the conference identifier and claims
that the factory creates it. Using a factory is only one method to
create the conference URI.=20

	[MB] Agreed.  I'll add a statement that within this model, the
factory is the one method, but that depending upon the implementation,
there may be other means of creating the conference URI.  We should
probably add an example of another means that is plausible such as a
pre-configured or out-of-band mechanism; does that sound reasonable?=20

	=20

	7. In section 5.2 you have "each of them accessible by a Call
Control protocol" what is call control protocol=20

	[MB] This should be, of course, the Call Signaling protocol.=20

	=20

	8. Section 5.4 present the conference user identifier. There
should be an association between this identifier and the user element in
the event package so that the users in the conference can be identified
in the notifications. Maybe you can explain how the user identifier is
created in the example in 6.2 and explain the connection to the user
element in the event package.=20

	[MB] Per Henning's comments, as well, we need to clarify this
section.  We'll post to the list separately, in response to Henning's
separate email on this point, how we'll resolve this issue. =20

	=20

	9.  In section 6.4 you describe manipulation within a series
range of conferences. You describe that a new iCAL arrives which changes
in only part of the occurrence. Creating a clone defines the new
occurrences but what about the original reservation that has the
original times, how do you prevent them from being scheduled. You need
to either change the iCAL information for the original reservation or to
have just the iCAL linked, using a linked list, to the conference
identifier without cloning and let the system calculate the right time.


	[MB] I kinda see your point, but I don't necessarily think we
have a problem, as we are creating a new child object (which is not
independent of the parent).  So, rather than all the reservations in the
series pointing to the same object, some of them point to this new child
object.  So, I would think the concern would be that if a time change
were made to the whole series, the start time for the child would also
change, which I think would be the intent. Since, it is a child, the
parent is aware of its existence, thus any potential concerns with
changes to the parent (original reservation) should be resolvable by
first visiting the child to determine if those changes should apply
(depending upon policy, etc.).=20

	=20

	10. Section 8.3 discuss sidebar is it possible to have a
participant in audio sidebar and see the presentation from the main
conference. Does this fall under the mechanism where the sidebar gets a
main conference media stream, suggest to mention that a sidebar may have
own media mixes and main conference media for other media streams.=20

	[MB]   Agreed, that we should mention this case. Chris'
suggestion is that the audio sidebar has a separate mix with  the main
mix/presentation as a participant.

	 =20

	Typos:

	 [MB] All fixed.  Thanks for catching these.=20

	In section 6:  capabilites

	In section 8.1 it should be figure 10 instead of figure 11.

	In section 10: specificiations

	=20

	=20

	Roni Even


------_=_NextPart_001_01C5C5E6.6034FBD2
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:st1 =3D "urn:schemas-microsoft-com:office:smarttags" xmlns:o =
=3D=20
"urn:schemas-microsoft-com:office:office"><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1515" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D532143919-29092005>Hi=20
Roni,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D532143919-29092005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D532143919-29092005>Thanks=20
for the detailed review.&nbsp; Responses are embedded below [MB].&nbsp;=20
</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>Mary</FONT></SPAN> </FONT></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] <B>On Behalf Of =
</B>Even,=20
  Roni<BR><B>Sent:</B> Wednesday, August 31, 2005 8:23 AM<BR><B>To:</B>=20
  XCON@ietf.org<BR><B>Subject:</B> [XCON] Comments on=20
  draft-ietf-xcon-framework-01.txt<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D762001913-31082005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Hi,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D762001913-31082005><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
  read the document and find in good shape that will enable to finish =
the open=20
  issues.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D762001913-31082005><FONT face=3DArial =
color=3D#0000ff size=3D2>My=20
  comments are more on editorial so I will have them as a one list. If =
any of=20
  them will need to be discussed, I can create a separate=20
  email.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D762001913-31082005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D762001913-31082005><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D762001913-31082005>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"1. In" w:st=3D"on">1. In</st1:metricconverter> the =
document you are=20
  using in some places call control signaling and in others call =
signaling. </P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D762001913-31082005>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>My =
suggestion=20
  is to use call signaling.<SPAN class=3D532143919-29092005><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;[MB]&nbsp;My preference would be to keep the word =
"control",=20
  but&nbsp;I know that&nbsp;gets&nbsp;long, which is why we got lazy=20
  and&nbsp;dropped it in some cases.&nbsp; So, I will go ahead and make =
this=20
  change unless someone&nbsp;objects.&nbsp; </FONT>&nbsp;</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"2. In" w:st=3D"on">2. In</st1:metricconverter> figure 1 =
there is call=20
  control client &#8211; suggest call signaling client.<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB]&nbsp;For=20
  consistency with the previous comment, I'll make this change.=20
  &nbsp;</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff size=3D2>And, =
I'll also modify=20
  Figure 1 for consistency and change that arrow that's labeled with =
protocols=20
  to be the "Call Signaling Protocol".&nbsp; </FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"3. In" w:st=3D"on">3. In</st1:metricconverter> figure 1 =
suggest=20
  changing conference control client to conference and media control=20
  client.<SPAN class=3D532143919-29092005><FONT face=3DArial=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB]=20
  Agreed.</FONT>&nbsp;</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"4. In" w:st=3D"on">4. In</st1:metricconverter> section =
4.1 &#8220;The basic=20
  common conference information can be represented using the</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN>conference-info-type =
schema as=20
  defined in&#8221; should be &#8220;conference-info type&#8221;<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><SPAN class=3D532143919-29092005><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>[MB] =
Agreed.</FONT>&nbsp;</SPAN>&nbsp;</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"5. In" w:st=3D"on">5. In</st1:metricconverter> section =
4.1, I suggest=20
  to add to the conference common information also the media semantics =
and refer=20
  to draft-hautakorpi-mmusic-sdp-media-content-01.<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff=20
  size=3D2>[MB]</FONT>&nbsp;<FONT face=3DArial><FONT color=3D#0000ff =
size=3D2> I agree=20
  that this document would be a good reference to add in general, but =
I'm not=20
  sure it needs to be discussed or brought into this section of the =
document. I=20
  think this does highlight some things that should naturally be =
included in the=20
  Common Conference Information and thus implies some extensions to the=20
  conference-info-type (or whatever is agreed based upon current =
discussions on=20
  </FONT><FONT color=3D#0000ff=20
  size=3D2>draft-novo-xcon-common-data-model-00.txt.&nbsp; &nbsp;I think =
this=20
  brings us to the more general issue of how much detail we want in this =
doc as=20
  to the detailed schema. </FONT></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: =
justify">6.<SPAN=20
  style=3D"mso-spacerun: yes">&nbsp; </SPAN>Section 5.1 discuss the =
conference=20
  identifier and claims that the factory creates it. Using a factory is =
only one=20
  method to create the conference URI.<SPAN =
class=3D532143919-29092005><FONT=20
  face=3DArial size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: =
justify"><SPAN=20
  class=3D532143919-29092005><FONT color=3D#0000ff><FONT face=3DArial =
size=3D2>[MB]=20
  Agreed.&nbsp; I'll add a statement that within this model, the factory =
is the=20
  one method, but that depending upon the implementation, there may be =
other=20
  means of</FONT>&nbsp;<FONT face=3DArial size=3D2>creating the =
conference=20
  URI.&nbsp; We should probably add an example of another means that is=20
  plausible such as a pre-configured or out-of-band mechanism; does that =
sound=20
  reasonable? </FONT></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><st1:metricconverter=20
  ProductID=3D"7. In" w:st=3D"on">7. In</st1:metricconverter> section =
5.2 you have=20
  &#8220;each of them accessible by a Call Control protocol&#8221; what =
is call control=20
  protocol<SPAN class=3D532143919-29092005><FONT face=3DArial=20
  size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial color=3D#0000ff =
size=3D2>[MB] This=20
  should be, of course, the Call Signaling =
protocol.</FONT>&nbsp;</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">8. Section 5.4 =
present the=20
  conference user identifier. There should be an association between =
this=20
  identifier and the user element in the event package so that the users =
in the=20
  conference can be identified in the notifications. Maybe you can =
explain how=20
  the user identifier is created in the example in 6.2 and explain the=20
  connection to the user element in the event package.<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial size=3D2><FONT =
color=3D#0000ff>[MB] Per=20
  Henning's comments, as well, we need to clarify this =
section.&nbsp;&nbsp;We'll=20
  post to the list separately, in response to Henning's separate email =
on this=20
  point, how we'll resolve this issue.</FONT> </FONT>&nbsp;</SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">9. <SPAN=20
  style=3D"mso-spacerun: yes">&nbsp;</SPAN>In section 6.4 you describe=20
  manipulation within a series range of conferences. You describe that a =
new=20
  iCAL arrives which changes in only part of the occurrence. Creating a =
clone=20
  defines the new occurrences but what about the original reservation =
that has=20
  the original times, how do you prevent them from being scheduled. You =
need to=20
  either change the iCAL information for the original reservation or to =
have=20
  just the iCAL linked, using a linked list, to the conference =
identifier=20
  without cloning and let the system calculate the right =
time.&nbsp;<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial size=3D2><FONT=20
  color=3D#0000ff>[MB]&nbsp;I&nbsp;kinda see your point, but I don't =
necessarily=20
  think we have a problem, as we are&nbsp;creating a new child object =
(which is=20
  not independent of the parent).&nbsp; So, rather than all the =
reservations in=20
  the series pointing to the same object, some of them point to this new =
child=20
  object.&nbsp; So, I would think the concern would be that if a time =
change=20
  were made to the whole series, the start time for the child would also =
change,=20
  which I think would be the intent.&nbsp;Since, it is a child, the =
parent is=20
  aware of its existence, thus any potential concerns with changes to=20
  the&nbsp;parent (original reservation) should be resolvable by first =
visiting=20
  the child to determine if those changes should apply (depending upon =
policy,=20
  etc.). </FONT></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005></SPAN><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">10. Section 8.3 =
discuss sidebar=20
  is it possible to have a participant in audio sidebar and see the =
presentation=20
  from the main conference. Does this fall under the mechanism where the =
sidebar=20
  gets a main conference media stream, suggest to mention that a sidebar =
may=20
  have own media mixes and main conference media for other media =
streams.<SPAN=20
  class=3D532143919-29092005><FONT face=3DArial =
size=3D2>&nbsp;</FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><SPAN=20
  class=3D532143919-29092005><FONT face=3DArial size=3D2><FONT=20
  color=3D#0000ff>[MB]</FONT>&nbsp;</FONT>&nbsp;<FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>&nbsp;Agreed, that we should mention this case.&nbsp;Chris' =
suggestion=20
  is that <FONT color=3D#000080><FONT color=3D#0000ff>the audio sidebar =
has a=20
  separate mix&nbsp;with&nbsp; the main mix/presentation as a=20
  participant.</FONT></FONT></FONT></SPAN></P>
  <P class=3DMsoNormal=20
  style=3D"MARGIN: 0cm 0cm 0pt"><o:p>&nbsp;</o:p><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">Typos:</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><o:p><FONT=20
  color=3D#0000ff>&nbsp;<SPAN class=3D532143919-29092005><FONT =
face=3DArial=20
  size=3D2>[MB] All fixed.&nbsp; Thanks for catching these.=20
  </FONT></SPAN></FONT></o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">In section 6: <SPAN =

  style=3D"mso-spacerun: yes">&nbsp;</SPAN>capabilites</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">In section 8.1 it =
should be=20
  figure 10 instead of figure 11.</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt">In section 10:=20
  specificiations</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm =
0pt"><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><o:p><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></o:p>&nbsp;</P>
  <P class=3DMsoNormal style=3D"MARGIN: 0cm 0cm 0pt"><o:p><SPAN=20
  class=3D762001913-31082005><FONT face=3DArial color=3D#0000ff =
size=3D2>Roni=20
  Even</FONT></SPAN></o:p></P></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C5C5E6.6034FBD2--


--===============1759975641==
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://www1.ietf.org/mailman/listinfo/xcon

--===============1759975641==--




From xcon-bounces@ietf.org Fri Sep 30 13:44:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELOvQ-0007WN-OB; Fri, 30 Sep 2005 13:44:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELOvP-0007WF-0H
	for xcon@megatron.ietf.org; Fri, 30 Sep 2005 13:43:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22855
	for <xcon@ietf.org>; Fri, 30 Sep 2005 13:43:58 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELP3J-0003Cw-7T
	for xcon@ietf.org; Fri, 30 Sep 2005 13:52:09 -0400
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j8UHhk024179; Fri, 30 Sep 2005 13:43:46 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [XCON] Umesh's Comments on draft-ietf-xcon-framework-01.txt
Date: Fri, 30 Sep 2005 12:43:45 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB0AB3D28A@zrc2hxm1.corp.nortel.com>
Thread-Topic: [XCON] Umesh's Comments on draft-ietf-xcon-framework-01.txt
Thread-Index: AcW313Ax6MoFJLfbRh6jecopiuN31wNcEXwQ
From: "Mary Barnes" <mary.barnes@nortel.com>
To: <umesh.chandra@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Content-Transfer-Encoding: quoted-printable
Cc: xcon@ietf.org
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/xcon>,
	<mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

Hi Umesh,

Thank you for your detailed review of the document.  Responses are
embedded below [MB].

Mary


-----Original Message-----
From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of
Umesh.Chandra@nokia.com
Sent: Monday, September 12, 2005 3:21 PM
To: xcon@ietf.org
Subject: [XCON] Comments on draft-ietf-xcon-framework-01.txt


Hello,

I reviewed the draft and it looks in a good shape to me, though I felt
some more detailed examples would aid in understanding it more clearly.
My comments besides the blueprint and templates which I sent in the
earlier email are as follows

1) In section 4.2 - is the conference template is used only to describe
the mixer or media related functionality only meaning - the media
controls available to end points to customize the media they receive
from the server, the ability to mute somebody in the conference based on
some privilages etc.=20

[MB] I agree this remains a bit confusing.  Did you have an explicit
text change to suggest or is this just in reference to the general
concern folks still seem to have on the format of the data (i.e. DP4)? =20

2) Editoral comment. In section 4.2 (3 paragraph) the sentence " This
information would allow authorized clients to manipulate mixer's
behavior and the resultant distribution of the media to all or
individual participants" should be changed to "This information would
allow authorized clients to manipulate mixer's behavior via focus, and
the resultant distribution of the media to all or individual
participants". The present sentence gives an impression that clients can
communicate directly with the mixer to change the media.

[MB] Agreed.

3)  In section 4.3, where are the permission and limits are specified in
the conference object - in the template or in the common conference
information section.

[MB] This relates to general issues that were also raised by other
reviewers (how is the policy realized in this model and the relationship
between template/common conference information/blueprint (DP4 again)?)
and needs further list discussion under a separate thread.  =20

4) In section 5.3, (2 paragraph) the draft says " The Conference Object
is identified by a single or a set of call signaling Conference
Identifiers, with a one-to-one mapping, as shown in the figure".  Is the
conference object identified by conference identifier (for example the
SIP URL of a SIP conference) or an conference object identifier. ?

[MB] This text needs clarification; it's really trying to describe the
relationship
of the Conference Object to the Confererence Identifier.  The conference
object is=20
identified by the conference object identifier. =20

5) Editorial comment. There is no definition for conference user
identifier in section 2 (convention and terminology). For consistency
sake it would be good to define it.
[MB] Agreed.=20

6) In section 6.1 (page 18), how does the parent object enforce a
different policy by marking certain data elements as "parent
enforceable". Are these markings done in the conference template ?
[MB] I am proposing to add additional text to 6.1 per comments received
from Dave. Once we agree the level of detail on policy in general we
want in this document (per your comment 3 above), we add additional text
to address this concern, as well.=20

7) In section 6.2, it would really help if you can provide an example as
to how an conference factory  select one of the system supported
conference object blueprint based on the privileges and media lines in
SDP. It would be good to see an SDP example with audio and video media,
how the blue print would look like to get an clear picture.=20
[MB] Or, would it better to just add a new example to section 8 and
reference that here (per my response to your comment 9 below)?   I think
the intent of this section is to provide a good high level view and
"picture" of the objects associated with the system realization, but not
to provide all the details.=20


8)  Section 7.3.4 - Do we still leave the section regarding NETCONF as a
possible protocol option ?
[MB] Henning posted the general question as to whether we needed any
discussion of these=20
protocols in this document.  Perhaps a compromise is to put this
information in=20
an appendix for now and delete it once we ship
it for publication, which should be sooner, rather than later.=20

9)  In section 8.1, where an example is provided as to how an
participant is added to the conference using the conference control
protocol, it woul d be a good idea to extend the example depicting how
the new participant "Bob" gets the information from the conference
server as to what type of blueprint is being used for this conference.
Basically from a system point of view it would be good to know how when
a participant joins the conference (when an authorized participant sends
CCP request to add it to the conferene) it gets to know about the
capabilities (conference and media) of the conference. I thought it was
not obvious from the present example in section 8.1

[MB] I think what you're asking for here is yet another example titled
something like "Conference Creation".  Your concerns here are similar to
those raised in point 7 above in that there's not alot of detail around
some of these mechanisms.  Part of the reason for this lack of detail is
that we don't want to be too prescriptive in this logical model that's
presented in section 6 as an example system realization - some of this
crosses over into implementation decisions. But, I do agree that either
we add more detailed text to the examples in 6.2 (and 6.3) or add an
additional "Conference Creation" example in section 8.=20

Some Nits and Typos


1) In section 3, page 7 remove the word and from the first line.
[MB] I can't find the specific sentence or paragraph you're referring
to. Did you review the txt or html version?  I have a feeling your
concern may be over the third paragraph and the phrase: " reserved
reoccurring conferences, and the standard protocols for managing and
      controlling different conference aspects."
However, the intent there was that the 2nd to the last "and" is before
the last element of the clause, "the standard protocols" which is
qualified with the phrase "for managing and controlling....". =20
I can reword as:
  " reserved reoccurring conferences, the standard protocols for
managing and the
      standard protocols for controlling different conference aspects."=20
But, that also seems quite wordy to me.  So, I would propose to leave it
as is.=20

2)  In section 6.1 page 18 (4 paragrpah) you have reference to section
5.3.1 describing how an unique conference object URI is assigned. There
is no description of it in section 5.3.1, instead there is an reference
in 5.3.1 to TBD. So I guess instead of refering section 5.3.1 it should
refer to the correct reference.
[MB] I think the point of referring to 5.3.1 is that it does provide
some detail as to the role of the Conference Object Identifier, albeit
not the complete detail. Perhaps to be explicit, we need to say that
it's "discussed in 5.3.1 and defined in the TBD reference".=20

3)  In section 8.3 page 35, terminate the line with a full stop. " A
Sidebar is created using the same mechanisms employed for a standard
conference as described in Section 6.1."
[MB] Fixed.  Note, this was on page 36 of my txt version of the doc, but
on page 35 of my printout, thus likely the reason for my confusion about
your first nit above, although I still can't find it.=20


BR
Umesh









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


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



