Comments inline...

Thanks & Regards,
Nataraju A.B.
-----Original Message-----
From: Praveen [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 06, 2006 11:07 AM
To: Nataraju A B
Cc: [email protected]
Subject: Re: [Sip-implementors] Malformed headers in SIP response

Hi,
           In case of optional we may ignore, but for some cases they
are
mentioned as conditional. For eg: Replaces header.
Do we need to ignore the conditional cases also, say incase of Replaces
only
?
[ABN] RFC does not say (I am not sure about this fact) exactly how to
handle when particular parameter is in error (I mean to discard the
message as a whole or header only or only parameter...), for a good
stack, I feel just discard only that particular parameter (if the error
is in some parameter parsing) is a better option... if that information
is mandatory for that particular header then you cal assume that header
not been received... 

Nataraju A B wrote:

> Comments inline...
>
> Thanks & Regards,
> Nataraju A.B.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Praveen
> Sent: Thursday, January 05, 2006 9:49 AM
> To: [email protected]
> Subject: [Sip-implementors] Malformed headers in SIP response
>
> Hi,
>             As per sec 8.2.2, RFC3261, UAS should ignore any malformed
> headers that are not necessary for processing requests.
> What about the same for in case of Responses. We should ignore or not
?
>
> [ABN] yes, you need to ignore the headers you don't understand... as
if
> those headers were not there in the response at all... the importance
of
> particular header differ from one request to other. (for instance
> contact header in 2xx of INV is mandatory whereas in OPTIONS or some
> other message its an optional header... )
>
> Thanks,
> praveen
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


The information contained in this e-mail message and/or attachments to
it
  may
contain confidential or privileged information. If you are not the
intended
  recipient, any dissemination, use, review, distribution, printing or
  copying of the information contained in this e-mail message and/or
  attachments to it are strictly prohibited. If you have received this
  communication in error, please notify us by reply e-mail immediately
and
  permanently delete the message and any attachments.

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

Reply via email to