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

Eliot Lear <> Fri, 14 July 2017 06:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ECF921317DF for <>; Thu, 13 Jul 2017 23:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.503
X-Spam-Status: No, score=-14.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JjpL_vHnJTRu for <>; Thu, 13 Jul 2017 23:13:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AE0AF12EC02 for <>; Thu, 13 Jul 2017 23:13:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2625; q=dns/txt; s=iport; t=1500012811; x=1501222411; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=pVuulkKHdJfh3KThOZP/aMqPiXbYiYwCYAWqihgzuC8=; b=MA+p/Tc2PaTIDt+LKUbHnjHH69Lfjci2PvOHpdc+DnmWzHnfz7K+LK7r KZISZ2hdBJd/PLPnDey3iKaiBPGRsmOuAsjwoWCjRj1iv/dFduTnGXF9U SnkpB/ZgMF4F4Ti6VP+ZEVdtTklC7zx857K1WWlxHYCA5BVY6a9kMK0Wy I=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,357,1496102400"; d="asc'?scan'208";a="653234756"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jul 2017 06:13:27 +0000
Received: from [] ([]) by (8.14.5/8.14.5) with ESMTP id v6E6DRUf002265; Fri, 14 Jul 2017 06:13:27 GMT
To: Brian E Carpenter <>, Toerless Eckert <>
Cc: Anima WG <>
References: <> <> <> <> <> <>
From: Eliot Lear <>
Message-ID: <>
Date: Fri, 14 Jul 2017 08:13:27 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="nco6g47WKwSf0KbLBncOmHJpD7MDqrFQ1"
Archived-At: <>
Subject: Re: [Anima] Is this how BRSKI/IPIP works?
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Jul 2017 06:13:33 -0000

Hi Brian,

On 7/14/17 12:41 AM, Brian E Carpenter wrote:
> That may be true, but for BRSKI as such, the only hard requirement is
> an address that is unique on a given link, which is a requirement anyway.
> IPIP is more of an issue for the node providing the proxy, which is
> hopefully a bit upscale from a light switch.

I made my comment in the context of a possible interface collision in
your diagram.  Those had to do with the autonomic nodes, not the
proxies, as I understand things.  To avoid those sorts of collisions, it
seems like using the h/w address remains sensible.  A collision in those
circumstances would be extremely unlikely, whereas relying on poor PRNG
almost assures it of happening.  These devices are likely to have very
little entropy available to them.