Skip to content

Commit 59b21b5

Browse files
committed
Add security section
Bump to version 3
1 parent 082281a commit 59b21b5

File tree

1 file changed

+29
-3
lines changed

1 file changed

+29
-3
lines changed

draft-lemieux-doi-uri-scheme-02.xml

Lines changed: 29 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@
1010

1111
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF"
1212
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" >
1414
<front>
1515
<title>The "doi" URI Scheme</title>
1616

17-
<seriesInfo name="Internet-Draft" value="draft-lemieux-doi-uri-scheme-02"
17+
<seriesInfo name="Internet-Draft" value="draft-lemieux-doi-uri-scheme-03"
1818
status="informational"/>
1919

2020
<author initials='P.-A.' surname='Lemieux' fullname='Pierre-Anthony Lemieux' role="editor">
@@ -143,7 +143,8 @@ docName="draft-lemieux-doi-uri-scheme-02" >
143143
<t><tt>"https://doi.org/api/handles/" scheme-specific-part</tt></t>
144144

145145
<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>
147148

148149
<t>The body of the response is a JSON object, as defined at <xref
149150
target="RFC8259"/>, that contains the following members:</t>
@@ -223,6 +224,22 @@ docName="draft-lemieux-doi-uri-scheme-02" >
223224
</figure>
224225

225226
</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>
226243
</middle>
227244

228245
<back>
@@ -252,6 +269,7 @@ docName="draft-lemieux-doi-uri-scheme-02" >
252269
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
253270
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3651.xml"/>
254271
<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"/>
255273
</references>
256274

257275
<references>
@@ -276,6 +294,14 @@ docName="draft-lemieux-doi-uri-scheme-02" >
276294
</author>
277295
</front>
278296
</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>
279305
</references>
280306
</references>
281307

0 commit comments

Comments
 (0)