-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
github-actions
committed
Oct 11, 2023
1 parent
4789e23
commit 8142177
Showing
6 changed files
with
134 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| <reference anchor="RFC.9472" target="https://www.rfc-editor.org/info/rfc9472"> | ||
| <front> | ||
| <title>A YANG Data Model for Reporting Software Bills of Materials (SBOMs) and Vulnerability Information</title> | ||
| <author fullname="E. Lear" initials="E." surname="Lear"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. Rose" initials="S." surname="Rose"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="October"/> | ||
| <workgroup>opsawg</workgroup> | ||
| <abstract> | ||
| <t>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.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9472"/> | ||
| <seriesInfo name="RFC" value="9472"/> | ||
| <seriesInfo name="IETF"/> | ||
| </reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| <reference anchor="RFC.9474" target="https://www.rfc-editor.org/info/rfc9474"> | ||
| <front> | ||
| <title>RSA Blind Signatures</title> | ||
| <author fullname="F. Denis" initials="F." surname="Denis"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="F. Jacobs" initials="F." surname="Jacobs"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="C. A. Wood" initials="C. A." surname="Wood"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="October"/> | ||
| <abstract> | ||
| <t>This document specifies an RSA-based blind signature protocol. RSA blind signatures were first introduced by Chaum for untraceable payments. A signature that is output from this protocol can be verified as an RSA-PSS signature.</t> | ||
| <t>This document is a product of the Crypto Forum Research Group (CFRG) in the IRTF.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9474"/> | ||
| <seriesInfo name="RFC" value="9474"/> | ||
| <seriesInfo name="IRTF"/> | ||
| </reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| <reference anchor="RFC.9478" target="https://www.rfc-editor.org/info/rfc9478"> | ||
| <front> | ||
| <title>Labeled IPsec Traffic Selector Support for the Internet Key Exchange Protocol Version 2 (IKEv2)</title> | ||
| <author fullname="P. Wouters" initials="P." surname="Wouters"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. Prasad" initials="S." surname="Prasad"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="October"/> | ||
| <workgroup>ipsecme</workgroup> | ||
| <abstract> | ||
| <t>This document defines a new Traffic Selector Type (TS Type) for the Internet Key Exchange Protocol version 2 (IKEv2) to add support for negotiating Mandatory Access Control (MAC) security labels as a Traffic Selector of the Security Policy Database (SPD). Security Labels for IPsec are also known as "Labeled IPsec". The new TS Type, TS_SECLABEL, consists of a variable length opaque field that specifies the security label.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9478"/> | ||
| <seriesInfo name="RFC" value="9478"/> | ||
| <seriesInfo name="IETF"/> | ||
| </reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| <reference anchor="RFC.9479" target="https://www.rfc-editor.org/info/rfc9479"> | ||
| <front> | ||
| <title>IS-IS Application-Specific Link Attributes</title> | ||
| <author fullname="L. Ginsberg" initials="L." surname="Ginsberg"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="P. Psenak" initials="P." surname="Psenak"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. Previdi" initials="S." surname="Previdi"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="W. Henderickx" initials="W." surname="Henderickx"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="J. Drake" initials="J." surname="Drake"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="October"/> | ||
| <workgroup>lsr</workgroup> | ||
| <abstract> | ||
| <t>Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Policy and Loop-Free Alternates) that also make use of the link attribute advertisements have been defined. In cases where multiple applications wish to make use of these link attributes, the current advertisements do not support application-specific values for a given attribute, nor do they support an indication of which applications are using the advertised value for a given link. This document introduces link attribute advertisements that address both of these shortcomings.</t> | ||
| <t>This document obsoletes RFC 8919.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9479"/> | ||
| <seriesInfo name="RFC" value="9479"/> | ||
| <seriesInfo name="IETF"/> | ||
| </reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| <reference anchor="RFC.9492" target="https://www.rfc-editor.org/info/rfc9492"> | ||
| <front> | ||
| <title>OSPF Application-Specific Link Attributes</title> | ||
| <author role="editor" fullname="P. Psenak" initials="P." surname="Psenak"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="L. Ginsberg" initials="L." surname="Ginsberg"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="W. Henderickx" initials="W." surname="Henderickx"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="J. Tantsura" initials="J." surname="Tantsura"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="J. Drake" initials="J." surname="Drake"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="October"/> | ||
| <workgroup>lsr</workgroup> | ||
| <abstract> | ||
| <t>Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications such as Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) that also make use of the link attribute advertisements have been defined. In cases where multiple applications wish to make use of these link attributes, the current advertisements do not support application-specific values for a given attribute, nor do they support indication of which applications are using the advertised value for a given link. This document introduces link attribute advertisements in OSPFv2 and OSPFv3 that address both of these shortcomings.</t> | ||
| <t>This document obsoletes RFC 8920.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9492"/> | ||
| <seriesInfo name="RFC" value="9492"/> | ||
| <seriesInfo name="IETF"/> | ||
| </reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| Tue Oct 10 15:13:36 UTC 2023 | ||
| Wed Oct 11 15:12:55 UTC 2023 |