IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions

Paul Kyzivat <pkyzivat@alum.mit.edu> Sat, 11 May 2013 00:40 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 C4E3E21F8FEB for <mmusic@ietfa.amsl.com>; Fri, 10 May 2013 17:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.168
X-Spam-Level:
X-Spam-Status: No, score=-0.168 tagged_above=-999 required=5 tests=[AWL=0.269, 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 XLZ15hK7UM+j for <mmusic@ietfa.amsl.com>; Fri, 10 May 2013 17:40:03 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id BEB8A21F9057 for <mmusic@ietf.org>; Fri, 10 May 2013 17:40:02 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta15.westchester.pa.mail.comcast.net with comcast id aQRD1l0040QuhwU5FQg2fP; Sat, 11 May 2013 00:40:02 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta02.westchester.pa.mail.comcast.net with comcast id aQg11l00p3ZTu2S3NQg1EQ; Sat, 11 May 2013 00:40:02 +0000
Message-ID: <518D9361.7060301@alum.mit.edu>
Date: Fri, 10 May 2013 20:40:01 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>
References: <7594FB04B1934943A5C02806D1A2204B1C36B485@ESESSMB209.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB1134DEF4B@xmb-aln-x02.cisco.com> <CABcZeBMrgaHGXFi_NRk+znsT-AGnRS5EDLgFhZgGA+VG81BhZw@mail.gmail.com> <CABkgnnW=4zNgauXc-=pv9j9zGdVntmb=K22wcRr77wfQc-6J3w@mail.gmail.com> <CABcZeBODcyo-JXqs6EZ-F5BY_TaM94+eu+UqNApFnTNjpehUzA@mail.gmail.com> <518D73E4.4090609@alum.mit.edu> <9D12C4E8-F7C1-4D32-A8AC-570AC86ACA23@vidyo.com>
In-Reply-To: <9D12C4E8-F7C1-4D32-A8AC-570AC86ACA23@vidyo.com>
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=1368232802; bh=Gw1yrBgvix1bRuWstprAnmoqKAGR+kT2vHhnFusURjQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=jP/E5OGihwo0wsW+SsSc0Rguk/0uje7N0Rw3zEOYTG6kbAiZ7w9Iwiieqfk5kxHYB /DR3F2a9GUr3g0S1HG4BNOr/+RHvy3l/2IDYG6r/88nOU4TNV1Rvd1FmjUg7RMqZSz Lmx6quN5VOW54I3ln57P+asz8e2sDKutdJbFv+5SeI0YjB4i3zDaGGN8CbZMHCGG/6 9UvBwgXxUvkdAwLBVHZa+Ud5bffnzp8BiUZsJ47FzSu2xWQiNIFi76Xg0VQnBI0QNi LzxzWzkQF9BkMzDExkrNUOaNkRiG6EClu58Ax68M2aMcRyFUDznDxS8aOxoL+6tgRb IRQuozqS6bNrA==
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE Weekly Summary: Assumptions
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: Sat, 11 May 2013 00:40:08 -0000

On 5/10/13 6:44 PM, Jonathan Lennox wrote:

>>>     I struggled to find it too.  It's in 9.2:
>>>
>>>         SIP entities refuse media streams by setting the port to zero in the
>>>         corresponding "m" line. "a=group" lines MUST NOT contain
>>>         identification-tags that correspond to "m" lines with the port
>>>     set to
>>>         zero.
>>>
>>>
>>> This feels like something we could relax for the offer.
>>
>> We could relax it. The question is if the change will break any existing
>> use. That is a hard question to answer.
>
> We could say that whether it's valid must be defined by the group semantic, and for all existing group semantics it's not.

WFM

v2.30.2 | Report a Bug | By Email | System Status