1 - 2 - 3 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
SCTP
Click on the red underlined text to get to the source
... Diameter clients MUST support either TCP or SCTP, while agents and
servers MUST support both. Future versions ...
... When connecting to a peer and either zero or more transports are
specified, SCTP SHOULD be tried first, followed by TCP. See Section
5.2 for more information on peer discovery.
...
... SCTP Guidelines ...
... The following are guidelines for Diameter implementations that
support SCTP:
1. For interoperability ...
... Diameter nodes MUST be prepared to
receive Diameter messages on any SCTP stream in the association.
...
...
2. To prevent blocking: All Diameter nodes SHOULD utilize all SCTP
streams available to the association to prevent head-of-the-line
...
... domain. This specification defines
D2T for TCP and D2S for SCTP. We also establish an IANA
registry for NAPTR service name ...
... IP address. All source
addresses that a Diameter node expects to use with SCTP [SCTP] MUST
be advertised in the CER ...
... supported-transports= string L M
SCTP
# This attribute lists the supported transports that the Diameter ...
... # implementation accepts. Note that a compliant Diameter
# implementation MUST support SCTP, though it MAY support other
# transports, too.
...
... "" _aaa._tcp.example.com
This indicates that the server supports SCTP, and TCP, in that order.
If the client ...
... If the client supports over SCTP, SCTP will be used, targeted to a
host determined by an SRV ...