Cisco Systems

Richtistrasse 7 Wallisellen 8304 Switzerland +41 44 878 9200 lear@cisco.com

NIST

100 Bureau Dr. Gaithersburg MD 20899 United States of America +1 301-975-8439 scott.rose@nist.gov

ops opsawg sbom discovery mud vex chaff To improve cybersecurity posture, automation is necessary to locate the software a device is using, whether that software has known vulnerabilities, and what, if any, recommendations suppliers may have. This memo extends the Manufacturer User Description (MUD) YANG schema to provide the locations of software bills of materials (SBOMs) and vulnerability information by introducing a transparency schema.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
  • .  Requirements Language
  • .  How This Information Is Retrieved
  • .  Formats
• .  The Well-Known Transparency Endpoint Set
• .  The mud-transparency Extension
• .  The mud-sbom Augmentation to the MUD YANG Data Model
• .  Examples
  • .  Without ACLS
  • .  SBOM Located on the Device
  • .  Further Contact Required
  • .  With ACLS
• .  Security Considerations
• .  IANA Considerations
  • .  MUD Extension
  • .  YANG Registration
  • .  Well-Known Prefix
• .  References
  • .  Normative References
  • .  Informative References
• Acknowledgments
• Authors' Addresses

Introduction A number of activities have taken place to improve the visibility of what software is running on a system and what vulnerabilities that software may have . Put simply, this memo seeks to answer two classes of questions for tens of thousands of devices and a large variety of device types. Those questions are as follows:

• Is this system susceptible to a particular vulnerability?
• Which devices in a particular environment contain vulnerabilities that require some action?

This memo doesn't specify the format of this information but rather only how to locate and retrieve these objects. That is, the model is intended to facilitate discovery and on its own provides no access to the underlying data. Software bills of materials (SBOMs) are descriptions of what software, including versioning and dependencies, a device contains. There are different SBOM formats such as Software Package Data Exchange or CycloneDX . System vulnerabilities may be similarly described using several data formats, including the aforementioned CycloneDX, the Common Vulnerability Reporting Framework , and the Common Security Advisory Format . This information is typically used to report the state of any known vulnerabilities on a system to administrators. SBOM and vulnerability information can be used in concert with other sources of vulnerability information. A network management tool could discover that a system uses a particular set of software components, searches a national vulnerability database to determine known vulnerabilities, and applies information provided by the manufacturer through this mechanism to produce a vulnerability report. That report may be used to indicate what, if any, versions of software correct that vulnerability or whether the system exercises the vulnerable code at all. Both classes of information elements are optional under the model specified in this memo. One can provide only an SBOM, only vulnerability information, or both an SBOM and vulnerability information. Note that SBOM formats may also carry other information, the most common being any licensing terms. Because this specification is neutral regarding content, it is left for format developers such as the Linux Foundation, OASIS, and ISO to decide what attributes they will support. This memo does not specify how vulnerability information may be retrieved directly from the endpoint. That is because vulnerability information changes occur to software updates at different rates. However, some SBOM formats may also contain vulnerability information. SBOMs and vulnerability information are advertised and retrieved through the use of a YANG augmentation of the Manufacturer User Description (MUD) model . Note that the schema creates a grouping that can also be used independently of MUD. Moreover, other MUD features, such as access controls, needn't be present. The mechanisms specified in this document are meant to address two use cases:

• A network-layer management system retrieving information from an Internet of Things (IoT) device as part of its ongoing life cycle. Such devices may or may not have query interfaces available.
• An application-layer management system retrieving vulnerability or SBOM information in order to evaluate the posture of an application server of some form. These application servers may themselves be containers or hypervisors. Discovery of the topology of a server is beyond the scope of this memo.

To satisfy these two key use cases, objects may be found in one of three methods:

1. on the devices themselves
2. on a website (e.g., via a URI)
3. through some form of out-of-band contact with the supplier

