Cloning: Additional data in the data model

From xcon-bounces@ietf.org Wed Jan 7 03:16:32 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEECE3A6989; Wed, 7 Jan 2009 03:16:32 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 254063A6A09 for ; Wed, 7 Jan 2009 03:16:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.249 X-Spam-Level: X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R16VPrFcc8PX for ; Wed, 7 Jan 2009 03:16:30 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id D29DF3A690E for ; Wed, 7 Jan 2009 03:16:29 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 351BF22193; Wed, 7 Jan 2009 12:15:22 +0100 (CET) X-AuditID: c1b4fb3e-ac86bbb00000429e-f9-49648ecac44d Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 1347322141; Wed, 7 Jan 2009 12:15:22 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 12:15:21 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 12:15:20 +0100 Message-ID: <9520E66537CC4941994C518E3E21091C1689EC@esealmw105.eemea.ericsson.se> In-Reply-To: <20081124125619.len1wq7uo44c4w08@webmail.unina.it> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Common-data-model -- video-layout Thread-Index: AclOK7lm1h8IHQSrTYCAy6mc3r8aVQijXdnA References: <20081124120711.sh7dfvqvgkogww0k@webmail.unina.it> <20081124125619.len1wq7uo44c4w08@webmail.unina.it> From: "Oscar Novo" To: "Lorenzo Miniero" , "Krishna Prasad Kalluri" X-OriginalArrivalTime: 07 Jan 2009 11:15:21.0782 (UTC) FILETIME=[3AFEFD60:01C970B9] X-Brightmail-Tracker: AAAAAA== Cc: xcon@ietf.org Subject: Re: [XCON] Common-data-model -- video-layout X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Krishna, Lorenzo is completely right. I'm sorry if I didn't answer to that question I was on holidays. Thanks Lorenzo to take care of that! Oscar -----Original Message----- From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Lorenzo Miniero Sent: 24. marraskuuta 2008 13:56 To: Krishna Prasad Kalluri Cc: xcon@ietf.org Subject: Re: [XCON] Common-data-model -- video-layout Hi Krishna, you can define a video layout per video stream, which is different than per conference. In fact, you can have more mixes in the same conference. You can have more elements in , each of whom may have a different if it's a video stream. Which participant should be attached to which stream can be defined in the data model as well. Lorenzo Quoting Krishna Prasad Kalluri : > Hi Lorenzo, > > How do define a layout per video stream? As I understood its possible > to define a video layout per mix (conference) > > Regards > Krishna > > -----Original Message----- > From: Lorenzo Miniero [mailto:lorenzo.miniero@unina.it] > Sent: den 24 november 2008 12:07 > To: Krishna Prasad Kalluri > Cc: xcon@ietf.org > Subject: Re: [XCON] Common-data-model -- video-layout > > Hi Krishna, > > you can still achieve what you want, by defining more video output > streams with different layouts, and attaching participants to them > according to your needs (e.g. a lightweight stream for all mobile > users, and a heavier stream for others). It's not as straightforward > as having a custom layout for each user, but it's compliant, for > instance, with how videomixing is currently handled in the MEDIACTRL mixer package. > > Lorenzo > > > Quoting Krishna Prasad Kalluri : > >> Hi, >> >> I have a question related to the video-layout element in XCON common >> data model. >> >> Question 1: >> >> The video-layout element is defined in the conference description > level. >> So one video conference will have only one layout. That means >> >> 1) From the conference mixer point of view its only one output mix. >> 2) All participants view the same layout. >> >> Is my understanding correct? If so the video-layout description in >> common-data-model is giving a different impression. From the text >> below I got an impression that each participant can have different > layout. >> >> The element is used in conjunction with a video stream >> to specify how the video streams (of participants) are viewed by each >> participant. Only one layout type can be specified for each output >> stream >> >> Question 2: >> >> In the data model is it possible to include video-layout per >> participant. May be its correct to say per endpoint. If the display >> of > >> endpoint is small (mobile phone) a participant can select a smaller >> layout (Eg: dual-view) . If the endpoint display is large (pc) a >> participant can select a bigger layout. Of course this causes more >> processing in the mixer to generate several output mixes. >> >> In H.248.19 it is possible to specify one layout type per termination. >> >> So in the data model I like to propose to add >> >> Users->user->endpoint->controls->video-layout >> >> Any way the summary is I like to see layout per participant >> (endpoint) >> >> Regards >> Krishna >> >> > > > > -- > Lorenzo Miniero, Junior Researcher > Dipartimento di Informatica e Sistemistica Universita' degli Studi di > Napoli "Federico II" > Via Claudio 21 -- 80125 Napoli (Italy) > Phone: +390817683821 - Fax: +390817683816 > Email: lorenzo.miniero@unina.it > -- Lorenzo Miniero, Junior Researcher Dipartimento di Informatica e Sistemistica Universita' degli Studi di Napoli "Federico II" Via Claudio 21 -- 80125 Napoli (Italy) Phone: +390817683821 - Fax: +390817683816 Email: lorenzo.miniero@unina.it _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Thu Jan 15 03:24:35 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9768B3A6877; Thu, 15 Jan 2009 03:24:35 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 267B93A6877 for ; Thu, 15 Jan 2009 03:24:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.504 X-Spam-Level: X-Spam-Status: No, score=-5.504 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOjUqd3eS4Fo for ; Thu, 15 Jan 2009 03:24:33 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 27FEC3A67E6 for ; Thu, 15 Jan 2009 03:24:32 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id DDBB3214CC for ; Thu, 15 Jan 2009 12:24:16 +0100 (CET) X-AuditID: c1b4fb3e-ab869bb00000429e-aa-496f1ce02a88 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B914321257 for ; Thu, 15 Jan 2009 12:24:16 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 12:24:16 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 15 Jan 2009 12:24:15 +0100 Message-ID: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Cloning: Additional data in the data model Thread-Index: Acl3A8x2UmPpfVkwSLGvtPjVGFZDRg== From: "Oscar Novo" To: X-OriginalArrivalTime: 15 Jan 2009 11:24:16.0269 (UTC) FILETIME=[CCE13BD0:01C97703] X-Brightmail-Tracker: AAAAAA== Subject: [XCON] Cloning: Additional data in the data model X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1521774567==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1521774567== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97703.CCDCC241" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97703.CCDCC241 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi folks, In IETF-73 has been a proposal to expand the data model to support the cloning method defined in the framework. At the moment, the data model supports the cloning method though the 'cascaded-focus' element which contains a 'parent' conference URI but it might be needed to add few more elements to be align with CCMP.=20 Some elements that could be added are: - An element that contains all the 'non-independent' children conferences - A policy attribute/element that indicates the "parent enforceable" of every element. However, it would make more sense to add it in a draft that discusses conference policies. It would be nice to know the opinion of the WG whether we want to support entirely this property or not.=20 Cheers, Oscar ------_=_NextPart_001_01C97703.CCDCC241 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cloning: Additional data in the data model

