Re: [Nethistory] The Internet, Architecture, Governance, Technical Work and Net History: A Speci

Guntur Wiseno Putra <gsenopu@gmail.com> Tue, 23 April 2019 12:21 UTC

Return-Path: <gsenopu@gmail.com>
X-Original-To: nethistory@ietfa.amsl.com
Delivered-To: nethistory@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C91B812007C; Tue, 23 Apr 2019 05:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKEiv8BodSdi; Tue, 23 Apr 2019 05:21:26 -0700 (PDT)
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 967711200C1; Tue, 23 Apr 2019 05:21:25 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id u15so12558865otq.10; Tue, 23 Apr 2019 05:21:25 -0700 (PDT)
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=7qpZ4y/AQeRL1pslHYB61q2ncpeYSefxRZ5Sp4avmXU=; b=I4paJrdjmopnc1IeWbUbdxTjsncPlfm3ZWotV+SXH/7aKB3KO9X6A/aLLTBaa56OyW th0nVLHTOhZapjviujEnXI4d1Xa1hM1jnngBkd0Yo/2xHviZndte0b/tuKJd9wsAj0vq 5kmoyWCLiMTA2iRbP/6FYNQ5ojQgE/tAzbUa5OM2WePD1IjwUi19ynJZcFWO0jmxwosX +OCJreCoQX/o4chFStB7uu0/4b3JpIoAMmFm4AQlYu2stsrt7hOSzNPK1/KEiM62ZLRz CT5fCH3ya6W5KeQE5nuHLdy326ojQ3Y/kIEYne8i5v1dxDjAXc/VA41s2mXx4nRGNM8W 9jJw==
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=7qpZ4y/AQeRL1pslHYB61q2ncpeYSefxRZ5Sp4avmXU=; b=kWcin00a7KKC1Fx9zA4+EBFNxQLy7LklOrC6Z3qvz3JZVO1j6Gep+xq9vqnFS2Cvr1 2eLrBwigqUvoeHxZCw7PsNi1RC1/zSzp9S8M358Mys8IucTRfSW2WjnUkXLB4mqlzu/Z i0sFVcOjg4h7EsCKVMUWgvE6cKmRMQSbK13l+mxIUp9brtr1jfLXFIRtk4f0qkcSczIz uALdAH+hkVzkrAvHe9qzsZfFhnqGHmkI/VqZ7nz1lFTLEvVBFmwLmpfefwsrocBDXrT9 g0r+OsBJyxjoGJySIrh+Nvd7F3Ngc4q1VXSgQw/4yfqyQk5ndYB6kDYkhWPUr03rZtMn OevA==
X-Gm-Message-State: APjAAAV7cwy4iTwf3As/4nSZyIV2VFLiq7ugtAw/LUuc4YOBZ2u7SoEm s2t/xnJl46eDjTPCfHej/6ImViQT7bW10kA5WiY=
X-Google-Smtp-Source: APXvYqx512G8hN0yPkIB8l53ywufUcHoCaH5MXd9ZrIO+oF/9fnJUT8hm1fym4D9EO+O+ryj/CKSvnJnLYb7GGAg4ug=
X-Received: by 2002:a9d:665a:: with SMTP id q26mr14290996otm.185.1556022084788; Tue, 23 Apr 2019 05:21:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:2065:0:0:0:0:0 with HTTP; Tue, 23 Apr 2019 05:21:24 -0700 (PDT)
In-Reply-To: <CAKi_AEtgukArGKTFcZyxaX7BrFWVXzfxr_V-7WrYiOrmeOzDKg@mail.gmail.com>
References: <CAKi_AEsFQLyNy3PZt0HR=Vid9HCgOviG_Hi5KPPU7CtvuZ352A@mail.gmail.com> <CAKi_AEvy52U24px+zyQ0f70jeEuJ4HJ3Hip1wCZ_X=UU_uEp1Q@mail.gmail.com> <C3855D43D6701846AD1151A536E7A0584F2A34D6@sjceml521-mbx.china.huawei.com> <CAKi_AEt-D-ZtXn87g3O_E237KRASNNs-9-Tbq9umSLDxQG7bSw@mail.gmail.com> <CAKi_AEtgukArGKTFcZyxaX7BrFWVXzfxr_V-7WrYiOrmeOzDKg@mail.gmail.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Tue, 23 Apr 2019 19:21:24 +0700
Message-ID: <CAKi_AEt=7b9YhkLDrQh9MkK0hsoD5P5ipZOPm487JgMsiHOV+A@mail.gmail.com>
To: Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "internetgovtech@iab.org" <internetgovtech@iab.org>, "nethistory@ietf.org" <nethistory@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a0676f0587319f12"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nethistory/yqbnzaC_sP_nzUaAdowIVktruOw>
Subject: Re: [Nethistory] The Internet, Architecture, Governance, Technical Work and Net History: A Speci
X-BeenThere: nethistory@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Matching net historical materials with institutions that may preserve them <nethistory.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nethistory>, <mailto:nethistory-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nethistory/>
List-Post: <mailto:nethistory@ietf.org>
List-Help: <mailto:nethistory-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nethistory>, <mailto:nethistory-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2019 12:21:29 -0000

Dear All,

As Brian E. Carpenter referred the "Internet Architecture" to Internet
protocols and their designs (mentioned in my message April 21st 2019): it
looks "special" to mention "RFC 791: Internet Protocol" (J. Postel,
September 1981) and its histories -- those obsolete and updates: which is
about the name/title "Internet Protocol" they have....

https://www.rfc-editor.org/info/rfc791

Regard,
Guntur Wiseno Putra

Pada Selasa, 23 April 2019, Guntur Wiseno Putra <gsenopu@gmail.com> menulis:

> Dear Hesham and All,
>
>
> There is a need for correction for the earlier message:
>
> The update "The Architectural Guidelines" (2002) --which I missed before--
> was made to propose such an extension of "Architectural Principles of the
> Internet" (1996) as the latter considered complexity (control) in relation
> with the Internet in large scale...
>
> https://www.rfc-editor.org/rfc/rfc3439.txt
>
> It should be:
>
> The update "The Architectural Guidelines" (2002) --which I missed before--
> was made to propose such an extension of "Architectural Principles of the
> Internet" (1996) as the first considered complexity (control) in relation
> with the Internet in large scale...
>
> https://www.rfc-editor.org/rfc/rfc3439.txt
>
>
> Regard,
> Gintur Wiseno Putra
>
> Pada Selasa, 23 April 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
> menulis:
>
>> Dear Hesham and All,
>>
>> The update "The Architectural Guidelines" (2002) --which I missed
>> before-- was made to propose such an extension of "Architectural Principles
>> of the Internet" (1996) as the latter considered complexity (control) in
>> relation with the Internet in large scale...
>>
>> https://www.rfc-editor.org/rfc/rfc3439.txt
>>
>>
>> Regard,
>> Guntur Wiseno Putra
>>
>>
>> Pada Senin, 22 April 2019, Hesham ElBakoury <Hesham.ElBakoury@huawei.com>
>> menulis:
>>
>>> I think you meant RFC1958 which is updated by RFC3439.
>>>
>>> Hesham
>>>
>>>
>>>
>>> *From:* Architecture-discuss [mailto:architecture-discuss-b
>>> ounces@ietf.org] *On Behalf Of *Guntur Wiseno Putra
>>> *Sent:* Monday, April 22, 2019 6:41 AM
>>> *To:* architecture-discuss@ietf.org; internetgovtech@iab.org;
>>> nethistory@ietf.org
>>> *Subject:* [arch-d] The Internet, Architecture, Governance, Technical
>>> Work and Net History: A Speci
>>>
>>>
>>>
>>> Dear All,
>>>
>>>
>>>
>>> Of the question "What is the Internet Architecture?" mentioned in the
>>> earlier message:
>>>
>>>
>>>
>>>
>>>
>>> Brian. E. Carpenter's text "RFC 1985: Architectural Principles of the
>>> Internet" mentioned about Internet protocols and their design: May this
>>> links helpful to get arrived there at related archives ( as the text did
>>> not use any online source but suppposedly paper ones as references)...:
>>>
>>>
>>>
>>>
>>>
>>> - https://datatracker.ietf.org/doc/search?name=
>>>
>>>
>>>
>>> - https://www.rfc-editor.org/
>>>
>>>
>>>
>>>   Here are  menus "Internet Standard", "Official Internet Protocol
>>> Standards", and "advanced search".
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Regard,
>>>
>>> Guntur Wiseno Putra
>>>
>>> Pada Senin, 22 April 2019, Guntur Wiseno Putra <gsenopu@gmail.com>
>>> menulis:
>>>
>>> Dear All,
>>>
>>>
>>>
>>> Individuals, or collectifs of individuals, are in an age of the
>>> Internet. It is such a presence may be approached and sensed by many ways
>>> --even when one said that s/he had just eat a food which a receipt was
>>> gotten by communicating by the Internet..
>>>
>>>
>>>
>>> Among others there are presences of "the Internet Architecture",
>>> "Internet Governance and Technical Work" and "Net History" as they
>>> represent interest-based mailing lists. How could one get arrived into
>>> those matters (together) --such a programmatic readership/learning: as
>>> sources and concepts have history and discources collectives/net... ?
>>> Should we imagine about information sources by making such a readership
>>> based on the linkage between the three...? Thus we may say about "The
>>> Internet Architecture, Governance and Technical Works: a Net History" (to
>>> say "A Net History in Terms of The Internet Architecture, Governance and
>>> Technical Work)...? --there would be a discourse map on the special
>>> readership which is about a co-presence of mailing lists...? --as one may
>>> use search engines of each mailing list for related interests...?
>>>
>>>
>>>
>>> To make an engagement with the programme should we go with such
>>> tentative journeys considering parts of the special readership...?
>>>
>>>
>>>
>>>
>>>
>>> For example:
>>>
>>> By considering the reasoning above:
>>>
>>>
>>>
>>> To the question on "What is the Internet Architecture?" we may refer to
>>> (archival) sources
>>>
>>>
>>>
>>>
>>>
>>> "RFC 1958: Architectural Principles of the Internet"
>>>
>>> (Carpenter, Brian E. Ed, IAB, 1996)
>>>
>>>
>>>
>>> https://www.rfc-editor.org/info/rfc1958
>>>
>>>
>>>
>>>
>>>
>>> (Note:)
>>>
>>> It was a snapshot record of the principles of the Internet Achitecture
>>> intended for general guidance and general interest...
>>>
>>>
>>>
>>> It was updated by RFC 3439...
>>>
>>>
>>>
>>> Both the concept "Internet Architecture" and the document RFC 1958 have
>>> history bringing readers to other relevant sources... They supposedly also
>>> give suggestions to come to broader or other conceptual discourses on
>>> "governance and technical work"
>>>
>>>
>>>
>>>
>>>
>>> Regard,
>>>
>>> Guntur Wiseno Putra
>>>
>>>