Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consent Receipt ID (v1.1.0 draft 3, section 4.1) #107

Open
hlflanagan opened this issue Sep 11, 2017 · 3 comments
Open

Consent Receipt ID (v1.1.0 draft 3, section 4.1) #107

hlflanagan opened this issue Sep 11, 2017 · 3 comments

Comments

@hlflanagan
Copy link

Is the unique number for each consent receipt something that needs to be unique globally, or unique for the issuing organization? The use of RFC 4122 suggests the former, but the spec doesn't describe how URNs will be registered or assigned.

@ShanChathusanda93
Copy link

Adding to the above question, Is that consent receipt id is valid only for the corresponding receipt or it is an unique id for the pii principal?
Thanks.

@dturnerx
Copy link

dturnerx commented Oct 2, 2017

The purpose of the consent receipt id is to uniquely identify each receipt within the scope of a particular implementation or domain. We recommend using RFC 4122 because it is well established and well understood. There is no need to register these as URNs.

@ShanChathusanda93
Copy link

So, when an user gets a consent receipt twice within the scope,should it be two consent receipt ids or one id for both receipts?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants