
From nobody Sat Nov  9 09:21:51 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFF41200C5 for <art@ietfa.amsl.com>; Sat,  9 Nov 2019 09:21:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level: 
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 12jZAbjsIqn8 for <art@ietfa.amsl.com>; Sat,  9 Nov 2019 09:21:47 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5121D12001E for <art@ietf.org>; Sat,  9 Nov 2019 09:21:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=fAtAE2n4Lj9Y03c/YB7WmOMFGtS3c1Ihsf0xxif841w=; b=u0xxjalgBs+ozl+dbeZQtX2Sjx zF6ZwP6/WRtVpx2nydrkpGBknXifOzmKl7C05qu7ZZ5FmLhECLu//flaGN0903084gz94XQ8XbGEr R4dnPVHOIgjXozzfVThwasEvtXEjs6eRDo1nDBjXqvDvvzx4jAXrtkeCdQZ1kJJwih8EuNHlDk3P5 owEvHAcJODKRG/BlO6o87mjCaSAjbnWA0rG8XvkH80uO6tZxXeCSWWjMPFXzCry3Ym3RvFG+UNBF4 ERTXISovaKbDH0HOD67LHVwrewzOXItmTi2GnKNi3B7ztWm4GgO7FY+85bqoMYU6kVctiDIGkqMei YLP0i7eA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:60350 helo=[192.168.1.13]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iTUQf-000UFB-QG; Sat, 09 Nov 2019 12:21:46 -0500
To: Tony Finch <dot@dotat.at>
Cc: "art@ietf.org" <art@ietf.org>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com>
Date: Sat, 9 Nov 2019 09:21:39 -0800
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: <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/nl9m4I8IeuK9uLdydtr6XJuNoTk>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Nov 2019 17:21:49 -0000

Hi, Tony,

While addressing these comments, I had a few notes below.

Joe

On 9/13/2019 12:41 PM, Tony Finch wrote:
...
>    o  Ordering: to determine the relative sequence of events across
>       systems, such as with Lamport clocks [La78] or Vector clocks
>       [Fi88][Ma88].
>
> Lamport clocks and vector clocks don't use time, but the section heading
> implies that they do.

It depends on how you interpret 'time'. If it's a sequence of labels
used for absolute and relative ordering, then they are. They're just not
continuous with respect to "natural time", but then nearly all time
scales have that property in one way or another.

>    o  NTP [RFC5905]: the Network Time Protocol, used in the Internet to
>       synchronize local clocks, in which dates are indicated by UTC
>       values. NTP times track the time of the clock they connect to.
>
> NTP uses a unix-style count of seconds so it isn't able to represent UTC
> values.

The doc describes the time NTP provides not its representation in its
protocol messages. It claims to sync within a few ms of UTC.

>  The NTP leap indicator bits are not synchronized with the
> occurrence of leap seconds so they don't disambiguate leapy timestamps.
> https://trac.ietf.org/trac/ntp/wiki/NtpVersionFourIssues

This is an issue with the protocol - that's not the focus of this doc.

> 4.3. Comparison of properties
>
> Should the discussion of GLONASS etc. be moved to section 5 before the
> table in which they occur?

It was left where it is; the table is just a summary of those systems.

> Should PTP be added to the list of time scales? (Given section 7 talks
> about selecting timescales I think it's worth pointing out one that is of
> practical use in computing, as opposed to TAI which is a retrospective
> paper clock.)

PTP isn't a time scale; it's a system for reporting time. The problem is
it reports multiple timescales that are already discussed.

I.e., the doc talks about time scales and systems that report ONE
timescale; not all protocols for representing or syncing timescales.

>    Unix time does not specify the definition of a 'second' or 'day',
>    and so it is not clear whether it intends to track SI seconds (where
>    time would be uniform) or solar time (where it would not).
>
> Unix time is defined in terms of struct tm fields, which are a
> representation of a UTC time stamp. It explicitly says it doesn't
> specify any relationship to real civil time.

Civil time is neither SI nor solar. The statement above explains that
even the duration of a second or day isn't defined for Unix time.

> ...
>
> Google deployed leap smear in 2011 (not 2017 as your reference states) and
> they weren't the first to propose it.

2017 is the date of the published archival reference. That's not a
statement of when it was deployed, which this document doesn't include.

> 7.2. Hazards of some time scales
>
> It's worth mentioning that if you aspire to representing UTC correctly
> then it cannot be done as a simple count of seconds, and Unix and NTP are
> shining examples of getting it wrong.
>
> There should be a discussion of leap-second-related hazards in Unix time
> and NTP.
This isn't a time protocol design doc or advice on which protocol to
use; it is advice on how to pick a time scale.
> The draft seems to give the impression that leap smear is a Google
> peculiarity, but there are several other organizations doing it (see the
> link to the leapsecs list above).

It mentions Google only as notable examples.

--



From nobody Mon Nov 11 06:37:40 2019
Return-Path: <dot@dotat.at>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E35B612009C for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 06:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 uNvtKBMj1ZRA for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 06:37:36 -0800 (PST)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [131.111.8.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6513112007C for <art@ietf.org>; Mon, 11 Nov 2019 06:37:36 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:56044) by ppsw-33.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1iUAov-001WPN-ig (Exim 4.92.3) (return-path <dot@dotat.at>); Mon, 11 Nov 2019 14:37:33 +0000
Date: Mon, 11 Nov 2019 14:37:33 +0000
From: Tony Finch <dot@dotat.at>
To: Joe Touch <touch@strayalpha.com>
cc: "art@ietf.org" <art@ietf.org>
In-Reply-To: <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com>
Message-ID: <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/icCOsRmSUxwU6z06bszkMfgtGFI>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2019 14:37:39 -0000

Joe Touch <touch@strayalpha.com> wrote:
> On 9/13/2019 12:41 PM, Tony Finch wrote:
> ....
> >    o  Ordering: to determine the relative sequence of events across
> >       systems, such as with Lamport clocks [La78] or Vector clocks
> >       [Fi88][Ma88].
> >
> > Lamport clocks and vector clocks don't use time, but the section heading
> > implies that they do.
>
> It depends on how you interpret 'time'.

I meant in the usual sense, as implied by the draft's terminology section.

> >    o  NTP [RFC5905]: the Network Time Protocol, used in the Internet to
> >       synchronize local clocks, in which dates are indicated by UTC
> >       values. NTP times track the time of the clock they connect to.
> >
> > NTP uses a unix-style count of seconds so it isn't able to represent UTC
> > values.
>
> The doc describes the time NTP provides not its representation in its
> protocol messages. It claims to sync within a few ms of UTC.

Your wording "UTC values" to me implies a vague description of the
representation of the timestamps. Perhaps you could re-word it to make it
clear that you meant something else.

> > Should PTP be added to the list of time scales? (Given section 7 talks
> > about selecting timescales I think it's worth pointing out one that is of
> > practical use in computing, as opposed to TAI which is a retrospective
> > paper clock.)
>
> PTP isn't a time scale; it's a system for reporting time. The problem is
> it reports multiple timescales that are already discussed.

The impression I get is that although PTP can transport different
timescales, it almost always uses a specific one which is different from
the other ones in the draft. (It differs from Unix time by the number of
leap seconds.)

It's a widely-available timescale, like many of the others listed in that
section, and I think readers would be surprised that it isn't listed in a
draft that's providing advice on choosing timescales.

> >    Unix time does not specify the definition of a 'second' or 'day',
> >    and so it is not clear whether it intends to track SI seconds (where
> >    time would be uniform) or solar time (where it would not).
> >
> > Unix time is defined in terms of struct tm fields, which are a
> > representation of a UTC time stamp. It explicitly says it doesn't
> > specify any relationship to real civil time.
>
> Civil time is neither SI nor solar. The statement above explains that
> even the duration of a second or day isn't defined for Unix time.

The problem with that paragraph is it sets up a false dichotomy. Unix time
does not intend to track solar time nor SI seconds, it tracks civil time,
which is a different third option. Leaving that option out is misleading.

> > Google deployed leap smear in 2011 (not 2017 as your reference states) and
> > they weren't the first to propose it.
>
> 2017 is the date of the published archival reference. That's not a
> statement of when it was deployed, which this document doesn't include.

   [Go17]    Google's approach to NTP leap smearing, proposed in 2017.
             https://developers.google.com/time/smear

The date 2017 doesn't appear on that page, and the page itself says
deployed in 2008 so I'm not sure why you say it isn't included. (I think I
got 2011 from my mail archives...) The reference doesn't match the title
nor the contents of the page it refers to.

> > 7.2. Hazards of some time scales
> >
> > It's worth mentioning that if you aspire to representing UTC correctly
> > then it cannot be done as a simple count of seconds, and Unix and NTP are
> > shining examples of getting it wrong.
> >
> > There should be a discussion of leap-second-related hazards in Unix time
> > and NTP.
>
> This isn't a time protocol design doc or advice on which protocol to
> use; it is advice on how to pick a time scale.

Exactly why I think it should discuss hazards of bad representations of
time. Especially since two of the main time systems it discusses suffer
from such bad representations.

> > The draft seems to give the impression that leap smear is a Google
> > peculiarity, but there are several other organizations doing it (see the
> > link to the leapsecs list above).
>
> It mentions Google only as notable examples.

Perhaps you could re-word it to make that more clear.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Southeast Iceland: Southeasterly 6 to gale 8, occasionally severe gale 9 at
first, backing northeasterly 4 to 6. Very rough or high, occasionally very
high in west at first. Rain. Good, occasionally poor.


From nobody Mon Nov 11 07:05:30 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B73A12086A for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 07:05:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 gchEeRztDhGa for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 07:05:26 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B2612000F for <art@ietf.org>; Mon, 11 Nov 2019 07:05:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=PKF9e+fbbQzDN2eg20Yhk/scguEsyW8SHT4agXUyFec=; b=qbHw+n+CISgIYjMGy1+9n13oO y5styJj66ekxT8Ry1F2yWIryebhpvYzh+1iMZt97IXLpAci0VojstZlo65EgykmiHa9Y1acmF1I3u 7LeZzzaTgnZK7SBqWhcPSOHtwX0aYnZRvo6RwVu2Wuif2AFqQl+MA3319oh0THCpzQHXHJk4/ueyZ MTu2+Sg6b7GWqj4PL7AT48npdcBdVCzfOsYcsWT0rd4MZnxlkQPmqFoERGnik1TfBxN9ohQLcGKwy qOqqi6bGxEiZfSL1iexTqLypOUQxf5Frx2ekdk91yBpntxMyZPF7xVyZhYJrocDHoM/cyU3FLEAAp DtalqmPrw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:52678 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iUBFo-0031Ub-5X; Mon, 11 Nov 2019 10:05:25 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_9B25D19C-4341-4532-A635-4C76821AFAC0"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk>
Date: Mon, 11 Nov 2019 07:05:18 -0800
Cc: "art@ietf.org" <art@ietf.org>
Message-Id: <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/NvAcGzXmRalKII3Oi71WIlNw0R8>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2019 15:05:28 -0000

--Apple-Mail=_9B25D19C-4341-4532-A635-4C76821AFAC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, Tony,

> On Nov 11, 2019, at 6:37 AM, Tony Finch <dot@dotat.at> wrote:
>=20
> Joe Touch <touch@strayalpha.com> wrote:
>> On 9/13/2019 12:41 PM, Tony Finch wrote:
>> ....
>>>   o  Ordering: to determine the relative sequence of events across
>>>      systems, such as with Lamport clocks [La78] or Vector clocks
>>>      [Fi88][Ma88].
>>>=20
>>> Lamport clocks and vector clocks don't use time, but the section =
heading
>>> implies that they do.
>>=20
>> It depends on how you interpret 'time'.
>=20
> I meant in the usual sense, as implied by the draft's terminology =
section.

They=E2=80=99re a bit like Schrodinger=E2=80=99s cat - they jump only =
whey you look at them (or would need to). IMO, they are time scales for =
that reason.

>=20
>>>   o  NTP [RFC5905]: the Network Time Protocol, used in the Internet =
to
>>>      synchronize local clocks, in which dates are indicated by UTC
>>>      values. NTP times track the time of the clock they connect to.
>>>=20
>>> NTP uses a unix-style count of seconds so it isn't able to represent =
UTC
>>> values.
>>=20
>> The doc describes the time NTP provides not its representation in its
>> protocol messages. It claims to sync within a few ms of UTC.
>=20
> Your wording "UTC values" to me implies a vague description of the
> representation of the timestamps. Perhaps you could re-word it to make =
it
> clear that you meant something else.

Will do.

>=20
>>> Should PTP be added to the list of time scales? (Given section 7 =
talks
>>> about selecting timescales I think it's worth pointing out one that =
is of
>>> practical use in computing, as opposed to TAI which is a =
retrospective
>>> paper clock.)
>>=20
>> PTP isn't a time scale; it's a system for reporting time. The problem =
is
>> it reports multiple timescales that are already discussed.
>=20
> The impression I get is that although PTP can transport different
> timescales, it almost always uses a specific one which is different =
from
> the other ones in the draft. (It differs from Unix time by the number =
of
> leap seconds.)

I haven=E2=80=99t found a public reference with enough detail on this. =
The only one I=E2=80=99ve found is Wikipedia, which has errors in its =
description of Unix time.

> It's a widely-available timescale,

I=E2=80=99m not sure I would agree with that - everything I=E2=80=99ve =
found says it=E2=80=99s limited to specialized industrial nets and =
systems; that=E2=80=99s another reason it=E2=80=99s not necessarily =
useful to add.=20

> like many of the others listed in that
> section, and I think readers would be surprised that it isn't listed =
in a
> draft that's providing advice on choosing timescales.
>=20
>>>   Unix time does not specify the definition of a 'second' or 'day',
>>>   and so it is not clear whether it intends to track SI seconds =
(where
>>>   time would be uniform) or solar time (where it would not).
>>>=20
>>> Unix time is defined in terms of struct tm fields, which are a
>>> representation of a UTC time stamp. It explicitly says it doesn't
>>> specify any relationship to real civil time.
>>=20
>> Civil time is neither SI nor solar. The statement above explains that
>> even the duration of a second or day isn't defined for Unix time.
>=20
> The problem with that paragraph is it sets up a false dichotomy. Unix =
time
> does not intend to track solar time nor SI seconds, it tracks civil =
time,
> which is a different third option. Leaving that option out is =
misleading.

The dichotomy is accurate - either time units are a physical constant or =
they=E2=80=99re defined relative to celestial events.

Civil time is just a time scale adopted by a government (or other type =
of group of people). I=E2=80=99m not aware of a civil time scale that =
isn=E2=80=99t based on one of those two.

>=20
>>> Google deployed leap smear in 2011 (not 2017 as your reference =
states) and
>>> they weren't the first to propose it.
>>=20
>> 2017 is the date of the published archival reference. That's not a
>> statement of when it was deployed, which this document doesn't =
include.
>=20
>   [Go17]    Google's approach to NTP leap smearing, proposed in 2017.
>             https://developers.google.com/time/smear
>=20
> The date 2017 doesn't appear on that page, and the page itself says
> deployed in 2008 so I'm not sure why you say it isn't included. (I =
think I
> got 2011 from my mail archives...) The reference doesn't match the =
title
> nor the contents of the page it refers to.

Ahh - wrong ref. Google developed it earlier but didn=E2=80=99t turn it =
on for public use until 2017:
https://www.theregister.co.uk/2016/12/02/google_public_ntp_servers/ =
<https://www.theregister.co.uk/2016/12/02/google_public_ntp_servers/>

I=E2=80=99ll correct that.

>=20
>>> 7.2. Hazards of some time scales
>>>=20
>>> It's worth mentioning that if you aspire to representing UTC =
correctly
>>> then it cannot be done as a simple count of seconds, and Unix and =
NTP are
>>> shining examples of getting it wrong.
>>>=20
>>> There should be a discussion of leap-second-related hazards in Unix =
time
>>> and NTP.
>>=20
>> This isn't a time protocol design doc or advice on which protocol to
>> use; it is advice on how to pick a time scale.
>=20
> Exactly why I think it should discuss hazards of bad representations =
of
> time. Especially since two of the main time systems it discusses =
suffer
> from such bad representations.

That=E2=80=99s perhaps another RFC.

>=20
>>> The draft seems to give the impression that leap smear is a Google
>>> peculiarity, but there are several other organizations doing it (see =
the
>>> link to the leapsecs list above).
>>=20
>> It mentions Google only as notable examples.
>=20
> Perhaps you could re-word it to make that more clear.

Will do.

---=

--Apple-Mail=_9B25D19C-4341-4532-A635-4C76821AFAC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi, =
Tony,<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Nov 11, 2019, at 6:37 AM, Tony Finch =
&lt;<a href=3D"mailto:dot@dotat.at" class=3D"">dot@dotat.at</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Joe Touch &lt;<a href=3D"mailto:touch@strayalpha.com" =
class=3D"">touch@strayalpha.com</a>&gt; wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">On 9/13/2019 12:41 PM, Tony Finch wrote:<br =
class=3D"">....<br class=3D""><blockquote type=3D"cite" class=3D""> =
&nbsp;&nbsp;o &nbsp;Ordering: to determine the relative sequence of =
events across<br class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;systems, such =
as with Lamport clocks [La78] or Vector clocks<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[Fi88][Ma88].<br class=3D""><br =
class=3D"">Lamport clocks and vector clocks don't use time, but the =
section heading<br class=3D"">implies that they do.<br =
class=3D""></blockquote><br class=3D"">It depends on how you interpret =
'time'.<br class=3D""></blockquote><br class=3D"">I meant in the usual =
sense, as implied by the draft's terminology section.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>They=E2=80=99re a bit like Schrodinger=E2=80=99s =
cat - they jump only whey you look at them (or would need to). IMO, they =
are time scales for that reason.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""> &nbsp;&nbsp;o &nbsp;NTP [RFC5905]: the Network Time =
Protocol, used in the Internet to<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;synchronize local clocks, in which dates =
are indicated by UTC<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;values. NTP times track the time of the =
clock they connect to.<br class=3D""><br class=3D"">NTP uses a =
unix-style count of seconds so it isn't able to represent UTC<br =
class=3D"">values.<br class=3D""></blockquote><br class=3D"">The doc =
describes the time NTP provides not its representation in its<br =
class=3D"">protocol messages. It claims to sync within a few ms of =
UTC.<br class=3D""></blockquote><br class=3D"">Your wording "UTC values" =
to me implies a vague description of the<br class=3D"">representation of =
the timestamps. Perhaps you could re-word it to make it<br =
class=3D"">clear that you meant something else.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Will =
do.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">Should PTP be added to =
the list of time scales? (Given section 7 talks<br class=3D"">about =
selecting timescales I think it's worth pointing out one that is of<br =
class=3D"">practical use in computing, as opposed to TAI which is a =
retrospective<br class=3D"">paper clock.)<br class=3D""></blockquote><br =
class=3D"">PTP isn't a time scale; it's a system for reporting time. The =
problem is<br class=3D"">it reports multiple timescales that are already =
discussed.<br class=3D""></blockquote><br class=3D"">The impression I =
get is that although PTP can transport different<br class=3D"">timescales,=
 it almost always uses a specific one which is different from<br =
class=3D"">the other ones in the draft. (It differs from Unix time by =
the number of<br class=3D"">leap seconds.)<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I =
haven=E2=80=99t found a public reference with enough detail on this. The =
only one I=E2=80=99ve found is Wikipedia, which has errors in its =
description of Unix time.</div><div><br class=3D""></div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">It's a =
widely-available timescale, </div></div></blockquote><div><br =
class=3D""></div><div>I=E2=80=99m not sure I would agree with that - =
everything I=E2=80=99ve found says it=E2=80=99s limited to specialized =
industrial nets and systems; that=E2=80=99s another reason it=E2=80=99s =
not necessarily useful to add.&nbsp;</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"">like many of =
the others listed in that<br class=3D"">section, and I think readers =
would be surprised that it isn't listed in a<br class=3D"">draft that's =
providing advice on choosing timescales.<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""> &nbsp;&nbsp;Unix time does not specify the definition of a =
'second' or 'day',<br class=3D""> &nbsp;&nbsp;and so it is not clear =
whether it intends to track SI seconds (where<br class=3D""> =
&nbsp;&nbsp;time would be uniform) or solar time (where it would =
not).<br class=3D""><br class=3D"">Unix time is defined in terms of =
struct tm fields, which are a<br class=3D"">representation of a UTC time =
stamp. It explicitly says it doesn't<br class=3D"">specify any =
relationship to real civil time.<br class=3D""></blockquote><br =
class=3D"">Civil time is neither SI nor solar. The statement above =
explains that<br class=3D"">even the duration of a second or day isn't =
defined for Unix time.<br class=3D""></blockquote><br class=3D"">The =
problem with that paragraph is it sets up a false dichotomy. Unix =
time<br class=3D"">does not intend to track solar time nor SI seconds, =
it tracks civil time,<br class=3D"">which is a different third option. =
Leaving that option out is misleading.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>The =
dichotomy is accurate - either time units are a physical constant or =
they=E2=80=99re defined relative to celestial events.</div><div><br =
class=3D""></div><div>Civil time is just a time scale adopted by a =
government (or other type of group of people). I=E2=80=99m not aware of =
a civil time scale that isn=E2=80=99t based on one of those =
two.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">Google deployed leap =
smear in 2011 (not 2017 as your reference states) and<br class=3D"">they =
weren't the first to propose it.<br class=3D""></blockquote><br =
class=3D"">2017 is the date of the published archival reference. That's =
not a<br class=3D"">statement of when it was deployed, which this =
document doesn't include.<br class=3D""></blockquote><br class=3D""> =
&nbsp;&nbsp;[Go17] &nbsp;&nbsp;&nbsp;Google's approach to NTP leap =
smearing, proposed in 2017.<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 href=3D"https://developers.google.com/time/smear" =
class=3D"">https://developers.google.com/time/smear</a><br class=3D""><br =
class=3D"">The date 2017 doesn't appear on that page, and the page =
itself says<br class=3D"">deployed in 2008 so I'm not sure why you say =
it isn't included. (I think I<br class=3D"">got 2011 from my mail =
archives...) The reference doesn't match the title<br class=3D"">nor the =
contents of the page it refers to.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Ahh - =
wrong ref. Google developed it earlier but didn=E2=80=99t turn it on for =
public use until 2017:</div><div><a =
href=3D"https://www.theregister.co.uk/2016/12/02/google_public_ntp_servers=
/" =
class=3D"">https://www.theregister.co.uk/2016/12/02/google_public_ntp_serv=
ers/</a></div><div><br class=3D""></div><div>I=E2=80=99ll correct =
that.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">7.2. Hazards of some =
time scales<br class=3D""><br class=3D"">It's worth mentioning that if =
you aspire to representing UTC correctly<br class=3D"">then it cannot be =
done as a simple count of seconds, and Unix and NTP are<br =
class=3D"">shining examples of getting it wrong.<br class=3D""><br =
class=3D"">There should be a discussion of leap-second-related hazards =
in Unix time<br class=3D"">and NTP.<br class=3D""></blockquote><br =
class=3D"">This isn't a time protocol design doc or advice on which =
protocol to<br class=3D"">use; it is advice on how to pick a time =
scale.<br class=3D""></blockquote><br class=3D"">Exactly why I think it =
should discuss hazards of bad representations of<br class=3D"">time. =
Especially since two of the main time systems it discusses suffer<br =
class=3D"">from such bad representations.<br =
class=3D""></div></div></blockquote><div><br =
class=3D""></div><div>That=E2=80=99s perhaps another RFC.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><blockquote=
 type=3D"cite" class=3D"">The draft seems to give the impression that =
leap smear is a Google<br class=3D"">peculiarity, but there are several =
other organizations doing it (see the<br class=3D"">link to the leapsecs =
list above).<br class=3D""></blockquote><br class=3D"">It mentions =
Google only as notable examples.<br class=3D""></blockquote><br =
class=3D"">Perhaps you could re-word it to make that more =
clear.</div></div></blockquote><br class=3D""></div><div>Will =
do.</div><div><br class=3D""></div><div>---</div></body></html>=

--Apple-Mail=_9B25D19C-4341-4532-A635-4C76821AFAC0--


From nobody Mon Nov 11 18:58:03 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7400120041 for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 18:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level: 
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 SnXc9o3YGGrg for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 18:57:59 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3CB5120110 for <art@ietf.org>; Mon, 11 Nov 2019 18:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+DGtOteIGkJjhvhT0jCoRk/l9WOaPbLcEsLSQEghrDk=; b=6XZTNNOxgZTGsI3XrrW1ardIO j1ihwMoVXQ9m9l94p4jX1edcX2ETMFB/HQ2BzCjey31hlzUalr5i/QHRvCTVfGSmGGYn/BDod5m2A gKvwviCnpHp4RQa/kOsB828xp7Y93vRDqTB1T7xmi4bu3fZDAn4pTsizQk9gARIY/2fQ+NQNW/xpr YI8oL8A1AXBOINmgpbT9MdnqJ7zYAXHGep/XuQkJCHdPd5Xahx4WNSTM2VVrEp59eX+9dP8+yfb0K kF2TnYBidFFWBZtrZl607cYLePsAULaF4u0JVn7LfOuhGwPSklNGAfmyywzfIr8xjGxLp91cZGlZz zUcJdUsNQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:57795 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iUMNO-001kQL-By; Mon, 11 Nov 2019 21:57:58 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_5380CD1D-350E-427A-9934-6B341E8DBF11"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com>
Date: Mon, 11 Nov 2019 18:57:53 -0800
Cc: "art@ietf.org" <art@ietf.org>
Message-Id: <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/5eR72P90iRXeV3NN6rLzpk3ak1s>
Subject: Re: [art] New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 02:58:02 -0000

--Apple-Mail=_5380CD1D-350E-427A-9934-6B341E8DBF11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

A little more about PTP, found here:
=
https://www.iol.unh.edu/sites/default/files/knowledgebase/1588/ptp_overvie=
w.pdf

>>>> Should PTP be added to the list of time scales? (Given section 7 =
talks
>>>> about selecting timescales I think it's worth pointing out one that =
is of
>>>> practical use in computing, as opposed to TAI which is a =
retrospective
>>>> paper clock.)
>>>=20
>>> PTP isn't a time scale; it's a system for reporting time. The =
problem is
>>> it reports multiple timescales that are already discussed.
>>=20
>> The impression I get is that although PTP can transport different
>> timescales, it almost always uses a specific one which is different =
from
>> the other ones in the draft. (It differs from Unix time by the number =
of
>> leap seconds.)

The source above claims PTP tries to coordinate the local clock to TAI.

That doc confirms it isn=E2=80=99t a time scale, as I originally =
indicated.

Joe=

--Apple-Mail=_5380CD1D-350E-427A-9934-6B341E8DBF11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">A =
little more about PTP, found here:<div class=3D""><a =
href=3D"https://www.iol.unh.edu/sites/default/files/knowledgebase/1588/ptp=
_overview.pdf" =
class=3D"">https://www.iol.unh.edu/sites/default/files/knowledgebase/1588/=
ptp_overview.pdf</a><br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">Should PTP be added to =
the list of time scales? (Given section 7 talks<br class=3D"">about =
selecting timescales I think it's worth pointing out one that is of<br =
class=3D"">practical use in computing, as opposed to TAI which is a =
retrospective<br class=3D"">paper clock.)<br class=3D""></blockquote><br =
class=3D"">PTP isn't a time scale; it's a system for reporting time. The =
problem is<br class=3D"">it reports multiple timescales that are already =
discussed.<br class=3D""></blockquote><br class=3D"">The impression I =
get is that although PTP can transport different<br class=3D"">timescales,=
 it almost always uses a specific one which is different from<br =
class=3D"">the other ones in the draft. (It differs from Unix time by =
the number of<br class=3D"">leap seconds.)<br =
class=3D""></div></div></blockquote></div></div></blockquote><div><br =
class=3D""></div><div>The source above claims PTP tries to coordinate =
the local clock to TAI.</div><div><br class=3D""></div><div>That doc =
confirms it isn=E2=80=99t a time scale, as I originally =
indicated.</div><div><br =
class=3D""></div><div>Joe</div></div></div></body></html>=

--Apple-Mail=_5380CD1D-350E-427A-9934-6B341E8DBF11--


From nobody Mon Nov 11 23:47:38 2019
Return-Path: <sla@ucolick.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08CBA1201AA for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 23:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 nzQ75Mut_u8f for <art@ietfa.amsl.com>; Mon, 11 Nov 2019 23:47:18 -0800 (PST)
Received: from smtp.ucolick.org (hunan.ucolick.org [128.114.23.233]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 537201200A1 for <art@ietf.org>; Mon, 11 Nov 2019 23:47:18 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 00FC527A5; Mon, 11 Nov 2019 23:47:17 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id F19942095; Mon, 11 Nov 2019 23:47:16 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id E1F9F61C; Mon, 11 Nov 2019 23:47:16 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id xAC7lGsq028565; Mon, 11 Nov 2019 23:47:16 -0800
Date: Mon, 11 Nov 2019 23:47:16 -0800
From: Steve Allen <sla@ucolick.org>
To: Joe Touch <touch@strayalpha.com>
Cc: "art@ietf.org" <art@ietf.org>
Message-ID: <20191112074716.GA28439@ucolick.org>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com> <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/pNy3ylvflqSwDJJ3aVDcUiVY9zE>
Subject: Re: [art] New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 07:47:36 -0000

On Mon 2019-11-11T18:57:53-0800 Joe Touch hath writ:
> A little more about PTP, found here:
> https://www.iol.unh.edu/sites/default/files/knowledgebase/1588/ptp_overview.pdf

> The source above claims PTP tries to coordinate the local clock to TAI.
>
> That doc confirms it isn’t a time scale, as I originally indicated.

In many cases it does not really matter whether a particular instance
of PTP is trying to match TAI or any other atomic time scale.

The issues of Bulletin Horaire show that the value of TAI is based on
re-setting all atomic time scales so that they all had
UT2(BIH) - A3 = -1.4123 s
at the epoch 1961-01-01T20:00:00 UT2.
https://www.ucolick.org/~sla/leapsecs/taiepoch.html

The offsets of GPS and other satellite systems are also arbitrary, so
the value of any atomic time scale is unrelated to any observable
phenomenon.

What matters is that the time scale used by a PTP implementation is
uniform within the scope of its systems.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Tue Nov 12 05:32:59 2019
Return-Path: <dot@dotat.at>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F88B120819 for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 05:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tnvuhaW0LuN3 for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 05:32:55 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [131.111.8.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 213E412002E for <art@ietf.org>; Tue, 12 Nov 2019 05:32:54 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:59276) by ppsw-42.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.138]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1iUWHr-0014ly-9K (Exim 4.92.3) (return-path <dot@dotat.at>); Tue, 12 Nov 2019 13:32:51 +0000
Date: Tue, 12 Nov 2019 13:32:51 +0000
From: Tony Finch <dot@dotat.at>
To: Joe Touch <touch@strayalpha.com>
cc: "art@ietf.org" <art@ietf.org>
In-Reply-To: <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com>
Message-ID: <alpine.DEB.2.20.1911121331500.10845@grey.csi.cam.ac.uk>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com> <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="1870870841-400743634-1573565571=:10845"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/5r4RR9Jdyn8YT9an24diSmo7RD8>
Subject: Re: [art] New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 13:32:57 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870870841-400743634-1573565571=:10845
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Joe Touch <touch@strayalpha.com> wrote:
>
> The source above claims PTP tries to coordinate the local clock to TAI.
>
> That doc confirms it isn=E2=80=99t a time scale, as I originally indicate=
d.

I'm struggling to understand why things like NTP and Unix and GPS are in
scope but PTP is not.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
people involved in running their communities
--1870870841-400743634-1573565571=:10845--


From nobody Tue Nov 12 05:37:59 2019
Return-Path: <dot@dotat.at>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19436120033 for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 05:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level: 
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RbqL4hPigmXK for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 05:37:55 -0800 (PST)
Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDD5312002E for <art@ietf.org>; Tue, 12 Nov 2019 05:37:54 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:46984) by ppsw-43.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1iUWMh-001ONn-p7 (Exim 4.92.3) (return-path <dot@dotat.at>); Tue, 12 Nov 2019 13:37:51 +0000
Date: Tue, 12 Nov 2019 13:37:51 +0000
From: Tony Finch <dot@dotat.at>
To: Joe Touch <touch@strayalpha.com>
cc: "art@ietf.org" <art@ietf.org>
In-Reply-To: <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com>
Message-ID: <alpine.DEB.2.20.1911121333180.10845@grey.csi.cam.ac.uk>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="1870870841-2014860517-1573565871=:10845"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/vpzEw5yMvm5HskDxEAvjC30GZ98>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 13:37:57 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1870870841-2014860517-1573565871=:10845
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Joe Touch <touch@strayalpha.com> wrote:

> >>> Lamport clocks and vector clocks don't use time, but the section head=
ing
> >>> implies that they do.
> >>
> >> It depends on how you interpret 'time'.
> >
> > I meant in the usual sense, as implied by the draft's terminology secti=
on.
>
> They=E2=80=99re a bit like Schrodinger=E2=80=99s cat - they jump only whe=
y you look at
> them (or would need to). IMO, they are time scales for that reason.

Perhaps the terminology section should make it clear that your definition
of time is extended in this way.

> > The problem with that paragraph is it sets up a false dichotomy. Unix t=
ime
> > does not intend to track solar time nor SI seconds, it tracks civil tim=
e,
> > which is a different third option. Leaving that option out is misleadin=
g.
>
> The dichotomy is accurate - either time units are a physical constant or
> they=E2=80=99re defined relative to celestial events.

Except for Lamport clocks or vector clocks. And civil time is not
either/or wrt physical constants and celestial events, it's a mashup of
both.

Tony.
--=20
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Sole: Variable 3 to 5, becoming west 6 to gale 8, perhaps severe gale 9 lat=
er.
Very rough or high. Showers. Moderate.
--1870870841-2014860517-1573565871=:10845--


From nobody Tue Nov 12 06:30:53 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75FBD12002E for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 06:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 oYNtXQG3NNtm for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 06:30:51 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB0FA1200B8 for <art@ietf.org>; Tue, 12 Nov 2019 06:30:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=SdIm0U1wSoaS1cuXpp2GNTBKeZmNN5LSNOi6liUlpZA=; b=I6okRP7zZm3VXfqJtG91uoEXx b8rh+6ky5/n3J51W47p/VIdsyZtNYBtaIBHY+JbTLzduo4memNhUBblV1VuxFr0GFdEan8moSsAGq aCLz3DTvj93wpnBa0/eu9w+qkQYYW2HAhhT0Zfm7TNmGr/9C1WbveAJz3nWNS6PCCZjdfAgy/oHFT PvvZNV1KHZWQS4Jkokn03g3xIR58Z0vJTgWX7aMUyetargag77z+CvuZxKuoPG4fOHAZee7io5mb8 nGdzQUmBZBExhIpTUA0Kk1i75CzQCybjcD8plKXH5kFczl/+ZS1gxtjEvUwnHq7smaVEDIH9cLHqU dhIEJXfng==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:58249 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iUXBp-00186g-RK; Tue, 12 Nov 2019 09:30:47 -0500
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <alpine.DEB.2.20.1911121331500.10845@grey.csi.cam.ac.uk>
Date: Tue, 12 Nov 2019 06:30:41 -0800
Cc: "art@ietf.org" <art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D49822F5-8A51-4A57-809E-ABF72988E265@strayalpha.com>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com> <748167A2-46AF-45D3-9CCB-339BF2123B7C@strayalpha.com> <alpine.DEB.2.20.1911121331500.10845@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/TDYBKGReLT88-iuuzRDtue7Z1V0>
Subject: Re: [art] New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 14:30:52 -0000

> On Nov 12, 2019, at 5:32 AM, Tony Finch <dot@dotat.at> wrote:
>=20
> Joe Touch <touch@strayalpha.com> wrote:
>>=20
>> The source above claims PTP tries to coordinate the local clock to =
TAI.
>>=20
>> That doc confirms it isn=E2=80=99t a time scale, as I originally =
indicated.
>=20
> I'm struggling to understand why things like NTP and Unix and GPS are =
in
> scope but PTP is not.

Unix is included as a time scale.=20

The others are not time scales. I see your point that PTP could be =
included there but it=E2=80=99s not intended for wide-scale deployment =
over the public Internet. Synchronous Ethernet isn=E2=80=99t listed =
either. I can add a note that there are other protocols - but I do think =
it=E2=80=99s reasonable to focus on those that are ~6 orders of =
magnitude more widely deployed.

Joe=


From nobody Tue Nov 12 06:34:12 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBC21208BE for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 06:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 g2FxTClX9m7a for <art@ietfa.amsl.com>; Tue, 12 Nov 2019 06:34:06 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41D21201DC for <art@ietf.org>; Tue, 12 Nov 2019 06:34:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=NS59lGlaeySXDx543LemtW7KInZpghHd47MSjpF7JMA=; b=LIgjWyUeoNQfAWUS8D0/5drjc EMDskwfbnQgghSvzGhA30zJQRZSMXcXPOqLCT3VkVhr71jHsez6shxuiLaJBih6bEbMbGTk9AbpxU wj8cEU7A/ekYfhJ8i2j5GPajjOO6tRSC0xlEoW6V28uQ76vXoXm21noDvXU0vyHloVooov3iuhsP/ 1eygEQouf5T/YUfF7IqJp6jWMLSP5muVPP7mb1tjGVz5xm7cmWaGU852+/nTWXqlWkLtpk2FlG3A1 hxT1u/FOs+kOC5hkZeklLcJXqvy4+NHYsJdaG8lcB77rT8zOvuTd0d70ZZ9pdh+0HdcyEe1YSPFb5 GUvfZ6/0w==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:58267 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iUXF2-001B6S-DL; Tue, 12 Nov 2019 09:34:05 -0500
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <alpine.DEB.2.20.1911121333180.10845@grey.csi.cam.ac.uk>
Date: Tue, 12 Nov 2019 06:33:59 -0800
Cc: "art@ietf.org" <art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <28AE8551-5A6A-4D05-817F-E4A8764C823A@strayalpha.com>
References: <156834269242.16573.17240497030993366068.idtracker@ietfa.amsl.com> <45c2fb64-1efd-68bf-4436-ec7bbb7bfc88@strayalpha.com> <alpine.DEB.2.20.1909131844350.5352@grey.csi.cam.ac.uk> <5320191a-09d4-4398-a242-e8d3ebb496d5@strayalpha.com> <alpine.DEB.2.20.1911111353350.10845@grey.csi.cam.ac.uk> <88C23DE6-C666-4071-97E7-5C271A54446A@strayalpha.com> <alpine.DEB.2.20.1911121333180.10845@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/xSoe66lX0POKot1hqbbJB0qf9s0>
Subject: Re: [art] New Version Notification for draft-touch-time-05.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2019 14:34:10 -0000

> On Nov 12, 2019, at 5:37 AM, Tony Finch <dot@dotat.at> wrote:
>=20
> Joe Touch <touch@strayalpha.com> wrote:
>=20
>>>>> Lamport clocks and vector clocks don't use time, but the section =
heading
>>>>> implies that they do.
>>>>=20
>>>> It depends on how you interpret 'time'.
>>>=20
>>> I meant in the usual sense, as implied by the draft's terminology =
section.
>>=20
>> They=E2=80=99re a bit like Schrodinger=E2=80=99s cat - they jump only =
whey you look at
>> them (or would need to). IMO, they are time scales for that reason.
>=20
> Perhaps the terminology section should make it clear that your =
definition
> of time is extended in this way.

Will do.

>=20
>>> The problem with that paragraph is it sets up a false dichotomy. =
Unix time
>>> does not intend to track solar time nor SI seconds, it tracks civil =
time,
>>> which is a different third option. Leaving that option out is =
misleading.
>>=20
>> The dichotomy is accurate - either time units are a physical constant =
or
>> they=E2=80=99re defined relative to celestial events.
>=20
> Except for Lamport clocks or vector clocks. And civil time is not
> either/or wrt physical constants and celestial events, it's a mashup =
of
> both.

Agree with your point about Lamport and vector clocks, but they=E2=80=99re=
 never presented as measuring the passage of time. Unix is. And civil =
time isn=E2=80=99t a time scale in of itself - it=E2=80=99s a =
designation of a time scale or combination of time scales. I can add =
that.

Note that this is down in the weeds of what this document is trying to =
accomplish. It isn=E2=80=99t intended to be THE definitive document =
about ways to keep time. It=E2=80=99s about *picking* a time scale and =
not trying to create your own.

Joe=


From nobody Sat Nov 16 01:37:07 2019
Return-Path: <y.oiwa@aist.go.jp>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B212412008B for <art@ietfa.amsl.com>; Sat, 16 Nov 2019 01:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aist.go.jp
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 cfjACmUdWoO2 for <art@ietfa.amsl.com>; Sat, 16 Nov 2019 01:37:02 -0800 (PST)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410042.outbound.protection.outlook.com [40.107.141.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B146A120059 for <art@ietf.org>; Sat, 16 Nov 2019 01:37:02 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Cl4rziJh+XwKQUd+5zKqlrpq7S9ws8k1RkLH6WoW6jJD1LuFAtezjmVRrFlcU78gHOkN2d061j6qrwSF0Tya4BPc4+d4gxX8Lr1ZI+F74AlJ5Eb90XoPZJRux/KZ71suTVU9LAKQYjrYc+8jeFBtn3DGKMjwHOKv+51h8GIaWjfTE5ieZZhjuMnI9obWS1xY/oqzN/uoypNu4bfZEcIint/7tlr9qroMHXoB95D235MdRDUHzxTNaIsMQjPEJE/wcPC1pjZl9isVUMgXB6I0Fnl0l3qbLHp7bt1aZ3v5lnHGAjTIu1dcAsgI5RKwQJtfaF5nhWHEturUIn16paUk7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+CxC+HOpatVT/8ddNebaE+fbEVX9inI/oo9CzbJmq+Y=; b=czUagO5MwH+KVX7kuuAcZ3bJPPuGmq4tdPhVxgZtI/Pi2+HzLZSfCKfORK4AoP2AcldfTe0mQb5djdLETbSpnHETr9g7sBH+iV2EtWLhn5xoXP7r5RBMnnmYuPBHK65scDWhHcW5dWNvYEtzDCWeIQaQl8UgnDKv43WA5BuIUkLJQ9X2bTKtEvazDFAySuMfvgu9Lel8GBNDHa7Il1rBy/+K8VUtso8PJSIlX9oItQGjNrywyUx/X5NHMxr4GfgDmVCxX7BUT4EIaI+KlMhUBvpCcjyEl4Y1QQkJ5g/+X+z5MSRJupV9Tv9tOg+pXCdUzNhEZVH3Y/HuIwWDToKA6Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=aist.go.jp; dmarc=pass action=none header.from=aist.go.jp; dkim=pass header.d=aist.go.jp; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aist.go.jp; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+CxC+HOpatVT/8ddNebaE+fbEVX9inI/oo9CzbJmq+Y=; b=bTLU7Equ1BT0WrjCm+BpHMxu1df3sfC+i3+2HVEEJC+vl/hZ3UZ1zeVfVJk4y8IgsLO3mEy+SR93jNJ8qVyBiGGNV/MYu5J2OIx3PoIxhV5ns2OAPJPY3LZlV5NuxsvrUzXCHpzUJ3OykSQ2Dr6tI5Id/JfFGiWdV3iqyUrgzq4=
Received: from OSBPR01MB1815.jpnprd01.prod.outlook.com (52.134.226.138) by OSBPR01MB2663.jpnprd01.prod.outlook.com (52.134.253.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.23; Sat, 16 Nov 2019 09:37:00 +0000
Received: from OSBPR01MB1815.jpnprd01.prod.outlook.com ([fe80::85b6:608:39a:f84a]) by OSBPR01MB1815.jpnprd01.prod.outlook.com ([fe80::85b6:608:39a:f84a%7]) with mapi id 15.20.2451.029; Sat, 16 Nov 2019 09:37:00 +0000
From: Yutaka OIWA <y.oiwa@aist.go.jp>
To: "http-auth@ietf.org" <http-auth@ietf.org>
CC: "art@ietf.org" <art@ietf.org>
Thread-Topic: Reference Implementation for new HTTP auths?
Thread-Index: AdWcYPPgt4JYgt4SSomuGwj9pYkR6A==
Date: Sat, 16 Nov 2019 09:37:00 +0000
Message-ID: <OSBPR01MB18151B01C9383A3AE4CA6CBEA0730@OSBPR01MB1815.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=y.oiwa@aist.go.jp; 
x-originating-ip: [2001:67c:1232:144:1d6a:fd56:990e:2812]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 320460b5-e57b-491e-d1fa-08d76a7887c6
x-ms-traffictypediagnostic: OSBPR01MB2663:
x-microsoft-antispam-prvs: <OSBPR01MB2663CC5C03AB6F521DECEAEDA0730@OSBPR01MB2663.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3968;
x-forefront-prvs: 02234DBFF6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(376002)(396003)(39850400004)(346002)(189003)(199004)(33656002)(86362001)(66446008)(52536014)(66556008)(66476007)(102836004)(2906002)(6506007)(76116006)(14444005)(71200400001)(66946007)(71190400001)(6916009)(305945005)(8936002)(74316002)(64756008)(2501003)(5660300002)(486006)(256004)(6116002)(186003)(476003)(7736002)(99286004)(450100002)(2351001)(46003)(8676002)(5640700003)(25786009)(6436002)(81156014)(81166006)(413944005)(4326008)(478600001)(966005)(7696005)(55016002)(9686003)(6306002)(316002)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:OSBPR01MB2663; H:OSBPR01MB1815.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:3; A:1; 
received-spf: None (protection.outlook.com: aist.go.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2OpWSPSLjk8fzm+qLfLF/q11xvOw/NeKQ75gGMb8il42edJf8/zgGRQ/raG+tOCuCKh/KbxYLFwMLp7uR79Hj09yR9LHVyLRUEnJWU8nJSJAmMv+/6Abf3DcKTTE+L4WRojNg+Lh/Z9nXokbnsXbSFbNIKwUuZ1WNVFtW7aR9TMm0L5StcXm/qG/+xEvi0h1hfxycZd5wKAp88LsLBtQEQD2pI7BIB3wR31unvaJdBvTE0c2X2U0Ci9J6lKnVl4YzeL4i+b+4p79Ct9+vikHCGACMkIHJyw1InqBCQ8RKEc/ykyspSDQddULotCBYi0d2qmgaSx5J8DfGL9+mg9MtdtLCepAlwnKlgXZkRG4xH8pyZzezG9pEO9T+vWvZMmB3MamQQlHyIkN29Xi7sqecmFQbxoq5iagNGtGRTbQxgMhOBve/7OPvLaNuIbbMGUu
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aist.go.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: 320460b5-e57b-491e-d1fa-08d76a7887c6
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2019 09:37:00.2238 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 18a7fec8-652f-409b-8369-272d9ce80620
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hMLTZyAK4UQlv+09kd4XKhYikr5b7ZNPRgb9j/BNVYnTqNgjPtFk4WrKa3WzoxouBZllovbROp2hXYddfefYnw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB2663
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/i38vYIBH5We1Stev53X3li6fCaA>
Subject: [art] Reference Implementation for new HTTP auths?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2019 09:37:06 -0000

Dear HTTP-AUTH friends,

Do you know is there a good reference implementation or test suites for
revised Basic/Digest authentication (RFC 7617/7616) and/or i18n (RFC 5987)?

We recently implemented a set of library code for these new standards and=20
We're looking forward to checking interoperability.
We checked for some limited interoperability with curl or other C-based
implementations using SHA-1, but for i18n or SHA-2 algorithms,=20
we were only possible to check with our own server/client implementation pa=
ir.

Our code is available in https://github.com/yoiwa/python-httpauth-lib ,
including server/client pair for almost-full-spec RFC 7616 written in Pytho=
n 3.
These codes are initially implemented for introducing stronger authenticati=
on
to our RESTCONF-based applications.

Information and/or suggestions are welcome.

Cheers,

Yutaka

--=20
Yutaka OIWA, Ph.D.          Leader, Software Quality Assurance Research Tea=
m
                                     Cyber Physical Security Research Cente=
r
     National Institute of Advanced Industrial Science and Technology (AIST=
)
                       Mail addresses: <y.oiwa@aist.go.jp>, <yutaka@oiwa.jp=
>
OpenPGP: id[440546B5] fp[7C9F 723A 7559 3246 229D  3139 8677 9BD2 4405 46B5=
]


From nobody Sat Nov 16 13:18:28 2019
Return-Path: <sayrer@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D3812012C for <art@ietfa.amsl.com>; Sat, 16 Nov 2019 13:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 s4mk6XpzepDR for <art@ietfa.amsl.com>; Sat, 16 Nov 2019 13:18:24 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 D1FDF120013 for <art@ietf.org>; Sat, 16 Nov 2019 13:18:24 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id q83so14441956iod.1; Sat, 16 Nov 2019 13:18:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lZEJQPUZk0qGLY96GqPqnKktljW7y1xGubH6XFJ6PV0=; b=G4wJsc7Gd6TaRmQRlpo+UrZJZvfm4pBiV41dlZC4COBsprK4/LxSUTpaS+Y0SGO69o jUGRUqRkmt3RJfPX94t5rQW5MOMRsiXLTjr5zDMNkYxQwBuABsTPd+BRf7tHhzn+2qjf 0bHb9InrGSFD0RVR3ZKkGkDLodySBvuKDlYlRKLKKoM+r1V548HLJaIZd3MNXxZp1UaQ ZPAPwZvsfkRqDRGmAVW3l5g89zLwP5eLWblplTH3i8hOsSPuvwhaQWT2UaCLh0NvelHZ ufv9ydF8+N446BGE0E1hKV6R12FThH8xglbBhDJn3O6ipidvQb9ShK9GMNaC6aIGPW9M UG1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lZEJQPUZk0qGLY96GqPqnKktljW7y1xGubH6XFJ6PV0=; b=U5/NLBMcJpT8Vz+zzKyS9X7f5iwOsRXnM5xPEn/wF9Hz4ZTzmT3RwaN1A7L+ZISGvV hCbLkyacOHW4UkZv3tYpOgOqDKCGiPJF1Pubwefh3/1ywin7qq6uRzkU96xsFWiKt90N MzSu5aFE8VotLLBrpf8A9RuNbO+rUunOGIEjt7ulrVWJ57kyJpnZ/rKBFRI3BpovXN61 gooCUMHJWgAcYgyXwE9QFHcKajrGwhXgpgkW7UCjPIxA9rJZZzuUNEH/3r6+PGywE21q /vY2N3nAbR91Gh84UrCqfYlY4TCMXslDLo8SHlMuihv+tI5MmzM+/fYcz1Fqj7sXgI35 fNkg==
X-Gm-Message-State: APjAAAULy3L6kPz8K0GvLueuI8pJKSecVLGYfKHC76n821i2eigskoMm Y2nFFJ65HsVc3oNBvL/iy1BWI5fTg2hBPcxNSis=
X-Google-Smtp-Source: APXvYqy+YYL6vLxFHcKv+HLuChOQ5EdluwuMRCFXFeDCa5zXyUNVdXJDNNTNMJWgdkDNdSAirLCvpieOzBT4zXERp8o=
X-Received: by 2002:a05:6602:22c3:: with SMTP id e3mr6992935ioe.73.1573939103946;  Sat, 16 Nov 2019 13:18:23 -0800 (PST)
MIME-Version: 1.0
References: <OSBPR01MB18151B01C9383A3AE4CA6CBEA0730@OSBPR01MB1815.jpnprd01.prod.outlook.com>
In-Reply-To: <OSBPR01MB18151B01C9383A3AE4CA6CBEA0730@OSBPR01MB1815.jpnprd01.prod.outlook.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Sat, 16 Nov 2019 13:18:12 -0800
Message-ID: <CAChr6SxftZwS_HLa2X5r0iFha3+2rJTbHOSpiHVhWx_9A4QBmQ@mail.gmail.com>
To: Yutaka OIWA <y.oiwa@aist.go.jp>
Cc: "http-auth@ietf.org" <http-auth@ietf.org>, "art@ietf.org" <art@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000305eb305977d413f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/hndierO_5tELGNvT6zte0g84VMI>
Subject: Re: [art] Reference Implementation for new HTTP auths?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Nov 2019 21:18:27 -0000

--000000000000305eb305977d413f
Content-Type: text/plain; charset="UTF-8"

On Sat, Nov 16, 2019 at 1:37 AM Yutaka OIWA <y.oiwa@aist.go.jp> wrote:

>
> Information and/or suggestions are welcome.
>


I don't know of any tests for the newer stuff, but you can build simple
command line clients for both the Chromium and Mozilla networking stacks.

Here's a sample C++ command line client for Chromium:
https://cs.chromium.org/chromium/src/components/cronet/native/sample/main.cc?dr=CSs&g=0

For Mozilla, you can use XPCShell, a JS shell with access to browser
internals such as networking and file i/o.
https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Language_bindings/XPConnect/xpcshell

The test suites for Mozilla, WebKit, and Chromium also contain a lot of
strange edge cases you might want to know about.

For Chromium, look at the http_auth_* files:
https://cs.chromium.org/chromium/src/net/http/?dr=CSs&g=0

For WebKit, look at the basic-auth XHR tests:
https://trac.webkit.org/browser/webkit/trunk/LayoutTests/http/tests/xmlhttprequest

For Mozilla, the tests are in JS. This file also shows how to use httpd.js,
their test server:
https://dxr.mozilla.org/mozilla-central/source/netwerk/test/unit/test_authentication.js#4

There are WHATWG tests for the XHR and Fetch APIs, but they don't look as
detailed as the browser's to me.
https://github.com/web-platform-tests/wpt

There are some relatively detailed compatibility considerations listed here:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/WWW-Authenticate

thanks,
Rob

--000000000000305eb305977d413f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Nov 16, 2019 at 1:37 AM Yutaka OI=
WA &lt;<a href=3D"mailto:y.oiwa@aist.go.jp">y.oiwa@aist.go.jp</a>&gt; wrote=
:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
<br>
Information and/or suggestions are welcome.<br></blockquote><div><br></div>=
<div><br></div><div>I don&#39;t know of any tests for the newer stuff, but =
you can build simple command line clients for both the Chromium and Mozilla=
 networking stacks.</div><div><br></div><div>Here&#39;s a sample C++ comman=
d line client for Chromium:</div><div><a href=3D"https://cs.chromium.org/ch=
romium/src/components/cronet/native/sample/main.cc?dr=3DCSs&amp;g=3D0">http=
s://cs.chromium.org/chromium/src/components/cronet/native/sample/main.cc?dr=
=3DCSs&amp;g=3D0</a></div><div><br></div><div>For Mozilla, you can use XPCS=
hell, a JS shell with access to browser internals such as networking and fi=
le i/o.</div><div><a href=3D"https://developer.mozilla.org/en-US/docs/Mozil=
la/Tech/XPCOM/Language_bindings/XPConnect/xpcshell">https://developer.mozil=
la.org/en-US/docs/Mozilla/Tech/XPCOM/Language_bindings/XPConnect/xpcshell</=
a></div><div><br></div><div>The test suites for Mozilla, WebKit, and Chromi=
um also contain a lot of strange edge cases you might want to know about.</=
div><div><br></div><div>For Chromium, look at the http_auth_* files:</div><=
div><a href=3D"https://cs.chromium.org/chromium/src/net/http/?dr=3DCSs&amp;=
g=3D0">https://cs.chromium.org/chromium/src/net/http/?dr=3DCSs&amp;g=3D0</a=
>=C2=A0</div><div>=C2=A0</div><div>For WebKit, look at the basic-auth XHR t=
ests:</div><div><a href=3D"https://trac.webkit.org/browser/webkit/trunk/Lay=
outTests/http/tests/xmlhttprequest">https://trac.webkit.org/browser/webkit/=
trunk/LayoutTests/http/tests/xmlhttprequest</a><br></div><div><br></div><di=
v>For Mozilla, the tests are in JS. This file also shows how to use httpd.j=
s, their test server:</div><div><a href=3D"https://dxr.mozilla.org/mozilla-=
central/source/netwerk/test/unit/test_authentication.js#4">https://dxr.mozi=
lla.org/mozilla-central/source/netwerk/test/unit/test_authentication.js#4</=
a><br></div><div><br></div><div>There are WHATWG tests for the XHR and Fetc=
h APIs, but they don&#39;t look as detailed as the browser&#39;s to me.</di=
v><div><a href=3D"https://github.com/web-platform-tests/wpt">https://github=
.com/web-platform-tests/wpt</a><br></div><div><br></div><div>There are some=
 relatively detailed compatibility considerations listed here:</div><div><a=
 href=3D"https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication">=
https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication</a><br></d=
iv><div><a href=3D"https://developer.mozilla.org/en-US/docs/Web/HTTP/Header=
s/WWW-Authenticate">https://developer.mozilla.org/en-US/docs/Web/HTTP/Heade=
rs/WWW-Authenticate</a><br></div><div><br></div><div>thanks,</div><div>Rob<=
/div><div><br></div></div></div>

--000000000000305eb305977d413f--


From nobody Mon Nov 18 01:11:02 2019
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A55120906; Mon, 18 Nov 2019 01:10:54 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157406825453.14183.10475707813554266347.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2019 01:10:54 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/4CEO6ZGPbZhRRPdLXF-5SVKbP2c>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-02.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 09:11:00 -0000

IESG state changed:

New State: AD Evaluation

(The previous state was Publication Requested)


Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Mon Nov 18 02:13:40 2019
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21E7C120874; Mon, 18 Nov 2019 02:13:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <art@ietf.org>, <draft-nottingham-rfc7320bis@ietf.org>, <adam@nostrum.com>, <mt@lowentropy.net>, <mt@mozilla.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157407201813.14156.12044047994970271252.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2019 02:13:38 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/UuhrpS-gmd2E5poRk6XNjONmv4Q>
Subject: [art] Datatracker State Update Notice: <draft-nottingham-rfc7320bis-02.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 10:13:38 -0000

IESG state changed:

New State: Last Call Requested

(The previous state was AD Evaluation)


Datatracker URL: https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Mon Nov 18 02:13:44 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88663120902; Mon, 18 Nov 2019 02:13:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "DraftTracker Mail System" <iesg-secretary@ietf.org>
To: <iesg-secretary@ietf.org>
Cc: art@ietf.org, adam@nostrum.com, mt@lowentropy.net, mt@mozilla.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157407201855.14156.12944870876900579097.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2019 02:13:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/wHhLRNmNv2f1HzaqVWBwmNzE7KY>
Subject: [art] Last Call: <draft-nottingham-rfc7320bis-02.txt>
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 10:13:38 -0000

Last Call Request has been submitted for
<draft-nottingham-rfc7320bis-02.txt>

https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/


From nobody Mon Nov 18 02:23:41 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: art@ietf.org
Delivered-To: art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 13ED11208A9; Mon, 18 Nov 2019 02:23:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: art@ietf.org, draft-nottingham-rfc7320bis@ietf.org, adam@nostrum.com, mt@lowentropy.net, mt@mozilla.com
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <157407262004.13995.17002547023445908822.idtracker@ietfa.amsl.com>
Date: Mon, 18 Nov 2019 02:23:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/kfL_tLR-CLJqk4VK7sFR2SQheL4>
Subject: [art] Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2019 10:23:40 -0000

The IESG has received a request from an individual submitter to consider the
following document: - 'URI Design and Ownership'
  <draft-nottingham-rfc7320bis-02.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2019-12-16. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
   extensible naming system wherein each scheme's specification may
   further restrict the syntax and semantics of identifiers using that
   scheme."  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI's owner, publishing independent standards
   that mandate particular forms of substructure in URIs is often
   problematic.

   This document provides guidance on the specification of URI
   substructure in standards.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-nottingham-rfc7320bis/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Tue Nov 19 18:17:05 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5941200E5 for <art@ietfa.amsl.com>; Tue, 19 Nov 2019 18:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level: 
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 VyWd2l1Afgqk for <art@ietfa.amsl.com>; Tue, 19 Nov 2019 18:17:02 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E84C81207FF for <art@ietf.org>; Tue, 19 Nov 2019 18:17:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:To:References:Subject:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=uihqu/sHbf15dwlAkfk0SyHA919n7dPVEIpEWsVimSQ=; b=vQvkfpWroURQMweYP5wRx+ixL +cduSXd+mOgCpkX489K4Wl+SA15UaUaxyBVryQAGRvL74bxUwvLIni02shiqPG/TUFtU1DUONCCU7 qoDcILfBJ6fiHA67XEX7uZYm7l+OWUbPxsee5exLBtMqUp0oPZAOo7V2LDieWyH276anH/RlFTGY1 +08H7eCmAkJU1hPcSdrPY5cyPHPFwA/8D5eXnMDjKfnBThusteanujAKfo/DECl2e5fgFSfXi2XIZ cE2ThWdYsbB6D2vrKURgsjMhLSbTk38oisDgPMg6daoKLnB7aRFzxlBWOb0juAh2W/NoVfGb+g6gd j1d3auD3g==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:53166 helo=[192.168.1.13]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iXFY8-001I24-EE; Tue, 19 Nov 2019 21:17:01 -0500
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com>
To: "art@ietf.org" <art@ietf.org>
From: Joe Touch <touch@strayalpha.com>
X-Forwarded-Message-Id: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com>
Message-ID: <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com>
Date: Tue, 19 Nov 2019 18:16:55 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------F255AD8B602AEFADF172CFC9"
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/SjBvl4S_SJSNZwgf2dMpOWE6Oik>
Subject: [art] Fwd: New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 02:17:03 -0000

This is a multi-part message in MIME format.
--------------F255AD8B602AEFADF172CFC9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi, all,

This version addresses all suggestions provided to date.

Joe


-------- Forwarded Message --------
Subject: 	New Version Notification for draft-touch-time-06.txt
Date: 	Tue, 19 Nov 2019 18:10:49 -0800
From: 	internet-drafts@ietf.org
To: 	Joseph Touch <touch@strayalpha.com>, Joe Touch <touch@strayalpha.com>




A new version of I-D, draft-touch-time-06.txt
has been successfully submitted by Joe Touch and posted to the
IETF repository.

Name: draft-touch-time
Revision: 06
Title: Resolving Multiple Time Scales in the Internet
Document date: 2019-11-19
Group: Individual Submission
Pages: 21
URL: https://www.ietf.org/internet-drafts/draft-touch-time-06.txt
Status: https://datatracker.ietf.org/doc/draft-touch-time/
Htmlized: https://tools.ietf.org/html/draft-touch-time-06
Htmlized: https://datatracker.ietf.org/doc/html/draft-touch-time
Diff: https://www.ietf.org/rfcdiff?url2=draft-touch-time-06

Abstract:
Internet systems use a variety of time scales, which can complicate
time comparisons and calculations. This document explains these
various ways of indicating time and explains how they can be used
together safely. This document is intended as a companion to
Internet time as discussed in RFC 3339.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--------------F255AD8B602AEFADF172CFC9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi, all,</p>
    <p>This version addresses all suggestions provided to date.</p>
    <p>Joe<br>
    </p>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>New Version Notification for draft-touch-time-06.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Tue, 19 Nov 2019 18:10:49 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td>Joseph Touch <a class="moz-txt-link-rfc2396E" href="mailto:touch@strayalpha.com">&lt;touch@strayalpha.com&gt;</a>, Joe Touch
              <a class="moz-txt-link-rfc2396E" href="mailto:touch@strayalpha.com">&lt;touch@strayalpha.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <br>
      A new version of I-D, draft-touch-time-06.txt<br>
      has been successfully submitted by Joe Touch and posted to the<br>
      IETF repository.<br>
      <br>
      Name: draft-touch-time<br>
      Revision: 06<br>
      Title: Resolving Multiple Time Scales in the Internet<br>
      Document date: 2019-11-19<br>
      Group: Individual Submission<br>
      Pages: 21<br>
      URL: <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-touch-time-06.txt">https://www.ietf.org/internet-drafts/draft-touch-time-06.txt</a><br>
      Status: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-touch-time/">https://datatracker.ietf.org/doc/draft-touch-time/</a><br>
      Htmlized: <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-touch-time-06">https://tools.ietf.org/html/draft-touch-time-06</a><br>
      Htmlized: <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-touch-time">https://datatracker.ietf.org/doc/html/draft-touch-time</a><br>
      Diff: <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-touch-time-06">https://www.ietf.org/rfcdiff?url2=draft-touch-time-06</a><br>
      <br>
      Abstract:<br>
      Internet systems use a variety of time scales, which can
      complicate<br>
      time comparisons and calculations. This document explains these<br>
      various ways of indicating time and explains how they can be used<br>
      together safely. This document is intended as a companion to<br>
      Internet time as discussed in RFC 3339.<br>
      <br>
      <br>
      <br>
      Please note that it may take a couple of minutes from the time of
      submission<br>
      until the htmlized version and diff are available at
      tools.ietf.org.<br>
      <br>
      The IETF Secretariat<br>
      <br>
    </div>
  </body>
</html>

--------------F255AD8B602AEFADF172CFC9--


From nobody Wed Nov 20 15:53:09 2019
Return-Path: <sla@ucolick.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DEF7120899 for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 15:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 x82sLH9PqISl for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 15:53:06 -0800 (PST)
Received: from smtp.ucolick.org (hunan.ucolick.org [128.114.23.233]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F43120168 for <art@ietf.org>; Wed, 20 Nov 2019 15:53:06 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 019CD2732 for <art@ietf.org>; Wed, 20 Nov 2019 15:53:05 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id F2E1222F9 for <art@ietf.org>; Wed, 20 Nov 2019 15:53:04 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id D40DE616 for <art@ietf.org>; Wed, 20 Nov 2019 15:53:04 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id xAKNr352013331 for art@ietf.org; Wed, 20 Nov 2019 15:53:03 -0800
Date: Wed, 20 Nov 2019 15:53:03 -0800
From: Steve Allen <sla@ucolick.org>
To: Applications and Real-Time Area Discussion <art@ietf.org>
Message-ID: <20191120235303.GA12868@ucolick.org>
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com> <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/p8mBTuGPda8J4wt3OGB22jn_ElM>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 23:53:07 -0000

On Tue 2019-11-19T18:16:55-0800 Joe Touch hath writ:
> Name: draft-touch-time
> Revision: 06
> Title: Resolving Multiple Time Scales in the Internet
> Document date: 2019-11-19
> Group: Individual Submission
> Pages: 21
> URL: https://www.ietf.org/internet-drafts/draft-touch-time-06.txt
> Status: https://datatracker.ietf.org/doc/draft-touch-time/
> Htmlized: https://tools.ietf.org/html/draft-touch-time-06
> Htmlized: https://datatracker.ietf.org/doc/html/draft-touch-time
> Diff: https://www.ietf.org/rfcdiff?url2=draft-touch-time-06

For a further reference on the multiple kinds of seconds see
the proceedings of the 56th meeting of the CIPM in 1967
https://www.bipm.org/utils/common/pdf/CIPM-PV-OCR/CIPM1967.pdf

Annex 1 on page 139 is a letter from the CIPM to the IAU making it
clear that the ephemeris second still exists, just not as the SI unit
of time.  By extension, but not so clearly documented in the
proceedings of a decade earlier, the mean solar second also still
exists.  This reference gives the basis for the ongoing existence of
three kinds of second in various time systems.

Intentionally not clear in any official document is that members of
various international committees had agreed that the cesium-based SI
second was unrelated to the duration of the calendar day, and that
without a decision from an international body they could not redefine
the calendar day to be something other than one rotation of the earth.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Wed Nov 20 18:04:16 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885F112012E for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 18:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 Gzxab5bSfuEo for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 18:04:13 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03B62120077 for <art@ietf.org>; Wed, 20 Nov 2019 18:04:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4N4IpRaw6c4N3bKjruiYF25+zzdQyVhQriNiDW+l1UY=; b=mlN8ZwhMPQMEXYrGYCeQwwcSxD uljFs9SRryufqlE0sWMY5cQ/GIn6sQ4dNH6DbiyZGrfyDLsbplQrus/Zksc5Pw8kUXOBmZVd5gg4T 3ji2oTk/iYRDZcvYlqVA6vqxZc6uMAeByhKPl4kPn11foTxAahfbzmcDq+OnmbeZPPkIZN5eNFw50 O6VEakwrXmS06rPKONgbQfEGgl6380cdESy26PNmhB1MQ5PQ91VV/0SZN95MZTCkVhbbCbWZRII8u FnNKBjh1HQl3euwRKbbCxnk8L9f7UpWOZbwSHvsoFptqf1GfzuoXIswkkF59KOSCpriL7FaOjF6Tz pssU/ZKQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:55224 helo=[192.168.1.13]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iXbpI-002mZg-3c; Wed, 20 Nov 2019 21:04:12 -0500
To: Steve Allen <sla@ucolick.org>, Applications and Real-Time Area Discussion <art@ietf.org>
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com> <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com> <20191120235303.GA12868@ucolick.org>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <841d2c1d-7d7d-8124-a6cb-c397aca57ecc@strayalpha.com>
Date: Wed, 20 Nov 2019 18:04:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191120235303.GA12868@ucolick.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/zYqxJyI86ReGR6wr0H81PyOA1Mc>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 02:04:15 -0000

Hi, Steve,

I appreciate the more detailed information. For this doc, do you think 
this reference should be added as additional info? Does it affect 
anything else?

I.e., any particular suggested on what aspect of this needs incorporation?

Thanks,
Joe

On 11/20/2019 3:53 PM, Steve Allen wrote:
> On Tue 2019-11-19T18:16:55-0800 Joe Touch hath writ:
>> Name: draft-touch-time
>> Revision: 06
>> Title: Resolving Multiple Time Scales in the Internet
>> Document date: 2019-11-19
>> Group: Individual Submission
>> Pages: 21
>> URL: https://www.ietf.org/internet-drafts/draft-touch-time-06.txt
>> Status: https://datatracker.ietf.org/doc/draft-touch-time/
>> Htmlized: https://tools.ietf.org/html/draft-touch-time-06
>> Htmlized: https://datatracker.ietf.org/doc/html/draft-touch-time
>> Diff: https://www.ietf.org/rfcdiff?url2=draft-touch-time-06
> For a further reference on the multiple kinds of seconds see
> the proceedings of the 56th meeting of the CIPM in 1967
> https://www.bipm.org/utils/common/pdf/CIPM-PV-OCR/CIPM1967.pdf
>
> Annex 1 on page 139 is a letter from the CIPM to the IAU making it
> clear that the ephemeris second still exists, just not as the SI unit
> of time.  By extension, but not so clearly documented in the
> proceedings of a decade earlier, the mean solar second also still
> exists.  This reference gives the basis for the ongoing existence of
> three kinds of second in various time systems.
>
> Intentionally not clear in any official document is that members of
> various international committees had agreed that the cesium-based SI
> second was unrelated to the duration of the calendar day, and that
> without a decision from an international body they could not redefine
> the calendar day to be something other than one rotation of the earth.
>
> --
> Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
> UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
> 1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
> Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art


From nobody Wed Nov 20 19:38:45 2019
Return-Path: <sla@ucolick.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E465912093D for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 19:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cAiqhz8aMnpm for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 19:38:42 -0800 (PST)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496DF12093A for <art@ietf.org>; Wed, 20 Nov 2019 19:38:42 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 28DEF29E9 for <art@ietf.org>; Wed, 20 Nov 2019 19:38:41 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 2619B283F for <art@ietf.org>; Wed, 20 Nov 2019 19:38:41 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id 0CB14616 for <art@ietf.org>; Wed, 20 Nov 2019 19:38:41 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id xAL3cen5019255 for art@ietf.org; Wed, 20 Nov 2019 19:38:40 -0800
Date: Wed, 20 Nov 2019 19:38:40 -0800
From: Steve Allen <sla@ucolick.org>
To: Applications and Real-Time Area Discussion <art@ietf.org>
Message-ID: <20191121033840.GA19153@ucolick.org>
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com> <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com> <20191120235303.GA12868@ucolick.org> <841d2c1d-7d7d-8124-a6cb-c397aca57ecc@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <841d2c1d-7d7d-8124-a6cb-c397aca57ecc@strayalpha.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/C3vuOvm4kb33sL4Ma0QxmttS63A>
Subject: Re: [art] Fwd: New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 03:38:44 -0000

On Wed 2019-11-20T18:04:06-0800 Joe Touch hath writ:
> I appreciate the more detailed information. For this doc, do you think this
> reference should be added as additional info? Does it affect anything else?
>
> I.e., any particular suggested on what aspect of this needs incorporation?

Only the reference to the letter from the CIPM which serves to
demonstrate that even folks at the SI recognize that there is more
than one kind of second, just not in the SI.

For astronomers this was never a question, there were always mean
solar and sidereal seconds, and those have not gone away as the
other kinds arrived.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Wed Nov 20 21:09:47 2019
Return-Path: <touch@strayalpha.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35974120959 for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 21:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 tuVZxJMwF2MN for <art@ietfa.amsl.com>; Wed, 20 Nov 2019 21:09:45 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D17512023E for <art@ietf.org>; Wed, 20 Nov 2019 21:09:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4/6GSKZ3Aw/TncHjwBgo+A3h9EUnm/EAGe+tKqZgSbo=; b=p4o4sGzGmN/61NUDbwWpgj11Z DssH0ULdhmfC/YP69HkFo39s3xOt29fRwVmSN5PBbeigkSX1NJS5RTUgpAqq22+0oAyMC+BeSdpsI D7KDa/dyCqoTUc5D/rE1p1kgMQjie7xCgRP5SyEn717i/ehkieB960mK+74L3CtXJikXHU//O+jXe J4oRzkAu3m3A6nWHkkqT9NekgMWoSEICAAiz8FbzibEvnnLpGOXa6bgVlP2noqRuDjLTGxYO7mg41 3wOKiixzrNt98JBb6iuwHjSVtHzl2teCIhezfsARdytVZqA5JPlUNOtveU/cHCeena7hEc/Jv/432 8zdV4QXiQ==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59905 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iXeiq-0025Ys-RF; Thu, 21 Nov 2019 00:09:45 -0500
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <20191121033840.GA19153@ucolick.org>
Date: Wed, 20 Nov 2019 21:09:38 -0800
Cc: Applications and Real-Time Area Discussion <art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8E0AC77-E6D8-4556-90D9-1622BF2F1FE8@strayalpha.com>
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com> <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com> <20191120235303.GA12868@ucolick.org> <841d2c1d-7d7d-8124-a6cb-c397aca57ecc@strayalpha.com> <20191121033840.GA19153@ucolick.org>
To: Steve Allen <sla@ucolick.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/fsChmKdgoELP9O93rweObKuIsuQ>
Subject: Re: [art] New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 05:09:46 -0000

> On Nov 20, 2019, at 7:38 PM, Steve Allen <sla@ucolick.org> wrote:
>=20
> On Wed 2019-11-20T18:04:06-0800 Joe Touch hath writ:
>> I appreciate the more detailed information. For this doc, do you =
think this
>> reference should be added as additional info? Does it affect anything =
else?
>>=20
>> I.e., any particular suggested on what aspect of this needs =
incorporation?
>=20
> Only the reference to the letter from the CIPM which serves to
> demonstrate that even folks at the SI recognize that there is more
> than one kind of second, just not in the SI.

The draft is all about the fact that there are multiple time scales and =
already explains that there are multiple definitions of a second.

> For astronomers this was never a question, there were always mean
> solar and sidereal seconds, and those have not gone away as the
> other kinds arrived.

Nobody is claiming they have disappeared, including this doc. If =
anything, that=E2=80=99s partly the point - basically =E2=80=9Cwhen =
deciding to create a time scale, first - don=E2=80=99t. Use one that =
already exists=E2=80=9D.

Again, what is relevant to *this* doc that you can suggest to add?

Joe=


From nobody Thu Nov 21 09:28:04 2019
Return-Path: <sla@ucolick.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA97C12081D for <art@ietfa.amsl.com>; Thu, 21 Nov 2019 09:28:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3djDtU4yZ8Rq for <art@ietfa.amsl.com>; Thu, 21 Nov 2019 09:28:00 -0800 (PST)
Received: from smtp.ucolick.org (hunan.ucolick.org [128.114.23.233]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B01D120013 for <art@ietf.org>; Thu, 21 Nov 2019 09:28:00 -0800 (PST)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 23F4B2732 for <art@ietf.org>; Thu, 21 Nov 2019 09:27:58 -0800 (PST)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 212EF20D5 for <art@ietf.org>; Thu, 21 Nov 2019 09:27:58 -0800 (PST)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id 02F4F616 for <art@ietf.org>; Thu, 21 Nov 2019 09:27:58 -0800 (PST)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id xALHRudK005507 for art@ietf.org; Thu, 21 Nov 2019 09:27:56 -0800
Date: Thu, 21 Nov 2019 09:27:56 -0800
From: Steve Allen <sla@ucolick.org>
To: Applications and Real-Time Area Discussion <art@ietf.org>
Message-ID: <20191121172756.GB5177@ucolick.org>
References: <157421584935.5435.8112837302791582389.idtracker@ietfa.amsl.com> <d4234fba-ce03-26f6-168a-c58fc9e87af4@strayalpha.com> <20191120235303.GA12868@ucolick.org> <841d2c1d-7d7d-8124-a6cb-c397aca57ecc@strayalpha.com> <20191121033840.GA19153@ucolick.org> <B8E0AC77-E6D8-4556-90D9-1622BF2F1FE8@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B8E0AC77-E6D8-4556-90D9-1622BF2F1FE8@strayalpha.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/TANE_bmIai-U5xVUfY_INRQUZeQ>
Subject: Re: [art] New Version Notification for draft-touch-time-06.txt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 17:28:02 -0000

On Wed 2019-11-20T21:09:38-0800 Joe Touch hath writ:
> Nobody is claiming they have disappeared, including this doc.  If
> anything, that’s partly the point - basically “when deciding to create
> a time scale, first - don’t.  Use one that already exists”.

The reference C61 is from the BIPM itself, and they have included a
forward reference indicating that the decision in reference C61 is
abrogated.  So as written in this document the reference C61 nullifies
itself.

A reference to the proceedings of the 56th meeting of the CIPM in 1967
https://www.bipm.org/utils/common/pdf/CIPM-PV-OCR/CIPM1967.pdf
Annex 1 on page 139 (the letter from the CIPM to the IAU) clarifies
that the second is unusual in the context of the SI because, unlike
the other units, the second was adopted from outside the SI, and that
actions within the SI do not abrogate external definitions and usage.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m


From nobody Tue Nov 26 14:47:24 2019
Return-Path: <noreply@ietf.org>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id BADDA120B04; Tue, 26 Nov 2019 14:47:13 -0800 (PST)
X-Original-To: draft-nottingham-rfc7320bis.all@ietf.org
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 783CC120B02; Tue, 26 Nov 2019 14:47:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.111.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
Date: Tue, 26 Nov 2019 14:47:13 -0800
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191126224713.BADDA120B04@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 14:47:13 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/xOE9RGVmj-fOqXIAZuMMi5ebsT0>
Subject: [art] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2019 22:47:14 -0000

Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-nottingham-rfc7320bis-02
Reviewer: Robert Sparks
Review Date: 2019-11-26
IETF LC End Date: 2019-12-16
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as a BCP but with nits to consider during the
approval process

Nits:

Neither the document nor the shepherds write-up acknowledge or explain the
replacement of RFC6838 with RFC3986 for a reference for specifying fragment
identifier syntax and semantics (hence dropping the reference to 6838). It
would be nice to have something captured in the record that supports/explains
this change.

Near that change, there is a typo, currently saying "fragment identiers'
syntax" (should be "identifiers'")

It might be good to capture in the "Note to Readers" that the RFC Editor should
also remove Section 6.3 (URIs) since all the references to them will be removed
with the removal of this Note.



From nobody Tue Nov 26 15:10:19 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id E25DE1200EB; Tue, 26 Nov 2019 15:10:08 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DAF12010E; Tue, 26 Nov 2019 15:10:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=J26wNpgk; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TMCpcYK+
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 5Atwuw49cjes; Tue, 26 Nov 2019 15:10:07 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B0F1200EB; Tue, 26 Nov 2019 15:10:04 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CC0C822789; Tue, 26 Nov 2019 18:10:03 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 26 Nov 2019 18:10:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=HCChxzl72z9nGBZVR/seMjnTQhDL I/tABGfKqLakZsU=; b=J26wNpgk6rR5+KaXy76+p8++573cB+0G660cDifHeBMC fP1knlqbRciGvdJWX3vBwT1LPz8KZVIa+TcTW25NNTxbzHG+0v/nBijaaW9Rygtu XVpuxGy1yaX1zilrrNEkwqB6WGVX/1yV1TCiJBvA41sIGLG9PHEWYhSvuQ/potEr 08v8wcPdtuYXVasDD6mhIigphPHfCPvHEhzsn/TxevTc2EuVF3sMOTGJyyrC8gHA pmuQWVKD1oUWI2ryXQZCXh6vpTLh3qh2RGFiIO1H3TjQ9CdxMeB1xNeg4tsaeyme Svg3JSxtCmGL0m4xMTdb2TF0D4iHf4hH+nVg3NQBpA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=HCChxz l72z9nGBZVR/seMjnTQhDLI/tABGfKqLakZsU=; b=TMCpcYK+i1pPhbwf0A3C2m iylWDX38Lo0Grd4ghN9GOWxUprMYc1QW+El3PcFx+jxuH2ySQi0XqVoUT3kyJocv teyNL9EJL631UQU+28fGPDh8N1Fl2HGecvsh/wj3XenX1QypzbnRtPoSLDtSzRwW K4c/aAs1pHXHrVa2U4wLjCbnLLDtK89e3bBa9I+bp9lIXek/B5FSEK00yuk1MYsY S/yjKHMpeNrW9UyefBsiOLPhMU9mFdCzwU7Xl6EBtQ450vZE7a4tWQA7fxrJN8SQ 5l3b4D4qtA/N/9AKfbCvwEyTVk3G6kMtln8EW2Tv65X5V93ld7EU8B6/S0/Htfeg ==
X-ME-Sender: <xms:y7DdXaSoiEfjrc-_b2NrFLGE_gOHg_NwaQcSVtK6_Kac7CAN5QDW2w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeigedgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecurf grrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:y7DdXTn6lzP1uaaMX0HbzQqNheMSYD8mYrbz7gqj0eqdmyIJXd4HJQ> <xmx:y7DdXQ4gXu-S0bL8I721LtiFGjH0DCQ-OnQqzxB89adqKVj5H2i_qw> <xmx:y7DdXZiVoqCWQi0s34P9FiRE-GnEEYm1fIoprTBwI7dgAkUQj9S19w> <xmx:y7DdXeB4vn1UgWq-z0eDhMqBUodcXctMntu0bps2trIjbf1XbENONw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 371F6E00A2; Tue, 26 Nov 2019 18:10:03 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com>
In-Reply-To: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
References: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
Date: Wed, 27 Nov 2019 10:09:43 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Robert Sparks" <rjsparks@nostrum.com>, gen-art@ietf.org
Cc: last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
Content-Type: text/plain
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191126231008.E25DE1200EB@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 15:10:08 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/SGwtyhNa6K1SsOel1NLjUm0Fa38>
Subject: Re: [art] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2019 23:10:09 -0000

Thanks for the review Robert,

On Wed, Nov 27, 2019, at 09:47, Robert Sparks via Datatracker wrote:
> Neither the document nor the shepherds write-up acknowledge or explain the
> replacement of RFC6838 with RFC3986 for a reference for specifying fragment
> identifier syntax and semantics (hence dropping the reference to 6838). It
> would be nice to have something captured in the record that supports/explains
> this change.

I did notice this change in my review, but didn't consider it to be significant.  The shift in focus is within the bounds of what I consider editorial discretion as the effect is identical.


From nobody Tue Nov 26 17:54:44 2019
Return-Path: <rjsparks@nostrum.com>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 1104D1200B9; Tue, 26 Nov 2019 17:54:34 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8844B120816; Tue, 26 Nov 2019 17:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.28
X-Spam-Level: 
X-Spam-Status: No, score=-1.28 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.4, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 jIX_6StkyM4y; Tue, 26 Nov 2019 17:54:32 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A0B041200B9; Tue, 26 Nov 2019 17:54:32 -0800 (PST)
Received: from [192.168.3.102] ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id xAR1sTq7091224 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 26 Nov 2019 19:54:30 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1574819671; bh=WWCt9EVZqY2d/XkrQjw5Kh2IlloT4fnhVy5zusSUC88=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=vpkXoQfKE+olzwcyUlKZQz76egqaNBWx2o9Lpbh9m9+/k3yUyS5Zhcq2wLHmyW/HX uH5oVJbw3XLX+DBTctBTy0RAyIiDqXPYaKqPfrToFvhjgeymTkbGNRyk5kloAPoE4a K15NPCKA0hLYTQwPl+5s8Ml+W/tJ4BHxOX4Vb6So=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be [192.168.3.102]
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Robert Sparks <rjsparks@nostrum.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 Nov 2019 19:54:29 -0600
Message-Id: <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com>
Cc: gen-art@ietf.org, last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
In-Reply-To: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: iPhone Mail (17B111)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127015434.1104D1200B9@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 17:54:34 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/B8eGe1Q2-aZUVdPEICBuXDME1us>
Subject: Re: [art] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 01:54:34 -0000

Hi Martin -

Sent from my iPhone

> On Nov 26, 2019, at 5:16 PM, Martin Thomson <mt@lowentropy.net> wrote:
>=20
> =EF=BB=BFThanks for the review Robert,
>=20
>> On Wed, Nov 27, 2019, at 09:47, Robert Sparks via Datatracker wrote:
>> Neither the document nor the shepherds write-up acknowledge or explain th=
e
>> replacement of RFC6838 with RFC3986 for a reference for specifying fragme=
nt
>> identifier syntax and semantics (hence dropping the reference to 6838). I=
t
>> would be nice to have something captured in the record that supports/expl=
ains
>> this change.
>=20
> I did notice this change in my review, but didn't consider it to be signif=
icant.  The shift in focus is within the bounds of what I consider editorial=
 discretion as the effect is identical.

I don=E2=80=99t buy that. If the effect is truly identical, leaving the text=
 alone would have been more in keeping with your characterization of the doc=
ument that it exists only to make one change.=20

I suspect there=E2=80=99s more benefit to the change than an identical effec=
t that just makes the editor feel better.=20

To be sure, this isn=E2=80=99t a huge deal, but it really would help to not m=
ake the readers not guess why the change was made.=20

RjS=


From nobody Tue Nov 26 17:56:32 2019
Return-Path: <mnot@mnot.net>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 71D19120816; Tue, 26 Nov 2019 17:56:20 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12954120133; Tue, 26 Nov 2019 17:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=pd1Z9omY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=L1+7EI/O
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 uK-T6aJKoson; Tue, 26 Nov 2019 17:56:17 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78E60120816; Tue, 26 Nov 2019 17:56:17 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 81C9C22675; Tue, 26 Nov 2019 20:56:16 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 26 Nov 2019 20:56:16 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=3 Ir0hwKwwMwpLWZ/DyS2rU+G7kKdiu00266xdiZhioE=; b=pd1Z9omYyyTmDZUWo eNasbGrdVx4Mv4XDbyX9jwj7ISaeFji1gc3KQ+0yX4wwScL3aGCTij9KZ9gFWKMQ uBrinDRaqPsquIFVdLPP7VLZLmtDxXexmtpy546tgTOG6WFuyKRUUOFFnyj7kjY7 RqbCdYCDk5mz+TtmokUZMaEa9T6L/GgbEoli/Llab2Xyl/YU55JHCoLh3Kd3lKWn +Tgjvb1fRaFPKh2pba47vhZdgR/oQeDmdY1pLJSc2+17l6Hs16cq2WFdoFJk2J07 eMuSO8Ok/3GhHJj0tvjs5oOYOCNRawdmyzMgbW/k450B9YJvBC+3FLIkG1HmqEkj c6NqQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=3Ir0hwKwwMwpLWZ/DyS2rU+G7kKdiu00266xdiZhi oE=; b=L1+7EI/OEbT24jKnX0dhuZUm3fS8msqjV0uEvXB2H9J2QkUmUUkibY1XL AVpQcOz5vHxMcDBddEAUcRn93LHURAMAeMwHD3fJlrGJB6UdC8kaJWgVrt5mKAiJ eEQKTSRG9bLjwj47xmbUwjIn/lXR6QDEW8J+KY94lniAK4yzvilC/UJf0xOFsNO0 +YrTzBIPXbXh+d5wQ53BlbTYQZDvRGFIKHiNlDaIPE9gBczPP7ZHmyHjukZGAvr8 0hoNVKaChUpntUZeddVmuu6kAbaYezsW9XcqTReL+6yFTatR+CVcXTtk6EH+KsJa P117s/5cbKITy0/uqcCOK+GNmQbQw==
X-ME-Sender: <xms:v9fdXagPIe26cNx5jGVXiGFncYwkbyyJC5qrxSUudmmpvhDGT-IC4Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeigedgfeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehudenucfrrghrrghm pehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiii gvpedt
X-ME-Proxy: <xmx:v9fdXdrZ-V0rKlPIBlqfZ6sK4hNjz-nXhHK4fj82XB7Y1QYnOpxNDQ> <xmx:v9fdXRlMLbgSqREBd4pQARmtPayQzvswlzut0D4Q5csJzvyhpZy5pA> <xmx:v9fdXUnQOaKZ0DaGwl2NmZpM6uCw3LValuGq9F8a5qSWFtxuqSmz9A> <xmx:wNfdXSNIpnAUfcKDCKrWjodeBilV2xtQQzVF_IzGEM9iBrNpohOZFA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 5849B80061; Tue, 26 Nov 2019 20:56:13 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com>
Date: Wed, 27 Nov 2019 12:56:10 +1100
Cc: Martin Thomson <mt@lowentropy.net>, last-call@ietf.org, gen-art@ietf.org,  draft-nottingham-rfc7320bis.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3601.0.10)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127015620.71D19120816@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 17:56:20 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/rj3jrVQcHvI-VzgD5BAxZcsOJRE>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 01:56:21 -0000

On 27 Nov 2019, at 12:54 pm, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
> To be sure, this isn=E2=80=99t a huge deal, but it really would help =
to not make the readers not guess why the change was made.=20

Do we expect most readers to be comparing the documents so closely? This =
is an 'obsoletes', not an 'updates'.

Cheers,

--
Mark Nottingham   https://www.mnot.net/


From nobody Tue Nov 26 18:13:34 2019
Return-Path: <cabo@tzi.org>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 61AC3120B45; Tue, 26 Nov 2019 18:13:16 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152B0120B47; Tue, 26 Nov 2019 18:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 dv2oNfe7n2P2; Tue, 26 Nov 2019 18:13:14 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D52120B45; Tue, 26 Nov 2019 18:13:14 -0800 (PST)
Received: from [192.168.217.116] (p548DC893.dip0.t-ipconnect.de [84.141.200.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 47N47C6Gzqz10xX; Wed, 27 Nov 2019 03:13:11 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net>
Date: Wed, 27 Nov 2019 03:13:11 +0100
Cc: Robert Sparks <rjsparks@nostrum.com>, last-call@ietf.org, gen-art@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org, Martin Thomson <mt@lowentropy.net>
X-Mao-Original-Outgoing-Id: 596513589.122836-263569aa4b68b0f04a4b08ac4fd09507
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com> <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.9.1)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127021316.61AC3120B45@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 18:13:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/h-sKiyXUZBQEmi21udCeC5l728o>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 02:13:16 -0000

On Nov 27, 2019, at 02:56, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Do we expect most readers to be comparing the documents so closely? =
This is an 'obsoletes', not an 'updates'.

Speaking for myself as a reader only: Yes.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Tue Nov 26 18:32:29 2019
Return-Path: <mnot@mnot.net>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 8182112006F; Tue, 26 Nov 2019 18:32:18 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32ACF120116; Tue, 26 Nov 2019 18:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=DQVXa4J8; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=k7be1H5t
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 gVGE2OYoZLsG; Tue, 26 Nov 2019 18:32:16 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A46012006F; Tue, 26 Nov 2019 18:32:16 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id DD4292260C; Tue, 26 Nov 2019 21:32:15 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 26 Nov 2019 21:32:15 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=U 3JVEvzZS8+tJHKdbg9ikUXBem+1p/TlS1YgzUWA/Xg=; b=DQVXa4J8jFgNVzwQt sjVuLdBIkJePe8Y1v2J8K4gCPkuH4D4ENZ9SCSAx/IZYYMWmNU46iM0CAQPolq0q vS1Iz0U+7Nt25XNA3XZmoVZToPZhEo0r5oBwRngwLYfh4eibByb9WtYElEKQGWtf AK3gXOK1wlRHBvxfHZjRm1/+jwcUJ9ZRdpbMO9VO4WVZizSrCqiR9ogdVeZI50Gf auEyWyVGs6NOXydpGWxcQV4+r3pW30n5kP1l6VEEl6nys9609IqRDgFlqkzQddjM /ZM5Hv14kc/89eVIJ0xQhEWaKp37IoOnOewhv/COsL6quwx/iv7nsoAV7YmjIoKq KS82g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=U3JVEvzZS8+tJHKdbg9ikUXBem+1p/TlS1YgzUWA/ Xg=; b=k7be1H5tUAj0Jo5Uj6qWKbiL0N7cb1RU83oyZJ39ruPiRXJkPfK4D6n8i 5tlg7Wses1yi7qsR/IQzR708O8fMSyrXG8nDDm4aHCq2duVvpuk1Th9Fj6JdEs5C 2vCD9GtbbBemVIpRk7/1rCg5/9wcsdXYvpTnP8yvDnLKVAWFqjGJoKK4ss8eYn5K I79AFMHlbbvck7YzBjGr8n9Mt+uGWzfJp2sehn8nzgAZ4o1FNkrhBBMTcmBupzmB rQ7uRV6KF4nR7Fb0YBAjbEwi0yrYbVAh+a5VeKZfU40PjhtqwVM34wn6Vrs/JcVJ J7KDUM7qW0c3HEptBnwjgjF8VKp2A==
X-ME-Sender: <xms:LuDdXVSoaO9p1vAoK-nVrYLGjIPdqSmORSH8JmwkJLj8f3q_Zzn4dw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeigedggeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehudenucfrrghrrghm pehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiii gvpedt
X-ME-Proxy: <xmx:LuDdXTAZYJ1QzIRW8N3_SN48NfgC7n5gRRCCije-4_PRK2ismqrohQ> <xmx:LuDdXV3GdvLrbInEJ1G616-Wos_T9f_hsBrkMEwFqq0lqyATqd_8-w> <xmx:LuDdXRUNhYXfMXq2feItaQ1Agwatidh5DCDgkZKi3zsLVaofd7ouAA> <xmx:L-DdXSbAkXif3AgNRdZt7W6hlsZdANqIcr0bHN_WiSo8phZmQMXlgg>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 93F683060057; Tue, 26 Nov 2019 21:32:12 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org>
Date: Wed, 27 Nov 2019 13:32:09 +1100
Cc: last-call@ietf.org, gen-art@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org, Martin Thomson <mt@lowentropy.net>, Robert Sparks <rjsparks@nostrum.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C01295C-6EDA-4C32-8BA3-BD8DA3B9C9A2@mnot.net>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com> <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net> <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3601.0.10)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127023218.8182112006F@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 18:32:18 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/a_kXbAExWP2MjgJ20eFPpm0lvTo>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 02:32:18 -0000

> On 27 Nov 2019, at 1:13 pm, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Nov 27, 2019, at 02:56, Mark Nottingham <mnot@mnot.net> wrote:
>>=20
>> Do we expect most readers to be comparing the documents so closely? =
This is an 'obsoletes', not an 'updates'.
>=20
> Speaking for myself as a reader only: Yes.

My concern is that every time we add text to a document, we increase the =
cognitive load for readers; adding the reasoning for *every* decision =
and change expands a page of text into 2 to 3 (or more), so we need to =
impose a filter of some sort.

The requirement in question is:

 "Media type definitions (as per [RFC6838]) SHOULD specify the fragment =
identifier syntax(es) to be used with them"

It was removed because it was misleading (6838 doesn't make such a =
requirement a SHOULD), and the focus of this update was to reduce the =
number of unnecessary requirements. 3986 isn't replacing that reference; =
it's providing a grounding for what fragment identifiers are.

IME this information doesn't help the reader understand the document any =
better unless they're closely comparing the two documents (as reviewers =
are now doing, and thanks to them). If folks disagree, that's fine, but =
I'd like to understand why they think this information is worthy of =
documenting in-spec.

Cheers,

--
Mark Nottingham   https://www.mnot.net/


From nobody Tue Nov 26 18:34:35 2019
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 2D17E12006F; Tue, 26 Nov 2019 18:34:25 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2C31120116; Tue, 26 Nov 2019 18:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.4, MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 bb3s-OZIUrA5; Tue, 26 Nov 2019 18:34:23 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7454A12006F; Tue, 26 Nov 2019 18:34:23 -0800 (PST)
Received: from [10.32.60.117] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged)) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id xAR2WqUo071303 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 26 Nov 2019 19:32:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] (may be forged) claimed to be [10.32.60.117]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Carsten Bormann" <cabo@tzi.org>
Cc: "Mark Nottingham" <mnot@mnot.net>, "Robert Sparks" <rjsparks@nostrum.com>,  last-call@ietf.org, gen-art@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org, "Martin Thomson" <mt@lowentropy.net>
Date: Tue, 26 Nov 2019 18:34:17 -0800
X-Mailer: MailMate (1.13r5655)
Message-ID: <42A97B53-6644-4FE1-B0EC-5B0B530531D6@vpnc.org>
In-Reply-To: <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org>
References: <3a7db097-84c0-4c44-aed0-51196a6a16b6@www.fastmail.com> <9F9A2298-0088-40B2-A69C-7F63D17EB8E3@nostrum.com> <A88B004F-6426-41BF-9711-4071A63637B5@mnot.net> <23E269D1-06A1-4EE6-B886-5E5B3824C27E@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127023425.2D17E12006F@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 18:34:25 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/DAJz705koQrhec1HMFfIljA0RnY>
Subject: Re: [art] [Last-Call] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 02:34:25 -0000

On 26 Nov 2019, at 18:13, Carsten Bormann wrote:

> On Nov 27, 2019, at 02:56, Mark Nottingham <mnot@mnot.net> wrote:
>>
>> Do we expect most readers to be comparing the documents so closely? 
>> This is an 'obsoletes', not an 'updates'.
>
> Speaking for myself as a reader only: Yes.

Yes for me as well. Because 7320 has been used as a means of saying "you 
can't do what you want" to some protocol proposals, I definitely expect 
folks to look at the history if that happens in the future with 7320bis.

--Paul Hoffman


From nobody Tue Nov 26 19:17:02 2019
Return-Path: <mnot@mnot.net>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id E01241200F7; Tue, 26 Nov 2019 19:16:52 -0800 (PST)
X-Original-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67FDE120130; Tue, 26 Nov 2019 19:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Cegi3TQy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nuc/3KBE
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 OFUVMgW3Nl4n; Tue, 26 Nov 2019 19:16:47 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1057E1200F7; Tue, 26 Nov 2019 19:16:47 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6841F22643; Tue, 26 Nov 2019 22:16:46 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 26 Nov 2019 22:16:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=H XWBZyUASU9PudGp2JTgcTPSakUmoiTzo2uCBkFTntI=; b=Cegi3TQylRoGppWHV k+I71/YL4gj1rRUIng/30g46LYVxORHXejWgcv86Z1Af59WDJCDSWW4dac6wUptQ cUGUjKp9739LVDcmUo/1VCfuXPJbuoWo7SZdHl71ZDz6nYH5QOwlv5sJgcuukgie 1w/eT0BZOGmPMMyGapaTkgTtt06uNHTLiC1kYeXbjrl0cqlqxxEZTfz9FdKKnjbd 1VU3f+gRn7Tj0ku0v4rHcfqOPupp/jMsQzUPU8WE1XahFp/rEr1xS40xwkE1z6OC iNVPxUoPb9NR7NPAogBH3hdHWCu9wBon1UBS1LM5PUjsv1m4mWIDFDpmnbw07bAA +vUyg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=HXWBZyUASU9PudGp2JTgcTPSakUmoiTzo2uCBkFTn tI=; b=nuc/3KBE96rlkQJVcK9cRFZd+aC+rQrNhATmsK9TgwnfT5ZV8WEyxALyc 54U3XuuF70RVi3AJgBtL/T83x3czycw1aBypiYGeY8zzjnJxGptgD/mdV8BjiNF9 jaW6K8+Te/e85GtnnL9J4o2uyjM/rX5Rj6wFnaKwb9aa1KrwAA8dHjgL72yI9rsP TmZTXbZcKBMRMikNXpypL+KuUfBjsPeNyHNPSK46RlFXH3AaAZQHo3MCq1OvVu0A gaDlEPD+FczI2OLymWNEOCuTKcuqkVNWgtiIBkAj6kaI+qXAY+T9K+9P6GMuedE3 0HaTwgQstvI9GIR3pLMe3fKhnZ9Ig==
X-ME-Sender: <xms:nerdXQtaj7okzTpqlsrc4-_rzGmKAkFrMWRQaMxyYDLKFk_3rXhN1Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeigedgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh eprhhftgdqvgguihhtohhrrdhorhhgpdhivghtfhdrohhrghdpmhhnohhtrdhnvghtnecu kfhppeduudelrddujedrudehkedrvdehudenucfrrghrrghmpehmrghilhhfrhhomhepmh hnohhtsehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:nerdXXHrp6EUh3yF5qPjqbEBBuTcSOiBeaQzxcKXzvBkAsCf3lITEw> <xmx:nerdXby8BG6YsAY-F8dYevKDYJKI--hvIDsi6aizdBbx6fRVT1kJOg> <xmx:nerdXWhMY1Mw1sw4Iz13bmoxghpOUE8jGOow9YlSl_470cu4J8nyMw> <xmx:nurdXbToveIO5g3fDtU7-hheBZBkwCn58sBx_-KQ5rARW2nAQ2k28Q>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 63FFC306005B; Tue, 26 Nov 2019 22:16:43 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
Date: Wed, 27 Nov 2019 14:16:39 +1100
Cc: gen-art@ietf.org, last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <82A768BF-D9B1-4899-801B-B15C64D902E0@mnot.net>
References: <157480843342.13609.14136034204321908736@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3601.0.10)
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191127031652.E01241200F7@ietfa.amsl.com>
Resent-Date: Tue, 26 Nov 2019 19:16:52 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/b43r1IdU7DYPFY8yKbq2kEHTn-0>
Subject: Re: [art] Genart last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 03:16:53 -0000

Hi Robert, thanks for the review. Responses below.

> On 27 Nov 2019, at 9:47 am, Robert Sparks via Datatracker =
<noreply@ietf.org> wrote:
>=20
> Reviewer: Robert Sparks
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-nottingham-rfc7320bis-02
> Reviewer: Robert Sparks
> Review Date: 2019-11-26
> IETF LC End Date: 2019-12-16
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready for publication as a BCP but with nits to consider =
during the
> approval process
>=20
> Nits:
>=20
> Neither the document nor the shepherds write-up acknowledge or explain =
the
> replacement of RFC6838 with RFC3986 for a reference for specifying =
fragment
> identifier syntax and semantics (hence dropping the reference to =
6838). It
> would be nice to have something captured in the record that =
supports/explains
> this change.

See my previous e-mail in this thread for the explanation.

> Near that change, there is a typo, currently saying "fragment =
identiers'
> syntax" (should be "identifiers'")

Fixed in source.

> It might be good to capture in the "Note to Readers" that the RFC =
Editor should
> also remove Section 6.3 (URIs) since all the references to them will =
be removed
> with the removal of this Note.

Good catch; done.

I've also updated the BCP115 reference to BCP35, as per =
<https://www.rfc-editor.org/errata_search.php?rfc=3D7320>. I note that =
tools.ietf.org doesn't appear to be updated to make the relationship =
between these clear.

Cheers and thanks for the review,

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed Nov 27 15:32:03 2019
Return-Path: <steffen@sdaoden.eu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212CB120AFE for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 15:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 P8K60djm-kTS for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 15:31:59 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 923F4120AF8 for <art@ietf.org>; Wed, 27 Nov 2019 15:31:32 -0800 (PST)
Received: by sdaoden.eu (Postfix, from userid 1000) id 94EF916054; Thu, 28 Nov 2019 00:31:30 +0100 (CET)
Date: Thu, 28 Nov 2019 00:31:29 +0100
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: art@ietf.org
Message-ID: <20191127233129.9829F%steffen@sdaoden.eu>
Mail-Followup-To: art@ietf.org
User-Agent: s-nail v14.9.15-227-g6877bbc2
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/f6r8ZHdnzjhygvhG9l8AqFM9ySA>
Subject: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 23:32:01 -0000

Hello.

This is surely the wrong list, but neither am i at ietf@ nor do
i want to stress the admin for this.

But i just have downloaded RFC 8689 and the text is a top-down
conversion, likely from XML (terrible).  Meaning, no ^L'ss aka
\f's to separate pages, no page numbers, no page titles and
footers etc.  Is that normal now, or was that a mistake?  RFC 8617
still was of the expected formatting.
Shall this reported somewhere specific?

(It came down via FROM=https://www.rfc-editor.org/rfc/ by
: ${WGET:=`command -v curl` --silent}.)

Ciao,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


From nobody Wed Nov 27 15:32:53 2019
Return-Path: <steffen@sdaoden.eu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A77F120AFA for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 15:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 HCMjOC5dLQIt for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 15:32:50 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C2B512091B for <art@ietf.org>; Wed, 27 Nov 2019 15:32:50 -0800 (PST)
Received: by sdaoden.eu (Postfix, from userid 1000) id F0F0416054; Thu, 28 Nov 2019 00:32:48 +0100 (CET)
Date: Thu, 28 Nov 2019 00:32:47 +0100
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: art@ietf.org
Message-ID: <20191127233247.NdhoL%steffen@sdaoden.eu>
In-Reply-To: <20191127233129.9829F%steffen@sdaoden.eu>
References: <20191127233129.9829F%steffen@sdaoden.eu>
Mail-Followup-To: art@ietf.org
User-Agent: s-nail v14.9.15-227-g6877bbc2
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ulc7zS6fbLMcVciFn9ZYhT7X-pk>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 23:32:52 -0000

Steffen Nurpmeso wrote in <20191127233129.9829F%steffen@sdaoden.eu>:
  ..
 |footers etc.  Is that normal now, or was that a mistake?  RFC 8617
 |still was of the expected formatting.

RFC 8621 indeed.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


From nobody Wed Nov 27 16:27:53 2019
Return-Path: <mt@lowentropy.net>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9434E12013B for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 16:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=BNJA/BVb; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IIuHVHpk
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 XUY2nzod0rGd for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 16:27:50 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 203031200C4 for <art@ietf.org>; Wed, 27 Nov 2019 16:27:50 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4374222675 for <art@ietf.org>; Wed, 27 Nov 2019 19:27:49 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 27 Nov 2019 19:27:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=rbWtKhDIJgvfFUAWiP9QyT/RDtEa7RH GWYXD91cDYHs=; b=BNJA/BVbuQeDN57oxkFIsv4Ok+SeDHKOd7Yg+ahGqGTY83b fQDQnPDt6usgnqc+/Q8C/4x75Oxr5iLcHV/17wp89FrIeyGvC6EaY0JNGoCO8D2a qHp3iQXS+4Xi/BVOyhhn3WJIZ43q+u8zOwQJ/osi3A5R4oJCSYtqDqIVfJGVhiVX lRSpuQm6AMzoLRGZafq3XjFLU3soSg/XH4zv4efIBgEb2rJuRZxmKQDKupjh+9GW lNXKX0/NDjiAgL8Dqww1g8b9gS0QkhB80Wj6FUFaJ0zfSiT/isZBhvfvytVdxfWs ftRqRwTADfwQSdqSWd/8gV7UYDTAoMu4aOR/xwA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rbWtKh DIJgvfFUAWiP9QyT/RDtEa7RHGWYXD91cDYHs=; b=IIuHVHpkwuIvfPwPBx6WEQ t0nSUZufmEAlruytcKDFroKU7CVW7uYyOXMBXe3NB9J6JCFH3UjsxbbuBeiy9JzX Kn8jSk+6p11sjRaT9ixVrGhIxNmSRyfBSaFGaD3Eq7EvC6s+zen0yJ7JN1U3Pr8M 6d3mZN8U8yXDgJiMeLKbNLGqUmVrLubvUy058J3PjydB15LoIhFPe495xFo3IBjk ZxyPA3qW9pDWPzKPz1ny0Gx1j78UzcxoK4dBjE/I5oUqy/ctcK5e2pR7FIU8S/DZ 9/lVLUJiiOnKf9Y25RJrukbPweJ17v6EI0KtsxuohIEcrXYCISQw5pmYOHVZ3X6Q ==
X-ME-Sender: <xms:hRTfXT3HPsG3dpDo9NXkJaJBsLUibmkKhBD-z8Kca6wy5AaBGMBp4A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeiiedgvddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgnecurfgrrh grmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehluhhs thgvrhfuihiivgeptd
X-ME-Proxy: <xmx:hRTfXYqsnVa3QTBdLYRaFrXM3B-u72D0kMgSWRGFqyeMaYj840ACaQ> <xmx:hRTfXVnQQVoZIr__88nQ_cOSAalnlDKX3EIEKMsh-FOVJjFfL6T5Ug> <xmx:hRTfXST-MIG8Zu8v5FFPoCkIH07KB8ovg_APEuo-QHamWf30IslYyg> <xmx:hRTfXfxr41Ju8pdpOjadmjkVJ2YFuJp3Z63bxCLdEkLIY7enfocUfQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E718FE00A2; Wed, 27 Nov 2019 19:27:48 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
In-Reply-To: <20191127233129.9829F%steffen@sdaoden.eu>
References: <20191127233129.9829F%steffen@sdaoden.eu>
Date: Thu, 28 Nov 2019 11:27:31 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: art@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/4-7HYpV7lhVP1seyoZ_2_jCwniY>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 00:27:51 -0000

On Thu, Nov 28, 2019, at 10:31, Steffen Nurpmeso wrote:
> But i just have downloaded RFC 8689 and the text is a top-down
> conversion, likely from XML (terrible).  Meaning, no ^L'ss aka
> \f's to separate pages, no page numbers, no page titles and
> footers etc.  Is that normal now, or was that a mistake?  RFC 8617
> still was of the expected formatting.
> Shall this reported somewhere specific?

This is the outcome of the process that produced RFC 799x and friends.

See https://tools.ietf.org/html/rfc7990#section-7.3

The lack of links in the text-to-HTML conversion of tools.ietf.org is probably worth reporting as a bug, but a low priority one considering that the HTML version should be available.  That said, datatracker.ietf.org only offers "HTMLIZED" and not HTML links.


From nobody Wed Nov 27 16:50:07 2019
Return-Path: <steffen@sdaoden.eu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF73E120BA5 for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 16:50:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 aNguZARrFV5b for <art@ietfa.amsl.com>; Wed, 27 Nov 2019 16:50:04 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E073120B3A for <art@ietf.org>; Wed, 27 Nov 2019 16:50:04 -0800 (PST)
Received: by sdaoden.eu (Postfix, from userid 1000) id DD1BA16054; Thu, 28 Nov 2019 01:50:02 +0100 (CET)
Date: Thu, 28 Nov 2019 01:50:00 +0100
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "Martin Thomson" <mt@lowentropy.net>
Cc: art@ietf.org
Message-ID: <20191128005000.yMa3P%steffen@sdaoden.eu>
In-Reply-To: <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
Mail-Followup-To: "Martin Thomson" <mt@lowentropy.net>, art@ietf.org
User-Agent: s-nail v14.9.15-227-g6877bbc2
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/qo7n8BzRp7AbN2-EMd2x8YpDnLQ>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 00:50:06 -0000

Martin Thomson wrote in <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastma\
il.com>:
 |On Thu, Nov 28, 2019, at 10:31, Steffen Nurpmeso wrote:
 |> But i just have downloaded RFC 8689 and the text is a top-down
 |> conversion, likely from XML (terrible).  Meaning, no ^L'ss aka
 |> \f's to separate pages, no page numbers, no page titles and
 |> footers etc.  Is that normal now, or was that a mistake?  RFC 8617
 |> still was of the expected formatting.
 |> Shall this reported somewhere specific?
 |
 |This is the outcome of the process that produced RFC 799x and friends.
 |
 |See https://tools.ietf.org/html/rfc7990#section-7.3

Oh, i have missed this, thank you.

 |The lack of links in the text-to-HTML conversion of tools.ietf.org \
 |is probably worth reporting as a bug, but a low priority one considering \
 |that the HTML version should be available.  That said, datatracker.ietf.\
 |org only offers "HTMLIZED" and not HTML links.

Yah, hm, hm.  It surely has merits, both HTML as well as PDF.
I have a local RFC pool since, pooh, maybe 2003 or so.  The german
computer magazine c't once put all (?) of them on one of their CDs
by then, and i am only throwing onto that stock ever since.
I personally am almost perfectly served with plain grep(1) on
plain text.  Actually i do not even really care about missing form
feeds, i was only surprised.

Next time i report there.  The anonymous imap.ietf. thing reports
"Resource temporarily unavailable", that could be a possible
starter.

Ciao,

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


