Re: [rtcweb] SDP and ssrc-group,

Peter Thatcher <pthatcher@google.com> Tue, 21 October 2014 17:31 UTC

Return-Path: <pthatcher@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 DED4B1A1B4A for <rtcweb@ietfa.amsl.com>; Tue, 21 Oct 2014 10:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.488
X-Spam-Level:
X-Spam-Status: No, score=-0.488 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, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wJFyOxk-JNfI for <rtcweb@ietfa.amsl.com>; Tue, 21 Oct 2014 10:31:44 -0700 (PDT)
Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD5B91A1AF0 for <rtcweb@ietf.org>; Tue, 21 Oct 2014 10:31:43 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id hy4so824819vcb.0 for <rtcweb@ietf.org>; Tue, 21 Oct 2014 10:31:42 -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=IzFt55UXPWrygA2iItbXqCG+vt3+5MMl70cM0gaZDcY=; b=XL6HXHIyKCOWN0H41gv+Y2vlMYZMSmPR35w08/znOePGd74TieNM/w05F3KH4h8NDh rT9lBThd68jroEACP5AXymMYjSGrtOAa0zw6/2jh632Jk64EXD9npj5tRVBIeXmUgk20 Zq4bWJVZm7VLd3pMsJk2piLoN2XByiL/MuFKT7B39WgSixJKQm7bWIPf0JTWQMh+1fnl ljlhjWz5VqfgM7g/i3C+eFCBP+yxjfW9YWjnh1N25krVqie/HxO9A/i/6J8c4XyszXIU v8NP86Q62JSGK+AJyZyQoZop+zGPsXQE/DXviY/3ksUKGX/WDiYA7GE/hodaWE5dBlrS cnYg==
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=IzFt55UXPWrygA2iItbXqCG+vt3+5MMl70cM0gaZDcY=; b=SSwj9opiScB71g0lJocXcE70GMTNHQf/vUsRT21Z13I9wCDDB2+t5yk7H3wjckDNFf mNzkMUeDv1QUGmksar5czwxEBWlTL8SS5Nwe2Z4+q1omUeGypb0Mi9gU1cEAfKLW9rpK Zua20qucWluiZzjs4qNWZGqmSyJXs5sOziy/giAxvrv3c8ydIs43rcl4OmrLgQOjO9xc OMO970IgfjRXCZNgq6A7EAU5b0Vip1E1q9mVbPi+Qh3sdoZd8SY1IU/2OdPVnxgAY5+G Ar5trUq0c0F8yvj3aJroRfch4nSD0Q4j0y8gCgJ9ZPgL3HW6FMToknWWZHCjYKqwAwB+ +dXQ==
X-Gm-Message-State: ALoCoQl+Hj7OAng/2470BuLVIcmpoZxBhCbslA0PtBTMbs6JyGPsxyDG/FK+SfBwp7EUFN115pqr
X-Received: by 10.220.195.196 with SMTP id ed4mr3011629vcb.65.1413912702033; Tue, 21 Oct 2014 10:31:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.173.136 with HTTP; Tue, 21 Oct 2014 10:31:01 -0700 (PDT)
In-Reply-To: <CALiegfmH8rRyEDbJjQ=kzMv0nGC=S9gNsE7roE=kqJyVcfgy8g@mail.gmail.com>
References: <CALiegfmH8rRyEDbJjQ=kzMv0nGC=S9gNsE7roE=kqJyVcfgy8g@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Tue, 21 Oct 2014 10:31:01 -0700
Message-ID: <CAJrXDUHekuQCLeCYzsnm8AuTUgiVppQHUqR7MKdQ9Q=eFFAy0w@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: multipart/alternative; boundary="001a11c1c3245946dd0505f234d1"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/ZTmRG8dOCr4pgDlwX2WlS5j6qcA
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SDP and ssrc-group,
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: Tue, 21 Oct 2014 17:31:46 -0000

