Re: [MMUSIC] Not fixing a=rtcp and rtcp-mux exclusive

Roman Shpount <roman@telurix.com> Tue, 02 February 2016 14:54 UTC

Return-Path: <roman@telurix.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 30CFB1B2BDB for <mmusic@ietfa.amsl.com>; Tue, 2 Feb 2016 06:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level:
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_14=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 14Jh2wSIXiCV for <mmusic@ietfa.amsl.com>; Tue, 2 Feb 2016 06:54:07 -0800 (PST)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02F7D1B2BA1 for <mmusic@ietf.org>; Tue, 2 Feb 2016 06:54:06 -0800 (PST)
Received: by mail-io0-x232.google.com with SMTP id 9so19677286iom.1 for <mmusic@ietf.org>; Tue, 02 Feb 2016 06:54:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=61n1rTOQAdXv6eeHPFo5aQPM3i32wSF+GJxCdH9J8Zk=; b=jcIcEqVmh5AOsw6SCn7+6Lu70M9app8anD+tg5UsAzMfwfG6VSqb1Joj1RHM4OIc8Y DxgQ6dzFprg8vXPGHUiKTXFl1kKHr/XFdDvZWIm/gXYBUfybE0th6aM6ILNdQrDz0duM HqmSlYUPLhFZXfE6IMkSgkBB3KjGChw/TUB4JVrJWiMBLIl9h87UVWeVsWF0DY71ryR6 zEfBCWTxnCaWcZnAyJx4cdOA0ZRoJ9mDpESvnUhxHo7IdcLBHu7hSGNKQ3eEAQNUHGab GYcABqQklOrFW1xJrgZV5PSJp4PSCcprZ7Opu5e1sct+Oubakpry3RraSGEKvh3b/Yk2 XmTQ==
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=61n1rTOQAdXv6eeHPFo5aQPM3i32wSF+GJxCdH9J8Zk=; b=E2B+yU7REhvroacmLDEcZQngYe7+cASYQ/LqwHrQc2sIsEkdTucgJp0CWc3NI/yIx7 950i7UYDvpEg3BVC7xDVVZOywRAXrudY2ElP8Xe/m7YqKpb5L4U9nvGZl0iaxy0XSD4E jW9pqvvlF+6vKJSBjIe9B3aVJeUl8NoqIbv+zFN1O+OyzaI3R7W54R9eBCLda5VFucbS EVTOk3jzlcEZOLsirt2/ppQnH9kSz/u8DlyzXlmtFpAiqANkrNaPGF2RfwQF1ZF4EYiF FGwt539mBYNOr15WYZFQiJBJE2cqhnUuSDs72OI8u/8fFFfyBeNW9Nt+D+K5KhF8HEsV K7Sg==
X-Gm-Message-State: AG10YOShZ+ORJUIyG60idgNy1uKl9SagEL7irLuS+H01DeI7ypwC++kj/LKOZ3Ex/JB3ww==
X-Received: by 10.107.12.19 with SMTP id w19mr1863666ioi.114.1454424846352; Tue, 02 Feb 2016 06:54:06 -0800 (PST)
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com. [209.85.223.178]) by smtp.gmail.com with ESMTPSA id k16sm1216739igf.0.2016.02.02.06.54.04 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 02 Feb 2016 06:54:05 -0800 (PST)
Received: by mail-io0-f178.google.com with SMTP id f81so19583690iof.0 for <mmusic@ietf.org>; Tue, 02 Feb 2016 06:54:04 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.157.70 with SMTP id g67mr17426142ioe.38.1454424844462; Tue, 02 Feb 2016 06:54:04 -0800 (PST)
Received: by 10.36.105.77 with HTTP; Tue, 2 Feb 2016 06:54:04 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37D664F2@ESESSMB209.ericsson.se>
References: <CAD5OKxvMdsdkYaJWB5UdvCTNj3a+pheXV+_1viyLrH_UOWBTpA@mail.gmail.com> <CAD5OKxum=E84NVTtWtSwYowDmyJ=sQifx6Na9wt0pUhYH1j_PA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37D557C6@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37D55EAA@ESESSMB209.ericsson.se> <CAD5OKxvaUi25TbOa48mKwkEJMnJqde_TQNfe1Cagdgj+jTbJ3g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37D57EFC@ESESSMB209.ericsson.se> <CAD5OKxuRwgs0w0iUorivK6BV_8bZNNN1D9w9ot4CVJ7CV-6xpw@mail.gmail.com> <CAMRcRGTDpXMdk9SqQtRCc+LyQff26-5NiV6er6dkbdJzJLEwAQ@mail.gmail.com> <56A51EE7.8060406@alum.mit.edu> <CAMRcRGRD_XedYjVfBxfwXFdxAmm_wTZ5HhK5S+iSrJXwOZogMw@mail.gmail.com> <56A53249.5020709@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37D59613@ESESSMB209.ericsson.se> <56A64EFD.4000509@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37D5B5E7@ESESSMB209.ericsson.se> <56A67995.4040309@alum.mit.edu> <CAD5OKxt_9DEH=NBsL1EunB3DviDsYhBCanQ2fpBZEA4pWyfadQ@mail.gmail.com> <56A67DBB.1000509@alum.mit.edu> <CAD5OKxsQqFPZn+BJGEtV8wNwkD3+BYuCQx3D-n_R9GY-r7xnHw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37D664F2@ESESSMB209.ericsson.se>
Date: Tue, 02 Feb 2016 09:54:04 -0500
X-Gmail-Original-Message-ID: <CAD5OKxt+PjhZydS57pcphr7dky8kknt+x-z5p-noOF+9ntYN4A@mail.gmail.com>
Message-ID: <CAD5OKxt+PjhZydS57pcphr7dky8kknt+x-z5p-noOF+9ntYN4A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="001a1140b47234f591052acaacbc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/WBkJiRE2ULKXLoik4kO9pZUR6zY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Not fixing a=rtcp and rtcp-mux exclusive
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: <https://mailarchive.ietf.org/arch/browse/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 Feb 2016 14:54:08 -0000

On Tue, Feb 2, 2016 at 4:32 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> So, assuming we would define a new attribute to indicate/negotiate
> mux-exclusive, I still think we need to say something about a=rtcp, don’t
> we?
>
>
>
> We could simply say that the a=rtcp attribute value must be identical to
> the port and address for RTP. That would work also for trickle ICE.
>
>
>
There is no harm in specifying a=rtcp but, in most practical scenarios, it
will serve no purpose. If legacy end point does not support mux-exclusive,
then media connection will be torn down even if the legacy end point does
support a=rtcp. The a=rtcp attribute should still be added for compliance
with ICE specification and for support of any forwarding or monitoring
agents.
_____________
Roman Shpount