Re: [Edm] On Section 3.2. At what level should versioning occur?

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Thu, 05 August 2021 09:30 UTC

Return-Path: <auerswal@unix-ag.uni-kl.de>
X-Original-To: edm@ietfa.amsl.com
Delivered-To: edm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612023A0A9D for <edm@ietfa.amsl.com>; Thu, 5 Aug 2021 02:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 9XNtXqXJFsAA for <edm@ietfa.amsl.com>; Thu, 5 Aug 2021 02:30:20 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D22743A0A9A for <edm@iab.org>; Thu, 5 Aug 2021 02:30:19 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 1759UFPh081841 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <edm@iab.org>; Thu, 5 Aug 2021 11:30:15 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 1759UFGK018689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <edm@iab.org>; Thu, 5 Aug 2021 11:30:15 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 1759UFeU018688 for edm@iab.org; Thu, 5 Aug 2021 11:30:15 +0200
Date: Thu, 05 Aug 2021 11:30:15 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: edm@iab.org
Message-ID: <20210805093015.GA17433@unix-ag.uni-kl.de>
References: <d1efb181-7b45-16e3-19f2-e03a8dd1c24a@lear.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <d1efb181-7b45-16e3-19f2-e03a8dd1c24a@lear.ch>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/edm/yBg5O7ZjNcNLFVHTH3mmOahWr_Y>
Subject: Re: [Edm] On Section 3.2. At what level should versioning occur?
X-BeenThere: edm@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <edm.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/edm>, <mailto:edm-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/edm/>
List-Post: <mailto:edm@iab.org>
List-Help: <mailto:edm-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/edm>, <mailto:edm-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2021 09:30:24 -0000

Hello Eliot,

On Thu, Aug 05, 2021 at 11:00:57AM +0200, Eliot Lear wrote:
> [...]
> I really like your section 3.2, but it does presume that the lower
> layers are able to accommodate exposing of version information. 
> Below the IP layer, when IEEE 802 is used, we are in very good
> shape; but does everything below that hourglass neck have that
> attribute, and do we want to demand that in order to implement
> v4/v6?  To that end, my suggestion is that you simply note this as
> an issue when we interact with other technologies.

I do not think this I-D section argues against using version information
for a protocol, but rather that increasing the version number is not
sufficient for implementing and deploying a new version of a protocol
at a later time.

> [...]
> Interestingly, when we do port allocations, we generally say that
> applicants SHOULD include versioning information in their protocols

I think that is good advice, since IMHO versioning information is a
necessary prerequisite for later on introducing another version.

> [...]

Thanks,
Erik