RFC 9472 on A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information

rfc-editor@rfc-editor.org Tue, 10 October 2023 18:15 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79A0C14CE25; Tue, 10 Oct 2023 11:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fy0PcztL2k_U; Tue, 10 Oct 2023 11:15:10 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C47EC14CEFD; Tue, 10 Oct 2023 11:15:10 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id EC8EBE629D; Tue, 10 Oct 2023 11:15:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9472 on A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231010181509.EC8EBE629D@rfcpa.amsl.com>
Date: Tue, 10 Oct 2023 11:15:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8x0Vu2f7YywbfFQzd6ZdBTXxpEM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2023 18:15:14 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9472

        Title:      A YANG Data Model for Reporting
                    Software Bills of Materials (SBOMs) 
                    and Vulnerability Information 
        Author:     E. Lear,
                    S. Rose
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2023
        Mailbox:    lear@cisco.com,
                    scott.rose@nist.gov
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-sbom-access-18.txt

        URL:        https://www.rfc-editor.org/info/rfc9472

        DOI:        10.17487/RFC9472

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.

This document is a product of the Operations and Management Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC