Fwd: I-D Action:draft-sparks-sip-invfix-03.txt
Robert Sparks <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
This got a fairly big touch due to better handling of transport error conditions. Please review this carefully. RjS Begin forwarded message: > From: [email protected] > Date: March 2, 2009 8:45:01 AM CST > To: [email protected] > Subject: I-D Action:draft-sparks-sip-invfix-03.txt > Reply-To: [email protected] > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title : Correct transaction handling for 200 responses to > Session Initiation Protocol INVITE requests > Author(s) : R. Sparks > Filename : draft-sparks-sip-invfix-03.txt > Pages : 20 > Date : 2009-03-02 > > 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. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-sparks-sip-invfix-03.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > _______________________________________________ > I-D-Announce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip