draft-bidulock-tsvwg-sctptpi-00.me

No7信令,我需要交换类似的代码, 请店长审核,谢谢了,急着交换,谢谢

.R1
# abbreviate A
# label L
no-default-database
no-accumulate
database ../idrefs
annotate X pp
move-punctuation
discard YZ
.R2
.de $0
.(x 0
\\$2 \\$1
.)x
..
.if '\*(.T'ascii' \{\
.fo 'B. Bidulock'Version 0.0'FORMFEED[Page %]'
.m1 1 \" top margin above header
.m2 1 \" top margin below header
.m3 1 \" btm margin above footer
.m4 0 \" btm margin below footer
.pl 11.0i
.ll 7.2i
.lt 7.2i
.nr LL 7.2i
.nr LT 7.2i
.ad l
.hy 0
.ta 3
.ba 0
.po 0
.nr so 0
.nr ii 6n
.nr pi 4n
.nr po 3n
.nr bs 0
.nr bi 2n
.\}
.if '\*(.T'ps' \{\
.fo 'B. Bidulock'Version 0.0'Page %'
.m1 0.25i \" top margin above header
.m2 0.25i \" top margin below header
.m3 0.25i \" btm margin above footer
.m4 0.25i \" btm margin below footer
.pl 11.0i
.ll 7.2i
.lt 7.2i
.nr LL 7.2i
.nr LT 7.2i
.ad b
.hy 6
.ta 3
.ba 0
.po 0.75i
.nr so 0
.nr ii 0.5i
.nr pi 0.5i
.nr po 0.25i
.nr bs 0
.nr bi 0.25i
.nr hi 0.5i
.\}
.he 'Internet Draft'SCTP-TPI'May 2001'
.(b C
\fCNetwork Working Group                                     Brian Bidulock
\fCINTERNET-DRAFT                                       OpenSS7 Corporation


\fCExpires in six months                                           May 2001


\fR\fBStream Control Transmission Protocol (SCTP)
\fR\fBTransport Provider Interface (TPI)
\fR\fBSCTP-TPI
\fR\fB<draft-bidulock-sctpstreams-sigtran-00.txt>

.)b
.ne 4
.uh "Status of this Memo"
.lp
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 or RFC 2026.  Internet-Drafts are working documents
of the Inetnet Engineering Task Force (IETF), its areas, and its working
groups.  Note that other groups may also distribute working documents as
Internet-Drafts.
.lp
Internet-Drafts are draft documents valid for a maximum of six months and may
be updated, replaced, or obsoleted by other documents at any time.  It is
inappropriate to use Internet-Drafts as reference material or to cite them
other than as 'work in progress'.
.lp
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
.lp
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
.lp
To learn the current status of any Internet-Draft, please check the
'1id-abstracts.txt' listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
.uh "Abstract"
.lp
This Internet Draft provides a specification mapping the Stream Control
Transmission Protocol RFC 2960
.[
rfc2960
.]
into a SVR 4.2 STREAMS provider interface.
The benefit of this specification includes compatibility to UNIX International
TLI (Transport Layer Interface),
.[
tpi
.]
TPI (Transport Provider Interface),
.[
tpi99
.]
and XOpen/XPG4 XTI (XOpen Transport
Interface)
.[
xti
.]
for maximum compatibility with OSI and IP transport provider
applications based on SVR 4.2 STREAMS.  In addition, this specification
provides access to the features of SCTP which extend beyond those of existing
transport level interfaces.
.(z
.(c
\fC+----------------+-----------+-----------------------------+
|   Transport    |  Stream   |     IS 8072 Transport       |
|  Primitives    | Msg Type  |         Primitives          |
+----------------+-----------+-----------------------------+
| T_CONN_REQ     | M_PROTO   | T-CONNECT request           |
| T_CONN_IND     | M_PROTO   | T-CONNECT indication        |
| T_CONN_RES     | M_PROTO   | T-CONNECT response          |
| T_CONN_CON     | M_PROTO   | T-CONNECT confirm           |
| T_DATA_REQ     | M_PROTO   | T-DATA request              |
| T_DATA_IND     | M_PROTO   | T-DATA indication           |
| T_EXDATA_REQ   | M_PROTO   | T-EXPEDITED-DATA request    |
| T_EXDATA_IND   | M_PROTO   | T-EXPEDITED-DATA indication |
| T_DISCON_REQ   | M_PROTO   | T-DISCONNECT request        |
| T_DISCON_IND   | M_PROTO   | T-DISCONNECT indication     |
| T_UNITDATA_REQ | M_PROTO   | T-UNITDATA request          |
| T_UNITDATA_IND | M_PROTO   | T-UNITDATA indication       |
| T_ORDREL_REQ   | M_PROTO   | not defined in ISO          |
| T_ORDREL_IND   | M_PROTO   | not defined in ISO          |
| T_BIND_REQ     | M_PROTO   | not defined in ISO          |
| T_BIND_ACK     | M_PCPROTO | not defined in ISO          |
| T_UNBIND_REQ   | M_PROTO   | not defined in ISO          |
| T_OK_ACK       | M_PCPROTO | not defined in ISO          |
| T_ERROR_ACK    | M_PCPROTO | not defined in ISO          |
| T_INFO_REQ     | M_PCPROTO | not defined in ISO          |
| T_INFO_ACK     | M_PCPROTO | not defined in ISO          |
| T_UDERROR_IND  | M_PROTO   | not defined in ISO          |
| T_OPTMGMT_REQ  | M_PROTO   | not defined in ISO          |
| T_OPTMGMT_ACK  | M_PCPROTO | not defined in ISO          |
| T_ADDR_REQ     | M_PROTO   | not defined in ISO          |
| T_ADDR_ACK     | M_PCPROTO | not defined in ISO          |
| T_OPTDATA_REQ  | M_PROTO   | not defined in ISO          |
| T_OPTDATA_IND  | M_PROTO   | not defined in ISO          |
+----------------+-----------+-----------------------------+
.)c
.ce 2
\fBFigure 1.\fR  Mapping of ISO IS8072 and RFC 2960 to Kernel-level
Transport Service Primitives
.)z

