Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Updating When Standards Track Documents May Refer Normatively to Documents at a Lower Level (RFC8067)

IP.com Disclosure Number: IPCOM000248978D
Original Publication Date: 2017-Jan-01
Included in the Prior Art Database: 2017-Jan-25
Document File: 6 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Leiba: AUTHOR

Abstract

[RFC3967] notes the importance of assuring that normative references from Standards Track and Best Current Practice (BCP) documents are appropriately mature, and specifies a process for allowing normative references to documents at lower maturity levels ("downrefs"). That process starts at IETF Last Call (see Section 3 of [RFC3967]):

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 44% of the total text.

Internet Engineering Task Force (IETF)                          B. Leiba Request for Comments: 8067                           Huawei Technologies BCP: 97                                                     January 2017 Updates: 3967 Category: Best Current Practice ISSN: 2070-1721

     Updating When Standards Track Documents May Refer Normatively to                        Documents at a Lower Level

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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It has been approved for publication by the Internet    Engineering Steering Group (IESG).  Further information on BCPs is    available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc8067.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Leiba                     Best Current Practice                 [Page 1]
 RFC 8067                 Document Downref Update            January 2017

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  The IESG's Responsibility with Respect to Downrefs  . . . . .   2    3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3    4.  Normative References  . . . . . . . . . . . . . . . . . . . .   3    Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   [RFC3967] notes the importance of assuring that normative references    from Standards Track and Best Current Practice (BCP) documents are    appropriatel...