Hi folks,

In IETF-73 has been a proposal to = expand the data model to support the cloning method defined in the = framework. At the moment, the data model supports the cloning method = though the 'cascaded-focus' element which contains a 'parent' conference = URI but it might be needed to add few more elements to be align with = CCMP.

Some elements that could be added = are:

- An element that contains all the = 'non-independent' children conferences
- A policy attribute/element that = indicates the "parent enforceable" of every element. However, = it would make more sense to add it in a draft that discusses conference = policies.

It would be nice to know the opinion of = the WG whether we want to support entirely this property or not.

Cheers,

Oscar

------_=_NextPart_001_01C97703.CCDCC241-- --===============1521774567== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon --===============1521774567==-- From xcon-bounces@ietf.org Thu Jan 15 03:31:08 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 986D328C0E8; Thu, 15 Jan 2009 03:31:08 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22B2D3A68E5 for ; Thu, 15 Jan 2009 03:31:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6 X-Spam-Level: X-Spam-Status: No, score=-6 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Of29J4uZCype for ; Thu, 15 Jan 2009 03:31:07 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 9297328C0E8 for ; Thu, 15 Jan 2009 03:31:06 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 32079211EC for ; Thu, 15 Jan 2009 12:30:50 +0100 (CET) X-AuditID: c1b4fb3c-aff62bb00000304c-e3-496f1e6a9983 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 16FBB21158 for ; Thu, 15 Jan 2009 12:30:50 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Jan 2009 12:30:49 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 15 Jan 2009 12:30:49 +0100 Message-ID: <9520E66537CC4941994C518E3E21091C298777@esealmw105.eemea.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Cloning method, question Thread-Index: Acl3BLcFKCgOd6o/QE+6DFGL+wPaVw== From: "Oscar Novo" To: X-OriginalArrivalTime: 15 Jan 2009 11:30:49.0759 (UTC) FILETIME=[B76B0AF0:01C97704] X-Brightmail-Tracker: AAAAAA== Subject: [XCON] Cloning method, question X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0604416362==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============0604416362== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97704.B7863DE9" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97704.B7863DE9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi again, If we dedice to support the 'non-independent' cloning method a question that arise is how the parent will notify the child about the changes? Which protocol will do that? CCMP, xcon-event-pachages? Oscar ------_=_NextPart_001_01C97704.B7863DE9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cloning method, question

Hi again,

If we dedice to support the = 'non-independent' cloning method a question that arise is how the parent = will notify the child about the changes? Which protocol will do that? = CCMP, xcon-event-pachages?

Oscar

------_=_NextPart_001_01C97704.B7863DE9-- --===============0604416362== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon --===============0604416362==-- From xcon-bounces@ietf.org Tue Jan 20 14:48:36 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD1E03A6957; Tue, 20 Jan 2009 14:48:36 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CD9D3A6957 for ; Tue, 20 Jan 2009 14:48:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.941 X-Spam-Level: X-Spam-Status: No, score=-0.941 tagged_above=-999 required=5 tests=[AWL=-0.757, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAiS0pPRjaDV for ; Tue, 20 Jan 2009 14:48:35 -0800 (PST) Received: from blu0-omc2-s5.blu0.hotmail.com (blu0-omc2-s5.blu0.hotmail.com [65.55.111.80]) by core3.amsl.com (Postfix) with ESMTP id 70A353A6851 for ; Tue, 20 Jan 2009 14:48:35 -0800 (PST) Received: from BLU144-W30 ([65.55.111.71]) by blu0-omc2-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Jan 2009 14:48:15 -0800 Message-ID: X-Originating-IP: [148.177.1.216] From: Amer Meer To: , Date: Tue, 20 Jan 2009 22:48:15 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 20 Jan 2009 22:48:15.0820 (UTC) FILETIME=[2E6C80C0:01C97B51] Subject: [XCON] draft-ietf-xcon-event-package-01.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0592607162==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org --===============0592607162== Content-Type: multipart/alternative; boundary="_4bc6ca35-b3cb-46c4-895a-54d6bb3cb360_" --_4bc6ca35-b3cb-46c4-895a-54d6bb3cb360_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello=2C =20 For Maximum Backward compatibility shouldn't both the server and client hav= e same requirements in regards to support for "application/conference-info+= xml" MIME type. =20 Amer _________________________________________________________________ Windows Live=99: Keep your life in sync. http://windowslive.com/explore?ocid=3DTXT_TAGLM_WL_t1_allup_explore_012009= --_4bc6ca35-b3cb-46c4-895a-54d6bb3cb360_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello=2C
=3B
For Maximum Backward compatibility shouldn't both the server and client hav= e same requirements in regards to support for "application/conference-info+= xml" MIME type.
=3B
Amer

Windows Live=99: Keep your life in= sync. Check it out. = --_4bc6ca35-b3cb-46c4-895a-54d6bb3cb360_-- --===============0592607162== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon --===============0592607162==-- From xcon-bounces@ietf.org Wed Jan 21 00:20:20 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BB0528C0FB; Wed, 21 Jan 2009 00:20:20 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 724B828C0F0 for ; Wed, 21 Jan 2009 00:20:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.062 X-Spam-Level: X-Spam-Status: No, score=-6.062 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2R4IZ7H0d0Vh for ; Wed, 21 Jan 2009 00:20:16 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id AB02728C0D7 for ; Wed, 21 Jan 2009 00:20:14 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A3B6B218AB; Wed, 21 Jan 2009 09:18:45 +0100 (CET) X-AuditID: c1b4fb3e-ac06abb00000429e-18-4976da65079e Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 574E2218B0; Wed, 21 Jan 2009 09:18:45 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Jan 2009 09:18:43 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 21 Jan 2009 09:18:42 +0100 Message-ID: <9520E66537CC4941994C518E3E21091C33FFF0@esealmw105.eemea.ericsson.se> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] draft-ietf-xcon-event-package-01.txt Thread-Index: Acl7UTLPg3rZ9uDTS4qXgAGiMSKSQwATmA2Q References: From: "Oscar Novo" To: "Amer Meer" , , X-OriginalArrivalTime: 21 Jan 2009 08:18:43.0912 (UTC) FILETIME=[DFF4DC80:01C97BA0] X-Brightmail-Tracker: AAAAAA== Subject: Re: [XCON] draft-ietf-xcon-event-package-01.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1994423365==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1994423365== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97BA0.DFB4279B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97BA0.DFB4279B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi Amer, =20 When you talk about backward compatibility, are you talking about backward compatibility with 4575? Note that the xcon-event-packages introduces a new mime type. That's mean, you should implement both notification methods if you want to support both event packages. =20 Oscar ________________________________ From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On Behalf Of Amer Meer Sent: 21. tammikuuta 2009 0:48 To: xcon@ietf.org; alan@ese.wustl.edu Subject: [XCON] draft-ietf-xcon-event-package-01.txt Hello, =20 For Maximum Backward compatibility shouldn't both the server and client have same requirements in regards to support for "application/conference-info+xml" MIME type. =20 Amer ________________________________ Windows Live(tm): Keep your life in sync. Check it out. =20 ------_=_NextPart_001_01C97BA0.DFB4279B Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi Amer,

When you talk about backward compatibility, are you = talking about=20 backward compatibility with 4575? Note that the=20 xcon-event-packages introduces a new mime type. That's mean, you = should=20 implement both notification methods if you want to support both event=20 packages.

Oscar

From: xcon-bounces@ietf.org=20 [mailto:xcon-bounces@ietf.org] On Behalf Of Amer = Meer
Sent: 21.=20 tammikuuta 2009 0:48
To: xcon@ietf.org;=20 alan@ese.wustl.edu
Subject: [XCON]=20 draft-ietf-xcon-event-package-01.txt

Hello,

For Maximum Backward compatibility = shouldn't both=20 the server and client have same requirements in regards to support for=20 "application/conference-info+xml" MIME=20 type.

Amer

Windows Live™: Keep your life in sync. Check it out. ------_=_NextPart_001_01C97BA0.DFB4279B-- --===============1994423365== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon --===============1994423365==-- From xcon-bounces@ietf.org Tue Jan 27 07:11:22 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BA1E28C1E7; Tue, 27 Jan 2009 07:11:22 -0800 (PST) X-Original-To: xcon@ietf.org Delivered-To: xcon@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 92E2B28C1CA; Tue, 27 Jan 2009 07:11:20 -0800 (PST) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090127151120.92E2B28C1CA@core3.amsl.com> Date: Tue, 27 Jan 2009 07:11:20 -0800 (PST) Cc: xcon@ietf.org Subject: [XCON] Last Call: draft-ietf-xcon-event-package (Conference Event Package Data Format Extension for Centralized Conferencing (XCON)) to Proposed Standard X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ietf@ietf.org List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org The IESG has received a request from the Centralized Conferencing WG (xcon) to consider the following document: - 'Conference Event Package Data Format Extension for Centralized Conferencing (XCON) ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-02-10. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-xcon-event-package-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17027&rfc_flag=0 _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Jan 30 10:16:32 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 282E728C175; Fri, 30 Jan 2009 10:16:32 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9E8A28C19D for ; Fri, 30 Jan 2009 10:16:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.881 X-Spam-Level: * X-Spam-Status: No, score=1.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o+kho6Qm2Wr5 for ; Fri, 30 Jan 2009 10:16:30 -0800 (PST) Received: from webmail.unina.it (webmail.unina.it [192.132.34.212]) by core3.amsl.com (Postfix) with ESMTP id 5D5E628C175 for ; Fri, 30 Jan 2009 10:16:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by webmail.unina.it (8.14.0/8.14.0) with ESMTP id n0UIG5ZQ024827; Fri, 30 Jan 2009 19:16:06 +0100 Received: from 143.225.81.253 ([143.225.81.253]) by webmail.unina.it (Horde MIME library) with HTTP; Fri, 30 Jan 2009 19:16:05 +0100 Message-ID: <20090130191605.rx6xh6sj1ck4wcww@webmail.unina.it> Date: Fri, 30 Jan 2009 19:16:05 +0100 From: spromano@unina.it To: Oscar Novo References: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> In-Reply-To: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) X-Virus-Scanned: ClamAV 0.94.2/8925/Fri Jan 30 17:55:38 2009 on webmail.unina.it X-Virus-Status: Clean Cc: xcon@ietf.org Subject: Re: [XCON] Cloning: Additional data in the data model X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="Yes" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Oscar, sorry for the late reply. IMHO, we might need in the data model: 1. information about the father/son relationship. This might be an = attribute, e.g.: 2. information about the conference/sidebar relationship, e.g.: . As to the "parent enforceable" relationship, I would leave it outside = of the data model. Cheers, Simon Quoting Oscar Novo : > Hi folks, > > In IETF-73 has been a proposal to expand the data model to support the > cloning method defined in the framework. At the moment, the data model > supports the cloning method though the 'cascaded-focus' element which > contains a 'parent' conference URI but it might be needed to add few > more elements to be align with CCMP. > > Some elements that could be added are: > > - An element that contains all the 'non-independent' children > conferences > - A policy attribute/element that indicates the "parent enforceable" of > every element. However, it would make more sense to add it in a draft > that discusses conference policies. > > It would be nice to know the opinion of the WG whether we want to > support entirely this property or not. > > Cheers, > > Oscar > > > -- = _\\|//_ ( O-O ) ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~ Simon Pietro Romano Universita' di Napoli Federico II Computer Science Department Phone: +39 081 7683823 -- Fax: +39 081 7684219 e-mail: spromano@unina.it <>. Magritte. oooO ~~~~~~~~~~~~~~~~~~~~~~( )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~ \ ( ( ) \_) ) / (_/ _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Jan 30 10:20:03 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6292928C2B4; Fri, 30 Jan 2009 10:20:03 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42B4628C1AE for ; Fri, 30 Jan 2009 10:20:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.581 X-Spam-Level: X-Spam-Status: No, score=0.581 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73iE00p4HH-d for ; Fri, 30 Jan 2009 10:20:01 -0800 (PST) Received: from webmail.unina.it (webmail.unina.it [192.132.34.212]) by core3.amsl.com (Postfix) with ESMTP id 398B628C19D for ; Fri, 30 Jan 2009 10:20:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by webmail.unina.it (8.14.0/8.14.0) with ESMTP id n0UIJdPo025371; Fri, 30 Jan 2009 19:19:40 +0100 Received: from 143.225.81.253 ([143.225.81.253]) by webmail.unina.it (Horde MIME library) with HTTP; Fri, 30 Jan 2009 19:19:39 +0100 Message-ID: <20090130191939.0fe3fntt4oswk44o@webmail.unina.it> Date: Fri, 30 Jan 2009 19:19:39 +0100 From: spromano@unina.it To: Oscar Novo References: <9520E66537CC4941994C518E3E21091C298777@esealmw105.eemea.ericsson.se> In-Reply-To: <9520E66537CC4941994C518E3E21091C298777@esealmw105.eemea.ericsson.se> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) X-Virus-Scanned: ClamAV 0.94.2/8925/Fri Jan 30 17:55:38 2009 on webmail.unina.it X-Virus-Status: Clean Cc: xcon@ietf.org Subject: Re: [XCON] Cloning method, question X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="Yes" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org I think that keeping track of such changes (and hence maintaining = coherence among inter-related conference objects) is part of the = conference server's business logic. If we come to how the clients are = notified about changes (in general), the event package should do the = job (not CCMP...). Simon Quoting Oscar Novo : > Hi again, > > If we dedice to support the 'non-independent' cloning method a question > that arise is how the parent will notify the child about the changes? > Which protocol will do that? CCMP, xcon-event-pachages? > > Oscar > -- = _\\|//_ ( O-O ) ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~ Simon Pietro Romano Universita' di Napoli Federico II Computer Science Department Phone: +39 081 7683823 -- Fax: +39 081 7684219 e-mail: spromano@unina.it <>. Magritte. oooO ~~~~~~~~~~~~~~~~~~~~~~( )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~ \ ( ( ) \_) ) / (_/ _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Jan 30 10:37:12 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ACA628C15C; Fri, 30 Jan 2009 10:37:12 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FCDD3A6B18 for ; Fri, 30 Jan 2009 10:37:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.629 X-Spam-Level: X-Spam-Status: No, score=0.629 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oo75ySccrDPr for ; Fri, 30 Jan 2009 10:37:10 -0800 (PST) Received: from webmail.unina.it (webmail.unina.it [192.132.34.212]) by core3.amsl.com (Postfix) with ESMTP id DAB9C3A6885 for ; Fri, 30 Jan 2009 10:37:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by webmail.unina.it (8.14.0/8.14.0) with ESMTP id n0UIamRq028254; Fri, 30 Jan 2009 19:36:48 +0100 Received: from 143.225.81.253 ([143.225.81.253]) by webmail.unina.it (Horde MIME library) with HTTP; Fri, 30 Jan 2009 19:36:48 +0100 Message-ID: <20090130193648.ssvv4lsa8s0cgow0@webmail.unina.it> Date: Fri, 30 Jan 2009 19:36:48 +0100 From: spromano@unina.it To: Oscar Novo References: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> In-Reply-To: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) X-Virus-Scanned: ClamAV 0.94.2/8925/Fri Jan 30 17:55:38 2009 on webmail.unina.it X-Virus-Status: Clean Cc: xcon@ietf.org Subject: Re: [XCON] Cloning: Additional data in the data model X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="Yes" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hello again, Oscar. While working on the data model, we realized that = the new schema you put in the draft (in appendix) does not define the = XCON data model explicitely as an extension of the one contained in = rfc4575. You import the mentioned schema, and you define further = elements, which are the new ones introduced within XCON. This works = fine, thanks to the presence of the "any" element: Personally, I would have liked something more explicit, e.g.: ***************************************************************** xmlns:info=3D"urn:ietf:params:xml:ns:conference-info" ***************************************************************************= **** This solution looks a bit "cleaner" to me, even though it might = violate the Unique Particle Attribution constraint with some XML = engines (e.g. JAXB). What is your feeling about this? Simon Quoting Oscar Novo : > Hi folks, > > In IETF-73 has been a proposal to expand the data model to support the > cloning method defined in the framework. At the moment, the data model > supports the cloning method though the 'cascaded-focus' element which > contains a 'parent' conference URI but it might be needed to add few > more elements to be align with CCMP. > > Some elements that could be added are: > > - An element that contains all the 'non-independent' children > conferences > - A policy attribute/element that indicates the "parent enforceable" of > every element. However, it would make more sense to add it in a draft > that discusses conference policies. > > It would be nice to know the opinion of the WG whether we want to > support entirely this property or not. > > Cheers, > > Oscar > > > -- = _\\|//_ ( O-O ) ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~ Simon Pietro Romano Universita' di Napoli Federico II Computer Science Department Phone: +39 081 7683823 -- Fax: +39 081 7684219 e-mail: spromano@unina.it <>. Magritte. oooO ~~~~~~~~~~~~~~~~~~~~~~( )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~ \ ( ( ) \_) ) / (_/ _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Sat Jan 31 03:27:51 2009 Return-Path: X-Original-To: xcon-archive@megatron.ietf.org Delivered-To: ietfarch-xcon-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA2503A67CC; Sat, 31 Jan 2009 03:27:51 -0800 (PST) X-Original-To: xcon@core3.amsl.com Delivered-To: xcon@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4C163A67CC for ; Sat, 31 Jan 2009 03:27:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O8R5tT3MFekG for ; Sat, 31 Jan 2009 03:27:49 -0800 (PST) Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.185]) by core3.amsl.com (Postfix) with ESMTP id 6862A3A67AA for ; Sat, 31 Jan 2009 03:27:49 -0800 (PST) Received: by rn-out-0910.google.com with SMTP id j66so590908rne.18 for ; Sat, 31 Jan 2009 03:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=w9kFgLcH2dplMOTC3sN1iPle0md4t/UwArE+nKeubew=; b=H8sY2yXsxj0fbqI8/E7vR9xr2qM+qBih0o+gm8fK3Op91az8Rxt16cbqAcadbiDGM3 SPU7yndC+W1vli9AvEpQ06dCGedI20evp7FblRgcZcN07xkdTfvVTH8bhJlRySRlxKFL JOfohoRK+oyDCdgeNXJOuu5JA4ewvwJyuwEQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=f0j3fGunzdMRymDIKmDruYSKM7dItP3ISYb7/71Wn1OqIF99v8AOfbpXQcU+VllSJT dr/2l41P8Z3Rsz66zdYFuFkTjTqW1sj8ySUvsmi1eyAiNNxvbcOYotQ0ZEvmos+udbyN 5VcjuyncfBJMtDEX+gzSDsvwtlmSg/aw8LQH4= MIME-Version: 1.0 Received: by 10.90.72.3 with SMTP id u3mr1632070aga.17.1233401249181; Sat, 31 Jan 2009 03:27:29 -0800 (PST) In-Reply-To: <20090130191605.rx6xh6sj1ck4wcww@webmail.unina.it> References: <9520E66537CC4941994C518E3E21091C298760@esealmw105.eemea.ericsson.se> <20090130191605.rx6xh6sj1ck4wcww@webmail.unina.it> Date: Sat, 31 Jan 2009 05:27:29 -0600 Message-ID: <11e0ee130901310327w4cae7b14ie4019eb05d942d@mail.gmail.com> From: Mary Barnes To: spromano@unina.it Cc: xcon@ietf.org Subject: Re: [XCON] Cloning: Additional data in the data model X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0140172043==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org --===============0140172043== Content-Type: multipart/alternative; boundary=00163630f1d752afbe0461c59bee --00163630f1d752afbe0461c59bee Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oscar and Simon, 1. Shouldn't we call it "parent/child" or "mother/daughter" relationship ;= ) Obviously, the latter is the pc choice. I'm also still thinking we need the "independent" info. While the logic would be handled by the conference server - e.g., can the parent be deleted= ? I think the client needs to know this, so that they don't try to delete a parent and they are aware that when they get any updates, why that's happening. I also think it might be useful for debug and administration. Thanks, Mary --who also apologizes for the late reply -- and I'm traveling (with my new mac :) and corporate email access (via secure web i/f) is so, so, so, slow. On Fri, Jan 30, 2009 at 12:16 PM, wrote: > Hi Oscar, > > sorry for the late reply. IMHO, we might need in the data model: > > 1. information about the father/son relationship. This might be an > attribute, e.g.: > > > > 2. information about the conference/sidebar relationship, e.g.: > > . > > As to the "parent enforceable" relationship, I would leave it outside of > the data model. > > Cheers, > > Simon > > > Quoting Oscar Novo : > > Hi folks, >> >> In IETF-73 has been a proposal to expand the data model to support the >> cloning method defined in the framework. At the moment, the data model >> supports the cloning method though the 'cascaded-focus' element which >> contains a 'parent' conference URI but it might be needed to add few >> more elements to be align with CCMP. >> >> Some elements that could be added are: >> >> - An element that contains all the 'non-independent' children >> conferences >> - A policy attribute/element that indicates the "parent enforceable" of >> every element. However, it would make more sense to add it in a draft >> that discusses conference policies. >> >> It would be nice to know the opinion of the WG whether we want to >> support entirely this property or not. >> >> Cheers, >> >> Oscar >> >> >> >> > > > -- > _\\|//_ > ( O-O ) > ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~ > Simon Pietro Romano > Universita' di Napoli Federico II > Computer Science Department > Phone: +39 081 7683823 -- Fax: +39 081 7684219 > e-mail: spromano@unina.it > > < idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte. > oooO > ~~~~~~~~~~~~~~~~~~~~~~( )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~ > \ ( ( ) > \_) ) / > (_/ > > _______________________________________________ > XCON mailing list > XCON@ietf.org > https://www.ietf.org/mailman/listinfo/xcon > --00163630f1d752afbe0461c59bee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oscar and Simon,

