| < draft-ietf-opsawg-ol-00.txt | draft-ietf-opsawg-ol-01.txt > | |||
|---|---|---|---|---|
| Network Working Group E. Lear | Network Working Group E. Lear | |||
| Internet-Draft Cisco Systems | Internet-Draft Cisco Systems | |||
| Updates: 8520 (if approved) C. Bormann | Updates: 8520 (if approved) C. Bormann | |||
| Intended status: Standards Track Universität Bremen TZI | Intended status: Standards Track Universität Bremen TZI | |||
| Expires: 23 April 2022 20 October 2021 | Expires: 26 October 2022 24 April 2022 | |||
| Ownership and licensing statements in YANG | Ownership and licensing statements in YANG | |||
| draft-ietf-opsawg-ol-00 | draft-ietf-opsawg-ol-01 | |||
| Abstract | Abstract | |||
| This memo provides for an extension to RFC 8520 that allows MUD file | This memo provides for an extension to RFC 8520 that allows MUD file | |||
| authors to specify ownership and licensing of MUD files themselves. | authors to specify ownership and licensing of MUD files themselves. | |||
| This memo updates RFC 8520. However, it can also be used for | This memo updates RFC 8520. However, it can also be used for | |||
| purposes outside of MUD, and the grouping is structured as such. | purposes outside of MUD, and the grouping is structured as such. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | 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." | |||
| This Internet-Draft will expire on 23 April 2022. | This Internet-Draft will expire on 26 October 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2022 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 (https://trustee.ietf.org/ | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| license-info) in effect on the date of publication of this document. | license-info) in effect on the date of publication of this document. | |||
| Please review these documents carefully, as they describe your rights | Please review these documents carefully, as they describe your rights | |||
| and restrictions with respect to this document. Code Components | and restrictions with respect to this document. Code Components | |||
| extracted from this document must include Simplified BSD License text | extracted from this document must include Revised BSD License text as | |||
| as described in Section 4.e of the Trust Legal Provisions and are | described in Section 4.e of the Trust Legal Provisions and are | |||
| provided without warranty as described in the Simplified BSD License. | provided without warranty as described in the Revised BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. The owner-license extension and model . . . . . . . . . . . . 3 | 2. The owner-license extension and model . . . . . . . . . . . . 3 | |||
| 3. The YANG schema for ownership and licensing . . . . . . . . . 3 | 3. The YANG schema for ownership and licensing . . . . . . . . . 3 | |||
| 4. Extension for MUD . . . . . . . . . . . . . . . . . . . . . . 5 | 4. Extension for MUD . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 7.1. MUD Extension . . . . . . . . . . . . . . . . . . . . . . 6 | 7.1. MUD Extension . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 8. Normative References . . . . . . . . . . . . . . . . . . . . 6 | 8. Normative References . . . . . . . . . . . . . . . . . . . . 7 | |||
| Appendix A. Changes from Earlier Versions . . . . . . . . . . . 7 | Appendix A. Changes from Earlier Versions . . . . . . . . . . . 7 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 1. Introduction | 1. Introduction | |||
| [RFC8520] Manufacturer Usage Descriptions (MUD) can be used to | [RFC8520] Manufacturer Usage Descriptions (MUD) can be used to | |||
| describe devices and their requirements to the network | describe devices and their requirements to the network | |||
| infrastructure. The original version of the specification does not | infrastructure. The original version of the specification does not | |||
| provide for a means to specify ownership and licensing of the MUD | provide for a means to specify ownership and licensing of the MUD | |||
| file itself. This can hinder those wishing to use, modify, or adapt | file itself. This can hinder those wishing to use, modify, or adapt | |||
| MUD files for the purpose of offering them, when the manufacturer is | MUD files for the purpose of offering them, when the manufacturer is | |||
| not involved. | not involved. | |||
| skipping to change at page 6, line 36 ¶ | skipping to change at page 6, line 36 ¶ | |||
| } | } | |||
| } | } | |||
| * *Task*: need Makefile for validating this against MUD. (Probably | * *Task*: need Makefile for validating this against MUD. (Probably | |||
| put this into a separate file, too.) | put this into a separate file, too.) | |||
| * *Issue*: Should we give an example for usage outside yang? | * *Issue*: Should we give an example for usage outside yang? | |||
| 6. Security Considerations | 6. Security Considerations | |||
| No security considerations have been identified. | The security considerations of Section 16 of [RFC8520] with respect | |||
| to obtaining validation for information claimed in a MUD file do | ||||
| * *Issue*: Should we maybe point out any specific seccons of 8520? | apply. While the information described in this specification is not | |||
| intended to directly influence the behavior of protective | ||||
| infrastructure, it may be used by an aggregator as input for deciding | ||||
| the legal basis that enables providing aggregated information; | ||||
| depending on the juridical environment, false information in the MUD | ||||
| file may thus expose the aggregator to additional legal risk. | ||||
| 7. IANA Considerations | 7. IANA Considerations | |||
| 7.1. MUD Extension | 7.1. MUD Extension | |||
| The IANA is requested to add "ol" to the MUD extensions registry as | The IANA is requested to add "ol" to the MUD extensions registry of | |||
| follows: | [IANA.mud] as follows: | |||
| Extension Name: ol | Extension Name: | |||
| Standard reference: This document | ||||
| ol | ||||
| Standard reference: | ||||
| This document | ||||
| 8. Normative References | 8. Normative References | |||
| [IANA.mud] IANA, "Manufacturer Usage Description (MUD)", | ||||
| <https://www.iana.org/assignments/mud>. | ||||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
| DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
| <https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| [RFC8520] Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage | [RFC8520] Lear, E., Droms, R., and D. Romascanu, "Manufacturer Usage | |||
| Description Specification", RFC 8520, | Description Specification", RFC 8520, | |||
| DOI 10.17487/RFC8520, March 2019, | DOI 10.17487/RFC8520, March 2019, | |||
| <https://www.rfc-editor.org/info/rfc8520>. | <https://www.rfc-editor.org/info/rfc8520>. | |||
| [SPDX] The Linux Foundation, "SPDX Specification 2.1", 2016. | [SPDX] The Linux Foundation, "SPDX Specification 2.1", 2016. | |||
| Appendix A. Changes from Earlier Versions | Appendix A. Changes from Earlier Versions | |||
| Draft -01: | ||||
| * Format IANA considerations | ||||
| * Discuss security considerations | ||||
| Draft -00: | Draft -00: | |||
| * Resubmit unchanged | * Resubmit unchanged | |||
| Individual Draft -01: | Individual Draft -01: | |||
| * Add some issues | * Add some issues | |||
| * correct spacing | * correct spacing | |||
| End of changes. 12 change blocks. | ||||
| 16 lines changed or deleted | 34 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/ | ||||