Versions Compared

Version Old Version 2 New Version 3
Changes made by

John Wunderlich

John Wunderlich

Saved on

Key

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

...

Participant

Attending

1

Chaudhury, Atef

2

Jones, Thomas

Yes

3

Krishnaraj, Venkat

4

Thoma, Andreas

5

Wunderlich, John

Yes

6

Williams, Christopher

Regrets

...

Participant

Attending

1

Auld, Lorrayne

2

Aronson Mark

3

Balfanz, Dirk

4

Brudnicki, David

5

D'Agostino, Salvatore

6

Davis, Peter

7

Dowtin, Jazzmine

8

Dutta, Tim

9

Flanagan, Heather

10

Fleenor, Judith

11

Glasscock, Amy

12

Graaf, Irene

13

Gropper, Adrian

14

Hodges, Gail

15

Hughes, Andrew

Yes

16

Jordaan, Loffie

Yes

17

LeVasseur, Lisa

18

Lopez, Cristina Timon

19

McBride, Adam

20

Pasquale, Jim

21

Snell, Oliver

22

Stowell, Therese

23

Sutor, Hannah

24

Tamanini, Greg

25

Vachino, Maria

26

Whysel, Noreen

...

Item

Who

Notes

  • Start the meeting.

  • Call to order

  • Approve minutes

  • Approve agenda

John Wunderlich

Called to order: 14:05

Quorum reached: No

Minutes to approve:

2024-11-20 Meeting notes - Draft2024-11-06 Meeting notes - Draft

Open Tasks Review

All

Link to Recommendations (Commenter Link): Recommendations for Privacy Enhancing Mobile Credentials

Task report
spacesPEMCP
createddateFrom01-01-2024
isMissingRequiredParameterstrue

Requirements Analysis

Andrew Hughes

Andrew Hughes has provided an requirements analysis

View file
namePEMC Requirements Report Analysis.docx

Discussion

  • Consider the use of the phrase “Authorized Processing” for the purposes of including consent plus other ways in which processing of credential data may proceed

  • In the context of this document the normal and expected presentation of the credential is a tap (or possibly a QR Code).

    • The only time that credential data may be collected without a tap or without notice would be will a legal authority or by a bad actor - both of which are out of scope

  • Requirements need to be read as a whole for a given actor in a given use case (i.e. an entity can’t pick and choose the requirements that they like.

  • Normative as term should be read as a description of the future state of the system.

Comment Disposition

John Wunderlich

Working throuch comments provided

Discussion

NOTE: Only Kantara Members can vote on approving report for publication. If you or your organisation are not Kantara members and want to vote, you will need to become Kantara members.

Disposition of Comments: PICPR20241010

Implementors and Implementors Guidelines

All

Looking for organisations to volunteer to implement the requirements and self certify. This is a valuble first step towards ensuring that the requirements are practicable and may lead to usefull revisions

Adjourn

...