Using the first method, devices will have interfaces that permit direct retrieval. Examples of these interfaces might be an HTTP or Constrained Application Protocol (CoAP) endpoint for retrieval. There may also be private interfaces as well. Using the second method, when a device does not have an appropriate retrieval interface, but one is directly available from the manufacturer, a URI to that information is discovered through interfaces such as MUD via DHCP or bootstrapping and ownership transfer mechanisms. Using the third method, a supplier may wish to make an SBOM or vulnerability information available under certain circumstances and may need to individually evaluate requests. The result of that evaluation might be the SBOM, the vulnerability itself, a restricted URL, or no access. To enable application-layer discovery, this memo defines a well-known URI . Management or orchestration tools can query this well-known URI to retrieve a system's SBOM information. Further queries may be necessary based on the content and structure of the response.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

How This Information Is Retrieved describes a data model to extend the MUD file format to carry SBOM and vulnerability information. describes mechanisms by which devices can emit a URL to point to this file. Additionally, devices can share this URL either through documentation or within a QR code on a box. describes a well-known URL from which an SBOM could be served from the local device. Note that vulnerability and SBOM information are likely to change at different rates. MUD's cache-validity node provides a way for manufacturers to control how often tooling should check for those changes through the cache-validity node.

Formats There are multiple ways to express both SBOMs and vulnerability information. When these are retrieved either from the device or from a remote web server, tools will need to observe the Content-Type header to determine precisely which format is being transmitted. Because IoT devices in particular have limited capabilities, use of a specific Accept: header in HTTP or the Accept Option in CoAP is NOT RECOMMENDED. Instead, backend tooling is encouraged to support all known formats and SHOULD silently discard SBOM information sent with a media type that is not understood. If multiple SBOMs are intended to be supported in the same file, the media type should properly reflect that. For example, one might make use of application/{someformat}+json-seq. It is left to those supporting those formats to make the appropriate registrations in this case. Some formats may support both vulnerability and software inventory information. When both vulnerability and software inventory information is available from the same URL, both sbom-url and members of the vuln-url list MUST indicate that. Network management systems MUST take note of when the SBOM and vulnerability information are accessible via the same resource and not retrieve the resource a second time.

The Well-Known Transparency Endpoint Set A well-known endpoint is defined: "/.well-known/sbom" retrieves an SBOM As discussed previously, the precise format of a response is based on the Content-Type provided.

The mud-transparency Extension We now formally define the mud-transparency extension; this is done in two parts. First, the extension name "transparency" is listed in the "extensions" array of the MUD file. Note that this schema extension is intended to be used wherever it might be appropriate (e.g., not just with MUD). Second, the "mud" container is augmented with a list of SBOM sources. This is done as follows: module: ietf-mud-transparency augment /mud:mud: +--rw transparency +--rw (sbom-retrieval-method)? | +--:(cloud) | | +--rw sboms* [version-info] | | +--rw version-info string | | +--rw sbom-url? inet:uri | +--:(local-well-known) | | +--rw sbom-local-well-known? identityref | +--:(sbom-contact-info) | +--rw sbom-contact-uri? inet:uri +--rw sbom-archive-list? inet:uri +--rw (vuln-retrieval-method)? +--:(cloud) | +--rw vuln-url* inet:uri +--:(vuln-contact-info) +--rw vuln-contact-uri? inet:uri See for a description of YANG trees.

The mud-sbom Augmentation to the MUD YANG Data Model This YANG module references , , , , and . module ietf-mud-transparency { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mud-transparency"; prefix mudtx; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-mud { prefix mud; reference "RFC 8520: Manufacturer Usage Description Specification"; } organization "IETF OPSAWG (Ops Area) Working Group"; contact "WG Web: <https://datatracker.ietf.org/wg/opsawg/> WG List: <opsawg@ietf.org> Editor: Eliot Lear <lear@cisco.com> Editor: Scott Rose <scott.rose@nist.gov>"; description "This YANG module augments the ietf-mud model to provide for reporting of SBOMs and vulnerability information. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 9472 (https://www.rfc-editor.org/info/rfc9472); see the RFC itself for full legal notices."; revision 2023-10-10 { description "Initial proposed standard."; reference "RFC 9472: A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information"; } identity local-type { description "Base identity for local well-known choices."; } identity http { base mudtx:local-type; description "Use http (RFC 7231) (insecure) to retrieve SBOM information. This method is NOT RECOMMENDED but may be unavoidable for certain classes of deployment where TLS has not or cannot be implemented."; reference "RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"; } identity https { base mudtx:local-type; description "Use https (secure) to retrieve SBOM information. See RFC 9110."; reference "RFC 9110: HTTP Semantics"; } identity coap { base mudtx:local-type; description "Use COAP (RFC 7252) (insecure) to retrieve SBOM. This method is NOT RECOMMENDED, although it may be unavoidable for certain classes of implementations/deployments."; reference "RFC 7252: The Constrained Application Protocol (CoAP)"; } identity coaps { base mudtx:local-type; description "Use COAPS (secure) to retrieve SBOM (RFC 7252)."; } grouping transparency-extension { description "This grouping provides a means to describe the location of software bills of material and vulnerability descriptions."; container transparency { description "Container of methods to get SBOMs and vulnerability information."; choice sbom-retrieval-method { description "How to find SBOM information."; case cloud { list sboms { key "version-info"; description "A list of SBOMs tied to different software or hardware versions."; leaf version-info { type string; description "The version to which this SBOM refers."; } leaf sbom-url { type inet:uri { pattern '((coaps?)|(https?)):.*'; } description "A statically located URL."; } } } case local-well-known { leaf sbom-local-well-known { type identityref { base mudtx:local-type; } description "Which communication protocol to choose."; } } case sbom-contact-info { leaf sbom-contact-uri { type inet:uri { pattern '((mailto)|(https?)|(tel)):.*'; } description "This MUST be a tel, an http, an https, or a mailto uri schema that customers can use to contact someone for SBOM information."; } } } leaf sbom-archive-list { type inet:uri; description "This URI returns a JSON list of URLs that consist of SBOMs that were previously published for this device. Publication dates can be found inside the SBOMs."; } choice vuln-retrieval-method { description "How to find vulnerability information."; case cloud { leaf-list vuln-url { type inet:uri; description "List of statically located URLs that reference vulnerability information."; } } case vuln-contact-info { leaf vuln-contact-uri { type inet:uri { pattern '((mailto)|(https?)|(tel)):.*'; } description "This MUST be a tel, an http, an https, or a mailto uri schema that customers can use to contact someone for vulnerability information."; } } } } } augment "/mud:mud" { description "Add extension for software transparency."; uses transparency-extension; } }

Examples In this example MUD file that uses a cloud service, the modelX presents a location of the SBOM in a URL. Note that the Access Control Lists (ACLs) in a MUD file are NOT required, although they are a very good idea for IP-based devices.

Without ACLS This first MUD file demonstrates how to get SBOM and vulnerability information without ACLs. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { sboms: [ { "version-info": "1.2", "sbom-url": "https://iot.example.com/info/modelX/sbom.json" } ], "vuln-url" : [ "https://iotd.example.com/info/modelX/csaf.json" ] }, "mud-url": "https://iot.example.com/modelX.json", "mud-signature": "https://iot.example.com/modelX.p7s", "last-update": "2022-01-05T13:29:12+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "retrieving vuln and SBOM info via a cloud service", "mfg-name": "Example, Inc.", "documentation": "https://iot.example.com/doc/modelX", "model-name": "modelX" } } The second example demonstrates that just SBOM information is included from the cloud. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { sboms: [ { "version-info": "1.2", "sbom-url": "https://iot.example.com/info/modelX/sbom.json" } ], }, "mud-url": "https://iot.example.com/modelX.json", "mud-signature": "https://iot.example.com/modelX.p7s", "last-update": "2022-01-05T13:29:12+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "retrieving vuln and SBOM info via a cloud service", "mfg-name": "Example, Inc.", "documentation": "https://iot.example.com/doc/modelX", "model-name": "modelX" } }

SBOM Located on the Device In the next example, the SBOM is located on the device, and there is no vulnerability information provided. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { "sbom-local-well-known": "https" }, "mud-url": "https://iot.example.com/modelX.json", "mud-signature": "https://iot.example.com/modelX.p7s", "last-update": "2022-01-05T13:29:47+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "retrieving SBOM info from a local source", "mfg-name": "Example, Inc.", "documentation": "https://iot.example.com/doc/modelX", "model-name": "modelX" } } In this example, the SBOM is retrieved from the device, while vulnerability information is available from the cloud. This is likely a common case because vendors may learn of vulnerability information more frequently than they update software. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { "sbom-local-well-known": "https", "vuln-url" : [ "https://iotd.example.com/info/modelX/csaf.json" ] }, "mud-url": "https://iot-device.example.com/modelX.json", "mud-signature": "https://iot-device.example.com/modelX.p7s", "last-update": "2022-01-05T13:25:14+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "mixed example: SBOM on device, vuln info in cloud", "mfg-name": "Example, Inc.", "documentation": "https://iot-device.example.com/doc/modelX", "model-name": "modelX" } }

Further Contact Required In this example, the network manager must take further steps to retrieve SBOM information. Vulnerability information is still available. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { "contact-info": "https://iot-device.example.com/contact-info.html", "vuln-url" : [ "https://iotd.example.com/info/modelX/csaf.json" ] }, "mud-url": "https://iot-device.example.com/modelX.json", "mud-signature": "https://iot-device.example.com/modelX.p7s", "last-update": "2021-07-09T06:16:42+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "retrieving vuln and SBOM info via a cloud service", "mfg-name": "Example, Inc.", "documentation": "https://iot-device.example.com/doc/modelX", "model-name": "modelX" } }

With ACLS Finally, here is a complete example where the device provides SBOM and vulnerability information as well as access control information. { "ietf-mud:mud": { "mud-version": 1, "extensions": [ "transparency" ], "mudtx:transparency": { "sbom-local-well-known": "https", "vuln-url" : [ "https://iotd.example.com/info/modelX/csaf.json" ] }, "mud-url": "https://iot.example.com/modelX.json", "mud-signature": "https://iot.example.com/modelX.p7s", "last-update": "2022-01-05T13:30:31+00:00", "cache-validity": 48, "is-supported": true, "systeminfo": "retrieving vuln and SBOM info via a cloud service", "mfg-name": "Example, Inc.", "documentation": "https://iot.example.com/doc/modelX", "model-name": "modelX", "from-device-policy": { "access-lists": { "access-list": [ { "name": "mud-65443-v4fr" } ] } }, "to-device-policy": { "access-lists": { "access-list": [ { "name": "mud-65443-v4to" } ] } } }, "ietf-access-control-list:acls": { "acl": [ { "name": "mud-65443-v4to", "type": "ipv4-acl-type", "aces": { "ace": [ { "name": "cl0-todev", "matches": { "ipv4": { "ietf-acldns:src-dnsname": "iotserver.example.com" } }, "actions": { "forwarding": "accept" } } ] } }, { "name": "mud-65443-v4fr", "type": "ipv4-acl-type", "aces": { "ace": [ { "name": "cl0-frdev", "matches": { "ipv4": { "ietf-acldns:dst-dnsname": "iotserver.example.com" } }, "actions": { "forwarding": "accept" } } ] } } ] } } At this point, the management system can attempt to retrieve the SBOM, determine which format is in use through the Content-Type header on the response to a GET request, independently repeat the process for vulnerability information, and apply ACLs as appropriate.

Security Considerations This document describes a schema for discovering the location of information relating to software transparency and does not specify the access model for the information itself. In particular, the YANG module specified in this document is not necessarily intended to be accessed via regular network management protocols, such as NETCONF or RESTCONF , and hence the regular security considerations for such usage are not considered here. Below, we describe protections relating to both discovery and some advice on protecting the underlying SBOM and vulnerability information. The model specifies both encrypted and unencrypted means to retrieve information. This is a matter of pragmatism. Unencrypted communications allow for manipulation of information being retrieved. Therefore, it is RECOMMENDED that implementations offer a means to configure endpoints so that they may make use of TLS or DTLS. The ietf-mud-transparency module has no operational impact on the element itself and is used to discover state information that may be available on or off the element. In as much as the module itself is made writeable, this only indicates a change in how to retrieve read-only elements. There are no means, for instance, to upload an SBOM. Additional risks are discussed below and are applicable to all nodes within the transparency container. If an attacker modifies the elements, they may misdirect automation to retrieve a different set of URLs than was intended by the designer. This in turn leads to two specific sets of risks:

• the information retrieved would be false
• the URLs themselves point to malware

To address either of these risks or any tampering of a URL:

• test any cloud-based URL against a reputation service
• provide the administrator an opportunity to approve further processing when the authority changes to one not known to be reputable

SBOMs provide an inventory of software. Knowledge of which specific software is loaded on a system can aid an attacker in identifying an appropriate exploit for a known vulnerability or guide the development of novel exploit against this system. However, if software is available to an attacker, the attacker may already be able to derive this very same software inventory. When this information resides on the endpoint itself, the endpoint SHOULD NOT provide unrestricted access to the well-known URL by default. Other servers that offer the data MAY restrict access to SBOM information using appropriate authorization semantics within HTTP. One way to do this would be to issue a certificate to the client for this purpose after a registration process has taken place. Another approach would involve the use of OAuth in combination. In particular, if a system attempts to retrieve an SBOM via HTTP or CoAP and the client is not authorized, the server MUST produce an appropriate error with instructions on how to register a particular client. Another risk is a skew in the SBOM listing and the actual software inventory of a device/container. For example, a manufacturer may update the SBOM on its server, but an individual device has not been upgraded yet. This may result in an incorrect policy being applied to a device. A unique mapping of a device's software version and its SBOM can minimize this risk. To further mitigate attacks against a device, manufacturers SHOULD recommend network access controls. Vulnerability information is generally made available to such databases as NIST's National Vulnerability Database . It is possible that vendors may wish to release information early to some customers. We do not discuss here whether that is a good idea, but if it is employed, then appropriate access controls and authorization SHOULD be applied to that information.

IANA Considerations

MUD Extension IANA has added "transparency" to the "MUD Extensions" registry as follows:

Value:

transparency

Reference:

RFC 9472

YANG Registration IANA has registered the following YANG module in the "YANG Module Names" registry :

Name:

ietf-mud-transparency

Namespace:

urn:ietf:params:xml:ns:yang:ietf-mud-transparency

Maintained by IANA:

N

Prefix:

mudtx

Reference:

RFC 9472

The following URI has been registered in the "IETF XML Registry" :

URI:

urn:ietf:params:xml:ns:yang:ietf-mud-transparency

Registrant Contact:

IESG

XML:

None. Namespace URIs do not represent an XML specification.

Well-Known Prefix IANA has added the following URI suffix to the "Well-Known URIs" registry in accordance with :

URI Suffix:

sbom

Change Controller:

IETF

Reference:

RFC 9472

Status:

permanent

Related Information:

See ISO/IEC 5962:2021 and SPDX.org

References Normative References In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. The Hypertext Transfer Protocol (HTTP) is a stateless \%application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation. The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation. CoAP provides a request/response interaction model between application endpoints, supports built-in discovery of services and resources, and includes key concepts of the Web such as URIs and Internet media types. CoAP is designed to easily interface with HTTP for integration with the Web while meeting specialized requirements such as multicast support, very low overhead, and simplicity for constrained environments. This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This memo specifies a component-based architecture for Manufacturer Usage Descriptions (MUDs). The goal of MUD is to provide a means for end devices to signal to the network what sort of access and network functionality they require to properly function. The initial focus is on access control. Later work can delve into other aspects. This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, a Link Layer Discovery Protocol (LLDP) TLV, a URL, an X.509 certificate extension, and a means to sign and verify the descriptions. This memo defines a path prefix for "well-known locations", "/.well-known/", in selected Uniform Resource Identifier (URI) schemes. In doing so, it obsoletes RFC 5785 and updates the URI schemes defined in RFC 7230 to reserve that space. It also updates RFC 7595 to track URI schemes that support well-known URIs in their registry. The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230. Informative References OASIS OASIS OASIS OASIS Standard OASIS CycloneDX Version 1.5.0 The White House EO 14028 NIST This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. The Linux Foundation Version 2.3

Acknowledgments Thanks to , , , and , who provided review comments.

Authors' Addresses Cisco Systems

Richtistrasse 7 Wallisellen 8304 Switzerland +41 44 878 9200 lear@cisco.com

NIST

100 Bureau Dr. Gaithersburg MD 20899 United States of America +1 301-975-8439 scott.rose@nist.gov