CC1:
260001
Mike P presents
E//: coversheet as CR, or shold it be living document, should be cat F
T-Mo: ok
Vicechair: cat F, purpose of meeting is pre R20, so needs to be CR
Oppo: update also revision to 1
-> revise

260002
Stavros presents
Nokia: also upstate JSON
E//: trying to remove "procedure and execution steps" heading, otherwise ok, also Huawei updates template
Nokia: in  GSMA NESAS the template has this heading
QC: clauses affected need to fixed in any way
E//: to 4.2.2.9.1: reference K.2.10 does not include this threat, either new threat needs to be inlcuded, or different reference
Oppo: add reference number
Nokia: check which clause is referenced to
E//: has a CR to 33.926 could follow similar approach
-> revise

260014
Markus presents
Huawei: keep the heading procedure and execution steps
Mitre: good to have extra rows, but keep procedure and execution steps
Nokia: agree, was like that in all the SCASs, so not delete procedure and execution steps, keep preconditions
Nokia: technically nothing is added, in 117, everywhere there is procedure and execution steps, otherwise we have to open everything, not pursue
TMo: all SCAS already have this, what is the big concern
E//: the aim is to bring inline that the test cases already are written like that. No updates are required, just avoid one sentence and execution steps.
Huawei: support as proposed by David, align this with how it is used in majority of test cases.
-> discussion continues

260003
Stawros presents
remove duplicate and, cat F
E//: is this to be converted to pCR
vicechair: title needs to be adapted accordingly
Huawei: change chould be in R20, not impact R19 anymore, changes are against rel 19, but make it R20 pCR
Mitre: there is no living doc for 516 at the moment
Huawei: correct,
TMo: procedure issue, easier for tracking under working item code it is
Vicechair: agenda is limited to pre R19
Chair: R20 can be pre-agreed, but then can be agreed in Goa very quickly
-> continue on email

260004
Stawros presents
Huawei: content ok, but should be in R20
-> continue on email

260005
Stawros presents
same as 0003/0004
-> continue on email

260006
Stawros presents
Huawei: in this meeting mainly on content, merge into living CR, can be submitted to Goa meeting
E//: 4.2.5: threat reference has been updated, which specific threat under 5.3 is applicable
Oppo: is SCAS in scope for Goa?
Chair: yes
E//: 4.2.3.5.1: reference to industry best practice, would there be something available
Nokia: this format has been used before
Mitre: ensuring sufficient random identifiers could be applicable

discussion on template for all documents in 260014

discussion on procedure "pCR and living document" vs CR in email thread on document 260002

offline call at UTC 13:00 on Tuesday