Re: [hybi] Versioning is a anti-pattern

Adam Barth <ietf@adambarth.com> Sat, 04 September 2010 02:06 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9F0F3A69BD for <hybi@core3.amsl.com>; Fri, 3 Sep 2010 19:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level:
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF6AMgElfK5Z for <hybi@core3.amsl.com>; Fri, 3 Sep 2010 19:06:40 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 979783A679F for <hybi@ietf.org>; Fri, 3 Sep 2010 19:06:40 -0700 (PDT)
Received: by qyk1 with SMTP id 1so634633qyk.10 for <hybi@ietf.org>; Fri, 03 Sep 2010 19:07:09 -0700 (PDT)
Received: by 10.229.1.162 with SMTP id 34mr857477qcf.226.1283566029666; Fri, 03 Sep 2010 19:07:09 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id t1sm2752196qcs.9.2010.09.03.19.07.03 (version=SSLv3 cipher=RC4-MD5); Fri, 03 Sep 2010 19:07:09 -0700 (PDT)
Received: by iwn3 with SMTP id 3so2266742iwn.31 for <hybi@ietf.org>; Fri, 03 Sep 2010 19:07:02 -0700 (PDT)
Received: by 10.231.173.144 with SMTP id p16mr1865150ibz.108.1283566022171; Fri, 03 Sep 2010 19:07:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.187.218 with HTTP; Fri, 3 Sep 2010 19:06:32 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1009022022090.7470@tvnag.unkk.fr>
References: <20100901224502.0519B3A687C@core3.amsl.com> <AANLkTikP1CF22fL0rBniXmrxEoBAbTNfzP9kyiNA4nbb@mail.gmail.com> <AANLkTi=_1m36ThFZTH_aGE_Unz0KTeexJq_74UGr2j+u@mail.gmail.com> <alpine.DEB.2.00.1009022022090.7470@tvnag.unkk.fr>
From: Adam Barth <ietf@adambarth.com>
Date: Fri, 03 Sep 2010 19:06:32 -0700
Message-ID: <AANLkTi=yQyvX_z3NhvNc4dFjfHwTH2edhYM2LukZDfsm@mail.gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] Versioning is a anti-pattern
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 02:06:41 -0000

On Thu, Sep 2, 2010 at 11:25 AM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Wed, 1 Sep 2010, Adam Barth wrote:
>> Please don't add versioning to the protocol.  Versioning is a anti-pattern
>> for the web.
>
> We've seen this mentioned before on this list but without a lot of
> clarifications and I'm curious:
>
> What are the other transfer protocols for which versioning have failed so
> significantly that versioning in protocols can be called an anti-pattern?

Versioning has been a big pain point for TLS.  Here's a presentation
that outlines some recent implementation experience:

http://www.ietf.org/proceedings/65/slides/tls-6.pdf

I encourage you to read through the presentation (it's pretty short).

> Or isn't it so that it truly is an anti-pattern for the *web* (with the
> emphasis added on the web word) and we're not really doing web here, we're
> discussing a transfer protocol.

It's a continual annoyance in dealing with the IETF to have to deal
with this "browsers don't matter" attitude.  In he case of this
working group, we're working on a protocol expressly for use by
browsers, which would seem to indicate that browser implementation
experience is relevant.

> HTTP is the primary "web protocol" and AFAIK, its versioning is usually not
> considered a failure.

The version number in HTTP hasn't been change in a very long time.  I
suspect we'd encounter tremendous difficulty if we tried to change it
today.

Adam