From xcon-bounces@ietf.org Mon Oct 03 15:25:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMVvr-0007Ly-2K; Mon, 03 Oct 2005 15:25:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMVvo-0007La-S5 for xcon@megatron.ietf.org; Mon, 03 Oct 2005 15:25:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26824 for ; Mon, 3 Oct 2005 15:24:57 -0400 (EDT) Received: from maillnx-us112.fmr.com ([192.223.198.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMW4I-0001Tg-LS for xcon@ietf.org; Mon, 03 Oct 2005 15:33:48 -0400 Received: from MSGMMKSM02WIN.DMN1.FMR.COM (msgmmksm02win.dmn1.fmr.com [10.33.139.33]) by maillnx-us112.fmr.com (Switch-3.1.2/Switch-3.1.0) with SMTP id j93JOcWA016922 for ; Mon, 3 Oct 2005 15:24:39 -0400 Received: from MSGMMKIV01WIN.DMN1.FMR.COM (10.33.148.30) by MSGMMKSM02WIN.DMN1.FMR.COM (Sigaba Gateway v3.83) with ESMTP id 48015408; Mon, 03 Oct 2005 15:24:38 -0400 Received: from MSGMROIM01WIN.DMN1.FMR.COM ([172.26.2.194]) by MSGMMKIV01WIN.DMN1.FMR.COM with SMTP_server; Mon, 03 Oct 2005 15:24:38 -0400 Received: from msgmroclm2win.fmr.com ([10.37.181.20]) by MSGMROIM01WIN.DMN1.FMR.COM with Microsoft SMTPSVC(5.0.2195.6713); Mon, 3 Oct 2005 15:24:38 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [XCON] Draft defining a Common Data Model for XCON Date: Mon, 3 Oct 2005 15:24:37 -0400 Message-ID: Thread-Topic: [XCON] Draft defining a Common Data Model for XCON Thread-Index: AcXEcZ3dXiaACj3JROuSXHpn16Dy2gD3DBKg From: "Morgan, Dave" To: "Orit Levin" , "Gonzalo Camarillo" , "XCON" , "Oscar Novo \(JO/LMF\)" X-OriginalArrivalTime: 03 Oct 2005 19:24:38.0262 (UTC) FILETIME=[186C5960:01C5C850] X-Spam-Score: 0.0 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d Content-Transfer-Encoding: quoted-printable Cc: 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Orit brings up a good point which needs to be resolved straight away. Should we: 1) Create a new namespace called common-conference-info (or XCon-conference-info for that matter) that incorporates all the conferencing elements needed in XCON to facilitate data manipulation protocols that operate on the conference object? OR 2) Use the conference-info namespace and schema in the sipping conferencing package and propose conference package extensions? Discussion on the mailing list of this topic would be greatly appreciated. Dave and Oscar ------------------------------------------------------------------------ David P. Morgan, PhD VP, Architecture & Planning Fidelity Investments Systems Company - Telecom Phone: 617 563-2178 Fax: 617 385 2122 Mailing: 82 Devonshire St, MZ V8C Boston, MA 02109-3614 Office: 245 Summer Street, 8th Floor -----Original Message----- From: Orit Levin [mailto:oritl@microsoft.com]=20 Sent: Wednesday, September 28, 2005 5:14 PM To: Gonzalo Camarillo; XCON Cc: Morgan, Dave Subject: RE: [XCON] Draft defining a Common Data Model for XCON Hi guys, It's really good that we have more people who have the cycles to invest into this work. I am still working on the next CCCP draft which will incorporate the lessons that we learned internally. One of these is, for example, the extensibility mechanism that I will include in the upcoming CCCP draft and will be relevant to this discussion as well. These are my thoughts about the draft: 1. Although in the Introduction the draft says that it is compliant with the Conference Event Package, it is not clear whether the draft aims at expanding the 'conference-type' defined in the package or it aims at redefining most of the information in a new namespace (as hinted by the xmlns:tns=3D"urn:ietf:params:xml:ns:common-conference-schema" in the Example). 2. If the intention is the latter, I think that we need to understand what the practical usage of the new common-conference-schema namespace is. I guess that you had in mind a data manipulation protocol that operates on a conference object of that type. I went though a similar exercise in CCCP. My conclusion is that you don't necessarily need or want to schematize all this information under a single XML tree belonging to a new namespace. For example, in CCCP we are referring to the Conference Event Package definitions without redefining any of them. Along the same lines - it is really not a good practice to redefine the XML definitions with their semantics in multiple documents. 3. That being said, I am sure that many new elements in the draft are good candidates for the conference package extensions. Any information that potentially needs to be distributed to the conference subscribers would fall under this category. I suggest to start working together on the Conference Package Extensions draft in parallel to any other efforts. Just to note, the way the current draft "extends" (in case this was the intention) the conference package schema in the Example - is not XML compliant with the conference event package schema itself. According to the Conference Event Package schema - any extension MUST come from "other" namespace with all the syntactic implications. =20 4. In the past, the main debate/disconnect around the "conference data model" was not so much about the common information, but about the template: what it is, how it looks like and, not less importantly, how the template fits into or lives side-by-side with the conference-type of the Conference Event Package. Your draft seems to suggest (under all the disclaimers above ;-) that the templates are included (as extensions) inside the conference-type. I personally like this approach because it automatically allows for distribution of any included information through the conference package notifications. (Of cause, only the information complying with the local policies will be included.) To rephrase, any information that is not defined as the Conference Event Package extension will require a separate mechanism (or at least a different event package) to be communicated to the interested parties. 5. Still we desperately need to conclude how a template relates to the conference data definition (and capture this in the framework)... Orit.=20 > -----Original Message----- > From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org] On=20 > Behalf Of Gonzalo Camarillo > Sent: Friday, September 23, 2005 5:10 AM > To: XCON > Cc: Dave.Morgan@fmr.com > Subject: [XCON] Draft defining a Common Data Model for XCON >=20 > Folks, >=20 > we have just submitted a draft defining a common data model for XCON. > Until it appears in the archives, you can fetch it from: >=20 > http://users.piuha.net/gonzalo/temp/draft-novo-xcon-common-dat > a-model-00.txt >=20 > We have taken a stab at defining the XML schema of a common=20 > data model for XCON. The idea would be that whichever=20 > conference policy protocol we define, it uses this data model. >=20 > You comments are appreciated. We hope to have discussions on=20 > this topic on the mailing list. >=20 > The following is the abstract of the draft: >=20 > This document collects, organizes, and describes the conference > variables that have been introduced in various protocol=20 > drafts of the > XCON and SIPPING working groups. The goal of this document is to > allow the conference control protocols to use a unified common > conference information data model for XCON. This=20 > document formally > defines an Extensible Markup Language (XML) Schema that represents > the common conference information in a conferencing server. The > information is modeled as a series of elements, each of which > contains a set of children and attributes. >=20 >=20 > Cheers, >=20 > Gonzalo >=20 >=20 > _______________________________________________ > XCON mailing list > XCON@ietf.org > https://www1.ietf.org/mailman/listinfo/xcon >=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Oct 03 19:02:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMZJx-00073G-2c; Mon, 03 Oct 2005 19:02:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMZJv-000735-Fe for xcon@megatron.ietf.org; Mon, 03 Oct 2005 19:02:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27186 for ; Mon, 3 Oct 2005 19:02:04 -0400 (EDT) Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMZST-0005GC-9h for xcon@ietf.org; Mon, 03 Oct 2005 19:10:58 -0400 Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Mon, 3 Oct 2005 16:01:56 -0700 Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.14]) by mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 3 Oct 2005 16:01:56 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 3 Oct 2005 16:01:55 -0700 Message-ID: Thread-Topic: Comments on draft-boulton-xcon-media-template-01 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcw== From: "Orit Levin" To: "XCON" X-OriginalArrivalTime: 03 Oct 2005 23:01:56.0144 (UTC) FILETIME=[739B4300:01C5C86E] X-Spam-Score: 0.8 (/) X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44 Cc: Chris Boulton , Umesh.Chandra@nokia.com Subject: [XCON] Comments on draft-boulton-xcon-media-template-01 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="===============0260357255==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============0260357255== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5C86E.734D6E15" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5C86E.734D6E15 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Guys, I would like to share my thoughts on the current "templates" draft direction. =20 1. The XML Schema Definition (e.g. 3.1.7) If my understanding is correct, the XML Schema definition in 3.1.7 is the single common XML schema definition which all the "templates" in the draft are defined from. =20 In order to be consistent with the current Framework terminology, I would say that "the XML Schema definition in 3.1.7 is the single template defined by this draft, which all the listed "blueprints" in this draft (e.g. basic-audio, advanced-audio, etc.) are instantiated from". =20 Conceptually speaking, the proposed approach looks to me as a definition of a "stencil" like UI-oriented format to be populated and communicated "as is" between a client and a server. If this is the idea, wouldn't it be easier to just use one of the existing protocols for UI representation? =20 I am not a great fan of this approach ;-) but it can be useful for unintelligent clients and would avoid the need for updating the client SW with every new template definition or extension. I will not object to this approach as long as we allow for different approaches (i.e. additional template types) as well ;-).=20 =20 2. The XML Definitions (e.g. 3.1.6, 3.2.6, etc.) Clearly from the XML, each of these XML documents is an example of a "blueprint" that needs to be defined by a specific conferencing system according to its administrative choices and capabilities and not by the IETF ;-) This also makes the whole approach work since the actual MIN and MAX values of the parameters are defined by the "blueprint" and not by the "template". =20 3. Do we really need a floor control in the basic blueprints? It is perfectly OK to have the floor control definitions in the template but would we typically need to have the floor control settings in the basic "blueprints"? This is just a question since anyway the "blueprint" definitions in the document should be examples only. =20 4. Parameters that exist in the conference event package In cases where the template parameters, controls, etc. correspond to more general elements defined in the Conference package, it will be very helpful to describe the relationships between/among them. For example, the sum of the participants of each role in the blueprint corresponds to the number of users in the conference package. =20 Thanks, Orit. ------_=_NextPart_001_01C5C86E.734D6E15 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Guys,
I = would like to=20 share my thoughts on the current "templates" draft=20 direction.
 
1. The = XML Schema=20 Definition (e.g. 3.1.7)
If my understanding is correct, the XML = Schema=20 definition in 3.1.7 is the single common XML schema definition which all = the=20 "templates" in the draft are defined from.
 
In order to be consistent with the current = Framework=20 terminology, I would say that "the XML Schema definition in 3.1.7 is the = single=20 template defined by this draft, which all the listed "blueprints" = in this=20 draft (e.g. basic-audio, advanced-audio, etc.) are instantiated=20 from".
 
Conceptually=20 speaking, the proposed approach looks to me as a definition of a = "stencil"=20 like UI-oriented format to be populated and communicated "as is" between = a=20 client and a server. If this is the idea, wouldn't it be easier to = just use=20 one of the existing protocols for UI representation?
 
I am = not a great fan=20 of this approach ;-) but it can be useful for unintelligent clients=20 and would avoid the need for updating the client SW with every new = template=20 definition or extension. I will not object to this approach as long as = we allow for different approaches (i.e. additional template = types) as=20 well ;-). 
 
2. The = XML=20 Definitions (e.g. 3.1.6, 3.2.6, etc.)
Clearly from the=20 XML, each of these XML documents is an example of a "blueprint" that = needs to be=20 defined by a specific conferencing system according to its = administrative=20 choices and capabilities and not by the IETF ;-) This also makes the = whole=20 approach work since the actual MIN and MAX values of the parameters are = defined=20 by the "blueprint" and not by the "template".
 
3. Do = we really need=20 a floor control in the basic blueprints?
It is = perfectly OK=20 to have the floor control definitions in the template but would we = typically=20 need to have the floor control settings in the basic "blueprints"? This = is just=20 a question since anyway the "blueprint" definitions in  the = document should=20 be examples only.
 
4. = Parameters that=20 exist in the conference event package
In = cases where the=20 template parameters, controls, etc. correspond to more general elements = defined=20 in the Conference package, it will be very helpful to describe the = relationships=20 between/among them. For example, the sum of the participants of each = role in the=20 blueprint corresponds to the number of users in the conference=20 package.
 
Thanks,
Orit.
------_=_NextPart_001_01C5C86E.734D6E15-- --===============0260357255== 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 --===============0260357255==-- From xcon-bounces@ietf.org Tue Oct 04 13:25:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMqXS-0000ff-Q2; Tue, 04 Oct 2005 13:25:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMqXR-0000fO-5L for xcon@megatron.ietf.org; Tue, 04 Oct 2005 13:25:13 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11329 for ; Tue, 4 Oct 2005 13:25:07 -0400 (EDT) Received: from e1.ny.us.ibm.com ([32.97.182.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMqg4-0001s1-UH for xcon@ietf.org; Tue, 04 Oct 2005 13:34:12 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e1.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j94HOrfL003566 for ; Tue, 4 Oct 2005 13:24:53 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j94HOrhH087930 for ; Tue, 4 Oct 2005 13:24:53 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j94HOr4U019884 for ; Tue, 4 Oct 2005 13:24:53 -0400 Received: from d01ml605.pok.ibm.com (d01ml605.pok.ibm.com [9.56.227.91]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j94HOqtc019372 for ; Tue, 4 Oct 2005 13:24:52 -0400 From: Zon-Yin Shae To: xcon@ietf.org Message-ID: Date: Tue, 4 Oct 2005 13:24:41 -0400 X-MIMETrack: Serialize by Router on D01ML605/01/M/IBM(Release 7.0|August 18, 2005) at 10/04/2005 13:24:51 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [XCON] Zon-Yin Shae is out of the office. 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org I will be out of the office starting 10/03/2005 and will not return until 10/14/2005. I will respond to your message when I return. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Oct 04 13:34:05 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMqg1-0004Hm-Lg; Tue, 04 Oct 2005 13:34:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMqg0-0004HK-1J for xcon@megatron.ietf.org; Tue, 04 Oct 2005 13:34:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12550 for ; Tue, 4 Oct 2005 13:34:02 -0400 (EDT) From: Umesh.Chandra@nokia.com Received: from mgw-ext01.nokia.com ([131.228.20.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMqoi-0002RG-Js for xcon@ietf.org; Tue, 04 Oct 2005 13:43:05 -0400 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j94HXwjp000809; Tue, 4 Oct 2005 20:34:01 +0300 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 20:33:57 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 12:33:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 4 Oct 2005 12:33:54 -0500 Message-ID: <815E2AF6A087FF45A68EF2F310ADE111A0B4B9@daebe102.NOE.Nokia.com> Thread-Topic: Comments on draft-boulton-xcon-media-template-01 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSw To: , X-OriginalArrivalTime: 04 Oct 2005 17:33:55.0663 (UTC) FILETIME=[CB89EDF0:01C5C909] X-Spam-Score: 0.3 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Content-Transfer-Encoding: quoted-printable Cc: cboulton@ubiquity.net Subject: [XCON] RE: Comments on draft-boulton-xcon-media-template-01 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hello Orit, =20 Thanks for the review and comments on the draft. Replines inline. Umesh ________________________________ From: ext Orit Levin [mailto:oritl@microsoft.com]=20 Sent: Monday, October 03, 2005 6:02 PM To: XCON Cc: Chris Boulton; Chandra Umesh (Nokia-NRC/Dallas) Subject: Comments on draft-boulton-xcon-media-template-01 =09 =09 Guys, I would like to share my thoughts on the current "templates" draft direction. =20 1. The XML Schema Definition (e.g. 3.1.7) =09 If my understanding is correct, the XML Schema definition in 3.1.7 is the single common XML schema definition which all the "templates" in the draft are defined from. =20 In order to be consistent with the current Framework terminology, I would say that "the XML Schema definition in 3.1.7 is the single template defined by this draft, which all the listed "blueprints" in this draft (e.g. basic-audio, advanced-audio, etc.) are instantiated from". [[Umesh]] I think you would have different templates for different conference scenarios like basic audio, basic audio/video etc. The way it would work is the moderator/creator of the conference would use a particular template based on the media being used in the conference and creates the blueprint. Ofcourse each conference template has functionalties which the moderator or creator of the conference might not want to use during the conference. But there will be different templates for different conferece senarios from which you instantiate the blueprint.=20 =20 Any reason why you would want to have just one template from which you could instantiate different type of conference scenarios. I guess may be we didnt understand this point clearly. =20 =20 Conceptually speaking, the proposed approach looks to me as a definition of a "stencil" like UI-oriented format to be populated and communicated "as is" between a client and a server. If this i the idea, wouldn't it be easier to just use one of the existing protocols for UI representation? =20 I am not a great fan of this approach ;-) but it can be useful for unintelligent clients and would avoid the need for updating the client SW with every new template definition or extension. I will not object to this approach as long as we allow for different approaches (i.e. additional template types) as well ;-). =20 =20 2. The XML Definitions (e.g. 3.1.6, 3.2.6, etc.) Clearly from the XML, each of these XML documents is an example of a "blueprint" that needs to be defined by a specific conferencing system according to its administrative choices and capabilities and not by the IETF ;-) This also makes the whole approach work since the actual MIN and MAX values of the parameters are defined by the "blueprint" and not by the "template". [[Umesh]] What we have section 3.1.6, 3.2.6 are just examples of an conference scenario. What ulimtaely would be in the draft would the XML schema which are the templates for difference conference scenarios. You are right when you say that the conferencing system admin would define the values from the templates which would be the blueprint. I am assuming the confusion is there since we have not provided the Schema (which is the actual template) and provided just the blueprint (or an examle). =20 3. Do we really need a floor control in the basic blueprints? It is perfectly OK to have the floor control definitions in the template but would we typically need to have the floor control settings in the basic "blueprints"? This is just a question since anyway the "blueprint" definitions in the document should be examples only. [[Umesh]] The reason we added floor control in the basic templates (or basic audio) would be for conference sceanrios like PTT. And also its possible to disable the floor control for a given conference scenario (as decided by the administrator of the conference). I would think that the floor control settings in the blueprints would be useful since if the end point UI is taking information from the blueprint (to display the UI), it could use the floor control setting to grey out the talk button on the UI incase the end point doesnt have the floor to talk. But i guess we need to discuss more on this point. =20 4. Parameters that exist in the conference event package In cases where the template parameters, controls, etc. correspond to more general elements defined in the Conference package, it will be very helpful to describe the relationships between/among them. For example, the sum of the participants of each role in the blueprint corresponds to the number of users in the conference package. [[Umesh]] Agreed. =20 =20 =20 Thanks, Orit. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Oct 04 15:39:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMsd9-0006Mw-DD; Tue, 04 Oct 2005 15:39:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMsd8-0006Mr-Jy for xcon@megatron.ietf.org; Tue, 04 Oct 2005 15:39:14 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20713 for ; Tue, 4 Oct 2005 15:39:12 -0400 (EDT) Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMslr-0005wN-Tu for xcon@ietf.org; Tue, 04 Oct 2005 15:48:16 -0400 Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 4 Oct 2005 12:39:03 -0700 Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.14]) by mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 12:39:03 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 4 Oct 2005 12:39:02 -0700 Message-ID: Thread-Topic: Comments on draft-boulton-xcon-media-template-01 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/A= From: "Orit Levin" To: , X-OriginalArrivalTime: 04 Oct 2005 19:39:03.0574 (UTC) FILETIME=[469A3B60:01C5C91B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8 Content-Transfer-Encoding: quoted-printable Cc: cboulton@ubiquity.net Subject: [XCON] RE: Comments on draft-boulton-xcon-media-template-01 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Umesh, Based on your reply I think that only a couple of additions and clarifications to the draft will make it much more explicit: 1. First, I do think that we do need more than a single template. May be even a dedicated one for each media type. Yes, please, add a template XML definition (.xsd) for each template in the draft. I suspect that once we have them defined, we will see that because of the "stencil-like" approach - they all will look very much the same. (On contrary, had you chosen the semantic oriented approach, the templates could look very different for different conference types: "basic interactive audio&video" vs. "e-learning application sharing with moderator", etc.) 2. Yes, please, rename the current "XML definition" sections to "Blueprint Example". This will avoid possible future confusions. Thanks a lot, Orit. =20 > -----Original Message----- > From: Umesh.Chandra@nokia.com [mailto:Umesh.Chandra@nokia.com]=20 > Sent: Tuesday, October 04, 2005 10:34 AM > To: Orit Levin; xcon@ietf.org > Cc: cboulton@ubiquity.net > Subject: RE: Comments on draft-boulton-xcon-media-template-01 >=20 > Hello Orit, > =20 > Thanks for the review and comments on the draft. Replines inline. > Umesh >=20 >=20 > ________________________________ >=20 > From: ext Orit Levin [mailto:oritl@microsoft.com]=20 > Sent: Monday, October 03, 2005 6:02 PM > To: XCON > Cc: Chris Boulton; Chandra Umesh (Nokia-NRC/Dallas) > Subject: Comments on draft-boulton-xcon-media-template-01 > =09 > =09 > Guys, > I would like to share my thoughts on the current "templates" > draft direction. > =20 > 1. The XML Schema Definition (e.g. 3.1.7) > =09 > If my understanding is correct, the XML Schema definition in > 3.1.7 is the single common XML schema definition which all=20 > the "templates" in the draft are defined from. > =20 > In order to be consistent with the current Framework=20 > terminology, I would say that "the XML Schema definition in=20 > 3.1.7 is the single template defined by this draft, which all=20 > the listed "blueprints" > in this draft (e.g. basic-audio, advanced-audio, etc.) are=20 > instantiated from". > [[Umesh]] I think you would have different templates=20 > for different conference scenarios like basic audio, basic=20 > audio/video etc. > The way it would work is the moderator/creator of the=20 > conference would use a particular template based on the media=20 > being used in the conference and creates the blueprint.=20 > Ofcourse each conference template has functionalties which=20 > the moderator or creator of the conference might not want to=20 > use during the conference. But there will be different=20 > templates for different conferece senarios from which you=20 > instantiate the blueprint.=20 > =20 > Any reason why you would want to have just one template=20 > from which you could instantiate different type of conference=20 > scenarios. I guess may be we didnt understand this point clearly. > =20 > =20 > Conceptually speaking, the proposed approach looks to=20 > me as a definition of a "stencil" like UI-oriented format to=20 > be populated and communicated "as is" between a client and a=20 > server. If this i the idea, wouldn't it be easier to just use=20 > one of the existing protocols for UI representation? > =20 > I am not a great fan of this approach ;-) but it can be=20 > useful for unintelligent clients and would avoid the need for=20 > updating the client SW with every new template definition or=20 > extension. I will not object to this approach as long as we=20 > allow for different approaches (i.e. additional template=20 > types) as well ;-). =20 > =20 > 2. The XML Definitions (e.g. 3.1.6, 3.2.6, etc.) > Clearly from the XML, each of these XML documents is an=20 > example of a "blueprint" that needs to be defined by a=20 > specific conferencing system according to its administrative=20 > choices and capabilities and not by the IETF ;-) This also=20 > makes the whole approach work since the actual MIN and MAX=20 > values of the parameters are defined by the "blueprint" and=20 > not by the "template". > [[Umesh]] What we have section 3.1.6, 3.2.6 are just=20 > examples of an conference scenario. What ulimtaely would be=20 > in the draft would the XML schema which are the templates for=20 > difference conference scenarios. > You are right when you say that the conferencing system admin=20 > would define the values from the templates which would be the=20 > blueprint. I am assuming the confusion is there since we have=20 > not provided the Schema (which is the actual template) and=20 > provided just the blueprint (or an examle). > =20 > 3. Do we really need a floor control in the basic blueprints? > It is perfectly OK to have the floor control=20 > definitions in the template but would we typically need to=20 > have the floor control settings in the basic "blueprints"?=20 > This is just a question since anyway the "blueprint"=20 > definitions in the document should be examples only. > [[Umesh]] The reason we added floor control in the=20 > basic templates (or basic audio) would be for conference=20 > sceanrios like PTT. > And also its possible to disable the floor control for a=20 > given conference scenario (as decided by the administrator of=20 > the conference). > I would think that the floor control settings in the=20 > blueprints would be useful since if the end point UI is=20 > taking information from the blueprint (to display the UI), it=20 > could use the floor control setting to grey out the talk=20 > button on the UI incase the end point doesnt have the floor=20 > to talk. But i guess we need to discuss more on this point. > =20 > 4. Parameters that exist in the conference event package > In cases where the template parameters, controls, etc. > correspond to more general elements defined in the Conference=20 > package, it will be very helpful to describe the=20 > relationships between/among them. For example, the sum of the=20 > participants of each role in the blueprint corresponds to the=20 > number of users in the conference package. > [[Umesh]] Agreed. > =20 > =20 > =20 > Thanks, > Orit. >=20 >=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Oct 04 16:00:40 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMsxs-0003jq-KJ; Tue, 04 Oct 2005 16:00:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMsxq-0003jX-HL for xcon@megatron.ietf.org; Tue, 04 Oct 2005 16:00:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23026 for ; Tue, 4 Oct 2005 16:00:36 -0400 (EDT) From: Umesh.Chandra@nokia.com Received: from mgw-ext02.nokia.com ([131.228.20.94]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMt6Y-000736-24 for xcon@ietf.org; Tue, 04 Oct 2005 16:09:40 -0400 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j94K0V63002414; Tue, 4 Oct 2005 23:00:32 +0300 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 23:00:29 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Oct 2005 15:00:01 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 4 Oct 2005 15:00:00 -0500 Message-ID: <815E2AF6A087FF45A68EF2F310ADE111A0B572@daebe102.NOE.Nokia.com> Thread-Topic: Comments on draft-boulton-xcon-media-template-01 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/AAAQgBQA== To: , X-OriginalArrivalTime: 04 Oct 2005 20:00:01.0667 (UTC) FILETIME=[347BFD30:01C5C91E] X-Spam-Score: 0.4 (/) X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48 Content-Transfer-Encoding: quoted-printable Cc: cboulton@ubiquity.net Subject: [XCON] RE: Comments on draft-boulton-xcon-media-template-01 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Orit, Reply inline.. Thanks Umesh=20 -----Original Message----- From: ext Orit Levin [mailto:oritl@microsoft.com]=20 Sent: Tuesday, October 04, 2005 2:39 PM To: Chandra Umesh (Nokia-NRC/Dallas); xcon@ietf.org Cc: cboulton@ubiquity.net Subject: RE: Comments on draft-boulton-xcon-media-template-01 Umesh, Based on your reply I think that only a couple of additions and clarifications to the draft will make it much more explicit: 1. First, I do think that we do need more than a single template. May be even a dedicated one for each media type. Yes, please, add a template XML definition (.xsd) for each template in the draft. I suspect that once we have them defined, we will see that because of the "stencil-like" approach - they all will look very much the same. (On contrary, had you chosen the semantic oriented approach, the templates could look very different for different conference types: "basic interactive audio&video" vs. "e-learning application sharing with moderator", etc.) [Umesh] I guess there would be an explosion of templates if we take a semantic based approach in desigining templates. By semantic based approach you mean having a specific template for a specific scenario, for example e-learning application sharing with moderator or Audio/video conference with text. That is why we tried to provide capabilities in the templates so that you could use templates for specific scenarios, case in point the floor control support which could be disabled if not required. The aim is to have templates defined in such a way that you could derive max conference scenarios out of it. The conference scenario document was taken into consideration when coming up with templates (and I think we still need to cover some scenarios). 2. Yes, please, rename the current "XML definition" sections to "Blueprint Example". This will avoid possible future confusions. Thanks a lot, Orit. =20 > -----Original Message----- > From: Umesh.Chandra@nokia.com [mailto:Umesh.Chandra@nokia.com] > Sent: Tuesday, October 04, 2005 10:34 AM > To: Orit Levin; xcon@ietf.org > Cc: cboulton@ubiquity.net > Subject: RE: Comments on draft-boulton-xcon-media-template-01 >=20 > Hello Orit, > =20 > Thanks for the review and comments on the draft. Replines inline. > Umesh >=20 >=20 > ________________________________ >=20 > From: ext Orit Levin [mailto:oritl@microsoft.com]=20 > Sent: Monday, October 03, 2005 6:02 PM > To: XCON > Cc: Chris Boulton; Chandra Umesh (Nokia-NRC/Dallas) > Subject: Comments on draft-boulton-xcon-media-template-01 > =09 > =09 > Guys, > I would like to share my thoughts on the current "templates" > draft direction. > =20 > 1. The XML Schema Definition (e.g. 3.1.7) > =09 > If my understanding is correct, the XML Schema definition in > 3.1.7 is the single common XML schema definition which all the=20 > "templates" in the draft are defined from. > =20 > In order to be consistent with the current Framework terminology, I=20 > would say that "the XML Schema definition in > 3.1.7 is the single template defined by this draft, which all the=20 > listed "blueprints" > in this draft (e.g. basic-audio, advanced-audio, etc.) are=20 > instantiated from". > [[Umesh]] I think you would have different templates for different=20 > conference scenarios like basic audio, basic audio/video etc. > The way it would work is the moderator/creator of the conference would > use a particular template based on the media being used in the=20 > conference and creates the blueprint. > Ofcourse each conference template has functionalties which the=20 > moderator or creator of the conference might not want to use during=20 > the conference. But there will be different templates for different=20 > conferece senarios from which you instantiate the blueprint. > =20 > Any reason why you would want to have just one template from which=20 > you could instantiate different type of conference scenarios. I guess=20 > may be we didnt understand this point clearly. > =20 > =20 > Conceptually speaking, the proposed approach looks to me as a=20 > definition of a "stencil" like UI-oriented format to be populated and=20 > communicated "as is" between a client and a server. If this i the=20 > idea, wouldn't it be easier to just use one of the existing protocols=20 > for UI representation? > =20 > I am not a great fan of this approach ;-) but it can be useful for=20 > unintelligent clients and would avoid the need for updating the client > SW with every new template definition or extension. I will not object=20 > to this approach as long as we allow for different approaches (i.e.=20 > additional template > types) as well ;-). =20 > =20 > 2. The XML Definitions (e.g. 3.1.6, 3.2.6, etc.) > Clearly from the XML, each of these XML documents is an example of a=20 > "blueprint" that needs to be defined by a specific conferencing system > according to its administrative choices and capabilities and not by=20 > the IETF ;-) This also makes the whole approach work since the actual=20 > MIN and MAX values of the parameters are defined by the "blueprint"=20 > and not by the "template". > [[Umesh]] What we have section 3.1.6, 3.2.6 are just examples of an=20 > conference scenario. What ulimtaely would be in the draft would the=20 > XML schema which are the templates for difference conference=20 > scenarios. > You are right when you say that the conferencing system admin would=20 > define the values from the templates which would be the blueprint. I=20 > am assuming the confusion is there since we have not provided the=20 > Schema (which is the actual template) and provided just the blueprint=20 > (or an examle). > =20 > 3. Do we really need a floor control in the basic blueprints? > It is perfectly OK to have the floor control definitions in the=20 > template but would we typically need to have the floor control=20 > settings in the basic "blueprints"? > This is just a question since anyway the "blueprint"=20 > definitions in the document should be examples only. > [[Umesh]] The reason we added floor control in the basic templates=20 > (or basic audio) would be for conference sceanrios like PTT. > And also its possible to disable the floor control for a given=20 > conference scenario (as decided by the administrator of the=20 > conference). > I would think that the floor control settings in the blueprints would=20 > be useful since if the end point UI is taking information from the=20 > blueprint (to display the UI), it could use the floor control setting=20 > to grey out the talk button on the UI incase the end point doesnt have > the floor to talk. But i guess we need to discuss more on this point. > =20 > 4. Parameters that exist in the conference event package > In cases where the template parameters, controls, etc. > correspond to more general elements defined in the Conference package, > it will be very helpful to describe the relationships between/among=20 > them. For example, the sum of the participants of each role in the=20 > blueprint corresponds to the number of users in the conference=20 > package. > [[Umesh]] Agreed. > =20 > =20 > =20 > Thanks, > Orit. >=20 >=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Wed Oct 12 09:34:04 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPgk8-000652-Gu; Wed, 12 Oct 2005 09:34:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPgk7-00064u-3u for xcon@megatron.ietf.org; Wed, 12 Oct 2005 09:34:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21261 for ; Wed, 12 Oct 2005 09:34:00 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPguL-0002KY-Rz for xcon@ietf.org; Wed, 12 Oct 2005 09:44:43 -0400 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8A8A910BB; Wed, 12 Oct 2005 15:33:54 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 15:33:54 +0200 Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 15:33:54 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Oct 2005 15:32:54 +0200 Message-ID: Thread-Topic: Comments on draft-boulton-xcon-media-template-01 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/AAAQgBQAGEXisw From: "Oscar Novo (JO/LMF)" To: , X-OriginalArrivalTime: 12 Oct 2005 13:33:54.0143 (UTC) FILETIME=[96DE5EF0:01C5CF31] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: quoted-printable Cc: Subject: [XCON] Comments on draft-even-xcon-pnc-00 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Roni, I guess that in your draft "People and Content video streams" you are = interested to mapped the "Live" and "Presentation" roles of H.239 with = SIP. Draft-hautakorpi-mmusic-sdp-media-content-01 has already mentioned = it. That draft explains that the 'main-video' SIP value is similar to = the 'presentation' role in H.239 and the 'alt-video' is similar to the = 'live' role in H.239. So, I don=B4t understand the propose of your = draft. I think you have to be concise with the types defined for the 'content' = attribute in the Draft-hautakorpi-mmusic-sdp-media-content-01 because it = makes confusion when you read the draft. All over the draft you talk = about 'main' and 'alt' type (for example, in the example of section 4 = you have the 'content' attribute with the 'main' and 'alt' type). This = types are not defined in Draft-hautakorpi-mmusic-sdp-media-content-01, = it defines the types "main-video", "alt-video" and "sl" for video = streams. And the last thing, in your draft you mapped the 'alt-video' and the = 'main-video' btw H.239 and SIP but you don't say anything about the 'sl' = type. What happended with the type? How do you mapped it in H.239? Thanks, Oscar=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Wed Oct 12 11:07:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPiD0-00040m-9j; Wed, 12 Oct 2005 11:07:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPiCv-00040b-HA for xcon@megatron.ietf.org; Wed, 12 Oct 2005 11:07:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27016 for ; Wed, 12 Oct 2005 11:07:50 -0400 (EDT) Received: from atlantis.osc.edu ([192.148.249.4] helo=email.osc.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPiNF-0005E4-QE for xcon@ietf.org; Wed, 12 Oct 2005 11:18:34 -0400 Received: from planwel (199-18-139-113.dhcp.columbus.oar.net [199.18.139.113]) by email.osc.edu (Postfix) with SMTP id A7FF827C023; Wed, 12 Oct 2005 11:07:40 -0400 (EDT) Message-ID: <4d7f01c5cf3e$b3ac4260$718b12c7@planwel> From: "Arif Khan" To: Date: Wed, 12 Oct 2005 11:07:45 -0400 Organization: OARnet MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Score: 0.5 (/) X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee Cc: The Megaconference , xcon@ietf.org, ViDeNet Zone Administrator's Listserv Subject: [XCON] Thrid Frontier Network Application Demo X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arif Khan List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1333511451==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1333511451== Content-Type: multipart/alternative; boundary="----=_NextPart_000_4D7B_01C5CF1D.2C7F2B20" This is a multi-part message in MIME format. ------=_NextPart_000_4D7B_01C5CF1D.2C7F2B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Greetings: You are cordially invited to attend the upcoming=20 Third Frontier Network Event at Shawnee State University virtually = tomorrow.=20 This event will focus on the rapid development of the Interactive = Digital=20 Imaging Technologies industry, as well as feature an exciting keynote=20 address from a national leader in this emerging field. There will also = be a=20 groundbreaking demonstration of adding assets to a live, regionally=20 networked beta gaming simulation, plus interactive presentations from = Ohio=20 college and university students, academic program directors and industry = representatives. The demo will show game players overlaid over the game in small = transparent=20 windows by using high bandwidth 2.0 mbps connections using Interlaced = Video=20 at 30 FPS (60 Fields Per Second), this is the first time ever this is = being=20 done, and may change the whole concept of game playing. The unique = feature=20 of this demo is that you will see players in real time commenting and=20 talking to each other while playing the game. For viewers it will not = be=20 interactive it is just a broadcast. KEYNOTE ADDRESS The Importance of High-speed Scalable Networks to the development of=20 Interactive Digital Technologies featuring Dr. Michael Zyda, Director of = the=20 Viterbi School of Engineering's GamePipe Laboratory at the University of = Southern California. WHERE: Shawnee State University, Vern Riffe Center for Fine Arts WHEN: Thursday, October 13, 2005 Presentation starts at 3:00 pm EST A joint reception follows at 4:30 pm. EST For more information and registration, please visit = http://www.oar.net/tfnevents There are three ways to watch the broadcast. Dialing Directions for Watching 4CIF Video: 1. Register with a GDS-enabled Gatekeeper. (To borrow space see:=20 http://commons.internet2.edu/reggate.html) 2. Make sure you are connecting at 384 kbps to 2.0 mbps. 3. Dial 001189 781 4444 (no spaces) Dialing Directions for Watching regular Video: 1. Register with a GDS-enabled Gatekeeper. (To borrow space see:=20 http://commons.internet2.edu/reggate.html) 2. Make sure you are connecting at 384 kbps to 2.0 mbps. 3. Dial 001189 781 5555 (no spaces) Watching Stream: Encoded at 384k rtsp://codian.oar.net/conf_h263_g711u_384000__TFN+Shawnee+State+-+Mike+Zy= da+ Encoded at 768k rtsp://codian.oar.net/conf_h263_g711u_768000__TFN+Shawnee+State+-+Mike+Zy= da+ Note: The best results will be viewing it on QuickTime Version 7.0 you can download it from http://www.apple.com/quicktime/download/win.html Kind Regards _____________________ Arif Khan Global Internet2 H.323 Services NOC OARnet - A Division of Ohio Supercomputer Center 800-627-6420 or 614-292-9191 614-292-9087 akhan@oar.net Ohio Supercomputer Center http://www.osc.edu OARnet http://www.oar.net Third Frontier Network http://www.osc.edu/oarnet/tfn/ Internet2 Commons http://commons.internet2.edu=20 ------=_NextPart_000_4D7B_01C5CF1D.2C7F2B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Greetings:
 
You are=20 cordially invited  to attend the upcoming
Third Frontier = Network Event=20 at Shawnee State University virtually tomorrow.
This event will = focus on the=20 rapid development of the Interactive Digital
Imaging Technologies = industry,=20 as well as feature an exciting keynote
address from a national = leader in=20 this emerging field. There will also be a
groundbreaking = demonstration of=20 adding assets to a live, regionally
networked beta gaming = simulation, plus=20 interactive presentations from Ohio
college and university students, = academic program directors and industry
representatives.

The = demo=20 will show game players overlaid over the game in small transparent =
windows=20 by using high bandwidth 2.0 mbps connections using Interlaced Video =
at 30=20 FPS (60 Fields Per Second), this is the first time ever this is being =
done,=20 and may change the whole concept of game playing.  The unique = feature=20
of this demo is that you will see players in real time commenting = and=20
talking to each other while playing the game.  For viewers it = will not=20 be
interactive it is just a broadcast.

KEYNOTE ADDRESS
The = Importance of High-speed Scalable Networks to the development of =
Interactive=20 Digital Technologies featuring Dr. Michael Zyda, Director of the =
Viterbi=20 School of Engineering's GamePipe Laboratory at the University of =
Southern=20 California.

WHERE: Shawnee State University, Vern Riffe Center = for Fine=20 Arts

WHEN: Thursday, October 13, 2005
Presentation starts at = 3:00 pm=20 EST
A joint reception follows at 4:30 pm. EST

For more = information and=20 registration, please visit http://www.oar.net/tfnevents

There are three ways to watch the=20 broadcast.

Dialing Directions for Watching 4CIF Video:
1. = Register=20 with a GDS-enabled Gatekeeper. (To borrow space see:
http://commons.internet2.edu/reggate.html)
2. Make sure you are connecting = at 384 kbps=20 to 2.0 mbps.
3. Dial 001189 781 4444 (no spaces)

Dialing = Directions=20 for Watching regular Video:
1. Register with a GDS-enabled = Gatekeeper. (To=20 borrow space see:
http://commons.internet2.edu/reggate.html)
2. Make sure you are connecting = at 384 kbps=20 to 2.0 mbps.
3. Dial 001189 781 5555 (no spaces)

Watching=20 Stream:
Encoded at=20 384k
rtsp://codian.oar.net/conf_h263_g711u_384000__TFN+Shawnee+State+-= +Mike+Zyda+

Encoded=20 at=20 768k
rtsp://codian.oar.net/conf_h263_g711u_768000__TFN+Shawnee+State+-= +Mike+Zyda+

Note: =20 The best results will be viewing it on QuickTime Version 7.0 you
can = download=20 it from http://www.apple.com/quicktime/download/win.html
<= BR>

Kind = Regards
_____________________
Arif=20 Khan
Global Internet2 H.323 Services NOC
OARnet - A Division of = Ohio=20 Supercomputer Center
800-627-6420 or=20 614-292-9191
614-292-9087
akhan@oar.net
Ohio Supercomputer Center http://www.osc.edu
OARnet http://www.oar.net
Third Frontier Network http://www.osc.edu/oarnet/tfn/
Internet2 Commons http://commons.internet2.edu=20
------=_NextPart_000_4D7B_01C5CF1D.2C7F2B20-- --===============1333511451== 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 --===============1333511451==-- From xcon-bounces@ietf.org Thu Oct 13 04:40:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPye0-0006Ln-68; Thu, 13 Oct 2005 04:40:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPydy-0006IY-AJ for xcon@megatron.ietf.org; Thu, 13 Oct 2005 04:40:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02590 for ; Thu, 13 Oct 2005 04:40:50 -0400 (EDT) Received: from fw.polycom.co.il ([212.179.41.2] helo=isrexch01.israel.polycom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPyoQ-0003ti-PJ for xcon@ietf.org; Thu, 13 Oct 2005 04:51:44 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Oct 2005 10:19:09 +0200 Message-ID: <144ED8561CE90C41A3E5908EDECE315C028BA9FA@IsrExch01.israel.polycom.com> Thread-Topic: Comments on draft-even-xcon-pnc-00 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/AAAQgBQAGEXiswACgLgLA= From: "Even, Roni" To: "Oscar Novo \(JO/LMF\)" , X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: quoted-printable Cc: Subject: [XCON] RE: Comments on draft-even-xcon-pnc-00 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Oscar, My draft intend to be a best current practice and should be in line with = the media-content draft and the mapping to H.239 described there. There = should be a new ietf-mmusic-sdp-media-content draft since it was = accepted as a working group item. As for SL type it is not part of H.239 but maybe I should add a usage = scenario for multipoint. Roni Even=20 -----Original Message----- From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com]=20 Sent: Wednesday, October 12, 2005 3:33 PM To: xcon@ietf.org; Even, Roni Subject: Comments on draft-even-xcon-pnc-00 Hi Roni, I guess that in your draft "People and Content video streams" you are = interested to mapped the "Live" and "Presentation" roles of H.239 with = SIP. Draft-hautakorpi-mmusic-sdp-media-content-01 has already mentioned = it. That draft explains that the 'main-video' SIP value is similar to = the 'presentation' role in H.239 and the 'alt-video' is similar to the = 'live' role in H.239. So, I don=B4t understand the propose of your = draft. I think you have to be concise with the types defined for the 'content' = attribute in the Draft-hautakorpi-mmusic-sdp-media-content-01 because it = makes confusion when you read the draft. All over the draft you talk = about 'main' and 'alt' type (for example, in the example of section 4 = you have the 'content' attribute with the 'main' and 'alt' type). This = types are not defined in Draft-hautakorpi-mmusic-sdp-media-content-01, = it defines the types "main-video", "alt-video" and "sl" for video = streams. And the last thing, in your draft you mapped the 'alt-video' and the = 'main-video' btw H.239 and SIP but you don't say anything about the 'sl' = type. What happended with the type? How do you mapped it in H.239? Thanks, Oscar=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Thu Oct 13 06:00:12 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPzsi-0002Vh-Qo; Thu, 13 Oct 2005 06:00:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPzsh-0002Vc-PA for xcon@megatron.ietf.org; Thu, 13 Oct 2005 06:00:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06660 for ; Thu, 13 Oct 2005 06:00:07 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ036-000689-TQ for xcon@ietf.org; Thu, 13 Oct 2005 06:11:02 -0400 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 52A2D116A; Thu, 13 Oct 2005 11:59:53 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Thu, 13 Oct 2005 11:59:18 +0200 Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Thu, 13 Oct 2005 11:59:18 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Oct 2005 11:58:17 +0200 Message-ID: Thread-Topic: Comments on draft-even-xcon-pnc-00 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/AAAQgBQAGEXiswACgLgLAAA3SzEA== From: "Oscar Novo (JO/LMF)" To: "Even, Roni" , X-OriginalArrivalTime: 13 Oct 2005 09:59:18.0221 (UTC) FILETIME=[C6A257D0:01C5CFDC] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: quoted-printable Cc: Subject: [XCON] RE: Comments on draft-even-xcon-pnc-00 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Roni, Then, I think you should refer in your draft to the new version = draft-ietf-mmusic-sdp-media-content-00 and not to the old one = draft-hautakorpi-mmusic-sdp-media-content-01 or at least when you submit = the draft tell that you are refering to the new version of the draft = that you can find: http://users.piuha.net/jantzgu/temp/draft-ietf-mmusic-sdp-media-content-0= 0.txt An a different question, what is doing this draft in XCON WG? = Shouldn=B4t it be in the MMUSIC WG? Thanks, Oscar -----Original Message----- From: Even, Roni [mailto:roni.even@polycom.co.il] Sent: 13. lokakuuta 2005 11:19 To: Oscar Novo (JO/LMF); xcon@ietf.org Subject: RE: Comments on draft-even-xcon-pnc-00 Oscar, My draft intend to be a best current practice and should be in line with = the media-content draft and the mapping to H.239 described there. There = should be a new ietf-mmusic-sdp-media-content draft since it was = accepted as a working group item. As for SL type it is not part of H.239 but maybe I should add a usage = scenario for multipoint. Roni Even=20 -----Original Message----- From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com]=20 Sent: Wednesday, October 12, 2005 3:33 PM To: xcon@ietf.org; Even, Roni Subject: Comments on draft-even-xcon-pnc-00 Hi Roni, I guess that in your draft "People and Content video streams" you are = interested to mapped the "Live" and "Presentation" roles of H.239 with = SIP. Draft-hautakorpi-mmusic-sdp-media-content-01 has already mentioned = it. That draft explains that the 'main-video' SIP value is similar to = the 'presentation' role in H.239 and the 'alt-video' is similar to the = 'live' role in H.239. So, I don=B4t understand the propose of your = draft. I think you have to be concise with the types defined for the 'content' = attribute in the Draft-hautakorpi-mmusic-sdp-media-content-01 because it = makes confusion when you read the draft. All over the draft you talk = about 'main' and 'alt' type (for example, in the example of section 4 = you have the 'content' attribute with the 'main' and 'alt' type). This = types are not defined in Draft-hautakorpi-mmusic-sdp-media-content-01, = it defines the types "main-video", "alt-video" and "sl" for video = streams. And the last thing, in your draft you mapped the 'alt-video' and the = 'main-video' btw H.239 and SIP but you don't say anything about the 'sl' = type. What happended with the type? How do you mapped it in H.239? Thanks, Oscar=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Thu Oct 13 12:28:36 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ5wa-0001QF-NM; Thu, 13 Oct 2005 12:28:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ5wZ-0001QA-GK for xcon@megatron.ietf.org; Thu, 13 Oct 2005 12:28:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27351 for ; Thu, 13 Oct 2005 12:28:31 -0400 (EDT) Received: from fw.polycom.co.il ([212.179.41.2] helo=isrexch01.israel.polycom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ677-00005H-Ca for xcon@ietf.org; Thu, 13 Oct 2005 12:39:29 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Oct 2005 18:29:44 +0200 Message-ID: <144ED8561CE90C41A3E5908EDECE315C028BAA29@IsrExch01.israel.polycom.com> Thread-Topic: Comments on draft-even-xcon-pnc-00 Thread-Index: AcXIbnM9MahOVsdHTeuduZMvqncFcwAkgBSwAAXx9/AAAQgBQAGEXiswACgLgLAAA3SzEAANnVtA From: "Even, Roni" To: "Oscar Novo \(JO/LMF\)" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Content-Transfer-Encoding: quoted-printable Cc: Subject: [XCON] RE: Comments on draft-even-xcon-pnc-00 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Oscar, I had to submit the draft before Jani's due to the last submission dates = for 00 draft, I was aware of the problem with the attribute names and = preferred to use the one in the ietf-mmusic draft which was not = published yet so I had a problem referring to it. I will fix this in the = next revision, it will be in line with the content draft and terminology = and . As for having it at XCON, I consulted with Allison and the conclusion = was to have it in XCON since it addresses multipoint conferencing = functionality based on both the content and the BFCP work. The purpose = is to make it a BCP Roni=20 -----Original Message----- From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com]=20 Sent: Thursday, October 13, 2005 11:58 AM To: Even, Roni; xcon@ietf.org Cc: Jani Hautakorpi (JO/LMF) Subject: RE: Comments on draft-even-xcon-pnc-00 Hi Roni, Then, I think you should refer in your draft to the new version = draft-ietf-mmusic-sdp-media-content-00 and not to the old one = draft-hautakorpi-mmusic-sdp-media-content-01 or at least when you submit = the draft tell that you are refering to the new version of the draft = that you can find: http://users.piuha.net/jantzgu/temp/draft-ietf-mmusic-sdp-media-content-0= 0.txt An a different question, what is doing this draft in XCON WG? = Shouldn=B4t it be in the MMUSIC WG? Thanks, Oscar -----Original Message----- From: Even, Roni [mailto:roni.even@polycom.co.il] Sent: 13. lokakuuta 2005 11:19 To: Oscar Novo (JO/LMF); xcon@ietf.org Subject: RE: Comments on draft-even-xcon-pnc-00 Oscar, My draft intend to be a best current practice and should be in line with = the media-content draft and the mapping to H.239 described there. There = should be a new ietf-mmusic-sdp-media-content draft since it was = accepted as a working group item. As for SL type it is not part of H.239 but maybe I should add a usage = scenario for multipoint. Roni Even=20 -----Original Message----- From: Oscar Novo (JO/LMF) [mailto:oscar.novo@ericsson.com] Sent: Wednesday, October 12, 2005 3:33 PM To: xcon@ietf.org; Even, Roni Subject: Comments on draft-even-xcon-pnc-00 Hi Roni, I guess that in your draft "People and Content video streams" you are = interested to mapped the "Live" and "Presentation" roles of H.239 with = SIP. Draft-hautakorpi-mmusic-sdp-media-content-01 has already mentioned = it. That draft explains that the 'main-video' SIP value is similar to = the 'presentation' role in H.239 and the 'alt-video' is similar to the = 'live' role in H.239. So, I don=B4t understand the propose of your = draft. I think you have to be concise with the types defined for the 'content' = attribute in the Draft-hautakorpi-mmusic-sdp-media-content-01 because it = makes confusion when you read the draft. All over the draft you talk = about 'main' and 'alt' type (for example, in the example of section 4 = you have the 'content' attribute with the 'main' and 'alt' type). This = types are not defined in Draft-hautakorpi-mmusic-sdp-media-content-01, = it defines the types "main-video", "alt-video" and "sl" for video = streams. And the last thing, in your draft you mapped the 'alt-video' and the = 'main-video' btw H.239 and SIP but you don't say anything about the 'sl' = type. What happended with the type? How do you mapped it in H.239? Thanks, Oscar=20 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Oct 14 08:22:10 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQOZe-0003bZ-Rg; Fri, 14 Oct 2005 08:22:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQOZa-0003b6-GL for xcon@megatron.ietf.org; Fri, 14 Oct 2005 08:22:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06558 for ; Fri, 14 Oct 2005 08:22:01 -0400 (EDT) Received: from pagergate.osc.edu ([192.148.249.4] helo=email.osc.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQOkG-0001ia-Jc for xcon@ietf.org; Fri, 14 Oct 2005 08:33:11 -0400 Received: from planwel (199-18-139-113.dhcp.columbus.oar.net [199.18.139.113]) by email.osc.edu (Postfix) with SMTP id 7331A27C051; Fri, 14 Oct 2005 08:21:50 -0400 (EDT) Message-ID: <018901c5d0b9$dc1fb5c0$718b12c7@planwel> From: "Arif Khan" To: References: <4d7f01c5cf3e$b3ac4260$718b12c7@planwel> Date: Fri, 14 Oct 2005 08:21:52 -0400 Organization: OARnet MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Score: 0.5 (/) X-Scan-Signature: 3b8eea209b62bd15620865bc4fbef8cd Cc: The Megaconference , xcon@ietf.org, ViDeNet Zone Administrator's Listserv Subject: [XCON] Thrid Frontier Network Application Demo X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arif Khan List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0223140287==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============0223140287== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0186_01C5D098.54D886D0" This is a multi-part message in MIME format. ------=_NextPart_000_0186_01C5D098.54D886D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Greetings All: I would like to thank all the remote sites for attending this event. We had around 37 sites from all over the world watching, we can also = watch the archived stream at http://sg60.oar.net/TFN/ please scroll down, it is second to the last with time stamp Created on: 10/13/2005 = -14:21 EDT Duration: 1 hour, 46 minutes, 57 seconds I would also like to get some feedback so that we can learn from the = mistakes and get things better for future events, and get more ideas as = what can be done to improve this concept. Kind Regards _____________________ Arif Khan Global Internet2 H.323 Services NOC OARnet - A Division of Ohio Supercomputer Center 800-627-6420 or 614-292-9191 614-292-9087 akhan@oar.net Ohio Supercomputer Center http://www.osc.edu OARnet http://www.oar.net Third Frontier Network http://www.osc.edu/oarnet/tfn/ Internet2 Commons http://commons.internet2.edu ----- Original Message -----=20 From: Arif Khan=20 To: Megaconjr@lists.cciu.org=20 Cc: The Megaconference ; ViDeNet Zone Administrator's Listserv ; = xcon@ietf.org=20 Sent: Wednesday, October 12, 2005 11:07 AM Subject: [MegaconfJr List] Thrid Frontier Network Application Demo Greetings: You are cordially invited to attend the upcoming=20 Third Frontier Network Event at Shawnee State University virtually = tomorrow.=20 This event will focus on the rapid development of the Interactive = Digital=20 Imaging Technologies industry, as well as feature an exciting keynote=20 address from a national leader in this emerging field. There will also = be a=20 groundbreaking demonstration of adding assets to a live, regionally=20 networked beta gaming simulation, plus interactive presentations from = Ohio=20 college and university students, academic program directors and = industry=20 representatives. The demo will show game players overlaid over the game in small = transparent=20 windows by using high bandwidth 2.0 mbps connections using Interlaced = Video=20 at 30 FPS (60 Fields Per Second), this is the first time ever this is = being=20 done, and may change the whole concept of game playing. The unique = feature=20 of this demo is that you will see players in real time commenting and=20 talking to each other while playing the game. For viewers it will not = be=20 interactive it is just a broadcast. KEYNOTE ADDRESS The Importance of High-speed Scalable Networks to the development of=20 Interactive Digital Technologies featuring Dr. Michael Zyda, Director = of the=20 Viterbi School of Engineering's GamePipe Laboratory at the University = of=20 Southern California. WHERE: Shawnee State University, Vern Riffe Center for Fine Arts WHEN: Thursday, October 13, 2005 Presentation starts at 3:00 pm EST A joint reception follows at 4:30 pm. EST For more information and registration, please visit = http://www.oar.net/tfnevents There are three ways to watch the broadcast. Dialing Directions for Watching 4CIF Video: 1. Register with a GDS-enabled Gatekeeper. (To borrow space see:=20 http://commons.internet2.edu/reggate.html) 2. Make sure you are connecting at 384 kbps to 2.0 mbps. 3. Dial 001189 781 4444 (no spaces) Dialing Directions for Watching regular Video: 1. Register with a GDS-enabled Gatekeeper. (To borrow space see:=20 http://commons.internet2.edu/reggate.html) 2. Make sure you are connecting at 384 kbps to 2.0 mbps. 3. Dial 001189 781 5555 (no spaces) Watching Stream: Encoded at 384k = rtsp://codian.oar.net/conf_h263_g711u_384000__TFN+Shawnee+State+-+Mike+Zy= da+ Encoded at 768k = rtsp://codian.oar.net/conf_h263_g711u_768000__TFN+Shawnee+State+-+Mike+Zy= da+ Note: The best results will be viewing it on QuickTime Version 7.0 = you can download it from http://www.apple.com/quicktime/download/win.html Kind Regards _____________________ Arif Khan Global Internet2 H.323 Services NOC OARnet - A Division of Ohio Supercomputer Center 800-627-6420 or 614-292-9191 614-292-9087 akhan@oar.net Ohio Supercomputer Center http://www.osc.edu OARnet http://www.oar.net Third Frontier Network http://www.osc.edu/oarnet/tfn/ Internet2 Commons http://commons.internet2.edu=20 ------=_NextPart_000_0186_01C5D098.54D886D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Greetings=20 All:

 I would like to thank all the remote sites for = attending this=20 event.

We had around 37 sites from all over the world=20 watching,   we can also watch the archived stream at http://sg60.oar.net/TFN/=20 please scroll
down, it is second to the last with time stamp Created = on:=20 10/13/2005 -14:21 EDT  Duration: 1 hour, 46 minutes, 57 = seconds

I=20 would also like to get some feedback so that we can learn from the = mistakes and=20 get things better for future events, and get more ideas as what can be = done to=20 improve this concept.
Kind Regards
_____________________
Arif Khan
Global Internet2 H.323 = Services=20 NOC
OARnet - A Division of Ohio Supercomputer Center
800-627-6420 = or=20 614-292-9191
614-292-9087
akhan@oar.net
Ohio Supercomputer = Center http://www.osc.edu
OARnet http://www.oar.net
Third Frontier = Network http://www.osc.edu/oarnet/tfn/
Internet2=20 Commons http://commons.internet2.edu
----- Original Message -----
From:=20 Arif Khan =
Cc: The = Megaconference ; ViDeNet Zone=20 Administrator's Listserv ; xcon@ietf.org
Sent: Wednesday, October 12, = 2005 11:07=20 AM
Subject: [MegaconfJr List] = Thrid Frontier=20 Network Application Demo

Greetings:
 
You are=20 cordially invited  to attend the upcoming
Third Frontier = Network=20 Event at Shawnee State University virtually tomorrow.
This event = will=20 focus on the rapid development of the Interactive Digital
Imaging=20 Technologies industry, as well as feature an exciting keynote =
address from=20 a national leader in this emerging field. There will also be a=20
groundbreaking demonstration of adding assets to a live, = regionally=20
networked beta gaming simulation, plus interactive presentations = from Ohio=20
college and university students, academic program directors and = industry=20
representatives.

The demo will show game players overlaid = over the=20 game in small transparent
windows by using high bandwidth 2.0 mbps = connections using Interlaced Video
at 30 FPS (60 Fields Per = Second), this=20 is the first time ever this is being
done, and may change the = whole=20 concept of game playing.  The unique feature
of this demo is = that you=20 will see players in real time commenting and
talking to each other = while=20 playing the game.  For viewers it will not be
interactive it = is just=20 a broadcast.

KEYNOTE ADDRESS
The Importance of High-speed = Scalable=20 Networks to the development of
Interactive Digital Technologies = featuring=20 Dr. Michael Zyda, Director of the
Viterbi School of Engineering's = GamePipe=20 Laboratory at the University of
Southern California.

WHERE: = Shawnee=20 State University, Vern Riffe Center for Fine Arts

WHEN: = Thursday,=20 October 13, 2005
Presentation starts at 3:00 pm EST
A joint = reception=20 follows at 4:30 pm. EST

For more information and registration, = please=20 visit http://www.oar.net/tfnevents

There are three ways to watch the=20 broadcast.

Dialing Directions for Watching 4CIF Video:
1. = Register=20 with a GDS-enabled Gatekeeper. (To borrow space see:
http://commons.internet2.edu/reggate.html)
2. Make sure you are connecting = at 384 kbps=20 to 2.0 mbps.
3. Dial 001189 781 4444 (no spaces)

Dialing = Directions=20 for Watching regular Video:
1. Register with a GDS-enabled = Gatekeeper. (To=20 borrow space see:
http://commons.internet2.edu/reggate.html)
2. Make sure you are connecting = at 384 kbps=20 to 2.0 mbps.
3. Dial 001189 781 5555 (no spaces)

Watching=20 Stream:
Encoded at=20 = 384k
rtsp://codian.oar.net/conf_h263_g711u_384000__TFN+Shawnee+State+-= +Mike+Zyda+

Encoded=20 at=20 = 768k
rtsp://codian.oar.net/conf_h263_g711u_768000__TFN+Shawnee+State+-= +Mike+Zyda+

Note: =20 The best results will be viewing it on QuickTime Version 7.0 = you
can=20 download it from http://www.apple.com/quicktime/download/win.html
<= BR>

Kind = Regards
_____________________
Arif=20 Khan
Global Internet2 H.323 Services NOC
OARnet - A Division of = Ohio=20 Supercomputer Center
800-627-6420 or=20 614-292-9191
614-292-9087
akhan@oar.net
Ohio Supercomputer Center http://www.osc.edu
OARnet http://www.oar.net
Third Frontier Network http://www.osc.edu/oarnet/tfn/
Internet2 Commons http://commons.internet2.edu =
------=_NextPart_000_0186_01C5D098.54D886D0-- --===============0223140287== 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 --===============0223140287==-- From xcon-bounces@ietf.org Mon Oct 17 09:32:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERV6E-0007kK-K5; Mon, 17 Oct 2005 09:32:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERV6B-0007kC-H7 for xcon@megatron.ietf.org; Mon, 17 Oct 2005 09:32:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12279 for ; Mon, 17 Oct 2005 09:32:06 -0400 (EDT) Received: from maillnx-us112.fmr.com ([192.223.198.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERVHP-00062U-Tl for xcon@ietf.org; Mon, 17 Oct 2005 09:43:56 -0400 Received: from MSGMROSM02WIN.dmn1.fmr.com (MSGMROSM02WIN.dmn1.fmr.com [172.26.31.170]) by maillnx-us112.fmr.com (Switch-3.1.2/Switch-3.1.0) with SMTP id j9HDVr6G029243 for ; Mon, 17 Oct 2005 09:31:53 -0400 Received: from MSGMROIV02WIN.DMN1.FMR.COM (10.37.74.75) by MSGMROSM02WIN.dmn1.fmr.com (Sigaba Gateway v3.83) with ESMTP id 49835458; Mon, 17 Oct 2005 09:31:53 -0400 Received: from MSGMROIM01WIN.DMN1.FMR.COM ([172.26.2.194]) by MSGMROIV02WIN.DMN1.FMR.COM with SMTP_server; Mon, 17 Oct 2005 09:31:52 -0400 Received: from msgmroclm2win.fmr.com ([10.37.181.20]) by MSGMROIM01WIN.DMN1.FMR.COM with Microsoft SMTPSVC(5.0.2195.6713); Mon, 17 Oct 2005 09:31:52 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5D31F.22025BAE" Date: Mon, 17 Oct 2005 09:31:51 -0400 Message-ID: X-MS-Has-Attach: yes Thread-Topic: Draft defining the conferencing roles for XCON Thread-Index: AcXTHyKHbVFq+5bpQneen0TTlpKJlg== From: "Morgan, Dave" To: "XCON" X-OriginalArrivalTime: 17 Oct 2005 13:31:52.0069 (UTC) FILETIME=[222C1B50:01C5D31F] X-Spam-Score: 0.6 (/) X-Scan-Signature: 9d7e8d783239e9f0c425c823a9c950ff Cc: Subject: [XCON] Draft defining the conferencing roles for XCON 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C5D31F.22025BAE Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C5D31F.22025BAE" ------_=_NextPart_002_01C5D31F.22025BAE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, Oscar and I have just submitted a draft defining the conferencing roles for XCON. Until it appears in the archives, you can refer to the attached document.=20 In this draft we have taken a stab at defining five roles within a conference. They are: administrator, creator, moderator, participant, and observer. We have also written an XML schema so that these role definitions can be incorporated into other XCON drafts.=20 Your comments are appreciated. We hope to have discussions on this topic on the mailing list. The following is the abstract of the draft: This document defines the set of possible conferencing roles that are used to represent participants within a Conference Object (as defined in the XCON Conference Framework [1]). The document also provides a set of semantics associated with each role. Additional roles may be defined in the future, as necessary, with their corresponding schema extensions, as appropriate. Cheers, Dave ------------------------------------------------------------------------ David P. Morgan, PhD=20 VP, Architecture & Planning=20 Fidelity Investments Systems Company - Telecom=20 Phone: 617 563-2178=20 Fax: 617 385 2122=20 Mailing: 82 Devonshire St, MZ V8C=20 Boston, MA 02109-3614=20 Office: 245 Summer Street, 8th Floor=20 =20 ------_=_NextPart_002_01C5D31F.22025BAE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Folks,

Oscar and=20 I have just submitted a draft defining the conferencing roles for = XCON.  Until it appears in the = archives, you=20 can refer to the attached = document.=20

In = this draft=20 we have taken a stab at defining five roles=20 within a conference.  They are: administrator, creator, = moderator,=20 participant, and observer.  We have also written an XML=20 schema so that these role definitions can be incorporated into = other XCON drafts. 

Your=20 comments are = appreciated. We=20 hope to have discussions on this topic = on=20 the mailing list. The following = is the=20 abstract of the draft:

   This document defines the = set of=20 possible conferencing roles that are
   used to represent=20 participants within a Conference Object (as
   defined in = the XCON=20 Conference Framework [1]).  The document also
   = provides a=20 set of semantics associated with each role.  = Additional
  =20 roles may be defined in the future, as necessary, with = their
  =20 corresponding schema extensions, as appropriate.

Cheers,

Dave

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

 
------_=_NextPart_002_01C5D31F.22025BAE-- ------_=_NextPart_001_01C5D31F.22025BAE Content-Type: text/plain; name="draft-morgan-xcon-roles-00.txt" Content-Transfer-Encoding: base64 Content-Description: draft-morgan-xcon-roles-00.txt Content-Disposition: attachment; filename="draft-morgan-xcon-roles-00.txt" Content-Transfer-Encoding: base64 DQoNCg0KWENPTiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgRC4gTW9yZ2FuDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgRmlkZWxpdHkgSW52ZXN0bWVudHMNCkV4cGlyZXM6IEFwcmlsIDIw LCAyMDA2ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTy4gTm92bw0K ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgIEVyaWNzc29uDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIE9jdG9iZXIgMTcsIDIwMDUNCg0KDQogICAgICAgICAgICAgUm9sZSBE ZWZpbml0aW9ucyBmb3IgQ2VudHJhbGl6ZWQgQ29uZmVyZW5jaW5nDQogICAgICAgICAgICAgICAg ICAgICBkcmFmdC1tb3JnYW4teGNvbi1yb2xlcy0wMC50eHQNCg0KU3RhdHVzIG9mIHRoaXMgTWVt bw0KDQogICBCeSBzdWJtaXR0aW5nIHRoaXMgSW50ZXJuZXQtRHJhZnQsIGVhY2ggYXV0aG9yIHJl cHJlc2VudHMgdGhhdCBhbnkNCiAgIGFwcGxpY2FibGUgcGF0ZW50IG9yIG90aGVyIElQUiBjbGFp bXMgb2Ygd2hpY2ggaGUgb3Igc2hlIGlzIGF3YXJlDQogICBoYXZlIGJlZW4gb3Igd2lsbCBiZSBk aXNjbG9zZWQsIGFuZCBhbnkgb2Ygd2hpY2ggaGUgb3Igc2hlIGJlY29tZXMNCiAgIGF3YXJlIHdp bGwgYmUgZGlzY2xvc2VkLCBpbiBhY2NvcmRhbmNlIHdpdGggU2VjdGlvbiA2IG9mIEJDUCA3OS4N Cg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50ZXJu ZXQgRW5naW5lZXJpbmcNCiAgIFRhc2sgRm9yY2UgKElFVEYpLCBpdHMgYXJlYXMsIGFuZCBpdHMg d29ya2luZyBncm91cHMuICBOb3RlIHRoYXQNCiAgIG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0 cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzIEludGVybmV0LQ0KICAgRHJhZnRzLg0KDQogICBJ bnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxpZCBmb3IgYSBtYXhpbXVtIG9m IHNpeCBtb250aHMNCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRl ZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55DQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0 ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJlZmVyZW5jZQ0KICAgbWF0ZXJpYWwgb3IgdG8g Y2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndvcmsgaW4gcHJvZ3Jlc3MuIg0KDQogICBUaGUgbGlz dCBvZiBjdXJyZW50IEludGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAgIGh0dHA6 Ly93d3cuaWV0Zi5vcmcvaWV0Zi8xaWQtYWJzdHJhY3RzLnR4dC4NCg0KICAgVGhlIGxpc3Qgb2Yg SW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAg aHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbC4NCg0KICAgVGhpcyBJbnRlcm5ldC1EcmFm dCB3aWxsIGV4cGlyZSBvbiBBcHJpbCAyMCwgMjAwNi4NCg0KQ29weXJpZ2h0IE5vdGljZQ0KDQog ICBDb3B5cmlnaHQgKEMpIFRoZSBJbnRlcm5ldCBTb2NpZXR5ICgyMDA1KS4NCg0KQWJzdHJhY3QN Cg0KICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHRoZSBzZXQgb2YgcG9zc2libGUgY29uZmVyZW5j aW5nIHJvbGVzIHRoYXQgYXJlDQogICB1c2VkIHRvIHJlcHJlc2VudCBwYXJ0aWNpcGFudHMgd2l0 aGluIGEgQ29uZmVyZW5jZSBPYmplY3QgKGFzDQogICBkZWZpbmVkIGluIHRoZSBYQ09OIENvbmZl cmVuY2UgRnJhbWV3b3JrIFsxXSkuICBUaGUgZG9jdW1lbnQgYWxzbw0KICAgcHJvdmlkZXMgYSBz ZXQgb2Ygc2VtYW50aWNzIGFzc29jaWF0ZWQgd2l0aCBlYWNoIHJvbGUuICBBZGRpdGlvbmFsDQog ICByb2xlcyBtYXkgYmUgZGVmaW5lZCBpbiB0aGUgZnV0dXJlLCBhcyBuZWNlc3NhcnksIHdpdGgg dGhlaXINCiAgIGNvcnJlc3BvbmRpbmcgc2NoZW1hIGV4dGVuc2lvbnMsIGFzIGFwcHJvcHJpYXRl Lg0KDQoNCg0KDQpNb3JnYW4gJiBOb3ZvICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyMCwgMjAw NiAgICAgICAgICAgICAgICAgW1BhZ2UgMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAg ICAgIFJvbGVzIGluIFhDT04gICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAwNQ0KDQoNClRhYmxl IG9mIENvbnRlbnRzDQoNCiAgIDEuICBJbnRyb2R1Y3Rpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAu IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMw0KICAgMi4gIFRlcm1pbm9sb2d5ICAuIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzDQogICAzLiAg T3ZlcnZpZXcgb2YgUm9sZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gIDMNCiAgICAgMy4xLiAgUm9sZXMgaW4gdGhlIENvbmZlcmVuY2UgVGVtcGxhdGUgLiAu IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNA0KICAgICAzLjIuICBSb2xlcyBpbiB0aGUgQ29tbW9u IENvbmZlcmVuY2UgRGF0YSBNb2RlbCAgLiAuIC4gLiAuIC4gLiAuICA0DQogICA0LiAgUm9sZSBE ZWZpbml0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g IDUNCiAgICAgNC4xLiAgQWRtaW5pc3RyYXRvciAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu IC4gLiAuIC4gLiAuIC4gLiAgNQ0KICAgICA0LjIuICBDcmVhdG9yICAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1DQogICAgIDQuMy4gIE1vZGVyYXRv ciAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDUNCiAg ICAgNC40LiAgUGFydGljaXBhbnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu IC4gLiAuIC4gLiAgNg0KICAgICA0LjUuICBPYnNlcnZlciAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA2DQogICA1LiAgUm9sZXMgaW4gYSBGbG9vciAu IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDYNCiAgIDYuICBD aGFuZ2luZyBSb2xlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu IC4gLiAgNw0KICAgNy4gIFhNTCBTY2hlbWEgRGVmaW5pdGlvbiAgLiAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuICA3DQogICA4LiAgRXh0ZW5zaWJpbGl0eSBvZiB0aGUgU2No ZW1hICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDgNCiAgIDkuICBTZWN1cml0 eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg OA0KICAgMTAuIElBTkEgQ29uc2lkZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gLiAuIC4gLiAuICA4DQogICAxMS4gQWNrbm93bGVkZ2VtZW50cyAuIC4gLiAuIC4gLiAu IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkNCiAgIDEyLiBSZWZlcmVuY2VzIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgOQ0KICAg ICAxMi4xLiBOb3JtYXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g LiAuIC4gLiAuICA5DQogICAgIDEyLjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAu IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkNCiAgIEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4g LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMQ0KICAgSW50ZWxs ZWN0dWFsIFByb3BlcnR5IGFuZCBDb3B5cmlnaHQgU3RhdGVtZW50cyAuIC4gLiAuIC4gLiAuIC4g LiAuIDEyDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN Cg0KTW9yZ2FuICYgTm92byAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMjAsIDIwMDYgICAgICAg ICAgICAgICAgIFtQYWdlIDJdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBSb2xl cyBpbiBYQ09OICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMDUNCg0KDQoxLiAgSW50cm9kdWN0 aW9uDQoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0aGUgc2V0IG9mIHBvc3NpYmxlIGNvbmZl cmVuY2luZyByb2xlcyB0aGF0IGFyZQ0KICAgdXNlZCB0byByZXByZXNlbnQgcGFydGljaXBhbnRz IHdpdGhpbiBhIENvbmZlcmVuY2UgT2JqZWN0IChhcw0KICAgZGVmaW5lZCBpbiB0aGUgWENPTiBD b25mZXJlbmNlIEZyYW1ld29yayBbMV0pLiAgVGhlIGRvY3VtZW50IGFsc28NCiAgIHByb3ZpZGVz IGEgc2V0IG9mIHNlbWFudGljcyBhc3NvY2lhdGVkIHdpdGggZWFjaCByb2xlLiAgQWRkaXRpb25h bA0KICAgcm9sZXMgbWF5IGJlIGRlZmluZWQgaW4gdGhlIGZ1dHVyZSwgYXMgbmVjZXNzYXJ5LCB3 aXRoIHRoZWlyDQogICBjb3JyZXNwb25kaW5nIHNjaGVtYSBleHRlbnNpb25zLCBhcyBhcHByb3By aWF0ZS4NCg0KICAgQSBDb25mZXJlbmNlIE1lZGlhIHRlbXBsYXRlIFs2XSBzcGVjaWZpZXMgd2hp Y2ggcm9sZXMgYXJlIGF2YWlsYWJsZQ0KICAgaW4gYSBDb25mZXJlbmNlIE9iamVjdCwgaW5jbHVk aW5nIHRoZSBtYXhpbXVtIG51bWJlciBvZiBvY2N1cnJlbmNlDQogICBwZXJtaXR0ZWQgZm9yIGVh Y2ggcm9sZS4gIEEgbWVkaWEgdGVtcGxhdGUgYWxzbyBkZWZpbmVzIHByb3BlcnRpZXMNCiAgIHN1 Y2ggYXMgZGVmYXVsdCB2YWx1ZXMgZm9yIGVhY2ggcm9sZSwgdGhlIGNvbmZlcmVuY2UgY29udHJv bHMNCiAgIGF2YWlsYWJsZSB0byBlYWNoIHJvbGUgYW5kIGhvdyB0aGV5IG1heSBiZSBtYW5pcHVs YXRlZCwgYW5kIHdoaWNoDQogICBtZWRpYSBzdHJlYW1zICh3aXRoIGFzc29jaWF0ZWQgcHJvcGVy dGllcykgYXJlIGFzc29jaWF0ZWQgd2l0aCBlYWNoDQogICByb2xlLg0KDQoNCjIuICBUZXJtaW5v bG9neQ0KDQogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwg IlNIQUxMIiwgIlNIQUxMDQogICBOT1QiLCJTSE9VTEQiLCAiU0hPVUxEIE5PVCIsICJSRUNPTU1F TkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbg0KICAgdGhpcyBkb2N1bWVudCBhcmUgdG8g YmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFJGQy0yMTE5IFsyXS4NCg0KDQozLiAgT3Zl cnZpZXcgb2YgUm9sZXMNCg0KICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIGZpdmUgbG9naWNhbCBy b2xlcyB0aGF0IGEgQ29uZmVyZW5jZSBTeXN0ZW0NCiAgIHNob3VsZCBhc3N1bWUgYXJlIGF2YWls YWJsZSBpbiBhIENvbmZlcmVuY2UgT2JqZWN0LiAgSW4gaGllcmFyY2hpY2FsDQogICBvcmRlciB0 aGV5IGFyZTogImFkbWluaXN0cmF0b3IiLCAiY3JlYXRvciIsICJtb2RlcmF0b3IiLA0KICAgInBh cnRpY2lwYW50IiwgYW5kICJvYnNlcnZlciIuICBUaGVzZSBmaXZlIHJvbGVzIGFyZSBzdWZmaWNp ZW50IHRvDQogICBkZWxpbmVhdGUgdGhlIHZhcmlvdXMgcHJpdmlsZWdlcyB0aGF0IGNvbmZlcmVu Y2UgYXR0ZW5kZWVzIG5lZWQgaW4gYQ0KICAgdmFyaWV0eSBvZiBjb25mZXJlbmNlIHNjZW5hcmlv cyBbM10uICBUaGUgc3BlY2lmaWMgbWVkaWEgY2FwYWJpbGl0aWVzDQogICBvZiBlYWNoIHJvbGUg YXJlIGRlZmluZWQgaW4gdGhlIGNvbmZlcmVuY2UgdGVtcGxhdGUgWzZdLiAgSXQgc2hvdWxkDQog ICBiZSBub3RlZCB0aGF0IGFsbCBmaXZlIHJvbGVzIG5lZWQgbm90IGJlIHNwZWNpZmllZCBvciBw cmVzZW50IGluIHRoZQ0KICAgY29uZmVyZW5jZSB0ZW1wbGF0ZSBidXQgU0hPVUxEIGJlIHN1cHBv cnRlZCBieSB0aGUgQ29uZmVyZW5jZSBTeXN0ZW0uDQogICBBIENvbmZlcmVuY2UgU3lzdGVtIE1B WSBjaG9vc2Ugbm90IHRvIHN1cHBvcnQgYSBwYXJ0aWN1bGFyIHJvbGUgaWYgaXQNCiAgIGNhbiB1 bmVxdWl2b2NhbGx5IGRlY2lkZSB0aGF0IHRoZSByb2xlIHdpbGwgbm90IGJlIHJlcXVpcmVkIGlu IGFueSBvZg0KICAgdGhlIHRlbXBsYXRlcyBzdXBwb3J0ZWQuDQoNCiAgIFRoZXNlIGZpdmUgcm9s ZXMgaGF2ZSBhbiBpbnRyaW5zaWMgaGllcmFyY2hpY2FsIG9yZGVyIHdpdGhpbiBhDQogICBzcGVj aWZpYyBjb25mZXJlbmNlLiAgQnkgaGllcmFyY2hpY2FsIG9yZGVyLCBpdCBpcyBpbXBsaWVkIHRo YXQgdGhlDQogICAiYWRtaW5pc3RyYXRvciIgYnkgZGVmYXVsdCBzaG91bGQgaGF2ZSBoaWdoZXIg cHJpdmlsZWdlcyB0aGFuIGENCiAgICJjcmVhdG9yIiwgd2hpY2ggYnkgZGVmYXVsdCBzaG91bGQg aGF2ZSBoaWdoZXIgcHJpdmlsZWdlcyB0aGFuIGENCiAgICJtb2RlcmF0b3IiIGFuZCBzbyBvbi4g IEZvciBleGFtcGxlLCB0aGUgImFkbWluaXN0cmF0b3IiIHNob3VsZCBoYXZlDQogICB0aGUgYWJp bGl0eSB0byBtYWtlIGNoYW5nZXMgdG8gYWxsIGNvbmZlcmVuY2UgdmFyaWFibGVzIGR1cmluZw0K ICAgaW5zdGFudGlhdGlvbiBhbmQgZnVsbCBsaWZlY3ljbGUgb2YgdGhlIENvbmZlcmVuY2UgT2Jq ZWN0LiAgVGhlDQogICAiY3JlYXRvciIgaXMgdGhlICdvd25lcicgb2YgdGhlIGNvbmZlcmVuY2Ug YW5kIGhhcyB2YXJpb3VzIHByaXZpbGVnZXMNCg0KDQoNCk1vcmdhbiAmIE5vdm8gICAgICAgICAg ICBFeHBpcmVzIEFwcmlsIDIwLCAyMDA2ICAgICAgICAgICAgICAgICBbUGFnZSAzXQ0KDA0KSW50 ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgUm9sZXMgaW4gWENPTiAgICAgICAgICAgICAgICAg T2N0b2JlciAyMDA1DQoNCg0KICAgd2hpY2ggc2hvdWxkIGFsbG93IHRoZW0gdG8gbW9kaWZ5IHRo ZSBjb25mZXJlbmNlIHZhcmlhYmxlcyB1cCB0byB0aGUNCiAgIHRpbWUgdGhlIGNvbmZlcmVuY2Ug aXMgaW5zdGFudGlhdGVkLiAgVGhlICJtb2RlcmF0b3IiIGlzIGEgbG9naWNhbA0KICAgZW50aXR5 IHRoYXQgd2lsbCBtYW5hZ2UgdGhlIGNvbmZlcmVuY2UuICBUaGUgInBhcnRpY2lwYW50IiBpcyBh DQogICBsb2dpY2FsIGVudGl0eSB3aXRoIGdlbmVyaWMgcHJpdmlsZWdlcyB0aGF0IHdpbGwgYmUg YXR0ZW5kaW5nIGENCiAgIGNvbmZlcmVuY2UuICBUaGUgIm9ic2VydmVyIiBpcyBhIGxvZ2ljYWwg ZW50aXR5IHdoaWNoIGNhbiBvbmx5DQogICByZWNlaXZlIG1lZGlhIHN0cmVhbXMgZnJvbSB0aGUg Y29uZmVyZW5jZS4gIEFsbCBjb25mZXJlbmNlIHRlbXBsYXRlcw0KICAgbXVzdCBoYXZlIGEgcm9s ZSBkZWZpbmVkIGFzICJwYXJ0aWNpcGFudCIuDQoNCiAgIEVhY2ggdXNlciBwYXJ0aWNpcGF0aW5n IGluIGEgY29uZmVyZW5jZSBpbnN0YWNlIGlzIGFuIGVudGl0eSB0aGF0IGNhbg0KICAgYXNzdW1l IG9uZSBvciBtb3JlIHJvbGVzLiAgQW55IGVudGl0eSBjYW4gYmUgYWxsb2NhdGVkIHRvIGFuDQog ICBhcHByb3BpYXRlZCBsb2dpY2FsIHJvbGUuICBBIHJvbGUgY2FuIGFsc28gYmUgYXNzdW1lZCBp biBjb25qdW5jdGlvbg0KICAgd2l0aCB0aGUgdXNlcnMgaWRlbnRpdHkgd2l0aGluIHRoZSBDb25m ZXJlbmNlIFN5c3RlbSBhcyBhIHJlc3VsdCBvZg0KICAgYW4gaWRlbnRpdHkgYXNzZXJ0aW9uIHRy YW5zYWN0aW9uIG9uIHRoZSBDb25mZXJlbmNlIFN5c3RlbS4gIElmIG5vDQogICByb2xlcyBhcmUg ZGVmaW5lZCBmb3IgYW4gZW50aXR5LCB0aGV5IHNob3VsZCBieSBkZWZhdWx0IGJlIGENCiAgICJw YXJ0aWNpcGFudCIgYnV0IGxvY2FsIHBvbGljeSBtYXkgZGVmaW5lIGFuIGFsdGVybmF0aXZlLg0K DQozLjEuICBSb2xlcyBpbiB0aGUgQ29uZmVyZW5jZSBUZW1wbGF0ZQ0KDQogICBXaGVuIHRoZSA8 cm9sZT4gZWxlbWVudCBpcyBkZWZpbmVkIGluIHRoZSAiTWVkaWEgUG9saWN5IFRlbXBsYXRlIGZv cg0KICAgWENPTiIgWzZdLCBpdCB3aWxsIGhhdmUgYSBzZXQgb2YgY2hpbGQgZWxlbWVudHMgdGhh dCB3aWxsIHNwZWNpZnkgdGhlDQogICBtZWRpYSBjYXBhYmlsaXRpZXMgYXZhaWxhYmxlIHRvIGEg bG9naWNhbCBlbnRpdHkgaW4gdGhhdCByb2xlLiAgVGhlc2UNCiAgIGNhcGFiaWxpdGllcyBhcmUg Y29sbGVjdGl2ZWx5IHJlZmVycmVkIHRvIGFzICJwcml2aWxlZ2VzIiBhbmQgY29uc2lzdA0KICAg b2YgYSBudW1iZXIgb2YgY29udHJvbHMgYW5kIHBhcmFtZXRlcnMuICBGb3IgZXhhbXBsZSwgdGhl IGNvbmZlcmVuY2UNCiAgICJtb2RlcmF0b3IiIG1heSBoYXZlIHByaXZpbGVnZXMgdGhhdCBhbGxv dyB0aGVtIHRvIGVpdGhlciBtdXRlIG9yDQogICByZW1vdmUgYSAicGFydGljaXBhbnQiLg0KDQog ICBUaGUgPHJvbGU+IGVsZW1lbnQgTVVTVCBoYXZlIGFuIGF0dHJpYnV0ZSBjYWxsZWQgJ25hbWUn LiAgVGhlICduYW1lJw0KICAgTVVTVCBiZSBvbmUgb2YgdGhlIGNvbmZlcmVuY2Ugcm9sZXMgZGVm aW5lZCBpbiB0aGlzIHNwZWNpZmljYXRpb24gb3INCiAgIGFuIGFwcHJvcHJpYXRlIGV4dGVuc2lv biwgc3BlY2lmaWNhbGx5IGl0IGhhcyB0byBiZSBvZiB0eXBlDQogICAiYWRtaW5pc3RyYXRvciIs ICJjcmVhdG9yIiwgIm1vZGVyYXRvciIsICJwYXJ0aWNpcGFudCIsIG9yDQogICAib2JzZXJ2ZXIi Lg0KDQogICBUaGUgPHJvbGU+IGVsZW1lbnQgTUFZIGhhdmUgPHBhcmFtZXRlcj4sIDxjb250cm9s PiBhbmQgPHN0cmVhbT4gY2hpbGQNCiAgIGVsZW1lbnRzIChhbW9uZyBvdGhlcnMpIHNwZWNpZmll ZCBpbiB0aGUgY29uZmVyZW5jZSB0ZW1wbGF0ZSBbNl0uDQogICBUaGUgPHN0cmVhbT4gZWxlbWVu dCBkZWZpbmVzIHRoZSBtZWRpYSBzdHJlYW1zIGF2YWlsYWJsZSBpbiB0aGF0DQogICByb2xlLiAg VGhlIDxyb2xlPiBjYW4gaGF2ZSBvbmUgb3IgbW9yZSBtZWRpYSBzdHJlYW1zIGF2YWlsYWJsZS4g IEVhY2gNCiAgIDxzdHJlYW0+IGVsZW1lbnQgTUFZIGNvbnRhaW4gYSBjaGlsZCBlbGVtZW50IGNh bGxlZCB0aGUgPGZsb29yPiB0aGF0DQogICBzcGVjaWZpZXMgYSBjb25mZXJlbmNlIGZsb29yIHdo aWNoIGNhbiBiZSBjb250cm9sbGVkIGJ5IGEgZmxvb3IgY2hhaXINCiAgIGluIHRoZSBjb25mZXJl bmNlIFs3XS4gIFRoZSByb2xlIGNhbiBoYXZlIG9uZSBvciBtb3JlIGFjdGl2ZSBmbG9vcnMuDQog ICBUeXBpY2FsbHkgdGhlICJtb2RlcmF0b3IiIHJvbGUgY29udGFpbnMgYSBkZWZpbml0aW9uIG9m IHRoZSBhY3RpdmUNCiAgIGZsb29ycy4NCg0KMy4yLiAgUm9sZXMgaW4gdGhlIENvbW1vbiBDb25m ZXJlbmNlIERhdGEgTW9kZWwNCg0KICAgVGhlIDxyb2xlcz4gZWxlbWVudCBpbiB0aGUgIkNvbW1v biBDb25mZXJlbmNlIEluZm9ybWF0aW9uIERhdGEgTW9kZWwNCiAgIGZvciBDZW50cmFsaXplZCBD b25mZXJlbmNpbmciIFs4XSBpcyBhIGNoaWxkIGVsZW1lbnQgb2YgdGhlIDx1c2VyPg0KICAgZWxl bWVudC4gIEl0IHNwZWNpZmllcyB0aGUgcm9sZXMgb2YgYSB1c2VyIGFuZCBpdCBNQVkgY29udGFp biBhIGNoaWxkDQogICBlbGVtZW50IGNhbGxlZCB0aGUgPGRlc2NyaXB0aW9uPiB0aGF0IGlzIGEg c2V0IG9mIGh1bWFuIHJlYWRhYmxlDQoNCg0KDQpNb3JnYW4gJiBOb3ZvICAgICAgICAgICAgRXhw aXJlcyBBcHJpbCAyMCwgMjAwNiAgICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwNCkludGVybmV0 LURyYWZ0ICAgICAgICAgICAgICAgIFJvbGVzIGluIFhDT04gICAgICAgICAgICAgICAgIE9jdG9i ZXIgMjAwNQ0KDQoNCiAgIHN0cmluZ3MgdGhhdCBkZXNjcmliZXMgdGhhdCByb2xlIGluIHRoZSBj b25mZXJlbmNlLiAgRm9yIGV4YW1wbGUsIGl0DQogICBtYXkgY29udGFpbiBpbmZvcm1hdGlvbiBy ZWdhcmRpbmcgdGhlIGNvbmZlcmVuY2UgYWRtaW5pc3RyYXRvciBhbmQNCiAgIHRoZSBiZXN0IHdh eSB0byBjb21tdW5pY2F0ZSB3aXRoIHRoZW0gb3IgaXQgbWF5IGNvbnRhaW4gaW5zdHJ1Y3Rpb25z DQogICBzdWNoIGFzIGNvbmZlcmVuY2UgcmVjb3JkaW5nICh0aGUgYWRkaXRpb24gb2YgYW4gb2Jz ZXJ2ZXIpIGNhbiBvbmx5DQogICBiZSBlbmFibGVkIGJ5IGNvbnRhY3RpbmcgdGhlIGFkbWluaXN0 cmF0b3IgYW5kIHJlcXVlc3RpbmcgdGhhdCBhDQogICBzZXJ2aWNlLXVyaSBiZSBhZGRlZCB0byB0 aGUgY29uZmVyZW5jZS4NCg0KDQo0LiAgUm9sZSBEZWZpbml0aW9ucw0KDQogICBUaGlzIHNlY3Rp b24gZGVmaW5lcyB0aGUgZGlmZmVyZW50IHR5cGVzIG9mIHJvbGVzIGluIGEgY29uZmVyZW5jZQ0K ICAgc3lzdGVtLg0KDQo0LjEuICBBZG1pbmlzdHJhdG9yDQoNCiAgIFRoZSBhZG1pbmlzdHJhdG9y IHJvbGUgaXMgdHlwaWNhbGx5IHRoZSBzeXN0ZW0gYWRtaW5pc3RyYXRvciBvZiB0aGUNCiAgIENv bmZlcmVuY2UgU3lzdGVtLiAgQnkgZGVmYXVsdCwgc29tZW9uZSBpbiB0aGlzIHJvbGUgU0hPVUxE IGhhdmUgdGhlDQogICBhYmlsaXR5IHRvIHJlYWQgb3IgbW9kaWZ5IGFsbCBjb25mZXJlbmNlIGVs ZW1lbnRzLiAgQWxsIGNvbmZlcmVuY2VzDQogICBTSE9VTEQgc3BlY2lmeSBhbiAiYWRtaW5pc3Ry YXRvciIuDQoNCjQuMi4gIENyZWF0b3INCg0KICAgVGhlIHJvbGUgb2YgImNyZWF0b3IiIGlzIHVz ZWQgdG8gaWRlbnRpZnkgdGhlIGxvZ2ljYWwgZW50aXR5IHRoYXQNCiAgIGNyZWF0ZWQgdGhlIGNv bmZlcmVuY2UuICBUaGUgY29uZmVyZW5jZSBjcmVhdG9yIGlzIHRoZSAnb3duZXInIG9mIHRoZQ0K ICAgY29uZmVyZW5jZSBhbmQgaGFzIHZhcmlvdXMgcHJpdmlsZWdlcyB3aGljaCBTSE9VTEQgYWxs b3cgdGhlbSB0bw0KICAgbW9kaWZ5IHRoZSBjb25mZXJlbmNlIHZhcmlhYmxlcyB1cCB0byB0aGUg dGltZSB0aGUgY29uZmVyZW5jZSBpcw0KICAgaW5zdGFudGlhdGVkLg0KDQogICBJbiB0aGUgY2Fz ZSBvZiBhbiBhZC1ob2MgY29uZmVyZW5jZSwgYWxzbyBrbm93biBhcyBhIHJlc2VydmF0aW9ubGVz cw0KICAgb3Igb24tZGVtYW5kIGNvbmZlcmVuY2UsIHRoZXJlIG1heSBiZSBubyBjb25mZXJlbmNl IGNyZWF0b3IsIG9yIHRoZQ0KICAgY29uZmVyZW5jZSBjcmVhdG9yIG1heSBiZSBzcGVjaWZpZWQg YXMgdGhlIGNvbmZlcmVuY2UgZm9jdXMuDQoNCiAgIFRoZSBjb25mZXJlbmNlIGNyZWF0b3IgZG9l cyBub3QgbmVjZXNzYXJpbHkgaGF2ZSB0byBhdHRlbmQgdGhlDQogICBtZWV0aW5nLiAgVGhleSBj b3VsZCBiZSBhIHNlY3JldGFyeSB0aGF0IHNldHMgdXAgdGhlIG1lZXRpbmcuDQoNCiAgIFdoZW4g dGhlIGNvbmZlcmVuY2UgY3JlYXRvciBhdHRlbmRzIHRoZSBtZWV0aW5nLCB0aGUgaGllcmFyY2hp Y2FsDQogICBuYXR1cmUgb2YgdGhlIHJvbGUgdHlwZXMgd2lsbCBhbGxvdyB0aGUgImNyZWF0b3Ii IHRvIGhhdmUgYWxsIHRoZQ0KICAgcHJpdmlsZWdlcyBvZiB0aGUgIm1vZGVyYXRvciIuDQoNCjQu My4gIE1vZGVyYXRvcg0KDQogICBUaGUgcm9sZSBvZiAibW9kZXJhdG9yIiBpcyB1c2VkIHRvIGlk ZW50aWZ5IHRoZSBsb2dpY2FsIGVudGl0eSB0aGF0DQogICB3aWxsIG1hbmFnZSB0aGUgY29uZmVy ZW5jZS4gIFRoZSAibW9kZXJhdG9yIiBpcyBpbiBlc3NlbmNlIHRoZQ0KICAgJ2ZhY2lsaXRhdG9y JyBvZiB0aGUgY29uZmVyZW5jZS4NCg0KICAgVGhlICJtb2RlcmF0b3IiIGlzIGFuIE9QVElPTkFM IHJvbGUsIGJ1dCBpZiBzcGVjaWZpZWQgaW4gdGhlDQogICBjb25mZXJlbmNlIHRlbXBsYXRlLCB0 aGUgIm1vZGVyYXRvciIgU0hPVUxEIGF0dGVuZCB0aGUgbWVldGluZy4NCg0KDQoNCg0KTW9yZ2Fu ICYgTm92byAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMjAsIDIwMDYgICAgICAgICAgICAgICAg IFtQYWdlIDVdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBSb2xlcyBpbiBYQ09O ICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMDUNCg0KDQogICBUaGVyZSBtYXkgYmUgbXVsdGlw bGUgbW9kZXJhdG9ycyBpbiBhIGNvbmZlcmVuY2UuICBGb3IgZXhhbXBsZSwgYQ0KICAgY29uZmVy ZW5jZSBtYXkgaGF2ZSB0d28gbW9kZXJhdG9yczogb25lIGNvbnRyb2xsaW5nIHdobyBjYW4gdGFs ayBhdCBhDQogICBwYXJ0aWN1bGFyIHRpbWUgYW5kIGFub3RoZXIgY29udHJvbGxpbmcgd2hvIGNh biB3cml0ZSBvbiBhIHNoYXJlZA0KICAgd2hpdGVib2FyZC4NCg0KNC40LiAgUGFydGljaXBhbnQN Cg0KICAgVGhlIHJvbGUgb2YgInBhcnRpY2lwYW50IiBpcyB1c2VkIHRvIGlkZW50aWZ5IGEgbG9n aWNhbCBlbnRpdHkgd2l0aA0KICAgZ2VuZXJpYyBwcml2aWxlZ2VzIHRoYXQgd2lsbCBiZSBwYXJ0 aWNpcGF0aW5nIGluIGEgQ29uZmVyZW5jZQ0KICAgSW5zdGFuY2UuICBUaGUgInBhcnRpY2lwYW50 IiBpcyBpbiBlc3NlbmNlIGFuICdhdHRlbmRlZScgdG8gdGhlDQogICBjb25mZXJlbmNlLg0KDQog ICBUaGUgInBhcnRpY2lwYW50IiBpcyBhIG1hbmRhdG9yeSByb2xlLCBhbmQgTVVTVCBiZSBkZWZp bmVkIGluIHRoZQ0KICAgY29uZmVyZW5jZSB0ZW1wbGF0ZS4gIFRoZXJlIFNIT1VMRCBiZSBiYXNp YyBsZXZlbHMgb2YgbWVkaWEgc3RyZWFtcw0KICAgYW5kIHRoZWlyIGFzc29jaWF0ZWQgc3RyZWFt LXR5cGVzIGRlZmluZWQgZm9yIHRoZSByb2xlIG9mDQogICAicGFydGljaXBhbnQiLg0KDQogICBU aGVyZSBNQVkgYmUgbXVsdGlwbGUgcGFydGljaXBhbnRzIGluIGEgY29uZmVyZW5jZS4NCg0KNC41 LiAgT2JzZXJ2ZXINCg0KICAgVGhlIHJvbGUgb2YgIm9ic2VydmVyIiBpcyB1c2VkIHRvIGlkZW50 aWZ5IGEgbG9naWNhbCBlbnRpdHkgd2hpY2ggY2FuDQogICBvbmx5IHJlY2VpdmUgbWVkaWEgc3Ry ZWFtcyBmcm9tIHRoZSBjb25mZXJlbmNlLiAgVGhlICJvYnNlcnZlciIgaXMgaW4NCiAgIGVzc2Vu Y2UgYSAnbGlzdGVuZXInIHRvIHRoZSBjb25mZXJlbmNlLiAgQW4gb2JzZXJ2ZXIgY291bGQgYmUg YQ0KICAgcGVyc29uIChzdXBlcnZpc29yKSBvciBhIG1hY2hpbmUgKGNhbGwgbG9nZ2VyIG9yIHJl Y29yZGluZyBkZXZpY2UpLg0KDQogICBUaGUgIm9ic2VydmVyIiBpcyBhbiBPUFRJT05BTCByb2xl LCBidXQgdGhlcmUgbWF5IGJlIG11bHRpcGxlDQogICBvYnNlcnZlcnMgaW4gYSBjb25mZXJlbmNl LiAgVGhlICJvYnNlcnZlciIgb25seSByZWNlaXZlcyBpbnB1dCBtZWRpYQ0KICAgc3RyZWFtcyBh bmQgTVVTVCBOT1QgZ2VuZXJhdGUgb3V0cHV0IHN0cmVhbXMuDQoNCg0KNS4gIFJvbGVzIGluIGEg Rmxvb3INCg0KICAgRmxvb3IgY29udHJvbCBpbiBjZW50cmFsaXplZCBjb25mZXJlbmNpbmcgaXMg aW50cm9kdWNlZCBpbiB0aGUgWENPTg0KICAgRnJhbWV3b3JrIERvY3VtZW50IFsxXSBhbmQgZGVz Y3JpYmVkIGluIGZ1cnRoZXIgZGV0YWlsIGluIHRoZSBCaW5hcnkNCiAgIEZsb29yIENvbnRyb2wg UHJvdG9jb2wgKEJGQ1ApIFs3XS4gIEZsb29ycyBjYW4gYmUgc3BlY2lmaWVkIGluIHRoZQ0KICAg Y29uZmVyZW5jZSB0ZW1wbGF0ZSBbNl0gb3IgY3JlYXRlZCBkeW5hbWljYWxseS4gIFVzZXJzIGNh biBiZSBhZGRlZA0KICAgb3IgZGVsZXRlZCBmcm9tIGEgZmxvb3Igd2hlbiB0aGUgY29uZmVyZW5j ZSBpcyBhY3RpdmUuDQoNCiAgIEEgZmxvb3IgY2hhaXIgaXMgYSBsb2dpY2FsIGVudGl0eSB0aGF0 IG1hbmFnZXMgYSBmbG9vciAoZ3JhbnRzLA0KICAgZGVuaWVzLCBvciByZXZva2VzIGEgZmxvb3Ip LiAgVGhlIGZsb29yIGNoYWlyIGlzIHVzdWFsbHkgaW4gYW4NCiAgICJhZG1pbmlzdHJhdG9yIiwg Im1vZGVyYXRvciIsIG9yICJjcmVhdG9yIiByb2xlLiAgQSBmbG9vciBwYXJ0aWNpcGFudA0KICAg aXMgYSBsb2dpY2FsIGVudGl0eSB0aGF0IHJlcXVlc3RzIGZsb29ycywgYW5kIHBvc3NpYmx5IGlu Zm9ybWF0aW9uDQogICBhYm91dCB0aGVtIGZyb20gYSBmbG9vciBjb250cm9sIHNlcnZlci4gIFRo ZXkgYXJlIHVzdWFsbHkgaW4gYQ0KICAgInBhcnRpY2lwYW50IiBvciBldmVuIGEgIm1vZGVyYXRv ciIgcm9sZSBbN10uDQoNCiAgIEluIHRoZSBjb25mZXJlbmNlIHNjZW5hcmlvcyBbM10sIHRoZSAn bGVjdHVyZXInIGlzIHNlZW4vaGVhcmQgYnkgdGhlDQogICBjb25mZXJlbmNlIHBhcnRpY2lwYW50 cyBhbmQgb2Z0ZW4gc2hhcmVzIGEgcHJlc2VudGF0aW9uIG9yDQoNCg0KDQpNb3JnYW4gJiBOb3Zv ICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyMCwgMjAwNiAgICAgICAgICAgICAgICAgW1BhZ2Ug Nl0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIFJvbGVzIGluIFhDT04gICAgICAg ICAgICAgICAgIE9jdG9iZXIgMjAwNQ0KDQoNCiAgIGFwcGxpY2F0aW9uIHdpdGggdGhlIG90aGVy IHBhcnRpY2lwYW50cy4gIEEgJ2xlY3R1cmVyJyBpcyBhIGxvZ2ljYWwNCiAgIGVudGl0eSB0aGF0 IGhhcyBiZWVuIGdyYW50ZWQgdGhlIGZsb29yIHdpdGhpbiBhIGNvbmZlcmVuY2UgYnkgdGhlDQog ICBmbG9vciBjaGFpci4gIEl0IGNhbiBiZSB0aGUgImFkbWluaXN0cmF0b3IiLCAibW9kZXJhdG9y IiwNCiAgICJwYXJ0aWNpcGFudCIsIG9yICJtb2RlcmF0b3IiIHJvbGUgaW4gdGhlIGNvbmZlcmVu Y2UuICBUaGUgJ2xlY3R1cmVyJw0KICAgTUFZIGFsc28gYmUgcmVmZXJyZWQgdG8gYXMgYSAncHJl c2VudGVyJy4NCg0KICAgVXNlcnMgaW4gYSBjb25mZXJlbmNlIE1BWSBhc3N1bWUgZGlmZmVyZW50 IHJvbGVzIGluIGRpZmZlcmVudCBmbG9vcnMuDQogICBUaGV5IE1BWSBhbHNvIGFzc3VtZSBkaWZm ZXJlbnQgcm9sZXMgaW4gdGhlIHNhbWUgZmxvb3IsIGFzIGZsb29yDQogICB0cmFuc2FjdGlvbnMg YXJlIHByb2Nlc3NlZC4NCg0KDQo2LiAgQ2hhbmdpbmcgUm9sZXMNCg0KICAgQXMgbWVudGlvbmVk IHByZXZpb3VzbHksIHVzZXJzIGNhbiBjaGFuZ2Ugcm9sZXMgZHVyaW5nIGEgY29uZmVyZW5jZS4N CiAgIFRoaXMgY2FuIGJlIGRvbmUgaW4gb25lIG9mIHR3byB3YXlzLiAgRmlyc3QsIHRoZSB1c2Vy IGNhbiBqb2luIGEgbmV3DQogICBmbG9vciBpbiBhIGRpZmZlcmVudCByb2xlLiAgU2Vjb25kLCBh biAiYWRtaW5pc3RyYXRvciIgY2FuDQogICBkeW5hbWljYWxseSBjaGFuZ2UgdGhhdCB1c2VyJ3Mg cm9sZS4gIFRoaXMgY2FuIGJlIGFjY29tcGxpc2hlZCBiZWZvcmUNCiAgIHRoZSBjb25mZXJlbmNl IGlzIGluc3RhbnRpYXRlZCwgb3IgZHVyaW5nIHRoZSBjb25mZXJlbmNlLCB1c2luZyBhbg0KICAg YXBwcm9wcmlhdGUgY29uZmVyZW5jZSBjb250cm9sIHByb3RvY29sIFs5XSwgWzEwXS4gIEEgbG9n aWNhbCBlbnRpdHkNCiAgIHdob3NlIHJvbGUgaGFzIGJlZW4gY2hhbmdlZCB3aWxsIHR5cGljYWxs eSBoYXZlIGFjY2VzcyB0byB0aGUgbWVkaWENCiAgIHN0cmVhbXMgYXNzb2NpYXRlZCB3aXRoIHRo YXQgcm9sZS4NCg0KICAgSXQgc2hvdWxkIGJlIG5vdGVkIHRoYXQgd2hlbiBhIGxvZ2ljYWwgZW50 aXR5IGlzIGdyYW50ZWQgdGhlIGZsb29yIGluDQogICBhbiBhY3RpdmUgY29uZmVyZW5jZSwgdGhl aXIgcm9sZSBkb2VzIG5vdCBjaGFuZ2UuICBBIHVzZXIncyByb2xlIGFsc28NCiAgIGRvZXMgbm90 IGNoYW5nZSB3aGVuIHRoZXkgYXJlIGVpdGhlciBncmFudGVkIGNvbmZlcmVuY2UgY29udHJvbHMs IG9yDQogICBjb25mZXJlbmNlIGNvbnRyb2xzIGFyZSBlbmFibGVkIGJ5IHRoZSAiYWRtaW5pc3Ry YXRvciIgb3IgIm1vZGVyYXRvciINCiAgIHdoaWxlIHRoZSBjb25mZXJlbmNlIGlzIGFjdGl2ZS4N Cg0KDQo3LiAgWE1MIFNjaGVtYSBEZWZpbml0aW9uDQoNCiAgIFRoaXMgc2VjdGlvbiBwcm92aWRl cyB0aGUgWE1MIHNjaGVtYSBkZWZpbml0aW9uIGZvciB0eXBlICdyb2xlLXR5cGUnLg0KICAgVGhp cyBzY2hlbWEgd2lsbCBiZSBjYWxsZWQgcm9sZS1zY2hlbWEueHNkLg0KDQoNCiAgIDx4czpzY2hl bWEgdGFyZ2V0TmFtZXNwYWNlPSJ1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOnJvbGUtc2NoZW1hIjsN CiAgICB4bWxucz0iIHVybjppZXRmOnBhcmFtczp4bWw6bnM6cm9sZS1zY2hlbWEiOw0KICAgIHht bG5zOnhzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYSI7Pg0KDQogICAgPHhzOnNp bXBsZVR5cGUgbmFtZT0icm9sZS10eXBlIj4NCiAgICAgICA8eHM6cmVzdHJpY3Rpb24gYmFzZT0i eHM6c3RyaW5nIj4NCiAgICAgICAgIDx4czplbnVtZXJhdGlvbiB2YWx1ZT0iQWRtaW5pc3RyYXRv ciIvPg0KICAgICAgICAgPHhzOmVudW1lcmF0aW9uIHZhbHVlPSJDcmVhdG9yIi8+DQogICAgICAg ICA8eHM6ZW51bWVyYXRpb24gdmFsdWU9Ik1vZGVyYXRvciIvPg0KICAgICAgICAgPHhzOmVudW1l cmF0aW9uIHZhbHVlPSJQYXJ0aWNpcGFudCIvPg0KICAgICAgICAgPHhzOmVudW1lcmF0aW9uIHZh bHVlPSJPYnNlcnZlciIvPg0KICAgICAgIDwveHM6cmVzdHJpY3Rpb24+DQogICAgPC94czpzaW1w bGVUeXBlPg0KDQoNCg0KTW9yZ2FuICYgTm92byAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMjAs IDIwMDYgICAgICAgICAgICAgICAgIFtQYWdlIDddDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAg ICAgICAgICBSb2xlcyBpbiBYQ09OICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMDUNCg0KDQog ICA8L3hzOnNjaGVtYT4NCg0KDQoNCjguICBFeHRlbnNpYmlsaXR5IG9mIHRoZSBTY2hlbWENCg0K ICAgQXMgZGVmaW5lZCBpbiB0aGUgWE1MIHNjaGVtYSBkZWZpbml0aW9uIGFib3ZlLCB0aGUgJ3Jv bGUtdHlwZScgTVVTVA0KICAgaGF2ZSBmaXZlIHZhbHVlcy4gIEZ1dHVyZSBleHRlbnNpb25zIHRv IHRoaXMgc2NoZW1hIG1heSBkZWZpbmUgbmV3DQogICB2YWx1ZXMgYW5kIHJlZ2lzdGVyIHRoZW0g d2l0aCBJQU5BLiAgQSBoeXBvdGhldGljYWwgZXhhbXBsZSBmb3IgYQ0KICAgc2NoZW1hIGV4dGVu c2lvbiBmb3IgYSBuZXcgcm9sZS10eXBlIHZhbHVlIG9mICJzdWItYWRtaW5pc3RyYXRvciIgaXMN CiAgIHNob3duIGJlbG93Og0KDQoNCiAgIDx4czpzY2hlbWEgdGFyZ2V0TmFtZXNwYWNlPSIuLi4i Ow0KICAgIHhtbG5zPSIuLi4iOw0KICAgIHhtbG5zOnhzPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx L1hNTFNjaGVtYSI7Pg0KDQogICAgPHhzOnJlZGVmaW5lIHNjaGVtYUxvY2F0aW9uPSJyb2xlLXNj aGVtYS54c2QiPg0KICAgICA8eHM6c2ltcGxlVHlwZSBuYW1lPSJyb2xlLXR5cGUiPg0KICAgICAg PHhzOnJlc3RyaWN0aW9uIGJhc2U9InhzOnN0cmluZyI+DQogICAgICA8eHM6ZW51bWVyYXRpb24g dmFsdWU9InN1Yi1hZG1pbmlzdHJhdG9yIi8+DQogICAgICA8L3hzOnJlc3RyaWN0aW9uPg0KICAg ICA8L3hzOnNpbXBsZVR5cGU+DQogICAgPC94czpyZWRlZmluZT4NCiAgIDwveHM6c2NoZW1hPg0K DQoNCg0KOS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIEEgZ29vZCBkaXNjdXNzaW9u IG9mIGFwcHJvcHJpYXRlIHNlY3VyaXR5IGNvbnNpZGVyYXRpb25zIGJldHdlZW4NCiAgIGNsaWVu dHMgYW5kIHRoZSBjb25mZXJlbmNpbmcgc2VydmVyIGNhbiBiZSBmb3VuZCBpbiBbN10uDQoNCg0K MTAuICBJQU5BIENvbnNpZGVyYXRpb25zDQoNCiAgIFRoaXMgZG9jdW1lbnQgcmVnaXN0ZXJzIGEg bmV3IFhNTCBzY2hlbWEgYXMgcGVyIHRoZSBndWlkZWxpbmVzIGluIFJGQw0KICAgMzY4OFs0XS4N Cg0KICAgVVJJOiB1cm46aWV0ZjpwYXJhbXM6eG1sOm5zOnJvbGUtc2NoZW1hDQoNCiAgIFJlZ2lz dHJhbnQgQ29udGFjdDogSUVURiBYQ09OIFdvcmtpbmcgR3JvdXAgPHhjb25AaWV0Zi5vcmc+LCBh cw0KICAgZGVzaWduYXRlZCBieSB0aGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4gWE1MOiBUaGUgWE1M IGNhbiBiZSBmb3VuZCBpbg0KICAgdGhlIGNvbnRlbnRzIG9mIFNlY3Rpb24gNw0KDQogICBUaGlz IHNlY3Rpb24gcmVnaXN0ZXJzIGEgbmV3IFhNTCBuYW1lc3BhY2UsIGFzIHBlciB0aGUgZ3VpZGVs aW5lcyBpbg0KICAgUkZDIDM2ODhbNF0uDQoNCg0KDQoNCk1vcmdhbiAmIE5vdm8gICAgICAgICAg ICBFeHBpcmVzIEFwcmlsIDIwLCAyMDA2ICAgICAgICAgICAgICAgICBbUGFnZSA4XQ0KDA0KSW50 ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgUm9sZXMgaW4gWENPTiAgICAgICAgICAgICAgICAg T2N0b2JlciAyMDA1DQoNCg0KICAgVVJJOiBUaGUgVVJJIGZvciB0aGlzIG5hbWVzcGFjZSBpcyB1 cm46aWV0ZjpwYXJhbXM6eG1sOm5zOnJvbGUtc2NoZW1hDQoNCiAgIFJlZ2lzdHJhbnQgQ29udGFj dDogSUVURiBTSVBQSU5HIFdvcmtpbmcgR3JvdXAgPHNpcHBpbmdAaWV0Zi5vcmc+LCBhcw0KICAg ZGVzaWduYXRlZCBieSB0aGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4NCg0KDQoxMS4gIEFja25vd2xl ZGdlbWVudHMNCg0KICAgVGhlIGF1dGhvcnMgd291bGQgbGlrZSB0byB0aGFuayBHb256YWxvIENh bWFyaWxsbywgT3JpdCBMZXZpbiwgVW1lc2gNCiAgIENoYW5kcmEsIGFuZCBDaHJpcyBCb3VsdG9u IGZvciB0aGVpciBjb21tZW50cyBhbmQgaW5wdXQuDQoNCg0KMTIuICBSZWZlcmVuY2VzDQoNCjEy LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbMV0gIEJhcm5lcywgTS4gYW5kIEMuIEJv dWx0b24sICJBIEZyYW1ld29yayBhbmQgRGF0YSBNb2RlbCBmb3INCiAgICAgICAgQ2VudHJhbGl6 ZWQgQ29uZmVyZW5jaW5nIiwgZHJhZnQtYmFybmVzLXhjb24tZnJhbWV3b3JrLTAyICh3b3JrDQog ICAgICAgIGluIHByb2dyZXNzKSwgRmVicnVhcnkgMjAwNS4NCg0KICAgWzJdICBCcmFkbmVyLCBT LiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNhdGUgUmVxdWlyZW1lbnQNCiAg ICAgICAgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjExOSwgTWFyY2ggMTk5Ny4NCg0KICAgWzNdICBF dmVuLCBSLiBhbmQgTi4gSXNtYWlsLCAiQ29uZmVyZW5jaW5nIFNjZW5hcmlvcyIsDQogICAgICAg IGRyYWZ0LWlldGYteGNvbi1jb25mZXJlbmNlLXNjZW5hcmlvcy0wNSAod29yayBpbiBwcm9ncmVz cyksDQogICAgICAgIFNlcHRlbWJlciAyMDA1Lg0KDQogICBbNF0gIE1lYWxsaW5nLCBNLiwgIlRo ZSBJRVRGIFhNTCBSZWdpc3RyeSIsIEJDUCA4MSwgUkZDIDM2ODgsDQogICAgICAgIEphbnVhcnkg MjAwNC4NCg0KICAgWzVdICBNZWFsbGluZywgTS4sICJUaGUgSUVURiBYTUwgUmVnaXN0cnkiLA0K ICAgICAgICBkcmFmdC1tZWFsbGluZy1pYW5hLXhtbG5zLXJlZ2lzdHJ5LTA1ICh3b3JrIGluIHBy b2dyZXNzKSwNCiAgICAgICAgSnVuZSAyMDAzLg0KDQoxMi4yLiAgSW5mb3JtYXRpdmUgUmVmZXJl bmNlcw0KDQogICBbNl0gICBCb3VsdG9uLCBDLiBhbmQgVS4gQ2hhbmRyYSwgIk1lZGlhIFBvbGlj eSBUZW1wbGF0ZXMgZm9yIFhDT04iLA0KICAgICAgICAgZHJhZnQtYm91bHRvbi14Y29uLW1lZGlh LXRlbXBsYXRlLTAxICh3b3JrIGluIHByb2dyZXNzKSwNCiAgICAgICAgIEFwcmlsIDIwMDUuDQoN CiAgIFs3XSAgIENhbWFyaWxsbywgRy4sICJUaGUgQmluYXJ5IEZsb29yIENvbnRyb2wgUHJvdG9j b2wgKEJGQ1ApIiwNCiAgICAgICAgIGRyYWZ0LWNhbWFyaWxsby14Y29uLWJmY3AtMDAgKHdvcmsg aW4gcHJvZ3Jlc3MpLCBNYXkgMjAwNC4NCg0KICAgWzhdICAgTm92bywgTy4sICJBIENvbW1vbiBD b25mZXJlbmNlIEluZm9ybWF0aW9uIERhdGEgTW9kZWwgZm9yDQogICAgICAgICBDZW50cmFsaXpl ZCBDb25mZXJlbmNpbmcgIChYQ09OKSIsDQogICAgICAgICBkcmFmdC1ub3ZvLXhjb24tY29tbW9u LWRhdGEtbW9kZWwtMDAgKHdvcmsgaW4gcHJvZ3Jlc3MpLA0KICAgICAgICAgU2VwdGVtYmVyIDIw MDUuDQoNCg0KDQoNCk1vcmdhbiAmIE5vdm8gICAgICAgICAgICBFeHBpcmVzIEFwcmlsIDIwLCAy MDA2ICAgICAgICAgICAgICAgICBbUGFnZSA5XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAg ICAgICAgUm9sZXMgaW4gWENPTiAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDA1DQoNCg0KICAg WzldICAgS2hhcnRhYmlsLCBILiwgIlRoZSBDb25mZXJlbmNlIFBvbGljeSBDb250cm9sIFByb3Rv Y29sIChDUENQKSIsDQogICAgICAgICBkcmFmdC1pZXRmLXhjb24tY3BjcC0wMSAod29yayBpbiBw cm9ncmVzcyksIE9jdG9iZXIgMjAwNC4NCg0KICAgWzEwXSAgTGV2aW4sIE8uLCAiQ29uZmVyZW5j ZSBQb2xpY3kgQ29udHJvbCBQcm90b2NvbCBmb3IgQ2VudHJhbGl6ZWQNCiAgICAgICAgIENvbmZl cmVuY2luZyIsIGRyYWZ0LWxldmluLXhjb24tY3BjcC0wMCAod29yayBpbiBwcm9ncmVzcyksDQog ICAgICAgICBKdW5lIDIwMDMuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpNb3Jn YW4gJiBOb3ZvICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyMCwgMjAwNiAgICAgICAgICAgICAg ICBbUGFnZSAxMF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIFJvbGVzIGluIFhD T04gICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAwNQ0KDQoNCkF1dGhvcnMnIEFkZHJlc3Nlcw0K DQogICBEYXZpZCBQLiBNb3JnYW4NCiAgIEZpZGVsaXR5IEludmVzdG1lbnRzDQogICA4MiBEZXZv bnNoaXJlIFN0LCBNWiBWOEMNCiAgIEJvc3RvbiwgTUEgIDAyMTA5LTM2MTQNCiAgIFVTQQ0KDQog ICBFbWFpbDogRGF2ZS5Nb3JnYW5AZm1yLmNvbQ0KDQoNCiAgIE9zY2FyIE5vdm8NCiAgIEVyaWNz c29uDQogICBIaXJzYWxhbnRpZSAxMQ0KICAgSm9ydmFzICAwMjQyMA0KICAgRmlubGFuZA0KDQog ICBFbWFpbDogT3NjYXIuTm92b0Blcmljc3Nvbi5jb20NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCk1vcmdhbiAmIE5vdm8g ICAgICAgICAgICBFeHBpcmVzIEFwcmlsIDIwLCAyMDA2ICAgICAgICAgICAgICAgIFtQYWdlIDEx XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgUm9sZXMgaW4gWENPTiAgICAgICAg ICAgICAgICAgT2N0b2JlciAyMDA1DQoNCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVu dA0KDQogICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZhbGlkaXR5 IG9yIHNjb3BlIG9mIGFueQ0KICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyBvciBvdGhl ciByaWdodHMgdGhhdCBtaWdodCBiZSBjbGFpbWVkIHRvDQogICBwZXJ0YWluIHRvIHRoZSBpbXBs ZW1lbnRhdGlvbiBvciB1c2Ugb2YgdGhlIHRlY2hub2xvZ3kgZGVzY3JpYmVkIGluDQogICB0aGlz IGRvY3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55IGxpY2Vuc2UgdW5kZXIgc3VjaCBy aWdodHMNCiAgIG1pZ2h0IG9yIG1pZ2h0IG5vdCBiZSBhdmFpbGFibGU7IG5vciBkb2VzIGl0IHJl cHJlc2VudCB0aGF0IGl0IGhhcw0KICAgbWFkZSBhbnkgaW5kZXBlbmRlbnQgZWZmb3J0IHRvIGlk ZW50aWZ5IGFueSBzdWNoIHJpZ2h0cy4gIEluZm9ybWF0aW9uDQogICBvbiB0aGUgcHJvY2VkdXJl cyB3aXRoIHJlc3BlY3QgdG8gcmlnaHRzIGluIFJGQyBkb2N1bWVudHMgY2FuIGJlDQogICBmb3Vu ZCBpbiBCQ1AgNzggYW5kIEJDUCA3OS4NCg0KICAgQ29waWVzIG9mIElQUiBkaXNjbG9zdXJlcyBt YWRlIHRvIHRoZSBJRVRGIFNlY3JldGFyaWF0IGFuZCBhbnkNCiAgIGFzc3VyYW5jZXMgb2YgbGlj ZW5zZXMgdG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4NCiAgIGF0dGVt cHQgbWFkZSB0byBvYnRhaW4gYSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVybWlzc2lvbiBmb3IgdGhl IHVzZSBvZg0KICAgc3VjaCBwcm9wcmlldGFyeSByaWdodHMgYnkgaW1wbGVtZW50ZXJzIG9yIHVz ZXJzIG9mIHRoaXMNCiAgIHNwZWNpZmljYXRpb24gY2FuIGJlIG9idGFpbmVkIGZyb20gdGhlIElF VEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pcHIu DQoNCiAgIFRoZSBJRVRGIGludml0ZXMgYW55IGludGVyZXN0ZWQgcGFydHkgdG8gYnJpbmcgdG8g aXRzIGF0dGVudGlvbiBhbnkNCiAgIGNvcHlyaWdodHMsIHBhdGVudHMgb3IgcGF0ZW50IGFwcGxp Y2F0aW9ucywgb3Igb3RoZXIgcHJvcHJpZXRhcnkNCiAgIHJpZ2h0cyB0aGF0IG1heSBjb3ZlciB0 ZWNobm9sb2d5IHRoYXQgbWF5IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVudA0KICAgdGhpcyBzdGFu ZGFyZC4gIFBsZWFzZSBhZGRyZXNzIHRoZSBpbmZvcm1hdGlvbiB0byB0aGUgSUVURiBhdA0KICAg aWV0Zi1pcHJAaWV0Zi5vcmcuDQoNCg0KRGlzY2xhaW1lciBvZiBWYWxpZGl0eQ0KDQogICBUaGlz IGRvY3VtZW50IGFuZCB0aGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGhlcmVpbiBhcmUgcHJvdmlk ZWQgb24gYW4NCiAgICJBUyBJUyIgYmFzaXMgYW5kIFRIRSBDT05UUklCVVRPUiwgVEhFIE9SR0FO SVpBVElPTiBIRS9TSEUgUkVQUkVTRU5UUw0KICAgT1IgSVMgU1BPTlNPUkVEIEJZIChJRiBBTlkp LCBUSEUgSU5URVJORVQgU09DSUVUWSBBTkQgVEhFIElOVEVSTkVUDQogICBFTkdJTkVFUklORyBU QVNLIEZPUkNFIERJU0NMQUlNIEFMTCBXQVJSQU5USUVTLCBFWFBSRVNTIE9SIElNUExJRUQsDQog ICBJTkNMVURJTkcgQlVUIE5PVCBMSU1JVEVEIFRPIEFOWSBXQVJSQU5UWSBUSEFUIFRIRSBVU0Ug T0YgVEhFDQogICBJTkZPUk1BVElPTiBIRVJFSU4gV0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJR0hU UyBPUiBBTlkgSU1QTElFRA0KICAgV0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklU TkVTUyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UuDQoNCg0KQ29weXJpZ2h0IFN0YXRlbWVudA0K DQogICBDb3B5cmlnaHQgKEMpIFRoZSBJbnRlcm5ldCBTb2NpZXR5ICgyMDA1KS4gIFRoaXMgZG9j dW1lbnQgaXMgc3ViamVjdA0KICAgdG8gdGhlIHJpZ2h0cywgbGljZW5zZXMgYW5kIHJlc3RyaWN0 aW9ucyBjb250YWluZWQgaW4gQkNQIDc4LCBhbmQNCiAgIGV4Y2VwdCBhcyBzZXQgZm9ydGggdGhl cmVpbiwgdGhlIGF1dGhvcnMgcmV0YWluIGFsbCB0aGVpciByaWdodHMuDQoNCg0KQWNrbm93bGVk Z21lbnQNCg0KICAgRnVuZGluZyBmb3IgdGhlIFJGQyBFZGl0b3IgZnVuY3Rpb24gaXMgY3VycmVu dGx5IHByb3ZpZGVkIGJ5IHRoZQ0KICAgSW50ZXJuZXQgU29jaWV0eS4NCg0KDQoNCg0KTW9yZ2Fu ICYgTm92byAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMjAsIDIwMDYgICAgICAgICAgICAgICAg W1BhZ2UgMTJdDQoMDQoNCg== ------_=_NextPart_001_01C5D31F.22025BAE 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_001_01C5D31F.22025BAE-- From xcon-bounces@ietf.org Mon Oct 17 10:10:06 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERVgk-0000Il-7E; Mon, 17 Oct 2005 10:10:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERVgd-0000H2-S7 for xcon@megatron.ietf.org; Mon, 17 Oct 2005 10:10:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14446 for ; Mon, 17 Oct 2005 10:09:52 -0400 (EDT) Received: from smtp3.wanadoo.co.uk ([193.252.22.156] helo=smtp3.freeserve.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERVry-0007CX-43 for xcon@ietf.org; Mon, 17 Oct 2005 10:21:43 -0400 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3204.me.freeserve.com (SMTP Server) with ESMTP id 61FEB1C00097; Mon, 17 Oct 2005 16:09:34 +0200 (CEST) Received: from RW (user-5076.l1.c4.dsl.pol.co.uk [81.79.147.212]) by mwinf3204.me.freeserve.com (SMTP Server) with SMTP id 1641E1C0008C; Mon, 17 Oct 2005 16:09:34 +0200 (CEST) X-ME-UUID: 20051017140934912.1641E1C0008C@mwinf3204.me.freeserve.com Message-ID: <01ed01c5d324$66819960$a300a8c0@RW> From: "Pete Cordell" To: "Morgan, Dave" , "XCON" References: Subject: Re: [XCON] Draft defining the conferencing roles for XCON Date: Mon, 17 Oct 2005 15:09:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 2.4 (++) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Content-Transfer-Encoding: 7bit Cc: 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Dave, I'm afraid I haven't followed the XCON work in detail, but saw your schema and was a bit worried about the versioning aspects of a schema that uses enumerations. Does XCON have a formal policy on how versioning of schema should be done? As you probably know, this is one of the weak areas of XML schema, and it's unlikely that a versionable schema will happen by accident! Hence I would recommend having a formal draft (for the time being) on what approach should be taken for versioning so everyone is on the same page. In my opinion reliance of changing namespace names is brittle and best avoided if possible. To that end, something like the following might be considered: This allows new roles to be added to role-type-defined, without causing problems for entities that validate against an old schema. Regards, Pete. -- ============================================= Pete Cordell Tech-Know-Ware Ltd for XML to C++ data binding visit http://www.tech-know-ware.com/lmx (or http://www.xml2cpp.com) ============================================= ----- Original Message ----- From: "Morgan, Dave" To: "XCON" Sent: Monday, October 17, 2005 2:31 PM Subject: [XCON] Draft defining the conferencing roles for XCON Folks, Oscar and I have just submitted a draft defining the conferencing roles for XCON. Until it appears in the archives, you can refer to the attached document. In this draft we have taken a stab at defining five roles within a conference. They are: administrator, creator, moderator, participant, and observer. We have also written an XML schema so that these role definitions can be incorporated into other XCON drafts. Your comments are appreciated. We hope to have discussions on this topic on the mailing list. The following is the abstract of the draft: This document defines the set of possible conferencing roles that are used to represent participants within a Conference Object (as defined in the XCON Conference Framework [1]). The document also provides a set of semantics associated with each role. Additional roles may be defined in the future, as necessary, with their corresponding schema extensions, as appropriate. Cheers, Dave ------------------------------------------------------------------------ David P. Morgan, PhD VP, Architecture & Planning Fidelity Investments Systems Company - Telecom Phone: 617 563-2178 Fax: 617 385 2122 Mailing: 82 Devonshire St, MZ V8C Boston, MA 02109-3614 Office: 245 Summer Street, 8th Floor -------------------------------------------------------------------------------- > _______________________________________________ > 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 Mon Oct 17 10:27:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERVxF-0004v3-J5; Mon, 17 Oct 2005 10:27:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERVxE-0004ux-QX for xcon@megatron.ietf.org; Mon, 17 Oct 2005 10:27:08 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15326 for ; Mon, 17 Oct 2005 10:27:01 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERW8a-0007iM-21 for xcon@ietf.org; Mon, 17 Oct 2005 10:38:52 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E0EE84F0032; Mon, 17 Oct 2005 16:26:56 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 17 Oct 2005 16:26:37 +0200 Received: from esealmw105.eemea.ericsson.se ([153.88.200.68]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 17 Oct 2005 16:26:37 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [XCON] Draft defining the conferencing roles for XCON Date: Mon, 17 Oct 2005 16:25:32 +0200 Message-ID: Thread-Topic: [XCON] Draft defining the conferencing roles for XCON Thread-Index: AcXTJJ98/d/4Q70LRVq9Y7D/3+6jBQAAagiQ From: "Oscar Novo (JO/LMF)" To: "Pete Cordell" , "Morgan, Dave" , "XCON" X-OriginalArrivalTime: 17 Oct 2005 14:26:37.0454 (UTC) FILETIME=[C86A12E0:01C5D326] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d Content-Transfer-Encoding: quoted-printable Cc: 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi Pete, Thanks for your suggestion! We know the versioning is one of the = problems of XML and we had lot of problems to define the extensibility = of the schema. Actually, we haven't thought about the posibility to use = "union". Thank you very much for your help. We will incorporate your = suggestion in the new version of our draft. Thanks, Oscar -----Original Message----- From: xcon-bounces@ietf.org [mailto:xcon-bounces@ietf.org]On Behalf Of Pete Cordell Sent: 17. lokakuuta 2005 17:09 To: Morgan, Dave; XCON Subject: Re: [XCON] Draft defining the conferencing roles for XCON Hi Dave, I'm afraid I haven't followed the XCON work in detail, but saw your = schema=20 and was a bit worried about the versioning aspects of a schema that uses = enumerations. Does XCON have a formal policy on how versioning of = schema=20 should be done? As you probably know, this is one of the weak areas of = XML=20 schema, and it's unlikely that a versionable schema will happen by = accident!=20 Hence I would recommend having a formal draft (for the time being) on = what=20 approach should be taken for versioning so everyone is on the same page. = In=20 my opinion reliance of changing namespace names is brittle and best = avoided=20 if possible. To that end, something like the following might be = considered: This allows new roles to be added to role-type-defined, without causing=20 problems for entities that validate against an old schema. Regards, Pete. -- =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=3D=3D=3D=3D=3D=3D=3D=3D Pete Cordell Tech-Know-Ware Ltd for XML to C++ data binding visit http://www.tech-know-ware.com/lmx (or http://www.xml2cpp.com) =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=3D=3D=3D=3D=3D=3D=3D=3D ----- Original Message -----=20 From: "Morgan, Dave" To: "XCON" Sent: Monday, October 17, 2005 2:31 PM Subject: [XCON] Draft defining the conferencing roles for XCON Folks, Oscar and I have just submitted a draft defining the conferencing roles for XCON. Until it appears in the archives, you can refer to the attached document. In this draft we have taken a stab at defining five roles within a conference. They are: administrator, creator, moderator, participant, and observer. We have also written an XML schema so that these role definitions can be incorporated into other XCON drafts. Your comments are appreciated. We hope to have discussions on this topic on the mailing list. The following is the abstract of the draft: This document defines the set of possible conferencing roles that are used to represent participants within a Conference Object (as defined in the XCON Conference Framework [1]). The document also provides a set of semantics associated with each role. Additional roles may be defined in the future, as necessary, with their corresponding schema extensions, as appropriate. Cheers, Dave ------------------------------------------------------------------------ David P. Morgan, PhD VP, Architecture & Planning Fidelity Investments Systems Company - Telecom Phone: 617 563-2178 Fax: 617 385 2122 Mailing: 82 Devonshire St, MZ V8C Boston, MA 02109-3614 Office: 245 Summer Street, 8th Floor -------------------------------------------------------------------------= ------- > _______________________________________________ > 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 _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Oct 18 10:49:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERslz-0005sR-Gd; Tue, 18 Oct 2005 10:49:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERslt-0005r5-QQ; Tue, 18 Oct 2005 10:48:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05080; Tue, 18 Oct 2005 10:48:50 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERsxS-0007hg-0e; Tue, 18 Oct 2005 11:00:54 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1ERslo-0003Dx-Ak; Tue, 18 Oct 2005 10:48:52 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 18 Oct 2005 10:48:52 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: xcon chair , Internet Architecture Board , xcon chair , xcon mailing list , RFC Editor Subject: [XCON] Document Action: 'Conferencing Scenarios' to Informational RFC 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org The IESG has approved the following document: - 'Conferencing Scenarios ' as an Informational RFC This document is the product of the Centralized Conferencing Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-conference-scenarios-05.txt Adam Roach has been the working group shepherd for the document. Note to RFC Editor Expand first use of IVR to Interactive Voice Response, first use of DTMF to Dual-tone Multi-Frequency. 5. Security Considerations OLD: Conferences generally have authorization rules about who may or may not join a conference, what type of media may or may not be used, etc. This information, sometimes called the conference policy or common conference information, is used by the Conferencing System to admit or deny participation in a conference. For the conference policy to be implemented, the Conferencing System needs to be able to authenticate potential participants. The methods used depend on the signaling protocols used by the conference. This can include a challenge/response mechanism, certificates, shared secret, asserted identity, etc. These conference-specific security requirements are discussed further in the XCON requirements and framework documents. NEW: Conferences generally have authorization rules about who may or may not join a conference, what type of media may or may not be used, etc. This information, sometimes called the conference policy or common conference information, is used by the Conferencing System to admit or deny participation in a conference. For the conference policy to be implemented, the Conferencing System needs to be able to authenticate potential participants. The methods used depend on the signaling protocols used by the conference. This can include a challenge/response mechanism, certificates, shared secret, asserted identity, etc. Conferences often require that their content be confidential. In addition, secure authorization of participants is incomplete if access to the media can be gained by unauthorized participants. Functions for securing the media, and for key management and distribution to authorized participants need to be provided by the Conferencing System. In some cases the functions used for participant authorization can be leveraged for this purpose. Privacy is an important aspect of conferencing. Users may wish to join a conference without anyone knowing that they have joined, in order to silently listen in. In other applications, a participant may wish just to hide their identity from other participants, but otherwise let them know of their presence. These functions need to be provided by the Conferencing System. These conference-specific security requirements are discussed further in the XCON framework document. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Oct 24 07:05:20 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU08m-000325-JN; Mon, 24 Oct 2005 07:05:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU08i-00031L-4w for xcon@megatron.ietf.org; Mon, 24 Oct 2005 07:05:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01920 for ; Mon, 24 Oct 2005 07:05:02 -0400 (EDT) Received: from cluster-b.mailcontrol.com ([217.68.146.190] helo=rly07b.srv.mailcontrol.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU0LQ-00071y-Py for xcon@ietf.org; Mon, 24 Oct 2005 07:18:26 -0400 Received: from GBNEWP0758M.eu.ubiquity.net ([62.172.205.164]) by rly07b.srv.mailcontrol.com (MailControl) with ESMTP id j9OB53wv003370; Mon, 24 Oct 2005 12:05:04 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 24 Oct 2005 12:05:03 +0100 Message-ID: <45730E094814E44488F789C1CDED27AE04E7881F@gbnewp0758m.eu.ubiquity.net> Thread-Topic: Media Policy Templates Thread-Index: AcXYispTjVHzT91HQEafMFBHaoud1Q== From: "Chris Boulton" To: X-Scanned-By: MailControl A-05-40-01 (www.mailcontrol.com) on 10.66.0.117 X-Spam-Score: 0.2 (/) X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d Cc: adam@nostrum.com, Alan Johnston , Umesh.Chandra@nokia.com Subject: [XCON] Media Policy Templates 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="===============1475379909==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1475379909== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5D88A.C8E6476C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5D88A.C8E6476C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 A new version (02) of the Media Policy Template draft has been submitted to the archives. The latest version includes example XML Blueprints and XML schema definitions for 'Basic-Audio', 'Basic-Video', 'Audio-Video' and 'Basic-Text'. The authors welcome feedback and discussion on the document. =20 Until it appears in the archives the document can be retrieved from the following link:- http://www.ubiquitysoftware.com/ietf/draft-boulton-xcon-media-template-0 2.txt. =20 Best Regards, =20 Chris Boulton. =20 =20 =20 Information contained in this e-mail and any attachments are intended for t= he use of the addressee only, and may contain confidential information of U= biquity Software Corporation. All unauthorized use, disclosure or distribu= tion is strictly prohibited. If you are not the addressee, please notify t= he sender immediately and destroy all copies of this email. Unless otherwi= se expressly agreed in writing signed by an officer of Ubiquity Software Co= rporation, nothing in this communication shall be deemed to be legally bind= ing. Thank you. ------_=_NextPart_001_01C5D88A.C8E6476C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 

        &= nbsp;   A new version (02) of the Media Policy Template draft has been submitted to t= he archives.  The latest version includes example XML Blueprints and XML schema definitions for ‘Basic-Audio’, ‘Basic-Video’, ‘Audio-Video’ and ‘Basic-Text’.  The authors welcome feedback and discussion on the document.

 

Until it appears in the archives the document can= be retrieved from the following link:- http://www.ubiquitysoftware.com/ietf/draft-boulton-xcon-media-t= emplate-02.txt.

 

Best Regards,

 

Chris Boulton.

 

 

 



Information contained in t= his e-mail and any attachments are intended for the use of the addressee on= ly, and may contain confidential information of Ubiquity Software Corporati= on. All unauthorized use, disclosure or distribution is strictly prohibited= .  If you are not the addressee, please notify the sender immediately = and destroy all copies of this email.  Unless otherwise expressly agre= ed in writing signed by an officer of Ubiquity Software Corporation, nothin= g in this communication shall be deemed to be legally binding. Thank-you ------_=_NextPart_001_01C5D88A.C8E6476C-- --===============1475379909== 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 --===============1475379909==-- From xcon-bounces@ietf.org Mon Oct 24 07:26:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU0Tf-0000u6-SS; Mon, 24 Oct 2005 07:26:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU0Te-0000ty-I8 for xcon@megatron.ietf.org; Mon, 24 Oct 2005 07:26:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02853 for ; Mon, 24 Oct 2005 07:26:41 -0400 (EDT) Received: from atlantis.osc.edu ([192.148.249.4] helo=email.osc.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU0gO-0007gp-IK for xcon@ietf.org; Mon, 24 Oct 2005 07:40:05 -0400 Received: from planwel (199-18-139-113.dhcp.columbus.oar.net [199.18.139.113]) by email.osc.edu (Postfix) with SMTP id B1D3B27C008 for ; Mon, 24 Oct 2005 07:26:40 -0400 (EDT) Message-ID: <00cb01c5d88d$d43a8340$718b12c7@planwel> From: "Arif Khan" To: References: <45730E094814E44488F789C1CDED27AE04E7881F@gbnewp0758m.eu.ubiquity.net> Date: Mon, 24 Oct 2005 07:26:51 -0400 Organization: OARnet MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Score: 0.6 (/) X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0 Subject: [XCON] Megaconference VII Set For December 1, 2005 - Largest IP-Based Videoconferencing Event X-BeenThere: xcon@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Arif Khan List-Id: Centralized Conferencing List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1428531616==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1428531616== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C8_01C5D86C.4D075180" This is a multi-part message in MIME format. ------=_NextPart_000_00C8_01C5D86C.4D075180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Megaconference VII Set For December 1, 2005 Every Continent on Earth to Participate Now Open for Your Participation. Free! Greetings Everyone, Mark Your Calendars! On December 1, 2005, a very special event will take = place around the world, and you are invited. Megaconference VII begins = Thursday December 1, at 7:00 a.m. EST, and will continue throughout the = day until 11:30 p.m. EST. Representatives from every continent on earth = will be attending and presenting during the world's largest simultaneous = connection of IP-based videoconferencing communication devices. This year's theme, Increasing Empathy Through Videoconferencing, focuses = on improving understanding between individuals and cultures through = worldwide videoconferencing. The preliminary agenda will be posted very = soon on the Megaconference website (see below). The Megaconference takes place once a year to present, test and discuss = all aspects of IP-based videoconferencing. Presentations will discuss = and demonstrate how groups use Internet videoconferencing in real-world = situations for teaching, learning, sharing knowledge and information, = and a variety of other topics. Actual end users of videoconferencing = will be the predominant feature of Megaconference VII, while technical = presentations will be limited. All presentations will be fully = interactive, engaging multiple sites and audiences around the world. = Musical mini-concerts; have you ever heard a Didgeridoo or the Tennessee = Schmaltz? You have if you attended a previous Megaconference! Door Prizes of videoconferencing equipment have been donated by major = vendors in the past. The Grand Prize is often a $10,000 video station. Registration is now open via the Megaconference website. Like any = professional conference, presenters and audience members will discuss = current projects and developments. Unlike other conferences, hundreds of = participants from universities, K-12 schools, and many other = organizations will gather simultaneously around the world using advanced = networks and technology. For the past seven years it has been an honor for the Ohio Supercomputer = Center (OSC) to host the Megaconference.=20 For more information, point your web browser to the official = Megaconference website.=20 Megaconference website http://www.megaconference.org (for registration = and information). You can also view previous years' streaming at = http://commonsvcg.oar.net/megaconference/ =20 Kind Regards, _____________________ Arif Khan Global Internet2 H.323 Services NOC OARnet - A Division of Ohio Supercomputer Center 800-627-6420 or 614-292-9191 akhan@oar.net Ohio Supercomputer Center http://www.osc.edu OARnet http://www.oar.net Third Frontier Network http://www.osc.edu/oarnet/tfn/ Internet2 Commons http://commons.internet2.edu ------=_NextPart_000_00C8_01C5D86C.4D075180 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Megaconference VII Set For December 1,=20 2005
Every=20 Continent on Earth to Participate
Now Open for Your Participation. =20 Free!

Greetings Everyone,

Mark Your Calendars! = On=20 December 1, 2005, a very special event will take place around the world, = and you=20 are invited. Megaconference VII begins Thursday December 1, at 7:00 a.m. = EST,=20 and will continue throughout the day until 11:30 p.m. EST. = Representatives from=20 every continent on earth will be attending and presenting during the = world's=20 largest simultaneous connection of IP-based videoconferencing = communication=20 devices.

This year's theme, Increasing Empathy Through=20 Videoconferencing, focuses on improving understanding between=20 individuals and cultures through worldwide videoconferencing. The = preliminary=20 agenda will be posted very soon on the Megaconference website (see=20 below).

The Megaconference takes place once a year to present, = test and=20 discuss all aspects of IP-based videoconferencing. Presentations will = discuss=20 and demonstrate how groups use Internet videoconferencing in real-world=20 situations for teaching, learning, sharing knowledge and information, = and a=20 variety of other topics. Actual end users of videoconferencing will be = the=20 predominant feature of Megaconference VII, while technical presentations = will be=20 limited. All presentations will be fully interactive, engaging multiple = sites=20 and audiences around the world. Musical mini-concerts; have you ever = heard a=20 Didgeridoo or the Tennessee Schmaltz? You have if you attended a = previous=20 Megaconference!
 
Door=20 Prizes of videoconferencing equipment have been donated by major vendors = in the=20 past.  The Grand Prize is often a $10,000 video = station.


Registration is now open via the = Megaconference=20 website. Like any professional conference, presenters and audience = members will=20 discuss current projects and developments. Unlike other conferences, = hundreds of=20 participants from universities, K-12 schools, and many other = organizations will=20 gather simultaneously around the world using advanced networks and=20 technology.

For the past seven years it has been an honor for the = Ohio=20 Supercomputer Center (OSC) to host the Megaconference.=20

For=20 more information, point your web browser to the official Megaconference = website.=20
Megaconference website http://www.megaconference.org (for registration and information).
You can = also view=20 previous years' streaming at http://commonsvcg.oar.net/megaconference/
 
Kind = Regards,
_____________________
Arif Khan
Global Internet2 H.323 = Services=20 NOC
OARnet - A Division of Ohio Supercomputer Center
800-627-6420 = or=20 614-292-9191
akhan@oar.net
Ohio=20 Supercomputer Center http://www.osc.edu
OARnet http://www.oar.net
Third Frontier = Network http://www.osc.edu/oarnet/tfn/
Internet2=20 Commons http://commons.internet2.edu ------=_NextPart_000_00C8_01C5D86C.4D075180-- --===============1428531616== 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 --===============1428531616==-- From xcon-bounces@ietf.org Mon Oct 24 15:11:27 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU7jD-00008Z-Ry; Mon, 24 Oct 2005 15:11:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU7jC-00008R-E6 for xcon@megatron.ietf.org; Mon, 24 Oct 2005 15:11:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26672 for ; Mon, 24 Oct 2005 15:11:10 -0400 (EDT) Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7vy-0006Er-HF for xcon@ietf.org; Mon, 24 Oct 2005 15:24:38 -0400 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j9OJAtL15323 for ; Mon, 24 Oct 2005 15:10:55 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 24 Oct 2005 14:10:54 -0500 Message-ID: Thread-Topic: Updated draft-ietf-xcon-framework-02 Thread-Index: AcXYzqgPTOndSmElSqGdj36bd8/xgA== From: "Mary Barnes" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 093efd19b5f651b2707595638f6c4003 Content-Transfer-Encoding: quoted-printable Subject: [XCON] Updated draft-ietf-xcon-framework-02 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org Hi all, I submitted the updated version of the framework earlier today. Until it appears in the repository, it's available at: http://home.comcast.net/~mary.barnes/IETF/draft-ietf-xcon-framework-02.t xt http://home.comcast.net/~mary.barnes/IETF/draft-ietf-xcon-framework-02.h tml A summary of changes is listed below. There were quite a few changes in anticipation of completing this document. Thanks again to the folks that provided the detailed reviews. Just a note that a few things that I mentioned, in original responses to your comments, as needing additional WG discussion (i.e. policy, blueprint terminology and cloning terminology), are believed to be resolved with this new version. Further detail is provided in the summary of changes below. If you feel that the changes still don't adequately address your original concern, please start a separate thread for discussion (with proposed text changes towards resolution). =20 We do still have some open issues, with the primary ones being DP4 and DP5 related. =20 Summary of issues: ------------------ 1) Dave Morgan did bring up a specific point related to DP4 and it would be useful to have follow-up discussion under that thread: http://www1.ietf.org/mail-archive/web/xcon/current/msg01488.html =20 2) There had been a couple suggestions to remove details in the section on the CCP. However, we've left that section primarily unchanged until the WG can agree a way forward. Then we can replace all the details with text on the general requirements and an overview of the solution for the conference control protocol. This is of course, DP5.=20 3) There are a few areas of the document where we have placeholders for additional references and/or "Editor's notes:" where additional text is needed. A couple of these are just "ran out of time" areas, whereas others require agreement on whether other documents should become WG documents, thus included as references in the FW.=20 Once we can agree these primary issues, and include the appropriate references to agreed documents in progress, this framework document should be complete.=20 Summary of changes: ------------------- 1) Editorial nits (many of which should improve the readability and clarity of the document -i.e. consistent terminology, capatilization, etc.).=20 2) Revamped abstract and introduction per suggestions from Henning and others.=20 3) Global removal of XCON as a qualifier (we had previously done this in a previous version with all the identifiers). In some cases it was necessary, at all and it others, it was just a matter of changing to using the phrase "centralized conferencing". 4) Global change of "call control signalling" to "call signalling" 5) Moved the terminology section after the Overview section. =20 - Modified the definitions to be more concise and per some of Henning's recommendations. - Added definition for blueprint, clarifying its relationship to templates. - Added definition of conference reservation.=20 6) Clarified the definition of policy and added more explicit text as to how policy is accomplished via the data model and system realization (section 4.3 and 6.1). This should address the concerns raised on the mailing list about lack of clarity and confusion over whether the policy is part of the data object or something different. =20 7) Removed the Editor's note/text in section 4 about the options for the schema (that approach never helped the WG reach any consensus). I've just added a reference to a TBD schema document.=20 8) Section 5:=20 - clarified the identifiers. Kept the logical definition as "identifiers", although most will be realized as URIs.=20 - deleted the section on conference instance. There is a basic definition in terminology that should suffice. Old text was causing more confusion than clarity. =20 - removed the term "umbrella" from sections conference User and conference object identifier sections - moved alot of detail from Conference User Identifier and conference Object Identifier sections into appendices, and adding additional detail, that will become the basis for separate documents. =20 9) In section 6: - added a bit of explanation as to the intent of the cloning tree model - it's not implementation binding, but rather to illustrate the data model and context for the protocol interactions.=20 - removed the term copying altogether. Cloning is the model and the idea is that the cloned object contains data indentical to the parent when it was created (whether it gets "copied" or whatever from the parent is an implementation issue).=20 - introduce the blueprint concept in section 6.1 prior to its implied usage in 6.2 and 6.3.=20 - removed the usage of the term occurrence (which is just a child reservation). 10) Remove security related details from Floor Control section and moving those to the security section. As a result removed most of the editorial notes from the front of the Floor control section and integrated the remaining ones inline into that section, where the resolution should be documented. =20 11) Section 8:=20 - Added new example 8.1 - conference creation - Added a placeholder for a more detailed example to the sidebar manipulations example to show a sidebar which has some media specifically associated with the sidebar (i.e. audio), yet still use the main conference for other media (visual presentation). 12) As a result of adding additional information to the security section, divided this section into subsections for clarity.=20 Regards, Mary. _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Tue Oct 25 12:06:59 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EURKF-0006Ap-9F; Tue, 25 Oct 2005 12:06:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EURKD-0006Ae-BR for xcon@megatron.ietf.org; Tue, 25 Oct 2005 12:06:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01851 for ; Tue, 25 Oct 2005 12:06:39 -0400 (EDT) Received: from dsl027-191-169.sfo1.dsl.speakeasy.net ([216.27.191.169] helo=jest.tellocorp.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURX7-0000lN-Eh for xcon@ietf.org; Tue, 25 Oct 2005 12:20:20 -0400 Received: from [127.0.0.1] ([10.75.74.128]) by jest.tellocorp.com (Sun Java System Messaging Server 6.2 (built Dec 2 2004)) with ESMTPS id <0IOX00FFQBA69W00@jest.tellocorp.com> for xcon@ietf.org; Tue, 25 Oct 2005 09:03:42 -0700 (PDT) Date: Tue, 25 Oct 2005 09:06:40 -0700 From: Alan Johnston To: xcon@ietf.org Message-id: <435E5810.8040608@tello.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7BIT Cc: adam@nostrum.com 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org All, Please submit your agenda requests for IETF-64 to myself and Adam. Include your name, topic, draft, and approximately how much time you would like. Thanks, Alan Johnston co-chair _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Thu Oct 27 10:50:10 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV950-0003Td-Mm; Thu, 27 Oct 2005 10:50:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV94w-0003QL-0V; Thu, 27 Oct 2005 10:50:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03909; Thu, 27 Oct 2005 10:49:47 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV9IG-0004WG-GR; Thu, 27 Oct 2005 11:03:53 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EV94r-0000Gd-RA; Thu, 27 Oct 2005 10:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 27 Oct 2005 10:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: xcon@ietf.org Subject: [XCON] I-D ACTION:draft-ietf-xcon-framework-02.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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Centralized Conferencing Working Group of the IETF. Title : A Framework and Data Model for Centralized Conferencing Author(s) : M. Barnes, et al. Filename : draft-ietf-xcon-framework-02.txt Pages : 54 Date : 2005-10-27 This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber and PSTN, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions, along with a conferencing data model. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-framework-02.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-02.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-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-10-27081824.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-xcon-framework-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-xcon-framework-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-10-27081824.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 Thu Oct 27 16:31:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVEPP-0006i0-P1; Thu, 27 Oct 2005 16:31:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVEPO-0006hY-0p for xcon@megatron.ietf.org; Thu, 27 Oct 2005 16:31:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10939 for ; Thu, 27 Oct 2005 16:31:17 -0400 (EDT) Received: from mail1.microsoft.com ([131.107.3.125]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVEcj-0006ZR-Vi for xcon@ietf.org; Thu, 27 Oct 2005 16:45:23 -0400 Received: from mailout1.microsoft.com ([157.54.1.117]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 27 Oct 2005 13:31:15 -0700 Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.14]) by mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Oct 2005 13:31:15 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Oct 2005 13:31:12 -0700 Message-ID: Thread-Topic: I-D ACTION:draft-levin-xcon-cccp-03.txt thread-index: AcXbNV9brxttM95JRpq7FI0WaSOBxg== From: "Orit Levin" To: X-OriginalArrivalTime: 27 Oct 2005 20:31:15.0458 (UTC) FILETIME=[60DA0E20:01C5DB35] X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: quoted-printable Subject: [XCON] I-D ACTION:draft-levin-xcon-cccp-03.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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org FYI This is a much more advanced version (than -02) and has an updated compiled XML schema and examples for each primitive. Orit. ------------------------------------------------------------------------ ------ A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Centralized Conference Control Protocol (CCCP) Author(s) : O. Levin, et al. Filename : draft-levin-xcon-cccp-03.txt Pages : 51 Date : 2005-10-27 =09 This document defines a Centralized Conferencing Control Protocol (CCCP) as a part of the XCON Working Group protocols suite. CCCP uses a client-server model for creation, querying, and manipulation of XCON entities, conference objects and sub-objects. An XCON entity, which implements a CCCP server, provides a means for authorized CCCP clients (e.g. conference participants) to affect the behavior of a conference in the XCON system. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-levin-xcon-cccp-03.txt _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Thu Oct 27 16:40:10 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVEXi-0007cT-0c; Thu, 27 Oct 2005 16:40:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVEXf-0007WG-RK for xcon@megatron.ietf.org; Thu, 27 Oct 2005 16:40:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15233 for ; Thu, 27 Oct 2005 16:39:51 -0400 (EDT) Received: from mail1.microsoft.com ([131.107.3.125]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVEl6-0008B8-K2 for xcon@ietf.org; Thu, 27 Oct 2005 16:54:01 -0400 Received: from mailout1.microsoft.com ([157.54.1.117]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 27 Oct 2005 13:39:57 -0700 Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.14]) by mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Oct 2005 13:39:57 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Oct 2005 13:39:53 -0700 Message-ID: Thread-Topic: I-D ACTION:draft-levin-xcon-conference-package-ext-00.txt thread-index: AcXbNpV3HyC2l9qgSuCPAQsgHHh0eQ== From: "Orit Levin" To: X-OriginalArrivalTime: 27 Oct 2005 20:39:57.0035 (UTC) FILETIME=[97BC63B0:01C5DB36] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable Subject: [XCON] I-D ACTION:draft-levin-xcon-conference-package-ext-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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org FYI ------------------------------------------------------------------------ ------- A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Extensions to the Session Initiation Protocol (SIP) Event Package for Conference State Author(s) : O. Levin Filename : draft-levin-xcon-conference-package-ext-00.txt Pages : 13 Date : 2005-10-19 This document introduces global elements into the SIP Conference Event Package XML schema to make the conference objects and sub- objects easily accessible by schemas external to the event package, such as the XCON conference control protocols. This document also defines the way to introduce XCON extensions into the SIP Conference Event Package in a backwards compatible manner. This document also defines a set of extensions to the SIP Conference Event Package XML schema being used in the XCON conferencing architecture. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-levin-xcon-conference-package- ext-00.txt _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Fri Oct 28 10:59:38 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVVhi-00012r-S7; Fri, 28 Oct 2005 10:59:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVVhh-00012m-Gg for xcon@megatron.ietf.org; Fri, 28 Oct 2005 10:59:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22655 for ; Fri, 28 Oct 2005 10:59:20 -0400 (EDT) Received: from maillnx-us112.fmr.com ([192.223.198.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVVvH-0008Ph-F4 for xcon@ietf.org; Fri, 28 Oct 2005 11:13:40 -0400 Received: from MSGMMKSM01WIN.DMN1.FMR.COM (MSGMMKSM01WIN.dmn1.fmr.com [10.33.139.32]) by maillnx-us112.fmr.com (Switch-3.1.2/Switch-3.1.0) with SMTP id j9SExK6G001817 for ; Fri, 28 Oct 2005 10:59:20 -0400 Received: from MSGMMKIV01WIN.DMN1.FMR.COM (10.33.148.30) by MSGMMKSM01WIN.DMN1.FMR.COM (Sigaba Gateway v3.83) with ESMTP id 51719723; Fri, 28 Oct 2005 10:59:20 -0400 Received: from MSGMROIM01WIN.DMN1.FMR.COM ([172.26.2.194]) by MSGMMKIV01WIN.DMN1.FMR.COM with SMTP_server; Fri, 28 Oct 2005 10:59:20 -0400 Received: from msgmroclm2win.fmr.com ([10.37.181.20]) by MSGMROIM01WIN.DMN1.FMR.COM with Microsoft SMTPSVC(5.0.2195.6713); Fri, 28 Oct 2005 10:59:19 -0400 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-Class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 28 Oct 2005 10:59:19 -0400 Message-ID: Thread-Topic: Comments on xcon-media-template-02 thread-index: AcXb0CxsskQdE5JZRYGN4WU6tgtS5g== From: "Morgan, Dave" To: "XCON" X-OriginalArrivalTime: 28 Oct 2005 14:59:19.0691 (UTC) FILETIME=[2C8AEDB0:01C5DBD0] X-Spam-Score: 0.9 (/) X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e Subject: [XCON] Comments on xcon-media-template-02 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="===============1018594129==" Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org This is a multi-part message in MIME format. --===============1018594129== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5DBD0.2C67513C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5DBD0.2C67513C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Chris and Umesh, here's my comments on your draft. =20 1. I think that the three individual basic template definitions for audio, video, and text should be combined into one basic multi-media template (I agree with Orit on this point). The fact that some media definitions may be described and not used are inconsequential. Furthermore, your next step would be to define a combined audio/video/text template anyway. Given that there is a lot of similarity in the definitions, I vote for combining them and then moving on to the advanced templates. 2. Section 1: Introduction. I think that you should say you're going to be "control protocol" agnostic. That being said, obviously the syntax has to match between the template and the control protocol. 3. Section 4.1.1: Description. I think you should add something in here on the audio mixing control, much like you have in the video section. 4. Section 4.1.1: Description. I would vote that by default the audio template allows all participants to speak when they join and that the floor control is disabled. This is how the vast majority of today's conferences are configured. 5. Section 4.1.2: Roles. I would use "logical entities" rather than "participants" to describe the conference attendees. This avoids confusion with the "participant" role. You use "entities" in the role descriptions later in the draft. 6. Section 4.1.2: Roles. I would include all 5 roles. You should include Administrator, most deployed systems have an Administrator. You should also include Creator, you refer to it. You might as well throw in Observer, then the basic (multimedia) template will be consistent with the 5 proposed roles. 7. Section 4.1.4: Controls. I would vote that we should keep the restriction that people cannot add controls to the basic template. That would be true for audio, video, and text. 8. Section 4.1.4.1: Mute. I like the idea of mute on the input and output streams. I also like the way you set up the controlarray on the logical stream. But I'm a bit confused, do we need to have a stream-id in here to identify which stream the moderator is muting? The same is true for "pausing" video and blocking text. 9. Section 4.1.4.2: Gain. I have an issue here. We need to define this either in db (with a default value of 0) or using a scale from 1.0 to 0.0 (with a default value of .5). We need to account for amplification and attenuation. 10. Section 4.1.6.1.1.1: Send_audio. I don't like the variable name "value" it doesn't have any connotation. Can you call it "floor-control" or something that better describes its function? 11. Section 4.1.7: Blueprint XML (Audio). I would make the gain volume default either .5 absolute or 0 db. Don't start the participant with no volume. Even if you do intend to mute the output. 12. Section 4.1.7: Blueprint XML (Audio). I would start with a max number of moderators being 1, not 128. 128 moderators would be total confusion. 13. Section 4.3.1: Description (Video). I would suggest using "video mixing control" instead of "local policy". 14. Section 4.3.1: Description (Video). You're going to need something here on "layout". The layout should be given for the basic video template, even if it's just "single-view". 15. Section 4.3.4.1: Pause-video. How about renaming "pause-video" to just "freeze". So for the 3 media types you would have mute (audio), freeze (video), and block (text). 16. Section 4.5.1: Description (Text). Actually I want to see my text message appear in the received text stream, this is how most systems work today. I must confess that's how I spot most of my typos.=20 17. Section 4.5.1: Description (Text). When you're talking about "defined to limit who can inject" you're really talking about the "moderator". So I would explicitly say "moderator". 18. Section 4.5.7: Blueprint XML Example (Text). By default I would favor the variable to block incoming text should be set to false. You should assume that conference participants know each other and want to communicate with each other. I would deal with "black-lists" with an advanced text template. Overall, excellent progress. We're all eager to see the template flushed out some more. =20 =20 Dave =20 ------------------------------------------------------------------------ David P. Morgan, PhD=20 VP, Architecture & Planning=20 Fidelity Investments Systems Company - Telecom=20 Phone: 617 563-2178=20 Fax: 617 385 2122=20 Mailing: 82 Devonshire St, MZ V8C=20 Boston, MA 02109-3614=20 Office: 245 Summer Street, 8th Floor=20 =20 ------_=_NextPart_001_01C5DBD0.2C67513C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Chris and Umesh, here’s my comments on your = draft.

 

  1. I think that the three individual = basic template=20 definitions for audio, video, and text should be combined into one = basic=20 multi-media template (I agree with Orit on this point).  The fact that some media = definitions=20 may be described and not used are inconsequential.   Furthermore, your next = step=20 would be to define a combined audio/video/text template anyway.  Given that there is a lot of = similarity in the definitions, I vote for combining them and then = moving on to=20 the advanced templates.
  2. Section 1: Introduction. I think = that you should=20 say you’re going to be “control protocol” = agnostic.  That being said, obviously = the syntax=20 has to match between the template and the control = protocol.
  3. Section 4.1.1: Description. I think = you should=20 add something in here on the audio mixing control, much like you have = in the=20 video section.
  4. Section 4.1.1: Description.  I would vote that by default = the audio=20 template allows all participants to speak when they join and that the = floor=20 control is disabled.  = This is how=20 the vast majority of today’s conferences are = configured.
  5. Section 4.1.2: Roles.  I would use “logical = entities” rather=20 than “participants” to describe the conference = attendees.  This avoids confusion with = the=20 “participant” role.  You use=20 “entities” in the role descriptions later in the = draft.
  6. Section 4.1.2: Roles.  I would include all 5 = roles.  You should include = Administrator, most=20 deployed systems have an Administrator. =20 You should also include Creator, you refer to it.  You might as well throw in = Observer,=20 then the basic (multimedia) template will be consistent with the 5 = proposed=20 roles.
  7. Section 4.1.4: Controls.  I would vote that we should = keep the=20 restriction that people cannot add controls to the basic = template.  That would be true for = audio, video,=20 and text.
  8. Section 4.1.4.1: Mute.  I like the idea of mute on = the input=20 and output streams.  I = also like=20 the way you set up the controlarray on the logical stream.  But I’m a bit = confused, do we need to=20 have a stream-id in here to identify which stream the moderator is=20 muting?  The same is = true for=20 “pausing” video and blocking text.
  9. Section 4.1.4.2:  Gain.  I have an issue here.  We need to define this = either in db=20 (with a default value of 0) or using a scale from 1.0 to 0.0 (with a = default=20 value of .5).  We need = to account=20 for amplification and attenuation.
  10. Section 4.1.6.1.1.1: Send_audio. I = don’t like=20 the variable name “value” it doesn’t have any = connotation.  Can you call it = “floor-control” or=20 something that better describes its function?
  11. Section 4.1.7: Blueprint XML = (Audio).  I would make the gain volume = default=20 either .5 absolute or 0 db.  = Don't=20 start the participant with no volume. =20 Even if you do intend to mute the output.
  12. Section 4.1.7: Blueprint XML = (Audio).  I would start with a max = number of=20 moderators being 1, not 128.  = 128=20 moderators would be total confusion.
  13. Section 4.3.1: Description = (Video).  I would suggest using "video = mixing=20 control" instead of "local policy".
  14. Section 4.3.1: Description = (Video).  You're going to need = something here on=20 "layout".  The layout = should be=20 given for the basic video template, even if it's just "single-view".
  15. Section 4.3.4.1: Pause-video. How = about renaming=20 "pause-video" to just "freeze". =20 So for the 3 media types you would have mute (audio), freeze = (video),=20 and block (text).
  16. Section 4.5.1: Description (Text). = Actually I=20 want to see my text message appear in the received text stream, this = is how=20 most systems work today.  = I must=20 confess that’s how I spot most of my typos.
  17. Section 4.5.1: Description (Text). = When you’re=20 talking about “defined to limit who can inject” = you’re really talking about=20 the “moderator”.  = So I would=20 explicitly say “moderator”.
  18. Section 4.5.7: Blueprint XML Example = (Text).  By default I = would favor=20 the  variable to block = incoming=20 text should be set to false.  You should assume that = conference=20 participants know each other and want to communicate with each = other.  I would deal with = "black-lists" with=20 an advanced text template.

 Overall, excellent=20 progress.  We’re all = eager to see=20 the template flushed out some more.

 

 

Dave

 

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


 
------_=_NextPart_001_01C5DBD0.2C67513C-- --===============1018594129== 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 --===============1018594129==-- From xcon-bounces@ietf.org Fri Oct 28 19:48:29 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVdxV-0007OB-SQ; Fri, 28 Oct 2005 19:48:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVdxU-0007Lm-Qk for xcon@megatron.ietf.org; Fri, 28 Oct 2005 19:48:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27489 for ; Fri, 28 Oct 2005 19:48:07 -0400 (EDT) Received: from magus.nostrum.com ([69.5.195.2] helo=nostrum.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVeB2-0000w2-SU for xcon@ietf.org; Fri, 28 Oct 2005 20:02:32 -0400 Received: from [172.17.2.251] (dsl001-129-069.dfw1.dsl.speakeasy.net [72.1.129.69]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id j9SNmClf057206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Oct 2005 18:48:13 -0500 (CDT) (envelope-from adam@nostrum.com) Message-ID: <4362B8BB.7020709@nostrum.com> Date: Fri, 28 Oct 2005 18:48:11 -0500 From: Adam Roach User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: xcon@ietf.org References: <435E5810.8040608@tello.com> In-Reply-To: <435E5810.8040608@tello.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 72.1.129.69 is authenticated by a trusted mechanism) X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Content-Transfer-Encoding: 7bit Cc: Alan Johnston Subject: [XCON] Agenda Posted 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org The agenda for XCON at IETF 64 has been posted. It is available in HTML and text formats at: http://www.softarmor.com/xcon/meets/ietf64/ /a _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon From xcon-bounces@ietf.org Mon Oct 31 18:55:35 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWjV1-0005gd-Eq; Mon, 31 Oct 2005 18:55:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWjUv-0005et-L7; Mon, 31 Oct 2005 18:55:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21030; Mon, 31 Oct 2005 18:55:08 -0500 (EST) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWjjC-00073f-Ut; Mon, 31 Oct 2005 19:10:15 -0500 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1EWjUu-0008Na-5O; Mon, 31 Oct 2005 18:55:28 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 31 Oct 2005 18:55:28 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: xcon chair , Internet Architecture Board , xcon chair , xcon mailing list , RFC Editor Subject: [XCON] Document Action: 'Requirements for Floor Control Protocol' to Informational RFC 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: , Sender: xcon-bounces@ietf.org Errors-To: xcon-bounces@ietf.org The IESG has approved the following document: - 'Requirements for Floor Control Protocol ' as an Informational RFC This document is the product of the Centralized Conferencing Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-xcon-floor-control-req-03.txt _______________________________________________ XCON mailing list XCON@ietf.org https://www1.ietf.org/mailman/listinfo/xcon