Clientside interoperability experiences for the SSL and TLS protocols
draft-ietf-tls-interoperability-00
| Document | Type | Expired Internet-Draft (tls WG) | |
|---|---|---|---|
| Last updated | 2006-10-18 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tls-interoperability-00.txt
https://www.ietf.org/archive/id/draft-ietf-tls-interoperability-00.txt
Abstract
This document presents a number of problems encountered when implementing TLS 1.0, TLS 1.1 and TLS Extensions for clients, and their consequences. The problems include servers that refuse to connect with clients supporting newer versions of the protocol, or that do not handle such negotiation properly. Another problem encountered is the incorrect use of values in the protocol messages.
Authors
Yngve Pettersen (yngve@opera.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)