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

Justin Uberti <juberti@google.com> Wed, 01 May 2013 22:29 UTC

Return-Path: <juberti@google.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 A00F421F8B8F for <mmusic@ietfa.amsl.com>; Wed, 1 May 2013 15:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.069
X-Spam-Level:
X-Spam-Status: No, score=-101.069 tagged_above=-999 required=5 tests=[AWL=-0.758, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666, USER_IN_WHITELIST=-100]
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 S5mzMOYJV35M for <mmusic@ietfa.amsl.com>; Wed, 1 May 2013 15:29:26 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2595221F986B for <mmusic@ietf.org>; Wed, 1 May 2013 15:29:22 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id c12so2520124ieb.3 for <mmusic@ietf.org>; Wed, 01 May 2013 15:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=gBhWNKKci5flG6QgjPlemXxuIBP1NsdC8tK4ebeh0kI=; b=e/UNX2l85r/FhV3xpDrNARwMIX1ycFM3Nj45DcySzQoP7LBnY1KNRzVsnEstPKz+iP zv94X6FwVoj2hWn8XMApP4TBN/VOBkl4u4W60sb21cqHZ3twc/Pz+wQo1+hccjK8z5Uh MtbLD6KZFzydrDYlGtSkWhSfCx79Rzg0HeDCPpRRttpfvWPGP9Gcp760EtFL8NQuYR9w 9q4ZAR4HEgMMgfwXSrh7rqF5O4T8+x8TJRn2zkNVhiaavBwgNhAmcdHcCUAqpUAWt4uB 4G7vZMGx3mjc0cKTup1tR+lm4wk/1X1rmzX6l+nBiHTayFJwv7ALuK7d6Ea75NVsMb4d S+BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=gBhWNKKci5flG6QgjPlemXxuIBP1NsdC8tK4ebeh0kI=; b=aJJe347k8+XG0WqdIYAVLsRG+CpTGZ1D2s+1Y205j67YCjqeY1n7KnT7BHeMPSDKym Kz9JKOQN4qniYfmAwNlccBkwrLpFqK9dtaNc1Z6Aj2mMbMejH9SE09fD0YAK2+PONtgh P3OR7rwgT7w9JedYebnYCgG4Kqbj9Krny9UaJUyTOTGMpl+R9H+XeKQDPQL8JZaiKj1R rBQ3qPG50fixAZifv8671uxwwdDitAaobHvIM6wCLsIk44iszLH8f9LCfdRdYZrvAHP3 Dk2UFRs18oXw/7yU3WwfNCJCiw5QXQJS2NcHutaM6LDq1pryUYTcmvb7CBgGNLiEL5eB ooHg==
X-Received: by 10.50.18.74 with SMTP id u10mr2708271igd.42.1367447361754; Wed, 01 May 2013 15:29:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.193.201 with HTTP; Wed, 1 May 2013 15:29:01 -0700 (PDT)
In-Reply-To: <51801BBD.1010505@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B1C368E12@ESESSMB209.ericsson.se> <517FFB7E.8050801@alum.mit.edu> <CABkgnnVf6f3RrP2h66_8hFPZScWU3Xp4f1x0dmW0xhmvZRQ70Q@mail.gmail.com> <51801BBD.1010505@alum.mit.edu>
From: Justin Uberti <juberti@google.com>
Date: Wed, 1 May 2013 15:29:01 -0700
Message-ID: <CAOJ7v-12j0k1W7GRfOzvPmfN-BZ0ve=fHVcWy+avronfc8wFYw@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=089e014947363f359404dbafa6bb
X-Gm-Message-State: ALoCoQlXZ17LIpyHXRouPYP5TiBlc96BtYvF5lPBi5GHn9LnsfpY9gkoQC7lT+GfyKi8MRjrU3Z68nHCQdHTEZZomdC4B4uBiOf0rmCpXLLuiP4EhSs41q1K/xhDmyvdVaMiskZOXIewNJXZZYfY5FgG996YxS9dtrJ/dIfBIyl6IVPtabGzzBgQkqzA9wTuJp9MRV2w1WdQ
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: Wed, 01 May 2013 22:29:26 -0000

+1 to mandating rtcp-mux when BUNDLEing.

Otherwise, we have weird situations, such as if you try to BUNDLE a SCTP
session and a non-RTCP-mux RTP session together; the former has 1 ICE
component, the latter has 2.


On Tue, Apr 30, 2013 at 12:30 PM, Paul Kyzivat <pkyzivat@alum.mit.edu>wrote;wrote:

> On 4/30/13 3:00 PM, Martin Thomson wrote:
>
>> 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.
>>
>
> Well, IIUC it was separate before there was a way to combine them.
> Why was that? Why hasn't separate RTCP gone away entirely?
>
>         Thanks,
>         Paul
>
> ______________________________**_________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/**listinfo/mmusic<https://www.ietf.org/mailman/listinfo/mmusic>
>