Skip to main content

Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level
draft-kucherawy-rfc3967bis-00

Document Type Expired Internet-Draft (individual)
Author Murray Kucherawy
Last updated 2016-01-21 (Latest revision 2015-07-20)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream WG state (None)
Document shepherd (None)
IESG IESG state Expired (IESG: Dead)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Barry Leiba
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-kucherawy-rfc3967bis-00.txt

Abstract

IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification (other than specifications from other standards bodies). For example, a standards track document may not have a normative reference to an informational RFC. Exceptions to this rule are sometimes needed as the IETF uses informational RFCs to describe non-IETF standards or IETF-specific modes of use of such standards. This document clarifies and updates the procedure used in these circumstances.

Authors

Murray Kucherawy

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)