[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Late Milestones (was Re: Draft agenda, SIP at IETF 72)
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: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] 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
> sip-implementors at cs.columbia.edu for questions on current sip
> Use sipping at ietf.org for new developments on the application of sip
>
____________________________From sip-bounces at ietf.org Sun Jul 20 09:33:46 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 1313B3A68C3;
Sun, 20 Jul 2008 09:33:46 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 363FD3A68C3
for <sip at core3.amsl.com>; Sun, 20 Jul 2008 09:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id MvzFvgaCA8TC for <sip at core3.amsl.com>;
Sun, 20 Jul 2008 09:33:43 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
by core3.amsl.com (Postfix) with ESMTP id 1CE0A3A6841
for <sip at ietf.org>; Sun, 20 Jul 2008 09:33:42 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m6KGYAc6000964;
Sun, 20 Jul 2008 11:34:10 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830);
Sun, 20 Jul 2008 11:34:10 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by
DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830);
Sun, 20 Jul 2008 18:34:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 20 Jul 2008 18:34:07 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002142B24 at DEEXC1U01.de.lucent.com>
In-Reply-To: <E2935488-AF73-457C-B333-6AD30FA684AC at softarmor.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] Late Milestones (was Re: Draft agenda, SIP at IETF 72)
Thread-Index: Acjo/Qs86ZlYFfAlRRCszX4iAGVjbwAOxWbA
References: <E22BEE62-CA95-4FAC-839D-A4654950C404 at softarmor.com><B70B8EAC-2BC3-446D-AB56-522871BD5B28 at nostrum.com><0D5F89FAC29E2C41B98A6A762007F5D0E9B5B7 at GBNTHT12009MSX.gb002.siemens.net><E6C2E8958BA59A4FB960963D475F7AC30EFF77827F at mail.acmepacket.com><487FA6A9.7070208 at cisco.com><D974C1F8-1BE4-40A7-ABF7-56B02D08F875 at softarmor.com><0D5F89FAC29E2C41B98A6A762007F5D0E9BBC2 at GBNTHT12009MSX.gb002.siemens.net>
<E2935488-AF73-457C-B333-6AD30FA684AC at softarmor.com>
From: "DRAGE, Keith \(Keith\)" <drage at alcatel-lucent.com>
To: "Dean Willis" <dean.willis at softarmor.com>,
"Elwell, John" <john.elwell at siemens.com>
X-OriginalArrivalTime: 20 Jul 2008 16:34:07.0699 (UTC)
FILETIME=[6E4B1230:01C8EA86]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <sip at ietf.org>
Subject: Re: [Sip] Late Milestones (was Re: Draft agenda, SIP at IETF 72)
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
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___________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
Keith
> -----Original Message-----
> From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] 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
> sip-implementors at cs.columbia.edu for questions on current sip
> Use sipping at ietf.org 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 sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip