Protocol Action: The Application Exchange Core to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 05 February 2002 21:07 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19393; Tue, 5 Feb 2002 16:07:54 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id PAA29970 for ietf-123-outbound.10@ietf.org; Tue, 5 Feb 2002 15:55:02 -0500 (EST)
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 PAA29928 for <all-ietf@loki.ietf.org>; Tue, 5 Feb 2002 15:49:58 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18841; Tue, 5 Feb 2002 15:49:54 -0500 (EST)
Message-Id: <200202052049.PAA18841@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>, Internet Architecture Board <iab@isi.edu>, apexwg@lists.beepcore.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: The Application Exchange Core to Proposed Standard
Date: Tue, 05 Feb 2002 15:49:54 -0500
Sender: scoya@cnri.reston.va.us
The IESG has approved publication of the following Internet-Drafts as Proposed Standards: o The Application Exchange Core <draft-ietf-apex-core-06.txt> o The APEX Access Service <draft-ietf-apex-access-08.txt> o The APEX Option Party Pack, Part Deux! <draft-ietf-apex-party-04.txt> o The APEX Presence Service <draft-ietf-apex-presence-06.txt> These documents are the product of the Application Exchange Working Group. The IESG contact persons are Ned Freed and Patrik Faltstrom. Technical Summary This set of memos describe APEX, an extensible, asynchronous message relaying service for application layer programs, the well-known endpoints "apex=access" and "apex=presence", and a set of options used to change the default behavior of the APEX "relay mesh". APEX, at its core, provides a best-effort datagram service. Each datagram, simply termed "data", is originated and received by APEX "endpoints" -- applications that dynamically attach to the APEX "relaying mesh". The data transmitted specifies: o an originating endpoint; o an opaque content (via a URI-reference); o one or more recipient endpoints; and, o zero or more options. Options are used to alter the semantics of the the service, may occur on a per-recipient or per-data basis, and may be processed by either a single or multiple relays. Additional APEX services are provided on top of the relaying mesh; this set of documents specifies services for access control and presence information management. Working Group Summary These specifications are all products of the APEX working group Protocol Quality Ned Freed reviewed these specifications for the IESG.