IETF Logo Mail Archive

Re: [Gendispatch] A gendispatch session at IETF 118?

Rob Sayre <sayrer@gmail.com> Wed, 06 September 2023 19:04 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04673C1519B0 for <gendispatch@ietfa.amsl.com>; Wed, 6 Sep 2023 12:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 cyEm2lGr0KGq for <gendispatch@ietfa.amsl.com>; Wed, 6 Sep 2023 12:04:14 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BD96C14F74A for <gendispatch@ietf.org>; Wed, 6 Sep 2023 12:04:14 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-52c9be5e6f0so113532a12.1 for <gendispatch@ietf.org>; Wed, 06 Sep 2023 12:04:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694027053; x=1694631853; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AUHjKww+U5Y/9S8gfYou1TahBpjCCdpanO2ImpgMF1E=; b=KzKCw4q9qulN1fpASdgSgD0rOwY9ngIDutR/Anhw8DrcjI6/slBHKVT9c2lrYYMgxT 9CgkLFK3HlgARL5jHE1WP85kyPaO2RbrOsZHe8VP6YNO2nGlvu3S+Xb/6agnAqNZs9t3 9KLT/Fsu9dmvpZoFl7DhIArCvYyYoV3wGmP+NvUto5vd+HynAi2EvN/5P9XAWCzTOZy3 kD3khpGi8jZI7/K9d8OsdbvZLUOyl/JP4+Z+TVEc61swuoYrO3PH1toPFpGEzBvaRCLW 9zV/ypLj/01WmgD4fKnNoJSYPekTXlpJpOVBJiS+JeEYN2eDIJ8B59wN2zzwHtcfNvBX nBzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1694027053; x=1694631853; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AUHjKww+U5Y/9S8gfYou1TahBpjCCdpanO2ImpgMF1E=; b=P2mDPMwNQbQE1N6e5cUCBQczI12ygm6zz7BS6u8CR0lxJZMA0YpdnqWErAg/Z0c3gY VQbkWLr5X/E7Pywu9SDSsyvgt0ukFDHLnKS4yBVNn5BaVDpH8qqfk3jnyAyLcezex8YH spmcZrU36dZHU/PL/1HsqrLzpKUbPSbA9vCYve1dEntWsjHUsst60rL9cmedugxf8NuA 3LefdE8Evgc3e97VEfhnvjjHavkY6c+UYSlU5YcfiTm6FjIKWR8ci+jUqXsJFnAJU+NF 1FS3nOX/LD4bb9UyDgb+qRYJBR7bHB1z7FqKzdHs+Pmp9wUVjRw1SvyAXMvQ53hfVTrF 9T5A==
X-Gm-Message-State: AOJu0YzthYKIyiuh32IflYq3GEnaHDEw1LnIE/FZqKLLf724gYwpSPVp OS//4diLDWcG632/v1KxrTBLEF2HS7Gk2WwJW8Q5Z40/CfVTnw==
X-Google-Smtp-Source: AGHT+IFMbNJJYu8bjVrdSpCUOGivwkZvHGW5rfeN3oUbG7uOF4d1+2fDCL98qcV8C7bdYqCBJwcZFDRG/MRJyvimm7Q=
X-Received: by 2002:a50:fb98:0:b0:522:3a37:a463 with SMTP id e24-20020a50fb98000000b005223a37a463mr2957757edq.20.1694027052350; Wed, 06 Sep 2023 12:04:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SwpLsJ0S4jkvWL4DPys0Y9pvJwWhZtbr7E6fvFioRpsEQ@mail.gmail.com> <e3aee3c9-fb21-2e83-a351-d8f347e0f764@lear.ch>
In-Reply-To: <e3aee3c9-fb21-2e83-a351-d8f347e0f764@lear.ch>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 06 Sep 2023 12:04:00 -0700
Message-ID: <CAChr6SyC1vsBLmWVKjB2tgC3amDeqVACJFhhaTp4VkQXt=oNLQ@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Cc: GENDISPATCH List <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b201130604b56892"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/gkqmb_bg5MLIR_TuoyuUE53-qPU>
Subject: Re: [Gendispatch] A gendispatch session at IETF 118?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2023 19:04:18 -0000

On Tue, Sep 5, 2023 at 10:54 PM Eliot Lear <lear@lear.ch> wrote:

>
> On 06.09.23 06:38, Rob Sayre wrote:
> > Hi,
> >
> > > Paul and I just submitted
> >
> https://datatracker.ietf.org/doc/html/draft-thomson-gendispatch-no-expiry-01
> >
> > I'm in favor, but maybe not for the same reasons.
> >
> > Doing things this way will let you just publish an I-D in the old way,
> > and I think that way is better.
> >
> What was the old way?
>

Ah, I didn't know it went all the way back to RFC 1310.

Anyway, that document, and all of the newer versions say "Under no
circumstances should an Internet Draft be referenced by any paper, report,
or Request for Proposal." But, of course, people do that all the time now.

I think the aim is to prevent confusion with RFCs. I'd say it's ok to let
that confusion exist. I don't think anyone not in this mailing list
universe knows the difference between IETF/IRTF/ISE etc anyway. If those
processes don't provide value (usually they do!), I think it's fine to
archive an I-D with no expiration.

thanks,
Rob

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