From nobody Fri Dec 1 06:18:27 2017 Return-Path: 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 9687A128D64 for ; Fri, 1 Dec 2017 06:18:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 UE5UXAAb0tce for ; Fri, 1 Dec 2017 06:18:24 -0800 (PST) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 F3833126C19 for ; Fri, 1 Dec 2017 06:18:23 -0800 (PST) Received: by mail-it0-x236.google.com with SMTP id o130so4352549itg.0 for ; Fri, 01 Dec 2017 06:18:23 -0800 (PST) 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=M7hkqFSfV38doU6Of4s5OKJOs4oaFh77HTLBp5CPk+M=; b=f+nFiGYveoCwfxKATblKAsOck0FFMz+yvlE5/k2sj/POoOlFeYpXKcF9T5ydv/hsme QhtkMYuDw/KCYgC6YgHHOpzri3aVnjAoWZczN/Rtf+qfhaSGc0r7dcycJL5Ilu4j8m/H Mq7XF+36p9Xm2sSVBwZpU6enXIImzlyOPzuYeWYKNwYmLBbnrj0E+Mb9IoDRf1xr8UjB GOIWam2IqEEbKYfreXIu8wYZ2vrNycxMmn+QQrIel8EbgcUIjaY37MoYWEGBTU9JADuz GF86tvJAshPpUBXGSiXUUkg/wc9QxJlnR6BftRSLQucGbhv9YqHguD01mUMS0C1rO4vC Nusw== 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=M7hkqFSfV38doU6Of4s5OKJOs4oaFh77HTLBp5CPk+M=; b=QnoUEX73NpPF4UeazZne968ut9oZK3ej1BuVn+dJKnKGjGVsuB+oSKxkaAW/18bFqe VPpyRBghAAr0F7hEirgB43Kl72MqobJ4H9Q8k9Yocc1w82rnkmhtNa3isRlmLciJnFFf SdYZTbDRTNpLN2ES8taVCIAU/KQIHC2aa7jsiHrpLYssPVyy6G5en+Rl01l/cnrVYaHK M9mj0nmtW5y2Yg/iiWy36AiYncUUiIxHxY+CyuAsU8NO6hLNkAtMxs4cAvMbg6AHrc+U gV01JtNbBTu9u/KOx9QbdDaRrmnOs4Gos1vID9Pzp8OMWAoqmr5qD4wdW3AlEAESlD2V egDA== X-Gm-Message-State: AKGB3mLv0iu8F62Dd+X3Nm1ErDTSsTk3Hbv1ry2KrDmvJsr84f8eikwF MNJNlLdNC08IBLtDQzz/w2enjM7SE4/q9lpHh76Vww== X-Google-Smtp-Source: AGs4zMYW20XxR9HML1Q+e3dSe9bRNGYV1y2FeV+NKEp1ROqzs8WBbJdDAv/zR3McJkAmTEgDeHgsPXzeVzwr7dsQvLU= X-Received: by 10.36.249.132 with SMTP id l126mr2126879ith.52.1512137903072; Fri, 01 Dec 2017 06:18:23 -0800 (PST) MIME-Version: 1.0 References: <08f56f91-f9a2-d6ca-5326-579c37b2a578@sit.fraunhofer.de> In-Reply-To: <08f56f91-f9a2-d6ca-5326-579c37b2a578@sit.fraunhofer.de> From: Adam Montville Date: Fri, 01 Dec 2017 14:18:12 +0000 Message-ID: To: Henk Birkholz Cc: "sacm@ietf.org" Content-Type: multipart/alternative; boundary="94eb2c1187cc906c35055f480a99" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 14:18:25 -0000 --94eb2c1187cc906c35055f480a99 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks all! On Thu, Nov 30, 2017 at 4:06 PM Henk Birkholz < henk.birkholz@sit.fraunhofer.de> wrote: > Hello Adam, > > welcome to the roster! I tracked your progress wrt issues and had no > objections. I agree with Jarret and Nancy - fire at will. > > We will resolve discrepancies via direct pushes and not pull requests > for now. When the dust has settled, we might revisit this approach, but > for now it seems the most appropriate. > > Viele Gr=C3=BC=C3=9Fe, > > Henk > > On 11/30/2017 10:35 PM, Adam Montville wrote: > > All: > > > > At IETF 100 I offered to take the pen on our terminology draft. I've > > begun cleaning out the issues, and I have picked up where I left of in > > my review (which was back in July). I've finished my review, but I > > haven't yet added each of the issues. > > > > Would you prefer that I create an issue for each proposal I have, or > > would you prefer I simply make the changes and you can diff them later? > > > > I ask for two reasons. First, there are a lot of changes I'd like to > > make, and I'd be making at least another 30-40 issues. Second, most of > > the changes I'd like to make are clarifying (i.e. removing unnecessary > > terms, and superfluous language). > > > > Unless many of you would plan to review each of the issues, I would > > prefer to clean up the draft and deal with any objections that may come > > after the fact. > > > > Thoughts? > > > > Kind regards, > > > > Adam > > > > > > _______________________________________________ > > sacm mailing list > > sacm@ietf.org > > https://www.ietf.org/mailman/listinfo/sacm > > > --94eb2c1187cc906c35055f480a99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks all!=C2=A0

On Thu, Nov 30, 2017 at 4:06 PM Henk Birkholz <henk.birkholz@sit.fraunhofer.de>= ; wrote:
Hello Adam,

welcome to the roster! I tracked your progress wrt issues and had no
objections. I agree with Jarret and Nancy - fire at will.

We will resolve discrepancies via direct pushes and not pull requests
for now. When the dust has settled, we might revisit this approach, but
for now it seems the most appropriate.

Viele Gr=C3=BC=C3=9Fe,

Henk

On 11/30/2017 10:35 PM, Adam Montville wrote:
> All:
>
> At IETF 100 I offered to take the pen on our terminology draft. I'= ve
> begun cleaning out the issues, and I have picked up where I left of in=
> my review (which was back in July). I've finished my review, but I=
> haven't yet added each of the issues.
>
> Would you prefer that I create an issue for each proposal I have, or > would you prefer I simply make the changes and you can diff them later= ?
>
> I ask for two reasons. First, there are a lot of changes I'd like = to
> make, and I'd be making at least another 30-40 issues. Second, mos= t of
> the changes I'd like to make are clarifying (i.e. removing unneces= sary
> terms, and superfluous language).
>
> Unless many of you would plan to review each of the issues, I would > prefer to clean up the draft and deal with any objections that may com= e
> after the fact.
>
> Thoughts?
>
> Kind regards,
>
> Adam
>
>
> _______________________________________________
> sacm mailing list
> sacm@ietf.org > https://www.ietf.org/mailman/listinfo/sacm
>
--94eb2c1187cc906c35055f480a99-- From nobody Fri Dec 1 07:10:09 2017 Return-Path: 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 A4C071293E4 for ; Fri, 1 Dec 2017 07:10:07 -0800 (PST) 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, FREEMAIL_FROM=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 (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 rMHc_oOxpjeS for ; Fri, 1 Dec 2017 07:10:06 -0800 (PST) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 067F0124319 for ; Fri, 1 Dec 2017 07:10:06 -0800 (PST) Received: by mail-pf0-x22d.google.com with SMTP id j124so4763848pfc.2 for ; Fri, 01 Dec 2017 07:10:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CNbP7Z/D/8mBjj7fCu4OXC7l/sXJkIhkTm+za3lQe7E=; b=Q9ZUiXbD4h3j74FFQ1Tqs1h1kO4dCMiamGM+0eveNVf9Yr/qcP8MHmO+cUsBhdHKG0 WhqlCjyPSp5gPCrq12qFhxNkww7z8xot0FjQjnPpskGIU0iif95Nap2c6c/0pSdx9/4X 41iw+Ym8jh0bw/4qmjeODrv7/NMyUiGDd73eBd0glpSMKNB9GHxim114HFVzlPOvAbgn FCWu9Raiki0JfAe8B9O1c92qMasGUNij3JwIlv27zILG7PspsDxF0lHZzms05LUvsCUl 9nZZ9+dQPZFdf6b99n+dXmwe9YFbPLp85kcgzrgrFXI1Oq0lPqQ/xA3WjStr+XOiT+Ez 0a1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CNbP7Z/D/8mBjj7fCu4OXC7l/sXJkIhkTm+za3lQe7E=; b=eOgurvIcFvs2K9a75Nfu18N7Acb35NnKU+CKjnpu34vgCdtZnQODcjYDPe9eNW9AuP xD1VVdoSFC8RTFAB67NgKH8+aTlHVHZDqc5G2n5GGW44nx12Lo7GDmhJA+wKZYgNv8aq WruYQrYE9LFUdIY+zxsNiJdCRa1PelH8WrFFLgsYZBh14q3oE0J6N6qNf4KeY9FYX45e hUKkvO7kafan8VFC6JLLVPKKuVM4ETU69XLlTc7AOjzko7sxljDc2dbxoHvxw/fXcT5T Y2mvsFujvQ9JPSQeSzkl7U6veKzG5vnjPewVXC5755reU0lV7N1QrCHd/XKTJQrLKB2Y Oz7w== X-Gm-Message-State: AJaThX4FZ8q32WkvOZweOImaXkLDRsFdWvh7URCZj+bkPRNYhTCs+kqq mrOEQFtZfqc4QDUFjKvHA1bGzqv/HeGj+rZdjUU= X-Google-Smtp-Source: AGs4zMaZZNoAtTlLJxnUFwMLcIAXwql4tRq2R0X60Gi05Mp/U2/J/qBTnMu50px9yLLS3Nm9J22Ca97C4Mw/9ZXwUs0= X-Received: by 10.99.109.202 with SMTP id i193mr6183980pgc.443.1512141005400; Fri, 01 Dec 2017 07:10:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.186.208 with HTTP; Fri, 1 Dec 2017 07:09:24 -0800 (PST) In-Reply-To: References: From: Kathleen Moriarty Date: Fri, 1 Dec 2017 10:09:24 -0500 Message-ID: To: Adam Montville Cc: "sacm@ietf.org" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:10:08 -0000 Hi Adam, Would a PR in github be a better answer? Best regards, Kathleen On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville wrote: > All: > > At IETF 100 I offered to take the pen on our terminology draft. I've begun > cleaning out the issues, and I have picked up where I left of in my review > (which was back in July). I've finished my review, but I haven't yet added > each of the issues. > > Would you prefer that I create an issue for each proposal I have, or would > you prefer I simply make the changes and you can diff them later? > > I ask for two reasons. First, there are a lot of changes I'd like to make, > and I'd be making at least another 30-40 issues. Second, most of the changes > I'd like to make are clarifying (i.e. removing unnecessary terms, and > superfluous language). > > Unless many of you would plan to review each of the issues, I would prefer > to clean up the draft and deal with any objections that may come after the > fact. > > Thoughts? > > Kind regards, > > Adam > > _______________________________________________ > sacm mailing list > sacm@ietf.org > https://www.ietf.org/mailman/listinfo/sacm > -- Best regards, Kathleen From nobody Fri Dec 1 07:11:11 2017 Return-Path: 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 17CCB129407 for ; Fri, 1 Dec 2017 07:11:07 -0800 (PST) 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, FREEMAIL_FROM=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 (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 y1dUxiuVFb7D for ; Fri, 1 Dec 2017 07:11:05 -0800 (PST) Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 8D4BC120713 for ; Fri, 1 Dec 2017 07:11:05 -0800 (PST) Received: by mail-pg0-x233.google.com with SMTP id g7so4606690pgs.0 for ; Fri, 01 Dec 2017 07:11:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YSDR9SxRRHpX+f2FeV+0fp4UlKCV41y5Eorbe1WE/ag=; b=QzHw2lJsds2ZOIizsdu+5UTKeGmQgvlSEX7OutLgcZPXvBBsxOZgziZ8bfv+o8J6J+ mbqBLAJoBo210qMNWWgIP59qrjU/co1lBV2wPrNScuKosRSazbpzjxfgexZPSgI/UYO0 gqLtcPiDjHDuWdTdCQY5ZcfwXt7hExD5Oe6rkkKEOA5FSHFxaUJs/CocPuOG7lNPK8Zr 4A+GQQOO0H7G14rm5PHyLMgCH71/1RF0nKgDnwjDo/PtIidp2iobro4CN5wJrRLU5PdS aEFCh0hfHGGhDS2MrU3LY58tzAaN9suDzxwPH3Moafw2AviAnSaau4IUTSi4uapRRcQe OuuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YSDR9SxRRHpX+f2FeV+0fp4UlKCV41y5Eorbe1WE/ag=; b=k3r3xhxGNcazRUvamFlyhSdxSBBkAdPWuJ/eNrIR8VnYc/YdlpFdKvi8Zfypw9l1I0 RnVf4YGNUmlFDk0whd90vCwmRMyUrEXisWYtguJl6/rsTRgWDL3FpEZCyAZ9tqWvBqCr jV7Cacdhtm081NNKmVS3NMQHSDZvLaWWJtkZLWu+z1TdDTAAEZqTsT6yw9faUx4uUL/E naAEUDcO/vMBtq7VoMWG3BBDxRqhBfbr4SMsVLVVRXij6WuRtxGVZjC6XhUbWWMGebNi mW7rPBnn5iOAbVQkLKdh12seyr4FL7hGfb+KOD43r++JvF7jd5Vci0FePWstOGfcrpZD 0p5g== X-Gm-Message-State: AJaThX7Pn2M5M2bNEiEjKgLN8CnjjCITTq6EcYIH8SKnRzwNP3VJYnMa XmRo3JcFsak6btzH1hvTMeytDw6IheAqScecbXE= X-Google-Smtp-Source: AGs4zMYvchQ1CP4e2U7eisgq6RAFo4tFVovWfK1yeJl0YrQhJcau8O/hGQaeXUHB5+OnzP8+ueP1if64/n4OlqZjaNw= X-Received: by 10.99.50.69 with SMTP id y66mr6201105pgy.217.1512141065209; Fri, 01 Dec 2017 07:11:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.186.208 with HTTP; Fri, 1 Dec 2017 07:10:24 -0800 (PST) In-Reply-To: References: From: Kathleen Moriarty Date: Fri, 1 Dec 2017 10:10:24 -0500 Message-ID: To: Adam Montville Cc: "sacm@ietf.org" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:11:07 -0000 Sorry, my email wasn't synced, and the PR was just a suggestion. On Fri, Dec 1, 2017 at 10:09 AM, Kathleen Moriarty wrote: > Hi Adam, > > Would a PR in github be a better answer? > > Best regards, > Kathleen > > On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville > wrote: >> All: >> >> At IETF 100 I offered to take the pen on our terminology draft. I've begun >> cleaning out the issues, and I have picked up where I left of in my review >> (which was back in July). I've finished my review, but I haven't yet added >> each of the issues. >> >> Would you prefer that I create an issue for each proposal I have, or would >> you prefer I simply make the changes and you can diff them later? >> >> I ask for two reasons. First, there are a lot of changes I'd like to make, >> and I'd be making at least another 30-40 issues. Second, most of the changes >> I'd like to make are clarifying (i.e. removing unnecessary terms, and >> superfluous language). >> >> Unless many of you would plan to review each of the issues, I would prefer >> to clean up the draft and deal with any objections that may come after the >> fact. >> >> Thoughts? >> >> Kind regards, >> >> Adam >> >> _______________________________________________ >> sacm mailing list >> sacm@ietf.org >> https://www.ietf.org/mailman/listinfo/sacm >> > > > > -- > > Best regards, > Kathleen -- Best regards, Kathleen From nobody Fri Dec 1 07:27:47 2017 Return-Path: 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 6B0FF1293EE for ; Fri, 1 Dec 2017 07:27:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 VZBjH8QtN-T1 for ; Fri, 1 Dec 2017 07:27:43 -0800 (PST) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 604C71293EC for ; Fri, 1 Dec 2017 07:27:43 -0800 (PST) Received: by mail-io0-x22c.google.com with SMTP id d16so11615328iob.4 for ; Fri, 01 Dec 2017 07:27:43 -0800 (PST) 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=urtU3o6Kz0SGADrI4Y3pw7G8z+zET230IE3PvBUkKSs=; b=RS9UPZqclUEmW7TgsE8I8xUqkTZsnsAP05Sm2VQCBqF4Vx7CZuQdqG5fGWRT6Yn3Bt Etjup5tpzPAE+V2AeShICeX+znEsE1cR5qsoXG5ZqWv7KHNcNGNlPLmX34/XtY1Y4WyW sBkvO1YaULd9Srk7bEgvMxyyzIfG/1IAylZ3/gRNt6BJZX3XVrQAmQaA4Juct7P2+RF9 UfEkxDdv1Rd9E++a4WnynD/kbWFUSTJQnUcbEG7ikTDQPEU2H9U8DZFo53aJfHWZP4M2 SNw9dgQw/dttvB64VUrQAxcIRlFY+ZCtTdx/zhzwUZHqPFMwIFC15cGy+4wnDB6YaZ4L Oqqg== 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=urtU3o6Kz0SGADrI4Y3pw7G8z+zET230IE3PvBUkKSs=; b=dbLd2DK6Veg+vf/zHELb9j40FaOJOBuoorOrtnkA/tRUWSVu1a5/pnILyfnMY077TD DGD1na3PMtv5yVl180mM6eXRwrj/i3fIdEPYuv89CZQNpU4TArIil8GSPZFBOoacnpJb mjEaqOKJtTBrKFV2YgScHRl0IIDp8bavGvRA0AjuEZi+SgVHHe+fG2+5hK+aWH0TPZOq ZDHE7kfULgquDu7kM8XhRANbpFJINf2K+FZgiEZHZpWog+r5GJlDyA/KET+328i5NGYQ GjoBnaMtI0Lg8me7+MgcbttaXk5B6lxJJib7RT0rBfIJv26eDD0RqgQ3mvUtYXxIM77T VxDw== X-Gm-Message-State: AJaThX7TbGwLnyqYWzoSj2Z4nY7geP9aWLQ1Vc+26dpGXfEo64ju8e1p E1jJusSAyAuIS7LHsG6faO8WG4VesYCz2oo6W0PE6A== X-Google-Smtp-Source: AGs4zMblCxjE/0dPZ91+myNQ+wWuIq7MjV+nq3XFgpfqWAZIHGLZZUPaQq7GstOQ1jPvN3RgflbvuSxjXT1UjY6rsvA= X-Received: by 10.107.38.2 with SMTP id m2mr13104500iom.272.1512142062446; Fri, 01 Dec 2017 07:27:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adam Montville Date: Fri, 01 Dec 2017 15:27:31 +0000 Message-ID: To: Kathleen Moriarty Cc: "sacm@ietf.org" Content-Type: multipart/alternative; boundary="001a1140eff07b8e34055f4902c2" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:27:45 -0000 --001a1140eff07b8e34055f4902c2 Content-Type: text/plain; charset="UTF-8" No problem, thanks! A PR would certainly work. I can do any of those things. Just not sure how many folks in the WG pay attention to GitHub, much less the PRs that may be submitted there. On Fri, Dec 1, 2017 at 9:11 AM Kathleen Moriarty < kathleen.moriarty.ietf@gmail.com> wrote: > Sorry, my email wasn't synced, and the PR was just a suggestion. > > On Fri, Dec 1, 2017 at 10:09 AM, Kathleen Moriarty > wrote: > > Hi Adam, > > > > Would a PR in github be a better answer? > > > > Best regards, > > Kathleen > > > > On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville > > wrote: > >> All: > >> > >> At IETF 100 I offered to take the pen on our terminology draft. I've > begun > >> cleaning out the issues, and I have picked up where I left of in my > review > >> (which was back in July). I've finished my review, but I haven't yet > added > >> each of the issues. > >> > >> Would you prefer that I create an issue for each proposal I have, or > would > >> you prefer I simply make the changes and you can diff them later? > >> > >> I ask for two reasons. First, there are a lot of changes I'd like to > make, > >> and I'd be making at least another 30-40 issues. Second, most of the > changes > >> I'd like to make are clarifying (i.e. removing unnecessary terms, and > >> superfluous language). > >> > >> Unless many of you would plan to review each of the issues, I would > prefer > >> to clean up the draft and deal with any objections that may come after > the > >> fact. > >> > >> Thoughts? > >> > >> Kind regards, > >> > >> Adam > >> > >> _______________________________________________ > >> sacm mailing list > >> sacm@ietf.org > >> https://www.ietf.org/mailman/listinfo/sacm > >> > > > > > > > > -- > > > > Best regards, > > Kathleen > > > > -- > > Best regards, > Kathleen > --001a1140eff07b8e34055f4902c2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No problem, thanks! A PR would certainly work. I can do an= y of those things. Just not sure how many folks in the WG pay attention to = GitHub, much less the PRs that may be submitted there.

On Fri, Dec 1, 2017 at 9:11 AM Kathleen M= oriarty <kathleen.mo= riarty.ietf@gmail.com> wrote:
k= athleen.moriarty.ietf@gmail.com> wrote:
> Hi Adam,
>
> Would a PR in github be a better answer?
>
> Best regards,
> Kathleen
>
> On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville
> <ad= am.w.montville@gmail.com> wrote:
>> All:
>>
>> At IETF 100 I offered to take the pen on our terminology draft. I&= #39;ve begun
>> cleaning out the issues, and I have picked up where I left of in m= y review
>> (which was back in July). I've finished my review, but I haven= 't yet added
>> each of the issues.
>>
>> Would you prefer that I create an issue for each proposal I have, = or would
>> you prefer I simply make the changes and you can diff them later?<= br> >>
>> I ask for two reasons. First, there are a lot of changes I'd l= ike to make,
>> and I'd be making at least another 30-40 issues. Second, most = of the changes
>> I'd like to make are clarifying (i.e. removing unnecessary ter= ms, and
>> superfluous language).
>>
>> Unless many of you would plan to review each of the issues, I woul= d prefer
>> to clean up the draft and deal with any objections that may come a= fter the
>> fact.
>>
>> Thoughts?
>>
>> Kind regards,
>>
>> Adam
>>
>> _______________________________________________
>> sacm mailing list
>> sacm@ietf.org
>> https://www.ietf.org/mailman/listinfo/sacm >>
>
>
>
> --
>
> Best regards,
> Kathleen



--

Best regards,
Kathleen
--001a1140eff07b8e34055f4902c2-- From nobody Fri Dec 1 07:40:35 2017 Return-Path: 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 D5CBB129407 for ; Fri, 1 Dec 2017 07:40:33 -0800 (PST) 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, FREEMAIL_FROM=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 (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 Ia-pTYUXSXwL for ; Fri, 1 Dec 2017 07:40:31 -0800 (PST) Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::22e]) (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 E0C48129405 for ; Fri, 1 Dec 2017 07:40:31 -0800 (PST) Received: by mail-pf0-x22e.google.com with SMTP id l24so4794555pfj.6 for ; Fri, 01 Dec 2017 07:40:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C+foefUS5Woz3I8Qil0EbVvFr8aPDp91Q9wmkMo0GTs=; b=FD8JtjIyZaNeaQIZJZiD54+1SclGuF5aOrWffzu3cWC+OR0QUFB7Z4DD5YqF/b5gn9 i29cD4J/xdzibQp0KxndAHmZ+pcw6/we22xyGjGIy1jltsi/ek1Ch9f0kv9jXFQhu4MV 64ix1rM9LSW1GG71d7mpQOK3yKBGafn8PqBv7MLI+8ZLtaaTwW6TgTExlGVBK81tSoh5 4NTT9wqU9GNWvlt8VN1nBhwlKip3TvNt8fjBlKRU+qs0FlfKUYoM8anhA+y+wtuKnYsZ esr1yMHGEV5varGEU7kQGDhTnaopQIQJxp+NgOaWgN2Q7/HiKNQ6BV/i4336YQAIgNGT Z7mQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C+foefUS5Woz3I8Qil0EbVvFr8aPDp91Q9wmkMo0GTs=; b=MNgtiNnI5PErUwPru3ZF4U4sy9ZpBrqa98UidQzMwdmBM+spWFiQro3r3xY9equOoV FBBO9Etj70r9lkjN/2rmud3xdfCYizKGpZhvp0f5im8qQQQC28XfJy3fCyFwrBbTCADJ V/WdJbEigF36VJWB5Se5C7MIRf97r+L1bv25gKEOLr9QP1Ub48E8LNggOs1H63oG6bKM +kk3WV+WL7RORoMX2LbX4nDx0D/vP3adrMOlsIiSTW9F63MjAlkfC5VH3hMQ2HzGQpuX 4iRuHYSCV5j5YjVG8UabguuOG93I+dPR0nqOV0WVwhxI1arVVoJGN184fncz7UtJKKIy pwYw== X-Gm-Message-State: AJaThX5Im9lfU1sOk49B6TDNj7f1BI6y8XK/aXs+ZbCKKOzZQyPtqM9J KKCW9gEm5fKrcvr1GS4SavWl1my5fkHpsW0yWYI= X-Google-Smtp-Source: AGs4zMYhU2zJbpD3yKbBrUdyyLG673Twurx3pYln7iiTbf0qce/t7K8s4AstP9hli4nt0w0bIzotmPImtQ1vLdqR3o8= X-Received: by 10.98.222.197 with SMTP id h188mr10874181pfg.132.1512142831263; Fri, 01 Dec 2017 07:40:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.100.186.208 with HTTP; Fri, 1 Dec 2017 07:39:50 -0800 (PST) In-Reply-To: References: From: Kathleen Moriarty Date: Fri, 1 Dec 2017 10:39:50 -0500 Message-ID: To: Adam Montville Cc: "sacm@ietf.org" Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:40:34 -0000 I agree with everyone else, one method to provide all of the updates seems like the best use of time for everyone. Thanks, Kathleen On Fri, Dec 1, 2017 at 10:27 AM, Adam Montville wrote: > No problem, thanks! A PR would certainly work. I can do any of those things. > Just not sure how many folks in the WG pay attention to GitHub, much less > the PRs that may be submitted there. > > On Fri, Dec 1, 2017 at 9:11 AM Kathleen Moriarty > wrote: >> >> Sorry, my email wasn't synced, and the PR was just a suggestion. >> >> On Fri, Dec 1, 2017 at 10:09 AM, Kathleen Moriarty >> wrote: >> > Hi Adam, >> > >> > Would a PR in github be a better answer? >> > >> > Best regards, >> > Kathleen >> > >> > On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville >> > wrote: >> >> All: >> >> >> >> At IETF 100 I offered to take the pen on our terminology draft. I've >> >> begun >> >> cleaning out the issues, and I have picked up where I left of in my >> >> review >> >> (which was back in July). I've finished my review, but I haven't yet >> >> added >> >> each of the issues. >> >> >> >> Would you prefer that I create an issue for each proposal I have, or >> >> would >> >> you prefer I simply make the changes and you can diff them later? >> >> >> >> I ask for two reasons. First, there are a lot of changes I'd like to >> >> make, >> >> and I'd be making at least another 30-40 issues. Second, most of the >> >> changes >> >> I'd like to make are clarifying (i.e. removing unnecessary terms, and >> >> superfluous language). >> >> >> >> Unless many of you would plan to review each of the issues, I would >> >> prefer >> >> to clean up the draft and deal with any objections that may come after >> >> the >> >> fact. >> >> >> >> Thoughts? >> >> >> >> Kind regards, >> >> >> >> Adam >> >> >> >> _______________________________________________ >> >> sacm mailing list >> >> sacm@ietf.org >> >> https://www.ietf.org/mailman/listinfo/sacm >> >> >> > >> > >> > >> > -- >> > >> > Best regards, >> > Kathleen >> >> >> >> -- >> >> Best regards, >> Kathleen -- Best regards, Kathleen From nobody Fri Dec 1 07:47:32 2017 Return-Path: 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 3FD0E129404 for ; Fri, 1 Dec 2017 07:47:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 G0hEXBpFe1KT for ; Fri, 1 Dec 2017 07:47:29 -0800 (PST) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 080A11293EC for ; Fri, 1 Dec 2017 07:47:29 -0800 (PST) Received: by mail-it0-x230.google.com with SMTP id b5so2907075itc.3 for ; Fri, 01 Dec 2017 07:47:28 -0800 (PST) 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=QIGZmhkP4VcNqaSrg1/HFbcpWl03U59NNefgI/d6HeU=; b=Nh3eUKewruQ+0oC1abe5I8/N8nLiBglkbh0jud4vCk2APAM3FtIXeJ6pZQovHuYRXU tC7WW1ahyTbT1COo8XuuUd7TSLt/BtgWsqf/UsYU96I5uBGrRaIX0lrrKHfDxTWgddEL sMPRaBFO5b0mmAWkXLXKqve+uaDRIibYzW5WtkL9uzFeB2SoOx7RWh7YG4y11b3omPJw G8RF79bs41c2UpLmzCNy1tplwtUtPL3/tm3vAA0yYT5AFmE6vB844VPb81FkwPAWvzuU 49eH4q/fTTGjOCSV8+3/4Y/Ld0BPcURxp3VN4TBDVM+j6sibMRU3VIYjw9zLwPEvPw04 IsYQ== 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=QIGZmhkP4VcNqaSrg1/HFbcpWl03U59NNefgI/d6HeU=; b=caQxRMkV/0BuOaH/rlZwKSvRGELMBSgFUX6afhOaa9yyoEVZK2HKBad2DPKfQiZhAC gkQwpvJZ6gDwYGoJ44Pi0UYVJXGeRte4ISQhQgp5o5u1MI/FoUToKOEnGQ39f94GUVqk E/V7Du4gzRbfqchzddTeLfuO310peVBFEvspfmMShjMbcI0TjrNDvQdkYuzGDtHGtP4j YwChG1KjYLFhXcoI92LbOj2FtXiB16wx7alDRN/GJhpf/Xe7o1vqLKGaxn3kubUsbPL8 obL0EI4UYhP77oMZbEfXc82pL/WueMDzzadYbmKeYKHP0bsuJQsqj76xrNmyjAyoOS1B Kg1Q== X-Gm-Message-State: AKGB3mKNMx98VwiRNw4jz5qzdwVWASk7lMe9n3N/f+X5A19gRC/+U0oa M1f/7n5vwtD1fhNMjJLjiaH/fkLpWiTo6QSRvgk= X-Google-Smtp-Source: AGs4zMaSuNyrDdlnRlXp2CJur0jhZrUZnSnj/DvH2UPDScVaedQQYO3IHUL2+GENSZJQHORuhi3ksuMZag0fZAgN16g= X-Received: by 10.36.61.144 with SMTP id n138mr2559583itn.109.1512143248094; Fri, 01 Dec 2017 07:47:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Adam Montville Date: Fri, 01 Dec 2017 15:47:17 +0000 Message-ID: To: Kathleen Moriarty Cc: "sacm@ietf.org" Content-Type: multipart/alternative; boundary="001a11444f7e26fa9e055f494951" Archived-At: Subject: Re: [sacm] SACM Terminology X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 15:47:31 -0000 --001a11444f7e26fa9e055f494951 Content-Type: text/plain; charset="UTF-8" outstanding! On Fri, Dec 1, 2017 at 9:40 AM Kathleen Moriarty < kathleen.moriarty.ietf@gmail.com> wrote: > I agree with everyone else, one method to provide all of the updates > seems like the best use of time for everyone. > > Thanks, > Kathleen > > On Fri, Dec 1, 2017 at 10:27 AM, Adam Montville > wrote: > > No problem, thanks! A PR would certainly work. I can do any of those > things. > > Just not sure how many folks in the WG pay attention to GitHub, much less > > the PRs that may be submitted there. > > > > On Fri, Dec 1, 2017 at 9:11 AM Kathleen Moriarty > > wrote: > >> > >> Sorry, my email wasn't synced, and the PR was just a suggestion. > >> > >> On Fri, Dec 1, 2017 at 10:09 AM, Kathleen Moriarty > >> wrote: > >> > Hi Adam, > >> > > >> > Would a PR in github be a better answer? > >> > > >> > Best regards, > >> > Kathleen > >> > > >> > On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville > >> > wrote: > >> >> All: > >> >> > >> >> At IETF 100 I offered to take the pen on our terminology draft. I've > >> >> begun > >> >> cleaning out the issues, and I have picked up where I left of in my > >> >> review > >> >> (which was back in July). I've finished my review, but I haven't yet > >> >> added > >> >> each of the issues. > >> >> > >> >> Would you prefer that I create an issue for each proposal I have, or > >> >> would > >> >> you prefer I simply make the changes and you can diff them later? > >> >> > >> >> I ask for two reasons. First, there are a lot of changes I'd like to > >> >> make, > >> >> and I'd be making at least another 30-40 issues. Second, most of the > >> >> changes > >> >> I'd like to make are clarifying (i.e. removing unnecessary terms, and > >> >> superfluous language). > >> >> > >> >> Unless many of you would plan to review each of the issues, I would > >> >> prefer > >> >> to clean up the draft and deal with any objections that may come > after > >> >> the > >> >> fact. > >> >> > >> >> Thoughts? > >> >> > >> >> Kind regards, > >> >> > >> >> Adam > >> >> > >> >> _______________________________________________ > >> >> sacm mailing list > >> >> sacm@ietf.org > >> >> https://www.ietf.org/mailman/listinfo/sacm > >> >> > >> > > >> > > >> > > >> > -- > >> > > >> > Best regards, > >> > Kathleen > >> > >> > >> > >> -- > >> > >> Best regards, > >> Kathleen > > > > -- > > Best regards, > Kathleen > --001a11444f7e26fa9e055f494951 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
outstanding!

On Fri, Dec 1, 2017 at 9:40 AM Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com= > wrote:
I agree with everyone e= lse, one method to provide all of the updates
seems like the best use of time for everyone.

Thanks,
Kathleen

On Fri, Dec 1, 2017 at 10:27 AM, Adam Montville
<adam.w.= montville@gmail.com> wrote:
> No problem, thanks! A PR would certainly work. I can do any of those t= hings.
> Just not sure how many folks in the WG pay attention to GitHub, much l= ess
> the PRs that may be submitted there.
>
> On Fri, Dec 1, 2017 at 9:11 AM Kathleen Moriarty
> <kathleen.moriarty.ietf@gmail.com> wrote:
>>
>> Sorry, my email wasn't synced, and the PR was just a suggestio= n.
>>
>> On Fri, Dec 1, 2017 at 10:09 AM, Kathleen Moriarty
>> <kathleen.moriarty.ietf@gmail.com> wrote:
>> > Hi Adam,
>> >
>> > Would a PR in github be a better answer?
>> >
>> > Best regards,
>> > Kathleen
>> >
>> > On Thu, Nov 30, 2017 at 4:35 PM, Adam Montville
>> > <adam.w.montville@gmail.com> wrote:
>> >> All:
>> >>
>> >> At IETF 100 I offered to take the pen on our terminology = draft. I've
>> >> begun
>> >> cleaning out the issues, and I have picked up where I lef= t of in my
>> >> review
>> >> (which was back in July). I've finished my review, bu= t I haven't yet
>> >> added
>> >> each of the issues.
>> >>
>> >> Would you prefer that I create an issue for each proposal= I have, or
>> >> would
>> >> you prefer I simply make the changes and you can diff the= m later?
>> >>
>> >> I ask for two reasons. First, there are a lot of changes = I'd like to
>> >> make,
>> >> and I'd be making at least another 30-40 issues. Seco= nd, most of the
>> >> changes
>> >> I'd like to make are clarifying (i.e. removing unnece= ssary terms, and
>> >> superfluous language).
>> >>
>> >> Unless many of you would plan to review each of the issue= s, I would
>> >> prefer
>> >> to clean up the draft and deal with any objections that m= ay come after
>> >> the
>> >> fact.
>> >>
>> >> Thoughts?
>> >>
>> >> Kind regards,
>> >>
>> >> Adam
>> >>
>> >> _______________________________________________
>> >> sacm mailing list
>> >> sacm@i= etf.org
>> >> https://www.ietf.org/mailman/listinfo/sa= cm
>> >>
>> >
>> >
>> >
>> > --
>> >
>> > Best regards,
>> > Kathleen
>>
>>
>>
>> --
>>
>> Best regards,
>> Kathleen



--

