Skip to main content

Handling Large User Datagram Protocol (UDP) Responses in the Session Initiation Protocol (SIP)
draft-gurbani-sip-large-udp-response-00

Document Type Expired Internet-Draft (individual)
Authors Vijay K. Gurbani , Scott Lawrence
Last updated 2006-10-04
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-gurbani-sip-large-udp-response-00.txt

Abstract

The Session Initiation Protocol (SIP) mandates a maximum size for any request transmitted over UDP. This maximum is set to the lesser of 1300 bytes or the path maximum transmission unit (MTU) size minus 200 bytes. If the size of the request exceeds this maximum, SIP requires implementations to switch the downstream transport to be a congestion controlled transport. However, when sending a response, a SIP implementation cannot choose the transport; it must use the transport specified by the Via. This document discusses the problems large responses can cause on UDP, and proposes an update to SIP to help diagnose and avoid those problems.

Authors

Vijay K. Gurbani
Scott Lawrence

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)