Howdy,
I have submitted a rough draft for a BCP for implementers to improve SIP interoperability.
Before you flame me for restricting SIP or having some evil intention against some practice your implementation happens to do, understand that:
a) this is just a first draft (though it's labeled version 01)
b) this is just a strawman, for discussion
c) interop problems are getting worse not better
d) interop problems are bad for us all, because it harms SIP's rep
e) this is a bit of a rushed job, and I haven't proof-read it well due to time constraints (I have a day job, like anyone)
f) I am flame resistant (of the email variety, anyway)
As always, comments/criticism/sarcasm/flames are welcomed.
Have a nice day. :)
-hadriel
> -----Original Message-----
> From: i-d-announce-bounces@xxxxxxxx [mailto:i-d-announce-bounces@xxxxxxxx]
> On Behalf Of Internet-Drafts@xxxxxxxx
> Sent: Monday, March 09, 2009 1:00 AM
> To: i-d-announce@xxxxxxxx
> Subject: I-D Action:draft-kaplan-sipping-interop-bcp-01.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
> Title : Best Current Practices for SIP Interoperability
> Author(s) : H. Kaplan
> Filename : draft-kaplan-sipping-interop-bcp-01.txt
> Pages : 13
> Date : 2009-03-08
>
> This document identifies several commonly found interoperability
> issues with SIP, and provides guidance to implementers for how to
> avoid them. This is an initial set of commonly found problems.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kaplan-sipping-interop-bcp-
> 01.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.
This attachment was removed.
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP