[arch-d] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)

Guntur Wiseno Putra <gsenopu@gmail.com> Sun, 01 March 2020 03:10 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 739813A09DA; Sat, 29 Feb 2020 19:10:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.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] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acsPy5TWyofm; Sat, 29 Feb 2020 19:10:08 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 4AFFB3A1893; Sat, 29 Feb 2020 19:10:08 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id x19so1615777otp.7; Sat, 29 Feb 2020 19:10:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YpSIlLJ9wIEFPOicTxcX2+aXlg0pjHF/A/PsYx56BZQ=; b=ELtuKbKP1bH8o+LlccuyDPQuYrRwKrwMcaYTECsPqMfkx4dyMDVcyb0z9QnenMXza6 Q2JuT1riwZDIDD2D5E5GnqWOgVYJ5mDfVsw5G8xXuJTru6FaPKSM7myYc9YtxwJ51/Hi mdZCwH2CDvXe1/7/c0NNxqqMLTCHYsuS7FN17318AycrlKkHMfpH+rQfeCewTbEto+F5 r10PjIJgbxnwLHE+ziX1Etuzu157HayE/crPLeaILMHbVD8pbaP4z5Z3OCUA284D89J6 8D5XUuc+WPh4iXSsrWPFFRAlJoBWj3Ab1EYLceLWuWyUwJrW0TfNpr50eWdAnCWUZ8ra QRcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YpSIlLJ9wIEFPOicTxcX2+aXlg0pjHF/A/PsYx56BZQ=; b=V+an8y/LG49aSXiWN/w/1m2MLooAgK1+m7gNYe7DVV8SOxaBdSVfgR0Go8kU0uW3VB cOBuQCTLW2Rt6Gjs/l+CqBbS+RigFrIKZa4oIND8isuz7D7qjJS97vhrGLQC6ZGmUKsS FoLSOSk8UF0GWKswU1LQvXhA1goO0sbfA0Ns80OCAC1lyZfuIB31NVHUzPsE70Sk/YIb 4rL6ae/mKpiAapQpV6e1K1MStDxov5kecme/EbScTI0Ns8HDPtSyFD1o9C577/zdwB16 ft8dTU1tTzwjrQ0y8+kCwo5w39OzvxZLNYiFyxjX7tBhNehkC/hxV2uMUz4uYYLqWXrR SMPg==
X-Gm-Message-State: APjAAAWBHcxdqrfuxkKZfbHXo++qtJbzO9waIwu6t6OCW5eW+jyk+rZD EPepnKgEMBb6iCgwRuipTIkNPIxpvibysj9iG68=
X-Google-Smtp-Source: APXvYqxhgdDyNx+0RvFHw2ipsJvSeBW1GUrlK8YLE92yrTSACW1QnOnpRSkGBHkiLQZirNUHZXgD5VEf7ATlU4/UOL4=
X-Received: by 2002:a9d:3df6:: with SMTP id l109mr8569771otc.284.1583032207321; Sat, 29 Feb 2020 19:10:07 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:a05:6830:1155:0:0:0:0 with HTTP; Sat, 29 Feb 2020 19:10:06 -0800 (PST)
In-Reply-To: <A1505922-7866-4D03-AEF8-E90E0090A9B7@liquidtelecom.com>
References: <876c9105-3da4-e614-2db0-bea025b54663@si6networks.com> <7749f91f-03f1-cc14-bae8-5fe68c88879f@si6networks.com> <CALx6S36wN7VEi_rxLC1ETcTvkGaPhs20KhQrGWAGGTrCL5OT+g@mail.gmail.com> <d41a94f5ede994b9e14605871f9f7140@strayalpha.com> <69bd06b8-7eee-dfbc-5476-bba0f71ae915@si6networks.com> <3c307da7e8f52b7a29037a1084daf254@strayalpha.com> <a24a3621-99f6-755d-c679-2061b9a67adf@si6networks.com> <CAOj+MMGJ11CBCov=-jfZUtROJPwhQB3A=+0gMBhzZgxoF_9N1A@mail.gmail.com> <A83D4788-AD7B-490C-B74E-2548A1345C47@strayalpha.com> <CAOj+MMHfKMGa7w9pkqg=2RC4XeuYk7+iHt949B3kUtc+vCeB1Q@mail.gmail.com> <CAKi_AEtxLZXV-tDFC0wTueZjGyBUvf7p4wDw8_OWVw6FmQz13g@mail.gmail.com> <A1505922-7866-4D03-AEF8-E90E0090A9B7@liquidtelecom.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Sun, 01 Mar 2020 10:10:06 +0700
Message-ID: <CAKi_AEvBUEQ8F3T+bpL8K9K7Ssg0uUiLTjE5__2+z12Eq46GEA@mail.gmail.com>
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>
Cc: Robert Raszuk <robert@raszuk.net>, Internet Area <int-area@ietf.org>, IETF <ietf@ietf.org>, Tom Herbert <tom@herbertland.com>, "architecture-discuss@iab.org" <architecture-discuss@iab.org>, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000062ac66059fc268f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/6kO28MxyQI-6WUWfgknlGC1OYL8>
Subject: [arch-d] Is IPv6 End-to-End? R.I.P. Architecture? (Fwd: Errata #5933 for RFC8200)
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: Sun, 01 Mar 2020 03:10:12 -0000

Dear Andrew &
architecture-discuss,


I struggled to read yours, Andrew, and others mentioned in this message.

What are about the 4 criteria (assets, incentives, costs and benefits)
mentioned by Pikander...?


He mentioned about "vision" following the criteria:

" We need some kind of an architectural vision and a related transition
path; an idea of where we are heading and perhaps how we could get there.

...".



"Vision is a coincidence between what are Pikander's on the Internet
Architecture (especially about protocols and changes) and what is
Heidegger's on art, technology and humanity:


He ... (Heidegger)... believes this because, as he explains in his earlier
text “The Origin of the Work of Art,” art is nothing other than the
revelation of the way we use things—and, if one wants, of the way we are
used by things.2 Here it is important to note that for Heidegger, the
artwork is not a thing but a vision that opens to the artist in the
clearing of Being.


More generally, the "vision" to elaborate concerns with developing the
Internet technology research and standards: L. Daigle (2009) said


"(In developing the Internet technology based on innivation and
interoprability:) In that model of development, there are three key types
of activity from which feedback needs to be fostered: (1) development of
technical specifications, (2) deployment, and (3) answering open questions
(research). The IETF focuses primarily on the first activity, but it has a
close relationship with the third in the shape of the Internet Research
Task Force (IRTF). The IETF process itself is deliberately open to and
seeking feedback from the second activity: deployment experiences".

