netconfcentral logo

Typedefs

abs-traffic-class-plus-one-type

Summary

Name abs-traffic-class-plus-one-type
Type enumeration
  
 
Specifies a value that can be translated to the numeric value
of the traffic class to be used as either the congesting or
monitored queue. The absolute value of the enumerated value is
the value of the taffic class plus 1. A value of 0 indicates the
traffic class is not participating in congestion isolation. For
example, the enumerated value congesting-queue-tc-5 specifies
that traffic class 4 is used as the congesting queue.

Details

Module ieee802-dot1q-congestion-isolation
Version 2020-08-10
Source ieee802-dot1q-congestion-isolation line 61

access-control-mode

Summary

Name access-control-mode
Type enumeration

Details

Module yumaworks-types
Version 2020-03-06
Source yumaworks-types line 221

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 111

access-operations-type

Summary

Name access-operations-type
Type bits
  
 
Access operation.

Details

Module ietf-netconf-acm
Version 2018-02-14
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-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 ACL type.

Details

Module ietf-access-control-list
Version 2019-03-04
Source ietf-access-control-list line 301

action-scope

Summary

Name action-scope
Type identityref
  
 
The scope of the action.

Details

Module bbf-qos-classifiers
Version 2018-07-13
Source bbf-qos-classifiers line 207

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 151

action-type

Summary

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

Details

Module ietf-netconf-acm
Version 2018-02-14
Source ietf-netconf-acm line 159

action-type

Summary

Name action-type
Type enumeration
  
 
Definition for action type.

Details

Module ietf-flowspec
Version 2015-09-15
Source ietf-flowspec line 118

activate-notification-type

Summary

Name activate-notification-type
Type enumeration
  
 
Type of notification on software or database activation events

Details

Module org-openroadm-common-types
Version 2020-05-29
Source org-openroadm-common-types line 91

activation-type

Summary

Name activation-type
Type enumeration
  
 
Indicates the activation type of an ACL.

Details

Module ietf-dots-data-channel
Version 2020-05-28
Source ietf-dots-data-channel line 79

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 2020-06-30
Source openconfig-isis-types line 199

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 95

address-attribute-type

Summary

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

Details

Module ietf-connectionless-oam
Version 2019-04-16
Source ietf-connectionless-oam line 139

address-family

Summary

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

Details

Module ietf-sdwan-svc
Version 2019-06-06
Source ietf-sdwan-svc line 34

address-family

Summary

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

Details

Module ietf-l3vpn-svc
Version 2018-01-19
Source ietf-l3vpn-svc line 153

address-family

Summary

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

Details

Module iana-routing-types
Version 2017-12-04
Source iana-routing-types line 45

address-family

Summary

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

Details

Module iana-routing-types
Version 2018-10-29
Source iana-routing-types line 52

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-definition

Summary

Name address-family-definition
Type identityref
  
 
RIB address family definition.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 402

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

address-set-name

Summary

Name address-set-name
Type string
  
 
This type represents an address object or an address group name.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 54

admin-groups

Summary

Name admin-groups
Type union
  
 
Derived types for TE administrative groups.

Details

Module ietf-te-types
Version 2020-06-10
Source ietf-te-types line 98

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
  
 
Represents the various possible administrative states.

Details

Module ietf-hardware
Version 2018-03-13
Reference RFC 4268: Entity State MIB - EntityAdminState
Source ietf-hardware line 91

admin-state

Summary

Name admin-state
Type enumeration
  
 
Admin state of the OAM function on an interface.

Details

Module ieee802-ethernet-link-oam
Version 2019-06-21
Reference IEEE Std 802.3, 30.3.6.1.2 and 30.3.6.2
Source ieee802-ethernet-link-oam line 309

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 2020-08-12
Source openconfig-transport-types line 102

admin-states

Summary

Name admin-states
Type enumeration

Details

Module org-openroadm-equipment-states-types
Version 2019-11-29
Source org-openroadm-equipment-states-types line 59

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

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 2018-05-17
Source ietf-pmip-qos line 235

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 2018-05-17
Source ietf-pmip-qos line 243

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 2020-05-01
Source openconfig-if-aggregate line 99

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 2018-03-13
Reference RFC 4268: Entity State MIB - EntityAlarmStatus
Source ietf-hardware line 184

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 2019-09-11
Source ietf-alarms line 333

alarm-type-id

Summary

Name alarm-type-id
Type identityref
  
 
Identifies an alarm type.  The description of the alarm type
id MUST indicate whether or not the alarm type is abstract.
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 2019-09-11
Source ietf-alarms line 475

alarm-type-qualifier

Summary

Name alarm-type-qualifier
Type string
  
 
If an alarm type cannot 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 to be part of
the instrumentation and is out of scope for this module.  An
empty string is used when this is part of a key.

Details

Module ietf-alarms
Version 2019-09-11
Source ietf-alarms line 487

alps-connection-direction-type

Summary

Name alps-connection-direction-type
Type string
  
 
connection direction type

Details

Module alps
Version none
Source alps line 31

alps-demand-group-oper-type

Summary

Name alps-demand-group-oper-type
Type string
  
 
demand group operation type

Details

Module alps
Version none
Source alps line 16

alps-demand-type

Summary

Name alps-demand-type
Type string
  
 
demand type

Details

Module alps
Version none
Source alps line 11

alps-endpoint-group-type

Summary

Name alps-endpoint-group-type
Type string
  
 
endpoint group type

Details

Module alps
Version none
Source alps line 26

alps-endpoint-type

Summary

Name alps-endpoint-type
Type string
  
 
endpoint type

Details

Module alps
Version none
Source alps line 21

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 2020-03-06
Source yumaworks-types line 111

amplifier-gain-range

Summary

Name amplifier-gain-range
Type enumeration
  
 
Operational mode for the amplifier:
this parameter allows modeling different operational modes (gain ranges) ,notably for switched-gain amplifiers.
It indicates which performance model shall be used by the path feasibility engine.
For standard amplifier, or when performance evaluation is based on incremental noise, use gain-range-1.
When performance evaluation is based on advanced parameters, specify used gain-range (1 to 4).
Up to release 2.1, only gain-range-1 is to be used (default value) 

Details

Module org-openroadm-common-amplifier-types
Version 2019-11-29
Source org-openroadm-common-amplifier-types line 76

amplifier-types

Summary

Name amplifier-types
Type enumeration
  
 
identifier for amplifier type
1. standard for amplifier as defined initially in the ROADM MSA specifications
To be completed if/when additional amplifier types are required 

Details

Module org-openroadm-common-amplifier-types
Version 2019-11-29
Source org-openroadm-common-amplifier-types line 51

angle

Summary

Name angle
Type decimal64
  
 
The angle in degress.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 1183

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 2020-06-30
Source openconfig-isis-types line 323

area-id-type

Summary

Name area-id-type
Type union
  
 
Area ID type.

Details

Module org-openroadm-ospf
Version 2020-05-29
Source org-openroadm-ospf line 280

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 2020-06-30
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 337

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 137

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-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 216

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 2020-06-30
Source openconfig-bgp-types line 716

asymmetric-key-ref

Summary

Name asymmetric-key-ref
Type leafref
  
 
This typedef enables modules to easily define a reference
to an asymmetric key stored in the Keystore.

Details

Module ietf-keystore
Version 2020-08-20
Source ietf-keystore line 87

attack-status

Summary

Name attack-status
Type enumeration
  
 
Enumeration for attack status codes.

Details

Module iana-dots-signal-channel
Version 2020-05-28
Source iana-dots-signal-channel line 158

auth-method-type

Summary

Name auth-method-type
Type enumeration
  
 
Method for authenticating an ONU.

Details

Module bbf-xpon-types
Version 2019-02-25
Source bbf-xpon-types line 332

authen-mode

Summary

Name authen-mode
Type enumeration
  
 
TRILL authentication mode.

Details

Module ietf-trill
Version 2015-12-21
Source ietf-trill line 86

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 2020-06-30
Source openconfig-openflow-types line 86

availability-status

Summary

Name availability-status
Type bits
  
 
A set of availability status conditions.  An empty set of
bits implies that none of the status conditions are
present, i.e., the entity is available.

Details

Module bbf-availability
Version 2018-07-13
Reference ITU-T X.731 clause 8.1.2.3.
Source bbf-availability line 135

band

Summary

Name band
Type enumeration
  
 
Represents the available upstream and downstream bands.

Details

Module bbf-vdsl
Submodule bbf-vdsl-base-body
Version 2019-10-21
Source bbf-vdsl-base-body line 886

bandplan

Summary

Name bandplan
Type enumeration
  
 
Valid bandplan definitions.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9960 clause 6
Source bbf-ghn-types line 200

bandwidth

Summary

Name bandwidth
Type identityref
  
 
Bandwidth of the port.

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 250

bandwidth

Summary

Name bandwidth
Type decimal64
  
 
Bandwidth in bits per second of a communcation channel.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 598

bandwidth

Summary

Name bandwidth
Type identityref
  
 
Bandwidth of the port.

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 211

bandwidth-gbps

Summary

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

Details

Module ietf-te-packet-types
Version 2020-06-10
Source ietf-te-packet-types line 119

bandwidth-gbps

Summary

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

Details

Module openconfig-mpls-types
Version 2020-02-04
Source openconfig-mpls-types line 439

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-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 ISO/IEC 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 a power of two.  Some examples are 0x0p0, 0x1p10,
and 0x1.abcde2p+20.

Details

Module ietf-routing-types
Version 2017-12-04
Reference IEEE Std 754-2008: IEEE Standard for Floating-Point Arithmetic. ISO/IEC C99: Information technology - Programming Languages - C.
Source ietf-routing-types line 491

bandwidth-kbps

Summary

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

Details

Module ietf-te-packet-types
Version 2020-06-10
Source ietf-te-packet-types line 105

bandwidth-kbps

Summary

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

Details

Module openconfig-mpls-types
Version 2020-02-04
Source openconfig-mpls-types line 425

bandwidth-mbps

Summary

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

Details

Module ietf-te-packet-types
Version 2020-06-10
Source ietf-te-packet-types line 112

bandwidth-mbps

Summary

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

Details

Module openconfig-mpls-types
Version 2020-02-04
Source openconfig-mpls-types line 432

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 2019-11-19
Source openconfig-interfaces line 138

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

bc-type

Summary

Name bc-type
Type uint8
  
 
Diffserv-TE bandwidth constraints as defined in RFC 4124.

Details

Module ietf-te-packet-types
Version 2020-06-10
Reference RFC 4124: Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering
Source ietf-te-packet-types line 94

bgp-as-path-prepend-repeat

Summary

Name bgp-as-path-prepend-repeat
Type uint8
  
 
Option for the BGP as-prepend policy action.  Prepends the
local AS number repeated n times

Details

Module bgp-policy
Version 2015-05-15
Source bgp-policy line 43

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 2020-06-30
Reference RFC 4360 - BGP Extended Communities Attribute RFC 5668 - 4-Octet AS Specific BGP Extended Community
Source openconfig-bgp-types line 572

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
 - color:<CO bits>:<4b value> per draft-ietf-idr-segment-routing-te-policy
   section 3

Details

Module openconfig-bgp-types
Version 2020-06-30
Reference RFC 4360 - BGP Extended Communities Attribute RFC 5668 - 4-Octet AS Specific BGP Extended Community draft-ietf-idr-segment-routing-te-policy
Source openconfig-bgp-types line 389

bgp-next-hop-type

Summary

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

Details

Module bgp-policy
Version 2015-05-15
Source bgp-policy line 75

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 2020-06-30
Reference RFC 4271 - A Border Gateway Protocol 4 (BGP-4), Sec 4.3
Source openconfig-bgp-types line 611

bgp-safi

Summary

Name bgp-safi
Type enumeration
  
 
Enumeration for BGP SAFI.

Details

Module iana-routing-types
Version 2017-12-04
Reference RFC 4760: Multiprotocol Extensions for BGP-4.
Source iana-routing-types line 326

bgp-safi

Summary

Name bgp-safi
Type enumeration
  
 
Enumeration for BGP SAFI.

Details

Module iana-routing-types
Version 2018-10-29
Reference RFC 4760: Multiprotocol Extensions for BGP-4.
Source iana-routing-types line 346

bgp-session-direction

Summary

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

Details

Module openconfig-bgp-types
Version 2020-06-30
Source openconfig-bgp-types line 334

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 bgp-policy
Version 2015-05-15
Source bgp-policy line 50

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 bgp-policy
Version 2015-05-15
Source bgp-policy line 89

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 2020-06-30
Reference RFC 1997 - BGP Communities Attribute
Source openconfig-bgp-types line 361

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 2020-06-30
Reference IANA Border Gateway Protocol (BGP) Well Known Communities
Source openconfig-bgp-types line 349

bpc

Summary

Name bpc
Type binary
  
 
A binary type where each octet represents data belonging to
a sub-carrier group. The first octet represents sub-carrier
group 0.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Source bbf-ghn-types line 148

bridge-id-type

Summary

Name bridge-id-type
Type string
  
 
Unique Bridge Identifier

Details

Module org-openroadm-rstp
Version 2020-05-29
Source org-openroadm-rstp line 109

bridge-port-number

Summary

Name bridge-port-number
Type leafref
  
 
An integer that uniquely identifies a Bridge Port.

Details

Module ietf-gptp
Version 2018-03-28
Source ietf-gptp line 154

bridge-ref

Summary

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

Details

Module ieee802-dot1ab-lldp
Version 2018-11-11
Source ieee802-dot1ab-lldp line 60

broadband-line-characteristics

Summary

Name broadband-line-characteristics
Type bits
  
 
The type defined for the broadband line characteristics
listed in TR-101i2.

Details

Module bbf-subscriber-types
Version 2017-05-08
Reference TR-101i2 - R158
Source bbf-subscriber-types line 92

burst-size

Summary

Name burst-size
Type uint32
  
 
Burst size in bytes.

Details

Module bbf-qos-policing-types
Version 2018-07-13
Source bbf-qos-policing-types line 98

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

carrier-form

Summary

Name carrier-form
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 264

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

ccm-interval-type

Summary

Name ccm-interval-type
Type enumeration
  
 
Indicates the interval at which CCM PDUs are sent by a MEP.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 373

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-ntw
Version 2020-05-26
Source ietf-l2vpn-ntw line 321

ccm-priority-type

Summary

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

Details

Module ietf-l2vpn-svc
Version 2018-04-03
Source ietf-l2vpn-svc line 220

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 2018-10-09
Source ietf-l2vpn-svc line 228

centiseconds

Summary

Name centiseconds
Type uint32
  
 
A period of time, measured in units of 0.01 seconds.

Details

Module ietf-yang-push
Version 2019-09-09
Source ietf-yang-push line 239

certificate-id-type

Summary

Name certificate-id-type
Type string
  
 
The certificate id must starts with a letter and
end with a letter or digit. Interior characters are only
alphabets, digits, minus, underscore and dot.

Details

Module org-openroadm-security
Version 2020-05-29
Source org-openroadm-security line 73

change-type

Summary

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

This type is based on the edit operations defined for
YANG Patch, with the difference that it is valid for a
receiver to process an update record that performs a
'create' operation on a datastore node the receiver believes
exists or to process a delete on a datastore node the
receiver believes is missing.

Details

Module ietf-yang-push
Version 2019-09-09
Reference RFC 8072: YANG Patch Media Type, Section 2.5
Source ietf-yang-push line 190

channel-estimation-profile-ref

Summary

Name channel-estimation-profile-ref
Type leafref
  
 
Used to reference a channel estimation profile.

Details

Module bbf-ghn
Submodule bbf-ghn-link-profiles
Version 2018-07-13
Source bbf-ghn-link-profiles line 99

channel-threshold-profile-ref

Summary

Name channel-threshold-profile-ref
Type leafref
  
 
xDSL Transceiver Unit (xTU) Channel Threshold Profile name.

Details

Module bbf-vdsl
Submodule bbf-vdsl-threshold-management
Version 2019-10-21
Source bbf-vdsl-threshold-management line 138

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 2020-05-19
Source openconfig-wifi-types line 46

chassis-id-subtype-type

Summary

Name chassis-id-subtype-type
Type enumeration
  
 
The source of a chassis identifier.

Details

Module ieee802-dot1ab-types
Version 2018-10-02
Reference LLDP MIB 20050506
Source ieee802-dot1ab-types line 36

chassis-id-subtype-type

Summary

Name chassis-id-subtype-type
Type enumeration
  
 
The source of a chassis identifier.

Details

Module ieee802-types
Version 2018-03-07
Reference LLDP MIB 20050506
Source ieee802-types line 43

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 2018-11-21
Reference IEEE 802.1AB LLDP MIB
Source openconfig-lldp-types line 207

chassis-id-type

Summary

Name chassis-id-type
Type string
  
 
The format of a chassis identifier string. Objects of this type
are always used with an associated lldp-chassis-is-subtype
object, which identifies the format of the particular
lldp-chassis-id object instance.

If the associated lldp-chassis-id-subtype object has a value of
chassis-component, 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 lldp-chassis-id-subtype object has a value
of interface-alias, 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 lldp-chassis-id-subtype object has a value
of port-component, 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 lldp-chassis-id-subtype object has a value of
mac-address, 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 lldp-chassis-id-subtype object has a value of
network-address, 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 lldp-chassis-id-subtype object has a value
of interface-name, 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 lldp-chassis-id-subtype object has a value of
local, then this string identifies a locally assigned
Chassis ID.

Details

Module ieee802-dot1ab-types
Version 2018-10-02
Reference LLDP MIB 20050506
Source ieee802-dot1ab-types line 99

chassis-id-type

Summary

Name chassis-id-type
Type string
  
 
The format of a chassis identifier string. Objects of this type
are always used with an associated lldp-chassis-is-subtype
object, which identifies the format of the particular
lldp-chassis-id object instance.

If the associated lldp-chassis-id-subtype object has a value of
chassis-component, 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 lldp-chassis-id-subtype object has a value
of interface-alias, 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 lldp-chassis-id-subtype object has a value
of port-component, 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 lldp-chassis-id-subtype object has a value of
mac-address, 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 lldp-chassis-id-subtype object has a value of
network-address, 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 lldp-chassis-id-subtype object has a value
of interface-name, 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 lldp-chassis-id-subtype object has a value of
local, then this string identifies a locally assigned
Chassis ID.

Details

Module ieee802-types
Version 2018-03-07
Reference LLDP MIB 20050506
Source ieee802-types line 106

child-node-name

Summary

Name child-node-name
Type string
  
 
Identifies a child node string for use in the
YANG mapping. There are two allowed formats:

module-name:child-name -- used only for a child node
from a different module namespace than the parent node.

child-name -- used only for a child node from the
same module namespace as the parent node.

Details

Module yumaworks-yangmap
Version 2018-01-04
Source yumaworks-yangmap line 141

circuit-type

Summary

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

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 231

classmask-descriptor

Summary

Name classmask-descriptor
Type enumeration
  
 
One CLASSMASK parameter is defined per the G.993.2 Annex
enabled in the xDSL Transmission System Enabling (XTSE). It
selects a single Power Spectral Density (PSD) mask class
per the G.993.2 Annex that is activated at the VTU-O.
The coding is as indicated in Table 7-6 of [ITU-T G.997.1].

Details

Module bbf-vdsl
Submodule bbf-vdsl-base-body
Version 2019-10-21
Reference ITU-T G.997.1 clause 7.3.1.2.15 VDSL2 PSD mask class selection (CLASSMASK)
Source bbf-vdsl-base-body line 753

client-status-enumeration

Summary

Name client-status-enumeration
Type enumeration
  
 
The client status. RPF, LPF and OK are defined.

Details

Module ietf-flexe
Version 2019-10-30
Reference OIF Flex 2.0: Section 7.3.8
Source ietf-flexe line 156

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
Version 2019-05-07
Reference IEEE Std 1588-2008: 5.3.4
Source ietf-ptp line 128

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
  
 
Represents an IEEE 802.1 MAC address represented in the
'canonical' order defined by IEEE 802.1a, EUI-64. EUI-48
converts to EUI-64 as specified by IEEE. The conversion
assigns values 255 and 254 to octets 3 and 4, respectively,
where octet 0 is the most significant and octet 7 the least.
For example, EUI-48 of AC:DE:48:23:45:67 would extend to
AC:DE:48:FF:FE:23:45:67.

Details

Module ietf-gptp
Version 2018-03-28
Source ietf-gptp line 28

cms

Summary

Name cms
Type binary
  
 
A CMS structure, as specified in RFC 5652, encoded using
ASN.1 distinguished encoding rules (DER), as specified in
ITU-T X.690.

Details

Module ietf-sztp-bootstrap-server
Version 2019-04-30
Reference RFC 5652: Cryptographic Message Syntax (CMS) 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-sztp-bootstrap-server line 57

cms

Summary

Name cms
Type binary
  
 
A ContentInfo structure, as specified in RFC 5652,
encoded using ASN.1 distinguished encoding rules (DER),
as specified in ITU-T X.690.

Details

Module ietf-zerotouch-information
Version 2018-12-20
Reference RFC 5652: Cryptographic Message Syntax (CMS) 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-information line 72

color-mode

Summary

Name color-mode
Type enumeration
  
 
The Color Mode (CM) indicates the type of color awareness which
is employed by the Policer.

Details

Module bbf-qos-policing-types
Version 2018-07-13
Reference MEF 10.3, Section 12.1
Source bbf-qos-policing-types line 127

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 2020-06-30
Source openconfig-bgp-types line 693

complex-admittance

Summary

Name complex-admittance
Type uint32
  
 
The range of valid values for the 3-element complex
conductances and susceptances, GTR and BTR (Tip-to-Ring);
GTG and BTG (Tip-to-Ground); and GRG and BRG (Ring-to-Ground)
is from 0.1 uSiemens to 0.1 Siemens. The values shall be
represented in linear format with a granularity of 0.1
uSiemens.

NOTE - The linear format is chosen for simplicity reason and
does not imply any future accuracy requirements.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.9 (MELT-CAG-TR, MELT-CAB-TR, MELT-CAG-TG, MELT-CAB-TG, MELT-CAG-RG, MELT-CAB-RG)
Source bbf-melt-pmd-measurement-parameter-body line 366

component-enum

Summary

Name component-enum
Type enumeration
  
 
Definition for component type.

Details

Module ietf-flowspec
Version 2015-09-15
Source ietf-flowspec line 51

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 2019-06-03
Source openconfig-platform-types line 331

composite-channel-id-type

Summary

Name composite-channel-id-type
Type union
  
 
A composite type strictly meant for leaves reflecting the
already allocated downstream or upstream channel-id on a
channel-group.
Such leaves are used to prevent conflicts when allocating
a channel-pair to a channel-group. For NG-PON2, the applicable
values are in [0..7], for XGS-PON a dedicated value 'xgs'
is used rather than '0' to prevent ambiguity between this and
the valid value '0' for NG-PON2.

Details

Module bbf-xpon-types
Version 2019-02-25
Source bbf-xpon-types line 277

composite-downstream-wavelength-type

Summary

Name composite-downstream-wavelength-type
Type union
  
 
A composite type strictly meant for leaves reflecting the
already allocated downstream or upstream channel-id on a
channel-group.
Such leaves are used to prevent conflicts when allocating a
channel-pair to a channel-group. For NG-PON2, the applicable
values are in [0..8], for XGS-PON a dedicated value 'xgs'
is applicable rather than value '0': this is not to a priori
forbid in yang model the coexistence of XGS-PON with NG-PON2
using channel-id=0.

Details

Module bbf-xpon-types
Version 2019-02-25
Source bbf-xpon-types line 300

confidentiality-offset

Summary

Name confidentiality-offset
Type enumeration
  
 
The confidentiality offset specifies a number of octets in an Ethernet
frame that are sent in unencrypted plain-text

Details

Module openconfig-macsec-types
Version 2019-07-01
Source openconfig-macsec-types line 39

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 2019-12-07
Source yangcli-pro line 506

config-error-type

Summary

Name config-error-type
Type bits
  
 
While making the MIP creation evaluation described in
22.2.3, the management entity can encounter errors in
the configuration.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 614

ConfirmTimeoutType

Summary

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

Details

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

conflict-cause

Summary

Name conflict-cause
Type enumeration
  
 
Enumeration for conflict causes.

Details

Module iana-dots-signal-channel
Version 2020-05-28
Source iana-dots-signal-channel line 129

conflict-state

Summary

Name conflict-state
Type enumeration
  
 
Nickname conflict state.

Details

Module ietf-trill
Version 2015-12-21
Source ietf-trill line 145

conflict-status

Summary

Name conflict-status
Type enumeration
  
 
Enumeration for conflict status.

Details

Module iana-dots-signal-channel
Version 2020-05-28
Source iana-dots-signal-channel line 99

connection-type

Summary

Name connection-type
Type enumeration

Details

Module org-openroadm-common-service-types
Version 2020-05-29
Source org-openroadm-common-service-types line 313

context-metadata-ref

Summary

Name context-metadata-ref
Type leafref
  
 
This type is used by data models that need to reference
configured context metadata headers.

Details

Module service-function-path-metadata
Version 2014-07-01
Source service-function-path-metadata line 23

control-mode

Summary

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

Details

Module ietf-l2vpn-ntw
Version 2020-05-26
Source ietf-l2vpn-ntw line 330

control-mode

Summary

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

Details

Module ietf-l2vpn-svc
Version 2018-04-03
Source ietf-l2vpn-svc line 229

control-mode

Summary

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

Details

Module ietf-l2vpn-svc
Version 2018-10-09
Source ietf-l2vpn-svc line 237

coordinate-length

Summary

Name coordinate-length
Type decimal64
  
 
The position along a single coordinate.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 622

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 2020-06-30
Source openconfig-yang-types line 102

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

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

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 2020-06-30
Source openconfig-yang-types line 115

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

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

coupling-flag

Summary

Name coupling-flag
Type uint8
  
 
The Coupling Flag (CF) allows the choice between two modes of
operation of the rate enforcement algorithm.

When CF is set to 0, the long term average rate of Service
Frames that are declared Yellow is bound by EIR.

When CF is set to 1, the long term average rate of Service
Frames that are declared Yellow is bound by CIR+EIR depending
on the volume of offered Service Frames which are declared
Green.

In both cases, the burst size of Service Frames which are
declared Yellow is bound by EBS.

Details

Module bbf-qos-policing-types
Version 2018-07-13
Reference MEF 10.3
Source bbf-qos-policing-types line 105

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-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-04-04
Reference IEEE Std 1003.1-2008 - crypt() function RFC 1321: The MD5 Message-Digest Algorithm FIPS.180-3.2008: Secure Hash Standard
Source iana-crypt-hash line 50

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 2018-11-21
Source openconfig-aaa-types line 149

cryptographic-algorithm-type

Summary

Name cryptographic-algorithm-type
Type identityref
  
 
This type identifies the cryptographic algorithm

Details

Module ietf-key-table
Version 2015-08-28
Source ietf-key-table line 118

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

cw-negotiation-type

Summary

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

Details

Module ietf-pseudowires
Version 2018-10-22
Source ietf-pseudowires line 47

cycle-duration

Summary

Name cycle-duration
Type union
  
 
Duration in ms of the MAC cycle.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.2.2
Source bbf-ghn-types line 87

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

data-rate

Summary

Name data-rate
Type uint32
  
 
Data rate in kbps.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Source bbf-ghn-types line 453

data-rate32

Summary

Name data-rate32
Type uint32
  
 
A type which represents the rate at which data is being
transferred.

Details

Module bbf-yang-types
Version 2019-10-21
Source bbf-yang-types line 227

data-rate32-or-undetermined

Summary

Name data-rate32-or-undetermined
Type union
  
 
A type which represents the rate at which data is being
transferred. A special value, 'undetermined', is used to
indicate the data rate is undetermined.

Details

Module bbf-yang-types
Version 2019-10-21
Source bbf-yang-types line 235

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 2020-06-30
Source openconfig-openflow-types line 98

datastore-ref

Summary

Name datastore-ref
Type identityref
  
 
A datastore identity reference.

Details

Module ietf-datastores
Version 2018-02-14
Source ietf-datastores line 110

date

Summary

Name date
Type string
  
 
A full UTC date, expressed in the format described in RFC3339.
That is to say:

YYYY-MM-DD

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.

Details

Module openconfig-yang-types
Version 2020-06-30
Reference RFC3339 - Date and Time on the Internet: full-date
Source openconfig-yang-types line 160

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

Summary

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

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 332

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 2020-06-30
Reference RFC3339 - Date and Time on the Internet: Timestamps
Source openconfig-yang-types line 127

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 300

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 262

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

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 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

dba-profile-ref

Summary

Name dba-profile-ref
Type leafref
  
 
Used to reference a DBA profile.

Details

Module bbf-ghn
Submodule bbf-ghn-domain-profiles
Version 2018-07-13
Source bbf-ghn-domain-profiles line 108

dbm-t

Summary

Name dbm-t
Type decimal64
  
 
Amplifier Power in dBm

Details

Module draft-ietf-ccamp-dwdm-if-param-yang-02
Version 2019-11-04
Source draft-ietf-ccamp-dwdm-if-param-yang-02 line 71

dc-test-voltage

Summary

