Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice

Joe Touch <touch@isi.edu> Fri, 03 June 2016 23:40 UTC

Return-Path: <touch@isi.edu>
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 ED29A12D9EB for <ietf@ietfa.amsl.com>; Fri, 3 Jun 2016 16:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 yJpr0AgKtkJQ for <ietf@ietfa.amsl.com>; Fri, 3 Jun 2016 16:40:37 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 B914512D8F9 for <ietf@ietf.org>; Fri, 3 Jun 2016 16:40:37 -0700 (PDT)
Received: from [128.9.184.224] ([128.9.184.224]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u53Ne8pb016057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 3 Jun 2016 16:40:09 -0700 (PDT)
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Barry Leiba <barryleiba@computer.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com> <575185A2.70908@cs.tcd.ie> <EDA3CD0D-BDCA-4AC6-AA67-318670080338@sobco.com> <CAC4RtVBngkPc-yQ8P0qyvwsG9L4qjDMDPZ5xwa4gR84=ov4iUg@mail.gmail.com> <CAF4+nEHzvVOq_1L2ukX-OcPGkVFgR2OOD5puLMBJGif3a=Hzaw@mail.gmail.com> <CAC4RtVC6sKnYQS3mOay8-rSLQ0+U5mYGVhBbSSD=0xNX6dt2ng@mail.gmail.com> <5751D5E8.6030803@cs.tcd.ie> <CALaySJ+3jorRopPKNHjy19fo1v1=dZEHarMJ1-gB89vNbkFxaw@mail.gmail.com> <5751ED8B.4020508@isi.edu> <9b7a1b04-f767-517a-bd84-28c030695dfc@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <57521556.7050100@isi.edu>
Date: Fri, 3 Jun 2016 16:40:06 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <9b7a1b04-f767-517a-bd84-28c030695dfc@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SzWPgX9u9JJjl0pNWwXhuZjy2Uk>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Jun 2016 23:40:39 -0000


On 6/3/2016 4:35 PM, Brian E Carpenter wrote:
> On 04/06/2016 08:50, Joe Touch wrote:
>> FWIW, IMO this is all make-work.
> Disagree. Misleading pointers on the IANA site will mislead some
> junior programmer sometime in the future, by a simple application
> of Murphy's law.
>
>> IANA pointers to the old doc should turn up "obsoleted by" notices. That
>> ought to be enough to trigger the user to follow the right path.
> That's not realistic. If IANA refers to RFC822, and the programmer has a
> copy of RFC822 on her disk, that's what she will follow, because RFC text
> never changes and does not say "I am obsolete".

If someone has a copy of IANA ports on their disk, no amount of updating
will fix the fact that it points to the wrong place.

We either expect people to use fresh information or not. Anyone who uses
RFCs should be accustomed to using the version that flags obsoleted docs.

Joe