20160930 - Goodbye, 1978 Internetting !

Ce matin, 30 septembre 2016 j'ai répondu le mail suivant à Bernad Aboba, chair du groupe de travail sur l'inféodation du AINA à l'ICANN, et aux membres de ce groupe de travail le mai suivant.

Etaient copiés :

• Vint Cerf, Google, VP, Internet. Auteur du projet d'interneting d'ARPANET, càd de l'internet
• Bob Kahn, son co-auteur (et restricteur) de TCP/IP
• John Klensin
• Robert Tréhin, le véritable créateur du réseau international à partir de Tymnet Europe
• Joe Rinde le designer du routage de Tymnet
• Louis Pouzin, le père de l'analyse des réseaux des réseaux (explication de Démocrite) et de ce qui manque à l'internet
• Michel Elie, le co-designer avec Hubert ZImmermann, du modèle OSI
• Brian Carpenter, qui a mis en forme l'architecture IETF et ouvert la porte à la suite (frange à frange)
• Pete Resnick et Paul Hoffman qui ont résolu le lien entre l'internet du passé (ASCII) et futur (multilingue) par le principe de subsidiarité.
• Bob McCormick qui a été instrumental dans l'extension proche du réseau domestique américain sur un pied d'égalité
• S Subbiah et Tan Tin Wee qui ont stabilisé le multilingisme du nommage (iDN-S)

Beaucoup manquent à cette liste dont je n'ai pas retrouvé les adresses e-mail. Nous les retrouverons peu à peu à travers la FTF.TF (Fringe To Fringe Task Force) pour la documentation de l'"intersem", le réseau de communications intersémiotique des "cobocoms" (les communications assistées par systèmiques opératives autonomes [bots]).

At 04:25 29/09/2016, Bernard Aboba wrote:

Tonite the Congress passed the continuing resolution, with no IANA riders. The IANA transition is now set to proceed on schedule: http://federalnewsradio.com/legislation/2016/09/pelosi-aide-says-deal-with-speaker-ryan-covers-flint-aid/

I understand

this to mean that, by tonight, the US Government care of Vint Cerf's 1978 ARPANET interneting project will be completed without having met its second motivation (cf. https://www.rfc-editor.org/ien/ien48.txt), i.e. to replace the then internationally prevailing Tymnet ACT multitechnology in its capacity to "allow new networking technology to be introduced into the existing catenet while remaining functionally compatible with existing systems" and "for the phased introduction of new and obsolescence of old networks without requiring a global simultaneous change."

Through my precautionary

positions, architectual analysis, and technical appeals, I made sure that the US Government, ICANN, IETF, ISOC, and more generally their RFC 6852 Global Community determination to maintain and replace the lack of a presentational, protectional, and semiotical architectonical layer by externally (mostly US) based involvements (of a political, legal, economic, commercial, normative, and proprietary nature, etc.) was consensual among them.

I, therefore, feel free

to freely resume my 1986 Tymnet Extended Systems/Services enterprise (closed by US military-industrial interests) of allowing new networking technology to be introduced into the existing catenet while remaining functionally compatible with the existing systems.

I will try

I will try to proceed in a LIBRE manner (i.e. in even being LIBRE of Libre) by the phased introduction of new, and the obsolescence of old, networks without requiring a global simultaneous change. Age, lack of personal and civil budget and experience will hopefully permit me to focus on bits for all (including bots) rather than on dollars for a few. I thank everyone whose ideas and work during these last 50 years have permitted this dream to be considered.

Acknowledgments

In particular, I’d like to mention Norman Hardy, LaRoy Times, Joe Rinde, Bill Krantz, Robert Tréhin, Louis Pouzin, Hubert Zimmermann, Michel Elie, Vint Cerf, John Klensin, ...

And:

• Brian Carpenter whose RFC 1958 (Architectural Principles of the Internet) tells us how to proceed "Everything else should be done at the fringes", This paved the way for the FTF (fringe to fringe) layers, I documented in extending OSI in1985 and further on (Tymnet III requirements).

• and Pete Resnick/Paul Hoffman for their RFC 5895 which " does not specify the behavior of a protocol that appears 'on the wire' [but] an operation that is to be applied to user input in order to prepare that user input for use in an 'on the network' protocol." In adding "As unusual as this may be for a document concerning Internet protocols, it is necessary to describe this operation for implementors ", they have included the principle of subsidiarity as the basis for the IETF protocol set (aka internet) architectural add-ons and cooperative semiotic extensions (intersem).

Closing 40 years now.

Opening a new area.

jfc