idnits 2.17.1 draft-ietf-tls-extensions-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3546 5 Title: Transport Layer Security (TLS) Extensions 6 Author(s): S. Blake-Wilson, M. Nystrom, D. Hopwood, 7 J. Mikkelsen, T. Wright 8 Status: Standards Track 9 Date: June 2003 10 Mailbox: sblakewilson@bcisse.com, magnus@rsasecurity.com, 11 david.hopwood@zetnet.co.uk, 12 janm@transactionware.com, 13 timothy.wright@vf.vodafone.co.uk 14 Pages: 29 15 Characters: 63437 16 Obsoletes: 2246 18 I-D Tag: draft-ietf-tls-extensions-06.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3546.txt 22 This document describes extensions that may be used to add 23 functionality to Transport Layer Security (TLS). It provides both 24 generic extension mechanisms for the TLS handshake client and server 25 hellos, and specific extensions using these generic mechanisms. 27 The extensions may be used by TLS clients and servers. The extensions 28 are backwards compatible - communication is possible between TLS 1.0 29 clients that support the extensions and TLS 1.0 servers that do not 30 support the extensions, and vice versa. 32 This document is a product of the Transport Layer Security Working 33 Group of the IETF. 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.