RFC 6458 on Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)

rfc-editor@rfc-editor.org Sun, 11 December 2011 22:19 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 BCC0721F84C2; Sun, 11 Dec 2011 14:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.241
X-Spam-Level:
X-Spam-Status: No, score=-105.241 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIlfWuMvGUx7; Sun, 11 Dec 2011 14:19:18 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id E729321F84CE; Sun, 11 Dec 2011 14:19:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DA1A472E004; Sun, 11 Dec 2011 14:18:24 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6458 on Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)
From: rfc-editor@rfc-editor.org
Message-Id: <20111211221824.DA1A472E004@rfc-editor.org>
Date: Sun, 11 Dec 2011 14:18:24 -0800 (PST)
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Sun, 11 Dec 2011 22:19:18 -0000

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

        
        RFC 6458

        Title:      Sockets API Extensions for the 
                    Stream Control Transmission Protocol (SCTP) 
        Author:     R. Stewart, M. Tuexen,
                    K. Poon, P. Lei,
                    V. Yasevich
        Status:     Informational
        Stream:     IETF
        Date:       December 2011
        Mailbox:    randall@lakerest.net, 
                    tuexen@fh-muenster.de, 
                    ka-cheong.poon@oracle.com,
                    peterlei@cisco.com, 
                    vladislav.yasevich@hp.com
        Pages:      115
        Characters: 237112
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-sctpsocket-32.txt

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

This document describes a mapping of the Stream Control Transmission
Protocol (SCTP) into a sockets API.  The benefits of this mapping
include compatibility for TCP applications, access to new SCTP
features, and a consolidated error and event notification scheme.
This document is not an Internet Standards Track specification; it is
published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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