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:RFC9599$8bc5ca23ae9c | IETF | STD:IETF:RFC9599 | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9599$8f553e639e46 | IETF | STD:IETF:RFC9599 | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P50 | author | J. Kaippallimalil | J. Kaippallimalil | string | ||||
STD:IETF:RFC9599$c1de85aa8fe9 | IETF | STD:IETF:RFC9599 | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9599$e192d9ca7abc | IETF | STD:IETF:RFC9599 | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9599$e192d9ca7abc | IETF | STD:IETF:RFC9599 | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | BEST CURRENT PRACTICE | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | BEST CURRENT PRACTICE | BEST CURRENT PRACTICE | string | ||||
STD:IETF:RFC9600$310144b9351e | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9600 | https://www.rfc-editor.org/rfc/rfc9600 | url | ||||
STD:IETF:RFC9600$5da67c81a95d | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Explicit Congestion Notification (ECN) allows a forwarding element to notify downstream devices, including the destination, of the onset of congestion without having to drop packets. This can improve network efficiency through better congestion control without packet drops. This document extends ECN to TRansparent In... | Explicit Congestion Notification (ECN) allows a forwarding element to notify downstream devices, including the destination, of the onset of congestion without having to drop packets. This can improve network efficiency through better congestion control without packet drops. This document extends ECN to TRansparent In... | monolingualtext | ||||
STD:IETF:RFC9600$6955a914863c | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Eastlake 3rd | D. Eastlake 3rd | string | ||||
STD:IETF:RFC9600$ad31bdd89694 | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9600$cab048781f34 | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9600$cab048781f34 | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9600$d718b5074f9d | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9600$e1bb946a8572 | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Briscoe | B. Briscoe | string | ||||
STD:IETF:RFC9600$e885bff18ddc | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | monolingualtext | ||||
STD:IETF:RFC9600$ec3451e2b24f | IETF | STD:IETF:RFC9600 | TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9601$0c08dbdd7971 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9601$1d1735c30053 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9601$4c217cde5801 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9601 | https://www.rfc-editor.org/rfc/rfc9601 | url | ||||
STD:IETF:RFC9601$5504727482a4 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Briscoe | B. Briscoe | string | ||||
STD:IETF:RFC9601$5d6fdc6ddd2b | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9601$5d6fdc6ddd2b | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9601$67ad59c4e236 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9601$aa56f520d35c | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of Explicit Congestion Notification (ECN) consistent for all forms of IP-in-IP tunnel. This specification updates RFC 6040 to clarify that its scope includes tunnels where two IP headers are separated by at least one shim heade... | RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of Explicit Congestion Notification (ECN) consistent for all forms of IP-in-IP tunnel. This specification updates RFC 6040 to clarify that its scope includes tunnels where two IP headers are separated by at least one shim heade... | monolingualtext | ||||
STD:IETF:RFC9601$d231fd6eb130 | IETF | STD:IETF:RFC9601 | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim | monolingualtext | ||||
STD:IETF:RFC9602$14eb71badc3e | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9602$25bec65bf9c0 | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9602 | https://www.rfc-editor.org/rfc/rfc9602 | url | ||||
STD:IETF:RFC9602$69a915ba57cc | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9602$69a915ba57cc | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9602$7cb014ae02d7 | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9602$8f37f83a696a | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data plane. Thus, Segment Identifiers (SIDs) used by SRv6 can resemble IPv6 addresses and behave like them while exhibiting slightly different behaviors in some situations. This document explores the characteristics of SRv6 SIDs and focuses on the relations... | Segment Routing over IPv6 (SRv6) uses IPv6 as the underlying data plane. Thus, Segment Identifiers (SIDs) used by SRv6 can resemble IPv6 addresses and behave like them while exhibiting slightly different behaviors in some situations. This document explores the characteristics of SRv6 SIDs and focuses on the relations... | monolingualtext | ||||
STD:IETF:RFC9602$b879c96e968d | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | S. Krishnan | S. Krishnan | string | ||||
STD:IETF:RFC9602$ebe874a71e5b | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9602$f7dd663da950 | IETF | STD:IETF:RFC9602 | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing Architecture | monolingualtext | ||||
STD:IETF:RFC9603$29617e6b9dba | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | monolingualtext | ||||
STD:IETF:RFC9603$419d4a243f10 | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9603 | https://www.rfc-editor.org/rfc/rfc9603 | url | ||||
STD:IETF:RFC9603$5062006f62dd | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Li | C. Li | string | ||||
STD:IETF:RFC9603$50b8c0bedaec | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Segment Routing (SR) can be used to steer packets through a network using the IPv6 or MPLS data plane, employing the source routing paradigm. An SR Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). Since SR can be ... | Segment Routing (SR) can be used to steer packets through a network using the IPv6 or MPLS data plane, employing the source routing paradigm. An SR Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). Since SR can be ... | monolingualtext | ||||
STD:IETF:RFC9603$50d6a1ba68ac | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9603$58047d3a84bc | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Zhu | Y. Zhu | string | ||||
STD:IETF:RFC9603$7bc9d4e8c9cf | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Koldychev | M. Koldychev | string | ||||
STD:IETF:RFC9603$a087837f539c | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9603$ad16d387d75e | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9603$ad16d387d75e | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9603$bd06ee3e92ee | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Kaladharan | P. Kaladharan | string | ||||
STD:IETF:RFC9603$d1c924249103 | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sivabalan | S. Sivabalan | string | ||||
STD:IETF:RFC9603$f927b84e0a1b | IETF | STD:IETF:RFC9603 | Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9604$0ec162e31d9f | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | In order to provide greater scalability, network confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (BSID), as described in RFC 8402. It is possible to associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE) Label Switched Path (LSP) or an SR TE path. The BS... | In order to provide greater scalability, network confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (BSID), as described in RFC 8402. It is possible to associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE) Label Switched Path (LSP) or an SR TE path. The BS... | monolingualtext | ||||
STD:IETF:RFC9604$363741d7372b | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9604$5648795f664c | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9604$6612d40cf6da | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Previdi | S. Previdi | string | ||||
STD:IETF:RFC9604$860996afe596 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Sivabalan | S. Sivabalan | string | ||||
STD:IETF:RFC9604$9526a9396759 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9604$9526a9396759 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9604$9782b5076f6d | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Carrying Binding Label/SID in PCE-Based Networks | Carrying Binding Label/SID in PCE-Based Networks | monolingualtext | ||||
STD:IETF:RFC9604$aa03192b6852 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Tantsura | J. Tantsura | string | ||||
STD:IETF:RFC9604$c3aa5d7beba9 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Li | C. Li | string | ||||
STD:IETF:RFC9604$ee425676684a | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9604 | https://www.rfc-editor.org/rfc/rfc9604 | url | ||||
STD:IETF:RFC9604$f4ff88715a81 | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9604$f6975f3b601f | IETF | STD:IETF:RFC9604 | Carrying Binding Label/SID in PCE-Based Networks | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9605$08302daf78b3 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9605$20fabc4b78dc | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. G. Murillo | S. G. Murillo | string | ||||
STD:IETF:RFC9605$21647c87057c | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | monolingualtext | ||||
STD:IETF:RFC9605$2aea9209063a | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9605$3cc3047d04b1 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the Secure Frame (SFrame) end-to-end encryption and authentication mechanism for media frames in a multiparty conference call, in which central media servers (Selective Forwarding Units or SFUs) can access the media metadata needed to make forwarding decisions without having access to the actual... | This document describes the Secure Frame (SFrame) end-to-end encryption and authentication mechanism for media frames in a multiparty conference call, in which central media servers (Selective Forwarding Units or SFUs) can access the media metadata needed to make forwarding decisions without having access to the actual... | monolingualtext | ||||
STD:IETF:RFC9605$45e1ccf2b8b5 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Omara | E. Omara | string | ||||
STD:IETF:RFC9605$51f175cb2682 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9605 | https://www.rfc-editor.org/rfc/rfc9605 | url | ||||
STD:IETF:RFC9605$7639fc6c3cc0 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Barnes | R. Barnes | string | ||||
STD:IETF:RFC9605$81d8ada2281a | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9605$81d8ada2281a | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9605$837ec5cd5438 | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Y. Fablet | Y. Fablet | string | ||||
STD:IETF:RFC9605$9110d28892db | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9605$c5b29430904a | IETF | STD:IETF:RFC9605 | Secure Frame (SFrame): Lightweight Authenticated Encryption for Real-Time Media | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Uberti | J. Uberti | string | ||||
STD:IETF:RFC9606$1d1acca41664 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9606$1dd5be73f315 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9606$45279e109ee7 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9606$58c30de90976 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | DNS Resolver Information | DNS Resolver Information | monolingualtext | ||||
STD:IETF:RFC9606$8f0ce5582122 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a method for DNS resolvers to publish information about themselves. DNS clients can use the resolver information to identify the capabilities of DNS resolvers. How DNS clients use such information is beyond the scope of this document. | This document specifies a method for DNS resolvers to publish information about themselves. DNS clients can use the resolver information to identify the capabilities of DNS resolvers. How DNS clients use such information is beyond the scope of this document. | monolingualtext | ||||
STD:IETF:RFC9606$b3399d938f2d | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9606$b3399d938f2d | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9606$b5006a5a40b1 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9606 | https://www.rfc-editor.org/rfc/rfc9606 | url | ||||
STD:IETF:RFC9606$bb1e705e0120 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Reddy.K | T. Reddy.K | string | ||||
STD:IETF:RFC9606$e5c79314ce29 | IETF | STD:IETF:RFC9606 | DNS Resolver Information | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9607$05c66b722493 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Faller | M. Faller | string | ||||
STD:IETF:RFC9607$1a199fa267e0 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9607$311cc901c48d | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9607 | https://www.rfc-editor.org/rfc/rfc9607 | url | ||||
STD:IETF:RFC9607$53b676e5af06 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9607$53b676e5af06 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9607$8f3199d7a71f | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Hanson | D. Hanson | string | ||||
STD:IETF:RFC9607$a5dbe0bc584c | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Maver | K. Maver | string | ||||
STD:IETF:RFC9607$c4005a9949bf | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9607$d53ec69a8af4 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | monolingualtext | ||||
STD:IETF:RFC9607$e17ea569f2fe | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9607$e3fea6ff6ea7 | IETF | STD:IETF:RFC9607 | RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes the RTP payload format of the Secure Communication Interoperability Protocol (SCIP). SCIP is an application-layer protocol that provides end-to-end session establishment, payload encryption, packetization and de-packetization of media, and reliable transport. This document provides a globally ... | This document describes the RTP payload format of the Secure Communication Interoperability Protocol (SCIP). SCIP is an application-layer protocol that provides end-to-end session establishment, payload encryption, packetization and de-packetization of media, and reliable transport. This document provides a globally ... | monolingualtext | ||||
STD:IETF:RFC9608$0538700940fc | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9608 | https://www.rfc-editor.org/rfc/rfc9608 | url | ||||
STD:IETF:RFC9608$179e2c711d59 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | X.509v3 public key certificates are profiled in RFC 5280. Short-lived certificates are seeing greater use in the Internet. The Certification Authority (CA) that issues these short-lived certificates do not publish revocation information because the certificate lifespan that is shorter than the time needed to detect, ... | X.509v3 public key certificates are profiled in RFC 5280. Short-lived certificates are seeing greater use in the Internet. The Certification Authority (CA) that issues these short-lived certificates do not publish revocation information because the certificate lifespan that is shorter than the time needed to detect, ... | monolingualtext | ||||
STD:IETF:RFC9608$321320b15eef | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Okubo | T. Okubo | string | ||||
STD:IETF:RFC9608$383ca509a4ba | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Mandel | J. Mandel | string | ||||
STD:IETF:RFC9608$39cdb9205093 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | No Revocation Available for X.509 Public Key Certificates | No Revocation Available for X.509 Public Key Certificates | monolingualtext | ||||
STD:IETF:RFC9608$67065e97f073 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9608$67065e97f073 | IETF | STD:IETF:RFC9608 | No Revocation Available for X.509 Public Key Certificates | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.