RFC 2543

RFC 2543
Title	RFC 2543
Type	Internet standard
Published	March 1999
Status	Historic
Authors	Jon Peterson, Henning Schulzrinne
Organization	Internet Engineering Task Force

RFC 2543 is a standards-track document that specified a protocol for initiating, modifying, and terminating multimedia communication sessions over packet-switched networks. The document defined a signaling framework widely referenced alongside contemporaneous work by the Internet Engineering Task Force, World Wide Web Consortium, International Telecommunication Union, IETF Working Group, and major vendors such as Cisco Systems and Microsoft. RFC 2543 influenced implementations in products and research from institutions like Bell Labs, MIT, Stanford University, Carnegie Mellon University, and Xerox PARC.

Introduction

RFC 2543 introduced a session initiation protocol that provided mechanisms for establishing sessions between user agents and proxy servers, facilitating interoperability among disparate systems produced by companies including Nortel Networks, Siemens, Alcatel, Lucent Technologies, and Ericsson. The specification positioned itself within the ecosystem shaped by standards from ITU-T, 3GPP, ETSI, and academic work at UC Berkeley and University College London. Its release prompted analysis and commentary in conferences such as SIGCOMM, ICCCN, IEEE INFOCOM, and ACM Multimedia.

Background and Purpose

The document addressed signaling needs emerging from deployments by carriers like AT&T, Verizon Communications, BT Group, and research projects at DARPA. It sought to provide a flexible, text-based protocol inspired by architectures seen in protocols from CERN and formats used in Hypertext Transfer Protocol, aligning with design patterns from Andrew File System efforts and the X Window System. The purpose included enabling services comparable to those in systems by Avaya and NEC while accommodating packet technologies promoted by IETF chartered groups and standards bodies such as IEEE and ITU.

Protocol Overview

RFC 2543 specified message types, transaction models, and state machines for components like user agents, registrars, and proxies—roles also discussed in literature from Bellcore and specifications by IETF SIPPING Working Group successors. It described SIP methods analogous in role to operations in SMTP, FTP, and HTTP/1.1 and defined header fields and URI usage similar to conventions from IETF RFC 2396 and directory mappings found in LDAP specifications influenced by work at Sun Microsystems. The architecture enabled interworking with signaling systems such as SS7 and media negotiation practices associated with H.323 and codec profiles used in implementations by RealNetworks and Qualcomm.

Message Formats and Procedures

Message syntax in the specification used a start-line and header model familiar to implementers of Hypertext Transfer Protocol and echoed ABNF constructs seen in RFC 2234. Procedures covered INVITE, ACK, BYE, REGISTER, and other methods implemented in stacks from vendors including Avaya Labs and open-source projects originating at University of California, Irvine and IETF community repositories. The document defined dialog state, transaction retransmission, and timing considerations that intersected with timer designs in TCP and retransmission strategies examined by researchers at MITRE and UC San Diego.

Security Considerations

RFC 2543 discussed authentication, encryption, and integrity protection referencing mechanisms from HTTP Digest Access Authentication and transport security approaches like those of IPsec and Secure Sockets Layer. It identified threats including message interception, spoofing, and replay that had been analyzed in work by RSA Laboratories, CERT Coordination Center, and security teams at Sun Microsystems. The specification recommended use of existing security infrastructure such as certificates aligned with practices from ITU-T X.509 and trust models promulgated by organizations like IETF PKIX Working Group.

Implementations and Adoption

Following publication, RFC 2543 was implemented in commercial products by Cisco Systems, Alcatel-Lucent, Siemens AG, and software from projects affiliated with University of Cambridge and Columbia University. Open-source stacks and toolkits drew contributions from communities around FreeSWITCH, Asterisk (PBX), OpenSIPS, and research prototypes in labs at Georgia Institute of Technology and ETH Zurich. Service providers in regions served by Deutsche Telekom, Telstra, and NTT Communications evaluated and deployed systems based on the specification, often integrating interconnection work influenced by ENUM and numbering plans supervised by International Telecommunication Union committees.

Legacy and Obsolescence

RFC 2543 was superseded by later revisions and updates from the Internet Engineering Task Force and related groups, influencing successor specifications maintained by the IETF SIPPING Working Group and consolidated in documents that addressed interoperability and security shortcomings identified by vendors and operators including Google, Apple Inc., and Facebook. Its concepts persisted in derivatives and extensions used in modern unified communications platforms developed by Zoom Video Communications, Avaya, Microsoft Teams, and standards harmonized with efforts from 3GPP and ETSI. The historical role of the specification is discussed in surveys at venues like IEEE Communications Magazine and retrospective analyses by researchers associated with ACM SIGCOMM.

Category:Internet standards