Name dc-test-voltage
Type int16
  
 
The test voltages for the measurement of the 4-element DC
resistance, VDCTR (Tip-to-Ring), VDCRT (Ring-to-Tip), VDCTG
(Tip-to-Ground), and VDCRG (Ring-to-Ground), shall be
represented in linear format. The range of valid values is from
-150 V to +150 V with a granularity of 0.1 V.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.2 (MELT-CDCV-TR, MELT-CDCV-RT, MELT-CDCV-TG, MELT-CDCV-RG)
Source bbf-melt-pmd-measurement-parameter-body line 284

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 2020-06-30
Source openconfig-routing-policy line 129

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

dei

Summary

Name dei
Type uint8
  
 
Drop Eligible Indicator. DEI is a 1-bit field in the VLAN tag.
May be used separately or in conjunction with PCP to indicate
frames eligible to be dropped in the presence of congestion.

Details

Module bbf-dot1q-types
Version 2018-07-13
Reference IEEE 802.1Q-2014: Virtual Bridged Local Area Networks
Source bbf-dot1q-types line 210

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 Std 1588 standard exclusively.

Details

Module ietf-ptp
Version 2019-05-07
Reference IEEE Std 1588-2008: 8.2.5.4.4
Source ietf-ptp line 33

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

derivative

Summary

Name derivative
Type decimal64
  
 
The slope of a line at a point on the line.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 818

dest-address-index-type

Summary

Name dest-address-index-type
Type uint32
  
 
An index value used as the key to the list of destination
MAC addresses used both as the destination addresses on
transmitted LLDPDUs and on received LLDPDUs. This index value
is also used as a secondary key in lists that use interface
as a primary key.

Details

Module ieee802-dot1ab-lldp
Version 2018-11-11
Source ieee802-dot1ab-lldp line 210

device-id

Summary

Name device-id
Type uint8
  
 
Device ID of a G.hn node.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.7.1.1
Source bbf-ghn-types line 117

device-role

Summary

Name device-role
Type identityref
  
 
Role of the device node.

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 285

device-role

Summary

Name device-role
Type identityref
  
 
Role of the device node.

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 239

device-type

Summary

Name device-type
Type enumeration
  
 
Defines device types.

Details

Module ietf-sdwan-svc
Version 2019-06-06
Source ietf-sdwan-svc line 64

DiffType

Summary

Name DiffType
Type enumeration
  
 
Type of comparison output requested.

Details

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

diffusion-coefficient

Summary

Name diffusion-coefficient
Type decimal64
  
 
Diffusivity or diffusion coefficient is a proportionality constant between the molar flux due to molecular diffusion and the gradient in the concentration of the species (or the driving force for diffusion).

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 362

direction

Summary

Name direction
Type enumeration
  
 
Which way are we talking about?

Details

Module ietf-mud
Version 2019-01-28
Source ietf-mud line 67

direction

Summary

Name direction
Type enumeration
  
 
Which way are we talking about?

Details

Module ietf-mud
Version 2018-06-15
Source ietf-mud line 58

direction

Summary

Name direction
Type enumeration

Details

Module org-openroadm-common-alarm-pm-types
Version 2019-11-29
Source org-openroadm-common-alarm-pm-types line 51

direction

Summary

Name direction
Type boolean
  
 
A boolean object indicating whether the direction is
out-facing (True) or in-facing (False).

Details

Module ieee802-dot1cb-stream-identification-types
Version 2020-08-05
Reference Clause 10.4.1.3 of IEEE Std 802.1CB-2017
Source ieee802-dot1cb-stream-identification-types line 101

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 296

direction

Summary

Name direction
Type enumeration
  
 
The data flow direction that is monitored to identify user-defined applications:request/response/both. Request indicates that data to the server is monitored to detect applications, Response indicates that data from the server is monitored to detect applications, and Both indicates that data from and to the server is monitored to detect applications.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 286

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

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

dni

Summary

Name dni
Type string
  
 
Domain Name Identifier of the G.hn domain.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.6.8.2.1
Source bbf-ghn-types line 156

domain-id-profile-ref

Summary

Name domain-id-profile-ref
Type leafref
  
 
Used to reference a domain-id profile.

Details

Module bbf-ghn
Submodule bbf-ghn-domain-profiles
Version 2018-07-13
Source bbf-ghn-domain-profiles line 117

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 2020-06-30
Source openconfig-inet-types line 286

domain-name

Summary

Name domain-name
Type string
  
 
Domain Name of the G.hn domain connected to this interface.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.6.1
Source bbf-ghn-types line 107

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 312

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 355

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 172

domain-name

Summary

Name domain-name
Type string
  
 
This type represents a domain object name.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 438

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 2018-08-10
Reference IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 245

dot1q-tag-type

Summary

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

Details

Module ieee802-dot1q-types
Version 2018-03-07
Reference IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 200

dot1q-tag-type

Summary

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

Details

Module bbf-dot1q-types
Version 2018-07-13
Reference IEEE 802.1Q-2014: Virtual Bridged Local Area Networks
Source bbf-dot1q-types line 122

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 2020-06-30
Source openconfig-yang-types line 78

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 463

downstream-data-rate-profile-ref

Summary

Name downstream-data-rate-profile-ref
Type leafref
  
 
Downstream Data Rate Profile identifier.

Details

Module bbf-vdsl
Submodule bbf-vdsl-service-profiles
Version 2019-10-21
Source bbf-vdsl-service-profiles line 120

downstream-data-rate-profile-ref

Summary

Name downstream-data-rate-profile-ref
Type leafref
  
 
Used to reference a downstream data rate profile.

Details

Module bbf-fast
Submodule bbf-fast-service-profiles
Version 2020-01-17
Source bbf-fast-service-profiles line 142

dpu-reconfiguration-state

Summary

Name dpu-reconfiguration-state
Type enumeration
  
 
Reports the ReConfiguration State for the line. A state
change alarm shall be raised indicating a change of the
line's Reconfiguration State (see clause A.7.2.1.2).

Details

Module bbf-hardware-rpf-dpu
Version 2019-06-11
Reference ITU-T G.997.2 clause A.7.4.1.3 (DPU-RCS)
Source bbf-hardware-rpf-dpu line 151

dpu-reconfiguration-state

Summary

Name dpu-reconfiguration-state
Type enumeration
  
 
Reports the ReConfiguration State for the line. A state
change alarm shall be raised indicating a change of the
line's Reconfiguration State (see clause A.7.2.1.2).

Details

Module bbf-hardware-rpf-dpu-state
Version 2019-06-11
Reference ITU-T G.997.2 clause A.7.4.1.3 (DPU-RCS)
Source bbf-hardware-rpf-dpu-state line 150

dr-priority-type

Summary

Name dr-priority-type
Type uint32
  
 
The port's designated router priority. Larger always preferred.
DR Priority is a 32-bit unsigned number, ranges 0-4294967295.

Details

Module openconfig-pim-types
Version 2018-11-21
Reference RFC7761 4.3.1 page 33
Source openconfig-pim-types line 67

drb-state

Summary

Name drb-state
Type enumeration
  
 
TRILL DRB port state type.

Details

Module ietf-trill
Version 2015-12-21
Source ietf-trill line 44

dscp

Summary

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

Details

Module openconfig-inet-types
Version 2020-06-30
Reference RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Source openconfig-inet-types line 353

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 76

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-08-24
Reference RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Source openconfig-inet-types line 232

dscp-range

Summary

Name dscp-range
Type string
  
 
Defines the type used to represent a list and/or ranges of
DSCP values.

This type is used to match an ordered list of DSCP values, or
contiguous ranges of DSCP values. Valid DSCP values must be in
the range 0 to 63, and included in the list in non
overlapping ascending order.

For example, '1,10-20,33,45-63'.

Details

Module bbf-inet-types
Version 2017-05-08
Source bbf-inet-types line 92

dscp-remarked

Summary

Name dscp-remarked
Type enumeration
  
 
Definition for dscp type.

Details

Module ietf-flowspec
Version 2015-09-15
Source ietf-flowspec line 151

dscp-type

Summary

Name dscp-type
Type union
  
 
Definition for dscp type.

Details

Module ietf-flowspec
Version 2015-09-15
Source ietf-flowspec line 263

duplex-type

Summary

Name duplex-type
Type enumeration
  
 
Used to represent the configured, negotiated, or actual 
duplex mode of an Ethernet interface.

Details

Module ieee802-ethernet-interface
Version 2019-06-21
Reference IEEE Std 802.3, 30.3.1.1.32, aDuplexStatus
Source ieee802-ethernet-interface line 55

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

dynamic-rate-control-type

Summary

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

Details

Module ieee802-ethernet-interface-half-duplex
Version 2019-06-21
Reference IEEE Std 802.3, 4.4.2 ipgStretchRatio and 30.3.1.1.34 aRateControlStatus
Source ieee802-ethernet-interface-half-duplex line 67

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

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 301

egress-action-field-value-type

Summary

Name egress-action-field-value-type
Type enumeration
  
 
Possible values returned in the egress action field.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 509

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 2019-11-07
Source openconfig-aft-types line 56

encoding

Summary

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

Details

Module ietf-subscribed-notifications
Version 2019-09-09
Source ietf-subscribed-notifications line 363

encoding-type

Summary

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

Details

Module yumaworks-types
Version 2020-03-06
Source yumaworks-types line 257

encoding-type

Summary

Name encoding-type
Type enumeration
  
 
Encoding type of an interface.

Details

Module ted
Version 2014-10-27
Reference RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description. RFC 4328: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control.
Source ted line 84

encryption-algorithm-type

Summary

Name encryption-algorithm-type
Type uint16
  
 
The encryption algorithm is specified with a 16-bit
number extracted from IANA Registry. The acceptable
values MUST follow the requirement levels for
encryption algorithms for ESP and IKEv2.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference IANA Registry- Transform Type 1 - Encryption Algorithm Transform IDs. RFC 8221 - Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH) and RFC 8247 - Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2).
Source ietf-ipsec-common line 54

encryption-mode

Summary

Name encryption-mode
Type enumeration
  
 
Encryption mode of the G.hn domain.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 9
Source bbf-ghn-types line 177

energy

Summary

Name energy
Type decimal64
  
 
Energy in joules.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 606

enlp-type

Summary

Name enlp-type
Type enumeration
  
 
The list of possible ENLP(Explicit NULL Label Policy) values.

Details

Module openconfig-segment-routing-types
Version 2020-02-04
Reference draft-ietf-idr-segment-routing-te-policy
Source openconfig-segment-routing-types line 131

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

equipment-type-enum

Summary

Name equipment-type-enum
Type enumeration

Details

Module org-openroadm-common-equipment-types
Version 2019-11-29
Source org-openroadm-common-equipment-types line 62

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 yuma-netconf
Version 2015-04-30
Reference RFC XXXX, section 4.3.
Source yuma-netconf line 378

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 288

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

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 178

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

esp-encap

Summary

Name esp-encap
Type enumeration
  
 
Types of ESP encapsulation when Network Address
Translation (NAT) is present between two NSFs.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference RFC 8229 - TCP Encapsulation of IKE and IPsec Packets and RFC 3948 - UDP Encapsulation of IPsec ESP Packets.
Source ietf-ipsec-common line 108

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 2019-06-21
Source ieee802-ethernet-interface line 44

ether-type

Summary

Name ether-type
Type uint16
  
 
The Ethernet Type (or Length) value.

Details

Module bbf-dot1q-types
Version 2018-07-13
Reference IEEE 802.3-2012: IEEE Standard for Ethernet, clause 3.2.6
Source bbf-dot1q-types line 222

ether-type-or-acronym

Summary

Name ether-type-or-acronym
Type union
  
 
This type allows to specify
- a specific integer value identifying a particular Ethertype
  value of packets,
- a 'pre-defined' enumeration value identifying one or more
  specific Ethertype values,
- the enumeration value 'any' that identifies all packets.

Details

Module bbf-dot1q-types
Version 2018-07-13
Source bbf-dot1q-types line 230

ethernet-encoding-type

Summary

Name ethernet-encoding-type
Type enumeration

Details

Module org-openroadm-common-service-types
Version 2020-05-29
Source org-openroadm-common-service-types line 245

ethertype

Summary

Name ethertype
Type union
  
 
The uint16 type placeholder 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 2019-03-04
Source ietf-ethertypes line 45

ethertype-type

Summary

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

Details

Module openconfig-packet-match-types
Version 2020-06-30
Source openconfig-packet-match-types line 303

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 2018-08-10
Reference 9.2 of IEEE Std 802-2014
Source ieee802-dot1q-types line 234

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 2018-03-07
Reference 9.2 of IEEE Std 802-2014
Source ieee802-dot1q-types line 189

event-counter32-or-unknown

Summary

Name event-counter32-or-unknown
Type union
  
 
An event-counter32-or-unknown type represents a
non-negative integer which may increase but shall never
exceed a maximum value.  The maximum value can not be
greater than 2^32-1 (4294967295 decimal).
The default value for the maximum value is 2^32-1.
The value of a event-counter32-or-inactive has its
maximum value whenever the information being modeled is
greater than or equal to its maximum value.
A special value (enum unknown) indicates that the value of
this counter is unknown is not active on the line.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Source bbf-ghn-types line 312

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 2019-06-21
Source ieee802-ethernet-link-oam line 181

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.

Details

Module ietf-alarms-x733
Version 2019-09-11
Reference ITU-T Recommendation X.733: Information Technology - Open Systems Interconnection - System Management: Alarm Reporting Function ITU-T Recommendation X.736: Information Technology - Open Systems Interconnection - System Management: Security Alarm Reporting Function
Source ietf-alarms-x733 line 98

exi-alignment

Summary

Name exi-alignment
Type enumeration
  
 
EXI alignment specification.

Details

Module ietf-netconf-exi
Version 2014-03-03
Source ietf-netconf-exi line 35

exi-fidelity

Summary

Name exi-fidelity
Type enumeration
  
 
EXI fidelity options.

Details

Module ietf-netconf-exi
Version 2014-03-03
Source ietf-netconf-exi line 59

exi-schema-id

Summary

Name exi-schema-id
Type uint16
  
 
Schema identifier for use in the EXI stream header.

Details

Module ietf-netconf-exi
Version 2014-03-03
Source ietf-netconf-exi line 150

extended-circuit-id

Summary

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

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 342

extended-rpc-status

Summary

Name extended-rpc-status
Type enumeration
  
 
status of RPC 

Details

Module org-openroadm-common-types
Version 2020-05-29
Source org-openroadm-common-types line 140

fabric-port-role

Summary

Name fabric-port-role
Type identityref
  
 
Role of the port in a fabric.

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 293

fabric-port-role

Summary

Name fabric-port-role
Type identityref
  
 
Role of the port in a fabric.

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 245

fabric-port-type

Summary

Name fabric-port-type
Type enumeration
  
 
Fabric port type

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 301

