Re: [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05

Ilari Liusvaara <ilariliusvaara@welho.com> Wed, 02 March 2016 22:22 UTC

Return-Path: <ilariliusvaara@welho.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 68BC81B32E7 for <tls@ietfa.amsl.com>; Wed, 2 Mar 2016 14:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.006] 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 FMUgji7kbrzn for <tls@ietfa.amsl.com>; Wed, 2 Mar 2016 14:22:32 -0800 (PST)
Received: from welho-filter2.welho.com (welho-filter2.welho.com [83.102.41.24]) by ietfa.amsl.com (Postfix) with ESMTP id 082DE1B32E6 for <tls@ietf.org>; Wed, 2 Mar 2016 14:22:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id EBBAF19C4; Thu, 3 Mar 2016 00:22:21 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id 2GSpm29XtToR; Thu, 3 Mar 2016 00:22:21 +0200 (EET)
Received: from LK-Perkele-V2 (87-100-151-39.bb.dnainternet.fi [87.100.151.39]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp1.welho.com (Postfix) with ESMTPSA id A84DE28D; Thu, 3 Mar 2016 00:22:21 +0200 (EET)
Date: Thu, 3 Mar 2016 00:22:16 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: Joseph Salowey <joe@salowey.net>
Message-ID: <20160302222216.GA12028@LK-Perkele-V2.elisa-laajakaista.fi>
References: <56A8904D.10307@ericsson.com> <CAOgPGoBU+h6cA9RDxBX2m1AR-3-GnC7OYcfDLTpDepX00g73dA@mail.gmail.com> <201602080117.57742.davemgarrett@gmail.com> <56CA239F.6010107@acm.org> <56D7076A.1020703@ericsson.com> <CAOgPGoB669zcdqMYXd0yD4Tkqx7yuj6dc0y1byv3bw1ZN_qv6Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAOgPGoB669zcdqMYXd0yD4Tkqx7yuj6dc0y1byv3bw1ZN_qv6Q@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: ilariliusvaara@welho.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/9DWCdelkGolszeo4ORG6eepcpso>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] WG last call of draft-ietf-avtcore-rfc5764-mux-fixes-05
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Mar 2016 22:22:34 -0000

On Wed, Mar 02, 2016 at 02:08:28PM -0800, Joseph Salowey wrote:
> Reserving large portions of other protocols number spaces is not a good way
> to do things.   This will quickly become unworkable if other protocols
> decide to do the same thing.  This type of behavior needs to be
> discouraged.  There is no guarantee that the multiplexing scheme prompting
> this registration request will work with TLS 1.3 or any future version of
> TLS.

Well, outside of some very exotic extensions (none are defined to date,
and I'm having problems even imagining what such things would actually
do), it would work in TLS 1.3 Editor's Draft (since it only ever uses
21, 22 and 23[1]).

Future versions of TLS are another matter...

And even if there was some extension to omit the version from record
header, it would still work (the demuxer would however need to be
aware of that extension).

 
[1] For comparision, TLS 1.2 uses 21-23 and also 20 and in presence of
certain (infamous) extension, 24.


-Ilari