RFC 1661

RFC 1661
Title	RFC 1661
Author	W. Simpson
Date	July 1994
Status	Proposed Standard
Series	Request for Comments
Number	1661
Pages	29

RFC 1661

RFC 1661 is the Request for Comments document that specifies the Point-to-Point Protocol (PPP) for use over serial links. It defines a data link layer protocol used to encapsulate network layer protocol information between two nodes, establishing connections, negotiating parameters, and supporting authentication and compression. The specification influenced networking implementations in operating systems and equipment from vendors across the Internet and telecommunications industries.

Overview

RFC 1661 presents the Point-to-Point Protocol, describing frame formats, control fields, and state machines used to manage link establishment and teardown. It situates PPP among protocols standardized by bodies such as the Internet Engineering Task Force, Internet Architecture Board, and aligns with related efforts like standards from the International Organization for Standardization and the Institute of Electrical and Electronics Engineers. The document enumerates features relevant to telecommunications providers, hardware manufacturers such as Cisco Systems, Juniper Networks, and software projects including BSD derivatives, Linux, and Microsoft Windows NT.

Background and Purpose

RFC 1661 was developed to replace earlier serial encapsulation methods used in implementations influenced by projects at Bolt, Beranek and Newman, University of California, Berkeley research, and commercial dial-up networks run by companies such as AT&T and MCI Communications. The purpose was to provide a flexible, extensible link-layer protocol suitable for point-to-point links in deployments operated by entities like Verizon Communications, British Telecom, and academic networks including ARPANET successors. The specification addresses needs identified by network engine vendors including Sun Microsystems and standards contributors from organizations like the Internet Society.

Protocol Specification

The protocol section defines PPP frame fields including the Flag, Address, Control, Protocol, Information, and Frame Check Sequence, along with procedures for byte stuffing and bit-oriented framing used in implementations by vendors such as NCR Corporation and IBM. It details the Link Control Protocol (LCP) state machine and options negotiation, citing interoperability concerns familiar to engineers from Digital Equipment Corporation and groups like the IETF Routing Area Working Group. RFC 1661 enumerates supported network control protocols such as the Internet Protocol described in documents by Vint Cerf and Bob Kahn contributors, and names extensions for protocol multiplexing used in network stacks developed at MIT and Carnegie Mellon University.

Configuration and Implementation

Implementers are guided through configuration options for authentication schemes and compression algorithms with references to methods adopted by vendors like Nortel Networks and 3Com. The document’s applicability influenced configuration utilities in operating systems from Apple Computer and IBM PC compatibles, and informed driver development in projects such as NetBSD, FreeBSD, and OpenBSD. The implementation guidance covers integration with higher-layer protocols standardized by committees including the IETF PPP Working Group and deployment scenarios in service provider networks run by Sprint Corporation and regional carriers.

Security Considerations

RFC 1661 includes authentication mechanisms intended to be used with authentication protocols later detailed in companion documents and utilized in authentication infrastructures like those operated by RADIUS servers in deployments managed by Cisco Systems and Microsoft. The security section warns about weak authentication choices and references stronger authentication approaches promoted by security researchers at MITRE Corporation and institutions such as SANS Institute. It also notes potential threats observed in public networks and commercial access services provided by firms such as WorldCom and suggests careful operator practices consistent with advisories from agencies like National Institute of Standards and Technology.

Interoperability and Compatibility

The specification emphasizes backward compatibility with existing encapsulation schemes and mentions test practices adopted in interoperability events organized by bodies like the IETF and manufacturers including Lucent Technologies and Motorola. PPP’s modular design enabled compatibility layers for network protocols developed at Bell Labs and integration into networking equipment from companies such as Alcatel-Lucent and Ericsson. The document thereby facilitated cross-vendor interoperability in enterprise environments managed by organizations including IBM and in academic networks at institutions like Stanford University and University of California, Los Angeles.

Historical Impact and Adoption

RFC 1661 played a central role in standardizing dial-up Internet access during the 1990s, shaping implementations in consumer operating systems by Microsoft Corporation and networking equipment from Cisco Systems and 3Com. It influenced subsequent standards and extensions worked on by contributors from Sun Microsystems, Bellcore, and the Internet Engineering Task Force community. The protocol’s legacy is evident in its use in remote access services, virtual private network technologies, and embedded systems developed by firms such as Siemens and Texas Instruments, and in education and research at institutions like MIT, Harvard University, and University of Cambridge.

Category:Internet protocols