fabric-port-type

Summary

Name fabric-port-type
Type enumeration
  
 
Fabric port type

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 252

failure-mode

Summary

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

Details

Module openconfig-openflow-types
Version 2020-06-30
Source openconfig-openflow-types line 52

far-end-test-groups

Summary

Name far-end-test-groups
Type bits
  
 
A set of bits representing each of the far end test groups.

Details

Module bbf-fast
Submodule bbf-fast-update-test-body
Version 2020-01-17
Source bbf-fast-update-test-body line 152

fast-rate-adaptation-profile-ref

Summary

Name fast-rate-adaptation-profile-ref
Type leafref
  
 
Used to reference a fast rate adaptation profile.

Details

Module bbf-fast
Submodule bbf-fast-quality-profiles
Version 2020-01-17
Source bbf-fast-quality-profiles line 146

fast-retrain-policy-profile-ref

Summary

Name fast-retrain-policy-profile-ref
Type leafref
  
 
Used to reference a fast retrain policy profile.

Details

Module bbf-fast
Submodule bbf-fast-quality-profiles
Version 2020-01-17
Source bbf-fast-quality-profiles line 164

fastdsl-mode-ref

Summary

Name fastdsl-mode-ref
Type identityref
  
 
Reference to a FastDSL mode of operation.

Details

Module bbf-fastdsl
Version 2019-06-11
Source bbf-fastdsl line 164

fault-alarm-type

Summary

Name fault-alarm-type
Type enumeration
  
 
The Fault Alarm indicators.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 666

fiber-pmd

Summary

Name fiber-pmd
Type decimal64
  
 
Polarization Mode Dispersion expressed in ps/km(1/2).

Details

Module org-openroadm-common-link-types
Version 2019-11-29
Source org-openroadm-common-link-types line 69

field-types

Summary

Name field-types
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 1113

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

FilterType

Summary

Name FilterType
Type enumeration
  
 
NETCONF 'filter' Attribute Content

Details

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

flexe-phy-enumeration

Summary

Name flexe-phy-enumeration
Type enumeration
  
 
The current type of PHYs bonded in a FlexE Group. Values for
this enumeration are specified by the OIF standard.

Details

Module ietf-flexe
Version 2019-10-30
Reference OIF Flex 2.0 and 2.1: Section 5.2.1.5
Source ietf-flexe line 96

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 2018-08-11
Source ietf-flexi-grid-ted line 89

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 2018-08-11
Source ietf-flexi-grid-ted line 100

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 2018-08-11
Source ietf-flexi-grid-ted line 111

float

Summary

Name float
Type union
  
 
Definition for float point referenced from maillist.

Details

Module ietf-flowspec
Version 2015-09-15
Source ietf-flowspec line 272

flow-rank

Summary

Name flow-rank
Type uint32
  
 
The rank of a flow with respect to all other flows
in the range of 1 to n where 1 represents the lowest
rank and n is the total number of flows.

Details

Module bbf-qos-policer-envelope-profiles
Version 2018-07-13
Source bbf-qos-policer-envelope-profiles line 143

fng-state-type

Summary

Name fng-state-type
Type enumeration
  
 
Indicates the different states of the MEP Fault Notification
Generator State Machine.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 415

forced-resignation-cause

Summary

Name forced-resignation-cause
Type enumeration
  
 
Cause of a forced resignation.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.6.1.1.4.5
Source bbf-ghn-types line 335

foreign-ac-voltage

Summary

Name foreign-ac-voltage
Type uint16
  
 
The range of valid values for the foreign AC voltages
VTR-AC (Tip-to-Ring), VTG-AC (Tip-to-Ground), and VRG-AC
(Ring-To-Ground) is from 0 to 250Vrms. The foreign AC voltage
shall be represented in linear format with a granularity of
100 mV.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.5 (MELT-FVAC-TR, MELT-FVAC-TG, MELT-FVAC-RG)
Source bbf-melt-pmd-measurement-parameter-body line 235

foreign-ac-voltage-frequency

Summary

Name foreign-ac-voltage-frequency
Type uint16
  
 
The range of valid values for the foreign AC voltage FTR-AC
(Tip-to-Ring), FTG-AC (Tip-to-Ground), and FRG-AC
(Ring-To-Ground) is from 10 to 90 Hz with a granularity
of 0.1 Hz.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.5 (MELT-FVACF-TR, MELT-FVACF-TG, MELT-FVACF-RG)
Source bbf-melt-pmd-measurement-parameter-body line 251

foreign-dc-voltage

Summary

Name foreign-dc-voltage
Type int16
  
 
The range of valid values for the foreign DC voltages,
VTR-DC (Tip-to-Ring), VTG-DC (Tip-to-Ground), and VRG-DC
(Ring-to-Ground) is from -350 to 350V. The foreign DC voltage
shall be represented in linear format with a granularity of
100 mV.

The reported DC voltage polarity is defined with respect to
ground for the VTG-DC and VRG-DC measurements and returns a
positive result for the VTR-DC measurement if the tip wire
is more positive than the ring wire. 

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.5 (MELT-FVDC-TR, MELT-FVDC-TG, MELT-FVDC-RG)
Source bbf-melt-pmd-measurement-parameter-body line 214

FormatType

Summary

Name FormatType
Type enumeration
  
 
Conversion Output Formats.

Details

Module yangdump-pro
Version 2019-09-22
Source yangdump-pro line 224

forwarder-ref

Summary

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

Details

Module bbf-l2-forwarding
Submodule bbf-l2-forwarding-forwarders
Version 2018-12-03
Source bbf-l2-forwarding-forwarders line 124

forwarder-state-ref

Summary

Name forwarder-state-ref
Type leafref
  
 
This type is used by data models that need to reference
operational forwarders.

Details

Module bbf-l2-forwarding
Submodule bbf-l2-forwarding-forwarders
Version 2018-12-03
Source bbf-l2-forwarding-forwarders line 134

four-element-dc-resistance

Summary

Name four-element-dc-resistance
Type uint32
  
 
The 4-element DC resistances, RTR (Tip-to-Ring), RRT
(Ring-to-Tip), RTG (Tip-to-Ground), and RRG (Ring-to-Ground),
shall be represented in linear format. The range of valid
values is from 0 to 10 Mohms with a granularity of 1 ohm.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.1 (MELT-CDCR-TR, MELT-CDCR-RT, MELT-CDCR-TG, MELT-CDCR-RG)
Source bbf-melt-pmd-measurement-parameter-body line 184

fragment-type

Summary

Name fragment-type
Type bits
  
 
Different fragment types to match against.

Details

Module ietf-dots-data-channel
Version 2020-05-28
Source ietf-dots-data-channel line 150

frequency-GHz

Summary

Name frequency-GHz
Type decimal64
  
 
Frequency value in GHz.

Details

Module org-openroadm-common-optical-channel-types
Version 2020-05-29
Source org-openroadm-common-optical-channel-types line 205

frequency-THz

Summary

Name frequency-THz
Type decimal64
  
 
Frequency value in THz.

Details

Module org-openroadm-common-optical-channel-types
Version 2020-05-29
Source org-openroadm-common-optical-channel-types line 196

frequency-type

Summary

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

Details

Module openconfig-transport-types
Version 2020-08-12
Source openconfig-transport-types line 95

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 gate-state-value-type indicates a gate state, open or closed,
for the stream gate.

Details

Module ieee802-dot1q-stream-filters-gates
Version 2020-02-15
Reference 12.31.3.2.1 of IEEE Std 802.1Qcr-2020
Source ieee802-dot1q-stream-filters-gates line 147

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 173

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

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 2020-06-30
Source openconfig-yang-types line 179

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 196

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

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 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

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-12-04
Reference RFC 3471: Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description. Section 3.2.
Source ietf-routing-types line 642

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 2020-08-06
Source ietf-te-topology line 107

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 141

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 2018-02-14
Source ietf-netconf-acm line 149

group-size

Summary

Name group-size
Type uint8
  
 
Group size for channel estimation.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9960 Table 7-13
Source bbf-ghn-types line 460

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 2018-05-17
Source ietf-pmip-qos line 251

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 2018-05-17
Source ietf-pmip-qos line 258

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

handshake-profile-ref

Summary

Name handshake-profile-ref
Type leafref
  
 
Used to reference a handshake profile.

Details

Module bbf-ghs
Submodule bbf-ghs-handshake-profiles
Version 2019-06-11
Source bbf-ghs-handshake-profiles line 112

hello-padding-type

Summary

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

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 212

hex-string

Summary

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

Details

Module openconfig-yang-types
Version 2020-06-30
Source openconfig-yang-types line 93

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 435

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

highest-defect-priority-type

Summary

Name highest-defect-priority-type
Type enumeration
  
 
An enumerated value, equal to the contents of the variable
highestDefect (20.35.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.
The integer value assigned to the enum value determines the
priority. The higher value corresponds to the higher priority.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 244

hop-limit-action-definition

Summary

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

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 276

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 2020-06-30
Source openconfig-inet-types line 327

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 369

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 409

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 206

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-minute-second

Summary

Name hour-minute-second
Type string
  
 
The representation of Hour, Minute, Sencond - hh:mm:ss

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 374

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 2019-05-28
Source ietf-l2vpn line 412

iana-if-type

Summary

Name iana-if-type
Type enumeration
  
 
This data type is used as the syntax of the 'type'
leaf in the 'interface' list in the YANG module
ietf-interface.

The definition of this typedef 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).

Details

Module iana-if-type
Version 2011-09-07
Source iana-if-type line 45

icmp-name-type

Summary

Name icmp-name-type
Type enumeration
  
 
This type is an enumeration of ICMP type names.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 87

icmp6-name-type

Summary

Name icmp6-name-type
Type enumeration
  
 
This type is an enumeration of ICMPv6 type names.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 174

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
  
 
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 2019-12-07
Source yangcli-pro line 496

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

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 2019-04-16
Source openconfig-types line 113

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 265

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 256

if-index

Summary

Name if-index
Type leafref
  
 
This type is used by the data model to reference network
interfaces in the system.

Details

Module ietf-gptp
Version 2018-03-28
Source ietf-gptp line 145

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 org-openroadm-ospf
Version 2020-05-29
Source org-openroadm-ospf line 289

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 286

ifState

Summary

Name ifState
Type enumeration
  
 
Interface state.

Details

Module l2vpn
Version 2014-08-21
Source l2vpn line 237

igmp-interval-type

Summary

Name igmp-interval-type
Type uint16
  
 
Interval at which the router sends the IGMP query message toward
the upstream neighbor.

Details

Module openconfig-igmp-types
Version 2018-11-21
Reference RFC3376 8.2 Page 40
Source openconfig-igmp-types line 54

igmp-version

Summary

Name igmp-version
Type uint8
  
 
IGMP Version.

Details

Module openconfig-igmp-types
Version 2018-11-21
Reference v1 = RFC1112, v2 = RFC2236, v3 = RFC3376
Source openconfig-igmp-types line 45

IndentType

Summary

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

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 312

information

Summary

Name information
Type decimal64
  
 
Amount of information in bits of information entropy.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 590

information-measurement

Summary

Name information-measurement
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 577

information-rate

Summary

Name information-rate
Type uint64
  
 
Information rate in bits per second.

Details

Module bbf-qos-policing-types
Version 2018-07-13
Source bbf-qos-policing-types line 91

ingress-action-field-value-type

Summary

Name ingress-action-field-value-type
Type enumeration
  
 
Possible values returned in the ingress action field.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 478

instance-id-type

Summary

Name instance-id-type
Type uint32

Details

Module lisp-address-types
Version 2015-03-23
Source lisp-address-types line 40

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

instanceType

Summary

Name instanceType
Type enumeration
  
 
Instance type. 

Details

Module l2vpn
Version 2014-08-21
Source l2vpn line 281

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 2019-11-29
Source yuma-types line 66

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-type

Summary

Name integrity-algorithm-type
Type uint16
  
 
The integrity algorithm is specified with a 16-bit
number extracted from IANA Registry.
The acceptable values MUST follow the requirement
levels for encryption algorithms for ESP and IKEv2.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference IANA Registry- Transform Type 3 - Integrity Algorithm Transform IDs. RFC 8221 - Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH) and RFC 8247 - Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2).
Source ietf-ipsec-common line 72

interface-event-type

Summary

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

Details

Module ietf-pim-base
Version 2018-04-16
Source ietf-pim-base line 194

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 2019-11-19
Source openconfig-interfaces line 148

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-ref

Summary

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

Details

Module ietf-interfaces
Version 2018-02-20
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 org-openroadm-device
Version 2020-05-29
Source org-openroadm-device line 223

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-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 2018-02-20
Source ietf-interfaces line 656

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-status-tlv-value-type

Summary

Name interface-status-tlv-value-type
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.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 188

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 2018-08-11
Source ietf-flexi-grid-ted line 73

interface-usage

Summary

Name interface-usage
Type enumeration
  
 
This type identifies the position of the interface in the
network. Access Nodes are typically asymetric: some interfaces
connect users to the Access Node while other interfaces connect
the Access Node to the network.

For some functionality of the Access Node the position of the
interface matters.

Details

Module bbf-interface-usage
Version 2018-12-03
Source bbf-interface-usage line 112

ip-address

Summary

Name ip-address
Type union
  
 
An IPv4 or IPv6 address with no prefix specified.

Details

Module openconfig-inet-types
Version 2020-06-30
Source openconfig-inet-types line 238

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 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 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-08-24
Source openconfig-inet-types line 124

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 248

ip-address-or-unresolved

Summary

Name ip-address-or-unresolved
Type union
  
 
A type meant for a leaf which is either an IP address or
reflects that no IP address is available.

Details

Module bbf-xpon-types
Version 2019-02-25
Source bbf-xpon-types line 398

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 80

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module openconfig-if-ip
Version 2019-01-08
Source openconfig-if-ip line 100

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module ietf-ip
Version 2018-02-22
Source ietf-ip line 79

ip-address-origin

Summary

Name ip-address-origin
Type enumeration
  
 
The origin of an address.

Details

Module org-openroadm-ip
Version 2020-05-29
Source org-openroadm-ip line 92

ip-mac-binding-type

Summary

Name ip-mac-binding-type
Type enumeration
  
 
The user and IP/MAC address binding mode: bidirectional, or unidirectional. In unidirectional binding, a user must use the specified IP and MAC addresses to log in. The same IP and MAC addresses can also be used by other users.  In bidirectional binding, a user must use the specified IP and MAC addresses to log in. The same IP and MAC addresses cannot be used by other bidirectional binding users.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 348

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-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-12-04
Source ietf-routing-types line 450

ip-prefix

Summary

Name ip-prefix
Type union
  
 
An IPv4 or IPv6 prefix.

Details

