RFC 4079: A Presence Architecture for the Distribution of GEOPRIV Location Objects
In plain English — editorial summary, not part of the RFC
GEOPRIV defines the concept of a 'using protocol' -- a protocol that carries GEOPRIV location objects. GEOPRIV also defines various scenarios for the distribution of location objects that require the concepts of subscriptions and asynchronous notifications. This document examines some existing IETF work on the concept of presence, shows how presence architectures map onto GEOPRIV architectures, and moreover demonstrates that tools already developed for presence could be reused to simplify the standardization and implementation of GEOPRIV. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4079
- Published
- July 2005
- Authors
- J. Peterson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4083Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)Current
May 2005
- RFC 4092Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)Obsoleted
June 2005
- RFC 4060RTP Payload Formats for European Telecommunications Standards Institute (ETSI) European Standard ES 202 050, ES 202 211, and ES 202 212 Distributed Speech Recognition EncodingCurrent
May 2005
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
- RFC 4114E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)Current
June 2005
- RFC 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current
June 2005
- RFC 4040RTP Payload Format for a 64 kbit/s Transparent CallCurrent
April 2005
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?