Re: [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> Sat, 09 October 2021 08:13 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 E6AF03A0745 for <architecture-discuss@ietfa.amsl.com>; Sat, 9 Oct 2021 01:13:23 -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 c9a4eQFzyD4C for <architecture-discuss@ietfa.amsl.com>; Sat, 9 Oct 2021 01:13:19 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 29AB63A0744 for <architecture-discuss@ietf.org>; Sat, 9 Oct 2021 01:13:19 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id b8so45013156edk.2 for <architecture-discuss@ietf.org>; Sat, 09 Oct 2021 01:13:19 -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=OVnpeoldF5H6rk7Pcr7laN3MBsJFFcA6UpTmR6Y2vR0=; b=oTbM4foeJjxkAteKDQ435Lmw87sp4KTWSYaNzzOxQGkszbZ1elHby+0OFuC4+B8dts taO2m4GCKRhrHRoT2vRv4txs3PLgv1JpffM5I6eVyP1y8IK3Qpbt1SbIfIWo/rCT9bCK Hb+iWUmRfk8h8bbyob3VAqvr94IMV2dxeY9KTS++/gmbcYPhM7rQfEAO+k1XeaIhRj1W 680ss4lQa9qLu60QbziyFNxYGJ5nEW2aDJQ3s2N6XY5RsmpXljB5hEmiGc5NbnZFOYv2 Mz3yXxhiFQ+VnWYTmdtz03GJ+A6dlNNprRh9I4o9vuJ6qHyKowPTnKUEJLGU0XRC+h4x uDnQ==
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=OVnpeoldF5H6rk7Pcr7laN3MBsJFFcA6UpTmR6Y2vR0=; b=JddhpPXqnmqPXm44pJHP8llLOyK3qhqHv3cMImHo1tLnvazwjF7M18203jn/5L1Mgj F422WPBmJXeovluvFrUR5mNmRYsqNhniSnvkwXn1FaXkrWsLKHrZYrX066otiF9WLHWE ssyVHLwWuOrAJOSU98Y+hFk1DbGm58OWOTBknGE2p1IOufCXQEyFRyo9PI2SkwjWIYLc flM8xzgz1s+rHfN1LyLSTjGgR4+1u8R08km9JEhliCfPUdMcjPbGR3I0CrqHT4vouD0j Dz8raSN38hDuMNCp7D0D44iYzaRPtxtUq6p9v/mQbbCTFpUDxUJUSX1v7VkbKIyUA+zB g5zw==
X-Gm-Message-State: AOAM531+YdHyX6dKbpNgynPnqyZ5xE7brsoqIcxMuXJ5bBiNlmiQ5wZv MDBSrki+tBuq/76QvNTtkgxrNC9css/AqBN2zkI=
X-Google-Smtp-Source: ABdhPJzf2MAUWruI6D9ark/43sO19hcF7INxbvD5WfZ8nR0LSha9h6fCGvt2OWiXhFQayEjIc7fkinAU4nYqSHq2F1s=
X-Received: by 2002:a05:6402:1057:: with SMTP id e23mr22573180edu.352.1633767196415; Sat, 09 Oct 2021 01:13:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:906:1402:0:0:0:0 with HTTP; Sat, 9 Oct 2021 01:13:15 -0700 (PDT)
In-Reply-To: <CAKi_AEt4Do9J0pLA=j1ycV_-oPzcE8fB6CG8hCRkNyuDZ67meA@mail.gmail.com>
References: <162991703946.25379.3009360954932586670@ietfa.amsl.com> <147A3BCB-EBBB-4BC7-B812-7C7670377CAC@vigilsec.com> <CAKi_AEt4Do9J0pLA=j1ycV_-oPzcE8fB6CG8hCRkNyuDZ67meA@mail.gmail.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Sat, 09 Oct 2021 15:13:15 +0700
Message-ID: <CAKi_AEvAPVxJj7i-iS4kXWfJpPNYqNy6x1rKJoAaAZo40z74aw@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="00000000000063581805cde711b5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/4BQAIeuR1Hbitgbfe_MrylaBKF8>
Subject: Re: [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: Sat, 09 Oct 2021 08:13:24 -0000

Dear Architecture-discuss,

For the deadline September 22th 2021, this comment of mine is late. But, it
may have its moment of importances for ones having such cares:

Of the architectural elements of the Internet invariants, what "extention"
and "emplacement"-- I mentioned in the previous message in this thread--
are when they work together may be expresed by this analytical
understanding (which may supposedly be translated into the language of
computer networks):

" ... the whole network connecting the works of Breton, Georges Bataille,
Leiris, and Blachot, and extending through the domain of ethnology, art
history, the history of religions, linguistics and psychoanalysis are
effacing the rubrics in which our culture classified itself and revealing
unforseen kinships, proximities and relations."


The RFC 1121 "Act One-the Poems" supposedly deserves to reopen...?



Regard,
Guntur Wiseno Putra

Pada Jumat, 17 September 2021, Guntur Wiseno Putra <gsenopu@gmail.com>
menulis:

> 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/Inf
> ormationalism%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
>>
>