Module openconfig-inet-types
Version 2020-06-30
Source openconfig-inet-types line 247

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 240

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 288

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 133

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 2020-06-30
Source openconfig-packet-match-types line 288

ip-route-match-type-definition

Summary

Name ip-route-match-type-definition
Type identityref
  
 
IP route match type definition.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 365

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 2020-06-30
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 256

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 47

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

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 142

ipsec-inner-protocol

Summary

Name ipsec-inner-protocol
Type union
  
 
IPsec protection can be applied to specific IP
traffic and layer 4 traffic (TCP, UDP, SCTP, etc.)
or ANY protocol in the IP packet payload. We
specify the IP protocol number with an uint8 or
ANY defining an enumerate with value 256 to
indicate the protocol number.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference Section 4.4.1.1 in RFC 4301. IANA Registry - Protocol Numbers.
Source ietf-ipsec-common line 230

ipsec-mode

Summary

Name ipsec-mode
Type enumeration
  
 
Type definition of IPsec mode: transport or
tunnel.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference Section 3.2 in RFC 4301.
Source ietf-ipsec-common line 90

ipsec-protocol-parameters

Summary

Name ipsec-protocol-parameters
Type enumeration
  
 
Only the Encapsulation Security Protocol (ESP) is
supported but it could be extended in the future.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference RFC 4303- IP Encapsulating Security Payload (ESP).
Source ietf-ipsec-common line 145

ipsec-spd-action

Summary

Name ipsec-spd-action
Type enumeration
  
 
The action when traffic matches an IPsec security
policy. According to RFC 4301 there are three
possible values: BYPASS, PROTECT AND DISCARD

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference Section 4.4.1 in RFC 4301.
Source ietf-ipsec-common line 205

ipsec-traffic-direction

Summary

Name ipsec-traffic-direction
Type enumeration
  
 
IPsec traffic direction is defined in two
directions: inbound and outbound. From a NSF
perspective inbound means the traffic that enters
the NSF and outbound is the traffic that is sent
from the NSF.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference Section 5 in RFC 4301.
Source ietf-ipsec-common line 186

ipv-spec-type

Summary

Name ipv-spec-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 the frame 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 2020-02-15
Reference 8.6.5.2 of IEEE Std 802.1Qcr-2020
Source ieee802-dot1q-stream-filters-gates line 87

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 2020-06-30
Source openconfig-inet-types line 92

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 179

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 using the default
zone.

Details

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

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 2020-06-30
Source openconfig-inet-types line 106

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 73

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-multicast-source-address

Summary

Name ipv4-multicast-source-address
Type union
  
 
Multicast source IPv4 address type.

Details

Module ietf-routing-types
Version 2017-12-04
Source ietf-routing-types line 461

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 2020-06-30
Source openconfig-inet-types line 193

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 251

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 299

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 105

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 2020-06-30
Source openconfig-inet-types line 122

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 201

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, using the default zone.

Details

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

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 2020-06-30
Source openconfig-inet-types line 156

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 93

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 2020-06-30
Reference RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
Source openconfig-inet-types line 365

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 95

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-08-24
Reference RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
Source openconfig-inet-types line 244

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-multicast-source-address

Summary

Name ipv6-multicast-source-address
Type union
  
 
Multicast source IPv6 address type.

Details

Module ietf-routing-types
Version 2017-12-04
Source ietf-routing-types line 475

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 2020-06-30
Source openconfig-inet-types line 207

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 272

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 320

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 114

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-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, except that it only allows
an IPv6 address as the global administrator.  The format
is <ipv6-address:2-octet-number>.

Two valid examples are 2001:db8::1:6544 and
2001:db8::5eb1:791:6b37:17958.

Details

Module ietf-routing-types
Version 2017-12-04
Reference RFC 5701: IPv6 Address Specific BGP Extended Community Attribute.
Source ietf-routing-types line 393

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

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, except that it only
allows an IPv6 address as the global administrator.
The format is <ipv6-address:2-octet-number>.

Two valid examples are 2001:db8::1:6544 and
2001:db8::5eb1:791:6b37:17958.

Details

Module ietf-routing-types
Version 2017-12-04
Reference RFC 5701: IPv6 Address Specific BGP Extended Community Attribute.
Source ietf-routing-types line 210

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 2020-06-30
Source openconfig-isis-types line 290

itf-status-type

Summary

Name itf-status-type
Type enumeration
  
 
Interface status

Details

Module example
Version none
Source example line 7

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

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-routing-key-chain
Version 2016-03-15
Source ietf-routing-key-chain line 68

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 org-openroadm-key-chain
Version 2019-11-29
Source org-openroadm-key-chain line 62

key-derivation-function-type

Summary

Name key-derivation-function-type
Type identityref
  
 
This type identifies the key derivation function

Details

Module ietf-key-table
Version 2015-08-28
Source ietf-key-table line 110

l2vpn-discovery-type

Summary

Name l2vpn-discovery-type
Type identityref
  
 
L2VPN discovery type

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 342

l2vpn-instance-name-ref

Summary

Name l2vpn-instance-name-ref
Type leafref
  
 
l2vpn-instance-name-ref

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 384

l2vpn-instance-type-ref

Summary

Name l2vpn-instance-type-ref
Type leafref
  
 
l2vpn-instance-type-ref

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 392

l2vpn-service-type

Summary

Name l2vpn-service-type
Type identityref
  
 
L2VPN service type

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 335

l2vpn-signaling-type

Summary

Name l2vpn-signaling-type
Type identityref
  
 
L2VPN signaling type

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 349

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-event-type

Summary

Name l3-event-type
Type enumeration
  
 
Layer 3 event type for notifications

Details

Module ietf-l3-unicast-topology
Version 2018-02-26
Source ietf-l3-unicast-topology line 62

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

l3-flag-type

Summary

Name l3-flag-type
Type identityref
  
 
L3 flag attributes

Details

Module ietf-l3-unicast-topology
Version 2018-02-26
Source ietf-l3-unicast-topology line 104

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 2018-11-21
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 55

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 2018-11-21
Reference IEEE 802.3ad
Source openconfig-lacp line 112

lacp-synchronization-type

Summary

Name lacp-synchronization-type
Type enumeration
  
 
Indicates LACP synchronization state of participant

Details

Module openconfig-lacp
Version 2018-11-21
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 94

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 2018-11-21
Reference IEEE 802.1AX-2008
Source openconfig-lacp line 74

lan-path-id

Summary

Name lan-path-id
Type int8
  
 
An integer specifying a path or LAN. If and only if a packet
matches an entry in the Sequence identification table (10.5)
that specifies HSR or PRP in its frerSeqEncEncapsType (10.5.1.5)
object, tsnStreamIdLanPathId specifies the LanId or PathId value
that must be matched for this tsnStreamIdEntry to apply. A value
of –1 indicates that the LanId or PathId are to be ignored.

Details

Module ieee802-dot1cb-frer-types
Version 2020-04-29
Reference Clause 10.22 of IEEE Std 802.1CB-2017
Source ieee802-dot1cb-frer-types line 67

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

last-event

Summary

Name last-event
Type uint32
  
 
Number of seconds That passed since the last event.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Source bbf-ghn-types line 305

layer-rate-enum

Summary

Name layer-rate-enum
Type enumeration

Details

Module org-openroadm-layerRate
Version 2019-11-29
Source org-openroadm-layerRate line 55

lbm-data-tlv-type

Summary

Name lbm-data-tlv-type
Type binary
  
 
The loopback message Data TLV type.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 684

length-scale

Summary

Name length-scale
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 224

level-number

Summary

Name level-number
Type uint8
  
 
This type defines ISIS level.

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 191

level-type

Summary

Name level-type
Type enumeration
  
 
This type defines ISIS level types

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 175

lifecycle-state

Summary

Name lifecycle-state
Type enumeration
  
 
Lifecycle state.

Details

Module org-openroadm-common-state-types
Version 2019-11-29
Source org-openroadm-common-state-types line 55

lifetime-action

Summary

Name lifetime-action
Type enumeration
  
 
When the lifetime of an IPsec SA expires an action
needs to be performed over the IPsec SA that
reached the lifetime. There are three posible
options: terminate-clear, terminate-hold and
replace.

Details

Module ietf-ipsec-common
Version 2019-08-05
Reference Section 4.5 in RFC 4301.
Source ietf-ipsec-common line 158

lifetime-type

Summary

Name lifetime-type
Type string
  
 
This type identifies a time in the format YYYYMMDDHHSSZ, where the first four digits specify the year, the next two digits specify the month, the next two digits specify the day, the next two digits specify the hour, the next two digits specify the second, ending with the letter 'Z' as a clear indication that the time is in Coordinated Universal Time (UTC).

Details

Module ietf-key-table
Version 2015-08-28
Source ietf-key-table line 126

limitmask-descriptor

Summary

Name limitmask-descriptor
Type bits
  
 
This contains the G.993.2 limit Power Spectral Density (PSD)
masks of the selected PSD mask class, enabled by the near-end
xDSL Transceiver Unit (xTU) on this line for each class of
profiles.

See Table 7-7 of ITU-T G.997.1 for the definition of each
bit.

Details

Module bbf-vdsl
Submodule bbf-vdsl-base-body
Version 2019-10-21
Reference ITU-T G.997.1 clause 7.3.1.2.16 VDSL2 limit PSD masks and band plans enabling (LIMITMASK)
Source bbf-vdsl-base-body line 607

line-amplifier-control-mode

Summary

Name line-amplifier-control-mode
Type enumeration
  
 
Identifies the line amplifier control mode, either off or gain.

Details

Module org-openroadm-common-amplifier-types
Version 2019-11-29
Source org-openroadm-common-amplifier-types line 63

line-identifier

Summary

Name line-identifier
Type string
  
 
identifies a line

Details

Module bbf-vdsl
Submodule bbf-vdsl-base-body
Version 2019-10-21
Source bbf-vdsl-base-body line 161

line-spectrum-profile-ref

Summary

Name line-spectrum-profile-ref
Type leafref
  
 
Used to reference a line spectrum profile.

Details

Module bbf-ghn
Submodule bbf-ghn-link-profiles
Version 2018-07-13
Source bbf-ghn-link-profiles line 90

line-threshold-profile-ref

Summary

Name line-threshold-profile-ref
Type leafref
  
 
xDSL Transceiver Unit (xTU) Line Threshold Profile name.

Details

Module bbf-vdsl
Submodule bbf-vdsl-threshold-management
Version 2019-10-21
Source bbf-vdsl-threshold-management line 129

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-access-type

Summary

Name link-access-type
Type enumeration
  
 
Link access type.

Details

Module ietf-routing-types
Version 2017-12-04
Source ietf-routing-types line 521

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 2019-05-28
Source ietf-l2vpn line 356

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-flag-type

Summary

Name link-flag-type
Type identityref
  
 
Link flag attributes

Details

Module ietf-l3-unicast-topology
Version 2018-02-26
Source ietf-l3-unicast-topology line 97

link-ref

Summary

Name link-ref
Type instance-identifier
  
 
A reference to a link in topology

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 270

link-ref

Summary

Name link-ref
Type instance-identifier
  
 
A reference to a link in topology

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 227

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

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 2020-03-24
Source openconfig-local-routing line 102

location

Summary

Name location
Type enumeration

Details

Module org-openroadm-common-alarm-pm-types
Version 2019-11-29
Source org-openroadm-common-alarm-pm-types line 68

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 26

LogCount

Summary

Name LogCount
Type int32
  
 
Number of log entries. -1 means all entries

Details

Module yangcli-pro
Version 2019-12-07
Source yangcli-pro line 432

LogIndex

Summary

Name LogIndex
Type uint32
  
 
Index into a log buffer.

Details

Module yangcli-pro
Version 2019-12-07
Source yangcli-pro line 440

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 2019-11-29
Source yuma-types line 76

loop-complex-admittance

Summary

Name loop-complex-admittance
Type uint32
  
 
The range of valid values for the 3-element complex
conductance and susceptance GTR,HV and BTR,HV (Tip-to-Ring) is
from 0.1 uSiemens to 0.1 Siemens. The values shall be
represented in linear format with a granularity of 0.1
uSiemens. The GTR,HV and BTR,HV values of the loop complex
admittance with high metallic voltage test are the total
conductance and susceptance measured. The GTR and BTR values
obtained from the 3-element complex admittance with controlled
metallic voltage test are not subtracted from the results.

NOTE - The linear format is chosen for simplicity reason and
does not imply any future accuracy requirements.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.10 (MELT-HAG-TR, MELT-HAB-TR)
Source bbf-melt-pmd-measurement-parameter-body line 386

loop-diagnostics-result

Summary

Name loop-diagnostics-result
Type enumeration
  
 
The overall results of the Loop Diagnostics mode.

Details

Module bbf-vdsl
Submodule bbf-vdsl-test-diagnostics
Version 2019-10-21
Reference ITU-T G.997.1 Clause 7.5.1.45 (LDR)
Source bbf-vdsl-test-diagnostics line 134

loop-resistance

Summary

Name loop-resistance
Type uint32
  
 
The loop resistances RTF-HV (Tip-to-Ring) and RRT-HV
(Ring-to-Tip) shall be represented in linear format. The range
of valid values is from 0 to 10 Mohms with a granularity of 1
ohm. The RTR-HV and RRT-HV values of the loop resistance with
high metallic voltage test are the total resistances measured.
The RTR and RRT values obtained from the 3-element resistance
with controlled metallic voltage test are not subtracted from
the results.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.7 (MELT-HDCR-TR, MELT-HDCR-RT)
Source bbf-melt-pmd-measurement-parameter-body line 266

loop-resistance-test-voltage

Summary

Name loop-resistance-test-voltage
Type int16
  
 
The test voltages for the measurement of the loop resistance
with a high metallic voltage, VDCHTR (Tip-to-Ring) and
VDCHRT (Ring-to-Tip) shall be represented in linear format.
The range of valid values is from -150 V to +150 V with a
granularity of 0.1 V.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clause E.2.3.8 (MELT-HDCV-TR, MELT-HDCV-RT)
Source bbf-melt-pmd-measurement-parameter-body line 316

loopback-mode-type

Summary

Name loopback-mode-type
Type enumeration
  
 
Loopback modes for transponder logical channels

Details

Module openconfig-transport-types
Version 2020-08-12
Source openconfig-transport-types line 121

loopback-status

Summary

Name loopback-status
Type enumeration
  
 
The loopback mode of an OAM interface.

Details

Module ieee802-ethernet-link-oam
Version 2019-06-21
Reference IEEE Std 802.3, 57.2.11
Source ieee802-ethernet-link-oam line 198

low-power-data-rate-profile-ref

Summary

Name low-power-data-rate-profile-ref
Type leafref
  
 
Used to reference a low power data rate profile.

Details

Module bbf-fast
Submodule bbf-fast-service-profiles
Version 2020-01-17
Source bbf-fast-service-profiles line 160

