Re: [rtcweb] WebRTC endpoint categories

Gaelle Martin-Cocher <> Thu, 11 December 2014 22:41 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id F3F791A89AF for <>; Thu, 11 Dec 2014 14:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id p7Dbt8YBDxV6 for <>; Thu, 11 Dec 2014 14:41:09 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id D45F41A1BE7 for <>; Thu, 11 Dec 2014 14:41:08 -0800 (PST)
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 11 Dec 2014 17:41:03 -0500
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 11 Dec 2014 17:41:02 -0500
Received: from ([fe80::fcd6:cc6c:9e0b:25bc]) by ([::1]) with mapi id 14.03.0210.002; Thu, 11 Dec 2014 17:41:02 -0500
From: Gaelle Martin-Cocher <>
To: Sergio Garcia Murillo <>, "" <>
Thread-Topic: [rtcweb] WebRTC endpoint categories
Thread-Index: AQHQFM0kak8mo4J6FkamLzsTItyLlZyJylqAgAEt3QA=
Date: Thu, 11 Dec 2014 22:41:02 +0000
Message-ID: <>
References: <> <> <> <> <> <20141210012208.GK19538@hex.shelbyville.oz> <> <20141210200027.GM19538@hex.shelbyville.oz> <> <20141210230012.GN19538@hex.shelbyville.oz> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-CA, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [rtcweb] WebRTC endpoint categories
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Dec 2014 22:41:11 -0000

Answering your questions below with [gmc] and repeating myself, sorry.

-----Original Message-----
From: rtcweb [] On Behalf Of Sergio Garcia Murillo
Sent: Wednesday, December 10, 2014 6:22 PM
Subject: Re: [rtcweb] WebRTC endpoint categories

Also, I hear some people complaining about the definition of a WebRTC compatible endpoint, but it would be good if those people expose what are the changes that they want to introduce:
  -Remove webrtc compatible endpoints mentions from spec 
[gmc] for me, that is an option if 'WebRTC-compatible endpoint' is not better defined.
Currently that unclear category correspond to both ‘meaningful’ entities (gateway, current WebRTC librairies, or Ron’s coffee maker) and possibly some sub-standard implementation.

  -Change definition of a webrtc compatible endpoint 
[gmc] yes, or actually clearly set out the requirements that apply to them. As said before: The WebRTC gateway in is defined as a WebRTC-compatible endpoint with some requirements being applied to it.
I am not sure how the last sentence in the WebRTC-compatible endpoint definition  “It is not constrained by this specification…”  applies to the gateway.
Proposal A: define in a draft the minimal requirements that apply to a WebRTC-compatible endpoint to “successfully communicate with a WebRTC endpoint”.    This draft can be an extension of the gateway draft.
Proposal B:  the WebRTC gateway could be removed from the WebRTC-compatible endpoint category and called a webRTC gateway with its own draft. As, there might be enough differences to  justify two entities, there would be the gateway draft and a draft for WebRTC-compatible endpoint as in proposal A.
Changing the naming of “WebRTC-compatible” to a less confusing term is a cosmetic change (but might be a good thing).

  -Mandate webrtc compatible enpoints to implement both MTI video codecs
[gmc] No. 

Proposal C: allow an endpoint that do not required some functions (by function it means that function in its entirety) to be called a WebRTC endpoint.
Example: an endpoint that does not need to do audio at all is a webRTC endpoint. An endpoint that chose to implement a single audio codec out of the two MTI audio codec is not a WebRTC endpoint.


Best regards

rtcweb mailing list