RFC 6026 on Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests
rfc-editor@rfc-editor.org Thu, 30 September 2010 18:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 EE6763A6D08; Thu, 30 Sep 2010 11:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.06
X-Spam-Level:
X-Spam-Status: No, score=-102.06 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 331f+rV0fbFo; Thu, 30 Sep 2010 11:13:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 982303A6E55; Thu, 30 Sep 2010 11:13:09 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4D725E06F2; Thu, 30 Sep 2010 11:13:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6026 on Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests
From: rfc-editor@rfc-editor.org
Message-Id: <20100930181356.4D725E06F2@rfc-editor.org>
Date: Thu, 30 Sep 2010 11:13:56 -0700
Cc: sipcore@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/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: Thu, 30 Sep 2010 18:13:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6026
Title: Correct Transaction Handling for 2xx
Responses to Session Initiation Protocol (SIP)
INVITE Requests
Author: R. Sparks, T. Zourzouvillys
Status: Standards Track
Stream: IETF
Date: September 2010
Mailbox: RjS@nostrum.com,
theo@crazygreek.co.uk
Pages: 20
Characters: 44035
Updates: RFC3261
I-D Tag: draft-ietf-sipcore-invfix-01.txt
URL: http://www.rfc-editor.org/rfc/rfc6026.txt
This document normatively updates RFC 3261, the Session Initiation
Protocol (SIP), to address an error in the specified handling of
success (2xx class) responses to INVITE requests. Elements following
RFC 3261 exactly will misidentify retransmissions of the request as a
new, unassociated request. The correction involves modifying the
INVITE transaction state machines. The correction also changes the
way responses that cannot be matched to an existing transaction are
handled to address a security risk. [STANDARDS TRACK]
This document is a product of the Session Initiation Protocol Core Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
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
Association Management Solutions, LLC