From nobody Fri Apr 1 10:01:57 2022 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF3C3A00B1 for ; Fri, 1 Apr 2022 10:01:56 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 7.46.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <164883251661.5159.3446355808335154315@ietfa.amsl.com> Date: Fri, 01 Apr 2022 10:01:56 -0700 From: IETF Secretariat Archived-At: Subject: [Roll] Milestones changed for roll WG X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2022 17:01:57 -0000 Changed milestone "Initial submission of a root initiated routing state in RPL to the IESG", set due date to May 2022 from July 2020. Changed milestone "Initial submission of Enabling secure network enrollment in RPL networks draft to the IESG", set due date to September 2022 from June 2020. Changed milestone "Initial submission of Mode of Operation extension and Capabilities for RPL to the IESG", set due date to November 2022 from December 2020, added draft-ietf-roll-mopex to milestone, removed draft-ietf-roll-mopex-cap from milestone. Changed milestone "Initial submission of a proposal for Source-Route Multicast for RPL to the IESG", set due date to November 2023 from June 2020. Changed milestone "Initial submission of a proposal to augment DIS flags and options to the IESG", set due date to November 2023 from June 2020. Changed milestone "Initial submission of a YANG model for MPL to the IESG", set due date to November 2023 from July 2020. Changed milestone "Recharter WG or close", set due date to November 2023 from October 2021. URL: https://datatracker.ietf.org/wg/roll/about/ From nobody Fri Apr 1 12:14:28 2022 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 409603A184B for ; Fri, 1 Apr 2022 12:14:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 7.46.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <164884046624.7373.3530775651454353660@ietfa.amsl.com> Date: Fri, 01 Apr 2022 12:14:26 -0700 From: IETF Secretariat Archived-At: Subject: [Roll] Milestones changed for roll WG X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2022 19:14:27 -0000 Changed milestone "Initial submission of Enabling secure network enrollment in RPL networks draft to the IESG", set description to "Initial submission of Controlling Secure Network Enrollment in RPL networks draft to the IESG". Changed milestone "Initial submission of Mode of Operation extension and Capabilities for RPL to the IESG", set description to "Initial submission of Mode of Operation extension for RPL to the IESG". URL: https://datatracker.ietf.org/wg/roll/about/ From nobody Fri Apr 1 12:15:13 2022 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E99BB3A19B3 for ; Fri, 1 Apr 2022 12:15:10 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 7.46.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <164884051093.4996.4729290727317898922@ietfa.amsl.com> Date: Fri, 01 Apr 2022 12:15:10 -0700 From: IETF Secretariat Archived-At: Subject: [Roll] Milestones changed for roll WG X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2022 19:15:11 -0000 Changed milestone "Initial submission of Capabilities for RPL to the IESG", set state to active from review, accepting new milestone. Changed milestone "Initial submission of Fast Border Router Crash Detection in RPL to the IESG", set state to active from review, accepting new milestone. URL: https://datatracker.ietf.org/wg/roll/about/ From nobody Fri Apr 8 06:27:07 2022 Return-Path: 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 F1C0F3A1A66 for ; Fri, 8 Apr 2022 06:27:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.107 X-Spam-Level: X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.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 g55WoH1Ny4z1 for ; Fri, 8 Apr 2022 06:27:00 -0700 (PDT) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 CB16A3A1A3F for ; Fri, 8 Apr 2022 06:27:00 -0700 (PDT) Received: by mail-yb1-xb2b.google.com with SMTP id g9so15060094ybj.9 for ; Fri, 08 Apr 2022 06:27:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=iyXuKthxI2nYq6ti22oHPFwFODW1rK/VvhJ3J9CQYpE=; b=D/aCUtKT1G3sGegQwm/kv5TBW1yz9CGmr1GJhGTwQp9QSBvmsQW3umThXOlshmmB2V 44y4xsoI0pnuBY9to0H31XvRLuSxEZ6cgRXaET0GKDAcIxxpb4aBUd3nbp6leir0wv8E Rsm64BAWNGve/XNxamgwXyElUAiN78GmM2xLbl5PcpoiRSJWhxuE6GLKrkx8m0slzuH3 dWeyxz2b/XJK7ASpW5FkYkSTLUQ2pS6zBFvaJ+XV1uy7awplgOlKjjTKSwigYuD3jE60 1K4cCJU2U6ZrRMp4PKLnvLd3KlrfcnaOW9e8aXjMSJMgSYpyUzZeG30pvr052Dn4P5TL OVmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=iyXuKthxI2nYq6ti22oHPFwFODW1rK/VvhJ3J9CQYpE=; b=cIz3ZeTbma1UMuGpKOfqoP7AP7kz+Utv7xGr8dog1bA0e6zddiAcW326A+yZrUp4rb 03klEfKJgG5UVpl2bF+cNe/pmI1p2vV+9i8f9aiz9feC+G2SDr7RWMNz502cw8bjugeI cOMu7fS8HoW5AzW1nHL9mxW80EVgqJTJhMeM/S3MPyJDZTvM6EP3SlJ+RmXTkBgdxSHU U1oGl0mu22E6O2ze+MJjgjp9/eOx3Xn79g2mefG68nAel3eH7enlzYpWkgJSRgJoWwJs h6TCIWZAmW5iLBpjdtlw4bu1goeGWPZmdL8IKnNtYTlLv2ZZFbfn/C3dHd88bsUo05Rb //Fg== X-Gm-Message-State: AOAM5314MQYhRPDqR5Lv7b7x00c7vXhOX8JUyYNRGhAhPmrQlrN1man7 X6ymkHZdSqwYa8NJoZ6n0thKlbYULU+y6uuNLYhRLyakSJM= X-Google-Smtp-Source: ABdhPJziaTQE7uubd7FU9WF/clbjyGMRB/3EDfBWtQgfapB/IVJM3QXDQ+/71XwuMgErWK6MUypdTTh4Uv7XicDD+hM= X-Received: by 2002:a5b:98a:0:b0:633:c93e:3e17 with SMTP id c10-20020a5b098a000000b00633c93e3e17mr14017281ybq.512.1649424419378; Fri, 08 Apr 2022 06:26:59 -0700 (PDT) MIME-Version: 1.0 From: Ines Robles Date: Fri, 8 Apr 2022 16:26:23 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="00000000000099d8b705dc248c1b" Archived-At: Subject: [Roll] WGLC for draft-ietf-roll-dao-projection-25 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2022 13:27:05 -0000 --00000000000099d8b705dc248c1b Content-Type: text/plain; charset="UTF-8" Dear all, A Working Group Last Call (WGLC) starts today (08th April) until 29th April for draft-ietf-roll-dao-projection-25. The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-roll-dao-projection/ Please review this draft to see if you think that it is ready for publication and send your comments to the list stating your view. Thank you very much in advance, Ines and Dominique. --00000000000099d8b705dc248c1b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

