IETF RFC 3620
[ACTIVE]
The TUNNEL Profile
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 18
- 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.
- Publication Date
- 2003-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3620- Link
- https://doi.org/10.17487/RFC3620
- Author(s)
- Darren New
- Keyword(s)
- Tunnel, BEEP, Firewalls
Latest version of IETF RFC 3620
Document Versions — IETF RFC 3620
-
▶ IETF RFC 3620 (2003-10-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2373 [Superseded*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2782 [Active*]
- IETF RFC 3080 [Active*]
- IETF RFC 3081 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3620.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3620, The TUNNEL Profile. Available at https://doi.org/10.17487/RFC3620
Snippet:
IETF RFC 3620, The TUNNEL Profile. Available at https://doi.org/10.17487/RFC3620
HTML (ISO 690 compliant)
Preview:
IETF RFC 3620, The TUNNEL Profile. Available at https://doi.org/10.17487/RFC3620
Snippet:
<span class="citation"><cite>IETF RFC 3620</cite>, The TUNNEL Profile. Available at <a href="https://doi.org/10.17487/RFC3620" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3620</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc3620">IETF RFC 3620</cite>, The TUNNEL Profile <span class="doi">10.17487/RFC3620</span> </li>
Referenced By
- IETF RFC 8553 [Active*]