IETF Logo Mail Archive

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

"Andrew G. Malis" <agmalis@gmail.com> Thu, 16 September 2021 20:02 UTC

Return-Path: <agmalis@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF773A0EDA; Thu, 16 Sep 2021 13:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sU3FHehVEgXG; Thu, 16 Sep 2021 13:02:51 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 729893A0ED1; Thu, 16 Sep 2021 13:02:51 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id m11so9390401ioo.6; Thu, 16 Sep 2021 13:02:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gIgxDRljb8gvc7nmMuHJaqqmB/FxKHTibTbTl2TKuZ8=; b=Rk0URjLYMKiadsa1hkaExalahRqCCayDtL9YBsKyeCPJ08xCugifPEVzh9W8EpiTcS TUldGSY44qJW07NztQ8Z+o6dik0TkeGFx1ZasYmdp8vDCmBfx/lwSLQrL3FK6UW98/LQ OsY8caO3bguYrpWi13TAHe5W9tly/7BfW4stNdxHXE4F/CnKJyMN6Jlz++nq4ZOECrVc LSWOPgflpT7KBNj31u4DKK6PV3qyDC5+EnsCThGrjAjhQiI4cYgg4W12PSDYnBxX2WnZ NZtCEyqmL5Usi0Hogtb+rNz+3lig2TXOftC2146Hey3bnSA8FOwgbh065bm6azT6yFlA JlJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gIgxDRljb8gvc7nmMuHJaqqmB/FxKHTibTbTl2TKuZ8=; b=hZp5aRfOHHHhq6i8hOp6qh3nsgXus8ySRXx9XysQbuLJB+zkpnqwa1EFfHDOcyLSwy ykcOjis+r/Hpme0TMwDHcPykAns4lD4EjMt5iepyMElGCuSeyre9rCCL90aCW5AYRsF8 nAqNtlGButq7A/MivrB1Tz9QCulSXisSVJsolfZnOZ8B0BZ02YQnCJX5m64QSePlqtvD z8jVIUZYJWX3Iq2uZj42AV1z0YHc40G9d4jAYE+vi9dM+sx8qOL2olVmf4vRpNK9Fzl9 BQfjP1oXHagL6AbzxqGbabWf8Zc327R1nPRkg5E+oL6DcFJvwbA5Wq90vGb88DTkmZS5 hJTg==
X-Gm-Message-State: AOAM533NoYFYhRAVHXSmoNHjZFOSgFJLitliUNTxmBjmNIRrSAzgugM0 2rYoA0/nyBO7w0JHyNpkZTUnIz9nEhzgZM4U7Bk=
X-Google-Smtp-Source: ABdhPJycIzW0s1n/D9j2pWiURGKWvbFbUsG4xvQW6LNbbe1yD9XqXq31tK7cMhuewfI0giIF5ZDJG2RzQuMIG9N2Cnc=
X-Received: by 2002:a05:6638:16d4:: with SMTP id g20mr5798500jat.22.1631822569803; Thu, 16 Sep 2021 13:02:49 -0700 (PDT)
MIME-Version: 1.0
References: <f2ea0c4f-9500-391d-b8d1-dcc3ac4a7b1c@nostrum.com> <CABcZeBOeKxO6KOWyC8WBqUxYyqAwqYdKOesBN+2nxtWAy17Mbg@mail.gmail.com> <ADDEE9BD-790B-4E44-982B-DAA15F50722A@tzi.org> <2B11D777-9D50-490F-B7C6-9DD769C789A6@mnot.net> <B6A2905B-6EB9-4A22-AD1A-10C4910408A2@tzi.org> <1534366.1631820151@dooku> <f3177492-7ea9-1a20-11bd-0387e6e80ecd@huitema.net>
In-Reply-To: <f3177492-7ea9-1a20-11bd-0387e6e80ecd@huitema.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 16 Sep 2021 16:02:33 -0400
Message-ID: <CAA=duU2BiHNviC1vpOyC=VBeK4e758tkPvJKFqsP-7NC1QOTNA@mail.gmail.com>
Subject: Re: [Tools-discuss] Content at notes.ietf.org is not archival
To: Christian Huitema <huitema@huitema.net>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Carsten Bormann <cabo@tzi.org>, Working Chairs <wgchairs@ietf.org>, IETF discussion list <ietf@ietf.org>, tools-discuss <tools-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009c12da05cc224c8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/HVHvbZ3RMAiJhQKIzqnHW8g05Ug>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2021 20:02:58 -0000

Christian,

Completed minutes are archived in the Datatracker. These are draft
minutes that we're talking about here.

Cheers,
Andy



On Thu, Sep 16, 2021 at 3:39 PM Christian Huitema <huitema@huitema.net>
wrote:

>
> On 9/16/2021 12:22 PM, Michael Richardson wrote:
> > Carsten Bormann <cabo@tzi.org> wrote:
> >      >> On 16. Sep 2021, at 09:46, Mark Nottingham <mnot@mnot.net>
> 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.)
> >
> > Well, I'm serious.
> > I think 30 days might be way too long.
> >
> > WG and design team leaders should know to download minutes at the end of
> the
> > session.  It's not hard.
> > But, in order to train that, the contents needs to disappear within the
> day,
> > and there will be some crying.   Some WG session minutes will go away.
> >
> >      > 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.
> >
> > Agreed.
>
> The IETF already archives mail messages and Internet drafts. How hard
> would it be to archive notes and minutes? After all, this texts are part
> of the standard making process, covered by the Note Well, etc.
>
> -- Christian Huitema
>
>

v2.23.0 | Report a Bug | By Email