idnits 2.17.1 draft-ietf-l2tpext-atmext-04.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 3301 5 Title: Layer Two Tunnelling Protocol (L2TP): 6 ATM access network extensions 7 Author(s): Y. T'Joens, P. Crivellari, B. Sales 8 Status: Standards Track 9 Date: June 2002 10 Mailbox: yves.tjoens@alcatel.be, 11 paolo.crivellari@alcatel.be, 12 bernard.sales@alcatel.be 13 Pages: 19 14 Characters: 42756 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-l2tpext-atmext-04.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3301.txt 21 This document augments the procedures described in RFC 2661 to further 22 support ATM SVC (Switched Virtual Circuits) or PVC (Permanent Virtual 23 Circuits) based access networks. L2TP (Layer 2 Tunneling Protocol) 24 specifies a protocol for tunnelling PPP packets over packet based 25 networks and over IP networks in particular. L2TP supports remote 26 access by ISDN and PSTN networks. The extensions defined within this 27 document allow for asymmetric bi-directional call establishment and 28 service selection in the ATM access network. 30 This document is a product of the Layer Two Tunneling Protocol 31 Extensions Working Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.