IETF Logo Mail Archive

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

Bernard Aboba <bernard.aboba@gmail.com> Wed, 13 July 2022 03:46 UTC

Return-Path: <bernard.aboba@gmail.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 24728C14F75F for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 20:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8jqZtPpc8YrR for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 20:46:08 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA0CEC14F728 for <architecture-discuss@ietf.org>; Tue, 12 Jul 2022 20:46:08 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id s206so9348922pgs.3 for <architecture-discuss@ietf.org>; Tue, 12 Jul 2022 20:46:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=7kdkZqIElxydaFxOR3/oWfTNzBEQai3nelcn0yUiHxo=; b=j6AwIBkvEW/04FWHffTFMaaT/8+i/fQs0UAbWZx6c7lvm8cgYteBtUx4wddIFjr/nD wfhCQmuonw7hl/AUU04IeKyWiv2MVLV6eK6ietkeCUqQXwbX/kwSrnbG9K+G6xMANCdb 0RkQUvhUdDph12N5Nw0xHAjJK/DaHEc6wSZZNMi0vmo32kP+jkQBOhsp62iCNVnkbDVi ogyUquiR8n37+oEybPcbC8OP1b0wJWugbUqLnknjWxP11VExEbAKUvFGiX1G7a592ifL vos17QAYpQw48Aru/iLWfD6PomOT3K925kGRWSKSamBrVezo/u/n7n8aNRZXrYnYjViM pQZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=7kdkZqIElxydaFxOR3/oWfTNzBEQai3nelcn0yUiHxo=; b=029UyjdDcZFEOFS0im6QMt390Hzkzx2PmGD/mkTFi87+XV0HG70Uw38Ziu6wKH+WoN A+TxvalYH1wjgXmk4bU3fayTOgByKsBEQrCYm0ouA5YxqY3RBluvz/pYVv3bDrhMx/R8 C72Y8rrbDTdj/SYJna/xceahkebJyqYJsTDoFHfahughGMd7ibbHeVjvP4fMfY8oi8q0 VpxuAHnhguNLXThequKLacIUrL4qSG2P5L65Vi3ZMYyXIxAP2EYZ9tuyGOWBvdXOtwyv 3+3Q0+Q71CwkWTEYY6UPSvR+CC+1Lzvs1ev293qfHucaA9drTIA308IESyG4Ey91XYz2 6ZFw==
X-Gm-Message-State: AJIora+sjADZHP+Y2lbukanAok7t78oxB8BgbmROK/E/5DHEYu99Z7R5 RFlV7FIDaFfw/a8nN/aaIUcldXBOE08=
X-Google-Smtp-Source: AGRyM1sn9KorkRyB4g/gAbQow8WaNpPHqgoErdDxbd32XpIsvnhkJtdXN9FpqKgZWVQczrMKT8K9nQ==
X-Received: by 2002:a63:f84b:0:b0:416:360f:230d with SMTP id v11-20020a63f84b000000b00416360f230dmr1306785pgj.376.1657683967743; Tue, 12 Jul 2022 20:46:07 -0700 (PDT)
Received: from smtpclient.apple (047-007-024-123.res.spectrum.com. [47.7.24.123]) by smtp.gmail.com with ESMTPSA id u8-20020a1709026e0800b001635b86a790sm7657927plk.44.2022.07.12.20.46.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 20:46:06 -0700 (PDT)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Google-Original-From: Bernard Aboba <Bernard.Aboba@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Tue, 12 Jul 2022 20:46:05 -0700
Message-Id: <D20FCDD6-3756-40E7-AD6A-416A2C464DF1@gmail.com>
References: <a06000c5-939a-a896-9c0f-576e9e2ff97f@gmail.com>
Cc: iab@iab.org, architecture-discuss@ietf.org
In-Reply-To: <a06000c5-939a-a896-9c0f-576e9e2ff97f@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: iPhone Mail (19F77)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/SkQn7vojBXvpOEusjgO3s72NHeE>
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 03:46:09 -0000

> On Jul 12, 2022, at 20:03, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> People writing fault-tolerant software will draw their own conclusions.

[BA] Looking at the document examples there are several cases of poorly written specifications. The Robustness Principle doesn’t condone that, nor does it preclude rejecting nonconformant inputs when there are good reasons to do so (e.g. security). If the spec is vague in places, if there are known interop issues, by all means fix it. It’s the Robustness principle, not the Don’t Worry Be Happy principle.

There is another thing that bothers me, which is the problem of untested code paths. Greasing alone cannot solve this. The Robustness Principle mostly applies to expected conditions. Many security vulnerabilities fall into these unexpected cracks. The best tool I have seen us a formal state machine analysis to identify attack vectors. Robustness Principle doesn’t preclude that either.

v2.23.0 | Report a Bug | By Email