Re: [rfc-i] NO policy in Style Guide, please
Jean Mahoney <jmahoney@amsl.com> Wed, 21 February 2024 23:35 UTC
Return-Path: <jmahoney@amsl.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FCFC14F736; Wed, 21 Feb 2024 15:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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
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 YjoK41-TLn_E; Wed, 21 Feb 2024 15:35:01 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 E5B61C14F70D; Wed, 21 Feb 2024 15:34:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D713F424CD3E; Wed, 21 Feb 2024 15:34:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZqBsJjPs-gj; Wed, 21 Feb 2024 15:34:48 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 9F8AA424CD01; Wed, 21 Feb 2024 15:34:48 -0800 (PST)
Message-ID: <4de4d61d-81cd-4a2b-90f7-476572300582@amsl.com>
Date: Wed, 21 Feb 2024 17:34:47 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, RFC Interest <rfc-interest@rfc-editor.org>, "rswg@rfc-editor.org" <rswg@rfc-editor.org>
References: <b00b1540-1c8c-4ef5-ba12-7949d444ad35@amsl.com> <d4ceb0b0-b361-4fbc-9a42-8e2780851b79@it.aoyama.ac.jp>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <d4ceb0b0-b361-4fbc-9a42-8e2780851b79@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/hUDctcXSqOPx2zTodkK1TGyZhGA>
Subject: Re: [rfc-i] NO policy in Style Guide, please
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2024 23:35:05 -0000
Martin, On 2/21/24 5:09 PM, Martin J. Dürst wrote: > Hello Jean, others, > > [copying RSWG] > > On 2024-02-21 23:37, Jean Mahoney wrote: >> Hi all, >> >> The RPC has added guidance on the use of links in documents. Please >> see the Web Portion of the Style Guide at >> <https://www.rfc-editor.org/styleguide/part2/#links>. > > Thanks for the pointer. I have comments on a few items. I'll use a > separate mail for each of them. > > The text you point to says: > "There is no hard limit on the number and frequency of links in > documents, and a limit should not be defined by policy." > > I definitely agree with the substance of this sentence. However, there's > a very big problem here. There are continuing occasional discussions in > the RSWG about what is and isn't, or should and shouldn't, be policy > (for which the RSWG is responsible) and what not. > > My personal take on this is that "we will know it when we see it", and > "whatever the RSWG thinks is policy is policy", so my position is that > abstract discussions about the border of policy are mostly a waste of time. > > However, it is very clear that it's the RSWG that defines policy > (whatever that is), which includes saying (if necessary) what is not > policy. A statement in the Style Guide saying that something "should not > be defined by policy" is therefore completely out of place. [JM] Yes, we can update the sentence by deleting the mention of policy: "There is no hard limit on the number and frequency of links in documents." > > If there should ever be an attempt in the RSWG to define any kind of > policy on the number of links in an RFC, I see absolutely no problem > with somebody from the RPC contributing to that discussion and arguing > that such a policy would be a bad idea. And I definitely would agree > with that. > > But putting anything like this in a style guide isn't appropriate. If it > wasn't intended that way, please explain it and fix it so that it's not > misunderstood. If there are other places in the Style Guide that contain > similar wording, please fix them, too. [JM] I've opened an issue for draft-rpc-rfc7322bis. Best regards, Jean > > Regards, Martin. > >> Best regards, >> Jean >> >> >> _______________________________________________ >> rfc-interest mailing list >> rfc-interest@rfc-editor.org >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Guidance on linking added to the Web Port… Jean Mahoney
- [rfc-i] NO policy in Style Guide, please (was: Re… Martin J. Dürst
- Re: [rfc-i] NO policy in Style Guide, please Jean Mahoney
- Re: [rfc-i] NO policy in Style Guide, please Eliot Lear
- Re: [rfc-i] NO policy in Style Guide, please Jean Mahoney
- Re: [rfc-i] Guidance on linking added to the Web … Jean Mahoney
- Re: [rfc-i] NO policy in Style Guide, please Martin J. Dürst
- Re: [rfc-i] Guidance on linking added to the Web … Martin J. Dürst