Re: [Anima] Is this how BRSKI/IPIP works?

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 14 July 2017 13:09 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ACB813170E for <anima@ietfa.amsl.com>; Fri, 14 Jul 2017 06:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qpPwwe2PdU48 for <anima@ietfa.amsl.com>; Fri, 14 Jul 2017 06:09:22 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E58B91296C9 for <anima@ietf.org>; Fri, 14 Jul 2017 06:09:21 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [62.168.35.69]) by relay.sandelman.ca (Postfix) with ESMTPS id C41DA1F8FB; Fri, 14 Jul 2017 13:09:20 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 1145159F; Fri, 14 Jul 2017 09:09:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: Toerless Eckert <tte@cs.fau.de>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Anima WG <anima@ietf.org>
In-reply-to: <c885cdc9-0ec9-98fd-858d-07c66bb84e25@cisco.com>
References: <467b3a9b-6fe0-c01f-6165-18e6e290a28c@gmail.com> <20170706033719.GF14122@faui40p.informatik.uni-erlangen.de> <827f69e7-4730-7bd2-c0ac-987e94adc61d@gmail.com> <20170706070938.GG14122@faui40p.informatik.uni-erlangen.de> <c885cdc9-0ec9-98fd-858d-07c66bb84e25@cisco.com>
Comments: In-reply-to Eliot Lear <lear@cisco.com> message dated "Thu, 13 Jul 2017 22:58:45 +0200."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 14 Jul 2017 15:09:18 +0200
Message-ID: <9854.1500037758@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Z7NslgafYxj0TPB3Mgq5NFgYeW0>
Subject: Re: [Anima] Is this how BRSKI/IPIP works?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jul 2017 13:09:23 -0000

Eliot Lear <lear@cisco.com> wrote:
    > On 7/6/17 9:09 AM, Toerless Eckert wrote:
    >> On Thu, Jul 06, 2017 at 04:34:05PM +1200, Brian E Carpenter wrote:
    >>> It used to be, but the recommendation today is a pseudo-random
    >>> value (RFC7217). In any case it's a software choice.

    >> brand new recommendations do not equate to be expected
    >> standard practice in products. Would be very good to have
    >> folks with practical insight into various products to
    >> provide more information.

    > On this point, I think it's quite likely that we will see a good number
    > of devices fielded that will do a lousy job of PRNG, and so it would be
    > inadvisable for them to implement RFC7217, lest they test their DAD code
    > in ways not really intended.  I'm not thinking about iPhones here, but
    > energy harvesting devices like some light switches, and a bunch of,
    > well,... crap.

    > The question is whether you should design for these devices.  IMHO "no"
    > is a perfectly valid answer, but I'm still a bit skeptical about the
    > value of 7217 for these class of devices in any event.

1) Constrained devices are out of scope for ANIMA.
2) even if they were in scope, kinetic powered light switches are not
   good candidates for join proxies.  Light bulbs, however.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-