RFC 2637:Point-to-Point Tunneling Protocol (PPTP)
RFC-Ref

vendor


Click on the red underlined text to get to the source

... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Vendor String (64 octets) + | | ...
... 0. Vendor Name A 64 octet field containing a vendor ...
... Vendor Name A 64 octet field containing a vendor specific string describing the type of PAC ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Vendor String (64 octets) + | | ...
... 0. Vendor Name A 64 octet field containing a vendor ...
... Vendor Name A 64 octet field containing a vendor specific string describing the type of PAC ...
... Physical Channel ID This field is set by the PAC in a vendor- specific manner to the physical channel ...
... Physical Channel ID This field is set by the PAC in a vendor- specific manner to the number of the physical channel ...
... Call Statistics This field is an ASCII string containing vendor-specific call statistics that can be logged for diagnostic purposes. If the length of the string is less than 128, the ...
... 6 (PAC-Error) - A generic vendor-specific error occurred in the PAC ...


... PPTP requires that a time-out be used to recover from dropped data or acknowledgment packets. The exact implementation of the time-out is vendor-specific. It is suggested that an adaptive time-out be implemented with backoff for congestion control. The time-out mechanism proposed here has the following ...
... throughput. To reduce packet processing overhead, vendors may choose not to recompute the adaptive time-out for every received acknowledgment. The result of this overhead ...



Google
Web
RFC-Ref