
From nobody Wed Apr  1 09:38:13 2015
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF57F1A905E; Wed,  1 Apr 2015 09:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 B81QKG65ysGO; Wed,  1 Apr 2015 09:38:05 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::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 2E02B1A9131; Wed,  1 Apr 2015 09:38:05 -0700 (PDT)
Received: by pacgg7 with SMTP id gg7so57002862pac.0; Wed, 01 Apr 2015 09:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=jHvr81gVQDApjPEHHbz+0n2O/rquTB6hXfJ8VhxOoeY=; b=V6ctwRBL3j3yA4YsiP5ZgEEplWdwLzWdxZtapwkdo7mjSXtYKsIWrJZlRX9luNc43Q j7DvXJbOJa+3jUdPBQpa2LUyKOBXCQW1cG1Am4vtJb1TpIKqZyViV0nDqG07FSDdoK5H jNuIX9Bv20y7PfZOOnIUAcEn2kxSf2vPhk++jtA3kT6sDYgIQYzogR8ZkoUllRvG2ySu g2MfKjCYvc5lleZ6lFAd/Hhy84oTiHP4oPNViCyPCyFI+QRV9Y7NKZdONm+2jDRyJPK6 SuQt4B3wgzacbTkF7RKvco9OamZGYtPwGvrfRLFyff4NBKD5CCSWxEt5xAa5/XA+XJHI rgvw==
X-Received: by 10.68.182.132 with SMTP id ee4mr47535052pbc.24.1427906284565; Wed, 01 Apr 2015 09:38:04 -0700 (PDT)
Received: from ?IPv6:2602:306:3406:4f00:2d74:e5c1:6b77:ba0e? ([2602:306:3406:4f00:2d74:e5c1:6b77:ba0e]) by mx.google.com with ESMTPSA id d4sm2623669pdm.50.2015.04.01.09.38.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 09:38:03 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8C100F87-1054-4020-9400-56526B7B7052"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: "Adam W. Montville" <adam.w.montville@gmail.com>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93D88B0@marathon>
Date: Wed, 1 Apr 2015 11:37:59 -0500
Message-Id: <D5A13F25-14BC-4F3A-ADC5-EDF6A6C143F7@gmail.com>
References: <B551AB38-A9E5-48C0-8049-F44122AF24AE@gmail.com> <551308DD.4040908@ThreatGuard.com> <9F61CC8E6ED7BC4DBA90C13F25D29C002DA5752B@umechpanz.easf.csd.disa.mil> <CAA=AuEdcmXdCe+iUfgLN3wnp98MZnNw5ULMmKnk+5wdrOA=Zmg@mail.gmail.com> <9F61CC8E6ED7BC4DBA90C13F25D29C002DA57678@umechpanz.easf.csd.disa.mil> <, > <CAA=AuEcBh3s6Hbkj_4G-OQCyGHHF0QkbusRXGbSWoatwgCtt=Q@mail.gmail.com> <359EC4B99E040048A7131E0F4E113AFCD93D88B0@marathon>
To: "Roman D. Danyliw" <rdd@cert.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/r_9DvBXZF-MFkHPsf5xC7fmiW4k>
Cc: MILE IETF <mile@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [mile] [sacm]   iodef:SoftwareType
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 16:38:10 -0000

--Apple-Mail=_8C100F87-1054-4020-9400-56526B7B7052
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

All:

It=92s come to my attention that there is such a thing as the =93ENUM =
Registry=94 (I honestly didn=92t know it existed), which has caused some =
confusion outside of our working groups [1]. =20

Because we now have a named registry, it may be better to call it by =
that name or some variant thereof (Security External Enumeration =
Registry - SEER). =20

Regards,

Adam


[1] https://en.wikipedia.org/wiki/Telephone_number_mapping =
<https://en.wikipedia.org/wiki/Telephone_number_mapping>


> On Mar 26, 2015, at 11:20 AM, Roman D. Danyliw <rdd@cert.org> wrote:
>=20
> (Reposting to SACM already on MILE)
> Hello!
>=20
> The original thread on the MILE list [1] about iodef:SoftwareType, =
this thread, and an illuminating offline explanation by Adam Montville =
and Dave Waltermire, highlighted an important distinction as we consider =
how to reuse the existing information models.  There is a difference =
between (a) an identifier into an enumeration; and (b) a blob which is =
the entirety of the information.  In both (a) and (b), a reference to =
the underlying specification is necessary.
>=20
> The ENUM [2] draft provides support for (a).  The current =
iodef:SoftwareType of RFC5070bis [3] supports neither.  Section 4.4 of =
IODEF-SCI [4] supports both (a) and (b).  The caveats for using =
IODEF-SCI for (b) is that the blob has to be XML.  Likewise, the =
approach for (a) uses the @ContentID attribute and/or the now replaced =
iodefv1:Reference class (It was replaced by ENUM and Takeshi Takahashi, =
the editor, has noted this needs to be updated after 5070bis is complete =
in an earlier posting to this thread).
>=20
> Support for multiple approaches to identifying software was voiced =
several times.  The two most actively discussed options were CPE and =
swid.  CPE is an instance of (a) and swid is an instance for (b). =20
>=20
> Thinking through the needs, the representation for software should:
> (1) support (a) and (b)
> (2) support public extensions (with an IANA registry) and private =
approaches
> (3) blobs in formats other than XML?
> (4) support the ability to convey the configuration of the software?=20=

