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:RFC9520$c1d498d2a76f | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In the DNS, resolvers employ caching to reduce both latency for end users and load on authoritative name servers. The process of resolution may result in one of three types of responses: (1) a response containing the requested data, (2) a response indicating the requested data does not exist, or (3) a non-response due ... | In the DNS, resolvers employ caching to reduce both latency for end users and load on authoritative name servers. The process of resolution may result in one of three types of responses: (1) a response containing the requested data, (2) a response indicating the requested data does not exist, or (3) a non-response due ... | monolingualtext | ||||
STD:IETF:RFC9520$edaa07aa4cd4 | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9520$efac8fa8d52c | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Negative Caching of DNS Resolution Failures | Negative Caching of DNS Resolution Failures | monolingualtext | ||||
STD:IETF:RFC9520$fdadabc4d03d | IETF | STD:IETF:RFC9520 | Negative Caching of DNS Resolution Failures | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9520 | https://www.rfc-editor.org/rfc/rfc9520 | url | ||||
STD:IETF:RFC9521$07087d2c5b51 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9521$2b2f7829347b | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Aldrin | S. Aldrin | string | ||||
STD:IETF:RFC9521$3463513edadd | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Pallagatti | S. Pallagatti | string | ||||
STD:IETF:RFC9521$561ef2ccb035 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9521$69681ca7c451 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Mirsky | G. Mirsky | string | ||||
STD:IETF:RFC9521$6bef2b337472 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9521 | https://www.rfc-editor.org/rfc/rfc9521 | url | ||||
STD:IETF:RFC9521$6ea6a689a0b5 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9521$6ea6a689a0b5 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9521$7ca995f505da | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9521$963ae59bbfda | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9521$9cdffe39e145 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | monolingualtext | ||||
STD:IETF:RFC9521$b7e7cfcbe6c9 | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | X. Min | X. Min | string | ||||
STD:IETF:RFC9521$cf466e96623c | IETF | STD:IETF:RFC9521 | Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in point-to-point Generic Network Virtualization Encapsulation (Geneve) unicast tunnels used to make up an overlay network. | This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in point-to-point Generic Network Virtualization Encapsulation (Geneve) unicast tunnels used to make up an overlay network. | monolingualtext | ||||
STD:IETF:RFC9522$231db8fed8a3 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9522$33738278b56a | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks and the networks that support IP networking and to provide a common basis for the development of traffic-engineering c... | This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks and the networks that support IP networking and to provide a common basis for the development of traffic-engineering c... | monolingualtext | ||||
STD:IETF:RFC9522$755ad0091c94 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Farrel | A. Farrel | string | ||||
STD:IETF:RFC9522$7d6f3272deed | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9522$8a04d645ad2c | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9522$8a04d645ad2c | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9522$9e803e042e38 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC3272 | RFC3272 | wikibase-item | ||||
STD:IETF:RFC9522$c58ffda031b6 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9522$e7b83395bbb9 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Overview and Principles of Internet Traffic Engineering | Overview and Principles of Internet Traffic Engineering | monolingualtext | ||||
STD:IETF:RFC9522$f4b6db7fb583 | IETF | STD:IETF:RFC9522 | Overview and Principles of Internet Traffic Engineering | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9522 | https://www.rfc-editor.org/rfc/rfc9522 | url | ||||
STD:IETF:RFC9523$0fe8b1882618 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | monolingualtext | ||||
STD:IETF:RFC9523$27b77d96843f | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9523$3847d2788deb | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Mizrahi | T. Mizrahi | string | ||||
STD:IETF:RFC9523$445e15725144 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9523$445e15725144 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9523$51a4a5fa5326 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Schapira | M. Schapira | string | ||||
STD:IETF:RFC9523$7f3a5019c3ee | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | D. Dolev | D. Dolev | string | ||||
STD:IETF:RFC9523$88bea3c94dec | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. Rozen-Schiff | N. Rozen-Schiff | string | ||||
STD:IETF:RFC9523$bac933dce8ba | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Network Time Protocol version 4 (NTPv4), as defined in RFC 5905, is the mechanism used by NTP clients to synchronize with NTP servers across the Internet. This document describes a companion application to the NTPv4 client, named "Khronos", that is used as a "watchdog" alongside NTPv4 and that provides improved se... | The Network Time Protocol version 4 (NTPv4), as defined in RFC 5905, is the mechanism used by NTP clients to synchronize with NTP servers across the Internet. This document describes a companion application to the NTPv4 client, named "Khronos", that is used as a "watchdog" alongside NTPv4 and that provides improved se... | monolingualtext | ||||
STD:IETF:RFC9523$d22aba737165 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9523 | https://www.rfc-editor.org/rfc/rfc9523 | url | ||||
STD:IETF:RFC9523$d86e65fd2f29 | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9523$ec8e71d21e8c | IETF | STD:IETF:RFC9523 | A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9524$1712876871b8 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9524$248e5d22cb1e | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | H. Bidgoli | H. Bidgoli | string | ||||
STD:IETF:RFC9524$2d5408bd2a3e | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9524$2d5408bd2a3e | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9524$44d6866a8642 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the Segment Routing Replication segment for multipoint service delivery. A Replication segment allows a packet to be replicated from a replication node to downstream nodes. | This document describes the Segment Routing Replication segment for multipoint service delivery. A Replication segment allows a packet to be replicated from a replication node to downstream nodes. | monolingualtext | ||||
STD:IETF:RFC9524$4b2b7ff90e7b | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9524$72fdc9493157 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9524$957fae7738d8 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Segment Routing Replication for Multipoint Service Delivery | Segment Routing Replication for Multipoint Service Delivery | monolingualtext | ||||
STD:IETF:RFC9524$a2e742c2698e | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Parekh | R. Parekh | string | ||||
STD:IETF:RFC9524$b4ed3bb186d7 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Voyer | D. Voyer | string | ||||
STD:IETF:RFC9524$d5bd85331627 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9524$e25ab8f11fc7 | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9524$fea52fafe99f | IETF | STD:IETF:RFC9524 | Segment Routing Replication for Multipoint Service Delivery | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9524 | https://www.rfc-editor.org/rfc/rfc9524 | url | ||||
STD:IETF:RFC9525$014fef9fe2d2 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Service Identity in TLS | Service Identity in TLS | monolingualtext | ||||
STD:IETF:RFC9525$0d3325ddab60 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2023-01 | 2023-01 | time | ||||
STD:IETF:RFC9525$260473bda962 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9525 | https://www.rfc-editor.org/rfc/rfc9525 | url | ||||
STD:IETF:RFC9525$31670623b1e0 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Many application technologies enable secure communication between two entities by means of Transport Layer Security (TLS) with Internet Public Key Infrastructure using X.509 (PKIX) certificates. This document specifies procedures for representing and verifying the identity of application services in such interactions. ... | Many application technologies enable secure communication between two entities by means of Transport Layer Security (TLS) with Internet Public Key Infrastructure using X.509 (PKIX) certificates. This document specifies procedures for representing and verifying the identity of application services in such interactions. ... | monolingualtext | ||||
STD:IETF:RFC9525$4c7dff061467 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9525$6a418a24877f | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P155 | follows | STD:IETF:RFC6125 | RFC6125 | wikibase-item | ||||
STD:IETF:RFC9525$7dd39a304d56 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Saint-Andre | P. Saint-Andre | string | ||||
STD:IETF:RFC9525$ae8333889b16 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9525$b5a90f759553 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Salz | R. Salz | string | ||||
STD:IETF:RFC9525$cf1cc38397a0 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9525$cf1cc38397a0 | IETF | STD:IETF:RFC9525 | Service Identity in TLS | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9526$0db542d28577 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | D. Migault | D. Migault | string | ||||
STD:IETF:RFC9526$20446bbb7be7 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | R. Hunter | R. Hunter | string | ||||
STD:IETF:RFC9526$29fd52d6e278 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9526$29fd52d6e278 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9526$66f089d37f09 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9526 | https://www.rfc-editor.org/rfc/rfc9526 | url | ||||
STD:IETF:RFC9526$698526177cec | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9526$b2d196e4a4c6 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | R. Weber | R. Weber | string | ||||
STD:IETF:RFC9526$b8a78924dde3 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Home network owners may have devices or services hosted on their home network that they wish to access from the Internet (i.e., from a network outside of the home network). Home networks are increasingly numbered using IPv6 addresses, which in principle makes this access simpler, but accessing home networks from the In... | Home network owners may have devices or services hosted on their home network that they wish to access from the Internet (i.e., from a network outside of the home network). Home networks are increasingly numbered using IPv6 addresses, which in principle makes this access simpler, but accessing home networks from the In... | monolingualtext | ||||
STD:IETF:RFC9526$beaee6de69fb | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Simple Provisioning of Public Names for Residential Networks | Simple Provisioning of Public Names for Residential Networks | monolingualtext | ||||
STD:IETF:RFC9526$c8a053cfa3ee | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | M. Richardson | M. Richardson | string | ||||
STD:IETF:RFC9526$eac68c1d1741 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9526$ebd5bd961c62 | IETF | STD:IETF:RFC9526 | Simple Provisioning of Public Names for Residential Networks | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9527$1012accbf70f | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Migault | D. Migault | string | ||||
STD:IETF:RFC9527$1a0c7ea31969 | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9527 | https://www.rfc-editor.org/rfc/rfc9527 | url | ||||
STD:IETF:RFC9527$306924a62b37 | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Weber | R. Weber | string | ||||
STD:IETF:RFC9527$320bac0cdf4b | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9527$320bac0cdf4b | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9527$48f8f503f624 | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9527$814f715accda | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines DHCPv6 options so that a Homenet Naming Authority (HNA) can automatically set the appropriate configuration and outsource the authoritative naming service for the home network. In most cases, the outsourcing mechanism is transparent for the end user. | This document defines DHCPv6 options so that a Homenet Naming Authority (HNA) can automatically set the appropriate configuration and outsource the authoritative naming service for the home network. In most cases, the outsourcing mechanism is transparent for the end user. | monolingualtext | ||||
STD:IETF:RFC9527$88efe2984706 | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | DHCPv6 Options for the Homenet Naming Authority | DHCPv6 Options for the Homenet Naming Authority | monolingualtext | ||||
STD:IETF:RFC9527$a6c408e3619e | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9527$bc05c11f7dca | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9527$c08c7cbc2e6f | IETF | STD:IETF:RFC9527 | DHCPv6 Options for the Homenet Naming Authority | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Mrugalski | T. Mrugalski | string | ||||
STD:IETF:RFC9528$0864055168c1 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9528$1be8733a8c56 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9528 | https://www.rfc-editor.org/rfc/rfc9528 | url | ||||
STD:IETF:RFC9528$5b4b969ea6b0 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | F. Palombini | F. Palombini | string | ||||
STD:IETF:RFC9528$7b995681acfa | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Preuß Mattsson | J. Preuß Mattsson | string | ||||
STD:IETF:RFC9528$9cb454af862c | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9528$9cb454af862c | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9528$c31db97a711a | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9528$c776493f78f3 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a very compact and lightweight authenticated Diffie-Hellman key exchange with ephemeral keys. EDHOC provides mutual authentication, forward secrecy, and identity protection. EDHOC is intended for usage in constrained scenarios, and a main use case is... | This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a very compact and lightweight authenticated Diffie-Hellman key exchange with ephemeral keys. EDHOC provides mutual authentication, forward secrecy, and identity protection. EDHOC is intended for usage in constrained scenarios, and a main use case is... | monolingualtext | ||||
STD:IETF:RFC9528$c84fb61812e7 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9528$e0d02b0546e4 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Selander | G. Selander | string | ||||
STD:IETF:RFC9528$fd55b1563bf0 | IETF | STD:IETF:RFC9528 | Ephemeral Diffie-Hellman Over COSE (EDHOC) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Ephemeral Diffie-Hellman Over COSE (EDHOC) | Ephemeral Diffie-Hellman Over COSE (EDHOC) | monolingualtext | ||||
STD:IETF:RFC9529$0470cab0c48d | IETF | STD:IETF:RFC9529 | Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC) | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document contains example traces of Ephemeral Diffie-Hellman Over COSE (EDHOC). | This document contains example traces of Ephemeral Diffie-Hellman Over COSE (EDHOC). | monolingualtext | ||||
STD:IETF:RFC9529$04a84b748455 | IETF | STD:IETF:RFC9529 | Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9529$04a84b748455 | IETF | STD:IETF:RFC9529 | Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC) | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.