Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-transports-14
Harald Alvestrand <harald@alvestrand.no> Sat, 09 July 2016 21:27 UTC
Return-Path: <harald@alvestrand.no>
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 4055B12D149 for <rtcweb@ietfa.amsl.com>; Sat, 9 Jul 2016 14:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.287
X-Spam-Level:
X-Spam-Status: No, score=-1.287 tagged_above=-999 required=5 tests=[RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8jVGZrrcjlT for <rtcweb@ietfa.amsl.com>; Sat, 9 Jul 2016 14:27:45 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CF1212B01E for <rtcweb@ietf.org>; Sat, 9 Jul 2016 14:27:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 131397C8A85; Sat, 9 Jul 2016 23:27:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtGHmY5Qetnd; Sat, 9 Jul 2016 23:27:42 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:1:8c38:e853:481d:3a13] (unknown [IPv6:2001:470:de0a:1:8c38:e853:481d:3a13]) by mork.alvestrand.no (Postfix) with ESMTPSA id E89557C8A84; Sat, 9 Jul 2016 23:27:41 +0200 (CEST)
To: Alissa Cooper <alissa@cooperw.in>, rtcweb@ietf.org
References: <F0709916-B88F-44C3-A5F4-6007E825F192@cooperw.in>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <57816C4D.5030609@alvestrand.no>
Date: Sat, 09 Jul 2016 23:27:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <F0709916-B88F-44C3-A5F4-6007E825F192@cooperw.in>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/9-DQNO5JZP_HPoOMRgic5rr0x6I>
Subject: Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-transports-14
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 09 Jul 2016 21:27:47 -0000
Thank you - I have filed this review as https://github.com/rtcweb-wg/rtcweb-transport/issues/21 and will address it after the Last Call ends. Den 07. juli 2016 23:33, skrev Alissa Cooper: > I have reviewed this document in preparation for IETF last call. It is in good shape and I have requested the last call. > > While the last call is ongoing, I would like to double-check that this document (particularly Section 4) raises no new security considerations that should be documented in Section 6. I'm wondering if there are scenarios where a malicious application could try to game the priority scheme to some ill effect? draft-ietf-tsvwg-rtcweb-qos talks a bit about this, so I'm wondering if anything needs to be said here. > > And I found a couple of nits to be resolved together with any LC comments: > > - Sec 3.2 - Please update the citation to point to draft-ietf-mmusic-ice-dualstack-fairness-02. > > - Sec 3.4 - > > "Third, using TCP only between the endpoint and its relay may result > in less issues with TCP in regards to real-time constraints, e.g. due > to head of line blocking." > > This is awkwardly phrased. I would suggest something like "Third, using TCP between the client's TURN server and its peer may result in more performance problems (due to head-of-line blocking) than using UDP." > > Alissa > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb >
- Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-tra… Harald Alvestrand
- Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-tra… Alissa Cooper
- [rtcweb] AD evaluation: draft-ietf-rtcweb-transpo… Alissa Cooper