IETF Logo Mail Archive

Re: [mile] Support for IODEF using JSON?

"Xialiang (Frank)" <frank.xialiang@huawei.com> Thu, 20 July 2017 06:42 UTC

Return-Path: <frank.xialiang@huawei.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 CC4AF1289B0 for <mile@ietfa.amsl.com>; Wed, 19 Jul 2017 23:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fl02QUzWo3Qw for <mile@ietfa.amsl.com>; Wed, 19 Jul 2017 23:42:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4E15127866 for <mile@ietf.org>; Wed, 19 Jul 2017 23:42:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DRP10963; Thu, 20 Jul 2017 06:42:08 +0000 (GMT)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 20 Jul 2017 07:42:07 +0100
Received: from DGGEML502-MBX.china.huawei.com ([169.254.2.84]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0301.000; Thu, 20 Jul 2017 14:41:57 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
CC: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Support for IODEF using JSON?
Thread-Index: AQHS/znETLwq1lMIeEespNpEmryzTaJcSAig
Date: Thu, 20 Jul 2017 06:41:56 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12BB25205@DGGEML502-MBX.china.huawei.com>
References: <9324FA98-280A-4EAC-A7DB-952A1E075696@cisco.com>
In-Reply-To: <9324FA98-280A-4EAC-A7DB-952A1E075696@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.73.101]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12BB25205DGGEML502MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.597050C1.000C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.84, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: fd390e2249ec5efaaadb83882a1bc096
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/_mdFuHVIcn8T07Jqzu_t62h0jJk>
Subject: Re: [mile] Support for IODEF using JSON?
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Jul 2017 06:42:13 -0000

Support.

From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Nancy Cam-Winget (ncamwing)
Sent: Monday, July 17, 2017 10:18 PM
To: mile@ietf.org
Subject: [mile] Support for IODEF using JSON?

Hi,

At today’s f2f MILE session, there was rough consensus to support IODEF with JSON.

We (the chairs) would like to confirm this through the mail group as well.  Please respond to this email
If you believe MILE should or should not add this as a WG item.

Thanks, Nancy

v2.23.0 | Report a Bug | By Email