[Rswg] Presentation consistency (Re: Making the RFC 9280 text more specific
Jean Mahoney <jmahoney@amsl.com> Thu, 07 March 2024 00:27 UTC
Return-Path: <jmahoney@amsl.com>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D44C14F61F for <rswg@ietfa.amsl.com>; Wed, 6 Mar 2024 16:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ikE-ZqpXdlIO for <rswg@ietfa.amsl.com>; Wed, 6 Mar 2024 16:27:19 -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 C2792C14F61D for <rswg@rfc-editor.org>; Wed, 6 Mar 2024 16:27:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B39C1424CD3E; Wed, 6 Mar 2024 16:27:19 -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 w38Do4Ij8m_4; Wed, 6 Mar 2024 16:27:19 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id 86AF6424B427; Wed, 6 Mar 2024 16:27:19 -0800 (PST)
Message-ID: <b678337e-d3ba-4273-a7cc-16f390f1e0c9@amsl.com>
Date: Wed, 06 Mar 2024 18:27:18 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Paul Hoffman <paul.hoffman@icann.org>, RSWG <rswg@rfc-editor.org>
References: <3907C5D7-C729-46FD-9D59-0360391DB4D5@icann.org>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <3907C5D7-C729-46FD-9D59-0360391DB4D5@icann.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/fkBvwZ7bETcoYJWf2jbZaPEdQEo>
Subject: [Rswg] Presentation consistency (Re: Making the RFC 9280 text more specific
X-BeenThere: rswg@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Working Group \(RSWG\)" <rswg.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rswg>, <mailto:rswg-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg/>
List-Post: <mailto:rswg@rfc-editor.org>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rswg>, <mailto:rswg-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2024 00:27:23 -0000
Hi all, On 3/5/24 11:15 AM, Paul Hoffman wrote: > Greetings again. Eliot has proposed the following to make the references to RFC 9280 more specific: > https://github.com/paulehoffman/draft-rswg-rfc7990-updates/pull/25/files [JM] The text regarding consistent presentation gives me pause, specifically the use of the phrase "across the Series": RFCs are copyedited, formatted, published, and may be reissued to maintain a consistent presentation across the Series. The phrase also exists in -05: Similarly, as production tools change, publication versions can be regenerated to ensure a consistent presentation across the series. Reissuing RFCs that are in RFCXML v3 is one thing (which still requires careful consideration and testing), maintaining presentation consistency across the entire Series _across time_ is another. Right now, the Series is mostly consistently presented due to the text publication format. The addition of the property "The series as a whole is consistently presented" could become an impediment to changing publication formats in the future. For instance, there have been discussions of dropping the text publication format because it lacks the features of HTML and PDF. If presentation consistency across the entire Series is a property we want, and the text format is the only thing that can provide that property because it would be a huge undertaking to convert the pre-v3 RFCs to RFCXML format so that they could be kept consistent with newer RFCs (and not all could be converted, for example, see RFC 8 [1]), then the text format would have to remain. Best regards, Jean [1] https://www.rfc-editor.org/info/rfc8 > > Please discuss this topic here. > > --Paul Hoffman >
- [Rswg] Making the RFC 9280 text more specific Paul Hoffman
- Re: [Rswg] Making the RFC 9280 text more specific Salz, Rich
- Re: [Rswg] Making the RFC 9280 text more specific Robert Sparks
- Re: [Rswg] Making the RFC 9280 text more specific Eliot Lear
- [Rswg] Presentation consistency (Re: Making the R… Jean Mahoney
- Re: [Rswg] Presentation consistency (Re: Making t… Brian E Carpenter
- Re: [Rswg] Presentation consistency (Re: Making t… Julian Reschke
- Re: [Rswg] Presentation consistency (Re: Making t… Jean Mahoney
- Re: [Rswg] Presentation consistency (Re: Making t… Carsten Bormann
- Re: [Rswg] Presentation consistency (Re: Making t… Carsten Bormann
- Re: [Rswg] [Ext] Making the RFC 9280 text more sp… Paul Hoffman
- Re: [Rswg] Presentation consistency (Re: Making t… Eliot Lear