Independent Submissions to the RFC Editor
draft-klensin-rfc-independent-05

Document Type Expired Internet-Draft (individual)
Last updated 2006-12-22
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
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-klensin-rfc-independent-05.txt

Abstract

There is a long-term tradition in the Internet community, predating the IETF by many years, of use of the RFC series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "independent submissions", serve a number of important functions for the Internet community, both inside and outside of the community of active IETF participants. This document discusses the independent submission model and some reasons why it is important. It then describes editorial and processing norms that can be used for independent submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher.

Authors

John Klensin (john-ietf@jck.com)

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