IETF Logo Mail Archive

Re: [TLS] WGLC comments on draft-ietf-tls-applayerprotoneg-01

"Salz, Rich" <rsalz@akamai.com> Tue, 20 August 2013 14:03 UTC

Return-Path: <rsalz@akamai.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 8CCF411E80E4 for <tls@ietfa.amsl.com>; Tue, 20 Aug 2013 07:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzCkSfSLPnJS for <tls@ietfa.amsl.com>; Tue, 20 Aug 2013 07:03:06 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 5F24E11E80D9 for <tls@ietf.org>; Tue, 20 Aug 2013 07:03:06 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id C89D2165576; Tue, 20 Aug 2013 14:03:03 +0000 (GMT)
Received: from prod-mail-relay04.akamai.com (prod-mail-relay04.akamai.com [172.27.8.27]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id BD24E165572; Tue, 20 Aug 2013 14:03:03 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub4.kendall.corp.akamai.com [172.27.105.20]) by prod-mail-relay04.akamai.com (Postfix) with ESMTP id 9405047C0A; Tue, 20 Aug 2013 14:03:03 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([169.254.1.119]) by USMA1EX-CASHUB4.kendall.corp.akamai.com ([172.27.105.20]) with mapi; Tue, 20 Aug 2013 10:03:00 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Yoav Nir <ynir@checkpoint.com>, Andrei Popov <Andrei.Popov@microsoft.com>
Date: Tue, 20 Aug 2013 10:03:00 -0400
Thread-Topic: [TLS] WGLC comments on draft-ietf-tls-applayerprotoneg-01
Thread-Index: AQHOnQaCdJJT7vp320qHp0flMWqEHJmc+GSAgABuHQCAALk1oA==
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C711CDF869DC@USMBX1.msg.corp.akamai.com>
References: <CABkgnnXUwLQnVNt19Advb3s7ZGoc_Mrmr7AodigxZKyEZmPYwg@mail.gmail.com> <3651ef9088a147dd8e8d887f769a9538@BL2PR03MB194.namprd03.prod.outlook.com> <7F46F059-63FA-4ABB-9176-68345DA5398B@checkpoint.com>
In-Reply-To: <7F46F059-63FA-4ABB-9176-68345DA5398B@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] WGLC comments on draft-ietf-tls-applayerprotoneg-01
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 20 Aug 2013 14:03:11 -0000

> I have no problem with having HTTP/2.0 there now, as long as we're all clear that this does not relate to draft-ietf-httpbis-http2-xx, but only to the protocol in the eventual RFC.

I think that's asking for trouble.  Some implementations will start using it because "draft-ietf-xxxx is in last call" and then some fundamental major issue will be found and they don't interop.  If HTTP WG doesn't want it, then leave it out.  Perhaps when they publish their RFC they could include the appropriate app registration.

> 3. The experimental namespace was requested by several TLS WG participants; it would be great if they could share their opinions of RFC 6648 section 3 "Recommendations for Creators of New Parameters".

If the protocol were a DNS CName entry, then the registration is 'free'  We could drop the requirement that the actual entry exist, just make it DNS syntax. And use example.com as the private/experimental space.

	/r$

--  
Principal Security Engineer
Akamai Technology
Cambridge, MA

v2.23.0 | Report a Bug | By Email