Skip to main content

Host Status

     <NOP>

An NCP may be up, down, pending, etc. When an NCP changes its state to UP it should send a <NOP> to each remote NCP which indicates the NCP is available. The sending NCP can then construct a vector of HOST status from the RFNMs it receives. An NCP receiving a <NOP> can update the availability of the sending NCP in its HOST status vector.

Note: This RFC was put into machine readable form for entry into the online RFC archives by Richard Ames 6/97.