Re: [rtcweb] Definitions of WebRTC entities

"Parthasarathi R" <partha@parthasarathi.co.in> Wed, 15 October 2014 00:29 UTC

Return-Path: <partha@parthasarathi.co.in>
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 8FA981A00CA for <rtcweb@ietfa.amsl.com>; Tue, 14 Oct 2014 17:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level:
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] 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 fNgmXOPyCtU8 for <rtcweb@ietfa.amsl.com>; Tue, 14 Oct 2014 17:29:48 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.27]) by ietfa.amsl.com (Postfix) with ESMTP id 96C021A00BE for <rtcweb@ietf.org>; Tue, 14 Oct 2014 17:29:47 -0700 (PDT)
Received: from userPC (unknown [122.167.224.12]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id D2ED33C0050; Wed, 15 Oct 2014 00:29:42 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1413332987; bh=rR7TAeE/lCAnx5ZjomXBwQ50cH6gdriQpi5nRjR2jyw=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=OttYuI2tE7OegFOlJxe9BCGWZZA9OK6SnSwARG+dTqe9WtWMdzoBtIiVZzDoRUI/c evWAmKi4d3irOECdnxaiBkVCSyykJ78d/EXmQGG7Gz42+SBJCMp4oKzbysZy8WR/dt G9rpg/kxXA0SnA3WslVkH6INav9ubq5ArIu44pD0=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: 'Harald Alvestrand' <harald@alvestrand.no>, '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> <54363216.3060700@alvestrand.no>
In-Reply-To: <54363216.3060700@alvestrand.no>
Date: Wed, 15 Oct 2014 05:59:36 +0530
Message-ID: <010d01cfe80f$1c8e3930$55aaab90$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/jjnVOK+o8w9MwT86r1SubD5TE7wEgC5NQ
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020205.543DBFFB.00E7, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: C_4847,
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/4qFgmZVGyh-ZGySy0f4EccJZPkU
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: Wed, 15 Oct 2014 00:29:52 -0000

Hi Harald,

<snip>
>>> 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.
<snip>

Could you please update the terminology as "WebRTC compatible device" instead of WebRTC compatible endpoint as the entity is not required to be endpoint.

Thanks
Partha.



> -----Original Message-----
> From: Harald Alvestrand [mailto:harald@alvestrand.no]
> Sent: Thursday, October 09, 2014 12:29 PM
> To: Parthasarathi R; 'Christer Holmberg'; rtcweb@ietf.org
> Subject: Re: [rtcweb] Definitions of WebRTC entities
> 
> 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 :-)