< draft-ma-identifier-access-http-03.txt   draft-ma-identifier-access-http-04.txt >
Internet Engineering Task Force C. Ma Internet Engineering Task Force C. Ma
Internet Draft J. Chen Internet Draft J. Chen
Intended status: Informational X. Fan Intended status: Informational X. Fan
Expires: December 21, 2022 M. Chen Expires: June 21, 2022 M. Chen
Z. Li Z. Li
China Academy of Information and Communications Technology China Academy of Information and Communications Technology
June 21, 2021 December 21, 2021
HTTP Usage in the Industrial Internet Identifier Data Access HTTP Usage in the Industrial Internet Identifier Data Access
Protocol (IIIDAP) Protocol (IIIDAP)
draft-ma-identifier-access-http-03 draft-ma-identifier-access-http-04
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on December 21, 2021. This Internet-Draft will expire on June 21, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 49 skipping to change at page 2, line 49
5.1. Positive Answers........................................ 6 5.1. Positive Answers........................................ 6
5.2. Redirects .............................................. 6 5.2. Redirects .............................................. 6
5.3. Negative Answers........................................ 7 5.3. Negative Answers........................................ 7
5.4. Malformed Queries....................................... 7 5.4. Malformed Queries....................................... 7
5.5. Rate Limits ............................................ 8 5.5. Rate Limits ............................................ 8
5.6. Cross-Origin Resource Sharing (CORS).................... 8 5.6. Cross-Origin Resource Sharing (CORS).................... 8
6. Security Considerations...................................... 8 6. Security Considerations...................................... 8
7. Internationalization Considerations.......................... 9 7. Internationalization Considerations.......................... 9
7.1. URIs and IRIs .......................................... 9 7.1. URIs and IRIs .......................................... 9
7.2. Language Identifiers in Queries and Responses........... 9 7.2. Language Identifiers in Queries and Responses........... 9
7.3. Language Identifiers in HTTP Headers .................... 9 7.3. Language Identifiers in HTTP Headers.................... 9
8. IANA Considerations ......................................... 9 8. IANA Considerations ......................................... 9
9. References .................................................. 9 9. References .................................................. 9
9.1. Normative References.................................... 9 9.1. Normative References.................................... 9
9.2. Informative References................................. 10 9.2. Informative References................................. 10
Appendix A. Protocol Example................................... 12 Appendix A. Protocol Example................................... 12
Appendix B. Cache Busting...................................... 13 Appendix B. Cache Busting...................................... 13
Appendix C. Bootstrapping and Redirection...................... 14 Appendix C. Bootstrapping and Redirection...................... 14
1. Introduction 1. Introduction
skipping to change at page 10, line 40 skipping to change at page 10, line 40
Recommendation, REC-cors-20140116, January 2014, Recommendation, REC-cors-20140116, January 2014,
<http://www.w3.org/TR/2014/REC-cors-20140116/>. <http://www.w3.org/TR/2014/REC-cors-20140116/>.
9.2. Informative References 9.2. Informative References
[REST] Fielding, R. and R. Taylor, "Principled Design of the [REST] Fielding, R. and R. Taylor, "Principled Design of the
Modern Web Architecture", ACM Transactions on Internet Modern Web Architecture", ACM Transactions on Internet
Technology, Vol. 2, No. 2, May 2002. Technology, Vol. 2, No. 2, May 2002.
[RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", STD 90, RFC 8259, Interchange Format", STD 90, RFC 8259, DOI
DOI 10.17487/RFC8259, December 2017, 10.17487/RFC8259, December 2017,
<https://www.rfc-editor.org/info/rfc8259>. <https://www.rfc-editor.org/info/rfc8259>.
[IDENTIFIER-SECURITY] [IDENTIFIER-SECURITY]
Ma, C., "Security Services for the Industrial Internet Ma, C., "Security Services for the Industrial Internet
Identifier Data Access Protocol (IIIDAP)", Work in Identifier Data Access Protocol (IIIDAP)", Work in
Progress, draft-mcd-identifier-access-security, June 2021. Progress, draft-mcd-identifier-access-security, December
2021.
[IDENTIFIER-QUERY] [IDENTIFIER-QUERY]
Ma, C., "Industrial Internet Identifier Data Access Ma, C., "Industrial Internet Identifier Data Access
Protocol (IIIDAP) Query Format", Work in Progress, draft- Protocol (IIIDAP) Query Format", Work in Progress, draft-
mcd-identifier-access-query, June 2021. mcd-identifier-access-query, December 2021.
[IDENTIFIER-RESPONSES] [IDENTIFIER-RESPONSES]
Ma, C., "JSON Responses for the Industrial Internet Ma, C., "JSON Responses for the Industrial Internet
Identifier Data Access Protocol (IIIDAP)", Work in Identifier Data Access Protocol (IIIDAP)", Work in
Progress, draft-mcd-identifier-access-response, June 2021. Progress, draft-mcd-identifier-access-response, December
2021.
[IDENTIFIER-AUTHORIZATION] [IDENTIFIER-AUTHORIZATION]
Ma, C., "Finding the Authoritative Registration Data Ma, C., "Finding the Authoritative Registration Data
(IIIDAP) Service", Work in Progress, draft-mcd-identifier- (IIIDAP) Service", Work in Progress, draft-mcd-identifier-
access-authority, June 2021. access-authority, December 2021.
Appendix A. Protocol Example Appendix A. Protocol Example
To demonstrate typical behavior of an IIIDAP client and server, the To demonstrate typical behavior of an IIIDAP client and server, the
following is an example of an exchange, including a redirect. The following is an example of an exchange, including a redirect. The
data in the response has been elided for brevity, as the data format data in the response has been elided for brevity, as the data format
is not described in this document. The media type used here is is not described in this document. The media type used here is
described in [IDENTIFIER-RESPONSES]. described in [IDENTIFIER-RESPONSES].
An example of an IIIDAP client and server exchange: An example of an IIIDAP client and server exchange:
 End of changes. 10 change blocks. 
11 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/