Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)

Haim Kaplan, V. Pascual2014 · DOI

TL;DR

This paper addresses a critical issue in SIP communication: how Back-to-Back User Agents (B2BUAs) can inadvertently create infinite request routing loops. It proposes normative requirements for B2BUAs to properly handle Max-Forwards and Max-Breadth headers, ensuring they don't reset these values and thus prevent unbounded loops, which have historically caused service outages.

What Problem Does This Paper Address?

The Session Initiation Protocol (SIP) is a fundamental signaling protocol for IP-based communication, enabling features like voice and video calls. A key mechanism to prevent infinite request forwarding loops in SIP is the Max-Forwards header, which dictates the maximum number of hops a request can traverse. However, a specific type of SIP entity called a Back-to-Back User Agent (B2BUA) presents a challenge. B2BUAs act as both a User Agent Server (UAS) and a User Agent Client (UAC) for different legs of a call. While technically compliant with SIP standards, B2BUAs have the ability to generate new SIP requests on their UAC side, and some have been observed to reset or not properly propagate the Max-Forwards value. This behavior can effectively break the loop detection mechanism, leading to "unbounded" or unending SIP request loops. These loops are often caused by misconfigurations but become problematic due to B2BUAs' actions, resulting in service outages and making troubleshooting extremely difficult. Additionally, a related issue, parallel forking amplification, is also exacerbated when B2BUAs don't propagate a Max-Breadth header, as defined in RFC 5393.

Methods

This document defines normative requirements for B2BUAs concerning two specific SIP header fields: Max-Forwards and Max-Breadth.

For Max-Forwards:

  • B2BUAs are required to copy the received Max-Forwards header from their UAS side to any request they generate on their UAC side.
  • They must decrement this value, mirroring the behavior of a proxy as defined in RFC 3261.
  • As a UAS, B2BUAs must also check the Max-Forwards header and reject or respond to requests if the value is zero.
  • If a received request lacks a Max-Forwards header, a new one must be created on the UAC side, with a recommended initial value of 70, consistent with proxy behavior.

For Max-Breadth:

  • B2BUAs are required to copy the received Max-Breadth header from their UAS side to any request they generate on their UAC side, similar to proxy behavior.
  • They must adhere to the requirements for proxies as described in RFC 5393, including generating the header if none is received and limiting its maximum value.
  • B2BUAs that generate parallel requests on their UAC side for a single incoming request must also follow the rules for Max-Breadth handling as if they were a parallel forking proxy.

The paper also recommends that B2BUAs implement the loop-detection mechanism for the Via header field, as defined for proxies in RFC 5393.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • B2BUAs as the Loop Enablers: The core insight is that while misconfigurations might initiate loops, it's the specific behavior of B2BUAs (resetting or not propagating Max-Forwards) that allows these loops to become unbounded and cause significant disruption.
  • Standardization is Key: The paper emphasizes that existing SIP loop detection mechanisms (like Via header checks) are insufficient for B2BUAs because B2BUAs can effectively "start fresh" on their UAC side. The solution lies in standardizing how B2BUAs handle critical loop-prevention headers.
  • Max-Forwards and Max-Breadth are Crucial: The paper highlights that these two headers, when handled correctly by B2BUAs, are the primary tools to mitigate both infinite routing loops and parallel forking amplification.
  • Privacy vs. Loop Detection Trade-off: The document acknowledges that some B2BUAs might reset these headers for privacy reasons (obfuscating hop count). However, it clearly states that this goal is at odds with loop detection, and administrators must decide which is more important. The RFC mandates loop detection as the default behavior.

Key Results

The paper doesn't present quantitative results from experiments or evaluations. Instead, its key "results" are the normative requirements it defines for B2BUAs. By mandating specific behaviors for Max-Forwards and Max-Breadth header handling, the paper aims to:

  • Mitigate the effect of unbounded SIP request loops.
  • Prevent parallel forking amplification issues.
  • Improve the robustness and reliability of SIP deployments that utilize B2BUAs.

Limitations and Future Work

  • Privacy Concerns: The paper acknowledges the conflict between the proposed loop detection mechanisms and the desire for privacy through header obfuscation. While it mandates loop detection by default, it notes that manufacturers may provide user-configurable overrides, implying that the tension between these goals remains.
  • Scope of B2BUA Types: While the requirements apply to "all B2BUA types," the paper notes that for in-dialog requests, B2BUAs may perform the same actions, suggesting a potential area for further clarification or refinement in future work.
  • Future Work: The paper doesn't explicitly outline future work but implies that the defined requirements are a necessary step towards a more stable SIP ecosystem. The ongoing challenge of balancing security, privacy, and functionality in network protocols is a continuous area for research.

Summary updated

Abstract

SIP Back-to-Back User Agents (B2BUAs) can cause unending SIP request routing loops because, as User Agent Clients, they can generate SIP requests with new Max-Forwards values. This document discusses the difficulties associated with loop detection for B2BUAs and the requirements for them to prevent infinite loops.
BibTeX
@misc{kaplan2014loop,
  author = {Haim Kaplan and V. Pascual},
  title = {{Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)}},
  year = {2014},
  doi = {10.17487/rfc7332},
}

Loading related content...

Figure