IETF Logo Mail Archive

[6lo] draft-ietf-6lo-fragment-recovery: What to do if hop limit is reached

Martine Lenders <m.lenders@fu-berlin.de> Tue, 05 November 2019 10:54 UTC

Return-Path: <m.lenders@fu-berlin.de>
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 9F4F11208DA for <6lo@ietfa.amsl.com>; Tue, 5 Nov 2019 02:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 QbSWFJFhMCrJ for <6lo@ietfa.amsl.com>; Tue, 5 Nov 2019 02:54:15 -0800 (PST)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D04D120894 for <6lo@ietf.org>; Tue, 5 Nov 2019 02:54:15 -0800 (PST)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for 6lo@ietf.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (envelope-from <m.lenders@fu-berlin.de>) id <1iRwTV-000zaG-CO>; Tue, 05 Nov 2019 11:54:13 +0100
Received: from mail-ot1-f50.google.com ([209.85.210.50]) by inpost2.zedat.fu-berlin.de (Exim 4.85) for 6lo@ietf.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (envelope-from <m.lenders@fu-berlin.de>) id <1iRwTV-003ZYw-1l>; Tue, 05 Nov 2019 11:54:13 +0100
Received: by mail-ot1-f50.google.com with SMTP id c19so1117983otr.11 for <6lo@ietf.org>; Tue, 05 Nov 2019 02:54:12 -0800 (PST)
X-Gm-Message-State: APjAAAVtti7k9o0p5dwqCX0zjjCiTZTi8GJ3Ru1TIW+4Unh8v0vEx5Z6 GDDQnfSoyut/5vuRBbc/vexuyZdKNX+OdwChqaQ=
X-Google-Smtp-Source: APXvYqxabEQKTfFniss/naetuvWOUuZrSiuoMMWZcuypzny9swho960m2Wv5c5pGST/6p5g3GuI4MC4FG9tPINoO7/U=
X-Received: by 2002:a05:6830:2096:: with SMTP id y22mr385812otq.128.1572951251938; Tue, 05 Nov 2019 02:54:11 -0800 (PST)
MIME-Version: 1.0
From: Martine Lenders <m.lenders@fu-berlin.de>
Date: Tue, 05 Nov 2019 11:53:35 +0100
X-Gmail-Original-Message-ID: <CALHmdRw2G32snHE_-Ov6sS3i5JvgzcsTTT9iqapPFkUZS5n97A@mail.gmail.com>
Message-ID: <CALHmdRw2G32snHE_-Ov6sS3i5JvgzcsTTT9iqapPFkUZS5n97A@mail.gmail.com>
To: 6lo@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009ef20a05969740af"
X-Originating-IP: 209.85.210.50
X-ZEDAT-Hint: A
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/vWZvBbdjR15vOYNkz-mw6VXBJH0>
Subject: [6lo] draft-ietf-6lo-fragment-recovery: What to do if hop limit is reached
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: Tue, 05 Nov 2019 10:54:17 -0000

Hello,

I'm aware this is a corner case that usually should not happen in a
properly configured WPAN, but what is an implementation of selective
fragment recovery supposed to do, if hop-limit 0 is reached? With minimal
forwarding I just reassembled it and handed it to IPv6 so it can send a
ICMPv6 Time exceeded error message. Should selective fragment recovery send
an abort ACK in that case as well? Or just the abort ACK?

Best regards,
Martine

v2.23.0 | Report a Bug | By Email