IETF Logo Mail Archive

Re: Internet-Draft draft-rsalz-2026bis-00.txt is now available.

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 30 August 2024 20:40 UTC

Return-Path: <brian.e.carpenter@gmail.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 2C07BC14F6FB for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2024 13:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 DkvuoHu3p_hS for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2024 13:40:54 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62D07C14F695 for <ietf@ietf.org>; Fri, 30 Aug 2024 13:40:54 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-7c3ebba7fbbso1554216a12.1 for <ietf@ietf.org>; Fri, 30 Aug 2024 13:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725050454; x=1725655254; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=wzv/nUnbpqXrUp5LgeAxqQXUIZoUSIK1ZCiIhbflnFQ=; b=aRqwzH2GVDlZMTFifjTD/Fgn/ZJ6CGPGVe1wHWXJ7PZ+PkGxntvCDyVeIF49T+hCnl 67VUg/EAZ+uoNxeBKr87rDUU2mndordYAJUu9VqJz9g7HxtVu/cNbFfbe8XsRN6AC2C8 EfXxqVjfEP/k19Ut//gmylgZkF//+x+NBHE2+nwMMYZfF2pZ6CcDhIEg+3a3hqqRUVyv 1KRp7DzInRWEy7dg6D3aE/aWMWunS5otr8h5ZCR/6IXrSoG2kxQcn737kNWuAi0eeB/z vrzzHhjB2gsOVAoLW/qS5Yq5KozmJmLLAVvWmSKI7yf55/MOyMRoechdPNIb8TlQE5ia 8lBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725050454; x=1725655254; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wzv/nUnbpqXrUp5LgeAxqQXUIZoUSIK1ZCiIhbflnFQ=; b=GXpnBG3iinFLo7YFP94TPnW98cS3zgXsFMmTEOqCvOzZmsvXcciEHrXgLf8p5Qr5SE 78KP4k+U5Kt8zXBlfaYzIXic0Y87QuYac7SlQ8cBLZPIwAx2Q7JyGnpY2t+f4ZaygP4t X/kN1JCNIUtSx9IHGtmYVN+DWBJxpF1Wvg+WCifxFHOdd6nsaQ1SialkkOn2HRYLQxci Q37GgynrjvSVIVo2v6igX3OnvPp/576U8W6pVnagkHRtHqUrPXaZYt8QxikokRNBVJc+ zHPTwGWSd0eGpPeFPvdXLlB1rP2qmRozbGIBOxcw60yJhUiBsYkDD9IkXLVa2Du+yshM LJJw==
X-Gm-Message-State: AOJu0Yw7eTPVLd2Jo/dgDfAfBgRMEWWf6H0On4YlZffE6UO4l3dpmLwb MiawCmk/lrovqX+5Sq2DfsmUbbv/HKZMZRWR3658axd8DqUgyDNu0MwtFA==
X-Google-Smtp-Source: AGHT+IFTe0V+9rHKsRorpuf/Z4ebVZX2Myt4Atae2XHJhZvEzlEs24/eY3T1pD9TWZdlGb+QFKC5Vg==
X-Received: by 2002:a17:90a:8d18:b0:2d8:8a03:b90d with SMTP id 98e67ed59e1d1-2d88a03bbe0mr1495457a91.41.1725050453454; Fri, 30 Aug 2024 13:40:53 -0700 (PDT)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2d85b39d398sm4301323a91.42.2024.08.30.13.40.51 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 30 Aug 2024 13:40:52 -0700 (PDT)
Message-ID: <35cf0624-72a8-4a5d-9f9f-330dd9565f20@gmail.com>
Date: Sat, 31 Aug 2024 08:40:50 +1200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Internet-Draft draft-rsalz-2026bis-00.txt is now available.
Content-Language: en-US
To: ietf@ietf.org
References: <9253BAA6-2278-496E-8832-EEB802B54242@sobco.com> <63c4e784-f949-4d5c-97c6-889d2d5bca3a@gmail.com> <7FA8E1ACC4330226FD4A5EEE@PSB> <9a0d142e-057d-44f3-af6b-db72a603ecfd@gmail.com> <LV8PR11MB85369B446C582BF1352049FDB5942@LV8PR11MB8536.namprd11.prod.outlook.com> <4724.1724967198@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4724.1724967198@obiwan.sandelman.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: Y5LXLOLWBQWGV5L6ZQ7BN6UPDEVCWIOY
X-Message-ID-Hash: Y5LXLOLWBQWGV5L6ZQ7BN6UPDEVCWIOY
X-MailFrom: brian.e.carpenter@gmail.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
X-Mailman-Version: 3.3.9rc4
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/ly-uY-SUHUcPuEQuv6YBDHK8PD0>
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 30-Aug-24 09:33, Michael Richardson wrote:
> 
> Rob Wilton \(rwilton\) <rwilton=40cisco.com@dmarc.ietf.org> wrote:
>      > 3.  Split/migrate the existing IETF process into what must be in the
>      > RFCs/BCP and what moves to webpages (hopefully also incorporating
>      > appropriate IESG statements).  If we want to change core parts of the
>      > IETF process, i.e., the parts that are documented in BCPs, then this
>      > may be a time to consider this, but this could also be deferred, to
>      > reduce risk).  Moving text to webpages may be quite a lot of work, but
> 
> What kind of risks are you thinking here?
> 
> I think that the biggest risk is a 1000 message long debate over minutia
> which pisses off half the community, and we lose the energy to finish :-)

There's another risk, which is why I keep banging on about https://www.ietf.org/process/informal/: sheer complexity. Cleaning up RFC 2026 and RFC 2418 will be no means solve the problem. We have multiple process BCPs, multiple related Informational RFCs, multiple IESG statements, and multiple bits of folklore.

     Brian

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