
From pkampana@cisco.com  Fri Mar  1 13:52:33 2013
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3934721F8D6D; Fri,  1 Mar 2013 13:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGBhYlaOSU3F; Fri,  1 Mar 2013 13:52:32 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 36D6F21F8D66; Fri,  1 Mar 2013 13:52:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3535; q=dns/txt; s=iport; t=1362174752; x=1363384352; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=DUFu3ziD9oZ9Fmwrtzt9XqUKgKXkelnjGzCUKCgnE/Y=; b=l71bu5l/tdo2Y7ZfQUhiXlsb7DlsIgUKEEEyeBRW3LEuJDfiIHmi6k0p fwRe7+EBaHfMbixSCIEBTbkuMfKSnBCbuWmPikF/+vJfAv1SvFQxlnPZ3 U2qSwNGvPLzbZXVMOTeqE1tbvL+mJXltWUk9YNDqtvLcTpGPTsIPnQtBA M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFQhMVGtJV2d/2dsb2JhbABEwj5/FnOCHwEBAQQBAQE3NBcEAgEIEQQBAQsUCQcnCxQJCAIEAQ4ECBOHeAzBGo1MEIEQJhIGgllhA5dhj02DCIFyNQ
X-IronPort-AV: E=Sophos;i="4.84,762,1355097600"; d="scan'208";a="179847234"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 01 Mar 2013 21:52:31 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r21LqVX1013508 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Mar 2013 21:52:31 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 15:52:31 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Thread-Topic: Including Mail fields in IODEF
Thread-Index: AQHOEBvuagQSHFBhb0e+qysbcbjrmZiRbEJg
Date: Fri, 1 Mar 2013 21:52:31 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com>, <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.89.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 01 Mar 2013 21:52:33 -0000

I think MARF provides more functionality and should be leverage for emails =
in IODEF.
I also think we need to resurrect http://tools.ietf.org/html/draft-vesely-m=
ile-mail-abuse-00 within MILE since MARF was concluded..
Panos


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Thursday, February 21, 2013 5:19 AM
To: mile@ietf.org; marf@ietf.org
Subject: [mile] Including Mail fields in IODEF

Hello,

Cross posting with MAIL and MARF -=20

In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below).  We would like some help to figure out the best app=
roach.  Should we embed ARF and MARF RFC extensions to accommodate this nee=
d or should we look at updating RFC5901?  Both take the approach of includi=
ng an email message as opposed to using XML to tag each field and allow for=
 this in the data model (in my opinion, that is fine and reduces bloat, but=
 there may be other opinions).

There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.

Thanks,
Kathleen
________________________________________
From: Harrington, Christopher
Sent: Wednesday, February 20, 2013 2:57 PM
To: Moriarty, Kathleen; mile@ietf.org
Subject: RE: Mail fields

I'm for the simplest solution as always. These are the indicator types that=
 we routinely share. I would use these as a base:

Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email

It's also very common to share the whole header. Bad guys routinely forge t=
hem and put extra header items that can be used as indicators.  Although no=
t an indicator sharing the entire email as an .eml or .msg file is also pre=
tty common.

Thanks,

--Chris


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Wednesday, February 20, 2013 2:58 AM
To: mile@ietf.org
Subject: [mile] Mail fields

Hi,

In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents.  A couple of commonly=
 exchanged fields were added into the Record class.  You can still extend o=
ut using RFC5901 and include a full mail message, but if you wanted to incl=
ude DKIM or Sender Policy Framework, you need something else.  The IETF gro=
up MARF already solved these issues.

MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:
http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00

Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data?  Other options would be to update RFC5901 or to extend IODEF =
further.  I prefer the use of MARF.  It is already in use by mail operators=
, so there is adoption.

Thanks,
Kathleen
_______________________________________________
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 superuser@gmail.com  Sun Mar  3 01:00:18 2013
Return-Path: <superuser@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C913F21F84AF; Sun,  3 Mar 2013 01:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IsCdxrgUrpK; Sun,  3 Mar 2013 01:00:17 -0800 (PST)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 52C0321F84DC; Sun,  3 Mar 2013 01:00:17 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id 12so816524wgh.3 for <multiple recipients>; Sun, 03 Mar 2013 01:00:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=20v0v+mv6OI7TEaWx4IlhmnUfpxU9HUYAzwGo4FB1XI=; b=ak2AiWFEgeoxbGiFN+fu3Ue1NSQNKeMPj4bI9jFSrfxj6RqAGAWGVyZYjGSr6URRij RNBsEm+wFUqHML0gG6w3bl3s9YPCxfSsvx75N6t1if916BtRuoUNnFKr7X0+aoQa6qHN T/174n/vISGIZzxivYZ7nu8m25mDANmnW6ZHkaIk4oGK/QXsEKYJMjTwrk+yQKTlt04B d0gLt3IeAOsDAlo/qX76yJ7GD9L3rUyfk0jPuTe3/Tt2aXpu/+Rc/KC5VwvA1onzTeAA 8ZgTuRKiJCIfpSRgOEb/yQ0S02MeoJSr2Uq8Abzns+vz8qVcnEOSAzG3epCFWkalAxIe Ky/w==
MIME-Version: 1.0
X-Received: by 10.180.93.168 with SMTP id cv8mr5902767wib.5.1362301216380; Sun, 03 Mar 2013 01:00:16 -0800 (PST)
Received: by 10.180.189.6 with HTTP; Sun, 3 Mar 2013 01:00:16 -0800 (PST)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com> <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com>
Date: Sun, 3 Mar 2013 01:00:16 -0800
Message-ID: <CAL0qLwa9ixHTeONJoq3SM-ZknKybHDg590cH5SHDhgbS=j89Gg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Content-Type: multipart/alternative; boundary=f46d043c7fba145e9204d70178df
X-Mailman-Approved-At: Sun, 03 Mar 2013 01:33:14 -0800
Cc: "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [mile] [marf] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 03 Mar 2013 09:00:19 -0000

--f46d043c7fba145e9204d70178df
Content-Type: text/plain; charset=ISO-8859-1

Hi Kathleen, sorry for the delay replying to this.  It seems to me that, as
you suggested, your options are:

1) As I read RFC5901, it's a set of XML tags used to extract specific
pieces of message data or meta-data and include them in an IODEF report.
You could simply add some DKIM and SPF fields as well.  Keep in mind that
SPF applies once per message (because there's always exactly one envelope)
but any number of DKIM results (including zero) can be present.  There's
also some religion around whether a failed DKIM signature is even worth
reporting, but we can get into that separately if needed.

2) RFC5901 also adds the capability to include a complete email message in
the report payload.  This could be an ARF message (using the SPF and DKIM
extensions), which itself can contain the original.

I would suggest going with (1) personally; it's more work procedurally, but
the result is cleaner.  With (2) you're able to capitalize on what MARF
did, but the receiver has to know that the payload message is actually an
abuse report that contains part or all of the problem message, and is not
itself the problem message.

Let me know if you'd like more detail on any of that.

-MSK


On Thu, Feb 21, 2013 at 2:19 AM, Moriarty, Kathleen <
kathleen.moriarty@emc.com> wrote:

> Hello,
>
> Cross posting with MAIL and MARF -
>
> In MILE related work, I have come across use cases that would like to
> include DKIM and SPF information in addition to specific mail fields (like
> the ones Chris lists below).  We would like some help to figure out the
> best approach.  Should we embed ARF and MARF RFC extensions to accommodate
> this need or should we look at updating RFC5901?  Both take the approach of
> including an email message as opposed to using XML to tag each field and
> allow for this in the data model (in my opinion, that is fine and reduces
> bloat, but there may be other opinions).
>
> There was a draft published last year (link included below) that includes
> MARF in an IODE extension.
>
> Thanks,
> Kathleen
> ________________________________________
> From: Harrington, Christopher
> Sent: Wednesday, February 20, 2013 2:57 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: RE: Mail fields
>
> I'm for the simplest solution as always. These are the indicator types that
> we routinely share. I would use these as a base:
>
> Email address (denoting if it is to or from)
> Email Subject
> Email attachment name
> Email attachment hash
> X-Mailer (from header)
> Hyperlink in email
>
> It's also very common to share the whole header. Bad guys routinely forge
> them and put extra header items that can be used as indicators.  Although
> not an indicator sharing the entire email as an .eml or .msg file is also
> pretty common.
>
> Thanks,
>
> --Chris
>
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Wednesday, February 20, 2013 2:58 AM
> To: mile@ietf.org
> Subject: [mile] Mail fields
>
> Hi,
>
> In looking at the updated rfc5070bis and coming across some requests for
> handling certain types of exchanges, I am curious to hear how others think
> we should handle mail related indicators and incidents.  A couple of
> commonly exchanged fields were added into the Record class.  You can still
> extend out using RFC5901 and include a full mail message, but if you wanted
> to include DKIM or Sender Policy Framework, you need something else.  The
> IETF group MARF already solved these issues.
>
> MARF uses the email tags rather than XML and there was a draft that
> embedded
> MARF content into IODEF (contains an example), can be found here:
> http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00
>
> Since mail is already marked and can be parsed, would this be a better
> option to use what MARF has already done to solve the question on how to
> exchange this data?  Other options would be to update RFC5901 or to extend
> IODEF further.  I prefer the use of MARF.  It is already in use by mail
> operators, so there is adoption.
>
> Thanks,
> Kathleen
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> _______________________________________________
> marf mailing list
> marf@ietf.org
> https://www.ietf.org/mailman/listinfo/marf
>

--f46d043c7fba145e9204d70178df
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Kathleen, sorry for the delay replying t=
o this.=A0 It seems to me that, as you suggested, your options are:<br><br>=
</div>1) As I read RFC5901, it&#39;s a set of XML tags used to extract spec=
ific pieces of message data or meta-data and include them in an IODEF repor=
t.=A0 You could simply add some DKIM and SPF fields as well.=A0 Keep in min=
d that SPF applies once per message (because there&#39;s always exactly one=
 envelope) but any number of DKIM results (including zero) can be present.=
=A0 There&#39;s also some religion around whether a failed DKIM signature i=
s even worth reporting, but we can get into that separately if needed.<br>
<br></div>2) RFC5901 also adds the capability to include a complete email m=
essage in the report payload.=A0 This could be an ARF message (using the SP=
F and DKIM extensions), which itself can contain the original.<br><br></div=
>
I would suggest going with (1) personally; it&#39;s more work procedurally,=
 but the result is cleaner.=A0 With (2) you&#39;re able to capitalize on wh=
at MARF did, but the receiver has to know that the payload message is actua=
lly an abuse report that contains part or all of the problem message, and i=
s not itself the problem message.<br>
<div><br></div><div>Let me know if you&#39;d like more detail on any of tha=
t.<br><br></div><div>-MSK<br></div></div><div class=3D"gmail_extra"><br><br=
><div class=3D"gmail_quote">On Thu, Feb 21, 2013 at 2:19 AM, Moriarty, Kath=
leen <span dir=3D"ltr">&lt;<a href=3D"mailto:kathleen.moriarty@emc.com" tar=
get=3D"_blank">kathleen.moriarty@emc.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hello,<br>
<br>
Cross posting with MAIL and MARF -<br>
<br>
In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below). =A0We would like some help to figure out the best a=
pproach. =A0Should we embed ARF and MARF RFC extensions to accommodate this=
 need or should we look at updating RFC5901? =A0Both take the approach of i=
ncluding an email message as opposed to using XML to tag each field and all=
ow for this in the data model (in my opinion, that is fine and reduces bloa=
t, but there may be other opinions).<br>

<br>
There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.<br>
<br>
Thanks,<br>
Kathleen<br>
________________________________________<br>
From: Harrington, Christopher<br>
Sent: Wednesday, February 20, 2013 2:57 PM<br>
To: Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><=
br>
Subject: RE: Mail fields<br>
<br>
I&#39;m for the simplest solution as always. These are the indicator types =
that<br>
we routinely share. I would use these as a base:<br>
<br>
Email address (denoting if it is to or from)<br>
Email Subject<br>
Email attachment name<br>
Email attachment hash<br>
X-Mailer (from header)<br>
Hyperlink in email<br>
<br>
It&#39;s also very common to share the whole header. Bad guys routinely for=
ge<br>
them and put extra header items that can be used as indicators. =A0Although=
<br>
not an indicator sharing the entire email as an .eml or .msg file is also<b=
r>
pretty common.<br>
<br>
Thanks,<br>
<br>
--Chris<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>] O=
n Behalf Of<br>
Moriarty, Kathleen<br>
Sent: Wednesday, February 20, 2013 2:58 AM<br>
To: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
Subject: [mile] Mail fields<br>
<br>
Hi,<br>
<br>
In looking at the updated rfc5070bis and coming across some requests for<br=
>
handling certain types of exchanges, I am curious to hear how others think<=
br>
we should handle mail related indicators and incidents. =A0A couple of<br>
commonly exchanged fields were added into the Record class. =A0You can stil=
l<br>
extend out using RFC5901 and include a full mail message, but if you wanted=
<br>
to include DKIM or Sender Policy Framework, you need something else. =A0The=
<br>
IETF group MARF already solved these issues.<br>
<br>
MARF uses the email tags rather than XML and there was a draft that embedde=
d<br>
MARF content into IODEF (contains an example), can be found here:<br>
<a href=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a=
><br>
<br>
Since mail is already marked and can be parsed, would this be a better<br>
option to use what MARF has already done to solve the question on how to<br=
>
exchange this data? =A0Other options would be to update RFC5901 or to exten=
d<br>
IODEF further. =A0I prefer the use of MARF. =A0It is already in use by mail=
<br>
operators, so there is adoption.<br>
<br>
Thanks,<br>
Kathleen<br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
marf mailing list<br>
<a href=3D"mailto:marf@ietf.org">marf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/marf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/marf</a><br>
</blockquote></div><br></div>

--f46d043c7fba145e9204d70178df--

From superuser@gmail.com  Sun Mar  3 01:09:36 2013
Return-Path: <superuser@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1DC21F8648; Sun,  3 Mar 2013 01:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.117
X-Spam-Level: 
X-Spam-Status: No, score=-3.117 tagged_above=-999 required=5 tests=[AWL=0.481,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HsdrMkLMPFTg; Sun,  3 Mar 2013 01:09:34 -0800 (PST)
Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by ietfa.amsl.com (Postfix) with ESMTP id 97A9A21F85EE; Sun,  3 Mar 2013 01:09:33 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id dr13so3442250wgb.26 for <multiple recipients>; Sun, 03 Mar 2013 01:09:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uF1tTBOit/eOXcG0zSoqhIq3LEc7i5Im8bBhw5oTpLY=; b=cRMMteOcFghHnLXzOeANcM/1QLap7HjK3bxQdzqAh6NlOaRMJ2ZbXL4lAYS5jjnvMs tPlvi/4gQ83hx8zSmlEIQ9FWYjytpsyPkpKrlFKzk4DS/ChEadLcPLrNY9pnwkMTTnxx sRk30Daecy0BpjpnpUXZ0KehOqCFaE4qK8sQvD6dSnnWRk26McyrY1jEF2fUdVFzK68X iBCJV06NFo4YGpVRPhCEYfHsRuLOxhSFx55QcF4fY4bqR9N56LF4fY2yt/u4fxRthQW0 6DZhI5FeerpV0s0EN93UBQaGp329hG6CL9bdLlUJmrinTZd3wRxBnH0c/ooWXF39ur5L et/g==
MIME-Version: 1.0
X-Received: by 10.180.82.70 with SMTP id g6mr5415567wiy.21.1362301772581; Sun, 03 Mar 2013 01:09:32 -0800 (PST)
Received: by 10.180.189.6 with HTTP; Sun, 3 Mar 2013 01:09:32 -0800 (PST)
In-Reply-To: <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com> <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com> <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com>
Date: Sun, 3 Mar 2013 01:09:32 -0800
Message-ID: <CAL0qLwZxwkcJi7Ej0fU5s8k-xZ=n_4fa0cvVVF05YtQPc3Ndag@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Content-Type: multipart/alternative; boundary=f46d044267263b52da04d701991a
X-Mailman-Approved-At: Sun, 03 Mar 2013 01:33:14 -0800
Cc: "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [mile] [marf] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 03 Mar 2013 09:09:36 -0000

--f46d044267263b52da04d701991a
Content-Type: text/plain; charset=ISO-8859-1

The issue with MARF inside IODEF is that the receiver needs to know that
the payload being provided inside an EmailMessage element is itself an ARF
report, and not the message that caused the report in the first place.  You
certainly could crack open the EmailMessage content and see if conforms to
the ARF specification to tell which kind of report you've gotten, but that
seems inelegant.

I suppose then another option is an extension element that indicates you've
received an ARF payload rather than the actual offending message.

Also of note: An ARF can contain the offending message or only the
offending message's header, and still be compliant.  If your application
needs the whole message, you'll have to add some additional stipulations
someplace.

-MSK


On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <
pkampana@cisco.com> wrote:

> I think MARF provides more functionality and should be leverage for emails
> in IODEF.
> I also think we need to resurrect
> http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00 within MILE
> since MARF was concluded..
> Panos
>
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Thursday, February 21, 2013 5:19 AM
> To: mile@ietf.org; marf@ietf.org
> Subject: [mile] Including Mail fields in IODEF
>
> Hello,
>
> Cross posting with MAIL and MARF -
>
> In MILE related work, I have come across use cases that would like to
> include DKIM and SPF information in addition to specific mail fields (like
> the ones Chris lists below).  We would like some help to figure out the
> best approach.  Should we embed ARF and MARF RFC extensions to accommodate
> this need or should we look at updating RFC5901?  Both take the approach of
> including an email message as opposed to using XML to tag each field and
> allow for this in the data model (in my opinion, that is fine and reduces
> bloat, but there may be other opinions).
>
> There was a draft published last year (link included below) that includes
> MARF in an IODE extension.
>
> Thanks,
> Kathleen
> ________________________________________
> From: Harrington, Christopher
> Sent: Wednesday, February 20, 2013 2:57 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: RE: Mail fields
>
> I'm for the simplest solution as always. These are the indicator types
> that we routinely share. I would use these as a base:
>
> Email address (denoting if it is to or from) Email Subject Email
> attachment name Email attachment hash X-Mailer (from header) Hyperlink in
> email
>
> It's also very common to share the whole header. Bad guys routinely forge
> them and put extra header items that can be used as indicators.  Although
> not an indicator sharing the entire email as an .eml or .msg file is also
> pretty common.
>
> Thanks,
>
> --Chris
>
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Wednesday, February 20, 2013 2:58 AM
> To: mile@ietf.org
> Subject: [mile] Mail fields
>
> Hi,
>
> In looking at the updated rfc5070bis and coming across some requests for
> handling certain types of exchanges, I am curious to hear how others think
> we should handle mail related indicators and incidents.  A couple of
> commonly exchanged fields were added into the Record class.  You can still
> extend out using RFC5901 and include a full mail message, but if you wanted
> to include DKIM or Sender Policy Framework, you need something else.  The
> IETF group MARF already solved these issues.
>
> MARF uses the email tags rather than XML and there was a draft that
> embedded MARF content into IODEF (contains an example), can be found here:
> http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00
>
> Since mail is already marked and can be parsed, would this be a better
> option to use what MARF has already done to solve the question on how to
> exchange this data?  Other options would be to update RFC5901 or to extend
> IODEF further.  I prefer the use of MARF.  It is already in use by mail
> operators, so there is adoption.
>
> Thanks,
> Kathleen
> _______________________________________________
> 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
> _______________________________________________
> marf mailing list
> marf@ietf.org
> https://www.ietf.org/mailman/listinfo/marf
>

--f46d044267263b52da04d701991a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>The issue with MARF inside IODEF is that the rec=
eiver needs to know that the payload being provided inside an EmailMessage =
element is itself an ARF report, and not the message that caused the report=
 in the first place.=A0 You certainly could crack open the EmailMessage con=
tent and see if conforms to the ARF specification to tell which kind of rep=
ort you&#39;ve gotten, but that seems inelegant.<br>
<br></div>I suppose then another option is an extension element that indica=
tes you&#39;ve received an ARF payload rather than the actual offending mes=
sage.<br><br>Also of note: An ARF can contain the offending message or only=
 the offending message&#39;s header, and still be compliant.=A0 If your app=
lication needs the whole message, you&#39;ll have to add some additional st=
ipulations someplace.<br>
<br></div>-MSK<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_blank">p=
kampana@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I think MARF provides more functionality and=
 should be leverage for emails in IODEF.<br>
I also think we need to resurrect <a href=3D"http://tools.ietf.org/html/dra=
ft-vesely-mile-mail-abuse-00" target=3D"_blank">http://tools.ietf.org/html/=
draft-vesely-mile-mail-abuse-00</a> within MILE since MARF was concluded..<=
br>

<span class=3D"HOEnZb"><font color=3D"#888888">Panos<br>
</font></span><div class=3D"im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>] O=
n Behalf Of Moriarty, Kathleen<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">Sent: Thursday, February 21, =
2013 5:19 AM<br>
To: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a>; <a href=3D"mailto:m=
arf@ietf.org">marf@ietf.org</a><br>
Subject: [mile] Including Mail fields in IODEF<br>
<br>
Hello,<br>
<br>
Cross posting with MAIL and MARF -<br>
<br>
In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below). =A0We would like some help to figure out the best a=
pproach. =A0Should we embed ARF and MARF RFC extensions to accommodate this=
 need or should we look at updating RFC5901? =A0Both take the approach of i=
ncluding an email message as opposed to using XML to tag each field and all=
ow for this in the data model (in my opinion, that is fine and reduces bloa=
t, but there may be other opinions).<br>

<br>
There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.<br>
<br>
Thanks,<br>
Kathleen<br>
________________________________________<br>
From: Harrington, Christopher<br>
Sent: Wednesday, February 20, 2013 2:57 PM<br>
To: Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><=
br>
Subject: RE: Mail fields<br>
<br>
I&#39;m for the simplest solution as always. These are the indicator types =
that we routinely share. I would use these as a base:<br>
<br>
Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email<br>
<br>
It&#39;s also very common to share the whole header. Bad guys routinely for=
ge them and put extra header items that can be used as indicators. =A0Altho=
ugh not an indicator sharing the entire email as an .eml or .msg file is al=
so pretty common.<br>

<br>
Thanks,<br>
<br>
--Chris<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>] O=
n Behalf Of Moriarty, Kathleen<br>
Sent: Wednesday, February 20, 2013 2:58 AM<br>
To: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
Subject: [mile] Mail fields<br>
<br>
Hi,<br>
<br>
In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents. =A0A couple of common=
ly exchanged fields were added into the Record class. =A0You can still exte=
nd out using RFC5901 and include a full mail message, but if you wanted to =
include DKIM or Sender Policy Framework, you need something else. =A0The IE=
TF group MARF already solved these issues.<br>

<br>
MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:<br>
<a href=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a=
><br>
<br>
Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data? =A0Other options would be to update RFC5901 or to extend IODE=
F further. =A0I prefer the use of MARF. =A0It is already in use by mail ope=
rators, so there is adoption.<br>

<br>
Thanks,<br>
Kathleen<br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
marf mailing list<br>
<a href=3D"mailto:marf@ietf.org">marf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/marf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/marf</a><br>
</div></div></blockquote></div><br></div>

--f46d044267263b52da04d701991a--

From pkampana@cisco.com  Sun Mar  3 14:37:09 2013
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60AC321F88C1; Sun,  3 Mar 2013 14:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dr41mYSW0Zm7; Sun,  3 Mar 2013 14:37:04 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id ABD5D21F88BF; Sun,  3 Mar 2013 14:37:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21339; q=dns/txt; s=iport; t=1362350224; x=1363559824; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iGg9gjCTBheDSlzIYA07Wu+PTPYqcVwwQVtlQrbxPY4=; b=XEOCIx1BhfoqyILmtpeXvrKsbuyhWGd4lujs9LRVTCUvtcLg1kUyq4Wd nug1b8HfYlv/EgKguQb1Q4SnfaShfICiOdViQgiuu5hUWoRW4gxtbf+B2 9RTH4H4lt9SNcNC9pVcWLRnNYmkVNcfxaLBU8EdxDgfHjNwV9oxoViSde w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFADTQM1GtJXHA/2dsb2JhbABFgkOGa7ByAYgpfhZzgh8BAQEEAQEBKkELDAQCAQgRAwEBAQsdByEGCxQJCAIEDgEECBOHZgMPDL1fDYknjEWBBxCBECAGBgEEBgEGA4JWYQOUZ4J9ijaFGIMIgXI1
X-IronPort-AV: E=Sophos;i="4.84,774,1355097600";  d="scan'208,217";a="183005571"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 03 Mar 2013 22:37:02 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r23Mb2Na007233 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 3 Mar 2013 22:37:02 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Sun, 3 Mar 2013 16:37:02 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Thread-Topic: [marf] Including Mail fields in IODEF
Thread-Index: AQHOF+7Za9kyjHSIHUueKEyqFsBb8piUjOJQ
Date: Sun, 3 Mar 2013 22:37:01 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A75187BDA@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com> <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com> <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com> <CAL0qLwZxwkcJi7Ej0fU5s8k-xZ=n_4fa0cvVVF05YtQPc3Ndag@mail.gmail.com>
In-Reply-To: <CAL0qLwZxwkcJi7Ej0fU5s8k-xZ=n_4fa0cvVVF05YtQPc3Ndag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.63.179]
Content-Type: multipart/alternative; boundary="_000_1C9F17D1873AFA47A969C4DD98F98A75187BDAxmbrcdx10ciscocom_"
MIME-Version: 1.0
Cc: "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [mile] [marf] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 03 Mar 2013 22:37:09 -0000

--_000_1C9F17D1873AFA47A969C4DD98F98A75187BDAxmbrcdx10ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thank you Murray.


The "<arf:EmailMessage>
   Received: from mailserver.example.net
        (mailserver.example.net [192.0.2.1])
        by example.com with ESMTP id M63d4137594e46;
        Thu, 08 Mar 2005 14:00:00 -0400
   From: &lt;somespammer@example.net&gt;
   To: &lt;Undisclosed Recipients&gt;
   Subject: Earn money
   MIME-Version: 1.0
   Content-type: text/plain
   Message-ID: 8787KJKJ3K4J3K4J3K4J3.mail@example.net
   Date: Thu, 02 Sep 2004 12:31:03 -0500

   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam
         </arf:EmailMessage>"

that I see in http://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-ab=
use-00.txt looks like just an email message. I don't see "feedback-type" or=
 other ARF fields for example that would make it a ARF.



draft-vesely-mile-mail-abuse-00.txt seems to define a header and then have =
the option for the actual message (EmailMessage). Am I reading it wrong?



Panos




From: Murray S. Kucherawy [mailto:superuser@gmail.com]
Sent: Sunday, March 03, 2013 4:10 AM
To: Panos Kampanakis (pkampana)
Cc: Moriarty, Kathleen; mile@ietf.org; marf@ietf.org
Subject: Re: [marf] Including Mail fields in IODEF

The issue with MARF inside IODEF is that the receiver needs to know that th=
e payload being provided inside an EmailMessage element is itself an ARF re=
port, and not the message that caused the report in the first place.  You c=
ertainly could crack open the EmailMessage content and see if conforms to t=
he ARF specification to tell which kind of report you've gotten, but that s=
eems inelegant.
I suppose then another option is an extension element that indicates you've=
 received an ARF payload rather than the actual offending message.

Also of note: An ARF can contain the offending message or only the offendin=
g message's header, and still be compliant.  If your application needs the =
whole message, you'll have to add some additional stipulations someplace.
-MSK

On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <pkampana@cisco=
.com<mailto:pkampana@cisco.com>> wrote:
I think MARF provides more functionality and should be leverage for emails =
in IODEF.
I also think we need to resurrect http://tools.ietf.org/html/draft-vesely-m=
ile-mail-abuse-00 within MILE since MARF was concluded..
Panos


-----Original Message-----
From: mile-bounces@ietf.org<mailto:mile-bounces@ietf.org> [mailto:mile-boun=
ces@ietf.org<mailto:mile-bounces@ietf.org>] On Behalf Of Moriarty, Kathleen
Sent: Thursday, February 21, 2013 5:19 AM
To: mile@ietf.org<mailto:mile@ietf.org>; marf@ietf.org<mailto:marf@ietf.org=
>
Subject: [mile] Including Mail fields in IODEF

Hello,

Cross posting with MAIL and MARF -

In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below).  We would like some help to figure out the best app=
roach.  Should we embed ARF and MARF RFC extensions to accommodate this nee=
d or should we look at updating RFC5901?  Both take the approach of includi=
ng an email message as opposed to using XML to tag each field and allow for=
 this in the data model (in my opinion, that is fine and reduces bloat, but=
 there may be other opinions).

There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.

Thanks,
Kathleen
________________________________________
From: Harrington, Christopher
Sent: Wednesday, February 20, 2013 2:57 PM
To: Moriarty, Kathleen; mile@ietf.org<mailto:mile@ietf.org>
Subject: RE: Mail fields

I'm for the simplest solution as always. These are the indicator types that=
 we routinely share. I would use these as a base:

Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email

It's also very common to share the whole header. Bad guys routinely forge t=
hem and put extra header items that can be used as indicators.  Although no=
t an indicator sharing the entire email as an .eml or .msg file is also pre=
tty common.

Thanks,

--Chris


-----Original Message-----
From: mile-bounces@ietf.org<mailto:mile-bounces@ietf.org> [mailto:mile-boun=
ces@ietf.org<mailto:mile-bounces@ietf.org>] On Behalf Of Moriarty, Kathleen
Sent: Wednesday, February 20, 2013 2:58 AM
To: mile@ietf.org<mailto:mile@ietf.org>
Subject: [mile] Mail fields

Hi,

In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents.  A couple of commonly=
 exchanged fields were added into the Record class.  You can still extend o=
ut using RFC5901 and include a full mail message, but if you wanted to incl=
ude DKIM or Sender Policy Framework, you need something else.  The IETF gro=
up MARF already solved these issues.

MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:
http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00

Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data?  Other options would be to update RFC5901 or to extend IODEF =
further.  I prefer the use of MARF.  It is already in use by mail operators=
, so there is adoption.

Thanks,
Kathleen
_______________________________________________
mile mailing list
mile@ietf.org<mailto:mile@ietf.org>
https://www.ietf.org/mailman/listinfo/mile
_______________________________________________
mile mailing list
mile@ietf.org<mailto:mile@ietf.org>
https://www.ietf.org/mailman/listinfo/mile
_______________________________________________
marf mailing list
marf@ietf.org<mailto:marf@ietf.org>
https://www.ietf.org/mailman/listinfo/marf


--_000_1C9F17D1873AFA47A969C4DD98F98A75187BDAxmbrcdx10ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thank you Murray.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">The &#8220;</span><span style=3D"color:blac=
k">&lt;arf:EmailMessage&gt;<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Received: from mailserver.example=
.net<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (ma=
ilserver.example.net [192.0.2.1])<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by =
example.com with ESMTP id M63d4137594e46;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thu=
, 08 Mar 2005 14:00:00 -0400<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; From: &amp;lt;somespammer@example=
.net&amp;gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; To: &amp;lt;Undisclosed Recipient=
s&amp;gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Subject: Earn money<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; MIME-Version: 1.0<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Content-type: text/plain<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Message-ID: 8787KJKJ3K4J3K4J3K4J3=
.mail@example.net<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Date: Thu, 02 Sep 2004 12:31:03 -=
0500<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Spam Spam Spam<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Spam Spam Spam<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Spam Spam Spam<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp; Spam Spam Spam<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; &lt;/arf:EmailMessage&gt;</span><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&#8221;<o:p><=
/o:p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">that I see in <a href=3D"http://bgp.potaroo=
.net/ietf/all-ids/draft-vesely-mile-mail-abuse-00.txt">http://bgp.potaroo.n=
et/ietf/all-ids/draft-vesely-mile-mail-abuse-00.txt</a> looks like just an =
email message. I don&#8217;t see &#8220;</span><span style=3D"color:black">=
feedback-type</span><span style=3D"font-size:11.0pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1F497D">&quot; or other ARF fields f=
or example that would make it a ARF.<o:p></o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"color:black">draft-vesely-mile-mail-abuse-00.txt </span=
><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">seems to define a header and then have the opti=
on for the actual message (EmailMessage). Am I reading it wrong?<o:p></o:p>=
</span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">Panos<o:p></o:p></span></pre>
<pre><span style=3D"color:black"><o:p>&nbsp;</o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Murray S=
. Kucherawy [mailto:superuser@gmail.com]
<br>
<b>Sent:</b> Sunday, March 03, 2013 4:10 AM<br>
<b>To:</b> Panos Kampanakis (pkampana)<br>
<b>Cc:</b> Moriarty, Kathleen; mile@ietf.org; marf@ietf.org<br>
<b>Subject:</b> Re: [marf] Including Mail fields in IODEF<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The issue with MARF i=
nside IODEF is that the receiver needs to know that the payload being provi=
ded inside an EmailMessage element is itself an ARF report, and not the mes=
sage that caused the report in the first
 place.&nbsp; You certainly could crack open the EmailMessage content and s=
ee if conforms to the ARF specification to tell which kind of report you've=
 gotten, but that seems inelegant.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I suppose then anothe=
r option is an extension element that indicates you've received an ARF payl=
oad rather than the actual offending message.<br>
<br>
Also of note: An ARF can contain the offending message or only the offendin=
g message's header, and still be compliant.&nbsp; If your application needs=
 the whole message, you'll have to add some additional stipulations somepla=
ce.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal">-MSK<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pk=
ampana) &lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_blank">pkampan=
a@cisco.com</a>&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoNormal">I think MARF provides more functionality and should =
be leverage for emails in IODEF.<br>
I also think we need to resurrect <a href=3D"http://tools.ietf.org/html/dra=
ft-vesely-mile-mail-abuse-00" target=3D"_blank">
http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a> within MILE =
since MARF was concluded..<br>
<span class=3D"hoenzb"><span style=3D"color:#888888">Panos</span></span><o:=
p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>] O=
n Behalf Of Moriarty, Kathleen<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Sent: Thursday, February 21, 2013 5:19 AM<br>
To: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a>; <a href=3D"mailto:m=
arf@ietf.org">
marf@ietf.org</a><br>
Subject: [mile] Including Mail fields in IODEF<br>
<br>
Hello,<br>
<br>
Cross posting with MAIL and MARF -<br>
<br>
In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below). &nbsp;We would like some help to figure out the bes=
t approach. &nbsp;Should we embed ARF and
 MARF RFC extensions to accommodate this need or should we look at updating=
 RFC5901? &nbsp;Both take the approach of including an email message as opp=
osed to using XML to tag each field and allow for this in the data model (i=
n my opinion, that is fine and reduces
 bloat, but there may be other opinions).<br>
<br>
There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.<br>
<br>
Thanks,<br>
Kathleen<br>
________________________________________<br>
From: Harrington, Christopher<br>
Sent: Wednesday, February 20, 2013 2:57 PM<br>
To: Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><=
br>
Subject: RE: Mail fields<br>
<br>
I'm for the simplest solution as always. These are the indicator types that=
 we routinely share. I would use these as a base:<br>
<br>
Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email<br>
<br>
It's also very common to share the whole header. Bad guys routinely forge t=
hem and put extra header items that can be used as indicators. &nbsp;Althou=
gh not an indicator sharing the entire email as an .eml or .msg file is als=
o pretty common.<br>
<br>
Thanks,<br>
<br>
--Chris<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>] O=
n Behalf Of Moriarty, Kathleen<br>
Sent: Wednesday, February 20, 2013 2:58 AM<br>
To: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
Subject: [mile] Mail fields<br>
<br>
Hi,<br>
<br>
In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents. &nbsp;A couple of com=
monly exchanged fields were added into
 the Record class. &nbsp;You can still extend out using RFC5901 and include=
 a full mail message, but if you wanted to include DKIM or Sender Policy Fr=
amework, you need something else. &nbsp;The IETF group MARF already solved =
these issues.<br>
<br>
MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:<br>
<a href=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a=
><br>
<br>
Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data? &nbsp;Other options would be to update RFC5901 or to extend I=
ODEF further. &nbsp;I prefer the use of MARF.
 &nbsp;It is already in use by mail operators, so there is adoption.<br>
<br>
Thanks,<br>
Kathleen<br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
marf mailing list<br>
<a href=3D"mailto:marf@ietf.org">marf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/marf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/marf</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_1C9F17D1873AFA47A969C4DD98F98A75187BDAxmbrcdx10ciscocom_--

From superuser@gmail.com  Sun Mar  3 19:46:38 2013
Return-Path: <superuser@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0472021F886D; Sun,  3 Mar 2013 19:46:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qCkQnp-KJpXf; Sun,  3 Mar 2013 19:46:33 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3F121F8717; Sun,  3 Mar 2013 19:46:26 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id k14so4011522wer.39 for <multiple recipients>; Sun, 03 Mar 2013 19:46:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=naGsKMv8T5swkmprE0gZB7mUzsafJiEzxvyQha/2nEg=; b=eNDXEtGN4UkbiXMaqRTCZPMRouNLGS2ObLOrCLbhQshcyrwdWRGnRbUTkMhIbEli7x bP7azDzNiknfF7OnojUpRnGpIlFgwYZRnp/ZUMfEM+0bYYivnVumxXcekJNB6zqEnu7q BGcxdDjOBQgJv4uDSdf7s5Gj4JKI3IQWe/fJnFJ7C6+0YrK07VtV8mH6Q/1/TgtSjJD3 NUxcR68GK+KOqkMmkZJFdDEFeIMfmCPv6EEolKT8NcmWhpez1VG9IFI8lYykAwJo2t/r Y12gJKHzZi0HjCn7AAjFl7PRcFil3beFam6bSyU0606XQ8Q1ik2NckcAJh3J4NHar/55 1DQA==
MIME-Version: 1.0
X-Received: by 10.180.185.44 with SMTP id ez12mr8295760wic.33.1362368786189; Sun, 03 Mar 2013 19:46:26 -0800 (PST)
Received: by 10.180.189.6 with HTTP; Sun, 3 Mar 2013 19:46:26 -0800 (PST)
In-Reply-To: <1C9F17D1873AFA47A969C4DD98F98A75187BDA@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com> <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com> <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com> <CAL0qLwZxwkcJi7Ej0fU5s8k-xZ=n_4fa0cvVVF05YtQPc3Ndag@mail.gmail.com> <1C9F17D1873AFA47A969C4DD98F98A75187BDA@xmb-rcd-x10.cisco.com>
Date: Sun, 3 Mar 2013 19:46:26 -0800
Message-ID: <CAL0qLwaE1pS98kq8XSETMk-kKvCWZnErP3RdKO3CRa5jOXtTnw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c225748dd5dd04d71133ce
Cc: "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [mile] [marf] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 04 Mar 2013 03:46:38 -0000

--001a11c225748dd5dd04d71133ce
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Panos,

The "feedback-type" would be part of the ArfHeader object, I would
imagine.  It appears immediately before the portion of the example you
cited.

This might also be a viable way to add ARF capability to IODEF, though I
don't think that was the original problem statement (which was only to
include DKIM and SPF details).

At any rate, I don't think you're reading it wrong.

-MSK


On Sun, Mar 3, 2013 at 2:37 PM, Panos Kampanakis (pkampana) <
pkampana@cisco.com> wrote:

>  Thank you Murray.****
>
> ** **
>
> The =93<arf:EmailMessage>****
>
>    Received: from mailserver.example.net****
>
>         (mailserver.example.net [192.0.2.1])****
>
>         by example.com with ESMTP id M63d4137594e46;****
>
>         Thu, 08 Mar 2005 14:00:00 -0400****
>
>    From: &lt;somespammer@example.net&gt;****
>
>    To: &lt;Undisclosed Recipients&gt;****
>
>    Subject: Earn money****
>
>    MIME-Version: 1.0****
>
>    Content-type: text/plain****
>
>    Message-ID: 8787KJKJ3K4J3K4J3K4J3.mail@example.net****
>
>    Date: Thu, 02 Sep 2004 12:31:03 -0500****
>
> ** **
>
>    Spam Spam Spam****
>
>    Spam Spam Spam****
>
>    Spam Spam Spam****
>
>    Spam Spam Spam****
>
>          </arf:EmailMessage>=94****
>
> that I see in http://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-=
abuse-00.txt looks like just an email message. I don=92t see =93feedback-ty=
pe" or other ARF fields for example that would make it a ARF.****
>
> ** **
>
> draft-vesely-mile-mail-abuse-00.txt seems to define a header and then hav=
e the option for the actual message (EmailMessage). Am I reading it wrong?*=
***
>
> ** **
>
> Panos****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Murray S. Kucherawy [mailto:superuser@gmail.com]
> *Sent:* Sunday, March 03, 2013 4:10 AM
> *To:* Panos Kampanakis (pkampana)
> *Cc:* Moriarty, Kathleen; mile@ietf.org; marf@ietf.org
> *Subject:* Re: [marf] Including Mail fields in IODEF****
>
> ** **
>
> The issue with MARF inside IODEF is that the receiver needs to know that
> the payload being provided inside an EmailMessage element is itself an AR=
F
> report, and not the message that caused the report in the first place.  Y=
ou
> certainly could crack open the EmailMessage content and see if conforms t=
o
> the ARF specification to tell which kind of report you've gotten, but tha=
t
> seems inelegant.****
>
> I suppose then another option is an extension element that indicates
> you've received an ARF payload rather than the actual offending message.
>
> Also of note: An ARF can contain the offending message or only the
> offending message's header, and still be compliant.  If your application
> needs the whole message, you'll have to add some additional stipulations
> someplace.****
>
> -MSK****
>
> ** **
>
> On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <
> pkampana@cisco.com> wrote:****
>
> I think MARF provides more functionality and should be leverage for email=
s
> in IODEF.
> I also think we need to resurrect
> http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00 within MILE
> since MARF was concluded..
> Panos****
>
>
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen****
>
> Sent: Thursday, February 21, 2013 5:19 AM
> To: mile@ietf.org; marf@ietf.org
> Subject: [mile] Including Mail fields in IODEF
>
> Hello,
>
> Cross posting with MAIL and MARF -
>
> In MILE related work, I have come across use cases that would like to
> include DKIM and SPF information in addition to specific mail fields (lik=
e
> the ones Chris lists below).  We would like some help to figure out the
> best approach.  Should we embed ARF and MARF RFC extensions to accommodat=
e
> this need or should we look at updating RFC5901?  Both take the approach =
of
> including an email message as opposed to using XML to tag each field and
> allow for this in the data model (in my opinion, that is fine and reduces
> bloat, but there may be other opinions).
>
> There was a draft published last year (link included below) that includes
> MARF in an IODE extension.
>
> Thanks,
> Kathleen
> ________________________________________
> From: Harrington, Christopher
> Sent: Wednesday, February 20, 2013 2:57 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: RE: Mail fields
>
> I'm for the simplest solution as always. These are the indicator types
> that we routinely share. I would use these as a base:
>
> Email address (denoting if it is to or from) Email Subject Email
> attachment name Email attachment hash X-Mailer (from header) Hyperlink in
> email
>
> It's also very common to share the whole header. Bad guys routinely forge
> them and put extra header items that can be used as indicators.  Although
> not an indicator sharing the entire email as an .eml or .msg file is also
> pretty common.
>
> Thanks,
>
> --Chris
>
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Wednesday, February 20, 2013 2:58 AM
> To: mile@ietf.org
> Subject: [mile] Mail fields
>
> Hi,
>
> In looking at the updated rfc5070bis and coming across some requests for
> handling certain types of exchanges, I am curious to hear how others thin=
k
> we should handle mail related indicators and incidents.  A couple of
> commonly exchanged fields were added into the Record class.  You can stil=
l
> extend out using RFC5901 and include a full mail message, but if you want=
ed
> to include DKIM or Sender Policy Framework, you need something else.  The
> IETF group MARF already solved these issues.
>
> MARF uses the email tags rather than XML and there was a draft that
> embedded MARF content into IODEF (contains an example), can be found here=
:
> http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00
>
> Since mail is already marked and can be parsed, would this be a better
> option to use what MARF has already done to solve the question on how to
> exchange this data?  Other options would be to update RFC5901 or to exten=
d
> IODEF further.  I prefer the use of MARF.  It is already in use by mail
> operators, so there is adoption.
>
> Thanks,
> Kathleen
> _______________________________________________
> 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
> _______________________________________________
> marf mailing list
> marf@ietf.org
> https://www.ietf.org/mailman/listinfo/marf****
>
> ** **
>

--001a11c225748dd5dd04d71133ce
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Panos,<br><br></div>The &quot;feedback-t=
ype&quot; would be part of the ArfHeader object, I would imagine.=A0 It app=
ears immediately before the portion of the example you cited.<br><br>This m=
ight also be a viable way to add ARF capability to IODEF, though I don&#39;=
t think that was the original problem statement (which was only to include =
DKIM and SPF details).<br>
<br></div>At any rate, I don&#39;t think you&#39;re reading it wrong.<br><b=
r></div>-MSK<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Sun, Mar 3, 2013 at 2:37 PM, Panos Kampanakis (pkampana) <span =
dir=3D"ltr">&lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_blank">pka=
mpana@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thank you Murray.<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">The =93</span><span style>&lt;arf:EmailMess=
age&gt;<u></u><u></u></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Received: from <a href=3D"http://mailserver.example=
.net" target=3D"_blank">mailserver.example.net</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0=A0=A0=A0=A0=A0 (<a href=3D"http://mailserver.exampl=
e.net" target=3D"_blank">mailserver.example.net</a> [192.0.2.1])<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0=A0=A0=A0=A0=A0 by <a href=3D"http://example.com" ta=
rget=3D"_blank">example.com</a> with ESMTP id M63d4137594e46;<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0=A0=A0=A0=A0=A0 Thu, 08 Mar 2005 14:00:00 -0400<u></=
u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 From: &amp;<a href=3D"mailto:lt%3Bsomespammer@examp=
le.net" target=3D"_blank">lt;somespammer@example.net</a>&amp;gt;<u></u><u><=
/u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 To: &amp;lt;Undisclosed Recipients&amp;gt;<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Subject: Earn money<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 MIME-Version: 1.0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Content-type: text/plain<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Message-ID: <a href=3D"mailto:8787KJKJ3K4J3K4J3K4J3=
.mail@example.net" target=3D"_blank">8787KJKJ3K4J3K4J3K4J3.mail@example.net=
</a><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Date: Thu, 02 Sep 2004 12:31:03 -0500<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Spam Spam Spam<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Spam Spam Spam<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Spam Spam Spam<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0 Spam Spam Spam<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=A0=A0=A0=A0=A0=A0=A0=A0 &lt;/arf:EmailMessage&gt;</span><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1f497d">=94<u></u><u></u></span></p>

<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">that I see in <a href=3D"http://bgp.potaroo=
.net/ietf/all-ids/draft-vesely-mile-mail-abuse-00.txt" target=3D"_blank">ht=
tp://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-abuse-00.txt</a> l=
ooks like just an email message. I don=92t see =93</span><span style>feedba=
ck-type</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:#1f497d">&quot; or other ARF fields for exa=
mple that would make it a ARF.<u></u><u></u></span></pre>

<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></pre>
<pre><span style>draft-vesely-mile-mail-abuse-00.txt </span><span style=3D"=
font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1f497d">seems to define a header and then have the option for the actua=
l message (EmailMessage). Am I reading it wrong?<u></u><u></u></span></pre>

<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1f497d">Panos<u></u><u></u></span></pre>
<pre><span style><u></u>=A0<u></u></span></pre>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=A0<u></u></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Murray S=
. Kucherawy [mailto:<a href=3D"mailto:superuser@gmail.com" target=3D"_blank=
">superuser@gmail.com</a>]
<br>
<b>Sent:</b> Sunday, March 03, 2013 4:10 AM<br>
<b>To:</b> Panos Kampanakis (pkampana)<br>
<b>Cc:</b> Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org" target=3D"_=
blank">mile@ietf.org</a>; <a href=3D"mailto:marf@ietf.org" target=3D"_blank=
">marf@ietf.org</a><br>
<b>Subject:</b> Re: [marf] Including Mail fields in IODEF<u></u><u></u></sp=
an></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The issue with MARF i=
nside IODEF is that the receiver needs to know that the payload being provi=
ded inside an EmailMessage element is itself an ARF report, and not the mes=
sage that caused the report in the first
 place.=A0 You certainly could crack open the EmailMessage content and see =
if conforms to the ARF specification to tell which kind of report you&#39;v=
e gotten, but that seems inelegant.<u></u><u></u></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I suppose then anothe=
r option is an extension element that indicates you&#39;ve received an ARF =
payload rather than the actual offending message.<br>
<br>
Also of note: An ARF can contain the offending message or only the offendin=
g message&#39;s header, and still be compliant.=A0 If your application need=
s the whole message, you&#39;ll have to add some additional stipulations so=
meplace.<u></u><u></u></p>

</div>
<p class=3D"MsoNormal">-MSK<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pk=
ampana) &lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_blank">pkampan=
a@cisco.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">I think MARF provides more functionality and should =
be leverage for emails in IODEF.<br>
I also think we need to resurrect <a href=3D"http://tools.ietf.org/html/dra=
ft-vesely-mile-mail-abuse-00" target=3D"_blank">
http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a> within MILE =
since MARF was concluded..<br>
<span><span style=3D"color:#888888">Panos</span></span><u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org" target=3D"_blank">mile-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:mile-bounces@ietf.org" target=3D"=
_blank">mile-bounces@ietf.org</a>] On Behalf Of Moriarty, Kathleen<u></u><u=
></u></p>

</div>
<div>
<div>
<p class=3D"MsoNormal">Sent: Thursday, February 21, 2013 5:19 AM<br>
To: <a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a>; <=
a href=3D"mailto:marf@ietf.org" target=3D"_blank">
marf@ietf.org</a><br>
Subject: [mile] Including Mail fields in IODEF<br>
<br>
Hello,<br>
<br>
Cross posting with MAIL and MARF -<br>
<br>
In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below). =A0We would like some help to figure out the best a=
pproach. =A0Should we embed ARF and
 MARF RFC extensions to accommodate this need or should we look at updating=
 RFC5901? =A0Both take the approach of including an email message as oppose=
d to using XML to tag each field and allow for this in the data model (in m=
y opinion, that is fine and reduces
 bloat, but there may be other opinions).<br>
<br>
There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.<br>
<br>
Thanks,<br>
Kathleen<br>
________________________________________<br>
From: Harrington, Christopher<br>
Sent: Wednesday, February 20, 2013 2:57 PM<br>
To: Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org" target=3D"_blank">=
mile@ietf.org</a><br>
Subject: RE: Mail fields<br>
<br>
I&#39;m for the simplest solution as always. These are the indicator types =
that we routinely share. I would use these as a base:<br>
<br>
Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email<br>
<br>
It&#39;s also very common to share the whole header. Bad guys routinely for=
ge them and put extra header items that can be used as indicators. =A0Altho=
ugh not an indicator sharing the entire email as an .eml or .msg file is al=
so pretty common.<br>

<br>
Thanks,<br>
<br>
--Chris<br>
<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:mile-bounces@ietf.org" target=3D"_blank">mile-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:mile-bounces@ietf.org" target=3D"=
_blank">mile-bounces@ietf.org</a>] On Behalf Of Moriarty, Kathleen<br>
Sent: Wednesday, February 20, 2013 2:58 AM<br>
To: <a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a><br=
>
Subject: [mile] Mail fields<br>
<br>
Hi,<br>
<br>
In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents. =A0A couple of common=
ly exchanged fields were added into
 the Record class. =A0You can still extend out using RFC5901 and include a =
full mail message, but if you wanted to include DKIM or Sender Policy Frame=
work, you need something else. =A0The IETF group MARF already solved these =
issues.<br>

<br>
MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:<br>
<a href=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a=
><br>
<br>
Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data? =A0Other options would be to update RFC5901 or to extend IODE=
F further. =A0I prefer the use of MARF.
 =A0It is already in use by mail operators, so there is adoption.<br>
<br>
Thanks,<br>
Kathleen<br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mile</a><br>
_______________________________________________<br>
marf mailing list<br>
<a href=3D"mailto:marf@ietf.org" target=3D"_blank">marf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/marf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/marf</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
</div></div></div>
</div>

</blockquote></div><br></div>

--001a11c225748dd5dd04d71133ce--

From kathleen.moriarty@emc.com  Tue Mar  5 20:58:19 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D1211E8129; Tue,  5 Mar 2013 20:58:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UuHaC4oZzyJ7; Tue,  5 Mar 2013 20:58:13 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3C811E80ED; Tue,  5 Mar 2013 20:58:13 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r264w91e008637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Mar 2013 23:58:10 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Tue, 5 Mar 2013 23:57:58 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r264vwnk026878; Tue, 5 Mar 2013 23:57:58 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Tue, 5 Mar 2013 23:57:57 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Date: Tue, 5 Mar 2013 23:57:56 -0500
Thread-Topic: [marf] Including Mail fields in IODEF
Thread-Index: Ac4YiuliWLnw6jWnTXaEzQRNpzN0ogBmlGpQ
Message-ID: <F5063677821E3B4F81ACFB7905573F24D796ACC6@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D6253D43@MX15A.corp.emc.com> <B14C10CA81885B4AAE1954F18457F2AB057004DB6D@MX36A.corp.emc.com> <F5063677821E3B4F81ACFB7905573F24D6253D5D@MX15A.corp.emc.com> <1C9F17D1873AFA47A969C4DD98F98A75187684@xmb-rcd-x10.cisco.com> <CAL0qLwZxwkcJi7Ej0fU5s8k-xZ=n_4fa0cvVVF05YtQPc3Ndag@mail.gmail.com> <1C9F17D1873AFA47A969C4DD98F98A75187BDA@xmb-rcd-x10.cisco.com> <CAL0qLwaE1pS98kq8XSETMk-kKvCWZnErP3RdKO3CRa5jOXtTnw@mail.gmail.com>
In-Reply-To: <CAL0qLwaE1pS98kq8XSETMk-kKvCWZnErP3RdKO3CRa5jOXtTnw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24D796ACC6MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "mile@ietf.org" <mile@ietf.org>, "marf@ietf.org" <marf@ietf.org>
Subject: Re: [mile] [marf] Including Mail fields in IODEF
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 06 Mar 2013 04:58:19 -0000

--_000_F5063677821E3B4F81ACFB7905573F24D796ACC6MX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Murray,

I may not have been clear enough in my first message.  I was asking about i=
ncluding ARF to represent any/all mail fields useful in exchanges by includ=
ing ARF.  The option of using RFC5901 with the full mail message would work=
 as well (as you pointed out).  If ARF has wider adoption, it may make sens=
e to use existing standards and tools to accomplish the task by embedding A=
RF in IODEF.  The format covers some data type representations not in IODEF=
, but specific to mail (which makes sense to extend when you get that deep)=
.

Thanks,
Kathleen

From: Murray S. Kucherawy [mailto:superuser@gmail.com]
Sent: Sunday, March 03, 2013 10:46 PM
To: Panos Kampanakis (pkampana)
Cc: Moriarty, Kathleen; mile@ietf.org; marf@ietf.org
Subject: Re: [marf] Including Mail fields in IODEF

Hi Panos,
The "feedback-type" would be part of the ArfHeader object, I would imagine.=
  It appears immediately before the portion of the example you cited.

This might also be a viable way to add ARF capability to IODEF, though I do=
n't think that was the original problem statement (which was only to includ=
e DKIM and SPF details).
At any rate, I don't think you're reading it wrong.
-MSK

On Sun, Mar 3, 2013 at 2:37 PM, Panos Kampanakis (pkampana) <pkampana@cisco=
.com<mailto:pkampana@cisco.com>> wrote:
Thank you Murray.


The "<arf:EmailMessage>
   Received: from mailserver.example.net<http://mailserver.example.net>
        (mailserver.example.net<http://mailserver.example.net> [192.0.2.1])
        by example.com<http://example.com> with ESMTP id M63d4137594e46;
        Thu, 08 Mar 2005 14:00:00 -0400
   From: &lt;somespammer@example.net<mailto:lt%3Bsomespammer@example.net>&g=
t;
   To: &lt;Undisclosed Recipients&gt;
   Subject: Earn money
   MIME-Version: 1.0
   Content-type: text/plain
   Message-ID: 8787KJKJ3K4J3K4J3K4J3.mail@example.net<mailto:8787KJKJ3K4J3K=
4J3K4J3.mail@example.net>
   Date: Thu, 02 Sep 2004 12:31:03 -0500

   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam
   Spam Spam Spam
         </arf:EmailMessage>"

that I see in http://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-ab=
use-00.txt looks like just an email message. I don't see "feedback-type" or=
 other ARF fields for example that would make it a ARF.



draft-vesely-mile-mail-abuse-00.txt seems to define a header and then have =
the option for the actual message (EmailMessage). Am I reading it wrong?



Panos




From: Murray S. Kucherawy [mailto:superuser@gmail.com<mailto:superuser@gmai=
l.com>]
Sent: Sunday, March 03, 2013 4:10 AM
To: Panos Kampanakis (pkampana)
Cc: Moriarty, Kathleen; mile@ietf.org<mailto:mile@ietf.org>; marf@ietf.org<=
mailto:marf@ietf.org>
Subject: Re: [marf] Including Mail fields in IODEF

The issue with MARF inside IODEF is that the receiver needs to know that th=
e payload being provided inside an EmailMessage element is itself an ARF re=
port, and not the message that caused the report in the first place.  You c=
ertainly could crack open the EmailMessage content and see if conforms to t=
he ARF specification to tell which kind of report you've gotten, but that s=
eems inelegant.
I suppose then another option is an extension element that indicates you've=
 received an ARF payload rather than the actual offending message.

Also of note: An ARF can contain the offending message or only the offendin=
g message's header, and still be compliant.  If your application needs the =
whole message, you'll have to add some additional stipulations someplace.
-MSK

On Fri, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) <pkampana@cisco=
.com<mailto:pkampana@cisco.com>> wrote:
I think MARF provides more functionality and should be leverage for emails =
in IODEF.
I also think we need to resurrect http://tools.ietf.org/html/draft-vesely-m=
ile-mail-abuse-00 within MILE since MARF was concluded..
Panos


-----Original Message-----
From: mile-bounces@ietf.org<mailto:mile-bounces@ietf.org> [mailto:mile-boun=
ces@ietf.org<mailto:mile-bounces@ietf.org>] On Behalf Of Moriarty, Kathleen
Sent: Thursday, February 21, 2013 5:19 AM
To: mile@ietf.org<mailto:mile@ietf.org>; marf@ietf.org<mailto:marf@ietf.org=
>
Subject: [mile] Including Mail fields in IODEF

Hello,

Cross posting with MAIL and MARF -

In MILE related work, I have come across use cases that would like to inclu=
de DKIM and SPF information in addition to specific mail fields (like the o=
nes Chris lists below).  We would like some help to figure out the best app=
roach.  Should we embed ARF and MARF RFC extensions to accommodate this nee=
d or should we look at updating RFC5901?  Both take the approach of includi=
ng an email message as opposed to using XML to tag each field and allow for=
 this in the data model (in my opinion, that is fine and reduces bloat, but=
 there may be other opinions).

There was a draft published last year (link included below) that includes M=
ARF in an IODE extension.

Thanks,
Kathleen
________________________________________
From: Harrington, Christopher
Sent: Wednesday, February 20, 2013 2:57 PM
To: Moriarty, Kathleen; mile@ietf.org<mailto:mile@ietf.org>
Subject: RE: Mail fields

I'm for the simplest solution as always. These are the indicator types that=
 we routinely share. I would use these as a base:

Email address (denoting if it is to or from) Email Subject Email attachment=
 name Email attachment hash X-Mailer (from header) Hyperlink in email

It's also very common to share the whole header. Bad guys routinely forge t=
hem and put extra header items that can be used as indicators.  Although no=
t an indicator sharing the entire email as an .eml or .msg file is also pre=
tty common.

Thanks,

--Chris


-----Original Message-----
From: mile-bounces@ietf.org<mailto:mile-bounces@ietf.org> [mailto:mile-boun=
ces@ietf.org<mailto:mile-bounces@ietf.org>] On Behalf Of Moriarty, Kathleen
Sent: Wednesday, February 20, 2013 2:58 AM
To: mile@ietf.org<mailto:mile@ietf.org>
Subject: [mile] Mail fields

Hi,

In looking at the updated rfc5070bis and coming across some requests for ha=
ndling certain types of exchanges, I am curious to hear how others think we=
 should handle mail related indicators and incidents.  A couple of commonly=
 exchanged fields were added into the Record class.  You can still extend o=
ut using RFC5901 and include a full mail message, but if you wanted to incl=
ude DKIM or Sender Policy Framework, you need something else.  The IETF gro=
up MARF already solved these issues.

MARF uses the email tags rather than XML and there was a draft that embedde=
d MARF content into IODEF (contains an example), can be found here:
http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00

Since mail is already marked and can be parsed, would this be a better opti=
on to use what MARF has already done to solve the question on how to exchan=
ge this data?  Other options would be to update RFC5901 or to extend IODEF =
further.  I prefer the use of MARF.  It is already in use by mail operators=
, so there is adoption.

Thanks,
Kathleen
_______________________________________________
mile mailing list
mile@ietf.org<mailto:mile@ietf.org>
https://www.ietf.org/mailman/listinfo/mile
_______________________________________________
mile mailing list
mile@ietf.org<mailto:mile@ietf.org>
https://www.ietf.org/mailman/listinfo/mile
_______________________________________________
marf mailing list
marf@ietf.org<mailto:marf@ietf.org>
https://www.ietf.org/mailman/listinfo/marf



--_000_F5063677821E3B4F81ACFB7905573F24D796ACC6MX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Murray=
,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>I may not have been clear enough in my firs=
t message.&nbsp; I was asking about including ARF to represent any/all mail=
 fields useful in exchanges by including ARF.&nbsp; The option of using RFC=
5901 with the full mail message would work as well (as you pointed out).&nb=
sp; If ARF has wider adoption, it may make sense to use existing standards =
and tools to accomplish the task by embedding ARF in IODEF.&nbsp; The forma=
t covers some data type representations not in IODEF, but specific to mail =
(which makes sense to extend when you get that deep).<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kathleen<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></=
p><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-fam=
ily:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;=
font-family:"Tahoma","sans-serif"'> Murray S. Kucherawy [mailto:superuser@g=
mail.com] <br><b>Sent:</b> Sunday, March 03, 2013 10:46 PM<br><b>To:</b> Pa=
nos Kampanakis (pkampana)<br><b>Cc:</b> Moriarty, Kathleen; mile@ietf.org; =
marf@ietf.org<br><b>Subject:</b> Re: [marf] Including Mail fields in IODEF<=
o:p></o:p></span></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><=
div><div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi Panos,=
<o:p></o:p></p></div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Th=
e &quot;feedback-type&quot; would be part of the ArfHeader object, I would =
imagine.&nbsp; It appears immediately before the portion of the example you=
 cited.<br><br>This might also be a viable way to add ARF capability to IOD=
EF, though I don't think that was the original problem statement (which was=
 only to include DKIM and SPF details).<o:p></o:p></p></div><p class=3DMsoN=
ormal style=3D'margin-bottom:12.0pt'>At any rate, I don't think you're read=
ing it wrong.<o:p></o:p></p></div><p class=3DMsoNormal>-MSK<o:p></o:p></p><=
/div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</=
o:p></p><div><p class=3DMsoNormal>On Sun, Mar 3, 2013 at 2:37 PM, Panos Kam=
panakis (pkampana) &lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_bla=
nk">pkampana@cisco.com</a>&gt; wrote:<o:p></o:p></p><div><div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>Thank you Murray.</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-m=
argin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:11.=
0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o=
:p></p><pre><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-ser=
if";color:#1F497D'>The &#8220;</span>&lt;arf:EmailMessage&gt;<o:p></o:p></p=
re><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;=
&nbsp; Received: from <a href=3D"http://mailserver.example.net" target=3D"_=
blank">mailserver.example.net</a></span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; (<a href=3D"http://mailserver.example.net" target=3D"_blank=
">mailserver.example.net</a> [192.0.2.1])</span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; by <a href=3D"http://example.com" target=3D"_blank">e=
xample.com</a> with ESMTP id M63d4137594e46;</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; Thu, 08 Mar 2005 14:00:00 -0400</span><o:p></o:p>=
</p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom=
-alt:auto'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp=
;&nbsp; From: &amp;<a href=3D"mailto:lt%3Bsomespammer@example.net" target=
=3D"_blank">lt;somespammer@example.net</a>&amp;gt;</span><o:p></o:p></p><p =
class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:au=
to'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;=
 To: &amp;lt;Undisclosed Recipients&amp;gt;</span><o:p></o:p></p><p class=
=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><=
span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Subj=
ect: Earn money</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:10.0pt=
;font-family:"Courier New"'>&nbsp;&nbsp; MIME-Version: 1.0</span><o:p></o:p=
></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbs=
p;&nbsp; Content-type: text/plain</span><o:p></o:p></p><p class=3DMsoNormal=
 style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Message-ID: <a=
 href=3D"mailto:8787KJKJ3K4J3K4J3K4J3.mail@example.net" target=3D"_blank">8=
787KJKJ3K4J3K4J3K4J3.mail@example.net</a></span><o:p></o:p></p><p class=3DM=
soNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span=
 style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; Date: Th=
u, 02 Sep 2004 12:31:03 -0500</span><o:p></o:p></p><p class=3DMsoNormal sty=
le=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'fo=
nt-size:10.0pt;font-family:"Courier New"'>&nbsp;</span><o:p></o:p></p><p cl=
ass=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto=
'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; S=
pam Spam Spam</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New"'>&nbsp;&nbsp; Spam Spam Spam</span><o:p></o:p></p>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nb=
sp; Spam Spam Spam</span><o:p></o:p></p><p class=3DMsoNormal style=3D'mso-m=
argin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size:10.=
0pt;font-family:"Courier New"'>&nbsp;&nbsp; Spam Spam Spam</span><o:p></o:p=
></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-botto=
m-alt:auto'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/arf:EmailMessage&gt;</spa=
n><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>&#8221;</span><o:p></o:p></p><pre><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>that I see in <a href=3D"=
http://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-abuse-00.txt" ta=
rget=3D"_blank">http://bgp.potaroo.net/ietf/all-ids/draft-vesely-mile-mail-=
abuse-00.txt</a> looks like just an email message. I don&#8217;t see &#8220=
;</span>feedback-type<span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&quot; or other ARF fields for example that wou=
ld make it a ARF.</span><o:p></o:p></pre><pre><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:=
p></pre><pre>draft-vesely-mile-mail-abuse-00.txt <span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>seems to define a h=
eader and then have the option for the actual message (EmailMessage). Am I =
reading it wrong?</span><o:p></o:p></pre><pre><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p></o:=
p></pre><pre><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Panos</span><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pr=
e><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto'><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal style=3D'm=
so-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><o:p=
></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin=
-bottom-alt:auto'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","=
sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"T=
ahoma","sans-serif"'> Murray S. Kucherawy [mailto:<a href=3D"mailto:superus=
er@gmail.com" target=3D"_blank">superuser@gmail.com</a>] <br><b>Sent:</b> S=
unday, March 03, 2013 4:10 AM<br><b>To:</b> Panos Kampanakis (pkampana)<br>=
<b>Cc:</b> Moriarty, Kathleen; <a href=3D"mailto:mile@ietf.org" target=3D"_=
blank">mile@ietf.org</a>; <a href=3D"mailto:marf@ietf.org" target=3D"_blank=
">marf@ietf.org</a><br><b>Subject:</b> Re: [marf] Including Mail fields in =
IODEF</span><o:p></o:p></p><div><div><p class=3DMsoNormal style=3D'mso-marg=
in-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p><div><div>=
<div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;margin-bottom:12=
.0pt'>The issue with MARF inside IODEF is that the receiver needs to know t=
hat the payload being provided inside an EmailMessage element is itself an =
ARF report, and not the message that caused the report in the first place.&=
nbsp; You certainly could crack open the EmailMessage content and see if co=
nforms to the ARF specification to tell which kind of report you've gotten,=
 but that seems inelegant.<o:p></o:p></p></div><p class=3DMsoNormal style=
=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>I suppose then another op=
tion is an extension element that indicates you've received an ARF payload =
rather than the actual offending message.<br><br>Also of note: An ARF can c=
ontain the offending message or only the offending message's header, and st=
ill be compliant.&nbsp; If your application needs the whole message, you'll=
 have to add some additional stipulations someplace.<o:p></o:p></p></div><p=
 class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:a=
uto'>-MSK<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'mso-margin=
-top-alt:auto;margin-bottom:12.0pt'>&nbsp;<o:p></o:p></p><div><p class=3DMs=
oNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Fri=
, Mar 1, 2013 at 1:52 PM, Panos Kampanakis (pkampana) &lt;<a href=3D"mailto=
:pkampana@cisco.com" target=3D"_blank">pkampana@cisco.com</a>&gt; wrote:<o:=
p></o:p></p><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margi=
n-bottom-alt:auto'>I think MARF provides more functionality and should be l=
everage for emails in IODEF.<br>I also think we need to resurrect <a href=
=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" target=3D"_=
blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a> withi=
n MILE since MARF was concluded..<br><span style=3D'color:#888888'>Panos</s=
pan><o:p></o:p></p><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:au=
to;mso-margin-bottom-alt:auto'><br><br>-----Original Message-----<br>From: =
<a href=3D"mailto:mile-bounces@ietf.org" target=3D"_blank">mile-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:mile-bounces@ietf.org" target=3D"_blank=
">mile-bounces@ietf.org</a>] On Behalf Of Moriarty, Kathleen<o:p></o:p></p>=
</div><div><div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto'>Sent: Thursday, February 21, 2013 5:19 AM<br>To: <a =
href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a>; <a href=
=3D"mailto:marf@ietf.org" target=3D"_blank">marf@ietf.org</a><br>Subject: [=
mile] Including Mail fields in IODEF<br><br>Hello,<br><br>Cross posting wit=
h MAIL and MARF -<br><br>In MILE related work, I have come across use cases=
 that would like to include DKIM and SPF information in addition to specifi=
c mail fields (like the ones Chris lists below). &nbsp;We would like some h=
elp to figure out the best approach. &nbsp;Should we embed ARF and MARF RFC=
 extensions to accommodate this need or should we look at updating RFC5901?=
 &nbsp;Both take the approach of including an email message as opposed to u=
sing XML to tag each field and allow for this in the data model (in my opin=
ion, that is fine and reduces bloat, but there may be other opinions).<br><=
br>There was a draft published last year (link included below) that include=
s MARF in an IODE extension.<br><br>Thanks,<br>Kathleen<br>________________=
________________________<br>From: Harrington, Christopher<br>Sent: Wednesda=
y, February 20, 2013 2:57 PM<br>To: Moriarty, Kathleen; <a href=3D"mailto:m=
ile@ietf.org" target=3D"_blank">mile@ietf.org</a><br>Subject: RE: Mail fiel=
ds<br><br>I'm for the simplest solution as always. These are the indicator =
types that we routinely share. I would use these as a base:<br><br>Email ad=
dress (denoting if it is to or from) Email Subject Email attachment name Em=
ail attachment hash X-Mailer (from header) Hyperlink in email<br><br>It's a=
lso very common to share the whole header. Bad guys routinely forge them an=
d put extra header items that can be used as indicators. &nbsp;Although not=
 an indicator sharing the entire email as an .eml or .msg file is also pret=
ty common.<br><br>Thanks,<br><br>--Chris<br><br><br>-----Original Message--=
---<br>From: <a href=3D"mailto:mile-bounces@ietf.org" target=3D"_blank">mil=
e-bounces@ietf.org</a> [mailto:<a href=3D"mailto:mile-bounces@ietf.org" tar=
get=3D"_blank">mile-bounces@ietf.org</a>] On Behalf Of Moriarty, Kathleen<b=
r>Sent: Wednesday, February 20, 2013 2:58 AM<br>To: <a href=3D"mailto:mile@=
ietf.org" target=3D"_blank">mile@ietf.org</a><br>Subject: [mile] Mail field=
s<br><br>Hi,<br><br>In looking at the updated rfc5070bis and coming across =
some requests for handling certain types of exchanges, I am curious to hear=
 how others think we should handle mail related indicators and incidents. &=
nbsp;A couple of commonly exchanged fields were added into the Record class=
. &nbsp;You can still extend out using RFC5901 and include a full mail mess=
age, but if you wanted to include DKIM or Sender Policy Framework, you need=
 something else. &nbsp;The IETF group MARF already solved these issues.<br>=
<br>MARF uses the email tags rather than XML and there was a draft that emb=
edded MARF content into IODEF (contains an example), can be found here:<br>=
<a href=3D"http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-vesely-mile-mail-abuse-00</a=
><br><br>Since mail is already marked and can be parsed, would this be a be=
tter option to use what MARF has already done to solve the question on how =
to exchange this data? &nbsp;Other options would be to update RFC5901 or to=
 extend IODEF further. &nbsp;I prefer the use of MARF. &nbsp;It is already =
in use by mail operators, so there is adoption.<br><br>Thanks,<br>Kathleen<=
br>_______________________________________________<br>mile mailing list<br>=
<a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/mile" target=3D"_blank">https=
://www.ietf.org/mailman/listinfo/mile</a><br>______________________________=
_________________<br>mile mailing list<br><a href=3D"mailto:mile@ietf.org" =
target=3D"_blank">mile@ietf.org</a><br><a href=3D"https://www.ietf.org/mail=
man/listinfo/mile" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
mile</a><br>_______________________________________________<br>marf mailing=
 list<br><a href=3D"mailto:marf@ietf.org" target=3D"_blank">marf@ietf.org</=
a><br><a href=3D"https://www.ietf.org/mailman/listinfo/marf" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/marf</a><o:p></o:p></p></div></di=
v></div><p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bo=
ttom-alt:auto'>&nbsp;<o:p></o:p></p></div></div></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_F5063677821E3B4F81ACFB7905573F24D796ACC6MX15Acorpemccom_--

From kathleen.moriarty@emc.com  Wed Mar  6 07:38:13 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12CC21F8A05 for <mile@ietfa.amsl.com>; Wed,  6 Mar 2013 07:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlTopv+eAhT8 for <mile@ietfa.amsl.com>; Wed,  6 Mar 2013 07:38:12 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA7721F8939 for <mile@ietf.org>; Wed,  6 Mar 2013 07:38:11 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r26Fc5kC007294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 6 Mar 2013 10:38:09 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 6 Mar 2013 10:37:58 -0500
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r26Fbw0T027553 for <mile@ietf.org>; Wed, 6 Mar 2013 10:37:58 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Wed, 6 Mar 2013 10:37:57 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Wed, 6 Mar 2013 10:37:56 -0500
Thread-Topic: DNS fields
Thread-Index: Ac4agJMkiPPv901iSGeK0eiK2EWNTQ==
Message-ID: <F5063677821E3B4F81ACFB7905573F24D796AD50@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24D796AD50MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] DNS fields
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 06 Mar 2013 15:38:13 -0000

--_000_F5063677821E3B4F81ACFB7905573F24D796AD50MX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

In trying to figure out how to represent DNS information when exchanging in=
dicators, there seems to be a few options and I'd like to hear opinions to =
guide direction.

Ideally, we would be able to directly reference the DomainData class of RFC=
5901 as it did a really good job of capturing what is needed for DNS during=
 an event.  If the event is not phishing, the required header information f=
or the phishing schema may be out of place.  The only thing that appears to=
 be missing (from use case descriptions) is additional DNS record types (PT=
R, MX, CNAME, TXT, etc.).  It would be nice if we could just reference the =
DomainData class in the IODEF Node class to associate the NodeName provided=
 with the related data, then just add an element for related DNS with an at=
tribute that lets you select the record type.

Since we can't reference it directly, there are a few options (in no partic=
ular order):
a.      Do we change RFC5901 so we can reference portions of the schema dir=
ectly (like we do for the W3C digital signature schema in RFC5070bis)?
b.      Do we use RFC5901 as an extension and maybe add more LureSource typ=
es and let it escape the boundary of being use case specific in case DNS in=
formation is needed when sharing indicators related to other types of attac=
ks?
c.      Do we pull in DomainData and its children into IODEF?
d.      Is there another schema that should be considered for this that is =
also in use (RFC5901 is in use by at least APWG and possibly CIF)?

Or are there other ideas of how this should be handled?

Thank you,
Kathleen


--_000_F5063677821E3B4F81ACFB7905573F24D796AD50MX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri, sans-serif" size=3D"2">
<div>Hi,</div>
<div>&nbsp;</div>
<div>In trying to figure out how to represent DNS information when exchangi=
ng indicators, there seems to be a few options and I&#8217;d like to hear o=
pinions to guide direction.</div>
<div>&nbsp;</div>
<div>Ideally, we would be able to directly reference the DomainData class o=
f RFC5901 as it did a really good job of capturing what is needed for DNS d=
uring an event.&nbsp; If the event is not phishing, the required header inf=
ormation for the phishing schema may
be out of place.&nbsp; The only thing that appears to be missing (from use =
case descriptions) is additional DNS record types (PTR, MX, CNAME, TXT, etc=
.).&nbsp; It would be nice if we could just reference the DomainData class =
in the IODEF Node class to associate the NodeName
provided with the related data, then just add an element for related DNS wi=
th an attribute that lets you select the record type.</div>
<div>&nbsp;</div>
<div>Since we can&#8217;t reference it directly, there are a few options (i=
n no particular order):</div>
<ol type=3D"a" style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: 3=
6pt; ">
<li>Do we change RFC5901 so we can reference portions of the schema directl=
y (like we do for the W3C digital signature schema in RFC5070bis)?</li><li>=
Do we use RFC5901 as an extension and maybe add more LureSource types and l=
et it escape the boundary of being use case specific in case DNS informatio=
n is needed when sharing indicators related to other types of attacks?</li>=
<li>Do we pull in DomainData and its children into IODEF?</li><li>Is there =
another schema that should be considered for this that is also in use (RFC5=
901 is in use by at least APWG and possibly CIF)?</li></ol>
<div>&nbsp;</div>
<div>Or are there other ideas of how this should be handled?</div>
<div>&nbsp;</div>
<div>Thank you,</div>
<div>Kathleen</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_F5063677821E3B4F81ACFB7905573F24D796AD50MX15Acorpemccom_--

From Paul.Stoecker@rsa.com  Thu Mar  7 04:44:31 2013
Return-Path: <Paul.Stoecker@rsa.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C807021F8A4E for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 04:44:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ct5atd5MHHRc for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 04:44:21 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D703221F8CB4 for <mile@ietf.org>; Thu,  7 Mar 2013 04:44:20 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27CiJrG031021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 7 Mar 2013 07:44:19 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 7 Mar 2013 07:44:04 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27Ci4kR024662 for <mile@ietf.org>; Thu, 7 Mar 2013 07:44:04 -0500
Received: from MXHUB103.corp.emc.com (10.253.50.16) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 7 Mar 2013 07:44:04 -0500
Received: from MX103CL01.corp.emc.com ([169.254.5.162]) by MXHUB103.corp.emc.com ([::1]) with mapi id 14.02.0342.003; Thu, 7 Mar 2013 07:44:04 -0500
From: "Stoecker, Paul" <Paul.Stoecker@rsa.com>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Less is More
Thread-Index: Ac4bMXJvoc30rQSbSmWkcAsaLlcWKA==
Date: Thu, 7 Mar 2013 12:44:02 +0000
Message-ID: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <032C9505F7677E4090832C31FC9F1538@mail.corp.emc.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] Less is More
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 12:44:31 -0000

As we have gone through this process of changing IODEF to essentially morph=
 it from something used to share incidents to something used to share indic=
ators, I have been getting the feeling that we are trying to make it everyt=
hing to everybody.

I had thought that the goal was to be able to share IOCs so that the adage =
of "my detection becomes your prevention" will ring true.  If that is our g=
oal isn't there a design paradigm that for efficiency you do the minimum ne=
eded to effectively solve the problem?  To that end, what is the minimum am=
ount of context that we need to share IOCs?  Do we really need to pull in A=
RF, RFC 5901, etc.? =20

Is IODEF really the solution as it was based on sharing Incident Informatio=
n rather than IOCs?  Should IODEF become the Indicator Object Definition Ex=
change Format?  If so, aren't there better ways to handle some of the indic=
ator data..like the System and Node classes being rewritten to handle multi=
ple IPs better?  I guess what I am saying is, if you had to design a schema=
 for the purpose of sharing IOCs starting from nothing would it turn out to=
 look like IODEF or would it be something fundamentally different?

I am not being critical of the work to date or of some of the ideas being p=
ut forward, but I do like to do these types of thought experiments during a=
 design process to make sure that we are happy with the direction and don't=
 need to make any course corrections.  I see all of the discussion about ad=
ding more context and it starts me thinking that we are adding "complexity"=
 and moving away from "less is more". =20

One of the things about me, having spent time in a SOC is that I want to ge=
t immediately down to the issue.  Just tell me what I need to know to detec=
t the malicious activity.  Once I find it I can take some very coarse, rudi=
mentary actions to protect my environment while it gets escalated to a team=
 to research it and gather the context needed to create effective long-term=
 permanent solutions.  Hence my concerns about trying to do too much with I=
ODEF.

Anyway, this is what happens when I am on holiday and my mind frees up to t=
hink about things ;-).=20

Regards,

Paul

Sent from my iPad=

From kathleen.moriarty@emc.com  Thu Mar  7 05:50:11 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9244621F8C68 for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 05:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.355
X-Spam-Level: 
X-Spam-Status: No, score=-0.355 tagged_above=-999 required=5 tests=[AWL=-2.244, BAYES_00=-2.599, FRT_STOCK2=3.988, GB_ABOUTYOU=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWl4ZQ6YWB8d for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 05:50:11 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D24F221F8B1C for <mile@ietf.org>; Thu,  7 Mar 2013 05:50:10 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27Do8EM023314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 7 Mar 2013 08:50:08 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 7 Mar 2013 08:49:39 -0500
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27DncmE025872 for <mile@ietf.org>; Thu, 7 Mar 2013 08:49:38 -0500
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Thu, 7 Mar 2013 08:49:38 -0500
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Stoecker, Paul" <Paul.Stoecker@rsa.com>, "mile@ietf.org" <mile@ietf.org>
Date: Thu, 7 Mar 2013 08:49:37 -0500
Thread-Topic: Less is More
Thread-Index: Ac4bMXJvoc30rQSbSmWkcAsaLlcWKAABcY4A
Message-ID: <F5063677821E3B4F81ACFB7905573F24D796AE70@MX15A.corp.emc.com>
References: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
In-Reply-To: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Less is More
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 13:50:11 -0000

Hi Paul & others,

Do you have some suggestions of what you would like to see change?  I perso=
nally agree that it would be nice to be able to handle multiple IPs better.=
  The watchlist-souce and watchlist-dest in examples doesn't really help ov=
er what was in place, although it does let you see that the grouping provid=
ed is an OR with the rest of the content in the EventData container.  As yo=
u or others come up with alternatives, please discuss them!

As for DNS and email, this data is exchanged today to help with the phishin=
g, mail abuse, and other attacks.  If we use ARF for those use cases, then =
only the parties and products interested in sharing that data will invoke t=
he use of ARF.  The rest may send a message to say the schema isn't support=
ed, but be able to parse the IODEF core of the document.  For the DomainDat=
a, I am working on a use case that asks for domain data to be exchanged in =
case the dns information changed (fraudulent).  This is used today by the A=
PWG when they track down anti-phishing and other CIRT teams use this data a=
s well (from interviews, etc.).  Either ARF or RFC5901 is needed to represe=
nt all of the fields needed for email.  We have the common actionable ones =
in the schema now (up for review), then extend out for more detailed inform=
ation.  Do you have a different approach that should be considered?

You brought up two other concerns.  One was on the size, doesn't the use of=
 extensions or other schemas address that concern?  You would only use the =
other schemas or extensions you need and wouldn't have to support all of th=
em.  My understanding of the changes is that we are trying to represent all=
 of the commonly exchanged indicators in the core and then extend out.  If =
supporting Domain information is not common enough, then it should be an ex=
tension (either RFC5901 or another schema).  If it is, then how do we handl=
e it?  These are questions for the list to guide the direction.  We are jus=
t at a draft stage.

I'd like to hear from others, but when I work with people to look at what t=
hey want to exchange, the data isn't useful unless you have some context.  =
This may have to do with the way we are sharing data in sharing groups vers=
us how you might send updates to a product that helps with detection/preven=
tion.  You can be very targeted in the latter case as the system can interp=
ret and take actions as opposed to when indicator data is received today wh=
ere context is needed to make decisions about your mitigating actions.  If =
you don't know enough about an indicator, you don't know what mitigations y=
ou can put in place.  If an IP is a command and control server versus a bot=
net, your actions will vary.

Any ideas?  It's good to get this discussion going as we iterate through a =
few changes and meet next week.  What lines do we draw for the core schema,=
 what needs to change and doesn't work well today, what does work well toda=
y, and what recommendations do folks want to make?

Thanks,
Kathleen

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sto=
ecker, Paul
Sent: Thursday, March 07, 2013 7:44 AM
To: mile@ietf.org
Subject: [mile] Less is More

As we have gone through this process of changing IODEF to essentially morph=
 it from something used to share incidents to something used to share indic=
ators, I have been getting the feeling that we are trying to make it everyt=
hing to everybody.

I had thought that the goal was to be able to share IOCs so that the adage =
of "my detection becomes your prevention" will ring true.  If that is our g=
oal isn't there a design paradigm that for efficiency you do the minimum ne=
eded to effectively solve the problem?  To that end, what is the minimum am=
ount of context that we need to share IOCs?  Do we really need to pull in A=
RF, RFC 5901, etc.? =20

Is IODEF really the solution as it was based on sharing Incident Informatio=
n rather than IOCs?  Should IODEF become the Indicator Object Definition Ex=
change Format?  If so, aren't there better ways to handle some of the indic=
ator data..like the System and Node classes being rewritten to handle multi=
ple IPs better?  I guess what I am saying is, if you had to design a schema=
 for the purpose of sharing IOCs starting from nothing would it turn out to=
 look like IODEF or would it be something fundamentally different?

I am not being critical of the work to date or of some of the ideas being p=
ut forward, but I do like to do these types of thought experiments during a=
 design process to make sure that we are happy with the direction and don't=
 need to make any course corrections.  I see all of the discussion about ad=
ding more context and it starts me thinking that we are adding "complexity"=
 and moving away from "less is more". =20

One of the things about me, having spent time in a SOC is that I want to ge=
t immediately down to the issue.  Just tell me what I need to know to detec=
t the malicious activity.  Once I find it I can take some very coarse, rudi=
mentary actions to protect my environment while it gets escalated to a team=
 to research it and gather the context needed to create effective long-term=
 permanent solutions.  Hence my concerns about trying to do too much with I=
ODEF.

Anyway, this is what happens when I am on holiday and my mind frees up to t=
hink about things ;-).=20

Regards,

Paul

Sent from my iPad
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile


From pinkerton@anl.gov  Thu Mar  7 05:56:11 2013
Return-Path: <pinkerton@anl.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6399821F8C2C for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 05:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.389
X-Spam-Level: *
X-Spam-Status: No, score=1.389 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ll1PFqBHxxN0 for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 05:56:10 -0800 (PST)
Received: from NAGURSKI.anl.gov (nagurski.anl.gov [146.137.81.22]) by ietfa.amsl.com (Postfix) with ESMTP id B984F21F8C16 for <mile@ietf.org>; Thu,  7 Mar 2013 05:56:10 -0800 (PST)
Received: from HALAS.anl.gov ([169.254.3.159]) by NAGURSKI.anl.gov ([2002:9289:5116::9289:5116]) with mapi id 14.02.0342.003; Thu, 7 Mar 2013 05:56:10 -0800
From: "Pinkerton, Scott C." <pinkerton@anl.gov>
To: "Stoecker, Paul" <Paul.Stoecker@rsa.com>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] Less is More
Thread-Index: Ac4bMXJvoc30rQSbSmWkcAsaLlcWKAACgwUA
Date: Thu, 7 Mar 2013 13:56:09 +0000
Message-ID: <CD5DF629.2B30F%pinkerton@anl.gov>
In-Reply-To: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [146.137.81.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AD396D92B0A5A94EAD6A067F6E735118@localhost>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Less is More
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 13:56:11 -0000

I very much like this term "my detection becomes your prevention".

Here in the Department of Energy - we were using "Detect locally, Protect
globally".

With that said, we have often talked about the need for a very rich set of
suggested actions to accompany indicators. Many people think that we
(within DOE) are merely trying to pass around a "block list."

At times, we would like to be able to suggest a wide range of actions,
such as:

- route IP as normal, but do full packet capture
- route IP to a Honeypot
- block IP

Another thing that we have found over time - it was important for our
information/indicator sharing infrastructure to include a "revocation"
capability.

Over the years, we have had our fair share of ooops - where someone
detected something, and advertised it as being hostile. Then came to find
out the error was internal with their tools, and that the IP wasn't really
hostile. For us, it was important to be able to re-distribute an alert on
that same IP, but with a new suggested action being to revoke the
blocking, revoke the packet capture, etc.

-scott


On 3/7/13 6:44 AM, "Stoecker, Paul" <Paul.Stoecker@rsa.com> wrote:

>As we have gone through this process of changing IODEF to essentially
>morph it from something used to share incidents to something used to
>share indicators, I have been getting the feeling that we are trying to
>make it everything to everybody.
>
>I had thought that the goal was to be able to share IOCs so that the
>adage of "my detection becomes your prevention" will ring true.  If that
>is our goal isn't there a design paradigm that for efficiency you do the
>minimum needed to effectively solve the problem?  To that end, what is
>the minimum amount of context that we need to share IOCs?  Do we really
>need to pull in ARF, RFC 5901, etc.?
>
>Is IODEF really the solution as it was based on sharing Incident
>Information rather than IOCs?  Should IODEF become the Indicator Object
>Definition Exchange Format?  If so, aren't there better ways to handle
>some of the indicator data..like the System and Node classes being
>rewritten to handle multiple IPs better?  I guess what I am saying is, if
>you had to design a schema for the purpose of sharing IOCs starting from
>nothing would it turn out to look like IODEF or would it be something
>fundamentally different?
>
>I am not being critical of the work to date or of some of the ideas being
>put forward, but I do like to do these types of thought experiments
>during a design process to make sure that we are happy with the direction
>and don't need to make any course corrections.  I see all of the
>discussion about adding more context and it starts me thinking that we
>are adding "complexity" and moving away from "less is more".
>
>One of the things about me, having spent time in a SOC is that I want to
>get immediately down to the issue.  Just tell me what I need to know to
>detect the malicious activity.  Once I find it I can take some very
>coarse, rudimentary actions to protect my environment while it gets
>escalated to a team to research it and gather the context needed to
>create effective long-term permanent solutions.  Hence my concerns about
>trying to do too much with IODEF.
>
>Anyway, this is what happens when I am on holiday and my mind frees up to
>think about things ;-).
>
>Regards,
>
>Paul
>
>Sent from my iPad
>_______________________________________________
>mile mailing list
>mile@ietf.org
>https://www.ietf.org/mailman/listinfo/mile


From pkampana@cisco.com  Thu Mar  7 06:58:06 2013
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1C121F8C8D for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 06:58:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.111
X-Spam-Level: 
X-Spam-Status: No, score=-6.111 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sa6MKYtyOjca for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 06:58:05 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A653A21F8C78 for <mile@ietf.org>; Thu,  7 Mar 2013 06:58:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6254; q=dns/txt; s=iport; t=1362668285; x=1363877885; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=NPZkTkzLocKJCegMFB5Zd7dIuUM16IAJsCyb3iJXYAM=; b=kNLwVoL97B6DUqFuLan0nor6foFElCFDQx6+xbylh+FHzVqVjTY3X1aT GWEhkj39V6yvO/T9hlUvMbrsbI55fzyLNYcyLRIE/9Um7g/j/H9h0X+v0 lIg7GlNKdkuNzRrT1MzC4pmewtfTyP4GHEQChA1n0wPAB7sClc/2opvL5 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAMyqOFGtJV2b/2dsb2JhbABDxESBXBZzgisBAQEEAQEBNx8VBhEEAgEIEQQBAQsUCQcnCxQJCAEBBAESCBOHeAy6WASNSgEQgQAmEgaCWWEDpzyDCYFyNQ
X-IronPort-AV: E=Sophos;i="4.84,803,1355097600"; d="scan'208";a="184863891"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 07 Mar 2013 14:58:05 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r27Ew446001307 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Mar 2013 14:58:04 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Thu, 7 Mar 2013 08:58:04 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "Stoecker, Paul" <Paul.Stoecker@rsa.com>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Less is More
Thread-Index: Ac4bMXJvoc30rQSbSmWkcAsaLlcWKAABcY4AAAMqK8A=
Date: Thu, 7 Mar 2013 14:58:03 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A7518C845@xmb-rcd-x10.cisco.com>
References: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com> <F5063677821E3B4F81ACFB7905573F24D796AE70@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D796AE70@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.63.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Less is More
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 14:58:06 -0000

If IOC can describe NameServers and phishing email fields that are needed, =
I also concur to reuse them withi IODEF potentially using Take's draft.
I am not sure it can though.
Panos


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Thursday, March 07, 2013 8:50 AM
To: Stoecker, Paul; mile@ietf.org
Subject: Re: [mile] Less is More

Hi Paul & others,

Do you have some suggestions of what you would like to see change?  I perso=
nally agree that it would be nice to be able to handle multiple IPs better.=
  The watchlist-souce and watchlist-dest in examples doesn't really help ov=
er what was in place, although it does let you see that the grouping provid=
ed is an OR with the rest of the content in the EventData container.  As yo=
u or others come up with alternatives, please discuss them!

As for DNS and email, this data is exchanged today to help with the phishin=
g, mail abuse, and other attacks.  If we use ARF for those use cases, then =
only the parties and products interested in sharing that data will invoke t=
he use of ARF.  The rest may send a message to say the schema isn't support=
ed, but be able to parse the IODEF core of the document.  For the DomainDat=
a, I am working on a use case that asks for domain data to be exchanged in =
case the dns information changed (fraudulent).  This is used today by the A=
PWG when they track down anti-phishing and other CIRT teams use this data a=
s well (from interviews, etc.).  Either ARF or RFC5901 is needed to represe=
nt all of the fields needed for email.  We have the common actionable ones =
in the schema now (up for review), then extend out for more detailed inform=
ation.  Do you have a different approach that should be considered?

You brought up two other concerns.  One was on the size, doesn't the use of=
 extensions or other schemas address that concern?  You would only use the =
other schemas or extensions you need and wouldn't have to support all of th=
em.  My understanding of the changes is that we are trying to represent all=
 of the commonly exchanged indicators in the core and then extend out.  If =
supporting Domain information is not common enough, then it should be an ex=
tension (either RFC5901 or another schema).  If it is, then how do we handl=
e it?  These are questions for the list to guide the direction.  We are jus=
t at a draft stage.

I'd like to hear from others, but when I work with people to look at what t=
hey want to exchange, the data isn't useful unless you have some context.  =
This may have to do with the way we are sharing data in sharing groups vers=
us how you might send updates to a product that helps with detection/preven=
tion.  You can be very targeted in the latter case as the system can interp=
ret and take actions as opposed to when indicator data is received today wh=
ere context is needed to make decisions about your mitigating actions.  If =
you don't know enough about an indicator, you don't know what mitigations y=
ou can put in place.  If an IP is a command and control server versus a bot=
net, your actions will vary.

Any ideas?  It's good to get this discussion going as we iterate through a =
few changes and meet next week.  What lines do we draw for the core schema,=
 what needs to change and doesn't work well today, what does work well toda=
y, and what recommendations do folks want to make?

Thanks,
Kathleen

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sto=
ecker, Paul
Sent: Thursday, March 07, 2013 7:44 AM
To: mile@ietf.org
Subject: [mile] Less is More

As we have gone through this process of changing IODEF to essentially morph=
 it from something used to share incidents to something used to share indic=
ators, I have been getting the feeling that we are trying to make it everyt=
hing to everybody.

I had thought that the goal was to be able to share IOCs so that the adage =
of "my detection becomes your prevention" will ring true.  If that is our g=
oal isn't there a design paradigm that for efficiency you do the minimum ne=
eded to effectively solve the problem?  To that end, what is the minimum am=
ount of context that we need to share IOCs?  Do we really need to pull in A=
RF, RFC 5901, etc.? =20

Is IODEF really the solution as it was based on sharing Incident Informatio=
n rather than IOCs?  Should IODEF become the Indicator Object Definition Ex=
change Format?  If so, aren't there better ways to handle some of the indic=
ator data..like the System and Node classes being rewritten to handle multi=
ple IPs better?  I guess what I am saying is, if you had to design a schema=
 for the purpose of sharing IOCs starting from nothing would it turn out to=
 look like IODEF or would it be something fundamentally different?

I am not being critical of the work to date or of some of the ideas being p=
ut forward, but I do like to do these types of thought experiments during a=
 design process to make sure that we are happy with the direction and don't=
 need to make any course corrections.  I see all of the discussion about ad=
ding more context and it starts me thinking that we are adding "complexity"=
 and moving away from "less is more". =20

One of the things about me, having spent time in a SOC is that I want to ge=
t immediately down to the issue.  Just tell me what I need to know to detec=
t the malicious activity.  Once I find it I can take some very coarse, rudi=
mentary actions to protect my environment while it gets escalated to a team=
 to research it and gather the context needed to create effective long-term=
 permanent solutions.  Hence my concerns about trying to do too much with I=
ODEF.

Anyway, this is what happens when I am on holiday and my mind frees up to t=
hink about things ;-).=20

Regards,

Paul

Sent from my iPad
_______________________________________________
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 Christopher.Harrington@emc.com  Thu Mar  7 07:21:57 2013
Return-Path: <Christopher.Harrington@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7FFD21F8D2D for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 07:21:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.389
X-Spam-Level: *
X-Spam-Status: No, score=1.389 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STOCK2=3.988]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58HAphkPWVCf for <mile@ietfa.amsl.com>; Thu,  7 Mar 2013 07:21:56 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 128CD21F88BE for <mile@ietf.org>; Thu,  7 Mar 2013 07:21:52 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27FLqRF016504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 7 Mar 2013 10:21:52 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 7 Mar 2013 10:21:41 -0500
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r27FLeJk003991 for <mile@ietf.org>; Thu, 7 Mar 2013 10:21:40 -0500
Received: from mx36a.corp.emc.com ([169.254.1.157]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Thu, 7 Mar 2013 10:21:39 -0500
From: "Harrington, Christopher" <Christopher.Harrington@emc.com>
To: "Stoecker, Paul" <Paul.Stoecker@rsa.com>, "mile@ietf.org" <mile@ietf.org>
Date: Thu, 7 Mar 2013 10:21:38 -0500
Thread-Topic: Less is More
Thread-Index: Ac4bMXJvoc30rQSbSmWkcAsaLlcWKAAEvZ1Q
Message-ID: <B14C10CA81885B4AAE1954F18457F2AB0571A48235@MX36A.corp.emc.com>
References: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
In-Reply-To: <82B14152-7F29-49A0-90E9-3D1414B9D4F0@rsa.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0067_01CE1B1D.8DAFE700"
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Less is More
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 07 Mar 2013 15:21:58 -0000

------=_NextPart_000_0067_01CE1B1D.8DAFE700
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Taking a step back I have less of an issue with the approach to the problem
as I see it defined. On that note what problem are we trying to solve? Are
we sharing IoCs or more generic sharing of threat data? The use cases seem
to support the latter. There is an important distinction between the two as
Paul pointed out. Let's take the phishing email as an example. We share
indicators of that activity, with the purpose of detection and potential
mitigation, on a daily basis. The actual email is never shared as the email
isn't an IoC. The discrete elements of the email that can be used to detect
and block the activity are the IoCs.  Similarly with the DDoS use case there
is data being shared that are not IoCs. To complicate things there is no way
to denote what should be considered an IoC and what isn't. 

If we have to support the more generic information sharing that includes
data from those use cases that are not IoCs then pulling in external schemas
is probably a requirement. Unless we want to rewrite IODEF to support it all
natively which I don't think we do.  If the goal is to share IoCs only then
we could extend IODEF natively to cover the vast majority of indicator types
with minimal external schemas. This is where Paul and I are getting hung up
as practitioners. We are talking about IoCs but also discussing sharing data
that is not IoCs. Supporting both types of data is going to be complicated
and probably a bit ugly. 

Thanks,

--Chris

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
Stoecker, Paul
Sent: Thursday, March 07, 2013 7:44 AM
To: mile@ietf.org
Subject: [mile] Less is More

As we have gone through this process of changing IODEF to essentially morph
it from something used to share incidents to something used to share
indicators, I have been getting the feeling that we are trying to make it
everything to everybody.

I had thought that the goal was to be able to share IOCs so that the adage
of "my detection becomes your prevention" will ring true.  If that is our
goal isn't there a design paradigm that for efficiency you do the minimum
needed to effectively solve the problem?  To that end, what is the minimum
amount of context that we need to share IOCs?  Do we really need to pull in
ARF, RFC 5901, etc.?  

Is IODEF really the solution as it was based on sharing Incident Information
rather than IOCs?  Should IODEF become the Indicator Object Definition
Exchange Format?  If so, aren't there better ways to handle some of the
indicator data..like the System and Node classes being rewritten to handle
multiple IPs better?  I guess what I am saying is, if you had to design a
schema for the purpose of sharing IOCs starting from nothing would it turn
out to look like IODEF or would it be something fundamentally different?

I am not being critical of the work to date or of some of the ideas being
put forward, but I do like to do these types of thought experiments during a
design process to make sure that we are happy with the direction and don't
need to make any course corrections.  I see all of the discussion about
adding more context and it starts me thinking that we are adding
"complexity" and moving away from "less is more".  

One of the things about me, having spent time in a SOC is that I want to get
immediately down to the issue.  Just tell me what I need to know to detect
the malicious activity.  Once I find it I can take some very coarse,
rudimentary actions to protect my environment while it gets escalated to a
team to research it and gather the context needed to create effective
long-term permanent solutions.  Hence my concerns about trying to do too
much with IODEF.

Anyway, this is what happens when I am on holiday and my mind frees up to
think about things ;-). 

Regards,

Paul

Sent from my iPad
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile


------=_NextPart_000_0067_01CE1B1D.8DAFE700
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIY1zCCA2Ew
ggJJoAMCAQICEAoBAQEAAAJ8AAAACgAAAAIwDQYJKoZIhvcNAQEFBQAwOjEZMBcGA1UEChMQUlNB
IFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMwHhcNMDEwMjIyMjAz
OTIzWhcNMjYwMjIyMjAzOTIzWjA6MRkwFwYDVQQKExBSU0EgU2VjdXJpdHkgSW5jMR0wGwYDVQQL
ExRSU0EgU2VjdXJpdHkgMjA0OCBWMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALeP
VXHSgN17aXmn8BhQMjxiZ/YKlQfd5hvzntnSQVRrrZ98vhnN+0arQWgeGOpVyC+ReIko+ycpYP/f
j4w7yUmbtaSUzgHqPrVje38m/RndwCG9hNEtT0bDTtzYNzk7KK/LnRrqK68hpcEjIri4G1oTh1eD
0fAg5+hPI0KwAKV9ienpYXOUmHEmvC1q4PdN8PG2KjgxgQ0p4QDBUQ9MUvgEWqp9ctO4hyq7YxAD
KrOhTw1aXka3PQ71dOyZn/k9JIGIpt1gVOiVNj3GCZOaoxKAAFWZGUe90KV8w7r7H/f1D/isubX0
N5gTGN6FW7cMgjuHb5U5WDDabgFoFyLMwAsCAwEAAaNjMGEwDwYDVR0TAQH/BAUwAwEB/zAOBgNV
HQ8BAf8EBAMCAQYwHwYDVR0jBBgwFoAUB8NRMKSq6UWuNST6/yQsM9CxnYwwHQYDVR0OBBYEFAfD
UTCkqulFrjUk+v8kLDPQsZ2MMA0GCSqGSIb3DQEBBQUAA4IBAQBfPoZ2brg1PE42HB55mL/91RIR
eVIO7jGJvN1/+dHGFSHoigFUDTr7VLnWY9SxqpZNokJN1FMfixDef2W+YBMncYikc+OEY9GkVeFQ
k+YbDnnQZ7xGyL8/Fw2V5saQad7ntC/elX3QEj89Pn9NPxRo9RFQ1cH0kKUIHTFg/2CMI1QKr/6h
bsXReipoeM8eggogtB+t5YWyamh1Tq0lN5SFvr2h1Oq3DEs8negSAPBfrA3hrHBjc/d/eZ8yJUJ0
BYAov73BJJZYFbEXIemJS9sHiGf0Fa1wPi9NhTvCt9v+mGgjieF0D970xYRjKRvMywfJAKSp18Ii
T2fXd+wgBWHeMIIEzDCCA7SgAwIBAgIQfwkpTisxI69dQcDR3n6N2TANBgkqhkiG9w0BAQUFADA6
MRkwFwYDVQQKExBSU0EgU2VjdXJpdHkgSW5jMR0wGwYDVQQLExRSU0EgU2VjdXJpdHkgMjA0OCBW
MzAeFw0xMTAzMDMyMDUyMTVaFw0xOTA0MDExNDQ1MzlaMIGXMQswCQYDVQQGEwJVUzEWMBQGA1UE
CBMNTWFzc2FjaHVzZXR0czEQMA4GA1UEBxMHQmVkZm9yZDEZMBcGA1UEChMQUlNBIFNlY3VyaXR5
IExMQzElMCMGA1UECxMcR2xvYmFsIFNlY3VyaXR5IE9yZ2FuaXphdGlvbjEcMBoGA1UEAxMTUlNB
IENvcnBvcmF0ZSBDQSB2MjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALaLCcEh7lhj
dqYo6ryZ8oHK4kJRmQuxfwMa/3PE1Vd4U7U5x15UuSX+qd78hnEdR6yGGxhmY8U2SDG31u+yJD9o
OpXFQm6/A4xzItwfcs6SD3Gt6nI/Oa6M0M/7MjPqSc1aUUm2NFiyb6DjotYLDzeAVCqF+4V/Dgc2
QdO1FZeFUCcb5lMqkVAr+O3uAEZEmtD3Cr06YavA38fxeWCiPoheUuWuAQcvOdEnSzJFm6GM8yBJ
l9J1cAibE6c4DCl+eHj4M+O/ON2fFVb/lQdS4xO7cSZ9fKGCI7kWr0/7ssSjPsIIGpg0hLRZ35aZ
fCK1fFLi9VKvIcTYTrA8Gf9bIGsCAwEAAaOCAW4wggFqMB8GA1UdIwQYMBaAFAfDUTCkqulFrjUk
+v8kLDPQsZ2MMBIGA1UdEwEB/wQIMAYBAf8CAQMwcAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3
dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0
YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwHQYDVR0OBBYEFHMbOEsly1qOvQLs310p9hB0
DtiYMIGRBgNVHSAEgYkwgYYwgYMGCSqGSIb3DQUGATB2MC4GCCsGAQUFBwIBFiJodHRwOi8vY2Eu
cnNhc2VjdXJpdHkuY29tL0NQUy5odG1sMEQGCCsGAQUFBwICMDgwFxYQUlNBIFNlY3VyaXR5IExM
QzADAgEBGh1DUFMgSW5jb3Jwb3JhdGVkIGJ5IHJlZmVyZW5jZTAOBgNVHQ8BAf8EBAMCAYYwDQYJ
KoZIhvcNAQEFBQADggEBAHGIVCAjCZ+z2vRElolRsLsz4L/js0Zm019rr/+eFks5VnSf5T0HJj7Z
tzjtna/+O5b01L8L6Fz64Yui+h/cnxvDwQrhzajbiMiN/JFH+kNOUJ9LcInBkmu45d98h+EQw3Yz
XwfnHYaXLArfgeY3CP8AYi0pxXEXf0bH8Prl+P0n4SOUqxh6J0GIz/haW1+usvMscB7lCpJ2loo9
+TmRn3WQrokgr1ILm/3apel6ydpkoFUxEoP5a1806Z7SD9KljN+Vc9o521VkMtnzLlDEkn05by/p
QNdlidY7eV7xcpCvuI6qFzyfHdI3G0/Vao0L0os6lEwb5PSa1IysLlHT0uUwggT+MIID5qADAgEC
AhBiTV1a7zr4E+gcgJ4lG6TBMA0GCSqGSIb3DQEBBQUAMIGXMQswCQYDVQQGEwJVUzEWMBQGA1UE
CBMNTWFzc2FjaHVzZXR0czEQMA4GA1UEBxMHQmVkZm9yZDEZMBcGA1UEChMQUlNBIFNlY3VyaXR5
IExMQzElMCMGA1UECxMcR2xvYmFsIFNlY3VyaXR5IE9yZ2FuaXphdGlvbjEcMBoGA1UEAxMTUlNB
IENvcnBvcmF0ZSBDQSB2MjAeFw0xMTAzMTAyMjQwMDRaFw0xOTAyMjgyMTU2MzNaMIGeMQswCQYD
VQQGEwJVUzEWMBQGA1UECBMNTWFzc2FjaHVzZXR0czEQMA4GA1UEBxMHQmVkZm9yZDEZMBcGA1UE
ChMQUlNBIFNlY3VyaXR5IExMQzElMCMGA1UECxMcR2xvYmFsIFNlY3VyaXR5IE9yZ2FuaXphdGlv
bjEjMCEGA1UEAxMaUlNBIENsYXNzIDIgUGVyc29uYWwgQ0EgdjIwggEiMA0GCSqGSIb3DQEBAQUA
A4IBDwAwggEKAoIBAQDNEVsNPFZOP83bMzCpUDGnf/5IDIQvVRhDHkyrkbv5X1ih4xdTsSdzTDrj
LUxIzC7nJswCv+jBaWWm1YoqzBXqQl2/Hl6T5Bt3HBT302GSYamtKcCWve25DoJav+dJd9U/XkCq
SSNN7DNVXkJrKC7Zq7OS6/O308pZNkCRJJfMRrodgSx1NoQYZJCfufTOshslVSVhj3Ar274qmuf8
iqM0RR5OMpm7t2dtHzvYJPHR3+HwfQ+s64YBC7NBrBLOYMeq8tzkPKzyITXhwopgbM6gbp+Z8qX5
/lo4Y3OEm7ED51iDqdruRoRnfTQGKdZJT7IYGLH+x0roRKmYKP/2HRNpAgMBAAGjggE7MIIBNzAP
BgNVHRMECDAGAQH/AgECMIGRBgNVHSAEgYkwgYYwgYMGCSqGSIb3DQUHAjB2MC4GCCsGAQUFBwIB
FiJodHRwOi8vY2EucnNhc2VjdXJpdHkuY29tL0NQUy5odG1sMEQGCCsGAQUFBwICMDgwFxYQUlNB
IFNlY3VyaXR5IExMQzADAgEBGh1DUFMgSW5jb3Jwb3JhdGVkIGJ5IHJlZmVyZW5jZTBABgNVHR8E
OTA3MDWgM6Axhi9odHRwOi8vY3JsLnJzYXNlY3VyaXR5LmNvbS9SU0FDb3Jwb3JhdGVDQXYyLmNy
bDAOBgNVHQ8BAf8EBAMCAYYwHQYDVR0OBBYEFBQw62v19Em1aFJ1ptu9rlvIrH1MMB8GA1UdIwQY
MBaAFHMbOEsly1qOvQLs310p9hB0DtiYMA0GCSqGSIb3DQEBBQUAA4IBAQCPepLT4buLa9p5VwF1
OW2YUwliCqxecs0CxRGJVR4cwvOuMeXxutP+m51n3vzseGkM0d1fmA9JTz8X+5LFdRD12Iw124oj
79QA7NKhO/xoPgbo0QxgnvHS15o94BPvFiZE6QGUjkHs9/hDvU+eIx7OG+Kzxt47vZZef+fJF0+s
ZgEDIMXXPXAtJW3xg/JhPrl4z0L7gmjgO+KxV0cyxaDrk6SEW5zZCqAcLehnW7MH8vvlzMsQ6pVr
f1g8xMCJonyxow9AwXGyQ0z1866qbJ8t+nQC/sGx3msJVHQg1JyjOWF4PMm8DdeUt+qUrSFRLY4J
MroY51gM90nnhtijtleCMIIFxDCCBKygAwIBAgIQXT90N24i2xwadZVlhXZ+sTANBgkqhkiG9w0B
AQUFADCBnjELMAkGA1UEBhMCVVMxFjAUBgNVBAgTDU1hc3NhY2h1c2V0dHMxEDAOBgNVBAcTB0Jl
ZGZvcmQxGTAXBgNVBAoTEFJTQSBTZWN1cml0eSBMTEMxJTAjBgNVBAsTHEdsb2JhbCBTZWN1cml0
eSBPcmdhbml6YXRpb24xIzAhBgNVBAMTGlJTQSBDbGFzcyAyIFBlcnNvbmFsIENBIHYyMB4XDTEx
MDcxNDE1MjgwOVoXDTEzMDcxNDE1MjgwOVowge8xEzARBgoJkiaJk/IsZAEZFgNjb20xEzARBgoJ
kiaJk/IsZAEZFgNlbWMxGDAWBgNVBAoTD0VNQyBDb3Jwb3JhdGlvbjERMA8GA1UECxMIQW1lcmlj
YXMxHDAaBgNVBAsTE0luZm9ybWF0aW9uIFN5c3RlbXMxDzANBgNVBAUTBjEyMjc2NTEXMBUGCgmS
JomT8ixkAQETB2hhcnJpYzgxHzAdBgNVBAMTFkNocmlzdG9waGVyIEhhcnJpbmd0b24xLTArBgkq
hkiG9w0BCQEWHmNocmlzdG9waGVyLmhhcnJpbmd0b25AZW1jLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAM0b9ETHWlRPJX2CZ5RSGjNkOgRYHwcmeBtNlGTBqVIGlFQUywADy67n
3XoOGuxzpvS9I2I5mcM+dFXfO7YIG6bYJk2igTfckR3HZVhH1WLIu5tk8De9VA30+vtSgDqw/GrF
VOVV+DR5qrFqZ5Iumn3QnGiRjdcOU9NRpBBR2vZWVnIiB9jxn+o5hIXFfWwieLDyW96Hph25fZql
Ww7rVVLSIDcSKK54MQkYmKhM7sUtczDFMY/2aUBMAYNdp5Sp9U7ZpPXPIOmZzR2QTrWbON6u6cNi
3bvsPkyZz3AXhpDjJFKb+EkR92mwpoTsuez113B4GEY5bVgmcfVuw2L3wPECAwEAAaOCAakwggGl
MB8GA1UdIwQYMBaAFBQw62v19Em1aFJ1ptu9rlvIrH1MMIGRBgNVHSAEgYkwgYYwgYMGCSqGSIb3
DQUHBTB2MC4GCCsGAQUFBwIBFiJodHRwOi8vY2EucnNhc2VjdXJpdHkuY29tL0NQUy5odG1sMEQG
CCsGAQUFBwICMDgwFxYQUlNBIFNlY3VyaXR5IExMQzADAgEBGh1DUFMgSW5jb3Jwb3JhdGVkIGJ5
IHJlZmVyZW5jZTApBgNVHSUEIjAgBgorBgEEAYI3FAICBggrBgEFBQcDAgYIKwYBBQUHAwQwSgYD
VR0RBEMwQYEeY2hyaXN0b3BoZXIuaGFycmluZ3RvbkBlbWMuY29toB8GCisGAQQBgjcUAgOgEQwP
aGFycmljOEBlbWMuY29tMA4GA1UdDwEB/wQEAwIHgDBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8v
Y3JsLnJzYXNlY3VyaXR5LmNvbTo4MC9SU0FDbGFzczJQZXJzb25hbENBdjIuY3JsMB0GA1UdDgQW
BBRW1M3IzplvKoMlZigKQPkAVmvlTjANBgkqhkiG9w0BAQUFAAOCAQEAkX75qUhpAq/WngSOqN/f
ykF7EyOqwrlNPjV/Ev4QwLKA+9JlouET4byWIxr66IRSV7YOu+zNdFfToGQ/8WKWjVBnrXunxe8k
97BRDr5TBdNdIYYpv4bUOkTHZchB1s4d/e4N3kP18W1xuC0i6bNfHpkAikOGIVvJ5Fi8gnZEDDeL
IlK2T6udJFzg0DkBzg1AVt0DQ3cHxYIBowMAbWmqdgzsItbdd6kKjgEPdpf1YFXlV+e/N2oArHTN
6dTLP8K3jJMFHXrPxp4qA68O/wHKaR3qgfidIzB6XjomaQCchY6oCWRMrufqcZ/HDAq7z7vru+x4
tGE+yUqYqEkBgVnxaTCCBdQwggS8oAMCAQICEEBVs4BiURueYjjhnbUS+bkwDQYJKoZIhvcNAQEF
BQAwgZ4xCzAJBgNVBAYTAlVTMRYwFAYDVQQIEw1NYXNzYWNodXNldHRzMRAwDgYDVQQHEwdCZWRm
b3JkMRkwFwYDVQQKExBSU0EgU2VjdXJpdHkgTExDMSUwIwYDVQQLExxHbG9iYWwgU2VjdXJpdHkg
T3JnYW5pemF0aW9uMSMwIQYDVQQDExpSU0EgQ2xhc3MgMiBQZXJzb25hbCBDQSB2MjAeFw0xMTA3
MTQxNTI4MTRaFw0xMzA3MTQxNTI1MDZaMIHzMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZIm
iZPyLGQBGRYDZW1jMRgwFgYDVQQKEw9FTUMgQ29ycG9yYXRpb24xETAPBgNVBAsTCEFtZXJpY2Fz
MRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0ZW1zMQ8wDQYDVQQFEwYxMjI3NjUxFzAVBgoJkiaJ
k/IsZAEBEwdoYXJyaWM4MSMwIQYDVQQDExpDaHJpc3RvcGhlciBIYXJyaW5ndG9uLUVuYzEtMCsG
CSqGSIb3DQEJARYeY2hyaXN0b3BoZXIuaGFycmluZ3RvbkBlbWMuY29tMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAtfexCM/OPHjt2B8L4hCnKUtcvGW7hhku6OYtYx1z4mfTGXbjP9bP
nv5L+4A3lCxuOQhUKfLdXVfikrGhxlFx9f6VRq16wD6WUa5XJIkThry88uFZwG6G1w3LvP34ijNL
vV+O1ZuNU6e+Hq/CRQm+TyEIbu7K1rDWyKxdOg9K52BYfaOn6GfBNnNch9p2q9EhBlpoab152mt3
+ncNv7TFkuWws8MOs4VV1CU5rWB+VSBGPeVJo9mX8+RkKTjHSlRLibNPwt8+Pj0ZKvJuwFL5K0MX
fKST19kNbXjJBfWF7yH7WLmvfJWJT0oUEhkQWEOGW3ibhgy3e78r4wQZnk5A2QIDAQABo4IBtTCC
AbEwNQYDVR0lBC4wLAYKKwYBBAGCNxQCAgYIKwYBBQUHAwIGCCsGAQUFBwMEBgorBgEEAYI3CgME
MB8GA1UdIwQYMBaAFBQw62v19Em1aFJ1ptu9rlvIrH1MMIGRBgNVHSAEgYkwgYYwgYMGCSqGSIb3
DQUHBTB2MC4GCCsGAQUFBwIBFiJodHRwOi8vY2EucnNhc2VjdXJpdHkuY29tL0NQUy5odG1sMEQG
CCsGAQUFBwICMDgwFxYQUlNBIFNlY3VyaXR5IExMQzADAgEBGh1DUFMgSW5jb3Jwb3JhdGVkIGJ5
IHJlZmVyZW5jZTBKBgNVHREEQzBBgR5jaHJpc3RvcGhlci5oYXJyaW5ndG9uQGVtYy5jb22gHwYK
KwYBBAGCNxQCA6ARDA9oYXJyaWM4QGVtYy5jb20wSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2Ny
bC5yc2FzZWN1cml0eS5jb206ODAvUlNBQ2xhc3MyUGVyc29uYWxDQXYyLmNybDAdBgNVHQ4EFgQU
5LsToi39CUKQ1y41KI1Xba78JFcwDgYDVR0PAQH/BAQDAgM4MA0GCSqGSIb3DQEBBQUAA4IBAQCe
ryMDShgtoiUuMsRE+QGJOKY6qVOrZ9SDGnzxoIAZ9HE0Mw8mZdFccRKZOIDvR/9JMUgIMF//JRTD
Eml7e6XYd8tDAqd9tr1VI/ukJ/pUnMJ/uDMY6azQH43cOVjdiaebQNWmZmYTDzvV+gvlpDPd8Sod
HAc7ZOyfDe9ofyP/e8YPhkwn6TGrK9598bqSm7MNQIjN1y6Jzrk1TdbmyD76jgxUvLdTI8gz6aW1
wYoEeVB1r1BXhN9tVxbsh5FjUBy654jp5BT/f+6JcA7Q6UncdRtwNu6wrxoj5wgzWGpVmBBkomoI
fRcNDadTU4wCwdG/mXSPdJaCqfPifbfQUGnRMYIEejCCBHYCAQEwgbMwgZ4xCzAJBgNVBAYTAlVT
MRYwFAYDVQQIEw1NYXNzYWNodXNldHRzMRAwDgYDVQQHEwdCZWRmb3JkMRkwFwYDVQQKExBSU0Eg
U2VjdXJpdHkgTExDMSUwIwYDVQQLExxHbG9iYWwgU2VjdXJpdHkgT3JnYW5pemF0aW9uMSMwIQYD
VQQDExpSU0EgQ2xhc3MgMiBQZXJzb25hbCBDQSB2MgIQXT90N24i2xwadZVlhXZ+sTAJBgUrDgMC
GgUAoIICmzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAzMDcx
NTIxMzhaMCMGCSqGSIb3DQEJBDEWBBRmDc5EH1Pc99Um5+KvgRKsIEXfmjCBqwYJKoZIhvcNAQkP
MYGdMIGaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCgYIKoZIhvcNAwcwCwYJYIZIAWUDBAEC
MA4GCCqGSIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDAH
BgUrDgMCGjALBglghkgBZQMEAgMwCwYJYIZIAWUDBAICMAsGCWCGSAFlAwQCATCBxAYJKwYBBAGC
NxAEMYG2MIGzMIGeMQswCQYDVQQGEwJVUzEWMBQGA1UECBMNTWFzc2FjaHVzZXR0czEQMA4GA1UE
BxMHQmVkZm9yZDEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IExMQzElMCMGA1UECxMcR2xvYmFsIFNl
Y3VyaXR5IE9yZ2FuaXphdGlvbjEjMCEGA1UEAxMaUlNBIENsYXNzIDIgUGVyc29uYWwgQ0EgdjIC
EEBVs4BiURueYjjhnbUS+bkwgcYGCyqGSIb3DQEJEAILMYG2oIGzMIGeMQswCQYDVQQGEwJVUzEW
MBQGA1UECBMNTWFzc2FjaHVzZXR0czEQMA4GA1UEBxMHQmVkZm9yZDEZMBcGA1UEChMQUlNBIFNl
Y3VyaXR5IExMQzElMCMGA1UECxMcR2xvYmFsIFNlY3VyaXR5IE9yZ2FuaXphdGlvbjEjMCEGA1UE
AxMaUlNBIENsYXNzIDIgUGVyc29uYWwgQ0EgdjICEEBVs4BiURueYjjhnbUS+bkwDQYJKoZIhvcN
AQEBBQAEggEAeWRXkOMkuz8XY1yDyVEmDNLTOPBB9aSVh3WQB+F3dx51/PMSdcbQB6Q0y/ZIqkHg
OCyC/nO43JLh1LO6POf6NRF+KdrgIxaXz2tABLE570yHVppgp/IXBljBp7IlVGZMgn31xCpAIJwZ
ziDrDHswCj9qsvEAk2ZLOXyOHoSVFDqAC8jpE7/gTVwtdYKk59uFqBjRiy41hOvJjdIJIsz53JH3
X+0xK65B0VKShAvp9d+C6nJXmMZz6xF3QPaRhz56BF2a9LmdJpVSF574ROiusaWBTA5tQBKeiJLh
XMWTKZnXOEHdHNrBBkBF1jVUVytTbqTCAjci6BEWUNzupaXDqgAAAAAAAA==

------=_NextPart_000_0067_01CE1B1D.8DAFE700--

From trammell@tik.ee.ethz.ch  Mon Mar 11 06:33:33 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACD8321F8AD6 for <mile@ietfa.amsl.com>; Mon, 11 Mar 2013 06:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krUYy2fWHUVE for <mile@ietfa.amsl.com>; Mon, 11 Mar 2013 06:33:31 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 679A521F8ACA for <mile@ietf.org>; Mon, 11 Mar 2013 06:33:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 9AD7CD9305 for <mile@ietf.org>; Mon, 11 Mar 2013 14:33:30 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8Jl+71L5nJYI for <mile@ietf.org>; Mon, 11 Mar 2013 14:33:30 +0100 (MET)
Received: from dhcp-5213.meeting.ietf.org (dhcp-5213.meeting.ietf.org [130.129.82.19]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 3176DD9304 for <mile@ietf.org>; Mon, 11 Mar 2013 14:33:30 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE0965D8-8929-4ECB-B9D7-17F1899DF085@tik.ee.ethz.ch>
Date: Mon, 11 Mar 2013 09:33:27 -0400
To: MILE IETF <mile@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [mile] IETF 86 agenda update
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 11 Mar 2013 13:33:33 -0000

Greetings, all,

I've made minor changes to the agenda at =
http://www.ietf.org/proceedings/86/minutes/minutes-86-mile -- we'll use =
the remaining time on the agenda to discuss changes to the WG charter =
following from the discussion during the meeting.

Presenters, please verify the duration of your slot, and direct any =
comments to mile-chairs@tools.ietf.org. Please also send slides to =
mile-chairs@tools.ietf.org, if you haven't already, by the end of day =
tomorrow, so we can get them up on the meeting materials page in a =
timely manner.

Many thanks, best regards,

Brian=

From bakerj@mitre.org  Tue Mar 12 06:59:17 2013
Return-Path: <bakerj@mitre.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3BB21F869C; Tue, 12 Mar 2013 06:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZCRZDE8WGwAs; Tue, 12 Mar 2013 06:59:16 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 18A7E21F85B8; Tue, 12 Mar 2013 06:59:16 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id A03111F02F8; Tue, 12 Mar 2013 09:59:15 -0400 (EDT)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 9027B1F02C0; Tue, 12 Mar 2013 09:59:15 -0400 (EDT)
Received: from IMCMBX03.MITRE.ORG ([169.254.3.117]) by IMCCAS02.MITRE.ORG ([129.83.29.69]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 09:59:15 -0400
From: "Baker, Jon" <bakerj@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: CCE Transition Announcement
Thread-Index: Ac4RADKco2InqncXQ+6jVz9MTMb/JgNi+C1Q
Date: Tue, 12 Mar 2013 13:59:14 +0000
Message-ID: <6C1C15D8B5510B4B8FF132B10D38651304BB153A@IMCMBX03.MITRE.ORG>
References: <AE2A97B34BC3DE44A5A71749D65BC262015D6E67@IMCMBX03.MITRE.ORG>
In-Reply-To: <AE2A97B34BC3DE44A5A71749D65BC262015D6E67@IMCMBX03.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.83.31.55]
Content-Type: multipart/alternative; boundary="_000_6C1C15D8B5510B4B8FF132B10D38651304BB153AIMCMBX03MITREOR_"
MIME-Version: 1.0
Subject: [mile] FW: CCE Transition Announcement
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Mar 2013 13:59:17 -0000

--_000_6C1C15D8B5510B4B8FF132B10D38651304BB153AIMCMBX03MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As an update for the SCAM and MILE lists, MITRE has transferred CCE to NIST=
. This transfer was announced to the CCE community a couple of weeks ago an=
d I have included that announcement message below. This morning I submitted=
 an update to the CCE IPR disclosure making it clear that this transfer has=
 occurred.

Jon

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jonathan O. Baker
G022 - IA Industry Collaboration
The MITRE Corporation
Email: bakerj@mitre.org<mailto:bakerj@mitre.org>

From: owner-cce-working-group-list@lists.mitre.org [mailto:owner-cce-workin=
g-group-list@lists.mitre.org] On Behalf Of Sain, Joe
Sent: Friday, February 22, 2013 8:26 AM
To: cce-working-group-list
Subject: CCE Transition Announcement

Members of the CCE Community -

We are pleased to announce that we are working with the National Institute =
of Standards and Technology (NIST) and the National Security Agency (NSA) t=
o transition operational responsibility and all intellectual property assoc=
iated with the Common Configuration Enumeration (CCE) from MITRE to NIST. O=
ver the next few weeks, MITRE and NIST will be working closely together to =
ensure a smooth transition that maintains the continuity of the effort.

What it Means
NIST will host the CCE corpus and all associated documentation, and they wi=
ll handle the receipt, processing, and publication of CCE submissions.  NIS=
T will also be responsible for all official CCE correspondence with vendors=
, the government, and the community. MITRE will continue to participate in =
an advisory role, and will remain active in the CCE Working Group.

We believe that this change will enable CCE to continue evolving to meet th=
e configuration management needs of all community members.

Regards,

Joe Sain
MITRE CCE Task Lead


--_000_6C1C15D8B5510B4B8FF132B10D38651304BB153AIMCMBX03MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As an update for the S=
CAM and MILE lists, MITRE has transferred CCE to NIST. This transfer was an=
nounced to the CCE community a couple of weeks ago and I have included that=
 announcement message below. This morning
 I submitted an update to the CCE IPR disclosure making it clear that this =
transfer has occurred.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jon<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jonathan O. Baker<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">G022 - IA Industry Col=
laboration<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The MITRE Corporation<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Email: <a href=3D"mail=
to:bakerj@mitre.org">
bakerj@mitre.org</a><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> owner-cc=
e-working-group-list@lists.mitre.org [mailto:owner-cce-working-group-list@l=
ists.mitre.org]
<b>On Behalf Of </b>Sain, Joe<br>
<b>Sent:</b> Friday, February 22, 2013 8:26 AM<br>
<b>To:</b> cce-working-group-list<br>
<b>Subject:</b> CCE Transition Announcement<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Members of the CCE Community &#8211; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We are pleased to announce that we are working with =
the National Institute of Standards and Technology (NIST) and the National =
Security Agency (NSA) to transition operational responsibility and all inte=
llectual property associated with
 the Common Configuration Enumeration (CCE) from MITRE to NIST. Over the ne=
xt few weeks, MITRE and NIST will be working closely together to ensure a s=
mooth transition that maintains the continuity of the effort.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><i>What it Means<o:p></o:p></i></p>
<p class=3D"MsoNormal">NIST will host the CCE corpus and all associated doc=
umentation, and they will handle the receipt, processing, and publication o=
f CCE submissions. &nbsp;NIST will also be responsible for all official CCE=
 correspondence with vendors, the government,
 and the community. MITRE will continue to participate in an advisory role,=
 and will remain active in the CCE Working Group.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We believe that this change will enable CCE to conti=
nue evolving to meet the configuration management needs of all community me=
mbers.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Joe Sain<o:p></o:p></p>
<p class=3D"MsoNormal">MITRE CCE Task Lead<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_6C1C15D8B5510B4B8FF132B10D38651304BB153AIMCMBX03MITREOR_--

From bakerj@mitre.org  Tue Mar 12 07:00:21 2013
Return-Path: <bakerj@mitre.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B59921F858C; Tue, 12 Mar 2013 07:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVC+s9ZiTDGg; Tue, 12 Mar 2013 07:00:16 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id B461721F8A9E; Tue, 12 Mar 2013 07:00:04 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 58D151F0572; Tue, 12 Mar 2013 10:00:04 -0400 (EDT)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 2A7581F02C0; Tue, 12 Mar 2013 10:00:04 -0400 (EDT)
Received: from IMCMBX03.MITRE.ORG ([169.254.3.117]) by IMCCAS04.MITRE.ORG ([129.83.29.81]) with mapi id 14.02.0318.004; Tue, 12 Mar 2013 10:00:04 -0400
From: "Baker, Jon" <bakerj@mitre.org>
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Transition of CPE from MITRE to NIST
Thread-Index: Ac4cLFfS+6ejMIhPRCiyHEw2BcE7KQCX8bPg
Date: Tue, 12 Mar 2013 14:00:02 +0000
Message-ID: <6C1C15D8B5510B4B8FF132B10D38651304BB1552@IMCMBX03.MITRE.ORG>
References: <808A833A2D415D41996B1CF760901A0A1D932EA6@IMCMBX04.MITRE.ORG>
In-Reply-To: <808A833A2D415D41996B1CF760901A0A1D932EA6@IMCMBX04.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.83.31.55]
Content-Type: multipart/alternative; boundary="_000_6C1C15D8B5510B4B8FF132B10D38651304BB1552IMCMBX03MITREOR_"
MIME-Version: 1.0
Subject: [mile] FW: Transition of CPE from MITRE to NIST
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Mar 2013 14:00:22 -0000

--_000_6C1C15D8B5510B4B8FF132B10D38651304BB1552IMCMBX03MITREOR_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As an update for the SCAM and MILE lists, MITRE has transferred CPE to NIST=
. This transfer was announced to the CPE community last week and I have inc=
luded that announcement message below. This morning I submitted an update t=
o the CPE IPR disclosure making it clear that this transfer has occurred.

Jon

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Jonathan O. Baker
G022 - IA Industry Collaboration
The MITRE Corporation
Email: bakerj@mitre.org<mailto:bakerj@mitre.org>

From: Cheikes, Brant A. [mailto:bcheikes@MITRE.ORG]
Sent: Friday, March 08, 2013 1:40 PM
To: cpe-discussion-list CPE Community Forum
Subject: [CPE-DISCUSSION-LIST] Transition of CPE from MITRE to NIST

Members of the CPE Community,

We are pleased to announce that we are working with the National Institute =
of Standards and Technology (NIST) and the National Security Agency (NSA) t=
o transition all intellectual property associated with the Common Platform =
Enumeration (CPE) from MITRE to NIST. Over the next few weeks, MITRE and NI=
ST will be working closely to ensure a smooth transition that maintains the=
 continuity of the effort.

What it Means
For the last several years, NIST has held operational responsibility for CP=
E. They host the Official CPE Dictionary, and handle the receipt, processin=
g, and publication of CPE submissions. With the August 2011 publication of =
CPE v2.3 as a suite of NIST Interagency Reports (NIST IRs 7695 through 7698=
), the specification of the CPE standard itself transitioned from MITRE to =
NIST. Throughout that time, MITRE held the CPE trademark, maintained a lega=
cy e-mail address for CPE submissions (cpe@mitre.org<mailto:cpe@mitre.org>)=
, maintained the official CPE website (cpe.mitre.org), and operated and mod=
erated the CPE Discussion List (cpe-discussion-list@lists.mitre.org<mailto:=
cpe-discussion-list@lists.mitre.org>). Going forward, all of CPE's operatin=
g functions as well as ownership of the trademark will transition to NIST, =
and NIST will be fully responsible for all official CPE correspondence with=
 vendors, the government, and the community. MITRE will continue to partici=
pate in an advisory role.

We believe that this change will enable CPE to continue to evolve to meet t=
he needs of all stakeholders and community members.

/Brant

Brant A. Cheikes
MITRE CPE Task Lead
The MITRE Corporation
202 Burlington Road, M/S K302
Bedford, MA 01730-1420
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352


--_000_6C1C15D8B5510B4B8FF132B10D38651304BB1552IMCMBX03MITREOR_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As an update for the S=
CAM and MILE lists, MITRE has transferred CPE to NIST. This transfer was an=
nounced to the CPE community last week and I have included that announcemen=
t message below. This morning I submitted
 an update to the CPE IPR disclosure making it clear that this transfer has=
 occurred.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jon<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jonathan O. Baker<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">G022 - IA Industry Col=
laboration<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The MITRE Corporation<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Email: <a href=3D"mail=
to:bakerj@mitre.org">
bakerj@mitre.org</a><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Cheikes,=
 Brant A. [mailto:bcheikes@MITRE.ORG]
<br>
<b>Sent:</b> Friday, March 08, 2013 1:40 PM<br>
<b>To:</b> cpe-discussion-list CPE Community Forum<br>
<b>Subject:</b> [CPE-DISCUSSION-LIST] Transition of CPE from MITRE to NIST<=
o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Members of the CPE =
Community,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">We are pleased to a=
nnounce that we are working with the National Institute of Standards and Te=
chnology (NIST) and the National Security Agency (NSA) to transition all in=
tellectual property associated with
 the Common Platform Enumeration (CPE) from MITRE to NIST. Over the next fe=
w weeks, MITRE and NIST will be working closely to ensure a smooth transiti=
on that maintains the continuity of the effort.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><i><span style=3D"font-size:12.0pt">What it Means<o:=
p></o:p></span></i></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">For the last severa=
l years, NIST has held operational responsibility for CPE. They host the Of=
ficial CPE Dictionary, and handle the receipt, processing, and publication =
of CPE submissions. With the August
 2011 publication of CPE v2.3 as a suite of NIST Interagency Reports (NIST =
IRs 7695 through 7698), the specification of the CPE standard itself transi=
tioned from MITRE to NIST. Throughout that time, MITRE held the CPE tradema=
rk, maintained a legacy e-mail address
 for CPE submissions (<a href=3D"mailto:cpe@mitre.org">cpe@mitre.org</a>), =
maintained the official CPE website (cpe.mitre.org), and operated and moder=
ated the CPE Discussion List (<a href=3D"mailto:cpe-discussion-list@lists.m=
itre.org">cpe-discussion-list@lists.mitre.org</a>).
 Going forward, all of CPE&#8217;s operating functions as well as ownership=
 of the trademark will transition to NIST, and NIST will be fully responsib=
le for all official CPE correspondence with vendors, the government, and th=
e community. MITRE will continue to participate
 in an advisory role.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">We believe that thi=
s change will enable CPE to continue to evolve to meet the needs of all sta=
keholders and community members.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">/Brant<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Brant A. Cheikes<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">MITRE CPE Task Lead=
<br>
The MITRE Corporation<br>
202 Burlington Road, M/S K302<br>
Bedford, MA 01730-1420<br>
Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352 <o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
</div>
</body>
</html>

--_000_6C1C15D8B5510B4B8FF132B10D38651304BB1552IMCMBX03MITREOR_--

From ietf@meetecho.com  Tue Mar 12 13:23:41 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C0DF11E8199 for <mile@ietfa.amsl.com>; Tue, 12 Mar 2013 13:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.664
X-Spam-Level: 
X-Spam-Status: No, score=-0.664 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2CL8nCx0p92 for <mile@ietfa.amsl.com>; Tue, 12 Mar 2013 13:23:40 -0700 (PDT)
Received: from smtpdg11.aruba.it (smtpdg6.aruba.it [62.149.158.236]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3DF11E8189 for <mile@ietf.org>; Tue, 12 Mar 2013 13:23:38 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.16.136]) by smtpcmd04.ad.aruba.it with bizsmtp id AkPa1l00S2w8SR601kPc1Z; Tue, 12 Mar 2013 21:23:37 +0100
Date: Tue, 12 Mar 2013 16:23:32 -0400 (EDT)
From: Meetecho Team <ietf@meetecho.com>
To: mile@ietf.org
Message-ID: <16822261.15.1363119812782.JavaMail.tcastaldi@dell-tcastaldi>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_14_32643052.1363119812780"
Subject: [mile] Meetecho support for MILE session
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Mar 2013 20:23:41 -0000

------=_Part_14_32643052.1363119812780
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

a virtual room has been reserved on the Meetecho system for the 
MILE WG meeting session.
Access to the on-line session (including audio and video streams) will
be made available (just a couple of minutes before session start time) at:
http://www.meetecho.com/ietf86/mile

The Meetecho session automatically logs you into the standard IETF
jabber room. So, from there, you can have an integrated experience
involving all media and allowing you to interact with the room.

A tutorial of interactivity features of the tool can be found at:
	http://www.meetecho.com/ietf86

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_14_32643052.1363119812780--

From kathleen.moriarty@emc.com  Wed Mar 13 06:40:05 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8556421F86E6 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 06:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7PiPwoUzIMj for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 06:40:05 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C11E221F8C1A for <mile@ietf.org>; Wed, 13 Mar 2013 06:40:02 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DDdxZ9015720 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 13 Mar 2013 09:39:59 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 13 Mar 2013 09:39:45 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DDdgNh013349 for <mile@ietf.org>; Wed, 13 Mar 2013 09:39:44 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub33.corp.emc.com ([::1]) with mapi; Wed, 13 Mar 2013 09:39:42 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Wed, 13 Mar 2013 09:39:42 -0400
Thread-Topic: Jabber and Note takers
Thread-Index: AQHOH/A3hAluTRUyhk+jYAasd0V/yQ==
Message-ID: <F5063677821E3B4F81ACFB7905573F24D79BE5B4@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] Jabber and Note takers
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 13:40:05 -0000

Hello,

Could we have two volunteers to assist with taking notes during the MILE se=
ssion at 1PM today?=20

This is an important function covered by volunteers in every WG session and=
 the work is very much appreciated.

Thank you!
Kathleen=

From inacio@cert.org  Wed Mar 13 07:41:13 2013
Return-Path: <inacio@cert.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5FED21F8B46 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 07:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0di1Z3GG9y1g for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 07:41:12 -0700 (PDT)
Received: from shetland.sei.cmu.edu (shetland.sei.cmu.edu [192.58.107.44]) by ietfa.amsl.com (Postfix) with ESMTP id B3C2E21F8B20 for <mile@ietf.org>; Wed, 13 Mar 2013 07:41:12 -0700 (PDT)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by shetland.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id r2DEfCVZ014783 for <mile@ietf.org>; Wed, 13 Mar 2013 10:41:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1363185672; bh=4rtAuErOUMpyXJaapb5HWKaaf7Ehn3xV3spk0P3eWSY=; h=From:To:Subject:Date:Message-ID:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=HIvEN0VBm2eC7j1lc2HB22UxOpKSoC9HYO03QaGskm3IeXvbApKj4ujjt4qoo79xL I+QH0Esfh9rzarllo9KVUHAXM8FSZM73Xsu+nXo/vL73KQEZXW3Q42oGjRkyom0G/I QdugRpmTuDqojZlJexKlfVrblK0lovOZcNWIlUhc=
Received: from owa.sei.cmu.edu (cascade.sei.cmu.edu [10.64.28.248]) by timber.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id r2DEfCXo003667 for <mile@ietf.org>; Wed, 13 Mar 2013 10:41:12 -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.02.0318.004; Wed, 13 Mar 2013 10:41:11 -0400
From: Chris Inacio <inacio@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: GRC draft comments
Thread-Index: AQHOH/jOePNNyceo2Eqkn/mtBvnYKw==
Date: Wed, 13 Mar 2013 14:41:11 +0000
Message-ID: <4AE532C8B0B4B548AF47570D250D81742B37D2@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.97.251]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A16932D87FDB754F905BB59E03D42362@sei.cmu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mile] GRC draft comments
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 14:41:13 -0000

Here are some comments on the GRC draft.  I started skimming more around se=
ction 7 or so to the ends, so there isn't anything too detailed there.  But=
 I'm not sure I would have detailed comments there anyway, at this point.


Why would / should the transport look into the GRC report XML to determine
its type to change the transport behavior.  This seems really, wrong.  Mayb=
e
an application establishing transport would do that, but I don't think that
should be described as "transport". (Bottom of page 10, GRCPolicy class.)
(You can read this as: clarify what you mean by transport, because the
current use of transport isn't particularly clear.  Something like RID
or a similar alternative, which then has another transport (e.g. TCP,=20
HTTP/TLS, etc.) needs to be clear.)


ReportID shouldn't have a default of the date.  That is a form of
information leakage.  I think that could be a MAY, with an acknowledgement
of the information leakage.  RANDOM would be a better default.  (An entity
could use some type of cryptographic algorithm that included date, but it
does leave the cryptographic channel somewhat exposed to attack via possibl=
e
known plain text.)

Should things like policy regions be registries?  Pro: it doesn't allow
strings to be created that have no common understanding of the meaning.
Con: can't validate the XML with information in a registry.  Should likely
apply to all MILE work.  This especially applies to MsgType of GRCPolicy
class.

What is the correct behavior of RID/"transport" for a GRCPolicy class with =
MsgType
ext-MsgType?

The GRCPolicy needs to be signed, or at least have the option.  Assume a
MITM attack that changes/adds the restriction setting, and makes the
document disclosable.  This MIGHT be otherwise protected by the transport,
but there is no promise of that.

Justifcation:  Do we need "other" and an extension mechanism too?  Neither
necessarily gives an implementor a lot of information about how to
act/behave.  I think 1 of these is enough.

ReportType: other & extension both included again.

GRCDocument: Version should be REQUIRED.


--
Chris Inacio
inacio@cert.org




From eburger-l@standardstrack.com  Wed Mar 13 08:27:52 2013
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF1021F8EAC for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 08:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NeRbo8UbMfYd for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 08:27:52 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) by ietfa.amsl.com (Postfix) with ESMTP id 7657621F89AA for <mile@ietf.org>; Wed, 13 Mar 2013 08:27:51 -0700 (PDT)
Received: from dhcp-42e0.meeting.ietf.org ([130.129.66.224]:57498) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1UFnah-00017C-Eo for mile@ietf.org; Wed, 13 Mar 2013 08:27:43 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <75782EF7-F21F-44DD-929C-AF4A37BDD860@standardstrack.com>
Date: Wed, 13 Mar 2013 11:27:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <384B5B5D-09AE-4A6A-AFCA-93DA799E014E@standardstrack.com>
References: <75782EF7-F21F-44DD-929C-AF4A37BDD860@standardstrack.com>
To: MILE IETF <mile@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [mile] What is Version (5070bis, enum, etc.)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 15:27:52 -0000

5070, 5070bis, and ENUM all use a 'version' attribute.=20

Section 3.1 of both 5070 and 5070bis define version as:
     Required.  STRING.  The IODEF specification version number to
     which this IODEF document conforms.  The value of this attribute
     MUST be "1.00"

OK, I will bite. The schema of 5070 and 5070bis are different. How do I =
know I have a 5070bis schema if it says <IODEF-Document version=3D"1.00">?=
 It is totally non-normative, but I suppose someone who is clueless =
about protocols would look at the double super secret <documentation> =
tag that says "Incident Object Description Exchange Format v1.00, see =
RFC 5070" for a 5070 document and "Incident Object Description Exchange =
Format v1.10, RFC5070-bis" for a 5070bis document. I say "double super =
secret" because that string only appears in the schema but has no text =
describing it. Also, making a programatic decision based on XML Schema =
documentation is not a very smart idea.

Let me push this further. What happens if a 5070bis document has =
<IODEF-Document version=3D"1.10">? 5070 and 5070bis both say=85 nothing. =
However, a good protocol writer will see the 'MUST be "1.00"' and thus =
will reject the document. Is this the desired behavior? If so, say so. I =
doubt it, but we are begging for interoperability failure if IODEF =
becomes successful and we enhance it in the future.

Enum reference format suffers from this as well, but I will address that =
in a separate email.



From eburger-l@standardstrack.com  Wed Mar 13 08:28:03 2013
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15A621F8EC2 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 08:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7t1VjqHW9ZoT for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 08:28:03 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) by ietfa.amsl.com (Postfix) with ESMTP id 0333C21F8EAC for <mile@ietf.org>; Wed, 13 Mar 2013 08:28:03 -0700 (PDT)
Received: from dhcp-42e0.meeting.ietf.org ([130.129.66.224]:57498) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1UFnaz-00017C-RD for mile@ietf.org; Wed, 13 Mar 2013 08:28:01 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <3DA83EFB-409F-4A7D-B69D-FEC71F4FABFD@standardstrack.com>
Date: Wed, 13 Mar 2013 11:28:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0C3F737-C43F-4CEB-A8BD-EEFEF9391D1A@standardstrack.com>
References: <3DA83EFB-409F-4A7D-B69D-FEC71F4FABFD@standardstrack.com>
To: MILE IETF <mile@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [mile] Comments on IODEF ENUM Draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 15:28:03 -0000

This document suffers from "do what I mean, not what I say" syndrome.

Here we are, suffering all of the indignities of XML -- lots of angle =
brackets, slashes, colons, white space, preambles, external definitions =
that no one looks up, etc. Why do we do this? Because we get explicit =
data element definitions and unambiguous understanding. So, given we are =
paying the XML fee, why would we then drop it all and come up with a =
structured string inside of a <ReferenceName> tag?

Let us say what we mean and break out the abbreviation, version, and id.

It gets worse, and I am back on the version bandwagon. What does it mean =
if you cannot find the right version? Dot separated strings are a "good =
idea"? What does that mean? Do you go to the closest major number? How =
do you report an inability to find the right document? What if the =
document is there, but you just do not want to support it? Since this =
draft is for a generic mechanism, it is somewhat OK to not describe =
specific actions, but it must enumerate that any definition and, if we =
go there, IANA registration, must specify the appropriate action to take =
in the common cases, and that people registering values must describe =
the registration-specific actions.

Lastly, the IANA section specifies a designated expert, but also says =
consult MILE. Pick one. Either it is a designated expert, and the AD =
will ensure their selectee works with MILE (or its successors) or you =
want work group review, and the WG chair will ensure they select an =
expert to do the review.


From Paul.Stoecker@rsa.com  Wed Mar 13 09:19:44 2013
Return-Path: <Paul.Stoecker@rsa.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE4521F85FC for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjLjMHXUY+or for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3452121F85EB for <mile@ietf.org>; Wed, 13 Mar 2013 09:19:43 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DGJeMZ016319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Mar 2013 12:19:41 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 13 Mar 2013 12:19:28 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DGJRex012088; Wed, 13 Mar 2013 12:19:27 -0400
Received: from MXHUB104.corp.emc.com (10.253.58.16) by mxhub13.corp.emc.com (128.222.70.234) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 13 Mar 2013 12:19:27 -0400
Received: from MX103CL01.corp.emc.com ([169.254.5.163]) by MXHUB104.corp.emc.com ([::1]) with mapi id 14.02.0342.003; Wed, 13 Mar 2013 12:19:26 -0400
From: "Stoecker, Paul" <Paul.Stoecker@rsa.com>
To: Eric Burger <eburger-l@standardstrack.com>
Thread-Topic: [mile] What is Version (5070bis, enum, etc.)
Thread-Index: AQHOH/9oWuM9Me0MX0qmOPzlbcI5BZijzREa
Date: Wed, 13 Mar 2013 16:19:27 +0000
Message-ID: <73930A69-4224-4B73-82D5-A23F411F2179@rsa.com>
References: <75782EF7-F21F-44DD-929C-AF4A37BDD860@standardstrack.com>, <384B5B5D-09AE-4A6A-AFCA-93DA799E014E@standardstrack.com>
In-Reply-To: <384B5B5D-09AE-4A6A-AFCA-93DA799E014E@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: MILE IETF <mile@ietf.org>
Subject: Re: [mile] What is Version (5070bis, enum, etc.)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 16:19:44 -0000

Eric,

Thanks.  This is something that I will correct after the IETF meeting as I =
am sure that I missed other items and there are some other changes that we =
will be discussing that will need to be incorporated.  This is my rookie ye=
ar as an editor, so I really appreciate the feedback.

Regards,

Paul

Sent from my iPhone

On Mar 13, 2013, at 11:28 AM, "Eric Burger" <eburger-l@standardstrack.com> =
wrote:

> 5070, 5070bis, and ENUM all use a 'version' attribute.=20
>=20
> Section 3.1 of both 5070 and 5070bis define version as:
>     Required.  STRING.  The IODEF specification version number to
>     which this IODEF document conforms.  The value of this attribute
>     MUST be "1.00"
>=20
> OK, I will bite. The schema of 5070 and 5070bis are different. How do I k=
now I have a 5070bis schema if it says <IODEF-Document version=3D"1.00">? I=
t is totally non-normative, but I suppose someone who is clueless about pro=
tocols would look at the double super secret <documentation> tag that says =
"Incident Object Description Exchange Format v1.00, see RFC 5070" for a 507=
0 document and "Incident Object Description Exchange Format v1.10, RFC5070-=
bis" for a 5070bis document. I say "double super secret" because that strin=
g only appears in the schema but has no text describing it. Also, making a =
programatic decision based on XML Schema documentation is not a very smart =
idea.
>=20
> Let me push this further. What happens if a 5070bis document has <IODEF-D=
ocument version=3D"1.10">? 5070 and 5070bis both say=85 nothing. However, a=
 good protocol writer will see the 'MUST be "1.00"' and thus will reject th=
e document. Is this the desired behavior? If so, say so. I doubt it, but we=
 are begging for interoperability failure if IODEF becomes successful and w=
e enhance it in the future.
>=20
> Enum reference format suffers from this as well, but I will address that =
in a separate email.
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20

From turners@ieca.com  Wed Mar 13 09:58:31 2013
Return-Path: <turners@ieca.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E57F21F87D0 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.241
X-Spam-Level: 
X-Spam-Status: No, score=-102.241 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1PaoU8GT+7N for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 09:58:30 -0700 (PDT)
Received: from gateway12.websitewelcome.com (gateway12.websitewelcome.com [67.18.72.134]) by ietfa.amsl.com (Postfix) with ESMTP id 2F65421F8623 for <mile@ietf.org>; Wed, 13 Mar 2013 09:58:30 -0700 (PDT)
Received: by gateway12.websitewelcome.com (Postfix, from userid 5007) id E328F710FEC0E; Wed, 13 Mar 2013 11:58:29 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway12.websitewelcome.com (Postfix) with ESMTP id D0AB6710FEBAB for <mile@ietf.org>; Wed, 13 Mar 2013 11:58:29 -0500 (CDT)
Received: from [198.180.150.142] (port=54046 helo=dhcp-119e.meeting.ietf.org) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UFp0X-0002PB-Jy; Wed, 13 Mar 2013 11:58:29 -0500
Message-ID: <5140B034.4000304@ieca.com>
Date: Wed, 13 Mar 2013 12:58:28 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Baker, Jon" <bakerj@mitre.org>,  David Waltermire <david.waltermire@nist.gov>
References: <AE2A97B34BC3DE44A5A71749D65BC262015D6E67@IMCMBX03.MITRE.ORG> <6C1C15D8B5510B4B8FF132B10D38651304BB153A@IMCMBX03.MITRE.ORG>
In-Reply-To: <6C1C15D8B5510B4B8FF132B10D38651304BB153A@IMCMBX03.MITRE.ORG>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.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: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (dhcp-119e.meeting.ietf.org) [198.180.150.142]:54046
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: "mile@ietf.org" <mile@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [mile] FW: CCE Transition Announcement
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 16:58:31 -0000

Jon,

Thanks to you and your colleagues for your efforts in making this 
happen.  I will certainly make it easier for the mile WG and sacm BOF to 
consider adopting these.

David,

You made an offer on the mile list back in August:
https://www.ietf.org/mail-archive/web/mile/current/msg00794.html
I'm hoping you're still willing to do the disclosure submission.

It would be great if you'd update the MITRE disclosures so that it's 
clear to community that they've been transferred.

spt

On 3/12/13 9:59 AM, Baker, Jon wrote:
> As an update for the SCAM and MILE lists, MITRE has transferred CCE to
> NIST. This transfer was announced to the CCE community a couple of weeks
> ago and I have included that announcement message below. This morning I
> submitted an update to the CCE IPR disclosure making it clear that this
> transfer has occurred.
>
> Jon
>
> ============================================
>
> Jonathan O. Baker
>
> G022 - IA Industry Collaboration
>
> The MITRE Corporation
>
> Email: bakerj@mitre.org <mailto:bakerj@mitre.org>
>
> *From:*owner-cce-working-group-list@lists.mitre.org
> [mailto:owner-cce-working-group-list@lists.mitre.org] *On Behalf Of
> *Sain, Joe
> *Sent:* Friday, February 22, 2013 8:26 AM
> *To:* cce-working-group-list
> *Subject:* CCE Transition Announcement
>
> Members of the CCE Community –
>
> We are pleased to announce that we are working with the National
> Institute of Standards and Technology (NIST) and the National Security
> Agency (NSA) to transition operational responsibility and all
> intellectual property associated with the Common Configuration
> Enumeration (CCE) from MITRE to NIST. Over the next few weeks, MITRE and
> NIST will be working closely together to ensure a smooth transition that
> maintains the continuity of the effort.
>
> /What it Means/
>
> NIST will host the CCE corpus and all associated documentation, and they
> will handle the receipt, processing, and publication of CCE submissions.
>   NIST will also be responsible for all official CCE correspondence with
> vendors, the government, and the community. MITRE will continue to
> participate in an advisory role, and will remain active in the CCE
> Working Group.
>
> We believe that this change will enable CCE to continue evolving to meet
> the configuration management needs of all community members.
>
> Regards,
>
> Joe Sain
>
> MITRE CCE Task Lead
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

From turners@ieca.com  Wed Mar 13 10:04:42 2013
Return-Path: <turners@ieca.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6732321F86EC for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 10:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.252
X-Spam-Level: 
X-Spam-Status: No, score=-102.252 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P+oqPpeux4NK for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 10:04:41 -0700 (PDT)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [67.18.14.8]) by ietfa.amsl.com (Postfix) with ESMTP id C092321F87E7 for <mile@ietf.org>; Wed, 13 Mar 2013 10:04:41 -0700 (PDT)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 55DBB9ECC7341; Wed, 13 Mar 2013 12:04:34 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway04.websitewelcome.com (Postfix) with ESMTP id 4A0E89ECC731B for <mile@ietf.org>; Wed, 13 Mar 2013 12:04:34 -0500 (CDT)
Received: from [198.180.150.142] (port=54072 helo=dhcp-119e.meeting.ietf.org) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UFp6X-0005F9-0Y; Wed, 13 Mar 2013 12:04:41 -0500
Message-ID: <5140B1A7.6030704@ieca.com>
Date: Wed, 13 Mar 2013 13:04:39 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Baker, Jon" <bakerj@mitre.org>,  David Waltermire <david.waltermire@nist.gov>
References: <808A833A2D415D41996B1CF760901A0A1D932EA6@IMCMBX04.MITRE.ORG> <6C1C15D8B5510B4B8FF132B10D38651304BB1552@IMCMBX03.MITRE.ORG>
In-Reply-To: <6C1C15D8B5510B4B8FF132B10D38651304BB1552@IMCMBX03.MITRE.ORG>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.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: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (dhcp-119e.meeting.ietf.org) [198.180.150.142]:54072
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: "mile@ietf.org" <mile@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Subject: Re: [mile] FW: Transition of CPE from MITRE to NIST
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 17:04:42 -0000

Jon,

Honestly not trying to sound like a broken record, but I'd like to again 
thank you and your colleagues for your efforts in making this happen. 
It'll certainly make it easier for the mile WG and sacm BOF to consider 
adopting these.

David,

Same here: You made an offer on the mile list back in August:
https://www.ietf.org/mail-archive/web/mile/current/msg00794.html
I'm hoping you're still willing to do the disclosure submission.

It would be great if you'd update the MITRE disclosures so that it's 
clear to community that they've been transferred.

spt

On 3/12/13 10:00 AM, Baker, Jon wrote:
> As an update for the SCAM and MILE lists, MITRE has transferred CPE to
> NIST. This transfer was announced to the CPE community last week and I
> have included that announcement message below. This morning I submitted
> an update to the CPE IPR disclosure making it clear that this transfer
> has occurred.
>
> Jon
>
> ============================================
>
> Jonathan O. Baker
>
> G022 - IA Industry Collaboration
>
> The MITRE Corporation
>
> Email: bakerj@mitre.org <mailto:bakerj@mitre.org>
>
> *From:*Cheikes, Brant A. [mailto:bcheikes@MITRE.ORG]
> *Sent:* Friday, March 08, 2013 1:40 PM
> *To:* cpe-discussion-list CPE Community Forum
> *Subject:* [CPE-DISCUSSION-LIST] Transition of CPE from MITRE to NIST
>
> Members of the CPE Community,
>
> We are pleased to announce that we are working with the National
> Institute of Standards and Technology (NIST) and the National Security
> Agency (NSA) to transition all intellectual property associated with the
> Common Platform Enumeration (CPE) from MITRE to NIST. Over the next few
> weeks, MITRE and NIST will be working closely to ensure a smooth
> transition that maintains the continuity of the effort.
>
> /What it Means/
>
> For the last several years, NIST has held operational responsibility for
> CPE. They host the Official CPE Dictionary, and handle the receipt,
> processing, and publication of CPE submissions. With the August 2011
> publication of CPE v2.3 as a suite of NIST Interagency Reports (NIST IRs
> 7695 through 7698), the specification of the CPE standard itself
> transitioned from MITRE to NIST. Throughout that time, MITRE held the
> CPE trademark, maintained a legacy e-mail address for CPE submissions
> (cpe@mitre.org <mailto:cpe@mitre.org>), maintained the official CPE
> website (cpe.mitre.org), and operated and moderated the CPE Discussion
> List (cpe-discussion-list@lists.mitre.org
> <mailto:cpe-discussion-list@lists.mitre.org>). Going forward, all of
> CPE’s operating functions as well as ownership of the trademark will
> transition to NIST, and NIST will be fully responsible for all official
> CPE correspondence with vendors, the government, and the community.
> MITRE will continue to participate in an advisory role.
>
> We believe that this change will enable CPE to continue to evolve to
> meet the needs of all stakeholders and community members.
>
> /Brant
>
> Brant A. Cheikes
>
> MITRE CPE Task Lead
> The MITRE Corporation
> 202 Burlington Road, M/S K302
> Bedford, MA 01730-1420
> Tel. 781-271-7505; Cell. 617-694-8180; Fax. 781-271-2352
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

From tony@yaanatech.com  Wed Mar 13 10:41:09 2013
Return-Path: <tony@yaanatech.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDE821F8D66 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 10:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-5nfF87kvBz for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 10:41:08 -0700 (PDT)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id CB05E21F87E7 for <mile@ietf.org>; Wed, 13 Mar 2013 10:41:08 -0700 (PDT)
Received: from [192.168.0.7] (pool-71-171-119-5.clppva.fios.verizon.net [71.171.119.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id 3288958081; Wed, 13 Mar 2013 17:41:08 +0000 (UTC)
Message-ID: <5140BA33.7070204@yaanatech.com>
Date: Wed, 13 Mar 2013 13:41:07 -0400
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: mile@ietf.org
References: <16822261.15.1363119812782.JavaMail.tcastaldi@dell-tcastaldi>
In-Reply-To: <16822261.15.1363119812782.JavaMail.tcastaldi@dell-tcastaldi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: [mile] ICANN Releases Guideline for Coordinated Vulnerability Disclosure Reporting
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
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, 13 Mar 2013 17:41:09 -0000

A URL is provided in the article.
http://www.circleid.com/posts/20130312_icann_guideline_for_coordinated_vu=
lnerability_disclosure_reporting/

It's not clear ICANN is working with the
IETF or other cybersecurity communities.
Might be useful to get them to engage.

--tony


From eburger@standardstrack.com  Wed Mar 13 11:18:18 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C304321F8EBB for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 11:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.292
X-Spam-Level: 
X-Spam-Status: No, score=-102.292 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ-iffFfWSe7 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 11:18:18 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) by ietfa.amsl.com (Postfix) with ESMTP id 3459621F8EB5 for <mile@ietf.org>; Wed, 13 Mar 2013 11:18:18 -0700 (PDT)
Received: from dhcp-642f.meeting.ietf.org ([130.129.100.47]:58427) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UFqFk-0006b6-GO; Wed, 13 Mar 2013 11:18:16 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <5140BA33.7070204@yaanatech.com>
Date: Wed, 13 Mar 2013 14:18:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E31BCC43-EC57-4840-9890-C29DA17704F9@standardstrack.com>
References: <16822261.15.1363119812782.JavaMail.tcastaldi@dell-tcastaldi> <5140BA33.7070204@yaanatech.com>
To: tony@yaanatech.com
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: mile@ietf.org
Subject: Re: [mile] ICANN Releases Guideline for Coordinated Vulnerability Disclosure Reporting
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 18:18:18 -0000

According to their document, they are not working with anyone. It simply =
says they will be happy to receive emails about threats and, if you are =
a trusted partner, they will be happy to send you an email.

All manual.

On Mar 13, 2013, at 1:41 PM, Tony Rutkowski <tony@yaanatech.com> wrote:

> A URL is provided in the article.
> =
http://www.circleid.com/posts/20130312_icann_guideline_for_coordinated_vul=
nerability_disclosure_reporting/
>=20
> It's not clear ICANN is working with the
> IETF or other cybersecurity communities.
> Might be useful to get them to engage.
>=20
> --tony
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Wed Mar 13 12:05:06 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E941521F8DC9 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 12:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level: 
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNHPPf2kOqAu for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 12:05:05 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB1E21F8E42 for <mile@ietf.org>; Wed, 13 Mar 2013 12:04:51 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DJ4kgE008153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 13 Mar 2013 15:04:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 13 Mar 2013 15:04:32 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2DJ4T9F006200 for <mile@ietf.org>; Wed, 13 Mar 2013 15:04:30 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Wed, 13 Mar 2013 15:04:29 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Wed, 13 Mar 2013 15:04:29 -0400
Thread-Topic: Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQHOIB2WPSqPazjoCkaiTRDs9BRkdw==
Message-ID: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 19:05:06 -0000

Hello,

In today's MILE session, a call for consensus began to include MMDEF in the=
 SCI draft as the mandatory-to-implement (MTI) specification.  The call for=
 consensus will last for 2 weeks and we ask that you contribute your opinio=
n.  The vote in the room was unanimous and we want to make sure we hear fro=
m participants not in attendance.

Poll will end on Wednesday next week.

Thank you!
Kathleen=

From tony@yaanatech.com  Wed Mar 13 12:06:14 2013
Return-Path: <tony@yaanatech.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F5B11E8185 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 12:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2fswvLZ6hp2 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 12:06:12 -0700 (PDT)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFCE11E818D for <mile@ietf.org>; Wed, 13 Mar 2013 12:06:12 -0700 (PDT)
Received: from [192.168.0.7] (pool-71-171-119-5.clppva.fios.verizon.net [71.171.119.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id D355058081; Wed, 13 Mar 2013 19:06:11 +0000 (UTC)
Message-ID: <5140CE22.2050508@yaanatech.com>
Date: Wed, 13 Mar 2013 15:06:10 -0400
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070802070709020804030703"
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
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, 13 Mar 2013 19:06:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms070802070709020804030703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Yes.

On 3/13/2013 3:04 PM, Moriarty, Kathleen wrote:
> Hello,
>
> In today's MILE session, a call for consensus began to include MMDEF in=
 the SCI draft as the mandatory-to-implement (MTI) specification.  The ca=
ll for consensus will last for 2 weeks and we ask that you contribute you=
r opinion.  The vote in the room was unanimous and we want to make sure w=
e hear from participants not in attendance.
>
> Poll will end on Wednesday next week.
>
> Thank you!
> Kathleen
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile



--------------ms070802070709020804030703
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINDTCC
BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0
aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp
bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx
MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh
dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg
U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn
/R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb
jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR
I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk
VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh
xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI
KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t
MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG
AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw
Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl
cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx
GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE
Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy
aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT
MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD
BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB
dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP
wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM
YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi
Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t
lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ
3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggbDMIIFq6ADAgECAhBT
hNb1O1n4bTJo0Ah1+gicMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE
ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv
cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzAzMDgwMDAwMDBa
Fw0xNDAzMDkyMzU5NTlaMIHEMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx
MzYyNzM4NTgzNTAzMSEwHwYJKoZIhvcNAQkBFhJ0b255QHlhYW5hdGVjaC5jb20xDzANBgNV
BAsMBlMvTUlNRTEeMBwGA1UECwwVUGVyc29uYSBOb3QgVmFsaWRhdGVkMR8wHQYDVQQLDBZT
eW1hbnRlYyBUcnVzdCBOZXR3b3JrMR0wGwYDVQQKDBRTeW1hbnRlYyBDb3Jwb3JhdGlvbjCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALTsANG1JvM4PXw45I4MAIPHPeu6urf2
ml82bH8tuyaGBzUX8AaxBPzChNDbng2wU264FzNKHOVQbiFAH14Xxb1Ih5uPvWh45feCO7PU
tSlkdHQSzilC8aOWEdy4+DZXzujp331xSZkjbT1iNWBhjhXubJTDwiYQWT0MBiN3A2IWC+1a
PVQvzSZyLLrM7QexO0A3fGuzWtJ9RMUBw++KuB3FQ/nM5iyKhfu2tfP7yiBV4rlwWdbbNe02
PLs2qwMPxIja/JT6tUdgjTn04XUynFgAbTVZniUkra+OodXxk9JGeIGgB+GorAwT0x/TcDeN
+DXoHfiBSso2Vmvwx+JkFNECAwEAAaOCAsswggLHMAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/
BAQDAgWgMCAGA1UdJQEB/wQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU+ENL
NB52WskhlVdfucmC2XHR4Y8wHQYDVR0RBBYwFIESdG9ueUB5YWFuYXRlY2guY29tMB8GA1Ud
IwQYMBaAFK35w5NyLbW5KGHkpNdg1cQKXhoBMIIBKwYIKwYBBQUHAQEEggEdMIIBGTCCARUG
CCsGAQUFBzAChoIBB2xkYXA6Ly9kaXJlY3RvcnkudmVyaXNpZ24uY29tL0NOJTIwJTNEJTIw
U3ltYW50ZWMlMjBDbGFzcyUyMDElMjBJbmRpdmlkdWFsJTIwU3Vic2NyaWJlciUyMENBJTIw
LSUyMEc0JTJDJTIwT1UlMjAlM0QlMjBQZXJzb25hJTIwTm90JTIwVmFsaWRhdGVkJTJDJTIw
T1UlMjAlM0QlMjBTeW1hbnRlYyUyMFRydXN0JTIwTmV0d29yayUyQyUyME8lMjAlM0QlMjBT
eW1hbnRlYyUyMENvcnBvcmF0aW9uJTJDJTIwQyUyMCUzRCUyMFVTP2NBQ2VydGlmaWNhdGU7
YmluYXJ5MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9wa2ktY3JsLnN5bWF1dGguY29tL2Nh
XzU2MWMxMDM2OTBjOTdhNjkyNDdhMGVmMDcxYWM4MWFmL0xhdGVzdENSTC5jcmwwbAYDVR0g
BGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGgu
Y29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTAqBgpg
hkgBhvhFARADBBwwGgYRYIZIAYb4RQEQAQICBAGGsxcWBTEwOTIyMA0GCSqGSIb3DQEBBQUA
A4IBAQDGN/ju6G1Df12wYlBSOzo39vOfJuVASX31X0WWvLieGYzIFPY1IRubH/TCfsUmdGxT
12q1Y6zm1nK+wmPg1xOFhgJNK9+Tfixu2WoKtkG5ZCeWcv48tyUGcr6+UHfvSdLxSQfmNuEU
6T30xH9zEkzChmI9FoUP4V+DjS49bbP9b3KlMNkJDOKrVNI5I233qmYxZZYatMartahrBIwy
Qfgor3+M/O8QYzYCAeSMwtpNYNqNXOlLBSCbGt4Y1Kdz7Xgg0fD49vMvRloZ3cMCCv2cLeg2
WlbxotVsn9IbWHq4CZbUKytgREtcbHUgbiIrYnlC4rcSxjX71W1W/u/gDNqgMYIEUjCCBE4C
AQEwgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEf
MB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3Qg
VmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEc0AhBThNb1O1n4bTJo0Ah1+gicMAkGBSsOAwIaBQCgggJrMBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDMxMzE5MDYxMFowIwYJKoZI
hvcNAQkEMRYEFKEGODYr7ok+wDSmt33M+YTZucX8MGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZI
AWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZI
hvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgcwGCSsGAQQBgjcQBDGBvjCBuzCB
pjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBvcmF0aW9uMR8wHQYDVQQL
ExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0
ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENB
IC0gRzQCEFOE1vU7WfhtMmjQCHX6CJwwgc4GCyqGSIb3DQEJEAILMYG+oIG7MIGmMQswCQYD
VQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFu
dGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG
A1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNAIQ
U4TW9TtZ+G0yaNAIdfoInDANBgkqhkiG9w0BAQEFAASCAQAaE53rmUR5dV4nZQ/g4TkVg1TA
iZ8Tdo+1SEed4tOaMjvNvnZQ/b6TuOKa+oh3FGo/swq3LH76a4rr64K5EdPorTDYDc+o90br
t+B3LgD0f3LAkJveou1ILsaKLqCPL6Ve9CqsYZf0YF1x1VZODT36yUio/pgwaHSBqDPQOogv
nx2sswxBNbDC4DKP5j470PqfCANugRHgZ+egm2d/aoqKk77qAvY1zuvG3YNdeso6hHPryjRm
KRWPHpaxWCUAy6Mr30fpfM0E7BAPJwfVMGL4idqQoByKHIFcGd0/kE3BYG6Id7p9LJtOcSY0
HvUFNqVmJqYm2bcLFmmjzHMqn1wcAAAAAAAA
--------------ms070802070709020804030703--

From trammell@tik.ee.ethz.ch  Wed Mar 13 16:22:38 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2823811E810D for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 16:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeXhVuM+gK7x for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 16:22:37 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 4831D11E8128 for <mile@ietf.org>; Wed, 13 Mar 2013 16:22:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 6248AD9305 for <mile@ietf.org>; Thu, 14 Mar 2013 00:22:30 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pIqFubxRm-rw for <mile@ietf.org>; Thu, 14 Mar 2013 00:22:30 +0100 (MET)
Received: from dhcp-5213.meeting.ietf.org (dhcp-5213.meeting.ietf.org [130.129.82.19]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id EB4DBD9304 for <mile@ietf.org>; Thu, 14 Mar 2013 00:22:29 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE13CAD6-E97D-4C15-AA76-8491734AEE18@tik.ee.ethz.ch>
Date: Wed, 13 Mar 2013 19:22:27 -0400
To: MILE IETF <mile@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [mile] Draft minutes posted
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 23:22:38 -0000

Greetings, all,

Draft minutes for today's MILE session at IETF 86 in Orlando have been =
posted to http://www.ietf.org/proceedings/86/minutes/minutes-86-mile. =
Many thanks again to David Black and Chris Inacio for taking notes! =
Please direct any comments or errata to the mile-chairs@tools.ietf.org.

Best regards,

Brian=

From ietf@meetecho.com  Wed Mar 13 16:26:58 2013
Return-Path: <ietf@meetecho.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC64011E8153 for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 16:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.658
X-Spam-Level: 
X-Spam-Status: No, score=-0.658 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H229MXy0SJHM for <mile@ietfa.amsl.com>; Wed, 13 Mar 2013 16:26:58 -0700 (PDT)
Received: from smtpdg7.aruba.it (smtpdg3.aruba.it [62.149.158.233]) by ietfa.amsl.com (Postfix) with ESMTP id B462811E8155 for <mile@ietf.org>; Wed, 13 Mar 2013 16:26:57 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.16.136]) by smtpcmd03.ad.aruba.it with bizsmtp id BBSt1l00E2w8SR601BSvAX; Thu, 14 Mar 2013 00:26:56 +0100
Date: Wed, 13 Mar 2013 19:26:51 -0400 (EDT)
From: Meetecho Team <ietf@meetecho.com>
To: mile@ietf.org
Message-ID: <4916061.1.1363217211090.JavaMail.tcastaldi@dell-tcastaldi>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_0_2614099.1363217211042"
Subject: [mile] MILE session recording available
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Mar 2013 23:26:59 -0000

------=_Part_0_2614099.1363217211042
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
MILE WG session at IETF 86 is available at the following URL:
http://ietf86.conf.meetecho.com/index.php/Recorded_Sessions#MILE

In case of problems with the playout, just drop an e-mail to ietf-support@meetecho.com.

For the chair(s): please feel free to put the link to the recording in the minutes,
if you think this might be useful.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_0_2614099.1363217211042--

From pkampana@cisco.com  Thu Mar 14 07:00:06 2013
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8A621F8F0C for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzt+40xiZHno for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:00:02 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 657B511E80E1 for <mile@ietf.org>; Thu, 14 Mar 2013 07:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=978; q=dns/txt; s=iport; t=1363269602; x=1364479202; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=a80q83q2SdYDeJuaxpaJMaQfUQwKFcElXUweHXuvL9g=; b=Lr/2t5b8tsYSCTCxMgQ8zmyzaFbbnglaPfoF9iKzKo1PPatPo8kUGRdZ CwrUvQ4oOtnPJhc+mZkRAuaixj5h2NrWop2vyqraooNW9K6++CM5V14bN f8NgliSlSAqwsOTc3BTY6RufbyiZJ+siu52XTG4WgcdP37AIPBHrzv8Ok k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAE7XQVGtJXG//2dsb2JhbABDh2G9FYFfFnSCKgEBAQQBAQEaHTQXBAIBCBEEAQELFAkHJwsUCQgCBAESCIgMDMElBI5fJhIGgllhA6dagwqCKA
X-IronPort-AV: E=Sophos;i="4.84,845,1355097600"; d="scan'208";a="184447599"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 14 Mar 2013 14:00:01 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2EE00bD028009 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Mar 2013 14:00:00 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 09:00:00 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQHOIB2WPSqPazjoCkaiTRDs9BRkd5ilNp0g
Date: Thu, 14 Mar 2013 13:59:59 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.89.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:00:07 -0000

I agree with MMDEF included in SCI.
I am not sure why it must be MTI. Due to some audio problems I missed part =
of the call yesterday. Can you briefly summarize why we want it MTI?

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Wednesday, March 13, 2013 3:04 PM
To: mile@ietf.org
Subject: [mile] Consensus Call - SCI draft MMDEF as MTI

Hello,

In today's MILE session, a call for consensus began to include MMDEF in the=
 SCI draft as the mandatory-to-implement (MTI) specification.  The call for=
 consensus will last for 2 weeks and we ask that you contribute your opinio=
n.  The vote in the room was unanimous and we want to make sure we hear fro=
m participants not in attendance.

Poll will end on Wednesday next week.

Thank you!
Kathleen
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile

From kathleen.moriarty@emc.com  Thu Mar 14 07:38:41 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B7E11E8185 for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILV9wmrNa7tl for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:38:40 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id A023F11E8112 for <mile@ietf.org>; Thu, 14 Mar 2013 07:38:29 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2EEcL0S026981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Mar 2013 10:38:24 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Thu, 14 Mar 2013 10:38:13 -0400
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2EEcBQT015976; Thu, 14 Mar 2013 10:38:12 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Thu, 14 Mar 2013 10:38:11 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, "mile@ietf.org" <mile@ietf.org>
Date: Thu, 14 Mar 2013 10:38:10 -0400
Thread-Topic: Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQHOIB2WPSqPazjoCkaiTRDs9BRkd5ilNp0ggAAKlk4=
Message-ID: <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com>
In-Reply-To: <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:38:41 -0000

Hello Panos,

Thank you for joining us remotely!  The recording is available for those wh=
o were not able to attend during the session.

We need to choose one included schema as MTI for 'black box' testing of the=
 method described.  Essentially, if you can exchange using the MTI spec, th=
en any other specs supported should theoretically work as the pattern has b=
een established.

MMDEF was recommended as it is in use by the eCrime WG as an extension to I=
ODEF/RFC5901.  It replaced the method to include malware in exchanges and s=
eemed to make sense to adopt more broadly as it is maintained by a group in=
 IEEE focused on that particular problem.

BTW, I meant to say the last call will end in two weeks from yesterday, Wed=
nesday March 27th.

Thank you!
Kathleen
________________________________________
From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
Sent: Thursday, March 14, 2013 9:59 AM
To: Moriarty, Kathleen; mile@ietf.org
Subject: RE: Consensus Call - SCI draft MMDEF as MTI

I agree with MMDEF included in SCI.
I am not sure why it must be MTI. Due to some audio problems I missed part =
of the call yesterday. Can you briefly summarize why we want it MTI?

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Wednesday, March 13, 2013 3:04 PM
To: mile@ietf.org
Subject: [mile] Consensus Call - SCI draft MMDEF as MTI

Hello,

In today's MILE session, a call for consensus began to include MMDEF in the=
 SCI draft as the mandatory-to-implement (MTI) specification.  The call for=
 consensus will last for 2 weeks and we ask that you contribute your opinio=
n.  The vote in the room was unanimous and we want to make sure we hear fro=
m participants not in attendance.

Poll will end on Wednesday next week.

Thank you!
Kathleen
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile

From david.black@emc.com  Thu Mar 14 07:54:08 2013
Return-Path: <david.black@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC62D11E812C for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.892
X-Spam-Level: 
X-Spam-Status: No, score=-101.892 tagged_above=-999 required=5 tests=[AWL=0.707, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-gRmtt+mxxY for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 07:54:04 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id F29421F0D0B for <mile@ietf.org>; Thu, 14 Mar 2013 07:54:03 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2EErvia028198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 14 Mar 2013 10:54:02 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 14 Mar 2013 10:53:46 -0400
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2EErjcQ025914 for <mile@ietf.org>; Thu, 14 Mar 2013 10:53:45 -0400
Received: from mx15a.corp.emc.com ([169.254.1.118]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Thu, 14 Mar 2013 10:53:45 -0400
From: "Black, David" <david.black@emc.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>
Date: Thu, 14 Mar 2013 10:53:43 -0400
Thread-Topic: Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQHOIB2WPSqPazjoCkaiTRDs9BRkd5ilNp0ggAAKlk6AAASdEA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com> <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 14:54:08 -0000

I support MMDEF as the MTI, and since MMDEF is a malware spec, I'd like
to resurrect a previously-discussed suggestion that the SCI draft include
discussion of the "EICAR Standard Anti-Virus Test File" as a specific
example that SHOULD (or MUST?) be supported for black-box testing purposes.

See: http://www.eicar.org/86-0-Intended-use.html

Thanks,
--David

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Thursday, March 14, 2013 10:38 AM
> To: Panos Kampanakis (pkampana); mile@ietf.org
> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>=20
> Hello Panos,
>=20
> Thank you for joining us remotely!  The recording is available for those =
who
> were not able to attend during the session.
>=20
> We need to choose one included schema as MTI for 'black box' testing of t=
he
> method described.  Essentially, if you can exchange using the MTI spec, t=
hen
> any other specs supported should theoretically work as the pattern has be=
en
> established.
>=20
> MMDEF was recommended as it is in use by the eCrime WG as an extension to
> IODEF/RFC5901.  It replaced the method to include malware in exchanges an=
d
> seemed to make sense to adopt more broadly as it is maintained by a group=
 in
> IEEE focused on that particular problem.
>=20
> BTW, I meant to say the last call will end in two weeks from yesterday,
> Wednesday March 27th.
>=20
> Thank you!
> Kathleen
> ________________________________________
> From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
> Sent: Thursday, March 14, 2013 9:59 AM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: RE: Consensus Call - SCI draft MMDEF as MTI
>=20
> I agree with MMDEF included in SCI.
> I am not sure why it must be MTI. Due to some audio problems I missed par=
t of
> the call yesterday. Can you briefly summarize why we want it MTI?
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Moriarty, Kathleen
> Sent: Wednesday, March 13, 2013 3:04 PM
> To: mile@ietf.org
> Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
>=20
> Hello,
>=20
> In today's MILE session, a call for consensus began to include MMDEF in t=
he
> SCI draft as the mandatory-to-implement (MTI) specification.  The call fo=
r
> consensus will last for 2 weeks and we ask that you contribute your opini=
on.
> The vote in the room was unanimous and we want to make sure we hear from
> participants not in attendance.
>=20
> Poll will end on Wednesday next week.
>=20
> Thank you!
> Kathleen
> _______________________________________________
> 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 pkampana@cisco.com  Thu Mar 14 08:28:18 2013
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BE211E82C1 for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 08:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkBWnPgwLgan for <mile@ietfa.amsl.com>; Thu, 14 Mar 2013 08:28:13 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id AF02211E82C6 for <mile@ietf.org>; Thu, 14 Mar 2013 08:28:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2430; q=dns/txt; s=iport; t=1363274890; x=1364484490; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=YMmI1NKKCt1uH80xKnkZHCuGRbHdhxKy+vhTwLbE5bA=; b=T2H3wC/eOTR5laoz2KwxESLk8SX6xE1phbZIBD2BILmg0EqD7MHCJ0VO mNhdDr99QcqEIfw7GCA58juZDyhZUKYUtiDF9ygeC3GfkLslCNC0wQnfC 2X3jNsUXsNW77cMbCtEqkUyTPThub07iLdEMaAma8ESXYcxfR+96Xzg9K Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJzqQVGtJV2a/2dsb2JhbABDxHiBYhZ0gioBAQEEAQEBGh00FwQCAQgRBAEBCxQJBycLFAkIAgQBEgiIDAzBMASOXyYSBoJZYQOnWoMKgig
X-IronPort-AV: E=Sophos;i="4.84,845,1355097600"; d="scan'208";a="187479946"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 14 Mar 2013 15:28:10 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r2EFS9Bj015081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Mar 2013 15:28:09 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 10:28:09 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQHOIB2WPSqPazjoCkaiTRDs9BRkd5ilNp0ggAAKlk6AAA88oA==
Date: Thu, 14 Mar 2013 15:28:08 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A7519298A@xmb-rcd-x10.cisco.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com> <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.102.89.108]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 14 Mar 2013 15:28:18 -0000

Makes sense.  I thought that CVE was MTI in the SCI draft. At least that is=
 my recollection from previous descussions.
But I agree with MMDEF being the MTI also.
Rgs,
Panos


-----Original Message-----
From: Moriarty, Kathleen [mailto:kathleen.moriarty@emc.com]=20
Sent: Thursday, March 14, 2013 10:38 AM
To: Panos Kampanakis (pkampana); mile@ietf.org
Subject: RE: Consensus Call - SCI draft MMDEF as MTI

Hello Panos,

Thank you for joining us remotely!  The recording is available for those wh=
o were not able to attend during the session.

We need to choose one included schema as MTI for 'black box' testing of the=
 method described.  Essentially, if you can exchange using the MTI spec, th=
en any other specs supported should theoretically work as the pattern has b=
een established.

MMDEF was recommended as it is in use by the eCrime WG as an extension to I=
ODEF/RFC5901.  It replaced the method to include malware in exchanges and s=
eemed to make sense to adopt more broadly as it is maintained by a group in=
 IEEE focused on that particular problem.

BTW, I meant to say the last call will end in two weeks from yesterday, Wed=
nesday March 27th.

Thank you!
Kathleen
________________________________________
From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
Sent: Thursday, March 14, 2013 9:59 AM
To: Moriarty, Kathleen; mile@ietf.org
Subject: RE: Consensus Call - SCI draft MMDEF as MTI

I agree with MMDEF included in SCI.
I am not sure why it must be MTI. Due to some audio problems I missed part =
of the call yesterday. Can you briefly summarize why we want it MTI?

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Wednesday, March 13, 2013 3:04 PM
To: mile@ietf.org
Subject: [mile] Consensus Call - SCI draft MMDEF as MTI

Hello,

In today's MILE session, a call for consensus began to include MMDEF in the=
 SCI draft as the mandatory-to-implement (MTI) specification.  The call for=
 consensus will last for 2 weeks and we ask that you contribute your opinio=
n.  The vote in the room was unanimous and we want to make sure we hear fro=
m participants not in attendance.

Poll will end on Wednesday next week.

Thank you!
Kathleen
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile

From superuser@gmail.com  Thu Mar 21 13:14:32 2013
Return-Path: <superuser@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 574CB21F899E for <mile@ietfa.amsl.com>; Thu, 21 Mar 2013 13:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EC9G14mLCKep for <mile@ietfa.amsl.com>; Thu, 21 Mar 2013 13:14:32 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id AB58721F896C for <mile@ietf.org>; Thu, 21 Mar 2013 13:14:28 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id hm14so7046703wib.3 for <mile@ietf.org>; Thu, 21 Mar 2013 13:14:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=RryqNgzGHXhY/wFds9vI0UZze5nXev7pV/GF/e28CBE=; b=1JB/zFsdhrgTeMjXcqtwaLQKa9Fv7bfN+4FfEyemvEJsP6e81KFsCJaIFC/iqjEd3p GiF41FS79wsufNe+TUNmGG5JFKqUJVVtBYky2UjJ4XNjv4Ufa/DX/RdOrP5mTDe/7amP zd1Svwj3cRLxSOIkr3NOSAVpVwbrof/oGVBmnP85tOz1jdJ96LfdD+79IKmrDPORR0S8 mvzLIEUVupM1Vu93GMz+PlN6YB6UmuVng+Fma6W0WGpEsS1r8F9Tgve4oM7tKYQwESEB x8oR4iDBKNwGExVRSVnnFBh5pK4bInhddwZRKLzto7RZJIWJNRHAWpY2JNWDQkkXqbbF ugxQ==
MIME-Version: 1.0
X-Received: by 10.180.185.44 with SMTP id ez12mr7038364wic.33.1363896864446; Thu, 21 Mar 2013 13:14:24 -0700 (PDT)
Received: by 10.180.13.71 with HTTP; Thu, 21 Mar 2013 13:14:24 -0700 (PDT)
Date: Thu, 21 Mar 2013 13:14:24 -0700
Message-ID: <CAL0qLwbAQnEnB_xwBecUJM_6pxSCKdBhYV0=+4Xk3Uxw=NuKfQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "mile@ietf.org" <mile@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c225741d9de204d874fc5c
Subject: [mile] Implementations
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 21 Mar 2013 20:14:32 -0000

--001a11c225741d9de204d874fc5c
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I'm curious to gauge the deployment of IODEF to date.  The mobile incident
reporting work I mentioned in Orlando is considering several protocol
options on which to base its work.

Is there a list someplace of organizations, software packages, vendors,
etc. that use IODEF, and perhaps some measure of the scale in which they're
using it?

Thanks,
-MSK

--001a11c225741d9de204d874fc5c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi all,<br><br></div>I&#39;m curious to gau=
ge the deployment of IODEF to date.=A0 The mobile incident reporting work I=
 mentioned in Orlando is considering several protocol options on which to b=
ase its work.<br>
<br></div>Is there a list someplace of organizations, software packages, ve=
ndors, etc. that use IODEF, and perhaps some measure of the scale in which =
they&#39;re using it?<br><br>Thanks,<br></div>-MSK<br></div>

--001a11c225741d9de204d874fc5c--

From kathleen.moriarty@emc.com  Thu Mar 21 17:23:53 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD7121F8AF0 for <mile@ietfa.amsl.com>; Thu, 21 Mar 2013 17:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HTrQcMNObiiH for <mile@ietfa.amsl.com>; Thu, 21 Mar 2013 17:23:52 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8487B21F8AE6 for <mile@ietf.org>; Thu, 21 Mar 2013 17:23:52 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2M0NohM023940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Mar 2013 20:23:50 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 21 Mar 2013 20:23:36 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2M0Navo031688; Thu, 21 Mar 2013 20:23:36 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Thu, 21 Mar 2013 20:23:36 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, "mile@ietf.org" <mile@ietf.org>
Date: Thu, 21 Mar 2013 20:21:49 -0400
Thread-Topic: [mile] Implementations
Thread-Index: Ac4mcL57vecXDN5qQviZM06KdoZ8rwAIoAVm
Message-ID: <F5063677821E3B4F81ACFB7905573F24DA806812@MX15A.corp.emc.com>
References: <CAL0qLwbAQnEnB_xwBecUJM_6pxSCKdBhYV0=+4Xk3Uxw=NuKfQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbAQnEnB_xwBecUJM_6pxSCKdBhYV0=+4Xk3Uxw=NuKfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Implementations
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 22 Mar 2013 00:23:54 -0000

Hi Murray,

Hopefully others will chime in, I am aware of the following:

Anti-phiushing working group (APWG)
eCrime working group
CIF (Ren-ISAC & some others working with them, I think some telcos)
DFLabs - has a product that uses IODEF
I think Arcsite also supports IODEF

There may be a few others...

Thanks,
Kathleen
________________________________________
From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Murray S. =
Kucherawy [superuser@gmail.com]
Sent: Thursday, March 21, 2013 4:14 PM
To: mile@ietf.org
Subject: [mile] Implementations

Hi all,

I'm curious to gauge the deployment of IODEF to date.  The mobile incident =
reporting work I mentioned in Orlando is considering several protocol optio=
ns on which to base its work.

Is there a list someplace of organizations, software packages, vendors, etc=
. that use IODEF, and perhaps some measure of the scale in which they're us=
ing it?

Thanks,
-MSK

From takeshi_takahashi@nict.go.jp  Sat Mar 23 01:17:39 2013
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9439F21F8457 for <mile@ietfa.amsl.com>; Sat, 23 Mar 2013 01:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.455
X-Spam-Level: **
X-Spam-Status: No, score=2.455 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_JP=1.244, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tq7sXSgISewt for <mile@ietfa.amsl.com>; Sat, 23 Mar 2013 01:17:35 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id A1B4F21F896B for <mile@ietf.org>; Sat, 23 Mar 2013 01:17:18 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id r2N8GsKh016726 for <mile@ietf.org>; Sat, 23 Mar 2013 17:16:54 +0900 (JST)
Received: from gw2.nict.go.jp (localhost [127.0.0.1]) by gw2.nict.go.jp  with ESMTP id r2N8GsWs024097 for <mile@ietf.org>; Sat, 23 Mar 2013 17:16:54 +0900 (JST)
Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp  with ESMTP id r2N8Gsgl024094 for <mile@ietf.org>; Sat, 23 Mar 2013 17:16:54 +0900 (JST)
Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id C91742C6CF for <mile@ietf.org>; Sat, 23 Mar 2013 17:16:53 +0900 (JST)
Received: from VAIO (unknown [133.243.119.109]) by mail2.nict.go.jp (NICT Mail) with ESMTP id BD00716963 for <mile@ietf.org>; Sat, 23 Mar 2013 17:16:53 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com>	<F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com>
Date: Sat, 23 Mar 2013 17:16:56 +0900
Message-ID: <000601ce279e$c8ab7940$5a026bc0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0007_01CE27EA.38939670"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFCibkFcoiRAxGJUwOvO7kpytpEUwHYmM6bAq+IVDUBugT0/pmYF3cA
Content-Language: ja
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 23 Mar 2013 08:17:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0007_01CE27EA.38939670
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

I remember the discussion on the EICAR and agree upon David's kind
suggestion.
The attached is the revised SCI draft, whose section 10 talks about the
EICAR (with an example XML).

Kind regards,
Take


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: Thursday, March 14, 2013 11:54 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
> 
> I support MMDEF as the MTI, and since MMDEF is a malware spec, I'd like to
> resurrect a previously-discussed suggestion that the SCI draft include
> discussion of the "EICAR Standard Anti-Virus Test File" as a specific
example
> that SHOULD (or MUST?) be supported for black-box testing purposes.
> 
> See: http://www.eicar.org/86-0-Intended-use.html
> 
> Thanks,
> --David
> 
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
> > Of Moriarty, Kathleen
> > Sent: Thursday, March 14, 2013 10:38 AM
> > To: Panos Kampanakis (pkampana); mile@ietf.org
> > Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
> >
> > Hello Panos,
> >
> > Thank you for joining us remotely!  The recording is available for
> > those who were not able to attend during the session.
> >
> > We need to choose one included schema as MTI for 'black box' testing
> > of the method described.  Essentially, if you can exchange using the
> > MTI spec, then any other specs supported should theoretically work as
> > the pattern has been established.
> >
> > MMDEF was recommended as it is in use by the eCrime WG as an
> extension
> > to IODEF/RFC5901.  It replaced the method to include malware in
> > exchanges and seemed to make sense to adopt more broadly as it is
> > maintained by a group in IEEE focused on that particular problem.
> >
> > BTW, I meant to say the last call will end in two weeks from
> > yesterday, Wednesday March 27th.
> >
> > Thank you!
> > Kathleen
> > ________________________________________
> > From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
> > Sent: Thursday, March 14, 2013 9:59 AM
> > To: Moriarty, Kathleen; mile@ietf.org
> > Subject: RE: Consensus Call - SCI draft MMDEF as MTI
> >
> > I agree with MMDEF included in SCI.
> > I am not sure why it must be MTI. Due to some audio problems I missed
> > part of the call yesterday. Can you briefly summarize why we want it
MTI?
> >
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
> > Of Moriarty, Kathleen
> > Sent: Wednesday, March 13, 2013 3:04 PM
> > To: mile@ietf.org
> > Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
> >
> > Hello,
> >
> > In today's MILE session, a call for consensus began to include MMDEF
> > in the SCI draft as the mandatory-to-implement (MTI) specification.
> > The call for consensus will last for 2 weeks and we ask that you
contribute
> your opinion.
> > The vote in the room was unanimous and we want to make sure we hear
> > from participants not in attendance.
> >
> > Poll will end on Wednesday next week.
> >
> > Thank you!
> > Kathleen
> > _______________________________________________
> > 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
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

------=_NextPart_000_0007_01CE27EA.38939670
Content-Type: application/pdf;
	name="draft-ietf-mile-sci-07.txt.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="draft-ietf-mile-sci-07.txt.pdf"

JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFIvRmlsdGVyIC9GbGF0ZURlY29k
ZT4+CnN0cmVhbQp4nK1WXW/bOBB8969Y9KUJEH8laNP2LXWcwmiS5hId7g5NHyhqZbORRJWkUvvf
d5aWP4vcFdfIcCzL5Ozs7Owy32jQG9JAXu2nLjv921Oa+s6APuA97XzrDOMCaj90Se8TLHpDw2NK
8s5y35COT+j05C0lZefganI5pr+sezDVlD4429T0y1fSo0Q9qJnyM3OYfO0MTyi57BxMqsCu4tA9
dyoPvw63fV1PRsnhyyVWlXFGPqjQ+Hd0F1SVKZd5SpzSD/+G8bFHl1icGy4ywfp/TLavK32WMz8D
FpS7MkWh3PPw+vNuNL5Nfg/rnx59VJlN1SKW81l40fXZ5O43eRFdcAr/HtHxYHgCLDHu5QZx8ul8
fNHlOXzija0otw5mcY0OjYNv9CJl51k3zoQFmQo/lypgIZBavz4RNhP3dg2HvFuagrtem+7gdS/M
A7Yev45bz1KEUjq0KSYz4ymzuim5ChQ5wahhxjSptMnk4af0K+tA5+y1M7UQofFcz1Q1ZbqI3HaI
3R/E/O4PKePcVEjIVHR7MaJXg9MBfcad3HyhYBGuheHKGT3jleefVIBUadH0u7+DowmGPaFzKFfa
FAadt/I8UjGObM0uIvge9A9UO/uI7JaZalWrVHYtyObEZcpZJrNlU5MWa4vJEflGz0h5iiIZtKzr
RgZ/X112U+Vj3uvlvU0B7uJYkEhR+ysu7XYt9kYRnvgmLU0ISyHzpihI2yVypZm+mzCTLHZqENMT
b8U470c3dPomkou3b7fYiB13IkJGB9R2vK6cEXGWrlgupnE1RXHZYdVO6ET5B7EFqMEJ4wRGgOTX
NjD2q0AWKI6mMrY9lWpBqvCWMgOxTdqsy/YzAbWvjZQyAaUCe4Ue7ODEr+tVLVSbFpRE+FkI9bt+
P1Oogkxjdj3pl551035sH99vcfr/rVLcsEXxURUmi+2skNrclE0pxLyZE3wbZn5HKamHCJAyNTUI
cXZEjutCabkDiE29LVgKny5a3bbkCABYrExuSl4aG1maStUwQO2MEtEtNZ5/pu8RK2ckqleSw6ko
pyokNHZpE0vGZRsa1atk2wspjVgRMaaOve+92Ag1svXCmeksSMXNGnrz+P5AYzLIXCQxB47Exoco
hbgLXerFtOueyiTivrvX40o1YWad+OAMXREDSFqe3SNnu+XbnXPLropjDZlu9Ue0+JrXS0+XPFXF
TvSbTW/dcoHuhksBEnedr8rT5n1/0PotCBzzxmsFxKk8d2VGQBDIyXkufDDkhIT4Ad5pceomxYbl
CIyNuJUMsr8pGAMHmT8a/i7b8SXbo6JhWBkei6NW0gXms0x02G9hG7eST1SAhOhGHeflcsDgSc3r
QwPp7lMY2Yzxp6xtFe2Jk0ROGRQwd7bcXU4lxADUq+Oo6fofsiPCXFFFb+9UG89rg/hPHrafbxSO
kOEXII6Tzh94/QAMXfAfZW5kc3RyZWFtCmVuZG9iago2IDAgb2JqCjEwODcKZW5kb2JqCjEyIDAg
b2JqCjw8L0xlbmd0aCAxMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJ2XUVPj
NhDH3/Mp9o27GUhjBwj0LZdAJzNwpcRz7UynD4q8dlRsKSfJkPTTd1exEydHC8YextiWf/rvane1
+Q6DfgQDPuurLHs/PY4gd70B/EJ/ee97LwoDoL7IEr4kNOgKohiSrLf9LoJ4CKPRFSRl79NMe7Qa
/dnUiszD8TH7dXpzezafzH54Ux+3uIB4EA0/J3/3hteQ3PU+0VOlZVGlCHNVrgqVKUzhy3wKd0qi
dgge1x6EgxSdtGpBb5WGOUqvjIbzPoLJPp/0omGD80uExFbOwx3mooAHa56Vo8EOhE5BWIQVP0qJ
9KL80lQeXoS1QvsNzUMsphzMxsjX1fVpeHwZpk7EomAxMDHkJu0bUtQnz2hvTVptNUO/4wkQH1gY
06MEbam0KUy+6cxj4rBWN6Sb8Yosk2KhCuW70/asc7q5WZPt7G2YYqa06mYxMWoW04Lnxl/HsHVt
ZizMvSUvVpZWYbJZoHUoK8uqZ5pelyJM9xorbrTxsk+FF5BsVvgz/HF/Nx0n4zd1XbRYwzZrUgjn
0HWxcc/a0tjOsfdCPj0IzxnWgXV5xGI7Hwrh2RvdIg1gdMRiO79VhUbbNTYAro5YHBtzaazSeSdV
9Fk0OGJd0MPfUTxpdB38/jrrktfymdL1EVfG+k6s+Ig1Yn+hVZlsx+H7WMMj1hU9fMQSU9Wd1cQ9
++meap7wxm7AG5hRCSOm9pCh4Cxyb7KaWGU/zZtkowrnqH7aIO0txo8spnHMJ1RzHXv9bL5CSbVV
MllSArxf16ipER/StGU1OcQ+H8snbV4KTPPgpw6cLavJoettXaUaodYwC3WG4n+JpWgXRi5p+4p5
zGpyKBr0WyyCjXXg8deTJconTqrd2gYHnDi4T2atmJImFEhevY42BS1xE+tRdKCFxEwowhTFGG2R
9SrWS8DyeOdslfAtq1m7KG6zvrFdhj6wwbibtWCL/l8txNcNi4rVI2ZokQKoY1WoWcN9Pkfbovx1
u6U8Yxv9AVYcWoDsYzQYNrVhXFG3Yt0JjNOUcrfTrtOwzvcNy3FjUs+S0JLpqqTNlZsZybssiLA7
OVAOcmteON5SsYHFhi+noa+iLo7ST/uDTkW1dmWNmDquQgsEG4otpqeAa7kUOud/meKWgvd2URqd
13qMzYVW/9RBRd2YsZTmDJJmhaGFC2HmlK/CoH7dibJao+v+sOkMvTGFA9QUjmyFq+Ryp6E2hPrE
wqJINzxZddDjsXsMYEZBrsjWYgO20lsf7ToRElUXoVOekTrYnY3v8k0p5FJpPGMJnDQ7c+quleTV
9rh9M1QilVIGNH1rMLY1xSksqM9Vfj8V0hKnNelZWGUqB9rosxY1eKet89D7+hkpANALVexIrdEk
/LayIaF3zLBcRKkXSEuykuM43BPiIq576SexFG6pKECo+S/6Rz8kbtYrxbvXfx1/PogcIf6LiDdJ
7zc6/wWRqTU7ZW5kc3RyZWFtCmVuZG9iagoxMyAwIG9iagoxMDk5CmVuZG9iagoxNyAwIG9iago8
PC9MZW5ndGggMTggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyNVsly2zgQvesr
unxJUqV4LLkSJ3NzvExcZUeJTR+mUjlAYEtCTAIMAFrRfP08LJRIeZyJZJkb0Mvr97r5g44OJ3QU
vvko69Eftye0dKMj+gu/5ejHaBIXUD7Imj4UWPSOJlMqFqO0b0LTYzo5eUdFPXp5pT1bzf71uRUL
T/ufq9n5xeXru7OrJ0/y55LnND2aHL8qvo+O31NxPXqJu6WRbc3auxdUC7lSml9bFqWYq0r5DQld
kl+1jhZChjvCsyPnsaSulFZ6+erFaHLcGZObOVvHsrVhr2nYCq+MdodYNX3brZppmGQy+GdpBQ/j
cG2Z+Kdynh6FVQYe03MhvXpUXnEvhH23JXuhKi5jtAiulb61uCzZSauaEAKZxV50Si+MrWN8YxIO
BoOpChFgp9J0xzJunEzokO6Ulkyulavn7PfwyaaeA2NMytPatFVJc8af5oWSSlTkDXE9z2lIox95
k00BCcf9iHHuVMmp6NsaDmEuYE6LecXYLnzAWLntUmDtWZcuViJZ+W/3O5S7uvQA+AWia+VXtF4p
ufofOEgKHYDYAVgeUgY8pweANOovsqVFBaKEvEKgMQ8XL5P3RIK2aYz12ENLK3RbCUsVP3IFHmQr
rmGpAvJ+s4/N1qHuzANxwJPCAfQeCtlZisvBSTjTvCbLwXWOBqlcGksSAURHUU8AulK10si1M9E2
lZIZOqOrTayLKEsVboEbW9AdfEh2TthNcJE5OE+SyFxB1BK6WnJg/T5p+ywSEF1jzSOoVPbIM0XU
BVtEaCqz7EhYwLDf3aXWJaEMsVuYqjLrxCujOWMZF95eng0I9ebo5Ii+4m44+UZ77MX+B95AKBYs
Pbi5vysOxulIn2bx/Pbiy/3V7cV5OL/7eHp9vT1JKwbO8GB2f53XhrOdlbPZzc3Fp/Nk6Ob074NU
poPZ5+Jq9un0+qDLsitWl2uAD8WcB2kCmcZy6B3CdUXZpk3TyeR9TDWcDFI9BtanTax+arkd2gb9
GGbxG0oH/LBLodU/qYSaOajYbGv+i4Y8FGjQJm7JqkW4sV6pdoHJvZV/5oCE90I+UIMjxtCYmkr4
sGho9bGtNJTdmx5rFg8Qkxt3fcC0AayahQMfo5oCN+NuaeqmxUOCVIEvaJYVg+Ac7oUshjRJkswc
DnJ3csV1LEtXhNwmsiKiHHohD+AStYnJIwSOc6ARNowe1OijWYcAYvMuTZCh6RpFDK+bQV2PSr2o
H8a+598ciqIK83iTh2NPyCGtntddFsmD22sPMGf2hkiw0B+qMcScQAcYUr8R32EJrQQB1ZH0z0zJ
D5s0QcrkjutsC4Ca3qDp9DNOwHVqCnMgjR2qjX2CKB758J5C2ZZFG1SoiNtRZGAKiINiCq3UcmhV
T9oLwPidUTZ48xmsGoC+HWgUyt6Lj8Kg3k608GQwx932tSvnmd6+Ks7oCC+6dMDy0PkR7HyzlUrg
ZoH5joI1jHGRpNxptvUmO3ry/rObwFj8ZhrzKMSDWAm3UmNitLfqcO8V8uJno8IIeu7z9bOAxI6/
weJFMfqC77/E/Y9sZW5kc3RyZWFtCmVuZG9iagoxOCAwIG9iagoxMTY0CmVuZG9iagoyMiAwIG9i
ago8PC9MZW5ndGggMjMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJx1VtFy2zYQ
fNdX3FuTGUWy7LRJ/ebGTkczSZraaqczmTyAwFFEQwIMAFpSv757ICWRTiKNTYkCDnu7e3f8SheL
FV3Ie7jqZra8f0XbOLug3/G3nX2drfICGi66od82WPSaVpe0KWf9vhVdXtGrV69p08yerV3i4Di9
uA2qTPT0tf7j9u7ti4c3629+GV5vuaDLi9XV882/s6tfafNu9kzu+kDWxaSc5jkpRz5slbP/qWS9
o52NlXVbSp4Ctz4kUhRZd8GmA7Zpa9il5z/NVlfHeDvlUpT1hqMOtmDaVSrRY1c7DqqwtezcqUi8
b2tvE5sF0aZiR6lixHaGAwJKKA000TZtfaAucp/gHOE4sAD95/07+oR/q8XFZ3pRqMiGVEpKf6EW
V3A1xAmsfTCIDxylr2u/i/1hB5fUHqEMPXqtiq5W4QDcpXUIVRzkEOtMF1M4DKFiy9qWVvfsWGTR
FGwMlguHrAz58pi58MaPHA4pU2gdlYF5CFT60ABO4n1C/ves2WJpTjlzastDxuiYJbrhpGwdJbrc
7dMcQg3JCuDa+y9yVtdS9A0flwtTSW3jODfc/15OT8EorbsGxCQeHXw6cmDWHpm2kN6opESMzKv2
XQ30FhTaokMQm8QbEsqKnRmkGYQLyXIkWw5x+qyhtU2V71L+LnlVXZM1wc5HIcm7uMCWy1+O7rtx
HrEDzKXgGxaFRPbsGid6KtNYJ3BUgvHF3pzdqitGXj0pZzNr70q77UIvN9isfEy427TIJUTRtMIR
45KZE3Jr1CFbmdSQ0NcOPpBzpgEEl9VVXq+65GEJ6FDD8FuWcklZu97bR7V8mXYKFTDFZl3vKPnc
tT5LAxVz7VbcHw/VQ+cc7g2x1DmaiCUosp/7UgFaEJarjoyHDcD4EXDmlY+yI9VEhRhj0HbC8kih
l7DX3T6xi4LzVtxoBfIQZyNkmtzdWFaZOByPsD0whOx06gI+6kMBBodeNFFtzEUhbSoFbzotXDje
ka5VjBx7dw35AHTk8cZRC0ILG1c5yvMJKSTdrOb8EaoAeJJKHULcGJNzVPUtKiMTfZ/LZp24OYKZ
cLQCS+ubDze0UQU8DEz0cM77zThvWn8DOZPIJ5Iz9PhD4iZkndvDhE9RtC+rSauIfeOmGkJLbcSu
lQkhKk2WwSwDNBSv2vbtR/KbZzLSWfT+/DhufKVlNBCh4Nyw5MCfkCN0PUzL/05By3yfKojiVMOx
VZrznPgg3z7T/EkTl0VzQr8TuuaTxAOXaFEYjPTX/bpHq9q2xk7RZZAug2M5eNpIj/KHwqIOgAgx
+m6UC63iusUBykgfgb87GXwyhk0/m8axjmbMzfQ7dpQN92OsPW1zQsuVjnsSQPp108iMHWo8H6iC
WY5soOocYjTFfjArpAu0eCxQ4ioBPp6HMqWn4mxy00ct4IBs75RpFKG8Q8vzjnvt5lJQBWNOS4Dz
owrRh6Og1+fHmiql9nq53Df1ssGUlPHzUKkA3It9NBM9iR4m+CXcNb1XdW6B74fd6FC6Um7L8mwE
SobUif7uPTI6m2i1uDz9PpHgeoLuyHNcWGZeYGAsDZ4Nat8uT9u/98LjBzqKW1odt8umQYEsqtTU
pz03Zzu+6e14TTd5Rn88PQL9fJnz36gvClxXdk6MllUvnhx1t28t5vEPoXz6iNqll58R8W4z+xPv
/wF1e4CiZW5kc3RyZWFtCmVuZG9iagoyMyAwIG9iagoxMjY5CmVuZG9iagoyNyAwIG9iago8PC9M
ZW5ndGggMjggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJydVu9v2zYQ/e6/4tAv
TVZb84+mbrthgBY7hYEk7RylGJDmAy2dbS4UpYhUYnfd/747kbJkNxuyyQiMUHzv7t49Hn0P/WAA
ff747zjt/Dgfw8p0+vCB/lad+86g2gD+K07h14g2vYXBEKJlx+EGMBzBePwWorRzNNMWC422NynE
0sLhM/s4mZ71rk5n373xzxkuYNgfjI6jPzqjdxCdd45oNVojWLFQCNKAzWCBkAotVpjAYguz8DKE
0ki9Aksbp5scCwtzfJD4CDfzs9OT4fDN7fHLzmBUEwqdwFWOsVzKWFiZadp+X8qCCHcAEEpl/m2e
KRlLNCAMLMuCwhTEx0zGsRBQarjCuNo+hoBeD9+08+dwswkIawu5KC1xZUvAjUWdEDhWwhha+3JU
c7wORl+OIS2NrRJ53Muf63wQqnQs/J9pV2NeghYpmlzECJScSkwXKChknPmjNNj16cs0V5iitg4H
okDQmYWiloPUNmWeZ0WVxkEYH9xzVX1wbWJ9U7GFeJ1lBuFxLeP1IbZh7hJJVq7WLa69vaCksU5h
LlVqaaVQPpRGTHamoFcppbmtWRw/Jl1uXIImJu33W3UCAcw0xMJw1gd6eJoCY5QPhBOQCCtAWkgy
kp6F2pVAi1wxbnIuXlo2iq5iCCVtnRHZVWXZHXu1zKtqWqplBVPK5dZ1lJ1RsMRMJrVYSCaiUj1X
LgpKmrdWWRG1OwRCbyFFobnipdSUd1ZaIxO318RZjq5x0jyldsu6r4NhAHSgvEknHCba5vgefr84
n4RR6PERUTkvG9ZUanIZJ82O8f6sUrSEbbLy7axmwp670yxBRYE/6haOj75IKI1dcNoRasCUOsrZ
0apvj9n1LS+QZLRuTnAwD21oA599HaJOjvzSuLEpjXxWWZAyXL6f1susiRsc/XH/FrpkeLZ9wqSe
YnfuOYhBy0wvNqkKXrTlHrXlPnUzYaexl4rsGlMztQV0Vm1FZu4yTUUhv3LNSHODGGfWadIoTC4l
ZYxrwrV2A+yCZWcDnQu9Kmm60jS6vjinKWS2dCA2rElpdo2rT32V076DXLaEbVrgDjLltySXS6Vo
rhW09lDT5GWRZzwBM622P9WluYG0N2O5zaJtIk8Q5jnJJjcQsoGbu+NV74nn1Z4a3xpJm+eb5/1H
vENOL68v6uRr5M+/7Dbe1Myzye0OcxXNZ5cf2FW9Gllh/uwHweCv3k2o+BKt1GnDqlCKetNKsg2b
oxJk9ZCGzgMNigMgtYEc6IbeAXCClqZhJFNsME88e5grK4r/CJnq5HmAWrs58mh9fpAfqlp4yOdc
5jNAAwcK+ZwZNtzzA10gXVrJv+//DnwTJol0dwIP0+ej9zisFfHdJ5oo5JL/R/G5VBoLf6Mwxcmw
OgyRuBNrYdayC8gXfnCApt9W9KvAPBWrem4+8dg4YcZp1PmNPn8Df/77BWVuZHN0cmVhbQplbmRv
YmoKMjggMCBvYmoKMTA4NAplbmRvYmoKMzIgMCBvYmoKPDwvTGVuZ3RoIDMzIDAgUi9GaWx0ZXIg
L0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicnVXbTttAEH33V4z6Uii1GyctUFRVoiQBS9yamPYh9GGx
x/EWex12FwIq/ffO+qJcHNKYtSIru3tmzsycGd9By3GhZZ7yHaTWh8EejJXVgmP6ja07y80vQPkK
Uvjm06V9cNvgR1aBc6Hdgb29ffBTa8sTGqVAbXclizQsL++i2+vbwyOvdlKuPt5Au+V2tv3fVucz
+KfWFu0+r7q6YvP5y1fbHv1EditQqV/bby23s96GAfxxHefdX3t0lAnNAm1g/wG0CkDvAYXuMs3W
Q+oM+0k2bYCZQw6flMa0KXbe92EYcs0zwZKGzOvHub3LhOkok0045bje4wQDzQyVptABBpkMN0fV
sc1Cf8mK16gUL9nKVTTASSY3lJ5L0jvhSmfyaXOtvrrsOccfKHnEg1dWK8WQL0B37BVrhw5nLb96
9fn4XiK4B+CJgIeUOAgSphRB27sV1I+5AnzUKBT5hBAjTuMAdIwQZQm1HhdjUEhpB0yInNDKMcQ+
Oh3HdQAONY2B20umzSgrGR+KxW0IMrKutIIsAibm3OnMeFoYPRVX5wx1nIXOYi0qEjDlOgYGoX6a
oDH75jFN3jgmHixZzAelAslvKCyW04JJwSvnw0t/9EeCibMIcJYhTwOlSJKIU/IcYkiUmYaCXpFR
GJ5cXJ12TZyacQGZQGMtzWTObTnEGbMqpTCNUZBzCeyB8YTdJLhIop7S3C8RU1reB5oKHQJTZc3y
CGbyWKmgSkXzQ3/RxUya65RY2Sks9M6vzmBIw8rr1sR9vWXa63rbHsGATfNqztpj6A+882OTGnse
XgNihBJFgHXoAnnCL0Or2QtrG2uz5ipbq32wqir1/iqKFbPlviIU6fJeY16w3U85yGe3jK7G/D2g
BpY4S77pW8AlafmlNbpkY4RdE2XPt77T8w/sYBVmZW5kc3RyZWFtCmVuZG9iagozMyAwIG9iago2
OTIKZW5kb2JqCjM3IDAgb2JqCjw8L0xlbmd0aCAzOCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+
CnN0cmVhbQp4nMVWy3LbNhTd6yvuZBN7xpYluanTdKVEcqoZW3YkuunU8QICL0XUJKAAoBT163sB
Eny57raUPbRI4NzXOQf+DqPhGEbuU915PrhYXcHWDEbwmX63g++DsV8A1Y3n8DGiRe9hPIEoGZT7
xjC5hKur9xDlg5OFtKgl2vOZZomF/rW4m82vz9efFi/eVNc1bmAyGl+eRn8NLn+B6GZwQk/XO+SL
2QeA1fzLw2I1nw0B5suHW7pNwdBLkQjOrFDyrQERo7T0ADXYlNnTt4PxZQCiq1qOht4iJErnzIJK
gIGxuuC20BgDP25QG+SFFvYIQpbLCH9IcBVQRNv3LCsQTKqKLIYNAk+VQQmJVrmHlyxHs2Ocoj3+
cXuzdF+fIBPGYtwgCekXL6bLKVi2yRC+nayRu3jw03D87RSUhjc7LfbM4pthO3T9tIVmYKdxx1wd
lDdwJfd4FHILK3aYMctgwwy9I3AW6neNchulsg1QmWbIzifmY9M6+ilMwbLsSPcXcWIK0sCUIRwS
41zp2K2wCpikqrZMir/D4KpSwPAUc0ahvqboYzdYvaLLPDA+A/xhz0uWAGaYEwPg9mEduZm4BW5s
k58DC5rFRKm7+2hxt5zeULx1tFosP/+vpKpKprpCGXWJth46AfdqzQtjqdYGJ7Ro+KZT+dRaxp/v
3Ti0fL182a7XlUFU8Tv7de9KJDdP6jSxTmkadGAJvdRiU9BI17/dPdzMwjTgQFXiHnWTryl42g7q
du+ZyCrSfVQ2renLZAwrTFCj5BhaYBosP/jlXdQJVza1yahu6yEVJDgU1F5fK93zHlbAEcm/oKhc
OHJ3GeYE2uk18IwZrxuu8p3y+ksqsmSZOjhRsO1W45aG1umy34imi1+1gub3J2rl7CFX2jWKTGY2
jaaewy5ShpRlrHjhaVLJvD/FVxTqsuvowHdeWAM0OkPfW54TJkcuePQbS4JeNFIb/he5G6QDiYPQ
L8hGY7qXA0BpSEFl+h1brYXn45aBGqxWdJ+626pkGGZpa4FUISOyzQaALM04E5T2Vzd8csezXvxu
4VWsmu0NEjmyIyzxLSQiZI3Ojy2BZGq7JTRDDglpkZP0OJPtlLSmo8FD7LQieeQ9agRl9Mjh+CZU
jMmHRjuPq+tP70ZXoycIkq3a0GcIcxw1zgf8Cd5ilHKFZEWMlG4m5LO39pbrtU+52vDob6qbeQ3E
wtVDBwnmG4w99wQRQ3qcajoNSJVft+T7jFmH/VIOL5zMqMQeaMawq/ZQpL3K9j7RTskVP4IAKgMM
jud9w1mWaxnbKM3Ko7LJtDnAL4cTaCXsHwybrKst0/pBk7JxrexnTFsXXjnUN5XnTifxy0Op4z5n
8HuRSdRsIzI6e87gK7JnicaUdFwfaRp5cBrHesvqUtp6NbVzt9y5e8A0VbQ03joEmakczzvau4nf
GLFnljKTCjrISYLZsPtPIcx/7IglBl67Hu/ZFuHqiRDn0eALff4BGetaRGVuZHN0cmVhbQplbmRv
YmoKMzggMCBvYmoKMTExOAplbmRvYmoKNDIgMCBvYmoKPDwvTGVuZ3RoIDQzIDAgUi9GaWx0ZXIg
L0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnictVVdb9owFH3Pr7jay+haMj7W0VXTJFpoF4mvQpimlT6Y
5EK8JjF1TGml/vhdJ4bwufZhM0IBx+f43HOP5Qco2WUo6Y95epH1sV+DaWKV4Jq+U+vBKqcLwDy8
CC5cWnQG5Qq4EyvDlaFShVrtDNzIKjixQhmjKjYkmyjYHk630bwqDi6dnTdmXOEYKqVy9cj9bVW/
gNuyCjR7XNw7jo/eW+XqctEL9EKmJkJGG4wvtOgVjgzd7AzbMJih5zTW0F+/FYujQsm2P4yOirfQ
Z4sGUwzuVrCB23c614BPqpiDd2A4QYmxh7vApWgDfF1tbssBC/l0LhGq57kfXsiShKCVz0uoG/Ak
m4aAJaAChIkIQ7Hg8RSYUpKP5woT28jJKjsH6Ddvhk6/2bAh9cvWTAgRslgDxYSYiHhFADzjTliE
G82ikW7LVAZCqCvFvPseQSlARtqoMEBPcRHDJ7tql0dHYG9UkZtO0ro91+l26i3SlFn7RnHburTW
fyEub+wBcfUYuI+x4hOOUu/EYLbsmBIw3lEmcSakQt82/csrGXzvDlsNgsA8QR8WAcb4SKTJ3AvW
NjHdpKHRj4yHbBwi0V0IFayyzWJ/LbAYYkT4BNrDgQudrpsJMzyr7fZ4q9+d0EseEgsnG6WxM8q4
dnj4vg6JiCtd86H46h8imglNYLq1luTpVOKUEVO6OA+0qZU68wulACEhElI78bPdatTd+oHsGDP+
c3JW5m/J05xc+Dg5z9tz27+6PC3VSnewKXlb2/4K3io5b9RfteupKun4MQ9jlGzMQ66eDba+OUtN
ixOeUK508GN9lJEmiJeiv+2tE3tpiO02qkD4dt33udbAwjSwy5oWFDI6RL56nqVevXuKwneZLUZE
vouPiUchw8yGUcGj1HOfkkIVPa4J5Zgq5EYB/VmeIjpg9H+zc05qrERKJCnyKZKpsZls031zVql+
xXgMIsb1/m6XniteHcTV6c5P8IaIbafXWp4oOfcUXQ++bnp2TtISXr1rs7vntJIuc9k9o2sj4CeA
Clhob11BzacZl2TcoXHbY1OEM30XNl3rhj5/ALgIbkJlbmRzdHJlYW0KZW5kb2JqCjQzIDAgb2Jq
CjgwOAplbmRvYmoKNDcgMCBvYmoKPDwvTGVuZ3RoIDQ4IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
Pj4Kc3RyZWFtCnictVbbbtNAEH33V8wbLSQml0KhQkghSSFS25TYRYiWh409dhbs3bC7aajUj2fW
l9hxEuAB1ors2HvOnLnaP6DjdqFjj+IcpM7z2SnE2unAe/rFzg+nm22A4hSk8M6nTa+g2wM/cnJc
F3p9OD19BX7qHE2EQSXQtEeKRQaaazIdjc/b3nCy86RY5ziHXqfbP/a/Of3X4F84R3T3ET6tEoGK
zXnCzUO1/fH4idPtl9uetQ+sZ7Qt5xlf3VyCt8RgMqqbfXzztt2+O+q47tO74/YtzNh6xAyDrxug
588mV+8Bf5p2Hb4DxAgVigB3oVsuEL4JvU6YiaRKa8gDq4n0Aqm4iDfA38ahiure+PN4pRBOzhoR
DxKmNaF7L0u0v+A6vw0LpsEsECKZJHJtlTBjFJ+vDGq30JQH7QxgNv54M5mNRy5kyXAtE0KKTFig
jIiJiDcEwHNuzVLcSjatzCwzOQhhYAwLvl8TlEqwkHZ35GFguBRw4vbd7t0xuFteVPkkadNrfzK9
GlyQpjxnfymuqctq/RfiGhVzQOFAAA9RGB5xVNYca+q530qlkTBHULiUymDoFpmsfPI+TG8uRnbP
SmNYpI/WeoEC78mEXgWLukmLvmc8YfMEie6dNItNAzERVj1RcWGCKeE1XN54PlxN/dJcZmVPlO2z
Fj3kSZ2FU2RVEeE05yp5+L5cyZQb6/OhQrYXMl1KS1DkrVbTcawwZsSUba5Ku/CV0vMFlQSpIJXK
RuLz5cVo4A8OVFERg/9cQ5vgN+RZTi5DjM6qkXU7Ox++6Jx2vsK25Ka2/R78reQqf3/SXk7E3cju
1LyWkVkzcmtZTlEWRUSeFfCW+PlDJmyrJ7LKskVtfWJzqSjLVEIC6vp6DXXF1N0vToQ8YEaWxQna
do7tvvz/bzu0lXcYRXL4yfOyFhoO6UKTQdR7tVYxbYg+oVR6MsWNDqNWgaERb92zcWLZ1pQ90P8g
WYW19srtwZq6jFi5IdcmRW8GTGMrIyzfPWUtFNMjb+mKK+tJzW2VWVQ5HkpUIIVhXBR1lNm11miW
0aBiIarnFZXCALmdQyEa8lSXOknjvDl6Guq0vVkxkTGurN9SaK4N9QDFnm98WCrbGTVJZFGR5RAi
JdMijQVVw6FWbj3nSWSckWwZoool5xarlFFbMFExkSXy0GSIpZI0U1Nbd/b7isrFZ98ZvW4XvAVo
gCVu4/09/rnkVumhdXvNYoTX9kth7Dsf6fgFVVzqCmVuZHN0cmVhbQplbmRvYmoKNDggMCBvYmoK
OTMzCmVuZG9iago1MiAwIG9iago8PC9MZW5ndGggNTMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+
PgpzdHJlYW0KeJytVu9vGkcQ/X5/xXyrrWBsTFInaVWJFpIg+VfgXFdK+mHZG46t7/bI7RJiKX98
3+ytgTNJ5EpdhADvzps3b9/M+ROddHt0Iq/4qcvkeHJGuUtO6C3eefIp6YUDFD90Sb+nOPSSeqeU
zpMmrkenfTo7e0lpmRyMrefasj8a1mru6fEaXw1Hb46mf4z3duJ6wzM6Pen1D9N/kv4rSs+Tg+fd
fvd5l2iqq9rY/PCn5PTnsIHjg4e/ki6Uc5Sx07WZsSO/YHLYw9dq3vziz1wbf0/GEkiWsgGwXv8B
zLFeyQHkGnsyjmrWVVmyzTgDgvL056qwXKuZKQRH2YxuWd1ZRuaQnx0ABUpX1ivJg7xcMDC8o/WC
rXAg9VmZQs0K7v6wGDBwvl5pv6pBQDmaV0VRrZ1ERW0Q9ezom+tZq7SvG+jW+hrp/gCjiR5d3lzQ
dMl6PNyJ/vW3zdEPIQFP2dPfm6hpOhlfviX+4o+2sU/IuS3uey4xOTShF6/birXUTBcm3gotoJ1f
V6S8hzlWnoOEcqih9ZpoMnp/M56Mhrh7qbUr8UwlKyvowUGA2wDI3QRPqZJbQmNJMjFLtN3Ae6Xv
rhGKxoiEPh5MWXtTWRJz9z4eUtsJW8VA7eo6HV9dDs6lBYKgTyT3mJdw/T/I7QgrX6pyWTn4E4jK
ksrzmnMFEuHERudoDinHMgr46+J8OEgHXXG9QBSMkKzSK2mVhqIRw9elcMv2NNYAzKR6XzUXAbXM
3GgViEtnGnQcms3Jb5MBFdugObuP2kSkRubjreLdWGFsW0wLXawwV0hhQAThwljZIhjb0EQixN6i
yZv72AA4WkGgDq0xXEDo2MlEqR1d3EzTLQxbJ54OpUtFFtfllkpvamvI7/ENxbZKqiyHjBQH0ESt
h8qrDSGFNBhQzjiPn7+QmZOtfKcNsk3fFi8mnb67ujkf0oxpWfOca6lvjwike0ij73dCiirPgebQ
kbRYlbCNlndVY+A2xS/rCuOxbBvv9hv6bWV77AEb7A5K0QQtC+0Z4qGutja0Nn4RtmWghyHeNM6u
rYOACg8LBVbHKIGNDPkMjtYIQGUtHTpwZtQiojQKPqEEYNbAzmheV+UurU5EkrNRZmgcTrTv4D9J
Lu3/Qiwdn3HYedULO6m6UxiqC9MhtIQquo/m8+jL0siT9zvrw7XKGf9UyJNilCbv8foX6jiCkGVu
ZHN0cmVhbQplbmRvYmoKNTMgMCBvYmoKOTAxCmVuZG9iago1NyAwIG9iago8PC9MZW5ndGggNTgg
MCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJy1Vdtu2kAQffdXjPpS0hQHQ5O0UVWJ
FpIikZCCUasmeVjsMWxj75LdJSRSP76zvmBza/vQDkIGe+fMmZkz4wdouB407Ce/BolzNDyFqXYa
cEHfqfPgeOkByC9BAh99OvQWvCb4kZP5edBswenpW/ATp9YTBpVAU+8oFhnYtN6g0z2vjz71tp7k
do4TaDa81oH/w2m9A7/v1OhuG74iuxeoNQRSaK6NBhkBE4BPBumGFGAkmBkevHS8VuHWEwEPURj3
Es1Mhm47DLmhsyzuMMMAY0zoKSy5mQGD0DzP0cK+eEriFy6An8JZoDJKiDpQfILaBoNlwcq6ppR4
HpL+KMBH+8slkObJipMBrkFhIBMKHmJIQMxAxhCCmBHa6PNg3O/YVA3jAqRAi5ZIldLbzLIklyek
YTlDQcEVsEfGYzaJcZ1EpZ5FEYiUNmoRmIUiTkxDJONYLlP2ZSMO6zvtcI3QzxK9aj/zYv4GI/Pu
Xo0vYTTHoNepeL//UK/f1hqu++r2oH4DQ7ZMm3i3chv5w97VhS1HvXTecsMIFYoAtx0L0rsdr2Nm
IqmSit9O2/QbBVJxMV25/Sb7ssx7ZoNPqTlwclaZBquXtdb6M57fhhnLVJp10pJgxpB4FwbTttrj
WaXOAIbdL+PesNsh3dv6Z/KHBJmwjqnsCHgFYPVisTVL1tVIloYlTWdahbYxLLi/JlfaDDm129oI
AzuK8MZtud7tAawLtGwiURtc+73BVbtPnLJW/SW5TV6W678gVwplD7m2gHQJ8IjTDNpFVdkUEiZb
zBTOpTIYunn/ykzyVTBBWGiay9Vg60UwqwTJu0lmvYuhP4KPklZbMSpMhBX9r5bF5Xjkw9XAL4KU
WDbajtLaQ6/pIY8JhXZnliNdkwyrIMujEmobRSbc2JT3qdf+kMlcWqS8WRUhT6cKp4yQ0sOlnvNc
qTHfUclibVJdv132O22/vUc6lS34H4WzKv4GvfTFIUOMzsr23AzPPx03Tht3sE55k9vuDP6Wctmg
P3Ev9t92ZbfUrmVklozSmhc7k0URgafSWiM/eV57jaaisrq26bCJVNRgkpGAKrVmSuzkOIXx2T2j
NTfjrwENsNjdWJndpzlXqGGP3VyzKYLn2eXc9Z0v9PkFmL6X5GVuZHN0cmVhbQplbmRvYmoKNTgg
MCBvYmoKODU5CmVuZG9iago2MiAwIG9iago8PC9MZW5ndGggNjMgMCBSL0ZpbHRlciAvRmxhdGVE
ZWNvZGU+PgpzdHJlYW0KeJytVVFP4kAQfu+vmPhyekoPxIiayyUoeNcEQWnNXU7vYWkH2JN2cXcR
TfzxN7tdKBW4+OA2pGW7M/PNfPNNH6Hq16BqLnePU+9LvwEj5VXhO/1G3qNXswfA3eIUziM6dAK1
Q4iGXm5Xg8M6NBonEKXebpBplBnqSkuyoYa3K+i12peV8CJYe+PWJQ7gsFqr70V/vfopRB1vl3bD
WEiejc4AfqMUICSkQqIP0MyAZwmPmaY9MQQ9RlD4hJLrF/d/75NXqy8c0Zoje8hQqQNQs3gMTMHF
zzAERSHwAOZjTptcAU7YQEimMaEIEGKsucjgyK/7R+TR+fLp8fDYOjdvjglR+wkz3cepkNqdI4wr
mxCLTHGllYHHMsBnjbRBvrVYgxtkMU/I1LcOWkwzv48ENHG3lZ1AY0qgMaWDMOeaMoNEv0zRoaBo
O8/pZIcgRlSkIiymA0wUKC1nsZ5JyhdNMJAWrlpJ0QDSpjaSIqYUKKHDesw0rECIJ0wpCH/0bjst
k6tmVD6R4YI0AlJKUZfB5Ako4gEzwyOwJ8aJigmWgbwp6iJxXkqEuB2KyUTMbRZFO+1XNq79ErDX
UoDlenX1/I8PZ929vYJwinHQWrH++q1Sud+t+v7n+73KHfTZ3HAIf5ZmYdQPut9NSSqF8ZoZDlFi
FuO6oQW9DPkOtEVZNguSj6iW0DgrN7FhuURINKba5+SPqe6G1rz2pFtgWks+mGm0RFhF29xI0P32
zW3Qb7eMdKhirj1TZJkxtBImx0sHhmErcpauKduGpW50c6CpNYsfrsmUJpKDdr+7quTa/R6U26oo
O0HrXUdBr9vsEKa8uO8E9xaXwfoR4By1W5CZUWhmBR9ylIvhYpVMg2WwBiqXNya+o65Iwml3gDBT
JKKlEu24LEIUU9BYL1UKcC5o+Cwam2XJSrcu5X11G0bQ7UU5MOdnGW5DWc07O50n5IWmGy7GfZr7
WvPDN5EjUq5Nzts61zyIdCqMA+teIjE3Gkkc0ZcgP1T0sMtx/av066rTakbNLe2yMqs+vFlOa9ZV
xB4YqXDMDwA1sIn/RtTt5ymXqLZp/u6ajZC+8Wa4tCPvhq5/K/tVf2VuZHN0cmVhbQplbmRvYmoK
NjMgMCBvYmoKODIzCmVuZG9iago2NyAwIG9iago8PC9MZW5ndGggNjggMCBSL0ZpbHRlciAvRmxh
dGVEZWNvZGU+PgpzdHJlYW0KeJyNVlFv2zYQftevOPRlSRsrdrzNWToMcGunFZDGqa1sQJM+0NJJ
YiOJLknXCdAfvyNFSZbjNKFhSCDvvvvuePfZ36HvD6BvPu4ZFd7xfASp8vrwgb6p990bWANwj6iA
dyEZncLgBMLEq/wGcDKE0egUwsI7CEqNskTdm0iWaNhdwWwyPe8t3gePTtw6xyWc9AfDw/CbN/wL
wgvvgHbnmKDEMsIzgC8oBQgJhZAIIgEuYkzOGgu4mZ+//6M/6n8FHyDMEApkJS/Tw9+8wbAGpEWu
OuMKMMcCSw30qslasQKBmXemKxuEsdYsurti2uQGUc6UIjSHc3uwwEhzUcLv/tAf3B6CT4cnf9ah
QhPE+sCn60UIkSg14yUQfI5MUZDS5jFnmwnTzKTWJNPh7IgqSus/yYmKOlZYxvSsgLFUayqJTWKF
EU94xCyv0qZUxo7zD/Iw2zwmNLLCGJYP1m1BbsEEGKEQS8WVNoXZcJ3ZY8PcECC2DsrsOt5vgSfA
QCIjRscSI+QUCGLUVB1F4YGXDWj0cARcw+Lj7Ppi4rBW0mT9C/oNcQpA2DEkUhTbxI4ckrGtoCEX
qbXoxAYliGm2LohUZL5CEl9tDVdSLKnOW1dobnVENf+XoiYVJRdnXO3VPF0EUx6TLt5TMMtXCwPd
ucugjGz5/XEcc+PNcnv5dTPamjOI9cPKNser+yJ/5fq5AXY06r6guqhI8iUqk66Fp96iqiU8eaAB
aHZVt0F307CtSj2rtFxHmloqNvOQiDwXG+vazuWb3t71ppPrzy5+vX46+r/AqLynl9ef6tZsvf/+
p9e7Pej7/uvbw95NMz1fG7dFOA8uP5hq9VrnR26NbDxy3CYdTF7Ati3LXmHjqZnO07M91X5KLzJW
aVJVe3OFJEF0w2uN9iKMeZUb6eJ8+vk6mE8n1CWmYl3xa9SuAdjWu11pfF7+nlW9tuxEbXYVBrPL
8QVxqor7QnK7vF6ozc+S617tEwTHWwop3UxHGUZ3pFxY7FKjGV8iqd9KSI2x766xTcjpEdmsFQ3U
JsMSjT6qdZS1vyVbAY33D8ZzRnJEcO8ECULd5Ebg2s5t5t/8CrRYl7OwE25Pic3ZER3ynFBIcao8
6VnsYNU4fN9FiYJrk/NTXWxeRLESBsDAb0h901RiysjfmlTdbP5BkHPI7hg1fsaPADWw3N8ZpOn9
ikvSuCfWzRVLEQZDM8/T0PtMn/8BUHOdS2VuZHN0cmVhbQplbmRvYmoKNjggMCBvYmoKOTE5CmVu
ZG9iago3MiAwIG9iago8PC9MZW5ndGggNzMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJl
YW0KeJy1Vdtu20YQfedXDPISu7FoXZLacYsCSiQnBHyLRCNF7TysuENpG3JX2V3FNpCP7+xyRVKy
lfqhpSCQIGfOnDlz2W/QjXvQdb9wz8rocHIEcxN14QP959G3qOcNINyyEt6lZHQMvT6keVT59aA/
gKOjY0jLaC+RFrVE2xlpllvYvpLL0fi0M32fPPoSrlOcQb/bG+ynf0eDt5CeRXv0dsLuRsyyE4C/
UCtQGkqlMQb48/xsNEyH9JQuEEpkUsg5qBzsQhjAAkuUFujRLnD/ZdQbrBHpMqxEYO4Ts5ULwtBa
ln29YtZlAVnBjIHbvSlmVigJr+NB3Lvdh5ig+r/W5DBHjTLDLXoOUyiO+UltATeT0/dvukfdL7BJ
eZvb0xk8lzKhBZx/4566IFWa59fTFDIlLRMSCL5AZiygoBjaxQo1ACZ5k/IG70DWUGqftSA65tCg
5HSvwFGaFcniE1liJnKRMc9N+rQkD7y/k4d7LTihkRVymD14tym5JSNghEJMjTDWiXNHHP1nx94R
ILoByr0NxH8DkQMDjYwYHWrMUFAg4GhJIUPhQcgaNHs4AGFh+vHy+mwUsJbaZf0T+jVxCkDYHHKt
yjaxg4DkbCtoKNTcW2zEBqOI6WJVEqnM/ZUmvtYbLrWakc6tMrrKHseuD0vkwlMKcYbtd2vFnDou
W7ynWJ6uVR45kZlXPB5yLpwHK5xuT5W4kpwBtw9L3+cv7sviRWjpBnjdECSIybSY4bozRQhF1Wj4
CZkrXa6fs2LF3SwLaaxe+R42m72b+LEgYVRZujbj1Vis0whtHXReN7aS2JrPjdyqgXtM/m6BEl2r
sO9MFIzU3+SxpbKPSkgVbWp47iY2V0Wh7nwGzVp71XnyerVB68cGfH39CFL+BKPyHl9cn68Hp/H+
/Y9O53avG8e/3O53burh/lK7TdNJcvHB6dFpnB+51Yut5Wi1q1uLNPk+g20jy9MHg5i75fH25LHa
uzbaglVbs9LekaIlSW24sugL4cyr3GhzT8afrpPJeERN7BTbcaLUAO2NvL28/4MzpZGdqF1epcnl
xfCMOFVVeSa5/+/Aa5V2B79ha33744O1Z32bWXv0aRvNkIyXSlvkcahok1sYaLJZGeTNUVePqVll
i3Zw511PLsA7Ratr12H2pu9Zpewro+5ZiANAC6yIt5pxfL8UGs2uXr25YnOE3ms3FOM0+kS/fwAN
XMezZW5kc3RyZWFtCmVuZG9iago3MyAwIG9iago5MTIKZW5kb2JqCjc3IDAgb2JqCjw8L0xlbmd0
aCA3OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nI1WXXPbNhB816+4t9oztmzZ
dZymT65lJ57xR2rJ006TPMDgkUJNEgwAWnF+ffdAUKJU94MaDSXhsNi73TvqKx2OJ3Qor3TX1ejg
/pQKPzqk93gXo6+jSQygdNMV/TJH0FuaHNE8H3X7JnR0TKenb2lejXau6sCu5rA/dSoPtH1d3U0v
Lvdn51d/W0nXJT/S0eHkeHf+5+j4J5pfj3a6BS654jp4unmYzen2bk6PTK3njJYLriksjCcVgjOP
bWDCF1nbw6IpefeH0eR4iGXCgh3ZHNu46hB7NJO/gmUrEwJnYwAdvemB5hKmS+W9hGhbNVYABHVp
SRWF40JhfwxhL5tl271aTlVQ74j+YGfJOqqs4zHR7zfX07P52ViQmSpWtamLjiTwU/5yFEhvZ+RV
xaRkSYWUF52FoPTTRyQCRRLRzzsz1sHYmn4cH48nn3dpM6d7ztlxrXmLnmAam3H+bhVBn+4vz08O
Tw+/0CblbW6vZ/B/Kaeq4fov7gM9oqLa1kGZGkpSycqHgexJA1J1tk55g3dvN6T2mzOg4w881xnu
HTjXvkVZYiINa5MbrSK3OqZVZ4n3M3bIzyYDGqJgkMeXuG2GbVdTUkABU298kOIswTEuC/vod5sn
KPk1Ef9ZbKrIsQKjA8eaDQ6ijAMqBO/ivHoFql/2yASafbh7uJ4mrMZJ1v9Cf0UcBwA7o9zZakhs
LyFJbAdNpS1ixMbZ5NELtGgrkNLytg58QwxsnH1EnQcynqDeN4BUwTqUydJV1STb5KwCSt4bQgxn
+sWOe2+0LI6evqu1ahROkVVRUHqqk2ctdldAWRFW6ENJMreuij/ZV8pUSnYYFnVqRkExtQlGlXR1
dntGIZ6ZsdeYIl3k2r2TKLNtYUnnrNu2MdNK0VeSeFalQX2EWgrLIuXM6jZadiO12F3iMa5AgyMT
DzOmhQIN4qMYxpHXmIZwFzS4tSGFrPNbkRIZS2ufqG1iacQzvlGaUz2GFUD12tg2Yd0TS8HdqGc3
ESLFbDsdym1Z2qUfVOkNGKKaLRrzhc5tTMh1QCt3iA8SRH8WozNIZMXxuKGHte38QI1ywei2VC5N
kNh16zL6/jR4O7YyoBrYt3FGRnxE+6YXqi7QPdpZQXAFxuH3jhYIn/XcKoyb8gWHZjKCHKMXfe/h
2KmZBdPa4oORVinl1OBs1qLCPZHec963LOgf7JKhTdyP1ItWOYU+RTGjijE/oCaSkrQIrzD2elp9
92wafWnKkhbqGRZkF8cpWgMfY0qX1nV7MIg8yA8GVRS9fJGDYA6vCu4rLwMjgJxvrAsyAoLVtuwe
voPROsAaVjpjPFZjH0iLdlMVDRFkxiHfwsWPa6+pFgiI0SJebjdHHo56Ns7WYpLNJrwbiteVcKVv
lK313bgY2kza7OH+/cUUrt9wTwZpStuQbaJNsREJac5knHXgKwyh1xk+GlMKu34CpNJvdMJEHr59
OfdnfWbnSSWEyj8zhM7Vk1oovzB7xOBajrf+eV18a4zw+Yfr00fRcHLyBYgX89GveP0Fl4BG+WVu
ZHN0cmVhbQplbmRvYmoKNzggMCBvYmoKMTE1NwplbmRvYmoKODIgMCBvYmoKPDwvTGVuZ3RoIDgz
IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCniczVXbbttGEH3XVwzyEhuwFElubYdv
qS+FgMRNJRkJ4OhhtRxS25C79O4ytvL1PUNS1zRAXwqUgsDFXs6cOXN2+ETDwYiG8uveuuy9mV5S
HnpD+h3/vPfUGzUbqHvpkn6bY9MVjcY0z3rtuRGNz+ny8ormZe9kYiN7y7F/41UW6fiZ/HFze9ef
XU9+WOmeO17SeDg6P53/1Tt/S/P3vRPMzldMtU3ZF2tjcyo5BJXLKHO+VJGUTanyLjrtCqoDpxQd
8YteKZvz6eve6HyDZGyIymoO5DKKgG0Y0YeH2VwQvpmUSVUYVd6oyJTXyivk1BwAkmBoZzPss9Go
wsT1GUAj574ZChNVAxirGjODjnxgCag6BOGQKp+a76AaWNdyeJeBCcRWu9qrnNMOYcqq6EdTgrFI
3O+QIPWz81/phjO2CPLlZDq5+XK6w3qc3l1fDH/5ddFQMzGQCsFpSQ4qIbdQOR87tKWxqcjaHbpY
bDUJtV5tmQ6wfXyxXxyNaaNVsUsGImk4AeE8Q2gUCaKAYIi+1rH2iG5sWz7j7EGNSrWmJVOmimAy
g43Oy+F1t6AdRNDO+7qKlCIaCDeJmAitJlYiqtBl9LxiiS/LpQkBoXYUAYuxZ70WxZ9qDkJFLQs+
k3gdAtxQIDVZakpIqclNlFRNbpVkIsq+AVhrS5ba+XXVHrDESq86KM+iNT2bokACtdRR6UhLF1ed
HQNvhUMun4D1UrGOrYB7SJ23JXXnc2XN95ZgA50ygEtjuTG4ZU5bX5Ysh0woz+TedEhbCzSWQSzA
7NX3UiR9d/+Orh0Exg1s4mzUna8gXOp0XcLvYvJAD9P7ILcv5QBToIyfP7wnq6BNpeTaCRGZCnrF
qL06qPwjVtqFj8rH0eJoYrxo7p6T5HIJoiBpbmCp9S65jtomvtis8fP5xdXVgg6tO21Pt9p5biwg
2ux1hj2/6vWS/cY9R11l62SUJuImymibdXIQFM/DdJJQ7W1iOGZJhRZThuSlLBIbEuNSzvpBm/5o
MOyS2aMKnVGKCN8kmMvYU+tw13CW1uN8eE0qTT3sCMFDW9MDvni69rcp3uCYIoRP6N7ZzTX4b6Xa
OeLfa9Xt/z/p9WMASWzWEBUfNiGritFlX/4JcXunSi4dmiqjS4dmV+aKwj2L7beOF/Gbq4lQpbLo
PMku/Xt4bxNhcyKhV22hZrtCXUuhaLZpiZOftGQ8MzQitOO2E4ZXWH47apbn6qtaqbAyZ8T4FBeD
o0/67UtloO3PvviPH6Vnji4WQLyd9/7E72/uBrShZW5kc3RyZWFtCmVuZG9iago4MyAwIG9iago5
NjUKZW5kb2JqCjg3IDAgb2JqCjw8L0xlbmd0aCA4OCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+
CnN0cmVhbQp4nI1WXXfaRhB951fMW+xzbGygiR2/EYxzaIzjAmnaE+dhkQZpi7Qrr1YQ/n3vSOKb
pBXHSGJ3Zu7cuTPrV7putuhaPvU9SBtXoxuK8sY1fcRf1HhttMoNVN+ClD5MsOmWWm2azBqVXYva
Hbq5uaVJ2jgbGM/OsL+8d2rm6fAafL7vP1yOe4Ojlfp64Cm1r1ud88k/jc57mjw2zqqFJ5VynqmA
KWSvdJLfUZccRzr3bkVs5HtmHSkae1cEvnAcUm81ZXf+ptHq7Hgac1A47Vc0MDBIldfW0DjjQM90
UL29nAnEfPe3l3MKrMkRLofD2pWd3eGl/W7H+y5UgfhlNKBvo4de5/3tu+/kY+VJ57gz/TV8JLPJ
Sp6oyDk8hItruioNqmxZEjuC1zyBYz8nQSWAwJc2kSQDGo08im84SxIOL23hKyh2dgKI7DwKTdpQ
XKTKXDpWoZomLIVITyEa8QzwDdIFLQImQUIIRdYgoqPUOolcxsGOfIe5mbPpCUTLWAfxITv78AJl
aAq3U8mXwybRJOZtDXH91HT4ZTwRW0lMJytSJqSsmCY6kJcFZCjp7vkSnFWZkcApDrpZBvuSpl6i
8pzz/yCi/8OzCU8Ko3awRg38qAX0XYL/rdmpXEBvoQ2KFE3y6+SPS1sSYA2ynVbqpKX2Jd97PtYQ
N4AAY1uTdX8esbHbgCVlaQEWEClzdqHFn7cEhzoy6GvDS1qopICKkQOpqV3wISdrGvXW81HUB81J
mItrx4F14SHYu20DXx230NVhyD/Z5Vi8Oq7riXy11yrZ0iJNCGqgAIPCbyntJomtYz5beAWm/o+M
nUcHLTR4kL54226jL0SSeygP8Y34tdBS3a3NPjAh856FZOWxrQ4E0TCeAl9VQWZfkfhN+SnVSPTl
bKiMig60OTABimc8Peoo9kuWb7gNYmUixhxdWjeXuRM5W2Sidu0h4SIIOM/lbYakVjUZ+Dmmrx+B
RSYvAnIzal7QQiviFP0n2ATOns83OcmavIsgXs6btbf/lapjTEhe8OlpV3uq23xHqjLooSQIil3J
WMzBvNpSToz1vAAunD3leD2rR+p+z0lFF+z0rJr6kCh06g3I2RmNaOTuGotOM+u8AuEOspVDahOk
3H4yYyBklNRx2Xk7YHbmwbGkScFAZUg6cxoeyyN336p29asT6lbQB3NjlzhyIplLtdFXKWSRhCjb
nMvm3+xiGjqY3SuwTR8SLFQ16A97FzgFLKH8YbLaE+KmNhEbhjBEZZlwdUFcYlMJJput2n/Qfdr5
h0LneVF1cI1LJbk9AAfizJx+h/0HNUfRSzzDwWTUv6BnVSTUw9mEcsz1+vQSX0+D8UTWjc3pk0oz
NNAc9SiNe4Nx7/MFjexUqjRUzkNRu24/KR8nzOvKDy2q4FDpLRWPKlIhB/QcQwNZxtXSU3cCv+O4
iFnT3ypVEfpqA+ttu2RsouYqVnmsQY9Hwk3avyAeDJKcfnJ9e8YkoNbNd3jsTxp/4PMvgfswe2Vu
ZHN0cmVhbQplbmRvYmoKODggMCBvYmoKMTEzMAplbmRvYmoKOTIgMCBvYmoKPDwvTGVuZ3RoIDkz
IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnicpVZtb9s2EP6uX3FTP6wFItuygSU1
phVu7AwGsnSLNWzDMAw0dZK4SKRCUrHy73eU5FqOkzVYadiCeXfP8/BeaN/DZBTCxL36Jy+98e05
ZMabwI/0zrx7L2wdoH/wEj7G5HQB4RTi1OviQpjO4Pz8AuLSe7uWFrVEGyw1Sy08XetPy9VVsLlc
n1j6dYVbmE7C2bv4H2/2HuJr7y3t3qwv4zNYSJsr+Qi3tb1TO3MnINWqhD8Ykwxi5LlUhcoez+Cj
FkxCrFlZYtE6vfvWC2d7tMvVbTy+QbtZnAGTCSzZg0jgN1aQ9FJo7GBv1psYUqXB5ig0GCE5aiQg
B5EIw2tjhJItQoqYbBm/A/puc2EgUbwuUdoR+U+/a4nfjwAWVYUyEQ2s5/D7T9ew4TmWDJaYCims
Q3OEq8aidNg9WZzj0DtBw7XYCpk5aYAFOibidCiYgJDt/hDlcPYBlUHePkluJh5QQk7nI5ErxnNQ
aQfesLIq0DjQTe8fTntdJld1kcAW4QG1SAVxWwUPrBAJswgsY0Ia2yXEdNq3j8Bqq0qyJz2KVaow
Lk+Hcn//oSkLB+rkR344mviAkquEzhz5v8ZXwYX/4YdDal1IY5J5T2KZztDesBJNxThGfq3lXKBN
5xWjnjBzQp9LMxeKUhYYLgLHcJQmIBfyINDIz62t5uPxbrcb7WYjpbPxdDIJx1SRriB+f5A+pkX9
AmfP9zTKaXm92ja6r/6V0iWVltWFjfz7mkrgyuEDs5ZapbZ45FDLg8szaRRlpbQF+coEniavq8O1
4sy2BWz9/u52R8Tgj5+wfhME/43wnIDOZyCiRXXhQXCKH33lOtIXRW4gl4t48dI99qXVAnZQX7tO
TutqyJWb2yZ+rLAtZOT3gtuCDzJ95H6p6PqWdp/Hz2aNhvqoG/8tM9iXdP75jnE8/jBsP5F4X9Pk
4rGpNzK6ywdN9uYNbfhQacXRmF6KifyCNT6UQn7ivNb0/dD8+1WyZm+s5VbVMsHk0A094/hlPZ2a
/aj0+UqsOxO4z/1x262g269dFjTB0Q8GDZrDS0WDdF9Qb56QP0eAjQ2OSFqB5COzHl5VLuPsdXAl
MtmGnoC9Jpp+d+hSFsn/DB80yHHKBoYucUdoXVEGPgdjZ3q+L49srvWcwf0BoZ6O2R3LmcnFGaAF
VoyeDN6qqahi5qW5/PNnliGEF38R4ir2fqHXv9MoqQ9lbmRzdHJlYW0KZW5kb2JqCjkzIDAgb2Jq
CjkxMAplbmRvYmoKOTcgMCBvYmoKPDwvTGVuZ3RoIDk4IDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
Pj4Kc3RyZWFtCnic5VRhb5swEP3uX3Hjy1qpNEC0po1GpKykU6ROzRI0Tar6wXGOxCsYYoxG//1c
AtMgoHWrUlXbWciCs9+9dzx7C9apDdbjKGcWkd58AOuUWPBRP2uyJXaxAMqJRfDB14vOwXbAD8hu
nw1OHwaDc/AjcjQVCqVAZXqSBgqaMb3xJlfm4nK6lynjCpfgWHb/2P9G+hfgX5Mj/fX9G9N0nxnH
b4ndrwBdFxYsllys4TKkadpFpzsKwB3Uc8M0RxrLOavIab15uhpiiBEKBYJG6BolXWNU0/FzMYuj
JMTcf0hwVBL7JZviNkPBGqnOOrhAZYDSWK7B4xUGZsr48Ouna2/sj40GBkRc3DCWydQ1LAMimldv
mVjGmVjhyug1OPW6SRWUqFKSLzOFFakE2dSrKBWbVdENyFL9QWokLlvqtGFhrsxOvLq2AjxOFI8F
DevgOwmtXd+lyq7W/+whfDxWirL7mZapD96fu/mlfVyjewA3s03M91OtVOb0u0cVfbrT/8bre7Ul
BmWt4RwDlI9KjDpwS90nVSpN2dqBDg6F3llIVRDL6Dc0/pOj3QFeM+6/cnl8yUKBki55yNXD6788
anQPenm8cwpcn97TDU03/ARQAQ1PGw2Y5Il2Z2fPbmd0jWBf3GnEiU8+6/ED9dpqGmVuZHN0cmVh
bQplbmRvYmoKOTggMCBvYmoKNDk1CmVuZG9iagoxMDIgMCBvYmoKPDwvTGVuZ3RoIDEwMyAwIFIv
RmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nO1W32+bMBB+919x42WtNBpItKaLQqWupFOk
Tu0StE2a9uA4R+IVDDFGpf/9zK9NBNKlTZ+mngWWOd93n+3zJzZgndhg5a3qWUh6syGsEmLBJ/2s
yIbYxQSoOhbCR09POgO7D55Pyjgb+gMYDs/AC8nRVCiUApXpSuor2LbpjTu5MueX05ansitcQN+y
B8feLzL4AN41OWr4x1myHGGAIQoFgoboGDN671JFDVAPsR7yaIm+mTA++v752r3wLozjt8QetKEg
5OKGsVQmjmEZENKsHqViEaViiUujd66DH2Eg0a8yjmboo0TB0GgCtwD2zDTu5YnYOuIMW75uDsWq
bwOq/EiG/6CxJ4lHEs1ZJLlYvUCecqkJbtJ8/7Z8uYsqJfkiVVgd+TxGNnXrEy+CVcklTfQHqZG4
7MjThYWZMnfiNVdTgEex4pGgwV7gX9NAoKQLHnD1cFiGqh6iMA4w8zTMX2fpqo4p/9w/rct9/MY0
nUOtcYEcB74hvROYJHAZUP1+shWIJdahZprN9XYqRM3XOG9JwXjnpv7xdtdlHdp5P5+tU68K9WQS
rwp1kELVd+O/Eae6up4nTi8uTafvC24evaNrmqz5O0AFNDjZyjvJYl0PO+n+uKUr1D9GPzXixCNf
dPsNoK6OPmVuZHN0cmVhbQplbmRvYmoKMTAzIDAgb2JqCjQ5MQplbmRvYmoKMTA3IDAgb2JqCjw8
L0xlbmd0aCAxMDggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJztU1Fv0zAQfvev
OPxCJ5E1SQUdVYM0lg5VGtroLISEeHDTS2tInNR2IPx7nDSBtU3FWCWEJs6KrPjO33d3vm8N7qkH
brWaPUpJfzaEpSYuvLHfkqyJVwdAs0UpvGY26Aw8H1hMNvc88AcwHJ4BS0lvKg0qicYJFY8N7Nr0
OpxcOrcX0z1PY5c4B9/1BifsMxm8BHZFevX5uNSLESaYojQgeYoBvUm4iTOV0lcnT4k3+BXbREdZ
midYsu85VhG9nxy1V+O6QBntuNqrq0zsuzqzmPFvITecgrE8ARXZAmNHR2L04e1VeM7O6R4IpEJe
R1GhdEBdCikv279CzrNCLnBB+7/hVhg3XKMZxqiqSug2cAfvvZjG/UMd2Hi6G1dnx41RYl4YbHpz
m2M0DdvW1JdtgFxSKLQ9UBZJqP0cOrGwNM5BvO0SavAsNyKTPLkXeDtKx4E3nesau42reb3q2H/R
zuv4ieMER9qWAIIAJl8tzQzzTBm4SLjW8EdWA26gjjTH2S62U0J3sv3HtfwgWf5XWPvGj0Ve71GJ
WES8yvIB+vrL8rqb7aPV13O/ronxL3zF9Uo8AzTAk9Od1k/K3Orh4HN9vOFLBN/7ZBEnjLyz6wfl
2GAyZW5kc3RyZWFtCmVuZG9iagoxMDggMCBvYmoKNDcxCmVuZG9iagoxMTIgMCBvYmoKPDwvTGVu
Z3RoIDExMyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nOVV3W+bMBB/56+48dJO
GmlItLVDyaosSSekZh8pmyZVfXDgCF7BUOy09L/fGZw0JI1UqQ97mBFY+O5+v/N92HfQ7bjQ1Y+Z
w8w6mZ/CUlpd+ELv0rqz3FoBzBRm8DkgpTNwexDEVmPnQq8Pp6dnEGTWsS8UlgKVMylZrGB3+N8m
0wvnauzvScy4wAX0um7/bfDH6n+E4NI63pIOTioZeWGS8xA/vT2y3H5bo5FLvFuhaDS2ZFrElCr5
YqUQBMtwaF8VGPoTG9RjQX+1MSmIpQ0rSQslIfESI/vkBVhYKecgXsu8Ac8LxXPB0heB/8KSxzxk
2uR1BCaGeVakWAUE8yRsRJhihkLp5d6HdXwHbxxn+MrRSthwCHPiiXi9JRinTMpDRfH8qAEbqFcO
x2lv1uTABMJkYMtbe7/2BgeDupE+X5Zr001Nb4ued4Q9TJhi6xrgeYSxI0Pu/Z5dTkbBaLee9mBK
jI2ZN8cYS+3UvtFur/0PXbaV43/SZE1gwwQzpiXve7XE7XYARkWBIuIV+L4HIwGUbIjzEsYJhrfk
G/iaS2PW7h9JmAU+hLkgpYyrxxZRkHAJEsO69Yoyv+cRSmACsGIaZoMertH5DnqrAdpMHY3fQISs
LDkhz2Z07EOGikVUucCFJELNV98HJjRRHq40A9l/zSklKmGKPrhlJ2GJAkumMILFo/5pkK/r6cYA
PXCVwNQfj+ZwXU83EPMUJQG3gyQhj4lBx4IqanO+QraSymAtkDZRsAXFhHQLVkodDe3VdqhoMUSz
yyc0cpJJrbveoL4STWJahB1SeLrsBudVlsI9ElUuhrbb6dpAjZZHxDy0fwYXzpl93j6BBs29OjER
bBmTdcq0JYpN/RKBkEN7VQqPo4o92hfLpEfLnpBec6Jo3pZ+s/4yK1O5AbtlCZMJfweogKUdaI9p
VVDjHzz3r7+zJUKvpxM7Dawf9PwFBqBq92VuZHN0cmVhbQplbmRvYmoKMTEzIDAgb2JqCjcyNQpl
bmRvYmoKMTE3IDAgb2JqCjw8L0xlbmd0aCAxMTggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+Pgpz
dHJlYW0KeJydVm1v2zYQ/u5fQfjLWmyx+CqRhmsgW7oiQLN1jT8MGIbhSB4TtZasSkqT9tfvpKSp
k9p1NhmGJPK5h3fH5476wPhMMD787u6hmmRvC3bRTTh7Rf+LyYeJGAHs7hYq9vOKQJYJyVZpcmsn
mFSsKCxbVZNnp3WPbY390UkLqWePr9PfT17+enT+y+k3M3fXr+iZ5EI9X72bKMdWryfPhuGbal13
83ITMR11oXwxvWrreYl9mjfQQtXNCTDfRhyJGZ8+/2Ei1COOm46sL/u+mWfZ9fX17FrNNu1FJjkX
2Z9nr8/DJVZwVNZdD3XA6ZI4Rmu2OK1DGbHuWXPVNpsOX0xbbDZtX9YXW7At4OkJq6EiXOjKtp/h
DVTNGmdhU02Xwjrt1CL7in1A8XZkXpUVLodsHHF1JNRKqrlwc6l/5HzO+SLbQm0bn2AX2rLpy029
vHf61ldW1ozWb6D+xG5uFtk2dJviuOuw6yoy3B4eYiPb0I8caxzMXkwTlGuMU9Z/aihWiFVZT1n2
gC7bzbc4w/5yEx8tse3Tcc1G98tUYss2iQH7eLWusQVfrsv+Eys7hpXHGDE+ZNkX2hBcjOUwDOsT
6IHFW8dJHtOHQILe62l+3PcQ3r+BftA3O28wnJ7cC4lsswp7iMR3fgktSWJ208Vv+B4wvoXrQ+uP
FhWsr6FFyhWM+FHHB5fewfQ/S2A3U1fOuxH4ehNgFMJO3AE3WSLtzJ/s/0dsu1FzYkbe0jUledDb
+LgreZS+O7kvf8uOF9mXl91QuCI5tsuzM2pS7BUOMhsiY+ejkBbZ3fzedUZ9r7Dr2S3FR3JzjJBd
3JJhZFcdRTi8j5DdVNkXrt3TPRU87U3V3PcGqVbCzIWcGz4rZM6H5vAVtZtl499h6LvdszQ/+j1k
Nw+YJy1MtLowRhuPxoMQOkluPU9pT+JHkiqa5SH7RTag9nN0lyCWEZQDhWgw99rzqKQxPmFyJufU
SzmkaHnB3SIb4d9lkyZfovI8aC2dTUEEoR0kn3SwzuXJO6llAagF6lw775Tey/flCqCdcU74whrp
rTGjI8NK33XFCLkMySoUyhSIyVsfkzBaWsNjnlNMvIi55Ki54d4UlMXDrliVNDgpoqLUu4C6iDwK
FWgHTJJDyq0SNkpb0JLhIJ9MuaIcCB91oUUBVoBRVlGGkpMFbQyOsQ6hfCfW8jPSoacJOjztBw6y
G07NJZYB2n+oEmafy2aR3Y/vNz07PXu5ol66hKZZl7ddKRuN72f2iX2kP1wKWkdrcyETggWbVB7R
ShSysOA9lwdL4ZD9k0pBKWesoa21gnazUFZGxKHqZSqc9bmWSWih+VNLQRYGuBTeJ7K1Do2mjaaa
cqmI3kWR5yqF3BkM5LeEw3oJmvQB4FNuRIo8/YdSCJabaBJ4MiwEaPDKSHDBKIW5SV5G4y1Vl7BJ
oznoSk7twlLbkVJ5S53DmuA15R0SUDeSlLTonFQuOFS54Qf5TMiH5hMc8FxEShVVp1VUCgWdX0rl
4J9aCrk9WAmhDUouRWG4cMIpScfCOEIWRo5ftSt4D5fQXZY/MewZrGePKF7eNGWL3b5o/noDF0gf
738T48vV5A/6/Qu9yfwJZW5kc3RyZWFtCmVuZG9iagoxMTggMCBvYmoKMTIwNgplbmRvYmoKMTIy
IDAgb2JqCjw8L0xlbmd0aCAxMjMgMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJyt
VWtvmzAU/c6vsPiyVloAE0ho5UR9pVukretSpH2opsnAJXELODXuI/v1swNt84Cm0waKIPa5x+de
n2vukGNh5Oi7fsa5YU/6aFoaDvqkflPjzsBLAKofcY5OQgUKEHZRmBpVHEZuF/X7AQpzY29cSBAF
yM6ZoKlEm9f429novHN1Ot6aqa9ziJDr4O5+eGN0D1D4xdhrxJGUZVDQHIbAYiqsmOfEfhnb/2Dg
7juCfzA5Y8W4KCXNMhCvXIqgJdRui20JqQKaZ4nNoxuIZdkyLSCjkvGinLF5C2YDheRiDgMzFkAl
JCcLE7FkYGKzLViFl/xexC0CX1ZIhzqL6yPN1ouhl3rYTwKv7/ueH4EfUYy91HWCyElT8+dbXLYm
e6O8u+QQScUU5F/o9bwkCHrYTYEGNEi7vQQCF7DbD2gUOe4/6t0lh0iWg/JIPh9qX3ecbsfthtg/
xO6h71h9z3McR9G8oFp9tLrPbX7a6Rhi5zR7pAK+gqRnVNJtELEZTyDtlDE7nNDHJtAq5FhKGt9e
Uqkbfx1I7OMkYVoPzTZpiK0UzHiyNnbKC0UmkeDZs4u5MGtTczGlBfu9zG/D0M+BF7r5R0+qjBno
NkanV+NJSOzV6fXACUxZKcXiMy2SDJCo/w5MKphaBSquzvJ4WcduEI1yyrJhXC10FJdMSAtelRC7
AqxVoJa1Njh6gEJu15ycZ/xxaxuuFqWEHMWq2adcq666p6HdyYXasEZDqC0SUJYrJGz+4HWoGjaH
+MC1HMu1XO3RGtnIcsrv9clfbxXoJMyh39c5LieabNYkidhVTrtTrRrvf6RaaJrnTHHPdoM3cm2W
rQWCeGAxIDb/NRdc8phn6qxsPHnJJRdyGKiSLl8a1qjJ3lcdYm+bg4ye5urLsmwWpDymHgMzynh8
25nxUprIfgeeyxmIDagy8qpDfXf5mQ3pLZ1Rdep8RCARzayNjBU7U/VELdf1JZ0Ccj19Eo9C47u6
/wAH8xO3ZW5kc3RyZWFtCmVuZG9iagoxMjMgMCBvYmoKNzUwCmVuZG9iagoxMjcgMCBvYmoKPDwv
TGVuZ3RoIDEyOCAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJVV23LTMBB991cs
faEd4mt6i6d0CI4LnumNxpQHhgfV2SSiseVKci9/z8p2EyeFAvJEtrS7Z3fPrpQ78BwfPPO07yy3
3KsDmCnLg0/0m1l3ll8rQPvKcviYktIh+AGkU6ux8yHow8HBIaS5tZ0UGmWB2h5JNtWwOZKLUXxi
j6PkhaQdJ3gDgef3d9KfVn8A6am13UqOPnOlhXw63nlr+f2uhGRvbBsiUWiWaXhgCkqJ91xUavEE
OZsgPHA9Bz1HUKKSGQJF+CDkLYiHAiXYtgHtwLWuEo05ECQXxfutrIG3GwRbcY1b62ZkOGIaU57j
ceB5vu0NbH839Q5DfxB6/jvPCz3vyF3qvDBGlUleGnfH50LzKc+YWYDCQoMWG/oAFJLSXFdYZE92
G98HfxA4nhM4FMGmA7frYT1jt5NyV7QUrDaP3KTI+IRiet6jnbquI5FVebu/F9Ql8n0HYFiWWEz4
IyRJEkLE6HtCJMC4xGyZpYKpkHWNkuH5EFJ2s0DCCfafS53OuYJJ3VYTnPICJ01FtawyXUkEMV2Z
a2MOvIAx1vWDXepyZ6110rmoZk1X5KxgMzShP4O09gqqkpivMXskoA3WJtPmXkpxT2QoyJZpEYzk
qChxqiJBzZmGi+vhKZAGRNcxMApW4oyIRYmTFkhLatScyVvVaxSHl3HUgyiKaYrNdGmmb/U0Hvfg
bGjkRvUiSk4N6G+QKJ2U0jlL0quYTogshazZdtaoNUVqHNLnPom6R++c5ahKlmG4aqW51mXouhmj
Cjo51xIdIWeuuFEo7w11auOUrpW6hqRGEHlOi6Gmvr2FS6bN1QFxQT3UBGmSe9H03REtmFJL2KXq
NUpF67Cr2uTVyK9wSsQXdA98vUrCVzNa2lAPL8iP6YraK6qwjbwNfNXzpB3UhEYx7Dnef9CZ4cr1
vxNIF9+Uz6qWsw5/rxLSRPZ3QroxvU4HeenWYsVGv2FjPKYqGKfmv4IkKbtlc6bmvAeogS2cjerG
jyWXdLL+ML5f0pmFYO8HIcap9YWeXwa02z1lbmRzdHJlYW0KZW5kb2JqCjEyOCAwIG9iago3ODAK
ZW5kb2JqCjEzMiAwIG9iago8PC9MZW5ndGggMTMzIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4K
c3RyZWFtCnic3VRdb5swFH3nV1xpD22lhs8R2rx1CZ2QqiwD1pdpD453IWwYXNtU67+fIYQkXZek
0/YyW4Dgnns5PufaD2CbDtjt7J+UGVYcQC4NG97rKzceDKcDQP+gDN6lGnQFjgtpZqzzHHA9CIIr
SJlxHlUKRYVqNBMkU/B8RB9m4e0omUa/RPpxi0twbce7SL8Z3jWkd8Z5931OGEpOKE622Ll1c3Fm
ON4WlXCkRVZQooq66nImMK0Z0y/TusqKvBHrUEJrUVQ5JE9SIdNV1vn3KKQOT3YZOaY9xGPMUGBF
ET7FUY9aKcUnlkWloGZVSGXm9aPFm2XZ05DWolnKeZSkUSzNlWLlUO6l8aZFjqJ4FPi2OyBvOG/r
LUuEaUmkRDnZrEFjfHcjwVtT36Zh2LIGUvIV0eFjOm5WgGiyQgk0a5GfLmz4iJWC8AcXKFvxjok5
0Dou6S4h66AWHYkYeS3Unh5+p8ciBNf04I5UeUNyfIUkfJdB2edbbtcSJ+qzKInKasEgrBqGff8N
qz6oliZ9ik6SEr5tPblLRbZLsC4Pdtw/a+DxtX/QtI0ye46Ndx2bFbRlQMTTn3r2dajwF1zbo/Mf
2xa83rags+0+7I/Lsd8FUvKdrIhcFZeASm9889lP9alR6GPjd5w+L/RuA3f8RVcMU+Ojnj8Bbo7F
PGVuZHN0cmVhbQplbmRvYmoKMTMzIDAgb2JqCjUwNwplbmRvYmoKMTM3IDAgb2JqCjw8L0xlbmd0
aCAxMzggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+PgpzdHJlYW0KeJy1lF1v2jAUhu/zK87dWmk4
HwhBc9dRmJCmbiMZvZh2YcxJ8Bo7qY8h67+fQ+gYrYbCuh0rsRKfj/c8if0AAQshaMZ+Fsrz50PI
yQvgvbty78ELdw6wn4SCd6lzGkEYQZp5bVwIUR+GwxGkyruYaYtGo+3dGJ5ZeG6zjzeTaS8Zz16s
7G2KS4iCsH+Zfvf6V5B+8C5272+5Qqq4wPjgu7a2in1fbJEpaQ2y0uTNk78qa12UfEV+yILLN17Y
PyRKKhQyk4JbWepd2hjGpVLuYbEpNBq+lIW0j8D1CiY/qpI2BsklacMXaMgFxr9rbou063PM0KAW
CF/ms/iEzl8R11VVODnLAmFccCKk+FiJ8xxETw2MmLuNF/PpvmpHRnVdM1eE5K52E++TWKPiTpXJ
XoNpjlVprNQ5TEujuP0XpI7VNgr/ktZVSytJIDqHFgleMS3JsrzcHkAR9bbRa1glojQNqeSRLKqT
pKKunDJpnM6WE9FJTvvyR4TCwCEa301g0AnQrX/dvfk75PcaiWCiN8pRaDxONj1gYaeNVHfeSE8S
jnsOdz27vyJgo//W9Bkfu5VxZt+iJvIPfaX8nq85reVbQAu8YHBs7iiT7iCDP9jXTzxHiIbfXMZJ
6n124yeJyaO3ZW5kc3RyZWFtCmVuZG9iagoxMzggMCBvYmoKNDgzCmVuZG9iagoxNDIgMCBvYmoK
PDwvTGVuZ3RoIDE0MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nK1T0W7aMBR9
z1dcaQ9rJRJIGIXmjUE6RaKFhQxNmvZg3Evi4Tip7dBtXz8nYUAZY2yaLcuy7/XxuefYT9BxXOhU
fTvTzGpHfUiU1YF3ZiTWk+XWCbCdaAZvY5M0ANeDeGU151zwutDvDyDOrKtQaJQCtT2WZKXhuIXT
cXBnz0fhL5Ftu8MleB23ex1/sbq3EE+sq3p/WBScUbLkCCNOlELlw5zmkonk+rXV835mup4DcD8M
RuA5HRM5xHggGaqCUPT396VaF367nRGkTsa0RCeXSfvj/WROU8xIHbDNPWh7Bs3t7tHmBVK2Mpw0
y0WN7cM94c9EIgy1lmxZaoRAlBnKJoeIRxilRBJqNGLf600D2sAtUCqz9g/FaEpo4hGuUKKgCB+i
0D9HfnfklGbBBoWOsMilblU0CV3PiK48eylj18g4HYWTv5NRUVI4gintJPnGrGoJc8p4u4H5k37T
AoWRCOmaGxCoH5NRi20QJkQkJUnwfwh2RPOQiGrotnYwp9oWhipJ9zBFueQ7kFm5VA/hPA4j5aQ6
42fhXlWZdhjZ/Ztb76x7puYd05d+van8Wgwn0HPc6kOPccUEq8lcbl++IfzkL6gC9uMe0u5dauai
5MJ4uGSc6W/1DxhWpajMPMPLPG0KusTWI/r/qGTvSMkIVcl1paLbu6mzYrImKVEpawFqMHce+Rl8
LZhE9Tu7P81MyeANPhvIILbem/4DVLJ++GVuZHN0cmVhbQplbmRvYmoKMTQzIDAgb2JqCjU0OApl
bmRvYmoKMTQ3IDAgb2JqCjw8L0xlbmd0aCAxNDggMCBSL0ZpbHRlciAvRmxhdGVEZWNvZGU+Pgpz
dHJlYW0KeJzdVVFv2zYQftevOLgPS4FItpw5ToVmhSfbhYAs6WzVKFD0gaYoi4tEqiSVOP++R0qy
nQ5Nh2FPk2ALIo/f3X333ekrjIIQRvbunrTyhqsp7LQ3gvf423lfvdAZQPegFfyeotEVhGNIc689
F8L4AqbTK0gr7ywRhinBjD9XJDfw/ZXczRdLfx0nf9vpriXbwngUXrxO//Iu3kB645259VtSMV0T
yqKjbWFMHQ2H8oGUQcWNYoFUu+GnP27WtGAVcRu+YropjfYnr3/xwosj4LpmlOecEsOlcPAR3NVM
wKYpBVNky0tunoCIDGZaM60rJgzcELFryI4hWAuzYUojQHSawyQIkdODyYrlTDFBGXxcJdFLoR+O
zOq6xNC2JYO4JNZ9ZD0d4kXDybjPJbwMAO42s5vOMcSyqpzNf0IgdWj/Z/6myN+nOJ4vIQzG/5w2
5Ijel1wbHQj8D3byYbinNMuHLczP2FrsDROauyClyPmuUe123APDnGmqeN2FfPajpoGlVBUxL5La
xvRTRjUl9TEdfRq27rI7fzGUnhyt6BGnbrblAeVDs9W3yTpNVjooTFW+CPfKWvrJyp+OpxNf/fov
ShyOA2fORMb3kGwimAlpCqYAlY5VIFVdWkGOL/t6pQXXoBl11aiVfOAZ0yhlYK0xyNy+cUFxA1WN
VMqMZbgAiNsOueCZAhxiJgEdg2AU24EoXj6BYjUOKIthD0qBS4/kCYzsMIFATZThtCmJ6nLv3QYd
bB8UYkllXJzEGELvLQyBeJ2sUteHzhY1h6F2ULmSlfPcY2ROcNs2l8+rZTwZTUdfIIDEQIMcg/OM
JKPC4LGQuu/kjDu2iHqCXJalfNQQbxaouhFoN0zO2xAMEFYhvnbkt6Zc7CBeLDqkUXDpMpPNrrCx
aQbPZQhEMUekbZET1me3MzBOEIdWMJafStrRc96+9FXVhQ3xNHUkK2M46bTBNmR2qwNpdD/MsOz2
RGY/bcGzQfH23b4q4aHtu+sBpj1oK4i5XQ8+pkv/avDut2eSeNt+C+eSNm40nh7G0yWxJ5kY9IpH
B0JfDxolIs5MHqEuSKUjXI6EjjiKJfet36PwU3JPCqILfg4MeS+D73prsa85qu9Hrff5Aw5qGL/5
goiL1PsT72/+ZlrYZW5kc3RyZWFtCmVuZG9iagoxNDggMCBvYmoKODYxCmVuZG9iagoxNTIgMCBv
YmoKPDwvTGVuZ3RoIDE1MyAwIFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nK1Va4+b
OBT9zq+w+NJWWzCPaSdBTLTdJNNG6mN2gqpKq9XKY5zEW7Cp7bz21+81JDNA6LYf1igi2Oce33M5
vnxDgR+iwF6nOy0dfH+N1toJ0Fv4rZ1vTlgD0OlGS/RbBqARCiOUrZwmLkRRjK6vRygrnecLYZgS
zHgzRVYG9cfi02x+6y2ni4uV07hlDygKwvhF9rcTj1H23nlupw9lIXTCZc5WN+5WiYQzs0oqokip
E1hMzqte6Afui2dOGA/FepryH8QD4szRij5oiNsYUyUY7/d7fx/7Uq1xFAQh/vLh/ZJuWEk8LrQh
gjJ3co5G6UJQnjNhULVVldTsxlWskspwsW7BWsDFDAlSAo5qrozPDqSsCuZTWbqTcDS+GscpfsJ2
KO5r5oyXbGIz84KxF8ZZFCfhOImufgmCJAhS3EK1g2dMU8Urw6WYPCbd5Iq4QLB/RcQRHQ4pbkPb
FG+0ZlqXENiettoglpqao2A27MZdEV6w3EXmWIFWkpdcuLjDhofp0g/MbGTe26Gd0huB6uz5ijOF
5AoRtNsWginywAtujohrxMoHlucs77J8T5nVlufcTpNiRgxBeZM3uMPtAgH6aKTkc3vbHgwtK0YX
s0db0R3zS24Uq50FTziXe1FIkmvcNuR5dLgtz/Tz3IOjE3jB1Sju1rKuZkdAt9KXJU2nUhj7zpQs
rBcVI0aq8+uCDIng/xDL19N/DvwIHp7Mn8yLpsvFfZbi9nI38J6tuTbq+I6IvGBgveYRzKHAG5PT
QfCAy3q4je0RzUvw1oQ2G/16cYxS3AA6FTil1Zmc78BE/WLB/G0h9xcvfXnUhpWIEsPW0mat5VZ1
WsEj9CP443K68ZgCx7dIeLW78ghMw9kfR37gR35kz/AJOcgylVvbhE+vilkR7uTVtdVYLwxkhIdS
SnGj6cdSDVFrZv4PqcLSnJWGr3E0+g+tw2nbBJnaccoQr/6qlDSSyuLGfT2QH2DvoL9NRlDS+s/A
HieygaWfbwk1/Kkt3BXErKQqB1AXXaFqd4Wc03pDdcTRQEuw48xtOSAYKEpOldRyZZI9F9BT4GtW
JVCXRFdRv000kr/fKk4lGfBFii+PRTo/gBpTtwlEaNP4HwpJv3obqY2L+k1qCC/Nhqkmz1dR/VHP
yFeyIXrDXyJmECn8XgmAhYNj+pU5jz/uyJqhOPgTGOeZ8ztc/wIVUm3hZW5kc3RyZWFtCmVuZG9i
agoxNTMgMCBvYmoKOTA0CmVuZG9iagoxNTcgMCBvYmoKPDwvTGVuZ3RoIDE1OCAwIFIvRmlsdGVy
IC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nIVV23KbMBB95yu2fmkyLUjCuTKE6TROWs90ekmY6UOn
D4q8tpUYRCTZjv++4pKU2JjAMELas2cXsXv0CDRgQMu7GUXmkZtTmBmPwhf3zLxHj1UAaAaRwefU
gc6AhZBOvdqPQTiE09MzSDPvYJxb1Dlaf6T51ML2Nf4xurr2by/HO5bmusY7CCkbHqb33vAc0m/e
wYstfuf7EN+gUHoytpglMOcGeA74JFAXFqZaZcBhoWbg+8nhe48Ntxhq59J00AraLI+45dsmZ3TL
mMoMk5BS5tNznw1TdhYxFoXsAw0jSmPygulwRyO0LKxUecLhN975BvUKNeAKcwu6Cu0YWrBdkv8f
DRO7KfBi8JQtBrtAB5VqglPfCBldlQFusFDawm2BYjy6GMytLSJCBGKQSasxUHrWyfOK6Yavy815
K3bl5agj94AD5aY7IGEBJYVWU7lAMthDVBOUVD0ke9NoEqn2eD/GoebK2MRsjNvaAJ94ViwwECqL
SWXo8yxy7n44X9p5TOr3PrStK4gxn4V+SFMWRsOziB4HLBweHZ/49LgqJNtZRC0eXjRxi2IhBS/r
JSbPi73pykniYrlc5U4DvAIaXCXMpVKOvZmIqlhdt8kyBdFdui2Hicq4zMvMY9K898HV3T0Km3Ah
1DK3MWnm/anrlRSYrPGuzL+e9DpYbpcmMUsh0BjnU8/3FxV5s6pqiHv2dBXZaavONiadfdwhDaQl
iNu6RvYJ27OlvRqTKtA2OP4qjVV6s0VQavGlyq3777B2MlxoXEm1NIsNZHyCsJZ2DnaOYNRSCwR3
JqyVfgC1zp321fLcomuCVApXl9LFQNT0fs3gG2lxp9871PkopU6dzyPq1Jn2qvMrbf6urJw2HQWm
lGartnfbZWSstEvMxcZv0vvEzsOABmEQVqH2yXhMWp/4ett3Njgm41zISavI3Ep1co6UWGbNOjs+
qU63lD9wdxDO5UdAC3wRbJXS1VMhNRrYc/35yWcIQ/bXUV6l3i93/wM0Tf1YZW5kc3RyZWFtCmVu
ZG9iagoxNTggMCBvYmoKNzYzCmVuZG9iagoxNjIgMCBvYmoKPDwvTGVuZ3RoIDE2MyAwIFIvRmls
dGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nJWWW3PaSBCF3/kVXbysXSW0CGJ8eeMiHCVgO6CU
NxX7YSwaGFsa4ZmRbf79nhHKxVyytaJcgDV0f336dMMzNf2Amu5RPSdZ7e/JKS1MrUmX+FvUnmtB
eYCqpySjXoxDZxS0KJ7XNp8LqNWm09MzirPaUaQsa8W2MdBibmn7iq4H4bAx7Uc7d6pryA/Uagbt
4/ix1j6neFQ7Cto+0YTnrFklbI7/qrU6P24EuHWV60xY+cLvDx0h2vfJsN8KgvN7op4WM8Xao6nv
Uf0zr+k11zND81xTYZikIhw2ZHOK1EwmwjKCBO0y03vGCT8XUnPGytKIXzg1dY96/RsKPnguCLmU
Ho2FTpYUnJ+f+r+YK6j2+VnHQTmttGmMmD2KATaUnM6kWiAO3gk1o5GPQEY6WcH9VUkAZ4fJTF7o
hCmaAU7OJWu6O/o6ie6OL+iSkUsmNF0rK96API0H1OmUyJVev12O0KNPQhVCr9GS5sluFSfN0yaq
GAi1TuXrhnnM8tGhfqr4v/k04CxZsnrKUUC8BJxKpOM7VMX1wyMnFh8ziZYrK3NF4VuyFGrBNCyb
Xd/o7PJ7OJdw9sB6twZQ79H+pNVy2l8JbVk52UvOjz510xc2VuMdQC8LMKZS8cYit1pa9AVHD1FH
3asu9XNl8DktHLWhKepw+JW5Kpu0OhU+QLxd6rEo9T7bJe80P5yAfJxrCfi1R5+dlycs0oaVmRMW
Lmlg+mDtJ+gyZwVn3x1NosHdcf1Ho/fSu9AeRumllNKNYHNv/s5W/lK7nk+xFlnGaepaDAXNKteW
8jn9hDso25+Y4SZjxIJN1XAH8ItyX8N3sMOo353cu5thofMVC2emFYPuUufFqmxuFDfQqQItRk31
LianMRbpq9AHqWMYZS5TBhda1d7KOR5jy5U5ozAMKepPL6kKiIqsmAkrti1Nt6jfOazE8g4lrv9X
HBBt0fwzHgW+m1O3A9ebPYMobkhDvLwReSo38zqFLtB10RgnXwp2w9HfTPEhmqFP33CeRQHdwjfM
k5EPKbvV9wRtR+Aq0D60ExBoJzjweijndrnbvHAm3bCUTr1t92GdJIen1Kwcpnfm3BkOhDfYMZm4
gTGD+4NtW+bZyrhgH1FYjzlZYn9s9MgVQ5xxtbausHaRGrs9X6o9Q1pHRpqWKcnlpOCCplYXiS00
l4OfI0pV0qag3SDbFV4nNq8K/PCnAlsHC+xJ7QLdbOay67470mWOnebtErcusLmtsOvVz+/L3659
FfxP4CuRsXGo7rcB/h2LJ7EUZgm3sSWR+u8zurmUTrwD1/cbZ6V2WXwY177g8S/I9kfZZW5kc3Ry
ZWFtCmVuZG9iagoxNjMgMCBvYmoKOTk0CmVuZG9iagoxNjcgMCBvYmoKPDwvTGVuZ3RoIDE2OCAw
IFIvRmlsdGVyIC9GbGF0ZURlY29kZT4+CnN0cmVhbQp4nI1W0XLaOhB95yt2eLnJjOtiuwmkb8SY
lBJSLnbonWl4UIwANbZEJTmp//6uZCU3DfhOzDAYI+05e/bsil/Q8wPomZf7zMvOx0UftqrTgyt8
bzu/OoFdAO4jL+Eyw0UDCELINp1mXwBhBP3+ALKyczLhmkpO9YeRJBsNb6/Jt1Ey/pDGk4Nf3DWm
9xD2gug0+9mJLiC77pz8ueBSktqDzPfgiygKwtdUejDCr9ekLgn3YIj3mbhneLvAW1wBX/zTvzpB
dCRathOlEri0270hJVV7klMFjMM/s2u4O8l2TK4hWTPNBL877XrwPYox1psoC5qLsqR8Tcw6pENz
Wt5TiZn0Lgx2eG6xg8gPfRSBb4Qsce0jxa0bKilHVBf2x2IcR1F0sQKYFjWnHlxhFsnat5nEPtzQ
J5tnd0Q0tQ8zVlIQHPSOtuX5XJbPdrHSpNwrzAaxwIB58LUqakM3fEX3mc3ZWbgySapcyIIgmYbL
pQ9TIR+N/t2riq1pwTiKh7nBd4mK8a2J36o8/a0N6ZTmFa6uIRZcYRBpNTTkLuM59ENHEjk0JA/V
R9bREdbngwGynlFSIK+tBzOUsZvtKEySbGzru6BbprSsHdYgcFi402uj/ZXwikgr1adD0LModFJx
lj94MG9Kh8DPBUBCSpEthbG1gKuB2dcK+S3XwplpcAh5HgTnK9sWa25KkSIaSikFdsm18//Uh3H1
kz0RSZwGiR+cfwIt2jBvOTMeNZmISuYo2ppyzTaMSoV9cbuY3J3CqOakZDnavaBbW7bD4owYugY9
UkNaK01L3DwajVLcPdzvC5bbbfgwubmd2QYzcpicvMNYMyLznZkOwRsZ4uE8iVdNP1OYTbJFghrI
vZCuIbsx9ifiDLUm+QPMiTbVgIRXpTNcmxC26QqiFOb+QtbiWbZvicTJytn7/4lghTZsWzWP38MD
QePkOGSaNphpTuRGmIkxbRp07qPbisKV/BhyG1qKnW7696VmBsWi30zSrJkmaGKe1+gQzE5D/6wX
HinZq0kY9N4yT94pVvKI3oPk915i77gKJP+J0QSbPwe7sbtJgSyVZrrCISk2kGpUhMi1aiYmzXdc
FGJbv6C0STEviLat8KpIXTOKOD1qxeU7k1pWBfYruWeFGX6GFCYoVCXtSdDmgeVxDywX4wZ1Eg/T
SRtIUypT17HEw+5JyAcbczE2QdtQD7Ce/Tan6ALnsCnBQ+yVA00+KVE7AguBp5VQD3VjwzaUo4QP
bbg0NrTRJ1od2s3NFLddC/w7YU6UAoaNWZtAyil4FloiGXkgO+TKPMD5TAr/z5imLgyrAi3Xj7kZ
51G0wohJ1vkbX/8CXelyz2VuZHN0cmVhbQplbmRvYmoKMTY4IDAgb2JqCjEwMTAKZW5kb2JqCjE3
MiAwIG9iago8PC9MZW5ndGggMTczIDAgUi9GaWx0ZXIgL0ZsYXRlRGVjb2RlPj4Kc3RyZWFtCnic
lVRdc5s6EH3nV+zkpfHU5gJ2ajdP5WK7dZ0PN9Ckc5tMR4YFVINEhMg0/77Lh9M4sTtzxTACadlz
9uxB92CZNlj11c1hbvxzNYakNCz4SHdi3Bt2EwDdFObwb0BBE7AdCGKj/c4GZwjj8QSC3DheCI1K
oB5MFYs1vByLy+lsPvC9xaudbsxxDY5lD3vBT2P4HoIz45hWv3s3s7s2IEgRzhfB1Qw8qQqpmOZS
9OHIk3kuBdwg2wgsS5iJKsd2t/fGsIfbVM/G7TGlve0d9cGkEOfdMzTfv/tfaH4oFRcJ+I+lxvxv
gL6/D/HSW5y1iFP2wCO4YRnpmHOFwEQES6ZQEAhTsRTt0jlTnIHHSl4gESKih1AvC/rWSzHcZLzU
0HSIhZo/IJwxkVQsQWJWM7jtwTWqkkoEx7SO+pTxRS63UDyrG2S/LODaPfu7ZA2N6yoThL7mGdeP
TR1uWZKAOQp9iP9zkoSyTz7fc1ct+h/h+jA1+/Cl4oLQfXrcyteHJb012OYhzE8sWzMVcVStthBg
mAoesgz8AkMe02NdF8RSgaZ9H8NKUU2vJfMkCS40uJWWefvRSkktQ5lRRTXz294p1POT+Lbp7BP/
YuEHLTzRWFXrbEtiYlkDm+S4wgfedo+qxYKcuEb1Os+e9n3zvOn87qD/vJSpDGubpzmP9B5PHhKy
jrxA4vsfr38QUnO/frNfJFLJ1xnuVTDmSdU66ZmTp1iGihfN6lwqEpcEbSohIz+0Wr7ORuJS2PTK
nQeNlT5X2eNLSahXqVTlG3CjSGHt0C5PwDZYpryeWcroaafui4YhFbsQpea60ggyppe4IVfTbMSk
s6MSnQBl6yyZyWTrndHAGdhwUW0qPlhyzXIWEuJSJkwg72LsyWgwGb8/gUBuHmW3+JkVTOz0dZVS
a07h7cSCER3SzhhOJu+cHc6znPHsFHRb2A+9LewDMdRmIs2fBcX/OYqXtZfpl4xijlm0k+o8dGOk
32shwo7RiWVZ8AlZdF8xRYYqYaro3Ol2VxkTsg/BNxifWM6oW/3quzs1dARr3B9PuB9aLDOUzWFr
j5vop670AcmkmbnbeTJZQY4u4cD4vqpPmeHojlLOAuMLXb8BjwrqGWVuZHN0cmVhbQplbmRvYmoK
MTczIDAgb2JqCjg0MAplbmRvYmoKMTc3IDAgb2JqCjw8L0xlbmd0aCAxNzggMCBSL0ZpbHRlciAv
RmxhdGVEZWNvZGU+PgpzdHJlYW0KeJx1kl9vmzAUxd/5FEeatLUqEP4kgfSpK6Qra5Nlhaiapj3c
EgfcgEnBTOPbzzCqKZ1mCxn5HB9+9+IXWKYNq5/jmpba5MFD1mgWPqkn0140ezBgXNIS14ky+bAd
JHvtzzkbjgvP85GU2lkkJKsFk0ZY017i7Yi+hMsbIw6if5Rx3LAnOJbtnifPmrtAcq+dqd0kr0pq
sOJFQfX5B812X5VtjJAdqZYlExLVHrdVyQoSO8QsbWsuOx3rzSacBPH7YLIO4nCyjY1g+ZComD7A
mc6wauuaOtyTYIgfdVy3vNhxkWFqWzpWMd55rjP6H6nJlSQroSMMFOts4Y/SNv6o3pz5K9smrwS7
xIUN3/fh+A4s37NO8Jcl8eIScqjPLIf6rtrGSFktzaz6qcx/u/Ctag8cd7SrnqjrMU6i1lQTItFI
LlvJ+lbEKWciZei7kbA0F1VRZd0I6y/suTFDQgeVVZKO6KAYRnHuWoZlL5whdNz7TEcSJ/WN8F2P
ZRyueGMSb6Qh1BmTUvP5qNzTqTPY++/kPbMOJkGF+ea/L38dec2a/12L7xvKGNzZDxW5TLSvav4G
CTWwzWVuZHN0cmVhbQplbmRvYmoKMTc4IDAgb2JqCjQzOQplbmRvYmoKNCAwIG9iago8PC9UeXBl
L1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNv
dXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgOSAwIFIKL0ZvbnQgMTAgMCBS
Cj4+Ci9Db250ZW50cyA1IDAgUgo+PgplbmRvYmoKMTEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlh
Qm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJv
Y1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDE0IDAgUgovRm9udCAxNSAwIFIKPj4KL0NvbnRl
bnRzIDEyIDAgUgo+PgplbmRvYmoKMTYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAg
NTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERG
IC9UZXh0XQovRXh0R1N0YXRlIDE5IDAgUgovRm9udCAyMCAwIFIKPj4KL0NvbnRlbnRzIDE3IDAg
Ugo+PgplbmRvYmoKMjEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0K
L1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQov
RXh0R1N0YXRlIDI0IDAgUgovRm9udCAyNSAwIFIKPj4KL0NvbnRlbnRzIDIyIDAgUgo+PgplbmRv
YmoKMjYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAw
L1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRl
IDI5IDAgUgovRm9udCAzMCAwIFIKPj4KL0NvbnRlbnRzIDI3IDAgUgo+PgplbmRvYmoKMzEgMCBv
YmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAz
IDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDM0IDAgUgov
Rm9udCAzNSAwIFIKPj4KL0NvbnRlbnRzIDMyIDAgUgo+PgplbmRvYmoKMzYgMCBvYmoKPDwvVHlw
ZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVz
b3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDM5IDAgUgovRm9udCA0MCAw
IFIKPj4KL0NvbnRlbnRzIDM3IDAgUgo+PgplbmRvYmoKNDEgMCBvYmoKPDwvVHlwZS9QYWdlL01l
ZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwv
UHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDQ0IDAgUgovRm9udCA0NSAwIFIKPj4KL0Nv
bnRlbnRzIDQyIDAgUgo+PgplbmRvYmoKNDYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFsw
IDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsv
UERGIC9UZXh0XQovRXh0R1N0YXRlIDQ5IDAgUgovRm9udCA1MCAwIFIKPj4KL0NvbnRlbnRzIDQ3
IDAgUgo+PgplbmRvYmoKNTEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0
Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0
XQovRXh0R1N0YXRlIDU0IDAgUgovRm9udCA1NSAwIFIKPj4KL0NvbnRlbnRzIDUyIDAgUgo+Pgpl
bmRvYmoKNTYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0
ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0
YXRlIDU5IDAgUgovRm9udCA2MCAwIFIKPj4KL0NvbnRlbnRzIDU3IDAgUgo+PgplbmRvYmoKNjEg
MCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVu
dCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDY0IDAg
UgovRm9udCA2NSAwIFIKPj4KL0NvbnRlbnRzIDYyIDAgUgo+PgplbmRvYmoKNjYgMCBvYmoKPDwv
VHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgov
UmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDY5IDAgUgovRm9udCA3
MCAwIFIKPj4KL0NvbnRlbnRzIDY3IDAgUgo+PgplbmRvYmoKNzEgMCBvYmoKPDwvVHlwZS9QYWdl
L01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2Vz
PDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDc0IDAgUgovRm9udCA3NSAwIFIKPj4K
L0NvbnRlbnRzIDcyIDAgUgo+PgplbmRvYmoKNzYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94
IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1Nl
dFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDc5IDAgUgovRm9udCA4MCAwIFIKPj4KL0NvbnRlbnRz
IDc3IDAgUgo+PgplbmRvYmoKODEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1
IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9U
ZXh0XQovRXh0R1N0YXRlIDg0IDAgUgovRm9udCA4NSAwIFIKPj4KL0NvbnRlbnRzIDgyIDAgUgo+
PgplbmRvYmoKODYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1Jv
dGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0
R1N0YXRlIDg5IDAgUgovRm9udCA5MCAwIFIKPj4KL0NvbnRlbnRzIDg3IDAgUgo+PgplbmRvYmoK
OTEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1Bh
cmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDk0
IDAgUgovRm9udCA5NSAwIFIKPj4KL0NvbnRlbnRzIDkyIDAgUgo+PgplbmRvYmoKOTYgMCBvYmoK
PDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAg
UgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDk5IDAgUgovRm9u
dCAxMDAgMCBSCj4+Ci9Db250ZW50cyA5NyAwIFIKPj4KZW5kb2JqCjEwMSAwIG9iago8PC9UeXBl
L1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNv
dXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTA0IDAgUgovRm9udCAxMDUg
MCBSCj4+Ci9Db250ZW50cyAxMDIgMCBSCj4+CmVuZG9iagoxMDYgMCBvYmoKPDwvVHlwZS9QYWdl
L01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2Vz
PDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDEwOSAwIFIKL0ZvbnQgMTEwIDAgUgo+
PgovQ29udGVudHMgMTA3IDAgUgo+PgplbmRvYmoKMTExIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRp
YUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1By
b2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAxMTQgMCBSCi9Gb250IDExNSAwIFIKPj4KL0Nv
bnRlbnRzIDExMiAwIFIKPj4KZW5kb2JqCjExNiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3gg
WzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0
Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTE5IDAgUgovRm9udCAxMjAgMCBSCj4+Ci9Db250ZW50
cyAxMTcgMCBSCj4+CmVuZG9iagoxMjEgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAg
NTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERG
IC9UZXh0XQovRXh0R1N0YXRlIDEyNCAwIFIKL0ZvbnQgMTI1IDAgUgo+PgovQ29udGVudHMgMTIy
IDAgUgo+PgplbmRvYmoKMTI2IDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4
NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4
dF0KL0V4dEdTdGF0ZSAxMjkgMCBSCi9Gb250IDEzMCAwIFIKPj4KL0NvbnRlbnRzIDEyNyAwIFIK
Pj4KZW5kb2JqCjEzMSAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQov
Um90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9F
eHRHU3RhdGUgMTM0IDAgUgovRm9udCAxMzUgMCBSCj4+Ci9Db250ZW50cyAxMzIgMCBSCj4+CmVu
ZG9iagoxMzYgMCBvYmoKPDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0
ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0
YXRlIDEzOSAwIFIKL0ZvbnQgMTQwIDAgUgo+PgovQ29udGVudHMgMTM3IDAgUgo+PgplbmRvYmoK
MTQxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9Q
YXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAx
NDQgMCBSCi9Gb250IDE0NSAwIFIKPj4KL0NvbnRlbnRzIDE0MiAwIFIKPj4KZW5kb2JqCjE0NiAw
IG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50
IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTQ5IDAg
UgovRm9udCAxNTAgMCBSCj4+Ci9Db250ZW50cyAxNDcgMCBSCj4+CmVuZG9iagoxNTEgMCBvYmoK
PDwvVHlwZS9QYWdlL01lZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAg
UgovUmVzb3VyY2VzPDwvUHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDE1NCAwIFIKL0Zv
bnQgMTU1IDAgUgo+PgovQ29udGVudHMgMTUyIDAgUgo+PgplbmRvYmoKMTU2IDAgb2JqCjw8L1R5
cGUvUGFnZS9NZWRpYUJveCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jl
c291cmNlczw8L1Byb2NTZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAxNTkgMCBSCi9Gb250IDE2
MCAwIFIKPj4KL0NvbnRlbnRzIDE1NyAwIFIKPj4KZW5kb2JqCjE2MSAwIG9iago8PC9UeXBlL1Bh
Z2UvTWVkaWFCb3ggWzAgMCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJj
ZXM8PC9Qcm9jU2V0Wy9QREYgL1RleHRdCi9FeHRHU3RhdGUgMTY0IDAgUgovRm9udCAxNjUgMCBS
Cj4+Ci9Db250ZW50cyAxNjIgMCBSCj4+CmVuZG9iagoxNjYgMCBvYmoKPDwvVHlwZS9QYWdlL01l
ZGlhQm94IFswIDAgNTk1IDg0Ml0KL1JvdGF0ZSAwL1BhcmVudCAzIDAgUgovUmVzb3VyY2VzPDwv
UHJvY1NldFsvUERGIC9UZXh0XQovRXh0R1N0YXRlIDE2OSAwIFIKL0ZvbnQgMTcwIDAgUgo+Pgov
Q29udGVudHMgMTY3IDAgUgo+PgplbmRvYmoKMTcxIDAgb2JqCjw8L1R5cGUvUGFnZS9NZWRpYUJv
eCBbMCAwIDU5NSA4NDJdCi9Sb3RhdGUgMC9QYXJlbnQgMyAwIFIKL1Jlc291cmNlczw8L1Byb2NT
ZXRbL1BERiAvVGV4dF0KL0V4dEdTdGF0ZSAxNzQgMCBSCi9Gb250IDE3NSAwIFIKPj4KL0NvbnRl
bnRzIDE3MiAwIFIKPj4KZW5kb2JqCjE3NiAwIG9iago8PC9UeXBlL1BhZ2UvTWVkaWFCb3ggWzAg
MCA1OTUgODQyXQovUm90YXRlIDAvUGFyZW50IDMgMCBSCi9SZXNvdXJjZXM8PC9Qcm9jU2V0Wy9Q
REYgL1RleHRdCi9FeHRHU3RhdGUgMTc5IDAgUgovRm9udCAxODAgMCBSCj4+Ci9Db250ZW50cyAx
NzcgMCBSCj4+CmVuZG9iagozIDAgb2JqCjw8IC9UeXBlIC9QYWdlcyAvS2lkcyBbCjQgMCBSCjEx
IDAgUgoxNiAwIFIKMjEgMCBSCjI2IDAgUgozMSAwIFIKMzYgMCBSCjQxIDAgUgo0NiAwIFIKNTEg
MCBSCjU2IDAgUgo2MSAwIFIKNjYgMCBSCjcxIDAgUgo3NiAwIFIKODEgMCBSCjg2IDAgUgo5MSAw
IFIKOTYgMCBSCjEwMSAwIFIKMTA2IDAgUgoxMTEgMCBSCjExNiAwIFIKMTIxIDAgUgoxMjYgMCBS
CjEzMSAwIFIKMTM2IDAgUgoxNDEgMCBSCjE0NiAwIFIKMTUxIDAgUgoxNTYgMCBSCjE2MSAwIFIK
MTY2IDAgUgoxNzEgMCBSCjE3NiAwIFIKXSAvQ291bnQgMzUKPj4KZW5kb2JqCjEgMCBvYmoKPDwv
VHlwZSAvQ2F0YWxvZyAvUGFnZXMgMyAwIFIKL01ldGFkYXRhIDE4MSAwIFIKPj4KZW5kb2JqCjcg
MCBvYmoKPDwvVHlwZS9FeHRHU3RhdGUKL09QTSAxPj5lbmRvYmoKOSAwIG9iago8PC9SNwo3IDAg
Uj4+CmVuZG9iagoxMCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxNCAwIG9iago8PC9SNwo3
IDAgUj4+CmVuZG9iagoxNSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxOSAwIG9iago8PC9S
Nwo3IDAgUj4+CmVuZG9iagoyMCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoyNCAwIG9iago8
PC9SNwo3IDAgUj4+CmVuZG9iagoyNSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoyOSAwIG9i
ago8PC9SNwo3IDAgUj4+CmVuZG9iagozMCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagozNCAw
IG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagozNSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoz
OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago0MCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9i
ago0NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago0NSAwIG9iago8PC9SOAo4IDAgUj4+CmVu
ZG9iago0OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago1MCAwIG9iago8PC9SOAo4IDAgUj4+
CmVuZG9iago1NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago1NSAwIG9iago8PC9SOAo4IDAg
Uj4+CmVuZG9iago1OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago2MCAwIG9iago8PC9SOAo4
IDAgUj4+CmVuZG9iago2NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago2NSAwIG9iago8PC9S
OAo4IDAgUj4+CmVuZG9iago2OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago3MCAwIG9iago8
PC9SOAo4IDAgUj4+CmVuZG9iago3NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago3NSAwIG9i
ago8PC9SOAo4IDAgUj4+CmVuZG9iago3OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago4MCAw
IG9iago8PC9SOAo4IDAgUj4+CmVuZG9iago4NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iago4
NSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iago4OSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9i
ago5MCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iago5NCAwIG9iago8PC9SNwo3IDAgUj4+CmVu
ZG9iago5NSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iago5OSAwIG9iago8PC9SNwo3IDAgUj4+
CmVuZG9iagoxMDAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTA0IDAgb2JqCjw8L1I3Cjcg
MCBSPj4KZW5kb2JqCjEwNSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxMDkgMCBvYmoKPDwv
UjcKNyAwIFI+PgplbmRvYmoKMTEwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjExNCAwIG9i
ago8PC9SNwo3IDAgUj4+CmVuZG9iagoxMTUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTE5
IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjEyMCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9i
agoxMjQgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKMTI1IDAgb2JqCjw8L1I4CjggMCBSPj4K
ZW5kb2JqCjEyOSAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagoxMzAgMCBvYmoKPDwvUjgKOCAw
IFI+PgplbmRvYmoKMTM0IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjEzNSAwIG9iago8PC9S
OAo4IDAgUj4+CmVuZG9iagoxMzkgMCBvYmoKPDwvUjcKNyAwIFI+PgplbmRvYmoKMTQwIDAgb2Jq
Cjw8L1I4CjggMCBSPj4KZW5kb2JqCjE0NCAwIG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagoxNDUg
MCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTQ5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2Jq
CjE1MCAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxNTQgMCBvYmoKPDwvUjcKNyAwIFI+Pgpl
bmRvYmoKMTU1IDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjE1OSAwIG9iago8PC9SNwo3IDAg
Uj4+CmVuZG9iagoxNjAgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoKMTY0IDAgb2JqCjw8L1I3
CjcgMCBSPj4KZW5kb2JqCjE2NSAwIG9iago8PC9SOAo4IDAgUj4+CmVuZG9iagoxNjkgMCBvYmoK
PDwvUjcKNyAwIFI+PgplbmRvYmoKMTcwIDAgb2JqCjw8L1I4CjggMCBSPj4KZW5kb2JqCjE3NCAw
IG9iago8PC9SNwo3IDAgUj4+CmVuZG9iagoxNzUgMCBvYmoKPDwvUjgKOCAwIFI+PgplbmRvYmoK
MTc5IDAgb2JqCjw8L1I3CjcgMCBSPj4KZW5kb2JqCjE4MCAwIG9iago8PC9SOAo4IDAgUj4+CmVu
ZG9iago4IDAgb2JqCjw8L0Jhc2VGb250L0NvdXJpZXIvVHlwZS9Gb250Ci9TdWJ0eXBlL1R5cGUx
Pj4KZW5kb2JqCjE4MSAwIG9iago8PC9UeXBlL01ldGFkYXRhCi9TdWJ0eXBlL1hNTC9MZW5ndGgg
MTM1ND4+c3RyZWFtCjw/eHBhY2tldCBiZWdpbj0n77u/JyBpZD0nVzVNME1wQ2VoaUh6cmVTek5U
Y3prYzlkJz8+Cjw/YWRvYmUteGFwLWZpbHRlcnMgZXNjPSJDUkxGIj8+Cjx4OnhtcG1ldGEgeG1s
bnM6eD0nYWRvYmU6bnM6bWV0YS8nIHg6eG1wdGs9J1hNUCB0b29sa2l0IDIuOS4xLTEzLCBmcmFt
ZXdvcmsgMS42Jz4KPHJkZjpSREYgeG1sbnM6cmRmPSdodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAy
LzIyLXJkZi1zeW50YXgtbnMjJyB4bWxuczppWD0naHR0cDovL25zLmFkb2JlLmNvbS9pWC8xLjAv
Jz4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J2EzMGM4MmM2LWNiYWQtMTFlZC0wMDAwLTBm
NmEyZWE4ZTc3JyB4bWxuczpwZGY9J2h0dHA6Ly9ucy5hZG9iZS5jb20vcGRmLzEuMy8nIHBkZjpQ
cm9kdWNlcj0nR1BMIEdob3N0c2NyaXB0IDkuMDQnLz4KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJv
dXQ9J2EzMGM4MmM2LWNiYWQtMTFlZC0wMDAwLTBmNmEyZWE4ZTc3JyB4bWxuczp4bXA9J2h0dHA6
Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8nPjx4bXA6TW9kaWZ5RGF0ZT4yMDEzLTAzLTIzVDA5OjEw
OjEzKzAxOjAwPC94bXA6TW9kaWZ5RGF0ZT4KPHhtcDpDcmVhdGVEYXRlPjIwMTMtMDMtMjNUMDk6
MTA6MTMrMDE6MDA8L3htcDpDcmVhdGVEYXRlPgo8eG1wOkNyZWF0b3JUb29sPkdOVSBFbnNjcmlw
dCAxLjYuNS45MDwveG1wOkNyZWF0b3JUb29sPjwvcmRmOkRlc2NyaXB0aW9uPgo8cmRmOkRlc2Ny
aXB0aW9uIHJkZjphYm91dD0nYTMwYzgyYzYtY2JhZC0xMWVkLTAwMDAtMGY2YTJlYThlNzcnIHht
bG5zOnhhcE1NPSdodHRwOi8vbnMuYWRvYmUuY29tL3hhcC8xLjAvbW0vJyB4YXBNTTpEb2N1bWVu
dElEPSd1dWlkOmEzMGM4MmM2LWNiYWQtMTFlZC0wMDAwLTBmNmEyZWE4ZTc3MjAxMy0wMy0yM1Qw
OToxMDoxMyswMTowMCcvPgo8cmRmOkRlc2NyaXB0aW9uIHJkZjphYm91dD0nYTMwYzgyYzYtY2Jh
ZC0xMWVkLTAwMDAtMGY2YTJlYThlNzcnIHhtbG5zOmRjPSdodHRwOi8vcHVybC5vcmcvZGMvZWxl
bWVudHMvMS4xLycgZGM6Zm9ybWF0PSdhcHBsaWNhdGlvbi9wZGYnPjxkYzp0aXRsZT48cmRmOkFs
dD48cmRmOmxpIHhtbDpsYW5nPSd4LWRlZmF1bHQnPkVuc2NyaXB0IE91dHB1dDwvcmRmOmxpPjwv
cmRmOkFsdD48L2RjOnRpdGxlPjwvcmRmOkRlc2NyaXB0aW9uPgo8L3JkZjpSREY+CjwveDp4bXBt
ZXRhPgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCjw/eHBhY2tldCBlbmQ9J3cnPz4K
ZW5kc3RyZWFtCmVuZG9iagoyIDAgb2JqCjw8L1Byb2R1Y2VyKEdQTCBHaG9zdHNjcmlwdCA5LjA0
KQovQ3JlYXRpb25EYXRlKEQ6MjAxMzAzMjMwOTEwMTMrMDEnMDAnKQovTW9kRGF0ZShEOjIwMTMw
MzIzMDkxMDEzKzAxJzAwJykKL1RpdGxlKEVuc2NyaXB0IE91dHB1dCkKL0NyZWF0b3IoR05VIEVu
c2NyaXB0IDEuNi41LjkwKT4+ZW5kb2JqCnhyZWYKMCAxODIKMDAwMDAwMDAwMCA2NTUzNSBmIAow
MDAwMDM5NDMzIDAwMDAwIG4gCjAwMDAwNDMxNjYgMDAwMDAgbiAKMDAwMDAzOTExOSAwMDAwMCBu
IAowMDAwMDMzMzg3IDAwMDAwIG4gCjAwMDAwMDAwMTUgMDAwMDAgbiAKMDAwMDAwMTE3MiAwMDAw
MCBuIAowMDAwMDM5NDk5IDAwMDAwIG4gCjAwMDAwNDE2NzIgMDAwMDAgbiAKMDAwMDAzOTU0MCAw
MDAwMCBuIAowMDAwMDM5NTY5IDAwMDAwIG4gCjAwMDAwMzM1NDYgMDAwMDAgbiAKMDAwMDAwMTE5
MiAwMDAwMCBuIAowMDAwMDAyMzYzIDAwMDAwIG4gCjAwMDAwMzk1OTkgMDAwMDAgbiAKMDAwMDAz
OTYyOSAwMDAwMCBuIAowMDAwMDMzNzA4IDAwMDAwIG4gCjAwMDAwMDIzODQgMDAwMDAgbiAKMDAw
MDAwMzYyMCAwMDAwMCBuIAowMDAwMDM5NjU5IDAwMDAwIG4gCjAwMDAwMzk2ODkgMDAwMDAgbiAK
MDAwMDAzMzg3MCAwMDAwMCBuIAowMDAwMDAzNjQxIDAwMDAwIG4gCjAwMDAwMDQ5ODIgMDAwMDAg
biAKMDAwMDAzOTcxOSAwMDAwMCBuIAowMDAwMDM5NzQ5IDAwMDAwIG4gCjAwMDAwMzQwMzIgMDAw
MDAgbiAKMDAwMDAwNTAwMyAwMDAwMCBuIAowMDAwMDA2MTU5IDAwMDAwIG4gCjAwMDAwMzk3Nzkg
MDAwMDAgbiAKMDAwMDAzOTgwOSAwMDAwMCBuIAowMDAwMDM0MTk0IDAwMDAwIG4gCjAwMDAwMDYx
ODAgMDAwMDAgbiAKMDAwMDAwNjk0NCAwMDAwMCBuIAowMDAwMDM5ODM5IDAwMDAwIG4gCjAwMDAw
Mzk4NjkgMDAwMDAgbiAKMDAwMDAzNDM1NiAwMDAwMCBuIAowMDAwMDA2OTY0IDAwMDAwIG4gCjAw
MDAwMDgxNTQgMDAwMDAgbiAKMDAwMDAzOTg5OSAwMDAwMCBuIAowMDAwMDM5OTI5IDAwMDAwIG4g
CjAwMDAwMzQ1MTggMDAwMDAgbiAKMDAwMDAwODE3NSAwMDAwMCBuIAowMDAwMDA5MDU1IDAwMDAw
IG4gCjAwMDAwMzk5NTkgMDAwMDAgbiAKMDAwMDAzOTk4OSAwMDAwMCBuIAowMDAwMDM0NjgwIDAw
MDAwIG4gCjAwMDAwMDkwNzUgMDAwMDAgbiAKMDAwMDAxMDA4MCAwMDAwMCBuIAowMDAwMDQwMDE5
IDAwMDAwIG4gCjAwMDAwNDAwNDkgMDAwMDAgbiAKMDAwMDAzNDg0MiAwMDAwMCBuIAowMDAwMDEw
MTAwIDAwMDAwIG4gCjAwMDAwMTEwNzMgMDAwMDAgbiAKMDAwMDA0MDA3OSAwMDAwMCBuIAowMDAw
MDQwMTA5IDAwMDAwIG4gCjAwMDAwMzUwMDQgMDAwMDAgbiAKMDAwMDAxMTA5MyAwMDAwMCBuIAow
MDAwMDEyMDI0IDAwMDAwIG4gCjAwMDAwNDAxMzkgMDAwMDAgbiAKMDAwMDA0MDE2OSAwMDAwMCBu
IAowMDAwMDM1MTY2IDAwMDAwIG4gCjAwMDAwMTIwNDQgMDAwMDAgbiAKMDAwMDAxMjkzOSAwMDAw
MCBuIAowMDAwMDQwMTk5IDAwMDAwIG4gCjAwMDAwNDAyMjkgMDAwMDAgbiAKMDAwMDAzNTMyOCAw
MDAwMCBuIAowMDAwMDEyOTU5IDAwMDAwIG4gCjAwMDAwMTM5NTAgMDAwMDAgbiAKMDAwMDA0MDI1
OSAwMDAwMCBuIAowMDAwMDQwMjg5IDAwMDAwIG4gCjAwMDAwMzU0OTAgMDAwMDAgbiAKMDAwMDAx
Mzk3MCAwMDAwMCBuIAowMDAwMDE0OTU0IDAwMDAwIG4gCjAwMDAwNDAzMTkgMDAwMDAgbiAKMDAw
MDA0MDM0OSAwMDAwMCBuIAowMDAwMDM1NjUyIDAwMDAwIG4gCjAwMDAwMTQ5NzQgMDAwMDAgbiAK
MDAwMDAxNjIwMyAwMDAwMCBuIAowMDAwMDQwMzc5IDAwMDAwIG4gCjAwMDAwNDA0MDkgMDAwMDAg
biAKMDAwMDAzNTgxNCAwMDAwMCBuIAowMDAwMDE2MjI0IDAwMDAwIG4gCjAwMDAwMTcyNjEgMDAw
MDAgbiAKMDAwMDA0MDQzOSAwMDAwMCBuIAowMDAwMDQwNDY5IDAwMDAwIG4gCjAwMDAwMzU5NzYg
MDAwMDAgbiAKMDAwMDAxNzI4MSAwMDAwMCBuIAowMDAwMDE4NDgzIDAwMDAwIG4gCjAwMDAwNDA0
OTkgMDAwMDAgbiAKMDAwMDA0MDUyOSAwMDAwMCBuIAowMDAwMDM2MTM4IDAwMDAwIG4gCjAwMDAw
MTg1MDQgMDAwMDAgbiAKMDAwMDAxOTQ4NiAwMDAwMCBuIAowMDAwMDQwNTU5IDAwMDAwIG4gCjAw
MDAwNDA1ODkgMDAwMDAgbiAKMDAwMDAzNjMwMCAwMDAwMCBuIAowMDAwMDE5NTA2IDAwMDAwIG4g
CjAwMDAwMjAwNzMgMDAwMDAgbiAKMDAwMDA0MDYxOSAwMDAwMCBuIAowMDAwMDQwNjQ5IDAwMDAw
IG4gCjAwMDAwMzY0NjMgMDAwMDAgbiAKMDAwMDAyMDA5MyAwMDAwMCBuIAowMDAwMDIwNjU4IDAw
MDAwIG4gCjAwMDAwNDA2ODAgMDAwMDAgbiAKMDAwMDA0MDcxMSAwMDAwMCBuIAowMDAwMDM2NjI5
IDAwMDAwIG4gCjAwMDAwMjA2NzkgMDAwMDAgbiAKMDAwMDAyMTIyNCAwMDAwMCBuIAowMDAwMDQw
NzQyIDAwMDAwIG4gCjAwMDAwNDA3NzMgMDAwMDAgbiAKMDAwMDAzNjc5NSAwMDAwMCBuIAowMDAw
MDIxMjQ1IDAwMDAwIG4gCjAwMDAwMjIwNDQgMDAwMDAgbiAKMDAwMDA0MDgwNCAwMDAwMCBuIAow
MDAwMDQwODM1IDAwMDAwIG4gCjAwMDAwMzY5NjEgMDAwMDAgbiAKMDAwMDAyMjA2NSAwMDAwMCBu
IAowMDAwMDIzMzQ1IDAwMDAwIG4gCjAwMDAwNDA4NjYgMDAwMDAgbiAKMDAwMDA0MDg5NyAwMDAw
MCBuIAowMDAwMDM3MTI3IDAwMDAwIG4gCjAwMDAwMjMzNjcgMDAwMDAgbiAKMDAwMDAyNDE5MSAw
MDAwMCBuIAowMDAwMDQwOTI4IDAwMDAwIG4gCjAwMDAwNDA5NTkgMDAwMDAgbiAKMDAwMDAzNzI5
MyAwMDAwMCBuIAowMDAwMDI0MjEyIDAwMDAwIG4gCjAwMDAwMjUwNjYgMDAwMDAgbiAKMDAwMDA0
MDk5MCAwMDAwMCBuIAowMDAwMDQxMDIxIDAwMDAwIG4gCjAwMDAwMzc0NTkgMDAwMDAgbiAKMDAw
MDAyNTA4NyAwMDAwMCBuIAowMDAwMDI1NjY4IDAwMDAwIG4gCjAwMDAwNDEwNTIgMDAwMDAgbiAK
MDAwMDA0MTA4MyAwMDAwMCBuIAowMDAwMDM3NjI1IDAwMDAwIG4gCjAwMDAwMjU2ODkgMDAwMDAg
biAKMDAwMDAyNjI0NiAwMDAwMCBuIAowMDAwMDQxMTE0IDAwMDAwIG4gCjAwMDAwNDExNDUgMDAw
MDAgbiAKMDAwMDAzNzc5MSAwMDAwMCBuIAowMDAwMDI2MjY3IDAwMDAwIG4gCjAwMDAwMjY4ODkg
MDAwMDAgbiAKMDAwMDA0MTE3NiAwMDAwMCBuIAowMDAwMDQxMjA3IDAwMDAwIG4gCjAwMDAwMzc5
NTcgMDAwMDAgbiAKMDAwMDAyNjkxMCAwMDAwMCBuIAowMDAwMDI3ODQ1IDAwMDAwIG4gCjAwMDAw
NDEyMzggMDAwMDAgbiAKMDAwMDA0MTI2OSAwMDAwMCBuIAowMDAwMDM4MTIzIDAwMDAwIG4gCjAw
MDAwMjc4NjYgMDAwMDAgbiAKMDAwMDAyODg0NCAwMDAwMCBuIAowMDAwMDQxMzAwIDAwMDAwIG4g
CjAwMDAwNDEzMzEgMDAwMDAgbiAKMDAwMDAzODI4OSAwMDAwMCBuIAowMDAwMDI4ODY1IDAwMDAw
IG4gCjAwMDAwMjk3MDIgMDAwMDAgbiAKMDAwMDA0MTM2MiAwMDAwMCBuIAowMDAwMDQxMzkzIDAw
MDAwIG4gCjAwMDAwMzg0NTUgMDAwMDAgbiAKMDAwMDAyOTcyMyAwMDAwMCBuIAowMDAwMDMwNzkx
IDAwMDAwIG4gCjAwMDAwNDE0MjQgMDAwMDAgbiAKMDAwMDA0MTQ1NSAwMDAwMCBuIAowMDAwMDM4
NjIxIDAwMDAwIG4gCjAwMDAwMzA4MTIgMDAwMDAgbiAKMDAwMDAzMTg5NiAwMDAwMCBuIAowMDAw
MDQxNDg2IDAwMDAwIG4gCjAwMDAwNDE1MTcgMDAwMDAgbiAKMDAwMDAzODc4NyAwMDAwMCBuIAow
MDAwMDMxOTE4IDAwMDAwIG4gCjAwMDAwMzI4MzIgMDAwMDAgbiAKMDAwMDA0MTU0OCAwMDAwMCBu
IAowMDAwMDQxNTc5IDAwMDAwIG4gCjAwMDAwMzg5NTMgMDAwMDAgbiAKMDAwMDAzMjg1MyAwMDAw
MCBuIAowMDAwMDMzMzY2IDAwMDAwIG4gCjAwMDAwNDE2MTAgMDAwMDAgbiAKMDAwMDA0MTY0MSAw
MDAwMCBuIAowMDAwMDQxNzM0IDAwMDAwIG4gCnRyYWlsZXIKPDwgL1NpemUgMTgyIC9Sb290IDEg
MCBSIC9JbmZvIDIgMCBSCi9JRCBbPDFBNzdFMEM3MkU5ODFGMzMxRjEwMUFFMUQ3M0MxMDdGPjwx
QTc3RTBDNzJFOTgxRjMzMUYxMDFBRTFENzNDMTA3Rj5dCj4+CnN0YXJ0eHJlZgo0MzM0NQolJUVP
Rgo=

------=_NextPart_000_0007_01CE27EA.38939670
Content-Type: text/plain;
	name="draft-ietf-mile-sci-07.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-mile-sci-07.txt"

=0A=
=0A=
=0A=
=0A=
MILE Working Group                                          T. Takahashi=0A=
Internet-Draft                                                      NICT=0A=
Intended status: Standards Track                            K. Landfield=0A=
                                                                  McAfee=0A=
                                                               T. Millar=0A=
                                                                  USCERT=0A=
                                                          Y. Kadobayashi=0A=
                                                                   NAIST=0A=
                                                            Feb 12, 2013=0A=
=0A=
=0A=
        IODEF-extension for structured cybersecurity information=0A=
                       draft-ietf-mile-sci-06.txt=0A=
=0A=
Abstract=0A=
=0A=
   This document extends the Incident Object Description Exchange Format=0A=
   (IODEF) defined in RFC 5070 [RFC5070] to exchange enriched=0A=
   cybersecurity information among cybersecurity entities and facilitate=0A=
   their operations.  It provides the capability of embedding structured=0A=
   information, such as identifier- and XML-based information.=0A=
=0A=
Status of This Memo=0A=
=0A=
   This Internet-Draft is submitted in full conformance with the=0A=
   provisions of BCP 78 and BCP 79.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF).  Note that other groups may also distribute=0A=
   working documents as Internet-Drafts.  The list of current Internet-=0A=
   Drafts is at http://datatracker.ietf.org/drafts/current/.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six months=0A=
   and may be updated, replaced, or obsoleted by other documents at any=0A=
   time.  It is inappropriate to use Internet-Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
Copyright Notice=0A=
=0A=
   Copyright (c) 2013 IETF Trust and the persons identified as the=0A=
   document authors.  All rights reserved.=0A=
=0A=
   This document is subject to BCP 78 and the IETF Trust's Legal=0A=
   Provisions Relating to IETF Documents=0A=
   (http://trustee.ietf.org/license-info) in effect on the date of=0A=
   publication of this document.  Please review these documents=0A=
   carefully, as they describe your rights and restrictions with respect=0A=
   to this document.  Code Components extracted from this document must=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 1]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   include Simplified BSD License text as described in Section 4.e of=0A=
   the Trust Legal Provisions and are provided without warranty as=0A=
   described in the Simplified BSD License.=0A=
=0A=
Table of Contents=0A=
=0A=
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2=0A=
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3=0A=
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3=0A=
   4.  Extension Definition  . . . . . . . . . . . . . . . . . . . .   4=0A=
     4.1.  IANA Table for Structured Cybersecurity Information . . .   4=0A=
     4.2.  Extended Data Type: XMLDATA . . . . . . . . . . . . . . .   5=0A=
     4.3.  Extended Classes  . . . . . . . . . . . . . . . . . . . .   5=0A=
       4.3.1.  AttackPattern . . . . . . . . . . . . . . . . . . . .   6=0A=
       4.3.2.  Platform  . . . . . . . . . . . . . . . . . . . . . .   7=0A=
       4.3.3.  Vulnerability . . . . . . . . . . . . . . . . . . . .   8=0A=
       4.3.4.  Scoring . . . . . . . . . . . . . . . . . . . . . . .  10=0A=
       4.3.5.  Weakness  . . . . . . . . . . . . . . . . . . . . . .  10=0A=
       4.3.6.  EventReport . . . . . . . . . . . . . . . . . . . . .  12=0A=
       4.3.7.  Verifcation . . . . . . . . . . . . . . . . . . . . .  13=0A=
       4.3.8.  Remediation . . . . . . . . . . . . . . . . . . . . .  14=0A=
   5.  Mandatory to Implement features . . . . . . . . . . . . . . .  15=0A=
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  15=0A=
     6.1.  Transport-Specific Concerns . . . . . . . . . . . . . . .  15=0A=
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16=0A=
   8.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .  17=0A=
   9.  Appendix I: XML Schema Definition for Extension . . . . . . .  18=0A=
   10. Appendix II: An XML for Checking Implementation's MTI=0A=
       conformity  . . . . . . . . . . . . . . . . . . . . . . . . .  22=0A=
   11. Appendix III: Candidate Specifications for the IANA Table . .  25=0A=
   12. Appendix IV: Another XML Example  . . . . . . . . . . . . . .  29=0A=
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  32=0A=
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  32=0A=
     13.2.  Informative References . . . . . . . . . . . . . . . . .  33=0A=
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  34=0A=
=0A=
1.  Introduction=0A=
=0A=
   The number of cyber attacks is growing day by day, and incident=0A=
   information needs to be reported, exchanged, and shared among=0A=
   organizations in order to cope with the situation.  IODEF is one of=0A=
   the tools enabling such exchange, and is already in use.=0A=
=0A=
   To efficiently run cybersecurity operations, these exchanged=0A=
   information needs to be machine-readable.  IODEF provides a=0A=
   structured means to describe the information, but it needs to embed=0A=
   various non-structured such information in order to convey detailed=0A=
   information.  Further structure within IODEF increases IODEF=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 2]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   documents' machine-readability and thus facilitates streamlining=0A=
   cybersecurity operations.=0A=
=0A=
   On the other hand, there exist various other activities facilitating=0A=
   detailed and structured description of cybersecurity information, as=0A=
   listed in Section 11 . Since such structured description facilitates=0A=
   cybersecurity operations, it would be beneficial to embed and convey=0A=
   these information inside IODEF document.=0A=
=0A=
   To enable that, this document extends the IODEF to embed and convey=0A=
   various structured cybersecurity information, with which=0A=
   cybersecurity operations can be facilitated.  Since IODEF defines a=0A=
   flexible and extensible format and supports a granular level of=0A=
   specificity, this document defines an extension to IODEF instead of=0A=
   defining a new report format.  For clarity, and to eliminate=0A=
   duplication, only the additional structures necessary for describing=0A=
   the exchange of such structured information are provided.=0A=
=0A=
2.  Terminology=0A=
=0A=
   The terminology used in this document follows the one defined in RFC=0A=
   5070 [RFC5070] .=0A=
=0A=
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=0A=
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this=0A=
   document are to be interpreted as described in RFC 2119 [RFC2119] .=0A=
=0A=
3.  Applicability=0A=
=0A=
   To maintain cybersecurity, organization needs to exchange=0A=
   cybersecurity information, which includes the following information:=0A=
   attack pattern, platform information, vulnerability and weakness,=0A=
   countermeasure instruction, computer event log, and the severity.=0A=
=0A=
   IODEF provides a scheme to describe and exchange such information=0A=
   among interested parties.  However, it does not define the detailed=0A=
   format to describe such information.=0A=
=0A=
   On the other hand, there already exist structured and detailed=0A=
   formats for describing those information and facilitating such=0A=
   exchange.  Major of them are listed in Section 11 . By embedding them=0A=
   into the IODEF document, the document can convey more detailed=0A=
   contents to the receivers, and the document can be easily reused.=0A=
=0A=
   These structured cybersecurity information facilitates cybersecurity=0A=
   operation at the receiver side.  Since the information is machine-=0A=
   readable, the data can be processed by computers.  That expedites the=0A=
   automation of cybersecurity operations=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 3]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   For instance, an organization wishing to report a security incident=0A=
   wants to describe what vulnerability was exploited.  Then the sender=0A=
   can simply use IODEF, where an XML [XML1.0] -based attack pattern=0A=
   record that follows the syntax and vocabulary defined by an industry=0A=
   specification is embedded instead of describing everything in free=0A=
   format text.  Receiver can identify the needed details of the attack=0A=
   pattern by looking up some of the XML tags defined by the=0A=
   specification.  Receiver can accumulate the attack pattern record in=0A=
   its database and could distribute it to the interested parties if=0A=
   needed, without needing human interventions.=0A=
=0A=
   Another example is that, when an administrator wishes to check the=0A=
   configuration of host computers in his organization, he may send a=0A=
   query to host computers, which may automatically generate XML-based=0A=
   software configuration information upon receiving thequery by running=0A=
   a software and may embed that to an IODEF document, which is then=0A=
   sent back to the administrator.=0A=
=0A=
4.  Extension Definition=0A=
=0A=
   This draft extends IODEF to embed structured cybersecurity=0A=
   information by introducing new classes, with which these information=0A=
   can be embedded inside IODEF document as element contents of=0A=
   AdditionalData and RecordItem classes.=0A=
=0A=
4.1.  IANA Table for Structured Cybersecurity Information=0A=
=0A=
   This extension embeds structured cybersecurity information defined by=0A=
   the other specifications.  The list of supported specifications is=0A=
   managed by IANA, and this draft defines the needed field for the=0A=
   list's entry.=0A=
=0A=
   Each entry has namespace [XMLNames] , specification name, version,=0A=
   reference URI, and applicable classes for each specification.=0A=
   Arbitrary URIs that may help readers to understand the specification=0A=
   could be embedded inside the Reference URI field, but it is=0A=
   recommended that standard/informational URI describing the=0A=
   specification is prepared and is embedded here.=0A=
=0A=
   The initial IANA table has only one entry, as below.=0A=
=0A=
=0A=
     Namespace:          http://xml/metadataSharing.xsd=0A=
     Specification Name: Malware Metadata Exchange Format=0A=
     Version:            1.2=0A=
     Reference URI:      http://standards.ieee.org/develop/=0A=
                         indconn/icsg/mmdef.html=0A=
     Applicable Classes: AttackPattern=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 4]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   The table is to be managed by IANA using the Expert Review [RFC5226]=0A=
   and Specification Required [RFC5226] allocation policies as further=0A=
   specified in Section 7 .=0A=
=0A=
   The SpecID attributes of extended classes (Section 4.3) must allow=0A=
   the values of the specifications' namespace fields, but otherwise,=0A=
   implementations are not required to support all specifications of the=0A=
   IANA table and may choose which specifications to support, though the=0A=
   specification listed in the initial table needs to be minimally=0A=
   supported, as described in Section 5 . In case an implementation=0A=
   received a data it does not support, it may expand its functionality=0A=
   by looking up the IANA table or notify the sender of its inability to=0A=
   parse the data by using any means defined outside the scope of this=0A=
   specification.=0A=
=0A=
4.2.  Extended Data Type: XMLDATA=0A=
=0A=
   This extension inherits all of the data types defined in the IODEF=0A=
   model.  One data type is added: XMLDATA.  An embedded XML data is=0A=
   represented by the XMLDATA data type.  This type is defined as the=0A=
   extension to the iodef:ExtensionType [RFC5070] , whose dtype=0A=
   attribute is set to "xml."=0A=
=0A=
4.3.  Extended Classes=0A=
=0A=
   The IODEF Incident element [RFC5070] is summarized below.  It is=0A=
   expressed in Unified Modeling Language (UML) syntax as used in the=0A=
   IODEF specification.  The UML representation is for illustrative=0A=
   purposes only; elements are specified in XML as defined in=0A=
   Appendix A.=0A=
=0A=
=0A=
   +--------------------+=0A=
   | Incident           |=0A=
   +--------------------+=0A=
   | ENUM purpose       |<>---------[IncidentID]=0A=
   | STRING ext-purpose |<>--{0..1}-[AlternativeID]=0A=
   | ENUM lang          |<>--{0..1}-[RelatedActivity]=0A=
   | ENUM restriction   |<>--{0..1}-[DetectTime]=0A=
   |                    |<>--{0..1}-[StartTime]=0A=
   |                    |<>--{0..1}-[EndTime]=0A=
   |                    |<>---------[ReportTime]=0A=
   |                    |<>--{0..*}-[Description]=0A=
   |                    |<>--{1..*}-[Assessment]=0A=
   |                    |<>--{0..*}-[Method]=0A=
   |                    |            |<>--[AdditionalData]=0A=
   |                    |                  |<>--[AttackPattern]=0A=
   |                    |                  |<>--[Vulnerability]=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 5]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   |                    |                  |<>--[Weakness]=0A=
   |                    |<>--{1..*}-[Contact]=0A=
   |                    |<>--{0..*}-[EventData]=0A=
   |                    |            |<>--[Flow]=0A=
   |                    |            |     |<>--[System]=0A=
   |                    |            |           |<>--[AdditionalData]=0A=
   |                    |            |                 |<>--[Platform]=0A=
   |                    |            |<>--[Expectation]=0A=
   |                    |            |<>--[Record]=0A=
   |                    |                  |<>--[RecordData]=0A=
   |                    |                        |<>--[RecordItem]=0A=
   |                    |                              |<>--[EventReport]=0A=
   |                    |<>--{0..1}-[History]=0A=
   |                    |<>--{0..*}-[AdditionalData]=0A=
   |                    |            |<>--[Verification]=0A=
   |                    |            |<>--[Remediation]=0A=
   +--------------------+=0A=
=0A=
=0A=
                         Figure 1: Incident class=0A=
=0A=
   This extension defines the following seven elements.=0A=
=0A=
4.3.1.  AttackPattern=0A=
=0A=
   An AttackPattern consists of an extension to the=0A=
   Incident.Method.AdditionalData element with a dtype of "xml".  The=0A=
   extension describes attack patterns of incidents or events.=0A=
=0A=
   It is recommended that Method class SHOULD contain one or more of the=0A=
   extension elements whenever available.=0A=
=0A=
   An AttackPattern class is structured as follows.=0A=
=0A=
=0A=
   +------------------------+=0A=
   | AttackPattern          |=0A=
   +------------------------+=0A=
   | ENUM SpecID            |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID      |<>--(0..*)-[ Reference ]=0A=
   | STRING AttackPatternID |<>--(0..*)-[ Platform ]=0A=
   +------------------------+=0A=
=0A=
=0A=
                       Figure 2: AttackPattern class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 6]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  A specification's identifier that=0A=
      specifies the format of a structured cybersecurity information.=0A=
      The value should be chosen from the namespaces [XMLNames] listed=0A=
      in the IANA table (Section 4.1) or "private".  The value "private"=0A=
      is prepared for conveying RawData based on a format that is not=0A=
      listed in the table.  This is usually used for conveying data=0A=
      formatted according to an organization's private schema.  When the=0A=
      value "private" is used, ext-SpecID element MUST be used.=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  A specification's identifier that=0A=
      specifies the format of a structured cybersecurity information.=0A=
      When this element is used, the value of SpecID element must be=0A=
      "private."=0A=
=0A=
   AttackPatternID:  OPTIONAL.  STRING.  An identifier of an attack=0A=
      pattern to be reported.  This attribute SHOULD be used whenever=0A=
      such identifier is available.  Both RawData and Reference elements=0A=
      MUST NOT be used when this attribute is used, while either of them=0A=
      MUST be used if this attribute is omitted.=0A=
=0A=
   The AttackPattern class is composed of the following aggregate=0A=
   classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  A complete document that is=0A=
      formatted according to the specification and its version=0A=
      identified by the SpecID/ext-SpecID.  When this element is used,=0A=
      writers/senders MUST ensure that the namespace specified by SpecID=0A=
      /ext-SpecID and the one used in the RawData element are=0A=
      consistent; if not, the namespace identified by SpecID SHOULD be=0A=
      prefered, and the inconsistency SHOULD be logged so a human can=0A=
      correct the problem.=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  This element=0A=
      allows an IODEF document to include a link to a structured=0A=
      information instead of directly embedding it into a RawData=0A=
      element.=0A=
=0A=
   Platform:  Zero or more.  An identifier of software platform involved=0A=
      in the specific attack pattern, which is elaborated in=0A=
      Section 4.3.2 .=0A=
=0A=
4.3.2.  Platform=0A=
=0A=
   A Platform identifies a software platform.  It is recommended that=0A=
   AttackPattern, Vulnerability, Weakness, and System classes contain=0A=
   this elements whenever available.=0A=
=0A=
   A Platform element is structured as follows.=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 7]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   +----------------------+=0A=
   | Platform             |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID    |<>--(0..*)-[ Reference ]=0A=
   | STRING PlatformID    |=0A=
   +----------------------+=0A=
=0A=
=0A=
                         Figure 3: Platform class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   PlatformID:  OPTIONAL.  STRING.  An identifier of a platform to be=0A=
      reported.  This attribute SHOULD be used whenever such identifier=0A=
      is available.  Both RawData and Reference elements MUST NOT be=0A=
      used when this attribute is used, while either of them MUST be=0A=
      used if this attribute is omitted.=0A=
=0A=
   This class is composed of the following aggregate classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
4.3.3.  Vulnerability=0A=
=0A=
   A Vulnerability consists of an extension to the=0A=
   Incident.Method.AdditionalData element with a dtype of "xml".  The=0A=
   extension describes the (candidate) vulnerabilities of incidents or=0A=
   events.=0A=
=0A=
   It is recommended that Method class SHOULD contain one or more of the=0A=
   extension elements whenever available.=0A=
=0A=
   A Vulnerability element is structured as follows.=0A=
=0A=
=0A=
   +------------------------+=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 8]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   | Vulnerability          |=0A=
   +------------------------+=0A=
   | ENUM SpecID            |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID      |<>--(0..*)-[ Reference ]=0A=
   | STRING VulnerabilityID |<>--(0..*)-[ Platform ]=0A=
   |                        |<>--(0..*)-[ Scoring ]=0A=
   +------------------------+=0A=
=0A=
=0A=
                       Figure 4: Vulnerability class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   VulnerabilityID:  OPTIONAL.  STRING.  An identifier of a=0A=
      vulnerability to be reported.  This attribute SHOULD be used=0A=
      whenever such identifier is available.  Both RawData and Reference=0A=
      elements MUST NOT be used when this attribute is used, while=0A=
      either of them MUST be used if this attribute is omitted.=0A=
=0A=
   This class is composed of the following aggregate classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
   Platform:  Zero or more.  An identifier of software platform affected=0A=
      by the vulnerability, which is elaborated in Section 4.3.2 .=0A=
=0A=
   Scoring:  Zero or more.  An indicator of the severity of the=0A=
      vulnerability, such as CVSS and CCSS scores, which is elaborated=0A=
      in Section 4.3.4 . Some of the structured information may include=0A=
      scores within it.  In this case, the Scoring element SHOULD NOT be=0A=
      used since the RawData element contains the scores.  If a reader/=0A=
      receiver detects scores in both RawData and Scoring elements and=0A=
      their inconsistency, it SHOULD prefer the scores derived from the=0A=
      RawData element, and SHOULD log the inconsistency so a human can=0A=
      correct the problem.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                         [Page 9]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
4.3.4.  Scoring=0A=
=0A=
   A Scoring class describes the scores of the severity in terms of=0A=
   security.  It is recommended that Vulnerability and Weakness classes=0A=
   contain the elements whenever available.=0A=
=0A=
   A Scoring class is structured as follows.=0A=
=0A=
=0A=
   +----------------------+=0A=
   | Scoring              |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>---------[ ScoreSet ]=0A=
   | STRING ext-SpecID    |=0A=
   +----------------------+=0A=
=0A=
=0A=
                          Figure 5: Scoring class=0A=
=0A=
   This class has two attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   This class is composed of an aggregate class.=0A=
=0A=
   ScoreSet:  One.  XMLDATA.  A complete document that is formatted=0A=
      according to the specification and its version identified by the=0A=
      SpecID/ext-SpecID.  This element includes a set of score=0A=
      information.  When this element is used, writers/senders MUST=0A=
      ensure that the namespace specified by SpecID/ext-SpecID and the=0A=
      one used in the RawData element are consistent; if not, the=0A=
      namespace identified by SpecID SHOULD be prefered, and the=0A=
      inconsistency SHOULD be logged so a human can correct the problem.=0A=
=0A=
   Writers/senders MUST ensure the specification name and version=0A=
   identified by the SpecID are consistent with the contents of the=0A=
   Score; if a reader/receiver detects an inconsistency, it SHOULD=0A=
   prefer the specification name and version derived from the content,=0A=
   and SHOULD log the inconsistency so a human can correct the problem.=0A=
=0A=
4.3.5.  Weakness=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 10]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   A Weakness consists of an extension to the=0A=
   Incident.Method.AdditionalData element with a dtype of "xml".  The=0A=
   extension describes the weakness types of incidents or events.=0A=
=0A=
   It is recommended that Method class SHOULD contain one or more of the=0A=
   extension elements whenever available.=0A=
=0A=
   A Weakness element is structured as follows.=0A=
=0A=
=0A=
   +----------------------+=0A=
   | Weakness             |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID    |<>--(0..*)-[ Reference ]=0A=
   | STRING WeaknessID    |<>--(0..*)-[ Platform ]=0A=
   |                      |<>--(0..*)-[ Scoring ]=0A=
   +----------------------+=0A=
=0A=
=0A=
                         Figure 6: Weakness class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   WeaknessID:  OPTIONAL.  STRING.  An identifier of a weakness to be=0A=
      reported.  This attribute SHOULD be used whenever such identifier=0A=
      is available/ Both RawData and Reference elements MUST NOT be used=0A=
      when this attribute is used, while either of them MUST be used if=0A=
      this attribute is omitted.=0A=
=0A=
   This class is composed of the following aggregate classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
   Platform:  Zero or more.  An identifier of software platform affected=0A=
      by the weakness, which is elaborated in Section 4.3.2 .=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 11]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   Scoring:  Zero or more.  An indicator of the severity of the=0A=
      weakness, such as CWSS score, which is elaborated in Section 4.3.4=0A=
      .=0A=
=0A=
4.3.6.  EventReport=0A=
=0A=
   An EventReport consists of an extension to the=0A=
   Incident.EventData.Record.RecordData.RecordItem element with a dtype=0A=
   of "xml".  The extension embeds structured event reports.=0A=
=0A=
   It is recommended that RecordItem class SHOULD contain one or more of=0A=
   the extension elements whenever available.=0A=
=0A=
   An EventReport element is structured as follows.=0A=
=0A=
=0A=
   +----------------------+=0A=
   | EventReport          |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID    |<>--(0..*)-[ Reference ]=0A=
   | STRING EventID       |=0A=
   +----------------------+=0A=
=0A=
=0A=
                        Figure 7: EventReport class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   EventID:  OPTIONAL.  STRING.  An identifier of an event to be=0A=
      reported.  This attribute SHOULD be used whenever such identifier=0A=
      is available.  Both RawData and Reference elements MUST NOT be=0A=
      used when this attribute is used, while either of them MUST be=0A=
      used if this attribute is omitted.=0A=
=0A=
   This class is composed of three aggregate classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 12]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
   This class MUST contain at least one of RawData or Reference=0A=
   elements.  Writers/senders MUST ensure the specification name and=0A=
   version identified by the SpecID are consistent with the contents of=0A=
   the RawData; if a reader/receiver detects an inconsistency, it SHOULD=0A=
   prefer the specification name and version derived from the content,=0A=
   and SHOULD log the inconsistency so a human can correct the problem.=0A=
=0A=
4.3.7.  Verifcation=0A=
=0A=
   A Verification consists of an extension to the=0A=
   Incident.AdditionalData element with a dtype of "xml".  The extension=0A=
   elements describes incident on vefifying incidents.=0A=
=0A=
   A Verification class is structured as follows.=0A=
=0A=
=0A=
   +----------------------+=0A=
   | Verification         |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID    |<>--(0..*)-[ Reference ]=0A=
   | STRING VerificationID|=0A=
   +----------------------+=0A=
=0A=
=0A=
                       Figure 8: Verification class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   VerificationID:  OPTIONAL.  STRING.  An identifier of an check item=0A=
      to be reported.  This attribute SHOULD be used whenever such=0A=
      identifier is available.  Both RawData and Reference elements MUST=0A=
      NOT be used when this attribute is used, while either of them MUST=0A=
      be used if this attribute is omitted.=0A=
=0A=
   This class is composed of two aggregate classes.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 13]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
   This class MUST contain at least either of RawData and Reference=0A=
   elements.  Writers/senders MUST ensure the specification name and=0A=
   version identified by the SpecID are consistent with the contents of=0A=
   the RawData; if a reader/receiver detects an inconsistency, it SHOULD=0A=
   prefer the specification name and version derived from the content,=0A=
   and SHOULD log the inconsistency so a human can correct the problem.=0A=
=0A=
4.3.8.  Remediation=0A=
=0A=
   A Remediation consists of an extension to the Incident.AdditionalData=0A=
   element with a dtype of "xml".  The extension elements describes=0A=
   incident remediation information including instructions.=0A=
=0A=
   It is recommended that Incident class SHOULD contain one or more of=0A=
   this extension elements whenever available.=0A=
=0A=
   A Remediation class is structured as follows.=0A=
=0A=
=0A=
   +----------------------+=0A=
   | Remediation          |=0A=
   +----------------------+=0A=
   | ENUM SpecID          |<>--(0..*)-[ RawData ]=0A=
   | STRING ext-SpecID    |<>--(0..*)-[ Reference ]=0A=
   | String RemediationID |=0A=
   +----------------------+=0A=
=0A=
=0A=
                        Figure 9: Remediation class=0A=
=0A=
   This class has the following attributes.=0A=
=0A=
   SpecID:  REQUIRED.  ENUM.  The meaning of this attribute is the same=0A=
      as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   ext-SpecID:  OPTIONAL.  STRING.  The meaning of this attribute is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   RemediationID:  OPTIONAL.  STRING.  An identifier of a remediation=0A=
      information to be reported.  This attribute SHOULD be used=0A=
      whenever such identifier is available.  Both RawData and Reference=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 14]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
      elements MUST NOT be used when this attribute is used, while=0A=
      either of them MUST be used if this attribute is omitted.=0A=
=0A=
   This class is composed of two aggregate classes.=0A=
=0A=
   RawData:  Zero or more.  XMLDATA.  The meaning of this element is the=0A=
      same as that of the AttackPattern class (Section 4.3.1) .=0A=
=0A=
   Reference:  Zero or more of iodef:Reference [RFC5070] .  The meaning=0A=
      of this element is the same as that of the AttackPattern class=0A=
      (Section 4.3.1) .=0A=
=0A=
   This class MUST contain at least either of RawData and Reference=0A=
   elements.  Writers/senders MUST ensure the specification name and=0A=
   version identified by the SpecID are consistent with the contents of=0A=
   the RawData; if a reader/receiver detects an inconsistency, it SHOULD=0A=
   prefer the specification name and version derived from the content,=0A=
   and SHOULD log the inconsistency so a human can correct the problem.=0A=
=0A=
5.  Mandatory to Implement features=0A=
=0A=
   The implementation of this draft MUST be capable of sending and=0A=
   receiving the XML conforming to the specification listed in the=0A=
   initial IANA table described in Section 4.1 without error.=0A=
=0A=
   The receiver MUST be capable of validating received XML documents=0A=
   that are embedeed inside that against their schemata.  Note that the=0A=
   receiver can look up the namespace in the IANA table to understand=0A=
   what specifications the embedded XML documents follows.=0A=
=0A=
6.  Security Considerations=0A=
=0A=
   This document specifies a format for encoding a particular class of=0A=
   security incidents appropriate for exchange across organizations.  As=0A=
   merely a data representation, it does not directly introduce security=0A=
   issues.  However, it is guaranteed that parties exchanging instances=0A=
   of this specification will have certain concerns.  For this reason,=0A=
   the underlying message format and transport protocol used MUST ensure=0A=
   the appropriate degree of confidentiality, integrity, and=0A=
   authenticity for the specific environment.=0A=
=0A=
   Organizations that exchange data using this document are URGED to=0A=
   develop operating procedures that document the following areas of=0A=
   concern.=0A=
=0A=
6.1.  Transport-Specific Concerns=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 15]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   The underlying messaging format and protocol used to exchange=0A=
   instances of the IODEF MUST provide appropriate guarantees of=0A=
   confidentiality, integrity, and authenticity.  The use of a=0A=
   standardized security protocol is encouraged.  The Real-time Inter-=0A=
   network Defense (RID) protocol [RFC6045] and its associated transport=0A=
   binding [RFC6046] provide such security.=0A=
=0A=
   The critical security concerns are that these structured information=0A=
   may be falsified or they may become corrupt during transit.  In areas=0A=
   where transmission security or secrecy is questionable, the=0A=
   application of a digital signature and/or message encryption on each=0A=
   report will counteract both of these concerns.  We expect that each=0A=
   exchanging organization will determine the need, and mechanism, for=0A=
   transport protection.=0A=
=0A=
7.  IANA Considerations=0A=
=0A=
   This document uses URNs to describe XML namespaces and XML schemata=0A=
   [XMLschemaPart1] [XMLschemaPart2] conforming to a registry mechanism=0A=
   described in [RFC3688] .=0A=
=0A=
   Registration request for the IODEF structured cybersecurity=0A=
   information extension namespace:=0A=
=0A=
      URI: urn:ietf:params:xml:ns:iodef-sci-1.0=0A=
=0A=
      Registrant Contact: Refer here to the authors' addresses section=0A=
      of the document.=0A=
=0A=
      XML: None=0A=
=0A=
   Registration request for the IODEF structured cybersecurity=0A=
   information extension XML schema:=0A=
=0A=
      URI: urn:ietf:params:xml:schema:iodef-sci-1.0=0A=
=0A=
      Registrant Contact: Refer here to the authors' addresses section=0A=
      of the document.=0A=
=0A=
      XML: Refer here to the XML Schema in the appendix of the document.=0A=
=0A=
   This memo creates the following registry for IANA to manage:=0A=
=0A=
      Name of the registry: "IODEF Structured Cyber Security Information=0A=
      Specifications"=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 16]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
      Namespace details: A registry entry for a Structured Cyber=0A=
      Security Information Specification (SCI specification) consists=0A=
      of:=0A=
=0A=
         Namespace: A URI [RFC3986] that is the XML namespace name used=0A=
         by the registered SCI specification.=0A=
=0A=
         Specification Name: A string containing the spelled-out name of=0A=
         the SCI specification in human-readable form.=0A=
=0A=
         Reference URI: A list of one or more of the URIs [RFC3986] from=0A=
         which the registered specification can be obtained.  The=0A=
         registered specification MUST be readily and publicly available=0A=
         from that URI.=0A=
=0A=
         Applicable Classes: A list of one or more of the Extended=0A=
         Classes specified in Section 4.3 of this document.  The=0A=
         registered SCI specification MUST only be used with the=0A=
         Extended Classes in the registry entry.=0A=
=0A=
      Information that must be provided to assign a new value: The above=0A=
      list of information.=0A=
=0A=
      Fields to record in the registry: Namespace/Specification Name/=0A=
      Version/Applicable Classes.=0A=
=0A=
      Initial registry contents: none=0A=
=0A=
      Allocation Policy: Expert Review [RFC5226] and Specification=0A=
      Required [RFC5226] .=0A=
=0A=
   The Designated Expert is expected to consult with the mile (Managed=0A=
   Incident Lightweight Exchange) working group or its successor if any=0A=
   such WG exists (e.g., via email to the working group's mailing list).=0A=
   The Designated Expert is expected to retrieve the SCI specification=0A=
   from the provided URI in order to check the public availability of=0A=
   the specification and verify the correctness of the URI.  An=0A=
   important responsibility of the Designated Expert is to ensure that=0A=
   the registered Applicable Classes are appropriate for the registered=0A=
   SCI specification.=0A=
=0A=
8.  Acknowledgment=0A=
=0A=
   We would like to acknowledge Mr.  David Black from EMC, who kindly=0A=
   provided generous support, especially on the IANA registry issues.=0A=
   We also would like to thank Jon Baker from MITRE, Paul Cichonski from=0A=
   NIST, Panos Kampanakis from CISCO, Robert Martin from MITRE, Kathleen=0A=
   Moriarty from EMC, Lagadec Philippe from NATO, Shuhei Yamaguchi from=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 17]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   NICT, Anthony Rutkowski from Yaana Technology, Brian Trammel from=0A=
   CERT/NetSA, and David Waltermire from NIST for their sincere=0A=
   discussion and feedback on this document.=0A=
=0A=
9.  Appendix I: XML Schema Definition for Extension=0A=
=0A=
   The XML Schema describing the elements defined in the Extension=0A=
   Definition section is given here.  Each of the examples in Section 12=0A=
   should be verified to validate against this schema by automated=0A=
   tools.=0A=
=0A=
=0A=
   <?xml version=3D"1.0" encoding=3D"UTF-8"?>=0A=
=0A=
   <xsd:schema targetNamespace=3D"urn:ietf:params:xml:ns:iodef-sci-1.0"=0A=
    xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"=0A=
    xmlns:iodef=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
    xmlns:iodef-sci=3D"urn:ietf:params:xml:ns:iodef-sci-1.0"=0A=
    elementFormDefault=3D"qualified" =
attributeFormDefault=3D"unqualified">=0A=
=0A=
   <xsd:import namespace=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
    schemaLocation=3D"iodef_schema.xsd"/>=0A=
=0A=
   <!--=0A=
    schemaLocation=3D"urn:ietf:params:xml:schema:iodef-1.0"/>=0A=
   -->=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D XMLDATA                                                        =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
   <xsd:complexType name=3D"XMLDATA">=0A=
     <xsd:complexContent>=0A=
       <xsd:restriction base=3D"iodef:ExtensionType">=0A=
         <xsd:sequence>=0A=
           <xsd:any namespace=3D"##any" processContents=3D"lax" =
minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"dtype" type=3D"iodef:dtype-type" =
use=3D"required" fixed=3D"xml"/>=0A=
         <xsd:attribute name=3D"ext-dtype" type=3D"xsd:string" =
use=3D"optional"/>=0A=
         <xsd:attribute name=3D"meaning" type=3D"xsd:string"/>=0A=
         <xsd:attribute name=3D"formatid" type=3D"xsd:string"/>=0A=
         <xsd:attribute name=3D"restriction" =
type=3D"iodef:restriction-type"/>=0A=
       </xsd:restriction>=0A=
     </xsd:complexContent>=0A=
   </xsd:complexType>=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 18]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Scoring Class                                                  =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"Scoring">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:element name=3D"ScoreSet" type=3D"iodef-sci:XMLDATA"=0A=
            minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D AttackPattern Class                                            =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"AttackPattern">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"=0A=
              minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0A=
             <xsd:element ref=3D"iodef:Reference" minOccurs=3D"0"=0A=
              maxOccurs=3D"unbounded"/>=0A=
           </xsd:choice>=0A=
           <xsd:element ref=3D"iodef-sci:Platform" minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"AttackPatternID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Vulnerability Class                                            =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"Vulnerability">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 19]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"=0A=
              minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0A=
             <xsd:element ref=3D"iodef:Reference" minOccurs=3D"0"=0A=
              maxOccurs=3D"unbounded"/>=0A=
           </xsd:choice>=0A=
           <xsd:element ref=3D"iodef-sci:Platform" minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
           <xsd:element ref=3D"iodef-sci:Scoring" minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"VulnerabilityID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Weakness Class                                                 =
 =3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"Weakness">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"=0A=
              minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0A=
             <xsd:element ref=3D"iodef:Reference" minOccurs=3D"0"=0A=
              maxOccurs=3D"unbounded"/>=0A=
           </xsd:choice>=0A=
           <xsd:element ref=3D"iodef-sci:Platform" minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
           <xsd:element ref=3D"iodef-sci:Scoring" minOccurs=3D"0"=0A=
            maxOccurs=3D"unbounded"/>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"WeaknessID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Platform Class                                                =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 20]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
     <xsd:element name=3D"Platform">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"=0A=
              minOccurs=3D"0" maxOccurs=3D"unbounded"/>=0A=
             <xsd:element ref=3D"iodef:Reference" minOccurs=3D"0"=0A=
              maxOccurs=3D"unbounded"/>=0A=
           </xsd:choice>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"PlatformID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D EventReport Class                                              =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"EventReport">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"/>=0A=
             <xsd:element ref=3D"iodef:Reference"/>=0A=
           </xsd:choice>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"EventID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Verification Class                                             =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"Verification">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"/>=0A=
             <xsd:element ref=3D"iodef:Reference"/>=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 21]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
           </xsd:choice>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"VerificationID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   =
<!--=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
   =3D=3D Remediation Class                                              =
=3D=3D=0A=
   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-->=0A=
=0A=
     <xsd:element name=3D"Remediation">=0A=
       <xsd:complexType>=0A=
         <xsd:sequence>=0A=
           <xsd:choice>=0A=
             <xsd:element name=3D"RawData" type=3D"iodef-sci:XMLDATA"/>=0A=
             <xsd:element ref=3D"iodef:Reference"/>=0A=
           </xsd:choice>=0A=
         </xsd:sequence>=0A=
         <xsd:attribute name=3D"SpecID" type=3D"xsd:string" =
use=3D"required"/>=0A=
         <xsd:attribute name=3D"ext-SpecID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
         <xsd:attribute name=3D"RemediationID" type=3D"xsd:string"=0A=
          use=3D"optional"/>=0A=
       </xsd:complexType>=0A=
     </xsd:element>=0A=
=0A=
   </xsd:schema>=0A=
=0A=
=0A=
=0A=
10.  Appendix II: An XML for Checking Implementation's MTI conformity=0A=
=0A=
   This section provides an example XML for checking implementation's=0A=
   MTI conformity.  The XML carries MMDEF metadata inside an IODEF=0A=
   document.  Note that the metadata is generated by genMMDEF [MMDEF]=0A=
   with EICAR [EICAR] files.  Implementations of this specification must=0A=
   be capable of parsing the example XML since MMDEF is specified as the=0A=
   draft's MTI specification.=0A=
=0A=
=0A=
   <?xml version=3D"1.0" encoding=3D"UTF-8"?>=0A=
   <IODEF-Document version=3D"1.00" lang=3D"en"=0A=
    xmlns=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
    xmlns:iodef=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 22]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
    xmlns:iodef-sci=3D"urn:ietf:params:xml:ns:iodef-sci-1.0"=0A=
    xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">=0A=
     <Incident purpose=3D"reporting">=0A=
       <IncidentID name=3D"csirt.example.com">189493</IncidentID>=0A=
       <ReportTime>2013-03-13T23:19:24+00:00</ReportTime>=0A=
       <Description>Incident report in company xx</Description>=0A=
       <Assessment>=0A=
         <Impact completion=3D"failed" type=3D"admin" />=0A=
       </Assessment>=0A=
       <Method>=0A=
         <Description>An identifier of a vulnerability is embedded=0A=
         </Description>=0A=
         <AdditionalData dtype=3D"xml">=0A=
           <iodef-sci:AttackPattern =
SpecID=3D"http://xml/metadataSharing.xsd">=0A=
             <iodef-sci:RawData dtype=3D"xml">=0A=
               <malwareMetaData xmlns=3D"http://xml/metadataSharing.xsd"=0A=
                 xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"=0A=
                 xsi:schemaLocation=3D=0A=
                 "http://xml/metadataSharing.xsd =
file:metadataSharing.xsd"=0A=
                 version=3D"1.200000" id=3D"10000">=0A=
                 <company>N/A</company>=0A=
                 <author>MMDEF Generation Script</author>=0A=
                 <comment>Test MMDEF v1.2 file generated using genMMDEF=0A=
                 </comment>=0A=
                 <timestamp>2013-03-23T15:12:50.726000</timestamp>=0A=
                 <objects>=0A=
                   <file id=3D"6ce6f415d8475545be5ba114f208b0ff">=0A=
                     <md5>6ce6f415d8475545be5ba114f208b0ff</md5>=0A=
                     =
<sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>=0A=
                     =
<sha256>e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934=0A=
                             ca495991b7852b855</sha256>=0A=
                     =
<sha512>cf83e1357eefb8bdf1542850d66d8007d620e4050b5715d=0A=
                             =
c83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec=0A=
                             2f63b931bd47417a81a538327af927da3e</sha512>=0A=
                     <size>184</size>=0A=
                     <filename>eicar_com.zip</filename>=0A=
                     <MIMEType>application/zip</MIMEType>=0A=
                   </file>=0A=
                   <file id=3D"44d88612fea8a8f36de82e1278abb02f">=0A=
                     <md5>44d88612fea8a8f36de82e1278abb02f</md5>=0A=
                     =
<sha1>3395856ce81f2b7382dee72602f798b642f14140</sha1>=0A=
                     =
<sha256>275a021bbfb6489e54d471899f7db9d1663fc695ec2fe2a=0A=
                             2c4538aabf651fd0f</sha256>=0A=
                     =
<sha512>cc805d5fab1fd71a4ab352a9c533e65fb2d5b885518f4e5=0A=
                             =
65e68847223b8e6b85cb48f3afad842726d99239c9e3650=0A=
                             5c64b0dc9a061d9e507d833277ada336ab</sha512>=0A=
                     <size>68</size>=0A=
                     <crc32>1750191932</crc32>=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 23]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
                     <filename>eicar.com</filename>=0A=
                     <filenameWithinInstaller>eicar.com=0A=
                     </filenameWithinInstaller>=0A=
                   </file>=0A=
                 </objects>=0A=
                 <relationships>=0A=
                   <relationship type=3D"createdBy" id=3D"1">=0A=
                     <source>=0A=
                       =
<ref>file[@id=3D"6ce6f415d8475545be5ba114f208b0ff"]=0A=
                       </ref>=0A=
                     </source>=0A=
                     <target>=0A=
                       =
<ref>file[@id=3D"44d88612fea8a8f36de82e1278abb02f"]=0A=
                       </ref>=0A=
                     </target>=0A=
                     <timestamp>2013-03-23T15:12:50.744000</timestamp>=0A=
                   </relationship>=0A=
                 </relationships>=0A=
               </malwareMetaData>=0A=
             </iodef-sci:RawData>=0A=
           </iodef-sci:AttackPattern>=0A=
         </AdditionalData>=0A=
       </Method>=0A=
       <Contact role=3D"creator" type=3D"organization">=0A=
         <ContactName>Example.com CSIRT</ContactName>=0A=
         <RegistryHandle registry=3D"arin">example-com</RegistryHandle>=0A=
         <Email>contact@csirt.example.com</Email>=0A=
       </Contact>=0A=
       <EventData>=0A=
         <Flow>=0A=
           <System category=3D"source">=0A=
             <Node>=0A=
               <Address category=3D"ipv4-addr">192.0.2.200</Address>=0A=
               <Counter type=3D"event">57</Counter>=0A=
             </Node>=0A=
           </System>=0A=
           <System category=3D"target">=0A=
             <Node>=0A=
               <Address category=3D"ipv4-net">192.0.2.16/28</Address>=0A=
             </Node>=0A=
             <Service ip_protocol=3D"6">=0A=
               <Port>80</Port>=0A=
             </Service>=0A=
           </System>=0A=
         </Flow>=0A=
         <Expectation action=3D"block-host" />=0A=
         <Expectation action=3D"other" />=0A=
       </EventData>=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 24]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
       <History>=0A=
         <!-- Contact was previously made with the source network owner =
-->=0A=
         <HistoryItem action=3D"contact-source-site">=0A=
           <DateTime>2001-09-14T08:19:01+00:00</DateTime>=0A=
           <Description>Notification sent to=0A=
             constituency-contact@192.0.2.200=0A=
           </Description>=0A=
         </HistoryItem>=0A=
       </History>=0A=
     </Incident>=0A=
   </IODEF-Document>=0A=
=0A=
=0A=
=0A=
11.  Appendix III: Candidate Specifications for the IANA Table=0A=
=0A=
   This draft defined the structure of the IANA table in Section 4.1 .=0A=
   Though the management of the table is up to IANA, this appendix=0A=
   provides candidate entries.  Note that OVAL and CVE are registered=0A=
   trademarks, and CAPEC, CCE, CEE, CPE, CWE, CWSS, MAEC, and OCIL are=0A=
   trademarks, of The MITRE Corporation.=0A=
=0A=
   1.   CAPEC 1.6=0A=
=0A=
=0A=
     Namespace:          http://capec.mitre.org/observables=0A=
     Specification Name: Common Attack Pattern Enumeration and=0A=
                         Classification=0A=
     Version:            1.6=0A=
     Reference URI:      http://capec.mitre.org/=0A=
     Applicable Classes: AttackPattern=0A=
=0A=
=0A=
=0A=
   2.   CCE 5.0=0A=
=0A=
=0A=
     Namespace:          http://cce.mitre.org=0A=
     Specification Name: Common Configuration Enumeration=0A=
     Version:            5.0=0A=
     Reference URI:      http://cce.mitre.org/=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
   3.   CCSS 1.0=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 25]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
     Namespace:          N/A=0A=
     Specification Name: Common Configuration Scoring System=0A=
     Version:            1.0=0A=
     Reference URI:      =
http://csrc.nist.gov/publications/PubsNISTIRs.html=0A=
                         #NIST-IR-7502=0A=
     Applicable Classes: Scoring=0A=
=0A=
=0A=
=0A=
   4.   CEE 1.0 alpha=0A=
=0A=
=0A=
     Namespace:          http://cee.mitre.org=0A=
     Specification Name: Common Event Expression=0A=
     Version:            1.0 alpha=0A=
     Reference URI:      http://cee.mitre.org/=0A=
     Applicable Classes: EventReport=0A=
=0A=
=0A=
=0A=
   5.   CPE 2.3 Language=0A=
=0A=
=0A=
     Namespace:          http://cpe.mitre.org/language/2.0=0A=
     Specification Name: Common Platform Enumeration Reference=0A=
     Version:            2.3=0A=
     Reference URI:      http://scap.nist.gov/specifications/cpe/,=0A=
                         =
http://csrc.nist.gov/publications/PubsNISTIRs.html=0A=
                         #NIST-IR-7695=0A=
     Applicable Classes: Platform=0A=
=0A=
=0A=
=0A=
   6.   CPE 2.3 Dictionary=0A=
=0A=
=0A=
     Namespace:          http://cpe.mitre.org/dictionary/2.0=0A=
     Specification Name: Common Platform Enumeration Dictionary=0A=
     Version:            2.3=0A=
     Reference URI:      http://scap.nist.gov/specifications/cpe/,=0A=
                         =
http://csrc.nist.gov/publications/PubsNISTIRs.html=0A=
                         #NIST-IR-7697=0A=
     Applicable Classes: Platform=0A=
=0A=
=0A=
=0A=
   7.   CVE 1.0=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 26]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
     Namespace:          http://cve.mitre.org/cve/downloads/1.0=0A=
     Specification Name: Common Vulnerability and Exposures=0A=
     Version:            1.0=0A=
     Reference URI:      http://cve.mitre.org/=0A=
     Applicable Classes: Vulnerability=0A=
=0A=
=0A=
=0A=
   8.   CVRF 1.0=0A=
=0A=
=0A=
     Namespace:          http://www.icasi.org/CVRF/schema/cvrf/1.0=0A=
     Specification Name: Common Vulnerability Reporting Format=0A=
     Version:            1.0=0A=
     Reference URI:      http://www.icasi.org/cvrf=0A=
     Applicable Classes: Vulnerability=0A=
=0A=
=0A=
=0A=
   9.   CVSS 2.0=0A=
=0A=
=0A=
     Namespace:          http://scap.nist.gov/schema/cvss-v2/1.0=0A=
     Specification Name: Common Vulnerability Scoring System=0A=
     Version:            2=0A=
     Reference URI:      http://www.first.org/cvss=0A=
     Applicable Classes: Scoring=0A=
=0A=
=0A=
=0A=
   10.  CWE 5.0=0A=
=0A=
=0A=
     Namespace:          N/A=0A=
     Specification Name: Common Weakness Enumeration=0A=
     Version:            5.1=0A=
     Reference URI:      http://cwe.mitre.org/=0A=
     Applicable Classes: Weakness=0A=
=0A=
=0A=
=0A=
   11.  CWSS 0.8=0A=
=0A=
=0A=
     Namespace:          N/A=0A=
     Specification Name: Common Weakness Scoring System=0A=
     Version:            0.8=0A=
     Reference URI:      http://cwe.mitre.org/cwss/=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 27]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
     Applicable Classes: Scoring=0A=
=0A=
=0A=
=0A=
   12.  MAEC 2.0=0A=
=0A=
=0A=
     Namespace:          http://maec.mitre.org/XMLSchema/maec-core-2=0A=
     Specification Name: Malware Attribute Enumeration and =
Characterization=0A=
     Version:            2.0=0A=
     Reference URI:      http://maec.mitre.org/=0A=
     Applicable Classes: EventReport, AttackPattern=0A=
=0A=
=0A=
=0A=
   13.  OCIL 2.0=0A=
=0A=
=0A=
     Namespace:          http://scap.nist.gov/schema/ocil/2.0=0A=
     Specification Name: Open Checklist Interactive Language=0A=
     Version:            2.0=0A=
     Reference URI:      http://scap.nist.gov/specifications/ocil/,=0A=
                         =
http://csrc.nist.gov/publications/PubsNISTIRs.html=0A=
                         #NIST-IR-7692=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
   14.  OVAL 5.10.1 Definitions=0A=
=0A=
=0A=
     Namespace:          =
http://oval.mitre.org/XMLSchema/oval-definitions-5=0A=
     Specification Name: Open Vulnerability and Assessment Language=0A=
     Version:            5.10.1=0A=
     Reference URI:      http://oval.mitre.org/=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
   15.  OVAL 5.10.1 Results=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 28]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
     Namespace:          http://oval.mitre.org/XMLSchema/oval-results-5=0A=
     Specification Name: Open Vulnerability and Assessment Language=0A=
     Version:            5.10.1=0A=
     Reference URI:      http://oval.mitre.org/=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
   16.  OVAL 5.10.1 Common=0A=
=0A=
=0A=
     Namespace:          http://oval.mitre.org/XMLSchema/oval-common-5=0A=
     Specification Name: Open Vulnerability and Assessment Language=0A=
     Version:            5.10.1=0A=
     Reference URI:      http://oval.mitre.org/=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
   17.  XCCDF 1.2=0A=
=0A=
=0A=
     Namespace:          http://checklists.nist.gov/xccdf/1.2=0A=
     Specification Name: Extensible Configuration Checklist Description=0A=
                         Format=0A=
     Version:            1.2=0A=
     Reference URI:      http://scap.nist.gov/specifications/xccdf/,=0A=
                         =
http://csrc.nist.gov/publications/PubsNISTIRs.html=0A=
                         #NIST-IR-7275-r4=0A=
     Applicable Classes: Verification=0A=
=0A=
=0A=
=0A=
12.  Appendix IV: Another XML Example=0A=
=0A=
   This section provides an example of an incident encoded in the IODEF.=0A=
   This do not necessarily represent the only way to encode a particular=0A=
   incident.  This example reports an attack to a CSIRT and is extended=0A=
   from the example described in [RFC5070] . It uses identifiers whose=0A=
   dictionary follows CVE 1.0 schema, and it aembeds XML following CEE=0A=
   0.6.  Though these specifications are not listed in the IANA table at=0A=
   this moment, this section shows the example to demonstrate the=0A=
   usability of the draft.=0A=
=0A=
=0A=
   <?xml version=3D"1.0" encoding=3D"UTF-8"?>=0A=
   <IODEF-Document version=3D"1.00" lang=3D"en"=0A=
    xmlns=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 29]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
    xmlns:iodef=3D"urn:ietf:params:xml:ns:iodef-1.0"=0A=
    xmlns:iodef-sci=3D"urn:ietf:params:xml:ns:iodef-sci-1.0"=0A=
    xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">=0A=
     <Incident purpose=3D"reporting">=0A=
       <IncidentID name=3D"csirt.example.com">189493</IncidentID>=0A=
       <ReportTime>2001-09-13T23:19:24+00:00</ReportTime>=0A=
       <Description>Incident report in company xx</Description>=0A=
       <Assessment>=0A=
         <Impact completion=3D"failed" type=3D"admin"/>=0A=
       </Assessment>=0A=
       <Method>=0A=
         <Description>An identifier of a vulnerability is embedded=0A=
         </Description>=0A=
         <AdditionalData dtype=3D"xml">=0A=
           <iodef-sci:Vulnerability=0A=
            SpecID=3D"http://cve.mitre.org/cve/downloads/1.0"=0A=
            VulnerabilityID=3D"CVE-2010-0483"/>=0A=
         </AdditionalData>=0A=
       </Method>=0A=
       <Contact role=3D"creator" type=3D"organization">=0A=
         <ContactName>Example.com CSIRT</ContactName>=0A=
         <RegistryHandle registry=3D"arin">example-com</RegistryHandle>=0A=
         <Email>contact@csirt.example.com</Email>=0A=
       </Contact>=0A=
       <EventData>=0A=
         <Flow>=0A=
           <System category=3D"source">=0A=
             <Node>=0A=
               <Address category=3D"ipv4-addr">192.0.2.200</Address>=0A=
               <Counter type=3D"event">57</Counter>=0A=
             </Node>=0A=
           </System>=0A=
           <System category=3D"target">=0A=
             <Node>=0A=
               <Address category=3D"ipv4-net">192.0.2.16/28</Address>=0A=
             </Node>=0A=
             <Service ip_protocol=3D"6">=0A=
               <Port>80</Port>=0A=
             </Service>=0A=
             <AdditionalData dtype=3D"xml">=0A=
               <iodef-sci:Platform=0A=
                SpecID=3D"http://cpe.mitre.org/dictionary/2.0"=0A=
                PlatformID=3D"cpe://microsoft:windows:xp:pro:sp2"/>=0A=
             </AdditionalData>=0A=
           </System>=0A=
         </Flow>=0A=
         <Expectation action=3D"block-host" />=0A=
         <Expectation action=3D"other"/>=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 30]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
         <!-- <RecordItem> has an excerpt from a log -->=0A=
         <Record>=0A=
           <RecordData>=0A=
             <DateTime>2001-09-13T18:11:21+02:00</DateTime>=0A=
             <Description>a Web-server event record</Description>=0A=
             <RecordItem dtype=3D"xml">=0A=
               <iodef-sci:EventReport SpecID=3D"http://cee.mitre.org">=0A=
                 <iodef-sci:RawData dtype=3D"xml">=0A=
                   <cee:cee xmlns=3D"http://cee.mitre.org/1.0/profile/"=0A=
                    xmlns:cee=3D"http://cee.mitre.org/1.0/">=0A=
                     <cee:event>=0A=
                       <host>system.example.com</host>=0A=
                       <pname>auth</pname>=0A=
                       <time>2011-12-20T12:38:05.123456-05:00</time>=0A=
                       <appname>application</appname>=0A=
                       <pid>123</pid>=0A=
                       <sev>10</sev>=0A=
                       <action>login</action>=0A=
                       <domain>app</domain>=0A=
                       <object>account</object>=0A=
                       <service>web</service>=0A=
                       <status>success</status>=0A=
                     </cee:event>=0A=
                   </cee:cee>=0A=
                 </iodef-sci:RawData>=0A=
               </iodef-sci:EventReport>=0A=
             </RecordItem>=0A=
           </RecordData>=0A=
         </Record>=0A=
       </EventData>=0A=
       <History>=0A=
         <!-- Contact was previously made with the source network owner =
-->=0A=
         <HistoryItem action=3D"contact-source-site">=0A=
           <DateTime>2001-09-14T08:19:01+00:00</DateTime>=0A=
           <Description>Notification sent to=0A=
            constituency-contact@192.0.2.200</Description>=0A=
         </HistoryItem>=0A=
       </History>=0A=
     </Incident>=0A=
   </IODEF-Document>=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 31]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
13.  References=0A=
=0A=
13.1.  Normative References=0A=
=0A=
   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate=0A=
              Requirement Levels", BCP 14, RFC 2119, March 1997.=0A=
=0A=
   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform=0A=
              Resource Identifier (URI): Generic Syntax", STD 66, RFC=0A=
              3986, January 2005.=0A=
=0A=
   [RFC5070]  Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident=0A=
              Object Description Exchange Format", RFC 5070, December=0A=
              2007.=0A=
=0A=
   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an=0A=
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,=0A=
              May 2008.=0A=
=0A=
   [RFC6045]  Moriarty, K., "Real-time Inter-network Defense (RID)", RFC=0A=
              6045, November 2010.=0A=
=0A=
   [RFC6046]  Moriarty, K. and B. Trammell, "Transport of Real-time=0A=
              Inter-network Defense (RID) Messages", RFC 6046, November=0A=
              2010.=0A=
=0A=
   [EICAR]    European Expert Group for IT-Security, "Anti-Malware=0A=
              Testfile", 2003.=0A=
=0A=
   [MMDEF]    IEEE ICSG Malware Metadata Exchange Format Working Group,=0A=
              "Malware Metadata Exchange Format", .=0A=
=0A=
   [XML1.0]   Bray, T., Maler, E., Paoli, J., Sperberg-McQueen, C., and=0A=
              F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth=0A=
              Edition)", W3C Recommendation, November 2008.=0A=
=0A=
   [XMLschemaPart1]=0A=
              Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,=0A=
              "XML Schema Part 1: Structures Second Edition", W3C=0A=
              Recommendation, October 2004.=0A=
=0A=
   [XMLschemaPart2]=0A=
              Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes=0A=
              Second Edition", W3C Recommendation, October 2004.=0A=
=0A=
   [XMLNames]=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 32]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
              Bray, T., Hollander, D., Layman, A., Tobin, R., and H.=0A=
              Thomson, ""Namespaces in XML (Third Edition)", W3C=0A=
              Recommendation, December 2009.=0A=
=0A=
13.2.  Informative References=0A=
=0A=
   [RFC3339]  Klyne, G., Ed. and C. Newman, "Date and Time on the=0A=
              Internet: Timestamps", RFC 3339, July 2002.=0A=
=0A=
   [RFC3552]  Rescorla, E. and B. Korver, "Guidelines for Writing RFC=0A=
              Text on Security Considerations", BCP 72, RFC 3552, July=0A=
              2003.=0A=
=0A=
   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,=0A=
              January 2004.=0A=
=0A=
   [RFC5322]  Resnick, P., Ed., "Internet Message Format", RFC 5322,=0A=
              October 2008.=0A=
=0A=
   [RFC6116]  Bradner, S., Conroy, L., and K. Fujiwara, "The E.164 to=0A=
              Uniform Resource Identifiers (URI) Dynamic Delegation=0A=
              Discovery System (DDDS) Application (ENUM)", RFC 6116,=0A=
              March 2011.=0A=
=0A=
   [CAPEC]    The MITRE Corporation, "Common Attack Pattern Enumeration=0A=
              and Classification (CAPEC)", .=0A=
=0A=
   [CCE]      The MITRE Corporation, "Common Configuration Enumeration=0A=
              (CCE)", .=0A=
=0A=
   [CCSS]     Scarfone, K. and P. Mell, "The Common Configuration=0A=
              Scoring System (CCSS)", NIST Interagency Report 7502,=0A=
              December 2010.=0A=
=0A=
   [CEE]      The MITRE Corporation, "Common Event Expression (CEE)", .=0A=
=0A=
   [CPE]      National Institute of Standards and Technology, "Common=0A=
              Platform Enumeration", June 2011.=0A=
=0A=
   [CVE]      The MITRE Corporation, "Common Vulnerability and Exposures=0A=
              (CVE)", .=0A=
=0A=
   [CVRF]     ICASI, "Common Vulnerability Reporting Framework (CVRF)",=0A=
              .=0A=
=0A=
   [CVSS]     Peter Mell, Karen Scarfone, and Sasha Romanosky, "The=0A=
              Common Vulnerability Scoring System (CVSS) and Its=0A=
              Applicability to Federal Agency Systems", .=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 33]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   [CWE]      The MITRE Corporation, "Common Weakness Enumeration=0A=
              (CWE)", .=0A=
=0A=
   [CWSS]     The MITRE Corporation, "Common Weakness Scoring System=0A=
              (CWSS)", .=0A=
=0A=
   [OCIL]     David Waltermire and Karen Scarfone and Maria Casipe, "The=0A=
              Open Checklist Interactive Language (OCIL) Version 2.0",=0A=
              April 2011.=0A=
=0A=
   [OVAL]     The MITRE Corporation, "Open Vulnerability and Assessment=0A=
              Language (OVAL)", .=0A=
=0A=
   [SCAP]     Waltermire, D., Quinn, S., Scarfone, K., and A.=0A=
              Halbardier, "The Technical Specification for the Security=0A=
              Content Automation Protocol (SCAP): SCAP Version 1.2",=0A=
              NIST Special Publication 800-126 Revision 2, September=0A=
              2011.=0A=
=0A=
   [XCCDF]    David Waltermire and Charles Schmidt and Karen Scarfone=0A=
              and Neal Ziring, "Specification for the Extensible=0A=
              Configuration Checklist Description Format (XCCDF) version=0A=
              1.2 (DRAFT)", July 2011.=0A=
=0A=
Authors' Addresses=0A=
=0A=
   Takeshi Takahashi=0A=
   National Institute of Information and Communications Technology=0A=
   4-2-1 Nukui-Kitamachi Koganei=0A=
   184-8795 Tokyo=0A=
   Japan=0A=
=0A=
   Phone: +80 423 27 5862=0A=
   Email: takeshi_takahashi@nict.go.jp=0A=
=0A=
=0A=
   Kent Landfield=0A=
   McAfee, Inc=0A=
   5000 Headquarters Drive=0A=
   Plano, TX 75024=0A=
   USA=0A=
=0A=
   Email: Kent_Landfield@McAfee.com=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 34]=0A=
=0C=0A=
Internet-Draft                 IODEF-SCI                        Feb 2013=0A=
=0A=
=0A=
   Thomas Millar=0A=
   US Department of Homeland Security, NPPD/CS&C/NCSD/US-CERT=0A=
   245 Murray Lane SW, Building 410, MS #732=0A=
   Washington, DC 20598=0A=
   USA=0A=
=0A=
   Phone: +1 888 282 0870=0A=
   Email: thomas.millar@us-cert.gov=0A=
=0A=
=0A=
   Youki Kadobayashi=0A=
   Nara Institute of Science and Technology=0A=
   8916-5 Takayama, Ikoma=0A=
   630-0192 Nara=0A=
   Japan=0A=
=0A=
   Email: youki-k@is.aist-nara.ac.jp=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Takahashi, et al.               Expires                        [Page 35]=0A=

------=_NextPart_000_0007_01CE27EA.38939670--


From kathleen.moriarty@emc.com  Tue Mar 26 13:48:11 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E7521F8600 for <mile@ietfa.amsl.com>; Tue, 26 Mar 2013 13:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+ME8qglYAoR for <mile@ietfa.amsl.com>; Tue, 26 Mar 2013 13:48:10 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EA8D221F8554 for <mile@ietf.org>; Tue, 26 Mar 2013 13:48:02 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2QKm0xk029143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Tue, 26 Mar 2013 16:48:01 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Tue, 26 Mar 2013 16:47:41 -0400
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2QKlfhv013443 for <mile@ietf.org>; Tue, 26 Mar 2013 16:47:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub33.corp.emc.com ([::1]) with mapi; Tue, 26 Mar 2013 16:47:40 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Tue, 26 Mar 2013 16:47:39 -0400
Thread-Topic: Updated charter for review
Thread-Index: Ac4qYye3LkhMGx3rQjuIbJ1ARFHetA==
Message-ID: <F5063677821E3B4F81ACFB7905573F24DA7FE28C@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24DA7FE28CMX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] Updated charter for review
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 26 Mar 2013 20:48:11 -0000

--_000_F5063677821E3B4F81ACFB7905573F24DA7FE28CMX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As discussed at the MILE meeting, we need to revise the charter.  Brian and=
 I updated the charter and it is attached for review and comment to the lis=
t.

Thank you in advance!

Best regards,
Kathleen & Brian



Managed Incident Lightweight Exchange (mile)
--------------------------------------------

 Charter

 Current Status: Active

 Chairs:
     Kathleen Moriarty
     Brian Trammell

 Security Area Directors:
     Stephen Farrell
     Sean Turner

 Security Area Advisor:
     Sean Turner

 Mailing Lists:
     General Discussion: mile@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/mile
     Archive:            http://www.ietf.org/mail-archive/web/mile/

Description of Working Group:


    The Managed Incident Lightweight Exchange (MILE) working group will dev=
elop
    standards for the purpose of improving incident and indicator informati=
on
    sharing and handling capabilities based on the work developed in the IE=
TF
    Extended INCident Handling (INCH) working group. The Incident Object
    Description Exchange Format (IODEF) in RFC5070 and Real-time Inter-netw=
ork
    Defense (RID) in RFC6045 were developed in the INCH working group by
    international Computer Security Incident Response Teams (CSIRTs) and
    industry to meet the needs of a global community interested in sharing,
    handling, and exchanging incident and indicator information.

    The working group will define enhancements and extensions to IODEF and =
RID
    and provide guidance for applying them. It will also focus on improving=
 the
    interoperability of existing and new IODEF implementations, and the
    interoperation of IODEF and its extensions and enhancements with relate=
d
    standards for information sharing. The extensions and guidance created =
by
    the MILE working group assists with the daily operations of CSIRTs at a=
n
    organization, service providers, law enforcement, and at the national l=
evel.

    The working group has completed Proposed Standard revisions of RID (RFC=
 6545)
    and RID transport (RFC 6546). Given that this transport supports a spec=
ific
    workflow, and other workflows may be used by other communities, the wor=
king
    group will consider the development of alternate transport or bindings =
for RID and
    IODEF information.

    An incident could be a benign configuration issue, IT incident, an
    infraction to a service level agreement (SLA), a system compromise,
    socially engineered phishing attack, or a denial-of-service (DoS)
    attack, etc.  When an incident is detected, the response may include
    simply filing a report, notification to the source of the incident, a
    request to a third party for resolution/mitigation, information sharing=
 on identified indicators of compromise, or a request to
    locate the source.  IODEF defines a data representation that provides a
    standard format for sharing information commonly exchanged about
    computer security incidents, which includes indicators with or without =
the relevant context information.  IODEF will be updated to meet the curren=
t and future needs, maintaining the built in extensibility, of information =
sharing where indicators with rich context for actionable sharing is provid=
ed.  RID enables the secure exchange of
    incident related information in an IODEF format providing options for
    security, privacy, and policy setting.

    MILE leverages collaboration and sharing experiences with the work
    developed in the INCH working group which includes the data model
    detailed in the IODEF, existing extensions to the IODEF for
    Anti-phishing (RFC5901), and RID (RFC6045, RFC6046) for the secure
    exchange of information.  MILE will also leverage the experience gained
    in using IODEF and RID in operational contexts. Related work, drafted
    outside of INCH will also be reviewed and includes RFC5941, Sharing
    Transaction Fraud Data.

    The MILE working group provides coordination for these various extensio=
n
    efforts to improve the capabilities for exchanging indicator and incide=
nt information.
    MILE has several objectives including the update of IODEF coupled with =
guidance information
    to enhance interoperability, deployment ease, and applicability to curr=
ent
    information security data sharing use cases. MILE also describes a
    generalization of RID for secure exchange of other security-relevant XM=
L
    formats. MILE produces additional guidance needed for the successful
    exchange of incident information for new use cases according to policy,
    security, and privacy requirements. Finally, MILE produces a document
    template with guidance for defining IODEF extensions to be followed whe=
n
    producing extensions to IODEF as appropriate.

    [Removed laundry list of drafts -- outdated. We should update the miles=
tones below as well]

Goals and Milestones:
  Done     - WGLC Real-time Inter-network Defense (RID)
  Done     - WGLC Transport for Real-time Inter-network Defense (RID)
  Done     - Submit Real-time Inter-network Defense (RID) to IESG for consi=
deration as Standards Track document
  Done     - Submit Transport Real-time Inter-network Defense (RID) to IESG=
 for consideration as Standards Track document
  Done     - WGLC Template for extensions to IODEF
  Done     - WGLC IODEF Extensions in IANA XML Registry
  Apr 2013 - WGLC IODEF Extension to support structured cybersecurity infor=
mation
  Done     - Submit Template for extensions to IODEF to IESG for considerat=
ion as Informational document
  Done     - Submit IODEF Extensions in IANA XML Registry to IESG for consi=
deration as Standards Track document
  Jun 2013 - Submit IODEF Extension to support structured cybersecurity inf=
ormation to IESG for consideration as Standards Track document.
  TBD      - WGLC RFC 5070bis
  TBD      - Submit RFC 5070bis to IESG for consideration as a Standards Tr=
ack document
  TBD      - WGLC IODEF Reference Format
  TBD      - Submit IODEF Reference Format to IESG for consideration as a S=
tandards Track document
  TBD      - WGLC Resource-Oriented Indicator Exchange
  TBD      - Submit Resource-Oriented Indicator Exchange to IESG for consid=
eration as a Standards Track document

  [ old milestone bits below ]

  [no doc]- WGLC IODEF Guidance
  [no doc] - Submit IODEF Extension Labeling for data protection, retention=
, policies, and regulations to IESG for consideration as Standards Track do=
cument
  [no doc] - Submit WGLC IODEF Guidance to IESG for consideration as Inform=
ational document
  May 2012 - WGLC GRC Report Exchange [stalled]
  Jun 2012 - Submit GRC Report Exchange to IESG for consideration as Standa=
rds Track document [stalled]
  Jun 2012 - WGLC Forensics extension [stalled]
  Jul 2012 - Submit IODEF Forensics extension to IESG for consideration as =
Standards Track document [stalled]




--_000_F5063677821E3B4F81ACFB7905573F24DA7FE28CMX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Courier New, monospace" size=3D"2">
<div>As discussed at the MILE meeting, we need to revise the charter.&nbsp;=
 Brian and I updated the charter and it is attached for review and comment =
to the list.</div>
<div>&nbsp;</div>
<div>Thank you in advance!</div>
<div>&nbsp;</div>
<div>Best regards,</div>
<div>Kathleen &amp; Brian</div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div>Managed Incident Lightweight Exchange (mile)</div>
<div>--------------------------------------------</div>
<div>&nbsp;</div>
<div> Charter</div>
<div>&nbsp;</div>
<div> Current Status: Active</div>
<div>&nbsp;</div>
<div> Chairs:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Kathleen Moriarty </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Brian Trammell </div>
<div>&nbsp;</div>
<div> Security Area Directors:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Stephen Farrell </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Sean Turner </div>
<div>&nbsp;</div>
<div> Security Area Advisor:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Sean Turner </div>
<div>&nbsp;</div>
<div> Mailing Lists:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; General Discussion: mile@ietf.org</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; To Subscribe:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; <a href=3D"https://www.ietf.org/mailman/listinfo/mile">
https://www.ietf.org/mailman/listinfo/mile</a></div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Archive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"http://www.ietf.org/mail-archive/w=
eb/mile/">
http://www.ietf.org/mail-archive/web/mile/</a></div>
<div>&nbsp;</div>
<div>Description of Working Group:</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; The Managed Incident Lightweight Exchange (MILE) wo=
rking group will develop</div>
<div>&nbsp;&nbsp;&nbsp; standards for the purpose of improving incident and=
 indicator information</div>
<div>&nbsp;&nbsp;&nbsp; sharing and handling capabilities based on the work=
 developed in the IETF</div>
<div>&nbsp;&nbsp;&nbsp; Extended INCident Handling (INCH) working group. Th=
e Incident Object</div>
<div>&nbsp;&nbsp;&nbsp; Description Exchange Format (IODEF) in RFC5070 and =
Real-time Inter-network</div>
<div>&nbsp;&nbsp;&nbsp; Defense (RID) in RFC6045 were developed in the INCH=
 working group by</div>
<div>&nbsp;&nbsp;&nbsp; international Computer Security Incident Response T=
eams (CSIRTs) and</div>
<div>&nbsp;&nbsp;&nbsp; industry to meet the needs of a global community in=
terested in sharing,</div>
<div>&nbsp;&nbsp;&nbsp; handling, and exchanging incident and indicator inf=
ormation. </div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; The working group will define enhancements and exte=
nsions to IODEF and RID</div>
<div>&nbsp;&nbsp;&nbsp; and provide guidance for applying them. It will als=
o focus on improving the</div>
<div>&nbsp;&nbsp;&nbsp; interoperability of existing and new IODEF implemen=
tations, and the</div>
<div>&nbsp;&nbsp;&nbsp; interoperation of IODEF and its extensions and enha=
ncements with related</div>
<div>&nbsp;&nbsp;&nbsp; standards for information sharing. The extensions a=
nd guidance created by</div>
<div>&nbsp;&nbsp;&nbsp; the MILE working group assists with the daily opera=
tions of CSIRTs at an</div>
<div>&nbsp;&nbsp;&nbsp; organization, service providers, law enforcement, a=
nd at the national level.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; The working group has completed Proposed Standard r=
evisions of RID (RFC 6545)</div>
<div>&nbsp;&nbsp;&nbsp; and RID transport (RFC 6546). Given that this trans=
port supports a specific</div>
<div>&nbsp;&nbsp;&nbsp; workflow, and other workflows may be used by other =
communities, the working</div>
<div>&nbsp;&nbsp;&nbsp; group will consider the development of alternate tr=
ansport or bindings for RID and</div>
<div>&nbsp;&nbsp;&nbsp; IODEF information.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; An incident could be a benign configuration issue, =
IT incident, an</div>
<div>&nbsp;&nbsp;&nbsp; infraction to a service level agreement (SLA), a sy=
stem compromise,</div>
<div>&nbsp;&nbsp;&nbsp; socially engineered phishing attack, or a denial-of=
-service (DoS)</div>
<div>&nbsp;&nbsp;&nbsp; attack, etc.&nbsp; When an incident is detected, th=
e response may include</div>
<div>&nbsp;&nbsp;&nbsp; simply filing a report, notification to the source =
of the incident, a</div>
<div>&nbsp;&nbsp;&nbsp; request to a third party for resolution/mitigation,=
 information sharing on identified indicators of compromise, or a request t=
o</div>
<div>&nbsp;&nbsp;&nbsp; locate the source.&nbsp; IODEF defines a data repre=
sentation that provides a</div>
<div>&nbsp;&nbsp;&nbsp; standard format for sharing information commonly ex=
changed about</div>
<div>&nbsp;&nbsp;&nbsp; computer security incidents, which includes indicat=
ors with or without the relevant context information.&nbsp; IODEF will be u=
pdated to meet the current and future needs, maintaining the built in exten=
sibility, of information sharing where indicators with
rich context for actionable sharing is provided.&nbsp; RID enables the secu=
re exchange of</div>
<div>&nbsp;&nbsp;&nbsp; incident related information in an IODEF format pro=
viding options for</div>
<div>&nbsp;&nbsp;&nbsp; security, privacy, and policy setting.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; MILE leverages collaboration and sharing experience=
s with the work</div>
<div>&nbsp;&nbsp;&nbsp; developed in the INCH working group which includes =
the data model</div>
<div>&nbsp;&nbsp;&nbsp; detailed in the IODEF, existing extensions to the I=
ODEF for</div>
<div>&nbsp;&nbsp;&nbsp; Anti-phishing (RFC5901), and RID (RFC6045, RFC6046)=
 for the secure</div>
<div>&nbsp;&nbsp;&nbsp; exchange of information.&nbsp; MILE will also lever=
age the experience gained</div>
<div>&nbsp;&nbsp;&nbsp; in using IODEF and RID in operational contexts. Rel=
ated work, drafted</div>
<div>&nbsp;&nbsp;&nbsp; outside of INCH will also be reviewed and includes =
RFC5941, Sharing</div>
<div>&nbsp;&nbsp;&nbsp; Transaction Fraud Data.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; The MILE working group provides coordination for th=
ese various extension</div>
<div>&nbsp;&nbsp;&nbsp; efforts to improve the capabilities for exchanging =
indicator and incident information.</div>
<div>&nbsp;&nbsp;&nbsp; MILE has several objectives including the update of=
 IODEF coupled with guidance information</div>
<div>&nbsp;&nbsp;&nbsp; to enhance interoperability, deployment ease, and a=
pplicability to current</div>
<div>&nbsp;&nbsp;&nbsp; information security data sharing use cases. MILE a=
lso describes a</div>
<div>&nbsp;&nbsp;&nbsp; generalization of RID for secure exchange of other =
security-relevant XML</div>
<div>&nbsp;&nbsp;&nbsp; formats. MILE produces additional guidance needed f=
or the successful</div>
<div>&nbsp;&nbsp;&nbsp; exchange of incident information for new use cases =
according to policy,</div>
<div>&nbsp;&nbsp;&nbsp; security, and privacy requirements. Finally, MILE p=
roduces a document</div>
<div>&nbsp;&nbsp;&nbsp; template with guidance for defining IODEF extension=
s to be followed when</div>
<div>&nbsp;&nbsp;&nbsp; producing extensions to IODEF as appropriate.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; [Removed laundry list of drafts -- outdated. We sho=
uld update the milestones below as well]</div>
<div>&nbsp;</div>
<div>Goals and Milestones:</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Real-time Inter-network Def=
ense (RID)</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Transport for Real-time Int=
er-network Defense (RID)</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit Real-time Inter-network D=
efense (RID) to IESG for consideration as Standards Track document</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit Transport Real-time Inter=
-network Defense (RID) to IESG for consideration as Standards Track documen=
t</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Template for extensions to =
IODEF</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC IODEF Extensions in IANA XM=
L Registry</div>
<div>&nbsp; Apr 2013 - WGLC IODEF Extension to support structured cybersecu=
rity information</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit Template for extensions t=
o IODEF to IESG for consideration as Informational document</div>
<div>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit IODEF Extensions in IANA =
XML Registry to IESG for consideration as Standards Track document</div>
<div>&nbsp; Jun 2013 - Submit IODEF Extension to support structured cyberse=
curity information to IESG for consideration as Standards Track document.</=
div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGLC RFC 5070bis</div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Submit RFC 5070bis to IESG =
for consideration as a Standards Track document</div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGLC IODEF Reference Format=
</div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Submit IODEF Reference Form=
at to IESG for consideration as a Standards Track document</div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Resource-Oriented Indi=
cator Exchange</div>
<div>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Submit Resource-Oriented In=
dicator Exchange to IESG for consideration as a Standards Track document</d=
iv>
<div>&nbsp;</div>
<div>&nbsp; [ old milestone bits below ]</div>
<div>&nbsp;</div>
<div>&nbsp; [no doc]- WGLC IODEF Guidance</div>
<div>&nbsp; [no doc] - Submit IODEF Extension Labeling for data protection,=
 retention, policies, and regulations to IESG for consideration as Standard=
s Track document</div>
<div>&nbsp; [no doc] - Submit WGLC IODEF Guidance to IESG for consideration=
 as Informational document</div>
<div>&nbsp; May 2012 - WGLC GRC Report Exchange [stalled]</div>
<div>&nbsp; Jun 2012 - Submit GRC Report Exchange to IESG for consideration=
 as Standards Track document [stalled]</div>
<div>&nbsp; Jun 2012 - WGLC Forensics extension [stalled]</div>
<div>&nbsp; Jul 2012 - Submit IODEF Forensics extension to IESG for conside=
ration as Standards Track document [stalled]</div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Calibri, sans-serif" size=3D"2">&nbsp;</font></div>
</font>
</body>
</html>

--_000_F5063677821E3B4F81ACFB7905573F24DA7FE28CMX15Acorpemccom_--

From kathleen.moriarty@emc.com  Tue Mar 26 17:00:19 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 748AC21F8BCF for <mile@ietfa.amsl.com>; Tue, 26 Mar 2013 17:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hrY-RrlpDDtV for <mile@ietfa.amsl.com>; Tue, 26 Mar 2013 17:00:08 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7877521F8B0C for <mile@ietf.org>; Tue, 26 Mar 2013 17:00:08 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2R0076D004425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Tue, 26 Mar 2013 20:00:07 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Tue, 26 Mar 2013 20:00:01 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2R000fB000326 for <mile@ietf.org>; Tue, 26 Mar 2013 20:00:00 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Tue, 26 Mar 2013 19:59:59 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Tue, 26 Mar 2013 19:59:57 -0400
Thread-Topic: Updated charter for review
Thread-Index: Ac4qYye3LkhMGx3rQjuIbJ1ARFHetAAGQt7A
Message-ID: <F5063677821E3B4F81ACFB7905573F24DA7FE2C9@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24DA7FE28C@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DA7FE28C@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24DA7FE2C9MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Updated charter for review
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 27 Mar 2013 00:00:19 -0000

--_000_F5063677821E3B4F81ACFB7905573F24DA7FE2C9MX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The good news, people are reading it, however, I sent out the wrong version=
.  The corrected one is included in this message.

Please provide feedback over the next 2 weeks.  We'll move the charter to t=
he next stage in the approval process after April 9th.

Thank you!
Kathleen

Managed Incident Lightweight Exchange (mile)
--------------------------------------------

Charter

Current Status: Active

Chairs:
     Kathleen Moriarty
     Brian Trammell

Security Area Directors:
     Stephen Farrell
     Sean Turner

Security Area Advisor:
     Sean Turner

Mailing Lists:
     General Discussion: mile@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/mile
     Archive:            http://www.ietf.org/mail-archive/web/mile/

Description of Working Group:


    The Managed Incident Lightweight Exchange (MILE) working group develops
    standards for the purpose of improving incident and indicator informati=
on
    sharing and handling capabilities. The Incident Object
    Description Exchange Format (IODEF) in RFC5070 and Real-time Inter-netw=
ork
    Defense (RID) in RFC6045 were developed in the INCH working group by
    international Computer Security Incident Response Teams (CSIRTs) and
    industry to meet the needs of a global community interested in sharing,
    handling, and exchanging incident and indicator information.

    The working group will define enhancements and extensions to IODEF and =
RID
    and provide guidance for applying them. It will also focus on improving=
 the
    interoperability of existing and new IODEF implementations, and the
    interoperation of IODEF and its extensions and enhancements with relate=
d
    standards for information sharing. The extensions and guidance created =
by
    the MILE working group assist with the daily operations of CSIRTs at an
    organization, service providers, law enforcement, and at the national l=
evel.

    The working group has completed Proposed Standard revisions of RID (RFC=
 6545)
    and RID transport (RFC 6546). This transport was designed to meet speci=
fic usage

    requirements of CSIRTs and related industry groups. In order to meet di=
fferent

    usage requirements for other communities, the working
    group will consider
    alternate transport or bindings for RID and IODEF information.

    An incident could be a benign configuration issue, IT incident, an
    infraction to a service level agreement (SLA), a system compromise,
    socially engineered phishing attack, or a denial-of-service (DoS)
    attack, etc.  When an incident is detected, the response may include
    simply filing a report, notification to the source of the incident, a
    request to a third party for resolution/mitigation, information sharing
    on identified indicators of compromise, or a request to
    locate the source.  IODEF defines a data representation that provides a
    standard format for sharing information commonly exchanged about
    computer security incidents, which includes indicators with or without =
the
    relevant context information.  IODEF will be updated to meet the curren=
t and
    future needs, maintaining the built in extensibility, of information sh=
aring
    where indicators with rich context for actionable sharing is provided.
    RID enables the secure exchange of incident related information in an I=
ODEF
    format providing options for security, privacy, and policy setting.

    MILE leverages collaboration and sharing experiences with prior work
    including the IODEF data model detailed in the IODEF, existing extensio=
ns
    to the IODEF for Anti-phishing (RFC5901), and RID (RFC6545, RFC6546) fo=
r
    the secure exchange of information.  MILE will also leverage the experi=
ence
    gained in using IODEF and RID in operational contexts.

    The MILE working group provides coordination for IODEF and RID extensio=
ns that
    improve capabilities for exchanging indicator and incident information.
    MILE's objectives include the update of IODEF coupled with guidance inf=
ormation
    to enhance interoperability, deployment ease, and applicability to curr=
ent
    information security data sharing use cases. MILE will also describe a
    generalization of RID for secure exchange of other security-relevant XM=
L
    formats. MILE will produce additional guidance needed for the successfu=
l
    exchange of indicator and incident information for new use cases accord=
ing to policy,
    security, and privacy requirements. Finally, MILE produced a document
    template with guidance for defining IODEF extensions to be followed whe=
n
    producing extensions to IODEF as appropriate.

    [Removed laundry list of drafts -- outdated. We should update the miles=
tones below as well]

Goals and Milestones:
  Done     - WGLC Real-time Inter-network Defense (RID)
  Done     - WGLC Transport for Real-time Inter-network Defense (RID)
  Done     - Submit Real-time Inter-network Defense (RID) to IESG for consi=
deration as Standards Track document
  Done     - Submit Transport Real-time Inter-network Defense (RID) to IESG=
 for consideration as Standards Track document
  Done     - WGLC Template for extensions to IODEF
  Done     - WGLC IODEF Extensions in IANA XML Registry
  Apr 2013 - WGLC IODEF Extension to support structured cybersecurity infor=
mation
  Done     - Submit Template for extensions to IODEF to IESG for considerat=
ion as Informational document
  Done     - Submit IODEF Extensions in IANA XML Registry to IESG for consi=
deration as Standards Track document
  Jun 2013 - Submit IODEF Extension to support structured cybersecurity inf=
ormation to IESG for consideration as Standards Track document.
  TBD      - WGLC RFC 5070bis
  TBD      - Submit RFC 5070bis to IESG for consideration as a Standards Tr=
ack document
  TBD      - WGLC IODEF Reference Format
  TBD      - Submit IODEF Reference Format to IESG for consideration as a S=
tandards Track document
  TBD      - WGLC Resource-Oriented Indicator Exchange
  TBD      - Submit Resource-Oriented Indicator Exchange to IESG for consid=
eration as a Standards Track document

  [ old milestone bits below ]

  [no doc]- WGLC IODEF Guidance
  [no doc] - Submit IODEF Extension Labeling for data protection, retention=
, policies, and regulations to IESG for consideration as Standards Track do=
cument
  [no doc] - Submit WGLC IODEF Guidance to IESG for consideration as Inform=
ational document
  May 2012 - WGLC GRC Report Exchange [stalled]
  Jun 2012 - Submit GRC Report Exchange to IESG for consideration as Standa=
rds Track document [stalled]
  Jun 2012 - WGLC Forensics extension [stalled]
  Jul 2012 - Submit IODEF Forensics extension to IESG for consideration as =
Standards Track document [stalled]

From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor=
iarty, Kathleen
Sent: Tuesday, March 26, 2013 4:48 PM
To: mile@ietf.org
Subject: [mile] Updated charter for review

As discussed at the MILE meeting, we need to revise the charter.  Brian and=
 I updated the charter and it is attached for review and comment to the lis=
t.

Thank you in advance!

Best regards,
Kathleen & Brian


 [Outdated draft charter deleted]


--_000_F5063677821E3B4F81ACFB7905573F24DA7FE2C9MX15Acorpemccom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The good =
news, people are reading it, however, I sent out the wrong version.&nbsp; T=
he corrected one is included in this message.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>Please provide feedback over the next 2 weeks.&nbsp; We&#8217;ll move the =
charter to the next stage in the approval process after April 9<sup>th</sup=
>.&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D'>Thank you!<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>Kathleen<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Managed Inc=
ident Lightweight Exchange (mile)<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>--------------------------------------------<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'> Charter<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbs=
p;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'> Current Status: Active<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'> Chairs:<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Kathleen Moriarty <o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Brian Trammell <o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'> Security Area Directors:<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Stephen Farrell <o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;S=
ean Turner <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'> Security Area Advisor:<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; Sean Turne=
r <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'> Mailing Lists:<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp; General Discussion: mile@ie=
tf.org<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&=
nbsp; To Subscribe:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://www.ietf.or=
g/mailman/listinfo/mile<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&n=
bsp;&nbsp;&nbsp;&nbsp; Archive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; http://www.ietf.org/mail-archive/web/mile/<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-famil=
y:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'>Description of Working Group:<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;=
&nbsp;&nbsp;The Managed Incident Lightweight Exchange (MILE) working group =
develops<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp=
; standards for the purpose of improving incident and indicator information=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; sharin=
g and handling capabilities. The Incident Object<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; Description Exchange Format (IODE=
F) in RFC5070 and Real-time Inter-network<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"=
;color:#1F497D'>&nbsp;&nbsp;&nbsp; Defense (RID) in RFC6045 were developed =
in the INCH working group by<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp; international Computer Security Incident Response Tea=
ms (CSIRTs) and<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbs=
p;&nbsp; industry to meet the needs of a global community interested in sha=
ring,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; h=
andling, and exchanging incident and indicator information. <o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;The working group=
 will define enhancements and extensions to IODEF and RID<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calib=
ri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; and provide guidance for=
 applying them. It will also focus on improving the<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; interoperability of existing a=
nd new IODEF implementations, and the<o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";col=
or:#1F497D'>&nbsp;&nbsp;&nbsp; interoperation of IODEF and its extensions a=
nd enhancements with related<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp; standards for information sharing. The extensions and=
 guidance created by<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp; the MILE working group assist with the daily operations of C=
SIRTs at an<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&n=
bsp; organization, service providers, law enforcement, and at the national =
level.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;T=
he working group has completed Proposed Standard revisions of RID (RFC 6545=
)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; and R=
ID transport (RFC 6546). This transport was designed to meet specific usage=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; requirements of CSIRTs an=
d related industry groups. In order to meet different<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>&nbsp;&nbsp;&nbsp; usage requirements for other communities, the w=
orking<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; =
group will consider<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp; alternate transport or bindings for RID and IODEF informatio=
n.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; <o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;An in=
cident could be a benign configuration issue, IT incident, an<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; infraction to a serv=
ice level agreement (SLA), a system compromise,<o:p></o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-=
serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; socially engineered phishing attac=
k, or a denial-of-service (DoS)<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp;&nbsp;&nbsp; attack, etc.&nbsp; When an incident is detected, t=
he response may include<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&n=
bsp;&nbsp;&nbsp; simply filing a report, notification to the source of the =
incident, a<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&n=
bsp; request to a third party for resolution/mitigation, information sharin=
g<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; on id=
entified indicators of compromise, or a request to<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; locate the source.&nbsp; IODEF =
defines a data representation that provides a<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>&nbsp;&nbsp;&nbsp; standard format for sharing informat=
ion commonly exchanged about<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp; computer security incidents, which includes indicator=
s with or without the<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp; relevant context information.&nbsp; IODEF will be updated to=
 meet the current and<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p;&nbsp;&nbsp; future needs, maintaining the built in extensibility, of inf=
ormation sharing<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nb=
sp;&nbsp; where indicators with rich context for actionable sharing is prov=
ided.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11=
.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; R=
ID enables the secure exchange of incident related information in an IODEF<=
o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; format =
providing options for security, privacy, and policy setting.<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; <o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;MILE leverages collabo=
ration and sharing experiences with prior work<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'>&nbsp;&nbsp;&nbsp; including the IODEF data model deta=
iled in the IODEF, existing extensions<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";co=
lor:#1F497D'>&nbsp;&nbsp;&nbsp; to the IODEF for Anti-phishing (RFC5901), a=
nd RID (RFC6545, RFC6546) for<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F49=
7D'>&nbsp;&nbsp;&nbsp; the secure exchange of information.&nbsp; MILE will =
also leverage the experience<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&nbsp;&nbsp; gained in using IODEF and RID in operational contexts=
. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp=
;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp;&nbsp;=
The MILE working group provides coordination for IODEF and RID extensions t=
hat<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; imp=
rove capabilities for exchanging indicator and incident information.<o:p></=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; MILE's object=
ives include the update of IODEF coupled with guidance information<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; to enhance inte=
roperability, deployment ease, and applicability to current<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; information security d=
ata sharing use cases. MILE will also describe a<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans=
-serif";color:#1F497D'>&nbsp;&nbsp;&nbsp; generalization of RID for secure =
exchange of other security-relevant XML<o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";c=
olor:#1F497D'>&nbsp;&nbsp;&nbsp; formats. MILE will produce additional guid=
ance needed for the successful<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'>&nbsp;&nbsp;&nbsp; exchange of indicator and incident information for =
new use cases according to policy,<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'>&nbsp;&nbsp;&nbsp; security, and privacy requirements. Finally, MI=
LE produced a document<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nb=
sp;&nbsp;&nbsp; template with guidance for defining IODEF extensions to be =
followed when<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;&nbsp;=
&nbsp; producing extensions to IODEF as appropriate.<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>&nbsp;&nbsp;&nbsp; [Removed laundry list of drafts -- outdated. We =
should update the milestones below as well]<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
>Goals and Milestones:<o:p></o:p></span></p><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nb=
sp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Real-time Inter-network Defense (RI=
D)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; Done&nbsp;&nbsp;=
&nbsp;&nbsp; - WGLC Transport for Real-time Inter-network Defense (RID)<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; Done&nbsp;&nbsp;&nbsp;=
&nbsp; - Submit Real-time Inter-network Defense (RID) to IESG for considera=
tion as Standards Track document<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit Transport Real-time Int=
er-network Defense (RID) to IESG for consideration as Standards Track docum=
ent<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; Done&nbsp;&nbsp=
;&nbsp;&nbsp; - WGLC Template for extensions to IODEF<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";color:#1F497D'>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - WGLC IODE=
F Extensions in IANA XML Registry<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>&nbsp; Apr 2013 - WGLC IODEF Extension to support structured cybers=
ecurity information<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbs=
p; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit Template for extensions to IODEF t=
o IESG for consideration as Informational document<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sa=
ns-serif";color:#1F497D'>&nbsp; Done&nbsp;&nbsp;&nbsp;&nbsp; - Submit IODEF=
 Extensions in IANA XML Registry to IESG for consideration as Standards Tra=
ck document<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; Jun 201=
3 - Submit IODEF Extension to support structured cybersecurity information =
to IESG for consideration as Standards Track document.<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGL=
C RFC 5070bis<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; TBD&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; - Submit RFC 5070bis to IESG for consideration=
 as a Standards Track document<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F4=
97D'>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGLC IODEF Reference Format=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; TBD&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; - Submit IODEF Reference Format to IESG for consideration a=
s a Standards Track document<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp; TBD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - WGLC Resource-Oriented Indica=
tor Exchange<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; TBD&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; - Submit Resource-Oriented Indicator Exchange t=
o IESG for consideration as a Standards Track document<o:p></o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri"=
,"sans-serif";color:#1F497D'>&nbsp; <o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>&nbsp;&nbsp;[ old milestone bits below ]<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>&nbsp; <o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>&nbsp;&nbsp;[no doc]- WGLC IODEF Guidance<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'>&nbsp; [no doc] - Submit IODEF Extension Labeling f=
or data protection, retention, policies, and regulations to IESG for consid=
eration as Standards Track document<o:p></o:p></span></p><p class=3DMsoNorm=
al><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
:#1F497D'>&nbsp; [no doc] - Submit WGLC IODEF Guidance to IESG for consider=
ation as Informational document<o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F=
497D'>&nbsp; May 2012 - WGLC GRC Report Exchange [stalled]<o:p></o:p></span=
></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cali=
bri","sans-serif";color:#1F497D'>&nbsp; Jun 2012 - Submit GRC Report Exchan=
ge to IESG for consideration as Standards Track document [stalled]<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";color:#1F497D'>&nbsp; Jun 2012 - WGLC Forensics e=
xtension [stalled]<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp; =
Jul 2012 - Submit IODEF Forensics extension to IESG for consideration as St=
andards Track document [stalled]<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-to=
p:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><s=
pan style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</spa=
n></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> m=
ile-bounces@ietf.org [mailto:mile-bounces@ietf.org] <b>On Behalf Of </b>Mor=
iarty, Kathleen<br><b>Sent:</b> Tuesday, March 26, 2013 4:48 PM<br><b>To:</=
b> mile@ietf.org<br><b>Subject:</b> [mile] Updated charter for review<o:p><=
/o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'>As discussed at the MILE meeting, we need to revise the charter.&nbsp;=
 Brian and I updated the charter and it is attached for review and comment =
to the list.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fam=
ily:"Courier New"'>Thank you in advance!<o:p></o:p></span></p></div><div><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
"'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>Best regards,<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New"'>Kathleen &amp; Brian<o:p></o:p></span></p></div><di=
v><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Calibri=
","sans-serif"'>&nbsp;</span><span style=3D'font-size:10.0pt;font-family:"C=
ourier New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;</span><s=
pan style=3D'font-size:10.0pt;font-family:"Courier New"'><o:p></o:p></span>=
</p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-fa=
mily:"Calibri","sans-serif"'>&nbsp;<span style=3D'color:#1F497D'>[Outdated =
draft charter deleted]</span></span><span style=3D'font-size:10.0pt;font-fa=
mily:"Courier New"'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><=
span style=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p>=
</span></p></div></div></body></html>=

--_000_F5063677821E3B4F81ACFB7905573F24DA7FE2C9MX15Acorpemccom_--

From kathleen.moriarty@emc.com  Wed Mar 27 17:59:30 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0EFC21F938D for <mile@ietfa.amsl.com>; Wed, 27 Mar 2013 17:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNdTWXUbZLlw for <mile@ietfa.amsl.com>; Wed, 27 Mar 2013 17:59:29 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 06D5A21F8EA2 for <mile@ietf.org>; Wed, 27 Mar 2013 17:59:28 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2S0xQPd024523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Mar 2013 20:59:26 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Wed, 27 Mar 2013 20:59:22 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2S0xKWS014685; Wed, 27 Mar 2013 20:59:21 -0400
Received: from mxhub37.corp.emc.com (128.222.70.104) by mxhub35.corp.emc.com (10.254.93.83) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 27 Mar 2013 20:59:20 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub37.corp.emc.com ([128.222.70.104]) with mapi; Wed, 27 Mar 2013 20:59:20 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, "mile@ietf.org" <mile@ietf.org>
Date: Wed, 27 Mar 2013 20:59:20 -0400
Thread-Topic: [mile] Consensus Call - SCI draft MMDEF as MTI
Thread-Index: AQFCibkFcoiRAxGJUwOvO7kpytpEUwHYmM6bAq+IVDUBugT0/pmYF3cAgAdhkdA=
Message-ID: <F5063677821E3B4F81ACFB7905573F24DA7FE484@MX15A.corp.emc.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com> <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com> <000601ce279e$c8ab7940$5a026bc0$@nict.go.jp>
In-Reply-To: <000601ce279e$c8ab7940$5a026bc0$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 00:59:30 -0000

Hello,

Thank you for voicing your opinions at the MILE meeting, the two week perio=
d is up and we have full agreement.  We will move forward with MMDEF as the=
 MTI for the SCI draft.

Take - Thank you for updating the draft to include MMDEF as the MTI as well=
 as the update below.  Could you expand the acronym for MTI in the draft an=
d update the version to the latest?

Bets regards,
Kathleen=20

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Tak=
eshi Takahashi
Sent: Saturday, March 23, 2013 4:17 AM
To: mile@ietf.org
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI

Hi all,

I remember the discussion on the EICAR and agree upon David's kind
suggestion.
The attached is the revised SCI draft, whose section 10 talks about the
EICAR (with an example XML).

Kind regards,
Take


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> Black, David
> Sent: Thursday, March 14, 2013 11:54 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>=20
> I support MMDEF as the MTI, and since MMDEF is a malware spec, I'd like t=
o
> resurrect a previously-discussed suggestion that the SCI draft include
> discussion of the "EICAR Standard Anti-Virus Test File" as a specific
example
> that SHOULD (or MUST?) be supported for black-box testing purposes.
>=20
> See: http://www.eicar.org/86-0-Intended-use.html
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
> > Of Moriarty, Kathleen
> > Sent: Thursday, March 14, 2013 10:38 AM
> > To: Panos Kampanakis (pkampana); mile@ietf.org
> > Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
> >
> > Hello Panos,
> >
> > Thank you for joining us remotely!  The recording is available for
> > those who were not able to attend during the session.
> >
> > We need to choose one included schema as MTI for 'black box' testing
> > of the method described.  Essentially, if you can exchange using the
> > MTI spec, then any other specs supported should theoretically work as
> > the pattern has been established.
> >
> > MMDEF was recommended as it is in use by the eCrime WG as an
> extension
> > to IODEF/RFC5901.  It replaced the method to include malware in
> > exchanges and seemed to make sense to adopt more broadly as it is
> > maintained by a group in IEEE focused on that particular problem.
> >
> > BTW, I meant to say the last call will end in two weeks from
> > yesterday, Wednesday March 27th.
> >
> > Thank you!
> > Kathleen
> > ________________________________________
> > From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
> > Sent: Thursday, March 14, 2013 9:59 AM
> > To: Moriarty, Kathleen; mile@ietf.org
> > Subject: RE: Consensus Call - SCI draft MMDEF as MTI
> >
> > I agree with MMDEF included in SCI.
> > I am not sure why it must be MTI. Due to some audio problems I missed
> > part of the call yesterday. Can you briefly summarize why we want it
MTI?
> >
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
> > Of Moriarty, Kathleen
> > Sent: Wednesday, March 13, 2013 3:04 PM
> > To: mile@ietf.org
> > Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
> >
> > Hello,
> >
> > In today's MILE session, a call for consensus began to include MMDEF
> > in the SCI draft as the mandatory-to-implement (MTI) specification.
> > The call for consensus will last for 2 weeks and we ask that you
contribute
> your opinion.
> > The vote in the room was unanimous and we want to make sure we hear
> > from participants not in attendance.
> >
> > Poll will end on Wednesday next week.
> >
> > Thank you!
> > Kathleen
> > _______________________________________________
> > 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
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

From eburger@standardstrack.com  Wed Mar 27 19:25:47 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C476021F9397 for <mile@ietfa.amsl.com>; Wed, 27 Mar 2013 19:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nX+oJz8ulszo for <mile@ietfa.amsl.com>; Wed, 27 Mar 2013 19:25:47 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.246.244]) by ietfa.amsl.com (Postfix) with ESMTP id 1761F21F8F9F for <mile@ietf.org>; Wed, 27 Mar 2013 19:25:47 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:54143 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UL2XA-0000e2-Jd for mile@ietf.org; Wed, 27 Mar 2013 19:25:44 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <1CBD9BD3-18CF-4787-B13E-3288FCB68AE0@cs.georgetown.edu>
Date: Wed, 27 Mar 2013 22:25:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5271802E-3724-426D-8DB8-E4718B0092AD@standardstrack.com>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com> <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com> <000601ce279e$c8ab7940$5a026bc0$@nict.go.jp> <F5063677821E3B4F81ACFB7905573F24DA7FE484@MX15A.corp.emc.com> <D65778B5-1396-4E58-A520-FB9701C85426@cs.georgetown.edu> <1CBD9BD3-18CF-4787-B13E-3288FCB68AE0@cs.georgetown.edu>
To: "mile@ietf.org IETF" <mile@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 02:25:47 -0000

Did we ever find a stable reference for MMDEF?

On Mar 27, 2013, at 8:59 PM, "Moriarty, Kathleen" =
<kathleen.moriarty@emc.com> wrote:

> Hello,
>=20
> Thank you for voicing your opinions at the MILE meeting, the two week =
period is up and we have full agreement.  We will move forward with =
MMDEF as the MTI for the SCI draft.
>=20
> Take - Thank you for updating the draft to include MMDEF as the MTI as =
well as the update below.  Could you expand the acronym for MTI in the =
draft and update the version to the latest?
>=20
> Bets regards,
> Kathleen=20
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Takeshi Takahashi
> Sent: Saturday, March 23, 2013 4:17 AM
> To: mile@ietf.org
> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>=20
> Hi all,
>=20
> I remember the discussion on the EICAR and agree upon David's kind
> suggestion.
> The attached is the revised SCI draft, whose section 10 talks about =
the
> EICAR (with an example XML).
>=20
> Kind regards,
> Take
>=20
>=20
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of
>> Black, David
>> Sent: Thursday, March 14, 2013 11:54 PM
>> To: Moriarty, Kathleen; mile@ietf.org
>> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>>=20
>> I support MMDEF as the MTI, and since MMDEF is a malware spec, I'd =
like to
>> resurrect a previously-discussed suggestion that the SCI draft =
include
>> discussion of the "EICAR Standard Anti-Virus Test File" as a specific
> example
>> that SHOULD (or MUST?) be supported for black-box testing purposes.
>>=20
>> See: http://www.eicar.org/86-0-Intended-use.html
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
>>> Of Moriarty, Kathleen
>>> Sent: Thursday, March 14, 2013 10:38 AM
>>> To: Panos Kampanakis (pkampana); mile@ietf.org
>>> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>>>=20
>>> Hello Panos,
>>>=20
>>> Thank you for joining us remotely!  The recording is available for
>>> those who were not able to attend during the session.
>>>=20
>>> We need to choose one included schema as MTI for 'black box' testing
>>> of the method described.  Essentially, if you can exchange using the
>>> MTI spec, then any other specs supported should theoretically work =
as
>>> the pattern has been established.
>>>=20
>>> MMDEF was recommended as it is in use by the eCrime WG as an
>> extension
>>> to IODEF/RFC5901.  It replaced the method to include malware in
>>> exchanges and seemed to make sense to adopt more broadly as it is
>>> maintained by a group in IEEE focused on that particular problem.
>>>=20
>>> BTW, I meant to say the last call will end in two weeks from
>>> yesterday, Wednesday March 27th.
>>>=20
>>> Thank you!
>>> Kathleen
>>> ________________________________________
>>> From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
>>> Sent: Thursday, March 14, 2013 9:59 AM
>>> To: Moriarty, Kathleen; mile@ietf.org
>>> Subject: RE: Consensus Call - SCI draft MMDEF as MTI
>>>=20
>>> I agree with MMDEF included in SCI.
>>> I am not sure why it must be MTI. Due to some audio problems I =
missed
>>> part of the call yesterday. Can you briefly summarize why we want it
> MTI?
>>>=20
>>> -----Original Message-----
>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
>>> Of Moriarty, Kathleen
>>> Sent: Wednesday, March 13, 2013 3:04 PM
>>> To: mile@ietf.org
>>> Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
>>>=20
>>> Hello,
>>>=20
>>> In today's MILE session, a call for consensus began to include MMDEF
>>> in the SCI draft as the mandatory-to-implement (MTI) specification.
>>> The call for consensus will last for 2 weeks and we ask that you
> contribute
>> your opinion.
>>> The vote in the room was unanimous and we want to make sure we hear
>>> from participants not in attendance.
>>>=20
>>> Poll will end on Wednesday next week.
>>>=20
>>> Thank you!
>>> Kathleen
>>> _______________________________________________
>>> 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
>>=20
>> _______________________________________________
>> 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 ramartin@mitre.org  Thu Mar 28 05:35:33 2013
Return-Path: <ramartin@mitre.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D830A21F8E5E for <mile@ietfa.amsl.com>; Thu, 28 Mar 2013 05:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pgPEGxaXUxcP for <mile@ietfa.amsl.com>; Thu, 28 Mar 2013 05:35:33 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3916421F8E06 for <mile@ietf.org>; Thu, 28 Mar 2013 05:35:31 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AA933229001B for <mile@ietf.org>; Thu, 28 Mar 2013 08:35:30 -0400 (EDT)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 8B3E71F0B16 for <mile@ietf.org>; Thu, 28 Mar 2013 08:35:30 -0400 (EDT)
Received: from [10.147.10.6] (129.83.31.51) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server id 14.2.342.3; Thu, 28 Mar 2013 08:35:09 -0400
Message-ID: <51543918.1050605@mitre.org>
Date: Thu, 28 Mar 2013 08:35:36 -0400
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: <mile@ietf.org>
References: <F5063677821E3B4F81ACFB7905573F24D79BE5CD@MX15A.corp.emc.com>, <1C9F17D1873AFA47A969C4DD98F98A751926C4@xmb-rcd-x10.cisco.com> <F5063677821E3B4F81ACFB7905573F24D79BE5F0@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71290FA9202@MX15A.corp.emc.com> <000601ce279e$c8ab7940$5a026bc0$@nict.go.jp> <F5063677821E3B4F81ACFB7905573F24DA7FE484@MX15A.corp.emc.com> <D65778B5-1396-4E58-A520-FB9701C85426@cs.georgetown.edu> <1CBD9BD3-18CF-4787-B13E-3288FCB68AE0@cs.georgetown.edu> <5271802E-3724-426D-8DB8-E4718B0092AD@standardstrack.com>
In-Reply-To: <5271802E-3724-426D-8DB8-E4718B0092AD@standardstrack.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
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, 28 Mar 2013 12:35:34 -0000

This page would seem to provide that.

<http://standards.ieee.org/develop/indconn/icsg/mmdef.html>

On 3/27/13 10:25 PM, Eric Burger wrote:
> Did we ever find a stable reference for MMDEF?
>
> On Mar 27, 2013, at 8:59 PM, "Moriarty, Kathleen" <kathleen.moriarty@emc.com> wrote:
>
>> Hello,
>>
>> Thank you for voicing your opinions at the MILE meeting, the two week period is up and we have full agreement.  We will move forward with MMDEF as the MTI for the SCI draft.
>>
>> Take - Thank you for updating the draft to include MMDEF as the MTI as well as the update below.  Could you expand the acronym for MTI in the draft and update the version to the latest?
>>
>> Bets regards,
>> Kathleen
>>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Takeshi Takahashi
>> Sent: Saturday, March 23, 2013 4:17 AM
>> To: mile@ietf.org
>> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>>
>> Hi all,
>>
>> I remember the discussion on the EICAR and agree upon David's kind
>> suggestion.
>> The attached is the revised SCI draft, whose section 10 talks about the
>> EICAR (with an example XML).
>>
>> Kind regards,
>> Take
>>
>>
>>> -----Original Message-----
>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
>>> Black, David
>>> Sent: Thursday, March 14, 2013 11:54 PM
>>> To: Moriarty, Kathleen; mile@ietf.org
>>> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>>>
>>> I support MMDEF as the MTI, and since MMDEF is a malware spec, I'd like to
>>> resurrect a previously-discussed suggestion that the SCI draft include
>>> discussion of the "EICAR Standard Anti-Virus Test File" as a specific
>> example
>>> that SHOULD (or MUST?) be supported for black-box testing purposes.
>>>
>>> See: http://www.eicar.org/86-0-Intended-use.html
>>>
>>> Thanks,
>>> --David
>>>
>>>> -----Original Message-----
>>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
>>>> Of Moriarty, Kathleen
>>>> Sent: Thursday, March 14, 2013 10:38 AM
>>>> To: Panos Kampanakis (pkampana); mile@ietf.org
>>>> Subject: Re: [mile] Consensus Call - SCI draft MMDEF as MTI
>>>>
>>>> Hello Panos,
>>>>
>>>> Thank you for joining us remotely!  The recording is available for
>>>> those who were not able to attend during the session.
>>>>
>>>> We need to choose one included schema as MTI for 'black box' testing
>>>> of the method described.  Essentially, if you can exchange using the
>>>> MTI spec, then any other specs supported should theoretically work as
>>>> the pattern has been established.
>>>>
>>>> MMDEF was recommended as it is in use by the eCrime WG as an
>>> extension
>>>> to IODEF/RFC5901.  It replaced the method to include malware in
>>>> exchanges and seemed to make sense to adopt more broadly as it is
>>>> maintained by a group in IEEE focused on that particular problem.
>>>>
>>>> BTW, I meant to say the last call will end in two weeks from
>>>> yesterday, Wednesday March 27th.
>>>>
>>>> Thank you!
>>>> Kathleen
>>>> ________________________________________
>>>> From: Panos Kampanakis (pkampana) [pkampana@cisco.com]
>>>> Sent: Thursday, March 14, 2013 9:59 AM
>>>> To: Moriarty, Kathleen; mile@ietf.org
>>>> Subject: RE: Consensus Call - SCI draft MMDEF as MTI
>>>>
>>>> I agree with MMDEF included in SCI.
>>>> I am not sure why it must be MTI. Due to some audio problems I missed
>>>> part of the call yesterday. Can you briefly summarize why we want it
>> MTI?
>>>>
>>>> -----Original Message-----
>>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf
>>>> Of Moriarty, Kathleen
>>>> Sent: Wednesday, March 13, 2013 3:04 PM
>>>> To: mile@ietf.org
>>>> Subject: [mile] Consensus Call - SCI draft MMDEF as MTI
>>>>
>>>> Hello,
>>>>
>>>> In today's MILE session, a call for consensus began to include MMDEF
>>>> in the SCI draft as the mandatory-to-implement (MTI) specification.
>>>> The call for consensus will last for 2 weeks and we ask that you
>> contribute
>>> your opinion.
>>>> The vote in the room was unanimous and we want to make sure we hear
>>>> from participants not in attendance.
>>>>
>>>> Poll will end on Wednesday next week.
>>>>
>>>> Thank you!
>>>> Kathleen
>>>> _______________________________________________
>>>> 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
>>>
>>> _______________________________________________
>>> 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
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>
