One document matched: draft-dhody-pce-pcep-pathkey-mib-08.xml
<?xml version="1.0" encoding="us-ascii"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[]>
<?rfc toc="yes" ?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="4"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="no"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc compact="yes" ?>
<?rfc iprnotified="Yes" ?>
<?rfc strict="no" ?>
<rfc ipr="trust200902" category="std" docName="draft-dhody-pce-pcep-pathkey-mib-08" obsoletes="" updates="" submissionType="IETF" xml:lang="en">
<front>
<title abbrev="PCEP PATHKEY MIB">Management Information Base (MIB) for
the PCE Communications Protocol (PCEP) for Path-Key based
Confidentiality in Inter-Domain Path Computation.</title>
<author initials="D" surname="Dhody" fullname="Dhruv Dhody">
<organization>Huawei Technology</organization>
<address>
<postal>
<street>Leela Palace</street>
<city>Bangalore</city>
<region>Karnataka</region>
<code>560008</code>
<country>INDIA</country>
</postal>
<email>dhruv.ietf@gmail.com</email>
</address>
</author>
<author initials="U" surname="Palle" fullname="Udayasree Palle">
<organization>Huawei Technology</organization>
<address>
<postal>
<street>Leela Palace</street>
<city>Bangalore</city>
<region>Karnataka</region>
<code>560008</code>
<country>INDIA</country>
</postal>
<email>udayasree.palle@huawei.com</email>
</address>
</author>
<author initials="Q" surname="Zhao" fullname="Quintin Zhao">
<organization>Huawei Technology</organization>
<address>
<postal>
<street>125 Nagog Technology Park</street>
<city>Acton</city>
<region>MA</region>
<code>01719</code>
<country>US</country>
</postal>
<email>quintin.zhao@huawei.com</email>
</address>
</author>
<author initials="D" surname="King" fullname="Daniel King">
<organization>Old Dog Consulting</organization>
<address>
<postal>
<street></street>
<city></city>
<region></region>
<code></code>
<country>UK</country>
</postal>
<email>daniel@olddog.co.uk</email>
</address>
</author>
<date month="August" year="2014" />
<area>Routing</area>
<workgroup>PCE Working Group</workgroup>
<abstract>
<t>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 managed objects for modeling of the Path
Computation Element communication Protocol (PCEP) for
communications between a Path Computation Client (PCC)
and a Path Computation Element (PCE), or between two PCEs
when path-key-based confidentiality in inter-domain path
computation is requested.</t>
</abstract>
</front>
<middle>
<section title="Introduction" toc="default">
<t>The Path Computation Element (PCE) defined in <xref target="RFC4655"/>
is an entity that is capable of computing a network path or route based
on a network graph, and applying computational constraints. A Path
Computation Client (PCC) may make requests to a PCE for paths to be
computed.</t>
<t>The PCE communication protocol (PCEP) is designed as a communication
protocol between PCCs and PCEs for path computations and is defined in
<xref target="RFC5440"/>.</t>
<t>If confidentiality is required between domains, Path-Key based
mechanism is described in <xref target="RFC5520"/>. For preserving the
confidentiality of the "Confidential Path Segment (CPS)"; the PCE returns
a path containing a loose hop in place of the segment that must be kept
confidential.</t>
<t><xref target="PCEP-MIB"/> defines a portion of the MIB for use with
network management protocols in the Internet community that can be used
to manage PCEP communications between a PCC and a PCE, or between two
PCEs. This memo describes MIB for path-key-based confidentiality in
inter-domain path computations.</t>
<section title="Requirements Language" toc="default">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref target="RFC2119"/>.</t>
</section>
</section>
<section title="Terminology" toc="default">
<t>This document uses the terminology defined in <xref target="RFC4655"/>,
<xref target="RFC5440"/> and <xref target="RFC5520"/>. The following
terminology is used in this document.</t>
<t>
<list style="hanging">
<t hangText="Domain:">Any collection of network elements within a
common sphere of address management or path computational
responsibility. Examples of domains include Interior Gateway
Protocol (IGP) areas and Autonomous Systems (ASs).</t>
<t hangText="IGP:">Interior Gateway Protocol. Either of the two
routing protocols, Open Shortest Path First (OSPF) or Intermediate
System to Intermediate System (IS-IS).</t>
</list>
</t>
</section>
<section title="The Internet-Standard Management Framework" toc="default">
<t>For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
<xref target="RFC3410"/>.</t>
<t>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 <xref target="RFC2578"/>
and STD 58, RFC 2580 <xref target="RFC2580"/>.</t>
</section>
<section title="PCEP Pathkey MIB Module Architecture" toc="default">
<t>The PCEP Pathkey MIB will contain the following information:</t>
<t>
<list style="symbols">
<t>PCEP Pathkey counters, timers and configurations</t>
<t>PCEP Pathkey table of Confidential Path Segment (CPS) related information.</t>
</list>
</t>
<t>The PCEP Pathkey MIB has no role when PCEP peer is PCC.</t>
<section title="Relations to other MIB modules" toc="default">
<t>The PCEP Pathkey MIB imports the following textual conventions from
the MPLS-TC-STD-MIB defined in <xref target="RFC3811"/>:</t>
<t>
<list style="symbols">
<t>MplsPathIndex</t>
<t>TeHopAddressType</t>
<t>TeHopAddress</t>
<t>TeHopAddressUnnum</t>
</list>
</t>
<t>The PCEP Pathkey MIB imports the following textual conventions
from the INET-ADDRESS-MIB defined in <xref target="RFC4001"/>:</t>
<t>
<list style="symbols">
<t>InetAddressType</t>
<t>InetAddress</t>
</list>
</t>
</section>
</section>
<section title="Example of the PCEP PathKey MIB module usage" toc="default">
<t>In this section we provide an example to showcase the relationship between
pcePcepPathKeyTable and pcePcepPathKeyHopTable described in
<xref target="SEC_OBJ_DEF"/>. While this example is not meant to
illustrate every permutation of the MIB, nor in its entirety, it is
intended as an aid to understand some of the key concepts. It is meant
to be read after going through the MIB itself.</t>
<t>
<figure>
<artwork><![CDATA[ pcePcepPathKeyTable of the PCEP-PATHKEY-MIB module:
{
pcePcepPathKey (4512),
pcePcepPathKeyCPSIndex (1),
pcePcepPathKeyReqSrcAddrType ipv4 (1),
pcePcepPathKeyReqSrcAddr (1.1.1.1),
pcePcepPathKeyRequestId (10),
pcePcepPathKeyRetrieved (1),
pcePcepPathKeyRtrAddrType ipv4 (1),
pcePcepPathKeyRtrAddr (2.2.2.2),
pcePcepPathKeyDiscardTime (10),
pcePcepPathKeyReuseTime (30)
}
Entries of pcePcepPathKeyHopTable of the PCEP-PATHKEY-MIB module:
{
pcePcepPathKeyHopListIndex 1,
pcePcepPathKeyHopIndex 1,
pcePcepPathKeyHopAddrType ipv4 (1),
pcePcepPathKeyHopIpAddr "192.168.100.1",
pcePcepPathKeyHopIpPrefixLen 32,
pcePcepPathKeyHopAddrUnnum 0,
}
{
pcePcepPathKeyHopListIndex 1,
pcePcepPathKeyHopIndex 2,
pcePcepPathKeyHopAddrType ipv4 (1),
pcePcepPathKeyHopIpAddr "192.168.100.2",
pcePcepPathKeyHopIpPrefixLen 32,
pcePcepPathKeyHopAddrUnnum 0
}]]></artwork>
</figure>
</t>
<t>The pcePcepPathKeyTable is the table for all the Path-Keys generated by
PCE. To access the CPS hidden by path-key pcePcepPathKey (4512), index
pcePcepPathKeyCPSIndex (1) is used in pcePcepPathKeyHopTable to find the
hop list (pcePcepPathKeyHopListIndex). To access each hop of the path another
index pcePcepPathKeyHopIndex is used along with pcePcepPathKeyHopListIndex.</t>
</section>
<section title="Object definitions" toc="default" anchor="SEC_OBJ_DEF">
<section title="PCEP-PATHKEY-MIB" toc="default">
<t>
<figure>
<artwork><![CDATA[PCEP-PATHKEY-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
mib-2,
NOTIFICATION-TYPE,
Unsigned32,
Counter32
FROM SNMPv2-SMI -- RFC 2578
TruthValue,
TimeStamp
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
MplsPathIndex,
TeHopAddressType,
TeHopAddress,
TeHopAddressUnnum
FROM MPLS-TC-STD-MIB -- RFC 3811
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001
]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathkeyMIB MODULE-IDENTITY
LAST-UPDATED
"201408051200Z" -- August 05, 2014
ORGANIZATION
"IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO
"Email: pce@ietf.org
WG charter
http://www.ietf.org/html.charters/pce-charter.html"
]]></artwork>
</figure>
</t>
<t>DESCRIPTION</t>
<t>"This MIB module defines a collection of objects for managing PCE communication protocol(PCEP) for Path-Key-Based Inter-Domain Path Computation"</t>
<t>Copyright (C) The IETF Trust (2014). This version of this
MIB module is part of RFC YYYY; see the RFC itself for full
legal notices.</t>
<t>
<figure>
<artwork><![CDATA[
-- RFC Ed,: replace YYYY with actual RFC number & remove
this note
-- Revision history
REVISION
"201408051200Z" -- 05 August 2014 12:00:00 EST
DESCRIPTION
"
Main Changes from -07 draft :
1. Editorial Changes."
REVISION
"201402061200Z" -- 06 February 2014 12:00:00 EST
DESCRIPTION
"
Main Changes from -06 draft :
1. Align to changes in base PCEP MIB."
REVISION
"201401031200Z" -- 03 January 2014 12:00:00 EST
DESCRIPTION
"
Main Changes from -05 draft :
1. Editorial Changes."
REVISION
"201307031200Z" -- 03 July 2013 12:00:00 EST
DESCRIPTION
"
Main Changes from -04 draft :
1. Aligment with the updates in PCEP-MIB draft
2. Editorial Changes."
REVISION
"201208171200Z" -- 17 Aug 2012 12:00:00 EST
DESCRIPTION
"
Main Changes from -03 draft :
1. Adding of DEFVAL for some objects.
2. Editorial Changes."
REVISION
"201202221200Z" -- 22 Feb 2012 12:00:00 EST
DESCRIPTION
"
Main Changes from -02 draft :
1. Editorial Changes.
2. Updated Contact Information."
REVISION
"201109051200Z" -- 05 Sept 2011 12:00:00 EST
DESCRIPTION
"
Main Changes from -01 draft :
1. Added pcePcepPathKeyCPSIndex.
2. Added pcePcepPathKeyHopListIndex.
3. Removed pcePcepPathKeyHopNum.
4. Updated Contact Information."
REVISION
"201103081200Z" -- 08 Mar 2011 12:00:00 EST
DESCRIPTION
"
Main Changes from -00 draft :
1. Added HopTable to store the CPS hops.
2. Added Path Key Creation Time."
REVISION
"201009171200Z" -- 17 Sep 2010 12:00:00 EST
DESCRIPTION
"Initial version, published as RFC YYYY."
-- RFC Ed.: replace YYYY with actual RFC number & remove
this note
::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove
this note
]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[
pcePcepPathKeyNotifications OBJECT IDENTIFIER ::=
{ pcePcepPathkeyMIB 0 }
pcePcepPathKeysObjects OBJECT IDENTIFIER ::=
{ pcePcepPathkeyMIB 1 }
pcePcepPathKeyConformance OBJECT IDENTIFIER ::=
{ pcePcepPathkeyMIB 2 }
pcePcepPathKeyObjects OBJECT IDENTIFIER ::=
{ pcePcepPathKeysObjects 1 }]]></artwork>
</figure>
</t>
<t> --</t>
<t> -- PCE Pathkey Objects</t>
<t> --</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyDiscardTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "minutes"
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value which indicates a period of time after the
expiration of which a PCE can discard unwanted
path-keys and CPS."
DEFVAL {10}
::= { pcePcepPathKeyObjects 1 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyReUseTimer OBJECT-TYPE
SYNTAX Unsigned32
UNITS "minutes"
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value which indicates a period of time which
should expire before an old path-key could be
reused for a new CPS."
DEFVAL {30}
::= { pcePcepPathKeyObjects 2 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyRetainStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-only
STATUS optional
DESCRIPTION
"The path-key retain status of this PCE to retain the
path-key and CPS after retrieval."
DEFVAL {disabled(2)}
::= { pcePcepPathKeyObjects 3 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeysGenerated OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of path-keys generated by this PCE."
::= { pcePcepPathKeyObjects 4 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandUn OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of attempts to expand an unknown
path-key."
::= { pcePcepPathKeyObjects 5 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandExp OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of attempts to expand an expired
path-key."
::= { pcePcepPathKeyObjects 6 }
]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandSame OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS optional
DESCRIPTION
"The number of attempts to expand the same
path-key."
::= { pcePcepPathKeyObjects 7 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpNoExpansion OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS optional
DESCRIPTION
"The number of path-keys expired without any attempt
to expand it."
::= { pcePcepPathKeyObjects 8 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpansionSuccess OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS optional
DESCRIPTION
"The number of path-key expansion requests (PCReq)
which had successful retrieval."
::= { pcePcepPathKeyObjects 9 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpansionFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS optional
DESCRIPTION
"The number of path-key expansion requests (PCReq)
which had failed retrieval."
::= { pcePcepPathKeyObjects 10 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyConfig OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"Path-key based confidentiality is enabled."
DEFVAL {disabled(2)}
::= { pcePcepPathKeyObjects 11 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyTable OBJECT-TYPE
SYNTAX SEQUENCE OF pcePcepPathKeyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the
Pathkey CPS of PCE. Applicable only when
pcePcepPathKeyConfig is enabled(1)."
::= { pcePcepPathKeyObjects 12 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyEntry OBJECT-TYPE
SYNTAX pcePcepPathKeyEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Represents a path-key and CPS entry. An entry is
only created when a path-key is
generated by PCE during inter-domain path
computation."
INDEX { pcePcepPathKey }
::= { pcePcepPathKeyTable 1 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyEntry ::= SEQUENCE {
pcePcepPathKey Unsigned32,
pcePcepPathKeyCPSIndex MplsPathIndex,
pcePcepPathKeyReqSrcAddrType InetAddressType,
pcePcepPathKeyReqSrcAddr InetAddress,
pcePcepPathKeyRequestId Unsigned32,
pcePcepPathKeyRetrieved INTEGER,
pcePcepPathKeyRtrAddrType InetAddressType,
pcePcepPathKeyRtrAddr InetAddress,
pcePcepPathKeyCreationTime TimeStamp,
pcePcepPathKeyDiscardTime Unsigned32,
pcePcepPathKeyReuseTime Unsigned32,
}]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKey OBJECT-TYPE
SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The path-key value to identify a CPS."
::= { pcePcepPathKeyEntry 1 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyCPSIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The HopList index of the CPS. This index
is used to expand Hops in
pcePcepPathKeyHopTable."
::= { pcePcepPathKeyEntry 2 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyReqSrcAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of the PCEP peer Internet address.
This object specifies how the value of the
pcePcepPathKeyReqSrcAddr object should be
interpreted."
::= { pcePcepPathKeyEntry 3 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyReqSrcAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Internet address of the PCEP peer that
issued the original request that led to the
creation of the path-key.
The type is given by
pcePcepPathKeyReqSrcAddrType "
::= { pcePcepPathKeyEntry 4 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyRequestId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The request ID of the original PCReq that led
to the creation of the path-key."
::= { pcePcepPathKeyEntry 5 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyRetrieved OBJECT-TYPE
SYNTAX INTEGER {
TRUE(1),
FALSE(2)
}
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"It specifies whether the path-key is retrieved
or not."
::= { pcePcepPathKeyEntry 6 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyRtrAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The type of the PCEP peer Internet address.
This object specifies how the value of the
pcePcepPathKeyRtrAddr object should be
interpreted. Applicable only when
pcePcepPathKeyRetrieved is TRUE(1)."
::= { pcePcepPathKeyEntry 7 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyRtrAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Internet address of the PCEP peer that
issued the path-key expansion or retrieval.
Applicable only when pcePcepPathKeyRetrieved
is TRUE(1). The type is given by
pcePcepPathKeyRtrAddrType."
::= { pcePcepPathKeyEntry 8 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyCreationTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of sysUpTime at which Path Key
was generated by PCE."
::= { pcePcepPathKeyEntry 9 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyDiscardTime OBJECT-TYPE
SYNTAX Unsigned32
UNIT "seconds"
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time after which the path segment associated
with the path-key will be discarded."
::= { pcePcepPathKeyEntry 10 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyReuseTime OBJECT-TYPE
SYNTAX Unsigned32
UNIT "seconds"
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time after which the path-key will be available
for re-use."
::= { pcePcepPathKeyEntry 11 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF pcePcepPathKeyHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about the
Pathkey Hop in the CPS of PCE."
::= { pcePcepPathKeyObjects 12 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopEntry OBJECT-TYPE
SYNTAX pcePcepPathKeyHopEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table represents a Hop in the CPS.
An entry is only created when a path-key generated
by PCE during inter-domain computation."
INDEX { pcePcepPathKeyHopListIndex,
pcePcepPathKeyHopIndex }
::= { pcePcepPathKeyHopTable 1 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopEntry ::= SEQUENCE {
pcePcepPathKeyHopListIndex MplsPathIndex,
pcePcepPathKeyHopIndex MplsPathIndex,
pcePcepPathKeyHopAddrType TeHopAddressType,
pcePcepPathKeyHopIpAddr TeHopAddress,
pcePcepPathKeyHopIpPrefixLen InetAddressPrefixLength,
pcePcepPathKeyHopAddrUnnum TeHopAddressUnnum,
} ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopListIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The primary index into pcePcepPathKeyHopEntry table
identifying a particular CPS. All hops in the CPS
will have the same ListIndex. This corresponds to
pcePcepPathKeyCPSIndex in pcePcepPathKeyEntry."
::= { pcePcepPathKeyHopEntry 1 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopIndex OBJECT-TYPE
SYNTAX MplsPathIndex
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The secondry index into pcePcepPathKeyHopEntry
table identifying a particular Hop in the CPS."
::= { pcePcepPathKeyHopEntry 2 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopAddrType OBJECT-TYPE
SYNTAX TeHopAddressType
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Hop Address Type of this CPS hop. Only
ipv4(1), ipv6(2) and unnum(4) are allowed."
DEFVAL { ipv4 }
::= { pcePcepPathKeyHopEntry 3 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopIpAddr OBJECT-TYPE
SYNTAX TeHopAddress
MAX-ACCESS read-only
STATUS mandatory
DESCRIPTION
"The Hop Address for this CPS hop.
The type of this address is determined by the
value of the corresponding
pcePcepPathKeyHopAddrType."
DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0
::= { pcePcepPathKeyHopEntry 4 } ]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopIpPrefixLen OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"pcePcepPathKeyHopAddrType if set to ipv4(1) or
ipv6(2), then this value will contain an
appropriate prefix length for the IP address in
object pcePcepPathKeyHopIpAddr. Otherwise this
value is irrelevant and should be ignored."
DEFVAL { 32 }
::= { pcePcepPathKeyHopEntry 5 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyHopAddrUnnum OBJECT-TYPE
SYNTAX TeHopAddressUnnum
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If pcePcepPathKeyHopAddrType is set to unnum(4),
then this value will contain the interface
identifier of the unnumbered interface for this
hop. This object should be used in conjunction
with pcePcepPathKeyHopIpAddr which would contain
the LSR Router ID in this case."
::= { pcePcepPathKeyHopEntry 6 }]]></artwork>
</figure>
</t>
<t>---</t>
<t>--- Notifications</t>
<t>---</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandUnNtf NOTIFICATION-TYPE
OBJECTS {
pcePcepPathKeyExpandUn
}
STATUS mandatory
DESCRIPTION
"This notification is sent when an attempt to expand
an unknown path-key is made. The value of the
counter pcePcepPathKeyExpandUn is also increased at
this time."
::= { pcePcepPathKeyNotifications 1 }
]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandExpNtf NOTIFICATION-TYPE
OBJECTS {
pcePcepPathKeyExpandExp
}
STATUS mandatory
DESCRIPTION
"This notification is sent when an attempt to expand
an expired path-key is made. The value of the
counter pcePcepPathKeyExpandExp is also increased
at this time."
::= { pcePcepPathKeyNotifications 2 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpandSameNtf NOTIFICATION-TYPE
OBJECTS {
pcePcepPathKeyExpandSame
}
STATUS optional
DESCRIPTION
"This notification is sent when a duplicate attempt
to expand the same path-key is made. The value of
the counter pcePcepPathKeyExpandSame is also
increased at this time."
::= { pcePcepPathKeyNotifications 3 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyExpNoExpansionNtf NOTIFICATION-TYPE
OBJECTS {
pcePcepPathKeyExpNoExpansion
}
STATUS optional
DESCRIPTION
"This notification is sent when path-key expires
without any attempt to expand it. The value of
the counter pcePcepPathKeyExpNoExpansion is also
increased at this time."
::= { pcePcepPathKeyNotifications 4 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[
--****************************************************************
-- Module Conformance Statement
--****************************************************************
pcePcepPathKeyGroups
OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 1 }
pcePcepPathKeyCompliances
OBJECT IDENTIFIER ::= { pcePcepPathKeyConformance 2 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[--
-- Read-Only Compliance
--]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The Module is implemented with support
for read-only. In other words, only monitoring
is available by implementing this
MODULE-COMPLIANCE."
MODULE -- this module
MANDATORY-GROUPS
{ pcePcepPathKeyGeneralGroup,
pcePcepPathKeyNotificationsGroup
}
::= { pcePcepPathKeyCompliances 1 }]]></artwork>
</figure>
</t>
<t>-- units of conformance</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyGeneralGroup OBJECT-GROUP
OBJECTS {
pcePcepPathKeyDiscardTimer,
pcePcepPathKeyReUseTimer,
pcePcepPathKeysGenerated,
pcePcepPathKeyExpandUn,
pcePcepPathKeyExpandExp,
pcePcepPathKeyConfig,
pcePcepPathKey,
pcePcepPathKeyCPSIndex,
pcePcepPathKeyReqSrcAddrType,
pcePcepPathKeyReqSrcAddr,
pcePcepPathKeyRequestId,
pcePcepPathKeyRetrieved,
pcePcepPathKeyRtrAddrType,
pcePcepPathKeyRtrAddr,
pcePcepPathKeyCreationTime,
pcePcepPathKeyDiscardTime,
pcePcepPathKeyReuseTime,
pcePcepPathKeyHopListIndex,
pcePcepPathKeyHopIndex,
pcePcepPathKeyHopAddrType,
pcePcepPathKeyHopIpAddr,
pcePcepPathKeyHopIpPrefixLen,
pcePcepPathKeyHopAddrUnnum,
}
STATUS current
DESCRIPTION
"Objects that apply to all PCEP Pathkey MIB
implementations."
::= { pcePcepPathKeyGroups 1 }]]></artwork>
</figure>
</t>
<t>
<figure>
<artwork><![CDATA[pcePcepPathKeyNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { pcePcepPathKeyExpandUnNtf,
pcePcepPathKeyExpandExpNtf
}
STATUS current
DESCRIPTION
"The notifications for a PCEP Pathkey MIB
implementation."
::= { pcePcepPathKeyGroups 2 }
END]]></artwork>
</figure>
</t>
</section>
</section>
<section title="IANA Considerations" toc="default">
<t>
The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
</t>
<figure>
<artwork><![CDATA[
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pcePcepPathkeyMIB { mib-2 XXX }
]]></artwork>
</figure>
<t>
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree
and to record the assignment in the SMI Numbers registry. When
the assignment has been made, the RFC Editor is asked to replace
"XXX" (here and in the MIB module) with the assigned value and to
remove this note.
</t>
</section>
<section title="Security Considerations" toc="default">
<t><xref target="PCEP-MIB"/> describes the security consideration related
to the PCE MIB module, which are applicable to PCE Path-Key MIB defined in
this document. Further <xref target="RFC5520"/> describes various security
consideration when dealing with Path-Key. Since this MIB contains confidential
path segment, care should be taken to maintain the confidentiality during
SNMP MIB operations.</t>
<t>Security features described by the SNMPv3 framework
<xref target="RFC3410"/> like User-based Security Model (USM)
<xref target="RFC3414"/> with the AES cipher algorithm
<xref target="RFC3826"/> and Transport Security Model (TSM)
<xref target="RFC5591"/> in combination with a secure transport
such as SSH <xref target="RFC5592"/> or TLS/DTLS
<xref target="RFC6353"/>. should be supported.</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119.xml" ?>
<?rfc include="reference.RFC.2578.xml" ?>
<?rfc include="reference.RFC.2579.xml" ?>
<?rfc include="reference.RFC.2580.xml" ?>
<?rfc include="reference.RFC.2863.xml" ?>
<?rfc include="reference.RFC.3411.xml" ?>
<?rfc include="reference.RFC.3811.xml" ?>
<?rfc include="reference.RFC.3813.xml" ?>
<?rfc include="reference.RFC.4001.xml" ?>
<?rfc include="reference.RFC.5440.xml" ?>
<!--PCEP-MIB-->
<reference anchor="PCEP-MIB">
<front>
<title>
Path Computation Element Protocol (PCEP) Management Information Base
</title>
<author initials="K" surname="Koushik" fullname="Kiran Koushik">
<organization/>
</author>
<author initials="S" surname="Emile" fullname="Stephan Emile">
<organization/>
</author>
<author initials="Q" surname="Zhao" fullname="Quintin Zhao">
<organization/>
</author>
<author initials="D" surname="King" fullname="Daniel King">
<organization/>
</author>
<author initials="J" surname="Hardwick" fullname="Jonathan Hardwick">
<organization/>
</author>
<date month="July" day="25" year="2014"/>
<abstract>
<t>
This memo defines a portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Path Computation Element communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between two PCEs.
</t>
</abstract>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-pce-pcep-mib-09"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-mib-09.txt"/>
</reference>
</references>
<references title="Informative References">
<?rfc include="reference.RFC.3410.xml" ?>
<?rfc include="reference.RFC.3414.xml" ?>
<?rfc include="reference.RFC.3826.xml" ?>
<?rfc include="reference.RFC.4655.xml" ?>
<?rfc include="reference.RFC.5520.xml" ?>
<?rfc include="reference.RFC.5591.xml" ?>
<?rfc include="reference.RFC.5592.xml" ?>
<?rfc include="reference.RFC.6353.xml" ?>
</references>
</back>
</rfc>| PAFTECH AB 2003-2026 | 2026-04-24 02:41:57 |