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:RFC9343$16689601af4b | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2022-01 | 2022-01 | time | ||||
STD:IETF:RFC9343$4ab18e68559c | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Fioccola | G. Fioccola | string | ||||
STD:IETF:RFC9343$622948bc6ff7 | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9343$622948bc6ff7 | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9343$86d16e2f430c | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Cociglio | M. Cociglio | string | ||||
STD:IETF:RFC9343$917a5ade4c7c | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9343$92a9bdd629f7 | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9343 | https://www.rfc-editor.org/rfc/rfc9343 | url | ||||
STD:IETF:RFC9343$99e985e00ed0 | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes how the Alternate-Marking Method can be used as a passive performance measurement tool in an IPv6 domain. It defines an Extension Header Option to encode Alternate-Marking information in both the Hop-by-Hop Options Header and Destination Options Header. | This document describes how the Alternate-Marking Method can be used as a passive performance measurement tool in an IPv6 domain. It defines an Extension Header Option to encode Alternate-Marking information in both the Hop-by-Hop Options Header and Destination Options Header. | monolingualtext | ||||
STD:IETF:RFC9343$9cf3ad635fac | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Qin | F. Qin | string | ||||
STD:IETF:RFC9343$b2c0133884eb | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Zhou | T. Zhou | string | ||||
STD:IETF:RFC9343$fa3d2f0a5bba | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IPv6 Application of the Alternate-Marking Method | IPv6 Application of the Alternate-Marking Method | monolingualtext | ||||
STD:IETF:RFC9343$fe6ef624483b | IETF | STD:IETF:RFC9343 | IPv6 Application of the Alternate-Marking Method | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9344$0638fa6e9189 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9344$45ab7f88a760 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a mechanism named "CCNinfo" that discovers information about the network topology and in-network cache in Content-Centric Networks (CCNs). CCNinfo investigates 1) the CCN routing path information per name prefix, 2) the Round-Trip Time (RTT) between the content forwarder and the consumer, and 3)... | This document describes a mechanism named "CCNinfo" that discovers information about the network topology and in-network cache in Content-Centric Networks (CCNs). CCNinfo investigates 1) the CCN routing path information per name prefix, 2) the Round-Trip Time (RTT) between the content forwarder and the consumer, and 3)... | monolingualtext | ||||
STD:IETF:RFC9344$522b9202c92d | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9344$74dc1c504b86 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9344$98e859795aaf | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | monolingualtext | ||||
STD:IETF:RFC9344$a9482b85f559 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | H. Asaeda | H. Asaeda | string | ||||
STD:IETF:RFC9344$cb8e6c14afec | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9344 | https://www.rfc-editor.org/rfc/rfc9344 | url | ||||
STD:IETF:RFC9344$d09068de7404 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | X. Shao | X. Shao | string | ||||
STD:IETF:RFC9344$e000aa02a937 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9344$e000aa02a937 | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9344$e35c0e954f7a | IETF | STD:IETF:RFC9344 | CCNinfo: Discovering Content and Network Information in Content-Centric Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | A. Ooka | A. Ooka | string | ||||
STD:IETF:RFC9345$1aa2c6aaebb7 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Sullivan | N. Sullivan | string | ||||
STD:IETF:RFC9345$40768dfbe4fb | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Rescorla | E. Rescorla | string | ||||
STD:IETF:RFC9345$4a3434375aba | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Barnes | R. Barnes | string | ||||
STD:IETF:RFC9345$4f66a9e30407 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9345$67ea519d923f | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Iyengar | S. Iyengar | string | ||||
STD:IETF:RFC9345$7204ea41ad8b | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9345$7204ea41ad8b | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9345$89323f6ece16 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The organizational separation between operators of TLS and DTLS endpoints and the certification authority can create limitations. For example, the lifetime of certificates, how they may be used, and the algorithms they support are ultimately determined by the Certification Authority (CA). This document describes a me... | The organizational separation between operators of TLS and DTLS endpoints and the certification authority can create limitations. For example, the lifetime of certificates, how they may be used, and the algorithms they support are ultimately determined by the Certification Authority (CA). This document describes a me... | monolingualtext | ||||
STD:IETF:RFC9345$89b97a109ad4 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Delegated Credentials for TLS and DTLS | Delegated Credentials for TLS and DTLS | monolingualtext | ||||
STD:IETF:RFC9345$99c97920c5b2 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9345$a016ccc0364f | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9345$d96fea98d128 | IETF | STD:IETF:RFC9345 | Delegated Credentials for TLS and DTLS | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9345 | https://www.rfc-editor.org/rfc/rfc9345 | url | ||||
STD:IETF:RFC9346$063e46783db1 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Previdi | S. Previdi | string | ||||
STD:IETF:RFC9346$249a6b6ed71e | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9346$2d70ff393823 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Xiaodong | D. Xiaodong | string | ||||
STD:IETF:RFC9346$3d2ff081d7d6 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9346$3dedda431d8a | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC5316 | RFC5316 | wikibase-item | ||||
STD:IETF:RFC9346$68227c66b213 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9346 | https://www.rfc-editor.org/rfc/rfc9346 | url | ||||
STD:IETF:RFC9346$81999edab4c3 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | monolingualtext | ||||
STD:IETF:RFC9346$9755a7cc8b28 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9346$a24c28ddcd43 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Ginsberg | L. Ginsberg | string | ||||
STD:IETF:RFC9346$e3f31c832880 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Chen | M. Chen | string | ||||
STD:IETF:RFC9346$e66f4b88987c | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9346$e66f4b88987c | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9346$f16a8f0f8b59 | IETF | STD:IETF:RFC9346 | IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). It defines IS-IS extensions for the flooding of TE information about inter-A... | This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) for multiple Autonomous Systems (ASes). It defines IS-IS extensions for the flooding of TE information about inter-A... | monolingualtext | ||||
STD:IETF:RFC9347$1fdef523b721 | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9347 | https://www.rfc-editor.org/rfc/rfc9347 | url | ||||
STD:IETF:RFC9347$27bd6f08cefa | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Hopps | C. Hopps | string | ||||
STD:IETF:RFC9347$8a3e6b9d6b6c | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | monolingualtext | ||||
STD:IETF:RFC9347$a0504b18a5c1 | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9347$af0cbf77ca0d | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9347$b20def15edc9 | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9347$b20def15edc9 | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9347$cbf38c5ca932 | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a mechanism for aggregation and fragmentation of IP packets when they are being encapsulated in Encapsulating Security Payload (ESP). This new payload type can be used for various purposes, such as decreasing encapsulation overhead for small IP packets; however, the focus in this document is to... | This document describes a mechanism for aggregation and fragmentation of IP packets when they are being encapsulated in Encapsulating Security Payload (ESP). This new payload type can be used for various purposes, such as decreasing encapsulation overhead for small IP packets; however, the focus in this document is to... | monolingualtext | ||||
STD:IETF:RFC9347$cff9c8ac009f | IETF | STD:IETF:RFC9347 | Aggregation and Fragmentation Mode for Encapsulating Security Payload (ESP) and Its Use for IP Traffic Flow Security (IP-TFS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9348$06c6ee85f2d0 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for IP Traffic Flow Security | A YANG Data Model for IP Traffic Flow Security | monolingualtext | ||||
STD:IETF:RFC9348$2961881ff7f3 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Hopps | C. Hopps | string | ||||
STD:IETF:RFC9348$2cd35ce643eb | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9348 | https://www.rfc-editor.org/rfc/rfc9348 | url | ||||
STD:IETF:RFC9348$465a7e9f5e07 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9348$465a7e9f5e07 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9348$56213f80475b | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9348$8389a0694048 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Fedyk | D. Fedyk | string | ||||
STD:IETF:RFC9348$b443e94faa42 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9348$c47c9b154349 | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a YANG module for the management of IP Traffic Flow Security (IP-TFS) additions to Internet Key Exchange Protocol version 2 (IKEv2) and IPsec. | This document describes a YANG module for the management of IP Traffic Flow Security (IP-TFS) additions to Internet Key Exchange Protocol version 2 (IKEv2) and IPsec. | monolingualtext | ||||
STD:IETF:RFC9348$de7e2af81a9d | IETF | STD:IETF:RFC9348 | A YANG Data Model for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9349$034c8712b900 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Fedyk | D. Fedyk | string | ||||
STD:IETF:RFC9349$30a65fe97a1c | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9349$31524fab57b1 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Definitions of Managed Objects for IP Traffic Flow Security | Definitions of Managed Objects for IP Traffic Flow Security | monolingualtext | ||||
STD:IETF:RFC9349$41cd4b19f24d | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9349$6c540e78a1f9 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes managed objects for the management of IP Traffic Flow Security additions to Internet Key Exchange Protocol Version 2 (IKEv2) and IPsec. This document provides a read-only version of the objects defined in the YANG module for the same purpose, which is in "A YANG Data Model for IP Traffic Flow S... | This document describes managed objects for the management of IP Traffic Flow Security additions to Internet Key Exchange Protocol Version 2 (IKEv2) and IPsec. This document provides a read-only version of the objects defined in the YANG module for the same purpose, which is in "A YANG Data Model for IP Traffic Flow S... | monolingualtext | ||||
STD:IETF:RFC9349$765d7f3bf870 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9349$765d7f3bf870 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9349$82d6393f08e7 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Kinzie | E. Kinzie | string | ||||
STD:IETF:RFC9349$9ecd66dda411 | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9349$b1e212acdedd | IETF | STD:IETF:RFC9349 | Definitions of Managed Objects for IP Traffic Flow Security | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9349 | https://www.rfc-editor.org/rfc/rfc9349 | url | ||||
STD:IETF:RFC9350$08f8312759ae | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9350$0c617b90d4b1 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Hegde | S. Hegde | string | ||||
STD:IETF:RFC9350$0e332c85e086 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9350 | https://www.rfc-editor.org/rfc/rfc9350 | url | ||||
STD:IETF:RFC9350$586b973e359f | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9350$72915586700a | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | IGP protocols historically compute the best paths over the network based on the IGP metric assigned to the links. Many network deployments use RSVP-TE or Segment Routing - Traffic Engineering (SR-TE) to steer traffic over a path that is computed using different metrics or constraints than the shortest IGP path. This ... | IGP protocols historically compute the best paths over the network based on the IGP metric assigned to the links. Many network deployments use RSVP-TE or Segment Routing - Traffic Engineering (SR-TE) to steer traffic over a path that is computed using different metrics or constraints than the shortest IGP path. This ... | monolingualtext | ||||
STD:IETF:RFC9350$7548fd8c8029 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Gulko | A. Gulko | string | ||||
STD:IETF:RFC9350$76eff4d706f7 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9350$9e55a7010216 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9350$a820bc1b022a | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9350$a820bc1b022a | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9350$ceb22e535519 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9350$ec85db5fc108 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | IGP Flexible Algorithm | IGP Flexible Algorithm | monolingualtext | ||||
STD:IETF:RFC9350$f24af100f494 | IETF | STD:IETF:RFC9350 | IGP Flexible Algorithm | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9351$11d36084cd90 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9351$1864b9607cc7 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9351$1864b9607cc7 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9351$47d55447fa61 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9351$578976cd8dc3 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | monolingualtext | ||||
STD:IETF:RFC9351$594f42de5360 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9351 | https://www.rfc-editor.org/rfc/rfc9351 | url | ||||
STD:IETF:RFC9351$6e3be635be73 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Zandi | S. Zandi | string | ||||
STD:IETF:RFC9351$7c2e3d25e9cd | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Dawra | G. Dawra | string | ||||
STD:IETF:RFC9351$9a626381f8a0 | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9351$9de63c22173a | IETF | STD:IETF:RFC9351 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm Advertisement | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.