Re: [TLS] MTI extensions?

Dave Garrett <davemgarrett@gmail.com> Sun, 15 March 2015 21:18 UTC

Return-Path: <davemgarrett@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 764BB1A1B8C for <tls@ietfa.amsl.com>; Sun, 15 Mar 2015 14:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 dRem7mCIhN1s for <tls@ietfa.amsl.com>; Sun, 15 Mar 2015 14:18:53 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41B391A01AE for <tls@ietf.org>; Sun, 15 Mar 2015 14:18:53 -0700 (PDT)
Received: by qcbkw5 with SMTP id kw5so29062920qcb.2 for <tls@ietf.org>; Sun, 15 Mar 2015 14:18:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=wsteRBOhJyrjON7qhYKU9WIJidnZgQNnY8GearsI340=; b=BiJP+ig9ksmXiWTXh2U8+dX3nzZwEhX+B+pj0VOuoXejfwkMLUx93SIQgVlMqaj1Ze t7wsi320uUvJQ7RB6sEgY53JrnR2MWfhxfRY9sBDjZSF7ldHoxLGvGTpnH05jPLpHIhw 4jU7yJcCRA2fzDF3+Fnflnm+ONyAqbND6MeEoT2g24dFkcQv4DaA87NsRWgBzTpm2O5j r2XrSy7k8Yu0m60yvGZHP5puZnnBJoYeTykN22bBzg/1xwwhQLwuecJ75gjB5AKjSKc2 +B6JDjoqU8rMwkEr9qUULHZXz1Lq98c0DG8S1xNWZwPK4+P7U4iO0DkYpWkSL5gQwkLH sHJg==
X-Received: by 10.55.23.83 with SMTP id i80mr110303993qkh.104.1426454332561; Sun, 15 Mar 2015 14:18:52 -0700 (PDT)
Received: from dave-laptop.localnet (pool-96-245-254-195.phlapa.fios.verizon.net. [96.245.254.195]) by mx.google.com with ESMTPSA id 10sm6112561qht.13.2015.03.15.14.18.52 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 15 Mar 2015 14:18:52 -0700 (PDT)
From: Dave Garrett <davemgarrett@gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 15 Mar 2015 17:18:50 -0400
User-Agent: KMail/1.13.5 (Linux/2.6.32-71-generic-pae; KDE/4.4.5; i686; ; )
References: <201503140212.53255.davemgarrett@gmail.com> <201503151659.02311.davemgarrett@gmail.com> <CABcZeBO6av8u2QN-aASjADw088eAN6hCFgAaAgQP9ECH0BrZSw@mail.gmail.com>
In-Reply-To: <CABcZeBO6av8u2QN-aASjADw088eAN6hCFgAaAgQP9ECH0BrZSw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201503151718.50477.davemgarrett@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/vnrG1UxdOEYcAdlbZy43FFP9roA>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] MTI extensions?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 15 Mar 2015 21:18:54 -0000

On Sunday, March 15, 2015 05:13:14 pm Eric Rescorla wrote:
> SNI might be plausible as a MUST implement but there are plenty of cases
> where it's not sensible to be MUST send, as in where there is no server
> hostname. E.g., WebRTC.

Yes, I acknowledged that when I started the thread, but with email threading being what it is, it got cut out of quotes. ;)

On Saturday, March 14, 2015 02:12:52 am Dave Garrett wrote:
> Idea: Add a small section after MTI cipher suites for MTI extensions.
[...]
> (not all deployments would need them, but they should always be available)


Dave