Best regards,
Kathleen
--001a11444f7e26fa9e055f494951-- From nobody Fri Dec 1 11:53:51 2017 Return-Path: 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 846421286D6 for ; Fri, 1 Dec 2017 11:53:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 mC6kDygP98GV for ; Fri, 1 Dec 2017 11:53:49 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 81E98127B73 for ; Fri, 1 Dec 2017 11:53:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=XO+MBKRSQMFXnrw0K5/cCs1Gx0k=; b=mORiS8iJ/4i/EtOo kvmwidA8vzpwyzEVVzwhZ4XoSCopsa9Uu+1l9wFIAHPgdJrJGI7DJWH1UwWTpeX/ ouZ10Dtq/Dqvr64j7GR0GtHCfRJPdCA5p1vm6QVF16+isqHHs8P9IZErEJ+ebOiZ wBbPaLs/mX9EpoJaucdbxDNwdYY= Received: by filter0961p1mdw1.sendgrid.net with SMTP id filter0961p1mdw1-30408-5A21B34C-7 2017-12-01 19:53:48.627941771 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0018p1iad2.sendgrid.net (SG) with ESMTP id nP-m6-_HSfqBibVXt-PkxA for ; Fri, 01 Dec 2017 19:53:48.731 +0000 (UTC) Date: Fri, 01 Dec 2017 19:53:48 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a21b34c84258_289d3fb40b5c4f281020c4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H+stJUA8jB7WxKdJkW/v49AoEsEPx2YohRDcNTb3gOSoLdmNTME+MGgUM8 xlh2q7s+L3y4nsMe+G0Z/bgFlJouGKyhufB6p6MLADRdbtv4akdyJ0/cIoPB5G1VG9rZdERN4lU0MR zbVzsWJKk/KLMELLAWiANC/H85xEay2IGLckZCik+fbb4lizwFruWaryEQ== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Processed Attributes (#17) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 19:53:50 -0000 ----==_mimepart_5a21b34c84258_289d3fb40b5c4f281020c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closing this because there isn't an architecture draft to speak of any more. -- 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-terminology/issues/17#issuecomment-348598403 ----==_mimepart_5a21b34c84258_289d3fb40b5c4f281020c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closing this because there isn't an architecture draft to speak of any more.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a21b34c84258_289d3fb40b5c4f281020c4-- From nobody Fri Dec 1 11:53:57 2017 Return-Path: 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 D2767127B73 for ; Fri, 1 Dec 2017 11:53:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, 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 t1KykfTAx30w for ; Fri, 1 Dec 2017 11:53:49 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39939124D85 for ; Fri, 1 Dec 2017 11:53:49 -0800 (PST) Date: Fri, 01 Dec 2017 11:53:48 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512158028; bh=iEzHB/XdqYYWsR24BvSyhYzDA+1vRtAfrMxE3miIMOM=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=U2pmDUGfzSu7TU5kBx1LVtgFPPdhqQJ+9ZI22hFYWTyW1gevGDM042ElHw4VPoOPO wCISa7IQmD6KWarJ3YCoT/dTdMz3uIwAmfCQ9RK+JtdgIQ/PoWaAOGEVPdeIyd9AXY bW2QMGg88Pp2xwTdAc8xfivGgdKrt5J7FQXs5T2I= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a21b34c937ce_27fd3fdeaf9c4f285662a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Processed Attributes (#17) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 19:53:51 -0000 ----==_mimepart_5a21b34c937ce_27fd3fdeaf9c4f285662a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #17. -- 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-terminology/issues/17#event-1368320028 ----==_mimepart_5a21b34c937ce_27fd3fdeaf9c4f285662a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #17.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a21b34c937ce_27fd3fdeaf9c4f285662a-- From nobody Sun Dec 10 06:48:57 2017 Return-Path: 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 89E73126C22 for ; Sun, 10 Dec 2017 06:48:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 pG5v3L_nxVOi for ; Sun, 10 Dec 2017 06:48:55 -0800 (PST) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 6FB17120724 for ; Sun, 10 Dec 2017 06:48:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=W3fhzf+xmsjv+9qaaMhgQPy0D8Y=; b=HJvNYWQYojZ8kLqq M9cOC7s1uoxes6Ii1edxJIbe4BOEEgGYXEPnuXfqrO9ToYwwT4G+HWRSQGXI51mR 2KAThUb1Fvg42PJiOI9ABBKD6HZjxQdmYFj6eBS9GjG+iT4gqnagDTNavCQes30C UkqiQwBNo7dQuiH/mK8sC1gzARE= Received: by filter0501p1mdw1.sendgrid.net with SMTP id filter0501p1mdw1-21501-5A2D4956-C 2017-12-10 14:48:54.255549338 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id wzLfRfKyQ5KyNzddo9xTeA for ; Sun, 10 Dec 2017 14:48:54.234 +0000 (UTC) Date: Sun, 10 Dec 2017 14:48:54 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49562583d_1f5b3f80dcbbef301364f8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HzWmW516OlfXx+3L8PR5AlWyX7nThTGZIUzPqSL8TqTZY95QJSCqQWwGKa kScTPcZZTcfdf5SgDkakXDcFFPV//m0qrRQ77d/8zGk2qW6BnCuBj5QRPuYvPphv+7hNx1MW/NVlJ/ Aq8X9CLSWXxcywX2uPWpMy34U6W2632OKXRmGEPm/s1o3cAofk8OL49UZA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should "Collection Method" be pulled out from "Collection Task" (#40) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:48:56 -0000 ----==_mimepart_5a2d49562583d_1f5b3f80dcbbef301364f8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #40. -- 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-terminology/issues/40#event-1380382163 ----==_mimepart_5a2d49562583d_1f5b3f80dcbbef301364f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #40.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49562583d_1f5b3f80dcbbef301364f8-- From nobody Sun Dec 10 06:49:02 2017 Return-Path: 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 C0D44120724 for ; Sun, 10 Dec 2017 06:48:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 Xj9n2_R0UJlM for ; Sun, 10 Dec 2017 06:48:55 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 A4D14120725 for ; Sun, 10 Dec 2017 06:48:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=FD3Ry4Szc3DOrldWPZgilfHdHFg=; b=ooHw8qotNx7IB+qG 5KIqy+bsy5eKG76kTqKrO1ImKSmZqUAh0+yvdZZ0DaI6UHPkDBpFQdrGvqpyLqBa VvjMIDsK0yT0YDrwC/DJG9DfX7e9BdSW81peqEHYjh/VkG66X4OgjPNO7EBbZlsy DIKvOwZloIXeapmcRxHw+t4NPjc= Received: by filter0587p1las1.sendgrid.net with SMTP id filter0587p1las1-11967-5A2D4956-13 2017-12-10 14:48:54.436532344 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0020p1iad2.sendgrid.net (SG) with ESMTP id 18YI2O41TP6_DRWLJKo8jQ for ; Sun, 10 Dec 2017 14:48:54.437 +0000 (UTC) Date: Sun, 10 Dec 2017 14:48:54 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49562745e_27e03fd8d89caf2c125e4"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H97LL9cIcOMDqlrDnEK8xvkoZRg3EeHexzf8RxJRZUnfwJuVihNhNIHZoK AYwgO3wlTtyHWA9GremJuGK500vMEgNyOJl8623Wg7bKKTnvctdlZGbmAD6EnIFU+LctoK4Co8sec3 zRbjUoa5yUVjkIje3uybmS+JrbTvzeKlxSspioz/edPCs3W0ypm18H53Gg== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we define "Endpoint Profile" or "Profile"? (#45) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:48:56 -0000 ----==_mimepart_5a2d49562745e_27e03fd8d89caf2c125e4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #45. -- 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-terminology/issues/45#event-1380382164 ----==_mimepart_5a2d49562745e_27e03fd8d89caf2c125e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #45.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49562745e_27e03fd8d89caf2c125e4-- From nobody Sun Dec 10 06:49:20 2017 Return-Path: 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 B442112785F for ; Sun, 10 Dec 2017 06:49:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 Jv7Snjt3K-rj for ; Sun, 10 Dec 2017 06:49:17 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 C902F1286B2 for ; Sun, 10 Dec 2017 06:49:11 -0800 (PST) Date: Sun, 10 Dec 2017 06:49:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512917351; bh=V+UPFn5WTZ7R1qQv9wYmhBPGOl4ufWpvKM1mUsKe6q4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JxL+01bkE8clhLOYTndcnyVCj0zd544kTpZCK96SFh4lweFIxLjyjj8/rVI/XV/7T 69CGHjwPzejLy3wTvNehk+FFIwp6Irj6JUj0BBGlFsfTsmI+27GKwBfpvY+uJsL+62 XJXRHJ/VBvXi/Aeu7cu1TQSC+DukhPRYMZqnO7u0= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967223ec_14953faf4f8c6f341138df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Please have "Endpoint Characterization" use "Endpoint Characteristic" in its definition (#44) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:19 -0000 ----==_mimepart_5a2d4967223ec_14953faf4f8c6f341138df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #44. -- 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-terminology/issues/44#event-1380382248 ----==_mimepart_5a2d4967223ec_14953faf4f8c6f341138df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #44.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967223ec_14953faf4f8c6f341138df-- From nobody Sun Dec 10 06:49:31 2017 Return-Path: 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 5471E12869B for ; Sun, 10 Dec 2017 06:49:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 mVTd_GQRysW5 for ; Sun, 10 Dec 2017 06:49:17 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 32DDF1286CA for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=UxoLrPQ3HoTIg+irovB7a3Efqgc=; b=LG8JkuCkx4ngl6mb TMVQNv9Eo0jEy0rOaC5xPWKRM9eQ/Lo/91Nhh5JVJWInJIAfkce0wzunVpNQZpL0 bbLaDNsmT4XCzXTNbYnV9ke1hmCPWJxmME/br4wR6+a78JPN4jMNeFhH+SNWqspE fc11fsokIUzYbmJnB21IO5A3pOo= Received: by filter1222p1mdw1.sendgrid.net with SMTP id filter1222p1mdw1-18651-5A2D4967-1B 2017-12-10 14:49:11.554433292 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id OsfIp8NFSzyf3XtfryuRWg for ; Sun, 10 Dec 2017 14:49:11.527 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49676bae3_c163ff760b20f387627f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H45woNWSkZwb6bWf2UEkeIinXvyHNhjo5sSzwmpMo+hTkRRf6HUHw4F4ia 2xLp1x/yFL2IkaVBJQt4sB24ju9sBnuiqUdigY/STYsADwksMcgunZjDBAur9a3ou8iNfqNceZJbpn B/nUPBa/IJDDfqmbdCCf/XjfBAkdtvUbfmlPUhvnlPKAjzQiyrwlLgvnFg== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Definition for "Excluded Endpoint" (#50) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:20 -0000 ----==_mimepart_5a2d49676bae3_c163ff760b20f387627f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #50. -- 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-terminology/issues/50#event-1380382254 ----==_mimepart_5a2d49676bae3_c163ff760b20f387627f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #50.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49676bae3_c163ff760b20f387627f-- From nobody Sun Dec 10 06:49:36 2017 Return-Path: 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 8F30E1286CA for ; Sun, 10 Dec 2017 06:49:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 gt2H-xnbY24R for ; Sun, 10 Dec 2017 06:49:20 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 4BF5A12878D for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=E7W1uPgyXzMrbVX92PQlk1Ngh6o=; b=D/hNBnUMKPXX2ChO sAp0C0sbYknCc0vvK0REL7XiPZidO0aYwTaTp0XgP87HeUonZT/804iyFIWn/Zbg SaPQYfvmVZiO9F61X8Wa52/nMuYYR+N3e77HUC8lUUOQ69ItQG7oVM6s6srDCpTN evZxZp9f8GpVkuf7x39/9DeqTXM= Received: by filter1177p1mdw1.sendgrid.net with SMTP id filter1177p1mdw1-11460-5A2D4967-14 2017-12-10 14:49:11.40144284 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0011p1iad2.sendgrid.net (SG) with ESMTP id 5996HdJPT7mV8HhqrOwttQ for ; Sun, 10 Dec 2017 14:49:11.623 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d496752a3f_72323fd9ffcb8f2c165813"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HyCyZSU26nl+hidSPj0TLKPh62c1VyMk4tRqvQm/BR77NtPTV9Cj6wzvt/ 13r8wEbq5iEhgoUSjVY9Zq5Mqp/anRBfdC+g+L5MvLI/Ibtq0aZDC13MfxKmWLMlgGUOe30JrSRyJA dtkoJTtqPa0kh4N5MbESv+mkIg1PgrALK5cwabEjKBW0/j3ysjTZMvFmew== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] "Endpoint Management Capabilities" (#47) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:22 -0000 ----==_mimepart_5a2d496752a3f_72323fd9ffcb8f2c165813 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #47. -- 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-terminology/issues/47#event-1380382251 ----==_mimepart_5a2d496752a3f_72323fd9ffcb8f2c165813 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #47.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d496752a3f_72323fd9ffcb8f2c165813-- From nobody Sun Dec 10 06:49:40 2017 Return-Path: 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 6BAC012785F for ; Sun, 10 Dec 2017 06:49:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 R7CeGEfh8aOR for ; Sun, 10 Dec 2017 06:49:21 -0800 (PST) Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 38074128768 for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Lo28nnpfagLeeuPtXCrlNDDAXn0=; b=QN1NhzDJu7rnmHSi TkeLbw3ecX1t9wE6ztBn4jKBqbVoaFRieOuXkgwgXOg2mpuhaKoPSUdRzA3QcIWv 7L/UjyFH5o+alysU+3g4lS91d+MUWplwfL8KDDIKEbiXbbOlbUF9bfkxOb2KXo/i 8DT0AoQP29LPCjtCnhGv3NY0w9c= Received: by filter0617p1mdw1.sendgrid.net with SMTP id filter0617p1mdw1-29697-5A2D4967-1 2017-12-10 14:49:11.02181893 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id rjiR_g6vTpiGxkeirHLy_w for ; Sun, 10 Dec 2017 14:49:11.058 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4966e5d53_2a6b3fee019e8f341888b9"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HwhIcn8hcZ1RcW+VJcQmSoLzlrQ2XGEKzaygRdwIto9oEjefA1ryoOTzQi kh4GQ9RgCX5QXD1EwG4yMDtSps/ln4OhDK6US937eQRuddhBYEw82VOeq1oho7qcRrUpppWtB1cUwC OsvFymwhJFTjhOGOav+0dZTAJepBkN/u4avI4qMHGENemFPBY529MKDhfw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Thoughts on "Data Origin" (#41) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:23 -0000 ----==_mimepart_5a2d4966e5d53_2a6b3fee019e8f341888b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #41. -- 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-terminology/issues/41#event-1380382244 ----==_mimepart_5a2d4966e5d53_2a6b3fee019e8f341888b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #41.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4966e5d53_2a6b3fee019e8f341888b9-- From nobody Sun Dec 10 06:49:45 2017 Return-Path: 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 A3193120724 for ; Sun, 10 Dec 2017 06:49:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, 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 toAuub549Z1B for ; Sun, 10 Dec 2017 06:49:23 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54755128799 for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) Date: Sun, 10 Dec 2017 06:49:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512917351; bh=jIhqIZ8tghO7Io2yhJ48zRuCmdbtPxe7faapauEIUDk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TCqva5w1rcd6LFA3/ieCTmNpobuEAGxkqPghs53Ya7yPqv/p+4Qt+y43OdiYvkmms obGDWFzcF24Y05AkC5IsmVkiO+xn3T0NyMALTcqSVuiXe1bM/zPkwhITj0PtHC95TY jjxA5MUsvljB0gzXJf0nAbcm+GHyDZWZgMEdTdis= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967a6042_5e623f9946f68f28177892"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Remove unnecessary text from "expected endpoint state" (#52) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:25 -0000 ----==_mimepart_5a2d4967a6042_5e623f9946f68f28177892 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #52. -- 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-terminology/issues/52#event-1380382256 ----==_mimepart_5a2d4967a6042_5e623f9946f68f28177892 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #52.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967a6042_5e623f9946f68f28177892-- From nobody Sun Dec 10 06:49:50 2017 Return-Path: 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 7D2D9120724 for ; Sun, 10 Dec 2017 06:49:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, 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 Pt7uJZyjFRgE for ; Sun, 10 Dec 2017 06:49:24 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C00B1288B8 for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) Date: Sun, 10 Dec 2017 06:49:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512917351; bh=KdZoInD0y5cz5OxH/Q8ZgdIriVVXZclnBA/a3WX/3p8=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fNYjOsXhgaQQNuNNEb2d28wsTfmNL4ukopphBwJdHyhNjSD2g+ZU3vjXqS78u7Dd+ GMU+6iQzomO2Qfzw1DU4W6aEU9mhzogRHm2a2hWVx1HuNoRy1SEUObwEWPbWYAz6AX Ce1Hr7FETI7CBqHBZnTt2Pnoez4e4gw8/zzY8Wwk= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: sacm , Comment Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967d2b38_1f973f80dcbbef3072332"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Thoughts on "SACM Function" (#53) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:25 -0000 ----==_mimepart_5a2d4967d2b38_1f973f80dcbbef3072332 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #53. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/53#event-1380382257 ----==_mimepart_5a2d4967d2b38_1f973f80dcbbef3072332 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #53.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967d2b38_1f973f80dcbbef3072332-- From nobody Sun Dec 10 06:49:54 2017 Return-Path: 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 957C7120724 for ; Sun, 10 Dec 2017 06:49:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 CU1fFQHhIGGS for ; Sun, 10 Dec 2017 06:49:24 -0800 (PST) Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 810FF12894A for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+daKvaTBreO2bUEnyZ1T0/NWYg8=; b=wfiaseIy7S47Rbk4 sMZls6VduZCeU2VDVDOm7WJWTXQC871bhqa4fYBnne3Cnf+18hNiaPfqeXJhfPM3 cQXGs16TjC5sjM7Yr5fj6YhHkUyVaZ8iiFev4nR8idRDnEmHeWf76Oqn7N/axJvN gF1suOOMlHuFocqxiEbeWNi6N0k= Received: by filter0374p1las1.sendgrid.net with SMTP id filter0374p1las1-20799-5A2D4967-13 2017-12-10 14:49:11.288270084 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id dVBr08VRSfqRsQBuSZgU5g for ; Sun, 10 Dec 2017 14:49:11.121 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967db29_66b93fcb19c02f281165ca"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/onnM1bgeOj2iHFnKTjU+ddsXqRBXip9ulnQLGEbj02zEjmI7IMT1KUdG EUCGLBcaB4aJUsdLcl5604FDccNxKJXJSkNPbnuQ7kA04HGXUBnK5OPyshKUhl+UuoK3WPi7U7BFXZ aG+aG4ffPS59sRocNhJ9aXNYJ21M7RM3mqA2zXQNfmHmpnb2id8DqvrgCA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Revisit "Endpoint Label" (#46) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:30 -0000 ----==_mimepart_5a2d4967db29_66b93fcb19c02f281165ca Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #46. -- 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-terminology/issues/46#event-1380382250 ----==_mimepart_5a2d4967db29_66b93fcb19c02f281165ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #46.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967db29_66b93fcb19c02f281165ca-- From nobody Sun Dec 10 06:49:57 2017 Return-Path: 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 CC9F61286CA for ; Sun, 10 Dec 2017 06:49:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 9BRv6mpWZ4IX for ; Sun, 10 Dec 2017 06:49:25 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 A730E128954 for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=lagXcY8VXVyghTlkvBJ2ZDvaYAs=; b=LIL0p2b9FxbvkOY6 iOoPTjOatBuzu8WOVsVDSyhwrdjTzVqS5V0v7ylfPfr+Q9iJJII6OcHz7YDXHuoy qKwrlzwO5J2EtLzQm0cWyQjZv1zxcM3B84+S4r+ZAEL3DLSyXILaSap96XLSWo0I rE1yX0PvYDqduMeWi2syQLBkPXw= Received: by filter0250p1las1.sendgrid.net with SMTP id filter0250p1las1-443-5A2D4967-1 2017-12-10 14:49:11.124472024 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id A1FuQmNISbmelCYKNPHcjQ for ; Sun, 10 Dec 2017 14:49:10.966 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4966d4663_a7e3f910982af3070442"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H6q029segslF3cDHeCXkYs2d0gsezFa4r0J8N3s0XoXaZhx62f3vPwrlud kwVZRTCHMMRWsBkk3zr/TOoPfmBRllmXXybKLpZbI9d9IWWHtof3riKyP3XrH6T5qplzli1uy9DFcG I8oiGFzx03oWEzZyNS5ww3my7HlGBOqNq2uTgqyoEgTfW8qjW20ndH/vhg== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Data Origin (#26) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:30 -0000 ----==_mimepart_5a2d4966d4663_a7e3f910982af3070442 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #26. -- 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-terminology/issues/26#event-1380382243 ----==_mimepart_5a2d4966d4663_a7e3f910982af3070442 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #26.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4966d4663_a7e3f910982af3070442-- From nobody Sun Dec 10 06:50:07 2017 Return-Path: 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 35F13128954 for ; Sun, 10 Dec 2017 06:49:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 4UhehIA0fY88 for ; Sun, 10 Dec 2017 06:49:29 -0800 (PST) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 3D9E8128961 for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=IUil3C79Wjv3e/NKySBfy1hnu94=; b=ZFt3iZMhd+iARXKF ArDQ7nr6cPmQdpnwve1Rr8yEYtB+z1xPICzH6jZ4XqSmFfDfYj4+OkJGWACbOk1t pYpp6w4HnDii3y8agzxiFmXQpNRANv3sXOtJQ89N9hovFg+0ulYj8A7PLGVCvN5R 8/mvMc+PcaJchd1wCtQolahXTu4= Received: by filter0983p1mdw1.sendgrid.net with SMTP id filter0983p1mdw1-30814-5A2D4968-1F 2017-12-10 14:49:12.287444743 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id CkaZeDkiSLeafNpj3tO9DQ for ; Sun, 10 Dec 2017 14:49:12.264 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d496827d02_7c2e3fe5397fcf341264f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H0vwK/pJm0gjF8ubUJ3pW9p3IxSC+jFOJPrY+1o5FytVk6fogRZCU7u0Pl lLDTNt6OjhB4PLvLJXsw25s0Zqjc2DG2A87LMyhtxp4ruZI4JamgpHBwr/pCOopYn7R+rPt3gXPtUC xpE1TpN3TZRM1C4PycxHgVVT9nIGsSZ20QzKyd+/6hCZ0JRs0WJNJPF6yA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose "hardware inventory" change to "endpoint hardware inventory" (#57) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:31 -0000 ----==_mimepart_5a2d496827d02_7c2e3fe5397fcf341264f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #57. -- 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-terminology/issues/57#event-1380382262 ----==_mimepart_5a2d496827d02_7c2e3fe5397fcf341264f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #57.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d496827d02_7c2e3fe5397fcf341264f7-- From nobody Sun Dec 10 06:50:11 2017 Return-Path: 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 6C8C6128A32 for ; Sun, 10 Dec 2017 06:49:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 KYSBjhekfRVS for ; Sun, 10 Dec 2017 06:49:31 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 7776E128990 for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=gBQNsl3vCIQG0knCrjZlKbeXPco=; b=JgoEKSdbgpzlMfyV IfHMbGjrx5da6gHii5SZ79uml77L/QIS40nkxSj+tjMBwsdIedBrCcfvfD/j59XH 5lzq3Z4GMi5ko4Z8v0OzBcPrbuQI5KfBscKfqjlNCX3A8xXWQNt+8LS3Jo9exKY/ JmbWUIUI0ZHCG1IE5rEwGv58Vbo= Received: by filter0199p1las1.sendgrid.net with SMTP id filter0199p1las1-31274-5A2D4968-17 2017-12-10 14:49:12.34858945 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id dh2ladv6QnOv2EunB0XsYQ for ; Sun, 10 Dec 2017 14:49:12.158 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4968d040_9bc3f9adaadaf344240"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/onnM1bgeOj2iHFnKTjU+fvsoI+etYR+9qh3wwXIVOyrSQDgyF+NcjCRN M+Ydwqj3N8BNfjPhP43AtNmT2vRc0RHsg4dpph5Y0tWMbJ0P4bya0Zud0K88CYvK3e1iWy3Ne972FX 2OkFQTWNEhGxxtqMQLq1eBMeSOYZHpELlyx/Gso5hlh4IXScNtLTyy4xog== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Remove superfluous text in "Guidance" (#55) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:32 -0000 ----==_mimepart_5a2d4968d040_9bc3f9adaadaf344240 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #55. -- 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-terminology/issues/55#event-1380382260 ----==_mimepart_5a2d4968d040_9bc3f9adaadaf344240 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #55.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4968d040_9bc3f9adaadaf344240-- From nobody Sun Dec 10 06:50:16 2017 Return-Path: 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 98258128AB0 for ; Sun, 10 Dec 2017 06:49:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 ymLTOZBJf5Dv for ; Sun, 10 Dec 2017 06:49:31 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 6F3E212896F for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Kp6IaLIDwaqZQZacBda9SWCevII=; b=VvwTlzhtycmDrOSu M7nD5zpjeB2j981ElXSWwJGub5oRuk4LRdWupo9cCRxWbTKEbvzlSqH8q1YCng6/ weiMaUNpqnuY0ee0OAXfim7CQTWjHpOUcCzi60lV7tNZqEYplAiYCm1Cvk1YGl4J td+DEwRW7zjdIDF/BganUfQeWcg= Received: by filter0516p1las1.sendgrid.net with SMTP id filter0516p1las1-19826-5A2D4967-4B 2017-12-10 14:49:11.772397279 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0020p1iad2.sendgrid.net (SG) with ESMTP id JWCw1-Z6R0qzqpDeh-47JA for ; Sun, 10 Dec 2017 14:49:11.662 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49675f4c3_1f8a3f80dcbbef305466b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H3tNww669/rg2q2vl7b+NQmtWkm/brAyN9mEDdVDjbTQ6xXYZIoMoWBdMM vH63YrgWDD/2Nq+Hcx4yWbIL6sO+s+VthCi2Tbha3wYl58i91AlylRKsiR/63OGZ5oRS/nPP4bnkS8 OwVPfblbBAv8cZsKo2WytTVuWYEaPo5Dpfer2jYi6YkuWHPMoapnQnEkIw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Definition for "Event" (#49) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:33 -0000 ----==_mimepart_5a2d49675f4c3_1f8a3f80dcbbef305466b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #49. -- 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-terminology/issues/49#event-1380382253 ----==_mimepart_5a2d49675f4c3_1f8a3f80dcbbef305466b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #49.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49675f4c3_1f8a3f80dcbbef305466b-- From nobody Sun Dec 10 06:50:21 2017 Return-Path: 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 D8D76128B27 for ; Sun, 10 Dec 2017 06:49:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 G4zZ5pM7Td1A for ; Sun, 10 Dec 2017 06:49:32 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 E44351289B5 for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=9n2FEt4nR1HrqirmZi3EZgqcPNs=; b=G4UfZfLon8axhrWL je0nv5gUOKiItai2A74KtX0A2cwLgIwd8krS0nDD1K/FZKWg5MbiLmeDSGfTq2Ka Hu8lAcQAvRZvVrVRLqWy1UysGAcQf2y/ZgxkkWY+d8Ouzt3CT4XyDCLMi06JciT8 Q9NvRT2G4UWU2PzbNAckXBOa5UA= Received: by filter0103p1las1.sendgrid.net with SMTP id filter0103p1las1-4200-5A2D4968-2A 2017-12-10 14:49:12.42165137 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id m-HE_i87R1uRXqCQ1k8Dfw for ; Sun, 10 Dec 2017 14:49:12.234 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4968267ca_9b33f9adaadaf34762eb"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H20dZHw7GyWqUPpopC/6DdJQVFA6JSl/IpMHNmonHnMVLs7mkOIAr03QS5 9BE5yyZppWzt4VFkfQXv/wb6TrugQtoAW6xCfMY3rDW8fAP9sofQ9d58cvYfyS0eC0OeZ8QPGtJhuP FhjZcTK3UoZom93jGvpe83mfJ+j/7aDDQQtQzkT6XvduwSlor0e6EabShA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] On "Hardware Component" (#56) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:34 -0000 ----==_mimepart_5a2d4968267ca_9b33f9adaadaf34762eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #56. -- 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-terminology/issues/56#event-1380382261 ----==_mimepart_5a2d4968267ca_9b33f9adaadaf34762eb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #56.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4968267ca_9b33f9adaadaf34762eb-- From nobody Sun Dec 10 06:50:25 2017 Return-Path: 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 F2CEB1289B5 for ; Sun, 10 Dec 2017 06:49:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 Vy6l1_lNjN0R for ; Sun, 10 Dec 2017 06:49:32 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 AB1831289B0 for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Gx5iEJlZh5UWpOefNzyLu2moG4U=; b=OEctH1uj2M6ARVxP +HkWWBHmY/7TFELk/ryBULkgP13TYwm6NoEOc/nFYzpbjV3n71iL7yyp48Oe5h/j mt1SdjxLmZ9u3UoS6igvIP2iHGQhawViDRdQO/sEkhSpDAnMo+mv0nQKrSS2t2Lr m57IY2H3ro2fBUlPvLA807qQcHc= Received: by filter0579p1las1.sendgrid.net with SMTP id filter0579p1las1-11993-5A2D4968-24 2017-12-10 14:49:12.669166787 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id awJi9DfBQe6N1e2R7Qyr3w for ; Sun, 10 Dec 2017 14:49:12.596 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49687f443_66b93fcb19c02f281181c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H8UASEM1cPZ7c9dGhU9yKsjPdLvDJg047FMaYh0anUU4n2nHZ456V+A48m Xtt4b6/hk29xR52sXYazaqMojplal+knA6nR/N7MAt9y3RhsK4BqEoYp3aXpfmHMJhkVnwGGJLspPM 1/0VfmwAODHgv4icNeY76cF6DupSzsPLzTtEBE7xtmMwdo/L/af8DigPkw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Is it possible to reduce the size of "SACM Component"? (#60) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:34 -0000 ----==_mimepart_5a2d49687f443_66b93fcb19c02f281181c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #60. -- 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-terminology/issues/60#event-1380382265 ----==_mimepart_5a2d49687f443_66b93fcb19c02f281181c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #60.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49687f443_66b93fcb19c02f281181c5-- From nobody Sun Dec 10 06:50:29 2017 Return-Path: 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 444D4128B44 for ; Sun, 10 Dec 2017 06:49:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 3KGqtOEs4rvR for ; Sun, 10 Dec 2017 06:49:33 -0800 (PST) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 007071289C3 for ; Sun, 10 Dec 2017 06:49:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=E9ayufJfU657SW2h1OSDtHyuY0U=; b=h04f1rIrlEwajBWK QKbTnbMQaFjeSe1qNBePzuaaIJQiPvax7kzdB59LDmPPxq5ZEq33H+WzthJm3CPx LsG4OA2Rs66zcaGGBrKF4Myf19u32rw+mpUC4qQG8RDND2NEC+A+Ssc0Gx+Oktqz pGkxeOtZvIwrqEXF/DYyPW144tA= Received: by filter0183p1las1.sendgrid.net with SMTP id filter0183p1las1-15228-5A2D4968-43 2017-12-10 14:49:12.77920163 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id xMldiUFpTWuLbd0ma6g6YA for ; Sun, 10 Dec 2017 14:49:12.681 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49689059a_ab63f910982af303281"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H26VevzztzeCr4Yt7qexLEJyIH7JWgBn2XV4PDIFjsrNXXI3wCBCdC36P1 r3WxVPqKH4lMJ9s53LN3fJ1+uSpwh6FoucwACQT/cEQEDfOmebH3XqUVgG16Yc81LqDfZqqht0yCS3 04mrosaoLCe4TfWQqVYQOO28vnoIdus/UuIWtbGPo+dqPuSohWOYUokqcA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Be more specific with common terms or leave them out (#59) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:35 -0000 ----==_mimepart_5a2d49689059a_ab63f910982af303281 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #59. -- 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-terminology/issues/59#event-1380382264 ----==_mimepart_5a2d49689059a_ab63f910982af303281 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #59.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49689059a_ab63f910982af303281-- From nobody Sun Dec 10 06:50:33 2017 Return-Path: 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 192531288B8 for ; Sun, 10 Dec 2017 06:49:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 pIfucSToSimW for ; Sun, 10 Dec 2017 06:49:29 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 BEDD112895E for ; Sun, 10 Dec 2017 06:49:12 -0800 (PST) Date: Sun, 10 Dec 2017 06:49:12 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512917352; bh=Zzk9hN46l0sTXx4f+RDVve5rpJXDqiF5K3RPUzwtaXk=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RXl1Xzb9csE2tGWNZpujXgnS4z/1VPeXDkFO2b31uBItz2yVrhBSS9RxCG9ODWc7+ lBytHlGN7DYqfWps3fhTRGU5bT+Eb5abWnvPx7fJk6htdpBD97/NSZV0av6I8Z4uI3 NSjbLZfOZMKinUppG6xZgU+sv1MsbFI0wmQyBPT4= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49682140d_69e33fd9ffcb8f2c1139ea"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Feedback on "guidance" (#54) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:49:31 -0000 ----==_mimepart_5a2d49682140d_69e33fd9ffcb8f2c1139ea Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #54. -- 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-terminology/issues/54#event-1380382259 ----==_mimepart_5a2d49682140d_69e33fd9ffcb8f2c1139ea Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #54.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49682140d_69e33fd9ffcb8f2c1139ea-- From nobody Sun Dec 10 06:51:35 2017 Return-Path: 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 7D413128B37 for ; Sun, 10 Dec 2017 06:51:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 wzywTWFhP3D0 for ; Sun, 10 Dec 2017 06:51:33 -0800 (PST) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 370531289B5 for ; Sun, 10 Dec 2017 06:50:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=y53DSdC3l8Wvl6Xr6VfC231rMZM=; b=rsG2rfHNg3kotomW k6PXGiFsqt6F3m3lTo/R+bH3d+JYMPJMWlK68GuhKE00Xai2/7Wfh5CsoSVViICO JV0XfwHtYvTddK8Vlj8jSRIiInUKdFkN0Jyuc0xt/vyRZvcXx+WZgga3Q7d5Kdwz bg4ASbIWHa2ETQZdUUL3v0JC3Lw= Received: by filter0633p1las1.sendgrid.net with SMTP id filter0633p1las1-14228-5A2D4967-1A 2017-12-10 14:49:11.509244791 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id JHyKbIIbRLy6BZnqCPn8tA for ; Sun, 10 Dec 2017 14:49:11.383 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49674cde5_6c353fcab06bcf28435c2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H3tNww669/rg2q2vl7b+NQnIZMEKri4aT+1w9bygN1cUhaL4TDlA80dniH l63GnWST3qtebj9DP0DKwk1WUWmI41/XSXGKxGlB+L84jEBfsvuNlriOL98kH0HGcaLi4zknf3cfrm 5OV24RBS1jj5PvjPrMhZsRfM9/lU/Fta2ukyHKGcSrWhUTxVFZw51TCIPg== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to definition for "Evaluation Task" (#48) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:51:34 -0000 ----==_mimepart_5a2d49674cde5_6c353fcab06bcf28435c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #48. -- 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-terminology/issues/48#event-1380382252 ----==_mimepart_5a2d49674cde5_6c353fcab06bcf28435c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #48.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49674cde5_6c353fcab06bcf28435c2-- From nobody Sun Dec 10 06:51:45 2017 Return-Path: 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 D078312878D for ; Sun, 10 Dec 2017 06:51:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 vXgGXhSmmgRR for ; Sun, 10 Dec 2017 06:51:34 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 4064F128D2E for ; Sun, 10 Dec 2017 06:50:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=btCXwqoJolhyzSYCdn7RiqYH74c=; b=PQzUlEAyzrCX8o42 fsGmVkKQSopN0QBKVO0lA44KXTG7inS7KvGtguWbOBHNQ/NKIoTDn/+8Dua9fTwN CLcgCIYuhG8qdTViAXgcwFGSpUO6AVz580vYR/99IaQHNYQsnUB7qZNnR6pJqjwv E94UXODkzOz9BzvmEeDzrol40Lg= Received: by filter0087p1las1.sendgrid.net with SMTP id filter0087p1las1-31567-5A2D4967-1D 2017-12-10 14:49:11.255680039 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0009p1iad1.sendgrid.net (SG) with ESMTP id qwt_UmlNT7OgO4cqWz2TWQ for ; Sun, 10 Dec 2017 14:49:11.131 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:11 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967103a1_14b43faf4f8c6f3460616"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H8gCIRJQFjv0SMTVT9zvGc/nn84upa80HgROxY2ZFE+ONz92Ac9cEnalsj ceSSAyzbv+tZf4acEmMMyg8QYuJegAjnRtYJZ8+CoHGOYwC/Cg2JstU1gL05GzUTSR8zv4A12KAYVV 0Tesxqq/28gWhnGG0Ag3p0Cyb4uoDNOpYEws0jFsNvNVRSxDq2KCzVVl+A== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] "Endpoint Attribute" should probably not use "Information Element" in its definition. (#42) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:51:36 -0000 ----==_mimepart_5a2d4967103a1_14b43faf4f8c6f3460616 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #42. -- 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-terminology/issues/42#event-1380382245 ----==_mimepart_5a2d4967103a1_14b43faf4f8c6f3460616 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #42.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967103a1_14b43faf4f8c6f3460616-- From nobody Sun Dec 10 06:51:49 2017 Return-Path: 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 5D05E128BBB for ; Sun, 10 Dec 2017 06:51:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 T40qMa_f84px for ; Sun, 10 Dec 2017 06:51:39 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 68F6F128DE5 for ; Sun, 10 Dec 2017 06:50:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zJcz/3D4jR7Cr7PwAaIwT7SSXRM=; b=K8cT9TUKnRPd47L1 TvWlmkUE6Le6u79OgYdtHqM8brpqFQm91U66ehAku8rzkBsU5Mu9aFOP5Z6n5q2E y0qwNROdA3C+vN+IOfZl0zVOlLWq8IOa22vjpMI6BlfYKIIlSWNaETqo7GwfLH1J U+l9ViLtlgje4D7WOFNZjyJs+So= Received: by filter0207p1las1.sendgrid.net with SMTP id filter0207p1las1-4729-5A2D4967-1A 2017-12-10 14:49:11.822264784 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id YoK5CvwGQ7iwaL4p4Lncag for ; Sun, 10 Dec 2017 14:49:11.799 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4967a212d_149f3faf4f8c6f34164ef"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxPHXuAUy9XW3sQPQJs30zBC12yLWwX0BOWD261LKBSmtLwmvBGjOCnzKz sHMMDNAqnZJk8yKhqv6eQ7htpiZHo4112DFQAMVm8FpTZs+1vAB3H5ab/omcdaz+vRmPEKjm7BGm+B E3JVKNJZsbVJnzB16lnt0/PDQtpp2pRL5/623yHwg9c2wrAQ/Z9ptoHWCA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should "expected endpoint state" be "expected attribute value" or "expected attribute state"? (#51) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:51:40 -0000 ----==_mimepart_5a2d4967a212d_149f3faf4f8c6f34164ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #51. -- 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-terminology/issues/51#event-1380382255 ----==_mimepart_5a2d4967a212d_149f3faf4f8c6f34164ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #51.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4967a212d_149f3faf4f8c6f34164ef-- From nobody Sun Dec 10 06:51:54 2017 Return-Path: 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 AF19F128DF2 for ; Sun, 10 Dec 2017 06:51:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 MfqEAp4Adrf5 for ; Sun, 10 Dec 2017 06:51:46 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 B2FB01293EC for ; Sun, 10 Dec 2017 06:50:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=iG2ix2Ok9eX9dmHRNp7dtYZrSoc=; b=Nc/tXG7cYHMJDkRS m6NiTZv3u4DcU4dCSE2InIBCMxQ8F0SGXJwR5po5eN4y25KrlA+rk8wDfDQfMHcf TBI5cGCtCVtIJyqwH3XN4l4/s9rZcP3QQQ+0qLfCH4lqGa2p+CVjLMbjrBwSbAvc O/lO7ct/aYWXlv/NY4laUYlbpA8= Received: by filter0565p1las1.sendgrid.net with SMTP id filter0565p1las1-14767-5A2D4968-20 2017-12-10 14:49:12.6669214 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id xdRjpVFaTviNWKevMf9d2A for ; Sun, 10 Dec 2017 14:49:12.575 +0000 (UTC) Date: Sun, 10 Dec 2017 14:49:12 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d49686eb92_a8c3f9adaadaf34666e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H26VevzztzeCr4Yt7qexLELLLpl6uk9Un0wEYQMwIbFoUg1K8RUG6Z08X8 tOtxUpPTPvc7PhpqTiV6Jst/JZT+emr6GTRFctsi3j+G8NnODl5sHkMpsQ08vzbFSD+o+SGK4w2x0A g5lITL2uWQfqttnFeiapAV4jsLXlOoodsaPIhM4gY4SjF4zOBV7tUVoy6g== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Is pruning of terms needed? (#58) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:51:48 -0000 ----==_mimepart_5a2d49686eb92_a8c3f9adaadaf34666e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #58. -- 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-terminology/issues/58#event-1380382263 ----==_mimepart_5a2d49686eb92_a8c3f9adaadaf34666e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #58.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d49686eb92_a8c3f9adaadaf34666e2-- From nobody Sun Dec 10 06:59:00 2017 Return-Path: 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 0B728127B57 for ; Sun, 10 Dec 2017 06:58:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.908 X-Spam-Level: X-Spam-Status: No, score=-5.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, 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 Ljsu7Ga9QSqU for ; Sun, 10 Dec 2017 06:58:57 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66EA1120724 for ; Sun, 10 Dec 2017 06:58:57 -0800 (PST) Date: Sun, 10 Dec 2017 06:58:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512917936; bh=4wuXQo9X1trEEP8MhPS+oZqWN2GCtY5Lr+BRKND/FAI=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post:From; b=bazwjLrVPt6RJmEz9EigWab1OmrVgZG854qmhZ7/P35mSQC8Q8BpuETYktbW5+87p UWel4UwZ41HvrmljNtZc3WgbWpUC1hQj1zUIAWMg+j5phlnLLsWtscn/9aqbEGB7bt SD3fnM33JEK0oKeNoum0eBRS7ldsGKP8VyHGDMIc= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4bb0b9509_1a8793ffaf373cf342167f6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Updating from 13-14 X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 14:58:59 -0000 ----==_mimepart_5a2d4bb0b9509_1a8793ffaf373cf342167f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit * Handled a plethora of issues listed in GitHub. * Pruned some commonly understood terms. * Narrowing term labels per their definitions. * In some cases, excised expositional text. * Where expositional text was left intact, it has been separated from the actual definition of a term. -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/releases/tag/draft-ietf-sacm-terminology-14 ----==_mimepart_5a2d4bb0b9509_1a8793ffaf373cf342167f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
  • Handled a plethora of issues listed in GitHub.
  • Pruned some commonly understood terms.
  • Narrowing term labels per their definitions.
  • In some cases, excised expositional text.
  • Where expositional text was left intact, it has been separated from the actual definition of a term.

—
You are receiving this because you are subscribed to this thread.
View it on GitHub or mute the thread.

----==_mimepart_5a2d4bb0b9509_1a8793ffaf373cf342167f6-- From nobody Sun Dec 10 07:01:25 2017 Return-Path: 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 D43F4127B57 for ; Sun, 10 Dec 2017 07:01:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 pkmIYkFf3ov6 for ; Sun, 10 Dec 2017 07:01:22 -0800 (PST) Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 95938120724 for ; Sun, 10 Dec 2017 07:01:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=aj9yGC0mYEiJ7Qnk4vdQzegE4Vo=; b=GZU/SqRwEq6pOdHf 13ZLdm1nUr3zfme49Us5cJ5+LLLy2VGDR067cKICN0ll8YbQpYk8KaMBhobFo0Et AIvFpJWtbuwgax8Cne5A47qhsFxRmms8ef9PX/3ZDzEOBQ7HiH+AIZBoGLYzbQOH cKv9YMkCtTSMZLvUwWJcuQbWzU4= Received: by filter0118p1las1.sendgrid.net with SMTP id filter0118p1las1-3473-5A2D4C3C-6D 2017-12-10 15:01:16.823434645 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id sZtWISbGTPGeqiQPorj2mQ for ; Sun, 10 Dec 2017 15:01:16.714 +0000 (UTC) Date: Sun, 10 Dec 2017 15:01:16 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4c3c942fa_676e3fcb19c02f2811069a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxGln4ikXLg1tcqPqaC3ytFIY9rhQ/Uf7fRncD66A6VVDi+hPRMGz5b4nS u/HanG01Wjk6Lsu8pZ0iNilVwEL5BGqPWbN3JTrUVyRIWa4TnDzxHUlMUc8G9Ml2QAnPnicGEg8Xjs 5g3dNBNMfCUChVYj22jVMRNPFUP6G2fe3Xt0qEr4U4kXQJ+sYmTPiBN6jw== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "asset" to "SACM asset"? (#61) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:01:24 -0000 ----==_mimepart_5a2d4c3c942fa_676e3fcb19c02f2811069a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The current definition of *asset*: `Is a system resource, as defined in {{RFC4949}}, that may be composed of other assets.` This may amount to changing the definition of asset to something more specific without also changing the label for the definition. -- 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-terminology/issues/61 ----==_mimepart_5a2d4c3c942fa_676e3fcb19c02f2811069a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The current definition of asset: Is a system resource, as defined in {{RFC4949}}, that may be composed of other assets. This may amount to changing the definition of asset to something more specific without also changing the label for the definition.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4c3c942fa_676e3fcb19c02f2811069a-- From nobody Sun Dec 10 07:02:43 2017 Return-Path: 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 028CE127B57 for ; Sun, 10 Dec 2017 07:02:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 5-XmUJcg8_oJ for ; Sun, 10 Dec 2017 07:02:40 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 94364120724 for ; Sun, 10 Dec 2017 07:02:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=uHuxEwsNB+iSTN71VCbH9Vgek2s=; b=I6GyMWld+ef9ilRk wYbFdCnUO0fk9Gcx79nQeqWahLRXhMNrEjPro8MmCL0iLL092vg365oqnIeMbSp7 ukBXmbf+LwjE+Ut3FWYVdvw6uz+6IzMoyepZGmpBH7gUAM9DKnQNuTWq17rKC0qM v8dUA7UIC+SlP/hMteLn8CD8Zlg= Received: by filter0624p1mdw1.sendgrid.net with SMTP id filter0624p1mdw1-30332-5A2D4C8F-7 2017-12-10 15:02:39.241434614 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id br5hAM11RlatNI4Q3FQVlg for ; Sun, 10 Dec 2017 15:02:39.225 +0000 (UTC) Date: Sun, 10 Dec 2017 15:02:39 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4c8f215ab_1f1b3fba41810f34138458"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H41GED4ggEVKYc/U2uci1mOo1Y9ACPbeldSQcov5HYzJG00UzIhNirYH7h ozFp/eNLcQcvOvDUwCDVvm+UajUGV7ffxGYMF3EgAZnU3Xaj1/bJJXZ0Dg9+0wsoAqWXRZCinJ8df8 Y67W+tVxw2oVbrx/mChEtQZFpIn5ob7/PKRGoQgqWwHS4dFlZ82r5FwNkA== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:02:42 -0000 ----==_mimepart_5a2d4c8f215ab_1f1b3fba41810f34138458 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The present definition of attribute: `Is a data element, as defined in RFC5209, that is atomic.` This amounts to refining the definition of the term without giving it a more specific label. -- 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-terminology/issues/62 ----==_mimepart_5a2d4c8f215ab_1f1b3fba41810f34138458 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The present definition of attribute: Is a data element, as defined in RFC5209, that is atomic. This amounts to refining the definition of the term without giving it a more specific label.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4c8f215ab_1f1b3fba41810f34138458-- From nobody Sun Dec 10 07:06:22 2017 Return-Path: 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 E5536126DFF for ; Sun, 10 Dec 2017 07:06:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 Rz95m1R6B_UX for ; Sun, 10 Dec 2017 07:06:20 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 00883120724 for ; Sun, 10 Dec 2017 07:06:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=fL/oD0vFx0Ml3hryEbesY0QMvqc=; b=I+h6+cYUgFrJAfU5 ox3fMUT7MJX8fXhIo9JwWa1DoAXZPW/YaxS4ipiUKDhlfFzsP+lB0V4DLn1hEfUA 9Ma71DLc4mmPGQiBDqEpxaXzwgffjFT2ZgN1regvo+TDXJR6T2wdHPyHR5The7F4 QuN6MV57QcvGpk4uP4tDsbF7+3s= Received: by filter0588p1mdw1.sendgrid.net with SMTP id filter0588p1mdw1-20466-5A2D4D66-24 2017-12-10 15:06:14.60768762 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id h-lsdSYNTOKeJXO-U9cYTg for ; Sun, 10 Dec 2017 15:06:14.556 +0000 (UTC) Date: Sun, 10 Dec 2017 15:06:14 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4d6671b03_1f903f80dcbbef3012262c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9Hx+I1vZIJXHuskIiDINwoGuDgVJoDk+6YjAmJZV8PpR0AP0ag+SQoJ1FJH /mPa7UAvdTFRXmZz0iMK/uOaX5WW+jBWzPrF/1W/+xeJzqvPwhvMf0arCgS7tdZn+IP7QpRn7auFwB Ip9M7TgqoU8MAet86kT3sv5lDzVOrdfvPb8VU90dbICkmuKcWSNpjAxuzQ== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposing a new approach to state and configuration (#63) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:06:21 -0000 ----==_mimepart_5a2d4d6671b03_1f903f80dcbbef3012262c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I believe we have poor definitions for configuration and state. We define configuration as non-volatile endpoint attributes and state as volatile endpoint attributes. This feels dissatisfying. I would propose that we take an approach indicating that endpoint state embodies endpoint attributes (they may as well be synonymous), and that state may be volatile or non-volatile. Then, configuration is sometimes used interchangeably with state or attributes. -- 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-terminology/issues/63 ----==_mimepart_5a2d4d6671b03_1f903f80dcbbef3012262c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I believe we have poor definitions for configuration and state.

We define configuration as non-volatile endpoint attributes and state as volatile endpoint attributes. This feels dissatisfying. I would propose that we take an approach indicating that endpoint state embodies endpoint attributes (they may as well be synonymous), and that state may be volatile or non-volatile. Then, configuration is sometimes used interchangeably with state or attributes.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4d6671b03_1f903f80dcbbef3012262c-- From nobody Sun Dec 10 07:09:20 2017 Return-Path: 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 97C62128768 for ; Sun, 10 Dec 2017 07:09:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.182 X-Spam-Level: X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 rM3q_zaG_Bzi for ; Sun, 10 Dec 2017 07:09:16 -0800 (PST) Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (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 89A1012894A for ; Sun, 10 Dec 2017 07:09:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=pGJ+ASINMAw0WsGuawwd555OIJ8=; b=fkPCUA/641dd1us0 2MegWvCiJlT/dT9iToG4jhafPlB02Hp3UqPOBhVqHt8GfeQOKRlrE+1LMO6LPGg6 APRtCXL3ZAXHzRwIEUWXAqcZ7PVqxT0aeFMiNjzy2qUzY8O9HjjVsW28Va35WRwD GR9+nF/3Sp8rF71czOieDvYdZ3c= Received: by filter0419p1mdw1.sendgrid.net with SMTP id filter0419p1mdw1-17088-5A2D4DF0-B 2017-12-10 15:08:32.195641408 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0023p1iad2.sendgrid.net (SG) with ESMTP id ReUtkxbqTl6gr_o1d8oT4A for ; Sun, 10 Dec 2017 15:08:32.160 +0000 (UTC) Date: Sun, 10 Dec 2017 15:08:32 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4df0ee4b_66ae3fcb19c02f28181466"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/rbuwTXslxgYo7PNGEUw0XtfWw9tV4r36yya/6LU8LvJ/qidYOw/cp7pi ml4WwFlZfmV2ibE1gAP8yabzj2jeg3EJeDQ3zxOxZfyxtHg+w/Z9MLrGsKmY/45saGeJeM2ZgLPfmW ClQBFDUKQw7eK8vkQ81vNcVIvUvZHVxK0MlM3tAAKKkfdirq+HIzMTr1Ow== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:09:18 -0000 ----==_mimepart_5a2d4df0ee4b_66ae3fcb19c02f28181466 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit For Data In Motion we say, "The SACM architecture and corresponding models focus on data in motion." For Data At Rest we say, "In the context of SACM, data models for data at rest are out of scope." Do we really need either of these statements in the terminology draft? They seem out of place. -- 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-terminology/issues/64 ----==_mimepart_5a2d4df0ee4b_66ae3fcb19c02f28181466 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

For Data In Motion we say, "The SACM architecture and corresponding models focus on data in motion."

For Data At Rest we say, "In the context of SACM, data models for data at rest are out of scope."

Do we really need either of these statements in the terminology draft? They seem out of place.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4df0ee4b_66ae3fcb19c02f28181466-- From nobody Sun Dec 10 07:11:09 2017 Return-Path: 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 E70FE124D85 for ; Sun, 10 Dec 2017 07:11:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 iGTBPDbmA7ZJ for ; Sun, 10 Dec 2017 07:11:06 -0800 (PST) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 C5E76120724 for ; Sun, 10 Dec 2017 07:11:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xHaFFJ2SFF0+tQEfA3OkCiUXDxk=; b=exRnduEWiFILcOtu 1CxGzug28rtoBQmA0+wf+bKSeFCcmNBpISY1J/0zEm5i7yAnJ6Vo/RnAPIWMoKk/ 7GIZmJ7RrXMtTF0pwl1kBfYqyAJqpxMmFBB86kW4Hn8bD8b00+lWYhvLyJU+BHUE SKmh21FBoQw7OhCts4IqR3wZ0UE= Received: by filter0481p1mdw1.sendgrid.net with SMTP id filter0481p1mdw1-19133-5A2D4E87-12 2017-12-10 15:11:03.681795888 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id 2KnfgXEdQJaXV2MiVDlhCg for ; Sun, 10 Dec 2017 15:11:03.636 +0000 (UTC) Date: Sun, 10 Dec 2017 15:11:03 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4e8786dd2_66bc3fcb19c02f28135674"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HztgXJ84/fr16DU24e7IgJJVXRaz5VR5CiabteyUPzphK1wQvl5Eu6Ui0L fMb5kmcY+LfaVCJW6dybbVv3ileoA29h/rDUesTCY1aPZfuO4t8CS8f2geOTmfg9hdtjLy67ZQ2FnI iTcQIveoT/ZCc0taKW2XGWcU8gihga07feDPdM9GE3QoXVGaHOjuE3BKpg== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Interaction Model from terminology (#65) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:11:08 -0000 ----==_mimepart_5a2d4e8786dd2_66bc3fcb19c02f28135674 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As presently defined: > "The definition of specific sequences regarding the exchange of messages (data in motion), including, for example, conditional branching, thresholds and timers. An interaction model, for example, can be used to define operations, such as registration or discovery, on the control plane. A composition of data models for data in motion and a corresponding interaction model is a protocol." This definition feels very similar to process or workflow (the latter is defined in our terminology as "A workflow is a modular composition of tasks that can contain loops, conditionals, multiple starting points and multiple endpoints"). I move to strike this term from the terminology unless there is some compelling reason to keep it. -- 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-terminology/issues/65 ----==_mimepart_5a2d4e8786dd2_66bc3fcb19c02f28135674 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

As presently defined:

"The definition of specific sequences regarding the exchange of messages (data in motion), including, for example, conditional branching, thresholds and timers. An interaction model, for example, can be used to define operations, such as registration or discovery, on the control plane. A composition of data models for data in motion and a corresponding interaction model is a protocol."

This definition feels very similar to process or workflow (the latter is defined in our terminology as "A workflow is a modular composition of tasks that can contain loops, conditionals, multiple starting points and multiple endpoints").

I move to strike this term from the terminology unless there is some compelling reason to keep it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4e8786dd2_66bc3fcb19c02f28135674-- From nobody Sun Dec 10 07:13:05 2017 Return-Path: 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 1381B124D85 for ; Sun, 10 Dec 2017 07:13:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.999 X-Spam-Level: X-Spam-Status: No, score=-6.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, 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 QG3aaUxnjbL2 for ; Sun, 10 Dec 2017 07:13:02 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85104120724 for ; Sun, 10 Dec 2017 07:13:02 -0800 (PST) Date: Sun, 10 Dec 2017 07:13:01 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512918781; bh=fne01Cme54sSIGfHdUXFJr7Ap09gsJ3ZpKNDimWqXZE=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ORcHukaX8RUCdRxUIVSYYCy9nsyypRZmCE95EtoUDrZTqDAiRK+nZsRlpyZsy2SkB 4aVEdrSb6HwmsHpkpoh4qJB7iq0ke1KFK2X1MkS2Jpi1uU6/v7U+4sA2QDIKBv9KE1 T0I1KMgDHYQXdGkX7qWgSzYZk7pcGFHuDDMOpSzc= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4efd98003_148c3faf4f8c6f341004a0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:13:04 -0000 ----==_mimepart_5a2d4efd98003_148c3faf4f8c6f341004a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit At its heart, metadata is simply "data about data", and there really isn't much more to say. There is a bunch of expositional text associated with the term in the draft: > In the SACM information model, data is referred to as Content. Metadata about the content is referred to as Content-Metadata, respectively. Content and Content-Metadata are combined into Subjects called Content-Elements in the SACM information model. Some information elements defined by the SACM information model can be part of the Content or the Content-Metadata. Therefore, if an information element is considered data or data about data depends on which kind of Subject it is associated with. The SACM information model also defines metadata about the data origin via the Subject Statement-Metadata. Typical examples of metadata are time stamps, data origin or data source. This information isn't really helpful to the definition, and because metadata is a very common term and widely understood as data about data, I propose we remove the term from this draft. -- 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-terminology/issues/66 ----==_mimepart_5a2d4efd98003_148c3faf4f8c6f341004a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

At its heart, metadata is simply "data about data", and there really isn't much more to say. There is a bunch of expositional text associated with the term in the draft:

In the SACM information model, data is referred to as Content. Metadata about the content is referred to as Content-Metadata, respectively. Content and Content-Metadata are combined into Subjects called Content-Elements in the SACM information model. Some information elements defined by the SACM information model can be part of the Content or the Content-Metadata. Therefore, if an information element is considered data or data about data depends on which kind of Subject it is associated with. The SACM information model also defines metadata about the data origin via the Subject Statement-Metadata. Typical examples of metadata are time stamps, data origin or data source.

This information isn't really helpful to the definition, and because metadata is a very common term and widely understood as data about data, I propose we remove the term from this draft.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4efd98003_148c3faf4f8c6f341004a0-- From nobody Sun Dec 10 07:15:52 2017 Return-Path: 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 28071124D85 for ; Sun, 10 Dec 2017 07:15:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 Yue3LUeMdRG4 for ; Sun, 10 Dec 2017 07:15:49 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 58146120724 for ; Sun, 10 Dec 2017 07:15:49 -0800 (PST) Date: Sun, 10 Dec 2017 07:15:48 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512918948; bh=YaGrrlaTbUaHQeptVaXCtWWKV5ZR8IpLpMbWJ533WuE=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=GqVpP6dzMt7eBZM/lo/CRaG//MrpKqmfsfGjVJ8q1oaDFvNksAePAZBxKDKYHf2dQ johfQupSfGKgcreeT/srmNMgnZ3kdaROcXbxb7ZecMriWcnAdCynTvqylifdA+T+Vx NE7dCLlXJLXFf5HuWk2ZJexmv7V5h7lS8Yj7c4rU= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d4fa4ad968_c133ff760b20f3812271a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Need to clarify "attribute" vs. "posture attributes" (#67) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:15:51 -0000 ----==_mimepart_5a2d4fa4ad968_c133ff760b20f3812271a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit attribute: "Is a data element, as defined in RFC5209, that is atomic." posture attributes: "Defined in RFC5209 as 'attributes describing the configuration or status (posture) of a feature of the endpoint. A Posture Attribute represents a single property of an observed state. For example, a Posture Attribute might describe the version of the operating system installed on the system.'" Perhaps we simply make "posture attributes" singular, then define attribute as "see posture attribute"? -- 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-terminology/issues/67 ----==_mimepart_5a2d4fa4ad968_c133ff760b20f3812271a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

attribute: "Is a data element, as defined in RFC5209, that is atomic."

posture attributes: "Defined in RFC5209 as 'attributes describing the configuration or status (posture) of a feature of the endpoint. A Posture Attribute represents a single property of an observed state. For example, a Posture Attribute might describe the version of the operating system installed on the system.'"

Perhaps we simply make "posture attributes" singular, then define attribute as "see posture attribute"?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d4fa4ad968_c133ff760b20f3812271a-- From nobody Sun Dec 10 07:43:44 2017 Return-Path: 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 12E1B128954 for ; Sun, 10 Dec 2017 07:43:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 j0cxEYFDFvhe for ; Sun, 10 Dec 2017 07:43:41 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 534AC124D6C for ; Sun, 10 Dec 2017 07:43:41 -0800 (PST) Date: Sun, 10 Dec 2017 07:43:40 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512920620; bh=6Xsf1MNSeTZzl74XFUW8VLyWo1asHU7Z2wjI5f2TuYs=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=k0TDYuY50MGhBcSVIloj3uPig5zxMaUpi3OBsBP0XS9FgvvEkSI0LkW5Qdao6c7I3 vn1+1YYb/3usjJbQWFGSaXyq04eCWvkVnkm2pqGqJpfkTGauKzQR/NiBlPX4lGvGcw k2Dn3V/+dk6ECUSD65QtV7FoUZOWdPriwO81KaTk= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d562c7898f_27e33fd8d89caf2c1540b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposal to remove the input/output details from definitions (#68) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:43:43 -0000 ----==_mimepart_5a2d562c7898f_27e33fd8d89caf2c1540b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Several of our terms, such as *SACM Component Discovery* include some indication of what input and output they would expect. Such information seems very much out of place in a terminology definition. Are input/output items pertinent to the definition of a term? -- 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-terminology/issues/68 ----==_mimepart_5a2d562c7898f_27e33fd8d89caf2c1540b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Several of our terms, such as SACM Component Discovery include some indication of what input and output they would expect. Such information seems very much out of place in a terminology definition.

Are input/output items pertinent to the definition of a term?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d562c7898f_27e33fd8d89caf2c1540b5-- From nobody Sun Dec 10 07:46:11 2017 Return-Path: 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 4F6BC124D6C for ; Sun, 10 Dec 2017 07:46:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, 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 VDHPs2eDhgrE for ; Sun, 10 Dec 2017 07:46:03 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16CD71289B0 for ; Sun, 10 Dec 2017 07:46:03 -0800 (PST) Date: Sun, 10 Dec 2017 07:46:02 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512920762; bh=9koU8eQ7Dhkr4GLPQOlx/DMUd8HS6kWrtf8aQEerT0k=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=nj0Obd0B/VhFdfJoM6BUPiYOBEhy/1pLjMgwt+5lpXymRPs6e3jwQqGMd3fXasqgf lZt060O/MV8kLYOr89PTyY9Z9J8Zmkcb1zVtfWSDhvx1BNl40gNgh61v8jUYqysA8Y PkTwn4OaD/u3aqaQQmjYMf/wzf3vgO4F3GdQMHU0= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d56ba674c2_27d73fd8d89caf2c1846c0"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Improve the definition of SACM Component Discovery (#69) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:46:09 -0000 ----==_mimepart_5a2d56ba674c2_27d73fd8d89caf2c1846c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit SACM Component Discovery: "The task of brokering appropriate SACM components according to their capabilities or roles on request." The definition doesn't seem to match the term. I would expect, instead, to see something like: "the action or process of discovering SACM Components within a SACM Domain." -- 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-terminology/issues/69 ----==_mimepart_5a2d56ba674c2_27d73fd8d89caf2c1846c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

SACM Component Discovery: "The task of brokering appropriate SACM components according to their capabilities or roles on request."

The definition doesn't seem to match the term. I would expect, instead, to see something like: "the action or process of discovering SACM Components within a SACM Domain."

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d56ba674c2_27d73fd8d89caf2c1846c0-- From nobody Sun Dec 10 07:48:00 2017 Return-Path: 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 120921289B5 for ; Sun, 10 Dec 2017 07:48:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 5tJYzV_p6rOW for ; Sun, 10 Dec 2017 07:47:58 -0800 (PST) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 8C6AB124D6C for ; Sun, 10 Dec 2017 07:47:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zThNmcJbEZ+a1aeR9VVy1+LDjU4=; b=NjJ/SnX/myc+nMRZ nyBUrLngpv/s5EEjOpPpTW5Xhjq1SOr9mcTLa4iDhofPMgm6wHNfvrh5naHZ8XN3 MiAJcjHxjIuGUFaEKjNZeSxR89vDIjWcrUn31ldPmpIwQGD9rFT21W91cTuVMNxl sgY2J17t/hoUWOjLIP5Heb7UDQI= Received: by filter0633p1las1.sendgrid.net with SMTP id filter0633p1las1-14228-5A2D572D-C 2017-12-10 15:47:57.310396355 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0020p1iad2.sendgrid.net (SG) with ESMTP id 9qGjgsxvRfyFDmZ79kOfgQ for ; Sun, 10 Dec 2017 15:47:57.362 +0000 (UTC) Date: Sun, 10 Dec 2017 15:47:57 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d572d17192_a983f910982af3048853e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9Hz7XUI7gQ7gNY3Ggu9CMG9U6tQ9qBRmVqYVfbvxz3jkMfGSGcn0i0d88TF qJfZeAGmjdBPK73WQR74B6okJEBZlHV1dzv3y14rQxaemsR59eL6QhgeRo1VkGPnxop+/E9SZYAZPU hWpoP5U0eByP92mxRdFNrWe7NsOBh40WTwo6mY25eFQdsYXe3jdzip2Jng== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Can't use software package to define software package (#70) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:48:00 -0000 ----==_mimepart_5a2d572d17192_a983f910982af3048853e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit At present, we define *software package* as "a generic software package", which is unsatisfactory. Wikipedia has this: "...in which individual files or resources are packed together as a software collection that provides certain functionality as part of a larger system." That is much better than what we have. See: https://en.wikipedia.org/wiki/Software_package -- 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-terminology/issues/70 ----==_mimepart_5a2d572d17192_a983f910982af3048853e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

At present, we define software package as "a generic software package", which is unsatisfactory. Wikipedia has this: "...in which individual files or resources are packed together as a software collection that provides certain functionality as part of a larger system." That is much better than what we have.

See: https://en.wikipedia.org/wiki/Software_package

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d572d17192_a983f910982af3048853e-- From nobody Sun Dec 10 07:50:54 2017 Return-Path: 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 51C6112702E for ; Sun, 10 Dec 2017 07:50:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 nvTPYOWHJdiB for ; Sun, 10 Dec 2017 07:50:50 -0800 (PST) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 E17F8124D6C for ; Sun, 10 Dec 2017 07:50:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Xbjfq4ebmiydOlGq9ur5sTlhfHA=; b=PqSSOCQiqc9yQP96 HB4gZVx+aiNp9Gf3TIcVWomR5FSr82RxD0GR1Kar3/3hjQdZp23bGqd28bWHtP6u Cna+SU0Sjeh0uCbC+gD1HDSsDGiT9/smhWQ+YwgHChBnLcdgG4IGvzCoMg22NvU2 a7lWFAMisiZzT0AmuPvDJA3Nuow= Received: by filter0299p1las1.sendgrid.net with SMTP id filter0299p1las1-4028-5A2D57D7-6 2017-12-10 15:50:47.156073143 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id qniMvYZ5SUy3rMPFr8iOQA for ; Sun, 10 Dec 2017 15:50:47.115 +0000 (UTC) Date: Sun, 10 Dec 2017 15:50:47 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d57d7164e_6c2f3fcab06bcf285542e6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H8gCIRJQFjv0SMTVT9zvGc8el0mbQKO6jFs/2oWBT5y+72nckOTbMYDaPr HV2XHXxmRVIdk23wwnO6HANm/L8eqnDy93I9QsPUbLTUNH0y1NQvcMaIsFt01nMHNzoyy4IcazuD4j Sxp3xC0Nlar92SuAOdTgnW+/sdW5CgO+BkhWB+clA2BT/FigYujFQpReWQ== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] We need to revisit Software Component and possibly Software Instance (#71) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:50:51 -0000 ----==_mimepart_5a2d57d7164e_6c2f3fcab06bcf285542e6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I'm not really happy with our definition for *Software Component*. To me, a software component may be part of a specific package, not an installed package. For example, the Atom text editor may have a "file viewer" component. This definition is more like the intent behind SACM Component. Does this really mean to say "software application"? That may solve a lot. If we update this to say software application, then we'll need to additionally update *Software Instance* to be defined as "a running instance of a software application." -- 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-terminology/issues/71 ----==_mimepart_5a2d57d7164e_6c2f3fcab06bcf285542e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I'm not really happy with our definition for Software Component. To me, a software component may be part of a specific package, not an installed package. For example, the Atom text editor may have a "file viewer" component. This definition is more like the intent behind SACM Component. Does this really mean to say "software application"? That may solve a lot.

If we update this to say software application, then we'll need to additionally update Software Instance to be defined as "a running instance of a software application."

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d57d7164e_6c2f3fcab06bcf285542e6-- From nobody Sun Dec 10 07:53:16 2017 Return-Path: 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 B5E5012702E for ; Sun, 10 Dec 2017 07:53:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 miUeaAN1JiVv for ; Sun, 10 Dec 2017 07:53:13 -0800 (PST) Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 32C96124D6C for ; Sun, 10 Dec 2017 07:53:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=wLM4Oq0ThQZH2suthsCWcLtc+uw=; b=phOsJSktNvg/ftvh y8YP4IRijgpXUOHxLWFyi5AlFvYlx/06tm8bnV4dqfW6gUET7DAP7Ma6REV6kDQZ tFQvxLN8NhQZbfaN7pQ0oO+u9biFFRm25T4XXP0IfEFrYTkO0qgewG35pGTMpgkL VbLVaMCIxshRuLB9hnykNnSaeX4= Received: by filter0356p1las1.sendgrid.net with SMTP id filter0356p1las1-9486-5A2D5864-B 2017-12-10 15:53:08.354426599 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id oAENZTfhQl6JR7njYdak_Q for ; Sun, 10 Dec 2017 15:53:08.098 +0000 (UTC) Date: Sun, 10 Dec 2017 15:53:08 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d5863f26d3_69903fd9ffcb8f2c297447"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/MVrTBMZEit78Jypul0s0Ao19xkZwgnGgFZz7WZiWwNIF/hFXnjyMJGYT CQxIWBlDXddDY6nnDNI0V8bjn1rG4SF73k5KY3ldpLHUYyHTXt5xdlN4lFS9/7kgUeXoRl9sXCQBPH dN/AOs1bGIYPZKTeNPCtO6gpIbUZr2OdjpcHZc39vpNO2pJGjhn0uBRfoA== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove (or redefine) Statement (#72) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:53:15 -0000 ----==_mimepart_5a2d5863f26d3_69903fd9ffcb8f2c297447 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have defined *Statement* as "a subject defined in the SACM information model." This feels too generic a term to be so specifically defined. In other words, the definition read alone would lead one to the term "SACM Subject" or something like that. Additionally, this term is also set up to be synonymous with *Subject*, which is defined elsewhere in this draft. -- 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-terminology/issues/72 ----==_mimepart_5a2d5863f26d3_69903fd9ffcb8f2c297447 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have defined Statement as "a subject defined in the SACM information model."

This feels too generic a term to be so specifically defined. In other words, the definition read alone would lead one to the term "SACM Subject" or something like that. Additionally, this term is also set up to be synonymous with Subject, which is defined elsewhere in this draft.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d5863f26d3_69903fd9ffcb8f2c297447-- From nobody Sun Dec 10 07:53:49 2017 Return-Path: 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 A52ED124D6C for ; Sun, 10 Dec 2017 07:53:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 u74bnB9j-No4 for ; Sun, 10 Dec 2017 07:53:47 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 36EC312702E for ; Sun, 10 Dec 2017 07:53:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=T+5mtl3uCJCfJ80pU14BPgggOso=; b=Zy0MfP7VmvdM4A8X KHTFZTgn0iZ9H2zNrZf7jl2CgI459SNQL1+PfR1coqzsaA1IKWEaPwd8/d842+xc SSkqf/HteroKz8hUp0Uk1MnoTffijVYX9eEYh1K8cioeQ+VyCAUt05swdUTNKEqV sgoLhkWJBMcyehiQTlwPPJl9Jeo= Received: by filter0080p1las1.sendgrid.net with SMTP id filter0080p1las1-23262-5A2D588A-1 2017-12-10 15:53:46.101351849 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0015p1iad2.sendgrid.net (SG) with ESMTP id GLhoxALpTSKzSFNvFReARg for ; Sun, 10 Dec 2017 15:53:45.961 +0000 (UTC) Date: Sun, 10 Dec 2017 15:53:46 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d5889de48e_1ef43fba41810f34232911"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1ad/u2TIJNtS8GEJFqaGAHGI5A+52RKzVPGLlsoU1FrVfv/1QOMMDuQDl SVWu0c3Co1PoMX9h+4pXbSteCYGAA/zVc7BC37F6zyyiPPWa5UnWTP9KjF7ugm3MdOs66ZmA2mxLCb wl+Q66hhLVOpye7GWk+zgFH4wCQguxA4mDr9flvLoBvRiCFURjntjoXUYw== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Supplicant (#73) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:53:49 -0000 ----==_mimepart_5a2d5889de48e_1ef43fba41810f34232911 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Supplicant seems like a commonly understood term, should we really define it in SACM terms here? -- 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-terminology/issues/73 ----==_mimepart_5a2d5889de48e_1ef43fba41810f34232911 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Supplicant seems like a commonly understood term, should we really define it in SACM terms here?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d5889de48e_1ef43fba41810f34232911-- From nobody Sun Dec 10 07:55:05 2017 Return-Path: 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 8C562124D6C for ; Sun, 10 Dec 2017 07:55:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 DmRl9rEgq1Xc for ; Sun, 10 Dec 2017 07:55:01 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 24BD012702E for ; Sun, 10 Dec 2017 07:55:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jD4s+m0Jr/1RNRqJ1ZdqK83Rzhw=; b=ZN22ExSQxgEpr5zb qI7pi1UO4Rv2T/OXn//V6MiLeejahGzuwewz38uoIGxOPfP+kjrZK6WtU6Bvgm+u 12iBwyJwqsHyknVxrLj/4tQt1l+divcxGiMtEGTWlNpxNBdFeYDiMxDbdkpeOD/L O9l3eG0T2ww/kuhoRctAPe2oUjY= Received: by filter0189p1las1.sendgrid.net with SMTP id filter0189p1las1-9891-5A2D58D3-31 2017-12-10 15:54:59.573726974 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id OxXXzN-LSoeaYr6vWqbv2Q for ; Sun, 10 Dec 2017 15:54:59.493 +0000 (UTC) Date: Sun, 10 Dec 2017 15:54:59 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d58d363dda_1f553f80dcbbef30193147"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H45woNWSkZwb6bWf2UEkeIg8JQ3sxeZedT9RmHWICvPyOfXWJIlOyarewa ke/HxSTtAjlLGV13jVKSJLOzBAla7eQ4opxcBuL4TvGY2+kvrbM16a1n4VRnJBOgJKYwR4quY6Z5sM kIJxZM0T7A2P8DxTxOKmOOKifqo6eQvSpGT8afWRbHb75wXYGygdo+vPeg== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization (#74) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:55:03 -0000 ----==_mimepart_5a2d58d363dda_1f553f80dcbbef30193147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have already talked about "Endpoint Characterization" and "Target Endpoint" is it really necessary to define the combination of the two? Or, does this jive with that? -- 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-terminology/issues/74 ----==_mimepart_5a2d58d363dda_1f553f80dcbbef30193147 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have already talked about "Endpoint Characterization" and "Target Endpoint" is it really necessary to define the combination of the two? Or, does this jive with that?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d58d363dda_1f553f80dcbbef30193147-- From nobody Sun Dec 10 07:55:35 2017 Return-Path: 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 1F1D9128ACA for ; Sun, 10 Dec 2017 07:55:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 eWDCwv2BXGmS for ; Sun, 10 Dec 2017 07:55:32 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 96629124D6C for ; Sun, 10 Dec 2017 07:55:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=VdIQAznmzXViqGWjiNR32Isp2K8=; b=AIw9Yw/9Jo7WT+QQ LGD8E08SMyPZIU0cslQ++C9rwDo2GCuMPxVx2EIuWt+hmYbu73LMQ7qARVgjMAy1 eFjMMp6fjr1LXTist0x9PUnbDxQIaKmr1s415isK190xY3IkJzyFwFmSIDqQrRli 2OZBQodZ7/7CcGqtwrDhK14za2E= Received: by filter0135p1las1.sendgrid.net with SMTP id filter0135p1las1-16964-5A2D58F3-10 2017-12-10 15:55:31.330532892 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0014p1iad2.sendgrid.net (SG) with ESMTP id 8prAJAcNR7O9jeDvIpAROg for ; Sun, 10 Dec 2017 15:55:31.248 +0000 (UTC) Date: Sun, 10 Dec 2017 15:55:31 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d58f329685_27b53fd8d89caf2c4585fc"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H2/wL8Bw3jPjT0hekytArJwDcwEpRuLEd2p3ZRWBQEGX7oTw6xWpSYQPyq p55JfMZY64L4Dz1uD5gYy5wFnD7DSAIhE7r36jmV3GG0XGM5Fx5iJoOGrRsvzi0bTTWRpcJQ0IMhiy eIUivMXdE4pJ9hlrOcGS8C05Ew1fXjsvrhnskZyaRikMIg3i1PXji/UYYQ== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization Task (#75) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:55:34 -0000 ----==_mimepart_5a2d58f329685_27b53fd8d89caf2c4585fc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have already talked about "Endpoint Characterization Task" and "Target Endpoint" is it really necessary to define the combination of the two? -- 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-terminology/issues/75 ----==_mimepart_5a2d58f329685_27b53fd8d89caf2c4585fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have already talked about "Endpoint Characterization Task" and "Target Endpoint" is it really necessary to define the combination of the two?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d58f329685_27b53fd8d89caf2c4585fc-- From nobody Sun Dec 10 07:56:03 2017 Return-Path: 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 6E611124D6C for ; Sun, 10 Dec 2017 07:56:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.954 X-Spam-Level: X-Spam-Status: No, score=-4.954 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 C-EGvtZyA95k for ; Sun, 10 Dec 2017 07:55:59 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [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 B6EA31288B8 for ; Sun, 10 Dec 2017 07:55:59 -0800 (PST) Date: Sun, 10 Dec 2017 07:55:59 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512921359; bh=2XlhOXH+gHBJ7KMicktRDx7b7TUKDYc0zEoOU6Z7E9g=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=McTxyXflOB5TkNaYWPufO3TsCD1Tx/H05NB7t4GLGSdKwhTw/gdgACisFglTWzOW+ 9ItOUbckawfoIJm5/NFBT2hAJA/ckLiRxWhmDDv2+6pcyJ+Pdrry9LQtObqw9191Lq 1icH5vIGQ8hIncKXMDY9lLrfcRsyFGcjZx0fc49c= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d590f16d7c_c423ff760b20f3830479c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Classification Task (#76) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:56:01 -0000 ----==_mimepart_5a2d590f16d7c_c423ff760b20f3830479c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have already talked about "Endpoint Classification Task" and "Target Endpoint" is it really necessary to define the combination of the two? -- 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-terminology/issues/76 ----==_mimepart_5a2d590f16d7c_c423ff760b20f3830479c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have already talked about "Endpoint Classification Task" and "Target Endpoint" is it really necessary to define the combination of the two?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d590f16d7c_c423ff760b20f3830479c-- From nobody Sun Dec 10 07:56:30 2017 Return-Path: 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 18CAC124D6C for ; Sun, 10 Dec 2017 07:56:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, 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 P7IkyZhkZ2cd for ; Sun, 10 Dec 2017 07:56:27 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 768771288B8 for ; Sun, 10 Dec 2017 07:56:27 -0800 (PST) Date: Sun, 10 Dec 2017 07:56:26 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512921386; bh=wAg1qw9o+CFOiAAi/9t6dJ61nbiOD4IGpNTG9CZysYs=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=wn7ogZvGNfSjyaskoYXPj6Sj9D4egKoD5pl3dfiKjetIxzosDejVXKDCH4yN2KCOC Lk8md3bt2082MyCXAnUeKA4TVjCoNkmVK/IUcbToxAGV35nt+hQD4XO2uA4U7Zu5/0 jr/WcGOJMxskuXk7hsOxlrLpWsImbq2Er03BnezM= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d592aced04_c1c3ff760b20f383466cf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Discovery Task (#77) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:56:29 -0000 ----==_mimepart_5a2d592aced04_c1c3ff760b20f383466cf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have already talked about "Endpoint Discovery Task" and "Target Endpoint" is it really necessary to define the combination of the two? -- 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-terminology/issues/77 ----==_mimepart_5a2d592aced04_c1c3ff760b20f383466cf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have already talked about "Endpoint Discovery Task" and "Target Endpoint" is it really necessary to define the combination of the two?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d592aced04_c1c3ff760b20f383466cf-- From nobody Sun Dec 10 07:57:40 2017 Return-Path: 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 AB25312702E for ; Sun, 10 Dec 2017 07:57:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, 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 s2VwvpMefOnb for ; Sun, 10 Dec 2017 07:57:38 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [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 04AD7124D6C for ; Sun, 10 Dec 2017 07:57:38 -0800 (PST) Date: Sun, 10 Dec 2017 07:57:37 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512921457; bh=d+JQbg5exA5wygk1OGeCQQxFv6bFTPkT7cG7d5nwIDc=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=APjg7W6boipZ25+7ABSIGHXBVjDxKF0t+cmUnoFOpWtZ9QBmY0GnYo4VfcUzFssNb Czj2ikB0JkeuCCPS4cIAP58aYPn755UYPqRzmZqlaHkfzbZeOqqYlJXb0j8+l6mqUr 8jlnheSpguAmnPJuQ2gAyVCgohtq2Hu4Q/0UR+9A= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d59715e6f3_67283fcb19c02f2839761e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Relabel Target Endpoint Identifier to Endpoint Identifier (#78) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:57:39 -0000 ----==_mimepart_5a2d59715e6f3_67283fcb19c02f2839761e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It doesn't seem that a target endpoint identifier should be any different from the identifier for an endpoint that is not targeted. -- 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-terminology/issues/78 ----==_mimepart_5a2d59715e6f3_67283fcb19c02f2839761e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

It doesn't seem that a target endpoint identifier should be any different from the identifier for an endpoint that is not targeted.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d59715e6f3_67283fcb19c02f2839761e-- From nobody Sun Dec 10 07:58:05 2017 Return-Path: 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 3EF13128B4E for ; Sun, 10 Dec 2017 07:58:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, 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 cCoOHHxtmI5R for ; Sun, 10 Dec 2017 07:58:01 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [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 9AC99124D6C for ; Sun, 10 Dec 2017 07:58:01 -0800 (PST) Date: Sun, 10 Dec 2017 07:58:00 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1512921480; bh=iq2Pi++ZcWeuqoy51F2JNq5OXlOLwku8ic2OTf+/sS0=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=bFRgoKPz6a8oAA/FHQXgZKlBbLfBBk+KbXhui7t2mcOMKRXVa8SaVRLZpUFDfqH7D xW9KTomm5+4N254OQiOQCnJmQsuMYsfxWcssI5iltSkzUt9p54qeliDww5cqssgHJN 9aIHm9NlvaWWCG6jgO1otZoc7e7JfZVgnHWr+XvQ= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d5988ecfec_69f13fd9ffcb8f2c2749f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Label (#79) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:58:03 -0000 ----==_mimepart_5a2d5988ecfec_69f13fd9ffcb8f2c2749f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We have already talked about "Endpoint Label" and "Target Endpoint" is it really necessary to define the combination of the two? -- 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-terminology/issues/79 ----==_mimepart_5a2d5988ecfec_69f13fd9ffcb8f2c2749f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

We have already talked about "Endpoint Label" and "Target Endpoint" is it really necessary to define the combination of the two?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d5988ecfec_69f13fd9ffcb8f2c2749f7-- From nobody Sun Dec 10 07:58:42 2017 Return-Path: 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 5B92612702E for ; Sun, 10 Dec 2017 07:58:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 KiWKVzeWHy8T for ; Sun, 10 Dec 2017 07:58:39 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 29FC8124D6C for ; Sun, 10 Dec 2017 07:58:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=hlrExt8OYQoX5fMEhpqopES7JpQ=; b=ovDQAenr9EkfeOxy Y58VK9+rFw+sCU7REya5twqzjAG68fvbxQ3iW9vd3BPj7HvZS/iHUh7DRXV0CNW3 wivdYOI5aKXWE0VJcs/nb6BGsXjDv2PyWuhKExavuOlTOBROo8pyIWy4Lp+uKE+f YAkbJKwk+mBi2pFX+ANGxvQ9l3M= Received: by filter0064p1las1.sendgrid.net with SMTP id filter0064p1las1-23997-5A2D59AD-39 2017-12-10 15:58:37.86842529 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id -aaO_Li3SO2OpY_ctZ37mQ for ; Sun, 10 Dec 2017 15:58:37.712 +0000 (UTC) Date: Sun, 10 Dec 2017 15:58:37 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d59ad98a6b_8353fb73d506f34395113"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H9jDTk3nqFsaQ6Kd3Ez6nBlKOZbPNzzGVAK6g4Xlx/VjWnulGn+Qy6arpP MyDjirFMbDNisRpH6mvX4t1I8H054NGwOXwoutXUr7rHbg0SsnrgTKroVIutNu3TtHiImYtDFBuRWE eeaLtVNCFvNdGz/w4Mmxw75aGlqZcKF6pjjLy1R4s4YLWTLL4pjqb3r9pg== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Do we really need to define timestamps? (#80) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 15:58:40 -0000 ----==_mimepart_5a2d59ad98a6b_8353fb73d506f34395113 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Do we need this term? Or should we talk about "data object timestamp" and "event timestamp" (and thus "network event timestamp")? -- 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-terminology/issues/80 ----==_mimepart_5a2d59ad98a6b_8353fb73d506f34395113 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Do we need this term? Or should we talk about "data object timestamp" and "event timestamp" (and thus "network event timestamp")?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d59ad98a6b_8353fb73d506f34395113-- From nobody Sun Dec 10 08:02:40 2017 Return-Path: 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 6613112702E for ; Sun, 10 Dec 2017 08:02:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.402 X-Spam-Level: X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 6y13V4klExaD for ; Sun, 10 Dec 2017 08:02:37 -0800 (PST) Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 1982C124D6C for ; Sun, 10 Dec 2017 08:02:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=c95fYSNWrDdncaT3jeM8tDsQA4I=; b=np1ANAy70N2EtlNY 5yhwqwasyIt+cbHdGgX/XS2tCGeYoLHvyNtYMWzpbXo0HxEkf1Zr08aro9+NBWJd q9rGCanX7x+fqe7IeCGmd3MqisSELH8PhJUg/8IIiscOjMSj+BAQI8v56VqnllzF FUWA4PSUica0N2BJAxeu6KYTxzQ= Received: by filter0853p1mdw1.sendgrid.net with SMTP id filter0853p1mdw1-29101-5A2D5A85-3B 2017-12-10 16:02:13.457015124 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id UVrgK-BESEmu2PNrbOAMAA for ; Sun, 10 Dec 2017 16:02:13.468 +0000 (UTC) Date: Sun, 10 Dec 2017 16:02:13 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d5a855ee4e_1f783f80dcbbef302371bf"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H+X4OGvXWV4QNxuJPJaxYdo5lCh0pLy7XPo5AljcQ52T4vSrNOWwhsElO1 r0kOFQon/9VyqtGeTKqf74IZs3x4E5YWVy71JANPqVaM59C8ttdmowypMDkcCafla8DXR8PBK8tbXu LnxGpPaj8X2eHxUun5Fdu8TaArJlPfr5xu8nbVnCFV8XvO/YsQS9Heh0XA== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Either remove or actually define Virtual Component (#81) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 16:02:38 -0000 ----==_mimepart_5a2d5a855ee4e_1f783f80dcbbef302371bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I feel like we should remove this term. Either that, or we need an actual definition, as what currently exists is a related, but non-definitional, statement: > A target endpoint can be composed entirely of logical system entities (see RFC4949). That is not a definition, but perhaps a characteristic of a target endpoint. -- 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-terminology/issues/81 ----==_mimepart_5a2d5a855ee4e_1f783f80dcbbef302371bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I feel like we should remove this term. Either that, or we need an actual definition, as what currently exists is a related, but non-definitional, statement:

A target endpoint can be composed entirely of logical system entities (see RFC4949).

That is not a definition, but perhaps a characteristic of a target endpoint.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d5a855ee4e_1f783f80dcbbef302371bf-- From nobody Sun Dec 10 08:06:50 2017 Return-Path: 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 829E1128B4E for ; Sun, 10 Dec 2017 08:06:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.616 X-Spam-Level: X-Spam-Status: No, score=-0.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 z7ONEyUcr3xc for ; Sun, 10 Dec 2017 08:06:47 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 271DB12702E for ; Sun, 10 Dec 2017 08:06:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=wvf3TCMnWHVmpMb0x7YEYNaMErE=; b=IhJpa1uHGxkCBW0W UkLdmnTwXyxUOTnG9qgZxktBtk2SR0ad+8ZmmBcQ60OjPJEsfSeQCQyObJ7d9VET VOsLVhidvrpjy/+FjLUuOvGiW7CaM/bSyuVUsyI6eUuO2sl0c1XLpMBSVK1aZRqR UdXoam8Dv0BP/4GS6OfVJnEEkSA= Received: by filter0051p1las1.sendgrid.net with SMTP id filter0051p1las1-24092-5A2D5B94-38 2017-12-10 16:06:44.494974261 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad2.sendgrid.net (SG) with ESMTP id czlrtU5xRpeKHa8KcnJHsA for ; Sun, 10 Dec 2017 16:06:44.416 +0000 (UTC) Date: Sun, 10 Dec 2017 16:06:44 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a2d5b9437c9a_1a87d3ffaf373cf3414773b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H5rtKsff/A/VH18evFXNKZKM1SMzhHrV9QYKoK/0GkYeMFV8B9OFwm0w03 Aq5gmGqIAZtpKr+UnTkBUEhSZanwqpXYyNUcj/SaiZXRqcuBIJf+roSzH/LifJA+/pYeXsY17k//bk 12HnNGXUZHDw1ROYbrUbLsUSJAtXLQ5u5jU0zqC6xGvLaZADLLx01B4cdA== Archived-At: Subject: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 16:06:48 -0000 ----==_mimepart_5a2d5b9437c9a_1a87d3ffaf373cf3414773b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The present definition is: > The process of which security alerts can be automated through the use of different components to monitor, analyze and assess endpoints and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats. I propose (changes emphasized): > The process *by* which security *programs* can be automated through the use of different components to monitor, analyze and assess endpoints and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats. -- 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-terminology/issues/82 ----==_mimepart_5a2d5b9437c9a_1a87d3ffaf373cf3414773b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

The present definition is:

The process of which security alerts can be automated through the use of different components to monitor, analyze and assess endpoints and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats.

I propose (changes emphasized):

The process by which security programs can be automated through the use of different components to monitor, analyze and assess endpoints and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a2d5b9437c9a_1a87d3ffaf373cf3414773b-- From nobody Sun Dec 10 08:22:02 2017 Return-Path: X-Original-To: sacm@ietf.org Delivered-To: sacm@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0749C124D6C; Sun, 10 Dec 2017 08:21:57 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sacm@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.67.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151292291698.22040.12722024233472359806@ietfa.amsl.com> Date: Sun, 10 Dec 2017 08:21:57 -0800 Archived-At: Subject: [sacm] I-D Action: draft-ietf-sacm-terminology-14.txt X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 16:21:57 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Automation and Continuous Monitoring WG of the IETF. Title : Security Automation and Continuous Monitoring (SACM) Terminology Authors : Henk Birkholz Jarrett Lu John Strassner Nancy Cam-Winget Adam Montville Filename : draft-ietf-sacm-terminology-14.txt Pages : 28 Date : 2017-12-10 Abstract: This memo documents terminology used in the documents produced by SACM (Security Automation and Continuous Monitoring). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sacm-terminology/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sacm-terminology-14 https://datatracker.ietf.org/doc/html/draft-ietf-sacm-terminology-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sacm-terminology-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Dec 12 17:59:52 2017 Return-Path: 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 A30C0128C82 for ; Tue, 12 Dec 2017 17:59:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, 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 MdQ6kh_BHE5T for ; Tue, 12 Dec 2017 17:59:49 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [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 EBEA3128C81 for ; Tue, 12 Dec 2017 17:59:48 -0800 (PST) Date: Tue, 12 Dec 2017 17:59:48 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513130388; bh=OSYgl0P5DADljNeL/kmZ7iFNd88q6dKw1RvKB2MKK+4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VjFdGxm+q8t6ExKtgccnrIG4d9IHcuCq0n3aZhuOSdttpjrvm++zDEC3hnu9XbDnF BUrS19BOnNdXk64xm0/3uDK6eOxdVJI9loz9lABNH/oEM6YKfRSDqZ8HjoqeAHID2P z/85ROi6qXnOrIZ4MRno31+C67FQyyPpdCZIfOZg= From: David Somers-Harris Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a30899422a64_35f63f9c20292f3877273"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: davidkazuhiro X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 01:59:50 -0000 ----==_mimepart_5a30899422a64_35f63f9c20292f3877273 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit What does "security program" mean? -- 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-terminology/issues/82#issuecomment-351257376 ----==_mimepart_5a30899422a64_35f63f9c20292f3877273 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

What does "security program" mean?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a30899422a64_35f63f9c20292f3877273-- From nobody Wed Dec 13 04:58:46 2017 Return-Path: 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 BD132124319 for ; Wed, 13 Dec 2017 04:58:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 p3ZMSaS_K_x4 for ; Wed, 13 Dec 2017 04:58:43 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 D6A821201F2 for ; Wed, 13 Dec 2017 04:58:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=umWphc/tETwY56b6yQ9+B+ivjcQ=; b=IlAEi4/uMoiAYs4N WBHnJnVxTkc2iyQytNtKHqiw9mS7J5NGl+MKP0qJ5QttPsqfHqE6HMBDH1Ydcdr0 QybAJsj7kcfOWDNKxPpNw94B10KYu+WP/xcuVRsT2/6nBq9vOpCC6xK/GPb362tn 1oCEKlXdJUM9RsSESGGib9dUrR4= Received: by filter0122p1las1.sendgrid.net with SMTP id filter0122p1las1-17197-5A312401-2E 2017-12-13 12:58:41.901525657 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0022p1iad2.sendgrid.net (SG) with ESMTP id GPHPcu3WQvyBOUgV-7LLOg for ; Wed, 13 Dec 2017 12:58:41.692 +0000 (UTC) Date: Wed, 13 Dec 2017 12:58:42 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a31240199414_45c93f8d4e14ef2c392998"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1ad/u2TIJNtS8GEJFqaGAHIRcA1T8ha2w3kbCuCWGsgNStgsjI+9Qx8Ty GFagPZ7Tk/ycqh8zfKh95/jLdb6/xH+LSUHWPK7YBMzEmTccKbcNjS57ybHqE7XWHbOjn2KB+2Bb/5 XiZLpnACFZYj0zolrgj9x/StdoE8M9wa6MhDPDkoyyDufj3xokBs3lX44g== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 12:58:45 -0000 ----==_mimepart_5a31240199414_45c93f8d4e14ef2c392998 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That's a fair question. In trying to find a standard definition for "security program", I realized that I should probably have said "information security program" which seems to have some fairly well-understood boundaries (see [these Google search results](https://www.google.com/search?ei=iiMxWriaGOWT_Qbf4ZWgBA&q=define%3A%22information+security+program%22&oq=define%3A%22information+security+program%22&gs_l=psy-ab.3...6158.8721.0.9011.18.14.2.0.0.0.130.1151.10j4.14.0....0...1c.1.64.psy-ab..7.0.0....0.qWAP7z_gH-E)). If you, or someone else, has a better way to describe this, please let me know. -- 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-terminology/issues/82#issuecomment-351383905 ----==_mimepart_5a31240199414_45c93f8d4e14ef2c392998 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

That's a fair question. In trying to find a standard definition for "sec= urity program", I realized that I should probably have said "information se= curity program" which seems to have some fairly well-understood boundaries = (see these Google search results).

If you, or someone else, has a better way to describe this, please let m= e know.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a31240199414_45c93f8d4e14ef2c392998-- From nobody Wed Dec 13 19:43:32 2017 Return-Path: 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 3F1991270A0 for ; Wed, 13 Dec 2017 19:43:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 NNDlHqBDY_-n for ; Wed, 13 Dec 2017 19:43:29 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 6DF06126C22 for ; Wed, 13 Dec 2017 19:43:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=ErCCaCbVEmq3FryQlOBL9vQS3T8=; b=eH9na76Acg1d21Js 5kNbHOF3UijWXswIOJUykdBo63/vCj+K8ozIpy52SzlY5D9tBIxaqmyYnXkYOPgg ELYfHea2E+hiDXXZmUNX6RcDgsKUMgsUVnHEbqpLVA31td2GqX4l4G56r143usI7 DrytTN5KXjh1Dg1kuzcGKECBGEI= Received: by filter0169p1iad2.sendgrid.net with SMTP id filter0169p1iad2-24210-5A31F35F-D 2017-12-14 03:43:27.257957739 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0019p1iad2.sendgrid.net (SG) with ESMTP id YhLUU4qGQ8qwmAqFadfXEw for ; Thu, 14 Dec 2017 03:43:27.301 +0000 (UTC) Date: Thu, 14 Dec 2017 03:43:27 +0000 (UTC) From: David Somers-Harris Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a31f35f2e161_109d3fde69fa2f304807a7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: davidkazuhiro X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxPHXuAUy9XW3sQPQJs30zBNS93KZys2b5aaup4Pp4vG4CxfuFS13Mu0ps 4gAkXLvehBdDLmIjGhIVqMomzAvQGW3fBHA9oVLRIqxquKRwVUfN5AqjYpIK3UsjkvpjQdm/3mm569 fUZq+pNXK2QuExuak/lB2uOmzdvfTv4DYpYn2u7VGwhXJ1YrFB6Vay3oPBZH60eZDoHAtmTd+Qu32j o= Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 03:43:31 -0000 ----==_mimepart_5a31f35f2e161_109d3fde69fa2f304807a7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ah OK I think I was confused by the definition of program. I thought you meant > a series of coded software instructions to control the operation of a computer or other machine. But apparently you meant > a set of related measures or activities with a particular long-term aim. But yes, Information Security is more specific than security. In any case, I think usage of such a term would require a new entry in the terminology section. -- 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-terminology/issues/82#issuecomment-351600085 ----==_mimepart_5a31f35f2e161_109d3fde69fa2f304807a7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ah OK I think I was confused by the definition of program. I thought you= meant

a series of coded software instructions to control the operation of a co= mputer or other machine.

But apparently you meant

a set of related measures or activities with a particular long-term aim.=

But yes, Information Security is more specific than security.

In any case, I think usage of such a term would require a new entry in t= he terminology section.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a31f35f2e161_109d3fde69fa2f304807a7-- From nobody Thu Dec 14 03:48:27 2017 Return-Path: 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 5C921128B88 for ; Thu, 14 Dec 2017 03:48:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.615 X-Spam-Level: X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 zdp7Enw5dGDZ for ; Thu, 14 Dec 2017 03:48:24 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 ABFEB128959 for ; Thu, 14 Dec 2017 03:48:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=O5lGJzjNtX7nSwuOtvYR+MVMfzo=; b=nHvdzk0is5Iw4sAO CaboyTFgMlGqjUgu5y1usHi64Zepy//WLJ9YFVG2zYv35QV0fOdGzpBBjWBD34nd BV4ysMtRUs8QwDYsTO33q9qI86wBGLMhqEKJk3U1r6EvTwkprgDZIvTsF/TAn1cL 5OfaAXeeDwYdEKEdBE/Ta94fUS8= Received: by filter0494p1las1.sendgrid.net with SMTP id filter0494p1las1-17801-5A326507-2 2017-12-14 11:48:23.120456951 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id 6xyq97N1R1-AprH_b1bdRw for ; Thu, 14 Dec 2017 11:48:22.989 +0000 (UTC) Date: Thu, 14 Dec 2017 11:48:23 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a326506ddb53_111e3fdb0f6cef3897047d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1ho66ZyBF36mrKB3ybK4MU+Q3a/fj9/ILLLgf0c8b++mC7gLwBZssxPr6 1sYee/BA1xwqxOYvfVpzAI+2zxcmQSlvLUZS9Zf4yz6g/5Ij9ZpRFzceyemXSInsaL23VCFW4Eeqfw ar3hcDbe5UgJ4nSms8PLDU8/+DwAEK+z6/ppD4FNC3ytQ90Vf2/z0JM8iA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 11:48:26 -0000 ----==_mimepart_5a326506ddb53_111e3fdb0f6cef3897047d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit We could add another term. How about this definition for _information security program_: > A documented approach for organizing and directing all activities undertaken to ensure the confidentiality, integrity, and availability of the information held by the organization. That's taken from ISO 704:2009. -- 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-terminology/issues/82#issuecomment-351689150 ----==_mimepart_5a326506ddb53_111e3fdb0f6cef3897047d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

We could add another term. How about this definition for information= security program:

A documented approach for organizing and directing all activities undert= aken to ensure the confidentiality, integrity, and availability of the info= rmation held by the organization.

That's taken from ISO 704:2009.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a326506ddb53_111e3fdb0f6cef3897047d-- From nobody Thu Dec 14 04:45:18 2017 Return-Path: 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 E4E19128D86 for ; Thu, 14 Dec 2017 04:45:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 OKwpY9qYGEfl for ; Thu, 14 Dec 2017 04:45:15 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 8DD29128D64 for ; Thu, 14 Dec 2017 04:45:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=M20vRYS1EjnEy83DLYNk0TCLr3I=; b=J6OWds1nddAxGyLx GHLK6XsT69duVB6fAp10HtzLOTuiimlj/j36zfVCucRra4XmJFVMqKoNZQEik4IW 3/F6IzMW7zYdr9q4IRoOQNnmIab69lo9Rbb5rgnoK6pMXtQ0+fnPh/YxT8gIitQI FebOayoauqvy9t60l2IOXIi0990= Received: by filter0491p1iad2.sendgrid.net with SMTP id filter0491p1iad2-21236-5A32725A-11 2017-12-14 12:45:14.279487459 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id uRlN8ShGTpCDeLhJ6JwEFQ for ; Thu, 14 Dec 2017 12:45:14.140 +0000 (UTC) Date: Thu, 14 Dec 2017 12:45:14 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32725aa34c_1e163fec97332f34228862"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxgcHB4isg96i/RTqc0yBuAH10jgZwA0aGBmJpgnqXbg/6jnU7O10RmteE DrAcXDrC5iW9lcuc4G+PgKunc/2vLF04Opr5FlmJ6BnDHlvBYXDpu6lNbla0nJuWqPUS2sBQn3Evcv 1hU6+V9nUZCBZ3V9fRz8mQvNsfdEDI73drSitc5kVg48hQMuN0266Mj/awp+Qg6og4bZUMY01CK2N0 8= Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "asset" to "SACM asset"? (#61) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 12:45:18 -0000 ----==_mimepart_5a32725aa34c_1e163fec97332f34228862 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I am not really sure why the term asset is still used. We do "security posture assessment of target endpoints". Of course, from an org pov, everything that supports a primary or secondary business process is an asset - and then some. Therefore most entities (such as components, functions and or even planes) count as assets. SAM is a thing that makes use of SWID, so I see a specific relationship there also. But effectively, Asset is a catch all phrase with little meaning to SACM, in general. It is still in because it doesn't hurt to see how SACM relates the term (which we do by the included examples), I think. It is not required to be in the terminology document. It helps if it is in there more than it hurts when it is not there, I think. I am more on the neutral side. Slightly in favor of removing it entirely rather than word-smithing its definition away from 4949. -- 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-terminology/issues/61#issuecomment-351701073 ----==_mimepart_5a32725aa34c_1e163fec97332f34228862 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I am not really sure why the term asset is still used. We do "security p= osture assessment of target endpoints". Of course, from an org pov, everyth= ing that supports a primary or secondary business process is an asset - and= then some. Therefore most entities (such as components, functions and or e= ven planes) count as assets. SAM is a thing that makes use of SWID, so I se= e a specific relationship there also. But effectively, Asset is a catch all= phrase with little meaning to SACM, in general.

It is still in because it doesn't hurt to see how SACM relates the term = (which we do by the included examples), I think. It is not required to be i= n the terminology document. It helps if it is in there more than it hurts w= hen it is not there, I think.

I am more on the neutral side. Slightly in favor of removing it entirely= rather than word-smithing its definition away from 4949.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32725aa34c_1e163fec97332f34228862-- From nobody Thu Dec 14 04:53:03 2017 Return-Path: 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 BAD4A128DF3 for ; Thu, 14 Dec 2017 04:53:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.498 X-Spam-Level: X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 0bVblJnIRWkB for ; Thu, 14 Dec 2017 04:53:00 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [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 08E15128DE5 for ; Thu, 14 Dec 2017 04:53:00 -0800 (PST) Date: Thu, 14 Dec 2017 04:52:59 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513255979; bh=pAN6FV87PiDE2oJABOgEx6PICf+jMbsdDDuvfW0cUJM=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OSa+coAzGXoO7gMqjdAtNRO7qa3HkWffXx9FOg3VzETg44k24aUR6xhHEXXQVhljc tg8qtvQ0jjQQA3T3+f/wDZ9j1+ZIEMQo+xckpYHpPBtyEfCgdt3jwob92NUCQqi58J 6LER0qZoiGZX4FOp7P2LZParqWwWhSVsb2QamFXY= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32742b36818_36ad3fe9ab61ef3424725"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 12:53:02 -0000 ----==_mimepart_5a32742b36818_36ad3fe9ab61ef3424725 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The information elements called attributes in SACM are actually very close to 5209. The proposed new wording implies that atomic is a part of the description in 5209. The pruned content was useful to set it into context. My proposal is to either keep the old definition and not change the term or scrap the consensus and find a new term. I am in strong favor of the former, as I do not see how an attribute is even an data element as it is an information element, nor does the new definition provide me with any guidance how to apply the definition in the context of SACM. -- 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-terminology/issues/62#issuecomment-351702727 ----==_mimepart_5a32742b36818_36ad3fe9ab61ef3424725 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The information elements called attributes in SACM are actually very c= lose to 5209. The proposed new wording implies that atomic is a part of t= he description in 5209. The pruned content was useful to set it into cont= ext.

My proposal is to either keep the old definition and not change the te= rm or scrap the consensus and find a new term. I am in strong favor of th= e former, as I do not see how an attribute is even an data element as it = is an information element, nor does the new definition provide me with an= y guidance how to apply the definition in the context of SACM.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32742b36818_36ad3fe9ab61ef3424725-- From nobody Thu Dec 14 05:54:29 2017 Return-Path: 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 980BD1292AE for ; Thu, 14 Dec 2017 05:54:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.799 X-Spam-Level: X-Spam-Status: No, score=-4.799 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_MSPIKE_H2=-2.8, 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 FtztOBOX2n3x for ; Thu, 14 Dec 2017 05:54:25 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 A3034124205 for ; Thu, 14 Dec 2017 05:54:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=LYW6obLJG/rdSNEdJV40MEGvkyw=; b=vbyVPRtfUm5LJJ4m dzcnASB4M+GZ9/iRtTfN2ZAWlpGa7hxuSK5y6QprXORNupXJKlj0shN5CqjVpr5n CtRiz1lh4bVwmVGPH5WOiZ8mHByxPSTEIo+CDEsPQPK8DcCF0vJd3/5S85ltYcmw BUQjyCXyGMX1/u5ji389zWU0aXg= Received: by filter0326p1iad2.sendgrid.net with SMTP id filter0326p1iad2-22893-5A328290-17 2017-12-14 13:54:24.55545648 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id AtSQXWjIT1qNHYksNpngiQ for ; Thu, 14 Dec 2017 13:54:24.504 +0000 (UTC) Date: Thu, 14 Dec 2017 13:54:24 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32829055913_3063f99834f6f3012342a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H6q029segslF3cDHeCXkYs0zIj3yhynXCMpmhIAeWNtqZP8v1c5MqkdCPi nMscYVwIL2609K3nT87wOLf36qjUN5tYAzp86DqBlToSisv+05hR0By0yO9zff7iVM13TRlDcyt6PI oE2ZgpFwR03s3vLAxHcx1TPanVGMx2Vm06wEfkidiznewRgUY653AHwfDw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposing a new approach to state and configuration (#63) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 13:54:27 -0000 ----==_mimepart_5a32829055913_3063f99834f6f3012342a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A comparison in a nutshell: Configuration is static and modified via the management plane. State is non-static result of interacting functions (and corresponding components) via the the control plane. A distributed automated system cannot function without a working control plane (as it cannot create state via interaction of components/functions), a system can survive for quite a while without a working management plane (configuration cannot be changed and components/functions cannot be monitored though). I.e. no - state is not configuration. I would recommend to never refer to configuration as non-volatile state. Configuration of multiple system entities begets state. Please note, in my personal opinion the sometimes colloquially used term "endpoint state" combines two of the most misleading words used in the SACM WG into an even more misleading term. I'd rather adopt the rather exotic and still emerging terminology - and therefore moving target - from I-D.ietf-netmod-revised-datastores: intended, dynamic, system, learned and default configuration. In this realm of definitions (which significantly diverges from 4949 at some points) "origin" is the taxonomic parent of these terms (origin being a specific subset of the term data provenance wrt "how did this value came to be") and learned configuration would be the semantically closest to state as currently defined in SACM wrt to YANG. I am opposed to change the core semantics of the current definition, but in strong favor of improving it. In consequence, I propose to word-smith the current text instead of trying to introduce a third realm of definitions, where "state" is the taxonomic parent of every other term. In general, I think it is vital to state (sry for the pun) that configuration is imperative guidance. -- 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-terminology/issues/63#issuecomment-351716762 ----==_mimepart_5a32829055913_3063f99834f6f3012342a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

A comparison in a nutshell: Configuration is static and modified via the= management plane. State is non-static result of interacting functions (and= corresponding components) via the the control plane. A distributed automat= ed system cannot function without a working control plane (as it cannot cre= ate state via interaction of components/functions), a system can survive fo= r quite a while without a working management plane (configuration cannot be= changed and components/functions cannot be monitored though).

I.e. no - state is not configuration. I would recommend to never refer t= o configuration as non-volatile state. Configuration of multiple system ent= ities begets state. Please note, in my personal opinion the sometimes collo= quially used term "endpoint state" combines two of the most misleading word= s used in the SACM WG into an even more misleading term.

I'd rather adopt the rather exotic and still emerging terminology - and = therefore moving target - from I-D.ietf-netmod-revised-datastores: intended= , dynamic, system, learned and default configuration. In this realm of defi= nitions (which significantly diverges from 4949 at some points) "origin" is= the taxonomic parent of these terms (origin being a specific subset of the= term data provenance wrt "how did this value came to be") and learned conf= iguration would be the semantically closest to state as currently defined i= n SACM wrt to YANG.

I am opposed to change the core semantics of the current definition, but= in strong favor of improving it. In consequence, I propose to word-smith t= he current text instead of trying to introduce a third realm of definitions= , where "state" is the taxonomic parent of every other term. In general, I = think it is vital to state (sry for the pun) that configuration is imperati= ve guidance.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32829055913_3063f99834f6f3012342a-- From nobody Thu Dec 14 06:01:01 2017 Return-Path: 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 7DE98126C83 for ; Thu, 14 Dec 2017 06:00:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 QneTkyZrJdoC for ; Thu, 14 Dec 2017 06:00:52 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 DB4FD12420B for ; Thu, 14 Dec 2017 06:00:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=AMfKfhhaM1WgjUXo9vXDAmjUlYo=; b=ZcjNCzVC/tb2hOVI gxqhEf6t/6K4FhQWQ/cs8RtVU1RjPjdwc4w/m9WVGJD7ov7i7Enw85notc9q48iR xdb0krPcXM5SzEctnDCcAh1hq9/U2DctSURTnD0ccORteJlf4cAeinsnb0OR2sZJ jn4Scq/o5phq9SJuyVHL04qONOk= Received: by filter0564p1las1.sendgrid.net with SMTP id filter0564p1las1-21023-5A328412-11 2017-12-14 14:00:50.273249542 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0010p1iad2.sendgrid.net (SG) with ESMTP id 26EqC52qQQKQxkf9b5sFuQ for ; Thu, 14 Dec 2017 14:00:50.211 +0000 (UTC) Date: Thu, 14 Dec 2017 14:00:50 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a328412cb87_2ff3fc7ec2dcf282144df"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HztgXJ84/fr16DU24e7IgJIDghvhqNI7dVbZuXclWHuZRlW6g9GGa8J6cK 3i2wflr4qdjBKwzReDiAKj7HqehutAX9eA4xJzoemIH4qn68vjO+MYdXVHVYo/Yn4KWyqNihHYYUiD 4aE5iHHCZPFjrmt35FeqHn6JpuiDF/LooLkfzai7ibinOj2xxGHsqpsG3w== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:00:53 -0000 ----==_mimepart_5a328412cb87_2ff3fc7ec2dcf282144df Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It is true that scope is not defined in this document. Also, explanatory (con)text should help and not confuse. In consequence, I would raise the question: Is it useful to reiterate the association with scope as explanatory (con)text, or is it confusing? -- 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-terminology/issues/64#issuecomment-351718453 ----==_mimepart_5a328412cb87_2ff3fc7ec2dcf282144df Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It is true that scope is not defined in this document. Also, explanatory= (con)text should help and not confuse.

In consequence, I would raise the question: Is it useful to reiterate th= e association with scope as explanatory (con)text, or is it confusing?

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a328412cb87_2ff3fc7ec2dcf282144df-- From nobody Thu Dec 14 06:13:37 2017 Return-Path: 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 7F3D61201F2 for ; Thu, 14 Dec 2017 06:13:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.499 X-Spam-Level: X-Spam-Status: No, score=-6.499 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 FGzs6SxG8d37 for ; Thu, 14 Dec 2017 06:13:33 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext1.iad.github.net [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68B1129353 for ; Thu, 14 Dec 2017 06:13:33 -0800 (PST) Date: Thu, 14 Dec 2017 06:13:33 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513260813; bh=6mCbVYC9PuSHK2voBCVrNiIAGn8oPAALotZ77/og4bc=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=h6X0dsIBT6fShTR+FZ4uGJuyHYZYYzJN4myZ5Isjzcib//SRAZYuuabUJc55pRISA GP6Cdtv717asp8prh0RauRVrzz+X+Vq6Az8gf5+enRonc6no8eQndbXoJ4DBEOdJkI HrEbL1H9Lcr3/3+4P/iQJZFMQU1jUjVeCYlX3Ey0= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32870d367c_22eff3fe9f1196f342979c2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Interaction Model from terminology (#65) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:13:35 -0000 ----==_mimepart_5a32870d367c_22eff3fe9f1196f342979c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The requirements on control plane functions imply certain interaction models (e.g. component registration, capability authentication, or content authorization). The same is true with the way how SACM content is conveyed: Request/Response schemes (e.g. REST), Repository Subscriptions (e.g. YANG Push), Brokered Pub/Sub Topics (e.g. xmpp-grid), or Deployment (e.g. dynamic Call-Home) make use of certain interaction models. As the SACM architecture intends not to prescribe certain solutions, it has to elaborate about the required functions on a more abstract level. The term Interaction Model supports the definition of appropriate non-prescriptive sets of functions in the architecture, I think. Maybe this is a flawed assumption? If so, we can remove the term. -- 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-terminology/issues/65#issuecomment-351721829 ----==_mimepart_5a32870d367c_22eff3fe9f1196f342979c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The requirements on control plane functions imply certain interaction = models (e.g. component registration, capability authentication, or conten= t authorization). The same is true with the way how SACM content is conve= yed: Request/Response schemes (e.g. REST), Repository Subscriptions (e.g.= YANG Push), Brokered Pub/Sub Topics (e.g. xmpp-grid), or Deployment (e.g= . dynamic Call-Home) make use of certain interaction models. As the SACM = architecture intends not to prescribe certain solutions, it has to elabor= ate about the required functions on a more abstract level. The term Inter= action Model supports the definition of appropriate non-prescriptive sets= of functions in the architecture, I think.

Maybe this is a flawed assumption? If so, we can remove the term.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32870d367c_22eff3fe9f1196f342979c2-- From nobody Thu Dec 14 06:35:53 2017 Return-Path: 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 0F5E812420B for ; Thu, 14 Dec 2017 06:35:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.499 X-Spam-Level: X-Spam-Status: No, score=-6.499 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 wZecPxE1PgZQ for ; Thu, 14 Dec 2017 06:35:50 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 154CC1201F2 for ; Thu, 14 Dec 2017 06:35:50 -0800 (PST) Date: Thu, 14 Dec 2017 06:35:49 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513262149; bh=t3vALUw7UI4c2sJTb32/e+Ywt+q2wTrfKw0IisbhsZA=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1E3lNG7RMxlftm45AVwDHpjocxwsE7Pn+vVR8BBM8d7nH5tUIg1DeegiNPW9//gLz qJeCdE58zxr/Z5WWf0/YP/zCtpzg3nupWJbL91E0mA8N5hdwmWeRJHAaB0fH1KaHKI LyrYE9TN6WDJrzER1VvcblDVhXw4eUSQJCF4pTKA= From: David Waltermire Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a328c456344e_178b3ffaa2834f2832690"; 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: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:35:52 -0000 ----==_mimepart_5a328c456344e_178b3ffaa2834f2832690 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The charter defines what is in scope for an IETF WG. Any mention of scope= should be left to the SACM charter. Regards, Dave From: Henk Birkholz [mailto:notifications@github.com] Sent: Thursday, December 14, 2017 9:01 AM To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should SACM scope state= ments belong in the terminology draft? (#64) It is true that scope is not defined in this document. Also, explanatory = (con)text should help and not confuse. In consequence, I would raise the question: Is it useful to reiterate the= association with scope as explanatory (con)text, or is it confusing? =E2=80=94 You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thre= ad. -- = 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-terminology/issues/64#issuecomm= ent-351727868= ----==_mimepart_5a328c456344e_178b3ffaa2834f2832690 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The charter defines what is in scope for an IETF WG. Any mention of scope= should be left to the SACM charter.

Regards,
Dave

From: Henk Birkholz [mailto:notifications@github.com]
Sent: Thursday, December 14, 2017 9:01 AM
To: sacmwg/draft-ietf-sacm-terminology <draft-ietf-sacm-terminology@no= reply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should SACM scope state= ments belong in the terminology draft? (#64)


It is true that scope is not defined in this document. Also, explanatory = (con)text should help and not confuse.

In consequence, I would raise the question: Is it useful to reiterate the= association with scope as explanatory (con)text, or is it confusing?

=E2=80=94
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks= .protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com%2Fsacmwg%2Fdraft-= ietf-sacm-terminology%2Fissues%2F64%23issuecomment-351718453&data=3D0= 2%7C01%7Cdavid.waltermire%40nist.gov%7Cc454bf0a45fb43b292af08d542fb15a1%7= C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C636488568520605164&sdata=3D= Qq8g%2FaHb8Ip9E6Kg1mBTE%2BOUNnCk4okjUmH8FxxMvEE%3D&reserved=3D0>, = or mute the thread<https://na01.safelinks.protection.outlook.com/?url=3D= https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJaiaGfGSf0= 8cvs-vqzeW1IL3FikEOQBks5tASoRgaJpZM4Q8hiP&data=3D02%7C01%7Cdavid.walt= ermire%40nist.gov%7Cc454bf0a45fb43b292af08d542fb15a1%7C2ab5d82fd8fa4797a9= 3e054655c61dec%7C1%7C0%7C636488568520605164&sdata=3DID14tcWGlUO8rtt1U= p8A0owhbbgjm3lRDWmBgARM7uc%3D&reserved=3D0>.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a328c456344e_178b3ffaa2834f2832690-- From nobody Thu Dec 14 06:37:33 2017 Return-Path: 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 82FD01201F2 for ; Thu, 14 Dec 2017 06:37:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.999 X-Spam-Level: X-Spam-Status: No, score=-6.999 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_HI=-5, 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 FgPuZzZSS5Jw for ; Thu, 14 Dec 2017 06:37:30 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [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 5FA9D126C89 for ; Thu, 14 Dec 2017 06:37:30 -0800 (PST) Date: Thu, 14 Dec 2017 06:37:29 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513262249; bh=HuvG45fW+gj2EkUTmLnyV0Si9MEIq6Wwm9pIqXu9Fmg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=BPLsAjO19cY4sE45ApQVsFhGnFUUE8BWcElr1FT6ogqOHhNy7UiGpKczpCrQIY5Zm oGQwbt8CMQIT0GCPfpe7VSwMjtyS679NW3jZLqzlkxU5NHNS8eYUMr/Em3zB/XOQJV E1XUQFEcAZ32uC/G9F1gty6l5WYQm8CjzO6rm6/w= From: David Waltermire Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a328ca9a3758_51173f8ea2402f34587d3"; 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: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "asset" to "SACM asset"? (#61) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:37:32 -0000 ----==_mimepart_5a328ca9a3758_51173f8ea2402f34587d3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am in favor of less jargon. If we don=E2=80=99t need the term asset, th= en we should drop it. Regards, Dave From: Henk Birkholz [mailto:notifications@github.com] Sent: Thursday, December 14, 2017 7:45 AM To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should we change "asset= " to "SACM asset"? (#61) I am not really sure why the term asset is still used. We do "security po= sture assessment of target endpoints". Of course, from an org pov, everyt= hing that supports a primary or secondary business process is an asset - = and then some. Therefore most entities (such as components, functions and= or even planes) count as assets. SAM is a thing that makes use of SWID, = so I see a specific relationship there also. But effectively, Asset is a = catch all phrase with little meaning to SACM, in general. It is still in because it doesn't hurt to see how SACM relates the term (= which we do by the included examples), I think. It is not required to be = in the terminology document. It helps if it is in there more than it hurt= s when it is not there, I think. I am more on the neutral side. Slightly in favor of removing it entirely = rather than word-smithing its definition away from 4949. =E2=80=94 You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread= . -- = 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-terminology/issues/61#issuecomm= ent-351728329= ----==_mimepart_5a328ca9a3758_51173f8ea2402f34587d3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am in favor of less jargon. If we don=E2=80=99t need the term asset, th= en we should drop it.

Regards,
Dave

From: Henk Birkholz [mailto:notifications@github.com]
Sent: Thursday, December 14, 2017 7:45 AM
To: sacmwg/draft-ietf-sacm-terminology <draft-ietf-sacm-terminology@no= reply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should we change "= asset" to "SACM asset"? (#61)


I am not really sure why the term asset is still used. We do "securi= ty posture assessment of target endpoints". Of course, from an org p= ov, everything that supports a primary or secondary business process is a= n asset - and then some. Therefore most entities (such as components, fun= ctions and or even planes) count as assets. SAM is a thing that makes use= of SWID, so I see a specific relationship there also. But effectively, A= sset is a catch all phrase with little meaning to SACM, in general.

It is still in because it doesn't hurt to see how SACM relates the te= rm (which we do by the included examples), I think. It is not required to= be in the terminology document. It helps if it is in there more than it = hurts when it is not there, I think.

I am more on the neutral side. Slightly in favor of removing it entirely = rather than word-smithing its definition away from 4949.

=E2=80=94
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://na01.safelinks= .protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com%2Fsacmwg%2Fdraft-= ietf-sacm-terminology%2Fissues%2F61%23issuecomment-351701073&data=3D0= 2%7C01%7Cdavid.waltermire%40nist.gov%7Ccd773c2a146f400585f808d542f08607%7= C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C636488523197215903&sdata=3D= vntuqjSIxxb0jwIwGSO8uD1Bxd92G7%2FsoAZ9F0JFQPg%3D&reserved=3D0>, or= mute the thread<https://na01.safelinks.protection.outlook.com/?url=3D= https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJaiaJP05dr= UChMsqnVC0gQRgK9hec6Pks5tARhZgaJpZM4Q8hXd&data=3D02%7C01%7Cdavid.walt= ermire%40nist.gov%7Ccd773c2a146f400585f808d542f08607%7C2ab5d82fd8fa4797a9= 3e054655c61dec%7C1%7C0%7C636488523197215903&sdata=3DYCwdh6FqgDd60cfwU= XBLNarlSMmtheDBxNQPITRP5ec%3D&reserved=3D0>.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a328ca9a3758_51173f8ea2402f34587d3-- From nobody Thu Dec 14 06:44:36 2017 Return-Path: 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 4AC6F126C89 for ; Thu, 14 Dec 2017 06:44:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.498 X-Spam-Level: X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 dKZDV1ZstrAy for ; Thu, 14 Dec 2017 06:44:33 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BE5D1293D6 for ; Thu, 14 Dec 2017 06:44:32 -0800 (PST) Date: Thu, 14 Dec 2017 06:44:31 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513262671; bh=5ig2AJxaL8OvAVsK5ik/KHT3UsZ0puMKPPZ06/uTlJE=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OI3WDAze3aY+CpeeXXCi2AL7umHz0HhEBd9J+8XWQJlqJNpW7zxJg6K/m+5sv40aw aICnr6ed+dQFpYvFGy8zRnU9/a/7/BcyEPaWz8B8dsLg3XCSjRgQ+aQGLcLsErXrck dx22ASEX2U/ZyQ2kjtMPLU+GkiElMoWA+ivQxcac= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a328e4f94c1b_26f23fa767062f2c1028e7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:44:35 -0000 ----==_mimepart_5a328e4f94c1b_26f23fa767062f2c1028e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I would like to rephrase it into a question and a meta-question: Is the definition helpful to understand the term metadata and its usage of the sub-types wrt implementors or other readers of the document? I am basically neutral. If not defined here, it has to be elaborated on where it is used most, which is in the information model, I think. I am slightly in favor of keeping both definition and context here in this doc and have a redundant paragraph about when or how a IE type is used to represent metadata and when it represents content, in the IM too. -- 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-terminology/issues/66#issuecomment-351730427 ----==_mimepart_5a328e4f94c1b_26f23fa767062f2c1028e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I would like to rephrase it into a question and a meta-question:

Is the definition helpful to understand the term metadata and its usag= e of the sub-types wrt implementors or other readers of the document?

=

I am basically neutral. If not defined here, it has to be elaborated o= n where it is used most, which is in the information model, I think. I am= slightly in favor of keeping both definition and context here in this do= c and have a redundant paragraph about when or how a IE type is used to r= epresent metadata and when it represents content, in the IM too.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a328e4f94c1b_26f23fa767062f2c1028e7-- From nobody Thu Dec 14 06:54:12 2017 Return-Path: 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 BD15A1293F5 for ; Thu, 14 Dec 2017 06:54:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.615 X-Spam-Level: X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 R1RjBzjVbB5K for ; Thu, 14 Dec 2017 06:54:10 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 A11521293F3 for ; Thu, 14 Dec 2017 06:54:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=KJAVwd2isRhrk4irX/ZkMWroB0U=; b=b7YM95H/PGKUw7L8 5fr+x2w4Ookly1uuuu4v2Iac/ly4fYkwvT7QZfO6eyC4rboQDfdHDhbXjgvgVZNm /ETDWBbCq62UoGuo99pNnio0XwYXTJgVfTemfdt5FnZOKj8bRUUtlDzFw2l3nBY5 GYeNTGIP8pLzEs9NNFcSYRdUcZM= Received: by filter0168p1las1.sendgrid.net with SMTP id filter0168p1las1-25190-5A32908F-35 2017-12-14 14:54:07.739099277 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad2.sendgrid.net (SG) with ESMTP id _LD-l4yTSHyGZcP13jRJbw for ; Thu, 14 Dec 2017 14:54:07.576 +0000 (UTC) Date: Thu, 14 Dec 2017 14:54:07 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32908ee43f2_5e7a3fbef8f20f348268a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1omiGAsJjtgi6gRcadZdGQRaarBQkmdCamxggXISwX4B/Wyy3YFCkGkYZ pbdXosBvbuRe3n9SoFldSeouSEy9CUlo+14lc8j62uq8Ps3OpuiTyWbtEhlHj4bVQ3i5PvgINtgjHR HC6cvDyMu5bI/J+qOlD5tz2oFbyaY4IDiST7VX6g4X4ONkX20zST2yl0Xg== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 14:54:12 -0000 ----==_mimepart_5a32908ee43f2_5e7a3fbef8f20f348268a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The charter text does neither include date in motion nor data at rest. How would you resolve the disconnect between definition and scope, Dave? Also, when the WG is closed, a definition, what the scope the created set of RFC (i.e. the scope of the contributions, not the scope of the WG) will have, should remain in at least one document. Where would you retain that information, Dave? -- 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-terminology/issues/64#issuecomment-351733285 ----==_mimepart_5a32908ee43f2_5e7a3fbef8f20f348268a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The charter text does neither include date in motion nor data at rest. H= ow would you resolve the disconnect between definition and scope, Dave?

Also, when the WG is closed, a definition, what the scope the created se= t of RFC (i.e. the scope of the contributions, not the scope of the WG) wil= l have, should remain in at least one document. Where would you retain that= information, Dave?

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32908ee43f2_5e7a3fbef8f20f348268a-- From nobody Thu Dec 14 07:02:49 2017 Return-Path: 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 074681293F5 for ; Thu, 14 Dec 2017 07:02:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ku83Y0P7H-zO for ; Thu, 14 Dec 2017 07:02:43 -0800 (PST) Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 C84D71293EE for ; Thu, 14 Dec 2017 07:02:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=M2d0GXsn3gkeO+sVBmE3Brf3t+w=; b=fZUG0P1IjRYVShfB ZL+tZmfTwSnG7DmzDdGTyHpmhFs7+K7PayawwyfdSha31a9+lXPY1NOh1UActO3H V3utbcqeQx1MsVz2IKNFhS9fpWvnmDdPDKieEPjlfHmvf2Efkb+MUp7j/v0y+k+1 DhKrW5U+OJT4fnleYnJ3yCi/zWI= Received: by filter0628p1iad2.sendgrid.net with SMTP id filter0628p1iad2-7179-5A329291-1C 2017-12-14 15:02:41.476662209 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad2.sendgrid.net (SG) with ESMTP id 14-NlOcVSiGNeH_hforntg for ; Thu, 14 Dec 2017 15:02:41.503 +0000 (UTC) Date: Thu, 14 Dec 2017 15:02:41 +0000 (UTC) From: David Waltermire Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a3292913205a_46963f936c620f2c9903d"; 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 X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H97LL9cIcOMDqlrDnEK8xvkbvrl3h2q+ueLP1ANoa7mm8D7+g41nrbEC8I /nsiqcsZMGSKpxuozpwytBdynsKr7IT8PGm93vMVU8cv//NAqp+7CZmCQszqvOzYm+IblarLDIG3JB RfPfjWeAQunSkHcvdE4aqKU+RijTLgR7bLpkxHDm/0ibkfZeUMLuHWY1ubW36LWliPEqV8jCUO5d3s s= Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:02:45 -0000 ----==_mimepart_5a3292913205a_46963f936c620f2c9903d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable If the charter does not state something as out of scope, it is typical that= the thing is considered within scope. From a process perspective, it=E2=80= =99s up to the WG chairs to sort out scope issues if needed. I don=E2=80=99t think it=E2=80=99s necessary to retain information about th= e scope of the WG. Each published RFC should articulate the scope of what i= t is defining. If cross RFC or architectural concerns need to be defined, t= hen an architecture draft should speak to such concerns. From: Henk Birkholz [mailto:notifications@github.com] Sent: Thursday, December 14, 2017 9:54 AM To: sacmwg/draft-ietf-sacm-terminology Cc: Waltermire, David A. (Fed) ; Comment Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should SACM scope stateme= nts belong in the terminology draft? (#64) The charter text does neither include date in motion nor data at rest. How = would you resolve the disconnect between definition and scope, Dave? Also, when the WG is closed, a definition, what the scope the created set o= f RFC (i.e. the scope of the contributions, not the scope of the WG) will h= ave, should remain in at least one document. Where would you retain that in= formation, Dave? =E2=80=94 You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. --=20 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-terminology/issues/64#issuecommen= t-351735771= ----==_mimepart_5a3292913205a_46963f936c620f2c9903d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable If the charter does not state something as out of scope, it is typical that= the thing is considered within scope. From a process perspective, it=E2=80= =99s up to the WG chairs to sort out scope issues if needed.

I don=E2=80=99t think it=E2=80=99s necessary to retain information about th= e scope of the WG. Each published RFC should articulate the scope of what i= t is defining. If cross RFC or architectural concerns need to be defined, t= hen an architecture draft should speak to such concerns.

From: Henk Birkholz [mailto:notifications@github.com]
Sent: Thursday, December 14, 2017 9:54 AM
To: sacmwg/draft-ietf-sacm-terminology <draft-ietf-sacm-terminology@nore= ply.github.com>
Cc: Waltermire, David A. (Fed) <david.waltermire@nist.gov>; Comment &= lt;comment@noreply.github.com>
Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should SACM scope stateme= nts belong in the terminology draft? (#64)


The charter text does neither include date in motion nor data at rest. How = would you resolve the disconnect between definition and scope, Dave?

Also, when the WG is closed, a definition, what the scope the created set o= f RFC (i.e. the scope of the contributions, not the scope of the WG) will h= ave, should remain in at least one document. Where would you retain that in= formation, Dave?

=E2=80=94
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://na01.safelinks.p= rotection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com%2Fsacmwg%2Fdraft-ietf= -sacm-terminology%2Fissues%2F64%23issuecomment-351733285&data=3D02%7C01= %7Cdavid.waltermire%40nist.gov%7C605e82d262c0412759b008d5430287bf%7C2ab5d82= fd8fa4797a93e054655c61dec%7C1%7C0%7C636488600502407702&sdata=3Dofei7mkl= oh8EqW7IuC0V%2BCNVmwqH%2FrEUj5ha1qdJt9k%3D&reserved=3D0>, or mute th= e thread<https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2= F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJaiaHlE-MYKy8aoFM5ff_v= 477swXvdtks5tATaOgaJpZM4Q8hiP&data=3D02%7C01%7Cdavid.waltermire%40nist.= gov%7C605e82d262c0412759b008d5430287bf%7C2ab5d82fd8fa4797a93e054655c61dec%7= C1%7C0%7C636488600502407702&sdata=3DnF%2F4XVhI1qiqhHLxkEV1dhJGyPbVJtqMc= dPC7pHFbmI%3D&reserved=3D0>.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a3292913205a_46963f936c620f2c9903d-- From nobody Thu Dec 14 07:05:04 2017 Return-Path: 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 615ED126D3F for ; Thu, 14 Dec 2017 07:04:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ErduE9RhC0_p for ; Thu, 14 Dec 2017 07:04:53 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 C3286129401 for ; Thu, 14 Dec 2017 07:04:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=evnKzIOmNfX5LHpAu3Wgu2lthck=; b=uDP0qXFJqPuqd2/X loeHVS8ylpi428Qf63sE/TSkC7XCuXE3fIE575orXh/OYMZn6oJGhn+TzKmUuTua WKk69SKHGtOAcV8ZeWztgB5qnm/Y0nYmY2tYDFSUWa2c+ZwUhfaNvzGjGyNWuYrN bEvwtxMDJF13scPsnD2GRsMQcro= Received: by filter0392p1iad2.sendgrid.net with SMTP id filter0392p1iad2-7090-5A329312-27 2017-12-14 15:04:50.857056785 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad2.sendgrid.net (SG) with ESMTP id ea9t3ZGOS1yGIbaZgtadGw for ; Thu, 14 Dec 2017 15:04:50.608 +0000 (UTC) Date: Thu, 14 Dec 2017 15:04:51 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329312a14b4_4e0e3f8947a02f34183244"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H5SIzNhhHYaEkCjoIBoBpX2CzfApy/2F9zub/7EWG2fjwfhHCQN6oMVJ0Z ebCauL9QVN7XvuOzBTF9M/o6p6d1XNkfoCHzd8FNaQ7RkvZrJRbbFIOpRT61YwGEofW2uGIYsP/kLB IWqmeprt4nU8szEJs0lmiaTclEPoL59vXvOQzqBE13IrKE0TpLtkp/AFYw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Need to clarify "attribute" vs. "posture attributes" (#67) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:04:55 -0000 ----==_mimepart_5a329312a14b4_4e0e3f8947a02f34183244 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Another way to resolve this, is to get rid of posture attribute. I am starting to slightly favor that approach Wrt Adam's proposal, attributes would be a synonym for posture attributes and we would have to merge the complete information element semantics into that definition (which would limit the definition of information elements to "security posture", I suppose, and that would be incorrect). Actually, I start to think that posture attribute is an artifact from the very beginning that we did not dare to throw out yet. -- 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-terminology/issues/67#issuecomment-351736433 ----==_mimepart_5a329312a14b4_4e0e3f8947a02f34183244 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Another way to resolve this, is to get rid of posture attribute. I am st= arting to slightly favor that approach

Wrt Adam's proposal, attributes would be a synonym for posture attribute= s and we would have to merge the complete information element semantics int= o that definition (which would limit the definition of information elements= to "security posture", I suppose, and that would be incorrect).

Actually, I start to think that posture attribute is an artifact from th= e very beginning that we did not dare to throw out yet.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a329312a14b4_4e0e3f8947a02f34183244-- From nobody Thu Dec 14 07:07:18 2017 Return-Path: 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 A4ABB1293F3 for ; Thu, 14 Dec 2017 07:07:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.381 X-Spam-Level: X-Spam-Status: No, score=-5.381 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 tQ9QPDoJ53ue for ; Thu, 14 Dec 2017 07:07:12 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3572126D3F for ; Thu, 14 Dec 2017 07:07:11 -0800 (PST) Date: Thu, 14 Dec 2017 07:07:11 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513264031; bh=ctKHwY9FQskTHCurB+5m4xu1iL5uJFVczIDVCSWrZ74=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Kiye1bkQA/y9ZfMn2fer3CUG/MBagqpUd1fk5U2AwqEV7R7Pd+I1aaGlmD6cGGfaG Mft6M+1CZv8qZ+U4Xx4r9FauufjWDKfTu/b8hov6waxY8FsRzmTHM8FKLgLiBe1C6r deAYkRAFDqMo6qU/F0ho0u06Xbsgdf4ZbYAEAoO8= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32939f53fa4_5e823fbef8f20f3434472b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposal to remove the input/output details from definitions (#68) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:07:16 -0000 ----==_mimepart_5a32939f53fa4_5e823fbef8f20f3434472b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed. I think they should go into the architecture. Also, we probably need more running code to refine the understanding of their "scope" (I do not mean WG scope!). -- 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-terminology/issues/68#issuecomment-351737107 ----==_mimepart_5a32939f53fa4_5e823fbef8f20f3434472b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Agreed. I think they should go into the architecture. Also, we probabl= y need more running code to refine the understanding of their "scope" (I = do not mean WG scope!).

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32939f53fa4_5e823fbef8f20f3434472b-- From nobody Thu Dec 14 07:15:15 2017 Return-Path: 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 DC409126DED for ; Thu, 14 Dec 2017 07:15:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.799 X-Spam-Level: X-Spam-Status: No, score=-4.799 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_MSPIKE_H2=-2.8, 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 GqzXr-rcf4nm for ; Thu, 14 Dec 2017 07:15:12 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 E2F0A126D3F for ; Thu, 14 Dec 2017 07:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=nXVX4WThdScTgB9gfFieHX8bY2E=; b=B9DUYocYbGEi+C6/ WExtCCrFhpeCcZNOKtzEaTbUVAvBpuf6pEwbVkuvIXcykZf4PJ2meUuNGq10iGy0 WZgiIQI6QMb5RfpfgV0s1cob63RoXHF6Ur8A3wfIrQMqDbW1pOosZPKQaiP2eJHs dRoFmChNUvmqFXndV1OJREo+PiM= Received: by filter0473p1las1.sendgrid.net with SMTP id filter0473p1las1-31993-5A32957D-27 2017-12-14 15:15:09.516310074 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id -1Upgd1MRkqGg31sbkr8fw for ; Thu, 14 Dec 2017 15:15:09.422 +0000 (UTC) Date: Thu, 14 Dec 2017 15:15:09 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32957d4ebd1_2a4d3ff3bb9b2f2810958b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H9jDTk3nqFsaQ6Kd3Ez6nBmkVYy7xuxHYHWWZTB0NqHKFGlalqH+H5GJE7 oAbP2Qh8tTGHCCPWdFrqfU42ft7Ld3W5Oohw2x45RfSDCuKX3BnZYepNZ0Q9AzPI8w1Wp5l2KbhPUO 9VI47TTozZn1VQHD83UszS1OSZu072PYZnfiuKsh5YLEVAp27FOkO2E6HA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should SACM scope statements belong in the terminology draft? (#64) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:15:14 -0000 ----==_mimepart_5a32957d4ebd1_2a4d3ff3bb9b2f2810958b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I agree that we do not need to retain WG charter scope. That is why I tried to highlight "scope of resulting solutions". In the end, there will be a set of proposed standards, a few of them informational. Imagine, the reader for example being an engineer of a vendor, I would like to know the intend and applicability of these proposed standards to my products and business strategy. Effectively, I would like to know if I can just use any data at rest representation I want, or if there are some imposed prescribed restrictions wrt the characteristics of how I store processed content in a repository - and there are none. This is the only reason why the text is in the definition. If this violates an exclusiveness that is tied to the context of the charter, we just have to rephrase it and/or put that information in another document. If not, maybe just keep it. -- 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-terminology/issues/64#issuecomment-351739403 ----==_mimepart_5a32957d4ebd1_2a4d3ff3bb9b2f2810958b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I agree that we do not need to retain WG charter scope.

That is why I tried to highlight "scope of resulting solutions".

In the end, there will be a set of proposed standards, a few of them inf= ormational. Imagine, the reader for example being an engineer of a vendor, = I would like to know the intend and applicability of these proposed standar= ds to my products and business strategy. Effectively, I would like to know = if I can just use any data at rest representation I want, or if there are s= ome imposed prescribed restrictions wrt the characteristics of how I store = processed content in a repository - and there are none.

This is the only reason why the text is in the definition. If this viola= tes an exclusiveness that is tied to the context of the charter, we just ha= ve to rephrase it and/or put that information in another document. If not, = maybe just keep it.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32957d4ebd1_2a4d3ff3bb9b2f2810958b-- From nobody Thu Dec 14 07:34:54 2017 Return-Path: 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 45ABB126DED for ; Thu, 14 Dec 2017 07:34:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.998 X-Spam-Level: X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 Zys_34NcKWN8 for ; Thu, 14 Dec 2017 07:34:51 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84905124319 for ; Thu, 14 Dec 2017 07:34:51 -0800 (PST) Date: Thu, 14 Dec 2017 07:34:50 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513265690; bh=UT9WpenkiLs3UO4PcZvGWTUizZvJB3wO4AnH/v4xtsA=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XIIRMQJRQC4AZaHHOm0DsL1qUi2p2tnnt4zgEqyWXn2dUV47rEpcZCvgXDNQAd+fC nqqUFXpJuMDayORClL1/FsIhTmQ8Vi5VNDojiwTAlefXMdRjywUL8WXiQMO6DIodGy WksQsuMA6QIIHwTkN65on1aVlvAxdaJoWbgoAtvw= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329a1a91a20_17b63fcfc04aef2856843"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Improve the definition of SACM Component Discovery (#69) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:34:53 -0000 ----==_mimepart_5a329a1a91a20_17b63fcfc04aef2856843 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Agreed. While the definition is not "wrong" it is totally confusing. Interestingly, you wrote action instead of task (which is on my list and off-topic). I will go with task for now, but at some point we should revisit task. Maybe somthing like this? "the task of discovering the capabilities provided by SACM components within a SACM domain via an appropriate set of control plane functions." This reverses the order of Component and Capability - but maybe that is for the better? Capabilities are the starting point, I think. If 10 components can provide the capability, maybe they provide also other characteristics that help me to choose. -- 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-terminology/issues/69#issuecomment-351745397 ----==_mimepart_5a329a1a91a20_17b63fcfc04aef2856843 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Agreed. While the definition is not "wrong" it is totally confusing.

Interestingly, you wrote action instead of task (which is on my list a= nd off-topic). I will go with task for now, but at some point we should r= evisit task.

Maybe somthing like this? "the task of discovering the capabilities pr= ovided by SACM components within a SACM domain via an appropriate set of = control plane functions." This reverses the order of Component and Capabi= lity - but maybe that is for the better? Capabilities are the starting po= int, I think. If 10 components can provide the capability, maybe they pro= vide also other characteristics that help me to choose.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a329a1a91a20_17b63fcfc04aef2856843-- From nobody Thu Dec 14 07:37:24 2017 Return-Path: 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 BBE59129412 for ; Thu, 14 Dec 2017 07:37:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.615 X-Spam-Level: X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 NW5-c9eeljp9 for ; Thu, 14 Dec 2017 07:37:15 -0800 (PST) Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 2E90B129407 for ; Thu, 14 Dec 2017 07:37:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=BBCLnTlztCQ0wfAFEQeteOZKzTY=; b=MQOKgMYSl0OqYe05 Iqq6+uvX6OaiJEWR0jWMblyipCRcveV4qDXyJGLWzeSOnCsoBdu/4B8YYmhAI3v6 0hOjzwO4eKxb6z7x5QHmNXsTM4vR59hA8NdkV7uejTciW325AvturQOdSF5x6xW3 Bx7wCowNokqAECRCUav0ruWCp/U= Received: by filter0575p1iad2.sendgrid.net with SMTP id filter0575p1iad2-6589-5A329AAA-1 2017-12-14 15:37:14.044848892 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id t1exuS7ZR_CQxqt4ezsbvA for ; Thu, 14 Dec 2017 15:37:14.012 +0000 (UTC) Date: Thu, 14 Dec 2017 15:37:14 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329aa9dc582_47a43fd6aac60f281201c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxF11fMUj1FVPjZQ5yjdJ1+zIjmcpdwOcZKa8nqTM+H/sANNQ58KLnlPyL dCyefT1Qykao7t/8Mv6qsTHCH9dGDpIHzwUDBV0UrmnYX/6EqtO931wUBz3pKBtDUhMukFzXQU/oAI c6gdeFqgOnvjvwx8+0cvhZ7ytJCOkLxEfsp5LsI1UYo6qhSnKvA+utav4w== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Can't use software package to define software package (#70) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:37:17 -0000 ----==_mimepart_5a329aa9dc582_47a43fd6aac60f281201c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit While I think we should not base definitions on wikipedia - everything beats a reflexive reference :+1: and the text is actually not bad. We have to come up with our own or a better reference, but that's a good starting point. I am pretty sure that ISO experts could help here. -- 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-terminology/issues/70#issuecomment-351746111 ----==_mimepart_5a329aa9dc582_47a43fd6aac60f281201c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

While I think we should not base definitions on wikipedia - everything b= eats a reflexive reference =F0=9F=91=8D and the text is actually not bad. We have to come= up with our own or a better reference, but that's a good starting point. I= am pretty sure that ISO experts could help here.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a329c8fa57f5_4bdb3f9aa6d5ef28494f9-- From nobody Thu Dec 14 07:51:18 2017 Return-Path: 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 289AA12704A for ; Thu, 14 Dec 2017 07:51:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.615 X-Spam-Level: X-Spam-Status: No, score=-0.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Q8MNQWKdcg8z for ; Thu, 14 Dec 2017 07:51:15 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 9B0CC126CD8 for ; Thu, 14 Dec 2017 07:51:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=yVKT5u5Vw5fYVN4+U8HMiJQ1h2A=; b=E5ZLhihEE2qHbwmT iEbQ5nOeNTRuLBI+ZQ1qFU5yxqpmZzVrlPIMPD6+Yp8BVwIrIoh5XYx1Th3oOavx sgClgrBxkHEbfpzZeMyc6oUhGPsyy2Nx4/Yh6fPTkPxQkE3aMnOOLJKOUrhcXEro q5SFl3q0F+lMkaUdKwk4EoyZmtY= Received: by filter0219p1iad2.sendgrid.net with SMTP id filter0219p1iad2-22566-5A329DF2-13 2017-12-14 15:51:14.56988562 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id 5EGW2WmCT9OQP0vMSpoT_w for ; Thu, 14 Dec 2017 15:51:14.402 +0000 (UTC) Date: Thu, 14 Dec 2017 15:51:14 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329df24023e_1a553fe87c7e6f2c225075"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HyCyZSU26nl+hidSPj0TLKMS5XgQB7wYJWSC6VSN6JYbeePCu6fZFJT5ei MRlNJ/oX0Qh71VPrniYMqi7t7j6SWwYoxvCr0Zs/60RIrfbsDvfJiT8CgINT6eN8CwzZymkuoQln2J 3Fc+oviXitIKMrjuMrKu2/ZqKtohIGRtlhGTNykfRkD2gJd1IqyJSe8GRw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove (or redefine) Statement (#72) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:51:17 -0000 ----==_mimepart_5a329df24023e_1a553fe87c7e6f2c225075 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually the definition of Statement includes two paragraphs, I think. Te other one is. "When a statement is used to provide content to a SACM domain, it is a top-level subject that bundles Content Elements into one subject and includes metadata about the data origin." If you want to merge both paragraphs into one, every improvement of the definition is welcome, if it retains the illustrated semantics. -- 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-terminology/issues/72#issuecomment-351750374 ----==_mimepart_5a329df24023e_1a553fe87c7e6f2c225075 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Actually the definition of Statement includes two paragraphs, I think. T= e other one is.

"When a statement is used to provide content to a SACM domain, it is a t= op-level subject that bundles Content Elements into one subject and include= s metadata about the data origin."

If you want to merge both paragraphs into one, every improvement of the = definition is welcome, if it retains the illustrated semantics.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a329df24023e_1a553fe87c7e6f2c225075-- From nobody Thu Dec 14 07:52:53 2017 Return-Path: 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 884DA126CD8 for ; Thu, 14 Dec 2017 07:52:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.881 X-Spam-Level: X-Spam-Status: No, score=-4.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 ItoVqfS3QGcM for ; Thu, 14 Dec 2017 07:52:50 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [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 24FC7124B0A for ; Thu, 14 Dec 2017 07:52:50 -0800 (PST) Date: Thu, 14 Dec 2017 07:52:49 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513266769; bh=PlfgihLrrdfRW0p4HRgesfqoWM7zl6Lb6plBLuiCYWg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=f1kaTxmQbIc07jfSg+7PBaNygiPixY28rSbEA99nIGE2k3UHkLjBRMTdNXqT0bV88 BPedpPbrwuJBJ+0cLj0fDYNDF5yEU0N6xVWJ7MtTgCzfq3y12ec2MQyNxHbHgOr7EP cFKVk7ZyDBmOayPRkk2dBxMsyfSjNfh/vYhfaeSM= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329e515b8e9_3d103fde0ea08f30111235"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Supplicant (#73) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:52:51 -0000 ----==_mimepart_5a329e515b8e9_3d103fde0ea08f30111235 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This issue has dependencies to the definition of the registration task, which is... underspecified at the moment, I think. -- 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-terminology/issues/73#issuecomment-351750857 ----==_mimepart_5a329e515b8e9_3d103fde0ea08f30111235 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This issue has dependencies to the definition of the registration task, which is... underspecified at the moment, I think.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a329e515b8e9_3d103fde0ea08f30111235-- From nobody Thu Dec 14 07:56:37 2017 Return-Path: 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 927C1126CF9 for ; Thu, 14 Dec 2017 07:56:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 iBa5OPBtq1tG for ; Thu, 14 Dec 2017 07:56:35 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 21F18120227 for ; Thu, 14 Dec 2017 07:56:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=YMJ9ntnROCCOosBfytC99C1JXhg=; b=GWY3+cIcMdHyo2f2 qAGA/PObFY+hq28vlq3xPHKIpsRjSSUWZBFbzmLTVJNgO79RVThyIz+BhJa97Gn8 kw8epGmJAMhXhqP8cdLDCicwkVR0mtuEuYiEg2jflKosBJJ+GKwRIA68+Rc1UWQP 6Z5+8C2jvB/KzA0rLNozZdA9rTE= Received: by filter0604p1las1.sendgrid.net with SMTP id filter0604p1las1-20676-5A329F31-14 2017-12-14 15:56:33.790114259 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0010p1iad2.sendgrid.net (SG) with ESMTP id TuPlXoN6SNK4IxyOnAxeyQ for ; Thu, 14 Dec 2017 15:56:33.765 +0000 (UTC) Date: Thu, 14 Dec 2017 15:56:34 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329f31957a6_3d323fde0ea08f3013925c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9Hyd7apOB7N8aEh+DFFLDtGje/toHFegjIl+v0Ldvvh550zLUPcnic4JJAz oBoN8RrXzRYD6lCrpTByVYO9prbsTZlQwBjGWb9CwKh+MUp/39rp3NRTTmTrHsQM1co6hwAH3xiDb5 bxhGe0wSu137q9p+zDM6ZhBzWKk5+JC53XpUbBm0QPKvkq0G3ClN0mOFAw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization (#74) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:56:36 -0000 ----==_mimepart_5a329f31957a6_3d323fde0ea08f3013925c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is an oversight. The term "Endpoint Characterization" is always about target endpoints and should be renamed to "Target Endpoint Characterization". -- 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-terminology/issues/74#issuecomment-351752055 ----==_mimepart_5a329f31957a6_3d323fde0ea08f3013925c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This is an oversight. The term "Endpoint Characterization" is always abo= ut target endpoints and should be renamed to "Target Endpoint Characterizat= ion".

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a329f31957a6_3d323fde0ea08f3013925c-- From nobody Thu Dec 14 07:58:36 2017 Return-Path: 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 01224126CF9 for ; Thu, 14 Dec 2017 07:58:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 deSWTvNQt3oo for ; Thu, 14 Dec 2017 07:58:33 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 88B94120227 for ; Thu, 14 Dec 2017 07:58:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=A6Bklno97LQ5vFDSMkSj4zbE1AA=; b=hxpsKYim18+KkhKs KqNfUWRXc92VgOjdGqJJzj18F1C8Kq0AgFsB/e48mpbyNQh7p1JmAJx0cbt/dwBV SPFl08OG9RKmXcFnCoYvWakD8Doxu4Qjuj9MqzE6my1MHScxT6zma0qVyzH9qOV7 LJNOQDMlvZqu+IZzS+dYTrv1Rd8= Received: by filter0393p1iad2.sendgrid.net with SMTP id filter0393p1iad2-20424-5A329FA7-1B 2017-12-14 15:58:32.056718054 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id POkL9rZyRGCoF9SJ7suBLg for ; Thu, 14 Dec 2017 15:58:32.043 +0000 (UTC) Date: Thu, 14 Dec 2017 15:58:32 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a329fa7e850a_7c153ff55767ef3016786e"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H9Y/ZpLlzex9B90ZJxZEMwSDVhyTmrZYIAmio402tlYAQuftvhx+QfYc1q zqG3BXBHgnQxgqDW231nZxbmL0zJ/3jT1Bg88I0CQZwHvw+/htabkHjIdIVo1mVgTip9kw/JiVYis4 DLYUgIx/J2LfA67SXfePP00G3le6nmVySPMZIogx010bWjxuIxBlz7UEyw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization Task (#75) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 15:58:35 -0000 ----==_mimepart_5a329fa7e850a_7c153ff55767ef3016786e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The task work-flow definition does not belong into the term definition and the editors are (obviously) all aware of that. Most of this text will move into the architecture next the other tasks/work-flow descriptions. -- 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-terminology/issues/75#issuecomment-351752695 ----==_mimepart_5a329fa7e850a_7c153ff55767ef3016786e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The task work-flow definition does not belong into the term definition a= nd the editors are (obviously) all aware of that. Most of this text will mo= ve into the architecture next the other tasks/work-flow descriptions.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a329fa7e850a_7c153ff55767ef3016786e-- From nobody Thu Dec 14 08:00:25 2017 Return-Path: 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 F02A6120227 for ; Thu, 14 Dec 2017 08:00:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.401 X-Spam-Level: X-Spam-Status: No, score=-0.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 UqvITRieaUV6 for ; Thu, 14 Dec 2017 08:00:17 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 B79C3129413 for ; Thu, 14 Dec 2017 08:00:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=W7lajokhQxdh24xWy0yywv4V8eU=; b=a95VUUVPa5HEU9Ww W570Xc7zXr7IXpFdYbYu1yIXYBQqe4/4z6OcQrSxoQWlb7BCICDDzxzgtJE1twkL F2jWh5+/itgLsZepPW+QTy+8sLuClqdtH3iTS8uL9aRvxtcmPBr41R9jPgQP7MSm VjYfWjT05aJh0HM24rDTRb0Snc0= Received: by filter0143p1las1.sendgrid.net with SMTP id filter0143p1las1-32350-5A32A010-39 2017-12-14 16:00:16.528981557 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id kj4mJ-dCShGvrTQli_vE8A for ; Thu, 14 Dec 2017 16:00:16.422 +0000 (UTC) Date: Thu, 14 Dec 2017 16:00:16 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32a01047e1c_300d3ff0dfdb8f344531b5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H98Lc24Y6GMdfa9f3gIWlpbFQUgZ4d4vWUvJZD6ae92zmZp++yUxrxsFbu PN8h3/awk3VqGB8vo9bkQfQn6Hfk1JSYZAqj4SMVSRfkYmn0HvgN3UgrTPHbqeaVpfZGzqNC/X4Mpa U5hbbT87vV1ZXTziINWrql5WSJmhOCUhzMRnPoc0F477oc7ohbjuLEKSjw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Classification Task (#76) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:00:24 -0000 ----==_mimepart_5a32a01047e1c_300d3ff0dfdb8f344531b5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, this is done correctly. It is not named "Endpoint Classification Task" anywhere, but "Target Endpoint Classification Task". -- 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-terminology/issues/76#issuecomment-351753235 ----==_mimepart_5a32a01047e1c_300d3ff0dfdb8f344531b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Actually, this is done correctly. It is not named "Endpoint Classification Task" anywhere, but "Target Endpoint Classification Task".

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a32a01047e1c_300d3ff0dfdb8f344531b5-- From nobody Thu Dec 14 08:04:21 2017 Return-Path: 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 74D7B12940A for ; Thu, 14 Dec 2017 08:04:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.881 X-Spam-Level: X-Spam-Status: No, score=-4.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 X4uwibGRNEjA for ; Thu, 14 Dec 2017 08:04:17 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [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 C53BE12940F for ; Thu, 14 Dec 2017 08:04:16 -0800 (PST) Date: Thu, 14 Dec 2017 08:04:16 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513267456; bh=R+YYknk5yhwJkeGJfdo+tbby8NbVaLnIumSP3D0wa0c=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pK0ISBxA8Oc//h5UV99mH0L3UM+ZBr9dtjctUAnBsDfRXWuzUj3bLyJfati1GjanY GFvrQyKAsSwT0yE6v7yNipBx2IQ3r73Up5CVWDgEKuF9CoLeOdvK0JXDapbk5IIfJu ox+haueLqTK+OYobm7NHc8OYXut178ghZvn+lmPc= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32a10019b93_1be7b3fd774b26f34904a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Discovery Task (#77) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:04:20 -0000 ----==_mimepart_5a32a10019b93_1be7b3fd774b26f34904a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Actually, this is also done correctly. It is not named "Endpoint Discovery Task" anywhere, but "Target Endpoint Classification" in the "list of tasks" and "Target Endpoint Classification Task" is an existing term definition. -- 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-terminology/issues/77#issuecomment-351754438 ----==_mimepart_5a32a10019b93_1be7b3fd774b26f34904a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Actually, this is also done correctly. It is not named "Endpoint Disco= very Task" anywhere, but "Target Endpoint Classification" in the "list of= tasks" and "Target Endpoint Classification Task" is an existing term def= inition.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32a10019b93_1be7b3fd774b26f34904a-- From nobody Thu Dec 14 08:08:52 2017 Return-Path: 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 8EEBA127241 for ; Thu, 14 Dec 2017 08:08:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 kQ_rEFHHSPaV for ; Thu, 14 Dec 2017 08:08:48 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 94D10126CD8 for ; Thu, 14 Dec 2017 08:08:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=L+beLc1VBVx1xrf+50tbLxtYS1U=; b=AA4wEhaOcsDyX6Qz 4atjzNmqwpxdJqnqdC6nVnS0qS45/QI+Ux+d+qLqrJTNkcz5k8Y5yIT3UwFXGlaF ssXR1+85yK8qXOEFitQa0gDRcyVFjvFyg1DIz7iRdZNFQhnlo6mGdBN4poyI6DQl SMh8B6PtYiV9oXqNrRYRRfgv0hQ= Received: by filter0084p1las1.sendgrid.net with SMTP id filter0084p1las1-12775-5A32A20F-15 2017-12-14 16:08:47.389694052 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0024p1iad2.sendgrid.net (SG) with ESMTP id U32TpU8DTDukMmG189zEDw for ; Thu, 14 Dec 2017 16:08:47.242 +0000 (UTC) Date: Thu, 14 Dec 2017 16:08:47 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32a20f27e5d_2fb33fbb57ad2f307461b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H+X4OGvXWV4QNxuJPJaxYdrZK+btjeLxmuPC4RoYrZV9ohwBmpY3AFWCaI XPJj8CHNQRoCpVZhL6+OFn3mCUd2p8N9i8K4IqFTQfEUI3yMYtRBEdaUVNXU8g7izcXmkt0PpKyJuD 3qpj2HX0al1xlQK1qnb2YAfEPCFSurVDyqmWoZEJT36bbo5xfd3YtuH2vA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Relabel Target Endpoint Identifier to Endpoint Identifier (#78) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:08:50 -0000 ----==_mimepart_5a32a20f27e5d_2fb33fbb57ad2f307461b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit An endpoint that is neither a Target Endpoint nor a SACM Component is an Excluded Endpoint (or "explicitly excluded target endpoint" if you will). Having said that, it is correct that in this case we could omit the "target" in the term and the definition would be still correct. I am neutral in this matter, with maybe slightly in favor of removing target in the term name and elaborating in the definition that this identifier is commonly used to differentiate and identify target endpoints. -- 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-terminology/issues/78#issuecomment-351755881 ----==_mimepart_5a32a20f27e5d_2fb33fbb57ad2f307461b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

An endpoint that is neither a Target Endpoint nor a SACM Component is an= Excluded Endpoint (or "explicitly excluded target endpoint" if you will).<= /p>

Having said that, it is correct that in this case we could omit the "tar= get" in the term and the definition would be still correct.

I am neutral in this matter, with maybe slightly in favor of removing ta= rget in the term name and elaborating in the definition that this identifie= r is commonly used to differentiate and identify target endpoints.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32a20f27e5d_2fb33fbb57ad2f307461b-- From nobody Thu Dec 14 08:19:08 2017 Return-Path: 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 3DE81127241 for ; Thu, 14 Dec 2017 08:19:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.018 X-Spam-Level: X-Spam-Status: No, score=-2.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 bdH7zxwZluvm for ; Thu, 14 Dec 2017 08:19:05 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 62D03126CD8 for ; Thu, 14 Dec 2017 08:19:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=zr9AfA5//qcY6NmxU2wLGHyQknA=; b=pzAO2+Tsu5A8um99 TH2ZalFnlnBQXYMZB2fMzSY4vtvCfQjXY/JentHIfGq6xPtXyPoLMHORAA+/KbyI 1INQ8zbncOQhZTod/j2eLUsnt2IyKhFG0GeMz1gBmbYC6C0xsCJ4Xcr33EB0YpYT fGT8GbtBOFD0zuZnRI1ktI/7ISU= Received: by filter0444p1iad2.sendgrid.net with SMTP id filter0444p1iad2-9818-5A32A478-3 2017-12-14 16:19:04.043597854 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id iVnhNOW9QU20gH1eibYcTg for ; Thu, 14 Dec 2017 16:19:04.075 +0000 (UTC) Date: Thu, 14 Dec 2017 16:19:04 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32a4782cad_4adf3fcb68b78f2c202873"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H2ncJ1q9BLnlrqvizohCROemiWh8QPX/92WDHoXUaFoglQtuQdFIuY5UJN smnRpS6kVa+CHQHhh2A/AH4y3M0iK4Fk7nRNcfrFcWxixKpE5jkrYi6fggnH6G5NhECI6+kX3S04cD Ba5AL21vtIQ7BgCnRd6WIAzHDKkXs4d6SGxyPcaTgbiVrp9yTLPw9Wm7XQ== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Label (#79) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:19:07 -0000 ----==_mimepart_5a32a4782cad_4adf3fcb68b78f2c202873 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If the concept Target Endpoint Label is dropped, we loose the object property relationship to data source in content metadata. Also, this term is an example of the indicated specialization in Endpoint Label (in the definition of Endpoint Label) similar to SACM Component Label. Both highlighted examples have Endpoint Label as their taxonomic parent, which makes sense and simplifies/homogenizes how "known things" are referenced in a SACM domain by not using the complete Target Endpoint Identifier (which can become quite big at times) all the time, but using the same label mechanism everywhere. -- 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-terminology/issues/79#issuecomment-351759032 ----==_mimepart_5a32a4782cad_4adf3fcb68b78f2c202873 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If the concept Target Endpoint Label is dropped, we loose the object pro= perty relationship to data source in content metadata. Also, this term is a= n example of the indicated specialization in Endpoint Label (in the definit= ion of Endpoint Label) similar to SACM Component Label. Both highlighted ex= amples have Endpoint Label as their taxonomic parent, which makes sense and= simplifies/homogenizes how "known things" are referenced in a SACM domain = by not using the complete Target Endpoint Identifier (which can become quit= e big at times) all the time, but using the same label mechanism everywhere= .

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32a4782cad_4adf3fcb68b78f2c202873-- From nobody Thu Dec 14 08:32:16 2017 Return-Path: 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 CAA3312941C for ; Thu, 14 Dec 2017 08:32:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xwp3FTfhOW6e for ; Thu, 14 Dec 2017 08:32:13 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 4043E1273B1 for ; Thu, 14 Dec 2017 08:32:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=O9pn+Iui51/adUbKBpyKwkwdDAM=; b=VlhJMuN5KwPdiXiw ZEacDkcxyf+O4O5ZepGR4Dk+gt8mBX/gMMJI9OWd6ZXPGbM7W9e1VjRCa6KMHFQK XLcem2RHVzntgxisHp76B8TJqJvJEyUd511euEJljn3Upkx8Tz6t+yo+pPCbCQMC p35QjVmu3RAsi6nDmHyZIYYE3WQ= Received: by filter0435p1iad2.sendgrid.net with SMTP id filter0435p1iad2-27517-5A32A78C-1C 2017-12-14 16:32:12.398252805 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0009p1iad1.sendgrid.net (SG) with ESMTP id Rw2G4fB_SuG4CaG1VZfbXQ for ; Thu, 14 Dec 2017 16:32:12.168 +0000 (UTC) Date: Thu, 14 Dec 2017 16:32:12 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32a78cf0fc_6a503f9c2cf14f341036f7"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/rbuwTXslxgYo7PNGEUw0UBHd/n45f4wgs/6PQ81a7GB8DIu6jwTSOW92 JaxVXIo9Zt9h70nlxA7Sv/t8ZNSS5ewKKF6pG0mWhRIstlRuFKHWeFR0x5v7nwD52OP7JuoDb/Mo4Y zqVm8/8GydUlteT1vS08bMtvO5YHoEMhNfdz8Lb9wa1BkCPyoBWpl7sJtA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Do we really need to define timestamps? (#80) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:32:16 -0000 ----==_mimepart_5a32a78cf0fc_6a503f9c2cf14f341036f7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Unfortunately, the current understanding is yes *sigh* because they are highly relevant in the scope of a SACM domain. Having said that, I am have a hard time understanding the question, as the definition basically references rfc4949 and the reference is about a "data object timestamp". I.e. we are already talking about data object timestamps. We came to the conclusion that while sometimes clumsy terms, such as, "Target Endpoint Characterization Record" cannot be avoided, here we could just refer to the term timestamp and illustrate the use in the context of a SACM domain. Is that a bad approach? We can name it "Data Object Timestamps", but I am not sure that this would solve a problem. -- 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-terminology/issues/80#issuecomment-351763141 ----==_mimepart_5a32a78cf0fc_6a503f9c2cf14f341036f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Unfortunately, the current understanding is yes sigh because th= ey are highly relevant in the scope of a SACM domain.

Having said that, I am have a hard time understanding the question, as t= he definition basically references rfc4949 and the reference is about a "da= ta object timestamp". I.e. we are already talking about data object timesta= mps. We came to the conclusion that while sometimes clumsy terms, such as, = "Target Endpoint Characterization Record" cannot be avoided, here we could = just refer to the term timestamp and illustrate the use in the context of a= SACM domain.

Is that a bad approach? We can name it "Data Object Timestamps", but I a= m not sure that this would solve a problem.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32a78cf0fc_6a503f9c2cf14f341036f7-- From nobody Thu Dec 14 08:47:43 2017 Return-Path: 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 54191129421 for ; Thu, 14 Dec 2017 08:47:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.998 X-Spam-Level: X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 mq7y3GjJYdZK for ; Thu, 14 Dec 2017 08:47:33 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext5.iad.github.net [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 8936C1288B8 for ; Thu, 14 Dec 2017 08:47:33 -0800 (PST) Date: Thu, 14 Dec 2017 08:47:32 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513270052; bh=cgllqZDFX0NOWdYFEZh/Seup6m9pk+gHsEGiHK5ushM=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TWBikJjLMMYc91Plahewq1OtitGAWE0nXYPFDhb7zwP6eStM3wtRUsIJ3J58oqqhx ybsYQEmcALzuOwhGHIrzD/wbrD+c+KNEAjawi+eyLukFeGw4n3iX4m6n6Y3V2aKOMm CkoaSgea6wimP++NGJWm7ue4XioYkU/XXmOjZcU8= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32ab248ecaf_10a3e3fe82fb82f34117228"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Either remove or actually define Virtual Component (#81) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 16:47:35 -0000 ----==_mimepart_5a32ab248ecaf_10a3e3fe82fb82f34117228 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If I remember correctly, the consensus was to include virtual "components", but I think the meaning behind this was things, such as virtual machines or virtualized network functions. Charles might remember more about this, as we had a long round table discussion on this with him present. A quick hotfix: relabel to Virtual Endpoint and change definition to: "An endpoint composed entirely of logical system components (see RFC4949)." Some context and explanatory text is still required, but that should address the biggest issues ad-hoc, I think. -- 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-terminology/issues/81#issuecomment-351767877 ----==_mimepart_5a32ab248ecaf_10a3e3fe82fb82f34117228 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If I remember correctly, the consensus was to include virtual "compone= nts", but I think the meaning behind this was things, such as virtual mac= hines or virtualized network functions. Charles might remember more about= this, as we had a long round table discussion on this with him present.<= /p>

A quick hotfix: relabel to Virtual Endpoint and change definition to: = "An endpoint composed entirely of logical system components (see RFC4949)= ." Some context and explanatory text is still required, but that should a= ddress the biggest issues ad-hoc, I think.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32ab248ecaf_10a3e3fe82fb82f34117228-- From nobody Thu Dec 14 11:06:25 2017 Return-Path: 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 EC1361293E4 for ; Thu, 14 Dec 2017 11:06:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.799 X-Spam-Level: X-Spam-Status: No, score=-4.799 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_MSPIKE_H2=-2.8, 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 gbhgPgpN6njh for ; Thu, 14 Dec 2017 11:06:22 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 D960F1200C1 for ; Thu, 14 Dec 2017 11:06:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=6WQ0sRBSmoyXqSHQL68ax0s8R90=; b=ZcTUAtAk3qRnhu3T obYI1eLCMw7iRji3jDt7z5OLEDeFMFqE+oh/oyEwcyjujQrulhuf+G5v7D4KuUbi EkPiR14OGd47Z0y9yENxygmt8w4BMDQ31WeE/I/+qvUT+oGXihpQvp5ry8wGLNDD DrxSTLQ9N3/OyDMdxBiJorJSUR4= Received: by filter0223p1iad2.sendgrid.net with SMTP id filter0223p1iad2-1042-5A32CB71-13 2017-12-14 19:05:21.307057672 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id 4w26B_TCQkmkqNGn6G7tPg for ; Thu, 14 Dec 2017 19:05:21.337 +0000 (UTC) Date: Thu, 14 Dec 2017 19:05:21 +0000 (UTC) From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32cb714b09c_3ffe3fe1e6da2f341709c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H/YECU3NXVKzeP+3cZfDciOAnMFvnxRFP35XJrDomys3Qc3DVWLsqUyZPF pP+YvDe9mlhq+Nfd2HlDOEyW0oXgUFxaRPk26WLlBRHeQpeP1oK8+9//o9UJkcsdFopnUo4RZgXwRs dNw/zYCD23zAPBY1rhLarHjoPlrkpLccbsHCO49xNmJ2D8qDKIQF94h4xQ== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "asset" to "SACM asset"? (#61) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 19:06:24 -0000 ----==_mimepart_5a32cb714b09c_3ffe3fe1e6da2f341709c5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree. From Henk's description, there is nothing unique about a SACM asset (vs a non-SACM asset). Hence, I vote for removing the term. regards, John On Thu, Dec 14, 2017 at 6:37 AM, David Waltermire wrote: > I am in favor of less jargon. If we don=E2=80=99t need the term asset, th= en we > should drop it. > > Regards, > Dave > > From: Henk Birkholz [mailto:notifications@github.com] > Sent: Thursday, December 14, 2017 7:45 AM > To: sacmwg/draft-ietf-sacm-terminology noreply.github.com> > Cc: Subscribed > Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should we change > "asset" to "SACM asset"? (#61) > > > I am not really sure why the term asset is still used. We do "security > posture assessment of target endpoints". Of course, from an org pov, > everything that supports a primary or secondary business process is an > asset - and then some. Therefore most entities (such as components, > functions and or even planes) count as assets. SAM is a thing that makes > use of SWID, so I see a specific relationship there also. But effectively, > Asset is a catch all phrase with little meaning to SACM, in general. > > It is still in because it doesn't hurt to see how SACM relates the term > (which we do by the included examples), I think. It is not required to be > in the terminology document. It helps if it is in there more than it hurts > when it is not there, I think. > > I am more on the neutral side. Slightly in favor of removing it entirely > rather than word-smithing its definition away from 4949. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com% > 2Fsacmwg%2Fdraft-ietf-sacm-terminology%2Fissues%2F61% > 23issuecomment-351701073&data=3D02%7C01%7Cdavid.waltermire%40nist.gov% > 7Ccd773c2a146f400585f808d542f08607%7C2ab5d82fd8fa4797a93e054655c6 > 1dec%7C1%7C0%7C636488523197215903&sdata=3DvntuqjSIxxb0jwIwGSO8uD1Bxd92G7 > %2FsoAZ9F0JFQPg%3D&reserved=3D0>, or mute the thread protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com% > 2Fnotifications%2Funsubscribe-auth%2FAJaiaJP05drUChMsqnVC0gQRgK9h > ec6Pks5tARhZgaJpZM4Q8hXd&data=3D02%7C01%7Cdavid.waltermire%40nist.gov% > 7Ccd773c2a146f400585f808d542f08607%7C2ab5d82fd8fa4797a93e054655c6 > 1dec%7C1%7C0%7C636488523197215903&sdata=3DYCwdh6FqgDd60cfwUXBLNarlSMmthe > DBxNQPITRP5ec%3D&reserved=3D0>. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > --=20 regards, John --=20 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-terminology/issues/61#issuecommen= t-351805635= ----==_mimepart_5a32cb714b09c_3ffe3fe1e6da2f341709c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree. From Henk's description, there is nothing unique about a SACM<= br> asset (vs a non-SACM asset). Hence, I vote for removing the term.

regards,
John

On Thu, Dec 14, 2017 at 6:37 AM, David Waltermire <notifications@github.= com>
wrote:

> I am in favor of less jargon. If we don=E2=80=99t need the term asset,= then we
> should drop it.
>
> Regards,
> Dave
>
> From: Henk Birkholz [mailto:notifications@github.com]
> Sent: Thursday, December 14, 2017 7:45 AM
> To: sacmwg/draft-ietf-sacm-terminology <draft-ietf-sacm-terminology= @
> noreply.github.com>
> Cc: Subscribed <subscribed@noreply.github.com>
> Subject: Re: [sacmwg/draft-ietf-sacm-terminology] Should we change
> "asset" to "SACM asset"? (#61)
>
>
> I am not really sure why the term asset is still used. We do "sec= urity
> posture assessment of target endpoints". Of course, from an org p= ov,
> everything that supports a primary or secondary business process is an=
> asset - and then some. Therefore most entities (such as components,
> functions and or even planes) count as assets. SAM is a thing that mak= es
> use of SWID, so I see a specific relationship there also. But effectiv= ely,
> Asset is a catch all phrase with little meaning to SACM, in general. >
> It is still in because it doesn't hurt to see how SACM relates the= term
> (which we do by the included examples), I think. It is not required to= be
> in the terminology document. It helps if it is in there more than it h= urts
> when it is not there, I think.
>
> I am more on the neutral side. Slightly in favor of removing it entire= ly
> rather than word-smithing its definition away from 4949.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub<https://na01.safeli= nks.
> protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com%
> 2Fsacmwg%2Fdraft-ietf-sacm-terminology%2Fissues%2F61%
> 23issuecomment-351701073&data=3D02%7C01%7Cdavid.waltermire%40nist.= gov%
> 7Ccd773c2a146f400585f808d542f08607%7C2ab5d82fd8fa4797a93e054655c6
> 1dec%7C1%7C0%7C636488523197215903&sdata=3DvntuqjSIxxb0jwIwGSO8uD1B= xd92G7
> %2FsoAZ9F0JFQPg%3D&reserved=3D0>, or mute the thread<https:/= /na01.safelinks.
> protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.com%
> 2Fnotifications%2Funsubscribe-auth%2FAJaiaJP05drUChMsqnVC0gQRgK9h
> ec6Pks5tARhZgaJpZM4Q8hXd&data=3D02%7C01%7Cdavid.waltermire%40nist.= gov%
> 7Ccd773c2a146f400585f808d542f08607%7C2ab5d82fd8fa4797a93e054655c6
> 1dec%7C1%7C0%7C636488523197215903&sdata=3DYCwdh6FqgDd60cfwUXBLNarl= SMmthe
> DBxNQPITRP5ec%3D&reserved=3D0>.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/61#is= suecomment-351728329>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSVRE1HEIPdUU= VDCbdd1q7eZwaD6yks5tATKpgaJpZM4Q8hXd>
> .
>



--
regards,
John

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32cb714b09c_3ffe3fe1e6da2f341709c5-- From nobody Thu Dec 14 11:09:17 2017 Return-Path: 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 027DA129459 for ; Thu, 14 Dec 2017 11:09:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.499 X-Spam-Level: X-Spam-Status: No, score=-6.499 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_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 Y0wPsrhPcl4Q for ; Thu, 14 Dec 2017 11:09:14 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [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 6B75F1200C1 for ; Thu, 14 Dec 2017 11:09:14 -0800 (PST) Date: Thu, 14 Dec 2017 11:09:13 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513278553; bh=EQXJDx5RgkQJHuLa4Q8SCAQvwr3NJNYg17VKEoOJdgo=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1kim3MZRqi40JOnoYFl60i5uarTrPmMX9w7CMRbYhecORjbNSmaHntfA7eQzBU/bG 1jSWy3fLIvzxrgyWQdxH9Ap3prNiAdNXpkZd8BSYayjGYwNfRakB3it75peamBEu9A GaAYjvBa5wWtQe7CeNamipiSbtbN4262mG+u904Y= From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32cc5968ff9_72a93fdca6d2ef34158151"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 19:09:17 -0000 ----==_mimepart_5a32cc5968ff9_72a93fdca6d2ef34158151 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm confused. Isn't this what the SACM charter is for? regards, John p.s.: sorry for the delay in responding; currently in a conference and traveling. On Thu, Dec 14, 2017 at 4:52 AM, Henk Birkholz = wrote: > The information elements called attributes in SACM are actually very cl= ose > to 5209. The proposed new wording implies that atomic is a part of the > description in 5209. The pruned content was useful to set it into conte= xt. > > My proposal is to either keep the old definition and not change the ter= m > or scrap the consensus and find a new term. I am in strong favor of the= > former, as I do not see how an attribute is even an data element as it = is > an information element, nor does the new definition provide me with any= > guidance how to apply the definition in the context of SACM. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = regards, John -- = 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-terminology/issues/62#issuecomm= ent-351806609= ----==_mimepart_5a32cc5968ff9_72a93fdca6d2ef34158151 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm confused. Isn't this what the SACM charter is for?

regards,
John

p.s.: sorry for the delay in responding; currently in a conference and traveling.

On Thu, Dec 14, 2017 at 4:52 AM, Henk Birkholz <notifications@github.c= om>
wrote:

> The information elements called attributes in SACM are actually very= close
> to 5209. The proposed new wording implies that atomic is a part of t= he
> description in 5209. The pruned content was useful to set it into co= ntext.
>
> My proposal is to either keep the old definition and not change the = term
> or scrap the consensus and find a new term. I am in strong favor of = the
> former, as I do not see how an attribute is even an data element as = it is
> an information element, nor does the new definition provide me with = any
> guidance how to apply the definition in the context of SACM.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/62#= issuecomment-351702727>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSfbhEPAhaM= _r8t39kvJjdeTnNuu4ks5tARorgaJpZM4Q8hZn>
> .
>



--
regards,
John

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32cc5968ff9_72a93fdca6d2ef34158151-- From nobody Thu Dec 14 11:23:37 2017 Return-Path: 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 B1FBD12714F for ; Thu, 14 Dec 2017 11:23:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 IOMjyjD5V3It for ; Thu, 14 Dec 2017 11:23:35 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 F1445124D6C for ; Thu, 14 Dec 2017 11:23:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=7HT1RLKTmypMhfbDPd0V9SEURuI=; b=nlnbm38TqMKxsKOg aABXNKnVgtFxmHx2LjyMZ6L4r33rUKnF+ZQdcidEHaBRaN+odCMCAhBMlych4G6a cpIvh17OqRXLMUC+PYWAzBX/3mcCybB3kOkW4OjSELfn71apuXll2nHsRO+ypF4f AkMjWK4zO+uVcowu34fyjakI0Hs= Received: by filter0358p1iad2.sendgrid.net with SMTP id filter0358p1iad2-29723-5A32CFB5-2A 2017-12-14 19:23:33.810995728 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id g98ABrCdSqirdP2DYr19kg for ; Thu, 14 Dec 2017 19:23:33.731 +0000 (UTC) Date: Thu, 14 Dec 2017 19:23:34 +0000 (UTC) From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32cfb58b5c6_21713fe422998f2c2697e5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H0Cjconpe3Aldedpdn2jV3UqJVZxEuERyc6CarKUJursP+NSF/sNq77dlU +Pe4vJ5/yCRPrufYSxQdm2jl/pnFaFfzGx0QtWNvG+VND+wbm8YFIZWMOimj2QX82zB8SuSvnQC1In maeygixAwhD+jozbegj7Vxl1w3pqFY6kX1AiOB8EVAJHxGcde7GCt+t/Vw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 19:23:37 -0000 ----==_mimepart_5a32cfb58b5c6_21713fe422998f2c2697e5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable My 2 cents. Metadata is a fundamental tool that is useful for describing and prescribing the characteristics and behavior of a set of objects (where "set" can be 1, of course). I would be loathe to remove the term for these reasons. >From Adam's original post: In the SACM information model, data is referred to as Content. Metadata about the content is referred to as Content-Metadata, respectively. Content and Content-Metadata are combined into Subjects called Content-Elements in the SACM information model. Some information elements defined by the SACM information model can be part of the Content or the Content-Metadata. Therefore, if an information element is considered data or data about data depends on which kind of Subject it is associated with. The SACM information model also defines metadata about the data origin via the Subject Statement-Metadata. Typical examples of metadata are time stamps, data origin or data source. IMHO, this definition needs to be reworked This information isn't really helpful to the definition, and because metadata is a very common term and widely understood as data about data, I propose we remove the term from this draft. While I agree that most people do think this, I believe that we should explicitly mention that metadata can be descriptive as well as prescriptive. regards, John On Thu, Dec 14, 2017 at 6:44 AM, Henk Birkholz wrote: > I would like to rephrase it into a question and a meta-question: > > Is the definition helpful to understand the term metadata and its usage of > the sub-types wrt implementors or other readers of the document? > > I am basically neutral. If not defined here, it has to be elaborated on > where it is used most, which is in the information model, I think. I am > slightly in favor of keeping both definition and context here in this doc > and have a redundant paragraph about when or how a IE type is used to > represent metadata and when it represents content, in the IM too. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > --=20 regards, John --=20 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-terminology/issues/66#issuecommen= t-351810280= ----==_mimepart_5a32cfb58b5c6_21713fe422998f2c2697e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable My 2 cents.

Metadata is a fundamental tool that is useful for describing and
prescribing the characteristics and behavior of a set of objects (where
"set" can be 1, of course). I would be loathe to remove the term = for these
reasons.

>From Adam's original post:

In the SACM information model, data is referred to as Content. Metadata
about the content is referred to as Content-Metadata, respectively. Content=
and Content-Metadata are combined into Subjects called Content-Elements in<= br> the SACM information model. Some information elements defined by the SACM information model can be part of the Content or the Content-Metadata.
Therefore, if an information element is considered data or data about data<= br> depends on which kind of Subject it is associated with. The SACM
information model also defines metadata about the data origin via the
Subject Statement-Metadata. Typical examples of metadata are time stamps, data origin or data source.
<jcs>
IMHO, this definition needs to be reworked
</jcs>

This information isn't really helpful to the definition, and because
metadata is a very common term and widely understood as data about data, I<= br> propose we remove the term from this draft.
<jcs>
While I agree that most people do think this, I believe that we should
explicitly mention that metadata can be descriptive as well as prescriptive= .
</jcs>


regards,
John

On Thu, Dec 14, 2017 at 6:44 AM, Henk Birkholz <notifications@github.com= >
wrote:

> I would like to rephrase it into a question and a meta-question:
>
> Is the definition helpful to understand the term metadata and its usag= e of
> the sub-types wrt implementors or other readers of the document?
>
> I am basically neutral. If not defined here, it has to be elaborated o= n
> where it is used most, which is in the information model, I think. I a= m
> slightly in favor of keeping both definition and context here in this = doc
> and have a redundant paragraph about when or how a IE type is used to<= br> > represent metadata and when it represents content, in the IM too.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#is= suecomment-351730427>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSTJSEYJo-g11= HuOnRZ9mt_995QBGks5tATRPgaJpZM4Q8hpR>
> .
>



--
regards,
John

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32cfb58b5c6_21713fe422998f2c2697e5-- From nobody Thu Dec 14 11:34:43 2017 Return-Path: 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 B0875124D6C for ; Thu, 14 Dec 2017 11:34:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 kq_gVlvHqhsP for ; Thu, 14 Dec 2017 11:34:39 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 093C21200C1 for ; Thu, 14 Dec 2017 11:34:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=sMLLD9Po4BgzBPkLUs7dKm+EaXI=; b=cCjj2Linkuvoe2Wy Z9Radqk6/BVXNVZ7JizpuOxRPLrar0xPLdOTDABwQ7PEusBpfS0KMtYWs1KN84sc x7pmtteFb6hwIc+rBRuVJT71ODp2aSICiWylSTSGkQrfAEQ9i626Kxe6lytekFG8 NBx4HtKFh697LmJQZfnqMBX0FLo= Received: by filter0283p1las1.sendgrid.net with SMTP id filter0283p1las1-17370-5A32D24D-B 2017-12-14 19:34:37.359639817 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad2.sendgrid.net (SG) with ESMTP id xbHJ_GExSFGQT2iC9oDYvg for ; Thu, 14 Dec 2017 19:34:37.201 +0000 (UTC) Date: Thu, 14 Dec 2017 19:34:37 +0000 (UTC) From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32d24d1be8c_58443f8e6c2b6f301302e2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H26VevzztzeCr4Yt7qexLELlFAj/a2zycwW9PiorVgR04HuG2scPKpAdWz g6YQ3sxGyjjNjBu1TxkozlUXYUFdS0cVNgdkqKRZQ4MFleHNz1Iv4sO4e1L48e5At7V6n/q/dmcrTR 4TtbbQEdiWgW/8MhjcEB62EXtVs0FmN3CgQepZywhiFC9UUOe59oXr2yqw== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposing a new approach to state and configuration (#63) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 19:34:42 -0000 ----==_mimepart_5a32d24d1be8c_58443f8e6c2b6f301302e2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree with Adam that the current definitions of configuration and state are insufficient (sorry Henk!). Also (sorry again Henk!) I fail to understand why either is tied to an **endpoint**. If we go back to control theory, the behavior of a functional block is defined by a transfer function that, for a given set of inputs and state, produces a given set of outputs. An endpoint is an externally visible point of the functional block, but do we really, really, really want to expose all endpoints? That would produce a huge attack surface. Henk wrote: A distributed automated system cannot function without a working control plane (as it cannot create state via interaction of components/functions), a system can survive for quite a while without a working management plane (configuration cannot be changed and components/functions cannot be monitored though). I disagree. The management plane is used to configure the control plane. If the management plane dies, so does the control plane. Henk wrote: state is not configuration. I would recommend to never refer to configuration as non-volatile state. Absolutely agree (see Henk, I still luv ya :-) ) Note that this is true in YANG as well (assuming that we want to build YANG data models at some point). Given the above, I agree to wordsmithing the current definition. best regards, John On Thu, Dec 14, 2017 at 5:54 AM, Henk Birkholz wrote: > A comparison in a nutshell: Configuration is static and modified via the > management plane. State is non-static result of interacting functions (and > corresponding components) via the the control plane. A distributed > automated system cannot function without a working control plane (as it > cannot create state via interaction of components/functions), a system can > survive for quite a while without a working management plane (configurati= on > cannot be changed and components/functions cannot be monitored though). > > I.e. no - state is not configuration. I would recommend to never refer to > configuration as non-volatile state. Configuration of multiple system > entities begets state. Please note, in my personal opinion the sometimes > colloquially used term "endpoint state" combines two of the most misleadi= ng > words used in the SACM WG into an even more misleading term. > > I'd rather adopt the rather exotic and still emerging terminology - and > therefore moving target - from I-D.ietf-netmod-revised-datastores: > intended, dynamic, system, learned and default configuration. In this rea= lm > of definitions (which significantly diverges from 4949 at some points) > "origin" is the taxonomic parent of these terms (origin being a specific > subset of the term data provenance wrt "how did this value came to be") a= nd > learned configuration would be the semantically closest to state as > currently defined in SACM wrt to YANG. > > I am opposed to change the core semantics of the current definition, but > in strong favor of improving it. In consequence, I propose to word-smith > the current text instead of trying to introduce a third realm of > definitions, where "state" is the taxonomic parent of every other term. In > general, I think it is vital to state (sry for the pun) that configuration > is imperative guidance. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > --=20 regards, John --=20 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-terminology/issues/63#issuecommen= t-351813122= ----==_mimepart_5a32d24d1be8c_58443f8e6c2b6f301302e2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I agree with Adam that the current definitions of configuration and state are insufficient (sorry Henk!).

Also (sorry again Henk!) I fail to understand why either is tied to an
**endpoint**. If we go back to control theory, the behavior of a functional=
block is defined by a transfer function that, for a given set of inputs and=
state, produces a given set of outputs. An endpoint is an externally
visible point of the functional block, but do we really, really, really
want to expose all endpoints? That would produce a huge attack surface.

Henk wrote:
A distributed automated system cannot function without a working control
plane (as it cannot create state via interaction of components/functions),<= br> a system can survive for quite a while without a working management plane (configuration cannot be changed and components/functions cannot be
monitored though).
<jcs>
I disagree. The management plane is used to configure the control plane. If=
the management plane dies, so does the control plane.
</jcs>

Henk wrote:
state is not configuration. I would recommend to never refer to
configuration as non-volatile state.
<jcs>
Absolutely agree (see Henk, I still luv ya :-) ) Note that this is true in<= br> YANG as well (assuming that we want to build YANG data models at some
point).
</jcs>

Given the above, I agree to wordsmithing the current definition.

best regards,
John

On Thu, Dec 14, 2017 at 5:54 AM, Henk Birkholz <notifications@github.com= >
wrote:

> A comparison in a nutshell: Configuration is static and modified via t= he
> management plane. State is non-static result of interacting functions = (and
> corresponding components) via the the control plane. A distributed
> automated system cannot function without a working control plane (as i= t
> cannot create state via interaction of components/functions), a system= can
> survive for quite a while without a working management plane (configur= ation
> cannot be changed and components/functions cannot be monitored though)= .
>
> I.e. no - state is not configuration. I would recommend to never refer= to
> configuration as non-volatile state. Configuration of multiple system<= br> > entities begets state. Please note, in my personal opinion the sometim= es
> colloquially used term "endpoint state" combines two of the = most misleading
> words used in the SACM WG into an even more misleading term.
>
> I'd rather adopt the rather exotic and still emerging terminology = - and
> therefore moving target - from I-D.ietf-netmod-revised-datastores:
> intended, dynamic, system, learned and default configuration. In this = realm
> of definitions (which significantly diverges from 4949 at some points)=
> "origin" is the taxonomic parent of these terms (origin bein= g a specific
> subset of the term data provenance wrt "how did this value came t= o be") and
> learned configuration would be the semantically closest to state as
> currently defined in SACM wrt to YANG.
>
> I am opposed to change the core semantics of the current definition, b= ut
> in strong favor of improving it. In consequence, I propose to word-smi= th
> the current text instead of trying to introduce a third realm of
> definitions, where "state" is the taxonomic parent of every = other term. In
> general, I think it is vital to state (sry for the pun) that configura= tion
> is imperative guidance.
>
> =E2=80=94
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/63#is= suecomment-351716762>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSayrLG-4VS7p= efIMP9KSSN5guRgaks5tASiQgaJpZM4Q8hfK>
> .
>



--
regards,
John

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a32d24d1be8c_58443f8e6c2b6f301302e2-- From nobody Thu Dec 14 11:42:22 2017 Return-Path: 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 72FE4124F57 for ; Thu, 14 Dec 2017 11:42:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.999 X-Spam-Level: X-Spam-Status: No, score=-6.999 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_HI=-5, 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 BRddiqqXIYQ7 for ; Thu, 14 Dec 2017 11:42:19 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFD60124D6C for ; Thu, 14 Dec 2017 11:42:18 -0800 (PST) Date: Thu, 14 Dec 2017 11:42:18 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513280538; bh=vPaPwGtaqksfRdPoUOGwToDmOq4zua0jAwRlRRyX274=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pKKzUcAcjxNsTGInNwl1AFKBPIketbf/qCaZKoyzKDaseiYQETXESSGCV78ilzEVW XYwUogsgVzsmLuJysYX3dwOZgr2UvGBs87ZWN4/a13RKsXXToxy0+C1QTv50kfp/NC 0EYSNojKISuuc8TFt+q98RpMQaT4QoTv88qeQvcs= From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a32d41a2fab_10403fae225e2f3012963"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Interaction Model from terminology (#65) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 19:42:20 -0000 ----==_mimepart_5a32d41a2fab_10403fae225e2f3012963 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In UML, interaction diagrams are a subset of behavior diagrams. Interacti= on diagrams describe the flow of data and control among the entities being modeled. For example, a sequence diagram shows how different entities communicate with each other using a sequence of messages. Things like BPM= N expand the (limited) concepts in a UML sequence diagram to include a rich= set of control constructs. Hence, I think we need this term. More importantly, we need user stories that use interaction and behavior diagrams to illustrate how SACM (can) work. regards, John On Thu, Dec 14, 2017 at 6:13 AM, Henk Birkholz = wrote: > The requirements on control plane functions imply certain interaction > models (e.g. component registration, capability authentication, or cont= ent > authorization). The same is true with the way how SACM content is conve= yed: > Request/Response schemes (e.g. REST), Repository Subscriptions (e.g. YA= NG > Push), Brokered Pub/Sub Topics (e.g. xmpp-grid), or Deployment (e.g. > dynamic Call-Home) make use of certain interaction models. As the SACM > architecture intends not to prescribe certain solutions, it has to > elaborate about the required functions on a more abstract level. The te= rm > Interaction Model supports the definition of appropriate non-prescripti= ve > sets of functions in the architecture, I think. > > Maybe this is a flawed assumption? If so, we can remove the term. > > =E2=80=94 > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = regards, John -- = 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-terminology/issues/65#issuecomm= ent-351815219= ----==_mimepart_5a32d41a2fab_10403fae225e2f3012963 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In UML, interaction diagrams are a subset of behavior diagrams. Interacti= on
diagrams describe the flow of data and control among the entities being modeled. For example, a sequence diagram shows how different entities
= communicate with each other using a sequence of messages. Things like BPM= N
expand the (limited) concepts in a UML sequence diagram to include a rich=
set of control constructs.

Hence, I think we need this term. More importantly, we need user stories<= br> that use interaction and behavior diagrams to illustrate how SACM (can) work.

regards,
John

On Thu, Dec 14, 2017 at 6:13 AM, Henk Birkholz <notifications@github.c= om>
wrote:

> The requirements on control plane functions imply certain interactio= n
> models (e.g. component registration, capability authentication, or c= ontent
> authorization). The same is true with the way how SACM content is co= nveyed:
> Request/Response schemes (e.g. REST), Repository Subscriptions (e.g.= YANG
> Push), Brokered Pub/Sub Topics (e.g. xmpp-grid), or Deployment (e.g.=
> dynamic Call-Home) make use of certain interaction models. As the SA= CM
> architecture intends not to prescribe certain solutions, it has to > elaborate about the required functions on a more abstract level. The= term
> Interaction Model supports the definition of appropriate non-prescri= ptive
> sets of functions in the architecture, I think.
>
> Maybe this is a flawed assumption? If so, we can remove the term. >
> =E2=80=94
> You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/65#= issuecomment-351721829>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSWdr8Lrd0Z= 4E5zhfVIMDG0som6Zgks5tAS0MgaJpZM4Q8hl2>
> .
>



--
regards,
John

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a32d41a2fab_10403fae225e2f3012963-- From nobody Thu Dec 14 15:17:21 2017 Return-Path: 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 4A1DC12896F for ; Thu, 14 Dec 2017 15:17:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 izp7Uvei_3TI for ; Thu, 14 Dec 2017 15:17:17 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 A7BAB129466 for ; Thu, 14 Dec 2017 15:16:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Fcv+j4wOjlpO48M+tY0KsERYJ7E=; b=IsXO0BvRRNfo4aaZ /8s+jM+HPk6VH6nH7n6CMpAlNhV6idCaUAUANtV4V7c87aJd22ypA2gmkq+ZViKp nOy61i+/tAFiAwe8CnKRcTmIZLfItYRLClFVpDN8N09RQLFjyvMs1l368oKbuED/ yNzx69xKTMWE/pTVx2sG3YAQmYA= Received: by filter0501p1iad2.sendgrid.net with SMTP id filter0501p1iad2-31432-5A330667-1D 2017-12-14 23:16:55.508902068 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id CXFfNyXCR2e4x0B7f8finA for ; Thu, 14 Dec 2017 23:16:55.236 +0000 (UTC) Date: Thu, 14 Dec 2017 23:16:55 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a3306679954_6a273f93bafa0f2c3008af"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H0vwK/pJm0gjF8ubUJ3pW9oCX61D9V0ZK44SQGNA/8c1jdmkKpCCBhPahM CuzIOp0fdif0e0wWayRw1RsluRJGJjpdWAsVcVTl3yMOTLhd0RNjaPvnIFzjncb2+i21IrT9i7c94l 3keMjYKH1Cy+ynDc3tVkX+IHrn5sTsykCUhJQPu8PamyRgC5rPjBv0dTFQ== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposing a new approach to state and configuration (#63) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2017 23:17:19 -0000 ----==_mimepart_5a3306679954_6a273f93bafa0f2c3008af Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Okay, lets delve into the finer nuances of this. tl;dr the definitions of configuration and state require some work. Jarrett already indicated that at the mic, if I remember correctly. Functions are essential to the architecture. I admit to simplifying the topic at hand. I still disagree with the notion of the control plane dieing, if the management plane dies. It continuous to function, but probably not with the intend it is supposed to function, if environmental requirements change (as you are unable to influence behavior of the control plane anymore). It might not act in a way you require it to do anymore, but it does not die. It "just" not acts according to updated requirements imposed to it by management plane updates and therefore it will not be compliant to current imperative guidance. It is "just" deprived of imperative guidance updates. I.e., it will not be in compliance with current imperative guidance anymore, but it does not "die" and the SACM domain should be aware of that state (see, I still agree with you :-) ) And yes, the definition most certainly requires some love, I agree with that, too. I also agree with the notion that control plane behavior should not be tied to "endpoints" but "functions". Alas, the term function has been pruned currently and as a result "endpoint" is the next level in the taxonomy of terms it can be tied to in the current version of the draft. Essentially, control plane behavior is of course steered by control plane functions (located on SACM components that are endpoints), but I agree it is not the endpoints that are in charge of orchestrating control plane behavior, the corresponding functional blocks located on SACM components are. In consequence, no - we really do not want to expose all the endpoints in this scope. That is the reason why there was the definition of functions that just got removed, in the first place. -- 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-terminology/issues/63#issuecomment-351865483 ----==_mimepart_5a3306679954_6a273f93bafa0f2c3008af Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Okay, lets delve into the finer nuances of this.

tl;dr the definitions of configuration and state require some work. Jarr= ett already indicated that at the mic, if I remember correctly. Functions a= re essential to the architecture.

I admit to simplifying the topic at hand. I still disagree with the noti= on of the control plane dieing, if the management plane dies. It continuous= to function, but probably not with the intend it is supposed to function, = if environmental requirements change (as you are unable to influence behavi= or of the control plane anymore). It might not act in a way you require it = to do anymore, but it does not die. It "just" not acts according to updated= requirements imposed to it by management plane updates and therefore it wi= ll not be compliant to current imperative guidance. It is "just" deprived o= f imperative guidance updates.

I.e., it will not be in compliance with current imperative guidance anym= ore, but it does not "die" and the SACM domain should be aware of that sta= te (see, I still agree with you :-) )

And yes, the definition most certainly requires some love, I agree with = that, too.

I also agree with the notion that control plane behavior should not be t= ied to "endpoints" but "functions". Alas, the term function has been pruned= currently and as a result "endpoint" is the next level in the taxonomy of = terms it can be tied to in the current version of the draft. Essentially, c= ontrol plane behavior is of course steered by control plane functions (loca= ted on SACM components that are endpoints), but I agree it is not the endpo= ints that are in charge of orchestrating control plane behavior, the corres= ponding functional blocks located on SACM components are. In consequence, n= o - we really do not want to expose all the endpoints in this scope. That i= s the reason why there was the definition of functions that just got remove= d, in the first place.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a3306679954_6a273f93bafa0f2c3008af-- From nobody Thu Dec 14 16:24:56 2017 Return-Path: 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 A4CEF1205F0 for ; Thu, 14 Dec 2017 16:24:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.474 X-Spam-Level: X-Spam-Status: No, score=-0.474 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=no 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 7TTss4HfzzRU for ; Thu, 14 Dec 2017 16:24:53 -0800 (PST) Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 3BB071200F3 for ; Thu, 14 Dec 2017 16:24:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=I/spaeYQwK9W/uIicF7qITFaf6E=; b=ux0pbtSUgaGUsu2o fTdHdD3S2TV3Ua821gmqXjjIQFJAmbrEzfKbVeSilJQCSsXsmU2KDyLf0DTcZxZC LL1q1itLehETy48fmI8/Zr89DrLP/eOsVsqOZSL1BDEROwfRzf/I9vVSfxi1yeqS SHZnMrOLrgmW+p1QKyEBElEIfUg= Received: by filter0426p1iad2.sendgrid.net with SMTP id filter0426p1iad2-7547-5A331654-3 2017-12-15 00:24:52.160865809 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id 9PpdRe_FSBGpEDVtoHhtZQ for ; Fri, 15 Dec 2017 00:24:52.043 +0000 (UTC) Date: Fri, 15 Dec 2017 00:24:52 +0000 (UTC) From: David Somers-Harris Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a331653d7a80_38d13fc90d6bef3490634"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: davidkazuhiro X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9Hz7XUI7gQ7gNY3Ggu9CMG9VS28pq5GfBDXYnzdZjOsWeUDWRvAMSVAuKqZ uhd7GcejOnvOF53vIUkWswqu6rHxDILOnTmq5ZD9vLP50R4/BhXDOtQRacUPmIKnKizP9d9H+uJZsa anFy0fbtOEwYcEcDhe56ial0XM0tzX/XUYtWJUubNxo6NQ4hj09ozU1KSyHt8VupVIfNHB+W4Ky/3k o= Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 00:24:55 -0000 ----==_mimepart_5a331653d7a80_38d13fc90d6bef3490634 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit That would do it :) -- 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-terminology/issues/82#issuecomment-351877024 ----==_mimepart_5a331653d7a80_38d13fc90d6bef3490634 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

That would do it :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a331653d7a80_38d13fc90d6bef3490634-- From nobody Fri Dec 15 07:34:28 2017 Return-Path: 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 298371292F4 for ; Fri, 15 Dec 2017 07:34:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.882 X-Spam-Level: X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.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 s7FTMW3mTk2e for ; Fri, 15 Dec 2017 07:34:25 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [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 6252B126B6E for ; Fri, 15 Dec 2017 07:34:23 -0800 (PST) Date: Fri, 15 Dec 2017 07:34:22 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513352062; bh=eWThPEj/2GxLD8FQBnyiqjdUnV7AT/Jz193Ud+/wcro=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GWOl3IDDr1x6CJ8odHqRTrCxMgrtf6XmXI4WqpVVTg7fgRoCcJXQcvDddmPbnxtY3 XpwBrKwpLR6IDJfhcnluz9d/WVqwGzPywjEV4raicglx7lk0KsbgxuIggMail7RFet 1f67hSbdADZhmrrxzpHznJAu6Gf4jnn9gGTQ68t0= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a33eb7e61d87_78c03fad419f0f28354844"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 15:34:27 -0000 ----==_mimepart_5a33eb7e61d87_78c03fad419f0f28354844 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit These are probably two points worthwhile to be captured and worked into an improved definition (if we decide not to drop the term): * any IE can be used as data or as metadata, depending on context * metadata can be descriptive as well as prescriptive -- 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-terminology/issues/66#issuecomment-352035067 ----==_mimepart_5a33eb7e61d87_78c03fad419f0f28354844 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

These are probably two points worthwhile to be captured and worked int= o an improved definition (if we decide not to drop the term):

  • any IE can be used as data or as metadata, depending on context
  • metadata can be descriptive as well as prescriptive

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a33eb7e61d87_78c03fad419f0f28354844-- From nobody Fri Dec 15 07:45:42 2017 Return-Path: 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 EBD5A1270A7 for ; Fri, 15 Dec 2017 07:45:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.382 X-Spam-Level: X-Spam-Status: No, score=-5.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, 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 IjqT6sXioSNl for ; Fri, 15 Dec 2017 07:45:39 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [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 57E91126C89 for ; Fri, 15 Dec 2017 07:45:39 -0800 (PST) Date: Fri, 15 Dec 2017 07:45:38 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513352738; bh=sHh4LdFG8t6IjNjUhiTWBLdm5Lr+Qq8rIsjdu1naecU=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cRb29bHiGfFU2y3QLf0ApR+sncWsgANgv0cHr2c19VVEdrLSzNvKCNFgpFH4wUmDQ rGFzMxQsj//lk1IqTFpkiGZcL/ntYY8C0/qhG5PienmgndNbP4AMv0wG5b0k7nWklH SfODMVvgW+BmRrNT3ibaTc30f55CyOraTHBtmtaU= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a33ee22af93f_c4a3ff72365cf34129425"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposed update to Security Automation (#82) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 15:45:41 -0000 ----==_mimepart_5a33ee22af93f_c4a3ff72365cf34129425 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit :+1: for adding the term "Information Security Program" defined in ISO 704:2009 in order to be used in the definition of Security Automation proposed by Adam. -- 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-terminology/issues/82#issuecomment-352038018 ----==_mimepart_5a33ee22af93f_c4a3ff72365cf34129425 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=F0=9F=91=8D for adding the term "Information Security Program" defined in ISO 7= 04:2009 in order to be used in the definition of Security Automation prop= osed by Adam.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a33ee22af93f_c4a3ff72365cf34129425-- From nobody Sat Dec 16 02:29:07 2017 Return-Path: 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 AA2401242F7 for ; Sat, 16 Dec 2017 02:29:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.095 X-Spam-Level: X-Spam-Status: No, score=-5.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, 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 hdV8rJ1NAFcR for ; Sat, 16 Dec 2017 02:29:04 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [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 ECB271205F1 for ; Sat, 16 Dec 2017 02:29:03 -0800 (PST) Date: Sat, 16 Dec 2017 02:29:02 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513420142; bh=x1HXbHcuUF5OTy85o1ehsBREIgx7W4sNwgrLmz+ZkL4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=guRrkYApuWDnUxxUZONrTuXere68idtvFesLuSS1tIllVjGzOPRtP3yfhCAcVCPyX jLgyBuW1gh0Q6wDmTNGLcLOQhvb+Qim5KQ4exKbu+rpOwHigcMwq1kx7k1rtSkdAxI bOVJmflI00Mt9wbn5ghHPr9EUySi3NYQa/o4hyA4= From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: sacm , Comment Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a34f56e8c0b2_27853ffbea12cf3475117f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Dec 2017 10:29:06 -0000 ----==_mimepart_5a34f56e8c0b2_27853ffbea12cf3475117f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hm, whike certainly possible, it would create a lot of redundancy (YANG just removed a similar type of redundancy, via NMDA, by collapsing redundant trees). An overused but viable example: the IE IPv4-Address. It can be part of an TE identifier -> being metadata. It can be part of SACM Content -> being data. Would you recommend to introduce two types of IPv4-Address for this? NETCONF, for example, reverted that kind of decision. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#issuecomment-352174828 ----==_mimepart_5a34f56e8c0b2_27853ffbea12cf3475117f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hm, whike certainly possible, it would create a lot of redundancy (YAN= G just removed a similar type of redundancy, via NMDA, by collapsing redu= ndant trees). An overused but viable example: the IE IPv4-Address.

It can be part of an TE identifier -> being metadata.

It can be part of SACM Content -> being data.

Would you recommend to introduce two types of IPv4-Address for this? N= ETCONF, for example, reverted that kind of decision.

&m= dash;
You are receiving this because you commented.
Reply to th= is email directly, view it on GitHub, or mute the thread.3D""=

= ----==_mimepart_5a36fdd15d26a_5b703fde6e95ef34178696-- From nobody Sun Dec 17 15:31:22 2017 Return-Path: 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 58115126D85 for ; Sun, 17 Dec 2017 15:31:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 aTCGarAYhPXY for ; Sun, 17 Dec 2017 15:31:19 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 549081201FA for ; Sun, 17 Dec 2017 15:31:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=RUz46X3ziyAT3R9Z4UZXjn58x1c=; b=tkM8I562IvUGZAk4 XUrZh7VqvnftWvpa1+yqLNOjZKCSlvnpewlFCNU64HO4QEFqgHHS42sCrxTOI1r8 WgwKsvTSevkpehHrLeCxO9XgZXOBf1+QE7u354+52GQY2G0E5v+tMP3M3WrVCThe CkPr7A/TDidP+iFc3U+qhXxGveI= Received: by filter0331p1las1.sendgrid.net with SMTP id filter0331p1las1-17497-5A36FE46-9 2017-12-17 23:31:18.168808081 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0006p1sjc2.sendgrid.net (SG) with ESMTP id UfPxI_6ESlOVCxn_DYBKNg for ; Sun, 17 Dec 2017 23:31:17.716 +0000 (UTC) Date: Sun, 17 Dec 2017 23:31:18 +0000 (UTC) From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: sacm , Comment Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a36fe45162d6_2e503f98915b8f38106668f"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H+X4OGvXWV4QNxuJPJaxYdqCGGSQtVWHqAyd4TC62GaReUaneiXDMz25/Y gCPZvKwaLHWV/lrgFLui6UfT0zLd5+lAHSqAK4KjLXs6AN+8crEzhFu905SR109muJLzLT3zBAOpLY P8B+Hs68CUrXQ1wDXNpX/oOYd2W6GG8dplAQnIkoot/Mqw0VhBmkrV3pqA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 23:31:21 -0000 ----==_mimepart_5a36fe45162d6_2e503f98915b8f38106668f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Disagree. You must define formal logic that says that an object can be of two different types. regards, John On Sat, Dec 16, 2017 at 11:14 AM, Henk Birkholz wrote: > Addendum: From an Ontology pov (I did not take that into account in my > first reply), it is rather okay to tie (domain/range association) a conce= pt > via two different object properties to two different other core concepts > (e.g. data & metadata) concepts. Even in the more restrictive scope of > taxonimc parents(hip), there can be more than one parent concept (although > this would render an a-box rather complex and might not be recommended in= a > production envirionment, as it requires more complex and reliable reasone= rs > - i.e. potentially creates a lot of reasoning overhead). > > =E2=80=94 > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > --=20 regards, John --=20 You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#issuecommen= t-352294863= ----==_mimepart_5a36fe45162d6_2e503f98915b8f38106668f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Disagree. You must define formal logic that says that an object can be of two different types.

regards,
John

On Sat, Dec 16, 2017 at 11:14 AM, Henk Birkholz <notifications@github.co= m>
wrote:

> Addendum: From an Ontology pov (I did not take that into account in my=
> first reply), it is rather okay to tie (domain/range association) a co= ncept
> via two different object properties to two different other core concep= ts
> (e.g. data & metadata) concepts. Even in the more restrictive scop= e of
> taxonimc parents(hip), there can be more than one parent concept (alth= ough
> this would render an a-box rather complex and might not be recommended= in a
> production envirionment, as it requires more complex and reliable reas= oners
> - i.e. potentially creates a lot of reasoning overhead).
>
> =E2=80=94
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#is= suecomment-352204884>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSUVP2cz2So0i= Q2glaPPP5FTW98xNks5tBBaagaJpZM4Q8hpR>
> .
>



--
regards,
John

&mda= sh;
You are receiving this because you commented.
Reply to this e= mail directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5a36fe45162d6_2e503f98915b8f38106668f-- From nobody Sun Dec 17 15:59:21 2017 Return-Path: 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 8C7121270A7 for ; Sun, 17 Dec 2017 15:59:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 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_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 f38padNMxW3C for ; Sun, 17 Dec 2017 15:59:17 -0800 (PST) Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (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 8B1731201FA for ; Sun, 17 Dec 2017 15:59:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=n77fJsXVKpYmLIu9WfxlNiVrX0A=; b=EnLC1W6XI3TV1b1b OGUSY9a1JVaGo5gDMT3foJVnsVOOWwHCU2pjjTcCoWBH5WXt6wgeTYpVpuGB8CJ/ QK9jqnZfft2QHXD6YygcXf9NzW+O5DhNK0Q0KxHs7U9DxOWyaAtP0FOD2JWLxtcg Y3Ukn0Dt1l0tglMvX5G/mfu/vRA= Received: by filter0256p1las1.sendgrid.net with SMTP id filter0256p1las1-29556-5A3704D3-29 2017-12-17 23:59:15.97819926 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0018p1iad2.sendgrid.net (SG) with ESMTP id sTe9S8fjTfCxMX9SAqK6UA for ; Sun, 17 Dec 2017 23:59:15.874 +0000 (UTC) Date: Sun, 17 Dec 2017 23:59:16 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: sacm , Comment Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a3704d3ac18f_7c1b3f8ab2c22f28160453c"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HxGln4ikXLg1tcqPqaC3ytFn7GAlWOeYPXbd8r8XkIxi4QYbjSqsfc3tan fOjxt5JSoMyWsbPsg6V9cWTZyk/HB3a2DTGy2vKnrmUKyTyOhFUCZDULTbGogqvRNoQm9twoFiHzvI GcxEmZCbDqWlr3m+PL88fv3Ruz/jT8uwEYtKptyBjJ/WumkXcdiRwbHxPA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Dec 2017 23:59:19 -0000 ----==_mimepart_5a3704d3ac18f_7c1b3f8ab2c22f28160453c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > Sorry, I fail to see: 1) why we care if there is redundancy in an **infor= mation** model a) YANG is a=20 > **data** model b) the purpose of an info model is to define objects and t= heir relationships;=20 > redundancy is a function of good the model is I agree, I got distracted by Ontologies :-) Touch=C3=A9. This is about the = IM. Redundancy vs. Readability and in consequence comprehensibility. > Nope. As I said earlier, having something being of two types is problemat= ic at best wrt code > generation. Furthermore, why would an identitifer ever be considered meta= data? Isn't an identifier at > least as important as data? :-) And remember= , metadata is typically considered optional. I would still argue it is the same type (e.g. in my example) used in differ= ent contexts (e.g. via ontological object property relationships), which pr= ovides it with more context, mae it data and metadata in the first place - = correspondingly until now I did not understood metadata as specific subset = of all types.... like unit32 and unit32-metadata. You made me become more neutral on this point, with a slight favor of not c= reating redundant IE types for metadata and data, but I am starting to unde= rstand your point better. --=20 You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#issuecommen= t-352296625= ----==_mimepart_5a3704d3ac18f_7c1b3f8ab2c22f28160453c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Sorry, I fail to see: 1) why we care if there is redundancy in an information model a) YANG is a
data model b) the purpose of an info model is to define ob= jects and their relationships;
redundancy is a function of good the model is

I agree, I got distracted by Ontologies :-) Touch=C3=A9. This is about t= he IM.
Redundancy vs. Readability and in consequence comprehensibility.

Nope. As I said earlier, having something being of two types is problema= tic at best wrt code
generation. Furthermore, why would an identitifer ever be considered metada= ta? Isn't an identifier at > least as important as data? :-) And remembe= r, metadata is typically considered optional.

I would still argue it is the same type (e.g. in my example) used in dif= ferent contexts (e.g. via ontological object property relationships), which= provides it with more context, mae it data and metadata in the first place= - correspondingly until now I did not understood metadata as specific subs= et of all types.... like unit32 and unit32-metadata.

You made me become more neutral on this point, with a slight favor of no= t creating redundant IE types for metadata and data, but I am starting to u= nderstand your point better.

&mda= sh;
You are receiving this because you commented.
Reply to this e= mail directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5a3704d3ac18f_7c1b3f8ab2c22f28160453c-- From nobody Sun Dec 17 16:31:58 2017 Return-Path: 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 5B268124D68 for ; Sun, 17 Dec 2017 16:31:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7 X-Spam-Level: X-Spam-Status: No, score=-7 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_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 0Pbar2mpJlxd for ; Sun, 17 Dec 2017 16:31:54 -0800 (PST) Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ACEA1201FA for ; Sun, 17 Dec 2017 16:31:54 -0800 (PST) Date: Sun, 17 Dec 2017 16:31:53 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513557113; bh=ObOT+9RDWErgDC+druZ+t5fqjaAGy+1TD75v3nVF8/c=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=x9hnBJdi4flu+5g1MJjdsY/LqCenQ+eMIHktAyoaWgMcUuxFiCCFDCTDGJOQWMpDS CZHzXICxpA+b6K5B28FmiNJVgarv94fNprqsjacvGwxfD8yi1Pz9dhcP8gqJC1VW7j kBlc7DW2O/zPOAC+kUI1/am0dPEcqFmmYNHICmDg= From: strazzie123 Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: sacm , Comment Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a370c792e047_489b3f98ec64af2c121147b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: strazzie123 X-GitHub-Recipient: sacm X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove the term metadata from the draft. (#66) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 00:31:56 -0000 ----==_mimepart_5a370c792e047_489b3f98ec64af2c121147b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would still argue it is the same type (e.g. in my example) used in different contexts (e.g. via ontological object property relationships), which provides it with more context, mae it data and metadata in the firs= t place - correspondingly until now I did not understood metadata as specif= ic subset of all types.... like unit32 and unit32-metadata. The problem is that while this could work for ontologies, it doesn't work= for info or data models. regards, John On Sun, Dec 17, 2017 at 3:59 PM, Henk Birkholz = wrote: > Sorry, I fail to see: 1) why we care if there is redundancy in an > *information* model a) YANG is a > *data* model b) the purpose of an info model is to define objects and > their relationships; > redundancy is a function of good the model is > > I agree, I got distracted by Ontologies :-) Touch=C3=A9. This is about = the IM. > Redundancy vs. Readability and in consequence comprehensibility. > > Nope. As I said earlier, having something being of two types is > problematic at best wrt code > generation. Furthermore, why would an identitifer ever be considered > metadata? Isn't an identifier at > least as important as data? :-) And > remember, metadata is typically considered optional. > > I would still argue it is the same type (e.g. in my example) used in > different contexts (e.g. via ontological object property relationships)= , > which provides it with more context, mae it data and metadata in the fi= rst > place - correspondingly until now I did not understood metadata as spec= ific > subset of all types.... like unit32 and unit32-metadata. > > You made me become more neutral on this point, with a slight favor of n= ot > creating redundant IE types for metadata and data, but I am starting to= > understand your point better. > > =E2=80=94 > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > , > or mute the thread > > . > -- = regards, John -- = You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#issuecomm= ent-352298888= ----==_mimepart_5a370c792e047_489b3f98ec64af2c121147b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I would still argue it is the same type (e.g. in my example) used in
different contexts (e.g. via ontological object property relationships),<= br> which provides it with more context, mae it data and metadata in the firs= t
place - correspondingly until now I did not understood metadata as specif= ic
subset of all types.... like unit32 and unit32-metadata.

<jcs>
The problem is that while this could work for ontologies, it doesn't = work
for info or data models.
</jcs>


regards,

John

On Sun, Dec 17, 2017 at 3:59 PM, Henk Birkholz <notifications@github.c= om>
wrote:

> Sorry, I fail to see: 1) why we care if there is redundancy in an > *information* model a) YANG is a
> *data* model b) the purpose of an info model is to define objects an= d
> their relationships;
> redundancy is a function of good the model is
>
> I agree, I got distracted by Ontologies :-) Touch=C3=A9. This is abo= ut the IM.
> Redundancy vs. Readability and in consequence comprehensibility.
= >
> Nope. As I said earlier, having something being of two types is
> problematic at best wrt code
> generation. Furthermore, why would an identitifer ever be considered=
> metadata? Isn't an identifier at > least as important as data= ? :-) And
> remember, metadata is typically considered optional.
>
> I would still argue it is the same type (e.g. in my example) used in=
> different contexts (e.g. via ontological object property relationshi= ps),
> which provides it with more context, mae it data and metadata in the= first
> place - correspondingly until now I did not understood metadata as s= pecific
> subset of all types.... like unit32 and unit32-metadata.
>
> You made me become more neutral on this point, with a slight favor o= f not
> creating redundant IE types for metadata and data, but I am starting= to
> understand your point better.
>
> =E2=80=94
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/66#= issuecomment-352296625>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AJgkSZeZcCkMqF= ppKT31ZXLRUcPtqH-Wks5tBarTgaJpZM4Q8hpR>
> .
>



--
regards,
John

&m= dash;
You are receiving this because you commented.
Reply to th= is email directly, view it on GitHub, or mute the thread.3D""=

----==_mimepart_5a381a8dd4c8d_1b3923fea1a588f381262eb-- From nobody Mon Dec 18 11:52:21 2017 Return-Path: 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 09D7F1277BB for ; Mon, 18 Dec 2017 11:52:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.152 X-Spam-Level: * X-Spam-Status: No, score=1.152 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 ff9RfuHsDRRu for ; Mon, 18 Dec 2017 11:52:20 -0800 (PST) Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 11D25120454 for ; Mon, 18 Dec 2017 11:52:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mPCMmc/cp99UnDY0YIY5dW4/j48=; b=sDrHim7E5dRFj6RR dIpmXREEzm/c2fDg3MTZlQh+CQb5Ip2wPiWz2foLm6iP3rt+28LNRiDEhIeDF44C DNE6S4BaOYrFQsXOUu3f5/mTg8OmZwIMboFVeK6EPkSbVLbh2lm79LsH94QnFhOm hvSTLr3rCIADBhbnZ5ij+lvKah4= Received: by filter0081p1las1.sendgrid.net with SMTP id filter0081p1las1-1559-5A381C72-22 2017-12-18 19:52:18.714411242 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id H46DhiLGRr2QSuIe8zyALA for ; Mon, 18 Dec 2017 19:52:18.665 +0000 (UTC) Date: Mon, 18 Dec 2017 19:52:19 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a381c7272628_7db93febbc378f382692a6"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H8tD+B9D76akcmZzbLIWs+vJYNIz6t2oGz2das1L6Kff1Rxu+TL2OgmBkj 2IYdDFGndk7S0RykP4ZWo+6VX6YIBOwdDTQpUKU3wYjCkn4y+m8F5tnoME+MNJs3qnkr6FJaHbdJv1 0oWabRzwfXCRVCJCE80FoY6qYNAwSosDLiFyJTDOml0fk1IwAZTvz9izLA== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization (#74) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 19:52:21 -0000 ----==_mimepart_5a381c7272628_7db93febbc378f382692a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok, then the definition would be changed to ```The description of the distinctive nature of a target endpoint, that is based on its characteristics``` from ```The description of the distinctive nature of an endpoint, that is based on its characteristics.``` -- 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-terminology/issues/74#issuecomment-352539220 ----==_mimepart_5a381c7272628_7db93febbc378f382692a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ok, then the definition would be changed to The description of the= distinctive nature of a target endpoint, that is based on its characterist= ics from The description of the distinctive nature of an endpo= int, that is based on its characteristics.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a381c7272628_7db93febbc378f382692a6-- From nobody Mon Dec 18 11:53:45 2017 Return-Path: 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 B2252124319 for ; Mon, 18 Dec 2017 11:53:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.57 X-Spam-Level: X-Spam-Status: No, score=0.57 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=0.7, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 m30SMDWb0O0E for ; Mon, 18 Dec 2017 11:53:43 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 10267120454 for ; Mon, 18 Dec 2017 11:53:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Q/4eBncqUt86rWlURWCGqEGgwTQ=; b=HZEzjzpVdxzKHh07 mLWXqdefrqHDGiIzWmTpHBLYGUIcN97rji35PZ0/Pn0FRgOtx2Ei06eb2LYCf3gn u0/W7lL9RmNDabZsP9/D3leE53UGSk3Ja/3UEwhpflk4mFaqHlB1nqUp+LbRfpYu gR6/beQh0J4AgeGarm05qZMXcxI= Received: by filter0157p1las1.sendgrid.net with SMTP id filter0157p1las1-27412-5A381CC5-28 2017-12-18 19:53:41.627847714 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0016p1iad2.sendgrid.net (SG) with ESMTP id 2OMj6OB1RRervkRocTcI4w for ; Mon, 18 Dec 2017 19:53:41.418 +0000 (UTC) Date: Mon, 18 Dec 2017 19:53:41 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a381cc543d1f_78b13fd78aac0f3436448"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9HztgXJ84/fr16DU24e7IgJKhU4nJOGc/UrPYELM+uFJJhaEyKvKI570xJe apmnS8z6gzPBG3ejIb9OSePw5S3VYcNFdbw9MvGcg80aJOcAVHiiHQbWt9fOD0HhXTO/PIbcGp9V1H Mw/SPt6kAflHqoVE6+RVeZb19KW+PBYt9uyci6CFCCt5wbHMuPS733rYRQ== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Characterization Task (#75) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 19:53:44 -0000 ----==_mimepart_5a381cc543d1f_78b13fd78aac0f3436448 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok. -- 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-terminology/issues/75#issuecomment-352539585 ----==_mimepart_5a381cc543d1f_78b13fd78aac0f3436448 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Ok.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a381cc543d1f_78b13fd78aac0f3436448-- From nobody Mon Dec 18 11:57:22 2017 Return-Path: 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 5D2D712D854 for ; Mon, 18 Dec 2017 11:57:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.152 X-Spam-Level: * X-Spam-Status: No, score=1.152 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 8YENHtYRkHIR for ; Mon, 18 Dec 2017 11:57:19 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 59F5B124319 for ; Mon, 18 Dec 2017 11:57:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=susEXdMh8H/vSuoeYSgXIo8VKWk=; b=HVE2JkrER/xJ94/b qNNCQLDUQUD/6pppTqzeoKMeVM6rPKRhnIoXxXpk8igPm2h9iCMpWvCdQ6wmM6Mz Ipvztkp/YsEpBGLm0ZOqJ9E7hmfbie9FTRuhhU23uEm6+AhMlHvi7tDGO5txIcrX iOfxa8Gu54DvHe3dy9DydYkV7o0= Received: by filter0597p1las1.sendgrid.net with SMTP id filter0597p1las1-22557-5A381D9D-13 2017-12-18 19:57:17.99441151 +0000 UTC Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0010p1iad2.sendgrid.net (SG) with ESMTP id GdQsWM_fRYKxalFn-CqJYg for ; Mon, 18 Dec 2017 19:57:18.083 +0000 (UTC) Date: Mon, 18 Dec 2017 19:57:18 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a381d9dc816c_197e3fea407cef3833175"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1ad/u2TIJNtS8GEJFqaGAG1DnuOnyFxef86ZCJaoRr79FlNFfqNUerbLH EHn068esgFTjCLbPwCHWhlKsbDk3S4wVqtSGV3bCwdHi2k8/S3HsGUjeW5JEQl725UMbCPgwfiLU2/ q3xwlINmdt7ymAZqfPqhvOiTFQ29QLXOaMVfpV81IeZxGKSgcHGU2Ina4w== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Discovery Task (#77) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 19:57:21 -0000 ----==_mimepart_5a381d9dc816c_197e3fea407cef3833175 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Would this, being a task, also be moved to the architecture draft per response to one of the other "task" items? -- 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-terminology/issues/77#issuecomment-352540531 ----==_mimepart_5a381d9dc816c_197e3fea407cef3833175 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Would this, being a task, also be moved to the architecture draft per response to one of the other "task" items?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a381d9dc816c_197e3fea407cef3833175-- From nobody Mon Dec 18 12:03:17 2017 Return-Path: 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 199AF12D86A for ; Mon, 18 Dec 2017 12:03:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.818 X-Spam-Level: X-Spam-Status: No, score=-3.818 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, 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 EsUsKEZjJHAH for ; Mon, 18 Dec 2017 12:03:10 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [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 493E512422F for ; Mon, 18 Dec 2017 12:03:10 -0800 (PST) Date: Mon, 18 Dec 2017 12:03:09 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513627389; bh=S6MFvj6NWCzo/WsKqj0aajQDJ1UGpu/KdQ8HxF9jmk0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0wT1OhT8z7SnT8JL6hkONxqpEwwUAkcndIVQXLI3pJX/gsZt0pT4J9sMcpynFibfd oBEOLUoIKqt2dhc4wnI0Dei8KMjrOV+z0GLqOE0HNuNPlp7QWeiV1Ew2F8ZybaOMqa 07n3kiEPWvvp4Lebz2tDWtO+2G8SSuTzP7dNpr90= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a381efd5c786_72a33fb92ce9ef38417ec"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Label (#79) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:03:16 -0000 ----==_mimepart_5a381efd5c786_72a33fb92ce9ef38417ec Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Ok, then from your perspective this is a necessary term. Then, I would propose an update to the definition where Target Endpoint Label ```is an endpoint label that identifies a specific target endpoint``` and call it good. Thoughts? -- 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-terminology/issues/79#issuecomment-352542186 ----==_mimepart_5a381efd5c786_72a33fb92ce9ef38417ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Ok, then from your perspective this is a necessary term. Then, I would= propose an update to the definition where Target Endpoint Label is= an endpoint label that identifies a specific target endpoint and = call it good. Thoughts?

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a381efd5c786_72a33fb92ce9ef38417ec-- From nobody Mon Dec 18 12:08:31 2017 Return-Path: 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 A8DBC12422F for ; Mon, 18 Dec 2017 12:08:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.171 X-Spam-Level: * X-Spam-Status: No, score=1.171 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 vOTrpDQlL_5R for ; Mon, 18 Dec 2017 12:08:28 -0800 (PST) Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 CF2E41205D3 for ; Mon, 18 Dec 2017 12:08:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=yI4OM+iHzCS4dpBlRS1yuJOSNug=; b=ONZqpP48yUlz1kX4 JOQ7EYYyc3hq/0Tox4+zpPLjC20XvltDA7D5OStFGOlj7bTIxOu+UyqY76mQuI/j b0YyRD5F9yefQPPrkJrRzDjkr2M4IJ6wh4fp/Hp4tsiuMFrgYsFv1kOadkX0Okqj iaFBgtrjGAEWUXXukrHd03g4oug= Received: by filter0357p1iad2.sendgrid.net with SMTP id filter0357p1iad2-5415-5A38203A-2E 2017-12-18 20:08:26.866453826 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0008p1iad1.sendgrid.net (SG) with ESMTP id _c3s19BZSimFi3bbI8QcUA for ; Mon, 18 Dec 2017 20:08:26.747 +0000 (UTC) Date: Mon, 18 Dec 2017 20:08:26 +0000 (UTC) From: Henk Birkholz Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a38203a9c5fa_caf3fa6461b6f30128983"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: henkbirkholz X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H1omiGAsJjtgi6gRcadZdGRYkYCCEI1rSsecnVHbiQXsL9sZxjN/vpb4Qt Kq6jO1hiu89SSCKdFGeNDRuiHuPnOnufQgZp225fXfwRepMRJBdBXMcTB8L7DFFs0oJT+ZffbuJBBl m2w+z3SKxcuu+g6w0TjIybQPnzUKcfD+WSN47KGd9C7DJGfRrhClPrrR0A== Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Target Endpoint Discovery Task (#77) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:08:29 -0000 ----==_mimepart_5a38203a9c5fa_caf3fa6461b6f30128983 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit As with other task descriptions, a concise definition will be part of the terminology document, but every detailed illustration of tasks belongs into the architecture document. -- 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-terminology/issues/77#issuecomment-352543444 ----==_mimepart_5a38203a9c5fa_caf3fa6461b6f30128983 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

As with other task descriptions, a concise definition will be part of th= e terminology document, but every detailed illustration of tasks belongs in= to the architecture document.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a38203a9c5fa_caf3fa6461b6f30128983-- From nobody Mon Dec 18 12:13:46 2017 Return-Path: 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 7FED21205D3 for ; Mon, 18 Dec 2017 12:13:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.818 X-Spam-Level: X-Spam-Status: No, score=-3.818 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.282, HTML_MESSAGE=0.001, 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 9LGGfGU3gxc1 for ; Mon, 18 Dec 2017 12:13:43 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8FD2124319 for ; Mon, 18 Dec 2017 12:13:39 -0800 (PST) Date: Mon, 18 Dec 2017 12:13:38 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513628018; bh=ZlvKXEhZw3XsCOesNM4v96J6Y9BnEgh4XHk/cXqNf/I=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Xb7qJAjZYkD5Axugv/3IIUk6cFldg1Q6+VO0jDQ3N5guE0EVpP0h4403RMKpx48qb cJtiLzxdKquHTyuXedX9/5ZKAimspbUNS5NXMyQaA6go3tD3OqH6e26BFQgD+6JCaI pYern1gS/E8wGXCFZa4G1EdOXtX5Zu5GspeCD06s= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a382172f0387_a703fbd4e556f2c2826a3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Proposing a new approach to state and configuration (#63) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:13:44 -0000 ----==_mimepart_5a382172f0387_a703fbd4e556f2c2826a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Then the proposal would be to bring back SACM Function and clean up state/configuration, possibly by adopting some terminology from I-D.ietf-netmod-revised-datastores: intended, dynamic, system, learned and default configuration. ?? -- 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-terminology/issues/63#issuecomment-352544729 ----==_mimepart_5a382172f0387_a703fbd4e556f2c2826a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Then the proposal would be to bring back SACM Function and clean up st= ate/configuration, possibly by adopting some terminology from I-D.ietf-ne= tmod-revised-datastores: intended, dynamic, system, learned and default c= onfiguration. ??

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a382172f0387_a703fbd4e556f2c2826a3-- From nobody Mon Dec 18 12:17:52 2017 Return-Path: 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 D3B5B124239 for ; Mon, 18 Dec 2017 12:17:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.596 X-Spam-Level: X-Spam-Status: No, score=0.596 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 CNEWT4N-920H for ; Mon, 18 Dec 2017 12:17:50 -0800 (PST) Received: from o9.sgmail.github.com (o9.sgmail.github.com [167.89.101.2]) (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 E7C93120046 for ; Mon, 18 Dec 2017 12:17:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=koRLp/KoydYRbdaMltxqLUdpWF4=; b=r7kY78VjAS03lBW2 AOoAp6X0oqetV6omYrSjewKgMpZhrnlGNIE2Sg0aGfs+R8VWiDYQlJFvjQ/wwZxS u+pkO+m13fDYqBTfS1ItKyJlVyEmu1n2nnQfb8M4ZyLyBRMkxBEm6Qa6L4ntGGsU YD19lGj8UNYGn9Hxs8KkgGgLT6w= Received: by filter0490p1iad2.sendgrid.net with SMTP id filter0490p1iad2-23254-5A38226C-3C 2017-12-18 20:17:48.845160838 +0000 UTC Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id CFf9OvQxTZmMFkTtz5fhDA for ; Mon, 18 Dec 2017 20:17:48.731 +0000 (UTC) Date: Mon, 18 Dec 2017 20:17:48 +0000 (UTC) From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a38226ca2083_34023fdbf087ef2c538f1"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org X-SG-EID: UtArl2HfP/Y+1oZ8SNY9H0vwK/pJm0gjF8ubUJ3pW9ox9sfhnAs809xayvkuJtTbm6QZvtru0RXi1Z yeug7Laf+Sk5eCbZ081Nb915sgJAj91gS92yev0JMV+Rb4hXYpIasvGs/NwT4jtise17OCCPU9lXBk iwnzLnJcdKcct7xa0u8baO5xPlZN0wY7otLD4EdHp9pHE0byxK/o4RCg6kW6eYhQXmup2vegNhazH6 8= Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Do we really need to define timestamps? (#80) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:17:51 -0000 ----==_mimepart_5a38226ca2083_34023fdbf087ef2c538f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If we need to define these and point to 4949 there's nothing wrong with that. I only observed that the 4949 definition of timestamp actually provides the definition for two specializations. If we're ok with "timestamps", that's probably fine. It just seems that in some cases we're trying very hard to be semantically precise, and in others not so much - I'm trying to understand how we choose. -- 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-terminology/issues/80#issuecomment-352545731 ----==_mimepart_5a38226ca2083_34023fdbf087ef2c538f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If we need to define these and point to 4949 there's nothing wrong with = that. I only observed that the 4949 definition of timestamp actually provid= es the definition for two specializations. If we're ok with "timestamps", t= hat's probably fine. It just seems that in some cases we're trying very har= d to be semantically precise, and in others not so much - I'm trying to und= erstand how we choose.

&mda= sh;
You are receiving this because you are subscribed to this thread.<= br />Reply to this email directly, view it on GitHu= b, or mute the thread.3D""

= ----==_mimepart_5a38226ca2083_34023fdbf087ef2c538f1-- From nobody Mon Dec 18 12:21:11 2017 Return-Path: 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 2AFCC12D882 for ; Mon, 18 Dec 2017 12:21:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.374 X-Spam-Level: X-Spam-Status: No, score=-4.374 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=0.726, HTML_MESSAGE=0.001, 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 66RS5AlUu84j for ; Mon, 18 Dec 2017 12:21:08 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext7.iad.github.net [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 6202F12D881 for ; Mon, 18 Dec 2017 12:20:55 -0800 (PST) Date: Mon, 18 Dec 2017 12:20:54 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513628454; bh=IgmDz74o84iksnL0xeKzuD2SAr8YVHhzdCQo50jrpk4=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rR5al52etwbrBQmXR75DXDyUDR3uq4iuU4qTW9IRpdl9AWwmhpWXDo6d5H0o+zgtP PLXnEpSnCrBML0orqIneNXtBcgpqii2+pNgqBWMLoCE7CBZU1MaMHqjh6qszP7aDRQ pQ6aF3O4af3XeQmGMa5NWv1eZQLrqJgANXtuIJR0= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a3823269aa98_4883fa142336f301228bd"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:21:10 -0000 ----==_mimepart_5a3823269aa98_4883fa142336f301228bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The new wording does not imply that atomic is part of the 5209 description; to the contrary, it is describing the difference. In terms of adding contextual information back, we can probably do that. I'd prefer to keep the context separate from the definition proper with a paragraph break, if that's what we choose to do. -- 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-terminology/issues/62#issuecomment-352546476 ----==_mimepart_5a3823269aa98_4883fa142336f301228bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The new wording does not imply that atomic is part of the 5209 descrip= tion; to the contrary, it is describing the difference.

In terms of adding contextual information back, we can probably do tha= t. I'd prefer to keep the context separate from the definition proper wit= h a paragraph break, if that's what we choose to do.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a3823269aa98_4883fa142336f301228bd-- From nobody Mon Dec 18 12:23:13 2017 Return-Path: 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 EC5D312D94E for ; Mon, 18 Dec 2017 12:23:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.099 X-Spam-Level: X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, 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 TIVAY8hoVgoA for ; Mon, 18 Dec 2017 12:23:10 -0800 (PST) Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ECAC12D889 for ; Mon, 18 Dec 2017 12:23:05 -0800 (PST) Date: Mon, 18 Dec 2017 12:23:04 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1513628585; bh=uN3Rd6a2TOLPUfbqykzcslzs092XnmBG1emvVPtOrC8=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=j5q4TqDkMHYRuBBiJ6aAFBNVWNoGDYfnybTCwH3mQoYhvS0ZV/LFVvlbMf6YW0e2T cfBT777m9OGAkIBRKrGrcIbuRmXRWC/UjiswAWI/IuXYQDo+0xvlMXy+vEYz4CpFRP qMvZzQLi8kAcNi7JQFw5J/51A7cfzUrhSrOeGn+Y= From: adammontville Reply-To: sacmwg/draft-ietf-sacm-terminology To: sacmwg/draft-ietf-sacm-terminology Cc: Subscribed Message-ID: In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a3823a8f11b5_598b3fd3202e4f2c7697b"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: adammontville X-GitHub-Recipient: sacm X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: sacm@ietf.org Archived-At: Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Propose to remove Interaction Model from terminology (#65) X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2017 20:23:12 -0000 ----==_mimepart_5a3823a8f11b5_598b3fd3202e4f2c7697b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit If we're keeping it, do we mind segregating the definition from the exposition? > The definition of specific sequences regarding the exchange of messages (data in motion), including, for example, conditional branching, thresholds and timers. >An interaction model, for example, can be used to define operations, such as registration or discovery, on the control plane. A composition of data models for data in motion and a corresponding interaction model is a protocol. -- 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-terminology/issues/65#issuecomment-352547018 ----==_mimepart_5a3823a8f11b5_598b3fd3202e4f2c7697b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If we're keeping it, do we mind segregating the definition from the ex= position?

The definition of specific sequences regarding the exchange of message= s (data in motion), including, for example, conditional branching, thresh= olds and timers.

An interaction model, for example, can be used to define operations, s= uch as registration or discovery, on the control plane. A composition of = data models for data in motion and a corresponding interaction model is a= protocol.

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it = on GitHub, or mute the thre= ad.3D""

= ----==_mimepart_5a3823a8f11b5_598b3fd3202e4f2c7697b-- From nobody Tue Dec 19 07:14:18 2017 Return-Path: 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 02F2E12704A for ; Tue, 19 Dec 2017 07:14:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_KAM_HTML_FONT_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mitre.onmicrosoft.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ID66LpA3UaH3 for ; Tue, 19 Dec 2017 07:14:13 -0800 (PST) Received: from smtpvmsrv1.mitre.org (smtpvmsrv1.mitre.org [192.52.194.136]) by ietfa.amsl.com (Postfix) with ESMTP id 0E31A120727 for ; Tue, 19 Dec 2017 07:14:12 -0800 (PST) Received: from smtpvmsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 67BB213BCF9 for ; Tue, 19 Dec 2017 10:14:12 -0500 (EST) Received: from imshyb01.MITRE.ORG (imshyb01.mitre.org [129.83.29.2]) by smtpvmsrv1.mitre.org (Postfix) with ESMTP id 400D76C0011 for ; Tue, 19 Dec 2017 10:14:12 -0500 (EST) Received: from imshyb02.MITRE.ORG (129.83.29.3) by imshyb01.MITRE.ORG (129.83.29.2) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 19 Dec 2017 10:14:12 -0500 Received: from gcc01-dm2-obe.outbound.protection.outlook.com (10.140.19.249) by imshyb02.MITRE.ORG (129.83.29.3) with Microsoft SMTP Server (TLS) id 15.0.1263.5 via Frontend Transport; Tue, 19 Dec 2017 10:14:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitre.onmicrosoft.com; s=selector1-mitre-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=uU1cCPmIGcpnmt7KVprNbqzmmhWZo8SQ35PBTqEWKNU=; b=GLushhsm2ymEm3lodQ+9XM5Vwc13pY4SIjdjiB+2whJMvLe2yjQ62nylBU/0e5TVQRixj1OcGmF1xhKI3kG6qCVe7dzyBVNwFf2lmU3cfZ4SOmispaMcu578gthNr7Z+1OFf+/EY49gOGUNOtmd28PUtXlEF9CYTjSh0IODlbgc= Received: from DM5PR0901MB2197.namprd09.prod.outlook.com (10.167.106.167) by DM5PR0901MB2197.namprd09.prod.outlook.com (10.167.106.167) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.323.15; Tue, 19 Dec 2017 15:14:10 +0000 Received: from DM5PR0901MB2197.namprd09.prod.outlook.com ([fe80::89ec:29fa:9272:a635]) by DM5PR0901MB2197.namprd09.prod.outlook.com ([fe80::89ec:29fa:9272:a635%13]) with mapi id 15.20.0323.018; Tue, 19 Dec 2017 15:14:10 +0000 From: "Haynes, Dan" To: "sacm@ietf.org" Thread-Topic: FEEDBACK REQUESTED: ECP Diagrams Thread-Index: AdN4Lmn74FyoN9yaTVaYp5nSoQjt/A== Date: Tue, 19 Dec 2017 15:14:10 +0000 Message-ID: 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=dhaynes@mitre.org; x-originating-ip: [192.160.51.89] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DM5PR0901MB2197; 6:9cOc4NrTd6g9+BIq5OQl2Y/KCWouGegZq4bP1X/5Ff2pEGVFcyDFxdoi//iBeQTpPC8HO+79GymNUgjPWoVaH+SnERhizATKJnJaOub1N88oEFErwjfxa3nH9OGnUno9hwYeG0W8VZzBC79fCHuso6PRnYoCIsG940Jo3MNXHJko5884DLqnbvPIEX1MH+YHt9poDmZizrPmL0TzGTk4SjvdsKIIVGhL2bTxgc++oqeDV4eZCzmhNwchGBTy5oYUHL9P95PVTVgAnA8mss28YLFBbl1Uur2gsQt/I2HA56n0Uu0jfQIEKXlqXcovUgbdvA4PiLQyrcMZe/aQjslUL79XBg7in3eb1bWo63qlCrY=; 5:PTx83PzI0xPFc7hi6Dz45sx61TByxuPBI0iLfilsU1a/qfw8dYC+RqBnGelO7stPosTTLXu19ryb31Srv5CkgTOn+0v3xD72Rkfy+ziagEqHvI7hXtbpTZbhLlQ4jfXj4JQfPyy1s1fWlC8N/IIO2vKs6VifTk/JxBwujnOn+dk=; 24:PjgkDcRq1Cqd4DYB0m9S5rP0RgtSkDz4K+Rzqea/bHzHGNUqR9c6F9HTU+N2v70uBgeZTWSMlBBsjAuGdFtc03lp03hfMTl6EuuTS5ylAHk=; 7:tcf2HNNTZ/yET25fGdlJ9GOAV3SZ0txBSTIJ/uDeeyzaYkxZQiC2NYyur57KEnChPiMmJ2QjmtmwZMFFs0K6+7nOSRJ9m8efSGoH6wUG/uFIKQzOGTVI/vlsVRnqFDSMODN3lsuu8cRtltRT6fUTPoFTgIslwy7fngUtbJIP3eyWcMhwr71B/XCuG0o5NdtfurW3ZM9e62g1RsWFZfuV/DGLoqL/cYL5z2hmx0t+rUwmtXV2xbe7KBYEGstbX8cg x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 635146db-2929-41c8-83cc-08d546f327df x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603307); SRVR:DM5PR0901MB2197; x-ms-traffictypediagnostic: DM5PR0901MB2197: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(120809045254105)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231023)(3002001)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(20161123558100)(6072148)(201708071742011); SRVR:DM5PR0901MB2197; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:DM5PR0901MB2197; x-forefront-prvs: 052670E5A4 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(39860400002)(346002)(366004)(76104003)(199004)(189003)(53754006)(5660300001)(6506007)(7736002)(97736004)(106356001)(81166006)(790700001)(3846002)(102836003)(59450400001)(6116002)(6916009)(14454004)(8676002)(316002)(3660700001)(33656002)(1730700003)(105586002)(2351001)(74316002)(25786009)(81156014)(2501003)(53946003)(16200700003)(66066001)(3280700002)(86362001)(53936002)(9686003)(54896002)(2906002)(6306002)(99286004)(68736007)(7696005)(5250100002)(478600001)(2900100001)(9326002)(55016002)(5640700003)(966005)(8936002)(5630700001)(6436002)(569006); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR0901MB2197; H:DM5PR0901MB2197.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: mitre.org does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_DM5PR0901MB21977BE1268BF2D3A4A9B3A4A50F0DM5PR0901MB2197_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 635146db-2929-41c8-83cc-08d546f327df X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Dec 2017 15:14:10.1187 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: c620dc48-1d50-4952-8b39-df4d54d74d82 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR0901MB2197 X-OriginatorOrg: mitre.org X-MITRE: 8GQsMWxq66rxk57w Archived-At: Subject: [sacm] FEEDBACK REQUESTED: ECP Diagrams X-BeenThere: sacm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SACM WG mail list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 15:14:16 -0000 --_000_DM5PR0901MB21977BE1268BF2D3A4A9B3A4A50F0DM5PR0901MB2197_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Everyone, Sorry for the delay on this, but, we had an action item to draw up some dia= grams for ECP based on the WG discussion at the September Virtual Interim M= eeting [1][2]. I have included the diagrams below :). The first three show the current NETCONF/YANG architecture, NEA architectur= e, and ECP diagram. After that, there is the revised ECP diagram which was = proposed at the meeting and two alternate diagrams that were created based = on discussion during that meeting. Please let us know what you think about the different options good and bad = so that we can work together to come up with a diagram that makes the most = sense for the group. Also, let me know if you have any questions. Thanks, Danny [1] https://datatracker.ietf.org/meeting/interim-2017-sacm-03/materials/min= utes-interim-2017-sacm-03-201709260900/ (see pages 7-9) [2] https://datatracker.ietf.org/meeting/interim-2017-sacm-03/materials/sli= des-interim-2017-sacm-03-sessa-ecp/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +----------------------------+ |Server (device) | | +--------------------+ | | | configuration | | +----+ | | ---------------| | |YANG|+ | | m d state data | | |mods||+ | | e a ---------------| | +----+|| -----> | t t notifications | | +----+| | | a a ---------------| | +----+ | | operations | | | +--------------------+ | | ^ | | | | | v | +------+ | +-------------+ | | | -------------> | | | |Client| | | NETCONF | | | (app)| | | engine | | | | <------------ | | | +------+ +-------------+ | | / \ | | / \ | | / \ | | +--------+ +---------+ | | | config | |system |+ | | | data- | |software ||+ | | | base | |component||| | | +--------+ +---------+|| | | +---------+| | | +---------+ | +----------------------------+ Figure 1: NETCONF/YANG Architecture (RFC622, Section 3.1) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +-------------+ +--------------+ | Posture | <--------PA--------> | Posture | | Validators | | Collectors | | (1 .. N) | | (1 .. N) | +-------------+ +--------------+ | | | | | | +-------------+ +--------------+ | Posture | | Posture | | Broker | <--------PB--------> | Broker | | Server | | Client | +-------------+ +--------------+ | | | | +-------------+ +--------------+ | Posture | | Posture | | Transport | <--------PT--------> | Transport | | Server | | Client | | (1 .. N) | | (1 .. N) | +-------------+ +--------------+ NEA SERVER NEA CLIENT Figure 2: NEA Architecture =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Server Endpoint +---------------+ +---------------+ | | | | | +-----------+ | | +-----------+ | | | Posture | | | | Posture | | | | Validator | | | | Collector | | | +-----------+ | | +-----------+ | | | | | | | | | | | | | Repository | | | | | | +--------+ | +-----------+ | | +-----------+ | | | | | Posture | | | | Posture | | | |<------->| | Server | | | | Client | | | | | +-----------+ | | +-----------+ | | | | | | | | | | | | | | | | | +--------+ | | | | | | | | | | | | | +-----------+ | | +-----------+ | | | Comms | | | | Comms | | | | Server | |<------>| | Client | | | +-----------+ | | +-----------+ | | | | | +---------------+ +---------------+ Figure 3: Current ECP Diagram =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Posture Manager Endpoint Orchestrator Repository +---------------+ +---------------+ +--------+ +--------+ | | | | | | | | | +-----------+ | | +-----------+ | | |<---->| | | | Posture | | | | Posture | | | | pub/ | | | | Validator | | | | Collector | | | | sub | | | +-----------+ | | +-----------+ | +--------+ | | | | | | | | | | | | | | | | Evaluator | | | | | | | | +------+ | | | +-----------+ |<-------| +-----------+ | | | | | | | Posture | | report | | Posture | | | | | | | | Collection| | | | Collection| | | |<-----> | |<-----| | Manager | | query | | Engine | | | |request/| | store| +-----------+ |------->| +-----------+ | | |respond | | | | | | | | | | | | | | | | | | +---------------+ +---------------+ +------+ +--------+ Figure 4: Proposed ECP Diagram (Option 1) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Posture = Manager Endpoint Orchestrator +---------------+ +---------------+ +--------+ | | | | | | | +-----------+ | | +-----------+ | | |<---->| | Posture | | | | Posture | | | | pub/ | | Validator | | | | Collector | | | | sub | +-----------+ | | +-----------+ | +--------+ | | | | | | | | | | | | Evaluator Repository | | | | | | +------+ +--------+ | +-----------+ |<-------| +-----------+ | | | | | | | Posture | | report | | Posture | | | | | | | | Collection| | | | Collection| | | |<-----> | |<-----| | Manager | | query | | Engine | | | |request/| | store| +-----------+ |------->| +-----------+ | | |respond | | | | | | | | | | | | | | +------+ +--------+ +---------------+ +---------------+ Figure 5: Alternate Diagram Based on WG Discussion (Option 2) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Orchestrator +-----------------------------------------------+ | | | | +-----------------------------------------------+ ^ ^ ^ |pub/sub |pub/sub |pub/sub | | | V v v Evaluator Repository Posture Manager Endpoint +------+ +--------+ +---------------+ +---------------+ | | | | | | | | | | | | | +-----------+ | | +-----------+ | | | | | | | Posture | | | | Posture | | | | | | | | Validator | | | | Collector | | | | | | | +-----------+ | | +-----------+ | | | | | | | | | | | | |<------>| |<-----| | | | | | | |request/| |store | | | | | | | |respond | | | +-----------+ |<-------| +-----------+ | | | | | | | Posture | | report | | Posture | | | | | | | | Collection| | | | Collection| | | | | | | | Manager | | query | | Engine | | | | | | | +-----------+ |------->| +-----------+ | | | | | | | | | | | | | | | | | | | | | +---------------+ +---------------+ +------+ +--------+ Figure 6: Alternate Diagram Based on WG Discussion (Option 3) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --_000_DM5PR0901MB21977BE1268BF2D3A4A9B3A4A50F0DM5PR0901MB2197_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Everyone,


Sorry for the delay on this, but, we had an action item to draw up some dia= grams for ECP based on the WG discussion at the September Virtual Interim M= eeting [1][2]. I have included the diagrams below :).

 

The first three show the current NETCONF/Y= ANG architecture, NEA architecture, and ECP diagram. After that, there is t= he revised ECP diagram which was proposed at the meeting and two alternate = diagrams that were created based on discussion during that meeting.

 

Please let us know what you think about th= e different options good and bad so that we can work together to come up wi= th a diagram that makes the most sense for the group.

 

Also, let me know if you have any question= s.

 

Thanks,

Danny

 

[1] https://datatracker.ietf.org/meeting/i= nterim-2017-sacm-03/materials/minutes-interim-2017-sacm-03-201709260900/ (s= ee pages 7-9)

[2] https://datatracker.ietf.org/meeting/i= nterim-2017-sacm-03/materials/slides-interim-2017-sacm-03-sessa-ecp/

&= nbsp;

=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

 =             &nb= sp;         +------------------= ----------+

 =             &nb= sp;         |Server (device) &= nbsp;           |

 =             &nb= sp;         |    = 3;--------------------+  |

 =             &nb= sp;        |    |&nb= sp;     configuration |  |

 =           +----+=      |    |     ----= -----------|  |

 =           |YANG|+&nb= sp;   |    | m d  state data   = ; |  |

 =           |mods||+&nb= sp;  |    | e a ---------------|  |

 =           +----+|= | -----> | t t  notifications |  |

 =            +----= +|   |    | a a ---------------|  |<= /o:p>

 =             = 3;----+   |    |     = operations    |  |

 =             &nb= sp;        |    += ;--------------------+  |

 =             &nb= sp;        |    = ;       ^      =           |<= /p>

 =             &nb= sp;        |    = ;       |      =           |<= /p>

 =             &nb= sp;        |    = ;       v      =           |<= /p>

 =    +------+       = ;   |     +-------------+  =       |

 =    |      | -------------> |&nbs= p;            | = ;       |

 =    |Client| <rpc>    |   = ;  |  NETCONF    |     &n= bsp;  |

 =    | (app)|        &= nbsp; |     |   engine    |&nb= sp;       |

 =    |      | <------------  = |             |=         |

 =    +------+ <rpc-reply>    += ;-------------+        |<= /span>

 =             &nb= sp;         |   &nbs= p;   /        \  &nb= sp;        |

 =             &nb= sp;         |   &nbs= p;  /          \ &nb= sp;        |

 =             &nb= sp;         |   &nbs= p; /            \&nb= sp;        |

 =             &nb= sp;         | +--------+&nb= sp;  +---------+   |

 =             &nb= sp;         | | config |  = ; |system   |+  |

 =             &nb= sp;         | |  data- | =   |software ||+ |

 =             &nb= sp;         | |   base |&= nbsp;  |component||| |

 =             &nb= sp;         | +--------+&nb= sp;  +---------+|| |

 =              &n= bsp;        |   &nbs= p;           +-------= --+| |

 =             &nb= sp;         |   &nbs= p;            +-= --------+ |

 =             &nb= sp;         +------------------= ----------+

&= nbsp;

Figure = 1: NETCONF/YANG Architecture (RFC622, Section 3.1)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /span>

    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
    |  Posture    |   <=
;--------PA-------->   |   Posture   =
 |
    |  Validators |     &=
nbsp;           &nbs=
p;        |   Collectors |
    |  (1 .. N)   |   &nb=
sp;            =
          |   (1 .. =
N)   |
    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
          |  &n=
bsp;            =
;            &n=
bsp;            =
; |
          |  &n=
bsp;            =
;            &n=
bsp;            =
; |
          |  &n=
bsp;            =
;            &n=
bsp;            =
; |
    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
    |   Posture   |  &nbs=
p;            &=
nbsp;          |   P=
osture    |
    |   Broker    |  =
; <--------PB-------->   |   Broker  &n=
bsp;  |
    |   Server    |  =
;            &n=
bsp;           | &nb=
sp; Client     |
    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
          |  &n=
bsp;            =
;            &n=
bsp;            =
; |
          |  &n=
bsp;            =
;             &=
nbsp;           &nbs=
p;|
    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
    |   Posture   |  &nbs=
p;            &=
nbsp;          |   P=
osture    |
    |   Transport |   <--------P=
T-------->   |   Transport  |
    |   Server    |  =
;            &n=
bsp;           | &nb=
sp; Client     |
    |   (1 .. N)  |   &nb=
sp;            =
          |   (1 .. =
N)   |
    +-------------+    &nbs=
p;            &=
nbsp;        +--------------+
 
       =
NEA SERVER           =
;            &n=
bsp;       NEA CLIENT

 

Figure = 2: NEA Architecture

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nbs= p;            &= nbsp;                  &n= bsp;            = ;            &n= bsp;            = ;  

 =  Server          &nb= sp;        Endpoint

          =       +---------------+  &n= bsp;     +---------------+

         &= nbsp;      |      &n= bsp;        |    &nb= sp;   |         &nbs= p;     |

         &= nbsp;      | +-----------+ |  &n= bsp;     | +-----------+ |

         &= nbsp;      | | Posture   | |  =       | | Posture   | |

         &= nbsp;      | | Validator | |   &nbs= p;    | | Collector | |

         &= nbsp;      | +-----------+ |  &n= bsp;     | +-----------+ |

         &= nbsp;      |      | =        |      &= nbsp; |      |      =   |

         &= nbsp;      |      | =        |      &= nbsp; |      |      =   |   

Repository      |  &= nbsp;   |        |  =       |      |  = ;      |    

+--------+      | += ;-----------+ |        | +------= -----+ |

|        |  &nb= sp;   | | Posture   | |     &n= bsp;  | | Posture   | |    

|        |ß---à| | Server    | |        |= | Client    | |

|        |  &nb= sp;   | +-----------+ |     &nbs= p;  | +-----------+ |   

|        |  &nb= sp;   |      |    &n= bsp;   |        |  &= nbsp;   |        |  =   

|        |  &nb= sp;   |      |    &n= bsp;   |        |  &= nbsp;   |        |<= /span>

+--------+      | = ;     |        |&nbs= p;       |      |&nb= sp;       |    

         &= nbsp;      |      |&= nbsp;       |     &n= bsp;  |      |     &= nbsp;  |

         &= nbsp;      | +-----------+ |  &n= bsp;     | +-----------+ |

         &= nbsp;      | | Comms     | |&n= bsp;       | | Comms     = | |

         &= nbsp;      | | Server    | |<---= --->| | Client    | |

         &= nbsp;      | +-----------+ |  &n= bsp;     | +-----------+ |

         &= nbsp;      |      &n= bsp;        |    &nb= sp;   |          &nb= sp;    |

   &nbs= p;            +-= --------------+        +--------= -------+

Figure = 3: Current ECP Diagram

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nbs= p;            &= nbsp;                  &n= bsp;            = ;            &n= bsp;            = ;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;      

  Posture Manager           &= nbsp;  Endpoint

Orchestrator    Repository  &n= bsp;   +---------------+     &nb= sp;  +---------------+

+--------+      +-= -------+      |     &= nbsp;         |   &n= bsp;    |        &nb= sp;      |

|        | &nbs= p;    |        |  &n= bsp;   | +-----------+ |     &nb= sp;  | +-----------+ |

|        |<----&g= t;|        |      | = | Posture   | |        | | Pos= ture   | |

|        | pub/ | &n= bsp;      |      | | Vali= dator | |        | | Collector | |<= /o:p>

|        | sub = |        |      | &= #43;-----------+ |        | +---= --------+ |

+--------+      | = ;       |      |&nbs= p;     |        |&nb= sp;       |      |&n= bsp;       |

         &= nbsp;      |      &n= bsp; |      |      | = ;       |      =   |      |      = ;  |   

Evaluator       | &n= bsp;      |      | &= nbsp;    |        | =        |      | = ;       |    
+------+        |  &nb= sp;     |      | +--------= ---+ |<-------| +-----------+ |

|      |   &nbs= p;    |        |  &n= bsp;   | | Posture   | | report | | Posture  = | |    

|      |   &nbs= p;    |        | &nb= sp;    | | Collection| |      =   | | Collection| |

|      |<-----> |  =       |<-----| | Manager   | | query&= nbsp; | | Engine    | |      &= nbsp;

|      |request/|  &= nbsp;     | store| +-----------+ |------->| = +-----------+ |   

|      |respond |   =      |      |   = ;            | =        |      &= nbsp;        |

|      |   &nbs= p;    |        |  &n= bsp;   |         &nb= sp;     |        |&n= bsp;            = ;  |    

|      |   &nbs= p;    |        |  &n= bsp;   +---------------+     &nb= sp;  +---------------+ 

+------+ =        +--------+    &= nbsp; 

Figure = 4: Proposed ECP Diagram (Option 1)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nbs= p;            &= nbsp;                  &n= bsp;            = ;            &n= bsp;            = ;  

     = ;           &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;P= osture Manager          &= nbsp;   Endpoint

         &= nbsp;    Orchestrator     +----= -----------+        +-----------= ----+

         &= nbsp;      +--------+   &nb= sp;  |          &nbs= p;    |        | &nb= sp;            = |

         &= nbsp;      |      &n= bsp; |      | +-----------+ |  &= nbsp;     | +-----------+ |

         &= nbsp;      |      &n= bsp; |<---->| | Posture   | |     =    | | Posture   | |

         &= nbsp;      |      &n= bsp; | pub/ | | Validator | |        | |= Collector | |

          =       |      &n= bsp; | sub  | +-----------+ |     &nb= sp;  | +-----------+ |

         &= nbsp;      +--------+   &nb= sp;  |      |     &n= bsp;  |        |   &= nbsp;  |        |=

         &= nbsp;           &nbs= p;          |   = ;   |        |  &nbs= p;     |      |  &nb= sp;     |   

Evaluator       Repositor= y      |      | &nbs= p;      |       = ; |      |      &nbs= p; |    

+------+      &nb= sp; +--------+      | +-----------+= ; |<-------| +-----------+ |

|      |   &nbs= p;    |        |  &n= bsp;   | | Posture   | | report | | Posture  = | |    

|      |   &nbs= p;    |        | &nb= sp;    | | Collection| |       = ; | | Collection| |

|      |<-----> |  =       |<-----| | Manager   | | query&= nbsp; | | Engine    | |      &= nbsp;

|      |request/|  &= nbsp;     | store| +-----------+ |------->| = +-----------+ |   

|      |respond |   =      |      |   = ;            | =        |      &= nbsp;        |

|      |   &nbs= p;    |        |  &n= bsp;   |         &nb= sp;     |        |&n= bsp;            = ;  |    

+------+      &nb= sp; +--------+      +---------------&#= 43;        +---------------+&nbs= p;

Figure 5: Alternate Diagram Based on WG Discussion (Option= 2)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nbs= p;            &= nbsp;                  &n= bsp;            = ;            &n= bsp;            = ;  

         &= nbsp;      Orchestrator

+-----------------------------------------------= 3;

|          = ;            &n= bsp;            = ;            |<= o:p>

|         =             &nb= sp;            =              |<= o:p>

+-----------------------------------------------= 3;

   ^       = ;         ^    =             &nb= sp;  ^

   |pub/sub     &nbs= p;   |pub/sub        &nbs= p;   |pub/sub

   |       = ;         |     = ;            &n= bsp; |

   V       = ;         v    =             &nb= sp;  v

 

Evaluator       Repositor= y        Posture Manager  &nbs= p;           Endpoint

+------+      &nb= sp; +--------+      +---------------&#= 43;        +---------------+

|      |   &nbs= p;    |        | &nb= sp;    |        &nbs= p;      |       = ; |            =    |

|      |   &nbs= p;    |        |  &n= bsp;   | +-----------+ |     &nb= sp;  | +-----------+ |

|      |    &nb= sp;   |        |  &n= bsp;   | | Posture   | |     &= nbsp;  | | Posture   | |

|      |   &nbs= p;    |        |  &n= bsp;   | | Validator | |       = ; | | Collector | |

|      |   &nbs= p;    |        |  &n= bsp;   | +-----------+ |     &nb= sp;  | +-----------+ |

|      |   &nbs= p;    |        | &nb= sp;    |      |   &n= bsp;    |        | &= nbsp;    |        |<= /o:p>

|      |<------>| &= nbsp;      |<-----|    &nbs= p; |        |    &nb= sp;   |      |    &n= bsp;   |

|      |request/|  &= nbsp;     |store |      | = ;       |      =   |      |      = ;  |  

|      |respond |  &= nbsp;     |      | +------= -----+ |<-------| +-----------+ |

|      |   &nbs= p;    |        |  &n= bsp;   | | Posture   | | report | | Posture  = | |    

|      |   &nbs= p;    |        | &nb= sp;    | | Collection| |      =   | | Collection| |

|      |   &nbs= p;    |        |  &n= bsp;   | | Manager   | | query  | | Engine &n= bsp;  | |       

|      |   &nbs= p;    |        | &nb= sp;    | +-----------+ |------->| +----------= -+ |   

|      |   &nbs= p;    |        |  &n= bsp;   |         &nb= sp;     |        |&n= bsp;            = ;  |

|      |   &nbs= p;    |        |  &n= bsp;   |         &nb= sp;     |        |&n= bsp;            = ;  |    

|      |   &nbs= p;    |        |  &n= bsp;   +---------------+     &nb= sp;  +---------------+ 

+------+      &nb= sp; +--------+     

Figure 6: Alternate Diagram Based on WG Discussion (Option= 3)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nbs= p;            &= nbsp;                  &n= bsp;            = ;            &n= bsp;            = ;  

 

 

   &nbs= p;            &= nbsp;    

 

 

 

--_000_DM5PR0901MB21977BE1268BF2D3A4A9B3A4A50F0DM5PR0901MB2197_--