[rfc-dist] RFC 3749 on Transport Layer Security Protocol Compression Methods

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri May 14 16:44:13 PDT 2004

A new Request for Comments is now available in online RFC libraries.

        RFC 3749

        Title:      Transport Layer Security Protocol Compression
        Author(s):  S. Hollenbeck
        Status:     Standards Track
        Date:       May 2004
        Mailbox:    shollenbeck at verisign.com
        Pages:      8
        Characters: 16411
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tls-compression-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3749.txt

The Transport Layer Security (TLS) protocol (RFC 2246) includes
features to negotiate selection of a lossless data compression method
as part of the TLS Handshake Protocol and to then apply the algorithm
associated with the selected method as part of the TLS Record
Protocol.  TLS defines one standard compression method which
specifies that data exchanged via the record protocol will not be
compressed.  This document describes an additional compression method
associated with a lossless data compression algorithm for use with
TLS, and it describes a method for the specification of additional
TLS compression methods.

This document is a product of the Transport Layer Security Working
Group of the IETF.

This is now a Proposed Standard Protocol.

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

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.echo 
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


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list