RFC 3620 · PROPOSED STANDARD · 2003
MON · 27 JUL 2026
The TUNNEL Profile
Overview
RFC 3620, “The TUNNEL Profile”, is a Proposed Standard document published in October 2003 by D. New. It has since been updated by RFC 8553. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 3620 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2003
- RFC 3619 Extreme Networks' Ethernet Automatic Protection Switching Version 1
- RFC 3621 Power Ethernet MIB
- RFC 3618 Multicast Source Discovery Protocol
- RFC 3617 Uniform Resource Identifier Scheme and Applicability Statement for the Trivial File Transfer Protocol
- RFC 3623 Graceful OSPF Restart
- RFC 3616 A Uniform Resource Name Namespace for Foundation for Intelligent Physical Agents
- RFC 3624 The Media Gateway Control Protocol Bulk Audit Package
- RFC 3615 A Uniform Resource Name Namespace for SWIFT Financial Messaging