Re: [xml2rfc] RfcMarkup not authoritative, HTML is gone?

Stewart Bryant <stewart.bryant@gmail.com> Mon, 16 September 2019 19:24 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57CB11200CC for <xml2rfc@ietfa.amsl.com>; Mon, 16 Sep 2019 12:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2n6cse8PZIrz for <xml2rfc@ietfa.amsl.com>; Mon, 16 Sep 2019 12:24:46 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A6261201C6 for <xml2rfc@ietf.org>; Mon, 16 Sep 2019 12:24:46 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id t3so519947wmj.1 for <xml2rfc@ietf.org>; Mon, 16 Sep 2019 12:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9j/w7cZO0qLyI7f2BOJAc3eLPxN4ngMBuLUH9o4SlO8=; b=T0IYqY8lE7l/KK8D7UtRlB3YfMPvWXouSa8kUpDeUCVksgF02xii7m28/3eemistXb LvAO7D6MyQsv/C3Adj+JltU6Pe40paHOiWUbX1qb9lBoRbFChgEVXs1TsYlEdfmmxgqR e0FgBUPE66mokmeBAMAk/d2vZmDOT+yZBLgjF5hzurWHI/2xO09KWCr7/JkamSxA6Vd/ HTCxw2pAQWQHemUlXspCeJkaBNqSKowNafIQEcEVtdhD8LGjpxhrQy3kQVWF1yZVPMqJ PO9aVNzeNVQ9bDaHcqBuiPg5PuGbdoeuHp8eqjjjGU7RaDpllbMYOAasemupCxQy8K47 aqag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9j/w7cZO0qLyI7f2BOJAc3eLPxN4ngMBuLUH9o4SlO8=; b=DwtkoGBVQGsDmlaIta5NB4GDixYBMX6E+NryUTdx0VOMDCnfmaylNKtVuZRQWo7ZSv 6FtHHV0pZCpbzhCSfiqRur1xODSg9NpOIGYRYxTIEPafRck/SAqlF4cZNHiJqrReSegq KwSIy5ey2C3PtSJMH/rqF4Ng+QbBpSOohFFPNBnLHCSyT+N+xEk1503tzN1hALWNYahb rL6pzKb6i2NE0dz/mCKnYsj8QSkeBf81DhEX1PWkz1Hz2X661kB1EXhMR+3VSN25rwtb QO9GLUVhqUZCoC4MU4kUCxImxR1QWzKJNw2fqNdlD/M4O4hodXmbWw6RzQ3Ut3nB8xoE rmGQ==
X-Gm-Message-State: APjAAAUzoksHP3hFhrUgv00Fj7fIk3hqsoMJrHP4gqL8UOwf0qgX9+Jz 0o+yMT9yiP/GPt8B2CSFf1zB/e8w
X-Google-Smtp-Source: APXvYqzC0Dj+rlNR/vIr5EzqeCXH3+7VnpavE57hLm6cCX8XZdAyP8ToEHUOOigkAjgI0QcwpZvg9A==
X-Received: by 2002:a1c:1d4:: with SMTP id 203mr493117wmb.104.1568661884398; Mon, 16 Sep 2019 12:24:44 -0700 (PDT)
Received: from [192.168.178.22] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id h63sm59084wmf.15.2019.09.16.12.24.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Sep 2019 12:24:43 -0700 (PDT)
To: "Andrew G. Malis" <agmalis@gmail.com>, Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc@ietf.org
References: <94358f7d-3465-4161-1597-f1dbfba73b3f@gmail.com> <d44ac5f1-e4c2-1239-4bea-714a721115b8@levkowetz.com> <9ceb0697-c3ae-4f14-606c-4e089f04e2f2@gmail.com> <a4874a50-ffc3-80f5-cb42-09f82072644c@gmx.de> <04713f10-5c19-2ad5-2fa6-2db5f1ed5599@gmail.com> <f5554cd0-9c74-3a8c-5af9-25b947d499d8@gmx.de> <7bb2a5fb-262d-39b5-3bb0-72e068923ea7@gmail.com> <c3c8db0e-e719-32e6-ca3c-736e25ce8936@gmx.de> <f2f49552-091d-50e4-e2e2-2fdd30cbb7ae@gmail.com> <bd07ad5a-a0a7-f821-54ec-c09ee5614e2a@gmx.de> <d9883584-1d5e-4d34-9bde-00d32dc49435@gmail.com> <599cb714-89e8-271c-4d5e-ba294fa7d3cf@alum.mit.edu> <ee1a1699-a5e3-3c2b-ad53-ff80a120f7eb@gmail.com> <19509146-279f-4fb7-4b44-3feea81e87f9@alum.mit.edu> <37d53cf7-3e99-e4dc-d66a-7bd452e0f3ea@gmx.de> <CAA=duU0OD8c93v3efFPtHB-wuJAa0RZTF_ShV+G1T1Tow9XqMw@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <22f2fb6e-de1f-d1fd-a167-39e7622953e3@gmail.com>
Date: Mon, 16 Sep 2019 20:24:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAA=duU0OD8c93v3efFPtHB-wuJAa0RZTF_ShV+G1T1Tow9XqMw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/dVGdet0h50IOXKSUVkShnjfjwyM>
Subject: Re: [xml2rfc] RfcMarkup not authoritative, HTML is gone?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 19:24:53 -0000


On 16/09/2019 17:36, Andrew G. Malis wrote:
>  > PDF RFCs have been possible in the past, but certainly not encouraged.
> 
> In the PALS WG, we did an RFC where the PDF is the "canonical" output ( 
> https://tools.ietf.org/pdf/rfc7893.pdf ). Check out the figures and 
> you'll see why. In the upcoming V3 world, we would be able to do this 
> with the HTML version as well. except that SVG figures will be black and 
> white only (a definite drawback in this case, esp. for figures 5-8).
> 
> Cheers,
> Andy
> 

.. and RFC5317 the text version being a pointer to the pdf which carried 
a set of slides jointly agreed with the ITU.

However the most famous was RFC1305 which defines NTPv3 (NTPv2 was 
published in PS format)

My experience has always been that if you had a good reason for 
publishing in pdf was always possible and perhaps authors should have 
pushed a bit harder.

- Stewart