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:RFC9608$9b341832cd6e | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9608$beab7425bcf6 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Housley | R. Housley | string | ||||
STD:IETF:RFC9608$c7d77c3ad6d5 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9608$ed4834ecbbc4 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9609$05aa72cfdaaf | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9609$06d1d7da5edd | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | P. Koch | P. Koch | string | ||||
STD:IETF:RFC9609$0ddfc832c3a5 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9609 | https://www.rfc-editor.org/rfc/rfc9609 | url | ||||
STD:IETF:RFC9609$37f76ad83442 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC8109 | RFC8109 | wikibase-item | ||||
STD:IETF:RFC9609$46a31dab4f12 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | P. Hoffman | P. Hoffman | string | ||||
STD:IETF:RFC9609$4f0fd5775254 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Initializing a DNS Resolver with Priming Queries | Initializing a DNS Resolver with Priming Queries | monolingualtext | ||||
STD:IETF:RFC9609$773a76ffa8af | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the queries that a DNS resolver should emit to initialize its cache. The result is that the resolver gets both a current NS resource record set (RRset) for the root zone and the necessary address information for reaching the root servers. This document obsoletes RFC 8109. | This document describes the queries that a DNS resolver should emit to initialize its cache. The result is that the resolver gets both a current NS resource record set (RRset) for the root zone and the necessary address information for reaching the root servers. This document obsoletes RFC 8109. | monolingualtext | ||||
STD:IETF:RFC9609$84c155abfbd6 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9609$84c155abfbd6 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9609$bdb0eb05ae77 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9609$d47ad61098ab | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | M. Larson | M. Larson | string | ||||
STD:IETF:RFC9609$e6fdfd4df633 | IETF | STD:IETF:RFC9609 | Initializing a DNS Resolver with Priming Queries | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9610$162f5264a78d | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Jenkins | N. Jenkins | string | ||||
STD:IETF:RFC9610$1680d176c6eb | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9610$1680d176c6eb | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9610$226133faa7e5 | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9610 | https://www.rfc-editor.org/rfc/rfc9610 | url | ||||
STD:IETF:RFC9610$42a19e36e156 | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9610$7b9025de921c | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9610$7cd1b802eea1 | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9610$a566bdcc267b | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | JSON Meta Application Protocol (JMAP) for Contacts | JSON Meta Application Protocol (JMAP) for Contacts | monolingualtext | ||||
STD:IETF:RFC9610$a66cc5a5eecd | IETF | STD:IETF:RFC9610 | JSON Meta Application Protocol (JMAP) for Contacts | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a data model for synchronising contact data with a server using the JSON Meta Application Protocol (JMAP). | This document specifies a data model for synchronising contact data with a server using the JSON Meta Application Protocol (JMAP). | monolingualtext | ||||
STD:IETF:RFC9611$014bbed10e53 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Klassert | S. Klassert | string | ||||
STD:IETF:RFC9611$08f1224d940b | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Antony | A. Antony | string | ||||
STD:IETF:RFC9611$380e099d35ea | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9611$56e0126fc734 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9611$7c199cae6ab7 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9611$7c199cae6ab7 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9611$8b40daff60be | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Brunner | T. Brunner | string | ||||
STD:IETF:RFC9611$994c6b04b346 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In order to increase the bandwidth of IPsec traffic between peers, this document defines one Notify Message Status Types and one Notify Message Error Types payload for the Internet Key Exchange Protocol Version 2 (IKEv2) to support the negotiation of multiple Child Security Associations (SAs) with the same Traffic Sele... | In order to increase the bandwidth of IPsec traffic between peers, this document defines one Notify Message Status Types and one Notify Message Error Types payload for the Internet Key Exchange Protocol Version 2 (IKEv2) to support the negotiation of multiple Child Security Associations (SAs) with the same Traffic Sele... | monolingualtext | ||||
STD:IETF:RFC9611$9f6d4e558b6f | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | monolingualtext | ||||
STD:IETF:RFC9611$c1be9f894f21 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Wouters | P. Wouters | string | ||||
STD:IETF:RFC9611$cf6e76348cec | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9611$d2669ad3c942 | IETF | STD:IETF:RFC9611 | Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9611 | https://www.rfc-editor.org/rfc/rfc9611 | url | ||||
STD:IETF:RFC9612$1311e2e78d51 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9612$75c6b9c4124f | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9612$75c6b9c4124f | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9612$7ba0fc4363f9 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | monolingualtext | ||||
STD:IETF:RFC9612$7fff20ba0163 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | I. Varlashkin | I. Varlashkin | string | ||||
STD:IETF:RFC9612$8477c984fa7f | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9612$8f222debcdfe | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9612$955c83571b83 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9612$969c94f845e9 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9612$a83b3ef78d62 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Bidirectional Forwarding Detection (BFD) is expected to be able to monitor a wide variety of encapsulations of paths between systems. When a BFD session monitors an explicitly routed unidirectional path, there may be a need to direct the egress BFD peer to use a specific path for the reverse direction of the BFD sessi... | Bidirectional Forwarding Detection (BFD) is expected to be able to monitor a wide variety of encapsulations of paths between systems. When a BFD session monitors an explicitly routed unidirectional path, there may be a need to direct the egress BFD peer to use a specific path for the reverse direction of the BFD sessi... | monolingualtext | ||||
STD:IETF:RFC9612$bfdbd71dc0f0 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | M. Chen | M. Chen | string | ||||
STD:IETF:RFC9612$d7a813b03d19 | IETF | STD:IETF:RFC9612 | Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9612 | https://www.rfc-editor.org/rfc/rfc9612 | url | ||||
STD:IETF:RFC9613$2613c78a242b | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9613$2613c78a242b | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9613$547d4527ca7e | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Drake | J. Drake | string | ||||
STD:IETF:RFC9613$5fa741b3d2d8 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Requirements for Solutions that Support MPLS Network Actions (MNAs) | Requirements for Solutions that Support MPLS Network Actions (MNAs) | monolingualtext | ||||
STD:IETF:RFC9613$6266df801524 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies requirements for the development of MPLS Network Actions (MNAs) that affect the forwarding or other processing of MPLS packets. These requirements are informed by a number of proposals for additions to the MPLS information in the labeled packet to allow such actions to be performed, either by a... | This document specifies requirements for the development of MPLS Network Actions (MNAs) that affect the forwarding or other processing of MPLS packets. These requirements are informed by a number of proposals for additions to the MPLS information in the labeled packet to allow such actions to be performed, either by a... | monolingualtext | ||||
STD:IETF:RFC9613$663ff8f6203c | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9613 | https://www.rfc-editor.org/rfc/rfc9613 | url | ||||
STD:IETF:RFC9613$9606b5e6fe62 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9613$9d5cb0654d26 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9613$9d7eb4afb22b | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Bocci | M. Bocci | string | ||||
STD:IETF:RFC9613$b495fe8dfe32 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Bryant | S. Bryant | string | ||||
STD:IETF:RFC9613$be8f3824c816 | IETF | STD:IETF:RFC9613 | Requirements for Solutions that Support MPLS Network Actions (MNAs) | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9614$12a207f0cd6e | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9614$240fa41b13ba | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the principle of privacy partitioning, which selectively spreads data and communication across multiple parties as a means to improve privacy by separating user identity from user data. This document describes emerging patterns in protocols to partition what data and metadata is revealed throug... | This document describes the principle of privacy partitioning, which selectively spreads data and communication across multiple parties as a means to improve privacy by separating user identity from user data. This document describes emerging patterns in protocols to partition what data and metadata is revealed throug... | monolingualtext | ||||
STD:IETF:RFC9614$3238ebaf820e | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. A. Wood | C. A. Wood | string | ||||
STD:IETF:RFC9614$4920d326f387 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Partitioning as an Architecture for Privacy | Partitioning as an Architecture for Privacy | monolingualtext | ||||
STD:IETF:RFC9614$53359bf7b9b3 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9614 | https://www.rfc-editor.org/rfc/rfc9614 | url | ||||
STD:IETF:RFC9614$5584bdb7ee8f | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9614$6ba08c525910 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Kühlewind | M. Kühlewind | string | ||||
STD:IETF:RFC9614$ae708c52d29d | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9614$df64c2390d42 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9614$df64c2390d42 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9614$e5d38c6b6d76 | IETF | STD:IETF:RFC9614 | Partitioning as an Architecture for Privacy | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9615$007ff64d4011 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document introduces an in-band method for DNS operators to publish arbitrary information about the zones for which they are authoritative, in an authenticated fashion and on a per-zone basis. The mechanism allows managed DNS operators to securely announce DNSSEC key parameters for zones under their management, inc... | This document introduces an in-band method for DNS operators to publish arbitrary information about the zones for which they are authoritative, in an authenticated fashion and on a per-zone basis. The mechanism allows managed DNS operators to securely announce DNSSEC key parameters for zones under their management, inc... | monolingualtext | ||||
STD:IETF:RFC9615$0f2a010ec346 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Thomassen | P. Thomassen | string | ||||
STD:IETF:RFC9615$2716f16a4c18 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | monolingualtext | ||||
STD:IETF:RFC9615$2ace9a71d080 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9615$758cdc5706ce | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9615$7d1fa6182213 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9615$7e2abd6bfb00 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Wisiol | N. Wisiol | string | ||||
STD:IETF:RFC9615$c012ec563154 | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9615 | https://www.rfc-editor.org/rfc/rfc9615 | url | ||||
STD:IETF:RFC9615$d6e42065fbfe | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9615$d6e42065fbfe | IETF | STD:IETF:RFC9615 | Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9616$053c0d4fbe6f | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Chroboczek | J. Chroboczek | string | ||||
STD:IETF:RFC9616$06b73af233c3 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9616$06b73af233c3 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9616$0d1df55657e5 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9616 | https://www.rfc-editor.org/rfc/rfc9616 | url | ||||
STD:IETF:RFC9616$20180206944a | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Delay-Based Metric Extension for the Babel Routing Protocol | Delay-Based Metric Extension for the Babel Routing Protocol | monolingualtext | ||||
STD:IETF:RFC9616$3c115bed8d1f | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9616$682439499190 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9616$6e4678093eb0 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines an extension to the Babel routing protocol that measures the round-trip time (RTT) between routers and makes it possible to prefer lower-latency links over higher-latency ones. | This document defines an extension to the Babel routing protocol that measures the round-trip time (RTT) between routers and makes it possible to prefer lower-latency links over higher-latency ones. | monolingualtext | ||||
STD:IETF:RFC9616$8ff69c7b4820 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9616$ae267c1aa006 | IETF | STD:IETF:RFC9616 | Delay-Based Metric Extension for the Babel Routing Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Jonglez | B. Jonglez | string | ||||
STD:IETF:RFC9617$2fa6f09b15bc | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9617 | https://www.rfc-editor.org/rfc/rfc9617 | url | ||||
STD:IETF:RFC9617$49b0d39eca93 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9617$564eacdb4c84 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9617$752e9bb9929a | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Brockners | F. Brockners | string | ||||
STD:IETF:RFC9617$89190f6b5ceb | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9617$89190f6b5ceb | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9617$8d56055ce39f | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | monolingualtext | ||||
STD:IETF:RFC9617$b645ccf15252 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In situ Operations, Administration, and Maintenance (IOAM) is an example of an on-path hybrid measurement method. IOAM defines a method for producing operational and telemetry information that may be exported using the in-band or out-of-band method. RFCs 9197 and 9326 discuss the data fields and associated data types... | In situ Operations, Administration, and Maintenance (IOAM) is an example of an on-path hybrid measurement method. IOAM defines a method for producing operational and telemetry information that may be exported using the in-band or out-of-band method. RFCs 9197 and 9326 discuss the data fields and associated data types... | monolingualtext | ||||
STD:IETF:RFC9617$b7b9c223b4e7 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Raghavan | S. Raghavan | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.