Fwd: RE: xcon BoF at IETF re secure videoconferencing

[Robert Olson]

more on this.

>Delivered-To: vidmid-vc at internet2.edu
>From: "Even, Roni" <roni.even at polycom.co.il>
>To: "'RL 'Bob' Morgan '" <rlmorgan at washington.edu>,
>    "'VidMid-VC '" <vidmid-vc at internet2.edu>
>Subject: RE: xcon BoF at IETF re secure videoconferencing
>Date: Sat, 12 Jul 2003 18:34:41 +0300
>X-Mailer: Internet Mail Service (5.5.2656.59)
>X-Virus-Scanned: by AMaViS 0.3.12pre8
>Reply-To: roni.even at polycom.co.il
>Sender: owner-vidmid-vc at internet2.edu
>X-Virus-Scanned: by AMaViS 0.3.12pre8
>X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.21
>X-Spam-Level:
>
>  Hi,
>The XCON BOF is about conference and media control for tightly coupled
>conferences and not abut seurity. The WG will try to develop a protocol for
>conference control, media control and floor control. Authorization is part
>of the requirements to define and change conference and media policies.
>
>Regards
>Roni Even
>
>-----Original Message-----
>From: RL 'Bob' Morgan
>To: VidMid-VC
>Sent: 12/07/2003 10:19
>Subject: xcon BoF at IETF re secure videoconferencing
>
>
>Dunno if anyone's heard of this, but:
>
>   http://ietf.org/ietf/03jul/xcon.txt
>
>looks like there will be a BoF on this at IETF this coming week, with
>the
>intent to form a WG.  Could be relevant to vidmid-vc work, clearly.
>I'll
>try to check it out, though it conflicts with two other WGs I would
>normally attend, sigh.  I guess there's already a mailing list for those
>innarested.
>
>  - RL "Bob"
>
>---
>
>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.
>
>
>
>-------------------------------------------------------------vidmid-vc-+
>For list utilities, archives, subscribe, unsubscribe, etc. please visit the
>ListProc web interface at
>
>     http://archives.internet2.edu/
>
>-------------------------------------------------------------vidmid-vc--