Re: [MMUSIC] Draft new: draft-holmberg-mmusic-udptl-dtls-00

Dan Wing <dwing@cisco.com> Wed, 28 August 2013 17:41 UTC

Return-Path: <dwing@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 DDDAA11E8210 for <mmusic@ietfa.amsl.com>; Wed, 28 Aug 2013 10:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.498
X-Spam-Level:
X-Spam-Status: No, score=-110.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lrrvT1VLMacf for <mmusic@ietfa.amsl.com>; Wed, 28 Aug 2013 10:41:15 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 45B1511E8196 for <mmusic@ietf.org>; Wed, 28 Aug 2013 10:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3930; q=dns/txt; s=iport; t=1377711675; x=1378921275; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=fHDMLyzfGFNvuYKYEwxbueHgR8/grh2/U9djsGngju0=; b=EUgLg21RIsrWEBWaHbmcl/f92nhMengl1opAAU56w59MvgixWGL610P5 9ZKZRDKZfCvec+kCLzGw1eGGM2TMWpwL0PBgkG/LVB5V9LzTsNOQtuZXk RY5BMegfVWTvW0RzUk1FPGtNUFWicn2e7abc+dQaMso2qv0uT7aaS8z+B c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAEY1HlKrRDoH/2dsb2JhbABbgwc1wHuBIBZ0giQBAQEDAQEBATctBwsFBwQLEQQBAQEnBycfCQgGE4d7BQ25To44eTMHBoMWfQOJM4pkg1qBLZA0g0AcgS4
X-IronPort-AV: E=Sophos;i="4.89,976,1367971200"; d="scan'208";a="87889523"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 28 Aug 2013 17:41:09 +0000
Received: from sjc-vpn7-327.cisco.com (sjc-vpn7-327.cisco.com [10.21.145.71]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r7SHf7Nu032466; Wed, 28 Aug 2013 17:41:07 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4754A3@ESESSMB209.ericsson.se>
Date: Wed, 28 Aug 2013 10:41:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <361F2B18-D0B3-487B-A534-8E8D4604561D@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1C46787F@ESESSMB209.ericsson.se> <E158A6F0-2A84-4B81-AFDE-CFF5E1EDE295@cisco.com> <7594FB04B1934943A5C02806D1A2204B1C4754A3@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1508)
Cc: mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new: draft-holmberg-mmusic-udptl-dtls-00
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 28 Aug 2013 17:41:20 -0000

On Aug 22, 2013, at 2:37 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi Dan,
> 
> Regarding the 3GPP SA3 study, the information I gave was a little misleading. From a security perspective SRTP would be fine.
> 
> The focus of the SA3 study was on how to provide security for the existing fax transmission mechanism, which uses UDPTL/UDP.
> 
> 3GPP already mandates IMS terminals to support UDPTL/UDP for unsecure fax. And, new terminals (supporting secure fax) are still required to also support unsecure fax, in order to communicate with legacy terminals when unsecure fax is sufficient. 
> 
> So, using UDPTL/DTLS/UDP for secure fax makes more sense, as it avoids implementing different mechanisms for secure and unsecure fax - UDPTL/DTLS/UDP only requires a new layer between UDPTL and UDP, it does not require changing the upper layers (UDPTL and above).
> 
> Hopefully this clarifies :)

(Sorry for my delay.  I was on vacation.)

Thanks for the clarification.


Back to your document, it says:

   Since the DTLS record layer "application_data" packet does not
   indicate whether it carries UDPTL, or some other protocol, the usage
   of a dedicated DTLS association for transport of UDPTL needs to be
   negotiated, e.g. using the Session Description Protocol (SDP)
   [RFC4566] and the SDP offer/answer mechanism [RFC3264].

   Therefore, this document specifies a new <proto> value [RFC4566] for
   the SDP "m=" line [RFC3264], in order to indicate UDPTL over DTLS in
   SDP messages [RFC4566].

Have you considered doing UDPTL negotiation in the DTLS handshake itself, using http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg?  That seems ideally suited for indicating the application layer protocol, perhaps in addition to the SDP signaling described in your I-D.

-d


> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com] 
> Sent: 19. elokuuta 2013 20:43
> To: Christer Holmberg
> Cc: mmusic; mmusic-chairs@tools.ietf.org
> Subject: Re: [MMUSIC] Draft new: draft-holmberg-mmusic-udptl-dtls-00
> 
> 
> On Aug 19, 2013, at 6:03 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
>> Hi,
>> 
>> We have submitted a new draft, draft-holmberg-mmusic-udptl-dtls-00, which defines usage of UDPTL over DTLS, in order to provide secure fax.
>> 
>> The draft was previously submitted to DISPATCH. Based on discussions with the ADs and chairs, it was decided that it shall be submitted to MMUSIC (note that no DTLS extensions are needed).
>> 
>> As is indicated in the draft, 3GPP has performed a study on how to 
>> provide secure fax in the IMS, and the outcome was that secure fax shall be transported using UDPTL over DTLS.
> 
> Got a pointer to that study?  Seems easier to carry UDPTL over RTP, which would allow the RTP to be secured using SRTP (and thus the UDPTL would be secured using SRTP).  There is a spec floating around to do exactly that (carry fax over RTP so that SRTP can secure it).  Advantage of using SRTP to secure fax is it separates the keying mechanism from security, so that Security Descriptions / MIKEY / DTLS-SRTP / whatever-is-invented-in-2020 will work just as effectively for voice as for fax.  And also that upgrading from a voice call to a "fax" call has no additional complexities due to security ("please press START to begin the fax transmission").
> 
> -d
> 
> 
>> However, there is nothing "3GPP/IMS specific" about the mechanism, as UDPTL is commonly used for fax also elsewhere.
>> 
>> Regards,
>> 
>> Christer
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>