Browse Prior Art Database

Internet Engineering Task Force Statements Of Boredom (SOBs) (RFC1438)

IP.com Disclosure Number: IPCOM000002266D
Original Publication Date: 1993-Apr-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 2 page(s) / 3K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Lyman Chapin: AUTHOR [+1]

Related Documents

10.17487/RFC1438: DOI

Abstract

This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). This memo provides information for the Internet community. It does not specify an Internet standard.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 64% of the total text.

Network Working Group L. Chapin Request for Comments: 1438 BBN C. Huitema INRIA 1 April 1993

Internet Engineering Task Force Statements Of Boredom (SOBs)

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.

Discussion

The current IETF process has two types of RFCs: standards track documents and other RFCs (e.g., informational, experimental, FYIs). The intent of the standards track documents is clear, and culminates in an official Internet Standard. Informational RFCs can be published on a less formal basis, subject to the reasonable constraints of the RFC Editor. Informational RFCs are not subject to peer review and carry no significance whatsoever within the IETF process.

The IETF currently has no mechanism or means of publishing documents that express its deep concern about something important, but otherwise contain absolutely no useful information whatsoever. This document creates a new subseries of RFCs, entitled, IETF Statements Of Boredom (SOBs). The SOB process is similar to that of the normal standards track. The SOB is submitted to the IAB, the IRSG, the IESG, the SOB Editor (Morpheus), and the Academie Francais for review, analysis, reproduction in triplicate, translation into ASN.1, and distribution to Internet insomniacs. However, once everyone has approved the document by falling asleep over it, the process ends and the document is discarded. The resulting vacuum is viewed as having the technical approval...

Processing...
Loading...