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

["Michael Behringer (mbehring)" <[e-mail]>]

> Michael Behringer (mbehring) <[e-mail]> 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