RFC 3788: Security Considerations for Signaling Transport (SIGTRAN) Protocols

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID

RFC3788

Published

June 2004

Authors

J. Loughney; M. Tuexen; J. Pastor-Balbas

Status

PROPOSED STANDARD

Stream

IETF

Area

rai

Pages

13

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3788

Topics

• SIGTRAN
• Signaling Transport
• Security

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4165Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA)Current

  September 2005

• RFC 4474Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)Obsoleted

  August 2006

• RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent

  November 2011

• RFC 3776Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home AgentsUpdated

  June 2004

• RFC 3766Determining Strengths For Public Keys Used For Exchanging Symmetric KeysCurrent

  April 2004

• RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent

  April 2004

• RFC 3833Threat Analysis of the Domain Name System (DNS)Current

  August 2004

• RFC 3723Securing Block Storage Protocols over IPUpdated

  April 2004

Also filed under

• PROPOSED STANDARD
• 2004
• IETF stream
• rai area