RE: [Sip] Re: issue with oubound and the used transport protocol

"Frank W. Miller" <fwmiller@cornfed.com> Thu, 30 November 2006 20:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpsl9-0005Qz-4b; Thu, 30 Nov 2006 15:43:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpsl7-0005Qt-To for sip@ietf.org; Thu, 30 Nov 2006 15:43:53 -0500
Received: from celine.siteprotect.com ([64.26.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gpsl3-0001gl-By for sip@ietf.org; Thu, 30 Nov 2006 15:43:53 -0500
Received: from cornfed (c-24-9-79-73.hsd1.co.comcast.net [24.9.79.73]) by celine.siteprotect.com (8.11.6/8.11.6) with ESMTP id kAUKfQL22683; Thu, 30 Nov 2006 14:41:26 -0600
Message-Id: <200611302041.kAUKfQL22683@celine.siteprotect.com>
From: "Frank W. Miller" <fwmiller@cornfed.com>
To: 'Francois Audet' <audet@nortel.com>, 'Fredrik Thulin' <ft@it.su.se>, sip@ietf.org, rohan@ekabal.com
Subject: RE: [Sip] Re: issue with oubound and the used transport protocol
Date: Thu, 30 Nov 2006 13:41:20 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AccUrG6zKoIal/J8TPaXiSc5msUvCQACW5GAAAJw6gA=
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF0E379DE1@zrc2hxm0.corp.nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc:
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

As an aside, the draft draft-fwmiller-ping-03 has expired.  While the draft
is still available at http://www.cornfed.com/ping.html and
http://www.cornfed.com/ping.txt, the question is whether it should be
resubmitted?  If there is no interest in it, I'll let it die on the IETF
site.

Thanks,
FM



-----Original Message-----
From: Francois Audet [mailto:audet@nortel.com] 
Sent: Thursday, November 30, 2006 12:38 PM
To: Fredrik Thulin; sip@ietf.org; rohan@ekabal.com
Subject: RE: [Sip] Re: issue with oubound and the used transport protocol

Just to be clear what my opinion is...

I agree with you that using CRLF with TCP would
be a lot cleaner and easier to implement. It would really make
the UDP-with-STUN alternative a moot point.

That combined with people moving to TLS/TCP for security 
reasons in my opinion means that having focused our energies on
a solution optimized for UDP was a big mistake.

The consequence is the plethora of mechanisms that people are
using today: PING, OPTIONS, CRLF, REGISTER, etc.

But in my opinion, getting the document finalized should be the
ultimate priority.


> -----Original Message-----
> From: Fredrik Thulin [mailto:ft@it.su.se] 
> Sent: Thursday, November 30, 2006 10:21
> To: Audet, Francois (SC100:3055)
> Cc: sip@ietf.org; rohan@ekabal.com
> Subject: Re: [Sip] Re: issue with oubound and the used 
> transport protocol
> 
> Francois Audet wrote:
> > Didn't we agree way back NOT to use PING, CRLF, etc., and use STUN 
> > instead?
> > 
> > Why is this debate being re-opened?
> 
> Because it seems more and more (to me at least) that Outbound 
> with UDP will just suck.
> 
> If Outbound UA's have to get their act together and implement 
> TLS/TCP, then we can simplify Outbound even further by 
> skipping the whole STUN keepalive thing, and go with CRLF 
> over TLS/TCP.
> 
> I am very much in favor of cutting both UDP and STUN 
> keepalives out of Outbound. I think that would lead to faster 
> deployment, and also make the world a better place by 
> eliminating some SIP over UDP.
> 
> /Fredrik
> 
> PS. By the way, when people say CRLF keepalives, do you mean 
> CRLF sent only from the UA, or CRLF from UA to edge proxy 
> followed by CRLF in the reverse direction too?
> 
> 
> 

_______________________________________________
Sip mailing list  https://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


_______________________________________________
Sip mailing list  https://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