RFC 8261 on Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets
rfc-editor@rfc-editor.org Thu, 16 November 2017 07:16 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A4312969E; Wed, 15 Nov 2017 23:16:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6FEnDOe4dik; Wed, 15 Nov 2017 23:16:17 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B42C2129576; Wed, 15 Nov 2017 23:16:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C16FDB80D8D; Wed, 15 Nov 2017 23:15:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8261 on Datagram Transport Layer Security (DTLS) Encapsulation of SCTP Packets
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171116071556.C16FDB80D8D@rfc-editor.org>
Date: Wed, 15 Nov 2017 23:15:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/m5nOL5YdsgnxuBrIw31zXRwQ1xQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 16 Nov 2017 07:16:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8261
Title: Datagram Transport Layer Security (DTLS)
Encapsulation of SCTP Packets
Author: M. Tuexen,
R. Stewart,
R. Jesup,
S. Loreto
Status: Standards Track
Stream: IETF
Date: November 2017
Mailbox: tuexen@fh-muenster.de,
randall@lakerest.net,
randell-ietf@jesup.org,
Salvatore.Loreto@ericsson.com
Pages: 10
Characters: 21035
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-sctp-dtls-encaps-09.txt
URL: https://www.rfc-editor.org/info/rfc8261
DOI: 10.17487/RFC8261
The Stream Control Transmission Protocol (SCTP) is a transport
protocol originally defined to run on top of the network protocols
IPv4 or IPv6. This document specifies how SCTP can be used on top of
the Datagram Transport Layer Security (DTLS) protocol. Using the
encapsulation method described in this document, SCTP is unaware of
the protocols being used below DTLS; hence, explicit IP addresses
cannot be used in the SCTP control chunks. As a consequence, the
SCTP associations carried over DTLS can only be single-homed.
This document is a product of the Transport Area Working Group Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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