Hrmm. I think you're right, and the place where it makes a big
difference is at
proxies in the path of the 200 that have a TCP hop on either side of
them - we want
that client transaction to still be there for retransmissions of the
200.
Whether the fix is as simple as setting timer D will take more
thinking (and I want
to wait for more feedback on the rest of the draft before cracking
this open).
I've started a list of things to work through with this item.
Thanks,
RjS
On Jul 3, 2007, at 4:30 AM, Bohaty David wrote:
Hello,
just my though about the draft, related to the requirement
"The client transaction SHOULD start timer D when it enters the
"Completed" state for any reason, with a value of at least 32 seconds
for unreliable transports, and a value of zero seconds for reliable
transports":
For client transactions, wouldn't it be better that the timer D is set
to 32s even for reliable transport after receiving 200-299
response, so
the transaction can collect also responses to a forked INVITE? This
would align the INVITE transaction with the UAC Core behaviour, which
according to "RFC3261 13.2.2.4 2xx Responses" considers the INVITE
transaction completed 64*T1 seconds after the reception of the
first 2xx
response.
Also the 200-299 is retransmitted end-to-end, so the reliability of
the
transport to the first hop does not really mean that the response
or ACK
is sent reliably all the way from UAS to UAC, respectivelly from
UAC to
UAS.
David Bohaty
System Architect
SITRONICS Telecom Solutions, Czech Republic a.s.
Tel.: +420 226 532 578, Fax: +420 241 480 899
BB Centrum - Beta, Vyskocilova 1481/4, 140 00 Praha 4, Czech Republic
www.sitronicsts.com
-----Original Message-----
From: Robert Sparks [mailto:[EMAIL PROTECTED]
Sent: 28 June 2007 04:35
To: SIP IETF
Subject: [Sip] Changes to the INVITE transaction to address bug 769
Everyone -
I've put together a proposal for addressing the spec bug captured at
http://bugs.sipit.net/show_bug.cgi?id=769
Please read through
http://www.ietf.org/internet-drafts/draft-sparks-sip-invfix-00.txt
and comment.
RjS
_______________________________________________
Sip mailing list https://www1.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
_______________________________________________
Sip mailing list https://www1.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
_______________________________________________
Sip mailing list https://www1.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
