Document ISO/IEC/JTC 1/SC 22/WG 23 N0773

Draft Minutes of Meeting #52
ISO/IEC JTC 1/SC 22/WG23
22-23 January 2018


Meeting Location : Orange Tree Golf Resort
10601 N. 56th Street
Scottsdale AZ 85254 USA


Local arrangements in separate document.

Agenda

1 Opening activities

1.1 Opening Comments

1.2 Introduction of Participants/Roll Call

Joyce Tokar – WG 9
Clive Pygott – WG 14
Gary Klimowicz – WG 5
Stephen Michell – Convenor
Erhard Ploedereder – Ada Europe liaison
Paul Preney – WG 21

1.3 Procedures for this Meeting

1.4 Approval of previous Minutes of meeting 51 (N0759)

1.5 Review of actions items and resolutions, Action Item and Decision Logs

Add to 44-08 to contact ASTM International (www.astm.org) w.r.t. unmanned air

1.6 Approval of Agenda

1.7 Future Meeting Schedule


2019





#66

Oct/ Nov 2019

Belfast, North Ireland with WG 21(?)


#65

22-23 August 2019

Seoul, Korea with SC 22


#64

TBD June 2019

WG 21, Cologne, Germany (?)


#63

TBD May 2019

Teleconference


#62

TBD April 2019

With WG 21


#61

TBD March 2019

Teleconference

#60

21-22 January 2019

Phoenix, AZ


2018





#59

8-9 Nov 2018

San Diego, CA


#58

12-14/09/18

Toronto, Ontario, Canada with SC 22


#57

6-7/06/18

With WG 21, Rapperswil, Switzerland, with WG 21


#56

14/05/18

Teleconference


#55

26-27 April 2018

Brno Chez Republic with WG 14


#54

14-15 March 2018

WebExWith WG 21, Jacksonville, FL, mostly WebEx


#53

12/02/18

WebEx







AI 52-01 – Steve – coordinate with David Keaton about April WG 14 meeting. Talk with Martin Sebor about rooms.

AI 52-02 – Steve – co-ordinate with Herb Sutter about accommodations in Rapperswil.

Liaison Activities

52.2.1 PL22.3/WG5 (Fortran) Gary Klimowicz

DIS for ISO IEC 1539, going into DIS ballot. Expect to publish in a few months. Steve to work with Gary to get TR 24772-8 making progress.

51.2.2 WG4 (COBOL)

Nothing.

52.2.3 WG9 (Ada) Erhard Ploedereder

Part 2 is delivered. Joyce Tokar is leading the WG 9/HRG, whose major work has been the production of TR 24772-2.

52.2.4 PL22.11/WG14 C Clive Pygott

In October meeting, made final changes to ISO IEC 9899 and preparing for DIS ballot. Looking for publication by Dec 2018. Major changes have been deferred for a possible 2021 or 2022 edition.

52.2.5 PL22.16/WG21 (C++) Michael Wong

ISO IEC 14882:2017 has been published. WG 21 is working on a revision for 2020.

WG 21 has started writing TR 24772-9, having drafts for about 6 subclauses of Clause 6. Proposed a liaison statement and terms of working together. There are significant issues being discussed about how to describe C++ issues, and mitigations.

52.2.6 MISRA C Clive Pygott

Working towards the next release, moving to C-11.

52.2.7 MISRA (C++) Clive Pygott

Working to update the document to incorporate C++-14. There is significant interest for the AutoSar with the expectation to merge MISRA-C++ with AutoSar. Michael Wong and CodePlay now participating.

52.2.8 SPARK Joyce Tokar

Draft of TR 24772-2 given to AdaCore. AdaCore has committed to do the work but is resource limited. Negotiations are ongoing.

52.2.9 Other Liaison Activities or National body reports

Ada Europe invites us to join them in Lisbon. We regret that we cannot co-locate in 2018.

52.3. Document Review

52.3.1 TR 24772-1 Vulnerabilities, language independent (N0771)

While Going through 24772-3 C language vulnerabilities, we identify a possible vulnerability associated with the overlap of source and destinations during a copy or move operation. This may need a new vulnerability writeup.

AI 52-03 – Erhard, Clause 6.41.3, add a paragraph describing private components under redefinition (see TR24772-2 clause 6.41)

AI 52-04 – Erhard, clause 7.31 Fault Tolerance – rewrite to focus on the vulnerability as opposed to a tutorial.

AI 52-05 – Steve, Erhard – clause 7.33.3 Clock Issues, rework to show the failures that can occur.

