Re: [6lo] recoverable fragments: should we adapt the fragment size to ECN?

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 27 May 2019 08:13 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB15C1200E9 for <6lo@ietfa.amsl.com>; Mon, 27 May 2019 01:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LN5n6yuS3aVg for <6lo@ietfa.amsl.com>; Mon, 27 May 2019 01:13:24 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E95281200FD for <6lo@ietf.org>; Mon, 27 May 2019 01:13:23 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id u11so14074748otq.7 for <6lo@ietf.org>; Mon, 27 May 2019 01:13:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0p1+DzYztr0sNWXjJg6lpaQuZQA5QFWx014SnytmOcA=; b=R8BSR5igKx4WfuIRb6ODt5ZFKjzjTLUXB6qZ9O4froPFfDt9tq8LxagjbWzqP3cMzM zdx5SHxo3rT/zb9a7jpWJlHcaCCYuhCn+eyxe7jrtI6G2h93WsxVX4qR2Ycd1cm0HfQU VhOMNgooIop1s5kocfviVOSe4VNmxp+ZyHI4yG/fiGmR0kdOEkveB4LwbTEtNUx5lYcY FWIu06gOlHj/IhKUTFp5ixHpwjPjrK+AzjR6dDPWKkddTrgSS5QUuufGBqEH2q5fZUqZ nVL8WaCy/9eChR4gNh4Y9Qb8M2WudnSpSUiGe+vo39RWkTAlv0/qVW8aAJGEocFquyEX IIZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0p1+DzYztr0sNWXjJg6lpaQuZQA5QFWx014SnytmOcA=; b=oRr4XDXtEcIw2ImqQ9Tfs3NkVhewjjo+NlPACrNj7C8Txan05EuhtUni+BzOnpZe+h RhUL0o1E4PVw7PJqVphhxwhgPjTEqPblfgHh6kDND8qQ/FSFMVFmzy1EAll2XrrZuAlG kiSvJ6qESJBadE8BJEOW4dIGe+IevzLgGXeOmH5tSohUZ9KrOyEgXB7TPxd0l2a3ujXn 5XJ8o5zJIC48BRTjtIW2jn7NQ8I+s6mZ81iqwbd1oa6GnvUB5hEV+eRgifAtEchFtyg+ p29VvsTdVHjwDqOTHARwo1VgjF5UFyz+/rIHpFoBOq7UehKtUEAFEcb1WhafbCsAk8E8 bwNQ==
X-Gm-Message-State: APjAAAXVQxlwlEa70P10jTgL2ikR9/twbAzgrlFR9eNCiRcgcA8FxjXp ruJrVm3HUrXVNiXpGD0S8qJ5xt0Zlwh/eEWyWN4=
X-Google-Smtp-Source: APXvYqwQzVadLq1gGamzxWsnDG6MPvPAT380mgiAbTN7Ji7O5FePUohtN3YCDyE4O2HDWtI1Ka8myxqTnHSAY55K7YA=
X-Received: by 2002:a9d:67d8:: with SMTP id c24mr26605492otn.190.1558944803339; Mon, 27 May 2019 01:13:23 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR11MB356527AB2145A9416CE536C2D8070@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB356527AB2145A9416CE536C2D8070@MN2PR11MB3565.namprd11.prod.outlook.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 27 May 2019 10:13:01 +0200
Message-ID: <CADnDZ8-XeznkrrRWdn4OROLHudKqNa4HDh+Fb77Has884p5uZg@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: "6lo@ietf.org" <6lo@ietf.org>, Laurent Toutain <laurent.toutain@imt-atlantique.fr>
Content-Type: multipart/alternative; boundary="0000000000003a4e500589da1f66"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/VKRMc8soY4zMaHOvM_KiXqtS8RU>
Subject: Re: [6lo] recoverable fragments: should we adapt the fragment size to ECN?
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2019 08:13:26 -0000

On Tue, May 21, 2019 at 3:05 PM Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> Dear all:
>
> *   During the review by Laurent, a question came up on we could change
> the fragment size when transmitting a datagram. As it goes we can, because
> the offset and size are indicated in each fragment. If the MTU goes down
> and a fragment must be resend, we can also resend a smaller piece with the
> original fragment sequence and send other fragments with unused sequences
> for the rest of the original fragment. This is made possible because the
> sequence is sequential in the bitmap but not in the order of fragments.
> That being said, a reaction to an ECN is to reduce the window. At the same
> time a node could also reduce the datagram size and enable a more
> streamlined transmission for all.   What do you all think? *
>

I think we should not change size to smaller when transmitting, but if
needed it must be limited for special cases.

AB


> *  Pascal   *
>
>
>
>
> * _______________________________________________ 6lo mailing list
> 6lo@ietf.org <6lo@ietf.org> https://www.ietf.org/mailman/listinfo/6lo
> <https://www.ietf.org/mailman/listinfo/6lo> *