ODVA Specification Mandatory Change List

Definition and Legend
This document tracks changes made in the specifications that are mandatory for products implementing the technologies.
ODVA publishes this list separately from the specifications in order to give developers and managers advanced noticeof changes that will impact the products for which they are responsible.
This document does not list any optional changes. For optional changes and enhancements, see the Revision page at the front of each specification volume.
Scope of Change
O: Optional: An optional feature/function
C: Conditional: An optional feature/function that is required under specific conditions, see specification
M: Mandatory: A feature/function that is required
If the Scope of Change differs between Descriptions of a single spec change, separate rows are shown.
Scope of Products Impacted
New: Products taking the conformance test the first time
Existing: Products that already have a valid DOC and are being updated with new featues, as defined in section 8 of the Conformance Policy (PUB00008)
The effective date is the date when the change will be enforced by conformance testing.
Specification volumes are referenced by number. The titles of the volumes can be found on a tab in this spreadsheet.
If there is a discrepancy between this spreadsheet and the specification, the latest released specification(s) will prevail.
The title of each page identifies the the publication cyle of the changes shown. There are two publication update cycles
each year, typically in April and November.
UpdatedApril 29, 2024

PUB00317_ODVA specification mandatory change list_R19

1/18

Volume Number
1
2
3
4
5
6
7A
7B
7C
8
9

Volume Title
The Common Industrial Protocol
EtherNet/IP Adaptation of CIP
DeviceNet Adaptation of CIP
ControlNet Adaptation of CIP
CIP Safety
CompoNet Adaptation of CIP
Integration of Modbus Devices into the CIP Architecture
Integration of HART Devices into the CIP Architecture
Integration of IO‐Link Devices into the CIP Architecture
CIP Security
CIP Motion

Edition at April 2024 (2024 PC 1) Publication
3.36
1.33
1.16
1.09
2.25
1.08
1.12
1.03
1.05
1.17
1.12

ODVA Specification Mandatory Change List
2024 PC 1

Topic

VolumeEditionDescription

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

Clarify options after General Status“Reply data too large” (0x11)

1

3.36

1. When a CIP target device returns status 0x11 (Reply data too large), a client should retry the request withalternate access methods, such as Message Router Send_Receive_Fragment service (preferred),
Get_Member service of the target object, or via connection opened with Large_Forward_Open. (Section 2‐ New and Existing
4.2)
2. A device supports only the Large_Forward_Open approach in such case will get an Advisory.

Parameter Object ‐ Get_Enum_String

1

3.36

The Enumerated Sring Number parameter of Get_Enum_String service was changed from USINT data type to
New and Existing
USINT for bit string data type, else using the Data Type of attribute 5. (Table 5A‐14.21)

C

Apr‐24

Apr‐24

Process Device Diag‐Profile Diag and Sim

1

3.36

1. Update and clarify some attributes of Process Device Diagnostics Object (Table 5B‐19.8).
2. Allow all diagnostics instances to be configurable. (Section 5B‐19.8, Table 5B‐19.26, Table 6‐43.13, Table 6‐ New and Existing
44.13, Table 6‐45.17, Table 6‐46.17, Table 6‐47.17)

C

Apr‐24

Apr‐24

New and ExistingC

Apr‐24

Apr‐24

NewC

Apr‐24

Apr‐24

Flow and Pressure Device Profiles‐ Units
and File Object

1

3.36

1. Clarify that File Object is optional for the Flow and Pressure Process Device Profiles. Add Predefined File
Object instance 0xCA for a device's Profile EDS File and Icon File. (Table 5A‐42.27, Table 6‐43.1 ‐ Table 6‐
47.1)
2. Limit the engineering units supported for each profile. (Section 6‐43.6.2.2.1, 6‐44.6.2.2.1, etc.)
3. Correct the conversion facor for 2E0Ehex US Beer Barrels. (Section D‐2.33)

MDAO and Device Profile update

9

1.12

MDAO updated to Revision 10

C

Apr‐24

Apr‐24ODVA Specification Mandatory Change List
2023 PC 2
PublishDate

Effective
Date

C

Nov‐23

Apr‐25Cipher suits required for a given profile applies to a device implementing that profile, no matter it is a Target
New and Exsitingor Originator. (Table 3‐5.4 and Table 3‐5.5)

C

Nov‐23

Nov‐23

1.33[IANA_Port_Admin] entry is required if a a device supports TCP/IP Interface Object's instance attribute 14(IANA Port Admin), otherwise not allowed. (Table 7‐7.1).

NewC

Nov‐23

Apr‐252

1.33

1. EtherNet/IP Usage Profiles was updated to allow a device support multliple usage profiles. (Table 11‐3.1).
2. The EtherNet/IP Capability Item in the ListIdentity response shall only set bits corresponding to theNewfeatures supported on the interface receiving the request, not all the interfaces supported by the device.
(Table 2‐4.5)

C

Nov‐23

Nov‐23

Modbus Serial Link Object Clarification

7A

1.12

1. Data Bits and Stop Bits of Modbus Serial Link Object instance attribute 3 shall be encoded as binary not
ASCII. (Table 5‐6.10)
2. Modbus Serial Link Object bumped to Revision 2. (Table 5‐6.1)

New and ExistingC

Nov‐23

Nov‐23

Identity object Protection Mode attribute

7C

1.05

Identity Object Protection Mode attribute 19 is now allowed for Virtual IO‐Link device. (Table 5‐1.1)

New and ExistingC

