Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?

Martin Thomson <martin.thomson@gmail.com> Tue, 30 April 2013 19:00 UTC

Return-Path: <martin.thomson@gmail.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 742F221F9C8C for <mmusic@ietfa.amsl.com>; Tue, 30 Apr 2013 12:00:41 -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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzCdYjJOSPxw for <mmusic@ietfa.amsl.com>; Tue, 30 Apr 2013 12:00:38 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6860821F9C96 for <mmusic@ietf.org>; Tue, 30 Apr 2013 12:00:32 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id m15so3323798wgh.3 for <mmusic@ietf.org>; Tue, 30 Apr 2013 12:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=T5qUI+AgSi+ITQm9LHw0/4rzU8wn++KOxKb5gpyLbxI=; b=XnYayf3bqbUFpZdnHWjraYlbKQ29a9JwuHXIckPi6y9RqphI3a+baDmxZ7yJbjjhwg RdGB/a9WVcUCmzfr0QMUQkiJ83cEx8XBGTgodyry/7MMD2N1d4pnKgEdgWwOnkN6YkOQ HxQd2oFNb5X2RRfqyvNzFk2oR4UrmSOu2JudGYQHasdK1xEOrT4lhpMfQSqmvQZKQ4cL zacrKBQZQrJdWLP3/AVT1y5i7ouhYYu04WKnmh4vEQ4f+UuGQJFRF6T9Hvt0z3wAKLaV UCtW0iZP3MNyugc9VDPwK1mQCRodyDV9ArEBVgZvcLUALZiXzonAW2aM9rBCPDCnH2X2 mrLQ==
MIME-Version: 1.0
X-Received: by 10.194.63.239 with SMTP id j15mr20445038wjs.30.1367348431597; Tue, 30 Apr 2013 12:00:31 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Tue, 30 Apr 2013 12:00:31 -0700 (PDT)
In-Reply-To: <517FFB7E.8050801@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B1C368E12@ESESSMB209.ericsson.se> <517FFB7E.8050801@alum.mit.edu>
Date: Tue, 30 Apr 2013 12:00:31 -0700
Message-ID: <CABkgnnVf6f3RrP2h66_8hFPZScWU3Xp4f1x0dmW0xhmvZRQ70Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: mandate RTP/RTCP multiplexing?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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, 30 Apr 2013 19:00:42 -0000

On 30 April 2013 10:12, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> What are the implications of *not* mandating it?

I'm more interesting in learning why someone might want to split it
out.  I can't see any reason for doing that...

...that is, except perhaps for some of the fictitious attacks I invent
when someone suggests that RTCP is a good place for a security
mechanism of one sort or other.