Operation Manual

50 NetWare MultiProtocol Router for ISDN 3.1 Installation and ISDN Configuration Guide
The following RFCs are supported by NetWare MultiProtocol Router
for ISDN 3.1:
Table 2-1:
Supported RFCs
Number Title
RFC 1144 Compressing TCP/IP Headers
RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)
RFC 1334 PPP Authentication Protocols (PAP and CHAP)
RFC 1378 The PPP AppleTalk Control Protocol (ATCP)
RFC 1552 The PPP Internetwork Packet Exchange Protocol (IPXCP),
exclusively for remote node access
RFC 1553 Compressing IPX Headers Over WAN Media (CIPX)
RFC 1570 PPP LCP Extensions (incl. callback option)
RFC 1618 PPP over ISDN
RFC 1634 Novell IPX Over Various WAN Media (IPXWAN)
RFC 1661 The Point-to-Point Protocol (PPP)
RFC 1662 PPP in HDLC Framing
RFC 1717 The PPP Multilink Protocol (MP)
RFC 1877 IPCP Extensions for Name Server Addresses
Since, as of writing, standards for some of the internetworking
features provided by the NetWare MultiProtocol Router for ISDN 3.1
do not yet exist or are still being developed, the following differ-
ences to the AVM Proprietary protocol apply:
- Inactivity Timeout and Self-Learning Timeout:
As of writing, PPP does not include a method to differentiate
between logical and underlying pyhsical disconnection of an
ISDN link. Thus, when an ISDN connection is cleared due to
expiration of the Inactivity Timeout, the physical and logical
connection are cleared at the same time. This is why you should
set the Disconnect Timeout to "Same as Inactivity Timeout".
- Spoofing mechanisms:
Since all parameter negotiations are cleared when the logical
connection is disestablished, the spoofing mechanisms on the
ISDN driver level have no meaning for PPP over ISDN.
Preparin.pm6 27.05.97, 21:0850