Imported Upstream version 0.4.8
[platform/upstream/libsmi.git] / mibs / iana / IANA-GMPLS-TC-MIB
1
2 IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
3
4    IMPORTS
5        MODULE-IDENTITY, mib-2              FROM SNMPv2-SMI  -- RFC 2578
6        TEXTUAL-CONVENTION                  FROM SNMPv2-TC;  -- RFC 2579
7
8    ianaGmpls MODULE-IDENTITY
9        LAST-UPDATED
10                   "200702270000Z" -- 27 February 2007 00:00:00 GMT
11        ORGANIZATION
12                   "IANA"
13        CONTACT-INFO
14                   "Internet Assigned Numbers Authority
15                    Postal: 4676 Admiralty Way, Suite 330
16                            Marina del Rey, CA 90292
17                    Tel:    +1 310 823 9358
18                    E-Mail: iana&iana.org"
19        DESCRIPTION
20          "Copyright (C) The IETF Trust (2007).  The initial version
21           of this MIB module was published in RFC 4802.  For full legal
22           notices see the RFC itself.  Supplementary information
23           may be available on:
24           http://www.ietf.org/copyrights/ianamib.html"
25
26           REVISION
27            "200702270000Z" -- 27 February 2007 00:00:00 GMT
28          DESCRIPTION
29            "Initial version issued as part of RFC 4802."
30
31        ::= { mib-2 152 }
32
33    IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
34        STATUS       current
35        DESCRIPTION
36             "This type is used to represent and control
37              the LSP encoding type of an LSP signaled by a GMPLS
38              signaling protocol.
39
40              This textual convention is strongly tied to the LSP
41              Encoding Types sub-registry of the GMPLS Signaling
42              Parameters registry managed by IANA.  Values should be
43              assigned by IANA in step with the LSP Encoding Types
44              sub-registry and using the same registry management rules.
45              However, the actual values used in this textual convention
46              are solely within the purview of IANA and do not
47              necessarily match the values in the LSP Encoding Types
48              sub-registry.
49
50              The definition of this textual convention with the
51              addition of newly assigned values is published
52              periodically by the IANA, in either the Assigned
53              Numbers RFC, or some derivative of it specific to
54              Internet Network Management number assignments.  (The
55              latest arrangements can be obtained by contacting the
56              IANA.)
57
58              Requests for new values should be made to IANA via
59              email (iana&iana.org)."
60        REFERENCE
61             "1. Generalized Multi-Protocol Label Switching (GMPLS)
62                 Signaling Functional Description, RFC 3471, section
63                 3.1.1.
64              2. Generalized MPLS Signalling Extensions for G.709 Optical
65                 Transport Networks Control, RFC 4328, section 3.1.1."
66        SYNTAX  INTEGER {
67                   tunnelLspNotGmpls(0),        -- GMPLS is not in use
68                   tunnelLspPacket(1),          -- Packet
69                   tunnelLspEthernet(2),        -- Ethernet
70                   tunnelLspAnsiEtsiPdh(3),     -- PDH
71                   -- the value 4 is deprecated
72                   tunnelLspSdhSonet(5),        -- SDH or SONET
73                   -- the value 6 is deprecated
74                   tunnelLspDigitalWrapper(7),  -- Digital Wrapper
75                   tunnelLspLambda(8),          -- Lambda
76                   tunnelLspFiber(9),           -- Fiber
77                   -- the value 10 is deprecated
78                   tunnelLspFiberChannel(11),   -- Fiber Channel
79
80                   tunnelDigitalPath(12),       -- Digital Path
81                   tunnelOpticalChannel(13)     -- Optical Channel
82                 }
83
84    IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
85        STATUS       current
86        DESCRIPTION
87             "This type is used to represent and
88              control the LSP switching type of an LSP signaled by a
89              GMPLS signaling protocol.
90
91              This textual convention is strongly tied to the Switching
92              Types sub-registry of the GMPLS Signaling Parameters
93              registry managed by IANA.  Values should be assigned by
94              IANA in step with the Switching Types sub-registry and
95              using the same registry management rules.  However, the
96              actual values used in this textual convention are solely
97              within the purview of IANA and do not necessarily match
98              the values in the Switching Types sub-registry.
99
100              The definition of this textual convention with the
101              addition of newly assigned values is published
102              periodically by the IANA, in either the Assigned
103              Numbers RFC, or some derivative of it specific to
104              Internet Network Management number assignments.  (The
105              latest arrangements can be obtained by contacting the
106              IANA.)
107
108              Requests for new values should be made to IANA via
109              email (iana&iana.org)."
110        REFERENCE
111             "1. Routing Extensions in Support of Generalized
112                 Multi-Protocol Label Switching, RFC 4202, section 2.4.
113              2. Generalized Multi-Protocol Label Switching (GMPLS)
114                 Signaling Functional Description, RFC 3471, section
115                 3.1.1."
116        SYNTAX  INTEGER {
117                   unknown(0),   -- none of the following, or not known
118                   psc1(1),      -- Packet-Switch-Capable 1
119                   psc2(2),      -- Packet-Switch-Capable 2
120                   psc3(3),      -- Packet-Switch-Capable 3
121                   psc4(4),      -- Packet-Switch-Capable 4
122                   l2sc(51),     -- Layer-2-Switch-Capable
123                   tdm(100),     -- Time-Division-Multiplex
124                   lsc(150),     -- Lambda-Switch-Capable
125                   fsc(200)      -- Fiber-Switch-Capable
126                 }
127
128    IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
129        STATUS       current
130        DESCRIPTION
131             "This data type is used to represent and control the LSP
132              Generalized Protocol Identifier (G-PID) of an LSP
133              signaled by a GMPLS signaling protocol.
134
135              This textual convention is strongly tied to the Generalized
136              PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
137              registry managed by IANA.  Values should be assigned by
138              IANA in step with the Generalized PIDs (G-PID) sub-registry
139              and using the same registry management rules.  However, the
140              actual values used in this textual convention are solely
141              within the purview of IANA and do not necessarily match the
142              values in the Generalized PIDs (G-PID) sub-registry.
143
144              The definition of this textual convention with the
145              addition of newly assigned values is published
146              periodically by the IANA, in either the Assigned
147              Numbers RFC, or some derivative of it specific to
148              Internet Network Management number assignments.  (The
149              latest arrangements can be obtained by contacting the
150              IANA.)
151
152              Requests for new values should be made to IANA via
153              email (iana&iana.org)."
154         REFERENCE
155             "1. Generalized Multi-Protocol Label Switching (GMPLS)
156                 Signaling Functional Description, RFC 3471, section
157                 3.1.1.
158              2. Generalized MPLS Signalling Extensions for G.709 Optical
159                 Transport Networks Control, RFC 4328, section 3.1.3."
160         SYNTAX  INTEGER {
161                   unknown(0),      -- unknown or none of the following
162                   -- the values 1, 2, 3 and 4 are reserved in RFC 3471
163                   asynchE4(5),
164                   asynchDS3T3(6),
165                   asynchE3(7),
166                   bitsynchE3(8),
167                   bytesynchE3(9),
168                   asynchDS2T2(10),
169                   bitsynchDS2T2(11),
170                   reservedByRFC3471first(12),
171                   asynchE1(13),
172                   bytesynchE1(14),
173                   bytesynch31ByDS0(15),
174                   asynchDS1T1(16),
175                   bitsynchDS1T1(17),
176
177                   bytesynchDS1T1(18),
178                   vc1vc12(19),
179                   reservedByRFC3471second(20),
180                   reservedByRFC3471third(21),
181                   ds1SFAsynch(22),
182                   ds1ESFAsynch(23),
183                   ds3M23Asynch(24),
184                   ds3CBitParityAsynch(25),
185                   vtLovc(26),
186                   stsSpeHovc(27),
187                   posNoScramble16BitCrc(28),
188                   posNoScramble32BitCrc(29),
189                   posScramble16BitCrc(30),
190                   posScramble32BitCrc(31),
191                   atm(32),
192                   ethernet(33),
193                   sdhSonet(34),
194                   digitalwrapper(36),
195                   lambda(37),
196                   ansiEtsiPdh(38),
197                   lapsSdh(40),
198                   fddi(41),
199                   dqdb(42),
200                   fiberChannel3(43),
201                   hdlc(44),
202                   ethernetV2DixOnly(45),
203                   ethernet802dot3Only(46),
204                   g709ODUj(47),
205                   g709OTUk(48),
206                   g709CBRorCBRa(49),
207                   g709CBRb(50),
208                   g709BSOT(51),
209                   g709BSNT(52),
210                   gfpIPorPPP(53),
211                   gfpEthernetMAC(54),
212                   gfpEthernetPHY(55),
213                   g709ESCON(56),
214                   g709FICON(57),
215                   g709FiberChannel(58)
216                 }
217
218    IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
219         STATUS current
220         DESCRIPTION
221             "This data type determines the setting of the
222              Admin Status flags in the Admin Status object or TLV, as
223              described in RFC 3471.  Setting this object to a non-zero
224              value will result in the inclusion of the Admin Status
225
226              object or TLV on signaling messages.
227
228              This textual convention is strongly tied to the
229              Administrative Status Information Flags sub-registry of
230              the GMPLS Signaling Parameters registry managed by IANA.
231              Values should be assigned by IANA in step with the
232              Administrative Status Flags sub-registry and using the
233              same registry management rules.  However, the actual
234              values used in this textual convention are solely
235              within the purview of IANA and do not necessarily match
236              the values in the Administrative Status Information
237              Flags sub-registry.
238
239              The definition of this textual convention with the
240              addition of newly assigned values is published
241              periodically by the IANA, in either the Assigned
242              Numbers RFC, or some derivative of it specific to
243              Internet Network Management number assignments.  (The
244              latest arrangements can be obtained by contacting the
245              IANA.)
246
247              Requests for new values should be made to IANA via
248              email (iana&iana.org)."
249         REFERENCE
250             "1. Generalized Multi-Protocol Label Switching (GMPLS)
251                 Signaling Functional Description, RFC 3471, section 8.
252              2. Generalized MPLS Signaling - RSVP-TE Extensions,
253                 RFC 3473, section 7.
254              3. GMPLS - Communication of Alarm Information,
255                 RFC 4783, section 3.2.1."
256         SYNTAX BITS {
257                   reflect(0), -- Reflect bit (RFC 3471)
258                   reserved1(1), -- reserved
259                   reserved2(2), -- reserved
260                   reserved3(3), -- reserved
261                   reserved4(4), -- reserved
262                   reserved5(5), -- reserved
263                   reserved6(6), -- reserved
264                   reserved7(7), -- reserved
265                   reserved8(8), -- reserved
266                   reserved9(9), -- reserved
267                   reserved10(10), -- reserved
268                   reserved11(11), -- reserved
269                   reserved12(12), -- reserved
270                   reserved13(13), -- reserved
271                   reserved14(14), -- reserved
272                   reserved15(15), -- reserved
273                   reserved16(16), -- reserved
274
275                   reserved17(17), -- reserved
276                   reserved18(18), -- reserved
277                   reserved19(19), -- reserved
278                   reserved20(20), -- reserved
279                   reserved21(21), -- reserved
280                   reserved22(22), -- reserved
281                   reserved23(23), -- reserved
282                   reserved24(24), -- reserved
283                   reserved25(25), -- reserved
284                   reserved26(26), -- reserved
285                   reserved27(27), -- Inhibit Alarm bit (RFC 4783)
286                   reserved28(28), -- reserved
287                   testing(29), -- Testing bit (RFC 3473)
288                   administrativelyDown(30), -- Admin down (RFC 3473)
289                   deleteInProgress(31) -- Delete bit (RFC 3473)
290                 }
291 END
292