> (5) ability to reason about software at different levels of versioning =
(x.x.x vs. x.x.* vs. x.*.*)?
> others?
>=20
> To the notion of public extensions in (2), which IANA registry should =
be used?  IODEF-SCI uses a single registry for a collection of classes =
that are semantically different.  Should a dedicated registry(ies) be =
used to track standards/formats that describe software?  If a dedicated =
registry is not used, how should implementers know which of the entries =
in the registry are valid software description standards/formats?
>=20
> Roman
>=20
> [1] http://www.ietf.org/mail-archive/web/mile/current/msg01660.html
> [2] draft-ietf-mile-enum-reference-format-14
> [3] draft-ietf-mile-rfc5070-bis-11
> [4] RFC 7203
>=20
>=20
> ________________________________________
> From: mile [mile-bounces@ietf.org] on behalf of Jerome Athias =
[athiasjerome@gmail.com]
> Sent: Wednesday, March 25, 2015 5:16 PM
> To: Wolfkiel, Joseph L CIV DISA ID (US)
> Cc: Gunnar Engelbach; MILE IETF; sacm@ietf.org
> Subject: Re: [mile] [sacm] iodef:SoftwareType
>=20
> so that would be better covered by OVAL (with CPE embedded), and/or
> some kind of MITRE MAEC (YARA included)/CybOX capabilities (mutex and
> in memory opcodes needed?)
>=20
> 2015-03-25 22:00 GMT+01:00 Wolfkiel, Joseph L CIV DISA ID (US)
> <joseph.l.wolfkiel.civ@mail.mil>:
>> I expect the MILE use case would also need to be able to deal with =
software for which the only available data is the name of a file and an =
execution path (e.g. "c:/program files/baddexec.jar").  This is out of =
the CPE case altogether, but would be critical to assist in either =
forensic analysis or malware detection.
>>=20
>> Joseph L. Wolfkiel
>> SCM Engineering Lead
>> DISA ID52
>> (301) 225-8820
>> Joseph.L.Wolfkiel.civ@mail.mil
>>=20
>>=20
>>=20
>> -----Original Message-----
>> From: Jerome Athias [mailto:athiasjerome@gmail.com]
>> Sent: Wednesday, March 25, 2015 4:28 PM
>> To: Wolfkiel, Joseph L CIV DISA ID (US)
>> Cc: Gunnar Engelbach; Adam W. Montville; MILE IETF; sacm@ietf.org
>> Subject: Re: [sacm] iodef:SoftwareType
>>=20
>> Hi,
>>=20
>> using CPEs, for example, in this case would be ok since using the
>> first part of it (application 'name', before the version - or with
>> '*') could cover the use case. (for SWID, I don't know)
>> Then, that's right that if we want, for MILE,  to cover use cases =
like
>> Policy P1 (e.g. CIS X Level 1) for Application A1 on Asset A1, and
>> Policy P2 (e.g. CIS X Level 2) for Application A1 (the same) on Asset
>> A2, etc.
>> it's a different story (ID, UID, GUID, context...)
>> Same for use cases where Software S1 + Software S2 is an issue, but
>> not when S1 used without S2, etc.
>> (context/groups)
>>=20
>> A model for Software/Application/Components (e.g. libraries) and
>> combinations of/relationships between them would have to provide the
>> granularity wanted/needed.
>> But this could be covered step by step.
>>=20
>>=20
>>=20
>>=20
>>=20
>> 2015-03-25 20:50 GMT+01:00 Wolfkiel, Joseph L CIV DISA ID (US)
>> <joseph.l.wolfkiel.civ@mail.mil>:
>>> We write most of our policies to the individual application level, =
but generally don't go to version.  If the MILE requirement includes the =
ability to specify to a given software instance on a particular device =
and you think the softwareType element needs to be able to deal with =
both constructs, then you'll definitely need the ability to handle =
different levels of granularity and be able to specify which type of =
identification you're making.
>>>=20
>>> Joseph L. Wolfkiel
>>> SCM Engineering Lead
>>> DISA ID52
>>> (301) 225-8820
>>> Joseph.L.Wolfkiel.civ@mail.mil
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar =
Engelbach
>>> Sent: Wednesday, March 25, 2015 3:14 PM
>>> To: Adam W. Montville; MILE IETF
>>> Cc: sacm@ietf.org
>>> Subject: Re: [sacm] iodef:SoftwareType
>>>=20
>>>=20
>>> As you say, it depends on the usage for the software identifier.
>>>=20
>>> For SACM that usage isn't likely to go beyond determining =
applicability
>>> because when it comes time to do the security checks then the policy
>>> implementation is likely to specify the particular endpoint =
attributes
>>> to be collected and not rely on any data associated with the =
software
>>> identification.
>>>=20
>>> It seems obvious to me that, with the goal of being able to support
>>> multiple software identification systems, that SACM would embed the =
raw
>>> identifier information below a tag that indicates which identifier =
type
>>> it is.
>>>=20
>>> As far as applicability checking goes, I can see two primary =
principles:
>>>=20
>>> 1) Avoiding false negatives
>>> 2) Efficiency
>>>=20
>>> Presumably a check system that has the ability to collect endpoint
>>> attributes and calculate security results from that also has the =
ability
>>> to self-determine its own applicability.  With that as a fallback, =
then
>>> the worst case is that every policy is attempted to be applied to =
every
>>> endpoint and execution halted for each found to self-determine
>>> non-applicability.
>>>=20
>>> Following from all that, if the decision point where policy =
assessment
>>> assignment is occurring is capable of parsing a particular software
>>> identifier well enough to positively remove a particular policy from =
the
>>> list of potentials, that should suffice.
>>>=20
>>>=20
>>> At first glance, this is not a very interoperable approach.  But =
from a
>>> practical usage standpoint the goal isn't to be perfect, it's to =
reduce
>>> resource utilization for security assessments below the threshold =
where
>>> it affects business operations.  I think it likely that the number =
of
>>> formats necessary to achieve that will be fairly small.  And adding
>>> support for new ones relatively simple.
>>>=20
>>>=20
>>> --gun
>>>=20
>>>=20
>>>=20
>>> On 3/25/2015 2:42 PM, Adam W. Montville wrote:
>>>> I=92m cross-posting to SACM because this is a relevant discussion =
to that WG also.
>>>>=20
>>>> During today=92s MILE session we discussed some options with =
respect to iodef:SoftwareType.  The room seemed to favor looking for a =
way to allow referencing software using more than one software =
identification mechanism.  It was also acknowledged that SACM might find =
use in being able to use different mechanisms of software =
identification.
>>>>=20
>>>> It could be easy enough to submit a given specification/data feed =
for expert review to the ENUM registry.  But, is this sufficient for our =
software identification needs?
>>>>=20
>>>> The potential issue is how the software identification will be =
relied upon downstream. If we want to take the software identification =
component at face value, then using the ENUM registry would likely be =
sufficient.  If, however, we need to specifically interpret or =
specifically apply portions of the software identification component, we =
need more information about (or a priori knowledge of) how to handle =
that type of software identification component.
>>>>=20
>>>> Perhaps it=92s sufficient to rely on encapsulating the software =
identification element in another construct, which could potentially =
make this a non-issue.  For example, if we needed installation =
information for applicability, we could bundle the SoftwareType within a =
larger class which would have any corresponding information (e.g. exact =
location of the software on an endpoint) required for the particular =
case.
>>>>=20
>>>> Still, for cases (if they exist) where a fully specified software =
identification component is intended to be used to identify a broader =
software class, we may run into underspecification issues.  The same is =
true where a software identification component intended to classify =
software is needed for instance-level identification.
>>>>=20
>>>> It seems that some cases of software identification would require =
specification over and above that which would be obtained by simply =
using the ENUM registry.
>>>>=20
>>>> Thoughts?
>>>>=20
>>>> Adam
>>>> _______________________________________________
>>>> sacm mailing list
>>>> sacm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/sacm
>>>=20
>>> _______________________________________________
>>> sacm mailing list
>>> sacm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sacm
>>>=20
>>> _______________________________________________
>>> sacm mailing list
>>> sacm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sacm
>>>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> _______________________________________________
> sacm mailing list
> sacm@ietf.org
> https://www.ietf.org/mailman/listinfo/sacm


