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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 12 July 2022 23:44 UTC

Return-Path: <brian.e.carpenter@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 5C544C14F692 for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 16:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 XNwKcoXa1XUx for <architecture-discuss@ietfa.amsl.com>; Tue, 12 Jul 2022 16:44:45 -0700 (PDT)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 33D80C157B4A for <architecture-discuss@ietf.org>; Tue, 12 Jul 2022 16:44:45 -0700 (PDT)
Received: by mail-pj1-x102c.google.com with SMTP id x18-20020a17090a8a9200b001ef83b332f5so932514pjn.0 for <architecture-discuss@ietf.org>; Tue, 12 Jul 2022 16:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=Sdt7unEOFGKz4DzYiTL2gJbz64YeCFQzQo1lVOqMcI4=; b=hdTOvYRDutP2Sbks+JyKsEoTPUY1RvX/H09SSFULy3BNvp0QHRrDGQDuza2LmDXzV+ qD4Rqc6XhEPgoKvIYy4gF/PiAXrGeDudWOrxo5RVMdu8XPpZIkZwBXPMbt/dWDIx1xLi Yn6p12tOkYxVUjuR7ndcQufm2qppfuwjuuhXklr/WpAftD1oaXiBIJKeo8/xbOS66N2z cD3ffrBux+Io1V3lQ6x/53Kk1nxnx1np7AkPNFGCNkEEfWb3nlKOGcd5Hpx1tU9HXMgH 6PDe1f85LdED8Ilca40cOI9DjttuqUSHBeKhRnRDuw1Y6h2eRI2c0plJ+h3VeldMU+0M q/kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=Sdt7unEOFGKz4DzYiTL2gJbz64YeCFQzQo1lVOqMcI4=; b=FPyrFNzxhDMsCLhQ6SJT4sBNaHPLmDzJFWVUIB+rT5NIvOqQyozSdjksafIcsQ6q5a 5fbpUIJA6uyNnO0d6p9LpGUbSEJ8uqUejcCttIZVGCCsomMAmDzg66mS4rLjUzY0szwP 2+Qx/nL5t4CWDCUYC1KbQtSAQI7pUxHT3+NZCLvgi8F+2X2Xq0s7sCmQb8TmMguEU247 g6SWwnrIz0EilGMkvM/c0NiOrJ6YBwnnAhBykUVp5eE9s1Ayjt42MiA5IVWFeQFlzvrq j1AMYdMzLaWc9Eph2GPQoizWhwLL7fXr5IvMR17S7Iyktk4/ihBeXzYWWYiwgu54XwYx qO2Q==
X-Gm-Message-State: AJIora/ALd7D0DtvLcvhoCl7KP6njgim5MCL6mNyx7MC/9Snl+xuzzcF 2nwKvqUDRKojaR1HYZzQi58=
X-Google-Smtp-Source: AGRyM1s4GvW1ZldmbFmUuFhSUbR5/Bh1cCFM7OkFErOd40u6A0O1fDMpc7sPXlBKz9K+V8g0utgI3A==
X-Received: by 2002:a17:902:c102:b0:16b:e03a:40ff with SMTP id 2-20020a170902c10200b0016be03a40ffmr454358pli.29.1657669484143; Tue, 12 Jul 2022 16:44:44 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id 63-20020a621542000000b00528c26c84a3sm7342090pfv.64.2022.07.12.16.44.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 16:44:43 -0700 (PDT)
Message-ID: <482ad0ea-a64d-5156-445e-9a00ff2a7103@gmail.com>
Date: Wed, 13 Jul 2022 11:44:40 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: iab@iab.org, architecture-discuss@ietf.org
References: <165757861882.5604.10456894596583178055@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <165757861882.5604.10456894596583178055@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/-rvoUKIV4QtzK1Uvf5w4hf9OaHs>
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: Tue, 12 Jul 2022 23:44:47 -0000

I still find it hard to accept that there is community consensus for
this document as it stands. Most of what its says is correct but it
still seems to unreasonably claim universal scope.

Some suggestions:

Title: The Robustness Principle May Have Harmful Consequences

Last sentence of Abstract:
For some types of protocol that are actively maintained, the
robustness principle can, and should, be avoided.

And a few changes in the main text such as:
OLD:
Time and experience shows that negative consequences to interoperability accumulate over time if implementations apply the robustness principle.

NEW:
Time and experience shows that negative consequences to interoperability sometimes accumulate over time if implementations apply the robustness principle.

Even with changes like this, I'm not sure everyone will agree.

Regards
    Brian Carpenter

On 12-Jul-22 10:30, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Internet Architecture Board IETF of the IETF.
> 
>          Title           : The Harmful Consequences of the Robustness Principle
>          Authors         : Martin Thomson
>                            David Schinazi
>    Filename        : draft-iab-protocol-maintenance-08.txt
>    Pages           : 15
>    Date            : 2022-07-11
> 
> Abstract:
>     The robustness principle, often phrased as "be conservative in what
>     you send, and liberal in what you accept", has long guided the design
>     and implementation of Internet protocols.  The posture this statement
>     advocates promotes interoperability in the short term, but can
>     negatively affect the protocol ecosystem over time.  For a protocol
>     that is actively maintained, the robustness principle can, and
>     should, be avoided.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-08.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-iab-protocol-maintenance-08
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt