Greetings all -
In addition to the main peer-to-peer testing that dominates
the SIPIT, we hold a series of multiparty tests off to the side
to focus on those scenarios that require coordinating more than
two or three implementations. There is no need to sign up for
these tests (other than registering to attend the SIPIT). Just
show up at the multiparty test tables when the tests you are
interested in are scheduled. You will be dedicating an entire
morning or afternoon to each test you participate in.
Here is the current schedule for the multiparty tests at SIPIT 11.
I've received a couple of requests to hold a test focusing on
transfer scenarios - if I get more, we'll add a transfer test
doubling up against one of the below tests.
AM PM
Monday (none) Forking
Tuesday STUN Spirals
Wednesday New Extensions SIGCOMP
Thursday IPV6 SIMPLE
Friday (none)
Below are summaries of what we do at these tests:
Multi-proxy forking
These scenarios exercise calls parallel forking through
multiple proxies, switching between transport mechanisms
at each hop. The tests stress exercising
* Via formation (including branch) and parsing
* hop-hop non-200 final responses and ACKs
* e-e 200 final responses and ACKs
* Propogation of client initiated CANCEL
* CANCEL of outstanding branches after
forwarding final response
* Multiple 200 OK responses
* Aggregation of 401/407 Challenges
* Route/Record-Route
* Loose Routing
* Preloaded Routes
* non-UDP/TCP transports
* early media
Who should attend:
Any endpoint implementation (including gateways)
Any proxy capable of parallel forking, particularly
those supporting more than one transport protocol
A typical scenario involves 5-7 endpoints and 3-5
proxies.
Spiral/Loop/Merge
These scenarios focus on requests that are routed
through proxies more than once. The tests stress
exercising
* Via formation and parsing
* Route/Record-Route
* Loop detection
* Spiral processing
* Merge resolution at endpoints.
* hop-hop non-200 final responses and ACKs
* e-e 200 final responses and ACKs
* Propogation of client initiated CANCEL
* non-UDP/TCP transports (if available)
* Very large SIP messages
Who should attend:
Any endpoint or proxy implementation.
A typical scenario involves 2 endpoints and 4-8 proxies.
SigComp
These scenarios focus on sending and receiving SIP messages
that have been compressed using the SigComp protocol. The
tests stress excercising:
* Sucessful compression and decompression of SIP messages
using SigComp over UDP.
* Sucessful compression and decompression of SIP messages
using SigComp over TCP.
* Proper handling of ";comp=sigcomp" parameter on Via headers.
* Proper handling of ";comp=sigcomp" parameter on URIs.
* Proper proxy handling of interaction between ";comp=sigcomp"
parameter on URIs and Route/Record-Route handling.
* Protocol stability and recovery under high traffic situations.
* Negotiation of SigComp shared state (e.g. static dictionaries).
Who should attend:
Any endpoint or proxy with SigComp.
A typical scenario will involve three to five nodes
New Extensions:
This period focuses on bringing together people that have
the first implementations of emerging standards. What we
test depends on what implementations show up. At SIPIT 11,
we anticipate testing at least UPDATE,
IPV6:
This session will focus on IPV6 implementations using the
forks and spirals tests as models. If possible, we'll look
at scenarios that cross a V4/V6 boundary.
STUN:
This session will focus on scenarios with NATs between SIP elements.
SIMPLE:
This session will focus on new development in SIMPLE implementations.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
