[sacm] EPCP and BCP Status

"Haynes Jr., Dan" <dhaynes@mitre.org> Mon, 02 December 2019 17:44 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 8C29D12003E for <sacm@ietfa.amsl.com>; Mon, 2 Dec 2019 09:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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.org
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 6VyAHZEAcerO for <sacm@ietfa.amsl.com>; Mon, 2 Dec 2019 09:43:58 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (smtpvbsrv1.mitre.org [198.49.146.234]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7322120048 for <sacm@ietf.org>; Mon, 2 Dec 2019 09:43:57 -0800 (PST)
Received: from smtpvbsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id DAEA233201D for <sacm@ietf.org>; Mon, 2 Dec 2019 12:43:56 -0500 (EST)
Received: from smtprhbv1.mitre.org (unknown [129.83.19.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpvbsrv1.mitre.org (Postfix) with ESMTPS id 897B6332017 for <sacm@ietf.org>; Mon, 2 Dec 2019 12:43:56 -0500 (EST)
Received: from mbfesmtp-mgt.mitre.org (unknown [198.49.146.235]) by smtprhbv1.mitre.org (Postfix) with ESMTP id 7991A80A98F for <sacm@ietf.org>; Mon, 2 Dec 2019 12:43:56 -0500 (EST)
Received: by mbfesmtp-mgt.mitre.org (Postfix, from userid 600) id 47RXXr3RpfzklC; Mon, 2 Dec 2019 17:43:32 +0000 (UTC)
Received: from GCC02-BL0-obe.outbound.protection.outlook.com (mail-bl2gcc02lp2104.outbound.protection.outlook.com [104.47.64.104]) by mbfesmtp-mgt.mitre.org (Postfix) with ESMTPS id 47RXXD4yvSzknf for <sacm@ietf.org>; Mon, 2 Dec 2019 17:43:24 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jm6YA0MsdPusrx/0Bx/27QHDmyIJlhmdClx0npJxV7SO/+vat0otyItwEJfAbzovZg0+TVcDMJVFD/Mn5rVrZbxxnzN8qPvqdfeD/kflivHuehzJJQxV8DvxSIQza2PBFVGl+HJzqkcD32Ovxt92s6LyHQNzYWM9mT0S8d8nTSt8zoWHFbPOTxxnXNonzk04Z18yhqZ8K4+0X3RjAOGUk1O185VCjfT1mWZQgPfwtiosPq8KY1uYUpJiqfaq8cUvSCHqg6SclcAUxeejpreTVJAIZJ1zk4BUhiIwluKA6+P0uEzIlLBTS9lcp3UZFBTEMX7kzM/LUTro1+GadC1xpw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0rfmVeHAib21MyMf/HNwqBqvHe1Nwn+ho9WHNwivIjU=; b=IO+nnDhtwZbBDQmDMU/8YPCZ/WgfngO5TCf9OYJcnyLkLWTuauvTuXau0/LZe8r6zvPrwSH8XuVMJiBARIEpy3tb8UFGPuMSDqupBn2X8QzSR9P3XxsMd0iDoolboeA0YNQ02JbIEnhYqgg+okOCO41TuyxcjeVtsZ79iIohr247ZVCUUwqyVALh0KDBvAPZt6wywJ7aGV9RDYKV9WnPBlZ0Pd+lwrBKLVMs5sQMd42D7Ac+olhGyx/yhnFxLvETfPbMDO4inWCxfftpgN4RoXuH880fxRhrppEUEJ7j9/FCxLHrbk01kHyYz0OVqFFyzKXP7N3+lAxV5C35YguosQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=mitre.org; dmarc=pass action=none header.from=mitre.org; dkim=pass header.d=mitre.org; arc=none
Received: from BY5PR09MB4486.namprd09.prod.outlook.com (52.135.41.138) by BY5PR09MB4357.namprd09.prod.outlook.com (52.135.41.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.18; Mon, 2 Dec 2019 17:43:22 +0000
Received: from BY5PR09MB4486.namprd09.prod.outlook.com ([fe80::891d:a0a5:63a1:f315]) by BY5PR09MB4486.namprd09.prod.outlook.com ([fe80::891d:a0a5:63a1:f315%7]) with mapi id 15.20.2495.014; Mon, 2 Dec 2019 17:43:22 +0000
From: "Haynes Jr., Dan" <dhaynes@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: EPCP and BCP Status
Thread-Index: AQHVqTf978St2I+jvUmKT4LvVAN9Ww==
Date: Mon, 02 Dec 2019 17:43:21 +0000
Message-ID: <C85093F2-9512-4C52-83BB-BA3CBD10745E@mitre.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1f.0.191110
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dhaynes@mitre.org;
x-originating-ip: [192.160.51.86]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: fefabe8b-3a30-40b5-90d3-08d7774f2011
x-ms-traffictypediagnostic: BY5PR09MB4357:
x-microsoft-antispam-prvs: <BY5PR09MB4357AB787353F7C504120A63A5430@BY5PR09MB4357.namprd09.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0239D46DB6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(376002)(346002)(136003)(366004)(53754006)(199004)(189003)(102836004)(6436002)(7736002)(6486002)(5640700003)(2351001)(99286004)(6916009)(186003)(33656002)(6506007)(26005)(6512007)(236005)(66446008)(64756008)(66556008)(66476007)(66616009)(66946007)(76116006)(91956017)(316002)(25786009)(5660300002)(36756003)(256004)(2616005)(71200400001)(58126008)(3846002)(5024004)(71190400001)(1730700003)(81156014)(81166006)(8676002)(8936002)(606006)(9326002)(6306002)(54896002)(66066001)(86362001)(14454004)(2906002)(6116002)(3480700005)(2501003)(966005)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR09MB4357; H:BY5PR09MB4486.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bVoDZVgC+Rupx3ep48gi3wIH3crieruXkfwkJkBflf43mHdVQUzS5Eg8ZA17IzwwO/IP6wfsk2boc07uF9Ahof2ao0+xUDzoj6QFK/g2FhvBZvYFqgkDGULK5ETwZ68tJuBI6R0soU7gnbNUX87RSkls7sQQlQxR7oZW7HL84tudkBhHMNcsFDk0vwEnRwomOnfZvt74WlM2UfGFGyF2lagFX9CW2dBIMiCXw7eOJ/8N5TgkRMts2nyaM8WaSk1XuN+sKqbUlUC0E33l1Z0aPWWSLVpWTIg6yxsBJGZctoQPqvo2NkK+uVqcn3Tj0P1BLDW++C9LdkNe0cLnm7xYx6fEP+UeGHVVYQ8F4O4TnVNEBJRVOtxpxV4kXaVWtLwF/HZqFk13aft6DBar95TBF4k1lvUinabUVlLqX+bvZC9HfNBQvdydrLK5dX01l/XAOViAMQIVj4js3chehgzFK4VfMycUf2kauzilRD2aY3c=
x-ms-exchange-transport-forked: True
Content-Type: multipart/mixed; boundary="_004_C85093F295124C5283BBBA3CBD10745Emitreorg_"
MIME-Version: 1.0
X-OriginatorOrg: mitre.org
X-MS-Exchange-CrossTenant-Network-Message-Id: fefabe8b-3a30-40b5-90d3-08d7774f2011
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Dec 2019 17:43:21.9133 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: sd2XE5B3MH73F2LQuit2nIoHx74IUZDoI+/LU3MsTKSj9JshI1/O6sm5mypry6Lz1Hf2aa7Zv5K40J9N3/sR2A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR09MB4357
X-MITRE: 8GQsMWxq66rxk57w
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.org; h=from:to:subject:date:message-id:content-type:mime-version; s=selector1; bh=0rfmVeHAib21MyMf/HNwqBqvHe1Nwn+ho9WHNwivIjU=; b=wdw0IiezPl2se/KplP9Krf0OUJfa030UhJbXViKtIodlbNAlCqN7XSbFK3/xFO4OYte7ZAYMn9QTGgcRf5HbMUaPPCp7wHjoNDJJrkbs2yR6MlvdxFcohx6KtiQNkWnD6SBBC7g2j4AOnKVVQDVAxY1kUJIZuq4Vj/YftuLdvMI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/t-hSYBu7Np0eYbP_JFsLgErgz0c>
Subject: [sacm] EPCP and BCP Status
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 02 Dec 2019 17:44:03 -0000

Hi Everyone,

Sorry in advance for the long email, but Jess mentioned at IETF 106, it was asked whether or not EPCP should be a BCP or Informational draft. Given that, I tried to go back and dig up some information and here’s what I found :).

Originally, EPCP was a Standards Track draft and in mid-2018, we changed its status to BCP (between -02 and -03). Also, around that time, there was a question on-list [1] as to whether or not it should be Standards Track or Informational where we re-iterated its BCP status.

1.      Is it going to be a Standard Track draft? Since I see you mentioned in the abstract it mainly describes the best practices, maybe an Informational draft is more suitable?

[Danny]: I think I forgot to change that in the last draft, but, we would like to see this draft published as a BCP since it discusses the best practices for using IETF and TCG standards for endpoint assessment.

In early 2019, we made further changes to the draft to better align it with the needs of a BCP draft (see attached slides).

Unfortunately, I couldn’t find any concrete information as to why its status was changed to BCP, but, I want to say someone suggested it and as a group we thought it made sense at the time. Without that concrete information, we should look at BCP 9 [2] which states:


                    The BCP subseries of the RFC series is designed to be a way to

                  standardize practices and the results of community deliberations.  A

                  BCP document is subject to the same basic set of procedures as

                  standards track documents and thus is a vehicle by which the IETF

                  community can define and ratify the community's best current thinking

                  on a statement of principle or on what is believed to be the best way

                  to perform some operations or IETF process function.

Given this, I think it is fair to say that EPCP represents the best way to perform posture collection when the collector resides on the endpoint. Specifically, it outlines six best practices (see Section 2 of EPCP) as well as how you can implement those best practices using existing IETF/ISO/TCG standards.

With all that said, does EPCP make sense as a BCP? Or, are there specific things that it is missing that make it a better candidate for an Informational draft?

Thanks,

Danny

[1] https://mailarchive.ietf.org/arch/msg/sacm/h4DU9TFF6LxEKmMySV-ftYD21GM
[2] https://tools.ietf.org/html/bcp9#page-1-15


Thanks,

Danny