Nov‐23

Nov‐23

Description

Scope of Products Scope of
Impacted
ChangeTopicVolumeEdition

Expand States Protected by CIP Security

8

1.17

1. Changes to security objects containing CIP Security configuration shall only be accepted when sent over a
CIP Security connection even if the device is in the Factory Default state. (Section 4‐3.1.3)
New and Existing
2. Changes to security related objects without containing CIP Security configuration shall be made over a CIP
Security connection once the CIP Security Object in not in the Factory Default state. (Section 4‐3.1.3)

Update Originator Cipher Suite
Requirements

8

1.17

IANA Port Admin EDS Keyword

2

EthernetIP Usage Profile Updates

ODVA Specification Mandatory Change List
2023 PC 1

Topic

VolumeEditionDescription

Scope of Products Scope of
Impacted
Change1. Introduce Concurrent Connections functionality to the CIP specification (Section 3‐7).
2. Add new services and attributes to Connection Manager Object to handle Concurrent Connections, bumpthe object revision to 02 (Table 3‐5.1 and 3‐5.8).
3. Define new Connection Path rules for Concurrent Connections (Section 3‐5.5.1.10, Appendix C‐1.4.3.6.2). New
4. Describe new CIP Routing behavior for Concurrent Connections (Section 10‐2.2).
5. Add new entries to [Connection Manager] section in EDS file (Table 7‐3.49).
6. Concurrent Connections packets use CRC to protect the integrity of packets (Appendix C‐7).

PublishDate

Effective
Date

C

Apr‐23

Apr‐23C

Apr‐23

Apr‐23C

Apr‐23

Apr‐23C

Apr‐23

Apr‐23

Concurrent Connections

1

3.34

Device Type Revision

1

3.34

Supporting Objects for Process Device
Profiles1

3.34

Flow Process Device Profile

1

3.34

Requirements for Process Device Profiles

1

3.34

Specify requirements for Process Device Profiles (Section 6‐2.5).

NewC

Apr‐23

Apr‐23C

Apr‐23

Apr‐23

New and ExistingC

Apr‐23

Apr‐23

New and ExistingM

Apr‐23

Apr‐23

New and ExistingC

Apr‐23

Nov‐24

1. Introduce revision concept to Device Profile definition (Table 6‐2.2).
2. Add a Supported Device Type Revision attribute 38 to Identity Object and bump its revision to 03 (Table 5ANew
2.1 and 5A‐2.3)
3. Add new entry to [Identity Object] section in EDS file.
1. Add Process Measurement Value Object and Process Totalized Value Object for process field devices(Section 5B‐21 and 5B‐22)
New
2. Add new object class sections for these objects in EZ‐EDS (Table 7‐3.4).
Add three new Process Device Profiles: Coriolis Flow Device, Electromagnetic Flow Device and Vortex FlowNew
Device (Table 6‐5.1 and 6‐5.2).

Pressure Process Device Profile

1

3.34

Add two new Process Device Profiles: Scaled Pressure Device and Standard Pressure Device (Table 6‐5.1 andNew
6‐5.2)

Process Device Diagnostics Simulation
Addition1

3.34

Update Process Device Diagnostics Object Revision to 4 (Table 5B‐19.5)
Devices not implementing LLDP Reception are not allowed to support LLDP Data Store attribute 4 and Last
Change attribute 5 of LLDP Management Object.
1. Clarify that data in LLDP frames is sent in big‐endian format. Deprecate the CIP Identification TLV with
subtype 1 and create a new CIP Identification TLV with subtype 9 that is clearly specified as big endian(Section 9‐8.3).
2. Make it possible for devices to support both the LLDP Date Table Object and SNMP at the same time
(Table 5‐15.3).

LLDP Reception Clarification

2

1.32

LLDP Clarifications

2

1.32

PRP‐HSR Updates

2

1.32

Add additional attribute 21 necessary to conform to the latest IEC 62439‐3 standard for HSR.

New and ExistingC

Apr‐23

Nov‐23

Improve error reporting

7C

1.04

Use object specific general status code to return IO‐Link command errors (Table 5‐3.4, 5‐3.8 and 5‐3.10).

NewC

Apr‐23

Apr‐23

Support access to Index 0

7C

1.04

Use 0x10000 as the instance value for accessing Index 0 in IO‐Link Service Parameter Object (Section 5‐3).

New and ExistingC

Apr‐23

Apr‐23OctetStringT conversion

7C

1.04

Change the conversion of an OctetStringT to an array of USINT instead of previous SHORT_STRING (Table C‐
New and Existing
3.1)

C

Apr‐23

Apr‐23ArrayT conversion

7C

1.04

Change the Conversion Type value of an ArrayT to allow for 2 byte conversion types. (Table C‐3.1).

NewC

Apr‐23

Apr‐23

RecordT conversion type

7C

1.04

Add a conversion type for the IO‐Link RecordT data type(Table C‐3.1).

New and ExistingC

Apr‐23

Apr‐23

TimeT STIME conversion

7C

1.04

The convertion between TimeT to STIME needs to use new constant (Appendix C‐3.1.1)

New and ExistingC

Apr‐23

Apr‐23

IO‐Link Service Parameter object Device
State conflict extended status

7C

1.04

Expand PSK USage Field

8

1.16

Member Services for PSK Attribute

8

1.16

Cipher Suite Requirements

8

1.16

Add Device State Conflict (0x10) and new Extended Status codes to IO‐Link Service Parameter object service
New
responses (Table 5‐3.3 ‐ 5‐3.12).
EtherNet/IP Security Object Revision bumps to 8, add a new Required PSK Usages Supported Class attribute
New and Existing(Table 5‐4.2 and section 5‐4.3.2).
Member services are required for Resource‐Constrained CIP Security Profiles, optional for others (Table 5‐
New and Existing
4.6).

C

Apr‐23

Apr‐23C

Apr‐23

Apr‐24C

Apr‐23

Nov‐24Make several previously required cipher suites to recommended (Table 3‐5.4 and 3‐5.5).

C

Apr‐23

Apr‐23

New and ExistingODVA Specification Mandatory Change List
2023 PC 1

PSK Usage Clarification

8

1.16

Certificate handling

8

1.16

Consumer Activity Monitor Usage
Clarification

5

2.25

Tst52 Split

5

2.25

Disallow multiple PSKs from being set that re‐use a given identity value (Section 5‐4.4.5).

New and Existing

CIP Security devices are required to support at least two dynamic instances of the Certificate Management
Object (Section 5‐5.1.1). CMO Revision becomes 2, Class attribute 2 and 3 are required now.
New and Existing
Devices that already passed the conformance test and only support one dynamic instance may continue
using just one dynamic instance. This will degrade the interoperability and robustness in systems, but it isrecognized that devices might not have the resources to implement this change.
Add text in FRS78 indicating that the Consumer Activity Monitor timer should be reset to the remaining data
New and Existing
age based on the last reception time stamp (Section 2‐1.8.3.1, F‐3.8.5, F‐3.9.2.3 ).
Split TST52 into four tests of TST132, TST133, TST134 and TST135 (Appendix F‐2.6.2, Table F‐3.11.5.2.1, F‐New
3.11.5.2.4, F‐5.1).

C

Apr‐23

Nov‐23C

Apr‐23

Nov‐23C

Apr‐23

Apr‐23C

Apr‐23

Apr‐23ODVA Specification Mandatory Change List
2022 PC 2

Topic

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

New

M

Nov‐22

Nov‐22C

Nov‐22

Apr‐23

New and ExistingC

Nov‐22

Apr‐24

New

M

Nov‐22

Nov‐22

VolumeEditionDescription

Enumeration for String Data Types

1

3.33

Any Param entry whose type is string (STRING, STRING2 or SHORT_STRING) can also be enumerated using
the Enum Keyword in addition to integer and bit string. (Section 7‐3.6.6.2 and Table 7‐3.26)

LLDP SNMP MIB

2

1.31

