RFC 2084: Considerations for Web Transaction Security
In plain English — editorial summary, not part of the RFC
This document specifies the requirements for the provision of security services to the HyperText Transport Protocol. These services include confidentiality, integrity, user authentication, and authentication of servers/services, including proxied or gatewayed services. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2084
- Published
- January 1997
- Authors
- G. Bossert; S. Cooper; W. Drummond
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2070Internationalization of the Hypertext Markup LanguageObsoleted
January 1997
- RFC 2068Hypertext Transfer Protocol -- HTTP/1.1Obsoleted
January 1997
- RFC 2854The 'text/html' Media TypeCurrent
June 2000
- RFC 3040Internet Web Replication and Caching TaxonomyCurrent
January 2001
- RFC 2065Domain Name System Security ExtensionsObsoleted
January 1997
- RFC 2440OpenPGP Message FormatObsoleted
November 1998
- RFC 2459Internet X.509 Public Key Infrastructure Certificate and CRL ProfileObsoleted
January 1999
- RFC 2517Building Directories from DNS: Experiences from WWWSeekerCurrent
February 1999
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?