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

Martin Thomson <> Thu, 22 August 2013 22:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1421311E81F8 for <>; Thu, 22 Aug 2013 15:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id x0yneiu6t2Xo for <>; Thu, 22 Aug 2013 15:33:32 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c03::229]) by (Postfix) with ESMTP id 5683F11E81C7 for <>; Thu, 22 Aug 2013 15:33:32 -0700 (PDT)
Received: by with SMTP id t61so2302611wes.28 for <>; Thu, 22 Aug 2013 15:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=nEl5tSR1TT2KH69vS0AeEPU1JDbwJuFpAXk239UwqWE=; b=TmVvNs4dwDq89Xje61uE8jd4gHPi2paz46UQSFt+X2bXu25NE1mrDzlV+AKl60MuDG uWJu9hD81nx5y54wAoaUpKm/q7M7xcKOJ3KRvUJvgEnwRQddsvP8MHFrHahYvt8Is++p oRpSDeoGmTTRFvuUJxT45iRR0FKgz+oW1ZVxU5gesQVEuufLfDFuNaWFjzRfBEbDcbzi vW9m6tK1kLkH4sT6bAvAvegSTkzDnubw0bGebEnbxyoWLKPcRydP2p1d52e0DfPcvAA3 tm3ENY7tsDK2WJwlNL1F3CYqACapxq9v37eFOktsiVhePWIGA8J++OZPsMMbM6UIwNwI 2QmQ==
MIME-Version: 1.0
X-Received: by with SMTP id wc5mr12677785wjc.23.1377210811358; Thu, 22 Aug 2013 15:33:31 -0700 (PDT)
Received: by with HTTP; Thu, 22 Aug 2013 15:33:31 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <>
Date: Thu, 22 Aug 2013 15:33:31 -0700
Message-ID: <>
From: Martin Thomson <>
To: "Stephan Friedl (sfriedl)" <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "" <>
Subject: Re: [TLS] WGLC comments on draft-ietf-tls-applayerprotoneg-01
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 22 Aug 2013 22:33:33 -0000

On 22 August 2013 14:19, Stephan Friedl (sfriedl) <> wrote:
> 1.      We will fix the typos.
> 2.      We will remove the HTTP/2.0 registration.  Martin can add the registration to the IANA Considerations section of the HTTP/2.0 draft.
> 3.      We will leave the lower-case HTTP/1.1 protocol ID as it is.

Sounds good.  Thanks.

> I'd suggest that we leave the 'exp' namespace in the draft and add a statement urging anyone choosing to avail themselves of an 'exp' prefixed opaque protocol identifier to review RFC6648 and make sure they are doing the right thing.  The 'exp' namespace has been explicitly requested by a number of TLS working group members, so I'm hesitant to remove it without more voices calling out for its removal.

I don't think that your analysis places sufficient weight on the cost
of changing names.  The experience that lead to the publication of
6648 shows that renaming doesn't happen in practice.  In this case,
there is also a size pressure that prevents the use of multiple names
for the same thing.

The key problem with X- or exp is that both carry zero semantics, but
they tend to create name-ghettos as a result of implementations that
explicitly ignore names with these prefixes.

Keeping 'exp' would be choosing the preferences of a small few over
IETF consensus on this matter.