lowest-alarm-priority-type

Summary

Name lowest-alarm-priority-type
Type enumeration
  
 
Specifies the lowest priority defect that is allowed to
generate a Fault Alarm (20.9.5). The to be reported defects
are identified per enum value.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 294

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 2020-06-30
Source openconfig-isis-types line 348

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 2018-02-07
Source ietf-connection-oriented-oam line 216

ma-name-string

Summary

Name ma-name-string
Type string
  
 
Generic administrative name for a
Maintenance Association (MA).

Details

Module ietf-connection-oriented-oam
Version 2019-04-16
Source ietf-connection-oriented-oam line 243

mac-address

Summary

Name mac-address
Type string
  
 
An IEEE 802 MAC address

Details

Module openconfig-yang-types
Version 2020-06-30
Source openconfig-yang-types line 198

mac-address

Summary

Name mac-address
Type enumeration
  
 
Type of MAC address.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.1.2
Source bbf-ghn-types line 395

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 403

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 2019-03-07
Reference 3.1 of IEEE Std 802-2014 8.1 of IEEE Std 802-2014
Source ieee802-types line 35

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 362

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 2018-03-07
Reference 3.1 of IEEE Std 802-2014 8.1 of IEEE Std 802-2014
Source ieee802-types line 30

macsec-cipher-suite

Summary

Name macsec-cipher-suite
Type enumeration
  
 
Set Cipher suite(s) for SAK derivation

Details

Module openconfig-macsec-types
Version 2019-07-01
Source openconfig-macsec-types line 28

man-addr-if-subtype

Summary

Name man-addr-if-subtype
Type enumeration
  
 
This is the basis of a particular type of
interface associated with the management address.

Details

Module ieee802-dot1ab-lldp
Version 2018-11-11
Reference IEEE Std 802.1AB-2016: 8.5.9.5
Source ieee802-dot1ab-lldp line 68

man-addr-type

Summary

Name man-addr-type
Type binary
  
 
The value of a management address associated with the LLDP
agent that may be used to reach higher layer entities to
assist discovery by network management.

It should be noted that appropriate security credentials,
such as SNMP engineId, may be required to access the LLDP
agent using a management address.  These necessary credentials
should be known by the network management and the objects
associated with the credentials are not included in the
LLDP agent.

Details

Module ieee802-dot1ab-lldp
Version 2018-11-11
Reference IEEE Std 802.1AB-2016: 8.5.9.4
Source ieee802-dot1ab-lldp line 97

mapping-mode-type

Summary

Name mapping-mode-type
Type enumeration

Details

Module org-openroadm-common-service-types
Version 2020-05-29
Source org-openroadm-common-service-types line 256

mass

Summary

Name mass
Type decimal64

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 277

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 2018-11-21
Source openconfig-policy-types line 106

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 2018-11-21
Source openconfig-policy-types line 84

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 101

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 2018-02-14
Source ietf-netconf-acm line 109

math-package

Summary

Name math-package
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 144

math-package

Summary

Name math-package
Type enumeration

Details

Module ieee1906-dot1-metrics
Version 2020-07-07
Source ieee1906-dot1-metrics line 70

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 2018-02-07
Source ietf-connection-oriented-oam line 229

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 2019-04-16
Source ietf-connection-oriented-oam line 256

md-level-type

Summary

Name md-level-type
Type uint8
  
 
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 ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 146

md-name-string

Summary

Name md-name-string
Type string
  
 
Generic administrative name for Maintenance Domain (MD).

Details

Module ietf-connection-oriented-oam
Version 2018-02-07
Source ietf-connection-oriented-oam line 210

md-name-string

Summary

Name md-name-string
Type string
  
 
Generic administrative name for Maintenance Domain (MD).

Details

Module ietf-connection-oriented-oam
Version 2019-04-16
Source ietf-connection-oriented-oam line 237

md5-crypt

Summary

Name md5-crypt
Type string
  
 
The md5-crypt type is used to store a password hash based on the
MD5 message digest algorithm.  When a clear text value is set to
a leaf of this type, the server calculates a MD5 password hash,
and stores the result in the datastore.  Thus, the password is
never stored in clear text.

When a leaf of this type is read, the stored password hash is
returned.

A value of this type matches one of the forms:

  $0$<clear text password>
  $1$<salt>$<password hash>

The '$0$' prefix signals that the value is clear text.  When
such a value is received by the server, an MD5 digest is
calculated, and the string '$1$<salt>$' is prepended to the
result, where <salt> is a random 2-8 characters long salt used
to generate the digest.  This value is stored in the
configuration data store.

If a value starting with '$1$<salt>$' is received, the server
knows that the value already represents an MD5 digest, 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 correct.

The digest algorithm is the md5 crypt function used for
encrypting passwords for various UNIX systems.

Details

Module nacm
Version 2010-09-02
Reference RFC 1321: The MD5 Message-Digest Algorithm http://en.wikipedia.org/wiki/Crypt_(Unix)
Source nacm line 244

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

measurement-voltage

Summary

Name measurement-voltage
Type uint16
  
 
The range of valid values for the AC voltages VACTR-CC
(Tip-to-Ring), VACTG-CC (Tip-to-Ground), and VACRG-CC
(Ring-to-Ground) for the 3-element capacitance test with
a controlled metallic voltage is from 0 V rms to 150 V rms.
The values shall be represented in linear format with a
granularity of 0.1 V.

The range of valid values for the AC voltage VACTR-HC for the
loop capacitance test with a high metallic voltage is from 0
Vrms to 150 Vrms. The values shall be represented in linear
format with a granularity of 0.1 V.

The range of valid values for the AC voltages VACTR-CA,
VACTG-CA, and VACRG-CA for the 3-element complex admittance
test with a controlled metallic voltage is from 0 Vrms to 150
Vrms. The values shall be represented in linear format with a
granularity of 0.1 V.

The range of valid values for the AC voltage VACTR-HA for the
loop complex admittance test with a high metallic voltage is
from 0 V rms to 150 V rms. The values shall be represented in
linear format with a granularity of 0.1 V.

Details

Module bbf-melt
Submodule bbf-melt-pmd-measurement-parameter-body
Version 2019-06-11
Reference ITU-T G.996.2 clauses E.2.3.11 (MELT-ACV-CC-TR, MELT-ACV-CC-TG, MELT-ACV-CC-RG); E.2.3.12 (MELT-ACV-HC-TR); E.2.3.13 (MELT-ACV-CA-TR, MELT-ACV-CA-TG, MELT-ACV-CA-RG); E.2.3.14 (MELT-ACV-HA-TR); and E.2.2.3 (MELT-HCA-V)
Source bbf-melt-pmd-measurement-parameter-body line 331

medium

Summary

Name medium
Type enumeration
  
 
Medium used by this interface.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9960 and ITU-T G.9964
Source bbf-ghn-types line 254

medium-access

Summary

Name medium-access
Type enumeration
  
 
Medium access used by this interface.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9963
Source bbf-ghn-types line 287

mep-defects-type

Summary

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

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 575

mep-id-type

Summary

Name mep-id-type
Type uint16
  
 
Maintenance association End Point Identifier, which is
unique over a given Maintenance Association.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 137

mep-name

Summary

Name mep-name
Type string
  
 
Generic administrative name for a Maintenance End Point
(MEP).

Details

Module ietf-connection-oriented-oam
Version 2018-02-07
Source ietf-connection-oriented-oam line 193

mep-name

Summary

Name mep-name
Type string
  
 
Generic administrative name for a MEP.

Details

Module ietf-connection-oriented-oam
Version 2019-04-16
Source ietf-connection-oriented-oam line 220

mep-tx-ltm-flags-type

Summary

Name mep-tx-ltm-flags-type
Type bits
  
 
The flags field for LTMs transmitted by the MEP.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 654

message-carrier-types

Summary

Name message-carrier-types
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 1063

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 2020-06-30
Source openconfig-isis-types line 273

metric-type

Summary

Name metric-type
Type enumeration
  
 
This type defines ISIS metric type

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 244

mgmd-protocol-and-version

Summary

Name mgmd-protocol-and-version
Type bits
  
 
Identifies the protocols and/or protocol versions supported.

Details

Module bbf-mgmd-types
Version 2019-10-21
Reference RFC 5519, description of object xxxInterfaceVersion
Source bbf-mgmd-types line 102

mhf-creation-type

Summary

Name mhf-creation-type
Type enumeration
  
 
Indicates if the Management Entity can create MHFs.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 81

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-08-08
Source ietf-lmap-common line 274

mka-an

Summary

Name mka-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-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 9.8, Clause 9.16
Source ieee802-dot1x-types line 179

mka-an

Summary

Name mka-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-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 9.8, Clause 9.16
Source ieee802-dot1x-types line 1

mka-kn

Summary

Name mka-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-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 9.8, Clause 9.16
Source ieee802-dot1x-types line 170

mka-kn

Summary

Name mka-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-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 9.8, Clause 9.16
Source ieee802-dot1x-types line 1

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 2019-06-21
Reference IEEE Std 802.3, 57.2.9 and 30.3.6.1.3.
Source ieee802-ethernet-link-oam line 162

mode

Summary

Name mode
Type enumeration
  
 
The mode of keyword identification to identify user-defined applications. If the keyword exists in one packet, the mode is Packet. If the keyword exists in multiple packets, the mode is Flow.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 271

modulation-format

Summary

Name modulation-format
Type enumeration
  
 
Modulation format

Details

Module org-openroadm-common-optical-channel-types
Version 2020-05-29
Source org-openroadm-common-optical-channel-types line 232

modulation-type

Summary

Name modulation-type
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 110

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 2018-11-21
Source openconfig-catalog-types line 235

month

Summary

Name month
Type enumeration
  
 
A type modeling the month in the Julian and Gregorian
tradition.

Details

Module ietf-lmap
Version 2015-01-23
Source ietf-lmap line 73

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-08-08
Source ietf-lmap-common line 170

motion-type

Summary

Name motion-type
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 198

motion-types

Summary

Name motion-types
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 1092

mp-direction-type

Summary

Name mp-direction-type
Type enumeration
  
 
Indicates the direction in which the Maintenance
Point (MEP or MIP) faces on the Bridge Port.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 117

mp-type

Summary

Name mp-type
Type enumeration
  
 
Indicates the type of Maintenance Point.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 64

mpls-label

Summary

Name mpls-label
Type union
  
 
type for MPLS label value encoding

Details

Module mpls-types
Version 2015-02-01
Reference RFC 3032 - MPLS Label Stack Encoding
Source mpls-types line 63

mpls-label

Summary

Name mpls-label
Type union
  
 
type for MPLS label value encoding

Details

Module openconfig-mpls-types
Version 2020-02-04
Reference RFC 3032 - MPLS Label Stack Encoding
Source openconfig-mpls-types line 345

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
  
 
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

Summary

Name mpls-label
Type union
  
 
The 20-bit label value in an MPLS label stack as specified
in RFC 3032.  This label value does not include the
encodings of Traffic Class and TTL.

Details

Module ietf-routing-types
Version 2017-12-04
Reference RFC 3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 679

mpls-label-action-definition

Summary

Name mpls-label-action-definition
Type identityref
  
 
MPLS label action definition.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 176

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-general-use

Summary

Name mpls-label-general-use
Type uint32
  
 
The 20-bit label value in an MPLS label stack as specified
in RFC 3032.  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-12-04
Reference RFC 3032: MPLS Label Stack Encoding.
Source ietf-routing-types line 665

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-label-special-purpose

Summary

Name mpls-label-special-purpose
Type identityref
  
 
This type represents the special-purpose MPLS label values.

Details

Module ietf-routing-types
Version 2017-12-04
Reference RFC 3032: MPLS Label Stack Encoding. RFC 7274: Allocating and Retiring Special-Purpose MPLS Labels.
Source ietf-routing-types line 653

mpls-ldp-adjacency-type

Summary

Name mpls-ldp-adjacency-type
Type enumeration
  
 
enumerated type for specifying LDP adjacencies

Details

Module openconfig-mpls-ldp
Version 2019-07-09
Source openconfig-mpls-ldp line 135

mpls-ldp-afi

Summary

Name mpls-ldp-afi
Type enumeration
  
 
enumerated type for specifying LDP AFIs

Details

Module openconfig-mpls-ldp
Version 2019-07-09
Source openconfig-mpls-ldp line 150

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 2020-02-04
Source openconfig-mpls-types line 446

msdu-mask-length-type

Summary

Name msdu-mask-length-type
Type uint16
  
 
unsigned integer between 2 and 1024

Details

Module ieee802-dot1cb-mask-and-match
Version 2020-07-29
Source ieee802-dot1cb-mask-and-match line 72

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 2018-08-10
Reference 13.8 of IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 171

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 2018-03-07
Reference 13.8 of IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 126

multi-pair-detection-state

Summary

Name multi-pair-detection-state
Type enumeration
  
 
Detection state of a multi-pair PSE.

Details

Module ieee802-ethernet-pse
Version 2019-06-21
Reference IEEE Std 802.3, 30.9.1.1.5
Source ieee802-ethernet-pse line 38

multicast-class1-mac-address-type

Summary

Name multicast-class1-mac-address-type
Type string
  
 
The multicast class 1 MAC address must take the
form of 01-80-C2-00-00-3x, where x represents
the MEG level, with x being a value in the range
of 0..7.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 53

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-action-type

Summary

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

Details

Module nacm
Version 2010-09-02
Source nacm line 199

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-group-name-type

Summary

Name nacm-group-name-type
Type string
  
 
Name of administrative group that can be
assigned to the user, and specified in
an access control rule.

Details

Module nacm
Version 2010-09-02
Source nacm line 188

nacm-matchall-string-type

Summary

Name nacm-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 nacm
Version 2010-09-02
Source nacm line 132

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-rights-type

Summary

Name nacm-rights-type
Type union
  
 
NETCONF Access Rights.
The string '*' indicates that all possible access
rights apply to the access rule.  Otherwise, only
the specific access rights represented by the bit names
that are present apply to the access rule.

Details

Module nacm
Version 2010-09-02
Source nacm line 142

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

nacm-user-name-type

Summary

Name nacm-user-name-type
Type string
  
 
General Purpose User Name string.

Details

Module nacm
Version 2010-09-02
Source nacm line 124

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-key-type

Summary

Name name-key-type
Type string
  
 
String type with at least 1 and up to 255 of the specified
characters.

Details

Module ieee802-dot1q-cfm-types
Version 2019-09-30
Source ieee802-dot1q-cfm-types line 692

name-string

Summary

Name name-string
Type string
  
 
Used where a string is needed which has a maximum length of
64 characters and a minimum length of 1 character.

Details

Module bbf-yang-types
Version 2019-10-21
Source bbf-yang-types line 118

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 2018-08-10
Source ieee802-dot1q-types line 89

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 2018-03-07
Source ieee802-dot1q-types line 53

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 2020-03-06
Source yumaworks-types line 65

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 276

narrow-metric

Summary

Name narrow-metric
Type uint8
  
 
This type defines ISIS narrow metric.

Details

Module openconfig-isis-types
Version 2020-06-30
Source openconfig-isis-types line 265

nbr-state-type

Summary

Name nbr-state-type
Type enumeration
  
 
OSPF neighbor state type.

Details

Module org-openroadm-ospf
Version 2020-05-29
Source org-openroadm-ospf line 331

NcAccessControlType

Summary

Name NcAccessControlType
Type enumeration
  
 
NCX System access control mode.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 160

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 2019-11-29
Source yuma-types line 195

NcIndex

Summary

Name NcIndex
Type uint32
  
 
Non-negative index value

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 238

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 2019-11-29
Source yuma-types line 267

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 2019-11-29
Source yuma-types line 245

NcPathSpec

Summary

Name NcPathSpec
Type string
  
 
A string which specifies a directory name.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 304

NcPortNumber

Summary

Name NcPortNumber
Type uint32
  
 
Transport layer port number.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 231

NcxFileName

Summary

Name NcxFileName
Type string
  
 
General Purpose NCX File Name string.
The first character can be a letter, digit, or
underscore character. The rest of the characters can be
printable characters except the following characters:

   * space ( )             ASCII 32
   * double quote          ASCII 34
   * ampersand (&)         ASCII 38
   * comma (,)             ASCII 44
   * forward slash (/)     ASCII 47
   * less-than sign (<)    ASCII 60
   * question mark (?)     ASCII 63
   * backslash (\)        ASCII 92
   * left curly brace ({)  ASCII 123
   * vertical bar (|)      ASCII 124

The allowed characters are not special to the server but many
of them would be interpreted as special characters by other
programs. Use such characters with extreme caution.

Details

Module yumaworks-types
Version 2020-03-06
Source yumaworks-types line 329

NcxIdentifier

Summary

Name NcxIdentifier
Type union
  
 
Union of all the Identifier types.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 110

NcxLineLength

Summary

Name NcxLineLength
Type uint32
  
 
Requested Maximum Line Length

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 134

NcxName

Summary

Name NcxName
Type string
  
 
General Purpose NCX Name string.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 91

NcxQName

Summary

Name NcxQName
Type string
  
 
Qualified Name:
 module-name:NcxName OR owner-name:NcxName.

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 99

NcxRpcType

Summary

Name NcxRpcType
Type enumeration
  
 
NCX RPC Type Classifications

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 182

NcxSessionId

Summary

Name NcxSessionId
Type uint32
  
 
NCX Session ID number

Details

Module yuma-types
Version 2019-11-29
Source yuma-types line 127

near-end-test-groups

Summary

Name near-end-test-groups
Type bits
  
 
A set of bits representing each of the near end test groups.

Details

Module bbf-fast
Submodule bbf-fast-update-test-body
Version 2020-01-17
Source bbf-fast-update-test-body line 133

neg-mode

Summary

Name neg-mode
Type enumeration
  
 
Defining a type of the negotiation mode

Details

Module ietf-l2vpn-ntw
Version 2020-05-26
Source ietf-l2vpn-ntw line 355

neg-mode

Summary

Name neg-mode
Type enumeration
  
 
Defining a type of the negotiation mode

Details

Module ietf-sdwan-svc
Version 2019-06-06
Source ietf-sdwan-svc line 49

neg-mode

Summary

Name neg-mode
Type enumeration
  
 
Defining a type of the negotiation mode

Details

Module ietf-l2vpn-svc
Version 2018-04-03
Source ietf-l2vpn-svc line 253

neg-mode

Summary

Name neg-mode
Type enumeration
  
 
Defines the type of negotiation mode.

Details

Module ietf-l2vpn-svc
Version 2018-10-09
Source ietf-l2vpn-svc line 262

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 2018-04-16
Source ietf-pim-base line 218

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-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 122

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module openconfig-if-ip
Version 2019-01-08
Source openconfig-if-ip line 141

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module ietf-ip
Version 2018-02-22
Source ietf-ip line 121

neighbor-origin

Summary

Name neighbor-origin
Type enumeration
  
 
The origin of a neighbor entry.

Details

Module org-openroadm-ip
Version 2020-05-29
Source org-openroadm-ip line 134

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 2020-06-30
Source openconfig-isis-types line 313

netconf-datastore-type

Summary

Name netconf-datastore-type
Type enumeration
  
 
Enumeration of possible NETCONF datastore types.

Details

Module ietf-netconf-monitoring
Version 2010-06-22
Reference RFC 4741: NETCONF Configuration Protocol
Source ietf-netconf-monitoring line 54

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 52

network-type

Summary

Name network-type
Type enumeration

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 211

new-master-reason-type

Summary

Name new-master-reason-type
Type enumeration
  
 
Indicates why the virtual router has transitioned to
master state.

Details

Module ietf-vrrp
Version 2018-03-13
Source ietf-vrrp line 97

nexthop-lb-weight-definition

Summary

Name nexthop-lb-weight-definition
Type uint8
  
 
Nexthop-lb-weight is used for load-balancing.
Each list member SHOULD 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 sum of 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.
Note that the weight of 0 is special because of
historical reasons.  It's typically used in
hardware devices to signify ECMP.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 644

nexthop-preference-definition

Summary

Name nexthop-preference-definition
Type uint8
  
 
Nexthop-preference is used for protection schemes.
It is an integer value between 1 and 99.  Lower
values are 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 the I2RS client should select N
nexthops and download them.  As for how to select
the nexthops, this is left to the implementations.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 628

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 2018-09-13
Source ietf-i2rs-rib line 666

nexthop-state-definition

Summary

Name nexthop-state-definition
Type identityref
  
 
Nexthop state definition.

Details

Module ietf-i2rs-rib
Version 2018-09-13
Source ietf-i2rs-rib line 548

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-flag-type

Summary

Name node-flag-type
Type identityref
  
 
Node flag attributes

Details

Module ietf-l3-unicast-topology
Version 2018-02-26
Source ietf-l3-unicast-topology line 90

node-id-profile-ref

Summary

Name node-id-profile-ref
Type leafref
  
 
Used to reference a node-id profile.

Details

Module bbf-ghn
Submodule bbf-ghn-node-profiles
Version 2018-07-13
Source bbf-ghn-node-profiles line 89

node-id-type

Summary

Name node-id-type
Type string
  
 
Globally unique identifier for a device.

Details

Module org-openroadm-common-node-types
Version 2019-11-29
Source org-openroadm-common-node-types line 55

node-ref

Summary

Name node-ref
Type instance-identifier
  
 
A reference to a node in topology

Details

Module ietf-dc-fabric-types
Version 2019-02-25
Source ietf-dc-fabric-types line 258

node-ref

Summary

Name node-ref
Type instance-identifier
  
 
A reference to a node in topology

Details

Module ietf-dc-fabric-types
Version 2018-11-08
Source ietf-dc-fabric-types line 217

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-types

Summary

Name node-types
Type enumeration
  
 
Identifier for node type
1. rdm for ROADM
2. xpdr for Transponder, Regen
3. ila for in-line amplifier
4. extplug for external pluggable

Details

Module org-openroadm-device-types
Version 2019-11-29
Source org-openroadm-device-types line 51

noise-margin-profile-ref

Summary

Name noise-margin-profile-ref
Type leafref
  
 
Used to reference a noise margin profile.

Details

Module bbf-fast
Submodule bbf-fast-quality-profiles
Version 2020-01-17
Source bbf-fast-quality-profiles line 137

non-rpc-related-notification-type

Summary

Name non-rpc-related-notification-type
Type enumeration
  
 
Defines notification types for non rpc related notifications.

Details

Module org-openroadm-controller-customization
Version 2020-05-29
Source org-openroadm-controller-customization line 143

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-events

Summary

Name notification-events
Type enumeration
  
 
Define possible notification events.

Details

Module org-openroadm-controller-customization
Version 2020-05-29
Source org-openroadm-controller-customization line 60

notification-type

Summary

Name notification-type
Type string
  
 
The name of a notification within a YANG module.

Details

Module ietf-notification-messages
Version 2019-10-10
Reference RFC-7950 Section 7.16
Source ietf-notification-messages line 192

nssa-translator-state-type

Summary

Name nssa-translator-state-type
Type enumeration
  
 
OSPF NSSA translator state type.

Details

Module org-openroadm-ospf
Version 2020-05-29
Source org-openroadm-ospf line 461

num-traffic-class-type

Summary

Name num-traffic-class-type
Type uint8
  
 
The number of traffic classes supported or participating in a
particular feature. There are between 1 and 8 supported traffic
classes defined by IEEE Std 802.1Q.

Details

Module ieee802-dot1q-types
Version 2018-08-10
Source ieee802-dot1q-types line 117

number

Summary

Name number
Type string
  
 
A generic representation of a number. This type does not make any assumption
about the precision to reach (simple, double etc., decimal32, 64) on the target
computer.

The number format is a string, so the implementation is expected to have parsing
options to convert this value into an appropriate format on the system. For
example, we know that Python is flexible enough to convert such a string into a
float number.

Examples of numbers that can be represented with this type:
-1, 2, 0, +4.5e4, -.5e4, -1.2e-5, 0.34, -5.6e-4 - 16e3j

We want to use this generic representation of a number to express any physical
body without the need for specifying number limit representation (such as
fraction-digit in decimal64 types). This way we can reuse a 'mass' to express
the 'mass of Sun' or a 'mass of a proton' by keeping the same fundamental
unit.

NOTE: For Python users, spaces are allowed in this pattern to make a clear
      distinction between the real and the imaginary parts. complex() does not
      accept -5.6e-4 - 16e3j as valid format, but prefers -5.6e-4-16e3j. Spaces
      need to be replaced first.

Details

Module ieee1906-dot1-function
Version 2020-07-07
Source ieee1906-dot1-function line 298

number-of-radio-amateur-mask

Summary

Name number-of-radio-amateur-mask
Type uint8
  
 
Number of radio-amateur masks defined.

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.8.5.5
Source bbf-ghn-types line 442

number-of-sub-carrier-mask

Summary

Name number-of-sub-carrier-mask
Type uint8
  
 
Number of sub-carrier masks defined

Details

Module bbf-ghn
Submodule bbf-ghn-types
Version 2018-07-13
Reference ITU-T G.9961 clause 8.8.5.5.
Source bbf-ghn-types line 431

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 222

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 206

ObjViewType

Summary

Name ObjViewType
Type enumeration
  
 
Requested view format for objects.

Details

Module yangdump-pro
Version 2019-09-22
Source yangdump-pro line 320

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

onu-id

Summary

Name onu-id
Type uint32
  
 
A type meant for ONU-IDs.

Details

Module bbf-xpon-types
Version 2019-02-25
Source bbf-xpon-types line 414

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

openroadm-link-type

Summary

Name openroadm-link-type
Type enumeration

Details

Module org-openroadm-network-types
Version 2020-05-29
Source org-openroadm-network-types line 195

openroadm-node-connection-status

Summary

Name openroadm-node-connection-status
Type enumeration

Details

Module org-openroadm-network-types
Version 2020-05-29
Source org-openroadm-network-types line 221

openroadm-node-type

Summary

Name openroadm-node-type
Type enumeration

Details

Module org-openroadm-network-types
Version 2020-05-29
Source org-openroadm-network-types line 107

openroadm-tp-type

Summary

Name openroadm-tp-type
Type enumeration

Details

Module org-openroadm-network-types
Version 2020-05-29
Source org-openroadm-network-types line 142

openroadm-version-type

Summary

Name openroadm-version-type
Type enumeration
  
 
OpenROADM version enum type

Details

Module org-openroadm-common-types
Version 2020-05-29
Source org-openroadm-common-types line 156

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 2018-03-13
Reference RFC 4268: Entity State MIB - EntityOperState
Source ietf-hardware line 122

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 2018-05-17
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 2018-08-11
Reference ITU-T G.698.2 (11/2009) Section 5.3
Source ietf-flexi-grid-ted line 63

operational-state

Summary

Name operational-state
Type enumeration
  
 
Operational state of an interface.

Details

Module ieee802-ethernet-link-oam
Version 2019-06-21
Reference IETF 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 236

operational-state-type

Summary

Name operational-state-type
Type enumeration
  
 
operational-state-type

Details

Module ietf-l2vpn
Version 2019-05-28
Source ietf-l2vpn line 400

operational-type

Summary

Name operational-type
Type enumeration
  
 
This is an attribute used to determine the
operational status of a particular element.

Details

Module ietf-l2vpn-ntw
Version 2020-05-26
Source ietf-l2vpn-ntw line 292

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 the lower-port is specified
and the upper-port is not specified.  The operator
therefore further qualifies the lower-port only.

Details

Module ietf-packet-fields
Version 2019-03-04
Source ietf-packet-fields line 71

operator

Summary

Name operator
Type bits
  
 
Specifies how to apply the defined bitmask.
'any' and 'match' bits must not be set simultaneously.

Details

Module ietf-dots-data-channel
Version 2020-05-28
Source ietf-dots-data-channel line 103

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 2018-11-06
Source ietf-packet-fields line 69

operator-state

Summary

Name operator-state
Type union
  
 
Operator states on an alarm.  The 'closed' state indicates
that an operator considers the alarm being resolved.  This is
separate from the alarm's 'is-cleared' leaf.

Details

Module ietf-alarms
Version 2019-09-11
Source ietf-alarms line 443

opt-if-och-tca-types

Summary

Name opt-if-och-tca-types
Type enumeration
  
 
The different types of TCA's

Details

Module draft-ietf-ccamp-dwdm-if-param-yang-02
Version 2019-11-04
Source draft-ietf-ccamp-dwdm-if-param-yang-02 line 79

optic-types

Summary

Name optic-types
Type enumeration

Details

Module org-openroadm-common-equipment-types
Version 2019-11-29
Source org-openroadm-common-equipment-types line 51

optical-control-mode

Summary

Name optical-control-mode
Type enumeration
  
 
Optical Control Mode: identifies specific algorithm related to power management and general optical control.

Details

Module org-openroadm-common-link-types
Version 2019-11-29
Reference openroadm.org: Open ROADM MSA Specification.
Source org-openroadm-common-link-types line 78

optional-header

Summary

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

Details

Module ietf-notification-messages
Version 2019-10-10
Source ietf-notification-messages line 175

optional-notification-header

Summary

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

Details

Module ietf-notification-messages
Version 2019-10-10
Source ietf-notification-messages line 184

opucn-trib-slot-def

Summary

Name opucn-trib-slot-def
Type string
  
 
OPUCn trib slot in the form of 'A.B' with
A = 1..n
B = 1..20

Details

Module org-openroadm-otn-common-types
Version 2020-03-27
Source org-openroadm-otn-common-types line 330

origin-ref

Summary

Name origin-ref
Type identityref
  
 
An origin identity reference.

Details

Module ietf-origin
Version 2018-02-14
Source ietf-origin line 125

origin-ref

Summary

Name origin-ref
Type identityref
  
 
An origin identity reference.

Details

Module ietf-origin
Version 2018-01-11
Source ietf-origin line 125

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 2018-11-21
Source openconfig-ospf-types line 62

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 2018-11-21
Source openconfig-ospf-types line 73

otn-interface-enum

Summary

Name otn-interface-enum
Type enumeration
  
 
Enumeration type for otn interface

Details

Module org-openroadm-otn-common
Version 2020-03-27
Source org-openroadm-otn-common line 90

packet-type

Summary

Name packet-type
Type enumeration
  
 
OSPF packet type.

Details

Module org-openroadm-ospf
Version 2020-05-29
Source org-openroadm-ospf line 429

pae-access-status

Summary

Name pae-access-status
Type enumeration
  
 
Indicates the transmitter's Controlled Port operational status
and current level of access resulting from authentication and
the consequent authorization controls applied by that port's
clients.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 10.4, Clause 12.5
Source ieee802-dot1x-types line 135

pae-access-status

Summary

Name pae-access-status
Type enumeration
  
 
Indicates the transmitter's Controlled Port operational status
      and current level of access resulting from authentication and
      the consequent authorization controls applied by that port's
      clients.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 10.4, Clause 12.5
Source ieee802-dot1x-types line 1

pae-auth-data

Summary

Name pae-auth-data
Type string
  
 
Authorization data associated with the CAK.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 9.16
Source ieee802-dot1x-types line 215

pae-auth-data

Summary

Name pae-auth-data
Type string
  
 
Authorization data associated with the CAK.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 9.16
Source ieee802-dot1x-types line 1

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-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 9.3.1, Clause 6.2
Source ieee802-dot1x-types line 190

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-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 9.3.1, Clause 6.2
Source ieee802-dot1x-types line 1

pae-if-index

Summary

Name pae-if-index
Type int32
  
 
The interface index value represented by this interface.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Source ieee802-dot1x-types line 235

pae-if-index

Summary

Name pae-if-index
Type int32
  
 
The interface index value represented by this interface.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Source ieee802-dot1x-types line 1

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 authenticator's key
management domain.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE Clause 12.6
Source ieee802-dot1x-types line 203

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 authenticator's key
      management domain.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE Clause 12.6
Source ieee802-dot1x-types line 1

pae-nid

Summary

Name pae-nid
Type string
  
 
Network Identity, which is a UTF-8 string identifying a
network or network service.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 3, Clause 10.1, Clause 12.6
Source ieee802-dot1x-types line 49

pae-nid

Summary

Name pae-nid
Type string
  
 
Network Identity, which is a UTF-8 string identifying a
      network or network service.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 3, Clause 10.1, Clause 12.6
Source ieee802-dot1x-types line 1

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 the NID. Any set of these
combinations can be supported.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 10.1, Clause 11.12.3
Source ieee802-dot1x-types line 83

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 the NID. Any set of these
      combinations can be supported.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 10.1, Clause 11.12.3
Source ieee802-dot1x-types line 1

pae-session-id

Summary

Name pae-session-id
Type string
  
 
Session Identifier, which is a UTF-8 string, uniquely
identifying the session within the context of the PAE's
system.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 12.5.1
Source ieee802-dot1x-types line 71

pae-session-id

Summary

Name pae-session-id
Type string
  
 
Session Identifier, which is a UTF-8 string, uniquely
      identifying the session within the context of the PAE's
      system.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 12.5.1
Source ieee802-dot1x-types line 1

pae-session-user-name

Summary

Name pae-session-user-name
Type string
  
 
Session user name, which is a UTF-8 string, representing the
identity of the peer Supplicant.

Details

Module ieee802-dot1x-types
Version 2019-05-28
Reference IEEE 802.1X-2020 Clause 12.5.1
Source ieee802-dot1x-types line 60

pae-session-user-name

Summary

Name pae-session-user-name
Type string
  
 
Session user name, which is a UTF-8 string, representing the
      identity of the peer Supplicant.

Details

Module ieee802-dot1x-types
Version 2020-02-18
Reference IEEE 802.1X-2020 Clause 12.5.1
Source ieee802-dot1x-types line 1

password-type

Summary

Name password-type
Type string
  
 
The password for this entry. This shouldn't be in clear text
The Password must contain at least 2 characters from
each of the following groups:
a) Lower case alphabetic (a-z)
b) Upper case alphabetic (A-Z)
c) Numeric 0-9
d) Special characters Allowed !$%^()[]_-~{}.+
Password must not contain Username.

