From xcon-bounces@ietf.org Thu Nov 01 03:39:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InUdq-0007HZ-Ag; Thu, 01 Nov 2007 03:39:02 -0400 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1InUdo-0007Fy-TX for xcon-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 03:39:01 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InUdj-0006un-H9 for xcon@ietf.org; Thu, 01 Nov 2007 03:38:55 -0400 Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InUdc-0004Dt-Mi for xcon@ietf.org; Thu, 01 Nov 2007 03:38:50 -0400 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 3C47D208E0; Thu, 1 Nov 2007 08:38:18 +0100 (CET) X-AuditID: c1b4fb3c-ae67bbb0000007e1-8f-4729826ade1f Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id F1ABB2001A; Thu, 1 Nov 2007 08:38:17 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Nov 2007 08:38:17 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [XCON] New version of the Conference Information Data Model -06- Date: Thu, 1 Nov 2007 08:35:13 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] New version of the Conference Information Data Model -06- Thread-Index: Acga1ipalUcVOHOzTsqPr+XbSCoHvABg4VrA References: <472607D9.1040100@nostrum.com> From: "Oscar Novo" To: "Avshalom Houri" , "Adam Roach" X-OriginalArrivalTime: 01 Nov 2007 07:38:17.0809 (UTC) FILETIME=[2B3CAC10:01C81C5A] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 1.8 (+) X-Scan-Signature: e95407604bef3289cd27cb4f3b3a35b4 Cc: Ben Campbell , xcon@ietf.org, Miguel-Angel Garcia , alan johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1409701046==" Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1409701046== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C81C59.BD661E74" This is a multi-part message in MIME format. ------_=_NextPart_001_01C81C59.BD661E74 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks Avshalom for your target review.=20 If the rest of reviewers are fast enough and you can check if all your comments are addressed, I can create a new version of the draft if some modification is needed before the cut-off. =20 Thanks, =20 Oscar =20 ________________________________ From: Avshalom Houri [mailto:AVSHALOM@il.ibm.com]=20 Sent: 30. lokakuuta 2007 11:24 To: Adam Roach Cc: alan johnston; Ben Campbell; Mary Barnes; Miguel-Angel Garcia; Oscar Novo; Srivatsa Srinivasan; xcon@ietf.org Subject: Re: [XCON] New version of the Conference Information Data Model -06- I have done re-review (checking if my comments were addressed) and all my comments were addressed.=20 --Avshalom Adam Roach =20 29/10/2007 18:18=20 To Oscar Novo =20 cc xcon@ietf.org, Miguel-Angel Garcia , Avshalom Houri/Haifa/IBM@IBMIL, Ben Campbell , Srivatsa Srinivasan , Mary Barnes , alan johnston =20 Subject Re: [XCON] New version of the Conference Information Data Model -06- =09 Dedicated Reviewers: Please perform a targeted review of the revised data model, focusing on=20 ensuring that your concerns have been addressed. Please respond to me=20 and Alan with an estimated date by which you believe you can complete=20 this review. (I anticipate that such re-reviews will take a minimum=20 amount of time, and request that they be performed this week, if at all=20 possible). After all five reviewers have completed their re-review, we will enter a two-week working group last call period. The plan is to have publication requested prior to our face-to-face=20 meeting in Vancouver, allowing us to concentrate on the event package=20 and protocol operations. Thanks to the data model authors for the new revision, and again to the=20 dedicated reviewers for their efforts in improving the document. /a [as chair] On 10/29/07 5:00 AM, Oscar Novo wrote: > > Hello, > > You can find a new version of the Conference Information Data Model at: > > _http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-0 6.txt_=20 > > > In this version, we try to solve all the issues and clarifications of=20 > the five dedicated reviewers selected in the last meeting. You can=20 > find the reviews in the XCON mailing list. Here you have the links: > > Miguel's review: > > _http://www1.ietf.org/mail-archive/web/xcon/current/msg02025.html_ > > Avshalom's review: > > _http://www1.ietf.org/mail-archive/web/xcon/current/msg02026.html_ > > Ben's review: > > _http://www1.ietf.org/mail-archive/web/xcon/current/msg02027.html_ > > Srivatsa's review: > > _http://www1.ietf.org/mail-archive/web/xcon/current/msg02028.html_ > > Mary Barne's review: > > _http://www1.ietf.org/mail-archive/web/xcon/current/msg02029.html_ > > As well, we try to solve the open issues discuss in the IETF 69. You=20 > can find the discussion in the minutes draft: > > _http://www3.ietf.org/proceedings/07jul/minutes/xcon.txt_ > > > This version has quiet many changes compared to the previous version=20 > (relax ng, structure of the document, security considerations, ...).=20 > Here, we only try to summarized the three major changes/problems in=20 > this version of the document: > > - We have removed the roles from the document since we believe is much > better to define the roles and their definition in a future policy=20 > document. Many of the reviewers have some concerns about the roles=20 > chapter and we could see the definition of roles is not enough mature=20 > to add it in the data model. > > - Few reviewers didn't like the idea to have a refer method in the=20 > , the initial concern is that this element is=20 > overloaded. We have decided to keep this element because in the=20 > IETF-60 meeting it was a consensus that a separate refer list was=20 > needed, mainly because the list is not a list of users that the focus=20 > invites to join the conference (dial-out list). Of course, we can=20 > discusses again this point and if the working group feels it's=20 > appropriate to remove this element from the data model we can do so in > the next version. > > - As it was decided in the IETF-69 we have collapsed all the=20 > sub-element of and into a single one. > > =20 > Not need to mention that all your comments are very welcome! > > Cheers, > > Oscar > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > XCON mailing list > XCON@ietf.org > https://www1.ietf.org/mailman/listinfo/xcon =20 > =20 ------_=_NextPart_001_01C81C59.BD661E74 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Thanks=20 Avshalom for your target review.
If the=20 rest of reviewers are fast enough and you can check if all your comments = are=20 addressed, I can create a new version of the draft if some modification = is=20 needed before the cut-off.
 
Thanks,
 
Oscar
 

From: Avshalom Houri=20 [mailto:AVSHALOM@il.ibm.com]
Sent: 30. lokakuuta 2007=20 11:24
To: Adam Roach
Cc: alan johnston; Ben = Campbell; Mary=20 Barnes; Miguel-Angel Garcia; Oscar Novo; Srivatsa Srinivasan;=20 xcon@ietf.org
Subject: Re: [XCON] New version of the = Conference=20 Information Data Model -06-


I have done re-review = (checking if=20 my comments were addressed) and all my comments were addressed. =

--Avshalom






Adam Roach=20 <adam@nostrum.com>

29/10/2007 18:18

To
Oscar Novo=20 <oscar.novo@ericsson.com>=20
cc
xcon@ietf.org, = Miguel-Angel Garcia=20 <miguel.garcia@nsn.com>, Avshalom = Houri/Haifa/IBM@IBMIL, Ben=20 Campbell <ben@nostrum.com>, Srivatsa Srinivasan=20 <srivats@microsoft.com>, Mary Barnes=20 <mary.barnes@nortel.com>, alan johnston=20 <alan@sipstation.com>=20
Subject
Re: [XCON] New version of = the=20 Conference Information Data Model = -06-

=




Dedicated Reviewers:

Please perform a targeted review of = the=20 revised data model, focusing on
ensuring that your concerns have = been=20 addressed. Please respond to me
and Alan with an estimated date by = which you=20 believe you can complete
this review. (I anticipate that such = re-reviews=20 will take a minimum
amount of time, and request that they be = performed this=20 week, if at all
possible).

After all five reviewers have = completed=20 their re-review, we will enter a
two-week working group last call=20 period.

The plan is to have publication requested prior to our=20 face-to-face
meeting in Vancouver, allowing us to concentrate on the = event=20 package
and protocol operations.

Thanks to the data model = authors for=20 the new revision, and again to the
dedicated reviewers for their = efforts in=20 improving the document.

/a

[as chair]


On = 10/29/07 5:00=20 AM, Oscar Novo wrote:
>
> Hello,
>
> You can = find a new=20 version of the Conference Information Data Model at:
>
>=20 _http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-06= .txt_=20
>
>
> In this version, we try to solve all the issues = and=20 clarifications of
> the five dedicated reviewers selected in the = last=20 meeting. You can
> find the reviews in the XCON mailing list. = Here you=20 have the links:
>
> Miguel's review:
>
>=20 _http://www1.ietf.org/mail-archive/web/xcon/current/msg02025.html_
>= ;
>=20 Avshalom's review:
>
>=20 _http://www1.ietf.org/mail-archive/web/xcon/current/msg02026.html_
>= ;
>=20 Ben's review:
>
>=20 _http://www1.ietf.org/mail-archive/web/xcon/current/msg02027.html_
>= ;
>=20 Srivatsa's review:
>
>=20 _http://www1.ietf.org/mail-archive/web/xcon/current/msg02028.html_
>= ;
>=20 Mary Barne's review:
>
>=20 _http://www1.ietf.org/mail-archive/web/xcon/current/msg02029.html_
>= ;
>=20 As well, we try to solve the open issues discuss in the IETF 69. You =
>=20 can find the discussion in the minutes draft:
>
>=20 _http://www3.ietf.org/proceedings/07jul/minutes/xcon.txt_
>
>=
>=20 This version has quiet many changes compared to the previous version =
>=20 (relax ng, structure of the document, security considerations, ...). =
>=20 Here, we only try to summarized the three major changes/problems in =
>=20 this version of the document:
>
> - We have removed the = roles from=20 the document since we believe is much
> better to define the = roles and=20 their definition in a future policy
> document. Many of the = reviewers=20 have some concerns about the roles
> chapter and we could see the = definition of roles is not enough mature
> to add it in the data=20 model.
>
> -  Few reviewers didn't like the idea to = have a=20 refer method in the
> <allowed-users-list>, the initial = concern is=20 that this element is
> overloaded. We have decided to keep this = element=20 because in the
> IETF-60 meeting it was a consensus that a = separate refer=20 list was
> needed, mainly because the list is not a list of users = that=20 the focus
> invites to join the conference (dial-out list). Of = course, we=20 can
> discusses again this point and if the working group feels = it's=20
> appropriate to remove this element from the data model we can = do so in=20
> the next version.
>
> - As it was decided in the = IETF-69 we=20 have collapsed all the
> sub-element of <conf-uris> and=20 <services-uris> into a single one.
>
>  
> = Not need=20 to mention that all your comments are very welcome!
>
>=20 Cheers,
>
> = Oscar
>
>
>
>
>
>=20 ------------------------------------------------------------------------<= BR>>
>=20 _______________________________________________
> XCON mailing=20 list
> XCON@ietf.org
> https://www1.ietf.org/mailman/listinfo/xcon<= FONT=20 size=3D2>
>  


