idnits 2.17.1 draft-ietf-pppext-rfc2878bis-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3518 5 Title: Point-to-Point Protocol (PPP) Bridging Control 6 Protocol (BCP) 7 Author(s): M. Higashiyama, F. Baker, T. Liao 8 Status: Standards Track 9 Date: April 2003 10 Mailbox: Mitsuru.Higashiyama@yy.anritsu.co.jp, 11 fred@cisco.com, tawei@cisco.com 12 Pages: 40 13 Characters: 82102 14 Obsoletes: 2878 16 I-D Tag: draft-ietf-pppext-rfc2878bis-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3518.txt 20 The Point-to-Point Protocol (PPP) provides a standard method for 21 transporting multi-protocol datagrams over point-to-point links. PPP 22 defines an extensible Link Control Protocol (LCP) and proposes a 23 family of Network Control Protocols (NCP) for establishing and 24 configuring different network-layer protocols. 26 This document defines the NCP for establishing and configuring Remote 27 Bridging for PPP links. 29 This document obsoletes RFC 2878, which was based on the IEEE 30 802.1D-1993 MAC Bridge. This document extends that specification 31 by improving support for bridge control packets. 33 This document is a product of the Point-to-Point Protocol Extensions 34 Working Group of the IETF. 36 This is now a Proposed Standard Protocol. 38 This document specifies an Internet standards track protocol for 39 the Internet community, and requests discussion and suggestions 40 for improvements. Please refer to the current edition of the 41 "Internet Official Protocol Standards" (STD 1) for the 42 standardization state and status of this protocol. Distribution 43 of this memo is unlimited. 45 This announcement is sent to the IETF list and the RFC-DIST list. 46 Requests to be added to or deleted from the IETF distribution list 47 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 48 added to or deleted from the RFC-DIST distribution list should 49 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 51 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 52 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 53 help: ways_to_get_rfcs. For example: 55 To: rfc-info@RFC-EDITOR.ORG 56 Subject: getting rfcs 58 help: ways_to_get_rfcs 60 Requests for special distribution should be addressed to either the 61 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 62 specifically noted otherwise on the RFC itself, all RFCs are for 63 unlimited distribution.echo 64 Submissions for Requests for Comments should be sent to 65 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 66 Authors, for further information.