IETF Logo Mail Archive

Re: [Roll] DAO-Projection and new MOPs

Michael Richardson <mcr@sandelman.ca> Wed, 19 December 2018 23:24 UTC

Return-Path: <mcr@sandelman.ca>
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 869B1126F72 for <roll@ietfa.amsl.com>; Wed, 19 Dec 2018 15:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Xe7Y9J1chGNc for <roll@ietfa.amsl.com>; Wed, 19 Dec 2018 15:24:10 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4563129BBF for <roll@ietf.org>; Wed, 19 Dec 2018 15:24:10 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id D2E962008C for <roll@ietf.org>; Wed, 19 Dec 2018 18:24:02 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 2A175C55; Wed, 19 Dec 2018 18:24:09 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 23B1CC4F for <roll@ietf.org>; Wed, 19 Dec 2018 18:24:09 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <982B626E107E334DBE601D979F31785C5DD4E008@BLREML503-MBX.china.huawei.com>
References: <CAO0Djp0wiHUg15SfLzqXRF6Ko9JBbeL7C9CLZ6HRXcNxf+=Gew@mail.gmail.com> <9098.1545152446@localhost> <982B626E107E334DBE601D979F31785C5DD4E008@BLREML503-MBX.china.huawei.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30679.1545261849.1@localhost>
Date: Wed, 19 Dec 2018 18:24:09 -0500
Message-ID: <30680.1545261849@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/F_ifaJN9pESt-Xdqb7b5aYJWluQ>
Subject: Re: [Roll] DAO-Projection and new MOPs
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: Wed, 19 Dec 2018 23:24:13 -0000

Rahul Arvind Jadhav <rahul.jadhav@huawei.com> wrote:
    > Actually this (new ICMP code) would have worked very nicely but as you
    > mentioned the legacy nodes won't send back any response for unknown
    > codes.

    > I checked whether 6550 has an explicit statement and it does.

    > Section 6: "If a node receives a RPL control message with an unknown
    > Code field, the node MUST discard the message without any further
    > processing, MAY raise a management alert, and MUST NOT send any
    > messages in response."

maybe this deserves an update as well then :-)

v2.23.0 | Report a Bug | By Email