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:RFC9733$e9c816251223 | IETF | STD:IETF:RFC9733 | BRSKI with Alternative Enrollment (BRSKI-AE) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. von Oheimb | D. von Oheimb | string | ||||
STD:IETF:RFC9733$f5db90f855bd | IETF | STD:IETF:RFC9733 | BRSKI with Alternative Enrollment (BRSKI-AE) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | BRSKI with Alternative Enrollment (BRSKI-AE) | BRSKI with Alternative Enrollment (BRSKI-AE) | monolingualtext | ||||
STD:IETF:RFC9734$52f639340037 | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9734 | https://www.rfc-editor.org/rfc/rfc9734 | url | ||||
STD:IETF:RFC9734$547a8ff984cb | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | monolingualtext | ||||
STD:IETF:RFC9734$84e24af44fed | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 5280 specifies several extended key purpose identifiers (KeyPurposeIds) for X.509 certificates. This document defines an Instant Messaging (IM) identity KeyPurposeId for inclusion in the Extended Key Usage (EKU) extension of X.509 v3 public key certificates | RFC 5280 specifies several extended key purpose identifiers (KeyPurposeIds) for X.509 certificates. This document defines an Instant Messaging (IM) identity KeyPurposeId for inclusion in the Extended Key Usage (EKU) extension of X.509 v3 public key certificates | monolingualtext | ||||
STD:IETF:RFC9734$87d85172b787 | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9734$91fe14ca82de | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9734$a7d37f321ca1 | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Mahy | R. Mahy | string | ||||
STD:IETF:RFC9734$b3c7fae69a5c | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9734$b3c7fae69a5c | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9734$d280e0aded20 | IETF | STD:IETF:RFC9734 | X.509 Certificate Extended Key Usage (EKU) for Instant Messaging URIs | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9735$10a22a4d7065 | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9735$29b24c32e6df | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Farinacci | D. Farinacci | string | ||||
STD:IETF:RFC9735$3f5cf24462dd | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9735$3f5cf24462dd | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9735$4a512a3676cd | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9735$4afdc2d080ff | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | monolingualtext | ||||
STD:IETF:RFC9735$697ca9ae012f | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines how to use the Address Family Identifier (AFI) 17 "Distinguished Name" in the Locator/ID Separation Protocol (LISP). LISP introduces two new numbering spaces: Endpoint Identifiers (EIDs) and Routing Locators (RLOCs). Distinguished Names (DNs) can be used in either EID-Records or RLOC-Records in ... | This document defines how to use the Address Family Identifier (AFI) 17 "Distinguished Name" in the Locator/ID Separation Protocol (LISP). LISP introduces two new numbering spaces: Endpoint Identifiers (EIDs) and Routing Locators (RLOCs). Distinguished Names (DNs) can be used in either EID-Records or RLOC-Records in ... | monolingualtext | ||||
STD:IETF:RFC9735$7576f5d5a9eb | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9735 | https://www.rfc-editor.org/rfc/rfc9735 | url | ||||
STD:IETF:RFC9735$77ebe1820d37 | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9735$80685bb28843 | IETF | STD:IETF:RFC9735 | Locator/ID Separation Protocol (LISP) Distinguished Name Encoding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | L. Iannone | L. Iannone | string | ||||
STD:IETF:RFC9736$03e0e2882717 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9736$09484dd756b4 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Lucente | P. Lucente | string | ||||
STD:IETF:RFC9736$15eb36ebd5d6 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9736$25923448b867 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9736$2b0cdb854b60 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 7854, the BGP Monitoring Protocol (BMP), uses different message types for different purposes. Most of these are structured as Type, Length, Value (TLV). One message type, the Peer Up message, lacks a set of TLVs defined for its use, instead sharing a namespace with the Initiation message. Experience has shown that ... | RFC 7854, the BGP Monitoring Protocol (BMP), uses different message types for different purposes. Most of these are structured as Type, Length, Value (TLV). One message type, the Peer Up message, lacks a set of TLVs defined for its use, instead sharing a namespace with the Initiation message. Experience has shown that ... | monolingualtext | ||||
STD:IETF:RFC9736$44ecb05b132b | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | monolingualtext | ||||
STD:IETF:RFC9736$6c24b15765a3 | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Scudder | J. Scudder | string | ||||
STD:IETF:RFC9736$baf0fae9d90a | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9736$baf0fae9d90a | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9736$cac4ab92a2bd | IETF | STD:IETF:RFC9736 | The BGP Monitoring Protocol (BMP) Peer Up Message Namespace | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9736 | https://www.rfc-editor.org/rfc/rfc9736 | url | ||||
STD:IETF:RFC9737$1818968431ff | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Parallel Network File System (pNFS) allows for a file's metadata and data to be on different servers (i.e., the metadata server (MDS) and the data server (DS)). When the MDS is restarted, the client can still modify the data file component. During the recovery phase of startup, the MDS and the DSs work together t... | The Parallel Network File System (pNFS) allows for a file's metadata and data to be on different servers (i.e., the metadata server (MDS) and the data server (DS)). When the MDS is restarted, the client can still modify the data file component. During the recovery phase of startup, the MDS and the DSs work together t... | monolingualtext | ||||
STD:IETF:RFC9737$2ff1a4b7f011 | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9737$739e921e100c | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Haynes | T. Haynes | string | ||||
STD:IETF:RFC9737$a7ad7d1411ea | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9737$cfa20286e1af | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9737 | https://www.rfc-editor.org/rfc/rfc9737 | url | ||||
STD:IETF:RFC9737$da6bbc5c7efd | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Myklebust | T. Myklebust | string | ||||
STD:IETF:RFC9737$e3f3a386d75c | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9737$e7fd99884ac9 | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Reporting Errors in NFSv4.2 via LAYOUTRETURN | Reporting Errors in NFSv4.2 via LAYOUTRETURN | monolingualtext | ||||
STD:IETF:RFC9737$fba62f80f850 | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9737$fba62f80f850 | IETF | STD:IETF:RFC9737 | Reporting Errors in NFSv4.2 via LAYOUTRETURN | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9738$0b5e59405032 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9738$0b5e59405032 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9738$2d5adfcdb4de | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | V. Nagulakonda | V. Nagulakonda | string | ||||
STD:IETF:RFC9738$49a6c36c88cf | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9738$61689e355476 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | A. Melnikov | A. Melnikov | string | ||||
STD:IETF:RFC9738$90647ca86e31 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The MESSAGELIMIT extension of the Internet Message Access Protocol (RFCs 3501 and 9051) allows servers to announce a limit on the number of messages that can be processed in a single FETCH, SEARCH, STORE, COPY, or MOVE command (or their UID variants), or in a single APPEND or UID EXPUNGE command. This helps servers to... | The MESSAGELIMIT extension of the Internet Message Access Protocol (RFCs 3501 and 9051) allows servers to announce a limit on the number of messages that can be processed in a single FETCH, SEARCH, STORE, COPY, or MOVE command (or their UID variants), or in a single APPEND or UID EXPUNGE command. This helps servers to... | monolingualtext | ||||
STD:IETF:RFC9738$995e61e45749 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9738$c6b5f96e8293 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | A. P. Achuthan | A. P. Achuthan | string | ||||
STD:IETF:RFC9738$d9aac450009b | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | L. Alves | L. Alves | string | ||||
STD:IETF:RFC9738$eedfbbc00ece | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | IMAP MESSAGELIMIT Extension | IMAP MESSAGELIMIT Extension | monolingualtext | ||||
STD:IETF:RFC9738$f0e38af96f5c | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9738$f9521df3ad10 | IETF | STD:IETF:RFC9738 | IMAP MESSAGELIMIT Extension | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9738 | https://www.rfc-editor.org/rfc/rfc9738 | url | ||||
STD:IETF:RFC9739$4a613ad33399 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9739$4a613ad33399 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9739$4af4d3c623a4 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9739$5e2449304fb0 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Mishra | M. Mishra | string | ||||
STD:IETF:RFC9739$83606cc127ad | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9739$9a28f58498b3 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9739$aaee13d12410 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Venaas | S. Venaas | string | ||||
STD:IETF:RFC9739$b351211257dc | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9739$b7992f20fec4 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. McBride | M. McBride | string | ||||
STD:IETF:RFC9739$b94a158ed6e3 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Bidgoli | H. Bidgoli | string | ||||
STD:IETF:RFC9739$d4b885e6a031 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies Protocol Independent Multicast Light (PIM Light) and the PIM Light Interface (PLI). A PLI does not need a PIM Hello message to accept PIM Join/Prune messages, and it can signal multicast states over networks that cannot support full PIM neighbor discovery, such as Bit Index Explicit Replication... | This document specifies Protocol Independent Multicast Light (PIM Light) and the PIM Light Interface (PLI). A PLI does not need a PIM Hello message to accept PIM Join/Prune messages, and it can signal multicast states over networks that cannot support full PIM neighbor discovery, such as Bit Index Explicit Replication... | monolingualtext | ||||
STD:IETF:RFC9739$dc1b5a436b22 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Protocol Independent Multicast Light (PIM Light) | Protocol Independent Multicast Light (PIM Light) | monolingualtext | ||||
STD:IETF:RFC9739$dc543a8ef421 | IETF | STD:IETF:RFC9739 | Protocol Independent Multicast Light (PIM Light) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9739 | https://www.rfc-editor.org/rfc/rfc9739 | url | ||||
STD:IETF:RFC9740$0d918864f445 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies new IP Flow Information Export (IPFIX) Information Elements (IEs) to solve issues with existing ipv6ExtensionHeaders and tcpOptions IPFIX IEs, especially the ability to export any observed IPv6 extension headers or TCP options. | This document specifies new IP Flow Information Export (IPFIX) Information Elements (IEs) to solve issues with existing ipv6ExtensionHeaders and tcpOptions IPFIX IEs, especially the ability to export any observed IPv6 extension headers or TCP options. | monolingualtext | ||||
STD:IETF:RFC9740$10f8d8af4268 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9740 | https://www.rfc-editor.org/rfc/rfc9740 | url | ||||
STD:IETF:RFC9740$760cae59fc9d | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9740$826ccd50d866 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9740$a347c57c075f | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | monolingualtext | ||||
STD:IETF:RFC9740$aa49e9b985f8 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9740$b081df811b12 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9740$b081df811b12 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9740$f0872efe45d0 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9740$fadc2f2d6c71 | IETF | STD:IETF:RFC9740 | New IPFIX Information Elements for TCP Options and IPv6 Extension Headers | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Claise | B. Claise | string | ||||
STD:IETF:RFC9741$922c5e5a2b3d | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9741 | https://www.rfc-editor.org/rfc/rfc9741 | url | ||||
STD:IETF:RFC9741$a057e6453cac | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Bormann | C. Bormann | string | ||||
STD:IETF:RFC9741$a5bdbb71b8a5 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9741$ae13f92a3f42 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | monolingualtext | ||||
STD:IETF:RFC9741$c770c27bc14b | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Concise Data Definition Language (CDDL), standardized in RFC 8610, provides "control operators" as its main language extension point. RFCs have added to this extension point in both an application-specific and a more general way. The present document defines a number of additional generally applicable control oper... | The Concise Data Definition Language (CDDL), standardized in RFC 8610, provides "control operators" as its main language extension point. RFCs have added to this extension point in both an application-specific and a more general way. The present document defines a number of additional generally applicable control oper... | monolingualtext | ||||
STD:IETF:RFC9741$cfffee006f73 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9741$ebce88d00df6 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9741$fe9ba9dd7c22 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9741$fe9ba9dd7c22 | IETF | STD:IETF:RFC9741 | Concise Data Definition Language (CDDL): Additional Control Operators for the Conversion and Processing of Text | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9742$086d9e5ac5f6 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9742 | https://www.rfc-editor.org/rfc/rfc9742 | url | ||||
STD:IETF:RFC9742$3c1c586cc687 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a YANG data model for the management of a syslog process. It is intended that this data model be used by vendors who implement syslog collectors in their systems. | This document defines a YANG data model for the management of a syslog process. It is intended that this data model be used by vendors who implement syslog collectors in their systems. | monolingualtext | ||||
STD:IETF:RFC9742$5c082765a155 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Koushik | K. Koushik | string | ||||
STD:IETF:RFC9742$6cbd984c6fd5 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9742$6cbd984c6fd5 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9742$726d0ac3324c | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9742$7c13a2e6f068 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for Syslog Management | A YANG Data Model for Syslog Management | monolingualtext | ||||
STD:IETF:RFC9742$7fd9ca3ff97a | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Jethanandani | M. Jethanandani | string | ||||
STD:IETF:RFC9742$c35712cd0703 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Clarke | J. Clarke | string | ||||
STD:IETF:RFC9742$d6faaa991344 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9742$d890a1f8f0a0 | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9742$fdcd525f51ce | IETF | STD:IETF:RFC9742 | A YANG Data Model for Syslog Management | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Wildes | C. Wildes | string | ||||
STD:IETF:RFC9743$0543d96e3e11 | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P1476 | title | Specifying New Congestion Control Algorithms | Specifying New Congestion Control Algorithms | monolingualtext | ||||
STD:IETF:RFC9743$2034894b6b9f | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9743$2034894b6b9f | IETF | STD:IETF:RFC9743 | Specifying New Congestion Control Algorithms | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.