IETF Logo Mail Archive

[rtcweb] About the current JSEP-06 draft

Justin Uberti <juberti@google.com> Mon, 14 July 2014 02:21 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 E58491A026A for <rtcweb@ietfa.amsl.com>; Sun, 13 Jul 2014 19:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 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.651, 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 Xxn4NW01iKSk for <rtcweb@ietfa.amsl.com>; Sun, 13 Jul 2014 19:21:28 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40BD11A0267 for <rtcweb@ietf.org>; Sun, 13 Jul 2014 19:21:28 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hu12so917854vcb.20 for <rtcweb@ietf.org>; Sun, 13 Jul 2014 19:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=Bmp5WjrA6JcKWWYGRfgI4sah17aofAmMAYDGgg+BPbM=; b=Lz/uR0qKnTuPx6UwgWL16ffvc6k0ZvHEOnwJkrXGv7MioKl6PP0onJMdcz5xv95Mo2 BdP9z4BvQCzJ4ByFXAO5SwS3QJqqKET7JXCiP4MQvjoXv/P5Cj7WNYjPEokcvxx+EpkH 5iZxsKDwoQ9wgTmjf7i11zJxbjO992tPKQwCKWj6G2gzzZhx37BMZOUHZhbvDPqt2jJ0 NmtZOqP4iG0sZjnvzXwmIh0jueY1Nz/jwLuyElqryDbT42QZnIeUTGEhPFyH7tqvIZEB ewMFOWRpWJ6bR6+olXAoSNYTw10jQP5ESaMRV30u7iApCuiQ2DFLT9MpeMHF0CXzlDiL knhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=Bmp5WjrA6JcKWWYGRfgI4sah17aofAmMAYDGgg+BPbM=; b=j7HLulSGgdRhDd3pNlgxYSQZdqLCekOEZu7IVtawQBmcW5lvYqDVZw3jrc7pA8ZJ/y LdMRW/RgtOS2E870HnwRtbbYnSWJ78h61Kr3vezPa5lDVv9odTRRadHZlYyk/ZbCVBdj R5YpbyTlbFXcvetZQwtyFAYa2lsttD2dPvbfZ+X7OtyDrc4iXCeBfERfTtqpsjJFditu zi+OfWrMs63VM7TED+4bV84lKhAKNfqpqCz9veyGfwJiJtxwTw+L55GQK5NfrBeKAn+q 0vhwr17YKVGHjJ90jo+gXIckw36uCyCWQCB3qfJtoKgxX22czq9tFfMUop8aP22H2X2q Ecug==
X-Gm-Message-State: ALoCoQkFVh2KwzNr2fkoswdPkbN65dftZan8yx+ADxrSBmLFl+fSOvqF62jsGfVlgC4dxN9yH4bG
X-Received: by 10.220.92.135 with SMTP id r7mr13426436vcm.11.1405304486976; Sun, 13 Jul 2014 19:21:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.27.8 with HTTP; Sun, 13 Jul 2014 19:21:06 -0700 (PDT)
From: Justin Uberti <juberti@google.com>
Date: Sun, 13 Jul 2014 19:21:06 -0700
Message-ID: <CAOJ7v-0sYm-rT+TGJQottv9tCAZiRMzYE6Y-Dc6f5q=hhoYktw@mail.gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, martin.ekblom@icewarp.com
Content-Type: multipart/alternative; boundary="047d7b66f5fbbf7d6504fe1df203"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/wnNW1Wx-wlhqfCzFL3tQtuMzHGQ
Subject: [rtcweb] About the current JSEP-06 draft
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: Mon, 14 Jul 2014 02:21:30 -0000

Adding rtcweb@ietf.org, the right mailing list for this.

This behavior (of OfferToReceiveAudio/Video) was added to be conformant
with Unified Plan, where each media stream requires its own m= line, and
therefore the offerer needs the ability to advertise additional m= lines if
it needs to receive more media streams than it is offering.

I agree that the w3c spec's handling of this topic could be clarified.

On Wed, Jul 2, 2014 at 2:37 AM, Martin Ekblom <martin.ekblom@icewarp.com>
wrote:

> Hi,
>
> I believe there is a conceptual misunderstanding in section 5.2.3.1. and
> 5.2.3.2. It seems to contradict the requirements of RFC 3264 / 4566 (SDP
> offers and answers) and not be in line with the WebRTC draft. I would like
> to contribute to improve  or clarify this section, or in case I'm mistaken
> confirm this.
>
> Is this the appropriate mailing list to disuss this?
>
> Regards,
> Martin Ekblom
> Front-end Developer
> www.icewarp.com
>
>
>

v2.23.0 | Report a Bug | By Email