Re: [Roll] On anisotropic

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 November 2021 16:41 UTC

Return-Path: <mcr+ietf@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 B95BC3A096D for <roll@ietfa.amsl.com>; Thu, 18 Nov 2021 08:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 kcRVoWfMa0s5 for <roll@ietfa.amsl.com>; Thu, 18 Nov 2021 08:40:59 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C04A43A096F for <roll@ietf.org>; Thu, 18 Nov 2021 08:40:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C64121802E for <roll@ietf.org>; Thu, 18 Nov 2021 11:43:26 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id CAYKI9bmFkd1 for <roll@ietf.org>; Thu, 18 Nov 2021 11:43:24 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id F0E3B1802C for <roll@ietf.org>; Thu, 18 Nov 2021 11:43:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1637253804; bh=ndWsVUkNcIxsjpUddyUyguFma3aHXQXr0hZJsS+4gUw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=7dA6EgFKS2Ub1kYb3hnZxJrD/9u0B7NUSl0q3X3ICWrzaMPP8CmeDPGtxdUjqRxEk 3JM5G5iQJDIg4Pf/WQ/LqYFqzIZ7PUSllkGHDQcmyKg0VV3HfFWNdKPxMRQWS7q+N+ GDRaGLNBSaoJ95IUVftrp93oCsobysesdhnqONssRUK6FbmqoKcnukLAY9ioH+LIuZ O9Pfc/hqW5lQsFWrLQn8sjGFU4xuBKCS4XaYSkkk885zzGhh1TVACK3QcUqO2tVPJu 5r+0tHdW7ZhXdjvmgnFLpgbgIi7M/NOBJL1WhrGdZHG9Amaed2MDoiF4AwS4QAtqyW 29at4YLlsWe1A==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 20ACB9E for <roll@ietf.org>; Thu, 18 Nov 2021 11:40:54 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
In-Reply-To: <CO1PR11MB488179E66D0F3B72779933A0D89B9@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <CO1PR11MB488179E66D0F3B72779933A0D89B9@CO1PR11MB4881.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 18 Nov 2021 11:40:54 -0500
Message-ID: <12376.1637253654@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/pWL7mz8qUoWiDr-pEOBi0jeybi4>
Subject: Re: [Roll] On anisotropic
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: Thu, 18 Nov 2021 16:41:05 -0000

Pascal Thubert \(pthubert\) <pthubert=40cisco.com@dmarc.ietf.org> wrote:
    > The term anisotropic came up mostly in the elaboration of RIFT, which
    > inherits that design property from RPL. The term has been used there
    > for a while and it seemed fair to give it back to the protocol that
    > introduced it.

I don't think we were disagreeing with the term, we just weren't sure why it
was important to mention it now.   You've explained that, so good!

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide