Re: [Sipping] Testing the water: A transaction torture-tests draft

	I was thinking a torture-tests draft in the same spirit as RFC 4475  
and draft-ietf-sipping-ipv6-torture-tests; an enumeration of test- 
cases that could cause trouble for an unsuspecting implementation,  
with exposition on what makes the case interesting, and how  
implementations should react. Of course, the tests themselves would  
read differently, since the contents of the messages won't matter  
apart from stuff like the method and branch params.

Best regards,
Byron Campen

>    From: Byron Campen <bcampen@estacado.net>
>
>    I have doing a lot of work lately on hardening a SIP stack, and I
>    have repeatedly come across bugs triggered not by syntactic garbage
>    (malformed header-field-values and the like), but by semantic
>    garbage, usually in the form of transaction collisions. I'm trying
>    to get a feel for working-group interest on the subject, so let me
>    know what you think.
>
> It's obviously very valuable work.  What are you proposing?
>
> Dale
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

Re: [Sipping] Testing the water: A transaction torture-tests draft

Attachment: smime.p7s