Normative References in RFCs from Open Source
draft-atlas-external-normref-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alia Atlas , Eliot Lear , Joel M. Halpern , Heather Flanagan , Jeff Tantsura | ||
| Last updated | 2018-05-02 (Latest revision 2017-10-29) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IETF procedures generally require that a standards track RFC may not have a normative reference to a non standards track specification except those from other standards bodies. This document creates an External Specification registry, similar to the DownRef registry that has been created based on [RFC3967] and permits normative references to community accepted external specifications.
Authors
Alia Atlas
Eliot Lear
Joel M. Halpern
Heather Flanagan
Jeff Tantsura
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)