--Apple-Mail=_8C100F87-1054-4020-9400-56526B7B7052
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">All:</div><div class=3D""><br =
class=3D""></div><div class=3D"">It=92s come to my attention that there =
is such a thing as the =93ENUM Registry=94 (I honestly didn=92t know it =
existed), which has caused some confusion outside of our working groups =
[1]. &nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Because we now have a named registry, it may be better to =
call it by that name or some variant thereof (Security External =
Enumeration Registry - SEER). &nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Regards,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Adam</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">[1]&nbsp;<a =
href=3D"https://en.wikipedia.org/wiki/Telephone_number_mapping" =
class=3D"">https://en.wikipedia.org/wiki/Telephone_number_mapping</a></div=
><div class=3D""><br class=3D""></div><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Mar 26, 2015, at 11:20 AM, =
Roman D. Danyliw &lt;<a href=3D"mailto:rdd@cert.org" =
class=3D"">rdd@cert.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">(Reposting to SACM =
already on MILE)<br class=3D"">Hello!<br class=3D""><br class=3D"">The =
original thread on the MILE list [1] about iodef:SoftwareType, this =
thread, and an illuminating offline explanation by Adam Montville and =
Dave Waltermire, highlighted an important distinction as we consider how =
to reuse the existing information models. &nbsp;There is a difference =
between (a) an identifier into an enumeration; and (b) a blob which is =
the entirety of the information. &nbsp;In both (a) and (b), a reference =
to the underlying specification is necessary.<br class=3D""><br =
class=3D"">The ENUM [2] draft provides support for (a). &nbsp;The =
current iodef:SoftwareType of RFC5070bis [3] supports neither. =
&nbsp;Section 4.4 of IODEF-SCI [4] supports both (a) and (b). &nbsp;The =
caveats for using IODEF-SCI for (b) is that the blob has to be XML. =
&nbsp;Likewise, the approach for (a) uses the @ContentID attribute =
and/or the now replaced iodefv1:Reference class (It was replaced by ENUM =
and Takeshi Takahashi, the editor, has noted this needs to be updated =
after 5070bis is complete in an earlier posting to this thread).<br =
class=3D""><br class=3D"">Support for multiple approaches to identifying =
software was voiced several times. &nbsp;The two most actively discussed =
options were CPE and swid. &nbsp;CPE is an instance of (a) and swid is =
an instance for (b). &nbsp;<br class=3D""><br class=3D"">Thinking =
through the needs, the representation for software should:<br =
class=3D"">(1) support (a) and (b)<br class=3D"">(2) support public =
extensions (with an IANA registry) and private approaches<br =
class=3D"">(3) blobs in formats other than XML?<br class=3D"">(4) =
support the ability to convey the configuration of the software? <br =
class=3D"">(5) ability to reason about software at different levels of =
versioning (x.x.x vs. x.x.* vs. x.*.*)?<br class=3D"">others?<br =
class=3D""><br class=3D"">To the notion of public extensions in (2), =
which IANA registry should be used? &nbsp;IODEF-SCI uses a single =
registry for a collection of classes that are semantically different. =
&nbsp;Should a dedicated registry(ies) be used to track =
standards/formats that describe software? &nbsp;If a dedicated registry =
is not used, how should implementers know which of the entries in the =
registry are valid software description standards/formats?<br =
class=3D""><br class=3D"">Roman<br class=3D""><br class=3D"">[1] <a =
href=3D"http://www.ietf.org/mail-archive/web/mile/current/msg01660.html" =
class=3D"">http://www.ietf.org/mail-archive/web/mile/current/msg01660.html=
</a><br class=3D"">[2] draft-ietf-mile-enum-reference-format-14<br =
class=3D"">[3] draft-ietf-mile-rfc5070-bis-11<br class=3D"">[4] RFC =
7203<br class=3D""><br class=3D""><br =
class=3D"">________________________________________<br class=3D"">From: =
mile [<a href=3D"mailto:mile-bounces@ietf.org" =
class=3D"">mile-bounces@ietf.org</a>] on behalf of Jerome Athias [<a =
href=3D"mailto:athiasjerome@gmail.com" =
class=3D"">athiasjerome@gmail.com</a>]<br class=3D"">Sent: Wednesday, =
March 25, 2015 5:16 PM<br class=3D"">To: Wolfkiel, Joseph L CIV DISA ID =
(US)<br class=3D"">Cc: Gunnar Engelbach; MILE IETF; <a =
href=3D"mailto:sacm@ietf.org" class=3D"">sacm@ietf.org</a><br =
class=3D"">Subject: Re: [mile] [sacm] iodef:SoftwareType<br class=3D""><br=
 class=3D"">so that would be better covered by OVAL (with CPE embedded), =
