IETF Logo Mail Archive

Re: [MMUSIC] BUNDLE goes UP: Do we need port zero for bundle-only m- lines?

"Parthasarathi R" <partha@parthasarathi.co.in> Thu, 15 August 2013 16:48 UTC

Return-Path: <partha@parthasarathi.co.in>
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 91EF711E81E4 for <mmusic@ietfa.amsl.com>; Thu, 15 Aug 2013 09:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 53swX3EOAA63 for <mmusic@ietfa.amsl.com>; Thu, 15 Aug 2013 09:48:32 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us1.mailhostbox.com [69.93.141.231]) by ietfa.amsl.com (Postfix) with ESMTP id D695811E81D9 for <mmusic@ietf.org>; Thu, 15 Aug 2013 09:48:32 -0700 (PDT)
Received: from userPC (unknown [122.172.186.109]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id F29AB1908180; Thu, 15 Aug 2013 16:48:28 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1376585311; bh=enkJ3M7ctteNi/SdfArKplA43YPGQTkQVDooolA74uc=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=Ic8F2fFIexU5HUPJqz4+fD0NPrJ8LJE7HMUHsIxii5GYntd+bBQjQ546kl+14tqwS gCWE4zdhcJ2tYDuP1jT76pIMBSmXaAUuCvTwgxpD1/AMY3KVs1Z9K+rJPljEc5GYW9 jsmpAVsxpCnGCzdiHFJ4/9RE/F8Agbcodvi5bHDI=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: "'Cullen Jennings (fluffy)'" <fluffy@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1C421C80@ESESSMB209.ericsson.se> <9AA75667-A597-4EB1-87B4-FA79A2F35C3C@oracle.com>, <5203D7E7.4070207@nostrum.com> <7594FB04B1934943A5C02806D1A2204B1C422522@ESESSMB209.ericsson.se> <1687A002-7B01-4468-85DD-FF19BDFDAE14@oracle.com> <5203EB64.70605@nostrum.com> <65BCA443-98E1-4843-9522-248DD5B4ED68@oracle.com> <5203F37A.8030204@nostrum.com> <33EF0E51-D7E2-42BC-98AA-1A96E2E3CB4D@oracle.com> <5203F4D8.9040904@nostrum.com> <9BB1DB2F-32DB-453E-BAEF-3E600EAD3413@oracle.com> <5204075B.1080108@nostrum.com> <A2E26DB5-CF47-44DF-8779-D470280977B6@oracle.com> <009d01ce951b$d52aa340$7f7fe9c0$@co.in> <C5E08FE080ACFD4DAE31E4BDBF944EB113678F9D@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB113678F9D@xmb-aln-x02.cisco.com>
Date: Thu, 15 Aug 2013 22:18:19 +0530
Message-ID: <001b01ce99d7$425295d0$c6f7c170$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHOmHzRKhPenv+lz0620AA+309SKpmWeNgw
Content-Language: en-us
X-CTCH-RefID: str=0001.0A0C0201.520D065F.008B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules:
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.138
Cc: 'mmusic WG' <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE goes UP: Do we need port zero for bundle-only m- lines?
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, 15 Aug 2013 16:48:37 -0000

Cullen,

The violation of RFC 3264 happens as follows:

1) In case m line has port "0" and bundle-only attribute exists in the
Answer, it is possible to interpret by the offerer in two ways as
	a) Answer is rejected by the answerer wherein bundle-only attribute
has to be ignored. This in inline with RFC 3264. Here, there is a need for
extra offer/answer to confirm bundle is supported or not.
	b) Answer is rejected by the answerer wherein bundle-only attribute
is supported. Here, there is no need of one more offer/answer but the
interop issues with SIP entities will happen.

2) There are middle-boxes which provides QoS based on the current
offer/answer. In case of WebRTC, the simplified topology shall be 

 "Browser----SIP server-----Browser/SIP UA"

In these scenario, SIP server initiates Qos based on offer/answer exchange
between browsers. These SIP servers will fail in case an optional attribute
like "bundle-only" updates RFC 3264 behavior like offer with port 0 and
answer with proper port.

Thanks
Partha

> -----Original Message-----
> From: Cullen Jennings (fluffy) [mailto:fluffy@cisco.com]
> Sent: Wednesday, August 14, 2013 4:59 AM
> To: Parthasarathi R
> Cc: mmusic WG
> Subject: Re: [MMUSIC] BUNDLE goes UP: Do we need port zero for bundle-
> only m- lines?
> 
> 
> On Aug 9, 2013, at 10:16 AM, Parthasarathi R
> <partha@parthasarathi.co.in> wrote:
> 
> > This approach also
> > Violates Sec 8.2 of RFC 3264 requirement
> >
> > " A stream that is offered with a port of zero MUST be marked with
> port
> >   zero in the answer."
> 
> No this would not be violated. When one side was 3264 only, this would
> still happen. But when both sides support bundle-only, then this
> restriction no longer holds. The bundle draft as an extension to 3264
> needs to clearly define all that.

v2.23.0 | Report a Bug | By Email