RFC63 Belated Network Meeting Report

0063 Belated Network Meeting Report. V.G. Cerf. July 1970. (Format: TXT=2961 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                          V. Cerf
Request for Comments #63                                       31 July 70

                     Belated Network Meeting Report

On 8 May 1970, a Network Working Group meeting was hosted at Lincoln Labs.
The topics under discussion were:

   1)   Lincoln Lab's Local Interaction Language (LIL)

   2)   Records, Messages, and Format in HOST-HOST information exchange.

   3)   Miscellaneous gripes

The first topic is thoroughly summarized in Lincoln Lab's Semi annual
Technical Summary titled "Graphics", dated May 31, 1970 (document id.
ESD-TR-70-151).

The second topic involved considerable  discussion of NWG/RFC #42 in which
it was proposed that all messages be preceded by an 8-bit type byte which
would declare the format of the message which followed.

The following decisions were reached:

   a)   Records may begin anywhere within a message.

   b)   The first 8 bits of a record are reserved for type information.

   c)   The first transmission on a connection starts a record.

Type 0 is agreed to mean that the transmission that follows consists of an
arbitrarily long record, and that no further type bytes will be present.

The notions of messages and records are independent of the flow-control
protocol.  Thus the receipt of a message does not carry any semantic
importance.  The receipt of a record, however, may initiate some interpre-
tation process.

After some discussion, the proposals in NWG/RFC #42 were permuted as follows:

   type 0 = bit string of arbitrary length follows

   type 1 = 8-bit ASCII follows

   type 2 = EBCDIC follows

   type 3 = MOD 33 TTY 7-bit ASCII




                                                                [Page 1]

Network Working Group                                         V. Cerf
Request for Comments #63                                      31 July 70


   type 4 = YOUR Local
            followed by another type byte

   type 5 = MY Local
            followed by another type byte

The praise or blame for the preceding decisions rests on the attendees at
the meeting, to wit:

E. Ancona (LL)
T. J. Barkalow (LL)
D. B. Black (Harvard)
Jack Bouknight (UI)
Howard Brodie (MAC)
Vint Cerf (UCLA)
Steve Crocker (UCLA)
Jim Curry (UTAH)
A. Evans (LL, MAC)
Robert Flegal (UTAH)
Jim Frogie (LL)
J. D. Fry (MITRE)
John Heafner (RAND)
Bob Hoffman (RAND)
Richard Kalin (LL)
William Kantrowitz (LL)
Peggy Karp (MITRE)
Abe Landsberg (SDC)
Robert Long (SDC)
James Madden (UI)
John Melvin (SRI)
Alan Nemeth (LL)
John Newkirk (Harvard)
Jon Postel (UCLA)
Tom O'Sullivan (Raytheon)
Ari Shoshani (SDC)
Joel Winett (LL)


Instead of sending NWG/RFC's to Chuck Rose at Case University, Jim Torson
will be receiving them.

       [ This RFC was put into machine readable form for entry ]
     [ into the online RFC archives by Tammy and Ofer Porat 1/97 ]




                                                                [Page 2]

一覧

 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 

スポンサーリンク

{mailto}関数 mailto: リンクの作成とメールアドレスのエンコードをする

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

上に戻る