RFC305 - Unknown Host Numbers

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group Ralph Alter

RFC#305 BBN

NIC #9078 23 February 1972

UNKNOWN HOST NUMBERS

--------------------

In response to a recent minor flurry of confusion, it seems worth

announcing publicly the fact that new IMPs are tested (almost

always) on the ARPA Net here at BBN before delivery to the intended

site. Accordingly, sites should not be surprised to receive RFCs

or at least RSTs from IMPs or Hosts they thought didn't exist, or

at least did not exist yet.

Occasionally, IMPs of some given configuration are tested in a

mode where they announce their IMP number as different from what

it will be when finally installed. A variety of reasons may create

sUCh a situation. The latest such occurrence is that a TIP, to be

installed shortly at ETAC with IMP number 20 (replacing the 316

IMP now at ETAC which is number 20) was recently tested here with

McClellan's IMP number (22). (It couldn't be tested with its own

number since the 316 IMP currently at ETAC is using that number.)

The result was RSTs from the TIP (Host 3) at IMP 22 - which is

network address 150 (226 octal or 96 hex).

One site asked if their Host tables needed updating. The answer

is _NO_. We fully eXPect IMPs tested under these circumstances to be

ignored or CLS'd by some Hosts. We suggest that Host tables (where

they are thought to be necessary) be modified only in response to

official notification from BBN via either an RFCor an update to

Appendix A of BBN Report #1822.

RA/jm

[ This RFCwas put into machine readable form for entry ]

[ into the online RFCarchives by BBN Corp. under the ]

[ direction of Alex McKenzie. 12/96 ]

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
 
 
© 2005- 王朝網路 版權所有 導航