I have not found where is the limitation of PublicKeyAlgorythm to be used for signature. The only restriction for values 240..255 has been found at clause 4.2.2.
So implemented partially.

TP to check unknown payload type

.  First run of of RECV TCs implementation done

.  Reviewed of existing Send TPs for Certificate profiles
.  Reviewed of existing  RECV CAM TCs
.  Review of new RECV DENM TCs
.  Implementation of RECV DENM TCs
.  Development of TCs for RECV GENMSG done
·  TTCN-3 Source codes are committed

.  Added new TCs for RECV Other profiles
.  Starting development of RECV Certificates

check that AA signed by root or other AA

Add TP to test undefined ITS_AID.

3 variants for each type of messages

add defines for local regions
fix #0007321 #0007327 #0007327 #0007325 #7328 #0007325 #0007324 
change 'containing length' to 'indicating length=2'
fix #0007323

fix #0007329

Actually the idea of these tests is to check that subordinate cert is inside the validity of the issuing cert.
fix #0007331

remove {}

All Message-related CRs has been closed
All BO messages are derived from specified BV message
fix #0007316 #0007361 #0007319 #0007255 #0007258

check that unknown headers are allowed in DENM

.  Terminated review of existing Send TPs for Certificate profiles
.  Terminated review of existing  RECV CAM profiles
.  Added new RCs for RECV CAM profiles done
.  Started review of RECV DENM profiles

notes #0007316 #0007349 #0007358 #0007350 #0007360
fix #0007317 #0007349