Re: [rfc-i] Update on the CSS - second round

Dave Thaler <> Wed, 22 February 2017 02:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 361EC12951F for <>; Tue, 21 Feb 2017 18:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mMcw0VnvLTzs for <>; Tue, 21 Feb 2017 18:53:40 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BC45012951E for <>; Tue, 21 Feb 2017 18:53:40 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 8B847B814F1; Tue, 21 Feb 2017 18:53:40 -0800 (PST)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 71F01B80A74; Tue, 21 Feb 2017 18:53:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 68J-eP0gNTfF; Tue, 21 Feb 2017 18:53:35 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTPS id 02343B805DB; Tue, 21 Feb 2017 18:53:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SgvJ/sLA8sfokxNfKfeWkIbXtZxjXdTjyVftjCj74ac=; b=MDdqM6c9Qfvy4Q8kWeost6IPgZcjW3eNI+d3HcZAg/mVFAhUJwh4LuI9QOVDq7ABqCAbBPI0n3r5w7SWgESNwY3BGYnM/Xmi8BrqKPX3nmHvn3mlRVUlcdeCOttkPdy1MaJpiq7ZFUhY1Mivu6+jEeH7n+OGZBnwcL+yym7qVdc=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Wed, 22 Feb 2017 02:53:32 +0000
Received: from ([]) by ([]) with mapi id 15.01.0919.018; Wed, 22 Feb 2017 02:53:32 +0000
From: Dave Thaler <>
To: Martin Thomson <>, "Heather Flanagan (RFC Series Editor)" <>
Thread-Topic: [rfc-i] Update on the CSS - second round
Thread-Index: AQHSjA8QpjXzSOv5aECo2Hnt4hOQTKF0SEwAgAAMltA=
Date: Wed, 22 Feb 2017 02:53:32 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: [2001:4898:80e8:a::452]
x-ms-office365-filtering-correlation-id: 0cf58d32-fc8a-42e5-91bb-08d45acdfd09
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:CY1PR03MB2265;
x-microsoft-exchange-diagnostics: 1; CY1PR03MB2265; 7:Q7Q2FxSHL53LojT2csDV+cVVhTiBOdQbn9uSA85gZDpnhilWQ5GioaHvkhNDnTbNyAso7i3z1serrjwFbypntnPD7eGsztZDdrjOJvEaZ3TNWumNAEQJebcoqRekC05kMZloyVkUM9j0ss5cr2UpAFLn+v1TwK+WGxT0x4e1AEm3JdjaTs87zYmXkhxI+p53CmF+LPmtngq+AW+dWVE1OAr+6/ym8ttLwzXfa7nVbVbEiP51zWamOgNIevPFxTgOyGsVMBnLHgG3Lx+TdbqwAbyB/jflT3e2wZlAiQSGFHtnkxvASVQkFn9hlmdyiUES6YnTbGR672sU0HSEbHhPQzRbrYGPGLyBqnwzXA19/bQ=
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(20161123558025)(6072148); SRVR:CY1PR03MB2265; BCL:0; PCL:0; RULEID:; SRVR:CY1PR03MB2265;
x-forefront-prvs: 022649CC2C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(39840400002)(39450400003)(39860400002)(39410400002)(39850400002)(15374003)(199003)(377454003)(24454002)(13464003)(189002)(7696004)(33656002)(99286003)(8936002)(10290500002)(68736007)(5660300001)(101416001)(25786008)(92566002)(55016002)(4326007)(2900100001)(8676002)(6506006)(3280700002)(39060400002)(6436002)(86362001)(81166006)(7736002)(9686003)(81156014)(86612001)(6306002)(77096006)(53546006)(229853002)(38730400002)(15650500001)(5005710100001)(76176999)(6116002)(2906002)(102836003)(2950100002)(50986999)(54356999)(97736004)(6246003)(53936002)(3660700001)(105586002)(74316002)(106356001)(122556002)(189998001)(305945005)(8990500004)(106116001)(10090500001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR03MB2265;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Feb 2017 02:53:32.3278 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR03MB2265
Subject: Re: [rfc-i] Update on the CSS - second round
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Cc: "" <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "rfc-interest" <>

Besides the double-comma issue, there's issues of spaces before commas in a number of the references (most obvious one being in RFC2811).
But that's also in the HTML source as Martin said.

-----Original Message-----
From: rfc-interest [] On Behalf Of Martin Thomson
Sent: Tuesday, February 21, 2017 6:06 PM
To: Heather Flanagan (RFC Series Editor) <>
Subject: Re: [rfc-i] Update on the CSS - second round

On 21 February 2017 at 17:52, Heather Flanagan (RFC Series Editor) <> wrote:

Hi Heather,

I checked these out on phone (with a decently large screen), desktop, and print preview.  These are all massive improvements and you seem to have found good resolutions to the issues I raised, thanks.

I don't think that the change to use Javascript for the table of contents on narrow views is an improvement.  It effectively removes the TOC from the document.  As a regular reader of these things, I need to see the table of contents.  Having to click or tap ruins that, especially since the button is on the very edge of what I can easily hit with my fat digits.

On narrower screens, leaving the TOC inline (where it would otherwise appear in the text version) is better.  The little hamburger icon could then be a link to the TOC.  That wouldn't require Javascript either, though that's not my overriding concern.

The other issues that I saw were all problems with the source.  For instance, the double-comma Brian observed was in the HTML source and easily corrected.  The precis document also uses something that appears to be a badly formatted definition list in the IANA considerations, but that turns out to be straightforward text with irregular spacing.
rfc-interest mailing list
rfc-interest mailing list