IETF Logo Mail Archive

Re: [sacm] Comments on draft-ietf-sacm-ecp

Adam Montville <adam.w.montville@gmail.com> Tue, 24 April 2018 19:38 UTC

Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 284D1120727; Tue, 24 Apr 2018 12:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61AcJNlQqaeW; Tue, 24 Apr 2018 12:38:32 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 2D754124F57; Tue, 24 Apr 2018 12:38:32 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id o76so8409352pfi.5; Tue, 24 Apr 2018 12:38:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=mo660mLxxzeoFIRTZ9pA7VFDOI0Zcm3WTdwbY4sgxTs=; b=CkZcot/cWfFLqa/gU9R3Sq6u5Gdc7o8B2AC/Ug8UQDwkcVouHKwXDxXw9KylYeq60b HoQ+pOluE98JQWEYESoSootTE2bZ2mkOL6GmT8bNIOX8g4LFsU8DZ4kX4965k0s94mdo bODUraqU3d7iLuNWLECns0GcJnBhe0rrU2ptoA3sQdnFGG6oQrTkq072hRKX0NoRuqx3 YLF+O+I8C1uSHjuCzFCKYTk9tUWRiKrjwphLhGKlrLoRtnDDAH5ek1JMFw45r3o0KWrN tZ6EXg7Hb2BHmDFIa4cSjIVZslrNXk+lKBIB0+/2we68Kyw2OsTR63U5kt4uWSX5sc9x P2Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=mo660mLxxzeoFIRTZ9pA7VFDOI0Zcm3WTdwbY4sgxTs=; b=VSepj0ZaIgurSFkOKMKctBoe0YX9F7Va6qR1lsn2IhASWlQNtjEljHFFBRKrvDmKHE p7WuK7ht4BnpPr+NfiSXPHcXAJ31dTvcMPYorhYgQo59hxrDCi/aBKxKTpzeVJnVdVFe 1QdiqfrMWhe7Kb4Le0IRmAzCqymD82QmoLsWf9nNZ+otrHpQYs4Xvy5TLYj37vVnGmnA hL59yvAxBO7bIuG6GmtICBnHnYBBfWdJc9yQci4IuGOBKirA1GbbxyqJDbdY2LI4yeL3 bMyuEiOKTxfZgFtMLoAGDm+x3lEvAHs/PG03cXK8MPEUTsudi7qCx38tmmFGBJy42+ol paEg==
X-Gm-Message-State: ALQs6tA9KpFoV0e/hP5vffQwakVpokY79EY70Ug9TdkK6qdFotdduiel TYZspqLjlPZmb7TutuUSAMM=
X-Google-Smtp-Source: AIpwx48tTtCSuJndF0vOS6XG7TA6a7WLbUF2HCJlKzUsGRFHW4KBxsLIu1Vz9WZMNelheIRqr7F1Hg==
X-Received: by 2002:a17:902:6689:: with SMTP id e9-v6mr26554116plk.176.1524598711509; Tue, 24 Apr 2018 12:38:31 -0700 (PDT)
Received: from macbook-3.lan (99-64-100-131.lightspeed.austtx.sbcglobal.net. [99.64.100.131]) by smtp.gmail.com with ESMTPSA id t68sm1930892pgc.62.2018.04.24.12.38.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Apr 2018 12:38:30 -0700 (PDT)
From: Adam Montville <adam.w.montville@gmail.com>
Message-Id: <52C2F21E-DEEB-47BA-B59B-0FF5B1F120F0@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_98242403-96CA-456D-A1F1-083C1827F087"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 24 Apr 2018 14:38:28 -0500
In-Reply-To: <E9F0DAAC-F227-4CEA-8784-AEA187879398@gmail.com>
Cc: "draft-ietf-sacm-ecp@ietf.org" <draft-ietf-sacm-ecp@ietf.org>, "<sacm@ietf.org>" <sacm@ietf.org>
To: "Haynes Jr., Dan" <dhaynes@mitre.org>
References: <A9A78B93-981C-4857-AC35-CD38055DA55B@gmail.com> <DM5PR0901MB219737E3075D0C2C84E916D3A5A50@DM5PR0901MB2197.namprd09.prod.outlook.com> <AAC84E16-2518-45C7-9F5A-6092712526D6@gmail.com> <DM5PR0901MB2197CC362C2CAC788F806367A5A40@DM5PR0901MB2197.namprd09.prod.outlook.com> <E9F0DAAC-F227-4CEA-8784-AEA187879398@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/fiPJK_GTSMInVOmXo_dwrhD9Z_k>
Subject: Re: [sacm] Comments on draft-ietf-sacm-ecp
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Apr 2018 19:38:34 -0000

Danny,

Just an FYI that this stuff hasn't fallen off my radar. I have a bunch of paring down suggestions - I just need to translate them to an e-mail so they can be digested.

Adam

> On Apr 4, 2018, at 10:02 AM, Adam Montville <adam.w.montville@gmail.com> wrote:
> 
> 
> 
>> On Apr 4, 2018, at 9:49 AM, Haynes Jr., Dan <dhaynes@mitre.org <mailto:dhaynes@mitre.org>> wrote:
>> 
>> I think the ECP draft is less about compliance and more about collection, and it's specifically about agent-based (or in-built) collection capabilities based on NEA and extensions thereto - in other words, ECP begins to specify a collection infrastructure for agent-based collection (sorry if I'm slow). In this way, the draft adds value to SACM, and leaves room for alternative approaches that may not be agent-based. If a tight scope statement could be created along these lines, I think that would go a long way toward clarifying the draft. 
>>  
>> [danny] Do you want to take a pass at that statement :)? Also, where are you thinking it would go? In the introduction?
>>  
>> :-) Dude. (Yeah, I'll give it a shot.) The big important question: Do I get authorship benes? ;-)
>> 
>> [danny] Not sure, I have no idea what the requirements are for that :).
> 
> Of course, I was (mostly) joking.

v2.23.0 | Report a Bug | By Email