IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 13 April 2016 15:18 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2ACE212E0EC for <anima-bootstrap@ietfa.amsl.com>; Wed, 13 Apr 2016 08:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level:
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 Nv4YHkjUzzmt for <anima-bootstrap@ietfa.amsl.com>; Wed, 13 Apr 2016 08:18:17 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9EE512E39A for <anima-bootstrap@ietf.org>; Wed, 13 Apr 2016 08:18:16 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 481322002A for <anima-bootstrap@ietf.org>; Wed, 13 Apr 2016 11:22:12 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 957AA63755 for <anima-bootstrap@ietf.org>; Wed, 13 Apr 2016 11:18:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "anima-bootstrap@ietf.org" <anima-bootstrap@ietf.org>
In-Reply-To: <8c3d30d618ae4035b2c5ac316491120c@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>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 13 Apr 2016 11:18:15 -0400
Message-ID: <16090.1460560695@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/JFPvF-O_KH8NubmNUnliQxZUshI>
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:18:20 -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.

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.

I also claim it is less hassle to it via origin address, because otherwise a
network configuration has to reach out to the proxy and provision it with the
right info for each interface as to "location".

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

v2.23.0 | Report a Bug | By Email