------_=_NextPart_001_01C81C59.BD661E74-- --===============1409701046== 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 --===============1409701046==-- From xcon-bounces@ietf.org Thu Nov 01 04:38:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1InVZj-0005ja-2G; Thu, 01 Nov 2007 04:38:51 -0400 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1InVZh-0005dj-61 for xcon-confirm+ok@megatron.ietf.org; Thu, 01 Nov 2007 04:38:49 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1InVZg-0005Vh-OW for xcon@ietf.org; Thu, 01 Nov 2007 04:38:48 -0400 Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1InVZa-0006FI-As for xcon@ietf.org; Thu, 01 Nov 2007 04:38:43 -0400 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 06DD620955; Thu, 1 Nov 2007 09:38:21 +0100 (CET) X-AuditID: c1b4fb3c-b0e80bb0000007e1-cb-4729907c845c Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E1B0920A5E; Thu, 1 Nov 2007 09:38:20 +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, 1 Nov 2007 09:38:20 +0100 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] XCON Chatroom consensus Date: Thu, 1 Nov 2007 09:35:15 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] XCON Chatroom consensus Thread-Index: AcgNCOO9BlaO1nOkS26Stp16CxagAAAAmeBQA9S19IA= References: <470FCF4A.9050505@nostrum.com> From: "Oscar Novo" To: "Mary Barnes" , "Adam Roach" , "Spencer Dawkins" X-OriginalArrivalTime: 01 Nov 2007 08:38:20.0858 (UTC) FILETIME=[8ED251A0:01C81C62] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af Cc: xcon@ietf.org X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Hello, After the discussion of the new chatroom elements that should be include in the data model. Here it's some more comments about the topic. If the WG agree on that I'll add these elements in the next version of the data model. Comments as [ON]. Cheers, Oscar -----Original Message----- From: Mary Barnes [mailto:mary.barnes@nortel.com]=20 Sent: 12. lokakuuta 2007 23:35 To: Adam Roach Cc: Oscar Novo; xcon@ietf.org Subject: RE: [XCON] XCON Chatroom consensus Adam, More responses inline below [MB2]. Mary. -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com] Sent: Friday, October 12, 2007 2:47 PM To: Barnes, Mary (RICH2:AR00) Cc: Oscar Novo; xcon@ietf.org Subject: Re: [XCON] XCON Chatroom consensus On 10/12/07 1:49 PM, Mary Barnes wrote: > -----Original Message----- > From: Oscar Novo [mailto:oscar.novo@ericsson.com] > > Section 2.4.3 (Password-Protected Chatrooms) > > "The current framework described in XCON uses user authentication for=20 > admissions control. However, some deployed systems instead use a=20 > single, chatroom-wide password that can be used to enter a chatroom. > This allows users to disseminate the password as a kind of invitation=20 > token without explicitly provisioning the allowed users into the=20 > chatroom system." > > If we decide to add this feature, it will require a new field=20 > ("conference password") in the XCON data model under element. > > [MB] But, the XCON model still requires that we have each user in the=20 > <"allowed-users-list"> and there is already a field for whether or not > PIN authorization (e.g., "IVR") is required. This chatroom-wide=20 > password is specific to the authentication and separate from the issue > as to whether or not you provision allowed users in the chatroom=20 > system (i.e., from the end user perspective, they only need the PW,=20 > the conferencing system functionality still needs the allocate=20 > identifiers and create the allowed users). [/MB] > =20 I was under the impression that one could create conferences that allowed general membership, without needing to add people to the . (If not, I think we'll run into problems). [MB2] You can have conferences with general membership, BUT the conferencing system associates an identifier with each user. The framework does mention (section 5.3) that while the user identifier is NOT required to join a conference, it is necessary to manipulate a conference. Non-XCON aware users (for lack of a better term) aren't expected to be aware of the user identifier - it's a system thing. But, it might also be necessary to include in notifications to XCON-aware clients as to conference membership, etc. I almost think the element should just be renamed as I think the other attributes, such as user-admission-policy, introduce the "allowed" aspect - i.e., that list is all users associated that can potentially be associated with the conference instance. [/MB2] The PIN concept is pretty much what we're looking for here, but we need a mechanism to extend it to other protocols. My reading right now is that the PIN in the data model is good only for PSTN users. [MB2] It's my understanding that a PIN concept could apply to any user type. But, maybe I've misunderstood the data model. Actually, there may be an inconsistency in the data model. It does say in section 4.1.2. that a URI of PSTN-ISDN has a "PIN code" attribute, however, there is a "join-handling" value of "IVR" in 4.5. which specifies that the user must provide a PIN and I don't think that is restricted to the PSTN-ISDN user. So, I wonder if that "PIN code" attribute is really necessary in the PSTN-type definition? [/MB2] [ON] In the version 06 of the data model we have modified the 'IVR' value of the element for an 'authenticate' value. The 'authenticate' value is not restricted to the PSTN-ISDN users as the 'IVR' value. As well, the element does not have the element anymore under . These changes have been done to validate the consensus achieve in the last ietf meeting. =20 In the next version of the draft we can add a new attribute 'conference password' in the element to complete the requirements of the discussion above.=20 [/ON] > 2.4.4. (Private and Semi-Private Chatrooms) > > "Currently, the XCON model allows users to be marked individually as=20 > anonymous or not via their corresponding tag. Some > systems, however, include a chatroom-wide setting that can be used to=20 > specify that all users in a chatroom are either completely anonymous=20 > (private), or anonymous to all users with equal or lesser permissions=20 > (semi-private)." > > If we decide to add this feature, it will require to modify the=20 > element with the values "private" and "semi-private" > instead of Boolean. > > [MB] I agree with Oscar's proposal. [/MB] > =20 So do I. [ON] We'll do that [/ON] > 2.4.5. (Banned Users) > > In addition to removing specific users from a conference, most=20 > deployed systems permit the specification of "banned" users. Such=20 > banned users are prevented from re-joining the chatroom until they=20 > have been un-banned. Currently it's needed additional work in the case > where all users are authenticated" > > If we decide to add this feature, a is needed to=20 > reject any users in the conference. > > [MB] I agree with Oscar's reponse on this one. [/MB] > =20 So do I. [ON] We'll do that [/ON] > 2.4.10.3. (Indication of Chatroom Log Archive Location) > > "Some systems include the ability for clients to access the on-line=20 > archive of a chatroom log from within the context of their chatroom=20 > client. (e.g., a menu selection or button that brings up a the=20 > chatroom log)." > > This feature can be defined using the element defined=20 > in RFC4575. Not need to create new elements. > =20 Ah, yes. I overlooked that. A service-uri pointing to a web-page with a purpose of "recording" would certainly serve the purpose quite nicely.=20 I'll make a note of this. Thanks for pointing it out. > 2.4.12. (Detailed User Registration) > > "Some chatroom systems allow -- and some require -- registration of=20 > detailed information about a user before they are allowed to join a=20 > chatroom. Currently, the XCON data model does not include a way to=20 > store persistent information (name, nickname, email address, etc.)=20 > about users who are not actively part of an ongoing chatroom session." > > The three solutions propose in the draft are: > > (1) Adding elements to the / element in=20 > the XCON data model that store information about users who are=20 > associated with the chatroom, but not presently participating in it; > > [MB] This is already "allowed" in the framework (i.e., an allowed-user > shouldn't necessarily have to be a participant), particularly in that=20 > a reservation can be setup with a list of allowed-users without them=20 > having yet joined the conference and per the 2nd sentence in section 5.3 > of the framework. My understanding was that it would then be up to a > conferencing system as to how it manages the persistence of the data - > if not then maybe we need something more in the framework, as well=20 > (e.g., a statement like "As well as users appearing in specific=20 > conference objects, a conferencing may maintain persistent information > about users." in section 5.3, possibly in the are where it is=20 > discussed that conference user identifiers can be distributed out-of-band,etc. > [/MB] > =20 I think you misread what I was proposing. I was pointing out that the is where we keep information about users associated with the conference but not currently participating in it. I said that we need to add elements to these entries that contain ancillary information, like name, nickname, email, etc. [MB2] Okay, I see your point and agree that we would need to add that additional info. [MB2] [ON] We'll add the solution number one to the next version of the data model [/ON] > 2.4.16. (Designation of Chatroom Language) > > "The XCON data model does not currently provide a mechanism for=20 > indicating the predominant language that is expected to be employed=20 > within a conference." > > The intention of the data model was to define this feature using the=20 > attribute 'lang' specify in the element. > We'll rewrote the text to make this idea more clear in the next version. > > [MB] I agree with Oscar, as I thought that was already in the data=20 > model. [/MB] > =20 Umm... I was under the impression that the language tag here indicated what language was being used in the , not in the conference itself. I guess one can take it as implied that the conference will be in the same language as the description, but that doesn't quite feel right to me. I would *personally* prefer it be more explicit than that in the data model. If consensus is that we want to necessarily use the language indicator in the to *also* indicate the language used inside the conference, then such a binding does, at least, need to be made explicit. [MB2] Okay, I see your point here too and agree that we likely need both. [/MB2] [ON] We'll add a new element under to differentiate both cases. [/ON] /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Sun Nov 04 20:54:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IorB0-0007Ag-Qh; Sun, 04 Nov 2007 20:54:54 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IorAz-00079g-KZ for xcon-confirm+ok@megatron.ietf.org; Sun, 04 Nov 2007 20:54:53 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IorAz-000798-7B for xcon@ietf.org; Sun, 04 Nov 2007 20:54:53 -0500 Received: from mail7.exchange.microsoft.com ([131.107.1.27] helo=mail.exchange.microsoft.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IorAy-0007c1-Ky for xcon@ietf.org; Sun, 04 Nov 2007 20:54:53 -0500 Received: from df-bhd-03.exchange.corp.microsoft.com (157.54.64.196) by DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft SMTP Server (TLS) id 8.1.236.0; Sun, 4 Nov 2007 17:54:51 -0800 Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by DF-BHD-03.exchange.corp.microsoft.com ([2002:9d36:40c4::9d36:40c4]) with mapi; Sun, 4 Nov 2007 17:54:51 -0800 From: Srivatsa Srinivasan To: Oscar Novo , "xcon@ietf.org" Date: Sun, 4 Nov 2007 17:55:08 -0800 Thread-Topic: New version of the Conference Information Data Model -06- Thread-Index: AcgaEuSdsgj7pfk+RIODHiSTgsl4/gFNkcbw Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 876202f9cbc0933cffbc58102e40f8f2 Cc: Subject: [XCON] RE: New version of the Conference Information Data Model -06- X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0312764270==" Errors-To: xcon-bounces@ietf.org --===============0312764270== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_C916C5C17067EA4A93577D163338D1370121BA2660A6DFGRTDANEMS_" --_000_C916C5C17067EA4A93577D163338D1370121BA2660A6DFGRTDANEMS_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Oscar et. Al I have reviewed this draft and most of my earlier comments have been addres= sed. Those comments that have not been addressed in full are not critical e= nough to warrant a rewrite. I noticed that the state attributes have been r= emoved from this version and will now be defined in the event package exten= sions draft. This makes this draft MUCH cleaner, thank you! Couple of minor nits follow (none of which require a rewrite). The first one is in section 4.5.4 is -- conference-floor-policy is defined = as a mandatory element, however, the tree diagram does not show this as man= datory. The second one is in Section 6 titled "XML Schema Extensibility". "The IETF MAY extend the data model schema with extension elements from the same namespace, but other instances are free to extend it from other than urn:ietf:params:xml:ns:xcon-conference-info." This should be corrected to read as follows. "The IETF MAY extend the data model schema with extension elements from the same namespace in future. Other instances are free to define extensi= on elements under any namespace other than urn:ietf:params:xml:ns:xcon-conf= erence-info." Regards, Srivatsa. From: Oscar Novo [mailto:oscar.novo@ericsson.com] Sent: Monday, October 29, 2007 3:00 AM To: xcon@ietf.org Subject: [XCON] New version of the Conference Information Data Model -06- Hello, You can find a new version of the Conference Information Data Model at: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-06.tx= t In this version, we try to solve all the issues and clarifications of the f= ive dedicated reviewers selected in the last meeting. You can find the revi= ews in the XCON mailing list. Here you have the links: Miguel's review: http://www1.ietf.org/mail-archive/web/xcon/current/msg02025.html Avshalom's review: http://www1.ietf.org/mail-archive/web/xcon/current/msg02026.html Ben's review: http://www1.ietf.org/mail-archive/web/xcon/current/msg02027.html Srivatsa's review: http://www1.ietf.org/mail-archive/web/xcon/current/msg02028.html Mary Barne's review: http://www1.ietf.org/mail-archive/web/xcon/current/msg02029.html As well, we try to solve the open issues discuss in the IETF 69. You can fi= nd the discussion in the minutes draft: http://www3.ietf.org/proceedings/07jul/minutes/xcon.txt This version has quiet many changes compared to the previous version (relax= ng, structure of the document, security considerations, ...). Here, we onl= y try to summarized the three major changes/problems in this version of the= document: - We have removed the roles from the document since we believe is much bett= er to define the roles and their definition in a future policy document. Ma= ny of the reviewers have some concerns about the roles chapter and we could= see the definition of roles is not enough mature to add it in the data mod= el. - Few reviewers didn't like the idea to have a refer method in the , the initial concern is that this element is overloaded. We h= ave decided to keep this element because in the IETF-60 meeting it was a co= nsensus that a separate refer list was needed, mainly because the list is n= ot a list of users that the focus invites to join the conference (dial-out = list). Of course, we can discusses again this point and if the working grou= p feels it's appropriate to remove this element from the data model we can = do so in the next version. - As it was decided in the IETF-69 we have collapsed all the sub-element of= and into a single one. Not need to mention that all your comments are very welcome! Cheers, Oscar --_000_C916C5C17067EA4A93577D163338D1370121BA2660A6DFGRTDANEMS_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable New version of the Conference Information Data Model -06-

Oscar et. Al

 

I have reviewed this draft and most of my earlier comments have been addresse= d. Those comments that have not been addressed in full are not critical enough= to warrant a rewrite. I noticed that the state attributes have been removed fr= om this version and will now be defined in the event package extensions draft.= This makes this draft MUCH cleaner, thank you!

 

Couple of minor nits follow (none of which require a rewrite).

 

The first one is in section 4.5.4 is -- conference-floor-policy is defined as a mandatory element, however, the tree diagram does not show this as mandator= y.

 

The second one is in Section 6 titled “XML Schema Extensibility&=
#8221;.
 
“The
   IETF MAY extend the data model schema with exten=
sion elements from
   the same namespace, bu=
t other instances are free to extend it from
 &nb=
sp; other than urn:ietf:params:xml:ns:xcon-conference-info.”
 
This should be corrected to read a=
s follows.

 

“The
   IETF MAY extend the data =
model schema with extension elements from
  =
 the same namespace in future. Other instances are free to define extension=
 elements under any namespace other than urn:ietf:params:xml:ns:xcon-confer=
ence-info.”

 

Regards,

Srivatsa.

 

From: Oscar Novo [mailto:oscar.novo@ericsson.com]
Sent: Monday, October 29, 2007 3:00 AM
To: xcon@ietf.org
Subject: [XCON] New version of the Conference Information Data Model -06-

 

Hello,=

You ca= n find a new version of the Conference Information Data Model at:

http://www.ietf= .org/internet-drafts/draft-ietf-xcon-common-data-model-06.txt

In thi= s version, we try to solve all the issues and clarifications of the five dedicated reviewers selected in the last meeting. You can find the reviews in the XCON mailing list. Here you have the links:

Miguel= 's review:

http://www1.iet= f.org/mail-archive/web/xcon/current/msg02025.html

Avshal= om's review:

http://www1.iet= f.org/mail-archive/web/xcon/current/msg02026.html

Ben's review:

http://www1.iet= f.org/mail-archive/web/xcon/current/msg02027.html

Srivat= sa's review:

http://www1.iet= f.org/mail-archive/web/xcon/current/msg02028.html

Mary B= arne's review:

http://www1.iet= f.org/mail-archive/web/xcon/current/msg02029.html

As wel= l, we try to solve the open issues discuss in the IETF 69. You can find the discussion in the minutes draft:

http://www3.ietf.org/p= roceedings/07jul/minutes/xcon.txt

 

This v= ersion has quiet many changes compared to the previous version (relax ng, structur= e of the document, security considerations, ...). Here, we only try to summarize= d the three major changes/problems in this version of the document:

- We h= ave removed the roles from the document since we believe is much better to defi= ne the roles and their definition in a future policy document. Many of the reviewers have some concerns about the roles chapter and we could see the definition of roles is not enough mature to add it in the data model.

- = ; Few reviewers didn't like the idea to have a refer method in the <allowed-users-list>, the initial concern is that this element= is overloaded. We have decided to keep this element because in the IETF-60 mee= ting it was a consensus that a separate refer list was needed, mainly because th= e list is not a list of users that the focus invites to join the conference (dial-out list). Of course, we can discusses again this point and if the wo= rking group feels it's appropriate to remove this element from the data model we = can do so in the next version.

- As i= t was decided in the IETF-69 we have collapsed all the sub-element of <conf-uris> and <services-uris> into a single one.<= /o:p>

 =
Not need = to mention that all your comments are very welcome!

Cheers= ,

Oscar =




--_000_C916C5C17067EA4A93577D163338D1370121BA2660A6DFGRTDANEMS_-- --===============0312764270== 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 --===============0312764270==-- From xcon-bounces@ietf.org Mon Nov 05 12:57:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip6CA-0000b4-Hw; Mon, 05 Nov 2007 12:57:06 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Ip6C9-0000X1-4d for xcon-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 12:57:05 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip6C8-0000Wr-PO for xcon@ietf.org; Mon, 05 Nov 2007 12:57:04 -0500 Received: from zcars04e.nortel.com ([47.129.242.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Ip6C8-0005RR-4P for xcon@ietf.org; Mon, 05 Nov 2007 12:57:04 -0500 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id lA5Hrrr19972; Mon, 5 Nov 2007 17:53:53 GMT 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] New version of the Conference Information Data Model -06- Date: Mon, 5 Nov 2007 11:54:29 -0600 Message-ID: In-Reply-To: <472607D9.1040100@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] New version of the Conference Information Data Model -06- Thread-Index: AcgaR2hB6HBAROo6TjuxdGuh5nkfJwFg5iiQ References: <472607D9.1040100@nostrum.com> From: "Mary Barnes" To: "Oscar Novo" X-Spam-Score: 0.0 (/) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Cc: Adam Roach , xcon@ietf.org X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org I re-reviewed the document, in particular the comments and nits I had previously noted. All the nits I had identified have been addressed. There are a few new nits I noticed and I have one remaining comment related to my previous comments. Comment: -------- The one remaining comment is around the roles related to my previous comment on the 2nd paragraph in section 3.2. My previous comment had been primarily around the text in the 2nd paragraph which had some inaccuracies and inconsistencies with the framework. =20 Per your past response to my comments that entire section discussing the roles was to be removed. However, the concept of role remains and it's definition has changed to "text" from the base "role-type" (Note that the "single-role-type" is still defined in the schema). The "role" element is used in the examples based on the previously defined types and the introductory text in section 7 refers to those previously defined types. I see that the reference for "roles" in section 4.6.4.4 is RFC 4575, however, that document doesn't give any information at all about those types and just mentions that they'll be defined in the future. I think this document should define them.=20 I can see that the text in the -05 and previous versions of this document was based on the draft specifically on roles: http://tools.ietf.org/html/draft-morgan-xcon-roles-00 So, I don't think we need a separate document. At a minimum, I would suggest just taking some of that previous text in 3.2 and putting it in section 4.6.4.4. something like: This child element consists of a set of the following string values:=20 "administrator", "creator", "moderator", "participant", and "observer". =20 A user with the role of "administrator" typically SHOULD be allowed to make changes=20 to all conference variables during the full lifecycle of the Conference Object.=20 A user with the role of "creator" SHOULD be allowed to modify specific conference variables, subject to local policy, of a conference reservation and an active conference. =20 A user with the role of "moderator" has specific privileges, subject to local policy,=20 that allow them to manipulate specific conference variables such as adding new users=20 to an active conference or controlling when the media for a conference. A user with a=20 role of "participant" typically is not allowed to modify conference variables other than those specific to the user's own media (e.g., "mute") or participation. A user with a role of=20 "observer" typically can only receive media streams from the conference. Each user participating in a conference instance is an entity that can assume one or more roles. If no roles are defined for an entity, they SHOULD=20 by default be a "participant" but local policy MAY define an alternative. A Conference System MAY not support all roles. As well, additional roles may be defined=20 in the future, as necessary, with their corresponding schema extensions. Nits: ----- 1) Section 3.3/Section 9.3: "XCON-URI" is used in section 3.3., but the IANA registry uses "XCON_URI" 2) Section 3.3, Figure 2: for some reason the bottom of the box for BFCP is skewed in the text version of the doc - it's fine in the HTML version. 3) Section 4.6.2. Expand PSTN (I noticed this only because I was double-checking the global changes of PSTN =3D> ISUP, etc. =20 -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com]=20 Sent: Monday, October 29, 2007 11:19 AM To: Oscar Novo Cc: xcon@ietf.org; Miguel-Angel Garcia; Avshalom Houri; Ben Campbell; Srivatsa Srinivasan; Barnes, Mary (RICH2:AR00); alan johnston Subject: Re: [XCON] New version of the Conference Information Data Model -06- Dedicated Reviewers: Please perform a targeted review of the revised data model, focusing on ensuring that your concerns have been addressed. Please respond to me and Alan with an estimated date by which you believe you can complete this review. (I anticipate that such re-reviews will take a minimum amount of time, and request that they be performed this week, if at all possible). After all five reviewers have completed their re-review, we will enter a two-week working group last call period. The plan is to have publication requested prior to our face-to-face meeting in Vancouver, allowing us to concentrate on the event package and protocol operations. Thanks to the data model authors for the new revision, and again to the dedicated reviewers for their efforts in improving the document. /a [as chair] _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Nov 06 14:57:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpUXu-0003Q9-At; Tue, 06 Nov 2007 14:57:10 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IpUXs-0003NE-Gm for xcon-confirm+ok@megatron.ietf.org; Tue, 06 Nov 2007 14:57:08 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpUXs-0003N6-5E for xcon@ietf.org; Tue, 06 Nov 2007 14:57:08 -0500 Received: from dsl001-129-069.dfw1.dsl.speakeasy.net ([72.1.129.69] helo=vicuna.estacado.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpUXp-0001Tw-Tp for xcon@ietf.org; Tue, 06 Nov 2007 14:57:08 -0500 Received: from localhost (alpaca.estacado.net [72.1.129.68]) (authenticated bits=0) by vicuna.estacado.net (8.14.1/8.14.1) with ESMTP id lA6JuipI025155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 6 Nov 2007 13:56:44 -0600 (CST) (envelope-from ben@estacado.net) Message-Id: <14E957F0-B14D-4D7E-B5EA-16775B959F27@estacado.net> From: Ben Campbell To: Adam Roach In-Reply-To: <472607D9.1040100@nostrum.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: Re: [XCON] New version of the Conference Information Data Model -06- Date: Tue, 6 Nov 2007 13:56:38 -0600 References: <472607D9.1040100@nostrum.com> X-Mailer: Apple Mail (2.912) X-Spam-Score: 0.1 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d Cc: Avshalom Houri , alan johnston , Miguel-Angel Garcia , xcon@ietf.org X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org I apologize for the lateness of this re-review--It's been an exceptionally busy couple of weeks. Most of my comments have been addressed, or were really not important enough to worry about. There is still one nit that does not appear to be addressed, and I have a new concern that I failed to discover the first time: IANA Considerations: This section seems lightweight compared to what I usually expect to see. It has nice syntax definitions, but unless I am missing something, doesn't offer specific instructions to IANA about what to do with the definitions; i.e. what registries they go in, etc. Furthermore, if the section on the XCON_URI is intended to register the URI scheme, it does not follow the procedures for doing so as I understand them. Remaining nit: Page 17, bullet, end of paragraph: "The types are...": Unless I am missing something, I can find no definition for a element. Perhaps this was meant to be , or perhaps the word layout was not intended to be in angle-brackets? On Oct 29, 2007, at 11:18 AM, Adam Roach wrote: > Dedicated Reviewers: > > Please perform a targeted review of the revised data model, focusing > on ensuring that your concerns have been addressed. Please respond > to me and Alan with an estimated date by which you believe you can > complete this review. (I anticipate that such re-reviews will take a > minimum amount of time, and request that they be performed this > week, if at all possible). > > After all five reviewers have completed their re-review, we will > enter a two-week working group last call period. > > The plan is to have publication requested prior to our face-to-face > meeting in Vancouver, allowing us to concentrate on the event > package and protocol operations. > > Thanks to the data model authors for the new revision, and again to > the dedicated reviewers for their efforts in improving the document. > > /a > > [as chair] > > > On 10/29/07 5:00 AM, Oscar Novo wrote: >> >> Hello, >> >> You can find a new version of the Conference Information Data Model >> at: >> >> _http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-06.txt_ >> >> In this version, we try to solve all the issues and clarifications >> of the five dedicated reviewers selected in the last meeting. You >> can find the reviews in the XCON mailing list. Here you have the >> links: >> >> Miguel's review: >> >> _http://www1.ietf.org/mail-archive/web/xcon/current/msg02025.html_ >> >> Avshalom's review: >> >> _http://www1.ietf.org/mail-archive/web/xcon/current/msg02026.html_ >> >> Ben's review: >> >> _http://www1.ietf.org/mail-archive/web/xcon/current/msg02027.html_ >> >> Srivatsa's review: >> >> _http://www1.ietf.org/mail-archive/web/xcon/current/msg02028.html_ >> >> Mary Barne's review: >> >> _http://www1.ietf.org/mail-archive/web/xcon/current/msg02029.html_ >> >> As well, we try to solve the open issues discuss in the IETF 69. >> You can find the discussion in the minutes draft: >> >> _http://www3.ietf.org/proceedings/07jul/minutes/xcon.txt_ >> >> >> This version has quiet many changes compared to the previous >> version (relax ng, structure of the document, security >> considerations, ...). Here, we only try to summarized the three >> major changes/problems in this version of the document: >> >> - We have removed the roles from the document since we believe is >> much better to define the roles and their definition in a future >> policy document. Many of the reviewers have some concerns about the >> roles chapter and we could see the definition of roles is not >> enough mature to add it in the data model. >> >> - Few reviewers didn't like the idea to have a refer method in the >> , the initial concern is that this element is >> overloaded. We have decided to keep this element because in the >> IETF-60 meeting it was a consensus that a separate refer list was >> needed, mainly because the list is not a list of users that the >> focus invites to join the conference (dial-out list). Of course, we >> can discusses again this point and if the working group feels it's >> appropriate to remove this element from the data model we can do so >> in the next version. >> >> - As it was decided in the IETF-69 we have collapsed all the sub- >> element of and into a single one. >> >> Not need to mention that all your comments are very welcome! >> >> Cheers, >> >> Oscar >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Nov 09 05:27:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqR5K-0002AO-RR; Fri, 09 Nov 2007 05:27:34 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqR5J-00029E-EA for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 05:27:33 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqR5I-00028o-Up for xcon@ietf.org; Fri, 09 Nov 2007 05:27:33 -0500 Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqR5H-0005Ym-Rf for xcon@ietf.org; Fri, 09 Nov 2007 05:27:32 -0500 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id lA9AQtFd028181; Fri, 9 Nov 2007 12:27:27 +0200 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Nov 2007 12:27:21 +0200 Received: from [10.144.23.46] ([10.144.23.46]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Nov 2007 12:27:21 +0200 Message-ID: <47343609.3090809@nsn.com> Date: Fri, 09 Nov 2007 12:27:21 +0200 From: Miguel Garcia User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: XCON Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Nov 2007 10:27:21.0421 (UTC) FILETIME=[1C9B07D0:01C822BB] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0 Cc: Subject: [XCON] Follow-up on the XCON data model draft X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Hi: This is the first part of a follow-up of the comments on the XCON data model that I posted earlier. I haven't done the full follow-up, but I think there is enough meat for discussion. I will try to complete the follow-up sometime next week. My original comments are: http://www1.ietf.org/mail-archive/web/xcon/current/msg02025.html And I have been looking at their implementation in vesion -06 of the data model: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-06.txt Let me highlight here issues that require a bit more of discussion. New comments are preceded by "[MG]": ---- 6) Figure 1. There are one or more objects called "Conference Object". Each one contains just another object called "Conference Information Data Model". According to the figure, the Conference Object just contains a Conference Information Data model, nothing else, nothing more. This makes me think that both things are the same. Or, in other words, perhaps the "Conference information data model" should be removed from the figure. Or, if it shouldn't, then you need to describe the relation between both in textual form. [MG] I haven't seen any action in the figure nor in the text. ----- 8) I miss a motivation for the existence of roles at the beginning of Section 3.2 [MG] I noticed that the discussion about the actual values of roles have been dropped. I don't have any problem about that (although I prefer to have roles). However, there are some leftovers. - Section 4.2.6: The has the mandatory 'required-participant' attribute. This attribute has one of 4 values: "none", "administrator", "moderator", and "participant". This attribute allows a privileged user to define when media mixing starts based on the latter of the mixing start time, and the time the first participant, administrator, or moderator arrives. So, I guess the 'required-participant' attribute is referring to roles, and has 4 roles values... however the document does not define the roles... so I see a contradiction here. The same applies to the , , and elements. I think the draft is now lame, assuming certain roles but not clearly indicating them. -------- 11) Section 4, the paragraph above Figure 2: it mentions the XCON-URI without a reference to where it is defined. Then I saw it in the IANA considerations section, so THIS might be the canonical document that defines it. So, I think the XCON URI deserves a section by itself, describing the semantics, syntax, etc. [MG] While the section to the XCON URI has been devoted, I don't like the fact that you write the syntax embedded in the IANA considerations section. Such section is not the place for that. The current Section 3.3 needs to add a subsection where write the syntax of the URI. --------- 15) Section 4.1.1, second paragraph. The element is mixing two semantics: one one side, it indicates whether mixing starts according to either a specified time or when a participant with a role joins. I think it would much clear to create three elements instead: one is a , which can take the values "by-time", "by-joining-role", or "at-first-join". Another would be the existing , which would be restricted to indicating a time, and only available when takes the value "by-time". A third one is which would take the values "participant", "moderator", "administrator", and is only available is takes the value "by-joining-role". [MG] What happened to this comment? ---- 19) Section 4.1.5.1.1 defines the element and Section 4.1.5.1.2 defines the element. I think these two are very similar, the only difference being that the former applies to audio streams, the latter to video streams. I would like to see a single element, perhaps called or something like that. This could apply for any kind of media stream, even for MSRP. [MG] What happened to this comment? I think we shouldn't be defining specif actions on a per media stream basis. What we need here is an element to disable a media stream, no matter whether the stream is of type, audio, video, gaming, text, message, or something else. ------ 20) Section 4.1.5.1.3 defines the element. I am missing attributes that defines the minimum and maximum levels. Without it, if I get that the mixing level is 10, I have now idea if it is 10 in a scale 1-10, 10 in a scale 1-100, or 10 in a scale 1-1000. Further more, without the maximum/minimum level, it wouldn't be possible to create a UI scale representation, making the control totally useless. [MG] While the text now speaks about two attributes, 'min' and 'max', the do not appear in the RelaxNG nor in the XML schema. On the other hand, checking the RelaxNG schema, I have now realized that there is a minInclusive and maxInclusive values, effectively putting limits to the scale in the XML schema. I would like to ask opinions for what is the desired option here. There are 3 of these options. a) with limits (minInclusive, maxInclusive). So, this effectively hard codes the limits of the scale in the schema. The minimum and maximum values are -127 and 127. b) with the 'min' and 'max' attributes. So, in this way, the user controls the range of the scale. I could therefore say 7. The server would need to re-scale to whatever scale the server implements. c) with limits (minInclusive, maxInclusive) and 'min' and 'max' attributes. I think this is the worst solution, because it has the constraints of both solutions. So, I think I am going to propose solution a), which is essentially equivalent to withdrawing my initial comment. But I would suggest that you mention the hardcoded limits in the text, to avoid mislead the reader. My prposal for the description of the element in Section 4.2.10 is: * The element is used in conjunction with a media output stream to indicate the amount of amplification of an audio stream. The value is an integer number that ranges from -127 to 127. If this control is not specified, access to the control is not available to the client. ---- End of first part. /Miguel -- Miguel A. Garcia tel:+358-50-4804586 Nokia Siemens Networks Espoo, Finland _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Nov 09 13:08:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYGz-0005O0-3N; Fri, 09 Nov 2007 13:08:05 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqYGx-0005Fe-6z for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 13:08:03 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYGw-0005FW-Tf for xcon@ietf.org; Fri, 09 Nov 2007 13:08:02 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqYGw-0008Di-Nx for xcon@ietf.org; Fri, 09 Nov 2007 13:08:02 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id 9D58826E3F; Fri, 9 Nov 2007 18:08:02 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IqYGw-000835-Ht; Fri, 09 Nov 2007 13:08:02 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: mary.barnes@nortel.com From: IETF I-D Submission Tool Message-Id: Date: Fri, 09 Nov 2007 13:08:02 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: oritl@microsoft.com, xcon@ietf.org Subject: [XCON] New Version Notification for draft-ietf-xcon-framework-10 X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org A new version of I-D, draft-ietf-xcon-framework-10.txt has been successfuly submitted by Mary Barnes and posted to the IETF repository. Filename: draft-ietf-xcon-framework Revision: 10 Title: A Framework for Centralized Conferencing Creation_date: 2007-11-09 WG ID: xcon Number_of_pages: 64 Abstract: This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. The IETF Secretariat. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Nov 09 13:08:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYHB-0005uF-Ck; Fri, 09 Nov 2007 13:08:17 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqYHA-0005tw-66 for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 13:08:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYH9-0005to-Sm for xcon@ietf.org; Fri, 09 Nov 2007 13:08:15 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqYH9-0008EB-Md for xcon@ietf.org; Fri, 09 Nov 2007 13:08:15 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id 92B4226E3F; Fri, 9 Nov 2007 18:08:15 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1IqYH9-00083Q-GR; Fri, 09 Nov 2007 13:08:15 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: mary.barnes@nortel.com From: IETF I-D Submission Tool Message-Id: Date: Fri, 09 Nov 2007 13:08:15 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: oritl@microsoft.com, xcon@ietf.org Subject: [XCON] New Version Notification for draft-ietf-xcon-framework-10 X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org A new version of I-D, draft-ietf-xcon-framework-10.txt has been successfuly submitted by Mary Barnes and posted to the IETF repository. Filename: draft-ietf-xcon-framework Revision: 10 Title: A Framework for Centralized Conferencing Creation_date: 2007-11-09 WG ID: xcon Number_of_pages: 64 Abstract: This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. The IETF Secretariat. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Nov 09 13:10:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYJP-0000yN-5e; Fri, 09 Nov 2007 13:10:35 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqYJO-0000y7-7P for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 13:10:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYJN-0000xy-U1; Fri, 09 Nov 2007 13:10:33 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqYJL-0008Jk-ES; Fri, 09 Nov 2007 13:10:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 666CC3289D; Fri, 9 Nov 2007 18:10:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IqYIr-00038G-AS; Fri, 09 Nov 2007 13:10:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 09 Nov 2007 13:10:01 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: xcon@ietf.org Subject: [XCON] I-D Action:draft-ietf-xcon-framework-10.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , 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 : A Framework for Centralized Conferencing Author(s) : M. Barnes, et al. Filename : draft-ietf-xcon-framework-10.txt Pages : 64 Date : 2007-11-09 This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-10.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-framework-10.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-framework-10.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: <2007-11-09130759.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-xcon-framework-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-xcon-framework-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-09130759.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 Fri Nov 09 13:10:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYJX-0001Ea-R9; Fri, 09 Nov 2007 13:10:43 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqYJP-0000yT-8K for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 13:10:35 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYJO-0000yF-Sl; Fri, 09 Nov 2007 13:10:34 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IqYJL-0008Jl-FW; Fri, 09 Nov 2007 13:10:34 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 7097E328B6; Fri, 9 Nov 2007 18:10:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IqYIr-00038L-Bm; Fri, 09 Nov 2007 13:10:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 09 Nov 2007 13:10:01 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: xcon@ietf.org Subject: [XCON] I-D Action:draft-ietf-xcon-framework-10.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , 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 : A Framework for Centralized Conferencing Author(s) : M. Barnes, et al. Filename : draft-ietf-xcon-framework-10.txt Pages : 64 Date : 2007-11-09 This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-10.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-framework-10.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-framework-10.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: <2007-11-09130813.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-xcon-framework-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-xcon-framework-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-09130813.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 Fri Nov 09 13:16:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYPO-0000Rt-4H; Fri, 09 Nov 2007 13:16:46 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IqYPM-0000Qf-Rs for xcon-confirm+ok@megatron.ietf.org; Fri, 09 Nov 2007 13:16:44 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IqYPM-0000OC-B6 for xcon@ietf.org; Fri, 09 Nov 2007 13:16:44 -0500 Received: from zrtps0kp.nortel.com ([47.140.192.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IqYPK-0005ZT-Py for xcon@ietf.org; Fri, 09 Nov 2007 13:16:43 -0500 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lA9IGQE21741; Fri, 9 Nov 2007 18:16:27 GMT 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] I-D Action:draft-ietf-xcon-framework-10.txt Date: Fri, 9 Nov 2007 12:14:10 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] I-D Action:draft-ietf-xcon-framework-10.txt Thread-Index: Acgi+90SWwzNmnctRWC2fWRwFJ2uaQAAEWwg References: From: "Mary Barnes" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 850245b51c39701e2700a112f3032caa Cc: Cullen Jennings , alan@sipstation.com, Adam Roach X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Hi all, This updated version is the result of IETF LC comments from the gen-art and secdir reviews, along with some initial IESG feedback (OPS and Security) (document was deferred from 11/1 telechat and is on the agenda for 11/15). The summary of the changes is below. There shouldn't be anything of controversy as these are all clarifications or corrections to existing text. The diff is not yet available on the tools page, but should be there shortly. In the interim, you can easily create your own diff by using the rfcdiff tool: http://tools.ietf.org/rfcdiff =20 Thanks, Mary Changes from -09 and -10 of XCON FW: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1) Abstract and Section 1 (IESG (Dan Romascanu) Comment): OLD: The Centralized Conferencing Framework defines logical entities and naming conventions, along with a high level conferencing data model. NEW: The Centralized Conferencing Framework defines logical entities and naming conventions.=20 2) Section 5.2.1: removed confusing unclear 2nd sentence since it really added no value(Scott Brim's comment from gen-art review) and changed the tense of the 3rd sentence (editor's comment): OLD: =20 In order to make each conference object externally accessible, the conferencing system allocates a unique URI per distinct conference object in the system. The conference object identifier is created both by the conferencing system based on internal actions as well as based on specific conference protocol requests. A conferencing system will allocate a conferencing object identifier for every conference blueprint, for every conference reservation and for every active conference. NEW:=20 In order to make each conference object externally accessible, the conferencing system allocates a unique URI per distinct conference object in the system. A conferencing system allocates a conferencing object identifier for every conference blueprint, for every conference reservation and for every active conference. 3) Updates to security section based on secdir (Kurt Zeilenga) and IESG (Tim Polk) comments: 3a) Section 10. Added a fourth paragraph about DoS attacks at the end of that section just prior to 10.1: OLD (last sentence 3rd paragraph): A final set of issues involves the privacy and security of the identity of a user in the conference, which is discussed in Section 10.2. NEW: Another set of issues involves the privacy and security of the identity of a user in the conference, which is discussed in Section 10.2. =20 A final issue is related to Denial of Service (DoS) attacks on the conferencing=20 system itself. In order to minimize the potential for DoS attacks, it is=20 recommended that conferencing systems require user authentication and authorization for any client participating in a conference. It is recommended that the specific signaling and media protocols include mechanisms=20 to minimize the potential for DoS. 3b) Section 10.1. Clarifying Authentication versus Authorization 3bi) Renamed section: OLD:=20 Authorization NEW:=20 User Authentication and Authorization 3bii) First paragraph: expanded acronyms and clarified text. Added 2nd sentence (removed last sentence) and moved 4th and 5th sentences to the end: OLD: Many policy authorization decisions are based on the identity of the user or the role that a user may have. There are several ways that a user might authenticate its identity to the system. The conferencing system may know about specific users and assign passwords to the users. The users may also be authenticated by knowing a particular conference ID and a PIN for it. Sometimes, a PIN is not required and the conference ID is used as a shared secret. The call signaling means can provide a trusted form of the user identity or it might just provide a hint of the possible identity and the user still needs to provide some authentication to prove it has the identity that was provided as a hint in the call signaling. This may be in the form of an IVR system or other means. The goal for the conferencing system is to figure out a user identity and a role for any attempt to send a request to the conferencing system. =20 NEW: Many policy authorization decisions are based on the identity=20 of the user or the role that a user may have. Conferencing systems typically require authentication of users to validate their identity.=20 There are several ways that a user might authenticate its identity to the system.=20 For users joining a conference using one of the call signaling protocols, the=20 user authentication mechanisms for the specific protocol often suffice.=20 The conferencing system may also know (e.g., out of band mechanisms) about specific=20 users and assign passwords to allow these users to be authorized. In some cases additional authorization may be required to allow the user to participate in the=20 conference. This may be in the form of an Interactive Voice Response (IVR) system or other means. The users may also be authorized by knowing a particular conference ID and a Personal Identification (PIN) for it. Sometimes, a PIN is not=20 required and the conference ID is used as a shared secret. =20 3biii) 3rd paragraph (change "authenticates" to "authorizes"): OLD: When guest users interact with the system, it is often in the context of a particular conference. In this case, the user may provide a PIN or a password that is specific to the conferences and authenticates the user to take on a certain role in that conference. The guest user can then perform actions that are allowed to any user with that role. NEW: When guest users interact with the system, it is often in the context of a particular conference. In this case, the user may provide a PIN or a password that is specific to the conferences and authorizes ^^^^^^^^^^ the user to take on a certain role in that conference. The guest user can then perform actions that are allowed to any user with that role. 3biv) 4th paragraph: Reworded to add detail about the number of digits/characters associated with specific numbers of bits in first two sentences: OLD: The term password is used to mean the usual, that is to say a reasonable sized, in number of bits, hard to predict shared secret. Today users often have passwords with more than 30 bits of randomness in them. PIN is a special password case - a shared secret that is only numeric and often contains a fairly small number of bits (often as few as 10 bits). =20 NEW: The term password refers to the usual, reasonable sized and hard to=20 predict shared secret. Today users often have passwords containing up to=20 30 bits (8-16 characters). PIN is a special password case - a shared secret=20 that is only numeric and often contains a fairly small=20 number of bits (often as few as 10 bits or 3 digits). =20 4) Updated references (gen-art review comment): OLD: draft-ietf-simple-message-sessions draft-ietf-xcon-bfcp-connection NEW: RFC 4975 RFC 5018 5) Updated Chris' affiliation. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Friday, November 09, 2007 12:10 PM To: i-d-announce@ietf.org Cc: xcon@ietf.org Subject: [XCON] I-D Action:draft-ietf-xcon-framework-10.txt 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 : A Framework for Centralized Conferencing Author(s) : M. Barnes, et al. Filename : draft-ietf-xcon-framework-10.txt Pages : 64 Date : 2007-11-09 This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-10.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-framework-10.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-framework-10.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. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 12 12:58:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdXt-0000RK-Vm; Mon, 12 Nov 2007 12:58:01 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IrdXs-0000Pu-7m for xcon-confirm+ok@megatron.ietf.org; Mon, 12 Nov 2007 12:58:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdXr-0000O9-Sx for xcon@ietf.org; Mon, 12 Nov 2007 12:57:59 -0500 Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrdXo-0006Pi-6R for xcon@ietf.org; Mon, 12 Nov 2007 12:57:59 -0500 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lACHvrT27989; Mon, 12 Nov 2007 17:57:53 GMT 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 Date: Mon, 12 Nov 2007 11:55:14 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: I-D Action:draft-boulton-xcon-session-chat-00.txt Thread-Index: Acga0q8AnkGw81WGQrSpLMBlieyoDAAQFZ8w From: "Mary Barnes" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: Subject: [XCON] FW: I-D Action:draft-boulton-xcon-session-chat-00.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Hi all, Just a note that this document replaces draft-boulton-xcon-msrp-conferencing-05. The updates include a new section to address some of the additional capabilities as identified in draft-roach-xcon-chatroom-analysis-00, as well as updating to reflect the current status of the SIMPLE WG chat document. It is still lacking in detail in terms of protocol details, but we'd prefer to get feedback on the general approach and to await further WG agreement on the way forward for a detailed protocol before adding a lot more detail. Thanks, Mary and Chris. -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Monday, October 29, 2007 9:30 PM To: i-d-announce@ietf.org Subject: I-D Action:draft-boulton-xcon-session-chat-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Instant Messaging Sessions within a Centralized Conferencing (XCON) System Author(s) : C. Boulton, M. Barnes Filename : draft-boulton-xcon-session-chat-00.txt Pages : 23 Date : 2007-10-29 The document "A Framework for Centralized Conferencing" defines a centralized conference as both signaling and protocol agnostic. The primary examples within this framework focus on audio and video as the media types for the session. This document describes the mechanisms, in the context of this centralized conferencing framework, when using instant messaging sessions as the media. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-boulton-xcon-session-chat-00.t xt 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-boulton-xcon-session-chat-00.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-boulton-xcon-session-chat-00.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. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 12 13:05:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdfM-0004Kg-KW; Mon, 12 Nov 2007 13:05:44 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IrdfK-0004I8-0A for xcon-confirm+ok@megatron.ietf.org; Mon, 12 Nov 2007 13:05:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrdfJ-0004Hr-Jt for xcon@ietf.org; Mon, 12 Nov 2007 13:05:41 -0500 Received: from cse.stfx.ca ([141.109.37.172]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrdfI-0003Ol-Gq for xcon@ietf.org; Mon, 12 Nov 2007 13:05:41 -0500 Received: from cse.stfx.ca (localhost [127.0.0.1] (may be forged)) by cse.stfx.ca (8.14.1/8.13.8) with ESMTP id lACHQmj5017364 for ; Mon, 12 Nov 2007 13:26:48 -0400 Received: (from mello@localhost) by cse.stfx.ca (8.14.1/8.13.8/Submit) id lACHQlIj017363; Mon, 12 Nov 2007 13:26:47 -0400 Date: Mon, 12 Nov 2007 13:26:47 -0400 Message-Id: <200711121726.lACHQlIj017363@cse.stfx.ca> To: xcon@ietf.org From: ltyang@gmail.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129 Subject: [XCON] CFP and CFW Proposals: CSE-08 in Brazil X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ltyang@gmail.com List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Please apologize for multiple copies. *Call for Papers and Workshop Proposals* *2008 IEEE 11th International Conference on Computational Science and Engineering* *CSE 2008* http://www.icmc.usp.br/cse08 July 16-18, 2008 - Sao Paulo - Brazil *Important Dates* ================= Workshop Proposals due: December 14, 2007 Paper submission due: January 25, 2008 Paper notification of acceptance: March 21, 2008 Final camera ready: April 25, 2008 *Paper submission* ================== Paper submission web site http://cse.stfx.ca/~cse08/sub/ Authors are expected to submit a paper in the PDF format with 5-10 keywords following the IEEE CS format (http://www.icmc.usp.br/~cse08/submission.html). Program committee members and external reviewers will provide authors with at least three technical reviews. Submitted papers will be ranked based on relevance to the Conference and technical merit. Final version of accepted papers should at most 8 pages and will be published by IEEE Computer Society Press as CSE 2008 conference proceedings. Authors of accepted papers, or at least one of them, are requested to register and present their work at the conference, otherwise their papers will be removed from the IEEE Digital Library after the conference. Selected best papers will be awarded and also considered for a special issue of International Journal of Computational Science and Engineering (IJCSE) and International Journal of High Performance Computing and Networking (IJHPCN). *Workshop Proposals* ==================== We encourage researches to submit their workshop proposals (according to the guidelines available at http://www.icmc.usp.br/~cse08/submission.html) in any one of the areas listed in the Scope (below) to cse08@icmc.usp.br with the subject "CSE-08 WORKSHOP PROPOSAL". *Scope* ======= The Computational Science and Engineering area has earned prominence through advances in electronic and integrated technologies beginning in the 1940s. Current times are very exciting and the years to come will witness a proliferation in the use of advanced computing systems. The scientific and engineering application domains have a key role in shaping future research and development activities in academia and industry, especially when the solution of large and complex problems must cope with tight timing schedules. This Conference is to bring together computer scientists, applied mathematicians, engineers in different disciplines and researchers to present, discuss and exchange ideas, results and experiences in the area of advanced computing for problems in science and engineering applications and inter-disciplinary applications. Among the main topics of interest (but not limited to) are: - Intelligent, Bioinspired and Autonomic Computing - Distributed and Parallel Computing - Distributed Database and Data Mining - Grid, P2P, Web Services and Internet Computing - Mobile Computing and Wireless Communications - HPC Applications - Scientific and Engineering Computing - Embedded and Ubiquitous Computing - Advanced Networking and Applications - Security, Privacy and Trust - Education in Computational Scientific and Engineering - Applications to the following areas, but not limited to: - computational fluid dynamics and mechanics - material sciences - space, weather, climate systems and global changes - computational environment and energy systems - computational ocean and earth sciences - combustion system simulation - computational chemistry - computational physics - bioinformatics and computational biology - medical applications - transportation systems simulations - combinatorial and global optimization problems - structural engineering - computational electro-magnetic - computer graphics and multimedia - semiconductor technology, and electronic circuits and system design - dynamic systems - computational finance - data mining - signal and image processing, etc *Programm Committee* ==================== General Co-Chairs Liria Matsumoto Sato, EP - University of Sao Paulo, Brazil Rodrigo Fernandes de Mello, ICMC - University of Sao Paulo, Brazil Kuan-Ching Li, Providence University, Taiwan Steering Committee Steering Committee Co-Chairs Laurence Tianruo Yang, St. Francis Xavier University, Canada Siang Wun Song, IME - University of Sao Paulo, Brazil Steering Committee Members Jack Dongarra, University of Tennessee, USA Cho-Li Wang, The University of Hong Kong, China Philippe Navaux, Federal University of Rio Grande do Sul, Brazil Alvaro L.G.A. Coutinho, Federal University of Rio de Janeiro, Brazil Jiannong Cao, Hong Kong Polytechnic University, China Rodrigo Fernandes de Mello, ICMC - University of Sao Paulo, Brazil Kuan-Ching Li, Providence University, Taiwan Program Co-Chairs Jose Alberto Cuminato, ICMC - University of Sao Paulo, Brazil Mark Baker, University of Reading, UK Program Vice-Chairs Intelligent, Bioinspired and Autonomic Computing Andre Carlos Ponce de Leon Ferreira de Carvalho, ICMC - University of Sao Paulo, Brazil Distributed and Parallel Computing Marcin Paprzycki, Systems Research Institute Polish Academy of Science, Poland Distributed Database and Data Mining Sunil Prabhakar, Purdue University, USA Grid, P2P, Web Services and Internet Computing Ching-Hsien Hsu, Chung-Hua University, Taiwan Mobile Computing and Wireless Communications Alvin Chan, The Hong Kong Polytechnic University, Hong Kong HPC Applications Daniel Katz, Louisiana State University, USA Scientific and Engineering Computing Osni Marques, Lawrence Berkeley National Laboratory, USA Embedded and Ubiquitous Computing Meikang Qiu, University of New Orleans, USA Advanced Networking and Applications Mario Dantas, Federal University of Santa Catarina, Brazil Security, Privacy and Trust Adriano Mauro Cansian, Paulista State University, Brazil Workshop Chairs Francisco Isidro Massetto, EP - University of Sao Paulo, Brazil Yiming Li, National Chiao Tung University, Taiwan Nectarios Koziris, National Technical University of Athens, Greece Local Arrangements Chairs Francisco Isidro Massetto, EP - University of Sao Paulo, Brazil Maio Donato Marino, EP - University of Sao Paulo, Brazil Evgueni Dodonov, ICMC - University of Sao Paulo, Brazil Jose Augusto Andrade Filho, ICMC - University of Sao Paulo, Brazil Marcelo Keese Albertini, ICMC - University of Sao Paulo, Brazil Ricardo Bertagna, ICMC - University of Sao Paulo, Brazil Publication Chair Luciano Jose Senger, State University of Ponta Grossa, Brazil Panel/Sponsorship Chairs Edson dos Santos Moreira, ICMC - University of Sao Paulo, Brazil Luis Carlos Trevelin, Federal University of Sao Carlos, Brazil Leandro Franco de Souza, ICMC - University of Sao Paulo, Brazil Web Chair Claudia Alves de Souza Mello, St. Francis Xavier University, Canada *About the Conference* ====================== The CSE (International Conference on Computational Science and Engineering) conference previously was held mainly as the International Workshop on High Performance Scientific and Engineering Computing for tenth editions, mostly in conjunction with International Conference on Parallel Processing (ICPP), as COATA-98 (Orlando, USA, July, 1998), HPSEC-99 (Fukushima, Japan, September 1999), HPSEC-00 (Toronto, Canada, August, 2000), HPSEC-01 (Valencia, Spain, September, 2001), HPSEC-02 (Vancouver, Canada, August, 2002), HPSEC-03 (Kaohsing, Taiwan, October, 2003), HPSEC-04 (Montreal, Canada, August, 2004), HPCSE-04 with WCC-04 (Toulouse, France, August, 2004), HPSEC-05 (Oslo, Norway, June, 2005), and HPSEC-06 (Columbus, USA, August, 2006). After many successful editions, this conference will be organized independently starting in 2008, in Sao Paulo, Brazil. This Conference is sponsored by IEEE TCSC Technical Committee on Scalable Computing and IEEE Computer Society. *About Sao Paulo, Brazil* ========================= Sao Paulo, the 19a richest city of the world, is officially inserted in a larger metropolitan region which holds 39 towns in total, and a population of more than 19 million inhabitants (2005). It is one of the biggest financial centers of Brazil and the world. Its economy is going through a deep transformation. Once a city with a strong industrial character, Sao Paulo's economy has become increasingly based on the tertiary sector, focusing on services and businesses for the country. Sao Paulo is located on a plateau, part of the vast region known as the Brazilian Highlands, with an average elevation of around 800 metres (2,625 ft) above sea level - though at a distance of only about 70 kilometers (43 mi) from the Atlantic Ocean. This distance is covered by two highways, the Anchieta and the Imigrantes, that roll down the range, leading to the portuary city of Santos and the beach resort of Guaruja. Rolling terrain prevails within the urbanized areas of Sao Paulo but in the North of the city - where the Serra da Cantareira Range boasts higher elevations and a sizable remnant of the Atlantic Rain Forest. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 12 17:56:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IriCJ-0001wn-M5; Mon, 12 Nov 2007 17:56:03 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IriCI-0001wg-EO for xcon-confirm+ok@megatron.ietf.org; Mon, 12 Nov 2007 17:56:02 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IriCI-0001wW-4N for xcon@ietf.org; Mon, 12 Nov 2007 17:56:02 -0500 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IriCH-0007sg-Nc for xcon@ietf.org; Mon, 12 Nov 2007 17:56:01 -0500 Received: from orthrus.local (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id lACMu0sG091833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2007 16:56:01 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <4738DA0E.4010701@nostrum.com> Date: Mon, 12 Nov 2007 16:56:14 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: XCON-IETF Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.91.2/4757/Mon Nov 12 11:20:27 2007 on shaman.nostrum.com X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: alan Johnston Subject: [XCON] Call for Consensus: Event Package Document X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org [as chair] As I mentioned two weeks ago, the chairs are now calling for consensus regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02 as the basis for our charter item to update the conference event package. The current document is available at: http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.txt Please register agreement or disagreement with adopting the document as a working group item by responding to this email. If you have no opinion on the topic, please respond to this email with an active abstention so that the chairs can register the total number of people who have considered the motion, even those who choose not to voice an opinion. Thanks. /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Nov 13 04:53:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrsSZ-00059o-0L; Tue, 13 Nov 2007 04:53:31 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IrsSX-00059e-RO for xcon-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 04:53:29 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrsSX-00059U-HI for xcon@ietf.org; Tue, 13 Nov 2007 04:53:29 -0500 Received: from cluster-b.mailcontrol.com ([217.68.146.190]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrsSX-0003fN-2J for xcon@ietf.org; Tue, 13 Nov 2007 04:53:29 -0500 Received: from rly03b.srv.mailcontrol.com (localhost.localdomain [127.0.0.1]) by rly03b.srv.mailcontrol.com (MailControl) with ESMTP id lAD9rEln024468 for ; Tue, 13 Nov 2007 09:53:14 GMT Received: from submission.mailcontrol.com (submission.mailcontrol.com [86.111.216.190]) by rly03b.srv.mailcontrol.com (MailControl) id lAD9qhQa023417 for xcon@ietf.org; Tue, 13 Nov 2007 09:52:43 GMT Received: from GBNEWP0758M.eu.ubiquity.net ([62.172.205.164]) by rly03b-eth0.srv.mailcontrol.com (envelope-sender cboulton@avaya.com) (MIMEDefang) with ESMTP id lAD9mRXX010489; Tue, 13 Nov 2007 09:52:42 +0000 (GMT) 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" Subject: RE: [XCON] Call for Consensus: Event Package Document Date: Tue, 13 Nov 2007 09:52:11 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: Acglf159NC3SR08KRJiENJKVXpEBDwAW3Lbw References: <4738DA0E.4010701@nostrum.com> From: "Chris Boulton" To: "Adam Roach" , "XCON-IETF" X-Scanned-By: MailControl A-08-00-00 (www.mailcontrol.com) on 10.66.1.113 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: alan Johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Agreed. Chris. -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com]=20 Sent: 12 November 2007 22:56 To: XCON-IETF Cc: alan Johnston Subject: [XCON] Call for Consensus: Event Package Document [as chair] As I mentioned two weeks ago, the chairs are now calling for consensus=20 regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02=20 as the basis for our charter item to update the conference event=20 package. The current document is available at: =20 http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.tx t Please register agreement or disagreement with adopting the document as=20 a working group item by responding to this email. If you have no opinion on the topic, please respond to this email with an active abstention so=20 that the chairs can register the total number of people who have=20 considered the motion, even those who choose not to voice an opinion. Thanks. /a _______________________________________________ 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 Tue Nov 13 04:55:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrsUb-0007Wj-MR; Tue, 13 Nov 2007 04:55:37 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IrsUa-0007VY-51 for xcon-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 04:55:36 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrsUZ-0007Us-Nv for xcon@ietf.org; Tue, 13 Nov 2007 04:55:35 -0500 Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrsUZ-0003jh-Bb for xcon@ietf.org; Tue, 13 Nov 2007 04:55:35 -0500 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 97FAA20065; Tue, 13 Nov 2007 10:55:34 +0100 (CET) X-AuditID: c1b4fb3c-b0e80bb0000007e1-2e-47397496f3bc Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8AF882072D; Tue, 13 Nov 2007 10:55:34 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 10:55:34 +0100 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] Call for Consensus: Event Package Document Date: Tue, 13 Nov 2007 10:52:19 +0100 Message-ID: In-Reply-To: <4738DA0E.4010701@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: AcglfsZgjUinPUTkTTCnJEnUNv/4ygAXBDnw References: <4738DA0E.4010701@nostrum.com> From: "Oscar Novo" To: "Adam Roach" , "XCON-IETF" X-OriginalArrivalTime: 13 Nov 2007 09:55:34.0421 (UTC) FILETIME=[5598EC50:01C825DB] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: alan Johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Why don't we decide that in the Vancouver meeting? I think decide it by e-mail it's not the right way to do things. At least, it won't be very 'anonymous' I would say.=20 Oscar=20 -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com]=20 Sent: 13. marraskuuta 2007 0:56 To: XCON-IETF Cc: alan Johnston Subject: [XCON] Call for Consensus: Event Package Document [as chair] As I mentioned two weeks ago, the chairs are now calling for consensus regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02 as the basis for our charter item to update the conference event package. The current document is available at: =20 http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.tx t Please register agreement or disagreement with adopting the document as a working group item by responding to this email. If you have no opinion on the topic, please respond to this email with an active abstention so that the chairs can register the total number of people who have considered the motion, even those who choose not to voice an opinion. Thanks. /a _______________________________________________ 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 Tue Nov 13 09:17:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrwZz-00010d-0H; Tue, 13 Nov 2007 09:17:27 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IrwZx-0000wP-OM for xcon-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 09:17:25 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrwZx-0000wH-DW for xcon@ietf.org; Tue, 13 Nov 2007 09:17:25 -0500 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IrwZw-0005Gp-Qd for xcon@ietf.org; Tue, 13 Nov 2007 09:17:25 -0500 Received: from localhost.localdomain (ppp-70-242-127-246.dsl.rcsntx.swbell.net [70.242.127.246]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id lADEHMAa039057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Nov 2007 08:17:22 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <4739B1EC.5020005@nostrum.com> Date: Tue, 13 Nov 2007 08:17:16 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: Oscar Novo Subject: Re: [XCON] Call for Consensus: Event Package Document References: <4738DA0E.4010701@nostrum.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 70.242.127.246 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.91.2/4763/Tue Nov 13 06:00:49 2007 on shaman.nostrum.com X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: alan Johnston , XCON-IETF X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org [as chair] The stated plan of action at the Chicago meeting was to call for consensus on the event package document _prior_ to the Vancouver meeting. This was an important part of the plan that the chairs worked out with the area director prior to the meeting as part of a negotiation to allow the working group to continue. Anonymity has never been important to consensus (quite the opposite, in fact -- the ability to anonymously object to a course of action without being identified encourages obstructionism). Many working groups outside of the Transport/RAI areas call for consensus at face-to-face meetings with a show of hands, which is far from anonymous. /a Oscar Novo wrote: > Why don't we decide that in the Vancouver meeting? I think decide it by > e-mail it's not the right way to do things. At least, it won't be very > 'anonymous' I would say. > > Oscar > > -----Original Message----- > From: Adam Roach [mailto:adam@nostrum.com] > Sent: 13. marraskuuta 2007 0:56 > To: XCON-IETF > Cc: alan Johnston > Subject: [XCON] Call for Consensus: Event Package Document > > [as chair] > > As I mentioned two weeks ago, the chairs are now calling for consensus > regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02 > as the basis for our charter item to update the conference event > package. The current document is available at: > > > http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.tx > t > > > Please register agreement or disagreement with adopting the document as > a working group item by responding to this email. If you have no opinion > on the topic, please respond to this email with an active abstention so > that the chairs can register the total number of people who have > considered the motion, even those who choose not to voice an opinion. > > Thanks. > > /a > > > _______________________________________________ > 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 Tue Nov 13 09:20:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irwcn-0003Ws-73; Tue, 13 Nov 2007 09:20:21 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Irwcj-0003WA-QE for xcon-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 09:20:17 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Irwcj-0003Vv-Fl for xcon@ietf.org; Tue, 13 Nov 2007 09:20:17 -0500 Received: from fw.polycom.co.il ([212.179.41.2] helo=isrexch01.israel.polycom.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Irwcj-0005Ne-1v for xcon@ietf.org; Tue, 13 Nov 2007 09:20:17 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [XCON] Call for Consensus: Event Package Document Date: Tue, 13 Nov 2007 16:22:02 +0200 Message-ID: <144ED8561CE90C41A3E5908EDECE315C0513258F@IsrExch01.israel.polycom.com> In-Reply-To: <4738DA0E.4010701@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: Acglf3dxWWQ8TbgZQ7aGw8RtA5xSDQAgP+9w From: "Even, Roni" To: "Adam Roach" , "XCON-IETF" X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: alan Johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Agree, Roni Even > -----Original Message----- > From: Adam Roach [mailto:adam@nostrum.com] > Sent: Tuesday, November 13, 2007 12:56 AM > To: XCON-IETF > Cc: alan Johnston > Subject: [XCON] Call for Consensus: Event Package Document >=20 > [as chair] >=20 > As I mentioned two weeks ago, the chairs are now calling for consensus > regarding whether to adopt = draft-srinivasan-xcon-eventpkg-extensions-02 > as the basis for our charter item to update the conference event > package. The current document is available at: >=20 >=20 > = http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.txt= >=20 >=20 > Please register agreement or disagreement with adopting the document = as > a working group item by responding to this email. If you have no = opinion > on the topic, please respond to this email with an active abstention = so > that the chairs can register the total number of people who have > considered the motion, even those who choose not to voice an opinion. >=20 > Thanks. >=20 > /a >=20 >=20 > _______________________________________________ > 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 Tue Nov 13 14:12:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is1BT-0000Bb-DU; Tue, 13 Nov 2007 14:12:27 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Is1BS-0008W7-0Z for xcon-confirm+ok@megatron.ietf.org; Tue, 13 Nov 2007 14:12:26 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Is1BR-0008TT-CT for xcon@ietf.org; Tue, 13 Nov 2007 14:12:25 -0500 Received: from zrtps0kn.nortel.com ([47.140.192.55]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Is1BR-00033T-1h for xcon@ietf.org; Tue, 13 Nov 2007 14:12:25 -0500 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lADJC8q26920; Tue, 13 Nov 2007 19:12:08 GMT 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] Call for Consensus: Event Package Document Date: Tue, 13 Nov 2007 13:11:06 -0600 Message-ID: In-Reply-To: <4738DA0E.4010701@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: AcglfzxNA2hupYfwQHivnxdPVtHdEAApv2CQ References: <4738DA0E.4010701@nostrum.com> From: "Mary Barnes" To: "Adam Roach" , "XCON-IETF" X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: alan Johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org I've read the document and agree it's a good starting point for a WG document. Mary.=20 -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com]=20 Sent: Monday, November 12, 2007 4:56 PM To: XCON-IETF Cc: alan Johnston Subject: [XCON] Call for Consensus: Event Package Document [as chair] As I mentioned two weeks ago, the chairs are now calling for consensus regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02 as the basis for our charter item to update the conference event package. The current document is available at: =20 http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.tx t Please register agreement or disagreement with adopting the document as a working group item by responding to this email. If you have no opinion on the topic, please respond to this email with an active abstention so that the chairs can register the total number of people who have considered the motion, even those who choose not to voice an opinion. Thanks. /a _______________________________________________ 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 Nov 14 07:57:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsHoR-00007J-G2; Wed, 14 Nov 2007 07:57:47 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IsHoO-000050-K5 for xcon-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 07:57:45 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsHoO-0008WI-75 for xcon@ietf.org; Wed, 14 Nov 2007 07:57:44 -0500 Received: from oslproxyp1.tandberg.com ([194.0.215.2]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsHoN-0000xT-Kd for xcon@ietf.org; Wed, 14 Nov 2007 07:57:44 -0500 Received: from OSLEXCP11.eu.tandberg.int (oslexcp11.eu.tandberg.int [10.47.136.43]) by oslproxyp1.tandberg.com (8.13.1/8.13.1) with ESMTP id lAECvf4x008859; Wed, 14 Nov 2007 13:57:41 +0100 Received: from oslexcp1.eu.tandberg.int ([10.47.136.29]) by OSLEXCP11.eu.tandberg.int with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Nov 2007 13:57:41 +0100 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] Call for Consensus: Event Package Document Date: Wed, 14 Nov 2007 13:57:41 +0100 Message-ID: <9F6ACAE02B6DD040A1E259977622CFDBBE5569@oslexcp1.eu.tandberg.int> In-Reply-To: <4738DA0E.4010701@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: Acglf0Kb/kUMgQSpTkaouEpqGxH8awBPi56A From: "Geir Arne Sandbakken" To: "Adam Roach" , "XCON-IETF" X-OriginalArrivalTime: 14 Nov 2007 12:57:41.0600 (UTC) FILETIME=[F11DDE00:01C826BD] X-Scanned-By: MIMEDefang 2.62 on 194.0.215.2 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: alan Johnston X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org I've read the document, and agree to adopt. Geir Arne > -----Original Message----- > From: Adam Roach [mailto:adam@nostrum.com] > Sent: 12 November 2007 23:56 > To: XCON-IETF > Cc: alan Johnston > Subject: [XCON] Call for Consensus: Event Package Document >=20 > [as chair] >=20 > As I mentioned two weeks ago, the chairs are now calling for consensus > regarding whether to adopt draft-srinivasan-xcon-eventpkg-extensions-02 > as the basis for our charter item to update the conference event > package. The current document is available at: >=20 >=20 > http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.tx t >=20 >=20 > Please register agreement or disagreement with adopting the document as > a working group item by responding to this email. If you have no opinion > on the topic, please respond to this email with an active abstention so > that the chairs can register the total number of people who have > considered the motion, even those who choose not to voice an opinion. >=20 > Thanks. >=20 > /a >=20 >=20 > _______________________________________________ > 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 Nov 14 08:44:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsIY2-0003nd-Vs; Wed, 14 Nov 2007 08:44:54 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IsIY1-0003mi-TU for xcon-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 08:44:53 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsIY1-0003lN-Ff for xcon@ietf.org; Wed, 14 Nov 2007 08:44:53 -0500 Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsIY0-0003pI-OA for xcon@ietf.org; Wed, 14 Nov 2007 08:44:53 -0500 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 304F020622; Wed, 14 Nov 2007 14:44:52 +0100 (CET) X-AuditID: c1b4fb3c-b1681bb0000007e1-ea-473afbd4f741 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1AD7A20066; Wed, 14 Nov 2007 14:44:52 +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, 14 Nov 2007 14:44:51 +0100 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] Call for Consensus: Event Package Document Date: Wed, 14 Nov 2007 14:41:36 +0100 Message-ID: In-Reply-To: <4739B1EC.5020005@nostrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] Call for Consensus: Event Package Document Thread-Index: Acgl/3dF6tq5p3DIRdi4lYU10xsc1AAw6IIg References: <4738DA0E.4010701@nostrum.com> <4739B1EC.5020005@nostrum.com> From: "Oscar Novo" To: "Adam Roach" X-OriginalArrivalTime: 14 Nov 2007 13:44:51.0967 (UTC) FILETIME=[882598F0:01C826C4] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Cc: alan Johnston , XCON-IETF X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org That's fine for me. I've read the document and I agree to adopt it. Oscar =20 -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com]=20 Sent: 13. marraskuuta 2007 16:17 To: Oscar Novo Cc: XCON-IETF; alan Johnston Subject: Re: [XCON] Call for Consensus: Event Package Document [as chair] The stated plan of action at the Chicago meeting was to call for consensus on the event package document _prior_ to the Vancouver meeting. This was an important part of the plan that the chairs worked out with the area director prior to the meeting as part of a negotiation to allow the working group to continue. Anonymity has never been important to consensus (quite the opposite, in fact -- the ability to anonymously object to a course of action without being identified encourages obstructionism). Many working groups outside of the Transport/RAI areas call for consensus at face-to-face meetings with a show of hands, which is far from anonymous. /a Oscar Novo wrote: > Why don't we decide that in the Vancouver meeting? I think decide it=20 > by e-mail it's not the right way to do things. At least, it won't be=20 > very 'anonymous' I would say. > > Oscar > > -----Original Message----- > From: Adam Roach [mailto:adam@nostrum.com] > Sent: 13. marraskuuta 2007 0:56 > To: XCON-IETF > Cc: alan Johnston > Subject: [XCON] Call for Consensus: Event Package Document > > [as chair] > > As I mentioned two weeks ago, the chairs are now calling for consensus > regarding whether to adopt=20 > draft-srinivasan-xcon-eventpkg-extensions-02 > as the basis for our charter item to update the conference event=20 > package. The current document is available at: > > =20 > http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02. > tx > t > > > Please register agreement or disagreement with adopting the document=20 > as a working group item by responding to this email. If you have no=20 > opinion on the topic, please respond to this email with an active=20 > abstention so that the chairs can register the total number of people=20 > who have considered the motion, even those who choose not to voice an opinion. > > Thanks. > > /a > > > _______________________________________________ > 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 Wed Nov 14 10:24:43 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsK6d-00006S-39; Wed, 14 Nov 2007 10:24:43 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IsK6b-0008Ss-Sh for xcon-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 10:24:41 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsK6b-0008Rm-FU for xcon@ietf.org; Wed, 14 Nov 2007 10:24:41 -0500 Received: from zrtps0kn.nortel.com ([47.140.192.55]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IsK6a-00065N-EI for xcon@ietf.org; Wed, 14 Nov 2007 10:24:41 -0500 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lAEFKb005996; Wed, 14 Nov 2007 15:20:38 GMT 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] XCON Chatroom consensus Date: Wed, 14 Nov 2007 09:18:04 -0600 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [XCON] XCON Chatroom consensus Thread-Index: AcgNCOO9BlaO1nOkS26Stp16CxagAAAAmeBQA9S19IACnNZtwA== References: <470FCF4A.9050505@nostrum.com> From: "Mary Barnes" To: "Oscar Novo" , "Adam Roach" , "Spencer Dawkins" X-Spam-Score: 0.0 (/) X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1 Cc: xcon@ietf.org X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Oscar, I didn't see any other responses here, but I'm okay with the proposals you suggest below. Mary.=20 -----Original Message----- From: Oscar Novo [mailto:oscar.novo@ericsson.com]=20 Sent: Thursday, November 01, 2007 3:35 AM To: Barnes, Mary (RICH2:AR00); Adam Roach; Spencer Dawkins Cc: xcon@ietf.org Subject: RE: [XCON] XCON Chatroom consensus Hello, After the discussion of the new chatroom elements that should be include in the data model. Here it's some more comments about the topic. If the WG agree on that I'll add these elements in the next version of the data model. Comments as [ON]. Cheers, Oscar -----Original Message----- From: Mary Barnes [mailto:mary.barnes@nortel.com] Sent: 12. lokakuuta 2007 23:35 To: Adam Roach Cc: Oscar Novo; xcon@ietf.org Subject: RE: [XCON] XCON Chatroom consensus Adam, More responses inline below [MB2]. Mary. -----Original Message----- From: Adam Roach [mailto:adam@nostrum.com] Sent: Friday, October 12, 2007 2:47 PM To: Barnes, Mary (RICH2:AR00) Cc: Oscar Novo; xcon@ietf.org Subject: Re: [XCON] XCON Chatroom consensus On 10/12/07 1:49 PM, Mary Barnes wrote: > -----Original Message----- > From: Oscar Novo [mailto:oscar.novo@ericsson.com] > > Section 2.4.3 (Password-Protected Chatrooms) > > "The current framework described in XCON uses user authentication for=20 > admissions control. However, some deployed systems instead use a=20 > single, chatroom-wide password that can be used to enter a chatroom. > This allows users to disseminate the password as a kind of invitation=20 > token without explicitly provisioning the allowed users into the=20 > chatroom system." > > If we decide to add this feature, it will require a new field=20 > ("conference password") in the XCON data model under element. > > [MB] But, the XCON model still requires that we have each user in the=20 > <"allowed-users-list"> and there is already a field for whether or not > PIN authorization (e.g., "IVR") is required. This chatroom-wide=20 > password is specific to the authentication and separate from the issue > as to whether or not you provision allowed users in the chatroom=20 > system (i.e., from the end user perspective, they only need the PW,=20 > the conferencing system functionality still needs the allocate=20 > identifiers and create the allowed users). [/MB] > =20 I was under the impression that one could create conferences that allowed general membership, without needing to add people to the . (If not, I think we'll run into problems). [MB2] You can have conferences with general membership, BUT the conferencing system associates an identifier with each user. The framework does mention (section 5.3) that while the user identifier is NOT required to join a conference, it is necessary to manipulate a conference. Non-XCON aware users (for lack of a better term) aren't expected to be aware of the user identifier - it's a system thing. But, it might also be necessary to include in notifications to XCON-aware clients as to conference membership, etc. I almost think the element should just be renamed as I think the other attributes, such as user-admission-policy, introduce the "allowed" aspect - i.e., that list is all users associated that can potentially be associated with the conference instance. [/MB2] The PIN concept is pretty much what we're looking for here, but we need a mechanism to extend it to other protocols. My reading right now is that the PIN in the data model is good only for PSTN users. [MB2] It's my understanding that a PIN concept could apply to any user type. But, maybe I've misunderstood the data model. Actually, there may be an inconsistency in the data model. It does say in section 4.1.2. that a URI of PSTN-ISDN has a "PIN code" attribute, however, there is a "join-handling" value of "IVR" in 4.5. which specifies that the user must provide a PIN and I don't think that is restricted to the PSTN-ISDN user. So, I wonder if that "PIN code" attribute is really necessary in the PSTN-type definition? [/MB2] [ON] In the version 06 of the data model we have modified the 'IVR' value of the element for an 'authenticate' value. The 'authenticate' value is not restricted to the PSTN-ISDN users as the 'IVR' value. As well, the element does not have the element anymore under . These changes have been done to validate the consensus achieve in the last ietf meeting. =20 In the next version of the draft we can add a new attribute 'conference password' in the element to complete the requirements of the discussion above.=20 [/ON] > 2.4.4. (Private and Semi-Private Chatrooms) > > "Currently, the XCON model allows users to be marked individually as=20 > anonymous or not via their corresponding tag. Some > systems, however, include a chatroom-wide setting that can be used to=20 > specify that all users in a chatroom are either completely anonymous=20 > (private), or anonymous to all users with equal or lesser permissions=20 > (semi-private)." > > If we decide to add this feature, it will require to modify the=20 > element with the values "private" and "semi-private" > instead of Boolean. > > [MB] I agree with Oscar's proposal. [/MB] > =20 So do I. [ON] We'll do that [/ON] > 2.4.5. (Banned Users) > > In addition to removing specific users from a conference, most=20 > deployed systems permit the specification of "banned" users. Such=20 > banned users are prevented from re-joining the chatroom until they=20 > have been un-banned. Currently it's needed additional work in the case > where all users are authenticated" > > If we decide to add this feature, a is needed to=20 > reject any users in the conference. > > [MB] I agree with Oscar's reponse on this one. [/MB] > =20 So do I. [ON] We'll do that [/ON] > 2.4.10.3. (Indication of Chatroom Log Archive Location) > > "Some systems include the ability for clients to access the on-line=20 > archive of a chatroom log from within the context of their chatroom=20 > client. (e.g., a menu selection or button that brings up a the=20 > chatroom log)." > > This feature can be defined using the element defined=20 > in RFC4575. Not need to create new elements. > =20 Ah, yes. I overlooked that. A service-uri pointing to a web-page with a purpose of "recording" would certainly serve the purpose quite nicely.=20 I'll make a note of this. Thanks for pointing it out. > 2.4.12. (Detailed User Registration) > > "Some chatroom systems allow -- and some require -- registration of=20 > detailed information about a user before they are allowed to join a=20 > chatroom. Currently, the XCON data model does not include a way to=20 > store persistent information (name, nickname, email address, etc.)=20 > about users who are not actively part of an ongoing chatroom session." > > The three solutions propose in the draft are: > > (1) Adding elements to the / element in=20 > the XCON data model that store information about users who are=20 > associated with the chatroom, but not presently participating in it; > > [MB] This is already "allowed" in the framework (i.e., an allowed-user > shouldn't necessarily have to be a participant), particularly in that=20 > a reservation can be setup with a list of allowed-users without them=20 > having yet joined the conference and per the 2nd sentence in section 5.3 > of the framework. My understanding was that it would then be up to a > conferencing system as to how it manages the persistence of the data - > if not then maybe we need something more in the framework, as well=20 > (e.g., a statement like "As well as users appearing in specific=20 > conference objects, a conferencing may maintain persistent information > about users." in section 5.3, possibly in the are where it is=20 > discussed that conference user identifiers can be distributed out-of-band,etc. > [/MB] > =20 I think you misread what I was proposing. I was pointing out that the is where we keep information about users associated with the conference but not currently participating in it. I said that we need to add elements to these entries that contain ancillary information, like name, nickname, email, etc. [MB2] Okay, I see your point and agree that we would need to add that additional info. [MB2] [ON] We'll add the solution number one to the next version of the data model [/ON] > 2.4.16. (Designation of Chatroom Language) > > "The XCON data model does not currently provide a mechanism for=20 > indicating the predominant language that is expected to be employed=20 > within a conference." > > The intention of the data model was to define this feature using the=20 > attribute 'lang' specify in the element. > We'll rewrote the text to make this idea more clear in the next version. > > [MB] I agree with Oscar, as I thought that was already in the data=20 > model. [/MB] > =20 Umm... I was under the impression that the language tag here indicated what language was being used in the , not in the conference itself. I guess one can take it as implied that the conference will be in the same language as the description, but that doesn't quite feel right to me. I would *personally* prefer it be more explicit than that in the data model. If consensus is that we want to necessarily use the language indicator in the to *also* indicate the language used inside the conference, then such a binding does, at least, need to be made explicit. [MB2] Okay, I see your point here too and agree that we likely need both. [/MB2] [ON] We'll add a new element under to differentiate both cases. [/ON] /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Wed Nov 14 22:00:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsUxc-00072y-Pb; Wed, 14 Nov 2007 22:00:08 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IsUxb-00072Z-Hi for xcon-confirm+ok@megatron.ietf.org; Wed, 14 Nov 2007 22:00:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IsUxb-00072D-85 for xcon@ietf.org; Wed, 14 Nov 2007 22:00:07 -0500 Received: from nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net ([2001:470:1f03:267::2] helo=nostrum.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IsUxa-0001n3-Mz for xcon@ietf.org; Wed, 14 Nov 2007 22:00:07 -0500 Received: from localhost.localdomain (ppp-70-242-127-246.dsl.rcsntx.swbell.net [70.242.127.246]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id lAF304tc017225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Nov 2007 21:00:05 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <473BB62F.7010704@nostrum.com> Date: Wed, 14 Nov 2007 20:59:59 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: XCON-IETF Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 70.242.127.246 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.91.2/4796/Wed Nov 14 18:09:59 2007 on shaman.nostrum.com X-Virus-Status: Clean X-Spam-Score: -1.4 (-) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Cc: Alan Johnston Subject: [XCON] Agenda Requests X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Anyone wanting time on the XCON agenda in Vancouver should contact me and Alan no later than Monday. Thanks. /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 19 08:40:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu6r7-0002fQ-3J; Mon, 19 Nov 2007 08:40:05 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Iu6r6-0002fD-8M for xcon-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 08:40:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu6r5-0002f0-U9; Mon, 19 Nov 2007 08:40:03 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iu6r4-0000t0-7y; Mon, 19 Nov 2007 08:40:03 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 29B51327BC; Mon, 19 Nov 2007 13:40:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Iu6r4-0004eI-2S; Mon, 19 Nov 2007 08:40:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 19 Nov 2007 08:40:02 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: xcon@ietf.org Subject: [XCON] I-D Action:draft-ietf-xcon-common-data-model-07.txt X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , 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 : Conference Information Data Model for Centralized Conferencing (XCON) Author(s) : O. Novo, et al. Filename : draft-ietf-xcon-common-data-model-07.txt Pages : 69 Date : 2007-11-19 This document defines an Extensible Markup Language (XML)-based conference information data model for centralized conferencing (XCON). A conference information data model is designed to convey information about the conference and about participation in the conference. The conference information data model defined in this document constitutes an extension of the data format specified in the Session Initiation Protocol (SIP) Event Package for Conference State. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-07.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-common-data-model-07.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-common-data-model-07.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: <2007-11-19083223.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-xcon-common-data-model-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-xcon-common-data-model-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-11-19083223.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 Nov 19 09:27:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu7aj-0002HM-PS; Mon, 19 Nov 2007 09:27:13 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Iu7aj-0002HA-EW for xcon-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 09:27:13 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu7aj-0002Gh-1f; Mon, 19 Nov 2007 09:27:13 -0500 Received: from mailgw3.ericsson.se ([193.180.251.60]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iu7ai-0003dD-7o; Mon, 19 Nov 2007 09:27:12 -0500 Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id A0BAB2083C; Mon, 19 Nov 2007 15:27:11 +0100 (CET) X-AuditID: c1b4fb3c-af619bb000002c9b-af-47419d3f57fb Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 80868203F3; Mon, 19 Nov 2007 15:27:11 +0100 (CET) Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Nov 2007 15:27:11 +0100 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 Date: Mon, 19 Nov 2007 15:23:52 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version of the Data Model Thread-Index: AcgqssJVT9HMjjdLTbyxboOLcPMR5AAAPfaA References: From: "Oscar Novo" To: , X-OriginalArrivalTime: 19 Nov 2007 14:27:11.0440 (UTC) FILETIME=[45DB2D00:01C82AB8] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Cc: xcon@ietf.org Subject: [XCON] New version of the Data Model X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org Hi folks, First of all, I want to thanks all the reviewers to review (again) the data model and to all your feedback. Thanks to Ben, Srivatsa, Miguel, Mary, and Avshalom. You have done a good job! In this new version we try mainly to fix the problems the reviews have found in the data model, as well as, we have added the 'chatroom' comments (http://www1.ietf.org/mail-archive/web/xcon/current/msg02062.html) proposed in the mailing list. To sum up: - Fixed the IANA considerations (Ben's feedback) - Fixed the "XML Schema Extensibility" text (Srivatsa feedback) - Removed totally the roles the Schema (Mary and Miguel's feedback) - Created a new subsection in the XCON URI section to define this URI (Miguel's feedback) - Defined the element with the limits (-127...+127) using the 'minInclusive', 'maxInclusive' from RelaxNG. (Miguel's feedback) - Fixed some remain nits. (all reviewers feedback) - Addition of a new element 'conference password' in the (Chatroom Consensus) - Modification of the element with the values "private" and "semi-private" instead of Boolean. (Chatroom Consensus) - Addition of a element (Chatroom Consensus) - Addition of element and the child element under (Chatroom Consensus) - Addition of the element under (Chatroom Consensus) Miguel, some of your comments from your last (re)review I have already answered to them some time ago. Check the next link: =20 http://www1.ietf.org/mail-archive/web/xcon/current/msg02046.html Please, Note that, even though, the roles are completely removed from the data model, still some reviewers think it's important to keep some role information in the data model. We could try to discuss this issue in the face to face meeting in few weeks.=20 You can fetch the last version of the draft in: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-07 .txt As you know, your feedback is welcome! Cheers, Oscar -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: 19. marraskuuta 2007 15:40 To: i-d-announce@ietf.org Cc: xcon@ietf.org Subject: [XCON] I-D Action:draft-ietf-xcon-common-data-model-07.txt=20 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 : Conference Information Data Model for Centralized Conferencing (XCON) Author(s) : O. Novo, et al. Filename : draft-ietf-xcon-common-data-model-07.txt Pages : 69 Date : 2007-11-19 This document defines an Extensible Markup Language (XML)-based conference information data model for centralized conferencing (XCON). A conference information data model is designed to convey information about the conference and about participation in the conference. The conference information data model defined in this document constitutes an extension of the data format specified in the Session Initiation Protocol (SIP) Event Package for Conference State. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-07 .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-common-data-model-07.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-common-data-model-07.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. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 19 10:31:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu8ah-0004Jn-Q5; Mon, 19 Nov 2007 10:31:15 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1Iu8ag-0004Jf-Om for xcon-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 10:31:14 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iu8ag-0004IC-DS for xcon@ietf.org; Mon, 19 Nov 2007 10:31:14 -0500 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iu8ag-0008OO-51 for xcon@ietf.org; Mon, 19 Nov 2007 10:31:14 -0500 Received: from localhost.localdomain (ppp-70-242-127-246.dsl.rcsntx.swbell.net [70.242.127.246]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id lAJFVCqO036238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Nov 2007 09:31:13 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <4741AC3B.20703@nostrum.com> Date: Mon, 19 Nov 2007 09:31:07 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.0 (X11/20070326) MIME-Version: 1.0 To: XCON-IETF References: <4738DA0E.4010701@nostrum.com> In-Reply-To: <4738DA0E.4010701@nostrum.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 70.242.127.246 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.91.2/4841/Sun Nov 18 22:25:36 2007 on shaman.nostrum.com X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: Alan Johnston Subject: [XCON] Consensus: Event Package Document X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org [as chair] Based on feedback collected on this mailing list, I am declaring the following document a working group item; it will form the basis for meeting our milestone to produce an updated event package for conferencing: http://tools.ietf.org/id/draft-srinivasan-xcon-eventpkg-extensions-02.txt Thanks. /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Nov 19 12:41:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuAcA-0004n6-Pf; Mon, 19 Nov 2007 12:40:54 -0500 Received: from xcon by megatron.ietf.org with local (Exim 4.43) id 1IuAcA-0004mx-AD for xcon-confirm+ok@megatron.ietf.org; Mon, 19 Nov 2007 12:40:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuAc9-0004ml-Et for xcon@ietf.org; Mon, 19 Nov 2007 12:40:53 -0500 Received: from shaman.nostrum.com ([72.232.15.10] helo=nostrum.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IuAc4-0006ER-Fm for xcon@ietf.org; Mon, 19 Nov 2007 12:40:53 -0500 Received: from orthrus.local (ppp-70-242-127-246.dsl.rcsntx.swbell.net [70.242.127.246]) (authenticated bits=0) by nostrum.com (8.14.1/8.14.1) with ESMTP id lAJHdTFm044579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Nov 2007 11:39:30 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <4741CA4F.80901@nostrum.com> Date: Mon, 19 Nov 2007 11:39:27 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: XCON-IETF Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 70.242.127.246 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.91.2/4843/Mon Nov 19 10:02:15 2007 on shaman.nostrum.com X-Virus-Status: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: Alan Johnston Subject: [XCON] Vancouver Agenda X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xcon-bounces@ietf.org [as chair] Based on requests and active work items, we have put together a preliminary agenda for the XCON meeting in Vancouver. http://www3.ietf.org/proceedings/07dec/agenda/xcon.txt Note that the -07 version of the data model isn't appearing in the rsync'ed version of the i-d repository at the moment, but can be found in the online repository: http://www.ietf.org/internet-drafts/draft-ietf-xcon-common-data-model-07.txt Direct any comments to Alan and me. /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon