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

Guntur Wiseno Putra <gsenopu@gmail.com> Wed, 24 April 2019 07:13 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 C274A1202FA; Wed, 24 Apr 2019 00:13:15 -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=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 P6_ZsmkjNsCi; Wed, 24 Apr 2019 00:13:12 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 D6D5F1202F3; Wed, 24 Apr 2019 00:13:11 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id a25so2579725otq.3; Wed, 24 Apr 2019 00:13:11 -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=6zk3Pzui+0/dQxFVIpXRFdFcvRlZmmBXS0bC4ukmPvU=; b=LeMEzFIMqRykRzquAQ05oqX9OmDRa/U+Jmg0T1Bbaz+xcMugmhaPTAimso/ac+M3yN Niq/TRSU4T5r7D5s3gm+35fYija86kgP2ujfrjXlyFOnOlMZuiiNM0wBOBUWtxF9xnzq KXLyvJGcRBNmeMpFaHBvOEouVbsLO+LRFMcla+0IYzOnleeaD/sJhoGWKErDAjaxDnqB S+wic2H5g/1IcBVHTg7krgyOuff32O+oMU+S+wdwyc4fRmWlX12mcRJP6JDsqDlO86Ji VVCH4Aj2czSes+gcYHk7iWKmCQ7Rb3iRVQawF/n5euvhK1tSKj1Sp9yoctQ9KEIgPmMa 5GyQ==
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=6zk3Pzui+0/dQxFVIpXRFdFcvRlZmmBXS0bC4ukmPvU=; b=dMYe+OolHnm4Lt0ANyQOcDQ2bunouHgRmiZ1ZG+M8TqRQmQlhb/3G/Ltb8R1KHIF/f xtnLu6UXsyQEocrD0kfg/Ci22UnDLTV9jmrRw1qluWA+N8eeJ8V0mrQ3SKlJN6FmIFUB 4eF4fWe482nukBEvJb9G31apWFEe0DpKoCPtvKp2G6H+JU6v/Mpu8/jsolv4henQrF9o q7T8COazMb8ydpQGk/W3NoKBpG+lLLaJogBpFBpY3q9pwz10jCPT4Rm9TwEDi1bSDPkI xO/HcmPvx6vrWpOGj0EH5YhgceT4gReRmIFAyMBqSL56eAN9vyNLQyiGBQF3Qul2J64T QR7A==
X-Gm-Message-State: APjAAAX4MJLrzuY87l68RX6DAHjSQWQ5CLPEUF3TnR5XihSKEVMICpoy GV0QQWNbJHweSsjf5MvShQrZgNBb4SUpBzOistY=
X-Google-Smtp-Source: APXvYqxgsx07Ku4k9r+bCnd+u61q1xmqqryDRhtGoOHCd+WgiReOoMNoz/oEYxocpddaHCaSIpNOuOK17Ij0EfxoKsc=
X-Received: by 2002:a9d:4d0b:: with SMTP id n11mr17400779otf.98.1556089990290; Wed, 24 Apr 2019 00:13:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:2065:0:0:0:0:0 with HTTP; Wed, 24 Apr 2019 00:13:09 -0700 (PDT)
In-Reply-To: <CAKi_AEttPFPcqqB_rH1nU_+Mg==niMznGoD8vq_93yB-uS_xXw@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> <CAKi_AEt=7b9YhkLDrQh9MkK0hsoD5P5ipZOPm487JgMsiHOV+A@mail.gmail.com> <CAKi_AEttPFPcqqB_rH1nU_+Mg==niMznGoD8vq_93yB-uS_xXw@mail.gmail.com>
From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Wed, 24 Apr 2019 14:13:09 +0700
Message-ID: <CAKi_AEtVjHkXrCPEOWR=thXXvP8Hb7qHCrF0Uic5GuprAPM-Jw@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="0000000000001c1f9e0587416fe6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nethistory/ZCFX6wtxZ6FkE1H9664heE2lcGQ>
Subject: [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: Wed, 24 Apr 2019 07:13:16 -0000

Dear All,

The websites www.datatracker.ietf.org and www.rfc-editor.org are historians
for the services of historical archives the provide. While a personal
historian may deserve to mention, especially on the "Internet Architecture":

D. Thaler documented aspects of Internet Protocol service model as they
evolved over time .... Some guidence for protocol designers an implementers
were also suggested...

"RFC 6250: Evolution of IP Service Model" (IAB, May 2011)

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

Regard,
Guntur Wiseno Putra

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

> 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
>
> The RFC 791 is one of Official Internet Protocol Standards: Internet
> Standards --of which there are ones do not use terms "Internet Protocol" --
> for examples "Transmission Control Protocol", "User Datagram Protocol", "
> Broadcasting Internet Datagrams"...
>
> https://www.rfc-editor.org/standards
>
> Regard,
> Guntur Wiseno Putra
>
> Pada Selasa, 23 April 2019, Guntur Wiseno Putra <gsenopu@gmail.com>;
> menulis:
>
>> 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
>>>>>
>>>>>