The RFC Archive
 The RFC Archive   RFC 603   « Jump to any RFC number directly 
 RFC Home
Full RFC Index
Recent RFCs
RFC Standards
Best Current Practice
RFC Errata
1 April RFC



IETF RFC 603

Response to RFC 597: Host status

Last modified on Thursday, March 2nd, 2000

Permanent link to RFC 603
Search GitHub Wiki for RFC 603
Show other RFCs mentioning RFC 603







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 top


Response to RFC 597: Host status RFC TOTAL SIZE: 1482 bytes PUBLICATION DATE: Thursday, March 2nd, 2000 LEGAL RIGHTS: The IETF Trust (see BCP 78)


RFC-ARCHIVE.ORG

© RFC 603: The IETF Trust, Thursday, March 2nd, 2000
© the RFC Archive, 2024, RFC-Archive.org
Maintainer: J. Tunnissen

Privacy Statement