1.3 Overview

  • Article

The profile described in this document differs from the PPTP protocol defined in [RFC2637] as follows:

  • This profile only allows a remote system acting as a PNS to connect to PAC using PPTP. The profile does not allow a remote system to connect to the PAC over a PPP link, such as a dial-up link. For more information, see section 3.2.5.3.

  • The profile does not support Start Control Connection Initiation Request Collision avoidance, as described in [RFC2637] section 3.1.3. For more information, see section 3.1.5.1.1.

  • The profile provides limited flow-control and congestion-control behavior. The profile does not allow adaptive adjustment of time-outs as specified in [RFC2637] section 4.4. For more information, see section 3.1.2.

  • The profile handles out-of-sequence packets as described in section 3.1.5.8, which is different from the definition for this process as specified in [RFC2637] section 4.3. For more information, see section 3.1.5.8.

  • The profile does not implement the sliding window protocol described in [RFC2637] section 4.2. For more information, see section 3.1.5.7. Because the sliding window protocol is not supported, the profile ignores the values of the Packet Recv. Window Size field from the peer.

  • The profile specifies a different timeout value as described in section 3.1.2, within which the control connection has to be in the established state as specified in [RFC2637] section 3.1.4.

  • The profile does not support any of the Result Code field values for the Call-Disconnect–Notify message as specified in [RFC2637] section 2.13. For the same reason, this profile does not support specifying the value "General Error" for the Result Code and passing the general error information in the Error Code field. This profile defines a new Result Code value of "0" as specified in section 3.2.5.5.