
From nobody Fri Apr  5 18:01:57 2019
Return-Path: <noreply@github.com>
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 AADCD12029D for <sacm@ietfa.amsl.com>; Fri,  5 Apr 2019 18:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level: 
X-Spam-Status: No, score=-8.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 yqR4a3FAjMk9 for <sacm@ietfa.amsl.com>; Fri,  5 Apr 2019 18:01:54 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B27812029A for <sacm@ietf.org>; Fri,  5 Apr 2019 18:01:54 -0700 (PDT)
Date: Fri, 05 Apr 2019 18:01:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554512513; bh=Mt7XNhQTC9l0hI++jd0nLv10mRmXK8AbRYoqaAOGJlM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=rVkXVRNJO5QlUhyaEfh62o/OCeHMSC4v/fJ2jzXDu2rxFUU0r9K0TgOZQGrN1onVF qDAcHUsCYaN+kSzhFcLB7utuINTcviAFfvhCVmunpx+j5GxlyvAQsYLvxh3W6RO727 Ye+GAKxXR97O/K4YBXM69Niv8MCI3w+tCk8eKiI4=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d15f37e337d05bca6c47eadc5485576609fa2baa8192cf0000000118bfbc8192a169ce19a0fc3b@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/8@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca7fa8177912_3c13fa0032d45b4462d3"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/m71RfLDUEWwx-osqRyIdsfLYX5E>
Subject: [sacm] [sacmwg/draft-ietf-sacm-coswid] Added an IANA registry for CoSWID items supporting future extension. (#8)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Apr 2019 01:01:57 -0000

----==_mimepart_5ca7fa8177912_3c13fa0032d45b4462d3
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Cleaned up IANA registrations, fixing some inconsistencies in the table labels.
dded additional CDDL sockets for resource collection entries providing for additional extension points to address future SWID/CoSWID extensions.
Updated section on extension points to address new CDDL sockets and to reference the new IANA registry for items.
Removed unused references and added new references to address placeholder comments.
Also:
- Added changelog entries.
- Updated inline CDDL.
- Normalized use of links in the markdown.
You can view, comment on, or merge this pull request online at:

  https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8

-- Commit Summary --

  * Added an IANA registry for CoSWID items supporting future extension.

-- File Changes --

    M concise-swid-tag.cddl (28)
    M draft-ietf-sacm-coswid.md (582)

-- Patch Links --

https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.patch
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8

----==_mimepart_5ca7fa8177912_3c13fa0032d45b4462d3
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Cleaned up IANA registrations, fixing some inconsistencies in the table labels.<br>
dded additional CDDL sockets for resource collection entries providing for additional extension points to address future SWID/CoSWID extensions.<br>
Updated section on extension points to address new CDDL sockets and to reference the new IANA registry for items.<br>
Removed unused references and added new references to address placeholder comments.<br>
Also:</p>
<ul>
<li>Added changelog entries.</li>
<li>Updated inline CDDL.</li>
<li>Normalized use of links in the markdown.</li>
</ul>

<hr>

<h4>You can view, comment on, or merge this pull request online at:</h4>
<p>&nbsp;&nbsp;<a href='https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8</a></p>

<h4>Commit Summary</h4>
<ul>
  <li>Added an IANA registry for CoSWID items supporting future extension.</li>
</ul>

<h4>File Changes</h4>
<ul>
  <li>
    <strong>M</strong>
    <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8/files#diff-0">concise-swid-tag.cddl</a>
    (28)
  </li>
  <li>
    <strong>M</strong>
    <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8/files#diff-1">draft-ietf-sacm-coswid.md</a>
    (582)
  </li>
</ul>

<h4>Patch Links:</h4>
<ul>
  <li><a href='https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.patch'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.patch</a></li>
  <li><a href='https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.diff'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8.diff</a></li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AKbE0aZkxOoso0KaaI_VWfhBAc0iAYBVks5vd_IBgaJpZM4cf7sZ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AKbE0RbMDHu8MHz40SXwx9kUflBnsW5iks5vd_IBgaJpZM4cf7sZ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Added an IANA registry for CoSWID items supporting future extension. (#8)"}],"action":{"name":"View Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8",
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>

----==_mimepart_5ca7fa8177912_3c13fa0032d45b4462d3--


From nobody Fri Apr  5 18:02:50 2019
Return-Path: <noreply@github.com>
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 3005212029F for <sacm@ietfa.amsl.com>; Fri,  5 Apr 2019 18:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level: 
X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 MIAIxDX0sQrM for <sacm@ietfa.amsl.com>; Fri,  5 Apr 2019 18:02:46 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1314A12029A for <sacm@ietf.org>; Fri,  5 Apr 2019 18:02:46 -0700 (PDT)
Date: Fri, 05 Apr 2019 18:02:45 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554512565; bh=bg+eTqfYpgpGAU8eYgxNufqQZ5e3J6qo/BWGfKrRAWs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WfbZvJQkU9TTLTiGcfxwl1JXzfAOgKRXCVZSVuAgY7yBBJTz4NKuoGxEUzg1+EXJN 5iAHQsijc/1ALheBPgDttbqbqN5kBQtyLhPEtFMyWOn1fbOwafE+nOyJM6yQ9CoMPl +8cDb5NsOVm/brsNNKBaHX+9YLlxpsDSvlBf6F7c=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d160e2a7fe970c5aa9624c1fefe6a7b0a5eaca66b392cf0000000118bfbcb592a169ce19a0fc3b@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/8/issue_event/2257201508@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-coswid/pull/8@github.com>
References: <sacmwg/draft-ietf-sacm-coswid/pull/8@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca7fab51d42d_f3e3fc06bad45c44788b"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/pmG1K8cSCV9nxOXofVnFf8n2m-c>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-coswid] Added an IANA registry for CoSWID items supporting future extension. (#8)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Apr 2019 01:02:48 -0000

----==_mimepart_5ca7fab51d42d_f3e3fc06bad45c44788b
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #8 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8#event-2257201508
----==_mimepart_5ca7fab51d42d_f3e3fc06bad45c44788b
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Merged <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="429980731" data-permission-text="Issue title is private" data-url="https://github.com/sacmwg/draft-ietf-sacm-coswid/issues/8" data-hovercard-type="pull_request" data-hovercard-url="/sacmwg/draft-ietf-sacm-coswid/pull/8/hovercard" href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8">#8</a> into master.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8#event-2257201508">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AKbE0R5AJUNBnB6WB0ZZLKsDYu6YlhJHks5vd_I1gaJpZM4cf7sZ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AKbE0afnr_UyzR2mxR4I-I_FNqBfKwhIks5vd_I1gaJpZM4cf7sZ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Merged #8 into master."}],"action":{"name":"View Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8#event-2257201508"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8#event-2257201508",
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/8#event-2257201508",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ca7fab51d42d_f3e3fc06bad45c44788b--


From nobody Sat Apr  6 16:31:43 2019
Return-Path: <noreply@github.com>
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 315F312022E for <sacm@ietfa.amsl.com>; Sat,  6 Apr 2019 16:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 wwUW9bOpO1Kj for <sacm@ietfa.amsl.com>; Sat,  6 Apr 2019 16:31:40 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DAF81201F1 for <sacm@ietf.org>; Sat,  6 Apr 2019 16:31:40 -0700 (PDT)
Date: Sat, 06 Apr 2019 16:31:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554593498; bh=oqGbaufUQAUD+yclVza81ZMWbNIhHQbfkwvSy0IGZM8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=tt0APPyIu9nReZYukGsKe/8mic89rylne21r18ov08dpHSxS0CK3KhLQKWu2a35cU QTSbRiqskQrPbKkdorf5q3bGb8jJUjycD4JYpaCz9A6YtqMc8XsrWe4ilvFyWRxe8D NChdze73T2pzdKUyeUWUK9ufkYbMMvh+dzrYhQC8=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d127b9d981789d0d590fcdd9994d4d449fae5f00b892cf0000000118c0f8da92a169ce19a29beb@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/9@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca936dad5862_79c03fb7f4cd45c431803e"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/8h7CmMU8YtVci3rkKDN5Iz_zUys>
Subject: [sacm] =?utf-8?q?=5Bsacmwg/draft-ietf-sacm-coswid=5D_Added_missi?= =?utf-8?q?ng_=24=24meta-extension_socket_and_other_minor_changes_to_the_?= =?utf-8?b?4oCmICgjOSk=?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Apr 2019 23:31:42 -0000

----==_mimepart_5ca936dad5862_79c03fb7f4cd45c431803e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=A6CDDL.=0D
Performed a final editorial pass of the document, clarifying language, ma=
king term use more consistent, fixing references, and replacing lowercase=
 RFC2119 keywords.=0D
Added table with semantics for the link ownership item.=0D
You can view, comment on, or merge this pull request online at:=0D
=0D
  https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9=0D
=0D
-- Commit Summary --=0D
=0D
  * Added missing $$meta-extension socket and other minor changes to the =
CDDL.=0D
=0D
-- File Changes --=0D
=0D
    M concise-swid-tag.cddl (1)=0D
    M draft-ietf-sacm-coswid.md (433)=0D
=0D
-- Patch Links --=0D
=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.patch=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.diff=0D
=0D
-- =0D
You are receiving this because you are subscribed to this thread.=0D
Reply to this email directly or view it on GitHub:=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9=0D

----==_mimepart_5ca936dad5862_79c03fb7f4cd45c431803e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>=E2=80=A6CDDL.<br>=0D
Performed a final editorial pass of the document, clarifying language, ma=
king term use more consistent, fixing references, and replacing lowercase=
 RFC2119 keywords.<br>=0D
Added table with semantics for the link ownership item.</p>=0D
=0D
<hr>=0D
=0D
<h4>You can view, comment on, or merge this pull request online at:</h4>=0D=

<p>&nbsp;&nbsp;<a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswi=
d/pull/9'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9</a></p>=
=0D
=0D
<h4>Commit Summary</h4>=0D
<ul>=0D
  <li>Added missing $$meta-extension socket and other minor changes to th=
e CDDL.</li>=0D
</ul>=0D
=0D
<h4>File Changes</h4>=0D
<ul>=0D
  <li>=0D
    <strong>M</strong>=0D
    <a href=3D"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9/fi=
les#diff-0">concise-swid-tag.cddl</a>=0D
    (1)=0D
  </li>=0D
  <li>=0D
    <strong>M</strong>=0D
    <a href=3D"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9/fi=
les#diff-1">draft-ietf-sacm-coswid.md</a>=0D
    (433)=0D
  </li>=0D
</ul>=0D
=0D
<h4>Patch Links:</h4>=0D
<ul>=0D
  <li><a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.=
patch'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.patch</a><=
/li>=0D
  <li><a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.=
diff'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9.diff</a></l=
i>=0D
</ul>=0D
=0D
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/sacm=
wg/draft-ietf-sacm-coswid/pull/9">view it on GitHub</a>, or <a href=3D"ht=
tps://github.com/notifications/unsubscribe-auth/AKbE0YNdYIPmu_ylgrqICRhRk=
xUynOcUks5veS5agaJpZM4cgeJ2">mute the thread</a>.<img src=3D"https://gith=
ub.com/notifications/beacon/AKbE0ehVZwJLXfChxmXscM6cQF_MKePdks5veS5agaJpZ=
M4cgeJ2.gif" height=3D"1" width=3D"1" alt=3D"" /></p>=0D
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid=
","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository",=
"main_image_url":"https://github.githubassets.com/images/email/message_ca=
rds/header.png","avatar_image_url":"https://github.githubassets.com/image=
s/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url"=
:"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippet=
s":[{"icon":"DESCRIPTION","message":"Added missing $$meta-extension socke=
t and other minor changes to the =E2=80=A6 (#9)"}],"action":{"name":"View=
 Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/pu=
ll/9"}}}</script>=0D
<script type=3D"application/ld+json">[=0D
{=0D
"@context": "http://schema.org",=0D
"@type": "EmailMessage",=0D
"potentialAction": {=0D
"@type": "ViewAction",=0D
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9",=0D
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9",=0D
"name": "View Pull Request"=0D
},=0D
"description": "View this Pull Request on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=0D

----==_mimepart_5ca936dad5862_79c03fb7f4cd45c431803e--


From nobody Sat Apr  6 16:32:13 2019
Return-Path: <noreply@github.com>
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 2E9FC1201F1 for <sacm@ietfa.amsl.com>; Sat,  6 Apr 2019 16:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level: 
X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 KSdu3av5c1iM for <sacm@ietfa.amsl.com>; Sat,  6 Apr 2019 16:32:10 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7A812023B for <sacm@ietf.org>; Sat,  6 Apr 2019 16:32:10 -0700 (PDT)
Date: Sat, 06 Apr 2019 16:32:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554593529; bh=PCu6zSZ6LFU+J9h3bpM5Y+xcPUdy0zEaYKJOh2vXg18=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GDHHIHdqhvBKNU+xVx2vWkamsm+gzcY4S9vZ8jqTFQa5d6el7evoOqpznqKG3P1XH suVZiv7WN/eNKb4oaoHquAna2kRdwG7NwmXhtpFeEmRI08cd4FqZNXqox+DWCjOWHR 7AWfyN0r5pL5R2MJcFQdHJLNvUTJjii3Hrsc/fd8=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d1c944afca4cc59ac4783dab87fa9d6c62faa59fbe92cf0000000118c0f8f992a169ce19a29beb@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/9/issue_event/2257687226@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-coswid/pull/9@github.com>
References: <sacmwg/draft-ietf-sacm-coswid/pull/9@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca936f9b450e_3f043f8190cd45b44033fe"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/0oOnUi4OPMiOUzGlKC_9BBhkaHM>
Subject: Re: [sacm]  =?utf-8?q?=5Bsacmwg/draft-ietf-sacm-coswid=5D_Added_missi?= =?utf-8?q?ng_=24=24meta-extension_socket_and_other_minor_changes_to_the_?= =?utf-8?b?4oCmICgjOSk=?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Apr 2019 23:32:12 -0000

----==_mimepart_5ca936f9b450e_3f043f8190cd45b44033fe
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #9 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9#event-2257687226
----==_mimepart_5ca936f9b450e_3f043f8190cd45b44033fe
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Merged <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="430087147" data-permission-text="Issue title is private" data-url="https://github.com/sacmwg/draft-ietf-sacm-coswid/issues/9" data-hovercard-type="pull_request" data-hovercard-url="/sacmwg/draft-ietf-sacm-coswid/pull/9/hovercard" href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9">#9</a> into master.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9#event-2257687226">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AKbE0dRd-DyMze-U4nCcvpORI8UQgq0Dks5veS55gaJpZM4cgeJ2">mute the thread</a>.<img src="https://github.com/notifications/beacon/AKbE0SxYmPxQykkrwp2irOy8Grn1NSLUks5veS55gaJpZM4cgeJ2.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Merged #9 into master."}],"action":{"name":"View Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9#event-2257687226"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9#event-2257687226",
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/9#event-2257687226",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5ca936f9b450e_3f043f8190cd45b44033fe--


From nobody Tue Apr  9 05:52:22 2019
Return-Path: <noreply@github.com>
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 F18191207D4 for <sacm@ietfa.amsl.com>; Tue,  9 Apr 2019 05:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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=github.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 c1OkFgRPdlgK for <sacm@ietfa.amsl.com>; Tue,  9 Apr 2019 05:52:19 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 283B71207DA for <sacm@ietf.org>; Tue,  9 Apr 2019 05:52:19 -0700 (PDT)
Date: Tue, 09 Apr 2019 05:52:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554814338; bh=lAcekXDnbaD2nqYsGxKk/teAPTde8C3dEvvjhI7PvEI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=aSkIWEzWbBLpGeTl9D9pqaUpfkFg3jgDp/iR8wXOEEa0m6PIr2bSqyhwbyTrij8Hr WmmuZ6Q3huvphL50mueI0XttnBGJQTIMPIL0q4azG2CtPkvjkQbrYIDC6gYd7ecx0L hY5z9EqGuyu4vqLye88OqdQttDbEDah2diXSRNYo=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d15437468788735f8736051c56bb9771dfa6e4d1b392cf0000000118c4578292a169ce19afc769@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/10@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cac95824033_3d773fe9be6d45c45188d"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/tnPbY2gWNeVPbq4Zotc6_l0sR90>
Subject: [sacm] =?utf-8?q?=5Bsacmwg/draft-ietf-sacm-coswid=5D_Fixed_an_in?= =?utf-8?q?consistency_between_the_index_values_of_valid_value_lists_?= =?utf-8?b?4oCmICgjMTAp?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 09 Apr 2019 12:52:21 -0000

----==_mimepart_5cac95824033_3d773fe9be6d45c45188d
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=E2=80=A6and the IANA registry.=0D
=0D
Also fixed a wierd character encoding issue.=0D
You can view, comment on, or merge this pull request online at:=0D
=0D
  https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10=0D
=0D
-- Commit Summary --=0D
=0D
  * Fixed an inconsistency between the index values of valid value lists =
and the IANA registry.=0D
=0D
-- File Changes --=0D
=0D
    M concise-swid-tag.cddl (151)=0D
    M draft-ietf-sacm-coswid.md (66)=0D
=0D
-- Patch Links --=0D
=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10.patch=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10.diff=0D
=0D
-- =0D
You are receiving this because you are subscribed to this thread.=0D
Reply to this email directly or view it on GitHub:=0D
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10=0D

----==_mimepart_5cac95824033_3d773fe9be6d45c45188d
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>=E2=80=A6and the IANA registry.</p>=0D
<p>Also fixed a wierd character encoding issue.</p>=0D
=0D
<hr>=0D
=0D
<h4>You can view, comment on, or merge this pull request online at:</h4>=0D=

<p>&nbsp;&nbsp;<a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswi=
d/pull/10'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10</a></=
p>=0D
=0D
<h4>Commit Summary</h4>=0D
<ul>=0D
  <li>Fixed an inconsistency between the index values of valid value list=
s and the IANA registry.</li>=0D
</ul>=0D
=0D
<h4>File Changes</h4>=0D
<ul>=0D
  <li>=0D
    <strong>M</strong>=0D
    <a href=3D"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10/f=
iles#diff-0">concise-swid-tag.cddl</a>=0D
    (151)=0D
  </li>=0D
  <li>=0D
    <strong>M</strong>=0D
    <a href=3D"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10/f=
iles#diff-1">draft-ietf-sacm-coswid.md</a>=0D
    (66)=0D
  </li>=0D
</ul>=0D
=0D
<h4>Patch Links:</h4>=0D
<ul>=0D
  <li><a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10=
.patch'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10.patch</a=
></li>=0D
  <li><a href=3D'https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10=
.diff'>https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10.diff</a><=
/li>=0D
</ul>=0D
=0D
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/sacm=
wg/draft-ietf-sacm-coswid/pull/10">view it on GitHub</a>, or <a href=3D"h=
ttps://github.com/notifications/unsubscribe-auth/AKbE0ZBkQOjp45dogN2lexr-=
wWLZcJAFks5vfI0CgaJpZM4ckbDu">mute the thread</a>.<img src=3D"https://git=
hub.com/notifications/beacon/AKbE0clvDC1Xk3ehyitaHRGNYzB1EzH_ks5vfI0CgaJp=
ZM4ckbDu.gif" height=3D"1" width=3D"1" alt=3D"" /></p>=0D
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid=
","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository",=
"main_image_url":"https://github.githubassets.com/images/email/message_ca=
rds/header.png","avatar_image_url":"https://github.githubassets.com/image=
s/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url"=
:"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippet=
s":[{"icon":"DESCRIPTION","message":"Fixed an inconsistency between the i=
ndex values of valid value lists =E2=80=A6 (#10)"}],"action":{"name":"Vie=
w Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/p=
ull/10"}}}</script>=0D
<script type=3D"application/ld+json">[=0D
{=0D
"@context": "http://schema.org",=0D
"@type": "EmailMessage",=0D
"potentialAction": {=0D
"@type": "ViewAction",=0D
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10",=0D
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10",=0D
"name": "View Pull Request"=0D
},=0D
"description": "View this Pull Request on GitHub",=0D
"publisher": {=0D
"@type": "Organization",=0D
"name": "GitHub",=0D
"url": "https://github.com"=0D
}=0D
}=0D
]</script>=0D

----==_mimepart_5cac95824033_3d773fe9be6d45c45188d--


From nobody Tue Apr  9 05:52:51 2019
Return-Path: <noreply@github.com>
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 AD9C81207D4 for <sacm@ietfa.amsl.com>; Tue,  9 Apr 2019 05:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level: 
X-Spam-Status: No, score=-6.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 M2ApxvlWfZUV for <sacm@ietfa.amsl.com>; Tue,  9 Apr 2019 05:52:48 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62E161207E0 for <sacm@ietf.org>; Tue,  9 Apr 2019 05:52:44 -0700 (PDT)
Date: Tue, 09 Apr 2019 05:52:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554814363; bh=GIbFFSv9M/D2nc0OEKdPg1QaUxRyHqB92OiKIp942SU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=2YWHRqpcnnY7E7CuDD8dhj6x9UPxpl+brz46svSetT2bpkuxURLD5FN9CISParP/R aC9P5g67+TAu2YTv+cXVhxENYYbZj4py+2m2n0s9GxBKddALZKJ2joKKzNxhbazPe1 htDHtzVCdTOJQsmKMH87oCRmds8CGOB0cHOpH76Q=
From: David Waltermire <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-coswid <reply+00a6c4d161b6b0e8a2c17f811e39b858f7dd5af57f5468a992cf0000000118c4579b92a169ce19afc769@reply.github.com>
To: sacmwg/draft-ietf-sacm-coswid <draft-ietf-sacm-coswid@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-coswid/pull/10/issue_event/2262727203@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-coswid/pull/10@github.com>
References: <sacmwg/draft-ietf-sacm-coswid/pull/10@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cac959b5bd7c_7bb03f9e682d45c411792"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: david-waltermire-nist
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/7CulndoKalonxqWCBhnTtg-TJq4>
Subject: Re: [sacm]  =?utf-8?q?=5Bsacmwg/draft-ietf-sacm-coswid=5D_Fixed_an_in?= =?utf-8?q?consistency_between_the_index_values_of_valid_value_lists_?= =?utf-8?b?4oCmICgjMTAp?=
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 09 Apr 2019 12:52:50 -0000

----==_mimepart_5cac959b5bd7c_7bb03f9e682d45c411792
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Merged #10 into master.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10#event-2262727203
----==_mimepart_5cac959b5bd7c_7bb03f9e682d45c411792
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Merged <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="430950249" data-permission-text="Issue title is private" data-url="https://github.com/sacmwg/draft-ietf-sacm-coswid/issues/10" data-hovercard-type="pull_request" data-hovercard-url="/sacmwg/draft-ietf-sacm-coswid/pull/10/hovercard" href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10">#10</a> into master.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10#event-2262727203">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AKbE0a7BJP0pgFG8ZUSWcyQzmbAftzLOks5vfI0bgaJpZM4ckbDu">mute the thread</a>.<img src="https://github.com/notifications/beacon/AKbE0QkvI4WrBXixS3tuZSqsphfOm83Tks5vfI0bgaJpZM4ckbDu.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/sacmwg/draft-ietf-sacm-coswid","title":"sacmwg/draft-ietf-sacm-coswid","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Merged #10 into master."}],"action":{"name":"View Pull Request","url":"https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10#event-2262727203"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10#event-2262727203",
"url": "https://github.com/sacmwg/draft-ietf-sacm-coswid/pull/10#event-2262727203",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5cac959b5bd7c_7bb03f9e682d45c411792--


From nobody Fri Apr 12 17:42:26 2019
Return-Path: <dan@ehrlichserver.com>
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 4B050120447 for <sacm@ietfa.amsl.com>; Fri, 12 Apr 2019 17:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ehrlichserver.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 67q56uI_T5kx for <sacm@ietfa.amsl.com>; Fri, 12 Apr 2019 17:42:22 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 017381203C1 for <sacm@ietf.org>; Fri, 12 Apr 2019 17:42:21 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id v22so10407038lje.9 for <sacm@ietf.org>; Fri, 12 Apr 2019 17:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ehrlichserver.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=0j/NMTH4S3oL5OSMCedRvkkqzOWY+nNmqkQUaknGLsQ=; b=PgqEhlC48NWL1nOJcy0fZGVUvtlUsiqjkNrud+3YcNxWcQvt6N7nkWOgzlOzeivJzk dIoM72VxnTCMnsGup19/BQ31aRxuFsLwa7ShQKvkruOtBGSlwh2lLWeJH6N3rnqESmUR 3dX9JysxzUaSzEPRcHsLc/im1757DVBflPGyo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0j/NMTH4S3oL5OSMCedRvkkqzOWY+nNmqkQUaknGLsQ=; b=pfa1yXlTvUU0gdcxow3ODxnRGaFlh5Dw9rzq1ipWiljrim3KcqnjNELdEDXflIqQTj NlhXFVgCLNquB3FhN2/GV6q3TOX+DHXKEphYZ7CneqiHbtdFA1Jof8Cdfap/suYxvaZ/ LhXOecsEbVtf8RdUvhKIUC8xFkYQAOi4n7cTsylhSaN8AwxxdKlW6t/1Q7vwUp6NLs0f EtuwDsRnmHTg+BctjP3w96kaDvpL/WoA4ejV/TWmz6nwlxKW27bY9rH2bic1FO7G8mW4 Y1J/+p2PWJ2+/O+KdL/dSzucfitpHleock5DPZJ+dhBOp4iONxo5CP3+lXr4qUq6TzAq tOXA==
X-Gm-Message-State: APjAAAWngnLeGkHdExo7j7qzJ2ePmpvmxS97g09Ybqm5d3xAI1+8qjto cZbupEBcyCQ434Bsong+xVcH5ft4Vr3V3D9Iu3lgsw==
X-Google-Smtp-Source: APXvYqy7W4n+hOUQd+PBqsbLXIz0ILYVY3WulRMzZOXNjCV5nfEKc75T+jjRy4S1buaSwsuLse0maYdkRlANVy4Sawo=
X-Received: by 2002:a2e:8693:: with SMTP id l19mr31566322lji.47.1555116140141;  Fri, 12 Apr 2019 17:42:20 -0700 (PDT)
MIME-Version: 1.0
From: Dan Ehrlich <dan@ehrlichserver.com>
Date: Fri, 12 Apr 2019 17:42:08 -0700
Message-ID: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com>
To: "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001e2f2d05865eb131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/hz2irmTYfslw1OS2kOtGDm8vOrI>
Subject: [sacm] ECP question
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: Sat, 13 Apr 2019 00:42:24 -0000

--0000000000001e2f2d05865eb131
Content-Type: text/plain; charset="UTF-8"

In the RFC for ECP, there is a section that mentions the potential use of
MAC addresses for identifying endpoints.

My understanding is that there are many things wrong with MAC addresses
today, such as that they can now be changed randomly by software, can't
really be verified, can be spoofed easily, etc.

I cannot find the link I was using from yesterday, but can the MAC address
mention be removed from ECP?


Apologies if I viewed an old draft or if this was previously discussed,

Dan Ehrlich
Austin, Texas
https://linkedin.com/in/danehrlich/
<https://www.linkedin.com/in/danehrlich/>

--0000000000001e2f2d05865eb131
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In the RFC for ECP, there is a section that mentions the p=
otential use of MAC addresses for identifying endpoints.=C2=A0<div><br></di=
v><div>My understanding is that there are many things wrong with MAC addres=
ses today, such as that they can now be changed randomly by software, can&#=
39;t really be verified, can be spoofed easily, etc.</div><div><br></div><d=
iv>I cannot find the link I was using from yesterday, but can the MAC addre=
ss mention be removed from ECP?=C2=A0</div><div><br></div><div><br></div><d=
iv>Apologies if I viewed an old draft or if this was previously discussed,<=
/div><div><br>Dan Ehrlich</div><div>Austin, Texas</div><div><a href=3D"http=
s://www.linkedin.com/in/danehrlich/">https://linkedin.com/in/danehrlich/</a=
><br></div></div>

--0000000000001e2f2d05865eb131--


From nobody Fri Apr 12 17:45:42 2019
Return-Path: <dan@ehrlichserver.com>
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 5349112045A for <sacm@ietfa.amsl.com>; Fri, 12 Apr 2019 17:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ehrlichserver.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 M0KSujlecdAw for <sacm@ietfa.amsl.com>; Fri, 12 Apr 2019 17:45:38 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8370120453 for <sacm@ietf.org>; Fri, 12 Apr 2019 17:45:37 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id h16so10394197ljg.11 for <sacm@ietf.org>; Fri, 12 Apr 2019 17:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ehrlichserver.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=rGSZ940eo8BkgcDhbCpuZqA6k/a6QLPJ+kW12PVHbTs=; b=Ro4AzFZwgJCr13uHnG4HS+4UX1azlOnxHRC+hA8sxCyBLvlZ7h7YKJB4knX11LZyst EtcJg/XthXvpmpIDJeMwX7PDgznSA3RGgO18/WxLtVNi8a53jq/Kl3uGSkZqHHRJ846U mz00wp7qeq4EtBpIAX6vlbN8MKFeqvC7zjwRo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=rGSZ940eo8BkgcDhbCpuZqA6k/a6QLPJ+kW12PVHbTs=; b=LtLkKZ3MZPFoJNV18IjQVqqisDLgu2Dj7y+ZDpb9Omqk8PRZB5F8QSvReRql8YaxpK 3y8pWEazDFFyIoQcrecyYjoBSTzQvJX9/FWxEB8x2sCF0LmccHA0q/J5sQFqbLBMOk2Y 4TZIy3TtxyL5bCAtF8k3ZFYHQzteh987pwNZ/Yq/pYzH/pMxD0Vp4UI+3eGGA4SXzYTe SD/24vpm5IMQQqQ56q3qk7AJ3kGS6hPgB90rW8Yt+4wDCtXjbiqcWmixgcPyJR1KG9Xs yq7ZwNDQIxjWNlxbTQ8KKS0gChrwZeGeFDA4e86UQvRq7qtU5xSXYfzH26p6ipUG2q6m 00zg==
X-Gm-Message-State: APjAAAVKtYrwHXDEbG7i8Rnrag0Dain9ZdrAWQMDPDCJOL47KcFutMBh C4tiWz+7IYocMza26IdmxY8c67qvcvkfjvmTSJb2dcZlHjd48A==
X-Google-Smtp-Source: APXvYqxTMIKk9w6DuGnvbJzC7IhQmPSnBgknLOncCgaaYcylgDYPvvqpALNcmp2DXOkiMdQHMsVDp0TZmcZBYiw7rM4=
X-Received: by 2002:a2e:9d12:: with SMTP id t18mr31720570lji.163.1555116336163;  Fri, 12 Apr 2019 17:45:36 -0700 (PDT)
MIME-Version: 1.0
References: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com>
In-Reply-To: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com>
From: Dan Ehrlich <dan@ehrlichserver.com>
Date: Fri, 12 Apr 2019 17:45:24 -0700
Message-ID: <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com>
To: "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cd312205865ebc0b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/91rDyxINbIVWM4cGLlGv25Ylcdw>
Subject: Re: [sacm] ECP question
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: Sat, 13 Apr 2019 00:45:41 -0000

--000000000000cd312205865ebc0b
Content-Type: text/plain; charset="UTF-8"

Link I mentioned:
https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/?include_text=1

Section 3.2.1

On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich <dan@ehrlichserver.com> wrote:

> In the RFC for ECP, there is a section that mentions the potential use of
> MAC addresses for identifying endpoints.
>
> My understanding is that there are many things wrong with MAC addresses
> today, such as that they can now be changed randomly by software, can't
> really be verified, can be spoofed easily, etc.
>
> I cannot find the link I was using from yesterday, but can the MAC address
> mention be removed from ECP?
>
>
> Apologies if I viewed an old draft or if this was previously discussed,
>
> Dan Ehrlich
> Austin, Texas
> https://linkedin.com/in/danehrlich/
> <https://www.linkedin.com/in/danehrlich/>
>

--000000000000cd312205865ebc0b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Link I mentioned:=C2=A0<a href=3D"https://datatracker.ietf=
.org/doc/draft-ietf-sacm-ecp/?include_text=3D1">https://datatracker.ietf.or=
g/doc/draft-ietf-sacm-ecp/?include_text=3D1</a><div><br></div><div>Section =
3.2.1</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich &lt;<a href=3D"mailt=
o:dan@ehrlichserver.com">dan@ehrlichserver.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">In the RFC f=
or ECP, there is a section that mentions the potential use of MAC addresses=
 for identifying endpoints.=C2=A0<div><br></div><div>My understanding is th=
at there are many things wrong with MAC addresses today, such as that they =
can now be changed randomly by software, can&#39;t really be verified, can =
be spoofed easily, etc.</div><div><br></div><div>I cannot find the link I w=
as using from yesterday, but can the MAC address mention be removed from EC=
P?=C2=A0</div><div><br></div><div><br></div><div>Apologies if I viewed an o=
ld draft or if this was previously discussed,</div><div><br>Dan Ehrlich</di=
v><div>Austin, Texas</div><div><a href=3D"https://www.linkedin.com/in/daneh=
rlich/" target=3D"_blank">https://linkedin.com/in/danehrlich/</a><br></div>=
</div>
</blockquote></div>

--000000000000cd312205865ebc0b--


From nobody Mon Apr 15 12:45:45 2019
Return-Path: <stephen.banghart@nist.gov>
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 A7D2212037F; Mon, 15 Apr 2019 12:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nist.gov
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 Ezgz6C89g70b; Mon, 15 Apr 2019 12:45:39 -0700 (PDT)
Received: from GCC01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0719.outbound.protection.outlook.com [IPv6:2a01:111:f400:fd00::719]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F117F1201C5; Mon, 15 Apr 2019 12:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nist.gov; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=52UhCEhWkR0F05c1Gw6jYVVWqoY1NpwMJtx99g/wdI8=; b=OfsoKjvkQjHLCDfIRvJXlWC2nctdfTwzfFyhuP9rVNpUX+lIxuwib3sGBZTjDoIU3cuf6JYPclSyGwSaZ8WLFovShebFUwkbOHbcXyNV2e6BFKSXvcLNTvRU7KzfN+vetFW36y5OA+H5dREuSSi5/VuCrfufKbKSZkDaFTZjMPA=
Received: from BN3PR09MB0609.namprd09.prod.outlook.com (10.160.120.12) by BN3PR09MB0611.namprd09.prod.outlook.com (10.160.120.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.19; Mon, 15 Apr 2019 19:45:32 +0000
Received: from BN3PR09MB0609.namprd09.prod.outlook.com ([fe80::1ce5:2c44:3260:75d3]) by BN3PR09MB0609.namprd09.prod.outlook.com ([fe80::1ce5:2c44:3260:75d3%8]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019 19:45:32 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: Dan Ehrlich <dan=40ehrlichserver.com@dmarc.ietf.org>, "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: [sacm] ECP question
Thread-Index: AQHU8ZHTJVTYrjWYtkWD91mq6GEQnqY5QTgAgARe/YA=
Date: Mon, 15 Apr 2019 19:45:32 +0000
Message-ID: <BN3PR09MB060951DE7B0D504F11BEBCD1F02B0@BN3PR09MB0609.namprd09.prod.outlook.com>
References: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com> <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com>
In-Reply-To: <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.196.176]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 63be751d-d791-4804-08dd-08d6c1daebfb
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN3PR09MB0611; 
x-ms-traffictypediagnostic: BN3PR09MB0611:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <BN3PR09MB0611F8D4C1967B28F321E225F02B0@BN3PR09MB0611.namprd09.prod.outlook.com>
x-forefront-prvs: 000800954F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(346002)(136003)(39860400002)(376002)(199004)(189003)(76176011)(110136005)(478600001)(2501003)(54896002)(446003)(71190400001)(186003)(9686003)(68736007)(53936002)(6306002)(66066001)(316002)(11346002)(45080400002)(229853002)(52536014)(476003)(71200400001)(33656002)(55016002)(486006)(790700001)(3846002)(236005)(6116002)(74316002)(7736002)(2906002)(106356001)(14444005)(99286004)(7696005)(105586002)(8676002)(53546011)(102836004)(86362001)(97736004)(14454004)(6506007)(81156014)(966005)(6436002)(6246003)(8936002)(256004)(26005)(25786009)(606006)(5660300002)(81166006); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR09MB0611; H:BN3PR09MB0609.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 0/HYrsFVZvQ8jdcI/8ksKYnpBjjF70ZuuKnxBLZQ4Pc4Ab+IEaSc7EedPEn5iAFwtejBzZIRWsGhTfZtRB/51iJkeOkoO2TqlqgwzesE54ZuFzt85owxGJr2E7EXKa7V/rGQO0fTRhHtz/T5UQQtuntGDgkozbI1Lf1JM/CSPIH9Zz4Q/LwSU1LqKFXICTrbIsvLW7+sDUUfdrzmpc9kOln9GeYNTBZFkC4vSlCSmrOaMLgBCH5F8dFndEhGwY9ndq9sC1CEv8bpq9E5hNa8CFriX18HkuZXVtkd3s36Hg5R8mza/fl9xEGhGE8Dw0jhpwzZw+rj9E7I55Vw3NA5KKkR63KfPugmkPTvDOnZtuTTJqfhe3ytfQpdPjtCv9Rh6rJPj2PhlpQszjCfdRLognV3QkyuIqGeeP1tKSlZC54=
Content-Type: multipart/alternative; boundary="_000_BN3PR09MB060951DE7B0D504F11BEBCD1F02B0BN3PR09MB0609namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-Network-Message-Id: 63be751d-d791-4804-08dd-08d6c1daebfb
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2019 19:45:32.4000 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR09MB0611
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/uBEbpPBf3GZZb5MF0cuvoeBYJkc>
Subject: Re: [sacm] ECP question
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, 15 Apr 2019 19:45:44 -0000

--_000_BN3PR09MB060951DE7B0D504F11BEBCD1F02B0BN3PR09MB0609namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RGFuLA0KDQpUaGUgbGluayB5b3UgcG9zdGVkIGhhZCBhIHNtYWxsIHR5cG8sIGhlcmUgaXMgYSBs
aW5rIHRvIHRoZSBkYXRhdHJhY2tlciBwYWdlIGZvciB0aGUgZHJhZnQ6IGh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtc2FjbS1lY3AvDQoNCkNvbW1lbnRzIGFzIGEg
bm9uLWF1dGhvcjoNClRoZSByZWZlcmVuY2UgdG8gTUFDIEFkZHJlc3NlcyBoZXJlIGlzIG9ubHkg
cmVhbGx5IGdpdmVuIGFzIGFuIGV4YW1wbGUsIGl04oCZcyBub3QgYSByZXF1aXJlbWVudCBvciBl
dmVuIG11Y2ggb2YgYSBzdWdnZXN0aW9uLiBXaGlsZSBpdOKAmXMgdHJ1ZSB0aGF0IE1BQyBhZGRy
ZXNzZXMgYXJlIGR1YmlvdXNseSB1c2VmdWwgdG9kYXksIHRoZXkgYXJlIHN0aWxsIHZhbGlkIHRv
IHVzZSBhcyBpZGVudGlmaWVycywgYW5kIGFyZSBzdGlsbCBwb3RlbnRpYWxseSB1c2VmdWwgYXMg
aWRlbnRpZnlpbmcgaW5mb3JtYXRpb24gaW4gdGhlIGVudGVycHJpc2UgZW5kcG9pbnQgY29sbGVj
dGlvbiBzY2VuYXJpbyAoeW91IG1vc3RseSB0cnVzdCB0aGUgZW5kcG9pbnRzIGluIHF1ZXN0aW9u
KS4NCg0KUmVtb3ZpbmcgdGhlIHJlZmVyZW5jZSBlbnRpcmVseSBwcm9iYWJseSB3b3VsZG7igJl0
IGh1cnQgYW55dGhpbmcsIGJ1dCB0aGUgdHJ1dGggaXMgdGhhdCBwZW9wbGUgdXNlIE1BQyBhZGRy
ZXNzZXMgdG8gdHJhY2sgbWFjaGluZXMgdG9kYXksIGFuZCBwb2ludGluZyBvdXQgdGhhdCB0aGV5
IGNhbiBiZSB1c2VkIGluIHRoaXMgYXJjaGl0ZWN0dXJlIGFzIGFuIElEIGlzLCBJTU8sIHdvcnRo
d2hpbGUuDQoNClBlcmhhcHMgYSBub3RlIG9uIE1BQyBhZGRyZXNzZXMgKEFuZCBtb3N0IGhhcmR3
YXJlIElEcykgYmVpbmcgZmxpbXN5IGNvdWxkIGJlIHByZXNlbnQgaW4gdGhlIFNlY3VyaXR5IENv
bnNpZGVyYXRpb25zLg0KDQpDaGVlcnMsDQpTdGVwaGVuIEJhbmdoYXJ0DQoNCg0KRnJvbTogc2Fj
bSA8c2FjbS1ib3VuY2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgRGFuIEVocmxpY2gNClNlbnQ6
IEZyaWRheSwgQXByaWwgMTIsIDIwMTkgODo0NSBQTQ0KVG86IGRyYWZ0LWlldGYtc2FjbS1lY3BA
aWV0Zi5vcmc7IHNhY21AaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbc2FjbV0gRUNQIHF1ZXN0aW9u
DQoNCkxpbmsgSSBtZW50aW9uZWQ6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWlldGYtc2FjbS1lY3AvP2luY2x1ZGVfdGV4dD0xPGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi4ub3JnL2RvYy9kcmFmdC1pZXRmLXNhY20tZWNwLz9pbmNsdWRlX3RleHQ9MT4NCg0KU2VjdGlv
biAzLjIuMQ0KDQpPbiBGcmksIEFwciAxMiwgMjAxOSBhdCA1OjQyIFBNIERhbiBFaHJsaWNoIDxk
YW5AZWhybGljaHNlcnZlci5jb208bWFpbHRvOmRhbkBlaHJsaWNoc2VydmVyLmNvbT4+IHdyb3Rl
Og0KSW4gdGhlIFJGQyBmb3IgRUNQLCB0aGVyZSBpcyBhIHNlY3Rpb24gdGhhdCBtZW50aW9ucyB0
aGUgcG90ZW50aWFsIHVzZSBvZiBNQUMgYWRkcmVzc2VzIGZvciBpZGVudGlmeWluZyBlbmRwb2lu
dHMuDQoNCk15IHVuZGVyc3RhbmRpbmcgaXMgdGhhdCB0aGVyZSBhcmUgbWFueSB0aGluZ3Mgd3Jv
bmcgd2l0aCBNQUMgYWRkcmVzc2VzIHRvZGF5LCBzdWNoIGFzIHRoYXQgdGhleSBjYW4gbm93IGJl
IGNoYW5nZWQgcmFuZG9tbHkgYnkgc29mdHdhcmUsIGNhbid0IHJlYWxseSBiZSB2ZXJpZmllZCwg
Y2FuIGJlIHNwb29mZWQgZWFzaWx5LCBldGMuDQoNCkkgY2Fubm90IGZpbmQgdGhlIGxpbmsgSSB3
YXMgdXNpbmcgZnJvbSB5ZXN0ZXJkYXksIGJ1dCBjYW4gdGhlIE1BQyBhZGRyZXNzIG1lbnRpb24g
YmUgcmVtb3ZlZCBmcm9tIEVDUD8NCg0KDQpBcG9sb2dpZXMgaWYgSSB2aWV3ZWQgYW4gb2xkIGRy
YWZ0IG9yIGlmIHRoaXMgd2FzIHByZXZpb3VzbHkgZGlzY3Vzc2VkLA0KDQpEYW4gRWhybGljaA0K
QXVzdGluLCBUZXhhcw0KaHR0cHM6Ly9saW5rZWRpbi5jb20vaW4vZGFuZWhybGljaC88aHR0cHM6
Ly9nY2MwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJG
JTJGd3d3LmxpbmtlZGluLmNvbSUyRmluJTJGZGFuZWhybGljaCUyRiZkYXRhPTAyJTdDMDElN0Nz
dGVwaGVuLmJhbmdoYXJ0JTQwbmlzdC5nb3YlN0M2NmRiYWQ5MDcyOTk0MDFhYWNiODA4ZDZiZmE5
NjljZCU3QzJhYjVkODJmZDhmYTQ3OTdhOTNlMDU0NjU1YzYxZGVjJTdDMSU3QzAlN0M2MzY5MDcx
MzE2OTMxODg2ODYmc2RhdGE9cW4xNDNFb2xBMUdoJTJCVSUyRk1mNmR3RWhmUDEyJTJCVlhkSThU
VG4wa0VYNHpHbyUzRCZyZXNlcnZlZD0wPg0K

--_000_BN3PR09MB060951DE7B0D504F11BEBCD1F02B0BN3PR09MB0609namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4w
aW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjEN
Cgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3ht
bD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6
ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBl
bGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxp
bms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkRhbiw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIGxpbmsg
eW91IHBvc3RlZCBoYWQgYSBzbWFsbCB0eXBvLCBoZXJlIGlzIGEgbGluayB0byB0aGUgZGF0YXRy
YWNrZXIgcGFnZSBmb3IgdGhlIGRyYWZ0Og0KPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1zYWNtLWVjcC8iPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LWlldGYtc2FjbS1lY3AvPC9hPg0KPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkNvbW1lbnRzIGFzIGEgbm9uLWF1dGhvcjo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlRoZSByZWZlcmVuY2UgdG8gTUFDIEFkZHJlc3NlcyBoZXJlIGlzIG9ubHkgcmVh
bGx5IGdpdmVuIGFzIGFuIGV4YW1wbGUsIGl04oCZcyBub3QgYSByZXF1aXJlbWVudCBvciBldmVu
IG11Y2ggb2YgYSBzdWdnZXN0aW9uLiBXaGlsZSBpdOKAmXMgdHJ1ZSB0aGF0IE1BQyBhZGRyZXNz
ZXMgYXJlIGR1YmlvdXNseSB1c2VmdWwgdG9kYXksIHRoZXkgYXJlIHN0aWxsIHZhbGlkIHRvIHVz
ZSBhcyBpZGVudGlmaWVycywgYW5kDQogYXJlIHN0aWxsIHBvdGVudGlhbGx5IHVzZWZ1bCBhcyBp
ZGVudGlmeWluZyBpbmZvcm1hdGlvbiBpbiB0aGUgZW50ZXJwcmlzZSBlbmRwb2ludCBjb2xsZWN0
aW9uIHNjZW5hcmlvICh5b3UgbW9zdGx5IHRydXN0IHRoZSBlbmRwb2ludHMgaW4gcXVlc3Rpb24p
LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5SZW1vdmluZyB0aGUgcmVmZXJlbmNlIGVudGlyZWx5
IHByb2JhYmx5IHdvdWxkbuKAmXQgaHVydCBhbnl0aGluZywgYnV0IHRoZSB0cnV0aCBpcyB0aGF0
IHBlb3BsZSB1c2UgTUFDIGFkZHJlc3NlcyB0byB0cmFjayBtYWNoaW5lcyB0b2RheSwgYW5kIHBv
aW50aW5nIG91dCB0aGF0IHRoZXkgY2FuIGJlIHVzZWQgaW4gdGhpcyBhcmNoaXRlY3R1cmUgYXMg
YW4gSUQgaXMsIElNTywgd29ydGh3aGlsZS4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QZXJo
YXBzIGEgbm90ZSBvbiBNQUMgYWRkcmVzc2VzIChBbmQgbW9zdCBoYXJkd2FyZSBJRHMpIGJlaW5n
IGZsaW1zeSBjb3VsZCBiZSBwcmVzZW50IGluIHRoZSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucy48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+U3RlcGhlbiBCYW5naGFydDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBzYWNt
ICZsdDtzYWNtLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IDxiPk9uIEJlaGFsZiBPZiA8L2I+DQpEYW4g
RWhybGljaDxicj4NCjxiPlNlbnQ6PC9iPiBGcmlkYXksIEFwcmlsIDEyLCAyMDE5IDg6NDUgUE08
YnI+DQo8Yj5Ubzo8L2I+IGRyYWZ0LWlldGYtc2FjbS1lY3BAaWV0Zi5vcmc7IHNhY21AaWV0Zi5v
cmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtzYWNtXSBFQ1AgcXVlc3Rpb248bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkxpbmsgSSBtZW50aW9uZWQ6Jm5ic3A7PGEgaHJlZj0iaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLi5vcmcvZG9jL2RyYWZ0LWlldGYtc2FjbS1lY3AvP2luY2x1
ZGVfdGV4dD0xIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLXNh
Y20tZWNwLz9pbmNsdWRlX3RleHQ9MTwvYT48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlNlY3Rpb24gMy4yLjE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gRnJpLCBBcHIgMTIsIDIwMTkgYXQgNTo0MiBQ
TSBEYW4gRWhybGljaCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRhbkBlaHJsaWNoc2VydmVyLmNvbSI+
ZGFuQGVocmxpY2hzZXJ2ZXIuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkluIHRoZSBSRkMgZm9yIEVDUCwgdGhlcmUgaXMgYSBz
ZWN0aW9uIHRoYXQgbWVudGlvbnMgdGhlIHBvdGVudGlhbCB1c2Ugb2YgTUFDIGFkZHJlc3NlcyBm
b3IgaWRlbnRpZnlpbmcgZW5kcG9pbnRzLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+TXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IHRoZXJlIGFyZSBt
YW55IHRoaW5ncyB3cm9uZyB3aXRoIE1BQyBhZGRyZXNzZXMgdG9kYXksIHN1Y2ggYXMgdGhhdCB0
aGV5IGNhbiBub3cgYmUgY2hhbmdlZCByYW5kb21seSBieSBzb2Z0d2FyZSwgY2FuJ3QgcmVhbGx5
IGJlIHZlcmlmaWVkLCBjYW4gYmUgc3Bvb2ZlZCBlYXNpbHksIGV0Yy48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBjYW5ub3QgZmluZCB0aGUg
bGluayBJIHdhcyB1c2luZyBmcm9tIHllc3RlcmRheSwgYnV0IGNhbiB0aGUgTUFDIGFkZHJlc3Mg
bWVudGlvbiBiZSByZW1vdmVkIGZyb20gRUNQPyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFwb2xvZ2llcyBpZiBJIHZpZXdlZCBh
biBvbGQgZHJhZnQgb3IgaWYgdGhpcyB3YXMgcHJldmlvdXNseSBkaXNjdXNzZWQsPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQpEYW4gRWhy
bGljaDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
QXVzdGluLCBUZXhhczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PGEgaHJlZj0iaHR0cHM6Ly9nY2MwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRs
b29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LmxpbmtlZGluLmNvbSUyRmluJTJGZGFuZWhy
bGljaCUyRiZhbXA7ZGF0YT0wMiU3QzAxJTdDc3RlcGhlbi5iYW5naGFydCU0MG5pc3QuZ292JTdD
NjZkYmFkOTA3Mjk5NDAxYWFjYjgwOGQ2YmZhOTY5Y2QlN0MyYWI1ZDgyZmQ4ZmE0Nzk3YTkzZTA1
NDY1NWM2MWRlYyU3QzElN0MwJTdDNjM2OTA3MTMxNjkzMTg4Njg2JmFtcDtzZGF0YT1xbjE0M0Vv
bEExR2glMkJVJTJGTWY2ZHdFaGZQMTIlMkJWWGRJOFRUbjBrRVg0ekdvJTNEJmFtcDtyZXNlcnZl
ZD0wIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9saW5rZWRpbi5jb20vaW4vZGFuZWhybGljaC88
L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_BN3PR09MB060951DE7B0D504F11BEBCD1F02B0BN3PR09MB0609namp_--


From nobody Fri Apr 26 05:52:45 2019
Return-Path: <jmfmckay@gmail.com>
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 F2FC1120045; Fri, 26 Apr 2019 05:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 y4VfBH7Iyysa; Fri, 26 Apr 2019 05:52:40 -0700 (PDT)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC6FC120183; Fri, 26 Apr 2019 05:52:40 -0700 (PDT)
Received: by mail-it1-x12f.google.com with SMTP id y10so5599991itc.1; Fri, 26 Apr 2019 05:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nmUPE0TG85bi4JYlzQdNs8jdQPLAfQ9IMNHZspRuMg0=; b=NSftfKcvAGbL26+Xt4dLro3fSfXgeNJyNAGS8Mi0GTgB3vWoJfLi5dGP6HW8Jjtibq oql5WrSZDYAW2uRXrzPDmWQ2rNQE4gSAdYIiwMiXhcSgm7Lpcr58nGiRwVOInpSP8vCp 7dG7LuhlR8yAWB/JeQM3iwadIkF8yEH+qN7tnjGDPUpgxJMnskHUPGCauFQaYXMaqkmF xT3SG9eV3eCZOykaCfQS1hNOzP3iNfRui0TVrbAWUBHf0fXnTawYSV5Ey2SbSJvz2GF+ G+v7084E45I3T5PFD897j/Rf17Wa8SieHxHRmFBR5lPKtti9Lww+eAbeavVbqT8rM3qw QqYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nmUPE0TG85bi4JYlzQdNs8jdQPLAfQ9IMNHZspRuMg0=; b=jK4dYjWof552jZzs5sszhGy562zTe3C5FlyEsJ4LNWL+9PpG3O8eDUACldGD33fJ+Y NtBPOHZ7g5QjCFdwJ0FBjm0uWWnTks9tfGi8caLz0KeTVupaPMRnYTwvD8QOolHlDAXm EUU4dG6+R4+5gkGYTXvuskPHlkzwXKCyDyjc49v/OmPuIs5tzXWZ+JbEbARZwdCh9rV1 LD1+a9h7sJxRyGT4v8Zy5PyCTaScU4VoC0KRCRpPwItaOSSYMfuh+XvqhAcoBPkr++RQ eF4I8UpYYsazeeWO6Oh/rrcrU0wkufx3WEjEJQmX6ZIsf8nl7c5rh5p7AaxnuLM1JY6o Lu0A==
X-Gm-Message-State: APjAAAVDXWCEoN8H40Ty/Z9NwfNc99Eh1tywryRxsEslFe3MkMKe9aaH 8ytlD80/97vz6L7rogqyMgs9eWMucWzVVgqlXuNUJyVu
X-Google-Smtp-Source: APXvYqwEgeTCLT+z0Qy/w4judafO3pblxdOaUDPEpPZYk19RMp0Q2HBeBMNOJhCDidxuce2Tg4R2Ygu9sG4wyQc9DxE=
X-Received: by 2002:a24:22ca:: with SMTP id o193mr7981217ito.131.1556283159925;  Fri, 26 Apr 2019 05:52:39 -0700 (PDT)
MIME-Version: 1.0
References: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com> <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com>
In-Reply-To: <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com>
From: Jessica Fitzgerald-McKay <jmfmckay@gmail.com>
Date: Fri, 26 Apr 2019 08:52:27 -0400
Message-ID: <CAM+R6NXa3WfxYk+unocaUGe=7B_fF0t61GdT3iCFDe0DD0yDFw@mail.gmail.com>
To: Dan Ehrlich <dan=40ehrlichserver.com@dmarc.ietf.org>
Cc: "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eada0c05876e686a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/1PpY5C7aal9rO_E7vlPBSG1yKx8>
Subject: Re: [sacm] ECP question
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: Fri, 26 Apr 2019 12:52:43 -0000

--000000000000eada0c05876e686a
Content-Type: text/plain; charset="UTF-8"

Dan,


Thank you for the review! Your understanding of MAC addresses mirrors mine:
they are not trustworthy as a sole device identifier. I think that, despite
that, they are still worth collection, for two reasons:

1) For device identity correlation-- For some network analytics, the MAC
address is what they can see. These analytics should have the capability to
correlate the behavior they see from an endpoint with a particular MAC
address to a better device identifier. One way to do that is to provide all
the identifiers an endpoint has (IP address, MAC address, device
certificate, etc.) to the CMDB. For traditional endpoints, the ECP requires
IF- IMC and (on the server side) IF-IMV. These interfaces allow endpoints
to share multiple forms of identity to the server, and then stored in the
CMDB for this sort of use case.

2) For attack identification-- ECP enables event-driven collection of
endpoint data. That is, if something changes on the endpoint, ECP enables
that change to be immediately (or, close to immediately) sent to the
server, and then to the CMDB. An endpoint could share any changes to its
MAC address as a part of that event-driven collection, which would help
network tools notice a malicious change in near-real-time.

Given these reasons, I would like to keep MAC addresses as a type of device
identity in the ECP.

I wonder if we could resolve your comments by including a note in the
security considerations about the trust limitations of MAC addresses. We
can say that they really should not be used as a sole device identifier,
and, if other identities can be reported, they really ought to be collected
at the same time as a MAC address. What do you think?

Thanks again for taking the time to share your thoughts!

Jess

On Fri, Apr 12, 2019 at 8:45 PM Dan Ehrlich <dan=
40ehrlichserver.com@dmarc.ietf.org> wrote:

> Link I mentioned:
> https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/?include_text=1
> <https://datatracker.ietf..org/doc/draft-ietf-sacm-ecp/?include_text=1>
>
> Section 3.2.1
>
> On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich <dan@ehrlichserver.com> wrote:
>
>> In the RFC for ECP, there is a section that mentions the potential use of
>> MAC addresses for identifying endpoints.
>>
>> My understanding is that there are many things wrong with MAC addresses
>> today, such as that they can now be changed randomly by software, can't
>> really be verified, can be spoofed easily, etc.
>>
>> I cannot find the link I was using from yesterday, but can the MAC
>> address mention be removed from ECP?
>>
>>
>> Apologies if I viewed an old draft or if this was previously discussed,
>>
>> Dan Ehrlich
>> Austin, Texas
>> https://linkedin.com/in/danehrlich/
>> <https://www.linkedin.com/in/danehrlich/>
>>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>

--000000000000eada0c05876e686a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)">Da=
n,<br><br><br></div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)"=
>Thank you for the review! Your understanding of MAC addresses mirrors mine=
: they are not trustworthy as a sole device identifier. I think that, despi=
te that, they are still worth collection, for two reasons:<br><br></div><di=
v class=3D"gmail_default" style=3D"color:rgb(0,0,0)">1) For device identity=
 correlation-- For some network analytics, the MAC address is what they can=
 see. These analytics should have the capability to correlate the behavior =
they see from an endpoint with a particular MAC address to a better device =
identifier. One way to do that is to provide all the identifiers an endpoin=
t has (IP address, MAC address, device certificate, etc.) to the CMDB. For =
traditional endpoints, the ECP requires IF- IMC and (on the server side) IF=
-IMV. These interfaces allow endpoints to share multiple forms of identity =
to the server, and then stored in the CMDB for this sort of use case.<br><b=
r></div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)">2) For atta=
ck identification-- ECP enables event-driven collection of endpoint data. T=
hat is, if something changes on the endpoint, ECP enables that change to be=
 immediately (or, close to immediately) sent to the server, and then to the=
 CMDB. An endpoint could share any changes to its MAC address as a part of =
that event-driven collection, which would help network tools notice a malic=
ious change in near-real-time.<br><br></div><div class=3D"gmail_default" st=
yle=3D"color:rgb(0,0,0)">Given these reasons, I would like to keep MAC addr=
esses as a type of device identity in the ECP.<br><br></div><div class=3D"g=
mail_default" style=3D"color:rgb(0,0,0)">I wonder if we could resolve your =
comments by including a note in the security considerations about the trust=
 limitations of MAC addresses. We can say that they really should not be us=
ed as a sole device identifier, and, if other identities can be reported, t=
hey really ought to be collected at the same time as a MAC address. What do=
 you think?<br><br></div><div class=3D"gmail_default" style=3D"color:rgb(0,=
0,0)">Thanks again for taking the time to share your thoughts!<br><br></div=
><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)">Jess<br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On F=
ri, Apr 12, 2019 at 8:45 PM Dan Ehrlich &lt;dan=3D<a href=3D"mailto:40ehrli=
chserver.com@dmarc.ietf.org">40ehrlichserver.com@dmarc.ietf.org</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"=
ltr">Link I mentioned:=C2=A0<a href=3D"https://datatracker.ietf..org/doc/dr=
aft-ietf-sacm-ecp/?include_text=3D1" target=3D"_blank">https://datatracker.=
ietf.org/doc/draft-ietf-sacm-ecp/?include_text=3D1</a><div><br></div><div>S=
ection 3.2.1</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich &lt;<a href=
=3D"mailto:dan@ehrlichserver.com" target=3D"_blank">dan@ehrlichserver.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr">In the RFC for ECP, there is a section that mentions the pot=
ential use of MAC addresses for identifying endpoints.=C2=A0<div><br></div>=
<div>My understanding is that there are many things wrong with MAC addresse=
s today, such as that they can now be changed randomly by software, can&#39=
;t really be verified, can be spoofed easily, etc.</div><div><br></div><div=
>I cannot find the link I was using from yesterday, but can the MAC address=
 mention be removed from ECP?=C2=A0</div><div><br></div><div><br></div><div=
