Re: [rtcweb] Drop RFC 4588 RTX session multiplexing support requirement from RTP USAGE

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 27 October 2014 16:41 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9398C1A1A4B for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 09:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 PAqx3senVGBo for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 09:41:20 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A51161A1A27 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 09:40:32 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id x12so1738942wgg.28 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 09:40:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=8kIeqK2sW4EZn20IzOlqhvSdvn4h6Vp7RpoAj3qUwG4=; b=V/wGFFaf8g/GjNBg/gYZ869R2zUnRRbxDmWZnv9TAQpGbGPLgINJp2JVIN9Nq9dNth PhWiLuilRul6l8TZHQzTC2yyVR7KTa9YdTQy8MbupypsxHm1SRDfT1Nskv+MrbMR/W3G KsDRTZDFaslF1sqs2/xhwq431MCUjEcPIiMrq8PMiBXoe6pdTPC1KiJ0vOSoZkk5wKzG Yf2dFwpAC9B8zGSdW+o+XO485E9C5AvKLg7GtNUq4rllWaGNDApw3zA/JTxOkUAB893x PIU7kExRZHoQQmY5EQWS4zr8CrfQGL+ZG5s1g7MH/AzfLMqT3v+NSQ16dAOA8FfWlWN6 GKXw==
X-Received: by 10.180.205.171 with SMTP id lh11mr22154943wic.66.1414428030991; Mon, 27 Oct 2014 09:40:30 -0700 (PDT)
Received: from [192.168.1.37] (144.Red-83-43-188.dynamicIP.rima-tde.net. [83.43.188.144]) by mx.google.com with ESMTPSA id c15sm10591554wib.3.2014.10.27.09.40.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Oct 2014 09:40:30 -0700 (PDT)
Message-ID: <544E7586.4080703@gmail.com>
Date: Mon, 27 Oct 2014 17:40:38 +0100
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>
References: <5446ACD8.1010004@gmail.com> <B9AC89FB-C656-42C7-9204-C2B3AC6B8E29@csperkins.org>
In-Reply-To: <B9AC89FB-C656-42C7-9204-C2B3AC6B8E29@csperkins.org>
Content-Type: multipart/alternative; boundary="------------060408080202040307060508"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/OczHwWKobVpZ4_knwEmtWsPSehU
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Drop RFC 4588 RTX session multiplexing support requirement from RTP USAGE
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 16:41:24 -0000

On 27/10/2014 17:36, Colin Perkins wrote:
> Hi,
>
> On 21 Oct 2014, at 19:58, Sergio Garcia Murillo 
> <sergio.garcia.murillo@gmail.com 
> <mailto:sergio.garcia.murillo@gmail.com>> wrote:
>> Not sure if it is done on pourpose, but according to the RTP usage 
>> draft, it may seem that full RFC 4588 is mandated at the recevier side:
>>
>>      Receivers are REQUIRED to implement support for RTP retransmission
>>      packets [RFC4588  <https://tools.ietf.org/html/rfc4588>].
>>
>> That would include both modes, session and ssrc multiplexing. Given 
>> the extensive usage of bundle and current implementations, session 
>> multiplexing support doesn't make much sense.
>>
>> Should we drop it, and state that only ssrc-multiplexing shall be 
>> supported at the receiving end?
>
> I don’t see any advantage to doing so, given that support for 
> non-BUNDLE sessions is REQUIRED. You need to implement the signalling 
> needed for session-multiplexing of retransmission packet anyway, so 
> disallowing it buys you nothing.
>

You can do SSRC multiplexing with BUNDLE and non-BUNDLE sessions, what I 
don't see is how to do session multiplexing with BUNDLE sessions.

Best regards
Sergio