IETF Logo Mail Archive

Re: [MMUSIC] Transport tags

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Fri, 13 January 2017 14:28 UTC

Return-Path: <eckelcu@cisco.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 B93B012963A for <mmusic@ietfa.amsl.com>; Fri, 13 Jan 2017 06:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TEsO5YsMt2X for <mmusic@ietfa.amsl.com>; Fri, 13 Jan 2017 06:28:26 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E41F12961A for <mmusic@ietf.org>; Fri, 13 Jan 2017 06:28:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2694; q=dns/txt; s=iport; t=1484317706; x=1485527306; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=72RAvMQZw5mrB4m0szVDe5Wdze5sfy48xNq+TbezcOs=; b=f7oUV1qTgyteyHOEhMcmWXf2kwNQMECVUUwKP+E2Uhtu73sZCPXBWi1W bszYbcxulDU0Fvq+B918GdPoHPtJnqSpO1YxOO+bbS2UM8iqZRV0kd5QX U3E8/40hwG6kN0zM/XhxbrmLH6O3qKLUHp3NSEnp72XmnPNpVdl3F4P/x 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DMAgBM43hY/4wNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgz8BAQEBAR+BaJ9ukxuCD4INhiICghJBEgECAQEBAQEBAWMohGkBAQEDAQxtBQkCAgEIGCcHGxcUEQIEDgWIewiyeYoLAQEBAQEBAQEBAQEBAQEBAQEBAQEBHQWIQoJfhEaDM4IxBYh4hmeLUwGRWJBtkmQBJgwlgUQVSgGGH3OIZgEBAQ
X-IronPort-AV: E=Sophos;i="5.33,221,1477958400"; d="scan'208";a="372363083"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Jan 2017 14:28:25 +0000
Received: from XCH-RCD-018.cisco.com (xch-rcd-018.cisco.com [173.37.102.28]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v0DESPCj016585 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 13 Jan 2017 14:28:25 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-018.cisco.com (173.37.102.28) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 13 Jan 2017 08:28:24 -0600
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Fri, 13 Jan 2017 08:28:24 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: [MMUSIC] Transport tags
Thread-Index: AQHSbE3p2SC5GZHiXUyd4kk6fM3mOqEzs4yAgACvV4CAAHqSgIAA1ReAgAADMACAAAZqgIAABU+AgAAExICAAAhlgIAArViA///+Bo4=
Date: Fri, 13 Jan 2017 14:28:24 +0000
Message-ID: <DA5874F4-F20D-4C2B-A5B9-32688EAAA34C@cisco.com>
References: <CAD5OKxvEqvah+ZJdPKJdGmKob84X8WaCqKQ2GEiatVbOSmEjDw@mail.gmail.com> <6A083F67-4ECB-4703-A881-EB2F074F309E@cisco.com> <CAD5OKxt9iVE8Sgax5rjzwyhNCupeXLCVDjz3iMU+A3eTjAnGoA@mail.gmail.com> <E0242B2A-4F7E-4915-8C73-ED68AC69846A@cisco.com> <7594FB04B1934943A5C02806D1A2204B4BF6F650@ESESSMB209.ericsson.se> <CAD5OKxu4nS4naza=f4Y0=TZJ3T5Cwc_XtsoVmP_WbxuFWiN0iA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BF6F72C@ESESSMB209.ericsson.se> <CAD5OKxuyzJP_pFAWVnMMBDATakZOqPKE0ujyXgSSPXRjhASsuQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4BF6F797@ESESSMB209.ericsson.se> <CAD5OKxsH=AhhwxAWiEcwmtUUe-NqEBwmc23tUPm1VVbSCPBWAQ@mail.gmail.com>, <0e376a55-f20b-b589-104a-6e34df5767e9@ericsson.com>
In-Reply-To: <0e376a55-f20b-b589-104a-6e34df5767e9@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ousg0rxfbFKKzAcmli1-fFWbvVk>
Cc: Paul Kyzivat <paul.kyzivat@comcast.net>, "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Transport tags
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 13 Jan 2017 14:28:28 -0000

It is possible and people already do use UDP/TLS/BFCP with ICE and without any TCP candidates. 

Cheers,
Charles

> On Jan 13, 2017, at 12:35 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
> 
> Hi,
> 
> A question, is the UDP/DTLS/BFCP only used with ICE, or are they also used without ICE support. I wonders how this relates to the discussion that the UDP/TCP destinction becomes mote when one actually are doing ICE/DTLS/BFCP, i.e. use ICE to agree on a datagram capable transport and then puts DTLS/BFCP over it, independent on what transport type the arrived candidate pairs are on.
> 
> Is there a point to the BFCP usages to actually be explicit that we one only want to use ICE negotiated DTLS secured BFCP, and thus should have a PROTO value for that, i.e. ICE/DTLS/BFCP?
> 
> Note, this is a question, not an actual proposal. Just an exploration so that you who use the protocol can consider if it makes sense.
> 
> Cheers
> 
> Magnus
> 
>> Den 2017-01-12 kl. 23:15, skrev Roman Shpount:
>> On Thu, Jan 12, 2017 at 4:45 PM, Christer Holmberg
>> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
>> wrote:
>> 
>>    >I do not think TCP/DTLS/BFCP is defined anywhere, so it does not
>>    have to be backwards compatible. We are not changing the proto
>>    value, we should >define a new one and explain how it works. This
>>    leaves TCP/BFCP and TLS/BFCP as they were previously defined and
>>    simply states that these transports >cannot be used with ICE. Only
>>    UDP/DTLS/BFCP and TCP/DTLS/BFCP can be used with ICE, with ICE not
>>    supported for all the other BFCP flavors.
>> 
>>    __
>> 
>>    __ __
>> 
>>    Ok, so TCP/BFCP and TLS/BFCP will still be kept in 4583bis, and
>>    should be used when ICE is not used?____
>> 
>> 
>> 
>> TCP/BFCP, TLS/BFCP and UDP/BFCP will be kept in 4583bis and can only be
>> used when ICE is not used. UDP/DTLS/BFCP and TCP/DTLS/BFCP are two
>> transport that can be used with or without ICE.
>> 
>> Regards,
>> _____________
>> Roman Shpount
>> 
> 
> 
> -- 
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email