Re: [Tools-discuss] Content at notes.ietf.org is not archival

[Carsten Bormann <[e-mail]>]

> On 16. Sep 2021, at 09:46, Mark Nottingham <[e-mail]> wrote:
> 
> Or, just automatically delete notes 30 days after creation.

(Again, I don’t know whether this was a serious proposal.
I’ll treat is as such for the purpose of this message.)

Or, don’t offer the service at all?
(Probably better than deleting it 30 days after creation (!).)

Most of the people who have done work in the IETF know about the value of accessing random traces of that work from the past.
After a couple of decades, we mostly got rid of the 6-month ideology around Internet-Drafts; I wouldn’t want to repeat that painful experience.

Collecting notes in our own service (as opposed to hackmd.io or Google docs) gives us more control.
Another benefit of having a common service is that, after a while, everybody knows how to use it and we can integrate it into other tools.

Crippling such a service because we can’t figure out how to keep up some ideology strikes me as an expression of contempt for the work of the IETF’s contributors.
You don’t have to feel the same way, but it should be well understood that this is the signal that is being sent.

Grüße, Carsten

>> On 16 Sep 2021, at 5:39 pm, Carsten Bormann <[e-mail]> wrote:
>> 
>> On 15. Sep 2021, at 21:21, Eric Rescorla <[e-mail]> wrote:
>>> 
>>> Hi Robert,
>>> 
>>> This is the kind of PSA that is often made and ignored and then people come to rely on the existing state of affairs, making it hard to change, ISTM that if you want to actually have it be easy to deprecate the data then you probably want to make it actively unreliable now.
>> 
>> I’m not sure there isn’t an emoticon missing from this message…
>> 
>> The message reminds me a bit of Windows UAC and the idea that users are responsible for the reliability of their operating systems.
>> (One main reason that this never can work is that users have work to do and are not in a mode to interrupt their work for arcane unrelated activities.)
>> 
>> Here, users are effectively asked to make manual backups of work that has been done in notes.ietf.org.
>> Many people already occasionally make such backups, stash them away in some unreliable way; others won’t and will start making queries of who has a backup and whether that is the most recent one.  (This already has happened.  Don’t ask.)
>> 
>> Instead of burdening everyone with their own unstructured backup mechanisms, maybe it does make sense to keep something going at the IETF side.
>> 
>> (Being able to underlay a git repository would be the best technical solution that still keeps most responsibility on the user side.
>> But I don’t want to talk mechanism here, just that it is not enough to issue another RFC 6919 "MUST (BUT WE KNOW YOU WON’T)”.)
>> 
>> Grüße, Carsten
>> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
>