netconfcentral logo

Typedefs

access-control-mode

Summary

Name access-control-mode
Type enumeration

Details

Module yumaworks-types
Version 2015-10-04
Source yumaworks-types line 211

access-modes

Summary

Name access-modes
Type enumeration
  
 
This defines NTP acess modes.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 118

access-operations-type

Summary

Name access-operations-type
Type bits
  
 
NETCONF Access Operation.

Details

Module ietf-netconf-acm
Version 2012-02-22
Source ietf-netconf-acm line 112

access-operations-type

Summary

Name access-operations-type
Type bits
  
 
Access Operation.

Details

Module ietf-netconf-acm
Version 2017-12-11
Source ietf-netconf-acm line 119

acl-ref

Summary

Name acl-ref
Type leafref
  
 
This type is used by data models that
need to referenced an acl

Details

Module ietf-acl
Version 2014-10-10
Source ietf-acl line 74

acl-ref

Summary

Name acl-ref
Type leafref
  
 
This type is used by data models that need to reference an
Access Control List

Details

Module ietf-access-control-list
Version 2017-10-03
Source ietf-access-control-list line 268

acl-type

Summary

Name acl-type
Type identityref
  
 
This type is used to refer to an Access Control List
(ACL) type

Details

Module ietf-acl
Version 2014-10-10
Source ietf-acl line 65

acl-type

Summary

Name acl-type
Type identityref
  
 
This type is used to refer to an Access Control List
(ACL) type

Details

Module ietf-access-control-list
Version 2017-10-03
Source ietf-access-control-list line 259

action-type

Summary

Name action-type
Type enumeration
  
 
Action taken by the server when a particular
rule matches.

Details

Module ietf-netconf-acm
Version 2012-02-22
Source ietf-netconf-acm line 152

action-type

Summary

Name action-type
Type enumeration
  
 
Action taken by the server when a particular
rule matches.

Details

Module ietf-netconf-acm
Version 2017-12-11
Source ietf-netconf-acm line 159

active-channel-t

Summary

Name active-channel-t
Type union
  
 
Number of channels active on a span - and on an amplifier

Details

Module ietf-opt-parameters-wdm
Version 2016-10-30
Source ietf-opt-parameters-wdm line 65

active-type

Summary

Name active-type
Type enumeration
  
 
active-type

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 271

adaptive-timer-type

Summary

Name adaptive-timer-type
Type enumeration
  
 
This type defines ISIS adaptive timer types

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 173

address-attribute-type

Summary

Name address-attribute-type
Type identityref
  
 
Target address attribute type.

Details

Module ietf-connectionless-oam
Version 2017-09-06
Source ietf-connectionless-oam line 113

address-family

Summary

Name address-family
Type enumeration
  
 
Defines a type for the address family.

Details

Module ietf-l3vpn-svc
Version 2017-12-04
Source ietf-l3vpn-svc line 140

address-family

Summary

Name address-family
Type enumeration
  
 
Enumeration containing all the IANA
 defined address families.

Details

Module iana-routing-types
Version 2017-09-19
Source iana-routing-types line 43

address-family

Summary

Name address-family
Type enumeration
  
 
Defines a type for the address family.

Details

Module ietf-l3vpn-svc
Version 2017-01-27
Source ietf-l3vpn-svc line 137

address-family-type

Summary

Name address-family-type
Type enumeration
  
 
Typedef for address family type.

Details

Module ietf-vbras
Version 2017-04-13
Source ietf-vbras line 57

address-family-type

Summary

Name address-family-type
Type enumeration
  
 
Typedef for address family type.

Details

Module ietf-vbng
Version 2017-07-16
Source ietf-vbng line 57

address-pool-type

Summary

Name address-pool-type
Type enumeration
  
 
Address pool type.

Details

Module ietf-address-pool
Version 2015-10-14
Source ietf-address-pool line 63

adj-state-type

Summary

Name adj-state-type
Type enumeration
  
 
This type defines states of an adjacency

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 286

adjid

Summary

Name adjid
Type uint32
  
 
The type for adjacency ID.

Details

Module ietf-bier-te
Version 2017-10-23
Source ietf-bier-te line 159

admin-group

Summary

Name admin-group
Type binary
  
 
Administrative group/Resource class/Color.

Details

Module ietf-te-types
Version 2017-10-29
Source ietf-te-types line 1317

admin-groups

Summary

Name admin-groups
Type union
  
 
TE administrative group derived type

Details

Module ietf-te-types
Version 2017-10-29
Source ietf-te-types line 1331

admin-state

Summary

Name admin-state
Type enumeration
  
 
Represents the various possible administrative states.

Details

Module ietf-hardware
Version 2017-03-07
Reference RFC 4268: EntityAdminState
Source ietf-hardware line 102

admin-state

Summary

Name admin-state
Type enumeration
  
 
admin state of the oam function on an interface

Details

Module ieee802-ethernet-link-oam
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.6.1.2 and 30.3.6.2
Source ieee802-ethernet-link-oam line 292

admin-state

Summary

Name admin-state
Type enumeration
  
 
Represents the various possible administrative states.

Details

Module ietf-hardware
Version 2017-12-18
Reference RFC 4268: EntityAdminState
Source ietf-hardware line 93

admin-state-type

Summary

Name admin-state-type
Type enumeration
  
 
Administrative state modes for
logical channels in the transponder model.

Details

Module openconfig-transport-types
Version 2017-08-16
Source openconfig-transport-types line 47

admin-string

Summary

Name admin-string
Type string
  
 
Represents SnmpAdminString as defined in RFC 3411.

Note that the size of an SnmpAdminString is measured in
octets, not characters.

Details

Module ietf-snmp
Submodule ietf-snmp-common
Version 2014-12-10
Reference RFC 3411: An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks. SNMP-FRAMEWORK-MIB.SnmpAdminString
Source ietf-snmp-common line 55

advertised-received

Summary

Name advertised-received
Type enumeration
  
 
Received or advertised.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 99

Aggregate-Max-DL-Bit-Rate-Value

Summary

Name Aggregate-Max-DL-Bit-Rate-Value
Type uint32
  
 
The aggregate maximum downlink bit rate that is
requested/allocated for downlink IP flows.  The measurement
units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 371

Aggregate-Max-UL-Bit-Rate-Value

Summary

Name Aggregate-Max-UL-Bit-Rate-Value
Type uint32
  
 
The aggregate maximum downlink bit rate that is
requested/allocated for downlink IP flows.  The measurement
units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 379

aggregation-type

Summary

Name aggregation-type
Type enumeration
  
 
Type to define the lag-type, i.e., how the LAG is
defined and managed

Details

Module openconfig-if-aggregate
Version 2017-12-21
Source openconfig-if-aggregate line 58

ais-interval

Summary

Name ais-interval
Type enumeration
  
 
ais-interval

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 104

alarm-state

Summary

Name alarm-state
Type bits
  
 
Represents the possible values of alarm states.  An alarm is a
persistent indication of an error or warning condition.

When no bits of this attribute are set, then no active alarms
are known against this component and it is not under repair.

Details

Module ietf-hardware
Version 2017-03-07
Reference RFC 4268: EntityAlarmStatus
Source ietf-hardware line 191

alarm-state

Summary

Name alarm-state
Type bits
  
 
Represents the possible values of alarm states.  An alarm is a
persistent indication of an error or warning condition.

When no bits of this attribute are set, then no active alarms
are known against this component and it is not under repair.

Details

Module ietf-hardware
Version 2017-12-18
Reference RFC 4268: EntityAlarmStatus
Source ietf-hardware line 182

alarm-text

Summary

Name alarm-text
Type string
  
 
The string used to inform operators about the alarm.  This
MUST contain enough information for an operator to be able
to understand the problem and how to resolve it.  If this
string contains structure, this format should be clearly
documented for programs to be able to parse that
information.

Details

Module ietf-alarms
Version 2017-10-30
Source ietf-alarms line 177

alarm-type-id

Summary

Name alarm-type-id
Type identityref
  
 
Identifies an alarm type.  The description of the alarm type
id MUST indicate if the alarm type is abstract or not.  An
abstract alarm type is used as a base for other alarm type ids
and will not be used as a value for an alarm or be present in
the alarm inventory.

Details

Module ietf-alarms
Version 2017-10-30
Source ietf-alarms line 308

alarm-type-qualifier

Summary

Name alarm-type-qualifier
Type string
  
 
If an alarm type can not be fully specified at design time by
alarm-type-id, this string qualifier is used in addition to
fully define a unique alarm type.

The definition of alarm qualifiers is considered being part
of the instrumentation and out of scope for this module.
An empty string is used when this is part of a key.

Details

Module ietf-alarms
Version 2017-10-30
Source ietf-alarms line 320

all-action

Summary

Name all-action
Type enumeration
  
 
This is used for protocol

Details

Module ietf-i2nsf-monitoring-information
Version 2017-07-19
Source ietf-i2nsf-monitoring-information line 56

all-action

Summary

Name all-action
Type enumeration
  
 
This is used for protocol

Details

Module ietf-i2nsf-nsf-monitoring-dm
Version 2017-10-29
Source ietf-i2nsf-nsf-monitoring-dm line 55

allocate-type

Summary

Name allocate-type
Type enumeration
  
 
Mechanisms for IP address allocation

Details

Module ietf-dhcp
Version 2017-03-02
Source ietf-dhcp line 45

AltNameMode

Summary

Name AltNameMode
Type boolean
  
 
Defines the alternate name search mode that
should be used when resolving YANG node names
in leafs or leaflists using the UrlPath data type.

If 'true' then nodes with an 'alt-name' defined
will be considered a match if the YANG name or the
alternative name matches the search string.

If 'false' then only the YANG node name will
be used in node name searches.

Details

Module yumaworks-types
Version 2015-10-04
Source yumaworks-types line 101

anyURI

Summary

Name anyURI
Type string
  
 
XSD universal resource identifier string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI
Source yuma-xsd line 345

area-address

Summary

Name area-address
Type string
  
 
This type defines the ISIS area address.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 296

area-address

Summary

Name area-address
Type string
  
 
This type defines the area address format.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 347

as-number

Summary

Name as-number
Type uint32
  
 
A numeric identifier for an autonomous system (AS). An AS is a
single domain, under common administrative control, which forms
a unit of routing policy. Autonomous systems can be assigned a
2-byte identifier, or a 4-byte identifier which may have public
or private scope. Private ASNs are assigned from dedicated
ranges. Public ASNs are assigned from ranges allocated by IANA
to the regional internet registries (RIRs).

Details

Module openconfig-inet-types
Version 2017-08-24
Reference RFC 1930 Guidelines for creation, selection, and registration of an Autonomous System (AS) RFC 4271 A Border Gateway Protocol 4 (BGP-4)
Source openconfig-inet-types line 263

as-number

Summary

Name as-number
Type uint32
  
 
The as-number type represents autonomous system numbers
which identify an Autonomous System (AS).  An AS is a set
of routers under a single technical administration, using
an interior gateway protocol and common metrics to route
packets within the AS, and using an exterior gateway
protocol to route packets to other ASs'.  IANA maintains
the AS number space and has delegated large parts to the
regional registries.

Autonomous system numbers were originally limited to 16
bits.  BGP extensions have enlarged the autonomous system
number space to 32 bits.  This type therefore uses an uint32
base type without a range restriction in order to support
a larger autonomous system number space.

In the value set and its semantics, this type is equivalent
to the InetAutonomousSystemNumber textual convention of
the SMIv2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System (AS) RFC 4271: A Border Gateway Protocol 4 (BGP-4) RFC 4893: BGP Support for Four-octet AS Number Space RFC 4001: Textual Conventions for Internet Network Addresses
Source ietf-inet-types line 139

as-number

Summary

Name as-number
Type uint32
  
 
The as-number type represents autonomous system numbers
which identify an Autonomous System (AS).  An AS is a set
of routers under a single technical administration, using
an interior gateway protocol and common metrics to route
packets within the AS, and using an exterior gateway
protocol to route packets to other ASes.  IANA maintains
the AS number space and has delegated large parts to the
regional registries.

Autonomous system numbers were originally limited to 16
bits.  BGP extensions have enlarged the autonomous system
number space to 32 bits.  This type therefore uses an uint32
base type without a range restriction in order to support
a larger autonomous system number space.

In the value set and its semantics, this type is equivalent
to the InetAutonomousSystemNumber textual convention of
the SMIv2.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System (AS) RFC 4271: A Border Gateway Protocol 4 (BGP-4) RFC 4001: Textual Conventions for Internet Network Addresses RFC 6793: BGP Support for Four-Octet Autonomous System (AS) Number Space
Source ietf-inet-types line 147

as-number

Summary

Name as-number
Type uint32
  
 
A numeric identifier for an autonomous system (AS). An AS is a
single domain, under common administrative control, which forms
a unit of routing policy. Autonomous systems can be assigned a
2-byte identifier, or a 4-byte identifier which may have public
or private scope. Private ASNs are assigned from dedicated
ranges. Public ASNs are assigned from ranges allocated by IANA
to the regional internet registries (RIRs).

Details

Module openconfig-inet-types
Version 2017-01-26
Reference RFC 1930 Guidelines for creation, selection, and registration of an Autonomous System (AS) RFC 4271 A Border Gateway Protocol 4 (BGP-4)
Source openconfig-inet-types line 110

as-path-segment-type

Summary

Name as-path-segment-type
Type enumeration
  
 
Defines the types of BGP AS path segments.

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 526

assoc-type

Summary

Name assoc-type
Type enumeration
  
 
The PCEP Association Type

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 427

association-modes

Summary

Name association-modes
Type enumeration
  
 
This defines NTP association modes.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 177

attenuator-t

Summary

Name attenuator-t
Type decimal64
  
 
Attenuation value (attenuator) applied after the Amplifier

Details

Module ietf-opt-parameters-wdm
Version 2016-10-30
Source ietf-opt-parameters-wdm line 84

auth-key-type

Summary

Name auth-key-type
Type enumeration
  
 
Enumeration of the authentication mechanisms supported by
LISP.

Details

Module ietf-lisp
Version 2017-07-01
Reference https://tools.ietf.org/html/rfc6830#section-6.1.6
Source ietf-lisp line 124

auth-method-type

Summary

Name auth-method-type
Type enumeration
  
 
Peer authentication method

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 239

auth-protocol-type

Summary

Name auth-protocol-type
Type enumeration
  
 
Peer authentication protocols

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 122

auth-type

Summary

Name auth-type
Type enumeration
  
 
BFD authentication type as defined in RFC5880. Range is 0 to
255.

Details

Module iana-bfd-types
Version 2017-10-30
Source iana-bfd-types line 90

auxiliary-id

Summary

Name auxiliary-id
Type uint8
  
 
A Controller may have multiple auxiliary connections as
specified by the Openflow protocol. The main Controller
connection should always have the auxiliary-id set to zero.
All other connections must have an auxiliary-id different
from 0.

Details

Module openconfig-openflow-types
Version 2017-08-24
Source openconfig-openflow-types line 70

bandwidth-gbps

Summary

Name bandwidth-gbps
Type uint64
  
 
Bandwidth values expressed in gigabits per second

Details

Module openconfig-mpls-types
Version 2017-08-24
Source openconfig-mpls-types line 375

bandwidth-gbps

Summary

Name bandwidth-gbps
Type uint64
  
 
Bandwidth values expressed in gigabits per second

Details

Module ietf-te-mpls-types
Version 2017-10-29
Source ietf-te-mpls-types line 79

bandwidth-ieee-float32

Summary

Name bandwidth-ieee-float32
Type string
  
 
Bandwidth in IEEE 754 floating point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits, and Fraction uses 23 bits.
The units are octets per second.
The encoding format is the external hexadecimal-significant
character sequences specified in IEEE 754 and C99. The
format is restricted to be normalized, non-negative, and
non-fraction: 0x1.hhhhhhp{+}d, 0X1.HHHHHHP{+}D, or 0x0p0,
where 'h' and 'H' are hexadecimal digits and'd' and 'D' are
integers in the range of [0..127].
When six hexadecimal digits are used for 'hhhhhh' or
'HHHHHH', the least significant digit must be an even
number. 'x' and 'X' indicate hexadecimal; 'p' and 'P'
indicate power of two. Some examples are: 0x0p0, 0x1p10, and
0x1.abcde2p+20

Details

Module ietf-routing-types
Version 2017-10-13
Reference IEEE Std 754-2008: IEEE Standard for Floating-Point Arithmetic.
Source ietf-routing-types line 484

bandwidth-ieee-float32

Summary

Name bandwidth-ieee-float32
Type string
  
 
Bandwidth in IEEE 754 floating point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits, and Fraction uses 23 bits.
The units are octets per second.
The encoding format is the external hexadecimal-significand
character sequences specified in IEEE 754 and C99,
restricted to be normalized, non-negative, and non-fraction:
0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D
where 'h' and 'H' are hexadecimal digits, 'd' and 'D' are
integers in the range of [0..127].
When six hexadecimal digits are used for 'hhhhhh' or 'HHHHHH',
the least significant digit must be an even number.
'x' and 'X' indicate hexadecimal; 'p' and 'P' indicate power
of two.
Some examples are: 0x0p0, 0x1p10, and 0x1.abcde2p+20

Details

Module ietf-routing-types
Version 2017-02-27
Reference IEEE Std 754-2008: IEEE Standard for Floating-Point Arithmetic.
Source ietf-routing-types line 366

bandwidth-kbps

Summary

Name bandwidth-kbps
Type uint64
  
 
Bandwidth values expressed in kilobits per second

Details

Module openconfig-mpls-types
Version 2017-08-24
Source openconfig-mpls-types line 361

bandwidth-kbps

Summary

Name bandwidth-kbps
Type uint64
  
 
Bandwidth values expressed in kilobits per second

Details

Module ietf-te-mpls-types
Version 2017-10-29
Source ietf-te-mpls-types line 65

bandwidth-mbps

Summary

Name bandwidth-mbps
Type uint64
  
 
Bandwidth values expressed in megabits per second

Details

Module openconfig-mpls-types
Version 2017-08-24
Source openconfig-mpls-types line 368

bandwidth-mbps

Summary

Name bandwidth-mbps
Type uint64
  
 
Bandwidth values expressed in megabits per second

Details

Module ietf-te-mpls-types
Version 2017-10-29
Source ietf-te-mpls-types line 72

bandwidth-profile-type

Summary

Name bandwidth-profile-type
Type identityref
  
 
Identifies a specific Bandwidth Profile type.

Details

Module ietf-eth-tran-types
Version 2017-09-12
Source ietf-eth-tran-types line 179

base-interface-ref

Summary

Name base-interface-ref
Type leafref
  
 
Reusable type for by-name reference to a base interface.
This type may be used in cases where ability to reference
a subinterface is not required.

Details

Module openconfig-interfaces
Version 2017-12-21
Source openconfig-interfaces line 84

base64Binary

Summary

Name base64Binary
Type string
  
 
XSD base64 binary encoded string

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#base64Binary
Source yuma-xsd line 56

bfd-diagnostic-code

Summary

Name bfd-diagnostic-code
Type enumeration
  
 
Diagnostic codes defined by BFD. These typically indicate the
reason for a change of session state.

Details

Module openconfig-bfd
Version 2017-11-17
Reference RFC5880 - Bidirectional Forwarding Detection, Section 4.1
Source openconfig-bfd line 78

bfd-encap-mode-type

Summary

Name bfd-encap-mode-type
Type enumeration
  
 
Possible BFD transport modes when running over TE
LSPs.

Details

Module ietf-te-mpls-types
Version 2017-10-29
Source ietf-te-mpls-types line 116

bfd-session-state

Summary

Name bfd-session-state
Type enumeration
  
 
The state of the BFD session according to the system referred
to by the context of the leaf.

Details

Module openconfig-bfd
Version 2017-11-17
Reference RFC5880 - Bidirectional Forwarding Detection, Section 4.1
Source openconfig-bfd line 50

bfd-type

Summary

Name bfd-type
Type enumeration
  
 
Type of BFD session

Details

Module ietf-te-mpls-types
Version 2017-10-29
Source ietf-te-mpls-types line 102

bfr-id

Summary

Name bfr-id
Type uint16
  
 
The type for bfr identifier

Details

Module ietf-bier
Version 2017-08-10
Source ietf-bier line 134

bfr-id

Summary

Name bfr-id
Type uint16
  
 
The BFR id of nodes.

Details

Module ietf-multicast-information
Version 2017-08-20
Source ietf-multicast-information line 136

bgp-community-regexp-type

Summary

Name bgp-community-regexp-type
Type string
  
 
Type definition for communities specified as regular
expression patterns

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 307

bgp-ext-community-recv-type

Summary

Name bgp-ext-community-recv-type
Type union
  
 
A type definition utilised to define the extended community
in a context where the system is receiving the extended
community from an external source, such that the value may be
unknown. In the case that the received extended community is
unknown it is defined to be a 8-octet quantity formatted
according to RFC4360:

Type Field: 1 or 2 octets.
Value Field: Remaining octets.

The high-order octet of the type field is encoded such that
bit 0 indicates whether the extended community type is IANA
assigned; and bit 1 indicates whether the extended community
is transitive.  The remaining bits of the high-order type
field must be interpreted to determine whether the low-order
type field should be parsed, or whether the entire remainder
of the extended community is a value.

Details

Module openconfig-bgp-types
Version 2017-07-30
Reference RFC 4360 - BGP Extended Communities Attribute RFC 5668 - 4-Octet AS Specific BGP Extended Community
Source openconfig-bgp-types line 382

bgp-ext-community-type

Summary

Name bgp-ext-community-type
Type union
  
 
Type definition for extended community attributes

Details

Module ietf-bgp-types
Version 2017-10-17
Reference RFC 4360 - BGP Extended Communities Attribute
Source ietf-bgp-types line 242

bgp-ext-community-type

Summary

Name bgp-ext-community-type
Type union
  
 
Type definition for extended community attributes. In the case that
common communities are utilised, they are represented as a string
of the form:
 - <2b AS>:<4b value> per RFC4360 section 3.1
 - <4b IPv4>:<2b value> per RFC4360 section 3.2
 - <4b AS>:<2b value> per RFC5668 section 2.
 - route-target:<2b AS>:<4b value> per RFC4360 section 4
 - route-target:<4b IPv4>:<2b value> per RFC4360 section 4
 - route-origin:<2b ASN>:<4b value> per RFC4360 section 5
 - route-origin:<4b IPv4>:<2b value> per RFC4360 section 5

Details

Module openconfig-bgp-types
Version 2017-07-30
Reference RFC 4360 - BGP Extended Communities Attribute RFC 5668 - 4-Octet AS Specific BGP Extended Community
Source openconfig-bgp-types line 274

bgp-next-hop-type

Summary

Name bgp-next-hop-type
Type union
  
 
type definition for specifying next-hop in policy actions

Details

Module openconfig-bgp-policy
Version 2017-07-30
Source openconfig-bgp-policy line 92

bgp-origin-attr-type

Summary

Name bgp-origin-attr-type
Type enumeration
  
 
Type definition for standard BGP origin attribute

Details

Module ietf-bgp-types
Version 2017-10-17
Reference RFC 4271 - A Border Gateway Protocol 4 (BGP-4), Sec 4.3
Source ietf-bgp-types line 317

bgp-origin-attr-type

Summary

Name bgp-origin-attr-type
Type enumeration
  
 
Type definition for standard BGP origin attribute

Details

Module openconfig-bgp-types
Version 2017-07-30
Reference RFC 4271 - A Border Gateway Protocol 4 (BGP-4), Sec 4.3
Source openconfig-bgp-types line 421

bgp-safi

Summary

Name bgp-safi
Type enumeration
  
 
Enumeration for BGP Subsequent Address
Family Identifier (SAFI) - RFC 4760.

Details

Module iana-routing-types
Version 2017-09-19
Source iana-routing-types line 300

bgp-session-direction

Summary

Name bgp-session-direction
Type enumeration
  
 
Type to describe the direction of NLRI transmission

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 196

bgp-session-direction

Summary

Name bgp-session-direction
Type enumeration
  
 
Type to describe the direction of NLRI transmission

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 223

bgp-set-community-option-type

Summary

Name bgp-set-community-option-type
Type enumeration
  
 
Type definition for options when setting the community
attribute in a policy action

Details

Module openconfig-bgp-policy
Version 2017-07-30
Source openconfig-bgp-policy line 67

bgp-set-med-type

Summary

Name bgp-set-med-type
Type union
  
 
Type definition for specifying how the BGP MED can
be set in BGP policy actions. The three choices are to set
the MED directly, increment/decrement using +/- notation,
and setting it to the IGP cost (predefined value).

Details

Module openconfig-bgp-policy
Version 2017-07-30
Source openconfig-bgp-policy line 106

bgp-std-community-type

Summary

Name bgp-std-community-type
Type union
  
 
Type definition for standard commmunity attributes

Details

Module ietf-bgp-types
Version 2017-10-17
Reference RFC 1997 - BGP Communities Attribute
Source ietf-bgp-types line 222

bgp-std-community-type

Summary

Name bgp-std-community-type
Type union
  
 
Type definition for standard commmunity attributes represented as
a integer value, or a string of the form N:M where N and M are
integers between 0 and 65535.

Details

Module openconfig-bgp-types
Version 2017-07-30
Reference RFC 1997 - BGP Communities Attribute
Source openconfig-bgp-types line 250

bgp-well-known-community-type

Summary

Name bgp-well-known-community-type
Type identityref
  
 
Type definition for well-known IETF community attribute
values

Details

Module ietf-bgp-types
Version 2017-10-17
Reference IANA Border Gateway Protocol (BGP) Well Known Communities
Source ietf-bgp-types line 211

bgp-well-known-community-type

Summary

Name bgp-well-known-community-type
Type identityref
  
 
Type definition for well-known IETF community attribute
values

Details

Module openconfig-bgp-types
Version 2017-07-30
Reference IANA Border Gateway Protocol (BGP) Well Known Communities
Source openconfig-bgp-types line 238

bier-mpls-label-range-size

Summary

Name bier-mpls-label-range-size
Type uint8
  
 
The type for BIER label range size.

Details

Module ietf-bier
Version 2017-08-10
Source ietf-bier line 146

bit-string

Summary

Name bit-string
Type uint16
  
 
The bit mask of one bitstring.

Details

Module ietf-bier-te
Version 2017-10-23
Source ietf-bier-te line 164

bit-string

Summary

Name bit-string
Type uint16
  
 
The bit mask of one bitstring.

Details

Module ietf-multicast-information
Version 2017-08-20
Source ietf-multicast-information line 153

bsl

Summary

Name bsl
Type enumeration
  
 
The bitstringlength type for imposition mode

Details

Module ietf-bier
Version 2017-08-10
Source ietf-bier line 152

byte

Summary

Name byte
Type int8
  
 
XSD 8 bit signed integer.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#byte
Source yuma-xsd line 198

cc-detect-multiplier

Summary

Name cc-detect-multiplier
Type uint8
  
 
The value rang for cv packet detect multiplier

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 79

cc-interval

Summary

Name cc-interval
Type uint32
  
 
The value rang for cc packet transmit and receive
interval.

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 66

cc-session-mode

Summary

Name cc-session-mode
Type enumeration
  
 
CC session mode

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 53

cc-type

Summary

Name cc-type
Type enumeration
  
 
The defined values for CC(Control Channel) Types for MPLS PWs.

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 43

ccm-priority-type

Summary

Name ccm-priority-type
Type uint8
  
 
A 3 bit priority value to be used in the VLAN tag,
if present in the transmitted frame.

Details

Module ietf-l2vpn-svc
Version 2017-10-13
Source ietf-l2vpn-svc line 158

change-type

Summary

Name change-type
Type enumeration
  
 
Specifies different types of datastore changes.

Details

Module ietf-yang-push
Version 2017-10-23
Reference RFC 8072 section 2.5, with a delta that it is ok to receive ability create on an existing node, or receive a delete on a missing node.
Source ietf-yang-push line 167

channels-type

Summary

Name channels-type
Type uint8
  
 
Type to specify all the WiFi channels available for use. This is
a superset of what may be allowed by any one particular regulatory
domain.

Details

Module openconfig-wifi-types
Version 2017-07-25
Source openconfig-wifi-types line 34

chassis-id-type

Summary

Name chassis-id-type
Type enumeration
  
 
Type definition with enumerations describing the source of
the chassis identifier

Details

Module openconfig-lldp-types
Version 2016-05-16
Reference IEEE 802.1AB LLDP MIB
Source openconfig-lldp-types line 197

checksum16-type

Summary

Name checksum16-type
Type string
  
 
16-bit checksum in hex-string format 0xXXXX.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 714

circuit-id

Summary

Name circuit-id
Type uint8
  
 
This type defines the circuit ID
associated with an interface.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 232

circuit-type

Summary

Name circuit-type
Type enumeration
  
 
This type defines ISIS interface types 

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 205

CliWithDefaultsType

Summary

Name CliWithDefaultsType
Type enumeration
  
 
Add 'none' to standard enumerations

Details

Module yuma-app-common
Version 2017-07-25
Source yuma-app-common line 86

clock-identity-type

Summary

Name clock-identity-type
Type binary
  
 
Derived data type to identify a clock

Details

Module ietf-ptp-dataset
Version 2017-01-09
Reference IEEE Std 1588-2008: 5.3.4
Source ietf-ptp-dataset line 125

clock-identity-type

Summary

Name clock-identity-type
Type binary
  
 
Derived data type to identify a clock

Details

Module ietf-ptp-dataset
Version 2017-02-08
Reference IEEE Std 1588-2008: 5.3.4
Source ietf-ptp-dataset line 125

clock-identity-type

Summary

Name clock-identity-type
Type binary
  
 
Derived data type to identify a clock

Details

Module ietf-ptp-dataset
Version 2017-04-20
Reference IEEE Std 1588-2008: 5.3.4
Source ietf-ptp-dataset line 130

clock-identity-type

Summary

Name clock-identity-type
Type binary
  
 
Derived data type to identify a clock

Details

Module ietf-ptp
Version 2017-11-28
Reference IEEE Std 1588-2008: 5.3.4
Source ietf-ptp line 127

common-header

Summary

Name common-header
Type identityref
  
 
Type of header object which may be included somewhere within a
message.

Details

Module ietf-notification-messages
Version 2017-10-03
Source ietf-notification-messages line 138

community-type

Summary

Name community-type
Type enumeration
  
 
type describing variations of community attributes:
STANDARD: standard BGP community [rfc1997]
EXTENDED: extended BGP community [rfc4360]
BOTH: both standard and extended community

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 402

community-type

Summary

Name community-type
Type enumeration
  
 
type describing variations of community attributes:
STANDARD: standard BGP community [rfc1997]
EXTENDED: extended BGP community [rfc4360]
BOTH: both standard and extended community

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 503

component-power-type

Summary

Name component-power-type
Type enumeration
  
 
A generic type reflecting whether a hardware component
is powered on or off

Details

Module openconfig-platform-types
Version 2017-12-14
Source openconfig-platform-types line 205

compute-unit-ref

Summary

