Re: [sipcore] Happy Eyeballs for SIP - DTLS as a SIP transport

worley@ariadne.com (Dale R. Worley) Mon, 19 December 2016 01:41 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C601512945F for <sipcore@ietfa.amsl.com>; Sun, 18 Dec 2016 17:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 ZzkG7lLrwALu for <sipcore@ietfa.amsl.com>; Sun, 18 Dec 2016 17:41:24 -0800 (PST)
Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (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 AD2BD126D73 for <sipcore@ietf.org>; Sun, 18 Dec 2016 17:41:24 -0800 (PST)
Received: from resomta-po-11v.sys.comcast.net ([96.114.154.235]) by resqmta-po-01v.sys.comcast.net with SMTP id Imx5cIXipP4DhImxAcVV0B; Mon, 19 Dec 2016 01:41:24 +0000
Received: from hobgoblin.ariadne.com ([24.60.114.4]) by resomta-po-11v.sys.comcast.net with SMTP id Imx7c2WgUy32lImx8ctwLZ; Mon, 19 Dec 2016 01:41:24 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id uBJ1eLC8017130; Sun, 18 Dec 2016 20:40:21 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id uBJ1eKF6017127; Sun, 18 Dec 2016 20:40:20 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <D3BAE81C-80E8-40A4-96A2-F789E6B06FE3@edvina.net> (oej@edvina.net)
Sender: worley@ariadne.com
Date: Sun, 18 Dec 2016 20:40:20 -0500
Message-ID: <87mvfs3ddn.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfFNDEP+RV9W0L+XzsNdsHkHTw0sGh5Trg0Cn6UnBTasJ1mHb+Li7Y/KDw8aauEo42k6K+WG3CT34+s6FONz6lPjJlSw5EyXWuP3CwDRjrAsfFHXKiXU5 c5A2inUdEfvwFO0HKhMubhB1IvrVWVkczCjJL6C/XYF17GjQbn/euqAsHvUmNw3KC9QwkMvj6bLHoGIoaYBZfRKvzSiN20jFBM4kZg8FRddoBngm5egMDt5g
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/NcwS2Zo5nV1z7N4Y5v0myGjVxcY>
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Happy Eyeballs for SIP - DTLS as a SIP transport
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2016 01:41:26 -0000

"Olle E. Johansson" <oej@edvina.net> writes:
>> One correction for my previous message:
>> "SIP+D2U" => "SIPS+D2U"
>> 
>> There obviously will be a need to extend syntax for relevant SIP
>> headers/parameters and semantics to use it as one of the valid
>> protocols. OTOH, I don't think there would be thorny issues and it
>> would be mostly replicating what has been done/said about other
>> transport protocols.
>
> Dale and I had a discussion about it at SIPit and it's an interesting
> mix of connection-less and connection-oriented that needs
> some documentation. But I do think it will help a lot of large-scale platforms.

Though I remember discussions with Roman Shpount that DTLS has some
serious deficiencies for really large-scale systems.  It seems like a
design adjustment might be needed for DTLS to be really usable for SIP
signaling.  There was a discussion on Sipcore back in March.

Dale