Presentation of contributions to ITU-T SG17: Guidelines

Slides:



Advertisements
Similar presentations
Critical Reading Strategies: Overview of Research Process
Advertisements

ITU WORKSHOP ON STANDARDS AND INTELLECTUAL PROPERTY RIGHTS (IPR) ISSUES Session 5: Software copyright issues Dirk Weiler, Chairman of ETSI General Assembly.
Cloud computing security related works in ITU-T SG17
Preparing a Grant Proposal: Some Basics
Committed to Connecting the World International Telecommunication Union April 2015 Presentation of contributions to ITU-T SG17: GuidelinesITU-T SG17 Martin.
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
Experimental Psychology PSY 433
Geneva, Switzerland, 4 December 2014 ITU-T Study Group 17 activities in the context of digital financial services and inclusion: Security and Identity.
Grant Writing/Comprehensive Workshop Paul R. Albert, Ph. D
Collaborative Report Writing the Proposal. Definition Proposal: a document written to convince your audience to adopt an idea, a product, or a service.
Report Writing Format.
Outline Components of a Report.
CHAPTER 4 Engineering Communication
BASIC IRRS TRAINING Lecture 7
IAEA International Atomic Energy Agency. IAEA Outline Learning Objectives The Mission Report Purpose and objectives What is not needed? Evolution of the.
The Online Submission Process: Guidelines and Training for Authors Marlowe H. Smaby, Michael R. Smith, Cleborne D. Maddux.
Report Writing. Table of contents Your report should include a table of contents if longer than about 5-10 pages. This allows the reader to quickly find.
International Telecommunication Union ITU Workshop on Standards and Intellectual Property Rights (IPR) Issues Yukio Hiramatsu Chairman, TTC IPR Committee.
©2011 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Research Methodology Class.   Your report must contains,  Abstract  Chapter 1 - Introduction  Chapter 2 - Literature Review  Chapter 3 - System.
Preparing a Written Report Prepared by: R Bortolussi MD FRCPC and Noni MacDonald MD FRCPC.
Scope of the Journal The International Journal of Sports Medicine (IJSM) provides a forum for the publication of papers dealing with basic or applied information.
4-2 CHAPTER 4 Engineering Communication © 2011 Cengage Learning Engineering. All Rights Reserved.
Research Methods Technical Writing Thesis Conference/Journal Papers
Technical Report Outline Title Page Frontispiece Abstract Table of Contents List of Figures/ List of Tables.
Technical Reports ELEC422 Design II. Objectives To gain experience in the process of generating disseminating and sharing of technical knowledge in electrical.
“Copyright and Terms of Service Copyright © Texas Education Agency. The materials found on this website are copyrighted © and trademarked ™ as the property.
KEY ISSUES FROM INITIAL REVIEW OF MATERIALS November 2008.
Project Report Format for Final Year Engineering Students.
ABSTRACT This is the template for preparing posters for the Electrical Safety Workshop (ESW). It is intended to define the required format for printing.
BCOM 7 Organizing and Preparing Reports and Proposals 11 Copyright ©2016 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated,
JSGS Professional Workshop Series Copyright ©Heather McWhinney, 2016 WRITING A CABINET DECISION ITEM.
Publishing research in a peer review journal: Strategies for success
Inter-American Telecommunication Commission
Inter-American Telecommunication Commission
BASIC IRRS TRAINING Lecture 7
CSE594 Fall 2009 Jennifer Wong Oct. 14, 2009
WTSA-12 Resolutions addressing security
Technical Report Writing
Report Writing Three phases of report writing Exploratory phase (MAPS)
Global Standards Collaboration (GSC) GSC-15
Tools for preparing, submitting and tracking Proposals to WTSA-16
WTSA-12 Resolutions addressing security
Report Writing.
Outline What is Literature Review? Purpose of Literature Review
Instructions Dear author(s),
Draft ETSI TS Annex C Presented by Michał Tabor for PSD2 Workshop
Reporting and Sharing Findings
IEEE MEDIA INDEPENDENT HANDOVER DCN: REVP
Technical Report Writing
The Starting Point: Asking Questions
How to Write a Scientific Report?
IRRS REFRESHER TRAINING Lecture 4
Writing reports Wrea Mohammed
Chapter Four Engineering Communication
What the Editors want to see!
ITU-T SG17 Q.3 Telecommunication information security management
Chapter 13 Proposals and Formal Reports
Chapter Four Engineering Communication
Sponsor Ballot Comment Resolution
Chapter Four Engineering Communication
Martin Euchner, Advisor, ITU-T Study Group 17
Writing an Abstract Based on slides prepared by Dr
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: sec
IEEE MEDIA INDEPENDENT HANDOVER DCN: xx-00-sec
Overview of The Bidder Response Form and Changes to the IT RFP Template March 8, 2019.
CSE594 Fall 2009 Jennifer Wong Oct. 14, 2009
STEPS Site Report.
TECHNICAL REPORTS WRITING
Presentation transcript:

Presentation of contributions to ITU-T SG17: Guidelines Martin Euchner, Advisor Martin.Euchner@itu.int ITU-T Study Group 17, Security

Overview

The importance of contributions Contributions provide the vital “fuel” to the work of Study Group 17. Well-written and well-structured contributions are essential to the success of Study Group 17 work programme. Our collaborative work towards global ICT security standards depends wholly on the timely submission of relevant, quality contributions by delegates to the ITU-T SG17.

Contributions can address topics within the mandate of Study Group 17, or related to the Questions under study Such as Inputs/comments against SG17 study items and work items under development. New work item proposals. Organization and working methods of SG17. Material for information or for discussion.

SG17 is interested in receiving Contributions from developing countries, which address Experiences and best practices of developing countries in the implementation of security standards; Review, and comments on existing ITU-T security Recommendations, or inputs to the current work items under study of SG17; Requirements/needs from developing countries for new technical security standards.

Suggested Areas of Focus (the listed items below from the 2014-09 ITU Security workshop do not necessarily constitute SG17 work items) Spam (in Q5/17) Identity management for mobile financial transactions (in Q10/17) e-health security (in Q9/17) Cloud computing security (in Q8/17) Big data security (in Q8/17) Personal data protection and privacy (in Qs 3, 5, 8, 10, 11/17) Critical information infrastructure security Smart grid security (in Q6/17) Internet of Things (IoT) security (in Q6/17) Exchange of cybersecurity information (in Q4/17) Directory and PKI (in Q11/17) Information security management (in Q3/17) Security architecture provisions for end users (in Q2/17)

Submission of contributions to SG17 is discouraged which addresses issues outside the remit of ITU; topics not in scope of Study Group 17.

Backup material

Where to find information on submitting contributions to ITU-T General directives on the preparation and submission of contributions are set out in the ITU-T A-series Recommendations. Rec. ITU-T A.1 covers the submission and processing of contributions, i.e. deadlines, posting, patent/licensing declarations. Rec. ITU-T A.2, including its Appendix, provides guidelines on content, mechanics and formatting.

Contributions should be concise and universal Concisely drafted and clearly written, comprehensive, universally understood. Not using technical jargon peculiar to an author’s country. Using international terminology and units (e.g. ISO/IEC system of units and UTC universal time). In one or more of the official languages of the Union. (alternative submission deadlines apply if translation required)

What should not be submitted or included Documents of purely theoretical interest, or not in scope of the mandate of Study Group 17, or not directly related to the Questions under study. Articles published in the technical press (unless they relate directly to Questions under study). Passages of an unduly commercial nature.

Detailed guidelines: Structure and Content

Length of contributions Should not, as a rule, exceed about 2500 words (no more than 5 printed pages). Should not include more than 3 pages of figures. (i.e. making 8 pages in all) Should be accompanied by an abstract of no more than 150-200 words.

Contribution content and structure A contribution should start with a Heading and an Abstract as independent sections. Main text of contribution should have 2 sections: 1. Rationale (or Discussion) 2. Proposal (or Conclusion). Supplementary sections such as annexes, if required. Patent and licensing declaration, if relevant. Note: Guidelines for structure of main text do not apply to draft Recommendations or to submission by Rapporteurs.

Heading and Abstract 1. The Heading Relevant Question, Place/Date of Meeting, SG and WP, Source (Member State, Sector Member, Academia, Associate), Title of Contribution, Contact Information of contributor. 2. The Abstract Very important section, which summarises content and aim of contribution. 150-200 words. Should enable readers to determine quickly whether of interest to them, often which WPs/Qs should review it. Should be understandable by other study groups too.

Rationale or Discussion 3. The Rationale (Discussion) Outlines the reasons, the justification for the proposals or conclusions. Develops the theme. Describes the methods used, any observations and findings. Provides comments on their significance.

Proposal - Conclusion 4. The Proposal and/or The Conclusion Main text should end with a Conclusion and ideally a concrete Proposal for moving work forward. A Proposal is used when offering suggestions for acceptance by meeting (e.g. solutions, plans to be implemented). It requests decisions or actions. A Conclusion is used when contribution is for information only. It summarizes observations. When both are used, Proposal follows Conclusion.

Supplementary Sections Supporting/more detailed information that can interrupt the flow of ideas in main text, should be placed in supplementary sections. These can include annexes, appendices, references and attachments. These should be very relevant to the contribution and limited in length & number.

Mechanics and Format Page Format: A4 format whenever possible. Clause numbering: Contribution should be structured logically and, using discrete clauses/subclauses for different levels of detail. (e.g. 1, 1.1, 1.2, 1.2.1) Figures and diagrams must be clear, legible in A4. Formulae – Mathematical formulae should only be presented for explaining texts. Details of how they are derived should be avoided.

Mechanics and Format (cont’d) Quotations: Simple reference to doc/para no. of existing texts or key phrase. No lengthy quotes. References to other ITU‑T texts to be made by using the official document number, e.g. COM 17 – R10. Revision to existing text – If contribution proposes modifications to an existing text, e.g. a draft Recommendation, the portions of the text to be modified should be clearly shown with revision marks.

Submission of Contributions: Timing

How to submit a contribution Via electronic means, through DDP (Direct Document Posting) or to the TSB e-mail address at tsbsg17@itu.int If software to be included, software copyright statement and licensing declaration form to be submitted at same time as contribution. (form available on ITU-T website)

When to submit a contribution At least 2 months before the meeting in question if translation is requested. Contributions received less than two months (but not less than 12 days) before cannot (guaranteed to) be translated. At least 12 calendar days before the meeting in question if no translation required. Contributions received less than 12 days before the meeting will not appear on the agenda and will be held for the next meeting

We look forward to your contributions Thank you