SCS: Secure Cookie Sessions for HTTP
draft-barbato-scs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Stefano Barbato | ||
| Last updated | 2006-09-07 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document provides an overview of SCS, a cryptographic protocol aimed at the protection of "client-side" HTTP sessions, i.e. sessions in which the application state is held entirely on the client in the form of cookies [10].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)