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:RFC9417$1763804a7468 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Quilbeuf | J. Quilbeuf | string | ||||
STD:IETF:RFC9417$1f886c0d0e59 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an architecture that provides some assurance that service instances are running as expected. As services rely upon multiple subservices provided by a variety of elements, including the underlying network devices and functions, getting the assurance of a healthy service is only possible with a h... | This document describes an architecture that provides some assurance that service instances are running as expected. As services rely upon multiple subservices provided by a variety of elements, including the underlying network devices and functions, getting the assurance of a healthy service is only possible with a h... | monolingualtext | ||||
STD:IETF:RFC9417$223552140463 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9417$2c7cd8ec3f7f | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9417$31a74d518a20 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9417$31a74d518a20 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9417$44d86bcd35dc | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Voyer | D. Voyer | string | ||||
STD:IETF:RFC9417$4af6b2a0af51 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Lopez | D. Lopez | string | ||||
STD:IETF:RFC9417$5485ae5589a2 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9417 | https://www.rfc-editor.org/rfc/rfc9417 | url | ||||
STD:IETF:RFC9417$71d2433d15b2 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9417$cf2475019813 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Service Assurance for Intent-Based Networking Architecture | Service Assurance for Intent-Based Networking Architecture | monolingualtext | ||||
STD:IETF:RFC9417$ffbfa748d8d4 | IETF | STD:IETF:RFC9417 | Service Assurance for Intent-Based Networking Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Arumugam | T. Arumugam | string | ||||
STD:IETF:RFC9418$108d14fecafe | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9418$377d1902f9c2 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9418$4f4496d7f62b | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9418 | https://www.rfc-editor.org/rfc/rfc9418 | url | ||||
STD:IETF:RFC9418$62b62095ef3c | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies YANG modules for representing assurance graphs. These graphs represent the assurance of a given service by decomposing it into atomic assurance elements called subservices. The companion document, "Service Assurance for Intent-Based Networking Architecture" (RFC 9417), presents an architecture f... | This document specifies YANG modules for representing assurance graphs. These graphs represent the assurance of a given service by decomposing it into atomic assurance elements called subservices. The companion document, "Service Assurance for Intent-Based Networking Architecture" (RFC 9417), presents an architecture f... | monolingualtext | ||||
STD:IETF:RFC9418$638776c3042d | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Lucente | P. Lucente | string | ||||
STD:IETF:RFC9418$6963c11f96ce | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9418$7290cfb938c7 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A YANG Data Model for Service Assurance | A YANG Data Model for Service Assurance | monolingualtext | ||||
STD:IETF:RFC9418$a3166d4ceff0 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Quilbeuf | J. Quilbeuf | string | ||||
STD:IETF:RFC9418$d3da85686786 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Claise | B. Claise | string | ||||
STD:IETF:RFC9418$e767181e0600 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9418$e767181e0600 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9418$f55ac13198a4 | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Arumugam | T. Arumugam | string | ||||
STD:IETF:RFC9418$fbeeb0d428ee | IETF | STD:IETF:RFC9418 | A YANG Data Model for Service Assurance | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Fasano | P. Fasano | string | ||||
STD:IETF:RFC9419$3dd72d0bb6e0 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document discusses principles for designing mechanisms that use or provide path signals and calls for standards action in specific valuable cases. RFC 8558 describes path signals as messages to or from on-path elements and points out that visible information will be used whether or not it is intended as a signal.... | This document discusses principles for designing mechanisms that use or provide path signals and calls for standards action in specific valuable cases. RFC 8558 describes path signals as messages to or from on-path elements and points out that visible information will be used whether or not it is intended as a signal.... | monolingualtext | ||||
STD:IETF:RFC9419$4aebe5111619 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9419$4aebe5111619 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9419$67c4d6bdad35 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Considerations on Application - Network Collaboration Using Path Signals | Considerations on Application - Network Collaboration Using Path Signals | monolingualtext | ||||
STD:IETF:RFC9419$741f785ce575 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9419$a52e0dc54445 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9419$a865b39f98bf | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9419$b4aa85833c8a | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Kühlewind | M. Kühlewind | string | ||||
STD:IETF:RFC9419$c6e60ffe4f78 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Hardie | T. Hardie | string | ||||
STD:IETF:RFC9419$ca2d3a03f48a | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Arkko | J. Arkko | string | ||||
STD:IETF:RFC9419$de3c630f48dc | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9419$fe98ba495cc9 | IETF | STD:IETF:RFC9419 | Considerations on Application - Network Collaboration Using Path Signals | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9419 | https://www.rfc-editor.org/rfc/rfc9419 | url | ||||
STD:IETF:RFC9420$0c594a11af5a | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9420$30a586cb7569 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Omara | E. Omara | string | ||||
STD:IETF:RFC9420$6685a383b53e | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9420$6685a383b53e | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9420$7e2b16ab3e3f | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Beurdouche | B. Beurdouche | string | ||||
STD:IETF:RFC9420$a350bc11dd58 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9420 | https://www.rfc-editor.org/rfc/rfc9420 | url | ||||
STD:IETF:RFC9420$c083259f1ea5 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Robert | R. Robert | string | ||||
STD:IETF:RFC9420$d4c05fbca559 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Barnes | R. Barnes | string | ||||
STD:IETF:RFC9420$d7fde3486a48 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicating endpoints, and not to any servers involved in delivering messages. Establishing keys to provide such protections is challenging for group chat settings, in which more th... | Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicating endpoints, and not to any servers involved in delivering messages. Establishing keys to provide such protections is challenging for group chat settings, in which more th... | monolingualtext | ||||
STD:IETF:RFC9420$d8933daa5a54 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Cohn-Gordon | K. Cohn-Gordon | string | ||||
STD:IETF:RFC9420$df94239fc6c0 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9420$e11918da499f | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The Messaging Layer Security (MLS) Protocol | The Messaging Layer Security (MLS) Protocol | monolingualtext | ||||
STD:IETF:RFC9420$ef2a68ed85dd | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9420$fbdb53035358 | IETF | STD:IETF:RFC9420 | The Messaging Layer Security (MLS) Protocol | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Millican | J. Millican | string | ||||
STD:IETF:RFC9421$19a654039582 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Richer | J. Richer | string | ||||
STD:IETF:RFC9421$31f0739104ee | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9421$52f4f2ae9709 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9421$61d0ddadaf26 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9421$7a2a36433c0c | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9421 | https://www.rfc-editor.org/rfc/rfc9421 | url | ||||
STD:IETF:RFC9421$8a2b9358d2e2 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9421$8a2b9358d2e2 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9421$a64ab672fecc | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Sporny | M. Sporny | string | ||||
STD:IETF:RFC9421$a64b1ef382cd | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Backman | A. Backman | string | ||||
STD:IETF:RFC9421$da8c5bac0a7c | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries... | This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries... | monolingualtext | ||||
STD:IETF:RFC9421$dba9a2729400 | IETF | STD:IETF:RFC9421 | HTTP Message Signatures | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | HTTP Message Signatures | HTTP Message Signatures | monolingualtext | ||||
STD:IETF:RFC9422$08e355b8d3d0 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9422$093342d1ca98 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Klensin | J. Klensin | string | ||||
STD:IETF:RFC9422$2c121adf9d48 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | N. Freed | N. Freed | string | ||||
STD:IETF:RFC9422$8889c07757d2 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines a LIMITS extension for the Simple Mail Transfer Protocol (SMTP), including submission, as well as the Local Mail Transfer Protocol (LMTP). It also defines an associated limit registry. The extension provides the means for an SMTP, submission, or LMTP server to inform the client of limits the ser... | This document defines a LIMITS extension for the Simple Mail Transfer Protocol (SMTP), including submission, as well as the Local Mail Transfer Protocol (LMTP). It also defines an associated limit registry. The extension provides the means for an SMTP, submission, or LMTP server to inform the client of limits the ser... | monolingualtext | ||||
STD:IETF:RFC9422$897b514685c3 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | The LIMITS SMTP Service Extension | The LIMITS SMTP Service Extension | monolingualtext | ||||
STD:IETF:RFC9422$a3a35034dbd3 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9422$ae6c4730aeef | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9422 | https://www.rfc-editor.org/rfc/rfc9422 | url | ||||
STD:IETF:RFC9422$b227202ee5af | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9422$b227202ee5af | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9422$ec481b7132a0 | IETF | STD:IETF:RFC9422 | The LIMITS SMTP Service Extension | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9423$865e0137f1f4 | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9423 | https://www.rfc-editor.org/rfc/rfc9423 | url | ||||
STD:IETF:RFC9423$9bdbdeff840b | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | C. Bormann | C. Bormann | string | ||||
STD:IETF:RFC9423$acaaca0972a7 | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9423$bb7cac64a25c | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Constrained RESTful Environments (CoRE) Target Attributes Registry | Constrained RESTful Environments (CoRE) Target Attributes Registry | monolingualtext | ||||
STD:IETF:RFC9423$c172d89f2dca | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9423$e1408dfb0b87 | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9423$e1408dfb0b87 | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9423$e288834ed07b | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9423$f2d22be05759 | IETF | STD:IETF:RFC9423 | Constrained RESTful Environments (CoRE) Target Attributes Registry | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Constrained RESTful Environments (CoRE) specifications apply web technologies to constrained environments. One such important technology is Web Linking (RFC 8288), which CoRE specifications use as the basis for a number of discovery protocols, such as the Link Format (RFC 6690) in the Constrained Application Protoc... | The Constrained RESTful Environments (CoRE) specifications apply web technologies to constrained environments. One such important technology is Web Linking (RFC 8288), which CoRE specifications use as the basis for a number of discovery protocols, such as the Link Format (RFC 6690) in the Constrained Application Protoc... | monolingualtext | ||||
STD:IETF:RFC9424$0376a76dc135 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Indicators of Compromise (IoCs) and Their Role in Attack Defence | Indicators of Compromise (IoCs) and Their Role in Attack Defence | monolingualtext | ||||
STD:IETF:RFC9424$0762800d3139 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | K. Paine | K. Paine | string | ||||
STD:IETF:RFC9424$08ebf1c396b3 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9424$20e184bafe4b | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Shaw | A. Shaw | string | ||||
STD:IETF:RFC9424$258a2ed4efca | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9424$659ed846b373 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | O. Whitehouse | O. Whitehouse | string | ||||
STD:IETF:RFC9424$7e1807d4f206 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9424$7e1807d4f206 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9424$a1fb0ab333c9 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Cyber defenders frequently rely on Indicators of Compromise (IoCs) to identify, trace, and block malicious activity in networks or on endpoints. This document reviews the fundamentals, opportunities, operational limitations, and recommendations for IoC use. It highlights the need for IoCs to be detectable in implemen... | Cyber defenders frequently rely on Indicators of Compromise (IoCs) to identify, trace, and block malicious activity in networks or on endpoints. This document reviews the fundamentals, opportunities, operational limitations, and recommendations for IoC use. It highlights the need for IoCs to be detectable in implemen... | monolingualtext | ||||
STD:IETF:RFC9424$ce926289d9e8 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | J. Sellwood | J. Sellwood | string | ||||
STD:IETF:RFC9424$ef340e255fb4 | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9424$fe975f18c60e | IETF | STD:IETF:RFC9424 | Indicators of Compromise (IoCs) and Their Role in Attack Defence | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9424 | https://www.rfc-editor.org/rfc/rfc9424 | url | ||||
STD:IETF:RFC9425$0ab31c860718 | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | JSON Meta Application Protocol (JMAP) for Quotas | JSON Meta Application Protocol (JMAP) for Quotas | monolingualtext | ||||
STD:IETF:RFC9425$19ca495547dd | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Cordier | R. Cordier | string | ||||
STD:IETF:RFC9425$31618efa617a | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9425$3f2e923bfd06 | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9425$b2943438423d | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9425$b2943438423d | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9425$d185d69e04c7 | IETF | STD:IETF:RFC9425 | JSON Meta Application Protocol (JMAP) for Quotas | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a data model for handling quotas on accounts with a server using the JSON Meta Application Protocol (JMAP). | This document specifies a data model for handling quotas on accounts with a server using the JSON Meta Application Protocol (JMAP). | monolingualtext |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.