IETF Logo Mail Archive

Re: [mile] Consensus Call - SCI draft MMDEF as MTI

"Moriarty, Kathleen" <kathleen.moriarty@emc.com> Thu, 14 March 2013 14:38 UTC

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 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

v2.23.0 | Report a Bug | By Email