interesting - I checked the IETF mailing list archive for that date and do not see an ID announcement for that ID (there are announcements for other IDs) Scott > On May 23, 2023, at 11:35 AM, Phillip Hallam-Baker <phill@xxxxxxxxxxxxxxx> wrote: > > While agreeing with John's point, the document in question was originally submitted as an internet draft - May 4, 1997 draft-rivest-sexp-00.txt > > Thus, rather than asking Ron if he would get MIT to publish, it would probably be politer to ask if he is willing for the IETF to complete its process. > > On Sun, May 21, 2023 at 12:32 PM John C Klensin <john-ietf@xxxxxxx> wrote: > Marc, > > IANAL, but I would assume that publication as in Informational > RFC, with all of the IPR issues and permissions that go with it, > would require explicit permission from Rivest and/or MIT. It > might be far easier for you to reach out to him, point out that > it has disappeared, and request/suggest a more stable location > and URL for this important paper. MIT is certainly able to do > that, usually honors requests from Institute Professors unless > there is strong reason not to, and the work required would be a > note from you to him and a note from him to the powers-that-be, > not the rather tedious process required to get an Informational > RFC organized and published. > > john > > > --On Sunday, May 21, 2023 06:28 -0700 Marc Petit-Huguenin > <marc@xxxxxxxxxxxxxxxxxx> wrote: > > > 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? > > > > Thanks. > > > > P.S.: I attached my copy of that document. Thanks to Zotero > > for making the Web a little less annoying. > >