Name compute-unit-ref
Type instance-identifier
  
 
A reference to a compute unit

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 156

config-edit-mode-type

Summary

Name config-edit-mode-type
Type enumeration
  
 
Specifies how edits will be applied in config mode.

Details

Module yangcli-pro
Version 2017-12-12
Source yangcli-pro line 408

ConfirmTimeoutType

Summary

Name ConfirmTimeoutType
Type uint32
  
 
NETCONF 'confirm-timeout' Element Content

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 510

connectivity-direction

Summary

Name connectivity-direction
Type enumeration
  
 
A type used to indicates whether a connectivity is
uni-directional, or bi-directional. If the relation is
uni-directional, the value of this type indicates the
direction.

Details

Module ietf-te-topology-sf
Version 2017-10-22
Source ietf-te-topology-sf line 48

control-client-connection-state

Summary

Name control-client-connection-state
Type enumeration
  
 
Indicates the Control-Client TWAMP-Control connection state.

Details

Module ietf-twamp
Version 2017-10-16
Source ietf-twamp line 135

control-mode

Summary

Name control-mode
Type enumeration
  
 
Defining a type of the control mode on L2CP protocols.

Details

Module ietf-l2vpn-svc
Version 2017-10-13
Source ietf-l2vpn-svc line 166

counter32

Summary

Name counter32
Type uint32
  
 
A 32-bit counter. A counter value is a monotonically increasing
value which is used to express a count of a number of
occurrences of a particular event or entity. When the counter
reaches its maximum value, in this case 2^32-1, it wraps to 0.

Discontinuities in the counter are generally triggered only when
the counter is reset to zero.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 75

counter32

Summary

Name counter32
Type uint32
  
 
The counter32 type represents a non-negative integer
that monotonically increases until it reaches a
maximum value of 2^32-1 (4294967295 decimal), when it
wraps around and starts increasing again from zero.

Counters have no defined 'initial' value, and thus, a
single value of a counter has (in general) no information
content.  Discontinuities in the monotonically increasing
value normally occur at re-initialization of the
management system, and at other times as specified in the
description of a schema node using this type.  If such
other times can occur, for example, the creation of
a schema node of type counter32 at times other than
re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate
the last discontinuity.

The counter32 type should not be used for configuration
schema nodes.  A default statement SHOULD NOT be used in
combination with the type counter32.

In the value set and its semantics, this type is equivalent
to the Counter32 type of the SMIv2.

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 46

counter32

Summary

Name counter32
Type uint32
  
 
The counter32 type represents a non-negative integer
that monotonically increases until it reaches a
maximum value of 2^32-1 (4294967295 decimal), when it
wraps around and starts increasing again from zero.

Counters have no defined 'initial' value, and thus, a
single value of a counter has (in general) no information
content.  Discontinuities in the monotonically increasing
value normally occur at re-initialization of the
management system, and at other times as specified in the
description of a schema node using this type.  If such
other times can occur, for example, the creation of
a schema node of type counter32 at times other than
re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate
the last discontinuity.

The counter32 type should not be used for configuration
schema nodes.  A default statement SHOULD NOT be used in
combination with the type counter32.

In the value set and its semantics, this type is equivalent
to the Counter32 type of the SMIv2.

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 59

counter64

Summary

Name counter64
Type uint64
  
 
A 64-bit counter. A counter value is a monotonically increasing
value which is used to express a count of a number of
occurrences of a particular event or entity. When a counter64
reaches its maximum value, 2^64-1, it loops to zero.
Discontinuities in a counter are generally triggered only when
the counter is reset to zero, through operator or system
intervention.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 88

counter64

Summary

Name counter64
Type uint64
  
 
The counter64 type represents a non-negative integer
that monotonically increases until it reaches a
maximum value of 2^64-1 (18446744073709551615 decimal),
when it wraps around and starts increasing again from zero.

Counters have no defined 'initial' value, and thus, a
single value of a counter has (in general) no information
content.  Discontinuities in the monotonically increasing
value normally occur at re-initialization of the
management system, and at other times as specified in the
description of a schema node using this type.  If such
other times can occur, for example, the creation of
a schema node of type counter64 at times other than
re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate
the last discontinuity.

The counter64 type should not be used for configuration
schema nodes.  A default statement SHOULD NOT be used in
combination with the type counter64.

In the value set and its semantics, this type is equivalent
to the Counter64 type of the SMIv2.

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 102

counter64

Summary

Name counter64
Type uint64
  
 
The counter64 type represents a non-negative integer
that monotonically increases until it reaches a
maximum value of 2^64-1 (18446744073709551615 decimal),
when it wraps around and starts increasing again from zero.

Counters have no defined 'initial' value, and thus, a
single value of a counter has (in general) no information
content.  Discontinuities in the monotonically increasing
value normally occur at re-initialization of the
management system, and at other times as specified in the
description of a schema node using this type.  If such
other times can occur, for example, the creation of
a schema node of type counter64 at times other than
re-initialization, then a corresponding schema node
should be defined, with an appropriate type, to indicate
the last discontinuity.

The counter64 type should not be used for configuration
schema nodes.  A default statement SHOULD NOT be used in
combination with the type counter64.

In the value set and its semantics, this type is equivalent
to the Counter64 type of the SMIv2.

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 116

crypt-hash

Summary

Name crypt-hash
Type string
  
 
The crypt-hash type is used to store passwords using
a hash function.  The algorithms for applying the hash
function and encoding the result are implemented in
various UNIX systems as the function crypt(3).

A value of this type matches one of the forms:

  $0$<clear text password>
  $<id>$<salt>$<password hash>
  $<id>$<parameter>$<salt>$<password hash>

The '$0$' prefix signals that the value is clear text.  When
such a value is received by the server, a hash value is
calculated, and the string '$<id>$<salt>$' or
$<id>$<parameter>$<salt>$ is prepended to the result.  This
value is stored in the configuration data store.
If a value starting with '$<id>$', where <id> is not '0', is
received, the server knows that the value already represents a
hashed value and stores it 'as is' in the data store.

When a server needs to verify a password given by a user, it
finds the stored password hash string for that user, extracts
the salt, and calculates the hash with the salt and given
password as input.  If the calculated hash value is the same
as the stored value, the password given by the client is
accepted.

This type defines the following hash functions:

  id | hash function | feature
  ---+---------------+-------------------
   1 | MD5           | crypt-hash-md5
   5 | SHA-256       | crypt-hash-sha-256
   6 | SHA-512       | crypt-hash-sha-512

The server indicates support for the different hash functions
by advertising the corresponding feature.

Details

Module iana-crypt-hash
Version 2014-08-06
Reference IEEE Std 1003.1-2008 - crypt() function RFC 1321: The MD5 Message-Digest Algorithm FIPS.180-4.2012: Secure Hash Standard (SHS)
Source iana-crypt-hash line 47

crypt-password-type

Summary

Name crypt-password-type
Type string
  
 
A password that is hashed based on the hash algorithm
indicated by the prefix in the string.  The string
takes the following form, based on the Unix crypt function:

$<id>[$<param>=<value>(,<param>=<value>)*][$<salt>[$<hash>]]

Common hash functions include:

id  | hash function
---+---------------
 1 | MD5
 2a| Blowfish
 2y| Blowfish (correct handling of 8-bit chars)
 5 | SHA-256
 6 | SHA-512

These may not all be supported by a target device.

Details

Module openconfig-aaa-types
Version 2017-09-18
Source openconfig-aaa-types line 133

cspf-tie-breaking

Summary

Name cspf-tie-breaking
Type enumeration
  
 
type to indicate the CSPF selection policy when
multiple equal cost paths are available

Details

Module openconfig-mpls
Submodule openconfig-mpls-te
Version 2017-08-24
Source openconfig-mpls-te line 143

ctrl-connection-state

Summary

Name ctrl-connection-state
Type enumeration
  
 
Control connection state

Details

Module ietf-twamp
Version 2015-06-30
Source ietf-twamp line 32

cv-detect-multiplier

Summary

Name cv-detect-multiplier
Type uint8
  
 
The value rang for cv packet detect multiplier

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 85

cv-interval

Summary

Name cv-interval
Type uint32
  
 
The value rang for cv packet transmit interval.

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 73

cv-type

Summary

Name cv-type
Type enumeration
  
 
The defined values for CV(Connectivity Verification) Types for MPLS PWs

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 58

cw-capable-type

Summary

Name cw-capable-type
Type enumeration
  
 
control-word capable preference type

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 31

cw-negotiation-type

Summary

Name cw-negotiation-type
Type enumeration
  
 
control-word negotiation preference type

Details

Module ietf-pseudowires
Version 2017-06-26
Source ietf-pseudowires line 41

cycle-number

Summary

Name cycle-number
Type string
  
 
A cycle number represented in the format YYYYMMDD.HHMMSS
where YYYY represents the year, MM the month (1..12), DD
the day of the months (01..31), HH the hour (00..23), MM
the minute (00..59), and SS the second (00..59). The cycle
number is using Coordinated Universal Time (UTC).

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 89

cycle-number

Summary

Name cycle-number
Type string
  
 
A cycle number represented in the format YYYYMMDD.HHMMSS
where YYYY represents the year, MM the month (1..12), DD
the day of the months (01..31), HH the hour (00..23), MM
the minute (00..59), and SS the second (00..59).  The cycle
number is using Coordinated Universal Time (UTC).

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 90

datapath-id

Summary

Name datapath-id
Type string
  
 
The datapath-id type represents an OpenFlow
datapath identifier. The lower 48-bits are for
a MAC address, while the upper 16-bits are
implementer-defined.

Details

Module openconfig-openflow-types
Version 2017-08-24
Source openconfig-openflow-types line 82

datastore

Summary

Name datastore
Type identityref
  
 
An NMDA datastore.

Details

Module ietf-netconf-datastores
Version 2017-08-24
Reference RFC XXXX: Network Management Datastore Architecture
Source ietf-netconf-datastores line 76

datastore-ref

Summary

Name datastore-ref
Type identityref
  
 
A datastore identity reference.

Details

Module ietf-datastores
Version 2017-08-17
Source ietf-datastores line 111

Date

Summary

Name Date
Type string
  
 
Represents a specific date in YYYY-MM-DD format.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 326

date

Summary

Name date
Type string
  
 
XSD date string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#date
Source yuma-xsd line 253

date-and-time

Summary

Name date-and-time
Type string
  
 
A date and time, expressed in the format described in RFC3339.
That is to say:

YYYY-MM-DDTHH:MM:SSZ+-hh:mm

where YYYY is the year, MM is the month expressed as a two-digit
month (zero padding if required), DD is the day of the month,
expressed as a two digit value. T is the literal character 'T',
HH is the hour of the day expressed as a two digit number, using
the 24-hour clock, MM is the minute of the hour expressed as a
two digit number. Z is the literal character 'Z', followed by a
timezone offset expressed in hours (hh) and minutes (mm), both
expressed as two digit numbers. The time offset is specified as
a positive or negative offset to UTC using the '+' or '-'
character preceding the offset.

Optionally, fractional seconds can be expressed after the minute
of the hour as a decimal number of unspecified precision
reflecting fractions of a second.

Details

Module openconfig-yang-types
Version 2017-07-30
Reference RFC3339 - Date and Time on the Internet: Timestamps
Source openconfig-yang-types line 101

date-and-time

Summary

Name date-and-time
Type string
  
 
The date-and-time type is a profile of the ISO 8601
standard for representation of dates and times using the
Gregorian calendar.  The profile is defined by the
date-time production in Section 5.6 of RFC 3339.

The date-and-time type is compatible with the dateTime XML
schema type with the following notable exceptions:

(a) The date-and-time type does not allow negative years.

(b) The date-and-time time-offset -00:00 indicates an unknown
    time zone (see RFC 3339) while -00:00 and +00:00 and Z all
    represent the same time zone in dateTime.

(c) The canonical format (see below) of data-and-time values
    differs from the canonical format used by the dateTime XML
    schema type, which requires all times to be in UTC using the
    time-offset 'Z'.

This type is not equivalent to the DateAndTime textual
convention of the SMIv2 since RFC 3339 uses a different
separator between full-date and full-time and provides
higher resolution of time-secfrac.



The canonical format for date-and-time values with a known time
zone uses a numeric time zone offset that is calculated using
the device's configured known offset to UTC time.  A change of
the device's offset to UTC time will cause date-and-time values
to change accordingly.  Such changes might happen periodically
in case a server follows automatically daylight saving time
(DST) time zone offset changes.  The canonical format for
date-and-time values with an unknown time zone (usually referring
to the notion of local time) uses the time-offset -00:00.

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 3339: Date and Time on the Internet: Timestamps RFC 2579: Textual Conventions for SMIv2 XSD-TYPES: XML Schema Part 2: Datatypes Second Edition
Source ietf-yang-types line 271

date-and-time

Summary

Name date-and-time
Type string
  
 
The date-and-time type is a profile of the ISO 8601
standard for representation of dates and times using the
Gregorian calendar.  The profile is defined by the
date-time production in Section 5.6 of RFC 3339.

The date-and-time type is compatible with the dateTime XML
schema type with the following notable exceptions:

(a) The date-and-time type does not allow negative years.

(b) The date-and-time time-offset -00:00 indicates an unknown
    time zone (see RFC 3339) while -00:00 and +00:00 and Z
    all represent the same time zone in dateTime.

(c) The canonical format (see below) of data-and-time values
    differs from the canonical format used by the dateTime XML
    schema type, which requires all times to be in UTC using
    the time-offset 'Z'.

This type is not equivalent to the DateAndTime textual
convention of the SMIv2 since RFC 3339 uses a different
separator between full-date and full-time and provides
higher resolution of time-secfrac.

The canonical format for date-and-time values with a known time
zone uses a numeric time zone offset that is calculated using
the device's configured known offset to UTC time.  A change of
the device's offset to UTC time will cause date-and-time values
to change accordingly.  Such changes might happen periodically
in case a server follows automatically daylight saving time
(DST) time zone offset changes.  The canonical format for
date-and-time values with an unknown time zone (usually
referring to the notion of local time) uses the time-offset
-00:00.

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 3339: Date and Time on the Internet: Timestamps RFC 2579: Textual Conventions for SMIv2 XSD-TYPES: XML Schema Part 2: Datatypes Second Edition
Source ietf-yang-types line 303

DateAndTime

Summary

Name DateAndTime
Type string
  
 
A date-time specification.

field  octets  contents                  range
-----  ------  --------                  -----
  1      1-2   year*                     0..65536
  2       3    month                     1..12
  3       4    day                       1..31
  4       5    hour                      0..23
  5       6    minutes                   0..59
  6       7    seconds                   0..60
	       (use 60 for leap-second)
  7       8    deci-seconds              0..9
  8       9    direction from UTC        '+' / '-'
  9      10    hours from UTC*           0..13
 10      11    minutes from UTC          0..59

* Notes:
- the value of year is in network-byte order
- daylight saving time in New Zealand is +13

For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
displayed as:

		 1992-5-26,13:30:15.0,-4:0

Note that if only local time is known, then timezone
information (fields 8-10) is not present.

Details

Module SNMPv2-TC
Version none
Source SNMPv2-TC line 678

dateTime

Summary

Name dateTime
Type string
  
 
XSD date and time string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dateTime
Source yuma-xsd line 240

date_and_time_b

Summary

Name date_and_time_b
Type int64
  
 
Binary representation of a date and time. This value is
encoded using a positive or negative value representing
a number of seconds relative to 1970-01-01T00:00Z in UTC
time (i.e. the epoch). Negative values represent a date
and time before the epoch, positive values represent a
date and time after the epoch.
This representation is defined in [RFC 7049] section
2.4.1. When implemented using CoMI, tag 0 is assumed
and not encoded.

Details

Module ietf-comi
Version 2017-07-01
Reference [RFC 7049] Concise Binary Object Representation (CBOR)
Source ietf-comi line 42

day-of-month

Summary

Name day-of-month
Type uint8
  
 
A day of a month of the Gregorian calendar.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 177

day-of-month

Summary

Name day-of-month
Type uint8
  
 
A day of a month of the Gregorian calendar.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 179

day-of-months-or-all

Summary

Name day-of-months-or-all
Type union
  
 
A day of a months or a wildcard indicating all days
of a month.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 183

day-of-months-or-all

Summary

Name day-of-months-or-all
Type union
  
 
A day of a month or a wildcard indicating all days
of a month.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 185

dbm-t

Summary

Name dbm-t
Type decimal64
  
 
Amplifier Power in dBm 

Details

Module ietf-ext-xponder-wdm-if
Version 2017-03-06
Source ietf-ext-xponder-wdm-if line 46

dbm-t

Summary

Name dbm-t
Type decimal64
  
 
Amplifier Power in dBm 

Details

Module ietf-opt-parameters-wdm
Version 2016-10-30
Source ietf-opt-parameters-wdm line 75

decimal

Summary

Name decimal
Type string
  
 
XSD decimal data type.
[To do: not sure if this is a bounded real number
 or an unbounded real number.].

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#decimal
Source yuma-xsd line 216

default-policy-type

Summary

Name default-policy-type
Type enumeration
  
 
Type used to specify route disposition in
a policy chain

Details

Module openconfig-routing-policy
Version 2017-07-14
Source openconfig-routing-policy line 100

DefaultOperationType

Summary

Name DefaultOperationType
Type enumeration
  
 
NETCONF 'default-operation' Element Content

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 500

defect-status-type

Summary

Name defect-status-type
Type string
  
 
The namespace of defect status type

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 229

defect-type

Summary

Name defect-type
Type string
  
 
The namespace of defect type

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 235

delay-mechanism-enumeration

Summary

Name delay-mechanism-enumeration
Type enumeration
  
 
The propagation delay measuring option used by the
port. Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-01-09
Reference IEEE Std 1588-2008: 8.2.5.4.4
Source ietf-ptp-dataset line 26

delay-mechanism-enumeration

Summary

Name delay-mechanism-enumeration
Type enumeration
  
 
The propagation delay measuring option used by the
port. Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-02-08
Reference IEEE Std 1588-2008: 8.2.5.4.4
Source ietf-ptp-dataset line 26

delay-mechanism-enumeration

Summary

Name delay-mechanism-enumeration
Type enumeration
  
 
The propagation delay measuring option used by the
port. Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-04-20
Reference IEEE Std 1588-2008: 8.2.5.4.4
Source ietf-ptp-dataset line 31

delay-mechanism-enumeration

Summary

Name delay-mechanism-enumeration
Type enumeration
  
 
The propagation delay measuring option used by the
port. Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp
Version 2017-11-28
Reference IEEE Std 1588-2008: 8.2.5.4.4
Source ietf-ptp line 31

device-role

Summary

Name device-role
Type enumeration
  
 
device role type

Details

Module ietf-fabric-types
Version 2017-11-29
Source ietf-fabric-types line 164

diagnostic

Summary

Name diagnostic
Type enumeration
  
 
BFD diagnostic as defined in RFC5880. Range is 0 to 31.

Details

Module iana-bfd-types
Version 2017-10-30
Source iana-bfd-types line 43

DiffType

Summary

Name DiffType
Type enumeration
  
 
Type of comparison output requested.

Details

Module yangdiff-pro
Version 2011-10-06
Source yangdiff-pro line 134

direction

Summary

Name direction
Type enumeration
  
 
Direction of packets going through an interface or
linecard.

Details

Module ietf-ipfix-psamp
Version 2012-09-05
Source ietf-ipfix-psamp line 297

direction

Summary

Name direction
Type enumeration
  
 
Which way are we talking about?

Details

Module ietf-mud
Version 2017-10-07
Source ietf-mud line 58

discriminator

Summary

Name discriminator
Type uint32
  
 
BFD discriminator

Details

Module ietf-bfd-types
Version 2017-10-30
Source ietf-bfd-types line 66

DisplayString

Summary

Name DisplayString
Type string
  
 
YANG version of the SMIv2 DisplayString TEXTUAL-CONVENTION.

Details

Module toaster
Version 2009-11-20
Reference RFC 2579, section 2.
Source toaster line 71

DisplayString

Summary

Name DisplayString
Type string
  
 
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

  - the use of character codes 0-127 (decimal)

  - the graphics characters (32-126) are interpreted as
    US ASCII

  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854

  - the other 25 codes have no standard interpretation

  - the sequence 'CR LF' means newline

  - the sequence 'CR NUL' means carriage-return

  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.

  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)

Any object defined using this syntax may not exceed 255
characters in length.

Details

Module SNMPv2-TC
Version none
Source SNMPv2-TC line 22

distinguished-name-type

Summary

Name distinguished-name-type
Type string
  
 
Distinguished Name address.

Details

Module ietf-lisp-address-types
Version 2015-11-05
Reference http://www.iana.org/assignments/address-family-numbers/ address-family-numbers.xhtml
Source ietf-lisp-address-types line 195

dm-interval

Summary

Name dm-interval
Type uint32
  
 
The value rang for dm packet transmit interval

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 155

dm-padding-value

Summary

Name dm-padding-value
Type enumeration
  
 
dm-padding-value

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 161

domain

Summary

Name domain
Type union
  
 
The Domain Information

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 289

domain-as

Summary

Name domain-as
Type uint32
  
 
Autonomous System number.

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 282

domain-isis-area

Summary

Name domain-isis-area
Type string
  
 
IS-IS Area ID.

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 274

domain-name

Summary

Name domain-name
Type string
  
 
The domain-name type represents a DNS domain name.
Fully quallified left to the models which utilize this type.

Internet domain names are only loosely specified.  Section
3.5 of RFC 1034 recommends a syntax (modified in Section
2.1 of RFC 1123).  The pattern above is intended to allow
for current practice in domain name use, and some possible
future expansion.  It is designed to hold various types of
domain names, including names used for A or AAAA records
(host names) and other records, such as SRV records.  Note
that Internet host names have a stricter syntax (described
in RFC 952) than the DNS recommendations in RFCs 1034 and
1123, and that systems that want to store host names in
schema nodes using the domain-name type are recommended to
adhere to this stricter standard to ensure interoperability.

The encoding of DNS names in the DNS protocol is limited
to 255 characters.  Since the encoding consists of labels
prefixed by a length bytes and there is a trailing NULL
byte, only 253 characters can appear in the textual dotted
notation.

Domain-name values use the US-ASCII encoding.  Their canonical
format uses lowercase US-ASCII characters.  Internationalized
domain names MUST be encoded in punycode as described in RFC
3492

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 216

domain-name

Summary

Name domain-name
Type string
  
 
The domain-name type represents a DNS domain name.  The
name SHOULD be fully qualified whenever possible.

Internet domain names are only loosely specified.  Section
3.5 of RFC 1034 recommends a syntax (modified in Section
2.1 of RFC 1123).  The pattern above is intended to allow
for current practice in domain name use, and some possible
future expansion.  It is designed to hold various types of
domain names, including names used for A or AAAA records
(host names) and other records, such as SRV records.  Note
that Internet host names have a stricter syntax (described
in RFC 952) than the DNS recommendations in RFCs 1034 and
1123, and that systems that want to store host names in
schema nodes using the domain-name type are recommended to
adhere to this stricter standard to ensure interoperability.

The encoding of DNS names in the DNS protocol is limited
to 255 characters.  Since the encoding consists of labels
prefixed by a length bytes and there is a trailing NULL
byte, only 253 characters can appear in the textual dotted
notation.

The description clause of schema nodes using the domain-name
type MUST describe when and how these names are resolved to
IP addresses.  Note that the resolution of a domain-name value
may require to query multiple DNS records (e.g., A for IPv4
and AAAA for IPv6).  The order of the resolution process and
which DNS record takes precedence can either be defined
explicitely or it may depend on the configuration of the
resolver.

Domain-name values use the US-ASCII encoding.  Their canonical
format uses lowercase US-ASCII characters.  Internationalized
domain names MUST be encoded in punycode as described in RFC
3492

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 952: DoD Internet Host Table Specification RFC 1034: Domain Names - Concepts and Facilities RFC 1123: Requirements for Internet Hosts -- Application and Support RFC 2782: A DNS RR for specifying the location of services (DNS SRV) RFC 3492: Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA) RFC 5891: Internationalizing Domain Names in Applications (IDNA): Protocol
Source ietf-inet-types line 321

domain-name

Summary

Name domain-name
Type string
  
 
The domain-name type represents a DNS domain name.  The
name SHOULD be fully qualified whenever possible.

Internet domain names are only loosely specified.  Section
3.5 of RFC 1034 recommends a syntax (modified in Section
2.1 of RFC 1123).  The pattern above is intended to allow
for current practice in domain name use, and some possible
future expansion.  It is designed to hold various types of
domain names, including names used for A or AAAA records
(host names) and other records, such as SRV records.  Note
that Internet host names have a stricter syntax (described
in RFC 952) than the DNS recommendations in RFCs 1034 and
1123, and that systems that want to store host names in
schema nodes using the domain-name type are recommended to
adhere to this stricter standard to ensure interoperability.

The encoding of DNS names in the DNS protocol is limited
to 255 characters.  Since the encoding consists of labels
prefixed by a length bytes and there is a trailing NULL
byte, only 253 characters can appear in the textual dotted
notation.

The description clause of schema nodes using the domain-name
type MUST describe when and how these names are resolved to
IP addresses.  Note that the resolution of a domain-name value
may require to query multiple DNS records (e.g., A for IPv4
and AAAA for IPv6).  The order of the resolution process and
which DNS record takes precedence can either be defined
explicitly or may depend on the configuration of the
resolver.

Domain-name values use the US-ASCII encoding.  Their canonical
format uses lowercase US-ASCII characters.  Internationalized
domain names MUST be A-labels as per RFC 5890.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 952: DoD Internet Host Table Specification RFC 1034: Domain Names - Concepts and Facilities RFC 1123: Requirements for Internet Hosts -- Application and Support RFC 2782: A DNS RR for specifying the location of services (DNS SRV) RFC 5890: Internationalized Domain Names in Applications (IDNA): Definitions and Document Framework
Source ietf-inet-types line 358

domain-ospf-area

Summary

Name domain-ospf-area
Type union
  
 
OSPF Area ID.

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 265

domain-type

Summary

Name domain-type
Type enumeration
  
 
The PCE Domain Type

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 243

Dot1afCfmIndexIntegerNextFree

Summary

Name Dot1afCfmIndexIntegerNextFree
Type uint32
  
 
An integer which may be used as a new Index in a table.

The special value of 0 indicates that no more new entries
can be created in the relevant table.

When a MIB is used for configuration, an object with this
SYNTAX always contains a legal value (if non-zero) for an
index that is not currently used in the relevant table. The
Command Generator (Network Management Application) reads
this variable and uses the (non-zero) value read when
creating a new row with an SNMP SET.  When the SET is
performed, the Command Responder (agent) must determine
whether the value is indeed still unused; Two Network
Management Applications may attempt to create a row
(configuration entry) simultaneously and use the same value.
If it is currently unused, the SET succeeds and the Command
Responder (agent) changes the value of this object,
according to an implementation-specific algorithm.
If the value is in use, however, the SET fails.
The Network Management Application must then re-read this
variable to obtain a new usable value.

An OBJECT-TYPE definition using this SYNTAX MUST specify the
relevant table for which the object is providing this
functionality.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 1287

Dot1agCfmCcmInterval

Summary

Name Dot1agCfmCcmInterval
Type enumeration
  
 
Indicates the interval at which CCMs are sent by a MEP.

Note: enumerations start at zero to match the 'CCM Interval
      field' protocol field.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.6.1.3:e, 20.8.1 and 21.6.1.3
Source ietf-cfm line 1056

Dot1agCfmConfigErrors

Summary

Name Dot1agCfmConfigErrors
Type bits
  
 
While making the MIP creation evaluation described in
802.1ag clause 22.2.3, the management entity can encounter
errors in the configuration.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.4.1.3:b and clauses 22.2.3 and 22.2.4
Source ietf-cfm line 1362

Dot1agCfmEgressActionFieldValue

Summary

Name Dot1agCfmEgressActionFieldValue
Type enumeration
  
 
Possible values returned in the egress action field

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.7.5.3:o, 20.36.2.10, 21.9.9.1, and Table 21-32
Source ietf-cfm line 1214

Dot1agCfmFngState

Summary

Name Dot1agCfmFngState
Type enumeration
  
 
Indicates the diferent states of the MEP Fault Notification
Generator State Machine.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.7.1.3:f and 20.35
Source ietf-cfm line 1108

Dot1agCfmHighestDefectPri

Summary

Name Dot1agCfmHighestDefectPri
Type enumeration
  
 
An enumerated value, equal to the contents of the variable
highestDefect (20.33.9 and Table 20-1), indicating the
highest-priority defect that has been present since the MEP
Fault Notification Generator State Machine was last in the
FNG_RESET state, either:

none(0)           no defects since FNG_RESET
defRDICCM(1)      DefRDICCM
defMACstatus(2)   DefMACstatus
defRemoteCCM(3)   DefRemoteCCM
defErrorCCM(4)    DefErrorCCM
defXconCCM(5)     DefXconCCM

The value 0 is used for no defects so that additional higher
priority values can be added, if needed, at a later time,
and so that these values correspond with those in
Dot1agCfmLowestAlarmPri.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 20.1.2, 12.14.7.7.2:c and 20.33.9
Source ietf-cfm line 852

Dot1agCfmIdPermission

Summary

Name Dot1agCfmIdPermission
Type enumeration
  
 
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.6.1.3:d and 21.5.3
Source ietf-cfm line 1015

Dot1agCfmIngressActionFieldValue

Summary

Name Dot1agCfmIngressActionFieldValue
Type enumeration
  
 
Possible values returned in the ingress action field.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.7.5.3:g, 20.36.2.6, 21.9.8.1, and Table 21-30
Source ietf-cfm line 1176

Dot1agCfmInterfaceStatus

Summary

Name Dot1agCfmInterfaceStatus
Type enumeration
  
 
An enumerated value from the Interface Status TLV from the
last CCM received from the last MEP. It indicates the status
of the Interface within which the MEP transmitting the CCM
is configured, or the next lower Interface in the Interface
Stack, if the MEP is not configured within an Interface.

NOTE: A 0 value is used for isNoInterfaceStatusTLV, so that
      these code points can be kept consistent with new code
      points added to ifOperStatus in the IF-MIB.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.7.6.3:g, 20.19.4 and 21.5.5
Source ietf-cfm line 789

Dot1agCfmLowestAlarmPri

Summary

Name Dot1agCfmLowestAlarmPri
Type enumeration
  
 
An integer value specifying the lowest priority defect
that is allowed to generate a Fault Alarm (20.9.5)

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.7.1.3:k and 20.9.5
Source ietf-cfm line 907

Dot1agCfmMaintAssocName

Summary

Name Dot1agCfmMaintAssocName
Type binary
  
 
Denotes a generic Maintenance Association Name. It is the
part of the Maintenance Association Identifier which is
unique within the Maintenance Domain Name and is appended
to the Maintenance Domain Name to form the Maintenance
Association Identifier (MAID).

A Dot1agCfmMaintAssocName value is always interpreted within
the context of a Dot1agCfmMaintAssocNameType value.  Every
usage of the Dot1agCfmMaintAssocName textual convention is
required to specify the Dot1agCfmMaintAssocNameType object
that provides the context.  It is suggested that the
Dot1agCfmMaintAssocNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintAssocName
textual convention, if they appear in the same logical row.

The value of a Dot1agCfmMaintAssocName object must
always be consistent with the value of the associated
Dot1agCfmMaintAssocNameType object. Attempts to set
an Dot1agCfmMaintAssocName object to a value inconsistent
with the associated Dot1agCfmMaintAssocNameType must fail
with an inconsistentValue error.

When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, IETF STD 58.  In this
case, the object definition MUST include a 'SIZE' clause
to limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 21.6.5.4, 21.6.5.5, 21.6.5.6
Source ietf-cfm line 651

Dot1agCfmMaintAssocNameType

Summary

Name Dot1agCfmMaintAssocNameType
Type enumeration
  
 
A value that represents a type (and thereby the format)
of a Dot1agCfmMaintAssocName.  The value can be one of
the following:
ieeeReserved(0)   Reserved for definition by IEEE 802.1
		  recommend to not use zero unless
		  absolutely needed.
primaryVid(1)     Primary VLAN ID.
		  12 bits represented in a 2-octet integer:
		  - 4 least significant bits of the first
		    byte contains the 4 most significant
		    bits of the 12 bits primary VID
		  - second byte contains the 8 least
		    significant bits of the primary VID

			 0 1 2 3 4 5 6 7 8
			 +-+-+-+-+-+-+-+-+
			 |0 0 0 0| (MSB) |
			 +-+-+-+-+-+-+-+-+
			 |  VID   LSB    |
			 +-+-+-+-+-+-+-+-+

charString(2)     RFC2579 DisplayString, except that the
		  character codes 0-31 (decimal) are not
		  used. (1..45) octets
unsignedInt16 (3) 2-octet integer/big endian
rfc2865VpnId(4)   RFC 2685 VPN ID
		  3 octet VPN authority Organizationally
		  Unique Identifier followed by 4 octet VPN
		  index identifying VPN according to the
		  OUI:

			 0 1 2 3 4 5 6 7 8
			 +-+-+-+-+-+-+-+-+
			 | VPN OUI (MSB) |
			 +-+-+-+-+-+-+-+-+
			 |   VPN OUI     |
			 +-+-+-+-+-+-+-+-+
			 | VPN OUI (LSB) |
			 +-+-+-+-+-+-+-+-+
			 |VPN Index (MSB)|
			 +-+-+-+-+-+-+-+-+
			 |  VPN Index    |
			 +-+-+-+-+-+-+-+-+
			 |  VPN Index    |
			 +-+-+-+-+-+-+-+-+
			 |VPN Index (LSB)|
			 +-+-+-+-+-+-+-+-+

ieeeReserved(xx)  Reserved for definition by IEEE 802.1
		  xx values can be [5..31] and [64..255]
ituReserved(xx)   Reserved for definition by  ITU-T Y.1731
		  xx values range from [32..63]

To support future extensions, the
Dot1agCfmMaintAssocNameType textual convention SHOULD NOT
be sub-typed in object type definitions. It MAY be
sub-typed in compliance statements in order to require
only a subset of these address types for a compliant
implementation.

Implementations must ensure that Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent.  An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName pairs
must be changed together if the nameType changes.

The Maintenance Domain name and Maintenance Association
name,when put together into the CCM PDU, MUST total 48
octets or less.If the Dot1agCfmMaintDomainNameType
object contains none(1), then the Dot1agCfmMaintAssocName
object MUST be 45 octets or less in length.  Otherwise,
the length of the Dot1agCfmMaintDomainName object plus the
length of the Dot1agCfmMaintAssocName object, added
together, MUST total less than or equal to 44 octets.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 21.6.5.4, Table 21-20
Source ietf-cfm line 545

Dot1agCfmMaintDomainName

Summary

Name Dot1agCfmMaintDomainName
Type binary
  
 
Denotes a generic Maintenance Domain Name.

A Dot1agCfmMaintDomainName value is interpreted within
the context of a Dot1agCfmMaintDomainNameType value.  Every
usage of the Dot1agCfmMaintDomainName textual convention is
required to specify the Dot1agCfmMaintDomainNameType object
that provides the context.  It is suggested that the
Dot1agCfmMaintDomainNameType object be logically registered
before the object(s) that use the Dot1agCfmMaintDomainName
textual convention, if they appear in the same logical row.

The value of a Dot1agCfmMaintDomainName object must always
be consistent with the value of the associated
Dot1agCfmMaintDomainNameType object. Attempts to set
an Dot1agCfmMaintDomainName object to a value inconsistent
with the associated Dot1agCfmMaintDomainNameType must fail
with an inconsistentValue error.

When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, IETF STD 58.  In this
case, the object definition MUST include a 'SIZE' clause
to limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.

A value of none(1) in the associated
Dot1agCfmMaintDomainNameType object means that no
Maintenance Domain name is present, and the contents of the
Dot1agCfmMaintDomainName object are meaningless.

See the DESCRIPTION of the Dot1agCfmMaintAssocNameType
TEXTUAL-CONVENTION for a discussion of the length limits on
the Maintenance Domain name and Maintenance Association
name.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 21.6.5
Source ietf-cfm line 499

Dot1agCfmMaintDomainNameType

Summary

Name Dot1agCfmMaintDomainNameType
Type enumeration
  
 
A value that represents a type (and thereby the format)
of a Dot1agCfmMaintDomainName.

To support future extensions, the
Dot1agCfmMaintDomainNameType textual convention SHOULD NOT
be sub-typed in object type definitions.  It MAY be
sub-typed in compliance statements in order to require only
a subset of these address types for a compliant
implementation.

Implementations must ensure that
Dot1agCfmMaintDomainNameType objects and any dependent
objects (e.g., Dot1agCfmMaintDomainName objects) are
consistent.  An inconsistentValue error must be generated
if an attempt to change an Dot1agCfmMaintDomainNameType
object would, for example, lead to an undefined
Dot1agCfmMaintDomainName value.
In particular,
Dot1agCfmMaintDomainNameType/Dot1agCfmMaintDomainName pairs
must be changed together if the nameType changes.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 21.6.5, Table 21-19
Source ietf-cfm line 447

Dot1agCfmMDLevel

Summary

Name Dot1agCfmMDLevel
Type int32
  
 
Integer identifying the Maintenance Domain Level (MD Level).
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM PDUs.  Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 18.3, 21.4.1
Source ietf-cfm line 691

Dot1agCfmMDLevelOrNone

Summary

Name Dot1agCfmMDLevelOrNone
Type int32
  
 
Integer identifying the Maintenance Domain Level (MD Level).
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM packets.  Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links.

The value (-1) is reserved to indicate that no MA Level has
been assigned.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 18.3, 12.14.3.1.3:c
Source ietf-cfm line 708

Dot1agCfmMepDefects

Summary

Name Dot1agCfmMepDefects
Type bits
  
 
A MEP can detect and report a number of defects, and
multiple defects can be present at the same time.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.7.1.3:o, 12.14.7.1.3:p, 12.14.7.1.3:q, 12.14.7.1.3:r, and 12.14.7.1.3:s.
Source ietf-cfm line 1319

Dot1agCfmMepId

Summary

Name Dot1agCfmMepId
Type uint32
  
 
Maintenance association End Point Identifier (MEPID):
A small integer, unique over a given Maintenance
Association, identifying a specific MEP.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 3.18 and 19.2.1
Source ietf-cfm line 948

Dot1agCfmMepIdOrZero

Summary

Name Dot1agCfmMepIdOrZero
Type uint32
  
 
Maintenance association End Point Identifier (MEPID):
A small integer, unique over a given Maintenance
Association, identifying a specific MEP.

The special value 0 is allowed to indicate special cases,
for example that no MEPID is configured.

Whenever an object is defined with this SYNTAX, then the
DESCRIPTION clause of such an object MUST specify what the
special value of 0 means.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 19.2.1
Source ietf-cfm line 961

Dot1agCfmMhfCreation

Summary

Name Dot1agCfmMhfCreation
Type enumeration
  
 
Indicates if the Management Entity can create MHFs.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.5.1.3:c and 22.2.3
Source ietf-cfm line 981

Dot1agCfmMpDirection

Summary

Name Dot1agCfmMpDirection
Type enumeration
  
 
Indicates the direction in which the Maintenance
association (MEP or MIP) faces on the bridge port.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.6.3.2:c
Source ietf-cfm line 728

Dot1agCfmPbbComponentIdentifier

Summary

Name Dot1agCfmPbbComponentIdentifier
Type uint32
  
 
A Provider Backbone Bridge (PBB) can comprise a number of
components, each of which can be managed in a manner
essentially equivalent to an 802.1Q bridge.  In order to
access these components easily, an index is used in a
number of tables.  If any two tables are indexed by
Dot1agCfmPbbComponentIdentifier, then entries in those
tables indexed by the same value of
Dot1agCfmPbbComponentIdentifier correspond to the same
component.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 17.5
Source ietf-cfm line 1405

Dot1agCfmPortStatus

Summary

Name Dot1agCfmPortStatus
Type enumeration
  
 
An enumerated value from he Port Status TLV from the last
CCM received from the last MEP. It indicates the ability
of the Bridge Port on which the transmitting MEP resides
to pass ordinary data, regardless of the status of the MAC
(Table 21-10).

NOTE: A 0 value is used for psNoPortStateTLV, so that
      additional code points can be added in a manner
      consistent with the Dot1agCfmInterfaceStatus textual
      convention.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clause 12.14.7.6.3:f, 20.19.3 and 21.5.4
Source ietf-cfm line 750

Dot1agCfmRelayActionFieldValue

Summary

Name Dot1agCfmRelayActionFieldValue
Type enumeration
  
 
Possible values the Relay action field can take.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.7.5.3:g, 20.36.2.5, 21.9.5, and Table 21-27
Source ietf-cfm line 1150

Dot1agCfmRemoteMepState

Summary

Name Dot1agCfmRemoteMepState
Type enumeration
  
 
Operational state of the remote MEP state machine.  This
state machine monitors the reception of valid CCMs from a
remote MEP with a specific MEPID.  It uses a timer that
expires in 3.5 times the length of time indicated by the
dot1agCfmMaNetCcmInterval object.

Details

Module ietf-cfm
Version 2017-03-29
Reference 802.1ag clauses 12.14.7.6.3:b, 20.22
Source ietf-cfm line 1251

dot1q-tag-type

Summary

Name dot1q-tag-type
Type identityref
  
 
Identifies a specific 802.1Q tag type

Details

Module ieee802-dot1q-types
Version 2017-07-20
Reference IEEE 802.1Q (2014)
Source ieee802-dot1q-types line 233

dotted-quad

Summary

Name dotted-quad
Type string
  
 
An unsigned 32-bit integer expressed as a dotted quad. The
format is four octets written as decimal numbers separated
with a period character.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 55

dotted-quad

Summary

Name dotted-quad
Type string
  
 
An unsigned 32-bit number expressed in the dotted-quad
notation, i.e., four octets written as decimal numbers
and separated with the '.' (full stop) character.

Details

Module ietf-yang-types
Version 2013-07-15
Source ietf-yang-types line 469

downstream-upstream

Summary

Name downstream-upstream
Type enumeration
  
 
Received or advertised.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 112

dpi-type

Summary

Name dpi-type
Type enumeration
  
 
This is used for dpi type

Details

Module ietf-i2nsf-monitoring-information
Version 2017-07-19
Source ietf-i2nsf-monitoring-information line 90

dpi-type

Summary

Name dpi-type
Type enumeration
  
 
This is used for dpi type

Details

Module ietf-i2nsf-nsf-monitoring-dm
Version 2017-10-29
Source ietf-i2nsf-nsf-monitoring-dm line 89

dscp

Summary

Name dscp
Type uint8
  
 
A differentiated services code point (DSCP) marking within the
IP header.

Details

Module openconfig-inet-types
Version 2017-08-24
Reference RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Source openconfig-inet-types line 279

dscp

Summary

Name dscp
Type uint8
  
 
The dscp type represents a Differentiated Services Code-Point
that may be used for marking packets in a traffic stream.

In the value set and its semantics, this type is equivalent
to the Dscp textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 3289: Management Information Base for the Differentiated Services Architecture RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
Source ietf-inet-types line 78

dscp

Summary

Name dscp
Type uint8
  
 
The dscp type represents a Differentiated Services Code Point
that may be used for marking packets in a traffic stream.
In the value set and its semantics, this type is equivalent
to the Dscp textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 3289: Management Information Base for the Differentiated Services Architecture RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
Source ietf-inet-types line 88

dscp

Summary

Name dscp
Type uint8
  
 
A differentiated services code point (DSCP) marking within the
IP header.

Details

Module openconfig-inet-types
Version 2017-01-26
Reference RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Source openconfig-inet-types line 126

duplex-type

Summary

Name duplex-type
Type enumeration
  
 
The current duplex mode of operation of an Ethernet
interface.

Details

Module ieee802-ethernet-interface
Version 2017-02-23
Reference IEEE Std 802.3, 30.3.1.1.32, aDuplexStatus
Source ieee802-ethernet-interface line 86

duplex-type

Summary

Name duplex-type
Type enumeration
  
 
The current duplex mode of operation of an Ethernet
interface.

Details

Module ieee802-ethernet-interface
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.1.1.32, aDuplexStatus
Source ieee802-ethernet-interface line 67

duration

Summary

Name duration
Type string
  
 
XSD duration string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#duration
Source yuma-xsd line 231

duration32-inf

Summary

Name duration32-inf
Type union
  
 
Duration represented as 32 bit seconds with infinite.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 85

dynamic-rate-control-type

Summary

Name dynamic-rate-control-type
Type enumeration
  
 
Allowed values for dynamic-rate-control

Details

Module ieee802-ethernet-interface-legacy
Version 2017-10-18
Reference IEEE Std 802.3, 4.4.2 ipgStretchRatio and 30.3.1.1.34 aRateControlStatus
Source ieee802-ethernet-interface-legacy line 79

edit-operation-type

Summary

Name edit-operation-type
Type enumeration
  
 
NETCONF 'operation' attribute values

Details

Module ietf-netconf
Version 2011-06-01
Reference RFC 6241, Section 7.2
Source ietf-netconf line 306

edit-operation-type

Summary

Name edit-operation-type
Type enumeration
  
 
NETCONF 'operation' attribute values

Details

Module yuma-netconf
Version 2015-04-30
Reference RFC XXXX, section 7.2.
Source yuma-netconf line 428

egress-action

Summary

Name egress-action
Type enumeration
  
 
This is used for egress action.

Details

Module ietf-i2nsf-nsf-facing-interface
Version 2017-10-30
Source ietf-i2nsf-nsf-facing-interface line 110

eid-id

Summary

Name eid-id
Type string
  
 
Type encoding of lisp-addresses to be generally used in EID
keyed lists.

Details

Module ietf-lisp
Version 2017-07-01
Source ietf-lisp line 118

email-address

Summary

Name email-address
Type string
  
 
This type represents a string with an email address.

Details

Module yang-catalog
Version 2017-09-26
Source yang-catalog line 106

enable

Summary

Name enable
Type boolean
  
 
enable

Details

Module ietf-twamp-light
Version 2017-06-13
Source ietf-twamp-light line 46

enable

Summary

Name enable
Type boolean
  
 
enable

Details

Module ietf-stamp
Version 2017-10-20
Source ietf-stamp line 47

enable

Summary

Name enable
Type boolean
  
 
enable

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 16

encapsulation-header-type

Summary

Name encapsulation-header-type
Type enumeration
  
 
Types of tunnel encapsulation that are supported by systems as either
head- or tail-end.

Details

Module openconfig-aft-types
Version 2017-08-24
Source openconfig-aft-types line 33

encoding

Summary

Name encoding
Type identityref
  
 
Specifies a data encoding, e.g. for a data subscription.

Details

Module ietf-subscribed-notifications
Version 2017-10-27
Source ietf-subscribed-notifications line 307

encoding-type

Summary

Name encoding-type
Type enumeration
  
 
The message encoding format to use

Details

Module yumaworks-types
Version 2015-10-04
Source yumaworks-types line 247

encryption-algorithm-t

Summary

Name encryption-algorithm-t
Type enumeration
  
 
Encryption algorithms -> RFC_5996

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 39

ENTITIES

Summary

Name ENTITIES
Type string
  
 
XSD ENTITIES attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITIES
Source yuma-xsd line 399

ENTITY

Summary

Name ENTITY
Type string
  
 
XSD ENTITY attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITY
Source yuma-xsd line 390

erHopMode

Summary

Name erHopMode
Type enumeration
  
 
TE Hop Address Type

Details

Module ietf-segment-routing-ipv6
Version 2017-10-23
Source ietf-segment-routing-ipv6 line 56

error-info

Summary

Name error-info
Type enumeration
  
 
error-info

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 212

error-severity-type

Summary

Name error-severity-type
Type enumeration
  
 
NETCONF Error Severity

Details

Module ietf-netconf
Version 2011-06-01
Reference RFC 6241, Section 4.3
Source ietf-netconf line 293

error-severity-type

Summary

Name error-severity-type
Type enumeration
  
 
NETCONF Error Severity

Details

Module yuma-netconf
Version 2015-04-30
Reference RFC XXXX, section 4.3.
Source yuma-netconf line 378

error-tag-type

Summary

Name error-tag-type
Type enumeration
  
 
NETCONF Error Tag

Details

Module ietf-netconf
Version 2011-06-01
Reference RFC 6241, Appendix A
Source ietf-netconf line 183

error-tag-type

Summary

Name error-tag-type
Type enumeration
  
 
NETCONF Error Tag

Details

Module yuma-netconf
Version 2015-04-30
Reference RFC 6241, Appendix A.
Source yuma-netconf line 268

ErrorOptionType

Summary

Name ErrorOptionType
Type enumeration
  
 
NETCONF 'error-option' Element Content

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 401

ErrorType

Summary

Name ErrorType
Type enumeration
  
 
NETCONF Error Type

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 255

erSidIpv6Type

Summary

Name erSidIpv6Type
Type enumeration
  
 
TE Hop Address Type

Details

Module ietf-segment-routing-ipv6
Version 2017-10-23
Source ietf-segment-routing-ipv6 line 70

esp-encap

Summary

Name esp-encap
Type enumeration
  
 
type defining types of ESP encapsulation

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 149

eth-if-speed-type

Summary

Name eth-if-speed-type
Type decimal64
  
 
Used to represent the configured, negotiated, or actual speed
of an Ethernet interface in Gigabits per second (Gb/s),
accurate to 3 decimal places (i.e. accurate to 1 Mb/s)

Details

Module ieee802-ethernet-interface
Version 2017-02-23
Source ieee802-ethernet-interface line 75

eth-if-speed-type

Summary

Name eth-if-speed-type
Type decimal64
  
 
Used to represent the configured, negotiated, or actual speed
of an Ethernet interface in Gigabits per second (Gb/s),
accurate to 3 decimal places (i.e. accurate to 1 Mb/s)

Details

Module ieee802-ethernet-interface
Version 2017-10-18
Source ieee802-ethernet-interface line 56

eth-tag-classify

Summary

Name eth-tag-classify
Type identityref
  
 
Identifies a specific VLAN tag classification.

Details

Module ietf-eth-tran-types
Version 2017-09-12
Source ietf-eth-tran-types line 146

eth-tag-type

Summary

Name eth-tag-type
Type identityref
  
 
Identifies a specific ETH VLAN tag type.

Details

Module ietf-eth-tran-types
Version 2017-09-12
Source ietf-eth-tran-types line 138

ethertype

Summary

Name ethertype
Type union
  
 
The uint16 type placeholder type is defined to enable
users to manage their own ethertypes not
covered by the module. Otherwise the module contains
enum definitions for the more commonly used ethertypes.

Details

Module ietf-ethertypes
Version 2017-10-03
Source ietf-ethertypes line 30

ethertype-type

Summary

Name ethertype-type
Type union
  
 
The Ethertype value may be expressed as a 16-bit number in
hexadecimal notation, or using a type defined by the
ETHERTYPE identity

Details

Module openconfig-packet-match-types
Version 2017-05-26
Source openconfig-packet-match-types line 276

ethertype-type

Summary

Name ethertype-type
Type string
  
 
The EtherType value represented in the canonical order defined
     by IEEE 802. The canonical representation uses uppercase
     characters.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Reference IEEE 802-2014 Clause 9.2
Source ieee802-dot1q-types line 221

event-location

Summary

Name event-location
Type enumeration
  
 
The location of the event that caused a log entry

Details

Module ieee802-ethernet-link-oam
Version 2017-10-18
Source ieee802-ethernet-link-oam line 173

event-ref

Summary

Name event-ref
Type leafref
  
 
This type is used by data models that need to reference
a configured event source.

Details

Module ietf-lmap-control
Version 2017-04-21
Source ietf-lmap-control line 47

event-ref

Summary

Name event-ref
Type leafref
  
 
This type is used by data models that need to reference
a configured event source.

Details

Module ietf-lmap-control
Version 2017-08-08
Source ietf-lmap-control line 48

event-type

Summary

Name event-type
Type enumeration
  
 
The event types as defined by X.733 and X.736.  The use of the
term 'event' is a bit confusing.  In an alarm context these
are top level alarm types.

Details

Module ietf-alarms-x733
Version 2017-10-30
Source ietf-alarms-x733 line 63

extended-admin-group

Summary

Name extended-admin-group
Type binary
  
 
Extended administrative group/Resource class/Color.

Details

Module ietf-te-types
Version 2017-10-29
Source ietf-te-types line 1325

extended-circuit-id

Summary

Name extended-circuit-id
Type uint32
  
 
This type defines interface circuit ID.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 313

extended-circuit-id

Summary

Name extended-circuit-id
Type uint32
  
 
This type defines the extended circuit ID
associated with an interface.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 239

fabric-port-role

Summary

Name fabric-port-role
Type enumeration
  
 
the role of the physical port 

Details

Module ietf-fabric-types
Version 2017-11-29
Source ietf-fabric-types line 180

fabric-port-type

Summary

Name fabric-port-type
Type enumeration
  
 
fabric port type

Details

Module ietf-fabric-types
Version 2017-11-29
Source ietf-fabric-types line 198

failure-mode

Summary

Name failure-mode
Type enumeration
  
 
Type to define Openflow failure mode.

Details

Module openconfig-openflow-types
Version 2017-08-24
Source openconfig-openflow-types line 36

fec-capability

Summary

Name fec-capability
Type enumeration
  
 
Enumeration of valid FEC capability values for Ethernet
interfaces with enabled MPCP

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.5.1.1.15
Source ieee802-ethernet-pon line 317

fec-mode

Summary

Name fec-mode
Type enumeration
  
 
Enumeration of valid FEC modes for Ethernet interfaces

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.5.1.1.16
Source ieee802-ethernet-pon line 343

fill-mode

Summary

Name fill-mode
Type enumeration
  
 
Indicates whether the padding added to the
UDP test packets will contain pseudo-random numbers, or
whether it should consist of all zeroes.

Details

Module ietf-twamp
Version 2015-06-30
Source ietf-twamp line 120

filter-id

Summary

Name filter-id
Type string
  
 
A type to identify filters which can be associated with a
subscription.

Details

Module ietf-subscribed-notifications
Version 2017-10-27
Source ietf-subscribed-notifications line 282

FilterType

Summary

Name FilterType
Type enumeration
  
 
NETCONF 'filter' Attribute Content

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 411

flexi-grid-link-ref

Summary

Name flexi-grid-link-ref
Type leafref
  
 
This type is used by data models that need to reference
a flexi-grid optical link.

Details

Module ietf-flexi-grid-ted
Version 2017-07-03
Source ietf-flexi-grid-ted line 87

flexi-grid-node-port-ref

Summary

Name flexi-grid-node-port-ref
Type leafref
  
 
This type is used by data models that need to reference
a flexi-grid port.

Details

Module ietf-flexi-grid-ted
Version 2017-07-03
Source ietf-flexi-grid-ted line 98

flexi-grid-transponder-ref

Summary

Name flexi-grid-transponder-ref
Type leafref
  
 
This type is used by data models that need to reference
a trasponder.

Details

Module ietf-flexi-grid-ted
Version 2017-07-03
Source ietf-flexi-grid-ted line 109

FormatType

Summary

Name FormatType
Type enumeration
  
 
Conversion Output Formats.

Details

Module yangdump-pro
Version 2017-06-14
Source yangdump-pro line 214

frequency-type

Summary

Name frequency-type
Type uint64
  
 
Type for optical spectrum frequency values

Details

Module openconfig-transport-types
Version 2017-08-16
Source openconfig-transport-types line 40

gal-mode

Summary

Name gal-mode
Type enumeration
  
 
gal mode

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 284

gate-state-value-type

Summary

Name gate-state-value-type
Type enumeration
  
 
The PSFPgateStatesValue indicates the desired gate state, open
or closed, for the stream gate.

Details

Module ieee802-dot1q-stream-filters-gates
Version 2017-12-20
Reference IEEE 802.1Qci: Clause 12.31.3.2.1
Source ieee802-dot1q-stream-filters-gates line 106

gauge32

Summary

Name gauge32
Type uint32
  
 
The gauge32 type represents a non-negative integer, which
may increase or decrease, but shall never exceed a maximum
value, nor fall below a minimum value.  The maximum value
cannot be greater than 2^32-1 (4294967295 decimal), and
the minimum value cannot be smaller than 0.  The value of
a gauge32 has its maximum value whenever the information
being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the
gauge32 also decreases (increases).

In the value set and its semantics, this type is equivalent
to the Gauge32 type of the SMIv2.

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 158

gauge32

Summary

Name gauge32
Type uint32
  
 
The gauge32 type represents a non-negative integer, which
may increase or decrease, but shall never exceed a maximum
value, nor fall below a minimum value.  The maximum value
cannot be greater than 2^32-1 (4294967295 decimal), and
the minimum value cannot be smaller than 0.  The value of
a gauge32 has its maximum value whenever the information
being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the
gauge32 also decreases (increases).

In the value set and its semantics, this type is equivalent
to the Gauge32 type of the SMIv2.

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-types line 176

gauge64

Summary

Name gauge64
Type uint64
  
 
A gauge value may increase or decrease - and reflects a value
at a particular point in time. If the value of the variable
being modeled using the gauge exceeds its maximum - 2^64-1 in
this case - the gauge is set to its maximum value.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 131

gauge64

Summary

Name gauge64
Type uint64
  
 
The gauge64 type represents a non-negative integer, which
may increase or decrease, but shall never exceed a maximum
value, nor fall below a minimum value.  The maximum value
cannot be greater than 2^64-1 (18446744073709551615), and
the minimum value cannot be smaller than 0.  The value of
a gauge64 has its maximum value whenever the information
being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the
gauge64 also decreases (increases).

In the value set and its semantics, this type is equivalent
to the CounterBasedGauge64 SMIv2 textual convention defined
in RFC 2856

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 2856: Textual Conventions for Additional High Capacity Data Types
Source ietf-yang-types line 180

gauge64

Summary

Name gauge64
Type uint64
  
 
The gauge64 type represents a non-negative integer, which
may increase or decrease, but shall never exceed a maximum
value, nor fall below a minimum value.  The maximum value
cannot be greater than 2^64-1 (18446744073709551615), and
the minimum value cannot be smaller than 0.  The value of
a gauge64 has its maximum value whenever the information
being modeled is greater than or equal to its maximum
value, and has its minimum value whenever the information
being modeled is smaller than or equal to its minimum value.
If the information being modeled subsequently decreases
below (increases above) the maximum (minimum) value, the
gauge64 also decreases (increases).

In the value set and its semantics, this type is equivalent
to the CounterBasedGauge64 SMIv2 textual convention defined
in RFC 2856

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 2856: Textual Conventions for Additional High Capacity Data Types
Source ietf-yang-types line 199

gDay

Summary

Name gDay
Type string
  
 
XSD day string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#gDay
Source yuma-xsd line 307

generalized-label

Summary

Name generalized-label
Type binary
  
 
Generalized label. Nodes sending and receiving the
Generalized Label know the kinds of link they are
using. Hence, the Generalized Label does not identify
its type.  Instead, nodes are expected to know from
the context and type of label to expect.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC3471: Section 3.2
Source ietf-routing-types line 504

generalized-label

Summary

Name generalized-label
Type binary
  
 
Generalized label. Nodes sending and receiving the
Generalized Label are aware of the link-specific
label context and type.

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC3471: Section 3.2
Source ietf-routing-types line 631

generalized-label

Summary

Name generalized-label
Type binary
  
 
Generalized label. Nodes sending and receiving the
Generalized Label know the kinds of link they are
using. Hence, the Generalized Label does not identify
its type.  Instead, nodes are expected to know from
the context and type of label to expect.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC3471: Section 3.2
Source ietf-routing-types line 473

geographic-coordinate-degree

Summary

Name geographic-coordinate-degree
Type decimal64
  
 
Decimal degree (DD) used to express latitude and longitude
geographic coordinates.

Details

Module ietf-te-topology
Version 2017-10-25
Source ietf-te-topology line 95

glob-pattern

Summary

Name glob-pattern
Type string
  
 
A glob style pattern (following POSIX.2 fnmatch() without
       special treatment of file paths):

         *         matches a sequence of characters
         ?         matches a single character
         [seq]     matches any character in seq
         [!seq]    matches any character not in seq

       A backslash followed by a character matches the following
       character. In particular:

         *        matches *
         ?        matches ?
         \        matches 

       A sequence seq may be a sequence of characters (e.g., [abc]
       or a range of characters (e.g., [a-c]).

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 57

glob-pattern

Summary

Name glob-pattern
Type string
  
 
A glob style pattern (following POSIX.2 fnmatch() without
       special treatment of file paths):

         *         matches a sequence of characters
         ?         matches a single character
         [seq]     matches any character in seq
         [!seq]    matches any character not in seq

       A backslash followed by a character matches the following
       character.  In particular:

         *        matches *
         ?        matches ?
         \        matches 

       A sequence seq may be a sequence of characters (e.g., [abc]
       or a range of characters (e.g., [a-c]).

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 58

gMonth

Summary

Name gMonth
Type string
  
 
XSD month string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#gMonth
Source yuma-xsd line 289

gMonthDay

Summary

Name gMonthDay
Type string
  
 
XSD month and day string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#gMonthDay
Source yuma-xsd line 298

group-name-type

Summary

Name group-name-type
Type string
  
 
Name of administrative group to which
users can be assigned.

Details

Module ietf-netconf-acm
Version 2012-02-22
Source ietf-netconf-acm line 142

group-name-type

Summary

Name group-name-type
Type string
  
 
Name of administrative group to which
users can be assigned.

Details

Module ietf-netconf-acm
Version 2017-12-11
Source ietf-netconf-acm line 149

Guaranteed-DL-Bit-Rate-Value

Summary

Name Guaranteed-DL-Bit-Rate-Value
Type uint32
  
 
The guaranteed bandwidth in bits per second for downlink
 IP flows.  The measurement units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 387

Guaranteed-UL-Bit-Rate-Value

Summary

Name Guaranteed-UL-Bit-Rate-Value
Type uint32
  
 
The guaranteed bandwidth in bits per second for uplink
IP flows.  The measurement units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 394

gYear

Summary

Name gYear
Type string
  
 
XSD year string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#gYear
Source yuma-xsd line 271

gYearMonth

Summary

Name gYearMonth
Type string
  
 
XSD year and month string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#gYearMonth
Source yuma-xsd line 280

hello-padding-type

Summary

Name hello-padding-type
Type enumeration
  
 
This type defines ISIS hello padding type

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 186

hex-string

Summary

Name hex-string
Type string
  
 
A string consisting of a hexadecimal characters.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 67

hex-string

Summary

Name hex-string
Type string
  
 
A hexadecimal string with octets represented as hex digits
separated by colons.  The canonical representation uses
lowercase characters.

Details

Module ietf-yang-types
Version 2013-07-15
Source ietf-yang-types line 441

hexBinary

Summary

Name hexBinary
Type binary
  
 
XSD hex binary encoded string

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#hexBinary
Source yuma-xsd line 65

hop-limit-action-def

Summary

Name hop-limit-action-def
Type identityref
  
 
IPv6 hop limit action def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 259

hops

Summary

Name hops
Type uint8
  
 
This corresponds to Time To Live for IPv4 and corresponds to hop
limit for IPv6

Details

Module ietf-bfd-types
Version 2017-10-30
Source ietf-bfd-types line 102

host

Summary

Name host
Type union
  
 
The host type represents either an unzoned IP address or a DNS
domain name.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 253

host

Summary

Name host
Type union
  
 
The host type represents either an IP address or a DNS
domain name.

Details

Module ietf-inet-types
Version 2010-09-24
Source ietf-inet-types line 378

host

Summary

Name host
Type union
  
 
The host type represents either an IP address or a DNS
domain name.

Details

Module ietf-inet-types
Version 2013-07-15
Source ietf-inet-types line 412

hour

Summary

Name hour
Type uint8
  
 
An hour of a day.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 249

hour

Summary

Name hour
Type uint8
  
 
An hour of a day.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 252

hour-or-all

Summary

Name hour-or-all
Type union
  
 
An hour of a day or a wildcard indicating all hours
of a day.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 255

hour-or-all

Summary

Name hour-or-all
Type union
  
 
An hour of a day or a wildcard indicating all hours
of a day.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 258

i-sid-type

Summary

Name i-sid-type
Type uint32
  
 
I-SID type that is 24-bits. This should be moved to ieee-types.yang at http://www.ieee802.org/1/files/public/docs2015/new-mholness-ieee-types-yang-v01.yang

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 389

IANAifType

Summary

Name IANAifType
Type enumeration
  
 
This data type is used as the syntax of the ifType
object in the (updated) definition of MIB-II's
ifTable.

The definition of this textual convention with the
addition of newly assigned values is published
periodically by the IANA, in either the Assigned
Numbers RFC, or some derivative of it specific to
Internet Network Management number assignments.  (The
latest arrangements can be obtained by contacting the
IANA.)

Requests for new values should be made to IANA via
email (iana&iana.org).

The relationship between the assignment of ifType
values and of OIDs to particular media-specific MIBs
is solely the purview of IANA and is subject to change
without notice.  Quite often, a media-specific MIB's
OID-subtree assignment within MIB-II's 'transmission'
subtree will be the same as its ifType value.
However, in some circumstances this will not be the
case, and implementors must not pre-assume any
specific relationship between ifType values and
transmission subtree OIDs.

Details

Module IANAifType-MIB
Version 2016-06-16
Source IANAifType-MIB line 476

IANAtunnelType

Summary

Name IANAtunnelType
Type enumeration
  
 
The encapsulation method used by a tunnel. The value
direct indicates that a packet is encapsulated
directly within a normal IP header, with no
intermediate header, and unicast to the remote tunnel
endpoint (e.g., an RFC 2003 IP-in-IP tunnel, or an RFC
1933 IPv6-in-IPv4 tunnel). The value minimal indicates
that a Minimal Forwarding Header (RFC 2004) is
inserted between the outer header and the payload
packet. The value UDP indicates that the payload
packet is encapsulated within a normal UDP packet
(e.g., RFC 1234).

The values sixToFour, sixOverFour, and isatap
indicates that an IPv6 packet is encapsulated directly
within an IPv4 header, with no intermediate header,
and unicast to the destination determined by the 6to4,
6over4, or ISATAP protocol.

The remaining protocol-specific values indicate that a
header of the protocol of that name is inserted
between the outer header and the payload header.

The IP Tunnel MIB [RFC4087] is designed to manage
tunnels of any type over IPv4 and IPv6 networks;
therefore, it already supports IP-in-IP tunnels.
But in a DS-Lite scenario, the tunnel type is
point-to-multipoint IP-in-IP tunnels.  The direct(2)
defined in the IP Tunnel MIB only supports point-to-point
tunnels.  So, it needs to define a new tunnel type for
DS-Lite.

The assignment policy for IANAtunnelType values is
identical to the policy for assigning IANAifType
values.

Details

Module IANAifType-MIB
Version 2016-06-16
Source IANAifType-MIB line 1341

ID

Summary

Name ID
Type string
  
 
XSD ID attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID
Source yuma-xsd line 363

identifier

Summary

Name identifier
Type string
  
 
An string value used to name something.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 41

identifier

Summary

Name identifier
Type string
  
 
A string value used to name something.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 42

IdentifierOrZero

Summary

Name IdentifierOrZero
Type union
  
 
Indicates an identifier or empty string to use the
schema or application defined default.

Details

Module yangcli-pro
Version 2017-12-12
Source yangcli-pro line 398

IDREF

Summary

Name IDREF
Type string
  
 
XSD IDREF attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREF
Source yuma-xsd line 372

IDREFS

Summary

Name IDREFS
Type string
  
 
XSD IDREFS attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREFS
Source yuma-xsd line 381

ieee-bandwidth

Summary

Name ieee-bandwidth
Type string
  
 
Bandwidth in IEEE 754 floating point 32-bit binary format:
(-1)**(S) * 2**(Exponent-127) * (1 + Fraction),
where Exponent uses 8 bits, and Fraction uses 23 bits.
The units are octets per second.
The encoding format is the external hexadecimal-significand
character sequences specified in IEEE 754 and C99,
restricted to be normalized, non-negative, and non-fraction:
0x1.hhhhhhp{+}d or 0X1.HHHHHHP{+}D
where 'h' and 'H' are hexadecimal digits, 'd' and 'D' are
integers in the range of [0..127].
When six hexadecimal digits are used for 'hhhhhh' or 'HHHHHH',
the least significant digit must be an even number.
'x' and 'X' indicate hexadecimal; 'p' and 'P' indicate power
of two.
Some examples are: 0x0p0, 0x1p10, and 0x1.abcde2p+20

Details

Module ietf-routing-types
Version 2017-02-19
Reference IEEE Std 754-2008: IEEE Standard for Floating-Point Arithmetic.
Source ietf-routing-types line 391

ieeefloat32

Summary

Name ieeefloat32
Type binary
  
 
An IEEE 32-bit floating point number. The format of this number
is of the form:
 1-bit  sign
 8-bit  exponent
 23-bit fraction
The floating point value is calculated using:
 (-1)**S * 2**(Exponent-127) * (1+Fraction)

Details

Module openconfig-types
Version 2017-08-16
Source openconfig-types line 84

ieIdType

Summary

Name ieIdType
Type uint16
  
 
Type for Information Element identifiers.

Details

Module ietf-ipfix-psamp
Version 2012-09-05
Source ietf-ipfix-psamp line 266

ieNameType

Summary

Name ieNameType
Type string
  
 
Type for Information Element names.  Whitespaces
are not allowed.

Details

Module ietf-ipfix-psamp
Version 2012-09-05
Source ietf-ipfix-psamp line 257

if-index

Summary

Name if-index
Type leafref
  
 
This type is used by data models that need to reference
configured interfaces.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 58

if-index-or-zero

Summary

Name if-index-or-zero
Type int32
  
 
This textual convention is an extension of the
InterfaceIndex convention.  The latter defines a greater
than zero value used to identify an interface or interface
sub-layer in the managed system.  This extension permits the
additional value of zero.  the value zero is object-specific
and must therefore be defined as part of the description of
any object which uses this syntax.  Examples of the usage of
zero might include situations where interface was unknown,
or when none or all interfaces need to be referenced.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 67

if-state-type

Summary

Name if-state-type
Type enumeration
  
 
OSPF interface state type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 500

if-state-type

Summary

Name if-state-type
Type enumeration
  
 
This type defines states of an interface

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 313

ifNameType

Summary

Name ifNameType
Type string
  
 
This corresponds to the DisplayString textual
convention of SNMPv2-TC, which is used for ifName in the IF
MIB module.

Details

Module ietf-ipfix-psamp
Version 2012-09-05
Reference RFC 2863 (ifName).
Source ietf-ipfix-psamp line 287

igmp-snooping-instance-ref

Summary

Name igmp-snooping-instance-ref
Type leafref
  
 
This type is used by data models that need to reference igmp
snooping instance.

Details

Module ietf-igmp-mld-snooping
Version 2017-10-25
Source ietf-igmp-mld-snooping line 163

igp-type

Summary

Name igp-type
Type enumeration
  
 
The IGP type

Details

Module ietf-bier
Version 2017-08-10
Source ietf-bier line 194

IndentType

Summary

Name IndentType
Type uint32
  
 
Requested indent amount.
Only a limited range of line indent values are allowed.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 306

InetAddress

Summary

Name InetAddress
Type binary
  
 
Denotes a generic Internet address.

An InetAddress value is always interpreted within the context
of an InetAddressType value.  Every usage of the InetAddress
textual convention is required to specify the InetAddressType
object that provides the context.  It is suggested that the
InetAddressType object be logically registered before the
object(s) that use the InetAddress textual convention, if
they appear in the same logical row.

The value of an InetAddress object must always be
consistent with the value of the associated InetAddressType
object.  Attempts to set an InetAddress object to a value
inconsistent with the associated InetAddressType
must fail with an inconsistentValue error.

When this textual convention is used as the syntax of an
index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, STD 58.  In this case,
the object definition MUST include a 'SIZE' clause to
limit the number of potential instance sub-identifiers;
otherwise the applicable constraints MUST be stated in
the appropriate conceptual row DESCRIPTION clauses, or
in the surrounding documentation if there is no single
DESCRIPTION clause that is appropriate.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 128

InetAddressDNS

Summary

Name InetAddressDNS
Type string
  
 
Represents a DNS domain name.  The name SHOULD be fully
qualified whenever possible.

The corresponding InetAddressType is dns(16).

The DESCRIPTION clause of InetAddress objects that may have
InetAddressDNS values MUST fully describe how (and when)
these names are to be resolved to IP addresses.

The resolution of an InetAddressDNS value may require to
query multiple DNS records (e.g., A for IPv4 and AAAA for
IPv6).  The order of the resolution process and which DNS
record takes precedence depends on the configuration of the
resolver.

This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 257

InetAddressIPv4

Summary

Name InetAddressIPv4
Type string
  
 
Represents an IPv4 network address:

Octets   Contents         Encoding
 1-4     IPv4 address     network-byte order

The corresponding InetAddressType value is ipv4(1).

This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 160

InetAddressIPv4z

Summary

Name InetAddressIPv4z
Type string
  
 
Represents a non-global IPv4 network address, together
with its zone index:

  Octets   Contents         Encoding
   1-4     IPv4 address     network-byte order
   5-8     zone index       network-byte order

The corresponding InetAddressType value is ipv4z(3).

The zone index (bytes 5-8) is used to disambiguate identical
address values on nodes that have interfaces attached to
different zones of the same scope.  The zone index may contain
the special value 0, which refers to the default zone for each
scope.

This textual convention SHOULD NOT be used directly in object

definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 200

InetAddressIPv6

Summary

Name InetAddressIPv6
Type string
  
 
Represents an IPv6 network address:

Octets   Contents         Encoding
 1-16    IPv6 address     network-byte order

The corresponding InetAddressType value is ipv6(2).

This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 180

InetAddressIPv6z

Summary

Name InetAddressIPv6z
Type string
  
 
Represents a non-global IPv6 network address, together
with its zone index:

  Octets   Contents         Encoding
   1-16    IPv6 address     network-byte order
  17-20    zone index       network-byte order

The corresponding InetAddressType value is ipv6z(4).

The zone index (bytes 17-20) is used to disambiguate
identical address values on nodes that have interfaces
attached to different zones of the same scope.  The zone index
may contain the special value 0, which refers to the default
zone for each scope.

This textual convention SHOULD NOT be used directly in object
definitions, as it restricts addresses to a specific format.
However, if it is used, it MAY be used either on its own or in
conjunction with InetAddressType, as a pair.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 229

InetAddressPrefixLength

Summary

Name InetAddressPrefixLength
Type uint32
  
 
Denotes the length of a generic Internet network address
prefix.  A value of n corresponds to an IP address mask
that has n contiguous 1-bits from the most significant
bit (MSB), with all other bits set to 0.

An InetAddressPrefixLength value is always interpreted within
the context of an InetAddressType value.  Every usage of the
InetAddressPrefixLength textual convention is required to
specify the InetAddressType object that provides the
context.  It is suggested that the InetAddressType object be
logically registered before the object(s) that use the
InetAddressPrefixLength textual convention, if they appear
in the same logical row.

InetAddressPrefixLength values larger than
the maximum length of an IP address for a specific
InetAddressType are treated as the maximum significant
value applicable for the InetAddressType.  The maximum
significant value is 32 for the InetAddressType
'ipv4(1)' and 'ipv4z(3)' and 128 for the InetAddressType
'ipv6(2)' and 'ipv6z(4)'.  The maximum significant value
for the InetAddressType 'dns(16)' is 0.

The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax.  Examples of the usage of zero might include
situations where the Internet network address prefix
is unknown or does not apply.

The upper bound of the prefix length has been chosen to
be consistent with the maximum size of an InetAddress.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 285

InetAddressType

Summary

Name InetAddressType
Type enumeration
  
 
A value that represents a type of Internet address.

unknown(0)  An unknown address type.  This value MUST
	    be used if the value of the corresponding
	    InetAddress object is a zero-length string.
	    It may also be used to indicate an IP address
	    that is not in one of the formats defined
	    below.

ipv4(1)     An IPv4 address as defined by the
	    InetAddressIPv4 textual convention.

ipv6(2)     An IPv6 address as defined by the
	    InetAddressIPv6 textual convention.

ipv4z(3)    A non-global IPv4 address including a zone
	    index as defined by the InetAddressIPv4z
	    textual convention.

ipv6z(4)    A non-global IPv6 address including a zone
	    index as defined by the InetAddressIPv6z
	    textual convention.

dns(16)     A DNS domain name as defined by the
	    InetAddressDNS textual convention.

Each definition of a concrete InetAddressType value must be
accompanied by a definition of a textual convention for use
with that InetAddressType.

To support future extensions, the InetAddressType textual
convention SHOULD NOT be sub-typed in object type definitions.
It MAY be sub-typed in compliance statements in order to
require only a subset of these address types for a compliant
implementation.

Implementations must ensure that InetAddressType objects
and any dependent objects (e.g., InetAddress objects) are
consistent.  An inconsistentValue error must be generated
if an attempt to change an InetAddressType object would,
for example, lead to an undefined InetAddress value.  In

particular, InetAddressType/InetAddress pairs must be
changed together if the address type changes (e.g., from
ipv6(2) to ipv4(1)).

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Source INET-ADDRESS-MIB line 71

InetAutonomousSystemNumber

Summary

Name InetAutonomousSystemNumber
Type uint32
  
 
Represents an autonomous system number that identifies an
Autonomous System (AS).  An AS is a set of routers under a
single technical administration, using an interior gateway
protocol and common metrics to route packets within the AS,
and using an exterior gateway protocol to route packets to
other ASes'.  IANA maintains the AS number space and has
delegated large parts to the regional registries.

Autonomous system numbers are currently limited to 16 bits
(0..65535).  There is, however, work in progress to enlarge the
autonomous system number space to 32 bits.  Therefore, this
textual convention uses an Unsigned32 value without a
range restriction in order to support a larger autonomous
system number space.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Reference RFC 1771, RFC 1930
Source INET-ADDRESS-MIB line 345

InetPortNumber

Summary

Name InetPortNumber
Type uint32
  
 
Represents a 16 bit port number of an Internet transport

layer protocol.  Port numbers are assigned by IANA.  A
current list of all assignments is available from
<http://www.iana.org/>.

The value zero is object-specific and must be defined as
part of the description of any object that uses this
syntax.  Examples of the usage of zero might include
situations where a port number is unknown, or when the
value zero is used as a wildcard in a filter.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Reference STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960
Source INET-ADDRESS-MIB line 324

InetScopeType

Summary

Name InetScopeType
Type enumeration
  
 
Represents a scope type.  This textual convention can be used
in cases where a MIB has to represent different scope types
and there is no context information, such as an InetAddress
object, that implicitly defines the scope type.

Note that not all possible values have been assigned yet, but
they may be assigned in future revisions of this specification.
Applications should therefore be able to deal with values
not yet assigned.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Reference RFC 3513
Source INET-ADDRESS-MIB line 367

InetVersion

Summary

Name InetVersion
Type enumeration
  
 
A value representing a version of the IP protocol.

unknown(0)  An unknown or unspecified version of the IP
	    protocol.

ipv4(1)     The IPv4 protocol as defined in RFC 791 (STD 5).

ipv6(2)     The IPv6 protocol as defined in RFC 2460.

Note that this textual convention SHOULD NOT be used to
distinguish different address types associated with IP
protocols.  The InetAddressType has been designed for this
purpose.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Reference RFC 791, RFC 2460
Source INET-ADDRESS-MIB line 415

InetZoneIndex

Summary

Name InetZoneIndex
Type uint32
  
 
A zone index identifies an instance of a zone of a
specific scope.

The zone index MUST disambiguate identical address
values.  For link-local addresses, the zone index will
typically be the interface index (ifIndex as defined in the
IF-MIB) of the interface on which the address is configured.

The zone index may contain the special value 0, which refers
to the default zone.  The default zone may be used in cases
where the valid zone index is not known (e.g., when a
management application has to write a link-local IPv6
address without knowing the interface index value).  The
default zone SHOULD NOT be used as an easy way out in
cases where the zone index for a non-global IPv6 address
is known.

Details

Module INET-ADDRESS-MIB
Version 2005-02-04
Reference RFC4007
Source INET-ADDRESS-MIB line 391

ingress-action

Summary

Name ingress-action
Type enumeration
  
 
This is used for ingress action.

Details

Module ietf-i2nsf-nsf-facing-interface
Version 2017-10-30
Source ietf-i2nsf-nsf-facing-interface line 83

instance-id-type

Summary

Name instance-id-type
Type uint32
  
 
Defines the range of values for an Instance ID.

Details

Module ietf-lisp-address-types
Version 2015-11-05
Source ietf-lisp-address-types line 181

instance-state-ref

Summary

Name instance-state-ref
Type leafref
  
 
This type is used for leaves that reference state data of
an ISIS protocol instance.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 221

instance-type

Summary

Name instance-type
Type enumeration
  
 
Instance type.

Details

Module ietf-address-pool
Version 2015-10-14
Source ietf-address-pool line 79

int

Summary

Name int
Type int32
  
 
XSD 32 bit signed integer.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#int
Source yuma-xsd line 162

int

Summary

Name int
Type int32
  
 
Changed int base type to int32 for YANG

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 61

integer

Summary

Name integer
Type string
  
 
XSD unbounded integer type.
This cannot be given a range like a number.
This pattern does not supoort string representations
of numbers, such as one two three

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#integer
Source yuma-xsd line 74

integrity-algorithm-t

Summary

Name integrity-algorithm-t
Type enumeration
  
 
Integrity Algorithms -> RFC_5996

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 89

interface-event-type

Summary

Name interface-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-base
Version 2017-02-19
Source ietf-pim-base line 135

interface-event-type

Summary

Name interface-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-base
Version 2017-03-09
Source ietf-pim-base line 106

interface-id

Summary

Name interface-id
Type string
  
 
User-defined identifier for an interface, generally used to
name a interface reference.  The id can be arbitrary but a
useful convention is to use a combination of base interface
name and subinterface index.

Details

Module openconfig-interfaces
Version 2017-12-21
Source openconfig-interfaces line 94

interface-ref

Summary

Name interface-ref
Type leafref
  
 
This type is used by data models that need to reference
interfaces.

Details

Module ietf-interfaces
Version 2017-12-16
Source ietf-interfaces line 55

interface-ref

Summary

Name interface-ref
Type leafref
  
 
This type is used by data models that need to reference
configured interfaces.

Details

Module ietf-interfaces
Version 2014-05-08
Source ietf-interfaces line 54

interface-state-ref

Summary

Name interface-state-ref
Type leafref
  
 
This type is used by data models that need to reference
the operationally present interfaces.

Details

Module example-ietf-interfaces
Version 2017-06-27
Source example-ietf-interfaces line 32

interface-state-ref

Summary

Name interface-state-ref
Type leafref
  
 
This type is used by data models that need to reference
the operationally present interfaces.

Details

Module ietf-interfaces
Version 2017-12-16
Source ietf-interfaces line 653

interface-state-ref

Summary

Name interface-state-ref
Type leafref
  
 
This type is used by data models that need to reference
the operationally present interfaces.

Details

Module ietf-interfaces
Version 2014-05-08
Source ietf-interfaces line 63

interface-type

Summary

Name interface-type
Type enumeration
  
 
Enumeration that defines if an interface is numbered or
unnumbered

Details

Module ietf-flexi-grid-ted
Version 2017-07-03
Source ietf-flexi-grid-ted line 71

interface-type

Summary

Name interface-type
Type enumeration
  
 
This type defines the type of adjacency
to be established on the interface.
This is affecting the type of hello
message that would be used.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 246

InterfaceIndex

Summary

Name InterfaceIndex
Type int32
  
 
A unique value, greater than zero, for each interface or
interface sub-layer in the managed system.  It is
recommended that values are assigned contiguously starting
from 1.  The value for each interface sub-layer must remain
constant at least from one re-initialization of the entity's
network management system to the next re-initialization.

Details

Module IF-MIB
Version 2000-06-14
Source IF-MIB line 85

InterfaceIndex

Summary

Name InterfaceIndex
Type int32

Details

Module test-if-mib
Version 2017-03-19
Source test-if-mib line 33

InterfaceIndexOrZero

Summary

Name InterfaceIndexOrZero
Type int32
  
 
This textual convention is an extension of the
InterfaceIndex convention.  The latter defines a greater
than zero value used to identify an interface or interface
sub-layer in the managed system.  This extension permits the
additional value of zero.  the value zero is object-specific
and must therefore be defined as part of the description of
any object which uses this syntax.  Examples of the usage of
zero might include situations where interface was unknown,
or when none or all interfaces need to be referenced.

Details

Module IF-MIB
Version 2000-06-14
Source IF-MIB line 99

InterfaceIndexOrZero

Summary

Name InterfaceIndexOrZero
Type int32

Details

Module test-if-mib
Version 2017-03-19
Source test-if-mib line 40

interval

Summary

Name interval
Type decimal64
  
 
Interval between packets in milliseconds.
0 means no packets are sent.

Details

Module ietf-connection-oriented-oam
Version 2017-06-01
Source ietf-connection-oriented-oam line 205

ip-address

Summary

Name ip-address
Type union
  
 
An IPv4 or IPv6 address with no prefix specified.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 168

ip-address

Summary

Name ip-address
Type union
  
 
The ip-address type represents an IP address and is IP
version neutral.  The format of the textual representations
implies the IP version.

Details

Module ietf-inet-types
Version 2010-09-24
Source ietf-inet-types line 170

ip-address

Summary

Name ip-address
Type union
  
 
The ip-address type represents an IP address and is IP
version neutral.  The format of the textual representation
implies the IP version.  This type supports scoped addresses
by allowing zone identifiers in the address format.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 4007: IPv6 Scoped Address Architecture
Source ietf-inet-types line 179

ip-address

Summary

Name ip-address
Type union
  
 
An IPv4 or IPv6 address with no prefix specified.

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 92

ip-address-no-zone

Summary

Name ip-address-no-zone
Type union
  
 
The ip-address-no-zone type represents an IP address and is
IP version neutral.  The format of the textual representation
implies the IP version.  This type does not support scoped
addresses since it does not allow zone identifiers in the
address format.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 4007: IPv6 Scoped Address Architecture
Source ietf-inet-types line 250

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module openconfig-if-ip
Version 2017-12-21
Source openconfig-if-ip line 78

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module ietf-ip
Version 2014-06-16
Source ietf-ip line 93

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module ietf-ip
Version 2017-12-16
Source ietf-ip line 79

ip-multicast-group-address

Summary

Name ip-multicast-group-address
Type union
  
 
This type represents an IP multicast group address and is IP
version neutral. The format of the textual representation
implies the IP version.

Details

Module ietf-routing-types
Version 2017-02-19
Source ietf-routing-types line 351

ip-multicast-group-address

Summary

Name ip-multicast-group-address
Type union
  
 
This type represents a version-neutral IP multicast group
address. The format of the textual representation implies
the IP version.

Details

Module ietf-routing-types
Version 2017-10-13
Source ietf-routing-types line 443

ip-multicast-group-address

Summary

Name ip-multicast-group-address
Type union
  
 
This type represents an IP multicast group address and is IP
version neutral. The format of the textual representation
implies the IP version.

Details

Module ietf-routing-types
Version 2017-02-27
Source ietf-routing-types line 329

ip-prefix

Summary

Name ip-prefix
Type union
  
 
An IPv4 or IPv6 prefix.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 177

ip-prefix

Summary

Name ip-prefix
Type union
  
 
The ip-prefix type represents an IP prefix and is IP
version neutral.  The format of the textual representations
implies the IP version.

Details

Module ietf-inet-types
Version 2010-09-24
Source ietf-inet-types line 246

ip-prefix

Summary

Name ip-prefix
Type union
  
 
The ip-prefix type represents an IP prefix and is IP
version neutral.  The format of the textual representations
implies the IP version.

Details

Module ietf-inet-types
Version 2013-07-15
Source ietf-inet-types line 290

ip-prefix

Summary

Name ip-prefix
Type union
  
 
An IPv4 or IPv6 prefix.

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 101

ip-protocol-type

Summary

Name ip-protocol-type
Type union
  
 
The IP protocol number may be expressed as a valid protocol
number (integer) or using a protocol type defined by the
IP_PROTOCOL identity

Details

Module openconfig-packet-match-types
Version 2017-05-26
Source openconfig-packet-match-types line 261

ip-route-match-type-def

Summary

Name ip-route-match-type-def
Type identityref
  
 
IP route match type def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 345

ip-version

Summary

Name ip-version
Type enumeration
  
 
This value represents the version of the IP protocol.
Note that integer representation of the enumerated values
are not specified, and are not required to follow the
InetVersion textual convention in SMIv2.

Details

Module openconfig-inet-types
Version 2017-08-24
Reference RFC 791: Internet Protocol RFC 2460: Internet Protocol, Version 6 (IPv6) Specification RFC 4001: Textual Conventions for Internet Network Addresses
Source openconfig-inet-types line 186

ip-version

Summary

Name ip-version
Type enumeration
  
 
This value represents the version of the IP protocol.

In the value set and its semantics, this type is equivalent
to the InetVersion textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 791: Internet Protocol RFC 2460: Internet Protocol, Version 6 (IPv6) Specification RFC 4001: Textual Conventions for Internet Network Addresses
Source ietf-inet-types line 49

ip-version

Summary

Name ip-version
Type enumeration
  
 
This value represents the version of the IP protocol.

In the value set and its semantics, this type is equivalent
to the InetVersion textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 791: Internet Protocol RFC 2460: Internet Protocol, Version 6 (IPv6) Specification RFC 4001: Textual Conventions for Internet Network Addresses
Source ietf-inet-types line 58

IpAddressOriginTC

Summary

Name IpAddressOriginTC
Type enumeration
  
 
The origin of the address.

manual(2) indicates that the address was manually configured
to a specified address, e.g., by user configuration.

dhcp(4) indicates an address that was assigned to this
system by a DHCP server.

linklayer(5) indicates an address created by IPv6 stateless

auto-configuration.

random(6) indicates an address chosen by the system at
random, e.g., an IPv4 address within 169.254/16, or an RFC
3041 privacy address.

Details

Module IP-MIB
Version 2006-02-02
Source IP-MIB line 68

IpAddressPrefixOriginTC

Summary

Name IpAddressPrefixOriginTC
Type enumeration
  
 
The origin of this prefix.

manual(2) indicates a prefix that was manually configured.

wellknown(3) indicates a well-known prefix, e.g., 169.254/16
for IPv4 auto-configuration or fe80::/10 for IPv6 link-local
addresses.  Well known prefixes may be assigned by IANA,
the address registries, or by specification in a standards
track RFC.

dhcp(4) indicates a prefix that was assigned by a DHCP
server.

routeradv(5) indicates a prefix learned from a router
advertisement.

Note: while IpAddressOriginTC and IpAddressPrefixOriginTC
are similar, they are not identical.  The first defines how
an address was created, while the second defines how a
prefix was found.

Details

Module IP-MIB
Version 2006-02-02
Source IP-MIB line 151

IpAddressStatusTC

Summary

Name IpAddressStatusTC
Type enumeration
  
 
The status of an address.  Most of the states correspond to
states from the IPv6 Stateless Address Autoconfiguration
protocol.

The preferred(1) state indicates that this is a valid
address that can appear as the destination or source address
of a packet.

The deprecated(2) state indicates that this is a valid but
deprecated address that should no longer be used as a source
address in new communications, but packets addressed to such
an address are processed as expected.

The invalid(3) state indicates that this isn't a valid
address and it shouldn't appear as the destination or source
address of a packet.

The inaccessible(4) state indicates that the address is not
accessible because the interface to which this address is
assigned is not operational.

The unknown(5) state indicates that the status cannot be
determined for some reason.

The tentative(6) state indicates that the uniqueness of the
address on the link is being verified.  Addresses in this
state should not be used for general communication and
should only be used to determine the uniqueness of the
address.

The duplicate(7) state indicates the address has been
determined to be non-unique on the link and so must not be

used.

The optimistic(8) state indicates the address is available
for use, subject to restrictions, while its uniqueness on
a link is being verified.

In the absence of other information, an IPv4 address is
always preferred(1).

Details

Module IP-MIB
Version 2006-02-02
Reference RFC 2462
Source IP-MIB line 94

ipsec-mode

Summary

Name ipsec-mode
Type enumeration
  
 
type define of ipsec mode

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 137

ipsec-next-layer-proto

Summary

Name ipsec-next-layer-proto
Type enumeration
  
 
Next layer proto on top of IP

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 205

ipsec-protocol

Summary

Name ipsec-protocol
Type enumeration
  
 
type define of ipsec security protocol

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 159

ipsec-spd-name

Summary

Name ipsec-spd-name
Type enumeration
  
 
IPsec SPD name type

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 220

ipsec-spd-operation

Summary

Name ipsec-spd-operation
Type enumeration
  
 
The operation when traffic matches IPsec security policy

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 195

ipsec-spi

Summary

Name ipsec-spi
Type uint32
  
 
The first 32-bit IPsec Security Parameter Index (SPI)
value on data. This field is defined in [RFC4303].

Details

Module ietf-trafficselector-types
Version 2017-10-29
Reference RFC 4303: IP Encapsulating Security Payload (ESP)
Source ietf-trafficselector-types line 74

ipsec-spi

Summary

Name ipsec-spi
Type uint32
  
 
This type defines the first 32-bit IPsec
Security Parameter Index (SPI) value on data
packets sent from a corresponding node to the
mobile node as seen by the home agent. This field
is defined in [RFC4303].

Details

Module ietf-traffic-selector-types
Version 2016-01-14
Reference RFC 4303: IP Encapsulating Security Payload (ESP)
Source ietf-traffic-selector-types line 80

ipsec-spi

Summary

Name ipsec-spi
Type uint32
  
 
SPI

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 171

ipsec-traffic-direction

Summary

Name ipsec-traffic-direction
Type enumeration
  
 
IPsec traffic direction

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 185

ipv-type

Summary

Name ipv-type
Type enumeration
  
 
An IPV can be either of the following:
  1) The null value. For a frame that passes through the gate,
     the priority value associated with theframe is used to
     determine the frame’s traffic class, using the Traffic
     Class Table as specified in 8.6.6.
  2) An internal priority value. For a frame that passes
     through the gate, the IPV is used, in place of the
     priority value associated with the frame, to determine the
     frame’s traffic class, using the Traffic Class Table as
     specified in 8.6.6.

