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:RFC9511$39daab25613d | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9511$4839bd99e957 | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9511 | https://www.rfc-editor.org/rfc/rfc9511 | url | ||||
STD:IETF:RFC9511$6cde50ff2439 | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9511$7278c832b293 | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Iurman | J. Iurman | string | ||||
STD:IETF:RFC9511$83e3be7e7a59 | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Active measurements over the public Internet can target either collaborating parties or non-collaborating ones. Sometimes these measurements, also called "probes", are viewed as unwelcome or aggressive. This document suggests some simple techniques for a source to identify its probes. This allows any party or organiza... | Active measurements over the public Internet can target either collaborating parties or non-collaborating ones. Sometimes these measurements, also called "probes", are viewed as unwelcome or aggressive. This document suggests some simple techniques for a source to identify its probes. This allows any party or organiza... | monolingualtext | ||||
STD:IETF:RFC9511$ff1e6a2f9477 | IETF | STD:IETF:RFC9511 | Attribution of Internet Probes | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | É. Vyncke | É. Vyncke | string | ||||
STD:IETF:RFC9512$17f819ff8a32 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Polli | R. Polli | string | ||||
STD:IETF:RFC9512$44036618a98a | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9512$558ecf7f53bd | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9512 | https://www.rfc-editor.org/rfc/rfc9512 | url | ||||
STD:IETF:RFC9512$733179c7f2f9 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Aro | E. Aro | string | ||||
STD:IETF:RFC9512$87a1133848c9 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9512$87a1133848c9 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9512$a723025c47ec | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | E. Wilde | E. Wilde | string | ||||
STD:IETF:RFC9512$bfe8fe100a94 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9512$e6aae2079f91 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document registers the application/yaml media type and the +yaml structured syntax suffix with IANA. Both identify document components that are serialized according to the YAML specification. | This document registers the application/yaml media type and the +yaml structured syntax suffix with IANA. Both identify document components that are serialized according to the YAML specification. | monolingualtext | ||||
STD:IETF:RFC9512$f72c5a4d9646 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9512$fe68c1e795c4 | IETF | STD:IETF:RFC9512 | YAML Media Type | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | YAML Media Type | YAML Media Type | monolingualtext | ||||
STD:IETF:RFC9513$411cf9135cfa | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9513$4cf31592157c | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9513$5cbd66fa550a | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | monolingualtext | ||||
STD:IETF:RFC9513$69e7f96bc796 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9513$69e7f96bc796 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9513$6ee3db9ca4a1 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Psenak | P. Psenak | string | ||||
STD:IETF:RFC9513$92133484e6b6 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Li | Z. Li | string | ||||
STD:IETF:RFC9513$ae1e35724af5 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9513$b1103790080b | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Hu | Z. Hu | string | ||||
STD:IETF:RFC9513$b79a8e7b3a2d | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Segment Routing (SR) architecture allows a flexible definition of the end-to-end path by encoding it as a sequence of topological elements called segments. It can be implemented over an MPLS or IPv6 data plane. This document describes the OSPFv3 extensions required to support SR over the IPv6 data plane. | The Segment Routing (SR) architecture allows a flexible definition of the end-to-end path by encoding it as a sequence of topological elements called segments. It can be implemented over an MPLS or IPv6 data plane. This document describes the OSPFv3 extensions required to support SR over the IPv6 data plane. | monolingualtext | ||||
STD:IETF:RFC9513$e006baa30e37 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9513 | https://www.rfc-editor.org/rfc/rfc9513 | url | ||||
STD:IETF:RFC9513$fa30c52b5007 | IETF | STD:IETF:RFC9513 | OSPFv3 Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9514$007a89f52ba4 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9514$13a821890056 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9514 | https://www.rfc-editor.org/rfc/rfc9514 | url | ||||
STD:IETF:RFC9514$51cef039315c | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9514$56595b7c0e06 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | monolingualtext | ||||
STD:IETF:RFC9514$5bf5fe3fecff | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9514$5f8c68f449c2 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Segment Routing over IPv6 (SRv6) allows for a flexible definition of end-to-end paths within various topologies by encoding paths as sequences of topological or functional sub-paths called "segments". These segments are advertised by various protocols such as BGP, IS-IS, and OSPFv3. This document defines extensions to... | Segment Routing over IPv6 (SRv6) allows for a flexible definition of end-to-end paths within various topologies by encoding paths as sequences of topological or functional sub-paths called "segments". These segments are advertised by various protocols such as BGP, IS-IS, and OSPFv3. This document defines extensions to... | monolingualtext | ||||
STD:IETF:RFC9514$71511a5a0ded | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9514$71511a5a0ded | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9514$75cc1a4b7ad1 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Decraene | B. Decraene | string | ||||
STD:IETF:RFC9514$a07628f6a277 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Dawra | G. Dawra | string | ||||
STD:IETF:RFC9514$a8a7ad0cef38 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Chen | M. Chen | string | ||||
STD:IETF:RFC9514$ada56a455625 | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9514$b738bd865aee | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9514$fada7fae9bfd | IETF | STD:IETF:RFC9514 | Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Bernier | D. Bernier | string | ||||
STD:IETF:RFC9515$488c9f4ccf33 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by changing the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range redesignated as "First Come First Served". | This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by changing the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range redesignated as "First Come First Served". | monolingualtext | ||||
STD:IETF:RFC9515$48b4e36d63f3 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9515$48b4e36d63f3 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9515$553d8ae03378 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Revision to Registration Procedures for Multiple BMP Registries | Revision to Registration Procedures for Multiple BMP Registries | monolingualtext | ||||
STD:IETF:RFC9515$6bfa35e92d7e | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Scudder | J. Scudder | string | ||||
STD:IETF:RFC9515$6de3cee6e254 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9515$a58077470d69 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9515$cc06e2fd18c5 | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9515$d169477ac67f | IETF | STD:IETF:RFC9515 | Revision to Registration Procedures for Multiple BMP Registries | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9515 | https://www.rfc-editor.org/rfc/rfc9515 | url | ||||
STD:IETF:RFC9516$049793cfd69a | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Meng | W. Meng | string | ||||
STD:IETF:RFC9516$07c122daa8b5 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9516 | https://www.rfc-editor.org/rfc/rfc9516 | url | ||||
STD:IETF:RFC9516$267837cfbc13 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | monolingualtext | ||||
STD:IETF:RFC9516$2decd8db808b | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Ao | T. Ao | string | ||||
STD:IETF:RFC9516$3641ec41d1b9 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9516$47e3c05c79e0 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9516$4b3a8f32eb0d | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9516$4dc87ac164ca | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mishra | G. Mishra | string | ||||
STD:IETF:RFC9516$5a5906407b24 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A set of requirements for active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) in a network is presented in this document. Based on these requirements, an encapsulation of active OAM messages in SFC and a mechanism to detect and localize defects are described. | A set of requirements for active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) in a network is presented in this document. Based on these requirements, an encapsulation of active OAM messages in SFC and a mechanism to detect and localize defects are described. | monolingualtext | ||||
STD:IETF:RFC9516$6dc782361104 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Leung | K. Leung | string | ||||
STD:IETF:RFC9516$b4c59f2424fb | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9516$b4c59f2424fb | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9516$b95beba20df4 | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9516$fa02a61e635f | IETF | STD:IETF:RFC9516 | Active Operations, Administration, and Maintenance (OAM) for Service Function Chaining (SFC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Khasnabish | B. Khasnabish | string | ||||
STD:IETF:RFC9517$03486251245e | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9517 | https://www.rfc-editor.org/rfc/rfc9517 | url | ||||
STD:IETF:RFC9517$23b7e2c75850 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | A URN Namespace for the Data Documentation Initiative (DDI) | A URN Namespace for the Data Documentation Initiative (DDI) | monolingualtext | ||||
STD:IETF:RFC9517$2b9407e4ec2f | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9517$3924ef1da953 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9517$57840e5a0b20 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9517$57840e5a0b20 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9517$6e187a1f510b | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Wackerow | J. Wackerow | string | ||||
STD:IETF:RFC9517$9f806deb0a10 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9517$fc93cee01b32 | IETF | STD:IETF:RFC9517 | A URN Namespace for the Data Documentation Initiative (DDI) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the Namespace Identifier (NID) "ddi" for Uniform Resource Names (URNs) used to identify resources that conform to the standards published by the Data Documentation Initiative (DDI) Alliance. The DDI Alliance is not affiliated with the Internet Engineering Task Force (IETF) or Internet Society (... | This document describes the Namespace Identifier (NID) "ddi" for Uniform Resource Names (URNs) used to identify resources that conform to the standards published by the Data Documentation Initiative (DDI) Alliance. The DDI Alliance is not affiliated with the Internet Engineering Task Force (IETF) or Internet Society (... | monolingualtext | ||||
STD:IETF:RFC9518$0c989345a70d | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9518 | https://www.rfc-editor.org/rfc/rfc9518 | url | ||||
STD:IETF:RFC9518$18c330de9257 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9518$34db1263ce16 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Centralization, Decentralization, and Internet Standards | Centralization, Decentralization, and Internet Standards | monolingualtext | ||||
STD:IETF:RFC9518$4f2a0a78591e | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses aspects of centralization that relate to Internet standards efforts. It argues that, while standards bodies have a limited ability to prevent many forms of centralization, they can still make contributions that assist in the decentralization of the Internet. | This document discusses aspects of centralization that relate to Internet standards efforts. It argues that, while standards bodies have a limited ability to prevent many forms of centralization, they can still make contributions that assist in the decentralization of the Internet. | monolingualtext | ||||
STD:IETF:RFC9518$59f8eeeaf3ba | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9518$9eb75b4388c5 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Nottingham | M. Nottingham | string | ||||
STD:IETF:RFC9518$a909da7591c0 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9518$d8ae728b5e27 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9518$d8ae728b5e27 | IETF | STD:IETF:RFC9518 | Centralization, Decentralization, and Internet Standards | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9519$14ad6aea9065 | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This specification updates the registration policies for adding new entries to registries within the IANA "Secure Shell (SSH) Protocol Parameters" group of registries. Previously, the registration policy was generally IETF Review, as defined in RFC 8126, although a few registries require Standards Action. This specif... | This specification updates the registration policies for adding new entries to registries within the IANA "Secure Shell (SSH) Protocol Parameters" group of registries. Previously, the registration policy was generally IETF Review, as defined in RFC 8126, although a few registries require Standards Action. This specif... | monolingualtext | ||||
STD:IETF:RFC9519$2df73d08187d | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9519$2df73d08187d | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9519$4bc94e144d7c | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Update to the IANA SSH Protocol Parameters Registry Requirements | Update to the IANA SSH Protocol Parameters Registry Requirements | monolingualtext | ||||
STD:IETF:RFC9519$5b3082b78b46 | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9519 | https://www.rfc-editor.org/rfc/rfc9519 | url | ||||
STD:IETF:RFC9519$7725cf7b5ff7 | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Yee | P. Yee | string | ||||
STD:IETF:RFC9519$b6ebc2215e73 | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9519$c1a2146018c3 | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9519$e34f45a7331b | IETF | STD:IETF:RFC9519 | Update to the IANA SSH Protocol Parameters Registry Requirements | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9520$1b2ae47d55cd | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9520$56f8192c7b6a | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Carroll | W. Carroll | string | ||||
STD:IETF:RFC9520$59d0803d1ae7 | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9520$6184b1bafa45 | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Wessels | D. Wessels | string | ||||
STD:IETF:RFC9520$7a434f5221d5 | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9520$7a434f5221d5 | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9520$7f475edcbe4d | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Thomas | M. Thomas | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.