IETF Logo Mail Archive

[MMUSIC] connection:new with DTLS

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 27 March 2015 17:53 UTC

Return-Path: <christer.holmberg@ericsson.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 EAA841A0368 for <mmusic@ietfa.amsl.com>; Fri, 27 Mar 2015 10:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 pOnQeVYoKIWl for <mmusic@ietfa.amsl.com>; Fri, 27 Mar 2015 10:53:37 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DD241A7008 for <mmusic@ietf.org>; Fri, 27 Mar 2015 10:53:35 -0700 (PDT)
X-AuditID: c1b4fb30-f79996d000006ebb-7c-5515991d0863
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 56.AC.28347.D1995155; Fri, 27 Mar 2015 18:53:33 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.236]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0210.002; Fri, 27 Mar 2015 18:53:33 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic (E-mail)" <mmusic@ietf.org>
Thread-Topic: connection:new with DTLS
Thread-Index: AdBotuiqe7drEiJIQAWagp/5LNYCqA==
Date: Fri, 27 Mar 2015 17:53:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D781C55@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D781C55ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+Jvja7sTNFQg03PVCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujOdXV7MUTLevOLBLrYFxjXkXIyeHhICJxLl7H9ggbDGJC/fW g9lCAkcYJS7ej+9i5AKylzBKLOxuY+xi5OBgE7CQ6P6nDVIjIqAu0bq5jxXEFhZQlJg48yM7 RFxN4tHCLlYIW0/iR/NSJhCbRUBVYnbLeWYQm1fAV+JFSydYDSPQ3u+n1oDVMAuIS9x6Mp8J 4h4BiSV7IOolBEQlXj7+xwphK0msPbydBaI+X+LYucNsEDMFJU7OfMIygVFoFpJRs5CUzUJS BhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxihanFiflphsZ6aUWZSYXF+fn6eWllmxi BMbDwS2/DXYwvnzueIhRgINRiYd3w3GRUCHWxLLiytxDjNIcLErivHbGh0KEBNITS1KzU1ML Uovii0pzUosPMTJxcEo1MLZv3/s4601jb1RzdNPaNz7TWB5y9enyG02+3/TfYGtabMKfJXy/ Vk6Lu2zidHdRS+a+mfPfHXz+t/KSBH/2t8oHaTmu4V0r5h35Jzu3fpdiKaPQ1ALmBOZDCkUR J6L47/I6d65dbHX4hePZy6ISXyezNy35cm7qf+l15RsOzWCfOXF1Qkb17UlKLMUZiYZazEXF iQCHwdTraAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/JVOAfU7ILsnJT1ZgFKZw3ED-PmQ>
Subject: [MMUSIC] connection:new with DTLS
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: Fri, 27 Mar 2015 17:53:40 -0000

Hi,

As Justin mentioned during the 2nd MMUSIC session, RFC 5763 forbids usage of 'connection:new' for DTLS-SRTP.

However, draft-sctp-sdp DOES allow it.


-          In case of plain SCTP, there is no DTLS (and, there are no ICE procedures for SCTP transport), so that is fine.


-          In case of SCTP/DTLS, I guess re-establishment of the SCTP association would also impact the overlying DTLS association. But, again, there are no ICE procedures for SCTP transport, so that should be fine.


-          In case of UDP/DTLS/SCTP I guess one can re-establish the SCTP association without impacting the underlying DTLS connection, so that should be fine too.


-          However, in case of TCP/DTLS/SCTP, the draft says that connection:new re-establishes both the TCP connection and the SCTP association, so I guess that would impact the DTLS connection.


Regards,

Christer

v2.23.0 | Report a Bug | By Email