Re: [Rswg] I-D Action: draft-rswg-rfc7990-updates-03.txt

John C Klensin <john-ietf@jck.com> Fri, 16 February 2024 23:27 UTC

Return-Path: <john-ietf@jck.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 46673C14F704 for <rswg@ietfa.amsl.com>; Fri, 16 Feb 2024 15:27:18 -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_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
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 hrgyY9bbhJVq for <rswg@ietfa.amsl.com>; Fri, 16 Feb 2024 15:27:16 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97D1DC14F6A6 for <rswg@rfc-editor.org>; Fri, 16 Feb 2024 15:27:13 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1rb7bq-000Oq0-9G; Fri, 16 Feb 2024 18:27:10 -0500
Date: Fri, 16 Feb 2024 18:27:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, rswg@rfc-editor.org
Message-ID: <9C03A39B154BBE06E8DB7678@PSB>
In-Reply-To: <98b8fa60-e738-5fe0-59c3-7f6c51079cdd@gmail.com>
References: <170794763921.33204.17986569217477876069@ietfa.amsl.com> <98b8fa60-e738-5fe0-59c3-7f6c51079cdd@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/my4ZmF7mzrL0d6vbJS3VnNYXFW0>
Subject: Re: [Rswg] I-D Action: draft-rswg-rfc7990-updates-03.txt
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: Fri, 16 Feb 2024 23:27:18 -0000


--On Saturday, February 17, 2024 08:58 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> dropping the requirement that the RPC use PDF/A-3 standard
> 
> I don't believe we have consensus on that and I don't agree
> with it. IMHO we should continue to require that. Yes, I know
> there are some loose ends but they aren't our loose ends.

Concur.  I think there may be consensus on not embedding the XML
but one of the big advantages of having a PMF form at all is
that a reader can be quite sure that what they are seeing when
they look at it is the same as what another reader will see even
if the times at which they look are separated by some years.
PDF/A was designed, by experts, to accommodate just that sort of
need.  Some random approximation to PDF doesn't do the job.
So, if there is a specific objection to PDF/A-3 that might
justify PDF/A-2 or even PDF/A[-1] instead, let's hear that
argument.  But dropping PDF/A entirely seems unwise to me.

best,
   john

> On 15-Feb-24 10:53, internet-drafts@ietf.org wrote:
>> Internet-Draft draft-rswg-rfc7990-updates-03.txt is now
>> available. It is a work item of the RFC Series Working Group
>> (RSWG) Editorial Stream Working Group of the IETF.
>> 
>>     Title:   Updated RFC Format Framework
>>     Authors: Paul Hoffman
>>              Heather Flanagan
>>     Name:    draft-rswg-rfc7990-updates-03.txt
>>     Pages:   11
>>     Dates:   2024-02-14
>> 
>> Abstract:
>> 
>>     In order to improve the readability of RFCs while
>>     supporting their archivability, the definitive version of
>>     the RFC Series transitioned from plain-text ASCII to XML
>>     using the RFCXML vocabulary; different publication
>>     versions are rendered from that base document.  This
>>     document is the framework that provides the problem
>>     statement, lays out a road map of the documents that
>>     capture the specific requirements, and describes how RFCs
>>     are published.
>> 
>>     This document obsoletes RFC 7990 and makes many
>>     significant changes to that document.  It also updates
>>     the stability policy in RFC 9280.
>> 
>>     This draft is part of the RFC Series Working Group
>>     (RSWG); see
>>     https://datatracker.ietf.org/edwg/rswg/documents/
>>     (https://datatracker.ietf.org/edwg/rswg/documents/).
>>     There is a repository for this draft at
>>     https://github.com/paulehoffman/draft-
>>     rswg-rfc7990-updates
>>     (https://github.com/paulehoffman/draft-rswg-
>>     rfc7990-updates).  Issues can be raised there, but
>>     probably should be on the mailing list instead.
>> 
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-rswg-rfc7990-updates/
>> 
>> There is also an HTMLized version available at:
>> https://datatracker.ietf.org/doc/html/draft-rswg-rfc7990-upda
>> tes-03
>> 
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-rswg-rfc7990-
>> updates-03
>> 
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>> 
>> 
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce