IETF Logo Mail Archive

Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards]

"touch@strayalpha.com" <touch@strayalpha.com> Mon, 09 December 2024 16:18 UTC

Return-Path: <touch@strayalpha.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 D0ED4C1D4A9D for <ietf@ietfa.amsl.com>; Mon, 9 Dec 2024 08:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=strayalpha.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 jsDbFyieMM0q for <ietf@ietfa.amsl.com>; Mon, 9 Dec 2024 08:18:12 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6CE4C1D4A8F for <ietf@ietf.org>; Mon, 9 Dec 2024 08:18:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=V9wtwnjObHE8yDsk2GlXLw69XD1fmLN6g6uDgT+jHXQ=; b=FKdWoNNPX/uZkS2gPnALkzLH4d 8RotxmTPC/kyxmC7bX0doU6DbxymsFgHDPc5VAGceOnEif8mfhIPmL/3uVGJ+8MkwsaDzUjj7mK+T G191oowQ6M+6nPuT2tmc1mtqR/Fd88mlWCCC5r0XXlFnC4WGTgplS293WInEM1rGh/M62MMwFctK6 bxpC1sUA7qCxTOL/7VBIc1daN9IP9zGhkmkNAWwNV0rXQGRMHp35riVABxVCZVUX4OBVjXNgd2Z3E Wt76q7pce4ADfrH6RRR9TqbUTEkRuWEyq2hKzBBhDXFtVQdfi7MWwhJZqrMQnxCvPxdZVrjVFfHlf YSNhZdHA==;
Received: from [172.58.211.142] (port=28318 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <touch@strayalpha.com>) id 1tKgST-00DNoo-37; Mon, 09 Dec 2024 11:18:06 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_DDDE560A-43F2-4F3C-A7BE-40CE398BC875"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
Subject: Re: [rfc-i] I-D expiry [was Re: RFCs vs Standards]
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <bf896cdd-7f49-420b-b499-f1597eaf9bcd@lear.ch>
Date: Mon, 09 Dec 2024 08:17:52 -0800
Message-Id: <7A3A7128-FEB3-4208-A5CF-A10BE651CE89@strayalpha.com>
References: <BE95E617-C929-43BA-BB40-41E189A8158B@akamai.com> <26439.33533.129915.244853@fireball.acr.fi> <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> <bf896cdd-7f49-420b-b499-f1597eaf9bcd@lear.ch>
To: Eliot Lear <lear@lear.ch>
X-Mailer: Apple Mail (2.3826.200.121)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Message-ID-Hash: JHGDYKJRZMCEMIY7UARRCNKL2ZMJVWJ4
X-Message-ID-Hash: JHGDYKJRZMCEMIY7UARRCNKL2ZMJVWJ4
X-MailFrom: touch@strayalpha.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: Christian Huitema <huitema@huitema.net>, Randy Bush <randy@psg.com>, Michael Richardson <mcr+ietf@sandelman.ca>, 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/iGEEYZSNohAtf6LerAL5zlJkf9Q>
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>

> On Dec 9, 2024, at 7:20 AM, Eliot Lear <lear@lear.ch> wrote:
> 
> What I care about is this:
> 
> The IETF community (and those generating IRTF and independent submissions) need a way to signal to the community that draft means just that: it's draft work, and not intended for broad deployment.  Otherwise, we end up with all of the support issues I mentioned earlier.
> 
> Eliot
> 

There’s no way to avoid that in any public message even it it is stated explicitly

Lots of things get deployed even when they aren’t in such messages.

I.e., that doesn’t seem avoidable.

Joe

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