| < draft-mcd-identifier-access-responce-03.txt | draft-mcd-identifier-access-responce-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, 2021 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 | |||
| JSON Responses for the Industrial Internet Identifier Data Access | JSON Responses for the Industrial Internet Identifier Data Access | |||
| Protocol (IIIDAP) | Protocol (IIIDAP) | |||
| draft-mcd-identifier-access-responce-03 | draft-mcd-identifier-access-responce-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 43 ¶ | skipping to change at page 2, line 43 ¶ | |||
| 9. Indicating Truncated Responses.............................. 18 | 9. Indicating Truncated Responses.............................. 18 | |||
| 10. IANA Considerations........................................ 20 | 10. IANA Considerations........................................ 20 | |||
| 10.1. IIIDAP JSON Media Type Registration................... 20 | 10.1. IIIDAP JSON Media Type Registration................... 20 | |||
| 11. Security Considerations.................................... 20 | 11. Security Considerations.................................... 20 | |||
| 12. Internationalization Considerations........................ 21 | 12. Internationalization Considerations........................ 21 | |||
| 12.1. Character Encoding.................................... 21 | 12.1. Character Encoding.................................... 21 | |||
| 12.2. URIs and IRIs ........................................ 21 | 12.2. URIs and IRIs ........................................ 21 | |||
| 13. Privacy Considerations..................................... 21 | 13. Privacy Considerations..................................... 21 | |||
| 14. References ................................................ 22 | 14. References ................................................ 22 | |||
| 14.1. Normative References.................................. 22 | 14.1. Normative References.................................. 22 | |||
| 14.2. Informative References................................ 23 | 14.2. Informative References................................ 22 | |||
| 1. Introduction | 1. Introduction | |||
| This document describes responses in the JSON [RFC8259] format for | This document describes responses in the JSON [RFC8259] format for | |||
| the queries as defined by the Industrial Internet Identifier Data | the queries as defined by the Industrial Internet Identifier Data | |||
| Access Protocol Query Format [IDENTIFIER-QUERY]. A communication | Access Protocol Query Format [IDENTIFIER-QUERY]. A communication | |||
| protocol for exchanging queries and responses is described in | protocol for exchanging queries and responses is described in | |||
| [IDENTIFIER-HTTP]. | [IDENTIFIER-HTTP]. | |||
| 1.1. Terminology and Definitions | 1.1. Terminology and Definitions | |||
| skipping to change at page 22, line 48 ¶ | skipping to change at page 22, line 48 ¶ | |||
| <http://www.rfc-editor.org/info/rfc3986>. | <http://www.rfc-editor.org/info/rfc3986>. | |||
| [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying | [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying | |||
| Languages", BCP 47, RFC 5646, September 2009, | Languages", BCP 47, RFC 5646, September 2009, | |||
| <http://www.rfc-editor.org/info/rfc5646>. | <http://www.rfc-editor.org/info/rfc5646>. | |||
| [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010, | [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010, | |||
| <http://www.rfc-editor.org/info/rfc5988>. | <http://www.rfc-editor.org/info/rfc5988>. | |||
| [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>. | |||
| 14.2. Informative References | 14.2. Informative References | |||
| [JSON_ascendancy] | [JSON_ascendancy] | |||
| MacVittie, L., "The Stealthy Ascendancy of JSON", April | MacVittie, L., "The Stealthy Ascendancy of JSON", April | |||
| 2011, <https://devcentral.f5.com/weblogs/macvittie/ | 2011, <https://devcentral.f5.com/weblogs/macvittie/ | |||
| archive/2011/04/27/the-stealthy-ascendancy-of-json.aspx>. | archive/2011/04/27/the-stealthy-ascendancy-of-json.aspx>. | |||
| [JSON_performance_study] | [JSON_performance_study] | |||
| skipping to change at page 23, line 29 ¶ | skipping to change at page 23, line 29 ¶ | |||
| STD 69, RFC 5730, August 2009, <http://www.rfc- | STD 69, RFC 5730, August 2009, <http://www.rfc- | |||
| editor.org/info/rfc5730>. | editor.org/info/rfc5730>. | |||
| [RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type | [RFC6839] Hansen, T. and A. Melnikov, "Additional Media Type | |||
| Structured Syntax Suffixes", RFC 6839, January 2013, | Structured Syntax Suffixes", RFC 6839, January 2013, | |||
| <http://www.rfc-editor.org/info/rfc6839> | <http://www.rfc-editor.org/info/rfc6839> | |||
| [IDENTIFIER-HTTP] | [IDENTIFIER-HTTP] | |||
| Ma, C., "HTTP Usage in the Industrial Internet Identifier | Ma, C., "HTTP Usage in the Industrial Internet Identifier | |||
| Data Access Protocol (IIIDAP)", Work in Progress, draft- | Data Access Protocol (IIIDAP)", Work in Progress, draft- | |||
| ma-identifier-access-http, June 2021. | ma-identifier-access-http, June 2022. | |||
| [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, June 2022. | |||
| [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, June 2022. | |||
| Authors' Addresses | Authors' Addresses | |||
| Chendi Ma | Chendi Ma | |||
| CAICT | CAICT | |||
| No.52 Huayuan North Road, Haidian District | No.52 Huayuan North Road, Haidian District | |||
| Beijing, Beijing, 100191 | Beijing, Beijing, 100191 | |||
| China | China | |||
| Phone: +86 177 1090 9864 | Phone: +86 177 1090 9864 | |||
| End of changes. 9 change blocks. | ||||
| 10 lines changed or deleted | 10 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/ | ||||