[rfc-dist] RFC 3817 on Layer 2 Tunneling Protocol (L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Jun 21 12:08:06 PDT 2004


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


        RFC 3817

        Title:      Layer 2 Tunneling Protocol (L2TP) Active Discovery
                    Relay for PPP over Ethernet (PPPoE)
        Author(s):  W. Townsley, R. da Silva
        Status:     Informational
        Date:       June 2004
        Mailbox:    mark at townsley.net, rdasilva at va.rr.com
        Pages:      17
        Characters: 37765
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-dasilva-l2tp-relaysvc-08.txt

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


The Point-to-Point Protocol (PPP) provides a standard method for
transporting multi-protocol datagrams over point-to-point links.
Layer Two Tunneling Protocol (L2TP), facilitates the tunneling of PPP
packets across an intervening packet-switched network.  And yet a
third protocol, PPP over Ethernet (PPPoE) describes how to build PPP
sessions and to encapsulate PPP packets over Ethernet.

L2TP Active Discovery Relay for PPPoE describes a method to relay
Active Discovery and Service Selection functionality from PPPoE over
the reliable control channel within L2TP.  Two new L2TP control
message types and associated PPPoE-specific Attribute Value Pairs
(AVPs) for L2TP are defined.  This relay mechanism provides enhanced
integration of a specific feature in the PPPoE tunneling protocol
with L2TP.

This document is a product of the Layer Two Tunneling Protocol
Extensions Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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

        To: rfc-info at 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 at 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 at 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.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list