Details

Module ieee802-dot1q-stream-filters-gates
Version 2017-12-20
Reference IEEE 802.1Qci: Clause 8.6.5.1.2
Source ieee802-dot1q-stream-filters-gates line 44

ipv4-address

Summary

Name ipv4-address
Type string
  
 
The ipv4-address type represents an IPv4 address in
dotted-quad notation.  The IPv4 address may include a zone
index, separated by a % sign.

The zone index is used to disambiguate identical address
values.  For link-local addresses, the zone index will
typically be the interface index number or the name of an
interface.  If the zone index is not present, the default
zone of the device will be used.

The canonical format for the zone index is the numerical
format

Details

Module ietf-inet-types
Version 2010-09-24
Source ietf-inet-types line 181

ipv4-address

Summary

Name ipv4-address
Type string
  
 
The ipv4-address type represents an IPv4 address in
dotted-quad notation.  The IPv4 address may include a zone
index, separated by a % sign.

The zone index is used to disambiguate identical address
values.  For link-local addresses, the zone index will
typically be the interface index number or the name of an
interface.  If the zone index is not present, the default
zone of the device will be used.

The canonical format for the zone index is the numerical
format

Details

Module ietf-inet-types
Version 2013-07-15
Source ietf-inet-types line 193

ipv4-address

Summary

Name ipv4-address
Type string
  
 
An IPv4 address in dotted quad notation.

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 30

ipv4-address

Summary

Name ipv4-address
Type string
  
 
An IPv4 address in dotted quad notation using the default
zone.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 68

ipv4-address-zoned

Summary

Name ipv4-address-zoned
Type string
  
 
An IPv4 address in dotted quad notation.  This type allows
specification of a zone index to disambiguate identical
address values.  For link-local addresses, the index is
typically the interface index or interface name.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 79

ipv4-multicast-source-address

Summary

Name ipv4-multicast-source-address
Type union
  
 
Multicast source IPv4 address type.

Details

Module ietf-routing-types
Version 2017-02-19
Source ietf-routing-types line 362

ipv4-multicast-source-address

Summary

Name ipv4-multicast-source-address
Type union
  
 
Multicast source IPv4 address type.

Details

Module ietf-routing-types
Version 2017-10-13
Source ietf-routing-types line 454

ipv4-multicast-source-address

Summary

Name ipv4-multicast-source-address
Type union
  
 
Multicast source IPv4 address type.

Details

Module ietf-routing-types
Version 2017-02-27
Source ietf-routing-types line 339

ipv4-prefix

Summary

Name ipv4-prefix
Type string
  
 
An IPv4 prefix represented in dotted quad notation followed by
a slash and a CIDR mask (0 <= mask <= 32).

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 137

ipv4-prefix

Summary

Name ipv4-prefix
Type string
  
 
The ipv4-prefix type represents an IPv4 address prefix.
The prefix length is given by the number following the
slash character and must be less than or equal to 32.



A prefix length value of n corresponds to an IP address
mask that has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0.

The canonical format of an IPv4 prefix has all bits of
the IPv4 address set to zero that are not part of the
IPv4 prefix.

Details

Module ietf-inet-types
Version 2010-09-24
Source ietf-inet-types line 257

ipv4-prefix

Summary

Name ipv4-prefix
Type string
  
 
The ipv4-prefix type represents an IPv4 address prefix.
The prefix length is given by the number following the
slash character and must be less than or equal to 32.

A prefix length value of n corresponds to an IP address
mask that has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0.

The canonical format of an IPv4 prefix has all bits of
the IPv4 address set to zero that are not part of the
IPv4 prefix.

Details

Module ietf-inet-types
Version 2013-07-15
Source ietf-inet-types line 301

ipv4-prefix

Summary

Name ipv4-prefix
Type string
  
 
An IPv4 prefix represented in dotted quad notation followed by
a slash and a CIDR mask (0 <= mask <= 32).

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 61

ipv6-address

Summary

Name ipv6-address
Type string
  
 
The ipv6-address type represents an IPv6 address in full,
mixed, shortened, and shortened-mixed notation.  The IPv6
address may include a zone index, separated by a % sign.





The zone index is used to disambiguate identical address
values.  For link-local addresses, the zone index will
typically be the interface index number or the name of an
interface.  If the zone index is not present, the default
zone of the device will be used.

The canonical format of IPv6 addresses uses the compressed
format described in RFC 4291, Section 2.2, item 2 with the
following additional rules: the :: substitution must be
applied to the longest sequence of all-zero 16-bit chunks
in an IPv6 address.  If there is a tie, the first sequence
of all-zero 16-bit chunks is replaced by ::.  Single
all-zero 16-bit chunks are not compressed.  The canonical
format uses lowercase characters and leading zeros are
not allowed.  The canonical format for the zone index is
the numerical format as described in RFC 4007, Section
11.2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 4291: IP Version 6 Addressing Architecture RFC 4007: IPv6 Scoped Address Architecture RFC 5952: A Recommendation for IPv6 Address Text Representation
Source ietf-inet-types line 203

ipv6-address

Summary

Name ipv6-address
Type string
  
 
The ipv6-address type represents an IPv6 address in full,
mixed, shortened, and shortened-mixed notation.  The IPv6
address may include a zone index, separated by a % sign.

The zone index is used to disambiguate identical address
values.  For link-local addresses, the zone index will
typically be the interface index number or the name of an
interface.  If the zone index is not present, the default
zone of the device will be used.



The canonical format of IPv6 addresses uses the textual
representation defined in Section 4 of RFC 5952.  The
canonical format for the zone index is the numerical
format as described in Section 11.2 of RFC 4007.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 4291: IP Version 6 Addressing Architecture RFC 4007: IPv6 Scoped Address Architecture RFC 5952: A Recommendation for IPv6 Address Text Representation
Source ietf-inet-types line 215

ipv6-address

Summary

Name ipv6-address
Type string
  
 
An IPv6 address represented as either a full address; shortened
or mixed-shortened formats.

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 40

ipv6-address

Summary

Name ipv6-address
Type string
  
 
An IPv6 address represented as either a full address; shortened
or mixed-shortened formats, using the default zone.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 92

ipv6-address-zoned

Summary

Name ipv6-address-zoned
Type string
  
 
An IPv6 address represented as either a full address; shortened
or mixed-shortened formats.  This type allows specification of
a zone index to disambiguate identical address values.  For
link-local addresses, the index is typically the interface
index or interface name.

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 113

ipv6-flow-label

Summary

Name ipv6-flow-label
Type uint32
  
 
The IPv6 flow-label is a 20-bit value within the IPv6 header
which is optionally used by the source of the IPv6 packet to
label sets of packets for which special handling may be
required.

Details

Module openconfig-inet-types
Version 2017-08-24
Reference RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
Source openconfig-inet-types line 291

ipv6-flow-label

Summary

Name ipv6-flow-label
Type uint32
  
 
The flow-label type represents flow identifier or Flow Label
in an IPv6 packet header that may be used to discriminate
traffic flows.

In the value set and its semantics, this type is equivalent
to the IPv6FlowLabel textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 3595: Textual Conventions for IPv6 Flow Label RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Source ietf-inet-types line 97

ipv6-flow-label

Summary

Name ipv6-flow-label
Type uint32
  
 
The ipv6-flow-label type represents the flow identifier or Flow
Label in an IPv6 packet header that may be used to
discriminate traffic flows.

In the value set and its semantics, this type is equivalent
to the IPv6FlowLabel textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 3595: Textual Conventions for IPv6 Flow Label RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Source ietf-inet-types line 106

ipv6-flow-label

Summary

Name ipv6-flow-label
Type uint32
  
 
The IPv6 flow-label is a 20-bit value within the IPv6 header
which is optionally used by the source of the IPv6 packet to
label sets of packets for which special handling may be
required.

Details

Module openconfig-inet-types
Version 2017-01-26
Reference RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
Source openconfig-inet-types line 138

ipv6-multicast-source-address

Summary

Name ipv6-multicast-source-address
Type union
  
 
Multicast source IPv6 address type.

Details

Module ietf-routing-types
Version 2017-02-19
Source ietf-routing-types line 376

ipv6-multicast-source-address

Summary

Name ipv6-multicast-source-address
Type union
  
 
Multicast source IPv6 address type.

Details

Module ietf-routing-types
Version 2017-10-13
Source ietf-routing-types line 468

ipv6-multicast-source-address

Summary

Name ipv6-multicast-source-address
Type union
  
 
Multicast source IPv6 address type.

Details

Module ietf-routing-types
Version 2017-02-27
Source ietf-routing-types line 352

ipv6-prefix

Summary

Name ipv6-prefix
Type string
  
 
An IPv6 prefix represented in full, shortened, or mixed
shortened format followed by a slash and CIDR mask
(0 <= mask <= 128).

Details

Module openconfig-inet-types
Version 2017-08-24
Source openconfig-inet-types line 148

ipv6-prefix

Summary

Name ipv6-prefix
Type string
  
 
The ipv6-prefix type represents an IPv6 address prefix.
The prefix length is given by the number following the
slash character and must be less than or equal 128.

A prefix length value of n corresponds to an IP address
mask that has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0.

The IPv6 address should have all bits that do not belong
to the prefix set to zero.

The canonical format of an IPv6 prefix has all bits of
the IPv6 address set to zero that are not part of the
IPv6 prefix.  Furthermore, IPv6 address is represented
in the compressed format described in RFC 4291, Section
2.2, item 2 with the following additional rules: the ::
substitution must be applied to the longest sequence of
all-zero 16-bit chunks in an IPv6 address.  If there is
a tie, the first sequence of all-zero 16-bit chunks is
replaced by ::.  Single all-zero 16-bit chunks are not
compressed.  The canonical format uses lowercase
characters and leading zeros are not allowed.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 4291: IP Version 6 Addressing Architecture
Source ietf-inet-types line 280

ipv6-prefix

Summary

Name ipv6-prefix
Type string
  
 
The ipv6-prefix type represents an IPv6 address prefix.
The prefix length is given by the number following the
slash character and must be less than or equal to 128.

A prefix length value of n corresponds to an IP address
mask that has n contiguous 1-bits from the most
significant bit (MSB) and all other bits set to 0.

The IPv6 address should have all bits that do not belong
to the prefix set to zero.

The canonical format of an IPv6 prefix has all bits of
the IPv6 address set to zero that are not part of the
IPv6 prefix.  Furthermore, the IPv6 address is represented
as defined in Section 4 of RFC 5952.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 5952: A Recommendation for IPv6 Address Text Representation
Source ietf-inet-types line 322

ipv6-prefix

Summary

Name ipv6-prefix
Type string
  
 
An IPv6 prefix represented in full, shortened, or mixed
shortened format followed by a slash and CIDR mask (0 <= mask <=
128).

Details

Module openconfig-inet-types
Version 2017-01-26
Source openconfig-inet-types line 72

ipv6-route-origin

Summary

Name ipv6-route-origin
Type string
  
 
An IPv6 route origin is a 20-octet BGP IPv6 address
specific extended community serving the same function
as a standard 8-octet route only allowing for
an IPv6 address as the global administrator. The format
is <ipv6-address:2-octet-number>.

Some valid examples are: 2001:DB8::1:6544 and
2001:DB8::5eb1:791:6b37:17958

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC5701: IPv6 Address Specific BGP Extended Community Attribute
Source ietf-routing-types line 386

ipv6-route-target

Summary

Name ipv6-route-target
Type string
  
 
An IPv6 route target is a 20-octet BGP IPv6 address
specific extended community serving the same function
as a standard 8-octet route target only allowing for
an IPv6 address as the global administrator. The format
is <ipv6-address:2-octet-number>.

Some valid examples are: 2001:DB8::1:6544 and
2001:DB8::5eb1:791:6b37:17958

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC5701: IPv6 Address Specific BGP Extended Community Attribute
Source ietf-routing-types line 205

Ipv6AddressIfIdentifierTC

Summary

Name Ipv6AddressIfIdentifierTC
Type string
  
 
This data type is used to model IPv6 address
interface identifiers.  This is a binary string
of up to 8 octets in network byte-order.

Details

Module IP-MIB
Version 2006-02-02
Source IP-MIB line 182

isis-interface-adj-state

Summary

Name isis-interface-adj-state
Type enumeration
  
 
This type defines the state of the interface.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 264

isis-metric-flags

Summary

Name isis-metric-flags
Type enumeration
  
 
Type definition for flags used in IS-IS metrics

Details

Module openconfig-isis
Submodule openconfig-isis-lsp
Version 2017-08-24
Source openconfig-isis-lsp line 75

isolation-mode-type

Summary

Name isolation-mode-type
Type enumeration
  
 
Isolation mode

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 58

key-chain-ref

Summary

Name key-chain-ref
Type leafref
  
 
This type is used by data models that need to reference
configured key chains.

Details

Module ietf-key-chain
Version 2017-06-15
Source ietf-key-chain line 172

l2vpn-discovery-type

Summary

Name l2vpn-discovery-type
Type identityref
  
 
L2VPN discovery type

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 319

l2vpn-instance-ac-ref

Summary

Name l2vpn-instance-ac-ref
Type leafref
  
 
l2vpn-instance-ac-ref

Details

Module ietf-igmp-mld-snooping
Version 2017-10-25
Source ietf-igmp-mld-snooping line 181

l2vpn-instance-name-ref

Summary

Name l2vpn-instance-name-ref
Type leafref
  
 
l2vpn-instance-name-ref

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 361

l2vpn-instance-pw-ref

Summary

Name l2vpn-instance-pw-ref
Type leafref
  
 
l2vpn-instance-pw-ref

Details

Module ietf-igmp-mld-snooping
Version 2017-10-25
Source ietf-igmp-mld-snooping line 189

l2vpn-instance-type-ref

Summary

Name l2vpn-instance-type-ref
Type leafref
  
 
l2vpn-instance-type-ref

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 369

l2vpn-service-type

Summary

Name l2vpn-service-type
Type identityref
  
 
L2VPN service type

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 312

l2vpn-signaling-type

Summary

Name l2vpn-signaling-type
Type identityref
  
 
L2VPN signaling type

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 326

l3-event-type

Summary

Name l3-event-type
Type enumeration
  
 
Layer 3 Event type for notifications

Details

Module ietf-l3-unicast-topology
Version 2017-12-16
Source ietf-l3-unicast-topology line 66

l3-flag-type

Summary

Name l3-flag-type
Type identityref
  
 
L3 flag attributes

Details

Module ietf-l3-unicast-topology
Version 2017-12-16
Source ietf-l3-unicast-topology line 108

label-adv-mode

Summary

Name label-adv-mode
Type enumeration
  
 
Label Advertisement Mode.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 125

lacp-activity-type

Summary

Name lacp-activity-type
Type enumeration
  
 
Describes the LACP membership type, active or passive, of the
interface in the aggregate

Details

Module openconfig-lacp
Version 2017-05-05
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 47

lacp-period-type

Summary

Name lacp-period-type
Type enumeration
  
 
Defines the period options for the time between sending
LACP messages

Details

Module openconfig-lacp
Version 2017-05-05
Reference IEEE 802.3ad
Source openconfig-lacp line 104

lacp-synchronization-type

Summary

Name lacp-synchronization-type
Type enumeration
  
 
Indicates LACP synchronization state of participant

Details

Module openconfig-lacp
Version 2017-05-05
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 86

lacp-timeout-type

Summary

Name lacp-timeout-type
Type enumeration
  
 
Type of timeout used, short or long, by LACP participants

Details

Module openconfig-lacp
Version 2017-05-05
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 66

LangString

Summary

Name LangString
Type string
  
 
XML string with a language attribute.

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 242

LangString2

Summary

Name LangString2
Type string
  
 
XML string with a language attribute.

Details

Module yuma-system
Version 2013-07-15
Source yuma-system line 90

Language

Summary

Name Language
Type string
  
 
XML language type for LangString

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 217

language

Summary

Name language
Type string
  
 
XSD language identifier string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#language
Source yuma-xsd line 354

Language2

Summary

Name Language2
Type string
  
 
XML language type for LangString

Details

Module yuma-system
Version 2013-07-15
Source yuma-system line 83

lcaf-ref

Summary

Name lcaf-ref
Type identityref
  
 
LCAF types reference.

Details

Module ietf-lisp-address-types
Version 2015-11-05
Source ietf-lisp-address-types line 222

ldp-address-family

Summary

Name ldp-address-family
Type identityref
  
 
LDP address family type.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 77

level

Summary

Name level
Type enumeration
  
 
This type defines ISIS level of an object.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 265

level-number

Summary

Name level-number
Type uint8
  
 
This type defines ISIS level.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 165

level-number

Summary

Name level-number
Type uint8
  
 
This type defines a current ISIS level.

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 328

level-type

Summary

Name level-type
Type enumeration
  
 
This type defines ISIS level types

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 149

lifecycle-status-type

Summary

Name lifecycle-status-type
Type enumeration
  
 
Lifecycle status

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 72

lifetime-action

Summary

Name lifetime-action
Type enumeration
  
 
Action when lifetime expiration

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 177

link-access-type

Summary

Name link-access-type
Type enumeration
  
 
Link access type.

Details

Module ietf-routing-types
Version 2017-02-19
Source ietf-routing-types line 419

link-access-type

Summary

Name link-access-type
Type enumeration
  
 
Link access type.

Details

Module ietf-routing-types
Version 2017-10-13
Source ietf-routing-types line 512

link-access-type

Summary

Name link-access-type
Type enumeration
  
 
Link access type.

Details

Module ietf-routing-types
Version 2017-02-27
Source ietf-routing-types line 393

link-discovery-protocol-type

Summary

Name link-discovery-protocol-type
Type identityref
  
 
This type is used to identify link discovery protocol

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 333

link-flag-type

Summary

Name link-flag-type
Type identityref
  
 
Link flag attributes

Details

Module ietf-l3-unicast-topology
Version 2017-12-16
Source ietf-l3-unicast-topology line 101

link-ref

Summary

Name link-ref
Type leafref
  
 
A type for an absolute reference a link instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)

Details

Module network-topology
Version 2013-10-21
Source network-topology line 103

link-ref

Summary

Name link-ref
Type leafref
  
 
A type for an absolute reference a link instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)

Details

Module network-topology
Version 2013-07-12
Source network-topology line 101

link-ref

Summary

Name link-ref
Type instance-identifier
  
 
A reference to a link

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 151

link-ref

Summary

Name link-ref
Type instance-identifier
  
 
A reference to a link in topology

Details

Module ietf-fabric-types
Version 2017-11-29
Source ietf-fabric-types line 159

lisp-address-family-ref

Summary

Name lisp-address-family-ref
Type identityref
  
 
LISP address family reference.

Details

Module ietf-lisp-address-types
Version 2015-11-05
Source ietf-lisp-address-types line 215

lisp-role-ref

Summary

Name lisp-role-ref
Type identityref
  
 
LISP role reference

Details

Module ietf-lisp
Version 2017-07-01
Source ietf-lisp line 83

lkr-interval

Summary

Name lkr-interval
Type enumeration
  
 
lkr-interval

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 91

LldpChassisId

Summary

Name LldpChassisId
Type int32
  
 
This describes the format of a chassis identifier string.
Objects of this type are always used with an associated
LldpChassisIdSubtype object, which identifies the format of
the particular LldpChassisId object instance.

If the associated LldpChassisIdSubtype object has a value of
'chassisComponent(1)', then the octet string identifies
a particular instance of the entPhysicalAlias object
(defined in IETF RFC 2737) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').

If the associated LldpChassisIdSubtype object has a value
of 'interfaceAlias(2)', then the octet string identifies
a particular instance of the ifAlias object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifAlias object does not contain any values,
another chassis identifier type should be used.

If the associated LldpChassisIdSubtype object has a value
of 'portComponent(3)', then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 2737) for a port or backplane component within
the containing chassis.

If the associated LldpChassisIdSubtype object has a value of
'macAddress(4)', then this string identifies a particular
unicast source address (encoded in network byte order and
IEEE 802.3 canonical bit order), of a port on the containing
chassis as defined in IEEE Std 802-2001.

If the associated LldpChassisIdSubtype object has a value of
'networkAddress(5)', then this string identifies a particular
network address, encoded in network byte order, associated
with one or more ports on the containing chassis.  The first
octet contains the IANA Address Family Numbers enumeration
value for the specific address type, and octets 2 through
N contain the network address value in network byte order.

If the associated LldpChassisIdSubtype object has a value
of 'interfaceName(6)', then the octet string identifies
a particular instance of the ifName object (defined in
IETF RFC 2863) for an interface on the containing chassis.
If the particular ifName object does not contain any values,
another chassis identifier type should be used.

If the associated LldpChassisIdSubtype object has a value of
'local(7)', then this string identifies a locally assigned
Chassis ID.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 191

LldpChassisIdSubtype

Summary

Name LldpChassisIdSubtype
Type enumeration
  
 
This describes the format of a chassis identifier string.
Objects of this type are always used with an associated
LldpChassisIdSubtype object, which identifies the format of
the particular LldpChassisId object instance.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 109

LldpPortId

Summary

Name LldpPortId
Type int32
  
 
This describes the format of a port identifier string.
Objects of this type are always used with an associated
LldpPortIdSubtype object, which identifies the format of the
particular LldpPortId object instance.

If the associated LldpPortIdSubtype object has a value of
'interfaceAlias(1)', then the octet string identifies a
particular instance of the ifAlias object (defined in IETF
RFC 2863).  If the particular ifAlias object does not contain
any values, another port identifier type should be used.

If the associated LldpPortIdSubtype object has a value of
'portComponent(2)', then the octet string identifies a
particular instance of the entPhysicalAlias object (defined
in IETF RFC 2737) for a port or backplane component.

If the associated LldpPortIdSubtype object has a value of
'macAddress(3)', then this string identifies a particular
unicast source address (encoded in network byte order
and IEEE 802.3 canonical bit order) associated with the port
(IEEE Std 802-2001).

If the associated LldpPortIdSubtype object has a value of
'networkAddress(4)', then this string identifies a network
address associated with the port.  The first octet contains
the IANA AddressFamilyNumbers enumeration value for the
specific address type, and octets 2 through N contain the
networkAddress address value in network byte order.

If the associated LldpPortIdSubtype object has a value of
'interfaceName(5)', then the octet string identifies a
particular instance of the ifName object (defined in IETF
RFC 2863).  If the particular ifName object does not contain
any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of
'agentCircuitId(6)', then this string identifies a agent-local
identifier of the circuit (defined in RFC 3046).

If the associated LldpPortIdSubtype object has a value of
'local(7)', then this string identifies a locally
assigned port ID.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 300

LldpPortIdSubtype

Summary

Name LldpPortIdSubtype
Type enumeration
  
 
This describes the source of a particular type of port
identifier used in the LLDP MIB.

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 245

lm-interval

Summary

Name lm-interval
Type uint32
  
 
The value rang for lm packet transmit interval

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 174

local-defined-next-hop

Summary

Name local-defined-next-hop
Type identityref
  
 
Pre-defined next-hop designation for locally generated
routes

Details

Module openconfig-local-routing
Version 2017-05-15
Source openconfig-local-routing line 86

lock-id-type

Summary

Name lock-id-type
Type uint32
  
 
A number identifying a specific partial-lock granted to a session.
It is allocated by the system, and SHOULD be used in the
partial-unlock operation.

Details

Module ietf-netconf-partial-lock
Version 2009-10-19
Source ietf-netconf-partial-lock line 29

LogCount

Summary

Name LogCount
Type int32
  
 
Number of log entries. -1 means all entries

Details

Module yangcli-pro
Version 2017-12-12
Source yangcli-pro line 334

login-mode

Summary

Name login-mode
Type enumeration
  
 
This is used for login mode

Details

Module ietf-i2nsf-monitoring-information
Version 2017-07-19
Source ietf-i2nsf-monitoring-information line 126

login-mode

Summary

Name login-mode
Type enumeration
  
 
This is used for login mode

Details

Module ietf-i2nsf-nsf-monitoring-dm
Version 2017-10-29
Source ietf-i2nsf-nsf-monitoring-dm line 125

LogIndex

Summary

Name LogIndex
Type uint32
  
 
Index into a log buffer.

Details

Module yangcli-pro
Version 2017-12-12
Source yangcli-pro line 342

long

Summary

Name long
Type int64
  
 
XSD 64 bit signed integer.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#long
Source yuma-xsd line 144

long

Summary

Name long
Type int64
  
 
Changed long base type to int64 for YANG

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 71

loopback-mode-type

Summary

Name loopback-mode-type
Type enumeration
  
 
Loopback modes for transponder logical channels

Details

Module openconfig-transport-types
Version 2017-08-16
Source openconfig-transport-types line 66

loopback-status

Summary

Name loopback-status
Type enumeration
  
 
The loopback mode of an OAM interface

Details

Module ieee802-ethernet-link-oam
Version 2017-10-18
Reference IEEE Std 802.3, 57.2.11
Source ieee802-ethernet-link-oam line 188

lsp-error

Summary

Name lsp-error
Type enumeration
  
 
The LSP Error Codes.

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 332

lsp-id

Summary

Name lsp-id
Type string
  
 
This type defines ISIS LSP ID. ISIS LSP ID type should be in
the form of xxxx.xxxx.xxxx.xx-xx

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 319

lsp-id

Summary

Name lsp-id
Type string
  
 
This type defines ISIS LSP ID using pattern,
system id looks like : 0143.0438.AeF0.02-01

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 336

ma-name-string

Summary

Name ma-name-string
Type string
  
 
Generic administrative name for an
Maintenance Association (MA).

Details

Module ietf-connection-oriented-oam
Version 2017-06-01
Source ietf-connection-oriented-oam line 221

mac-address

Summary

Name mac-address
Type string
  
 
An IEEE 802 MAC address

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 149

mac-address

Summary

Name mac-address
Type string
  
 
The mac-address type represents an IEEE 802 MAC address.
The canonical representation uses lowercase characters.

In the value set and its semantics, this type is equivalent
to the MacAddress textual convention of the SMIv2.

Details

Module ietf-yang-types
Version 2010-09-24
Reference IEEE 802: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture RFC 2579: Textual Conventions for SMIv2
Source ietf-yang-types line 373

mac-address

Summary

Name mac-address
Type string
  
 
The mac-address type represents an IEEE 802 MAC address.
The canonical representation uses lowercase characters.

In the value set and its semantics, this type is equivalent
to the MacAddress textual convention of the SMIv2.

Details

Module ietf-yang-types
Version 2013-07-15
Reference IEEE 802: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture RFC 2579: Textual Conventions for SMIv2
Source ietf-yang-types line 409

mac-address

Summary

Name mac-address
Type string
  
 
The mac-address type represents a MAC address in the canonical
format and hexadecimal format specified by IEEE Std 802.
     The hexidecimal representation uses uppercase characters.

Details

Module ieee802-types
Version 2017-07-20
Reference IEEE 802-2014, Clauses 3.1, 8.1
Source ieee802-types line 41

MacAddress

Summary

Name MacAddress
Type string
  
 
Represents an 802 MAC address represented in the
`canonical' order defined by IEEE 802.1a, i.e., as if it
were transmitted least significant bit first, even though
802.5 (in contrast to other 802.x protocols) requires MAC
addresses to be transmitted most significant bit first.

Details

Module SNMPv2-TC
Version none
Source SNMPv2-TC line 66

mak-an

Summary

Name mak-an
Type uint32
  
 
A number that is concatenated with a MACsec Secure Channel
Identifier to identify a Secure Association. Indicates an
Association Number (AN) assigned by the Key Server for use with
the key number for transmission.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 9.8, Clause 9.16
Source ieee802-dot1x line 255

mak-kn

Summary

Name mak-kn
Type uint32
  
 
Indicates a Key Number (KN) used in MKA. It is assigned by
the Key Server (sequentially beginning with 1).

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 9.8, Clause 9.16
Source ieee802-dot1x line 246

map-reply-action

Summary

Name map-reply-action
Type enumeration
  
 
Defines the lisp map-cache ACT type

Details

Module ietf-lisp
Version 2017-07-01
Reference https://tools.ietf.org/html/rfc6830#section-6.1.4
Source ietf-lisp line 90

map-type

Summary

Name map-type
Type enumeration
  
 
The map-type

Details

Module ietf-te-service-mapping
Version 2017-10-27
Source ietf-te-service-mapping line 73

mapping-system-ref

Summary

Name mapping-system-ref
Type identityref
  
 
Mapping System reference

Details

Module ietf-lisp
Version 2017-07-01
Source ietf-lisp line 75

match-set-options-restricted-type

Summary

Name match-set-options-restricted-type
Type enumeration
  
 
Options that govern the behavior of a match statement.  The
default behavior is ANY, i.e., the given value matches any
of the members of the defined set.  Note this type is a
restricted version of the match-set-options-type.

Details

Module openconfig-policy-types
Version 2017-07-14
Source openconfig-policy-types line 89

match-set-options-type

Summary

Name match-set-options-type
Type enumeration
  
 
Options that govern the behavior of a match statement.  The
default behavior is ANY, i.e., the given value matches any
of the members of the defined set

Details

Module openconfig-policy-types
Version 2017-07-14
Source openconfig-policy-types line 67

matchall-string-type

Summary

Name matchall-string-type
Type string
  
 
The string containing a single asterisk '*' is used
to conceptually represent all possible values
for the particular leaf using this data type.

Details

Module ietf-netconf-acm
Version 2012-02-22
Source ietf-netconf-acm line 102

matchall-string-type

Summary

Name matchall-string-type
Type string
  
 
The string containing a single asterisk '*' is used
to conceptually represent all possible values
for the particular leaf using this data type.

Details

Module ietf-netconf-acm
Version 2017-12-11
Source ietf-netconf-acm line 109

md-level

Summary

Name md-level
Type uint32
  
 
Maintenance Domain level.  The level may be restricted in
certain protocols (e.g., protocol in layer 0 to layer 7).

Details

Module ietf-connection-oriented-oam
Version 2017-06-01
Source ietf-connection-oriented-oam line 234

md-name-string

Summary

Name md-name-string
Type string
  
 
Generic administrative name for Maintenance Domain (MD).

Details

Module ietf-connection-oriented-oam
Version 2017-06-01
Source ietf-connection-oriented-oam line 215

me-direction

Summary

Name me-direction
Type enumeration
  
 
me-direction

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 117

me-state

Summary

Name me-state
Type enumeration
  
 
me-state

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 138

me-type

Summary

Name me-type
Type enumeration
  
 
ME type

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 20

measure-mode

Summary

Name measure-mode
Type enumeration
  
 
measure mode

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 180

mep-name

Summary

Name mep-name
Type string
  
 
Generic administrative name for a Maintenance End Point
(MEP).

Details

Module ietf-connection-oriented-oam
Version 2017-06-01
Source ietf-connection-oriented-oam line 198

mesh-group-state

Summary

Name mesh-group-state
Type enumeration
  
 
This type describes meshgroup state of an interface

Details

Module ietf-isis
Version 2017-11-20
Source ietf-isis line 392

MessageId

Summary

Name MessageId
Type string
  
 
NETCONF message-id attribute

Details

Module yuma-netconf
Version 2015-04-30
Source yuma-netconf line 248

metric-style

Summary

Name metric-style
Type enumeration
  
 
This type defines ISIS metric styles

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 247

metric-type

Summary

Name metric-type
Type enumeration
  
 
This type defines ISIS metric type

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 218

minute

Summary

Name minute
Type uint8
  
 
A minute of an hour.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 265

minute

Summary

Name minute
Type uint8
  
 
A minute of an hour.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 268

minute-or-all

Summary

Name minute-or-all
Type union
  
 
A minute of an hour or a wildcard indicating all
minutes of an hour.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 271

minute-or-all

Summary

Name minute-or-all
Type union
  
 
A minute of an hour or a wildcard indicating all
minutes of an hour.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 274

mld-snooping-instance-ref

Summary

Name mld-snooping-instance-ref
Type leafref
  
 
This type is used by data models that need to reference mld
snooping instance.

Details

Module ietf-igmp-mld-snooping
Version 2017-10-25
Source ietf-igmp-mld-snooping line 172

mode

Summary

Name mode
Type bits
  
 
Authentication mode bit mask

Details

Module ietf-twamp
Version 2015-06-30
Source ietf-twamp line 43

mode

Summary

Name mode
Type enumeration
  
 
Enumeration of the valid modes in which Link OAM may run

Details

Module ieee802-ethernet-link-oam
Version 2017-10-18
Reference IEEE Std 802.3, 57.2.9 and 30.3.6.1.3.
Source ieee802-ethernet-link-oam line 156

module-version-type

Summary

Name module-version-type
Type string
  
 
This type defines acceptable formats for the version of a
module.  The version may be a semantic version, or a YANG
revision statement date, and may include wildcards when
included in a bundle compatibility list, e.g.:

semver format: <major>.<minor>.<patch>
examples: 0.1.0, 2.1.0, 1.1.*, 2.*.*

revision format:  YYYY-MM-DD
example:  2016-11-31

Details

Module openconfig-catalog-types
Version 2017-05-01
Source openconfig-catalog-types line 225

module-version-type

Summary

Name module-version-type
Type string
  
 
This type defines acceptable formats for the version of a
module.  The version may be a semantic version, or a YANG
revision statement date, and may include wildcards when
included in a bundle compatibility list, e.g.:

semver format: <major>.<minor>.<patch>
examples: 0.1.0, 2.1.0, 1.1.*, 2.*.*

revision format:  YYYY-MM-DD
example:  2016-11-31

Details

Module openconfig-catalog-types
Version 2017-03-08
Source openconfig-catalog-types line 222

month

Summary

Name month
Type enumeration
  
 
A type modeling the month in the Gregorian calendar.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 101

month

Summary

Name month
Type enumeration
  
 
A type modeling the month in the Gregorian calendar.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 102

month-or-all

Summary

Name month-or-all
Type union
  
 
A month or a wildcard indicating all twelve months.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 168

month-or-all

Summary

Name month-or-all
Type union
  
 
A month or a wildcard indicating all twelve months.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 170

mount-status

Summary

Name mount-status
Type enumeration
  
 
This type is used to represent the status of a
mountpoint.

Details

Module ietf-mount
Version 2017-03-30
Source ietf-mount line 122

mpcp-admin-state

Summary

Name mpcp-admin-state
Type enumeration
  
 
Enumeration of valid administrative states for a MultiPoint MAC
Control sublayer on the OLT or ONU

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.5.2.1
Source ieee802-ethernet-pon line 145

mpcp-llid

Summary

Name mpcp-llid
Type uint32
  
 
A unique identifier for a MAC within an EPON network.
Logical Link Identifiers (LLIDs) are dynamically assigned by
the OLT during the registration process. For a complete
description of how the LLID is used in an EPON device see
IEEE Std 802.3 subclause 65.1.3.3 for 1G-EPON or
76.2.6.1.3 for 10G-EPON.
The third and fourth octets following the SLD contain the mode
and logical_link_id values. OLTs and ONUs act upon these values
in a different manner.

If the device is an OLT, then the following comparison is made:
a) The received mode bit is ignored.
b) If the received logical_link_id value matches
0x7FFF or 0x7FFE and an enabled MAC exists with a
logical_link_id variable with the same value,
then the comparison is considered a match to that MAC.
c) If the received logical_link_id has a value other than
0x7FFF or 0x7FFE and an enabled MAC exists with a mode variable
with a value of 0 and a logical_link_id variable matching
the received logical_link_id value, then the comparison
is considered a match to that MAC.

If the device is an ONU then the following comparison is made:
d) If the received mode bit is equal to 0 and the received
logical_link_id value matches the logical_link_id variable,
then the comparison is considered a match.
e) If the received mode bit is equal to 1 and the received
logical_link_id value does not match the logical_link_id
variable, or the received logical_link_id matches 0x7FFE,
then the comparison is considered a match.
f) If the received logical_link_id value matches one of the
assigned multicast LLIDs, then the comparison
is considered a match.

If no match is found, then the packet shall be discarded
within the RS. If a match is found, then the packet
is intended to be transferred.

If the packet is transferred, then both octets of the LLID
field shall be replaced with normal preamble octets.

If the packet is transferred, the one octet preceding the LLID
is passed without modification. A number of LLIDs have been
reserved (see IEEE Std 802.3, Figure 76-4) for various purposes
including downstream broadcast, discovery messages, and upstream
registration request messages. An additional block of LLIDs has
been set aside for future use and definition. A registered ONU
shall not transmit frames with one of these reserved LLIDs.

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 76.2.6.1.3.2 (1G-EPON and 10G-EPON)
Source ieee802-ethernet-pon line 57

mpcp-llid-count

Summary

Name mpcp-llid-count
Type uint32
  
 
Indicates the number of registered LLIDs. The initialization value is
0. This is applicable for an OLT with the same value for all virtual
interfaces and for an ONU.

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 76.2.6.1.3.2 (1G-EPON and 10G-EPON)
Source ieee802-ethernet-pon line 130

mpcp-logical-link-admin-state

Summary

Name mpcp-logical-link-admin-state
Type enumeration
  
 
Enumeration of valid administrative states for a logical link
on the OLT or ONU

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Source ieee802-ethernet-pon line 217

mpcp-logical-link-state

Summary

Name mpcp-logical-link-state
Type enumeration
  
 
Enumeration of valid MPCP registration states for Ethernet
interfaces

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.5.1.6
Source ieee802-ethernet-pon line 189

mpcp-maximum-queue-count-per-report

Summary

Name mpcp-maximum-queue-count-per-report
Type uint8
  
 
Defines the maximum number of queues (0-7) in the REPORT
MPCPDU as defined in IEEE Std 802.3, Clause 64 and Clause 77.

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Source ieee802-ethernet-pon line 118

mpcp-mode

Summary

Name mpcp-mode
Type enumeration
  
 
Enumeration of valid mpcp modes for Ethernet interfaces

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.5.1.3
Source ieee802-ethernet-pon line 169

mpcp-supported

Summary

Name mpcp-supported
Type boolean
  
 
This object indicates that the given Ethernet interface
supports MPCP, i.e., it is an Ethernet PON (EPON) interface.

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Source ieee802-ethernet-pon line 49

mpls-hop-type

Summary

Name mpls-hop-type
Type enumeration
  
 
enumerated type for specifying loose or strict
paths

Details

Module openconfig-mpls
Submodule openconfig-mpls-te
Version 2017-08-24
Source openconfig-mpls-te line 111

mpls-label

Summary

Name mpls-label
Type union
  
 
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 623

mpls-label

Summary

Name mpls-label
Type union
  
 
The 20-bit label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 666

mpls-label

Summary

Name mpls-label
Type union
  
 
type for MPLS label value encoding

Details

Module openconfig-mpls-types
Version 2017-08-24
Reference RFC 3032 - MPLS Label Stack Encoding
Source openconfig-mpls-types line 281

mpls-label

Summary

Name mpls-label
Type union
  
 
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 580

mpls-label-action-def

Summary

Name mpls-label-action-def
Type identityref
  
 
MPLS label action def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 159

mpls-label-general-use

Summary

Name mpls-label-general-use
Type uint32
  
 
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).
The label range specified by this type is for general use,
with special-purpose MPLS label values excluded.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 609

mpls-label-general-use

Summary

Name mpls-label-general-use
Type uint32
  
 
The 20-bit label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).
The label range specified by this type is for general use,
with special-purpose MPLS label values excluded.

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 653

mpls-label-general-use

Summary

Name mpls-label-general-use
Type uint32
  
 
The 20 bits label values in an MPLS label stack entry,
specified in RFC3032. This label value does not include
the encodings of Traffic Class and TTL (time to live).
The label range specified by this type is for general use,
with special-purpose MPLS label values excluded.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 567

mpls-label-special-purpose

Summary

Name mpls-label-special-purpose
Type identityref
  
 
This type represents the special-purpose Multiprotocol Label
Switching (MPLS) label values.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC3032: MPLS Label Stack Encoding. RFC7274: Allocating and Retiring Special-Purpose MPLS Labels.
Source ietf-routing-types line 596

mpls-label-special-purpose

Summary

Name mpls-label-special-purpose
Type identityref
  
 
This type represents the special-purpose Multiprotocol Label
Switching (MPLS) label values.

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC3032: MPLS Label Stack Encoding. RFC7274: Allocating and Retiring Special-Purpose MPLS Labels.
Source ietf-routing-types line 640

mpls-label-special-purpose

Summary

Name mpls-label-special-purpose
Type identityref
  
 
This type represents the special-purpose Multiprotocol Label
Switching (MPLS) label values.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC3032: MPLS Label Stack Encoding. RFC7274: Allocating and Retiring Special-Purpose MPLS Labels.
Source ietf-routing-types line 555

mpls-srlg-flooding-type

Summary

Name mpls-srlg-flooding-type
Type enumeration
  
 
Enumerated bype for specifying how the SRLG is flooded

Details

Module openconfig-mpls
Submodule openconfig-mpls-te
Version 2017-08-24
Source openconfig-mpls-te line 95

mpls-tc

Summary

Name mpls-tc
Type uint8
  
 
Values of the MPLS Traffic Class (formerly known as
Experimental, EXP) bits

Details

Module openconfig-mpls-types
Version 2017-08-24
Source openconfig-mpls-types line 382

mstid-type

Summary

Name mstid-type
Type uint32
  
 
In an MSTP Bridge, an MSTID, i.e., a value used to identify
a spanning tree (or MST) instance

Details

Module ieee802-dot1q-types
Version 2017-07-20
Reference IEEE Std 802.1Q-2017: Virtual Bridged Local Area Networks.
Source ieee802-dot1q-types line 156

mt-id

Summary

Name mt-id
Type uint16
  
 
The type for multi-topology identifier

Details

Module ietf-bier
Version 2017-08-10
Source ietf-bier line 140

multiplier

Summary

Name multiplier
Type uint8
  
 
Multiplier

Details

Module ietf-bfd-types
Version 2017-10-30
Source ietf-bfd-types line 95

multipoint-type

Summary

Name multipoint-type
Type enumeration
  
 
p2mp or mp2mp.

Details

Module ietf-mpls-mldp
Version 2017-10-19
Source ietf-mpls-mldp line 73

nacm-action

Summary

Name nacm-action
Type enumeration
  
 
Action taken by the server when a particular
rule matches.

Details

Module yuma-nacm
Version 2012-10-05
Source yuma-nacm line 102

nacm-group

Summary

Name nacm-group
Type identityref
  
 
Type of administrative group that can be
assigned to the user, and specified in
an access control rule.

The identityref data type is used to allow as
many groups to be added as needed.  There are
no standard semantics for each identity.
It simply represents a unique group name.

Details

Module yuma-nacm
Version 2012-10-05
Source yuma-nacm line 86

nacm-rights

Summary

Name nacm-rights
Type bits
  
 
NETCONF Access Rights

Details

Module yuma-nacm
Version 2012-10-05
Source yuma-nacm line 59

nacm-user-name

Summary

Name nacm-user-name
Type string
  
 
General Purpose User Name string.

Details

Module yuma-nacm
Version 2012-10-05
Source yuma-nacm line 51

Name

Summary

Name Name
Type string
  
 
XSD name string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#Name
Source yuma-xsd line 316

name-type

Summary

Name name-type
Type string
  
 
A text string of up to 32 characters, of locally determined
significance.

Details

Module ietf-igmp-mld-snooping
Version 2017-10-25
Source ietf-igmp-mld-snooping line 140

name-type

Summary

Name name-type
Type string
  
 
A text string of up to 32 characters, of locally determined
significance.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Source ieee802-dot1q-types line 74

NameMatchMode

Summary

Name NameMatchMode
Type enumeration
  
 
Defines the search mode that should be used
when resolving YANG node names in leafs and
leaf-lists using the UrlPath data type.

Details

Module yumaworks-types
Version 2015-10-04
Source yumaworks-types line 55

nameType

Summary

Name nameType
Type string
  
 
Type for 'name' leafs, which are used to identify
specific instances within lists, etc.
Leading and trailing whitespaces are not allowed.

Details

Module ietf-ipfix-psamp
Version 2012-09-05
Source ietf-ipfix-psamp line 277

narrow-metric

Summary

Name narrow-metric
Type uint8
  
 
This type defines ISIS narrow metric.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 239

nbr-state-type

Summary

Name nbr-state-type
Type enumeration
  
 
OSPF neighbor state type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 542

NcAccessControlType

Summary

Name NcAccessControlType
Type enumeration
  
 
NCX System access control mode.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 154

NcDebugType

Summary

Name NcDebugType
Type enumeration
  
 
NCX Session debug logging control enumeration.
Each successive value includes all the previous
messages from lower value enumeration values,
plus the messages for the specified value.

off == no logging is done
write == log write  messages (NOT SUPPORTED IN YUMA)
dev0 == log developer level 0 messages (NOT SUPPORTED
	  IN YUMA)
error == log error messages
warn == log warning messages
info == log info messages
dev1    == log developer level 1 messages (NOT SUPPORTED
	   IN YUMA)
debug  == log debug level 1 messages
debug2 == log debug level 2 messages
debug3 == log debug level 3 messages
debug4 == log debug level 4 messages

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 189

NcIndex

Summary

Name NcIndex
Type uint32
  
 
Non-negative index value

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 232

NcModuleSpec

Summary

Name NcModuleSpec
Type string
  
 
A string which specifies a module name, or a filespec
which represents a module, with an optional revision date.

      If this string represents a filespec,
      containing any path separation characters, and/or
      ending with the '.yang' or '.yin' extension,
      then only that file location will be checked.

      If this string represents a module name, then
      the module search path will be checked for
      a file with the module name and the '.yang'
      or '.yin.' extension.

      If this string contains a module name
      followed by an 'at sign' character (@),
      followed by a revision string (e.g., foo@2010-01-01),
      then that specific version of the module will be used.

      If this string begins with a '~' character,
      then a username is expected to follow or
      a directory separator character.  If it begins
      with a '$' character, then an environment variable
      name is expected to follow.

      ~/some/path ==> <my-home-dir>/some/path

      ~fred/some/path ==> <fred-home-dir>/some/path

      $workdir/some/path ==> <workdir-env-var>/some/path
   

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 261

NCName

Summary

Name NCName
Type string
  
 
XSD not-namespace-qualified name string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName
Source yuma-xsd line 334

NcPathList

Summary

Name NcPathList
Type string
  
 
PATHSPEC formatted string indicating the machine-dependent
search path for the NCX programs to use.  Parameters
with this data type can be used to override the
default search order, and insert special work
directories in the search path.

Each component in the string is an absolute or
relative directory path specification.
The colon char ':' is used to separate the path strings.
Whitespace is not allowed in the string at all.

For example, the following string contains 3 paths
that would be used in the order given:

/home/users/testbed1/yang:/home/users/yang:/usr/share/yang

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 239

NcPathSpec

Summary

Name NcPathSpec
Type string
  
 
A string which specifies a directory name.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 298

NcPortNumber

Summary

Name NcPortNumber
Type uint32
  
 
Transport layer port number.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 225

NcxIdentifier

Summary

Name NcxIdentifier
Type union
  
 
Union of all the Identifier types.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 105

NcxLineLength

Summary

Name NcxLineLength
Type uint32
  
 
Requested Maximum Line Length

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 128

NcxName

Summary

Name NcxName
Type string
  
 
General Purpose NCX Name string.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 86

NcxQName

Summary

Name NcxQName
Type string
  
 
Qualified Name:
 module-name:NcxName OR owner-name:NcxName.

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 94

NcxRpcType

Summary

Name NcxRpcType
Type enumeration
  
 
NCX RPC Type Classifications

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 176

NcxSessionId

Summary

Name NcxSessionId
Type uint32
  
 
NCX Session ID number

Details

Module yuma-types
Version 2015-09-25
Source yuma-types line 121

neg-mode

Summary

Name neg-mode
Type enumeration
  
 
Defining a type of the negotiation mode

Details

Module ietf-l2vpn-svc
Version 2017-10-13
Source ietf-l2vpn-svc line 188

negativeInteger

Summary

Name negativeInteger
Type string
  
 
XSD unbounded negative integer.
This cannot be given a range like a number.
This pattern does not supoort string representations
of numbers, such as one two three

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#negativeInteger
Source yuma-xsd line 102

neighbor-event-type

Summary

Name neighbor-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-base
Version 2017-02-19
Source ietf-pim-base line 159

neighbor-event-type

Summary

Name neighbor-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-base
Version 2017-03-09
Source ietf-pim-base line 129

neighbor-list-ref

Summary

Name neighbor-list-ref
Type string
  
 
A type for a reference to a neighbor address list.
The string value is the name identifier for uniquely
identifying the referenced address list, which contains a list
of addresses that a routing policy can applied. The definition
of such an address list is outside the scope of this document.

Details

Module ietf-mpls-ldp-extended
Version 2017-10-29
Source ietf-mpls-ldp-extended line 148

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module openconfig-if-ip
Version 2017-12-21
Source openconfig-if-ip line 119

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module ietf-ip
Version 2014-06-16
Source ietf-ip line 137

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module ietf-ip
Version 2017-12-16
Source ietf-ip line 121

net

Summary

Name net
Type string
  
 
This type defines OSI NET address. A NET should should be in
the form xx.yyyy.yyyy.yyyy.00 with up to 9 sets of yyyy.

Details

Module openconfig-isis-types
Version 2017-08-24
Source openconfig-isis-types line 287

netconf-datastore-type

Summary

Name netconf-datastore-type
Type enumeration
  
 
Enumeration of possible NETCONF datastore types.

Details

Module ietf-netconf-monitoring
Version 2010-10-04
Reference RFC 4741: NETCONF Configuration Protocol
Source ietf-netconf-monitoring line 53

network-instance-ref

Summary

Name network-instance-ref
Type leafref
  
 
A re-usable type that can be referenced within other
modules that references a network instance.

Details

Module openconfig-network-instance
Version 2017-12-13
Source openconfig-network-instance line 128

new-master-reason-type

Summary

Name new-master-reason-type
Type enumeration
  
 
The reason for the virtual router to transition to master
state.

Details

Module ietf-vrrp
Version 2017-12-15
Source ietf-vrrp line 88

nexthop-lb-weight-def

Summary

Name nexthop-lb-weight-def
Type uint8
  
 
Nexthop-lb-weight is used for load-balancing.
Each list member MUST be assigned a weight
between 1 and 99. The weight determines the
proportion of traffic to be sent over a nexthop
used for forwarding as a ratio of the weight of
this nexthop divided by the weights of all the
nexthops of this route that are used for forwarding.
To perform equal load-balancing, one MAY specify
a weight of 0 for all the member nexthops.  The
value 0 is reserved for equal load-balancing
and if applied, MUST be applied to all member nexthops.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 624

nexthop-preference-def

Summary

Name nexthop-preference-def
Type uint8
  
 
Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99. Lower
values are more preferred. To download N
nexthops to the FIB, the N nexthops with the lowest
value are selected. If there are more than N
nexthops that have the same preference, an
implementation of i2rs client should select N
nexthops and download them, as for how to select
the nexthops is left to the implementations.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 609

nexthop-ref

Summary

Name nexthop-ref
Type leafref
  
 
A nexthop reference that provides
an indirection reference to a nexthop.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 642

nexthop-state-def

Summary

Name nexthop-state-def
Type identityref
  
 
Nexthop state def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 529

NMTOKEN

Summary

Name NMTOKEN
Type string
  
 
XSD NMTOKEN attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NMTOKEN
Source yuma-xsd line 417

NMTOKENS

Summary

Name NMTOKENS
Type string
  
 
XSD NMTOKENS attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NMTOKENS
Source yuma-xsd line 426

node-flag-type

Summary

Name node-flag-type
Type identityref
  
 
Node flag attributes

Details

Module ietf-l3-unicast-topology
Version 2017-12-16
Source ietf-l3-unicast-topology line 94

node-ref

Summary

Name node-ref
Type leafref
  
 
A type for an absolute reference to a node instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)

Details

Module network-topology
Version 2013-10-21
Source network-topology line 92

node-ref

Summary

Name node-ref
Type leafref
  
 
A type for an absolute reference to a node instance.
(This type should not be used for relative references.
In such a case, a relative path should be used instead.)

Details

Module network-topology
Version 2013-07-12
Source network-topology line 91

node-ref

Summary

Name node-ref
Type instance-identifier
  
 
A reference to a node

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 146

node-ref

Summary

Name node-ref
Type instance-identifier
  
 
A reference to a node in topology

Details

Module ietf-fabric-types
Version 2017-11-29
Source ietf-fabric-types line 149

nonNegativeInteger

Summary

Name nonNegativeInteger
Type string
  
 
XSD unbounded non-negative integer.
This cannot be given a range like a number.
This pattern does not supoort string representations
of numbers, such as one two three

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger
Source yuma-xsd line 116

nonPositiveInteger

Summary

Name nonPositiveInteger
Type string
  
 
XSD unbounded non-positive integer.
This cannot be given a range like a number.
This pattern does not supoort string representations
of numbers, such as one two three

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonPositiveInteger
Source yuma-xsd line 130

normalizedString

Summary

Name normalizedString
Type string
  
 
XSD normalized string

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#normalizedString
Source yuma-xsd line 38

NOTATION

Summary

Name NOTATION
Type string
  
 
XSD NOTATION attribute type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NOTATION
Source yuma-xsd line 408

notification-type

Summary

Name notification-type
Type string
  
 
The name of a notification within a YANG module.

Details

Module ietf-notification-messages
Version 2017-10-03
Reference RFC-7950 Section 7.16
Source ietf-notification-messages line 147

nsf-type

Summary

Name nsf-type
Type enumeration
  
 
This is used for type of NSF.

Details

Module ietf-i2nsf-capability
Version 2017-10-30
Source ietf-i2nsf-capability line 76

nssa-translator-state-type

Summary

Name nssa-translator-state-type
Type enumeration
  
 
OSPF NSSA translator state type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 672

ntp-clock-status

Summary

Name ntp-clock-status
Type enumeration
  
 
This defines NTP clock status.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 218

ntp-maxpoll

Summary

Name ntp-maxpoll
Type uint8
  
 
The maximul poll exponent for this NTP association.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 109

ntp-minpoll

Summary

Name ntp-minpoll
Type uint8
  
 
The minimum poll exponent for this NTP association.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 100

ntp-stratum

Summary

Name ntp-stratum
Type uint8
  
 
The level of each server in the hierarchy is defined by
a stratum number. Primary servers are assigned stratum
one; secondary servers at each lower level are assigned
stratum numbers one greater than the preceding level

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 79

ntp-sync-state

Summary

Name ntp-sync-state
Type enumeration
  
 
This defines NTP clock sync states.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 238

ntp-version

Summary

Name ntp-version
Type uint8
  
 
The current NTP version supported by corresponding
association.

Details

Module ietf-ntp
Version 2017-10-28
Source ietf-ntp line 90

object-identifier

Summary

Name object-identifier
Type string
  
 
The object-identifier type represents administratively
assigned names in a registration-hierarchical-name tree.

Values of this type are denoted as a sequence of numerical
non-negative sub-identifier values.  Each sub-identifier
value MUST NOT exceed 2^32-1 (4294967295).  Sub-identifiers
are separated by single dots and without any intermediate
whitespace.

The ASN.1 standard restricts the value space of the first
sub-identifier to 0, 1, or 2.  Furthermore, the value space
of the second sub-identifier is restricted to the range
0 to 39 if the first sub-identifier is 0 or 1.  Finally,
the ASN.1 standard requires that an object identifier
has always at least two sub-identifier.  The pattern
captures these restrictions.

Although the number of sub-identifiers is not limited,
module designers should realize that there may be
implementations that stick with the SMIv2 limit of 128
sub-identifiers.

This type is a superset of the SMIv2 OBJECT IDENTIFIER type
since it is not restricted to 128 sub-identifiers.  Hence,
this type SHOULD NOT be used to represent the SMIv2 OBJECT
IDENTIFIER type, the object-identifier-128 type SHOULD be
used instead.

Details

Module ietf-yang-types
Version 2010-09-24
Reference ISO9834-1: Information technology -- Open Systems Interconnection -- Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree
Source ietf-yang-types line 209

object-identifier

Summary

Name object-identifier
Type string
  
 
The object-identifier type represents administratively
assigned names in a registration-hierarchical-name tree.

Values of this type are denoted as a sequence of numerical
non-negative sub-identifier values.  Each sub-identifier
value MUST NOT exceed 2^32-1 (4294967295).  Sub-identifiers
are separated by single dots and without any intermediate
whitespace.

The ASN.1 standard restricts the value space of the first
sub-identifier to 0, 1, or 2.  Furthermore, the value space
of the second sub-identifier is restricted to the range
0 to 39 if the first sub-identifier is 0 or 1.  Finally,
the ASN.1 standard requires that an object identifier
has always at least two sub-identifiers.  The pattern
captures these restrictions.

Although the number of sub-identifiers is not limited,
module designers should realize that there may be
implementations that stick with the SMIv2 limit of 128
sub-identifiers.

This type is a superset of the SMIv2 OBJECT IDENTIFIER type
since it is not restricted to 128 sub-identifiers.  Hence,
this type SHOULD NOT be used to represent the SMIv2 OBJECT
IDENTIFIER type; the object-identifier-128 type SHOULD be
used instead.

Details

Module ietf-yang-types
Version 2013-07-15
Reference ISO9834-1: Information technology -- Open Systems Interconnection -- Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree
Source ietf-yang-types line 225

objective-function

Summary

Name objective-function
Type enumeration
  
 
The PCEP Objective functions

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 449

ObjViewType

Summary

Name ObjViewType
Type enumeration
  
 
Requested view format for objects.

Details

Module yangdump-pro
Version 2017-06-14
Source yangdump-pro line 310

ompe-mode

Summary

Name ompe-mode
Type enumeration
  
 
Enumeration of valid OMP-Emulation modes for Ethernet
interfaces

Details

Module ieee802-ethernet-pon
Version 2017-10-18
Reference IEEE Std 802.3, 30.3.7.1.2
Source ieee802-ethernet-pon line 291

one-way-rcv-type

Summary

Name one-way-rcv-type
Type enumeration
  
 
one way receive type

Details

Module ietf-mplstpoam
Version 2017-10-29
Source ietf-mplstpoam line 297

opaque

Summary

Name opaque
Type binary
  
 
The Opaque type supports the capability to pass arbitrary ASN.1
syntax.  A value is encoded using the ASN.1 Basic Encoding Rules
into a string of octets.  This, in turn, is encoded as an OCTET
STRING, in effect 'double-wrapping' the original ASN.1 value.

In the value set and its semantics, this type is equivalent to
the Opaque type of the SMIv2.  This type exists in the SMIv2
solely for backward-compatibility reasons and this is also
true for this YANG data type.

Details

Module ietf-yang-smiv2
Version 2012-06-22
Reference RFC 2578: Structure of Management Information Version 2 (SMIv2)
Source ietf-yang-smiv2 line 52

oper-state

Summary

Name oper-state
Type enumeration
  
 
Represents the possible values of operational states.

Details

Module ietf-hardware
Version 2017-03-07
Reference RFC 4268: EntityOperState
Source ietf-hardware line 132

oper-state

Summary

Name oper-state
Type enumeration
  
 
Represents the possible values of operational states.

Details

Module ietf-hardware
Version 2017-12-18
Reference RFC 4268: EntityOperState
Source ietf-hardware line 123

oper-status-event-type

Summary

Name oper-status-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-mpls-ldp
Version 2017-10-29
Source ietf-mpls-ldp line 138

operation

Summary

Name operation
Type enumeration
  
 
Operation type.

Details

Module ietf-schedule
Version 2017-09-06
Source ietf-schedule line 45

operation-type

Summary

Name operation-type
Type enumeration
  
 
This is used for operation type

Details

Module ietf-i2nsf-monitoring-information
Version 2017-07-19
Source ietf-i2nsf-monitoring-information line 108

operation-type

Summary

Name operation-type
Type enumeration
  
 
This is used for operation type

Details

Module ietf-i2nsf-nsf-monitoring-dm
Version 2017-10-29
Source ietf-i2nsf-nsf-monitoring-dm line 107

operational-code

Summary

Name operational-code
Type enumeration
  
 
The type of QoS request. Reserved values:   (6) to (255)
	Currently not used.  Receiver MUST ignore the option
	received with any value in this range.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 80

operational-mode

Summary

Name operational-mode
Type string
  
 
Vendor-specific mode that guarantees interoperability.
It must be an string with the following format:
B-DScW-ytz(v) where all these attributes are conformant
to the ITU-T recomendation

Details

Module ietf-flexi-grid-ted
Version 2017-07-03
Reference ITU-T G.698.2 (11/2009) Section 5.3
Source ietf-flexi-grid-ted line 61

operational-mode

Summary

Name operational-mode
Type string
  
 
Vendor-specific mode that guarantees interoperability.
It must be an string with the following format:
B-DScW-ytz(v) where all these attributes are conformant
to the ITU-T recomendation

Details

Module ietf-te-wson-types
Version 2017-10-09
Reference ITU-T G.698.2 (11/2009) Section 5.3
Source ietf-te-wson-types line 26

operational-state

Summary

Name operational-state
Type enumeration
  
 
Operational state of an interface

Details

Module ieee802-ethernet-link-oam
Version 2017-10-18
Reference [RFC-4878] dot3OamOperStatus; IEEE Std 802.3, 30.3.6.1.4, 30.3.6.1.10, and 30.3.6.1.11
Source ieee802-ethernet-link-oam line 220

operational-state

Summary

Name operational-state
Type enumeration
  
 
The operational status of the LSP

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 299

operational-state-type

Summary

Name operational-state-type
Type enumeration
  
 
operational-state-type

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 377

operational-status

Summary

Name operational-status
Type enumeration
  
 
Operational state of a LSP Ping test.

Details

Module ietf-lspping
Version 2017-10-29
Source ietf-lspping line 94

operator

Summary

Name operator
Type enumeration
  
 
The source and destination port range definitions
can be further qualified using an operator. An
operator is needed only if lower-port is specified
and upper-port is not specified. The operator
therefore further qualifies lower-port only.

Details

Module ietf-packet-fields
Version 2017-10-03
Source ietf-packet-fields line 61

operator-state

Summary

Name operator-state
Type enumeration
  
 
Operator states on an alarm.  The 'closed' state indicates
that an operator considers the alarm being resolved.  This
is separate from the resource alarm clear flag.

Details

Module ietf-alarms
Version 2017-10-30
Source ietf-alarms line 264

opt-if-och-tca-types

Summary

Name opt-if-och-tca-types
Type enumeration
  
 
 The different types of TCA's

Details

Module ietf-ext-xponder-wdm-if
Version 2017-03-06
Source ietf-ext-xponder-wdm-if line 54

optimization-goal

Summary

Name optimization-goal
Type enumeration
  
 
TE optimization goal

Details

Module ietf-te-types
Version 2017-10-29
Source ietf-te-types line 993

origin-ref

Summary

Name origin-ref
Type identityref
  
 
An origin identity reference.

Details

Module ietf-origin
Version 2017-08-17
Source ietf-origin line 123

ospf-area-identifier

Summary

Name ospf-area-identifier
Type union
  
 
An identifier for an area with OSPF version 2 or 3. This value
is expressed as either a dotted-quad, or a unsigned 32-bit
number

Details

Module openconfig-ospf-types
Version 2017-08-24
Source openconfig-ospf-types line 45

ospf-metric

Summary

Name ospf-metric
Type uint16
  
 
A common type that can be utilised to express an OSPF metric

Details

Module openconfig-ospf-types
Version 2017-08-24
Source openconfig-ospf-types line 56

OwnerString

Summary

Name OwnerString
Type string
  
 
This data type is used to model an administratively
assigned name of the owner of a resource.  This information
is taken from the NVT ASCII character set.  It is suggested
that this name contain one or more of the following: ASCII
form of the manager station's transport address, management
station name (e.g., domain name), network management
personnel's name, location, or phone number.  In some cases
the agent itself will be the owner of an entry.  In these
cases, this string shall be set to a string starting with
'agent'.

Details

Module IF-MIB
Version 2000-06-14
Source IF-MIB line 66

packet-type

Summary

Name packet-type
Type enumeration
  
 
OSPF packet type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 640

padding-fill-mode

Summary

Name padding-fill-mode
Type enumeration
  
 
Indicates what type of packet padding is used in the
TWAMP-Test packets.

Details

Module ietf-twamp
Version 2017-10-16
Source ietf-twamp line 226

pae-access-status

Summary

Name pae-access-status
Type enumeration
  
 
Indicates the transmitters Controlled Port operational status
and current level of access resulting from authentication and
the consequent authorization controls applied by that ports
clients.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 10.4, Clause 12.5
Source ieee802-dot1x line 211

pae-auth-data

Summary

Name pae-auth-data
Type string
  
 
Authorization data associated with the CAK.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 9.16
Source ieee802-dot1x line 291

pae-ckn

Summary

Name pae-ckn
Type string
  
 
Indicates the CAK name to identify the Connectivity
Association Key (CAK) which is the root key in the MACsec Key
Agreement key hierarchy. All potential members of the CA use
the same CKN.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 9.3.1, Clause 6.2
Source ieee802-dot1x line 266

pae-if-index

Summary

Name pae-if-index
Type int32
  
 
The interface index value represented by this interface.

Details

Module ieee802-dot1x
Version 2017-07-20
Source ieee802-dot1x line 311

pae-kmd

Summary

Name pae-kmd
Type string
  
 
A Key Management Domain (KMD). A string of up to 253 UTF-8
characters that names the transmitting authenticators key
management domain.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE Clause 12.6
Source ieee802-dot1x line 279

pae-nid

Summary

Name pae-nid
Type string
  
 
Network Identify, which is a UTF-8 string identifying a
network or network service.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 3, Clause 10.1, Clause 12.6
Source ieee802-dot1x line 125

pae-nid-capabilities

Summary

Name pae-nid-capabilities
Type bits
  
 
Authentication and protection capabilities supported for the
NID. Indicates the combinations of authentication and
protection capabilities supported for a NID. Any set of these
combinations can be supported.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 10.1, Clause 11.12.3
Source ieee802-dot1x line 159

pae-session-id

Summary

Name pae-session-id
Type string
  
 
Session Identifier, which is a utf8 string, uniquely
identifying the session within the context of the PAEs
system.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 12.5.1
Source ieee802-dot1x line 147

pae-session-user-name

Summary

Name pae-session-user-name
Type string
  
 
Session user name, which is a utf8 string, representing the
identify of the peer Supplicant.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1X-2010 Clause 12.5.1
Source ieee802-dot1x line 136

pae-system-ref

Summary

Name pae-system-ref
Type leafref
  
 
This type is used by data models that need to reference
configured PAE systems.

Details

Module ieee802-dot1x
Version 2017-07-20
Source ieee802-dot1x line 116

path

Summary

Name path
Type string
  
 
This type represents a string with path to the file.

Details

Module yang-catalog
Version 2017-09-26
Source yang-catalog line 114

pause-fc-direction-type

Summary

Name pause-fc-direction-type
Type enumeration
  
 
Enumerates the possible PAUSE frame based flow control
settings that can be used in explicit configuration, or when
reporting the operational state

Details

Module ieee802-ethernet-interface
Version 2017-02-23
Reference IEEE 802.3.1, dot3PauseAdminMode and dot3PauseOperMode
Source ieee802-ethernet-interface line 103

pause-fc-direction-type

Summary

Name pause-fc-direction-type
Type enumeration
  
 
Enumerates the possible PAUSE frame based PAUSE frame based flow
control settings that can be used in explicit configuration, or when
reporting the operational state

Details

Module ieee802-ethernet-interface
Version 2017-10-18
Reference IEEE Std 802.3.1, dot3PauseAdminMode and dot3PauseOperMode
Source ieee802-ethernet-interface line 84

pbb-component-type

Summary

Name pbb-component-type
Type enumeration
  
 
This type is used to identify the type of PBB component

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 341

pcep-admin-status

Summary

Name pcep-admin-status
Type enumeration
  
 
The Admin Status of the PCEP entity.
Takes one of the following values
    - admin-status-up(1): Admin Status is Up.
    - admin-status-down(2): Admin Status is Down

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 117

pcep-initiator

Summary

Name pcep-initiator
Type enumeration
  
 
The initiator of the session, that is, whether the TCP
connection was initiated by the local PCEP entity or
the remote peer.
Takes one of the following values
    - local(1): Initiated locally
    - remote(2): Initiated remotely

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 184

pcep-oper-status

Summary

Name pcep-oper-status
Type enumeration
  
 
The operational status of the PCEP entity.
Takes one of the following values
    - oper-status-up(1): Active
    - oper-status-down(2): Inactive
    - oper-status-going-up(3): Activating
    - oper-status-going-down(4): Deactivating
    - oper-status-failed(5): Failed
    - oper-status-failed-perm(6): Failed Permanantly

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 138

pcep-role

Summary

Name pcep-role
Type enumeration
  
 
The role of a PCEP speaker.
Takes one of the following values
- unknown(0): the role is not known.
- pcc(1): the role is of a Path Computation
  Client (PCC).
- pce(2): the role is of a Path Computation
  Server (PCE).
- pccAndPce(3): the role is of both a PCC and
  a PCE.

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 79

pcep-sess-state

Summary

Name pcep-sess-state
Type enumeration
  
 
The current state of the session.
The set of possible states excludes the idle state
since entries do not exist in the idle state.
Takes one of the following values
   - tcp-pending(1): PCEP TCP Pending state
   - open-wait(2): PCEP Open Wait state
   - keep-wait(3): PCEP Keep Wait state
   - session-up(4): PCEP Session Up state

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 207

pcp-selection-type

Summary

Name pcp-selection-type
Type enumeration
  
 
Priority Code Point selection types.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Reference IEEE 802.1Q-2017 Clause 12.6.2.5.3, 6.9.3
Source ieee802-dot1q-types line 167

peer-list-ref

Summary

Name peer-list-ref
Type string
  
 
A type for a reference to a peer address list.
The string value is the name identifier for uniquely
identifying the referenced address list, which contains a list
of addresses that a routing policy can applied. The definition
of such an address list is outside the scope of this document.

Details

Module ietf-mpls-ldp-extended
Version 2017-10-29
Source ietf-mpls-ldp-extended line 169

peer-type

Summary

Name peer-type
Type enumeration
  
 
labels a peer or peer group as explicitly internal or
external

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 335

peer-type

Summary

Name peer-type
Type enumeration
  
 
Labels a peer or peer group as explicitly internal or
external

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 442

Per-MN-Agg-Max-DL-Bit-Rate-Value

Summary

Name Per-MN-Agg-Max-DL-Bit-Rate-Value
Type uint32
  
 
The aggregate maximum downlink bit rate that is
requested/allocated for all the mobile node's IP flows.
The measurement units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 253

Per-MN-Agg-Max-UL-Bit-Rate-Value

Summary

Name Per-MN-Agg-Max-UL-Bit-Rate-Value
Type uint32
  
 
The aggregate maximum uplink bit rate that is
   requested/allocated for the mobile node's IP flows. The
   measurement units are bits per second.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 261

percent

Summary

Name percent
Type uint8
  
 
Percentage

Details

Module ietf-address-pool
Version 2015-10-14
Source ietf-address-pool line 55

percent

Summary

Name percent
Type uint8
  
 
Percentage

Details

Module ietf-nat
Version 2017-11-16
Source ietf-nat line 69

percent

Summary

Name percent
Type uint8
  
 
Percentage

Details

Module ietf-pcp-server
Version 2017-10-17
Source ietf-pcp-server line 45

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 383

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module ietf-routing-types
Version 2017-10-13
Source ietf-routing-types line 604

percentage

Summary

Name percentage
Type decimal64
  
 
Percentage

Details

Module ietf-twamp-light
Version 2017-06-13
Source ietf-twamp-light line 85

percentage

Summary

Name percentage
Type decimal64
  
 
Percentage

Details

Module ietf-stamp
Version 2017-10-20
Source ietf-stamp line 86

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module ietf-te-types
Version 2017-10-29
Source ietf-te-types line 1037

percentage

Summary

Name percentage
Type decimal64
  
 
Percentage.

Details

Module ietf-connectionless-oam
Version 2017-09-06
Source ietf-connectionless-oam line 120

percentage

Summary

Name percentage
Type uint8
  
 
Percentage value in integer format.

Details

Module ietf-poe-power-management
Version 2017-03-09
Source ietf-poe-power-management line 45

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module openconfig-types
Version 2017-08-16
Source openconfig-types line 56

percentile

Summary

Name percentile
Type decimal64
  
 
Percentile is a measure used in statistics
indicating the value below which a given
percentage of observations in a group of
observations fall.

Details

Module ietf-twamp-light
Version 2017-06-13
Source ietf-twamp-light line 92

percentile

Summary

Name percentile
Type decimal64
  
 
Percentile is a measure used in statistics
indicating the value below which a given
percentage of observations in a group of
observations fall.

Details

Module ietf-stamp
Version 2017-10-20
Source ietf-stamp line 92

performance-metric-normality

Summary

Name performance-metric-normality
Type enumeration
  
 
Indicates whether a performance metric is normal, abnormal, or
unknown.

Details

Module ietf-te-types
Version 2017-10-29
Reference RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. RFC7810: IS-IS Traffic Engineering (TE) Metric Extensions. RFC7823: Performance-Based Path Selection for Explicitly Routed Label Switched Paths (LSPs) Using TE Metric Extensions
Source ietf-te-types line 1045

phys-address

Summary

Name phys-address
Type string
  
 
A physical layer address, expressed as a series of pairs of
hexadecimal digits.

Details

Module openconfig-yang-types
Version 2017-07-30
Source openconfig-yang-types line 140

phys-address

Summary

Name phys-address
Type string
  
 
Represents media- or physical-level addresses represented
as a sequence octets, each octet represented by two hexadecimal
numbers.  Octets are separated by colons.  The canonical
representation uses lowercase characters.

In the value set and its semantics, this type is equivalent
to the PhysAddress textual convention of the SMIv2.

Details

Module ietf-yang-types
Version 2010-09-24
Reference RFC 2579: Textual Conventions for SMIv2
Source ietf-yang-types line 357

phys-address

Summary

Name phys-address
Type string
  
 
Represents media- or physical-level addresses represented
as a sequence octets, each octet represented by two hexadecimal
numbers.  Octets are separated by colons.  The canonical
representation uses lowercase characters.

In the value set and its semantics, this type is equivalent
to the PhysAddress textual convention of the SMIv2.

Details

Module ietf-yang-types
Version 2013-07-15
Reference RFC 2579: Textual Conventions for SMIv2
Source ietf-yang-types line 389

PhysAddress

Summary

Name PhysAddress
Type string
  
 
Represents media- or physical-level addresses.

Details

Module SNMPv2-TC
Version none
Source SNMPv2-TC line 59

pim-mode

Summary

Name pim-mode
Type enumeration
  
 
The PIM mode in which a group is operating.

Details

Module ietf-pim-base
Version 2017-02-19
Source ietf-pim-base line 173

pim-mode

Summary

Name pim-mode
Type enumeration
  
 
The PIM mode in which a group is operating.

Details

Module ietf-pim-base
Version 2017-03-09
Source ietf-pim-base line 142

pinned-certificates

Summary

Name pinned-certificates
Type leafref
  
 
This typedef enables importing modules to easily define a
reference to pinned-certificates.  Use of this type also
impacts the YANG tree diagram output.

Details

Module ietf-keystore
Version 2017-10-30
Reference I-D.ietf-netmod-yang-tree-diagrams: YANG Tree Diagrams
Source ietf-keystore line 153

pinned-host-keys

Summary

Name pinned-host-keys
Type leafref
  
 
This typedef enables importing modules to easily define a
reference to pinned-host-keys.  Use of this type also
impacts the YANG tree diagram output.

Details

Module ietf-keystore
Version 2017-10-30
Reference I-D.ietf-netmod-yang-tree-diagrams: YANG Tree Diagrams
Source ietf-keystore line 165

pkcs7

Summary

Name pkcs7
Type binary
  
 
A PKCS #7 SignedData structure, as specified by Section 9.1
in RFC 2315, encoded using ASN.1 distinguished encoding rules
(DER), as specified in ITU-T X.690.

Details

Module ietf-zerotouch-device
Version 2017-10-19
Reference RFC 2315: PKCS #7: Cryptographic Message Syntax Version 1.5. ITU-T X.690: Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).
Source ietf-zerotouch-device line 67

pkcs7

Summary

Name pkcs7
Type binary
  
 
A PKCS #7 SignedData structure, as specified by Section 9.1
in RFC 2315, encoded using ASN.1 distinguished encoding rules
(DER), as specified in ITU-T X.690.

Details

Module ietf-zerotouch-bootstrap-server
Version 2017-10-19
Reference RFC 2315: PKCS #7: Cryptographic Message Syntax Version 1.5. ITU-T X.690: Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER).
Source ietf-zerotouch-bootstrap-server line 47

podl-detection-state

Summary

Name podl-detection-state
Type enumeration
  
 
detection state of a PoDL PSE

Details

Module ieee802-ethernet-pse
Version 2017-10-18
Reference IEEE Std 802.3, 30.15.1.3
Source ieee802-ethernet-pse line 112

policy-result-type

Summary

Name policy-result-type
Type enumeration
  
 
Type used to specify route disposition in
a policy chain

Details

Module openconfig-routing-policy
Version 2017-07-14
Source openconfig-routing-policy line 118

port-id-type

Summary

Name port-id-type
Type enumeration
  
 
Type definition with enumerations describing the basis of
the port identifier

Details

Module openconfig-lldp-types
Version 2016-05-16
Reference IEEE 802.1AB LLDP MIB
Source openconfig-lldp-types line 248

port-num-range

Summary

Name port-num-range
Type union
  
 
Port numbers may be represented as a single value,
an inclusive range as <lower>..<higher>, or as ANY to
indicate a wildcard.

Details

Module openconfig-packet-match-types
Version 2017-05-26
Source openconfig-packet-match-types line 240

port-number

Summary

Name port-number
Type uint16
  
 
A 16-bit port number used by a transport protocol such as TCP
or UDP.

Details

Module openconfig-inet-types
Version 2017-08-24
Reference RFC 768 User Datagram Protocol RFC 793 Transmission Control Protocol
Source openconfig-inet-types line 304

port-number

Summary

Name port-number
Type uint16
  
 
The port-number type represents a 16-bit port number of an
Internet transport layer protocol such as UDP, TCP, DCCP, or
SCTP.  Port numbers are assigned by IANA.  A current list of
all assignments is available from <http://www.iana.org/>.

Note that the port number value zero is reserved by IANA.  In
situations where the value zero does not make sense, it can
be excluded by subtyping the port-number type.

In the value set and its semantics, this type is equivalent
to the InetPortNumber textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2010-09-24
Reference RFC 768: User Datagram Protocol RFC 793: Transmission Control Protocol RFC 4960: Stream Control Transmission Protocol RFC 4340: Datagram Congestion Control Protocol (DCCP) RFC 4001: Textual Conventions for Internet Network Addresses
Source ietf-inet-types line 113

port-number

Summary

Name port-number
Type uint16
  
 
The port-number type represents a 16-bit port number of an
Internet transport-layer protocol such as UDP, TCP, DCCP, or
SCTP.  Port numbers are assigned by IANA.  A current list of
all assignments is available from <http://www.iana.org/>.

Note that the port number value zero is reserved by IANA.  In
situations where the value zero does not make sense, it can
be excluded by subtyping the port-number type.
In the value set and its semantics, this type is equivalent
to the InetPortNumber textual convention of the SMIv2.

Details

Module ietf-inet-types
Version 2013-07-15
Reference RFC 768: User Datagram Protocol RFC 793: Transmission Control Protocol RFC 4960: Stream Control Transmission Protocol RFC 4340: Datagram Congestion Control Protocol (DCCP) RFC 4001: Textual Conventions for Internet Network Addresses
Source ietf-inet-types line 122

port-number

Summary

Name port-number
Type uint16
  
 
A 16-bit port number used by a transport protocol such as TCP
or UDP.

Details

Module openconfig-inet-types
Version 2017-01-26
Reference RFC 768 User Datagram Protocol RFC 793 Transmission Control Protocol
Source openconfig-inet-types line 151

port-number-type

Summary

Name port-number-type
Type uint32
  
 
The port number of the Bridge port for which this entry
     contains Bridge management information.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Source ieee802-dot1q-types line 83

port-state-enumeration

Summary

Name port-state-enumeration
Type enumeration
  
 
The current state of the protocol engine associated 
with the port.  Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-01-09
Reference IEEE Std 1588-2008: 8.2.5.3.1, 9.2.5
Source ietf-ptp-dataset line 54

port-state-enumeration

Summary

Name port-state-enumeration
Type enumeration
  
 
The current state of the protocol engine associated 
with the port.  Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-02-08
Reference IEEE Std 1588-2008: 8.2.5.3.1, 9.2.5
Source ietf-ptp-dataset line 54

port-state-enumeration

Summary

Name port-state-enumeration
Type enumeration
  
 
The current state of the protocol engine associated 
with the port.  Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp-dataset
Version 2017-04-20
Reference IEEE Std 1588-2008: 8.2.5.3.1, 9.2.5
Source ietf-ptp-dataset line 59

port-state-enumeration

Summary

Name port-state-enumeration
Type enumeration
  
 
The current state of the protocol engine associated
with the port.  Values for this enumeration are specified
by the IEEE 1588 standard exclusively.

Details

Module ietf-ptp
Version 2017-11-28
Reference IEEE Std 1588-2008: 8.2.5.3.1, 9.2.5
Source ietf-ptp line 57

positiveInteger

Summary

Name positiveInteger
Type string
  
 
XSD unbounded positive integer.
This cannot be given a range like a number.
This pattern does not supoort string representations
of numbers, such as one two three

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#positiveInteger
Source yuma-xsd line 88

power

Summary

Name power
Type decimal64
  
 
Type used for power values, selected and measured.

Details

Module ietf-microwave-radio-link
Version 2017-10-23
Source ietf-microwave-radio-link line 391

power-class

Summary

Name power-class
Type enumeration
  
 
power class

Details

Module ieee802-ethernet-pse
Version 2017-10-18
Reference IEEE Std 802.3, 30.9.1.1.6 aPSEPowerClassification
Source ieee802-ethernet-pse line 150

prefix-flag-type

Summary

Name prefix-flag-type
Type identityref
  
 
Prefix flag attributes

Details

Module ietf-l3-unicast-topology
Version 2017-12-16
Source ietf-l3-unicast-topology line 87

prefix-list-ref

Summary

Name prefix-list-ref
Type string
  
 
A type for a reference to a prefix list.
The string value is the name identifier for uniquely
identifying the referenced prefix set, which contains a list
of prefixes that a routing policy can applied. The definition
of such a prefix set is outside the scope of this document.

Details

Module ietf-mpls-ldp-extended
Version 2017-10-29
Source ietf-mpls-ldp-extended line 158

prefix-set-ref

Summary

Name prefix-set-ref
Type string
  
 
A type for a reference to a prefix set.
The string value is the name identifier for uniquely
identifying the referenced prefix set, which contains a list
of prefixes that a routing policy can applied. The definition
of such a prefix set is outside the scope of this document.

Details

Module ietf-rip
Version 2017-12-05
Source ietf-rip line 118

priority-type

Summary

Name priority-type
Type uint8
  
 
A range of priorities from 0 to 7 (inclusive). The Priority
     Code Point (PCP) is a 3-bit field that refers to the
class of service associated with an 802.1Q VLAN tagged frame.
The field specifies a priority value between 0 and 7, these
values can be used by quality of service (QoS) to prioritize
different classes of traffic.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Source ieee802-dot1q-types line 92

profile-index-range

Summary

Name profile-index-range
Type int32
  
 
Range used for the profile index. Currently restricted to
0 or 1 to identify the odd or even profiles.

Details

Module ietf-pot-profile
Version 2016-06-15
Source ietf-pot-profile line 27

protocol-frame-format-type

Summary

Name protocol-frame-format-type
Type enumeration
  
 
A value representing the frame format to be matched.

Details

Module ieee802-dot1q-types
Version 2017-07-20
Reference IEEE 802.1Q-2017 Clause 12.10.1.7.1
Source ieee802-dot1q-types line 192

pse-detection-state

Summary

Name pse-detection-state
Type enumeration
  
 
detection state of a multi-pair PSE

Details

Module ieee802-ethernet-pse
Version 2017-10-18
Reference IEEE Std 802.3, 30.9.1.1.5
Source ieee802-ethernet-pse line 79

pse-detection-state

Summary

Name pse-detection-state
Type enumeration
  
 
detection state of a multi-pair PSE

Details

Module ietf-poe-power-management
Version 2017-03-09
Reference IEEE Std 802.3, 30.9.1.1.5
Source ietf-poe-power-management line 105

pseudowire-ref

Summary

Name pseudowire-ref
Type leafref
  
 
A type that is a reference to a pseudowire

Details

Module ietf-pseudowires
Version 2017-06-26
Source ietf-pseudowires line 27

pseudowire-status-type

Summary

Name pseudowire-status-type
Type bits
  
 
Pseudowire status type, as registered in the IANA Pseudowire Status Code Registry

Details

Module ietf-pseudowires
Version 2017-06-26
Source ietf-pseudowires line 53

pst

Summary

Name pst
Type enumeration
  
 
The Path Setup Type

Details

Module ietf-pcep
Version 2017-07-01
Source ietf-pcep line 410

pw-rtp-flag

Summary

Name pw-rtp-flag
Type enumeration
  
 
The use flag of rtp header.

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 194

pw-template-ref

Summary

Name pw-template-ref
Type leafref
  
 
A type that is a reference to a pw-template

Details

Module ietf-pseudowires
Version 2017-06-26
Source ietf-pseudowires line 34

pw-timestamp-mode

Summary

Name pw-timestamp-mode
Type enumeration
  
 
The timestamp mode of TDM service.

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 212

pw-type

Summary

Name pw-type
Type enumeration
  
 
The PW type of the PW.

Details

Module ietf-pw
Version 2017-05-05
Source ietf-pw line 83

qinq-id

Summary

Name qinq-id
Type string
  
 
Type definition representing a single double-tagged/QinQ VLAN
identifier. The format of a QinQ VLAN-ID is x.y where X is the
'outer' VLAN identifier, and y is the 'inner' VLAN identifier.
Both x and y must be valid VLAN IDs (1 <= vlan-id <= 4094)
with the exception that y may be equal to a wildcard (*). In
cases where y is set to the wildcard, this represents all inner
VLAN identifiers where the outer VLAN identifier is equal to
x

Details

Module openconfig-vlan-types
Version 2017-07-14
Source openconfig-vlan-types line 105

qinq-id-range

Summary

Name qinq-id-range
Type union
  
 
A type definition representing a range of double-tagged/QinQ
VLAN identifiers. The format of a QinQ VLAN-ID range can be
specified in three formats. Where the range is outer VLAN IDs
the range is specified as x..y.z. In this case outer VLAN
identifiers meeting the criteria x <= outer-vlan-id <= y are
accepted iff the inner VLAN-ID is equal to y - or any inner-tag
if the wildcard is specified. Alternatively the range can be
specified as x.y..z. In this case only VLANs with an
outer-vlan-id qual to x are accepted (x may again be the
wildcard). Inner VLANs are accepted if they meet the inequality
y <= inner-vlan-id <= z.

Details

Module openconfig-vlan-types
Version 2017-07-14
Source openconfig-vlan-types line 124

QName

Summary

Name QName
Type string
  
 
XSD namespace-qualified name string type.

Details

Module yuma-xsd
Version 2009-11-21
Reference http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName
Source yuma-xsd line 325

qos-attrubite-type-enum

Summary

Name qos-attrubite-type-enum
Type enumeration
  
 
The type of the QoS attribute.  This specification reserves
  the following reserved values.
    (12) to (254) -  Reserved
       These values are reserved for future allocation.

    (255)  Reserved
       This value is reserved and cannot be used.

Details

Module ietf-pmip-qos
Version 2017-10-29
Source ietf-pmip-qos line 119

queue-behavior

Summary

Name queue-behavior
Type enumeration
  
 
Type definition for different queueing behaviours that
are available to a scheduler.

Details

Module openconfig-qos-types
Version 2016-12-16
Source openconfig-qos-types line 115

read-write-mode-type

Summary

Name read-write-mode-type
Type enumeration
  
 
Indicates if entity is read-write,
read-only, etc.

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 45

redundancy-group-template-ref

Summary

Name redundancy-group-template-ref
Type leafref
  
 
redundancy-group-template-ref

Details

Module ietf-l2vpn
Version 2017-09-21
Source ietf-l2vpn line 354

redundancy-type

Summary

Name redundancy-type
Type enumeration
  
 
Redundancy type

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 128

reliability-level-type

Summary

Name reliability-level-type
Type enumeration
  
 
Reliability level

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 109

remove-private-as-option

Summary

Name remove-private-as-option
Type identityref
  
 
set of options for configuring how private AS path numbers
are removed from advertisements

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 374

remove-private-as-option

Summary

Name remove-private-as-option
Type identityref
  
 
Set of options for configuring how private AS path numbers
are removed from advertisements

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 483

reply-mode

Summary

Name reply-mode
Type enumeration
  
 
Reply mode.

Details

Module ietf-lspping
Version 2017-10-29
Source ietf-lspping line 52

resource

Summary

Name resource
Type union
  
 
This is an identification of the alarming resource, such as an
interface.  It should be as fine-grained as possible both to
guide the operator and to guarantee uniqueness of the
alarms.  If a resource has both a config and a state tree
normally this should identify the state tree,
(e.g., /interfaces-state/interface/name).
But if the instrumentation can detect a broken config, this
should be identified as the resource.
If the alarming resource is modelled in YANG, this
type will be an instance-identifier.  If the resource is an
SNMP object, the type will be an object-identifier.  If the
resource is anything else, for example a distinguished name or
a CIM path, this type will be a string.

Details

Module ietf-alarms
Version 2017-10-30
Source ietf-alarms line 153

resource-reservation-level-type

Summary

Name resource-reservation-level-type
Type enumeration
  
 
Resource reservation level

Details

Module ietf-coms-core
Version 2017-10-27
Source ietf-coms-core line 90

response-type

Summary

Name response-type
Type enumeration
  
 
The type of response expected from the server
for this request.

Details

Module yumaworks-test
Version 2013-03-31
Source yumaworks-test line 79

restart-exit-reason-type

Summary

Name restart-exit-reason-type
Type enumeration
  
 
Describes the outcome of the last attempt at a
graceful restart, either by itself or acting
as a helper.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 606

restart-helper-status-type

Summary

Name restart-helper-status-type
Type enumeration
  
 
Restart helper status type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 589

restart-status-type

Summary

Name restart-status-type
Type enumeration
  
 
OSPF graceful restart status type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 693

result-type

Summary

Name result-type
Type enumeration
  
 
Result of each LSP Ping test probe.

Details

Module ietf-lspping
Version 2017-10-29
Source ietf-lspping line 112

revision

Summary

Name revision
Type binary
  
 
Revision date encoded as a binary string as follow:
- First byte = Year divided by 100
- Second byte = Year modulo 100 (0 to 99)
- Third byte = Month (1 = January to 12 = december)
- Forth byte = Day (1 to 31)

Details

Module ietf-constrained-yang-library
Version 2017-01-20
Source ietf-constrained-yang-library line 57

revision-identifier

Summary

Name revision-identifier
Type string
  
 
Represents a specific date in YYYY-MM-DD format.
TBD: make pattern more precise to exclude leading zeros.

Details

Module ietf-yang-library
Version 2015-01-30
Source ietf-yang-library line 63

revision-identifier

Summary

Name revision-identifier
Type string
  
 
Represents a specific date in YYYY-MM-DD format.

Details

Module ietf-yang-library
Version 2016-06-21
Source ietf-yang-library line 63

revision-identifier

Summary

Name revision-identifier
Type string
  
 
Represents a date in YYYY-MM-DD format.

Details

Module ietf-sid-file
Version 2017-11-26
Source ietf-sid-file line 40

revision-identifier

Summary

Name revision-identifier
Type string
  
 
Represents a specific date in YYYY-MM-DD format.

Details

Module ietf-yang-library
Version 2017-10-30
Source ietf-yang-library line 76

rib-family-def

Summary

Name rib-family-def
Type identityref
  
 
Rib address family def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 383

route-change-reason-def

Summary

Name route-change-reason-def
Type identityref
  
 
Route change reason def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 601

route-distinguisher

Summary

Name route-distinguisher
Type string
  
 
A route distinguisher is an 8-octet value used to distinguish
routes from different BGP VPNs (RFC 4364). A route
distinguisher consists of three fields: A 2-octet type field,
an administrator field, and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4364, the encoding pattern is defined as:

0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
2-octet-other-hex-number:6-octet-hex-number

Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs).
Source ietf-routing-types line 288

route-distinguisher

Summary

Name route-distinguisher
Type string
  
 
A route distinguisher is an 8-octet value used to
distinguish routes from different BGP VPNs (RFC 4364).
As per RFC 4360, a route distinguisher will have the same
format as a route target and will consist of two or three
fields including a 2-octet type field, an administrator
field, and, optionally, an assigned number field.

According to the data formats for type 0, 1, 2, and 6
defined in RFC4360, RFC5668, and RFC7432, the encoding
pattern is defined as:

0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
6:6-octet-mac-address.

Additionally, a generic pattern is defined for future
route discriminator types:

2-octet-other-hex-number:6-octet-hex-number

Some valid examples are: 0:100:100, 1:1.1.1.1:100,
2:1234567890:203 and 6:26:00:08:92:78:00

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC4360: BGP Extended Communities Attribute. RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs) RFC5668: 4-Octet AS Specific BGP Extended Community. RFC7432: BGP MPLS-Based Ethernet VPN
Source ietf-routing-types line 263

route-distinguisher

Summary

Name route-distinguisher
Type string
  
 
A route distinguisher is an 8-octet value used to distinguish
routes from different BGP VPNs (RFC 4364). A route
distinguisher consists of three fields: A 2-octet type field,
an administrator field, and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4364, the encoding pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
2-octet-other-hex-number:6-octet-hex-number
Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs).
Source ietf-routing-types line 271

route-distinguisher

Summary

Name route-distinguisher
Type union
  
 
A route distinguisher value

Details

Module openconfig-network-instance-types
Version 2017-08-24
Reference RFC4364
Source openconfig-network-instance-types line 232

route-installed-state-def

Summary

Name route-installed-state-def
Type identityref
  
 
Route installed state def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 555

route-origin

Summary

Name route-origin
Type string
  
 
A route origin is an 8-octet BGP extended community
identifying the set of sites where the BGP route
originated (RFC 4364). A route target consists of two
or three fields: a 2-octet type field, an administrator
field, and, optionally, an assigned number field.

According to the data formats for type 0, 1, 2, and 6
defined in RFC4360, RFC5668, and RFC7432, the encoding
pattern is defined as:

0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
6:6-octet-mac-address.

Additionally, a generic pattern is defined for future
route origin types:

2-octet-other-hex-number:6-octet-hex-number

Some valid examples are: 0:100:100, 1:1.1.1.1:100,
2:1234567890:203 and 6:26:00:08:92:78:00

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC4360: BGP Extended Communities Attribute. RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs) RFC5668: 4-Octet AS Specific BGP Extended Community. RFC7432: BGP MPLS-Based Ethernet VPN
Source ietf-routing-types line 325

route-policy-ref

Summary

Name route-policy-ref
Type string
  
 
A type for a reference to a route policy.
The string value is the name identifier for uniquely
identifying the referenced routing policy, which contains one
or more policy rules that can be used for a routing decision.
The definition of such a routing policy is outside the scope
of this document.

Details

Module ietf-rip
Version 2017-12-05
Source ietf-rip line 128

route-preference

Summary

Name route-preference
Type uint32
  
 
This type is used for route preferences.

Details

Module ietf-routing
Version 2016-11-04
Source ietf-routing line 138

route-preference

Summary

Name route-preference
Type uint32
  
 
This type is used for route preferences.

Details

Module ietf-routing
Version 2017-12-11
Source ietf-routing line 131

route-preference

Summary

Name route-preference
Type uint32
  
 
This type is used for route preferences.

Details

Module ietf-routing-2
Version 2017-09-13
Source ietf-routing-2 line 127

route-state-def

Summary

Name route-state-def
Type identityref
  
 
Route state def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 503

route-target

Summary

Name route-target
Type string
  
 
A route target is an 8-octet BGP extended community
initially identifying a set of sites in a BGP
VPN (RFC 4364). However, it has since taken on a more
general role in BGP route filtering.
A route target consists of three fields:
a 2-octet type field, an administrator field,
and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4360 and RFC5668, the encoding pattern is defined as:

0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.

Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC4360: BGP Extended Communities Attribute. RFC5668: 4-Octet AS Specific BGP Extended Community.
Source ietf-routing-types line 223

route-target

Summary

Name route-target
Type string
  
 
A route target is an 8-octet BGP extended community
initially identifying a set of sites in a BGP
VPN (RFC 4364). However, it has since taken on a more
general role in BGP route filtering.
A route target consists of two or three fields:
a 2-octet type field, an administrator field,
and, optionally, an assigned number field.

According to the data formats for type 0, 1, 2, and 6
defined in RFC4360, RFC5668, and RFC7432, the encoding
pattern is defined as:

0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
6:6-octet-mac-address.

Additionally, a generic pattern is defined for future
route target types:

2-octet-other-hex-number:6-octet-hex-number

Some valid examples are: 0:100:100, 1:1.1.1.1:100,
2:1234567890:203 and 6:26:00:08:92:78:00

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC4360: BGP Extended Communities Attribute. RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs) RFC5668: 4-Octet AS Specific BGP Extended Community. RFC7432: BGP MPLS-Based Ethernet VPN
Source ietf-routing-types line 142

route-target

Summary

Name route-target
Type string
  
 
A route target is an 8-octet BGP extended community
initially identifying a set of sites in a BGP
VPN (RFC 4364). However, it has since taken on a more
general role in BGP route filtering.
A route target consists of three fields:
a 2-octet type field, an administrator field,
and an assigned number field.
According to the data formats for type 0, 1, and 2 defined in
RFC4360 and RFC5668, the encoding pattern is defined as:
0:2-octet-asn:4-octet-number
1:4-octet-ipv4addr:2-octet-number
2:4-octet-asn:2-octet-number.
Some valid examples are: 0:100:100, 1:1.1.1.1:100, and
2:1234567890:203.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC4360: BGP Extended Communities Attribute. RFC5668: 4-Octet AS Specific BGP Extended Community.
Source ietf-routing-types line 210

route-target-type

Summary

Name route-target-type
Type enumeration
  
 
Indicates the role a route target takes
in route filtering.

Details

Module ietf-routing-types
Version 2017-02-19
Reference RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs).
Source ietf-routing-types line 262

route-target-type

Summary

Name route-target-type
Type enumeration
  
 
Indicates the role a route target takes
in route filtering.

Details

Module ietf-routing-types
Version 2017-10-13
Reference RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs).
Source ietf-routing-types line 237

route-target-type

Summary

Name route-target-type
Type enumeration
  
 
Indicates the role a route target takes
in route filtering.

Details

Module ietf-routing-types
Version 2017-02-27
Reference RFC4364: BGP/MPLS IP Virtual Private Networks (VPNs).
Source ietf-routing-types line 246

route-type

Summary

Name route-type
Type enumeration
  
 
OSPF route type.

Details

Module ietf-ospf
Version 2017-10-30
Source ietf-ospf line 476

route-type-def

Summary

Name route-type-def
Type identityref
  
 
Route type def.

Details

Module ietf-i2rs-rib
Version 2017-12-05
Source ietf-i2rs-rib line 427

router-id

Summary

Name router-id
Type union
  
 
OSPF/BGP router id or ISIS system ID.

Details

Module ietf-segment-routing
Version 2017-07-01
Source ietf-segment-routing line 168

routing-instance-ref

Summary

Name routing-instance-ref
Type leafref
  
 
This type is used for leafs that reference a routing instance
   configuration.

Details

Module ietf-arp
Version 2017-10-18
Source ietf-arp line 132

routing-instance-ref

Summary

Name routing-instance-ref
Type leafref
  
 
This type is used for leafs that reference a routing instance
configuration.

Details

Module ietf-connectionless-oam
Version 2017-09-06
Source ietf-connectionless-oam line 127

routing-password

Summary

Name routing-password
Type string
  
 
This type is indicative of a password that is used within
a routing protocol which can be returned in plain text to the
NMS by the local system. Such passwords are typically stored
as encrypted strings. Since the encryption used is generally
well known, it is possible to extract the original value from
the string - and hence this format is not considered secure.
Leaves specified with this type should not be modified by
the system, and should be returned to the end-user in plain
text. This type exists to differentiate passwords, which
may be sensitive, from other string leaves. It could, for
example, be used by the NMS to censor this data when
viewed by particular users.

Details

Module openconfig-types
Version 2017-08-16
Source openconfig-types line 98

RowStatus

Summary

Name RowStatus
Type enumeration
  
 
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row.
The status column has six defined values:

Whereas five of the six values (all except `notReady') may
be specified in a management protocol set operation, only
three values will be returned in response to a management
protocol retrieval operation:  `notReady', `notInService' or
`active'.  That is, when queried, an existing conceptual row
has only three states:  it is either available for use by
the managed device (the status column has value `active');
it is not available for use by the managed device, though
the agent has sufficient information to attempt to make it
so (the status column has value `notInService'); or, it is
not available for use by the managed device, and an attempt
to make it so would fail because the agent has insufficient
information (the state column has value `notReady').

Details

Module ietf-cfm
Version 2017-03-29
Source ietf-cfm line 348

RowStatus

Summary

Name RowStatus
Type enumeration
  
 
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of [2].)

