IETF Logo Mail Archive

[rfc-i] Re: rfc-i Q: Terminology and standards references...

Toerless Eckert <tte@cs.fau.de> Wed, 29 April 2026 15:13 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: rfc-interest@mail2.ietf.org
Delivered-To: rfc-interest@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 919DDE5BD32B for <rfc-interest@mail2.ietf.org>; Wed, 29 Apr 2026 08:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777475600; bh=Fj03oVvp8KEO4ppmpNChvK260xmtD41DB5ocN4DO+vU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=gdOKkNz2LlzR1R4ybh+xjfrtrglm2KOcUmEdgVPf85H6KqLKEloWnQmTeJeAVpov1 BbHGpJyEtu5uTVAYGuJr1YyG+I2iBvsrV1liRri3FX1M9dVEAiEPOpX7N8YdDER5Dv wmsguFuygoVm6Q4L29q/29uNZROk4/nXU6kndFIU=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cs.fau.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HRjOzbdbE5v for <rfc-interest@mail2.ietf.org>; Wed, 29 Apr 2026 08:13:17 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 mail2.ietf.org (Postfix) with ESMTPS id 10BE7E5BD1BF for <rfc-interest@rfc-editor.org>; Wed, 29 Apr 2026 08:13:04 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4g5LQX1VdRz1RCpF; Wed, 29 Apr 2026 17:12:52 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.fau.de; s=r20250630-faui40; t=1777475574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BNDJsjmWGN6aDVTJU8yKT55bK+ix7tkj9mqd/tLWgT8=; b=seFiegRhAxkT1PUoOdtwfmlaYlSrxJnjuShRhAOsT/kPzgzoXk1bhq6Sm6ylP+69ormqKa INO9p2fPHkFYiX8mAXbwJPqXY9rH+fQ4Ee5Y8ePv9c3T3BCN4NtKPgqGlPg3aabyTQIoSL FscCInU7YVb6myadvIwEsJPavaW+Xb01I1DM383B3Wkjc1n2kG5u0A+T64YBAXB27/boxI 2qr5BLr8CVgvkvrlRowkUOcmBk5D4xKefBbDJEKbc6+RQ7UWh/4qXeyfGu4jLOussJAP6I QHHHdohIlzMUBby0Ce91fhQI7EjTpOriGQ2ym5LeC+28a/QOBhUHo4Sa2ud7yA==
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4g5LQW74xczl3hv; Wed, 29 Apr 2026 17:12:51 +0200 (CEST)
Date: Wed, 29 Apr 2026 17:12:51 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <afIf84Jt5U-XYi3H@faui48e.informatik.uni-erlangen.de>
References: <ae-KoxY5i2ldwn3V@faui48e.informatik.uni-erlangen.de> <EC374DB7-F301-44D7-8904-6F8CB3F9003D@tzi.org> <cju89-HFMpLSvSIzgJBzkSLRJmv4ihMd4fvINuQAhzbZt91W03Y9mmT74VBrRGsV-f7XC2djmiaxCvzv1idS_m98IoppRwP6u-Huy8tXUWU=@ounsworth.ca> <2ee61dde-f649-4051-aaf6-62e055fa3f3c@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2ee61dde-f649-4051-aaf6-62e055fa3f3c@gmail.com>
Message-ID-Hash: LPXV2NMGBG77A2XUJJTPD2NAXHU53C37
X-Message-ID-Hash: LPXV2NMGBG77A2XUJJTPD2NAXHU53C37
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rfc-interest.rfc-editor.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Mike Ounsworth <mike@ounsworth.ca>, Interest RFC <rfc-interest@rfc-editor.org>, Working Group Chairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rfc-i] Re: rfc-i Q: Terminology and standards references...
List-Id: "A general discussion list about the RFC Series and its operational processes." <rfc-interest.rfc-editor.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/_TZip1fHhAoDNf-KM1mqF299GgA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Owner: <mailto:rfc-interest-owner@rfc-editor.org>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Subscribe: <mailto:rfc-interest-join@rfc-editor.org>
List-Unsubscribe: <mailto:rfc-interest-leave@rfc-editor.org>

On Tue, Apr 28, 2026 at 08:42:29AM +1200, Brian E Carpenter wrote:
> BTW this is an IETF process discussion, not an RFC editing discussion.

So, what would have been a better list to discuss - ietf@ietf.org seems too broad
and there is no authors@ietf.org (even though i asked i think several times) ...

Cheers
    Toerless

>     Brian
> 
> > 
> > 
> > -Mike
> > 
> > "Knowing is a barrier which prevents learning" -- Frank Herbert, Dune.
> > 
> > 
> > "An expert is a person who has found out by his own painful experience all the mistakes that one can make in a very narrow field.” -- Niels Bohr
> > 
> > On Monday, April 27th, 2026 at 11:28 AM, Carsten Bormann <cabo@tzi.org> wrote:
> > 
> > > On 2026-04-27, at 18:11, Toerless Eckert <tte@cs.fau.de> wrote:
> > > > 
> > > > Wondering: I a standards track draft/RFC explicitly uses (lets say for the
> > > > terminology from some other RFC:
> > > > 
> > > > Does this make the reference to that other RFC normative or can it stay
> > > > informational - if it would be informational without that terminology inheritance ?
> > > 
> > > Is the terminology used in a normative way?
> > > 
> > >     The knarf MUST NOT keep a connection to a gnorpy node open for more than 60 seconds.
> > > 
> > > If the definition of gnorpy is in the referenced document, this is a normative reference.
> > > 
> > > Grüße, Carsten
> > > 
> > > 
> > 
> > _______________________________________________
> > rfc-interest mailing list -- rfc-interest@rfc-editor.org
> > To unsubscribe send an email to rfc-interest-leave@rfc-editor.org

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