Re: [Sip] Draft agenda, SIP at IETF 72

"Elwell, John" <john.elwell@siemens.com> Thu, 17 July 2008 07:10 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54E8D28C137; Thu, 17 Jul 2008 00:10:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFED928C140 for <sip@core3.amsl.com>; Thu, 17 Jul 2008 00:10:57 -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 gvZ9FTMBehbY for <sip@core3.amsl.com>; Thu, 17 Jul 2008 00:10:56 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 22E9328C139 for <sip@ietf.org>; Thu, 17 Jul 2008 00:10:56 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0K4500D8A2N15O@siemenscomms.co.uk> for sip@ietf.org; Thu, 17 Jul 2008 08:11:25 +0100 (BST)
Date: Thu, 17 Jul 2008 08:11:24 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <B70B8EAC-2BC3-446D-AB56-522871BD5B28@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0E9B5B7@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Draft agenda, SIP at IETF 72
Thread-Index: Acjnie9lUOfeRI5PRPKGl7qTbb99xwAUfFAA
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <E22BEE62-CA95-4FAC-839D-A4654950C404@softarmor.com> <B70B8EAC-2BC3-446D-AB56-522871BD5B28@nostrum.com>
Cc: SIP IETF <sip@ietf.org>, Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sip] Draft agenda, SIP at IETF 72
X-BeenThere: sip@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@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

My 3 (well, 4) most important topics:
- RFC 4474 issues
- INFO
- Next steps towards Draft
- UA loose route

John
 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Robert Sparks
> Sent: 16 July 2008 22:21
> To: Dean Willis
> Cc: SIP IETF; Cullen Jennings
> Subject: Re: [Sip] Draft agenda, SIP at IETF 72
> 
> This is a really good place to start bashing from. Thanks for going  
> through the pain it takes to put this together.
> 
> Everyone should take note that the second session has a RAI conflict
> (with DRINKS) and think through where to put conversations so that
> we minimize the pain caused by the necessary split of people.
> 
> I think I'd rather see the large, architectural questions,
> INFO and Identity, moved into the conflict free spot and
> put topics with a smaller constituency into the second session.
> 
> I also think people across the working group should chime in 
> with what  
> they think
> the three most important _DRAFTS_ to talk about, in person, at this  
> meeting are.
> I strongly suspect there's a surprise or two that will come 
> out of that.
> 
> I'll throw my own list in later (because I want to think 
> awhile about  
> what's _not_
> in the proposed agenda), but to help tune things early:
> 
> I do want to talk about 199.
> 
> I don't see why we should spend face time on sip-keep at this point.
> 
> I think we can get away without face time on record-route fix.
> (its unlikely at this late stage that we'll find a crisis to work  
> through there).
> 
> I have received very little feedback on invfix, and I don't think
>      we need to spend any in-meeting time on the essential
>      corrections process itself. So, I propose we take that entire
>      topic to the list and/or hallways. I'll take on pushing a few
>      key folks to review the big recent changes to invfix and
>      speak up that they've done so before we get to the meetings.
> 
> Everybody else: If you hold the token on any of the other drafts and  
> feel you can
>   resolve any issues you currently have the same way, I strongly urge
>   you to propose something similar for your time.
> 
> 
> RjS
> 
> 
> 
> On Jul 16, 2008, at 10:45 AM, Dean Willis wrote:
> 
> >
> > This is the draft agenda for the SIP meeting at IETF 72 in Dublin.
> >
> > * Note that this agenda is subject to change based on list  
> > conversations
> >
> > * Note that we're still trying to work out how to have the  
> > "Identity" discussion
> >
> > Pretty HTML is at:
> > http://www.softarmor.com/mediawiki/index.php/SIP_Agenda_IETF_72
> >
> > Text follows
> >
> > -----------------
> >
> > Agenda for SIP at IETF 72, Primary Session, Tuesday July 29, 2008,  
> > 1300-1500, Convention 3
> >
> > Agenda Bash
> > Chairs
> > 10
> >
> > Using SAML for SIP
> > Chairs
> > draft-ietf-sip-saml-04
> > 10
> >
> > Identify requirements for test matrix to move SIP to Draft Standard
> > Robert Sparks
> > draft-sparks-sip-steps-to-draft-00
> > 20
> >
> > Essential corrections to RFC 3261 (1st batch)
> > Robert Sparks
> > draft-sparks-sip-invfix-02
> > 15
> >
> > Delivery of Request URI and Parameters to UAS Through Proxy
> > Speaker TBD
> > draft-rosenberg-sip-ua-loose-route-02
> > draft-holmberg-sip-target-uri-delivery-01
> > 25
> >
> >
> > Mechanisms for UA Initiated Privacy
> > Mayumi Munakata
> > draft-ietf-sip-ua-privacy-02
> > 15
> >
> > MIME body handling in SIP
> > Gonzalo Camarillo
> > draft-ietf-sip-body-handling-02
> > 15
> >
> > Guidelines for double route recording
> > Thomas Froment
> > draft-ietf-sip-record-route-fix-03
> > Time TBD
> >
> > Keepalive Without Outbound
> > Christer Holmberg
> > draft-holmberg-sip-keep-01
> > 10
> >
> >
> > Agenda for SIP at IETF 72, Primary Session, Thursday July 
> 31, 2008,  
> > 1510-1610, Convention 3
> >
> > Agenda Bash
> > Chairs
> > 5
> >
> > Termination of early dialog prior to final response
> > Christer Holmberg
> > draft-ietf-sip-199-00
> > 20
> >
> > INFO
> > Speaker TBD
> > draft-burger-sip-info-02
> > draft-kaplan-sip-info-events-01
> > draft-rosenberg-sip-info-litmus-01
> > draft-kaplan-sipping-dtmf-package-00
> > draft-willis-sip-infopackage-00
> > 35
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@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@cs.columbia.edu for questions on current sip
> Use sipping@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@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip