Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic

"John R Levine" <johnl@taugh.com> Mon, 14 May 2018 12:55 UTC

Return-Path: <johnl@taugh.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 8FB3712DB6C for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 05:55:42 -0700 (PDT)
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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=eOyCxtAr; dkim=pass (1536-bit key) header.d=taugh.com header.b=fqLu09/3
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 WaYZITCfHtUH for <ietf@ietfa.amsl.com>; Mon, 14 May 2018 05:55:41 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 ADDA11270A0 for <ietf@ietf.org>; Mon, 14 May 2018 05:55:40 -0700 (PDT)
Received: (qmail 53467 invoked from network); 14 May 2018 12:55:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d0d8.5af9874a.k1805; bh=lzEvYJruCDfNsVI36FzCHHEX2tsn8ML3SJ7Ru1scRoI=; b=eOyCxtArPPl3YaEyn8N5tAdpBZ0uOuxEpIcI7MrHQ5EeG2m6lBIyOC+BfJ6X1aj49KFMMGJO1vvkb6zGJ08ln4ZhZqBt/BlMCwIJzREZG2kG7e9s42aTwznnFCTihF1h3kcmBRPLx0LWXDoA0vl/BwdoQGtyzgK/Y5gyWmh+5PtLvecffDLdBjkQX1hbnkEijZqMW9v7A4fgG3iBxxyHucwpbytNyEhrfL//o/bkIW/1RKmaez/U33fT4F/0l9On
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d0d8.5af9874a.k1805; bh=lzEvYJruCDfNsVI36FzCHHEX2tsn8ML3SJ7Ru1scRoI=; b=fqLu09/3fdZ3fHeHqwFKRoFrse6DdU6XTJUR7W8ME02RFtv2I7k/K0EByk+b4+aio+mH/+CsR7DDhOXdGrM9kFxQx8yEXIBFK9pSZJDJGVkK3zeZCsNaEs/O+sfQjFhM7prBWc9XEs1uFziaKjSGuzFM1xI81HCfPVYMRm7O/jwPR8qKncSp9GMGLuvXakw0kqjhgA/mLcaSzq/Vyv7xFDB5f3BTcHjPa8wywsHI6lofOpNxHBM2Rtg/trFzDsGj
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 14 May 2018 12:55:38 -0000
Date: 14 May 2018 08:55:37 -0400
Message-ID: <alpine.OSX.2.21.1805140842110.39370@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Barry Leiba" <barryleiba@computer.org>
Cc: "IETF discussion list" <ietf@ietf.org>
Subject: Re: Last Call: Moving RFC 4405, RFC 4406, RFC 4407 (Sender-ID) to Historic
In-Reply-To: <CALaySJ+Nw80odyGXP+aimWrR2Hr1-OK+A-zTeC9Dc4QVHwatOQ@mail.gmail.com>
References: <CAC4RtVCq-27o7QjVfd8pES0Zi4zHaOs9uWh4eDR+L_Y4Os_JLg@mail.gmail.com> <20180514031854.ED51426858FB@ary.qy> <CALaySJJ13vrB76CGfyxpUobi0WGfRW8X0MDvwxc+kE92ZGTpVA@mail.gmail.com> <D16F6317605491B34CDB2D7F@PSB> <CALaySJ+Nw80odyGXP+aimWrR2Hr1-OK+A-zTeC9Dc4QVHwatOQ@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/efEOoMg-WJZET9sKEB7eiw2eEuc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 14 May 2018 12:55:42 -0000

> When the status change document is published, the metadata for RFCs 4405,
> 4406, and 4407 will point to the status change document, as you request
> below.

The RFC production center has a database of documents that they use to 
produce the indexes and per-RFC web pages.  I know something about it 
because I added DOIs to it.  That database has slots for one RFC to 
obsolete or update another, which show up in those indexes and web pages. 
They don't point to the datatracker or arbitrary URLs.  One of the reasons 
we have tiny historicizing RFCs like 7805 and 7142 is to leave breadcrumbs 
to the RFCs that they affect.

For that reason I have a lot of sympathy for Klensin's preference for a 
small RFC that contains the paragraph from the datatracker.  At a minimum, 
we should file an erratum on 6686 so it obsoletes 4405-4407 and that 
goes into the indexes and web pages.

R's,
John

PS: For anyone who's about to argue that it's odd for our processes to 
depend on an old database managed with PHP scripts I wouldn't disagree, 
but I don't think a rewrite is on the schedule any time soon.  It does a 
lot of other stuff coordinating RFC production and it works well enough 
for its main purposes.