IETF Logo Mail Archive

Re: BCP97bis

John C Klensin <john-ietf@jck.com> Sun, 17 October 2021 18:04 UTC

Return-Path: <john-ietf@jck.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 B2E533A0DD2; Sun, 17 Oct 2021 11:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 S0I_Futd76sp; Sun, 17 Oct 2021 11:04:27 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BBAD3A0DC7; Sun, 17 Oct 2021 11:04:23 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1mcAWB-000Nns-SS; Sun, 17 Oct 2021 14:04:19 -0400
Date: Sun, 17 Oct 2021 14:04:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Larry Masinter <LMM@acm.org>, 'Russ Housley' <housley@vigilsec.com>, "'Murray S. Kucherawy'" <superuser@gmail.com>
cc: 'IETF' <ietf@ietf.org>
Subject: Re: BCP97bis
Message-ID: <7FD4ED52C043B31F774E9381@PSB>
In-Reply-To: <A7AD43FD-0117-44E7-9AB2-CDE3CB8682E1@akamai.com>
References: <CAL0qLwbwvs2Cp_urgJ=hzc6yEMGDaz3C0xf6RQXRrB89wAx=Rw@mail.gmail.com> <CAL0qLwavK5dYdmYPVxdMT5rA=jBZv1cEyAsVBEWOD7p9MoZR1g@mail.gmail.c om> <C657F78F-FF99-4898-8A08-844B32589DDE@vigilsec.com> <CAL0qLwbLqyWSqFGL2x-FpXXD19QG9-eZkrnTVm_fxt3tUfZSgg@mail.gmail.com> <C92D456E-63ED-453B-8F33-3AAECA40D1DA@vigilsec.com> <27721119-D39D-427D-8EEE-C5027DA15B06@akamai.com> <007c01d7c2dc$9090c780$b1b25680$@acm.org> <A7AD43FD-0117-44E7-9AB2-CDE3CB8682E1@akamai.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k_-WVyS8xzmLwjd3NCIGYpgMuDU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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: Sun, 17 Oct 2021 18:04:32 -0000


--On Sunday, October 17, 2021 17:13 +0000 "Salz, Rich"
<rsalz=40akamai.com@dmarc.ietf.org> wrote:

>   *   To make a stable reference in an unstable world, add a
> date.
> 
> Or add text "retrieved on xxx xxx xxx" like Wikipedia
> often does.

That makes it clear what is being referenced, which is good.
Absent other provisions/ requirements, it does nothing to
guarantee that the content will be there when someone goes
looking for it years (or decades) later.

   john

v2.27.6 | Report a Bug | By Email | System Status