aboutsummaryrefslogtreecommitdiff
path: root/draft-schanzen-reclaimid.xml
blob: 4776d4690e785b9edda8f756839d044ba401fa1d (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent" [
<!ENTITY RFC1034 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1034.xml">
<!ENTITY RFC1035 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1035.xml">
<!ENTITY RFC2119 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2782 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2782.xml">
<!ENTITY RFC3629 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml">
<!ENTITY RFC3686 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3686.xml">
<!ENTITY RFC3826 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3826.xml">
<!ENTITY RFC3912 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3912.xml">
<!ENTITY RFC5869 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5869.xml">
<!ENTITY RFC5890 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml">
<!ENTITY RFC5891 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml">
<!ENTITY RFC6781 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6781.xml">
<!ENTITY RFC6895 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6895.xml">
<!ENTITY RFC6979 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6979.xml">
<!ENTITY RFC7748 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7748.xml">
<!ENTITY RFC8032 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8032.xml">
<!ENTITY RFC8126 PUBLIC '' "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="info" docName="draft-schanzen-reclaimid-00" ipr="trust200902" obsoletes="" updates="" submissionType="IETF" xml:lang="en" version="3">
 <!-- xml2rfc v2v3 conversion 2.26.0 -->
 <front>
  <title abbrev="reclaimid">
   re:claimID - A System for Self-sovereign, Decentralised Identity Management and Personal Data Sharing
  </title>
  <seriesInfo name="Internet-Draft" value="draft-schanzen-reclaimid-00"/>
  <author fullname="Martin Schanzenbach" initials="M." surname="Schanzenbach">
   <organization>GNUnet e.V.</organization>
   <address>
    <postal>
     <street>Boltzmannstrasse 3</street>
     <city>Garching</city>
     <code>85748</code>
     <country>DE</country>
    </postal>
    <email>schanzen@gnunet.org</email>
   </address>
  </author>
  <author fullname="Christian Grothoff" initials="C." surname="Grothoff">
   <organization>Berner Fachhochschule</organization>
   <address>
    <postal>
     <street>Hoeheweg 80</street>
     <city>Biel/Bienne</city>
     <code>2501</code>
     <country>CH</country>
    </postal>
    <email>grothoff@gnunet.org</email>
   </address>
  </author>

  <!-- Meta-data Declarations -->
  <area>General</area>
  <workgroup>Independent Stream</workgroup>
  <keyword>identity management</keyword>
  <abstract>
   <t>This document contains the re:claimID technical specification.</t>
  </abstract>
 </front>
 <middle>
   <section anchor="introduction" numbered="true" toc="default">
     <name>Introduction</name>
     <t>
       re:claimID is a decentralized, self-sovereign identity management
       system. It allows users to be in control over their digital identities
       without having to rely on central identity provider services (IdPs) in
       order to share personal data.
     </t>
     <t>
       re:claimID is built upon the GNU Name System <xref target="GNS"/>
       for data sharing and storage.
       It leverages the zone privacy and key blinding properties of the name
       system in order to provide a secure sharing and authorization mechanism.
     </t>
     <t>
       The system supports both "self-asserted" as well as third party asserted
       identity attributes. The assertion mechanisms are out of scope of this
       document.
     </t>
     <t>
       The re:claimID system can used and integrated into the OpenID Connect
       protocol.
     </t>
     <t>
       This document defines the normative wire format of resource records, resolution processes,
       cryptographic routines and security considerations for use by implementors.
     </t>
     <t>
       The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
       "OPTIONAL" in this document are to be interpreted as described
       in <xref target="RFC2119"/>.
     </t>
   </section>
   <section anchor="identities" numbered="true" toc="default">
     <name>Identities</name>
     <t>
       An identity in re:claimID is defined through a zone in GNS.
       As such, the creation of a zone in GNS implicitly also creates
       a re:claimID identity.
     </t>
     <section anchor="attributes" numbered="true" toc="default">
       <name>Attributes</name>
       <t>
         A re:claimID identity attribute is stored in GNS under records
         of type "RECLAIM_ATTRIBUTE". An attribute consists of an identifier,
         an optional attestation identifier, a type, a flag, a name and data.
         The record format of a RECLAIM_ATTRIBUTE is as follows:
       </t>
         <figure anchor="figure_gnsattribute">
           <artwork name="" type="" align="left" alt=""><![CDATA[
0     8     16    24    32    40    48    56
+-----+-----+-----+-----+-----+-----+-----+-----+
|         TYPE          |         FLAG          |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                      ID                       |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                    ATTESTATION                |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
|         NSIZE         |          DSIZE        |
+-----+-----+-----+-----+-----+-----+-----+-----+
/                  NAME + DATA                  /
/                                               /
+-----------------------------------------------+
             ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
         <t>
           where:
         </t>
         <dl>
           <dt>TYPE</dt>
           <dd>
             Is the 32 bit attribute type as defined in the GANA registry.
           </dd>
           <dt>FLAG</dt>
           <dd>
             Is a 32 bit attribute flag combination as defined in the GANA registry
           </dd>
           <dt>ID</dt>
           <dd>
             Is a 256 bit attribute identifier.
           </dd>
           <dt>ATTESTATION</dt>
           <dd>
             Is the 256 bit credential identifier which asserts this attribute.
             0 means no attestation.
           </dd>
           <dt>NSIZE</dt>
           <dd>
             32 bit length of the attribute name in bytes.
           </dd>
           <dt>DSIZE</dt>
           <dd>
             32 bit length of the attribute data.
           </dd>
           <dt>NAME</dt>
           <dd>
             The attribute name. A UTF-8 string with NULL byte at the end.
           </dd>
           <dt>DATA</dt>
           <dd>
             The attribute data.
           </dd>
         </dl>
     </section>
     <section anchor="credentials" numbered="true" toc="default">
       <name>Credentials</name>
       <t>
         A re:claimID credential is stored in GNS under records
         of type "RECLAIM_CREDENTIAL". A credential consists of an identifier,
         a type, a flag, a name and data.
         The record format of a RECLAIM_CREDENTIAL is as follows:
       </t>
         <figure anchor="figure_gnscred">
           <artwork name="" type="" align="left" alt=""><![CDATA[
0     8     16    24    32    40    48    56
+-----+-----+-----+-----+-----+-----+-----+-----+
|         TYPE          |         FLAG          |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                      ID                       |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
|         NSIZE         |          DSIZE        |
+-----+-----+-----+-----+-----+-----+-----+-----+
/                  NAME + DATA                  /
/                                               /
+-----------------------------------------------+
             ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
         <t>
           where:
         </t>
         <dl>
           <dt>TYPE</dt>
           <dd>
             Is the 32 bit credential type as defined in the GANA registry.
           </dd>
           <dt>FLAG</dt>
           <dd>
             Is a 32 bit credential flag combination as defined in the GANA registry
           </dd>
           <dt>ID</dt>
           <dd>
             Is a 256 bit credential identifier.
           </dd>
           <dt>NSIZE</dt>
           <dd>
             32 bit length of the credential name in bytes.
           </dd>
           <dt>DSIZE</dt>
           <dd>
             32 bit length of the credential data.
           </dd>
           <dt>NAME</dt>
           <dd>
             The credential name. A UTF-8 string with NULL byte at the end.
           </dd>
           <dt>DATA</dt>
           <dd>
             The credential data.
           </dd>
         </dl>
    </section>
    <section anchor="tickets" numbered="true" toc="default">
      <name>Tickets</name>
      <t>
        In order to share a set of identity attributes with a third party,
        re:claimID introduces the concept of "Tickets". A Ticket may be
        issued by a user for an identity to a relying party.
        The Ticket may then be used by the relying party to retrieve the
        shared attributes from the name system.
        The record wire format of a Ticket is as follows:
      </t>
       <figure anchor="figure_ticket">
         <artwork name="" type="" align="left" alt=""><![CDATA[
0     8     16    24    32    40    48    56
+-----+-----+-----+-----+-----+-----+-----+-----+
|      IDENTITY TYPE    |       IDENTITY        |
+-----------------------+                       |
|                       +-----------------------|
|                       |    AUDIENCE TYPE      |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                    AUDIENCE                   |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                      TID                      |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
             ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
       </figure>
       <t>
         where:
       </t>
       <dl>
         <dt>IDENTITY TYPE</dt>
         <dd>
           Is the 32 bit identity type as defined in GANA for GNS
           identity zone types (e.g. PKEY).
         </dd>
         <dt>IDENTITY</dt>
         <dd>
           Is the 256 bit identity public zone key of the user.
         </dd>
         <dt>AUDIENCE TYPE</dt>
         <dd>
           Is the 32 bit audience type as defined in GANA for GNS
           identity zone types (e.g. PKEY).
         </dd>
         <dt>AUDIENCE</dt>
         <dd>
           Is the 256 bit audience public zone key of the relying party.
         </dd>
         <dt>TID</dt>
         <dd>
           Is a 256 bit ticket identifier.
         </dd>
       </dl>
       <t>
         The TID essentially serves as a shared secret between user and
         relying party. knowledge of the IDENTITY key and the TID allows
         the relying party to iteratively query attribute data in GNS.
         Tickets are stored as RECLAIM_TICKET records under a label derived
         from the TID by applying a Base64-encoding. In addition to the ticket,
         the record set also contains references to the shared attributes as
         well as any credential presentations which attest attribute values.
      </t>
      <section anchor="attrrefs" numbered="true" toc="default">
        <name>Attribute References</name>
       <t>
         An attribute reference is stored in GNS under records
         of type "RECLAIM_ATTRIBUTE_REF". An attribute reference
         is stored in GNS under a label derived from a ticket ID.
         The reference points to an actual attribute ID.
         The record format of a RECLAIM_ATTRIBUTE_REF is as follows:
       </t>
         <figure anchor="figure_gnsattrref">
           <artwork name="" type="" align="left" alt=""><![CDATA[
0     8     16    24    32    40    48    56
+-----+-----+-----+-----+-----+-----+-----+-----+
|                 ATTRIBUTE ID                  |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
             ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
         <t>
           where:
         </t>
         <dl>
           <dt>ATTRIBUTE ID</dt>
           <dd>
             Is the 256 bit attribute ID of an existing attribute.
           </dd>
         </dl>
      </section>
      <section anchor="credpres" numbered="true" toc="default">
        <name>Credential Presentations</name>
       <t>
         A re:claimID presentation is stored in GNS under records
         of type "RECLAIM_PRESENTATION". A presentation is derived from a
         credential and may contain only a subset of the attestations.
         The presentation construct is used to support selective disclosure
         of third party issued credentials. It consists of
         a type, a flag, a name and data.
         The record format of a RECLAIM_PRESENTATION is as follows:
       </t>
         <figure anchor="figure_gnspres">
           <artwork name="" type="" align="left" alt=""><![CDATA[
0     8     16    24    32    40    48    56
+-----+-----+-----+-----+-----+-----+-----+-----+
|         TYPE          |         FLAG          |
+-----+-----+-----+-----+-----+-----+-----+-----+
|                      ID                       |
|                                               |
|                                               |
|                                               |
+-----+-----+-----+-----+-----+-----+-----+-----+
|         NSIZE         |          DSIZE        |
+-----+-----+-----+-----+-----+-----+-----+-----+
/                  NAME + DATA                  /
/                                               /
+-----------------------------------------------+
             ]]></artwork>
           <!--        <postamble>which is a very simple example.</postamble>-->
         </figure>
         <t>
           where:
         </t>
         <dl>
           <dt>TYPE</dt>
           <dd>
             Is the 32 bit presentation type as defined in the GANA registry.
           </dd>
           <dt>FLAG</dt>
           <dd>
             Is a 32 bit presentation flag combination as defined in the GANA registry
           </dd>
           <dt>ID</dt>
           <dd>
             Is a 256 bit credential identifier.
           </dd>
           <dt>NSIZE</dt>
           <dd>
             32 bit length of the presentation name in bytes.
           </dd>
           <dt>DSIZE</dt>
           <dd>
             32 bit length of the credential data.
           </dd>
           <dt>NAME</dt>
           <dd>
             The credential name. A UTF-8 string with NULL byte at the end.
           </dd>
           <dt>DATA</dt>
           <dd>
             The credential data.
           </dd>
         </dl>

      </section>
    </section>
  </section>
   <section anchor="access" numbered="true" toc="default">
     <name>Access Management</name>
     <section anchor="authorization" numbered="true" toc="default">
       <name>Authorization</name>
     </section>
     <section anchor="revocation" numbered="true" toc="default">
       <name>Revocation</name>
     </section>
   </section>
   <section anchor="openid" numbered="true" toc="default">
     <name>OpenID Connect Integration</name>
     <section anchor="openidclientreg" numbered="true" toc="default">
       <name>Client Registration</name>
     </section>
     <section anchor="AuthorizationCode" numbered="true" toc="default">
       <name>Authorization Code</name>
     </section>
     <section anchor="IDToken" numbered="true" toc="default">
       <name>ID Token</name>
     </section>
     <section anchor="UserinfoEndpoint" numbered="true" toc="default">
       <name>Userinfo Endpoint</name>
     </section>

   </section>
   <section anchor="encoding" numbered="true" toc="default">
     <name>Internationalization and Character Encoding</name>
     <t>
         All attribute names in re:claimID are encoded in UTF-8
       <xref target="RFC3629" />.
     </t>
   </section>

   <section anchor="security" numbered="true" toc="default">
     <name>Security Considerations</name>
   </section>
   <section anchor="gana" numbered="true" toc="default">
       <name>GANA Considerations</name>
       <t>
         GANA is requested to populate this registry as follows:
       </t>
       <figure anchor="figure_rrtypenums">
         <artwork name="" type="" align="left" alt=""><![CDATA[
Number: 65549
Name: RECLAIM_TICKET
Contact: N/A
References: [This.I-D]
Description: Ticket

Number: 65549
Name: RECLAIM_ATTRIBUTE
Contact: N/A
References: [This.I-D]
Description: Identity attribute

Number: 65550
Name: RECLAIM_ATTRIBUTE_REF
Contact: N/A
References: [This.I-D]
Description: Refrerence to identity attribute

Number: 65551
Name: RECLAIM_OIDC_CLIENT
Contact: N/A
References: [This.I-D]
Description: OIDC client description

Number: 65552
Name: RECLAIM_OIDC_REDIRECT
Contact: N/A
References: [This.I-D]
Description: OIDC client redirect(s)

Number: 65553
Name: RECLAIM_CREDENTIAL
Contact: N/A
References: [This.I-D]
Description: Credential

Number: 65554
Name: RECLAIM_PRESENTATION
Contact: N/A
References: [This.I-D]
Description: Credential presentation
           ]]></artwork>
       </figure>
       <t>
         GANA is requested to amend the "GNUnet Signature Purpose" registry
         as follows:
       </t>
       <figure anchor="figure_purposenums">
         <artwork name="" type="" align="left" alt=""><![CDATA[
Purpose: 27
Name: RECLAIM_CODE_SIGN
References: [This.I-D]
Description: Signature in OIDC authorization code
           ]]></artwork>
       </figure>
     </section>
     <!-- gana -->
     <section>
       <name>Test Vectors</name>
     </section>
   </middle>
   <back>
     <references>
       <name>Normative References</name>

       &RFC2119;
       &RFC3629;

       <reference anchor="GNS" target="https://lsd.gnunet.org/lsd0001">
         <front>
           <title>The GNU Name System</title>
          <author initials="M." surname="Schanzenbach" fullname="Martin Schanzenbach">
            <organization>GNUnet e.V.</organization>
          </author>

          <author initials="C." surname="Grothoff" fullname="Christian Grothoff">
            <organization>GNUnet e.V.</organization>
          </author>

          <author initials="B." surname="Fix"
            fullname="Bernd Fix">
            <organization>GNUnet e.V.</organization>
          </author>
           <date year="2020" month="March"/>
         </front>
       </reference>
     </references>
   </back>
 </rfc>