Clientside interoperability experiences for the SSL and TLS protocols
draft-pettersen-tls-interop-experience-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yngve Pettersen | ||
| Last updated | 2006-06-21 | ||
| 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 presents a number of problems encountered when implementing TLS 1.0, TLS 1.0 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 does not handle such negotiation properly. Other problems encountered are incorrect use of values in the protocol messages. The consequences of these problems range from delayed introduction of new protocol versions and features, to fallback mechanisms that may disable protocol security features, to implementations that cannot interoperate with some other implementations.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)