idnits 2.17.1 draft-ietf-l2tpext-rfc2661-iana-01.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 BCP 68 4 RFC 3438 6 Title: Layer Two Tunneling Protocol (L2TP) Internet 7 Assigned Numbers Authority (IANA) Considerations 8 Update 9 Author(s): W. Townsley 10 Status: Best Current Practice 11 Date: December 2002 12 Mailbox: mark@townsley.net 13 Pages: 5 14 Characters: 9135 15 SeeAlso: BCP 68 17 I-D Tag: draft-ietf-l2tpext-rfc2661-iana-01.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3438.txt 21 This document describes updates to the Internet Assigned Numbers 22 Authority (IANA) considerations for the Layer Two Tunneling Protocol 23 (L2TP). 25 This document is a product of the Layer Two Tunneling Protocol 26 Extensions Working Group of the IETF. 28 This document specifies an Internet Best Current Practices for the 29 Internet Community, and requests discussion and suggestions for 30 improvements. Distribution of this memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.