RFC 3620 on The TUNNEL Profile
rfc-editor@rfc-editor.org Tue, 21 October 2003 23:44 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19366 for <ietf-announce-web-archive@odin.ietf.org>; Tue, 21 Oct 2003 19:44:41 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AC5yr-0006wl-Vq for ietf-announce-list@asgard.ietf.org; Tue, 21 Oct 2003 19:32:01 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AC5Jf-0006sR-5f for all-ietf@asgard.ietf.org; Tue, 21 Oct 2003 18:49:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16264 for <all-ietf@ietf.org>; Tue, 21 Oct 2003 18:49:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC5Jc-000401-00 for all-ietf@ietf.org; Tue, 21 Oct 2003 18:49:24 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AC5Jc-0003zy-00 for all-ietf@ietf.org; Tue, 21 Oct 2003 18:49:24 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id h9LMnMf02847; Tue, 21 Oct 2003 15:49:22 -0700 (PDT)
Message-Id: <200310212249.h9LMnMf02847@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3620 on The TUNNEL Profile
Cc: rfc-editor@rfc-editor.org, idwg-public@zurich.ibm.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 21 Oct 2003 15:49:22 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3620 Title: The TUNNEL Profile Author(s): D. New Status: Standards Track Date: October 2003 Mailbox: dnew@san.rr.com Pages: 18 Characters: 35365 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idwg-beep-tunnel-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3620.txt 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. This document is a product of the Intrusion Detection Exchange Format Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3620 on The TUNNEL Profile rfc-editor