metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 3581: An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing

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

The Session Initiation Protocol (SIP) operates over UDP and TCP, among others. When used with UDP, responses to requests are returned to the source address the request came from, and to the port written into the topmost Via header field value of the request. This behavior is not desirable in many cases, most notably, when the client is behind a Network Address Translator (NAT). This extension defines a new parameter for the Via header field, called "rport", that allows a client to request that the server send the response back to the source IP address and port from which the request originated. [STANDARDS-TRACK]

Document record

Document ID
RFC3581
Published
August 2003
Authors
J. Rosenberg; H. Schulzrinne
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
13
Also known as
—

Topics

Related documents

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

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3581-an-extension-to-the-session-initiation-protocol-sip-for-symmetric-response-routi