The Community String is the index to this view of the hmtsDevTable. Only the devices that have successfully registered at least once are listed in this view. This table is current for HMTS that support the community string proxy as defined in SCTE 25-2 (Formerly HMS004). It is the responsability of the HMTS to keep the contents of the hmtsDevTable, hmtsComFaultTable, hmtsIPDevTable and hmtsCommDevTable consistent according to the following rules: - For each active row in hmtsDevTable whose hmtsDevComStat instance is different of noError(1), there must be a row with the same physical address in hmtsComFaultTable. - For each row in hmtsComFaultTable, there must be a corresponding row in hmtsDevTable with RowStatus active. - Each active row in the hmtsDevTable that has a valid IP address must also be present in the hmtsIPDevTable. - For each row in hmtsIPDevTable there must be a corresponding row in hmtsDevTable with rowstatus active. - Each active row in the hmtsDevTable that has a valid community string and whose RowStatus is active must also be present in hmtsCommDevTable. - For each row that exists in hmtsCommDevTable there must exist a row with the same community string in hmtsDevTable with RowStatus active. - An IP address is valid if there does not exist another row in the hmtsDevTable with the same IP address and RowStatus active, and if it has been assigned by either an external DHCP server, the internal DHCP server (if hmtsIPManagementMethod is set to client) or if it fits in one of the ranges defined by hmtsNetAddrTable (if hmtsIPManagementMethod is set to manualXP, manualHMTS or automatic). - A community string is valid if there does not exist another row in the hmtsDevTable with the same community string and RowStatus active.