• 软件测试技术
  • 软件测试博客
  • 软件测试视频
  • 开源软件测试技术
  • 软件测试论坛
  • 软件测试沙龙
  • 软件测试资料下载
  • 软件测试杂志
  • 软件测试人才招聘
    暂时没有公告

字号: | 推荐给好友 上一篇 | 下一篇

RFC613 - Network connectivity: A response to RFC603

发布: 2007-6-23 14:09 | 作者:   | 来源:   | 查看: 13次 | 进入软件测试论坛讨论

领测软件测试网

   
  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 RFCwas put into machine readable form for entry ]
[ into the online RFCarchives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]

文章来源于领测软件测试网 https://www.ltesting.net/


关于领测软件测试网 | 领测软件测试网合作伙伴 | 广告服务 | 投稿指南 | 联系我们 | 网站地图 | 友情链接
版权所有(C) 2003-2010 TestAge(领测软件测试网)|领测国际科技(北京)有限公司|软件测试工程师培训网 All Rights Reserved
北京市海淀区中关村南大街9号北京理工科技大厦1402室 京ICP备2023014753号-2
技术支持和业务联系:info@testage.com.cn 电话:010-51297073

软件测试 | 领测国际ISTQBISTQB官网TMMiTMMi认证国际软件测试工程师认证领测软件测试网