52.3.2 TR 24772-2 Ada language specific part

WG 9 has reworked Part 2.

AI 52-06 – Erhard, Joyce – read the text of each subclause 6.x.2 for applicability of the general guidance in TR 24772-1 subclause 6.x.5

52.3.3 TR 24772-3 C language specific part, Document N0764

Clive has submitted a new version of TR 24772-3 C to take into account WG 14’s comments. He is reworking Part 3 to reflect those issues.

Changes are reflected in N0774.

AI 52-07 – Paul Preney – for clause 6.15, examine the overflow and use limits.h and expressions using them, and send to Clive.

AI 52-08 – Clive – clause 6.34.1 – investigate the parameter count issue and correct document.

AI 52-09 – Erhard, Clive – also for 6.34.1, investigate what C does w.r.t One Definition Rule. See Hubert Tong’s message of 23 Jan.

52.3.4 TR 24772-4 Python language specific part

See N0762. We have proposed material for the OO vulnerabilities from the Python Typing experts reflector.

AI 52-10 – Paul Preney, Erhard Ploedereder, - reach out to coworkers or co-conspirators for help with Python concurrency vulnerabilities.

52.3.5 TR 24772-8 Fortran

Gary Klimowicz participated in the meeting for WG 5. Future developments are expected.

3.6 TR 24772-9 C++

N0758 or later document. WG 14/SG 12 has updated 6 vulnerabilities and drafted a liaison statement to guide joint work.

3.7 Spark

      AdaCore has acknowledged their responsibility to create the Spark part. Joyce will communicate with Yannick Moy about the work.

3.8 Potential TR24772 Guidance on avoiding Programming Vulnerabilities – IS

Update from N0735

We discuss the document. There is a context from safety and security communities, where the surrounding management, engineering and architectural contexts need to be considered. Some proposed wording – “When appropriate safety or security standards, are required, then the coding and design rules provided in this standard shall be followed.”

Idea, we could have some rules that must be obeyed, and many that can be tailored.

How do we handle explanatory material? - these are already in the other documents, which should be referenced (as the part 1)

AI 52-11 – Larry, add wording that includes the above context wording, plus referencing to TR 24772-1 and send as N0777. Also consider the “safety” part for each rule as appropriate.

AI 52-12 – all - review the document (N0777) for applicability to the “must” rules, and to recommend what else the standard should cover.

Numbering of document set to let us include other kinds of coding documents or standards. We could make the general document TR 24772-1-1 and any general guidelines or standards as -1-2, -1-3, etc. Ada could be TR24772-2 (or TR 24772-2-1) and Ada-specific coding guidelines -2-2, -2-3 etc. No decision was reached at this meeting.

4 Review of Assignment of responsibilities


5 Resolutions and Action Items

AI 52-01 – Steve – coordinate with David Keaton about April WG 14 meeting in Brno. Talk with Martin Sebor about rooms.

AI 52-02 – Steve – co-ordinate with Herb Sutter about accommodations in Rapperswil.

AI 52-03 – Erhard, Clause 6.41.3, add a paragraph describing private components under redefinition (see TR24772-2 clause 6.41)

AI 52-04 – Erhard, clause 7.31 Fault Tolerance – rewrite to focus on the vulnerability as opposed to a tutorial.

AI 52-05 – Steve, Erhard – clause 7.33.3 Clock Issues, rework to show the failures that can occur.

AI 52-06 – Erhard, Joyce – read the text of each subclause 6.x.2 for applicability of the general guidance in TR 24772-1 subclause 6.x.5

AI 52-07 – Paul Preney – for clause 6.15, examine the overflow and use limits.h and expressions using them, and send to Clive.

AI 52-08 – Clive – clause 6.34.1 – investigate the parameter count issue and correct document.

AI 52-09 – Erhard, Clive – also for 6.34.1, investigate what C does w.r.t One Definition Rule. See Hubert Tong’s message of 23 Jan.

AI 52-10 – Paul Preney, Erhard Ploedereder, - reach out to coworkers or co-conspirators for help with Python concurrency vulnerabilities

AI 52-11 – Larry, add wording that includes the above context wording, plus referencing to TR 24772-1 and send as N0777. Also consider the “safety” part for each rule as appropriate.

AI 52-12 – all - review the document (N0777) for applicability to the “must” rules, and to recommend what else the standard should cover.



6. Adjournment

Meeting adjourned at 1700 on 23 January 2018.