Converted from YANG file 'IANAifType-MIB.yang' by yangdump version 2.2.1724 Module: IANAifType-MIB Organization: IANA Version: 2005-10-10 Contact: Internet Assigned Numbers Authority Postal: ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Tel: +1 310 823 9358 E-Mail: iana@iana.org This MIB module defines the IANAifType Textual Convention, and thus the enumerated values of the ifType object defined in MIB-II's ifTable. /usr/share/yuma/modules/ietf/IANAifType-MIB.yang IANA Internet Assigned Numbers Authority Postal: ICANN 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Tel: +1 310 823 9358 E-Mail: iana@iana.org 2005-10-10 Registration of new IANA ifType 230. 2005-09-09 Registration of new IANA ifType 229. 2005-05-27 Registration of new IANA ifType 228. 2005-03-03 Added the IANAtunnelType TC and deprecated IANAifType sixToFour (215) per RFC4087. 2004-11-22 Registration of new IANA ifType 227. 2004-06-17 Registration of new IANA ifType 226. 2004-05-12 Added description for IANAifType 6, and changed the descriptions for IANAifTypes 180, 181, and 182. 2004-05-07 Registration of new IANAifType 225. 2003-08-25 Deprecated IANAifTypes 7 and 11. Obsoleted IANAifTypes 62, 69, and 117. ethernetCsmacd (6) should be used instead of these values 2003-08-18 Registration of new IANAifType 224. 2003-08-07 Registration of new IANAifTypes 222 and 223. 2003-03-18 Registration of new IANAifType 221. 2003-01-13 Registration of new IANAifType 220. 2002-10-17 Registration of new IANAifType 219. 2002-07-16 Registration of new IANAifTypes 217 and 218. 2002-07-10 Registration of new IANAifTypes 215 and 216. 2002-06-19 Registration of new IANAifType 214. 2002-01-04 Registration of new IANAifTypes 211, 212 and 213. 2001-12-20 Registration of new IANAifTypes 209 and 210. 2001-11-15 Registration of new IANAifTypes 207 and 208. 2001-11-06 Registration of new IANAifType 206. 2001-11-02 Registration of new IANAifType 205. 2001-10-16 Registration of new IANAifTypes 199, 200, 201, 202, 203, and 204. 2001-09-19 Registration of new IANAifType 198. 2001-05-11 Registration of new IANAifType 197. 2001-01-12 Registration of new IANAifTypes 195 and 196. 2000-12-19 Registration of new IANAifTypes 193 and 194. 2000-12-07 Registration of new IANAifTypes 191 and 192. 2000-12-04 Registration of new IANAifType 190. 2000-10-17 Registration of new IANAifTypes 188 and 189. 2000-10-02 Registration of new IANAifType 187. 2000-09-01 Registration of new IANAifTypes 184, 185, and 186. 2000-08-24 Registration of new IANAifType 183. 2000-08-23 Registration of new IANAifTypes 174-182. 2000-08-22 Registration of new IANAifTypes 170, 171, 172 and 173. 2000-04-25 Registration of new IANAifTypes 168 and 169. 2000-03-06 Fixed a missing semi-colon in the IMPORT. Also cleaned up the REVISION log a bit. It is not complete, but from now on it will be maintained and kept up to date with each change to this MIB module. 1999-10-08 Include new name assignments up to cnr(85). This is the first version available via the WWW at: ftp://ftp.isi.edu/mib/ianaiftype.mib 1994-01-31 Initial version of this MIB as published in RFC 1573. This data type is used as the syntax of the ifType object in the (updated) definition of MIB-II's ifTable. The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) Requests for new values should be made to IANA via email (iana@iana.org). The relationship between the assignment of ifType values and of OIDs to particular media-specific MIBs is solely the purview of IANA and is subject to change without notice. Quite often, a media-specific MIB's OID-subtree assignment within MIB-II's 'transmission' subtree will be the same as its ifType value. However, in some circumstances this will not be the case, and implementors must not pre-assume any specific relationship between ifType values and transmission subtree OIDs. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 The encapsulation method used by a tunnel. The value direct indicates that a packet is encapsulated directly within a normal IP header, with no intermediate header, and unicast to the remote tunnel endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC 1933 IPv6-in-IPv4 tunnel). The value minimal indicates that a Minimal Forwarding Header (RFC 2004) is inserted between the outer header and the payload packet. The value UDP indicates that the payload packet is encapsulated within a normal UDP packet (e.g., RFC 1234). The values sixToFour, sixOverFour, and isatap indicates that an IPv6 packet is encapsulated directly within an IPv4 header, with no intermediate header, and unicast to the destination determined by the 6to4, 6over4, or ISATAP protocol. The remaining protocol-specific values indicate that a header of the protocol of that name is inserted between the outer header and the payload header. The assignment policy for IANAtunnelType values is identical to the policy for assigning IANAifType values. 1 2 3 4 5 6 7 8 9 10 11 12 13 14