RFC 3694: Threat Analysis of the Geopriv Protocol
In plain English — editorial summary, not part of the RFC
This document provides some analysis of threats against the Geopriv protocol architecture. It focuses on protocol threats, threats that result from the storage of data by entities in the architecture, and threats posed by the abuse of information yielded by Geopriv. Some security properties that meet these threats are enumerated as a reference for Geopriv requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3694
- Published
- February 2004
- Authors
- M. Danley; D. Mulligan; J. Morris; J. Peterson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 18
- Also known as
- —
- Updated by:
- RFC 6280
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3693Geopriv RequirementsUpdated
February 2004
- RFC 3690IP Telephony Requirements for Emergency Telecommunication Service (ETS)Current
February 2004
- RFC 3689General Requirements for Emergency Telecommunication Service (ETS)Current
February 2004
- RFC 3702Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol (SIP)Current
February 2004
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
- RFC 3711The Secure Real-time Transport Protocol (SRTP)Updated
March 2004
- RFC 3666Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call FlowsCurrent
January 2004
- RFC 3665Session Initiation Protocol (SIP) Basic Call Flow ExamplesCurrent
January 2004
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?