Re: Rivest's S-Expressions I-D no longer found

Michael StJohns <mstjohns@comcast.net> Mon, 22 May 2023 00:15 UTC

Return-Path: <mstjohns@comcast.net>
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 713AAC13AE3E for <ietf@ietfa.amsl.com>; Sun, 21 May 2023 17:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.798
X-Spam-Level:
X-Spam-Status: No, score=-0.798 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.999] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrFtp4I5Hvq5 for <ietf@ietfa.amsl.com>; Sun, 21 May 2023 17:15:21 -0700 (PDT)
Received: from resdmta-h1p-028482.sys.comcast.net (resdmta-h1p-028482.sys.comcast.net [96.102.200.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91DB9C14F74A for <ietf@ietf.org>; Sun, 21 May 2023 17:15:21 -0700 (PDT)
Received: from resomta-h1p-027908.sys.comcast.net ([96.102.179.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resdmta-h1p-028482.sys.comcast.net with ESMTP id 0t76qCfkHj6eM0tAtqiWrR; Mon, 22 May 2023 00:13:19 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1684714399; bh=3Uy10wdPqWL4ANPRdaMUQJr8KIVMIaHveHk/DzQ+oyA=; h=Received:Received:Content-Type:Message-ID:Date:MIME-Version: Subject:To:From:Xfinity-Spam-Result; b=EM+rDy3E/f5RK8MUQB3kMrINkQ89+mLXgdoHSTvZDROSonkAf03bmeDkAsHhU6tYE f/fP3tFpvA6KlHbXXwnACiLJqnFyPsaJ26CQyr8g/OoKgdKbbg5BDmOWuXgaR5lPe0 wEEeOqCVJq1FUPWzH1pZJo6zLYiGyv/SgywYT4bbKYjH6QaUfaGBuM5dZYksn8X6YX f35jQawBzWNpEj1Ul55Y1ziALNB4NSgih7QcZG+SRI/jJ6qms4mJFONYz14FpSZrvh G/wvP5YLEsGFTmNsVZlyG/EmjZFnDrrjKZFyS2hTCDg3nPX4bKauNEmj9p9nEfR6Cc rAbHSyAHK9oDA==
Received: from [192.168.1.23] ([108.31.156.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-h1p-027908.sys.comcast.net with ESMTPSA id 0tAOq9cAvSOrw0tAQqAOnm; Mon, 22 May 2023 00:12:55 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrfeejtddgfeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpegtkfffgggfuffvfhfhjgesrgdtreertdefjeenucfhrhhomhepofhitghhrggvlhcuufhtlfhohhhnshcuoehmshhtjhhohhhnshestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepjeffhfehgeejjeefffdvveevtddtleejfffhgfeiudeuueevkeekhfevuefhffdvnecuffhomhgrihhnpehmihhtrdgvughupdgrrhgthhhivhgvrdhorhhgnecukfhppedutdekrdefuddrudehiedrjeeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurddvfegnpdhinhgvthepuddtkedrfedurdduheeirdejiedpmhgrihhlfhhrohhmpehmshhtjhhohhhnshestghomhgtrghsthdrnhgvthdpnhgspghrtghpthhtohepuddprhgtphhtthhopehivghtfhesihgvthhfrdhorhhg
X-Xfinity-VMeta: sc=0.00;st=legit
Content-Type: multipart/alternative; boundary="------------o70qEKdVZc3Sp0P5ET7eTkwl"
Message-ID: <b8f9d16e-eba7-dd80-19cb-8da871923106@comcast.net>
Date: Sun, 21 May 2023 20:12:47 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Subject: Re: Rivest's S-Expressions I-D no longer found
Content-Language: en-US
To: ietf@ietf.org
References: <5da5a46c-ac33-d5be-5ad6-b992ba6f1341@gmail.com> <A950CCFA-5ED0-4207-A80F-6DF774A0288A@strayalpha.com>
From: Michael StJohns <mstjohns@comcast.net>
In-Reply-To: <A950CCFA-5ED0-4207-A80F-6DF774A0288A@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_D11K87QJhNCKsNQ0eohZWHguE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Mon, 22 May 2023 00:15:25 -0000

RFC1602 - published March 1994 appears to be the point at which ISOC 
started claiming rights in contributions.  Assuming this was actually a 
November 1997 draft, it would be covered by the contributions language 
and most IPR issues shouldn't apply if someone wanted to get it 
published as an RFC (or reinstated as a draft as below - we really 
should have a copy of this in any case).

All that's the sort of legalistic view.  The polite thing to do would be 
to ask Dr Rivest and MIT to re-post it somewhere somewhat stable as 
suggested elsewhere.

Later. Mike

>   Contributor agrees to grant, and does grant to ISOC, a
>                perpetual, non-exclusive, royalty-free, world-wide right
>                and license under any copyrights in the contribution to
>                reproduce, distribute, perform or display publicly and
>                prepare derivative works that are based on or incorporate
>                all or part of the contribution, and to reproduce,
>                distribute and perform or display publicly any such
>                derivative works, in any form and in all languages, and to
>                authorize others to do so.


On 5/21/2023 6:57 PM, Joe Touch wrote:
> There was a time before when draft copyright was assigned to the ISOC.
>
> I don’t recall the date, but this seems prior.
>
> Joe
>
>> On May 21, 2023, at 1:53 PM, Brian E Carpenter<brian.e.carpenter@gmail.com>  wrote:
>>
>> Is there any reason why draft-rivest-sexp-00.txt cannot be reinstated to the datatracker? This has been done in the past with "lost" I-Ds.
>>
>> Regards
>>    Brian Carpenter
>>
>>> On 22-May-23 06:34, John Levine wrote:
>>> It appears that Marc Petit-Huguenin<marc@petit-huguenin.org>  said:
>>>> -=-=-=-=-=-
>>>> -=-=-=-=-=-
>>>> -=-=-=-=-=-
>>>>
>>>> https://people.csail.mit.edu/rivest/Sexp.txt  is no longer reachable.  This is a document I use often in my work so I'd like to have a more stable reference, like an Informational RFC.
>>>>
>>>> Is there any interest in trying to do that?
>>> The Internet Archive says it was last seen over a year ago in January 2022.
>>> I concur with the suggestion to get MIT to resuscitate it, but in the meantime,
>>> here's a copy that's not going away any time soon:
>>> https://web.archive.org/web/20220113221331/https://people.csail.mit.edu/rivest/Sexp.txt
>>> R's,
>>> John