rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)
Toerless Eckert <tte@cs.fau.de> Fri, 12 March 2021 14:49 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96FC33A1146; Fri, 12 Mar 2021 06:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Sm2C7KRXMkS5; Fri, 12 Mar 2021 06:49:21 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF0E3A117C; Fri, 12 Mar 2021 06:49:21 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id BE8FD548056; Fri, 12 Mar 2021 15:49:12 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id B6740440166; Fri, 12 Mar 2021 15:49:12 +0100 (CET)
Date: Fri, 12 Mar 2021 15:49:12 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: ietf@ietf.org, chair@ietf.org
Subject: rfc791 coming up to 40 years ... what to do (remember, celebrate, ...?)
Message-ID: <20210312144912.GA27453@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lyEIHK5LehP_psEKTsJCURkcLb4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2021 14:49:31 -0000
Wanted to bring to the list this topic after mentioning it at the plenary. I guess there are all type of memorable dates for the Internet and also more traditional dates for the IETF as an organization, but if i look at the Intersection of the organizations work product and its biggest success, then this seem like a unique IETF event opportunity. So, here is my idea what to do, nonwithstanding anything else of course: Having trolled a bit on internet-history@elists.isoc.org, it is nice to see that there are still a lot of folks around who made it happen back 40 years and from then on. But alas, i am sure that will be different in 10 years. So, one thing i think would be great to do and for which it might even be the last big opportunity would be some form of e.g.: 1 day workshop with interesting invited talks from contributors to that history. Given how a) travel even without Corona for the witnesses of history may not always be a welcome option, b) and given how i think that such a one day workshop would very easily have a target audience far exceeding the IETF community itself, c) and finally given how such an event would best be well preserved for historic consumption, this would actually be ideal to be had as a video event to be recorded. Maybe/probably ISOC would be best to organize, but given how i think as IETF'ers we would like to see focus put on technical payload, i'd hope folks from IETF would drive to make something like this happen. again.. just an idea. Happy to hear any opinion! Cheers Toerless
- rfc791 coming up to 40 years ... what to do (reme… Toerless Eckert
- Re: rfc791 coming up to 40 years ... what to do (… Spencer Dawkins at IETF
- Re: rfc791 coming up to 40 years ... what to do (… Keith Moore
- Re: rfc791 coming up to 40 years ... what to do (… Joe Touch
- Re: rfc791 coming up to 40 years ... what to do (… Behcet Sarikaya
- Re: rfc791 coming up to 40 years ... what to do (… Phillip Hallam-Baker
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Keith Moore
- Re: rfc791 coming up to 40 years ... what to do (… Keith Moore
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Alejandro Acosta
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Nico Williams
- Re: rfc791 coming up to 40 years ... what to do (… Phillip Hallam-Baker
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas
- Re: rfc791 coming up to 40 years ... what to do (… Marc Petit-Huguenin
- Re: rfc791 coming up to 40 years ... what to do (… Phillip Hallam-Baker
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Nico Williams
- Re: rfc791 coming up to 40 years ... what to do (… Joseph Touch
- Re: rfc791 coming up to 40 years ... what to do (… Nico Williams
- Re: rfc791 coming up to 40 years ... what to do (… Michael Thomas