Dale Worley wrote:
On Fri, 2009-02-13 at 10:40 -0600, Vijay K. Gurbani wrote:
Next, the main area of discussion in the thread was what
constitutes a message in the context of CLF logging: is
it how rfc3261 describes it? That is, a SIP request is
one message, a response is another message, and so on?
Or does message = SIP request +
0 or more provisional responses +
1 final response
"1 or more final responses"!
Or should that be "0 or more final responses", since we might not
receive a final response?
Pedantically speaking, it should be "0 or 1 final response".
Under what condition would you get more than 1 final response
for the same transaction from a downstream forking proxy?
IIRC, we had a corner case in rfc2543 where proxies used to
forward a 6xx or a 2xx upstream immediately, whichever came
first. So, if a 6xx came first and was forwarded, a 2xx
would also be forwarded if it arrived after the 6xx (since a
2xx-class response cannot be quashed at a proxy.) This corner
case was fixed in rfc3261, so I'd be surprised if a rfc3261
forking proxy sends multiple final responses upstream.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
