A.5 Procedures

[Sakae OKUBO]

-------- Original Message --------
Subject: RFC 2960 on Stream Control Transmission Protocol
Date: 31 Oct 2000 17:33:12 -0800
From: rfc-ed at ISI.EDU (RFC Editor)
Organization: Cisco Systems, Inc.
Newsgroups: cisco.external.ietf.announce


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


         RFC 2960

         Title:     Stream Control Transmission Protocol
         Author(s):  R. Stewart, Q. Xie, K. Morneault, C. Sharp,
                     H. Schwarzbauer, T. Taylor, I. Rytina, M. Kalla,
                     L. Zhang, V. Paxson
         Status:     Standards Track
        Date:       October 2000
         Mailbox:    rrs at cisco.com, qxie1 at email.mot.com,
                     kmorneau at cisco.com, chsharp at cisco.com,
                     HannsJuergen.Schwarzbauer at icn.siemens.de,
                     taylor at nortelnetworks.com,
                     ian.rytina at ericsson.com,
                     kalla at research.telcordia.com, lixia at cs.ucla.edu,
                     vern at aciri.org
         Pages:      134
         Characters: 297757
         Updates/Obsoletes/SeeAlso:  None

         I-D Tag:    draft-ietf-sigtran-sctp-13.txt

         URL:        ftp://ftp.isi.edu/in-notes/rfc2960.txt


This document describes the Stream Control Transmission Protocol
(SCTP).  SCTP is designed to transport PSTN signaling messages over
IP networks, but is capable of broader applications.

SCTP is a reliable transport protocol operating on top of a
connectionless packet network such as IP.  It offers the following
services to its users:

-- acknowledged error-free non-duplicated transfer of user data,
-- data fragmentation to conform to discovered path MTU size,
-- sequenced delivery of user messages within multiple streams,
    with an option for order-of-arrival delivery of individual
    user messages,
-- optional bundling of multiple user messages into a single SCTP
    packet, and
-- network-level fault tolerance through supporting of multi-homing
    at either or both ends of an association.

The design of SCTP includes appropriate congestion avoidance behavior
and resistance to flooding and masquerade attacks.

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

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

         To: rfc-info at RFC-EDITOR.ORG
         Subject: getting rfcs

         help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.


-------------------------------------------------------------------
Chip Sharp                       Consulting Engineering
Cisco Systems
"The best way to pick a lock is with a key."
http://www.netaid.org
-------------------------------------------------------------------

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com