At Fri, 29 Feb 2008 12:29:42 -0600, Dean Willis wrote: > > > On Feb 29, 2008, at 5:00 AM, DRAGE, Keith (Keith) wrote: > > > > Media security requirements is holding up other chartered items in > > both > > SIP and AVT. When we considered this for inclusion, we believed there > > were two items that may need agenda item. Overnight Dean seems to have > > taken the time away at the moment, but I remain unconvinced that this > > does not need time. > > > > This is the media-security requirements milestones: > > > > Sep 2007 Requirements for media keying to WGLC (Informational) > > Nov 2007 Requirements for media keying to IESG (Informational) > > > > Which provides the requirements for the mechanism in these charter > > items > > in SIP. > > > > Dec 2007 Establishment of secure media sessions using DTLS-SRTP to > > WGLC (PS) > > Feb 2008 Establishment of secure media sessions using DTLS-SRTP to > > IESG (PS) > > > > And these chartered items in AVT: > > > > Dec 2007 Submit in band keying mechanism for SRTP draft for > > Proposed > > Standard > > It still has 30 minutes on the draft agenda, if I'm reading it > correctly. > > It's the framework draft (draft-ietf-sip-dtls-srtp-framework-01) that > currently doesn't have agenda time. The framework depends on the > requirements, right?
Well, sort of. To the extent to which we're discussing new requirements that might require modifying the technical content of the framework, yes. I'm not aware of any such requirements. To the extent to which we're discussing editorial changes that affect the "requirements analysis" at the end of the framework document (e.g., changing the name of requirements but not their content) then there's an editorial dependency, but I'm fine with having that analysis be against a given version of the requirements document. To the extent to which we're just wordsmithing the requirements document (for instance, discussing whether to remove the appendix), then no. -Ekr _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
