Re: [rtcweb] Should we reference the pause/resume I-D?
Justin Uberti <juberti@google.com> Wed, 12 March 2014 20:56 UTC
Return-Path: <juberti@google.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 7A1681A0778 for <rtcweb@ietfa.amsl.com>; Wed, 12 Mar 2014 13:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 NKNs9HnnQKzz for <rtcweb@ietfa.amsl.com>; Wed, 12 Mar 2014 13:56:35 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 431EC1A07A5 for <rtcweb@ietf.org>; Wed, 12 Mar 2014 13:56:35 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id oz11so86610veb.20 for <rtcweb@ietf.org>; Wed, 12 Mar 2014 13:56:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BOR7Xc29Fo6JI3Yp4HdxLAMkArNSrzoaTVpCyK4aPoE=; b=ZduWq77590IIcWlG2tSxhKEiof2+ERtc2fm9Lb4JDpfdrhtMg6c1b3VqrjzIU6iU36 GVWUBcoqCHybYMCEpT4CeIpzUDERMGGjRis9/FASFeHqz3nd3HfogHqiI5ocu147lWbD 0BKmKmdazwgJHyv1mn7L931xnqwpdd2CAMGzWnGXWttNt7wJ0/pscWvg98x5UGLHNPc5 clOq8SEw/DiBobvbRt5H4YblS3X93nKohnXStH0xIB7xxDDPe7WRCZphoG1A1ogvpYrs 9pWeGPiEZIzOUk/AHoeMg59PItMwnbvE15libFtVMxDRAcfXtSopZ3t2pirpX2JXjFRz EZCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=BOR7Xc29Fo6JI3Yp4HdxLAMkArNSrzoaTVpCyK4aPoE=; b=ZKV2x3ksUJHyeV46W5LfXmmmA4v5K6Z+GqdU1I72briQqkGcDYUpg/zqqf5+e9H6KZ dWahxb6+e5rr+I3wLCChnvcmQp+4CW7JLGVRejzi89jRhpTOSGxfQrB+hixSLVXNI28s a5cCNt291oCVr1NFK5ra7dzAsl/ZfZxxy2X7BOEcG1+OjJD9WadL/GsDO+SoinAn6cpi tr/F+30Mbza862neZVeRgeTpqbSHOWWhvegicY3RnVUI3wg99bimJStov2DYLnFy6gfo cZ2ROuzpRN5/bGq6jAAVKu4TCvwS2xYGI4TWgGPrtIBMu/mDq8H5HvsQG8Mr8Ow0tPl6 csQw==
X-Gm-Message-State: ALoCoQmWMDKvQhI+9s+hqRABfEYNw0+OLqMLu4pXspDWGdK+xCLbw4cRbsWnx5U4izzFwy1DFLGnwxsKXq7d8+d2OGOPcKDAD+7hyw892BYQkqB1Bvoaa5UwB3+8b/DF1Jf0MQxY6SzZb0d3+WX9VNfb/EFgaPOLanw3yflwwQpL69DdnYWzVfRCyqiXcgoIQus9eOU9kuCR
X-Received: by 10.220.92.135 with SMTP id r7mr33521201vcm.11.1394657788763; Wed, 12 Mar 2014 13:56:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 12 Mar 2014 13:56:08 -0700 (PDT)
In-Reply-To: <CAOW+2dsb1GqQmOxf7V6C1Xd_LG12d+kanSm80=kSwmQY=B7GSg@mail.gmail.com>
References: <1447FA0C20ED5147A1AA0EF02890A64B1CF8B463@ESESSMB209.ericsson.se> <CAOW+2dsb1GqQmOxf7V6C1Xd_LG12d+kanSm80=kSwmQY=B7GSg@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 12 Mar 2014 13:56:08 -0700
Message-ID: <CAOJ7v-3S1axGPVWB8TF_ALwZ6ExF-D7m3MGsfrkx6EsQNWNpxQ@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b66f5fb153fd804f46f121f"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/_43IFRknJVW6rN-Pz9WROJnR3-A
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Should we reference the pause/resume I-D?
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, 12 Mar 2014 20:56:38 -0000
Agreed. Aren't there also patent declarations against this doc from multiple holders? While SDP will likely be removed from the API in the future, the replacement would be a app-specific message sent over websockets, which seems like it would work just fine. On Wed, Mar 12, 2014 at 12:50 PM, Bernard Aboba <bernard.aboba@gmail.com>wrote: > While I do like the pause/resume draft, having core RTCWEB WG documents > (such as RTP Usage) depend on it seems like a bit of a stretch. After all, > the document was only adopted last week, and it is a rare IETF WG document > that can go from a -00 WG draft to publication as an RFC in under a year. > > > On Wed, Mar 12, 2014 at 11:01 AM, Stefan Håkansson LK < > stefan.lk.hakansson@ericsson.com> wrote: > >> Hi, >> >> at the IETF last week there was consensus in the AVTEXT WG meeting to >> adopt the pause/resume draft [1] as a WG draft. >> >> In rtcweb/webrtc we're have the situation that we're discussing so >> called "doo-hickeys" as an API surface where the web app (amongst other >> things) can pause and resume the sending of a track. This can >> be signaled with the direction attribute and a SDP O/A exchange (and the >> app pausing/resuming sending of a track would presumably lead to a >> "negotiationneeded" event being fired). >> >> But I think we should in addition require the browser to signal it >> according to one of the methods in [1] (e.g. TMMBN = 0), and also >> understand that signaling (a browser receiving TMMBN = 0 must know that >> the other end-point will pause sending). >> >> My argument is that we know that many dislike SDP in rtcweb, and a >> likely development is that it will be removed in a later version. My >> speculation is that signaling as outlined in [1] will then be used for >> pause/resume. If we support this from the beginning earlier >> implementations could more easily interop with those later versions. >> >> >> Stefan >> >> [1] >> https://tools.ietf.org/id/draft-westerlund-avtext-rtp-stream-pause-05.txt >> >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb >> > > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > >
- Re: [rtcweb] Should we reference the pause/resume… Randell Jesup
- [rtcweb] Should we reference the pause/resume I-D? Stefan Håkansson LK
- Re: [rtcweb] Should we reference the pause/resume… Bernard Aboba
- Re: [rtcweb] Should we reference the pause/resume… Justin Uberti
- Re: [rtcweb] Should we reference the pause/resume… Stefan Håkansson LK
- Re: [rtcweb] Should we reference the pause/resume… Justin Uberti
- Re: [rtcweb] Should we reference the pause/resume… Bernard Aboba
- Re: [rtcweb] Should we reference the pause/resume… Stefan Håkansson LK
- Re: [rtcweb] Should we reference the pause/resume… Roni Even
- Re: [rtcweb] Should we reference the pause/resume… Charles Eckel (eckelcu)