Item Subject: cc:Mail Text
     For those asking, there is a write-up on RAFCP in the General Release
     5.0 MPE/iX Communicator on pp. 7-22 and 7-23.
 
     Front-end DTCs:  72MX  16MX  TEB(Telnet Express Box)  16RX
 
     Remote DTCs:  72MX  16MX  16RX  DTC16  DTC48(w/memory expansion)
 
     (Note:  The 16RX is NOT managed by OVDTCMGR.  It is managed by
              DTC 16RX Manager, which runs on HP-UX)
 
 
     The remote DTC encapsulates the AFCP packets under UDP/IP and sends
     these packets to the Front-end DTC.  The Front-end DTC deencapsulates
     these packets and sends AFCP packets to the HP3000.  The reverse
     happens when data is going from the HP3000 to the end-user.
 
     Some of the following have already been mentioned in previous posts,
     but here are some points that IMO need to be understood before making
     the decision to go to RAFCP:
 
 
     1.  The Front-end DTC and the Remote DTC are managed by TWO DIFFERENT
                OVDTCMGRs or by the DTC 16RX Manager(16RX's only).  RAFCP
                is a data path solution for routed networks.  It is NOT a
                routable management solution.  DTC 16RX Manager provides a
                routable management solution.  Therefore, DTC 16RX aside,
                you need an OVDTCMGR PC at each location for which you have
                a DTC in an RFACP environment.
 
     2.  Front-end DTCs are not dedicated to RAFCP.  They can be used as
                regular DTCs at the same time.  There have been tests in
                which a Front-end DTC has handled more than 300 active
                connections.
 
     3.  RAFCP requires the existance and use of a Domain Name Server.
 
 
     Hope this helps.
 
     Jon Broz
     HP Cleveland
     (The Indians are 10-1 in their last 11 games)
     ------------------------------------------------------------------