On Fri, Sep 30, 2016 at 2:03 PM, Paul Kyzivat <[email protected]> wrote:
> The inclusion of generic-param is a provision for future extensions with > backward compatibility. It doesn't mean that anybody is *permitted* to add > whatever they want. (It takes a published RFC to validly define a new > header field parameter.) So if you *insert* values that haven't been > properly defined and registered then you are violating the specs. This interpretation would break a lot of SIP implementations. The reason for this is that Via and Route generic parameters are used by stateless proxies to store application specific state. There is no other place to put it. Skype for business was one example. I can probably find another 10-15 examples similar to that from other products. Regards, _____________ Roman Shpount _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
