Return-Path: <suhasietf@gmail.com>
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 DF5D621F8640 for <rtcweb@ietfa.amsl.com>;
 Thu, 19 Sep 2013 13:55:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.866
X-Spam-Level: 
X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=-0.533,
 BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, NO_RELAYS=-0.001,
 SARE_HTML_USL_OBFU=1.666]
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 8k33khiXfXJS for
 <rtcweb@ietfa.amsl.com>; Thu, 19 Sep 2013 13:55:39 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com
 [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id
 B0A1921F8887 for <rtcweb@ietf.org>; Thu, 19 Sep 2013 13:55:30 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w62so8590705wes.15 for
 <rtcweb@ietf.org>; Thu, 19 Sep 2013 13:55:29 -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=YQ1BpIhKQtOA2pyof2eCs6w9Fdt0jGRCaztDKuSh4fw=;
 b=SFzHVyR5qlRLRsjmWqTR+q6WLO1YPuvPE/KTQfVjP79PVEwe5zcQG+Pk08uunCaCJW
 M3NQJmgdPVRlBR2VbP6YYoiTSCoyYFDv7x3Qvfr/49mZVX9YzP4996GBGQd5bToKg5J1
 5GIMh9DtfZhxH1AjosKULY1uC19sZ31/LkAla0TDKXf/+6Ysx/qDiEgkYqgbfYS9PU5p
 ml98uL+RYJmiqYGHCIxWadvD7T0tqdZUp2YbjYnaLBBqQDeF1h5iESQm7o6ZMh34SNZw
 jEegiuwJCJ0dlG8vqwJYvhQxC1j7gIj398ZOmB7dlHJPZ1A0vZk7Y9x1+b84by/HJq/V 5bgg==
MIME-Version: 1.0
X-Received: by 10.180.107.167 with SMTP id hd7mr2882218wib.13.1379624129743;
 Thu, 19 Sep 2013 13:55:29 -0700 (PDT)
Received: by 10.194.178.231 with HTTP; Thu, 19 Sep 2013 13:55:29 -0700 (PDT)
In-Reply-To: <523AF421.7000807@alvestrand.no>
References: <523AF421.7000807@alvestrand.no>
Date: Thu, 19 Sep 2013 13:55:29 -0700
Message-ID: <CAMRcRGQXeH7D+u2g-jdoWfHJ+FmE+mgpAztmsyArZNS0KAz=Fw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=e89a8f2353a72d50c904e6c2c64e
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP-04: Nits and niggles
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: Thu, 19 Sep 2013 20:55:42 -0000

--e89a8f2353a72d50c904e6c2c64e
Content-Type: text/plain; charset=ISO-8859-1

Regarding a=ssrc comment above,
The text from RFC5576 says this

Each "ssrc" media attribute specifies a single source-level attribute
   for the given <ssrc-id>.  For each source mentioned in SDP, the
   source-level attribute "cname", defined in Section 6.1
<http://tools.ietf.org/html/rfc5576#section-6.1>, MUST be
   provided.  Any number of other source-level attributes for the source
   MAY also be provided.



given the above, would it be cname attribute for a given ssrc that
should be mandated at the minimum ?



Cheers

Suhas





On Thu, Sep 19, 2013 at 5:54 AM, Harald Alvestrand <harald@alvestrand.no>wrote:

> I'm sure we'll have lots of things to discuss about JSEP. I just thought
> I'd get these out of the way.
>
> - Usage of MSID. In addition to the a=msid: lines, the session-level
> generation procedure needs to say that a line "a=msid-semantic:WMS <id>" is
> added to the session-level description, containing the IDs of the
> MediaStreams that are signalled.
>
> - a=ssrc lines. The spec (5.2.1 second list last bullet) simply says "an
> a=ssrc line". But RFC 5576 specifies that all ssrc lines contain an
> attribute. Suggestion: define one that does no harm (role=primary?)
>
> - recycling of m= lines. The section in 5.2.2 (subsequent offers) that
> talks about this doesn't mention that the media in the m-line has to match,
> although section 5.3.1 (initial answer) actually talks about it. I'm
> assuming that's an oversight.
>
> I'd suggest pulling the language about "selecting an appropriate m-line
> for a track" out in a separate subsection, so that we have one place to
> point to for this.
>
> Out of time, let's get these ones out of the way for -05....
>
>
>
> ______________________________**_________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>

--e89a8f2353a72d50c904e6c2c64e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Regarding a=3Dssrc comment above,</div>The text from =
RFC5576 says this=A0<div><br></div><div><pre class=3D"" style=3D"font-size:=
1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Each &quot;ssrc&quot=
; media attribute specifies a single source-level attribute
   for the given &lt;ssrc-id&gt;.  For each source mentioned in SDP, the
   source-level attribute &quot;cname&quot;, defined in <a href=3D"http://t=
ools.ietf.org/html/rfc5576#section-6.1">Section 6.1</a>, MUST be
   provided.  Any number of other source-level attributes for the source
   MAY also be provided.</pre><pre class=3D"" style=3D"font-size:1em;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"" styl=
e=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><br><=
/pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal">given the above, would it be cname =
attribute for a given ssrc that should be mandated at the minimum ?</span><=
/font></pre>
<pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"ar=
ial"><span style=3D"white-space:normal"><br></span></font></pre><pre class=
=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font face=3D"arial"><span=
 style=3D"white-space:normal"><br>
</span></font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0=
px"><font face=3D"arial"><span style=3D"white-space:normal">Cheers</span></=
font></pre><pre class=3D"" style=3D"margin-top:0px;margin-bottom:0px"><font=
 face=3D"arial"><span style=3D"white-space:normal">Suhas</span></font></pre=
>
<pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margin-top:=
0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre></div></div><div class=3D=
"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Sep 19, 2013 at 5:54 AM, Harald =
Alvestrand <span dir=3D"ltr">&lt;<a href=3D"mailto:harald@alvestrand.no" ta=
rget=3D"_blank">harald@alvestrand.no</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
I&#39;m sure we&#39;ll have lots of things to discuss about JSEP. I just th=
ought I&#39;d get these out of the way.<br>
<br>
- Usage of MSID. In addition to the a=3Dmsid: lines, the session-level gene=
ration procedure needs to say that a line &quot;a=3Dmsid-semantic:WMS &lt;i=
d&gt;&quot; is added to the session-level description, containing the IDs o=
f the MediaStreams that are signalled.<br>

<br>
- a=3Dssrc lines. The spec (5.2.1 second list last bullet) simply says &quo=
t;an a=3Dssrc line&quot;. But RFC 5576 specifies that all ssrc lines contai=
n an attribute. Suggestion: define one that does no harm (role=3Dprimary?)<=
br>

<br>
- recycling of m=3D lines. The section in 5.2.2 (subsequent offers) that ta=
lks about this doesn&#39;t mention that the media in the m-line has to matc=
h, although section 5.3.1 (initial answer) actually talks about it. I&#39;m=
 assuming that&#39;s an oversight.<br>

<br>
I&#39;d suggest pulling the language about &quot;selecting an appropriate m=
-line for a track&quot; out in a separate subsection, so that we have one p=
lace to point to for this.<br>
<br>
Out of time, let&#39;s get these ones out of the way for -05....<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
rtcweb mailing list<br>
<a href=3D"mailto:rtcweb@ietf.org" target=3D"_blank">rtcweb@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtcweb" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/rtcweb</a><br>
</blockquote></div><br></div>

--e89a8f2353a72d50c904e6c2c64e--