PLEASE do NOT send a message to both sip and aip-implementors.
The people that would respond to your query are on both lists,
and it is annoying to get both copies of a request.
If you were to define sip over some other transport, you
would have to include in that definition how it was to
deal with fragmentation. You would not change sip.
Brian
> -----Original Message-----
> From: Takumi Ohba [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 09, 2001 1:07 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [Sip-implementors] RE: [SIP] over-length message
>
>
> Dear all,
>
> Sorry for continuing this topic on this mailing list, but I
> would like to
> confirm one point, which may relate to SIP protocol development.
>
> I understand that SIP over transport protocols using IP has
> no limit, thanks
> to the IP fragmentation function.
> So, SIP has no need to worry about message length if it uses IP based
> transport protocols, but should use TCP if it wants to send
> longer message
> than the path MTU.
> I also understand that supporting IP fragmentation is
> implementation issue.
>
> On the other hand, SIP cannot send too long message over a transport
> protocol that has no fragmentation function, such as MTP or
> signalling AAL.
> However, nobody except me considers that SIP uses such
> transport protocol at
> this stage, and therefore, this is not a problem. In other
> word, it is only
> a future possible problem.
> If we will use such transport protocols, SIP will have to
> care about message
> length and specify something (handling of over length
> message, or message
> segmentation procedures in SIP level).
>
> Is my understanding correct?
>
> Regards,
> Takumi Ohba
>
> ***************************************************
> Takumi OHBA
> NTT Network Service Systems Laboratories
> tel +81 422 59 4405 fax +81 422 59 3494
> e-mail [EMAIL PROTECTED]
> ***************************************************
>
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
