[SIPForum-techwg] TCP vs. UDP (actually, SIPconnect does *not* change SIP)

[Elwell, John]

> -----Original Message-----
> From: techwg-bounces at sipforum.org 
> [mailto:techwg-bounces at sipforum.org] On Behalf Of Francois Audet
> Sent: 19 May 2008 17:19
> To: Eric Burger; Richard Shockey
> Cc: techwg at sipforum.org
> Subject: Re: [SIPForum-techwg] TCP vs. UDP 
> (actually,SIPconnect does *not* change SIP)
> 
> To be clear:
> 
> 1) I prefer MUST TCP
> 2) I am ok with MUST TCP, MUST UDP, strongly RECOMMEND TCP
[JRE] Eric is trying to avoid RECOMMEND, MAY, SHOULD etc. To stand the
best chance of interoperability I agree we should avoid such options. I
prefer MUST TCP - market forces will require people to implement UDP
too, but there is no need for SIPConnect to specify UDP, and no need to
test UDP for SIPConnect compliance.

John

> 
> > -----Original Message-----
> > From: techwg-bounces at sipforum.org 
> > [mailto:techwg-bounces at sipforum.org] On Behalf Of Eric Burger
> > Sent: Sunday, May 18, 2008 11:15
> > To: Richard Shockey
> > Cc: techwg at sipforum.org
> > Subject: Re: [SIPForum-techwg] TCP vs. UDP (actually, 
> > SIPconnect does *not* change SIP)
> > 
> > (1) I think you mean TCP is the default.
> > 
> > (2) What do we gain by mentioning UDP at all?  If there are 
> > 507 test cases for SIPconnect stuff, mentioning UDP means 
> > there are now 1014 test cases (507 for SIPconnect with TCP, 
> > 507 for SIPconnect with UDP).
> > 
> > Yes, not mentioning UDP, but still supporting RFC 3261, means 
> > you don't get to not do UDP.  However, it makes SIPconnect 
> > compliance testing and verification much easier.
> > 
> > [507 is just a random number; pick your guess as to what is 
> > the right number.  The factor of two does not go away.]
> > 
> > 
> > On May 18, 2008, at 1:36 PM, Richard Shockey wrote:
> > 
> > >
> > >>
> > >> I agree.  This was my concern when I read MUST TCP, but 
> > only MAY UDP 
> > >> in the document.
> > >>
> > >> I believe it is perfectly acceptable to say that 
> > SIPconnect compliant 
> > >> devices MUST support TCP, but there are a lot of UDP only 
> > devices in 
> > >> use within networks right now.  These need to keep working when 
> > >> connected with SIPconnect 1.1 compliant devices or no 
> > enterprise or 
> > >> service provider will have any interest in it.
> > >>
> > >> To my mind that means that both TCP and UDP are MUSTs.  
> > But, perhaps 
> > >> TCP should be RECOMMENDed as the default transport (with 
> UDP as a 
> > >> fall- back)?
> > >
> > >
> > > Chair hat off. Yes .. both are MUST but STRONGLY 
> > RECOMMENDED that UDP 
> > > is the default.
> > >
> > >
> > >>
> > >> Regards,
> > >>
> > >> Peter
> > >>
> > >
> > > _______________________________________________
> > > techwg mailing list
> > > Send mail to: techwg at sipforum.org
> > > Unsubscribe or edit options at:  
> > > http://sipforum.org/mailman/listinfo/techwg
> > 
> > _______________________________________________
> > techwg mailing list
> > Send mail to: techwg at sipforum.org
> > Unsubscribe or edit options at:  
> > http://sipforum.org/mailman/listinfo/techwg
> > 
> 
> _______________________________________________
> techwg mailing list
> Send mail to: techwg at sipforum.org
> Unsubscribe or edit options at:  
> http://sipforum.org/mailman/listinfo/techwg
>