Internet DRAFT - draft-stephan-pce-pcedp-pcc-mib
draft-stephan-pce-pcedp-pcc-mib
Network Working Group E. Stephan
Internet-Draft France Telecom
Expires: December 27, 2006 June 25, 2006
Definitions of Managed Objects for Path Computation Element Discovery
Protocol (PCEDP) inside a Path Computation Client (PCC)
draft-stephan-pce-pcedp-pcc-mib-01
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 27, 2006.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects used for managing Path
Computation Elements Discovery Protocol (PCEDP) inside a Path
Computation Client (PCC) application.
Stephan Expires December 27, 2006 [Page 1]
Internet-Draft PCC PCEDP MIB June 2006
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 4
6.2. The Discovery objects . . . . . . . . . . . . . . . . . . 5
6.3. General PCEs capabilities objects . . . . . . . . . . . . 5
6.4. The Notification Group . . . . . . . . . . . . . . . . . . 5
7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6
7.1. Relationship to IGP MIB modules . . . . . . . . . . . . . 6
7.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 6
8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . . 21
Appendix A. Open Issues . . . . . . . . . . . . . . . . . . . . . 21
Appendix B. Editing MIB module in XML . . . . . . . . . . . . . . 22
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24
Stephan Expires December 27, 2006 [Page 2]
Internet-Draft PCC PCEDP MIB June 2006
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes objects used for managing Path
Computation Elements Discovery Protocol (PCEDP) inside a Path
Computation Client (PCC) application.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted
as described in BCP 14, RFC 2119 [RFC2119].
4. Terminology
The terminology used in this document is built on notions introduced
and discussed in PCE WG documents. The reader should be familiar
with these documents.
Domain:
any collection of network elements within a common sphere of
address management or path computational responsibility.
IGP Area:
OSPF Area or ISIS level.
PCC:
Stephan Expires December 27, 2006 [Page 3]
Internet-Draft PCC PCEDP MIB June 2006
Path Computation Client: any client application requesting a path
computation to be performed by a Path Computation Element.
PCE:
Path Computation Element: an entity (component, application, or
network node) that is capable of computing a network path or route
based on a network graph, and applying computational constraints.
5. Overview
[I-D.ietf-pce-architecture], describes the architecture for a PCE-
based path computation model for MPLS and GMPLS TE LSPs. The
architecture allows the separation of PCE from PCC. It requires that
a PCC be aware of the location of one or more PCEs. This relies on a
communication protocol between PCC and PCE for automatic and dynamic
PCE discovery.
[I-D.ietf-pce-discovery-reqs] defines the mechanism and the
information of PCE discovery. [I-D.ietf-pce-disco-proto-igp]
declines theses components for PCCs participating to an IGP routing
domain:
o The discovery mechanism relies on IGP (OSPF, ISIS) routing
protocol;
o It defines the information elements a PCE participating in the IGP
advertises in IGP extensions.
The section "6.10.2.1. PCC MIB module " of [I-D.ietf-pce-discovery-
reqs] identifies the information to be disclosed on the management
interface of the PCC. The current MIB module defines the
corresponding objects.
6. Structure of the MIB Module
Objects in this MIB module are arranged into groups. Each group is
organized as a set of related objects. The overall structure and
assignment of objects to their groups, and the intended purpose of
each group, is shown below.
6.1. Textual Conventions
6.1.1. PccPceDpRoutingDomainID
A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS information
element carries the identifier of a routing domain (area,as) which
type and size depend on both the routing protocol and on the version
of Internet protocol in use in this routing domain.
Stephan Expires December 27, 2006 [Page 4]
Internet-Draft PCC PCEDP MIB June 2006
The Textual Convention PccPceDpRoutingDomainID defines a common SMI
type for these different kinds of routing domain identifiers.
These TCs are used for defining PCE-DOMAINS and PCE-DEST-DOMAINS
objects.
6.2. The Discovery objects
These objects provide PCE discovery information and discovery
activities.
It includes:
- A control to disable the automatic discovery mechanism;
- The number of known PCEs;
- The number of discovered PCEs;
- The set of known PCEs.
pccPcedpDiscPceTable gives discovery information per PCE:
- Addresses, discovery Mechanism type;
- Discovery time, last activity time
pccPcedpDiscActTable gives discovery activity per PCE:
* congestion
* discovery protocol activity: these objects will define the
average and maximum rates of arrival, departure and
modification of PCE discovery to enable effective analysis of
the operation of the protocols.
* these objects will report on the operation of the discovery
protocol by counting the number of unacceptable and
incomprehensible information exchanges.
6.3. General PCEs capabilities objects
These objects provides general information per PCE regarding PCE-
PATHSCOPE, PCE-DOMAINS and PCE-DEST-DOMAINS
CapPathScopeTable defines PCE computation capabilities and PCE
preferences per kind of routing domain.
CapDomainTable defines domains for which a PCE has topology
visibility and can compute paths.
CapDestDomainTable defines domains toward which a PCE can compute
path
6.4. The Notification Group
This group will define notifications when thresholds (e.g. on the
maximum rate of change, on the number of unacceptable messages) are
Stephan Expires December 27, 2006 [Page 5]
Internet-Draft PCC PCEDP MIB June 2006
crossed, or when important events occur (e.g. the number of
discovered PCEs decreases to zero).
7. Relationship to Other MIB Modules
7.1. Relationship to IGP MIB modules
PCEDP relies on existing protocols which have specialized MIB objects
to monitor protocol activities. Consequently this document considers
that the monitoring of the undelying protocol in out of the scope of
the current MIB module.
7.2. MIB modules required for IMPORTS
The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578],
SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], and IF-MIB [RFC2863] and
also REFERENCEs document RFC0768 [RFC0768]
8. Definitions
PCC-PCEDP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Gauge32, Integer32, IpAddress,
experimental FROM SNMPv2-SMI
RowStatus,
TEXTUAL-CONVENTION,
TimeStamp,
TruthValue
FROM SNMPv2-TC
Ipv6Address
FROM IPV6-TC
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF
AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
IANAipRouteProtocol
FROM IANA-RTPROTO-MIB;
pccPcedpMIB MODULE-IDENTITY
Stephan Expires December 27, 2006 [Page 6]
Internet-Draft PCC PCEDP MIB June 2006
LAST-UPDATED "200606150000Z" -- June 15, 2006
ORGANIZATION "PCE Working Group"
CONTACT-INFO "WG-email: pce@ietf.org
WG-URL: http://www.ietf.org/html.charters/pce-charter.html
TODO: This section has to be completed with chairs and authors
addresses
"
DESCRIPTION
"This MIB module defines a collection of objects for managing Path
Computation Elements (PCEs) Discovery Protocol inside a Path
Computation Client (PCC) application."
::= { experimental 10000 } -- Temporary node ( for smilint)
-- Textual Conventions used in this MIB module --
PccPceDpRoutingDomainID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS
information element carries the identifier of a routing domain
(area,as) which type depends on both the routing protocol and
on the version of Internet protocol in use in this routing
domain.
This TC defines a common SMI type for the different kinds of
routing domain identifiers.
An PccPceDpRoutingDomainID value is always interpreted within
the context of an AddressFamilyNumbers value. Every usage of
the PccPceDpRoutingDomainID textual convention is required to
specify the AddressFamilyNumbers object which provides the
context.
The value of an PccPceDpRoutingDomainID object must always be
consistent with the value of the associated
AddressFamilyNumbers object.
Following is the mapping between AddressFamilyNumbers type and
PccPceDpRoutingDomainID size:
ipV4(1):
PccPceDpRoutingDomainID is an InetAddressIPv4
corresponding to the name of an OSPF area;
ipV6(2):
PccPceDpRoutingDomainID is an InetAddressIPv6
corresponding to the name of an OSPF area;
Stephan Expires December 27, 2006 [Page 7]
Internet-Draft PCC PCEDP MIB June 2006
nsap(3):
PccPceDpRoutingDomainID type is OCTET STRING (SIZE
(0..20)), corresponding to the name of an ISIS area (see
RFC 1195);
asNumber(18)
PccPceDpRoutingDomainID type is OCTET STRING (SIZE (2))
corresponding to the name of an Autonomous System.
"
SYNTAX OCTET STRING (SIZE (0..20))
-- Notification --
pccPcedpNotifications OBJECT IDENTIFIER ::= { pccPcedpMIB 0 }
-- empty for now
pccPcedpMIBObjects OBJECT IDENTIFIER ::= { pccPcedpMIB 1 }
pccPcedpDiscoveryObjects OBJECT IDENTIFIER ::= { pccPcedpMIBObjects 1
}
pccPcedpDiscAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to disabled(2) disables the discovery of
PCEs. Once disabled, The discovery must be explicitly enabled
to restore discovery of PCEs. Setting this object to
enabled(1) enables the discovery of PCEs."
::= { pccPcedpDiscoveryObjects 1 }
pccPcedpDiscKnowPCEs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCEs the PCC is potentially in relation with.
This includes PCE manually declared and active PCEs"
::= { pccPcedpDiscoveryObjects 2 }
pccPcedpDiscActivePCEs OBJECT-TYPE
SYNTAX Counter32
Stephan Expires December 27, 2006 [Page 8]
Internet-Draft PCC PCEDP MIB June 2006
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of active PCEs.
The detection of the activity a a PCE depends on the nature
discovery mechanism.
PCE discovered using PCED information received:
The relation between the PCC and a PCE is active while the
PCE discovery protocol maintains a communication between the
PCC and this PCE.
PCE Manually declared:
The relation between the PCC and a PCE is active and the
discovery mechanism is implementation specific;
"
::= { pccPcedpDiscoveryObjects 3 }
pccPcedpDiscPceTable OBJECT-TYPE
SYNTAX SEQUENCE OF PccPcedpDiscPceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the PCEs discovered by the PCC."
::= { pccPcedpDiscoveryObjects 4 }
pccPcedpDiscPceEntry OBJECT-TYPE
SYNTAX PccPcedpDiscPceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the general information of each PCE
discovered by the PCC.
"
INDEX { pccPcedpDiscPceIndex }
::= { pccPcedpDiscPceTable 1 }
PccPcedpDiscPceEntry ::= SEQUENCE {
pccPcedpDiscPceIndex Integer32,
pccPcedpDiscMechanism IANAipRouteProtocol,
pccPcedpDiscPceIPv4Address IpAddress,
pccPcedpDiscPceIPv6Address Ipv6Address,
pccPcedpDiscPceTime TimeStamp,
pccPcedpDiscPceLastUpdated TimeStamp
}
pccPcedpDiscPceIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
Stephan Expires December 27, 2006 [Page 9]
Internet-Draft PCC PCEDP MIB June 2006
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object identifies locally the PCE for which this entry
contains information."
::= { pccPcedpDiscPceEntry 1 }
pccPcedpDiscMechanism OBJECT-TYPE
SYNTAX IANAipRouteProtocol
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the type of discovery mechanism used by
PCC to discover the PCE.
The acceptable value are :
local (2), -- local interface
isIs (9), -- Dual IS-IS
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
"
::= { pccPcedpDiscPceEntry 2 }
pccPcedpDiscPceIPv4Address OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the IP address to be used to reach the PCE. It
corresponds to the PCED PCE-ADDRESS.
.
A value of 0.0.0.0 indicates the absence of this address."
::= { pccPcedpDiscPceEntry 3 }
pccPcedpDiscPceIPv6Address OBJECT-TYPE
SYNTAX Ipv6Address
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the IPv6 address to be used to reach the PCE.
It corresponds to the PCED PCE-ADDRESS.
A value of ::0 indicates the absence of this address."
::= { pccPcedpDiscPceEntry 4 }
pccPcedpDiscPceTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
Stephan Expires December 27, 2006 [Page 10]
Internet-Draft PCC PCEDP MIB June 2006
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this entry was created.
local entry: the value of sysUpTime at the time PCC restarted."
::= { pccPcedpDiscPceEntry 5 }
pccPcedpDiscPceLastUpdated OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this entry was last
updated.
Static entry: if the entry values keep unchanged since the re-
initialization of the PCC then this object contains a zero
value."
::= { pccPcedpDiscPceEntry 6 }
--
-- pccPcedpDiscActTable;
--
pccPcedpDiscActTable OBJECT-TYPE
SYNTAX SEQUENCE OF PccPcedpDiscActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing for each PCE the activity of the
discovery mechanism."
::= { pccPcedpDiscoveryObjects 5 }
pccPcedpDiscActEntry OBJECT-TYPE
SYNTAX PccPcedpDiscActEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the activity of the discovery mechanism
of a PCE discovered by the PCC."
INDEX { pccPcedpDiscPceIndex }
::= { pccPcedpDiscActTable 1 }
PccPcedpDiscActEntry ::= SEQUENCE {
pccPcedpDiscActCongestion TruthValue,
Stephan Expires December 27, 2006 [Page 11]
Internet-Draft PCC PCEDP MIB June 2006
pccPcedpDiscActCongestionDuration Unsigned32
}
pccPcedpDiscActCongestion OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether a PCE experiences a processing
congestion state or not.
"
::= { pccPcedpDiscActEntry 1 }
pccPcedpDiscActCongestionDuration OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies, in seconds, the congestion duration.
When the value of pccPcedpDiscActCongestion is 'false' then
this objet MUST be to '0'"
::= { pccPcedpDiscActEntry 2 }
pccPcedpCapabilityObjects OBJECT IDENTIFIER ::= { pccPcedpMIBObjects
2 }
--
-- PCE-PATHSCOPE informations elements
--
pccPcedpCapPathScopeTable OBJECT-TYPE
SYNTAX SEQUENCE OF PccPcedpCapPathScopeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the capacity of the PCEs discovered by
the PCC."
::= { pccPcedpCapabilityObjects 1 }
pccPcedpCapPathScopeEntry OBJECT-TYPE
SYNTAX PccPcedpCapPathScopeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Stephan Expires December 27, 2006 [Page 12]
Internet-Draft PCC PCEDP MIB June 2006
"Information describing the capacity of each PCE discovered by
the PCC."
INDEX { pccPcedpDiscPceIndex }
::= { pccPcedpCapPathScopeTable 1 }
PccPcedpCapPathScopeEntry ::= SEQUENCE {
pccPcedpCapPathScopeIntraArea TruthValue,
pccPcedpCapPathScopeInterArea TruthValue,
pccPcedpCapPathScopeDefaultInterArea TruthValue,
pccPcedpCapPathScopeInterAS TruthValue,
pccPcedpCapPathScopeDefaultInterAS TruthValue,
pccPcedpCapPathScopeInterLayer TruthValue,
pccPcedpCapPathScopePrefIntraArea Integer32,
pccPcedpCapPathScopePrefInterArea Integer32,
pccPcedpCapPathScopePrefInterAS Integer32,
pccPcedpCapPathScopePrefInterLayer Integer32
}
pccPcedpCapPathScopeIntraArea OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the L option of the PATH-
SCOPE sub TLV:
The value is 'true' if the PCE can compute intra-area path."
::= { pccPcedpCapPathScopeEntry 1 }
pccPcedpCapPathScopeInterArea OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the R option of the PATH-
SCOPE sub TLV:
The value is 'true' if the PCE can act as PCE for inter-area
TE LSPs computation."
::= { pccPcedpCapPathScopeEntry 2 }
pccPcedpCapPathScopeDefaultInterArea OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the Rd option of the PATH-
SCOPE sub TLV:
Stephan Expires December 27, 2006 [Page 13]
Internet-Draft PCC PCEDP MIB June 2006
The value is 'true' if the PCE can act as a default PCE for
inter-area TE LSPs computation."
::= { pccPcedpCapPathScopeEntry 3 }
pccPcedpCapPathScopeInterAS OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the S option of the PATH-
SCOPE sub TLV:
The value is 'true' if the PCE can act as PCE for inter-AS
TE LSPs computation."
::= { pccPcedpCapPathScopeEntry 4 }
pccPcedpCapPathScopeDefaultInterAS OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the Sd option of the PATH-
SCOPE sub TLV:
The value is 'true' if the PCE can act as a default PCE for
inter-AS TE LSPs computation."
::= { pccPcedpCapPathScopeEntry 5 }
pccPcedpCapPathScopeInterLayer OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the PCE supports the Y option of the PATH-
SCOPE sub TLV:
The value is 'true' if the PCE can compute or take part into
the computation of paths across layers."
::= { pccPcedpCapPathScopeEntry 6}
pccPcedpCapPathScopePrefIntraArea OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the level of preference of the option of computation
'L' compared to other computation options:
A value of 7 reflects the highest preference.
When the value of PccPcedpCapCompIntraArea is 'false' then
this objet MUST be to '0'."
::= { pccPcedpCapPathScopeEntry 7}
Stephan Expires December 27, 2006 [Page 14]
Internet-Draft PCC PCEDP MIB June 2006
pccPcedpCapPathScopePrefInterArea OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the level of preference of the option of computation
'R' compared to other computation options:
A value of 7 reflects the highest preference.
When the value of PccPcedpCapCompInterArea is 'false' then
this objet MUST be to '0'."
::= { pccPcedpCapPathScopeEntry 8}
pccPcedpCapPathScopePrefInterAS OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the level of preference of the option of computation
'S' compared to other computation options:
A value of 7 reflects the highest preference.
When the value of PccPcedpCapCompInterAS is 'false' then
this objet MUST be to '0'."
::= { pccPcedpCapPathScopeEntry 9}
pccPcedpCapPathScopePrefInterLayer OBJECT-TYPE
SYNTAX Integer32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the level of preference of the option of computation
'Y' compared to other computation options:
A value of 7 reflects the highest preference.
When the value of PccPcedpCapCompInterLayer is 'false' then
this objet MUST be to '0'."
::= { pccPcedpCapPathScopeEntry 10}
--
-- PCE-DOMAINS information elements
--
pccPcedpCapDomainTable OBJECT-TYPE
SYNTAX SEQUENCE OF PccPcedpCapDomainEntry
MAX-ACCESS not-accessible
STATUS current
Stephan Expires December 27, 2006 [Page 15]
Internet-Draft PCC PCEDP MIB June 2006
DESCRIPTION
"Information describing the set of domains where the PCE has
topology visibility and can compute paths."
::= { pccPcedpCapabilityObjects 2 }
pccPcedpCapDomainEntry OBJECT-TYPE
SYNTAX PccPcedpCapDomainEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the domains of each PCE discovered by
the PCC."
INDEX { pccPcedpDiscPceIndex, pccPcedpCapDomainIndex }
::= { pccPcedpCapDomainTable 1 }
PccPcedpCapDomainEntry ::= SEQUENCE {
pccPcedpCapDomainIndex Integer32,
pccPcedpCapDomainIDType AddressFamilyNumbers,
pccPcedpCapDomainID PccPceDpRoutingDomainID
}
pccPcedpCapDomainIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object identifies locally a domain for which the PCE
identified by pccPcedpDiscPceIndex has topology visibility and
can compute paths."
::= { pccPcedpCapDomainEntry 1 }
pccPcedpCapDomainIDType OBJECT-TYPE
SYNTAX AddressFamilyNumbers
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the type of the domainID of a PCE-
DOMAIN SUB TLV.
Acceptable types are :
ipV4(1) and ipV6(2) for an OSPF area ID;
nsap(3) for and ISIS area ID;
asNumber(18) for an BGP AS number"
::= { pccPcedpCapDomainEntry 2 }
pccPcedpCapDomainID OBJECT-TYPE
SYNTAX PccPceDpRoutingDomainID
Stephan Expires December 27, 2006 [Page 16]
Internet-Draft PCC PCEDP MIB June 2006
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ID (area,AS) of the routing domain for which this entry
contains information."
::= { pccPcedpCapDomainEntry 3 }
--
-- PCE-DEST-DOMAINS information elements
--
pccPcedpCapDestDomainTable OBJECT-TYPE
SYNTAX SEQUENCE OF PccPcedpCapDestDomainEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the set of destination domains toward
which a PCE can compute path."
::= { pccPcedpCapabilityObjects 3 }
pccPcedpCapDestDomainEntry OBJECT-TYPE
SYNTAX PccPcedpCapDestDomainEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information describing the destination domains of each PCE."
INDEX { pccPcedpDiscPceIndex, pccPcedpCapDestDomainIndex }
::= { pccPcedpCapDestDomainTable 1 }
PccPcedpCapDestDomainEntry ::= SEQUENCE {
pccPcedpCapDestDomainIndex Integer32,
pccPcedpCapDestDomainIDType AddressFamilyNumbers,
pccPcedpCapDestDomainID PccPceDpRoutingDomainID
}
pccPcedpCapDestDomainIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object identifies locally a destination domain toward
which a PCE identified by pccPcedpDiscPceIndex can compute
path."
::= { pccPcedpCapDestDomainEntry 1 }
pccPcedpCapDestDomainIDType OBJECT-TYPE
Stephan Expires December 27, 2006 [Page 17]
Internet-Draft PCC PCEDP MIB June 2006
SYNTAX AddressFamilyNumbers
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the type of the routing domain.
Acceptable types are :
ipV4(1) and ipV6(2) for an OSPF area ID;
nsap(3) for and ISIS area ID;
asNumber(18) for an BGP AS number"
::= { pccPcedpCapDestDomainEntry 2 }
pccPcedpCapDestDomainID OBJECT-TYPE
SYNTAX PccPceDpRoutingDomainID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ID (area,AS) of the routing domain for which this entry
contains information."
::= { pccPcedpCapDestDomainEntry 3 }
-- PATH-COMP-CAP sub-TLV
-- TODO
-- CONGESTION sub-TLV
-- TODO
pccPcedpPceActivityGroup OBJECT IDENTIFIER ::= { pccPcedpMIBObjects 3
}
-- empty for now: TODO
--
-- PCC agents conformance statement
--
pccPcedpConformance OBJECT IDENTIFIER ::= { pccPcedpMIB 2 }
pccPcedpGroups OBJECT IDENTIFIER ::= { pccPcedpConformance 1 }
pccPcedpCompliances OBJECT IDENTIFIER ::= { pccPcedpConformance 2 }
-- PCC agent compliance statements
Stephan Expires December 27, 2006 [Page 18]
Internet-Draft PCC PCEDP MIB June 2006
pccPcedpGeneralPceInformation MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement only
general information monitoring as proposed in the 2nd S. of the
section 6.1 of [I-D.ietf-pce-discovery-reqs]."
MODULE
--
-- objets of pccPcedpDiscTable
-- objects of pccPcedpPathScopeTable
--
::= { pccPcedpCompliances 1 }
pccPcedpDetailledPceInformation MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMP entities that implement
detailled monitoring as proposed in the 3rd S. of the section 6.1
of [I-D.ietf-pce-discovery-reqs]."
MODULE
--
-- objets of pccPcedpDiscTable;
-- objects of pccPcedpDiscActTable;
-- objects of pccPcedpPathScopeTable;
-- objects of pccPcedpDomainTable;
-- objects of pccPcedpDestDomainTable
--
::= { pccPcedpCompliances 2 }
END
9. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
o on/off of discovery : Unauthorized changes to
pccPcedpDiscAdminStatus could result in a temporary interruption
of the discovery ;
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
Stephan Expires December 27, 2006 [Page 19]
Internet-Draft PCC PCEDP MIB June 2006
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o IP addresses of PCE.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
10. IANA Considerations
.
11. References
11.1. Normative References
[I-D.ietf-pce-disco-proto-igp]
Roux, J., "IGP protocol extensions for Path Computation
Element (PCE) Discovery",
draft-ietf-pce-disco-proto-igp-01 (work in progress),
March 2006.
[I-D.ietf-pce-discovery-reqs]
Roux, J., "Requirements for Path Computation Element (PCE)
Discovery", draft-ietf-pce-discovery-reqs-05 (work in
progress), June 2006.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Stephan Expires December 27, 2006 [Page 20]
Internet-Draft PCC PCEDP MIB June 2006
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
11.2. Informative References
[I-D.harrington-text-mib-doc-template]
Harrington, D., "A Template for Documents Containing a MIB
Module", draft-harrington-text-mib-doc-template-00 (work
in progress), June 2006.
[I-D.harrington-xml2rfc-mib-doc-template]
Harrington, D., "An XML2RFC Template for Documents
Containing a MIB Module",
draft-harrington-xml2rfc-mib-doc-template-00 (work in
progress), June 2006.
[I-D.ietf-pce-architecture]
Farrel, A., "A Path Computation Element (PCE) Based
Architecture", draft-ietf-pce-architecture-05 (work in
progress), April 2006.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
Appendix A. Open Issues
This list of open issues should be cleared and removed before this
Stephan Expires December 27, 2006 [Page 21]
Internet-Draft PCC PCEDP MIB June 2006
document hits the IESG.
Appendix B. Editing MIB module in XML
This section must be removed before this document hits the IESG.
This section is not related to PCE WG. It focuses on MIB document
editing, and XML editing of MIB module using xxe pluging and xml2rfc.
Prior to the edition of the document the author initiated a
discussion with the Rfc-editor regarding the way to write SMI
definition in XML. This discussion has 2 results:
1. This document use some material from "MIB Module Document Text
Template" [I-D.harrington-text-mib-doc-template].;
2. Regarding xml2rfc usage, currently MIB modules are writen in raw
text encapsulated in XML <figure> and <artwork> tokens. So the
editor must take care of all formating aspecs such as the length
of each line, bullet tabulation... This is against the spirit of
xml2rfc and of XML. So I writen this MIB module using XML <list>
tokens to let xml2rfc deals with the formating of the document.
The results are excellent:
1. The text version of this MIB module does not differ from a
mib module handcrafted;
2. smilint does not detect any difference;
3. The editong with xxe is user friendly;
3. Conclusion:
1. Writing MIB module in XML is the right direction.
2. MIB module editing will be very fast if we define a set of
XML templates for SMI objects definition. These definitions
should be added to"MIB Module Document Template"
[I-D.harrington-xml2rfc-mib-doc-template].
Following are some comments related to "MIB Module Document Text
Template" [I-D.harrington-text-mib-doc-template] :
1. It should help to determine which SNMP and SMI rfc are normative
or informative.
Stephan Expires December 27, 2006 [Page 22]
Internet-Draft PCC PCEDP MIB June 2006
Author's Address
Stephan Emile
France Telecom Division R&D
2 avenue Pierre Marzin
Lannion, F-22307
Fax: +33 2 96 05 18 52
Email: emile.stephan@francetelecom.com
Stephan Expires December 27, 2006 [Page 23]
Internet-Draft PCC PCEDP MIB June 2006
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Stephan Expires December 27, 2006 [Page 24]
