RFC 3341: The Application Exchange (APEX) Access Service
In plain English — editorial summary, not part of the RFC
This memo describes the 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.
Document record
- Document ID
- RFC3341
- Published
- July 2002
- Authors
- M. Rose; G. Klyne; D. Crocker
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3342The Application Exchange (APEX) Option Party Pack, Part Deux!Current
July 2002
- RFC 3343The Application Exchange (APEX) Presence ServiceCurrent
May 2003
- RFC 3340The Application Exchange CoreCurrent
July 2002
- RFC 9460Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)Current
November 2023
- RFC 3339Date and Time on the Internet: TimestampsUpdated
July 2002
- RFC 3354Internet Open Trading Protocol Version 2 RequirementsCurrent
August 2002
- RFC 3375Generic Registry-Registrar Protocol RequirementsCurrent
September 2002
- RFC 3377Lightweight Directory Access Protocol (v3): Technical SpecificationObsoleted
September 2002
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?