Re: I-D expiry [was Re: RFCs vs Standards]
Scott Bradner <sob@sobco.com> Sun, 08 December 2024 01:19 UTC
Return-Path: <sob@sobco.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 3213FC14F701 for <ietf@ietfa.amsl.com>; Sat, 7 Dec 2024 17:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sobco.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 s2dqs53XjZPq for <ietf@ietfa.amsl.com>; Sat, 7 Dec 2024 17:19:14 -0800 (PST)
Received: from sobco.sobco.com (sobco.sobco.com [199.204.155.45]) by ietfa.amsl.com (Postfix) with ESMTP id 25DC9C151061 for <ietf@ietf.org>; Sat, 7 Dec 2024 17:19:13 -0800 (PST)
Received: from smtpclient.apple (golem.sobco.com [199.204.155.34]) by sobco.sobco.com (Postfix) with ESMTPSA id 389517CFE2F; Sat, 7 Dec 2024 20:19:13 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=sobco.com; s=mail; t=1733620753; bh=xvJAbl/JowSSbvUneUydkhu/KWQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=vvntDEs31zIVzQoZDUhomTSHv3Z09TId0NA4Ab1y88OEoCuMcDW2Cnu6cKTl2dXoK cMQ35UsIV/fyi35vdsaENKSvpERPZ6R4dVxovWJxkAJNYxM5HTAYxubBwfmKhftqqv 8FBaGgPOvpIGdlzlaITjVIfl0J+GaW3YpP3OpD4YmaxOn69XXQZTZCekxHTwVH9DXk /lNEcqYsy94ovplCRctEfEeo8j4b78Gdel0DqU+9wRYGZmLpEIEWl6MMaiPiDbE/Co /x7ntC4Uu61ygbaiHjzsYU0dtpMRJ/UQbWT3Dt/VtgKQ9ySTIodjVce/8ShvI1GxqX w9jDy344ngNxg==
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
Subject: Re: I-D expiry [was Re: RFCs vs Standards]
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <acf763e0-5d4d-4cb5-9fa4-2497344b2c3e@cs.tcd.ie>
Date: Sat, 07 Dec 2024 20:19:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <06802B6D-5235-4C42-806E-BA39DADC53E6@sobco.com>
References: <BE95E617-C929-43BA-BB40-41E189A8158B@akamai.com> <SY8P300MB0711C796AB6095C788556516EE292@SY8P300MB0711.AUSP300.PROD.OUTLOOK.COM> <15450.1732763286@obiwan.sandelman.ca> <3029EB03-6E7A-47CB-9682-F511CB51EE17@akamai.com> <10065.1732826193@obiwan.sandelman.ca> <CACsn0cmWVeFdJ3dzMj5SV4XpJF4rssULtfQ1moeefoq-Evhk=g@mail.gmail.com> <CAGL5yWb=tLvMOYFKT3ffVbcy7BAD=i4B0VHEUdkvwRvZ3X3Bsw@mail.gmail.com> <m2mshh4v8l.wl-randy@psg.com> <CABcZeBMjxNbBMYU2p3_a8-5VCExgmY-7XLof7die05YOEX-38A@mail.gmail.com> <70419651-6443-4393-9ca1-8a1c98a68db0@cs.tcd.ie> <CABcZeBNtBRxi5zSf9OvUip2AtyVD6Wt9+kQESuUzo-=Kur9+ZQ@mail.gmail.com> <fac981d9-2fe9-4a84-8af1-845acd72af58@cs.tcd.ie> <14124.1733073164@obiwan.sandelman.ca> <d52ee080-814b-46fd-9e0f-41349941eeac@cs.tcd.ie> <1384.1733077486@obiwan.sandelman.ca> <m2frn53g8h.wl-randy@psg.com> <a8290be2-9713-4fd3-914c-1d8090d27d38@huitema.net> <d37dd3c7-ebc3-485f-997c-e6301782a8c4@gmail.com> <3005CAE1-D2A8-4C37-B1A3-6938C0813245@tzi.org> <acf763e0-5d4d-4cb5-9fa4-2497344b2c3e@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3826.200.121)
Message-ID-Hash: NK6HPLE7KLD2G466Z2QOXFI3WCZMZMHE
X-Message-ID-Hash: NK6HPLE7KLD2G466Z2QOXFI3WCZMZMHE
X-MailFrom: sob@sobco.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Carsten Bormann <cabo@tzi.org>, IETF discussion list <ietf@ietf.org>
X-Mailman-Version: 3.3.9rc6
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>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7lPVdnSZUWOEQKQxSKpIxaZ5QGM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
IDs are cited all the time in patent cases (I've done so many times) - there is not an issue with identifying the right content - the IETF Secretariat has a process that provides the text that was published under a particular name and the date it was published Scott > On Dec 7, 2024, at 8:15 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > > Hiya, > > On 07/12/2024 23:51, Carsten Bormann wrote: >> any I-D) being inappropriate to cite > > Well, I-Ds truly are not great things to cite because: > > - if you only cite the file name(e.g. [1]) then the > content may have changed when the reader gets to it > - if you cite a specific draft number and a newer draft > is ever created the reader won't know which was meant unless > the author called that out, which is extremely rare - much > more common would be that neither author nor reader really > know any of these IETF/I-D minutiae. > > I don't think the above is at all affected by supposed > expiry. > > I-Ds can be very useful things to reference and some such > references are done well, but most in the academic literature > are done seemingly carelessly or without really understanding > what can change. > > S. > > [1] https://datatracker.ietf.org/doc/draft-thomson-gendispatch-no-expiry/ >
- I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: I-D expiry [was Re: RFCs vs Standards] Carsten Bormann
- Re: I-D expiry [was Re: RFCs vs Standards] touch@strayalpha.com
- Re: I-D expiry [was Re: RFCs vs Standards] John Levine
- Re: I-D expiry [was Re: RFCs vs Standards] Scott Bradner
- Re: I-D expiry [was Re: RFCs vs Standards] Carsten Bormann
- Re: I-D expiry [was Re: RFCs vs Standards] touch@strayalpha.com
- Re: I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: I-D expiry [was Re: RFCs vs Standards] Stephen Farrell
- Re: I-D expiry [was Re: RFCs vs Standards] Scott Bradner
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Eliot Lear
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] touch@strayalpha.com
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Eliot Lear
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Joe Touch
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] John Levine
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Eliot Lear
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Watson Ladd
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Cloudflare/Argo error was Re: [rfc-i] I-D expiry … Lloyd W
- Re: Cloudflare/Argo error was Re: [rfc-i] I-D exp… Robert Sparks
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Christian Huitema
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Bill Gage
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] John Levine
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Bill Gage
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Wes Beebee (wbeebee)
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Salz, Rich
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Brian E Carpenter
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Joel Halpern
- Re: RE: [rfc-i] I-D expiry [was Re: RFCs vs Stand… Rob Sayre
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Nick Hilliard
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Joel Halpern
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Salz, Rich
- RE: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Michael Jones
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Christian Huitema
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Eliot Lear
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Donald Eastlake
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- RE: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Roman Danyliw
- RE: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Roman Danyliw
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards] Phillip Hallam-Baker
- Re: I-D expiry [was Re: RFCs vs Standards] S Moonesamy