1. Shouldn't we call it "= ;parent/child" or "mother/daughter" relationship ;) Ob= viously, the latter is the pc choice.

I'= m also still thinking we need the "independent" info. While the l= ogic would be handled by the conference server - e.g., can the parent be de= leted? I think the client needs to know this, so that they don't = try to delete a parent and they are aware that when they get any updates, w= hy that's happening. I also think it might be useful for debug and admi= nistration.

Thanks,

Mary

--who also apologizes = for the late reply

-- and I'm traveling (with my new mac :) &= nbsp;and corporate email access (via secure web i/f) is so, so, so, slow.

On Fri, Jan 30, 2009 at 12:16 PM, <spromano@unina.it> wrote:

Hi Oscar,

sorry for the late reply. IMHO, we might need in the data model:

1. information about the father/son relationship. This might be an attribut= e, e.g.:

<xs:attribute name=3D"fatherEntity" type=3D"xs:anyURI&quo= t; use=3D"optional"/>

2. information about the conference/sidebar relationship, e.g.:

<xs:attribute name=3D"sidebarOf" type=3D"xs:anyURI" = use=3D"optional"/>.

As to the "parent enforceable" relationship, I would leave it out= side of the data model.

Cheers,

Simon

Quoting Oscar Novo <oscar.novo@ericsson.com>:

Hi folks,

In IETF-73 has been a proposal to expand the data model to support the
cloning method defined in the framework. At the moment, the data model
supports the cloning method though the 'cascaded-focus' element whi= ch
contains a 'parent' conference URI but it might be needed to add fe= w
more elements to be align with CCMP.

Some elements that could be added are:

- An element that contains all the 'non-independent' children
conferences
- A policy attribute/element that indicates the "parent enforceable&qu= ot; of
every element. However, it would make more sense to add it in a draft
that discusses conference policies.

It would be nice to know the opinion of the WG whether we want to
support entirely this property or not.

Cheers,

Oscar

--
&nbs= p; _\\|//_
&nbs= p; ( O-O )
~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
Simon= Pietro Romano
Universita' di Napoli = Federico II
Computer Science D= epartment
Phone: +39 081 7683823 -- Fax: +39 081 7684219<= br> e-mail: spromano@unina.it

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

_______________________________________________
XCON mailing list
XCON@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/xcon

--00163630f1d752afbe0461c59bee-- --===============0140172043== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ XCON mailing list XCON@ietf.org https://www.ietf.org/mailman/listinfo/xcon --===============0140172043==--