Protocol Action: The PPP Compression Control Protocol (CCP) to Proposed Standard

[The IESG <[e-mail]>]

The IESG has approved the Internet-Draft "The PPP Compression Control
Protocol (CCP)" <draft-ietf-pppext-compression-04.txt> as a Proposed
Standard. This document is the product of the Point-to-Point Protocol
Extensions Working Group. The IESG contact persons are Frank Kastenholz
and Jeff Burgan.

The IESG also approved the publication of the following ten
Internet-Drafts as Informational RFCs:


 1. PPP Stac LZS Compression Protocol
	<draft-ietf-pppext-stacker-06.txt>
 2. PPP Hewlett-Packard Packet-by-Packet Compression (HP PPC) Protocol
	<draft-ietf-pppext-hpppc-00.txt>
 3. PPP Gandalf FZA Compression Protocol
	<draft-ietf-pppext-gandalf-00.txt>
 4. PPP Predictor Compression Protocol'
	<draft-ietf-pppext-predictor-00.txt>
 5. PPP BSD Compression Protocol
	<draft-ietf-pppext-bsd-compress-05.txt
 6. PPP Deflate Protocol
	<draft-ietf-pppext-deflate-00.txt>
 7. PPP LZS-DCP Compression Protocol (LZS-DCP)
	<draft-ietf-pppext-lzs-dcp-01.txt>
 8. PPP Magnalink Variable Resource Compression
	<draft-ietf-pppext-magnalink-01.txt>
 9. PPP for Data Compression in Data Circuit-Terminating Equipment (DCE)
	<draft-ietf-pppext-dce-compress-00.txt>
10. PPP Serial Data Transport Protocol (SDTP)
	<draft-ietf-pppext-sdtp-00.txt>


Technical Summary

   The "PPP Compression Control Protocol provides a standard method for
   negotiating compression techniques to use over a point-to-point
   connection. This is of particular to those who use low speed serial
   connections and wish to obtain high throughput.

   The Compression Control Protocol does NOT define any of the
   compression algorithms which may be used. These algorithms will be
   defined in a separate set of Informational RFCs. Many of these
   algorithms are proprietary. It was felt by the working group, and
   the area directors have concurred, that it would not be proper to
   define any one algorithm to be the standard compression algorithm.

Working Group Summary

   This protocol is the result of an effort in the PPP Working group.
   The protocol is subject to certain patent claims from the Motorola
   Corporation. The working group discussed alternate techniques that
   did not use encumbered technology but could not come to consensus on
   such a technique. Furthermore, Motorola was unwilling to provide the
   licensing agreements required by RFC 1602. A Variance to the
   requirements of RFC 1602, allowing the adoption of the CCP was
   requested by the working group and was received from the IETF, see
   RFC 1915.


Protocol Quality

   This protocol has been reviewed by Frank Kastenholz and Susan
   Thomson (RET.), Co-Internet Area Directors. There are at least 5
   known implementations of this protocol, which have demonstrated
   varying levels of interoperability. There may be others.


Special Note:

On 5 June, 1995, the IESG received the following communication from
Motorola Inc.

   Motorola, Inc. has advised the IETF that it holds two patents that it
   believes to be essential to the CCP and ECP standards, U.S. 5,245,614
   and U.S.  5,130,993, and has declared its willingness to make licenses
   to these patents available to any party under reasonable terms and
   conditions that are demonstrably free of unfair discrimination.
   Parties interested in obtaining such a license may contact:

   Mr. John A. Fisher
   Vice President and Intellectual Property Licensing Counsel
   Motorola, Inc.
   1303 E. Algonquin Road
   Schaumburg, Ill. 60196

The IESG and IETF make no statement on the validity of this claim.

See also RFC 1915.


Note to RFC Editor:

The following references need to get updated...

[1]  Should now refer to the updated RFC 1661, July 1994.

[2]  Should now refer to RFC 1700, October 1994.

[3]  Should now refer to the published RFC 1663, July 1994.

Also, the new chair's name and address should be include in the RFC.
This will replace Fred Baker's name.