https://www.ietfjournal.org/developing-internet-technology-
research-and-standards/

More recently about the "vision" to elaborate is section 4. How We See the
Internet of 2019 ISOC GlobalbReport "Consolidation in the Internet Economy"

https://future.internetsociety.org/2019/wp-content/uploads/sites/2/2019/04/InternetSociety-GlobalInternetReport-ConsolidationintheInternetEconomy.pdf




Regard,
Guntur Wiseno Putra

Pada Minggu, 01 Maret 2020, Andrew Alston <Andrew.Alston@liquidtelecom.com>
menulis:

> Guntur,
>
>
>
> I have to say – I sat and thought about what you wrote here – and there
> was one line tha really struck in in the context of this whole debate
>
>
>
> <snip>
>
> > Any change requires a reason to overcome the associated hurdle.
> Consequently, I have found it very instructive to try to think about the
> network and protocols in terms of assets, incentives, costs, and benefits".
>
> On this – we are in total agreement – which is why when I look at what has
> occurred in SPRING – I find myself getting very depressed.
>
>
>
> In order to consider protocols and change in the context of the four
> criteria you listed – we would need certain information –
>
>
>
>    1. Why do the authors of the disputed draft insist on holding with PSP
>    – what is the substantive use case – I for one – do not believe this has
>    been close to addressed in light of the fact that there were no less than 4
>    ways to progress the contentious draft (compromises were offered,
>    everything from, progress the draft with this moved to another document
>    that could be debated, to update the rfc8200) – in every case – the authors
>    refused to budge
>    2. In order to evaluate benefit you need people who are prepared to
>    state the benefit they see in something – instead we have a document
>    advancing based not on consensus but on (and I quote) “We had to move this
>    forward” and citing a bunch of people who +1’ed a list in what was in my
>    view a clearly orchestrated +1 campaign as justification for support.  I’ll
>    be releasing a rather interesting summary from the lists showing just how
>    many times the majority of those people have **ever** posted to the
>    lists before – it makes for an interesting read.
>    3. With regards to the costs – without knowing what the real reason
>    for insisting on holding to this – and there must be done considering the
>    dogged way the authors and the vendor behind this document have insisted on
>    it – without giving proper reasons – this cannot be evaluated.
>
>
>
> So – on the basis of the criteria you listed alone – the fact that we are
> seeing something being railed through a working group – despite substantive
> – numerous – and unaddressed objections in total violation of the very
> concept of consensus – disturbs me greatly.  I have always believed that if
> things like appeals can be avoided – that is always first prize – sadly in
> this case – we are now forced into an appeal process and we will see how it
> plays out – but – in light of all this – I can understand why people on so
> many lists are questioning what is going on.
>
>
>
> Thanks
>
>
>
> Andrew
>