RFC 7092 on A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents
rfc-editor@rfc-editor.org Fri, 20 December 2013 21:23 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 57E7C1AE17A; Fri, 20 Dec 2013 13:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.953
X-Spam-Level:
X-Spam-Status: No, score=0.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 WpU_a6eJTcmT; Fri, 20 Dec 2013 13:23:43 -0800 (PST)
Received: from rfc-editor.org (unknown [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA0E1AE17F; Fri, 20 Dec 2013 13:23:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3CA5E7FC3AF; Fri, 20 Dec 2013 13:23:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7092 on A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents
From: rfc-editor@rfc-editor.org
Message-Id: <20131220212312.3CA5E7FC3AF@rfc-editor.org>
Date: Fri, 20 Dec 2013 13:23:12 -0800
Cc: drafts-update-ref@iana.org, straw@ietf.org, 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: Fri, 20 Dec 2013 21:23:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7092
Title: A Taxonomy of Session Initiation
Protocol (SIP) Back-to-Back User Agents
Author: H. Kaplan, V. Pascual
Status: Informational
Stream: IETF
Date: December 2013
Mailbox: hadriel.kaplan@oracle.com,
victor.pascual@quobis.com
Pages: 10
Characters: 22085
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-straw-b2bua-taxonomy-03.txt
URL: http://www.rfc-editor.org/rfc/rfc7092.txt
In many SIP deployments, SIP entities exist in the SIP signaling path
between the originating and final terminating endpoints, which go
beyond the definition of a SIP proxy, performing functions not
defined in Standards Track RFCs. The only term for such devices
provided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), which
is defined as the logical concatenation of a SIP User Agent Server
(UAS) and User Agent Client (UAC).
There are numerous types of SIP B2BUAs performing different roles in
different ways; for example, IP Private Branch Exchanges (IPBXs),
Session Border Controllers (SBCs), and Application Servers (ASs).
This document identifies several common B2BUA roles in order to
provide taxonomy other documents can use and reference.
This document is a product of the Sip Traversal Required for Applications to Work Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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