Re: [rtcweb] Definitions of WebRTC entities

Harald Alvestrand <harald@alvestrand.no> Thu, 09 October 2014 06:58 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADE81A9133 for <rtcweb@ietfa.amsl.com>; Wed, 8 Oct 2014 23:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level:
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPiJRk0-_Dzd for <rtcweb@ietfa.amsl.com>; Wed, 8 Oct 2014 23:58:34 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE141A9117 for <rtcweb@ietf.org>; Wed, 8 Oct 2014 23:58:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 1155E7C09ED; Thu, 9 Oct 2014 08:58:33 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19lRzdC2RCri; Thu, 9 Oct 2014 08:58:32 +0200 (CEST)
Received: from [172.30.42.85] (c-58f0e555.03-217-73746f1.cust.bredbandsbolaget.se [85.229.240.88]) by mork.alvestrand.no (Postfix) with ESMTPSA id F0ADF7C09DD; Thu, 9 Oct 2014 08:58:31 +0200 (CEST)
Message-ID: <54363216.3060700@alvestrand.no>
Date: Thu, 09 Oct 2014 08:58:30 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Parthasarathi R <partha@parthasarathi.co.in>, 'Christer Holmberg' <christer.holmberg@ericsson.com>, rtcweb@ietf.org
References: <542E53D2.5040500@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D465376@ESESSMB209.ericsson.se> <C45C84E3-FC63-4DF6-ABDE-701FC7584E3C@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D465985@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D465A34@ESESSMB209.ericsson.se> <00f501cfe24a$b8515930$28f40b90$@co.in> <543418D5.8010509@alvestrand.no> <006301cfe316$6d3c5590$47b500b0$@co.in>
In-Reply-To: <006301cfe316$6d3c5590$47b500b0$@co.in>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/sVnMdKkEyOZnBVps7-luzxVFetE
Subject: Re: [rtcweb] Definitions of WebRTC entities
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Oct 2014 06:58:36 -0000

On 10/08/2014 06:39 PM, Parthasarathi R wrote:
> Hi Harald,
>
> Please read inline.
>
> Thanks
> Partha
>
>> -----Original Message-----
>> From: Harald Alvestrand [mailto:harald@alvestrand.no]
>> Sent: Tuesday, October 07, 2014 10:16 PM
>> To: Parthasarathi R; 'Christer Holmberg'; rtcweb@ietf.org
>> Subject: Re: [rtcweb] Definitions of WebRTC entities
>>
>> On 10/07/2014 06:21 PM, Parthasarathi R wrote:
>>> Hi Christer,
>>>
>>> I have no issue with WebRTC User Agent, WebRTC device, WebRTC
>> endpoint.
>>> I have bit trouble with WebRTC compatible endpoint as a entity name
>> as
>>> 1) It may pass SRTP/data channel
>> What do you mean by "pass"? That's a slippery term.
> <Partha> "relay" will be more appropriate term as mentioned in Sec 5 Para 2 of draft-alvestrand-rtcweb-gateways. </Partha>
>
>>> 2) It is not required to be endpoint but it shall be middle box.
>> What do you mean by "middle box"? Again, that term is slippery.
> <Partha> I intent to say that the entity which is between two endpoints and it does not end any media session itself. Here, The confusion is that WebRTC compatible endpoint which is not an endpoint but it is a middle box. </Partha>

Seems that this entity (whatever it's called) isn't an endpoint at all,
so defining terms for endpoints shouldn't be relevant to whatever this
device is.

There's always more boxes in the middle..... although as long as they
don't have the DTLS keys, it's limited what they can do to the packets.



>
>>> WebRTC gateway looks more appropriate entity name in those scenarios.
>> As written in my proposal, a WebRTC gateway is a WebRTC compatible
>> endpoint.
>>
> <Partha> As per your proposal, we need to define WebRTC compatible endpoint first which is super set of WebRTC gateway. Then, we need to clarify which kind of WebRTC compatible endpoint qualify as WebRTC gateway. But Christer wishes to have only two definition (Full/Subset).  </Partha>

And I don't agree with Christer, so then we're two :-)