Re: [Smart] SMART meeting at IETF 105

[Kirsty P <[e-mail]>]

SMART folks,

Just to note that this will be a *side* meeting at IETF 105 - this also means you won't see it in the main agenda. Apologies for any confusion!

Kirsty
________________________________
From: Smart <[e-mail]> on behalf of Kirsty P <Kirsty.p=[e-mail]>
Sent: 17 July 2019 10:24
To: [e-mail]
Subject: [Smart] SMART meeting at IETF 105


SMART folks,


We will be meeting at IETF 105 on Wednesday 24th July 09:00-10:30 ET in the C2 room (21st Floor).

The meeting will include plans for the group going forward and discussion of the six drafts under SMART themes, listed below.

Everyone is welcome to join and we looking forward to seeing you there!


Kirsty


======


draft-taddei-smart-cless-introduction

  *   Also known as CLESS: Capabilities and Limitations of Endpoint Security Solutions: https://datatracker.ietf.org/doc/draft-taddei-smart-cless-introduction/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-taddei-smart-cless-introduction%2F&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825534785&sdata=jZ3q0baYXavrEKEK1BBdcvmGL96mIpNfTZnKj74ak7Q%3D&reserved=0>
  *   CLESS attempts to establish the capabilities and limitations of endpoint-only security solutions and explore potential alternative approaches.


draft-mcfadden-smart-endpoint-taxonomy-for-cless

  *   Endpoint Taxonomy for CLESS: https://datatracker.ietf.org/doc/draft-mcfadden-smart-endpoint-taxonomy-for-cless/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-mcfadden-smart-endpoint-taxonomy-for-cless%2F&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825534785&sdata=%2Bq7KjYGFVA6OrEDo29b9R2np4Gk0407W43SoOKGDHNQ%3D&reserved=0>
  *   CLESS discusses endpoints in general terms. It has been suggested that there are classes of endpoints that have different characteristics. Those classes may have completely different threat landscapes and the endpoints may have completely different security capabilities. In support of the work on CLESS, this document provides a taxonomy of endpoints that is intended to provide a foundation for further work on CLESS and research on approaches to providing endpoint security alternatives in a diverse group of settings.


draft-sasse-smart-secui-questions

  *   Open Questions in Supporting Secure User Interactions: https://github.com/smart-rg/drafts/blob/master/draft-sasse-smart-secui-questions.txt<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsmart-rg%2Fdrafts%2Fblob%2Fmaster%2Fdraft-sasse-smart-secui-questions.txt&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825544786&sdata=sHZWXaSXuJmvjulb5Xxk5uEOnJRG5KNLIf%2FfWQ3Klu8%3D&reserved=0>
  *   Describes open questions in supporting usable security at the UI level. The questions are split into defining a set of manageable security tasks for countering the most common attacks, and the UI elements for signalling whether an intended action is secure.


draft-lazanski-smart-users-internet

  *   An Internet for Users Again: https://datatracker.ietf.org/doc/draft-lazanski-smart-users-internet<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-lazanski-smart-users-internet&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825544786&sdata=Jx%2Foo%2FiV%2BT8YNWIPtB1RnRKEMP6pMeA5KLHyD7SmlVc%3D&reserved=0>
  *   RFC 3552 introduces a threat model that does not include endpoint security. In the fifteen years since RFC 3552 security issues and cyber attacks have increased, especially on the endpoint. This document proposes a new approach to Internet cyber security protocol development that focuses on the user of the Internet, namely those who use the endpoint and are the most vulnerable to attacks.


draft-moriarty-caris2

  *   Coordinating Attack Response at Internet Scale 2 Report: https://datatracker.ietf.org/doc/draft-moriarty-caris2/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-moriarty-caris2%2F&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825554782&sdata=GKx9yoWTJtlemk9ps7VsCMt40tJ8vpzGoUmlainlHAw%3D&reserved=0>
  *   Coordinating Attack Response at Internet Scale (CARIS) 2 (https://www.internetsociety.org/events/caris2<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.internetsociety.org%2Fevents%2Fcaris2&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825554782&sdata=bIwnGlgPhaKUKtcOZaOebmpSWRDJ6eymg%2FGl4fTAkVo%3D&reserved=0>), sponsored by the Internet Society, took place 28 February and 1 March 2019 in Cambridge, Massachusetts, USA. Participants spanned regional, national, international, and enterprise CSIRTs, operators, service providers, network and security operators, transport operators and researchers, incident response researchers, vendors, and participants from standards communities.


draft-mcfadden-smart-rfc3552-research-methodology

  *   Methodology for Researching Security Considerations Sections: https://datatracker.ietf.org/doc/draft-mcfadden-smart-rfc3552-research-methodology<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-mcfadden-smart-rfc3552-research-methodology&data=02%7C01%7Ckirsty.p%40ncsc.gov.uk%7C7a3ee571969e4ec8956708d70a9897cf%7C14aa5744ece1474ea2d734f46dda64a1%7C0%7C0%7C636989522825564773&sdata=scPL1tRC%2FZGwQ4j%2BZeESEhHVKDdlQsIBcb%2BcyuOdZXA%3D&reserved=0>
  *   RFC3552 provides guidance to authors in crafting RFC text on Security Considerations. The RFC is more than fifteen years old. With the threat landscape and security ecosystem significantly changed since the RFC was published, RFC3552 is a candidate for update. This draft proposes that, prior to drafting an update to RFC3552, an examination of recent, published Security Considerations sections be carried out as a baseline for how to improve RFC3552. It suggests a methodology for examining Security Considerations sections in published RFCs and the extraction of both quantitative and qualitative information that could inform a revision of the older guidance.



This information is exempt under the Freedom of Information Act 2000 (FOIA) and may be exempt under other UK information legislation. Refer any FOIA queries to [e-mail]. All material is UK Crown Copyright ©