IETF Logo Mail Archive

Re: [MMUSIC] Sending a=rtcp-mux-only w/o a=rtcp-mux

Roman Shpount <roman@telurix.com> Fri, 03 February 2017 18:05 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 921061294B3 for <mmusic@ietfa.amsl.com>; Fri, 3 Feb 2017 10:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=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 9ae5QbTEbYoZ for <mmusic@ietfa.amsl.com>; Fri, 3 Feb 2017 10:05:54 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 5C83B129494 for <mmusic@ietf.org>; Fri, 3 Feb 2017 10:05:54 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id 11so6164516qkl.3 for <mmusic@ietf.org>; Fri, 03 Feb 2017 10:05:54 -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:from:date:message-id:subject:to :cc; bh=krcIJ0Kkwu9tWDLnjtOu8VsHX+OtcP/QVPAaXRBgNug=; b=pvxJtOtqRYWSLzD85NHxS3fmikGv8OgGX34gI29AkPEhWyZGe+qGfMAQBD1z/f5QBd F3s4bZDqGVDH3uvE4usqfPFFry1rqLIeDMfFrKEMWM2Qb/Iduc7W60tq28PUA/g61J1b XmUoY8emFu1r95hq+9A56fKnBR8iKmsVern1B5oe1iq84eKUpvlWPkyEoZyFq0OsEA7R B7vej3wwfLk4R1zGRk7ikcvZxakDN6iUWQu2/WEYulzGqP4Q4Mr7pwY+MMpb1zaIEZSP pt0u1qJeaE0UCnjtVtSQVKZMVDk1bNcTFj3R9WboEVC6b/woHU2dARQo3kkxk6gUSiEj 9U+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=krcIJ0Kkwu9tWDLnjtOu8VsHX+OtcP/QVPAaXRBgNug=; b=kOa80i+KQdws3AEcy5QVbGPcrIUFUV6ncjxf2hOzy4MxGd47RJRKdO0lfkoahUK3Ra 4+3RxXSB1fzTY3QvUAxEh2C4zq7CG3R+EMj7QG9qX7vOds90vk8ioJx21K1z0UHXvSsP qlnmv7OSBVv0OONrZLGCo1D2oyI4ajlH/PJfEkMLfA2BQoazFnKxYgp1SoZmenP63n+z RBVz00mjV1syZmWm6wBTEILraPN0NNzs2Nx1UlHJ9FkI5IE9XtsFcxNcz02WnrSjkZFp slAbBXc5DVratovsHnpFtRDOvXWQv1lrn2an3E32QMsdD00mkkuiE+xIcYrz3X+Ctfti P02A==
X-Gm-Message-State: AMke39mvp0YN36tinezIcKibtBbEmWQGF53mBCEU+euYIUpN5B4q6ivMsG3/XIrrC7HPag==
X-Received: by 10.55.69.80 with SMTP id s77mr15105722qka.159.1486145153094; Fri, 03 Feb 2017 10:05:53 -0800 (PST)
Received: from mail-qt0-f176.google.com (mail-qt0-f176.google.com. [209.85.216.176]) by smtp.gmail.com with ESMTPSA id d52sm25004036qtc.2.2017.02.03.10.05.52 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Feb 2017 10:05:52 -0800 (PST)
Received: by mail-qt0-f176.google.com with SMTP id w20so42846552qtb.1 for <mmusic@ietf.org>; Fri, 03 Feb 2017 10:05:52 -0800 (PST)
X-Received: by 10.200.52.129 with SMTP id w1mr13703013qtb.43.1486145152385; Fri, 03 Feb 2017 10:05:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.131.66 with HTTP; Fri, 3 Feb 2017 10:05:51 -0800 (PST)
In-Reply-To: <CABcZeBOY5pNRB=W_Zkqm5gYDMRGb-p7ChYctGRmfw5oGyYk-Pg@mail.gmail.com>
References: <CABcZeBPESaiH2wuE8RhcBHKz5h10MjKQ_EBDzcRpoy7mYeaspA@mail.gmail.com> <CABcZeBOY5pNRB=W_Zkqm5gYDMRGb-p7ChYctGRmfw5oGyYk-Pg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 03 Feb 2017 13:05:51 -0500
X-Gmail-Original-Message-ID: <CAD5OKxueYNNR1idytvRQAco2gAXW18J1MsdKf5Jgr+vn7qZ1=Q@mail.gmail.com>
Message-ID: <CAD5OKxueYNNR1idytvRQAco2gAXW18J1MsdKf5Jgr+vn7qZ1=Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary="001a11479b4ae4f6dd0547a4219b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WMoneXQTIBR5qSeDF9SRgmwXTEg>
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Sending a=rtcp-mux-only w/o a=rtcp-mux
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: Fri, 03 Feb 2017 18:05:55 -0000

In 3, offerer sends rtcp-mux and rtcp-mux-only together. If it gets an
answer without either rtcp-mux or rtcp-mux-only, offerer must tear down the
connection.

In 4, offerer sends rtcp-mux-only. If it gets an answer without
rtcp-mux-only, offer must tear down the connection.

In general 3 is redundant and was intended to be used during transition
while rtcp-mux-only is implemented.

Regards,

_____________
Roman Shpount

On Fri, Feb 3, 2017 at 12:41 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> Following up to myself, I don't think it's sensible for answers to contain
> a=rtcp-mux-only, because either you accepted mux, in which case all is
> good, or you rejected it, in which case it was rejected.
>
> -Ekr
>
>
> On Fri, Feb 3, 2017 at 9:38 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>> I have been reading the mux-exclusive document and I'm not sure it says
>> quite what we want. Specifically, S 4.2 says:
>>
>>    When an offerer sends the initial offer, if the offerer wants to
>>    indicate exclusive RTP/RTCP multiplexing for RTP-based media, the
>>    offerer MUST associate an SDP 'rtcp-mux-only' attribute with the
>>    associated SDP media description ("m=" line).
>>
>>    In addition, if the offerer associates an SDP 'rtcp-mux-only'
>>    attribute with an SDP media description ("m=" line), the offerer MAY
>>    also associate an SDP 'rtcp-mux' attribute with the same SDP media
>>    description ("m=" line), following the procedures in [RFC5761].
>>
>> As I understand this text, the offerer may say the following things:
>>
>>  1. No a=rtcp-mux: No muxing.
>>  2. a=rtcp-mux: I am offering RTCP mux
>>  3. a=rtcp-mux-only + a=rtcp-mux: I will only do RTCP mux
>>  4. a=rtcp-mux-only: I will only do RTCP mux (same as #3).
>>
>> I don't think the last of these is sensible. No current implementation
>> will know what to do with a=rtcp-mux-only w/o a=rtcp-mux, so this will
>> result in interop failures. Thus the MAY in the second graf needs to be
>> a MUST.
>>
>> -Ekr
>>
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

v2.23.0 | Report a Bug | By Email