Re: [rtcweb] Regarding Federation Arguments

[Bernard Aboba <[e-mail]>]

[BA]  I don't understand that sentence either, partly because it's not clear to me what "this" refers to.  The previous sentence talks about "the signaling path needs to be agreed upon, either by standardization or by other means of agreement", but also talks about "their proprietary representation".  Is "this" referring to the former or the latter?   Here's a rewrite that makes more sense (at least to me):  "If the two Web servers are operated by different entities, the inter-domain signalling mechanism needs to be agreed upon, either by standardization or by other means of agreement.  Existing protocols that support federation (SIP or XMPP) could be used to enable inter-domain federation between servers, while either a standards-based or proprietary protocol could be used between the browser and the web server.  For example, if both domains implement SIP,  SIP could be used for inter-domain communication between servers, along with either a standardized signaling mechanism (e.g. SIP over Websockets) or a a proprietary signaling mechanism used between the application running in the browser and the web server.   Similarly, if both domains implement XMPP, XMPP couild be used for inter-domain communication between XMPP servers, with either a standardized signaling mechanism (e.g. XMPP over Websockets or BOSH) or a proprietary signaling mechanism used between the application running in the browser and the web server."   Cullen said: "I don't understand the meaning of the sentence 
 
This part is outside the scope of the RTCWEB standards suite.

I think we need to construct a solution that can work if domains want to federate with SIP - therefore this should be one our use cases. However, I think domain should be free to choose whatever they want to federate - it just needs to be possible to federate. I'd like to see this clarified."
  ============================================================== "If the two Web servers are operated by different entities, the
signalling path needs to be agreed upon, either by standardization or
by other means of agreement; for example, both servers mightimplement SIP, and the servers would talk SIP to each other, and eachwould translate between the SIP protocol and their proprietary
representation for sending to their application running in the
browser.This part is outside the scope of the RTCWEB standars
suite."