Browse Prior Art Database

PPP LCP Extensions (RFC1570)

IP.com Disclosure Number: IPCOM000002404D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2019-Feb-13
Document File: 20 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Simpson: AUTHOR

Related Documents

10.17487/RFC1570: DOI

Abstract

The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 10% of the total text.

Network Working Group W. Simpson, Editor Request for Comments: 1570 Daydreamer Updates: 1548 January 1994 Category: Standards Track

PPP LCP Extensions

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Abstract

The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection. This document defines several additional LCP features which have been suggested over the past few years.

This document is the product of the Point-to-Point Protocol Working Group of the Internet Engineering Task Force (IETF). Comments should be submitted to the ietf-ppp@ucdavis.edu mailing list.

Table of Contents

1. Additional LCP Packets ................................ 1 1.1 Identification .................................. 1 1.2 Time-Remaining .................................. 3 2. Additional LCP Configuration Options .................. 6 2.1 FCS-Alternatives ................................ 6 2.1.1 LCP considerations .............................. 7 2.1.2 Null FCS ........................................ 8 2.2 Self-Describing-Padding ......................... 9 2.3 Callback ........................................ 11 2.4 Compound-Frames ................................. 12 2.4.1 LCP considerations .............................. 14 APPENDICES ................................................... 15 A. Fast Frame Check Sequence (FCS) Implementation ........ 15 A.1 32-bit FCS Computation Method ................... 15 SECURITY CONSIDERATIONS ...................................... 17 REFERENCES ................................................... 17 ACKNOWLEDGEMENTS ............................................. 18 CHAIR’S ADDRESS .............................................. 18 EDITOR’S ADDRESS ............................................. 18

Simpson [Page i]

RFC 1570 PPP LCP extensions January 1994

1. Additional LCP Packets

The Packet format and basic facilities are already defined for LCP [1].

Up-to-date values of the LCP Code field are specified in the most recent "Assigned Numbers" RFC [2]. This specification concerns the following values:

12 Identification 13 Time-Remaining

1.1. Identification

Description

This Code provides a method for an implementation to identify itself to its peer. This Code might be used for many diverse purposes, such as link troubleshooting, license enforcement, etc.

Identification is a Link Maintenance packet. Identification packets MAY be sent at any time, including before LCP has reached the Opened state.

The sender transmits a LCP packet with the Code fi...

Processing...
Loading...