[Roll] DIS Multicast behaviour
Shobhit <shobhit.bits@gmail.com> Wed, 11 May 2016 09:41 UTC
Return-Path: <shobhit.bits@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 C000112D599 for <roll@ietfa.amsl.com>; Wed, 11 May 2016 02:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 4oWS5y7fVgxi for <roll@ietfa.amsl.com>; Wed, 11 May 2016 02:41:35 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 23ACD12D5E2 for <roll@ietf.org>; Wed, 11 May 2016 02:41:35 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id s184so49730551vkb.3 for <roll@ietf.org>; Wed, 11 May 2016 02:41:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=z040NrJIrL7lyL68oYGS6YfYGxZBXYXkvy053OVyOHk=; b=owAqxvhKYAnJ1kboJVlj5JvSf+iSSDQ9I2ofuStoHhC2rKxH41WVpiVX0cltrZHU+O zThG2+y02y7QxhQ42h8KCTcoZXL00JsJEPBMzNCBdRqfygoIgXqvlR3OsUMq+XWH97ZV 9AhqN1FfCvl7yoQy9gvwmdrokpZgXTPpxmwlN5oGmbDPNIlvtKHmIVq1RD6oT3s2ucWC +JYuNwKn84dvB2yRhzb4IF5ETDl5tTNLtgJ4JPB4DGYkBmcKAjBN+ksD/JjatdjrpSXG 5pdWqLbKrZIHPtdU7RrlBWzRIM3r5bqVmIEEtEg4CAybDRJguPTXUNkGEhX+74gww1Fm WR1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=z040NrJIrL7lyL68oYGS6YfYGxZBXYXkvy053OVyOHk=; b=OcLVVd6zQst2MG8oav6KGhfAyt4ApUO11ox0gISqF78nM02gasuS7iasoFQoQytljy mGHMHteZpUW07lacPkiFjZftH525NlRBn9mCYYBFyPTxuJLPKj/aJ3M7rVnR2xIPCjiM W8dbKUyUgVl6vJz9gUCOZAzkcZvReMhbBnlsJrsTgjSqZ3MJOmmHPHVB8BiDe7poaBJi TcjKHDJq15Zt0Ej1H5NqXzxEiDcZ5KIeXH0Jcm8SYrToCVKV9uXYVemtffgdr6GgyTsy 8BABQfVme5iBLdwsqzRYJExLw2hxJmgvxwkfwyjdoM72i1ee8Z97FYYrTc5CXv11Dpi7 HVpA==
X-Gm-Message-State: AOPr4FVQhHcPDFoJDMnJAJkQhmTKsKx+AHPwe7uL/J/gR1U2j+7Gp0sZplium6SS7cNkSv4hM0fzRJVd2pkLBA==
MIME-Version: 1.0
X-Received: by 10.31.210.65 with SMTP id j62mr1140553vkg.133.1462959694284; Wed, 11 May 2016 02:41:34 -0700 (PDT)
Received: by 10.176.2.40 with HTTP; Wed, 11 May 2016 02:41:34 -0700 (PDT)
Date: Wed, 11 May 2016 15:11:34 +0530
Message-ID: <CAN5cqrW1eNtUpDGPUmowkiVaPKkWXF4io5ZSSa6OXpo+=aJGRQ@mail.gmail.com>
From: Shobhit <shobhit.bits@gmail.com>
To: roll@ietf.org
Content-Type: multipart/alternative; boundary="001a114bc2d4e60c3f05328dd88f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/sgUjO7FAMso0CRQOWpB85Q6kgWo>
Subject: [Roll] DIS Multicast behaviour
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
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: Wed, 11 May 2016 09:41:37 -0000
Hi,
I have requirement to receive multicast DIS messages from any node without
resetting the trickle timer.
As standard indicates that if any node will receive the multicast DIS
message , it will be considered as inconsistency with respect to trickle
timer of recipient(RFC 6550 ,Sec 8.3).
It also indicates this behavior can be controlled by DIS flag.
But after checking the DIS flag option , it is mentioned that it is unused
filed (Sec 6.2.1).
"Flags: 8-bit unused field reserved for flags. The field MUST be
initialized to zero by the sender and MUST be ignored by the
receiver."
Please suggest if there is any way to stop the reset of trickle timer in
case of reception of multicast DIS message.
--
Regards,
Shobhit
- [Roll] DIS Multicast behaviour Shobhit
- Re: [Roll] DIS Multicast behaviour dominique.barthel