IETF Logo Mail Archive

[sacm] IETF 98: SACM Vulnerability Assessment Scenario Follow-Up Work

"Haynes, Dan" <dhaynes@mitre.org> Thu, 23 March 2017 19:13 UTC

Return-Path: <dhaynes@mitre.org>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B11C8129BF2 for <sacm@ietfa.amsl.com>; Thu, 23 Mar 2017 12:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSWnBNF_T5wS for <sacm@ietfa.amsl.com>; Thu, 23 Mar 2017 12:12:59 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 1E187129BEF for <sacm@ietf.org>; Thu, 23 Mar 2017 12:12:59 -0700 (PDT)
Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AD40073C018 for <sacm@ietf.org>; Thu, 23 Mar 2017 15:13:01 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (imshyb01.mitre.org [129.83.29.2]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id 9E7716C4045 for <sacm@ietf.org>; Thu, 23 Mar 2017 15:13:01 -0400 (EDT)
Received: from imshyb01.MITRE.ORG (129.83.29.2) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 23 Mar 2017 15:12:58 -0400
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5 via Frontend Transport; Thu, 23 Mar 2017 15:12:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8UHesREZxV6sPEl5Qb68qhxP9cpeg/aMsQEhhuIhoIE=; b=SD9eHE10XMUFgIYiRHG0PZVZJsSKsQ/OIXRm59GoCJe3BewAePx6IdG6Y56Uv1hjEncYLxreuxTvSaoYETPvo3H7hkDbVtTsMrcWBPIfBfZpWRNADBZfwvlDDcFObAA7dpgZRuNQ4C1sBSLu+mi+o1qfLyfa2wnrVAc0/L1r9IY=
Received: from DM5PR09MB1354.namprd09.prod.outlook.com (10.172.38.135) by DM5PR09MB1356.namprd09.prod.outlook.com (10.172.39.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.14; Thu, 23 Mar 2017 19:12:56 +0000
Received: from DM5PR09MB1354.namprd09.prod.outlook.com ([10.172.38.135]) by DM5PR09MB1354.namprd09.prod.outlook.com ([10.172.38.135]) with mapi id 15.01.0991.013; Thu, 23 Mar 2017 19:12:56 +0000
From: "Haynes, Dan" <dhaynes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: IETF 98: SACM Vulnerability Assessment Scenario Follow-Up Work
Thread-Index: AdKeofZI18TKbnbeRK6hM5c/aW5Lhw==
Date: Thu, 23 Mar 2017 19:12:56 +0000
Message-ID: <DM5PR09MB1354008850F09E8D768C3C91A53F0@DM5PR09MB1354.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=mitre.org;
x-originating-ip: [192.160.51.87]
x-microsoft-exchange-diagnostics: 1; DM5PR09MB1356; 7:ov/SSn4mgrKbF43cky44kIWAep9TNM1FRGX+ljsDpp/rSqaKx8JYOo7lPtKRD4vF8HTesYtwu83vmSl7eLq4laRHqRvUOmM0+MMcUROUvUoI7w9WiCUBtmdjeR4lhPIkE61P/396cedTa5cCRAgHHMxlsccwrzBMVJooAyMANIkRyDmguVveFg9fojZx+A817Iew39HsRv5Vd6T8M3/Qro1d2zH/vRzJvPG9dvFaJA6AWNXeTXJWLHjiws666AkDbMmY+N7hkIIbj3FXNadg4yS68z+65YkEYfg6rqu9Ap1eVlyEsPSvfjV1MwfBJRalVR0HryB0njux/YhOP+5cYA==
x-ms-office365-filtering-correlation-id: 030b4cf6-700d-4562-990c-08d472209d14
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081); SRVR:DM5PR09MB1356;
x-microsoft-antispam-prvs: <DM5PR09MB1356A04695271D03D4B7E7F7A53F0@DM5PR09MB1356.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123555025)(20161123558025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:DM5PR09MB1356; BCL:0; PCL:0; RULEID:; SRVR:DM5PR09MB1356;
x-forefront-prvs: 0255DF69B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39850400002)(39840400002)(39860400002)(39450400003)(39410400002)(53754006)(50986999)(54356999)(97736004)(2900100001)(2906002)(6916009)(66066001)(2501003)(5630700001)(9326002)(6306002)(8936002)(122556002)(81166006)(9686003)(54896002)(99286003)(6506006)(2351001)(6436002)(1730700003)(77096006)(55016002)(6116002)(53936002)(8676002)(790700001)(3846002)(74316002)(5640700003)(7696004)(86362001)(7736002)(3660700001)(189998001)(5660300001)(33656002)(38730400002)(110136004)(3280700002)(25786009)(102836003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR09MB1356; H:DM5PR09MB1354.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR09MB1354008850F09E8D768C3C91A53F0DM5PR09MB1354namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Mar 2017 19:12:56.3833 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR09MB1356
X-OriginatorOrg: mitre.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/PUZSIQDj86uXvSylSPp3QqYZ6_s>
Subject: [sacm] IETF 98: SACM Vulnerability Assessment Scenario Follow-Up Work
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 19:13:02 -0000

Hi Everyone,

During the Vulnerability Assessment Scenario session at IETF 98, we would like to work towards the following.


*        Reaching consensus on the components necessary for a single flow through the Vulnerability Assessment Scenario

*        Reaching consensus on the interactions between components

*        Reaching consensus on a diagram that shows the components and their interactions with each other

*        Reaching consensus on the different tasks and identify where they occur in the diagram

*        Enumerating the IEs necessary for the interactions between components

Since IETF 97, we have had a virtual interim meeting [1][2] and two follow-up calls [3][4] as well as some discussion on the mailing lists [5][6]. Also, the SACM Vulnerability Assessment Scenario has been moved to the SACM wiki [7][8].

Please let me know if you have any questions or if there is anything else you would like to add to the discussion since we have 90+ minutes according to the agenda :).

Thanks,

Danny

[1] https://www.ietf.org/proceedings/interim-2017-sacm-01/slides/slides-interim-2017-sacm-01-sessa-vulnerability-assessment-scenario-00.pdf
[2] https://www.ietf.org/proceedings/interim-2017-sacm-01/minutes/minutes-interim-2017-sacm-01-201701111000-00
[3] https://www.ietf.org/mail-archive/web/sacm/current/msg04631.html
[4] https://www.ietf.org/mail-archive/web/sacm/current/msg04637.html
[5] https://www.ietf.org/mail-archive/web/sacm/current/msg04630.html
[6] https://www.ietf.org/mail-archive/web/sacm/current/msg04650.html
[7] https://trac.ietf.org/trac/sacm/wiki/SacmVulnerabilityAssessmentScenario
[8] https://www.ietf.org/mail-archive/web/sacm/current/msg04697.html

v2.23.0 | Report a Bug | By Email