bk99.de entertain the web since 1997

bk99.de
RFC · Real-time communicationStandard explained

RFC 3261: SIP: Setting up sessions over the internet

Summary

RFC 3261 defines SIP for locating participants and for setting up, changing and ending multimedia sessions. Signalling and media path can be operated independently. Flexible addressing runs into NAT and security boundaries in real networks.

Ideas

  • Registrars link user addresses with current contact targets.
  • Proxies forward signalling between domains.
  • SDP describes media separately from SIP signalling.

Facts

  • RFC 3261 replaces RFC 2543.

Remarks

  • RFC 3261 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Protect SIP signalling and limit open relay operation.
  • Analyse signalling and RTP media separately when troubleshooting.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2003

RFC 3550: RTP: Transporting real-time media

RFC 3550 describes RTP and RTCP for time-critical audio and video data over packet-switched networks. Real-time communication optimises for timely rather than perfect delivery. Measurable quality feedback enables adaptive media transmission.

RFC · 1993

RFC 1459: IRC: Open real-time communication

RFC 1459 documents the Internet Relay Chat protocol for federated servers, channels and direct messages. Simple text protocols can carry communities for decades. Federation distributes operations but requires shared conventions.

RFC · 2004

RFC 3711: SRTP: Confidential real-time media

RFC 3711 adds encryption, integrity and replay protection for audio and video streams to RTP. Real-time security must combine low delay with effective protection. Key management remains a central task outside the media format.