RE: RTPSec BOF proposal for IETF 68

["Dan Wing" <dwing@xxxxxxxxx>]

Lakshminath,

> Some notes:  IIRC, in Montreal, we ran out of time on getting
> opinions on some of the open issues.  RTP and RTCP was one that we
> dealt with in San Diego (has that been decided?). 

If you're referring to keying in the RTP path (DTLS, ZRTP, MIKEYv2) or RTCP
path (EKT), I believe there was consensus that it was okay to key in the RTP
path, with some expressing distaste about its lack of purity.

> Any other open issues anyone recalls?

We have several open issues in draft-wing-media-security-requirements, and
some issues that are for future study.  We are going to update that document
for the upcoming meeting, as some of the open issues and some of the text is
not sufficiently clear.

> Next, do we have a consensus set of evaluation criteria now to weigh
> the solution drafts against?  It would be good to publish that soon
> in some form (probably as an update to Dan and Francois's draft?)

We need to evaluate protocols based on a consensus of the requirements for
an Internet protocol.  I don't think draft-wing-media-security-requirements
has had sufficient review or consensus yet.

The draft Francois and I wrote (draft-wing-rtpsec-keying-eval) can be used
to evaluate the proposals against the requirements.  We will be publishing
an update to it for this IETF (delete DTLS-RTP, which has been dropped by
its authors; clean up some cruft).

Of course, if new keying mechanisms are published we'll need at least a few
days to integrate them!

-d