RFC1438 Internet Engineering Task Force Statements Of Boredom (SOBs)

1438 Internet Engineering Task Force Statements Of Boredom (SOBs). A.Lyman Chapin, C. Huitema. April 1 1993. (Format: TXT=3044 bytes) (Status: INFORMATIONAL)

日本語訳
RFC一覧

参照

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 of the IETF, but it is not, and cannot become,
   an official Internet Standard.











Chapin & Huitema                                                [Page 1]

RFC 1438                       IETF SOBs                    1 April 1993


References

   [1] Internet Activities Board, "The Internet Standards Process", RFC
       1310, IAB, March 1992.

   [2] Postel, J., Editor, "IAB OFFICIAL PROTOCOL STANDARDS", RFC 1410,
       IAB, March 1993.

Security Considerations

   Security issues are not discussed in this memo, but then again, no
   other issues of any importance are discussed in this memo either.

Authors' Addresses

   A. Lyman Chapin
   Bolt, Beranek & Newman
   Mail Stop 20/5b
   150 Cambridge Park Drive
   Cambridge, MA 02140
   USA

   Phone: 1 617 873 3133
   EMail: Lyman@BBN.COM


   Christian Huitema
   INRIA, Sophia-Antipolis
   2004 Route des Lucioles
   BP 109
   F-06561 Valbonne Cedex
   France

   Phone: +33 93 65 77 15
   EMail: Christian.Huitema@MIRSA.INRIA.FR
















一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

文字列の部分一致検索を行う方法

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る