Adam Roach wrote:
Why are they parsing anything but the topmost Via header field? It seems a waste of processing time to parse the entire stack of Vias.

Some implementations that do loop detection tend to parse all
the Vias in an incoming request; the more intelligent ones tend
to scan for a Via they may have inserted earlier and only parse
that one.

Implementations, unfortunately, differ in how much of the Via
stack they will parse.  I want to ensure that, at the very least,
the implementations do not automatically reject a message because
of this particular issue.

Also -- and this just struck me after sending the email out --
there are a couple of postings on the list that make a case
for the current "received" parameter being broken as per the
ABNF.  Please see

http://www1.ietf.org/mail-archive/web/sipping/current/msg10788.html
http://www1.ietf.org/mail-archive/web/sipping/current/msg10373.html

Thanks,

- vijay
--
Vijay K. Gurbani  [EMAIL PROTECTED],research.bell-labs.com,acm.org}
Bell Laboratories, Lucent Technologies, Inc.
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to