Fwd: xcon BoF at IETF re secure videoconferencing

Robert Olson olson at mcs.anl.gov
Mon Jul 14 10:38:53 CDT 2003


hm, something to track closely and see about interacting with..

>Delivered-To: vidmid-vc at internet2.edu
>Date: Sat, 12 Jul 2003 01:19:16 -0600 (MDT)
>From: "RL 'Bob' Morgan" <rlmorgan at washington.edu>
>X-X-Sender: rlmorgan at localhost.localdomain
>To: VidMid-VC <vidmid-vc at internet2.edu>
>Subject: xcon BoF at IETF re secure videoconferencing
>X-Virus-Scanned: by AMaViS 0.3.12pre8
>Reply-To: rlmorgan at washington.edu
>Sender: owner-vidmid-vc at internet2.edu
>X-Virus-Scanned: by AMaViS 0.3.12pre8
>X-Spam-Status: No, hits=0.6 required=5.0 tests=TO_LOCALPART_EQ_REAL 
>version=2.21
>X-Spam-Level:
>
>
>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--




More information about the ag-dev mailing list