Re: [core] #409 (block): CoAP over TCP: Multiple Simultaneous TCP Connections

"weigengyu" <weigengyu@bupt.edu.cn> Sun, 08 May 2016 04:11 UTC

Return-Path: <weigengyu@bupt.edu.cn>
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 4A71412D1E1 for <core@ietfa.amsl.com>; Sat, 7 May 2016 21:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.559
X-Spam-Level:
X-Spam-Status: No, score=-0.559 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] 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 vh24xtdgu88g for <core@ietfa.amsl.com>; Sat, 7 May 2016 21:11:04 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8B46212B029 for <core@ietf.org>; Sat, 7 May 2016 21:11:02 -0700 (PDT)
Received: from mx1.bupt.edu.cn (unknown [127.0.0.1]) by mx1.bupt.edu.cn (AnyMacro(G7)) with SMTP id 0E0A219F3EA for <core@ietf.org>; Sun, 8 May 2016 12:11:01 +0800 (HKT)
Received: from WeiGengyuPC (unknown [114.254.85.28]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id D9B2A19F390; Sun, 8 May 2016 12:11:00 +0800 (HKT)
Message-ID: <FF92F5B995FF4B4184ED7DD3E06A860E@WeiGengyuPC>
From: weigengyu <weigengyu@bupt.edu.cn>
To: trac+core@zinfandel.tools.ietf.org, draft-ietf-core-block@tools.ietf.org, Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <065.865b9837ab99aed6c309ae6125f98820@trac.tools.ietf.org> <B3ED15D3873E403990D707DBF79FF1DC@WeiGengyuPC> <572B099D.2080606@gmx.net>
In-Reply-To: <572B099D.2080606@gmx.net>
Date: Sun, 08 May 2016 12:11:00 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/5awph6w_Uh44xaOCsNLhekSnXMU>
Cc: core@ietf.org
Subject: Re: [core] #409 (block): CoAP over TCP: Multiple Simultaneous TCP Connections
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 08 May 2016 04:11:06 -0000

Hi Hannes,

Ciao Hannes wrote:
> Hi Gengyu,
> thanks for your input.

> In the issue I added to the tracker I raised two issues, namely
> 1) "What should the CoAP over TCP state regarding the use of multiple TCP 
> connections?"
> It seems you are arguing that nothing should be said about that topic.

My suggestion is that CoAP does not need to touch the issure using mutliple 
TCP connections.
The reason is to refer P2P software in which it is the application software 
to do this.

> 2) "Should we recommend the use of Block-wise Transfer for large file
> transfers and incorporate BERT into the CoAP over TCP draft?"

Yes. The draft should give statements for this. CoAP over TCP should support 
CoAP Block-wise Transfer related to RFC7252.

> You didn't directly answer that question and I am curious what your 
> thoughts are.

When doing CoAP over TCP, RFC7252 should be considered firstly.

If an application tranfers a large data by CoAP/UDP, it should concern the 
limit of UDP datagram, i.e less than 64KB.
Then the data may be delivered by CoAP Block-wise Tranfer.
If the size of data is greadter than 64KB, the application should do 
multiple invocations of CoAP/UDP.

If CoAP/TCP is considered, one TCP connection can transfer 64KB data in one 
window, probably with sevreal segments.
The 64KB limitation should be kept for the purpose with consistency to 
RFC7252,  and this limitaion may need clarifying in the draft.

Regards,


Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----原始邮件----- 
From: Hannes Tschofenig
Sent: Thursday, May 05, 2016 4:51 PM
To: weigengyu ; trac+core@zinfandel.tools.ietf.org ; 
draft-ietf-core-block@tools.ietf.org
Cc: core@ietf.org
Subject: Re: [core] #409 (block): CoAP over TCP: Multiple Simultaneous TCP 
Connections