>Apologies if I viewed an old draft or if this was previously discussed,</d=
iv><div><br>Dan Ehrlich</div><div>Austin, Texas</div><div><a href=3D"https:=
//www.linkedin.com/in/danehrlich/" target=3D"_blank">https://linkedin.com/i=
n/danehrlich/</a><br></div></div>
</blockquote></div>
_______________________________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>
</blockquote></div>

--000000000000eada0c05876e686a--


From nobody Fri Apr 26 07:06:48 2019
Return-Path: <kathleen.moriarty.ietf@gmail.com>
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 03F83120432; Fri, 26 Apr 2019 07:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bNxZDH5G7civ; Fri, 26 Apr 2019 07:06:44 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCD771201D9; Fri, 26 Apr 2019 07:06:43 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id s24so2688518otk.13; Fri, 26 Apr 2019 07:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CEFPj8Z4KxaQeVDxVIvqpLYFy1PDyHxIrmzcgxaDhNc=; b=UaWBxmHH5n6iRBpHYT0RuRTuOaFd8FHoXQetK8yVwIILME4szrpqQ107wNmAq1otng 7L7cyFbBMOFUpRv2Faiov6hunA1RNmcbUt0+cVyn0sCzt5gPJIPou5kgtVWgjKPh+xtx daiUeHK6tXEnE3qopUsR/AWvNCLyPZtzc4mlH3GfltyQWeTOhRJuCGmw+HusJqsSIoWH B/7+bXqHZY1fxa9424ZGTYGZacSB5ehE6+A7wGLbbcK+G1dlE8G0eZcHwIqacEZZGslA 1swkWdjAFfl4DlQ1BjyHwFTh9tqmrE3ap4HgiUPcNrd2Unh4bIt8XOfQLJGdSkrKxyNu IK8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CEFPj8Z4KxaQeVDxVIvqpLYFy1PDyHxIrmzcgxaDhNc=; b=e13HyE3WSzu8PHM1b4WuQLgzfVwJRo9U8E+p8w3r4V/K+spP+3mF3NUX9qArhbDE+3 rrEXEB2pFGCMjugDLJRKCIvLaUEhfXd8287o3rVpAezpVThGHzIIn41+lfhe7U0VCBgo dUJsPByyZh5I0y3vieFwXpikoRgN1LVM7bh6CdQTUgbWUT4//twC0Hkrbmf7zXxnrnow rsXqYvlZoOOYb/DtmYj+8ngIuA1bcT43EUiizJu5WEx/Wru/2SrWWZkEvlyxyuOjyGB4 iUyHYstCHNfFNVhzcByRC9JVgQIwv38anjRRGOyWKwMGKoTEcEt1AcOSRFBLVN0/xB83 QWOg==
X-Gm-Message-State: APjAAAVUgohdcaUdQ7flPziis3wxOxPxGQ5J+LkT0tWOITpydhesDqFk Ys/lpf5v2dzQrwa/Muioy/gxKi2R1lBPj+bY/cc=
X-Google-Smtp-Source: APXvYqy6pltqN7lzhnP9ic5XxnBR7FOPpb0/isD6pC/lB8uw6EEw+6SguZgUB7N3Fx3G+gTjx6LcC4+6TKwS0cSLbbw=
X-Received: by 2002:a9d:2e8:: with SMTP id 95mr28988721otl.283.1556287603048;  Fri, 26 Apr 2019 07:06:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAABgnxisAZdgVWH11Rp-6NoNhwDnFUz2Bc3wYez-oCb0LA0JFQ@mail.gmail.com> <CAABgnxjPQL27bth-BwBYaKaKU941XRDRdsbpoZ1WxPcdEpmVhA@mail.gmail.com> <CAM+R6NXa3WfxYk+unocaUGe=7B_fF0t61GdT3iCFDe0DD0yDFw@mail.gmail.com>
In-Reply-To: <CAM+R6NXa3WfxYk+unocaUGe=7B_fF0t61GdT3iCFDe0DD0yDFw@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 26 Apr 2019 10:06:06 -0400
Message-ID: <CAHbuEH67qr6j=PW2KUvvOyzCYqb77rvtD2347WpNCe4bfSpGkQ@mail.gmail.com>
To: Jessica Fitzgerald-McKay <jmfmckay@gmail.com>
Cc: Dan Ehrlich <dan=40ehrlichserver.com@dmarc.ietf.org>,  "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bf84b505876f71c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/qH4L1wviYfq6X3xP5l-_oKVVBbA>
Subject: Re: [sacm] ECP question
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: Fri, 26 Apr 2019 14:06:46 -0000

--000000000000bf84b505876f71c0
Content-Type: text/plain; charset="UTF-8"

Hi,

On Fri, Apr 26, 2019 at 8:52 AM Jessica Fitzgerald-McKay <jmfmckay@gmail.com>
wrote:

> Dan,
>
>
> Thank you for the review! Your understanding of MAC addresses mirrors
> mine: they are not trustworthy as a sole device identifier. I think that,
> despite that, they are still worth collection, for two reasons:
>
> 1) For device identity correlation-- For some network analytics, the MAC
> address is what they can see. These analytics should have the capability to
> correlate the behavior they see from an endpoint with a particular MAC
> address to a better device identifier. One way to do that is to provide all
> the identifiers an endpoint has (IP address, MAC address, device
> certificate, etc.) to the CMDB. For traditional endpoints, the ECP requires
> IF- IMC and (on the server side) IF-IMV. These interfaces allow endpoints
> to share multiple forms of identity to the server, and then stored in the
> CMDB for this sort of use case.
>
> 2) For attack identification-- ECP enables event-driven collection of
> endpoint data. That is, if something changes on the endpoint, ECP enables
> that change to be immediately (or, close to immediately) sent to the
> server, and then to the CMDB. An endpoint could share any changes to its
> MAC address as a part of that event-driven collection, which would help
> network tools notice a malicious change in near-real-time.
>
> Given these reasons, I would like to keep MAC addresses as a type of
> device identity in the ECP.
>
> I wonder if we could resolve your comments by including a note in the
> security considerations about the trust limitations of MAC addresses. We
> can say that they really should not be used as a sole device identifier,
> and, if other identities can be reported, they really ought to be collected
> at the same time as a MAC address. What do you think?
>

I think this is a good idea.  They may also be in a Privacy Considerations
section.  You may want to call out the scope of collection in this
description as well.  For instance, it may be recommended for use only
within a closed network (datacenter, managed network, enterprise, etc.).
For MAC addresses, randomization has been defined separately by multiple
vendors, but in ways that you can detect who the vendor is by their
randomization pattern.  Privacy work to mitigate that came out of IEEE to
standardize the randomization method across vendors.  I don't think that is
well deployed.

IMO, The section should touch on each of the identifier types and perhaps
limit the recommended scope of use as a precautionary measure to assist
with privacy. This will help address comments that could come in IETF last
call or from the IESG.

Thank you,
Kathleen

>
> Thanks again for taking the time to share your thoughts!
>
> Jess
>
> On Fri, Apr 12, 2019 at 8:45 PM Dan Ehrlich <dan=
> 40ehrlichserver.com@dmarc.ietf.org> wrote:
>
>> Link I mentioned:
>> https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/?include_text=1
>> <https://datatracker.ietf..org/doc/draft-ietf-sacm-ecp/?include_text=1>
>>
>> Section 3.2.1
>>
>> On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich <dan@ehrlichserver.com>
>> wrote:
>>
>>> In the RFC for ECP, there is a section that mentions the potential use
>>> of MAC addresses for identifying endpoints.
>>>
>>> My understanding is that there are many things wrong with MAC addresses
>>> today, such as that they can now be changed randomly by software, can't
>>> really be verified, can be spoofed easily, etc.
>>>
>>> I cannot find the link I was using from yesterday, but can the MAC
>>> address mention be removed from ECP?
>>>
>>>
>>> Apologies if I viewed an old draft or if this was previously discussed,
>>>
>>> Dan Ehrlich
>>> Austin, Texas
>>> https://linkedin.com/in/danehrlich/
>>> <https://www.linkedin.com/in/danehrlich/>
>>>
>> _______________________________________________
>> sacm mailing list
>> sacm@ietf.org
>> https://www.ietf.org/mailman/listinfo/sacm
>>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm
>


