idnits 2.17.1 draft-shimizu-ppp-mapos-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 RFC 3186 5 Title: MAPOS/PPP Tunneling mode 6 Author(s): S. Shimizu, T. Kawano, K. Murakami, E. Beier 7 Status: Informational 8 Date: December 2001 9 Mailbox: shimizu@ntt-20.ecl.net, kawano@core.ecl.net, 10 murakami@ntt-20.ecl.net, Beier@bina.de 11 Pages: 14 12 Characters: 27109 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-shimizu-ppp-mapos-01.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3186.txt 19 This document specifies tunneling configuration over MAPOS (Multiple 20 Access Protocol over SONET/SDH) networks. Using this mode, a MAPOS 21 network can provide transparent point-to-point link for PPP over 22 SONET/SDH (Packet over SONET/SDH, POS) without any additional 23 overhead. 25 This memo provides information for the Internet community. It does 26 not specify an Internet standard of any kind. Distribution of this 27 memo is unlimited. 29 This announcement is sent to the IETF list and the RFC-DIST list. 30 Requests to be added to or deleted from the IETF distribution list 31 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 32 added to or deleted from the RFC-DIST distribution list should 33 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 35 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 36 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 37 help: ways_to_get_rfcs. For example: 39 To: rfc-info@RFC-EDITOR.ORG 40 Subject: getting rfcs 42 help: ways_to_get_rfcs 44 Requests for special distribution should be addressed to either the 45 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 46 specifically noted otherwise on the RFC itself, all RFCs are for 47 unlimited distribution.echo 48 Submissions for Requests for Comments should be sent to 49 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 50 Authors, for further information.