RFC 2107: Ascend Tunnel Management Protocol - ATMP
In plain English — editorial summary, not part of the RFC
This document specifies a generic tunnel management protocol that allows remote dial-in users to access their home network as if they were directly attached to the home network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2107
- Published
- February 1997
- Authors
- K. Hamzeh
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2881Network Access Server Requirements Next Generation (NASREQNG) NAS ModelCurrent
July 2000
- RFC 2139RADIUS AccountingObsoleted
April 1997
- RFC 2015MIME Security with Pretty Good Privacy (PGP)Updated
October 1996
- RFC 1948Defending Against Sequence Number AttacksObsoleted
May 1996
- RFC 2286Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128Current
February 1998
- RFC 2315PKCS #7: Cryptographic Message Syntax Version 1.5Current
March 1998
- RFC 1810Report on MD5 PerformanceCurrent
June 1995
- RFC 2808The SecurID(r) SASL MechanismCurrent
April 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?