Conformance update plans

Plan to improve conformance of the DCL with the Matter spec.

DCL updates

Update PKI module

1. Add missed validation for the SerialNumber field, as mentioned in the CHIP spec max length should be 20 octets - spec
2. Update and add missed constraints while adding revocation distribution points - missed size constraints for CRLSignerCertificate, update size constraints for CRLSignerDelegator (spec), add missed constraints for DataFileSize, DataDigest and DataDigestType fields (spec)
   • CRLSignerDelegator size is 2MB and should be lowered to 2KB (2048 bytes)
   • CRLSignerCertificate size is not set and should be set to 2KB (2048 bytes)
3. Double-check validations regarding the CRLSignerCertificate field

Update Model module

1. Update value constraint for the DiscoveryCapabilitiesBitmask field, it should be between 0-30, not 0-14 (spec)
2. Rename the MaintenanceUrl field to EnhancedSetupFlowMaintenanceUrl
3. Update constraint for the OtaChecksumType field, iit should be within [1,7,8,10,11,12], not 0-65535 (spec)
4. Document mapping about that DeviceModel from the CHIP spec relates to the Model from DCL
5. Document mapping about that DeviceSoftwareVersionModel from the CHIP spec relates to the ModelVersion from DCL

Compliance Module

1. Document mapping about that CHIP spec defines only a single DeviceSoftwareCompliance schema, but there are several related schemas in DCL
   • ComplianceInfo - contains more fields which are not described in CHIP spec
   • DeviceSoftwareCompliance - contains list of ComplianceInfo

Updates to Matter DCL spec

1. Vendor, DeviceModel, DeviceSoftwareVersionModel and DeviceSoftwareCompliance Schemas
   • Add the missed Creator/Owner field to mention who registers the schema record
   • The field uniquely identifies the DCL key(address) that was used to register the associated record(VendorInfo, Model etc) in DCL
2. Product Attestation Authority and Intermediate Certificate Schema
   • Update sections about GrantApprovals and GrantRejects fields - fix types and naming conflict
   • • They named as approvals and rejects
   • Add the missed SubjectAsText field
3. Operational Trust Anchor Schema
   • Replace IsVidVerificationSigner boolean field with certificationType enum field
   • • Describe possible enum variants

Redesign/reformat the CHIP specification document with the internals of DCL

1. Reformat/Feed document with new sub sections about write and read requests for all Schemas - describe associated endpoints and high-level implementation/explanation details from DCL
2. Update mapping document in DCL after applying changes into CHIP spec
   • Document mappings about that CHIP spec defines two(PAA/PAI and OTA → NOC/ICA) separate schemas for certificates, but it is a single common Certificate schema in DCL
   • • DCL separates certificates by type (schema)
   • Document mappings about the PKI Revocation Distribution Points Schema mentioned in CHIP implemented within the PKI module