and/or<br class=3D"">some kind of MITRE MAEC (YARA included)/CybOX =
capabilities (mutex and<br class=3D"">in memory opcodes needed?)<br =
class=3D""><br class=3D"">2015-03-25 22:00 GMT+01:00 Wolfkiel, Joseph L =
CIV DISA ID (US)<br class=3D"">&lt;<a =
href=3D"mailto:joseph.l.wolfkiel.civ@mail.mil" =
class=3D"">joseph.l.wolfkiel.civ@mail.mil</a>&gt;:<br =
class=3D""><blockquote type=3D"cite" class=3D"">I expect the MILE use =
case would also need to be able to deal with software for which the only =
available data is the name of a file and an execution path (e.g. =
"c:/program files/baddexec.jar"). &nbsp;This is out of the CPE case =
altogether, but would be critical to assist in either forensic analysis =
or malware detection.<br class=3D""><br class=3D"">Joseph L. Wolfkiel<br =
class=3D"">SCM Engineering Lead<br class=3D"">DISA ID52<br =
class=3D"">(301) 225-8820<br class=3D""><a =
href=3D"mailto:Joseph.L.Wolfkiel.civ@mail.mil" =
class=3D"">Joseph.L.Wolfkiel.civ@mail.mil</a><br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">-----Original Message-----<br =
class=3D"">From: Jerome Athias [mailto:athiasjerome@gmail.com]<br =
class=3D"">Sent: Wednesday, March 25, 2015 4:28 PM<br class=3D"">To: =
Wolfkiel, Joseph L CIV DISA ID (US)<br class=3D"">Cc: Gunnar Engelbach; =
Adam W. Montville; MILE IETF; sacm@ietf.org<br class=3D"">Subject: Re: =
[sacm] iodef:SoftwareType<br class=3D""><br class=3D"">Hi,<br =
class=3D""><br class=3D"">using CPEs, for example, in this case would be =
ok since using the<br class=3D"">first part of it (application 'name', =
before the version - or with<br class=3D"">'*') could cover the use =
case. (for SWID, I don't know)<br class=3D"">Then, that's right that if =
we want, for MILE, &nbsp;to cover use cases like<br class=3D"">Policy P1 =
(e.g. CIS X Level 1) for Application A1 on Asset A1, and<br =
class=3D"">Policy P2 (e.g. CIS X Level 2) for Application A1 (the same) =
on Asset<br class=3D"">A2, etc.<br class=3D"">it's a different story =
(ID, UID, GUID, context...)<br class=3D"">Same for use cases where =
Software S1 + Software S2 is an issue, but<br class=3D"">not when S1 =
used without S2, etc.<br class=3D"">(context/groups)<br class=3D""><br =
class=3D"">A model for Software/Application/Components (e.g. libraries) =
and<br class=3D"">combinations of/relationships between them would have =
to provide the<br class=3D"">granularity wanted/needed.<br class=3D"">But =
this could be covered step by step.<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D"">2015-03-25 20:50 =
GMT+01:00 Wolfkiel, Joseph L CIV DISA ID (US)<br =
class=3D"">&lt;joseph.l.wolfkiel.civ@mail.mil&gt;:<br =
class=3D""><blockquote type=3D"cite" class=3D"">We write most of our =
policies to the individual application level, but generally don't go to =
version. &nbsp;If the MILE requirement includes the ability to specify =
to a given software instance on a particular device and you think the =
softwareType element needs to be able to deal with both constructs, then =
you'll definitely need the ability to handle different levels of =
granularity and be able to specify which type of identification you're =
making.<br class=3D""><br class=3D"">Joseph L. Wolfkiel<br class=3D"">SCM =
Engineering Lead<br class=3D"">DISA ID52<br class=3D"">(301) 225-8820<br =
class=3D"">Joseph.L.Wolfkiel.civ@mail.mil<br class=3D""><br class=3D""><br=
 class=3D""><br class=3D"">-----Original Message-----<br class=3D"">From: =
sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Gunnar Engelbach<br =
class=3D"">Sent: Wednesday, March 25, 2015 3:14 PM<br class=3D"">To: =
Adam W. Montville; MILE IETF<br class=3D"">Cc: sacm@ietf.org<br =
class=3D"">Subject: Re: [sacm] iodef:SoftwareType<br class=3D""><br =
class=3D""><br class=3D"">As you say, it depends on the usage for the =
software identifier.<br class=3D""><br class=3D"">For SACM that usage =
isn't likely to go beyond determining applicability<br class=3D"">because =
when it comes time to do the security checks then the policy<br =
class=3D"">implementation is likely to specify the particular endpoint =
attributes<br class=3D"">to be collected and not rely on any data =
associated with the software<br class=3D"">identification.<br =
class=3D""><br class=3D"">It seems obvious to me that, with the goal of =
being able to support<br class=3D"">multiple software identification =
systems, that SACM would embed the raw<br class=3D"">identifier =
information below a tag that indicates which identifier type<br =
class=3D"">it is.<br class=3D""><br class=3D"">As far as applicability =
checking goes, I can see two primary principles:<br class=3D""><br =
class=3D"">1) Avoiding false negatives<br class=3D"">2) Efficiency<br =
class=3D""><br class=3D"">Presumably a check system that has the ability =
to collect endpoint<br class=3D"">attributes and calculate security =
results from that also has the ability<br class=3D"">to self-determine =
its own applicability. &nbsp;With that as a fallback, then<br =
class=3D"">the worst case is that every policy is attempted to be =
applied to every<br class=3D"">endpoint and execution halted for each =
found to self-determine<br class=3D"">non-applicability.<br class=3D""><br=
 class=3D"">Following from all that, if the decision point where policy =
