[arch-d] draft-iab-protocol-maintenance-09
David Schinazi <dschinazi.ietf@gmail.com> Wed, 19 October 2022 18:29 UTC
Return-Path: <dschinazi.ietf@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 94B34C1524C0 for <architecture-discuss@ietfa.amsl.com>; Wed, 19 Oct 2022 11:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (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 xWidTryb152b for <architecture-discuss@ietfa.amsl.com>; Wed, 19 Oct 2022 11:29:36 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 1CE2FC1524B9 for <architecture-discuss@ietf.org>; Wed, 19 Oct 2022 11:29:36 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id b2so42037244eja.6 for <architecture-discuss@ietf.org>; Wed, 19 Oct 2022 11:29:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=2Q97rcnmLXQ2fg7GW7hlg0r3jLkzBonw1dORsNGIlEM=; b=mIjxOGZNOTNV8Dl1R/S8vIPgsQelk6m7lntH8PswDmK63cZ7U/fnuxkKvDosx7LFOS xKnKx03W/EBMDiJ3SSjP5uQS1NS0s2qYkLqnc3Pfp4pqUhzYLfgkQMw28xtmLumDt9JN FNKo99fZs6rD2sKahO7SAW/vFIrGlgxX6m6gQF+B7B9TDEh9bniXmFMofC0nWsJT7LcV 0p52KjB7Q558j9RbEbpf7+osKbhd9+uh5g5f+qPFg4L8swYDrIctAxzvsxrr5X0rcuH1 zR/c5nH9Hzt1UfrenhaxOsrHNImyt3CSZWK6bPmFo1KzY3TRoMvnkPfp6IhskuiGIAxb DXPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2Q97rcnmLXQ2fg7GW7hlg0r3jLkzBonw1dORsNGIlEM=; b=SiwdTWsRgZBBIrrYxxRCgfpWDfLHIQP91BvxHPYtCJfymNXS659OFJMCkRMdKH0CAI dZ0PBfSAyN7d+BTAQRLMDhEXve7tm10T0j2eaj2qhkyVhOM26QOA43Hvqgp8ITyvLVKJ fVXexVy2DjVvS4TVG/yfdZlXMYjg+DDwZQ2M8wFEnv5bcES95XWTLxT7rlSB1a+LG3D7 1AZzWfoz0dsyaCj3iXBeeNnb+ejnElDLfHMQF4e/TX1vBd5+hRxSGd0IKxj13vycjUW2 8fPWTW1PTcP3Npe2EPBCnXe381PT0TTKF1eBVgD2HiILO15+CphLc6BR96YilLa2gVL9 jNuw==
X-Gm-Message-State: ACrzQf2j/z7cGGc7iOI06f2nGlGqy/lUs7YT/O3ZFRrw8m6oWWE1+kcs x+f3RpkV4NSRFWwAddqApRzXIP4zEjvNBO3OqzsdNdOjHug=
X-Google-Smtp-Source: AMsMyM5NnI5fVJgRWjhpnzSfs8gJ26XmDj8kc9WWtQnHvixfZFPjPo910dJ5bvKUPC3YbOAtyVjUCadnuybwl52cTvw=
X-Received: by 2002:a17:906:fe0b:b0:787:f1d3:2105 with SMTP id wy11-20020a170906fe0b00b00787f1d32105mr7991391ejb.83.1666204173270; Wed, 19 Oct 2022 11:29:33 -0700 (PDT)
MIME-Version: 1.0
References: <166616127293.25856.7930329759300640223@ietfa.amsl.com>
In-Reply-To: <166616127293.25856.7930329759300640223@ietfa.amsl.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 19 Oct 2022 11:29:21 -0700
Message-ID: <CAPDSy+6bq5+KyTn0RkiLJ9iDOnSCqHjWXOYd+LJ_dmxwZ2rYpg@mail.gmail.com>
To: architecture-discuss@ietf.org, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="000000000000df046005eb6763da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/BYpBurJDTsU5lKON8GzUWew-HHY>
Subject: [arch-d] draft-iab-protocol-maintenance-09
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, 19 Oct 2022 18:29:39 -0000
Hello Architecture Enthusiasts, Martin and I spent some time incorporating the feedback we received at IETF 114 regarding draft-iab-protocol-maintenance. Thanks again to everyone who contributed to the discussion. What came out of it was a significant change in tone of the document, with a much stronger focus on Active Protocol Maintenance and less on the Robustness Principle. Please take a look at the latest version and let us know what you think! Here's the most up-to-date copy: https://intarchboard.github.io/draft-protocol-maintenance/draft-iab-protocol-maintenance.html Thanks, David ---------- Forwarded message --------- Name: draft-iab-protocol-maintenance Revision: 09 Title: Maintaining Robust Protocols Document date: 2022-10-19 Group: iab Pages: 15 URL: https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-09.txt Status: https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/ Html: https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-09.html Htmlized: https://datatracker.ietf.org/doc/html/draft-iab-protocol-maintenance Diff: https://www.ietf.org/rfcdiff?url2=draft-iab-protocol-maintenance-09 Abstract: The main goal of the networking standards process is to enable the long term interoperability of protocols. This document describes active protocol maintenance, a means to accomplish that goal. By evolving specifications and implementations, it is possible to reduce ambiguity over time and create a healthy ecosystem. 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. However, it has been interpreted in a variety of ways. While some interpretations help ensure the health of the Internet, others can negatively affect interoperability over time. When a protocol is actively maintained, protocol designers and implementers can avoid these pitfalls.
- [arch-d] draft-iab-protocol-maintenance-09 David Schinazi