-
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
Nov 21, 2023
1 parent
b1e7d56
commit b8c00a0
Showing
5 changed files
with
117 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,23 @@ | ||
| <reference anchor="RFC.9403" target="https://www.rfc-editor.org/info/rfc9403"> | ||
| <front> | ||
| <title>A YANG Data Model for RIB Extensions</title> | ||
| <author fullname="A. Lindem" initials="A." surname="Lindem"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="Y. Qu" initials="Y." surname="Qu"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="November"/> | ||
| <workgroup>rtgwg</workgroup> | ||
| <abstract> | ||
| <t>A Routing Information Base (RIB) is a list of routes and their corresponding administrative data and operational state.</t> | ||
| <t>RFC 8349 defines the basic building blocks for the RIB data model, and this model augments it to support multiple next hops (aka paths) for each route as well as additional attributes.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9403"/> | ||
| <seriesInfo name="RFC" value="9403"/> | ||
| <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,26 @@ | ||
| <reference anchor="RFC.9498" target="https://www.rfc-editor.org/info/rfc9498"> | ||
| <front> | ||
| <title>The GNU Name System</title> | ||
| <author fullname="M. Schanzenbach" initials="M." surname="Schanzenbach"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="C. Grothoff" initials="C." surname="Grothoff"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="B. Fix" initials="B." surname="Fix"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="November"/> | ||
| <abstract> | ||
| <t>This document provides the GNU Name System (GNS) technical specification. GNS is a decentralized and censorship-resistant domain name resolution protocol that provides a privacy-enhancing alternative to the Domain Name System (DNS) protocols.</t> | ||
| <t>This document defines the normative wire format of resource records, resolution processes, cryptographic routines, and security and privacy considerations for use by implementers.</t> | ||
| <t>This specification was developed outside the IETF and does not have IETF consensus. It is published here to inform readers about the function of GNS, guide future GNS implementations, and ensure interoperability among implementations (for example, pre-existing GNUnet implementations).</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9498"/> | ||
| <seriesInfo name="RFC" value="9498"/> | ||
| <seriesInfo name="INDEPENDENT"/> | ||
| </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,33 @@ | ||
| <reference anchor="RFC.9505" target="https://www.rfc-editor.org/info/rfc9505"> | ||
| <front> | ||
| <title>A Survey of Worldwide Censorship Techniques</title> | ||
| <author fullname="J. L. Hall" initials="J. L." surname="Hall"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="M. D. Aaron" initials="M. D." surname="Aaron"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="A. Andersdotter" initials="A." surname="Andersdotter"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="B. Jones" initials="B." surname="Jones"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="N. Feamster" initials="N." surname="Feamster"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="M. Knodel" initials="M." surname="Knodel"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="November"/> | ||
| <abstract> | ||
| <t>This document describes technical mechanisms employed in network censorship that regimes around the world use for blocking or impairing Internet traffic. It aims to make designers, implementers, and users of Internet protocols aware of the properties exploited and mechanisms used for censoring end-user access to information. This document makes no suggestions on individual protocol considerations, and is purely informational, intended as a reference. This document is a product of the Privacy Enhancement and Assessment Research Group (PEARG) in the IRTF.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9505"/> | ||
| <seriesInfo name="RFC" value="9505"/> | ||
| <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,34 @@ | ||
| <reference anchor="RFC.9516" target="https://www.rfc-editor.org/info/rfc9516"> | ||
| <front> | ||
| <title>Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC)</title> | ||
| <author fullname="G. Mirsky" initials="G." surname="Mirsky"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="W. Meng" initials="W." surname="Meng"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="T. Ao" initials="T." surname="Ao"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="B. Khasnabish" initials="B." surname="Khasnabish"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="K. Leung" initials="K." surname="Leung"> | ||
| <organization/> | ||
| </author> | ||
| <author fullname="G. Mishra" initials="G." surname="Mishra"> | ||
| <organization/> | ||
| </author> | ||
| <author> | ||
| <organization>RFC Series</organization> | ||
| </author> | ||
| <date year="2023" month="November"/> | ||
| <workgroup>sfc</workgroup> | ||
| <abstract> | ||
| <t>A set of requirements for active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) in a network is presented in this document. Based on these requirements, an encapsulation of active OAM messages in SFC and a mechanism to detect and localize defects are described.</t> | ||
| </abstract> | ||
| </front> | ||
| <seriesInfo name="DOI" value="10.17487/RFC9516"/> | ||
| <seriesInfo name="RFC" value="9516"/> | ||
| <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 @@ | ||
| Mon Nov 20 15:14:31 UTC 2023 | ||
| Tue Nov 21 15:13:36 UTC 2023 |