assessment<br class=3D"">assignment is occurring is capable of parsing a =
particular software<br class=3D"">identifier well enough to positively =
remove a particular policy from the<br class=3D"">list of potentials, =
that should suffice.<br class=3D""><br class=3D""><br class=3D"">At =
first glance, this is not a very interoperable approach. &nbsp;But from =
a<br class=3D"">practical usage standpoint the goal isn't to be perfect, =
it's to reduce<br class=3D"">resource utilization for security =
assessments below the threshold where<br class=3D"">it affects business =
operations. &nbsp;I think it likely that the number of<br =
class=3D"">formats necessary to achieve that will be fairly small. =
&nbsp;And adding<br class=3D"">support for new ones relatively =
simple.<br class=3D""><br class=3D""><br class=3D"">--gun<br =
class=3D""><br class=3D""><br class=3D""><br class=3D"">On 3/25/2015 =
2:42 PM, Adam W. Montville wrote:<br class=3D""><blockquote type=3D"cite" =
class=3D"">I=92m cross-posting to SACM because this is a relevant =
discussion to that WG also.<br class=3D""><br class=3D"">During today=92s =
MILE session we discussed some options with respect to =
iodef:SoftwareType. &nbsp;The room seemed to favor looking for a way to =
allow referencing software using more than one software identification =
mechanism. &nbsp;It was also acknowledged that SACM might find use in =
being able to use different mechanisms of software identification.<br =
class=3D""><br class=3D"">It could be easy enough to submit a given =
specification/data feed for expert review to the ENUM registry. =
&nbsp;But, is this sufficient for our software identification needs?<br =
class=3D""><br class=3D"">The potential issue is how the software =
identification will be relied upon downstream. If we want to take the =
software identification component at face value, then using the ENUM =
registry would likely be sufficient. &nbsp;If, however, we need to =
specifically interpret or specifically apply portions of the software =
identification component, we need more information about (or a priori =
knowledge of) how to handle that type of software identification =
component.<br class=3D""><br class=3D"">Perhaps it=92s sufficient to =
rely on encapsulating the software identification element in another =
construct, which could potentially make this a non-issue. &nbsp;For =
example, if we needed installation information for applicability, we =
could bundle the SoftwareType within a larger class which would have any =
corresponding information (e.g. exact location of the software on an =
endpoint) required for the particular case.<br class=3D""><br =
class=3D"">Still, for cases (if they exist) where a fully specified =
software identification component is intended to be used to identify a =
broader software class, we may run into underspecification issues. =
&nbsp;The same is true where a software identification component =
intended to classify software is needed for instance-level =
identification.<br class=3D""><br class=3D"">It seems that some cases of =
software identification would require specification over and above that =
which would be obtained by simply using the ENUM registry.<br =
class=3D""><br class=3D"">Thoughts?<br class=3D""><br class=3D"">Adam<br =
class=3D"">_______________________________________________<br =
class=3D"">sacm mailing list<br class=3D"">sacm@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/sacm<br =
class=3D""></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">sacm mailing list<br class=3D"">sacm@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/sacm<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">sacm mailing list<br class=3D"">sacm@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/sacm<br class=3D""><br =
class=3D""></blockquote></blockquote><br =
class=3D"">_______________________________________________<br =
class=3D"">mile mailing list<br class=3D""><a =
href=3D"mailto:mile@ietf.org" class=3D"">mile@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/mile<br =
class=3D"">_______________________________________________<br =
class=3D"">sacm mailing list<br class=3D"">sacm@ietf.org<br =
class=3D"">https://www.ietf.org/mailman/listinfo/sacm<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_8C100F87-1054-4020-9400-56526B7B7052--


