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

[Jonathan Rosenberg <[e-mail]>]

I would also suggest the same list. And in particular, if we don't make 
a lot of progress on INFO and rfc4474, we have wasted our time. Those 
two IMHO should cover 75% of our meeting time. Having a bunch of 10 
minute presentations, each of which is on a topic that only three people 
care about, is not a good use of everyones time. Those two topics 
clearly have big impact on SIP as a whole and are of broad interest.

-Jonathan R.


Hadriel Kaplan wrote:
> My list is the same as John's, fwiw.
> I'm also very surprised SIP can be scheduled in conflict with any other RAI WG, especially a brand new one. :(
> 
> -hadriel
> 
>> -----Original Message-----
>> From: [e-mail] [mailto:[e-mail]] On Behalf Of
>> Elwell, John
>> Sent: Thursday, July 17, 2008 3:11 AM
>> To: Robert Sparks; Dean Willis
>> Cc: SIP IETF; Cullen Jennings
>> Subject: Re: [Sip] Draft agenda, SIP at IETF 72
>>
>> My 3 (well, 4) most important topics:
>> - RFC 4474 issues
>> - INFO
>> - Next steps towards Draft
>> - UA loose route
>>
>> John
>>
>>
>>> -----Original Message-----
>>> From: [e-mail] [mailto:[e-mail]] 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 [e-mail] for questions on current sip
>>>> Use [e-mail] 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 [e-mail] for questions on current sip
>>> Use [e-mail] 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 [e-mail] for questions on current sip
>> Use [e-mail] 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 [e-mail] for questions on current sip
> Use [e-mail] for new developments on the application of sip
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
[e-mail]
http://www.jdrosen.net                         PHONE: [phone]
http://www.cisco.com
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [e-mail] for questions on current sip
Use [e-mail] for new developments on the application of sip