Re: [mile] Support for IODEF using JSON?
John Field <jfield@pivotal.io> Mon, 17 July 2017 20:40 UTC
Return-Path: <jfield@pivotal.io>
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 51B5612ECC6 for <mile@ietfa.amsl.com>; Mon, 17 Jul 2017 13:40:11 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pivotal-io.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pyNxrMovAse for <mile@ietfa.amsl.com>; Mon, 17 Jul 2017 13:40:08 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B1991300BC for <mile@ietf.org>; Mon, 17 Jul 2017 13:40:08 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id 191so1026925oii.2 for <mile@ietf.org>; Mon, 17 Jul 2017 13:40:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zLgir10p2wdKDhtpbAaDcAiHP+oS/NkN0u0VzGTeNSo=; b=XHTsEdiF1SUcVxxr3yPVFvoTXYSVTdb2lKDqd5sTwNLFfuvLsoG1aUpsGxrXq0MDcN EZJjlO0VAA0A56M2+oB2ZTQN5OBxgFU4xTDw+uug5/dbKrgmvxYYIHYjyJJlvBbrxkkm dTM/9/YUXar70jXkSwW09z3n0r5Ix+c7zjeh2C8exdPMMJz2iEeVaLx6cGmZ5Zegum+r utT+LRipy19rJ3VnAm6iR1oomh7U2I00HKsu0jufoO8gsbUIZZSXuWxf1mKzRRHzMdsm P89Xg6ZBp6Q2Op2KWKenUzcOJkNIVzYfKIFHIzcnEN0RnHLKCWpiRf2Ob+H+0wRFFP0n XnRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zLgir10p2wdKDhtpbAaDcAiHP+oS/NkN0u0VzGTeNSo=; b=n0xduWMq5XOFDJIQUHHCJvdRB5z563+A027GfJ0rDxoSfc6st+4ZrntgSrYA4ltgEX 3P9mAYB1Zkj6FjRGDSlBNt4Xl4lQOyyxq35Yie/SqQeANZgGcEbAAswogPZHmHI4RMp4 JgGGWFOxlsJTd5pu1ilUzw4odcjmZWIO2bjPabQL0fsEq3GfmxwmnrNWUpgK0XAYlob4 UKHYZvoKE32+b73CXg7MXhihe47b06SCLUUGkdriZQzww/waj27IQgIUvvti0b9ZKvpu WNBmV4NWg2+V8zBVJTlnrPVam5KoE0eAyWuvJo6tYG8nyzgT1jel5DwndnNz+gkTpzkK o25g==
X-Gm-Message-State: AIVw1101C7+/vHP5VhyyTbgYUiHOt/7ENmYZKzfFI1FGFBqiKE0s6kzo GRamff2uc6TROYVmqW06djpXbiglM3gI
X-Received: by 10.202.8.14 with SMTP id 14mr17533874oii.68.1500324007861; Mon, 17 Jul 2017 13:40:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.246.166 with HTTP; Mon, 17 Jul 2017 13:40:07 -0700 (PDT)
In-Reply-To: <9324FA98-280A-4EAC-A7DB-952A1E075696@cisco.com>
References: <9324FA98-280A-4EAC-A7DB-952A1E075696@cisco.com>
From: John Field <jfield@pivotal.io>
Date: Mon, 17 Jul 2017 16:40:07 -0400
Message-ID: <CAC0wChHZuYz3QWx1=azpywq3VJ3zWqYAAz_2vNWJ1Nyd47ji+Q@mail.gmail.com>
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
Cc: "mile@ietf.org" <mile@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c13050e8983920554896765"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/uAj4EtVmjv0pPcVaSN_UGy_tSMU>
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: Mon, 17 Jul 2017 20:40:11 -0000
Thanks for posting the question. I believe we SHOULD support IODEF with JSON. Regards, John On Mon, Jul 17, 2017 at 4:17 PM, Nancy Cam-Winget (ncamwing) < ncamwing@cisco.com> wrote: > 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 > > > > _______________________________________________ > mile mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile > > -- John P. Field | Security PM | Pivotal Direct: (908) 962-3394 | jfield@ <jfield@gopivotal.com>pivotal.io
- [mile] Support for IODEF using JSON? Nancy Cam-Winget (ncamwing)
- Re: [mile] Support for IODEF using JSON? John Field
- Re: [mile] Support for IODEF using JSON? Adam Montville
- Re: [mile] Support for IODEF using JSON? Roman Danyliw
- Re: [mile] Support for IODEF using JSON? Patrick Curry
- Re: [mile] Support for IODEF using JSON? Panos Kampanakis (pkampana)
- Re: [mile] Support for IODEF using JSON? Xialiang (Frank)