A Working Group Last Call (WGLC) starts t= oday (08th April) until 29th April for draft-ietf-roll-dao-projection-25.
The draft is available here: https://datatracker.ietf.org/doc/draf= t-ietf-roll-dao-projection/

Please review this draft to s= ee if you think that it is ready for publication and send your comments to = the list stating your view.

Thank you very much in advance,

= Ines and Dominique.
--00000000000099d8b705dc248c1b-- From nobody Wed Apr 13 10:41:15 2022 Return-Path: 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 A803F3A1C10 for ; Wed, 13 Apr 2022 10:41:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 mHtZmz7PuqoY for ; Wed, 13 Apr 2022 10:41:09 -0700 (PDT) Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE0E03A1C06 for ; Wed, 13 Apr 2022 10:41:08 -0700 (PDT) Received: from dooku.sandelman.ca (desktop4.sandelman.ca [209.87.249.16]) by relay.sandelman.ca (Postfix) with ESMTPS id 3B2111F47B for ; Wed, 13 Apr 2022 17:41:04 +0000 (UTC) Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1942E1A0477; Wed, 13 Apr 2022 12:44:19 -0400 (EDT) From: Michael Richardson To: Routing Over Low power and Lossy networks In-reply-to: <5fad2f45-02a5-7241-f797-43165b0fc9a2@mimuw.edu.pl> References: <49ac5fc3-4a3c-fb87-d366-eb7e7cfd60df@mimuw.edu.pl> <18233.1583176305@localhost> <10272666-28c7-ab3e-9ceb-1b8f2bb6e5e5@mimuw.edu.pl> <02c7a894-b7a8-8fcb-9119-172a91a3871b@mimuw.edu.pl> <8421.1620834368@localhost> <21a67951-92c7-5cfa-7bda-a11ac004492c@mimuw.edu.pl> <260038.1647531160@dooku> <5fad2f45-02a5-7241-f797-43165b0fc9a2@mimuw.edu.pl> Comments: In-reply-to Konrad Iwanicki message dated "Fri, 18 Mar 2022 22:10:25 +0100." X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 26.3 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Wed, 13 Apr 2022 12:44:19 -0400 Message-ID: <386984.1649868259@dooku> Archived-At: Subject: Re: [Roll] Border router failure detection X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2022 17:41:14 -0000 --=-=-= Content-Type: text/plain Konrad Iwanicki wrote: > I may be wrong, but what I understood from Pascal's idea is that we > could try to get the root more involved in the process of coordinating > the children acting as sentinels, at least in the periods when it is > up. I think that this is an interesting thing to do. I wonder if we need to do this now, or if it is something that could be added later. As I think about it, I think that we should (quickly) publish RNFD as an Experimental RFC. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCgAdFiEEow/1qDVgAbWL2zxYcAKuwszYgEMFAmJW/eIACgkQcAKuwszY gEPPCAv9FSIw/C9gYVOcDwppWz/3Mq7YSu5pgNAOvGLT6SsXTQnzXluCwhZ8JI8A qPU3Seu7AKcPQ4M+3Yp7fQi7rKIFKnAvOsBimcpcecthbXg9wE7adHLevyx3gKz5 OZ7nlSvdqQ/7fMHiNZAH8WnxCT7hfd/B1m9IFUYcBZWp51SRFQu1mK1PpzSnKJp2 +7tdbFLsx7FASK8sJAarwn0Kw1ed5iFDiqtkxKpQ/JtTiIxCQKw6dfIO12iC+QJD 9u50S4mUTFFYOg9Fc3nZvbmb1YKc/1QTQB2PFTmizNSFJHWtX1sHvb/4Zk9JBkTw TMzsFhvFZ1ebF/oSbu5W6IhGeT80QbGgjSl2N8y1yK4xodVddR9KjkjrXAXA3bqJ 9EXkZ8FPneNHKQi+uzqc0833sbZJMuOXByqPfIM1/jVlr48PH4w1UH93SKPZFjXn rI4oHDnt7LtCmLvReLFdB3YNFKmdGm2+3uob7NleEyCqWc8x/tYhov/pPfimXc59 rbguxlQI =5bLL -----END PGP SIGNATURE----- --=-=-=-- From nobody Fri Apr 15 02:21:47 2022 Return-Path: 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 5EC6C3A0F5C for ; Fri, 15 Apr 2022 02:21:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ryjqeH_8Tx6s for ; Fri, 15 Apr 2022 02:21:39 -0700 (PDT) Received: from mail.mimuw.edu.pl (mail.mimuw.edu.pl [IPv6:2001:6a0:5001::4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 962BE3A0F5E for ; Fri, 15 Apr 2022 02:21:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by duch.mimuw.edu.pl (Postfix) with ESMTP id 6CC1A61F64794; Fri, 15 Apr 2022 11:21:35 +0200 (CEST) X-Virus-Scanned: amavisd-new at mimuw.edu.pl Received: from duch.mimuw.edu.pl ([127.0.0.1]) by localhost (mail.mimuw.edu.pl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id h0ef0YZubWP9; Fri, 15 Apr 2022 11:21:33 +0200 (CEST) Received: from [192.168.0.31] (unknown [213.134.178.208]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by duch.mimuw.edu.pl (Postfix) with ESMTPSA; Fri, 15 Apr 2022 11:21:31 +0200 (CEST) Message-ID: Date: Fri, 15 Apr 2022 11:21:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Content-Language: en-US To: Routing Over Low power and Lossy networks , Michael Richardson References: <49ac5fc3-4a3c-fb87-d366-eb7e7cfd60df@mimuw.edu.pl> <18233.1583176305@localhost> <10272666-28c7-ab3e-9ceb-1b8f2bb6e5e5@mimuw.edu.pl> <02c7a894-b7a8-8fcb-9119-172a91a3871b@mimuw.edu.pl> <8421.1620834368@localhost> <21a67951-92c7-5cfa-7bda-a11ac004492c@mimuw.edu.pl> <260038.1647531160@dooku> <5fad2f45-02a5-7241-f797-43165b0fc9a2@mimuw.edu.pl> <386984.1649868259@dooku> From: Konrad Iwanicki In-Reply-To: <386984.1649868259@dooku> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Roll] Border router failure detection X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2022 09:21:45 -0000 On 13/04/2022 18:44, Michael Richardson wrote: > Konrad Iwanicki wrote: > > I may be wrong, but what I understood from Pascal's idea is that we > > could try to get the root more involved in the process of coordinating > > the children acting as sentinels, at least in the periods when it is > > up. > > I think that this is an interesting thing to do. > I wonder if we need to do this now, or if it is something that could be added > later. That's a good question. From what I remember, the idea concerned probing the root, which is somewhat independent of RNFD's current focus but of course complementary. In such a case, indeed, this could be added later as a separate mechanism. I may be wrong, though. > As I think about it, I think that we should (quickly) publish RNFD as an > Experimental RFC. I have little experience with the various tracks, in particular the advantages of an intermediate experimental RFC. If you think that this is the best way to move things forward with the draft, I would not object. Best, -- - Konrad Iwanicki. From nobody Sun Apr 17 11:23:31 2022 Return-Path: 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 1225E3A0DD8 for ; Sun, 17 Apr 2022 11:23:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.11 X-Spam-Level: X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net 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 6KHdvo1HDVN6 for ; Sun, 17 Apr 2022 11:23:25 -0700 (PDT) Received: from nmtao102.oxsus-vadesecure.net (mta-102b.oxsus-vadesecure.net [51.81.61.67]) (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 13FFB3A0DCF for ; Sun, 17 Apr 2022 11:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; bh=nl0B06f6pz+9CCF+P1b5fKjbUPSZNXYZBnzRG/ iKYN0=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1650219803; x=1650824603; b=ezW5QAoFuclFRSUUCMgpvHAQLE9JexYys1qwm19jtddTXjOEoAQTPhu uw1O0CZ4YmfQovd7px70F83B/RHll3ndI9be8UJ/MdRh4hTq1pS09T54X5T11CTLlzwDl8/ epmEPSMMMgyAI8gH7X200m3B0/pYcm8kR3u5IGJopuwkwK2QjNHbUQxDZrCyu3ga9OA0Cza lwsTiuEmplvYiYJl1+wY/+iEN6mTnMZqdN0UhxCleteMYEWv0nOet1CS/EDiSF1IqPahStc U3GGO+KA0x4ZnYTCGv8bNuniRrysx3y40Dk6wTmmdym0cKj+P88UMDB5GpPioe5lCtkek4M ndA== Received: from [192.168.1.72] ([99.51.72.196]) by smtp.oxsus-vadesecure.net ESMTP oxsus1nmtao02p with ngmta id ec03a55d-16e6c22b1016139d; Sun, 17 Apr 2022 18:23:23 +0000 Message-ID: <9ce28d04-d586-9b77-2b4b-8e92ac2536dc@earthlink.net> Date: Sun, 17 Apr 2022 11:23:22 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 From: Charlie Perkins References: <835adc29-d9a0-91c7-2c7a-185195ee1296@lupinlodge.com> Content-Language: en-US To: Routing Over Low power and Lossy networks In-Reply-To: <835adc29-d9a0-91c7-2c7a-185195ee1296@lupinlodge.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Authentication-Results: oxsus-vadesecure.net; auth=pass smtp.auth=charles.perkins@earthlink.net smtp.mailfrom=charles.perkins@earthlink.net; Archived-At: Subject: [Roll] Proposed new multicast group for AODV-RPL X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2022 18:23:28 -0000 Hello folks, AODV-RPL messages could possibly be confusing to nodes that implement other protocols with MOP==4, and so we propose to create a new multicast group, perhaps called "All-AODV-RPL-nodes".  Nodes joining that multicast group MUST implement AODV-RPL and in particular have the ability to process and transmit RREQ and RREP messages.  AODV-RPL does not place any requirement on other nodes using MOP==4. This is an efficient way of resolving a possible issue for other devices implementing RPL protocols with MOP==4.  I had originally thought that such other implementations would simply drop packets with unrecognized options.  But, as it turns out, that is not what RFC 6550 specifies.  I still think that good implementations would not forward unrecognized AODV-RPL options, but there is ambiguity on this point.  Moreover, without a new multicast group, it is possible to imagine implementations that would mix AODV-RPL options with other non-AODV-RPL options.  That would be more likely to cause errors. Regards, Charlie P.