-- 

Best regards,
Kathleen

--000000000000bf84b505876f71c0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Fri, Apr 26, 2019 at 8:52 AM Jessica Fitzgerald=
-McKay &lt;<a href=3D"mailto:jmfmckay@gmail.com">jmfmckay@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div style=3D"color:rgb(0,0,0)">Dan,<br><br><br></div><div style=
=3D"color:rgb(0,0,0)">Thank you for the review! Your understanding of MAC a=
ddresses mirrors mine: they are not trustworthy as a sole device identifier=
. I think that, despite that, they are still worth collection, for two reas=
ons:<br><br></div><div style=3D"color:rgb(0,0,0)">1) For device identity co=
rrelation-- For some network analytics, the MAC address is what they can se=
e. These analytics should have the capability to correlate the behavior the=
y see from an endpoint with a particular MAC address to a better device ide=
ntifier. One way to do that is to provide all the identifiers an endpoint h=
as (IP address, MAC address, device certificate, etc.) to the CMDB. For tra=
ditional endpoints, the ECP requires IF- IMC and (on the server side) IF-IM=
V. These interfaces allow endpoints to share multiple forms of identity to =
the server, and then stored in the CMDB for this sort of use case.<br><br><=
/div><div style=3D"color:rgb(0,0,0)">2) For attack identification-- ECP ena=
bles event-driven collection of endpoint data. That is, if something change=
s on the endpoint, ECP enables that change to be immediately (or, close to =
immediately) sent to the server, and then to the CMDB. An endpoint could sh=
are any changes to its MAC address as a part of that event-driven collectio=
n, which would help network tools notice a malicious change in near-real-ti=
me.<br><br></div><div style=3D"color:rgb(0,0,0)">Given these reasons, I wou=
ld like to keep MAC addresses as a type of device identity in the ECP.<br><=
br></div><div style=3D"color:rgb(0,0,0)">I wonder if we could resolve your =
comments by including a note in the security considerations about the trust=
 limitations of MAC addresses. We can say that they really should not be us=