The status column has six defined values:

     - `active', which indicates that the conceptual row is
     available for use by the managed device;

     - `notInService', which indicates that the conceptual
     row exists in the agent, but is unavailable for use by
     the managed device (see NOTE below); 'notInService' has
     no implication regarding the internal consistency of
     the row, availability of resources, or consistency with
     the current state of the managed device;

     - `notReady', which indicates that the conceptual row
     exists in the agent, but is missing information
     necessary in order to be available for use by the
     managed device (i.e., one or more required columns in
     the conceptual row have not been instanciated);

     - `createAndGo', which is supplied by a management
     station wishing to create a new instance of a
     conceptual row and to have its status automatically set
     to active, making it available for use by the managed
     device;

     - `createAndWait', which is supplied by a management
     station wishing to create a new instance of a
     conceptual row (but not make it available for use by
     the managed device); and,
     - `destroy', which is supplied by a management station
     wishing to delete all of the instances associated with
     an existing conceptual row.

Whereas five of the six values (all except `notReady') may
be specified in a management protocol set operation, only
three values will be returned in response to a management
protocol retrieval operation:  `notReady', `notInService' or
`active'.  That is, when queried, an existing conceptual row
has only three states:  it is either available for use by
the managed device (the status column has value `active');
it is not available for use by the managed device, though
the agent has sufficient information to attempt to make it
so (the status column has value `notInService'); or, it is
not available for use by the managed device, and an attempt
to make it so would fail because the agent has insufficient
information (the state column has value `notReady').

			 NOTE WELL

     This textual convention may be used for a MIB table,
     irrespective of whether the values of that table's
     conceptual rows are able to be modified while it is
     active, or whether its conceptual rows must be taken
     out of service in order to be modified.  That is, it is
     the responsibility of the DESCRIPTION clause of the
     status column to specify whether the status column must
     not be `active' in order for the value of some other
     column of the same conceptual row to be modified.  If
     such a specification is made, affected columns may be
     changed by an SNMP set PDU if the RowStatus would not
     be equal to `active' either immediately before or after
     processing the PDU.  In other words, if the PDU also
     contained a varbind that would change the RowStatus
     value, the column in question may be changed if the
     RowStatus was not equal to `active' as the PDU was
     received, or if the varbind sets the status to a value
     other than 'active'.

Also note that whenever any elements of a row exist, the
RowStatus column must also exist.

To summarize the effect of having a conceptual row with a
status column having a SYNTAX clause value of RowStatus,
consider the following state diagram:

			     STATE
  +--------------+-----------+-------------+-------------
  |      A       |     B     |      C      |      D
  |              |status col.|status column|
  |status column |    is     |      is     |status column
ACTION    |does not exist|  notReady | notInService|  is active
--------------+--------------+-----------+-------------+-------------
set status    |noError    ->D|inconsist- |inconsistent-|inconsistent-
column to     |       or     |   entValue|        Value|        Value
createAndGo   |inconsistent- |           |             |
  |         Value|           |             |
--------------+--------------+-----------+-------------+-------------
set status    |noError  see 1|inconsist- |inconsistent-|inconsistent-
column to     |       or     |   entValue|        Value|        Value
createAndWait |wrongValue    |           |             |
--------------+--------------+-----------+-------------+-------------
set status    |inconsistent- |inconsist- |noError      |noError
column to     |         Value|   entValue|             |
active        |              |           |             |
  |              |     or    |             |
  |              |           |             |
  |              |see 2   ->D|see 8     ->D|          ->D
--------------+--------------+-----------+-------------+-------------
set status    |inconsistent- |inconsist- |noError      |noError   ->C
column to     |         Value|   entValue|             |
notInService  |              |           |             |
  |              |     or    |             |      or
  |              |           |             |
  |              |see 3   ->C|          ->C|see 6
--------------+--------------+-----------+-------------+-------------
set status    |noError       |noError    |noError      |noError   ->A
column to     |              |           |             |      or
destroy       |           ->A|        ->A|          ->A|see 7
--------------+--------------+-----------+-------------+-------------
set any other |see 4         |noError    |noError      |see 5
column to some|              |           |             |
value         |              |      see 1|          ->C|          ->D
--------------+--------------+-----------+-------------+-------------

(1) goto B or C, depending on information available to the
agent.

(2) if other variable bindings included in the same PDU,
provide values for all columns which are missing but
required, and all columns have acceptable values, then
return noError and goto D.

(3) if other variable bindings included in the same PDU,
provide legal values for all columns which are missing but
required, then return noError and goto C.

(4) at the discretion of the agent, the return value may be
either:

     inconsistentName:  because the agent does not choose to
     create such an instance when the corresponding
     RowStatus instance does not exist, or

     inconsistentValue:  if the supplied value is
     inconsistent with the state of some other MIB object's
     value, or

     noError: because the agent chooses to create the
     instance.

If noError is returned, then the instance of the status
column must also be created, and the new state is B or C,
depending on the information available to the agent.  If
inconsistentName or inconsistentValue is returned, the row
remains in state A.

(5) depending on the MIB definition for the column/table,
either noError or inconsistentValue may be returned.

(6) the return value can indicate one of the following
errors:

     wrongValue: because the agent does not support
     notInService (e.g., an agent which does not support
     createAndWait), or

     inconsistentValue: because the agent is unable to take
     the row out of service at this time, perhaps because it
     is in use and cannot be de-activated.

(7) the return value can indicate the following error:

     inconsistentValue: because the agent is unable to
     remove the row at this time, perhaps because it is in
     use and cannot be de-activated.

(8) the transition to D can fail, e.g., if the values of the
conceptual row are inconsistent, then the error code would
be inconsistentValue.

NOTE: Other processing of (this and other varbinds of) the
set request may result in a response other than noError
being returned, e.g., wrongValue, noCreation, etc.

		  Conceptual Row Creation

There are four potential interactions when creating a
conceptual row:  selecting an instance-identifier which is
not in use; creating the conceptual row; initializing any
objects for which the agent does not supply a default; and,
making the conceptual row available for use by the managed
device.

Interaction 1: Selecting an Instance-Identifier

The algorithm used to select an instance-identifier varies
for each conceptual row.  In some cases, the instance-
identifier is semantically significant, e.g., the
destination address of a route, and a management station
selects the instance-identifier according to the semantics.

In other cases, the instance-identifier is used solely to
distinguish conceptual rows, and a management station
without specific knowledge of the conceptual row might
examine the instances present in order to determine an
unused instance-identifier.  (This approach may be used, but
it is often highly sub-optimal; however, it is also a
questionable practice for a naive management station to
attempt conceptual row creation.)

Alternately, the MIB module which defines the conceptual row
might provide one or more objects which provide assistance
in determining an unused instance-identifier.  For example,
if the conceptual row is indexed by an integer-value, then
an object having an integer-valued SYNTAX clause might be
defined for such a purpose, allowing a management station to
issue a management protocol retrieval operation.  In order
to avoid unnecessary collisions between competing management
stations, `adjacent' retrievals of this object should be
different.

Finally, the management station could select a pseudo-random
number to use as the index.  In the event that this index

was already in use and an inconsistentValue was returned in
response to the management protocol set operation, the
management station should simply select a new pseudo-random
number and retry the operation.

A MIB designer should choose between the two latter
algorithms based on the size of the table (and therefore the
efficiency of each algorithm).  For tables in which a large
number of entries are expected, it is recommended that a MIB
object be defined that returns an acceptable index for
creation.  For tables with small numbers of entries, it is
recommended that the latter pseudo-random index mechanism be
used.

Interaction 2: Creating the Conceptual Row

Once an unused instance-identifier has been selected, the
management station determines if it wishes to create and
activate the conceptual row in one transaction or in a
negotiated set of interactions.

Interaction 2a: Creating and Activating the Conceptual Row

The management station must first determine the column
requirements, i.e., it must determine those columns for
which it must or must not provide values.  Depending on the
complexity of the table and the management station's
knowledge of the agent's capabilities, this determination
can be made locally by the management station.  Alternately,
the management station issues a management protocol get
operation to examine all columns in the conceptual row that
it wishes to create.  In response, for each column, there
are three possible outcomes:

     - a value is returned, indicating that some other
     management station has already created this conceptual
     row.  We return to interaction 1.

     - the exception `noSuchInstance' is returned,
     indicating that the agent implements the object-type
     associated with this column, and that this column in at
     least one conceptual row would be accessible in the MIB
     view used by the retrieval were it to exist. For those
     columns to which the agent provides read-create access,
     the `noSuchInstance' exception tells the management
     station that it should supply a value for this column
     when the conceptual row is to be created.

     - the exception `noSuchObject' is returned, indicating
     that the agent does not implement the object-type
     associated with this column or that there is no
     conceptual row for which this column would be
     accessible in the MIB view used by the retrieval.  As
     such, the management station can not issue any
     management protocol set operations to create an
     instance of this column.

Once the column requirements have been determined, a
management protocol set operation is accordingly issued.
This operation also sets the new instance of the status
column to `createAndGo'.

When the agent processes the set operation, it verifies that
it has sufficient information to make the conceptual row
available for use by the managed device.  The information
available to the agent is provided by two sources:  the
management protocol set operation which creates the
conceptual row, and, implementation-specific defaults
supplied by the agent (note that an agent must provide
implementation-specific defaults for at least those objects
which it implements as read-only).  If there is sufficient
information available, then the conceptual row is created, a
`noError' response is returned, the status column is set to
`active', and no further interactions are necessary (i.e.,
interactions 3 and 4 are skipped).  If there is insufficient
information, then the conceptual row is not created, and the
set operation fails with an error of `inconsistentValue'.
On this error, the management station can issue a management
protocol retrieval operation to determine if this was
because it failed to specify a value for a required column,
or, because the selected instance of the status column
already existed.  In the latter case, we return to
interaction 1.  In the former case, the management station
can re-issue the set operation with the additional
information, or begin interaction 2 again using
`createAndWait' in order to negotiate creation of the
conceptual row.

			 NOTE WELL

     Regardless of the method used to determine the column
     requirements, it is possible that the management
     station might deem a column necessary when, in fact,
     the agent will not allow that particular columnar
     instance to be created or written.  In this case, the
     management protocol set operation will fail with an
     error such as `noCreation' or `notWritable'.  In this
     case, the management station decides whether it needs
     to be able to set a value for that particular columnar
     instance.  If not, the management station re-issues the
     management protocol set operation, but without setting
     a value for that particular columnar instance;
     otherwise, the management station aborts the row
     creation algorithm.

Interaction 2b: Negotiating the Creation of the Conceptual
Row

The management station issues a management protocol set
operation which sets the desired instance of the status
column to `createAndWait'.  If the agent is unwilling to
process a request of this sort, the set operation fails with
an error of `wrongValue'.  (As a consequence, such an agent
must be prepared to accept a single management protocol set
operation, i.e., interaction 2a above, containing all of the
columns indicated by its column requirements.)  Otherwise,
the conceptual row is created, a `noError' response is
returned, and the status column is immediately set to either
`notInService' or `notReady', depending on whether it has
sufficient information to (attempt to) make the conceptual
row available for use by the managed device.  If there is
sufficient information available, then the status column is
set to `notInService'; otherwise, if there is insufficient
information, then the status column is set to `notReady'.
Regardless, we proceed to interaction 3.

Interaction 3: Initializing non-defaulted Objects

The management station must now determine the column
requirements.  It issues a management protocol get operation
to examine all columns in the created conceptual row.  In
the response, for each column, there are three possible
outcomes:

     - a value is returned, indicating that the agent
     implements the object-type associated with this column
     and had sufficient information to provide a value.  For
     those columns to which the agent provides read-create
     access (and for which the agent allows their values to
     be changed after their creation), a value return tells
     the management station that it may issue additional
     management protocol set operations, if it desires, in
     order to change the value associated with this column.

     - the exception `noSuchInstance' is returned,
     indicating that the agent implements the object-type
     associated with this column, and that this column in at
     least one conceptual row would be accessible in the MIB
     view used by the retrieval were it to exist. However,
     the agent does not have sufficient information to
     provide a value, and until a value is provided, the
     conceptual row may not be made available for use by the
     managed device.  For those columns to which the agent
     provides read-create access, the `noSuchInstance'
     exception tells the management station that it must
     issue additional management protocol set operations, in
     order to provide a value associated with this column.

     - the exception `noSuchObject' is returned, indicating
     that the agent does not implement the object-type
     associated with this column or that there is no
     conceptual row for which this column would be
     accessible in the MIB view used by the retrieval.  As
     such, the management station can not issue any
     management protocol set operations to create an
     instance of this column.

If the value associated with the status column is
`notReady', then the management station must first deal with
all `noSuchInstance' columns, if any.  Having done so, the
value of the status column becomes `notInService', and we
proceed to interaction 4.

Interaction 4: Making the Conceptual Row Available

Once the management station is satisfied with the values
associated with the columns of the conceptual row, it issues
a management protocol set operation to set the status column
to `active'.  If the agent has sufficient information to
make the conceptual row available for use by the managed
device, the management protocol set operation succeeds (a
`noError' response is returned).  Otherwise, the management
protocol set operation fails with an error of
`inconsistentValue'.

			 NOTE WELL

     A conceptual row having a status column with value
     `notInService' or `notReady' is unavailable to the
     managed device.  As such, it is possible for the
     managed device to create its own instances during the
     time between the management protocol set operation
     which sets the status column to `createAndWait' and the
     management protocol set operation which sets the status
     column to `active'.  In this case, when the management
     protocol set operation is issued to set the status
     column to `active', the values held in the agent
     supersede those used by the managed device.

If the management station is prevented from setting the
status column to `active' (e.g., due to management station
or network failure) the conceptual row will be left in the
`notInService' or `notReady' state, consuming resources
indefinitely.  The agent must detect conceptual rows that
have been in either state for an abnormally long period of
time and remove them.  It is the responsibility of the
DESCRIPTION clause of the status column to indicate what an
abnormally long period of time would be.  This period of
time should be long enough to allow for human response time
(including `think time') between the creation of the
conceptual row and the setting of the status to `active'.
In the absence of such information in the DESCRIPTION
clause, it is suggested that this period be approximately 5
minutes in length.  This removal action applies not only to
newly-created rows, but also to previously active rows which
are set to, and left in, the notInService state for a
prolonged period exceeding that which is considered normal
for such a conceptual row.

		 Conceptual Row Suspension

When a conceptual row is `active', the management station
may issue a management protocol set operation which sets the
instance of the status column to `notInService'.  If the
agent is unwilling to do so, the set operation fails with an
error of `wrongValue' or `inconsistentValue'.  Otherwise,
the conceptual row is taken out of service, and a `noError'
response is returned.  It is the responsibility of the
DESCRIPTION clause of the status column to indicate under
what circumstances the status column should be taken out of
service (e.g., in order for the value of some other column
of the same conceptual row to be modified).

		  Conceptual Row Deletion

For deletion of conceptual rows, a management protocol set
operation is issued which sets the instance of the status
column to `destroy'.  This request may be made regardless of
the current value of the status column (e.g., it is possible
to delete conceptual rows which are either `notReady',
`notInService' or `active'.)  If the operation succeeds,
then all instances associated with the conceptual row are
immediately removed.

Details

Module SNMPv2-TC
Version none
Source SNMPv2-TC line 166

rp-event-type

Summary

Name rp-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-rp
Version 2017-02-19
Source ietf-pim-rp line 112

rp-event-type

Summary

Name rp-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-rp
Version 2017-03-09
Source ietf-pim-rp line 88

rp-event-type

Summary

Name rp-event-type
Type enumeration
  
 
Operational status event type for notifications.

Details

Module ietf-pim-rp
Version 2017-12-08
Source ietf-pim-rp line 110

rr-cluster-id-type

Summary

Name rr-cluster-id-type
Type union
  
 
union type for route reflector cluster ids:
option 1: 4-byte number
option 2: IP address

Details

Module ietf-bgp-types
Version 2017-10-17
Source ietf-bgp-types line 391

rr-cluster-id-type

Summary

Name rr-cluster-id-type
Type union
  
 
Union type for route reflector cluster ids:
option 1: 4-byte number
option 2: IP address

Details

Module openconfig-bgp-types
Version 2017-07-30
Source openconfig-bgp-types line 492

sadb-msg-satype

Summary

Name sadb-msg-satype
Type enumeration
  
 
PF_KEY Security Association types

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 748

sadb-msg-type

Summary

Name sadb-msg-type
Type enumeration
  
 
PF_KEY base message types

Details

Module ietf-ipsec
Version 2017-05-02
Source ietf-ipsec line 727

scaling-criteria-operation

Summary

Name scaling-criteria-operation
Type enumeration
  
 
Operations to analize list of scaling criterias

Details

Module ietf-te-kpi-telemetry
Version 2017-10-25
Source ietf-te-kpi-telemetry line 100

schedule-ref

Summary

Name schedule-ref
Type leafref
  
 
This type is used by data models that need to reference
a configured schedule.

Details

Module ietf-lmap-control
Version 2017-04-21
Source ietf-lmap-control line 65

schedule-ref

Summary

Name schedule-ref
Type leafref
  
 
This type is used by data models that need to reference
a configured Schedule.

Details

Module ietf-lmap-control
Version 2017-08-08
Source ietf-lmap-control line 66

schema-instance-identifier

Summary

Name schema-instance-identifier
Type string
  
 
Path expression used to represent a special
schema-instance identifier string.

A schema-instance-identifier value string is an
unrestricted YANG instance-identifier expression.
All the same rules as an instance-identifier apply
except predicates for keys are optional.  If a key
predicate is missing, then the schema-instance-identifier
represents all possible server instances for that key.

Details

Module yuma-nacm
Version 2012-10-05
Source yuma-nacm line 116

schema-node-path

Summary

Name schema-node-path
Type string
  
 
Identifies a schema-node path string for use in the
SID registry. This string format follows the rules
for an instance-identifier, as defined in RFC 7959,
except that no predicates are allowed.

This format is intended to support the YANG 1.1 ABNF
for a schema node identifier, except module names
are used instead of prefixes, as specified in RFC 7951.

Details

Module ietf-sid-file
Version 2017-11-26
Reference RFC 7950, The YANG 1.1 Data Modeling Language; Section 6.5: Schema Node Identifier; RFC 7951, JSON Encoding of YANG Data; Section 6.11: The instance-identifier type
Source ietf-sid-file line 48

sci-list-entry

Summary

Name sci-list-entry
Type string
  
 
8 octet string, where the first 6 octets represents the MAC
Address (in canonical format), and the next 2 octets represents
the Port Identifier.

Details

Module ieee802-dot1x
Version 2017-07-20
Reference IEEE 802.1AE Clause 7.1.2, Clause 10.7.1
Source ieee802-dot1x line 299

sec-event-format

Summary

Name sec-event-format
Type enumeration
  
 
This is used for SecEventFormat.

Details

Module ietf-i2nsf-nsf-facing-interface
Version 2017-10-30
Source ietf-i2nsf-nsf-facing-interface line 47

second

Summary

Name second
Type uint8
  
 
A second of a minute.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 281

second

Summary

Name second
Type uint8
  
 
A second of a minute.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 284

second-or-all

Summary

Name second-or-all
Type union
  
 
A second of a minute or a wildcard indicating all
seconds of a minute.

Details

Module ietf-lmap-common
Version 2017-04-21
Source ietf-lmap-common line 287

second-or-all

Summary

Name second-or-all
Type union
  
 
A second of a minute or a wildcard indicating all
seconds of a minute.

Details

Module ietf-lmap-common
Version 2017-08-08
Source ietf-lmap-common line 290

security-level

Summary

Name security-level
Type enumeration

Details

Module ietf-snmp
Submodule ietf-snmp-common
Version 2014-12-10
Reference RFC 3411: An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
Source ietf-snmp-common line 131

security-model

Summary

Name security-model
Type union

Details

Module ietf-snmp
Submodule ietf-snmp-common
Version 2014-12-10
Reference RFC 3411: An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
Source ietf-snmp-common line 102

security-model-or-any

Summary

Name security-model-or-any
Type union

Details

Module ietf-snmp
Submodule ietf-snmp-common
Version 2014-12-10
Reference RFC 3411: An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks
Source ietf-snmp-common line 119

selection-filter-ref

Summary

<
Name selection-filter-ref
Type leafref