Jonathan,
in principle I agree with you.
However, I would like to know what exactly you connotate by 'barf' - does
it mean the UA crashes, or does it mean it
gracefully declines ?
I have worked with people on the embedded side who simply cannot allocate
more than Xk for SIP messages and
by policy, their application rejects any message greater than this, by
returning a message too long bad response( I think its a 413). While this
may not be desirable, at times it can be a practical limitation.
If the UA crashes, I would say its certainly a no-no. If it declines by
saying 'sorry, I can't handle your message', then its certainly
a scenario that should be still in line. I would say that this approach is
still inter-operable .
Regds
Arjun
--
Arjun Roychowdhury @ Hughes Software Systems
Jonathan Rosenberg <[EMAIL PROTECTED]> on 09/29/2000 03:27:32 AM
To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>, "'sip (E-mail)'"
<[EMAIL PROTECTED]>
cc:
Subject: More arbitrary limits
Folks,
It has just come to my attention that the vendor of a shipping SIP based
system has SIP UAs that barf when a message arrives with more than 9 Via
headers.
Again, I cannot emphasize enough how much of a recipe for disaster this is.
The system will work for small to mid size deployments, and then, all of a
sudden, once we are really rolling, completely break in the middle of an
operational deployment.
I suggest we add this to the torture tests at the bakeoffs.
Thanks,
Jonathan R.
---
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000
http://www.dynamicsoft.com
