[MMUSIC] Associating packets with m-lines in a bundle

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 23 May 2013 18:50 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 9B15E21F942D for <mmusic@ietfa.amsl.com>; Thu, 23 May 2013 11:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.007
X-Spam-Level:
X-Spam-Status: No, score=0.007 tagged_above=-999 required=5 tests=[AWL=-0.156, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_14=0.6, 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 JlGKnIK90qaK for <mmusic@ietfa.amsl.com>; Thu, 23 May 2013 11:50:15 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 9803121F9608 for <mmusic@ietf.org>; Thu, 23 May 2013 11:26:30 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta13.westchester.pa.mail.comcast.net with comcast id fQXR1l0051YDfWL5DWSVSL; Thu, 23 May 2013 18:26:29 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id fWSV1l00c3ZTu2S3gWSVJz; Thu, 23 May 2013 18:26:29 +0000
Message-ID: <519E5F54.3000806@alum.mit.edu>
Date: Thu, 23 May 2013 14:26:28 -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: IETF MMUSIC WG <mmusic@ietf.org>
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=1369333589; bh=+ybxvzpTN9QDqwDRWv4/EJRu/R2QJN0rsL082EChGvE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=YHMRcrWW5KOqoMS7PpRpc/K0QtY2nhwitZZ2Kdvudtd3V3AJz+DLGx2tUPfmE/bXi 1qysYka9VoirUnEZssKMm0s3a7rcm3wSUKa+ln66LBryfFX8Y6cT8MBeMIr+RBAOcQ 41JbWXixg0CLB0HfZ4t6rEpNmWSgIQLLBTnCRLdsncf3AI1ySCx70XpFaMT3CrUF1c ROzGz1ZFiEPCz7MqTSsBA5NvEAHoJh9pYzFEMLTu7rkAAGJR9a3MiyufudYFIX+nJc pbByDBm/xiY5hzmc+nBckokqy0Wmty2q/P/4HTzUaU3l0+x0o4QL++/WmxXQVqR/YS XcWysCa6Y5SSA==
Subject: [MMUSIC] Associating packets with m-lines in a bundle
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, 23 May 2013 18:50:31 -0000

After all the discussion in the meeting today, I thought it would be 
good to unwind all the indenting and start a new thread on one issue 
that is part of the "demux" problem:

IMO the following should obviously be a truism. I want to know if all agree.

If an O/A exchange negotiates a bundle with multiple m-lines,
then attributes in those m-lines and the associated media sections must 
provide sufficient information to associate each incoming packet on the 
5-tuple to exactly *one* of those m-lines.

(If it doesn't, then there was no point in including those m-lines in 
the bundle.)

For instance a=ssrc, if unique to one m-line, can bind packets with that 
SSRC to the m-line.

If a property such as SSRC is used this way, then there is the 
possibility of receiving packets that don't match any of the m-lines. I 
think we ought to address that, by defining some syntax to specify what 
to do with packets that don't match any m-line. This might be to specify 
one m-line as the default, or that packets that don't match be discarded.

This is not the complete demux problem. Added data and logic may be 
needed to decide what application processing each of those packets may 
require. Once a packet has been associated with an m-line, then some of 
the attributes associated with that m-line may provide may provide 
further information about how to decide how to process the packet. There 
can also be information that comes via other means to qualify packet 
processing.

	Thanks,
	Paul