IETF Logo Mail Archive

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

Eliot Lear <lear@cisco.com> Mon, 17 July 2017 06:54 UTC

Return-Path: <lear@cisco.com>
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 43297131690 for <anima@ietfa.amsl.com>; Sun, 16 Jul 2017 23:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 fe41POm2psNT for <anima@ietfa.amsl.com>; Sun, 16 Jul 2017 23:54:51 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBB781315FE for <anima@ietf.org>; Sun, 16 Jul 2017 23:54:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6918; q=dns/txt; s=iport; t=1500274491; x=1501484091; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=8Q44rTXbGn5mHCkMfe+60gkqZ2uIoot5XAx1DRKBFpg=; b=WHvCJVBdF86VObAlDHQEkYxLGBhmyHRKc+afBHOV/e83/sWKY9i7Tosw s1853CKX4DmOezFB9B9Myj5swYYMkulrgXq6PGFKkPUTD+hVq0kqxUiAq zuVGnFJw6rcwxszKTpfGcKJtPwiR+EbhZJVcdUU7+ZrdFfZcC0JfhKUvm U=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DkAADDXWxZ/xbLJq1cGgEBAQECAQEBAQgBAQEBhD6BFI4Lc5BskFiFLIIRBxoBCoFggzsChDMYAQIBAQEBAQEBayiFGQEBAQMBASFLCxALBA4GKgICJyIOBgEMBgIBAYorEK5YgiYnimwBAQEBAQEBAQEBAQEBAQEBAQEBAQEOD4MohS4rgnmHfYJhBYlViGGMfoQsgh2NTYsuhwGVVx84gQoxIQgbFUmHGD42iQwBAQE
X-IronPort-AV: E=Sophos;i="5.40,373,1496102400"; d="asc'?scan'208,217";a="654315208"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jul 2017 06:54:46 +0000
Received: from [10.61.216.24] ([10.61.216.24]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v6H6sjal026587; Mon, 17 Jul 2017 06:54:46 GMT
To: Michael Richardson <mcr+ietf@sandelman.ca>, Toerless Eckert <tte@cs.fau.de>
Cc: Anima WG <anima@ietf.org>
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>
From: Eliot Lear <lear@cisco.com>
Message-ID: <ac374936-2718-c737-e871-e9f97ea6f78a@cisco.com>
Date: Mon, 17 Jul 2017 08:54:46 +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: <23694.1500273241@dooku.sandelman.ca>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="i3jtx3pCXnX4FlMPbDB3IECbopiIrWlau"
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/ETrkc20zAbD7nVCI_VBwdMTRG3A>
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 06:54:53 -0000

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?


On 7/17/17 8:34 AM, Michael Richardson wrote:
> Toerless Eckert <tte@cs.fau.de> wrote:
>     > I thought i had asked that question already but not sure, and not seen
>     > an answer: - I have never seen that a device has more than one
>     > link-local addr on an interface.  Is this permitted by IPv6 arck ? Can
>     > you configure this in eg: Linux. I thought i tried on linux/cisco-ios
>     > in the past and i do not quite remember, but i think it failed (only
>     > one address).
>
> dooku-[~](2.3.0) mcr 10879 %sudo ip -6 addr add fe80::1234/64 dev wlan0
>
> dooku-[~](2.3.0) mcr 10788 %ifconfig wlan0
> wlan0     Link encap:Ethernet  HWaddr 08:11:96:01:81:e0
>           inet addr:31.133.129.16  Bcast:31.133.143.255  Mask:255.255.240.0
>           inet6 addr: fe80::1234/64 Scope:Link
>           inet6 addr: fe80::a11:96ff:fe01:81e0/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
> dooku-[~](2.3.0) mcr 10788 %ip -6 addr ls dev wlan0
> 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
>     inet6 fe80::1234/64 scope link
>        valid_lft forever preferred_lft forever
>     inet6 fe80::a11:96ff:fe01:81e0/64 scope link
>        valid_lft forever preferred_lft forever
>
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
>
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

v2.14.0 | Report a Bug | By Email