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

Paul Kyzivat <> Fri, 24 May 2013 15:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D4CEC21F86BB for <>; Fri, 24 May 2013 08:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.295
X-Spam-Status: No, score=-0.295 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ogmoie3jNio7 for <>; Fri, 24 May 2013 08:11:28 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe14:43:76:96:62:32]) by (Postfix) with ESMTP id 9CE7C21F855F for <>; Fri, 24 May 2013 08:11:22 -0700 (PDT)
Received: from ([]) by with comcast id foZD1l0011c6gX853rBJwH; Fri, 24 May 2013 15:11:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([]) by with comcast id frBJ1l00h3ZTu2S3jrBJSr; Fri, 24 May 2013 15:11:18 +0000
Message-ID: <>
Date: Fri, 24 May 2013 11:11:17 -0400
From: Paul Kyzivat <>
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: "Dale R. Worley" <>
References: <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=q20121106; t=1369408278; bh=t73CNW5fY64Di5/6dlSzlZKzeZy+qVmewz3cVa/hs3U=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=qvopjmEcHRTUyKb2G5UerhqzIZ3kdUgu0siY6CJZstpeUtFqsO8v/ixm6NhyQIsHl YboiSqLvrAOvtNQWvheb/IAJCNRlYp3xfwmznfBWJU/sjbw6c2H5wHh6TzawPioOMM W1t7f+rKR2YIrxwxtXFDB7m5SEsJg9NlYbgy1thCcaYKWE64izF+nQdmLig5XdDUL+ 5xoMRX8Dzs1Se0HbdQV3avsuBvhbC+L4E/S+d6wJjPjC0KIuUArRemLD0l8dliYkLh PQUF42IzJHPAxWtFEcTt5BJFKLJdx9W3zeD1cGs7sqdm9xND5shokgRHX1zlNoPBxs HL226/UJGsQng==
Subject: Re: [MMUSIC] Associating packets with m-lines in a bundle
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 24 May 2013 15:11:34 -0000

On 5/23/13 6:07 PM, Dale R. Worley wrote:
>> From: Paul Kyzivat <>
>> 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.
> I agree.  I think there are non-legacy situations where this need may
> be relaxed, but all interoperation in legacy situations seems to
> require discerning the appropriate m= line so information in the SDP
> section can be used to identify the particular application processing
> stream.

??? There aren't any legacy interoperation situations for bundle.

>> [...] 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.
> I think that discarding them is the only workable approach.  There's
> no reason to assume that sending them to a default m= line would allow
> the upper level of demultiplexing to succeed.

My thought was that the receiver could signal a "default m-line". This 
would need to be done for each classification criterion. E.g.,

a=ssrc:* ...

would identify the m-line that should be used for otherwise unspecified 
ssrc values.


would identify the m-line to use for packets carrying no header 
extension or an undeclared value.

Any packet that still can't be classified after including such wildcards 
would be discarded.

I don't think such wildcarding makes any sense for PT.