.sh 1 "Introduction"
.lp
In contrast with the RFC 2126 (ITOT)
.[
rfc2126
.]
which uses TCP to provide ISO Network Service in support of ISO Transport
Service, this specification takes the approach of using the Open Group ISO
Transport Provider Interface
.[
tpi99
.]
as an interface to the RFC 2960 Stream Control Transmission Protocol (SCTP).
.[
rfc2960
.]
This permits applications which are written to the XPG4/XTI
.[
xti
.]
library which interfaces to the TPI
.[
tpi99
.]
and socket compatibility libraries to be used without much modification for
use with a SCTP Transport Provider which conforms to the SCTP-TPI.
.lp
This document provides an SCTP-specific implementation of the Transport
Provider Interface and provides details concerning address formats, options
and option formats, and specific IOCTLs and error handling around the
framework provided for in the TPI.
.[
tpi99
.]
.lp
This document describes the specification of an SCTP Transport Provider which
uses the Open Group STREAMS Transport Provider Interface as an interface to
Stream Control Transmission Protocol features and functions.  Because of the
need to select the SCTP stream upon which data is transmitted or received, it
is necessary to use Version 2, Draft 2 of the Transport Provider Interface
.[
tpi99
.]
as a basis for the specification, as this version incudes the
\fBT_OPTDATA_REQ\fR and \fBT_OPTDATA_IND\fR primitives which are necessary for
the selection of SCTP stream identifier, payload protocol identifier, and
other SCTP-specific options.  It is possible to use a subset of this
specification which is compatible with the TLI
.[
tli
.]
or older versions of the TPI,
.[
tpi
.]
however, selection of SCTP stream for transmission becomes awkward and
distinguishing streams upon reception may be impossible.
.lp
The TPI specification
.[
tpi99
.]
leaves a number of implementation- and provider-specific details to be
described by a particular implementation or provider.  This document details
the SCTP provider-specific details which are necessary for access to SCTP
features and functions.  In addition, it proposes some common
implementation-specific managment features and functions necessary to support
the global SCTP options as well as provide access to the SCTP-MIB.

.sh 1 "SCTP Provider-Specific Details"
.sh 2 "SCTP Transport Addresses"
.lp
The SCTP Transport Address is used in the following primitives:
.(l
.(c
\fC+----------------+--------------------------------+
|   Transport    |            Parameter           |
|  Primitives    |             Fields             |
+----------------+--------------------------------+
| T_INFO_ACK     |          ADDR_size             |
| T_ADDR_ACK     | LOCADDR_length, LOCADDR_offset |
|                | REMADDR_length, REMADDR_offset |
| T_BIND_REQ     |    ADDR_length,    ADDR_offset |
| T_BIND_ACK     |    ADDR_length,    ADDR_offset |
| T_CONN_REQ     |    DEST_length,    DEST_offset |
| T_CONN_CON     |     RES_length,     RES_offset |
| T_CONN_IND     |     SRC_length,     SRC_offset |
+----------------+--------------------------------+
.)c
.ce 2
\fBFigure 1.\fR  Transport Primitives which use
the SCTP Transport Address
.)l
.lp
The format of the SCTP address is as follows:
.(l
.nf
\fCstruct sctp_addr {
	uint16_t    port;
	uint32_t    addr[0];
};
.fi
.)l
.ba +4
.lp
Where
.ip "\fIport\fR"
is the 16-bit local or peer SCTP port number.
.ip "\fIaddr[]\fR"
is a list of 0 or more 32-bit IPv4 network addresses.
.ba -4
.lp
The SCTP Transport Address is interpreted by the SCTP Transport Provider in
the designated primitives and according to the rules described as follows:
.ip "\fIT_INFO_ACK\fR"
This primitive indicates the maximum size of a protocol address in the
\fIADDR_size\fR field of the primitive.  SCTP providers should set this field
to accomodate a number of network addresses in the \fIaddr\fR list in support
of multihomed hosts.  SCTP providers which do not support multihoming should
set this size to 6 for IPv4 providers.
.ip "\fIT_ADDR_ACK\fR"
This primitive indicates the locally bound protocol address and the remote
connected protocol address in the \fILOCADDR_length\fR, \fILOCADDR_offset\fR,
\fIREMADDR_length\fR, and \fIREMADDR_offset\fR, respectively.
The following rules define the SCTP provider-specific interpretation of the
transport address: