IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 22 May 2023 01:41 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 3D4ECC137398 for <ietf@ietfa.amsl.com>; Sun, 21 May 2023 18:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.097
X-Spam-Level:
X-Spam-Status: No, score=-5.097 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.999] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WWxpqpT7Qv1q for <ietf@ietfa.amsl.com>; Sun, 21 May 2023 18:41:11 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F369C13738C for <ietf@ietf.org>; Sun, 21 May 2023 18:41:11 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-1ae52ce3250so50983465ad.2 for <ietf@ietf.org>; Sun, 21 May 2023 18:41:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684719670; x=1687311670; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=9co7ykc0gM/su9CbXSk3AFjJRFsN8fcP6eU6k5OuX9w=; b=Q0ULdKXRY/+kkag5JDKAUV9mdVgl1b7jQyr2zEMXNeCOwIPuLHfqbCO+sBVTWdVBAy /MeSJZKTr5NfSPGNkVQIgJfPqddV7N0yMUkvwQ2/pDt8QKfnztRS6Xl/WIq3lpFmqLGr 9Y86Em5HSKXZMWkuFR7MKfdcT6OeMZwzMIPUlgek8yYmZehDeeT/AaovQiA8tz1q02rr HrrepBwUEyZ4K9QUPWtilIefKpyGlKsTf3K078eXyK6hjOU7zUHeKek5v2noZCcdJGNt WGeZvy8imOSijfuNmdEA8ZXKA/WpAzqn/yIa1l31CJn2xSdcPh3Ce73hyspGRsjD0J7e QsMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684719670; x=1687311670; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9co7ykc0gM/su9CbXSk3AFjJRFsN8fcP6eU6k5OuX9w=; b=j0G2kcSJCvBW9hdRjYoDdT6jK7DLfgVLBho/t+nsNyVohreZJdBy0LTd0qs/Zw/z4T isPzFVbu5RFzkK14FN5HhhCSIKEUjKBwNqY9DRCHB+jiAkH0pT5i7xbGbvNCkwEl32N/ iEGmWRZYOn1MRXxe8klT0FSQ3bgNIQLOujp5EIRT2+jBXuo00jRRfbwnMuetKObAZ4bl 4m1wUW2KyGMfLF7f69yvou4m//d4nOUd6yAiVOA+3tqtC01Mdt5tmFRx0DLLwv+bgRvU +mOG9U72TQLGMaxmgv5qFgpw2D7CryTNH6d2wu9pJe0TioM6KJqQHk7ylU82YMlj7djy 08Vg==
X-Gm-Message-State: AC+VfDzzLVhU8Uqne/Nt3bIKrF9WFsVgKSnkJUP9+16yAHqEsI2SlA7w 43BCnnw3v06pv4Vr2BXMvzY=
X-Google-Smtp-Source: ACHHUZ6RUWGaquOhh5BDv43qZl9fPC04CzY9SCG2NOUxAQdX2RR+qnKEuxlKOIEZQms4Rf84BveZFw==
X-Received: by 2002:a17:902:c1c9:b0:1aa:fe40:6f96 with SMTP id c9-20020a170902c1c900b001aafe406f96mr10183476plc.23.1684719670505; Sun, 21 May 2023 18:41:10 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id i1-20020a17090332c100b001a94a497b50sm3545856plr.20.2023.05.21.18.41.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 21 May 2023 18:41:10 -0700 (PDT)
Message-ID: <251491e3-bfb3-b6d5-7223-21d3b2514cd8@gmail.com>
Date: Mon, 22 May 2023 13:41:05 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Re: Rivest's S-Expressions I-D no longer found
Content-Language: en-US
To: Scott Bradner <sob@sobco.com>
Cc: ietf@ietf.org
References: <5da5a46c-ac33-d5be-5ad6-b992ba6f1341@gmail.com> <A950CCFA-5ED0-4207-A80F-6DF774A0288A@strayalpha.com> <BF5F8AEC-7B95-4D77-A0BE-8009074EE5E3@sobco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <BF5F8AEC-7B95-4D77-A0BE-8009074EE5E3@sobco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/86pVEEIRnKXc-coKEAYK0gYUqSM>
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 01:41:15 -0000

Hi Scott,

Yes, I wondered about that. You're right; it isn't listed in the relevant IMR either (https://www.rfc-editor.org/in-notes/museum/imr/). So it was never posted by the IETF
Secretariat.

Regards
    Brian

On 22-May-23 11:30, Scott Bradner wrote:
> I do not have a copy of that file in my ID directory & I was saving every ID that got published
> so maybe the doc was never published as an ID even though it is in ID format. That would
> be consistent with RFC 2693 referring to the file and not to the ID.
> 
> I also do not find any announcement of such an ID being published in the old item list archive
> 
> Scott
> 
>> On May 21, 2023, at 6:57 PM, Joe Touch <touch@strayalpha.com> 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
>>>
>>
>

v2.23.0 | Report a Bug | By Email