ed as a sole device identifier, and, if other identities can be reported, t=
hey really ought to be collected at the same time as a MAC address. What do=
 you think?<br></div></div></blockquote><div><br></div><div>I think this is=
 a good idea.=C2=A0 They may also be in a Privacy Considerations section.=
=C2=A0 You may want to call out the scope of collection in this description=
 as well.=C2=A0 For instance, it may be recommended for use only within a c=
losed network (datacenter, managed network, enterprise, etc.).=C2=A0 For MA=
C addresses, randomization has been defined separately by multiple vendors,=
 but in ways that you can detect who the vendor is by their randomization p=
attern.=C2=A0 Privacy work to mitigate that came out of IEEE to standardize=
 the randomization method across vendors.=C2=A0 I don&#39;t think that is w=
ell deployed.=C2=A0=C2=A0</div><div><br></div><div>IMO, The section should =
touch on each of the identifier types and perhaps limit the recommended sco=
pe of use as a precautionary measure to assist with privacy. This will help=
 address comments that could come in IETF last call or from the IESG.</div>=
<div><br></div><div>Thank you,</div><div>Kathleen</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr"><div style=3D"color:rgb(0,0,=
0)"><br></div><div style=3D"color:rgb(0,0,0)">Thanks again for taking the t=
ime to share your thoughts!<br><br></div><div style=3D"color:rgb(0,0,0)">Je=
ss<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"=
gmail_attr">On Fri, Apr 12, 2019 at 8:45 PM Dan Ehrlich &lt;dan=3D<a href=
=3D"mailto:40ehrlichserver.com@dmarc.ietf.org" target=3D"_blank">40ehrlichs=
erver.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr">Link I mentioned:=C2=A0<a href=3D"=
https://datatracker.ietf..org/doc/draft-ietf-sacm-ecp/?include_text=3D1" ta=
rget=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/?inclu=
de_text=3D1</a><div><br></div><div>Section 3.2.1</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 12, 2019=
 at 5:42 PM Dan Ehrlich &lt;<a href=3D"mailto:dan@ehrlichserver.com" target=
