Last Call: The PPP Compression Control Protocol (CCP) to Proposed Standard
IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Mon, 21 March 1994 23:06 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16734; 21 Mar 94 18:06 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id ab16730; 21 Mar 94 18:06 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa02161; 21 Mar 94 18:06 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16718; 21 Mar 94 18:06 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16714; 21 Mar 94 18:06 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa02154; 21 Mar 94 18:06 EST
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa16707; 21 Mar 94 18:06 EST
To: IETF-Announce:;
Cc: IESG <IESG@CNRI.Reston.VA.US>
cc: ietf-ppp@merit.edu
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Last Call: The PPP Compression Control Protocol (CCP) to Proposed Standard
Date: Mon, 21 Mar 1994 18:06:05 -0500
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9403211806.aa16707@IETF.CNRI.Reston.VA.US>
The IESG has received a request from the Point-to-Point Protocol Extensions Working Group to consider "The PPP Compression Control Protocol (CCP)" <draft-ietf-pppext-compression-04.txt> for the status of Proposed Standard. Associated with the CPP protocol are the following five internet-drafts which will be considered for publication as Informational RFCs: 1. PPP Stacker LZS Compression Protocol <draft-ietf-pppext-stacker-00.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-00.txt The reason that the various algorithm documents are not on a standards track is because patents apply to these and some represent businesses of their author's companies. There can, therefore, never be multiple interoperable implementations of same. The documents are structured in this way specifically to enable businesses to persue their courses with minimum impact of their patents and claims on the standard or the process that generates it. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@cnri.reston.va.us, or ietf@cnri.reston.va.us mailing lists by April 11, 1994. IESG Secretary