here we go... from the "Proxy Behaviour" section

16.3 Request Validation

   1. Reasonable syntax check

      The request MUST be well-formed enough to be handled with a server
      transaction.  Any components involved in the remainder of these
      Request Validation steps or the Request Forwarding section MUST be
      well-formed.  Any other components, well-formed or not, SHOULD be
      ignored and remain unchanged when the message is forwarded.  For
      instance, an element would not reject a request because of a
      malformed Date header field.  Likewise, a proxy would not remove a
      malformed Date header field before forwarding a request.

      This protocol is designed to be extended.  Future extensions may
      define new methods and header fields at any time.  An element MUST
      NOT refuse to proxy a request because it contains a method or
      header field it does not know about.



 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Attila 
Sipos
Sent: 09 February 2009 11:00
To: Iñaki Baz Castillo
Cc: [email protected]
Subject: Re: [Sip-implementors] "Reason-Header" inCANCELthroughvariousproxies

I think it's in RFC 3261 in the proxy section.
I'll have to look.

But it's like the general rule for UA:
It a UA doesn't understand a header it should ignore it.




 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Iñaki Baz 
Castillo
Sent: 09 February 2009 10:54
Cc: [email protected]
Subject: Re: [Sip-implementors] "Reason-Header" in CANCELthroughvariousproxies

2009/2/9 Attila Sipos <[email protected]>:
> Yes,
>
> Proxies should respect ALL headers.
>
> Or more generally, if a proxy doesn't understand a header it should 
> forward it on.
>
> This is the only way for SIP to work for future headers.

Where is it specified? I'd like to know it in order to report it to some proxy 
implementations.

--
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to