RFC 3342: The Application Exchange (APEX) Option Party Pack, Part Deux!
In plain English — editorial summary, not part of the RFC
APEX, at its core, provides a best-effort application-layer datagram service. Options are used to alter the semantics of the core service. This memo defines various options to change the default behavior of APEX's 'relaying mesh'.
Document record
- Document ID
- RFC3342
- Published
- July 2002
- Authors
- E. Dixon; H. Franklin; J. Kint; G. Klyne; D. New; S. Pead; M. Rose; M. Schwartz
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3343The Application Exchange (APEX) Presence ServiceCurrent
May 2003
- RFC 3341The Application Exchange (APEX) Access ServiceCurrent
July 2002
- RFC 1764The PPP XNS IDP Control Protocol (XNSCP)Current
March 1995
- RFC 3340The Application Exchange CoreCurrent
July 2002
- RFC 2779Instant Messaging / Presence Protocol RequirementsCurrent
February 2000
- RFC 2377Naming Plan for Internet Directory-Enabled ApplicationsUpdated
September 1998
- RFC 2303Minimal PSTN address format in Internet MailObsoleted
March 1998
- RFC 1564DSA Metrics (OSI-DS 34 (v3))Current
January 1994
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?