From nobody Thu Nov 28 02:27:43 2019
Return-Path: <petithug@acm.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C530120116 for <art@ietfa.amsl.com>; Thu, 28 Nov 2019 02:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.058
X-Spam-Level: *
X-Spam-Status: No, score=1.058 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_FMBLA_NEWDOM=1.499, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 1-ssJhPjFRPT for <art@ietfa.amsl.com>; Thu, 28 Nov 2019 02:27:40 -0800 (PST)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C476120113 for <art@ietf.org>; Thu, 28 Nov 2019 02:27:40 -0800 (PST)
Received: from [IPv6:2601:648:8400:8e7d:c9d2:c0b4:28:e68a] (unknown [IPv6:2601:648:8400:8e7d:c9d2:c0b4:28:e68a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 382B9AE4A2; Thu, 28 Nov 2019 11:27:36 +0100 (CET)
To: Martin Thomson <mt@lowentropy.net>, art@ietf.org
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
From: Marc Petit-Huguenin <petithug@acm.org>
Autocrypt: addr=petithug@acm.org; prefer-encrypt=mutual; keydata= mQINBE6Mh9wBEADrUEDZChteJbQtsHwZITZExr7TAqT7pniNwhBX3nFgd+FrV3lsLKJ1rym2 52MAYpubXEJZGzMp6uCCAnROWbtmQbOm8z/jHnjxHhPqfuYCYPpAQqu8K/Sc194Rp37krMwB jz32yr7+gvWLzRgQGKIh9d2mzy8QLMETVWWQWGb6fEfpOxXo0wumN1rc/275kZwOu44JIPGg zbgwZdnEqYOUUa18K9MXeRDoWbwDISP30CvKuZDwD14lbBE3o7tBQrU9uoMhE7eFlTjbsCox qoubI2tZSuOTF8mRXjPmNrRGtf9mYkQnOB7y6qy/QxmOVMq4IRtHzOYIm/EZ6NTodcpZQHOM 2v6B6YK9uKrYrapSpJzn4f9oU7alT31Y3o2hOlxAWDQ16+Dd1MOPYsKQXOwY1/ihm4PTjiJ8 ud8yPzy7c+BSVs5wkBU6QuLNIgZHrrxdn+KxM+F/oAVtfzO7XzVoeOcXyWi3/CHL5pgoBruY enIF/RrRuplpy09pvZjmFPNfqKBYJGnqpQuqsQwO7LsFqDqfY2EuHg+KsGN1XuN+jxXc48/1 gCnKw7ALSPWEb7g25wD6KfiZTAcyRTG8LePNFQKhw61LbIWmkw9EaVLyXvwPTc1iCSc0dDT/ pcT/z+8xrWOyWGZNZAjR584NlDpKollbItcxYtFcYZkvTCmOVwARAQABtCZNYXJjIFBldGl0 LUh1Z3VlbmluIDxwZXRpdGh1Z0BhY20ub3JnPokCOAQTAQgAIgIbIwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AFAlfy11wACgkQKcRFldZqfsRWqBAAu/61DGo+j38UefTKnEse0mftPBXa S4lre7vknn33MI0L5QXmiM8zRs9FOKSuXPx0EV+JhI4pWZGW/2MJPuyifXHvnIChcdGInN8J GBdTLZSOgdDFZL9msO+QUsvMA8ZUsqlKOEcVL1NyoLupblCWNq4fYhBCx1zDwX9LZSuGn8lZ Mk8a4QFGoR6dWKaOxeCwnoquW5IK1CfRIhYjHfQMjA5gY0H46F0iCqBaFF/S7krQwIJd0XN4 YbSL4KOrWuxtgQ+iH/iaxxBXgJ1blBNRzXaWJBF4PHv23nSnEzWO17j+uVMaHJu7ycYEf8T9 pVc0xcok1BM2rCrNE5FUFAzsUtAtBZEEK6sSIeOhRG93uD/Hv1hrWzEwf+Z7B1tVQLCQQ4kL 7wyS7SXI/JTuW2xTEGCmwMeWYGERdkgsatmx4zi5nVHDjt3/mlPMj4L+u05SkI2iV4W6xxU1 jHlBIJDs7AVM0dsxzTyIPf2Sz843WyHuBgkoCskxGfOwlkZzDX9rwcWRKal1wjy1w/25LsBY U50INandw3UbrS2I73VX8ARI8uOWZrW7uzRLf8EmuPhtSQ35ThmdoNSgGMP9EXwNgzi/i+5G hbX5KbrSLG9SITFJEcJA4tnwu3nqmBh7D7vbd5ln5X7rmqPdyjidt0zcSjvuaBA+nkmakA4A O+choWy5Ag0EToyH3AEQAL+LguHhcSDCL/IevdcvH/5/fzO2fmuuTxdGwrZZSm7l6/HD2Ira h6Wpa1LvVeRbnsRq8k6O8/i3wVapEoQPmNY3vjWfXaJb8R4vHcqgcxw9N9jhZa+mvGJk9+cI ilDyPzHRBBID4d/3oFKQCQ4Y2SIkO66znPhfBOS2f2AU7AtXHhVEyj6WsLK6boEMcj7j+w5a es2nZam0jhgoz+4DQem4uk8outrRlboGnZN7A2kCNuy39UeOp7BpvQ95IKcJCIeSoiJt2A4B NPQroqhW0zGn9Y9FJ9UiZ9YIeNPYbscUxxvrD+OU9Jv67hW0v3KfvoIKDwVKpO3MW6o+1teS Gt1KCSz+CvGJCvIxfCk7S5K5SBne7ZNKz7rkGXYIzlyr7ZoEgRHmqGmcK/sHTS4e6g2pQQrR USkspyqLZl5Uzmg7yI5oGBL0aHTzYdDkkOKMRXYnl7ivBeNtGcniGqlONLJxpbwec8j7hLRq pXFuepbtPqX/GefuK8rdo+ppEqpRJ50cJTegchTfWfSjn5/mG1B4Oz9OnOcBEeTLO729n0K9 BeTx1pmisD6P/fyrqZZTozDwVEi7Wo9AOaqWOhuTe8L0FlFIk6fc/yM0wzvDWP7sNrevEYHK V9rd+Yc/Jjt293J4uayrt6DNMmSkAw3nlBq3uK5d54J0FAsAUcsE/W2/ABEBAAGJAh8EGAEI AAkCGwwFAlfy11wACgkQKcRFldZqfsSQyA/+Kx3eWtKyb/y35TjgtjT/Hrtw+aIpr1uK97LA ln1j5m7+lQ/jh0/rvSZjs+YQMYLqVGI8oaaF/u+qrokkU6pfrhVZ49D1BmmSTMBSYgnBDYqZ yZ+uzQnnDYt/mpo2OLbl9BhuifR5QXLp43cE1FIhyDT46wfse5tNZ+ll4m4HtXuTw4W3b4cP Hto10260Mki7hXbkDMZ+icBFDMkrrZyYHSnBhelzIM7XnY7A/XZdulfFcDXEcZhAFEv3ylJs xTnGwzDyP1VAdBFL3hpP1CqfP1Kti4hKcxXZYbIgTSsBjcYbPchw3ktUTU29I/nWKH5gmD+q wFizyhtt8Qhl6U67OdZ/XbRGBXs/7tlYJIGiGZyG7IQtDOX0PsVd+6WRcDdFqkpBwYkxU8gd iCeW+YTQ5d8mXXPT2dhFAeK2hCFa2+IdaXvH8ovjZpTMeKstHrWJUDaSqQ4GFT676DbDyqtm P6Ul9cjGVtXIs64FWqR9wrbwBH1GuIHhDmG9sN5AkyB9mxXaEG3uG4E6qQeedtIKC6p+ebAs aTGgztFWMJDC8LUznu7B0oyWxNVoE/RGt5mesOeAtqYr6Jtdh7unyk8BYP1y4e+SSMwvtwh+ 69tJwNhGYbOJrdX34tXNAKb6r/rFRjVJm+sPPs5ok7LddvV35o+Fho0LRNDsioDV3HytlhA=
Message-ID: <e2317cdb-2cd9-7e80-990b-0e4481d05856@acm.org>
Date: Thu, 28 Nov 2019 02:27:28 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wIlaXVDrRDy8DNL9cMQnUdoc8z6UbesyM"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Eegwb1YLbNoHfz059sSxCKEbD6Y>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 10:27:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--wIlaXVDrRDy8DNL9cMQnUdoc8z6UbesyM
Content-Type: multipart/mixed; boundary="JS22FWFsZYEgdlOmYF6qkWiTnyyV7oEhi";
 protected-headers="v1"
From: Marc Petit-Huguenin <petithug@acm.org>
To: Martin Thomson <mt@lowentropy.net>, art@ietf.org
Message-ID: <e2317cdb-2cd9-7e80-990b-0e4481d05856@acm.org>
Subject: Re: [art] New RFCs text formatting
References: <20191127233129.9829F%steffen@sdaoden.eu>
 <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>
In-Reply-To: <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com>

--JS22FWFsZYEgdlOmYF6qkWiTnyyV7oEhi
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 11/27/19 4:27 PM, Martin Thomson wrote:
> On Thu, Nov 28, 2019, at 10:31, Steffen Nurpmeso wrote:
>> But i just have downloaded RFC 8689 and the text is a top-down
>> conversion, likely from XML (terrible).  Meaning, no ^L'ss aka
>> \f's to separate pages, no page numbers, no page titles and
>> footers etc.  Is that normal now, or was that a mistake?  RFC 8617
>> still was of the expected formatting.
>> Shall this reported somewhere specific?
>=20
> This is the outcome of the process that produced RFC 799x and friends.
>=20

Hmm, applying xml2rfc 2.35.0 on the xml file does not restore the headers=
, footers and page breaks.  Is there an option to generate a True RFC(tm)=
 or is it a bug?


--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--JS22FWFsZYEgdlOmYF6qkWiTnyyV7oEhi--

--wIlaXVDrRDy8DNL9cMQnUdoc8z6UbesyM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAl3foRAACgkQKcRFldZq
fsTj7RAApkGa4IY1ZlSNIY9aMqdYLF/B1A4NYNYOycdhO2Fc4ihCcxHIcHncWms4
jLjSW/hgMAdpzccVVvvh23Zs2bOXxAg/XO6I7opwgehQb2Mzml3h0fHdaHVpQrH8
Ll51ZeqPOIrzKgC1r8KSY5G/a8/yvjMNWXlGaPhtYlNRXF2hoT2ginJkhAsF6M6u
5/KEjaXSnkn0AaovAkrUFz8xS9EkMet1oo42hLRiAPpIOC2j0LVtKUIwcetVXgzp
bMDcNIDW3sXgE7gygJN5EYvpcFz3sJB5+pJ3sORO3ZaSNt2VQvXL4YQDwvxg53te
VXYnDeJff+JbanBWCCqOSsAGpellBKTCkcM6rvo26rE8s22h+ATXhTNSYN2MksUa
tXQ/W8goR1CsmU0RM0llHTJabtAxsDktw+56fwMrUmyvEvOLATjeAHYrwQe8bIMv
ydaCobQt9yEF9hgyX+uCFtlH1euQxAjIQ3/9laXWqgSI2plgmYLEqANj9PH04RPE
kfm8OortlN6VjxwbcwHsbzLQa2psCrECDmu9jTd1gjtbJV5uiFBVoqtR8ouyWZKS
gN/RljIz+6Izy64fLTg93cB0oiQWxi/rhMQUX2x76l27Rc2yx9oI6E+nb3vxyDG1
8luJs+OW5fL2sswUmoDkNJqViK3u7MvX0zk357syRU/OszIgFX0=
=FwRm
-----END PGP SIGNATURE-----

--wIlaXVDrRDy8DNL9cMQnUdoc8z6UbesyM--


From nobody Thu Nov 28 06:38:25 2019
Return-Path: <noreply@ietf.org>
X-Original-To: expand-draft-nottingham-rfc7320bis.all@virtual.ietf.org
Delivered-To: art@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 63B6F12022E; Thu, 28 Nov 2019 06:38:12 -0800 (PST)
X-Original-To: draft-nottingham-rfc7320bis.all@ietf.org
Delivered-To: xfilter-draft-nottingham-rfc7320bis.all@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33634120114; Thu, 28 Nov 2019 06:38:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Qin Wu via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: last-call@ietf.org, draft-nottingham-rfc7320bis.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.111.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Qin Wu <bill.wu@huawei.com>
Message-ID: <157495189212.5546.12078741991663995232@ietfa.amsl.com>
Date: Thu, 28 Nov 2019 06:38:12 -0800
Resent-From: <alias-bounces@ietf.org>
Resent-To: mnot@mnot.net, adam@nostrum.com, mt@mozilla.com, art@ietf.org, mt@lowentropy.net
Resent-Message-Id: <20191128143812.63B6F12022E@ietfa.amsl.com>
Resent-Date: Thu, 28 Nov 2019 06:38:12 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/RlniAxpgFPHv6XLc_22rIeufDYY>
Subject: [art] Opsdir last call review of draft-nottingham-rfc7320bis-02
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 14:38:12 -0000

Reviewer: Qin Wu
Review result: Ready

This document provides a good guidance on the specification of URI 
substructure in standards. One key value of this document is to remove
constraints upon the structure of URIs and provide best current practice on how
to specify structure and semantics within URIs. I believe it is ready for
publication.

Major issue:
Not found

Minor issue:
I am curious why this bis document is not published through WG process but
through individual stream process. If this document is published through
individual steam process with AD sponsored, should this document be classified
as informational? Where was this document initially discussed to build IETF
consensus? In which WG? Is removing constraints on the structure of URIs
causing a lot of debate, e.g., the following constraints relaxation: “ Note
that this does not apply to Applications defining a structure of URIs paths
"under" a resource under control of the server.  Because the prefix is under
control of the party deploying the application, collisions and rigidity are
avoided, and the risk of erroneous client assumptions is reduced. ” Try to look
into the history of the relevant discussion.



From nobody Thu Nov 28 08:33:13 2019
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 028AA12089D; Thu, 28 Nov 2019 08:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 4ClKjM3LKWu5; Thu, 28 Nov 2019 08:33:10 -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 05D79120859; Thu, 28 Nov 2019 08:33:10 -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 1iaMj5-000DLQ-9b; Thu, 28 Nov 2019 11:33:07 -0500
Date: Thu, 28 Nov 2019 11:33:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org
cc: art@ietf.org, rfc-editor@rfc-editor.org
Message-ID: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
In-Reply-To: <20191128005000.yMa3P%steffen@sdaoden.eu>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu>
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/art/npjUlAx2is8znJLJLVq1izNYxqI>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 16:33:12 -0000

(copying the IETF list -- this is not an ART matter alone)

TL;DL warning: while not terribly long, this is a rant.

--On Thursday, November 28, 2019 01:50 +0100 Steffen Nurpmeso
<steffen@sdaoden.eu> wrote:

>...
> Yah, hm, hm.  It surely has merits, both HTML as well as PDF.
> I have a local RFC pool since, pooh, maybe 2003 or so.  The
> german computer magazine c't once put all (?) of them on one
> of their CDs by then, and i am only throwing onto that stock
> ever since. I personally am almost perfectly served with plain
> grep(1) on plain text.  Actually i do not even really care
> about missing form feeds, i was only surprised.

Hi.  I realize it is very late, probably too late, to be
complaining about this, but my clear recollection was that, when
the v3 project was started, the community was promised that,
while the authoritative/ canonical/ archival format would shift
to the XML and fully-functional HTML and PDF format (not just
HTML and PDF produced from plain text forms) would become
available, the plain text format would be preserved sufficiently
that tools [1] that were designed for, and used with, RFCs for
the last 40-odd years would continue to work and work equally
well [2].  If page breaks, running headers and footers, and TOCs
and indices with page references have disappeared, some of those
tools will cease working (even if grep still does) and that
violates that particular commitment.  If there were an xml2rfc
v3 option that was guaranteed to be supported and that would
generate the older format, even if that format were never stored
on IETF servers, I think that would be sufficient to let us (and
our tools) keep working, but that does not seem to be the case
at present (nor does it address any TOC or index issues).[3]

This is especially important because at least some of us who
prefer the text form when working with RFCs (even if some of us
might prefer something else for reading them), after losing the
argument about whether XML (or any other generic or formatting
markup arrangement) was appropriate as the canonical/archival
form essentially tuned out of the discussions of xml2rfc v3
details and decided to devote our available IETF time to
technical standards and other work that we felt had impact on
the Internet rather than just on the IETF and how it operated.
The tuning out was reinforced as it became clear that xml2rfc v3
was evolving into a odd hybrid between generic and formatting
markup, one that was as or more likely to share the disadvantage
of each rather than the advantages and that, in terms we use
when talking about networking, raises all of the issues of layer
violations.  So we didn't read the reports and documents
carefully; we just assumed that, as long as the plain text
format was stable (pagination and all), we would continue to be
able to work without having to spend time converting habits and
tools.

Perhaps what all of this means is that I (and a few others) are
just old and stuck in our ways and that the IETF would be better
off if we just retired or otherwise moved on.   The "old" part
is certainly true for some of us but I'm not convinced about the
"better off" part.  However, by requiring us to develop new
tools or learn new tricks, this change may have the effect of
raising the bar for effective participation in the IETF enough
to push us out.   That is especially likely when we need to
review and revise older documents.  Personally, I think that
pushing anyone out who is willing to do work and might have
useful contributions to make is a bad idea.

So, even if it is too late to reconsider these decisions, I hope
we can at least be aware of possible negative side effects.

best,
   john


[1] The concern is about user-developed tools, used by one
person or a cluster of people who have shared them, not ones
developed or maintained under IETF auspices.

[2] Reading RFC 7994 only after these changes were identified, I
find that Sections 4.1ff remove headers and footers and the page
numbers from the TOC.  But the introductory paragraph of Section
4 does say 

	"One plain-text output will be created during the
	publication process with basic pagination that includes
	a form feed instruction every 58 lines at most,
	including blank lines."

So perhaps that omission is a bug.


[3] The last argument for removing pagination in Section 2.1.3
of RFC 6949 is almost completely bogus.   The problems with
unbroken sections that span several pages, including
difficulties with references to material in those sections, was
noticed not long after RFC 1543 was published with its specific
comments about cross-references to sections and not pages, IIR
much earlier.  There was discussion even before then about
insisting on numbered paragraphs, an idea that was abandoned in
large measure because of difficulties with document preparation
and tooling.  For some years, the RFC Editor pushed back
aggressively or (or simply modified) such very long sections,
especially when there were cross-references to them (by either
section number or page number).  Later, for reasons unrelated to
this rant, the pushback became much less frequent.  The problem
is over-long sections; the solution is to manage RFC Style
decisions (during final editing if not earlier) so that they
don't happen, not to pretend that eliminating page numbers will
eliminate those sections by precluding the possibility of using
page number for more granular references.


From nobody Thu Nov 28 08:59:51 2019
Return-Path: <cabo@tzi.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8124912085C; Thu, 28 Nov 2019 08:59:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tWyAzUGcwSDF; Thu, 28 Nov 2019 08:59:44 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D2CB120836; Thu, 28 Nov 2019 08:59:44 -0800 (PST)
Received: from client-0012.vpn.uni-bremen.de (client-0012.vpn.uni-bremen.de [134.102.107.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 47P3lf3pszzypK; Thu, 28 Nov 2019 17:59:42 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
Date: Thu, 28 Nov 2019 17:59:43 +0100
Cc: Steffen Nurpmeso <steffen@sdaoden.eu>, IETF Discussion <ietf@ietf.org>, art@ietf.org, rfc-editor@rfc-editor.org
X-Mao-Original-Outgoing-Id: 596653178.683643-cd7f13e4ed6a585f51b9fc34567a7b81
Content-Transfer-Encoding: quoted-printable
Message-Id: <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/OwHwK3mj5T6ta7zEJvX7yRGzhZ0>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 16:59:46 -0000

On Nov 28, 2019, at 17:33, John C Klensin <john-ietf@jck.com> wrote:
>=20
> So, even if it is too late to reconsider these decisions, I hope
> we can at least be aware of possible negative side effects.

It is never too late to fix this bug.

I think the last few months have uncovered a lot of usages for the plain =
text form of RFCs, as well as the fact that =E2=80=9Cnobody will ever =
look at the plain text now that we have HTML=E2=80=9D is maybe true for =
80 %, but not for 100 %.

Gr=C3=BC=C3=9Fe, Carsten


From nobody Thu Nov 28 09:55:18 2019
Return-Path: <Claudio.Allocchio@garr.it>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 085DC120219; Thu, 28 Nov 2019 09:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=garr.it
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 8WA-R5FC_35L; Thu, 28 Nov 2019 09:55:13 -0800 (PST)
Received: from cyrus.dir.garr.it (cyrus.dir.garr.it [193.206.158.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68B4A1200B3; Thu, 28 Nov 2019 09:55:13 -0800 (PST)
Received: from cyrus.dir.garr.it ([10.2.2.41]) by cyrus-mailhub1.dir.garr.it (8.15.2/8.15.2/Debian-8) with ESMTPS id xASHtB5v003278 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Nov 2019 18:55:11 +0100
Received: internal info suppressed
Date: Thu, 28 Nov 2019 18:55:06 +0100 (CET)
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
X-X-Sender: claudio@synx02.dir.garr.it
To: John C Klensin <john-ietf@jck.com>
cc: Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org, art@ietf.org, rfc-editor@rfc-editor.org
In-Reply-To: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
Message-ID: <alpine.OSX.2.20.1911281852030.30602@synx02.dir.garr.it>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=garr.it; s=cyrus; t=1574963710; bh=M/7PTEYvY3rM4BuUHb29j3XNRD12Cl9e7T+bTmJSWG0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=fDBtyoa6QAcm3ZdvCNgLnKiXKmtGdxulELIAhksULZf3wvT6jw8bTsqP7Cc12GAZg 42ay15jcyXpjG3A4/zloKJzyciKUgij3UB7Q8pKpwoe2uVGRFJNNNqpbyoVEYDyppf 7INLlN2c8B31Py7taqUghW8vzF3JgxeuUJruiiXc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/quH7kYulOpM7XyzIkr2GsOZ_YbE>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 17:55:17 -0000

and just let me add to John, that "aestetic" is not always a synonym od 
"funcionality". More machine processable formats are ok if there is an 
advantage out of their use, but if not... then, why?

It's late... but do not foget this

PS: no I'm not a nostalgic of TXT formatting, expecially of the itme when 
there were no toold than "vi" or equivalent an formatting according to 
rules was a real pain (and very few wanted to be I-D editors also because 
of this)...


On Thu, 28 Nov 2019, John C Klensin wrote:

> (copying the IETF list -- this is not an ART matter alone)
>
> TL;DL warning: while not terribly long, this is a rant.
>
> --On Thursday, November 28, 2019 01:50 +0100 Steffen Nurpmeso
> <steffen@sdaoden.eu> wrote:
>
>> ...
>> Yah, hm, hm.  It surely has merits, both HTML as well as PDF.
>> I have a local RFC pool since, pooh, maybe 2003 or so.  The
>> german computer magazine c't once put all (?) of them on one
>> of their CDs by then, and i am only throwing onto that stock
>> ever since. I personally am almost perfectly served with plain
>> grep(1) on plain text.  Actually i do not even really care
>> about missing form feeds, i was only surprised.
>
> Hi.  I realize it is very late, probably too late, to be
> complaining about this, but my clear recollection was that, when
> the v3 project was started, the community was promised that,
> while the authoritative/ canonical/ archival format would shift
> to the XML and fully-functional HTML and PDF format (not just
> HTML and PDF produced from plain text forms) would become
> available, the plain text format would be preserved sufficiently
> that tools [1] that were designed for, and used with, RFCs for
> the last 40-odd years would continue to work and work equally
> well [2].  If page breaks, running headers and footers, and TOCs
> and indices with page references have disappeared, some of those
> tools will cease working (even if grep still does) and that
> violates that particular commitment.  If there were an xml2rfc
> v3 option that was guaranteed to be supported and that would
> generate the older format, even if that format were never stored
> on IETF servers, I think that would be sufficient to let us (and
> our tools) keep working, but that does not seem to be the case
> at present (nor does it address any TOC or index issues).[3]
>
> This is especially important because at least some of us who
> prefer the text form when working with RFCs (even if some of us
> might prefer something else for reading them), after losing the
> argument about whether XML (or any other generic or formatting
> markup arrangement) was appropriate as the canonical/archival
> form essentially tuned out of the discussions of xml2rfc v3
> details and decided to devote our available IETF time to
> technical standards and other work that we felt had impact on
> the Internet rather than just on the IETF and how it operated.
> The tuning out was reinforced as it became clear that xml2rfc v3
> was evolving into a odd hybrid between generic and formatting
> markup, one that was as or more likely to share the disadvantage
> of each rather than the advantages and that, in terms we use
> when talking about networking, raises all of the issues of layer
> violations.  So we didn't read the reports and documents
> carefully; we just assumed that, as long as the plain text
> format was stable (pagination and all), we would continue to be
> able to work without having to spend time converting habits and
> tools.
>
> Perhaps what all of this means is that I (and a few others) are
> just old and stuck in our ways and that the IETF would be better
> off if we just retired or otherwise moved on.   The "old" part
> is certainly true for some of us but I'm not convinced about the
> "better off" part.  However, by requiring us to develop new
> tools or learn new tricks, this change may have the effect of
> raising the bar for effective participation in the IETF enough
> to push us out.   That is especially likely when we need to
> review and revise older documents.  Personally, I think that
> pushing anyone out who is willing to do work and might have
> useful contributions to make is a bad idea.
>
> So, even if it is too late to reconsider these decisions, I hope
> we can at least be aware of possible negative side effects.
>
> best,
>   john
>
>
> [1] The concern is about user-developed tools, used by one
> person or a cluster of people who have shared them, not ones
> developed or maintained under IETF auspices.
>
> [2] Reading RFC 7994 only after these changes were identified, I
> find that Sections 4.1ff remove headers and footers and the page
> numbers from the TOC.  But the introductory paragraph of Section
> 4 does say
>
> 	"One plain-text output will be created during the
> 	publication process with basic pagination that includes
> 	a form feed instruction every 58 lines at most,
> 	including blank lines."
>
> So perhaps that omission is a bug.
>
>
> [3] The last argument for removing pagination in Section 2.1.3
> of RFC 6949 is almost completely bogus.   The problems with
> unbroken sections that span several pages, including
> difficulties with references to material in those sections, was
> noticed not long after RFC 1543 was published with its specific
> comments about cross-references to sections and not pages, IIR
> much earlier.  There was discussion even before then about
> insisting on numbered paragraphs, an idea that was abandoned in
> large measure because of difficulties with document preparation
> and tooling.  For some years, the RFC Editor pushed back
> aggressively or (or simply modified) such very long sections,
> especially when there were cross-references to them (by either
> section number or page number).  Later, for reasons unrelated to
> this rant, the pushback became much less frequent.  The problem
> is over-long sections; the solution is to manage RFC Style
> decisions (during final editing if not earlier) so that they
> don't happen, not to pretend that eliminating page numbers will
> eliminate those sections by precluding the possibility of using
> page number for more granular references.
>
> _______________________________________________
> art mailing list
> art@ietf.org
> https://www.ietf.org/mailman/listinfo/art
>

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                         Senior Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

      PGP Key: https://www.cert.garr.it/servizi/informazioni-su-pgp-keys


From nobody Thu Nov 28 10:25:10 2019
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70C1E1208BB; Thu, 28 Nov 2019 10:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 Gj6Ojxqh0Gh0; Thu, 28 Nov 2019 10:25:08 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B68831208B8; Thu, 28 Nov 2019 10:25:08 -0800 (PST)
Received: from [10.10.10.159] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id xASINdhZ034601 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 28 Nov 2019 11:23:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.10.10.159]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "John C Klensin" <john-ietf@jck.com>
Cc: ietf@ietf.org, art@ietf.org, rfc-editor@rfc-editor.org
Date: Thu, 28 Nov 2019 10:25:05 -0800
X-Mailer: MailMate (1.13r5655)
Message-ID: <8FEF3892-AB75-4D61-AB5B-CF837C0D1773@vpnc.org>
In-Reply-To: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/FoJUXCa1GS4FmsWZ5Hw1vDVtR9M>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 18:25:09 -0000

On 28 Nov 2019, at 8:33, John C Klensin wrote:

> (copying the IETF list -- this is not an ART matter alone)
> Hi.  I realize it is very late, probably too late, to be
> complaining about this, but my clear recollection was that, when
> the v3 project was started, the community was promised that,
> while the authoritative/ canonical/ archival format would shift
> to the XML and fully-functional HTML and PDF format (not just
> HTML and PDF produced from plain text forms) would become
> available, the plain text format would be preserved sufficiently
> that tools [1] that were designed for, and used with, RFCs for
> the last 40-odd years would continue to work and work equally
> well [2].

I strongly believe you are wrong: no such promise was made. If you can 
find any actual message that made such a promise, I'm happy to stand 
corrected.

--Paul Hoffman


From nobody Thu Nov 28 11:06:03 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB7D81200F6; Thu, 28 Nov 2019 11:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 Hj2PrvfZnYQJ; Thu, 28 Nov 2019 11:05:54 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B829B1200A4; Thu, 28 Nov 2019 11:05:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1574967938; bh=+Rvn83BKMJsE37AzUTX0B2UsEynO4HBcq6H9r8ywCXM=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=lQ3dlXZe7GPypbtW+lSuMoqRUVkBxEc+x2u3Z9f7z0OL42D3QSPXy+vjLv8FOs8sI i7OsI2R8TYJcTgv7+EaSf8V8w9DyOUoZjgD6aD7krs30NNRfoMRp1xFbTwsFSAZ6S/ yvjOz8qvMjSRPY10skK8c4GSrVOXv257ZMEoENDQ=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.130.159]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MqJqN-1hxmiH1fwB-00nMKa; Thu, 28 Nov 2019 20:05:38 +0100
To: John C Klensin <john-ietf@jck.com>, Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org
Cc: art@ietf.org, rfc-editor@rfc-editor.org
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <502f830c-973d-cc9d-12b4-0bda40b05c46@gmx.de>
Date: Thu, 28 Nov 2019 20:05:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <08EE9B7B7C15D8F8B5DE6AF5@PSB>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:b4i9ZpVAYjD+Ap2eHuGNK8WqgkemCElIMPBRQxJ8t9W1Muv8eMV KVjzxu8Jsoyuw7Dm7n9WDw71PxB0EfZAy/ds8I0o/mNPM7iHqdOF7uBdV+RXM5EAbOWCaxW uEfGFKq/p6PIe0KNNIXCxIg0mrz2t4ggf05RK7gMtbKGZYaM903lRENrr3wuyZ16yr63oG8 3x+bry+dZZCqEbnw6hsWw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:wtByHHxDjJI=:KXMChsbdxSuk70ehSEtiWd 0g19cmlSlowbbJCAc1mpvPCDAD5zOm+tczDddHNb4CFlRPLsAMW/j2eb3A0Ro/Ht+/9NLp7B0 dmzzAxl5is66Gx+ev2lj636dp4II0Z5m+tqvQEuxWoRrYWx76F91yQxdaxS/zflKX4xkbfEdc AXCNS44vBQG6ioSt7GXE94JVVbxaJEDuQHFjIp01VbCXfJc3FqEpKIOyPtrME11AYBWULC9// E2eUPusDkR8F8iGRR2whbrCjOuNykf8cgZI6CeR7Sj0VT254C5IhhRIdgwjzhtOeisM6O2qn+ n85l32W0AEQOmfMPXV7xd5dfvb7uQJuUW25FuApgEbh5YS7pQejKaEfexevllQDKQ3haZk7YL 3cj/tMny5pnHgPaojFpMhOPxqRfHYkRGJJ3m8apZy8xXzZyxdWckH5Xo35S91CNC56g5WlWjw JTNNvDFGZVQg+yNDpXac31dAq+GE2FwOhva5RDh2U8zzFdLu4w/1ZECy+bsKofyk6lfnzYE7g 93OtooK4DyRPGrzS0s3UZ4/xXZyM6iS42I5NqJbk8h9xoz1GgmNN8UWfnPw4N4jFLbQ8y+uZ+ PsZ6qPdPwt8AMVlV9EQoP0s0VU7FNEqtGk3ZzeLwgFzmfWve7ym4BIexmb3WCSRR/p/Dr3evp 25jx0cxPYDaepSinO+gm2FUI3Rz/hqPEreanmHqvi+Bds6x3uyCsC7Z4CFg2/Bgb1Ln6aVmwb hDIBwE1QFqu/MJFjb1k3kpbfc0m8rMV4UVORcK1WWg9blbK9M+W2H/lLwvyzyZwYfhhUlMPxn pDaJyEsSUNdKuIGJWM0keOPFBD6wwX5LOLKlfab2EBtnssbSMFYN+nfSPym8cD8l7QCUgKlan L6ZX+sRUuQVGuroJfFvI9hjSD7SK/K5uxj1e+EqWXqW51dEvoc4A9zjLoXe9MLZCPhdDXdp1X 8HsUMyAIANtBVfsrP0/SNDKq/P3eFKNMOoUrR8Ysz8R5ELnDYXWCLXnj/+djaB21R7ZwP3Pof V5fBsPtkfS9Wr5Xn7yzK8tymv5EdW5KEQE8bO1LboCl/kxEKtPRp0KhyCwGTADXKQQHgfGIbi kfWeQSQBR1YPav5sabXtAq9E8pkFt8i0ngArTa2/Zq6c00ICq0uzWSW2Sv0lZ8cuABKR11hSS Yt3OHh6xh04Aydvu0qIufZI5o++bx7mWf/2vG9CEnoShQdiBmC6tSxQ8+w08IuZj2nw3E4gT3 /j5RLtcJB28Sip27/L5CuLMDwjbltVqQia3Yzyh0k8B6+3Dcob4ivCC2Y1gQ=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/mK3C96ohy789Nn2dbmotofTe3Uw>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Nov 2019 19:05:56 -0000

On 28.11.2019 17:33, John C Klensin wrote:
> ...
> [1] The concern is about user-developed tools, used by one
> person or a cluster of people who have shared them, not ones
> developed or maintained under IETF auspices.

Do you have a concrete case of a tool that fails with the new format?

> [2] Reading RFC 7994 only after these changes were identified, I
> find that Sections 4.1ff remove headers and footers and the page
> numbers from the TOC.  But the introductory paragraph of Section
> 4 does say
>
> 	"One plain-text output will be created during the
> 	publication process with basic pagination that includes
> 	a form feed instruction every 58 lines at most,
> 	including blank lines."
>
> So perhaps that omission is a bug.

AFAIR, the intent was to *paginate*, nothing more (yes, no headers,
footers, no page numbers).

 > ...

Best regards, Julian


From nobody Thu Nov 28 18:23:10 2019
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC89E12010C; Thu, 28 Nov 2019 18:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.105
X-Spam-Level: 
X-Spam-Status: No, score=-1.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 BeD5IpxmnOFd; Thu, 28 Nov 2019 18:23:01 -0800 (PST)
Received: from bsa3.jck.com (unknown [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 017341200FA; Thu, 28 Nov 2019 18:23:01 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iaVvp-0003Dz-G3; Thu, 28 Nov 2019 21:22:53 -0500
Date: Thu, 28 Nov 2019 21:22:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org
cc: art@ietf.org, rfc-editor@rfc-editor.org
Message-ID: <5A8862BB0F82FECBBF737CC6@JcK-HP5.jck.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
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/OGhvZQOPpgGElkNrSi69GW352ms>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 02:23:03 -0000

--On Thursday, 28 November, 2019 20:05 +0100 Julian Reschke
<julian.reschke@gmx.de> wrote:

> On 28.11.2019 17:33, John C Klensin wrote:
>> ...
>> [1] The concern is about user-developed tools, used by one
>> person or a cluster of people who have shared them, not ones
>> developed or maintained under IETF auspices.
> 
> Do you have a concrete case of a tool that fails with the new
> format?

Julian, I think that is precisely the wrong question to be
asking.  My note indicated that the concern was about private
tools, not ones that the IETF community has necessarily ever
been told about. I'll answer the question anyway, which is that
I have such tools, mostly written for an emacs clone as either
macros or in its proprietary extension language.  Some of them
predate even the first instance of XML2RFC.  A subset of those
include some that have not been used recently but that were used
to write drafts for RFCs either direct-to-text or using private
macros for nroff or similar format markup systems that were then
converted to text using those systems before submission. Others
have been in active use more recently.  One got into trouble
with RFC RFC 8689 because, for some reason, it tried to do a
search on "[Page" or some regex equivalent.  I don't know how
important that search is or how hard it would be to replace (I
haven't looked at the internals of most of those in 20-odd
years) but the point is that this is a more disruptive change
than some of would have predicted.

My response to Paul's comment is similar, again with the
observation that it may be much too late to do anything other
than maybe learn a lesson: it really does not make any
difference whether I can find a specific promise or not.  I
believe the community of people who work with RFCs (not just the
subset who have been designing and implementing v3 or the
overlapping subset who design and implement too for the
community) were led to believe this was going to be a
non-disruptive change.  We were told that we could keep working
in v2 (with whatever v2-prep tools we had) and submitting that
way and the Production Center would sort things out, and, while
v3 would bring many advantage to the Production Center, those
who wanted to use it, and people who preferred reading RFCs in
more "modern" formats, no one needed to make changes in how they
were doing things.  In addition to the positive things that have
been said about v3, to the best of my knowledge at least, the
community was never told "this is going to result in some
incompatible changes that you will need to deal with, are those
changes acceptable for the benefits they will bring".  In
itself, the absence of that question strongly implies only
changes that are non-disruptive except to those who choose to
use new features and to the Production Center.

Well, causing old tools, even non-public tools, to not work as
they did before and without changes to those tools is a
disruptive change.

>> [2] Reading RFC 7994 only after these changes were
>> identified, I find that Sections 4.1ff remove headers and
>> footers and the page numbers from the TOC.  But the
>> introductory paragraph of Section 4 does say
>> 
>> 	"One plain-text output will be created during the
>> 	publication process with basic pagination that includes
>> 	a form feed instruction every 58 lines at most,
>> 	including blank lines."
>> 
>> So perhaps that omission is a bug.
> 
> AFAIR, the intent was to *paginate*, nothing more (yes, no
> headers,
> footers, no page numbers).

That is certainly what 7994 says.   To me, the important
question is whether publication in that (and other) documents is
sufficient to warn the community about changes that may be
incompatible with tools or working procedures used by
contributors.  If the answer is "yes", then every one of us is
responsible for being thoroughly familiar with every RFC or
announcement that might affect IETF procedures, publications,
and other ways in which we do things so there is an opportunity
to raise timely objections.   I don't think we want to go there
but should instead assume that people in the community should be
warned by explicit questions and requests for consensus before
incompatible changes are made.  YMMD, of course,

   best,
    john



From nobody Thu Nov 28 21:02:16 2019
Return-Path: <julian.reschke@gmx.de>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B20FD1208ED; Thu, 28 Nov 2019 21:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 cdpfShTMvvr2; Thu, 28 Nov 2019 21:02:07 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 BF9DC12004A; Thu, 28 Nov 2019 21:02:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1575003713; bh=sRAccdfLdBIwRcr5RycLuPtdh7hK80bHpuoRLwjDMWA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=Uukr1HTbsTJarERhtv4wwkIJpiF0SepC5Ce7vlIVU2s1LtSzpGgP/Qsd+yeb4lxev fXgIuSkZtAG7HxkNDPJ3xYF4i1lBT29jeQ5Li+1Rb7BO3FMG6b5rEw6tXJ8VaUHJjN 8lD5RJq3teUFkP9Rhi04h48+N1M9f3CIvMWO3zUI=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.131.11]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MZCb5-1iEsoD3UfZ-00V8l7; Fri, 29 Nov 2019 06:01:52 +0100
To: John C Klensin <john-ietf@jck.com>, Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org
Cc: art@ietf.org, rfc-editor@rfc-editor.org
References: <5A8862BB0F82FECBBF737CC6@JcK-HP5.jck.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <725e1fd3-5af6-02f1-3a81-763797b8222c@gmx.de>
Date: Fri, 29 Nov 2019 06:01:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <5A8862BB0F82FECBBF737CC6@JcK-HP5.jck.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:0x7jlGAjAmJ/h74zPGJ69INU0FmwDtpTbSDd6dY6JRYFrqarexj ar/pisCFIYfoN1nr8+GR4sOkT+C6jPPkcCil1VcQMdo5aCDGfX/DypJo3p79jRX1E6JJMPP Fye+B6075E7LiCKyktxMDjlbo9+ID4E6LeiUfGkNZmoykbkUH4kzg40M40WBa9D7wJoMYuR 1Ud3tSXsfXH3VCwvNBFpw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:03yhrDPOHrc=:zsL7RAvvfD9P2ijqWiktdw IkD9ElogQQ/aLz/xXI/+/RuJiuHnK13PvAM1w3qt9JKGL/uyGeBHfuLuFn/w9n0VnER43orxy TQ1eaivOfzwmISFjQ2BeeiXvyASi04d6fNR5hYEmJ4Pykg2ey3pIMzGmXdjxenWlRf8m6MY1g q3Lo6i/efj4XxqGzNA41eXvSg81uLiXWQVVTmK/iu9MSCrvvRoKMwNmoF5uDxL90IAKHD75yL M7NBBQwcZjTOMp1XIUTb09lcNAL6aXCp6gmW6nbPP1y0olHIEuIVFoDgm9M2voiQB5y4mavJh d4lJF54cjbBrsVI9zwWbcIPhSfAmcLhvOOjGOOzMRoiOa96Cm+NV02gtFAUR4jNEMLBc7UNRv Ng364oIVJrOpvPs9je4b3OJrT6np92FqiRtgMvcPhx2puTY4ESMtn/wl0XPDxoJ5saPEqZ2wo rYnQGdGCVFJCRN8DVfGzhiFsyv8JrgIwd1aEANOoMPjapx9CFl6Wn40Dk5shMXUP20ftLbpzy KjkMSV8fcIQLqOibOzu/XaKOjdnYid87Nkuce16lG+JpPchcUq1+1Q6JzojFQuXhE8fgBZdFD WHEGEBSV619RYQ2trUvVKmHlXsATixIF4oQEzcsPaZ7q/eMbe80ANOR1banp/AG093lF2p9NC wCnuccpeVjS1xQ7CfFTU0wwz9tC/vl5CkJicXSomIGGQn9OruoyLT4AyEXMLsFAy1ldop0/Ts 4Z8OVi030GqtEWihvEt4G2sWv4FQBCCHyqXGTeBUNJAKWEWN7K/GCGRSDlu7G/WgZ32ipRgfI jMIayt+nWAjP6+r++F6ZxQP8k3yreHnErCNwmoeztkH8W/4WPatlax18VorZbo+3zg/yY98Ic hTnv/SGRjT1Xv6MIe5EbiCB4pjtHL+FPSeT3a0SwhMsAWENAfpEcny6iuAo56hN0QGkrr00Zq UcRfKOEOAs3pqRTM5Sppbphev/rcfKLqA1/9Y5OdW/IE74Rt9NtS10+jBpkhULjSzaAPb3KGs 3xG4XIhGoqQxR9JLqCoqp880ZfBn3XehpY0h6F2vJ5lNGIchwWXcjNOxOnBWU3VXvBaz8AXeS R5wh0D3vBA0VGrKb09DevxiydOrfOR4oP1baGJMAWtAFE6LMvuoMxWA93vmdRh/ZN2nsY1ECC KJMStPlR898SCRZgW7MGo7kqYoPyrXcBOQ/i5xiiD0VqGxdZtsfu5W7ETQm4rx2C3j33OAH1s Em3XqQYvEPBatia8Htvrn5T8/pbdqXZsk2HU2TNjLpxSx1HEr0TYta6Vgucg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/B1CIXSJjmnqhBkDCo-AlzSFfNvg>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 05:02:09 -0000

On 29.11.2019 03:22, John C Klensin wrote:
> ...
> Julian, I think that is precisely the wrong question to be
> asking.  My note indicated that the concern was about private
> tools, not ones that the IETF community has necessarily ever
> been told about. I'll answer the question anyway, which is that
> I have such tools, mostly written for an emacs clone as either
> macros or in its proprietary extension language.  Some of them
> predate even the first instance of XML2RFC.  A subset of those
> include some that have not been used recently but that were used
> to write drafts for RFCs either direct-to-text or using private
> macros for nroff or similar format markup systems that were then
> converted to text using those systems before submission. Others
> have been in active use more recently.  One got into trouble
> with RFC RFC 8689 because, for some reason, it tried to do a
> search on "[Page" or some regex equivalent.  I don't know how
> important that search is or how hard it would be to replace (I
> haven't looked at the internals of most of those in 20-odd
> years) but the point is that this is a more disruptive change
> than some of would have predicted.
>
> My response to Paul's comment is similar, again with the
> observation that it may be much too late to do anything other
> than maybe learn a lesson: it really does not make any
> difference whether I can find a specific promise or not.  I
> believe the community of people who work with RFCs (not just the
> subset who have been designing and implementing v3 or the
> overlapping subset who design and implement too for the
> community) were led to believe this was going to be a
> non-disruptive change.  We were told that we could keep working
> in v2 (with whatever v2-prep tools we had) and submitting that
> way and the Production Center would sort things out, and, while
> v3 would bring many advantage to the Production Center, those
> who wanted to use it, and people who preferred reading RFCs in
> more "modern" formats, no one needed to make changes in how they
> were doing things.  In addition to the positive things that have
> been said about v3, to the best of my knowledge at least, the
> community was never told "this is going to result in some
> incompatible changes that you will need to deal with, are those
> changes acceptable for the benefits they will bring".  In
> itself, the absence of that question strongly implies only
> changes that are non-disruptive except to those who choose to
> use new features and to the Production Center.
>
> Well, causing old tools, even non-public tools, to not work as
> they did before and without changes to those tools is a
> disruptive change.
> ...

John, with all due respect, there's a reason I asked, so for me this
question definitively is not the "wrong" question.

When we had these discussions many years ago, the assumption was that
tools that operate on plain text RFCs would strip pagination first (or
ignore it altogether) before doing what they need to do next. I would
like to understand whether this assumption was wrong, and how *exactly*
tools now break.

>>> [2] Reading RFC 7994 only after these changes were
>>> identified, I find that Sections 4.1ff remove headers and
>>> footers and the page numbers from the TOC.  But the
>>> introductory paragraph of Section 4 does say
>>>
>>> 	"One plain-text output will be created during the
>>> 	publication process with basic pagination that includes
>>> 	a form feed instruction every 58 lines at most,
>>> 	including blank lines."
>>>
>>> So perhaps that omission is a bug.
>>
>> AFAIR, the intent was to *paginate*, nothing more (yes, no
>> headers,
>> footers, no page numbers).
>
> That is certainly what 7994 says.   To me, the important
> question is whether publication in that (and other) documents is
> sufficient to warn the community about changes that may be
> incompatible with tools or working procedures used by
> contributors.  If the answer is "yes", then every one of us is
> responsible for being thoroughly familiar with every RFC or
> announcement that might affect IETF procedures, publications,
> and other ways in which we do things so there is an opportunity
> to raise timely objections.   I don't think we want to go there
> but should instead assume that people in the community should be
> warned by explicit questions and requests for consensus before
> incompatible changes are made.  YMMD, of course,
> ...

Heather has sent out mails, published FAQs, explained things at the
plenary, and had a poster at the RFC desk for a long time. I would say
this was hard to miss.

Best regards, Julian

PS: I have many other issues with the V3 switch, mainly that we are now
publishing "canonical" versions in a undocumented and un-reviewed
format. In comparison to that, the changes in the produced text format
currently seem to be a minor issue.



From nobody Fri Nov 29 06:31:17 2019
Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110FB1207FD; Fri, 29 Nov 2019 06:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.105
X-Spam-Level: 
X-Spam-Status: No, score=-1.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 cJ9hswxWWX-R; Fri, 29 Nov 2019 06:31:10 -0800 (PST)
Received: from bsa3.jck.com (unknown [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A941D12016E; Fri, 29 Nov 2019 06:31:10 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1iahIX-0004oO-8M; Fri, 29 Nov 2019 09:31:05 -0500
Date: Fri, 29 Nov 2019 09:31:00 -0500
From: John C Klensin <john-ietf@jck.com>
To: Julian Reschke <julian.reschke@gmx.de>, Steffen Nurpmeso <steffen@sdaoden.eu>, ietf@ietf.org
cc: art@ietf.org, rfc-editor@rfc-editor.org
Message-ID: <F7107E01971AACB319FA5B2C@JcK-HP5.jck.com>
In-Reply-To: <725e1fd3-5af6-02f1-3a81-763797b8222c@gmx.de>
References: <5A8862BB0F82FECBBF737CC6@JcK-HP5.jck.com> <725e1fd3-5af6-02f1-3a81-763797b8222c@gmx.de>
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
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/RRaTip_wJk56ls_DhaWXo1wSF_Y>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 14:31:12 -0000

--On Friday, 29 November, 2019 06:01 +0100 Julian Reschke
<julian.reschke@gmx.de> wrote:

>...
>> Well, causing old tools, even non-public tools, to not work as
>> they did before and without changes to those tools is a
>> disruptive change.
>> ...
> 
> John, with all due respect, there's a reason I asked, so for
> me this
> question definitively is not the "wrong" question.
 
> When we had these discussions many years ago, the assumption
> was that
> tools that operate on plain text RFCs would strip pagination
> first (or
> ignore it altogether) before doing what they need to do next.
> I would
> like to understand whether this assumption was wrong, and how
> *exactly*
> tools now break.

Ok, that is fair.  As can't speak for others but, as I think I
said in my earlier note, some of my tools do searches on
"[Page".  I don't remember why but suspect it may have had to do
with skipping over boilerplate or the like when those formats
were changing.  I don't know if my tools have other
sensitivities (see below) and won't know until I try to use them
and see what (if anything) breaks or do a careful code search.
I'm also not claiming that it would be hard to change those
tools --I just don't know without looking -- just that making me
(and others) spend time adapting is possibly not in the best
interests of the IETF if the total amount of time someone can
spend on IETF work is limited and that adaptation time takes
away from doing technical work.

>...
>> That is certainly what 7994 says.   To me, the important
>> question is whether publication in that (and other) documents
>> is sufficient to warn the community about changes that may be
>> incompatible with tools or working procedures used by
>> contributors.  If the answer is "yes", then every one of us is
>> responsible for being thoroughly familiar with every RFC or
>> announcement that might affect IETF procedures, publications,
>> and other ways in which we do things so there is an
>> opportunity to raise timely objections.   I don't think we
>> want to go there but should instead assume that people in the
>> community should be warned by explicit questions and requests
>> for consensus before incompatible changes are made.  YMMD, of
>> course,
>> ...
> 
> Heather has sent out mails, published FAQs, explained things
> at the
> plenary, and had a poster at the RFC desk for a long time. I
> would say
> this was hard to miss.

Most of those messages have said that v3 is coming, there are
big changes, throughput of the Production Center is likely to
slow down.  And, fwiw, I've seen the "RFC desk" twice in about
three years and, for personal (but IAB/IETF-induced) reasons,
have been somewhat tuned out).  AFAICT, none of those messages
have clearly said "if you are dependent on pagination and/or
per-page headers or footer, get over it", at least without
having that information buried (however unintentionally) in a
lot of material that was basically noise.

> PS: I have many other issues with the V3 switch, mainly that
> we are now publishing "canonical" versions in a undocumented
> and un-reviewed format. In comparison to that, the changes in
> the produced text format currently seem to be a minor issue.

What seemed to be a high likelihood of something like this
happening was one of several reasons why some of us were
concerned about, and opposed to, making the XML format the
canonical/archival one.  In this case, that concern was that,
once actual deployment started, the community would discover a
need to make adjustments to what was basically an untested
specification.   The need to debug something that had previously
been tested only among the developers and other very interested
parties and to make adjustments as the code was developed and
evolved should come as a surprise to no one with any experience
in programming or product deployment.  Having the documentation
be somewhat out of synch with that is no surprise either.

Whether it is a minor detail or not depends on how the community
reacts to the change.  As I understand the announcements that
have been made, people have the option of submitting text and
having the Production Center sort of the details.  So, suppose
that, either because of the interactions with existing tools or
because v3 is a someone-undocumented or under-documented moving
target, some of us drop back to preparing documents using nroff
(or one of its descendants), MS Word, or text directly and then
submit the text files?  You may know things that I don't, but
I'd assume that would either require much more staff in the
Production Center or would slow document throughput to a trickle
for a long time.  I would consider that a much more major issue
that either the tools issue or the undocumented and un-reviewed
format ones that feed into it.

As usual, YMMD.

   john


From nobody Fri Nov 29 08:35:46 2019
Return-Path: <bob.hinden@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB82E120A1E; Fri, 29 Nov 2019 08:35:32 -0800 (PST)
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 HQ7mEIAuG_Iy; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) (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 93D01120A25; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
Received: by mail-wr1-x443.google.com with SMTP id z3so35900846wru.3; Fri, 29 Nov 2019 08:35:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=AId8iazP5fJe2cxeDN4Ow+x9YK6uUhmDB4lgk1JUYRc=; b=oySlBXejVnyjAnxA+Ldtb++TCv2ZzZ9+AnT2fLtJyGf4r774cPLhzUzs+GO5QvYJrY HWtcCeRuD3EDYuE3O67Ile4xLUjzspSW0NvH5AGzOk5dtIUS+a1iYgrCQ5AWkzYqtopA qL9X0PS3qKediJMizypWTeDF88/O59IOwAkvAF6ih/C8LHszxo3cLexkWOB69gCyvXsT NdcBe0hjxUk4oRWf1YFZ7br3XJmES2ZNl/O+7hgd0tblAaj+P80vtKh/cwJaXWq0r6i6 xlAQZR9LyWyCVWsZCsWFd4IeFDbFQbBWftlu212CgnqKDkExFxL+uJZrIgKC0yleINng +J6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=AId8iazP5fJe2cxeDN4Ow+x9YK6uUhmDB4lgk1JUYRc=; b=C7uWKGTFtn7b/uN3WpZw093GpMjgt61em3M1axww7vQ45LaReO9Bv2CNVU7AZM2891 PWrKlyV+4jTVygw1H7EYX65A5U+vDdHG7i3dF1gZHa5Zdi4f76h7B80itRuUL4y9BVrs CvPtQu/tiBLjYHsImuyHYyP2Xm261Vu8XMQmf4ss0SzNtvaJToIjDDbYl6r64erswFuK T+7kyEOSY5xR9R89JkI2oUNUzLY/fDhKXNcUtj/vZvf/PBgjEHOFCxo1cTqDSBwm9CYI eicFI+ZJk+At/Gm+U9FzWb3anpa1DfM2vU0hc6gf1sPlH/znYFbzcFtwl6/ofNtrD104 w7NA==
X-Gm-Message-State: APjAAAVmml7bYMPt3LqAzkNM3/rkg+CFXd41oTJsUcbTFORN4dw3RVAh vedRVaV93Ub1yKUVdr33WdU=
X-Google-Smtp-Source: APXvYqwr+Fhuv2o+nTDhjJzgfAdjeZ2JEip6Mh2xtLDfQqFrd7gY+IyEW1TnQ01ZMhTesnE6VfgP1A==
X-Received: by 2002:adf:f803:: with SMTP id s3mr33472936wrp.7.1575045328918; Fri, 29 Nov 2019 08:35:28 -0800 (PST)
Received: from ?IPv6:2601:647:5a00:ef0b:289f:98c9:af3:443d? ([2601:647:5a00:ef0b:289f:98c9:af3:443d]) by smtp.gmail.com with ESMTPSA id d67sm13766547wmd.13.2019.11.29.08.35.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Nov 2019 08:35:28 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <95AE48FA-BBBA-40DC-939E-D81B41B73E22@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_205A6B93-4FF4-4CCB-A1BA-F23325EDAF28"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 29 Nov 2019 08:35:22 -0800
In-Reply-To: <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
Cc: Bob Hinden <bob.hinden@gmail.com>, John C Klensin <john-ietf@jck.com>, art@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>, Steffen Nurpmeso <steffen@sdaoden.eu>, IETF <ietf@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/FeTxurwNYfnlVQcSvhRRCPVpU8U>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 16:35:33 -0000

--Apple-Mail=_205A6B93-4FF4-4CCB-A1BA-F23325EDAF28
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Carsten,

> On Nov 28, 2019, at 8:59 AM, Carsten Bormann <cabo@tzi.org> wrote:
>=20
> On Nov 28, 2019, at 17:33, John C Klensin <john-ietf@jck.com> wrote:
>>=20
>> So, even if it is too late to reconsider these decisions, I hope
>> we can at least be aware of possible negative side effects.
>=20
> It is never too late to fix this bug.
>=20
> I think the last few months have uncovered a lot of usages for the =
plain text form of RFCs, as well as the fact that =E2=80=9Cnobody will =
ever look at the plain text now that we have HTML=E2=80=9D is maybe true =
for 80 %, but not for 100 %.

I think that is about right, I use both html and txt.  Html for reading =
on the screen, txt for doing comments and markups, excerpts in email, =
etc.

I have one active document that I converted to V3.   I note that the txt =
output of XML2RFC produces headers, footers, and page breaks.

The other thing I have noticed, since I now have the latest draft =
produced by V3 and the previous drafts produced by V2, is that several =
things changed that make this transition more difficult than needed.

The first I have found was when doing the conversion from V2 to V3, the =
default was to expand references, instead of the one line version.   =
This can be worked around when using the

--add-xinclude

when doing the conversion.

The other was default symbols in lists.   These can be worked around by =
using the --legacy-list-symbols when running XML2RFC.

My point is that in both cases I think the defaults should have been to =
make it closer to V2.  The current defaults make it harder to deal with =
converting an existing in progress draft from V2 to V3.  I suspect these =
are issues that many will run into when starting to use V3.

Thanks,
Bob


--Apple-Mail=_205A6B93-4FF4-4CCB-A1BA-F23325EDAF28
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEm0rfRsOCoyamPexGrut0EXfnu6gFAl3hSMoACgkQrut0EXfn
u6jllQf/QNUt+TV4Icr9DnovWEuw5waPIR5GRlJ+e5y7Q9J2D6YXvA4tO+R0zn4Q
UDWch1by9p/68PAQ9ows0Tc+wOB+A0gJz4CT2PFtBqy/dlpk5Tk0Pc8kB81xsA++
H/BH72ZYZqILfe/bj6DbdtNkF6Na3OXXPYZdv9xhqM5ciulo1OqCp9L+DPwK5PUt
weGdSIuEBrWv6NTJmh9pz12X1VQF94PuqeiUd/vZAY/V4hqWvZr/G2X+GVl7NDIR
GvXjlnVZyxvboybw18cVFQGYPGuloyGydKsBXShv2Fx4xbZVBawhKJ7rled6IVk0
du8iHXhNX9lv0HkHmN+JOnLYJr+oew==
=+5TT
-----END PGP SIGNATURE-----

--Apple-Mail=_205A6B93-4FF4-4CCB-A1BA-F23325EDAF28--


From nobody Fri Nov 29 08:59:23 2019
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045C4120A3B for <art@ietfa.amsl.com>; Fri, 29 Nov 2019 08:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 xPslcSKeNleE for <art@ietfa.amsl.com>; Fri, 29 Nov 2019 08:59:19 -0800 (PST)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720080.outbound.protection.outlook.com [40.107.72.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 481DC12086C for <art@ietf.org>; Fri, 29 Nov 2019 08:59:13 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=d/2o/1ckEuKZdaeNVjDq/5pkcEZFoeBMg/TIo4LiQEs0YiGKHhP9m72iWwrFhMp5Xtsns/YF+A6z9aZ9rfitxKrfvGcrDFpiggZ7IJI0etBvBrkcUBC6/R1DZmKSyUoi76ShqWVDoQVKI8gOEOWLoHn2ip6gaum+gJSH3o7oFrR2ZErlwuS5lz4fiH5XFY7/0RmNZvG4JylfIeewlSr52UPr5Im+oHyUY1EJw5Q27XuMZJH5aT5+gz1glFgMqAHU/dbflUKupCVR8VUUxu65YfBI7pzowzkn/Ah+yWGWQzFkA0IIpe7100+NXYixCBbaI7qPeNX5ebjaj3yheQlZIg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nix5SkkH4jbyQo7A34h3hNbKycUu8tZCph1sTqT9kvU=; b=HxiU3I6A9KsIofq/yDl51OOgp7t9QON6ZlTD6EO8D0uA9evX1O3OIks7HVGLpQ3BNiNGRL1ZD3bWqgJRhfKj8CqLwV6Ndr1agr/DE7hjXrbNfBLHu7m42Y6FuboixVJlmf0MEYvqsVx/OJ3aNPG0y6HOCLgOc+rBvy810deC4urcytWEZfmvoZJIVYjphdUCdor2v0VdBGntxzW//Si4tJvkHggYaKJBl4r9jbZ5HrOZFIH061dAL7ekuNNB12BJmJaxhGMUKX3W79hcO9lZep2iWdaqTU1DgcfUP1RUb5rDn49qyhjfp0AvSKSdzGHsTOQU6J+y/vnG9lKOaOI0dA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nix5SkkH4jbyQo7A34h3hNbKycUu8tZCph1sTqT9kvU=; b=aNatFGj6dqlINhciIMtmpdPusjzkq5TjS6ngF4E+i+d2KswVwpOIdn25H5i31UQTyEkvHsYyU4+2ANXSpp2uLCxlnAflxRLcji8E0wIV84Jkowk7dI6snUAOLOOBasepaNzeMiab1vSPK7XEYXc4JzJwccBBh3+Jh6cS5NXfD9c=
Received: from CY4PR1201CA0012.namprd12.prod.outlook.com (2603:10b6:910:16::22) by DM6PR12MB2938.namprd12.prod.outlook.com (2603:10b6:5:18a::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.17; Fri, 29 Nov 2019 16:59:11 +0000
Received: from BL2NAM02FT027.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e46::203) by CY4PR1201CA0012.outlook.office365.com (2603:10b6:910:16::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.18 via Frontend Transport; Fri, 29 Nov 2019 16:59:11 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com;  client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by BL2NAM02FT027.mail.protection.outlook.com (10.152.77.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.17 via Frontend Transport; Fri, 29 Nov 2019 16:59:10 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id xATGx9Zu027485 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <art@ietf.org>; Fri, 29 Nov 2019 11:59:10 -0500
To: art@ietf.org
References: <20191127233129.9829F%steffen@sdaoden.eu> <db882e3c-d3fb-4742-8456-7b400225ecce@www.fastmail.com> <20191128005000.yMa3P%steffen@sdaoden.eu> <08EE9B7B7C15D8F8B5DE6AF5@PSB> <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <27a16250-11c6-f807-6555-5d1eaf1a5711@alum.mit.edu>
Date: Fri, 29 Nov 2019 11:59:09 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <136271A4-28AD-4615-AD7E-EB63B95C05C3@tzi.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(39860400002)(136003)(376002)(346002)(396003)(199004)(189003)(53546011)(2351001)(65956001)(186003)(31686004)(336012)(86362001)(50466002)(65806001)(8936002)(47776003)(76176011)(2486003)(23676004)(2616005)(26826003)(478600001)(2906002)(26005)(446003)(11346002)(956004)(229853002)(4744005)(5660300002)(70206006)(14444005)(76130400001)(356004)(8676002)(246002)(786003)(75432002)(6246003)(31696002)(305945005)(7596002)(106002)(36906005)(70586007)(58126008)(2870700001)(2361001)(316002)(88552002)(6916009); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR12MB2938; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; A:1; MX:1; 
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: bc887c13-5b19-4cbe-e7f7-08d774ed74ba
X-MS-TrafficTypeDiagnostic: DM6PR12MB2938:
X-Microsoft-Antispam-PRVS: <DM6PR12MB293822A52E5CEDCEDD09C657F9460@DM6PR12MB2938.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 0236114672
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 0eBG07aF7nWws9CU5iS5bzyRbwusajV1xXOVtjqwIh2ZnhtiV4u6VlgIadewNuWQTxcWLmxvJddPzn6ONxWFyZRgpN5g2/M8Wg1vNzCRG20iXsPFbSnSKFpWv4NoUbhjIGhD3dLoVeGGXa5adE7TCjvfMSsjXMVDh2rxwG7oO4C7VyYRBmhPiM3ToV+Axmq3EToZ/pzxATdWQpbHIjzqdHQl7HwNunrnn9amzU8LyucqpGxqCbOfpMq2iJLAUHT3101YxLpi6NhjuSLYMr+LIQf0PDU33TJLoFtiDh74JSJHnc6dxf0mFquMwRqRTIgLvKocfaJdHVdTaalEakz4F+LXv+8x3ERqNxxlcIv0KSwqeCWEsEzYchYbdGLKwvZEvYU4r6hSF6nUwrYEUbxu8c+b/1No5b1xh+eoNU2vwW/VdSChwEOV0zdiEgAhmB/h
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Nov 2019 16:59:10.9430 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: bc887c13-5b19-4cbe-e7f7-08d774ed74ba
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33];  Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR12MB2938
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/L_iKQa3g6kVAzVIjOiQtPXn1VVg>
Subject: Re: [art] New RFCs text formatting
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Nov 2019 16:59:22 -0000

On 11/28/19 11:59 AM, Carsten Bormann wrote:
> On Nov 28, 2019, at 17:33, John C Klensin <john-ietf@jck.com> wrote:
>>
>> So, even if it is too late to reconsider these decisions, I hope
>> we can at least be aware of possible negative side effects.
> 
> It is never too late to fix this bug.
> 
> I think the last few months have uncovered a lot of usages for the plain text form of RFCs, as well as the fact that “nobody will ever look at the plain text now that we have HTML” is maybe true for 80 %, but not for 100 %.

I hardly ever look at the true HTML versions. I generally prefer the 
HTMLized form, as it offers many conveniences over the plain text while 
giving line-for-line compatibility with that. It is convenient for 
clipping sections of text into emails for commenting while retaining the 
formatting.

I expect that my interest in the pure HTML format will expand when there 
are documents of interest (to me) that that graphics that don't 
represent well in text.

	Thanks,
	Paul

