Re: [mile] Support for IODEF using JSON?
Adam Montville <adam.w.montville@gmail.com> Tue, 18 July 2017 05:12 UTC
Return-Path: <adam.w.montville@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 2A405128C81 for <mile@ietfa.amsl.com>; Mon, 17 Jul 2017 22:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5h1iim5TcDqv for <mile@ietfa.amsl.com>; Mon, 17 Jul 2017 22:12:26 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 31E64120227 for <mile@ietf.org>; Mon, 17 Jul 2017 22:12:26 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id a62so14820864itd.1 for <mile@ietf.org>; Mon, 17 Jul 2017 22:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aG/Ha63QLYlRKydHDK4zOqLEaiu1+xCd/ZlboAZFaQU=; b=eZmpvx24CAq5tQAquK5qM+D/t6y3h4E5C77iGNBfFp+Vgc0WFsCNntbXqSbBmGIooL wVVx+E6PoOaEFbFaJUNG6wN0Z96pWK5es5rW1pywu4HUv3FfDlo3eSDNcku/Zv8u+O2T u7HduIsUt3OggMTymSncy8NgiZKkwndruchwcLy+WAC/0qO9q4PO8dkpVtC5PxqTg1kq zCCrpbIPi5NoBpwGaQGudT7dHzR0XhTyQHEe3DQu4+ntpGDu0Is5QdV4Xl2FuU5RjDf5 0kidJfuDLUs3VbQl6OiMvh782QBrRRa/7FpYTQATXWMdao36U+uiMPdkqL7skK7YopjD BX/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aG/Ha63QLYlRKydHDK4zOqLEaiu1+xCd/ZlboAZFaQU=; b=c3Q+TjkJM4v+KcKdZgvL2nGl93z74KVOghylR6CyZIoUw/UG2a+91/gMbsd8+OEXns Pzev+kE/j61ij953foMIU+fhll7ztRits7dydsVL/HL3zFQpbzRCsNhpDz8JStHR0AwY hQ8uxjntemk0en6oCP5SF84lVL2NLZWU8GpRhf+jeurByBlP6kZ1nwmhws9r7tZe8Xhs gypKhWEZYBeQDpJsQc1cfHWi/6qTZ2KATnJAWahOPZwH8pKGxUrhVt0uUs7A6Bx2zUEm rkbokNVNDhSHwrv2MOOtauFVWpS9V//8Q3pwy07P18P7p9IdXDLVXqB04jEFjZv/mSah R7Lg==
X-Gm-Message-State: AIVw112W11LxKDBmejyYwL8uWqvQr4aYzEfSuZF882J+2uTHiNLuuLOL ZsC190+lF5X1o1IEsPYDtTLwJJovCw==
X-Received: by 10.36.131.10 with SMTP id d10mr828309ite.126.1500354745502; Mon, 17 Jul 2017 22:12:25 -0700 (PDT)
MIME-Version: 1.0
References: <9324FA98-280A-4EAC-A7DB-952A1E075696@cisco.com> <CAC0wChHZuYz3QWx1=azpywq3VJ3zWqYAAz_2vNWJ1Nyd47ji+Q@mail.gmail.com>
In-Reply-To: <CAC0wChHZuYz3QWx1=azpywq3VJ3zWqYAAz_2vNWJ1Nyd47ji+Q@mail.gmail.com>
From: Adam Montville <adam.w.montville@gmail.com>
Date: Tue, 18 Jul 2017 05:12:15 +0000
Message-ID: <CACknUNUbW24ZnUvUm0LUEMiTE99TqzB++KXyYBPPW+HkMTfqUA@mail.gmail.com>
To: John Field <jfield@pivotal.io>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
Cc: "mile@ietf.org" <mile@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c118822a4965a0554908f44"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/4pS1gAGdwedi1m7P7HKrFBn9RfE>
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: Tue, 18 Jul 2017 05:12:28 -0000
+1 On Mon, Jul 17, 2017 at 10:40 PM John Field <jfield@pivotal.io> wrote: > 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 mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile >
- [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)