athan; Alex Balashov
> Cc: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] SIP Stacks - large UDP messages
>
> >>Usually it is simpler to implement the following strategy:
> >>
> >> - If the message is below 64K, send the message using UD
>>Usually it is simpler to implement the following strategy:
>>
>> - If the message is below 64K, send the message using UDP.
>> - If the UDP transaction times out, try TCP transport.
Simple, yes.
But bad also.
Why do people want to use UDP for large messages?
It's a great way to block things u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2010 09:15 AM, Iñaki Baz Castillo wrote:
> 2010/10/12 Marc Petit-Huguenin :
>
>> No, I do not, quite the opposite in fact. But I really wish that SIP
>> authors,
>> either for proprietary or FOSS stack (and this apply in fact for all Intern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/12/2010 07:45 AM, Iñaki Baz Castillo wrote:
> 2009/5/19 Marc Petit-Huguenin :
>> I mean a professional grade SIP stack, not the toy stacks
>> that you can download on the Internet
>
> Your vision is really "great". It seems that your are proud o
2010/10/12 M. Ranganathan :
>>> IMHO this is an exotic specification. What about if the
>>> proxy/registart has to route a long request to a user registered in a
>>> UDP location? should the proxy try TCP? to which port? what about NAT?
>>> So this is a so exotic "feature" that I strongly understan
On Tue, Oct 12, 2010 at 4:06 PM, Alex Balashov
wrote:
> On 10/12/2010 12:15 PM, Iñaki Baz Castillo wrote:
>
>> Second paragraph of Section 18.1.1 of RFC 3261:
>>
>> -
>> If a request is within 200 bytes of the path MTU, or if it is larger
>> than 1300 bytes and the path MTU
On Tue, Oct 12, 2010 at 11:36 AM, Iñaki Baz Castillo wrote:
> 2010/10/12 M. Ranganathan :
>
>> But let me ask
>>> you a question: Do you know XMPP protocol? There are hundreds of
>>> *good* XMPP implementations "available in internet" licensed as free
>>> software, and most of them interoperate v
On 10/12/2010 12:15 PM, Iñaki Baz Castillo wrote:
> Second paragraph of Section 18.1.1 of RFC 3261:
>
> -
> If a request is within 200 bytes of the path MTU, or if it is larger
> than 1300 bytes and the path MTU is unknown, the request MUST be sent
> using an RFC 2914 [43]
2010/10/12 Marc Petit-Huguenin :
> And this is where implementers can really help, by participating in the
> discussion of the specifications. This is what I did for TURN - I implemented
> it from scratch 3 times during the long gestation of the I-D, and continuously
> reported issues.
And that i
2010/10/12 Marc Petit-Huguenin :
> No, I do not, quite the opposite in fact. But I really wish that SIP authors,
> either for proprietary or FOSS stack (and this apply in fact for all Internet
> protocols) really read and implement the RFCs, instead of cherry-picking what
> they like or not in th
2010/10/12 M. Ranganathan :
> But let me ask
>> you a question: Do you know XMPP protocol? There are hundreds of
>> *good* XMPP implementations "available in internet" licensed as free
>> software, and most of them interoperate very well with each other.
>
>
> XMPP is much simpler than SIP and it
On Tue, Oct 12, 2010 at 10:45 AM, Iñaki Baz Castillo wrote:
> 2009/5/19 Marc Petit-Huguenin :
>> I mean a professional grade SIP stack, not the toy stacks
>> that you can download on the Internet
>
> Your vision is really "great". It seems that your are proud of SIP
> being so difficult to impleme
2009/5/19 Marc Petit-Huguenin :
> I mean a professional grade SIP stack, not the toy stacks
> that you can download on the Internet
Your vision is really "great". It seems that your are proud of SIP
being so difficult to implement, and perhaps you think that SIP is
just for big vendors (those who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2010 11:06 AM, M. Ranganathan wrote:
> On Tue, May 19, 2009 at 1:57 PM, Marc Petit-Huguenin wrote:
>> Alex Balashov wrote:
>>> The RFCs are fairly
>>>
Any of you are aware of literature on how to write SIP stacks besides the
documen
On Tue, Oct 5, 2010 at 3:20 PM, Marc Petit-Huguenin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/05/2010 11:06 AM, M. Ranganathan wrote:
>> On Tue, May 19, 2009 at 1:57 PM, Marc Petit-Huguenin
>> wrote:
>>> Alex Balashov wrote:
The RFCs are fairly
> Any of you
On Tue, May 19, 2009 at 1:57 PM, Marc Petit-Huguenin wrote:
> Alex Balashov wrote:
>> The RFCs are fairly
>>
>>> Any of you are aware of literature on how to write SIP stacks besides the
>>> documentation provided by open source SIP stacks?
>>
>> The RFCs are fairly exacting and rigourous on the t
Hi,
You can also try doubango (http://doubango.org/).
Android demo project: http://code.google.com/p/imsdroid/
iOS demo project: http://code.google.com/p/idoubs/
Regards,
--- En date de : Mer 20.5.09, Mike Coffee a écrit :
De: Mike Coffee
Objet: Re: [Sip-implementors] SIP Stacks
À: "
Well I agree that its not an easy task but its achievable. If you are
spending a good quality time in understanding open source SIP stacks and
writing applications on top of it, you may as well try to figure out how it
is designed and developed in that process. At the worst if I may not end up
dev
Paul Kyzivat wrote:
>
> cool goose wrote:
>> Thanks All for pointing me towards some resources. I have never written any
>> protocol stacks before except for few small SIP tools. This would be my
>> first time writing a SIP stack and that's where I felt a need for some
>> literature or books on de
)
Subject: Re: [Sip-implementors] SIP Stacks
El Miércoles, 20 de Mayo de 2009, Paul Kyzivat escribió:
> cool goose wrote:
> > Thanks All for pointing me towards some resources. I h
El Miércoles, 20 de Mayo de 2009, Paul Kyzivat escribió:
> cool goose wrote:
> > Thanks All for pointing me towards some resources. I have never written
> > any protocol stacks before except for few small SIP tools. This would be
> > my first time writing a SIP stack and that's where I felt a need
cool goose wrote:
> Thanks All for pointing me towards some resources. I have never written any
> protocol stacks before except for few small SIP tools. This would be my
> first time writing a SIP stack and that's where I felt a need for some
> literature or books on designing protocol stacks. An
Thanks All for pointing me towards some resources. I have never written any
protocol stacks before except for few small SIP tools. This would be my
first time writing a SIP stack and that's where I felt a need for some
literature or books on designing protocol stacks. Anyways, if I run into
somethi
> > Any of you are aware of literature on how to write SIP stacks
> > besides the documentation provided by open source SIP stacks?
>
> I mean any literature discussing the architecture and design patterns
> used in the stack development.
I'm sure that you can find plenty with your favorite sear
Alex Balashov wrote:
> The RFCs are fairly
>
>> Any of you are aware of literature on how to write SIP stacks besides the
>> documentation provided by open source SIP stacks?
>
> The RFCs are fairly exacting and rigourous on the topic of the layers of
> abstraction required on the implementationa
--Original Message-
> > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
> > implementors-boun...@lists.cs.columbia.edu] On Behalf Of cool goose
> > Sent: Tuesday, May 19, 2009 1:00 PM
> > To: sip-implementors@lists.cs.columbia.edu
> > Subject: [Sip-imple
The RFCs are fairly
> Any of you are aware of literature on how to write SIP stacks besides the
> documentation provided by open source SIP stacks?
The RFCs are fairly exacting and rigourous on the topic of the layers of
abstraction required on the implementational level.
--
Alex Balashov
Eva
sday, May 19, 2009 1:00 PM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: [Sip-implementors] SIP Stacks
>
> Hi Guys,
>
> Any of you are aware of literature on how to write SIP stacks besides the
> documentation provided by open source SIP st
Hi Guys,
Any of you are aware of literature on how to write SIP stacks besides the
documentation provided by open source SIP stacks?
Thank You,
CoolGoose.
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia
29 matches
Mail list logo
