[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    [Sip-implementors] Clarification needed in RFC3261
From:       "nabeel mohamed" <freakynab () gmail ! com>
Date:       2007-10-31 23:13:21
Message-ID: 360c922a0710311601o5e9e83csa156e8ab62883a64 () mail ! gmail ! com
[Download RAW message or body]

Hi all,

Can you clarify me the below questions,

1/ What provision should the SIP stack provide in handling ICMP error
responses, received for the
    request sent ?

    RFC 3261 says, that the unreachable ICMP responses should be
passed to the user agent and
    other responses like(TTL exceeded, parameter problem) should be ignored.

    How should we go about in implementing the above ?

2/ Are there any defined restrictions on the maximum length of URI,
userinfo, request/status line, each
   header line, message body, whole message etc. ?

3/ From RFC 3261,

    "If the transport packet ends before the end of the message body,
this is considered an error.  If the
     message is a response, it MUST be discarded.  If the message is a
request, the element SHOULD
     generate a 400 (Bad Request) response."

     Can the parser module auto-correct the Content-Length according
to the message body and send
     it upwards, instead of discarding/generating 400 response in case
of response/request ?

Thanks & Regards,
Nabeel

[prev in list] [next in list] [prev in thread] [next in thread]