RFC 7332 on Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)
rfc-editor@rfc-editor.org Wed, 13 August 2014 00:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B4BF1A6EE8 for <ietf-announce@ietfa.amsl.com>; Tue, 12 Aug 2014 17:36:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level:
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45dqCMjaE42B for <ietf-announce@ietfa.amsl.com>; Tue, 12 Aug 2014 17:36:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 96A511A07DC for <ietf-announce@ietf.org>; Tue, 12 Aug 2014 17:36:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 65932180015; Tue, 12 Aug 2014 17:34:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7332 on Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140813003415.65932180015@rfc-editor.org>
Date: Tue, 12 Aug 2014 17:34:15 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/bkiWrXoXUyd4-xGO5d8jnsxk_do
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 00:36:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7332
Title: Loop Detection Mechanisms for Session
Initiation Protocol (SIP)
Back-to-Back User Agents (B2BUAs)
Author: H. Kaplan, V. Pascual
Status: Standards Track
Stream: IETF
Date: August 2014
Mailbox: hadrielk@yahoo.com,
victor.pascual@quobis.com
Pages: 5
Characters: 11157
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-straw-b2bua-loop-detection-04.txt
URL: https://www.rfc-editor.org/rfc/rfc7332.txt
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.
This document is a product of the Sip Traversal Required for Applications to Work Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC