idnits 2.17.1 draft-ietf-l2tpext-link-07.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 3437 5 Title: Layer-Two Tunneling Protocol Extensions for PPP 6 Link Control Protocol Negotiation 7 Author(s): W. Palter, W. Townsley 8 Status: Standards Track 9 Date: December 2002 10 Mailbox: mark@townsley.net, palter.ietf@zev.net 11 Pages: 10 12 Characters: 20820 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-l2tpext-link-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3437.txt 19 This document defines extensions to the Layer Two Tunneling Protocol 20 (L2TP) for enhanced support of link-specific Point to Point Protocol 21 (PPP) options. PPP endpoints typically have direct access to the 22 common physical media connecting them and thus have detailed knowledge 23 about the media that is in use. When the L2TP is used, the two PPP 24 peers are no longer directly connected over the same physical media. 25 Instead, L2TP inserts a virtual connection over some or all of the PPP 26 connection by tunneling PPP frames over a packet switched network such 27 as IP. Under some conditions, an L2TP endpoint may need to negotiate 28 PPP Link Control Protocol (LCP) options at a location which may not 29 have access to all of the media information necessary for proper 30 participation in the LCP negotiation. This document provides a 31 mechanism for communicating desired LCP options between L2TP endpoints 32 in advance of PPP LCP negotiation at the far end of an L2TP tunnel, as 33 well as a mechanism for communicating the negotiated LCP options back 34 to where the native PPP link resides. 36 This document is a product of the Layer Two Tunneling Protocol 37 Extensions Working Group of the IETF. 39 This is now a Proposed Standard Protocol. 41 This document specifies an Internet standards track protocol for 42 the Internet community, and requests discussion and suggestions 43 for improvements. Please refer to the current edition of the 44 "Internet Official Protocol Standards" (STD 1) for the 45 standardization state and status of this protocol. Distribution 46 of this memo is unlimited. 48 This announcement is sent to the IETF list and the RFC-DIST list. 49 Requests to be added to or deleted from the IETF distribution list 50 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 51 added to or deleted from the RFC-DIST distribution list should 52 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 54 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 55 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 56 help: ways_to_get_rfcs. For example: 58 To: rfc-info@RFC-EDITOR.ORG 59 Subject: getting rfcs 61 help: ways_to_get_rfcs 63 Requests for special distribution should be addressed to either the 64 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 65 specifically noted otherwise on the RFC itself, all RFCs are for 66 unlimited distribution.echo 67 Submissions for Requests for Comments should be sent to 68 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 69 Authors, for further information.