
From nobody Mon Dec  1 07:07:04 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239FF1A1BE1 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 07:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] 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 AWjvm2cJZ1Kr for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 07:07:01 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D8671A0263 for <mmusic@ietf.org>; Mon,  1 Dec 2014 07:07:01 -0800 (PST)
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-03v.sys.comcast.net with comcast id NF6d1p0055AAYLo01F70yw; Mon, 01 Dec 2014 15:07:00 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-15v.sys.comcast.net with comcast id NF701p0073Ge9ey01F70xv; Mon, 01 Dec 2014 15:07:00 +0000
Message-ID: <547C8432.8040105@alum.mit.edu>
Date: Mon, 01 Dec 2014 10:07:30 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <2F938AAE444ADB47AFEE6307955A30CE2EB86B81@BGB01XUD1002.national.core.bbc.co.uk>
In-Reply-To: <2F938AAE444ADB47AFEE6307955A30CE2EB86B81@BGB01XUD1002.national.core.bbc.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417446420; bh=TFzeJBwNVpsA/5/Fj9J6Y+H3WqGWWypiFnw45kfPH8I=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=MpqaVhAW293TqRyHgMcRTht1S+FqT989+YwZlxRbM1K0GOr9h8oEtE8YEscXXKwIq cxNaVcVGZjQwChm9Ztuoq6crU5bM2VK6OAQLk0rXKxbGC3APLoTJPpFQovMWOgL+4T kfpFIlRnfG9TFJNTB9sKgkFRNQeq3SDz1L5e0K8+f7hsyOhBkwvq8kigN7rvaRjOLN Jk9D+AepO6Hbw4OAAO+krb/e2KsFDeKoBLrZwBOvJFW/TpTHWrr8FaKeEq79bmxKy9 wLAefielMbJC/8515IS3ngJ6pqMp/+lbubVHPAMeaG4QgqktdauR1pKUe7InEROQ1l u05LzTKZNAXFA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yynps2wH9yAktZ-AgCRLug0VuBY
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 15:07:03 -0000

On 11/27/14 4:12 AM, Peter Stevens wrote:
> Hi,
>
> Colin has commented on this particular attribute:
>
>  > a=ptime: and a=maxptime:
>  > - Are these always integers?
>
> This is a question within the EBU Audio Contribution over IP (ACIP)
> group have noted that the ptime units are not specified within RFC4566.
> If you were not already aware, within the AES, the AES67-2013 AES
> Standard for audio applications of networks - High-performance streaming
> audio-over-ip interoperability, packet time is defined with decimal
> values as follows:
>
> a-ptime <milliseconds>[.<milliseconds decimal>]
> a=maxptime <milliseconds>[.<milliseconds decimal>]
>
> Do ptime integers possibly conflict with decimal values?
> It is unknown how manufacturers of products define their value of ptime
> internally, such as 20ms, as either an integer of 20 (ms) or as 0.020

I am essentially just a scribe here. The point of working on the ABNF 
for these is to be precise where that wasn't previously the case. I made 
my best guess as to what was intended. If there are existing uses of 
fractional values, then we should specify that.

My concern with this attribute is backward compatibility. If the 
definition was extended to allow decimal fractions, would that be 
backward compatible with existing implementations that might not expect 
to see fractional values?

One possibility would be to allow the use of decimal fractions only when 
the fractional part is non-zero. E.g.,

       ptime-value = packet-time
       packet-time = integer | non-zero-real
       non-zero-real = (integer / "0") "." *"0" integer

(Note that in SDP ABNF "integer" never starts with a "0".)

(This definition could also be used for framerate.) It would guarantee 
that values that are an integral number of milliseconds never have a 
fractional part, which would provide some compatibility with 
implementations that expect only integers.

If there are no *existing* uses of fractional values, but a desire to 
use them, then another possibility is to define a new attribute.

	Thanks,
	Paul



From nobody Mon Dec  1 08:45:36 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15B811A6F24 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 08:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 8BEvPZ3mkCKk for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 08:45:32 -0800 (PST)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B76A1A6F62 for <mmusic@ietf.org>; Mon,  1 Dec 2014 08:45:31 -0800 (PST)
Received: from resomta-po-02v.sys.comcast.net ([96.114.154.226]) by resqmta-po-04v.sys.comcast.net with comcast id NGi41p0084tLnxL01GlWiu; Mon, 01 Dec 2014 16:45:30 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-02v.sys.comcast.net with comcast id NGlV1p00b3Ge9ey01GlWor; Mon, 01 Dec 2014 16:45:30 +0000
Message-ID: <547C9B29.9060801@alum.mit.edu>
Date: Mon, 01 Dec 2014 11:45:29 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org>
In-Reply-To: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417452330; bh=CZBe31n5f34yclMDCHOv3CVv6McfXq0I4m5Qm3olrdU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=li485lYSycc01/3iw0LtNgpsOHUUHq2UOnQNGMNSsfWcy5PSq9t7KpJoMTSA0a+MQ Yb6QIs+RmO4e384kJA7vurvqily/nubqUHnbTrElQLhkNtUUFmn9uvZF8r8oUHA+l4 1G7YtFErwCNy/ZbNikUqmvzP1zJaLFkjcESuvdnQajvyAtogtir3n07O9UVOUZjTV+ 0/EwVSVhCaKhXZENPMFCzxB8tzAkDEIBa8C2C2hzjPHJQ/JX0NPDF9HKkzO6tbGPcY v10NY+LvAltWC93U1XiWTDzT1CfXWUGgxrZPQXnQLXp1Z7803mXx5AS21MuQIyIGIl wOnXA6wwgm/Og==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/o6ixkqQLTW3_4SrBt7-_13MJ3ys
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 16:45:34 -0000

Collin,

Thanks for reviewing this. I have some followup questions for you inline.

On 11/25/14 7:34 AM, Colin Perkins wrote:
> Hi,
>
> The chairs asked me to review the ABNF in rfc4566bis. This looks to be
> going in the right direction. Some comments:

> *a=cat:*
> - This attribute was used with SAP [RFC2974] to categorise session
> announcements, for example “a=cat:sport.football”. There was never a
> formal definition beyond a dot-separated string, and intentionally no
> central registry of categories.
> - Should likely have a not to say this is obsolete.
> - Syntax should likely be non-ws-string

I'm ok with this if nobody objects.

> *a=keywds:*
> - Like a=cat:, this was intended for use with SAP. I’m not aware that it
> was ever implemented.
> - Should likely have a not to say this is obsolete.
> - Syntax should likely be: “keywords = text”

I'm ok with this if nobody objects.

> *a=tool:*
> - Something like HTTP user agent string
> - Syntax should likely be: “tool-name-and-version = text”

WFM

> *a=ptime: *and *a=maxptime:*
> - Are these always integers?

There is a separate thread on this.

> *a=rtpmap:*
> - payload-type is an integer in the range 0-127 in RTP
> - encoding-name is a MIME subtype, and should have the syntax to match this
> - is clock-rate always an integer?

If there is no way that larger values could ever be used then I'm fine 
with calling out this restriction. I'll probably do it in text rather 
than in ABNF.

> *a=type:*
> - I assume a registry was intended, but it’s not clear there’s any need now

Do you mean that you don't think we need a mechanism to define further 
values? Or that it would be sufficient to do so with another update to 
this document?

Do you know if these names were intended to be case sensitive? That is 
an important distinction to make. And whatever choice is made will 
potentially have backward compatibility problems for somebody.

> *a=charset:*
> - This is a name from the registry at
> http://www.iana.org/assignments/character-sets/character-sets.xhtml and
> needs to follow that syntax

In this and other cases where what goes in the SDP is a reference to 
something defined in a registry, I am inclined to give a simplified 
syntax that might be a superset of what is permitted in the registry. It 
doesn't matter a whole lot if it allows some invalid values, because 
such names will never be in the registry.

This will help implementers. And when the exact formal definition isn't 
available in ABNF, or is very complex, it can also ease formal checking 
of the SDP ABNF.

Given that explanation, is there anything wrong with what I have?

> *a=sdplang:* and *a=lang:*
> - Should reference the RFC5646 definition

Same comment as charset.

> *a=quality:*
> - I thought the intent here was a real number, in the range 0…10

What I could find only discussed quality in the context of video media, 
and restricted the range to 0..10 in that case. But it didn't explicitly 
limit (or define) the use of quality for other media. It seems 
reasonable to me that the same range would apply to any media where 
quality applies, but I wasn't sure.

Also, should the values here be restricted to integral values, or should 
fractional values be allowed?

BTW - I just noticed I have an error in my ABNF: I limit the 
quality-value to an integer, which excludes zero. So I need to change 
the abnf in one way or another.

> *a=fmtp:*
> - The format parameters are MIME media type parameters, and need to
> reflect their syntax.

My understanding is that the values are whatever was in the <fmt> field 
of the associated m-line. What is valid there is defined for each 
<proto> field. For the RTP variants, it is a payload type. For UDP it is 
a media (sub)type. But we can't know in general what if might be for 
other <proto>s, since new ones could be defined in the future.

The m-line syntax defines the fmt as a token. So I figured that the same 
definition should be used here.

	Thanks,
	Paul


From nobody Mon Dec  1 12:41:37 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0EC21A8A82 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 12:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 nJERB-Pdq7gu for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 12:41:34 -0800 (PST)
Received: from resqmta-po-08v.sys.comcast.net (resqmta-po-08v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:167]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07A1B1A8AC7 for <mmusic@ietf.org>; Mon,  1 Dec 2014 12:41:32 -0800 (PST)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-08v.sys.comcast.net with comcast id NLgu1p0024ueUHc01LhXTH; Mon, 01 Dec 2014 20:41:31 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-03v.sys.comcast.net with comcast id NLhW1p00i3Ge9ey01LhXVW; Mon, 01 Dec 2014 20:41:31 +0000
Message-ID: <547CD27A.3090006@alum.mit.edu>
Date: Mon, 01 Dec 2014 15:41:30 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417466491; bh=3Ba45dos1C4GHy22hzteXM8lYJSgBmtlsmScnn2I4IA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=qvIBeln0RoVWingFb3+GyQjLSHx/clSfHU0PF3aLFlHyMQT/eaQ0QEfCMI4Mva+GB R5E7Xok/jMriJ0qBPrg1p9HVyhcxGktXF+Cb7eI3kDC0gNo82Xi74C1jV9O/t5N8bW OkpyJXzTfT7aWOY2MOGz24BzDEKP1mfv1OwekGAZFAhTnYNOIK/fW1D4ocyxpXCAb1 haBsSBMR9op33AGAsg92ti95bXOC9Xqz0vru++8yxU1oTElb4xrsH4QaTsYCH1+yee ljvk23LejKWLLTJEywrXgYdmiN8mCLk/L+kyp9uw00jUI+9NOgOIomChM06OHLgm2R f3138Y6TPCckg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5QDRTqvCKc0BT2x6kW1qCrQqNTI
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 20:41:35 -0000

On 11/27/14 3:54 PM, Christer Holmberg wrote:
> Hi,
>
> For SCTP-SDP, the general idea is that the SDP connection attribute is
> used in the same way as for TCP,
>
> i.e. an attribute ‘new’ value means that a new SCTP association shall be
> created.
>
> For ‘SCTP’ there should be no issues. The procedures are more or less
> identical as for TCP (the difference being that both endpoints initiate
> the SCTP association).
>
> ---
>
> For ‘DTLS/SCTP’, there are some decisions to make:
>
> -If the transport layer protocol is UDP, I assume a ‘new’ value will not
> automatically re-establish the DTLS connection – only the SCTP
> association will be re-established.

Why?

If some part of the 5-tuple changes then it will be *necessary* to 
establish a new DTLS connection. Even if the 5-tuple doesn't change, 
aren't there going to be cases where you want to reestablish the DTLS?

> -However, if the transport layer protocol is TCP, does that mean that a
> ‘new’ value will mean that BOTH the TCP connection, AND the SCTP
> association, will be re-established? IF the TCP connection is also
> re-established, then I guess the DTLS connection will be re-established.

There are all consequences of using the same atttribute to control 
independent behavior at two different layers of the protocol stack.

The *right* fix would be to have one attribute for the DTLS behavior and 
another for the SCTP behavior.

	Thanks,
	Paul


From nobody Mon Dec  1 14:05:58 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4217A1AC419 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, SPF_SOFTFAIL=0.665] 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 pwwOtWSYmG3p for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:05:53 -0800 (PST)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:170]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E8A11AC41E for <mmusic@ietf.org>; Mon,  1 Dec 2014 14:05:53 -0800 (PST)
Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-11v.sys.comcast.net with comcast id NN5A1p0094vw8ds01N5slc; Mon, 01 Dec 2014 22:05:52 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-04v.sys.comcast.net with comcast id NN5s1p0043Ge9ey01N5swP; Mon, 01 Dec 2014 22:05:52 +0000
Message-ID: <547CE63F.8030307@alum.mit.edu>
Date: Mon, 01 Dec 2014 17:05:51 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D53F54A@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D53F54A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417471552; bh=HM4eIigJ/cLh26O9FuISGbUQGG+voN2tVcMS5zQDMHs=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=HlMyOm+yIMeU3phf0gF1m6Z6vkTWmutj2Ox1RhGuZ7lFuFk+Gd1IUdPohhe0iFi+x ZcDVr6nCUkUjdEOBq8XcCZNz+Syay6kgwvzBFtzBnlY2cSCU46QIubiehJf5BoFPK3 NVicmRDZN9vZX9l3ZRX4bGDlRS6FkPAjAGpUpoIW54XJw53XxsQ75GR8FKNGjxTDRY /xcZIDlT8UQXzzntNgP8cmjrj5FxAv1M5oQ4M/mYOLkLktRhF+EMb0UAXjfCX2EfT1 D9RnQNoYng4lTlwW20TxLqwJcepPfm00vEduxNoM/5cfo0shQ0tyHvITONyTM/dn9J mA2Wkm3Z+bJbw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/FIzrBsm-CkFLNgHWeRlVlPruSrA
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 22:05:55 -0000

Christer,

Here are some comments on the new version:

Section 4.3:

Using MIME subtypes on the m-line doesn't really work well. The value 
doesn't really define a data format - it defines a discipline for 
choosing and using stream ids, and possibly a format for each one. I 
think that all of the first paragraph should be deleted, with the 
exception of the first sentence.

Section 5.1:

IMO 5000 is a bad choice for the default port value. It falls in the 
middle of the registered port list. It isn't currently registered (I 
don't know why) but it potentially could. I suggest that a number 
outside of the registered port range (>49151) would be safest. To avoid 
being arbitrary, I suggest 65535 - the largest possible 16 bit number.

Section 6.2:

I don't understand why sctpmap-attr is defined, since it isn't 
referenced anywhere. I think it is a holdover from when there was an 
sctpmap attribute.

It seems that what is being done here is to define the syntax of a=fmtp 
for all fmt values that might be used with sctp. I don't think that is 
kosher. I think fmtp needs to be defined for webrtc-datachannel, and 
again for each other application-usage that wants to use it.

It is unpleasant to expect all application-usages to do this. But the 
alternative is to go back to defining a special attribute for 
max-message-size. Perhaps:

      Attribute name: sctp-attr
      Attribute value: sctp-attr-value
      Attribute Syntax:

      sctp-attr-value = association-usage [max-message-size]
      max-message-size  =  "max-message-size" EQUALS 1*DIGIT

Section 8:

I think something probably needs to be said about 
sendonly/recvonly/inactive. I'm not sure what. Maybe they shouldn't be 
used at all. Or maybe they can make some sort of sense.

Section 9:

The NOTE seems inadequate. If SCTP is being used in an environment that 
does gating based on SDP, then multihoming probably won't work. None of 
the negotiated alternative addresses will get their gates opened. So 
maybe more needs to be said about this.

Section 10.1:

The last paragraph about NATs references RFC6951. Wouldn't it be clearer 
if it simply referenced DTLS/SCTP defined in this draft?

Section 10.2:

This isn't quite true is it? ICE is defined to work over DTLS/SCTP. 
While the emphasis is on those cases where the SCTP is bundled with 
SRTP, it should work just fine without bundle.

	Thanks,
	Paul

On 11/28/14 9:07 AM, Christer Holmberg wrote:
> Hi,
>
> I’ve submitted a new version of the SCTP-SDP draft. There has been quite
> big editorial changes from the previous version. New stuff, including
> the SDP Offer/Answer procedures, have been added.
>
> I have yet NOT changed the proto values (e.g ‘DTLS/SCTP’ ->
> ‘UDP/DTLS/SCTP’). In Honolulu there was a generic discussion regarding
> that, whether to use “DTLS” or “TLS” etc, and I’d like to see some
> documented outcome regarding that before changing.
>
> There are currently two open issue (of which one is related to the proto
> values) documented in the draft.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Mon Dec  1 14:15:57 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786171ACCC7 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 FKJEfIR5x6QJ for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:15:42 -0800 (PST)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46AB01A913B for <mmusic@ietf.org>; Mon,  1 Dec 2014 14:15:42 -0800 (PST)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-09v.sys.comcast.net with comcast id NNFA1p0054ueUHc01NFhYg; Mon, 01 Dec 2014 22:15:41 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-03v.sys.comcast.net with comcast id NNFh1p0093Ge9ey01NFhzl; Mon, 01 Dec 2014 22:15:41 +0000
Message-ID: <547CE88C.40605@alum.mit.edu>
Date: Mon, 01 Dec 2014 17:15:40 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D534E7B@ESESSMB209.ericsson.se> <2649C056-4D86-4448-B71F-A42954E1BF49@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D538EF9@ESESSMB209.ericsson.se> <07B6DC62-93DB-4C15-BECE-68BB70B663FB@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D5390C0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63E883@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417472141; bh=JAmHZkL4SWP2bYsL8sMn733ea03mdinsXQ09hPXUeyk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=USWitme2LPyAxHx1e3A48rurvBz81/AqW+j18nSlVRi+LSn7lYjnlPW2lenQbM9VF E02XIh3uV/k+mrUmOdVESFSy11B5JhJqIADBYJyrvfhCul2TEZRKpy6xzjYK7BfYE9 C9vCOyoq8K6Q8SBs9dZ6Y2aCZfYmdKCpJy3FYJe8kV+C9y9Wp43uLsjCpa37DR6eL5 J/PMpPyQmB2lZ5nbI/Ulw2rI0O4tKB+/klgaQVkWdqEb0tHTXMCromKh7Oo/nZ6vS8 DItDpsZNL2oqJIOL4VRUIdFGLwhhpKYmcIadQ1O3bi5tjJhtxPv5YFIRUu89zi1o85 bTlzgW8ydVUmg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/aJCQE-9LRAzuz5Hs_cdXPkBxLS8
Subject: Re: [MMUSIC] Single SCTP usage per SDP session?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 22:15:43 -0000

On 11/26/14 2:00 PM, Christer Holmberg wrote:

> <Raju>
>> Per my understanding, draft-ietf-tsvwg-sctp-dtls-encaps just talks about SCTP over DTLS and allowing multiple SCTP associations, which is perfectly fine.
>> Then it is possible to come up with SCTP-SDP semantics to use that capability.
>> One m= line allowing one SCTP over DTLS limit is fine. Using BUNDLE you can replicate same 4-tuple in multiple m= lines. Then there is only one DTLS association
>> established and multiple SCTP associations over that is possible (one per m= line).
>> If BUNDLE is not used then I believe same 4-tuple on multiple m= lines are NOT possible. This is because, per my understanding, unlike TCP/native-SCTP used under non-
>> ICE environments, in ICE-environments the TCP/UDP port specified is used both as client and server port for DTLS.
>
> Even with BUNDLE, you would have to use the same m= line port value from the beginning, which is not allowed. So, you basically would have to add the additional SCTPoDTLS m= lines once the usage of BUNDLE has been negotiated.

bundle-only would allow you to set this up.

	Thanks,
	Paul


From nobody Mon Dec  1 14:29:41 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3464B1ACC72 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] 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 eHmtF8pxZDfn for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 14:29:37 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40CCB1ACD03 for <mmusic@ietf.org>; Mon,  1 Dec 2014 14:29:37 -0800 (PST)
Received: from ppp118-209-77-237.lns20.mel4.internode.on.net ([118.209.77.237]:53331 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <Christian.Groves@nteczone.com>) id 1XvZTD-0000S0-28 for mmusic@ietf.org; Tue, 02 Dec 2014 09:29:27 +1100
Message-ID: <547CEBC5.5070209@nteczone.com>
Date: Tue, 02 Dec 2014 09:29:25 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu>
In-Reply-To: <547C9B29.9060801@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/75RYeBHOdekOIJ7olWfckrKvEsc
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 22:29:39 -0000

Hello,

>> *a=keywds:*
>> - Like a=cat:, this was intended for use with SAP. I’m not aware that it
>> was ever implemented.
>> - Should likely have a not to say this is obsolete.
>> - Syntax should likely be: “keywords = text”
>
> I'm ok with this if nobody objects.

[CNG] It seems at least someone is using it: 
http://www.gwg.nga.mil/misb/docs/rp/RP1302.pdf


Regards, Christian


From nobody Mon Dec  1 15:39:58 2014
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5851ACDA0 for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 15:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_STOP=2.3] 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 9yhFlki5z6cT for <mmusic@ietfa.amsl.com>; Mon,  1 Dec 2014 15:39:53 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6249B1ACDDF for <mmusic@ietf.org>; Mon,  1 Dec 2014 15:39:53 -0800 (PST)
Received: from [81.187.2.149] (port=39701 helo=[192.168.0.22]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1XvaZL-0004QW-3o; Mon, 01 Dec 2014 23:39:51 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <547C9B29.9060801@alum.mit.edu>
Date: Mon, 1 Dec 2014 23:39:46 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org>
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/kKEaj8AkKewHgXjnqTSMK4XJjA0
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 23:39:55 -0000

Paul,

On 1 Dec 2014, at 16:45, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> Collin,
>=20
> Thanks for reviewing this. I have some followup questions for you =
inline.
>=20
> On 11/25/14 7:34 AM, Colin Perkins wrote:
>> Hi,
>>=20
>> The chairs asked me to review the ABNF in rfc4566bis. This looks to =
be
>> going in the right direction. Some comments:
>=20
>> *a=3Dcat:*
>> - This attribute was used with SAP [RFC2974] to categorise session
>> announcements, for example =93a=3Dcat:sport.football=94. There was =
never a
>> formal definition beyond a dot-separated string, and intentionally no
>> central registry of categories.
>> - Should likely have a not to say this is obsolete.
>> - Syntax should likely be non-ws-string
>=20
> I'm ok with this if nobody objects.
>=20
>> *a=3Dkeywds:*
>> - Like a=3Dcat:, this was intended for use with SAP. I=92m not aware =
that it
>> was ever implemented.
>> - Should likely have a not to say this is obsolete.
>> - Syntax should likely be: =93keywords =3D text=94
>=20
> I'm ok with this if nobody objects.
>=20
>> *a=3Dtool:*
>> - Something like HTTP user agent string
>> - Syntax should likely be: =93tool-name-and-version =3D text=94
>=20
> WFM
>=20
>> *a=3Dptime: *and *a=3Dmaxptime:*
>> - Are these always integers?
>=20
> There is a separate thread on this.
>=20
>> *a=3Drtpmap:*
>> - payload-type is an integer in the range 0-127 in RTP
>> - encoding-name is a MIME subtype, and should have the syntax to =
match this
>> - is clock-rate always an integer?
>=20
> If there is no way that larger values could ever be used then I'm fine =
with calling out this restriction. I=92ll probably do it in text rather =
than in ABNF.

The payload type is a 7-bit field in the RTP header, so definitely =
cannot be outside this range. Writing this in the text makes sense.

>> *a=3Dtype:*
>> - I assume a registry was intended, but it=92s not clear there=92s =
any need now
>=20
> Do you mean that you don't think we need a mechanism to define further =
values? Or that it would be sufficient to do so with another update to =
this document?

This list hasn=92t changed in RFC 2327 in 1998. I think it=92s safe to =
leave updates to a future revision of this document.

> Do you know if these names were intended to be case sensitive? That is =
an important distinction to make. And whatever choice is made will =
potentially have backward compatibility problems for somebody.

I expect the general rule at the start of Section 5 (top of page 8) =
applies:

   An SDP session description consists of a number of lines of text of
   the form:

      <type>=3D<value>

   where <type> MUST be exactly one case-significant character and
   <value> is structured text whose format depends on <type>.  In
   general, <value> is either a number of fields delimited by a single
   space character or a free format string, and is case-significant
   unless a specific field defines otherwise.

Hence, this is case significant.


>> *a=3Dcharset:*
>> - This is a name from the registry at
>> http://www.iana.org/assignments/character-sets/character-sets.xhtml =
and needs to follow that syntax
>=20
> In this and other cases where what goes in the SDP is a reference to =
something defined in a registry, I am inclined to give a simplified =
syntax that might be a superset of what is permitted in the registry. It =
doesn't matter a whole lot if it allows some invalid values, because =
such names will never be in the registry.
>=20
> This will help implementers. And when the exact formal definition =
isn't available in ABNF, or is very complex, it can also ease formal =
checking of the SDP ABNF.
>=20
> Given that explanation, is there anything wrong with what I have?

Why not reference the correct ABNF from RFC 2978? I don=92t understand =
the desire to put something incorrect here.=20

>> *a=3Dsdplang:* and *a=3Dlang:*
>> - Should reference the RFC5646 definition
>=20
> Same comment as charset.

Same answer. There=92s already a standard ABNF syntax for these, and =
this document should refer to it rather than trying to define something =
new.

>> *a=3Dquality:*
>> - I thought the intent here was a real number, in the range 0=8510
>=20
> What I could find only discussed quality in the context of video =
media, and restricted the range to 0..10 in that case. But it didn't =
explicitly limit (or define) the use of quality for other media. It =
seems reasonable to me that the same range would apply to any media =
where quality applies, but I wasn't sure.
>=20
> Also, should the values here be restricted to integral values, or =
should fractional values be allowed?

I always assumed fractional values were allowed, but you=92d have to =
check with someone who=92s implemented this.

> BTW - I just noticed I have an error in my ABNF: I limit the =
quality-value to an integer, which excludes zero. So I need to change =
the abnf in one way or another.
>=20
>> *a=3Dfmtp:*
>> - The format parameters are MIME media type parameters, and need to
>> reflect their syntax.
>=20
> My understanding is that the values are whatever was in the <fmt> =
field of the associated m-line. What is valid there is defined for each =
<proto> field. For the RTP variants, it is a payload type. For UDP it is =
a media (sub)type. But we can't know in general what if might be for =
other <proto>s, since new ones could be defined in the future.
>=20
> The m-line syntax defines the fmt as a token. So I figured that the =
same definition should be used here.

For RTP, you do know explicitly that the <format specific parameters> in =
the a=3Dfmtp: line are MIME media subtype parameters, and need to =
conform to that syntax.

--=20
Colin Perkins
https://csperkins.org/





From nobody Tue Dec  2 00:22:57 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 140E31A0172 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:22:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 NdV4Af6drwsa for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:22:52 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 702E81A00C3 for <mmusic@ietf.org>; Tue,  2 Dec 2014 00:22:52 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-f6-547d76d90ecf
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 01.C0.04231.9D67D745; Tue,  2 Dec 2014 09:22:50 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 09:22:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Single SCTP usage per SDP session?
Thread-Index: AdAIiilGRQ9HT1LDRYu/Q2dfZ4TTzAAxes8AAAUE9XD///IzAP//5OAwgABrp4D//7ZsQIAIlnMA//9GRRA=
Date: Tue, 2 Dec 2014 08:22:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D56AD9F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D534E7B@ESESSMB209.ericsson.se> <2649C056-4D86-4448-B71F-A42954E1BF49@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D538EF9@ESESSMB209.ericsson.se> <07B6DC62-93DB-4C15-BECE-68BB70B663FB@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D5390C0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63E883@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se> <547CE88C.40605@alum.mit.edu>
In-Reply-To: <547CE88C.40605@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvje6tstoQg8Xr+S2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj7f35bAWruCo6Tsxka2BczNHFyMkhIWAi sWLjUiYIW0ziwr31bF2MXBxCAkcYJVY8XckI4SxmlNh9Zx1QFQcHm4CFRPc/bZAGEQFfiWeP b7OB2MJA4Xm72pkh4pYScz69h7KTJGY+ncsK0soioCJxdIMwSJgXqHVe3zVmiPE/mCX+H/wN Vs8poCUx43gzmM0IdND3U2vAjmMWEJe49WQ+1KECEkv2nGeGsEUlXj7+xwphK0n82HCJBaJe R2LB7k9sELa2xLKFr5khFgtKnJz5hGUCo+gsJGNnIWmZhaRlFpKWBYwsqxhFi1OLi3PTjYz1 Uosyk4uL8/P08lJLNjEC4+Tglt+6OxhXv3Y8xCjAwajEw/vxU02IEGtiWXFl7iFGaQ4WJXHe RefmBQsJpCeWpGanphakFsUXleakFh9iZOLglGpgrNtjk/jlf7DqBe97IqpMjvvEIha/6Dbz MsmeKF/YcnpyyMwCe7fgnv1hc8wTjr0KtXLTKUu8YMFc1PTN1qLnMo+v9+9Jj/vTbj3oN5jX rjxh4/Hza6JSY3IbOLOj39/uXLdfnuMYp36u74WQFtHsiVunzFGfPU3q/MWFLu7Fcnk9nOaZ az4psRRnJBpqMRcVJwIA+934SXQCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/hCmPV-1Sze3mHXvEMCm8jH0jE5c
Subject: Re: [MMUSIC] Single SCTP usage per SDP session?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 08:22:54 -0000

Hi,

>>> Per my understanding, draft-ietf-tsvwg-sctp-dtls-encaps just talks abou=
t SCTP over DTLS and allowing multiple SCTP associations, which is perfectl=
y fine.
>>> Then it is possible to come up with SCTP-SDP semantics to use that capa=
bility.
>>> One m=3D line allowing one SCTP over DTLS limit is fine. Using BUNDLE=20
>>> you can replicate same 4-tuple in multiple m=3D lines. Then there is on=
ly one DTLS association established and multiple SCTP associations over tha=
t is possible (one per m=3D line).
>>> If BUNDLE is not used then I believe same 4-tuple on multiple m=3D=20
>>> lines are NOT possible. This is because, per my understanding, unlike T=
CP/native-SCTP used under non- ICE environments, in ICE-environments the TC=
P/UDP port specified is used both as client and server port for DTLS.
>>
>> Even with BUNDLE, you would have to use the same m=3D line port value fr=
om the beginning, which is not allowed. So, you basically would have to add=
 the additional SCTPoDTLS m=3D lines once the usage of BUNDLE has been nego=
tiated.
>
> bundle-only would allow you to set this up.

Correct.

But, then we would need to have rules saying that you are not allowed to mo=
ve an m=3D line associated with a SCTP usage out of the BUNDLE group, etc.

Regards,

Christer


From nobody Tue Dec  2 00:49:20 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8E21A020A for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 xfSGLqCHkONt for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:49:18 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C01A1A0367 for <mmusic@ietf.org>; Tue,  2 Dec 2014 00:49:17 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-a4-547d7d0b00f8
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id E8.F5.04231.B0D7D745; Tue,  2 Dec 2014 09:49:16 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 09:49:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQ==
Date: Tue, 2 Dec 2014 08:49:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyM+JvjS5PbW2IwfkeJoupyx+zWKzYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4Mr41aBZcF6h4ty//UwNjDskuxg5OSQETCSa f09hg7DFJC7cWw9kc3EICRxhlJj68So7hLOYUWLxocWMXYwcHGwCFhLd/7RBGkQEfCWePb4N 1iwsECVxcm83K0Q8WuLd381Qtp7EiZbJLCCtLAIqEpfXVoGYvECtt7aGg1QwAq39fmoNE4jN LCAucevJfCaIcwQkluw5zwxhi0q8fPyPFcJWkvix4RILRL2OxILdn9ggbG2JZQtfg9XzCghK nJz5hGUCo/AsJGNnIWmZhaRlFpKWBYwsqxhFi1OLi3PTjYz1Uosyk4uL8/P08lJLNjECA/7g lt+6OxhXv3Y8xCjAwajEw/vxU02IEGtiWXFl7iFGaQ4WJXHeRefmBQsJpCeWpGanphakFsUX leakFh9iZOLglGpg7FvhsnH9Q0lb07j8DpHLfr6qfxabhPQuyNLfmHFNxWAyn5SIy+bDa7L3 /tzRe5nXvYDduFj838xJZ9bvu8nBGnVCKinqIUO+cNkH22uPfi65zxTScqbMcYmWbZNoy6Ps hTlap4/P1NoZnqDZuOXyWr65J9iSJt9dGZY60Tpo77XHHkvsHczLlViKMxINtZiLihMB+fES MlkCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/viZn4YgvVVIKeKM1jKM65vJBMyQ
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 08:49:19 -0000

Hi Paul,

Thanks for your comments! Reply inline.

> Section 4.3:
>
> Using MIME subtypes on the m-line doesn't really work well. The value doe=
sn't really define a data format - it defines a discipline for choosing and=
 using stream=20
> ids, and possibly a format for each one. I think that all of the first pa=
ragraph should be deleted, with the exception of the first sentence.

I can do that, if no one else have an issue doing so.

-------------

> Section 5.1:
>
> IMO 5000 is a bad choice for the default port value. It falls in the midd=
le of the registered port list. It isn't currently=20
> registered (I don't know why) but it potentially could. I suggest that a =
number outside of the registered port range=20
> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the=
 largest possible 16 bit number.

I have no problem to change the default value.

However, 5000 was defined before I got involved with the draft, so I think =
it would be good to get some input from Gonzalo and/or Salvatore whether th=
ere was some specific reason for 5000.

-------------

> Section 6.2:
>
> I don't understand why sctpmap-attr is defined, since it isn't referenced=
 anywhere. I think it is a holdover from when there was an sctpmap attribut=
e.

Correct, that is a mistake.

The purpose of Section 6.2 is to define the format of the SDM fmtp attribut=
e when used with SCTP.

> It seems that what is being done here is to define the syntax of a=3Dfmtp=
 for all fmt values that might be used with sctp. I don't think that is kos=
her.=20
> I think fmtp needs to be defined for webrtc-datachannel, and again for ea=
ch other application-usage that wants to use it.
>
> It is unpleasant to expect all application-usages to do this. But the alt=
ernative is to go back to defining a special attribute for max-message-size=
. Perhaps:
>
>      Attribute name: sctp-attr
>      Attribute value: sctp-attr-value
>      Attribute Syntax:
>
>      sctp-attr-value =3D association-usage [max-message-size]
>      max-message-size  =3D  "max-message-size" EQUALS 1*DIGIT

If we decide to have a special attribute, why not simply call it "a=3Dmax-m=
essage-size"?

We only allow a single association-usage per m- line, so there is no need t=
o explicitly map the fmt value to a specific sctp-attr attribute.

      Attribute name: sctp-max-message-size	(We can use a shorter name)
      Attribute value: max-message-size
      Attribute Syntax:

      sctp-max-message-size =3D max-message-size
      max-message-size  =3D  1*DIGIT

-------------

> Section 8:
>
> I think something probably needs to be said about sendonly/recvonly/inact=
ive. I'm not sure what. Maybe they shouldn't be used at all. Or maybe they =
can make some sort of sense.

I was thinking about the same thing, but left it out of this version on pur=
pose (I should have added an open issue regarding it, though).

I see no reason why we couldn't use sendonly/recvonly/inactive also for SCT=
P - assuming it only impacts what is sent on the SCTP association. I.e. it =
would not impact the DTLS connection, and whatever (UDP or TCP) is below DT=
LS.

-------------

> Section 9:
>
> The NOTE seems inadequate. If SCTP is being used in an environment that d=
oes gating based on SDP, then multihoming probably won't work. None of the =
negotiated alternative addresses will get their gates opened. So maybe more=
 needs to be said about this.

So, you don't think the existing text is wrong - you just think we need mor=
e text, right?

-------------

> Section 10.1:
>
> The last paragraph about NATs references RFC6951. Wouldn't it be clearer =
if it simply referenced DTLS/SCTP defined in this draft?

I can look into that.

-------------

> Section 10.2:
>
> This isn't quite true is it? ICE is defined to work over DTLS/SCTP.=20
>
> While the emphasis is on those cases where the SCTP is bundled with SRTP,=
 it should work just fine without bundle.

Ok, I guess the text should be more clear, and talk about "pure" SCTP and S=
CTP/DTLS.

Regards,

Christer


From nobody Tue Dec  2 00:56:55 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D6DC1A0369 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6ExCebFEVxkU for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 00:56:52 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 560431A0387 for <mmusic@ietf.org>; Tue,  2 Dec 2014 00:56:52 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-fc-547d7ed2103c
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 60.0D.29772.2DE7D745; Tue,  2 Dec 2014 09:56:50 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 09:56:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
Thread-Index: AdAKgkYeRp59/KWiSPW7X4BmEjVKXwDHIeIAABubemA=
Date: Tue, 2 Dec 2014 08:56:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se> <547CD27A.3090006@alum.mit.edu>
In-Reply-To: <547CD27A.3090006@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvje6lutoQg5d35SymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvjxpeJrAWtfBXbPu1gbmDs5e5i5OSQEDCR uHh+PSOELSZx4d56ti5GLg4hgSOMEof/bYJyFjNK9E28y9rFyMHBJmAh0f1PG6RBRMBX4tnj 22wgtrCAu8T6/XtZIeIeEgfnToGyrSSO9D1jArFZBFQktm/ZC1bPC9T7evNfsLiQQL7Es4ff wY7gFNCROHXwCFicEeig76fWgNnMAuISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YIWwliR8bLrFA 1OtILNj9iQ3C1pZYtvA1M8ReQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVo2hxanFSbrqR kV5qUWZycXF+nl5easkmRmCcHNzy22AH48vnjocYBTgYlXh4P3yqCRFiTSwrrsw9xCjNwaIk zrvw3LxgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYyMmevz4q4uSFiyJD5hcdW5bYlvg5ld zoe18zSl34u/884n48XnmZFV00+Ilhm/yeAyMdBb4Kdzbiv38Qsc05f9Wqoja/sqLqzIPmuD xc9XF1qFWn/uesnVEnzqkkqxp+zBE/eLd7xwb6mZ2O506+Frnrl/TvG8XvToSvPDY0tm2aa0 iv82aA5SYinOSDTUYi4qTgQAd7e+NnQCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2PtG9ym-ET3lIgGHGtE4jtIcPVU
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 08:56:54 -0000

Hi,

>> For SCTP-SDP, the general idea is that the SDP connection attribute is=20
>> used in the same way as for TCP,
>>
>> i.e. an attribute 'new' value means that a new SCTP association shall=20
>> be created.
>>
>> For 'SCTP' there should be no issues. The procedures are more or less=20
>> identical as for TCP (the difference being that both endpoints=20
>> initiate the SCTP association).
>>
>> ---
>>
>> For 'DTLS/SCTP', there are some decisions to make:
>>
>> -If the transport layer protocol is UDP, I assume a 'new' value will=20
>> not automatically re-establish the DTLS connection - only the SCTP=20
>> association will be re-established.
>
> Why?
>
> If some part of the 5-tuple changes then it will be *necessary* to establ=
ish a new DTLS connection.

Correct - I should have clarified that I am talking about the case there th=
e 5-tuple does not change.

> Even if the 5-tuple doesn't change, aren't there going to be cases where =
you want to reestablish the DTLS?

Maybe there are. But, this is related to the question whether you need to s=
ignal that in SDP.

>> -However, if the transport layer protocol is TCP, does that mean that=20
>> a 'new' value will mean that BOTH the TCP connection, AND the SCTP=20
>> association, will be re-established? IF the TCP connection is also=20
>> re-established, then I guess the DTLS connection will be re-established.
>
> There are all consequences of using the same atttribute to control indepe=
ndent behavior at two different layers of the protocol stack.

Yes.

> The *right* fix would be to have one attribute for the DTLS behavior and =
another for the SCTP behavior.

We could for sure define an SDP "sctp-setup" attribute, IF people see a nee=
d for it.

Regards,

Christer


From nobody Tue Dec  2 04:00:55 2014
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632541A1AE5 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:00:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 jnpROrBRZK7D for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:00:52 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B0911A1AE6 for <mmusic@ietf.org>; Tue,  2 Dec 2014 04:00:49 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-2b-547da9f04931
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 7F.D2.24955.0F9AD745; Tue,  2 Dec 2014 13:00:48 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.148]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 13:00:47 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQAEmAMA
Date: Tue, 2 Dec 2014 12:00:46 +0000
Message-ID: <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <002A779D9A006A4FA7B24232EAAC29D3@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGfG3RvfDytoQg12XhS2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj45T3LAX/2Cqm/nVqYDzC2sXIySEhYCJx bUcvI4QtJnHh3nq2LkYuDiGBI4wSTy/2MkM4ixkl9hw9xw5SxSZgJvH84RZmEFsEyL7+uZcJ xGYW8JV4ueALWFxYIEpi2bp/7BA10RLv/m5mhbCNJLqu97KA2CwCKhKfplwGs3kF7CVO3zoC NkcIaM6VjyfBbE4BP4kdV1eD2YxA130/tQZql7jErSfzmSCuFpBYsuc8M4QtKvHy8T+oz5Qk Gpc8YYWo15FYsPsTG4RtLfHtxxGouLbEsoWvmSFuEJQ4OfMJywRG8VlIVsxC0j4LSfssJO2z kLQvYGRdxShanFqclJtuZKyXWpSZXFycn6eXl1qyiREYbwe3/FbdwXj5jeMhRgEORiUe3g+f akKEWBPLiitzDzFKc7AoifMuPDcvWEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAOjiYX5nHU8 HrUP9sb06N4L+fX7/fm6eYc4Q/WuMMhXry1/V2pyZpPhCdO89PPe+svTfzQrRv2vVTt/dEZh QLvTZOYfpdO7VDbrJjzM8mXhcb52fv+Vrdf+nwpVONCV/5/Ruq6BjXv+jsuLVrZsVbetmukr eWjeR0emzNSz9qyPTBfwh7zaNSlYiaU4I9FQi7moOBEAxCQ+YZgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/GI859fHaCiHp7c1ATWmKn7_MCBk
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 12:00:53 -0000

Hi there,

On Dec 2, 2014, at 10:49 AM, Christer Holmberg <christer.holmberg@ericsson.=
com> wrote:
>=20
>=20
>> Section 5.1:
>>=20
>> IMO 5000 is a bad choice for the default port value. It falls in the mid=
dle of the registered port list. It isn't currently=20
>> registered (I don't know why) but it potentially could. I suggest that a=
 number outside of the registered port range=20
>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - th=
e largest possible 16 bit number.
>=20
> I have no problem to change the default value.
>=20
> However, 5000 was defined before I got involved with the draft, so I thin=
k it would be good to get some input from Gonzalo and/or Salvatore whether =
there was some specific reason for 5000.
>=20
> -------------

5000 is the default value the current/available SCTP over TLS are using.


br
/Salvatore=


From nobody Tue Dec  2 04:12:01 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB9E31A1AF2 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:11:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6S8_HWg5fQ2q for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:11:57 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E88FA1A1AEA for <mmusic@ietf.org>; Tue,  2 Dec 2014 04:11:56 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-47-547dac8a4c52
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 9A.B2.04076.A8CAD745; Tue,  2 Dec 2014 13:11:55 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 13:11:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQAEmAMAAAJpkeA=
Date: Tue, 2 Dec 2014 12:11:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D56E80D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com>
In-Reply-To: <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM+JvjW73mtoQgztLhCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSuje91DloID7BWTDs1ia2D8ytrFyMkhIWAi cWzNf2YIW0ziwr31bCC2kMARRolZVyK6GLmA7MWMEu09h1i6GDk42AQsJLr/aYOYIkC9jw/k g5QzC/hKvFzwBWyMsECUxMm93WDjRQSiJd793QxlW0n0vfvJBGKzCKhIPG3axgJi8wL1nr7W xAyxqplRYuKeBewgCU4BB4k9DdfBmhmBbvt+ag0TxDJxiVtP5jNB3CwgsWTPeaj7RSVePv4H 9ZeSxI8Nl1gg6nUkFuz+xAZha0ssW/iaGWKxoMTJmU9YJjCKzUIydhaSlllIWmYhaVnAyLKK UbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzB6Dm75bbWD8eBzx0OMAhyMSjy8Hz7VhAixJpYV V+YeYpTmYFES5114bl6wkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkbpJ8wW+g/+yuh+CFg3 8fL7yBeP/h6/KPaJVUHnTrD5jg+z1ix+c8xq2WnVE/80w9+931JqffKlpzBziTszS2li0su1 AczT9q9gNL8RJv+reX7om4+bzu2dsTvmyQ5XA//Aj2cdl8bfam382OYos7bi+MYbn+r2NYnF +mj82X5OyeScYvCR0u/blFiKMxINtZiLihMBWUqZ6X8CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/fzGrQH56f4E5h_9E0EtrzPxZ0w0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 12:11:59 -0000

Hi,

>>> Section 5.1:
>>>=20
>>> IMO 5000 is a bad choice for the default port value. It falls in the=20
>>> middle of the registered port list. It isn't currently registered (I=20
>>> don't know why) but it potentially could. I suggest that a number=20
>>> outside of the registered port range
>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - t=
he largest possible 16 bit number.
>>=20
>> I have no problem to change the default value.
>>=20
>> However, 5000 was defined before I got involved with the draft, so I thi=
nk it would be good to get some input from Gonzalo and/or Salvatore whether=
 there was some specific reason for 5000.
>>=20
>> -------------
>
> 5000 is the default value the current/available SCTP over TLS are using.

Thanks for the information, Sal!

I guess we in the SCTP-SDP draft could refer to the SCTPoDTLS spec, to clar=
ify where the value comes from.

Regards,

Christer


From nobody Tue Dec  2 04:54:39 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8261A1B2E for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:54:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 hIVi_GJ4APTR for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 04:54:34 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E610F1A1B40 for <mmusic@ietf.org>; Tue,  2 Dec 2014 04:54:33 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-93-547db6879f57
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 04.B9.04076.786BD745; Tue,  2 Dec 2014 13:54:31 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 13:54:31 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: bundle-only attribute with non-zero port value?
Thread-Index: AdAOLuRFHIaCbMzPRi+fiBvvfsNEKQ==
Date: Tue, 2 Dec 2014 12:54:30 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D56E9BF@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D56E9BFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+JvjW77ttoQg13bFS2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujINft7EWXFSs2PWogb2B8Y9MFyMnh4SAiUTn6wtMELaYxIV7 69m6GLk4hASOMEq8eHiHGcJZzCix/dEWxi5GDg42AQuJ7n/aIA0iAuoSX/f2MIPYwgIOEjOu nWKFiLtKrF/ziA3C1pM4uuQoC4jNIqAisXPVBTCbV8BXYvOKTWC9jECLv59aA3YEs4C4xK0n 86EOEpBYsuc8M4QtKvHy8T9WCFtJ4seGSywQ9fkSkxb/hJopKHFy5hOWCYxCs5CMmoWkbBaS Moi4jsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQT IzAmDm75bbWD8eBzx0OMAhyMSjy8Hz7VhAixJpYVV+YeYpTmYFES5114bl6wkEB6Yklqdmpq QWpRfFFpTmrxIUYmDk6pBkZJuQP7baLE3i0rT7k+y6OptUpRa8HWPJHb5nVrUlpfPj77IMw6 2SYpSHL1z3CGpid8Ss1/Vr6OYvgtICbVU/+Glf211o0P2QzaPkHdKvXvzKJObL1Vu/vHhXMc Rws8dfMmPnDz3v3i1cP5zUpBmbc9PJQ6th/e0qPi1Ni9wd63jvXRioBpHUosxRmJhlrMRcWJ ALxd3DRqAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qxcLRJBsYJLFExh32Eu2BPfx4As
Subject: [MMUSIC] BUNDLE: bundle-only attribute with non-zero port value?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 12:54:37 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D56E9BFESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Currently  BUNDLE allows usage of the SDP bundle-only attribute in any offe=
r - even if the associated m- line contains a negotiated BUNDLE address.

As we know, the purpose of the attribute is to ensure that the answerer rej=
ects the associated m- line if the answerer does not support BUNDLE, or if =
the answerer does not keep the m- line within the BUNDLE group.

Once the BUNDLE address have been negotiated, the offerer can ensure the sa=
me thing by assigning the BUNDLE address to an m- line. If the answerer doe=
s not want to keep it within the BUNDLE group, it will reject the m- line (=
per BUNDLE procedures).

So, the question is: is there a need to use the bundle-attribute in m- line=
s with a non-zero port value? It would simply the procedures by specifying =
that the attribute can only be used together with port zero.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D56E9BFESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Currently&nbsp; BUNDLE allows usage of the SDP bundl=
e-only attribute in any offer &#8211; even if the associated m- line contai=
ns a negotiated BUNDLE address.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we know, the purpose of the attribute is to ensur=
e that the answerer rejects the associated m- line if the answerer does not=
 support BUNDLE, or if the answerer does not keep the m- line within the BU=
NDLE group.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Once the BUNDLE address have been negotiated, the of=
ferer can ensure the same thing by assigning the BUNDLE address to an m- li=
ne. If the answerer does not want to keep it within the BUNDLE group, it wi=
ll reject the m- line (per BUNDLE
 procedures).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, the question is: is there a need to use the bund=
le-attribute in m- lines with a non-zero port value? It would simply the pr=
ocedures by specifying that the attribute can only be used together with po=
rt zero.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D56E9BFESESSMB209erics_--


From nobody Tue Dec  2 05:23:11 2014
Return-Path: <salvatore.loreto@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DEF51A8728 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 05:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 q1W7J84NUJV1 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 05:22:53 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D4441A1B49 for <mmusic@ietf.org>; Tue,  2 Dec 2014 05:22:52 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-7a-547dbd2a1df9
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 88.AF.29772.A2DBD745; Tue,  2 Dec 2014 14:22:50 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.148]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 14:22:50 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQAEmAMAAALdvAA=
Date: Tue, 2 Dec 2014 13:22:48 +0000
Message-ID: <63330DF6-9E4D-439B-BF7E-E2A5775111A3@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com>
In-Reply-To: <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <654C712EBECABC4FB8610CD0EF4FF337@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGfG3Rldrb22Iwd/vihZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXxaFkDS0EbZ8WpJb3sDYwz2LsYOTkkBEwk vqz4zQhhi0lcuLeerYuRi0NI4AijxN4d15khnMWMEk93/wSrYhMwk3j+cAsziC0CZF//3MsE YjML+Eq8XPAFLC4sECWxbN0/doiaaIl3fzezQthWEj9bToDZLAIqEo3b3rOB2LwC9hIrjz2D 2tzMKDFxzwKwZk4BB4k9DdfBGhiBzvt+ag3UMnGJW0/mM0GcLSCxZM95ZghbVOLl43+sELaS xIrtlxgh6nUkFuz+xAZhW0s07/jKDGFrSyxb+JoZ4ghBiZMzn7BMYBSfhWTFLCTts5C0z0LS PgtJ+wJG1lWMosWpxUm56UZGeqlFmcnFxfl5enmpJZsYgTF3cMtvgx2ML587HmIU4GBU4uH9 8KkmRIg1say4MvcQozQHi5I478Jz84KFBNITS1KzU1MLUovii0pzUosPMTJxcEo1MLLcLdwf ynKyefHzOROfrd6/ZeJCqY+MOx4fes32fY+i3QvLdbpV0yY9erx84hHmF/lH/GUPa6ZM+m+e Wayv4D9388PV570VmJs7U7MY3v80UyhPCVxtuySZIWC7xXxhw197jLPk/CP2buatvdx48Ucc g3t/iGTkqrknfy+adsK5Scyn5tXHveuUWIozEg21mIuKEwESVGbTmgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZWUqh3gcAyapper3T35t8W8MUtk
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 13:23:01 -0000

On Dec 2, 2014, at 2:00 PM, Salvatore Loreto <salvatore.loreto@ericsson.com=
> wrote:

> Hi there,
>=20
> On Dec 2, 2014, at 10:49 AM, Christer Holmberg <christer.holmberg@ericsso=
n.com> wrote:
>>=20
>>=20
>>> Section 5.1:
>>>=20
>>> IMO 5000 is a bad choice for the default port value. It falls in the mi=
ddle of the registered port list. It isn't currently=20
>>> registered (I don't know why) but it potentially could. I suggest that =
a number outside of the registered port range=20
>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - t=
he largest possible 16 bit number.
>>=20
>> I have no problem to change the default value.
>>=20
>> However, 5000 was defined before I got involved with the draft, so I thi=
nk it would be good to get some input from Gonzalo and/or Salvatore whether=
 there was some specific reason for 5000.
>>=20
>> -------------
>=20
> 5000 is the default value the current/available SCTP over TLS are using.

just to clarify
what I meant is that 5000 is the value that as far as I know Firefox is usi=
ng in its SCTP over TLS data channel implementation

br
Salvatore=


From nobody Tue Dec  2 07:49:20 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE0C1A1BCD for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 07:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 QfVXDOGXx26w for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 07:49:18 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 072CE1A1B06 for <mmusic@ietf.org>; Tue,  2 Dec 2014 07:49:16 -0800 (PST)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-01v.sys.comcast.net with comcast id NfpF1p0052GyhjZ01fpFHP; Tue, 02 Dec 2014 15:49:15 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-09v.sys.comcast.net with comcast id NfpE1p00q3Ge9ey01fpEoM; Tue, 02 Dec 2014 15:49:15 +0000
Message-ID: <547DDF7A.2060309@alum.mit.edu>
Date: Tue, 02 Dec 2014 10:49:14 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D534E7B@ESESSMB209.ericsson.se> <2649C056-4D86-4448-B71F-A42954E1BF49@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D538EF9@ESESSMB209.ericsson.se> <07B6DC62-93DB-4C15-BECE-68BB70B663FB@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D5390C0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63E883@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se> <547CE88C.40605@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56AD9F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D56AD9F@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417535355; bh=XsM2cnvU7nJS/Xr4l/O4Sdq8c6Vnk5xsxI9JNz3/Ir4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ACc6wEzA+e6N8vvskQKPuwphBFj+tdp3feDFSqTLmidpyXATwF0amB8UByzHOyt0n TlwEGmqlwC9PhbPIBDiev7Bv0VepMest/UxaO4rlw3Y9h6ldUnHqmfk62bAjrQYZIf 8zgyXhre8Gh6OVTChhLxqIGifsGucp0nuxYzEQV1ZICCs/iX+ncfiAAgvxyJDZRtVL bV8t6cPlQFtnXwTD3xpCuw0tvRklQAA4JjYn1u9hVbSskVC4DP4XJBq3sZndu2tmjw fWl74qmvXazWP+WBca1gUF6JWeatYMQC5zIFQW8ITPVsuZFuSfPRKsJf7SNS4EVvLZ 1LQmC8JWKTJ1Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/p4mitjvig31lTYdM3TWr2c2T-kg
Subject: Re: [MMUSIC] Single SCTP usage per SDP session?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 15:49:19 -0000

On 12/2/14 3:22 AM, Christer Holmberg wrote:
> Hi,
>
>>>> Per my understanding, draft-ietf-tsvwg-sctp-dtls-encaps just talks about SCTP over DTLS and allowing multiple SCTP associations, which is perfectly fine.
>>>> Then it is possible to come up with SCTP-SDP semantics to use that capability.
>>>> One m= line allowing one SCTP over DTLS limit is fine. Using BUNDLE
>>>> you can replicate same 4-tuple in multiple m= lines. Then there is only one DTLS association established and multiple SCTP associations over that is possible (one per m= line).
>>>> If BUNDLE is not used then I believe same 4-tuple on multiple m=
>>>> lines are NOT possible. This is because, per my understanding, unlike TCP/native-SCTP used under non- ICE environments, in ICE-environments the TCP/UDP port specified is used both as client and server port for DTLS.
>>>
>>> Even with BUNDLE, you would have to use the same m= line port value from the beginning, which is not allowed. So, you basically would have to add the additional SCTPoDTLS m= lines once the usage of BUNDLE has been negotiated.
>>
>> bundle-only would allow you to set this up.
>
> Correct.
>
> But, then we would need to have rules saying that you are not allowed to move an m= line associated with a SCTP usage out of the BUNDLE group, etc.

How is this different from any other bundle-only m-line?


From nobody Tue Dec  2 08:02:40 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4262D1A1BE4 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 i3o2DG25bZ7v for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:02:37 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29FA1A1BD2 for <mmusic@ietf.org>; Tue,  2 Dec 2014 08:02:35 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-11v.sys.comcast.net with comcast id Ng021p0022Bo0NV01g2ab7; Tue, 02 Dec 2014 16:02:34 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-05v.sys.comcast.net with comcast id Ng2a1p00B3Ge9ey01g2afN; Tue, 02 Dec 2014 16:02:34 +0000
Message-ID: <547DE29A.4030706@alum.mit.edu>
Date: Tue, 02 Dec 2014 11:02:34 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Salvatore Loreto <salvatore.loreto@ericsson.com>,  Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <706F76AF-34B5-4E7F-9992-ECDFC972602B@ericsson.com> <63330DF6-9E4D-439B-BF7E-E2A5775111A3@ericsson.com>
In-Reply-To: <63330DF6-9E4D-439B-BF7E-E2A5775111A3@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417536154; bh=8E+9Ll/imEYpWIMSanpdUjPWC0yKdtaYhNWBrL/3gnk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=XF6rSw72XpqcmLAagy8eSaOLClVNVF+mmD4F1l8PidSQZcouHzdQVW23/eP3flgsZ WlgeYCQ61JQ4PrRiqWIpiOPiGv3ixIggWKwJQo724hfcBwPY/Wo7D+dnP83BoJRJyE fvgASeLWZXYx8cE7233kCphZMUtUkzySS2z7dN1i9NFZk237hNVML7Tq+obXujuwaD CFsyYQhhNkaNmdOQkfH0Gj41ZbRJbe3oEq/2TRpcfPMg44A9zVVfDu1ruzqdzoVfRt i/RKgbsPDLcw0Vj5ETOHjvnDRiIhY4uDwYUK3k+gsE4HUHxnKVL3czZ+wi30weJ++i Fndaqd1ZdQ6Wg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/EO-L4-AKDKei2jIPk152YpAV9io
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:02:38 -0000

On 12/2/14 8:22 AM, Salvatore Loreto wrote:
>
> On Dec 2, 2014, at 2:00 PM, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote:
>
>> Hi there,
>>
>> On Dec 2, 2014, at 10:49 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>>>
>>>
>>>> Section 5.1:
>>>>
>>>> IMO 5000 is a bad choice for the default port value. It falls in the middle of the registered port list. It isn't currently
>>>> registered (I don't know why) but it potentially could. I suggest that a number outside of the registered port range
>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>>>
>>> I have no problem to change the default value.
>>>
>>> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>>>
>>> -------------
>>
>> 5000 is the default value the current/available SCTP over TLS are using.
>
> just to clarify
> what I meant is that 5000 is the value that as far as I know Firefox is using in its SCTP over TLS data channel implementation

AFAIK it is being explicitly specified as 5000, not that there is 
reliance on a default value of 5000. Changing the default only affects 
those implementations depending on the default.

Also, if those implementations are using different SDP syntax, not 
conformant with this version of the draft, then they will need to be 
changed anyway before this change becomes effective.

	Thanks,
	Paul


From nobody Tue Dec  2 08:15:11 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 294DB1A1EE8 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, SPF_SOFTFAIL=0.665] 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 gbGxtwPHft-n for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:15:08 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B415D1A1EEE for <mmusic@ietf.org>; Tue,  2 Dec 2014 08:15:06 -0800 (PST)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-08v.sys.comcast.net with comcast id NgEp1p0022PT3Qt01gF5N7; Tue, 02 Dec 2014 16:15:05 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-14v.sys.comcast.net with comcast id NgF51p00K3Ge9ey01gF5al; Tue, 02 Dec 2014 16:15:05 +0000
Message-ID: <547DE589.7010108@alum.mit.edu>
Date: Tue, 02 Dec 2014 11:15:05 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417536905; bh=QbPc3zsFKBA7pV8ArbHIXh/drXfcAyhgUMX7kcSsV2c=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ODSypUwYOmYjCyyK+3Ctt28zyZFM1tzGQg9Ectt6ldFMJ87EHqqRfIbulij5aBNwm QC4pcAlKp/atHyi0k7ilAI60mFqMz4XUw23A3EV6PizuiNfXgqrQ1FHsDvy+dv74dW 4NaJ4znEUwfddn3crirujzOCs46piNpdQIJxJ+m5HTdpi+3N7gKpv3WCQMJi1SBP29 czWtJOAQNF++dtxFMVK8Ua6+b1QfjFXwNxvRpC7A4QSGmzsm+DIZ5jI9wFGfpG0OF+ q9ltuDE1Xb3WWLFQqZmfqvsLytKgIomuR/deAQFul57HzP/XClOSukTyHnXYREmYOV RBjrZ6T+pK7nw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5030Vv71fUqiSf58tDIYtJmc3jM
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:15:09 -0000

On 12/2/14 3:49 AM, Christer Holmberg wrote:
> Hi Paul,
>
> Thanks for your comments! Reply inline.
>
>> Section 4.3:
>>
>> Using MIME subtypes on the m-line doesn't really work well. The value doesn't really define a data format - it defines a discipline for choosing and using stream
>> ids, and possibly a format for each one. I think that all of the first paragraph should be deleted, with the exception of the first sentence.
>
> I can do that, if no one else have an issue doing so.
>
> -------------
>
>> Section 5.1:
>>
>> IMO 5000 is a bad choice for the default port value. It falls in the middle of the registered port list. It isn't currently
>> registered (I don't know why) but it potentially could. I suggest that a number outside of the registered port range
>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>
> I have no problem to change the default value.
>
> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>
> -------------
>
>> Section 6.2:
>>
>> I don't understand why sctpmap-attr is defined, since it isn't referenced anywhere. I think it is a holdover from when there was an sctpmap attribute.
>
> Correct, that is a mistake.
>
> The purpose of Section 6.2 is to define the format of the SDM fmtp attribute when used with SCTP.
>
>> It seems that what is being done here is to define the syntax of a=fmtp for all fmt values that might be used with sctp. I don't think that is kosher.
>> I think fmtp needs to be defined for webrtc-datachannel, and again for each other application-usage that wants to use it.
>>
>> It is unpleasant to expect all application-usages to do this. But the alternative is to go back to defining a special attribute for max-message-size. Perhaps:
>>
>>       Attribute name: sctp-attr
>>       Attribute value: sctp-attr-value
>>       Attribute Syntax:
>>
>>       sctp-attr-value = association-usage [max-message-size]
>>       max-message-size  =  "max-message-size" EQUALS 1*DIGIT
>
> If we decide to have a special attribute, why not simply call it "a=max-message-size"?
>
> We only allow a single association-usage per m- line, so there is no need to explicitly map the fmt value to a specific sctp-attr attribute.
>
>        Attribute name: sctp-max-message-size	(We can use a shorter name)
>        Attribute value: max-message-size
>        Attribute Syntax:
>
>        sctp-max-message-size = max-message-size
>        max-message-size  =  1*DIGIT

That would work too, if we expect that there will only ever be the one 
sctp-association-wide property to specify.

> -------------
>
>> Section 8:
>>
>> I think something probably needs to be said about sendonly/recvonly/inactive. I'm not sure what. Maybe they shouldn't be used at all. Or maybe they can make some sort of sense.
>
> I was thinking about the same thing, but left it out of this version on purpose (I should have added an open issue regarding it, though).
>
> I see no reason why we couldn't use sendonly/recvonly/inactive also for SCTP - assuming it only impacts what is sent on the SCTP association. I.e. it would not impact the DTLS connection, and whatever (UDP or TCP) is below DTLS.

My question is: what does it mean? (Given that there are multiple 
streams, and from an SCTP perspective the streams are unidirectional.) 
Some issues:

- If someone is using channels, and the protocol over a channel requires 
ACKs, is it restricted to sendrecv?

- Does it make sense to change the directionality of all the channels in 
parallel?

Also, there is the option of using the direction attributes on a 
per-channel basis via a=dcsa.

Maybe it makes the most sense, for now at least, to specify that the 
directionality attributes have no defined meaning in conjunction with an 
SCTP association.

> -------------
>
>> Section 9:
>>
>> The NOTE seems inadequate. If SCTP is being used in an environment that does gating based on SDP, then multihoming probably won't work. None of the negotiated alternative addresses will get their gates opened. So maybe more needs to be said about this.
>
> So, you don't think the existing text is wrong - you just think we need more text, right?

Right.

> -------------
>
>> Section 10.1:
>>
>> The last paragraph about NATs references RFC6951. Wouldn't it be clearer if it simply referenced DTLS/SCTP defined in this draft?
>
> I can look into that.
>
> -------------
>
>> Section 10.2:
>>
>> This isn't quite true is it? ICE is defined to work over DTLS/SCTP.
>>
>> While the emphasis is on those cases where the SCTP is bundled with SRTP, it should work just fine without bundle.
>
> Ok, I guess the text should be more clear, and talk about "pure" SCTP and SCTP/DTLS.

	Thanks,
	Paul


From nobody Tue Dec  2 08:31:03 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83CF21A1C06 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:31:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 BjiGqHuNYCPH for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:30:58 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD2721A1BF9 for <mmusic@ietf.org>; Tue,  2 Dec 2014 08:30:49 -0800 (PST)
Received: from us70tusmtp1.zam.alcatel-lucent.com (unknown [135.5.2.63]) by Websense Email Security Gateway with ESMTPS id 4B81115930EE0 for <mmusic@ietf.org>; Tue,  2 Dec 2014 16:30:45 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id sB2GUkFO023649 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Tue, 2 Dec 2014 11:30:46 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 11:30:46 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
Thread-Index: AdAOOh4XGrrUYNLGRo+3IKnmkB+//Q==
Date: Tue, 2 Dec 2014 16:30:45 +0000
Deferred-Delivery: Tue, 2 Dec 2014 16:30:00 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E648763@US70UWXCHMBA02.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/SCiW34pXVtY7-sYJJZBOBDIxQRM
Subject: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:31:00 -0000

Section 5.1.1.3 says "subprotocol" is a mandatory parameter.
However, "5.1.  DATA_CHANNEL_OPEN Message" of draft-ietf-rtcweb-data-protoc=
ol (DCEP) says the subprotocol can be empty (i.e. unspecified).

We also foresee draft-ejzak-mmusic-data-channel-sdpneg to be used for cases=
 where stream id is negotiated while subprotocol is unspecified.

To align it with DCEP and to allow the above use case, we want to make the =
subprotocol optional in dcmap.
Existing text in 5.1.1.3=20
"Subprotocol is a mandatory parameter."
will be changed to
"Subprotocol is a an optional parameter. If the subprotocol parameter is no=
t present, then its value defaults to empty string"

Please let us know if you have any objections to this.

Thanks
Raju


From nobody Tue Dec  2 08:48:59 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DC71A1F04 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 b2ZQgtE8V94c for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:48:51 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F0A81A1EEE for <mmusic@ietf.org>; Tue,  2 Dec 2014 08:48:43 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-ea-547ded694f60
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id F9.AF.29772.96DED745; Tue,  2 Dec 2014 17:48:41 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 17:48:41 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Single SCTP usage per SDP session?
Thread-Index: AdAIiilGRQ9HT1LDRYu/Q2dfZ4TTzAAxes8AAAUE9XD///IzAP//5OAwgABrp4D//7ZsQIAIlnMA//9GRRAAPAMdAP//35IA
Date: Tue, 2 Dec 2014 16:48:40 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D570172@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D534E7B@ESESSMB209.ericsson.se> <2649C056-4D86-4448-B71F-A42954E1BF49@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D538EF9@ESESSMB209.ericsson.se> <07B6DC62-93DB-4C15-BECE-68BB70B663FB@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D5390C0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63E883@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se> <547CE88C.40605@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56AD9F@ESESSMB209.ericsson.se> <547DDF7A.2060309@alum.mit.edu>
In-Reply-To: <547DDF7A.2060309@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+JvjW7m29oQg0tTNC2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj96c9zAVNvBUzP19maWDcztXFyMkhIWAi cetZIzuELSZx4d56ti5GLg4hgSOMEo0T/zNBOIsZJa5e28faxcjBwSZgIdH9TxukQUTAV+LZ 49tsILYwUHjernZmiLilxJxP75lBykUE8iT+zZUCCbMIqEg0/e9jAbF5gVr/Lutjhxh/j0Xi 0sOPYOM5BXQkJm0qA6lhBLrn+6k1TCA2s4C4xK0n85kg7hSQWLLnPDOELSrx8vE/VghbSaJx yRNWiHodiQW7P7FB2NoSyxa+ZobYKyhxcuYTlgmMorOQjJ2FpGUWkpZZSFoWMLKsYhQtTi1O yk03MtJLLcpMLi7Oz9PLSy3ZxAiMkoNbfhvsYHz53PEQowAHoxIP74dPNSFCrIllxZW5hxil OViUxHkXnpsXLCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoFRxl02KP3iefHZlznft87YKlqb uXbb9klM91nvL/uh8fcDX4fs8fWuPU8mZinP+nmk3sD0CE/pr9ZyZ+eDC/kcSg/X33ioFujr oXdW7YNYYs6zss6nS56YyB77otV/d9IO+QVPEoMybn7i195z/Zff+4LiV1Xqu6IkzJcle02f ezU1Zs/uALcSJZbijERDLeai4kQAwNUoGHMCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6wcovrIo6EjQHZUEEzn7TLRTTMs
Subject: Re: [MMUSIC] Single SCTP usage per SDP session?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:48:55 -0000

Hi,

>>>>> Per my understanding, draft-ietf-tsvwg-sctp-dtls-encaps just talks ab=
out SCTP over DTLS and allowing multiple SCTP associations, which is perfec=
tly fine.
>>>>> Then it is possible to come up with SCTP-SDP semantics to use that ca=
pability.
>>>>> One m=3D line allowing one SCTP over DTLS limit is fine. Using BUNDLE=
=20
>>>>> you can replicate same 4-tuple in multiple m=3D lines. Then there is =
only one DTLS association established and multiple SCTP associations over t=
hat is possible (one per >>>>> m=3D line).
>>>>> If BUNDLE is not used then I believe same 4-tuple on multiple m=3D=20
>>>>> lines are NOT possible. This is because, per my understanding, unlike=
 TCP/native-SCTP used under non- ICE=20
>>>>> environments, in ICE-environments the TCP/UDP port specified is used =
both as client and server port for DTLS.
>>>>
>>>> Even with BUNDLE, you would have to use the same m=3D line port value =
from the beginning, which is not allowed. So, you basically would have to a=
dd the additional >>>> SCTPoDTLS m=3D lines once the usage of BUNDLE has be=
en negotiated.
>>>
>>> bundle-only would allow you to set this up.
>>
>> Correct.
>>
>> But, then we would need to have rules saying that you are not allowed to=
 move an m=3D line associated with a SCTP usage out of the BUNDLE group, et=
c.
>
> How is this different from any other bundle-only m-line?

bundle-only is used to ensure that an m- line is only accepted by the answe=
rer if accepted into a BUNDLE group. Currently nothing prevents the offerer=
 to, in a later offer, move that m- line out of that BUNDLE group.

Regards,

Christer


From nobody Tue Dec  2 08:54:17 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D051A1EF1 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VQuUt_ILb3ti for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 08:54:14 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94E101A1EEE for <mmusic@ietf.org>; Tue,  2 Dec 2014 08:54:13 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-00-547deeb3c308
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id F0.EE.04076.3BEED745; Tue,  2 Dec 2014 17:54:11 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 17:54:10 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
Thread-Index: AdAOOh4XGrrUYNLGRo+3IKnmkB+//QAFlBLg
Date: Tue, 2 Dec 2014 16:54:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5701B9@ESESSMB209.ericsson.se>
References: <E1FE4C082A89A246A11D7F32A95A17828E648763@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E648763@US70UWXCHMBA02.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM+Jvje7md7UhBgcvGFtMXf6YxaJh4xVW ByaP1md7WT2WLPnJFMAUxWWTkpqTWZZapG+XwJXxsmEPc8EEropfP5czNjBu5ehi5OSQEDCR +PTiGBuELSZx4d56MFtI4AijxMubel2MXED2YkaJ85uusnQxcnCwCVhIdP/TBqkREciR+H3r PSuILSwQLbG5qY8NpEREIEZi7YQaCNNI4ugVQxCTRUBF4lK7IUgxr4CvxM4/t1ghFsVIvF/7 gRHE5hSIlejZM4UJxGYEOub7qTVgNrOAuMStJ/OZII4UkFiy5zwzhC0q8fLxP1YIW0micckT Voh6HYkFuz+xQdjaEssWvmaG2CsocXLmE5YJjKKzkIydhaRlFpKWWUhaFjCyrGIULU4tLs5N NzLSSy3KTC4uzs/Ty0st2cQIjI+DW35b7WA8+NzxEKMAB6MSD++HTzUhQqyJZcWVuYcYpTlY lMR5F56bFywkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBUe8smyBXbbTop1mZe+ZmHXjiNmm6 guhtnX0Cuw/GBXN992Tbn27Rl6kuJsgt7H7VQ1Z9zcFdsoZvZ4Uc2bvpmVun0xrlri72Tal6 vKLNZnfqhGYfP6a4T2/OT8EJRS+s5dZbTzJRMvjFoa7CYLzE/n74jmaulYoKa3s/r18et5nH KvDybds5SizFGYmGWsxFxYkAVEljYnACAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/QjKI-w8JsuoIHjghJ1ot9v6-QRw
Subject: Re: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol" optional in dcmap
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 16:54:15 -0000

Hi,

If "subprotocol" is optional in DCEP then I think it should be optional als=
o in draft-sdpneg.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Makaraju, Maridi=
 Raju (Raju)
Sent: 02 December 2014 18:31
To: mmusic@ietf.org
Subject: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: make "subprotocol=
" optional in dcmap

Section 5.1.1.3 says "subprotocol" is a mandatory parameter.
However, "5.1.  DATA_CHANNEL_OPEN Message" of draft-ietf-rtcweb-data-protoc=
ol (DCEP) says the subprotocol can be empty (i.e. unspecified).

We also foresee draft-ejzak-mmusic-data-channel-sdpneg to be used for cases=
 where stream id is negotiated while subprotocol is unspecified.

To align it with DCEP and to allow the above use case, we want to make the =
subprotocol optional in dcmap.
Existing text in 5.1.1.3=20
"Subprotocol is a mandatory parameter."
will be changed to
"Subprotocol is a an optional parameter. If the subprotocol parameter is no=
t present, then its value defaults to empty string"

Please let us know if you have any objections to this.

Thanks
Raju

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Dec  2 09:07:41 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E35C61A1C06 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.565
X-Spam-Level: 
X-Spam-Status: No, score=0.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] 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 sWN-9d_Sa6tE for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:07:31 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA9CC1A1BD4 for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:07:31 -0800 (PST)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-08v.sys.comcast.net with comcast id Nh6D1p0042Udklx01h7W8z; Tue, 02 Dec 2014 17:07:30 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-18v.sys.comcast.net with comcast id Nh7W1p00B3Ge9ey01h7WnH; Tue, 02 Dec 2014 17:07:30 +0000
Message-ID: <547DF1D2.6060908@alum.mit.edu>
Date: Tue, 02 Dec 2014 12:07:30 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se> <547CD27A.3090006@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417540050; bh=Zk7xY25kyUqiJN+3MLbl0NjzJL+rIc1AAFlHJhfVDfY=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Wer2KvFvxvJqIVtdBPZirNWJeAfixVTDH3EQBM0coiTk0+tIXDKnEM1AjWwCRRutx omwzbgMoB5NGHK3N1yd1/GH7VtaPrzEtnp+W9m7mzj41EggMxfAyXk/ZRGvE2Vnh7z 40jsQSBLEFMVzybt/ygZiABRCqG0YafN8xmI/cs0nEh4NC6XxtrCuRaCnEJdBYPo9d tQ02t7yn+XQmzLhuly9gzrTljWQYKaIG9hK2u7+ltwReHpTzo8HUisV5ilJvSvQsh9 U8G6B53T+VWt4z/oBd6ERK7w+mw6FDwvRn1P6n7olYve7KE5ngMFHkIqIzDKGBsqxe AGiOUpa/WV/wg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/n2izjnQ4z-S_XJiJ-wbCbWeSRrc
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:07:39 -0000

On 12/2/14 3:56 AM, Christer Holmberg wrote:

>>> For 'DTLS/SCTP', there are some decisions to make:
>>>
>>> -If the transport layer protocol is UDP, I assume a 'new' value will
>>> not automatically re-establish the DTLS connection - only the SCTP
>>> association will be re-established.
>>
>> Why?
>>
>> If some part of the 5-tuple changes then it will be *necessary* to establish a new DTLS connection.
>
> Correct - I should have clarified that I am talking about the case there the 5-tuple does not change.
>
>> Even if the 5-tuple doesn't change, aren't there going to be cases where you want to reestablish the DTLS?
>
> Maybe there are. But, this is related to the question whether you need to signal that in SDP.

If the fingerprint changes, then doesn't the DTLS need to be 
renegotiated? (Regardless of whether 'new' is specified.)

>>> -However, if the transport layer protocol is TCP, does that mean that
>>> a 'new' value will mean that BOTH the TCP connection, AND the SCTP
>>> association, will be re-established? IF the TCP connection is also
>>> re-established, then I guess the DTLS connection will be re-established.
>>
>> There are all consequences of using the same atttribute to control independent behavior at two different layers of the protocol stack.
>
> Yes.
>
>> The *right* fix would be to have one attribute for the DTLS behavior and another for the SCTP behavior.
>
> We could for sure define an SDP "sctp-setup" attribute, IF people see a need for it.

ISTM the issue is about there being multiple *layers* that are being 
negotiated, rather than specifically what protocol those layers are.

So the only time you need to specify this is when there is ambiguity 
about which layer it might be.

Perhaps we could define an extension to a=setup and a=connection. E.g.

          setup-attr           =  "a=setup:" role [ " " proto]
          role                 =  "active" / "passive" / "actpass"
                                  / "holdconn"

(where proto is as defined in SDP). When absent it would default to the 
entire proto field from the m-line. Other valid values would be prefixes 
of the proto in the m-line. So, for the case at hand, we could have
	m=application 12345 DTLS/SCTP webrtc-datachannel
	a=setup:active DTLS/SCTP
	a=setup:passive DTLS

That would be entirely equivalent to:

	m=application 12345 DTLS/SCTP webrtc-datachannel
	a=setup:active
	a=setup:passive DTLS

And in general we could have:

	m=foo 12345 A/B/C/D fmt1 fmt2 ...
	a=setup:<direction> A/B/C/D
	a=setup:<direction> A/B/C
	a=setup:<direction> A/B
	a=setup:<direction> A

And do the same thing for a=connection.

	Thanks,
	Paul


From nobody Tue Dec  2 09:09:59 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B4D1A6EF1 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 SwFWjKe32Vvr for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:09:36 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01B641A1EFE for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:09:35 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-6b-547df24c1dfd
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id AD.43.24955.C42FD745; Tue,  2 Dec 2014 18:09:33 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 18:09:32 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQANeciAAAN2uiA=
Date: Tue, 2 Dec 2014 17:09:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu>
In-Reply-To: <547DE589.7010108@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+Jvja7vp9oQg72nBS2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj9epfTAVr5SoWnV/M3sD4XLyLkZNDQsBE 4sCVBWwQtpjEhXvrgWwuDiGBI4wSKyatZYdwFjNKPPxziLmLkYODTcBCovufNkiDiICvxLPH t8GahQWiJE7u7WaFiEdLvPu7mRWkXETASmLJhniQMIuAisScpu9gYV6g1g9bo0DCQgL5EnOn HGcEsTkFdCTmrP3DAmIzAp3z/dQaJhCbWUBc4taT+UwQZwpILNlznhnCFpV4+fgfK4StJNG4 5AkrRL2OxILdn9ggbG2JZQtfg9XzCghKnJz5hGUCo+gsJGNnIWmZhaRlFpKWBYwsqxhFi1OL k3LTjYz1Uosyk4uL8/P08lJLNjECY+Tglt+qOxgvv3E8xCjAwajEw/vhU02IEGtiWXFl7iFG aQ4WJXHehefmBQsJpCeWpGanphakFsUXleakFh9iZOLglGpgLPlic1Hf9v96j91zI/6fZZqy 9rCiYMrz/yVhM3zq3n9+K/F0o6/qjaN/PRa/0Dmzav9B1tBt2/LaTUKX9X6+wHN3sdnhdHON o0mCRxUn5LAv+x4sbHvfNXnCi+ObO+4l9DTmR+7fbKrxbeW2fb+mh4i5PxBY3O57beY7l11H H3TaOu8xyKyPuKDEUpyRaKjFXFScCABPgQlPcgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2CluJ1DmjisvfgdKWXCLfToFoqY
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:09:43 -0000

Hi,

>>> Section 6.2:
>>>
>>> I don't understand why sctpmap-attr is defined, since it isn't referenc=
ed anywhere. I think it is a holdover from when there was an sctpmap attrib=
ute.
>>
>> Correct, that is a mistake.
>>
>> The purpose of Section 6.2 is to define the format of the SDM fmtp attri=
bute when used with SCTP.
>>
>>> It seems that what is being done here is to define the syntax of a=3Dfm=
tp for all fmt values that might be used with sctp. I don't think that is k=
osher.
>>> I think fmtp needs to be defined for webrtc-datachannel, and again for =
each other application-usage that wants to use it.
>>>
>>> It is unpleasant to expect all application-usages to do this. But the a=
lternative is to go back to defining a special attribute for max-message-si=
ze. Perhaps:
>>>
>>>       Attribute name: sctp-attr
>>>       Attribute value: sctp-attr-value
>>>       Attribute Syntax:
>>>
>>>       sctp-attr-value =3D association-usage [max-message-size]
>>>       max-message-size  =3D  "max-message-size" EQUALS 1*DIGIT
>>
>> If we decide to have a special attribute, why not simply call it "a=3Dma=
x-message-size"?
>>
>> We only allow a single association-usage per m- line, so there is no nee=
d to explicitly map the fmt value to a specific sctp-attr attribute.
>>
>>        Attribute name: sctp-max-message-size	(We can use a shorter name)
>>        Attribute value: max-message-size
>>        Attribute Syntax:
>>
>>        sctp-max-message-size =3D max-message-size
>>        max-message-size  =3D  1*DIGIT
>
> That would work too, if we expect that there will only ever be the one sc=
tp-association-wide property to specify.

Well, if we want to specify max message size e.g. per SCTP stream, then we'=
d need something else. But, I don't think anyone has asked for that?

-------------

>>> Section 8:
>>>
>>> I think something probably needs to be said about sendonly/recvonly/ina=
ctive. I'm not sure what. Maybe
>>> they shouldn't be used at all. Or maybe they can make some sort of sens=
e.
>>
>> I was thinking about the same thing, but left it out of this version on =
purpose (I should have added an open issue regarding it, though).
>>
>> I see no reason why we couldn't use sendonly/recvonly/inactive also for =
SCTP - assuming it only impacts=20
>> what is sent on the SCTP association. I.e. it would not impact the DTLS =
connection, and whatever (UDP or TCP) is below DTLS.
>
> My question is: what does it mean? (Given that there are multiple streams=
, and from an SCTP perspective the streams are unidirectional.) Some issues=
:
>
> - If someone is using channels, and the protocol over a channel requires =
ACKs, is it restricted to sendrecv?
>
> - Does it make sense to change the directionality of all the channels in =
parallel?

Well, it depends on for what you are using the SCTP association.

For example, if you would send RTP over SCTP, I guess you could use sendonl=
y/recvonly in the same way as you do for UDP.

If you implement data channels, then sendonly/recvonly would probably cause=
 problem in most cases. It's similar to the case where consent to send expi=
res in one direction :)

> Also, there is the option of using the direction attributes on a per-chan=
nel basis via a=3Ddcsa.

I think such direction would have to be a subset of the SCTP association wi=
de value.=20

> Maybe it makes the most sense, for now at least, to specify that the dire=
ctionality attributes have no defined meaning in conjunction with an SCTP a=
ssociation.

What if someone wants to use SCTP with preconditions?

Alternatively, we recommend against using non-sendrecv, unless one is absol=
utely sure it won't cause problems.

IF used, it applies to the whole SCTP association, including all SCTP stres=
ms etc.

Regards,

Christer


From nobody Tue Dec  2 09:14:07 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F24F1A6EFC for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:13:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 yEfqvukn3ZDb for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:13:56 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA5671A06E9 for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:13:55 -0800 (PST)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-11v.sys.comcast.net with comcast id NhDJ1p0042Qkjl901hDvRy; Tue, 02 Dec 2014 17:13:55 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-15v.sys.comcast.net with comcast id NhDu1p00H3Ge9ey01hDu6S; Tue, 02 Dec 2014 17:13:55 +0000
Message-ID: <547DF352.8070601@alum.mit.edu>
Date: Tue, 02 Dec 2014 12:13:54 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D534E7B@ESESSMB209.ericsson.se> <2649C056-4D86-4448-B71F-A42954E1BF49@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D538EF9@ESESSMB209.ericsson.se> <07B6DC62-93DB-4C15-BECE-68BB70B663FB@ericsson.com> <7594FB04B1934943A5C02806D1A2204B1D5390C0@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E63E883@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D539F4F@ESESSMB209.ericsson.se> <547CE88C.40605@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56AD9F@ESESSMB209.ericsson.se> <547DDF7A.2060309@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D570172@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D570172@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417540435; bh=mZMYLSarw01UAG5lpVAbKU10W6+anj0D56NPs2pbjgA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=nWI1bNNcpMf+xzU8nKSKw3OjWV2qVo1Yq8gyu+rFL3KumYA3gzOvE/sknLnSVjEky tAaNoQrUjcedLMcbjQAPN4YPc00WM4QXx5ZtC+7RVJ1c9a12zJDv+wU687WXpmR8Hz TEcKf8KIfu5J1cCZ/ZLyt3KidpMkdG+0N//ums+6lfYOnJ7bHKpEg9XlLWf5IMkjGq TqqS4CddSN9Y3g1PqXAyJBeU6NDbWI3f3k+5pndfKUuG60JyWocEC/gfZFuvdo3pKF 0gwKPGiZBqHL/+0q5D6E6LGRQxD2xAkOEy/AtJvacDM9HVUSC//Hxo4YLvaIOt7k4O P2Z3/fcTv1sQQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7lAIpNtqcvkXjxknPAJ82MkDq9s
Subject: Re: [MMUSIC] Single SCTP usage per SDP session?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:13:57 -0000

On 12/2/14 11:48 AM, Christer Holmberg wrote:
> Hi,
>
>>>>>> Per my understanding, draft-ietf-tsvwg-sctp-dtls-encaps just talks about SCTP over DTLS and allowing multiple SCTP associations, which is perfectly fine.
>>>>>> Then it is possible to come up with SCTP-SDP semantics to use that capability.
>>>>>> One m= line allowing one SCTP over DTLS limit is fine. Using BUNDLE
>>>>>> you can replicate same 4-tuple in multiple m= lines. Then there is only one DTLS association established and multiple SCTP associations over that is possible (one per >>>>> m= line).
>>>>>> If BUNDLE is not used then I believe same 4-tuple on multiple m=
>>>>>> lines are NOT possible. This is because, per my understanding, unlike TCP/native-SCTP used under non- ICE
>>>>>> environments, in ICE-environments the TCP/UDP port specified is used both as client and server port for DTLS.
>>>>>
>>>>> Even with BUNDLE, you would have to use the same m= line port value from the beginning, which is not allowed. So, you basically would have to add the additional >>>> SCTPoDTLS m= lines once the usage of BUNDLE has been negotiated.
>>>>
>>>> bundle-only would allow you to set this up.
>>>
>>> Correct.
>>>
>>> But, then we would need to have rules saying that you are not allowed to move an m= line associated with a SCTP usage out of the BUNDLE group, etc.
>>
>> How is this different from any other bundle-only m-line?
>
> bundle-only is used to ensure that an m- line is only accepted by the answerer if accepted into a BUNDLE group. Currently nothing prevents the offerer to, in a later offer, move that m- line out of that BUNDLE group.

And that is no different here. If you bundled multiple SCTP 
associations, each on a separate SCTP port, then you can take them out 
of the bundle, each on its own addr/udp-port.

If you want to take more than one out, you can put each on its own udp 
port, or you could group them together in a second (new) bundle, again 
using bundle-only for all but the first in that bundle.

This is very similar to the situation with RTP, except that you must use 
bundle-only when there is more than one in a bundle.

	Thanks,
	Paul


From nobody Tue Dec  2 09:23:51 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0671A6FB2 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:23:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 bdFhjNPEsQTu for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:23:40 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146E11ACE11 for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:23:12 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-1c-547df57ef472
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F3.2D.04231.E75FD745; Tue,  2 Dec 2014 18:23:11 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 18:23:10 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
Thread-Index: AdAKgkYeRp59/KWiSPW7X4BmEjVKXwDHIeIAABubemAADzXRAAACaWUA
Date: Tue, 2 Dec 2014 17:23:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5702F5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se> <547CD27A.3090006@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se> <547DF1D2.6060908@alum.mit.edu>
In-Reply-To: <547DF1D2.6060908@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyM+JvjW7919oQg7WL+CymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj1+Q9LAVXpSqezZ7F2MD4UqSLkZNDQsBE 4vi8LewQtpjEhXvr2boYuTiEBI4wSrw5fJoFwlnMKPGr5z9rFyMHB5uAhUT3P22QBhEBX4ln j2+zgdjCAu4S6/fvZYWIe0gcnDsFynaTWLD2KguIzSKgInH452kwmxeo92/7N1aI+VcZJe7t ewyW4BTQkdh34BwTiM0IdNH3U2vAbGYBcYlbT+YzQVwqILFkz3lmCFtU4uXjf6wQtpJE45In rBD1OhILdn9ig7C1JZYtfM0MsVhQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcUoWpxaXJyb bmSsl1qUmVxcnJ+nl5dasokRGCkHt/zW3cG4+rXjIUYBDkYlHt6Pn2pChFgTy4orcw8xSnOw KInzLjo3L1hIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD44LHi7ecETjzf57DqqTHqwLtenye /nZktj/LN6V3w1WxtpWzBA0jlLwfvNl796CaSXjHb24xEVvnuVy9id/tYmZtU/FWaqh7G5Ty +wJnhDjX3Oa29nuLl5ixPl2vc6o8YvHJxEmPO0N4Zx2O8bk7OTjuBZuB+TOBfT9P6Za5nczX P7lf7KNIvRJLcUaioRZzUXEiAJ1Ptvl1AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/LVyV-5i9Nmf0kNi-s2qmcLGKxyg
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:23:47 -0000

Hi,

>>>> For 'DTLS/SCTP', there are some decisions to make:
>>>>
>>>> -If the transport layer protocol is UDP, I assume a 'new' value will=20
>>>> not automatically re-establish the DTLS connection - only the SCTP=20
>>>> association will be re-established.
>>>
>>> Why?
>>>
>>> If some part of the 5-tuple changes then it will be *necessary* to esta=
blish a new DTLS connection.
>>
>> Correct - I should have clarified that I am talking about the case there=
 the 5-tuple does not change.
>>
>>> Even if the 5-tuple doesn't change, aren't there going to be cases wher=
e you want to reestablish the DTLS?
>>
>> Maybe there are. But, this is related to the question whether you need t=
o signal that in SDP.
>
> If the fingerprint changes, then doesn't the DTLS need to be renegotiated=
? (Regardless of whether 'new' is specified.)
>
>>>> -However, if the transport layer protocol is TCP, does that mean=20
>>>> that a 'new' value will mean that BOTH the TCP connection, AND the=20
>>>> SCTP association, will be re-established? IF the TCP connection is=20
>>>> also re-established, then I guess the DTLS connection will be re-estab=
lished.
>>>
>>> There are all consequences of using the same atttribute to control inde=
pendent behavior at two different layers of the protocol stack.
>>
>> Yes.
>>
>>> The *right* fix would be to have one attribute for the DTLS behavior an=
d another for the SCTP behavior.
>>
>> We could for sure define an SDP "sctp-setup" attribute, IF people see a =
need for it.
>
> ISTM the issue is about there being multiple *layers* that are being nego=
tiated, rather than specifically what protocol those layers are.
>
> So the only time you need to specify this is when there is ambiguity abou=
t which layer it might be.
>
> Perhaps we could define an extension to a=3Dsetup and a=3Dconnection. E.g=
.
>
>          setup-attr           =3D  "a=3Dsetup:" role [ " " proto]
>          role                 =3D  "active" / "passive" / "actpass"
>                                  / "holdconn"
>
> (where proto is as defined in SDP).=20

That would assume that the protocol you want to control is actually explici=
tly part of the SDP proto field value.

> When absent it would default to the entire proto field from the m-line. O=
ther valid values would be prefixes of the proto in the m-line.=20
> So, for the case at hand, we could have
>	m=3Dapplication 12345 DTLS/SCTP webrtc-datachannel
>	a=3Dsetup:active DTLS/SCTP
>	a=3Dsetup:passive DTLS
>
> That would be entirely equivalent to:
>
>	m=3Dapplication 12345 DTLS/SCTP webrtc-datachannel
>	a=3Dsetup:active
>	a=3Dsetup:passive DTLS
>
> And in general we could have:
>
>	m=3Dfoo 12345 A/B/C/D fmt1 fmt2 ...
>	a=3Dsetup:<direction> A/B/C/D
>	a=3Dsetup:<direction> A/B/C
>	a=3Dsetup:<direction> A/B
>	a=3Dsetup:<direction> A
>
> And do the same thing for a=3Dconnection.

It's an interesting idea, but I think it would be very complicated.

Also keep in mind that DTLS-SRTP (and other protocols using DTLS) already u=
se the setup attribute both for the connection protocol (if present) establ=
ishment direction and TLS role detection.

Also keep in mind that, for the SCTP association, we don't need to indicate=
 who is active and who is passive, as both endpoints try to establish the S=
CTP association.

Regards,

Christer


From nobody Tue Dec  2 09:37:56 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 577831A1B62 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:37:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] 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 wUonHTuvTGat for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:37:50 -0800 (PST)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D9BC1A1BBD for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:37:39 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-01v.sys.comcast.net with comcast id NhcN1p0012LrikM01hdeXk; Tue, 02 Dec 2014 17:37:38 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-12v.sys.comcast.net with comcast id Nhdd1p00L3Ge9ey01hddbv; Tue, 02 Dec 2014 17:37:38 +0000
Message-ID: <547DF8E1.2080700@alum.mit.edu>
Date: Tue, 02 Dec 2014 12:37:37 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417541858; bh=OZu1X2LJ8P2/Sf2YMcJmOCT8DqVazl2n/8iDRKdZ9d8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=tVPcfQmjL0qMi1RiZV+lIuRAyrJ8h1XxdQrG+086QlRheVpqQ7LTz1u1fYAAb9bnP HTW8a1oQ6zERwQsWW55tlfaxJ6jnUukmf99vjHNNsjDwJeXGi4W4pO/PwBADCVOAo6 EXUP2GyIWV125I1fTzhIL4UZDal/vSF6jtAoBiQH7krcPSWdY7taNCoE2S3oSNtDLj BhGB9QxrRkANTn+UAFnkXgcwP+MZLJBW5tGzlCYv2RcsbxXFi4KlECHOFA9o/Om5Pb Qdp2O+evMp8ULP9EvTUGA87Zk8Bgtyxeddk4U2EnSNYGBMsq/xvHrx7BlzRjbLqDbw t/Y8a0CBuCa4Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/eo8OWhorTr3FPHRN57kQuBvHxhQ
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:37:52 -0000

On 12/2/14 12:09 PM, Christer Holmberg wrote:
> Hi,
>
>>>> Section 6.2:
>>>>
>>>> I don't understand why sctpmap-attr is defined, since it isn't referenced anywhere. I think it is a holdover from when there was an sctpmap attribute.
>>>
>>> Correct, that is a mistake.
>>>
>>> The purpose of Section 6.2 is to define the format of the SDM fmtp attribute when used with SCTP.
>>>
>>>> It seems that what is being done here is to define the syntax of a=fmtp for all fmt values that might be used with sctp. I don't think that is kosher.
>>>> I think fmtp needs to be defined for webrtc-datachannel, and again for each other application-usage that wants to use it.
>>>>
>>>> It is unpleasant to expect all application-usages to do this. But the alternative is to go back to defining a special attribute for max-message-size. Perhaps:
>>>>
>>>>        Attribute name: sctp-attr
>>>>        Attribute value: sctp-attr-value
>>>>        Attribute Syntax:
>>>>
>>>>        sctp-attr-value = association-usage [max-message-size]
>>>>        max-message-size  =  "max-message-size" EQUALS 1*DIGIT
>>>
>>> If we decide to have a special attribute, why not simply call it "a=max-message-size"?
>>>
>>> We only allow a single association-usage per m- line, so there is no need to explicitly map the fmt value to a specific sctp-attr attribute.
>>>
>>>         Attribute name: sctp-max-message-size	(We can use a shorter name)
>>>         Attribute value: max-message-size
>>>         Attribute Syntax:
>>>
>>>         sctp-max-message-size = max-message-size
>>>         max-message-size  =  1*DIGIT
>>
>> That would work too, if we expect that there will only ever be the one sctp-association-wide property to specify.
>
> Well, if we want to specify max message size e.g. per SCTP stream, then we'd need something else. But, I don't think anyone has asked for that?

OK. I'm fine with a max-message-size attribute.
Define it only for SCTP, but maybe others might choose to define it for 
other protocols in the future.

>>>> Section 8:
>>>>
>>>> I think something probably needs to be said about sendonly/recvonly/inactive. I'm not sure what. Maybe
>>>> they shouldn't be used at all. Or maybe they can make some sort of sense.
>>>
>>> I was thinking about the same thing, but left it out of this version on purpose (I should have added an open issue regarding it, though).
>>>
>>> I see no reason why we couldn't use sendonly/recvonly/inactive also for SCTP - assuming it only impacts
>>> what is sent on the SCTP association. I.e. it would not impact the DTLS connection, and whatever (UDP or TCP) is below DTLS.
>>
>> My question is: what does it mean? (Given that there are multiple streams, and from an SCTP perspective the streams are unidirectional.) Some issues:
>>
>> - If someone is using channels, and the protocol over a channel requires ACKs, is it restricted to sendrecv?
>>
>> - Does it make sense to change the directionality of all the channels in parallel?
>
> Well, it depends on for what you are using the SCTP association.
>
> For example, if you would send RTP over SCTP, I guess you could use sendonly/recvonly in the same way as you do for UDP.

Sending RTP over SCTP opens up a new set of questions:
- which stream(s) are used?
- is RTCP sent on a different stream from RTP?
   (I guess it would be a good idea.)

Note that with RTP a=inactive applies to the RTP but not the RTCP.

All those questions need to be figured out again for RTP over SCTP.
And we had that discussion. People could find no benefit to RTP over 
SCTP, compared to SRTP over DTLS/SCTP.

Also note that sendrecv doesn't really make sense for SCTP *streams*, 
since they are all unidirectional. It does make sense over 
webrtc-datachannels, but that is a special case of SCTP.

> If you implement data channels, then sendonly/recvonly would probably cause problem in most cases. It's similar to the case where consent to send expires in one direction :)

It may make sense for certain protocols over the channels, but not others.

>> Also, there is the option of using the direction attributes on a per-channel basis via a=dcsa.
>
> I think such direction would have to be a subset of the SCTP association wide value.

I suppose we could view an association-wide value to be a default for a 
per-channel value. But again it only makes sense when channels are in use.

>> Maybe it makes the most sense, for now at least, to specify that the directionality attributes have no defined meaning in conjunction with an SCTP association.
>
> What if someone wants to use SCTP with preconditions?

Another can of worms. What do you want to prevent while negotiating 
preconditions? (E.g., do you want to block use of ICE until the 
preconditions are resolved?)

> Alternatively, we recommend against using non-sendrecv, unless one is absolutely sure it won't cause problems.

Without a definition of what it *means*, one can't be sure of anything.

If we are to define the meaning, then I guess
- sendonly: can send on outgoing streams (any ID), don't want to
   receive on any streams. (But what do you do if something still
   arrives on a stream?)
- recvonly: want to receive on incoming streams, will not send on
   any stream.
- inactive: will not send on any stream, don't want to receive on
   any stream.

This is at the SCTP level. Since DCEP uses messages on streams, this 
means you can't establish new channels on an inactive association.

I'm not sure about stream reset. Can it be sent on inactive or recvonly 
streams?

Whatever the right answers are, they need to be defined.

	Thanks,
	Paul

> IF used, it applies to the whole SCTP association, including all SCTP stresms etc.
>
> Regards,
>
> Christer
>


From nobody Tue Dec  2 09:51:03 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7FE31A6FB9 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.565
X-Spam-Level: 
X-Spam-Status: No, score=0.565 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_111=0.6, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] 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 RSinz511wFjo for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:51:01 -0800 (PST)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76B8C1A6FB8 for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:51:01 -0800 (PST)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-03v.sys.comcast.net with comcast id NhqF1p00D2PT3Qt01hr0Yp; Tue, 02 Dec 2014 17:51:00 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-14v.sys.comcast.net with comcast id Nhqz1p00i3Ge9ey01hr086; Tue, 02 Dec 2014 17:51:00 +0000
Message-ID: <547DFC03.5020100@alum.mit.edu>
Date: Tue, 02 Dec 2014 12:50:59 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se> <547CD27A.3090006@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se> <547DF1D2.6060908@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D5702F5@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5702F5@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417542660; bh=6ex5z2nIW0aIQxqDSScpQIyQsavMRfdnEFyLPkxBWKk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=hRGD+88dLRDsNEqID1Sd/r9CEK4VK60NRgfJVNIw+0Gol42DPReBIJ3RTlPWAN649 hBGIH4lSusEI9SNsqMgSg5o/z66QEZ1T7rywuCZQLpjPf55yU9eKoUTcwFAc0/kEvW sZaUqoS36T5ghvok0zELF6nEaKBcdG1ctpmtYBqjinv2fdbExu0hqNekMH0Ah40kGA chuDeA6l3cqegUaPuPcEwHB7qMG7LEM/xvfy0Vv2b5fF8DdkDLkzBPKm9fw1r+mHTB lMDDJ12ItA9+1OP/01WdsScRCWuUWODElt92OrlwI7X/LLIJJ0vdcXTh2PjQwc1GUL PqwOP6YWU+BCw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/vQj-Hy2SdTdJM2x1Spx4kxq03g8
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:51:02 -0000

On 12/2/14 12:23 PM, Christer Holmberg wrote:
> Hi,
>
>>>>> For 'DTLS/SCTP', there are some decisions to make:
>>>>>
>>>>> -If the transport layer protocol is UDP, I assume a 'new' value will
>>>>> not automatically re-establish the DTLS connection - only the SCTP
>>>>> association will be re-established.
>>>>
>>>> Why?
>>>>
>>>> If some part of the 5-tuple changes then it will be *necessary* to establish a new DTLS connection.
>>>
>>> Correct - I should have clarified that I am talking about the case there the 5-tuple does not change.
>>>
>>>> Even if the 5-tuple doesn't change, aren't there going to be cases where you want to reestablish the DTLS?
>>>
>>> Maybe there are. But, this is related to the question whether you need to signal that in SDP.
>>
>> If the fingerprint changes, then doesn't the DTLS need to be renegotiated? (Regardless of whether 'new' is specified.)
>>
>>>>> -However, if the transport layer protocol is TCP, does that mean
>>>>> that a 'new' value will mean that BOTH the TCP connection, AND the
>>>>> SCTP association, will be re-established? IF the TCP connection is
>>>>> also re-established, then I guess the DTLS connection will be re-established.
>>>>
>>>> There are all consequences of using the same atttribute to control independent behavior at two different layers of the protocol stack.
>>>
>>> Yes.
>>>
>>>> The *right* fix would be to have one attribute for the DTLS behavior and another for the SCTP behavior.
>>>
>>> We could for sure define an SDP "sctp-setup" attribute, IF people see a need for it.
>>
>> ISTM the issue is about there being multiple *layers* that are being negotiated, rather than specifically what protocol those layers are.
>>
>> So the only time you need to specify this is when there is ambiguity about which layer it might be.
>>
>> Perhaps we could define an extension to a=setup and a=connection. E.g.
>>
>>           setup-attr           =  "a=setup:" role [ " " proto]
>>           role                 =  "active" / "passive" / "actpass"
>>                                   / "holdconn"
>>
>> (where proto is as defined in SDP).
>
> That would assume that the protocol you want to control is actually explicitly part of the SDP proto field value.
>
>> When absent it would default to the entire proto field from the m-line. Other valid values would be prefixes of the proto in the m-line.
>> So, for the case at hand, we could have
>> 	m=application 12345 DTLS/SCTP webrtc-datachannel
>> 	a=setup:active DTLS/SCTP
>> 	a=setup:passive DTLS
>>
>> That would be entirely equivalent to:
>>
>> 	m=application 12345 DTLS/SCTP webrtc-datachannel
>> 	a=setup:active
>> 	a=setup:passive DTLS
>>
>> And in general we could have:
>>
>> 	m=foo 12345 A/B/C/D fmt1 fmt2 ...
>> 	a=setup:<direction> A/B/C/D
>> 	a=setup:<direction> A/B/C
>> 	a=setup:<direction> A/B
>> 	a=setup:<direction> A
>>
>> And do the same thing for a=connection.
>
> It's an interesting idea, but I think it would be very complicated.

Syntactically it is pretty simple.
Conceptually it is a bit complex because it makes you really think about 
the protocol layering.

> Also keep in mind that DTLS-SRTP (and other protocols using DTLS) already use the setup attribute both for the connection protocol (if present) establishment direction and TLS role detection.

Hmm. I guess it is true that what I have proposed means that in the case of

	m=audio 12345 DTLS/SRTP ...
	a=setup:active

Really applies to the SRTP over the DTLS, not the DTLS itself, and to 
refer specifically to the DTLS it would be necessary to override the 
default, with:

	m=audio 12345 DTLS/SRTP ...
	a=setup:active DTLS

Possibly that could be resolved by stating that the default for the 
proto is the longest prefix of the proto in the m-line for which a=setup 
is defined.

> Also keep in mind that, for the SCTP association, we don't need to indicate who is active and who is passive, as both endpoints try to establish the SCTP association.

Then why use a=setup for it?

	Thanks,
	Paul


From nobody Tue Dec  2 09:55:06 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C15B1A2130 for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 8rNLgCLvgpwa for <mmusic@ietfa.amsl.com>; Tue,  2 Dec 2014 09:55:01 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CF691A1BFB for <mmusic@ietf.org>; Tue,  2 Dec 2014 09:55:01 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-0d-547dfcf34263
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 75.96.29772.3FCFD745; Tue,  2 Dec 2014 18:54:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0195.001; Tue, 2 Dec 2014 18:54:59 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
Thread-Index: AdAKgkYeRp59/KWiSPW7X4BmEjVKXwDHIeIAABubemAADzXRAAACaWUA///424D//+55wA==
Date: Tue, 2 Dec 2014 17:54:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5703E3@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D53C625@ESESSMB209.ericsson.se> <547CD27A.3090006@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D56BEEE@ESESSMB209.ericsson.se> <547DF1D2.6060908@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D5702F5@ESESSMB209.ericsson.se> <547DFC03.5020100@alum.mit.edu>
In-Reply-To: <547DFC03.5020100@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvje7nP7UhBhtvqFhMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfG8Y0dLAVTmCtaDjSzNTBuZupi5OSQEDCR eHDvLiuELSZx4d56ti5GLg4hgSOMEgv+T2WFcBYzSpw/fg7I4eBgE7CQ6P6nDdIgIuAr8ezx bTYQW1jAXWL9/r2sEHEPiYNzp0DZYRLPNn4Hs1kEVCTm/nvADGLzAvXuXb2BCWL+biaJp82X WEDmcwroSPy9oQZSwwh00PdTa8AOZRYQl7j1ZD7U0QISS/acZ4awRSVePv4H9YCSROOSJ6wQ 9ToSC3Z/YoOwtSWWLXwNtVdQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcUoWpxanJSbbmSk l1qUmVxcnJ+nl5dasokRGCcHt/w22MH48rnjIUYBDkYlHt4Pn2pChFgTy4orcw8xSnOwKInz Ljw3L1hIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDo9+3c0n6+xuOTbijzvCx6vP9O7nbdGYt f+CgFutSvzj/wC8ecc3lfkaOL6JeXt39NnjqgWhW95tbvhexeRTdUlvpGJNnr13wdN+nPbfM l933+Z+pEjSFXXXK29/SJQts/m9qWc5g5vpQuOrqvYV/L0n7erUk2tf+O/ZNtkjek0lUWHZ+ YejbJCWW4oxEQy3mouJEAG0aee90AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nEpG89kY4ZHzDteUf1iXsBGlDLw
Subject: Re: [MMUSIC] SCTP-SDP: SDP connection attribute considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 17:55:03 -0000

Hi,

...

>> Also keep in mind that, for the SCTP association, we don't need to indic=
ate who is active and who is passive, as both endpoints try to establish th=
e SCTP association.
>
> Then why use a=3Dsetup for it?

To negotiate the TLS role.

And, again, I am talking about DTLS/SCTP and SCTP/DTLS. For "pure" SCTP the=
 setup attribute is not needed at all.

Regards,

Christer


From nobody Wed Dec  3 00:14:25 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891891A0166 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 00:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 jg0V_jm6Y71h for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 00:14:22 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CBC61A00F9 for <mmusic@ietf.org>; Wed,  3 Dec 2014 00:14:21 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-9f-547ec65b7bc9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C7.98.24955.B56CE745; Wed,  3 Dec 2014 09:14:19 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 09:14:19 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQANeciAAAN2uiD///tZgP//AsFQ
Date: Wed, 3 Dec 2014 08:14:19 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu>
In-Reply-To: <547DF8E1.2080700@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+JvjW70sboQg6e/5C2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj/arr7AVzxCt+bPvP1sDYL9TFyMkhIWAi sefqBRYIW0ziwr31bF2MXBxCAkcYJdae2MQI4SxmlNjzejFzFyMHB5uAhUT3P22QBhEBX4ln j2+zgdjCAlESJ/d2s0LEoyXe/d0MZbtJrOu4yg7SyiKgItF5zhUkzAvUumP5A7BWIYGrjBKX FqaC2JwCOhJbPzxjBLEZge75fmoNE4jNLCAucevJfCaIOwUkluw5zwxhi0q8fPyPFcJWlGh/ 2sAIUa8jsWD3JzYIW1ti2cLXzBB7BSVOznzCMoFRdBaSsbOQtMxC0jILScsCRpZVjKLFqcVJ uelGxnqpRZnJxcX5eXp5qSWbGIFRcnDLb9UdjJffOB5iFOBgVOLh3VBTFyLEmlhWXJl7iFGa g0VJnHfhuXnBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhinKK85YlA2YauWBS+zbjdvoGXd OZ+q6x5hIRlqVjvf8ocK/H3EL7B3nabe4icMR4LennlsLVAQlns08YJuU7CAq2tpRk9l2Vu7 zWxbBQ5M/vGjY8/Z6eGH3t7uzbOPu+m3b1nz3/ydFSURgod4tltXb3qucU30s5ZvX9BS7pCr 4iU1p3+t/6PEUpyRaKjFXFScCAAM9fAFcwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/pXVDXKlII9ekG4v_39QyblK60-A
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 08:14:23 -0000

Hi,

>>>>> Section 6.2:
>>>>>
>>>>> I don't understand why sctpmap-attr is defined, since it isn't refere=
nced anywhere. I think it is a holdover from when there was an sctpmap attr=
ibute.
>>>>
>>>> Correct, that is a mistake.
>>>>
>>>> The purpose of Section 6.2 is to define the format of the SDM fmtp att=
ribute when used with SCTP.
>>>>
>>>>> It seems that what is being done here is to define the syntax of a=3D=
fmtp for all fmt values that might be used with sctp. I don't think that is=
 kosher.
>>>>> I think fmtp needs to be defined for webrtc-datachannel, and again fo=
r each other application-usage that wants to use it.
>>>>>
>>>>> It is unpleasant to expect all application-usages to do this. But the=
 alternative is to go back to defining a special attribute for max-message-=
size. Perhaps:
>>>>>
>>>>>        Attribute name: sctp-attr
>>>>>        Attribute value: sctp-attr-value
>>>>>        Attribute Syntax:
>>>>>
>>>>>        sctp-attr-value =3D association-usage [max-message-size]
>>>>>        max-message-size  =3D  "max-message-size" EQUALS 1*DIGIT
>>>>
>>>> If we decide to have a special attribute, why not simply call it "a=3D=
max-message-size"?
>>>>
>>>> We only allow a single association-usage per m- line, so there is no n=
eed to explicitly map the fmt value to a specific sctp-attr attribute.
>>>>
>>>>         Attribute name: sctp-max-message-size	(We can use a shorter na=
me)
>>>>         Attribute value: max-message-size
>>>>         Attribute Syntax:
>>>>
>>>>         sctp-max-message-size =3D max-message-size
>>>>         max-message-size  =3D  1*DIGIT
>>>
>>> That would work too, if we expect that there will only ever be the one =
sctp-association-wide property to specify.
>>
>> Well, if we want to specify max message size e.g. per SCTP stream, then =
we'd need something else. But, I don't think anyone has asked for that?
>
> OK. I'm fine with a max-message-size attribute.
> Define it only for SCTP, but maybe others might choose to define it for o=
ther protocols in the future.

We could add text saying that the sctp-sdp draft only defines usag of the a=
ttribute for SCTP, SCTP/DTLS and DTLS/SCTP, and that usage with other proto=
 values need to be specified.

-------------

>>>>> Section 8:

...

First, I didn't suggest that we'd define RTP over SCTP. I only used RTP as =
an example where sendonly/recvonly/inactive is useful.

But, I DO hear what you are saying. I was checking RFC 4566 and 3264, and t=
hey are not very clear either. RFC 4566 does define the RTP/RTCP impacts, s=
o it seems it has to be done case by case.

So, I guess we could specify that the usage has to be defined per SCTP asso=
ciation usage.

Then, the question is whether we want to define the usage for webrtc-datach=
annels. We could do that either in the SCTP-SDP draft, or somewhere else - =
e.g. in Keith Richard's draft.

Regards,

Christer


From nobody Wed Dec  3 02:00:13 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFF61A19E4 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 02:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 AnECW-d0oBgG for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 02:00:10 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46C001A0AFE for <mmusic@ietf.org>; Wed,  3 Dec 2014 02:00:10 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-1e-547edf28a9f5
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 97.AC.29772.82FDE745; Wed,  3 Dec 2014 11:00:08 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 11:00:08 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Salvatore Loreto <salvatore.loreto@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
Thread-Index: AdAO3vobOG9fyqvZTs6dIUhJ2pZtLA==
Date: Wed, 3 Dec 2014 10:00:07 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyM+Jvja7G/boQg1c3VSymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvja3sna8E63oq555YwNjBe4epi5OSQEDCR uNtwiQnCFpO4cG89WxcjF4eQwBFGiQuvlrJDOIsZJb7uvsjSxcjBwSZgIdH9TxukQUQgRmLH tUdsIGFmAXWJq4uDQMLCAnkSp77uAasWEciXuPLeCaJaT+L4vc+sIDaLgIrE9hfHmEFsXgFf iaerdoPFGYFO+H5qDdg5zALiEreezIc6TUBiyZ7zzBC2qMTLx/9YIWxFifanDYwQ9ToSC3Z/ YoOwtSWWLXwNNV9Q4uTMJywTGEVmIRk7C0nLLCQts5C0LGBkWcUoWpxanJSbbmSkl1qUmVxc nJ+nl5dasokRGAsHt/w22MH48rnjIUYBDkYlHt4NNXUhQqyJZcWVuYcYpTlYlMR5F56bFywk kJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMUxvj8+6yA2CK6asy2BKTb+468ERgyzxzUFfZmTV Bj/bLVu5S25X3rnQ1X1uk2xPT7i4OmRSfL2uyPLTW7Ulyz/ZXZRsYF7tv1M+5+Oy2wGC8Ys/ V7StLLrRt+a3sUp0iqD/rhCm6DnTNJ19pbJnTgzs154gNoO/omj909hjbsqWqVIJXzd7KLEU ZyQaajEXFScCADaCHAxmAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/9JUM6scFOZgwsVPxFTJjiD-FOQM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 10:00:12 -0000

Hi,

>>>>> Section 5.1:
>>>>>
>>>>> IMO 5000 is a bad choice for the default port value. It falls in=20
>>>>> the middle of the registered port list. It isn't currently=20
>>>>> registered (I don't know why) but it potentially could. I suggest=20
>>>>> that a number outside of the registered port range
>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 -=
 the largest possible 16 bit number.
>>>>
>>>> I have no problem to change the default value.
>>>>
>>>> However, 5000 was defined before I got involved with the draft, so I t=
hink it would be good to get some input from Gonzalo and/or Salvatore wheth=
er there was some specific reason for 5000.
>>>>
>>>> -------------
>>>
>>> 5000 is the default value the current/available SCTP over TLS are using=
.
>>
>> just to clarify
>> what I meant is that 5000 is the value that as far as I know Firefox=20
>> is using in its SCTP over TLS data channel implementation
>
> AFAIK it is being explicitly specified as 5000, not that there is relianc=
e on a default value of 5000. Changing the default only affects those imple=
mentations depending on the default.
>
> Also, if those implementations are using different SDP syntax, not confor=
mant with this version of the draft, then they will need to be changed anyw=
ay before this change becomes effective.

Another option is to not define a default port to begin with, and mandate t=
he usage of the sctp-port attribute.

Because, assume you would have two SCTP associations (described using diffe=
rent m- lines), both without an sctp-port attribute. You would use the same=
 SCTP port for both SCTP associations...

Regards,

Christer


From nobody Wed Dec  3 04:26:01 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16AE11A1AC9 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 04:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 6BCRWYmRfnj6 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 04:25:56 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 031731A0174 for <mmusic@ietf.org>; Wed,  3 Dec 2014 04:25:55 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-d3-547f015245df
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 5B.3A.24955.2510F745; Wed,  3 Dec 2014 13:25:54 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 13:25:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQANeciAAAN2uiD///tZgP//AsFQ//231aA=
Date: Wed, 3 Dec 2014 12:25:53 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyM+JvjW4QY32IwaNuCYupyx+zWKzYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4Mr4evwxa8FXpYozl96yNDD2S3cxcnJICJhI XJvcxAhhi0lcuLeerYuRi0NI4AijxMvlU5kgnMWMEtPXvwWq4uBgE7CQ6P6nDRIXEWhmlLh2 fjkLSLewQJTEyb3drCC2iEC0xLu/m6FsP4n7n6aC1bAIqEi8v7ObCWQOr4CvxIW/KhDzZzJJ 7F4/kQmkhhOo/vjTG2C9jEAXfT+1BizOLCAucevJfCaISwUkluw5zwxhi0q8fPyPFcJWlGh/ 2sAIUa8jsWD3JzYIW1ti2cLXYPW8AoISJ2c+YZnAKDoLydhZSFpmIWmZhaRlASPLKkbR4tTi pNx0I2O91KLM5OLi/Dy9vNSSTYzASDm45bfqDsbLbxwPMQpwMCrx8G6oqQsRYk0sK67MPcQo zcGiJM678Ny8YCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2M2UsdfndZFLaVPXu88HxiZ/8d rq1/BFV3X7yrPNs7XidrW96HhFyDUA0z8Ydz/aM4RQ4a+EkI/psYtvno4cm5pxXSnGZ/Kp2d 7td8lVP+rkewrP+siK/LDY5sXleyz+He/13Gj8NU7l55/bH5Rvvess8sTv0neGa//92cOPuX 11nJVfPjUxe6K7EUZyQaajEXFScCAK8oWEZ1AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/_vKtvkhRKieF8YW2T_aS-w9rts4
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 12:25:58 -0000

Hi,

Below is some text suggestions:

>>>>>> Section 6.2:
>>>>>>
>>>>>> I don't understand why sctpmap-attr is defined, since it isn't refer=
enced anywhere. I think it is a holdover from when there was an sctpmap att=
ribute.
>>>>>
>>>>> Correct, that is a mistake.
>>>>>
>>>>> The purpose of Section 6.2 is to define the format of the SDM fmtp at=
tribute when used with SCTP.
>>>>>
>>>>>> It seems that what is being done here is to define the syntax of a=
=3Dfmtp for all fmt values that might be used with sctp. I don't think that=
 is kosher.
>>>>>> I think fmtp needs to be defined for webrtc-datachannel, and again f=
or each other application-usage that wants to use it.
>>>>>>
>>>>>> It is unpleasant to expect all application-usages to do this. But th=
e alternative is to go back to defining a special attribute for max-message=
-size. Perhaps:
>>>>>>
>>>>>>        Attribute name: sctp-attr
>>>>>>        Attribute value: sctp-attr-value
>>>>>>        Attribute Syntax:
>>>>>>
>>>>>>        sctp-attr-value =3D association-usage [max-message-size]
>>>>>>        max-message-size  =3D  "max-message-size" EQUALS 1*DIGIT
>>>>>
>>>>> If we decide to have a special attribute, why not simply call it "a=
=3Dmax-message-size"?
>>>>>
>>>>> We only allow a single association-usage per m- line, so there is no =
need to explicitly map the fmt value to a specific sctp-attr attribute.
>>>>>
>>>>>         Attribute name: sctp-max-message-size	(We can use a shorter n=
ame)
>>>>>         Attribute value: max-message-size
>>>>>         Attribute Syntax:
>>>>>
>>>>>         sctp-max-message-size =3D max-message-size
>>>>>         max-message-size  =3D  1*DIGIT
>>>>
>>>> That would work too, if we expect that there will only ever be the one=
 sctp-association-wide property to specify.
>>>
>>> Well, if we want to specify max message size e.g. per SCTP stream, then=
 we'd need something else. But, I don't think anyone has asked for that?
>>
>> OK. I'm fine with a max-message-size attribute.
>> Define it only for SCTP, but maybe others might choose to define it for =
other protocols in the future.
>
> We could add text saying that the sctp-sdp draft only defines usag of the=
 attribute for SCTP, SCTP/DTLS and DTLS/SCTP, and that usage with other pro=
to values need to be specified.

Suggested text:

-------------

6.  SDP 'max-message-size' Attribute

6.1.  General

   The SDP 'max-message-size' attribute can be associated with an m-
   line to indicate the maximum message size that an SCTP endpoint is
   willing to receive on the SCTP association associated with the m-
   line.

   The remote peer MUST assume that larger messages will be rejected by
   the SCTP endpoint.  SCTP endpoints need to decide on appropriate
   behaviour in case a message that exceeds the maximum size needs to be
   sent.

   If the SDP 'max-message-size' attribute contains a maximum message
   size value of zero, it indicates the SCTP endpoint will handle
   messages of any size, subject to memory capacity etc.

   If the SDP 'max-message-size' attribute is not present, the default
   value is 64K.

6.2.  Syntax

       max-message-size-attr =3D  "a=3Dmax-message-size:" max-message-size
       max-message-size      =3D  1*DIGIT

-------------


Section 8:

>...
>
> First, I didn't suggest that we'd define RTP over SCTP. I only used RTP a=
s an example where sendonly/recvonly/inactive is useful.
>
> But, I DO hear what you are saying. I was checking RFC 4566 and 3264, and=
 they are not very clear either. RFC 4566 does define the RTP/RTCP impacts,=
 so it seems it has to be done case by case.
>
> So, I guess we could specify that the usage has to be defined per SCTP as=
sociation usage.
>
> Then, the question is whether we want to define the usage for webrtc-data=
channels. We could do that either in the SCTP-SDP draft, or somewhere else =
- e.g. in Keith Richard's draft.

Suggested text:

-------------

8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute

   This specification does not define usage of the SDP direction
   attributes.  Specifications for an individual SCTP association usage
   MAY define how the attributes can be used with that usage.  If usage
   for a SCTP association usage has not be defined, SDP direction
   attributes MUST be discarded if present.

-------------

Regards,

Christer



From nobody Wed Dec  3 04:56:57 2014
Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E151A1AA6 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 04:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 5wMRE7ODm_ZI for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 04:56:53 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8401A1A17 for <mmusic@ietf.org>; Wed,  3 Dec 2014 04:56:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id D7E687C32D9 for <mmusic@ietf.org>; Wed,  3 Dec 2014 13:56:51 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stbfreRiF91A for <mmusic@ietf.org>; Wed,  3 Dec 2014 13:56:41 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:70d4:5af0:ebdf:3bb]) by mork.alvestrand.no (Postfix) with ESMTPSA id 9FBAC7C0C0E for <mmusic@ietf.org>; Wed,  3 Dec 2014 13:56:41 +0100 (CET)
Message-ID: <547F0889.6080008@alvestrand.no>
Date: Wed, 03 Dec 2014 13:56:41 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VKEFoxJ6H8j2WGh6hXZwLLc_-uQ
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 12:56:55 -0000

On 12/03/2014 01:25 PM, Christer Holmberg wrote:
> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>
>     This specification does not define usage of the SDP direction
>     attributes.  Specifications for an individual SCTP association usage
>     MAY define how the attributes can be used with that usage.  If usage
>     for a SCTP association usage has not be defined, SDP direction
>     attributes MUST be discarded if present.

Looks good to me, but you might want to avoid using "usage" twice with 
different meanings in the same sentence.

What about:

8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute

    This specification does not define any meaning for the SDP direction
    attributes.  Specifications for an individual SCTP association usage
    MAY define how the attributes can be used with that usage.  If the meaning
    of these attributes for a SCTP association usage has not been defined, SDP direction
    attributes MUST be discarded if present.



From nobody Wed Dec  3 05:55:41 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0891A1B2B for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 05:55:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 SBJEFAOpOWla for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 05:55:38 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B8121A1AE3 for <mmusic@ietf.org>; Wed,  3 Dec 2014 05:55:37 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-62-547f1657a3d6
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id C5.AF.04231.7561F745; Wed,  3 Dec 2014 14:55:35 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0195.001; Wed, 3 Dec 2014 14:55:34 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
Thread-Index: AdAODNkiaIw1Y9qQQkmGjr1PcUsXoQANeciAAAN2uiD///tZgP//AsFQ//231aCABIlBgP//3w6A
Date: Wed, 3 Dec 2014 13:55:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D573605@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se> <547F0889.6080008@alvestrand.no>
In-Reply-To: <547F0889.6080008@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrELMWRmVeSWpSXmKPExsUyM+JvjW64WH2Iwd+ZOhbH+rrYLKYuf8zi wORxZcIVVo8lS34yBTBFcdmkpOZklqUW6dslcGUsmrCaseAvd8Wlpl7GBsbznF2MnBwSAiYS +8/MZIawxSQu3FvP1sXIxSEkcIRRYm/XByYIZzGjxIRHn4EyHBxsAhYS3f+0QRpEBIIlln/a zgRiCwtESZzc280KEY+WePd3M5QdJfH86nFGEJtFQEVi56I+dhCbV8BXYuKa/+wQ8xuYJba3 TwNr4BTQlfh0+CUbiM0IdNH3U2vAFjALiEvcejKfCeJSAYkle85DXS0q8fLxP1YIW1Gi/WkD I0S9jsSC3Z/YIGxtiWULXzNDLBaUODnzCcsERtFZSMbOQtIyC0nLLCQtCxhZVjGKFqcWF+em GxnrpRZlJhcX5+fp5aWWbGIERsrBLb91dzCufu14iFGAg1GJh3dDTV2IEGtiWXFl7iFGaQ4W JXHeRefmBQsJpCeWpGanphakFsUXleakFh9iZOLglGpgjP+2u+0wl4GAZPeOYvejWyfwKcnX SAknhXAsqOV6u+vmnB/XFzZKibyo1RK03v7RausHsy93I/ae3rjrZ57l+flLohyubvb6eUOh KeLGLullExSOeW68uE57lpTBz9OSE9PWi1zvZaxbfOnm8YevlL7H2eWUqU71mPpZTjY0lP+B imKq5Daj90osxRmJhlrMRcWJABsdDkh1AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nDvSHwzD7im_eR_T1gliZbSea4w
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 13:55:39 -0000

Hi Harald,

You suggested text looks good, but perhaps "semantics" instead of "meaning"=
?=20

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestran=
d
Sent: 3. joulukuuta 2014 14:57
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Pa=
ul's comments

On 12/03/2014 01:25 PM, Christer Holmberg wrote:
> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>
>     This specification does not define usage of the SDP direction
>     attributes.  Specifications for an individual SCTP association usage
>     MAY define how the attributes can be used with that usage.  If usage
>     for a SCTP association usage has not be defined, SDP direction
>     attributes MUST be discarded if present.

Looks good to me, but you might want to avoid using "usage" twice with diff=
erent meanings in the same sentence.

What about:

8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute

    This specification does not define any meaning for the SDP direction
    attributes.  Specifications for an individual SCTP association usage
    MAY define how the attributes can be used with that usage.  If the mean=
ing
    of these attributes for a SCTP association usage has not been defined, =
SDP direction
    attributes MUST be discarded if present.


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Dec  3 06:18:20 2014
Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32EF91A1B2F for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 06:18:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 ente_mR0Y3wz for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 06:18:15 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id D3C771A1B27 for <mmusic@ietf.org>; Wed,  3 Dec 2014 06:18:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id ED8BE7C0BDE; Wed,  3 Dec 2014 15:18:13 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjhg_OVCz9lX; Wed,  3 Dec 2014 15:18:09 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:70d4:5af0:ebdf:3bb]) by mork.alvestrand.no (Postfix) with ESMTPSA id 9A3DE7C0B4A; Wed,  3 Dec 2014 15:18:09 +0100 (CET)
Message-ID: <547F1B9F.40304@alvestrand.no>
Date: Wed, 03 Dec 2014 15:18:07 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se> <547F0889.6080008@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D573605@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D573605@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/FoPlcKUqbEprpJDrTGNGlnk0UR4
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 14:18:18 -0000

On 12/03/2014 02:55 PM, Christer Holmberg wrote:
> Hi Harald,
>
> You suggested text looks good, but perhaps "semantics" instead of "meaning"?

"semantics" is probably good. "meaning" brings out the epistomologists.....

>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestrand
> Sent: 3. joulukuuta 2014 14:57
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
>
> On 12/03/2014 01:25 PM, Christer Holmberg wrote:
>> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>>
>>      This specification does not define usage of the SDP direction
>>      attributes.  Specifications for an individual SCTP association usage
>>      MAY define how the attributes can be used with that usage.  If usage
>>      for a SCTP association usage has not be defined, SDP direction
>>      attributes MUST be discarded if present.
> Looks good to me, but you might want to avoid using "usage" twice with different meanings in the same sentence.
>
> What about:
>
> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>
>      This specification does not define any meaning for the SDP direction
>      attributes.  Specifications for an individual SCTP association usage
>      MAY define how the attributes can be used with that usage.  If the meaning
>      of these attributes for a SCTP association usage has not been defined, SDP direction
>      attributes MUST be discarded if present.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Dec  3 06:53:18 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D05B1A1B38 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 06:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 xNXNeg30GZzX for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 06:53:05 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 167BC1A1BA4 for <mmusic@ietf.org>; Wed,  3 Dec 2014 06:51:45 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-08v.sys.comcast.net with comcast id P2ql1p00926dK1R012rlCk; Wed, 03 Dec 2014 14:51:45 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-01v.sys.comcast.net with comcast id P2rk1p00R3Ge9ey012rkf6; Wed, 03 Dec 2014 14:51:45 +0000
Message-ID: <547F2380.8060706@alum.mit.edu>
Date: Wed, 03 Dec 2014 09:51:44 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417618305; bh=5Ay/KQEauMXab8EDX91lTjNY+YCBT0PaFkLLEyFSem4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=OXFEZ+c4HHch4pW7mrE2qVFSeA6853GBRwH5qJXjVYmhofX0ZHJIloQdgWQnGVb1m jpBT2xtH4SK/psCLaRCUxgcRPaVHpAjQiEdBBa7HFFSQueYNX6y3St//nUwoDg5WqV dg/uhkPqIOj4o1hAtmob+f0pcBNLh8U6B0Q47PFJAtF4jA6+u4sKRxXX/X3WH4fLW1 pB2pjo1frgjLLn9qZnHx1yQkIvtxE8H+vqb7NM+KbVFwmWE4tUQqTl4eaD5VsCz50W xTAOG65RCQscO3y04NgvBtOd+pg398c5RH94JqoWk5INVkN1EiIzg6Dr3nqRsU+oL7 IUOvPF+Rk24wA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VjihmTlOEpWBvlDK-I4Q69ialaU
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 14:53:09 -0000

On 12/3/14 5:00 AM, Christer Holmberg wrote:
> Hi,
>
>>>>>> Section 5.1:
>>>>>>
>>>>>> IMO 5000 is a bad choice for the default port value. It falls in
>>>>>> the middle of the registered port list. It isn't currently
>>>>>> registered (I don't know why) but it potentially could. I suggest
>>>>>> that a number outside of the registered port range
>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>>>>>
>>>>> I have no problem to change the default value.
>>>>>
>>>>> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>>>>>
>>>>> -------------
>>>>
>>>> 5000 is the default value the current/available SCTP over TLS are using.
>>>
>>> just to clarify
>>> what I meant is that 5000 is the value that as far as I know Firefox
>>> is using in its SCTP over TLS data channel implementation
>>
>> AFAIK it is being explicitly specified as 5000, not that there is reliance on a default value of 5000. Changing the default only affects those implementations depending on the default.
>>
>> Also, if those implementations are using different SDP syntax, not conformant with this version of the draft, then they will need to be changed anyway before this change becomes effective.
>
> Another option is to not define a default port to begin with, and mandate the usage of the sctp-port attribute.
>
> Because, assume you would have two SCTP associations (described using different m- lines), both without an sctp-port attribute. You would use the same SCTP port for both SCTP associations...

Remember - multiple SCTP associations, especially bundled ones, is 
likely to be a very rare occurrence. The normal case, especially in a 
bundle, will be for a single one. In that case the sctp port is 
irrelevant. So, optimizing for the common case by having a default will 
be one less thing that most people won't have to think about.

	Thanks,
	Paul


From nobody Wed Dec  3 07:01:29 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F381A1B2F for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 07:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 DcgHE7haXu5h for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 07:01:27 -0800 (PST)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07761A1A4E for <mmusic@ietf.org>; Wed,  3 Dec 2014 07:01:26 -0800 (PST)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-07v.sys.comcast.net with comcast id P31R1p0092AWL2D0131Rs8; Wed, 03 Dec 2014 15:01:25 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-04v.sys.comcast.net with comcast id P31R1p00L3Ge9ey0131RES; Wed, 03 Dec 2014 15:01:25 +0000
Message-ID: <547F25C5.6090003@alum.mit.edu>
Date: Wed, 03 Dec 2014 10:01:25 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D56BE8C@ESESSMB209.ericsson.se> <547DE589.7010108@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D57024A@ESESSMB209.ericsson.se> <547DF8E1.2080700@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D572773@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5731D5@ESESSMB209.ericsson.se> <547F0889.6080008@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D573605@ESESSMB209.ericsson.se> <547F1B9F.40304@alvestrand.no>
In-Reply-To: <547F1B9F.40304@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417618885; bh=nvQ4HUOVEkVjBYa8lVL0cie9C1ApQj69UpJxVGkSgD0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=iIC2g9ZWSgoo5ukGVCSlZzHUK1LjBMTelvHgDckAE986VKMRUuG9LJ7xojPSLqu2q qk4APGH7stDdub8q67CjEM5Ytng19LHUI4E1OTQ+rN3ciZSrkm/hgUVr/32luMIDOZ 4uqNpVEWYou2cnaMkZacs+JGINneDK4P4oRYmoLWN1pGoJixv9tbE3zBmhrcQUWskM RTa/I07fS303+slq36zhfY3h+cvDMBZE0Z3C1km57vXCwNIxdWHad0B2EA1M6oYb3n 61uDpB3u2cmTuFzHI25KM5HEFf/dVWwxkK4vWnm1nETvT9Kzo/CB9PBr/K9LGhC9T6 75Jw9bRrUmeFA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nkdrFdv84R-rSWNqzi4hch1-Ko4
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 15:01:28 -0000

WFM

On 12/3/14 9:18 AM, Harald Alvestrand wrote:
> On 12/03/2014 02:55 PM, Christer Holmberg wrote:
>> Hi Harald,
>>
>> You suggested text looks good, but perhaps "semantics" instead of
>> "meaning"?
>
> "semantics" is probably good. "meaning" brings out the epistomologists.....
>
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald
>> Alvestrand
>> Sent: 3. joulukuuta 2014 14:57
>> To: mmusic@ietf.org
>> Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08
>> - Paul's comments
>>
>> On 12/03/2014 01:25 PM, Christer Holmberg wrote:
>>> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>>>
>>>      This specification does not define usage of the SDP direction
>>>      attributes.  Specifications for an individual SCTP association
>>> usage
>>>      MAY define how the attributes can be used with that usage.  If
>>> usage
>>>      for a SCTP association usage has not be defined, SDP direction
>>>      attributes MUST be discarded if present.
>> Looks good to me, but you might want to avoid using "usage" twice with
>> different meanings in the same sentence.
>>
>> What about:
>>
>> 8.2.  SDP sendrecv/sendonly/sendrecv/inactive Attribute
>>
>>      This specification does not define any meaning for the SDP direction
>>      attributes.  Specifications for an individual SCTP association usage
>>      MAY define how the attributes can be used with that usage.  If
>> the meaning
>>      of these attributes for a SCTP association usage has not been
>> defined, SDP direction
>>      attributes MUST be discarded if present.
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Wed Dec  3 09:51:02 2014
Return-Path: <dwing@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B25C11A8AE9; Wed,  3 Dec 2014 09:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 qi3O9W5eBamd; Wed,  3 Dec 2014 09:50:53 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08B5D1A8AF2; Wed,  3 Dec 2014 09:50:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2447; q=dns/txt; s=iport; t=1417629048; x=1418838648; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=DFXBXqDk9dGC/W54xS5yizI0WPAz/NLp2o0iH6QXRGs=; b=AatHFc9pih596H5EG8+t2310vlYPWxzr4M7ABiBUx32huMuePUVRuPQe NDhjXz4K/ADYfTxaA2zeL7y0akyCovn2ThSo8O2tDueLYpcTS9TsQmAw8 x3XW4NF6n6y20kC6Qm1fw8J/Z4G3ZAHHo5DXe9zsjaNmFJnvsDnj0ZcE8 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAJtMf1StJA2K/2dsb2JhbABagwZSxyGGF4EWFgEBAQEBfYQwEz0CgT+IUA3WPgEBAQEGAQEBAQEBAQEBFQSQZoMrgR4FilKJU4Y0gSKFeSWMVoQZHoJ1AQEB
X-IronPort-AV: E=Sophos;i="5.07,509,1413244800"; d="scan'208";a="102363874"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP; 03 Dec 2014 17:50:47 +0000
Received: from [10.24.69.20] ([10.24.69.20]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sB3Hogt6016801 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 3 Dec 2014 17:50:45 GMT
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Dec 2014 09:50:41 -0800
Message-Id: <86C3445F-F8D6-4208-8D42-A16B218B146B@cisco.com>
To: draft-ietf-avtext-splicing-notification@tools.ietf.org, avtext@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/hza47xcRBoS8ZTyUZTiYlnAYRvY
Cc: mmusic <mmusic@ietf.org>
Subject: [MMUSIC] SDP directorate review of draft-ietf-avtext-splicing-notification-00
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 17:50:57 -0000

SDP directorate review of draft-ietf-avtext-splicing-notification-00, =
Dan Wing, 2-Dec-2014.

1.  the SDP in draft-ietf-avtext-splicing-notification is re-using FID =
from RFC5888, but is using different semantics.  How does a receiver =
know if the FID semantics are RFC5888's semantics or are =
draft-ietf-avtext-splicing-notification's semantics?  Seems we would =
benefit from an indication of the semantics in the SDP, perhaps a new =
session-level attribute (e.g., "a=3Dsplicing") or perhaps not re-use =
a=3Dgroup:FID and instead invent its own grouping for splicing (e.g., =
a=3Dgroup:SPLICE).

2. Security Considerations says:

   In the Secure Real-time Transport Protocol =20
   (SRTP)[RFC3711], RTP header extensions are authenticated but not =20
   encrypted.  A malicious endpoint could choose to set the values in =20=

   this header extension falsely, so as to falsely claim the splicing =20=

   time.

A malicious endpoint would need the SRTP key to do that, correct?  The =
I-D should mention that the malicious endpoint needs the SRTP key. =20

Also, auch a malicious endpoint (with possession of the SRTP key) could =
also cause splicing of any arbitrary content it wishes, like a Rick =
Astley video, which is a different attack that isn't just against the =
*time*.  I-D should mention that.  I don't think either of these are =
significant, as the same problem exists without splicing.



Nits: =20

1. The SDP in Section 6 has spurious whitespace, for example a space =
after "m=3D", which is prohibited by =
https://tools.ietf.org/html/rfc4566#page-8 ("Whitespace MUST NOT be used =
on either side of the "=3D" sign").  My read of the grouping RFC =
(RFC5888) is that it doesn't allow the spurious whitespace after =
"a=3Dmid:", either.  The SDP in Section 6 is unclear if it is normative =
or a non-normative example.

2. Section 3.1 title, "ExtenTion" -> "ExtenSion"

3. Section 4 title, "Reduing" -> "ReduCing"

4. Section 6,
OLD:
   But at
   a particular point in time, the mixer only selects one stream and
   output the content from the chosen stream to the downstream
   receivers.
NEW:
   But at
   a particular point in time, the mixer only selects one stream and
   outputs the content from the chosen stream to the downstream
.........^
   receivers.

5. idnits had a couple of complaints, =
https://tools.ietf.org/tools/idnits/webservice

-d


From nobody Wed Dec  3 10:07:24 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E371A8AE8 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:07:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.235
X-Spam-Level: 
X-Spam-Status: No, score=-3.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_I_LETTER=-2, SPF_SOFTFAIL=0.665] 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 QnwXwI0FOUQN for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:07:14 -0800 (PST)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A6541A8734 for <mmusic@ietf.org>; Wed,  3 Dec 2014 10:07:11 -0800 (PST)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with comcast id P6721p00B2GyhjZ01679bN; Wed, 03 Dec 2014 18:07:09 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-09v.sys.comcast.net with comcast id P6781p00g3Ge9ey01679Lj; Wed, 03 Dec 2014 18:07:09 +0000
Message-ID: <547F514C.4020707@alum.mit.edu>
Date: Wed, 03 Dec 2014 13:07:08 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu> <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org>
In-Reply-To: <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417630029; bh=ybz4gkFjVzcEeEzwJh2eZUPYNYMsu4jACg8yqu2DZks=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=eTD065elw5xpLWNDmhCGpUnZ39KNEIH4kwvYd7xgZxSHWx55/KQEqnJ5AGmog/suW kYgWHhGyO/edkQdjQKleBy3JSmevjFwWZdIzt/SU1xHXnBbA0Xe6LnAa65LlDgfKf1 jCY5PfmkCIBNzZJrghCvIkZ0/cvt8vD9MuMtpTIoZBYlEAnBilxCcLhs+W8IlexxmQ Rbca84cudg2ZU0SrUder28KS8Jtd9tnpAbQ4Rmbt6we2KKfotsmQty3ZM70lhFkmGd Od090NUeWTjE4j+shxt7NW4kMCdZlBUBvaIzjf7hq6noIwwUDy75A1NR4ADZcizwKT rmRHgjeWK2TJg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/zUAeJgmfIZis8n9rMfQRwyVZmW0
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 18:07:21 -0000

On 12/1/14 6:39 PM, Colin Perkins wrote:

>>> *a=charset:*
>>> - This is a name from the registry at
>>> http://www.iana.org/assignments/character-sets/character-sets.xhtml and needs to follow that syntax
>>
>> In this and other cases where what goes in the SDP is a reference to something defined in a registry, I am inclined to give a simplified syntax that might be a superset of what is permitted in the registry. It doesn't matter a whole lot if it allows some invalid values, because such names will never be in the registry.
>>
>> This will help implementers. And when the exact formal definition isn't available in ABNF, or is very complex, it can also ease formal checking of the SDP ABNF.
>>
>> Given that explanation, is there anything wrong with what I have?
>
> Why not reference the correct ABNF from RFC 2978? I don’t understand the desire to put something incorrect here.

I've looked again at 2978, and it is less than clear. It says:

    Each assigned name MUST uniquely identify a single charset.  All
    charset names MUST be suitable for use as the value of a MIME content
    type charset parameter and hence MUST conform to MIME parameter value
    syntax.  This applies even if the specific charset being registered
    is not suitable for use with the "text" media type.
    ...
    Finally, charsets being registered for use with the "text" media type
    MUST have a primary name that conforms to the more restrictive syntax
    of the charset field in MIME encoded-words [RFC-2047, RFC-2184] and
    MIME extended parameter values [RFC-2184].  A combined ABNF
    definition for such names is as follows:

      mime-charset = 1*mime-charset-chars
      ...

The final paragraph above seems to say that mime-charset only applies 
for charsets registered for use with "text", but based on the first 
paragraph this syntax could apply for all charset names.

And this syntax doesn't apply any limit to how long the names can be, 
while the IANA registry itself says:

    The character set names may be up to 40 characters taken from the
    printable characters of US-ASCII.  However, no distinction is made
    between use of upper and lower case letters.

I based my ABNF on that. But yes, I could reference mime-charset from 2978.

Note also that I currently reference "Preferred MIME Name", but have a 
note asking if I should instead be referencing "Name". These are 
references to column headings in the table in the registry, for lack of 
something better to reference. Looking again at the registry, I think I 
need instead to say:

OLD:

    The charset specified MUST be one of those registered with IANA, such
    as ISO-8859-1.  The character set identifier is a US-ASCII string and
    MUST be compared against the IANA identifiers using a case-
    insensitive comparison.  If the identifier is not recognised or not
    supported, all strings that are affected by it SHOULD be regarded as
    octet strings.

NEW:

    The charset specified MUST be one of those registered in the IANA
    Character Sets registry
    (http://www.iana.org/assignments/character-sets), such
    as ISO-8859-1.  The character set identifier is a US-ASCII string and
    MUST be compared against identifiers from the "Name" or "Preferred
    MIME Name" field of the registry using a case-insensitive
    comparison.  If the identifier is not recognised or not supported,
    all strings that are affected by it SHOULD be regarded as octet
    strings.

I think this is needed because the identifiers in the "Preferred MIME 
Name" field are not repeated in the "Name" field, but both are allowed 
to be used in references.

	Thanks,
	Paul


From nobody Wed Dec  3 10:29:53 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1DF01A6FF1 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.065
X-Spam-Level: *
X-Spam-Status: No, score=1.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MANGLED_STOP=2.3, SPF_SOFTFAIL=0.665] 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 z7O6Hp5OozAB for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:29:49 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 186461A1AD8 for <mmusic@ietf.org>; Wed,  3 Dec 2014 10:29:48 -0800 (PST)
Received: from resomta-ch2-07v.sys.comcast.net ([69.252.207.103]) by resqmta-ch2-10v.sys.comcast.net with comcast id P6VR1p00B2EPM31016VoJz; Wed, 03 Dec 2014 18:29:48 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-07v.sys.comcast.net with comcast id P6Vn1p00H3Ge9ey016VnDC; Wed, 03 Dec 2014 18:29:48 +0000
Message-ID: <547F569B.5040305@alum.mit.edu>
Date: Wed, 03 Dec 2014 13:29:47 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu> <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org>
In-Reply-To: <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417631388; bh=PW2PdHj3e6EkpmL8X6rVqu4Ns3li3Hz0ESZz0E2beLA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=bpNnPLKK4Z55dCkWWUYoJ5oRjLsQJ0mEWCxp7mPzV5CX5qyEXBkwGyczGZEa60UeD /UmNDX8xd7lBUpMi11yqIYlZkUVbLC+0aQFqxyWxPPhGZVCK+V4g/X2DlAi2pWVG8Z YdjPB5FCiabb+2NTbbBn9zdOrDUrrv5mQQg6EXNF+esjh9Y638aoSkbnlXTvwl+tzd osLOxVdpqwWksBNAK2dKdwqaVhS8mrWbNH4IetkEJx2lcEtg9PPXCaKBIHLvQ4NUnM ix8iXs304J5GXSUACOiT5LlN3cSNda2BLGthcAYGB6OXmd3lX76wwpRF7tJ0bfJFhL jgTjGMUmHu0aA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yMvbnXLqCd5sl10FOCAjafv8UeE
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 18:29:51 -0000

On 12/1/14 6:39 PM, Colin Perkins wrote:

>>> *a=rtpmap:*
>>> - payload-type is an integer in the range 0-127 in RTP
>>> - encoding-name is a MIME subtype, and should have the syntax to match this
>>> - is clock-rate always an integer?
>>
>> If there is no way that larger values could ever be used then I'm fine with calling out this restriction. I’ll probably do it in text rather than in ABNF.
>
> The payload type is a 7-bit field in the RTP header, so definitely cannot be outside this range. Writing this in the text makes sense.

ok

>>> *a=type:*
>>> - I assume a registry was intended, but it’s not clear there’s any need now
>>
>> Do you mean that you don't think we need a mechanism to define further values? Or that it would be sufficient to do so with another update to this document?
>
> This list hasn’t changed in RFC 2327 in 1998. I think it’s safe to leave updates to a future revision of this document.

ok

>> Do you know if these names were intended to be case sensitive? That is an important distinction to make. And whatever choice is made will potentially have backward compatibility problems for somebody.
>
> I expect the general rule at the start of Section 5 (top of page 8) applies:
>
>     An SDP session description consists of a number of lines of text of
>     the form:
>
>        <type>=<value>
>
>     where <type> MUST be exactly one case-significant character and
>     <value> is structured text whose format depends on <type>.  In
>     general, <value> is either a number of fields delimited by a single
>     space character or a free format string, and is case-significant
>     unless a specific field defines otherwise.
>
> Hence, this is case significant.

That is how I have the syntax written now.
So I'll leave it that way unless I get some other strong argument to 
change it.

>>> *a=charset:*
>>> - This is a name from the registry at
>>> http://www.iana.org/assignments/character-sets/character-sets.xhtml and needs to follow that syntax
>>
>> In this and other cases where what goes in the SDP is a reference to something defined in a registry, I am inclined to give a simplified syntax that might be a superset of what is permitted in the registry. It doesn't matter a whole lot if it allows some invalid values, because such names will never be in the registry.
>>
>> This will help implementers. And when the exact formal definition isn't available in ABNF, or is very complex, it can also ease formal checking of the SDP ABNF.
>>
>> Given that explanation, is there anything wrong with what I have?
>
> Why not reference the correct ABNF from RFC 2978? I don’t understand the desire to put something incorrect here.

I commented on this separately.

>>> *a=sdplang:* and *a=lang:*
>>> - Should reference the RFC5646 definition
>>
>> Same comment as charset.
>
> Same answer. There’s already a standard ABNF syntax for these, and this document should refer to it rather than trying to define something new.

OK. I can do that.

>>> *a=quality:*
>>> - I thought the intent here was a real number, in the range 0…10
>>
>> What I could find only discussed quality in the context of video media, and restricted the range to 0..10 in that case. But it didn't explicitly limit (or define) the use of quality for other media. It seems reasonable to me that the same range would apply to any media where quality applies, but I wasn't sure.
>>
>> Also, should the values here be restricted to integral values, or should fractional values be allowed?
>
> I always assumed fractional values were allowed, but you’d have to check with someone who’s implemented this.

I'm happy to do that if it isn't going to break anybody.

I *could* do it so that the fraction is only permitted if it is 
non-zero, as I proposed for another field. But that doesn't necessarily 
make things better if there are uses out there that include a zero 
fractional part.

>> BTW - I just noticed I have an error in my ABNF: I limit the quality-value to an integer, which excludes zero. So I need to change the abnf in one way or another.
>>
>>> *a=fmtp:*
>>> - The format parameters are MIME media type parameters, and need to
>>> reflect their syntax.
>>
>> My understanding is that the values are whatever was in the <fmt> field of the associated m-line. What is valid there is defined for each <proto> field. For the RTP variants, it is a payload type. For UDP it is a media (sub)type. But we can't know in general what if might be for other <proto>s, since new ones could be defined in the future.
>>
>> The m-line syntax defines the fmt as a token. So I figured that the same definition should be used here.
>
> For RTP, you do know explicitly that the <format specific parameters> in the a=fmtp: line are MIME media subtype parameters, and need to conform to that syntax.

We aren't concerned with the <format specific parameters> here.
(The syntax of those is format specific.:-)

We are only concerned with the <fmt> parameter, which replicates one 
from the m-line.

For RTP m-lines this will always be an integer. But for the most part 
rtpmap is used instead of fmtp for RTP format specific parameters. There 
is text saying to use fmtp for codec-specific parameters. So I guess if 
fmtp is used with RTP then one would first need to use rtpmap to 
determine the codec, and then use rules defined by that codec to parse 
the format specific parameters.

	Thanks,
	Paul


From nobody Wed Dec  3 10:32:56 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF681A904C for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:32:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 hRoWLWFBTwH7 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 10:32:49 -0800 (PST)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4741A9008 for <mmusic@ietf.org>; Wed,  3 Dec 2014 10:32:17 -0800 (PST)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-04v.sys.comcast.net with comcast id P6XP1p00327uzMh016YGgS; Wed, 03 Dec 2014 18:32:16 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-02v.sys.comcast.net with comcast id P6YG1p00D3Ge9ey016YGtD; Wed, 03 Dec 2014 18:32:16 +0000
Message-ID: <547F5730.80805@alum.mit.edu>
Date: Wed, 03 Dec 2014 13:32:16 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu> <547CEBC5.5070209@nteczone.com>
In-Reply-To: <547CEBC5.5070209@nteczone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417631536; bh=H6qZns24lL3ZqZK61kOCwTE745KBxRaZaHLfjB0f7Mc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=UxaYy0VI3ebc+28QZ8W98TuAda8ecnmupVpQxcD8zS4YcfYw0XzcV8Nxwb9rsxluV L4utWcR19OjJ0y9+DqQ7UzQnjOtKD/8eBKmLNSzIOWYrNNmKnE3AgSWxi/1eoEWNlg jrz7xk6aBcQGAsyy5Ar9HmFS3jBDXSZcrE8JOPzyBaEphbitn0TcRX/qQ9+lLr+QC9 tSk99wpc8y7oqKXM6aQ0S87pQq6pUjXmA9kYZPxWaV3s0h9wAfW9jmug9nBMR2K0sC IMge7cP/0bV84T6+2xzh6jEtldS03yiOmXbc01M++JZT9sQsTW/DWqf0MIUTw96/1w nnDsr9mXYSlZg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/YL1UrhgmFigRCUOvwt9ZEOkeyjw
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 18:32:50 -0000

On 12/1/14 5:29 PM, Christian Groves wrote:
> Hello,
>
>>> *a=keywds:*
>>> - Like a=cat:, this was intended for use with SAP. I’m not aware that it
>>> was ever implemented.
>>> - Should likely have a not to say this is obsolete.
>>> - Syntax should likely be: “keywords = text”
>>
>> I'm ok with this if nobody objects.
>
> [CNG] It seems at least someone is using it:
> http://www.gwg.nga.mil/misb/docs/rp/RP1302.pdf

Interesting, and good to know.

	Thanks,
	Paul


From nobody Wed Dec  3 23:42:23 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B041A8931 for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 23:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 4PVF5e2T-sPT for <mmusic@ietfa.amsl.com>; Wed,  3 Dec 2014 23:42:20 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DA21A88CB for <mmusic@ietf.org>; Wed,  3 Dec 2014 23:42:19 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-42-54801059b34c
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 13.B9.04231.95010845; Thu,  4 Dec 2014 08:42:17 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 08:42:17 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Salvatore Loreto <salvatore.loreto@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
Thread-Index: AdAO3vobOG9fyqvZTs6dIUhJ2pZtLAAIUu8AACUwfZA=
Date: Thu, 4 Dec 2014 07:42:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D577E4B@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu>
In-Reply-To: <547F2380.8060706@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyM+JvjW6kQEOIwaJ35hZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWx9vVJxoILQhXv2s4xNjC+5eti5OCQEDCR WHvJrIuRE8gUk7hwbz1bFyMXh5DAEUaJvx+WsUM4ixklJh1/yQTSwCZgIdH9TxukQUQgRmLH tUdsIGFmAXWJq4uDQMLCAnkSp77uYQEJiwjkS1x57wRRbSWxZNdpdhCbRUBF4vnpY2wgNq+A r8TFE2dYQcqFgMrfTuAACXMK6EjsOLeLGcRmBLrs+6k1TCA2s4C4xK0n85kgLhaQWLLnPDOE LSrx8vE/VoinlCSmbU2DKNeRWLD7ExuErS2xbOFrZoitghInZz5hmcAoNgvJ1FlIWmYhaZmF pGUBI8sqRtHi1OLi3HQjY73Uoszk4uL8PL281JJNjMCoObjlt+4OxtWvHQ8xCnAwKvHwGpyr DxFiTSwrrsw9xCjNwaIkzrvo3LxgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwswfFTuM4t yGpvK/r9xrqT3c5zx6ske+8bp/7vidKpvrpor5bY39RjipOmWu3bWMdcw+d4YOZM9j9dD4Os /4m/7biTzxS3bpOtWKRgM/eZC9/Xp3VqzrrIvMbfyYtvU9Qfa48fD79k5nWvy+B6Z/yhb5IV 20rxtki3hufR/GYn1tz9rHpxEoMSS3FGoqEWc1FxIgApXMYiewIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/GRzTQLAe62Wi8JsJYhQbVSdJNmE
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 07:42:22 -0000

Hi,

>>>>>>> Section 5.1:
>>>>>>>
>>>>>>> IMO 5000 is a bad choice for the default port value. It falls in=20
>>>>>>> the middle of the registered port list. It isn't currently=20
>>>>>>> registered (I don't know why) but it potentially could. I suggest=20
>>>>>>> that a number outside of the registered port range
>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535=
 - the largest possible 16 bit number.
>>>>>>
>>>>>> I have no problem to change the default value.
>>>>>>
>>>>>> However, 5000 was defined before I got involved with the draft, so I=
 think it would be good to get some input from Gonzalo and/or Salvatore whe=
ther there was some specific reason for 5000.
>>>>>>
>>>>>> -------------
>>>>>
>>>>> 5000 is the default value the current/available SCTP over TLS are usi=
ng.
>>>>
>>>> just to clarify
>>>> what I meant is that 5000 is the value that as far as I know Firefox=20
>>>> is using in its SCTP over TLS data channel implementation
>>>
>>> AFAIK it is being explicitly specified as 5000, not that there is relia=
nce on a default value of 5000. Changing the default only affects those imp=
lementations depending on the default.
>>>
>>> Also, if those implementations are using different SDP syntax, not conf=
ormant with this version of the draft, then they will need to be changed an=
yway before this change becomes effective.
>>
>> Another option is to not define a default port to begin with, and mandat=
e the usage of the sctp-port attribute.
>>
>> Because, assume you would have two SCTP associations (described using di=
fferent m- lines), both without an sctp-port attribute. You would use the s=
ame SCTP port for both SCTP associations...
>
> Remember - multiple SCTP associations, especially bundled ones, is likely=
 to be a very rare occurrence. The normal case, especially in a bundle, wil=
l be for a single one. In that=20
> case the sctp port is irrelevant. So, optimizing for the common case by h=
aving a default will be one less thing that most people won't have to think=
 about.

People have to think about it anyway - the question is whether they always =
will have to signal it in SDP :)

Personally I don't have any strong opinion - if people want a default port =
value I am happy to add it to the draft. Just gimme a numbah :)

Regards,

Christer


From nobody Thu Dec  4 04:19:48 2014
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1F81A0248 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 04:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 3mtwM-AGYHzV for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 04:19:43 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5A821A0276 for <mmusic@ietf.org>; Thu,  4 Dec 2014 04:19:42 -0800 (PST)
Received: from [130.209.247.112] (port=60617 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1XwVNk-00083g-JD; Thu, 04 Dec 2014 12:19:41 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <547F569B.5040305@alum.mit.edu>
Date: Thu, 4 Dec 2014 12:19:36 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C5CDFED-DB62-4BE9-AE8B-029304309258@csperkins.org>
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu> <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org> <547F569B.5040305@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/JbQcfoB1gkf9yNlVZl72v7z52-0
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 12:19:46 -0000

On 3 Dec 2014, at 18:29, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 12/1/14 6:39 PM, Colin Perkins wrote:
=85snip=85
>>>> *a=3Dfmtp:*
>>>> - The format parameters are MIME media type parameters, and need to
>>>> reflect their syntax.
>>>=20
>>> My understanding is that the values are whatever was in the <fmt> =
field of the associated m-line. What is valid there is defined for each =
<proto> field. For the RTP variants, it is a payload type. For UDP it is =
a media (sub)type. But we can't know in general what if might be for =
other <proto>s, since new ones could be defined in the future.
>>>=20
>>> The m-line syntax defines the fmt as a token. So I figured that the =
same definition should be used here.
>>=20
>> For RTP, you do know explicitly that the <format specific parameters> =
in the a=3Dfmtp: line are MIME media subtype parameters, and need to =
conform to that syntax.
>=20
> We aren't concerned with the <format specific parameters> here.
> (The syntax of those is format specific.:-)
>=20
> We are only concerned with the <fmt> parameter, which replicates one =
from the m-line.
>=20
> For RTP m-lines this will always be an integer. But for the most part =
rtpmap is used instead of fmtp for RTP format specific parameters. There =
is text saying to use fmtp for codec-specific parameters. So I guess if =
fmtp is used with RTP then one would first need to use rtpmap to =
determine the codec, and then use rules defined by that codec to parse =
the format specific parameters.

RTP payload formats and their parameters are defined by a (MIME) media =
type registration. This registration includes a media type, subtype, and =
parameters. The media type (e.g., audio) goes in the <media> part of the =
m=3D line. The media subtype goes in the <encoding name> part of the =
a=3Drtpmap: line. The media parameters go in the <format specific =
parameters> part of the a=3Dfmtp: line. This lets you specify a concrete =
ABNF for the <encoding name> and <format specific parameters> that is =
independent of the codec.=20

--=20
Colin Perkins
https://csperkins.org/





From nobody Thu Dec  4 04:26:16 2014
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65D211A0363 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 04:26:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2] 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 J4oNHHp-x5lN for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 04:26:10 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E084E1A034F for <mmusic@ietf.org>; Thu,  4 Dec 2014 04:26:09 -0800 (PST)
Received: from [130.209.247.112] (port=60690 helo=mangole.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1XwVTw-0000R4-Hs; Thu, 04 Dec 2014 12:26:06 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <547F514C.4020707@alum.mit.edu>
Date: Thu, 4 Dec 2014 12:26:02 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8F1B802-9724-45F4-8182-2F198DFD72A6@csperkins.org>
References: <596DA376-D525-49A2-B260-2BADB38AF2E2@csperkins.org> <547C9B29.9060801@alum.mit.edu> <57F676D2-E980-4359-87B1-BE1D764B095A@csperkins.org> <547F514C.4020707@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/BS11tENHtLiRibFa0si6o748EFs
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 12:26:12 -0000

On 3 Dec 2014, at 18:07, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 12/1/14 6:39 PM, Colin Perkins wrote:
>=20
>>>> *a=3Dcharset:*
>>>> - This is a name from the registry at
>>>> http://www.iana.org/assignments/character-sets/character-sets.xhtml =
and needs to follow that syntax
>>>=20
>>> In this and other cases where what goes in the SDP is a reference to =
something defined in a registry, I am inclined to give a simplified =
syntax that might be a superset of what is permitted in the registry. It =
doesn't matter a whole lot if it allows some invalid values, because =
such names will never be in the registry.
>>>=20
>>> This will help implementers. And when the exact formal definition =
isn't available in ABNF, or is very complex, it can also ease formal =
checking of the SDP ABNF.
>>>=20
>>> Given that explanation, is there anything wrong with what I have?
>>=20
>> Why not reference the correct ABNF from RFC 2978? I don=92t =
understand the desire to put something incorrect here.
>=20
> I've looked again at 2978, and it is less than clear. It says:
>=20
>   Each assigned name MUST uniquely identify a single charset.  All
>   charset names MUST be suitable for use as the value of a MIME =
content
>   type charset parameter and hence MUST conform to MIME parameter =
value
>   syntax.  This applies even if the specific charset being registered
>   is not suitable for use with the "text" media type.
>   ...
>   Finally, charsets being registered for use with the "text" media =
type
>   MUST have a primary name that conforms to the more restrictive =
syntax
>   of the charset field in MIME encoded-words [RFC-2047, RFC-2184] and
>   MIME extended parameter values [RFC-2184].  A combined ABNF
>   definition for such names is as follows:
>=20
>     mime-charset =3D 1*mime-charset-chars
>     ...
>=20
> The final paragraph above seems to say that mime-charset only applies =
for charsets registered for use with "text", but based on the first =
paragraph this syntax could apply for all charset names.
>=20
> And this syntax doesn't apply any limit to how long the names can be, =
while the IANA registry itself says:
>=20
>   The character set names may be up to 40 characters taken from the
>   printable characters of US-ASCII.  However, no distinction is made
>   between use of upper and lower case letters.
>=20
> I based my ABNF on that. But yes, I could reference mime-charset from =
2978.
>=20
> Note also that I currently reference "Preferred MIME Name", but have a =
note asking if I should instead be referencing "Name". These are =
references to column headings in the table in the registry, for lack of =
something better to reference. Looking again at the registry, I think I =
need instead to say:
>=20
> OLD:
>=20
>   The charset specified MUST be one of those registered with IANA, =
such
>   as ISO-8859-1.  The character set identifier is a US-ASCII string =
and
>   MUST be compared against the IANA identifiers using a case-
>   insensitive comparison.  If the identifier is not recognised or not
>   supported, all strings that are affected by it SHOULD be regarded as
>   octet strings.
>=20
> NEW:
>=20
>   The charset specified MUST be one of those registered in the IANA
>   Character Sets registry
>   (http://www.iana.org/assignments/character-sets), such
>   as ISO-8859-1.  The character set identifier is a US-ASCII string =
and
>   MUST be compared against identifiers from the "Name" or "Preferred
>   MIME Name" field of the registry using a case-insensitive
>   comparison.  If the identifier is not recognised or not supported,
>   all strings that are affected by it SHOULD be regarded as octet
>   strings.
>=20
> I think this is needed because the identifiers in the "Preferred MIME =
Name" field are not repeated in the "Name" field, but both are allowed =
to be used in references.

I expect the charset community has common practices in this area. It =
might be worth asking the designated expert for the registry what=92s =
the preferred field to match on, and how to reference the name syntax. =
Alternatively, the APPS area director can likely suggest a reviewer who =
can advise on the right thing to do.

--=20
Colin Perkins
https://csperkins.org/





From nobody Thu Dec  4 07:05:20 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727D71AD425 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 eadJbp3o82Tj for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:05:05 -0800 (PST)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1991AD41E for <mmusic@ietf.org>; Thu,  4 Dec 2014 07:04:50 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id ex7so34973963wid.15 for <mmusic@ietf.org>; Thu, 04 Dec 2014 07:04:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=gW0DXPH5cRG9Wyx7SiRI2Pi6TiLkcNcURa490gUAsTE=; b=vMYkrCd5Iw2a2qmWAWwc5B4V28k+SMbGNwDlHTWC3QKJ4B+fPvqdmfaYtsH91KvVIY 8+MzsEnRFdHfzUwC1ln6wv03LoRWftk+oFE+4sMg503jK8wNRVtPV8K4lrYyCN4NYL9J NJl6+h2n6awtOaJ+a/QTjsov8H0N3NNuHvBLeFks/k5QTFk4YwBI7/t0gK9toQTrylcx oiNCvQJX4tMFqnd5sEB3JRFkLM89gI5bu+lBV7PbH9J8A9FTflTfCw4GFoPxXtDcvwUh Nz3ir0Arxap+/zpsoXFc4B8UbBW7yGu8QbbHpyMbf64ojCojw2fTe10g6ut+8rR1W9tB fxIg==
X-Received: by 10.194.238.40 with SMTP id vh8mr16832499wjc.57.1417705488474; Thu, 04 Dec 2014 07:04:48 -0800 (PST)
Received: from RoniE (bzq-79-180-141-8.red.bezeqint.net. [79.180.141.8]) by mx.google.com with ESMTPSA id p5sm4555905wix.7.2014.12.04.07.04.47 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Dec 2014 07:04:47 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mmusic@ietf.org>
Date: Thu, 4 Dec 2014 17:04:45 +0200
Message-ID: <078d01d00fd3$a503cc30$ef0b6490$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_078E_01D00FE4.688D1160"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdAP0upWnZj92y3WSwqJPDE80Esflw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/pnQAJgU3BYC87m0uSUkHuUBEQFU
Subject: [MMUSIC] Group sttribute FID in draft-ietf-mmusic-sdp-mux-attributes-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 15:05:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_078E_01D00FE4.688D1160
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

According to RFC5888 section 8.5.3 says that "FID MUST NOT be used to group
"m" lines with the same IP address/port."
So should section 8.1 say that FID must not be used for bundled lines, or is
this what Normal and no impact means?
 
Roni

 


------=_NextPart_000_078E_01D00FE4.688D1160
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>According =
to RFC5888 section 8.5.3 says that &#8220;<span =
style=3D'color:black'>FID MUST NOT be used to group &quot;m&quot; lines =
with the same IP address/port.&#8221;<o:p></o:p></span></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>So should section 8.1 say that FID must not be used for bundled lines, =
or is this what Normal and no impact means?<o:p></o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
><o:p>&nbsp;</o:p></span></pre><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Roni<o:p></o:p></span></pre><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_078E_01D00FE4.688D1160--


From nobody Thu Dec  4 07:40:31 2014
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9055E1AD448 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 7kqwPVC3ZYtk for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:40:27 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 984B41AD3F9 for <mmusic@ietf.org>; Thu,  4 Dec 2014 07:40:27 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id p10so17983459pdj.39 for <mmusic@ietf.org>; Thu, 04 Dec 2014 07:40:26 -0800 (PST)
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=2o+PyyryscSQBSFFX3iwYlddL87pIL6L9TIPL3ZfkWU=; b=cRk4Iy7S/5HXyelWocDkWR6nYmp7Aisg5P5KV5ePVxhaWv3Ug29zboXmgWL4wlYYgn Bodb30cpXUjeTz4uuydTGBXFVwAaXVTPSHT8rSOHPc6OK9L7lKsMxuwuRSYRSbd2GYlg 2qaxo+KQVCEKcxsmXLzxhQ+v50GJ72+qPcAeNCfJlHQzjbqfdFzlA6G8lEQINT+FY+Fr MnW8DrFrBN8aKdo6y8CUyxSFnDtySlz1ew88mnx3jYZ8vSaAk2N8xBMaaK05rC2BIKh5 6cCods3VD0oxOggVqn9m703wFE/C+wfY3goBn0IQFu5PJvW5OUhbRguxODZM4tCJYi4x 4tLA==
MIME-Version: 1.0
X-Received: by 10.68.91.37 with SMTP id cb5mr4266520pbb.22.1417707626754; Thu, 04 Dec 2014 07:40:26 -0800 (PST)
Received: by 10.70.60.201 with HTTP; Thu, 4 Dec 2014 07:40:26 -0800 (PST)
In-Reply-To: <078d01d00fd3$a503cc30$ef0b6490$@gmail.com>
References: <078d01d00fd3$a503cc30$ef0b6490$@gmail.com>
Date: Thu, 4 Dec 2014 21:10:26 +0530
Message-ID: <CAMRcRGQb6SD--xgkXykm8Bqm7O+aGk-MOJc7ErPV7OCHf26AUQ@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b676e727cf750050965c7a5
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/dsV0vNnahEBjEjPAgkGUDutTA2U
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Group sttribute FID in draft-ietf-mmusic-sdp-mux-attributes-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 15:40:29 -0000

--047d7b676e727cf750050965c7a5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Roni


   The category NORMAL is used to indicate that the original semantics of
using a=3Dgroup:FID defined in RFC5888 is unchanged under Multiplexing whic=
h
also extends to the section 8.5.3 as well.

Please let me know if you think if it serves the needed clarity or if we
should change the assigned category


Thanks
Suhas


On Thu, Dec 4, 2014 at 8:34 PM, Roni Even <ron.even.tlv@gmail.com> wrote:

> Hi,
>
> According to RFC5888 section 8.5.3 says that =E2=80=9CFID MUST NOT be use=
d to group "m" lines with the same IP address/port.=E2=80=9D
>
> So should section 8.1 say that FID must not be used for bundled lines, or=
 is this what Normal and no impact means?
>
>
>
> Roni
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--047d7b676e727cf750050965c7a5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Roni<div><br></div><div><br></div><div>=C2=A0 =C2=A0=
The category NORMAL is used to indicate that the original semantics of usin=
g a=3Dgroup:FID defined in RFC5888 is unchanged under Multiplexing which al=
so extends to the section 8.5.3 as well.</div><div><br></div><div>Please le=
t me know if you think if it serves the needed clarity or if we should chan=
ge the assigned category</div><div><br></div><div><br></div><div>Thanks<br>=
</div><div>Suhas</div><div><br></div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Thu, Dec 4, 2014 at 8:34 PM, Roni Even <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:ron.even.tlv@gmail.com" target=3D"_blank">=
ron.even.tlv@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"Mso=
Normal">Hi,<u></u><u></u></p><pre><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;">According to RFC5888 section=
 8.5.3 says that =E2=80=9C<span style=3D"color:black">FID MUST NOT be used =
to group &quot;m&quot; lines with the same IP address/port.=E2=80=9D<u></u>=
<u></u></span></span></pre><pre><span style=3D"font-size:11.0pt;font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">So should section =
8.1 say that FID must not be used for bundled lines, or is this what Normal=
 and no impact means?<span class=3D"HOEnZb"><font color=3D"#888888"><u></u>=
<u></u></font></span></span></pre><span class=3D"HOEnZb"><font color=3D"#88=
8888"><pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black"><u></u>=C2=A0<u></u></span></pre><pre><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:black">Roni<u></u><u></u></span></pre><p class=3D"MsoNorma=
l"><u></u>=C2=A0<u></u></p></font></span></div></div><br>__________________=
_____________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div>

--047d7b676e727cf750050965c7a5--


From nobody Thu Dec  4 07:52:18 2014
Return-Path: <Peter.Stevens@bbc.co.uk>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52CF31A1A15 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.311
X-Spam-Level: 
X-Spam-Status: No, score=-6.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_18=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CgWkgtCczG2M for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 07:52:10 -0800 (PST)
Received: from mailout1.mh.bbc.co.uk (mailout1.mh.bbc.co.uk [132.185.144.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6BF81AD464 for <mmusic@ietf.org>; Thu,  4 Dec 2014 07:50:47 -0800 (PST)
Received: from BGB01XI1001.national.core.bbc.co.uk ([10.184.50.51]) by mailout1.mh.bbc.co.uk (8.14.4/8.14.3) with ESMTP id sB4FoiEP013401 for <mmusic@ietf.org>; Thu, 4 Dec 2014 15:50:44 GMT
Received: from BGB01XUD1002.national.core.bbc.co.uk ([169.254.11.150]) by BGB01XI1001.national.core.bbc.co.uk ([10.184.50.51]) with mapi id 14.02.0342.004; Thu, 4 Dec 2014 15:50:44 +0000
From: Peter Stevens <Peter.Stevens@bbc.co.uk>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Comments on ABNF in 4566bis
Thread-Index: AdAP2gjA1e3mwvlTS+KKZFT+KsC/cA==
Date: Thu, 4 Dec 2014 15:50:43 +0000
Message-ID: <2F938AAE444ADB47AFEE6307955A30CE2EB98487@BGB01XUD1002.national.core.bbc.co.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.10.56.249]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Ht-Xp6l7FgVcOx7xnSZedtXdTrU
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 15:52:14 -0000

Hi Paul,

I understand your position as scribe here and to have precise ABNF definiti=
ons is a good thing. Colin's input has highlighted an issue of which we wer=
e aware and backward compatibility and a common usage between the EBU and A=
ES (and probably others) is one of those, so being able to possibly change =
the definition and at the same time keep backward compatibility would be ve=
ry useful.

I've referred this back to both groups and I'm waiting for comments.

Thanks

Peter

________________________________________
From: Paul Kyzivat [pkyzivat@alum.mit.edu]
Sent: 01 December 2014 15:07
To: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis

On 11/27/14 4:12 AM, Peter Stevens wrote:
> Hi,
>
> Colin has commented on this particular attribute:
>
>  > a=3Dptime: and a=3Dmaxptime:
>  > - Are these always integers?
>
> This is a question within the EBU Audio Contribution over IP (ACIP)
> group have noted that the ptime units are not specified within RFC4566.
> If you were not already aware, within the AES, the AES67-2013 AES
> Standard for audio applications of networks - High-performance streaming
> audio-over-ip interoperability, packet time is defined with decimal
> values as follows:
>
> a-ptime <milliseconds>[.<milliseconds decimal>]
> a=3Dmaxptime <milliseconds>[.<milliseconds decimal>]
>
> Do ptime integers possibly conflict with decimal values?
> It is unknown how manufacturers of products define their value of ptime
> internally, such as 20ms, as either an integer of 20 (ms) or as 0.020

I am essentially just a scribe here. The point of working on the ABNF
for these is to be precise where that wasn't previously the case. I made
my best guess as to what was intended. If there are existing uses of
fractional values, then we should specify that.

My concern with this attribute is backward compatibility. If the
definition was extended to allow decimal fractions, would that be
backward compatible with existing implementations that might not expect
to see fractional values?

One possibility would be to allow the use of decimal fractions only when
the fractional part is non-zero. E.g.,

       ptime-value =3D packet-time
       packet-time =3D integer | non-zero-real
       non-zero-real =3D (integer / "0") "." *"0" integer

(Note that in SDP ABNF "integer" never starts with a "0".)

(This definition could also be used for framerate.) It would guarantee
that values that are an integral number of milliseconds never have a
fractional part, which would provide some compatibility with
implementations that expect only integers.

If there are no *existing* uses of fractional values, but a desire to
use them, then another possibility is to define a new attribute.

        Thanks,
        Paul


From nobody Thu Dec  4 08:19:34 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A777E1AD463 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 08:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] 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 5D0xNtRzqpRi for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 08:19:32 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF741A1B9E for <mmusic@ietf.org>; Thu,  4 Dec 2014 08:19:29 -0800 (PST)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-05v.sys.comcast.net with comcast id PUJ61p0022Qkjl901UKUsT; Thu, 04 Dec 2014 16:19:28 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-15v.sys.comcast.net with comcast id PUKT1p00d3Ge9ey01UKUlc; Thu, 04 Dec 2014 16:19:28 +0000
Message-ID: <5480898F.5020700@alum.mit.edu>
Date: Thu, 04 Dec 2014 11:19:27 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <2F938AAE444ADB47AFEE6307955A30CE2EB98487@BGB01XUD1002.national.core.bbc.co.uk>
In-Reply-To: <2F938AAE444ADB47AFEE6307955A30CE2EB98487@BGB01XUD1002.national.core.bbc.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417709968; bh=/zK77hMpaveSXfeAnYzDjIzXPJstPmhKv7eMVdp3Ir8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=nqBFnQf/YiX7EyUqoBRo5Kt4EPsL0ma5+xZbAqOrhnpAsYSDJP5fPAx/RRdpYyvG8 aykP5ouHTrQpemM9DQnirls4qGEZv2m6ARuhTGCxqPxsyjc4z7j48cJjvO+BSdO7g8 vMtGW3a83jB4/b2pNDGEzDT+9LcxWlsvDNH+8mpKgeNdMeehslAB57AM64CzQABXdk bQifdLjVrMvRHQsDoS+V2M92x08GVjQ1LaUAzYYzmM0Dbon2eC0eRWLf5YxsvQVwoO eyuUz43gaZr4fNrsdlbwPOFQlkX03kHupaa23dSMrei3r9kqgKQ0I56XYG7RBaa2xL lzSkJIH2SAKOA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/AfYLBq-4q4TTakFwwjsA9Y6ZKW0
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 16:19:33 -0000

Peter,

On 12/4/14 10:50 AM, Peter Stevens wrote:
> Hi Paul,
>
> I understand your position as scribe here and to have precise ABNF definitions is a good thing. Colin's input has highlighted an issue of which we were aware and backward compatibility and a common usage between the EBU and AES (and probably others) is one of those, so being able to possibly change the definition and at the same time keep backward compatibility would be very useful.
>
> I've referred this back to both groups and I'm waiting for comments.

Your case is one of doing extensions with backward compatibility.
That is related to, but slightly different from, trying to formally 
specify a previously informal syntax that may or may not have included 
decimal fractions. Depending on what we find currently deployed, we may 
need different solutions for each parameter.

I do expect that we will want the same definition for ptime and 
maxptime, but the answer for the quality parameter might be different.

For each, I see three candidate syntaxes to consider:

1) only whole-numbers
2) optional fractional part
3) optional fractional part only when the fraction is non-zero

Going with (3) will help ensure that an implementation that supports 
fractions will interwork with implementations that only support 
whole-numbers as long as only integral values are used. But it's hard to 
know whether that solves a real problem.

Since you are defining new usage, I presume you could work with either 
(2) or (3), right?

	Thanks,
	Paul

> Thanks
>
> Peter
>
> ________________________________________
> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
> Sent: 01 December 2014 15:07
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
>
> On 11/27/14 4:12 AM, Peter Stevens wrote:
>> Hi,
>>
>> Colin has commented on this particular attribute:
>>
>>   > a=ptime: and a=maxptime:
>>   > - Are these always integers?
>>
>> This is a question within the EBU Audio Contribution over IP (ACIP)
>> group have noted that the ptime units are not specified within RFC4566.
>> If you were not already aware, within the AES, the AES67-2013 AES
>> Standard for audio applications of networks - High-performance streaming
>> audio-over-ip interoperability, packet time is defined with decimal
>> values as follows:
>>
>> a-ptime <milliseconds>[.<milliseconds decimal>]
>> a=maxptime <milliseconds>[.<milliseconds decimal>]
>>
>> Do ptime integers possibly conflict with decimal values?
>> It is unknown how manufacturers of products define their value of ptime
>> internally, such as 20ms, as either an integer of 20 (ms) or as 0.020
>
> I am essentially just a scribe here. The point of working on the ABNF
> for these is to be precise where that wasn't previously the case. I made
> my best guess as to what was intended. If there are existing uses of
> fractional values, then we should specify that.
>
> My concern with this attribute is backward compatibility. If the
> definition was extended to allow decimal fractions, would that be
> backward compatible with existing implementations that might not expect
> to see fractional values?
>
> One possibility would be to allow the use of decimal fractions only when
> the fractional part is non-zero. E.g.,
>
>         ptime-value = packet-time
>         packet-time = integer | non-zero-real
>         non-zero-real = (integer / "0") "." *"0" integer
>
> (Note that in SDP ABNF "integer" never starts with a "0".)
>
> (This definition could also be used for framerate.) It would guarantee
> that values that are an integral number of milliseconds never have a
> fractional part, which would provide some compatibility with
> implementations that expect only integers.
>
> If there are no *existing* uses of fractional values, but a desire to
> use them, then another possibility is to define a new attribute.
>
>          Thanks,
>          Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Dec  4 08:22:17 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E58E31AD464 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 08:22:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_18=0.6, SPF_SOFTFAIL=0.665] 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 uK4nlinVPUTl for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 08:22:12 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D1231AD48B for <mmusic@ietf.org>; Thu,  4 Dec 2014 08:22:08 -0800 (PST)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-08v.sys.comcast.net with comcast id PUMo1p0052GyhjZ01UN749; Thu, 04 Dec 2014 16:22:07 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-09v.sys.comcast.net with comcast id PUN71p0063Ge9ey01UN7We; Thu, 04 Dec 2014 16:22:07 +0000
Message-ID: <54808A2F.7090100@alum.mit.edu>
Date: Thu, 04 Dec 2014 11:22:07 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <2F938AAE444ADB47AFEE6307955A30CE2EB98487@BGB01XUD1002.national.core.bbc.co.uk>
In-Reply-To: <2F938AAE444ADB47AFEE6307955A30CE2EB98487@BGB01XUD1002.national.core.bbc.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417710127; bh=eJuEuPz9O9ynR1al53yfWjTusKKLGEy1qUzJkDpTlxQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=dKgV4zbrT+9XoERSWaVB8XeFIliiOxutebqpoRJRXfXiJOblbA1oUyErynSt5SNQf ZBNbRnwkrMfhzNpykPrIJZKb89GuQrisZcTMynx2tB3y1ptgWpUzFieB/4XHDDV1k+ oEEafUqU420gbo84sG2eIY1BIhjQGs2Ws2mf2vRkCEcvQoJZv7y70UKbRvfbJkhNEk zltvh+ewcoSLB3vxgqIW+VhRxsoHimqgNHPCdOQ3PmOwnOHPKQxumXG1w0PIGJ6X4x j1L89Gc2STW8gXQOqfYHSrTDhry3o4Bk8ro1TDQp3Su3eADhRDUQRZChoGRzITmIcB 9xZkD+O7Z+wVw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/QPPdm9s9SHRGNy2xI5bCE-eskxE
Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 16:22:16 -0000

One more thing:

These cases where questions arise about the syntax of attributes are 
precisely why this work needed to be done. If forces us to confront 
issues we didn't know we had.

	Thanks,
	Paul

On 12/4/14 10:50 AM, Peter Stevens wrote:
> Hi Paul,
>
> I understand your position as scribe here and to have precise ABNF definitions is a good thing. Colin's input has highlighted an issue of which we were aware and backward compatibility and a common usage between the EBU and AES (and probably others) is one of those, so being able to possibly change the definition and at the same time keep backward compatibility would be very useful.
>
> I've referred this back to both groups and I'm waiting for comments.
>
> Thanks
>
> Peter
>
> ________________________________________
> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
> Sent: 01 December 2014 15:07
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] Comments on ABNF in 4566bis
>
> On 11/27/14 4:12 AM, Peter Stevens wrote:
>> Hi,
>>
>> Colin has commented on this particular attribute:
>>
>>   > a=ptime: and a=maxptime:
>>   > - Are these always integers?
>>
>> This is a question within the EBU Audio Contribution over IP (ACIP)
>> group have noted that the ptime units are not specified within RFC4566.
>> If you were not already aware, within the AES, the AES67-2013 AES
>> Standard for audio applications of networks - High-performance streaming
>> audio-over-ip interoperability, packet time is defined with decimal
>> values as follows:
>>
>> a-ptime <milliseconds>[.<milliseconds decimal>]
>> a=maxptime <milliseconds>[.<milliseconds decimal>]
>>
>> Do ptime integers possibly conflict with decimal values?
>> It is unknown how manufacturers of products define their value of ptime
>> internally, such as 20ms, as either an integer of 20 (ms) or as 0.020
>
> I am essentially just a scribe here. The point of working on the ABNF
> for these is to be precise where that wasn't previously the case. I made
> my best guess as to what was intended. If there are existing uses of
> fractional values, then we should specify that.
>
> My concern with this attribute is backward compatibility. If the
> definition was extended to allow decimal fractions, would that be
> backward compatible with existing implementations that might not expect
> to see fractional values?
>
> One possibility would be to allow the use of decimal fractions only when
> the fractional part is non-zero. E.g.,
>
>         ptime-value = packet-time
>         packet-time = integer | non-zero-real
>         non-zero-real = (integer / "0") "." *"0" integer
>
> (Note that in SDP ABNF "integer" never starts with a "0".)
>
> (This definition could also be used for framerate.) It would guarantee
> that values that are an integral number of milliseconds never have a
> fractional part, which would provide some compatibility with
> implementations that expect only integers.
>
> If there are no *existing* uses of fractional values, but a desire to
> use them, then another possibility is to define a new attribute.
>
>          Thanks,
>          Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Dec  4 09:09:37 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E701A1B92 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 09:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 kFP8Jsgsb77j for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 09:09:35 -0800 (PST)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 077B11A1B81 for <mmusic@ietf.org>; Thu,  4 Dec 2014 09:09:34 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-03v.sys.comcast.net with comcast id PV7w1p0062N9P4d01V9aZb; Thu, 04 Dec 2014 17:09:34 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-13v.sys.comcast.net with comcast id PV9Z1p00S3Ge9ey01V9Z3l; Thu, 04 Dec 2014 17:09:34 +0000
Message-ID: <5480954D.8020701@alum.mit.edu>
Date: Thu, 04 Dec 2014 12:09:33 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D577E4B@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D577E4B@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417712974; bh=7cNI5M5yf1SiRFu5qaz2p3/kLXUVx1PWYUWtXAbAjPk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=amXixRjGbbq4CPKSGlSIyCTJbCnKgSOjgiUm98zg++9Jp7ZfD1uitRnthhxQmqapI 4Hi+jd+4xAIJkZ51FdKZAmf3F4Mife2bguE8Zua4Z+G1x40BEw2TXexOvglU0SN/JI f++NoY7FPT1UlEzJMMs2JmSyRLT+9f6SJxIutFju4xwb6oN9+QofLBNLxHwXmPEXPE uibeYai7hedaIjjOzAItB87NUaq+NVzrezszap0unKHNZe46fBAX4c8Xy/p1lU3lk9 q1MwSb8kc3Vj0qcGo7Oxk+L71crgCcTcBt15f/24sIH6Np4or1s6v9g/Sr3UR7sJls n+seYD+btJkKA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/-TBRn25FJmzd1jzSzlDskev6bdw
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 17:09:36 -0000

On 12/4/14 2:42 AM, Christer Holmberg wrote:
> Hi,
>
>>>>>>>> Section 5.1:
>>>>>>>>
>>>>>>>> IMO 5000 is a bad choice for the default port value. It falls in
>>>>>>>> the middle of the registered port list. It isn't currently
>>>>>>>> registered (I don't know why) but it potentially could. I suggest
>>>>>>>> that a number outside of the registered port range
>>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>>>>>>>
>>>>>>> I have no problem to change the default value.
>>>>>>>
>>>>>>> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>>>>>>>
>>>>>>> -------------
>>>>>>
>>>>>> 5000 is the default value the current/available SCTP over TLS are using.
>>>>>
>>>>> just to clarify
>>>>> what I meant is that 5000 is the value that as far as I know Firefox
>>>>> is using in its SCTP over TLS data channel implementation
>>>>
>>>> AFAIK it is being explicitly specified as 5000, not that there is reliance on a default value of 5000. Changing the default only affects those implementations depending on the default.
>>>>
>>>> Also, if those implementations are using different SDP syntax, not conformant with this version of the draft, then they will need to be changed anyway before this change becomes effective.
>>>
>>> Another option is to not define a default port to begin with, and mandate the usage of the sctp-port attribute.
>>>
>>> Because, assume you would have two SCTP associations (described using different m- lines), both without an sctp-port attribute. You would use the same SCTP port for both SCTP associations...
>>
>> Remember - multiple SCTP associations, especially bundled ones, is likely to be a very rare occurrence. The normal case, especially in a bundle, will be for a single one. In that
>> case the sctp port is irrelevant. So, optimizing for the common case by having a default will be one less thing that most people won't have to think about.
>
> People have to think about it anyway - the question is whether they always will have to signal it in SDP :)
>
> Personally I don't have any strong opinion - if people want a default port value I am happy to add it to the draft. Just gimme a numbah :)

Most people won't need to think about it at all.

	Thanks,
	Paul


From nobody Thu Dec  4 17:31:52 2014
Return-Path: <dwing@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB821A8AD0 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 17:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.611
X-Spam-Level: 
X-Spam-Status: No, score=-13.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 S2Xkbm1obkC1 for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 17:31:43 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C723A1A8A7C for <mmusic@ietf.org>; Thu,  4 Dec 2014 17:31:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3154; q=dns/txt; s=iport; t=1417743103; x=1418952703; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=0j89fY0LTrXlkLFyUaMNmIPYFgXf6eMCv+vBBCFW62M=; b=FT3qVZF7mgYm3g18HL6uF+sbCXnE/cUbGywn1Bk1NXYSihvgOlZtjnwA 7QdlX5qoqqwIO2ytw63p2SeojAya2rWJi7LnUuTgalopYHJyFbdTqesO8 Z73pZkWm275+1oENckyDzC4lTkfR0/Nl7B725QpFSchNls7swqkn9v6ZQ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAGUKgVStJA2L/2dsb2JhbABZDoJ4UljGPAqFRE8CgRoWAQEBAQF9hAIBAQEDAQEBATc0CwULCw4KLicwBgESiDIJDdcAAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSQHDMHgyGBFQWFVoRXjyuGb4xOgjCBAGAeMIJDAQEB
X-IronPort-AV: E=Sophos;i="5.07,519,1413244800"; d="scan'208";a="102790927"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-1.cisco.com with ESMTP; 05 Dec 2014 01:31:42 +0000
Received: from [10.24.194.44] ([10.24.194.44]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id sB51VfBZ010568 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Dec 2014 01:31:42 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <547F2380.8060706@alum.mit.edu>
Date: Thu, 4 Dec 2014 17:31:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/utG8G8qFwZM9SJxmwg7vZWmFYCg
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 01:31:48 -0000

On Dec 3, 2014, at 6:51 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 12/3/14 5:00 AM, Christer Holmberg wrote:
>> Hi,
>>=20
>>>>>>> Section 5.1:
>>>>>>>=20
>>>>>>> IMO 5000 is a bad choice for the default port value. It falls in
>>>>>>> the middle of the registered port list. It isn't currently
>>>>>>> registered (I don't know why) but it potentially could. I =
suggest
>>>>>>> that a number outside of the registered port range
>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest =
65535 - the largest possible 16 bit number.
>>>>>>=20
>>>>>> I have no problem to change the default value.
>>>>>>=20
>>>>>> However, 5000 was defined before I got involved with the draft, =
so I think it would be good to get some input from Gonzalo and/or =
Salvatore whether there was some specific reason for 5000.
>>>>>>=20
>>>>>> -------------
>>>>>=20
>>>>> 5000 is the default value the current/available SCTP over TLS are =
using.
>>>>=20
>>>> just to clarify
>>>> what I meant is that 5000 is the value that as far as I know =
Firefox
>>>> is using in its SCTP over TLS data channel implementation
>>>=20
>>> AFAIK it is being explicitly specified as 5000, not that there is =
reliance on a default value of 5000. Changing the default only affects =
those implementations depending on the default.
>>>=20
>>> Also, if those implementations are using different SDP syntax, not =
conformant with this version of the draft, then they will need to be =
changed anyway before this change becomes effective.
>>=20
>> Another option is to not define a default port to begin with, and =
mandate the usage of the sctp-port attribute.
>>=20
>> Because, assume you would have two SCTP associations (described using =
different m- lines), both without an sctp-port attribute. You would use =
the same SCTP port for both SCTP associations...
>=20
> Remember - multiple SCTP associations, especially bundled ones, is =
likely to be a very rare occurrence.

We shouldn't have a default port number for SCTP; this re-invents the =
mistakes of "RTCP =3D RTP port + 1" that necessitated the late =
standardization of a=3Drtcp which is *still* not reliably signaled by =
SIP endpoints (fortunately WebRTC is requiring it, I believe).  A fixed =
port number doesn't work with NAPT, A+P, or all the other stuff that =
mucks with port numbers.   Yes, I know SCTP dreams of NAPTs that don't =
rewrite ports, but even that dream doesn't work well if everything is =
trying to use the same port number.

I propose eliminating the sentence:
  "If the SDP sctp-port attribute is not present, the default value is
   5000."
and require signaling the SCTP port number.

-d



> The normal case, especially in a bundle, will be for a single one. In =
that case the sctp port is irrelevant. So, optimizing for the common =
case by having a default will be one less thing that most people won't =
have to think about.
>=20
> 	Thanks,
> 	Paul
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu Dec  4 17:32:23 2014
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A944D1A8A7D for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 17:32:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6] 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 lrO6H6wtkaGV for <mmusic@ietfa.amsl.com>; Thu,  4 Dec 2014 17:32:09 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD2301A8A7C for <mmusic@ietf.org>; Thu,  4 Dec 2014 17:32:08 -0800 (PST)
Received: from ppp118-209-33-128.lns20.mel4.internode.on.net ([118.209.33.128]:54707 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <Christian.Groves@nteczone.com>) id 1XwhkY-0006x9-F9 for mmusic@ietf.org; Fri, 05 Dec 2014 12:32:02 +1100
Message-ID: <54810B09.1080200@nteczone.com>
Date: Fri, 05 Dec 2014 12:31:53 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <20141126140229.31432.80074.idtracker@ietfa.amsl.com>
In-Reply-To: <20141126140229.31432.80074.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/PU9dSKi8kSSBS1KS_9BxIns6NtQ
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 01:32:10 -0000

Hello Suhas,

A few comments:

1) With regards to 5.55 ITU-T-Rec.Q1970 I think mux category "Not 
Recommended" or "Special" would probably be more appropriate. a=ipbcp is 
used to signal the version and type of a SDP based IPBCP message. It's 
used in a BICC (ITU-T Q.1901) environment limited to a single media 
payload. The use of IPBCP messages for multiplexed transport would 
require updates to several Q.19xx series Recommendations.

Also the heading title should be changed to align with the other ITU-T 
related heading, i.e. from "ITU-T-Rec.Q1970" to "ITU-T Q.1970".

2) 5.48 ATM SDP - I still not quite sure about the criteria for 
assigning the mux category. The text indicates that "For all adaptation 
types (AAL1, AAL2 and AAL5), bearer connections may be bundled into a 
single media group" however the BUNDLE draft is only for nettypes IN and 
addresstypes "IP4" or "IP6". So I wouldn't assign mux category "NORMAL" 
because some extra work would be needed to define how BUNDLE would be 
used for the ATM SDP parameters.  If multiplexing was applied then would 
the attributes related to the underlying ATM bearer need to be identical 
i.e. attributes from 5.6.1/RFC3108? Given the age and that these are not 
IP related, i'd be inclined to mark them all as NOT RECOMMENDED.

3) 5.56 H.248.15 - FYI there's some work underway in the ITU-T SG16 on 
the support of multiplexing based on BUNDLE in H.248.STGROUP 
(http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip).

Regards, Christian

On 27/11/2014 1:02 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.
>
>          Title           : A Framework for SDP Attributes when Multiplexing
>          Author          : Suhas Nandakumar
> 	Filename        : draft-ietf-mmusic-sdp-mux-attributes-05.txt
> 	Pages           : 88
> 	Date            : 2014-11-26
>
> Abstract:
>     The Session Description Protocol (SDP) provides mechanisms to
>     describe attributes of multimedia sessions and of individual media
>     streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
>     multimedia session.  In the RTCWEB WG, there is a need to use a
>     single 5-tuple for sending and receiving media associated with
>     multiple media descriptions ("m=" lines).  Such a requirement has
>     raised concerns over the semantic implications of the SDP attributes
>     associated with the RTP Media Streams multiplexed over a single
>     underlying transport layer flow.
>
>     The scope of this specification is to provide a framework for
>     analyzing the multiplexing characteristics of SDP attributes.  This
>     specification also categorizes the existing SDP attributes based on
>     the framework described herein.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-05
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-05
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Fri Dec  5 01:15:49 2014
Return-Path: <rachel.huang@huawei.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9966E1ACE1E; Fri,  5 Dec 2014 01:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.911
X-Spam-Level: 
X-Spam-Status: No, score=-3.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qam92lW8CL7v; Fri,  5 Dec 2014 01:15:43 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C34DD1A0075; Fri,  5 Dec 2014 01:15:42 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BMK05226; Fri, 05 Dec 2014 09:15:41 +0000 (GMT)
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 5 Dec 2014 09:15:03 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Fri, 5 Dec 2014 17:14:59 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: =?utf-8?B?8J+Uk0RhbiBXaW5n?= <dwing@cisco.com>, "draft-ietf-avtext-splicing-notification@tools.ietf.org" <draft-ietf-avtext-splicing-notification@tools.ietf.org>, "avtext@ietf.org" <avtext@ietf.org>
Thread-Topic: SDP directorate review of draft-ietf-avtext-splicing-notification-00
Thread-Index: AQHQDyGz8OOGrsZyvkuiRzIp1VJYHZyAuSHA
Date: Fri, 5 Dec 2014 09:14:58 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB8627A5B0@nkgeml501-mbs.china.huawei.com>
References: <86C3445F-F8D6-4208-8D42-A16B218B146B@cisco.com>
In-Reply-To: <86C3445F-F8D6-4208-8D42-A16B218B146B@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.214.42.186]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/r0Q8PJeQ1Vfp2bpvU0eFR1PlOnE
Cc: mmusic <mmusic@ietf.org>
Subject: [MMUSIC] =?utf-8?b?562U5aSNOiBTRFAgZGlyZWN0b3JhdGUgcmV2aWV3IG9m?= =?utf-8?q?_draft-ietf-avtext-splicing-notification-00?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 09:15:45 -0000

SGkgRGFuLA0KDQpUaGFuayB5b3UgZm9yIHRoZSBjYXJlZnVsIHJldmlldy4gVGhlc2UgdHdvIGlz
c3VlcyB3aWxsIGJlIGFkZHJlc3NlZCBpbiB0aGUgbmV3IHZlcnNpb24uDQoNCkJSLA0KUmFjaGVs
DQoNCi0tLS0t6YKu5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujog8J+Uk0RhbiBXaW5nIFttYWls
dG86ZHdpbmdAY2lzY28uY29tXSANCuWPkemAgeaXtumXtDogMjAxNOW5tDEy5pyINOaXpSAxOjUx
DQrmlLbku7bkuro6IGRyYWZ0LWlldGYtYXZ0ZXh0LXNwbGljaW5nLW5vdGlmaWNhdGlvbkB0b29s
cy5pZXRmLm9yZzsgYXZ0ZXh0QGlldGYub3JnDQrmioTpgIE6IG1tdXNpYw0K5Li76aKYOiBTRFAg
ZGlyZWN0b3JhdGUgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LXNwbGljaW5nLW5vdGlmaWNh
dGlvbi0wMA0KDQpTRFAgZGlyZWN0b3JhdGUgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LXNw
bGljaW5nLW5vdGlmaWNhdGlvbi0wMCwgRGFuIFdpbmcsIDItRGVjLTIwMTQuDQoNCjEuICB0aGUg
U0RQIGluIGRyYWZ0LWlldGYtYXZ0ZXh0LXNwbGljaW5nLW5vdGlmaWNhdGlvbiBpcyByZS11c2lu
ZyBGSUQgZnJvbSBSRkM1ODg4LCBidXQgaXMgdXNpbmcgZGlmZmVyZW50IHNlbWFudGljcy4gIEhv
dyBkb2VzIGEgcmVjZWl2ZXIga25vdyBpZiB0aGUgRklEIHNlbWFudGljcyBhcmUgUkZDNTg4OCdz
IHNlbWFudGljcyBvciBhcmUgZHJhZnQtaWV0Zi1hdnRleHQtc3BsaWNpbmctbm90aWZpY2F0aW9u
J3Mgc2VtYW50aWNzPyAgU2VlbXMgd2Ugd291bGQgYmVuZWZpdCBmcm9tIGFuIGluZGljYXRpb24g
b2YgdGhlIHNlbWFudGljcyBpbiB0aGUgU0RQLCBwZXJoYXBzIGEgbmV3IHNlc3Npb24tbGV2ZWwg
YXR0cmlidXRlIChlLmcuLCAiYT1zcGxpY2luZyIpIG9yIHBlcmhhcHMgbm90IHJlLXVzZSBhPWdy
b3VwOkZJRCBhbmQgaW5zdGVhZCBpbnZlbnQgaXRzIG93biBncm91cGluZyBmb3Igc3BsaWNpbmcg
KGUuZy4sIGE9Z3JvdXA6U1BMSUNFKS4NCg0KMi4gU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgc2F5
czoNCg0KICAgSW4gdGhlIFNlY3VyZSBSZWFsLXRpbWUgVHJhbnNwb3J0IFByb3RvY29sICANCiAg
IChTUlRQKVtSRkMzNzExXSwgUlRQIGhlYWRlciBleHRlbnNpb25zIGFyZSBhdXRoZW50aWNhdGVk
IGJ1dCBub3QgIA0KICAgZW5jcnlwdGVkLiAgQSBtYWxpY2lvdXMgZW5kcG9pbnQgY291bGQgY2hv
b3NlIHRvIHNldCB0aGUgdmFsdWVzIGluICANCiAgIHRoaXMgaGVhZGVyIGV4dGVuc2lvbiBmYWxz
ZWx5LCBzbyBhcyB0byBmYWxzZWx5IGNsYWltIHRoZSBzcGxpY2luZyAgDQogICB0aW1lLg0KDQpB
IG1hbGljaW91cyBlbmRwb2ludCB3b3VsZCBuZWVkIHRoZSBTUlRQIGtleSB0byBkbyB0aGF0LCBj
b3JyZWN0PyAgVGhlIEktRCBzaG91bGQgbWVudGlvbiB0aGF0IHRoZSBtYWxpY2lvdXMgZW5kcG9p
bnQgbmVlZHMgdGhlIFNSVFAga2V5LiAgDQoNCkFsc28sIGF1Y2ggYSBtYWxpY2lvdXMgZW5kcG9p
bnQgKHdpdGggcG9zc2Vzc2lvbiBvZiB0aGUgU1JUUCBrZXkpIGNvdWxkIGFsc28gY2F1c2Ugc3Bs
aWNpbmcgb2YgYW55IGFyYml0cmFyeSBjb250ZW50IGl0IHdpc2hlcywgbGlrZSBhIFJpY2sgQXN0
bGV5IHZpZGVvLCB3aGljaCBpcyBhIGRpZmZlcmVudCBhdHRhY2sgdGhhdCBpc24ndCBqdXN0IGFn
YWluc3QgdGhlICp0aW1lKi4gIEktRCBzaG91bGQgbWVudGlvbiB0aGF0LiAgSSBkb24ndCB0aGlu
ayBlaXRoZXIgb2YgdGhlc2UgYXJlIHNpZ25pZmljYW50LCBhcyB0aGUgc2FtZSBwcm9ibGVtIGV4
aXN0cyB3aXRob3V0IHNwbGljaW5nLg0KDQoNCg0KTml0czogIA0KDQoxLiBUaGUgU0RQIGluIFNl
Y3Rpb24gNiBoYXMgc3B1cmlvdXMgd2hpdGVzcGFjZSwgZm9yIGV4YW1wbGUgYSBzcGFjZSBhZnRl
ciAibT0iLCB3aGljaCBpcyBwcm9oaWJpdGVkIGJ5IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9yZmM0NTY2I3BhZ2UtOCAoIldoaXRlc3BhY2UgTVVTVCBOT1QgYmUgdXNlZCBvbiBlaXRoZXIg
c2lkZSBvZiB0aGUgIj0iIHNpZ24iKS4gIE15IHJlYWQgb2YgdGhlIGdyb3VwaW5nIFJGQyAoUkZD
NTg4OCkgaXMgdGhhdCBpdCBkb2Vzbid0IGFsbG93IHRoZSBzcHVyaW91cyB3aGl0ZXNwYWNlIGFm
dGVyICJhPW1pZDoiLCBlaXRoZXIuICBUaGUgU0RQIGluIFNlY3Rpb24gNiBpcyB1bmNsZWFyIGlm
IGl0IGlzIG5vcm1hdGl2ZSBvciBhIG5vbi1ub3JtYXRpdmUgZXhhbXBsZS4NCg0KMi4gU2VjdGlv
biAzLjEgdGl0bGUsICJFeHRlblRpb24iIC0+ICJFeHRlblNpb24iDQoNCjMuIFNlY3Rpb24gNCB0
aXRsZSwgIlJlZHVpbmciIC0+ICJSZWR1Q2luZyINCg0KNC4gU2VjdGlvbiA2LA0KT0xEOg0KICAg
QnV0IGF0DQogICBhIHBhcnRpY3VsYXIgcG9pbnQgaW4gdGltZSwgdGhlIG1peGVyIG9ubHkgc2Vs
ZWN0cyBvbmUgc3RyZWFtIGFuZA0KICAgb3V0cHV0IHRoZSBjb250ZW50IGZyb20gdGhlIGNob3Nl
biBzdHJlYW0gdG8gdGhlIGRvd25zdHJlYW0NCiAgIHJlY2VpdmVycy4NCk5FVzoNCiAgIEJ1dCBh
dA0KICAgYSBwYXJ0aWN1bGFyIHBvaW50IGluIHRpbWUsIHRoZSBtaXhlciBvbmx5IHNlbGVjdHMg
b25lIHN0cmVhbSBhbmQNCiAgIG91dHB1dHMgdGhlIGNvbnRlbnQgZnJvbSB0aGUgY2hvc2VuIHN0
cmVhbSB0byB0aGUgZG93bnN0cmVhbSAuLi4uLi4uLi5eDQogICByZWNlaXZlcnMuDQoNCjUuIGlk
bml0cyBoYWQgYSBjb3VwbGUgb2YgY29tcGxhaW50cywgaHR0cHM6Ly90b29scy5pZXRmLm9yZy90
b29scy9pZG5pdHMvd2Vic2VydmljZQ0KDQotZA0KDQo=


From nobody Fri Dec  5 03:06:15 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C10D1ACE50; Fri,  5 Dec 2014 03:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 KRsuHkGVat5K; Fri,  5 Dec 2014 03:06:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF1BE1ACE51; Fri,  5 Dec 2014 03:06:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141205110609.14805.97490.idtracker@ietfa.amsl.com>
Date: Fri, 05 Dec 2014 03:06:09 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yBv-B91QLWmh_PRaqHeFcG1sdQs
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sctp-sdp-09.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 11:06:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Salvatore Loreto
                          Gonzalo Camarillo
	Filename        : draft-ietf-mmusic-sctp-sdp-09.txt
	Pages           : 18
	Date            : 2014-12-05

Abstract:
   SCTP (Stream Control Transmission Protocol) is a transport protocol
   used to establish associations between two endpoints.

   This specification describes how to describe SCTP associations using
   the Session Description Protocol (SDP), and defines the following new
   SDP Media Description protocol identifiers (proto values):'SCTP',
   'SCTP/DTLS' and 'DTLS/SCTP'.

   The specification also describes how to use the new proto values
   together with the SDP Offer/Answer mechanism in order to negotiate
   and establish SCTP associations, and how to indicate the SCTP
   application usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sctp-sdp/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sctp-sdp-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Dec  5 03:09:49 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DBF41ACE3D for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 03:09:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 NtXOt_lXRboW for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 03:09:45 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF66E1ACE3A for <mmusic@ietf.org>; Fri,  5 Dec 2014 03:09:44 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-b7-54819276d108
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id DD.14.04231.67291845; Fri,  5 Dec 2014 12:09:42 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 12:09:42 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-sctp-sdp-09
Thread-Index: AdAQe4PRZ5KN2jGmS4+m3D2oNYEQiw==
Date: Fri, 5 Dec 2014 11:09:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D57D53E@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D57D53EESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+JvjW7ZpMYQg/9/DC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujO4Le5gLbolVnNlxiKWBcZJIFyMnh4SAicSyw9tYIGwxiQv3 1rN1MXJxCAkcYZS4cGUiK4SzmFHi0pGJQBkODjYBC4nuf9ogDSIC6hJf9/Ywg9jCApYS+06s Y4aI20k0HW5khLD1JN5dhbBZBFQk9px8zQZi8wr4Slx5+RjMZgRa/P3UGiYQm1lAXOLWk/lM EAcJSCzZc54ZwhaVePn4HyuErSjx8dU+Roj6fIneG2vZIWYKSpyc+YRlAqPQLCSjZiEpm4Wk DCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9iFC1OLS7OTTcy1kstykwuLs7P08tLLdnE CIyJg1t+6+5gXP3a8RCjAAejEg/vBvnGECHWxLLiytxDjNIcLErivIvOzQsWEkhPLEnNTk0t SC2KLyrNSS0+xMjEwSnVwCim9/qm2IZKgUqfB+U19X0qLSn5By4uyu06kJK58TpvPNumx5Gl NzLNU5tWs+f9Cb8804qv/Vy9380oLuOrD4wnb93j23+2c15PnIjfkY27GKd4vdx2c+OJL5y9 pxMkLE6+Sl50je+otkfYh/Sy2Bsr2K7zMVo5C9dMjEpYnThRbAmz19K7YkosxRmJhlrMRcWJ AKODTQVqAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/hJcv7XdOIv1SBzBpCy_wCgoEpH0
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-09
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 11:09:48 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D57D53EESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi SCTP lovers,

As we have done good progress, especially regarding the Offer/Answer impact=
s on DTLS, I have submitted a new version (-09) of the SCTP-SDP, where I tr=
y to capture everything.

Happy weekend reading! :)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D57D53EESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi SCTP lovers,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">As we have done good progress, especially regarding =
the Offer/Answer impacts on DTLS, I have submitted a new version (-09) of t=
he SCTP-SDP, where I try to capture everything.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Happy weekend reading! :)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D57D53EESESSMB209erics_--


From nobody Fri Dec  5 03:31:56 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 031201ACE27 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 03:31:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 gEXXvt2Bk7Tb for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 03:31:53 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2383C1A01CB for <mmusic@ietf.org>; Fri,  5 Dec 2014 03:31:52 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-cc-548197a6ef7c
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 05.C5.24955.6A791845; Fri,  5 Dec 2014 12:31:51 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 12:31:50 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Outcome of proto value discussion?
Thread-Index: AdAQfug5j1OpJasqTfqcelLd0hCC3g==
Date: Fri, 5 Dec 2014 11:31:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D57D5FA@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D57D5FAESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+Jvje7y6Y0hBgfeclhMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGcd2LGEq+CNWcbtnFnsD4wGRLkZODgkBE4lTP/4yQdhiEhfu rWfrYuTiEBI4wiix8+gDRpCEkMBiRon/E4K7GDk42AQsJLr/aYOERQTUJb7u7WEGsYUFtCVu XZ7CBBE3kJj86jAzhK0nsf1bG9gYFgEVid+P7rCD2LwCvhKXfl9nA7EZgfZ+P7UGrJdZQFzi 1pP5UPcISCzZc54ZwhaVePn4HyuErSjx8dU+Roj6fIn9624yQ8wUlDg58wnLBEahWUhGzUJS NgtJGURcR2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FKFqcWpyUm25krJdalJlcXJyfp5eX WrKJERgRB7f8Vt3BePmN4yFGAQ5GJR7eDfKNIUKsiWXFlbmHGKU5WJTEeReemxcsJJCeWJKa nZpakFoUX1Sak1p8iJGJg1OqgVE0IOydi+HsSg+/jDeLpb/f+bPTOJjdxuZ29UGPBaXKL/g/ 9LUqmfBPWThfcGqQu9yS/4aue4VLtAtcExpOmgsplS7mEV2rdOy80oktwtJu+8xSHQ2Zebo8 Y3793rRT/eqCCX89ZsSksPbmT57GJbR/teJ9x9mHEp5vfzrtz2Z+5rbIxWUmWUosxRmJhlrM RcWJANFPFy9pAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/WuYbeyVxCKQoGzrJQ9lwxSP_y2s
Subject: [MMUSIC] Outcome of proto value discussion?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 11:31:55 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D57D5FAESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Was there any outcome of the proto value discussion?

For example, for SCTP-SDP, are we going to use "DTLS/SCTP", or "UDP/DTLS/SC=
TP" and "TCP/DTLS/SCTP", or "UDP/TLS/SCTP" and "TCP/TLS/SCTP", or what?

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D57D5FAESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Was there any outcome of the proto value discussion?=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For example, for SCTP-SDP, are we going to use &#822=
0;DTLS/SCTP&#8221;, or &#8220;UDP/DTLS/SCTP&#8221; and &#8220;TCP/DTLS/SCTP=
&#8221;, or &#8220;UDP/TLS/SCTP&#8221; and &#8220;TCP/TLS/SCTP&#8221;, or w=
hat?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D57D5FAESESSMB209erics_--


From nobody Fri Dec  5 05:56:20 2014
Return-Path: <thomas.stach@unify.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3D71A19EC for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 05:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 kI7qvkO-_oy9 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 05:56:16 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 10CB61A0A85 for <mmusic@ietf.org>; Fri,  5 Dec 2014 05:56:16 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 947A01EB8522; Fri,  5 Dec 2014 14:56:14 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.125]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 14:56:14 +0100
From: "Stach, Thomas" <thomas.stach@unify.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: bundle-only attribute with non-zero port value?
Thread-Index: AdAOLuRFHIaCbMzPRi+fiBvvfsNEKQCX5n4Q
Date: Fri, 5 Dec 2014 13:56:13 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE121E25E79C@MCHP04MSX.global-ad.net>
References: <7594FB04B1934943A5C02806D1A2204B1D56E9BF@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D56E9BF@ESESSMB209.ericsson.se>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_F81CEE99482EFE438DAE2A652361EE121E25E79CMCHP04MSXglobal_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/RUbX683Nz4f28TQpemJBCE_3ZlM
Subject: Re: [MMUSIC] BUNDLE: bundle-only attribute with non-zero port value?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 13:56:19 -0000

--_000_F81CEE99482EFE438DAE2A652361EE121E25E79CMCHP04MSXglobal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Christer,

I don't think there is a use case for the bundle-only attribute with a non-=
zero port value that you can't achieve with port=3D0.

Regards
Thomas


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: Dienstag, 2. Dezember 2014 13:55
To: mmusic@ietf.org
Subject: [MMUSIC] BUNDLE: bundle-only attribute with non-zero port value?

Hi,

Currently  BUNDLE allows usage of the SDP bundle-only attribute in any offe=
r - even if the associated m- line contains a negotiated BUNDLE address.

As we know, the purpose of the attribute is to ensure that the answerer rej=
ects the associated m- line if the answerer does not support BUNDLE, or if =
the answerer does not keep the m- line within the BUNDLE group.

Once the BUNDLE address have been negotiated, the offerer can ensure the sa=
me thing by assigning the BUNDLE address to an m- line. If the answerer doe=
s not want to keep it within the BUNDLE group, it will reject the m- line (=
per BUNDLE procedures).

So, the question is: is there a need to use the bundle-attribute in m- line=
s with a non-zero port value?
It would simply the procedures by specifying that the attribute can only be=
 used together with port zero.

Regards,

Christer

--_000_F81CEE99482EFE438DAE2A652361EE121E25E79CMCHP04MSXglobal_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"DE" style=3D"color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal">I don&#8217;t think there is a use case for the bund=
le-only attribute with a non-zero port value that you can&#8217;t achieve w=
ith port=3D0.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Thomas<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mmusic [=
mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> Dienstag, 2. Dezember 2014 13:55<br>
<b>To:</b> mmusic@ietf.org<br>
<b>Subject:</b> [MMUSIC] BUNDLE: bundle-only attribute with non-zero port v=
alue?<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Currently&nbsp; BUNDLE allows usage of the SDP bundl=
e-only attribute in any offer &#8211; even if the associated m- line contai=
ns a negotiated BUNDLE address.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As we know, the purpose of the attribute is to ensur=
e that the answerer rejects the associated m- line if the answerer does not=
 support BUNDLE, or if the answerer does not keep the m- line within the BU=
NDLE group.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Once the BUNDLE address have been negotiated, the of=
ferer can ensure the same thing by assigning the BUNDLE address to an m- li=
ne. If the answerer does not want to keep it within the BUNDLE group, it wi=
ll reject the m- line (per BUNDLE
 procedures).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, the question is: is there a need to use the bund=
le-attribute in m- lines with a non-zero port value?
<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal">It would simply the procedures by specifying that th=
e attribute can only be used together with port zero.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_F81CEE99482EFE438DAE2A652361EE121E25E79CMCHP04MSXglobal_--


From nobody Fri Dec  5 07:33:19 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76FC21ACEB2 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 07:33:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.335
X-Spam-Level: 
X-Spam-Status: No, score=-0.335 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, MIME_8BIT_HEADER=0.3, SPF_SOFTFAIL=0.665] 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 tH6IIgj0LkWP for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 07:33:17 -0800 (PST)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 653D81A899D for <mmusic@ietf.org>; Fri,  5 Dec 2014 07:33:17 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-04v.sys.comcast.net with comcast id PrYw1p0032LrikM01rZGYh; Fri, 05 Dec 2014 15:33:16 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-12v.sys.comcast.net with comcast id PrZF1p00X3Ge9ey01rZG6z; Fri, 05 Dec 2014 15:33:16 +0000
Message-ID: <5481D03B.2000607@alum.mit.edu>
Date: Fri, 05 Dec 2014 10:33:15 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?8J+Uk0RhbiBXaW5n?= <dwing@cisco.com>,  Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu> <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com>
In-Reply-To: <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417793596; bh=m/wlm1u8PZbx+CAb0JdRXtCMPN4yazLaBrwrTNqzXTM=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=HOv6Hcldshmg+TND4v5KHv4l6GVCkOdh1REp06RGfMI8GNQkKEZNo9+uFUdIJJxiD T2CM0XqShG5x9DrvJ0nASrBSnbCiEQD+niE6ukAuG7tYncAREtcR8Fcz9vIDg6iGRE B82F+WbhlO/wWfry1HIxxEdLe/fUbcE0DIqxA7og7u6kjOhElmHbx1nUFfW0OpfIVh Ya93upsKJ4Gso93D7pinFrUw8DjIVQf1IRCYNIP0oj4UTUfQib07O/U6GtTpQ5nfhV mHPNBcEBleifSDCwDzV/c5rTnmQ4WFlPx3nY5ieSp8g1SsqamLB3+gYw6ALc/+3IB2 WcU1dZxynZpMg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ySbcqbhaBFlBNF5TFemvdOZBGw4
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 15:33:18 -0000

Dan,

On 12/4/14 8:31 PM, đź”“Dan Wing wrote:
>
> On Dec 3, 2014, at 6:51 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> On 12/3/14 5:00 AM, Christer Holmberg wrote:
>>> Hi,
>>>
>>>>>>>> Section 5.1:
>>>>>>>>
>>>>>>>> IMO 5000 is a bad choice for the default port value. It falls in
>>>>>>>> the middle of the registered port list. It isn't currently
>>>>>>>> registered (I don't know why) but it potentially could. I suggest
>>>>>>>> that a number outside of the registered port range
>>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>>>>>>>
>>>>>>> I have no problem to change the default value.
>>>>>>>
>>>>>>> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>>>>>>>
>>>>>>> -------------
>>>>>>
>>>>>> 5000 is the default value the current/available SCTP over TLS are using.
>>>>>
>>>>> just to clarify
>>>>> what I meant is that 5000 is the value that as far as I know Firefox
>>>>> is using in its SCTP over TLS data channel implementation
>>>>
>>>> AFAIK it is being explicitly specified as 5000, not that there is reliance on a default value of 5000. Changing the default only affects those implementations depending on the default.
>>>>
>>>> Also, if those implementations are using different SDP syntax, not conformant with this version of the draft, then they will need to be changed anyway before this change becomes effective.
>>>
>>> Another option is to not define a default port to begin with, and mandate the usage of the sctp-port attribute.
>>>
>>> Because, assume you would have two SCTP associations (described using different m- lines), both without an sctp-port attribute. You would use the same SCTP port for both SCTP associations...
>>
>> Remember - multiple SCTP associations, especially bundled ones, is likely to be a very rare occurrence.
>
> We shouldn't have a default port number for SCTP; this re-invents the mistakes of "RTCP = RTP port + 1" that necessitated the late standardization of a=rtcp which is *still* not reliably signaled by SIP endpoints (fortunately WebRTC is requiring it, I believe).  A fixed port number doesn't work with NAPT, A+P, or all the other stuff that mucks with port numbers.   Yes, I know SCTP dreams of NAPTs that don't rewrite ports, but even that dream doesn't work well if everything is trying to use the same port number.

Remember, this is only for the case where SCTP is being carried over 
another transport that has a port number.

And this isn't analogous to RTCP. In that case there are two independent 
streams. That isn't the case here.

And for those cases where multiple SCTP ports are needed, defining the 
attribute from the start means there aren't the backward compatibility 
issues that there were for a=rtcp.

	Thanks,
	Paul

> I propose eliminating the sentence:
>    "If the SDP sctp-port attribute is not present, the default value is
>     5000."
> and require signaling the SCTP port number.


From nobody Fri Dec  5 09:18:00 2014
Return-Path: <dwing@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6171B1A03F9 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 09:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.611
X-Spam-Level: 
X-Spam-Status: No, score=-13.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_14=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 DbfdtxeTk7YN for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 09:17:56 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D50C31A03A8 for <mmusic@ietf.org>; Fri,  5 Dec 2014 09:17:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3535; q=dns/txt; s=iport; t=1417799875; x=1419009475; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=8MMnIpaEGckA1uDFqhkQxXQlE4qUeYZWlHQ9XXTxeyo=; b=NpvFHmW0erFjwqvfzcLsLcSd2rhfhlBzXdmxMRCsym7p1Vh0y7T1NUkP ivWoslaONLuNRZL/pXxLOr2i+q6sa2XwCH9s/rF82nG5gO0/BgNQZmiwa UcmDbxJNd0nGijp86mjS3br01FUtazrTf8SdBZaG7YU2QJGQDgw3l/pob o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnAFACHogVStJV2d/2dsb2JhbABZDoJ4gSqDBcleAoEeFgEBAQEBfYQCAQEBAwEjRBIFCwkCDgoCAiYCAlcGE4gyCaMunGaWZQEBAQEBAQEBAQEBAQEBAQEBAQEZgSiOdDMHgm8ygRUFhViEWIMsjAOGb4xQgjCBAGAeMIJDAQEB
X-IronPort-AV: E=Sophos;i="5.07,522,1413244800"; d="scan'208";a="103059126"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-4.cisco.com with ESMTP; 05 Dec 2014 17:17:55 +0000
Received: from [10.24.227.43] ([10.24.227.43]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id sB5HH3QR019366 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Dec 2014 17:17:54 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <5481D03B.2000607@alum.mit.edu>
Date: Fri, 5 Dec 2014 09:17:53 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F9079B7-37DA-4102-BFB1-7D1F73FD6C89@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu> <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com> <5481D03B.2000607@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Q2VC_cPyYhIgzYV5dfEHtlEDWcs
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 17:17:57 -0000

On Dec 5, 2014, at 7:33 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> Dan,
>=20
> On 12/4/14 8:31 PM, =F0=9F=94=93Dan Wing wrote:
>>=20
>> On Dec 3, 2014, at 6:51 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>>=20
>>> On 12/3/14 5:00 AM, Christer Holmberg wrote:
>>>> Hi,
>>>>=20
>>>>>>>>> Section 5.1:
>>>>>>>>>=20
>>>>>>>>> IMO 5000 is a bad choice for the default port value. It falls =
in
>>>>>>>>> the middle of the registered port list. It isn't currently
>>>>>>>>> registered (I don't know why) but it potentially could. I =
suggest
>>>>>>>>> that a number outside of the registered port range
>>>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest =
65535 - the largest possible 16 bit number.
>>>>>>>>=20
>>>>>>>> I have no problem to change the default value.
>>>>>>>>=20
>>>>>>>> However, 5000 was defined before I got involved with the draft, =
so I think it would be good to get some input from Gonzalo and/or =
Salvatore whether there was some specific reason for 5000.
>>>>>>>>=20
>>>>>>>> -------------
>>>>>>>=20
>>>>>>> 5000 is the default value the current/available SCTP over TLS =
are using.
>>>>>>=20
>>>>>> just to clarify
>>>>>> what I meant is that 5000 is the value that as far as I know =
Firefox
>>>>>> is using in its SCTP over TLS data channel implementation
>>>>>=20
>>>>> AFAIK it is being explicitly specified as 5000, not that there is =
reliance on a default value of 5000. Changing the default only affects =
those implementations depending on the default.
>>>>>=20
>>>>> Also, if those implementations are using different SDP syntax, not =
conformant with this version of the draft, then they will need to be =
changed anyway before this change becomes effective.
>>>>=20
>>>> Another option is to not define a default port to begin with, and =
mandate the usage of the sctp-port attribute.
>>>>=20
>>>> Because, assume you would have two SCTP associations (described =
using different m- lines), both without an sctp-port attribute. You =
would use the same SCTP port for both SCTP associations...
>>>=20
>>> Remember - multiple SCTP associations, especially bundled ones, is =
likely to be a very rare occurrence.
>>=20
>> We shouldn't have a default port number for SCTP; this re-invents the =
mistakes of "RTCP =3D RTP port + 1" that necessitated the late =
standardization of a=3Drtcp which is *still* not reliably signaled by =
SIP endpoints (fortunately WebRTC is requiring it, I believe). A fixed =
port number doesn't work with NAPT, A+P, or all the other stuff that =
mucks with port numbers.   Yes, I know SCTP dreams of NAPTs that don't =
rewrite ports, but even that dream doesn't work well if everything is =
trying to use the same port number.
>=20
> Remember, this is only for the case where SCTP is being carried over =
another transport that has a port number.

I had missed that.

I do agree IANA registration of the port seems a good idea.

-d


>=20
> And this isn't analogous to RTCP. In that case there are two =
independent streams. That isn't the case here.
>=20
> And for those cases where multiple SCTP ports are needed, defining the =
attribute from the start means there aren't the backward compatibility =
issues that there were for a=3Drtcp.
>=20
> 	Thanks,
> 	Paul
>=20
>> I propose eliminating the sentence:
>>   "If the SDP sctp-port attribute is not present, the default value =
is
>>    5000."
>> and require signaling the SCTP port number.


From nobody Fri Dec  5 09:53:58 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB121AD4B6 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 09:53:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.335
X-Spam-Level: 
X-Spam-Status: No, score=-0.335 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, MIME_8BIT_HEADER=0.3, SPF_SOFTFAIL=0.665] 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 Nk8Ere53v3z4 for <mmusic@ietfa.amsl.com>; Fri,  5 Dec 2014 09:53:50 -0800 (PST)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 825ED1AD4B8 for <mmusic@ietf.org>; Fri,  5 Dec 2014 09:53:48 -0800 (PST)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-10v.sys.comcast.net with comcast id Ptpg1p0042PT3Qt01ttnBn; Fri, 05 Dec 2014 17:53:47 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-14v.sys.comcast.net with comcast id Pttm1p00Z3Ge9ey01ttmfr; Fri, 05 Dec 2014 17:53:47 +0000
Message-ID: <5481F12A.1020101@alum.mit.edu>
Date: Fri, 05 Dec 2014 12:53:46 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?8J+Uk0RhbiBXaW5n?= <dwing@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu> <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com> <5481D03B.2000607@alum.mit.edu> <6F9079B7-37DA-4102-BFB1-7D1F73FD6C89@cisco.com>
In-Reply-To: <6F9079B7-37DA-4102-BFB1-7D1F73FD6C89@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1417802027; bh=pVUMktIDUgQlp2UMbC0eI3yb/hxvlHKy6+UwUEmV9F4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=dCxuJim2x3pGjHSW/JnQ74IKEHQx770WUbgjtcc1ZH98YWVazF7H/L+zfres0tQi9 8LEWDnj8CbsFYOWjF4apB0V5AkHRBw+PWiImYeLjOijHtB48pNosrLj7LZiWzsqM3q OWDzR2WGP+jbiQOV/2JN8brH+TKu+5UFattEiMTukfPr+mdTIVl2R8AquxIVpRZeou qV19Z7fRzoOjM4ewbLOR8/tlYpr9Kds91ZcC5HwdDYlJCelmDC31P3T2lxcUbGlRJc QB1wze5fUD25ftACpXGaLF3SLSKK3TNtUJoRGKxenC7PymisDZ8IsFgwNHVqmTB0Gj +SJYLupy3iQgQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/eHfCirprZAxv6j2yGsC_ewrureY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 17:53:52 -0000

On 12/5/14 12:17 PM, đź”“Dan Wing wrote:
>
> On Dec 5, 2014, at 7:33 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> Dan,
>>
>> On 12/4/14 8:31 PM, đź”“Dan Wing wrote:
>>>
>>> On Dec 3, 2014, at 6:51 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>>
>>>> On 12/3/14 5:00 AM, Christer Holmberg wrote:
>>>>> Hi,
>>>>>
>>>>>>>>>> Section 5.1:
>>>>>>>>>>
>>>>>>>>>> IMO 5000 is a bad choice for the default port value. It falls in
>>>>>>>>>> the middle of the registered port list. It isn't currently
>>>>>>>>>> registered (I don't know why) but it potentially could. I suggest
>>>>>>>>>> that a number outside of the registered port range
>>>>>>>>>> (>49151) would be safest. To avoid being arbitrary, I suggest 65535 - the largest possible 16 bit number.
>>>>>>>>>
>>>>>>>>> I have no problem to change the default value.
>>>>>>>>>
>>>>>>>>> However, 5000 was defined before I got involved with the draft, so I think it would be good to get some input from Gonzalo and/or Salvatore whether there was some specific reason for 5000.
>>>>>>>>>
>>>>>>>>> -------------
>>>>>>>>
>>>>>>>> 5000 is the default value the current/available SCTP over TLS are using.
>>>>>>>
>>>>>>> just to clarify
>>>>>>> what I meant is that 5000 is the value that as far as I know Firefox
>>>>>>> is using in its SCTP over TLS data channel implementation
>>>>>>
>>>>>> AFAIK it is being explicitly specified as 5000, not that there is reliance on a default value of 5000. Changing the default only affects those implementations depending on the default.
>>>>>>
>>>>>> Also, if those implementations are using different SDP syntax, not conformant with this version of the draft, then they will need to be changed anyway before this change becomes effective.
>>>>>
>>>>> Another option is to not define a default port to begin with, and mandate the usage of the sctp-port attribute.
>>>>>
>>>>> Because, assume you would have two SCTP associations (described using different m- lines), both without an sctp-port attribute. You would use the same SCTP port for both SCTP associations...
>>>>
>>>> Remember - multiple SCTP associations, especially bundled ones, is likely to be a very rare occurrence.
>>>
>>> We shouldn't have a default port number for SCTP; this re-invents the mistakes of "RTCP = RTP port + 1" that necessitated the late standardization of a=rtcp which is *still* not reliably signaled by SIP endpoints (fortunately WebRTC is requiring it, I believe). A fixed port number doesn't work with NAPT, A+P, or all the other stuff that mucks with port numbers.   Yes, I know SCTP dreams of NAPTs that don't rewrite ports, but even that dream doesn't work well if everything is trying to use the same port number.
>>
>> Remember, this is only for the case where SCTP is being carried over another transport that has a port number.
>
> I had missed that.
>
> I do agree IANA registration of the port seems a good idea.

The current default (5000) is a currently unassigned value in the range 
reserved for (registered) user ports. That seems wrong. I am proposing 
to use a number (65535) from the dynamic port number range as the default.

I agree that another possibility would be to register a port for the 
purpose. (Potentially this port could be in the system ports range. The 
restriction on use of system ports doesn't apply when the protocol is 
implemented in application space over another transport.)

I just find it a little easier to go with a dynamic port.

	Thanks
	Paul


From nobody Mon Dec  8 03:26:34 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6781A01EC; Mon,  8 Dec 2014 03:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 jJPVjRySFa6B; Mon,  8 Dec 2014 03:26:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 349DB1A0181; Mon,  8 Dec 2014 03:26:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141208112629.10438.22407.idtracker@ietfa.amsl.com>
Date: Mon, 08 Dec 2014 03:26:29 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Dj1pRsRGB6IUW-r1qtzm5j3O5Bw
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-13.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 11:26:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-13.txt
	Pages           : 48
	Date            : 2014-12-08

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, associated with multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  This
   specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264 to
   allow an answerer to assign a non-zero port value to an "m=" line in
   an SDP answer, even if the "m=" line in the associated SDP offer
   contained a zero port value.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   RTCP source description (SDES) item and a new RTP header extension
   that provides an additional way to do this correlation by using them
   to carry a value that associates the RTP/RTCP packets with a specific
   media description.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-bundle-negotiation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-bundle-negotiation-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Dec  8 03:29:21 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D771A0183 for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 03:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 B0Y9iWxI14_5 for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 03:29:17 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A6AC1A0174 for <mmusic@ietf.org>; Mon,  8 Dec 2014 03:29:16 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-6a-54858b8b7e67
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 32.B1.24955.B8B85845; Mon,  8 Dec 2014 12:29:15 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0195.001; Mon, 8 Dec 2014 12:29:14 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: raft-ietf-mmusic-sdp-bundle-negotiation-13
Thread-Index: AdAS2emyOSN4nPzlQpm6wsU4jGibqg==
Date: Mon, 8 Dec 2014 11:29:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5843C3@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D5843C3ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+JvjW53d2uIwbEmQYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEr48ddn4KTkhUXp31mamA8KdbFyMkhIWAi0bd3DTuELSZx4d56 NhBbSOAIo8St82ldjFxA9mJGiTfdjaxdjBwcbAIWEt3/tEFqRATUJb7u7WEGsYUF3CQ2/m5i gYh7S/x5+o4JwtaTeDNtEZjNIqAi0fO3C6yeV8BXYsXePWA2I9De76fWgNUwC4hL3Hoynwni HgGJJXvOM0PYohIvH/9jhbCVJH5suMQCUZ8vsXr/MRaImYISJ2c+YZnAKDQLyahZSMpmISmD iOtILNj9iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxhFi1OLk3LTjYz1Uosyk4uL8/P08lJLNjEC 4+Hglt+qOxgvv3E8xCjAwajEw2sg0hoixJpYVlyZe4hRmoNFSZx34bl5wUIC6YklqdmpqQWp RfFFpTmpxYcYmTg4pRoYueJ9m1L6oqzOclRevHJWvfmYemDZlOUrmO0nGLSwsG+8dDv5x/06 2zvd87UDefK2WoYwHWGMvpfuqOlwd/nd+EWmD3ZVTOMKeP9x+tmW6sv9ul6JH4JV262cBD93 zGXsmsr7m+OOrtQkz3110fFv96kmF79nflVUwqxq9O7hxzfpKQvWbS5RYinOSDTUYi4qTgQA U1b2q2gCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/L1tJAS6qkpayokoMOGoRmjApUO8
Subject: [MMUSIC] Draft new version: raft-ietf-mmusic-sdp-bundle-negotiation-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 11:29:19 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D5843C3ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi BUNDLE lovers,

I have submitted a new version (-13) of BUNDLE, based on WGLC comments etc.

There are a number of technical and editorial modifications, so I encourage=
 people to read the document (especially if you have previously provided re=
view comments).

Note that the SDP 'bundle-only' attribute is now defined only with a zero p=
ort value.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D5843C3ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi BUNDLE lovers,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I have submitted a new version (-13) of BUNDLE, base=
d on WGLC comments etc.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are a number of technical and editorial modifi=
cations, so I encourage people to read the document (especially if you have=
 previously provided review comments).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Note that the SDP &#8216;bundle-only&#8217; attribut=
e is now defined only with a zero port value.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D5843C3ESESSMB209erics_--


From nobody Mon Dec  8 04:24:00 2014
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1361A1B56 for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 04:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, SPF_PASS=-0.001] 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 kDFCARkGzxus for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 04:23:53 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 059071A1B8E for <mmusic@ietf.org>; Mon,  8 Dec 2014 04:23:53 -0800 (PST)
Received: by mail-pd0-f176.google.com with SMTP id y10so5095080pdj.7 for <mmusic@ietf.org>; Mon, 08 Dec 2014 04:23:52 -0800 (PST)
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=KPkovqueTipx2i3HB/gKMSxEgy17tpcPtUszVTCKe/U=; b=YfIwLfLbQ++KXoCPE8kh0qus8NA1py70ax24g7dL0LVIsQDYHnukR0S4IE0nHESiCc CNN/13wMaH1V6v5ijzn5F+56YidVq641Z2QtnMRegse/XcENJJraLZbeZPn1YtlgS1sz Dxs1xHqo8yLEijkxEaWhlu1UaAyvqUr22ofTHX8hxfxeUC/UY5+Vv+36RebzTkxqaY2Y SkreSUSUsdBrxCzczI2BgnaElwFkZlageRlQSq314b5vGiDbQwuqAvcJC/5uzs3Bw5jB Xt/lcJgWFYH2T6v0CcstWOYF63ArHiL2EmPceRRDwYRbEeU83f1FOLkcLGVxSBYBS8re ba8Q==
MIME-Version: 1.0
X-Received: by 10.70.48.166 with SMTP id m6mr21066671pdn.22.1418041432264; Mon, 08 Dec 2014 04:23:52 -0800 (PST)
Received: by 10.70.60.201 with HTTP; Mon, 8 Dec 2014 04:23:52 -0800 (PST)
In-Reply-To: <54810B09.1080200@nteczone.com>
References: <20141126140229.31432.80074.idtracker@ietfa.amsl.com> <54810B09.1080200@nteczone.com>
Date: Mon, 8 Dec 2014 17:53:52 +0530
Message-ID: <CAMRcRGQpvySMa9c=3B1tPqxTRRJ4PnibfbbdRVvCG=_cjFXCGQ@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christian Groves <Christian.Groves@nteczone.com>
Content-Type: multipart/alternative; boundary=089e0102ed86d8d7be0509b37fa1
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yYF3vbwcnxTOyf0XCotNrJi4-QA
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 12:23:55 -0000

--089e0102ed86d8d7be0509b37fa1
Content-Type: text/plain; charset=UTF-8

Hello Christian

  Please see inline for the responses.

   Also,  a question to chairs,  should I produce a newer version of the
document to reflect the changes below or wait till we end the last call.

Please advice.

Thanks
Suhas

On Fri, Dec 5, 2014 at 7:01 AM, Christian Groves <
Christian.Groves@nteczone.com> wrote:

> Hello Suhas,
>
> A few comments:
>
> 1) With regards to 5.55 ITU-T-Rec.Q1970 I think mux category "Not
> Recommended" or "Special" would probably be more appropriate. a=ipbcp is
> used to signal the version and type of a SDP based IPBCP message. It's used
> in a BICC (ITU-T Q.1901) environment limited to a single media payload. The
> use of IPBCP messages for multiplexed transport would require updates to
> several Q.19xx series Recommendations.
>

[Suhas]  I am not an expert in this area and from limited reading of the
the ITU Spec it felt like ipbcp is used just to signify IPBCP version
number (as pointed by you) and thus felt as far as multiplexing is
concerned , the category NORMAL for this attributes makes sense. Given the
single media payload restriction above, It seems SPECIAL category is more
appropriate and provides the implementors an option to consult the spec
before making multiplexing decisions.

I can update the draft to reflect the same.

Also the heading title should be changed to align with the other ITU-T
> related heading, i.e. from "ITU-T-Rec.Q1970" to "ITU-T Q.1970".
>

[Suhas] Thanks, will update in the next version.

>
> 2) 5.48 ATM SDP - I still not quite sure about the criteria for assigning
> the mux category. The text indicates that "For all adaptation types (AAL1,
> AAL2 and AAL5), bearer connections may be bundled into a single media
> group" however the BUNDLE draft is only for nettypes IN and addresstypes
> "IP4" or "IP6". So I wouldn't assign mux category "NORMAL" because some
> extra work would be needed to define how BUNDLE would be used for the ATM
> SDP parameters.  If multiplexing was applied then would the attributes
> related to the underlying ATM bearer need to be identical i.e. attributes
> from 5.6.1/RFC3108? Given the age and that these are not IP related, i'd be
> inclined to mark them all as NOT RECOMMENDED.
>

[Suhas] The notes associated with the section 5.48 in this draft was added
to mention that RFC3018 doesn't address cases where ATM serves as a
low-level transport pipe for IP packets which in turn might carry
multiplexed media streams.  I am open to move it to NOT RECOMMENDED given
your analysis.

>
> 3) 5.56 H.248.15 - FYI there's some work underway in the ITU-T SG16 on the
> support of multiplexing based on BUNDLE in H.248.STGROUP (
> http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip).
>
> Regards, Christian
>
>
> On 27/11/2014 1:02 AM, internet-drafts@ietf.org wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>   This draft is a work item of the Multiparty Multimedia Session Control
>> Working Group of the IETF.
>>
>>          Title           : A Framework for SDP Attributes when
>> Multiplexing
>>          Author          : Suhas Nandakumar
>>         Filename        : draft-ietf-mmusic-sdp-mux-attributes-05.txt
>>         Pages           : 88
>>         Date            : 2014-11-26
>>
>> Abstract:
>>     The Session Description Protocol (SDP) provides mechanisms to
>>     describe attributes of multimedia sessions and of individual media
>>     streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
>>     multimedia session.  In the RTCWEB WG, there is a need to use a
>>     single 5-tuple for sending and receiving media associated with
>>     multiple media descriptions ("m=" lines).  Such a requirement has
>>     raised concerns over the semantic implications of the SDP attributes
>>     associated with the RTP Media Streams multiplexed over a single
>>     underlying transport layer flow.
>>
>>     The scope of this specification is to provide a framework for
>>     analyzing the multiplexing characteristics of SDP attributes.  This
>>     specification also categorizes the existing SDP attributes based on
>>     the framework described herein.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-05
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-05
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--089e0102ed86d8d7be0509b37fa1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Christian<div><br></div><div>=C2=A0 Please see inlin=
e for the responses.=C2=A0</div><div><br></div><div>=C2=A0 =C2=A0Also, =C2=
=A0a question to chairs, =C2=A0should I produce a newer version of the docu=
ment to reflect the changes below or wait till we end the last call.</div><=
div><br></div><div>Please advice.</div><div><br></div><div>Thanks</div><div=
>Suhas</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fr=
i, Dec 5, 2014 at 7:01 AM, Christian Groves <span dir=3D"ltr">&lt;<a href=
=3D"mailto:Christian.Groves@nteczone.com" target=3D"_blank">Christian.Grove=
s@nteczone.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex">Hello Suhas,<br>
<br>
A few comments:<br>
<br>
1) With regards to 5.55 ITU-T-Rec.Q1970 I think mux category &quot;Not Reco=
mmended&quot; or &quot;Special&quot; would probably be more appropriate. a=
=3Dipbcp is used to signal the version and type of a SDP based IPBCP messag=
e. It&#39;s used in a BICC (ITU-T Q.1901) environment limited to a single m=
edia payload. The use of IPBCP messages for multiplexed transport would req=
uire updates to several Q.19xx series Recommendations.<br></blockquote><div=
>=C2=A0</div><div>[Suhas] =C2=A0I am not an expert in this area and from li=
mited reading of the the ITU Spec it felt like ipbcp is used just to signif=
y IPBCP version number (as pointed by you) and thus felt as far as multiple=
xing is concerned , the category NORMAL for this attributes makes sense. Gi=
ven the single media payload restriction above, It seems SPECIAL category i=
s more appropriate and provides the implementors an option to consult the s=
pec before making multiplexing decisions.</div><div><br></div><div>I can up=
date the draft to reflect the same.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also the heading title should be changed to align with the other ITU-T rela=
ted heading, i.e. from &quot;ITU-T-Rec.Q1970&quot; to &quot;ITU-T Q.1970&qu=
ot;.<br></blockquote><div>=C2=A0</div><div>[Suhas] Thanks, will update in t=
he next version.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex">
<br>
2) 5.48 ATM SDP - I still not quite sure about the criteria for assigning t=
he mux category. The text indicates that &quot;For all adaptation types (AA=
L1, AAL2 and AAL5), bearer connections may be bundled into a single media g=
roup&quot; however the BUNDLE draft is only for nettypes IN and addresstype=
s &quot;IP4&quot; or &quot;IP6&quot;. So I wouldn&#39;t assign mux category=
 &quot;NORMAL&quot; because some extra work would be needed to define how B=
UNDLE would be used for the ATM SDP parameters.=C2=A0 If multiplexing was a=
pplied then would the attributes related to the underlying ATM bearer need =
to be identical i.e. attributes from 5.6.1/RFC3108? Given the age and that =
these are not IP related, i&#39;d be inclined to mark them all as NOT RECOM=
MENDED.<br></blockquote><div><br></div><div>[Suhas] The notes associated wi=
th the section 5.48 in this draft was added to mention that RFC3018 doesn&#=
39;t address=C2=A0<span style=3D"color:rgb(0,0,0);font-size:1em">cases wher=
e ATM serves as a low-level transport pipe for IP packets which in turn mig=
ht carry multiplexed media streams.=C2=A0 I am open to move it to NOT RECOM=
MENDED given your analysis.</span></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rg=
b(204,204,204);border-left-style:solid;padding-left:1ex"><br>
3) 5.56 H.248.15 - FYI there&#39;s some work underway in the ITU-T SG16 on =
the support of multiplexing based on BUNDLE in H.248.STGROUP (<a href=3D"ht=
tp://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip" target=3D=
"_blank">http://wftp3.itu.int/av-arch/<u></u>avc-site/2013-2016/1411_Seo/<u=
></u>TD-14.zip</a>).<br>
<br>
Regards, Christian<div class=3D""><div class=3D"h5"><br>
<br>
On 27/11/2014 1:02 AM, <a href=3D"mailto:internet-drafts@ietf.org" target=
=3D"_blank">internet-drafts@ietf.org</a> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0 This draft is a work item of the Multiparty Multimedia Session Contr=
ol Working Group of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: A Framework for SDP Attributes when Multiplexing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
: Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-sdp-mux-<u></u>attributes-05.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 88<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2014-11-26<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0 The Session Description Protocol (SDP) provides mechanisms to=
<br>
=C2=A0 =C2=A0 describe attributes of multimedia sessions and of individual =
media<br>
=C2=A0 =C2=A0 streams (e.g., Real-time Transport Protocol (RTP) sessions) w=
ithin a<br>
=C2=A0 =C2=A0 multimedia session.=C2=A0 In the RTCWEB WG, there is a need t=
o use a<br>
=C2=A0 =C2=A0 single 5-tuple for sending and receiving media associated wit=
h<br>
=C2=A0 =C2=A0 multiple media descriptions (&quot;m=3D&quot; lines).=C2=A0 S=
uch a requirement has<br>
=C2=A0 =C2=A0 raised concerns over the semantic implications of the SDP att=
ributes<br>
=C2=A0 =C2=A0 associated with the RTP Media Streams multiplexed over a sing=
le<br>
=C2=A0 =C2=A0 underlying transport layer flow.<br>
<br>
=C2=A0 =C2=A0 The scope of this specification is to provide a framework for=
<br>
=C2=A0 =C2=A0 analyzing the multiplexing characteristics of SDP attributes.=
=C2=A0 This<br>
=C2=A0 =C2=A0 specification also categorizes the existing SDP attributes ba=
sed on<br>
=C2=A0 =C2=A0 the framework described herein.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attri=
butes/" target=3D"_blank">https://datatracker.ietf.org/<u></u>doc/draft-iet=
f-mmusic-sdp-mux-<u></u>attributes/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-=
05" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-ietf-mmusic-s=
dp-mux-<u></u>attributes-05</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-sdp-mux-att=
ributes-05" target=3D"_blank">http://www.ietf.org/rfcdiff?<u></u>url2=3Ddra=
ft-ietf-mmusic-sdp-<u></u>mux-attributes-05</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-<u></u>drafts/</a><br>
<br>
______________________________<u></u>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/mmusic</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div></div>

--089e0102ed86d8d7be0509b37fa1--


From nobody Mon Dec  8 04:49:02 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BB51A86DD for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 04:49:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level: 
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 9UguYAmdBcXP for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 04:48:58 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 124471A86E5 for <mmusic@ietf.org>; Mon,  8 Dec 2014 04:48:57 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-e9-54859e383d9d
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6C.58.04076.83E95845; Mon,  8 Dec 2014 13:48:56 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0195.001; Mon, 8 Dec 2014 13:48:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, =?utf-8?B?8J+Uk0RhbiBXaW5n?= <dwing@cisco.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
Thread-Index: AdAO3vobOG9fyqvZTs6dIUhJ2pZtLAAIUu8AAEikDgAAHWRXgAADp3+AAAFA0gAAjj74QA==
Date: Mon, 8 Dec 2014 12:48:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D584720@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D572AB3@ESESSMB209.ericsson.se> <547F2380.8060706@alum.mit.edu> <0D3BD107-9C93-460E-80D3-8F75958485D4@cisco.com> <5481D03B.2000607@alum.mit.edu> <6F9079B7-37DA-4102-BFB1-7D1F73FD6C89@cisco.com> <5481F12A.1020101@alum.mit.edu>
In-Reply-To: <5481F12A.1020101@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+Jvja7FvNYQg/1r+SwuXnvIZDF1+WMW ixUbDrA6MHv8ff+ByWPK742sHkuW/GQKYI7isklJzcksSy3St0vgyvh09jhbwQedirlb1jM2 MN7R7mLk5JAQMJG42nWPEcIWk7hwbz1bFyMXh5DAEUaJ5odrWCGcxYwSF7f0MHcxcnCwCVhI dP8DaxYRiJK4+2cOK4jNLBAtsXLTRrBBwgJ5Eqe+7mEBKRcRyJe48t4JojxM4tWGyWDlLAIq EvvvrWACsXkFfCXuzu2DWjWTSeLUlv9gCU4BHYlT7T3sIDYj0HHfT61hgtglLnHryXwmiKMF JJbsOc8MYYtKvHz8jxXCVpL4seES2A3MApoS63fpQ7QqSkzpfsgOsVdQ4uTMJywTGMVmIZk6 C6FjFpKOWUg6FjCyrGIULU4tLs5NNzLSSy3KTC4uzs/Ty0st2cQIjKeDW35b7WA8+NzxEKMA B6MSD6+BSGuIEGtiWXFl7iFGaQ4WJXHehefmBQsJpCeWpGanphakFsUXleakFh9iZOLglGpg lL7b9OK9Wu1Gv0bt3YmH2WZoV/CwXsoVVpjEy3l+PrOaO5MI59K7BqI2Fu77Wdo0Xxkv7pi5 6Ov8l54CJxlkWN24JjGYFB5g97r/w3AN017uyMXHYxZKSd6b3fW/P2TTIqWmLT7ZOxO0TWbd 7mF4o5q7XeaTrqnfqsy9szPvTl52qGb6hFXsSizFGYmGWsxFxYkAidwS94gCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/vSwLom-kWyHtsQtMyGwDU6CEkgc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-sctp-sdp-08 - Paul's comments - default SCTP port
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Dec 2014 12:49:00 -0000

SGksDQoNCkkgZG91YnQgaXQgaXMgd2l0aGluIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50IHRv
IHJlZ2lzdGVyIGEgZGVkaWNhdGVkIFNDVFAgcG9ydCB3aXRoIElBTkEuLi4NCg0KQnV0LCB0aGUg
cXVlc3Rpb24gaXMgc3RpbGwgd2hldGhlciB3ZSwgZm9yIFNEUCBPZmZlci9BbnN3ZXIgdXNhZ2Us
IHdhbnQgdG8gZGVmaW5lIGEgZGVmYXVsdCB2YWx1ZSBmb3IgdGhlIFNEUCAnc2N0cC1wb3J0JyBh
dHRyaWJ1dGUsIG9yIHdoZXRoZXIgd2UgbWFuZGF0ZSBpdCB0byBhbHdheXMgYmUgcHJlc2VudCBm
b3IgJ1VEUC9EVExTL1NDVFAnIGFuZCAnVENQL0RUTFMvU0NUUCcuDQoNClJlZ2FyZHMsDQoNCkNo
cmlzdGVyDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBQYXVsIEt5eml2YXQg
W21haWx0bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHVdIA0KU2VudDogNS4gam91bHVrdXV0YSAyMDE0
IDE5OjU0DQpUbzog8J+Uk0RhbiBXaW5nDQpDYzogQ2hyaXN0ZXIgSG9sbWJlcmc7IFNhbHZhdG9y
ZSBMb3JldG87IG1tdXNpY0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtNTVVTSUNdIERyYWZ0IG5l
dyB2ZXJzaW9uOiBkcmFmdC1pZXRmLW1tdXNpYy1zY3RwLXNkcC0wOCAtIFBhdWwncyBjb21tZW50
cyAtIGRlZmF1bHQgU0NUUCBwb3J0DQoNCk9uIDEyLzUvMTQgMTI6MTcgUE0sIPCflJNEYW4gV2lu
ZyB3cm90ZToNCj4NCj4gT24gRGVjIDUsIDIwMTQsIGF0IDc6MzMgQU0sIFBhdWwgS3l6aXZhdCA8
cGt5eml2YXRAYWx1bS5taXQuZWR1PiB3cm90ZToNCj4NCj4+IERhbiwNCj4+DQo+PiBPbiAxMi80
LzE0IDg6MzEgUE0sIPCflJNEYW4gV2luZyB3cm90ZToNCj4+Pg0KPj4+IE9uIERlYyAzLCAyMDE0
LCBhdCA2OjUxIEFNLCBQYXVsIEt5eml2YXQgPHBreXppdmF0QGFsdW0ubWl0LmVkdT4gd3JvdGU6
DQo+Pj4NCj4+Pj4gT24gMTIvMy8xNCA1OjAwIEFNLCBDaHJpc3RlciBIb2xtYmVyZyB3cm90ZToN
Cj4+Pj4+IEhpLA0KPj4+Pj4NCj4+Pj4+Pj4+Pj4gU2VjdGlvbiA1LjE6DQo+Pj4+Pj4+Pj4+DQo+
Pj4+Pj4+Pj4+IElNTyA1MDAwIGlzIGEgYmFkIGNob2ljZSBmb3IgdGhlIGRlZmF1bHQgcG9ydCB2
YWx1ZS4gSXQgZmFsbHMgDQo+Pj4+Pj4+Pj4+IGluIHRoZSBtaWRkbGUgb2YgdGhlIHJlZ2lzdGVy
ZWQgcG9ydCBsaXN0LiBJdCBpc24ndCBjdXJyZW50bHkgDQo+Pj4+Pj4+Pj4+IHJlZ2lzdGVyZWQg
KEkgZG9uJ3Qga25vdyB3aHkpIGJ1dCBpdCBwb3RlbnRpYWxseSBjb3VsZC4gSSANCj4+Pj4+Pj4+
Pj4gc3VnZ2VzdCB0aGF0IGEgbnVtYmVyIG91dHNpZGUgb2YgdGhlIHJlZ2lzdGVyZWQgcG9ydCBy
YW5nZQ0KPj4+Pj4+Pj4+PiAoPjQ5MTUxKSB3b3VsZCBiZSBzYWZlc3QuIFRvIGF2b2lkIGJlaW5n
IGFyYml0cmFyeSwgSSBzdWdnZXN0IDY1NTM1IC0gdGhlIGxhcmdlc3QgcG9zc2libGUgMTYgYml0
IG51bWJlci4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IEkgaGF2ZSBubyBwcm9ibGVtIHRvIGNoYW5n
ZSB0aGUgZGVmYXVsdCB2YWx1ZS4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IEhvd2V2ZXIsIDUwMDAg
d2FzIGRlZmluZWQgYmVmb3JlIEkgZ290IGludm9sdmVkIHdpdGggdGhlIGRyYWZ0LCBzbyBJIHRo
aW5rIGl0IHdvdWxkIGJlIGdvb2QgdG8gZ2V0IHNvbWUgaW5wdXQgZnJvbSBHb256YWxvIGFuZC9v
ciBTYWx2YXRvcmUgd2hldGhlciB0aGVyZSB3YXMgc29tZSBzcGVjaWZpYyByZWFzb24gZm9yIDUw
MDAuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiAtLS0tLS0tLS0tLS0tDQo+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4gNTAwMCBpcyB0aGUgZGVmYXVsdCB2YWx1ZSB0aGUgY3VycmVudC9hdmFpbGFibGUgU0NUUCBv
dmVyIFRMUyBhcmUgdXNpbmcuDQo+Pj4+Pj4+DQo+Pj4+Pj4+IGp1c3QgdG8gY2xhcmlmeQ0KPj4+
Pj4+PiB3aGF0IEkgbWVhbnQgaXMgdGhhdCA1MDAwIGlzIHRoZSB2YWx1ZSB0aGF0IGFzIGZhciBh
cyBJIGtub3cgDQo+Pj4+Pj4+IEZpcmVmb3ggaXMgdXNpbmcgaW4gaXRzIFNDVFAgb3ZlciBUTFMg
ZGF0YSBjaGFubmVsIA0KPj4+Pj4+PiBpbXBsZW1lbnRhdGlvbg0KPj4+Pj4+DQo+Pj4+Pj4gQUZB
SUsgaXQgaXMgYmVpbmcgZXhwbGljaXRseSBzcGVjaWZpZWQgYXMgNTAwMCwgbm90IHRoYXQgdGhl
cmUgaXMgcmVsaWFuY2Ugb24gYSBkZWZhdWx0IHZhbHVlIG9mIDUwMDAuIENoYW5naW5nIHRoZSBk
ZWZhdWx0IG9ubHkgYWZmZWN0cyB0aG9zZSBpbXBsZW1lbnRhdGlvbnMgZGVwZW5kaW5nIG9uIHRo
ZSBkZWZhdWx0Lg0KPj4+Pj4+DQo+Pj4+Pj4gQWxzbywgaWYgdGhvc2UgaW1wbGVtZW50YXRpb25z
IGFyZSB1c2luZyBkaWZmZXJlbnQgU0RQIHN5bnRheCwgbm90IGNvbmZvcm1hbnQgd2l0aCB0aGlz
IHZlcnNpb24gb2YgdGhlIGRyYWZ0LCB0aGVuIHRoZXkgd2lsbCBuZWVkIHRvIGJlIGNoYW5nZWQg
YW55d2F5IGJlZm9yZSB0aGlzIGNoYW5nZSBiZWNvbWVzIGVmZmVjdGl2ZS4NCj4+Pj4+DQo+Pj4+
PiBBbm90aGVyIG9wdGlvbiBpcyB0byBub3QgZGVmaW5lIGEgZGVmYXVsdCBwb3J0IHRvIGJlZ2lu
IHdpdGgsIGFuZCBtYW5kYXRlIHRoZSB1c2FnZSBvZiB0aGUgc2N0cC1wb3J0IGF0dHJpYnV0ZS4N
Cj4+Pj4+DQo+Pj4+PiBCZWNhdXNlLCBhc3N1bWUgeW91IHdvdWxkIGhhdmUgdHdvIFNDVFAgYXNz
b2NpYXRpb25zIChkZXNjcmliZWQgdXNpbmcgZGlmZmVyZW50IG0tIGxpbmVzKSwgYm90aCB3aXRo
b3V0IGFuIHNjdHAtcG9ydCBhdHRyaWJ1dGUuIFlvdSB3b3VsZCB1c2UgdGhlIHNhbWUgU0NUUCBw
b3J0IGZvciBib3RoIFNDVFAgYXNzb2NpYXRpb25zLi4uDQo+Pj4+DQo+Pj4+IFJlbWVtYmVyIC0g
bXVsdGlwbGUgU0NUUCBhc3NvY2lhdGlvbnMsIGVzcGVjaWFsbHkgYnVuZGxlZCBvbmVzLCBpcyBs
aWtlbHkgdG8gYmUgYSB2ZXJ5IHJhcmUgb2NjdXJyZW5jZS4NCj4+Pg0KPj4+IFdlIHNob3VsZG4n
dCBoYXZlIGEgZGVmYXVsdCBwb3J0IG51bWJlciBmb3IgU0NUUDsgdGhpcyByZS1pbnZlbnRzIHRo
ZSBtaXN0YWtlcyBvZiAiUlRDUCA9IFJUUCBwb3J0ICsgMSIgdGhhdCBuZWNlc3NpdGF0ZWQgdGhl
IGxhdGUgc3RhbmRhcmRpemF0aW9uIG9mIGE9cnRjcCB3aGljaCBpcyAqc3RpbGwqIG5vdCByZWxp
YWJseSBzaWduYWxlZCBieSBTSVAgZW5kcG9pbnRzIChmb3J0dW5hdGVseSBXZWJSVEMgaXMgcmVx
dWlyaW5nIGl0LCBJIGJlbGlldmUpLiBBIGZpeGVkIHBvcnQgbnVtYmVyIGRvZXNuJ3Qgd29yayB3
aXRoIE5BUFQsIEErUCwgb3IgYWxsIHRoZSBvdGhlciBzdHVmZiB0aGF0IG11Y2tzIHdpdGggcG9y
dCBudW1iZXJzLiAgIFllcywgSSBrbm93IFNDVFAgZHJlYW1zIG9mIE5BUFRzIHRoYXQgZG9uJ3Qg
cmV3cml0ZSBwb3J0cywgYnV0IGV2ZW4gdGhhdCBkcmVhbSBkb2Vzbid0IHdvcmsgd2VsbCBpZiBl
dmVyeXRoaW5nIGlzIHRyeWluZyB0byB1c2UgdGhlIHNhbWUgcG9ydCBudW1iZXIuDQo+Pg0KPj4g
UmVtZW1iZXIsIHRoaXMgaXMgb25seSBmb3IgdGhlIGNhc2Ugd2hlcmUgU0NUUCBpcyBiZWluZyBj
YXJyaWVkIG92ZXIgYW5vdGhlciB0cmFuc3BvcnQgdGhhdCBoYXMgYSBwb3J0IG51bWJlci4NCj4N
Cj4gSSBoYWQgbWlzc2VkIHRoYXQuDQo+DQo+IEkgZG8gYWdyZWUgSUFOQSByZWdpc3RyYXRpb24g
b2YgdGhlIHBvcnQgc2VlbXMgYSBnb29kIGlkZWEuDQoNClRoZSBjdXJyZW50IGRlZmF1bHQgKDUw
MDApIGlzIGEgY3VycmVudGx5IHVuYXNzaWduZWQgdmFsdWUgaW4gdGhlIHJhbmdlIHJlc2VydmVk
IGZvciAocmVnaXN0ZXJlZCkgdXNlciBwb3J0cy4gVGhhdCBzZWVtcyB3cm9uZy4gSSBhbSBwcm9w
b3NpbmcgdG8gdXNlIGEgbnVtYmVyICg2NTUzNSkgZnJvbSB0aGUgZHluYW1pYyBwb3J0IG51bWJl
ciByYW5nZSBhcyB0aGUgZGVmYXVsdC4NCg0KSSBhZ3JlZSB0aGF0IGFub3RoZXIgcG9zc2liaWxp
dHkgd291bGQgYmUgdG8gcmVnaXN0ZXIgYSBwb3J0IGZvciB0aGUgcHVycG9zZS4gKFBvdGVudGlh
bGx5IHRoaXMgcG9ydCBjb3VsZCBiZSBpbiB0aGUgc3lzdGVtIHBvcnRzIHJhbmdlLiBUaGUgcmVz
dHJpY3Rpb24gb24gdXNlIG9mIHN5c3RlbSBwb3J0cyBkb2Vzbid0IGFwcGx5IHdoZW4gdGhlIHBy
b3RvY29sIGlzIGltcGxlbWVudGVkIGluIGFwcGxpY2F0aW9uIHNwYWNlIG92ZXIgYW5vdGhlciB0
cmFuc3BvcnQuKQ0KDQpJIGp1c3QgZmluZCBpdCBhIGxpdHRsZSBlYXNpZXIgdG8gZ28gd2l0aCBh
IGR5bmFtaWMgcG9ydC4NCg0KCVRoYW5rcw0KCVBhdWwNCg0K


From nobody Mon Dec  8 17:10:02 2014
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C091A1AFA for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 17:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.91
X-Spam-Level: 
X-Spam-Status: No, score=-13.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 SCoaC0FuBwoZ for <mmusic@ietfa.amsl.com>; Mon,  8 Dec 2014 17:09:58 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF0261A1AE2 for <mmusic@ietf.org>; Mon,  8 Dec 2014 17:09:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19319; q=dns/txt; s=iport; t=1418087398; x=1419296998; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=WIj5zC4jEsIdyQ9NFm+Yh/OdZZh/Ag3pNpt10KwTA5A=; b=jb2fzVI3stAr6Twroc7+7zhZ4bWp5NaC1IYaf69ER6DRHO3KXSgJr5+x P2EQYqrDNNGRnOi+7pWVFr9V+H7SJiSB+bzdtTl1dt8bTRMQqP627+hv4 lqnN3o4R6SghE/P2IyiMrMbduDJSFE90M+LA/vCjNPIXAX7xAX5f44j27 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQHAPlKhlStJV2Y/2dsb2JhbABZgwZSUwWzIwUBd5FfAQuFOU4CgSkWAQEBAQF9hAIBAQEDAQEBAWgDCgEFCwsYCRYIBwkDAgECARUfEQYBDAEFAgEBBYgnCAgF1kkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXhiOJQVgHCYQtBYlCgnGFM4U8gQ0wgi+CE4U3M4Ijg16EDCEwAYECgUABAQE
X-IronPort-AV: E=Sophos;i="5.07,541,1413244800";  d="scan'208,217";a="378615796"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 09 Dec 2014 01:09:56 +0000
Received: from [10.155.85.126] (dhcp-10-155-85-126.cisco.com [10.155.85.126]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sB919tQ0015956; Tue, 9 Dec 2014 01:09:56 GMT
Message-ID: <54864BE3.6010803@cisco.com>
Date: Mon, 08 Dec 2014 20:09:55 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Suhas Nandakumar <suhasietf@gmail.com>, Christian Groves <Christian.Groves@nteczone.com>
References: <20141126140229.31432.80074.idtracker@ietfa.amsl.com> <54810B09.1080200@nteczone.com> <CAMRcRGQpvySMa9c=3B1tPqxTRRJ4PnibfbbdRVvCG=_cjFXCGQ@mail.gmail.com>
In-Reply-To: <CAMRcRGQpvySMa9c=3B1tPqxTRRJ4PnibfbbdRVvCG=_cjFXCGQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------020205060005050605050508"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/heOtk_XMWgawUxkH3qp0JsMGUQU
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 01:10:01 -0000

This is a multi-part message in MIME format.
--------------020205060005050605050508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 12/8/14, 7:23 AM, Suhas Nandakumar wrote:
> Hello Christian
>
>   Please see inline for the responses.
>
>    Also,  a question to chairs,  should I produce a newer version of 
> the document to reflect the changes below or wait till we end the last 
> call.
>
Unless anybody in the WG disagrees with the proposed changes you might 
as well incorporate them at this point.

Thanks

-- Flemming

> Please advice.
>
> Thanks
> Suhas
>
> On Fri, Dec 5, 2014 at 7:01 AM, Christian Groves 
> <Christian.Groves@nteczone.com <mailto:Christian.Groves@nteczone.com>> 
> wrote:
>
>     Hello Suhas,
>
>     A few comments:
>
>     1) With regards to 5.55 ITU-T-Rec.Q1970 I think mux category "Not
>     Recommended" or "Special" would probably be more appropriate.
>     a=ipbcp is used to signal the version and type of a SDP based
>     IPBCP message. It's used in a BICC (ITU-T Q.1901) environment
>     limited to a single media payload. The use of IPBCP messages for
>     multiplexed transport would require updates to several Q.19xx
>     series Recommendations.
>
> [Suhas]  I am not an expert in this area and from limited reading of 
> the the ITU Spec it felt like ipbcp is used just to signify IPBCP 
> version number (as pointed by you) and thus felt as far as 
> multiplexing is concerned , the category NORMAL for this attributes 
> makes sense. Given the single media payload restriction above, It 
> seems SPECIAL category is more appropriate and provides the 
> implementors an option to consult the spec before making multiplexing 
> decisions.
>
> I can update the draft to reflect the same.
>
>     Also the heading title should be changed to align with the other
>     ITU-T related heading, i.e. from "ITU-T-Rec.Q1970" to "ITU-T Q.1970".
>
> [Suhas] Thanks, will update in the next version.
>
>
>     2) 5.48 ATM SDP - I still not quite sure about the criteria for
>     assigning the mux category. The text indicates that "For all
>     adaptation types (AAL1, AAL2 and AAL5), bearer connections may be
>     bundled into a single media group" however the BUNDLE draft is
>     only for nettypes IN and addresstypes "IP4" or "IP6". So I
>     wouldn't assign mux category "NORMAL" because some extra work
>     would be needed to define how BUNDLE would be used for the ATM SDP
>     parameters.  If multiplexing was applied then would the attributes
>     related to the underlying ATM bearer need to be identical i.e.
>     attributes from 5.6.1/RFC3108? Given the age and that these are
>     not IP related, i'd be inclined to mark them all as NOT RECOMMENDED.
>
>
> [Suhas] The notes associated with the section 5.48 in this draft was 
> added to mention that RFC3018 doesn't address cases where ATM serves 
> as a low-level transport pipe for IP packets which in turn might carry 
> multiplexed media streams.  I am open to move it to NOT RECOMMENDED 
> given your analysis.
>
>
>     3) 5.56 H.248.15 - FYI there's some work underway in the ITU-T
>     SG16 on the support of multiplexing based on BUNDLE in
>     H.248.STGROUP
>     (http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip).
>
>     Regards, Christian
>
>
>     On 27/11/2014 1:02 AM, internet-drafts@ietf.org
>     <mailto:internet-drafts@ietf.org> wrote:
>
>         A New Internet-Draft is available from the on-line
>         Internet-Drafts directories.
>           This draft is a work item of the Multiparty Multimedia
>         Session Control Working Group of the IETF.
>
>                  Title           : A Framework for SDP Attributes when
>         Multiplexing
>                  Author          : Suhas Nandakumar
>                 Filename        :
>         draft-ietf-mmusic-sdp-mux-attributes-05.txt
>                 Pages           : 88
>                 Date            : 2014-11-26
>
>         Abstract:
>             The Session Description Protocol (SDP) provides mechanisms to
>             describe attributes of multimedia sessions and of
>         individual media
>             streams (e.g., Real-time Transport Protocol (RTP)
>         sessions) within a
>             multimedia session.  In the RTCWEB WG, there is a need to
>         use a
>             single 5-tuple for sending and receiving media associated with
>             multiple media descriptions ("m=" lines).  Such a
>         requirement has
>             raised concerns over the semantic implications of the SDP
>         attributes
>             associated with the RTP Media Streams multiplexed over a
>         single
>             underlying transport layer flow.
>
>             The scope of this specification is to provide a framework for
>             analyzing the multiplexing characteristics of SDP
>         attributes.  This
>             specification also categorizes the existing SDP attributes
>         based on
>             the framework described herein.
>
>
>         The IETF datatracker status page for this draft is:
>         https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>
>         There's also a htmlized version available at:
>         http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-05
>
>         A diff from the previous version is available at:
>         http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-05
>
>
>         Please note that it may take a couple of minutes from the time
>         of submission
>         until the htmlized version and diff are available at
>         tools.ietf.org <http://tools.ietf.org>.
>
>         Internet-Drafts are also available by anonymous FTP at:
>         ftp://ftp.ietf.org/internet-drafts/
>
>         _______________________________________________
>         mmusic mailing list
>         mmusic@ietf.org <mailto:mmusic@ietf.org>
>         https://www.ietf.org/mailman/listinfo/mmusic
>
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--------------020205060005050605050508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 12/8/14, 7:23 AM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMRcRGQpvySMa9c=3B1tPqxTRRJ4PnibfbbdRVvCG=_cjFXCGQ@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">Hello Christian
        <div><br>
        </div>
        <div>&nbsp; Please see inline for the responses.&nbsp;</div>
        <div><br>
        </div>
        <div>&nbsp; &nbsp;Also, &nbsp;a question to chairs, &nbsp;should I produce a newer
          version of the document to reflect the changes below or wait
          till we end the last call.</div>
        <div><br>
        </div>
      </div>
    </blockquote>
    Unless anybody in the WG disagrees with the proposed changes you
    might as well incorporate them at this point. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <blockquote
cite="mid:CAMRcRGQpvySMa9c=3B1tPqxTRRJ4PnibfbbdRVvCG=_cjFXCGQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Please advice.</div>
        <div><br>
        </div>
        <div>Thanks</div>
        <div>Suhas</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Dec 5, 2014 at 7:01 AM,
            Christian Groves <span dir="ltr">&lt;<a
                moz-do-not-send="true"
                href="mailto:Christian.Groves@nteczone.com"
                target="_blank">Christian.Groves@nteczone.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hello
              Suhas,<br>
              <br>
              A few comments:<br>
              <br>
              1) With regards to 5.55 ITU-T-Rec.Q1970 I think mux
              category "Not Recommended" or "Special" would probably be
              more appropriate. a=ipbcp is used to signal the version
              and type of a SDP based IPBCP message. It's used in a BICC
              (ITU-T Q.1901) environment limited to a single media
              payload. The use of IPBCP messages for multiplexed
              transport would require updates to several Q.19xx series
              Recommendations.<br>
            </blockquote>
            <div>&nbsp;</div>
            <div>[Suhas] &nbsp;I am not an expert in this area and from
              limited reading of the the ITU Spec it felt like ipbcp is
              used just to signify IPBCP version number (as pointed by
              you) and thus felt as far as multiplexing is concerned ,
              the category NORMAL for this attributes makes sense. Given
              the single media payload restriction above, It seems
              SPECIAL category is more appropriate and provides the
              implementors an option to consult the spec before making
              multiplexing decisions.</div>
            <div><br>
            </div>
            <div>I can update the draft to reflect the same.</div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Also
              the heading title should be changed to align with the
              other ITU-T related heading, i.e. from "ITU-T-Rec.Q1970"
              to "ITU-T Q.1970".<br>
            </blockquote>
            <div>&nbsp;</div>
            <div>[Suhas] Thanks, will update in the next version.&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
              2) 5.48 ATM SDP - I still not quite sure about the
              criteria for assigning the mux category. The text
              indicates that "For all adaptation types (AAL1, AAL2 and
              AAL5), bearer connections may be bundled into a single
              media group" however the BUNDLE draft is only for nettypes
              IN and addresstypes "IP4" or "IP6". So I wouldn't assign
              mux category "NORMAL" because some extra work would be
              needed to define how BUNDLE would be used for the ATM SDP
              parameters.&nbsp; If multiplexing was applied then would the
              attributes related to the underlying ATM bearer need to be
              identical i.e. attributes from 5.6.1/RFC3108? Given the
              age and that these are not IP related, i'd be inclined to
              mark them all as NOT RECOMMENDED.<br>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] The notes associated with the section 5.48 in
              this draft was added to mention that RFC3018 doesn't
              address&nbsp;<span style="color:rgb(0,0,0);font-size:1em">cases
                where ATM serves as a low-level transport pipe for IP
                packets which in turn might carry multiplexed media
                streams.&nbsp; I am open to move it to NOT RECOMMENDED given
                your analysis.</span></div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
              3) 5.56 H.248.15 - FYI there's some work underway in the
              ITU-T SG16 on the support of multiplexing based on BUNDLE
              in H.248.STGROUP (<a moz-do-not-send="true"
href="http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip"
                target="_blank">http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/TD-14.zip</a>).<br>
              <br>
              Regards, Christian
              <div class="">
                <div class="h5"><br>
                  <br>
                  On 27/11/2014 1:02 AM, <a moz-do-not-send="true"
                    href="mailto:internet-drafts@ietf.org"
                    target="_blank">internet-drafts@ietf.org</a> wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0px 0px
                    0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">A
                    New Internet-Draft is available from the on-line
                    Internet-Drafts directories.<br>
                    &nbsp; This draft is a work item of the Multiparty
                    Multimedia Session Control Working Group of the
                    IETF.<br>
                    <br>
                    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Title&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: A Framework for SDP
                    Attributes when Multiplexing<br>
                    &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Author&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Suhas Nandakumar<br>
                    &nbsp; &nbsp; &nbsp; &nbsp; Filename&nbsp; &nbsp; &nbsp; &nbsp; : draft-ietf-mmusic-sdp-mux-attributes-05.txt<br>
                    &nbsp; &nbsp; &nbsp; &nbsp; Pages&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 88<br>
                    &nbsp; &nbsp; &nbsp; &nbsp; Date&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 2014-11-26<br>
                    <br>
                    Abstract:<br>
                    &nbsp; &nbsp; The Session Description Protocol (SDP) provides
                    mechanisms to<br>
                    &nbsp; &nbsp; describe attributes of multimedia sessions and
                    of individual media<br>
                    &nbsp; &nbsp; streams (e.g., Real-time Transport Protocol
                    (RTP) sessions) within a<br>
                    &nbsp; &nbsp; multimedia session.&nbsp; In the RTCWEB WG, there is
                    a need to use a<br>
                    &nbsp; &nbsp; single 5-tuple for sending and receiving media
                    associated with<br>
                    &nbsp; &nbsp; multiple media descriptions ("m=" lines).&nbsp; Such
                    a requirement has<br>
                    &nbsp; &nbsp; raised concerns over the semantic implications
                    of the SDP attributes<br>
                    &nbsp; &nbsp; associated with the RTP Media Streams
                    multiplexed over a single<br>
                    &nbsp; &nbsp; underlying transport layer flow.<br>
                    <br>
                    &nbsp; &nbsp; The scope of this specification is to provide a
                    framework for<br>
                    &nbsp; &nbsp; analyzing the multiplexing characteristics of
                    SDP attributes.&nbsp; This<br>
                    &nbsp; &nbsp; specification also categorizes the existing SDP
                    attributes based on<br>
                    &nbsp; &nbsp; the framework described herein.<br>
                    <br>
                    <br>
                    The IETF datatracker status page for this draft is:<br>
                    <a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/"
                      target="_blank">https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/</a><br>
                    <br>
                    There's also a htmlized version available at:<br>
                    <a moz-do-not-send="true"
href="http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-05"
                      target="_blank">http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-05</a><br>
                    <br>
                    A diff from the previous version is available at:<br>
                    <a moz-do-not-send="true"
href="http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-05"
                      target="_blank">http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-05</a><br>
                    <br>
                    <br>
                    Please note that it may take a couple of minutes
                    from the time of submission<br>
                    until the htmlized version and diff are available at
                    <a moz-do-not-send="true"
                      href="http://tools.ietf.org" target="_blank">tools.ietf.org</a>.<br>
                    <br>
                    Internet-Drafts are also available by anonymous FTP
                    at:<br>
                    <a moz-do-not-send="true"
                      href="ftp://ftp.ietf.org/internet-drafts/"
                      target="_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
                    <br>
                    _______________________________________________<br>
                    mmusic mailing list<br>
                    <a moz-do-not-send="true"
                      href="mailto:mmusic@ietf.org" target="_blank">mmusic@ietf.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://www.ietf.org/mailman/listinfo/mmusic"
                      target="_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
                    <br>
                  </blockquote>
                  <br>
                  _______________________________________________<br>
                  mmusic mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:mmusic@ietf.org" target="_blank">mmusic@ietf.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://www.ietf.org/mailman/listinfo/mmusic"
                    target="_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020205060005050605050508--


From nobody Tue Dec  9 14:21:05 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068A11A1A27 for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 14:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 4xWsRdGz602S for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 14:21:01 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA2D1A1A46 for <mmusic@ietf.org>; Tue,  9 Dec 2014 14:20:58 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-06v.sys.comcast.net with comcast id RaL51p00D2Bo0NV01aLx9N; Tue, 09 Dec 2014 22:20:57 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-05v.sys.comcast.net with comcast id RaLw1p00g3Ge9ey01aLxgq; Tue, 09 Dec 2014 22:20:57 +0000
Message-ID: <548775C8.3000004@alum.mit.edu>
Date: Tue, 09 Dec 2014 17:20:56 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Christer.Holmberg@ericsson.com" <Christer.Holmberg@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418163657; bh=p/JuiRASjji/vh0kLrQ03VTLIe8v+CV2+hVbmhzjC6E=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=tqwZU8vUL8YpKn69UdRzOJfC+YFf2qyh+pz8R56Z+CEUaogM6nHvB45LPh6YF/3yT 6iJ99XUoCGjMhod0mRyl/LSKHz68cIHAgy7EaLDu4HZON6QC3bH9G/Vcc9AF7BpT4c j/cABV3onzeaxFPqz2/Q9Q/VPzsFL4m8pv9pxhlboYdCSPCvjQuNEJfoEXuGZFdYew 28iz/c1H+SSgV0CMLy8oKC1fyWh1u/nMaqpO6ecHW/YLjRTvP5nJ8M6mowmgJd8FLi 94hqOTKqMRqDK3W0LOBnnwfIoLG1Wrl5Qm425TEwFH8ezRejn1lQAk/ZHurrqfdEDO G4OZ8gfSB21jQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/N6jx14fyCQ6EFdePqenjatfuP3A
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: [MMUSIC] bundle-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 22:21:03 -0000

In general the use of the new terminology (identification-tag) is an 
improvement. I have the following comments:

Section 5.1 says:

    A single address:port combination is also used for sending bundled
    media.  The address:port combination used for sending bundled media
    MAY be the same as the BUNDLE address, used to receive bundled media,
    depending on whether symmetric RTP is used.  A given address:port
    combination MUST NOT be used for sending media associated with
    multiple BUNDLE groups.

If symmetric RTP is *not* used, what is the value of requiring that a 
single address:port be used for sending? The receiver, and 
intermediaries, won't know what that address is until the media starts 
flowing.

Also, why would it be forbidden to use the same address to send to 
multiple bundle groups?

The restriction makes sense with ICE, but in that case it is ICE 
providing the restriction. In the absence of ICE these restrictions seem 
arbitrary and without motivation.

(Note that this limitation is also mentioned in section 10.3.1.)

Section 7.2:

I presume that the "c=" line associated with a bundled "m=" line could 
either be a media-level c-line following the m-line, or a session-level 
c-line preceding the first m-line. Is that right?

Perhaps that should be stated.

Section 8.5.2:

I want to check what is intended here.

Suppose I have previously established a bundle group. It has several 
m-lines. In the prior O/A all of those m-lines had the same 
address:port. Now I want to change the bundle address.

As I read the text in this section, I must change the address in *1* of 
the m-lines, and suggest it as the offerer bundle address, but leave the 
old address in the other m-lines.

That isn't what I had been thinking happened. I had been assuming that 
the address would be changed in all the m-lines.

The consequence of this is that if the answerer doesn't want the change, 
it will have to reject the one changed m-line, and select the old 
address as the bundle address. If I was making the change because I am 
no longer capable of using the old address then this won't work for me. 
It would be better for me to have the entire bundle rejected.

Section 11.2.1 says:

    When an offerer assigns a unique address to a bundled "m=" line
    (excluding and bundle-only "m=" line), it MUST also associate unique
    ICE candidates [RFC5245] to the "m=" line.

The parenthetical remark doesn't make sense to me. Did you perhaps mean: 
"(excluding any bundle-only "m=" lines)"?

	Thanks,
	Paul


From nobody Tue Dec  9 16:25:10 2014
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE321A0404 for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 16:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 LDMN7BqY1YyD for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 16:25:06 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 979351A0250 for <mmusic@ietf.org>; Tue,  9 Dec 2014 16:25:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2280; q=dns/txt; s=iport; t=1418171107; x=1419380707; h=message-id:date:from:mime-version:to:cc:subject; bh=AaTRZbYfxRzP+Y7CW3QdO/qmw+ajJXhhjcthXHubQcI=; b=gnyI2Ut0WbBZmqqvXaDGETNRdn4RA44myOvuwWeJsbn6jU0b993kLbx5 UdmsCj1OMXLBdmxgokG1WGCU4nwRBYonipfwJqvOpPf8c2A8qRdflfhN0 tq7wpelOt0YFO05T6T1PeBue+djTf3wvBRT4qfpn6xAX/dtA/sHyX7SlO 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMIALyRh1StJV2R/2dsb2JhbABZgwa0ZwUBd5dhgSoWAQEBAQF9hDZLAR8BHBYYAwIBAgFLDQEHAQGINNdlAQEBAQEBAQECAQEBAQEBAQEBGYYNiXaEPQWJQI1WgQ2CXYIQhTWGL4IwgVwhgnMBAQE
X-IronPort-AV: E=Sophos;i="5.07,548,1413244800";  d="scan'208,217";a="375825136"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-9.cisco.com with ESMTP; 10 Dec 2014 00:25:07 +0000
Received: from [10.155.85.126] (dhcp-10-155-85-126.cisco.com [10.155.85.126]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id sBA0P5oM027249; Wed, 10 Dec 2014 00:25:05 GMT
Message-ID: <548792E1.6060105@cisco.com>
Date: Tue, 09 Dec 2014 19:25:05 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="------------080301010004030802070107"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/RiYdCRWarRM8m8U6bAtd-ypYDv0
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>, draft-ejzak-mmusic-msrp-usage-data-channel@tools.ietf.org, draft-ejzak-mmusic-data-channel-sdpneg@tools.ietf.org
Subject: [MMUSIC] New milestone for "SDP Negotiation of DataChannel sub-protocols" and adoption of Ejzak drafts
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 00:25:08 -0000

This is a multi-part message in MIME format.
--------------080301010004030802070107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Greetings

During IETF91, Keith Drage provided an update on "SDP Negotiation of 
DataChannel sub-protocols" and the two associated I-Ds:

     draft-ejzak-mmusic-data-channel-sdpneg-02
     draft-ejzak-dispatch-msrp-usage-data-channel-01

Several people indicated interest and support for the work and a hum 
indicated strong consensus for adding a new MMUSIC milestone for this 
and adopting the above two drafts as WG items for that milestone.

If you have any comments or concerns with the above, please let us know 
no later than December 16, 2014.

Thanks

     Ari & Flemming (MMUSIC co-chairs)



--------------080301010004030802070107
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Greetings<br>
    <br>
    During IETF91, Keith Drage provided an update on "SDP Negotiation of
    DataChannel sub-protocols" and the two associated I-Ds:<br>
    <br>
    &nbsp;&nbsp;&nbsp; draft-ejzak-mmusic-data-channel-sdpneg-02<br>
    &nbsp;&nbsp;&nbsp; draft-ejzak-dispatch-msrp-usage-data-channel-01
    <meta name="ProgId" content="PowerPoint.Slide">
    <meta name="Generator" content="Microsoft PowerPoint 14">
    <!--StartFragment--><!--EndFragment--><br>
    <br>
    Several people indicated interest and support for the work and a hum
    indicated strong consensus for adding a new MMUSIC milestone for
    this and adopting the above two drafts as WG items for that
    milestone. <br>
    <br>
    If you have any comments or concerns with the above, please let us
    know no later than December 16, 2014. <br>
    <br>
    Thanks <br>
    <br>
    &nbsp;&nbsp;&nbsp; Ari &amp; Flemming (MMUSIC co-chairs)<br>
    <br>
    <br>
    <meta name="ProgId" content="PowerPoint.Slide">
    <meta name="Generator" content="Microsoft PowerPoint 14">
    <!--StartFragment--><!--EndFragment-->
  </body>
</html>

--------------080301010004030802070107--


From nobody Tue Dec  9 16:40:09 2014
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B921F1A0073 for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 16:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 p2Afym0hxwDi for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 16:40:06 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD8FB1A0250 for <mmusic@ietf.org>; Tue,  9 Dec 2014 16:40:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=513; q=dns/txt; s=iport; t=1418172006; x=1419381606; h=message-id:date:from:mime-version:to:cc:subject: content-transfer-encoding; bh=NQjzWxnnnHvhPfHv9DyvdfOiM8kxKjETSFX4MW6XdWk=; b=ixucT0KqSY0poorTyZKT4KChwNVMQtV7MGKCBJjS0uulgpNKUhH5aJs+ 9fQppHDee5/cYm6cP9ReHR0qaWoay0WS8MSXFLO2JmSYiQo+2PD6ZqwUh AquABCzs2IW5C47kUobRnVT3ubwXUVMLTcYBtuowCqPNcMIQbrc7+Pw90 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMIALSVh1StJV2Q/2dsb2JhbABZgwa0ZwUBd5dhgSoWAQEBAQF9hEFAATwWBBQDAgECAUsNAQcBAYg0100BAQEBAQEBAQIBAQEBAQEchg2JdoQ9AQSJQI1WgQ2CXYIQi2SCMIFcIYJzAQEB
X-IronPort-AV: E=Sophos;i="5.07,548,1413244800"; d="scan'208";a="104226266"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-8.cisco.com with ESMTP; 10 Dec 2014 00:40:06 +0000
Received: from [10.155.85.126] (dhcp-10-155-85-126.cisco.com [10.155.85.126]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id sBA0e5d6022050; Wed, 10 Dec 2014 00:40:05 GMT
Message-ID: <54879664.3050608@cisco.com>
Date: Tue, 09 Dec 2014 19:40:04 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/EBjm9fuwe8FuHUKaqNkzL1mmUUk
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>, draft-burman-mmusic-sdp-simulcast@tools.ietf.org
Subject: [MMUSIC] New milestone for "Using Simulcast in SDP and RTP Sessions" and adoption of draft-burman-mmusic-sdp-simulcast-00 as WG item
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 00:40:07 -0000

Greetings

During IETF 91, Bo Burman presented the updated/new draft on using 
simulcast in SDP and RTP sessions:

     draft-burman-mmusic-sdp-simulcast-00

There were several people that indicated interest and support for the 
work, and a WG hum indicated strong consensus for adding a milestone and 
adopting the above draft as a WG item.

If you have any concerns or comments with doing so, please let us know 
no later than December 16, 2014.

Thanks

     Ari & Flemming (MMUSIC co-chairs)


From nobody Tue Dec  9 23:37:11 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35E6A1A6F21 for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 23:37:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6z7ZUMoLC8So for <mmusic@ietfa.amsl.com>; Tue,  9 Dec 2014 23:37:06 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 979841A00E4 for <mmusic@ietf.org>; Tue,  9 Dec 2014 23:37:05 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-bf-5487f81f78eb
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 6C.1A.29772.F18F7845; Wed, 10 Dec 2014 08:37:03 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0195.001; Wed, 10 Dec 2014 08:37:03 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQ==
Date: Wed, 10 Dec 2014 07:37:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyM+Jvja78j/YQg1frNCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj4V/vgidyFds67jA3MPZJdDFycEgImEis ms7bxcgJZIpJXLi3nq2LkYtDSOAIo8SUv7OYIZwljBJ/GtYwgjSwCVhIdP/TBjFFBDQkJm1V A+llFlCReHX6MiuILQwUvrJqORuILSKgKTF94W8mCFtP4uTuBnaQVhYBVYmuhcIgYV4BX4kb s2eDtTICnfD91BomiJHiEreezGeCOE1AYsme88wQtqjEy8f/WCFsRYmr05dD1etILNj9iQ3C 1pZYtvA1M8R8QYmTM5+wTGAUmYVk7CwkLbOQtMxC0rKAkWUVo2hxanFSbrqRkV5qUWZycXF+ nl5easkmRmAcHNzy22AH48vnjocYBTgYlXh4C963hwixJpYVV+YeYpTmYFES5114bl6wkEB6 YklqdmpqQWpRfFFpTmrxIUYmDk6pBkaNUlkf97NZK0QCvh2z9OlnZshu6/16jC3AeXuQqMay 3TrGVuwhl4r5b+x1e68tlGi+xrE4zqEiZoo958J7JvFWB7Lf9TusXtskeyHd8kFNW4Xk8drg j1y7/Ja1iOwPe8fGsbRJ1XjNxwdPnZIXCcpoXDN1cXk3p3pe9b1VZbfY91770fplgRJLcUai oRZzUXEiABRiSENkAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/3YLuIOSwS1aICUsPgFLxclwH_DY
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 07:37:08 -0000

Hi Paul,

> In general the use of the new terminology (identification-tag) is an impr=
ovement. I have the following comments:
>
> Section 5.1 says:
>
>    A single address:port combination is also used for sending bundled
>    media.  The address:port combination used for sending bundled media
>    MAY be the same as the BUNDLE address, used to receive bundled media,
>    depending on whether symmetric RTP is used.  A given address:port
>    combination MUST NOT be used for sending media associated with
>    multiple BUNDLE groups.
>
> If symmetric RTP is *not* used, what is the value of requiring that a sin=
gle address:port be used for sending? The receiver, and intermediaries, won=
't know what that address is until the media starts flowing.
>
> Also, why would it be forbidden to use the same address to send to multip=
le bundle groups?
>
> The restriction makes sense with ICE, but in that case it is ICE providin=
g the restriction. In the absence of ICE these restrictions seem arbitrary =
and without motivation.
>
> (Note that this limitation is also mentioned in section 10.3.1.)

I thought we agreed in Honolulu that we would use a single address:port als=
o for sending.

--------------

> Section 7.2:
>
> I presume that the "c=3D" line associated with a bundled "m=3D" line coul=
d either be a media-level c-line following the m-line, or a session-level c=
-line preceding the first m-line. Is that right?

Yes.

> Perhaps that should be stated.

Eventhough I think it's basic SDP, I can add some text.

But, in that case one could argue that we have to say the same thing for SD=
P attributes which can be both session-level and media-level...

--------------

> Section 8.5.2:
>
> I want to check what is intended here.
>
> Suppose I have previously established a bundle group. It has several m-li=
nes. In the prior O/A all of those m-lines had the same address:port. Now I=
 want to change the bundle address.
>
> As I read the text in this section, I must change the address in *1* of t=
he m-lines, and suggest it as the offerer bundle address, but leave the old=
 address in the other m-lines.
>
> That isn't what I had been thinking happened. I had been assuming that th=
e address would be changed in all the m-lines.
>
> The consequence of this is that if the answerer doesn't want the change, =
it will have to reject the one changed m-line, and select the old address a=
s=20
> the bundle address. If I was making the change because I am no longer cap=
able of using the old address then this won't work for me.=20
> It would be better for me to have the entire bundle rejected.

The thinking has been that only an accepted BUNDLE address can be assigned =
to multiple m- lines. Your suggestion would change that, because the new ad=
dress (when suggested in the offer) has not been accepted as a BUNDLE addre=
ss yet.

Also, even if the offerer assigns the new address to all m- lines, and the =
answerer rejects the offer, the offerer still has to fall back to the previ=
ous offerer BUNDLE address - no matter whether it can use it or not.

AND, assuming we go along with your suggestion, I guess that also means tha=
t if a new m- line is added (section 8.5.3), and if the offerer wants the a=
ddress of that m- line to become the new offerer BUNDLE address, the offere=
r must also assign the address of the new m- line also to the other m- line=
s in the BUNDLE group.

--------------


> Section 11.2.1 says:
>
>    When an offerer assigns a unique address to a bundled "m=3D" line
>    (excluding and bundle-only "m=3D" line), it MUST also associate unique
>    ICE candidates [RFC5245] to the "m=3D" line.
>
> The parenthetical remark doesn't make sense to me. Did you perhaps mean:=
=20
> "(excluding any bundle-only "m=3D" lines)"?

Yes. I'll fix that.

Thanks!=20

Regards,

Christer


From nobody Wed Dec 10 06:32:59 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241AA1A9023 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 06:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 AbWIRGAEcdJl for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 06:32:55 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95D911A1AA8 for <mmusic@ietf.org>; Wed, 10 Dec 2014 06:32:55 -0800 (PST)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-11v.sys.comcast.net with comcast id RqYo1p00327uzMh01qYuLk; Wed, 10 Dec 2014 14:32:54 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-02v.sys.comcast.net with comcast id RqYt1p00X3Ge9ey01qYuep; Wed, 10 Dec 2014 14:32:54 +0000
Message-ID: <54885995.2060305@alum.mit.edu>
Date: Wed, 10 Dec 2014 09:32:53 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418221974; bh=v8MhQJQc6m86PSl18yxK6krILpHMSpV0m23SRUIZ0XI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=oVSa2CQTsRnL9lI0JNCt4AIW98QD32FaqEfupm2bYSFQax8m7o/calGW/ykAtxruL wsezg8U8wurR3o8u3FDkcxf/bHbb6QPiV6XpGiCS11SD7h2yz6mvGEtl/u5c8T8zgM Q2oTkNbtID2U9tEBV4wI7djP9Tqt+Bsqt3BLZjX//KLZvW43fLY3hx1EcYcxFCqANw KkL3PKdEvmtHPHhuJOqxKK7jc2Fi6Kry/NtWohVKjFi6hojHEoX0uGKTSPmFYngQWt H/uvd67bWNLVr/2FNMuuXx4ZgSmsZGQ3R8elayGI8c7ye4f5/+rqijhKB2VBKdgonQ 1SP7xJqZu4mew==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qgvz9RuikNBAShMbWBmifMPHoRk
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 14:32:57 -0000

On 12/10/14 2:37 AM, Christer Holmberg wrote:
> Hi Paul,
>
>> In general the use of the new terminology (identification-tag) is an improvement. I have the following comments:
>>
>> Section 5.1 says:
>>
>>     A single address:port combination is also used for sending bundled
>>     media.  The address:port combination used for sending bundled media
>>     MAY be the same as the BUNDLE address, used to receive bundled media,
>>     depending on whether symmetric RTP is used.  A given address:port
>>     combination MUST NOT be used for sending media associated with
>>     multiple BUNDLE groups.
>>
>> If symmetric RTP is *not* used, what is the value of requiring that a single address:port be used for sending? The receiver, and intermediaries, won't know what that address is until the media starts flowing.
>>
>> Also, why would it be forbidden to use the same address to send to multiple bundle groups?
>>
>> The restriction makes sense with ICE, but in that case it is ICE providing the restriction. In the absence of ICE these restrictions seem arbitrary and without motivation.
>>
>> (Note that this limitation is also mentioned in section 10.3.1.)
>
> I thought we agreed in Honolulu that we would use a single address:port also for sending.

I don't recall exactly what was said.

Here I'm asking if such a restriction adds any value and makes any sense.

>> Section 7.2:
>>
>> I presume that the "c=" line associated with a bundled "m=" line could either be a media-level c-line following the m-line, or a session-level c-line preceding the first m-line. Is that right?
>
> Yes.
>
>> Perhaps that should be stated.
>
> Eventhough I think it's basic SDP, I can add some text.
>
> But, in that case one could argue that we have to say the same thing for SDP attributes which can be both session-level and media-level...

My question is really about the meaning of the general phrase: 'the 
"<something>=" line *associated with a bundled "m=" line.'

To me it makes sense that it would include both session and media-level 
lines. I'm just not certain that this will be obvious to everyone.

>> Section 8.5.2:
>>
>> I want to check what is intended here.
>>
>> Suppose I have previously established a bundle group. It has several m-lines. In the prior O/A all of those m-lines had the same address:port. Now I want to change the bundle address.
>>
>> As I read the text in this section, I must change the address in *1* of the m-lines, and suggest it as the offerer bundle address, but leave the old address in the other m-lines.
>>
>> That isn't what I had been thinking happened. I had been assuming that the address would be changed in all the m-lines.
>>
>> The consequence of this is that if the answerer doesn't want the change, it will have to reject the one changed m-line, and select the old address as
>> the bundle address. If I was making the change because I am no longer capable of using the old address then this won't work for me.
>> It would be better for me to have the entire bundle rejected.
>
> The thinking has been that only an accepted BUNDLE address can be assigned to multiple m- lines. Your suggestion would change that, because the new address (when suggested in the offer) has not been accepted as a BUNDLE address yet.

First I just wanted to verify that is what is intended.
That is now settled.

Next is whether that is the best way to handle this.

> Also, even if the offerer assigns the new address to all m- lines, and the answerer rejects the offer, the offerer still has to fall back to the previous offerer BUNDLE address - no matter whether it can use it or not.

The answerer could reject all the m-lines yet accept the offer.

But yes, if the offer itself is rejected then there is need to fall back.

> AND, assuming we go along with your suggestion, I guess that also means that if a new m- line is added (section 8.5.3), and if the offerer wants the address of that m- line to become the new offerer BUNDLE address, the offerer must also assign the address of the new m- line also to the other m- lines in the BUNDLE group.

True. That is an argument in favor of keeping things as they are.

I guess you have convinced me.

	Thanks,
	Paul

>> Section 11.2.1 says:
>>
>>     When an offerer assigns a unique address to a bundled "m=" line
>>     (excluding and bundle-only "m=" line), it MUST also associate unique
>>     ICE candidates [RFC5245] to the "m=" line.
>>
>> The parenthetical remark doesn't make sense to me. Did you perhaps mean:
>> "(excluding any bundle-only "m=" lines)"?
>
> Yes. I'll fix that.
>
> Thanks!
>
> Regards,
>
> Christer
>


From nobody Wed Dec 10 06:57:28 2014
Return-Path: <ari.keranen@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166921A6FA0 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 06:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level: 
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 0qO9lUJ9E318 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 06:57:10 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51EA91A6F9F for <mmusic@ietf.org>; Wed, 10 Dec 2014 06:57:05 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-da-54885f3ef91e
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 1A.EC.04076.E3F58845; Wed, 10 Dec 2014 15:57:02 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.65) with Microsoft SMTP Server id 14.3.195.1; Wed, 10 Dec 2014 15:57:01 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0EE611102B1; Wed, 10 Dec 2014 16:57:02 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 29E6A5F85A;	Wed, 10 Dec 2014 16:58:00 +0200 (EET)
Received: from ip-193-234-217-42.guest.ericsson.fi (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id BA1A05F265; Wed, 10 Dec 2014 16:57:59 +0200 (EET)
Message-ID: <54885F3D.4040508@ericsson.com>
Date: Wed, 10 Dec 2014 16:57:01 +0200
From: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPLMWRmVeSWpSXmKPExsUyM+Jvja5dfEeIwaJD1hZTlz9msVh84D6r A5PHlN8bWT2WLPnJFMAUxWWTkpqTWZZapG+XwJUxv/M6U8E6k4ops9ezNDCeVe9i5OCQEDCR +PHNoouRE8gUk7hwbz1bFyMXh5DAEUaJs+tnsIIkhAQ2MEpcnMQFkdjDKHFm0U9GCGcto0T/ 6hNQzjZGiUs7+hhBWngFtCUuPVjFBmKzCKhK/J7+hxnEZhOwlVj96iYLiC0qkCzR9fIhE0S9 oMTJmU/A4iICZhKN7RfA6pkFZCRmnG0EqxEWMJdobT3IChG3kJg5/zwjhC0vsf3tHGaIH9Qk rp7bxAxxtqrE1X+vGCcwCs9CsmIWkvZZSNoXMDKvYhQtTi0uzk03MtJLLcpMLi7Oz9PLSy3Z xAgM8YNbflvtYDz43PEQowAHoxIPb8H79hAh1sSy4srcQ4zSHCxK4rwLz80LFhJITyxJzU5N LUgtii8qzUktPsTIxMEp1cDYFPTm3YH5P8v+fjryRiHp6t3eq46Hd1Yc813t8ibGhXulk4ad ed5NDeHetXIr862MdSS3ztRUmWWxzISTR+WLJNe8sB0miUIfl7Iy8V8rkTeKCxe73WobzRvz xFV51awfK176SFy6wL7qcnpRcPxuafcP/c6lh8/2SR6c/Et2bU7w4ZTeh4VKLMUZiYZazEXF iQDXd+wmUgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/9Ail9BlNsHquJtJmtbFOvPX1iak
Cc: mmusic <mmusic@ietf.org>
Subject: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes-05 review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 14:57:18 -0000

Hi Suhas,

Here are my review comments on the SDP mux draft. Technically I think 
the doc is in pretty good shape, so these are mostly editorial issues.


Cheers,
Ari


Abstract

    In the RTCWEB WG, there is a need to use a
    single 5-tuple for sending and receiving media associated with
    multiple media descriptions ("m=" lines).

Bundling is not RTCWEB-only feature, so I would rather drop the RTCWEB 
reference at least from the abstract, and write it in more general way 
(e.g., "in order to save resources and decrease connection setup times, 
these is a need..." like in section 3)


    Such a requirement has
    raised concerns over the semantic implications of the SDP attributes
    associated with the RTP Media Streams multiplexed over a single
    underlying transport layer flow.

I think we are beyond "raised concerns" and have actually found out it 
was a real issue, so I would update the wording here.


    The scope of this specification is to provide a framework for
    analyzing the multiplexing characteristics of SDP attributes.

s/scope/purpose/


1.  Introduction

    Real-Time Communication in WEB-browsers (Rtcweb) framework requires
    Real-time Transport Protocol (RTP) as the media transport protocol
    and Session Description Protocol (SDP) [RFC4566] for describing and
    negotiating multi-media communication sessions.

This (and the following paragraph) should also be more general. Here 
perhaps you can use RTCWEB as an example of where such feature is 
required, but adding an RTCWEB reference (e.g. the use case doc) would 
be good here for context.

I think it would make sense also to reference the bundle draft already 
here and writing a sentence or two about the relationship with this draft.

also:
  s/requires/uses/
  s/multi-media/multimedia/


3.  Motivation

    This imposes further restrictions on applicability of
    these SDP attributes as they are defined today.

Not sure where "these" here refers to. I guess that word can either be 
dropped, or clarify which attributes you mean.


4.  SDP Attribute Analysis Framework

Would it make sense to have "before" and "after" in all the SDP examples 
(now there's only the "before" part)?


4.2.  Category: NOT RECOMMENDED

Can/should we recommend here what to do in this case? Not multiplex? Not 
add such attributes? Either way?


4.3.  Category: IDENTICAL

    Attributes that MUST be identical across all the media descriptions
    being multiplexed.

Maybe clarify that attributes and their *values* (if exist) must be 
identical.


         <allOneLine>
         a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2
         df881ae642c371ba46df
         </allOneLine>

The draft uses now 3 different ways of presenting too long SDP lines 
(see e.g., 4.5, 4.7 and 14.3.1.1). I guess they are from the defining 
RFCs, but I would rather see uniform style across this document. 
Personally I prefer the style of section 4.5 (2 char indent).


4.4.  Category: SUM

Should clarify where do you put the SUM'ed value.


4.5.  Category: TRANSPORT

    Attributes that can be set normally for multiple items in a
    multiplexed group but the software MUST pick just one of the
    attribute of the given type for use.  The one chosen is the attribute
    associated with the "m=" line that represents the information being
    used for the transport of the RTP.

How do you "pick" the one; by repeating the same value for each bundled 
"m="-line?

Also, do we need to consider non-RTP cases too?


4.8.  Category: SPECIAL

    Attributes where the text in the source draft must be consulted for
    further handling when multiplexed.

s/source draft/specification defining the attribute/


5.9.  RFC6773 - DCCP-UDP Encapsulation

    Since RFC6773 is about tunneling DCCP in UDP, with the UDP port being
    the port of the DCCP en-/de-capsulation service.

Can't parse the sentence. Something missing here? Or extra "since"?


    This MAY or MAY NOT work depending on the
    nature of DCCP encapsulations and ports choses thus rendering it to
    be very application dependent.

Lower-case (non-RFC2119) "may" and "may not" would be appropriate here. 
Also s/ports choses/port choices/?


5.12.  RFC5245 - Interactive Connectivity Establishment (ICE)

Since the ICE candidate behavior is already specified in the bundle 
draft at least reference there would be good? Also please make sure that 
these stay in sync with what bundle has until it's an RFC.


5.21.  RFC6230 - Media Control Channel Framework

            | cfw-id  | Not Applicable  | M     | NORMAL       |

Should that be "Not Impacted" as in other NORMAL cases?


5.39.  RFC6189 - ZRTP

    | zrtp-hash  | Complicates if all the        | M     | NOT          |
    |            | m=lines are not authenticated |       | RECOMMENDED  |
    |            | as given in the example below |       |              |

Where's the example? You mean the one in section 4.2?


5.46.  RFC2326 - Real Time Streaming Protocol

Could mention here briefly why RTSP is not supported (similar to the 
next section).


5.50.  3GPP TS 183.063

    | PSCid               | Not Impacted | Not-Applicable | NORMAL      |

The "Not-Applicable" level is not defined. Could add that to section 5 
or explain here and in 5.58.


7.1.  RFC4585 - RTP/AVPF

Are the "Attr Name" here really attribute names or should one use some 
other name in this case?


7.3.  RFC6285 - Unicast-Based RAMS

This one was missing the "intro description". Could add something brief 
for consistency with rest of the doc. Same for 7.6, 9.1, 9.2, 10.x (I'll 
leave it up to you where you consider it worthwhile adding).

And is the "Attr Name" field here just "Name" intentionally? Same in 
following two sections.


13.1.  RFC5109 - RTP Payload Format for Generic FEC

    Draft draft-lennox-payload-ulp-ssrc-mux proposes a simple fix to make

This is a bit tricky. This should be a proper reference, but referencing 
expired drafts is not a good practice either. I would lean towards 
taking this sentence away since (if?) the fix is not going forward at 
the IETF.


14.2.1.  Recommendation - Procedures for Potential Configuration Pairing

    that are consistent across all the bundled media descriptions.

Could add "bundled media" to the terminology section.


15.  IANA Considerations

It would be great if someone double-checked that the "Mux Category" 
entries here match to the text. Probably a simple script could do that too.


From nobody Wed Dec 10 23:02:06 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E0F1A9128 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 23:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, 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 u2U07EH6s1M7 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 23:01:58 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A39FE1ACD16 for <mmusic@ietf.org>; Wed, 10 Dec 2014 23:01:57 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-20-54894163a442
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id EE.91.24955.36149845; Thu, 11 Dec 2014 08:01:55 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0195.001; Thu, 11 Dec 2014 08:01:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQAMbXWAACPMjwA=
Date: Thu, 11 Dec 2014 07:01:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu>
In-Reply-To: <54885995.2060305@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+JvjW6yY2eIwY1d0hZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWxbX83W8FHw4r5196xNjDuU+9i5OSQEDCR OHDoJROELSZx4d56ti5GLg4hgSOMErN3n2SHcJYwSlxbvhCoioODTcBCovufNogpIqAhMWmr Gkgvs4CKxKvTl1lBbGGg8JVVy9lAbBEBTYnpC38zQdhWEod3bWEBsVkEVCX2tHQwgti8Ar4S O/92M4PYQgL5Eu9nPWAGGc8poCPxdiVYmBHotO+n1jBBrBKXuPVkPtTJAhJL9pxnhrBFJV4+ /scKYStKtD9tYISo15FYsPsTG4StLbFs4WtmiLWCEidnPmGZwCg2C8nYWUhaZiFpmYWkZQEj yypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwNg5uOW36g7Gy28cDzEKcDAq8fAWvG8PEWJN LCuuzD3EKM3BoiTOu/DcvGAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjBbqbZs9DO2vOat8 POXsL3334/r7Fhu9987excK1NNVsc0jqyvtFdVExDukcLvLLD15bvObS6/PdqzUeSYfUGsZ/ SK2tTBO1c2/ukVD+Jb12Taj92kdG5XNqtwrUZQpWFZyKCfhUclr5fLDNdvddS/v3eu5IOtG5 xFpik3TFoqJPWZ+F9m68o8RSnJFoqMVcVJwIAI8mVwp+AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/FCq2WmncE0JrAV9GAi7kHvP3_Bs
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 07:02:00 -0000

Hi Paul,

>>> In general the use of the new terminology (identification-tag) is an im=
provement. I have the following comments:
>>>
>>> Section 5.1 says:
>>>
>>>     A single address:port combination is also used for sending bundled
>>>     media.  The address:port combination used for sending bundled media
>>>     MAY be the same as the BUNDLE address, used to receive bundled medi=
a,
>>>     depending on whether symmetric RTP is used.  A given address:port
>>>     combination MUST NOT be used for sending media associated with
>>>     multiple BUNDLE groups.
>>>
>>> If symmetric RTP is *not* used, what is the value of requiring that a s=
ingle address:port be used for sending? The receiver, and intermediaries, w=
on't know what that address is until the media starts flowing.
>>>
>>> Also, why would it be forbidden to use the same address to send to mult=
iple bundle groups?
>>>
>>> The restriction makes sense with ICE, but in that case it is ICE provid=
ing the restriction. In the absence of ICE these restrictions seem arbitrar=
y and without motivation.
>>>
>>> (Note that this limitation is also mentioned in section 10.3.1.)
>>
>> I thought we agreed in Honolulu that we would use a single address:port =
also for sending.
>
> I don't recall exactly what was said.
>
> Here I'm asking if such a restriction adds any value and makes any sense.

First, the SDP attribute handling rules in draft-nandakumar-mmusic-sdp-mux-=
attributes are based on the media being multiplexed. It would be difficult =
e.g. for an intermediary to apply those, if e.g. one endpoint DOES send med=
ia from a single address:port, and the other endpoint doesn't (in which cas=
es the rules in draft-nandakumar-mmusic-sdp-mux-attributes don't apply). An=
d, the intermediary wouldn't even know whether an endpoint uses a single ad=
dress:port until the endpoint start sending media. So, it think mandating a=
 single address:port provides consistency, which makes the life easier espe=
cially for intermediaries (but perhaps also for endpoints).

Second, doesn't the definition of 5-tuple imply using a single address:port=
 also for sending?


------------


>>> Section 7.2:
>>>
>>> I presume that the "c=3D" line associated with a bundled "m=3D" line co=
uld either be a media-level c-line following the m-line, or a session-level=
 c-line preceding the first m-line. Is that right?
>>
>> Yes.
>>
>>> Perhaps that should be stated.
>>
>> Eventhough I think it's basic SDP, I can add some text.
>>
>> But, in that case one could argue that we have to say the same thing for=
 SDP attributes which can be both session-level and media-level...
>
> My question is really about the meaning of the general phrase: 'the "<som=
ething>=3D" line *associated with a bundled "m=3D" line.'
>
> To me it makes sense that it would include both session and media-level l=
ines. I'm just not certain that this will be obvious to everyone.

Do you have some clarification text in mind?

------------

>>> Section 8.5.2:
>>>
>>> I want to check what is intended here.
>>>
>>> Suppose I have previously established a bundle group. It has several m-=
lines. In the prior O/A all of those m-lines had the same address:port. Now=
 I want to change the bundle address.
>>>
>>> As I read the text in this section, I must change the address in *1* of=
 the m-lines, and suggest it as the offerer bundle address, but leave the o=
ld address in the other m-lines.
>>>
>>> That isn't what I had been thinking happened. I had been assuming that =
the address would be changed in all the m-lines.
>>>
>>> The consequence of this is that if the answerer doesn't want the=20
>>> change, it will have to reject the one changed m-line, and select the o=
ld address as the bundle address. If I was making the change because I am n=
o longer capable of using the old address then this won't work for me.
>>> It would be better for me to have the entire bundle rejected.
>>
>> The thinking has been that only an accepted BUNDLE address can be assign=
ed to multiple m- lines. Your suggestion would change that, because the new=
 address (when suggested in the offer) has not been accepted as a BUNDLE ad=
dress yet.
>
> First I just wanted to verify that is what is intended.
> That is now settled.
>
> Next is whether that is the best way to handle this.
>
>> Also, even if the offerer assigns the new address to all m- lines, and t=
he answerer rejects the offer, the offerer still has to fall back to the pr=
evious offerer BUNDLE address - no matter whether it can use it or not.
>
> The answerer could reject all the m-lines yet accept the offer.
>
> But yes, if the offer itself is rejected then there is need to fall back.
>
>> AND, assuming we go along with your suggestion, I guess that also means =
that if a new m- line is added (section 8.5.3), and if the=20
>> offerer wants the address of that m- line to become the new offerer BUND=
LE address, the offerer must also assign the address of the=20
>> new m- line also to the other m- lines in the BUNDLE group.
>
> True. That is an argument in favor of keeping things as they are.
>
> I guess you have convinced me.

I wasn't trying to convince you - I just wanted to make sure we take all th=
e impacts into consideration. I have learned that, what first may look like=
 a small and isolated change, may have big impacts throughout the document =
:)

The advantage of assigning the suggested new offerer BUNDLE address to all =
"m=3D" lines is that you don't have to send a BAS offer afterwards - which =
is a big advantage.

Of course, in the case of adding a new m- line to a BUNDLE group, if the an=
swerer does not accept it in the BUNDLE group, the answerer will have to re=
ject it. In that case, the offerer could send a new offer, and keep the new=
 "m=3D" line outside the BUNDLE group. But, IF the new "m=3D" line IS accep=
ted in the BUNDLE group, the BAS offer is not needed.

So, personally I have no problem with your suggestion. Mandating a shared a=
ddress (whether it's a previously selected offerer BUNDLE address, or a new=
 suggested offerer BUNDLE address) makes things more clear. I just want to =
make sure others are ok too, because it would be a technical change.

Regards,

Christer


From nobody Wed Dec 10 23:47:25 2014
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBA8A1AC41D for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 23:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.601
X-Spam-Level: *
X-Spam-Status: No, score=1.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 vwr8Jc2oI-y8 for <mmusic@ietfa.amsl.com>; Wed, 10 Dec 2014 23:47:20 -0800 (PST)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A02D1A1BFA for <mmusic@ietf.org>; Wed, 10 Dec 2014 23:47:19 -0800 (PST)
Received: by mail-lb0-f171.google.com with SMTP id n15so3713039lbi.16 for <mmusic@ietf.org>; Wed, 10 Dec 2014 23:47:17 -0800 (PST)
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=eW2vacT4zdz97S9cmah5sP3kSC/ZMAqq4SoMhkqYO3c=; b=MbFvVArqI4OW5Qlg6L71fr/4LVlTWVf+tYEmpXbl1puc8jZiHFC6bIyno9DHQKo3K3 +P11Iit3Q6SjdxGHUA81MMGKLRuBbaMWRtzJDSY/3fn8Tbyq14lKHrjTb1SSQ8QnGMiw MzuGFTK18BJv5vVcHHQUkIZiGxe6v9ObCWmyLIoiqgGcmHZyuYSiNE44K1U/8k2+46wZ xnOOgh3lVQQQF1jVgKPm4vW3yNCCRAdozp3+smIld2TF+F+dP7X1IRkM9qnhB4sZ3HQN CtpVJz+orZ6gY+yVkPoIu8Uivf8LnaaVu6nPQWtn8e/dA1e9LnVUKlcUiI8ESwQvCDr+ 1VbQ==
MIME-Version: 1.0
X-Received: by 10.112.146.37 with SMTP id sz5mr8209692lbb.27.1418284037799; Wed, 10 Dec 2014 23:47:17 -0800 (PST)
Received: by 10.112.46.66 with HTTP; Wed, 10 Dec 2014 23:47:17 -0800 (PST)
In-Reply-To: <54885F3D.4040508@ericsson.com>
References: <54885F3D.4040508@ericsson.com>
Date: Thu, 11 Dec 2014 13:17:17 +0530
Message-ID: <CAMRcRGQZ8aQep-8VehcYmfMPy_iEffzA0RYJA3SYGNMcYX+vwg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7b3a8b1e43845d0509ebfc51
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/PcQkNnhmK6oSy-0b7wuzdNcZlDw
Cc: "Suhas Nandakumar \(snandaku\)" <snandaku@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes-05 review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 07:47:23 -0000

--047d7b3a8b1e43845d0509ebfc51
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Ari

  Many thanks for the review. Please see inline

Thanks
Suhas

On Wed, Dec 10, 2014 at 8:27 PM, Ari Ker=C3=A4nen <ari.keranen@ericsson.com=
>
wrote:

> Hi Suhas,
>
> Here are my review comments on the SDP mux draft. Technically I think the
> doc is in pretty good shape, so these are mostly editorial issues.
>
>
> Cheers,
> Ari
>
>
> Abstract
>
>    In the RTCWEB WG, there is a need to use a
>    single 5-tuple for sending and receiving media associated with
>    multiple media descriptions ("m=3D" lines).
>
> Bundling is not RTCWEB-only feature, so I would rather drop the RTCWEB
> reference at least from the abstract, and write it in more general way
> (e.g., "in order to save resources and decrease connection setup times,
> these is a need..." like in section 3)
>
>
>    Such a requirement has
>    raised concerns over the semantic implications of the SDP attributes
>    associated with the RTP Media Streams multiplexed over a single
>    underlying transport layer flow.
>
> I think we are beyond "raised concerns" and have actually found out it wa=
s
> a real issue, so I would update the wording here.
>
>
[Suhas] - I will try to make it more general in the next version.


>
>    The scope of this specification is to provide a framework for
>    analyzing the multiplexing characteristics of SDP attributes.
>
> s/scope/purpose/
>
> [Suhas] - Accepted


> 1.  Introduction
>
>    Real-Time Communication in WEB-browsers (Rtcweb) framework requires
>    Real-time Transport Protocol (RTP) as the media transport protocol
>    and Session Description Protocol (SDP) [RFC4566] for describing and
>    negotiating multi-media communication sessions.
>
> This (and the following paragraph) should also be more general. Here
> perhaps you can use RTCWEB as an example of where such feature is require=
d,
> but adding an RTCWEB reference (e.g. the use case doc) would be good here
> for context.
>
> I think it would make sense also to reference the bundle draft already
> here and writing a sentence or two about the relationship with this draft=
.
>
> also:
>  s/requires/uses/
>  s/multi-media/multimedia/
>
> [Suhas] - Accpted

>
> 3.  Motivation
>
>    This imposes further restrictions on applicability of
>    these SDP attributes as they are defined today.
>
> Not sure where "these" here refers to. I guess that word can either be
> dropped, or clarify which attributes you mean.
>
>
[Suhas] - removed the word "these" for clarity.


>
> 4.  SDP Attribute Analysis Framework
>
> Would it make sense to have "before" and "after" in all the SDP examples
> (now there's only the "before" part)?
>
>
[Suhas] - I am not sure giving before and after examples be less confusing.
Since we are not defining new way of doing things to contrast the
approaches.


>
> 4.2.  Category: NOT RECOMMENDED
>
> Can/should we recommend here what to do in this case? Not multiplex? Not
> add such attributes? Either way?
>
>
[Suhas] - the definition for the category already encompasses this as
highlighted below.
"Attributes that are *recommended against multiplexing* since their usage
under multiplexing might lead to incorrect behavior."


>
> 4.3.  Category: IDENTICAL
>
>    Attributes that MUST be identical across all the media descriptions
>    being multiplexed.
>
> Maybe clarify that attributes and their *values* (if exist) must be
> identical.
>
>
>         <allOneLine>
>         a=3Dzrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2
>         df881ae642c371ba46df
>         </allOneLine>
>
> The draft uses now 3 different ways of presenting too long SDP lines (see
> e.g., 4.5, 4.7 and 14.3.1.1). I guess they are from the defining RFCs, bu=
t
> I would rather see uniform style across this document. Personally I prefe=
r
> the style of section 4.5 (2 char indent).
>
>
[Suhas] - Will move all the examples to reflect the format in Section 4.5


> 4.4.  Category: SUM
>
> Should clarify where do you put the SUM'ed value.
>

[Suhas] .. Since the calculated SUM value is expected to be consumed in the
software processing SDP, the definition of this category already captures
this fact.


>
>
> 4.5.  Category: TRANSPORT
>
>    Attributes that can be set normally for multiple items in a
>    multiplexed group but the software MUST pick just one of the
>    attribute of the given type for use.  The one chosen is the attribute
>    associated with the "m=3D" line that represents the information being
>    used for the transport of the RTP.
>
> How do you "pick" the one; by repeating the same value for each bundled
> "m=3D"-line?
>
> Also, do we need to consider non-RTP cases too?
>
> [Suhas] - The expectation is to repeat as per the BUNDLE spec. Hence we
have just added the way such a value is chosen but not the way the chose
value is represented in the SDP as it is defined in the BUNDLE spec.


>
> 4.8.  Category: SPECIAL
>
>    Attributes where the text in the source draft must be consulted for
>    further handling when multiplexed.
>
> s/source draft/specification defining the attribute/
>

[Suhas] - Accepted

>
>
> 5.9.  RFC6773 - DCCP-UDP Encapsulation
>
>    Since RFC6773 is about tunneling DCCP in UDP, with the UDP port being
>    the port of the DCCP en-/de-capsulation service.
>
> Can't parse the sentence. Something missing here? Or extra "since"?
>
> [Suhas] -Removed since since it clarifies the text better.


>
>    This MAY or MAY NOT work depending on the
>    nature of DCCP encapsulations and ports choses thus rendering it to
>    be very application dependent.
>
> Lower-case (non-RFC2119) "may" and "may not" would be appropriate here.
> Also s/ports choses/port choices/?
>

[Suhas] - Done

>
>
> 5.12.  RFC5245 - Interactive Connectivity Establishment (ICE)
>
> Since the ICE candidate behavior is already specified in the bundle draft
> at least reference there would be good? Also please make sure that these
> stay in sync with what bundle has until it's an RFC.
>
> [Suhas] - BUNDLE spec provides O/A procedures for ICE but does not provid=
e
the category assignments for the ICE attributes.


>
> 5.21.  RFC6230 - Media Control Channel Framework
>
>            | cfw-id  | Not Applicable  | M     | NORMAL       |
>
> Should that be "Not Impacted" as in other NORMAL cases?
>

[Suhas] - Accepted

>
>
> 5.39.  RFC6189 - ZRTP
>
>    | zrtp-hash  | Complicates if all the        | M     | NOT          |
>    |            | m=3Dlines are not authenticated |       | RECOMMENDED  =
|
>    |            | as given in the example below |       |              |
>
> Where's the example? You mean the one in section 4.2?
>
> [Suhas] - The example SDP was removed from this section to not duplicate
but I had forgotten the delete the reference to the example in here. Hence,
will remove the example refernce


>
> 5.46.  RFC2326 - Real Time Streaming Protocol
>
> Could mention here briefly why RTSP is not supported (similar to the next
> section).
>
> [Suhas] - Done

>
> 5.50.  3GPP TS 183.063
>
>    | PSCid               | Not Impacted | Not-Applicable | NORMAL      |
>
> The "Not-Applicable" level is not defined. Could add that to section 5 or
> explain here and in 5.58.
>
> [Suhas] - Will add appropriate SDP attribute levels to these sections

>
> 7.1.  RFC4585 - RTP/AVPF
>
> Are the "Attr Name" here really attribute names or should one use some
> other name in this case?
>
> [Suhas] - Will clean up the column name for consistency

>
> 7.3.  RFC6285 - Unicast-Based RAMS
>
> This one was missing the "intro description". Could add something brief
> for consistency with rest of the doc. Same for 7.6, 9.1, 9.2, 10.x (I'll
> leave it up to you where you consider it worthwhile adding).
>
> [Suhas] - Agreed, I will add the intro text for all these sections. It
helps readability as well.


> And is the "Attr Name" field here just "Name" intentionally? Same in
> following two sections.
>
>
> 13.1.  RFC5109 - RTP Payload Format for Generic FEC
>
>    Draft draft-lennox-payload-ulp-ssrc-mux proposes a simple fix to make
>
> This is a bit tricky. This should be a proper reference, but referencing
> expired drafts is not a good practice either. I would lean towards taking
> this sentence away since (if?) the fix is not going forward at the IETF.
>
> [Suhas] - Removed this reference.

>
> 14.2.1.  Recommendation - Procedures for Potential Configuration Pairing
>
>    that are consistent across all the bundled media descriptions.
>
> Could add "bundled media" to the terminology section.
>
> [Suhas] removed bundled with multiplexed to keep it uniform

>
> 15.  IANA Considerations
>
> It would be great if someone double-checked that the "Mux Category"
> entries here match to the text. Probably a simple script could do that to=
o.
>
> [Suhas]  - I can work on this to be sure

> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--047d7b3a8b1e43845d0509ebfc51
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Ari<div><br></div><div>=C2=A0 Many thanks for the re=
view. Please see inline</div><div><br></div><div>Thanks</div><div>Suhas</di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Dec 10,=
 2014 at 8:27 PM, Ari Ker=C3=A4nen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
ari.keranen@ericsson.com" target=3D"_blank">ari.keranen@ericsson.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border=
-left-style:solid;padding-left:1ex">Hi Suhas,<br>
<br>
Here are my review comments on the SDP mux draft. Technically I think the d=
oc is in pretty good shape, so these are mostly editorial issues.<br>
<br>
<br>
Cheers,<br>
Ari<br>
<br>
<br>
Abstract<br>
<br>
=C2=A0 =C2=A0In the RTCWEB WG, there is a need to use a<br>
=C2=A0 =C2=A0single 5-tuple for sending and receiving media associated with=
<br>
=C2=A0 =C2=A0multiple media descriptions (&quot;m=3D&quot; lines).<br>
<br>
Bundling is not RTCWEB-only feature, so I would rather drop the RTCWEB refe=
rence at least from the abstract, and write it in more general way (e.g., &=
quot;in order to save resources and decrease connection setup times, these =
is a need...&quot; like in section 3)<br>
<br>
<br>
=C2=A0 =C2=A0Such a requirement has<br>
=C2=A0 =C2=A0raised concerns over the semantic implications of the SDP attr=
ibutes<br>
=C2=A0 =C2=A0associated with the RTP Media Streams multiplexed over a singl=
e<br>
=C2=A0 =C2=A0underlying transport layer flow.<br>
<br>
I think we are beyond &quot;raised concerns&quot; and have actually found o=
ut it was a real issue, so I would update the wording here.<br>
<br></blockquote><div><br></div><div>[Suhas] - I will try to make it more g=
eneral in the next version.</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-lef=
t-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0The scope of this specification is to provide a framework for<=
br>
=C2=A0 =C2=A0analyzing the multiplexing characteristics of SDP attributes.<=
br>
<br>
s/scope/purpose/<br><br></blockquote><div>[Suhas] - Accepted=C2=A0</div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
1.=C2=A0 Introduction<br>
<br>
=C2=A0 =C2=A0Real-Time Communication in WEB-browsers (Rtcweb) framework req=
uires<br>
=C2=A0 =C2=A0Real-time Transport Protocol (RTP) as the media transport prot=
ocol<br>
=C2=A0 =C2=A0and Session Description Protocol (SDP) [RFC4566] for describin=
g and<br>
=C2=A0 =C2=A0negotiating multi-media communication sessions.<br>
<br>
This (and the following paragraph) should also be more general. Here perhap=
s you can use RTCWEB as an example of where such feature is required, but a=
dding an RTCWEB reference (e.g. the use case doc) would be good here for co=
ntext.<br>
<br>
I think it would make sense also to reference the bundle draft already here=
 and writing a sentence or two about the relationship with this draft.<br>
<br>
also:<br>
=C2=A0s/requires/uses/<br>
=C2=A0s/multi-media/multimedia/<br>
<br></blockquote><div>[Suhas] - Accpted=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
3.=C2=A0 Motivation<br>
<br>
=C2=A0 =C2=A0This imposes further restrictions on applicability of<br>
=C2=A0 =C2=A0these SDP attributes as they are defined today.<br>
<br>
Not sure where &quot;these&quot; here refers to. I guess that word can eith=
er be dropped, or clarify which attributes you mean.<br>
<br></blockquote><div><br></div><div>[Suhas] - removed the word &quot;these=
&quot; for clarity.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:=
rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
4.=C2=A0 SDP Attribute Analysis Framework<br>
<br>
Would it make sense to have &quot;before&quot; and &quot;after&quot; in all=
 the SDP examples (now there&#39;s only the &quot;before&quot; part)?<br>
<br></blockquote><div><br></div><div>[Suhas] - I am not sure giving before =
and after examples be less confusing. Since we are not defining new way of =
doing things to contrast the approaches.=C2=A0</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">
<br>
4.2.=C2=A0 Category: NOT RECOMMENDED<br>
<br>
Can/should we recommend here what to do in this case? Not multiplex? Not ad=
d such attributes? Either way?<br>
<br></blockquote><div><br></div><div>[Suhas] - the definition for the categ=
ory already encompasses this as highlighted below.</div><div>&quot;Attribut=
es that are <b>recommended against multiplexing</b> since their usage under=
 multiplexing might lead to incorrect behavior.&quot;</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">
<br>
4.3.=C2=A0 Category: IDENTICAL<br>
<br>
=C2=A0 =C2=A0Attributes that MUST be identical across all the media descrip=
tions<br>
=C2=A0 =C2=A0being multiplexed.<br>
<br>
Maybe clarify that attributes and their *values* (if exist) must be identic=
al.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;allOneLine&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a=3Dzrtp-hash:1.10 fe30efd02423cb054e50efd02487=
42<u></u>ac7a52c8f91bc2<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 df881ae642c371ba46df<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;/allOneLine&gt;<br>
<br>
The draft uses now 3 different ways of presenting too long SDP lines (see e=
.g., 4.5, 4.7 and 14.3.1.1). I guess they are from the defining RFCs, but I=
 would rather see uniform style across this document. Personally I prefer t=
he style of section 4.5 (2 char indent).<br>
<br></blockquote><div>=C2=A0</div><div>[Suhas] - Will move all the examples=
 to reflect the format in Section 4.5</div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;=
border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex=
">
4.4.=C2=A0 Category: SUM<br>
<br>
Should clarify where do you put the SUM&#39;ed value.<br></blockquote><div>=
<br></div><div>[Suhas] .. Since the calculated SUM value is expected to be =
consumed in the software processing SDP, the definition of this category al=
ready captures this fact.</div><div>=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
4.5.=C2=A0 Category: TRANSPORT<br>
<br>
=C2=A0 =C2=A0Attributes that can be set normally for multiple items in a<br=
>
=C2=A0 =C2=A0multiplexed group but the software MUST pick just one of the<b=
r>
=C2=A0 =C2=A0attribute of the given type for use.=C2=A0 The one chosen is t=
he attribute<br>
=C2=A0 =C2=A0associated with the &quot;m=3D&quot; line that represents the =
information being<br>
=C2=A0 =C2=A0used for the transport of the RTP.<br>
<br>
How do you &quot;pick&quot; the one; by repeating the same value for each b=
undled &quot;m=3D&quot;-line?<br>
<br>
Also, do we need to consider non-RTP cases too?<br><br></blockquote><div>[S=
uhas] - The expectation is to repeat as per the BUNDLE spec. Hence we have =
just added the way such a value is chosen but not the way the chose value i=
s represented in the SDP as it is defined in the BUNDLE spec.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">
<br>
4.8.=C2=A0 Category: SPECIAL<br>
<br>
=C2=A0 =C2=A0Attributes where the text in the source draft must be consulte=
d for<br>
=C2=A0 =C2=A0further handling when multiplexed.<br>
<br>
s/source draft/specification defining the attribute/<br></blockquote><div><=
br></div><div>[Suhas] - Accepted=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-colo=
r:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
5.9.=C2=A0 RFC6773 - DCCP-UDP Encapsulation<br>
<br>
=C2=A0 =C2=A0Since RFC6773 is about tunneling DCCP in UDP, with the UDP por=
t being<br>
=C2=A0 =C2=A0the port of the DCCP en-/de-capsulation service.<br>
<br>
Can&#39;t parse the sentence. Something missing here? Or extra &quot;since&=
quot;?<br><br></blockquote><div>[Suhas] -Removed since since it clarifies t=
he text better.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(=
204,204,204);border-left-style:solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0This MAY or MAY NOT work depending on the<br>
=C2=A0 =C2=A0nature of DCCP encapsulations and ports choses thus rendering =
it to<br>
=C2=A0 =C2=A0be very application dependent.<br>
<br>
Lower-case (non-RFC2119) &quot;may&quot; and &quot;may not&quot; would be a=
ppropriate here. Also s/ports choses/port choices/?<br></blockquote><div><b=
r></div><div>[Suhas] - Done=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
5.12.=C2=A0 RFC5245 - Interactive Connectivity Establishment (ICE)<br>
<br>
Since the ICE candidate behavior is already specified in the bundle draft a=
t least reference there would be good? Also please make sure that these sta=
y in sync with what bundle has until it&#39;s an RFC.<br>
<br></blockquote><div>[Suhas] - BUNDLE spec provides O/A procedures for ICE=
 but does not provide the category assignments for the ICE attributes.</div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">
<br>
5.21.=C2=A0 RFC6230 - Media Control Channel Framework<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| cfw-id=C2=A0 | Not Applicable=C2=
=A0 | M=C2=A0 =C2=A0 =C2=A0| NORMAL=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
<br>
Should that be &quot;Not Impacted&quot; as in other NORMAL cases?<br></bloc=
kquote><div><br></div><div>[Suhas] - Accepted=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
5.39.=C2=A0 RFC6189 - ZRTP<br>
<br>
=C2=A0 =C2=A0| zrtp-hash=C2=A0 | Complicates if all the=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 | M=C2=A0 =C2=A0 =C2=A0| NOT=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br=
>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | m=3Dlines are not=
 authenticated |=C2=A0 =C2=A0 =C2=A0 =C2=A0| RECOMMENDED=C2=A0 |<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | as given in the e=
xample below |=C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 |<br>
<br>
Where&#39;s the example? You mean the one in section 4.2?<br>
<br></blockquote><div>[Suhas] - The example SDP was removed from this secti=
on to not duplicate but I had forgotten the delete the reference to the exa=
mple in here. Hence, will remove the example refernce</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;=
padding-left:1ex">
<br>
5.46.=C2=A0 RFC2326 - Real Time Streaming Protocol<br>
<br>
Could mention here briefly why RTSP is not supported (similar to the next s=
ection).<br>
<br></blockquote><div>[Suhas] - Done=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
5.50.=C2=A0 3GPP TS 183.063<br>
<br>
=C2=A0 =C2=A0| PSCid=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
| Not Impacted | Not-Applicable | NORMAL=C2=A0 =C2=A0 =C2=A0 |<br>
<br>
The &quot;Not-Applicable&quot; level is not defined. Could add that to sect=
ion 5 or explain here and in 5.58.<br>
<br></blockquote><div>[Suhas] - Will add appropriate SDP attribute levels t=
o these sections=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,20=
4);border-left-style:solid;padding-left:1ex">
<br>
7.1.=C2=A0 RFC4585 - RTP/AVPF<br>
<br>
Are the &quot;Attr Name&quot; here really attribute names or should one use=
 some other name in this case?<br>
<br></blockquote><div>[Suhas] - Will clean up the column name for consisten=
cy=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">
<br>
7.3.=C2=A0 RFC6285 - Unicast-Based RAMS<br>
<br>
This one was missing the &quot;intro description&quot;. Could add something=
 brief for consistency with rest of the doc. Same for 7.6, 9.1, 9.2, 10.x (=
I&#39;ll leave it up to you where you consider it worthwhile adding).<br>
<br></blockquote><div>[Suhas] - Agreed, I will add the intro text for all t=
hese sections. It helps readability as well.</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wid=
th:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-l=
eft:1ex">
And is the &quot;Attr Name&quot; field here just &quot;Name&quot; intention=
ally? Same in following two sections.<br>
<br>
<br>
13.1.=C2=A0 RFC5109 - RTP Payload Format for Generic FEC<br>
<br>
=C2=A0 =C2=A0Draft draft-lennox-payload-ulp-ssrc-<u></u>mux proposes a simp=
le fix to make<br>
<br>
This is a bit tricky. This should be a proper reference, but referencing ex=
pired drafts is not a good practice either. I would lean towards taking thi=
s sentence away since (if?) the fix is not going forward at the IETF.<br>
<br></blockquote><div>[Suhas] - Removed this reference.=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wid=
th:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-l=
eft:1ex">
<br>
14.2.1.=C2=A0 Recommendation - Procedures for Potential Configuration Pairi=
ng<br>
<br>
=C2=A0 =C2=A0that are consistent across all the bundled media descriptions.=
<br>
<br>
Could add &quot;bundled media&quot; to the terminology section.<br>
<br></blockquote><div>[Suhas] removed bundled with multiplexed to keep it u=
niform=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">
<br>
15.=C2=A0 IANA Considerations<br>
<br>
It would be great if someone double-checked that the &quot;Mux Category&quo=
t; entries here match to the text. Probably a simple script could do that t=
oo.<br>
<br></blockquote><div>[Suhas] =C2=A0- I can work on this to be sure=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">
______________________________<u></u>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/mmusic</a><br>
</blockquote></div><br></div></div>

--047d7b3a8b1e43845d0509ebfc51--


From nobody Thu Dec 11 01:39:53 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016E71ACD92; Thu, 11 Dec 2014 01:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 963A_v-fp9nY; Thu, 11 Dec 2014 01:39:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF15C1ACD88; Thu, 11 Dec 2014 01:39:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141211093949.21068.72428.idtracker@ietfa.amsl.com>
Date: Thu, 11 Dec 2014 01:39:49 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/eBk8dBcrWsroHeHNSdlM5XGQ2oI
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 09:39:51 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : A Framework for SDP Attributes when Multiplexing
        Author          : Suhas Nandakumar
	Filename        : draft-ietf-mmusic-sdp-mux-attributes-06.txt
	Pages           : 90
	Date            : 2014-12-11

Abstract:
   The Session Description Protocol (SDP) provides mechanisms to
   describe attributes of multimedia sessions and of individual media
   streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
   multimedia session.  [I-D.ietf-mmusic-sdp-bundle-negotiation]
   provides SDP extensions to negotiate the usage of single 5-tuple for
   sending and receiving media associated with multiple media
   descriptions ("m=" lines).  Such a mechanism has made it necessary to
   understand the semantic implications of the SDP attributes associated
   with the RTP Media Streams multiplexed over a single underlying
   transport layer flow.

   The purpose of this specification is to provide a framework for
   analyzing the multiplexing characteristics of SDP attributes.  This
   specification also categorizes the existing SDP attributes based on
   the framework described herein.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Dec 11 01:44:39 2014
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7941ACD83 for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 01:44:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 pX0RpZRwYTPY for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 01:44:33 -0800 (PST)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B78191ACD79 for <mmusic@ietf.org>; Thu, 11 Dec 2014 01:44:32 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id g10so2707837pdj.34 for <mmusic@ietf.org>; Thu, 11 Dec 2014 01:44:32 -0800 (PST)
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 :content-type; bh=I8pQYLP8uBbpQR702Ysa/OexPY4+JaRt0xlqfzjklrU=; b=Gdw8FPvl7M1ebzWgvXn60IouV6aMSZmcme+TOG1aMuwLA1o9kOOf10a1YWyI8L+TYG VUofMOpY2F+0cq2wACzcxlDNcR7T6G8C5bAm4JRRbWek5498BxuOZ7ReWiMngJA/xhgK Z5jahN4x6ZYYLA4MXS/qujltLZu1H1oKfU8D2Fa5RuOcoROIbdxZq7GAxYm/qkueXJeq J6L9CIsuDkTAY8f9G/2m3r6JywyA1K4sGeWxPL08sC2VFs6iAmXAPznKz9dgNP2vHbLk 8SAOLmmP9QmGKBYtqPrjd/WagDnfDizwcAnbC+9DzgDQkpdKATJ1W+0ML5hVB6QAxzBJ P8/A==
MIME-Version: 1.0
X-Received: by 10.68.91.37 with SMTP id cb5mr15905119pbb.22.1418291072019; Thu, 11 Dec 2014 01:44:32 -0800 (PST)
Received: by 10.70.60.201 with HTTP; Thu, 11 Dec 2014 01:44:31 -0800 (PST)
In-Reply-To: <20141211093949.21068.72428.idtracker@ietfa.amsl.com>
References: <20141211093949.21068.72428.idtracker@ietfa.amsl.com>
Date: Thu, 11 Dec 2014 15:14:31 +0530
Message-ID: <CAMRcRGRTRzQyNx=OcWh2RFxS__khY1P8pvm1WvXwr=34rDcJ2w@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b676e728932460509ed9f36
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/O8Fm3EaojwSH_um4gFAfRoU5-Hk
Subject: [MMUSIC] Fwd: I-D Action: draft-ietf-mmusic-sdp-mux-attributes-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 09:44:37 -0000

--047d7b676e728932460509ed9f36
Content-Type: text/plain; charset=UTF-8

Hello All

  This version incorporates review comments from Christian Grooves and Ari
Keranen

Cheers
Suhas

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Thu, Dec 11, 2014 at 3:09 PM
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-06.txt
To: i-d-announce@ietf.org
Cc: mmusic@ietf.org


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Multiparty Multimedia Session Control
Working Group of the IETF.

        Title           : A Framework for SDP Attributes when Multiplexing
        Author          : Suhas Nandakumar
        Filename        : draft-ietf-mmusic-sdp-mux-attributes-06.txt
        Pages           : 90
        Date            : 2014-12-11

Abstract:
   The Session Description Protocol (SDP) provides mechanisms to
   describe attributes of multimedia sessions and of individual media
   streams (e.g., Real-time Transport Protocol (RTP) sessions) within a
   multimedia session.  [I-D.ietf-mmusic-sdp-bundle-negotiation]
   provides SDP extensions to negotiate the usage of single 5-tuple for
   sending and receiving media associated with multiple media
   descriptions ("m=" lines).  Such a mechanism has made it necessary to
   understand the semantic implications of the SDP attributes associated
   with the RTP Media Streams multiplexed over a single underlying
   transport layer flow.

   The purpose of this specification is to provide a framework for
   analyzing the multiplexing characteristics of SDP attributes.  This
   specification also categorizes the existing SDP attributes based on
   the framework described herein.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

--047d7b676e728932460509ed9f36
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello All</div><div><br></div><div>=C2=A0 This versio=
n incorporates review comments from Christian Grooves and Ari Keranen</div>=
<div><br></div><div>Cheers</div><div>Suhas</div><br><div class=3D"gmail_quo=
te">---------- Forwarded message ----------<br>From: <b class=3D"gmail_send=
ername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.o=
rg">internet-drafts@ietf.org</a>&gt;</span><br>Date: Thu, Dec 11, 2014 at 3=
:09 PM<br>Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attribute=
s-06.txt<br>To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.=
org</a><br>Cc: <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br><b=
r><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Multiparty Multimedia Session Contro=
l Working Group of the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 A Framework for SDP Attributes when Multiplexing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Suha=
s Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-sdp-mux-attributes-06.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 90<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2014-12-11<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The Session Description Protocol (SDP) provides mechanisms to<=
br>
=C2=A0 =C2=A0describe attributes of multimedia sessions and of individual m=
edia<br>
=C2=A0 =C2=A0streams (e.g., Real-time Transport Protocol (RTP) sessions) wi=
thin a<br>
=C2=A0 =C2=A0multimedia session.=C2=A0 [I-D.ietf-mmusic-sdp-bundle-negotiat=
ion]<br>
=C2=A0 =C2=A0provides SDP extensions to negotiate the usage of single 5-tup=
le for<br>
=C2=A0 =C2=A0sending and receiving media associated with multiple media<br>
=C2=A0 =C2=A0descriptions (&quot;m=3D&quot; lines).=C2=A0 Such a mechanism =
has made it necessary to<br>
=C2=A0 =C2=A0understand the semantic implications of the SDP attributes ass=
ociated<br>
=C2=A0 =C2=A0with the RTP Media Streams multiplexed over a single underlyin=
g<br>
=C2=A0 =C2=A0transport layer flow.<br>
<br>
=C2=A0 =C2=A0The purpose of this specification is to provide a framework fo=
r<br>
=C2=A0 =C2=A0analyzing the multiplexing characteristics of SDP attributes.=
=C2=A0 This<br>
=C2=A0 =C2=A0specification also categorizes the existing SDP attributes bas=
ed on<br>
=C2=A0 =C2=A0the framework described herein.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attri=
butes/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-mmusi=
c-sdp-mux-attributes/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-=
06" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-=
attributes-06</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-sdp-mux-att=
ributes-06" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf=
-mmusic-sdp-mux-attributes-06</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div>

--047d7b676e728932460509ed9f36--


From nobody Thu Dec 11 10:37:58 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6340A1A87E2 for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:37:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_44=0.6, SPF_PASS=-0.001] 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 gELPENdExEOl for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:37:54 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76AF31A87B1 for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:37:54 -0800 (PST)
Received: by mail-oi0-f46.google.com with SMTP id h136so4062276oig.5 for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:37:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=lu1T9haOJj2NfK0KJ2GcvFAMOfXyX5kHpjTYHc+ds6A=; b=jj+EqkC3Nryj9rfGDOtRuaOmNYyLLuEO93bP2Tqm1G+mNtK58rR1ju/Ia5s07jpCrt wcVz357L6Uf/e9vhPnfhUm/XIKr2Gh3gSUdUTpuqtCDVvUgWljdceUC6zOA9vPMXlen9 8TnK7ydTC8G2XzbFroj9Mh8Mb1+yzW2D3upWydNs/yWtj35m2NZLhX1bhiIaVARkGYJv v3UcLhKDORFegiL48hRzhErQb57fanPuK6oDjl94IZPA9jMKJlwkYo/VQUZLzqniODAe mZFa5VytGeV3oajgz2Zk1P0MxikA6Rjvg0hlhVH4KB7ggXLKxOw2kgljQFvZLxXhQ+Be HZ7g==
MIME-Version: 1.0
X-Received: by 10.202.212.82 with SMTP id l79mr6988017oig.12.1418323073786; Thu, 11 Dec 2014 10:37:53 -0800 (PST)
Received: by 10.202.107.19 with HTTP; Thu, 11 Dec 2014 10:37:53 -0800 (PST)
Date: Thu, 11 Dec 2014 10:37:53 -0800
Message-ID: <CABkgnnXmgfEmN8ZS-Q41hV=Fif4uoGSCN0S1vn_deViYph6eCw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, Harald Tveit Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/42QIutWRDo0VgeOWDnNcWaEbFNQ
Subject: [MMUSIC] msid and a=ssrc
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 18:37:55 -0000

Appendix B of the msid draft really equivocates about whether the
"msid" attribute is valid for use in source specific attributes or
not.  The IANA section doesn't describe msid as a source specific
attribute, but the existence of appendix B is very confusing.

Is `a=ssrc:123 msid:blah blah` a valid SDP construct?  If so, what
does it mean?  If not, can appendix B be deleted?


From nobody Thu Dec 11 10:42:07 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D361A0636 for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 HlZpzGmC1hMN for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:42:05 -0800 (PST)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EB001A6FC0 for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:42:05 -0800 (PST)
Received: by mail-qc0-f173.google.com with SMTP id i17so4353124qcy.18 for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:42:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=NX/Hb4xr5qqHp/iXUreymwqfxAbivgBtO3yYdwGEWa8=; b=ubPWoHySQKNQM4NiZSXub8U5J7dZlrVBBXdd5G2pP8LVzoUbANHFJWfznkbHUCTj3f szoJ5AMe6flRULIFYCV8lI0yp32bQCQq+gD3ElvjMDxE+ywDd1JpSTYjpiinObdfWj6C puh2cGMhyqTlhHpi/VmsVKnpR32YbQqCMrqAe/Snz6tGaC7bIYytXiavXmrEu6jEH77K D08ILxm7IyV5g8KJ5J/UIbGH63edgcENtQqNinYb80qXkVcahjqoEzuVqqgxb+XERIC3 33pVlGOUt8IYJUourbQB/LR12MVsUWJo/beUrh+gvrl6AIMi0US4an2cJKkmgF1GSQHs RKDw==
MIME-Version: 1.0
X-Received: by 10.202.225.197 with SMTP id y188mr7032960oig.94.1418323324259;  Thu, 11 Dec 2014 10:42:04 -0800 (PST)
Received: by 10.202.107.19 with HTTP; Thu, 11 Dec 2014 10:42:04 -0800 (PST)
Date: Thu, 11 Dec 2014 10:42:04 -0800
Message-ID: <CABkgnnXR==KsiDBKhABi_s6j_0Ft-_UU70=a+spNz818VezRrA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/enyd3ozJXLaV5fJ3l2ugAnw-zpk
Subject: [MMUSIC] MSID nits
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 18:42:06 -0000

If this were on github, I'd send a PR...

Is this the right name for msid: "Media stream group Identifier" ?
Even accounting for the strange capitalization, isn't it a "media
stream identifier with optional group identifier" ?

OLD:
   This document requests IANA to create a new registry called
   "Semantics for the msid-semantic SDP attribute", which should have
   exactly the same rules as for the "Semantics for the ssrc-group SDP
   attribute" registry (Expert Review), and to register the "WMS"
   semantic within this new registry.
NEW:
   This document requests IANA to create a new registry called
   "Semantics for the msid-semantic SDP attribute" in the "Session
   Description Protocol (SDP) Parameters" group.  This registry
   operates on the Expert Review policy [RFC5226].

   The "WMS" semantic is registered in this new registry.

I'd also recommend section headings to separate the two new attributes
from the creation of the semantic registry.


From nobody Thu Dec 11 10:51:08 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06BD01A6F01 for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 iwG4KtpX7UIp for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 10:51:06 -0800 (PST)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DFC01A701C for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:50:55 -0800 (PST)
Received: by mail-oi0-f54.google.com with SMTP id u20so4097208oif.41 for <mmusic@ietf.org>; Thu, 11 Dec 2014 10:50:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=SPAga5r5qEI33Rh80Z+ecj6Yixg2ZvrwU0ZuU8qAJGw=; b=B/9bulgXLRw8m3X5PcdOeWveJL67nWBeSxJdCx6xqGGyEqxljDFeRda2mlUz/2nZD1 LYzxoEFCnoViXPo2iT3zDC608u3GzCST3rnLdhSR2o9/gtvMqTY2uT0ZvHivcYi+wdOp ijSBZvHJMP1KzkiSZnlVATwGiK2hfTzyjZdy9G8FwVrgdAtzJGTEUEiT1iSDqH/LaucN K++qqYYoBUr4NYXNf2GOVNgkOAoDVXISrAiyMEfn9g+eTV+kh9Il8CHwd9iRFp9BEf5N ChMnErD5PXRX7NejgumwGUN+9yAeLZXi5Hujj/SXZTZaChDBcD1JCMxRbjaZQHaEu4mw f+vg==
MIME-Version: 1.0
X-Received: by 10.182.97.66 with SMTP id dy2mr7393041obb.30.1418323854920; Thu, 11 Dec 2014 10:50:54 -0800 (PST)
Received: by 10.202.107.19 with HTTP; Thu, 11 Dec 2014 10:50:54 -0800 (PST)
Date: Thu, 11 Dec 2014 10:50:54 -0800
Message-ID: <CABkgnnWsHWuc=bnVWkYj0W1Lkpkn88sOaDESDBvEjoGF7wruqg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/8ruynsuWc8UZA2bC3WijlRE6vfo
Subject: [MMUSIC] MSID and mapping to tracks and streams
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 18:51:08 -0000

   The value of the "identifier" field in the msid consists of the "id"
   attribute of a MediaStream, as defined in its WebIDL specification.

   The value of the "appdata" field in the msid consists of the "id"
   attribute of a MediaStreamTrack, as defined in its WebIDL
   specification.

I think that this is backwards. The media section (m=) corresponds to
a track, not a stream.  The MediaStream is the secondary identifier.

I'd have thought that this was merely personal bias, until I read this:

   The identifier is a string of ASCII characters that are legal in a
   "token", consisting of between 1 and 64 characters.  It MUST be
   unique among the identifier values used in the same SDP session.  It
   is RECOMMENDED that it is generated using a random-number generator.

This rule, as specified and in combination with the aforementioned,
would absolutely prevent the use of multiple tracks from the same
stream (i.e., the most common case in existence).

Also, this is mightly confusing to me:

   [...]  Once negotiation has completed on a
   session, there is no memory apart from the currently valid SDP
   descriptions; an msid "identifier" value that appears in a later
   negotiation will be taken to refer to a new MediaStream.

I have no idea what this might be saying.  I can imagine a whole lot
of things that might be said here: "a track (not stream) that is bound
to a given media section is unaffected by changes in the msid values
in that media section during renegotiation" or "a track on the sending
side that is bound to a media section, then subsequently swapped out
(see replaceTrack) for another, MAY cause the msid values to change in
subsequent renegotiations, but this does not result in action from the
receiving side".


From nobody Thu Dec 11 15:48:13 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE2B1A9042 for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 15:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level: 
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 7dTCLWTm7-Md for <mmusic@ietfa.amsl.com>; Thu, 11 Dec 2014 15:48:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id DAA461A9040 for <mmusic@ietf.org>; Thu, 11 Dec 2014 15:48:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 43681181CD8; Thu, 11 Dec 2014 15:48:07 -0800 (PST)
To: schulzrinne@cs.columbia.edu, anup@netscape.com, robla@real.com, rlb@ipv.sx, alissa@cooperw.in, fandreas@cisco.com, ari.keranen@ericsson.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20141211234807.43681181CD8@rfc-editor.org>
Date: Thu, 11 Dec 2014 15:48:07 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/f7BsrOzgKD3Qq7hDDTWZFyR_hwc
Cc: juliusfriedman@gmail.com, mmusic@ietf.org, rfc-editor@rfc-editor.org
Subject: [MMUSIC] [Technical Errata Reported] RFC2326 (4199)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Dec 2014 23:48:12 -0000

The following errata report has been submitted for RFC2326,
"Real Time Streaming Protocol (RTSP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=2326&eid=4199

--------------------------------------
Type: Technical
Reported by: Julius Friedman <juliusfriedman@gmail.com>

Section: 4

Original Text
-------------
4 RTSP Message

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (RFC 2279 [21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See RFC 2279 [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.

Corrected Text
--------------


4 RTSP Message

   RTSP is a text-based protocol and uses the ISO 10646 character set in
   UTF-8 encoding (RFC 2279 [21]). Lines are terminated by CRLF, but
   receivers should be prepared to also interpret CR and LF by
   themselves as line terminators.

     Text-based protocols make it easier to add optional parameters in a
     self-describing manner. Since the number of parameters and the
     frequency of commands is low, processing efficiency is not a
     concern. Text-based protocols, if done carefully, also allow easy
     implementation of research prototypes in scripting languages such
     as Tcl, Visual Basic and Perl.

     The 10646 character set avoids tricky character set switching, but
     is invisible to the application as long as US-ASCII is being used.
     This is also the encoding used for RTCP. ISO 8859-1 translates
     directly into Unicode with a high-order octet of zero. ISO 8859-1
     characters with the most-significant bit set are represented as
     1100001x 10xxxxxx. (See RFC 2279 [21])

   RTSP messages can be carried over any lower-layer transport protocol
   that is 8-bit clean.

   Requests contain methods, the object the method is operating upon and
   parameters to further describe the method. Methods are idempotent,
   unless otherwise noted. Methods are also designed to require little
   or no state maintenance at the media server.

*Please note the hexadecimal octet 0x36 should not be included in any 
part of a RTSP message, if present it should be replaced with binary 
escaped sequence as defined in: <consensus>*.

Notes
-----
Section [15.1 Base Syntax] makes the following definitions:
..
safe               =  "$" | "-" | "_" | "." | "+"
..
reserved           =  ";" | "/" | "?" | ":" | "@" | "&" | "="
extra              =  "!" | "*" | "$'$" | "(" | ")" | ","
unreserved         =  alpha | digit | safe | extra
xchar              =  unreserved | reserved | escape

However it doesn't explicitly state the association of "$" [hexadecimal 0x24]

Section [10.12 Embedded (Interleaved) Binary Data] specified a mechanism of transferring RTSP messages over a TCP connection with a application layer header consisting of the hexadecimal octet 0x24; followed by a single octet channel identifier and the RFC4571 length specifier of the frame.

Due to the fact 0x24 violates section 4's requirements based on the fact it cannot be masked with the octet (AND 0xc3) to ensure it is a valid character I am filing this errata.

The chosen octet may also be present, specifically in the types of RTSP messages which are interleaved during playback such as ANNOUNCE. E.g. 0x24 could be a part of the configuration specifying the bits per pixel or audio bit depth as part of the SDP inter alia.

In such cases the underlying parser would interpret this octet as the start of the defined application header and cause framing errors which could cause data loss as allow for buffer overflow attacks of carefully crafted binary data.

There are also definitions which need to be made in the stadard for what to do when less then the amount of bytes indicated by the application layer frame header are or are not present. (e.g. more or less bytes are required then are present during reception of the given the [$CXX] application header sequence).

It is based on these considerations among others that I recommend that "$" [hexadecimal octet 0x24] be added to the reserved list and if necessary an escaping mechanism be defined where it is replaced with an escaped sequence which is agreed upon after consensus.

Due to the fact that drafts also specify that RTSP can be extended with any type of message so long as the data is not "$" the first character it is ambiguous may also appear elsewhere in the status line.

There are also issues with the ambiguous definition of pdu fragmentation defined in the latest draft, e.g. the mechanism defined as possibly required when pdu's larger then 65535 bytes are used however it specified no way to convey how this occurs or why.

The same can also be said for "sink" and "source" however I will address those definitions et al when appropriate.

Thank you for your time!

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC2326 (no draft string recorded)
--------------------------------------
Title               : Real Time Streaming Protocol (RTSP)
Publication Date    : April 1998
Author(s)           : H. Schulzrinne, A. Rao, R. Lanphier
Category            : PROPOSED STANDARD
Source              : Multiparty Multimedia Session Control
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Dec 12 01:24:46 2014
Return-Path: <ari.keranen@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367BD1A19E5 for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 01:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.301
X-Spam-Level: 
X-Spam-Status: No, score=-3.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 YYodIuUqhzcj for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 01:24:42 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9C561A90D3 for <mmusic@ietf.org>; Fri, 12 Dec 2014 01:24:41 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-cc-548ab457cc8d
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id AB.82.24955.754BA845; Fri, 12 Dec 2014 10:24:40 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.29) with Microsoft SMTP Server id 14.3.195.1; Fri, 12 Dec 2014 10:24:39 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 53433110207; Fri, 12 Dec 2014 11:24:39 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id C26B75F924;	Fri, 12 Dec 2014 11:25:39 +0200 (EET)
Received: from ip-193-234-217-42.guest.ericsson.fi (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 483835F7AD; Fri, 12 Dec 2014 11:25:39 +0200 (EET)
Message-ID: <548AB456.1020206@ericsson.com>
Date: Fri, 12 Dec 2014 11:24:38 +0200
From: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Suhas Nandakumar <suhasietf@gmail.com>
References: <54885F3D.4040508@ericsson.com> <CAMRcRGQZ8aQep-8VehcYmfMPy_iEffzA0RYJA3SYGNMcYX+vwg@mail.gmail.com>
In-Reply-To: <CAMRcRGQZ8aQep-8VehcYmfMPy_iEffzA0RYJA3SYGNMcYX+vwg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+JvjW7Elq4Qg21ZFlOXP2axWHzgPqvF zrkdzA7MHlN+b2T12DnrLrvHkiU/mQKYo7hsUlJzMstSi/TtErgyzq7ex1yw2b/ids9K9gbG GZZdjJwcEgImEm8uNrJC2GISF+6tZ+ti5OIQEjjCKLHv7EwoZwOjREfXS2YIZw+jxOvWr+wg LUICaxklTm3khEhsY5T4cK6LGSTBK6AtMeXaLEYQm0VAVWLX5x1MIDabgK3E6lc3WUBsUYFk ia6XD5kg6gUlTs58AhYXEdCSWL14LlicWSBI4uKJB2BxYQEXiRnr/0EtLpB4OHE3mM0pEChx 8/wmVoh6C4mZ888zQtjyEs1bZzND/KYmcfXcJmaIXlWJq/9eMU5gFJ2FZPUsJO2zkLQvYGRe xShanFqclJtuZKyXWpSZXFycn6eXl1qyiREYJwe3/FbdwXj5jeMhRgEORiUe3oJJXSFCrIll xZW5hxilOViUxHkXnpsXLCSQnliSmp2aWpBaFF9UmpNafIiRiYNTqoGxQsVsk4Gihau5jtq5 rxH6Qm/7I3uMV66+xtB44WXzlZh/oqFXvRevqI356D79B+O8GV+NGDIOT3wdk96UdnFedphV kuXls2X3HL6qXLKIeWF8c/GZxxwZPDOrJE39dyQGPmo/4uatrTflcZnRzISgp5mT3Tfr2LOW 5cdEr7g0kyF9kurhheuUWIozEg21mIuKEwFsABa3dAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/94iUuGCa8CQ2OzkQommu7V6zAmI
Cc: "Suhas Nandakumar \(snandaku\)" <snandaku@cisco.com>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ietf-mmusic-sdp-mux-attributes-05 review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 09:24:45 -0000

Hi Suhas,

The updates you propose below look good to me and thanks for the 
clarifications too.


Cheers,
Ari

On 11/12/14 09:47, Suhas Nandakumar wrote:
> Hello Ari
>
>    Many thanks for the review. Please see inline
>
> Thanks
> Suhas
>
> On Wed, Dec 10, 2014 at 8:27 PM, Ari KerĂ¤nen <ari.keranen@ericsson.com
> <mailto:ari.keranen@ericsson.com>> wrote:
>
>     Hi Suhas,
>
>     Here are my review comments on the SDP mux draft. Technically I
>     think the doc is in pretty good shape, so these are mostly editorial
>     issues.
>
>
>     Cheers,
>     Ari
>
>
>     Abstract
>
>         In the RTCWEB WG, there is a need to use a
>         single 5-tuple for sending and receiving media associated with
>         multiple media descriptions ("m=" lines).
>
>     Bundling is not RTCWEB-only feature, so I would rather drop the
>     RTCWEB reference at least from the abstract, and write it in more
>     general way (e.g., "in order to save resources and decrease
>     connection setup times, these is a need..." like in section 3)
>
>
>         Such a requirement has
>         raised concerns over the semantic implications of the SDP attributes
>         associated with the RTP Media Streams multiplexed over a single
>         underlying transport layer flow.
>
>     I think we are beyond "raised concerns" and have actually found out
>     it was a real issue, so I would update the wording here.
>
>
> [Suhas] - I will try to make it more general in the next version.
>
>
>         The scope of this specification is to provide a framework for
>         analyzing the multiplexing characteristics of SDP attributes.
>
>     s/scope/purpose/
>
> [Suhas] - Accepted
>
>     1.  Introduction
>
>         Real-Time Communication in WEB-browsers (Rtcweb) framework requires
>         Real-time Transport Protocol (RTP) as the media transport protocol
>         and Session Description Protocol (SDP) [RFC4566] for describing and
>         negotiating multi-media communication sessions.
>
>     This (and the following paragraph) should also be more general. Here
>     perhaps you can use RTCWEB as an example of where such feature is
>     required, but adding an RTCWEB reference (e.g. the use case doc)
>     would be good here for context.
>
>     I think it would make sense also to reference the bundle draft
>     already here and writing a sentence or two about the relationship
>     with this draft.
>
>     also:
>       s/requires/uses/
>       s/multi-media/multimedia/
>
> [Suhas] - Accpted
>
>
>     3.  Motivation
>
>         This imposes further restrictions on applicability of
>         these SDP attributes as they are defined today.
>
>     Not sure where "these" here refers to. I guess that word can either
>     be dropped, or clarify which attributes you mean.
>
>
> [Suhas] - removed the word "these" for clarity.
>
>
>     4.  SDP Attribute Analysis Framework
>
>     Would it make sense to have "before" and "after" in all the SDP
>     examples (now there's only the "before" part)?
>
>
> [Suhas] - I am not sure giving before and after examples be less
> confusing. Since we are not defining new way of doing things to contrast
> the approaches.
>
>
>     4.2.  Category: NOT RECOMMENDED
>
>     Can/should we recommend here what to do in this case? Not multiplex?
>     Not add such attributes? Either way?
>
>
> [Suhas] - the definition for the category already encompasses this as
> highlighted below.
> "Attributes that are *recommended against multiplexing* since their
> usage under multiplexing might lead to incorrect behavior."
>
>
>     4.3.  Category: IDENTICAL
>
>         Attributes that MUST be identical across all the media descriptions
>         being multiplexed.
>
>     Maybe clarify that attributes and their *values* (if exist) must be
>     identical.
>
>
>              <allOneLine>
>              a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742__ac7a52c8f91bc2
>              df881ae642c371ba46df
>              </allOneLine>
>
>     The draft uses now 3 different ways of presenting too long SDP lines
>     (see e.g., 4.5, 4.7 and 14.3.1.1). I guess they are from the
>     defining RFCs, but I would rather see uniform style across this
>     document. Personally I prefer the style of section 4.5 (2 char indent).
>
> [Suhas] - Will move all the examples to reflect the format in Section 4.5
>
>     4.4.  Category: SUM
>
>     Should clarify where do you put the SUM'ed value.
>
>
> [Suhas] .. Since the calculated SUM value is expected to be consumed in
> the software processing SDP, the definition of this category already
> captures this fact.
>
>
>
>     4.5.  Category: TRANSPORT
>
>         Attributes that can be set normally for multiple items in a
>         multiplexed group but the software MUST pick just one of the
>         attribute of the given type for use.  The one chosen is the
>     attribute
>         associated with the "m=" line that represents the information being
>         used for the transport of the RTP.
>
>     How do you "pick" the one; by repeating the same value for each
>     bundled "m="-line?
>
>     Also, do we need to consider non-RTP cases too?
>
> [Suhas] - The expectation is to repeat as per the BUNDLE spec. Hence we
> have just added the way such a value is chosen but not the way the chose
> value is represented in the SDP as it is defined in the BUNDLE spec.
>
>
>     4.8.  Category: SPECIAL
>
>         Attributes where the text in the source draft must be consulted for
>         further handling when multiplexed.
>
>     s/source draft/specification defining the attribute/
>
>
> [Suhas] - Accepted
>
>
>
>     5.9.  RFC6773 - DCCP-UDP Encapsulation
>
>         Since RFC6773 is about tunneling DCCP in UDP, with the UDP port
>     being
>         the port of the DCCP en-/de-capsulation service.
>
>     Can't parse the sentence. Something missing here? Or extra "since"?
>
> [Suhas] -Removed since since it clarifies the text better.
>
>
>         This MAY or MAY NOT work depending on the
>         nature of DCCP encapsulations and ports choses thus rendering it to
>         be very application dependent.
>
>     Lower-case (non-RFC2119) "may" and "may not" would be appropriate
>     here. Also s/ports choses/port choices/?
>
>
> [Suhas] - Done
>
>
>
>     5.12.  RFC5245 - Interactive Connectivity Establishment (ICE)
>
>     Since the ICE candidate behavior is already specified in the bundle
>     draft at least reference there would be good? Also please make sure
>     that these stay in sync with what bundle has until it's an RFC.
>
> [Suhas] - BUNDLE spec provides O/A procedures for ICE but does not
> provide the category assignments for the ICE attributes.
>
>
>     5.21.  RFC6230 - Media Control Channel Framework
>
>                 | cfw-id  | Not Applicable  | M     | NORMAL       |
>
>     Should that be "Not Impacted" as in other NORMAL cases?
>
>
> [Suhas] - Accepted
>
>
>
>     5.39.  RFC6189 - ZRTP
>
>         | zrtp-hash  | Complicates if all the        | M     | NOT
>          |
>         |            | m=lines are not authenticated |       |
>     RECOMMENDED  |
>         |            | as given in the example below |       |
>          |
>
>     Where's the example? You mean the one in section 4.2?
>
> [Suhas] - The example SDP was removed from this section to not duplicate
> but I had forgotten the delete the reference to the example in here.
> Hence, will remove the example refernce
>
>
>     5.46.  RFC2326 - Real Time Streaming Protocol
>
>     Could mention here briefly why RTSP is not supported (similar to the
>     next section).
>
> [Suhas] - Done
>
>
>     5.50.  3GPP TS 183.063
>
>         | PSCid               | Not Impacted | Not-Applicable | NORMAL
>          |
>
>     The "Not-Applicable" level is not defined. Could add that to section
>     5 or explain here and in 5.58.
>
> [Suhas] - Will add appropriate SDP attribute levels to these sections
>
>
>     7.1.  RFC4585 - RTP/AVPF
>
>     Are the "Attr Name" here really attribute names or should one use
>     some other name in this case?
>
> [Suhas] - Will clean up the column name for consistency
>
>
>     7.3.  RFC6285 - Unicast-Based RAMS
>
>     This one was missing the "intro description". Could add something
>     brief for consistency with rest of the doc. Same for 7.6, 9.1, 9.2,
>     10.x (I'll leave it up to you where you consider it worthwhile adding).
>
> [Suhas] - Agreed, I will add the intro text for all these sections. It
> helps readability as well.
>
>     And is the "Attr Name" field here just "Name" intentionally? Same in
>     following two sections.
>
>
>     13.1.  RFC5109 - RTP Payload Format for Generic FEC
>
>         Draft draft-lennox-payload-ulp-ssrc-__mux proposes a simple fix
>     to make
>
>     This is a bit tricky. This should be a proper reference, but
>     referencing expired drafts is not a good practice either. I would
>     lean towards taking this sentence away since (if?) the fix is not
>     going forward at the IETF.
>
> [Suhas] - Removed this reference.
>
>
>     14.2.1.  Recommendation - Procedures for Potential Configuration Pairing
>
>         that are consistent across all the bundled media descriptions.
>
>     Could add "bundled media" to the terminology section.
>
> [Suhas] removed bundled with multiplexed to keep it uniform
>
>
>     15.  IANA Considerations
>
>     It would be great if someone double-checked that the "Mux Category"
>     entries here match to the text. Probably a simple script could do
>     that too.
>
> [Suhas]  - I can work on this to be sure
>
>     _________________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/mmusic
>     <https://www.ietf.org/mailman/listinfo/mmusic>
>
>


From nobody Fri Dec 12 01:32:06 2014
Return-Path: <ari.keranen@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F15241AC529 for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 01:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 jHq_1hNGLFr1 for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 01:32:03 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CB2B1A19E5 for <mmusic@ietf.org>; Fri, 12 Dec 2014 01:32:03 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-d1-548ab6110225
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id E3.78.04231.116BA845; Fri, 12 Dec 2014 10:32:01 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.92) with Microsoft SMTP Server id 14.3.195.1; Fri, 12 Dec 2014 10:32:01 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 3CC6E1102B1; Fri, 12 Dec 2014 11:32:01 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id AE2375F924;	Fri, 12 Dec 2014 11:33:01 +0200 (EET)
Received: from ip-193-234-217-42.guest.ericsson.fi (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 5659A5F7AD; Fri, 12 Dec 2014 11:33:01 +0200 (EET)
Message-ID: <548AB610.40006@ericsson.com>
Date: Fri, 12 Dec 2014 11:32:00 +0200
From: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUyM+Jvja7gtq4QgwMzdC3eXLSzmLr8MYsD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlXHl92HWgr3MFZ9W/WNrYLzI1MXIwSEhYCKx YxpXFyMnkCkmceHeerYuRi4OIYEjjBJ7Z/eyQjgbGCV23D3FCFIlJLCHUWLDXw+IxFpGie3n HrBAONuAqlY0MoNU8QpoSjw89R9sBYuAqsTE7fogYTYBW4nVr26ygNiiAskSXS8fMkGUC0qc nPkELC4iICOxd9NmZpBWZgFLiSvd1SBhYSDz6fyrYDcwC1hIzJx/HsqWl9j+dg4zxAdqElfP bWKGuFNV4uq/V4wTGIVnIdkwC0n7LCTtCxiZVzGKFqcWF+emGxnrpRZlJhcX5+fp5aWWbGIE BvfBLb91dzCufu14iFGAg1GJh7dgUleIEGtiWXFl7iFGaQ4WJXHeRefmBQsJpCeWpGanphak FsUXleakFh9iZOLglGpgtE+5EKu60EBDUfq+4v6X0wuXhsddFgt9KaD+0NtUXn1u1o5sR924 k3oFt7a6Xjl5d/vUI99EV1xP4PHvXHe1MmjNsnaRtAs7uKZGCVSb/91iEFTa9Ol8W2Te1qa7 Xx4YLpmQs5WNv7tvUr6M71MfHnWbx7ZRf7nuHXK49XaVlOfnF0L/3r1cpMRSnJFoqMVcVJwI AGuC3k1PAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7x9PZ53mChz9WFTGl_JwgHvUSCE
Cc: draft-ietf-mmusic-sdp-mux-attributes@tools.ietf.org
Subject: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-mux-attributes-06
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 09:32:05 -0000

Hi all,

We are now starting a 4 week Working Group Last Call for

             draft-ietf-mmusic-sdp-mux-attributes-06

as Proposed Standard. Please review and provide any comments you may 
have on the document by Friday, January 9, 2015.

Comments should be sent to the document authors and the MMUSIC WG list. 
If you review the document but do not have any comments, please send a 
note to that effect as well.


Thanks,
Ari


From nobody Fri Dec 12 10:46:17 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839161A00B7 for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 10:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 dVPpPDj-jTzJ for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 10:46:10 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705F91A6FFD for <mmusic@ietf.org>; Fri, 12 Dec 2014 10:46:09 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-9e-548b37ef1f7a
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A1.0B.04076.FE73B845; Fri, 12 Dec 2014 19:46:07 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.189]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0195.001; Fri, 12 Dec 2014 19:46:07 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQAMbXWAACPMjwAAS2d2cA==
Date: Fri, 12 Dec 2014 18:46:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D59298E@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM+Jvje578+4Qg0vPVCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj7MsjzAWTlCs+bNnG0sB4UrqLkZNDQsBE Yu3hZ8wQtpjEhXvr2boYuTiEBI4wSnROfcwO4SxhlJi7YCFrFyMHB5uAhUT3P22QBhGBOIlp J5+zgtjMAioSr05fBrOFBTQkrqxazgZRoykxfeFvJgjbSWJC72UWEJtFQFXi6b9uJpCRvAK+ EvNnOICEhQQ2M0r8aywGsTkF/CT6NmxnBLEZgW77fmoNE8QqcYlbT+YzQdwsILFkz3mo+0Ul Xj7+xwphK0ksuv0Zql5HYsHuT2wQtrbEsoWvwep5BQQlTs58wjKBUWwWkrGzkLTMQtIyC0nL AkaWVYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiB0XNwy2+rHYwHnzseYhTgYFTi4S2c1BUi xJpYVlyZe4hRmoNFSZx34bl5wUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYNdawVfJ33U5o PqN1Skay/+/SeVEvF4fWyM+83q/zztj39dWbApfEU5ZmaUR9/x1y69ScY+XR3+92XdjZqhat f+Lydqu5QftsnntvOzXJg3UycwxLkZZOseC57gbWe78/pYpfvWV3wOxZQkWYwIvjEWtyuNqX nVnzcOKO6EAHVcYfzxY1W87MVWIpzkg01GIuKk4EAF2OoEl/AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2etMBq-pzN2ntM8okxa2nYMxdIk
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 18:46:14 -0000

Hi,

------------

>>>> Section 8.5.2:
>>>>
>>>> I want to check what is intended here.
>>>>
>>>> Suppose I have previously established a bundle group. It has several m=
-lines. In the prior=20
>>>> O/A all of those m-lines had the same address:port. Now I want to chan=
ge the bundle address.
>>>>
>>>> As I read the text in this section, I must change the address in *1* o=
f the m-lines, and suggest it as=20
>>>> the offerer bundle address, but leave the old address in the other m-l=
ines.
>>>>
>>>> That isn't what I had been thinking happened. I had been assuming that=
 the address would be changed in all the m-lines.
>>>>
>>>> The consequence of this is that if the answerer doesn't want the=20
>>>> change, it will have to reject the one changed m-line, and select the =
old address as the bundle address. If I was making the change because I am =
no longer capable of >>>> using the old address then this won't work for me=
.
>>>> It would be better for me to have the entire bundle rejected.
>>>
>>> The thinking has been that only an accepted BUNDLE address can be assig=
ned to multiple m- lines. Your suggestion would change that, because the ne=
w address (when >>> suggested in the offer) has not been accepted as a BUND=
LE address yet.
>>
>> First I just wanted to verify that is what is intended.
>> That is now settled.
>>
>> Next is whether that is the best way to handle this.
>>
>>> Also, even if the offerer assigns the new address to all m- lines, and =
the answerer rejects the offer, the offerer still has to fall back to the p=
revious offerer BUNDLE address >>>- no matter whether it can use it or not.
>>>
>>> The answerer could reject all the m-lines yet accept the offer.
>>>
>> But yes, if the offer itself is rejected then there is need to fall back=
.
>>
>>> AND, assuming we go along with your suggestion, I guess that also=20
>>> means that if a new m- line is added (section 8.5.3), and if the=20
>>> offerer wants the address of that m- line to become the new offerer BUN=
DLE address, the offerer must also assign the address of the new m- line al=
so to the other m- >>> lines in the BUNDLE group.
>>>
>> True. That is an argument in favor of keeping things as they are.
>>
>> I guess you have convinced me.
>
> I wasn't trying to convince you - I just wanted to make sure we take all =
the impacts into consideration. I=20
> have learned that, what first may look like a small and isolated > change=
, may have big impacts throughout the document :)
>
> The advantage of assigning the suggested new offerer BUNDLE address to al=
l "m=3D" lines is that you don't have=20
> to send a BAS offer afterwards - which is a big advantage.
>
> Of course, in the case of adding a new m- line to a BUNDLE group, if the =
answerer does not accept it in the=20
> BUNDLE group, the answerer will have to reject it. In that case, the offe=
rer could send a new offer, and keep=20
> the new "m=3D" line outside the BUNDLE group. But, IF the new "m=3D" line=
 IS accepted in the BUNDLE group, the=20
> BAS offer is not needed.
>
> So, personally I have no problem with your suggestion. Mandating a shared=
 address (whether it's a previously=20
> selected offerer BUNDLE address, or a new suggested offerer BUNDLE addres=
s) makes things more clear. I just=20
> want to make sure others are ok too, because it would be a technical chan=
ge.

I wonder whether others have an opinion on this issue.

The idea would be to, when a new offerer BUNDLE address is suggested, assig=
n that suggested address to ALL bundle m- lines within the offer (instead o=
f only assigning it to one m- line within the offer, and keep the previousl=
y selected offerer BUNDLE address for the other m- lines).

The advantage would be that no BAS offer is needed.

The only disadvantage is that, if the answerer does not accept (which I thi=
nk will be an extremely rare case) the new offerer BUNDLE address, it has t=
o reject the offer in order to fallback to the previous offerer BUNDLE addr=
ess.

=20
Also, when a new m- line is added to a BUNDLE group, the idea would be to a=
lways assign the current offerer BUNDLE address to that m- line. If the ans=
werer does not accept the m- line in the BUNDLE group, it has to reject the=
 m- line. But, there would be no need for a BAS offer.

Personally, the more I think about it, the more I like the suggestion :)

Regards,

Christer


From nobody Fri Dec 12 17:03:48 2014
Return-Path: <ibc@aliax.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEABC1A1A5C for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 17:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level: 
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 AzrRrdY6-Z7f for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 17:03:46 -0800 (PST)
Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com [209.85.192.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 240251A8732 for <mmusic@ietf.org>; Fri, 12 Dec 2014 17:03:46 -0800 (PST)
Received: by mail-qg0-f50.google.com with SMTP id i50so6182728qgf.23 for <mmusic@ietf.org>; Fri, 12 Dec 2014 17:03:45 -0800 (PST)
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=Kt12VcUVbancvMUQ2nBBqojMULE2qLXAZJnSEDODObk=; b=fmX8YbthMCm7e9+0M5LeWaRJ/1HCsytt6LC5ubPPn9NASuko/reGCM9llBGnupEdux Z+YOy/sPGF/FBeXyivBbOJSc6AWLqA95ws6TZenZujnUSxiVwCOdR2XA0YdHPsb+sK67 iHjq79HlGq4IIrmTX1Piw6v0m5t6W/jReQN+FI6cJcg1ztTKVi8IhRJtA6+DWSidDyV6 VXv0shxnchonKRz+Jc+c34JuGnCZ+DSo5yvawl2n1riM/MLLh4/ukrobbw+m8ow+3Pps jsCk8xqVwH4ueLVmC0uRPKdPWVmfrnzi2Ba8u7vSVlNXs+rm9wOKUB7Em7VOCyNxyVoa WTEQ==
X-Gm-Message-State: ALoCoQl3k1gx4HoXOuTEVTJ6ddsXUw8hM8ZPldGLX+xmQ+mAM+8z/vtrW+jrUAJXOznDmlcpHqmB
X-Received: by 10.224.29.134 with SMTP id q6mr35130997qac.73.1418432625331; Fri, 12 Dec 2014 17:03:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.26.135 with HTTP; Fri, 12 Dec 2014 17:03:25 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sat, 13 Dec 2014 02:03:25 +0100
Message-ID: <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/eZRg8-VDGAl35LlW_DW4E3c4ZOk
Cc: IETF MMUSIC WG <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 01:03:47 -0000

2014-12-11 8:01 GMT+01:00 Christer Holmberg <christer.holmberg@ericsson.com>:
> Of course, in the case of adding a new m- line to a BUNDLE group, if the answerer does not accept it in the BUNDLE group, the answerer will have to reject it.

> In that case, the offerer could send a new offer,

But you know it wont XD

Why to try again by changing "something"?


From nobody Fri Dec 12 22:57:02 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8023C1AC3E3 for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 22:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 tXOpUyRtHHeB for <mmusic@ietfa.amsl.com>; Fri, 12 Dec 2014 22:56:59 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486261AC3DF for <mmusic@ietf.org>; Fri, 12 Dec 2014 22:56:58 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-4f-548be3388d0c
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 7E.F0.24955.833EB845; Sat, 13 Dec 2014 07:56:56 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.68]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0195.001; Sat, 13 Dec 2014 07:56:56 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQAMbXWAACPMjwAAVs4OgAAOcQBq
Date: Sat, 13 Dec 2014 06:56:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se>, <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com>
In-Reply-To: <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D5A0AE4ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42KZGfG3RtficXeIwZU2U4vp+2wspi5/zGKx YsMBVgdmj3MN79k9/r7/wOSxZMlPpgDmKC6blNSczLLUIn27BK6MiZfWMxXsU6849OsBUwPj CrUuRk4OCQETiYlHdjFD2GISF+6tZ+ti5OIQEjjCKDHtyBxGCGcxo8TLa8tYuxg5ONgELCS6 /2mDNIgI2Ej8u3CBHcRmFvCSWHRoBguILSxgKPHl0D5GiBojiedTVrJD2G4SLQ8+MYHYLAKq Ek2nDrCB2LwCvhITvv2FWvyDUeLaivNgCU6BQIkvV1aBXccIdN33U2uYIJaJSzR9WckKcbWA xJI956E+EJV4+fgf2J3MAvkSP09yQMwXlDg58wnLBEaRWUi6ZyFUzUJSBRHWlFi/Sx+iWlFi SvdDdghbQ6J1zlx2ZPEFjOyrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQKj7OCW36o7GC+/ cTzEKMDBqMTDu2F1d4gQa2JZcWXuIUZpDhYlcd6F5+YFCwmkJ5akZqemFqQWxReV5qQWH2Jk 4uCUamDs1qiTEr99j/NihPvTi3fXM5ocXRFf7nPp+PVpq/78y1Dd9uXy0+m8rvUnVCfezpCK 2bvxvPmp4GllqzY7LTp8qmrx/FyFf7cs//WtK3DdOt+zekb1bMflaWn8Ke9Tn2a8eev2SPAG 59m930J+uDMet51qYNkquj0htKH/ar7s7q+/Cz7GqWzwV2Ipzkg01GIuKk4EADpiVXqTAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/RCcKDmeHWwoaN7jYG98DPYgQVrk
Cc: IETF MMUSIC WG <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 06:57:01 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D5A0AE4ESESSMB209erics_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCllvdSBjYW4gdHJ5IGFnYWluIGJ5IG5vdCBhZGRpbmcgdGhlIG0tIGxpbmUgdG8gdGhl
IEJVTkRMRSBncm91cC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KU2VudCBmcm9tIG15IFdp
bmRvd3MgUGhvbmUNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBJw7Fh
a2kgQmF6IENhc3RpbGxvPG1haWx0bzppYmNAYWxpYXgubmV0Pg0KU2VudDog4oCOMTMv4oCOMTIv
4oCOMjAxNCAwMzowMw0KVG86IENocmlzdGVyIEhvbG1iZXJnPG1haWx0bzpjaHJpc3Rlci5ob2xt
YmVyZ0Blcmljc3Nvbi5jb20+DQpDYzogSUVURiBNTVVTSUMgV0c8bWFpbHRvOm1tdXNpY0BpZXRm
Lm9yZz47IFBhdWwgS3l6aXZhdDxtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1Pg0KU3ViamVj
dDogUmU6IFtNTVVTSUNdIGJ1bmRsZS0xMyAtIFBhdWwncyBjb21tZW50cw0KDQoyMDE0LTEyLTEx
IDg6MDEgR01UKzAxOjAwIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmlj
c3Nvbi5jb20+Og0KPiBPZiBjb3Vyc2UsIGluIHRoZSBjYXNlIG9mIGFkZGluZyBhIG5ldyBtLSBs
aW5lIHRvIGEgQlVORExFIGdyb3VwLCBpZiB0aGUgYW5zd2VyZXIgZG9lcyBub3QgYWNjZXB0IGl0
IGluIHRoZSBCVU5ETEUgZ3JvdXAsIHRoZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IGl0
Lg0KDQo+IEluIHRoYXQgY2FzZSwgdGhlIG9mZmVyZXIgY291bGQgc2VuZCBhIG5ldyBvZmZlciwN
Cg0KQnV0IHlvdSBrbm93IGl0IHdvbnQgWEQNCg0KV2h5IHRvIHRyeSBhZ2FpbiBieSBjaGFuZ2lu
ZyAic29tZXRoaW5nIj8NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg==

--_000_7594FB04B1934943A5C02806D1A2204B1D5A0AE4ESESSMB209erics_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVu
dD0iTWljcm9zb2Z0IEV4Y2hhbmdlIFNlcnZlciI+DQo8IS0tIGNvbnZlcnRlZCBmcm9tIHRleHQg
LS0+PHN0eWxlPjwhLS0gLkVtYWlsUXVvdGUgeyBtYXJnaW4tbGVmdDogMXB0OyBwYWRkaW5nLWxl
ZnQ6IDRwdDsgYm9yZGVyLWxlZnQ6ICM4MDAwMDAgMnB4IHNvbGlkOyB9IC0tPjwvc3R5bGU+DQo8
L2hlYWQ+DQo8Ym9keT4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2Fs
aWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdCI+SGksPGJyPg0KPGJyPg0KWW91IGNhbiB0
cnkgYWdhaW4gYnkgbm90IGFkZGluZyB0aGUgbS0gbGluZSB0byB0aGUgQlVORExFIGdyb3VwLjxi
cj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2hyaXN0ZXI8YnI+DQo8YnI+DQpTZW50IGZy
b20gbXkgV2luZG93cyBQaG9uZTwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxocj4N
CjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTox
MXB0OyBmb250LXdlaWdodDpib2xkIj5Gcm9tOg0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij48YSBocmVmPSJtYWlsdG86
aWJjQGFsaWF4Lm5ldCI+ScOxYWtpIEJheiBDYXN0aWxsbzwvYT48L3NwYW4+PGJyPg0KPHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZv
bnQtd2VpZ2h0OmJvbGQiPlNlbnQ6DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNh
bGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQiPuKAjjEzL+KAjjEyL+KAjjIwMTQgMDM6
MDM8L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJp
ZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPlRvOg0KPC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij48YSBo
cmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIj5DaHJpc3RlciBIb2xt
YmVyZzwvYT48L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fu
cy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPkNjOg0KPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0
Ij48YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIj5JRVRGIE1NVVNJQyBXRzwvYT47DQo8
YSBocmVmPSJtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1Ij5QYXVsIEt5eml2YXQ8L2E+PC9z
cGFuPjxicj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZv
bnQtc2l6ZToxMXB0OyBmb250LXdlaWdodDpib2xkIj5TdWJqZWN0Og0KPC9zcGFuPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij5SZTog
W01NVVNJQ10gYnVuZGxlLTEzIC0gUGF1bCdzIGNvbW1lbnRzPC9zcGFuPjxicj4NCjxicj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8Zm9udCBzaXplPSIyIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwcHQ7
Ij4NCjxkaXYgY2xhc3M9IlBsYWluVGV4dCI+MjAxNC0xMi0xMSA4OjAxIEdNVCYjNDM7MDE6MDAg
Q2hyaXN0ZXIgSG9sbWJlcmcgJmx0O2NocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDs6
PGJyPg0KJmd0OyBPZiBjb3Vyc2UsIGluIHRoZSBjYXNlIG9mIGFkZGluZyBhIG5ldyBtLSBsaW5l
IHRvIGEgQlVORExFIGdyb3VwLCBpZiB0aGUgYW5zd2VyZXIgZG9lcyBub3QgYWNjZXB0IGl0IGlu
IHRoZSBCVU5ETEUgZ3JvdXAsIHRoZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IGl0Ljxi
cj4NCjxicj4NCiZndDsgSW4gdGhhdCBjYXNlLCB0aGUgb2ZmZXJlciBjb3VsZCBzZW5kIGEgbmV3
IG9mZmVyLDxicj4NCjxicj4NCkJ1dCB5b3Uga25vdyBpdCB3b250IFhEPGJyPg0KPGJyPg0KV2h5
IHRvIHRyeSBhZ2FpbiBieSBjaGFuZ2luZyAmcXVvdDtzb21ldGhpbmcmcXVvdDs/PGJyPg0KPGJy
Pg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpt
bXVzaWMgbWFpbGluZyBsaXN0PGJyPg0KbW11c2ljQGlldGYub3JnPGJyPg0KPGEgaHJlZj0iaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMiPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxicj4NCjwvZGl2Pg0KPC9zcGFuPjwv
Zm9udD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B1D5A0AE4ESESSMB209erics_--


From nobody Sat Dec 13 01:40:03 2014
Return-Path: <ibc@aliax.net>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176671A8847 for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 01:40:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 vfdm1PBcMJAo for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 01:39:59 -0800 (PST)
Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6B11A87EE for <mmusic@ietf.org>; Sat, 13 Dec 2014 01:39:59 -0800 (PST)
Received: by mail-qc0-f173.google.com with SMTP id i17so6661613qcy.32 for <mmusic@ietf.org>; Sat, 13 Dec 2014 01:39:58 -0800 (PST)
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:date :message-id:subject:from:to:cc:content-type; bh=AJe9BKEr3GD0yx05V6+UDKafOefhQqK2RO8ZgZj26hc=; b=jalmOhoZeIqwjSjlhX88bIQfAY0y+CRnASk1AZgrqZlyxCdGbuWinTAJkiSiwu8MKU +CLdYRkgOVJuI1qHahsX/lQTEBkpmDFTXZ7myv6zShQqD7ghBerWFX866OLVb0ec5SsO VVLz8kLtzv5rAoWyap2cDu5SzIl1t8LLUHZsDIFSnnucB0wK80lgvLZYem0Q3sV+94wZ gkgjfnq1EsOyisV2RudODsGIkYS6RU+yY9a+qZLhgfD2907oJTQcVcl89iAW7DkW3ck+ Qn9BaH7kPUmlh+coZkcn+zvNfWd+dF9M641bxHDRzaLjH6lMZXGWNs8bdO3pOeijVL6G GAcA==
X-Gm-Message-State: ALoCoQnFzjOFJiyBh08vr11aYhBYI72vGwTMfHvA8Z61Gh9e0FqTDR8wRH3L661FL/Q/y6GXzDfy
MIME-Version: 1.0
X-Received: by 10.229.196.70 with SMTP id ef6mr38791700qcb.31.1418463598557; Sat, 13 Dec 2014 01:39:58 -0800 (PST)
Received: by 10.96.26.135 with HTTP; Sat, 13 Dec 2014 01:39:58 -0800 (PST)
Received: by 10.96.26.135 with HTTP; Sat, 13 Dec 2014 01:39:58 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se> <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se>
Date: Sat, 13 Dec 2014 10:39:58 +0100
Message-ID: <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11c35e02eb6069050a15caf1
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/PhrFvY6OjFqDilwDb-OepuRj3k8
Cc: mmusic@ietf.org, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 09:40:01 -0000

--001a11c35e02eb6069050a15caf1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You don't know why the peer rejected it, so trying again (by randomly
changing something) does not provide a determinist behavior/result.
On 13 Dec 2014 07:56, "Christer Holmberg" <christer.holmberg@ericsson.com>
wrote:

>   Hi,
>
> You can try again by not adding the m- line to the BUNDLE group.
>
> Regards,
>
> Christer
>
> Sent from my Windows Phone
>  ------------------------------
> From: I=C3=B1aki Baz Castillo <ibc@aliax.net>
> Sent: =E2=80=8E13/=E2=80=8E12/=E2=80=8E2014 03:03
> To: Christer Holmberg <christer.holmberg@ericsson.com>
> Cc: IETF MMUSIC WG <mmusic@ietf.org>; Paul Kyzivat <pkyzivat@alum.mit.edu=
>
> Subject: Re: [MMUSIC] bundle-13 - Paul's comments
>
>   2014-12-11 8:01 GMT+01:00 Christer Holmberg <
> christer.holmberg@ericsson.com>:
> > Of course, in the case of adding a new m- line to a BUNDLE group, if th=
e
> answerer does not accept it in the BUNDLE group, the answerer will have t=
o
> reject it.
>
> > In that case, the offerer could send a new offer,
>
> But you know it wont XD
>
> Why to try again by changing "something"?
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a11c35e02eb6069050a15caf1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">You don&#39;t know why the peer rejected it, so trying again=
 (by randomly changing something) does not provide a determinist behavior/r=
esult. </p>
<div class=3D"gmail_quote">On 13 Dec 2014 07:56, &quot;Christer Holmberg&qu=
ot; &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg=
@ericsson.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">





<div>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">Hi,<br>
<br>
You can try again by not adding the m- line to the BUNDLE group.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">From:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:ibc@aliax.net" target=3D"_blank">I=C3=B1aki Baz Castillo</a></s=
pan><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Sent:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">=E2=80=
=8E13/=E2=80=8E12/=E2=80=8E2014 03:03</span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">To:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">Christer Holm=
berg</a></span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Cc:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt"><a hre=
f=3D"mailto:mmusic@ietf.org" target=3D"_blank">IETF MMUSIC WG</a>;
<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">Paul Kyzivat</a>=
</span><br>
<span style=3D"font-family:Calibri,sans-serif;font-size:11pt;font-weight:bo=
ld">Subject:
</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt">Re: [M=
MUSIC] bundle-13 - Paul&#39;s comments</span><br>
<br>
</div>
</div>
<font><span style=3D"font-size:10pt">
<div>2014-12-11 8:01 GMT+01:00 Christer Holmberg &lt;<a href=3D"mailto:chri=
ster.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.co=
m</a>&gt;:<br>
&gt; Of course, in the case of adding a new m- line to a BUNDLE group, if t=
he answerer does not accept it in the BUNDLE group, the answerer will have =
to reject it.<br>
<br>
&gt; In that case, the offerer could send a new offer,<br>
<br>
But you know it wont XD<br>
<br>
Why to try again by changing &quot;something&quot;?<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div>
</span></font>
</div>

</blockquote></div>

--001a11c35e02eb6069050a15caf1--


From nobody Sat Dec 13 03:05:55 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E000F1A002A for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 03:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 NYuvwQPTwwDE for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 03:05:46 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23E4D1A0026 for <mmusic@ietf.org>; Sat, 13 Dec 2014 03:05:44 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-5f-548c1d86af40
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 54.85.04231.68D1C845; Sat, 13 Dec 2014 12:05:43 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.68]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0195.001; Sat, 13 Dec 2014 12:05:42 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQAMbXWAACPMjwAAVs4OgAAOcQBqAAOZUQAABFcCkA==
Date: Sat, 13 Dec 2014 11:05:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5AB221@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se> <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se> <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com>
In-Reply-To: <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D5AB221ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42KZGfG3RrddtifE4MZ5Fovp+2wspi5/zGKx YsMBVgdmj3MN79k9/r7/wOSxZMlPpgDmKC6blNSczLLUIn27BK6MLesTCuZVVbz7eJatgfFH WRcjJ4eEgInEtx1X2SBsMYkL99YD2VwcQgJHGCVeX+lkhHAWM0r0nfjE3sXIwcEmYCHR/U8b pEFEwEbi34UL7CA2s4CvxMsFX5hBbGEBQ4kvh/YxQtQYSTyfshKsVUQgTOLpM3cQk0VAVWLt WrC1vECd/d8+g9lCAq3MEq/vO4HYnAKBEv1vNrKA2IxAp30/tYYJYpO4xK0n85kgThaQWLLn PDOELSrx8vE/VghbSWLR7c9Q9fkSbydugNolKHFy5hOWCYyis5CMmoWkbBaSsllAlzILaEqs 36UPUaIoMaX7ITuErSHROmcuO7L4Akb2VYyixanFxbnpRsZ6qUWZycXF+Xl6eaklmxiBkXdw y2/dHYyrXzseYhTgYFTi4d2wujtEiDWxrLgy9xCjNAeLkjjvonPzgoUE0hNLUrNTUwtSi+KL SnNSiw8xMnFwSjUwpu6wiHqiG+670nnBla3mLrP1xM0Fkg+9vv6T83+Zj+etN8uTU2a96vba vjCv9lLIkSuRnQf2enRLL+6ZPeX2csGor018fywOvin8WnM1/ELRj6Y9M6Ks3zzQb9w0V+FR ycQYxW6xgIqPYTkys0KWy0S+3XYlpTh0XsZtuRWtM/fw6tX4uh3rVWIpzkg01GIuKk4EAHAS 8uqdAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/MxX1d4Gtrcgh5I9JOm35c4tHsaI
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 11:05:52 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D5AB221ESESSMB209erics_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCj5Zb3UgZG9uJ3Qga25vdyB3aHkgdGhlIHBlZXIgcmVqZWN0ZWQgaXQsIHNvIHRyeWlu
ZyBhZ2FpbiAoYnkgcmFuZG9tbHkgPmNoYW5naW5nIHNvbWV0aGluZykgZG9lcyBub3QgcHJvdmlk
ZSBhIGRldGVybWluaXN0IGJlaGF2aW9yL3Jlc3VsdC4NCg0KV2VsbCwgdGhhdCBpcyB1bmZvcnR1
bmF0ZWx5IGEgZ2VuZXJhbCBwcm9ibGVtIGluIFNEUCBPL0EuIFlvdSBkb27igJl0IGFsd2F5cyBr
bm93IGV4YWN0bHkgd2h5IHNvbWV0aGluZyBpcyByZWplY3RlZC4NCg0KQWxzbyBrZWVwIGluIG1p
bmQgdGhhdCB0aGUgY3VycmVudCBkcmFmdCwgd2hlbiBhbiBtLSBsaW5lIGlzIGFkZGVkIHRvIGFu
IEJVTkRMRSBncm91cCwgYWxyZWFkeSBhbGxvd3MgYXNzaWduaW5nIHRoZSBCVU5ETEUgYWRkcmVz
cyB0byB0aGF0IG0tIGxpbmUuIFNvLCB0aGF0IGlzIG5vdGhpbmcgbmV3LiBXaGF0IGlzIG5ldyBp
cyB0aGF0IHRoZSBvZmZlcmVyIHdvdWxkIGFsd2F5cyBhZGQgdGhlIEJVTkRMRSBhZGRyZXNzIHRv
IHRoZSBhZGRlZCBtLSBsaW5lLCB3aGljaCBhbHNvIGhlbHBzIHNldHRpbmcgdGhlIGFzc29jaWF0
ZWQgU0RQIGF0dHJpYnV0ZSB2YWx1ZXMgZXRjICh0aGUgdmFsdWVzIG1heSBiZSBkaWZmZXJlbnQg
ZGVwZW5kaW5nIG9uIHdoZXRoZXIgYW4gbS0gbGluZSBpcyB3aXRoaW4gYSBCVU5ETEUgZ3JvdXAg
b3Igbm90LCBhcyBkZXNjcmliZWQgaW4gdGhlIHNkcC1tdXggZHJhZnQpLg0KDQpUaGUgc2Vjb25k
IG5ldyB0aGluZyAod2hpY2ggdHJpZ2dlcmVkIHRoaXMgZGlzY3Vzc2lvbikgaXMgdGhhdCwgd2hl
biBhIG5ldyBCVU5ETEUgYWRkcmVzcyBpcyBzdWdnZXN0ZWQsIHRoYXQgQlVORExFIGFkZHJlc3Mg
c2hvdWxkIGJlIGFzc2lnbmVkIHRvIGFsbCBtLSBsaW5lcyB3aXRoaW4gdGhlIEJVTkRMRSBncm91
cC4gSWYgdGhlIGFuc3dlcmVyIGFjY2VwdHMgaXQsIHRoZXJlIGlzIG5vIG5lZWQgZm9yIGEgQkFT
IG9mZmVyLiBJZiB0aGUgYW5zd2VyZXIgcmVqZWN0cyBpdCwgdGhlcmUgd2lsbCBiZSBhIGZhbGxi
YWNrIHRvIHRoZSBjdXJyZW50IEJVTkRMRSBhZGRyZXNzICh1c2luZyBub3JtYWwgMzI2NCBydWxl
cykuIEkgYmVsaWV2ZSBhbiBhZGRyZXNzIGNoYW5nZSB3aWxsIGJlIGFjY2VwdGVkIGluIG1vc3Qg
Y2FzZXMsIGFuZCBpZiBpdOKAmXMgbm90IHRoZW4gdGhlcmUgaXMgcHJvYmFibHkgZ29pbmcgdG8g
YmUgcHJvYmxlbXMgYW55d2F54oCmDQoNClNvLCByZWdhcmRpbmcgdGhlIGZpcnN0IGNoYW5nZSAo
YWx3YXlzIGFzc2lnbiB0aGUgYnVuZGxlIGFkZHJlc3MgdG8gYSBuZXcgbS0gbGluZSksIEkgc3Vw
cG9ydCB0aGF0IG9uZS4gQnV0LCBJIGRvIHJlYWxpemUgcGVvcGxlIG1heSBoYXZlIG90aGVyIG9w
aW5pb25zLCBzbyB0aGF04oCZcyB3aHkgSSBsaWtlIHRvIGhlYXIgdGhlbSA6KQ0KDQpSZWdhcmRp
bmcgdGhlIHNlY29uZCBjaGFuZ2UgKGFzc2lnbiB0aGUgbmV3IGFkZHJlc3MgdG8gYWxsIG0tIGxp
bmVzKSwgSSBwZXJzb25hbGx5IHN1cHBvcnQgYWxzbyB0aGF0IG9uZSwgYW5kIEkgY2Fu4oCZdCBz
ZWUgYSByZWFzb24gbm90IHRvIGRvIGl0LiBCdXQsIGFnYWluLCBmZWVsIGZyZWUgdG8gcHJvdmUg
bWUgd3JvbmcgOikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQoNCg0KDQoNCg0KDQoNCg0K
T24gMTMgRGVjIDIwMTQgMDc6NTYsICJDaHJpc3RlciBIb2xtYmVyZyIgPGNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4g
d3JvdGU6DQpIaSwNCg0KWW91IGNhbiB0cnkgYWdhaW4gYnkgbm90IGFkZGluZyB0aGUgbS0gbGlu
ZSB0byB0aGUgQlVORExFIGdyb3VwLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpTZW50IGZy
b20gbXkgV2luZG93cyBQaG9uZQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZy
b206IEnDsWFraSBCYXogQ2FzdGlsbG88bWFpbHRvOmliY0BhbGlheC5uZXQ+DQpTZW50OiDigI4x
My/igI4xMi/igI4yMDE0IDAzOjAzDQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmc8bWFpbHRvOmNocmlz
dGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4NCkNjOiBJRVRGIE1NVVNJQyBXRzxtYWlsdG86bW11
c2ljQGlldGYub3JnPjsgUGF1bCBLeXppdmF0PG1haWx0bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHU+
DQpTdWJqZWN0OiBSZTogW01NVVNJQ10gYnVuZGxlLTEzIC0gUGF1bCdzIGNvbW1lbnRzDQoyMDE0
LTEyLTExIDg6MDEgR01UKzAxOjAwIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVy
Z0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+Og0K
PiBPZiBjb3Vyc2UsIGluIHRoZSBjYXNlIG9mIGFkZGluZyBhIG5ldyBtLSBsaW5lIHRvIGEgQlVO
RExFIGdyb3VwLCBpZiB0aGUgYW5zd2VyZXIgZG9lcyBub3QgYWNjZXB0IGl0IGluIHRoZSBCVU5E
TEUgZ3JvdXAsIHRoZSBhbnN3ZXJlciB3aWxsIGhhdmUgdG8gcmVqZWN0IGl0Lg0KDQo+IEluIHRo
YXQgY2FzZSwgdGhlIG9mZmVyZXIgY291bGQgc2VuZCBhIG5ldyBvZmZlciwNCg0KQnV0IHlvdSBr
bm93IGl0IHdvbnQgWEQNCg0KV2h5IHRvIHRyeSBhZ2FpbiBieSBjaGFuZ2luZyAic29tZXRoaW5n
Ij8NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1t
dXNpYyBtYWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3Jn
Pg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg==

--_000_7594FB04B1934943A5C02806D1A2204B1D5AB221ESESSMB209erics_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1h
bCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5l
dyBSb21hbiIsc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N
CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFy
Z2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVm
dDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
IixzZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1y
ZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdE
O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVT
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUi
IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHlsZT0iY29s
b3I6IzFGNDk3RCI+Jmd0Ozwvc3Bhbj5Zb3UgZG9uJ3Qga25vdyB3aHkgdGhlIHBlZXIgcmVqZWN0
ZWQgaXQsIHNvIHRyeWluZyBhZ2FpbiAoYnkgcmFuZG9tbHkNCjxzcGFuIHN0eWxlPSJjb2xvcjoj
MUY0OTdEIj4mZ3Q7PC9zcGFuPmNoYW5naW5nIHNvbWV0aGluZykgZG9lcyBub3QgcHJvdmlkZSBh
IGRldGVybWluaXN0IGJlaGF2aW9yL3Jlc3VsdC48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PldlbGwsIHRoYXQgaXMgdW5mb3J0dW5hdGVseSBhIGdlbmVyYWwgcHJvYmxlbSBpbiBTRFAgTy9B
LiBZb3UgZG9u4oCZdCBhbHdheXMga25vdyBleGFjdGx5IHdoeSBzb21ldGhpbmcgaXMgcmVqZWN0
ZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5
N0QiPkFsc28ga2VlcCBpbiBtaW5kIHRoYXQgdGhlIGN1cnJlbnQgZHJhZnQsIHdoZW4gYW4gbS0g
bGluZSBpcyBhZGRlZCB0byBhbiBCVU5ETEUgZ3JvdXAsIGFscmVhZHkgYWxsb3dzIGFzc2lnbmlu
ZyB0aGUgQlVORExFIGFkZHJlc3MgdG8gdGhhdCBtLSBsaW5lLiBTbywgdGhhdCBpcyBub3RoaW5n
IG5ldy4gV2hhdA0KIGlzIG5ldyBpcyB0aGF0IHRoZSBvZmZlcmVyIHdvdWxkIGFsd2F5cyBhZGQg
dGhlIEJVTkRMRSBhZGRyZXNzIHRvIHRoZSBhZGRlZCBtLSBsaW5lLCB3aGljaCBhbHNvIGhlbHBz
IHNldHRpbmcgdGhlIGFzc29jaWF0ZWQgU0RQIGF0dHJpYnV0ZSB2YWx1ZXMgZXRjICh0aGUgdmFs
dWVzIG1heSBiZSBkaWZmZXJlbnQgZGVwZW5kaW5nIG9uIHdoZXRoZXIgYW4gbS0gbGluZSBpcyB3
aXRoaW4gYSBCVU5ETEUgZ3JvdXAgb3Igbm90LCBhcyBkZXNjcmliZWQNCiBpbiB0aGUgc2RwLW11
eCBkcmFmdCkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMxRjQ5N0QiPlRoZSBzZWNvbmQgbmV3IHRoaW5nICh3aGljaCB0cmlnZ2VyZWQgdGhpcyBkaXNj
dXNzaW9uKSBpcyB0aGF0LCB3aGVuIGEgbmV3IEJVTkRMRSBhZGRyZXNzIGlzIHN1Z2dlc3RlZCwg
dGhhdCBCVU5ETEUgYWRkcmVzcyBzaG91bGQgYmUgYXNzaWduZWQgdG8gYWxsIG0tIGxpbmVzIHdp
dGhpbiB0aGUgQlVORExFDQogZ3JvdXAuIElmIHRoZSBhbnN3ZXJlciBhY2NlcHRzIGl0LCB0aGVy
ZSBpcyBubyBuZWVkIGZvciBhIEJBUyBvZmZlci4gSWYgdGhlIGFuc3dlcmVyIHJlamVjdHMgaXQs
IHRoZXJlIHdpbGwgYmUgYSBmYWxsYmFjayB0byB0aGUgY3VycmVudCBCVU5ETEUgYWRkcmVzcyAo
dXNpbmcgbm9ybWFsIDMyNjQgcnVsZXMpLiBJIGJlbGlldmUgYW4gYWRkcmVzcyBjaGFuZ2Ugd2ls
bCBiZSBhY2NlcHRlZCBpbiBtb3N0IGNhc2VzLCBhbmQgaWYgaXTigJlzIG5vdCB0aGVuDQogdGhl
cmUgaXMgcHJvYmFibHkgZ29pbmcgdG8gYmUgcHJvYmxlbXMgYW55d2F54oCmPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlNvLCByZWdhcmRp
bmcgdGhlIGZpcnN0IGNoYW5nZSAoYWx3YXlzIGFzc2lnbiB0aGUgYnVuZGxlIGFkZHJlc3MgdG8g
YSBuZXcgbS0gbGluZSksIEkgc3VwcG9ydCB0aGF0IG9uZS4gQnV0LCBJIGRvIHJlYWxpemUgcGVv
cGxlIG1heSBoYXZlIG90aGVyIG9waW5pb25zLCBzbyB0aGF04oCZcyB3aHkgSSBsaWtlIHRvDQog
aGVhciB0aGVtIDopPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0QiPlJlZ2FyZGluZyB0aGUgc2Vjb25kIGNoYW5nZSAoYXNzaWduIHRoZSBuZXcg
YWRkcmVzcyB0byBhbGwgbS0gbGluZXMpLCBJIHBlcnNvbmFsbHkgc3VwcG9ydCBhbHNvIHRoYXQg
b25lLCBhbmQgSSBjYW7igJl0IHNlZSBhIHJlYXNvbiBub3QgdG8gZG8gaXQuIEJ1dCwgYWdhaW4s
IGZlZWwgZnJlZSB0byBwcm92ZQ0KIG1lIHdyb25nIDopPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlJlZ2FyZHMsPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkNocmlzdGVyPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cD48
bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiAxMyBEZWMgMjAx
NCAwNzo1NiwgJnF1b3Q7Q2hyaXN0ZXIgSG9sbWJlcmcmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0
bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iPmNocmlzdGVyLmhvbG1iZXJnQGVyaWNz
c29uLmNvbTwvYT4mZ3Q7IHdyb3RlOjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxl
ZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1s
ZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+SGksPGJyPg0KPGJyPg0KWW91
IGNhbiB0cnkgYWdhaW4gYnkgbm90IGFkZGluZyB0aGUgbS0gbGluZSB0byB0aGUgQlVORExFIGdy
b3VwLjxicj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2hyaXN0ZXI8YnI+DQo8YnI+DQpT
ZW50IGZyb20gbXkgV2luZG93cyBQaG9uZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHls
ZT0idGV4dC1hbGlnbjpjZW50ZXIiPg0KPGhyIHNpemU9IjMiIHdpZHRoPSIxMDAlIiBhbGlnbj0i
Y2VudGVyIj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+PGEgaHJlZj0ibWFpbHRvOmliY0BhbGlheC5uZXQiIHRhcmdldD0iX2JsYW5rIj5J
w7Fha2kgQmF6IENhc3RpbGxvPC9hPjwvc3Bhbj48YnI+DQo8Yj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlNl
bnQ6IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj7igI4xMy/igI4xMi/igI4yMDE0IDAzOjAz
PC9zcGFuPjxicj4NCjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+VG86IDwvc3Bhbj48L2I+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj48YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIiB0
YXJnZXQ9Il9ibGFuayI+Q2hyaXN0ZXIgSG9sbWJlcmc8L2E+PC9zcGFuPjxicj4NCjxiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+Q2M6IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48YSBocmVmPSJtYWls
dG86bW11c2ljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+SUVURiBNTVVTSUMgV0c8L2E+Ow0K
PGEgaHJlZj0ibWFpbHRvOnBreXppdmF0QGFsdW0ubWl0LmVkdSIgdGFyZ2V0PSJfYmxhbmsiPlBh
dWwgS3l6aXZhdDwvYT48L3NwYW4+PGJyPg0KPGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5TdWJqZWN0OiA8
L3NwYW4+DQo8L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5SZTogW01NVVNJQ10gYnVuZGxlLTEzIC0gUGF1
bCdzIGNvbW1lbnRzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+MjAx
NC0xMi0xMSA4OjAxIEdNVCYjNDM7MDE6MDAgQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0OzxhIGhyZWY9
Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iIHRhcmdldD0iX2JsYW5rIj5j
aHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208L2E+Jmd0Ozo8YnI+DQomZ3Q7IE9mIGNvdXJz
ZSwgaW4gdGhlIGNhc2Ugb2YgYWRkaW5nIGEgbmV3IG0tIGxpbmUgdG8gYSBCVU5ETEUgZ3JvdXAs
IGlmIHRoZSBhbnN3ZXJlciBkb2VzIG5vdCBhY2NlcHQgaXQgaW4gdGhlIEJVTkRMRSBncm91cCwg
dGhlIGFuc3dlcmVyIHdpbGwgaGF2ZSB0byByZWplY3QgaXQuPGJyPg0KPGJyPg0KJmd0OyBJbiB0
aGF0IGNhc2UsIHRoZSBvZmZlcmVyIGNvdWxkIHNlbmQgYSBuZXcgb2ZmZXIsPGJyPg0KPGJyPg0K
QnV0IHlvdSBrbm93IGl0IHdvbnQgWEQ8YnI+DQo8YnI+DQpXaHkgdG8gdHJ5IGFnYWluIGJ5IGNo
YW5naW5nICZxdW90O3NvbWV0aGluZyZxdW90Oz88YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCm1tdXNpYyBtYWlsaW5nIGxpc3Q8
YnI+DQo8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11
c2ljQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbW11c2ljIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9tbXVzaWM8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_7594FB04B1934943A5C02806D1A2204B1D5AB221ESESSMB209erics_--


From nobody Sat Dec 13 03:34:06 2014
Return-Path: <ari.keranen@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 761DC1A0037 for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 03:34:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 hIAB31oudjVV for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 03:34:03 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CED591A0030 for <mmusic@ietf.org>; Sat, 13 Dec 2014 03:34:02 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-89-548c2428b492
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 5B.E4.24955.8242C845; Sat, 13 Dec 2014 12:34:01 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.3.195.1; Sat, 13 Dec 2014 12:34:00 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 95EEB1102B1; Sat, 13 Dec 2014 13:34:00 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 8A3565F8F8;	Sat, 13 Dec 2014 13:35:02 +0200 (EET)
Received: from As-MacBook-Air.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E49E75F816;	Sat, 13 Dec 2014 13:35:01 +0200 (EET)
Message-ID: <548C2428.3060809@ericsson.com>
Date: Sat, 13 Dec 2014 11:34:00 +0000
From: =?windows-1252?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDLMWRmVeSWpSXmKPExsUyM+Jvja6mSk+IQe8uTov3F3Qtpi5/zOLA 5DHl90ZWjyVLfjIFMEVx2aSk5mSWpRbp2yVwZdzuespcsI6p4tO1FvYGxveMXYwcHBICJhLb p6l0MXICmWISF+6tZ+ti5OIQEjjCKLHk9ztWkISQwAZGif47XhCJPYwSpyaeYIZw1jJKzHrR A+UsZ5S4cGUfI0gLr4C2xP8Hm5hBbBYBVYndv46D2WwCjhK3H74EGysqkCyxZuskdoh6QYmT M5+wgNgiAjISezdtBqtnBpoz+84sJhBbWMBIonX+ZGaQs5kF7CUebC2DKJGX2P52DjPEC2oS V89BrBUCWnv13yvGCYzCs5BsmIXQPQtJ9wJG5lWMosWpxUm56UbGeqlFmcnFxfl5enmpJZsY gcF9cMtv1R2Ml984HmIU4GBU4uHdsLo7RIg1say4MvcQozQHi5I478Jz84KFBNITS1KzU1ML Uovii0pzUosPMTJxcEo1MIZHJTO4vldcalmhOWtWSsGqQMbghpYv7OYca30TGUV27055H776 QPKHYqYjTl/vJKn6JP6/X/wyzPyks83637o+rB52Wta/jPQmylzWjXvqvbItnKkh18Ztexib /pEr3180q/46kPZaa3PHz7Kyz61W0gFKgoLHZlddKj/3m0Wpy6lwb8x3JZbijERDLeai4kQA R8+/U08CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/QJuaF0AXBls5SFJNhKqtR5BFPIE
Cc: Flemming Andreasen <fandreas@cisco.com>
Subject: [MMUSIC] Draft MMUSIC Meeting Minutes from IETF 91
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 11:34:04 -0000

Hi all,

The draft meeting minutes for the two MMUSIC sessions at IETF 91 in 
Honolulu are available at:

   http://www.ietf.org/proceedings/91/minutes/minutes-91-mmusic

Please take a look and let us know if you have any questions or comments.


Thanks,
Ari & Flemming
(MMUSIC co-chairs)


From nobody Sat Dec 13 08:48:11 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF0F1A1A36 for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 08:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level: 
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 gWuwbRv8fhab for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 08:48:07 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08F021A1A07 for <mmusic@ietf.org>; Sat, 13 Dec 2014 08:48:07 -0800 (PST)
Received: from us70tusmtp1.zam.alcatel-lucent.com (unknown [135.5.2.63]) by Websense Email Security Gateway with ESMTPS id 67C6D454DAE93; Sat, 13 Dec 2014 16:47:58 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id sBDGm35h022906 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 13 Dec 2014 11:48:03 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Sat, 13 Dec 2014 11:48:03 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] bundle-13 - Paul's comments
Thread-Index: AQHQFIY1q3i7v5ypXUS+mvZc6iMtqZyMuEqNgAC2cYCAAC2OAIAAF/OAgAADSQA=
Date: Sat, 13 Dec 2014 16:48:02 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E65F5CC@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se> <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se> <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5AB221@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5AB221@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/x33vnmOnD6rrlpyCL5rhlFdVsTE
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 16:48:09 -0000

DQoNCj5Gcm9tOiBtbXVzaWMgW21haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVo
YWxmIE9mIENocmlzdGVyIEhvbG1iZXJnDQo+U2VudDogU2F0dXJkYXksIERlY2VtYmVyIDEzLCAy
MDE0IDU6MDYgQU0NCg0KPkhpLA0KPllvdSBkb24ndCBrbm93IHdoeSB0aGUgcGVlciByZWplY3Rl
ZCBpdCwgc28gdHJ5aW5nIGFnYWluIChieSByYW5kb21seSA+Y2hhbmdpbmcgc29tZXRoaW5nKSBk
b2VzIG5vdCBwcm92aWRlIGEgZGV0ZXJtaW5pc3QgYmVoYXZpb3IvcmVzdWx0Lg0KPldlbGwsIHRo
YXQgaXMgdW5mb3J0dW5hdGVseSBhIGdlbmVyYWwgcHJvYmxlbSBpbiBTRFAgTy9BLiBZb3UgZG9u
4oCZdCBhbHdheXMgPmtub3cgZXhhY3RseSB3aHkgc29tZXRoaW5nIGlzIHJlamVjdGVkLg0KPkFs
c28ga2VlcCBpbiBtaW5kIHRoYXQgdGhlIGN1cnJlbnQgZHJhZnQsIHdoZW4gYW4gbS0gbGluZSBp
cyBhZGRlZCB0byBhbiA+QlVORExFIGdyb3VwLCBhbHJlYWR5IGFsbG93cyBhc3NpZ25pbmcgdGhl
IEJVTkRMRSBhZGRyZXNzIHRvIHRoYXQgbS0gbGluZS4gPlNvLCB0aGF0IGlzIG5vdGhpbmcgbmV3
LiBXaGF0IGlzIG5ldyBpcyB0aGF0IHRoZSBvZmZlcmVyIHdvdWxkIGFsd2F5cyBhZGQgPnRoZSBC
VU5ETEUgYWRkcmVzcyB0byB0aGUgYWRkZWQgbS0gbGluZSwgd2hpY2ggYWxzbyBoZWxwcyBzZXR0
aW5nIHRoZSA+YXNzb2NpYXRlZCBTRFAgYXR0cmlidXRlIHZhbHVlcyBldGMgKHRoZSB2YWx1ZXMg
bWF5IGJlIGRpZmZlcmVudCBkZXBlbmRpbmcgPm9uIHdoZXRoZXIgYW4gbS0gbGluZSBpcyB3aXRo
aW4gYSBCVU5ETEUgZ3JvdXAgb3Igbm90LCBhcyBkZXNjcmliZWQgaW4gdGhlID5zZHAtbXV4IGRy
YWZ0KS4NCj5UaGUgc2Vjb25kIG5ldyB0aGluZyAod2hpY2ggdHJpZ2dlcmVkIHRoaXMgZGlzY3Vz
c2lvbikgaXMgdGhhdCwgd2hlbiBhIG5ldyA+QlVORExFIGFkZHJlc3MgaXMgc3VnZ2VzdGVkLCB0
aGF0IEJVTkRMRSBhZGRyZXNzIHNob3VsZCBiZSBhc3NpZ25lZCB0byBhbGwgPm0tIGxpbmVzIHdp
dGhpbiB0aGUgQlVORExFIGdyb3VwLiBJZiB0aGUgYW5zd2VyZXIgYWNjZXB0cyBpdCwgdGhlcmUg
aXMgbm8gPm5lZWQgZm9yIGEgQkFTIG9mZmVyLiBJZiB0aGUgYW5zd2VyZXIgcmVqZWN0cyBpdCwg
dGhlcmUgd2lsbCBiZSBhIGZhbGxiYWNrID50byB0aGUgY3VycmVudCBCVU5ETEUgYWRkcmVzcyAo
dXNpbmcgbm9ybWFsIDMyNjQgcnVsZXMpLiBJIGJlbGlldmUgYW4gPmFkZHJlc3MgY2hhbmdlIHdp
bGwgYmUgYWNjZXB0ZWQgaW4gbW9zdCBjYXNlcywgYW5kIGlmIGl04oCZcyBub3QgdGhlbiB0aGVy
ZSBpcyA+cHJvYmFibHkgZ29pbmcgdG8gYmUgcHJvYmxlbXMgYW55d2F54oCmDQo+U28sIHJlZ2Fy
ZGluZyB0aGUgZmlyc3QgY2hhbmdlIChhbHdheXMgYXNzaWduIHRoZSBidW5kbGUgYWRkcmVzcyB0
byBhIG5ldyBtLSA+bGluZSksIEkgc3VwcG9ydCB0aGF0IG9uZS4gQnV0LCBJIGRvIHJlYWxpemUg
cGVvcGxlIG1heSBoYXZlIG90aGVyIG9waW5pb25zLCA+c28gdGhhdOKAmXMgd2h5IEkgbGlrZSB0
byBoZWFyIHRoZW0gOikNCg0KPFJhanU+DQpJZiBhbnN3ZXJlciByZWplY3RzIEJVTkRMRSBmb3Ig
bmV3IG09IGxpbmUgdGhlbiBhIEJBUyBvZmZlciBpcyByZXF1aXJlZC4gU3VjaCBCQVMgaXMgcmVx
dWlyZWQgZm9yIGluaXRpYWwgb2ZmZXIvYW5zd2VyIG9ubHkgaWYgQlVORExFIGlzIG5lZ290aWF0
ZWQuIEJ1dCBmb3Igc3ViLXNlcXVlbnQgb2ZmZXIvYW5zd2VyIG1ha2luZyBCQVMgcmVxdWlyZW1l
bnQgZm9yIG5vbi1CVU5ETEUgY2FzZSBpcyBraW5kIG9mIGNvbmZ1c2luZyBhbmQgaW5jb25zaXN0
ZW50LiBJTUhPLCBoYXZpbmcgQkFTIHJlcXVpcmVtZW50IG9ubHkgZm9yIEJVTkRMRSBjYXNlIG9m
IGluaXRpYWwgYW5kIHN1Yi1zZXF1ZW50IG9mZmVycyBpcyBjbGVhciBhbmQgc2ltcGxlLg0KDQpB
bHNvLCBpZiB0aGUgb2ZmZXJlciB3YW50cyBuZXcgbT0gbGluZSBhcyAnYnVuZGxlLW9ubHknIHRo
ZW4gd29uJ3QgaXQgc3RpbGwgc2V0IHBvcnQgdG8gMD8gQWdhaW4sIElNTywgbWFraW5nIHNlbWFu
dGljcyBmb3IgdGhpcyBjb25zaXN0ZW50IHdpdGggaW5pdGlhbCBvZmZlciBpcyBhbHNvIGNsZWFy
IGFuZCBzaW1wbGUuDQoNCkluaXRpYWwgb2ZmZXIvYW5zd2VyIG5lZ290aWF0aW5nIGEgQlVORExF
IGlzIG5vIGd1YXJhbnRlZSB0aGF0IHN1Yi1zZXF1ZW50IG9mZmVyL2Fuc3dlcnMgYWxzbyBkbyBz
by4gVGhpcyBpcyBiZWNhdXNlIG5ld2x5IGFkZGVkIG09IGxpbmUncyBkZXN0aW5hdGlvbiBjb3Vs
ZCBiZSBkaWZmZXJlbnQgZnJvbSBwcmV2aW91c2x5IG5lZ290aWF0ZWQgQlVORExFRCBkZXN0aW5h
dGlvbiBhZGRyZXNzIGFzIGl0IG1heSB0cmF2ZXJzZSBkaWZmZXJlbnQgbWlkZGxlIGJveGVzIChl
LmcuIHZpZGVvIHRyYW5zY29kaW5nIHJlcXVpcmVtZW50cyBmb3IgbmV3bHkgYWRkZWQgbT0gbGlu
ZSkuIA0KDQo8L1JhanU+DQoNCj5SZWdhcmRpbmcgdGhlIHNlY29uZCBjaGFuZ2UgKGFzc2lnbiB0
aGUgbmV3IGFkZHJlc3MgdG8gYWxsIG0tIGxpbmVzKSwgSSA+cGVyc29uYWxseSBzdXBwb3J0IGFs
c28gdGhhdCBvbmUsIGFuZCBJIGNhbuKAmXQgc2VlIGEgcmVhc29uIG5vdCB0byBkbyBpdC4gPkJ1
dCwgYWdhaW4sIGZlZWwgZnJlZSB0byBwcm92ZSBtZSB3cm9uZyA6KQ0KDQo8UmFqdT4NCldoZW4g
YSBuZXcgQlVORExFIGFkZHJlc3MgaXMgc3VnZ2VzdGVkLCB0aGUgc2FtZSBTRFAgbWF5IGNoYW5n
ZSBzb21lIG90aGVyIHBhcmFtZXRlcnMgKGxpa2UgdmlkZW8gY29kZWNzKS4gU3VjaCBjaGFuZ2Vz
IG1heSByZXF1aXJlIGRpZmZlcmVudCBkZXN0aW5hdGlvbihzKSB0byBiZSBwcm92aWRlZCBpbiBT
RFAgYW5zd2VyIGFuZCBhcyBhIHJlc3VsdCBwcmV2aW91cyBCVU5ETEUgYWRkcmVzcyBjYW4ndCBi
ZSB1c2VkLiBTbywgZXZlbiBpbiB0aGlzIGNhc2UgaXQgaXMgYmV0dGVyIHRvIGJlIGNvbnNpc3Rl
bnQgYW5kIGhhdmUgc2FtZSBydWxlcyBhcyBpbml0aWFsIG9mZmVyL2Fuc3dlciwgaS5lLiB0byBh
c3NpZ24gdW5pcXVlIGFkZHJlc3MgZm9yIGVhY2ggbT0gbGluZSBhbmQgaWYgQlVORExFIGlzIG5l
Z290aWF0ZWQgdGhlbiBmb2xsb3cgdXAgd2l0aCBCQVMgb2ZmZXIuDQoNCkV2ZW4gaWYgdGhlIFNE
UCBqdXN0IGNoYW5nZXMgQlVORExFIGFkZHJlc3Mgb25seSwgSU1ITywgdG8gcHJlc2VydmUgY29u
c2lzdGVuY3kgYW5kIGtlZXBpbmcgaXQgc2ltcGxlIGl0IGlzIGJldHRlciB0byBzdGljayB0byBp
bml0aWFsIG9mZmVyL2Fuc3dlciBzZW1hbnRpY3MuDQoNCjwvUmFqdT4NCg0KQlINClJhanUNCg==


From nobody Sat Dec 13 09:28:29 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAC41A1A98 for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 09:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level: 
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 1flMo64RAKAs for <mmusic@ietfa.amsl.com>; Sat, 13 Dec 2014 09:28:25 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2469D1A1A19 for <mmusic@ietf.org>; Sat, 13 Dec 2014 09:28:24 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-37-548c7737f1e8
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 18.BB.04231.7377C845; Sat, 13 Dec 2014 18:28:23 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.68]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0195.001; Sat, 13 Dec 2014 18:28:22 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] bundle-13 - Paul's comments
Thread-Index: AdAUTBbGQ9NZrkv1S3WttkWwhKcfqQAMbXWAACPMjwAAVs4OgAAOcQBqAAOZUQAABFcCkAAKnDUAAALcZPA=
Date: Sat, 13 Dec 2014 17:28:21 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5AC973@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se> <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se> <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5AB221@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E65F5CC@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E65F5CC@US70UWXCHMBA02.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42KZGfG3Rte8vCfEoGuZqMX0fTYWU5c/ZrFY seEAq0XDxiusDiwerc/2snqca3jP7vH3/QcmjyVLfjIFsERx2aSk5mSWpRbp2yVwZRw5+pa9 YIZexc8/59gaGBt0uxg5OSQETCQer77MCGGLSVy4t56ti5GLQ0jgCKPE0omroJzFjBLvP/Wx dzFycLAJWEh0/9MGiYsINDJKLFkwjwWkm1nAV+L9z+nsILawgKHEl0P7wKaKCBhJPJ+ykh3C TpKYOPsuK4jNIqAqcfrEMrBeXqDeFVd7WCGWzWGRmLJ1MxNIglMgVmL95vlgDYxA530/tYYJ Ypm4xK0n85kgzhaQWLLnPDOELSrx8vE/VghbSWLt4e0sIEczC2hKrN+lD9GqKDGl+yE7xF5B iZMzn7BMYBSbhWTqLISOWUg6ZiHpWMDIsopRtDi1uDg33chYL7UoM7m4OD9PLy+1ZBMjMMoO bvmtu4Nx9WvHQ4wCHIxKPLwbVneHCLEmlhVX5h5ilOZgURLnXXRuXrCQQHpiSWp2ampBalF8 UWlOavEhRiYOTqkGxrSoX2da5m9+eV5YWTHvpJy/3O43CVtD+D/uWcaX5xT+cM35NW90dnYd bJ7kvDq4scBnXai/a+K+1UXTfO8+cDghmBl36c7+8zdmldm3zfh6UfODSq9X80dWdqftZvp8 PxT0vverv1lY/b35Z5bA80q2KM9VH8TsPn2Zom3U51Pq1j39mEDYEiWW4oxEQy3mouJEAG/y f6mTAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/xIJh4AJmkIAeOgXtTD_AeecJC8U
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Dec 2014 17:28:28 -0000

SGksDQoNCj4+PllvdSBkb24ndCBrbm93IHdoeSB0aGUgcGVlciByZWplY3RlZCBpdCwgc28gdHJ5
aW5nIGFnYWluIChieSByYW5kb21seSANCj4+PmNoYW5naW5nIHNvbWV0aGluZykgZG9lcyBub3Qg
cHJvdmlkZSBhIGRldGVybWluaXN0IGJlaGF2aW9yL3Jlc3VsdC4NCj4+Pg0KPj5XZWxsLCB0aGF0
IGlzIHVuZm9ydHVuYXRlbHkgYSBnZW5lcmFsIHByb2JsZW0gaW4gU0RQIE8vQS4gWW91IGRvbuKA
mXQgYWx3YXlzIA0KPj5rbm93IGV4YWN0bHkgd2h5IHNvbWV0aGluZyBpcyByZWplY3RlZC4NCj4+
DQo+PkFsc28ga2VlcCBpbiBtaW5kIHRoYXQgdGhlIGN1cnJlbnQgZHJhZnQsIHdoZW4gYW4gbS0g
bGluZSBpcyBhZGRlZCB0byBhbiANCj4+QlVORExFIGdyb3VwLCBhbHJlYWR5IGFsbG93cyBhc3Np
Z25pbmcgdGhlIEJVTkRMRSBhZGRyZXNzIHRvIHRoYXQgbS0gbGluZS4gDQo+PlNvLCB0aGF0IGlz
IG5vdGhpbmcgbmV3LiBXaGF0IGlzIG5ldyBpcyB0aGF0IHRoZSBvZmZlcmVyIHdvdWxkIGFsd2F5
cyBhZGQgDQo+PnRoZSBCVU5ETEUgYWRkcmVzcyB0byB0aGUgYWRkZWQgbS0gbGluZSwgd2hpY2gg
YWxzbyBoZWxwcyBzZXR0aW5nIHRoZSANCj4+YXNzb2NpYXRlZCBTRFAgYXR0cmlidXRlIHZhbHVl
cyBldGMgKHRoZSB2YWx1ZXMgbWF5IGJlIGRpZmZlcmVudCBkZXBlbmRpbmcgDQo+Pm9uIHdoZXRo
ZXIgYW4gbS0gbGluZSBpcyB3aXRoaW4gYSBCVU5ETEUgZ3JvdXAgb3Igbm90LCBhcyBkZXNjcmli
ZWQgaW4gdGhlIA0KPj5zZHAtbXV4IGRyYWZ0KS4NCj4+DQo+PlRoZSBzZWNvbmQgbmV3IHRoaW5n
ICh3aGljaCB0cmlnZ2VyZWQgdGhpcyBkaXNjdXNzaW9uKSBpcyB0aGF0LCB3aGVuIGEgDQo+Pm5l
dyBCVU5ETEUgYWRkcmVzcyBpcyBzdWdnZXN0ZWQsIHRoYXQgQlVORExFIGFkZHJlc3Mgc2hvdWxk
IGJlIA0KPj5hc3NpZ25lZCB0byBhbGwgbS0gbGluZXMgd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXAu
IElmIHRoZSBhbnN3ZXJlciANCj4+YWNjZXB0cyBpdCwgdGhlcmUgaXMgbm8gbmVlZCBmb3IgYSBC
QVMgb2ZmZXIuIElmIHRoZSBhbnN3ZXJlciByZWplY3RzIA0KPj5pdCwgdGhlcmUgd2lsbCBiZSBh
IGZhbGxiYWNrIHRvIHRoZSBjdXJyZW50IEJVTkRMRSBhZGRyZXNzICh1c2luZyANCj4+bm9ybWFs
IDMyNjQgcnVsZXMpLiBJIGJlbGlldmUgYW4gYWRkcmVzcyBjaGFuZ2Ugd2lsbCBiZSBhY2NlcHRl
ZCBpbiANCj4+bW9zdCBjYXNlcywgYW5kIGlmIGl04oCZcyBub3QgdGhlbiB0aGVyZSBpcyBwcm9i
YWJseSBnb2luZyB0byBiZSANCj4+cHJvYmxlbXMgYW55d2F54oCmIFNvLCByZWdhcmRpbmcgdGhl
IGZpcnN0IGNoYW5nZSAoYWx3YXlzIGFzc2lnbiB0aGUgDQo+PmJ1bmRsZSBhZGRyZXNzIHRvIGEg
bmV3IG0tIGxpbmUpLCBJIHN1cHBvcnQgdGhhdCBvbmUuIEJ1dCwgSSBkbyANCj4+cmVhbGl6ZSBw
ZW9wbGUgbWF5IGhhdmUgb3RoZXIgb3BpbmlvbnMsID5zbyB0aGF04oCZcyB3aHkgSSBsaWtlIHRv
IGhlYXIgDQo+PnRoZW0gOikNCj4NCj5JZiBhbnN3ZXJlciByZWplY3RzIEJVTkRMRSBmb3IgbmV3
IG09IGxpbmUgdGhlbiBhIEJBUyBvZmZlciBpcyByZXF1aXJlZC4NCg0KV2h5Pw0KDQpBIEJBUyBv
ZmZlciBpcyBvbmx5IG5lZWRlZCBpZiB0aGUgc2VsZWN0ZWQgb2ZmZXJlciBCVU5ETEUgYWRkcmVz
cyBpcyBkaWZmZXJlbnQgZnJvbSBvbiBvciBtb3JlIG9mIHRoZSBhZGRyZXNzZXMgaW4gdGhlIG9m
ZmVyLg0KDQo+U3VjaCBCQVMgaXMgcmVxdWlyZWQgZm9yIGluaXRpYWwgb2ZmZXIvYW5zd2VyIG9u
bHkgaWYgQlVORExFIGlzIG5lZ290aWF0ZWQuIEJ1dCBmb3IgDQo+IHN1Yi1zZXF1ZW50IG9mZmVy
L2Fuc3dlciBtYWtpbmcgQkFTIHJlcXVpcmVtZW50IGZvciBub24tQlVORExFIGNhc2UgaXMga2lu
ZCBvZiA+Y29uZnVzaW5nIGFuZCBpbmNvbnNpc3RlbnQuDQoNCk5vbi1CVU5ETEUgY2FzZT8gSSBh
bSBub3Qgc3VyZSBJIHVuZGVyc3RhbmQuLi4NCg0KPklNSE8sIGhhdmluZyBCQVMgcmVxdWlyZW1l
bnQgb25seSBmb3IgQlVORExFIGNhc2Ugb2YgaW5pdGlhbCBhbmQgc3ViLXNlcXVlbnQgPm9mZmVy
cyBpcyBjbGVhciBhbmQgc2ltcGxlLg0KDQpXZWxsLCB0aGF0IGlzIHdoYXQgdGhlIGRyYWZ0IGN1
cnJlbnRseSBzYXlzLiBQYXVsJ3Mgc3VnZ2VzdGlvbiByZW1vdmVzIHRoZSBuZWVkIGZvciBhIEJB
UyBpbiBzdWItc2VxdWVudCBvZmZlcnMsIHdoaWNoIGlzIGdvb2QuDQoNCj5BbHNvLCBpZiB0aGUg
b2ZmZXJlciB3YW50cyBuZXcgbT0gbGluZSBhcyAnYnVuZGxlLW9ubHknIHRoZW4gd29uJ3QgaXQg
c3RpbGwgc2V0IHBvcnQgdG8gPjA/IEFnYWluLCBJTU8sIG1ha2luZyBzZW1hbnRpY3MgZm9yIHRo
aXMgY29uc2lzdGVudCB3aXRoIGluaXRpYWwgb2ZmZXIgaXMgYWxzbyBjbGVhciBhbmQgPnNpbXBs
ZS4NCg0KUG9ydCB6ZXJvIGlzIG5vdCBuZWVkZWQgaW4gc3ViLXNlcXVlbnQgb2ZmZXJzLCBiZWNh
dXNlIHlvdSBnZXQgdGhlIHNhbWUgZWZmZWN0IGJ5IGFzc2lnbmluZyB0aGUgQlVORExFIGFkZHJl
c3MgdG8gdGhlIG5ldyBtLSBsaW5lOiBpZiB0aGUgYW5zd2VyZXIgZG9lcyBub3QgYWNjZXB0IGl0
IGludG8gdGhlIEJVTkRMRSBncm91cCwgaXQgTVVTVCByZWplY3QgaXQuIEFuZCwgaWYgdGhlIGFu
c3dlcmVyIGFjY2VwdHMgdGhlIG5ldyBtLSBsaW5lIGludG8gdGhlIEJVTkRMRSBncm91cCwgYSBC
QVMgb2ZmZXIgaXMgbm90IG5lZWRlZCAoYXMgdGhlIEJVTkRMRSBhZGRyZXNzIHdhcyBhc3NpZ25l
ZCB0byB0aGUgbmV3IG0tIGxpbmUgaW4gdGhlIG9mZmVyKS4gDQoNCj5Jbml0aWFsIG9mZmVyL2Fu
c3dlciBuZWdvdGlhdGluZyBhIEJVTkRMRSBpcyBubyBndWFyYW50ZWUgdGhhdCBzdWItc2VxdWVu
dCA+b2ZmZXIvYW5zd2VycyBhbHNvIGRvIHNvLiBUaGlzIGlzIGJlY2F1c2UgbmV3bHkgYWRkZWQg
bT0gbGluZSdzIGRlc3RpbmF0aW9uIGNvdWxkIGJlID5kaWZmZXJlbnQgZnJvbSBwcmV2aW91c2x5
IG5lZ290aWF0ZWQgQlVORExFRCBkZXN0aW5hdGlvbiBhZGRyZXNzIGFzIGl0IG1heSB0cmF2ZXJz
ZSA+ZGlmZmVyZW50IG1pZGRsZSBib3hlcyAoZS5nLiB2aWRlbyB0cmFuc2NvZGluZyByZXF1aXJl
bWVudHMgZm9yIG5ld2x5IGFkZGVkIG09ID5saW5lKS4NCg0KU3VyZS4gQnV0LCBpbiB0aGF0IGNh
c2UgdGhlIG9mZmVyZXIgY2FuIHNlbmQgYSBuZXcgb2ZmZXIsIHdoZXJlIHRoZSBuZXcgbS0gbGlu
ZSBpcyBub3QgYWRkZWQgdG8gdGhlIEJVTkRMRSBncm91cC4gVGhhdCBpcyB0aGUgY2FzZSBhbHJl
YWR5IHRvZGF5LCBiZWNhdXNlIHRoZSBkcmFmdCBhbGxvd3MgYXNzaWduaW5nIHRoZSBCVU5ETEUg
YWRkcmVzcyB0byB0aGUgbmV3IG0tIGxpbmUuDQoNCj4+UmVnYXJkaW5nIHRoZSBzZWNvbmQgY2hh
bmdlIChhc3NpZ24gdGhlIG5ldyBhZGRyZXNzIHRvIGFsbCBtLSBsaW5lcyksIEkgDQo+PnBlcnNv
bmFsbHkgc3VwcG9ydCBhbHNvIHRoYXQgb25lLCBhbmQgSSBjYW7igJl0IHNlZSBhIHJlYXNvbiBu
b3QgdG8gZG8gDQo+Pml0LiBCdXQsIGFnYWluLCBmZWVsIGZyZWUgdG8gcHJvdmUgbWUgd3Jvbmcg
OikNCj4NCj4NCj5XaGVuIGEgbmV3IEJVTkRMRSBhZGRyZXNzIGlzIHN1Z2dlc3RlZCwgdGhlIHNh
bWUgU0RQIG1heSBjaGFuZ2Ugc29tZSBvdGhlciA+cGFyYW1ldGVycyAobGlrZSB2aWRlbyBjb2Rl
Y3MpLiBTdWNoIGNoYW5nZXMgbWF5IHJlcXVpcmUgZGlmZmVyZW50IGRlc3RpbmF0aW9uKHMpIHRv
ID5iZSBwcm92aWRlZCBpbiBTRFAgYW5zd2VyIGFuZCBhcyBhIHJlc3VsdCBwcmV2aW91cyBCVU5E
TEUgYWRkcmVzcyBjYW4ndCBiZSB1c2VkLiA+U28sIGV2ZW4gaW4gdGhpcyBjYXNlIGl0IGlzIGJl
dHRlciB0byBiZSBjb25zaXN0ZW50IGFuZCBoYXZlIHNhbWUgcnVsZXMgYXMgaW5pdGlhbCA+b2Zm
ZXIvYW5zd2VyLCBpLmUuIHRvIGFzc2lnbiB1bmlxdWUgYWRkcmVzcyBmb3IgZWFjaCBtPSBsaW5l
IGFuZCBpZiBCVU5ETEUgaXMgPm5lZ290aWF0ZWQgdGhlbiBmb2xsb3cgdXAgd2l0aCBCQVMgb2Zm
ZXIuDQo+DQo+RXZlbiBpZiB0aGUgU0RQIGp1c3QgY2hhbmdlcyBCVU5ETEUgYWRkcmVzcyBvbmx5
LCBJTUhPLCB0byBwcmVzZXJ2ZSBjb25zaXN0ZW5jeSA+YW5kIGtlZXBpbmcgaXQgc2ltcGxlIGl0
IGlzIGJldHRlciB0byBzdGljayB0byBpbml0aWFsIG9mZmVyL2Fuc3dlciBzZW1hbnRpY3MuDQoN
ClBlcmhhcHMgd2Ugc2hvdWxkIGFsbG93IGJvdGggYWx0ZXJuYXRpdmVzIHRoZW4uIEl0IGVuYWJs
ZXMgdGhlIGNhc2Ugb2Ygbm90IGhhdmluZyB0byBzZW5kIHRoZSBCQVMgb2ZmZXIgaXMgdGhlIG9m
ZmVyIGlzIGFjY2VwdGVkLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=


From nobody Sun Dec 14 06:55:40 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F881A6FBA for <mmusic@ietfa.amsl.com>; Sun, 14 Dec 2014 06:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level: 
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 r7ODnWLTl4LB for <mmusic@ietfa.amsl.com>; Sun, 14 Dec 2014 06:55:37 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A624F1A6FB1 for <mmusic@ietf.org>; Sun, 14 Dec 2014 06:55:36 -0800 (PST)
Received: from us70uusmtp4.zam.alcatel-lucent.com (unknown [135.5.2.66]) by Websense Email Security Gateway with ESMTPS id 3DF2EE0E4B3E6; Sun, 14 Dec 2014 14:55:31 +0000 (GMT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id sBEEtWkc023175 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 14 Dec 2014 09:55:32 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.03.0195.001; Sun, 14 Dec 2014 09:55:32 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
Thread-Topic: [MMUSIC] bundle-13 - Paul's comments
Thread-Index: AQHQFIY1q3i7v5ypXUS+mvZc6iMtqZyMuEqNgAC2cYCAAC2OAIAAF/OAgAADSQCAAGehgIABCz7g
Date: Sun, 14 Dec 2014 14:55:30 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E65FF0C@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D58B788@ESESSMB209.ericsson.se> <54885995.2060305@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D58DDD5@ESESSMB209.ericsson.se> <CALiegf=tJ0izpyuzu2JHWos3QCX+GA2xuU3nL+uhZ=Ve65u-RA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5A0AE4@ESESSMB209.ericsson.se> <CALiegfnk2FsgeF9T6pyF+TSmhLhtM0upEDTRUzghb-+XRpOOtQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D5AB221@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E65F5CC@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D5AC973@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5AC973@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ai9tvjYzpMRbNAsBJ338Dtsqjf8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] bundle-13 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Dec 2014 14:55:39 -0000

PiBIaSwNCj4gDQo+ID4+PllvdSBkb24ndCBrbm93IHdoeSB0aGUgcGVlciByZWplY3RlZCBpdCwg
c28gdHJ5aW5nIGFnYWluIChieSByYW5kb21seQ0KPiA+Pj5jaGFuZ2luZyBzb21ldGhpbmcpIGRv
ZXMgbm90IHByb3ZpZGUgYSBkZXRlcm1pbmlzdCBiZWhhdmlvci9yZXN1bHQuDQo+ID4+Pg0KPiA+
PldlbGwsIHRoYXQgaXMgdW5mb3J0dW5hdGVseSBhIGdlbmVyYWwgcHJvYmxlbSBpbiBTRFAgTy9B
LiBZb3UgZG9u4oCZdCBhbHdheXMNCj4gPj5rbm93IGV4YWN0bHkgd2h5IHNvbWV0aGluZyBpcyBy
ZWplY3RlZC4NCj4gPj4NCj4gPj5BbHNvIGtlZXAgaW4gbWluZCB0aGF0IHRoZSBjdXJyZW50IGRy
YWZ0LCB3aGVuIGFuIG0tIGxpbmUgaXMgYWRkZWQgdG8gYW4NCj4gPj5CVU5ETEUgZ3JvdXAsIGFs
cmVhZHkgYWxsb3dzIGFzc2lnbmluZyB0aGUgQlVORExFIGFkZHJlc3MgdG8gdGhhdCBtLSBsaW5l
Lg0KPiA+PlNvLCB0aGF0IGlzIG5vdGhpbmcgbmV3LiBXaGF0IGlzIG5ldyBpcyB0aGF0IHRoZSBv
ZmZlcmVyIHdvdWxkIGFsd2F5cyBhZGQNCj4gPj50aGUgQlVORExFIGFkZHJlc3MgdG8gdGhlIGFk
ZGVkIG0tIGxpbmUsIHdoaWNoIGFsc28gaGVscHMgc2V0dGluZyB0aGUNCj4gPj5hc3NvY2lhdGVk
IFNEUCBhdHRyaWJ1dGUgdmFsdWVzIGV0YyAodGhlIHZhbHVlcyBtYXkgYmUgZGlmZmVyZW50IGRl
cGVuZGluZw0KPiA+Pm9uIHdoZXRoZXIgYW4gbS0gbGluZSBpcyB3aXRoaW4gYSBCVU5ETEUgZ3Jv
dXAgb3Igbm90LCBhcyBkZXNjcmliZWQgaW4gdGhlDQo+ID4+c2RwLW11eCBkcmFmdCkuDQo+ID4+
DQo+ID4+VGhlIHNlY29uZCBuZXcgdGhpbmcgKHdoaWNoIHRyaWdnZXJlZCB0aGlzIGRpc2N1c3Np
b24pIGlzIHRoYXQsIHdoZW4gYQ0KPiA+Pm5ldyBCVU5ETEUgYWRkcmVzcyBpcyBzdWdnZXN0ZWQs
IHRoYXQgQlVORExFIGFkZHJlc3Mgc2hvdWxkIGJlDQo+ID4+YXNzaWduZWQgdG8gYWxsIG0tIGxp
bmVzIHdpdGhpbiB0aGUgQlVORExFIGdyb3VwLiBJZiB0aGUgYW5zd2VyZXINCj4gPj5hY2NlcHRz
IGl0LCB0aGVyZSBpcyBubyBuZWVkIGZvciBhIEJBUyBvZmZlci4gSWYgdGhlIGFuc3dlcmVyIHJl
amVjdHMNCj4gPj5pdCwgdGhlcmUgd2lsbCBiZSBhIGZhbGxiYWNrIHRvIHRoZSBjdXJyZW50IEJV
TkRMRSBhZGRyZXNzICh1c2luZw0KPiA+Pm5vcm1hbCAzMjY0IHJ1bGVzKS4gSSBiZWxpZXZlIGFu
IGFkZHJlc3MgY2hhbmdlIHdpbGwgYmUgYWNjZXB0ZWQgaW4NCj4gPj5tb3N0IGNhc2VzLCBhbmQg
aWYgaXTigJlzIG5vdCB0aGVuIHRoZXJlIGlzIHByb2JhYmx5IGdvaW5nIHRvIGJlDQo+ID4+cHJv
YmxlbXMgYW55d2F54oCmIFNvLCByZWdhcmRpbmcgdGhlIGZpcnN0IGNoYW5nZSAoYWx3YXlzIGFz
c2lnbiB0aGUNCj4gPj5idW5kbGUgYWRkcmVzcyB0byBhIG5ldyBtLSBsaW5lKSwgSSBzdXBwb3J0
IHRoYXQgb25lLiBCdXQsIEkgZG8NCj4gPj5yZWFsaXplIHBlb3BsZSBtYXkgaGF2ZSBvdGhlciBv
cGluaW9ucywgPnNvIHRoYXTigJlzIHdoeSBJIGxpa2UgdG8gaGVhcg0KPiA+PnRoZW0gOikNCj4g
Pg0KPiA+SWYgYW5zd2VyZXIgcmVqZWN0cyBCVU5ETEUgZm9yIG5ldyBtPSBsaW5lIHRoZW4gYSBC
QVMgb2ZmZXIgaXMgcmVxdWlyZWQuDQo+IA0KPiBXaHk/DQoNCjxSYWp1Pg0KSSBtZWFudCBhIG5l
dyBvZmZlciwgbm90IEJBUyBvZmZlciwgdG8gdHJ5IG09IGxpbmUgd2l0aG91dCBCVU5ETEUuIFNv
cnJ5IGZvciBzdGF0aW5nIGl0IHdyb25nLg0KDQo8L1JhanU+DQoNCj4gDQo+IEEgQkFTIG9mZmVy
IGlzIG9ubHkgbmVlZGVkIGlmIHRoZSBzZWxlY3RlZCBvZmZlcmVyIEJVTkRMRSBhZGRyZXNzIGlz
DQo+IGRpZmZlcmVudCBmcm9tIG9uIG9yIG1vcmUgb2YgdGhlIGFkZHJlc3NlcyBpbiB0aGUgb2Zm
ZXIuDQo+IA0KPiA+U3VjaCBCQVMgaXMgcmVxdWlyZWQgZm9yIGluaXRpYWwgb2ZmZXIvYW5zd2Vy
IG9ubHkgaWYgQlVORExFIGlzIG5lZ290aWF0ZWQuDQo+IEJ1dCBmb3INCj4gPiBzdWItc2VxdWVu
dCBvZmZlci9hbnN3ZXIgbWFraW5nIEJBUyByZXF1aXJlbWVudCBmb3Igbm9uLUJVTkRMRSBjYXNl
IGlzDQo+IGtpbmQgb2YgPmNvbmZ1c2luZyBhbmQgaW5jb25zaXN0ZW50Lg0KPiANCj4gTm9uLUJV
TkRMRSBjYXNlPyBJIGFtIG5vdCBzdXJlIEkgdW5kZXJzdGFuZC4uLg0KDQo8UmFqdT4NCkZvciBp
bml0aWFsIG9mZmVyLCBhIG5ldyBvZmZlciAoQkFTKSBpcyBuZWVkZWQgdG8gc3luYyB1cCB0aGUg
YWRkcmVzc2VlcyBpbiBjYXNlIEJVTkRMRSBpcyBuZWdvdGlhdGVkLiBCdXQsIG1ha2luZyBzdWNo
IGEgbmV3IG9mZmVyIHJlcXVpcmVtZW50IHdoZW4gQlVORExFIGlzIHJlamVjdGVkIGZvciBzdWIt
c2VxdWVudCBvZmZlciBtYWtlcyB0aGUgaW5pdGlhbCBhbmQgc3ViLXNlcXVlbnQgb2ZmZXIgcHJv
Y2VkdXJlcyBpbmNvbnNpc3RlbnQuICANCjwvUmFqdT4NCg0KPiANCj4gPklNSE8sIGhhdmluZyBC
QVMgcmVxdWlyZW1lbnQgb25seSBmb3IgQlVORExFIGNhc2Ugb2YgaW5pdGlhbCBhbmQgc3ViLQ0K
PiBzZXF1ZW50ID5vZmZlcnMgaXMgY2xlYXIgYW5kIHNpbXBsZS4NCj4gDQo+IFdlbGwsIHRoYXQg
aXMgd2hhdCB0aGUgZHJhZnQgY3VycmVudGx5IHNheXMuIFBhdWwncyBzdWdnZXN0aW9uIHJlbW92
ZXMgdGhlDQo+IG5lZWQgZm9yIGEgQkFTIGluIHN1Yi1zZXF1ZW50IG9mZmVycywgd2hpY2ggaXMg
Z29vZC4NCg0KPFJhanU+DQpJTU8sIEkgc3RpbGwgdGhpbmsgY3VycmVudCB0ZXh0IGlzIGNsZWFy
IGFuZCBzaW1wbGUuIFRyeWluZyB0byBvcHRpbWl6ZSBzdWItc2VxdWVudCBvZmZlcnMgYmFzZWQg
b24gcHJpb3IgbmVnb3RpYXRpb24gb2YgQlVORExFIG1heSBjb21wbGljYXRlIGFuZCBhZGRzIGV4
Y2VwdGlvbnMgdG8gdGhlIHJ1bGUgd2hpbGUgb3ZlcmFsbCBnYWlucyBtYXkgYmUgbWluaW1hbC4g
SSBhbSBvayBlaXRoZXIgd2F5IHRob3VnaCwgYnV0IG15IHByZWZlcmVuY2Ugdm90ZSBpcyB0byBr
ZWVwaW5nIGl0IHNpbXBsZSBpbiBzdWNoIHNjZW5hcmlvcy4NCjwvUmFqdT4NCg0KPiANCj4gPkFs
c28sIGlmIHRoZSBvZmZlcmVyIHdhbnRzIG5ldyBtPSBsaW5lIGFzICdidW5kbGUtb25seScgdGhl
biB3b24ndCBpdCBzdGlsbA0KPiBzZXQgcG9ydCB0byA+MD8gQWdhaW4sIElNTywgbWFraW5nIHNl
bWFudGljcyBmb3IgdGhpcyBjb25zaXN0ZW50IHdpdGgNCj4gaW5pdGlhbCBvZmZlciBpcyBhbHNv
IGNsZWFyIGFuZCA+c2ltcGxlLg0KPiANCj4gUG9ydCB6ZXJvIGlzIG5vdCBuZWVkZWQgaW4gc3Vi
LXNlcXVlbnQgb2ZmZXJzLCBiZWNhdXNlIHlvdSBnZXQgdGhlIHNhbWUNCj4gZWZmZWN0IGJ5IGFz
c2lnbmluZyB0aGUgQlVORExFIGFkZHJlc3MgdG8gdGhlIG5ldyBtLSBsaW5lOiBpZiB0aGUgYW5z
d2VyZXINCj4gZG9lcyBub3QgYWNjZXB0IGl0IGludG8gdGhlIEJVTkRMRSBncm91cCwgaXQgTVVT
VCByZWplY3QgaXQuIEFuZCwgaWYgdGhlDQo+IGFuc3dlcmVyIGFjY2VwdHMgdGhlIG5ldyBtLSBs
aW5lIGludG8gdGhlIEJVTkRMRSBncm91cCwgYSBCQVMgb2ZmZXIgaXMgbm90DQo+IG5lZWRlZCAo
YXMgdGhlIEJVTkRMRSBhZGRyZXNzIHdhcyBhc3NpZ25lZCB0byB0aGUgbmV3IG0tIGxpbmUgaW4g
dGhlIG9mZmVyKS4NCg0KPFJhanU+DQpQb3J0IDAgaXMgdGhlbiBhbm90aGVyIGV4Y2VwdGlvbiB0
byB0aGUgcnVsZSB3aGljaCBpcyBkaWZmZXJlbnQgZm9yIGZpcnN0IG9mZmVyIHZzLiBzdWItc2Vx
dWVudCBvZmZlcnMuIEFnYWluLCBteSBwcmVmZXJlbmNlIHdvdWxkIGJlIHRvIGtlZXAgaXQgc2lt
cGxlIGZvciB0aGlzIGFzIHdlbGwuIElmIHdlIGFsbG93IHN1Yi1zZXF1ZW50IG9mZmVycyB0byBi
ZSBkaWZmZXJlbnQgdGhlbiB3ZSBuZWVkIHRvIGRlZmluZSBzdWItc2VxdWVudCBvZmZlcnMgYmVp
bmcgb2ZmZXJzIHRoYXQgb2NjdXIgYWZ0ZXIgQlVORExFIG5lZ290aWF0aW9uIGlzIGRvbmUgYXMg
Zmlyc3QgQlVORExFIGl0c2VsZiBjb3VsZCBiZSBuZWdvdGlhdGVkIGluIGEgc3ViLXNlcXVlbnQg
b2ZmZXJzLg0KDQpSZWxhdGVkIHF1ZXN0aW9ucyBvbiA4LjQuMi4gIEJ1bmRsZSBBZGRyZXNzIFN5
bmNocm9uaXphdGlvbiAoQkFTKS4uLg0KYS4gQ2FuIGEgQkFTIG9mZmVyIGNvbnRhaW4gbmV3IG09
IGxpbmVzPyBJZiB5ZXMsIHdoYXQgYXJlIHRoZSBzZW1hbnRpY3M/DQogICBJIHdvdWxkIGFzc3Vt
ZSBzYW1lIHNlbWFudGljcyBhcyBhIG5vbi1CQVMgb2ZmZXIuIEEgY2xhcmlmaWNhdGlvbg0KICAg
d291bGQgYmUgZ29vZC4NCmIuIENhbiBhbnN3ZXJlciBvcmlnaW5hdGUgYW4gb2ZmZXIgYmVmb3Jl
IHRoZSBCQVMgb2ZmZXIvYW5zd2VyIGlzIGRvbmU/IElmIGFuc3dlcmVyIHNlbmRzIGFub3RoZXIg
b2ZmZXIgYmVmb3JlIEJBUyBvZmZlciB0aGVuIGNhbiBCQVMgc3luYyBiZSBkb25lIGluIHRoYXQg
cm91bmQgb2YgU0RQIG9mZmVyL2Fuc3dlcj8NCg0KPC9SYWp1Pg0KDQo+IA0KPiA+SW5pdGlhbCBv
ZmZlci9hbnN3ZXIgbmVnb3RpYXRpbmcgYSBCVU5ETEUgaXMgbm8gZ3VhcmFudGVlIHRoYXQgc3Vi
LXNlcXVlbnQNCj4gPm9mZmVyL2Fuc3dlcnMgYWxzbyBkbyBzby4gVGhpcyBpcyBiZWNhdXNlIG5l
d2x5IGFkZGVkIG09IGxpbmUncyBkZXN0aW5hdGlvbg0KPiBjb3VsZCBiZSA+ZGlmZmVyZW50IGZy
b20gcHJldmlvdXNseSBuZWdvdGlhdGVkIEJVTkRMRUQgZGVzdGluYXRpb24gYWRkcmVzcw0KPiBh
cyBpdCBtYXkgdHJhdmVyc2UgPmRpZmZlcmVudCBtaWRkbGUgYm94ZXMgKGUuZy4gdmlkZW8gdHJh
bnNjb2RpbmcNCj4gcmVxdWlyZW1lbnRzIGZvciBuZXdseSBhZGRlZCBtPSA+bGluZSkuDQo+IA0K
PiBTdXJlLiBCdXQsIGluIHRoYXQgY2FzZSB0aGUgb2ZmZXJlciBjYW4gc2VuZCBhIG5ldyBvZmZl
ciwgd2hlcmUgdGhlIG5ldyBtLQ0KPiBsaW5lIGlzIG5vdCBhZGRlZCB0byB0aGUgQlVORExFIGdy
b3VwLiBUaGF0IGlzIHRoZSBjYXNlIGFscmVhZHkgdG9kYXksDQo+IGJlY2F1c2UgdGhlIGRyYWZ0
IGFsbG93cyBhc3NpZ25pbmcgdGhlIEJVTkRMRSBhZGRyZXNzIHRvIHRoZSBuZXcgbS0gbGluZS4N
Cg0KPFJhanU+DQpZZXMsIGJ1dCBJTU8gc3RpY2tpbmcgdG8gaW5pdGlhbCBvZmZlci9zZW1hbnRp
Y3MgbWFrZXMgaXQgc2ltcGxlIGFuZCBzdGlsbCBoYW5kbGUgYWxsIG9mZmVyL2Fuc3dlciBzY2Vu
YXJpb3MuIEkgY29uc2lkZXIgdGhlIHByb3Bvc2VkIGNoYW5nZXMgYXMgYW4gb3B0aW1pemF0aW9u
LCB3aGljaCBtYXkgbm90IGhhdmUgbWFueSBiZW5lZml0cyBidXQgaW50cm9kdWNlcyBzb21lIHJp
c2tzIChhcyBhbHJlYWR5IHBvaW50ZWQgYnkgScOxYWtpIEJheiBDYXN0aWxsbyBlYXJsaWVyLCBv
ZiBzZWNvbmQgZ3Vlc3NpbmcgdGhlIHJlYXNvbiBmb3Igb2ZmZXIgcmVqZWN0aW9uKSBhbmQgbW9y
ZSBpbXBsZW1lbnRhdGlvbiBsb2dpYy4NCjwvUmFqdT4NCg0KPiANCj4gPj5SZWdhcmRpbmcgdGhl
IHNlY29uZCBjaGFuZ2UgKGFzc2lnbiB0aGUgbmV3IGFkZHJlc3MgdG8gYWxsIG0tIGxpbmVzKSwg
SQ0KPiA+PnBlcnNvbmFsbHkgc3VwcG9ydCBhbHNvIHRoYXQgb25lLCBhbmQgSSBjYW7igJl0IHNl
ZSBhIHJlYXNvbiBub3QgdG8gZG8NCj4gPj5pdC4gQnV0LCBhZ2FpbiwgZmVlbCBmcmVlIHRvIHBy
b3ZlIG1lIHdyb25nIDopDQo+ID4NCj4gPg0KPiA+V2hlbiBhIG5ldyBCVU5ETEUgYWRkcmVzcyBp
cyBzdWdnZXN0ZWQsIHRoZSBzYW1lIFNEUCBtYXkgY2hhbmdlIHNvbWUgb3RoZXINCj4gPnBhcmFt
ZXRlcnMgKGxpa2UgdmlkZW8gY29kZWNzKS4gU3VjaCBjaGFuZ2VzIG1heSByZXF1aXJlIGRpZmZl
cmVudA0KPiBkZXN0aW5hdGlvbihzKSB0byA+YmUgcHJvdmlkZWQgaW4gU0RQIGFuc3dlciBhbmQg
YXMgYSByZXN1bHQgcHJldmlvdXMgQlVORExFDQo+IGFkZHJlc3MgY2FuJ3QgYmUgdXNlZC4gPlNv
LCBldmVuIGluIHRoaXMgY2FzZSBpdCBpcyBiZXR0ZXIgdG8gYmUgY29uc2lzdGVudA0KPiBhbmQg
aGF2ZSBzYW1lIHJ1bGVzIGFzIGluaXRpYWwgPm9mZmVyL2Fuc3dlciwgaS5lLiB0byBhc3NpZ24g
dW5pcXVlIGFkZHJlc3MNCj4gZm9yIGVhY2ggbT0gbGluZSBhbmQgaWYgQlVORExFIGlzID5uZWdv
dGlhdGVkIHRoZW4gZm9sbG93IHVwIHdpdGggQkFTIG9mZmVyLg0KPiA+DQo+ID5FdmVuIGlmIHRo
ZSBTRFAganVzdCBjaGFuZ2VzIEJVTkRMRSBhZGRyZXNzIG9ubHksIElNSE8sIHRvIHByZXNlcnZl
DQo+IGNvbnNpc3RlbmN5ID5hbmQga2VlcGluZyBpdCBzaW1wbGUgaXQgaXMgYmV0dGVyIHRvIHN0
aWNrIHRvIGluaXRpYWwNCj4gb2ZmZXIvYW5zd2VyIHNlbWFudGljcy4NCj4gDQo+IFBlcmhhcHMg
d2Ugc2hvdWxkIGFsbG93IGJvdGggYWx0ZXJuYXRpdmVzIHRoZW4uIEl0IGVuYWJsZXMgdGhlIGNh
c2Ugb2Ygbm90DQo+IGhhdmluZyB0byBzZW5kIHRoZSBCQVMgb2ZmZXIgaXMgdGhlIG9mZmVyIGlz
IGFjY2VwdGVkLg0KDQo8UmFqdT4NCkkgYW0gb2sgdG8gYWxsb3cgYm90aCBhbHRlcm5hdGl2ZXMu
DQo8L1JhanU+DQoNClRoYW5rcw0KUmFqdQ0K


From nobody Wed Dec 17 11:14:35 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE401A1EFC for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 11:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 QA-d30ETQblK for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 11:14:31 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AA01A1BC4 for <mmusic@ietf.org>; Wed, 17 Dec 2014 11:14:30 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-8f-5491d6149347
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 95.36.04076.416D1945; Wed, 17 Dec 2014 20:14:28 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0195.001; Wed, 17 Dec 2014 20:14:28 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
Thread-Index: AdAZ+3RRvr7r/rTWQnCuYlntTHiCwQAMhfAw
Date: Wed, 17 Dec 2014 19:14:27 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D5FE30FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+Jvja7ItYkhBosuq1tMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGV/2fGAq6LavOHX7DksD41ezLkZODgkBE4mm9VdZIWwxiQv3 1rN1MXJxCAkcYZT4N20CE4SzhFFi6Zm3QA4HB5uAhUT3P22QBhEBdYmve3uYQWqEBboYJQ7c a2GFSPQzSnw8KA1hG0n8a3jFDtLLIqAqca7PHSTMK+Ar0diykwXEFgKyz035BGZzCvhJzNuz mBnEZgQ66PupNUwgNrOAuMStJ/OZIA4VkFiy5zwzhC0q8fLxP6gHlCTWHt7OAlGfL3Hz0z9m iF2CEidnPmGZwCgyC8moWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebAYyZk8QWM7KsYRYtT i4tz042M9FKLMpOLi/Pz9PJSSzYxAmPo4JbfVjsYDz53PMQowMGoxMO74eOEECHWxLLiytxD jNIcLErivAvPzQsWEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwBixegpLz+nfhZJX2lb4uVw9 eG5t4Qm384LPjvRvvGD2ka9a5OqunT+ysy+8DLq0v7qa5UNl7NXZp7+vPHCP20uqL3PTjs27 la8HyJydY7bx0h8N/zbHl2f1XJQk2HIO5Wc0HvjvPPtLFQ8v1zT3QzMzCkvfv60UWV64MmR5 89apRRXRs1e9eO+jxFKckWioxVxUnAgAgWrCQ4ICAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/mDDBdQQp3G9P-bHSHX99T4Nsfec
Subject: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 19:14:34 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D5FE30FESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We currently have the following text in BUNDLE, when the answerer selects t=
he offerer BUNDLE address:

                "If one or more of the criteria are not fulfilled, the answ=
erer MUST select the next
                identification-tag in the identification-tag list, and perf=
orm the same criteria
                check for the "m=3D" line associated with that identificati=
on-tag. If there are no
                more identification-tags in the identification-tag list, th=
e answerer MUST NOT
                create the BUNDLE group."

Now, as the text says, if there is no bundled "m=3D" line address in the of=
fer which fulfills
the criteria for being selected as the offerer BUNDLE address, the answer M=
UST NOT
create the offerer BUNDLE group. So far so good.

However, I think it would be good to have some text on what the answerer DO=
ES with
the "m=3D" lines (in case the answerer doesn't reject the whole offer, that=
 is).

So, I suggested to append the following text to the paragraph:

"Unless the answerer rejects the whole offer, the answerer  MUST apply the =
answerer
procedures for moving an "m=3D" line out of a BUNDLE group to each  bundled=
 "m=3D" line
in the offer when creating the answer."

This basically means that, if the "m=3D" line had a shared address, or a bu=
ndle-only attribute, it will be
rejected. If the "m=3D" line had a unique address, the answerer will assign=
 a unique address in the answer.

Comments?

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D5FE30FESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We currently have the following=
 text in BUNDLE, when the answerer selects the offerer BUNDLE address:<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;If one o=
r more of the criteria are not fulfilled, the answerer MUST select the next=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identification-=
tag in the identification-tag list, and perform the same criteria
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check for the &=
quot;m=3D&quot; line associated with that identification-tag. If there are =
no
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; more identifica=
tion-tags in the identification-tag list, the answerer MUST NOT
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; create the BUND=
LE group.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Now, as the text says, if there=
 is no bundled &#8220;m=3D&#8221; line address in the offer which fulfills
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the criteria for being selected=
 as the offerer BUNDLE address, the answer MUST NOT
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">create the offerer BUNDLE group=
. So far so good.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, I think it would be go=
od to have some text on what the answerer DOES with
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the &#8220;m=3D&#8221; lines (i=
n case the answerer doesn&#8217;t reject the whole offer, that is).<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So, I suggested to append the f=
ollowing text to the paragraph:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">&#=
8220;Unless the answerer rejects the whole offer, the answerer &nbsp;MUST a=
pply the answerer
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">pr=
ocedures for moving an &quot;m=3D&quot; line out of a BUNDLE group to each =
&nbsp;bundled &quot;m=3D&quot; line
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">in=
 the offer when creating the answer.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US"><o=
:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">This basically means that, if t=
he &#8220;m=3D&#8221; line had a shared address, or a bundle-only attribute=
, it will be
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">rejected. If the &#8220;m=3D&#8=
221; line had a unique address, the answerer will assign a unique address i=
n the answer.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Comments?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Christer<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D5FE30FESESSMB209erics_--


From nobody Wed Dec 17 13:11:14 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 628BB1A87EC for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 13:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 zcB4GRR4-ans for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 13:11:10 -0800 (PST)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C37521A7001 for <mmusic@ietf.org>; Wed, 17 Dec 2014 13:11:09 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-12v.sys.comcast.net with comcast id UlAt1p00A2Bo0NV01lB8uE; Wed, 17 Dec 2014 21:11:08 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-05v.sys.comcast.net with comcast id UlB81p00B3Ge9ey01lB8a9; Wed, 17 Dec 2014 21:11:08 +0000
Message-ID: <5491F16C.7090901@alum.mit.edu>
Date: Wed, 17 Dec 2014 16:11:08 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1418850669; bh=3vjrmtMawFelsAhkXhA3f4/mIPrnOUfyAu1XVY0r/gw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=LFSf631NhM+7doJKJLPhB1ycy+V4+2D7cZfJbLskpl3/13r3cIuM2DoFauLKmyedt TTu1AEB9EbXzfGkxVrouX5CE0ZyAIRVFBHlgQmREVGTgckZehigQzf2dQb6v9SWA2r kqHbV+377DzTXzUgmMun6VlcToNbiN9/aPGBYbnVrinM7+cbb0u08fERQ7tJAzx2Yq 2FLrcnyNBG24cVVoF0eJCvdeLsvIkFMYeSx1VnkWp5ZfMFTwzpKw84l8+0a8KInNm3 kkoMewWhEapW3t/tE8fRuX0tQqCYzeNKeMizKWMCpqntcWKMhj+7GWyfxSiH4R6gIA 8sIr4v4lVKdrg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Ib7JsXZUa7iy7M8hDY7zxKVfaL0
Subject: Re: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 21:11:11 -0000

This sounds good to me.

	Thanks,
	Paul

On 12/17/14 2:14 PM, Christer Holmberg wrote:
> Hi,
>
> We currently have the following text in BUNDLE, when the answerer
> selects the offerer BUNDLE address:
>
>                  “If one or more of the criteria are not fulfilled, the
> answerer MUST select the next
>
>                  identification-tag in the identification-tag list, and
> perform the same criteria
>
>                  check for the "m=" line associated with that
> identification-tag. If there are no
>
>                  more identification-tags in the identification-tag
> list, the answerer MUST NOT
>
>                  create the BUNDLE group.”
>
> Now, as the text says, if there is no bundled “m=” line address in the
> offer which fulfills
>
> the criteria for being selected as the offerer BUNDLE address, the
> answer MUST NOT
>
> create the offerer BUNDLE group. So far so good.
>
> However, I think it would be good to have some text on what the answerer
> DOES with
>
> the “m=” lines (in case the answerer doesn’t reject the whole offer,
> that is).
>
> So, I suggested to append the following text to the paragraph:
>
> “Unless the answerer rejects the whole offer, the answerer  MUST apply
> the answerer
>
> procedures for moving an "m=" line out of a BUNDLE group to each
>   bundled "m=" line
>
> in the offer when creating the answer.”
>
> This basically means that, if the “m=” line had a shared address, or a
> bundle-only attribute, it will be
>
> rejected. If the “m=” line had a unique address, the answerer will
> assign a unique address in the answer.
>
> Comments?
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Wed Dec 17 14:16:09 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23A181A8821 for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 14:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 tk3GOc6TJtDC for <mmusic@ietfa.amsl.com>; Wed, 17 Dec 2014 14:16:07 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE80C1A87EB for <mmusic@ietf.org>; Wed, 17 Dec 2014 14:16:00 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id wp4so6505492obc.6 for <mmusic@ietf.org>; Wed, 17 Dec 2014 14:16:00 -0800 (PST)
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:content-transfer-encoding; bh=O1HKoXEZX3WpvXThXAW1S8uLe3Q3AXUbG9nj1nZ6vLo=; b=vayf0ooLKVhdAmkDiXWLj4ussFvX/l6OgeP5eHEM5PPf5sqEw832qeKVoiSH8cYyQk ERELEXeSUbUtIFm/7JefX0UVGPTPwOwdJPwEev/zMPXKM+i3fLvBt+fA+M8KphXNaTZI d067/XBzbHavQea/N21k+2L2z530lPI2ALl970kAWIzVV4Zc/S7ywbwruOvu+JO2+l7m PcAaq+dN3msYBmFMZRH5TSN8Lg5omMZAU95NfOEmdo6Xs4TPilHvDevemopyu3isGJ5S ChhXlcrlzaaoA9UPajGhFk6Xww7U2/M6bxM7fJ8YdnXiGq/YeBo0ivjR3QnUdhoBQo1/ lSVQ==
MIME-Version: 1.0
X-Received: by 10.202.219.198 with SMTP id s189mr16389518oig.72.1418854560204;  Wed, 17 Dec 2014 14:16:00 -0800 (PST)
Received: by 10.202.49.203 with HTTP; Wed, 17 Dec 2014 14:16:00 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
Date: Wed, 17 Dec 2014 14:16:00 -0800
Message-ID: <CABkgnnVFbfGQeeC9DBosmi8J0SVMiexkfffNgvHAc0urVMS3kw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/uca_PR1AwQTJWl3sWskpXxqhkbM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 22:16:09 -0000

On 17 December 2014 at 11:14, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> =E2=80=9CUnless the answerer rejects the whole offer, the answerer  MUST =
apply the
> answerer
>
> procedures for moving an "m=3D" line out of a BUNDLE group to each  bundl=
ed
> "m=3D" line
>
> in the offer when creating the answer.=E2=80=9D

This statement, out of context, reads as "don't negotiate bundle".
Though I guess that it is hard to get all the conditions right.  After
all, bundle-only sections don't get moved out either.


From nobody Thu Dec 18 05:52:50 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27791A8997 for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 05:52:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 C70HoT96tHmJ for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 05:52:47 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C38021A899D for <mmusic@ietf.org>; Thu, 18 Dec 2014 05:52:46 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-59-5492dc2c5879
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 92.FC.04231.C2CD2945; Thu, 18 Dec 2014 14:52:45 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0195.001; Thu, 18 Dec 2014 14:52:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
Thread-Index: AdAZ+3RRvr7r/rTWQnCuYlntTHiCwQAMhfAwAARG8QAAIr/5oA==
Date: Thu, 18 Dec 2014 13:52:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D603518@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se> <CABkgnnVFbfGQeeC9DBosmi8J0SVMiexkfffNgvHAc0urVMS3kw@mail.gmail.com>
In-Reply-To: <CABkgnnVFbfGQeeC9DBosmi8J0SVMiexkfffNgvHAc0urVMS3kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+Jvja7unUkhBsfes1tcO/OP0WLq8scs DkweO2fdZfdYsuQnUwBTFJdNSmpOZllqkb5dAlfGq8O72ApesVcsnvKGpYHxAnsXIyeHhICJ xPXdu9kgbDGJC/fWg9lCAkcYJZavN4ewlzBK3Puf0sXIwcEmYCHR/U8bJCwioCux6OwDdpAw s4C6xNXFQV2MXBzCAjMZJd6vus8E4ogIzGKUeDB9OgtEg5PE+k9rwfayCKhKrHx0FCzOK+Ar cfnnBRaQBiGBG4wSOybsZAJJcAoESqw4vYAZxGYEOu77qTVgcWYBcYlbT+YzQRwtILFkz3lm CFtU4uXjf6wQtpJE45InrBDXaUqs36UP0aooMaX7ITvEXkGJkzOfsExgFJuFZOoshI5ZSDpm IelYwMiyilG0OLW4ODfdyFgvtSgzubg4P08vL7VkEyMwdg5u+a27g3H1a8dDjAIcjEo8vIbO k0KEWBPLiitzDzFKc7AoifMuOjcvWEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAPjvICfG2fV GDbunCB/8y3jvE6tmx8PbDPfxZ0gl1m+Q3S+A5/hizk6127IMh5Zbfz8a/y7dfWJwv07GmYf PG8WGWz+Z6OseoJO+arr3pH5fgtb9vSXTGjcemGjQUTwAe3lMw/N+HDXpNl5t9kstb1ORYam EvunOocafn32/6ht0fY13aFqz7SOKbEUZyQaajEXFScCAGVm3ux+AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ysmHnjj50IzFDMqTx11z0sKm7-k
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 13:52:48 -0000

SGkgTWFydGluLA0KDQo+PiDigJxVbmxlc3MgdGhlIGFuc3dlcmVyIHJlamVjdHMgdGhlIHdob2xl
IG9mZmVyLCB0aGUgYW5zd2VyZXIgIE1VU1QgYXBwbHkgDQo+PiB0aGUgYW5zd2VyZXIgcHJvY2Vk
dXJlcyBmb3IgbW92aW5nIGFuICJtPSIgbGluZSBvdXQgb2YgYSBCVU5ETEUgZ3JvdXAgdG8gZWFj
aCAgDQo+PiBidW5kbGVkICJtPSIgbGluZSBpbiB0aGUgb2ZmZXIgd2hlbiBjcmVhdGluZyB0aGUg
YW5zd2VyLuKAnQ0KPg0KPiBUaGlzIHN0YXRlbWVudCwgb3V0IG9mIGNvbnRleHQsIHJlYWRzIGFz
ICJkb24ndCBuZWdvdGlhdGUgYnVuZGxlIi4NCj4gVGhvdWdoIEkgZ3Vlc3MgdGhhdCBpdCBpcyBo
YXJkIHRvIGdldCBhbGwgdGhlIGNvbmRpdGlvbnMgcmlnaHQuICBBZnRlciBhbGwsIGJ1bmRsZS1v
bmx5IHNlY3Rpb25zIGRvbid0IGdldCBtb3ZlZCBvdXQgZWl0aGVyLg0KDQpJIGd1ZXNzIEkgc2hv
dWxkIGhhdmUgY29waWVkIG1vcmUgdGV4dCBpbnRvIHRoZSBvcmlnaW5hbCBlLW1haWwuDQoNClRo
aXMgaXMgcmVsYXRlZCB0byB0aGUgY2FzZSB3aGVyZSB0aGUgb2ZmZXJlciBoYXMgb2ZmZXJlZCBC
VU5ETEUsIGJ1dCBub25lIG9mIHRoZSBidW5kbGVkIG0tIGxpbmUgYWRkcmVzc2VzIGZ1bGZpbCB0
aGUgY3JpdGVyaWEgZm9yIGJlaW5nIHNlbGVjdGVkIGFzIHRoZSBvZmZlcmVyIEJVTkRMRSBhZGRy
ZXNzIGJ5IHRoZSBhbnN3ZXJlci4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg==


From nobody Thu Dec 18 07:53:04 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAEDD1A1A68 for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 07:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level: 
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 BinGaLUVuqEE for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 07:52:46 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93AF61A90DB for <mmusic@ietf.org>; Thu, 18 Dec 2014 07:52:46 -0800 (PST)
Received: from us70uusmtp4.zam.alcatel-lucent.com (unknown [135.5.2.66]) by Websense Email Security Gateway with ESMTPS id D40321B278507; Thu, 18 Dec 2014 15:52:40 +0000 (GMT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id sBIFqbY9027153 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Dec 2014 10:52:42 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.03.0195.001; Thu, 18 Dec 2014 10:52:37 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
Thread-Index: AdAZ+3RRvr7r/rTWQnCuYlntTHiCwQAMhfAwACsdwoA=
Date: Thu, 18 Dec 2014 15:52:36 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E66C70E@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: multipart/alternative; boundary="_000_E1FE4C082A89A246A11D7F32A95A17828E66C70EUS70UWXCHMBA02z_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qFLNRaQY-sSJVQku5JIQAVvRAdE
Subject: Re: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 15:52:53 -0000

--_000_E1FE4C082A89A246A11D7F32A95A17828E66C70EUS70UWXCHMBA02z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have no objections.
Please see a minor comment inline.

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: Wednesday, December 17, 2014 1:14 PM


Hi,

We currently have the following text in BUNDLE, when the answerer selects t=
he offerer BUNDLE address:

                "If one or more of the criteria are not fulfilled, the answ=
erer MUST select the next
                identification-tag in the identification-tag list, and perf=
orm the same criteria
                check for the "m=3D" line associated with that identificati=
on-tag. If there are no
                more identification-tags in the identification-tag list, th=
e answerer MUST NOT
                create the BUNDLE group."

Now, as the text says, if there is no bundled "m=3D" line address in the of=
fer which fulfills
the criteria for being selected as the offerer BUNDLE address, the answer M=
UST NOT
create the offerer BUNDLE group. So far so good.

However, I think it would be good to have some text on what the answerer DO=
ES with
the "m=3D" lines (in case the answerer doesn't reject the whole offer, that=
 is).

So, I suggested to append the following text to the paragraph:

"Unless the answerer rejects the whole offer, the answerer  MUST apply the =
answerer
procedures for moving an "m=3D" line out of a BUNDLE group to each  bundled=
 "m=3D" line
in the offer when creating the answer."
<Raju>
I believe ".. moving an "m=3D" line out of a BUNDLE group..." also includes=
 rejecting the m=3D line by setting port to 0. Do we need some text to clar=
ify this?
</Raju>

BR
Raju

--_000_E1FE4C082A89A246A11D7F32A95A17828E66C70EUS70UWXCHMBA02z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have no objections. =
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see a minor com=
ment inline.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mmusic [=
mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> Wednesday, December 17, 2014 1:14 PM<br>
<br>
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">We currently have the following text in BUNDLE, when=
 the answerer selects the offerer BUNDLE address:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;If one or more of the criteri=
a are not fulfilled, the answerer MUST select the next<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identification-tag in the identifica=
tion-tag list, and perform the same criteria
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check for the &quot;m=3D&quot; line =
associated with that identification-tag. If there are no
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; more identification-tags in the iden=
tification-tag list, the answerer MUST NOT
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; create the BUNDLE group.&#8221;<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Now, as the text says, if there is no bundled &#8220=
;m=3D&#8221; line address in the offer which fulfills
<o:p></o:p></p>
<p class=3D"MsoNormal">the criteria for being selected as the offerer BUNDL=
E address, the answer MUST NOT
<o:p></o:p></p>
<p class=3D"MsoNormal">create the offerer BUNDLE group. So far so good.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">However, I think it would be good to have some text =
on what the answerer DOES with
<o:p></o:p></p>
<p class=3D"MsoNormal">the &#8220;m=3D&#8221; lines (in case the answerer d=
oesn&#8217;t reject the whole offer, that is).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, I suggested to append the following text to the =
paragraph:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">&#8220;Unless the answere=
r rejects the whole offer, the answerer &nbsp;MUST apply the answerer
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">procedures for moving an =
&quot;m=3D&quot; line out of a BUNDLE group to each &nbsp;bundled &quot;m=
=3D&quot; line
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">in the offer when creatin=
g the answer.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&lt;Raju&gt;<o:p=
></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">I believe &#8220=
;.. </span></i></b>moving an &quot;m=3D&quot; line out of a BUNDLE group&#8=
230;&#8221;
<b><i><span style=3D"color:#1F497D">also includes rejecting the m=3D line b=
y setting port to 0. Do we need some text to clarify this?<o:p></o:p></span=
></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">&lt;/Raju&gt;</s=
pan></i></b><span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">BR<o:p></o:p></s=
pan></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">Raju</span></i><=
/b><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_E1FE4C082A89A246A11D7F32A95A17828E66C70EUS70UWXCHMBA02z_--


From nobody Thu Dec 18 09:36:49 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA2C1A9103 for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 09:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 xMq8dbmKukBJ for <mmusic@ietfa.amsl.com>; Thu, 18 Dec 2014 09:36:46 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 971391A9100 for <mmusic@ietf.org>; Thu, 18 Dec 2014 09:36:45 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-b6-549310abd01e
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 59.60.24955.BA013945; Thu, 18 Dec 2014 18:36:43 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0195.001; Thu, 18 Dec 2014 18:36:43 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
Thread-Index: AdAZ+3RRvr7r/rTWQnCuYlntTHiCwQAMhfAwACsdwoAAA7aoMA==
Date: Thu, 18 Dec 2014 17:36:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D604F34@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D5F98D8@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D5FE30F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E66C70E@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E66C70E@US70UWXCHMBA02.zam.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D604F34ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyM+Jvje5qgckhBkvPaFtMXf6YxaJh4xVW ByaP1md7WT2WLPnJFMAUxWWTkpqTWZZapG+XwJWxtvkcS8FW94qdl/vZGxjX2XUxcnJICJhI zJjylwXCFpO4cG89WxcjF4eQwBFGiW03bzFDOEsYJf5+2cHexcjBwSZgIdH9TxukQUQgR+L3 rfesIDXCAn2MEsePtrFBJPoZJT4elIawnSRaf85iBbFZBFQl1tw/D2bzCvhKHNn3lBViwRNG iUtzmhlBEpwCsRLf9q0CK2IEOun7qTVMIDazgLjErSfzmSBOFZBYsuc8M4QtKvHy8T9WCFtJ onHJE1aQQ5kF8iXmb1WH2CUocXLmE5YJjCKzkEyahVA1C0kVRImOxILdn9ggbG2JZQtfM8PY Zw48ZkIWX8DIvopRtDi1OCk33chYL7UoM7m4OD9PLy+1ZBMjMK4ObvmtuoPx8hvHQ4wCHIxK PLwGzpNChFgTy4orcw8xSnOwKInzLjw3L1hIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDo8V2 dY9E1ZPLLebUnrz7iNt92z0WqVLNjfabHy2P+yw1/YKs3VKVPTIWxeuqvyhVa0W9cqmxyF4f YiQZX35yf9WJBJXdK0KaxabmmZ3g65169fTcRQqKZ4TWzN86pbV81z39rYE5dqvbVm6Sf3zX r8av/ujh+QJTtY5xtwef0Qh79+KWf/+Pb0osxRmJhlrMRcWJAPhDePCMAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/otbCDcP89RdXbvEbJYoWfska7OY
Subject: Re: [MMUSIC] BUNDLE: How to process bundled m- lines when no address fulfills the criteria for being selected as the offerer BUNDLE address?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 17:36:48 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D604F34ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We currently have the following text in BUNDLE, when the answerer selects t=
he offerer BUNDLE address:

                "If one or more of the criteria are not fulfilled, the answ=
erer MUST select the next
                identification-tag in the identification-tag list, and perf=
orm the same criteria
                check for the "m=3D" line associated with that identificati=
on-tag. If there are no
                more identification-tags in the identification-tag list, th=
e answerer MUST NOT
                create the BUNDLE group."

Now, as the text says, if there is no bundled "m=3D" line address in the of=
fer which fulfills
the criteria for being selected as the offerer BUNDLE address, the answer M=
UST NOT
create the offerer BUNDLE group. So far so good.

However, I think it would be good to have some text on what the answerer DO=
ES with
the "m=3D" lines (in case the answerer doesn't reject the whole offer, that=
 is).

So, I suggested to append the following text to the paragraph:

"Unless the answerer rejects the whole offer, the answerer  MUST apply the =
answerer
procedures for moving an "m=3D" line out of a BUNDLE group to each  bundled=
 "m=3D" line
in the offer when creating the answer."
<Raju>
I believe ".. moving an "m=3D" line out of a BUNDLE group..." also includes=
 rejecting the m=3D line by setting port to 0. Do we need some text to clar=
ify this?
</Raju>

The section on moving an "m=3D" line out of a BUNDLE group describes the ca=
se when the "m=3D" line must be rejected.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D604F34ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D;mso-fareast-language:EN=
-US"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-US">We currently have the following=
 text in BUNDLE, when the answerer selects the offerer BUNDLE address:<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#8220;If one o=
r more of the criteria are not fulfilled, the answerer MUST select the next=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identification-=
tag in the identification-tag list, and perform the same criteria
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; check for the &=
quot;m=3D&quot; line associated with that identification-tag. If there are =
no
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; more identifica=
tion-tags in the identification-tag list, the answerer MUST NOT
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; create the BUND=
LE group.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Now, as the text says, if there=
 is no bundled &#8220;m=3D&#8221; line address in the offer which fulfills
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the criteria for being selected=
 as the offerer BUNDLE address, the answer MUST NOT
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">create the offerer BUNDLE group=
. So far so good.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However, I think it would be go=
od to have some text on what the answerer DOES with
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">the &#8220;m=3D&#8221; lines (i=
n case the answerer doesn&#8217;t reject the whole offer, that is).<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">So, I suggested to append the f=
ollowing text to the paragraph:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">&#=
8220;Unless the answerer rejects the whole offer, the answerer &nbsp;MUST a=
pply the answerer
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">pr=
ocedures for moving an &quot;m=3D&quot; line out of a BUNDLE group to each =
&nbsp;bundled &quot;m=3D&quot; line
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:36.0pt"><span lang=3D"EN-US">in=
 the offer when creating the answer.&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"color:#1F497D">&=
lt;Raju&gt;<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"color:#1F497D">I=
 believe &#8220;..
</span></i></b><span lang=3D"EN-US">moving an &quot;m=3D&quot; line out of =
a BUNDLE group&#8230;&#8221; <b>
<i><span style=3D"color:#1F497D">also includes rejecting the m=3D line by s=
etting port to 0. Do we need some text to clarify this?<o:p></o:p></span></=
i></b></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:5.5pt"><b><i><span lang=3D"EN-U=
S" style=3D"color:#1F497D">&lt;/Raju&gt;</span></i></b><b><i><span lang=3D"=
EN-US"><o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span><=
/i></b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:red">The sect=
ion on moving an &#8220;m=3D&#8221; line out of a BUNDLE group describes th=
e case when the &#8220;m=3D&#8221; line must be rejected.<o:p></o:p></span>=
</b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:red"><o:p>&nb=
sp;</o:p></span></b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:red">Regards,=
<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:red"><o:p>&nb=
sp;</o:p></span></b></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"color:red">Christer=
<o:p></o:p></span></b></p>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D604F34ESESSMB209erics_--


From nobody Fri Dec 19 02:40:12 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE001A8783; Fri, 19 Dec 2014 02:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 j6aq_jm-iKmW; Fri, 19 Dec 2014 02:40:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0E011A6F84; Fri, 19 Dec 2014 02:40:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.8.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141219104006.11895.68642.idtracker@ietfa.amsl.com>
Date: Fri, 19 Dec 2014 02:40:06 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7jGzuysai0OrKOh5re59Isb3kmE
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sctp-sdp-10.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 10:40:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Salvatore Loreto
                          Gonzalo Camarillo
	Filename        : draft-ietf-mmusic-sctp-sdp-10.txt
	Pages           : 19
	Date            : 2014-12-19

Abstract:
   SCTP (Stream Control Transmission Protocol) is a transport protocol
   used to establish associations between two endpoints.

   This specification describes how to describe SCTP associations using
   the Session Description Protocol (SDP), and defines the following new
   SDP Media Description protocol identifiers (proto values):'SCTP',
   'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.

   The specification also describes how to use the new proto values
   together with the SDP Offer/Answer mechanism in order to negotiate
   and establish SCTP associations, and how to indicate the SCTP
   application usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sctp-sdp/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sctp-sdp-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Dec 19 02:42:47 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B7D1A87AF for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 02:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 wmqlygo8dki9 for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 02:42:43 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A2641A8778 for <mmusic@ietf.org>; Fri, 19 Dec 2014 02:42:42 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-17-54940120357b
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id D8.18.29772.02104945; Fri, 19 Dec 2014 11:42:40 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0195.001; Fri, 19 Dec 2014 11:42:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: SCTP-SDP-10
Thread-Index: AdAbeDBGXMaZOlLtTnuxmB64Tzqu/Q==
Date: Fri, 19 Dec 2014 10:42:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D60BCD8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D60BCD8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+Jvja4C45QQg8VXBS3+7U2ymLr8MYsD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlTHxwU/Wgq0SFecn/WJtYDwt2sXIySEhYCLx 8FczC4QtJnHh3no2EFtI4AijxOXGtC5GLiB7CaPEjRlrGbsYOTjYBCwkuv9pg9SICKhLfN3b wwxiMws4Spy9tZ0JxBYGit8/uoIZokZHYvua20wQtp7E//cv2UFsFgFViRkfn4Pt4hXwlVjT eB4szgh0w/dTa5ggZopL3HoynwniNgGJJXvOM0PYohIvH/9jhbAVJa5OXw5Vny9xrPMgE8RM QYmTM5+wTGAUnoVk1CwkZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjKLFqcVJ uelGRnqpRZnJxcX5eXp5qSWbGIGxc3DLb4MdjC+fOx5iFOBgVOLh3TBlcogQa2JZcWXuIUZp DhYlcd6F5+YFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamDc+m3RIpMTT1l76phu5krUPu42 31R3O0v3VcHkfPFVkvVPtl2oXtrHGn9U/1/N63QthZg7X9zis1kS/wqwRploSpl4xD2WX3aq 9+OxmS+YuafN+T/p0s/JRpVevXnLmPlsTSy2rp61r3i1RIZpbZ3m8iZ9SdEVy4Oc3k715DvG t4Xh3evpNXZKLMUZiYZazEXFiQBWxNtOfgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/LHw374IFba2JevWdPX9VDecM2S0
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: [MMUSIC] Draft new version: SCTP-SDP-10
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 10:42:44 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D60BCD8ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I've submitted a new version (-10) of draft-ietf-mmusic-sctp-sdp.

There are currently no open issues in the draft.

Some examples will still have to be added, but other than that the authors =
now think that the draft is in such shape that we should start moving towar=
ds WGLC.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D60BCD8ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I&#8217;ve submitted a new version (-10) of draft-ie=
tf-mmusic-sctp-sdp.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are currently no open issues in the draft.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Some examples will still have to be added, but other=
 than that the authors now think that the draft is in such shape that we sh=
ould start moving towards WGLC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D60BCD8ESESSMB209erics_--


From nobody Fri Dec 19 05:02:36 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860431A8AD1; Fri, 19 Dec 2014 05:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 Y45Dxg0q-LfU; Fri, 19 Dec 2014 05:02:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BDB1A9140; Fri, 19 Dec 2014 05:02:28 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141219130228.23142.64399.idtracker@ietfa.amsl.com>
Date: Fri, 19 Dec 2014 05:02:28 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/1Jdom9Glp0l_8UMR42umvx2qJak
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-14.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 13:02:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-14.txt
	Pages           : 48
	Date            : 2014-12-19

Abstract:
   This specification defines a new Session Description Protocol (SDP)
   Grouping Framework extension, 'BUNDLE'.  The extension can be used
   with the SDP Offer/Answer mechanism to negotiate the usage of a
   single address:port combination (BUNDLE address) for receiving media,
   referred to as bundled media, associated with multiple SDP media
   descriptions ("m=" lines).

   To assist endpoints in negotiating the use of bundle this
   specification defines a new SDP attribute, 'bundle-only', which can
   be used to request that specific media is only used if bundled.  This
   specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264 to
   allow an answerer to assign a non-zero port value to an "m=" line in
   an SDP answer, even if the "m=" line in the associated SDP offer
   contained a zero port value.

   There are multiple ways to correlate the bundled RTP packets with the
   appropriate media descriptions.  This specification defines a new
   RTCP source description (SDES) item and a new RTP header extension
   that provides an additional way to do this correlation by using them
   to carry a value that associates the RTP/RTCP packets with a specific
   media description.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-bundle-negotiation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-14

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-bundle-negotiation-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Dec 19 05:05:17 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD5C1A914A for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 05:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 vAR9ZxDfWtlb for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 05:04:55 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52BFD1AC3F5 for <mmusic@ietf.org>; Fri, 19 Dec 2014 05:04:55 -0800 (PST)
X-AuditID: c1b4fb30-f79d66d00000744c-71-549422755b09
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 89.55.29772.57224945; Fri, 19 Dec 2014 14:04:53 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0195.001; Fri, 19 Dec 2014 14:04:52 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: BUNDLE-14
Thread-Index: AdAbjFtetfDP6QSgQxCeekDl6XYOjQ==
Date: Fri, 19 Dec 2014 13:04:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D60C2ED@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D60C2EDESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyM+JvjW6p0pQQgxcTFCz+7U2ymLr8MYsD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlXHuzlaWggNSFcsmdzE2MK4S72Lk4JAQMJG4 9a6qi5ETyBSTuHBvPVsXIxeHkMARRonPZ1ZAOUsYJVqnrmUCaWATsJDo/qcN0iAioC7xdW8P M4jNLOAocfbWdiYQW1hAVWLHr2UsEDVaEv2b5oO1igjoSaw/mgcSZgEqOd/yDayVV8BXYv+S PnYQmxHohu+n1jBBjBSXuPVkPhPEbQISS/acZ4awRSVePv7HCmErSlydvhxsPLNAvsSV31YQ IwUlTs58wjKBUXgWkkmzEKpmIamCKNGRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKFqcW J+WmGxnppRZlJhcX5+fp5aWWbGIERs3BLb8NdjC+fO54iFGAg1GJh3fDlMkhQqyJZcWVuYcY pTlYlMR5F56bFywkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qBMVvDb4LarjcL2p0ss8Ok3Pel tBYGHJLlLGc4Iypvq1bWs5fnql3ghXcCRgWnhWvVF8iLG31+u8ZsW9W/KZtmGUifYzV+lq8b x9xYXxoy9XbQvlUhX0M0dB8d0U3QL7c9ZiN+Zg3n8pIekbi4jGsXpxbenyZs1fbP65bGnYbG 105uPd851biUWIozEg21mIuKEwEwKFbsewIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/0b-W0jWRKEj5oea4SLTjl3co8Tg
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: [MMUSIC] Draft new version: BUNDLE-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 13:04:59 -0000
X-List-Received-Date: Fri, 19 Dec 2014 13:04:59 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D60C2EDESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I've submitted a new version (-14) of BUNDLE.

The main technical change is for suggesting a new offerer BUNDLE address, w=
here it is now stated that the new suggested address can be assigned to eac=
h bundled "m=3D" line.

In addition, I added procedure text regarding the case where no bundled "m=
=3D" line fulfills the criteria for being selected as the offerer BUNDLE ad=
dress by the answerer.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D60C2EDESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I&#8217;ve submitted a new version (-14) of BUNDLE.<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The main technical change is for suggesting a new of=
ferer BUNDLE address, where it is now stated that the new suggested address=
 can be assigned to each bundled &#8220;m=3D&#8221; line.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In addition, I added procedure text regarding the ca=
se where no bundled &#8220;m=3D&#8221; line fulfills the criteria for being=
 selected as the offerer BUNDLE address by the answerer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D60C2EDESESSMB209erics_--


From nobody Fri Dec 19 08:45:33 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF7D1A89E1 for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 08:45:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 i9wRS1mTbGAX for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 08:45:28 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A14F1A89BB for <mmusic@ietf.org>; Fri, 19 Dec 2014 08:45:27 -0800 (PST)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-06v.sys.comcast.net with comcast id VUlF1p0042Bo0NV01UlT0b; Fri, 19 Dec 2014 16:45:27 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-05v.sys.comcast.net with comcast id VUlS1p00R3Ge9ey01UlTzM; Fri, 19 Dec 2014 16:45:27 +0000
Message-ID: <54945626.8030501@alum.mit.edu>
Date: Fri, 19 Dec 2014 11:45:26 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D60C2ED@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D60C2ED@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419007527; bh=T+URoDvyMC95PrbhfPqEq+24S9YG59HRGjuPPed8x4o=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=RbMkjsOu+KmGh1daWsDSnjOmueBLXDCTMa57Cui4ET6NJpSQa/WWBhMzBbgS8Lpuw jpyJjeeqksbAtpHTjLdOgwR5JXtWFEio5lkzC2IIKKgqS++Z7DdFBm/FEM1MPryqLK 9YyPEPmPAT7nUuarcv6/5Kw8pyjYqtUe8vcV0UmvVsvQ8Dj3DzEazuFOoRenurL8bU td6OzfH9OoFz/bPbpfhnDZBfKPyBAv7bCGivjlLzejspgFibQyZPZuooUYh1bn4T7/ 6h3M+nz2TZjPITZp1b/vG01po7dJubvyhURxpPBJ429Z7SUVOazC8ncMwj5N0lR0kz 0C8xRxhSL8nbw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/djo2j1NlCLXb-4HhJX1Zx3NqT4A
Subject: Re: [MMUSIC] Draft new version: BUNDLE-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 16:45:31 -0000

This change works for me, with the following minor issue:

In 8.5.2, the following:

    In addition, the offerer MUST indicate that the offerer suggests
    address as the new offerer BUNDLE address [Section 8.2.2]

doesn't read quite right. IIUC, the following would be clearer:

    In addition, the offerer MUST indicate that the offerer suggested
    address is the new offerer BUNDLE address [Section 8.2.2]

	Thanks,
	Paul

On 12/19/14 8:04 AM, Christer Holmberg wrote:
> Hi,
>
> I’ve submitted a new version (-14) of BUNDLE.
>
> The main technical change is for suggesting a new offerer BUNDLE
> address, where it is now stated that the new suggested address can be
> assigned to each bundled “m=” line.
>
> In addition, I added procedure text regarding the case where no bundled
> “m=” line fulfills the criteria for being selected as the offerer BUNDLE
> address by the answerer.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Fri Dec 19 09:06:06 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 973ED1A8A4A for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 09:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_14=0.6, SPF_SOFTFAIL=0.665] 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 fveHlga5VQik for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 09:05:58 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64FDC1A8A60 for <mmusic@ietf.org>; Fri, 19 Dec 2014 09:05:50 -0800 (PST)
Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-06v.sys.comcast.net with comcast id VV5l1p00D2N9P4d01V5pYb; Fri, 19 Dec 2014 17:05:49 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-13v.sys.comcast.net with comcast id VV5o1p00i3Ge9ey01V5pAk; Fri, 19 Dec 2014 17:05:49 +0000
Message-ID: <54945AEC.3070706@alum.mit.edu>
Date: Fri, 19 Dec 2014 12:05:48 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D60BCD8@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D60BCD8@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419008749; bh=BShpKqB12ho4DIBvmcF6231r25JiGIRbVDzUn6YtK4A=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=c3UAeM5tCu4xLpIcf1LGU4nvswApR8tnAFPU5WcyzAzAs4a8WMCoRt6OighlfeJ/Q LrlzAux16XulUY657l/zdQwKTY7QtQvyo63paSBhJZuKtwX1x1BhdS0cITEBVfTkRU dQgXjlg1RFe2RaQfEmasJKyq+34gj6sRxaACcZXZgQyabtcjd6IDmkwdhlXiNETZIt aW7tK/ycfs0fplQefySxJzb5KCwFONSryICDE4oh5ziQ6cDHlnpY8ot2CQFZ1cA5KD GGf+J5LSYYIXH4rsyqSK2E+CvrNlaaCQR9c0xmI2eU3DMNtlJFSzr/sxmwbrdQR0e+ oYJMBZBq36ixg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/EJWMXs1ZEZhceqoDF8tYs0JvStc
Subject: Re: [MMUSIC] Draft new version: SCTP-SDP-10
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 17:05:59 -0000

On 12/19/14 5:42 AM, Christer Holmberg wrote:
> Hi,
>
> I’ve submitted a new version (-10) of draft-ietf-mmusic-sctp-sdp.
>
> There are currently no open issues in the draft.
>
> Some examples will still have to be added, but other than that the
> authors now think that the draft is in such shape that we should start
> moving towards WGLC.

One major issue with this new version:

Now that the new a=max-message-size attribute has been defined in 
section 6, section 7 now is quite broken. It is no longer used for 
defining max message size. So pretty much all of what is in section 7 
can now be removed. The one exception is the default value of 64K, which 
should be moved into section 6.

It may make sense to retain a section 7, but change it to simply note 
that a=fmtp provides a mechanism for specifying attributes that are 
specific to a particular association-usage, and that the detailed syntax 
of that must be defined as part of the definition of an association-usage.

	Thanks,
	Paul


From nobody Fri Dec 19 12:17:21 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 764121AC39C for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 12:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 xlIOZMj0vhlQ for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 12:17:18 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA3681AC398 for <mmusic@ietf.org>; Fri, 19 Dec 2014 12:17:17 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-80-549487cb2316
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 0B.8B.04076.BC784945; Fri, 19 Dec 2014 21:17:16 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0195.001; Fri, 19 Dec 2014 21:17:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: BUNDLE-14 - Paul's comment
Thread-Index: AdAbyNbXRhP6ZF1vSBmSIpVOYTUS5Q==
Date: Fri, 19 Dec 2014 20:17:15 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D60E367@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvje6Z9ikhBos72CymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj++xTzAXtrBVPn89mbGD8ztzFyMkhIWAi MfnSTSYIW0ziwr31bF2MXBxCAkcYJVrPrIVyljBKHL1+g7GLkYODTcBCovufNkiDiICvxLPH t9lAbGEBZ4nmpm52iLiLxI+Lh8HKRQT0JObtLgMJswioSqz+s5QNJMwL1LrhNFgnI9Da76fW gJ3ALCAucevJfKhzBCSW7DkPdaaoxMvH/1ghbCWJRbc/Q9XrSCzY/YkNwtaWWLbwNVg9r4Cg xMmZT1gmMArPQjJ2FpKWWUhaZiFpWcDIsopRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMOQP bvlttYPx4HPHQ4wCHIxKPLwbpkwOEWJNLCuuzD3EKM3BoiTOu/DcvGAhgfTEktTs1NSC1KL4 otKc1OJDjEwcnFINjEsNRBptp9tsfzO/KOP/U717k6faBDFsV46Z1dt2YT7PWha9un/8j48I V+wzWmxgf/fT2cyVOyWqZU9Uez1i0cn4abKW/ZW31u6oJ/dvvhY60Rp4NHvpn8nxPccO/XmX cK0natt0hfOzf7Gmnb46d8fZb4HNKUsEbxptlJm+6OLHOeHxYW6vJ11UYinOSDTUYi4qTgQA xqponFoCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/TKN973319IIH7yvkOztYQ2zK6Vs
Subject: Re: [MMUSIC] Draft new version: BUNDLE-14 - Paul's comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 20:17:19 -0000

Hi,

>This change works for me, with the following minor issue:
>
>In 8.5.2, the following:
>
>    In addition, the offerer MUST indicate that the offerer suggests
>    address as the new offerer BUNDLE address [Section 8.2.2]
>
>doesn't read quite right. IIUC, the following would be clearer:
>
>    In addition, the offerer MUST indicate that the offerer suggested
>    address is the new offerer BUNDLE address [Section 8.2.2]

I think we could make it even simpler, by saying:

	"In addition, the offerer MUST indicate that the address is the
	new suggested offerer BUNDLE address [Section 8.2.2]."

Regards,

Christer


From nobody Fri Dec 19 15:09:17 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 925551A87B8 for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 15:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 5A_5MQgfzk8o for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 15:09:09 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 734DC1A90A5 for <mmusic@ietf.org>; Fri, 19 Dec 2014 15:09:08 -0800 (PST)
X-AuditID: c1b4fb3a-f79116d000000fec-b8-5494b012846f
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 12.16.04076.210B4945; Sat, 20 Dec 2014 00:09:06 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0195.001; Sat, 20 Dec 2014 00:09:06 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: SCTP-SDP-10 - Paul's comments
Thread-Index: AdAb4NioQW3X3ddwTNSbA/eAVd6gIg==
Date: Fri, 19 Dec 2014 23:09:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D60E9B2@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUyM+Jvja7QhikhBmsWaltMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfG/2czWAtucFQcOnCJvYHxGVsXIyeHhICJ xPRf95ggbDGJC/fWA8W5OIQEjjBKrDp5iRXCWcIo8fjURcYuRg4ONgELie5/2iANIgK+Es8e 3wYbJCzgJtHauoYdIu4ucaqvmRHC1pM4seo2C4jNIqAq0XF0OVg9L1Dv0mOzmEFsRqDF30+t ATuCWUBc4taT+VAHCUgs2XOeGcIWlXj5+B8rhK0ksfbwdhaIeh2JBbs/sUHY2hLLFr5mhpgv KHFy5hOWCYzCs5CMnYWkZRaSlllIWhYwsqxiFC1OLS7OTTcy0kstykwuLs7P08tLLdnECAz7 g1t+W+1gPPjc8RCjAAejEg/vhimTQ4RYE8uKK3MPMUpzsCiJ8y48Ny9YSCA9sSQ1OzW1ILUo vqg0J7X4ECMTB6dUA2PGz4yttQql4QfOH5y0fkm2Y9SL/QkCcz0fXtr0ZNfUwJ/XnRZ+Nevq iEgVYnO+zrD/cHbmk+RyHotpPmySfzuyN7mYPbl17VJBXM+3lnVd+dNNhCYsNE/faKJc2T/1 f8ZK6a4uocTW2s0e3s8vX/jwbNPNpGSLlqd7D16PykpNY1tS8TM0OkSJpTgj0VCLuag4EQDq CnkNXAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/XK7taN2fD97fLOXLjFnICZzUYn4
Subject: Re: [MMUSIC] Draft new version: SCTP-SDP-10 - Paul's comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 23:09:14 -0000

Hi,

>> I've submitted a new version (-10) of draft-ietf-mmusic-sctp-sdp.
>>
>> There are currently no open issues in the draft.
>>
>> Some examples will still have to be added, but other than that the=20
>> authors now think that the draft is in such shape that we should start=20
>> moving towards WGLC.
>
> One major issue with this new version:
>
> Now that the new a=3Dmax-message-size attribute has been defined in secti=
on 6, section 7 now is=20
> quite broken. It is no longer used for defining max message size.=20

Correct. I was supposed to remove that...

> So pretty much all of what is in section 7 can now be removed. The one ex=
ception is the default value of 64K, which should be=20
> moved into section 6.

Yes.

> It may make sense to retain a section 7, but change it to simply note tha=
t a=3Dfmtp provides a=20
> mechanism for specifying attributes that are specific to a particular ass=
ociation-usage, and=20
> that the detailed syntax of that must be defined as part of the definitio=
n of an association-usage.

Yes.

Thanks!

Regards,

Christer


From nobody Fri Dec 19 15:52:00 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5481A9168; Fri, 19 Dec 2014 15:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 G2nenBW0U6No; Fri, 19 Dec 2014 15:51:36 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A3C1A90F0; Fri, 19 Dec 2014 15:51:36 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.9.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141219235136.30889.92547.idtracker@ietfa.amsl.com>
Date: Fri, 19 Dec 2014 15:51:36 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/mDrcCCMP0LmzMMlBKeIOgB0P4yY
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sctp-sdp-11.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 23:51:39 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : Stream Control Transmission Protocol (SCTP)-Based Media Transport in the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Salvatore Loreto
                          Gonzalo Camarillo
	Filename        : draft-ietf-mmusic-sctp-sdp-11.txt
	Pages           : 20
	Date            : 2014-12-19

Abstract:
   SCTP (Stream Control Transmission Protocol) is a transport protocol
   used to establish associations between two endpoints.

   This specification describes how to describe SCTP associations using
   the Session Description Protocol (SDP), and defines the following new
   SDP Media Description protocol identifiers (proto values):'SCTP',
   'SCTP/DTLS', 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.

   The specification also describes how to use the new proto values
   together with the SDP Offer/Answer mechanism in order to negotiate
   and establish SCTP associations, and how to indicate the SCTP
   application usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sctp-sdp/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sctp-sdp-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Dec 19 15:53:06 2014
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E2D1A90AA for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 15:53:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 07zV8wxso8j4 for <mmusic@ietfa.amsl.com>; Fri, 19 Dec 2014 15:53:02 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2401A8A3B for <mmusic@ietf.org>; Fri, 19 Dec 2014 15:53:02 -0800 (PST)
X-AuditID: c1b4fb2d-f79fc6d000001087-d8-5494ba5c992f
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 04.2A.04231.C5AB4945; Sat, 20 Dec 2014 00:53:00 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.175]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0195.001; Sat, 20 Dec 2014 00:52:59 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: SCTP-SDP-11
Thread-Index: AdAb5toJ4o9v+/MaTd2XA4Ig5QQ1rQ==
Date: Fri, 19 Dec 2014 23:52:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D60EBA2@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D60EBA2ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+JvjW7MrikhBv83yVj825tkMXX5YxYH Jo8lS34yeXy5/JktgCmKyyYlNSezLLVI3y6BK2PRlUnMBZ/FKqau2s/YwLhYpIuRk0NCwERi 1aIDbBC2mMSFe+uBbC4OIYEjjBKt5x+yQzhLGCU2HPnB2MXIwcEmYCHR/U8bpEFEQF3i694e ZhCbWcBR4uyt7UwgJcJA8fcrAyFKdCR+tzeyQth6Eo+nzWIBsVkEVCWaLk0Fa+UV8JW4sayd CcRmBLrh+6k1TBAjxSVuPZnPBHGbgMSSPeeZIWxRiZeP/7FC2EoSaw9vZ4Goz5d48PcbI8RM QYmTM5+wTGAUnoVk1CwkZbOQlEHEdSQW7P7EBmFrSyxb+JoZxj5z4DETsvgCRvZVjKLFqcXF uelGxnqpRZnJxcX5eXp5qSWbGIGxc3DLb90djKtfOx5iFOBgVOLh3TBlcogQa2JZcWXuIUZp DhYlcd5F5+YFCwmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamAMEdC1n18baNxxMvdR2dtvb555 7vzyyuD07TBWzq+PDxR91ONfJTaFYf+qG8svcNevuvSmyJ5TVSWTv7pum4nmLT+GM4cn9nlr +JlLXq89cFGueuLeSVI9jR9bVH4dW3doU9MrLzu3u2tMDfcpM3Ev1mv/efDgVHaGiAy9fUw3 Dt26t+H8gtS7SizFGYmGWsxFxYkAyPV0834CAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/1SHdGgxHyU7yE0Nlvv90o7luLgQ
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: [MMUSIC] Draft new version: SCTP-SDP-11
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 23:53:04 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D60EBA2ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on Paul's comment on version-10, I fixed that and submitted version-1=
1.

I also noted that the max-message-size was missing from the IANA considerat=
ions, so I added it there.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D60EBA2ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Based on Paul&#8217;s comment on version-10, I fixed=
 that and submitted version-11.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I also noted that the max-message-size was missing f=
rom the IANA considerations, so I added it there.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D60EBA2ESESSMB209erics_--


From nobody Sat Dec 20 13:18:39 2014
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534301AC3A8 for <mmusic@ietfa.amsl.com>; Sat, 20 Dec 2014 13:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 DnJUtG2HS5u3 for <mmusic@ietfa.amsl.com>; Sat, 20 Dec 2014 13:18:22 -0800 (PST)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4820B1A9075 for <mmusic@ietf.org>; Sat, 20 Dec 2014 13:13:18 -0800 (PST)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by resqmta-ch2-04v.sys.comcast.net with comcast id VxCM1p00D2LrikM01xDHqh; Sat, 20 Dec 2014 21:13:17 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-12v.sys.comcast.net with comcast id VxDG1p00N3Ge9ey01xDGro; Sat, 20 Dec 2014 21:13:17 +0000
Message-ID: <5495E66C.1090903@alum.mit.edu>
Date: Sat, 20 Dec 2014 16:13:16 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D60EBA2@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D60EBA2@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419109997; bh=me1JzeLl6mWVslfa3fCEfxUkMj94Mi4JWo7+fAWB9bI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=rgaTsASw0n24EcF8HsgTMIZtYOmjOCXeLOg5d10IYjhxzo1BTYnCZHhttfZgEsakl F4sPotkqZZQHeqKFOdP/Xb1ubmL+zRJUY0VyVren8No5Ql0sQoxsQ1JMW9AXKayi1u 11Eqi90sfeVK9GSNMgzkER7a9A9swa+lxQJFxs8S3SglPLoAfe6OkyhOwfDiPcCoxD LeISkg0rOT3QbFOSV3K0yI0IEZsVidLfTYX0dz7tuMFdJA94ufrsNuClQcPwN1/o7G splWitfOD67W+kLUyhnAjc9uYY1QdT50MQhYe22HuQNqVwrHK/koFop/AvrZfAzFIb Ynw3EIuXnwYkA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/SqzqrJATirE6sGV87r95FtAI9ts
Subject: Re: [MMUSIC] Draft new version: SCTP-SDP-11
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Dec 2014 21:18:25 -0000

WFM

On 12/19/14 6:52 PM, Christer Holmberg wrote:
> Hi,
>
> Based on Paul’s comment on version-10, I fixed that and submitted
> version-11.
>
> I also noted that the max-message-size was missing from the IANA
> considerations, so I added it there.
>
> Regards,
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Tue Dec 30 05:46:00 2014
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEF51ACE9D; Sat, 27 Dec 2014 21:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 GkxlbTcMqTLt; Sat, 27 Dec 2014 21:24:19 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE6F11A90BA; Sat, 27 Dec 2014 21:24:18 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id y13so15178216pdi.17; Sat, 27 Dec 2014 21:24:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=KvlbBvufcLLvvSX4iTl47dUcOgP18DCuPoXfLLHidPU=; b=JS7XF1UZH+dFZZlT4IVkF6Md8HJ97ltJ414Oza0o+upiNGoV5F9bwHiew1tYHkJd/d ioNC1Kvt+KI5wrT+O8W0IlLES7CX0vcu4S8RpxXVeuPqz0MD4j2egMK0e4/vsKioXbEf wF7HnktHhfIEIhYdy+BIdeCSg1y3P8ZvO8hhLsiWnzwYh/jB6Usn0yG8ki6N2S9omf3l GWsGiihDNhE4BhcB9GBdR3AZxJJCdNQl08u0etwvcj5r1QILFjtW86ssmUyn4PKw0+x3 fhoYDgloFmcfTNT1JQZLvB+acoQ50fljNzbvvdU65XGzGCeiiqowQufIqfRM3ZZHrakg nodg==
MIME-Version: 1.0
X-Received: by 10.70.22.227 with SMTP id h3mr80954255pdf.160.1419744258051; Sat, 27 Dec 2014 21:24:18 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sat, 27 Dec 2014 21:24:18 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sat, 27 Dec 2014 21:24:18 -0800 (PST)
Date: Sun, 28 Dec 2014 00:24:18 -0500
Message-ID: <CACFvNHWZdjmYYNu5DQnr53mzwjekU8wxwh+3yGRSTdgvN0Sm=w@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=047d7b6da18a2c5322050b3ff8e7
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/IfTlzHee2floXlXCKJEbPBGYotk
X-Mailman-Approved-At: Tue, 30 Dec 2014 05:45:55 -0800
Subject: [MMUSIC] Question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2014 05:24:20 -0000

--047d7b6da18a2c5322050b3ff8e7
Content-Type: text/plain; charset=UTF-8

I hope everyone had a great holiday!

I also hope the New Year is also as splendid for all of the members of the
IETF as it has ever been.

I am sorry to 'bother' again however while waiting for my responses on my
previous summary email 'On the following Errata' I ran across something I
had a question on which may need to be addressed further.

Rfc 2326 explicitly states that seeking can be disabled by not including
the end information in the range header.

What if I want to have the end but I don't want to allow seeking?

E.g. my clip is 10 minutes and I have already been playing for 3 and there
are 7 remaining; why can't I convey that and not allow seeking?

Obviously I can just return a BadRequest when a seek is performed or just
an OKAY to pretend like it's honored; but how can I convey in a standards
compliant manner that the stream is not seekable BEFORE the client attempts
the seek operation when also indicating the current and end times of the
media in question?

Thanks in advance and best wishes again!

Sincerely,
Julius Friedman

--047d7b6da18a2c5322050b3ff8e7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I hope everyone had a great holiday!</p>
<p dir=3D"ltr">I also hope the New Year is also as splendid for all of the =
members of the IETF as it has ever been. </p>
<p dir=3D"ltr">I am sorry to &#39;bother&#39; again however while waiting f=
or my responses on my previous summary email &#39;On the following Errata&#=
39; I ran across something I had a question on which may need to be address=
ed further. </p>
<p dir=3D"ltr">Rfc 2326 explicitly states that seeking can be disabled by n=
ot including the end information in the range header. </p>
<p dir=3D"ltr">What if I want to have the end but I don&#39;t want to allow=
 seeking? </p>
<p dir=3D"ltr">E.g. my clip is 10 minutes and I have already been playing f=
or 3 and there are 7 remaining; why can&#39;t I convey that and not allow s=
eeking? </p>
<p dir=3D"ltr">Obviously I can just return a BadRequest when a seek is perf=
ormed or just an OKAY to pretend like it&#39;s honored; but how can I conve=
y in a standards compliant manner that the stream is not seekable BEFORE th=
e client attempts the seek operation when also indicating the current and e=
nd times of the media in question?</p>
<p dir=3D"ltr">Thanks in advance and best wishes again! </p>
<p dir=3D"ltr">Sincerely, <br>
Julius Friedman</p>

--047d7b6da18a2c5322050b3ff8e7--


From nobody Tue Dec 30 05:46:02 2014
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0041AC3D5; Sun, 28 Dec 2014 16:43:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 0aqdxsON2p9q; Sun, 28 Dec 2014 16:43:43 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D58A1AC3C5; Sun, 28 Dec 2014 16:43:43 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id eu11so16377710pac.11; Sun, 28 Dec 2014 16:43:42 -0800 (PST)
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 :content-type; bh=yJ3Ux3xWmBHCMqxTpFNsG2GNC8fUeinpo1yeQOg16Ag=; b=Vc3lHPP/lFDTK9fLW8TQHgOvzPuvSuOS4xtv35nE1wsduu5ef0plbyRzJAT73SINio WZQ9DJ78CwlcFHu3Kh7rqTxwuXAavImVG+6fJ/U2ruWNnW2YIuo/EVudqHMpDk/qmYj6 EP5ncjWfd8dzH43xBYQfBo1fPE0+O16oG2Nj/SyhW1kJrOCWNtINOoHzwzlDnQXfHPLZ Q05/5BdYpSdIBNee3WC1NIPpowgJAdWGjbI5lGarO2/J8MKkG+bJNwN148TiKyY+biEu wPoFMUNKfbucu2a/7Ah3FXKylnsklLiNceoCIyT2S23DcFSXcLaKRifAeZ0tXFclKeV8 5vtQ==
MIME-Version: 1.0
X-Received: by 10.70.140.130 with SMTP id rg2mr86563969pdb.49.1419813822521; Sun, 28 Dec 2014 16:43:42 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sun, 28 Dec 2014 16:43:42 -0800 (PST)
In-Reply-To: <874msfcna5.fsf@hobgoblin.ariadne.com>
References: <CACFvNHWZdjmYYNu5DQnr53mzwjekU8wxwh+3yGRSTdgvN0Sm=w@mail.gmail.com> <874msfcna5.fsf@hobgoblin.ariadne.com>
Date: Sun, 28 Dec 2014 19:43:42 -0500
Message-ID: <CACFvNHXhFQe2CEKsv4q637SoGa-vKuhztN+a1ywK1ewU_Sa6KA@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>, avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=001a1134c7c889e8cd050b502aeb
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/F3ciPFdFCFzZIFRaeg_2lh_8QQE
X-Mailman-Approved-At: Tue, 30 Dec 2014 05:45:55 -0800
Subject: Re: [MMUSIC] [AVTCORE] Question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 00:43:46 -0000

--001a1134c7c889e8cd050b502aeb
Content-Type: text/plain; charset=UTF-8

Hello Dale, (et al)

I would like to address your response:

"In any case, why would we want to prevent seeking on a stored media
object?  I can see why if the media is an un-stored media stream, but in
that case, the software likely doesn't know the total length that the
media will have."

I will justify how "likely" this is as follows:

1) A Live 10 minute `media` which has been playing for 3 minutes, leaving
me 7 minutes in play but unable to seek.
   a) If the stream was stored or recorded this obviously wouldn't be an
issue

2) I have a server which requires authorization to seek but not to play.

3) I am a client and I have started playing and 'PAUSE' is not supported

4) I am a server re-streaming from a server where "Range" is not supported

"Perhaps referring to the mailing list discussion for this RFC would
reveal the answer."

Which mailing list is that? 'mmusic' they have also been addressed, several
times. I never get a response from them.

In any other case I hope all is well and that I haven't been marked as spam
or WORSE that there is something wrong with the list and my messages are
just not being received.

Anyway , thank you for your prompt response!

Sincerely,
Julius

On Sun, Dec 28, 2014 at 7:28 PM, Dale R. Worley <worley@ariadne.com> wrote:

> Julius Friedman <juliusfriedman@gmail.com> writes:
> > Rfc 2326 explicitly states that seeking can be disabled by not including
> > the end information in the range header.
> >
> > What if I want to have the end but I don't want to allow seeking?
> >
> > E.g. my clip is 10 minutes and I have already been playing for 3 and
> there
> > are 7 remaining; why can't I convey that and not allow seeking?
>
> I'm no expert in RTSP, but reading the RFC, it appears that the server
> indicates if seeking is allowed by the inclusion of the end-time:
>
>     D.2.1 Basic Playback
>
>      Client implementations may use the presence of length information
>      to determine if the clip is seekable, and visibly disable seeking
>      features for clips for which the length information is unavailable.
>
> Exactly why the server cannot indicate the total media length without
> implicitly stating the media is seekable, I don't know.  Perhaps it's
> because any such media is theoretically seekable, since it must already
> be instantiated as a stored data object.  Or perhaps it is because if
> seeking is not implemented, the user interface is expected to not
> display the "slider bar", and so there is no way to tell the user how
> much time remains in the media:
>
>      Client implementations may use the presence of length information
>      to determine if the clip is seekable, and visibly disable seeking
>      features for clips for which the length information is unavailable.
>      A common use of the presentation length is to implement a "slider
>      bar" which serves as both a progress indicator and a timeline
>      positioning tool.
>
> Perhaps referring to the mailing list discussion for this RFC would
> reveal the answer.
>
> In any case, why would we want to prevent seeking on a stored media
> object?  I can see why if the media is an un-stored media stream, but in
> that case, the software likely doesn't know the total length that the
> media will have.
>
> Dale
>

--001a1134c7c889e8cd050b502aeb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello Dale, (et al)</div><div><br></div><div>I would =
like to address your response:</div><div><br></div>&quot;<span style=3D"fon=
t-size:12.8000001907349px">In any case, why would we want to prevent seekin=
g on a stored media</span><br style=3D"font-size:12.8000001907349px"><span =
style=3D"font-size:12.8000001907349px">object?=C2=A0 I can see why if the m=
edia is an un-stored media stream, but in</span><br style=3D"font-size:12.8=
000001907349px"><span style=3D"font-size:12.8000001907349px">that case, the=
 software likely doesn&#39;t know the total length that the</span><br style=
=3D"font-size:12.8000001907349px"><span style=3D"font-size:12.8000001907349=
px">media will have.&quot;</span><div><span style=3D"font-size:12.800000190=
7349px"><br></span></div><div><span style=3D"font-size:12.8000001907349px">=
I will justify how &quot;likely&quot; this is as follows:<br></span></div><=
div><span style=3D"font-size:12.8000001907349px"><br></span></div><div><spa=
n style=3D"font-size:12.8000001907349px">1) A Live 10 minute `media` which =
has been playing for 3 minutes, leaving me 7 minutes in play but unable to =
seek.</span></div><div><span style=3D"font-size:12.8000001907349px">=C2=A0 =
=C2=A0a) If the stream was stored or=C2=A0recorded=C2=A0this=C2=A0obviously=
=C2=A0wouldn&#39;t be an issue</span></div><div><span style=3D"font-size:12=
.8000001907349px"><br></span></div><div><span style=3D"font-size:12.8000001=
907349px">2) I have a server which requires authorization to seek but not t=
o play.</span></div><div><br></div><div><span style=3D"font-size:12.8000001=
907349px">3)=C2=A0</span><span style=3D"font-size:12.8000001907349px">I am =
a client and I have started playing and &#39;PAUSE&#39; is not supported</s=
pan></div><div><span style=3D"font-size:12.8000001907349px"><br></span></di=
v><div><span style=3D"font-size:12.8000001907349px">4)=C2=A0</span><span st=
yle=3D"font-size:12.8000001907349px">I am a server re-streaming from a serv=
er where &quot;Range&quot; is not supported</span></div><div><span style=3D=
"font-size:12.8000001907349px"><br></span></div><div><span style=3D"font-si=
ze:12.8000001907349px">&quot;Perhaps referring to the mailing list discussi=
on for this RFC would</span><br style=3D"font-size:12.8000001907349px"><spa=
n style=3D"font-size:12.8000001907349px">reveal the answer.&quot;</span><br=
></div><div><span style=3D"font-size:12.8000001907349px"><br></span></div><=
div><span style=3D"font-size:12.8000001907349px">Which mailing list is that=
? &#39;mmusic&#39; they have also been addressed, several times. I never ge=
t a response from them.</span></div><div><span style=3D"font-size:12.800000=
1907349px"><br></span></div><div><span style=3D"font-size:12.8000001907349p=
x">In any other case I hope all is well and that I haven&#39;t been marked =
as spam or WORSE that there is something wrong with the list and my message=
s are just not being received.</span></div><div><span style=3D"font-size:12=
.8000001907349px"><br></span></div><div><span style=3D"font-size:12.8000001=
907349px">Anyway , thank you for your prompt response!</span></div><div><sp=
an style=3D"font-size:12.8000001907349px"><br></span></div><div><span style=
=3D"font-size:12.8000001907349px">Sincerely,</span></div><div><span style=
=3D"font-size:12.8000001907349px">Julius</span></div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Sun, Dec 28, 2014 at 7:28 PM, =
Dale R. Worley <span dir=3D"ltr">&lt;<a href=3D"mailto:worley@ariadne.com" =
target=3D"_blank">worley@ariadne.com</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"><span class=3D"">Julius Friedman &lt;<a href=3D"mailto:ju=
liusfriedman@gmail.com">juliusfriedman@gmail.com</a>&gt; writes:<br>
&gt; Rfc 2326 explicitly states that seeking can be disabled by not includi=
ng<br>
&gt; the end information in the range header.<br>
&gt;<br>
&gt; What if I want to have the end but I don&#39;t want to allow seeking?<=
br>
&gt;<br>
&gt; E.g. my clip is 10 minutes and I have already been playing for 3 and t=
here<br>
&gt; are 7 remaining; why can&#39;t I convey that and not allow seeking?<br=
>
<br>
</span>I&#39;m no expert in RTSP, but reading the RFC, it appears that the =
server<br>
indicates if seeking is allowed by the inclusion of the end-time:<br>
<br>
=C2=A0 =C2=A0 D.2.1 Basic Playback<br>
<br>
=C2=A0 =C2=A0 =C2=A0Client implementations may use the presence of length i=
nformation<br>
=C2=A0 =C2=A0 =C2=A0to determine if the clip is seekable, and visibly disab=
le seeking<br>
=C2=A0 =C2=A0 =C2=A0features for clips for which the length information is =
unavailable.<br>
<br>
Exactly why the server cannot indicate the total media length without<br>
implicitly stating the media is seekable, I don&#39;t know.=C2=A0 Perhaps i=
t&#39;s<br>
because any such media is theoretically seekable, since it must already<br>
be instantiated as a stored data object.=C2=A0 Or perhaps it is because if<=
br>
seeking is not implemented, the user interface is expected to not<br>
display the &quot;slider bar&quot;, and so there is no way to tell the user=
 how<br>
much time remains in the media:<br>
<br>
=C2=A0 =C2=A0 =C2=A0Client implementations may use the presence of length i=
nformation<br>
=C2=A0 =C2=A0 =C2=A0to determine if the clip is seekable, and visibly disab=
le seeking<br>
=C2=A0 =C2=A0 =C2=A0features for clips for which the length information is =
unavailable.<br>
=C2=A0 =C2=A0 =C2=A0A common use of the presentation length is to implement=
 a &quot;slider<br>
=C2=A0 =C2=A0 =C2=A0bar&quot; which serves as both a progress indicator and=
 a timeline<br>
=C2=A0 =C2=A0 =C2=A0positioning tool.<br>
<br>
Perhaps referring to the mailing list discussion for this RFC would<br>
reveal the answer.<br>
<br>
In any case, why would we want to prevent seeking on a stored media<br>
object?=C2=A0 I can see why if the media is an un-stored media stream, but =
in<br>
that case, the software likely doesn&#39;t know the total length that the<b=
r>
media will have.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Dale<br>
</font></span></blockquote></div><br></div>

--001a1134c7c889e8cd050b502aeb--


From nobody Tue Dec 30 05:46:03 2014
Return-Path: <juliusfriedman@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A48141ACD6A; Sun, 28 Dec 2014 20:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, SPF_PASS=-0.001, WEIRD_PORT=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 bZJV2u1WnE13; Sun, 28 Dec 2014 20:48:19 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F68E1ACD67; Sun, 28 Dec 2014 20:48:19 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ey11so16739671pad.10; Sun, 28 Dec 2014 20:48:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=iMQ5n4fa5ZenWcmkWdqVyRNFoh0YQjvrEZPZbhyT5CI=; b=DXQnquLbtxlhzduiqx3IapiU6tJ6MNRUX08tdy2qjkHHV0s4pcvGDvl0yGyvNIFYP0 YiQ/y19BRlvxa2DpfeptgOfd1/aB/l2xh0LxvNTdwlPQSOchz9qknSsOLE9wabuuD21H XoF4zmAIPZDdNj5qAbWfC6+xFTWXrp4aLe3lR0ADvBacFTA4Kd529jIfTvnzJw27iUiW IAc5six9Wa6JHWivrKmOr/m8gmuPQAvlaETw7mJBggZ8czg3wCmRT2nacm1tCBLwx+3J UmZxNIiZxP+f+Zyy9YPds+HRdYL+tOwCyv7tH6ixrAYV7tU6Bnr5D5Uc5gihma8nh/Q1 Q9EA==
MIME-Version: 1.0
X-Received: by 10.68.211.193 with SMTP id ne1mr87802279pbc.49.1419828498691; Sun, 28 Dec 2014 20:48:18 -0800 (PST)
Received: by 10.70.117.99 with HTTP; Sun, 28 Dec 2014 20:48:18 -0800 (PST)
Date: Sun, 28 Dec 2014 23:48:18 -0500
Message-ID: <CACFvNHUz=VfYj+nz_WXbEvmzGvmNUiocCM1doPoPNJH+Qsemow@mail.gmail.com>
From: Julius Friedman <juliusfriedman@gmail.com>
To: avt@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary=e89a8fb208e84e7d0c050b5395e1
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/lkD9WkGqchUIr78vPiAG4RfYCR0
X-Mailman-Approved-At: Tue, 30 Dec 2014 05:45:55 -0800
Subject: [MMUSIC] Possible Erratta in RFC2326 relating to 'source' parameter.
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 04:48:21 -0000

--e89a8fb208e84e7d0c050b5395e1
Content-Type: text/plain; charset=UTF-8

RFC2326 Specifies in Section [12.39 Transport]

 source:
          If the source address for the stream is different than can be
          derived from the RTSP endpoint address (the server in playback
          or the client in recording), the source MAY be specified.

Then directly below in the same section

 Transport           =    "Transport" ":"
                            1\#transport-spec
   transport-spec      =    transport-protocol/profile[/lower-transport]
                            *parameter
   transport-protocol  =    "RTP"
   profile             =    "AVP"
   lower-transport     =    "TCP" | "UDP"
   parameter           =    ( "unicast" | "multicast" )
                       |    ";" "destination" [ "=" address ]
                       |    ";" "interleaved" "=" channel [ "-" channel ]
                       |    ";" "append"
                       |    ";" "ttl" "=" ttl
                       |    ";" "layers" "=" 1*DIGIT
                       |    ";" "port" "=" port [ "-" port ]
                       |    ";" "client_port" "=" port [ "-" port ]
                       |    ";" "server_port" "=" port [ "-" port ]
                       |    ";" "ssrc" "=" ssrc
                       |    ";" "mode" = <"> 1\#mode <">
   ttl                 =    1*3(DIGIT)
   port                =    1*5(DIGIT)
   ssrc                =    8*8(HEX)
   channel             =    1*3(DIGIT)
   address             =    host
   mode                =    <"> *Method <"> | Method


Since 'source' is not listed I don't know the syntax, I assumed it to
be an "IPAddress" however the text sates "address" so I imagine if I
found a 'source=1.2.3.4:1554' that would be valid however I want to
make sure since there isn't any syntax specified in the RFC.

Also I would wonder is there any restriction on specifying a port or
address range also ? e.g. 'source=1.2.3.4/321202/2'

I believe there was a similar issue with Rtp-Info headers which was
fixed in 'biz' however this among other issues were not addressed and
I am wondering if any other updates will be made to this RFC before
2.0 Draft is finalized.

Hopefully this won't have to be added to my list of `issues` but
unless I am missing something I will also have to file errata for
this.

Thanks in advance!

--e89a8fb208e84e7d0c050b5395e1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">RFC2326 Specifies in Section [<span style=3D"color:rgb(0,0=
,0);white-space:pre-wrap">12.39 Transport]</span><div><span style=3D"color:=
rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><pre style=3D"color:=
rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"> source:
          If the source address for the stream is different than can be
          derived from the RTSP endpoint address (the server in playback
          or the client in recording), the source MAY be specified.
</pre></div><div>Then directly below in the same section</div><div><br></di=
v><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-=
wrap"> Transport           =3D    &quot;Transport&quot; &quot;:&quot;
                            1\#transport-spec
   transport-spec      =3D    transport-protocol/profile[/lower-transport]
                            *parameter
   transport-protocol  =3D    &quot;RTP&quot;
   profile             =3D    &quot;AVP&quot;
   lower-transport     =3D    &quot;TCP&quot; | &quot;UDP&quot;
   parameter           =3D    ( &quot;unicast&quot; | &quot;multicast&quot;=
 )
                       |    &quot;;&quot; &quot;destination&quot; [ &quot;=
=3D&quot; address ]
                       |    &quot;;&quot; &quot;interleaved&quot; &quot;=3D=
&quot; channel [ &quot;-&quot; channel ]
                       |    &quot;;&quot; &quot;append&quot;
                       |    &quot;;&quot; &quot;ttl&quot; &quot;=3D&quot; t=
tl
                       |    &quot;;&quot; &quot;layers&quot; &quot;=3D&quot=
; 1*DIGIT
                       |    &quot;;&quot; &quot;port&quot; &quot;=3D&quot; =
port [ &quot;-&quot; port ]
                       |    &quot;;&quot; &quot;client_port&quot; &quot;=3D=
&quot; port [ &quot;-&quot; port ]
                       |    &quot;;&quot; &quot;server_port&quot; &quot;=3D=
&quot; port [ &quot;-&quot; port ]
                       |    &quot;;&quot; &quot;ssrc&quot; &quot;=3D&quot; =
ssrc
                       |    &quot;;&quot; &quot;mode&quot; =3D &lt;&quot;&g=
t; 1\#mode &lt;&quot;&gt;
   ttl                 =3D    1*3(DIGIT)
   port                =3D    1*5(DIGIT)
   ssrc                =3D    8*8(HEX)
   channel             =3D    1*3(DIGIT)
   address             =3D    host
   mode                =3D    &lt;&quot;&gt; *Method &lt;&quot;&gt; | Metho=
d</pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-=
wrap"><br></pre><pre style=3D"word-wrap:break-word"><font face=3D"arial, sa=
ns-serif"><span style=3D"white-space:normal">Since &#39;source&#39; is not =
listed I don&#39;t know the syntax, I assumed it to be an &quot;IPAddress&q=
uot; however the text sates &quot;address&quot; so I imagine if I found a &=
#39;source=3D<a href=3D"http://1.2.3.4:1554">1.2.3.4:1554</a>&#39; that wou=
ld be valid however I want to make sure since there isn&#39;t any syntax sp=
ecified in the RFC.=C2=A0</span></font></pre><pre style=3D"word-wrap:break-=
word"><font face=3D"arial, sans-serif"><span style=3D"white-space:normal">A=
lso I would wonder is there any restriction on specifying a port or address=
 range also ? e.g. &#39;source=3D<a href=3D"http://1.2.3.4/321202/2">1.2.3.=
4/321202/2</a>&#39;</span></font></pre><pre style=3D"word-wrap:break-word">=
<font face=3D"arial, sans-serif"><span style=3D"white-space:normal">I belie=
ve there was a similar issue with Rtp-Info headers which was fixed in &#39;=
biz&#39; however this among other issues were not addressed and I am wonder=
ing if any other updates will be made to this RFC before 2.0 Draft is final=
ized.</span></font></pre><pre style=3D"word-wrap:break-word"><font face=3D"=
arial, sans-serif"><span style=3D"white-space:normal">Hopefully this won&#3=
9;t have to be added to my list of `issues` but unless I am missing somethi=
ng I will also have to file=C2=A0errata=C2=A0for this.</span></font></pre><=
pre style=3D"word-wrap:break-word"><span style=3D"white-space:normal;font-f=
amily:arial,sans-serif">Thanks in advance!</span></pre></div></div>

--e89a8fb208e84e7d0c050b5395e1--


From nobody Tue Dec 30 05:47:56 2014
Return-Path: <worley@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B451AC3C6 for <mmusic@ietfa.amsl.com>; Sun, 28 Dec 2014 16:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level: 
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 uhvgQHd3vxOX for <mmusic@ietfa.amsl.com>; Sun, 28 Dec 2014 16:30:28 -0800 (PST)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E59E91AC3C5 for <mmusic@ietf.org>; Sun, 28 Dec 2014 16:30:27 -0800 (PST)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-02v.sys.comcast.net with comcast id ZCWT1p0012Qkjl901CWTBo; Mon, 29 Dec 2014 00:30:27 +0000
Received: from hobgoblin.ariadne.com ([173.75.213.57]) by resomta-ch2-15v.sys.comcast.net with comcast id ZCTw1p00N1Es2At01CU2b7; Mon, 29 Dec 2014 00:28:22 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id sBT0SJ3O026123; Sun, 28 Dec 2014 19:28:19 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sBT0SII8026120; Sun, 28 Dec 2014 19:28:18 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHWZdjmYYNu5DQnr53mzwjekU8wxwh+3yGRSTdgvN0Sm=w@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 28 Dec 2014 19:28:18 -0500
Message-ID: <874msfcna5.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419813027; bh=6ayPN+7fABe5J/tnd92g3UQxDYojIiQuLNTuU58cSEo=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Vn1VVrFkQL1FS++zM6XsGZ+1UyhNDWV7ShAZ5AnqP3AxxqMHSDUPHWNAhOJbk26ug gJTNb1q8HusA213RzfA1kOOZnPJT+hWt29vBJcnwYVSJI4BWqBmik0HbL8Ev3eXQv3 dASq8kHhdvgdipxPjOCBafATySu6hJtFsvDFOkVhagHA9+yLRB//srv+6z5KCM4wCH 2s4e8o2Sqjl/61cgxHTUdSLf0HUqO4vxMGs5FPM/2ClWzA05fsmyPbP4PzZol4ymRA hP4INuZ6gL13SEiyL1PxW5oEeo6pUDo3dhL8Tzb1HT9EPmINH7saZACCCoSFteGIvL 3CO/KD/bJLvyw==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/p1fIVpc-p93YemtIMYEm5gX4EuU
X-Mailman-Approved-At: Tue, 30 Dec 2014 05:47:53 -0800
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [MMUSIC] [AVTCORE] Question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Dec 2014 00:30:29 -0000

Julius Friedman <juliusfriedman@gmail.com> writes:
> Rfc 2326 explicitly states that seeking can be disabled by not including
> the end information in the range header.
>
> What if I want to have the end but I don't want to allow seeking?
>
> E.g. my clip is 10 minutes and I have already been playing for 3 and there
> are 7 remaining; why can't I convey that and not allow seeking?

I'm no expert in RTSP, but reading the RFC, it appears that the server
indicates if seeking is allowed by the inclusion of the end-time:

    D.2.1 Basic Playback

     Client implementations may use the presence of length information
     to determine if the clip is seekable, and visibly disable seeking
     features for clips for which the length information is unavailable.

Exactly why the server cannot indicate the total media length without
implicitly stating the media is seekable, I don't know.  Perhaps it's
because any such media is theoretically seekable, since it must already
be instantiated as a stored data object.  Or perhaps it is because if
seeking is not implemented, the user interface is expected to not
display the "slider bar", and so there is no way to tell the user how
much time remains in the media:

     Client implementations may use the presence of length information
     to determine if the clip is seekable, and visibly disable seeking
     features for clips for which the length information is unavailable.
     A common use of the presentation length is to implement a "slider
     bar" which serves as both a progress indicator and a timeline
     positioning tool.

Perhaps referring to the mailing list discussion for this RFC would
reveal the answer.

In any case, why would we want to prevent seeking on a stored media
object?  I can see why if the media is an un-stored media stream, but in
that case, the software likely doesn't know the total length that the
media will have.

Dale

