Re: [MMUSIC] What is an m-line?

Martin Thomson <martin.thomson@gmail.com> Mon, 13 May 2013 20:47 UTC

Return-Path: <martin.thomson@gmail.com>
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 AD70B21F944F for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 13:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 UhVhhopSSeGJ for <mmusic@ietfa.amsl.com>; Mon, 13 May 2013 13:47:15 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0A17F21F9003 for <mmusic@ietf.org>; Mon, 13 May 2013 13:47:14 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id n12so6562021wgh.13 for <mmusic@ietf.org>; Mon, 13 May 2013 13:47:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=02tptXlxdya6E6x+fzJ5QkTr9kCcGPe/xairS8wj08w=; b=XyBYKNXvD+2kh4OgrmtB2A6aZpK3OWyaZsk5sYiGhpQcGSMFdh+s4chocioWaZ/Z2g 7H0Is6bYdD+l6jxDgoCqth0sR08hnlY9xCy4bTI/cfDlsNHbdjEjiU65IETlEYgADcb0 MPxxT9o2Gyf35R15uy/tUuZGll/2/LwGwrTEf8ZFDCyN/bcqh5PSvqRimY0WD5m/m8z/ tvw6AfUdYmjyekpD0HOT2FWt3hxiL64s3OYzpPK5koOqsb+15lbEY6AWUpfbItfhsScC /Pj7oxHAymwgLZqj4fpt7FB0XHwQYdgDd7+S019to7XY7uKsQ1JIfiq7yQm++HBa4vPV ioSg==
MIME-Version: 1.0
X-Received: by 10.180.198.49 with SMTP id iz17mr22314934wic.19.1368478034182; Mon, 13 May 2013 13:47:14 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Mon, 13 May 2013 13:47:14 -0700 (PDT)
In-Reply-To: <BLU169-W783DE3B448E226C811D1F393A00@phx.gbl>
References: <CABkgnnWPWMLEecfqksGJrWrqvsu44gts48igUiLyiVV0iPhwQQ@mail.gmail.com> <BLU169-W783DE3B448E226C811D1F393A00@phx.gbl>
Date: Mon, 13 May 2013 13:47:14 -0700
Message-ID: <CABkgnnXtfPP8ufdHmvc+ELYYcgiK3MCVyyT079Zerw3jZoXjuQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] What is an m-line?
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: Mon, 13 May 2013 20:47:15 -0000

On 13 May 2013 12:14, Bernard Aboba <bernard_aboba@hotmail.com> wrote:
> [...] Approach #1 is also
> consistent with the multicast scenarios envisaged in the early days of SDP,
> where multiple SSRCs could send to the same multicast address and port.


Oops, I meant to try to head this line of reasoning off.  Let's talk
about offer/answer only.

I'd rather not boil two oceans.