Browse Prior Art Database

Variance for The PPP Connection Control Protocol and The PPP Encryption Control Protocol (RFC1915)

IP.com Disclosure Number: IPCOM000004157D
Original Publication Date: 1996-Feb-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 6 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

F. Kastenholz: AUTHOR

Abstract

Status of this Memo

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 22% of the total text.

Network Working Group F. Kastenholz

Request for Comments: 1915 FTP Software, Inc.

BCP: 3 February 1996

Category: Best Current Practice

Variance for

The PPP Connection Control Protocol

and

The PPP Encryption Control Protocol

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Table of Contents

1. Variance ............................................. 1

1.1 The Problem ......................................... 1

1.1.1 History ........................................... 1

1.1.2 Other Attempted Solutions ......................... 2

1.2 Variance to Procedures in RFC 1602 .................. 2

1.3 The Solution ........................................ 3

1.4 Perceived Benefits .................................. 3

1.5 Perceived Risks ..................................... 3

Security Considerations ................................. 3

Author's Address ........................................ 3

2. Appendix A -- Most Recent Communication from Motorola. 4

3. APPENDIX B -- Relevant Section of RFC 1602 ........... 5

1. Variance

1.1. The Problem

1.1.1. History

The PPP Working group has developed two protocols, one to control

compression on PPP links; the Compression Control Protocol (CCP),

documented in draft-ietf-pppext-compression-04.txt. The second is the

Encryption Control Protocol (ECP), used to control encryption on

serial links, documented in draft-ietf-pppext-encryption-03.txt.

During the development of these protocols, the Motorola Corporation

informed the IETF that they may infringe on certain patents held by

Motorola, specificlally U.S. patents 5,245,614 and 5,130,993.

After development of the protocols was completed, they were submitted

to the IESG for standardization. At this point, because of the

outstanding patent claims, their progress was halted. Per the

procedures of RFC 1602, the IESG Secretariat attempted to gain the

licenses required by RFC 1602. In particular, per section 5.6 of RFC

1602, an attempt was made to acquire a form of the license and make

it publically available via the Internet.

Motorola would prefer to provide a general statement indicating that

licenses will be made available "to any party under reasonable terms

and conditions that are demonstrably free of unfair discrimination."

1.1.2. Other Attempted Solutions

An attempt was made to have the PPP working group develop revised

versions of CCP and ECP that would not infringe on the patents. While

technically possible, the proposed technical changes are viewed by

some members of the working group as much less technicall...