Couple items for the list that popped to my mind (based on my share of interop 
issues I've seen) :


 *   Demonstrate correct recognition of when to retry requests and when to give 
up (401/423/403/480/500/503 etc use cases)
 *   Demonstrate correct implementations of retrying requests after the 
specified time internal when servers are busy/overloaded etc

Serhad

________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of Robert 
Sparks
Sent: Monday, March 02, 2009 12:19 PM
To: SIP List
Subject: [Sip] Fwd: I-D Action:draft-sparks-sip-3261-interop-statement-00.txt

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.
_______________________________________________
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

Reply via email to