[Lwip] [Fwd: I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-04.txt]

[Carles Gomez Montenegro]

Dear LWIG and TCPM WGs,

As you can see below, we have updated the "TCP Usage Guidance in the
Internet of Things (IoT)" draft.

This revision intends to address previously pending TODOs, as well as
comments from the LWIG session in Montreal.

As you may recall, we are getting ready for requesting a WGLC. Your
comments will be most welcome.

Thanks,

Carles (on behalf of all authors)


 Original Message 
Subject: [Lwip] I-D Action:
draft-ietf-lwig-tcp-constrained-node-networks-04.txt
From:internet-dra...@ietf.org
Date:Tue, October 9, 2018 7:30 am
To:  i-d-annou...@ietf.org
Cc:  lwip@ietf.org
--


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Light-Weight Implementation Guidance WG
of the IETF.

Title   : TCP Usage Guidance in the Internet of Things (IoT)
Authors : Carles Gomez
  Jon Crowcroft
  Michael Scharf
Filename: draft-ietf-lwig-tcp-constrained-node-networks-04.txt
Pages   : 25
Date: 2018-10-08

Abstract:
   This document provides guidance on how to implement and use the
   Transmission Control Protocol (TCP) in Constrained-Node Networks
   (CNNs), which are a characterstic of the Internet of Things (IoT).
   Such environments require a lightweight TCP implementation and may
   not make use of optional functionality.  This document explains a
   number of known and deployed techniques to simplify a TCP stack as
   well as corresponding tradeoffs.  The objective is to help embedded
   developers with decisions on which TCP features to use.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lwig-tcp-constrained-node-networks/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lwig-tcp-constrained-node-networks-04
https://datatracker.ietf.org/doc/html/draft-ietf-lwig-tcp-constrained-node-networks-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lwig-tcp-constrained-node-networks-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip


___
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip

[Lwip] I-D Action: draft-ietf-lwig-tcp-constrained-node-networks-04.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Light-Weight Implementation Guidance WG of the 
IETF.

Title   : TCP Usage Guidance in the Internet of Things (IoT)
Authors : Carles Gomez
  Jon Crowcroft
  Michael Scharf
Filename: draft-ietf-lwig-tcp-constrained-node-networks-04.txt
Pages   : 25
Date: 2018-10-08

Abstract:
   This document provides guidance on how to implement and use the
   Transmission Control Protocol (TCP) in Constrained-Node Networks
   (CNNs), which are a characterstic of the Internet of Things (IoT).
   Such environments require a lightweight TCP implementation and may
   not make use of optional functionality.  This document explains a
   number of known and deployed techniques to simplify a TCP stack as
   well as corresponding tradeoffs.  The objective is to help embedded
   developers with decisions on which TCP features to use.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-lwig-tcp-constrained-node-networks/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-lwig-tcp-constrained-node-networks-04
https://datatracker.ietf.org/doc/html/draft-ietf-lwig-tcp-constrained-node-networks-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lwig-tcp-constrained-node-networks-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip

Re: [Lwip] [E] [6lo] fragment forwarding implementation and performance report

[Chakrabarti, Samita]

Hi Rahul,

Thanks very much for sharing the fragment forwarding implementation results..
The following drafts are implemented as per the link you provided:
Fragment Forwarding drafts

   1. Virtual reassembly buffers in 6LoWPAN
   

   2. LLN Minimal Fragment Forwarding
   


>From the results, I noticed an observation that send rate 80s, and 40s are
doing better than the 160s  send rate with 50s forwarding fragment spacing.
Send rate Xs means sending fragmented packets at X sec interval - right?
I thought, the performance would improve with higher X value,  but that is
not true - perhaps due to increased payload size.
A graph or tabular result with same payload size with increased send
interval rate might be useful to figure out the optimal pacing time for
that payload - just a thought.

In general, very interesting results!

Also, it shows that by controlling the pacing of forwarding the fragments
the performance can be improved to a great degree in a medium to small size
mesh. ( in this example, 50 nodes).

What happens when you increase the mesh size ( aka number of nodes)?

Cheers,
-Samita

On Mon, Oct 8, 2018 at 7:17 AM Rahul Jadhav  wrote:

> 
>
>
>
> Hello All,
>
>
> We tried experimenting with the virtual reassembly buffer and fragment
> forwarding drafts.
>
> One fundamental characteristic that has major implications on fragment
> forwarding performance is its behavior with realistic 802.15.4 RF
> (especially when a train of fragments are simultaneously received and
> transmitted). This is something which was not evaluated in any other
> experiment.
>
>
>
> You ll find the details of the implementation, test setup details and
> performance result here:
>
> https://github.com/nyrahul/ietf-data/blob/rst/6lo-fragfwd-perf-report.rst
> 
>
>
>
> Results are quite interesting: Simultaneous send/recv of fragments with
> fragment forwarding has major implications on PDR/Latency.
>
>
>
> Feedback most welcome.
>
>
>
> Thanks,
>
> Rahul
> ___
> 6lo mailing list
> 6...@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_6lo=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=pWMzx7FsqijEJPyfMBfn-HJss-wVVTf0K5y-cxCTXL8=PeFHI-ltr748QRhWwqigY8iNFPw9EcyFDwOeSrv6KQc=ebzWBVEJyovVUcFHM2mByigGnDBv0aoTSm21fmwa5vU=
>
___
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip

[Lwip] fragment forwarding implementation and performance report

[Rahul Jadhav]

Hello All,


We tried experimenting with the virtual reassembly buffer and fragment
forwarding drafts.

One fundamental characteristic that has major implications on fragment
forwarding performance is its behavior with realistic 802.15.4 RF
(especially when a train of fragments are simultaneously received and
transmitted). This is something which was not evaluated in any other
experiment.



You ll find the details of the implementation, test setup details and
performance result here:

https://github.com/nyrahul/ietf-data/blob/rst/6lo-fragfwd-perf-report.rst



Results are quite interesting: Simultaneous send/recv of fragments with
fragment forwarding has major implications on PDR/Latency.



Feedback most welcome.



Thanks,

Rahul
___
Lwip mailing list
Lwip@ietf.org
https://www.ietf.org/mailman/listinfo/lwip