Tweet This is a modified version of the Internet RFC suitable for machine-translating. Original version is available here: RFC7224
Ad
PROPOSED STANDARD
Internet Engineering Task Force (IETF) M. Bjorklund
Request for Comments: 7224 Tail-f Systems
Category: Standards Track May 2014
ISSN: 2070-1721
IANA Interface Type YANG Module
Abstract
This document defines the initial version of the iana-if-type YANG module.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7224.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document defines the initial version of the iana-if-type YANG module for interface type definitions.
The iana-if-type module reflects IANA's existing "ifType definitions" registry [IFTYPE-IANA-REGISTRY]. The latest revision of the module can be obtained from the IANA web site.
Whenever a new interface type is added to the "ifType definitions" registry, the IANAifType-MIB and the iana-if-type YANG module are updated by IANA.
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).
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
"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
"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
} 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
"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.";
}
}
<CODE ENDS>
Bjorklund Standards Track [Page 34]
RFC 7224 IANA Interface Type YANG Module May 20143. IANA Considerations
This document defines the initial version of the IANA-maintained iana-if-type YANG module.
The iana-if-type YANG module is intended to reflect the "ifType definitions" registry [IFTYPE-IANA-REGISTRY], exactly like the IANAifType-MIB MIB module [IANAifType-MIB] reflects the "ifType definitions" registry.
IANA has added this new note to the "iana-if-type YANG Module" registry:
Interface types must not be directly added to the iana-if-type YANG module. They must instead be added to the "ifType definitions" registry.
When an interface type is added to the "ifType definitions" registry, a new "identity" statement must be added to the iana-if-type YANG module. The name of the "identity" is the same as the corresponding enumeration in the IANAifType-MIB. The following substatements to the "identity" statement should be defined:
"base": Contains the value "iana-interface-type".
"status": Include only if a registration has been deprecated (use the value "deprecated") or obsoleted (use the value "obsolete").
"description": Replicate the description from the registry,
if any. Insert line breaks as needed so that the line does not exceed 72 characters.
"reference": Replicate the reference from the registry, if any,
and add the title of the document.
Unassigned or reserved values are not present in the module.
When the iana-if-type YANG module is updated, a new "revision" statement must be added in front of the existing revision statements.
IANA has added this new note to the "ifType definitions" registry:
When this registry is modified, the YANG module iana-if-type must be updated as defined in RFC 7224. The "Reference" text in the "ifType definitions" registry has been updated as:
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, October 2010.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, May 2014.
Author's Address
Martin Bjorklund Tail-f Systems
EMail: mbj@tail-f.com
Bjorklund Standards Track [Page 37]
Ad
Translate documents to 日本語, svenska, Nederlands, Deutsch, français, русский, italiano, español, Tiếng Việt, polski, português, 中文, українська, català, norsk, فارسی, suomi, Bahasa Indonesia, العربية, čeština, 한국어, Bahasa Melayu, magyar, română, српски and other languages.