Details

Module org-openroadm-user-mgmt
Version 2019-11-29
Source org-openroadm-user-mgmt line 76

path-attribute-flags

Summary

Name path-attribute-flags
Type union
  
 
Path attributes flags type.

Details

Module ietf-te-types
Version 2020-06-10
Source ietf-te-types line 120

pattern-type

Summary

Name pattern-type
Type enumeration
  
 
The match pattern of the user-defined application rule. If the keyword is a fixed string, the pattern type is Plain. If the keyword is not a fixed string, the pattern type is Regular Expression.

Details

Module ietf-policy-object
Version 2018-10-12
Source ietf-policy-object line 305

pause-fc-direction-type

Summary

Name pause-fc-direction-type
Type enumeration
  
 
Used to represent the configured, negotiated, or actual 
PAUSE frame-based flow control setting.

Details

Module ieee802-ethernet-interface
Version 2019-06-21
Reference IEEE Std 802.3.1, dot3PauseAdminMode and dot3PauseOperMode
Source ieee802-ethernet-interface line 77

payload-type-def

Summary

Name payload-type-def
Type string
  
 
Common type definition for odu payload-type

Details

Module org-openroadm-otn-common-types
Version 2020-03-27
Source org-openroadm-otn-common-types line 321

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 2019-05-28
Source ietf-l2vpn line 364

pbit

Summary

Name pbit
Type uint8
  
 
Priority Code Point. PCP is a 3-bit field that refers to the
class of service applied to a 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 bbf-dot1q-types
Version 2018-07-13
Reference IEEE 802.1Q-2014: Virtual Bridged Local Area Networks
Source bbf-dot1q-types line 183

pbit-list

Summary

Name pbit-list
Type string
  
 
A set of p-bit values.
A list of PBIT bits values, or non overlapping PBIT bits value
ranges, in ascending order, between 0 and 7.

Example: 0,2-4,7

Details

Module bbf-dot1q-types
Version 2018-07-13
Source bbf-dot1q-types line 197

pcc-capabilities

Summary

Name pcc-capabilities
Type bits
  
 
Path Computation Capabilities.

Details

Module ted
Version 2014-10-27
Reference RFC 5088, draft-ietf-pce-disco-protoc-isis-07.txt OSPF/ISIS Protocol Extensions for Path Computation Element (PCE) Discovery.
Source ted line 152

pcp-selection-type

Summary

Name pcp-selection-type
Type enumeration
  
 
Priority Code Point selection types.

Details

Module ieee802-dot1q-types
Version 2018-08-10
Reference 12.6.2.5.3 of IEEE Std 802.1Q-2018 6.9.3 of IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 181

pcp-selection-type

Summary

Name pcp-selection-type
Type enumeration
  
 
Priority Code Point selection types.

Details

Module ieee802-dot1q-types
Version 2018-03-07
Reference 12.6.2.5.3 of IEEE Std 802.1Q-2018 6.9.3 of IEEE Std 802.1Q-2018
Source ieee802-dot1q-types line 136

peer-state

Summary

Name peer-state
Type enumeration
  
 
TRILL neighbour state type.

Details

Module ietf-trill
Version 2015-12-21
Source ietf-trill line 65

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 2020-06-30
Source openconfig-bgp-types line 632

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 2018-05-17
Source ietf-pmip-qos line 117

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 2018-05-17
Source ietf-pmip-qos line 125

per-sub-carrier-group-int16-tuple

Summary

Name per-sub-carrier-group-int16-tuple
Type binary
  
 
A binary type where a tuple of octet pairs represent data
belonging to a sub-carrier group. The first tuple
represents sub-carrier group 0 and the last tuple represents
sub-carrier group 511. In each pair of octets in the tuple, the
most significant byte is loaded first. The order of the tuple
is determined by the node to which this type is associated.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 149

per-sub-carrier-group-uint16

Summary

Name per-sub-carrier-group-uint16
Type binary
  
 
A binary type where each pair of octets represents data
belonging to a sub-carrier group. The first two octets
represents sub-carrier group 0 and the last two represents
sub-carrier group 511. In each pair of octets, the most
significant byte is loaded first.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 137

per-sub-carrier-group-uint16

Summary

Name per-sub-carrier-group-uint16
Type binary
  
 
A binary type where each pair of octets represents data
belonging to a sub-carrier. The first two octets represents
sub-carrier 0. In each pair of octets, the most significant
byte is loaded first.

Details

Module bbf-fast
Submodule bbf-fast-line-status-body
Version 2020-01-17
Source bbf-fast-line-status-body line 236

per-sub-carrier-group-uint16-tuple

Summary

Name per-sub-carrier-group-uint16-tuple
Type binary
  
 
A binary type where a tuple of octet pairs represent data
belonging to a sub-carrier group. The first tuple
represents sub-carrier group 0 and the last tuple represents
sub-carrier group 511. In each pair of octets in the tuple, the
most significant byte is loaded first. The order of the tuple
is determined by the node to which this type is associated.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 162

per-sub-carrier-group-uint8

Summary

Name per-sub-carrier-group-uint8
Type binary
  
 
A binary type where each octet represents data belonging to
a sub-carrier group. The first octet represents sub-carrier
group 0 and the last represents sub-carrier group 511.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 127

per-sub-carrier-group-uint8

Summary

Name per-sub-carrier-group-uint8
Type binary
  
 
A binary type where each octet represents data belonging to
a sub-carrier group. The first octet represents sub-carrier
group 0.

Details

Module bbf-fast
Submodule bbf-fast-line-status-body
Version 2020-01-17
Source bbf-fast-line-status-body line 228

per-sub-carrier-int32-tuple

Summary

Name per-sub-carrier-int32-tuple
Type binary
  
 
A binary type where each group of 8 octets represents a tuple.
A tuple consists of two 4-octet groups and represents data
belonging to a sub-carrier. The first tuple represents
sub-carrier group 0 and the last tuple represents sub-carrier
group (length/8 - 1). In each 4-octet group in the
tuple, the most significant byte is loaded first. The order of
the tuples is determined by the node to which this type is
associated.

Details

Module bbf-selt
Submodule bbf-selt-pmd-measurement-parameter-body
Version 2019-06-11
Source bbf-selt-pmd-measurement-parameter-body line 155

per-sub-carrier-nibble

Summary

Name per-sub-carrier-nibble
Type binary
  
 
A binary type where each nibble represents data belonging to
a sub-carrier. The first nibble represents sub-carrier 0 and
the last represents sub-carrier 8191.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 175

per-sub-carrier-nibble

Summary

Name per-sub-carrier-nibble
Type binary
  
 
A binary type where each nibble represents data belonging to
a sub-carrier. The first nibble represents sub-carrier 0 and
the last represents sub-carrier 4095.

Details

Module bbf-fast
Submodule bbf-fast-line-status-body
Version 2020-01-17
Source bbf-fast-line-status-body line 208

per-sub-carrier-uint16

Summary

Name per-sub-carrier-uint16
Type binary
  
 
A binary type where each pair of octets represents data
belonging to a sub-carrier group. The first pair represents
sub-carrier group 0 and the last represents sub-carrier
group (length/2 - 1).

Details

Module bbf-selt
Submodule bbf-selt-processing-derived-parameter-body
Version 2019-06-11
Source bbf-selt-processing-derived-parameter-body line 135

per-sub-carrier-uint16

Summary

Name per-sub-carrier-uint16
Type binary
  
 
A binary type where each pair of octets represents data
belonging to a sub-carrier. The first two octets represent
sub-carrier 0 and the last two represent sub-carrier 8191.
In each pair of octets, the most significant byte is loaded
first.

Details

Module bbf-vdsl
Submodule bbf-vdsl-xtu-sub-carrier-status-body
Version 2019-10-21
Source bbf-vdsl-xtu-sub-carrier-status-body line 185

per-sub-carrier-uint8

Summary

Name per-sub-carrier-uint8
Type binary
  
 
A binary type where each octet represents data belonging to
a sub-carrier group. The first octet represents sub-carrier
group 0 and the last octet represents the sub-carrier
group (length - 1).

Details

Module bbf-selt
Submodule bbf-selt-pmd-measurement-parameter-body
Version 2019-06-11
Source bbf-selt-pmd-measurement-parameter-body line 144

per-sub-carrier-uint8

Summary

Name per-sub-carrier-uint8
Type binary
  
 
A binary type where each octet represents data belonging to
a sub-carrier. The first octet represents sub-carrier 0 and
the last represents sub-carrier 4095.

Details

Module bbf-fast
Submodule bbf-fast-line-status-body
Version 2020-01-17
Source bbf-fast-line-status-body line 218

percent

Summary

Name percent
Type uint8
  
 
A percentage.

Details

Module bbf-yang-types
Version 2019-10-21
Source bbf-yang-types line 127

percent

Summary

Name percent
Type uint8
  
 
Percentage

Details

Module ietf-nat
Version 2019-01-10
Source ietf-nat line 76

percent

Summary

Name percent
Type decimal64
  
 
This value represents a percent.

Details

Module ieee1906-dot1-2015
Version 2016-12-20
Source ieee1906-dot1-2015 line 552

percent

Summary

Name percent
Type union
  
 
A 'classical' percentage is a number x such as 0 <= x <= 100

Details

Module ieee1906-dot1-math
Version 2020-07-07
Source ieee1906-dot1-math line 289

percent

Summary

Name percent
Type uint8
  
 
Percentage

Details

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

percentage

Summary

Name percentage
Type decimal64
  
 
Percentage

Details

Module ietf-stamp
Version 2019-10-20
Source ietf-stamp line 115

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module openconfig-types
Version 2019-04-16
Source openconfig-types line 86

percentage

Summary

Name percentage
Type uint8
  
 
Integer indicating a percentage value

Details

Module mpls-types
Version 2015-02-01
Source mpls-types line 55

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 uint8
  
 
Integer indicating a percentage value.

Details

Module ietf-routing-types
Version 2017-12-04
Source ietf-routing-types line 614

percentage

Summary

Name percentage
Type decimal64