Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th) - Late night version
Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 20 June 2013 18:18 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 33BA621F9C88 for <mmusic@ietfa.amsl.com>; Thu, 20 Jun 2013 11:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.328
X-Spam-Level:
X-Spam-Status: No, score=-0.328 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 lyVjP52YWQRX for <mmusic@ietfa.amsl.com>; Thu, 20 Jun 2013 11:18:27 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 9493421F9CD7 for <mmusic@ietf.org>; Thu, 20 Jun 2013 11:18:24 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta05.westchester.pa.mail.comcast.net with comcast id qamS1l0010EZKEL55iJ9ib; Thu, 20 Jun 2013 18:18:09 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta01.westchester.pa.mail.comcast.net with comcast id qiJ81l00o3ZTu2S3MiJ8iq; Thu, 20 Jun 2013 18:18:09 +0000
Message-ID: <51C34761.2080500@alum.mit.edu>
Date: Thu, 20 Jun 2013 14:18:09 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1C3B154D@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C3B154D@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1371752289; bh=y/SnIn3OzzjoaN37VmH0Qbstm+aiwgSUgAVvA4sP89U=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ea1fjDsk/7nl+KgkTk6SxXWDJvTR/cJDPtJyMWW/OLpsA5/lH09fpCpG5WZ0kyssx fPfsl6jNOR0BIBLijrj7s3/Xm5R5p5aF1F3hYYGVmJGY1XcEnIrcTCObE+S4z1fr1u TbMSbJ5Fa+5TjcUGkvTDMd6tKgWymlX8iAZvdrzarpJO4nU7991S3tiR8cRHKx9zlM waz1ySUrRhjRCBpa3O8r4qUjJPA9Nz4ToaXYcBaZLCfCS1cDgh53eKAHeRpRSEveKo e1L1NQTDk07sGNTpZaAXVfnXBKe+Dkq/UsP2PU44pHQRydUS2KHGIP/F5z6rDfttml FAhFxV6HAO4Wg==
Subject: Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19th) - Late night version
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: Thu, 20 Jun 2013 18:18:32 -0000
Getting better. More inline. On 6/19/13 2:38 PM, Christer Holmberg wrote: > Hi, > > I modified the text, based on the comments. > > - The text now refers to RFC 5764 for RTP, DTLS, STUN de-multiplexing. > - I added an open note regarding how much we need to specify regarding "m= line de-muxing" for the same transport protocol. > - I removed the MUST for having to be able to do "m= line de-muxing" for the same transport protocol, as there could be cases where it's not needed. > > Regards, > > Christer > > -------------------------------------------------- > > > 9.1. General > > Endpoints can assign "m=" lines representing different transport > protocols [RFC4566], identified using the "m=" line proto value > [RFC4566]. > > As each "m=" line in a BUNDLE group share the BUNDLE address, an > endpoint MUST be able to de-multiplex data received on the BUNDLE > address, meaning it MUST be able to associate the received with one > of the transport protocols assigned to the BUNDLE group. Endpoints > MUST NOT assign a transport protocols to a BUNDLE group, unless it is > able to separate received data from data associated with other > transport protocols assigned to the BUNDLE group. > > In addition, if an endpoint assigns multiple "m=" lines representing > the same transport protocol to a BUNDLE group, the endpoint might > also have to be able to, in addition to associating received data to > its transport protocol, associate the received data with a specific > "m=" line representing that transport protocol. > > OPEN ISSUE: We need to discuss how much, if anything, we need to say > about associating RTP packets with the correct "m=" line, in cases > where there are multiple "m=" lines for RTP media. My position on this is well known - presumably the issue refers to my arguments. So I won't repeat them here. *If* we can agree that associating packets to m-lines is a MUST, then the two paragraphs above the open issue can be collapsed into one. (If you can associate to an m-line, then of course you can associate to the protocol described by the m-line. > Section 5.1.2 of [RFC5764] specifies how to de-multiplex RTP, DTLS and > STUN [RFC5389] data packets. Something special must be said about STUN, because it is indeed an exception to my point about associating to an m-line. It is also an exception to associating to a protocol mentioned in m-lines. What is complex here is that we are dealing with layered protocols, but SDP syntax pretends they are not. To address this fully, I think it is necessary to identify the protocol *stack* for each m-line, and then figure out which of those layers are shared by multiple m-lines. STUN is a middle layer in the stack, presumably shared by all the m-lines. Thanks, Paul > If endpoints want to assign "m=" lines representing other transport > protocols to a BUNDLE group, it MUST be documented how the de- > multiplexing is performed. There might also be a need for signalling > extensions in order for endpoints to exchange data needed for the de- > multiplexing. > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic >
- [MMUSIC] BUNDLE TEXT: De-mux procedures (June 19t… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June… Christer Holmberg
- Re: [MMUSIC] BUNDLE TEXT: De-mux procedures (June… Paul Kyzivat