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:RFC9617$e0b7f7508795 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Zhou | T. Zhou | string | ||||
STD:IETF:RFC9617$eb154e1ef4b3 | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Guichard | J. Guichard | string | ||||
STD:IETF:RFC9617$f45ac1ad2bfc | IETF | STD:IETF:RFC9617 | A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9618$125da74b4264 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9618$27a2f5968693 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9618$5c2894410bf5 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9618 | https://www.rfc-editor.org/rfc/rfc9618 | url | ||||
STD:IETF:RFC9618$6692ed10aa55 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFC 5280 to replace the algorithm for X.509 policy validation with an equivalent, more efficient algorithm. The original algorithm built a structure that scaled exponentially in the worst case, leaving implementations vulnerable to denial-of-service attacks. | This document updates RFC 5280 to replace the algorithm for X.509 policy validation with an equivalent, more efficient algorithm. The original algorithm built a structure that scaled exponentially in the worst case, leaving implementations vulnerable to denial-of-service attacks. | monolingualtext | ||||
STD:IETF:RFC9618$6cd6c75113ae | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9618$df3fb73e078e | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Updates to X.509 Policy Validation | Updates to X.509 Policy Validation | monolingualtext | ||||
STD:IETF:RFC9618$ef5d81ee7952 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9618$ef5d81ee7952 | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9618$fb2c735b72eb | IETF | STD:IETF:RFC9618 | Updates to X.509 Policy Validation | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Benjamin | D. Benjamin | string | ||||
STD:IETF:RFC9619$12398a31f1a4 | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document updates RFC 1035 by constraining the allowed value of the QDCOUNT parameter in DNS messages with OPCODE = 0 (QUERY) to a maximum of one, and it specifies the required behavior when values that are not allowed are encountered. | This document updates RFC 1035 by constraining the allowed value of the QDCOUNT parameter in DNS messages with OPCODE = 0 (QUERY) to a maximum of one, and it specifies the required behavior when values that are not allowed are encountered. | monolingualtext | ||||
STD:IETF:RFC9619$3438a00dfe02 | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9619$3438a00dfe02 | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9619$500283ad608c | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Abley | J. Abley | string | ||||
STD:IETF:RFC9619$510ecd910430 | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9619$5a9d2671e848 | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Bellis | R. Bellis | string | ||||
STD:IETF:RFC9619$a6d6a991d6ca | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | In the DNS, QDCOUNT Is (Usually) One | In the DNS, QDCOUNT Is (Usually) One | monolingualtext | ||||
STD:IETF:RFC9619$bfc91979430e | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9619$d41e3014884a | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9619$ebf494087d0e | IETF | STD:IETF:RFC9619 | In the DNS, QDCOUNT Is (Usually) One | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9619 | https://www.rfc-editor.org/rfc/rfc9619 | url | ||||
STD:IETF:RFC9620$079a6705c05f | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | G. Grover | G. Grover | string | ||||
STD:IETF:RFC9620$373bac3c4b56 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9620$641e711cbc8e | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Guidelines for Human Rights Protocol and Architecture Considerations | Guidelines for Human Rights Protocol and Architecture Considerations | monolingualtext | ||||
STD:IETF:RFC9620$7da3c46a81a8 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document sets guidelines for human rights considerations for developers working on network protocols and architectures, similar to the work done on the guidelines for privacy considerations (RFC 6973). This is an updated version of the guidelines for human rights considerations in RFC 8280. This document is a pro... | This document sets guidelines for human rights considerations for developers working on network protocols and architectures, similar to the work done on the guidelines for privacy considerations (RFC 6973). This is an updated version of the guidelines for human rights considerations in RFC 8280. This document is a pro... | monolingualtext | ||||
STD:IETF:RFC9620$8c5c28d3e244 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9620$8c5c28d3e244 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9620$8e1dd090db1c | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9620 | https://www.rfc-editor.org/rfc/rfc9620 | url | ||||
STD:IETF:RFC9620$ada11803e4f8 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | N. ten Oever | N. ten Oever | string | ||||
STD:IETF:RFC9620$c22b31cea4e1 | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9620$f717e13ddb1f | IETF | STD:IETF:RFC9620 | Guidelines for Human Rights Protocol and Architecture Considerations | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9621$088778b07b30 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. S. Perkins | C. S. Perkins | string | ||||
STD:IETF:RFC9621$0a3b57d75db5 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an architecture that exposes transport protocol features to applications for network communication. The Transport Services Application Programming Interface (API) is based on an asynchronous, event-driven interaction pattern. This API uses Messages for representing data transfer to application... | This document describes an architecture that exposes transport protocol features to applications for network communication. The Transport Services Application Programming Interface (API) is based on an asynchronous, event-driven interaction pattern. This API uses Messages for representing data transfer to application... | monolingualtext | ||||
STD:IETF:RFC9621$0ae16005592b | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9621$0f549d2c7e48 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Brunstrom | A. Brunstrom | string | ||||
STD:IETF:RFC9621$0f7827c5225a | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9621$1e242904539c | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Architecture and Requirements for Transport Services | Architecture and Requirements for Transport Services | monolingualtext | ||||
STD:IETF:RFC9621$30bc13f708f1 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9621$7dd979624445 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9621$7dd979624445 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9621$b20a7d382560 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Fairhurst | G. Fairhurst | string | ||||
STD:IETF:RFC9621$b4aa865fc790 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Trammell | B. Trammell | string | ||||
STD:IETF:RFC9621$d6655b7c0a04 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9621 | https://www.rfc-editor.org/rfc/rfc9621 | url | ||||
STD:IETF:RFC9621$f469748256c7 | IETF | STD:IETF:RFC9621 | Architecture and Requirements for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9622$274578ca2d24 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P.S. Tiesel | P.S. Tiesel | string | ||||
STD:IETF:RFC9622$4fa10b9ee166 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document describes an abstract Application Programming Interface (API) to the transport layer that enables the selection of transport protocols and network paths dynamically at runtime. This API enables faster deployment of new protocols and protocol features without requiring changes to the applications. The sp... | This document describes an abstract Application Programming Interface (API) to the transport layer that enables the selection of transport protocols and network paths dynamically at runtime. This API enables faster deployment of new protocols and protocol features without requiring changes to the applications. The sp... | monolingualtext | ||||
STD:IETF:RFC9622$5397edfa65d6 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Kühlewind | M. Kühlewind | string | ||||
STD:IETF:RFC9622$5b35fb0582ff | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9622$6235efc358e2 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9622 | https://www.rfc-editor.org/rfc/rfc9622 | url | ||||
STD:IETF:RFC9622$6492322c55f0 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Trammell | B. Trammell | string | ||||
STD:IETF:RFC9622$6c6f27aa6b4f | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9622$6c6f27aa6b4f | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9622$778e92b30c67 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9622$a3a481dd72dd | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9622$b7c858dcb5d3 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | G. Fairhurst | G. Fairhurst | string | ||||
STD:IETF:RFC9622$b829940aec45 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | An Abstract Application Programming Interface (API) for Transport Services | An Abstract Application Programming Interface (API) for Transport Services | monolingualtext | ||||
STD:IETF:RFC9622$d4f82e46d776 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Welzl | M. Welzl | string | ||||
STD:IETF:RFC9622$d4fa73b77aac | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9622$da954bb82f00 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. S. Perkins | C. S. Perkins | string | ||||
STD:IETF:RFC9622$f0a7fd496518 | IETF | STD:IETF:RFC9622 | An Abstract Application Programming Interface (API) for Transport Services | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Enghardt | R. Enghardt | string | ||||
STD:IETF:RFC9623$016d35b1c5d0 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9623$0b894933e77a | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | A. Brunstrom | A. Brunstrom | string | ||||
STD:IETF:RFC9623$1a0aea646ee7 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9623 | https://www.rfc-editor.org/rfc/rfc9623 | url | ||||
STD:IETF:RFC9623$2122964706d7 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | The Transport Services System enables applications to use transport protocols flexibly for network communication and defines a protocol-independent Transport Services Application Programming Interface (API) that is based on an asynchronous, event-driven interaction pattern. This document serves as a guide to implement... | The Transport Services System enables applications to use transport protocols flexibly for network communication and defines a protocol-independent Transport Services Application Programming Interface (API) that is based on an asynchronous, event-driven interaction pattern. This document serves as a guide to implement... | monolingualtext | ||||
STD:IETF:RFC9623$435066fdcaad | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | P.S. Tiesel | P.S. Tiesel | string | ||||
STD:IETF:RFC9623$466572467097 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9623$5d78943550e4 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | T. Pauly | T. Pauly | string | ||||
STD:IETF:RFC9623$622af8c49c48 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9623$622af8c49c48 | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | INFORMATIONAL | INFORMATIONAL | string | ||||
STD:IETF:RFC9623$625d3d5e0d4f | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | M. Welzl | M. Welzl | string | ||||
STD:IETF:RFC9623$af9f7b3303ff | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9623$d350d8010dad | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P1476 | title | Implementing Interfaces to Transport Services | Implementing Interfaces to Transport Services | monolingualtext | ||||
STD:IETF:RFC9623$d63e1497fa6a | IETF | STD:IETF:RFC9623 | Implementing Interfaces to Transport Services | INFORMATIONAL | Q212971 | Request for Comments | P50 | author | R. Enghardt | R. Enghardt | string | ||||
STD:IETF:RFC9624$0529e000e084 | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9624$3e0ca73e589c | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9624$3e0ca73e589c | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9624$4288d0f0aa1f | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9624$5cde910ac78a | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9624$7c4be44a334a | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies protocols and procedures for forwarding Broadcast, Unknown Unicast, or Multicast (BUM) traffic of Ethernet VPNs (EVPNs) using Bit Index Explicit Replication (BIER). | This document specifies protocols and procedures for forwarding Broadcast, Unknown Unicast, or Multicast (BUM) traffic of Ethernet VPNs (EVPNs) using Bit Index Explicit Replication (BIER). | monolingualtext | ||||
STD:IETF:RFC9624$8a26a1998064 | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Przygienda | T. Przygienda | string | ||||
STD:IETF:RFC9624$c1c0bd8b3cca | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | monolingualtext | ||||
STD:IETF:RFC9624$c7899e2933ad | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9624$cd5400dee8e1 | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9624$d26e6f972d74 | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9624 | https://www.rfc-editor.org/rfc/rfc9624 | url | ||||
STD:IETF:RFC9624$f456d4e51cb6 | IETF | STD:IETF:RFC9624 | EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9625$14b3e0a14076 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | Z. Zhang | Z. Zhang | string | ||||
STD:IETF:RFC9625$29032171efaa | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9625$29032171efaa | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9625$35e52d73fa2b | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Drake | J. Drake | string | ||||
STD:IETF:RFC9625$381495a49a45 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9625$692b4166ca66 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Rabadan | J. Rabadan | string | ||||
STD:IETF:RFC9625$730c85360bbd | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Ethernet VPN (EVPN) provides a service that allows a single Local Area Network (LAN), comprising a single IP subnet, to be divided into multiple segments. Each segment may be located at a different site, and the segments are interconnected by an IP or MPLS backbone. Intra-subnet traffic (either unicast or multicast) ... | Ethernet VPN (EVPN) provides a service that allows a single Local Area Network (LAN), comprising a single IP subnet, to be divided into multiple segments. Each segment may be located at a different site, and the segments are interconnected by an IP or MPLS backbone. Intra-subnet traffic (either unicast or multicast) ... | monolingualtext | ||||
STD:IETF:RFC9625$78fe736d0c07 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | W. Lin | W. Lin | string | ||||
STD:IETF:RFC9625$9f7f1ddc9ff6 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | E. Rosen | E. Rosen | string | ||||
STD:IETF:RFC9625$b48e75b5d14c | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | A. Sajassi | A. Sajassi | string | ||||
STD:IETF:RFC9625$c4adb23c9e55 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9625 | https://www.rfc-editor.org/rfc/rfc9625 | url | ||||
STD:IETF:RFC9625$ccf2ebee5e1d | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | monolingualtext | ||||
STD:IETF:RFC9625$d25eee8e0ed3 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2024-01 | 2024-01 | time | ||||
STD:IETF:RFC9625$fa40dee70e04 | IETF | STD:IETF:RFC9625 | EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.