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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 17 July 2017 08:55 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 25B2712EC36 for <anima@ietfa.amsl.com>; Mon, 17 Jul 2017 01:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 Yab5cxUjL7S7 for <anima@ietfa.amsl.com>; Mon, 17 Jul 2017 01:55:47 -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 5167812EA7C for <anima@ietf.org>; Mon, 17 Jul 2017 01:55:47 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-8110.meeting.ietf.org [31.133.129.16]) by relay.sandelman.ca (Postfix) with ESMTPS id 28E911F8F5; Mon, 17 Jul 2017 08:55:46 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 56245598; Mon, 17 Jul 2017 10:55:40 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: Toerless Eckert <tte@cs.fau.de>, Anima WG <anima@ietf.org>
In-reply-to: <ac374936-2718-c737-e871-e9f97ea6f78a@cisco.com>
References: <467b3a9b-6fe0-c01f-6165-18e6e290a28c@gmail.com> <14885.1499820271@dooku.sandelman.ca> <20170716182749.GC23525@faui40p.informatik.uni-erlangen.de> <23694.1500273241@dooku.sandelman.ca> <ac374936-2718-c737-e871-e9f97ea6f78a@cisco.com>
Comments: In-reply-to Eliot Lear <lear@cisco.com> message dated "Mon, 17 Jul 2017 08:54:46 +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: Mon, 17 Jul 2017 10:55:40 +0200
Message-ID: <11013.1500281740@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/lHxv8qO1rp9vLZCq-wZwPR4cB_A>
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: Mon, 17 Jul 2017 08:55:48 -0000

Eliot Lear <lear@cisco.com> wrote:
    > On the other hand, maybe it's fundamental, but is relying on LL in this
    > architecture to go beyond LL boundaries the right thing to do?

We've already established a way around the concern that made me think
that we needed multiple LL for the proxy, and also that we needed multiple
Ar for the proxy connection.

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