Support of Identity Instance attribute 25 (Application Profiles)

According to CIP Volume 1, Edition 3.38, Table 5A-2.3 (Identity Object Instance Attributes) instances attribute 25 will be come mandatory for all devices that implement at least one application profile listed in the CIP Specification, Volume 1, Chapter 11.

There are currently three application profiles defined:

• CIP Security (ID 0x01)
• EtherNet/IP Transports (ID 0x02)
• EtherNet/IP Usage (ID 0x03)

This attribute indicates which application profiles are supported by the device and is crucial for ensuring compatibility with upcoming conformance test revisions and ODVA requirements.

Scope:

• This new attribute must be supported by all LFWs.
• Target EIP-Core: V3.10, trunk
• Target LFW versions: V5.6, V3.10, trunk

Action items:

• Add support for Identity instance attribute 25
  • Attr 25 is enable by default
  • Attr 25 is not part of the remanent data
  • attr 25 is gettable from the net and host
  • attr 25 is NOT settable from the net and host
  • Non CIP Security LFWs (Scanner and Adapter)
    • Number of Application profiles supported: 2
    • Profile Number: 0x02 (EtherNet/IP Transports)
      • Features Supported:
        • Bit 0: 1 UCMM over TCP 
        • Bit 1: 0 UCMM over UDP
        • Bit 2: 1 Class 3 Connections via TCP
        • Bit 3: 0 Class 3 Connections via UDP
        • Bit 4: 0 Class 2 Connections via TCP
        • Bit 5: 0 Class 2 Connections via UDP
        • Bit 6: 0/1 Class 1 Connections     depends on whether the device supports at least one class 0/1 connection (suggestion: check for available PDC instances)
        • Bit 7: 0/1 Class 0 Connections     depends on whether the device supports at least one class 0/1 connection (suggestion: check for available PDC instances)
        • Bits 8-15: 0
    • Profile Number: 0x03 (EtherNet/IP Usage)
      • Features Supported: 
        • Bit 0: 1 Standard EtherNet/IP Usage Profile 
        • Bit 1: 0 In-Cabinet EtherNet/IP Usage Profile
        • Bits 2-15: 0
  • CIP Security LFW (same as above + CIP Security Application Profile)
    • Number of Application profiles supported: 3
    • .....
    • Profile Number: 0x01 (CIP Security)
    • Features Supported: 
      Bits are gathered through CIP Security Object instances attribute 2 (Security Profiles)
      • Bit 0: 0 EtherNet/IP Integrity Profile (Obsoleted and Reserved)
      • Bit 1: 1 EtherNet/IP Confidentiality Profile
      • Bit 2: 0 CIP Authorization Profile (Reserved) 
      • Bit 3: 0 CIP User Authentication Profile
      • Bit 4: 0 Resource-Constrained CIP Security Profile 
      • Bit 5: 0 EtherNet/IP Pull Model for Certificates Profile 
      • Bit 6: 1 Device-Based Firewall 
      • Bits 7-15: 0
• Documentation:
  • Add inst attr 25 to API Manual
  • Add Migration Note
    • Mention new Attr 25
    • Mention that device now responds with new items in ListIdentity Response
• Extend List Identity response for all LFWs by:
  • EtherNet/IP Capability item  (0x87)   (holds the content of the EtherNet/IP Transports Application Profile part of inst attr 25)
  • EtherNet/IP Usage Item       (0x88)  (holds the content of the EtherNet/IP Usage Application Profile part of inst attr 25)
  • Note: the CIP Security Item is already supported by the CIP Security LFWs.
• EDS adaptation is required
  Add keyword: [Device].ApplicationProfilesAssembly and corresponding AssemN entry