IT. Expert System.

RFC (unknown status)

Response to RFC 597: Host status. J.D. Burchfiel. December 1973. RFC603. (Format: TXT=1482 bytes) (Updates RFC597) (Updated by RFC613) (Status: UNKNOWN) (DOI: 10.17487 / RFC603)


 Network Working Group                                  J.D. Burchfiel
RFC # 603                                              BBN-TENEX
NIC # 21022                                            31 December, 1973
                   Response to RFC # 597: Host Status
    I have several questions about the November 1973 ARPANET
topographical map:
    1.  AMES is 4-connected, i.e. four network connections will go down
        if the IMP fails.  Is there some aspiration that IMPs should be
        no more than three connected?
    2.  The seven IMPS in the Washington area are arranged into a loop.
        This guarantees that local communication can take place even if
        one connection fails, and is probably a worthwhile preparation
        for area routing.  On the other hand, for example, a break
        between MIT-IPC and MIT-MAC will require them to communicate
        through a 12-hop path through Washington.  This can be remedied
        by a short (inexpensive) connection between Harvard and Lincoln
        Labs.  Is there a plan to pull the Boston area, the San
        Francisco area, and the Los Angeles area into loops like the
        Washington area?
       [ 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 ]
Burchfiel                                                       [Page 1] 


Content

Android Reference

Java basics

Java Enterprise Edition (EE)

Java Standard Edition (SE)

SQL

HTML

PHP

CSS

Java Script

MYSQL

JQUERY

VBS

REGEX

C

C++

C#

Design patterns

RFC (standard status)

RFC (proposed standard status)

RFC (draft standard status)

RFC (informational status)

RFC (experimental status)

RFC (best current practice status)

RFC (historic status)

RFC (unknown status)

IT dictionary

License.
All information of this service is derived from the free sources and is provided solely in the form of quotations. This service provides information and interfaces solely for the familiarization (not ownership) and under the "as is" condition.
Copyright 2016 © ELTASK.COM. All rights reserved.
Site is optimized for mobile devices.
Downloads: 706 / . Delta: 0.04290 с