Remote Bootstrap

Context:

You have a new device which has to communicate with other components to fulfill its purpose. The device is either connected directly to the other components, or it goes through a network and multiple intermediaries. Either way, the new device has to know how to create these connections. The device is located in a remote location where it is hard to reach for maintenance.

Forces:

• Security: Security credentials for authentication, authorization, or encryption may be needed for communication but these credentials have to be brought onto the device and have to be secure themselves.
• Simplicity: The device has to work without any further actions required by its owner. For example, the end-user does not have the ability to do any required setup or a company wants to install a large number of devices.
• Size or Cost Constraints: The device’s design, i.e., its form factor and the number of components, has to be small and simple because it needs to fit into size or cost limitations. Adding components just for bootstrapping, such as a memory card slot or USB connector for Medium-Based Bootstrap may not make sense.
• Robustness: You intend to use the device in harsh environments and you need it to be durable. For example, you want to seal it to be water tight, or you want to put into a rugged enclosure which is intentionally hard to access to prevent any adverse effects from the outside. But this limits access to the device for legitimate maintenance purposes.
• Flexibility: The details needed for first communication change with time. You need to adapt the device to these changes.
• Physical Access: You want to place the device in a location that is hard to reach, which makes it difficult or dangerous to do a Medium-Based Bootstrap.
• Scalability: You have to set up communication for a large number of devices, which costs time and resources if done manually.