Re: [rtcweb] Use Case draft - legacy interop

[Harald Alvestrand <[e-mail]>]

(changing subject line to fork thread)

On 05/03/2012 03:06 PM, Jim Barnett wrote:
> Yes, the use cases in  4.3 are browser-GW, though none of them really
> covers the call center case (routing to an arbitrary agent, recording
> the call, etc.)
>
> However, the requirements in section 5 don't seem to mention legacy
> connectivity, unless that's what F27 is supposed to cover ("The browser
> MUST be able to initiate and accept a media session where the data
> needed for establishment can be carried in SIP.")  It might be good to
> have a specific legacy requirement along the forms of "The Browser must
> be able to communicate with legacy devices that have the following
> characteristics ...." Of course, this gets into the whole
> interoperability discussion. For example, should the Browser be able to
> interoperate with devices that don't support  ICE?  (I have been
> assuming that the call center gateway would  support ICE).
My memory of our last rounds of discussion was that we decided not to 
have a non-gateway legacy interop case because
a) given the variety of legacy equipment, it would basically require a 
specific device as the "interop partner" (a rathole), and
b) it would bind the architecture of RTCWeb in ways that might prevent 
us from achieving our goals in other ways (especially security issues).

YMMV.