[Roll] Issue with MPL Option in IPv6 fragments
rabi narayan sahoo <rabinarayans0828@gmail.com> Sat, 25 May 2019 11:00 UTC
Return-Path: <rabinarayans0828@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96267120088 for <roll@ietfa.amsl.com>; Sat, 25 May 2019 04:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 xGQVjegnCQ_D for <roll@ietfa.amsl.com>; Sat, 25 May 2019 04:00:46 -0700 (PDT)
Received: from mail-it1-x12b.google.com (mail-it1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (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 41837120025 for <roll@ietf.org>; Sat, 25 May 2019 04:00:46 -0700 (PDT)
Received: by mail-it1-x12b.google.com with SMTP id e184so17540107ite.1 for <roll@ietf.org>; Sat, 25 May 2019 04:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=7RHgW5fwO0na0amE0tDxqQsUexpCPf1z13Ry34+i7pY=; b=N4RjYbhWPKZJXYMHh8vOTS0BVj1fNBfxhU7u0qxBDdHblihPpoZPesN5agDVdynqez NPBIkAViYZhsihvxFI2aqFF19CsrHXDwTfv9M16Fx9913hy/iBG9fIsB72rygKDzy6aW FPpbM5Rk3/O+YH3Jt8QhAJzwXN2xtQlzDIv9yoNpHjfpfy1pHYv1EsZKIRFFs7qLea19 TXCw7wt+ZkfF7wpC5410lUqOCuXWoak+rp5mlhY+5MYiI0UvOtk75iTm1P7CeVsf2RO6 X0denlXeCDE2opI326ZTBQVPyOICc0vqjK6dLq1btkRiRNm+HN0FcExJXUZ4M4p6vv/S 37jQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=7RHgW5fwO0na0amE0tDxqQsUexpCPf1z13Ry34+i7pY=; b=JYfH5WeOb8bnDc7VPl43qSngqtk6OkcR6cnNyDT2RhhXWMjIHffMFpiRvcOLFdhcHe HkGY+gDrkp7SRkHM9keEGVaf1rwDTHMW+DcH2jAFFPUfUXmzp8GMBl3i1WQOtLxCe+xU t6tENrgYi2We/0GUzo3DmfB9X/4P0q6FaLTMHryopfOe1X2vhjBpjsR1JCbpGYTX5LQP 6jkgAEb9JvKxSr4BxJbZDoxdYentqzZeZnS4m6kcOt+vEiKm/0FytaihhaW0zjuFLiOF Wb7ADuyxaHqWTXJwkhYTSFMNBHaF7Gc0rNiXGQ0yKWZG8GvlC+ienI6qL0e+1adN30hr B+BQ==
X-Gm-Message-State: APjAAAXPsvPv45E3/L7mEZcariaL9uTEazKOBYi/FBiY3vMPQYrks94Z WXhH9+Z0lkXDFcZKyiSx72SPXeGAZfLsF3Gbmobcj5mY
X-Google-Smtp-Source: APXvYqxpt3Sj/kKxl9BtrkVCgNO7Dk09Ok+m9IWBc1+be/hD4FFW5gycD7pnOc9qRrVyoxWwFxrEhJa/JCVvXXSSTXc=
X-Received: by 2002:a24:46d0:: with SMTP id j199mr20780772itb.63.1558782045380; Sat, 25 May 2019 04:00:45 -0700 (PDT)
MIME-Version: 1.0
From: rabi narayan sahoo <rabinarayans0828@gmail.com>
Date: Sat, 25 May 2019 16:30:34 +0530
Message-ID: <CAPT0++0YFGJgysEkd2bEs_4MXSwnppqpQ7xoCb600uun3UDaqQ@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000018e2b40589b43a51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/lLYmDsYUaWlRs6hW89AgjNj3FTE>
Subject: [Roll] Issue with MPL Option in IPv6 fragments
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2019 11:00:48 -0000
Deal All As per RFC 7731 MPL Option is carried in MPL Data Messages in an IPv6 Hop-by-Hop Options header, immediately following the IPv6 header. This option carries sequence number and seed id that will be used by MPL forwarders in the MPL domain to determine if the received data message is new or duplicate one. If an UDP based application sends multicast packet whose payload size is > 1280 bytes (Minimum IPv6 MTU) it will result into of fragmentation of the IPv6 packet. As per RFC 8200 hop-by-hop header is part of the Per-fragment-header and will be same for all the fragments. In this case the fragments of multicast IPv6 packet will have the same sequence number in the MPL option. Once MPL forwarder receives any of these fragments it will consider the rest of the fragments as duplicate one and drop. This will lead to the loss of the multicast message. Thanks Rabi
- [Roll] Issue with MPL Option in IPv6 fragments rabi narayan sahoo