[arch-d] Call for Comment: <draft-iab-use-it-or-lose-it-02> (Long-term Viability of Protocol Extension Mechanisms)

Guntur Wiseno Putra <gsenopu@gmail.com> Fri, 17 September 2021 03:57 UTC

Return-Path: <gsenopu@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 A36B43A1BDF for <architecture-discuss@ietfa.amsl.com>; Thu, 16 Sep 2021 20:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_DOTEDU=1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Bte4urswzLTl for <architecture-discuss@ietfa.amsl.com>; Thu, 16 Sep 2021 20:57:23 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D94EE3A1BE1 for <architecture-discuss@ietf.org>; Thu, 16 Sep 2021 20:57:22 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id j13so24773375edv.13 for <architecture-discuss@ietf.org>; Thu, 16 Sep 2021 20:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VyP6rtSLBuHG+m/LgyhSRaQkl3zBFjlNjmdsaujKLFs=; b=fBOhKNQa5BtAYMo6WelQWQIylnEOXgiTtNPuuJrPGfaBFfcghtlQ9i+jO3zNuZwESO Z+tX0KveE4KBNqOeZpA1Q0SwlyBA1iKLc0LNOSLoZ//vwVCp5wGkTFdtA/VlN3TIYDXv MIwGLQIU+NTWVaUu3LNgKVMruzFsu0r9WmnFc87NTJF6nmrm7zyBR55ByVXwzq3VdExw Q7GPkCUA5Wi+QmFKVs8mptCn4I+FLDM7iLHz5Yb6AzaqoG5dfaem1mIwm14RYR3xx5sH K9X/20IRPivHdq5d8F9pn56uBZDg8wzeWycZ4LmgR0g/EqGK3o7ylRTVzIPfhH3jn8cN E8yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VyP6rtSLBuHG+m/LgyhSRaQkl3zBFjlNjmdsaujKLFs=; b=dw6sidM+xefJh6wcn58PsR6BrfnsI4bljq+cG2hqlbE5kQ6D2fB50ixxHNv2axfDUF F92fBZJL/jNTWPFIUr3AQG6WAlkZLRhWe29SyWSJMfpVpN6yTCGMvcl8cULa95t64ots 86cZQ9QZ/Q5Py1AXRXwHWgCW8iIw30N2fOKvUDi8j8DtIJIk0uwEh7Pp6lGJWMEHAXYz 5gJGAGjp7jLVlgiHiH96upPjD4V6koSKqiqgETUHw0mMwaCO71E21BbcYEa3qbwI44q7 4fuIBwnfqAFaE6pucpDm4Ebn3AShIynuuH4aREQ2LVdBMxkIoDztELcONlCk7xjOO5O8 mmvA==
X-Gm-Message-State: AOAM5312X1P6/xpY0KTfEmeLXB87I6DUMiHwKjBfFkO17csdRUs+RKs4 OlCbvupyoUmP+Bc8rg6ud5GZfv2e2FXaqPKk85A4f3HH
X-Google-Smtp-Source: ABdhPJyJlHrURJCLqk5OuU4O5Nr8fV4LdS5kADE2ZQscwD93tB6Ovs14h2kk2TxBMqL8es7RS8XLCBIFS09E1URx6kY=
X-Received: by 2002:a17:906:a04f:: with SMTP id bg15mr10405733ejb.417.1631851040518; Thu, 16 Sep 2021 20:57:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:906:1402:0:0:0:0 with HTTP; Thu, 16 Sep 2021 20:57:19 -0700 (PDT)
In-Reply-To: <147A3BCB-EBBB-4BC7-B812-7C7670377CAC@vigilsec.com>
References: <162991703946.25379.3009360954932586670@ietfa.amsl.com> <147A3BCB-EBBB-4BC7-B812-7C7670377CAC@vigilsec.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Fri, 17 Sep 2021 10:57:19 +0700
Message-ID: <CAKi_AEt4Do9J0pLA=j1ycV_-oPzcE8fB6CG8hCRkNyuDZ67meA@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000098b5c405cc28ed8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/OrueloG-V2xy3HuSbU-j69OFvD4>
Subject: [arch-d] Call for Comment: <draft-iab-use-it-or-lose-it-02> (Long-term Viability of Protocol Extension Mechanisms)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 17 Sep 2021 03:57:28 -0000

