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

Document Type Expired Internet-Draft (sip WG)
Last updated 2006-06-19
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
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-ietf-sip-hop-limit-diagnostics-03.txt

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 (slawrence@pingtel.com)

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