From nobody Wed Apr  1 12:22:41 2015
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA42D1A6F0A for <mile@ietfa.amsl.com>; Wed,  1 Apr 2015 12:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 dTAcvtqVgH8m for <mile@ietfa.amsl.com>; Wed,  1 Apr 2015 12:22:38 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (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 C82581A036E for <mile@ietf.org>; Wed,  1 Apr 2015 12:22:37 -0700 (PDT)
Received: by lahf3 with SMTP id f3so43858164lah.2 for <mile@ietf.org>; Wed, 01 Apr 2015 12:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=u0HS3HaVjpj93lqAY8YuIQW/rgDWemZsW809yDFK4tE=; b=DzI0pvaJMEIGsXWQfCNQXMxfu/KYNTPuOwRc8r3ob5WZ5YrGiUMLUeU8ATcTdBgDQj 4s/kQ1WC3LSM0D7kn9sZKwS7UU1dQlbWKOlS705JHNy8nqySGXi630AHTvO7JPWW/dwD GBsCa/KRzAdbYebT986j4+LDtmkMyiq2elCzBaLxdpnmgpjkBzGzyIajM149LR98MGgH Pyhsdnd+uNVsNdc11b335liiUjXJ68+9Cysmu6zH1/GzyNVySE4815HUpBEwe34E1aFU INK/I0r1JtlyAy30QaosMK4Wzcv4WcRd2AE5+xuUdK5xkNbxLJPyCn2Dkn2SfGEZypYA P8Lg==
MIME-Version: 1.0
X-Received: by 10.152.37.202 with SMTP id a10mr38157913lak.0.1427916156364; Wed, 01 Apr 2015 12:22:36 -0700 (PDT)
Received: by 10.112.167.101 with HTTP; Wed, 1 Apr 2015 12:22:36 -0700 (PDT)
In-Reply-To: <8B8C515B-3D14-4D17-AAD3-72A0EFF99E0D@iab.org>
References: <8B8C515B-3D14-4D17-AAD3-72A0EFF99E0D@iab.org>
Date: Wed, 1 Apr 2015 15:22:36 -0400
Message-ID: <CAHbuEH7tEnC8pd+Jb4byReYgMFwD_-8Htd6ekq27Jra9Gh_b1w@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: MILE IETF <mile@ietf.org>
Content-Type: multipart/alternative; boundary=089e0149405644ecc70512aea3bc
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/_T67wLygzXuvb9pq7PC-1lOiY54>
Subject: [mile] Fwd: Date change for CARIS submissions
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 19:22:39 -0000

--089e0149405644ecc70512aea3bc
Content-Type: text/plain; charset=UTF-8

Please note the submission date change to April 10th for the CARIS
workshop.  We look forward to your submission and participation.

Thank you,
Kathleen
---------- Forwarded message ----------
From: IAB Chair <iab-chair@iab.org>
Date: Wed, Apr 1, 2015 at 3:17 PM
Subject: Date change for CARIS submissions
To: ietf list <ietf-announce@ietf.org>, ietf@ietf.org


Dear colleagues,

The Co-ordinating Attack Response at Internet Scale (CARIS) workshop
program committee is extending the deadline for submissions by one
week, to 10 April 2015.  The call for papers is available from
https://www.iab.org/activities/workshops/caris/call-for-papers/.  For
more information on CARIS, please see
https://www.iab.org/activities/workshops/caris/.

Best regards,

Andrew Sullivan
IAB Chair




-- 

Best regards,
Kathleen

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

<div dir=3D"ltr">Please note the submission date change to April 10th for t=
he CARIS workshop.=C2=A0 We look forward to your submission and participati=
on.<div><br></div><div>Thank you,</div><div>Kathleen<br><div class=3D"gmail=
_quote">---------- Forwarded message ----------<br>From: <b class=3D"gmail_=
sendername">IAB Chair</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:iab-chair=
@iab.org">iab-chair@iab.org</a>&gt;</span><br>Date: Wed, Apr 1, 2015 at 3:1=
7 PM<br>Subject: Date change for CARIS submissions<br>To: ietf list &lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;, <a h=
ref=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br><br><br>Dear colleagues,<=
br>
<br>
The Co-ordinating Attack Response at Internet Scale (CARIS) workshop<br>
program committee is extending the deadline for submissions by one<br>
week, to 10 April 2015.=C2=A0 The call for papers is available from<br>
<a href=3D"https://www.iab.org/activities/workshops/caris/call-for-papers/"=
 target=3D"_blank">https://www.iab.org/activities/workshops/caris/call-for-=
papers/</a>.=C2=A0 For<br>
more information on CARIS, please see<br>
<a href=3D"https://www.iab.org/activities/workshops/caris/" target=3D"_blan=
k">https://www.iab.org/activities/workshops/caris/</a>.<br>
<br>
Best regards,<br>
<br>
Andrew Sullivan<br>
<span class=3D"HOEnZb"><font color=3D"#888888">IAB Chair<br>
<br>
</font></span></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr"><br><div>Best regards,</div><div>Kath=
leen</div></div></div>
</div></div>

--089e0149405644ecc70512aea3bc--


From nobody Wed Apr  1 15:06:04 2015
Return-Path: <turners@ieca.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8141A00AE for <mile@ietfa.amsl.com>; Wed,  1 Apr 2015 15:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.508
X-Spam-Level: *
X-Spam-Status: No, score=1.508 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FSL_HELO_BARE_IP_2=1.675, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 fG9APfAQiNt7 for <mile@ietfa.amsl.com>; Wed,  1 Apr 2015 15:06:02 -0700 (PDT)
Received: from gateway02.websitewelcome.com (gateway02.websitewelcome.com [69.93.136.20]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0CB41A0070 for <mile@ietf.org>; Wed,  1 Apr 2015 15:06:02 -0700 (PDT)
Received: by gateway02.websitewelcome.com (Postfix, from userid 5007) id 58E37F4396FDA; Wed,  1 Apr 2015 17:06:02 -0500 (CDT)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway02.websitewelcome.com (Postfix) with ESMTP id 4A21EF4396F9F for <mile@ietf.org>; Wed,  1 Apr 2015 17:06:02 -0500 (CDT)
Received: from [96.231.227.6] (port=53641 helo=192.168.1.10) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <turners@ieca.com>) id 1YdQlr-0001KQ-KB; Wed, 01 Apr 2015 17:05:59 -0500
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Turner <turners@ieca.com>
In-Reply-To: <FDAFC2B5-EDC6-43F0-9707-EB9CD6428CBA@cert.org>
Date: Wed, 1 Apr 2015 18:06:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AEE209E-65CB-4D6D-B8A1-10BFEF09BA17@ieca.com>
References: <359EC4B99E040048A7131E0F4E113AFCD93D4479@marathon> <FDAFC2B5-EDC6-43F0-9707-EB9CD6428CBA@cert.org>
To: "Roman D. Danyliw" <rdd@cert.org>
X-Mailer: Apple Mail (2.1878.6)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 96.231.227.6
X-Exim-ID: 1YdQlr-0001KQ-KB
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (192.168.1.10) [96.231.227.6]:53641
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 3
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/wC5YyYgeAV-a2u24BJDMjUlFDWw>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Feedack on 5070bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 22:06:04 -0000

On Mar 25, 2015, at 10:54, Chris Inacio <inacio@cert.org> wrote:

>=20
>> On Mar 25, 2015, at 8:16 AM, Roman D. Danyliw <rdd@cert.org> wrote:
>>=20
>> Hello!
>>=20
>> I've been remiss in sharing feedback I've received privately on the =
5070bis.
>>=20
>> (1) If one has 10s/100s of thousands of a particular type of =
indicator, it is too cumbersome to encode them individually into a =
particular class.  More desirable would be a means to convey a long list =
in a single element.
>> Instead of the following:
>> <Address type=3D"ipv4-addr">10.1.1.1</Address>
>> <Address type=3D"ipv4-addr">10.1.1.2</Address>
>> <Address type=3D"ipv4-addr">10.1.1.3</Address>
>> <Address type=3D"ipv4-addr">10.1.1.4</Address>
>> ...
>> Have something like the following
>> <BulkObservable type=3D"ipv4-addr">
>> 10.1.1.1
>> 10.1.1.2
>> 10.1.1.3
>> 10.1.1.4
>> =85
>>=20
>=20
> I like this, since this allows service feeds to more easily leverage =
IODEF.

+1

spt

>> (2) The Service class can convey a port number.  It would be valuable =
to convey the observed port number and also an assessment of the actual =
observed protocol.  For example, how would one represent "I saw traffic =
on port 8493/tcp but it was HTTP=94.
>=20
>>=20
>=20
>> (3) The Counter class doesn't allow one to represent peak and average =
measurements, only actual packet counts.
>>=20
>> Roman
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>=20
>=20
>=20
> --
> Chris Inacio
> inacio@cert.org
>=20
>=20
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Thu Apr  2 00:36:23 2015
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 862231B2BA6 for <mile@ietfa.amsl.com>; Thu,  2 Apr 2015 00:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.497
X-Spam-Level: **
X-Spam-Status: No, score=2.497 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 WmH7QEbdK6Gc for <mile@ietfa.amsl.com>; Thu,  2 Apr 2015 00:36:20 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2F41B2BA4 for <mile@ietf.org>; Thu,  2 Apr 2015 00:36:19 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id t327a8Ok020842; Thu, 2 Apr 2015 16:36:08 +0900 (JST)
Received: from TakeVaioVJP13 (ssh.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id t327a7It020834; Thu, 2 Apr 2015 16:36:07 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Sean Turner'" <turners@ieca.com>, "'Roman D. Danyliw'" <rdd@cert.org>
References: <359EC4B99E040048A7131E0F4E113AFCD93D4479@marathon> <FDAFC2B5-EDC6-43F0-9707-EB9CD6428CBA@cert.org> <3AEE209E-65CB-4D6D-B8A1-10BFEF09BA17@ieca.com>
In-Reply-To: <3AEE209E-65CB-4D6D-B8A1-10BFEF09BA17@ieca.com>
Date: Thu, 2 Apr 2015 16:36:13 +0900
Message-ID: <009201d06d17$b28d3b60$17a7b220$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKTAo/G3QfhQk0Cjvt5hhmnCdvlfwIiJmAxAmeibbibj9uwQA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.5 at zenith1
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/HZg2nv32lKA4r82gNHeBo7ayKdo>
Cc: mile@ietf.org
Subject: Re: [mile] Feedack on 5070bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 07:36:21 -0000

> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Sean Turner
> Sent: Thursday, April 2, 2015 7:06 AM
> 
> On Mar 25, 2015, at 10:54, Chris Inacio <inacio@cert.org> wrote:
> 
> >
> >> On Mar 25, 2015, at 8:16 AM, Roman D. Danyliw <rdd@cert.org> wrote:
> >>
> >> Hello!
> >>
> >> I've been remiss in sharing feedback I've received privately on the
5070bis.
> >>
> >> (1) If one has 10s/100s of thousands of a particular type of indicator,
it
> is too cumbersome to encode them individually into a particular class.
More
> desirable would be a means to convey a long list in a single element.
> >> Instead of the following:
> >> <Address type="ipv4-addr">10.1.1.1</Address>
> >> <Address type="ipv4-addr">10.1.1.2</Address>
> >> <Address type="ipv4-addr">10.1.1.3</Address>
> >> <Address type="ipv4-addr">10.1.1.4</Address>
> >> ...
> >> Have something like the following
> >> <BulkObservable type="ipv4-addr">
> >> 10.1.1.1
> >> 10.1.1.2
> >> 10.1.1.3
> >> 10.1.1.4
> >> .
> >>
> >
> > I like this, since this allows service feeds to more easily leverage
IODEF.
> 
> +1
> 
> spt

+1

Take

> 
> >> (2) The Service class can convey a port number.  It would be valuable
to
> convey the observed port number and also an assessment of the actual
observed
> protocol.  For example, how would one represent "I saw traffic on port
8493/tcp
> but it was HTTP".
> >
> >>
> >
> >> (3) The Counter class doesn't allow one to represent peak and average
> measurements, only actual packet counts.
> >>
> >> Roman
> >> _______________________________________________
> >> mile mailing list
> >> mile@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mile
> >
> >
> >
> > --
> > Chris Inacio
> > inacio@cert.org
> >
> >
> >
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Fri Apr  3 05:06:07 2015
Return-Path: <rdd@cert.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086F81A8FD5 for <mile@ietfa.amsl.com>; Fri,  3 Apr 2015 05:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 M9x7ClXkmuMH for <mile@ietfa.amsl.com>; Fri,  3 Apr 2015 05:06:03 -0700 (PDT)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C1AA1A8F3E for <mile@ietf.org>; Fri,  3 Apr 2015 05:06:03 -0700 (PDT)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id t33C62X4009340 for <mile@ietf.org>; Fri, 3 Apr 2015 08:06:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1428062762; bh=4B1xG5H1hjCTQiQlLVDlPhfqgVJRtEqqAh6FeseaStM=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To:Cc; b=BNfN0s/rfTz9KTGzrugQj/Sk1NAQrpx4gY09Qas30imKbGWLNp2MNVSZdIwbbR4QH ++ezaxsDbAxcVd/zAHWDblSXazKwKgTv1Sx/o9JMn23f1qA2tesCp1AgI5x4TAF59Z wPUb3HqlOWwwlAfOC9xEAdZkZj+d21MuRsRz9g30=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by timber.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id t33C5nqE010296 for <mile@ietf.org>; Fri, 3 Apr 2015 08:06:01 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0210.002; Fri, 3 Apr 2015 08:05:53 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: MILE IETF <mile@ietf.org>
Thread-Topic: [mile] #54 (rfc5070-bis): Reorganize IODEF schema
Thread-Index: AQHQbgZQ8XmEyDY0pUGK0M/eg/R/MJ07MK0h
Date: Fri, 3 Apr 2015 12:05:52 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD93E2F43@marathon>
References: <051.66754e7f7f3c86b171e0b6899b530b00@tools.ietf.org>
In-Reply-To: <051.66754e7f7f3c86b171e0b6899b530b00@tools.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/wCK_yU20EtSyxCETS027XYKfocA>
Subject: Re: [mile] #54 (rfc5070-bis): Reorganize IODEF schema
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2015 12:06:05 -0000

Hello!

If you have further ideas on how to improve the definitions in the schema p=
lease add to this discussion thread on the list.

Roman

________________________________________
From: mile issue tracker [trac+mile@tools.ietf.org]
Sent: Friday, April 03, 2015 8:04 AM
To: draft-ietf-mile-rfc5070-bis@tools.ietf.org; Roman D. Danyliw
Cc: mile@ietf.org
Subject: [mile] #54 (rfc5070-bis): Reorganize IODEF schema

#54: Reorganize IODEF schema

 The the current schema is inconsistent in it's definition of classes and
 uses of types.  There is no right way but if style choices will help
 implementers, we should act on the feedback.  To date, the following
 feedback has been voiced:

 * Fix inconsistent spacing
 * Consider declaring each of the classes individually.  Do not nest
 declarations.  This helps code generators that parse the schema
 * Consider declaring each of the enumerated attribute types outside of the
 attributes that use them.

--
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-mile-
  rdd@cert.org           |  rfc5070-bis@tools.ietf.org
     Type:  enhancement  |     Status:  new
 Priority:  major        |  Milestone:
Component:  rfc5070-bis  |    Version:
 Severity:  -            |   Keywords:
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/mile/trac/ticket/54>
mile <http://tools.ietf.org/mile/>=

