User Adaptation Layer Management (UA LM)

This document discusses how Transport Layer Security (TLS) and IPsec can be used to secure communication for SIGTRAN protocols. The main goal is to recommend the minimum security means that a SIGTRAN node must implement in order to attain secured communication. The support of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS support is optional.

This documents discusses how TLS and IPsec can be used to secure the communication for SIGTRAN protocols. The support of IPsec is mandatory for all nodes running SIGTRAN protocols and the support of TLS is optional.

This document describes the applicability of the several protocols developed under the signalling transport framework[RFC2719]. A description of the main issues regarding the use of the Stream Control Transmission Protocol (SCTP)[RFC2960] and each adaptation layer for transport of telephony signalling information over IP infrastructure is explained.

This memo describes ASP Congestion (ASPCONG) that provides the ability for an Application Server Process (ASP) to indicate congestion to a Signalling Gateway (SG) for the SS7 Signalling User Adaptation Layers [M2UA..SUA, ISUA, TUA]. Extension parameters and procedures are added by this memo in extension to those of the User Adaptation layers to provide for ASP congestion.

This Internet-Draft describes ASP Extensions (ASPEXT) for Signalling User Adaptation Protocols [IUA, DUA, V5UA, M2UA, M3UA, SUA, TUA], which permits cooperating Signalling Peer Processes (SPPs) to indicate to each other the specific protocol extensions that each supports.

This Internet-Draft describes Signalling Gateway (SG) Information (SGINFO) for Signalling User Adaptation Protocols [M2UA, M3UA, SUA, TUA], which permits supporting Signalling Gateways (SG) to convey additional Application Server (AS) support information to Application Server Processes (ASPs) activating for AS on the SG. This additional AS support information consists of information pertaining to the underlying SS7 Signalling Provider that otherwise would have to be statically configured at the Application Server Process (ASP) or exchanged between SG and ASP using a non-IETF defined protocol.

This Internet-Draft describes Load Selection for Signalling User Adaptation Protocols [M3UA, SUA, TUA], which permits an Application Server Processes (ASP) to indicate its placement within an Application Server and permits an Signalling Gateway (SG) to distribute traffic over ASPs in Application Servers under Application Server Process (ASP) control.

This Internet-Draft describes Load Selection for Signalling User Adaptation Protocols [M3UA, SUA, TUA], which permits an Application Server Processes (ASP) to indicate its placement within an Application Server and permits an Signalling Gateway (SG) to distribute traffic over ASPs in Application Servers under Application Server Process (ASP) control.

This Internet-Draft describes Correlation Id and Heartbeat procedures to support lossless fail-over between SCTP [RFC 2960] associations for Signalling User Adaptation Protocols [M3UA, SUA, TUA] above MTP3 [Q.704] supporting the concept of a Routing Context. These procedures permit lossless fail-over between Application Server Processes (ASPs) at a Signalling Gateway (SG) and fail-over between Signalling Gateway Processes (SGPs) and Signalling Gateways (SGs) at an Application Server Process (ASP). Lossless fail-over permits these fail-overs to occur without loss or duplication of UA-User messages.

This memo describes Registration Extensions (REGEXT) that provides the ability for an Application Server Process (ASP) to modify existing Routing (Link) Keys with a Signalling Gateway (SG).

Current procedures in the SS7 Signalling User Adaptation Layers (UAs) [M2UA..TUA] do not provide for the modification of Routing (Link) Keys without deactivation of the Application Server (AS). This causes problems in making changes to live systems.

The extensions described in this memo permit modification of Signalling Link membership in Application Servers for SS7 MTP2-User Adaptation Layer [M2UA], modification of Circuit Identification Code (CIC) ranges for the SS7 MTP3-User Adaptation Layer [M3UA], modification of Circuit Identification Code (CIC) rnages for the SS7 ISUP-User Adaptation Layer [ISUA], modificiation of Destination Local Reference (DLR) ranges for SS7 SCCP-User Adaptation Layer [SUA], and modification of Transaction Identifier (TID) ranges for SS7 TCAP-User Adaptation Layer [TUA].

This memo describes Session Id Registration (SESSID) that provides the ability for one (listening) Application Server to indicate that a session should be established with another (accepting) Application Server for connection- and transaction-oriented messaging in the SS7 Signalling User Adaptation Layers [M3UA-BIS..TUA]. Extension parameters and procedures are added by this memo in extension to those of the User Adaptation layers to provide a closer model to that of the XNS/XTI interfaces, where one interface may be designated as a `listener' and another designated as an `acceptor'. This permits ISO compliant interfaces for SCCP to maintain the same semantic for SUA and TUA.

This Internet-Draft describes Load Selection for Signalling User Adaptation Protocols [M3UA-BIS, SUA..TUA], which permits an Application Server Processes (ASP) to indicate its placement within an Application Server and permits an Signalling Gateway (SG) to distribute traffic over ASPs in Application Servers under Application Server Process (ASP) control.

This document defines an architecture framework and functional requirements for transport of signaling information over IP. The framework describes relationships between functional and physical entities exchanging signaling information, such as Signaling Gateways and Media Gateway Controllers. It identifies interfaces where signaling transport may be used and the functional and performance requirements that apply from existing Switched Circuit Network (SCN) signaling protocols.