10
10
11
11
<rfc xmlns : xi =" http://www.w3.org/2001/XInclude" submissionType =" IETF"
12
12
category=" info" ipr =" trust200902" xml : lang =" en" version =" 3"
13
- docName=" draft-lemieux-doi-uri-scheme-02 " >
13
+ docName=" draft-lemieux-doi-uri-scheme-03 " >
14
14
<front >
15
15
<title >The "doi" URI Scheme</title >
16
16
17
- <seriesInfo name =" Internet-Draft" value =" draft-lemieux-doi-uri-scheme-02 "
17
+ <seriesInfo name =" Internet-Draft" value =" draft-lemieux-doi-uri-scheme-03 "
18
18
status =" informational" />
19
19
20
20
<author initials =' P.-A.' surname =' Lemieux' fullname =' Pierre-Anthony Lemieux' role =" editor" >
@@ -143,7 +143,8 @@ docName="draft-lemieux-doi-uri-scheme-02" >
143
143
<t ><tt >"https://doi.org/api/handles/" scheme-specific-part</tt ></t >
144
144
145
145
<t >where <tt >scheme-specific-part</tt > is the scheme-specific-part of the
146
- DOI name URI, as defined at <xref target =" doi-name-syntax" />.</t >
146
+ DOI name URI, as defined at <xref target =" doi-name-syntax" />, and the
147
+ "https" scheme is specified at <xref target =" RFC9110" />.</t >
147
148
148
149
<t >The body of the response is a JSON object, as defined at <xref
149
150
target =" RFC8259" />, that contains the following members:</t >
@@ -223,6 +224,22 @@ docName="draft-lemieux-doi-uri-scheme-02" >
223
224
</figure >
224
225
225
226
</section >
227
+
228
+ <section >
229
+ <name >Security Considerations</name >
230
+ <t >A DOI name is an opaque string, which does not have a discernible
231
+ meaning on its own and is for use by humans and machines alike. It
232
+ consists of a sequence of Unicode codepoints and the security
233
+ considerations at <xref target =" UNICODE-TR36" /> apply.</t >
234
+
235
+ <t >The DOI name resolution process is conducted using the Hypertext
236
+ Transfer Protocol Secure, which ensures condifentiality and integrity of
237
+ the transaction, and he security considerations at <xref
238
+ target =" RFC9110" /> apply.</t >
239
+
240
+ <t >The results of the DOI name resolution process is a JSON object and the
241
+ security considerations at <xref target =" RFC8259" /> apply.</t >
242
+ </section >
226
243
</middle >
227
244
228
245
<back >
@@ -252,6 +269,7 @@ docName="draft-lemieux-doi-uri-scheme-02" >
252
269
<xi : include href =" https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml" />
253
270
<xi : include href =" https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3651.xml" />
254
271
<xi : include href =" https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml" />
272
+ <xi : include href =" https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml" />
255
273
</references >
256
274
257
275
<references >
@@ -276,6 +294,14 @@ docName="draft-lemieux-doi-uri-scheme-02" >
276
294
</author >
277
295
</front >
278
296
</reference >
297
+ <reference anchor =" UNICODE-TR36" target =" https://www.unicode.org/reports/tr36/" >
298
+ <front >
299
+ <title >Unicode Security Considerations</title >
300
+ <author >
301
+ <organization >Unicode Consortium</organization >
302
+ </author >
303
+ </front >
304
+ </reference >
279
305
</references >
280
306
</references >
281
307
0 commit comments