IETF Logo Mail Archive

Re: [MMUSIC] Transport tags

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Thu, 12 January 2017 15:52 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 B1106129469 for <mmusic@ietfa.amsl.com>; Thu, 12 Jan 2017 07:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 muakg0blB_5j for <mmusic@ietfa.amsl.com>; Thu, 12 Jan 2017 07:51:59 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE12412946A for <mmusic@ietf.org>; Thu, 12 Jan 2017 07:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22218; q=dns/txt; s=iport; t=1484236318; x=1485445918; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+BUrtpA2TRlJ6jcXyOvHgrdInrUhopUwoLdWbo3ZocA=; b=Hj4uy3okVhTsKHLBY1L0En5bnpf3Vgw4Oz+UzKvCbMmRDUzyGmeiWZHU cS2wuFoj5k6ZbR8JGLTeLcfYFkaQ4mTFxxpMNysrUhi7YS+1tRhE9bou2 gBwKF4fHLMsSir9H49Fi+TGM8Q6dCk6DVzaUfOB9GkBPc9uYbclCtaFbt s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AbAQCtpXdY/5tdJa1dGQEBAQEBAQEBAQEBBwEBAQEBgnJKAQEBAQEfX4EJB4MDRooIkhWTG4IPgg0qhXgCGoFnPxQBAgEBAQEBAQFjKIRpAQEBBAwXVg4CAgEGAhEDAQIoAwICAhkXFAkIAgQOBYkADpJvnU6CJSuJaQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFBYhCCIJXhF0JFoJQLYIxBYh2jDKGBAGGWop7CpBgkmMBHziBRBU6EAGGHnOHWYENAQEB
X-IronPort-AV: E=Sophos;i="5.33,219,1477958400"; d="scan'208,217";a="191773135"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jan 2017 15:51:57 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v0CFpvPI011103 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Jan 2017 15:51:57 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 12 Jan 2017 09:51:56 -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; Thu, 12 Jan 2017 09:51:56 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Transport tags
Thread-Index: AQHSbE3p2SC5GZHiXUyd4kk6fM3mOqEzs4yAgACvV4CAAHqSgA==
Date: Thu, 12 Jan 2017 15:51:56 +0000
Message-ID: <E0242B2A-4F7E-4915-8C73-ED68AC69846A@cisco.com>
References: <CAD5OKxvEqvah+ZJdPKJdGmKob84X8WaCqKQ2GEiatVbOSmEjDw@mail.gmail.com> <6A083F67-4ECB-4703-A881-EB2F074F309E@cisco.com> <CAD5OKxt9iVE8Sgax5rjzwyhNCupeXLCVDjz3iMU+A3eTjAnGoA@mail.gmail.com>
In-Reply-To: <CAD5OKxt9iVE8Sgax5rjzwyhNCupeXLCVDjz3iMU+A3eTjAnGoA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.182.35]
Content-Type: multipart/alternative; boundary="_000_E0242B2A4F7E49158C73ED68AC69846Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KLGMQ_BwlyiMNa0wYDKxgW7__tI>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <paul.kyzivat@comcast.net>
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: Thu, 12 Jan 2017 15:52:02 -0000

Works for me.

Cheers,
Charles

From: Roman Shpount <roman@telurix.com>
Date: Wednesday, January 11, 2017 at 4:33 PM
To: Charles Eckel <eckelcu@cisco.com>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Paul Kyzivat <paul.kyzivat@comcast.net>, "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Transport tags

I guess BFCP will need TCP/DTLS/BFCP added to the list.

Should we correct draft-ietf-mmusic-sctp-sdp draft to match and change UDP/DTLS/SCTP to UDP/TLS/SCTP?

Regards,

_____________
Roman Shpount

On Wed, Jan 11, 2017 at 5:05 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com<mailto:eckelcu@cisco.com>> wrote:
Here is what we have for BFCP in https://tools.ietf.org/html/draft-ietf-bfcpbis-rfc4583bis-16#section-13:

                       +--------------+------------+
                       | Value        | Reference  |
                       +--------------+------------+
                       | TCP/BFCP     | [RFC XXXX] |
                       | TCP/TLS/BFCP | [RFC XXXX] |
                       | UDP/BFCP     | [RFC XXXX] |
                       | UDP/TLS/BFCP | [RFC XXXX] |
                       +--------------+------------+

Cheers,
Charles

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on behalf of Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Date: Wednesday, January 11, 2017 at 1:01 PM
To: Magnus Westerlund <magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com>>
Cc: Paul Kyzivat <paul.kyzivat@comcast.net<mailto:paul.kyzivat@comcast.net>>, "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Subject: [MMUSIC] Transport tags

What should we use for the new protocols that we are defining?

Should it be UDP/TLS/SCTP or UDP/DTLS/SCTP?
Should it be UDP/TLS/BFCP or UDP/DTLS/BFCP?

I would like to see some consistency here.

Regards,
_____________
Roman Shpount

On Wed, Jan 11, 2017 at 3:30 AM, Magnus Westerlund <magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com>> wrote:
Den 2017-01-10 kl. 19:08, skrev Roman Shpount:
P.S. In the quoted text someone mentioned "UDP/TLS/RTP/SAVPF", should it
be "UDP/DTLS/RTP/SAVPF"?

No, actually UDP/TLS/RTP/SAVPF is what is registered for DTLS-SRTP over UDP with RTP SAVPF profile. See [RFC5764]. The "UDP/DTLS/RTP/SAVPF" is not registered.

So the alternatives for the dependency of default candidate protocol type in your proposal would be:

UDP: "UDP/TLS/RTP/SAVPF"
TCP: "TCP/DTLS/RTP/SAVPF"


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287<tel:%2B46%2010%207148287>
Färögatan 6                 | Mobile +46 73 0949079<tel:%2B46%2073%200949079>
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com>
----------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email