Reproofing on attribute change

[paul-grassi]

Consider content around re-proofing. For example, with verified attributes/providers, there may be no need to ever reproof, just get updated attribute. For example, name change. I proof today as smith, change name to jones - municipality just sends attribute update. Assumes proper binding to smith, so this may not be an automatic

[jimfenton]

I don't think of an attribute change like that as re-proofing. We do still have the limited re-proofing that is required if the subscriber loses too many authenticators, but that's more about binding to "smith" than attribute values.