Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level
draft-leiba-3967upd-downref-03

[Ballot comment]
Should there be any recommendation on where IESG should record that a particular DownRef was not Ladt Called, but is considered "safe"? E.g. using a datatracker comment, IESG telechat meeting notes.

[Ballot comment]
I do think that our discussion about ensuring that downrefs are called out at Last Call time, whether or not they're in the downref registry, is headed in the right direction.

[Ballot comment]
I support this change because delaying a doc to repeat the last call often doesn't make sense. However, I guess it would be easy to have tooling support that would automatically add a list of downrefs to the last call text (given it's already in the nits check)...?

[Ballot comment]
I support this change because delaying the doc to repeat the last call often doesn't make sense. However, I guess it would be easy to have tooling support that would automatically add a list of downrefs to the last call text (given it's already in the nits)...?

[Ballot comment]
Should there be any recommendation on where IESG should record that a particular DownRef was not Ladt Called, but is considered "safe"? E.g. using a datatracker comment.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-leiba-3967upd-downref-00.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: ben@nostrum.com, draft-leiba-3967upd-downref@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Updating when Standards Track Documents may Refer Normatively to Documents at a Lower Level) to Best Current Practice


The IESG has received a request from an individual submitter to consider
the following document:
- 'Updating when Standards Track Documents may Refer Normatively to
  Documents at a Lower Level'
  as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-15. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-leiba-3967upd-downref/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-leiba-3967upd-downref/ballot/


No IPR declarations have been submitted directly on this I-D.