345259865 is "real"
2693756249 is rtx

On Tue, Oct 21, 2014 at 9:25 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> Hi,
>
> May I know which SSRC (345259865 or 2693756249) will be used for the
> real media stream (plus RED and FEC) and which SSRC will be used for
> RTX?
>
>
>
> --------------------------
> m=video 62164 RTP/SAVPF 100 116 117 96
> a=mid:video
> a=rtpmap:100 VP8/90000
> a=rtpmap:116 red/90000
> a=rtpmap:117 ulpfec/90000
> a=rtpmap:96 rtx/90000
> a=fmtp:96 apt=100
> a=ssrc-group:FID 345259865 2693756249
> a=ssrc:345259865 cname:erS7E/KHLYKTejNs
> a=ssrc:345259865 msid:DWpWct9bWKzTMNYZn5bKVgwZ8Mfy2EtfqBY5
> c0134f05-e7c2-4afd-a979-4e224de5eb91
> a=ssrc:345259865 mslabel:DWpWct9bWKzTMNYZn5bKVgwZ8Mfy2EtfqBY5
> a=ssrc:345259865 label:c0134f05-e7c2-4afd-a979-4e224de5eb91
> a=ssrc:2693756249 cname:erS7E/KHLYKTejNs
> a=ssrc:2693756249 msid:DWpWct9bWKzTMNYZn5bKVgwZ8Mfy2EtfqBY5
> c0134f05-e7c2-4afd-a979-4e224de5eb91
> a=ssrc:2693756249 mslabel:DWpWct9bWKzTMNYZn5bKVgwZ8Mfy2EtfqBY5
> a=ssrc:2693756249 label:c0134f05-e7c2-4afd-a979-4e224de5eb91
> -------------------------------
>
>
>
>
> RFC 5576 does not clarify it at all:
>
> http://tools.ietf.org/html/rfc5576#section-4.2
>
> --------------------------------------------------
> 4.2.  The "ssrc-group" Media Attribute
>
>    a=ssrc-group:<semantics> <ssrc-id> ...
>
>    [..]
>
>    The <semantics> parameter is taken from the specification of the
>    "group" attribute [RFC3388].  The initial semantic values defined for
>    the "ssrc-group" attribute are FID (Flow Identification) [RFC3388]
>    and FEC (Forward Error Correction) [RFC4756].  In each case, the
>    relationship among the grouped sources is the same as the
>    relationship among corresponding sources in media streams grouped
>    using the SDP "group" attribute.
> --------------------------------------------------
>
>
>
> The referenced RFC 3388 neither clarifies it:
>
> ---------------------------------------------------
> 7.4 FID Semantics
>
>    Several "m" lines grouped together using FID semantics form a media
>    flow.  A media agent handling a media flow that comprises several "m"
>    lines MUST send a copy of the media to every "m" line part of the
>    flow as long as the codecs and the direction attribute present in a
>    particular "m" line allow it.
>
>    It is assumed that the application uses only one codec at a time to
>    encode the media produced.  This codec MAY change dynamically during
>    the session, but at any particular moment only one codec is in use.
>
>    The application encodes the media using the current codec and checks
>    one by one all the "m" lines that are part of the flow.  If a
>    particular "m" line contains the codec being used and the direction
>    attribute is "sendonly" or "sendrecv", a copy of the encoded media is
>    sent to the address/port specified in that particular media stream.
>    If either the "m" line does not contain the codec being used or the
>    direction attribute is neither "sendonly" nor "sendrecv", nothing is
>    sent over this media stream.
> ----------------------------------------------------
>
>
>
>
> So, how is the usage of ssrc-group? Where is it really defined?
>
> Can I put more than 2 ssrc together in the same ssrc-group line?
>
> How should the receiver interpret it?
>
> Does a ssrc-group always mean RTX usage? Where is that specified in
> the above SDP?
>
> Does not the above SDP look a complete mixture of hacks and workarounds?
>
>
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>