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

Barry Leiba <> Tue, 07 June 2016 01:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B0EB12D151 for <>; Mon, 6 Jun 2016 18:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vbM3sSlp_p5j for <>; Mon, 6 Jun 2016 18:23:00 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6358D12D625 for <>; Mon, 6 Jun 2016 18:23:00 -0700 (PDT)
Received: by with SMTP id z123so61127249itg.0 for <>; Mon, 06 Jun 2016 18:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=gvsp1D2np/avFaAXyz61BXRi3dgFOK675lXgPWyEzRM=; b=lMC0Hk3PDOhLOVZPe72PhLNQknykGXW+b+Do502Uqg9AEIjBqI0e6WvjHBIyPrOLaJ IWxfLoVyEZ/xGDcfIhIZ90HDc/+YFgp82kgsYWcb7/D+a5IB+asssybWD0RxqaSfeFjV SZJEOjl1shCP2qKxwpQLJLnKZ1NLmwOz1LnGWBUdXYsp4jCwfIqKKIeGIFRv743FoD6Y 38epH2VMUeLlog0whm1VMX/6gGc7gtbbQeH5W+qi6yqGiS4P6o9x+XOhwSCb0ACU8Any BqtCcG42PaTXJmnIdNNDXRW/KZJW5lJ2WUei4FYW4cwVo4nWfb7Mk8z0lc2B4gCshQ3s ISJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=gvsp1D2np/avFaAXyz61BXRi3dgFOK675lXgPWyEzRM=; b=cUkmqnQpQvjNjEk7wV+VAZ6AX4qyO2UGtz63InBuhENkTLdT19ajTNm7N79eclCNUA uPjGeaInWQ+D/OzAvR1Y+9PiuCvcgHAy3Bzr8PA8+/y8CqtVnQqCZrmXEZLKWMrgA+Sc oziIaOaZRw+qNB9fVg//4jtyDHgGLSvjiuNlKawYbIuDvi/e4lGxeRlXju0KWXcsL+WE u7NiRxCh17E6RUL4h2XDYR7dVJueJ6RFt28tW6dz6baxftFCze02A3d5llHjlZHfva1j wE7SdpEjQs1hZL5n8jzYUtywIZrpax43/lE+5BL83q6uXMVVCF6uiLeWnuVfnPt/KkTt 45aw==
X-Gm-Message-State: ALyK8tIL22aeoMJ0AX9V9tYv/ny46nHyRD0PtW2bQh2DtScJjIvGeuBmSxbUZ52t/dPsejRpV6TLRrJCu6wEhA==
X-Received: by with SMTP id m11mr2100106ita.96.1465262579779; Mon, 06 Jun 2016 18:22:59 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Mon, 6 Jun 2016 18:22:58 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
From: Barry Leiba <>
Date: Mon, 6 Jun 2016 21:22:58 -0400
X-Google-Sender-Auth: VxzZ1tYAegP6uED0Gp1afVs_W0Y
Message-ID: <>
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: Stephen Farrell <>
Content-Type: text/plain; charset=UTF-8
Archived-At: <>
Cc: IETF discussion list <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Jun 2016 01:23:01 -0000

OK, I have new text to propose for the paragraph in question (sorry:
it makes it a bit longer) as a result of this discussion.  Thanks,
everyone, for putting in your comments.

Stephen, and all, how does this work?:

   If information for registered items has been or is being moved to
   other documents, then the registration information should be changed
   to point to those other documents. In most cases, documentation
   references should not be left pointing to the obsoleted document
   for registries or registered items that are still in current use.
   For registries or registered items that are no longer in current
   use, it will usually make sense to leave the references pointing
   to the old document -- the last current reference for the obsolete
   items.  The main point is to make sure that the reference pointers
   are as useful and current as is reasonable, and authors should
   consider that as they write the IANA Considerations for the new
   document.  As always: do the right thing, and there is flexibility
   to allow for that.