Dear Architecture-discuss,


The abstract said:

"The ability to change protocols depends on exercising the extension and
version negotiation mechanisms that support change. This document explores
how regular use of new protocol features can ensure that it remains
possible to deploy changes to a protocol. Examples are given where lack of
use caused changes to be more difficult or costly. "



1)The extension mechanism would be a way perhaps for next applications of
electronic genetics (electronic anti body, for example) --considering the
current event Covid 19 Pandemic.


"Finally, the promise of genetic engineering is precisely its ability to
reprogram
different codes and their protocols of communication in different areas of
different bodies (or systems) of different species".


(Manuel Castell's "Informationalism, Technology and Network Society"
section"Informationalism: the Technologocal Paradigm of Network Society"

(Manuel Castell, "Informationalism, Technology and Network Society"

https://annenberg.usc.edu/sites/default/files/2015/04/28/
Informationalism%2C%20Networks%20and%20the%20Network%20Society.pdf
)


2) Yet, perhaps, if in our day emplacement supplants extension, so the
extension mechanism of the Internet mentioned above has its limits:

"In our day, emplacement is supplanting extension which itself replaced
localization. Emplacement is defined by the relations of proximity between
points or elements. In formal terms these can be described as series,
trees, lattices. ...

(There is) the importance of problems of emplacement in contemporary
engineering: the storage of information or of the partial results of a
calculation on the memory of a machine, the calculation of discrete
elements, with a random output (such as, quite simply, automobile or in
fact the tones on a relephone line), the identification of tagged or coded
elements in an ensemble that is either distributed haphazardly or sorted in
a univocal classification, or sorted according in a plurivocal
classificatoon, and so on. The problem of place or emplacement is posed in
terms of demography (also)...

Furthermore there was an analysis of "the space outside" which went to an
interest to certain emplacements "that have the curious property of being
connnected to all (the???) other emplacenents, but in such a way that they
suspend, neutralize, or reverse the set of relations that are designated,
reflected, or represented ("réflechis") by them... (as they) are of two
great types": utopias and heterotopias".

NOTE: I red a machine-based copy of Foucault, Michel, "Aesthetics, Method
and Epistemology: Essential Works of Foucault 1954-1984 Volume Two(edited
by James Faubion), Penguin Books, 2000 Ch. "Different Spaces" pp. 175-86.
This is the text of a lecture presented to the Architectural Studies Circle
14 March 1967; it was first published until 1984 ("Architecture, Mouvement,
Continuité 5 (October 1984)).



Regard,
Guntur Wiseno Putra

Pada Senin, 13 September 2021, Russ Housley <housley@vigilsec.com> menulis:

> I read the document, and I encourage the IAB to publish it.
>
> Russ
>
> > On Aug 25, 2021, at 2:43 PM, IAB Executive Administrative Manager <
> execd@iab.org> wrote:
> >
> > This is an announcement of an IETF-wide Call for Comment on
> > draft-iab-use-it-or-lose-it-02.
> >
> > The document is being considered for publication as an Informational RFC
> > within the IAB stream, and is available for inspection at:
> > <https://datatracker.ietf.org/doc/draft-iab-use-it-or-lose-it/>
> >
> > The Call for Comment will last until 2021-09-22. Please send comments to
> > architecture-discuss@ietf.org and iab@iab.org.
> >
> > Abstract:
> >
> >   The ability to change protocols depends on exercising the extension
> >   and version negotiation mechanisms that support change.  This
> >   document explores how regular use of new protocol features can ensure
> >   that it remains possible to deploy changes to a protocol.  Examples
> >   are given where lack of use caused changes to be more difficult or
> >   costly.
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>