Re: [Anima-bootstrap] Can the proxy add information during bootstrap?

"Michael Behringer (mbehring)" <mbehring@cisco.com> Wed, 13 April 2016 15:30 UTC

Return-Path: <mbehring@cisco.com>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E2012D9B1 for <anima-bootstrap@ietfa.amsl.com>; Wed, 13 Apr 2016 08:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 vHE7mMu46sbe for <anima-bootstrap@ietfa.amsl.com>; Wed, 13 Apr 2016 08:30:54 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF10612DA10 for <anima-bootstrap@ietf.org>; Wed, 13 Apr 2016 08:30:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1658; q=dns/txt; s=iport; t=1460561453; x=1461771053; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=rBesfdvfI+aHnDzrd79zZpzDTbMfcv5fk6HcN79gx/I=; b=VaoHuix3Ywi5RxLhvCxZ7ipsBehxkP+e6Bgpgms134x0XpcuLirQcsBt 6o/bfCOKO9caLB6ywr519gaaceQBPCTAihRNjTJWJ4CrpHoPcBUQ4B/oN /KQIrNzo9dDx8MX5srtIyZ7qG9TqPi/t+uATh/rCnQgM+PSyMwc75WY9n s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgCSZQ5X/4sNJK1egzeBUAa6RgENg?= =?us-ascii?q?XSGDgKBQDgUAQEBAQEBAWUnhEEBAQEDATpECwIBCBgeEDIlAgQBEgiIGAjDHQE?= =?us-ascii?q?BAQEBAQEDAQEBAQEBAQEYhiGES4oVBZgIAY4FgW6ETohbjyYBHgEBQoNnbIh8f?= =?us-ascii?q?gEBAQ?=
X-IronPort-AV: E=Sophos;i="5.24,480,1454976000"; d="scan'208";a="260844337"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Apr 2016 15:30:52 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u3DFUqCo018194 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Apr 2016 15:30:52 GMT
Received: from xch-rcd-006.cisco.com (173.37.102.16) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 13 Apr 2016 10:30:51 -0500
Received: from xch-rcd-006.cisco.com ([173.37.102.16]) by XCH-RCD-006.cisco.com ([173.37.102.16]) with mapi id 15.00.1104.009; Wed, 13 Apr 2016 10:30:51 -0500
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
Thread-Topic: [Anima-bootstrap] Can the proxy add information during bootstrap?
Thread-Index: AQHRlRlxL75adUdvWUak1H6GJRHLbZ+HZZEAgAAA2oCAAMw9gP//xbDAgABgrYD//639AA==
Date: Wed, 13 Apr 2016 15:30:51 +0000
Message-ID: <165fb533767948d39ce89def735f1f9b@XCH-RCD-006.cisco.com>
References: <5c12b5d6940d4970bd3c0ad4c94b4696@XCH-RCD-006.cisco.com> <14252.1460506458@obiwan.sandelman.ca> <570D96FE.1000105@gmail.com> <20160413004957.GH21173@cisco.com> <18364.1460552457@obiwan.sandelman.ca> <8c3d30d618ae4035b2c5ac316491120c@XCH-RCD-006.cisco.com> <16090.1460560695@obiwan.sandelman.ca>
In-Reply-To: <16090.1460560695@obiwan.sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.238.142]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/wrrHy7DukaRn9uXfxHsAjFsCAmc>
Subject: Re: [Anima-bootstrap] Can the proxy add information during bootstrap?
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 13 Apr 2016 15:30:56 -0000

> Michael Behringer (mbehring) <mbehring@cisco.com> wrote:
>     >> If you know enough in advance to know which device (down to the SN)
>     >> was supposed to be in each location, then I don't think you need/have
>     >> a zero- touch situation.
> 
>     > I've heard the requirement quite a few times to be able to see where in
>     > the network a device is trying to enrol. For starters, assuming you are
>     > shipping devices to install locations randomly, then you can make the
>     > link between device and target config.
> 
> why?  and once you reject the device, what happens next?  How does the
> device communicate back to the installer: "I'm in the wrong place"
> vs,  "This isn't the network I'm looking for"?
> Remember: we are doing this so that the installer can be clueless.
> 
> Can you please me more precise then "I've heard"?  I'd like the real customer
> belief here.

Need to dig - that goes several years back...
 
> Does the customer understand the new model, or are they working on their
> old DHCP thinking?
> 
>     > My feeling: Unless a big issue, would be good to support the passing on
>     > of proxy information in the bootstrap protocol.
> 
> I claim you can do this with origin address.  We already have to have a unique
> ACP origin address *per link* because we have to know how to return the
> packets to the correct link.

Err... I'm not parsing that - an ACP address per link? I must have missed something. In my mental model an AN node has an ACP *loopback* but links are only addressed with link local? Can you expand? 

Michael