Re: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options

"Max Pritikin (pritikin)" <pritikin@cisco.com> Tue, 08 December 2015 23:48 UTC

Return-Path: <pritikin@cisco.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 978CB1ACE91 for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Dec 2015 15:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 BbZsr1uDMZOF for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Dec 2015 15:48:44 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 271881ACE88 for <anima-bootstrap@ietf.org>; Tue, 8 Dec 2015 15:48:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3178; q=dns/txt; s=iport; t=1449618523; x=1450828123; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=bX41Fv9sQsSJNBUZ/DaGTakzh6kUCl209sWqhGj3ZBQ=; b=C9Q5xHcI2NuCJfq/a4trTj4bnYuoaQI5dzsnhUwCZJSGN4+PJCtbWwHy 5AbTat3GRFp/Q4xyjVBd0yf3w8dVKIW+qnC9I2GCYydtJJDfOlQbUdTOi X2IW6GYs8s97s5/Y4CLKPTKvABMuhDkTT4RitoUnuxhE5Z3vblJgwrXnK 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AlBQDCa2dW/4kNJK1UCoM6gUEGvUeBboJegzACHIEaOhIBAQEBAQEBgQqENAEBAQMBIxFFBQsCAQgYAgImAgICMBUQAgQOBYgnCK4ikG4BAQEBAQEBAQEBAQEBAQEBAQEBGoEBh2KCboQwKYMeL4EVBYVVgXeHEIgFAYsBgjqBW5cgg3EBKAE6hARyhGiBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,401,1444694400"; d="scan'208";a="51659187"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Dec 2015 23:48:43 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id tB8NmhWg027268 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Dec 2015 23:48:43 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 8 Dec 2015 17:48:42 -0600
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1104.009; Tue, 8 Dec 2015 17:48:42 -0600
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Thread-Topic: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options
Thread-Index: AQHRLjUzUXhNiuqCZk29llWSg8eoaJ677SQAgARf/ICAAAYvgIABxvuAgAAT0AA=
Date: Tue, 08 Dec 2015 23:48:42 +0000
Message-ID: <43C69994-D02E-44A0-A739-4A6E45A3CE8C@cisco.com>
References: <20151204014333.GZ29056@cisco.com> <A4DCBB7E-A722-4AC1-A7B7-BD185ABEBF7F@cisco.com> <13379.1449515233@dooku.sandelman.ca> <20D831CB-5075-4899-9C4F-D3D04334B1CF@cisco.com> <2495.1449614267@dooku.sandelman.ca>
In-Reply-To: <2495.1449614267@dooku.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.99.106.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C4E50481C187E8468A2AF39C0F74BC59@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/B1LJERCSjMDQr2wCADxCg_ehs98>
Cc: "Toerless Eckert (eckert)" <eckert@cisco.com>, "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
Subject: Re: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2015 23:48:45 -0000

> On Dec 8, 2015, at 3:37 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Max Pritikin (pritikin) <pritikin@cisco.com> wrote:
>>> This is one reason I'd like the new device to do things that
>>> configured devices do regularly.  So sending out a multicast IKEv2
>>> INIT might really make sense here.  Every device should do it every 5
>>> to 15 minutes.
>>> 
>>> A new device will either send them, or receive them.  Either way, it
>>> can respond and within the privacy of IKEv2, can do something.  That
>>> doesn't you can't use a proxy to get things through: the resulting
>>> one-hop-ACP won't be part of the production ACP.
> 
>> Michael, I failed to parse your response.
> 
>> Are you agreeing with Toerless’ argument that the new device should be
>> a responder?
> 
> No. I'm saying that a new device should do as little as possible to call
> attention to itself,

Ok, sounds like you’re agreeing with the threat but not necessarily the suggested mitigation.

> and should prefer to do things that all other devices
> are already doing.

I’m partially convinced that its worth minimizing how much a device “sticks its neck out” but once bootstrap is initiated I don’t think hiding the exchange is very easy nor worth the effort.

> 
>> Or, are you arguing that the new device should initiate the
>> bootstrapping; but do so in a way that does not expose it is a new
>> device?
> 
> For non-challenged (IoT) devices on non-challenged networks, the new device should
> initiate and drive the bootstrapping.
> 
> It would be best if this communication was indistinguishable from other ACP
> communication to an outsider.

This can only occur if bootstrapping is over a “provisional” ACP. I’m uncomfortable with having GRASP and ACP include special cases for bootstrapping. My gut feel is that the simplicity of a specific bootstrapping sequence — even if identifiable — is preferable. 

A *non-privacy* preserving bootstrapping is preferable from a certain point of view. I want my autonomic network to track and identify any overlapping autonomic bootstrapping to domains I don’t recognize. 

- max

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