RFC21 Network meeting

0021 Network meeting. V.G. Cerf. October 1969. (Format: TXT=2143 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                            V. Cerf
Request for Comments: 21                                            UCLA
                                                        October 17, 1969



At UCLA on October 10, there was a network meeting attended by:

           SDC                             UCLA

        John Kreznar                    Vint Cerf
        Dick Linde                      Steve Crocker
        Marty Bleier                    Jon Postel
        Bob Long                        Michel Elie


           UCSB

        Ron Stoughton
        Nancy O'Hara
        George Gregg



Topics discussed:

        1.  Revisions to BBN memo 1822
        
        2.  Revisions to NWG/RFC 11

        3.  Transmission of multiple control messages



1.  Changes to BBN Memo No. 1822 (underlined)
    As informally communicated by Dave Wa

    p. 11 "The IMP program can handle up to 63 active transmit links
    and 63 active receive links at a time.  If the Host attempts to
    send a message on a new link when 63 active transmit links already
    exist, a "Link Table Full" message will be sent from the IMP to
    the Host, and the message will be discarded."
    
    p. 11 "1.  Any link that is not used for a period of 26 seconds
       will have its entry automatically deleted by the IMP program."



[Cerf:  How about deleting only if the transmit link table is full?

 Crocker:  No, because there is no other way for links to be deleted
           so they would always tend to accumulate.  Furthermore,
           the table at one site may be full while another site may
           not be.]

    p. 13  "5 Regular with discard."

    This allows IMP systems to generate traffic which never actually
    reaches any Hosts since it will be discarded when it reaches the 
    top of the IMP-HOST queue in the destination Host's IMP.  The
    Network Measurement Center will make use of this feature.

    p. 13  Message type 6 is no longer assigned, and message type 10
    is really in octal so is actually type 8.  Types 9-15 are unassigned.

    p. 17   Type 10 is really type 8.

2.  Revisions to NWG/RFC 11

    This memo has been obsoleted by developments at UCLA and
    discussions with other nodes.  NWG/RFC 22 contains some of the
    major changes.  An updated version of NWG/RFC 11 is forthcoming.

3.  George Gregg of UCSB will publish NWG/RFC 23 concerning the

一覧

 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 

スポンサーリンク

screen.colorDepth

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

上に戻る