Re: [TLS] IANA Alert registry does not include ALPN alert

Sean Turner <sean@sn3rd.com> Tue, 06 September 2016 20:31 UTC

Return-Path: <sean@sn3rd.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 C277B12B411 for <tls@ietfa.amsl.com>; Tue, 6 Sep 2016 13:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 9Qz7rVV_NnEj for <tls@ietfa.amsl.com>; Tue, 6 Sep 2016 13:31:22 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 A52F112B3F7 for <tls@ietf.org>; Tue, 6 Sep 2016 13:31:22 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id v123so230730585qkh.2 for <tls@ietf.org>; Tue, 06 Sep 2016 13:31:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hrGU7epG1Cm2MdXCvMn/WYsVmFrLAmfz2k/w3GarhAk=; b=AF6wK9ZOJyayOXWXViIw2yYhcNN3owbPHNLyLji5B4ts/zRh8OXdwOnszLGspoCbRc ilmCuS5GIk6Gdq2VtAzrC6ZtQlHdeF1DnjSHA5oINSj2xdLB6EMTBMMyncxs8ShFzKaq L5vICIyopofwEiO5jE57MtOmV2dRX/MBCLN78=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hrGU7epG1Cm2MdXCvMn/WYsVmFrLAmfz2k/w3GarhAk=; b=aNeh1x9zwXXUXQW1ngziz+ziW36pQxkrSKT/DUK9v3pacZYjWu1Zto+GJgrHShTjZ9 pisf/rwZRSZTI9fJR3ReonL7aLX2IRRxqFy7lmOkih+juYdxxu6gAMe+uoljKeoSqXCQ 7pn41c4poVKsipLKYZu0Q1K/noS3/795+9fieiX9P//F0tJGS6zjlPV6n0VhykVcCvxq PBWjU8PsMklxzMLnZtLd3rBlIIAMT3nlcw5un2C4HM/VzD7HcfAxALtHH0iC+DENDRBh IS8/mpfdxFUpriNMAeWy9B7oTRvBmT0xBYZE4O9AkF7iDwjx+faa76phxh2ir1KsJ4EO taBQ==
X-Gm-Message-State: AE9vXwN0a4a9Lms1mfND5odb8/GoKBDV8E4Z4ASgWIU7OQ9GL+cEE7k+gSFG2/G9s9Dirg==
X-Received: by 10.55.82.4 with SMTP id g4mr49960034qkb.220.1473193881757; Tue, 06 Sep 2016 13:31:21 -0700 (PDT)
Received: from [172.16.0.112] ([96.231.228.70]) by smtp.gmail.com with ESMTPSA id s27sm4807825qtc.3.2016.09.06.13.31.20 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 06 Sep 2016 13:31:20 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CABcZeBNdbi_QKi29ctz5eMfq-97DyY+-4kc_xzOOWwEkkG786A@mail.gmail.com>
Date: Tue, 06 Sep 2016 16:31:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <15D21453-24F5-406B-81D9-2A71DD9EA048@sn3rd.com>
References: <4863811.CEEb377QKO@pintsize.usersys.redhat.com> <CY1PR15MB0778325C9D42BFC71EA4C360FFEC0@CY1PR15MB0778.namprd15.prod.outlook.com> <CABcZeBNdbi_QKi29ctz5eMfq-97DyY+-4kc_xzOOWwEkkG786A@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/iV23qAr-xL96Z9PXRWNczuhNf7w>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] IANA Alert registry does not include ALPN alert
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 06 Sep 2016 20:31:25 -0000

Will do.  Might not make the -00 version but we can add it as an issue to fix in -01.

spt

> On Aug 26, 2016, at 10:41, Eric Rescorla <ekr@rtfm.com> wrote:
> 
> I believe the chairs are preparing an IANA update RFC. We can cram it in there.
> 
> -Ekr
> 
> 
> On Fri, Aug 26, 2016 at 7:27 AM, Xiaoyin Liu <xiaoyin.l@outlook.com> wrote:
> I guess the reason is that this new alert is not mentioned in the IANA Considerations section in RFC7301. I don’t know how to fix it though.
> 
>  
> Best,
> 
> Xiaoyin
> 
>  
>  
>  
> From: Hubert Kario
> Sent: Friday, August 26, 2016 10:03
> To: tls@ietf.org
> Subject: [TLS] IANA Alert registry does not include ALPN alert
> 
>  
> The IANA TLS Alert Registry[1] does not include the 
> no_application_protocol(120) alert from RFC7301[2] (a.k.a. Application-Layer 
> Protocol Negotiation Extension)
> 
> What's the procedure to fix it?
> 
>  1 - https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-6
>  2 - https://tools.ietf.org/html/rfc7301#section-3.2
> -- 
> Regards,
> Hubert Kario
> Senior Quality Engineer, QE BaseOS Security team
> Web: www.cz.redhat.com
> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
> 
> 
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls