From dean.willis at softarmor.com Thu Jun 5 22:10:16 2003 From: dean.willis at softarmor.com (Dean Willis) Date: Thu Jun 5 21:10:48 2003 Subject: [XCON] Hello, This is a very first test message. Message-ID: <001701c32bd0$c7d346d0$ee036e3f@txdwillis> I'm sending it out to the list. Did it work? -- Dean From alan.johnston at mci.com Thu Jun 5 23:53:19 2003 From: alan.johnston at mci.com (Alan Johnston) Date: Thu Jun 5 22:57:05 2003 Subject: [XCON] Test Posting Message-ID: <5.2.1.1.0.20030605225153.0204f398@pop.mcit.com> This is a test! From alan.johnston at mci.com Tue Jun 24 15:16:22 2003 From: alan.johnston at mci.com (Alan Johnston) Date: Tue Jun 24 14:46:47 2003 Subject: [XCON] Centralized Conferencing (xcon) BOF Announcement Message-ID: <5.2.1.1.0.20030624141450.023c2688@pop.mcit.com> FYI. Centralized Conferencing BOF (xcon) Tuesday, July 15 at 1700-1800 ============================== CHAIRS: Alan Johnston (alan.johnston@mci.com) Adam Roach (adam@dynamicsoft.com) AGENDA: - Intro and Agenda Bashing (5 min) - Problem Statement and Overview of Scope (10 min) - Charter Discussion (15 min) - Open Discussion (30 min) Description of Proposed Working Group The focus of this working group is to develop a standardized suite of protocols for tightly-coupled multimedia conferences, where strong security and authorization requirements are integral to the solution. Tightly-coupled conferences have a central point of control and authorization so they can enforce specific media and membership relationships, and provide an accurate roster of participants. The media mixing or combining function of a tightly-coupled conference need not be performed centrally, however. Unlike previous attempts at standardizing conferencing-related activities, the scope of this effort is intentionally very narrow, and is intended to enable interoperability in a commercial environment which already has a number of implementations. Privacy, security, and authorization mechanisms are integral to the solution generated by the working group. This includes allowing participants to be completely invisible or to be visible but participate anonymously with respect to some or all of the other participants. Authorization rules allow for participants and non-participants to have roles (ex: speaker, moderator, owner), and to be otherwise authorized to perform membership and media manipulation for or on behalf of other participants. In order to preserve these properties, the protocols used will require implementation of channel security and authentication services. Initially this combination of protocols will be specified with respect to session setup with SIP, but most of the specific components would be applicable to conferences setup using other protocols. [None of the protocols defined by this group will be SIP or require SIP extensions.] The group will use the high-level requirements and framework already described by documents published by the SIPPING WG. The deliverables for the group will be: - A mechanism for membership and authorization control - A mechanism to manipulate and describe media "layout" or "topology" for multiple media types (audio, video, text) - A mechanism for notification of conference related events/changes (for example a roster) - A basic floor control protocol - Peer-to-peer cascading of conferences (one conference is a participant in another and vice versa) The following items are specifically out-of-scope: - Voting - Multicast media (due to security concerns) - Fully distributed conferences - Loosely-coupled conferences (no central point of control) - Far-end device control - Protocol used between the conference controller and the mixer(s) - Capabilities negotiation of the mixer(s) - Master-slave cascaded conferences The working group will coordinate closely with the SIPPING and MMUSIC working groups. In addition the working group will cooperate with other groups as needed, including SIP, AVT, and the W3C SMIL working groups. In addition, the working group will consider a number of existing drafts (a non-exhaustive list is included below) as input to the working group. Related documents in other working groups: - draft-ietf-sipping-conferencing-requirements-00.txt - draft-ietf-sipping-conferencing-framework-00.txt - draft-ietf-sipping-cc-conferencing-00.txt - draft-ietf-sipping-cc-framework-02.txt - draft-ietf-sipping-conference-package-00.txt Partial list of input documents: (All documents available at http://ee.wustl.edu/~alan/xcon/ until they appear in the IETF archives.) - draft-even-xcon-conference-scenarios-00.txt - draft-koskelainen-xcon-cpcp-reqs-00.txt - draft-even-xcon-media-policy-requirements-00.txt - draft-koskelainen-xcon-floor-control-req-00.txt - draft-koskelainen-xcon-xcap-cpcp-usage-00.txt - draft-levin-xcon-cpcp-00.txt - draft-mahy-xcon-media-policy-control-00.txt Comments on the above drafts are welcome on the xcon mailing list: Mailing-List: xcon@softarmor.com http://www.softarmor.com/mailman/listinfo/xcon From eunah at etri.re.kr Wed Jun 25 22:43:33 2003 From: eunah at etri.re.kr (eunah@etri.re.kr) Date: Wed Jun 25 07:43:16 2003 Subject: [XCON] Re: [Sip] Centralized Conferencing (xcon) BOF Announcement Message-ID: <8470181DABD5D511B3E700D0B7A8AC4A03B752D1@cms3> Hi, I have very similar idea with "draft-koskelainen-xcon-xcap-cpcp-usage- 00.txt". I'm writing a draft about CPCP, and it is not submitted to IETF yet (I'm still working on it), but you can find the document in the following URL: http://pec.etri.re.kr/~eunah/ietf/draft-sipping-conf-policy-control-00. txt I think a part of it can be an input to Petri's work. I appreciate any comments and opinion on that. Eunsook Kim Senior Researcher ETRI(Electronics and Telecommunication Research Institute) Office: 82-42-860-6124 Mobile:82-11-9711-1466 ----- Original Message ----- From: "Alan Johnston" To: Cc: "Adam Roach" Sent: Wednesday, June 25, 2003 4:16 AM Subject: [Sip] Centralized Conferencing (xcon) BOF Announcement > FYI. > > Centralized Conferencing BOF (xcon) > > Tuesday, July 15 at 1700-1800 > ============================== > > CHAIRS: Alan Johnston (alan.johnston@mci.com) > Adam Roach (adam@dynamicsoft.com) > > AGENDA: > > - Intro and Agenda Bashing (5 min) > - Problem Statement and Overview of Scope (10 min) > - Charter Discussion (15 min) > - Open Discussion (30 min) > > > Description of Proposed Working Group > > > The focus of this working group is to develop a standardized suite of > protocols for tightly-coupled multimedia conferences, where strong security > and authorization requirements are integral to the solution. > Tightly-coupled conferences have a central point of control and > authorization so they can enforce specific media and membership > relationships, and provide an accurate roster of participants. The media > mixing or combining function of a tightly-coupled conference need not be > performed centrally, however. Unlike previous attempts at standardizing > conferencing-related activities, the scope of this effort is intentionally > very narrow, and is intended to enable interoperability in a commercial > environment which already has a number of implementations. > > > Privacy, security, and authorization mechanisms are integral to the > solution generated by the working group. This includes allowing > participants to be completely invisible or to be visible but participate > anonymously with respect to some or all of the other participants. > Authorization rules allow for participants and non-participants to have > roles (ex: speaker, moderator, owner), and to be otherwise authorized to > perform membership and media manipulation for or on behalf of other > participants. In order to preserve these properties, the protocols used > will require implementation of channel security and authentication services. > > > Initially this combination of protocols will be specified with respect to > session setup with SIP, but most of the specific components would be > applicable to conferences setup using other protocols. [None of the > protocols defined by this group will be SIP or require SIP extensions.] The > group will use the high-level requirements and framework already described > by documents published by the SIPPING WG. > > > The deliverables for the group will be: > - A mechanism for membership and authorization control > - A mechanism to manipulate and describe media "layout" or "topology" for > multiple media types (audio, video, text) > - A mechanism for notification of conference related events/changes (for > example a roster) > - A basic floor control protocol > - Peer-to-peer cascading of conferences (one conference is a participant in > another and vice versa) > > > The following items are specifically out-of-scope: > - Voting > - Multicast media (due to security concerns) > - Fully distributed conferences > - Loosely-coupled conferences (no central point of control) > - Far-end device control > - Protocol used between the conference controller and the mixer(s) > - Capabilities negotiation of the mixer(s) > - Master-slave cascaded conferences > > > The working group will coordinate closely with the SIPPING and MMUSIC > working groups. In addition the working group will cooperate with other > groups as needed, including SIP, AVT, and the W3C SMIL working groups. > In addition, the working group will consider a number of existing drafts (a > non-exhaustive list is included below) as input to the working group. > > > Related documents in other working groups: > - draft-ietf-sipping-conferencing-requirements-00.txt > - draft-ietf-sipping-conferencing-framework-00.txt > - draft-ietf-sipping-cc-conferencing-00.txt > - draft-ietf-sipping-cc-framework-02.txt > - draft-ietf-sipping-conference-package-00.txt > > Partial list of input documents: > (All documents available at http://ee.wustl.edu/~alan/xcon/ until they > appear in the IETF archives.) > > - draft-even-xcon-conference-scenarios-00.txt > - draft-koskelainen-xcon-cpcp-reqs-00.txt > - draft-even-xcon-media-policy-requirements-00.txt > - draft-koskelainen-xcon-floor-control-req-00.txt > - draft-koskelainen-xcon-xcap-cpcp-usage-00.txt > - draft-levin-xcon-cpcp-00.txt > - draft-mahy-xcon-media-policy-control-00.txt > > Comments on the above drafts are welcome on the xcon mailing list: > > Mailing-List: xcon@softarmor.com > http://www.softarmor.com/mailman/listinfo/xcon > > >