Re: [MMUSIC] Bundling data channel and RTP? - Text proposal - Second try
"Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com> Mon, 15 June 2015 14:21 UTC
Return-Path: <albrecht.schwarz@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3261B2DDB for <mmusic@ietfa.amsl.com>; Mon, 15 Jun 2015 07:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FeM-w1DKKv8i for <mmusic@ietfa.amsl.com>; Mon, 15 Jun 2015 07:21:19 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1F371B2DBE for <mmusic@ietf.org>; Mon, 15 Jun 2015 07:20:50 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 700B4FF96BAB0; Mon, 15 Jun 2015 14:20:46 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t5FEKTIm013533 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Jun 2015 16:20:42 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.123]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Mon, 15 Jun 2015 16:19:43 +0200
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "GUBALLA, JENS (JENS)" <jens.guballa@alcatel-lucent.com>, mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Bundling data channel and RTP? - Text proposal - Second try
Thread-Index: AdClBipG7UfqYMuMRya9DuFvp6kbcwCYWjsAAADdq2AAAogRAA==
Date: Mon, 15 Jun 2015 14:19:42 +0000
Message-ID: <786615F3A85DF44AA2A76164A71FE1AC7AD94962@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D8BF21F@ESESSMB209.ericsson.se> <547EE95EB794FD4DB8062F7A4C86D0BC4A3677BA@FR712WXCHMBA13.zeu.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D8D881E@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D8D881E@ESESSMB209.ericsson.se>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/HoIfsGJbnQ8614rgvo5RGALh0Ls>
Cc: "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Bundling data channel and RTP? - Text proposal - Second try
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 15 Jun 2015 14:21:20 -0000
Hello Christer, wrt > While I do realize that "connection" is not suitable for connectionless protocols, in my opinion it was a mistake to use "association", because it has caused lots of confusion. I often get questions on what the difference between a DTLS association and DTLS connection is :) 1st) There is not any contradiction between "connection" and "connectionless" (according to the basic reference model for communicaions (X.200)). Id est, a (N)-connection is either operated in communication mode (§ 5.3.3/X.200) "connection oriented" (= "connection mode" § 5.3.3.2/X.200) or "connectionless" (§ 5.3.3.3/X.200). => no contradiction ("there are connectionless (N)-connections ...") 2nd) DTLS as protocol belongs to category connection-oriented, not connectionless. The (DTLS)-connection is of type connection-oriented. Furthermore: that's the reason why there are also "UDP connections" despite their connectionless nature. Regards, Albrecht -----Original Message----- From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Montag, 15. Juni 2015 15:07 To: GUBALLA, JENS (JENS); mmusic Cc: pkyzivat@alum.mit.edu Subject: Re: [MMUSIC] Bundling data channel and RTP? - Text proposal - Second try Hi Jens, Thanks for your feeback! See inline. >> ------------- >> >> 12. DTLS Considerations >> >> One or more media streams within a BUNDLE group might use the >> Datagram Transport Layer Security (DTLS) protocol [RFC6347] in order >> to encrypt the data, or to negotiate encryption keys if another >> encryption mechanism is used to encrypt media. >> >> When DTLS is used within a BUNDLE group, the following rules apply: >> >> o There can only be one DTLS association [RFC6347] associated with >> the BUNDLE group; > > [JG] I prefer the term "DTLS connection" over "DTLS association" > because I am not aware that the latter term is defined anywhere in the > scope of (D)TLS. > RFC6347 is using the terms "connection" and "association" > interchangeably without any definition. On the other hand the term > "connection" is at least present in the glossary section of RFC5246. RFC 5763 and RFC 5764, both related to DTLS-SRTP, use "association": "We use the term "association" to refer to a particular DTLS cipher suite and keying material set that is associated with a single host/ port quartet. The same DTLS/TLS session can be used to establish the keying material for multiple associations." (RFC 5763) "Each DTLS-SRTP session contains a single DTLS association (called a "connection" in TLS jargon),..." (RFC 5764) While I do realize that "connection" is not suitable for connectionless protocols, in my opinion it was a mistake to use "association", because it has caused lots of confusion. I often get questions on what the difference between a DTLS association and DTLS connection is :) >> o Each usage of the DTLS association within the BUNDLE group MUST >> use the same mechanism for determining which endpoints (the >> offerer or answerer) becomes DTLS client and DTLS server; and >> >> o If the DTLS client supports DTLS-SRTP [RFC5764] it MUST include >> the 'use_srtp' extension [RFC5764] in the DTLS ClientHello message >> [RFC5764], The client MUST include the extension even if the usage >> of DTLS-SRTP is not negotiated as part of the session. > > [JG] I believe here "session" is referring to "SIP session", not to > "DTLS session", right? Should be explicitly stated in any case. See below. >> NOTE: The inclusion of the 'use_srtp' extension during the initial >> DTLS handshake ensures that a DTLS renegotiation will not be required >> in order to include the extension, in case DTLS-SRTP encrypted media >> is added to the BUNDLE group later during the session. > > [JG] "Session": Same comment as above. It's not DTLS, but it can of course be something else than SIP. I guess we could say something like "multimedia session", "SDP session", or something... Regards, Christer
- Re: [MMUSIC] Bundling data channel and RTP? - Tex… Christer Holmberg
- Re: [MMUSIC] Bundling data channel and RTP? - Tex… GUBALLA, JENS (JENS)
- Re: [MMUSIC] Bundling data channel and RTP? - Tex… Christer Holmberg
- Re: [MMUSIC] Bundling data channel and RTP? - Tex… Schwarz, Albrecht (Albrecht)
- Re: [MMUSIC] Bundling data channel and RTP? - Tex… Christer Holmberg