RFC 2804: IETF Policy on Wiretapping
In plain English — editorial summary, not part of the RFC
This document describes the position that the Internet Engineering Task Force (IETF) has taken regarding the inclusion into IETF standards-track documents of functionality designed to facilitate wiretapping. This memo explains what the IETF thinks the question means, why its answer is "no", and what that answer means. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2804
- Published
- May 2000
- Authors
- IAB; IESG
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2777Publicly Verifiable Nomcom Random SelectionObsoleted
February 2000
- RFC 3026Liaison to IETF/ISOC on ENUMCurrent
January 2001
- RFC 2860Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityCurrent
June 2000
- RFC 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 2000
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 3005IETF Discussion List CharterObsoleted
November 2000
- RFC 31133GPP-IETF Standardization CollaborationCurrent
June 2001
- RFC 31313GPP2-IETF Standardization CollaborationCurrent
June 2001
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?