Re: [rtcweb] Opening unordered data channel issue

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 22 August 2013 18:24 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A51E111E81DC for <rtcweb@ietfa.amsl.com>; Thu, 22 Aug 2013 11:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.479
X-Spam-Level:
X-Spam-Status: No, score=-110.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 241XH6d9pOo8 for <rtcweb@ietfa.amsl.com>; Thu, 22 Aug 2013 11:24:05 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 8991B11E81C5 for <rtcweb@ietf.org>; Thu, 22 Aug 2013 11:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=345; q=dns/txt; s=iport; t=1377195843; x=1378405443; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=VOIWD2EsSHzbx98OiIDbAII6OKXDDzCbEIt8PDW8M74=; b=aXHm2xnoP5SytoUWkEnjO5/782xg1f/IL9pzxsyj2lzaN+DyqUI2CGc8 nt7eofp1RREEIBbAqp5+tdFhx+guxs1QEPGA54XZ79dXX5x0D/uXevZ8d uPNAWg8hSMyJpCJcPD4Q19GQ9ekJ6hJzTXke2UXlX/BbqTJ0b8G5ymAjB 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQFANRWFlKtJXHB/2dsb2JhbABagweBBoJUvTSBHRZ0giQBAQEDATo/BQsCAQgOFBQQMiUCBA4FCIgCBrcBkDMCMQeDG3sDqUCDH4Ir
X-IronPort-AV: E=Sophos;i="4.89,935,1367971200"; d="scan'208";a="250585836"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-5.cisco.com with ESMTP; 22 Aug 2013 18:24:03 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r7MIO2YQ007065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 22 Aug 2013 18:24:02 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.221]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Thu, 22 Aug 2013 13:24:02 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [rtcweb] Opening unordered data channel issue
Thread-Index: AQHOn2TG7XWf5uzJ2k2e0ui0oC+xmQ==
Date: Thu, 22 Aug 2013 18:24:02 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB114920305@xmb-aln-x02.cisco.com>
References: <EA6D9D69-7A0C-4215-8561-04D9FF7BD868@lurchi.franken.de> <CAOJ7v-2BwXLfyTaqmqJGe2wyWQKO-xTBpe-9gBwyBwuDoy337A@mail.gmail.com>
In-Reply-To: <CAOJ7v-2BwXLfyTaqmqJGe2wyWQKO-xTBpe-9gBwyBwuDoy337A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <98BC23A26EDFDE459B0E32385AADB109@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Opening unordered data channel issue
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 18:24:11 -0000

On Aug 22, 2013, at 11:12 AM, Justin Uberti <juberti@google.com> wrote:

> I agree that b) is the cleanest choice. While this makes the handshake 2-way, it does not suffer from the performance issues that affected the previous 2- and 3-way handshake proposals, since data can be sent immediately without waiting for the ACK.

+1