Re: [sipcore] Milestone to revise RFC 3265: Conclusion

Folks,

the WG item version of this draft has just been submitted. I would like 
to see discussions about the scope of this effort, per my previous email 
below.

http://www.ietf.org/id/draft-ietf-sipcore-rfc3265bis-00.txt

Thanks,

Gonzalo
SIPCORE co-chair

Gonzalo Camarillo wrote:
> Hi,
> 
> based on all the responses received, there is agreement that the WG 
> should work on revising RFC 3265 and that this draft is a good starting 
> point for that. Therefore, I will ask our ADs to add a milestone to 
> revise RFC 3265 and the author of the draft to submit it as a SIPCORE WG 
> item.
> 
> Keith brought up two good questions about the scope of this effort that 
> we need to resolve (while he agrees on a limited-scope update that would 
> preserve backwards compatibility, he would object to a wider scope). The 
> first discussions on this topic need to deal with those questions in 
> order to reach an agreement on the actual scope of this effort.
> 
> Thanks,
> 
> Gonzalo
> SIPCORE cochair
> 
> 
> Gonzalo Camarillo wrote:
>> Folks,
>>
>> since the publication of RFC 3265, we have gotten significant 
>> experience deploying SIP-based notification systems. It has been 
>> proposed to revise RFC 3265 based on that experience. We have two 
>> questions for the WG:
>>
>> 1) should we add a milestone to our charter to revise RFC 3265?
>>
>> 2) if we add such a milestone, should we take the following draft as 
>> the initial WG item for the milestone?
>>
>> http://tools.ietf.org/html/draft-roach-sipcore-rfc3265bis-00
>>
>> Thanks,
>>
>> Gonzalo
>> SIPCORE co-chair
>> _______________________________________________
>> sipcore mailing list
>> sipcore@ietf.org
>> https://www.ietf.org/mailman/listinfo/sipcore
>>
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 