IETF Logo Mail Archive

Re: [TLS] Impact of draft-ietf-mptcp-api on TLS

Sean Turner <turners@ieca.com> Tue, 27 November 2012 19:11 UTC

Return-Path: <turners@ieca.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C84821F857D for <tls@ietfa.amsl.com>; Tue, 27 Nov 2012 11:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.282
X-Spam-Level:
X-Spam-Status: No, score=-102.282 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mV2IuFXky5bn for <tls@ietfa.amsl.com>; Tue, 27 Nov 2012 11:11:45 -0800 (PST)
Received: from gateway11.websitewelcome.com (gateway11.websitewelcome.com [67.18.94.11]) by ietfa.amsl.com (Postfix) with ESMTP id 0B85221F8743 for <tls@ietf.org>; Tue, 27 Nov 2012 11:11:45 -0800 (PST)
Received: by gateway11.websitewelcome.com (Postfix, from userid 5011) id 69E6786FD826B; Tue, 27 Nov 2012 13:11:24 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway11.websitewelcome.com (Postfix) with ESMTP id A0CF486FD7F83 for <tls@ietf.org>; Tue, 27 Nov 2012 13:11:23 -0600 (CST)
Received: from [108.45.19.185] (port=56052 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1TdQZ2-00079Y-4x for tls@ietf.org; Tue, 27 Nov 2012 13:11:24 -0600
Message-ID: <50B5105B.1050806@ieca.com>
Date: Tue, 27 Nov 2012 14:11:23 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: tls@ietf.org
References: <50A53890.4090502@ieca.com>
In-Reply-To: <50A53890.4090502@ieca.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (thunderfish.local) [108.45.19.185]:56052
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Subject: Re: [TLS] Impact of draft-ietf-mptcp-api on TLS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2012 19:11:45 -0000

On 11/15/12 1:46 PM, Sean Turner wrote:
> The Multipath TCP (MPTCP) work is starting to bubble up to the IESG:
> http://datatracker.ietf.org/doc/draft-ietf-mptcp-api/
> Both Stephen and I have concerns about its interactions with TLS:
> https://datatracker.ietf.org/doc/draft-ietf-mptcp-api/ballot/
>
> Has anybody here had a look at mptcp (or want to have a look) and have
> any thoughts about its interactions with TLS?

What's on offer to for the mptcp api draft is as follows:

"Implementations of TLS [RFC5246] making use of the basic API that
compare the addresses used by MPTCP against names or addresses present
in X.509 certificates [RFC5280,RFC6125] MUST only consider the addresses
used in the initial subflow since MPTCP itself handles the security of
subsequent subflows. A need for finer-grained controls would imply a
need to use an advanced API."

Thoughts?

spt

v2.23.0 | Report a Bug | By Email