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:RFC9538$10efc3a09e71 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9538$25afd1f75555 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Stephan | E. Stephan | string | ||||
STD:IETF:RFC9538$47d2f3c1c547 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9538 | https://www.rfc-editor.org/rfc/rfc9538 | url | ||||
STD:IETF:RFC9538$4891f3074991 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines metadata to support delegating the delivery of HTTPS content between two or more interconnected Content Delivery Networks (CDNs). Specifically, this document defines a Content Delivery Network Interconnection (CDNI) Metadata interface object to enable delegation of X.509 certificates leveraging d... | This document defines metadata to support delegating the delivery of HTTPS content between two or more interconnected Content Delivery Networks (CDNs). Specifically, this document defines a Content Delivery Network Interconnection (CDNI) Metadata interface object to enable delegation of X.509 certificates leveraging d... | monolingualtext | ||||
STD:IETF:RFC9538$55df54232c3d | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Fieau | F. Fieau | string | ||||
STD:IETF:RFC9538$76e7ce9f2fee | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | monolingualtext | ||||
STD:IETF:RFC9538$82c6a8a58073 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9538$bcc0d845b4d2 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Mishra | S. Mishra | string | ||||
STD:IETF:RFC9538$cb66dd2f29a1 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9538$cb66dd2f29a1 | IETF | STD:IETF:RFC9538 | Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9539$101a1e6033a3 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | monolingualtext | ||||
STD:IETF:RFC9539$19d0b2ab4c28 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9539$798f1d127d5f | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9539$889d0810aa99 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | J. Salazar | J. Salazar | string | ||||
STD:IETF:RFC9539$b48ee092928a | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9539 | https://www.rfc-editor.org/rfc/rfc9539 | url | ||||
STD:IETF:RFC9539$c0dc4ec015bc | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | P. Hoffman | P. Hoffman | string | ||||
STD:IETF:RFC9539$c60c1fec3dab | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9539$dffec67d34da | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | D. K. Gillmor | D. K. Gillmor | string | ||||
STD:IETF:RFC9539$e56234616933 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document sets out steps that DNS servers (recursive resolvers and authoritative servers) can take unilaterally (without any coordination with other peers) to defend DNS query privacy against a passive network monitor. The protections provided by the guidance in this document can be defeated by an active attacker, ... | This document sets out steps that DNS servers (recursive resolvers and authoritative servers) can take unilaterally (without any coordination with other peers) to defend DNS query privacy against a passive network monitor. The protections provided by the guidance in this document can be defeated by an active attacker, ... | monolingualtext | ||||
STD:IETF:RFC9539$e82d6b76d2a1 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9539$e82d6b76d2a1 | IETF | STD:IETF:RFC9539 | Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9540$095f1ceb596e | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9540$4595f42c0544 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9540$4595f42c0544 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9540$466220c58464 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Discovery of Oblivious Services via Service Binding Records | Discovery of Oblivious Services via Service Binding Records | monolingualtext | ||||
STD:IETF:RFC9540$52f58df20e34 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a parameter that can be included in Service Binding (SVCB) and HTTPS DNS resource records to denote that a service is accessible using Oblivious HTTP, by offering an Oblivious Gateway Resource through which to access the target. This document also defines a mechanism for learning the key configur... | This document defines a parameter that can be included in Service Binding (SVCB) and HTTPS DNS resource records to denote that a service is accessible using Oblivious HTTP, by offering an Oblivious Gateway Resource through which to access the target. This document also defines a mechanism for learning the key configur... | monolingualtext | ||||
STD:IETF:RFC9540$8ebe90776d30 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9540$9050167e2f15 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9540$bf0503ef656a | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9540 | https://www.rfc-editor.org/rfc/rfc9540 | url | ||||
STD:IETF:RFC9540$c6a663239f6e | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9540$e4c9a0941f20 | IETF | STD:IETF:RFC9540 | Discovery of Oblivious Services via Service Binding Records | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Reddy.K | T. Reddy.K | string | ||||
STD:IETF:RFC9541$065499e3a678 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | monolingualtext | ||||
STD:IETF:RFC9541$22282963939a | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Nagaraj | K. Nagaraj | string | ||||
STD:IETF:RFC9541$3d61c80ed459 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Provider Backbone Bridging (PBB) can be combined with Ethernet Virtual Private Networks (EVPNs) to deploy Ethernet Local Area Network (E-LAN) services in large Multiprotocol Label Switching (MPLS) networks. That combination is what we refer to as "PBB-EVPN." Single-Active multihoming and per Service Instance Identifie... | Provider Backbone Bridging (PBB) can be combined with Ethernet Virtual Private Networks (EVPNs) to deploy Ethernet Local Area Network (E-LAN) services in large Multiprotocol Label Switching (MPLS) networks. That combination is what we refer to as "PBB-EVPN." Single-Active multihoming and per Service Instance Identifie... | monolingualtext | ||||
STD:IETF:RFC9541$4a7db4f1117d | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Miyake | M. Miyake | string | ||||
STD:IETF:RFC9541$52a2b70943ef | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sathappan | S. Sathappan | string | ||||
STD:IETF:RFC9541$58725c8b8b12 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9541$67436a6b2152 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9541$67436a6b2152 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9541$8769ce514fbd | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9541$8c7660d36db6 | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9541$adb4ef6bb42c | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9541$b9a10775e43c | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Matsuda | T. Matsuda | string | ||||
STD:IETF:RFC9541$f84ab4466b4a | IETF | STD:IETF:RFC9541 | Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9541 | https://www.rfc-editor.org/rfc/rfc9541 | url | ||||
STD:IETF:RFC9542$1d36b59ce8e8 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9542$25a3e23ce8ae | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9542$3e18fde2746c | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC7042 | RFC7042 | wikibase-item | ||||
STD:IETF:RFC9542$4cddd88b786f | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9542 | https://www.rfc-editor.org/rfc/rfc9542 | url | ||||
STD:IETF:RFC9542$9162374d5d60 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9542$b2c34be7a560 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | D. Eastlake 3rd | D. Eastlake 3rd | string | ||||
STD:IETF:RFC9542$dbacb0fbee6d | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | Y. Li | Y. Li | string | ||||
STD:IETF:RFC9542$e82d1d236311 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses several aspects of such parameters and their use in IETF protocols, specifies IANA considerations for assignment of points under the IANA Organizationally Unique Identifier (OUI), and provides some values for use in... | Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses several aspects of such parameters and their use in IETF protocols, specifies IANA considerations for assignment of points under the IANA Organizationally Unique Identifier (OUI), and provides some values for use in... | monolingualtext | ||||
STD:IETF:RFC9542$f9899d96155c | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | monolingualtext | ||||
STD:IETF:RFC9542$fad83d5f915f | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | J. Abley | J. Abley | string | ||||
STD:IETF:RFC9542$fd76d86842c9 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9542$fd76d86842c9 | IETF | STD:IETF:RFC9542 | IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9543$5a28082a9361 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9543$5a28082a9361 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9543$6dfac349ff07 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9543$7de6204fe9a0 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9543$857755836da1 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | L. Contreras | L. Contreras | string | ||||
STD:IETF:RFC9543$a0b2a668131c | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes network slicing in the context of networks built from IETF technologies. It defines the term "IETF Network Slice" to describe this type of network slice and establishes the general principles of network slicing in the IETF context. The document discusses the general framework for requesting and... | This document describes network slicing in the context of networks built from IETF technologies. It defines the term "IETF Network Slice" to describe this type of network slice and establishes the general principles of network slicing in the IETF context. The document discusses the general framework for requesting and... | monolingualtext | ||||
STD:IETF:RFC9543$a14df489190b | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Farrel | A. Farrel | string | ||||
STD:IETF:RFC9543$a2325f3d95a1 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Makhijani | K. Makhijani | string | ||||
STD:IETF:RFC9543$a57ca769fd85 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9543 | https://www.rfc-editor.org/rfc/rfc9543 | url | ||||
STD:IETF:RFC9543$b4d58c72079d | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Rokui | R. Rokui | string | ||||
STD:IETF:RFC9543$b720f99c53bc | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9543$bb4e85808ae9 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9543$d87a49fd921a | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | A Framework for Network Slices in Networks Built from IETF Technologies | A Framework for Network Slices in Networks Built from IETF Technologies | monolingualtext | ||||
STD:IETF:RFC9543$e1df172c4efe | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Homma | S. Homma | string | ||||
STD:IETF:RFC9543$f4e954914128 | IETF | STD:IETF:RFC9543 | A Framework for Network Slices in Networks Built from IETF Technologies | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Drake | J. Drake | string | ||||
STD:IETF:RFC9544$048790c07df1 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9544$08a72136ae8d | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9544$12afd9519e19 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. François | J. François | string | ||||
STD:IETF:RFC9544$142a884f0a97 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Clemm | A. Clemm | string | ||||
STD:IETF:RFC9544$2d51d8de5a00 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9544 | https://www.rfc-editor.org/rfc/rfc9544 | url | ||||
STD:IETF:RFC9544$4abced002276 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Halpern | J. Halpern | string | ||||
STD:IETF:RFC9544$6af52bad86a8 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a set of metrics for networking services with
performance requirements expressed as Service Level Objectives
(SLOs). These metrics, referred to as "Precision Availability Metrics
(PAMs)", are useful for defining and monitoring SLOs. For example,
PAMs can be used by providers and/or customers of ... | This document defines a set of metrics for networking services with
performance requirements expressed as Service Level Objectives
(SLOs). These metrics, referred to as "Precision Availability Metrics
(PAMs)", are useful for defining and monitoring SLOs. For example,
PAMs can be used by providers and/or customers of ... | monolingualtext | ||||
STD:IETF:RFC9544$74cf555e475e | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9544$783194b0403e | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Strassner | J. Strassner | string | ||||
STD:IETF:RFC9544$792d0b0f3eba | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9544$92f9408424d0 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9544$92f9408424d0 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9544$c0c8d2aed3c4 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | monolingualtext | ||||
STD:IETF:RFC9544$df0f5835de12 | IETF | STD:IETF:RFC9544 | Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | X. Min | X. Min | string | ||||
STD:IETF:RFC9545$02d5140e8e89 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9545$1f573c952fbc | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9545$29ccedcb5da1 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Li | C. Li | string | ||||
STD:IETF:RFC9545$68391f33112c | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9545$68391f33112c | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9545$6e9968de87a5 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9545$a4e6def96be5 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Path Segment Identifier in MPLS-Based Segment Routing Networks | Path Segment Identifier in MPLS-Based Segment Routing Networks | monolingualtext | ||||
STD:IETF:RFC9545$b17f54ed6884 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Li | H. Li | string | ||||
STD:IETF:RFC9545$c27294e9c56d | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Gandhi | R. Gandhi | string | ||||
STD:IETF:RFC9545$c3ed84458d53 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Cheng | W. Cheng | string | ||||
STD:IETF:RFC9545$eeea72d36e55 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A Segment Routing (SR) path is identified by an SR segment list. A subset of segments from the segment list cannot be leveraged to distinguish one SR path from another as they may be partially congruent. SR path identification is a prerequisite for various use cases such as performance measurement and end-to-end 1+1 pa... | A Segment Routing (SR) path is identified by an SR segment list. A subset of segments from the segment list cannot be leveraged to distinguish one SR path from another as they may be partially congruent. SR path identification is a prerequisite for various use cases such as performance measurement and end-to-end 1+1 pa... | monolingualtext | ||||
STD:IETF:RFC9545$f3e24f90f3c9 | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9545 | https://www.rfc-editor.org/rfc/rfc9545 | url | ||||
STD:IETF:RFC9545$f860695bb00e | IETF | STD:IETF:RFC9545 | Path Segment Identifier in MPLS-Based Segment Routing Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Zigler | R. Zigler | string | ||||
STD:IETF:RFC9546$3a76e1fe3229 | IETF | STD:IETF:RFC9546 | Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9546$44e22fc4c59a | IETF | STD:IETF:RFC9546 | Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Varga | B. Varga | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.