Re: Fwd: I-D Action:draft-sparks-sip-3261-interop-statement-00.txt

On Mar 21, 2009, at 7:28 AM, Jonathan Rosenberg wrote:

> Thanks, Robert.
>
> Before commenting on the specific list of things, my meta-question  
> is what exactly we plan to do with this list. I think we have agreed  
> at previous meetings that we were not currently planning on taking  
> SIP to draft. Do you think that has changed?
>
> The document does say:
>
>> While not required by process until
>>   advancing to Draft, such a report would provide useful  
>> information to
>>   guide where we focus our energy maintaing the standard at Proposed.
>
> its not clear to me, what this means. Will we take this list, run  
> tests at sipit, and based on that define updates to 3261 to clarify?  
> Does this imply that there are tests we're NOT running which we  
> should be, that this draft helps us sort out?

Yes - what I'm currently planning to do is start to collect interop  
statements on this list, evolve the list over time, and use that body  
of information to further inform what's implemented, what's giving  
people trouble, and what's not being used.

>
>
> Thanks,
> Jonathan R.
>
> Robert Sparks wrote:
>> Also split out of steps-to-draft
>> Begin forwarded message:
>>> *From: *[email protected] <mailto:[email protected]>
>>> *Date: *March 2, 2009 8:30:02 AM CST
>>> *To: *[email protected] <mailto:[email protected]>
>>> *Subject: **I-D Action:draft-sparks-sip-3261-interop- 
>>> statement-00.txt *
>>> *Reply-To: *[email protected] <mailto:[email protected] 
>>> >
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts  
>>> directories.
>>>
>>> Title           : RFC3261 Interop Statement
>>> Author(s)       : R. Sparks
>>> Filename        : draft-sparks-sip-3261-interop-statement-00.txt
>>> Pages           : 9
>>> Date            : 2009-03-02
>>>
>>> This document captures an outline of the interoperability statements
>>> that will be collected to construct an interoperability report for
>>> RFC 3261.  The outline is stil under review and should not be  
>>> treated
>>> as complete, but will drive data collection at upcoming
>>> interoperability events.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-sparks-sip-3261-interop-statement-00.txt
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> Below is the data which will enable a MIME compliant mail reader
>>> implementation to automatically retrieve the ASCII version of the
>>> Internet-Draft.
>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> ------------------------------------------------------------------------
>> _______________________________________________
>> 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
>
> -- 
> Jonathan D. Rosenberg, Ph.D.                   111 Wood Avenue South
> Cisco Fellow                                   Iselin, NJ 08830
> Cisco, Voice Technology Group
> [email protected]
> http://www.jdrosen.net                         PHONE: (408) 902-3084
> 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 [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip