[core] Mail regarding draft-zcao-core-speedy-blocktran
Jim Schaad <ietf@augustcellars.com> Fri, 29 March 2019 19:34 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3741202DA; Fri, 29 Mar 2019 12:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 biMHZUXaKjnK; Fri, 29 Mar 2019 12:34:40 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776AB120304; Fri, 29 Mar 2019 12:34:37 -0700 (PDT)
Received: from Jude (62.168.35.125) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 29 Mar 2019 12:34:31 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: draft-zcao-core-speedy-blocktran@ietf.org
CC: core@ietf.org
Date: Fri, 29 Mar 2019 20:34:25 +0100
Message-ID: <012e01d4e666$6d291a90$477b4fb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdTmZZECUL3REi7MT9avKUcTbpATeA==
Content-Language: en-us
X-Originating-IP: [62.168.35.125]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/7L3usuYPvkdooaLyR7oRCUINmBw>
Subject: [core] Mail regarding draft-zcao-core-speedy-blocktran
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Mar 2019 19:34:43 -0000
In today's F2F meeting one of the reasons for doing this that was brought up was that this would be more efficient under a TCP situation. I would like to point out that the BERT extension in the TCP (Section 6 of RFC 8323) is designed so that multiples of 1024B blocks can be sent as a single block operation. Additionally, it would be possible to just get an entire huge response in a single GET although this may cause problems with the network processing for the device. For these reasons I do not believe that this is a protocol that should ever be thought of as running over a reliable transport. Much better options already exist. Jim