Added requirements and reference for ODVA devices implementing the SNMP LLDP MIB. (Section 9‐8.1)
New and Existing(https://www.odva.org/subscriptions‐services/additional‐tools/request‐lldp‐management‐information‐base)

Safety Reset Type2 Clarification

5

2.24

TST130 Adding Running Conditions
Correct Reset Factory settings command
code

5

2.24

7C

1.3

Changed Soft‐set MacID to Soft‐set NodeID, Soft‐set Baud Rate to Soft‐set Communication Link Parameters(Table 5‐4.21)
Added running conditions for TST130. (Appendix F‐5.1)
Identity Object Type 1 Reset shall cause IO‐Link Master issue Restore factory setting command 0x82 (not0x81) to the IO‐Link Device. (Table 5‐2.6)

New and ExistingM

Nov‐22

Nov‐22

NewC

Nov‐22

Apr‐24Ingress Egress Object

8

1.15

1. Added a new CIP Security Profile: Device‐Based Firewall Profile (Table 8‐1.1 and Section 8‐2.1)
2. Added new Ingress Egress Object which is required by Device‐Based Firewall Profile(Section 5‐9)
3. Added Available Originator Cipher Suites and Allowed Originator Cipher Suites attributes to EtherNet/IP
Security Object (Table 5‐4.3)

Correct EIPSO Reset Condition

8

1.15

EtherNet/IP Security Object Reset service will be accepted over any connection up until the CIP Security
Object’s state attribute transitions to Configured, at which point this Reset will only be accepted over a CIP
Security connection. (Table 5‐4.5.1)

New and ExistingM

Nov‐22

Nov‐22Make Wildcards Optional for SAN with
Hostname8

1.15

IP Address must be supported in SAN, Hostname and URI support in SAN are optional. (Section 5‐4.4.17)

New and ExistingM

Nov‐22

Nov‐22ODVA Specification Mandatory Change List
2022 PC 1

Topic

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

Added an Optional Product Identity Certificate attribute 39 (Table 5A‐2.3) and a Conditional
Certificate_Challenge service (Table 5A‐2.18) to Identity Object.

New and ExistingC

Apr‐22

Apr‐22

3.32

Clarify Register Object Direction and Size attributes are NV attributes, also clarify the Set are Optional for
attribute 2‐4. (Table 5A‐2.2)

New and ExistingC

Apr‐22

Apr‐22

VolumeEdition

Product Authenticity Check

1

3.32

Register Object Data Access Rule
Clarification

1

Description

Improve LLDP alignment with IEEE
802.1AB‐2016

2

1.30

LLDP Specification was updated to align with IEEE 802.1AB‐2016:
1. For LLDP Enable attribute 1 of LLDP Management Object, on set of Global Enable Bit 0 from 1 to 0, allexisting table entries shall be removed. (Table 5‐15.4)
2. LLDP Management Object msgTxInterval attribute 2 valid range was changed. Last Change attribute 5
meaning was changed. (Table 5‐15.3)
3. The meaning of LLDP Data Table Object Last Change attribute 9 was changed. (Table 5‐16.3)
4. Added LLDP Link State Transition requirements (Section 9‐8.6)

New and ExistingC

Apr‐22

Apr‐22SAN Formatting Clarification

8

1.14

Clarify that only DNS Name, IP Address and Uniform Resource Identifier (URI) must be supported in Subject
New and Existing
Alternative Name (SAN) within CIP Security certificates. (Section 5‐5.7.1)

C

Apr‐22

Apr‐22

New and ExistingC

Apr‐22

Nov‐23

New and ExistingC

Apr‐22

Apr‐22

CRL Clarification

8

1.14

1. The EtherNet/IP Security Object Certificate Revocation List attribute 8 now can hold an Array of CRLs
rather than a single CRL and the object revision was bumped to 7. (Table 5‐4.3)
2. Clarify that a certificate may only be revoked by the Certificate Authority which originally signed it.
(Section 5‐4.4.8)
3. Two kinds of GAA Format: one for Revision 1‐6; another for Revision 7 and onward. (Table 5‐4.11)

Send Receive Fragment Requirement
Date

8

1.14

The requirement of supporting Send_Receive_Fragment service was extended to November 2022.

ODVA Specification Mandatory Change List
2021 PC 2

Topic

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

Clarify that Find_Next_object_Instance service is not supported at the instance level, even though theInstance ID value to use as the lower bound of the search is provided in the application path. (Appedix A‐
4.14)

New and ExistingC

Nov‐21

Nov‐21

3.31

CIP Security devices are required to allow certain authenticated requests while in Explicit and/or Implicit
Protection mode. (Section 5A‐2.3.1.16.1, Vol 8 section 5‐2)

New and ExistingC

Nov‐21

Nov‐211

3.31

1. Removed the summary text in Section 5A‐42.5.6 to eliminate the redundancy and conflicit to Table 5A‐
42.26.
2. Did the same change to previous revision of File Object which is listed in Appendix E‐2.5.6.

New and ExistingC

Nov‐21

Nov‐211

3.31

An attribute with Settable (Set) Access rule shall be accessed by at least one of the set services. (Section 4‐
4.1)

New and ExistingC

Nov‐21

Nov‐21

C

Nov‐21

Apr‐23

VolumeEditionDescription

Find Next Object Instance Service
Clarification

1

3.31

Clarify Protection Mode

1

File Object Download Transfer
Clarification
Set Access Rule Clarification 2021

Cipher Suite Changes

8

1.13

1. Require GCM‐based cipher suites be supported and change RSA‐based cipher from required to optional
for CIP Security endpoints . (Table 3‐5.4 Section 5‐4.4.6 and 5‐4.9)
2. EtherNet/IP Security Object Allowed Cipher Suites attribute 4 shall only allow cipher suites that support
New and Existing
confidentiality in the Factory Default state. PSK based cipher suites shall not be allowed by default. (Section
4‐4.4)

Conditional Support for Security Profiles
Configured

8

1.13

Support for Security Profiles Configured attribute 3 of CIP Security Object will be required starting from April
New
2022.

C

Nov‐21

Apr‐22C

Nov‐21

Nov‐21

Pull Model Profile

8

1.13

1. Added a new EtherNet/IP Pull Mode Profile for devices supporting Pull Model.(Table 1‐3.1)(Table 5‐3.5)
2. All CIP Security devices must support Push model and optionally support Pull model. For devices
New and Existingsupporting both mechanism, the Pull Model is the default mechanism for obtaining a certificate. (Section 4‐
3.4.1)PSK Usage Field

8

1.13

Added PSK Usage field to the Pre‐Shared Keys attribute 5 of EtherNet/IP Security Object which brings
EtherNet/IP Security Object to Revision 7. (Table 5‐4.2 and Table 5‐4.3)

New and ExistingC

Nov‐21

Apr‐23

SAN Update

8

1.13

Check Subject Alternative Name attribute 17 of EtherNet/IP Security Object is optional for device with
New and Existingoriginator funcationality. It must not be implemented by devices without originator capabilites. (Table 5‐4.3)

C

Nov‐21

Nov‐21Make Certificate Signing Request
Attributes (csrattrs) Optional

8

1.13

Requesting csrattrs to the EST server during configuration of Pull Model is changed from required tooptional. (Section 4‐3.4)

New and ExistingO

Nov‐21

Nov‐21Prevent DTLS Timeout Disable

8

1.13

C

Nov‐21

Apr‐23

LLDP Management Object Correction (published in PUB00346R0 in June 2021)

2

1.29

Removed the ability to disable DTLS timeouts. (Table 5‐4.3)
New and Existing
1. Definition correction to LLDP Enable attribute 1 for both LLDP Enable Array Length and LLDP Enable Array
fields.
New and Existing
2. Access Rule of MsgTxHold attribute 3 was changed from Get to Set.

M

Apr‐21

Apr‐21LLDP Date Extension

Electronic Key Segment for IO‐Link
Device

2

7C

1.29

1. LLDP enforcement date was extended from December 2021 to May 2022.
2. Clarify the LLDP implementation requirements: a device containing bridge(s) or implementing In‐Cabinet
Profile must support both LLDP transmission and reception; otherwise supporting LLDP transmission isrequired but LLDP reception support is optional. (Section 9‐8.1)

New and ExistingM

Nov‐21

May‐22

1.02

1. The Electronic Key Compatibility bit 7 is moved from Minor Revision byte to Major Revision byte. (Apendix
C‐2)
2. In the Revision attribute 4 of Identity Object of the Virtual IO‐Link Device, Major Revision bits 0‐3 shall be New and Existing
IO‐Link Protocol Minor Revision, bits 4‐6 shall be IO‐Link Protocol Major Revision. Minor Revision filed shallbe upper 8 bits of the IO‐Link Device ID. (Section 5‐2.2.3)

C

Nov‐21

Nov‐21ODVA Specification Mandatory Change List
2021 PC 1

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

1. Some instance attributes of Time Sync Object changed data types but no data length change.
2. Time Sync Object is at revision 5 which has a new conditional Associated Interface Labels attribute 31.
Associated Interface Objects attribute 29 description is also calarified.

New and ExistingC

Apr‐21

Apr‐213.30

1. Process Device Diagnostic Object Revision 3 is required. (Table 5B‐19.5)
2. A required Supported Profile Diagnostics attribute 17 was added. (Table 5B‐19.6)

New and ExistingC

Apr‐21

Apr‐21C

Apr‐21

Apr‐21

Topic

VolumeEditionTime Sync Object Attribute Clarifications

1

3.30

Process Device Diagnostics Object
Updates1

Description

In‐Cabinet EtherNet‐IP Profile

2

1.27

1. A required EtherNet/IP Usage Item in ListIdentity response for devices implementing the In‐Cabinet Usage
profile. (Table 2‐4.6)
2. Two conditional attributes were added to Ethernet Link Object which are required for In‐Cabinet Usage
Profile. (Table 5‐5.3)
3. New Select Link Link Object, In‐Cabinet Actual Topology Object and In‐Cabinet Commissioning Object were New
added. (Section 5‐17, 5‐18 & 5‐19)
4. LLDP Data Table Object and two new attributes are required for In‐Cabinet Profile Gateway/Routerdevices. (Table 5‐16.3)
5. New required LLDP TLVs for In‐Cabinet Profile Gateways Nodes and End Nodes. (Section 9‐8.3)

Active Certificate Deletion Behavior

8

1.12

Added behavior specification about deletation of an active device certificate. (Section 5‐4.4.6 and 5‐4.9)

New and ExistingC

Apr‐21

Apr‐22NewC

Apr‐21

Apr‐21

Constrained CIP Security

8

1.12

1.Added a ligthweight Constrained CIP Security Profile for resource‐constrained devices. (Table 1‐3.2)
2. Defined a User Authentication/Authorization Proxy scheme for resource‐constrained devices and CIP
Security Object is updated to support this new prpofile. (Section 2‐6 and section 5‐3.4)
3. Added two new required Pre‐Shared Key Cipher Suites. (Table 3‐5.5)
4. Updated EtherNet/IP Security Object to revision 6 to support multiple PSKs needed by Constrained CIP
Security Profile. (Section 5‐4.3 and 5‐4.4)

Update EST Service Name

8

1.12

Request CIP Endpoints to look for EST server _est‐cip._tcp service instead of _est._tcp service for CIP
certificates. (Section 4‐3.4.3.2.1)

New and ExistingC

Apr‐21

Apr‐21

Send Receive Fragment Requirement

8

1.12

Ethernet/IP devices implemented EtherNet/IP Seucirty Profiles are required to support
Send_Receive_Fragment service, Pull Model and File Object. (Table 8‐2.1)

New and ExistingC

Apr‐21

Apr‐21C

Apr‐21

Nov‐22

Certificate Signing Request with Subject
Alt Name81.12

1. Added Subject Alternative Name to Create_CSR service which updated Certificate Management Object torevision 2. (Table 5‐5.15). Conformant CIP Security devices shall be updated to support the new service
New and Existing
parameter.
2. A optional Check Subject Alternative Name attribute was added to EtherNet/IP Security Object. (Table 5‐
4.3)

Requirement for Output Ownership

5

2.22

OCPUNID is required only for connection points that directly control ‘safety outputs’ within an ‘output
device’. (Section F‐3.10.1.4) (Section 5‐4.2)

New and ExistingC

Apr‐21

Apr‐21

2.22

From 1/1/2021 to 1/1/2022, target‐only device(s) seeking a new Declaration of Conformity from ODVA
without base format deprecation will be given a conformance warning. After 1/1/2022 target‐only device(s)New and Existing
which have not deprecated the base format will not be able to obtain a new Declaration of Conformity from
ODVA.

C

Apr‐21

Apr‐21

Addition of base format deprecation
grace period

5

ODVA Specification Mandatory Change List
2020 PC 2

Topic

PublishDate

Effective
Date

C

Nov‐20Nov‐20

New and ExistingC

Nov‐20Nov‐20New status code 0x13A (Serial Number Mismatch) (Table 3‐5.34)(Table 5A‐3.33)

New and ExistingC

Nov‐20Nov‐203.29

1. Identity Object Revision 2 is defined. For devices support revision greater than 1, GAA response shall
include attribute 14, 19‐22 if those attributes are implemented. (Table 5A‐2.11)
2. Issue Advisory for devices only support revision 1.

New

C

Nov‐20Nov‐20

1.11

1.The newly added CIP Secuirty User Authentication Profile will provide user level authentiation and basic
authorization. (Table 1‐3.2)
2. Added three new CIP objects: Authority Object, Password Authenticator Object and Certificate
Authenticator Object. (section 5‐2)
3. A updated format of CIP Security Item in ListIdentity response. (Table 3‐5.1)
4. CIP Security Object is in Revision 4 and add new Required Security Profiles Configured instance attribute
3. (Table 5‐3.1 and Table 5‐3.2)

NewC

Nov‐20Apr‐22

1.11

1. Kick_Timer service of CIP Security Object shall only be accepted in Configuration In Progresss stateotherwise shall return status 0x0C (section 5‐3.7.2)
2. When Delete service is used to delete an static instance, status code 0x2D shall be returned, not status
0x0C. (section 5‐5.5.2)
3. Kick_Timer service of EtherNet/IP Security Object shall only be accepted in Configuration In Progresss
state otherwise shall return status 0x0C (section 5‐4.7.2)

New and ExistingM

Nov‐20Nov‐21

2.21

1. The Max_Fault_Number parameter in Safety Open is changed from a range to a constant 2. (section 2‐6.1)
2. The Max Fault Number attribute 22 is changed to have a fixed value 2 and Get only. (Table 5‐6.2)
New and Existing
3. The Max_Fault_Number field of Safety Network Segment is changed to a fixed value 2. (Table C‐5.1)
4. TST112, TST117, TST9, TST118, TST10, TST119, TST95 are all updated to use Max_Fault_Number = 2 (F‐3.6.2, F3.9.2, F‐3.4.2, F‐4.11)

M

Nov‐20Nov‐20

EditionCIP Security Session ID

1

3.29

The User Authentication Session ID Network Segment is added (Section C‐1.4.3) to support CIP Security User
New and Existing
Authenication Profile.

Process Device Diagnostics Object
Updates1

3.29

1. Process Device Diagnostic Object Revision 2 is required. (Table 5B‐19.4)
2. A Optional Recommended Action attribute 11 was added. (Table 5B‐19.6)
3. Class attribute 16 User Diagnostic Groups was changed from Required to Optional. (Table 5B‐19.1)

Serial Number E‐key Correction

1

3.29

Identity Object Instance Level GAA
Response

1

CIP Security User Authentication Profile

Objects Cleanup

Modification of Max Fault Count

8

8

5

Description

Scope of Products Scope of
Impacted
ChangeVolumeODVA Specification Mandatory Change List
2020 PC 1

Topic
Unit Code cleanup

Description

Scope of Products Scope of
Impacted
ChangeVolumeEdition1

3.28

Update Symbols for several Engeering Units, such as x2609, x260A, x261A, x2621, etc. (Section D‐2.7, D‐2.25) New and Existing

PublishDate

Effective
Date

M

Apr‐20Apr‐20C

Apr‐20Apr‐20Member List Clarifications

1

3.28

1. Assembly Object instance attribute 1 and 2 clarification (Table 5A‐5.4).
2. Clarify that the padding between Connection Point members shall be represented as null members in the
New and Existing
Connection Point Member list. (section 4.8.1)
3. Correct Standard Network Diagnostic Assmbly Content and Ordering. (Table 5A‐5.15)
4. Explain how to handle padding in Get_Connection_Point_Member_List service. (section A‐4.23.1)

CIP Security Object Reset

8

1.10

Specify CIP Security Object Revision 3 which adds a Required Reset service. (Table 5‐3.5)

New and ExistingM

Apr‐20Apr‐21DTLS Extensions for UDP‐Only Transport

8

1.10

1. For UDP‐only EtherNet/IP security device, DTLS is used for all CIP communications sent in a CIP Security
context. (Section 3‐2.1)
2. New StartDTLS command (section 3‐5.3.2)
3. Specify EtherNet/IP Security Object Revision 5 which adds new UPD‐only Policy attribute. (Table 5‐4.3)

NewC

Apr‐20Apr‐20C

Apr‐20Apr‐20M

Apr‐20Apr‐20UDP‐Only EtherNetIP for Constrained
Devices2

1.26

1.Specify requirements for a UDP‐only EtherNet/IP solution which causes changes in handling ofEncapsulation commands and UCMM. (Table 2‐3.2)
2. ListIdentiy reply has one new EtherNet/IP Capability Item. (Table 2‐4.5, Table 2‐6.3)
New
3. Introduce the EtherNet/IP Transports Application Profile. (Chapter 11)
4. TCP/IP Interface Object Encapsulation Inactivity Timeout attribute is not allowed for UDP‐Only EtherNet/IP
Transport Profile. (Table 5‐4.3)

Unit Code cleanup

7B

1.2

Update Symbols of several Engeering Units for HART devices. (section D‐1.1)

New and Existing

Base Format Deprecation

5

2.20

Remove the requirement to implement and test the Base Format. (Table 2‐1.3)

New and ExistingM

Apr‐20Apr‐20

Test TST42, TST43 and TST44 Corrections

5

2.20

Update TST42, TST43 and TST44 to accept correct error code. (F‐3.10.1.2, F‐3.10.1.3,

New and ExistingM

Apr‐20Nov‐21

Cleanup Configuration Procedure
Guidelines

5

2.20

Remove classs 3 connection requirement for SNCT configuration data transfer so SRS138 was removed fromNew
TST55. (F‐3.11.5.5)

M

Apr‐20Nov‐21

Switch change detect

5

2.20

Remove the requirement for a background test of the switches in safety devices so FRS350, FRS351 and FRS
New
354 were removed from TST50 (F‐3.11.2); FRS350 and RSR364 were remvoed from TST108 (F‐3.11.3).

M

Apr‐20Apr‐20ODVA Specification Mandatory Change List
2019 PC 2

Topic

PublishDate

Effective
DateC

Dec‐19Jun‐21

New and ExistingC

Dec‐19Dec‐19New and ExistingC

Dec‐19May‐19New and ExistingC

Dec‐19Dec‐191.9Specify EtherNet/Ip Security Object Revision 4, added new Pull Model Disabled state and changed Atrribute
New and Existing#13 to Get only. Stte Event Matrix Table 5‐14.14 was updated with the new state.

C

Dec‐19Dec‐191.25

1. LLDP Management Object (0x109) and LLDP Data Table Object (0x10A) definition are added (Section 5‐15
and Section 5‐16).
2. Specify ODVA specific implementation of the Link Layer Discovery Protocol (LLDP) (section 9‐8). If LLDP
protocol is supported, LLDP Management Object shall be implemented. If receive mode is implemented,
New and Existing
either LLDP Data Table Object or SNMP shall be implemented.
3. EtherNet/IP Devices undergoing certification for the first time and multi‐port devices receiving an updatethat adds CIP functionality are required to implement LLDP protocol.

M

Dec‐19Dec‐21

EditionFile Object Clarifications & Extensions

1

3.27

1. Specify File Object Revision 3 which has new attribute 12 and different behaivor (Table 5A‐42.27) than rev
1 or 2. CIP Security device is required to support revision 3.
New and Existing
2. New Optional Encoding parameter to Create service (Table 5A‐42.10).

Assembly Object Class Revision Attributeclarification

1

3.27

Assembly Object Revision attribute value can be either 02 or 03 (Table 5A‐5.3).

Orphan Certificate Cleanup

8

1.9

EIPSO Reset Condition

8

1.9

EIPSO State Addition

8

LLDP

2

Description

Scope of Products Scope of
Impacted
ChangeVolume1. Specify CIP Security Object Revision 2 which adds a Required Object_Cleanup service (Table 5‐3.9).
2. Update Apply Behavior Flag parameter for Apply_Config service of EtherNet/IP Security Object (Table 5‐4.12).
Reset service must be sent over a TLS session conditional on the EtherNet/IP Security Object being in theconfigured state. (Section 5‐4.5.1)

ODVA Specification Mandatory Change List
2019 PC 1

VolumeEditionDescription

Scope of Products
Impacted

Scope of
ChangePublishDate

Effective
DateStandard Network Diagnostic Assy

1

3.26

1. Assembly Object Revision attribute should be 3, 1 and 2 are only allowed for Static Assemblies (Table 5A‐
5.3). New Conditional attribute Member List Signature (Table 5A‐5.4).
2. New Conditional Get_Connection_Point_Member_List service for Connection Manager, Time Sync Object(Table 3‐5.3, Table 5B‐2.17).

New and ExistingC

Apr‐19Nov‐20Identity Object Reset Service Clarification

1

3.26

1. Reset service is only required for instqance 1.
2. Devices that reset the whole device if a Reset has been directed to Instances greater than 1 will be non‐conformant.

New and ExistingC

Apr‐19Apr‐20DTLS Timeout Enhancement8

1.8

New and ExistingC

Apr‐19Apr‐19Requiring CIP Security for Services8

1.8

New and ExistingC

Apr‐19May‐19CMO State Machine Clarification8

1.8

Feedback Ratio

5

2.18

Topic

EtherNet/IP Security Object Revision updates to 3. New required attribute DTLS Timeout is added for CIP
Security device.
After a device’s CIP Security Object has attained the CONFIGURED state configuration changes must
only be accepted if the changes are made over a CIP Security connection for File Object, TCP/IP Object andEthernet Link Object (Section 4‐3.1.3).
Verify_Certificate service clarification and CMO State clarification. (Table 5‐5.17 and Table 5‐5.18)
Add new Conditional attributes and services to Safety Dual Feedback Channel Object for multiport safety
devices. (Section 5‐4)

New and ExistingC

Apr‐19Apr‐19New and ExistingC

Apr‐19Apr‐19ODVA Specification Mandatory Change List
2018 PC 2

TopicVolumeEditionCommon Object Class EDS Correction

1

3.25

HART Hooks
File Instance Clear_File and Save Params
STIME correction
Remove Integrity Profile

1
1
1
8

3.25
3.25
3.25
2.17

Description
Object_Name and Object_Class_Code keywords are required in the [Assembly], [Parameter], [Group] sectionof eds file if such object exists in the device.(Table 7‐3.32, Table 7‐3.5, Table 7‐3.29.)
New required attributes are added to Identity Object for HART devices (Table 5A‐2.3)
Clear_File service shall not clear File Save Parameter. (Section 5A‐42.5.7)
STIME shall be data type ULINT not LINT.
Integrity Profile is obsolete for CIP Security device.

Scope of Products
Impacted

Scope of
ChangePublishDate

Effective
Date

New and ExistingM

Nov‐18Apr‐19New
New and Existing
New and Existing
New and Existing

C
M
M
M

Nov‐18
Nov‐18
Nov‐18
Nov‐18

Nov‐18
Nov‐18
Nov‐18
Nov‐18ODVA Specification Mandatory Change List
2018 PC 1

Topic

VolumeEdition

System Time Definition
Invalid Connection Size Status CodePull Model

1
1
8

3.24
3.24
1.6

EIP Security Object IF Linkage

8

1.6

Multiport Safety Devices

5

2.17

Description

Scope of Products Scope of
Impacted
ChangeImprove elementary data type for System Time (STIME) (Table C2.1, Section C‐3.3, Section 7‐3.5.1.12)
New and Existing
Allow an exception for CIP‐Modbus translators to use Status Code 0x109 (Table 3‐5.33)
New and Existing
Pull Model is a new mandatory capability of CIP Security devices. (Section 4‐3, 5‐4, 5‐5, 6‐5.3)
New and Existing
Each CIP Security device with more than one IP address shall support the Port Object and the
New and Existing
Associated Communication Objects attribute. (Section 5‐4.1)
Add new Required attributes and services of Safety Supervisor Object for multiport safety devices. (Section 5‐
New and Existing4)

PublishDate

Effective
Date

M
M
C

Apr‐18Apr‐18Apr‐18Apr‐18Apr‐18May‐21C

Apr‐18Apr‐18C

Apr‐18Apr‐18ODVA Specification Mandatory Change List
2017 PC 2

TopicVolumeEdition

1

3.23

1

3.23

1

Description

Scope of Products Scope of
Impacted
ChangePublishDate

Effective
Date

New and ExistingC

Nov‐17

May‐19New and ExistingC

Nov‐17

Nov‐17

Port Type 0 Associated Communication
Objects Issue
CIP Sync over PRP
Connection Manager Error Codes
Updates
Get‐Set_Attribute_List Clarifications
Commissioning Updates

3.23

a. Revision Class attribute can be 3 or 4 (required for Master capabple device). (Section 5B‐2.3)
b. New conditional attribute 30. (Section 5B‐2.4)
a. Port Type and associated objects classification. (Table 3‐7.4)
b. Associated Communication Object attribute clarification. (Section 3‐7.2.1.9)
A new PTP profile for PRP (Table 5B‐2.20)

New and ExistingC

Nov‐17

Nov‐171

3.23

New Connection Manager Error Codes (Table 3‐5.33)

New and ExistingC

Nov‐17

Nov‐17

1
8

3.23
1.5

New and Existing
New and ExistingCC

Nov‐17
Nov‐17

Nov‐18
Nov‐17

Enhance Certificate Trust

8

1.5

Clarification of Get/Set_Attribute_List service (Section A‐4.3 and Section A‐4.4)
Enhanced commissioning requirements. (Section 4‐3 and section 5‐3)
a. New required Trusted Identities attribute of EtherNet/IP Security Object (Section 5‐4.4)
b. Clarification of Certificate Management Object (Section 5‐5.4)

New and ExistingC

Nov‐17

Nov‐17

Correct CIP Security Object Get Attr All

8

1.5

Correct error in CIP Security Object instance level Get_Attribute_All response layout (Table 5‐3.8)

New and ExistingC

Nov‐17

Nov‐17

1.5

Guideline on how to open non‐secure Class 0/1 connection via secure UCMM or Class 3 connection (Section
New and Existing
3‐5.7.2.4)

C

Nov‐17

May‐18PTP_Leap_Seconds_Attribute

Secure CL3 and Non‐Secure CL1Clarification

8

ODVA Specification Mandatory Change List
2017 PC 1

Topic

VolumeEditionFile Object Enhancements

1

3.22

PTP port number association

1

3.22

Missing Item Count
Null Fwd Open Clarification

8
8

1.4
1.4

Cert Format Clarification

8

1.4

PSK Format Clarification

8

1.4

MCAO_Not_Required

9

1.1

Enhancements for PRP HSR

2

1.23

Description

Scope of Products Scope of
Impacted
Changea. Revision Class attribute can be 1 or 2. (Section 5A‐42.2)
b. Changed definition of the File Save Parameters attribute. (Section 5A‐42.2.1.8)
New and Existingc. State Event Matrix change for Download Transfer, First‐and‐last and Upload_Transfer event. (Table 5A‐
42.26)
a. Associated Interface Objects attribute is added to Time Sync Object to declare the PTP port number
association. (Table 5B‐2‐3)
Only Newb. [AssociatedInterfaceObjects] Entry Keyword is added to eds file. (Section 7‐3.6.6.1)
Added Item Count to CPF Item for Unconnected Message over UDP for DTLS. (Table 3‐5.4)
New and ExistingSpecify how a Null ForwardOpen should be sent in the presence of CIP Security. (Section 3‐7)
New and Existing
Certificate Encodings Flag attribute and Certificate Encoding attribute are added to Certificate Management
New and Existing
Object to specify certificate format. (Section 5‐5.3.3 and Section 5‐5.4.1)
Specify encoding format for Pre‐shared keys. (Section 5‐4.4.5)
New and Existing
A Motion Control Axis Object or a vendor specific equivalent construct needs to be in CIP Motion Controller.
New and Existing(Section 1‐2.2)
a. PRP/HSR Nodes Table with Active Status attribute is added to PRP/HSR Table Object. (Section 5‐14.3.3.1)
b. Get_Member service is now Required for PRP/HSR Table Object. (Table 5‐14.4)
New and Existingc. Diagnostic attributes 17 ‐ 20 are added to PRP/HSR Protocol Object. (Table 5‐13.3)

PUB00317_ODVA specification mandatory change list_R19

PublishDate

Effective
Date

C

Apr‐17

Nov‐17C

Apr‐17

Nov‐17MC

Apr‐17
Apr‐17

Apr‐17
Apr‐17M

Apr‐17

Apr‐17M

Apr‐17

Apr‐17C

Apr‐17

Apr‐17C

Apr‐17

Nov‐17