[rfc-dist] RFC 4346 on The Transport Layer Security (TLS) Protocol Version 1.1
rfc-editor@rfc-editor.org
rfc-editor at rfc-editor.org
Wed Apr 26 15:13:38 PDT 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4346
Title: The Transport Layer Security (TLS)
Protocol Version 1.1
Author: T. Dierks, E. Rescorla
Status: Standards Track
Date: April 2006
Mailbox: tim at dierks.org,
ekr at rtfm.com
Pages: 87
Characters: 187041
Obsoletes: RFC2246
See-Also:
I-D Tag: draft-ietf-tls-rfc2246-bis-13.txt
URL: http://www.rfc-editor.org/rfc/rfc4346.txt
This document specifies Version 1.1 of the Transport Layer Security
(TLS) protocol. The TLS protocol provides communications security
over the Internet. The protocol allows client/server applications to
communicate in a way that is designed to prevent eavesdropping,
tampering, or message forgery. [STANDARDS TRACK]
This document is a product of the Transport Layer Security
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of
the Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
More information about the rfc-dist
mailing list