Re: New Version Notification for draft-leiba-3967upd-downref-00.txt

Barry Leiba <> Tue, 09 August 2016 20:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5E4E412D54C for <>; Tue, 9 Aug 2016 13:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZC0ZIGiOj2CR for <>; Tue, 9 Aug 2016 13:03:51 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 814A112D0B8 for <>; Tue, 9 Aug 2016 13:03:51 -0700 (PDT)
Received: by with SMTP id w38so11196929qtb.0 for <>; Tue, 09 Aug 2016 13:03:51 -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; bh=wIBAUCSCXwGBPvQBsWRGo3rMRVFzzoNV9zlDwDR+kN4=; b=PTHq2QRsmuZ0zUv/kKlJOV8c5xpW/UKKRxwlW5sFDRWFUmrkWnfWkRaJZd3Im4x7m0 FbLN+penkrD7m9SBEBfdq+Afbm2YgetCebp/t6CGWRfCcVTVMmKqqaMjVoLXWtXjKkMm lCQLM+6qBUNXYMQDaOjRLR55Q+3l0+GbXGATERiXwjqFuL1AdJwWOhqG6i0T/1Og/f2O LruiC/QwI2Gc8YSaDlTXexyM1oBXit80WWwkGnXtKuYf+xfEZfZqccmy88MOH98E1x6b ZYHJleeNVYQ8vYWya3XX4jJe3nMZmWgfr1GksoY2LF0aei+Hi9S3dw6ojp4rP8Fttzs2 eQHw==
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; bh=wIBAUCSCXwGBPvQBsWRGo3rMRVFzzoNV9zlDwDR+kN4=; b=Uao2TdmekhVfQzKmD0CvCQ+lBP8ipLIy3kjVxMbOvBbbbGGvayY+ZTLAPkZU+mA6J7 a+DzTIrvSUXLQvxZzKOKqDrvyoqgfXt+s7QRAV4mQnjfb4HhSqWkCv2LLFX0svDLbfjA riTcxhbeaP1QuBqZ8Am6B+mF3QcMsUjrk1uuT1yUzTiD8AXGLk5tfYjhkbX4MDdLT1SQ EfLMocCgVFQBJVl0toebhp+/OzIpEkKD3c/JxXHsK2QZYaYOjIa4fBByc5zmFBgmnZsu xkpIEmmCik7zz3MPFFFkOzhFA14UFWY5Cjp7mQ0eaDzr76QibkUofzzcm4d1CiRIBgEE p9xw==
X-Gm-Message-State: AEkoouvja2HgTaZYr0CnF9ESBsWXpnb0H5DZli1JzIfAB+cFeEAweruvMX0BdsJfe9+WCp3zRmyfvcq08Ka4oA==
X-Received: by with SMTP id b25mr229441qta.72.1470773030424; Tue, 09 Aug 2016 13:03:50 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 9 Aug 2016 13:03:49 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Barry Leiba <>
Date: Tue, 9 Aug 2016 15:03:49 -0500
X-Google-Sender-Auth: vu7sAb_S1L4-L2cj_ueT1fC7v9Y
Message-ID: <>
Subject: Re: New Version Notification for draft-leiba-3967upd-downref-00.txt
To: IETF discussion list <>
Content-Type: text/plain; charset=UTF-8
Archived-At: <>
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, 09 Aug 2016 20:03:53 -0000

This draft is meant to address something that's become a significant
annoyance for the IESG over the last few years: Standards Track drafts
from working groups contain reasonable downrefs (often things such as
Informational documents that define terminology), but those downrefs
are not called out during last call, as currently required by RFC
3967, for any of various reasons... for example, the document editors
put the reference in as an Informative one, but it was decided after
last call to make the reference Normative, now triggering the RFC 3967

Do we really want to repeat the last call for that?  According to RFC
3967, we have to.  But there's no actual benefit to that, so it
becomes process purely for process' sake -- form over substance.

This draft, intended to update BCP 97 (RFC 3967), relaxes the process
slightly, still stressing the need for maturity and still strongly
recommending calling out the downrefs during last call, but allowing
the IESG to use its judgment in the end.

I think experience since RFC 3967 has shown that this is the right way
to go.  Discussion here, please, before Ben, who has kindly agreed to
AD-sponsor this, sends it out for last call.


On Tue, Aug 9, 2016 at 2:54 PM,  <> wrote:
> A new version of I-D, draft-leiba-3967upd-downref-00.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
> Name:           draft-leiba-3967upd-downref
> Revision:       00
> Title:          Updating when Standards Track Documents may Refer Normatively to Documents at a Lower Level
> Document date:  2016-08-09
> Group:          Individual Submission
> Pages:          3
> URL:  
> Status:
> Htmlized:
> Abstract:
>    RFC 3967 specifies a process for allowing normative references to
>    documents at lower maturity levels ("downrefs"), which involves
>    calling out the downref explicitly in the last call notice.  That
>    requirement has proven to be unnecessarily strict, and this document
>    updates RFC 3967, allowing the IESG more flexibility in accepting
>    downrefs in Standards Track documents.