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:RFC9826$f029ee21e45d | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9826 | https://www.rfc-editor.org/rfc/rfc9826 | url | ||||
STD:IETF:RFC9826$f82b888be9af | IETF | STD:IETF:RFC9826 | A YANG Data Model for the Path Computation Element Communication Protocol (PCEP) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Hardwick | J. Hardwick | string | ||||
STD:IETF:RFC9827$0a05c32ba501 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | V. Smyslov | V. Smyslov | string | ||||
STD:IETF:RFC9827$11235094e347 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9827$11235094e347 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9827$197450f58d08 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document clarifies and extends the meaning of Transform Type 5 in Internet Key Exchange Protocol Version 2 (IKEv2). It updates RFC 7296 by renaming Transform Type 5 from "Extended Sequence Numbers (ESN)" to "Sequence Numbers (SN)". It also renames two currently defined values for this Transform Type: value 0 fro... | This document clarifies and extends the meaning of Transform Type 5 in Internet Key Exchange Protocol Version 2 (IKEv2). It updates RFC 7296 by renaming Transform Type 5 from "Extended Sequence Numbers (ESN)" to "Sequence Numbers (SN)". It also renames two currently defined values for this Transform Type: value 0 fro... | monolingualtext | ||||
STD:IETF:RFC9827$21f247f17c98 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | monolingualtext | ||||
STD:IETF:RFC9827$650a96ca05f6 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9827$8f80ddd96970 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9827$b4b56c967732 | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9827$d8ecbaeee49d | IETF | STD:IETF:RFC9827 | Renaming the Extended Sequence Numbers (ESN) Transform Type in the Internet Key Exchange Protocol Version 2 (IKEv2) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9827 | https://www.rfc-editor.org/rfc/rfc9827 | url | ||||
STD:IETF:RFC9828$4f19fd23a7ba | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P.-A. Lemieux | P.-A. Lemieux | string | ||||
STD:IETF:RFC9828$5f1f70a8bbcc | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9828 | https://www.rfc-editor.org/rfc/rfc9828 | url | ||||
STD:IETF:RFC9828$a054dc4cf0db | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9828$b44acb91120a | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9828$b92bdd243a97 | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | monolingualtext | ||||
STD:IETF:RFC9828$d31a2a846501 | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9828$d4e258b17fe7 | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9828$d4e258b17fe7 | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9828$d91b325bc17a | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Taubman | D. Taubman | string | ||||
STD:IETF:RFC9828$ee4a5a06d9fd | IETF | STD:IETF:RFC9828 | RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream Latency | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document defines the RTP payload format for the streaming of a video signal encoded as a sequence of JPEG 2000 codestreams. The format allows sub-codestream latency, such that the first RTP packet for a given image can be emitted before the entire image is available to or encoded by the sender. | This document defines the RTP payload format for the streaming of a video signal encoded as a sequence of JPEG 2000 codestreams. The format allows sub-codestream latency, such that the first RTP packet for a given image can be emitted before the entire image is available to or encoded by the sender. | monolingualtext | ||||
STD:IETF:RFC9829$164165e4180e | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9829$826fc401ac46 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9829$8e869e216b51 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9829$8e869e216b51 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9829$a0c31aadad57 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9829$be53407c364e | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | T. Buehler | T. Buehler | string | ||||
STD:IETF:RFC9829$c1b91c93f82c | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document revises how the Resource Public Key Infrastructure (RPKI) handles Certificate Revocation List (CRL) Number extensions. This document updates RFC 6487. | This document revises how the Resource Public Key Infrastructure (RPKI) handles Certificate Revocation List (CRL) Number extensions. This document updates RFC 6487. | monolingualtext | ||||
STD:IETF:RFC9829$c51648e69fa5 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | monolingualtext | ||||
STD:IETF:RFC9829$d6630611d9d4 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9829 | https://www.rfc-editor.org/rfc/rfc9829 | url | ||||
STD:IETF:RFC9829$e7c753cbc573 | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Maddison | B. Maddison | string | ||||
STD:IETF:RFC9829$fe8d56f2e5de | IETF | STD:IETF:RFC9829 | Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | J. Snijders | J. Snijders | string | ||||
STD:IETF:RFC9830$0311bbc71529 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9830$109fe4527830 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9830$109fe4527830 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9830$26b64c4ff293 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | Advertising Segment Routing Policies in BGP | Advertising Segment Routing Policies in BGP | monolingualtext | ||||
STD:IETF:RFC9830$453073afbfa5 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9830$995174920ec8 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | P. Mattes | P. Mattes | string | ||||
STD:IETF:RFC9830$a580eefffe86 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9830$c91ce4af1478 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Previdi | S. Previdi | string | ||||
STD:IETF:RFC9830$d77e24f47a4f | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | D. Jain | D. Jain | string | ||||
STD:IETF:RFC9830$d9361023b02a | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9830$da5b9d72a3dc | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9830 | https://www.rfc-editor.org/rfc/rfc9830 | url | ||||
STD:IETF:RFC9830$dc4c90438930 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | A Segment Routing (SR) Policy is an ordered list of segments (also referred to as "instructions") that define a source-routed policy. An SR Policy consists of one or more Candidate Paths (CPs), each comprising one or more segment lists. A headend can be provisioned with these CPs using various mechanisms such as Comman... | A Segment Routing (SR) Policy is an ordered list of segments (also referred to as "instructions") that define a source-routed policy. An SR Policy consists of one or more Candidate Paths (CPs), each comprising one or more segment lists. A headend can be provisioned with these CPs using various mechanisms such as Comman... | monolingualtext | ||||
STD:IETF:RFC9830$e1cf2ff737c5 | IETF | STD:IETF:RFC9830 | Advertising Segment Routing Policies in BGP | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9831$10114e7227be | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9831$10114e7227be | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9831$1893dcdb5f47 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9831 | https://www.rfc-editor.org/rfc/rfc9831 | url | ||||
STD:IETF:RFC9831$4977751fc12f | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9831$5b4b7f66c3ac | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9831$7fd30a551429 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | P. Mattes | P. Mattes | string | ||||
STD:IETF:RFC9831$80d988c642a9 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | C. Filsfils | C. Filsfils | string | ||||
STD:IETF:RFC9831$815247519600 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies the signaling of additional Segment Routing (SR) Segment Types for SR Policies in BGP using the SR Policy Subsequent Address Family Identifier (SAFI). | This document specifies the signaling of additional Segment Routing (SR) Segment Types for SR Policies in BGP using the SR Policy Subsequent Address Family Identifier (SAFI). | monolingualtext | ||||
STD:IETF:RFC9831$8f4b424a7743 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | K. Talaulikar | K. Talaulikar | string | ||||
STD:IETF:RFC9831$ab9547caa35b | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | Segment Type Extensions for BGP Segment Routing (SR) Policy | Segment Type Extensions for BGP Segment Routing (SR) Policy | monolingualtext | ||||
STD:IETF:RFC9831$b2c16afb3d11 | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9831$e3e5d4e28cae | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | D. Jain | D. Jain | string | ||||
STD:IETF:RFC9831$fd245024126c | IETF | STD:IETF:RFC9831 | Segment Type Extensions for BGP Segment Routing (SR) Policy | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | S. Previdi | S. Previdi | string | ||||
STD:IETF:RFC9832$0395b77c77be | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9832$3632aa8baf08 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P1683 | quotation (abstract) | This document specifies a mechanism referred to as "Intent-Driven Service Mapping". The mechanism uses BGP to express Intent-based association of overlay routes with underlay routes having specific Traffic Engineering (TE) characteristics satisfying a certain Service Level Agreement (SLA). This is achieved by defining ... | This document specifies a mechanism referred to as "Intent-Driven Service Mapping". The mechanism uses BGP to express Intent-based association of overlay routes with underlay routes having specific Traffic Engineering (TE) characteristics satisfying a certain Service Level Agreement (SLA). This is achieved by defining ... | monolingualtext | ||||
STD:IETF:RFC9832$5265c3267bbe | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9832$650cfc098f24 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9832$650cfc098f24 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | EXPERIMENTAL | EXPERIMENTAL | string | ||||
STD:IETF:RFC9832$838a319d3cb0 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P1476 | title | BGP Classful Transport Planes | BGP Classful Transport Planes | monolingualtext | ||||
STD:IETF:RFC9832$d0abc43a0222 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | K. Vairavakkalai | K. Vairavakkalai | string | ||||
STD:IETF:RFC9832$da8d8cba5db4 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9832 | https://www.rfc-editor.org/rfc/rfc9832 | url | ||||
STD:IETF:RFC9832$dd8ba2f03cf2 | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P50 | author | N. Venkataraman | N. Venkataraman | string | ||||
STD:IETF:RFC9832$f6bed029883c | IETF | STD:IETF:RFC9832 | BGP Classful Transport Planes | EXPERIMENTAL | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9833$234055a2c502 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9833$2465441f47a0 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9833$30e77cdad0b2 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9833$30e77cdad0b2 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9833$38f24e9277b7 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Roberts | R. Roberts | string | ||||
STD:IETF:RFC9833$3ea1e07a492d | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Wu | B. Wu | string | ||||
STD:IETF:RFC9833$4647f10ed2c2 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A Common YANG Data Model for Attachment Circuits | A Common YANG Data Model for Attachment Circuits | monolingualtext | ||||
STD:IETF:RFC9833$72a82a0e5198 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Barguil | S. Barguil | string | ||||
STD:IETF:RFC9833$80931a6234dd | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9833$89f48ad1fa9e | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9833$99ebe4e29dce | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | The document specifies a common attachment circuits (ACs) YANG data
model, which is designed to be reusable by other models. This design
is meant to ensure consistent AC structures among models that
manipulate ACs. For example, this common model can be reused by
service models to expose ACs as a service, service mode... | The document specifies a common attachment circuits (ACs) YANG data
model, which is designed to be reusable by other models. This design
is meant to ensure consistent AC structures among models that
manipulate ACs. For example, this common model can be reused by
service models to expose ACs as a service, service mode... | monolingualtext | ||||
STD:IETF:RFC9833$da82a763a8c2 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9833 | https://www.rfc-editor.org/rfc/rfc9833 | url | ||||
STD:IETF:RFC9833$deecc8848a07 | IETF | STD:IETF:RFC9833 | A Common YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | O. Gonzalez de Dios | O. Gonzalez de Dios | string | ||||
STD:IETF:RFC9834$0ae589efeaf1 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | M. Boucadair | M. Boucadair | string | ||||
STD:IETF:RFC9834$2237aeda5202 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9834$2237aeda5202 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9834$3c048f67b150 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | B. Wu | B. Wu | string | ||||
STD:IETF:RFC9834$55eb985af511 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P577 | publication date | 2025-01 | 2025-01 | time | ||||
STD:IETF:RFC9834$5d1d19467cca | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Roberts | R. Roberts | string | ||||
STD:IETF:RFC9834$8352ba394d4d | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | O. Gonzalez de Dios | O. Gonzalez de Dios | string | ||||
STD:IETF:RFC9834$a95708fa0c3b | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P407 | language of work or name | en | English | wikibase-item | ||||
STD:IETF:RFC9834$b13c7253c78a | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P953 | full work available at URL | https://www.rfc-editor.org/rfc/rfc9834 | https://www.rfc-editor.org/rfc/rfc9834 | url | ||||
STD:IETF:RFC9834$c5b33044a0b8 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9834$c76b7414264d | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1683 | quotation (abstract) | Delivery of network services assumes that appropriate setup is
provisioned over the links that connect customer termination points
and a provider network. The required setup to allow successful data
exchange over these links is referred to as an attachment circuit
(AC), while the underlying link is referred to as a "be... | Delivery of network services assumes that appropriate setup is
provisioned over the links that connect customer termination points
and a provider network. The required setup to allow successful data
exchange over these links is referred to as an attachment circuit
(AC), while the underlying link is referred to as a "be... | monolingualtext | ||||
STD:IETF:RFC9834$e8c0937f3362 | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | S. Barguil | S. Barguil | string | ||||
STD:IETF:RFC9834$e955bc03f41f | IETF | STD:IETF:RFC9834 | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS) | monolingualtext | ||||
STD:IETF:RFC9835$0ad735b0b950 | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P31 | instance of | Q212971 | Request for Comments | wikibase-item | ||||
STD:IETF:RFC9835$1e2fc33c047d | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9835$1e2fc33c047d | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P5008 | on focus list of Wikimedia project (status) | PROPOSED STANDARD | PROPOSED STANDARD | string | ||||
STD:IETF:RFC9835$7d158e9f4870 | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P1476 | title | A Network YANG Data Model for Attachment Circuits | A Network YANG Data Model for Attachment Circuits | monolingualtext | ||||
STD:IETF:RFC9835$90596481ef78 | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | O. Gonzalez de Dios | O. Gonzalez de Dios | string | ||||
STD:IETF:RFC9835$919fa128f0bd | IETF | STD:IETF:RFC9835 | A Network YANG Data Model for Attachment Circuits | PROPOSED STANDARD | Q212971 | Request for Comments | P50 | author | R. Roberts | R. Roberts | string |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.