RFC 3620: The TUNNEL Profile
In plain English — editorial summary, not part of the RFC
This memo describes a Blocks Extensible Exchange Protocol (BEEP) profile that allows a BEEP peer to serve as an application-layer proxy. It allows authorized users to access services through a firewall.
Document record
- Document ID
- RFC3620
- Published
- October 2003
- Authors
- D. New
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 18
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3767Securely Available Credentials ProtocolUpdated
June 2004
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3529Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)Updated
April 2003
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 4767The Intrusion Detection Exchange Protocol (IDXP)Current
March 2007
- RFC 7029Extensible Authentication Protocol (EAP) Mutual Cryptographic BindingCurrent
October 2013
- RFC 7170Tunnel Extensible Authentication Protocol (TEAP) Version 1Obsoleted
May 2014
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?