...
Future liability across the entire transaction.
Alignment with the European framework and other frameworks.
PKI vs non PKI
Government metadata to prove identification verification.
Registry of “names”
Well-defined requirements for C, B, G.
Terminology (unified terms and plan language).
Simplify attributes bundles documentation (for a next round).
Highlights:
FICAM needs a charter that defines the relationship PKI, TFS and other solutions. Operational procedures: Define the rules.
Revise/update the requirements goal oriented rather than process oriented.
Important to know which FRPs will be the first adopters, level of adoption. What the early adopters will need? So the CSPs can adapt the innovation to that.
...
RPs are asking FICAM to make a mapping of the TFPs with differences and equivalences.
NIST/FICAM. FICAM should lead on discrepancies when NIST requirements are not align with the TFPs. Normalization for interoperability.
Standardize across the frameworks.
FICAM is reviewing the UK model. In the assessments they also include physical check.
OIDF started a working group to profile openid connect for government digital identity transactions. The wg name is iGov and we invite participants to join. The group is co-led by UK GDS, Ping Identity, and NIST.
Next steps:
Charters drafts via hub model.
Matching services.
Coordinate a meeting with the RPs to talk on particular areas.
Meet quarterly – virtual and face-to-face.
Work in demographics.
...