RFC 3341 on The Application Exchange (APEX) Access Service
rfc-editor@rfc-editor.org Wed, 24 July 2002 23:46 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06197; Wed, 24 Jul 2002 19:46:32 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA07323 for ietf-123-outbound.10@ietf.org; Wed, 24 Jul 2002 19:45:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA07085 for <all-ietf@loki.ietf.org>; Wed, 24 Jul 2002 19:21:08 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05458 for <all-ietf@ietf.org>; Wed, 24 Jul 2002 19:20:02 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g6ONL4E21164; Wed, 24 Jul 2002 16:21:05 -0700 (PDT)
Message-Id: <200207242321.g6ONL4E21164@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3341 on The Application Exchange (APEX) Access Service
Cc: rfc-editor@rfc-editor.org, apexwg@lists.beepcore.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 24 Jul 2002 16:21:04 -0700
Sender: rfc-ed@ISI.EDU
A new Request for Comments is now available in online RFC libraries.
RFC 3341
Title: The Application Exchange (APEX) Access Service
Author(s): M. Rose, G. Klyne, D. Crocker
Status: Standards Track
Date: July 2002
Mailbox: mrose@dbc.mtview.ca.us,
Graham.Klyne@MIMEsweeper.com,
dcrocker@brandenburg.com
Pages: 24
Characters: 46675
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-apex-access-08.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3341.txt
This memo describes the Application Exchange (APEX) access service,
addressed as the well-known endpoint "apex=access". The access
service is used to control use of both the APEX "relaying mesh" and
other APEX services.
This document is a product of the Application Exchange 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.