idnits 2.17.1 draft-ietf-tsvwg-tls-over-sctp-00.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 3436 5 Title: Transport Layer Security over Stream Control 6 Transmission Protocol 7 Author(s): A. Jungmaier, E. Rescorla, M. Tuexen 8 Status: Standards Track 9 Date: December 2002 10 Mailbox: ajung@exp-math.uni-essen.de, ekr@rtfm.com, 11 Michael.Tuexen@icn.siemens.de 12 Pages: 9 13 Characters: 16333 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-tsvwg-tls-over-sctp-00.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3436.txt 20 This document describes the usage of the Transport Layer Security 21 (TLS) protocol, as defined in RFC 2246, over the Stream Control 22 Transmission Protocol (SCTP), as defined in RFC 2960 and RFC 3309. 24 The user of TLS can take advantage of the features provided 25 by SCTP, namely the support of multiple streams to avoid head of line 26 blocking and the support of multi-homing to provide network level 27 fault tolerance. 29 Additionally, discussions of extensions of SCTP are also 30 supported, meaning especially the support of dynamic 31 reconfiguration of IP-addresses. 33 This document is a product of the Transport Area Working Group Working 34 Group of the IETF. 36 This is now a Proposed Standard Protocol. 38 This document specifies an Internet standards track protocol for 39 the Internet community, and requests discussion and suggestions 40 for improvements. Please refer to the current edition of the 41 "Internet Official Protocol Standards" (STD 1) for the 42 standardization state and status of this protocol. Distribution 43 of this memo is unlimited. 45 This announcement is sent to the IETF list and the RFC-DIST list. 46 Requests to be added to or deleted from the IETF distribution list 47 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 48 added to or deleted from the RFC-DIST distribution list should 49 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 51 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 52 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 53 help: ways_to_get_rfcs. For example: 55 To: rfc-info@RFC-EDITOR.ORG 56 Subject: getting rfcs 58 help: ways_to_get_rfcs 60 Requests for special distribution should be addressed to either the 61 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 62 specifically noted otherwise on the RFC itself, all RFCs are for 63 unlimited distribution.echo 64 Submissions for Requests for Comments should be sent to 65 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 66 Authors, for further information.