RFC 6083 on Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)

rfc-editor@rfc-editor.org Thu, 20 January 2011 17:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 482B828C0EE; Thu, 20 Jan 2011 09:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.997
X-Spam-Level:
X-Spam-Status: No, score=-101.997 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWFHm1CGb43K; Thu, 20 Jan 2011 09:49:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 89A2D28C0D9; Thu, 20 Jan 2011 09:49:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CA4DE0732; Thu, 20 Jan 2011 09:51:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6083 on Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)
From: rfc-editor@rfc-editor.org
Message-Id: <20110120175152.4CA4DE0732@rfc-editor.org>
Date: Thu, 20 Jan 2011 09:51:51 -0800
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2011 17:49:09 -0000

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

        
        RFC 6083

        Title:      Datagram Transport Layer Security (DTLS) 
                    for Stream Control Transmission Protocol (SCTP) 
        Author:     M. Tuexen, R. Seggelmann,
                    E. Rescorla
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    tuexen@fh-muenster.de, 
                    seggelmann@fh-muenster.de, 
                    ekr@networkresonance.com
        Pages:      9
        Characters: 16674
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-dtls-for-sctp-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6083.txt

This document describes the usage of the Datagram Transport Layer
Security (DTLS) protocol over the Stream Control Transmission
Protocol (SCTP).

DTLS over SCTP provides communications privacy for applications that
use SCTP as their transport protocol and allows client/server
applications to communicate in a way that is designed to prevent
eavesdropping and detect tampering or message forgery.

Applications using DTLS over SCTP can use almost all transport
features provided by SCTP and its extensions.  [STANDARDS-TRACK]

This document is a product of the Transport Area Working Group 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC