The proposal KAP-22 moves to "final" but still missing critical elements and still needs to be shaped, including:
- RFC 2119 and RFC 8174 in Specification
- Specification mentions things such as KYC, authentication, and compliance, which are unrelated to the Loyalty Program, should be separated from KAP-22 and addressed as dependencies instead.
- Rationale Why the KAP-22 uses 'period-based'
- Backwards Compatibility KAP-20 is a dependency of KAP-22 must be required in the preamble.
- Reference Implementation
- Security considerations
The proposal KAP-22 moves to "final" but still missing critical elements and still needs to be shaped, including: