Repository navigation
ANP 1.2 Release
ANP 1.2 is the current specification-set release. It promotes the previously frozen vNext drafts into their canonical document paths. This is a documentation release: it does not change SDK, service, or product implementations, and it does not authorize public capability advertisement.
Highlights
-
ANP-02 as the common authentication entry
Adds the released DID-method-independent HTTP/JSON authentication specification fordid:wbaand nativedid:web. Onboarding and reader entry now point to ANP-02, not ANP-03. -
Promote core identity and naming specs
Promotes ANP-03 (WBA method rules and identity continuity), ANP-04 (WNS), and Appendix B (nativedid:webintegration) from vNext into the current English and Chinese documents. Aligns the white paper, ANP-07, ANP-08, ANP-09, and Appendix A with the 1.2 catalog. -
Messaging 1.2
Promotes all nine messaging documents (P1–P9, English and Chinese) intomessage/andchinese/message/, with a Messaging 1.2 index. The specification-set version is 1.2; Profile wire identifiers are not globally renumbered:- P1 / P2 / P3 / P7 / P8 remain
.v1 - P9 remains a v1 binding extension without an independent
meta.profile - P4 / P5 / P6 keep the
.v2contracts already defined in vNext
- P1 / P2 / P3 / P7 / P8 remain
Status notes
- ANP-06 remains a draft. Document version 1.2 does not change its draft status or the
anp.meta.negotiation.v1wire identifier. - P6 Group E2EE remains a candidate. Stable v2 still requires a registered MLS
ExtensionType; provisional0xF0A1is not a completed registration. - AP2 / ANP-10 English metadata is corrected to
Draft / not releasedso it matches the existing draft title and opening text. English document version remains 1.1; Chinese remains 0.1. Payment flows are unchanged. - Former
vNext/indexes are historical archives that point at the current documents. Snapshot bodies are unchanged.
Versioning note
Version: 1.2 identifies the specification/document release version, not a wire version. Profile identifiers, protocolVersion, interface versions, algorithms, and signature/AAD formats follow their owning specifications and are not globally renumbered.
Publication of specifications does not mean implementations already support ANP 1.2, and it does not enable public discovery of draft or candidate capabilities.
Source
- Spec promotion PR: #98