Re: [MMUSIC] RID, MID and BUNDLE: Associate received RTP packet with m- line

Christer Holmberg <> Thu, 22 October 2015 19:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 346DD1B3C2E for <>; Thu, 22 Oct 2015 12:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wzeFlytDDMr9 for <>; Thu, 22 Oct 2015 12:11:13 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 874951B3C98 for <>; Thu, 22 Oct 2015 12:11:12 -0700 (PDT)
X-AuditID: c1b4fb30-f79626d000006adf-09-562934ce3da9
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 87.E4.27359.EC439265; Thu, 22 Oct 2015 21:11:10 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Thu, 22 Oct 2015 21:11:09 +0200
From: Christer Holmberg <>
To: "Mo Zanaty (mzanaty)" <>
Thread-Topic: [MMUSIC] RID, MID and BUNDLE: Associate received RTP packet with m- line
Thread-Index: AQHRDP1K55HrvCQ2BUaqlMEgbecddZ534MyQ
Date: Thu, 22 Oct 2015 19:11:09 +0000
Message-ID: <>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37B89A21ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM+Jvje45E80wg3nPDC2mLn/MYvHiwRwm ByaPKb83snosWfKTKYApissmJTUnsyy1SN8ugStj8t3wgul1FY0/pRoYFxR0MXJySAiYSNye sIcRwhaTuHBvPVsXIxeHkMBRRolZl/pYIZzFjBLX3j1j72Lk4GATsJDo/qcN0iAioCvx7vcz RpAws4C6xNXFQSBhYYFwiWlr28DCIgIREmu+OUJUG0nM+fiGGcRmEVCVeLgNwuYV8JXY3doD teklo8TmH8fZQRKcAvoSLxYcZAWxGYFu+35qDROIzSwgLnHryXwmiJsFJJbsOc8MYYtKvHz8 jxXCVpJYsf0SI0R9vsTlmb1sEMsEJU7OfMIygVF0FpJRs5CUzUJSBhHXkViw+xMbhK0tsWzh a2YY+8yBx0zI4gsY2VcxihanFiflphsZ6aUWZSYXF+fn6eWllmxiBEbawS2/DXYwvnzueIhR gINRiYf3AZdGmBBrYllxZe4hRgkOZiUR3v6nQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8zUwP QoUE0hNLUrNTUwtSi2CyTBycwBht3lDGzrE3z6Sxyo3xDHv1lP4tDse18lK3hEud2j3R3Mjw RnvbuyD/F/n3L8enPjA/zMT8/PtNSWMzDbtD+79H7Nwycf3ECo71x6ZtOCsoU2S8vatl0grr YDOpbYe0Dm5KjJLiT3sR9s9ESDz96yLGGze3ftzBUM0ZrPbBXC9+uXD718zoWyeUWIozEg21 mIuKEwH7CLjAsAIAAA==
Archived-At: <>
Cc: "" <>
Subject: Re: [MMUSIC] RID, MID and BUNDLE: Associate received RTP packet with m- line
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 22 Oct 2015 19:11:16 -0000


From: Mo Zanaty (mzanaty) []
Sent: 22 October 2015 22:10
To: Christer Holmberg <>
Subject: Re: [MMUSIC] RID, MID and BUNDLE: Associate received RTP packet with m- line

Referring to BUNDLE works for warning implementers against relying on MID in every RTP packet. But the same warning is needed for RID regardless of whether BUNDLE is used or not.


On 10/22/15, 3:01 PM, Christer Holmberg <<>> wrote:


>MID and RID are both RTCP SDES items that echo SDP identifiers in RTP/RTCP using the generic sdes->hdrext mechanism. Once the identifier value is associated to an RTP stream (identified by its SSRC) via >RTCP packets with MID/RID SDES items or RTP packets with MID/RID header extensions, the >association can remain in effect without echoing the header extension in every RTP packet.
>We should probably add some text to warn implementers not to rely on receiving MID and RID in >every RTP packet, and use the last valid association to that SSRC when absent.

Or, you could simply refer to BUNDLE, because this is only going to be an issue when BUNDLE is used.




On Oct 22, 2015, at 9:53 AM, Christer Holmberg <<>> wrote:

Section 7 of the RID draft says:

"Note that 'rid's are only required to be unique within a media
   section ("m-line"); they do not necessarily need to be unique within
   an entire RTP session.  In traditional usage, each media section is
   sent on its own unique 5-tuple, which provides an unambiguous scope.
   Similarly, when using BUNDLE
   [I-D.ietf-mmusic-sdp-bundle-negotiation], MID values associate RTP
   streams uniquely to a single media description."

However, when BUNDLE is used, the MID value (RTP MID header extension) is not guaranteed to be present in every RTP packet. Section 14.1. of BUNDLE says:

"The RTP MID header extension SHOULD be included in some RTP packets
   at the start of the session and whenever the SSRC changes.  It might
   also be useful to include the header extension in RTP packets that
   comprise random access points in the media (e.g., with video

So, if the MID value is NOT included, and RTP packets associated with multiple m- lines use the same RIP value and the same PT value, will it be possible to associate the RTP packets to a single media description?



mmusic mailing list<>