IETF Logo Mail Archive

Re: [MMUSIC] RE : I-D Action: draft-ietf-mmusic-sdp-miscellaneous-caps-04.txt

Andrew Allen <aallen@blackberry.com> Thu, 14 March 2013 18:10 UTC

Return-Path: <prvs=17855228f7=aallen@blackberry.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 9665611E81AB for <mmusic@ietfa.amsl.com>; Thu, 14 Mar 2013 11:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ww1vehBV84b4 for <mmusic@ietfa.amsl.com>; Thu, 14 Mar 2013 11:10:40 -0700 (PDT)
Received: from mhs061cnc.rim.net (mhs061cnc.rim.net [208.65.73.35]) by ietfa.amsl.com (Postfix) with ESMTP id 72F4211E8144 for <mmusic@ietf.org>; Thu, 14 Mar 2013 11:10:40 -0700 (PDT)
X-AuditID: 0a412830-b7ef86d00000339d-51-51421295e823
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by mhs061cnc.rim.net (SBG) with SMTP id CC.0E.13213.59212415; Thu, 14 Mar 2013 13:10:30 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.02.0328.009; Thu, 14 Mar 2013 13:10:29 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "jonathan@vidyo.com" <jonathan@vidyo.com>, "fandreas@cisco.com" <fandreas@cisco.com>
Thread-Topic: [MMUSIC] RE : I-D Action: draft-ietf-mmusic-sdp-miscellaneous-caps-04.txt
Thread-Index: AQHOILR4FRB+udTQGku/nF8/mU+ospillH4AgAAMq4CAAADiAIAABM+AgAAiZgCAAAZvAP//rVJA
Date: Thu, 14 Mar 2013 18:10:29 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338D2AE5E@XMB104ADS.rim.net>
In-Reply-To: <DBB452AD-7443-4B45-A706-BC79442979BB@vidyo.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.67.110.253]
Content-Type: multipart/alternative; boundary="_000_BBF5DDFE515C3946BC18D733B20DAD2338D2AE5EXMB104ADSrimnet_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDKsWRmVeSWpSXmKPExsXC5ZyvrTtNyCnQYMY/Lov3F3Qt9i8+z2wx dfljFovDb5+yO7B4TPm9kdVjyZKfTB4tz06yebQ9u8MewBLVwGiTlFhSFpyZnqdvZ5OYl5df kliSqpCSWpxsq+STmp6YoxBQlFmWmFyp4JJZnJyTmJmbWqSkkJliq2SipFCQk5icmpuaV2Kr lFhQkJqXomTHpYABbIDKMvMUUvOS81My89JtlTyD/XUtLEwtdQ2V7HQTOnkyfvw9xVLQ41Ux e/NsxgbGFo8uRk4OCQETiZdrt7JD2GISF+6tZwOxhQTamCQudAp2MXIB2ZsZJe5NOMgIkmAT 0JLYf3g6E4gtIhAlcb3rJjOIzSyQIXG2bRYLiC0sECHxZvVFFoiaSIl772ewwtQvOLYczGYR UJXYevwfmM0r4CHx8fxDMJtTwFZi44s1YAcxCshK7D57nQlivrjErSfzmSAOFZBYsuc8M4Qt KvHyMcQcCQFFib97v7NC1OdLdGxaxwwxX1Di5MwnLBMYRWYhGTULSdksJGWzGDmA4poS63fp Q5QoSkzpfsgOYWtItM6Zy44svoCRfRWjYG5GsYGZYXJesl5RZq5eXmrJJkZQinHUMNjB+P69 xSFGAQ5GJR5ez4WOgUKsiWXFlbmHGCU4mJVEeHf9BQrxpiRWVqUW5ccXleakFh9iDAIG0ERm Ke7kfGD6yyuJNzYwIJKjJM4rEigaKCSQDkxi2ampBalFMEOZODhBlnJJiRQDU1FqUWJpSUY8 KGHGFwNTplQDozZTnu3PNL7fooG5ejPDtm69r+Tx78yMOUx18rOXF38uK3eSrNjVvj54br+a sfmcr3ovDb362PTiJs/i36mkaLovnS9vebTfnHXLZp3Sz3t4cf/TV15M8ad77jdP/1PoMftF 88SurA8uIvWO82wyy+fmhm3Ol9Dq/RCW7nStzaG8K7lg9+sOJZbijERDLeai4kQAcO5L+X8D AAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] RE : I-D Action: draft-ietf-mmusic-sdp-miscellaneous-caps-04.txt
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, 14 Mar 2013 18:10:41 -0000

My understanding also was that we agreed that CCAP was not an alternative to ICE.


From: Jonathan Lennox [mailto:jonathan@vidyo.com]
Sent: Thursday, March 14, 2013 01:06 PM Central Standard Time
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>; Andrew Allen; mmusic@ietf.org <mmusic@ietf.org>
Subject: Re: [MMUSIC] RE : I-D Action: draft-ietf-mmusic-sdp-miscellaneous-caps-04.txt


On Mar 14, 2013, at 1:43 PM, Flemming Andreasen wrote:

On 3/14/13 11:40 AM, mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> wrote:
Re-,

What is important is the quality of produced documents. The content of the document is not frozen and unless I'm mistaken there is not IETF LC.

Correct.
What I understand from the text in the draft is: ccap is allowed to signal an IPv4@ and IPv6@ if ICE is not supported.

ccap is not prohibited from doing so in the absence of ICE, however as explained in the document
1) When the IETF Standard Track mechanism ICE is available, ccap MUST NOT signal an IPv4/IPV6 address alternative.
2) The draft does (intentionally) not provide a full solution for negotiating alternative IP-addresses since we have a Standards Track mechanism for doing so (ICE).

Hi, Fleming --

My understanding of the WG consensus -- and my interpretation of the text in the draft -- was stronger than this: ccap MUST NOT be used for the kinds of alternatives ICE can express, whether or not ICE is actually being used in a particular offer/answer.

If we're getting divergent interpretations of this document, we probably do need to update its text.

--
Jonathan Lennox
jonathan@vidyo.com<mailto:jonathan@vidyo.com>



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

v2.23.0 | Report a Bug | By Email