=3D"_blank">dan@ehrlichserver.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div dir=3D"ltr">In the RFC for ECP, there=
 is a section that mentions the potential use of MAC addresses for identify=
ing endpoints.=C2=A0<div><br></div><div>My understanding is that there are =
many things wrong with MAC addresses today, such as that they can now be ch=
anged randomly by software, can&#39;t really be verified, can be spoofed ea=
sily, etc.</div><div><br></div><div>I cannot find the link I was using from=
 yesterday, but can the MAC address mention be removed from ECP?=C2=A0</div=
><div><br></div><div><br></div><div>Apologies if I viewed an old draft or i=
f this was previously discussed,</div><div><br>Dan Ehrlich</div><div>Austin=
, Texas</div><div><a href=3D"https://www.linkedin.com/in/danehrlich/" targe=
t=3D"_blank">https://linkedin.com/in/danehrlich/</a><br></div></div>
</blockquote></div>
_______________________________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>
</blockquote></div>
_______________________________________________<br>
sacm mailing list<br>
<a href=3D"mailto:sacm@ietf.org" target=3D"_blank">sacm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/sacm" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/sacm</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div><di=
v>Kathleen</div></div></div></div>

--000000000000bf84b505876f71c0--


From nobody Fri Apr 26 19:44:52 2019
Return-Path: <david.oliva@verizon.net>
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 57B38120145 for <sacm@ietfa.amsl.com>; Fri, 26 Apr 2019 19:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verizon.net
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 XCXhS_Jq3L8H for <sacm@ietfa.amsl.com>; Fri, 26 Apr 2019 19:44:48 -0700 (PDT)
Received: from sonic311-25.consmr.mail.gq1.yahoo.com (sonic311-25.consmr.mail.gq1.yahoo.com [98.137.65.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441391200F8 for <sacm@ietf.org>; Fri, 26 Apr 2019 19:44:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizon.net; s=a2048;  t=1556333087; bh=I9GiQnDyFq9u9dw4FsVRO7PI82/fVemEIdFh8vFvxCE=;  h=Date:From:To:Cc:Subject:References:From:Subject; b=tb7O3IWaltX4dsnsDu0hw9uuENNRVIBFyI7La0AgG3RTPT4eGBVQxHSKt5+gxEbLwfEMRFrIm+ol+NOXchTwiyaLxsFJR0gp28ASjBRTVtbpktAe0MmdBeSqIvsSaZ23LA250WivGqRWeXo4CTWm5pnXjz3EKtxrxwuWt4D7SA2uNunxtbU1O7Wc8PGTqxxaPuUFBv44O6UDJ4y/UbhVjt8fdWrvM+Sfi6lbcDHaY093nRdEMuAVByA4o470kI1/hkd9shUP1yJKJVGBjlgIEtTSWpEVSlHfwUz/9cQT5HRcVyBkQd29KLK26fnlc9lSUN3eveMmso/L/Q1lJPcQww==
X-YMail-OSG: fKpejDAVM1kDiT4TVnuTaQkpK77rNSoxVv967Zo_McEoPdZXC_MIHoUfL79iwwv FN_cUN2X27pp.sTT_KjD2TBa.57wi7nppLTfj7AFkPwMlKETLUBaZ_NWiZGY902qCBW6J5B7gAK5 HJl9Zjf29WIEMdv0zoRo9yZWoPlSDMG6fSftk0T3r5zzj1ch10aloNtJ646AMMnTcBaCRBbdcMnq fVSV.SjJPQAU_5aSNK4BS66xQ47D6C9rQv5KflnU4y2b7Upl.iia3xj2_3Wgn09TlfmC.u6NECXL t.a7i3KnKucE0ckAeu2vhyPv1a9.zQ77aQP7WBH.7G1x9QpqqlQCU9qUp_jZXZ2TNDULHcTeSJx2 LQY1vfLwb97f9DxPJZ8fGc4Zf3AZQtZtZy3WZlMeiRCyvBuxPMqARJYK5fUsijFPUEbzP507KH0q BWVZs0fI85cUSJStXrFg6Pf92eOsVgb41f4UYWSX7ZEBetb6vh3QIxPiXJ2J9FCMpXK_oLF43_1e cT7FP..XqEqM__.dpILMjmU4w6e1ywQ57lABN8HhmIsCoQbNBdcEsrvl3o3IX9ec44mJtrbX_ggA JeHjiSmYY292RgIWkEXzfQDIsLBy3vS0Myp0ji_PI6Va01HQLBPk2fLug8hPUBdMG3oBJQoxXSFp 6bVempLSBmi2jFYkNt3bLWhvm5nruMYm08z2nXHz5MHB02e80tKFeRf1ke9DmllTNNugipSJMDv1 KqROjcVT2srh97bK5evMXatsM4isqANJdvJZcTHVprkpOoP3LT9D3zvHy0f9zuOXZNSc5QdzHPeF zbv00Doj5fTfUcAm6JC7qUmRSELp5zk0KVu8MrStCzUDtF1L82pq8XjWk1RkMRiTWypPlhfWBUm_ j5ruWrG11f2TPgL1Yha7R1BaNDxe8zd40KJa9eIRxhe3oa0eemuebOmq19ydrcwDa2nkmdYdMJzy fRwWnPQfw0lc9bdfjgw4IkSbDCLLDoMdLK4HD8A35C_tYx0UT8Ypm7Bs.BXPLojtiaY9J0CKx8Ao WGpYnRM7isZqYxqY8Ki5XEP5UnCtwVn8dJDrULIc0fAMfOGKOLUwz_.0Uc9WBYcXK_biWA9522_R IqVPIOaHvEOy.NEFgZMQYL5deNc_lCRiECwtImpP1o0ek.34OAH6rNcQEMKj7BClwoJ3opy2bUBM 5nXsKxmcTp40-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Sat, 27 Apr 2019 02:44:47 +0000
Date: Sat, 27 Apr 2019 02:44:46 +0000 (UTC)
From: Ruben Oliva <david.oliva@verizon.net>
To: kathleen.moriarty.ietf@gmail.com, jmfmckay@gmail.com
Cc: draft-ietf-sacm-ecp@ietf.org, dan@ehrlichserver.com@dmarc.ietf.org,  sacm@ietf.org
Message-ID: <938745215.1173888.1556333086822@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1173887_2066412604.1556333086820"
References: <938745215.1173888.1556333086822.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.13554 aolwebmail Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/ne8U-I4rXpny7eEjrVgqnUTzm70>
Subject: Re: [sacm] ECP question
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: Sat, 27 Apr 2019 02:44:51 -0000

------=_Part_1173887_2066412604.1556333086820
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

 Hello team:
Here's two additional cents to this trail.
MAC addresses are used in events correlation and auditing.

David Oliva
=20
=20
-----Original Message-----
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Jessica Fitzgerald-McKay <jmfmckay@gmail.com>
Cc: draft-ietf-sacm-ecp@ietf.org <draft-ietf-sacm-ecp@ietf.org>; Dan Ehrlic=
h <dan=3D40ehrlichserver.com@dmarc.ietf.org>; sacm@ietf.org <sacm@ietf.org>
Sent: Fri, Apr 26, 2019 10:06 am
Subject: Re: [sacm] ECP question

Hi,
On Fri, Apr 26, 2019 at 8:52 AM Jessica Fitzgerald-McKay <jmfmckay@gmail.co=
m> wrote:

Dan,


Thank you for the review! Your understanding of MAC addresses mirrors mine:=
 they are not trustworthy as a sole device identifier.. I think that, despi=
te that, they are still worth collection, for two reasons:

1) For device identity correlation-- For some network analytics, the MAC ad=
dress is what they can see. These analytics should have the capability to c=
orrelate the behavior they see from an endpoint with a particular MAC addre=
ss to a better device identifier. One way to do that is to provide all the =
identifiers an endpoint has (IP address, MAC address, device certificate, e=
tc.) to the CMDB. For traditional endpoints, the ECP requires IF- IMC and (=
on the server side) IF-IMV. These interfaces allow endpoints to share multi=
ple forms of identity to the server, and then stored in the CMDB for this s=
ort of use case.

2) For attack identification-- ECP enables event-driven collection of endpo=
int data. That is, if something changes on the endpoint, ECP enables that c=
hange to be immediately (or, close to immediately) sent to the server, and =
then to the CMDB. An endpoint could share any changes to its MAC address as=
 a part of that event-driven collection, which would help network tools not=
