Versions Compared

Old Version 1

changes.mady.by.user John Wunderlich

Saved on

compared with

New Version 2

changes.mady.by.user Hannah Sutor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Participant

Attending

1

Chaudhury, Atef / Krishnaraj, Venkat

X

2

Davis, Peter

X

3

Hughes, Andrew

4

Jones, Thomas

X

5

Thoma, Andreas

6

Wunderlich, John

X

7

Williams, Christopher

Non-Voting

Participant

Attending

1

Auld, Lorrayne

2

Aronson Mark

Moved to non-voting 2023-08-30

3

Balfanz, Dirk

4

Brudnicki, David

5

D'Agostino, Salvatore

X, Moved to non-voting 2023-08-30

6

Dowtin, Jazzmine

7

Dutta, Tim

8

Flanagan, Heather

9

Fleenor, Judith

10

Glasscock, Amy

11

Gropper, Adrian

12

Hodges, Gail

Moved to non-voting 2023-08-30

13

Jordaan, Loffie

14

LeVasseur, Lisa

15

Lopez, Cristina Timon

16

Pasquale, Jim

Moved to non-voting 2023-08-30

17

Snell, Oliver

18

Stowell, Therese

19

Sutor, Hannah

X

20

Tamanini, Greg

21

Vachino, Maria

22

Whysel, Noreen

...

Time

Item

Who

Notes

5 min.

  • Start the meeting.

  • Call to order.

  • Approve minute

  • Approve agenda

John Wunderlich 

Called to order: 13:02

Quorum reached: Yes @ 13:03

Minutes to approve: No objections, Approved (tick)

2023-08-23 Meeting notes - Draft2023-08-09 Meeting notes - Draft2023-08-02 Meeting notes - DraftCandidate Requirements2023-07-19 Meeting notes - Draft2023-07-12 Meeting notes - Draft2023-06-07 Meeting notes - Draft

2023-04-05 Meeting notes - Draft

2023-04-12 Meeting notes - Draft

2023-04-26 Meeting notes - Draft

0 min.

Open Tasks Review

All

Task report
spacesPEMCP
isMissingRequiredParameterstrue
labelsmeeting-notes

5 min

Announcements

Christopher taking lead on next couple of meetings. John to focus on getting implementer’s report out the door.

Ask: Warning for when discussion of implementer’s report will happen so scheduled can be accommodated.

50 min

Requirements discussion

Goal: Get a VIP statement for purpose, legitimacy, and specification.

  • Discussion: Would issuer specify purposes for which credential should be used?

    • Holder should always have final say. If released by the holder, issuer could potentially restrict who gets / asks for one.

    • Terminal authentication is the verifier taking technical steps to ensure that the verifiers reading hardware/software combination meets a certain standard.

      • Identifier of the relying party that the issuer can then build business rules for in their app if their app encounters a typical relying party.

      • Issuer can issue a policy - sometimes the issuer builds the wallet, too. Wallet has credential and policy and has to make decision. Issuer can issue a policy to the wallet.

    • Falls into limiting use into authorized uses, or a security issue around only allowing readers that meet issuer’s standard

    • Issuer says “you must meet policy X” before credential will be issued to device. At presentation time, that authorized wallet uses the information provided to the issuer to validate that the device is on the list that’s in the policy and will provide the data to the reader. (this would be a new set of requirements)

Requirements CoverageCandidate Requirements

30

Wrap up the Implementors report

The report has gone to the group for comment:

Draft for Work Group Comment

5 min.

Other Business


Adjourn


...