idnits 2.17.1 draft-ietf-l2tpext-ppp-discinfo-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 3145 5 Title: L2TP Disconnect Cause Information 6 Author(s): R. Verma, M. Verma, J. Carlson 7 Status: Standards Track 8 Date: July 2001 9 Mailbox: rverma@dc.com, Madhvi_Verma@3com.com, 10 james.d.carlson@sun.com 11 Pages: 10 12 Characters: 17421 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-l2tpext-ppp-discinfo-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3145.txt 19 This document provides an extension to the Layer 2 Tunneling Protocol 20 ("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP) 21 sessions. L2TP lacks a mechanism for a host to provide PPP-related 22 disconnect cause information to another host. This information, 23 provided by the extension described in this document, can be useful 24 for accounting and debugging purposes. 26 This document is a product of the Layer Two Tunneling Protocol 27 Extensions Working Group of the IETF. 29 This is now a Proposed Standard Protocol. 31 This document provides an extension to the Layer 2 Tunneling Protocol 32 ("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP) 33 sessions. L2TP lacks a mechanism for a host to provide PPP-related 34 disconnect cause information to another host. This information, 35 provided by the extension described in this document, can be useful 36 for accounting and debugging purposes. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.