Its not clear what your goals are. Are you making a stack just for an
intermediary?
The key is that if a header is unknown then you can't do any meaningful
processing on it. So if you are proxying you can copy it along and that
is about all. If you are a UAS and you don't know it then all you can do
is ignore it.
There is a possibility that the application on top of the stack
understands the header but the stack does not. That becomes an issue for
stack design. You can provide a means for the stack to present the
unknown headers to the application in a way that allows the application
to meaningfully process them. Or you can provide the application with a
way to extend the stack's knowledge to encompass new headers.
Paul
Iñaki Baz Castillo wrote:
> El Tuesday 25 March 2008 12:41:10 [EMAIL PROTECTED] escribió:
>> Hi Iñaki,
>>
>> The custom headers are of interest to particular implementation. It depends
>> on how you interpret multiple custom header line with same header name. if
>> you process like list, it would be similar to list else overwritten with
>> last header value. AFAIK, 3261 does not mandate on custom headers.
>>
>> It would never be an issue for any intermediary entities, since they just
>> relay as it is or drop it completely based on the role they play (proxy,
>> b2bua, ...)
>
> Ok, so I just will do the multi-header parsing for known headers using it
> (Via, Route...).
>
> Thanks.
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
