Adam B. Roach ([EMAIL PROTECTED]):
> Due to the wide number of people attending this most recent
> bakeoff, it is virtually assured that no-one got around to
> testing with every implementation there. To that end, I'd
> like to share some lessons learned from our interop tests.
> These are't aimed at any teams in particular; I'm only
> including issues I saw in at least two different implementations.
>
> [...]
>
> 2) Many proxy implementations were doing overaggressive parsing.
> While the performance implications of this don't affect
> the other nodes in the network, the interoperability issues
> it introduces do cause problems. In keeping with the
> premise of "be strict in what you generate, but forgiving
> in what you accept," I strongly recommend that you don't
> validate fields unless you intend to use the information
> contained in them.
>
> [...]
I'd like to add to this thought that many user agents were also doing
overaggressive parsing. For example, many failed on this User-Agent
header I supplied:
User-Agent: [[: i:n:s:i:p:i:d :]]
Yes, [:] are all not allowed in a User-Agent header according to the
HTTP spec, however I don't see this as being reason enough to drop the
packet or even return an error code.
> 4) SDP is still causing some problems. The most common problems
> I'm seeing are still:
>
> - failure to include a t= line
Your implementation shouldn't rely on one being there.
--
Billy Biggs [EMAIL PROTECTED]
http://www.div8.net/billy [EMAIL PROTECTED]
