@techreport{ietf-sip-hop-limit-diagnostics-03,
    number =    {draft-ietf-sip-hop-limit-diagnostics-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-sip-hop-limit-diagnostics/03/},
    author =    {Scott Lawrence},
    title =     {{Diagnostic Responses for Session Initiation Protocol Hop Limit Errors}},
    pagetotal = 17,
    year =      2006,
    month =     jun,
    day =       19,
    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.},
}