Re: [TLS] TLS ALPN (rfc7301), no reserved seperator char and why is 0 no banned

Martin Thomson <martin.thomson@gmail.com> Mon, 13 April 2015 21:51 UTC

Return-Path: <martin.thomson@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 05C951A8A3D for <tls@ietfa.amsl.com>; Mon, 13 Apr 2015 14:51:04 -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 5avFru6_4PtC for <tls@ietfa.amsl.com>; Mon, 13 Apr 2015 14:51:03 -0700 (PDT)
Received: from mail-vn0-x229.google.com (mail-vn0-x229.google.com [IPv6:2607:f8b0:400c:c0f::229]) (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 C5D741A8A06 for <tls@ietf.org>; Mon, 13 Apr 2015 14:51:02 -0700 (PDT)
Received: by vnbg7 with SMTP id g7so24301480vnb.11 for <tls@ietf.org>; Mon, 13 Apr 2015 14:51:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YcuVLmhVTAqWCFcN1ws4/kVi0//qtVUaPCbG4FmNz/o=; b=lniuxzo9U2igBikORfe7OKVqwNY7WGJ23KZ+z/Q3EBuIRVaqkuuOTs0b1v7Hi9DSjv nUfciBMqSDDlp6JY/9dRcXGsto7G8tN/d2hkuTo+UoQxyNE/ZLt9xOtlmeUzVUvSNe1P 9RPU6eJp7sJ2XghPx1g7JiWURmlf0MaIULukN24/wUyWzS2RfKLPv8QpszlxV5m6QGuG ORdbnCu/0f7COAkH7mOd4irzYiCHuivfoOc8tEXa42MiRMcGqVwevc3wuuLtwr2fxgWD GtXQ4/DJKTzfDdhqJE5zyoYvfs5xagdvqTUcqmIfo0V+Nla2mj+nMX3M/hymviw7eATG mxcw==
MIME-Version: 1.0
X-Received: by 10.60.158.202 with SMTP id ww10mr14091093oeb.18.1428961862066; Mon, 13 Apr 2015 14:51:02 -0700 (PDT)
Received: by 10.202.212.212 with HTTP; Mon, 13 Apr 2015 14:51:01 -0700 (PDT)
In-Reply-To: <20150413214453.AC7AB1B281@ld9781.wdf.sap.corp>
References: <BN3PR0301MB1250C67CE251D36E3D5958EC8CE70@BN3PR0301MB1250.namprd03.prod.outlook.com> <20150413214453.AC7AB1B281@ld9781.wdf.sap.corp>
Date: Mon, 13 Apr 2015 14:51:01 -0700
Message-ID: <CABkgnnULuU4ehjmRS+AoFgTiLbyYoKoGyg+50FoSOpaeqGoqgQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "mrex@sap.com" <mrex@sap.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/Jgvsh0t12S-BgZc5gNZYUyfm7N0>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] TLS ALPN (rfc7301), no reserved seperator char and why is 0 no banned
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: Mon, 13 Apr 2015 21:51:04 -0000

On 13 April 2015 at 14:44, Martin Rex <mrex@sap.com> wrote:
> But I just fail to see a rationale why it needs to be that artificially
> awkward with no pressing need.

The rationale could be as simple as the fact that no one made any
attempt to constrain the value-space when the RFC was discussed in the
working group.

Apparently, people who had NPN implementations were already doing the
ugly API thing (the API in NSS is definitely not an examplar here) and
so no one objected at the time.

I agree that it's more painful than absolutely necessary.