... and, importantly, record enough information about peer sleds to be able to re-identify them. For full context, see: RFD 238: Trust Quorum and Rack Unlock.
RFD 259, Section 3.2 documents:
Each server derives a bootstrap IPv6 /64 prefix. This may be non-persistent and randomly generated...
However, today, the bootstrap addresses are persistent. This durability allows services - such as RSS - to uniquely identify them, which allows RSS to safely provision services to sleds safely, even across reboots.
If sleds could uniquely identify their peers based on some other form of identity - for example, from a certificate derived from the RoT - that could be used as a unique ID, and the bootstrap address could become more transient.
... and, importantly, record enough information about peer sleds to be able to re-identify them. For full context, see: RFD 238: Trust Quorum and Rack Unlock.
RFD 259, Section 3.2 documents:
However, today, the bootstrap addresses are persistent. This durability allows services - such as RSS - to uniquely identify them, which allows RSS to safely provision services to sleds safely, even across reboots.
If sleds could uniquely identify their peers based on some other form of identity - for example, from a certificate derived from the RoT - that could be used as a unique ID, and the bootstrap address could become more transient.