VidMid-VC Conference Call May 16, 2005

*Attendees*
Nadim El-Khoury, University of North Carolina, Chapel Hill (Chair)
Paul Hill, MIT
Ann West, EDUCAUSE/Internet2
Lisa Hogeboom, Internet2
Steve Olshansky, Internet2
Jessica Bibbee, Internet2 (scribe)

New *Action Items*
[AI] {Nadim} will update the federated secure diagram from the I2MM BoF
presentation, and send the URL out to the VidMid-VC mailing list once it is
posted.

[AI] {Steve} will post the updated federated secure diagram (pdf) from
{Nadim} on the VidMid-VC site.

[AI] {Nadim} will work with {Tyler} to coordinate future VidMid-VC efforts
under RTC direction.

[AI] The Group motioned to move the VidMid-VC conference calls to an
every-4-weeks schedule, beginning with the next call on June 13, 2005 at 11am
ET.

Carry Over *Action Items*
[AI] {Nadim} will send out information about a proposed design meeting to
identify potential partners and future steps to take.

*Discussion*
[AI] The Group motioned to move the VidMid-VC conference calls to an
every-4-weeks schedule, beginning with the next call on June 13, 2005 at 11am
ET. As more direction is given with respect to RTC, the Group will address
the frequency of the conference calls accordingly.

{Nadim} discussed the set of slides diagramming the federated secure model,
which was presented at the I2MM VidMid-VC BoF. At the BoF, those present
decided to change one of the flows. The two flows involved user access to a
Service Provider MCU conference service and user identification across
multiple domains. An important point is that the policies need to be set up
out-of-band, after which, you already have the information to skip the
authorization step. These policies will identify which attributes are to be
used. [AI] {Nadim} will update the federated secure diagram from the I2MM BoF
presentation, and send the URL out to the VidMid-VC mailing list once it is
posted. [AI] {Steve} will post the updated federated secure diagram (pdf)
from {Nadim} on the VidMid-VC site.

{Nadim} looked into using tokens as a mean of sending security information.
We would need to come up with the technical assertion, then find out where to
place it. This would require the approval of the ITU. Ideally, it would be
good to be able to point to a standard documentation that is recognized -
this would provide time to move the technical document forward.

If possible, VidMid-VC should coordinate efforts with SIP and H.323. [AI]
{Nadim} will work with {Tyler} to coordinate future VidMid-VC efforts under
RTC direction.

Another issue is whether to incorporate digital certificates. It was agreed
that going the SAML route - versus digital certs - will do more to solve the
federation issue.

The next VidMid-VC WG conference call will follow in four weeks, on Monday,
June 13, 2005 at 11am ET.