RFC613 Network connectivity: A response to RFC 603

0613 Network connectivity: A response to RFC 603. A.M. McKenzie. January 1974. (Format: TXT=2557 bytes) (Updates RFC0603) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                   Alex McKenzie
RFC # 613                                               BBN-NET
NIC # 21525                                             January 21, 1974


             Network connectivity:  A response to RFC #603

Network topology is a complicated political and economic question with
obvious technical overtones.  I shall not attempt, in this note, to
cover all the possible arguments which might be made, but merely to
respond directly to the points raised in RFC #603.

    1.  The important consideration in deciding whether it is good or
    bad to have a node (AMES) be four connected is not how many circuits
    are affected by a node failure; rather one should consider how well
    the network is still connected after a node failure.  For example,
    if ALL nodes in the network were four-connected I doubt that anyone
    would argue that this was bad for reliability.  The weaknesses are
    not the three-connected and four-connected nodes but rather the
    ONE-connected (Hawaii, London) and two-connected nodes.  I must
    agree with Burchfiel's implied argument that it is better to have
    two adjacent three-connected nodes than to have a four-connected
    node adjacent to a two-connected node;  unfortunately the realities
    of installing interfaces and common carrier services cause the
    Network to expand in sub-optimal ways.

    2.  "Loops" are not good per se, they appear good because the act of
    making loops increases the connectivity and thereby reduces the
    effect of multiple failures.  Adding more circuits costs ARPA money,
    both capital cost for IMP interfaces and recurring cost for the
    circuits. The network group at BBN has suggested to ARPA several
    times that "connectivity should be increased" but it was only late
    in December 1973 that we made specific suggestions for the locations
    of additional circuits.  These recommendations were not based on
    building loops (although they may have that effect) but were based
    on breaking the long chains of IMPs which have occurred as the
    Network has grown.  ARPA and NAC are now presumably in the process
    of evaluating our suggestions, and perhaps formulating other
    possibilities.





       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.            10/99 ]




McKenzie                                                        [Page 1]

一覧

 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 

スポンサーリンク

file ファイル・タイプを判定する

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

上に戻る