Re: [rtcweb] Definitions of WebRTC entities
Silvia Pfeiffer <silviapfeiffer1@gmail.com> Fri, 03 October 2014 20:41 UTC
Return-Path: <silviapfeiffer1@gmail.com>
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 9879A1A7014 for <rtcweb@ietfa.amsl.com>; Fri, 3 Oct 2014 13:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 MRL90EGXTmrh for <rtcweb@ietfa.amsl.com>; Fri, 3 Oct 2014 13:41:24 -0700 (PDT)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A238A1A6FDC for <rtcweb@ietf.org>; Fri, 3 Oct 2014 13:41:24 -0700 (PDT)
Received: by mail-yk0-f170.google.com with SMTP id 20so618612yks.15 for <rtcweb@ietf.org>; Fri, 03 Oct 2014 13:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fkjysYvqQmE4A2Ig6wTEY0055A+WH2pDN5oVFv6AaoY=; b=Gj+Utj/oaJyrI6Qt4WWt3Hg8rH8jv1CGbYSQpGB52Jgwj0LYPzdjdswAGupAOWCH+5 et3ECmRfqD6F5UusDVre05yXE1611gmWEZQ4KXeJ2/jp3EiwryMONYL1X1Fr8Pj6g7Mj x1EeEH5mXhJX+gpVr0GB1ilb8Hmnyw6YS++bHDBICJIBqu0D8KabnJAMaXfoyN9H0SFp wbWKou3oux5Jx40JWUzrNk7J49JENe2MmN4p97LWWKv7jl2FB4tA0j8cIzOqh0nhfw0t Q+tBDc3UVVDn4EaSyI8uFYroevkkudEcefZiB2bHr4vdl1CzP9Dt8HY3bEmv5eVNk3T0 y30g==
MIME-Version: 1.0
X-Received: by 10.236.154.134 with SMTP id h6mr11471674yhk.70.1412368883806; Fri, 03 Oct 2014 13:41:23 -0700 (PDT)
Received: by 10.170.219.194 with HTTP; Fri, 3 Oct 2014 13:41:23 -0700 (PDT)
Received: by 10.170.219.194 with HTTP; Fri, 3 Oct 2014 13:41:23 -0700 (PDT)
In-Reply-To: <542E53D2.5040500@alvestrand.no>
References: <542E53D2.5040500@alvestrand.no>
Date: Sat, 04 Oct 2014 06:41:23 +1000
Message-ID: <CAHp8n2kV_LmKkBtzxdC1GZcBow1yq6=sZd2H5n2Zen7j5qVvFQ@mail.gmail.com>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary="20cf303bfada9c779c05048ac1aa"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/lIPpMlFjUv5IsWVnTdLCtzgednE
Cc: rtcweb@ietf.org
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: Fri, 03 Oct 2014 20:41:26 -0000
These are good! On 3 Oct 2014 17:44, "Harald Alvestrand" <harald@alvestrand.no> wrote: > > After all the feedback, I've taken another whack at this. > > It seems that the term "WebRTC endpoint" is already used widely enough that it's worth continuing to use it. So I ended up with the following suggested text for -overview's definitions. > > Comments? > If this seems OK, I'll emit another -overview next week with these definitions. > > -------------------------- > > o A WebRTC User Agent (also called an UA or browser) is something that conforms to both the protocol specification and the Javascript API defined above. > > o A WebRTC device is something that conforms to the protocol > specification, but does not claim to implement the Javascript API. > > o A WebRTC endpoint is either a WebRTC UA or a WebRTC device. Since a webrtc UA is a superset of a webrtc device, webrtc endpoint and webrtc device end up meaning the same, don't they? > o A WebRTC-compatible endpoint is an endpoint that is capable of successfully communicating with a WebRTC endpoint, but may fail to meet some requirement of the WebRTC endpoint. This may limit where in the network such an endpoint can be attached, or may limit the security guarantees that it offers to others. > > o A WebRTC gateway is a WebRTC-compatible endpoint that mediates media traffic to non-WebRTC entities. > > ----------------------------- > > FOR TRANSPORT: > > A WebRTC-compatible endpoint is capable of inititating or accepting a session with a WebRTC endpoint. The following requirements on a WebRTC endpoint are not required for such success: > > - Support for full ICE. If the endpoint is only ever going to be attached to the public Internet, it does not need to be able to fix its own external address; ICE-Lite is enough. > - Support for the full suite of MTI codecs for a WebRTC endpoint. In particular, audio gateways that connect to native G.711 networks may choose to implement G.711 and not implement Opus. > - Offering BUNDLE or RTCP-MUX > - Using MSID in its offers or answers > <should congestion cutoff requirement be in or out?> > <there will be more> > > Note that support for DTLS, ICE and TURN ARE required for a WebRTC-compatible endpoint, and if RTP is used at all, DTLS-SRTP MUST be used. > > Is your intent to specify which parts of the protocol are not required to be supported by webrtc-compatible endpoints in a rfc? I think it would be useful... Silvia. _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] Definitions of WebRTC entities Christer Holmberg
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Christer Holmberg
- Re: [rtcweb] Definitions of WebRTC entities Christer Holmberg
- Re: [rtcweb] Definitions of WebRTC entities Silvia Pfeiffer
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Parthasarathi R
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Christer Holmberg
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Christer Holmberg
- Re: [rtcweb] Definitions of WebRTC entities Parthasarathi R
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Parthasarathi R
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Rauschenbach, Uwe (NSN - DE/Munich)
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Schwarz, Albrecht (Albrecht)
- Re: [rtcweb] Definitions of WebRTC entities Rauschenbach, Uwe (NSN - DE/Munich)
- Re: [rtcweb] Definitions of WebRTC entities Harald Alvestrand
- Re: [rtcweb] Definitions of WebRTC entities Colin Perkins