draft-ietf-ccamp-gmpls-te-mib-12.txt   draft-ietf-ccamp-gmpls-te-mib-13.txt 
Internet Working Group Thomas D. Nadeau, Ed. Internet Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: June 2006 Adrian Farrel, Ed. Expires: September 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
December 2005 March 2006
Generalized Multiprotocol Label Switching (GMPLS) Traffic Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base Engineering Management Information Base
draft-ietf-ccamp-gmpls-te-mib-12.txt draft-ietf-ccamp-gmpls-te-mib-13.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 24 skipping to change at page 2, line 24
5.1. gmplsTunnelTable ..................................... 5 5.1. gmplsTunnelTable ..................................... 5
5.2. gmplsTunnelHopTable .................................. 6 5.2. gmplsTunnelHopTable .................................. 6
5.3. gmplsTunnelARHopTable ................................ 6 5.3. gmplsTunnelARHopTable ................................ 6
5.4. gmplsTunnelCHopTable ................................. 6 5.4. gmplsTunnelCHopTable ................................. 6
5.5. gmplsTunnelErrorTable ................................ 6 5.5. gmplsTunnelErrorTable ................................ 6
5.6. gmplsTunnelReversePerfTable .......................... 6 5.6. gmplsTunnelReversePerfTable .......................... 6
5.7. Use of 32-bit and 64-bit Counters ................... 6 5.7. Use of 32-bit and 64-bit Counters ................... 6
6. Cross-referencing to the gmplsLabelTable ............... 7 6. Cross-referencing to the gmplsLabelTable ............... 7
7. Example of GMPLS Tunnel Setup .......................... 7 7. Example of GMPLS Tunnel Setup .......................... 7
8. GMPLS Traffic Engineering MIB Module .................. 11 8. GMPLS Traffic Engineering MIB Module .................. 11
9. Security Considerations ............................... 48 9. Security Considerations ............................... 47
10. Acknowledgments ...................................... 49 10. Acknowledgments ...................................... 48
11. IANA Considerations .................................. 49 11. IANA Considerations .................................. 48
11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 50 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 49
11.2. Dependence on IANA MIB Modules ..................... 50 11.2. Dependence on IANA MIB Modules ..................... 49
11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 50 11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 49
12. References ........................................... 58 12. References ........................................... 57
12.1. Normative References ............................... 59 12.1. Normative References ............................... 57
12.2. Informative References ............................. 59 12.2. Informative References ............................. 58
13. Contact Information .................................. 60 13. Contact Information .................................. 59
14. Intellectual Property Considerations ................. 60 14. Intellectual Property Considerations ................. 59
15. Full Copyright Statement ............................. 61 15. Full Copyright Statement ............................. 60
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling In particular, it describes managed objects for modeling
Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based
traffic engineering. The tables and objects defined in this document traffic engineering. The tables and objects defined in this document
extend those defined in the equivalent document for MPLS traffic extend those defined in the equivalent document for MPLS traffic
engineering [RFC3812], and management of GMPLS traffic engineering is engineering [RFC3812], and management of GMPLS traffic engineering is
skipping to change at page 8, line 50 skipping to change at page 8, line 48
{ {
gmplsTunnelUnnumIf = true (1), gmplsTunnelUnnumIf = true (1),
gmplsTunnelAttributes = labelRecordingRequired (1), gmplsTunnelAttributes = labelRecordingRequired (1),
gmplsTunnelLSPEncoding = tunnelLspLambda, gmplsTunnelLSPEncoding = tunnelLspLambda,
gmplsTunnelSwitchingType = lsc, gmplsTunnelSwitchingType = lsc,
gmplsTunnelLinkProtection = shared (2), gmplsTunnelLinkProtection = shared (2),
gmplsTunnelGPid = lambda, gmplsTunnelGPid = lambda,
gmplsTunnelSecondary = false (2), gmplsTunnelSecondary = false (2),
gmplsTunnelDirection = bidirectional (1) gmplsTunnelDirection = bidirectional (1)
gmplsTunnelPathComp = explicit(2), gmplsTunnelPathComp = explicit(2),
gmplsTunnelRequestedUpstreamNotifyRecipientType = ipv4(1), gmplsTunnelSendPathNotifyRecipientType = ipv4(1),
gmplsTunnelRequestedUpstreamNotifyRecipient = 'C0A86401'H, gmplsTunnelSendPathNotifyRecipient = 'C0000201'H,
gmplsTunnelAdminStatusFlags = 0, gmplsTunnelAdminStatusFlags = 0,
gmplsTunnelExtraParamsPtr = 0.0 gmplsTunnelExtraParamsPtr = 0.0
} }
Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and
gmplsTunnelHopTable are created and activated at this time. gmplsTunnelHopTable are created and activated at this time.
In mplsTunnelResourceTable: In mplsTunnelResourceTable:
{ {
mplsTunnelResourceIndex = 6, mplsTunnelResourceIndex = 6,
mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMaxRate = 0,
mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMeanRate = 0,
mplsTunnelResourceMaxBurstSize = 0, mplsTunnelResourceMaxBurstSize = 0,
mplsTunnelResourceRowStatus = createAndGo (4) mplsTunnelResourceRowStatus = createAndGo (4)
skipping to change at page 11, line 10 skipping to change at page 11, line 10
In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2)
{ {
mplsTunnelRowStatus = active(1) mplsTunnelRowStatus = active(1)
} }
8. GMPLS Traffic Engineering MIB Module 8. GMPLS Traffic Engineering MIB Module
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], [RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411],
[RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202] [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202]
and [GMPLS-G709]. and [RFC4328].
GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
TruthValue, TimeStamp, RowPointer TruthValue, TimeStamp, RowPointer
skipping to change at page 11, line 43 skipping to change at page 11, line 43
FROM MPLS-TE-STD-MIB -- RFC3812 FROM MPLS-TE-STD-MIB -- RFC3812
IANAGmplsLSPEncodingType, IANAGmplsSwitchingType, IANAGmplsLSPEncodingType, IANAGmplsSwitchingType,
IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation
FROM IANA-GMPLS-TC-MIB FROM IANA-GMPLS-TC-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
; ;
gmplsTeStdMIB MODULE-IDENTITY gmplsTeStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200510130001Z" -- 13 October 2005 00:00:01 GMT "200603020001Z" -- 2 March 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working "IETF Common Control And Measurement Plane (CCAMP) Working
Group" Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2005). This version of "Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC xxxx; see the RFC itself for this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices. full legal notices.
-- RFC Ed. Please replace xxxx above with the correct RFC number and -- RFC Ed. Please replace xxxx above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module contains managed object definitions This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in: for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS) 1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor), Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003. RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003." L. (Editor), RFC 3473, January 2003."
REVISION REVISION
"200510130001Z" -- 13 October 2005 00:00:01 GMT "200603020001Z" -- 2 March 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC xxxx." "Initial version issued as part of RFC xxxx."
::= { mplsStdMIB XXX } ::= { mplsStdMIB XXX }
-- RFC Editor. Please replace xxxx above with the correct RFC number and -- RFC Editor. Please replace xxxx above with the correct RFC number and
-- remove this note. -- remove this note.
-- RFC Editor. Please replace XXX above with the OID assigned by IANA -- RFC Editor. Please replace XXX above with the OID assigned by IANA
-- and remove this note -- and remove this note
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
skipping to change at page 15, line 13 skipping to change at page 15, line 13
} }
gmplsTunnelUnnumIf OBJECT-TYPE gmplsTunnelUnnumIf OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes whether or not this tunnel corresponds to an unnumbered "Denotes whether or not this tunnel corresponds to an unnumbered
interface represented by an entry in the interfaces group table interface represented by an entry in the interfaces group table
(the ifTable) with ifType set to mpls (166). (the ifTable) with ifType set to mpls (166).
This object is only used if mplsTunnelIsIf is set to 'true'. This object is only used if mplsTunnelIsIf is set to true(1).
If both this object and the mplsTunnelIsIf object are set to If both this object and the mplsTunnelIsIf object are set to
'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID true(1), the originating LSR adds an LSP_TUNNEL_INTERFACE_ID
object to the outgoing Path message. object to the outgoing Path message.
This object contains information that is only used by the This object contains information that is only used by the
terminating LSR." terminating LSR."
REFERENCE REFERENCE
"1. Signalling Unnumbered Links in RSVP-TE, RFC 3477." "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477."
DEFVAL { false } DEFVAL { false }
::= { gmplsTunnelEntry 1 } ::= { gmplsTunnelEntry 1 }
gmplsTunnelAttributes OBJECT-TYPE gmplsTunnelAttributes OBJECT-TYPE
skipping to change at page 41, line 4 skipping to change at page 40, line 42
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering "1. Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB), RFC 3812." (TE) Management Information Base (MIB), RFC 3812."
::= { gmplsTeNotifications 1 } ::= { gmplsTeNotifications 1 }
gmplsTeGroups gmplsTeGroups
OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
gmplsTeCompliances gmplsTeCompliances
OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
-- The mandatory group has to be implemented by all LSRs that
-- originate, terminate or act as transit for TE-LSPs/tunnels.
-- In addition, depending on the type of tunnels supported, other
-- groups become mandatory as explained below.
gmplsTeModuleFullCompliance MODULE-COMPLIANCE gmplsTeModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support for "Compliance statement for agents that provide full support for
GMPLS-TE-STD-MIB. Such devices can then be monitored and also GMPLS-TE-STD-MIB. Such devices can then be monitored and also
be configured using this MIB module." be configured using this MIB module.
The mandatory group has to be implemented by all LSRs that
originate, terminate or act as transit for TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, other
groups become mandatory as explained below."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup, gmplsTunnelScalarGroup,
gmplsTunnelSignaledGroup gmplsTunnelSignaledGroup
} }
::= { gmplsTeCompliances 1 } ::= { gmplsTeCompliances 1 }
-- Compliance requirement for read-only compliant implementations. -- Compliance requirement for read-only compliant implementations.
skipping to change at page 41, line 43 skipping to change at page 41, line 34
MODULE -- this module MODULE -- this module
-- The mandatory group has to be implemented by all LSRs that -- The mandatory group has to be implemented by all LSRs that
-- originate, terminate or act as transit for TE-LSPs/tunnels. -- originate, terminate or act as transit for TE-LSPs/tunnels.
-- In addition, depending on the type of tunnels supported, other -- In addition, depending on the type of tunnels supported, other
-- groups become mandatory as explained below. -- groups become mandatory as explained below.
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup gmplsTunnelScalarGroup,
gmplsTunnelUnnumIf
} }
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support signaled "This group is mandatory for devices which support signaled
tunnel set up, in addition to gmplsTunnelGroup. The following tunnel set up, in addition to gmplsTunnelGroup. The following
constraints apply: constraints apply:
mplsTunnelSignallingProto should be at least read-only mplsTunnelSignallingProto should be at least read-only
returning a value of ldp(2), or rsvp(3)." returning a value of ldp(2), or rsvp(3)."
GROUP gmplsTunnelIsNotIntfcGroup
DESCRIPTION
"This group is mandatory for devices which support tunnels that
are not interfaces, in addition to gmplsTunnelGroup. The
following constraints apply:
mplsTunnelIsIf must at least be read-only returning no(0)."
GROUP gmplsTunnelIsIntfcGroup GROUP gmplsTunnelIsIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support tunnels that "This group is mandatory for devices which support tunnels that
are interfaces, in addition to gmplsTunnelGroup." are interfaces, in addition to gmplsTunnelGroup."
GROUP gmplsTunnelOptionalGroup GROUP gmplsTunnelOptionalGroup
DESCRIPTION DESCRIPTION
"Objects in this group are optional." "Objects in this group are optional."
GROUP gmplsTeNotificationGroup GROUP gmplsTeNotificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those implementations which can "This group is mandatory for those implementations which can
implement the notifications contained in this group." implement the notifications contained in this group."
-- All scalars have max access read-only -- All scalars have max access read-only
OBJECT gmplsTunnelAttributes OBJECT gmplsTunnelAttributes
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 43, line 17 skipping to change at page 42, line 46
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelSecondary OBJECT gmplsTunnelSecondary
SYNTAX TruthValue SYNTAX TruthValue
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelDirection OBJECT gmplsTunnelDirection
SYNTAX INTEGER {
forward (0),
bidirectional (1)
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only forward (0) is required." "Only forward (0) is required."
OBJECT gmplsTunnelPathComp OBJECT gmplsTunnelPathComp
SYNTAX INTEGER {
dynamicFull(1), -- CSPF fully computed
explicit(2), -- fully specified path
dynamicPartial(3) -- CSPF partially computed
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only explicit (2) is required." "Only explicit (2) is required."
OBJECT gmplsTunnelUpstreamNotifyRecipientType OBJECT gmplsTunnelUpstreamNotifyRecipientType
SYNTAX InetAddressType SYNTAX InetAddressType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelUpstreamNotifyRecipient OBJECT gmplsTunnelUpstreamNotifyRecipient
SYNTAX InetAddress SYNTAX InetAddress
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 44, line 33 skipping to change at page 44, line 4
SYNTAX InetAddressType SYNTAX InetAddressType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelSendPathNotifyRecipient OBJECT gmplsTunnelSendPathNotifyRecipient
SYNTAX InetAddress SYNTAX InetAddress
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelAdminStatusFlags OBJECT gmplsTunnelAdminStatusFlags
SYNTAX IANAGmplsAdminStatusInformation SYNTAX IANAGmplsAdminStatusInformation
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelExtraParamsPtr OBJECT gmplsTunnelExtraParamsPtr
SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- gmplsTunnelHopLabelStatuses has max access read-only -- gmplsTunnelHopLabelStatuses has max access read-only
OBJECT gmplsTunnelHopExplicitForwardLabel OBJECT gmplsTunnelHopExplicitForwardLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 46, line 11 skipping to change at page 45, line 29
gmplsTunnelErrorHelpString gmplsTunnelErrorHelpString
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to implement "Necessary, but not sufficient, set of objects to implement
tunnels. In addition, depending on the type of the tunnels tunnels. In addition, depending on the type of the tunnels
supported (for example, manually configured or signaled, supported (for example, manually configured or signaled,
persistent or non-persistent, etc.), the following other persistent or non-persistent, etc.), the following other
groups defined below are mandatory: groups defined below are mandatory:
gmplsTunnelSignaledGroup, gmplsTunnelIsNotIntfcGroup - gmplsTunnelSignaledGroup
and/or gmplsTunnelIsIntfcGroup." - gmplsTunnelIsIntfcGroup."
::= { gmplsTeGroups 1 } ::= { gmplsTeGroups 1 }
gmplsTunnelSignaledGroup OBJECT-GROUP gmplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelAttributes, gmplsTunnelAttributes,
gmplsTunnelLSPEncoding, gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType, gmplsTunnelSwitchingType,
gmplsTunnelLinkProtection, gmplsTunnelLinkProtection,
gmplsTunnelGPid, gmplsTunnelGPid,
gmplsTunnelSecondary, gmplsTunnelSecondary,
skipping to change at page 47, line 4 skipping to change at page 46, line 21
gmplsTunnelScalarGroup OBJECT-GROUP gmplsTunnelScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelsConfigured, gmplsTunnelsConfigured,
gmplsTunnelsActive gmplsTunnelsActive
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Scalar objects needed to implement MPLS tunnels." "Scalar objects needed to implement MPLS tunnels."
::= { gmplsTeGroups 3 } ::= { gmplsTeGroups 3 }
gmplsTunnelIsIntfcGroup OBJECT-GROUP gmplsTunnelIsIntfcGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelUnnumIf gmplsTunnelUnnumIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement tunnels that are interfaces." "Objects needed to implement tunnels that are interfaces."
::= { gmplsTeGroups 4 } ::= { gmplsTeGroups 4 }
gmplsTunnelIsNotIntfcGroup OBJECT-GROUP
OBJECTS {
gmplsTunnelUnnumIf
}
STATUS current
DESCRIPTION
"Objects needed to implement tunnels that are not interfaces."
::= { gmplsTeGroups 5 }
gmplsTunnelOptionalGroup OBJECT-GROUP gmplsTunnelOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelExtraParamsPtr, gmplsTunnelExtraParamsPtr,
gmplsTunnelARHopLabelStatuses, gmplsTunnelARHopLabelStatuses,
gmplsTunnelARHopExplicitForwardLabel, gmplsTunnelARHopExplicitForwardLabel,
gmplsTunnelARHopExplicitForwardLabelPtr, gmplsTunnelARHopExplicitForwardLabelPtr,
gmplsTunnelARHopExplicitReverseLabel, gmplsTunnelARHopExplicitReverseLabel,
gmplsTunnelARHopExplicitReverseLabelPtr, gmplsTunnelARHopExplicitReverseLabelPtr,
gmplsTunnelARHopProtection, gmplsTunnelARHopProtection,
gmplsTunnelCHopLabelStatuses, gmplsTunnelCHopLabelStatuses,
gmplsTunnelCHopExplicitForwardLabel, gmplsTunnelCHopExplicitForwardLabel,
gmplsTunnelCHopExplicitForwardLabelPtr, gmplsTunnelCHopExplicitForwardLabelPtr,
gmplsTunnelCHopExplicitReverseLabel, gmplsTunnelCHopExplicitReverseLabel,
gmplsTunnelCHopExplicitReverseLabelPtr gmplsTunnelCHopExplicitReverseLabelPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The objects in this group are optional." "The objects in this group are optional."
::= { gmplsTeGroups 6 } ::= { gmplsTeGroups 5 }
gmplsTeNotificationGroup NOTIFICATION-GROUP gmplsTeNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
gmplsTunnelDown gmplsTunnelDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. None is "Set of notifications implemented in this module. None is
mandatory." mandatory."
::= { gmplsTeGroups 7 } ::= { gmplsTeGroups 6 }
END END
9. Security Considerations 9. Security Considerations
It is clear that the MIB modules described in this document in It is clear that the MIB modules described in this document in
association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful
for monitoring of MPLS and GMPLS tunnels. These MIB modules can also for monitoring of MPLS and GMPLS tunnels. These MIB modules can also
be used for configuration of certain objects, and anything that can be used for configuration of certain objects, and anything that can
be configured can be incorrectly configured, with potentially be configured can be incorrectly configured, with potentially
skipping to change at page 51, line 4 skipping to change at page 50, line 10
specified in this document as { transmission YYY }. specified in this document as { transmission YYY }.
-- RFC Editor. -- RFC Editor.
-- Please replace YYY above with assigned OID and remove this note. -- Please replace YYY above with assigned OID and remove this note.
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579
ianaGmpls MODULE-IDENTITY ianaGmpls MODULE-IDENTITY
LAST-UPDATED "200510130001Z" -- 13 October 2005 00:00:01 GMT LAST-UPDATED "200603020001Z" -- 2 March 2006 00:00:01 GMT
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: USC/Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292 4676 Admiralty Way, Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 822 1511
E-Mail: iana@isi.edu" E-Mail: iana@isi.edu"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2005). The initial version "Copyright (C) The Internet Society (2006). The initial version
of this MIB module was published in RFC XXX. For full legal of this MIB module was published in RFC XXX. For full legal
notices see the RFC itself. Supplementary information notices see the RFC itself. Supplementary information
may be available on: may be available on:
http://www.ietf.org/copyrights/ianamib.html" http://www.ietf.org/copyrights/ianamib.html"
-- RFC Editor. Please replace XXX above with the correct RFC number -- RFC Editor. Please replace XXX above with the correct RFC number
-- Your actions may vary depending on how IANA chooses to handle -- Your actions may vary depending on how IANA chooses to handle
-- this IANA MIB. -- this IANA MIB.
-- Please remove this note. -- Please remove this note.
REVISION REVISION
"200510130001Z" -- 13 October 2005 00:00:01 GMT "200603020001Z" -- 2 March 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC XXX."
::= { transmission YYY } ::= { transmission YYY }
-- RFC Editor. Please replace YYY above with the OID assigned by IANA -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- Please replace XXX with the real RFC number. -- Please replace XXX with the real RFC number.
-- Please remove this note. -- Please remove this note.
IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 52, line 20 skipping to change at page 51, line 25
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu)." email (iana@isi.edu)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section Signaling Functional Description, RFC 3471, section
3.1.1. 3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical 2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, draft-ietf-ccamp-gmpls-g709, Transport Networks Control, RFC 4328, section 3.1.1."
work in progress, section 3.1.1."
-- RFC Editor. Please update this reference to the RFC before -- RFC Editor. Please update this reference to the RFC before
-- publication and remove this note -- publication and remove this note
SYNTAX INTEGER { SYNTAX INTEGER {
tunnelLspNotGmpls (0), -- GMPLS is not in use tunnelLspNotGmpls (0), -- GMPLS is not in use
-- This is not part of the LSP -- This is not part of the LSP
-- Encoding Type registry, but -- Encoding Type registry, but
-- is needed for the correct -- is needed for the correct
-- functioning of the -- functioning of the
-- GMPLS-TE-STD-MIB -- GMPLS-TE-STD-MIB
tunnelLspPacket (1), -- Packet tunnelLspPacket (1), -- Packet
skipping to change at page 54, line 40 skipping to change at page 53, line 40
latest arrangements can be obtained by contacting the latest arrangements can be obtained by contacting the
IANA.) IANA.)
Requests for new values should be made to IANA via Requests for new values should be made to IANA via
email (iana@isi.edu)." email (iana@isi.edu)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section Signaling Functional Description, RFC 3471, section
3.1.1. 3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical 2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, draft-ietf-ccamp-gmpls-g709, Transport Networks Control, RFC 4328, section 3.1.3."
work in progress, section 3.1.3."
-- RFC Editor. Please update this reference to the RFC before -- RFC Editor. Please update this reference to the RFC before
-- publication and remove this note -- publication and remove this note
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), -- unknown or none of the following unknown(0), -- unknown or none of the following
-- the values 1, 2, 3 and 4 are reserved in RFC 3471
asynchE4(5), asynchE4(5),
asynchDS3T3(6), asynchDS3T3(6),
asynchE3(7), asynchE3(7),
bitsynchE3(8), bitsynchE3(8),
bytesynchE3(9), bytesynchE3(9),
asynchDS2T2(10), asynchDS2T2(10),
bitsynchDS2T2(11), bitsynchDS2T2(11),
-- the value 12 is reserved in RFC 3471
asynchE1(13), asynchE1(13),
bytesynchE1(14), bytesynchE1(14),
bytesynch31ByDS0(15), bytesynch31ByDS0(15),
asynchDS1T1(16), asynchDS1T1(16),
bitsynchDS1T1(17), bitsynchDS1T1(17),
bytesynchDS1T1(18), bytesynchDS1T1(18),
vc1vc12(19), vc1vc12(19),
-- the values 20 and 21 are reserved in RFC 3471
ds1SFAsynch(22), ds1SFAsynch(22),
ds1ESFAsynch(23), ds1ESFAsynch(23),
ds3M23Asynch(24), ds3M23Asynch(24),
ds3CBitParityAsynch(25), ds3CBitParityAsynch(25),
vtLovc(26), vtLovc(26),
stsSpeHovc(27), stsSpeHovc(27),
posNoScramble16BitCrc(28), posNoScramble16BitCrc(28),
posNoScramble32BitCrc(29), posNoScramble32BitCrc(29),
posScramble16BitCrc(30), posScramble16BitCrc(30),
posScramble32BitCrc(31), posScramble32BitCrc(31),
skipping to change at page 59, line 30 skipping to change at page 58, line 30
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in
Support of Generalized Multi-Protocol Label Switching", Support of Generalized Multi-Protocol Label Switching",
RFC 4202, October 2005. RFC 4202, October 2005.
[RFC4328] Papadimitriou, D., Ed., "Generalized MPLS Signalling
Extensions for G.709 Optical Transport Networks
Control", draft-ietf-ccamp-gmpls-g709, work in progress.
[GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol
Label Switching (GMPLS) Label Switching Router (LSR) Label Switching (GMPLS) Label Switching Router (LSR)
Management Information Base", Management Information Base",
draft-ietf-ccamp-gmpls-lsr-mib, work in progress. draft-ietf-ccamp-gmpls-lsr-mib, work in progress.
[GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual
Conventions for Multiprotocol Label Switching (MPLS) Conventions for Multiprotocol Label Switching (MPLS)
Management", draft-ietf-ccamp-gmpls-tc-mib, work in Management", draft-ietf-ccamp-gmpls-tc-mib, work in
progress. progress.
[GMPLS-G709] Papadimitriou, D., Ed., "Generalized MPLS Signalling
Extensions for G.709 Optical Transport Networks
Control", draft-ietf-ccamp-gmpls-g709, work in progress.
12.2. Informative References 12.2. Informative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
skipping to change at page 61, line 22 skipping to change at page 60, line 21
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 42 change blocks. 
77 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/