RFC 8343: A YANG Data Model for Interface Management

This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic…

Read RFC 8343 on the RFC Editor

Outgoing relationships (6 related RFCs)

Obsoletes — RFC 7223: A YANG Data Model for Interface Management
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 7950: The YANG 1.1 Data Modeling Language
Normative reference — RFC 8040: RESTCONF Protocol
Informative reference — RFC 7224: IANA Interface Type YANG Module

Incoming relationships (32 related RFCs)

Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
Normatively referenced by — RFC 8960: A YANG Data Model for MPLS Base
Normatively referenced by — RFC 8695: A YANG Data Model for the Routing Information Protocol (RIP)
Normatively referenced by — RFC 9129: YANG Data Model for the OSPF Protocol
Normatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9633: Deterministic Networking (DetNet) YANG Data Model
Normatively referenced by — RFC 8531: Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) Protocols
Normatively referenced by — RFC 9020: YANG Data Model for Segment Routing
Normatively referenced by — RFC 9067: A YANG Data Model for Routing Policy
Normatively referenced by — RFC 9127: YANG Data Model for Bidirectional Forwarding Detection (BFD)
Normatively referenced by — RFC 9105: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)
Normatively referenced by — RFC 9128: YANG Data Model for Protocol Independent Multicast (PIM)
Normatively referenced by — RFC 8916: A YANG Data Model for the Multicast Source Discovery Protocol (MSDP)
Normatively referenced by — RFC 9166: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping
Normatively referenced by — RFC 9243: A YANG Data Model for DHCPv6 Configuration
Normatively referenced by — RFC 9249: A YANG Data Model for NTP
Normatively referenced by — RFC 9296: ifStackTable for the Point-to-Point (P2P) Interface over a LAN Type: Definition and Examples
Normatively referenced by — RFC 9398: A YANG Data Model for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Proxy Devices
Normatively referenced by — RFC 9403: A YANG Data Model for RIB Extensions
Normatively referenced by — RFC 9617: A YANG Data Model for In Situ Operations, Administration, and Maintenance (IOAM)
Normatively referenced by — RFC 9647: A YANG Data Model for Babel
Normatively referenced by — RFC 9719: YANG Data Model for Routing in Fat Trees (RIFT)
Normatively referenced by — RFC 9742: A YANG Data Model for Syslog Management
Normatively referenced by — RFC 9950: A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)
Informatively referenced by — RFC 8969: A Framework for Automating Service and Network Management with YANG
Informatively referenced by — RFC 9291: A YANG Network Data Model for Layer 2 VPNs
Informatively referenced by — RFC 9099: Operational Security Considerations for IPv6 Networks
Informatively referenced by — RFC 9254: Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)
Informatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Informatively referenced by — RFC 9595: YANG Schema Item iDentifier (YANG SID)