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

Martin Thomson <martin.thomson@gmail.com> Wed, 15 April 2015 19:07 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 D39D31A87DE for <tls@ietfa.amsl.com>; Wed, 15 Apr 2015 12:07:30 -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 GVCl-FNvAUJV for <tls@ietfa.amsl.com>; Wed, 15 Apr 2015 12:07:29 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 74C5C1A87D1 for <tls@ietf.org>; Wed, 15 Apr 2015 12:07:29 -0700 (PDT)
Received: by oift201 with SMTP id t201so36793878oif.3 for <tls@ietf.org>; Wed, 15 Apr 2015 12:07:29 -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=CjuD4iFd5Ij3fY2/Lms5rxkbKFfLqTOzFNldrcEOth0=; b=lE9/iTbkL4ftsrur44ZyN5Uemr4EtOMH97d43eDtjerUxnpvTvVEnEH1yOyUF4coh+ w6PlCtM7/APL8fC1j/7xjg631sXJH3XIgDxcOcKsqTdi5taFsAsNCDNmjvN0JoDCNuZN AbRQCUAkkLY1VrJVVYYS4CZlcGwHJoIvheN/2sst/UNMfTSngx7DYYcsoIdX5KdnDWEh 65z18q5sGla5poPRK1T+Jm06C1o+/CgQAi6IOkQeVBgYasOE8VVgXlUDnmH+rJdKalHc ChSLK++Klu993y/fMUlN0m85YMaYeI7QkdFGBVhcV3d5I2XWBWFrO6dtfsGZqIP3l/i7 j4jQ==
MIME-Version: 1.0
X-Received: by 10.182.56.196 with SMTP id c4mr22653978obq.26.1429124848993; Wed, 15 Apr 2015 12:07:28 -0700 (PDT)
Received: by 10.202.212.212 with HTTP; Wed, 15 Apr 2015 12:07:28 -0700 (PDT)
In-Reply-To: <BN3PR0301MB1250C1D685D10C9F3747BF538CE50@BN3PR0301MB1250.namprd03.prod.outlook.com>
References: <20150414225328.924711B28A@ld9781.wdf.sap.corp> <1531163.KgFZIyykO4@pintsize.usersys.redhat.com> <BN3PR0301MB12509693B1F91EAA100F18958CE50@BN3PR0301MB1250.namprd03.prod.outlook.com> <CABkgnnUU5E76o9g7em57xujaKtqg5ApH=9Mtm3MHpc3uyi8G+Q@mail.gmail.com> <BN3PR0301MB1250C1D685D10C9F3747BF538CE50@BN3PR0301MB1250.namprd03.prod.outlook.com>
Date: Wed, 15 Apr 2015 12:07:28 -0700
Message-ID: <CABkgnnVPhiZp1XSPAz4Zv-m1M_uV4WmCU_pMxmzJ3P9mY9cxbA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Andrei Popov <Andrei.Popov@microsoft.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/b3m1QnOdI-f5tUAIuJCvr2no6Ac>
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: Wed, 15 Apr 2015 19:07:31 -0000

On 15 April 2015 at 11:59, Andrei Popov <Andrei.Popov@microsoft.com> wrote:
> Since the ALPN RFC allows the use of octet strings as ALPN IDs, it seems wrong to characterize non-ASCII IDs as "junk" or "crazy" values. ALPN IDs are not intended for display to the user, and don't have to consist of ASCII characters.

I was only getting into character :)  Obviously, "crazy" is
subjective.  I would hope that the IETF doesn't get into the business
of using the whole expressive range provided by ALPN, because that
only makes it harder to use.