[rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
"Karl Stahl" <karl.stahl@intertex.se> Sat, 21 September 2013 21:44 UTC
Return-Path: <karl.stahl@intertex.se>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDF511E819B for <rtcweb@ietfa.amsl.com>; Sat, 21 Sep 2013 14:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.502
X-Spam-Level:
X-Spam-Status: No, score=-1.502 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_50=0.001, GB_I_INVITATION=-2, MSGID_MULTIPLE_AT=1.449, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sK8o7yj890L for <rtcweb@ietfa.amsl.com>; Sat, 21 Sep 2013 14:44:40 -0700 (PDT)
Received: from smtp.it-norr.com (smtp.it-norr.com [80.244.64.161]) by ietfa.amsl.com (Postfix) with ESMTP id 21B1211E81A0 for <rtcweb@ietf.org>; Sat, 21 Sep 2013 14:44:29 -0700 (PDT)
Received: from ([90.229.134.75]) by smtp.it-norr.com (Telecom3 SMTP service) with ASMTP id 201309212344265890; Sat, 21 Sep 2013 23:44:26 +0200
From: Karl Stahl <karl.stahl@intertex.se>
To: rtcweb@ietf.org, draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org
References: <C5E08FE080ACFD4DAE31E4BDBF944EB11667BBA0@xmb-aln-x02.cisco.com> <5238446D.8050700@ericsson.com> <9F33F40F6F2CD847824537F3C4E37DDF17BCF581@MCHP04MSX.global-ad.net> <07a601ceb64e$5caaba00$16002e00$@stahl@intertex.se> <07b001ceb65f$ce3f0cf0$6abd26d0$@stahl@intertex.se>
In-Reply-To: <07b001ceb65f$ce3f0cf0$6abd26d0$@stahl@intertex.se>
Date: Sat, 21 Sep 2013 23:44:27 +0200
Message-ID: <07e401ceb713$bef87a60$3ce96f20$@stahl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHOs51tjte/V8mikk+NN5idi26Ro5nO5Y8ggABAlmCAACsPkIABLYKw
Content-Language: sv
Subject: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 21 Sep 2013 21:44:45 -0000
Yet another thing related to draft-ietf-rtcweb-use-cases-and-requirements-11: It is about payload type, PT=, in SDP and RTP, so I am copying MMUSIC Network service providers have expressed an interest to know whether packets carry audio or video, to be able to handle them differently in the network (e.g. quality wise). PT is visible outside the encrypted payload in RTP, however if dynamic payload types PT:96-127 are used, you cannot know what the payload is without knowledge of the SDP (which we for WebRTC must assume the network provider has no knowledge of). In http://www.ietf.org/assignments/rtp-parameters/rtp-parameters.xml I see no PTs defined for Opus, VP8, H.264 etc. considered for WebRTC. So, can we have payload types assigned to codecs that will be recommended for WebRTC (PT:35-71 are unassigned)? Or can we at least split dynamic payload types PT:96-127 into groups for audio and video codecs? I relation to that simple request, one may wonder how the network anyway can know what is carried in an UPD packet (the RTP header is no reserved field - it could be the payload of something else). Quality related requirements F38, A23 and A26 in the use case draft, nowadays only seem to relate to the browsers, not assuming that diffserve bits or similar are conveyed to the network. That is realistic, since most operating systems don't allow quality markings (diffserve, TOS) of packets. However, 3.2.1. Simple Video Communication Service, mentions "The web service monitors the quality of the service (focus on quality of audio and video) the end-users experience.". I don't understand how "The *web service* monitors" based on the listed requirements. Should it be "The *browsers* monitors"? What are then the possibilities for a network to classify traffic for quality or other purposes? 3G/4G networks have DPIs (Deep Packet Inspection) - such box may guess what encrypted RTP traffic is... or may not... Real time communication protocols using ICE as a pre-protocol to establish media paths give a possibility though. If the network provider offers a TURN server at his access, and enforces the TURN server to be used (by eating STUN packets), then the RTP flows set up through the TURN server could classify and mark packets. Then it is useful to know whether it is an audio or video packet by looking at the payload type. A LAN firewall, can also include a TURN-server, that in addition to classifying and marking packets for the transport network (if honored - which rarely is the case on the Internet today), it can also prioritize and traffic shape so the RTP traffic at least is undisturbed through a data crowded Internet access. A more difficult request comes from networks using bandwidth reservation (RSVP) for quality, like mobile and cable networks. Such networks would benefit from knowing the bandwidth used, but that is not fixes for advanced codecs like the ones considered for WebRTC. One way would be to reserve maximum bandwidth, and possibly repeat the reservation if less is actually used. /Karl -----Ursprungligt meddelande----- Från: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] För Karl Stahl Skickat: den 21 september 2013 02:16 Till: rtcweb@ietf.org; draft-ietf-rtcweb-use-cases-and-requirements@tools.ietf.org Ämne: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11 While reading the draft-ietf-rtcweb-use-cases-and-requirements-11, here are a few "telephony related" WebRTC things I think should be clarified in the use cases. 3.2.1. Simple Video Communication Service 3.2.1.1. Description ... The invited user might accept or reject the session. [Suggest adding] The invited user might accept only audio, rejecting video (even if a camera is enabled). A user may also select to initiate an audio session, without video. And in API requirements: ---------------------------------------------------------------- A1 The Web API must provide means for the application to ask the browser for permission to use cameras and microphones, individually as input devices. (One must be able to answer with voice only - declining video.) ---------------------------------------------------------------- Same under 6.2. Browser Considerations ... The browser is expected to provide mechanisms for users to revise and even completely revoke consent to use device resources such as camera and microphone. [Suggest adding] Specifically, a user must be given the opportunity to only accept audio in a video call invitation. 3.2.12. Multiparty video communication 3.2.12.1. Description ... [Suggest adding] It is essential that automatic adjustments of microphone volume is disabled, or microphones not spoken into are muted. (This is a serious problem with most soft clients (SIP clients) of today, plaguing conferences with ever increasing noise from silent participants.) And in API requirements: ---------------------------------------------------------------- A15 The Web API must provide means for the web application to adjust the level in audio streams. ---------------------------------------------------------------- Axx The Web API must provide means to disable any automatic volume adjustment in the sent audio streams. (To avoid disturbing noise in conferences - making many softclients unusable). ---------------------------------------------------------------- 3.2.6. Simple Video Communication Service, access change 3.2.6.1. Description ... the user has to start a trip during the session. The communication device automatically changes to use WiFi when the Ethernet cable is removed and then moves to cellular access to the Internet when moving out of WiFi coverage. The session continues even though the access method changes. [Question] Is this some sort of roaming without network support (please clarify)? Getting a new access will also give the client a new IP address, won't it? How could then the session continue? The browsers will have no signaling connection and cannot renegotiate a media connection, can they? _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-… Cullen Jennings (fluffy)
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Stefan Håkansson LK
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Magnus Westerlund
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Bernard Aboba
- [rtcweb] TURN server address via DHCP, WGLC of dr… Karl Stahl
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Hutton, Andrew
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Harald Alvestrand
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Bernard Aboba
- [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Marc Abrams
- [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-use-c… Karl Stahl
- [rtcweb] [mmusic] TURN server address via DHCP, W… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Hutton, Andrew
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Marc Abrams
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Hutton, Andrew
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Hutton, Andrew
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Sergio Garcia Murillo
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Tirumaleswar Reddy (tireddy)
- Re: [rtcweb] TURN server address via DHCP, WGLC o… cb.list6
- Re: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-u… Dan Wing
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Karl Stahl
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Chenxin (Xin)
- Re: [rtcweb] additional ICE info Bernard Aboba
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Karl Stahl
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Chenxin (Xin)
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Karl Stahl
- Re: [rtcweb] additional ICE info Dan Wing
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Cullen Jennings (fluffy)
- Re: [rtcweb] additional ICE info Harald Alvestrand
- Re: [rtcweb] additional ICE info Dan Wing
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Harald Alvestrand
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Markus.Isomaki
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Chenxin (Xin)
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Karl Stahl
- Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… cb.list6
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Cullen Jennings (fluffy)
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Justin Uberti
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Karl Stahl
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Jeremy Laurenson (jlaurens)
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Justin Uberti
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Martin Thomson
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Bernard Aboba
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Jeremy Laurenson (jlaurens)
- [rtcweb] [mmusic] TURN server address via DHCP, W… Karl Stahl
- Re: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-u… Magnus Westerlund
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Saverio Vardaro
- Re: [rtcweb] additional ICE info Martin Thomson
- Re: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-u… Karl Stahl
- Re: [rtcweb] [mmusic] TURN server address via DHC… Cullen Jennings (fluffy)
- Re: [rtcweb] [mmusic] TURN server address via DHC… Karl Stahl
- Re: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-u… Christer Holmberg
- Re: [rtcweb] [mmusic] TURN server address via DHC… Justin Uberti
- Re: [rtcweb] [mmusic] TURN server address via DHC… cb.list6
- [rtcweb] Payload Types assignments was Re: SV: [m… Magnus Westerlund
- Re: [rtcweb] TURN server address via DHCP, WGLC o… Karl Stahl
- Re: [rtcweb] [mmusic] TURN server address via DHC… Karl Stahl
- Re: [rtcweb] [mmusic] WGLC of draft-ietf-rtcweb-u… Karl Stahl
- Re: [rtcweb] [mmusic] TURN server address via DHC… Justin Uberti
- Re: [rtcweb] Payload Types assignments was Re: SV… Karl Stahl
- Re: [rtcweb] Payload Types assignments was Re: SV… Harald Alvestrand
- Re: [rtcweb] Payload Types assignments was Re: SV… BeckW
- Re: [rtcweb] Payload Types assignments was Re: SV… Ted Hardie
- Re: [rtcweb] Payload Types assignments was Re: SV… BeckW
- Re: [rtcweb] Payload Types assignments was Re: SV… Harald Alvestrand
- Re: [rtcweb] Payload Types assignments was Re: SV… Martin Thomson
- Re: [rtcweb] Payload Types assignments was Re: SV… Harald Alvestrand
- Re: [rtcweb] Payload Types assignments was Re: SV… BeckW
- Re: [rtcweb] Payload Types assignments was Re: SV… Martin Thomson
- Re: [rtcweb] Payload Types assignments was Re: SV… Ted Hardie
- Re: [rtcweb] Payload Types assignments was Re: SV… Lee, Richard FTC
- Re: [rtcweb] Payload Types assignments was Re: SV… Dan Wing
- Re: [rtcweb] Payload Types assignments was Re: SV… BeckW
- Re: [rtcweb] Payload Types assignments was Re: SV… Karl Stahl
- [rtcweb] [mmusic] Anycast discovery, Was TURN ser… Karl Stahl
- [rtcweb] [avtext] Payload Types assignments was R… Karl Stahl
- [rtcweb] [tram] Payload Types assignments Karl Stahl
- Re: [rtcweb] [tram] Payload Types assignments Colin Perkins
- Re: [rtcweb] [tram] Payload Types assignments Karl Stahl
- Re: [rtcweb] [tram] Payload Types assignments Magnus Westerlund
- Re: [rtcweb] [tram] Payload Types assignments Charles Eckel (eckelcu)
- Re: [rtcweb] [tram] Payload Types assignments Colin Perkins
- Re: [rtcweb] [tram] Payload Types assignments Harald Alvestrand
- Re: [rtcweb] [tram] Payload Types assignments Karl Stahl
- Re: [rtcweb] [tram] Payload Types assignments Karl Stahl
- Re: [rtcweb] [tram] Payload Types assignments Karl Stahl
- Re: [rtcweb] [tram] Payload Types assignments Harald Alvestrand
- Re: [rtcweb] [tram] Payload Types assignments Karl Stahl