Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000238265D
Original Publication Date: 2014-Aug-01
Included in the Prior Art Database: 2014-Aug-13
Document File: 10 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Kaplan: AUTHOR [+2]

Abstract

SIP provides a means of preventing infinite request forwarding loops in [RFC3261], and a means of mitigating parallel forking amplification floods in [RFC5393]. Neither document normatively defines specific behavior for B2BUAs, however.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 25% of the total text.

Internet Engineering Task Force (IETF)                         H. Kaplan Request for Comments: 7332                                        Oracle Category: Standards Track                                     V. Pascual ISSN: 2070-1721                                                   Quobis                                                              August 2014

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

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7332.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Kaplan & Pascual             Standards Track                    [Page 1]
 RFC 7332                Loop Detection for B2BUAs            August 2014

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   2    3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3    4.  B2BUA Loop-Detection Behavior . . . . . . . . . . . . . . . .   3    5.  B2BUA Max-Forwards Behavior . . . ....