Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)

Joe Touch <touch@strayalpha.com> Fri, 12 July 2019 13:49 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0582C120118 for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2019 06:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.217
X-Spam-Level:
X-Spam-Status: No, score=-1.217 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, MIME_QP_LONG_LINE=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 oJGP9YyAXy0B for <ietf@ietfa.amsl.com>; Fri, 12 Jul 2019 06:48:58 -0700 (PDT)
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 C7C111200CD for <ietf@ietf.org>; Fri, 12 Jul 2019 06:48:58 -0700 (PDT)
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=faooPglliFPRIWjoYmdKbY4zTBy5QUfma9a6iFsH7ps=; b=df66XUNspmrookv/IoV1Cl8YE GKd0cJu3GPEhevuwVTYC8eNwDrROezIqJdxnguZ15Y3yQ+/ZyCN64gKAaKt8Lf9oGc3ANcdDUvKLN OCzxFCOJpxJaX9agt23tHGXEeMMa/aAm02ryvJ/qj9/IpNpLIK6CiMsVICO4Gre/UyOwq0Rsf73Lk EIvmbVMFdE4EvriZPE76o+ebILVRZDbPLQ5CJ6eH8Nywb5/kww7NskWD/lRs9plYA1nvt/cLWHNkl YMZTYCv9u45W0rVVj4PmFjRTX+c2HA3soY8VfjZEtb4Y+2lV7uM3tBIUFsRvoOWOQiX4NzAuy8tSE DyIDM4brg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:65084 helo=[192.168.1.6]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hlvut-000Som-6v; Fri, 12 Jul 2019 09:48:56 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail-8E5B8A03-58AC-4921-A2B7-FF12C8884EC8"
Mime-Version: 1.0 (1.0)
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
From: Joe Touch <touch@strayalpha.com>
X-Mailer: iPad Mail (16F203)
In-Reply-To: <1FFE8C9F-5205-490A-97A1-A31661781F03@fugue.com>
Date: Fri, 12 Jul 2019 06:48:50 -0700
Cc: "lloyd.wood@yahoo.co.uk" <lloyd.wood@yahoo.co.uk>, Phillip Hallam-Baker <phill@hallambaker.com>, Christian Huitema <huitema@huitema.net>, Keith Moore <moore@network-heretics.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <6143CFB1-DDDB-483F-9322-17DD9E304808@strayalpha.com>
References: <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <20190710045202.GA3215@localhost> <20190710064451.GB3215@localhost> <06EF2608-038E-400F-86BA-34F57630B53F@fugue.com> <CAMm+LwjFgSK7DSaN2CpLxmL=PO22s2qjBvBHC48jH9UnFy8=wg@mail.gmail.com> <20190711172441.GN3215@localhost> <7FC9E7F4-FD46-4DD0-B623-D48647AC59FD@network-heretics.com> <CAMm+Lwim17yG-6a6TTPZ_jWNEwJDNH8yntzcRXztxoHi9ofnkw@mail.gmail.com> <AE2B5AB4-8241-49D8-8E3F-CD87F0E34144@strayalpha.com> <2077469571.58959.1562914196203@mail.yahoo.com> <324FF8ED-21F8-4D87-9511-FDD99DFDEF52@strayalpha.com> <1FFE8C9F-5205-490A-97A1-A31661781F03@fugue.com>
To: Ted Lemon <mellon@fugue.com>
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/ietf/3LrOT7U_oY53wZmdBepyVXKj2M0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jul 2019 13:49:02 -0000


> On Jul 12, 2019, at 6:17 AM, Ted Lemon <mellon@fugue.com> wrote:
> 
>> On Jul 12, 2019, at 3:31 AM, Joe Touch <touch@strayalpha.com> wrote:
>> My issue with the errata is that it presumes that URLs in RFCs ever need to be updated or corrected. They do not and should not. Search engines are more than sufficient to address the issue of URL ephemerality - which, FWIW, happens as much (if not more) at large public sites (such as ietf.org and Isi.edu) as privately run sites (such as mine at strayalpha.com).
> 
> This isn’t entirely true: a dangling pointer in an RFC actually becomes an attack surface if it’s important enough to search for the missing thing it once pointed to.  Now I can publish an alternative piece of software that you can download that not only converts word documents to RFCs, but also sends me your personal information, etc.

Microsoft disabled macros by default since Office 2016, so this won’t happen unless the user explicitly disables that protection (it’s a pop up on each Word doc with macros). I never mention macros in the RFC, so that’s not advisable.

But there are many RFCs with dangling pointers. Every RFC that pointed to ftp.isi.edu, for example. And as I noted, the IETF tools site URL has changed - in fact, it even has a dangling pointer ON ITS OWN page (to http://www.ietf.org/tools, which is even more insecure).

> The real problem here is that the RFC ever pointed to a reference link that wasn’t on an IETF web site.   The only time that I think this makes sense is as an informative reference.

That’s what this was, essentially. 

> Of course, in this case in theory they are just Word templates, but can’t those contain Visual Basic?

Yes, but see above about that being disabled by default when opening new docs unless the user overrides them.

Joe