ice a malicious change in near-real-time.

Given these reasons, I would like to keep MAC addresses as a type of device=
 identity in the ECP.

I wonder if we could resolve your comments by including a note in the secur=
ity considerations about the trust limitations of MAC addresses. We can say=
 that they really should not be used as a sole device identifier, and, if o=
ther identities can be reported, they really ought to be collected at the s=
ame time as a MAC address. What do you think?


I think this is a good idea.=C2=A0 They may also be in a Privacy Considerat=
ions section.=C2=A0 You may want to call out the scope of collection in thi=
s description as well.=C2=A0 For instance, it may be recommended for use on=
ly within a closed network (datacenter, managed network, enterprise, etc.).=
=C2=A0 For MAC addresses, randomization has been defined separately by mult=
iple vendors, but in ways that you can detect who the vendor is by their ra=
ndomization pattern.=C2=A0 Privacy work to mitigate that came out of IEEE t=
o standardize the randomization method across vendors.=C2=A0 I don't think =
that is well deployed.=C2=A0=C2=A0
IMO, The section should touch on each of the identifier types and perhaps l=
imit the recommended scope of use as a precautionary measure to assist with=
 privacy. This will help address comments that could come in IETF last call=
 or from the IESG.
Thank you,Kathleen

Thanks again for taking the time to share your thoughts!

Jess

On Fri, Apr 12, 2019 at 8:45 PM Dan Ehrlich <dan=3D40ehrlichserver.com@dmar=
c.ietf.org> wrote:

Link I mentioned:=C2=A0https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp=
/?include_text=3D1
Section 3.2.1
On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich <dan@ehrlichserver.com> wrote:

In the RFC for ECP, there is a section that mentions the potential use of M=
AC addresses for identifying endpoints.=C2=A0
My understanding is that there are many things wrong with MAC addresses tod=
ay, such as that they can now be changed randomly by software, can't really=
 be verified, can be spoofed easily, etc.
I cannot find the link I was using from yesterday, but can the MAC address =
mention be removed from ECP?=C2=A0

Apologies if I viewed an old draft or if this was previously discussed,
Dan EhrlichAustin, Texashttps://linkedin.com/in/danehrlich/

_______________________________________________
sacm mailing list
sacm@ietf.org
https://www.ietf.org/mailman/listinfo/sacm

_______________________________________________
sacm mailing list
sacm@ietf.org
https://www.ietf.org/mailman/listinfo/sacm



--=20

Best regards,Kathleen_______________________________________________
sacm mailing list
sacm@ietf.org
https://www.ietf.org/mailman/listinfo/sacm

------=_Part_1173887_2066412604.1556333086820
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<font color='black' size='2' face='arial'>
<div> <font size="2">Hello team:</font></div>

<div><font size="2"><br>
</font></div>

<div><font size="2">Here's two additional cents to this trail.</font></div>

<div><font size="2"><br>
</font></div>

<div><font size="2">MAC addresses are used in events correlation and auditing.</font></div>

<div><font size="2"><br>
</font></div>

<div><font size="2"><br>
</font></div>

<div><font size="2">David Oliva</font><br>
</div>

<div> <br>
</div>

<div> <br>
</div>

<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>
From: Kathleen Moriarty &lt;kathleen.moriarty.ietf@gmail.com&gt;<br>
To: Jessica Fitzgerald-McKay &lt;jmfmckay@gmail.com&gt;<br>
Cc: draft-ietf-sacm-ecp@ietf.org &lt;draft-ietf-sacm-ecp@ietf.org&gt;; Dan Ehrlich &lt;dan=40ehrlichserver.com@dmarc.ietf.org&gt;; sacm@ietf.org &lt;sacm@ietf.org&gt;<br>
Sent: Fri, Apr 26, 2019 10:06 am<br>
Subject: Re: [sacm] ECP question<br>
<br>

<div id="yiv3079115067">
<div>
<div dir="ltr">
<div>Hi,</div>
<br clear="none">
<div class="yiv3079115067gmail_quote">
<div class="yiv3079115067gmail_attr" dir="ltr">On Fri, Apr 26, 2019 at 8:52 AM Jessica Fitzgerald-McKay &lt;<a rel="noopener noreferrer" shape="rect" ymailto="mailto:jmfmckay@gmail.com" target="_blank" href="mailto:jmfmckay@gmail.com">jmfmckay@gmail.com</a>&gt; wrote:<br clear="none"></div>
<blockquote class="yiv3079115067gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">
<div dir="ltr">
<div style="color:rgb(0,0,0);">Dan,<br clear="none"><br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">Thank you for the review! Your understanding of MAC addresses mirrors mine: they are not trustworthy as a sole device identifier.. I think that, despite that, they are still worth collection, for two reasons:<br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">1) For device identity correlation-- For some network analytics, the MAC address is what they can see. These analytics should have the capability to correlate the behavior they see from an endpoint with a particular MAC address to a better device identifier. One way to do that is to provide all the identifiers an endpoint has (IP address, MAC address, device certificate, etc.) to the CMDB. For traditional endpoints, the ECP requires IF- IMC and (on the server side) IF-IMV. These interfaces allow endpoints to share multiple forms of identity to the server, and then stored in the CMDB for this sort of use case.<br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">2) For attack identification-- ECP enables event-driven collection of endpoint data. That is, if something changes on the endpoint, ECP enables that change to be immediately (or, close to immediately) sent to the server, and then to the CMDB. An endpoint could share any changes to its MAC address as a part of that event-driven collection, which would help network tools notice a malicious change in near-real-time.<br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">Given these reasons, I would like to keep MAC addresses as a type of device identity in the ECP.<br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">I wonder if we could resolve your comments by including a note in the security considerations about the trust limitations of MAC addresses. We can say that they really should not be used as a sole device identifier, and, if other identities can be reported, they really ought to be collected at the same time as a MAC address. What do you think?<br clear="none"></div>
</div>
</blockquote>
<div><br clear="none"></div>

<div>I think this is a good idea.&nbsp; They may also be in a Privacy Considerations section.&nbsp; You may want to call out the scope of collection in this description as well.&nbsp; For instance, it may be recommended for use only within a closed network (datacenter, managed network, enterprise, etc.).&nbsp; For MAC addresses, randomization has been defined separately by multiple vendors, but in ways that you can detect who the vendor is by their randomization pattern.&nbsp; Privacy work to mitigate that came out of IEEE to standardize the randomization method across vendors.&nbsp; I don't think that is well deployed.&nbsp;&nbsp;</div>

<div><br clear="none"></div>

<div>IMO, The section should touch on each of the identifier types and perhaps limit the recommended scope of use as a precautionary measure to assist with privacy. This will help address comments that could come in IETF last call or from the IESG.</div>

<div><br clear="none"></div>

<div>Thank you,</div>

<div>Kathleen</div>
<blockquote class="yiv3079115067gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">
<div class="yiv3079115067yqt9194855588" id="yiv3079115067yqtfd35576">
<div dir="ltr">
<div style="color:rgb(0,0,0);"><br clear="none"></div>

<div style="color:rgb(0,0,0);">Thanks again for taking the time to share your thoughts!<br clear="none"><br clear="none"></div>

<div style="color:rgb(0,0,0);">Jess<br clear="none"></div>
</div>
<br clear="none">
<div class="yiv3079115067gmail_quote">
<div class="yiv3079115067gmail_attr" dir="ltr">On Fri, Apr 12, 2019 at 8:45 PM Dan Ehrlich &lt;dan=<a rel="noopener noreferrer" shape="rect" ymailto="mailto:40ehrlichserver.com@dmarc.ietf.org" target="_blank" href="mailto:40ehrlichserver.com@dmarc.ietf.org">40ehrlichserver.com@dmarc.ietf.org</a>&gt; wrote:<br clear="none"></div>
<blockquote class="yiv3079115067gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">
<div dir="ltr">Link I mentioned:&nbsp;<a rel="noopener noreferrer" shape="rect" target="_blank" href="https://datatracker.ietf..org/doc/draft-ietf-sacm-ecp/?include_text=1">https://datatracker.ietf.org/doc/draft-ietf-sacm-ecp/?include_text=1</a>
<div><br clear="none"></div>

<div>Section 3.2.1</div>
</div>
<br clear="none">
<div class="yiv3079115067gmail_quote">
<div class="yiv3079115067gmail_attr" dir="ltr">On Fri, Apr 12, 2019 at 5:42 PM Dan Ehrlich &lt;<a rel="noopener noreferrer" shape="rect" ymailto="mailto:dan@ehrlichserver.com" target="_blank" href="mailto:dan@ehrlichserver.com">dan@ehrlichserver.com</a>&gt; wrote:<br clear="none"></div>
<blockquote class="yiv3079115067gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">
<div dir="ltr">In the RFC for ECP, there is a section that mentions the potential use of MAC addresses for identifying endpoints.&nbsp;
<div><br clear="none"></div>

<div>My understanding is that there are many things wrong with MAC addresses today, such as that they can now be changed randomly by software, can't really be verified, can be spoofed easily, etc.</div>

<div><br clear="none"></div>

<div>I cannot find the link I was using from yesterday, but can the MAC address mention be removed from ECP?&nbsp;</div>

<div><br clear="none"></div>

<div><br clear="none"></div>

<div>Apologies if I viewed an old draft or if this was previously discussed,</div>

<div><br clear="none">Dan Ehrlich</div>

<div>Austin, Texas</div>

<div><a rel="noopener noreferrer" shape="rect" target="_blank" href="https://www.linkedin.com/in/danehrlich/">https://linkedin.com/in/danehrlich/</a><br clear="none"></div>
</div>

</blockquote></div>

_______________________________________________<br clear="none">
sacm mailing list<br clear="none">
<a rel="noopener noreferrer" shape="rect" ymailto="mailto:sacm@ietf.org" target="_blank" href="mailto:sacm@ietf.org">sacm@ietf.org</a><br clear="none">
<a rel="noopener noreferrer" shape="rect" target="_blank" href="https://www.ietf.org/mailman/listinfo/sacm">https://www.ietf.org/mailman/listinfo/sacm</a><br clear="none">
</blockquote></div>

_______________________________________________<br clear="none">
sacm mailing list<br clear="none">
<a rel="noopener noreferrer" shape="rect" ymailto="mailto:sacm@ietf.org" target="_blank" href="mailto:sacm@ietf.org">sacm@ietf.org</a><br clear="none">
<a rel="noopener noreferrer" shape="rect" target="_blank" href="https://www.ietf.org/mailman/listinfo/sacm">https://www.ietf.org/mailman/listinfo/sacm</a></div>
<br clear="none">
</blockquote></div>
<br clear="all">
<div><br clear="none"></div>
-- <br clear="none">
<div class="yiv3079115067gmail_signature" dir="ltr">
<div dir="ltr"><br clear="none">
<div>Best regards,</div>

<div>Kathleen</div>
</div>
</div>
</div>
</div>
</div>

<div class="yqt9194855588" id="yqtfd36176">_______________________________________________<br clear="none">sacm mailing list<br clear="none"><a shape="rect" ymailto="mailto:sacm@ietf.org" rel="noopener noreferrer" href="mailto:sacm@ietf.org">sacm@ietf.org</a><br clear="none"><a shape="rect" target="_blank" rel="noopener noreferrer" href="https://www.ietf.org/mailman/listinfo/sacm">https://www.ietf.org/mailman/listinfo/sacm</a><br clear="none"></div>
</div>
</font>
------=_Part_1173887_2066412604.1556333086820--

