RFC 3518 on Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.


        RFC 3518

        Title:      Point-to-Point Protocol (PPP) Bridging Control
                    Protocol (BCP)
        Author(s):  M. Higashiyama, F. Baker, T. Liao
        Status:     Standards Track
        Date:       April 2003
        Mailbox:    Mitsuru.Higashiyama@yy.anritsu.co.jp,
                    fred@cisco.com, tawei@cisco.com
        Pages:      40
        Characters: 82102
        Obsoletes:  2878

        I-D Tag:    draft-ietf-pppext-rfc2878bis-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3518.txt


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) and proposes a
family of Network Control Protocols (NCP) for establishing and
configuring different network-layer protocols.

This document defines the NCP for establishing and configuring Remote
Bridging for PPP links.

This document obsoletes RFC 2878, which was based on the IEEE
802.1D-1993 MAC Bridge.  This document extends that specification
by improving support for bridge control packets.

This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
<ftp://ftp.isi.edu/in-notes/rfc3518.txt>

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux