Dave, I explain the change with two figures in order not to be misunderstood (again). I use SIP as an example; Jonathan gave a nice presentation. Working Assumption previously: ............................ .............................. . . . . . +-------+ . . +-------+ . . | | . SIP . | | . . | Proxy |------------- | Proxy | . . | 1 | . . | 2 | . . | | . . | | . . / +-------+ . . +-------+ \ . . / . . \ . . / . . \ SIP . . SIP / . . \ . . / . . \ . . / . . \ . . / . . \ . . / . . \ . . +-------+ . . +-------+ . . | | . . | | . . | | . . | | . . | UA 1 | . . | UA 2 | . . | | . . | | . . +-------+ . . +-------+ . . Domain A . . Domain B . ............................ .............................. Figure 1: The SIP trapezoid We have lots of standardization efforts that focus on the UA<->Proxy leg in the RAI area. Suggested new working assumption: +-----------+ +-----------+ | Web/ | | Web/ | | SIP | SIP | SIP | | |-------------| | | Server | | Server | | 1 | | 2 | +-----------+ +-----------+ / \ / \ Proprietary over / \ HTTP/Websockets / \ / Proprietary over \ / HTTP/Websockets \ / \ +-----------+ +-----------+ |JS/HTML/CSS| |JS/HTML/CSS| +-----------+ +-----------+ +-----------+ +-----------+ | | | | | | | | | Browser | ------------------------- | Browser | | | Media | | | | | | +-----------+ +-----------+ Figure 2: Browser RTC Trapezoid The server-to-server interaction I was referring to in my previous mail is the interaction between server 1 to server 2. With cross-domain usage there still a standardization need. This is what I mean by "the interoperability need shifts". We had spoken about the implications of that change already. Ciao Hannes
|
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf