BCP 147, RFC 5407 on Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)
rfc-editor@rfc-editor.org Wed, 10 December 2008 22:57 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1553128C1FB; Wed, 10 Dec 2008 14:57:10 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8942228C1F3; Wed, 10 Dec 2008 14:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.664
X-Spam-Level:
X-Spam-Status: No, score=-16.664 tagged_above=-999 required=5 tests=[AWL=0.935, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxrbG9M+DNpf; Wed, 10 Dec 2008 14:57:06 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id A050728C1F2; Wed, 10 Dec 2008 14:57:06 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 31C9A1A349B; Wed, 10 Dec 2008 14:57:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 147, RFC 5407 on Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)
From: rfc-editor@rfc-editor.org
Message-Id: <20081210225701.31C9A1A349B@bosco.isi.edu>
Date: Wed, 10 Dec 2008 14:57:01 -0800
Cc: sipping@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
BCP 147
RFC 5407
Title: Example Call Flows of Race Conditions
in the Session Initiation Protocol (SIP)
Author: M. Hasebe, J. Koshiko,
Y. Suzuki, T. Yoshikawa,
P. Kyzivat
Status: Best Current Practice
Date: December 2008
Mailbox: hasebe.miki@east.ntt.co.jp,
j.koshiko@east.ntt.co.jp,
suzuki.yasushi@lab.ntt.co.jp,
tomoyuki.yoshikawa@east.ntt.co.jp,
pkyzivat@cisco.com
Pages: 60
Characters: 120005
See Also: BCP0147
I-D Tag: draft-ietf-sipping-race-examples-06.txt
URL: http://www.rfc-editor.org/rfc/rfc5407.txt
This document gives example call flows of race conditions in the
Session Initiation Protocol (SIP). Race conditions are inherently
confusing and difficult to thwart; this document shows the best
practices to handle them. The elements in these call flows include
SIP User Agents and SIP Proxy Servers. Call flow diagrams and
message details are given. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion
and suggestions for improvements.
This document is a product of the Session Initiation Proposal Investigation Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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/rfcsearch.html.
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
USC/Information Sciences Institute
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce