Delete models. Models can be extracted from ygot code.

api/models/iana-if-type.yang

-module iana-if-type {
-  namespace "urn:ietf:params:xml:ns:yang:iana-if-type";
-  prefix ianaift;
-
-  import ietf-interfaces {
-    prefix if;
-  }
-
-  organization "IANA";
-  contact
-    "        Internet Assigned Numbers Authority
-
-     Postal: ICANN
-             12025 Waterfront Drive, Suite 300
-             Los Angeles, CA 90094-2536
-             United States
-
-     Tel:    +1 310 301 5800
-     <mailto:iana&iana.org>";
-  description
-    "This YANG module defines YANG identities for IANA-registered
-     interface types.
-
-     This YANG module is maintained by IANA and reflects the
-     'ifType definitions' registry.
-
-     The latest revision of this YANG module can be obtained from
-     the IANA web site.
-
-     Requests for new values should be made to IANA via
-     email (iana&iana.org).
-
-     Copyright (c) 2014 IETF Trust and the persons identified as
-     authors of the code.  All rights reserved.
-
-     Redistribution and use in source and binary forms, with or
-     without modification, is permitted pursuant to, and subject
-     to the license terms contained in, the Simplified BSD License
-     set forth in Section 4.c of the IETF Trust's Legal Provisions
-     Relating to IETF Documents
-     (http://trustee.ietf.org/license-info).
-
-     The initial version of this YANG module is part of RFC 7224;
-     see the RFC itself for full legal notices.";
-  reference
-    "IANA 'ifType definitions' registry.
-     <http://www.iana.org/assignments/smi-numbers>";
-
-  revision 2017-01-19 {
-    description
-      "Registered ifType 289.";
-  }
-
-  revision 2016-11-23 {
-    description
-      "Registered ifTypes 283-288.";
-  }
-
-  revision 2016-06-09 {
-    description
-      "Registered ifType 282.";
-  }
-  revision 2016-05-03 {
-    description
-      "Registered ifType 281.";
-  }
-  revision 2015-06-12 {
-    description
-      "Corrected formatting issue.";
-  }  
-  revision 2014-09-24 {
-    description
-      "Registered ifType 280.";
-  }
-  revision 2014-09-19 {
-    description
-      "Registered ifType 279.";
-  }
-  revision 2014-07-03 {
-    description
-      "Registered ifTypes 277-278.";
-  }
-  revision 2014-05-19 {
-    description
-      "Updated the contact address.";
-  }
-  revision 2014-05-08 {
-    description
-      "Initial revision.";
-    reference
-      "RFC 7224: IANA Interface Type YANG Module";
-  }
-
-  identity iana-interface-type {
-    base if:interface-type;
-    description
-      "This identity is used as a base for all interface types
-       defined in the 'ifType definitions' registry.";
-  }
-
-  identity other {
-    base iana-interface-type;
-  }
-  identity regular1822 {
-    base iana-interface-type;
-  }
-  identity hdh1822 {
-    base iana-interface-type;
-  }
-  identity ddnX25 {
-    base iana-interface-type;
-  }
-  identity rfc877x25 {
-    base iana-interface-type;
-    reference
-      "RFC 1382 - SNMP MIB Extension for the X.25 Packet Layer";
-  }
-  identity ethernetCsmacd {
-    base iana-interface-type;
-    description
-      "For all Ethernet-like interfaces, regardless of speed,
-       as per RFC 3635.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity iso88023Csmacd {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Deprecated via RFC 3635.
-       Use ethernetCsmacd(6) instead.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity iso88024TokenBus {
-    base iana-interface-type;
-  }
-  identity iso88025TokenRing {
-    base iana-interface-type;
-  }
-  identity iso88026Man {
-    base iana-interface-type;
-  }
-  identity starLan {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Deprecated via RFC 3635.
-       Use ethernetCsmacd(6) instead.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity proteon10Mbit {
-    base iana-interface-type;
-  }
-  identity proteon80Mbit {
-    base iana-interface-type;
-  }
-  identity hyperchannel {
-    base iana-interface-type;
-  }
-  identity fddi {
-    base iana-interface-type;
-    reference
-      "RFC 1512 - FDDI Management Information Base";
-  }
-  identity lapb {
-    base iana-interface-type;
-    reference
-      "RFC 1381 - SNMP MIB Extension for X.25 LAPB";
-  }
-  identity sdlc {
-    base iana-interface-type;
-  }
-  identity ds1 {
-    base iana-interface-type;
-    description
-      "DS1-MIB.";
-    reference
-      "RFC 4805 - Definitions of Managed Objects for the
-                  DS1, J1, E1, DS2, and E2 Interface Types";
-  }
-  identity e1 {
-    base iana-interface-type;
-    status obsolete;
-    description
-      "Obsolete; see DS1-MIB.";
-    reference
-      "RFC 4805 - Definitions of Managed Objects for the
-                  DS1, J1, E1, DS2, and E2 Interface Types";
-  }
-  identity basicISDN {
-    base iana-interface-type;
-    description
-      "No longer used.  See also RFC 2127.";
-  }
-  identity primaryISDN {
-    base iana-interface-type;
-    description
-      "No longer used.  See also RFC 2127.";
-  }
-  identity propPointToPointSerial {
-    base iana-interface-type;
-    description
-      "Proprietary serial.";
-  }
-  identity ppp {
-    base iana-interface-type;
-  }
-  identity softwareLoopback {
-    base iana-interface-type;
-  }
-  identity eon {
-    base iana-interface-type;
-    description
-      "CLNP over IP.";
-  }
-  identity ethernet3Mbit {
-    base iana-interface-type;
-  }
-  identity nsip {
-    base iana-interface-type;
-    description
-      "XNS over IP.";
-  }
-  identity slip {
-    base iana-interface-type;
-    description
-      "Generic SLIP.";
-  }
-  identity ultra {
-    base iana-interface-type;
-    description
-      "Ultra Technologies.";
-  }
-  identity ds3 {
-    base iana-interface-type;
-    description
-      "DS3-MIB.";
-    reference
-      "RFC 3896 - Definitions of Managed Objects for the
-                  DS3/E3 Interface Type";
-  }
-  identity sip {
-    base iana-interface-type;
-    description
-      "SMDS, coffee.";
-    reference
-      "RFC 1694 - Definitions of Managed Objects for SMDS
-                  Interfaces using SMIv2";
-  }
-  identity frameRelay {
-    base iana-interface-type;
-    description
-      "DTE only.";
-    reference
-      "RFC 2115 - Management Information Base for Frame Relay
-                  DTEs Using SMIv2";
-  }
-  identity rs232 {
-    base iana-interface-type;
-    reference
-      "RFC 1659 - Definitions of Managed Objects for RS-232-like
-                  Hardware Devices using SMIv2";
-  }
-  identity para {
-    base iana-interface-type;
-    description
-      "Parallel-port.";
-    reference
-      "RFC 1660 - Definitions of Managed Objects for
-                  Parallel-printer-like Hardware Devices using
-                  SMIv2";
-  }
-  identity arcnet {
-    base iana-interface-type;
-    description
-      "ARCnet.";
-  }
-  identity arcnetPlus {
-    base iana-interface-type;
-    description
-      "ARCnet Plus.";
-  }
-  identity atm {
-    base iana-interface-type;
-    description
-      "ATM cells.";
-  }
-  identity miox25 {
-    base iana-interface-type;
-    reference
-      "RFC 1461 - SNMP MIB extension for Multiprotocol
-                  Interconnect over X.25";
-  }
-  identity sonet {
-    base iana-interface-type;
-    description
-      "SONET or SDH.";
-  }
-  identity x25ple {
-    base iana-interface-type;
-    reference
-      "RFC 2127 - ISDN Management Information Base using SMIv2";
-  }
-  identity iso88022llc {
-    base iana-interface-type;
-  }
-  identity localTalk {
-    base iana-interface-type;
-  }
-  identity smdsDxi {
-    base iana-interface-type;
-  }
-  identity frameRelayService {
-    base iana-interface-type;
-    description
-      "FRNETSERV-MIB.";
-    reference
-      "RFC 2954 - Definitions of Managed Objects for Frame
-                  Relay Service";
-  }
-  identity v35 {
-    base iana-interface-type;
-  }
-  identity hssi {
-    base iana-interface-type;
-  }
-  identity hippi {
-    base iana-interface-type;
-  }
-  identity modem {
-    base iana-interface-type;
-    description
-      "Generic modem.";
-  }
-  identity aal5 {
-    base iana-interface-type;
-    description
-      "AAL5 over ATM.";
-  }
-  identity sonetPath {
-    base iana-interface-type;
-  }
-  identity sonetVT {
-    base iana-interface-type;
-  }
-  identity smdsIcip {
-    base iana-interface-type;
-    description
-      "SMDS InterCarrier Interface.";
-  }
-  identity propVirtual {
-    base iana-interface-type;
-    description
-      "Proprietary virtual/internal.";
-    reference
-      "RFC 2863 - The Interfaces Group MIB";
-  }
-  identity propMultiplexor {
-    base iana-interface-type;
-    description
-      "Proprietary multiplexing.";
-    reference
-      "RFC 2863 - The Interfaces Group MIB";
-  }
-  identity ieee80212 {
-    base iana-interface-type;
-    description
-      "100BaseVG.";
-  }
-  identity fibreChannel {
-    base iana-interface-type;
-    description
-      "Fibre Channel.";
-  }
-  identity hippiInterface {
-    base iana-interface-type;
-    description
-      "HIPPI interfaces.";
-  }
-  identity frameRelayInterconnect {
-    base iana-interface-type;
-    status obsolete;
-    description
-      "Obsolete; use either
-       frameRelay(32) or frameRelayService(44).";
-  }
-  identity aflane8023 {
-    base iana-interface-type;
-    description
-      "ATM Emulated LAN for 802.3.";
-  }
-  identity aflane8025 {
-    base iana-interface-type;
-    description
-      "ATM Emulated LAN for 802.5.";
-  }
-  identity cctEmul {
-    base iana-interface-type;
-    description
-      "ATM Emulated circuit.";
-  }
-  identity fastEther {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Obsoleted via RFC 3635.
-       ethernetCsmacd(6) should be used instead.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity isdn {
-    base iana-interface-type;
-    description
-      "ISDN and X.25.";
-    reference
-      "RFC 1356 - Multiprotocol Interconnect on X.25 and ISDN
-                  in the Packet Mode";
-  }
-  identity v11 {
-    base iana-interface-type;
-    description
-      "CCITT V.11/X.21.";
-  }
-  identity v36 {
-    base iana-interface-type;
-    description
-      "CCITT V.36.";
-  }
-  identity g703at64k {
-    base iana-interface-type;
-    description
-      "CCITT G703 at 64Kbps.";
-  }
-  identity g703at2mb {
-    base iana-interface-type;
-    status obsolete;
-    description
-      "Obsolete; see DS1-MIB.";
-  }
-  identity qllc {
-    base iana-interface-type;
-    description
-      "SNA QLLC.";
-  }
-  identity fastEtherFX {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Obsoleted via RFC 3635.
-       ethernetCsmacd(6) should be used instead.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity channel {
-    base iana-interface-type;
-    description
-      "Channel.";
-  }
-  identity ieee80211 {
-    base iana-interface-type;
-    description
-      "Radio spread spectrum.";
-  }
-  identity ibm370parChan {
-    base iana-interface-type;
-    description
-      "IBM System 360/370 OEMI Channel.";
-  }
-  identity escon {
-    base iana-interface-type;
-    description
-      "IBM Enterprise Systems Connection.";
-  }
-  identity dlsw {
-    base iana-interface-type;
-    description
-      "Data Link Switching.";
-  }
-  identity isdns {
-    base iana-interface-type;
-    description
-      "ISDN S/T interface.";
-  }
-  identity isdnu {
-    base iana-interface-type;
-    description
-      "ISDN U interface.";
-  }
-  identity lapd {
-    base iana-interface-type;
-    description
-      "Link Access Protocol D.";
-  }
-  identity ipSwitch {
-    base iana-interface-type;
-    description
-      "IP Switching Objects.";
-  }
-  identity rsrb {
-    base iana-interface-type;
-    description
-      "Remote Source Route Bridging.";
-  }
-  identity atmLogical {
-    base iana-interface-type;
-    description
-      "ATM Logical Port.";
-    reference
-      "RFC 3606 - Definitions of Supplemental Managed Objects
-                  for ATM Interface";
-  }
-  identity ds0 {
-    base iana-interface-type;
-    description
-      "Digital Signal Level 0.";
-    reference
-      "RFC 2494 - Definitions of Managed Objects for the DS0
-                  and DS0 Bundle Interface Type";
-  }
-  identity ds0Bundle {
-    base iana-interface-type;
-    description
-      "Group of ds0s on the same ds1.";
-    reference
-      "RFC 2494 - Definitions of Managed Objects for the DS0
-                  and DS0 Bundle Interface Type";
-  }
-  identity bsc {
-    base iana-interface-type;
-    description
-      "Bisynchronous Protocol.";
-  }
-  identity async {
-    base iana-interface-type;
-    description
-      "Asynchronous Protocol.";
-  }
-  identity cnr {
-    base iana-interface-type;
-    description
-      "Combat Net Radio.";
-  }
-  identity iso88025Dtr {
-    base iana-interface-type;
-    description
-      "ISO 802.5r DTR.";
-  }
-  identity eplrs {
-    base iana-interface-type;
-    description
-      "Ext Pos Loc Report Sys.";
-  }
-  identity arap {
-    base iana-interface-type;
-    description
-      "Appletalk Remote Access Protocol.";
-  }
-  identity propCnls {
-    base iana-interface-type;
-    description
-      "Proprietary Connectionless Protocol.";
-  }
-  identity hostPad {
-    base iana-interface-type;
-    description
-      "CCITT-ITU X.29 PAD Protocol.";
-  }
-  identity termPad {
-    base iana-interface-type;
-    description
-      "CCITT-ITU X.3 PAD Facility.";
-  }
-  identity frameRelayMPI {
-    base iana-interface-type;
-    description
-      "Multiproto Interconnect over FR.";
-  }
-  identity x213 {
-    base iana-interface-type;
-    description
-      "CCITT-ITU X213.";
-  }
-  identity adsl {
-    base iana-interface-type;
-    description
-      "Asymmetric Digital Subscriber Loop.";
-  }
-  identity radsl {
-    base iana-interface-type;
-    description
-      "Rate-Adapt. Digital Subscriber Loop.";
-  }
-  identity sdsl {
-    base iana-interface-type;
-    description
-      "Symmetric Digital Subscriber Loop.";
-  }
-  identity vdsl {
-    base iana-interface-type;
-    description
-      "Very H-Speed Digital Subscrib. Loop.";
-  }
-  identity iso88025CRFPInt {
-    base iana-interface-type;
-    description
-      "ISO 802.5 CRFP.";
-  }
-  identity myrinet {
-    base iana-interface-type;
-    description
-      "Myricom Myrinet.";
-  }
-  identity voiceEM {
-    base iana-interface-type;
-    description
-      "Voice recEive and transMit.";
-  }
-  identity voiceFXO {
-    base iana-interface-type;
-    description
-      "Voice Foreign Exchange Office.";
-  }
-  identity voiceFXS {
-    base iana-interface-type;
-    description
-      "Voice Foreign Exchange Station.";
-  }
-  identity voiceEncap {
-    base iana-interface-type;
-    description
-      "Voice encapsulation.";
-  }
-  identity voiceOverIp {
-    base iana-interface-type;
-    description
-      "Voice over IP encapsulation.";
-  }
-  identity atmDxi {
-    base iana-interface-type;
-    description
-      "ATM DXI.";
-  }
-  identity atmFuni {
-    base iana-interface-type;
-    description
-      "ATM FUNI.";
-  }
-  identity atmIma {
-    base iana-interface-type;
-    description
-      "ATM IMA.";
-  }
-  identity pppMultilinkBundle {
-    base iana-interface-type;
-    description
-      "PPP Multilink Bundle.";
-  }
-  identity ipOverCdlc {
-    base iana-interface-type;
-    description
-      "IBM ipOverCdlc.";
-  }
-  identity ipOverClaw {
-    base iana-interface-type;
-    description
-      "IBM Common Link Access to Workstn.";
-  }
-  identity stackToStack {
-    base iana-interface-type;
-    description
-      "IBM stackToStack.";
-  }
-  identity virtualIpAddress {
-    base iana-interface-type;
-    description
-      "IBM VIPA.";
-  }
-  identity mpc {
-    base iana-interface-type;
-    description
-      "IBM multi-protocol channel support.";
-  }
-  identity ipOverAtm {
-    base iana-interface-type;
-    description
-      "IBM ipOverAtm.";
-    reference
-      "RFC 2320 - Definitions of Managed Objects for Classical IP
-                  and ARP Over ATM Using SMIv2 (IPOA-MIB)";
-  }
-  identity iso88025Fiber {
-    base iana-interface-type;
-    description
-      "ISO 802.5j Fiber Token Ring.";
-  }
-  identity tdlc {
-    base iana-interface-type;
-    description
-      "IBM twinaxial data link control.";
-  }
-  identity gigabitEthernet {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Obsoleted via RFC 3635.
-       ethernetCsmacd(6) should be used instead.";
-    reference
-      "RFC 3635 - Definitions of Managed Objects for the
-                  Ethernet-like Interface Types";
-  }
-  identity hdlc {
-    base iana-interface-type;
-    description
-      "HDLC.";
-  }
-  identity lapf {
-    base iana-interface-type;
-    description
-      "LAP F.";
-  }
-  identity v37 {
-    base iana-interface-type;
-    description
-      "V.37.";
-  }
-  identity x25mlp {
-    base iana-interface-type;
-    description
-      "Multi-Link Protocol.";
-  }
-  identity x25huntGroup {
-    base iana-interface-type;
-    description
-      "X25 Hunt Group.";
-  }
-  identity transpHdlc {
-    base iana-interface-type;
-    description
-      "Transp HDLC.";
-  }
-  identity interleave {
-    base iana-interface-type;
-    description
-      "Interleave channel.";
-  }
-  identity fast {
-    base iana-interface-type;
-    description
-      "Fast channel.";
-  }
-  identity ip {
-    base iana-interface-type;
-    description
-      "IP (for APPN HPR in IP networks).";
-  }
-  identity docsCableMaclayer {
-    base iana-interface-type;
-    description
-      "CATV Mac Layer.";
-  }
-  identity docsCableDownstream {
-    base iana-interface-type;
-    description
-      "CATV Downstream interface.";
-  }
-  identity docsCableUpstream {
-    base iana-interface-type;
-    description
-      "CATV Upstream interface.";
-  }
-  identity a12MppSwitch {
-    base iana-interface-type;
-    description
-      "Avalon Parallel Processor.";
-  }
-  identity tunnel {
-    base iana-interface-type;
-    description
-      "Encapsulation interface.";
-  }
-  identity coffee {
-    base iana-interface-type;
-    description
-      "Coffee pot.";
-    reference
-      "RFC 2325 - Coffee MIB";
-  }
-  identity ces {
-    base iana-interface-type;
-    description
-      "Circuit Emulation Service.";
-  }
-  identity atmSubInterface {
-    base iana-interface-type;
-    description
-      "ATM Sub Interface.";
-  }
-  identity l2vlan {
-    base iana-interface-type;
-    description
-      "Layer 2 Virtual LAN using 802.1Q.";
-  }
-  identity l3ipvlan {
-    base iana-interface-type;
-    description
-      "Layer 3 Virtual LAN using IP.";
-  }
-  identity l3ipxvlan {
-    base iana-interface-type;
-    description
-      "Layer 3 Virtual LAN using IPX.";
-  }
-  identity digitalPowerline {
-    base iana-interface-type;
-    description
-      "IP over Power Lines.";
-  }
-  identity mediaMailOverIp {
-    base iana-interface-type;
-    description
-      "Multimedia Mail over IP.";
-  }
-  identity dtm {
-    base iana-interface-type;
-    description
-      "Dynamic synchronous Transfer Mode.";
-  }
-  identity dcn {
-    base iana-interface-type;
-    description
-      "Data Communications Network.";
-  }
-  identity ipForward {
-    base iana-interface-type;
-    description
-      "IP Forwarding Interface.";
-  }
-  identity msdsl {
-    base iana-interface-type;
-    description
-      "Multi-rate Symmetric DSL.";
-  }
-  identity ieee1394 {
-    base iana-interface-type;
-
-    description
-      "IEEE1394 High Performance Serial Bus.";
-  }
-  identity if-gsn {
-    base iana-interface-type;
-    description
-      "HIPPI-6400.";
-  }
-  identity dvbRccMacLayer {
-    base iana-interface-type;
-    description
-      "DVB-RCC MAC Layer.";
-  }
-  identity dvbRccDownstream {
-    base iana-interface-type;
-    description
-      "DVB-RCC Downstream Channel.";
-  }
-  identity dvbRccUpstream {
-    base iana-interface-type;
-    description
-      "DVB-RCC Upstream Channel.";
-  }
-  identity atmVirtual {
-    base iana-interface-type;
-    description
-      "ATM Virtual Interface.";
-  }
-  identity mplsTunnel {
-    base iana-interface-type;
-    description
-      "MPLS Tunnel Virtual Interface.";
-  }
-  identity srp {
-    base iana-interface-type;
-    description
-      "Spatial Reuse Protocol.";
-  }
-  identity voiceOverAtm {
-    base iana-interface-type;
-    description
-      "Voice over ATM.";
-  }
-  identity voiceOverFrameRelay {
-    base iana-interface-type;
-    description
-      "Voice Over Frame Relay.";
-  }
-  identity idsl {
-    base iana-interface-type;
-    description
-      "Digital Subscriber Loop over ISDN.";
-  }
-  identity compositeLink {
-    base iana-interface-type;
-    description
-      "Avici Composite Link Interface.";
-  }
-  identity ss7SigLink {
-    base iana-interface-type;
-    description
-      "SS7 Signaling Link.";
-  }
-  identity propWirelessP2P {
-    base iana-interface-type;
-    description
-      "Prop. P2P wireless interface.";
-  }
-  identity frForward {
-    base iana-interface-type;
-    description
-      "Frame Forward Interface.";
-  }
-  identity rfc1483 {
-    base iana-interface-type;
-    description
-      "Multiprotocol over ATM AAL5.";
-    reference
-      "RFC 1483 - Multiprotocol Encapsulation over ATM
-                  Adaptation Layer 5";
-  }
-  identity usb {
-    base iana-interface-type;
-    description
-      "USB Interface.";
-  }
-  identity ieee8023adLag {
-    base iana-interface-type;
-    description
-      "IEEE 802.3ad Link Aggregate.";
-  }
-  identity bgppolicyaccounting {
-    base iana-interface-type;
-    description
-      "BGP Policy Accounting.";
-  }
-  identity frf16MfrBundle {
-    base iana-interface-type;
-    description
-      "FRF.16 Multilink Frame Relay.";
-  }
-  identity h323Gatekeeper {
-    base iana-interface-type;
-    description
-      "H323 Gatekeeper.";
-  }
-  identity h323Proxy {
-    base iana-interface-type;
-    description
-      "H323 Voice and Video Proxy.";
-  }
-  identity mpls {
-    base iana-interface-type;
-    description
-      "MPLS.";
-  }
-  identity mfSigLink {
-    base iana-interface-type;
-    description
-      "Multi-frequency signaling link.";
-  }
-  identity hdsl2 {
-    base iana-interface-type;
-    description
-      "High Bit-Rate DSL - 2nd generation.";
-  }
-  identity shdsl {
-    base iana-interface-type;
-    description
-      "Multirate HDSL2.";
-  }
-  identity ds1FDL {
-    base iana-interface-type;
-    description
-      "Facility Data Link (4Kbps) on a DS1.";
-  }
-  identity pos {
-    base iana-interface-type;
-    description
-      "Packet over SONET/SDH Interface.";
-  }
-  identity dvbAsiIn {
-    base iana-interface-type;
-    description
-      "DVB-ASI Input.";
-  }
-  identity dvbAsiOut {
-    base iana-interface-type;
-    description
-      "DVB-ASI Output.";
-  }
-  identity plc {
-    base iana-interface-type;
-    description
-      "Power Line Communications.";
-  }
-  identity nfas {
-    base iana-interface-type;
-    description
-      "Non-Facility Associated Signaling.";
-  }
-  identity tr008 {
-    base iana-interface-type;
-    description
-      "TR008.";
-  }
-  identity gr303RDT {
-    base iana-interface-type;
-    description
-      "Remote Digital Terminal.";
-  }
-  identity gr303IDT {
-    base iana-interface-type;
-    description
-      "Integrated Digital Terminal.";
-  }
-  identity isup {
-    base iana-interface-type;
-    description
-      "ISUP.";
-  }
-  identity propDocsWirelessMaclayer {
-    base iana-interface-type;
-    description
-      "Cisco proprietary Maclayer.";
-  }
-  identity propDocsWirelessDownstream {
-    base iana-interface-type;
-    description
-      "Cisco proprietary Downstream.";
-  }
-  identity propDocsWirelessUpstream {
-    base iana-interface-type;
-    description
-      "Cisco proprietary Upstream.";
-  }
-  identity hiperlan2 {
-    base iana-interface-type;
-    description
-      "HIPERLAN Type 2 Radio Interface.";
-  }
-  identity propBWAp2Mp {
-    base iana-interface-type;
-    description
-      "PropBroadbandWirelessAccesspt2Multipt (use of this value
-       for IEEE 802.16 WMAN interfaces as per IEEE Std 802.16f
-       is deprecated, and ieee80216WMAN(237) should be used
-       instead).";
-  }
-  identity sonetOverheadChannel {
-    base iana-interface-type;
-    description
-      "SONET Overhead Channel.";
-  }
-  identity digitalWrapperOverheadChannel {
-    base iana-interface-type;
-    description
-      "Digital Wrapper.";
-  }
-  identity aal2 {
-    base iana-interface-type;
-    description
-      "ATM adaptation layer 2.";
-  }
-  identity radioMAC {
-    base iana-interface-type;
-    description
-      "MAC layer over radio links.";
-  }
-  identity atmRadio {
-    base iana-interface-type;
-    description
-      "ATM over radio links.";
-  }
-  identity imt {
-    base iana-interface-type;
-    description
-      "Inter-Machine Trunks.";
-  }
-  identity mvl {
-    base iana-interface-type;
-    description
-      "Multiple Virtual Lines DSL.";
-  }
-  identity reachDSL {
-    base iana-interface-type;
-    description
-      "Long Reach DSL.";
-  }
-  identity frDlciEndPt {
-    base iana-interface-type;
-    description
-      "Frame Relay DLCI End Point.";
-  }
-  identity atmVciEndPt {
-    base iana-interface-type;
-    description
-      "ATM VCI End Point.";
-  }
-  identity opticalChannel {
-    base iana-interface-type;
-    description
-      "Optical Channel.";
-  }
-  identity opticalTransport {
-    base iana-interface-type;
-    description
-      "Optical Transport.";
-  }
-  identity propAtm {
-    base iana-interface-type;
-    description
-      "Proprietary ATM.";
-  }
-  identity voiceOverCable {
-    base iana-interface-type;
-    description
-      "Voice Over Cable Interface.";
-  }
-  identity infiniband {
-    base iana-interface-type;
-    description
-      "Infiniband.";
-  }
-  identity teLink {
-    base iana-interface-type;
-    description
-      "TE Link.";
-  }
-  identity q2931 {
-    base iana-interface-type;
-    description
-      "Q.2931.";
-  }
-  identity virtualTg {
-    base iana-interface-type;
-    description
-      "Virtual Trunk Group.";
-  }
-  identity sipTg {
-    base iana-interface-type;
-    description
-      "SIP Trunk Group.";
-  }
-  identity sipSig {
-    base iana-interface-type;
-    description
-      "SIP Signaling.";
-  }
-  identity docsCableUpstreamChannel {
-    base iana-interface-type;
-    description
-      "CATV Upstream Channel.";
-  }
-  identity econet {
-    base iana-interface-type;
-    description
-      "Acorn Econet.";
-  }
-  identity pon155 {
-    base iana-interface-type;
-    description
-      "FSAN 155Mb Symetrical PON interface.";
-  }
-  identity pon622 {
-    base iana-interface-type;
-    description
-      "FSAN 622Mb Symetrical PON interface.";
-  }
-  identity bridge {
-    base iana-interface-type;
-    description
-      "Transparent bridge interface.";
-  }
-  identity linegroup {
-    base iana-interface-type;
-    description
-      "Interface common to multiple lines.";
-  }
-  identity voiceEMFGD {
-    base iana-interface-type;
-    description
-      "Voice E&M Feature Group D.";
-  }
-  identity voiceFGDEANA {
-    base iana-interface-type;
-    description
-      "Voice FGD Exchange Access North American.";
-  }
-  identity voiceDID {
-    base iana-interface-type;
-    description
-      "Voice Direct Inward Dialing.";
-  }
-  identity mpegTransport {
-    base iana-interface-type;
-    description
-      "MPEG transport interface.";
-  }
-  identity sixToFour {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "6to4 interface (DEPRECATED).";
-    reference
-      "RFC 4087 - IP Tunnel MIB";
-  }
-  identity gtp {
-    base iana-interface-type;
-    description
-      "GTP (GPRS Tunneling Protocol).";
-  }
-  identity pdnEtherLoop1 {
-    base iana-interface-type;
-    description
-      "Paradyne EtherLoop 1.";
-  }
-  identity pdnEtherLoop2 {
-    base iana-interface-type;
-    description
-      "Paradyne EtherLoop 2.";
-  }
-  identity opticalChannelGroup {
-    base iana-interface-type;
-    description
-      "Optical Channel Group.";
-  }
-  identity homepna {
-    base iana-interface-type;
-    description
-      "HomePNA ITU-T G.989.";
-  }
-  identity gfp {
-    base iana-interface-type;
-    description
-      "Generic Framing Procedure (GFP).";
-  }
-  identity ciscoISLvlan {
-    base iana-interface-type;
-    description
-      "Layer 2 Virtual LAN using Cisco ISL.";
-  }
-  identity actelisMetaLOOP {
-    base iana-interface-type;
-    description
-      "Acteleis proprietary MetaLOOP High Speed Link.";
-  }
-  identity fcipLink {
-    base iana-interface-type;
-    description
-      "FCIP Link.";
-  }
-  identity rpr {
-    base iana-interface-type;
-    description
-      "Resilient Packet Ring Interface Type.";
-  }
-  identity qam {
-    base iana-interface-type;
-    description
-      "RF Qam Interface.";
-  }
-  identity lmp {
-    base iana-interface-type;
-    description
-      "Link Management Protocol.";
-    reference
-      "RFC 4327 - Link Management Protocol (LMP) Management
-                  Information Base (MIB)";
-  }
-  identity cblVectaStar {
-    base iana-interface-type;
-    description
-      "Cambridge Broadband Networks Limited VectaStar.";
-  }
-  identity docsCableMCmtsDownstream {
-    base iana-interface-type;
-    description
-      "CATV Modular CMTS Downstream Interface.";
-  }
-  identity adsl2 {
-    base iana-interface-type;
-    status deprecated;
-    description
-      "Asymmetric Digital Subscriber Loop Version 2
-       (DEPRECATED/OBSOLETED - please use adsl2plus(238)
-       instead).";
-    reference
-      "RFC 4706 - Definitions of Managed Objects for Asymmetric
-                  Digital Subscriber Line 2 (ADSL2)";
-  }
-  identity macSecControlledIF {
-    base iana-interface-type;
-    description
-      "MACSecControlled.";
-  }
-  identity macSecUncontrolledIF {
-    base iana-interface-type;
-    description
-      "MACSecUncontrolled.";
-  }
-  identity aviciOpticalEther {
-    base iana-interface-type;
-    description
-      "Avici Optical Ethernet Aggregate.";
-  }
-  identity atmbond {
-    base iana-interface-type;
-    description
-      "atmbond.";
-  }
-  identity voiceFGDOS {
-    base iana-interface-type;
-    description
-      "Voice FGD Operator Services.";
-  }
-  identity mocaVersion1 {
-    base iana-interface-type;
-    description
-      "MultiMedia over Coax Alliance (MoCA) Interface
-       as documented in information provided privately to IANA.";
-  }
-  identity ieee80216WMAN {
-    base iana-interface-type;
-    description
-      "IEEE 802.16 WMAN interface.";
-  }
-  identity adsl2plus {
-    base iana-interface-type;
-    description
-      "Asymmetric Digital Subscriber Loop Version 2 -
-       Version 2 Plus and all variants.";
-  }
-  identity dvbRcsMacLayer {
-    base iana-interface-type;
-    description
-      "DVB-RCS MAC Layer.";
-    reference
-      "RFC 5728 - The SatLabs Group DVB-RCS MIB";
-  }
-  identity dvbTdm {
-    base iana-interface-type;
-    description
-      "DVB Satellite TDM.";
-    reference
-      "RFC 5728 - The SatLabs Group DVB-RCS MIB";
-  }
-  identity dvbRcsTdma {
-    base iana-interface-type;
-    description
-      "DVB-RCS TDMA.";
-    reference
-      "RFC 5728 - The SatLabs Group DVB-RCS MIB";
-  }
-  identity x86Laps {
-    base iana-interface-type;
-    description
-      "LAPS based on ITU-T X.86/Y.1323.";
-  }
-  identity wwanPP {
-    base iana-interface-type;
-    description
-      "3GPP WWAN.";
-  }
-  identity wwanPP2 {
-    base iana-interface-type;
-    description
-      "3GPP2 WWAN.";
-  }
-  identity voiceEBS {
-    base iana-interface-type;
-    description
-      "Voice P-phone EBS physical interface.";
-  }
-  identity ifPwType {
-    base iana-interface-type;
-    description
-      "Pseudowire interface type.";
-    reference
-      "RFC 5601 - Pseudowire (PW) Management Information Base (MIB)";
-  }
-  identity ilan {
-    base iana-interface-type;
-    description
-      "Internal LAN on a bridge per IEEE 802.1ap.";
-  }
-  identity pip {
-    base iana-interface-type;
-    description
-      "Provider Instance Port on a bridge per IEEE 802.1ah PBB.";
-  }
-  identity aluELP {
-    base iana-interface-type;
-    description
-      "Alcatel-Lucent Ethernet Link Protection.";
-  }
-  identity gpon {
-    base iana-interface-type;
-    description
-      "Gigabit-capable passive optical networks (G-PON) as per
-       ITU-T G.948.";
-  }
-  identity vdsl2 {
-    base iana-interface-type;
-    description
-      "Very high speed digital subscriber line Version 2
-       (as per ITU-T Recommendation G.993.2).";
-    reference
-      "RFC 5650 - Definitions of Managed Objects for Very High
-                  Speed Digital Subscriber Line 2 (VDSL2)";
-  }
-  identity capwapDot11Profile {
-    base iana-interface-type;
-    description
-      "WLAN Profile Interface.";
-    reference
-      "RFC 5834 - Control and Provisioning of Wireless Access
-                  Points (CAPWAP) Protocol Binding MIB for
-                  IEEE 802.11";
-  }
-  identity capwapDot11Bss {
-    base iana-interface-type;
-    description
-      "WLAN BSS Interface.";
-    reference
-      "RFC 5834 - Control and Provisioning of Wireless Access
-                  Points (CAPWAP) Protocol Binding MIB for
-                  IEEE 802.11";
-  }
-  identity capwapWtpVirtualRadio {
-    base iana-interface-type;
-    description
-      "WTP Virtual Radio Interface.";
-    reference
-      "RFC 5833 - Control and Provisioning of Wireless Access
-                  Points (CAPWAP) Protocol Base MIB";
-  }
-  identity bits {
-    base iana-interface-type;
-    description
-      "bitsport.";
-  }
-  identity docsCableUpstreamRfPort {
-    base iana-interface-type;
-    description
-      "DOCSIS CATV Upstream RF Port.";
-  }
-  identity cableDownstreamRfPort {
-    base iana-interface-type;
-    description
-      "CATV downstream RF Port.";
-  }
-  identity vmwareVirtualNic {
-    base iana-interface-type;
-    description
-      "VMware Virtual Network Interface.";
-  }
-  identity ieee802154 {
-    base iana-interface-type;
-    description
-      "IEEE 802.15.4 WPAN interface.";
-    reference
-      "IEEE 802.15.4-2006";
-  }
-  identity otnOdu {
-    base iana-interface-type;
-    description
-      "OTN Optical Data Unit.";
-  }
-  identity otnOtu {
-    base iana-interface-type;
-    description
-      "OTN Optical channel Transport Unit.";
-  }
-  identity ifVfiType {
-    base iana-interface-type;
-    description
-      "VPLS Forwarding Instance Interface Type.";
-  }
-  identity g9981 {
-    base iana-interface-type;
-    description
-      "G.998.1 bonded interface.";
-  }
-  identity g9982 {
-    base iana-interface-type;
-    description
-      "G.998.2 bonded interface.";
-  }
-  identity g9983 {
-    base iana-interface-type;
-    description
-      "G.998.3 bonded interface.";
-  }
-
-  identity aluEpon {
-    base iana-interface-type;
-    description
-      "Ethernet Passive Optical Networks (E-PON).";
-  }
-  identity aluEponOnu {
-    base iana-interface-type;
-    description
-      "EPON Optical Network Unit.";
-  }
-  identity aluEponPhysicalUni {
-    base iana-interface-type;
-    description
-      "EPON physical User to Network interface.";
-  }
-  identity aluEponLogicalLink {
-    base iana-interface-type;
-    description
-      "The emulation of a point-to-point link over the EPON
-       layer.";
-  }
-  identity aluGponOnu {
-    base iana-interface-type;
-    description
-      "GPON Optical Network Unit.";
-    reference
-      "ITU-T G.984.2";
-  }
-  identity aluGponPhysicalUni {
-    base iana-interface-type;
-    description
-      "GPON physical User to Network interface.";
-    reference
-      "ITU-T G.984.2";
-  }
-  identity vmwareNicTeam {
-    base iana-interface-type;
-    description
-      "VMware NIC Team.";
-  }
-  identity docsOfdmDownstream {
-    base iana-interface-type;
-    description
-      "CATV Downstream OFDM interface.";
-  }
-  identity docsOfdmaUpstream {
-    base iana-interface-type;
-    description
-      "CATV Upstream OFDMA interface.";
-  }
-  identity gfast {
-    base iana-interface-type;
-    description
-      "G.fast port.";
-    reference
-      "ITU-T G.9701";
-  }
-  identity sdci {
-    base iana-interface-type;
-    description
-      "SDCI (IO-Link).";
-    reference
-      "IEC 61131-9 Edition 1.0 2013-09";
-  }
-  identity xboxWireless {
-    base iana-interface-type;
-    description
-      "Xbox wireless.";
-  }
-  identity fastdsl {
-    base iana-interface-type;
-    description
-      "FastDSL.";
-    reference
-      "BBF TR-355";
-  }
-  identity docsCableScte55d1FwdOob {
-    base iana-interface-type;
-    description
-      "Cable SCTE 55-1 OOB Forward Channel.";
-  }
-  identity docsCableScte55d1RetOob {
-    base iana-interface-type;
-    description
-      "Cable SCTE 55-1 OOB Return Channel.";
-  }
-  identity docsCableScte55d2DsOob {
-    base iana-interface-type;
-    description
-      "Cable SCTE 55-2 OOB Downstream Channel.";
-  }
-  identity docsCableScte55d2UsOob {
-    base iana-interface-type;
-    description
-      "Cable SCTE 55-2 OOB Upstream Channel.";
-  }
-  identity docsCableNdf {
-    base iana-interface-type;
-    description
-      "Cable Narrowband Digital Forward.";
-  }
-  identity docsCableNdr {
-    base iana-interface-type;
-    description
-      "Cable Narrowband Digital Return.";
-  }
-  identity ptm {
-    base iana-interface-type;
-    description
-      "Packet Transfer Mode.";
-  }
-}

api/models/ietf-inet-types.yang

-module ietf-inet-types {
-
-  namespace "urn:ietf:params:xml:ns:yang:ietf-inet-types";
-  prefix "inet";
-
-  organization
-   "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
-
-  contact
-   "WG Web:   <http://tools.ietf.org/wg/netmod/>
-    WG List:  <mailto:netmod@ietf.org>
-
-    WG Chair: David Kessens
-              <mailto:david.kessens@nsn.com>
-
-    WG Chair: Juergen Schoenwaelder
-              <mailto:j.schoenwaelder@jacobs-university.de>
-
-    Editor:   Juergen Schoenwaelder
-              <mailto:j.schoenwaelder@jacobs-university.de>";
-
-  description
-   "This module contains a collection of generally useful derived
-    YANG data types for Internet addresses and related things.
-
-    Copyright (c) 2013 IETF Trust and the persons identified as
-    authors of the code.  All rights reserved.
-
-    Redistribution and use in source and binary forms, with or
-    without modification, is permitted pursuant to, and subject
-    to the license terms contained in, the Simplified BSD License
-    set forth in Section 4.c of the IETF Trust's Legal Provisions
-    Relating to IETF Documents
-    (http://trustee.ietf.org/license-info).
-
-    This version of this YANG module is part of RFC 6991; see
-    the RFC itself for full legal notices.";
-
-  revision 2013-07-15 {
-    description
-     "This revision adds the following new data types:
-      - ip-address-no-zone
-      - ipv4-address-no-zone
-      - ipv6-address-no-zone";
-    reference
-     "RFC 6991: Common YANG Data Types";
-  }
-
-  revision 2010-09-24 {
-    description
-     "Initial revision.";
-    reference
-     "RFC 6021: Common YANG Data Types";
-  }
-
-  /*** collection of types related to protocol fields ***/
-
-  typedef ip-version {
-    type enumeration {
-      enum unknown {
-        value "0";
-        description
-         "An unknown or unspecified version of the Internet
-          protocol.";
-      }
-      enum ipv4 {
-        value "1";
-        description
-         "The IPv4 protocol as defined in RFC 791.";
-      }
-      enum ipv6 {
-        value "2";
-        description
-         "The IPv6 protocol as defined in RFC 2460.";
-      }
-    }
-    description
-     "This value represents the version of the IP protocol.
-
-      In the value set and its semantics, this type is equivalent
-      to the InetVersion textual convention of the SMIv2.";
-    reference
-     "RFC  791: Internet Protocol
-      RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
-      RFC 4001: Textual Conventions for Internet Network Addresses";
-  }
-
-  typedef dscp {
-    type uint8 {
-      range "0..63";
-    }
-    description
-     "The dscp type represents a Differentiated Services Code Point
-      that may be used for marking packets in a traffic stream.
-      In the value set and its semantics, this type is equivalent
-      to the Dscp textual convention of the SMIv2.";
-    reference
-     "RFC 3289: Management Information Base for the Differentiated
-                Services Architecture
-      RFC 2474: Definition of the Differentiated Services Field
-                (DS Field) in the IPv4 and IPv6 Headers
-      RFC 2780: IANA Allocation Guidelines For Values In
-                the Internet Protocol and Related Headers";
-  }
-
-  typedef ipv6-flow-label {
-    type uint32 {
-      range "0..1048575";
-    }
-    description
-     "The ipv6-flow-label type represents the flow identifier or Flow
-      Label in an IPv6 packet header that may be used to
-      discriminate traffic flows.
-
-      In the value set and its semantics, this type is equivalent
-      to the IPv6FlowLabel textual convention of the SMIv2.";
-    reference
-     "RFC 3595: Textual Conventions for IPv6 Flow Label
-      RFC 2460: Internet Protocol, Version 6 (IPv6) Specification";
-  }
-
-  typedef port-number {
-    type uint16 {
-      range "0..65535";
-    }
-    description
-     "The port-number type represents a 16-bit port number of an
-      Internet transport-layer protocol such as UDP, TCP, DCCP, or
-      SCTP.  Port numbers are assigned by IANA.  A current list of
-      all assignments is available from <http://www.iana.org/>.
-
-      Note that the port number value zero is reserved by IANA.  In
-      situations where the value zero does not make sense, it can
-      be excluded by subtyping the port-number type.
-      In the value set and its semantics, this type is equivalent
-      to the InetPortNumber textual convention of the SMIv2.";
-    reference
-     "RFC  768: User Datagram Protocol
-      RFC  793: Transmission Control Protocol
-      RFC 4960: Stream Control Transmission Protocol
-      RFC 4340: Datagram Congestion Control Protocol (DCCP)
-      RFC 4001: Textual Conventions for Internet Network Addresses";
-  }
-
-  /*** collection of types related to autonomous systems ***/
-
-  typedef as-number {
-    type uint32;
-    description
-     "The as-number type represents autonomous system numbers
-      which identify an Autonomous System (AS).  An AS is a set
-      of routers under a single technical administration, using
-      an interior gateway protocol and common metrics to route
-      packets within the AS, and using an exterior gateway
-      protocol to route packets to other ASes.  IANA maintains
-      the AS number space and has delegated large parts to the
-      regional registries.
-
-      Autonomous system numbers were originally limited to 16
-      bits.  BGP extensions have enlarged the autonomous system
-      number space to 32 bits.  This type therefore uses an uint32
-      base type without a range restriction in order to support
-      a larger autonomous system number space.
-
-      In the value set and its semantics, this type is equivalent
-      to the InetAutonomousSystemNumber textual convention of
-      the SMIv2.";
-    reference
-     "RFC 1930: Guidelines for creation, selection, and registration
-                of an Autonomous System (AS)
-      RFC 4271: A Border Gateway Protocol 4 (BGP-4)
-      RFC 4001: Textual Conventions for Internet Network Addresses
-      RFC 6793: BGP Support for Four-Octet Autonomous System (AS)
-                Number Space";
-  }
-
-  /*** collection of types related to IP addresses and hostnames ***/
-
-  typedef ip-address {
-    type union {
-      type inet:ipv4-address;
-      type inet:ipv6-address;
-    }
-    description
-     "The ip-address type represents an IP address and is IP
-      version neutral.  The format of the textual representation
-      implies the IP version.  This type supports scoped addresses
-      by allowing zone identifiers in the address format.";
-    reference
-     "RFC 4007: IPv6 Scoped Address Architecture";
-  }
-
-  typedef ipv4-address {
-    type string {
-      pattern
-        '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
-      +  '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
-      + '(%[\p{N}\p{L}]+)?';
-    }
-    description
-      "The ipv4-address type represents an IPv4 address in
-       dotted-quad notation.  The IPv4 address may include a zone
-       index, separated by a % sign.
-
-       The zone index is used to disambiguate identical address
-       values.  For link-local addresses, the zone index will
-       typically be the interface index number or the name of an
-       interface.  If the zone index is not present, the default
-       zone of the device will be used.
-
-       The canonical format for the zone index is the numerical
-       format";
-  }
-
-  typedef ipv6-address {
-    type string {
-      pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
-            + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|'
-            + '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}'
-            + '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))'
-            + '(%[\p{N}\p{L}]+)?';
-      pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|'
-            + '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)'
-            + '(%.+)?';
-    }
-    description
-     "The ipv6-address type represents an IPv6 address in full,
-      mixed, shortened, and shortened-mixed notation.  The IPv6
-      address may include a zone index, separated by a % sign.
-
-      The zone index is used to disambiguate identical address
-      values.  For link-local addresses, the zone index will
-      typically be the interface index number or the name of an
-      interface.  If the zone index is not present, the default
-      zone of the device will be used.
-
-      The canonical format of IPv6 addresses uses the textual
-      representation defined in Section 4 of RFC 5952.  The
-      canonical format for the zone index is the numerical
-      format as described in Section 11.2 of RFC 4007.";
-    reference
-     "RFC 4291: IP Version 6 Addressing Architecture
-      RFC 4007: IPv6 Scoped Address Architecture
-      RFC 5952: A Recommendation for IPv6 Address Text
-                Representation";
-  }
-
-  typedef ip-address-no-zone {
-    type union {
-      type inet:ipv4-address-no-zone;
-      type inet:ipv6-address-no-zone;
-    }
-    description
-     "The ip-address-no-zone type represents an IP address and is
-      IP version neutral.  The format of the textual representation
-      implies the IP version.  This type does not support scoped
-      addresses since it does not allow zone identifiers in the
-      address format.";
-    reference
-     "RFC 4007: IPv6 Scoped Address Architecture";
-  }
-
-  typedef ipv4-address-no-zone {
-    type inet:ipv4-address {
-      pattern '[0-9\.]*';
-    }
-    description
-      "An IPv4 address without a zone index.  This type, derived from
-       ipv4-address, may be used in situations where the zone is
-       known from the context and hence no zone index is needed.";
-  }
-
-  typedef ipv6-address-no-zone {
-    type inet:ipv6-address {
-      pattern '[0-9a-fA-F:\.]*';
-    }
-    description
-      "An IPv6 address without a zone index.  This type, derived from
-       ipv6-address, may be used in situations where the zone is
-       known from the context and hence no zone index is needed.";
-    reference
-     "RFC 4291: IP Version 6 Addressing Architecture
-      RFC 4007: IPv6 Scoped Address Architecture
-      RFC 5952: A Recommendation for IPv6 Address Text
-                Representation";
-  }
-
-  typedef ip-prefix {
-    type union {
-      type inet:ipv4-prefix;
-      type inet:ipv6-prefix;
-    }
-    description
-     "The ip-prefix type represents an IP prefix and is IP
-      version neutral.  The format of the textual representations
-      implies the IP version.";
-  }
-
-  typedef ipv4-prefix {
-    type string {
-      pattern
-         '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
-       +  '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])'
-       + '/(([0-9])|([1-2][0-9])|(3[0-2]))';
-    }
-    description
-     "The ipv4-prefix type represents an IPv4 address prefix.
-      The prefix length is given by the number following the
-      slash character and must be less than or equal to 32.
-
-      A prefix length value of n corresponds to an IP address
-      mask that has n contiguous 1-bits from the most
-      significant bit (MSB) and all other bits set to 0.
-
-      The canonical format of an IPv4 prefix has all bits of
-      the IPv4 address set to zero that are not part of the
-      IPv4 prefix.";
-  }
-
-  typedef ipv6-prefix {
-    type string {
-      pattern '((:|[0-9a-fA-F]{0,4}):)([0-9a-fA-F]{0,4}:){0,5}'
-            + '((([0-9a-fA-F]{0,4}:)?(:|[0-9a-fA-F]{0,4}))|'
-            + '(((25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])\.){3}'
-            + '(25[0-5]|2[0-4][0-9]|[01]?[0-9]?[0-9])))'
-            + '(/(([0-9])|([0-9]{2})|(1[0-1][0-9])|(12[0-8])))';
-      pattern '(([^:]+:){6}(([^:]+:[^:]+)|(.*\..*)))|'
-            + '((([^:]+:)*[^:]+)?::(([^:]+:)*[^:]+)?)'
-            + '(/.+)';
-    }
-
-    description
-     "The ipv6-prefix type represents an IPv6 address prefix.
-      The prefix length is given by the number following the
-      slash character and must be less than or equal to 128.
-
-      A prefix length value of n corresponds to an IP address
-      mask that has n contiguous 1-bits from the most
-      significant bit (MSB) and all other bits set to 0.
-
-      The IPv6 address should have all bits that do not belong
-      to the prefix set to zero.
-
-      The canonical format of an IPv6 prefix has all bits of
-      the IPv6 address set to zero that are not part of the
-      IPv6 prefix.  Furthermore, the IPv6 address is represented
-      as defined in Section 4 of RFC 5952.";
-    reference
-     "RFC 5952: A Recommendation for IPv6 Address Text
-                Representation";
-  }
-
-  /*** collection of domain name and URI types ***/
-
-  typedef domain-name {
-    type string {
-      pattern
-        '((([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.)*'
-      + '([a-zA-Z0-9_]([a-zA-Z0-9\-_]){0,61})?[a-zA-Z0-9]\.?)'
-      + '|\.';
-      length "1..253";
-    }
-    description
-     "The domain-name type represents a DNS domain name.  The
-      name SHOULD be fully qualified whenever possible.
-
-      Internet domain names are only loosely specified.  Section
-      3.5 of RFC 1034 recommends a syntax (modified in Section
-      2.1 of RFC 1123).  The pattern above is intended to allow
-      for current practice in domain name use, and some possible
-      future expansion.  It is designed to hold various types of
-      domain names, including names used for A or AAAA records
-      (host names) and other records, such as SRV records.  Note
-      that Internet host names have a stricter syntax (described
-      in RFC 952) than the DNS recommendations in RFCs 1034 and
-      1123, and that systems that want to store host names in
-      schema nodes using the domain-name type are recommended to
-      adhere to this stricter standard to ensure interoperability.
-
-      The encoding of DNS names in the DNS protocol is limited
-      to 255 characters.  Since the encoding consists of labels
-      prefixed by a length bytes and there is a trailing NULL
-      byte, only 253 characters can appear in the textual dotted
-      notation.
-
-      The description clause of schema nodes using the domain-name
-      type MUST describe when and how these names are resolved to
-      IP addresses.  Note that the resolution of a domain-name value
-      may require to query multiple DNS records (e.g., A for IPv4
-      and AAAA for IPv6).  The order of the resolution process and
-      which DNS record takes precedence can either be defined
-      explicitly or may depend on the configuration of the
-      resolver.
-
-      Domain-name values use the US-ASCII encoding.  Their canonical
-      format uses lowercase US-ASCII characters.  Internationalized
-      domain names MUST be A-labels as per RFC 5890.";
-    reference
-     "RFC  952: DoD Internet Host Table Specification
-      RFC 1034: Domain Names - Concepts and Facilities
-      RFC 1123: Requirements for Internet Hosts -- Application
-                and Support
-      RFC 2782: A DNS RR for specifying the location of services
-                (DNS SRV)
-      RFC 5890: Internationalized Domain Names in Applications
-                (IDNA): Definitions and Document Framework";
-  }
-
-  typedef host {
-    type union {
-      type inet:ip-address;
-      type inet:domain-name;
-    }
-    description
-     "The host type represents either an IP address or a DNS
-      domain name.";
-  }
-
-  typedef uri {
-    type string;
-    description
-     "The uri type represents a Uniform Resource Identifier
-      (URI) as defined by STD 66.
-
-      Objects using the uri type MUST be in US-ASCII encoding,
-      and MUST be normalized as described by RFC 3986 Sections
-      6.2.1, 6.2.2.1, and 6.2.2.2.  All unnecessary
-      percent-encoding is removed, and all case-insensitive
-      characters are set to lowercase except for hexadecimal
-      digits, which are normalized to uppercase as described in
-      Section 6.2.2.1.
-
-      The purpose of this normalization is to help provide
-      unique URIs.  Note that this normalization is not
-      sufficient to provide uniqueness.  Two URIs that are
-      textually distinct after this normalization may still be
-      equivalent.
-
-      Objects using the uri type may restrict the schemes that
-      they permit.  For example, 'data:' and 'urn:' schemes
-      might not be appropriate.
-
-      A zero-length URI is not a valid URI.  This can be used to
-      express 'URI absent' where required.
-
-      In the value set and its semantics, this type is equivalent
-      to the Uri SMIv2 textual convention defined in RFC 5017.";
-    reference
-     "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
-      RFC 3305: Report from the Joint W3C/IETF URI Planning Interest
-                Group: Uniform Resource Identifiers (URIs), URLs,
-                and Uniform Resource Names (URNs): Clarifications
-                and Recommendations
-      RFC 5017: MIB Textual Conventions for Uniform Resource
-                Identifiers (URIs)";
-  }
-
-}

api/models/ietf-yang-types.yang

-module ietf-yang-types {
-
-  namespace "urn:ietf:params:xml:ns:yang:ietf-yang-types";
-  prefix "yang";
-
-  organization
-   "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
-
-  contact
-   "WG Web:   <http://tools.ietf.org/wg/netmod/>
-    WG List:  <mailto:netmod@ietf.org>
-
-    WG Chair: David Kessens
-              <mailto:david.kessens@nsn.com>
-
-    WG Chair: Juergen Schoenwaelder
-              <mailto:j.schoenwaelder@jacobs-university.de>
-
-    Editor:   Juergen Schoenwaelder
-              <mailto:j.schoenwaelder@jacobs-university.de>";
-
-  description
-   "This module contains a collection of generally useful derived
-    YANG data types.
-
-    Copyright (c) 2013 IETF Trust and the persons identified as
-    authors of the code.  All rights reserved.
-
-    Redistribution and use in source and binary forms, with or
-    without modification, is permitted pursuant to, and subject
-    to the license terms contained in, the Simplified BSD License
-    set forth in Section 4.c of the IETF Trust's Legal Provisions
-    Relating to IETF Documents
-    (http://trustee.ietf.org/license-info).
-
-    This version of this YANG module is part of RFC 6991; see
-    the RFC itself for full legal notices.";
-
-  revision 2013-07-15 {
-    description
-     "This revision adds the following new data types:
-      - yang-identifier
-      - hex-string
-      - uuid
-      - dotted-quad";
-    reference
-     "RFC 6991: Common YANG Data Types";
-  }
-
-  revision 2010-09-24 {
-    description
-     "Initial revision.";
-    reference
-     "RFC 6021: Common YANG Data Types";
-  }
-
-  /*** collection of counter and gauge types ***/
-
-  typedef counter32 {
-    type uint32;
-    description
-     "The counter32 type represents a non-negative integer
-      that monotonically increases until it reaches a
-      maximum value of 2^32-1 (4294967295 decimal), when it
-      wraps around and starts increasing again from zero.
-
-      Counters have no defined 'initial' value, and thus, a
-      single value of a counter has (in general) no information
-      content.  Discontinuities in the monotonically increasing
-      value normally occur at re-initialization of the
-      management system, and at other times as specified in the
-      description of a schema node using this type.  If such
-      other times can occur, for example, the creation of
-      a schema node of type counter32 at times other than
-      re-initialization, then a corresponding schema node
-      should be defined, with an appropriate type, to indicate
-      the last discontinuity.
-
-      The counter32 type should not be used for configuration
-      schema nodes.  A default statement SHOULD NOT be used in
-      combination with the type counter32.
-
-      In the value set and its semantics, this type is equivalent
-      to the Counter32 type of the SMIv2.";
-    reference
-     "RFC 2578: Structure of Management Information Version 2
-                (SMIv2)";
-  }
-
-  typedef zero-based-counter32 {
-    type yang:counter32;
-    default "0";
-    description
-     "The zero-based-counter32 type represents a counter32
-      that has the defined 'initial' value zero.
-
-      A schema node of this type will be set to zero (0) on creation
-      and will thereafter increase monotonically until it reaches
-      a maximum value of 2^32-1 (4294967295 decimal), when it
-      wraps around and starts increasing again from zero.
-
-      Provided that an application discovers a new schema node
-      of this type within the minimum time to wrap, it can use the
-      'initial' value as a delta.  It is important for a management
-      station to be aware of this minimum time and the actual time
-      between polls, and to discard data if the actual time is too
-      long or there is no defined minimum time.
-
-      In the value set and its semantics, this type is equivalent
-      to the ZeroBasedCounter32 textual convention of the SMIv2.";
-    reference
-      "RFC 4502: Remote Network Monitoring Management Information
-                 Base Version 2";
-  }
-
-  typedef counter64 {
-    type uint64;
-    description
-     "The counter64 type represents a non-negative integer
-      that monotonically increases until it reaches a
-      maximum value of 2^64-1 (18446744073709551615 decimal),
-      when it wraps around and starts increasing again from zero.
-
-      Counters have no defined 'initial' value, and thus, a
-      single value of a counter has (in general) no information
-      content.  Discontinuities in the monotonically increasing
-      value normally occur at re-initialization of the
-      management system, and at other times as specified in the
-      description of a schema node using this type.  If such
-      other times can occur, for example, the creation of
-      a schema node of type counter64 at times other than
-      re-initialization, then a corresponding schema node
-      should be defined, with an appropriate type, to indicate
-      the last discontinuity.
-
-      The counter64 type should not be used for configuration
-      schema nodes.  A default statement SHOULD NOT be used in
-      combination with the type counter64.
-
-      In the value set and its semantics, this type is equivalent
-      to the Counter64 type of the SMIv2.";
-    reference
-     "RFC 2578: Structure of Management Information Version 2
-                (SMIv2)";
-  }
-
-  typedef zero-based-counter64 {
-    type yang:counter64;
-    default "0";
-    description
-     "The zero-based-counter64 type represents a counter64 that
-      has the defined 'initial' value zero.
-
-      A schema node of this type will be set to zero (0) on creation
-      and will thereafter increase monotonically until it reaches
-      a maximum value of 2^64-1 (18446744073709551615 decimal),
-      when it wraps around and starts increasing again from zero.
-
-      Provided that an application discovers a new schema node
-      of this type within the minimum time to wrap, it can use the
-      'initial' value as a delta.  It is important for a management
-      station to be aware of this minimum time and the actual time
-      between polls, and to discard data if the actual time is too
-      long or there is no defined minimum time.
-
-      In the value set and its semantics, this type is equivalent
-      to the ZeroBasedCounter64 textual convention of the SMIv2.";
-    reference
-     "RFC 2856: Textual Conventions for Additional High Capacity
-                Data Types";
-  }
-
-  typedef gauge32 {
-    type uint32;
-    description
-     "The gauge32 type represents a non-negative integer, which
-      may increase or decrease, but shall never exceed a maximum
-      value, nor fall below a minimum value.  The maximum value
-      cannot be greater than 2^32-1 (4294967295 decimal), and
-      the minimum value cannot be smaller than 0.  The value of
-      a gauge32 has its maximum value whenever the information
-      being modeled is greater than or equal to its maximum
-      value, and has its minimum value whenever the information
-      being modeled is smaller than or equal to its minimum value.
-      If the information being modeled subsequently decreases
-      below (increases above) the maximum (minimum) value, the
-      gauge32 also decreases (increases).
-
-      In the value set and its semantics, this type is equivalent
-      to the Gauge32 type of the SMIv2.";
-    reference
-     "RFC 2578: Structure of Management Information Version 2
-                (SMIv2)";
-  }
-
-  typedef gauge64 {
-    type uint64;
-    description
-     "The gauge64 type represents a non-negative integer, which
-      may increase or decrease, but shall never exceed a maximum
-      value, nor fall below a minimum value.  The maximum value
-      cannot be greater than 2^64-1 (18446744073709551615), and
-      the minimum value cannot be smaller than 0.  The value of
-      a gauge64 has its maximum value whenever the information
-      being modeled is greater than or equal to its maximum
-      value, and has its minimum value whenever the information
-      being modeled is smaller than or equal to its minimum value.
-      If the information being modeled subsequently decreases
-      below (increases above) the maximum (minimum) value, the
-      gauge64 also decreases (increases).
-
-      In the value set and its semantics, this type is equivalent
-      to the CounterBasedGauge64 SMIv2 textual convention defined
-      in RFC 2856";
-    reference
-     "RFC 2856: Textual Conventions for Additional High Capacity
-                Data Types";
-  }
-
-  /*** collection of identifier-related types ***/
-
-  typedef object-identifier {
-    type string {
-      pattern '(([0-1](\.[1-3]?[0-9]))|(2\.(0|([1-9]\d*))))'
-            + '(\.(0|([1-9]\d*)))*';
-    }
-    description
-     "The object-identifier type represents administratively
-      assigned names in a registration-hierarchical-name tree.
-
-      Values of this type are denoted as a sequence of numerical
-      non-negative sub-identifier values.  Each sub-identifier
-      value MUST NOT exceed 2^32-1 (4294967295).  Sub-identifiers
-      are separated by single dots and without any intermediate
-      whitespace.
-
-      The ASN.1 standard restricts the value space of the first
-      sub-identifier to 0, 1, or 2.  Furthermore, the value space
-      of the second sub-identifier is restricted to the range
-      0 to 39 if the first sub-identifier is 0 or 1.  Finally,
-      the ASN.1 standard requires that an object identifier
-      has always at least two sub-identifiers.  The pattern
-      captures these restrictions.
-
-      Although the number of sub-identifiers is not limited,
-      module designers should realize that there may be
-      implementations that stick with the SMIv2 limit of 128
-      sub-identifiers.
-
-      This type is a superset of the SMIv2 OBJECT IDENTIFIER type
-      since it is not restricted to 128 sub-identifiers.  Hence,
-      this type SHOULD NOT be used to represent the SMIv2 OBJECT
-      IDENTIFIER type; the object-identifier-128 type SHOULD be
-      used instead.";
-    reference
-     "ISO9834-1: Information technology -- Open Systems
-      Interconnection -- Procedures for the operation of OSI
-      Registration Authorities: General procedures and top
-      arcs of the ASN.1 Object Identifier tree";
-  }
-
-  typedef object-identifier-128 {
-    type object-identifier {
-      pattern '\d*(\.\d*){1,127}';
-    }
-    description
-     "This type represents object-identifiers restricted to 128
-      sub-identifiers.
-
-      In the value set and its semantics, this type is equivalent
-      to the OBJECT IDENTIFIER type of the SMIv2.";
-    reference
-     "RFC 2578: Structure of Management Information Version 2
-                (SMIv2)";
-  }
-
-  typedef yang-identifier {
-    type string {
-      length "1..max";
-      pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*';
-      pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*';
-    }
-    description
-      "A YANG identifier string as defined by the 'identifier'
-       rule in Section 12 of RFC 6020.  An identifier must
-       start with an alphabetic character or an underscore
-       followed by an arbitrary sequence of alphabetic or
-       numeric characters, underscores, hyphens, or dots.
-
-       A YANG identifier MUST NOT start with any possible
-       combination of the lowercase or uppercase character
-       sequence 'xml'.";
-    reference
-      "RFC 6020: YANG - A Data Modeling Language for the Network
-                 Configuration Protocol (NETCONF)";
-  }
-
-  /*** collection of types related to date and time***/
-
-  typedef date-and-time {
-    type string {
-      pattern '\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?'
-            + '(Z|[\+\-]\d{2}:\d{2})';
-    }
-    description
-     "The date-and-time type is a profile of the ISO 8601
-      standard for representation of dates and times using the
-      Gregorian calendar.  The profile is defined by the
-      date-time production in Section 5.6 of RFC 3339.
-
-      The date-and-time type is compatible with the dateTime XML
-      schema type with the following notable exceptions:
-
-      (a) The date-and-time type does not allow negative years.
-
-      (b) The date-and-time time-offset -00:00 indicates an unknown
-          time zone (see RFC 3339) while -00:00 and +00:00 and Z
-          all represent the same time zone in dateTime.
-
-      (c) The canonical format (see below) of data-and-time values
-          differs from the canonical format used by the dateTime XML
-          schema type, which requires all times to be in UTC using
-          the time-offset 'Z'.
-
-      This type is not equivalent to the DateAndTime textual
-      convention of the SMIv2 since RFC 3339 uses a different
-      separator between full-date and full-time and provides
-      higher resolution of time-secfrac.
-
-      The canonical format for date-and-time values with a known time
-      zone uses a numeric time zone offset that is calculated using
-      the device's configured known offset to UTC time.  A change of
-      the device's offset to UTC time will cause date-and-time values
-      to change accordingly.  Such changes might happen periodically
-      in case a server follows automatically daylight saving time
-      (DST) time zone offset changes.  The canonical format for
-      date-and-time values with an unknown time zone (usually
-      referring to the notion of local time) uses the time-offset
-      -00:00.";
-    reference
-     "RFC 3339: Date and Time on the Internet: Timestamps
-      RFC 2579: Textual Conventions for SMIv2
-      XSD-TYPES: XML Schema Part 2: Datatypes Second Edition";
-  }
-
-  typedef timeticks {
-    type uint32;
-    description
-     "The timeticks type represents a non-negative integer that
-      represents the time, modulo 2^32 (4294967296 decimal), in
-      hundredths of a second between two epochs.  When a schema
-      node is defined that uses this type, the description of
-      the schema node identifies both of the reference epochs.
-
-      In the value set and its semantics, this type is equivalent
-      to the TimeTicks type of the SMIv2.";
-    reference
-     "RFC 2578: Structure of Management Information Version 2
-                (SMIv2)";
-  }
-
-  typedef timestamp {
-    type yang:timeticks;
-    description
-     "The timestamp type represents the value of an associated
-      timeticks schema node at which a specific occurrence
-      happened.  The specific occurrence must be defined in the
-      description of any schema node defined using this type.  When
-      the specific occurrence occurred prior to the last time the
-      associated timeticks attribute was zero, then the timestamp
-      value is zero.  Note that this requires all timestamp values
-      to be reset to zero when the value of the associated timeticks
-      attribute reaches 497+ days and wraps around to zero.
-
-      The associated timeticks schema node must be specified
-      in the description of any schema node using this type.
-
-      In the value set and its semantics, this type is equivalent
-      to the TimeStamp textual convention of the SMIv2.";
-    reference
-     "RFC 2579: Textual Conventions for SMIv2";
-  }
-
-  /*** collection of generic address types ***/
-
-  typedef phys-address {
-    type string {
-      pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?';
-    }
-
-    description
-     "Represents media- or physical-level addresses represented
-      as a sequence octets, each octet represented by two hexadecimal
-      numbers.  Octets are separated by colons.  The canonical
-      representation uses lowercase characters.
-
-      In the value set and its semantics, this type is equivalent
-      to the PhysAddress textual convention of the SMIv2.";
-    reference
-     "RFC 2579: Textual Conventions for SMIv2";
-  }
-
-  typedef mac-address {
-    type string {
-      pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}';
-    }
-    description
-     "The mac-address type represents an IEEE 802 MAC address.
-      The canonical representation uses lowercase characters.
-
-      In the value set and its semantics, this type is equivalent
-      to the MacAddress textual convention of the SMIv2.";
-    reference
-     "IEEE 802: IEEE Standard for Local and Metropolitan Area
-                Networks: Overview and Architecture
-      RFC 2579: Textual Conventions for SMIv2";
-  }
-
-  /*** collection of XML-specific types ***/
-
-  typedef xpath1.0 {
-    type string;
-    description
-     "This type represents an XPATH 1.0 expression.
-
-      When a schema node is defined that uses this type, the
-      description of the schema node MUST specify the XPath
-      context in which the XPath expression is evaluated.";
-    reference
-     "XPATH: XML Path Language (XPath) Version 1.0";
-  }
-
-  /*** collection of string types ***/
-
-  typedef hex-string {
-    type string {
-      pattern '([0-9a-fA-F]{2}(:[0-9a-fA-F]{2})*)?';
-    }
-    description
-     "A hexadecimal string with octets represented as hex digits
-      separated by colons.  The canonical representation uses
-      lowercase characters.";
-  }
-
-  typedef uuid {
-    type string {
-      pattern '[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-'
-            + '[0-9a-fA-F]{4}-[0-9a-fA-F]{12}';
-    }
-    description
-     "A Universally Unique IDentifier in the string representation
-      defined in RFC 4122.  The canonical representation uses
-      lowercase characters.
-
-      The following is an example of a UUID in string representation:
-      f81d4fae-7dec-11d0-a765-00a0c91e6bf6
-      ";
-    reference
-     "RFC 4122: A Universally Unique IDentifier (UUID) URN
-                Namespace";
-  }
-
-  typedef dotted-quad {
-    type string {
-      pattern
-        '(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}'
-      + '([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])';
-    }
-    description
-      "An unsigned 32-bit number expressed in the dotted-quad
-       notation, i.e., four octets written as decimal numbers
-       and separated with the '.' (full stop) character.";
-  }
-}

api/models/openconfig-extensions.yang

-module openconfig-extensions {
-
-  yang-version "1";
-
-  // namespace
-  namespace "http://openconfig.net/yang/openconfig-ext";
-
-  prefix "oc-ext";
-
-  // meta
-  organization "OpenConfig working group";
-
-  contact
-    "OpenConfig working group
-    www.openconfig.net";
-
-  description
-    "This module provides extensions to the YANG language to allow
-    OpenConfig specific functionality and meta-data to be defined.";
-
-  revision "2020-06-16" {
-    description
-      "Add extension for POSIX pattern statements.";
-    reference "0.5.0";
-  }
-
-  revision "2018-10-17" {
-    description
-      "Add extension for regular expression type.";
-    reference "0.4.0";
-  }
-
-  revision "2017-04-11" {
-    description
-      "rename password type to 'hashed' and clarify description";
-    reference "0.3.0";
-  }
-
-  revision "2017-01-29" {
-    description
-      "Added extension for annotating encrypted values.";
-    reference "0.2.0";
-  }
-
-  revision "2015-10-09" {
-    description
-      "Initial OpenConfig public release";
-    reference "0.1.0";
-  }
-
-
-  // extension statements
-  extension openconfig-version {
-    argument "semver" {
-      yin-element false;
-    }
-    description
-      "The OpenConfig version number for the module. This is
-      expressed as a semantic version number of the form:
-        x.y.z
-      where:
-        * x corresponds to the major version,
-        * y corresponds to a minor version,
-        * z corresponds to a patch version.
-      This version corresponds to the model file within which it is
-      defined, and does not cover the whole set of OpenConfig models.
-
-      Individual YANG modules are versioned independently -- the
-      semantic version is generally incremented only when there is a
-      change in the corresponding file.  Submodules should always
-      have the same semantic version as their parent modules.
-
-      A major version number of 0 indicates that this model is still
-      in development (whether within OpenConfig or with industry
-      partners), and is potentially subject to change.
-
-      Following a release of major version 1, all modules will
-      increment major revision number where backwards incompatible
-      changes to the model are made.
-
-      The minor version is changed when features are added to the
-      model that do not impact current clients use of the model.
-
-      The patch-level version is incremented when non-feature changes
-      (such as bugfixes or clarifications to human-readable
-      descriptions that do not impact model functionality) are made
-      that maintain backwards compatibility.
-
-      The version number is stored in the module meta-data.";
-  }
-
-  extension openconfig-hashed-value {
-    description
-      "This extension provides an annotation on schema nodes to
-      indicate that the corresponding value should be stored and
-      reported in hashed form.
-
-      Hash algorithms are by definition not reversible. Clients
-      reading the configuration or applied configuration for the node
-      should expect to receive only the hashed value. Values written
-      in cleartext will be hashed. This annotation may be used on
-      nodes such as secure passwords in which the device never reports
-      a cleartext value, even if the input is provided as cleartext.";
-  }
-
-  extension regexp-posix {
-     description
-      "This extension indicates that the regular expressions included
-      within the YANG module specified are conformant with the POSIX
-      regular expression format rather than the W3C standard that is
-      specified by RFC6020 and RFC7950.";
-  }
-
-  extension posix-pattern {
-    argument "pattern" {
-      yin-element false;
-    }
-    description
-      "Provides a POSIX ERE regular expression pattern statement as an
-      alternative to YANG regular expresssions based on XML Schema Datatypes.
-      It is used the same way as the standard YANG pattern statement defined in
-      RFC6020 and RFC7950, but takes an argument that is a POSIX ERE regular
-      expression string.";
-    reference
-      "POSIX Extended Regular Expressions (ERE) Specification:
-      https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04";
-  }
-
-  extension telemetry-on-change {
-    description
-      "The telemetry-on-change annotation is specified in the context
-      of a particular subtree (container, or list) or leaf within the
-      YANG schema. Where specified, it indicates that the value stored
-      by the nodes within the context change their value only in response
-      to an event occurring. The event may be local to the target, for
-      example - a configuration change, or external - such as the failure
-      of a link.
-
-      When a telemetry subscription allows the target to determine whether
-      to export the value of a leaf in a periodic or event-based fashion
-      (e.g., TARGET_DEFINED mode in gNMI), leaves marked as
-      telemetry-on-change should only be exported when they change,
-      i.e., event-based.";
-  }
-
-  extension telemetry-atomic {
-    description
-      "The telemetry-atomic annotation is specified in the context of
-      a subtree (containre, or list), and indicates that all nodes
-      within the subtree are always updated together within the data
-      model. For example, all elements under the subtree may be updated
-      as a result of a new alarm being raised, or the arrival of a new
-       protocol message.
-
-      Transport protocols may use the atomic specification to determine
-      optimisations for sending or storing the corresponding data.";
-  }
-
-  extension operational {
-    description
-      "The operational annotation is specified in the context of a
-      grouping, leaf, or leaf-list within a YANG module. It indicates
-      that the nodes within the context are derived state on the device.
-
-      OpenConfig data models divide nodes into the following three categories:
-
-       - intended configuration - these are leaves within a container named
-         'config', and are the writable configuration of a target.
-       - applied configuration - these are leaves within a container named
-         'state' and are the currently running value of the intended configuration.
-       - derived state - these are the values within the 'state' container which
-         are not part of the applied configuration of the device. Typically, they
-         represent state values reflecting underlying operational counters, or
-         protocol statuses.";
-  }
-
-  extension catalog-organization {
-    argument "org" {
-      yin-element false;
-    }
-    description
-      "This extension specifies the organization name that should be used within
-      the module catalogue on the device for the specified YANG module. It stores
-      a pithy string where the YANG organization statement may contain more
-      details.";
-  }
-
-  extension origin {
-    argument "origin" {
-      yin-element false;
-    }
-    description
-      "This extension specifies the name of the origin that the YANG module
-      falls within. This allows multiple overlapping schema trees to be used
-      on a single network element without requiring module based prefixing
-      of paths.";
-  }
-}

api/models/openconfig-if-types.yang

-module openconfig-if-types {
-  yang-version "1";
-
-  namespace "http://openconfig.net/yang/openconfig-if-types";
-
-  prefix "oc-ift";
-
-  // import statements
-  import openconfig-extensions { prefix oc-ext; }
-
-  // meta
-  organization
-    "OpenConfig working group";
-
-  contact
-    "OpenConfig working group
-    netopenconfig@googlegroups.com";
-
-  description
-    "This module contains a set of interface type definitions that
-    are used across OpenConfig models. These are generally physical
-    or logical interfaces, distinct from hardware ports (which are
-    described by the OpenConfig platform model).";
-
-  oc-ext:openconfig-version "0.2.1";
-
-  revision "2018-11-21" {
-    description
-      "Add OpenConfig module metadata extensions.";
-    reference "0.2.1";
-  }
-
-  revision "2018-01-05" {
-    description
-      "Add tunnel types into the INTERFACE_TYPE identity.";
-    reference "0.2.0";
-  }
-
-  revision "2016-11-14" {
-    description
-      "Initial version";
-    reference "0.1.0";
-  }
-
-  // OpenConfig specific extensions for module metadata.
-  oc-ext:regexp-posix;
-  oc-ext:catalog-organization "openconfig";
-  oc-ext:origin "openconfig";
-
-  identity INTERFACE_TYPE {
-    description
-      "Base identity from which interface types are derived.";
-  }
-
-  identity IF_ETHERNET {
-    base INTERFACE_TYPE;
-    description
-      "Ethernet interfaces based on IEEE 802.3 standards, as well
-      as FlexEthernet";
-    reference
-      "IEEE 802.3-2015 - IEEE Standard for Ethernet
-      OIF Flex Ethernet Implementation Agreement 1.0";
-  }
-
-  identity IF_AGGREGATE {
-    base INTERFACE_TYPE;
-    description
-      "An aggregated, or bonded, interface forming a
-      Link Aggregation Group (LAG), or bundle, most often based on
-      the IEEE 802.1AX (or 802.3ad) standard.";
-    reference
-      "IEEE 802.1AX-2008";
-  }
-
-  identity IF_LOOPBACK {
-    base INTERFACE_TYPE;
-    description
-      "A virtual interface designated as a loopback used for
-      various management and operations tasks.";
-  }
-
-  identity IF_ROUTED_VLAN {
-    base INTERFACE_TYPE;
-    description
-      "A logical interface used for routing services on a VLAN.
-      Such interfaces are also known as switch virtual interfaces
-      (SVI) or integrated routing and bridging interfaces (IRBs).";
-  }
-
-  identity IF_SONET {
-    base INTERFACE_TYPE;
-    description
-      "SONET/SDH interface";
-  }
-
-  identity IF_TUNNEL_GRE4 {
-    base INTERFACE_TYPE;
-    description
-      "A GRE tunnel over IPv4 transport.";
-  }
-
-  identity IF_TUNNEL_GRE6 {
-    base INTERFACE_TYPE;
-    description
-      "A GRE tunnel over IPv6 transport.";
-  }
-
-}