RE: [Sip] MAJOR Open Issue #184: Message size limitations

[John.Hearty@Level3.com]

> -----Original Message-----
> From: Bobby Sardana [mailto:sardana@obsoft.com]
> Sent: Thursday, January 03, 2002 12:32 AM
> To: Juha Heinanen
> Cc: Jonathan Rosenberg; Dean Willis; Michael Thomas; Hearty, John;
> sip@ietf.org
> Subject: Re: [Sip] MAJOR Open Issue #184: Message size limitations
> 
> 
> From an implementation's perspective, co-orelating responses 
> from different
> transport types can lead to bulky UA implementations.
> 
> A simple methodology, if TCP/UDP support is needed in SIP, would be:
> 
> a. Use the same transport type for all downstream/upstream 
> communication.

 I am NOT in favor of this.  Some network architectures rely on secure
relationships between elements.  The transport used up to that point can't
override that relationship, i.e. expect UDP to work between two proxies that
normally only talk TLS to each other.

> b. When in doubt, use TCP.
> 
> If we are planning to mix request/responses using TCP/UDP, 
> then mandate only one
> and deprecate the other.
> 
> Regards,
> 
> Bobby Sardana.
> sardana@obsoft.com
> 
> Juha Heinanen wrote:
> 
> > Bobby Sardana writes:
> >
> >  > Just curious, why can't the 499 be propagated all the 
> way to the UAC with
> >  > no intermediary (proxy) storage of responses? So if the 
> request originated
> >  > as UDP and the UAS cannot handle it, because of size 
> limitations, and
> >  > requires that a TCP request be made, just reject the 
> request and propagate
> >  > it (like some other errors) back to the UAC. The UAC can 
> then originate a
> >  > TCP request.
> >
> > just to ask again, why can't the uas use tcp to send the 
> response even
> > if it got the request using udp?  sip should care what the transport
> > protocol is.
> >
> > -- juha
> 

_______________________________________________
Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip