RFC 7332: Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7332
- Published
- August 2014
- Authors
- H. Kaplan; V. Pascual
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7340Secure Telephone Identity Problem Statement and RequirementsCurrent
September 2014
- RFC 7320URI Design and OwnershipObsoleted
July 2014
- RFC 7345UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)Updated
August 2014
- RFC 7352Sieve Email Filtering: Detecting Duplicate DeliveriesCurrent
September 2014
- RFC 7310RTP Payload Format for Standard apt-X and Enhanced apt-X CodecsCurrent
July 2014
- RFC 7303XML Media TypesCurrent
July 2014
- RFC 7362Latching: Hosted NAT Traversal (HNT) for Media in Real-Time CommunicationCurrent
September 2014
- RFC 7363Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)Current
September 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?