Correct transaction handling for 200 responses to Session Initiation Protocol INVITE requests
draft-sparks-sipcore-invfix-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert Sparks , Theo Zourzouvillys | ||
| Last updated | 2010-01-13 (Latest revision 2009-09-12) | ||
| Replaces | draft-sparks-sip-invfix | ||
| Replaced by | draft-ietf-sipcore-invfix | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sipcore-invfix | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document normatively updates RFC 3261, the Session Initiation Protocol (SIP), to address an error in the specified handling of success (200 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.
Authors
Robert Sparks
Theo Zourzouvillys
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)