Re: [hybi] WS port with BOSH-like fallback?

"Alakkad, Achuth (GE Healthcare)" <Achuth.Alakkad@ge.com> Mon, 29 November 2010 09:13 UTC

Return-Path: <Achuth.Alakkad@ge.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D85413A6B49 for <hybi@core3.amsl.com>; Mon, 29 Nov 2010 01:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMhNeoEjCAip for <hybi@core3.amsl.com>; Mon, 29 Nov 2010 01:13:26 -0800 (PST)
Received: from exprod5og103.obsmtp.com (exprod5og103.obsmtp.com [64.18.0.145]) by core3.amsl.com (Postfix) with ESMTP id B92E43A6B4E for <hybi@ietf.org>; Mon, 29 Nov 2010 01:13:25 -0800 (PST)
Received: from source ([4.78.218.129]) (using TLSv1) by exprod5ob103.postini.com ([64.18.4.12]) with SMTP ID DSNKTPNu+p1JnGzKOI0gWSQ3Z9DqUJXKZf+w@postini.com; Mon, 29 Nov 2010 01:14:35 PST
Received: from unknown (HELO alpmlef06.e2k.ad.ge.com) ([3.159.18.15]) by Cinmlip07.e2k.ad.ge.com with ESMTP; 29 Nov 2010 04:14:34 -0500
Received: from BANMLVEM07.e2k.ad.ge.com ([3.159.220.56]) by alpmlef06.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 29 Nov 2010 04:14:33 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB8FA5.D4117FB9"
Date: Mon, 29 Nov 2010 14:44:03 +0530
Message-ID: <4590EC7E9324CF43A2B37F81AFD6357007BB59B9@BANMLVEM07.e2k.ad.ge.com>
In-Reply-To: <AANLkTi=UpWdjqU0Lkh11wSGtHVDO71_CvjWJyH4mPyQi@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [hybi] WS port with BOSH-like fallback?
thread-index: AcuPVufkaE7fzo39Qcmx7KMlSnSMQwATdoKw
References: <AANLkTi=UpWdjqU0Lkh11wSGtHVDO71_CvjWJyH4mPyQi@mail.gmail.com>
From: "Alakkad, Achuth (GE Healthcare)" <Achuth.Alakkad@ge.com>
To: Greg Wilkins <gregw@intalio.com>, Hybi <hybi@ietf.org>
X-OriginalArrivalTime: 29 Nov 2010 09:14:33.0267 (UTC) FILETIME=[D5FCA030:01CB8FA5]
Subject: Re: [hybi] WS port with BOSH-like fallback?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Nov 2010 09:13:27 -0000

To me the main advantage of websocket is that, it makes use of exisiting
accepted port (80). Thus not affecting any intermediatory devices, such
as firewal configuration. If we are going to go with an independent port
for websockets, then will it start of a monotonous rework for those
devices ( like firewall, proxy etc..).


________________________________

From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
Greg Wilkins
Sent: Monday, November 29, 2010 5:19 AM
To: Hybi
Subject: [hybi] WS port with BOSH-like fallback?



So tell me again why we don't just ask IANA for a websocket port?

Browsers can try to port and if it fails to connect they can fall back
to something like BOSH over port 80.
This get's us through firewalls and keep port 80 for HTTP.

I think that is the right technical solution (use ports for what ports
were designed for) and avoids the growing conflict over usage of port
80.

cheers