-
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
Aug 28, 2024
1 parent
0da177e
commit d46c49c
Showing
6 changed files
with
145 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,28 @@ | ||
| <reference anchor="RFC.9588" target="https://www.rfc-editor.org/info/rfc9588"> | ||
| <front> | ||
| <title>Kerberos Simple Password-Authenticated Key Exchange (SPAKE) Pre-authentication</title> | ||
| <author fullname="N. McCallum" initials="N." surname="McCallum"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. Sorce" initials="S." surname="Sorce"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="R. Harwood" initials="R." surname="Harwood"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="G. Hudson" initials="G." surname="Hudson"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2024" month="August"/> | ||
| <workgroup>kitten</workgroup> | ||
| <abstract> | ||
| <t>This document defines a new pre-authentication mechanism for the Kerberos protocol. The mechanism uses a password-authenticated key exchange (PAKE) to prevent brute-force password attacks, and it may incorporate a second factor.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9588"/> | ||
| <seriesInfo name="RFC" value="9588"/> | ||
| <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.9605" target="https://www.rfc-editor.org/info/rfc9605"> | ||
| <front> | ||
| <title>Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media</title> | ||
| <author fullname="E. Omara" initials="E." surname="Omara"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="J. Uberti" initials="J." surname="Uberti"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. G. Murillo" initials="S. G." surname="Murillo"> | ||
| <organization/> | ||
| </author> | ||
| <author role="editor" fullname="R. Barnes" initials="R." surname="Barnes"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="Y. Fablet" initials="Y." surname="Fablet"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2024" month="August"/> | ||
| <workgroup>sframe</workgroup> | ||
| <abstract> | ||
| <t>This document describes the Secure Frame (SFrame) end-to-end encryption and authentication mechanism for media frames in a multiparty conference call, in which central media servers (Selective Forwarding Units or SFUs) can access the media metadata needed to make forwarding decisions without having access to the actual media.</t> | ||
| <t>This mechanism differs from the Secure Real-Time Protocol (SRTP) in that it is independent of RTP (thus compatible with non-RTP media transport) and can be applied to whole media frames in order to be more bandwidth efficient.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9605"/> | ||
| <seriesInfo name="RFC" value="9605"/> | ||
| <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,28 @@ | ||
| <reference anchor="RFC.9617" target="https://www.rfc-editor.org/info/rfc9617"> | ||
| <front> | ||
| <title>A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)</title> | ||
| <author role="editor" fullname="T. Zhou" initials="T." surname="Zhou"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="J. Guichard" initials="J." surname="Guichard"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="F. Brockners" initials="F." surname="Brockners"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="S. Raghavan" initials="S." surname="Raghavan"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2024" month="August"/> | ||
| <workgroup>ippm</workgroup> | ||
| <abstract> | ||
| <t>In situ Operations, Administration, and Maintenance (IOAM) is an example of an on-path hybrid measurement method. IOAM defines a method for producing operational and telemetry information that may be exported using the in-band or out-of-band method. RFCs 9197 and 9326 discuss the data fields and associated data types for IOAM. This document defines a YANG module for the configuration of IOAM functions.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9617"/> | ||
| <seriesInfo name="RFC" value="9617"/> | ||
| <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,34 @@ | ||
| <reference anchor="RFC.9630" target="https://www.rfc-editor.org/info/rfc9630"> | ||
| <front> | ||
| <title>Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM)</title> | ||
| <author fullname="H. Song" initials="H." surname="Song"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="M. McBride" initials="M." surname="McBride"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="G. Mirsky" initials="G." surname="Mirsky"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="G. Mishra" initials="G." surname="Mishra"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="H. Asaeda" initials="H." surname="Asaeda"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="T. Zhou" initials="T." surname="Zhou"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2024" month="August"/> | ||
| <workgroup>mboned</workgroup> | ||
| <abstract> | ||
| <t>This document specifies two solutions to meet the requirements of on-path telemetry for multicast traffic using IOAM. While IOAM is advantageous for multicast traffic telemetry, some unique challenges are present. This document provides the solutions based on the IOAM trace option and direct export option to support the telemetry data correlation and the multicast tree reconstruction without incurring data redundancy.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9630"/> | ||
| <seriesInfo name="RFC" value="9630"/> | ||
| <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,22 @@ | ||
| <reference anchor="RFC.9637" target="https://www.rfc-editor.org/info/rfc9637"> | ||
| <front> | ||
| <title>Expanding the IPv6 Documentation Space</title> | ||
| <author fullname="G. Huston" initials="G." surname="Huston"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="N. Buraglio" initials="N." surname="Buraglio"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2024" month="August"/> | ||
| <workgroup>v6ops</workgroup> | ||
| <abstract> | ||
| <t>The document describes the reservation of an additional IPv6 address prefix for use in documentation. This update to RFC 3849 expands on the existing 2001:db8::/32 address block with the reservation of an additional, larger prefix. The addition of a /20 prefix allows documented examples to more closely reflect a broader range of realistic, current deployment scenarios and more closely aligns with contemporary allocation models for large networks.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9637"/> | ||
| <seriesInfo name="RFC" value="9637"/> | ||
| <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 Aug 27 15:16:35 UTC 2024 | ||
| Wed Aug 28 15:16:20 UTC 2024 |