Appendix A Usefulness

[kc2rxo]

Is Appendix A useful here? I don't see how.

[kc2rxo]

Initial response:

ASTM F3411 Authentication has really only 3 states: None, Invalid or Valid. This is because under ASTM the idea is that Authentication is done by an external service hosted somewhere on the Internet so you will always get some sort of answer back. With DRIP this classification becomes more complex as we support "offline" scenarios where the receiver does not have Internet connectivity. Since we are using asymmetric keys this means the public key must somehow be obtained - DRIP Registries gets more into detail how these keys are stored on DNS and one reason for DRIP Authentication is to send the key over Broadcast RID.

There are two keys of interest: the PK of the UA and the PK of the HDA (or Registry). The draft gives a clear way to send the PK of the UA over the Broadcast RID messages - however the PK of the Registry is not. It can be using the same mechanism but is not required to do so due to potential operational constraints and implementation of a given UA transmitter. As such there are scenarios where you may have part of the key-chain but not all of it.

The intent of Appendix A is to give some kind of recommended way to classify these various states and convey it to the user through colors and state names/text.

[kc2rxo]

Comment from Bob:

ASTM Authentication has really only 3 states

Remove 'really'