Skip to main content

Diagnostic Responses for Session Initiation Protocol Hop Limit Errors
draft-ietf-sip-hop-limit-diagnostics-03

Document Type Expired Internet-Draft (sip WG)
Expired & archived
Author Scott Lawrence
Last updated 2006-06-19
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The Session Initiation Protocol (SIP) imposes a limit on the number of hops a request can transit on the way to its destination. When this limit is reached, a 483 (Too Many Hops) error response is returned. The present form of the 483 response does not provide enough information for the UAC or proxy on the path to diagnose failures whose symptom is that the hop limit is reached. This document specifies additional diagnostic information to be returned in a 483 response.

Authors

Scott Lawrence

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