Conflicting requirements for CableCheck and EVSEProcessing = Ongoing setting

I think this is somehow similar to the ticket here #5 (closed) but is not very clear...

CableCheck overall process Timeout value is defined in table 111, which sets it to 40 secs in the EV side

However, CableCheck allows the use of the EVSEProcessing field, which can be set to "Ongoing", which then applies the Ongoing timer for CableCheck which allows the EV-EVSE to loop up to 60s

As it seems that the intention is for these two timers to run in parallel, I guess the one for the overall process would be triggered, but the spec is not clear at all of how the handling should be and in this case you should only have 1 timeout, which shall be the one that is more strict, which is the 40secs.

So, in the end a proposal could be to add a requirement below "8.7.3.6 EVCC Timing for cable check" saying that in this case the Ongoing timeout limit must align with the CableCheck Overall Timing and we only have one timeout set to 40s.

Also, I want to leave a note that the description in the following pic for the different kind of timers, is not clear enough of what they are and must be interpreted (I am referring specifically for the ones of CommunicationSetup, CableCheck, PreCharge). For instance, for PreCharge one can also get confused checking the table for the Req/Res timeout of 2 secs, but then checks that there is also a timeout for PreCharge of 7 secs. A better description here and in the text below "8.7.3 Session setup and ready to charge" would help a lot