For the following two:
Sep 2008 X.509 Certificates for TLS use in SIP to IESG
-- Waiting on Keith
Sep 2008 X.509 extended key usage for SIP to IESG
-- Waiting on Keith
There has been a major change in domain-certs since WGLC which I am
waiting for enough people in the WG to read (and if necessary to object
to).
There is a potential further change coming in based on comments from
PKIX - see Vijay's message of a few days back.
And having worked my way through both of them, I will be trying to take
some time in Dublin with the editor's to clean a few things up!
Regards
Keith
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Dean Willis
> Sent: Friday, July 18, 2008 6:38 PM
> To: Elwell, John
> Cc: SIP IETF
> Subject: [Sip] Late Milestones (was Re: Draft agenda, SIP at IETF 72)
>
>
> On Jul 18, 2008, at 4:03 AM, Elwell, John wrote:
>
> > Dean,
> >
> > So these milestone items we are late on, how many of them are late
> > because they are held up waiting for face-to-face discussion?
>
> That's a good question. I'm having a hard time telling, since
> some (like SAML) don't seem to get a lot of list discussion either.
>
>
> Let's take a look:
>
> Jun 2007 Mechanism and guidelines for outbound connections to IESG
> -- Waiting on me
>
> Jul 2007 Example security flows to WGLC
> -- Waiting on author, I think
>
> Jul 2007 Location Conveyance with SIP to IESG
> -- Waiting on face-to-face, but in GEOPRIV
>
> Aug 2007 Connection reuse mechanism to IESG
> -- Waiting on Keith
>
> Sep 2007 Session Policies to IESG
> -- Waiting on Keith
>
> Sep 2007 Example security flows to IESG
> -- Waiting on WGLC
>
> Sep 2007 Using SAML for SIP to WGLC
> -- Not sure, maybe F2F?
>
> Nov 2007 Requirements for media keying to IESG
> -- Waiting on me
>
> Dec 2007 Extensions to SIP UA Profile Delivery Change
> Notification to IESG
> -- Hey, this one is done! I've just notified the
> secretariat. Yay!
>
> Dec 2007 Using SAML for SIP to IESG
> -- Waiting on the WGLC, which may be waiting on F2F
>
> Dec 2007 Extension for use in etags in conditional
> notification to IESG
> -- Waiting on the author. Somebody buy Aki a beer!
>
> Dec 2007 Delivering request-URI and parameters to UAS via
> proxy to WGLC
> -- DEFINITELY waiting on F2F
>
> Dec 2007 Establishment of secure media sessions using
> DTLS-SRTP to WGLC
> -- Waiting on author. Somebody buy EKR a babysitter!
>
> Feb 2008 Identify requirements for test matrix to move SIP to
> Draft Std
> -- Waiting on F2F. On current agenda.
>
> Feb 2008 Delivering request-URI and parameters to UAS via
> proxy to IESG
> -- Waiting on WGLC, which is waiting on F2F
>
> Feb 2008 Revise charter
> -- Waiting on some decisions WRT Identity, which is probably F2F
>
> Feb 2008 Establishment of secure media sessions using
> DTLS-SRTP to IESG
> -- Waiting on WGLC, which is waiting on author
>
> Apr 2008 MIME body handling in SIP to IESG
> -- I'm not exactly sure.
>
> Apr 2008 Essential corrections to RFC 3261 (1st batch) to IESG
> -- May or may not need F2F for invix
>
> May 2008 Mechanisms for UA initiated privacy to WGLC
> -- Waiting for F2F
>
> Jul 2008 Mechanisms for UA initiated privacy to IESG
> -- waiting for WGLC, which is waiting F2F
>
> Aug 2008 Guidelines for double route recording to IESG
> -- In WGLC from July 16, may or may not need F2F
>
> Sep 2008 X.509 Certificates for TLS use in SIP to IESG
> -- Waiting on Keith
>
> Sep 2008 X.509 extended key usage for SIP to IESG
> -- Waiting on Keith
>
> Sep 2008 Termination of early dialog prior to final response to WGLC
> -- Waiting on F2F
>
> Nov 2008 Termination of early dialog prior to final response to IESG
> -- Waiting on WGLC, hence on F2F
>
>
> So, it looks like we MAY require F2F time to advance the following:
>
> SAML
> Record-Route Fix?
> invfix (Essential Corrections #1)?
> Delivery of URI and Parameters to UAS Through Proxy
> Requirements for Test matrix to Move to Draft Revise Charter
> Body Handling?
> UA Initiated Privacy
> Termination of Early Dialog (which isn't "late" yet)
>
> The three "?" items (Record-Route, invfix, and Body Handling)
> are all in a WGLC cycle, so we don't know yet whether we he
> have critical F2F issues.
>
> --
> Dean
>
> _______________________________________________
> 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
>
_______________________________________________
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
