statement_id stringlengths 26 83 | source stringclasses 6
values | subject_id stringlengths 3 70 | subject_label stringlengths 0 250 | subject_description stringlengths 0 250 | subject_instance_of_ids stringlengths 0 139 | subject_instance_of_labels stringlengths 0 310 | property_id stringlengths 2 6 | property_label stringlengths 0 80 | value_id stringlengths 1 1.9k | value_label stringlengths 0 1.9k | value_type stringclasses 8
values | qualifier_property_id stringclasses 948
values | qualifier_property_label stringclasses 947
values | qualifier_value_id stringlengths 0 686 | qualifier_value_label stringlengths 0 205 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
STD:IETF:RFC9698$78c8e6f79d30 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines an IMAP extension to let clients know that the messages in this IMAP server are also available via the JSON Meta Application Protocol (JMAP), and how. It is intended for clients that want to migrate gradually to JMAP or use JMAP extensions within an IMAP client. | This document defines an IMAP extension to let clients know that the messages in this IMAP server are also available via the JSON Meta Application Protocol (JMAP), and how. It is intended for clients that want to migrate gradually to JMAP or use JMAP extensions within an IMAP client. | monolingualtext | ||||
STD:IETF:RFC9698$7a623f7e283e | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Gulbrandsen | A. Gulbrandsen | string | ||||
STD:IETF:RFC9698$ebb74d547cc0 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Gondwana | B. Gondwana | string | ||||
STD:IETF:RFC9698$f6c4102b4413 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9698$f6c4102b4413 | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9698$ff52ec783f9c | IETF | STD:IETF:RFC9698 | The JMAPACCESS Extension for IMAP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9699$024b9d4b90b7 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9699 | https://www.rfc-editor.org/rfc/rfc9699 | url | ||||
STD:IETF:RFC9699$47388d04f7a9 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9699$48befd2f6ed1 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Rahman | A. Rahman | string | ||||
STD:IETF:RFC9699$58814cf80c15 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document explores the issues involved in the use of edge computing resources to operationalize a media use case that involves an Extended Reality (XR) application. In particular, this document discusses an XR application that can run on devices having different form factors (such as different physical sizes and s... | This document explores the issues involved in the use of edge computing resources to operationalize a media use case that involves an Extended Reality (XR) application. In particular, this document discusses an XR application that can run on devices having different form factors (such as different physical sizes and s... | monolingualtext | ||||
STD:IETF:RFC9699$789a534b3612 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Krishna | R. Krishna | string | ||||
STD:IETF:RFC9699$7f814d91eec9 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9699$af380523645c | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9699$af380523645c | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9699$d0c79ba81875 | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9699$ed6851ef80af | IETF | STD:IETF:RFC9699 | Use Case for an Extended Reality Application on Edge Computing Infrastructure | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Use Case for an Extended Reality Application on Edge Computing Infrastructure | Use Case for an Extended Reality Application on Edge Computing Infrastructure | monolingualtext | ||||
STD:IETF:RFC9700$52cf70f14585 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9700$5e438fe7286d | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9700 | https://www.rfc-editor.org/rfc/rfc9700 | url | ||||
STD:IETF:RFC9700$9012cc95c43c | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | J. Bradley | J. Bradley | string | ||||
STD:IETF:RFC9700$a0513110e4d7 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Best Current Practice for OAuth 2.0 Security | Best Current Practice for OAuth 2.0 Security | monolingualtext | ||||
STD:IETF:RFC9700$aa4f0880052e | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes best current security practice for OAuth 2.0. It updates and extends the threat model and security advice given in RFCs 6749, 6750, and 6819 to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0. ... | This document describes best current security practice for OAuth 2.0. It updates and extends the threat model and security advice given in RFCs 6749, 6750, and 6819 to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0. ... | monolingualtext | ||||
STD:IETF:RFC9700$ae960afc17a7 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | D. Fett | D. Fett | string | ||||
STD:IETF:RFC9700$bd761108c4b5 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9700$bd761108c4b5 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9700$c39a87498a43 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | A. Labunets | A. Labunets | string | ||||
STD:IETF:RFC9700$cd2c3509849e | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9700$cff7d5aee985 | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | T. Lodderstedt | T. Lodderstedt | string | ||||
STD:IETF:RFC9700$f6e1b5400bbe | IETF | STD:IETF:RFC9700 | Best Current Practice for OAuth 2.0 Security | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9701$099db7aa8452 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Lodderstedt | T. Lodderstedt | string | ||||
STD:IETF:RFC9701$299e73052306 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9701 | https://www.rfc-editor.org/rfc/rfc9701 | url | ||||
STD:IETF:RFC9701$360d18819ad3 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification proposes an additional response secured by JSON Web Token (JWT) for OAuth 2.0 Token Introspection. | This specification proposes an additional response secured by JSON Web Token (JWT) for OAuth 2.0 Token Introspection. | monolingualtext | ||||
STD:IETF:RFC9701$3f2f7cb897b9 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9701$3f2f7cb897b9 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9701$451728954cdb | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | JSON Web Token (JWT) Response for OAuth Token Introspection | JSON Web Token (JWT) Response for OAuth Token Introspection | monolingualtext | ||||
STD:IETF:RFC9701$9da270c01fce | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Dzhuvinov | V. Dzhuvinov | string | ||||
STD:IETF:RFC9701$b22dca307fe7 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9701$bec9910dd384 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9701$db3b85dcfc89 | IETF | STD:IETF:RFC9701 | JSON Web Token (JWT) Response for OAuth Token Introspection | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9702$3be6954542be | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9702$3be6954542be | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9702$3c37f997386e | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines two YANG modules. The first module is the initial version of the IANA-maintained YANG module for Maximum Segment Identifier (SID) Depth (MSD) Types, which includes identities for both the MPLS data plane and Segment Routing over IPv6 (SRv6) data plane. The second module augments the IETF MPLS YA... | This document defines two YANG modules. The first module is the initial version of the IANA-maintained YANG module for Maximum Segment Identifier (SID) Depth (MSD) Types, which includes identities for both the MPLS data plane and Segment Routing over IPv6 (SRv6) data plane. The second module augments the IETF MPLS YA... | monolingualtext | ||||
STD:IETF:RFC9702$45712eee4937 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | monolingualtext | ||||
STD:IETF:RFC9702$48623d2b9750 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9702 | https://www.rfc-editor.org/rfc/rfc9702 | url | ||||
STD:IETF:RFC9702$6da20c41c65a | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9702$89e155a89fc3 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Qu | Y. Qu | string | ||||
STD:IETF:RFC9702$8ceda73936e0 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9702$9bf042905836 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9702$d505c0f2b60a | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9702$f95ac4ee0807 | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Litkowski | S. Litkowski | string | ||||
STD:IETF:RFC9702$fa8671649f0d | IETF | STD:IETF:RFC9702 | YANG Data Model for Maximum Segment Identifier (SID) Depth (MSD) Types and MPLS MSD | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Lindem | A. Lindem | string | ||||
STD:IETF:RFC9703$0704af92c478 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Srivastava | M. Srivastava | string | ||||
STD:IETF:RFC9703$1330235a16f0 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Xu | X. Xu | string | ||||
STD:IETF:RFC9703$26f078f19843 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9703$3391dc53e53f | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9703$53c7c18493c7 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Arora | K. Arora | string | ||||
STD:IETF:RFC9703$5ae48d27d829 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | monolingualtext | ||||
STD:IETF:RFC9703$812e259d2878 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Egress Peer Engineering (EPE) is an application of Segment Routing (SR) that solves the problem of egress peer selection. The SR-based BGP-EPE solution allows a centralized controller, e.g., a Software-Defined Network (SDN) controller, to program any egress peer. The EPE solution requires the node or the SDN controll... | Egress Peer Engineering (EPE) is an application of Segment Routing (SR) that solves the problem of egress peer selection. The SR-based BGP-EPE solution allows a centralized controller, e.g., a Software-Defined Network (SDN) controller, to program any egress peer. The EPE solution requires the node or the SDN controll... | monolingualtext | ||||
STD:IETF:RFC9703$900217f28d74 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9703 | https://www.rfc-editor.org/rfc/rfc9703 | url | ||||
STD:IETF:RFC9703$ba656735fed6 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9703$bb0f68d197d3 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9703$bb0f68d197d3 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9703$bcd75beba4b5 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Ninan | S. Ninan | string | ||||
STD:IETF:RFC9703$f987b3f273f9 | IETF | STD:IETF:RFC9703 | Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hegde | S. Hegde | string | ||||
STD:IETF:RFC9704$0bf5507a5876 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Schwartz | B. Schwartz | string | ||||
STD:IETF:RFC9704$14415311da33 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Establishing Local DNS Authority in Validated Split-Horizon Environments | Establishing Local DNS Authority in Validated Split-Horizon Environments | monolingualtext | ||||
STD:IETF:RFC9704$3c970d4c2733 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9704$3c970d4c2733 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9704$53e47897e422 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Smith | K. Smith | string | ||||
STD:IETF:RFC9704$6f745b7efc93 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9704 | https://www.rfc-editor.org/rfc/rfc9704 | url | ||||
STD:IETF:RFC9704$7dae43b0b0f0 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9704$87cf6cc8bf0c | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9704$bdd7048831e6 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | When split-horizon DNS is deployed by a network, certain domain names can be resolved authoritatively by a network-provided DNS resolver. DNS clients that are not configured to use this resolver by default can use it for these specific domains only. This specification defines a mechanism for domain owners to inform D... | When split-horizon DNS is deployed by a network, certain domain names can be resolved authoritatively by a network-provided DNS resolver. DNS clients that are not configured to use this resolver by default can use it for these specific domains only. This specification defines a mechanism for domain owners to inform D... | monolingualtext | ||||
STD:IETF:RFC9704$dd510288f06b | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9704$e2481cfb7a19 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Wing | D. Wing | string | ||||
STD:IETF:RFC9704$ec49b4572bc7 | IETF | STD:IETF:RFC9704 | Establishing Local DNS Authority in Validated Split-Horizon Environments | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Reddy.K | T. Reddy.K | string | ||||
STD:IETF:RFC9705$0a2ce710ee47 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9705$0a2ce710ee47 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9705$0c40e08094c3 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9705$0e5ebd6319cb | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Saad | T. Saad | string | ||||
STD:IETF:RFC9705$2a11709349a0 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Pacella | D. Pacella | string | ||||
STD:IETF:RFC9705$343f745f94cc | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9705$3f82f1d783e0 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The RSVP-TE Fast Reroute (FRR) extensions specified in RFC 4090 define two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnels. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one... | The RSVP-TE Fast Reroute (FRR) extensions specified in RFC 4090 define two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnels. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one... | monolingualtext | ||||
STD:IETF:RFC9705$74eee235bd8e | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Ramachandran | C. Ramachandran | string | ||||
STD:IETF:RFC9705$7707cd38ed25 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9705 | https://www.rfc-editor.org/rfc/rfc9705 | url | ||||
STD:IETF:RFC9705$8a4910f17637 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | monolingualtext | ||||
STD:IETF:RFC9705$b09416e7b039 | IETF | STD:IETF:RFC9705 | Refresh-Interval Independent RSVP Fast Reroute Facility Protection | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9706$0a39004ac647 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | As Internet audience sizes for high-interest live events reach unprecedented levels and bitrates climb to support formats and applications such as 4K, 8K, and Augmented Reality (AR), live streaming can place a unique type of stress upon network resources. TreeDN is a tree-based Content Delivery Network (CDN) architect... | As Internet audience sizes for high-interest live events reach unprecedented levels and bitrates climb to support formats and applications such as 4K, 8K, and Augmented Reality (AR), live streaming can place a unique type of stress upon network resources. TreeDN is a tree-based Content Delivery Network (CDN) architect... | monolingualtext | ||||
STD:IETF:RFC9706$541205da75c1 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Adam | R. Adam | string | ||||
STD:IETF:RFC9706$66b21fc13d89 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Lenart | C. Lenart | string | ||||
STD:IETF:RFC9706$74da0d10de51 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9706$7bb5e53ce6c9 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Giuliano | L. Giuliano | string | ||||
STD:IETF:RFC9706$7d375a0925c2 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9706$811db2428c1e | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | monolingualtext | ||||
STD:IETF:RFC9706$a3751738273b | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9706$c6c48073bfde | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9706 | https://www.rfc-editor.org/rfc/rfc9706 | url | ||||
STD:IETF:RFC9706$ca93c6308e06 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9706$ca93c6308e06 | IETF | STD:IETF:RFC9706 | TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass Audiences | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9707$1da429cc408f | IETF | STD:IETF:RFC9707 | Report from the IAB Workshop on Barriers to Internet Access of Services (BIAS) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Knodel | M. Knodel | string | ||||
STD:IETF:RFC9707$2b931419858f | IETF | STD:IETF:RFC9707 | Report from the IAB Workshop on Barriers to Internet Access of Services (BIAS) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9707 | https://www.rfc-editor.org/rfc/rfc9707 | url | ||||
STD:IETF:RFC9707$370cc8c0135c | IETF | STD:IETF:RFC9707 | Report from the IAB Workshop on Barriers to Internet Access of Services (BIAS) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.