Re: [arch-d] I-D Action: draft-iab-protocol-maintenance-08.txt

Joel Halpern <jmh@joelhalpern.com> Wed, 13 July 2022 14:34 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 590D4C15A723 for <architecture-discuss@ietfa.amsl.com>; Wed, 13 Jul 2022 07:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.128
X-Spam-Level:
X-Spam-Status: No, score=-2.128 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGKS2j02cLUY for <architecture-discuss@ietfa.amsl.com>; Wed, 13 Jul 2022 07:34:02 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59DB7C15A720 for <architecture-discuss@ietf.org>; Wed, 13 Jul 2022 07:34:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4Ljg9Q1r6Yz1pXqJ; Wed, 13 Jul 2022 07:34:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1657722842; bh=SWCaBwKBpePvq92KMX2pM/ZZg/c7tssK3S3kleOiw+E=; h=Date:Subject:To:References:From:In-Reply-To:From; b=fICY7nhEWB7880kFP/ttN9xootcdsFvrkF0/X12PdOoieV2lBfmhZzgry8QB+hnj4 Zm9/wA/k0O9n0sX9nv6J0ZQ6kyMpZnengY9Grdrs1Zt4A9enSW+CKH4C8xvF1pQKkX L7gnOXBzbNaTl32zadQW9ro+ltPCQiQHMvwqI4aM=
X-Quarantine-ID: <OlaRBLwxVojk>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.181] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4Ljg9P4qSqz1nt6w; Wed, 13 Jul 2022 07:34:01 -0700 (PDT)
Message-ID: <ade079ff-b8b4-76ab-626c-e74f99229205@joelhalpern.com>
Date: Wed, 13 Jul 2022 10:33:59 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Martin Thomson <mt@lowentropy.net>, architecture-discuss@ietf.org
References: <a06000c5-939a-a896-9c0f-576e9e2ff97f@gmail.com> <D20FCDD6-3756-40E7-AD6A-416A2C464DF1@gmail.com> <dbee51f0-1913-af6e-de00-c3a7f5b77f68@gmail.com> <6723979f-c496-43e1-a389-a50dd3af2224@beta.fastmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <6723979f-c496-43e1-a389-a50dd3af2224@beta.fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/rFY5d1zniW4DpkSquMIk1R5WE4o>
Subject: Re: [arch-d] I-D Action: draft-iab-protocol-maintenance-08.txt
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 14:34:06 -0000

Your description of the Robustness Principle below does not match my 
understanding at all.  It was never intended as an excuse for protocol 
developers to do a bad job.

If that is what you object to, write a draft that objects to that.  And 
provide examples where you consider that happened. Your current draft 
does something different, asking us to give up a tool that has proven at 
least in the Internet and Routing areas to be very useful.

Yours,

Joel

On 7/13/2022 12:14 AM, Martin Thomson wrote:
> This idea that the robustness principle might step in where the 
> protocol design falls short is exactly the sort of thing that needs to 
> stop. We can do better (see above), but relying on implementers to 
> just get it right was a poor strategy even when we didn't know much 
> better. Collectively, we are a group experts who are equipped with the 
> best knowledge and tooling, so there really isn't any excuse for 
> shipping specifications that fall over when they encounter something 
> as trivially predictable as a race condition.
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss