IETF Logo Mail Archive

Re: [MMUSIC] draft-ietf-ice-rfc5245bis-00: Impacts due to ICE solution for indicating exclusive support of RTP/RTCP-mux.

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 07 December 2015 17:47 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1BD61AD0CB for <mmusic@ietfa.amsl.com>; Mon, 7 Dec 2015 09:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 lGOAH_FW3ZZ1 for <mmusic@ietfa.amsl.com>; Mon, 7 Dec 2015 09:47:39 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 585A41AD0C8 for <mmusic@ietf.org>; Mon, 7 Dec 2015 09:47:38 -0800 (PST)
X-AuditID: c1b4fb25-f79876d0000011ee-a5-5665c6380304
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E8.EE.04590.836C5665; Mon, 7 Dec 2015 18:47:36 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.142]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0248.002; Mon, 7 Dec 2015 18:47:35 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ietf-ice-rfc5245bis-00: Impacts due to ICE solution for indicating exclusive support of RTP/RTCP-mux.
Thread-Index: AdEw9h0T1n2MvyaVQyCQVkwuTjgRDQAFyfKAAAKFblI=
Date: Mon, 07 Dec 2015 17:47:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37C897CC@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37C89172@ESESSMB209.ericsson.se>, <5665C35B.50206@alum.mit.edu>
In-Reply-To: <5665C35B.50206@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37C897CCESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbFdVNfiWGqYwayHghZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXx93FQwbLYis+7P7M3MD736WLk5JAQMJHY PWEmM4QtJnHh3no2EFtI4DCjxPR10V2MXED2YkaJVwcPsnQxcnCwCVhIdP/TBqkREfCVePb4 NhtIjbBAM6PE1C0bGUEcEYEWRolzq/vZIKqsJH4s/sYEYrMIqEjMWHSSFcTmBeo+emYdM8S2 bIkTj++A1XMKaEl0H97MDmIzAl30/dQasF5mAXGJpi8rWSEuFZBYsuc81NWiEi8f/2OFqMmX +LX3DTvEfEGJkzOfsExgFJ6FpH0WkrJZSMog4gYSX97fhrK1JZYtfM0MYetLdL8/zYQsvoCR fRWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYPwc3PJbdQfj5TeOhxgFOBiVeHg3tKaECbEm lhVX5h5ilOBgVhLhlc1MDRPiTUmsrEotyo8vKs1JLT7EKM3BoiTO28z0IFRIID2xJDU7NbUg tQgmy8TBKdXAKNb9vMjcX6xu3sVWqzyJyNpfn1j6WxdGvV/1LeX0p+srfXzP293pcrLY5HX4 Fher3ZeLG57/kRH5/k0vmrnpo2f9D07zYkemi/bMK6bHMzj8n1Hw99Lj9/bLmxaGhRy+YnJM PiK/a8WNogmTjj37Y1dXeZNfffXN71qLExMcK219ZvKUN6wpUWIpzkg01GIuKk4EACBBUcub AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/vCgM5FHofq1Ld8UpqHfeELQOETg>
Subject: Re: [MMUSIC] draft-ietf-ice-rfc5245bis-00: Impacts due to ICE solution for indicating exclusive support of RTP/RTCP-mux.
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 07 Dec 2015 17:47:41 -0000

Hi Paul,

Please see my reply to Roman, where I asked about how one would be able to distinguish between RTP/RTCP-mux and no RTCP at all in case only RTP candidates are provided.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Paul Kyzivat<mailto:pkyzivat@alum.mit.edu>
Sent: ‎07/‎12/‎2015 19:35
To: mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-ietf-ice-rfc5245bis-00: Impacts due to ICE solution for indicating exclusive support of RTP/RTCP-mux.

Christer,

The new text seems to imply there is a valid situation where RTP is used
but RTCP is not *used*. Is that intended? Does RTP allow that?

(I realize it is done in the wild, but this would legitimize it.)

        Thanks,
        Paul

On 12/7/15 8:52 AM, Christer Holmberg wrote:
> Hi,
>
> In order to clarify that the absence of an RTCP component does NOT by
> default mean that RTCP is not used, I suggest some additional text to
> the new text.
>
> Regards,
>
> Christer
>
> Section 4.1.1.1:
>
> --------------------
>
> OLD TEXT:
>
>     Each component has an ID assigned to it, called the component ID.
>
>     For RTP-based media streams, the RTP itself has a component ID of 1,
>
>     and RTCP a component ID of 2.  If an agent is using RTCP, it MUST
>
>     obtain a candidate for it.  If an agent is using both RTP and RTCP,
>
>     it would end up with 2*K host candidates if an agent has K IP
>
>     addresses.
>
> NEW TEXT (based on e-mail discussion):
>
> Each component has an ID assigned to it, called the component ID.
>
> For RTP-based media streams, unless RTP and RTCP are multiplexed on
>
> the same port (RTP/RTCP multiplexing), the RTP has a component ID of 1
>
> and RTCP a component ID of 2. In case of RTP/RTCP multiplexing, a
>
> component ID of 1 is used for both RTP and RTCP.
>
> When candidates are obtained, unless the agent knows for sure that
>
> RTP/RTCP multiplexing will be used (i.e. the agent knows that the
>
> other agent also supports, and is willing to use, RTP/RTCP multiplexing),
>
> or unless the agent only supports RTP/RTCP multiplexing,
>
> the agent MUST obtain a separate candidate for RTCP. If an agent has
>
> obtained a candidate for RTCP, and end up using RTP/RTCP multiplexing,
>
> the agent does not need to perform connectivity checks on the RTCP
> candidate.
>
> If an agent is using separate candidates for RTP and RTCP, it will end up
>
> with 2*K host candidates if the agent has K IP addresses.
>
> NOTE: The responding agent, when obtaining its candidates, will
> typically know
>
> whether the other agent supports RTP/RTCP multiplexing, in which case it
> will
>
> not need to obtain a separate candidate for RTCP.
>
> <new>NOTE: There needs to be a signalling mechanism to indicate whether
>
> the absence of a component ID of 2 means that RTCP is not used, or that
>
> RTP/RTCP multiplexing is used. Such mechanism is outside the scope of
>
> this document.</new>
>
> Section 4.2:
>
> ---------------
>
> OLD TEXT:
>
> Each component has an ID assigned to it, called the component ID.
>
>        For RTP-based media streams, the RTP itself has a component ID of 1,
>
>        and RTCP a component ID of 2.  If an agent is using RTCP, it MUST
>
>        obtain candidates for it.
>
> NEW TEXT:
>
> Each component has an ID assigned to it, called the component ID.
>
>        For RTP-based media streams, the RTP itself has a component ID of 1,
>
>        and RTCP a component ID of 2.  If an agent is using RTCP, it MUST
>
>        obtain candidates for it<new>, unless the agent only supports
> multiplexing
>
>        of RTP and RTCP on the same port</new>.
>
> <new>NOTE: There needs to be a signalling mechanism to indicate whether
>
> the absence of a component ID of 2 means that RTCP is not used, or that
>
> RTP/RTCP multiplexing is used. Such mechanism is outside the scope of
>
> this document.</new>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email