Re: SIP bakeoff registration now open

[Colin Perkins <[e-mail]>]

--> Francois Menard List Account writes:
>Would that also include RTCP compatibility tests ?

In order to progress RTP to draft standard it is necessary to demonstrate
interoperability of all options and features of the protocol. Accordingly,
we need to have demonstrated RTCP along with the other features of RTP.
Note that this doesn't imply that every implementation must implement every
feature of RTP (although I would hope that all implement at least a minimal
subset of RTCP), rather that every feature must be implemented in at least
two implementations.

Colin



>On Thu, 2 Mar 2000, Colin Perkins wrote:
>
>> --> Henning Schulzrinne writes:
>> >http://www.sipbakeoff.org/4/ has details. Please contact Terri Cali
>> >(cc'ed) with any questions.
>> >
>> >I look forward to seeing many of you at the bake-off. 
>> >
>> >I'd also appreciate feedback on whether and to what extent we should
>> >test more formally for RTP interoperability at this event. This has
>> >become an issue as we cannot progress RTP to draft status without more
>> >implementations that comply. Since a phone that only rings but doesn't
>> >"talk" is of somewhat limited use, this might be of some interest. (This
>> >would obviously only affect UAs, not servers.)
>> 
>> I'd strongly support moves to perform RTP interoperability testing at the
>> SIP bakeoff. The AVT working group has produced a number of internet drafts
>> listing those features which would need to be tested and suggesting testing 
>> procedures:
>> 
>> 	draft-ietf-avt-rtp-interop-02.txt
>> 	draft-ietf-avt-profile-interop-00.txt
>> 	draft-ietf-avt-rtptest-02.txt
>> 
>> And as Henning says, this demonstration must be completed before the revised 
>> RTP specification can become an RFC. 
>> 
>> I would also encourage vendors who have performed in-house interoperability
>> testing of RTP implementations to consider making this information available
>> to the AVT working group chairs, so we can complete the interoperability
>> requirements (we're aware that some vendors have concerns with making this
>> available - contact us, and we can work to address them).
>> 
>> Colin
>>