Re: [MMUSIC] The way forward wih mux-exclusive

Roman Shpount <roman@telurix.com> Thu, 14 April 2016 20:10 UTC

Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB9112D6A6 for <mmusic@ietfa.amsl.com>; Thu, 14 Apr 2016 13:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
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 DMGKF7Db05G5 for <mmusic@ietfa.amsl.com>; Thu, 14 Apr 2016 13:10:01 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 1CA8312D5FE for <mmusic@ietf.org>; Thu, 14 Apr 2016 13:10:01 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id 2so115290568ioy.1 for <mmusic@ietf.org>; Thu, 14 Apr 2016 13:10:01 -0700 (PDT)
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; bh=DtCU5hD+3BhWyMEJbxmu/77qhxsxavHH27SH8kxs7xw=; b=wPubyqcv4deqSvFEL9/Vc/5kqC+NJjIbauRA4rkOOrnyKNfo28eNMW2tHWWdbvB17O ut+NVyciizGYKNoM4HvxrQuMbvweybUDxspB4qTr8VRRtHcxbLYzKiKR5+l5V9owsxJ6 d73lQqAgE3nYakcR8MwUlEw4Xmg5oJsBVO8gmKNqQrRpiZIwty9X2NgZixuI5WY96pF3 xXhpANglTZlxP73AMx8yIuYCn430zthJI+Cq9TI/UxgtkVH7QawiBy9euuBptKBNguGC wdJ4PFTz38358nQ0HV66QOStXswgmgWdaTm3qgEPWsbs7Na37qw+g9Csa44vGXPdl0Gl Ihtg==
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; bh=DtCU5hD+3BhWyMEJbxmu/77qhxsxavHH27SH8kxs7xw=; b=CecBKNRxH0o3zD26wVma1S62GfEUbcq/4pa0DVn+GqMHoOdNXGNVqct/nSlagWkcT/ TLffi8NgOR0ILBlCIUNxlQcqyMfAdQ0A8x0W8l6z32Xt+tkdr9M3NIN8C996lSNXVZoF a9pkDDbJoR7w0X15N5j9FXs8y0+dBw4DMCGnlRcnCOltTF46NkpR8xIVpl8Bzr3Dkuge s6cNrv6TOYgxWa2UCeB6ubV64tB1omAfa7YcHLydCdbD4z/w+qFBELemv0+zxfMXCn7S mTfVqrLLvURJ28g+7RPHFW86MnwdyBznjASWVg/H5+Af8bMEWba7WW7aBgqVxzLFrygJ X9iQ==
X-Gm-Message-State: AOPr4FUWTWvOOa+t88vnZQ8664NCM4eB7UjtLCzFqM7CTV3g/Rpm2YoLv6+qtmilOOVruw==
X-Received: by 10.107.47.167 with SMTP id v39mr18009341iov.89.1460664600429; Thu, 14 Apr 2016 13:10:00 -0700 (PDT)
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com. [209.85.223.170]) by smtp.gmail.com with ESMTPSA id q198sm26094198iod.6.2016.04.14.13.09.59 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2016 13:10:00 -0700 (PDT)
Received: by mail-io0-f170.google.com with SMTP id o126so115353227iod.0 for <mmusic@ietf.org>; Thu, 14 Apr 2016 13:09:59 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.30.71 with SMTP id e68mr18779016ioe.145.1460664599698; Thu, 14 Apr 2016 13:09:59 -0700 (PDT)
Received: by 10.36.106.194 with HTTP; Thu, 14 Apr 2016 13:09:59 -0700 (PDT)
In-Reply-To: <570FF6EF.7020308@alum.mit.edu>
References: <5707C2A6.2060001@cisco.com> <CAD5OKxshqQA5YMn6RuALcWhYjLTQB4d-H-7+JatMwO7AnT+pCw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37F37087@ESESSMB209.ericsson.se> <CAD5OKxtj-58ZN5VqKouu3Pf6c3Hjd+eQz9aD_a6+cLgaf-98tw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37F3715D@ESESSMB209.ericsson.se> <CAD5OKxuq+djAMceiweSpzNtfVWHzBtm=n8-=-uuhybVHAtvNHQ@mail.gmail.com> <570FF6EF.7020308@alum.mit.edu>
Date: Thu, 14 Apr 2016 16:09:59 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv=SdH2_LQVh3gqDqTnpWk-_GhwsrnJdajcvnYw3P+VFQ@mail.gmail.com>
Message-ID: <CAD5OKxv=SdH2_LQVh3gqDqTnpWk-_GhwsrnJdajcvnYw3P+VFQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary="001a1140d71e9a20550530777af0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/UB1WLmLMRiT2_dWDcQ3AqEFkeuw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] The way forward wih mux-exclusive
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 14 Apr 2016 20:10:03 -0000

On Thu, Apr 14, 2016 at 4:00 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 4/14/16 3:49 PM, Roman Shpount wrote:
>
>> This can currently produce interop problems. With current usage, if
>> rtcp-mux is supported by the remote end point, it will correctly
>> negotiate with rtcp-mux-exclusive. If you remove rtcp-mux attribute from
>> the offer, connection will not be established. This will be especially
>> important during the migration from rtcp-mux to rtcp-mux-exclusive for
>> current implementations. Only inserting rtcp-mux-exclusive, of cause, is
>> better long term, since it is removing redundant information from SDP.
>>
>
> So, why not remove use of rtcp-mux as a *requirement* and leave it as an
> implementation tactic for migration?


I would be happy to remove this as a "requirement". Specify that it can be
optionally used during the migration. But if we do this we will need to
update RFC5761, since rtcp-mux will be used without RTCP fallback address
being provided (which is required by RFC5761).
_____________
Roman Shpount