
From nobody Thu May  1 13:10:50 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DEEF1A6FA9; Thu,  1 May 2014 13:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 EgwJX8FhFbUc; Thu,  1 May 2014 13:10:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C4EA01A0956; Thu,  1 May 2014 13:10:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140501201046.797.49114.idtracker@ietfa.amsl.com>
Date: Thu, 01 May 2014 13:10:46 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/K3oq4FyagHX1QsXOnNb0m3ECeKk
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 01 May 2014 20:10:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Managed Incident Lightweight Exchange Working Group of the IETF.

        Title           : IODEF Usage Guidance
        Author          : Panos Kampanakis
	Filename        : draft-ietf-mile-iodef-guidance-03.txt
	Pages           : 26
	Date            : 2014-05-01

Abstract:
   The Incident Object Description Exchange Format [RFC5070] defines a
   data representation that provides a framework for sharing information
   commonly exchanged by Computer Security Incident Response Teams
   (CSIRTs) about computer security incidents.  Since the IODEF model
   includes a wealth of available options that can be used to describe a
   security incident or issue, it can be challenging for implementers to
   develop tools that can Leverage IODEF for incident sharing.  This
   document provides guidelines for IODEF implementers.  It will also
   address how common security indicators can be represented in IODEF
   and use-cases of how IODEF is being used so far.The goal of this
   document is to make IODEF's adoption by vendors easier and encourage
   faster and wider adoption of the model by Computer Security Incident
   Response Teams (CSIRTs) around the world.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mile-iodef-guidance-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu May  1 13:19:57 2014
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE8381A6FBC for <mile@ietfa.amsl.com>; Thu,  1 May 2014 13:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 jIjFH5tzjXpY for <mile@ietfa.amsl.com>; Thu,  1 May 2014 13:19:55 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 52DE91A0974 for <mile@ietf.org>; Thu,  1 May 2014 13:19:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3518; q=dns/txt; s=iport; t=1398975593; x=1400185193; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=pMJblTGhQ3r5TYjYkIbt9H6OhDhfEIm7ZqN2ukqE4Q0=; b=PSw+XuHmAIaVGRiMNUelPe0vgQ01WRQc17bz1HdHItoVEo+S0ju6KyqF pJSZAvXzaKHCVb+3jVfGB4IU4sI7dLWl3PD7bMseT7jW32YOpwMUzJQ/n lAuzJnTWY5ee+tRgHC+IuO9kAsLuU+7ssOPWfAhtRJI3n7jGDLNs+xuIM M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUGAImrYlOtJV2d/2dsb2JhbABagwZPUQa9HIc+gRQWdIIlAQEBBAEBATc0FwQCAQgRBAEBCxQJBycLFAkIAgQTCAGIOAgFyWoXjiEPKQaDHoEVBJprkTKDM4Ir
X-IronPort-AV: E=Sophos;i="4.97,966,1389744000"; d="scan'208";a="40350948"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 01 May 2014 20:19:52 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s41KJqDF025871 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mile@ietf.org>; Thu, 1 May 2014 20:19:52 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.104]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0123.003; Thu, 1 May 2014 15:19:52 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
Thread-Index: AQHPZXmCtKb5432LC0m3xQBrA8Tvb5ssKX/Q
Date: Thu, 1 May 2014 20:19:51 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A750FBDABEA@xmb-rcd-x10.cisco.com>
References: <20140501201046.797.49114.idtracker@ietfa.amsl.com>
In-Reply-To: <20140501201046.797.49114.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.239.216]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/sATeUFIqk9XKcHp3gRCce1GNeTU
Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 01 May 2014 20:19:57 -0000

Hello,

This is the -03 version of the IODEF guidance draft incorporating Roman's, =
Kathleen's, Trevor's and David's comments so far. The updated made from -02=
 version are=20
   (1)  Added "Updates" section.
   (2)  Added details about the flow of information exchanges in "Inter-
        vendor and Service Provider Exercise" section.  Also updated the
        usecases with more background information.
   (3)  Added future use-cases in the "Collective Intelligence
        Framework" section
   (4)  Updated Perl and Python references with the actual module names.
        Added IODEF implementation reference "implementations".
   (5)  Added Predicate logic section
   (6)  Updated Logic of watchlist of indicators section to simplify the
        logic and include examples.
   (7)  Renamed Externally defined indicators section to Indicator
        reference and elaborated on the use of indicator-uid and
        indicator-set-uid attribute use.

It is still not complete and some sections need to be expanded. I will now =
work on -04 and hopefully will have a more complete version in a couple of =
months.

Feedback and reviews are welcome.

Regards,
Panos



-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Thursday, May 01, 2014 4:11 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Managed Incident Lightweight Exchange Wor=
king Group of the IETF.

        Title           : IODEF Usage Guidance
        Author          : Panos Kampanakis
	Filename        : draft-ietf-mile-iodef-guidance-03.txt
	Pages           : 26
	Date            : 2014-05-01

Abstract:
   The Incident Object Description Exchange Format [RFC5070] defines a
   data representation that provides a framework for sharing information
   commonly exchanged by Computer Security Incident Response Teams
   (CSIRTs) about computer security incidents.  Since the IODEF model
   includes a wealth of available options that can be used to describe a
   security incident or issue, it can be challenging for implementers to
   develop tools that can Leverage IODEF for incident sharing.  This
   document provides guidelines for IODEF implementers.  It will also
   address how common security indicators can be represented in IODEF
   and use-cases of how IODEF is being used so far.The goal of this
   document is to make IODEF's adoption by vendors easier and encourage
   faster and wider adoption of the model by Computer Security Incident
   Response Teams (CSIRTs) around the world.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-iodef-guidance-03


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile


From nobody Wed May  7 04:55:46 2014
Return-Path: <david.waltermire@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4CB1A06F7 for <mile@ietfa.amsl.com>; Wed,  7 May 2014 04:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 sOoswaG7W9PC for <mile@ietfa.amsl.com>; Wed,  7 May 2014 04:55:43 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id 475971A02A5 for <mile@ietf.org>; Wed,  7 May 2014 04:55:43 -0700 (PDT)
Received: from BN1PR09MB0137.namprd09.prod.outlook.com (10.255.192.139) by BN1PR09MB0137.namprd09.prod.outlook.com (10.255.192.139) with Microsoft SMTP Server (TLS) id 15.0.934.12; Wed, 7 May 2014 11:55:38 +0000
Received: from BN1PR09MB0137.namprd09.prod.outlook.com ([10.255.192.139]) by BN1PR09MB0137.namprd09.prod.outlook.com ([10.255.192.139]) with mapi id 15.00.0934.000; Wed, 7 May 2014 11:55:38 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: IETF 90 Meeting Conflicts
Thread-Index: AQHPaetBRK9gz+hMRUi9fLaMRD3dGA==
Date: Wed, 7 May 2014 11:55:37 +0000
Message-ID: <35b2f4ac53d1419790496ebe5772eb14@BN1PR09MB0137.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.16.52]
x-forefront-prvs: 0204F0BDE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(164054003)(77982001)(79102001)(46102001)(66066001)(99286001)(21056001)(80022001)(64706001)(76576001)(4396001)(20776003)(74502001)(74662001)(31966008)(558084003)(85852003)(101416001)(74316001)(86362001)(99396002)(81342001)(83072002)(50986999)(2656002)(87936001)(33646001)(92566001)(83322001)(81542001)(54356999)(77096999)(76482001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR09MB0137; H:BN1PR09MB0137.namprd09.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: nist.gov does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=david.waltermire@nist.gov; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/7tom4yJwltw58TvSZkM11Dtc_1I
Subject: [mile] IETF 90 Meeting Conflicts
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 07 May 2014 11:55:44 -0000

I am working on scheduling the MILE wg meeting for IETF 90. Are there meeti=
ng conflicts that we should avoid other than SACM?=0A=
=0A=
Thanks,=0A=
Dave=


From nobody Wed May  7 11:38:06 2014
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C86781A0828 for <mile@ietfa.amsl.com>; Wed,  7 May 2014 11:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ysJGTxBRzP7l for <mile@ietfa.amsl.com>; Wed,  7 May 2014 11:38:03 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 771331A07D6 for <mile@ietf.org>; Wed,  7 May 2014 11:38:03 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id z6so883743yhz.11 for <mile@ietf.org>; Wed, 07 May 2014 11:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nrfx2Svpn2GA2DcGUzjjMSQU/qV2W0dngWjV34EojvM=; b=c7qE78qNa0ceVvC6bV4CcfBtNtY0MEgW8jHNjCAdV41sAaCJ8vmu7ie8kjlytFgs04 q1IxVb7TMOiy7XM6VPHVGNS0KhqaSIm4utOzmhG3n3/Rkh8EuRH8lCPb4ViL5j5fgoGS KSDbhV00naQMnUlh7XRvyRqBkQd1GchseDj6gqAEtQt8DDijloKC8cIHlPieWA8CZn0S bimc5ZBUZB4rppaWBTQsDbXzLsBrsTyjoO2r1oqeYt64JJXE2oc0D1gS6fucGUM4URj4 O/qTqNjH4pMevsXRFQYIJySZDRj8n8PZ3NigLKZCdx4Lk4CHoOQSZkNpRZP77r0LwlIM MqUw==
X-Received: by 10.236.200.67 with SMTP id y43mr70545662yhn.77.1399487879154; Wed, 07 May 2014 11:37:59 -0700 (PDT)
Received: from [10.136.62.48] ([166.170.58.225]) by mx.google.com with ESMTPSA id j76sm28251965yhi.33.2014.05.07.11.37.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 May 2014 11:37:57 -0700 (PDT)
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (11D167)
In-Reply-To: <35b2f4ac53d1419790496ebe5772eb14@BN1PR09MB0137.namprd09.prod.outlook.com>
Date: Wed, 7 May 2014 13:37:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <12A017CF-9064-4BB3-8FAF-E8AE07E3EBF0@gmail.com>
References: <35b2f4ac53d1419790496ebe5772eb14@BN1PR09MB0137.namprd09.prod.outlook.com>
To: "Waltermire, David A." <david.waltermire@nist.gov>
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/8YKEyIHZEqbLHUMGhODEOwdgM0w
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] IETF 90 Meeting Conflicts
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 07 May 2014 18:38:04 -0000

Please add SAAG to the list.  We usually had that and ones that had conflict=
s for the chairs (co-chairing other sessions).

Thanks,
Kathleen=20

Sent from my iPhone

> On May 7, 2014, at 6:55 AM, "Waltermire, David A." <david.waltermire@nist.=
gov> wrote:
>=20
> I am working on scheduling the MILE wg meeting for IETF 90. Are there meet=
ing conflicts that we should avoid other than SACM?
>=20
> Thanks,
> Dave
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Wed May  7 16:28:32 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDFC1A0441; Wed,  7 May 2014 16:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 YpSqAUburj7x; Wed,  7 May 2014 16:28:11 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE051A043F; Wed,  7 May 2014 16:28:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140507232811.8881.80911.idtracker@ietfa.amsl.com>
Date: Wed, 07 May 2014 16:28:11 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/ObO0NbIfh_s_dPInL9KEV7catTw
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-enum-reference-format-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 07 May 2014 23:28:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Managed Incident Lightweight Exchange Working Group of the IETF.

        Title           : IODEF Enumeration Reference Format
        Authors         : Adam W. Montville
                          David Black
	Filename        : draft-ietf-mile-enum-reference-format-04.txt
	Pages           : 8
	Date            : 2014-05-07

Abstract:
   The Incident Object Description Exchange Format [IODEF] provides a
   Reference class used to reference external entities (such as
   enumeration identifiers).  However, the method of external entity
   identification has been left unstructured.  This document describes a
   method to provide structure for referencing external entities for the
   [IODEF] Reference class.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mile-enum-reference-format-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu May  8 04:30:51 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DECE61A029B for <mile@ietfa.amsl.com>; Thu,  8 May 2014 04:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.856
X-Spam-Level: *
X-Spam-Status: No, score=1.856 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 RVy4FmK_l3YT for <mile@ietfa.amsl.com>; Thu,  8 May 2014 04:30:47 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB08A1A042C for <mile@ietf.org>; Thu,  8 May 2014 04:30:44 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id s48BUdij012747; Thu, 8 May 2014 20:30:39 +0900 (JST)
Received: from mail1.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp  with ESMTP id s48BUdVI022125; Thu, 8 May 2014 20:30:39 +0900 (JST)
Received: from mail1.nict.go.jp (localhost [127.0.0.1]) by mail1.nict.go.jp (NICT Mail) with ESMTP id 50F7016435; Thu,  8 May 2014 20:30:39 +0900 (JST)
Received: from VAIO (unknown [133.243.119.184]) by mail1.nict.go.jp (NICT Mail) with ESMTP id 448BE16416; Thu,  8 May 2014 20:30:39 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Thu, 8 May 2014 20:30:43 +0900
Message-ID: <01e401cf6ab0$f2a08c30$d7e1a490$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9qsA+FzhqqrW29RBS5A/ti/OBQiA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith1
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/Pl_OHh8JOding8WusvDFbHdTKl0
Cc: mile-chairs@tools.ietf.org
Subject: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 08 May 2014 11:30:49 -0000

Greetings, all,

This is the Working Group Last Call for
draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference Format.

The last call starts now, and ends Monday 26 May 2014.

Please read the latest revision of the draft,
http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, and
send your comments to the mailing list; we'd also appreciate a comment if
you're fine with the draft as is.

Many thanks, and best regards,

Take




From nobody Thu May  8 09:28:37 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1201A0052; Thu,  8 May 2014 09:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 5BfnZylEmTpg; Thu,  8 May 2014 09:28:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id BA9DA1A0074; Thu,  8 May 2014 09:28:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7AB8B180014; Thu,  8 May 2014 09:27:49 -0700 (PDT)
To: ietf@augustcellars.com, Kathleen.Moriarty@emc.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140508162749.7AB8B180014@rfc-editor.org>
Date: Thu,  8 May 2014 09:27:49 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/kQVtymnIBYfuA2yp_pBgrdAFcVA
Cc: mile@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org, stephen.farrell@cs.tcd.ie
Subject: [mile] [Errata Verified] RFC6545 (3939)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 08 May 2014 16:28:33 -0000

The following errata report has been verified for RFC6545,
"Real-time Inter-network Defense (RID)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6545&eid=3939

--------------------------------------
Status: Verified
Type: Technical

Reported by: Jim Schaad <ietf@augustcellars.com>
Date Reported: 2014-03-29
Verified by: Stephen Farrell (IESG)

Section: 7.1.1

Original Text
-------------
      <iodef-rid:XMLDocument dtype="xml" meaning="xml">
       <IODEF-Document lang="en">
        <iodef:Incident purpose="traceback" restriction="need-to-know">
          <iodef:IncidentID name="CERT-FOR-OUR-DOMAIN">
                           CERT-FOR-OUR-DOMAIN#207-1
          </iodef:IncidentID>


Corrected Text
--------------
      <iodef-rid:XMLDocument dtype="xml" meaning="xml">
       <iodef:IODEF-Document lang="en">
        <iodef:Incident purpose="traceback" restriction="need-to-know">
          <iodef:IncidentID name="CERT-FOR-OUR-DOMAIN">
                           CERT-FOR-OUR-DOMAIN#207-1
          </iodef:IncidentID>


Notes
-----
The IODEF-Document node (both opening and closing) are missing the namespace prefix.  Without this, the contents of the node will not be correctly validated.

(Change is in line 2 above.  The closing tag change is the same, but is not part of the delta change above.)

--------------------------------------
RFC6545 (draft-ietf-mile-rfc6045-bis-11)
--------------------------------------
Title               : Real-time Inter-network Defense (RID)
Publication Date    : April 2012
Author(s)           : K. Moriarty
Category            : PROPOSED STANDARD
Source              : Managed Incident Lightweight Exchange
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu May  8 09:29:30 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D7A1A0095; Thu,  8 May 2014 09:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 mQ7Th25SObT7; Thu,  8 May 2014 09:29:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id C792F1A0052; Thu,  8 May 2014 09:29:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 853EA180454; Thu,  8 May 2014 09:28:46 -0700 (PDT)
To: ietf@augustcellars.com, Kathleen.Moriarty@emc.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140508162846.853EA180454@rfc-editor.org>
Date: Thu,  8 May 2014 09:28:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/BJQmGNLyTVKSzI42P-erGId6YD4
Cc: mile@ietf.org, rfc-editor@rfc-editor.org, iesg@ietf.org, stephen.farrell@cs.tcd.ie
Subject: [mile] [Errata Verified] RFC6545 (3940)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 08 May 2014 16:29:30 -0000

The following errata report has been verified for RFC6545,
"Real-time Inter-network Defense (RID)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6545&eid=3940

--------------------------------------
Status: Verified
Type: Technical

Reported by: Jim Schaad <ietf@augustcellars.com>
Date Reported: 2014-03-29
Verified by: Stephen Farrell (IESG)

Section: 5.4

Original Text
-------------
<RID-Document version="2.0" lang="en-US"
      xmlns:iodef-rid="urn:ietf:params:xml:ns:iodef-rid-2.0"
      xmlns:xsi="http://www.w3c.org/2001/XMLSchema-instance"
      xsi:schemaLocation="urn:ietf:params:xml:ns:iodef-rid-2.0.xsd">


Corrected Text
--------------
<iodef-rid:RID version="2.0" lang="en-US"
      xmlns:iodef-rid="urn:ietf:params:xml:ns:iodef-rid-2.0"
      xmlns:xsi="http://www.w3c.org/2001/XMLSchema-instance"
      xsi:schemaLocation="urn:ietf:params:xml:ns:iodef-rid-2.0.xsd
http://www.iana.org/assignments/xml-registry/schema/iodef-rid-2.0.xsd">


Notes
-----
Two errors in the text are fixed:

1.  The root node is incorrect.  It does not have a namespace declared for the root node and there is no node named RID-Document in the schema that is declared.  The correct root node is RID and it should have the rid v2 name space

2.  The schemaLocation is a pair of text strings in this location.  The first is the namespace and the second is a location to get the schema for that namespace.  An alternative is to omit the attribute as any application that is loading this document should already have the schema and should never need to go out and fetch it.

--------------------------------------
RFC6545 (draft-ietf-mile-rfc6045-bis-11)
--------------------------------------
Title               : Real-time Inter-network Defense (RID)
Publication Date    : April 2012
Author(s)           : K. Moriarty
Category            : PROPOSED STANDARD
Source              : Managed Incident Lightweight Exchange
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu May  8 10:19:33 2014
Return-Path: <david.waltermire@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E791A0079 for <mile@ietfa.amsl.com>; Thu,  8 May 2014 10:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 XjI9FzjLmAj4 for <mile@ietfa.amsl.com>; Thu,  8 May 2014 10:19:29 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0139.outbound.protection.outlook.com [207.46.163.139]) by ietfa.amsl.com (Postfix) with ESMTP id E4BF41A0078 for <mile@ietf.org>; Thu,  8 May 2014 10:19:28 -0700 (PDT)
Received: from BN1PR09MB0137.namprd09.prod.outlook.com (10.255.192.139) by BN1PR09MB0139.namprd09.prod.outlook.com (10.255.192.141) with Microsoft SMTP Server (TLS) id 15.0.939.12; Thu, 8 May 2014 17:19:23 +0000
Received: from BN1PR09MB0137.namprd09.prod.outlook.com ([10.255.192.139]) by BN1PR09MB0137.namprd09.prod.outlook.com ([10.255.192.139]) with mapi id 15.00.0934.000; Thu, 8 May 2014 17:19:22 +0000
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: [mile] IETF 90 Meeting Conflicts
Thread-Index: AQHPaetBRK9gz+hMRUi9fLaMRD3dGJs1cxWAgAF8BwA=
Date: Thu, 8 May 2014 17:19:21 +0000
Message-ID: <4c9979f4c08744c4afbdf44831a7271c@BN1PR09MB0137.namprd09.prod.outlook.com>
References: <35b2f4ac53d1419790496ebe5772eb14@BN1PR09MB0137.namprd09.prod.outlook.com> <12A017CF-9064-4BB3-8FAF-E8AE07E3EBF0@gmail.com>
In-Reply-To: <12A017CF-9064-4BB3-8FAF-E8AE07E3EBF0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.227.61]
x-forefront-prvs: 0205EDCD76
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(164054003)(13464003)(199002)(189002)(24454002)(51704005)(377454003)(76576001)(19580395003)(74316001)(76482001)(74662001)(92566001)(46102001)(19580405001)(86362001)(83072002)(66066001)(74502001)(83322001)(85852003)(101416001)(21056001)(15975445006)(81342001)(81542001)(79102001)(33646001)(77096999)(2656002)(87936001)(99286001)(99396002)(50986999)(31966008)(77982001)(64706001)(76176999)(20776003)(80022001)(4396001)(54356999)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR09MB0139; H:BN1PR09MB0137.namprd09.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: nist.gov does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=david.waltermire@nist.gov; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/xM1UVoZ5t3gyu9lt7ll1i3s9fAc
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] IETF 90 Meeting Conflicts
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 08 May 2014 17:19:31 -0000

Thanks. I'll submit the request with SAAG and SACM as conflicts.

Thanks,
Dave

-----Original Message-----
From: Kathleen Moriarty [mailto:kathleen.moriarty.ietf@gmail.com]=20
Sent: Wednesday, May 07, 2014 2:38 PM
To: Waltermire, David A.
Cc: mile@ietf.org
Subject: Re: [mile] IETF 90 Meeting Conflicts

Please add SAAG to the list.  We usually had that and ones that had conflic=
ts for the chairs (co-chairing other sessions).

Thanks,
Kathleen=20

Sent from my iPhone

> On May 7, 2014, at 6:55 AM, "Waltermire, David A." <david.waltermire@nist=
.gov> wrote:
>=20
> I am working on scheduling the MILE wg meeting for IETF 90. Are there mee=
ting conflicts that we should avoid other than SACM?
>=20
> Thanks,
> Dave
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Fri May  9 04:17:33 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F801A0282 for <mile@ietfa.amsl.com>; Fri,  9 May 2014 04:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.857
X-Spam-Level: ***
X-Spam-Status: No, score=3.857 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 7o7W5NjjNJHj for <mile@ietfa.amsl.com>; Fri,  9 May 2014 04:17:27 -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 586F01A0277 for <mile@ietf.org>; Fri,  9 May 2014 04:17:27 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id s49BHMA8001752 for <mile@ietf.org>; Fri, 9 May 2014 20:17:22 +0900 (JST)
Received: from mail3.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp  with ESMTP id s49BHMge013215 for <mile@ietf.org>; Fri, 9 May 2014 20:17:22 +0900 (JST)
Received: from mail3.nict.go.jp (localhost [127.0.0.1]) by mail3.nict.go.jp (NICT Mail) with ESMTP id E7E351664B for <mile@ietf.org>; Fri,  9 May 2014 20:17:21 +0900 (JST)
Received: from VAIO (unknown [133.243.119.184]) by mail3.nict.go.jp (NICT Mail) with ESMTP id DF7F516649 for <mile@ietf.org>; Fri,  9 May 2014 20:17:21 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Fri, 9 May 2014 20:17:26 +0900
Message-ID: <000001cf6b78$42243370$c66c9a50$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9reC5fiwDq2RjISkSLThbiXH9Rfw==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith2
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/ejyFPgKE39ParFbOCIJkrLp_OV4
Subject: Re: [mile] Fwd: New Version Notification for draft-murillo-mile-cps-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 09 May 2014 11:17:30 -0000

Hi Martin,

Thank you for your kind comments.

> There's one question that still lingers: whether we should not 
> re-utilize other extensions or use the IODEF-extension for structured 
> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the 
> points above would be applicable to both scenarios.

I like this CPS draft, but I also like IODEF-SCI's framework (well, I am one
of the authors).
I do not want to be the obstacle of developing this interesting work, so I
do not have any intention to stick to IODEF-SCI at all.
But I would like to understand the pros and cons of not using SCI framework
for the CPS extension more vividly.

Section 1.7 of the CPS draft explains the reason for not using the
IODEF-SCI's framework, but it was not so clear to me..
Can we discuss this issue when we have got example XML documents of the CPS
extension? (I guess later version of the CPS draft will have the example XML
documents?) Then we can compare how the XML documents will look like for
each case of using and not using IODEF-SCI framework on the CPS extension.

Kind regards,
Take


> -----Original Message-----
> From: Martin Murillo [mailto:murillo@ieee.org]
> Sent: Wednesday, April 30, 2014 12:30 PM
> To: Takeshi Takahashi; mile@ietf.org
> Subject: Re: [mile] Fwd: New Version Notification for 
> draft-murillo-mile-cps-00.txt
> 
> Dear Takeshi,
> 
> Thanks for the feedback and highlighting various extraneous elements 
> which have rich IODEF equivalents. This makes the reporting lighter 
> and decreases implementation overhead. I have answered to each item below.
> 
> 1. The IncidentType element specifies whether the incident is 
> accidental, on purpose, or theresult of other actions. The IncdntType 
> attribute is missplaced. Thanks for taking notice of that. However I 
> wonder whether the IncidentType element should be renamed. I think we 
> agree that we need a field where whether the incident is accidental, 
> on purpose, or undetermined can be placed. While the nature of the 
> incident is rarely known immediately, there are instances in which the 
> operator or other local party causes accidental instances; these 
> instances might cause repercussions in other locations (i.e. balancing in
an electric grid).
> 
> 2. I agree with you, the IncidentTilte element is a perfect candidate 
> to go to a shallower level, especially when it will be the first 
> variable that an operator or appropriate party reads.
> 
> 3. Given that the IODEF:Contact class is rich enough to differentiate 
> between a reporting party and an additional contact 
> person/institution, I believe that we should use such class. Because 
> the different stakeholders responsible for the Corporate Network, 
> Control Servers, and Field Devices, this class might need to be 
> extended. This is also relevant when the attack has taken place at any 
> of those levels: For instance, the Corporate Network (or a false 
> impersonator) might instruct the control room (Control servers) wrong 
> setpoint configurations. Or the Control Network might experience a 
> breach and setpoints altered in such servers. In extreme situations, the
attacks might be directly to the field devices. In each of those cases.
> In each of those cases the contact person might be one or more.
> 
> 4, 5, 6. I think the IODEF classes can be indeed used. Thank you. The 
> extension capabilities fo the System Class makes it quite appropriate 
> to offer rich information.
> 
> Regarding your last point, SFK should indeed be used instead of SFC.
> 
> There's one question that still lingers: whether we should not 
> re-utilize other extensions or use the IODEF-extension for structured 
> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the 
> points above would be applicable to both scenarios.
> 
> Martin
> 
> On 4/23/2014 4:42 AM, Takeshi Takahashi wrote:
> > Hi Martin,
> >
> > I've read through the drafts. Thank you very much for sharing your 
> > expertise here.
> > It was a new use case for me, and was really interesting.
> >
> > I am wondering if we can minimize the number of extension fields by 
> > using the existing IODEF fields.
> > By minimizing the number of similar fields, I hope we can simplify 
> > the draft and minimize the burden of implementations.
> >
> > >From this viewpoint, let me ask several checking questions.
> >
> > 1. IncidentType element and IncdntType Attribute
> >    What are the difference between them? I think your current draft 
> > has them as place holders. I would like to hear a bit further.
> >
> > 2. The IncidentTitle element
> >    Can we use the Description element inside the IODEF:Incident 
> > class for this purpose, instead of having new field here?
> >    It would be useful to have title or such information that can 
> > hint the content of the IODEF document, but I feel like that it 
> > would be helpful to have this type of information at the shallower 
> > level of IODEF document rather than having it in the deeper level of 
> > IODEF document (inside
> > additionalData)
> >
> > 3. The ReportingParty element
> >    Can we use the IODEF:contact class instead of having new field? 
> > We could extend it further if needed.
> >
> > 4. The ReportReliability element
> >    Can we use the IODEF:confidence class instead of having new field?
> > We could extend it further if needed.
> >
> > 5. The TargetSystems element
> >    Can we extend the IODEF:system class instead of having new field?
> > We could extend it further if needed.
> >
> > 6. type attribute of the IODEF:Impact class
> >    When we use this extension, what value should be set for the type 
> > attribute of the IODEF:Impact class?
> >
> > By the way, here are small questions.
> >
> > 1. should [SFC] be [SFK], since the acronym seems to come from the 
> > initials of the authors of the reference (Stouffer, K., Falco, J., 
> > and
> K. Scarfonw) ?
> >
> > I might have misunderstood your draft, so please correct me if I am
wrong.
> >
> > Kind regards,
> > Take
> >
> >
> >> -----Original Message-----
> >> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Martin 
> >> Murillo
> >> Sent: Wednesday, January 29, 2014 10:11 AM
> >> To: Johnson, Blake; Jerome Athias
> >> Cc: mile@ietf.org
> >> Subject: Re: [mile] Fwd: New Version Notification for 
> >> draft-murillo-mile-cps-00.txt
> >>
> >> Have read the links posted by Jerome and info on the Experience 
> >> Sharing Tool (EST). It is my impression that a revision under the 
> >> light of the EST would be very appropriate, and one of the first 
> >> uses of the extension, given its report-based nature.  Look forward 
> >> to seeing
> > the reviews in this light.
> >> As Jerome mentioned, focusing on referencing already existing 
> >> taxonomies (and when necessary reusing them and referencing their 
> >> xml implementations, if publicly available) would be the best 
> >> approach; given the early stages in the field, I tend to think that 
> >> atomic data will
> > need to be used.
> >> Regarding the term "Asset" vs "System", I believe system provides a 
> >> more general connotation, while asset, seem to focus more on 
> >> mainstream infrastructure; because the inclusion of IoT-related 
> >> infrastructure (anywhere from centralized home control to 
> >> self-driving cars), I wonder whether "Asset" is too an specific term.
> >>
> >> Martin
> >>
> >> Martin
> >>
> >> On 1/24/2014 2:09 PM, Johnson, Blake wrote:
> >>> This is an interesting application of IODEF that I had not considered.
> >> Most industry sharing that takes place in this space, from my 
> >> perspective, is in the form of in person and telephone threat 
> >> briefings. These are facilitated by the FBI, DHS, and the ISAC's.
> >>> At least a handful of the ISAC's have started sharing structured 
> >>> threat
> >> indicator data, and the taxonomy for this extension could cover 
> >> what the Electric Sector ISAC currently refers to as 'Experience
Sharing.'
> >> I can review this proposal as it relates to information captured by 
> >> the ES-ISAC's Experience Sharing tool, using IEC/ANSI 62443 (ISA99) 
> >> as an informative reference.
> >>> Blake Johnson
> >>> Threat Intelligence Analyst
> >>> Alliant Energy | Infrastructure Secruity
> >>> Office: 608-458-6320 | Cell: 608-843-2790
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Jerome 
> >>> Athias
> >>> Sent: Friday, January 24, 2014 3:18 AM
> >>> To: murillo@ieee.org
> >>> Cc: mile@ietf.org
> >>> Subject: Re: [mile] Fwd: New Version Notification for 
> >>> draft-murillo-mile-cps-00.txt
> >>>
> >>> Hi,
> >>>
> >>> from what I know (which is limited), and as you mention, this ICS 
> >>> area is often also called Critical Infrastructures (CIs), or SCADA
> >>>
> >>> for a little bit of background, we could explore the Cybersecurity 
> >>> Framework Example references 
> >>> http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
> >>>
> >>
> http://www.ictqatar.qa/en/documents/download/National%20Industrial%20
> >> C
> >>> ontrol%20Systems%20Security%20Standard-English.pdf
> >>> ANSI/ISA-99.02.01-2009
> >>>
> >>> I don't have enough knowledge about the status and adoption of the 
> >>> different efforts in term of XML representation/format/standards 
> >>> http://xml.coverpages.org/emergencyManagement.html
> >>> and resilience
> >>>
> >>> It would maybe be possible to obtain information from there 
> >>> http://ics-cert.us-cert.gov http://ics-isac.org/
> >>>
> >>> My first feedback is that it looks like an interesting extension.
> >>>
> >>> I would suggest to focus on the reuse of existing Taxonomies, or 
> >>> references to them.
> >>>
> >>> As such, for [Industry], maybe
> >>> http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012
> >>> ISO 3166 (Country Codes)
> >>>
> >>>
> >>> [TargetSystems], I (personally) don't like the word "system" and 
> >>> prefer
> >> "asset"
> >>> [CompromisedPhysicalInfrastrucute] (with a typo ;p) seems to be a 
> >>> category of "Infrastructure" (or group of assets)
> >>>
> >>>
> >>> [EntryPoint] could be ok since it could be a little bit different 
> >>> from "endpoint"
> >>>
> >>> [PerpetratingParty] seems to reference "Threat Actor" or "Threat 
> >>> Agent" or "Attacker"
> >>>
> >>> [RecurrencePreventionMeasures] is this Security Controls? (and
> >>> Mitigations/Remediations)
> >>> Reference:
> >>>
> https://web.nvd.nist.gov/view/800-53/control?controlName=AC-3&type=1
> >>>
> >>>
> >>> Describing an [Exploit] is not so easy (depending on the level of 
> >>> details wanted/needed)
> >>>
> >>> Figure 1 (or "Diagram 1") is interesting, (of course it is 
> >>> different from, i.e. CAESARS), it MAYBE could be more layered
> >>>
> >>
> http://www.isa.org/InTechTemplate.cfm?template=/ContentManagement/Con
> >> t
> >>> entDisplay.cfm&ContentID=94401
> >>>
> >>> (To follow: ENISA CDXI)
> >>>
> >>>
> >>> Some typos
> >>>
> >>>
> >>>
> >>> Next step: more XML focused ;)
> >>>
> >>>
> >>> My 2 bitcents
> >>>
> >>> 2014/1/24 Martin Murillo <murillo@ieee.org>:
> >>>> Dear all,
> >>>>
> >>>> Please find below a link to a proposed draft for extending IODEF 
> >>>> for the reporting of cyber-physical system incidents. These 
> >>>> systems are often referred as  Operational Technology Systems, 
> >>>> Industrial Control Systems, Automatic Control  Systems, or simply 
> >>>> Control
> Systems.
> >>>>
> >>>> Cyber-Physical systems have been around for decades.  However, 
> >>>> they are now at a higher risk to be  the target of attacks by 
> >>>> individual highly-skilled attackers, organized groups, 
> >>>> nation-states, or simply suffer repercussions of mainstream IT 
> >>>> cyber-attacks. While over 90% of critical control system 
> >>>> infrastructure is currently owned by private enterprises, these 
> >>>> can have direct repercussions on national security of world 
> >>>> nations.  Indeed, various of these systems are key parts of 
> >>>> nuclear reactor facilities, transportation systems, electric 
> >>>> power distribution, oil and natural gas distribution, health 
> >>>> care, water
> >> and waste-water treatment, dam infrastructure, missile
> >>>> and defense systems, and others.   The disruption of these control
> >> systems
> >>>> could have a significant impact on public health, safety, and 
> >>>> lead to large economic losses.
> >>>>
> >>>> Among the issues that catalyze this higher risk are:
> >>>>
> >>>> i) these systems are gradually becoming more interconnected, ii) 
> >>>> legacy systems do not have proper cybersecurity protection, iii) 
> >>>> the existence of highly-skilled individuals and motivations, iv) 
> >>>> some these systems are generally considered critical, v) these 
> >>>> are a natural extension of IT cyber-attacks, vi) the emergence of 
> >>>> the Internet of Things (IOT), and vi) these attacks can be 
> >>>> carried out
> >> remotely and quite inexpensively.
> >>>> While there might exist national approaches to deal with 
> >>>> incidents, there's the need of a global international approach 
> >>>> that will engulf governments, private organizations and other
stakeholders.
> >>>> IETF, as a leading global Internet standards organization, seeks 
> >>>> to satisfy this need through open standards that seek to 
> >>>> encompass issues that are critical for the global community.
> >>>>
> >>>> Feedback at two levels are welcome:
> >>>>
> >>>> 1. On the existence and inclusion either by utilizing any already
> > existing
> >>>> industry formats (XML-   encoded) and/or by utilizing atomic data
> >>>> 2. Contributions on making the extension (and background
> >>>> information) more comprehensive, accurate and principally useful 
> >>>> for the community
> >>>>
> >>>> Look forward to feedback and other input!
> >>>>
> >>>> Martin Murillo
> >>>>
> >>>> A new version of I-D, draft-murillo-mile-cps-00.txt has been 
> >>>> successfully submitted by Martin Murillo and posted to the IETF 
> >>>> repository.
> >>>>
> >>>> Name:           draft-murillo-mile-cps
> >>>> Revision:       00
> >>>> Title:          IODEF extension for Reporting Cyber-Physical System
> >>>> Incidents
> >>>> Document date:  2014-01-21
> >>>> Group:          Individual Submission
> >>>> Pages:          24
> >>>> URL:
> >>>> http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt
> >>>> Status:
> >> https://datatracker.ietf.org/doc/draft-murillo-mile-cps/
> >>>> Htmlized:
> http://tools.ietf.org/html/draft-murillo-mile-cps-00
> >>>>
> >>>>
> >>>> Abstract:
> >>>>     This draft document will extend the Incident Object Description
> >>>>     Exchange Format (IODEF) defined in [RFC5070] to support the
> >> reporting
> >>>>     of incidents dealing with attacks to physical infrastructure
> > through
> >>>>     the utilization of IT means as a vehicle or as a tool.  These
> > systems
> >>>>     might also be referred as Cyber-Physical Systems (CPS),
> Operational
> >>>>     Technology Systems, Industrial Control Systems, Automatic
> Control
> >>>>     Systems, or simply Control Systems.  These names are used
> >>>>     interchangeably in this document.  In this context, an 
> >>>> incident
> is
> >>>>     generally the result of a cybersecurity issue whose main goal 
> >>>> is
> >> to
> >>>>     affect the operation of a CPS.  It is considered that any
> >>>>     unauthorized alteration of the operation is always malign.  This
> >>>>     extension will provide the capability of embedding structured
> >>>>     information, such as identifier- and XML-based information.  
> >>>> In
> its
> >>>>     current state, this document provides important 
> >>>> considerations
> for
> >>>>     further work in implementing Cyber-Physical System incident
> >> reports,
> >>>>     either by utilizing any already existing industry formats (XML-
> >>>>     encoded) and/or by utilizing atomic data.
> >>>>
> >>>>     In addition, this document should provide appropriate 
> >>>> material
> for
> >>>>     helping making due considerations in making an appropriate
> decision
> >>>>     on how a CPS reporting is done: 1) through a data format 
> >>>> extension
> >> to
> >>>>     the Incident Object Description Exchange Format [RFC5070], 2)
> >> forming
> >>>>     part of an already existing IODEF-extension for structured
> >>>>     cybersecurity information (currently draft
> >>>>     draft-ietf-mile-sci-11.txt), or others.  While the format and
> >>>>     contents of the present document fit more the earlier option,
these
> >>>>     can also be incorporated to the later.
> >>>>
> >>>>
> >>>>
> >>>> Please note that it may take a couple of minutes from the time of 
> >>>> submission until the htmlized version and diff are available at
> >> tools.ietf.org.
> >>>> The IETF Secretariat
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >
> >


From nobody Sun May 11 12:48:18 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213291A0340 for <mile@ietfa.amsl.com>; Sun, 11 May 2014 12:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 4H0IQ0KQY25J for <mile@ietfa.amsl.com>; Sun, 11 May 2014 12:48:15 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 6E66A1A033D for <mile@ietf.org>; Sun, 11 May 2014 12:48:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1399837689; d=isode.com; s=selector; i=@isode.com; bh=ubCYCUI3pRCqurQJpcSh+efqhGR2QBumvgbjnGxrxag=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=EdwYhBjqdqnEHnbUo9Oq0Ym20Ql9bumK/lNL/eayZbcbZM77L+9nBCyrv3tpRL5+dXkevD vn55SjNvlrJrdUKf8pvSlJaQ7t6Z8P7e4P9+v/pH/8ShDxsmlmP6gGGTqJ0dOUDrij/m1Y KZ37whHrwmT79LRAn3riaFZEVAdny4k=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <U2=T-ABCkqvG@statler.isode.com>; Sun, 11 May 2014 20:48:09 +0100
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-Id: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com>
Date: Sun, 11 May 2014 20:54:53 +0100
To: "<mile@ietf.org>" <mile@ietf.org>
X-Mailer: iPad Mail (11D201)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/_0N-p2LT6_UZzs5TepXGgIGIyYE
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 11 May 2014 19:48:17 -0000

> On 8 May 2014, at 12:30, "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp=
> wrote:
>=20
> Greetings, all,
>=20
> This is the Working Group Last Call for
> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference Format.=

>=20
> The last call starts now, and ends Monday 26 May 2014.
>=20
> Please read the latest revision of the draft,
> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, and
> send your comments to the mailing list; we'd also appreciate a comment if
> you're fine with the draft as is.

Hi,
Below is my review of the draft:

General comment: Is this intended as Proposed Standard? The draft header doe=
sn't say the document type.

The document seems to update ReferenceName syntax to allow for nested XML el=
ements. However the document doesn't say that.
In relationship to this: would this document cause any interoperability issu=
es with programs that can only parse the old schema?


4  IANA Considerations

      Note that certain name requests should not be permitted as either
      Full Name or Abbreviation entries for the requested IANA table.

Do you mean restrictions imposed by the syntax described below or something e=
lse? If you intended to exclude some specific keywords, where is the list of=
 them defined? Either way, I think you need to clarify. If you just meant th=
e ABNF restrictions, I suggest adding something like "The restrictions are s=
pecified in the ABNF below".

      Allocation Policy: Expert Review [RFC5226] and Specification
      Required [RFC5226]

Nit: I think it would be better to say "Specification Required (which implie=
s Expert Review)".


From nobody Sun May 11 15:46:25 2014
Return-Path: <david.black@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5751A0377 for <mile@ietfa.amsl.com>; Sun, 11 May 2014 15:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 nyvJemvyqm1t for <mile@ietfa.amsl.com>; Sun, 11 May 2014 15:46:21 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id B05731A0375 for <mile@ietf.org>; Sun, 11 May 2014 15:46:21 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s4BMkDvh003631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 May 2014 18:46:14 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s4BMkDvh003631
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1399848374; bh=YMU/msT7hMgHl03IW97jwY7FQKs=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=fXyDKKrkgqEsOwYRL+v5mmNoRQv33Bd3XeF6yzRsaQj5sOhAjbb8S+bszgYm5EExd ofJHCNK3uGl+qEu1NCWW6Rvl4jfOZUEnJquyizkgnNLK2cuD1hLfa33j64/pNRxEc5 FYCHeDIOtzM6EBju82hr5YaxeyltPi32XOoHLixM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s4BMkDvh003631
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd05.lss.emc.com (RSA Interceptor); Sun, 11 May 2014 18:46:03 -0400
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s4BMk2t3017599 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 11 May 2014 18:46:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Sun, 11 May 2014 18:46:02 -0400
From: "Black, David" <david.black@emc.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, "<mile@ietf.org>" <mile@ietf.org>
Date: Sun, 11 May 2014 18:45:59 -0400
Thread-Topic: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
Thread-Index: Ac9tUfwW4MTMJLV3RMSUlzEEp/PDoQAGC6vQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C55B1BF@MX15A.corp.emc.com>
References: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com>
In-Reply-To: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.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-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/LEN_VFMbK7ImwgYWyJElafESHLc
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 11 May 2014 22:46:24 -0000

Alexey,

Thanks for the review - I'll take the IANA topics ...

> 4  IANA Considerations
>=20
>       Note that certain name requests should not be permitted as either
>       Full Name or Abbreviation entries for the requested IANA table.
>=20
> Do you mean restrictions imposed by the syntax described below or somethi=
ng
> else? If you intended to exclude some specific keywords, where is the lis=
t of
> them defined? Either way, I think you need to clarify. If you just meant =
the
> ABNF restrictions, I suggest adding something like "The restrictions are
> specified in the ABNF below".

Hmm ... my recollection is that this text was intended to encourage the
Designated Expert for the registry to use his/her best judgment to exclude
"unprintable" acronyms and the like.  I think we can assume that any such
expert reviewer will do that anyway and simply delete this sentence.

>       Allocation Policy: Expert Review [RFC5226] and Specification
>       Required [RFC5226]
>=20
> Nit: I think it would be better to say "Specification Required (which imp=
lies
> Expert Review)".

Sure, that makes sense to me.

Thanks,
--David

> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Alexey Melnikov
> Sent: Sunday, May 11, 2014 3:55 PM
> To: <mile@ietf.org>
> Cc: mile-chairs@tools.ietf.org
> Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-
> reference-format
>=20
>=20
> > On 8 May 2014, at 12:30, "Takeshi Takahashi" <takeshi_takahashi@nict.go=
.jp>
> wrote:
> >
> > Greetings, all,
> >
> > This is the Working Group Last Call for
> > draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference Form=
at.
> >
> > The last call starts now, and ends Monday 26 May 2014.
> >
> > Please read the latest revision of the draft,
> > http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, an=
d
> > send your comments to the mailing list; we'd a so appreciate a comment =
if
> > you're fine with the draft as is.
>=20
> Hi,
> Below is my review of the draft:
>=20
> General comment: Is this intended as Proposed Standard? The draft header
> doesn't say the document type.
>=20
> The document seems to update ReferenceName syntax to allow for nested XML
> elements. However the document doesn't say that.
> In relationship to this: would this document cause any interoperability i=
ssues
> with programs that can only parse the old schema?
>=20
>=20
> 4  IANA Considerations
>=20
>       Note that certain name requests should not be permitted as either
>       Full Name or Abbreviation entries for the requested IANA table.
>=20
> Do you mean restrictions imposed by the syntax described below or somethi=
ng
> else? If you intended to exclude some specific keywords, where is the lis=
t of
> them defined? Either way, I think you need to clarify. If you just meant =
the
> ABNF restrictions, I suggest adding something like "The restrictions are
> specified in the ABNF below".
>=20
>       Allocation Policy: Expert Review [RFC5226] and Specification
>       Required [RFC5226]
>=20
> Nit: I think it would be better to say "Specification Required (which imp=
lies
> Expert Review)".
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Sun May 18 16:57:58 2014
Return-Path: <adam@stoicsecurity.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566D81A021D for <mile@ietfa.amsl.com>; Sun, 18 May 2014 16:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 fiLWMXU572dq for <mile@ietfa.amsl.com>; Sun, 18 May 2014 16:57:55 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CDD91A021F for <mile@ietf.org>; Sun, 18 May 2014 16:57:55 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb1so4912767pad.23 for <mile@ietf.org>; Sun, 18 May 2014 16:57:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=dMU0DY0GJPQ3nL5/bYmtJm6/q5G2KaPWenY7gBwGx5E=; b=OXUOeRrLuhOh6SxNXF5JHPQvQbojmElX4ZC0+4Hvmo47yvLX++ZohimsYUb9TF6m3S Ng4DHTdS45ywdEJFqXofCudIrVyB9V9d15qhaV1ST0n1bfaC63eIXSWMsLF092bvxBqL Uf9/dHXQhj4pn4BltG+R8xpBgxf7AjzFJYuOBfIh7OSkdpe3/RCTzcd83fFElTuQQfI3 DS1f6Q49bQPHe8VPqJ9H2dR+LV3CsPFZcmy9mldqWvAMcCKLe20EVIaGk4Wn0hh+m+hg WIg/nVGTMQhv/B3rVKSo7tYQHPjqIOJBZpiIEiMNmJn4sm3JKuvJYVWtARGrHyMybLsP HOfg==
X-Gm-Message-State: ALoCoQkTBxxXjmATa9uPvDqSTz3ko41b3C05zfyl5BvWU0micu4nP29oz8+xdvVyPzwg4o7PPXsy
X-Received: by 10.67.4.138 with SMTP id ce10mr38228730pad.12.1400457475257; Sun, 18 May 2014 16:57:55 -0700 (PDT)
Received: from [172.20.10.164] ([12.216.224.110]) by mx.google.com with ESMTPSA id yv7sm67368569pac.33.2014.05.18.16.57.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 18 May 2014 16:57:53 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_18ABCC4F-48A3-4330-BF1C-1CDC53E27D5B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Adam Montville <adam@stoicsecurity.com>
In-Reply-To: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com>
Date: Sun, 18 May 2014 18:57:49 -0500
Message-Id: <2684CD65-659D-4F8A-A951-532623C2D86A@stoicsecurity.com>
References: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/BdWt25I5MfgmBqOm7J8Qt5um9B0
Cc: "<mile@ietf.org>" <mile@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 18 May 2014 23:57:58 -0000

--Apple-Mail=_18ABCC4F-48A3-4330-BF1C-1CDC53E27D5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On May 11, 2014, at 2:54 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

>=20
>> On 8 May 2014, at 12:30, "Takeshi Takahashi" =
<takeshi_takahashi@nict.go.jp> wrote:
>>=20
>> Greetings, all,
>>=20
>> This is the Working Group Last Call for
>> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference =
Format.
>>=20
>> The last call starts now, and ends Monday 26 May 2014.
>>=20
>> Please read the latest revision of the draft,
>> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, =
and
>> send your comments to the mailing list; we'd also appreciate a =
comment if
>> you're fine with the draft as is.
>=20
> Hi,
> Below is my review of the draft:
>=20
> General comment: Is this intended as Proposed Standard? The draft =
header doesn't say the document type.

I'll update this, thank you.

>=20
> The document seems to update ReferenceName syntax to allow for nested =
XML elements. However the document doesn't say that.
> In relationship to this: would this document cause any =
interoperability issues with programs that can only parse the old =
schema?

I am unsure about interoperability issues, but they should be minimal =
and are likely implementation specific. =20

I tried an experiment where I generated some code (JAXB) for IODEF 1.0 =
and then fed it a modified recon example (Section 7.2 from RFC 5070).  =
The <ReferenceName> element contained an <EnumRef> element as opposed to =
the string "nmap".  Unmarshalling seemed to work without issue, but when =
examining the ReferenceName element , the only thing present was a =
newline character.    In an example that doesn't use generated code but =
instead uses a SAX or DOM parser, we can grab the inner XML.  Using a =
validating DOM/SAX/other parser will, of course, break if the =
enumeration reference XML is embedded, so parsers will need to be =
updated.

I'm not a professional implementor, so it would be good to hear =
considerations from others.  Then, should these considerations be placed =
in the document (I assume that was the good point of raising the issue)?

With respect to your first sentence above, I assert that the document =
does not "seem" to update ReferenceName, but actually does. :-)  Is it =
necessary to explicitly state the obvious in this case?  I'm happy to =
update the document, but I'm not sure I believe such a statement is =
necessary.  If it is necessary, then a single sentence can be added to =
the abstract making the statement.  Thoughts here?


>=20
>=20
> 4  IANA Considerations
>=20
>      Note that certain name requests should not be permitted as either
>      Full Name or Abbreviation entries for the requested IANA table.
>=20
> Do you mean restrictions imposed by the syntax described below or =
something else? If you intended to exclude some specific keywords, where =
is the list of them defined? Either way, I think you need to clarify. If =
you just meant the ABNF restrictions, I suggest adding something like =
"The restrictions are specified in the ABNF below".
>=20
>      Allocation Policy: Expert Review [RFC5226] and Specification
>      Required [RFC5226]
>=20
> Nit: I think it would be better to say "Specification Required (which =
implies Expert Review)".
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


--Apple-Mail=_18ABCC4F-48A3-4330-BF1C-1CDC53E27D5B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTeUj9AAoJELhc5c4zaVWHdk4H/j3ivi0eG7MGePTPa9e0fKuO
5MK1JuYoQ+FVy9R0MxUzBfr73LEow1pW+GEKHuAln891fKviNlTHdy8aZkSOnZgY
r5YEKoBoMXVvMcpD4dIOpEiRhghEQTMsKgSX7kpMajlyKnDCpJLGbJEy35nPKyG5
eBuWpjlT6PHFI1Vnq2EXHSd/jsin0x4KoYzty97LqsOdlhSF2f/xPkEQF06GNssl
Na9bs2IIvjUej/EsXwhLBPKwCfajrVvkbyT6TQ7x3LqyeKw18IFQoeudJrQmDWvO
hcrbSk4mSKJP5bdHZU/qitdb0VAupotFzjI8ECHQPN3aALFCd0NLsjLDpPGkGAE=
=VwRl
-----END PGP SIGNATURE-----

--Apple-Mail=_18ABCC4F-48A3-4330-BF1C-1CDC53E27D5B--


From nobody Sun May 18 19:39:39 2014
Return-Path: <david.black@emc.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75EF1A0248 for <mile@ietfa.amsl.com>; Sun, 18 May 2014 19:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 VcaQ9Cd5LEjH for <mile@ietfa.amsl.com>; Sun, 18 May 2014 19:39:36 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D19B91A024D for <mile@ietf.org>; Sun, 18 May 2014 19:39:35 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s4J2dXlv002901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 May 2014 22:39:34 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s4J2dXlv002901
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1400467174; bh=UEu+z+ZYTzhZVTS77Up4YgPfhwk=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=UG1cfYqehLceqAKDQi5CHTP/C+k5gBBRx45yLDgXeaTn/STxqUPLe0VgLcNndD0nW RzeKedvIUYqhYlnhmoCKuHgjbS7M6kETl1cZ4HGLf9CFLxz3EfgOZjuGtWrtSFC2FI GO26Lu6cgcMXf6xjyYQzgWEgb0qdU+qDIO0AYTtc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s4J2dXlv002901
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd03.lss.emc.com (RSA Interceptor); Sun, 18 May 2014 22:39:18 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s4J2dHKm020864 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 18 May 2014 22:39:18 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Sun, 18 May 2014 22:39:17 -0400
From: "Black, David" <david.black@emc.com>
To: Adam Montville <adam@stoicsecurity.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Date: Sun, 18 May 2014 22:39:15 -0400
Thread-Topic: Reference and related nits in draft-ietf-mile-enum-reference-format
Thread-Index: Ac9zC4UqZqjgbzJ/SOiFZexw0N3q2w==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@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-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/LQ8xbOJmThFHTK7nwOn-Ka3tHp4
Cc: "<mile@ietf.org>" <mile@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 19 May 2014 02:39:38 -0000

Hi Adam,

> With respect to your first sentence above, I assert that the document doe=
s not
> "seem" to update ReferenceName, but actually does. :-)  Is it necessary t=
o
> explicitly state the obvious in this case?  I'm happy to update the docum=
ent,
> but I'm not sure I believe such a statement is necessary.  If it is neces=
sary,
> then a single sentence can be added to the abstract making the statement.
> Thoughts here?

In this case, it is necessary to state the obvious for the sake of clarity =
-
I've been there and had to do that ;-).  In addition to a sentence in the
abstract, the header on the title page needs an "Updates: 5070 (if approved=
)"
line, and a section should be added entitled "Summary of Changes to RFC 507=
0"
that identifies the changes.

For a somewhat longer recent example, see RFC 7146:
	http://datatracker.ietf.org/doc/rfc7146/

----------------

Here are some additional editorial nits that need attention ...

a) I recently had another draft dinged by the IESG for using a citation as
a word in a sentence e.g., "[IODEF]" in the first sentence in Section 2:

   The need is to place enumeration identifiers and their references in
   [IODEF]'s Reference class.

Believe it or not, the appropriate change is "[IODEF]" -> "IODEF [IODEF]" -
I suggest just doing this and not asking why :-). The whole draft should be
checked for other uses of citations in this fashion.

b) In addition, references should not be cited in the abstract, so I believ=
e
the appropriate changes to the two citations in the abstract are:

   The Incident Object Description Exchange Format [IODEF] provides a

		"[IODEF]" -> "(IODEF)"

   Reference class used to reference external entities (such as
   enumeration identifiers).  However, the method of external entity
   identification has been left unstructured.  This document describes a
   method to provide structure for referencing external entities for the
   [IODEF] Reference class.

		"[IODEF]" -> "IODEF"

Otherwise, the draft still looks good.

Thanks,
--David

> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
> Sent: Sunday, May 18, 2014 7:58 PM
> To: Alexey Melnikov
> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
> Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-
> reference-format
>=20
>=20
> On May 11, 2014, at 2:54 PM, Alexey Melnikov <alexey.melnikov@isode.com>
> wrote:
>=20
> >
> >> On 8 May 2014, at 12:30, "Takeshi Takahashi" <takeshi_takahashi@nict.g=
o.jp>
> wrote:
> >>
> >> Greetings, all,
> >>
> >> This is the Working Group Last Call for
> >> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference For=
mat.
> >>
> >> The last call starts now, and ends Monday 26 May 2014.
> >>
> >> Please read the latest revision of the draft,
> >> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, a=
nd
> >> send your comments to the mailing list; we'd also appreciate a comment=
 if
> >> you're fine with the draft as is.
> >
> > Hi,
> > Below is my review of the draft:
> >
> > General comment: Is this intended as Proposed Standard? The draft heade=
r
> doesn't say the document type.
>=20
> I'll update this, thank you.
>=20
> >
> > The document seems to update ReferenceName syntax to allow for nested X=
ML
> elements. However the document doesn't say that.
> > In relationship to this: would this document cause any interoperability
> issues with programs that can only parse the old schema?
>=20
> I am unsure about interoperability issues, but they should be minimal and=
 are
> likely implementation specific.
>=20
> I tried an experiment where I generated some code (JAXB) for IODEF 1.0 an=
d
> then fed it a modified recon example (Section 7.2 from RFC 5070).  The
> <ReferenceName> element contained an <EnumRef> element as opposed to the
> string "nmap".  Unmarshalling seemed to work without issue, but when exam=
ining
> the ReferenceName element , the only thing present was a newline characte=
r.
> In an example that doesn't use generated code but instead uses a SAX or D=
OM
> parser, we can grab the inner XML.  Using a validating DOM/SAX/other pars=
er
> will, of course, break if the enumeration reference XML is embedded, so
> parsers will need to be updated.
>=20
> I'm not a professional implementor, so it would be good to hear considera=
tions
> from others.  Then, should these considerations be placed in the document=
 (I
> assume that was the good point of raising the issue)?
>=20
> With respect to your first sentence above, I assert that the document doe=
s not
> "seem" to update ReferenceName, but actually does. :-)  Is it necessary t=
o
> explicitly state the obvious in this case?  I'm happy to update the docum=
ent,
> but I'm not sure I believe such a statement is necessary.  If it is neces=
sary,
> then a single sentence can be added to the abstract making the statement.
> Thoughts here?
>=20
>=20
> >
> >
> > 4  IANA Considerations
> >
> >      Note that certain name requests should not be permitted as either
> >      Full Name or Abbreviation entries for the requested IANA table.
> >
> > Do you mean restrictions imposed by the syntax described below or somet=
hing
> else? If you intended to exclude some specific keywords, where is the lis=
t of
> them defined? Either way, I think you need to clarify. If you just meant =
the
> ABNF restrictions, I suggest adding something like "The restrictions are
> specified in the ABNF below".
> >
> >      Allocation Policy: Expert Review [RFC5226] and Specification
> >      Required [RFC5226]
> >
> > Nit: I think it would be better to say "Specification Required (which
> implies Expert Review)".
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile


From nobody Mon May 19 05:29:27 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 837281A0249 for <mile@ietfa.amsl.com>; Mon, 19 May 2014 05:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 lr_V9eR_hZHa for <mile@ietfa.amsl.com>; Mon, 19 May 2014 05:29:20 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id F2DF41A004C for <mile@ietf.org>; Mon, 19 May 2014 05:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1400502559; d=isode.com; s=selector; i=@isode.com; bh=6tUkGwWjeBjKrQd+d8KVXBodFbSI0CGBE7IcDxxEVFA=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=vq54reLr3+stDWo6KAcNxIo9bKHVIkxvByWUkj6C54O7Jxmi3mkLxZeMR5H7HBngCtQ+XU sur6ICESl+u+/CEupjPFqEvuMy7T3b08itaSVQVhcvuGLemtifFU0L/Uu5+igx0cyhVKsV 0weE7Ejv1PVesEg+wgj2k3sO9waT+64=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <U3n5HgAiszeu@statler.isode.com>; Mon, 19 May 2014 13:29:18 +0100
Message-ID: <5379F90D.4040901@isode.com>
Date: Mon, 19 May 2014 13:29:01 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
To: Adam Montville <adam@stoicsecurity.com>
References: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com> <2684CD65-659D-4F8A-A951-532623C2D86A@stoicsecurity.com>
In-Reply-To: <2684CD65-659D-4F8A-A951-532623C2D86A@stoicsecurity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/EqU6Gy8ZSpvLamu8SwiS9tM_O1E
Cc: "<mile@ietf.org>" <mile@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 19 May 2014 12:29:24 -0000

Hi Adam,

On 19/05/2014 00:57, Adam Montville wrote:
> On May 11, 2014, at 2:54 PM, Alexey Melnikov 
> <alexey.melnikov@isode.com> wrote: 
  [...]
>> The document seems to update ReferenceName syntax to allow for nested 
>> XML elements. However the document doesn't say that. In relationship 
>> to this: would this document cause any interoperability issues with 
>> programs that can only parse the old schema? 
> I am unsure about interoperability issues, but they should be minimal 
> and are likely implementation specific. I tried an experiment where I 
> generated some code (JAXB) for IODEF 1.0 and then fed it a modified 
> recon example (Section 7.2 from RFC 5070). The <ReferenceName> element 
> contained an <EnumRef> element as opposed to the string "nmap". 
> Unmarshalling seemed to work without issue, but when examining the 
> ReferenceName element , the only thing present was a newline 
> character. In an example that doesn't use generated code but instead 
> uses a SAX or DOM parser, we can grab the inner XML. Using a 
> validating DOM/SAX/other parser will, of course, break if the 
> enumeration reference XML is embedded, so parsers will need to be 
> updated. I'm not a professional implementor, so it would be good to 
> hear considerations from others. Then, should these considerations be 
> placed in the document (I assume that was the good point of raising 
> the issue)?
I think some discussion of this would be helpful. It can be entirely 
informative.
> With respect to your first sentence above, I assert that the document 
> does not "seem" to update ReferenceName, but actually does. :-) Is it 
> necessary to explicitly state the obvious in this case?

I was expecting that the XML Schema in your document would make it 
clear. But instead you introduced a new XML element which doesn't seem 
to be connected to ReferenceName. So either updating the XML Schema or 
saying that explicitly would help.
> I'm happy to update the document, but I'm not sure I believe such a 
> statement is necessary. If it is necessary, then a single sentence can 
> be added to the abstract making the statement. Thoughts here?

Best Regards,
Alexey


From nobody Mon May 19 06:33:45 2014
Return-Path: <adam@stoicsecurity.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860611A0369 for <mile@ietfa.amsl.com>; Mon, 19 May 2014 06:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 JdhTKVCTy2Zy for <mile@ietfa.amsl.com>; Mon, 19 May 2014 06:33:39 -0700 (PDT)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20B781A006E for <mile@ietf.org>; Mon, 19 May 2014 06:33:39 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so5745690pab.24 for <mile@ietf.org>; Mon, 19 May 2014 06:33:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=/jlWqkm3lWkUkm6Z7I4zko8GaLSPhzW4EvENwFelOEw=; b=SrwYk6OeVBnkGQl+jbONlgQWktNVG2GQfEe7S5erWmVS8SSPCSkLyh13IWoLPdv3k0 Of9+3SAMOFgmfZUxUGz+pvsXj0rcvYhF14V31ORpSxI61CuiaqiQbp6ryowONcdrW+Nl b9Ily6Fo0KPz9BwM/iRvtCTSZsuTxgkAMe+4cfxKAMkX7lmqdn8hEQfwzjixlNfOc1OT Fe+V6g40djqbnpkj/JB51H0uujDxlaPLKN3F504esR6YgvrjsMmxulBRc+3yn2FPa7yp aHCJk/l7YJl5nPEJv/T9NqFjpAnCT647lduFpK+O0irf8fYU6Y+jgbpBpbcwz7rG0yXB 5I0w==
X-Gm-Message-State: ALoCoQlDM57IyqjNWeYHUw3he9vqpCmmXp8BSWMYRjpOglR2uo0jBmxuyDESyHx0u6j3I6fYBj1L
X-Received: by 10.68.191.138 with SMTP id gy10mr4613149pbc.169.1400506417986;  Mon, 19 May 2014 06:33:37 -0700 (PDT)
Received: from [172.20.10.164] ([12.216.224.110]) by mx.google.com with ESMTPSA id cj1sm75805444pac.40.2014.05.19.06.33.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 May 2014 06:33:36 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E900C2A4-4D8F-40DA-BB7C-6AFA08012C2D"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Adam Montville <adam@stoicsecurity.com>
In-Reply-To: <5379F90D.4040901@isode.com>
Date: Mon, 19 May 2014 06:33:34 -0700
Message-Id: <9DC5BDDA-ED50-49C1-ADCC-6688A21C7C58@stoicsecurity.com>
References: <8E012330-F557-4EC5-B41F-51BE8051D14F@isode.com> <2684CD65-659D-4F8A-A951-532623C2D86A@stoicsecurity.com> <5379F90D.4040901@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/t4R-wnLfgfVhaV0Y0NqA-pVwzn4
Cc: "<mile@ietf.org>" <mile@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 19 May 2014 13:33:43 -0000

--Apple-Mail=_E900C2A4-4D8F-40DA-BB7C-6AFA08012C2D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On May 19, 2014, at 5:29 AM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:

> Hi Adam,
>=20
> On 19/05/2014 00:57, Adam Montville wrote:
>> On May 11, 2014, at 2:54 PM, Alexey Melnikov =
<alexey.melnikov@isode.com> wrote:=20
> [...]
>>> The document seems to update ReferenceName syntax to allow for =
nested XML elements. However the document doesn't say that. In =
relationship to this: would this document cause any interoperability =
issues with programs that can only parse the old schema?=20
>> I am unsure about interoperability issues, but they should be minimal =
and are likely implementation specific. I tried an experiment where I =
generated some code (JAXB) for IODEF 1.0 and then fed it a modified =
recon example (Section 7.2 from RFC 5070). The <ReferenceName> element =
contained an <EnumRef> element as opposed to the string "nmap". =
Unmarshalling seemed to work without issue, but when examining the =
ReferenceName element , the only thing present was a newline character. =
In an example that doesn't use generated code but instead uses a SAX or =
DOM parser, we can grab the inner XML. Using a validating DOM/SAX/other =
parser will, of course, break if the enumeration reference XML is =
embedded, so parsers will need to be updated. I'm not a professional =
implementor, so it would be good to hear considerations from others. =
Then, should these considerations be placed in the document (I assume =
that was the good point of raising the issue)?
> I think some discussion of this would be helpful. It can be entirely =
informative.

I'll add some discussion about this to the draft, unless you intend for =
further discussion to be held here, on the list, before any updates to =
the draft are made.

>> With respect to your first sentence above, I assert that the document =
does not "seem" to update ReferenceName, but actually does. :-) Is it =
necessary to explicitly state the obvious in this case?
>=20
> I was expecting that the XML Schema in your document would make it =
clear. But instead you introduced a new XML element which doesn't seem =
to be connected to ReferenceName. So either updating the XML Schema or =
saying that explicitly would help.

I can change the schema in the draft.  It's my mistake that the schema =
is new, when it really should amend the schema expressed in 5070. =20

--Apple-Mail=_E900C2A4-4D8F-40DA-BB7C-6AFA08012C2D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTegguAAoJELhc5c4zaVWHrhMH/3DFY2Ia55TtWtEN9r10xsTT
KMVa67U95zpCAQQNkJwE/c8LXvRj1qZZtRmOoqnt9UTRVFCfRHyv16ku1eiTlQqG
00YLzsz1Z/zXuHI7iUGd0vtiGGWc/tKAXK5Zjhj8Hl070rCY73bHInho+ONIiMq/
kXPRbVaTK3hOVREo1jjad8NoKv14vfcff//yTmR6a9P2MoWWYDof1Q6gOOWyqzM/
GsGDkHHjMUFtpsosM9jOKh8plNy+h2qwDpkATG0gWntn1IH8+iu1/o4a8yNNA5BG
GwP1AcwNiMO5N2bwwSIuQIoUZRtTywEdGvqwdZU65MAEgPYso1ebK+ZHC2hvz4M=
=7Yiz
-----END PGP SIGNATURE-----

--Apple-Mail=_E900C2A4-4D8F-40DA-BB7C-6AFA08012C2D--


From nobody Mon May 19 06:59:05 2014
Return-Path: <adam@stoicsecurity.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B501A0386 for <mile@ietfa.amsl.com>; Mon, 19 May 2014 06:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 So61UnJ3ToPi for <mile@ietfa.amsl.com>; Mon, 19 May 2014 06:59:00 -0700 (PDT)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 284711A005C for <mile@ietf.org>; Mon, 19 May 2014 06:59:00 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so5883504pab.10 for <mile@ietf.org>; Mon, 19 May 2014 06:59:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=+00Ys/BiYBVy6CdWHdQDjDenvaTMyu+JLfS969NSfBI=; b=OM4i3ctsoYRcywvq4axg5hBUZZQukgeA9vZ8KKA5blvFMRhja8Ps5nkBRMghb8CpUY GYGdpwyyC6AgtbTXPDfXKUMddCAhb4JgKPvc3hzG2s2A0SHCJ3WszEguygmeElZUnBZF qQ3z1HjaM6g0uio3BSG0xpxEH/mU5c9ZoPuMMtwV1TcrPPJE8qYdGTlgmdeIwfS+vRgl H8sHkOD0MMRJEmhBzgSfyDgvKW4SY5OWiKcnFavJcS7vzBDH7Vf+/gKhn/LyneEkcprZ axjj+YrfqJHpIZBA1cU7lWuojEOPDDKd+NlTN6FOgo05p3XOstbrT6N9xnb5pDCFcwXy QgTg==
X-Gm-Message-State: ALoCoQmb3NlHxsX+ZNBk25ojf1Hw/H19fDYxn1hgR2YYGCSCqO3Ro23fZTsHNHHYYgq2+elkN7oz
X-Received: by 10.68.201.10 with SMTP id jw10mr42910399pbc.25.1400507940077; Mon, 19 May 2014 06:59:00 -0700 (PDT)
Received: from [172.20.10.164] ([12.216.224.110]) by mx.google.com with ESMTPSA id vm3sm30290602pbc.45.2014.05.19.06.58.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 May 2014 06:58:58 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E9F1C673-48EB-4992-87DD-D474D7E27366"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Adam Montville <adam@stoicsecurity.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com>
Date: Mon, 19 May 2014 06:58:55 -0700
Message-Id: <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/BiaXHfgP5EdOCQx37PjNG8hEn4I
Cc: "<mile@ietf.org>" <mile@ietf.org>, "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 19 May 2014 13:59:02 -0000

--Apple-Mail=_E9F1C673-48EB-4992-87DD-D474D7E27366
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

David, thank you.  I've noted all of these and will make appropriate =
updates.

Are there other comments other than those posed by Alexey and David?

On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> wrote:

> Hi Adam,
>=20
>> With respect to your first sentence above, I assert that the document =
does not
>> "seem" to update ReferenceName, but actually does. :-)  Is it =
necessary to
>> explicitly state the obvious in this case?  I'm happy to update the =
document,
>> but I'm not sure I believe such a statement is necessary.  If it is =
necessary,
>> then a single sentence can be added to the abstract making the =
statement.
>> Thoughts here?
>=20
> In this case, it is necessary to state the obvious for the sake of =
clarity -
> I've been there and had to do that ;-).  In addition to a sentence in =
the
> abstract, the header on the title page needs an "Updates: 5070 (if =
approved)"
> line, and a section should be added entitled "Summary of Changes to =
RFC 5070"
> that identifies the changes.
>=20
> For a somewhat longer recent example, see RFC 7146:
> 	http://datatracker.ietf.org/doc/rfc7146/
>=20
> ----------------
>=20
> Here are some additional editorial nits that need attention ...
>=20
> a) I recently had another draft dinged by the IESG for using a =
citation as
> a word in a sentence e.g., "[IODEF]" in the first sentence in Section =
2:
>=20
>   The need is to place enumeration identifiers and their references in
>   [IODEF]'s Reference class.
>=20
> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF =
[IODEF]" -
> I suggest just doing this and not asking why :-). The whole draft =
should be
> checked for other uses of citations in this fashion.
>=20
> b) In addition, references should not be cited in the abstract, so I =
believe
> the appropriate changes to the two citations in the abstract are:
>=20
>   The Incident Object Description Exchange Format [IODEF] provides a
>=20
> 		"[IODEF]" -> "(IODEF)"
>=20
>   Reference class used to reference external entities (such as
>   enumeration identifiers).  However, the method of external entity
>   identification has been left unstructured.  This document describes =
a
>   method to provide structure for referencing external entities for =
the
>   [IODEF] Reference class.
>=20
> 		"[IODEF]" -> "IODEF"
>=20
> Otherwise, the draft still looks good.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
>> Sent: Sunday, May 18, 2014 7:58 PM
>> To: Alexey Melnikov
>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
>> Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-
>> reference-format
>>=20
>>=20
>> On May 11, 2014, at 2:54 PM, Alexey Melnikov =
<alexey.melnikov@isode.com>
>> wrote:
>>=20
>>>=20
>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi" =
<takeshi_takahashi@nict.go.jp>
>> wrote:
>>>>=20
>>>> Greetings, all,
>>>>=20
>>>> This is the Working Group Last Call for
>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference =
Format.
>>>>=20
>>>> The last call starts now, and ends Monday 26 May 2014.
>>>>=20
>>>> Please read the latest revision of the draft,
>>>> =
http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04, and
>>>> send your comments to the mailing list; we'd also appreciate a =
comment if
>>>> you're fine with the draft as is.
>>>=20
>>> Hi,
>>> Below is my review of the draft:
>>>=20
>>> General comment: Is this intended as Proposed Standard? The draft =
header
>> doesn't say the document type.
>>=20
>> I'll update this, thank you.
>>=20
>>>=20
>>> The document seems to update ReferenceName syntax to allow for =
nested XML
>> elements. However the document doesn't say that.
>>> In relationship to this: would this document cause any =
interoperability
>> issues with programs that can only parse the old schema?
>>=20
>> I am unsure about interoperability issues, but they should be minimal =
and are
>> likely implementation specific.
>>=20
>> I tried an experiment where I generated some code (JAXB) for IODEF =
1.0 and
>> then fed it a modified recon example (Section 7.2 from RFC 5070).  =
The
>> <ReferenceName> element contained an <EnumRef> element as opposed to =
the
>> string "nmap".  Unmarshalling seemed to work without issue, but when =
examining
>> the ReferenceName element , the only thing present was a newline =
character.
>> In an example that doesn't use generated code but instead uses a SAX =
or DOM
>> parser, we can grab the inner XML.  Using a validating DOM/SAX/other =
parser
>> will, of course, break if the enumeration reference XML is embedded, =
so
>> parsers will need to be updated.
>>=20
>> I'm not a professional implementor, so it would be good to hear =
considerations
>> from others.  Then, should these considerations be placed in the =
document (I
>> assume that was the good point of raising the issue)?
>>=20
>> With respect to your first sentence above, I assert that the document =
does not
>> "seem" to update ReferenceName, but actually does. :-)  Is it =
necessary to
>> explicitly state the obvious in this case?  I'm happy to update the =
document,
>> but I'm not sure I believe such a statement is necessary.  If it is =
necessary,
>> then a single sentence can be added to the abstract making the =
statement.
>> Thoughts here?
>>=20
>>=20
>>>=20
>>>=20
>>> 4  IANA Considerations
>>>=20
>>>     Note that certain name requests should not be permitted as =
either
>>>     Full Name or Abbreviation entries for the requested IANA table.
>>>=20
>>> Do you mean restrictions imposed by the syntax described below or =
something
>> else? If you intended to exclude some specific keywords, where is the =
list of
>> them defined? Either way, I think you need to clarify. If you just =
meant the
>> ABNF restrictions, I suggest adding something like "The restrictions =
are
>> specified in the ABNF below".
>>>=20
>>>     Allocation Policy: Expert Review [RFC5226] and Specification
>>>     Required [RFC5226]
>>>=20
>>> Nit: I think it would be better to say "Specification Required =
(which
>> implies Expert Review)".
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>=20


--Apple-Mail=_E9F1C673-48EB-4992-87DD-D474D7E27366
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTeg4fAAoJELhc5c4zaVWH3SQH/0TcqvFhNbHl/6cZv1UvXW3C
q4LcvHnUn5uPi770nXDM5h3nUc2MwUiIsgp4q3h0FYj++igVp7JNfjjh1ZSeV+2I
P8s8aJO524C3taZ4I5SAxnbnVEOP7oP4twEkr8g3fB6RuthjAwAhqG+LPXZVi4R/
B0uHwMSid0ADK+1SYGOjn3oleXwBFBcTmSyGB26JC0gDRzsUTVNsPKhnslh4tJGi
Cqxd7ynYM3uBxK+GY8K/0wKSKbNAanY5asAKoeoexGTVzKAo9TGx3m2z+3iTE+Z8
uhQ0CXsOri7Btrn0gEtpb9EfGfE//tvAlLeWoV59akRstkQFhrVxbl/vKjSer4E=
=+s8q
-----END PGP SIGNATURE-----

--Apple-Mail=_E9F1C673-48EB-4992-87DD-D474D7E27366--


From nobody Wed May 21 12:56:05 2014
Return-Path: <eburger@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68ACD1A082A for <mile@ietfa.amsl.com>; Wed, 21 May 2014 12:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.977
X-Spam-Level: *
X-Spam-Status: No, score=1.977 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779] autolearn=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 wVpFPB35igC1 for <mile@ietfa.amsl.com>; Wed, 21 May 2014 12:56:00 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFD9F1A0707 for <mile@ietf.org>; Wed, 21 May 2014 12:56:00 -0700 (PDT)
Received: from [141.161.133.8] (port=49832 helo=[10.129.225.120]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <eburger@standardstrack.com>) id 1WnCcA-0005G7-Q5 for mile@ietf.org; Wed, 21 May 2014 12:55:58 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_69684136-5D36-4A23-BBFF-2D9789CFADB4"; protocol="application/pgp-signature"; micalg=pgp-sha1
Message-Id: <63DF8BAD-3A7B-4454-8B40-AE8A9D1E1333@standardstrack.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Date: Wed, 21 May 2014 15:55:49 -0400
References: <000001cf6b78$42243370$c66c9a50$@nict.go.jp>
To: mile@ietf.org
In-Reply-To: <000001cf6b78$42243370$c66c9a50$@nict.go.jp>
X-Mailer: Apple Mail (2.1878.2)
X-OutGoing-Spam-Status: No, score=-2.9
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-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/_jhSf5TgbdSeKaRnyov_udS6uFU
Subject: Re: [mile] New Version Notification for draft-murillo-mile-cps-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 21 May 2014 19:56:03 -0000

--Apple-Mail=_69684136-5D36-4A23-BBFF-2D9789CFADB4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

And I do not think the world is eager to have two things that do the =
same thing. We already have that problem in this space. I would suggest =
adopting one and only one way of doing this. I have no opinion as to =
whether it should be CPS or SCI.

On May 9, 2014, at 7:17 AM, Takeshi Takahashi =
<takeshi_takahashi@nict.go.jp> wrote:

> Hi Martin,
>=20
> Thank you for your kind comments.
>=20
>> There's one question that still lingers: whether we should not=20
>> re-utilize other extensions or use the IODEF-extension for structured=20=

>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the=20
>> points above would be applicable to both scenarios.
>=20
> I like this CPS draft, but I also like IODEF-SCI's framework (well, I =
am one
> of the authors).
> I do not want to be the obstacle of developing this interesting work, =
so I
> do not have any intention to stick to IODEF-SCI at all.
> But I would like to understand the pros and cons of not using SCI =
framework
> for the CPS extension more vividly.
>=20
> Section 1.7 of the CPS draft explains the reason for not using the
> IODEF-SCI's framework, but it was not so clear to me..
> Can we discuss this issue when we have got example XML documents of =
the CPS
> extension? (I guess later version of the CPS draft will have the =
example XML
> documents?) Then we can compare how the XML documents will look like =
for
> each case of using and not using IODEF-SCI framework on the CPS =
extension.
>=20
> Kind regards,
> Take
>=20
>=20
>> -----Original Message-----
>> From: Martin Murillo [mailto:murillo@ieee.org]
>> Sent: Wednesday, April 30, 2014 12:30 PM
>> To: Takeshi Takahashi; mile@ietf.org
>> Subject: Re: [mile] Fwd: New Version Notification for=20
>> draft-murillo-mile-cps-00.txt
>>=20
>> Dear Takeshi,
>>=20
>> Thanks for the feedback and highlighting various extraneous elements=20=

>> which have rich IODEF equivalents. This makes the reporting lighter=20=

>> and decreases implementation overhead. I have answered to each item =
below.
>>=20
>> 1. The IncidentType element specifies whether the incident is=20
>> accidental, on purpose, or theresult of other actions. The IncdntType=20=

>> attribute is missplaced. Thanks for taking notice of that. However I=20=

>> wonder whether the IncidentType element should be renamed. I think we=20=

>> agree that we need a field where whether the incident is accidental,=20=

>> on purpose, or undetermined can be placed. While the nature of the=20
>> incident is rarely known immediately, there are instances in which =
the=20
>> operator or other local party causes accidental instances; these=20
>> instances might cause repercussions in other locations (i.e. =
balancing in
> an electric grid).
>>=20
>> 2. I agree with you, the IncidentTilte element is a perfect candidate=20=

>> to go to a shallower level, especially when it will be the first=20
>> variable that an operator or appropriate party reads.
>>=20
>> 3. Given that the IODEF:Contact class is rich enough to differentiate=20=

>> between a reporting party and an additional contact=20
>> person/institution, I believe that we should use such class. Because=20=

>> the different stakeholders responsible for the Corporate Network,=20
>> Control Servers, and Field Devices, this class might need to be=20
>> extended. This is also relevant when the attack has taken place at =
any=20
>> of those levels: For instance, the Corporate Network (or a false=20
>> impersonator) might instruct the control room (Control servers) wrong=20=

>> setpoint configurations. Or the Control Network might experience a=20
>> breach and setpoints altered in such servers. In extreme situations, =
the
> attacks might be directly to the field devices. In each of those =
cases.
>> In each of those cases the contact person might be one or more.
>>=20
>> 4, 5, 6. I think the IODEF classes can be indeed used. Thank you. The=20=

>> extension capabilities fo the System Class makes it quite appropriate=20=

>> to offer rich information.
>>=20
>> Regarding your last point, SFK should indeed be used instead of SFC.
>>=20
>> There's one question that still lingers: whether we should not=20
>> re-utilize other extensions or use the IODEF-extension for structured=20=

>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the=20
>> points above would be applicable to both scenarios.
>>=20
>> Martin
>>=20
>> On 4/23/2014 4:42 AM, Takeshi Takahashi wrote:
>>> Hi Martin,
>>>=20
>>> I've read through the drafts. Thank you very much for sharing your=20=

>>> expertise here.
>>> It was a new use case for me, and was really interesting.
>>>=20
>>> I am wondering if we can minimize the number of extension fields by=20=

>>> using the existing IODEF fields.
>>> By minimizing the number of similar fields, I hope we can simplify=20=

>>> the draft and minimize the burden of implementations.
>>>=20
>>>> =46rom this viewpoint, let me ask several checking questions.
>>>=20
>>> 1. IncidentType element and IncdntType Attribute
>>>   What are the difference between them? I think your current draft=20=

>>> has them as place holders. I would like to hear a bit further.
>>>=20
>>> 2. The IncidentTitle element
>>>   Can we use the Description element inside the IODEF:Incident=20
>>> class for this purpose, instead of having new field here?
>>>   It would be useful to have title or such information that can=20
>>> hint the content of the IODEF document, but I feel like that it=20
>>> would be helpful to have this type of information at the shallower=20=

>>> level of IODEF document rather than having it in the deeper level of=20=

>>> IODEF document (inside
>>> additionalData)
>>>=20
>>> 3. The ReportingParty element
>>>   Can we use the IODEF:contact class instead of having new field?=20
>>> We could extend it further if needed.
>>>=20
>>> 4. The ReportReliability element
>>>   Can we use the IODEF:confidence class instead of having new field?
>>> We could extend it further if needed.
>>>=20
>>> 5. The TargetSystems element
>>>   Can we extend the IODEF:system class instead of having new field?
>>> We could extend it further if needed.
>>>=20
>>> 6. type attribute of the IODEF:Impact class
>>>   When we use this extension, what value should be set for the type=20=

>>> attribute of the IODEF:Impact class?
>>>=20
>>> By the way, here are small questions.
>>>=20
>>> 1. should [SFC] be [SFK], since the acronym seems to come from the=20=

>>> initials of the authors of the reference (Stouffer, K., Falco, J.,=20=

>>> and
>> K. Scarfonw) ?
>>>=20
>>> I might have misunderstood your draft, so please correct me if I am
> wrong.
>>>=20
>>> Kind regards,
>>> Take
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Martin=20
>>>> Murillo
>>>> Sent: Wednesday, January 29, 2014 10:11 AM
>>>> To: Johnson, Blake; Jerome Athias
>>>> Cc: mile@ietf.org
>>>> Subject: Re: [mile] Fwd: New Version Notification for=20
>>>> draft-murillo-mile-cps-00.txt
>>>>=20
>>>> Have read the links posted by Jerome and info on the Experience=20
>>>> Sharing Tool (EST). It is my impression that a revision under the=20=

>>>> light of the EST would be very appropriate, and one of the first=20
>>>> uses of the extension, given its report-based nature.  Look forward=20=

>>>> to seeing
>>> the reviews in this light.
>>>> As Jerome mentioned, focusing on referencing already existing=20
>>>> taxonomies (and when necessary reusing them and referencing their=20=

>>>> xml implementations, if publicly available) would be the best=20
>>>> approach; given the early stages in the field, I tend to think that=20=

>>>> atomic data will
>>> need to be used.
>>>> Regarding the term "Asset" vs "System", I believe system provides a=20=

>>>> more general connotation, while asset, seem to focus more on=20
>>>> mainstream infrastructure; because the inclusion of IoT-related=20
>>>> infrastructure (anywhere from centralized home control to=20
>>>> self-driving cars), I wonder whether "Asset" is too an specific =
term.
>>>>=20
>>>> Martin
>>>>=20
>>>> Martin
>>>>=20
>>>> On 1/24/2014 2:09 PM, Johnson, Blake wrote:
>>>>> This is an interesting application of IODEF that I had not =
considered.
>>>> Most industry sharing that takes place in this space, from my=20
>>>> perspective, is in the form of in person and telephone threat=20
>>>> briefings. These are facilitated by the FBI, DHS, and the ISAC's.
>>>>> At least a handful of the ISAC's have started sharing structured=20=

>>>>> threat
>>>> indicator data, and the taxonomy for this extension could cover=20
>>>> what the Electric Sector ISAC currently refers to as 'Experience
> Sharing.'
>>>> I can review this proposal as it relates to information captured by=20=

>>>> the ES-ISAC's Experience Sharing tool, using IEC/ANSI 62443 (ISA99)=20=

>>>> as an informative reference.
>>>>> Blake Johnson
>>>>> Threat Intelligence Analyst
>>>>> Alliant Energy | Infrastructure Secruity
>>>>> Office: 608-458-6320 | Cell: 608-843-2790
>>>>>=20
>>>>>=20
>>>>> -----Original Message-----
>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Jerome=20
>>>>> Athias
>>>>> Sent: Friday, January 24, 2014 3:18 AM
>>>>> To: murillo@ieee.org
>>>>> Cc: mile@ietf.org
>>>>> Subject: Re: [mile] Fwd: New Version Notification for=20
>>>>> draft-murillo-mile-cps-00.txt
>>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> from what I know (which is limited), and as you mention, this ICS=20=

>>>>> area is often also called Critical Infrastructures (CIs), or SCADA
>>>>>=20
>>>>> for a little bit of background, we could explore the Cybersecurity=20=

>>>>> Framework Example references=20
>>>>> http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
>>>>>=20
>>>>=20
>> http://www.ictqatar.qa/en/documents/download/National%20Industrial%20
>>>> C
>>>>> ontrol%20Systems%20Security%20Standard-English.pdf
>>>>> ANSI/ISA-99.02.01-2009
>>>>>=20
>>>>> I don't have enough knowledge about the status and adoption of the=20=

>>>>> different efforts in term of XML representation/format/standards=20=

>>>>> http://xml.coverpages.org/emergencyManagement.html
>>>>> and resilience
>>>>>=20
>>>>> It would maybe be possible to obtain information from there=20
>>>>> http://ics-cert.us-cert.gov http://ics-isac.org/
>>>>>=20
>>>>> My first feedback is that it looks like an interesting extension.
>>>>>=20
>>>>> I would suggest to focus on the reuse of existing Taxonomies, or=20=

>>>>> references to them.
>>>>>=20
>>>>> As such, for [Industry], maybe
>>>>> http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=3D2012
>>>>> ISO 3166 (Country Codes)
>>>>>=20
>>>>>=20
>>>>> [TargetSystems], I (personally) don't like the word "system" and=20=

>>>>> prefer
>>>> "asset"
>>>>> [CompromisedPhysicalInfrastrucute] (with a typo ;p) seems to be a=20=

>>>>> category of "Infrastructure" (or group of assets)
>>>>>=20
>>>>>=20
>>>>> [EntryPoint] could be ok since it could be a little bit different=20=

>>>>> from "endpoint"
>>>>>=20
>>>>> [PerpetratingParty] seems to reference "Threat Actor" or "Threat=20=

>>>>> Agent" or "Attacker"
>>>>>=20
>>>>> [RecurrencePreventionMeasures] is this Security Controls? (and
>>>>> Mitigations/Remediations)
>>>>> Reference:
>>>>>=20
>> https://web.nvd.nist.gov/view/800-53/control?controlName=3DAC-3&type=3D=
1
>>>>>=20
>>>>>=20
>>>>> Describing an [Exploit] is not so easy (depending on the level of=20=

>>>>> details wanted/needed)
>>>>>=20
>>>>> Figure 1 (or "Diagram 1") is interesting, (of course it is=20
>>>>> different from, i.e. CAESARS), it MAYBE could be more layered
>>>>>=20
>>>>=20
>> http://www.isa.org/InTechTemplate.cfm?template=3D/ContentManagement/Con=

>>>> t
>>>>> entDisplay.cfm&ContentID=3D94401
>>>>>=20
>>>>> (To follow: ENISA CDXI)
>>>>>=20
>>>>>=20
>>>>> Some typos
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Next step: more XML focused ;)
>>>>>=20
>>>>>=20
>>>>> My 2 bitcents
>>>>>=20
>>>>> 2014/1/24 Martin Murillo <murillo@ieee.org>:
>>>>>> Dear all,
>>>>>>=20
>>>>>> Please find below a link to a proposed draft for extending IODEF=20=

>>>>>> for the reporting of cyber-physical system incidents. These=20
>>>>>> systems are often referred as  Operational Technology Systems,=20
>>>>>> Industrial Control Systems, Automatic Control  Systems, or simply=20=

>>>>>> Control
>> Systems.
>>>>>>=20
>>>>>> Cyber-Physical systems have been around for decades.  However,=20
>>>>>> they are now at a higher risk to be  the target of attacks by=20
>>>>>> individual highly-skilled attackers, organized groups,=20
>>>>>> nation-states, or simply suffer repercussions of mainstream IT=20
>>>>>> cyber-attacks. While over 90% of critical control system=20
>>>>>> infrastructure is currently owned by private enterprises, these=20=

>>>>>> can have direct repercussions on national security of world=20
>>>>>> nations.  Indeed, various of these systems are key parts of=20
>>>>>> nuclear reactor facilities, transportation systems, electric=20
>>>>>> power distribution, oil and natural gas distribution, health=20
>>>>>> care, water
>>>> and waste-water treatment, dam infrastructure, missile
>>>>>> and defense systems, and others.   The disruption of these =
control
>>>> systems
>>>>>> could have a significant impact on public health, safety, and=20
>>>>>> lead to large economic losses.
>>>>>>=20
>>>>>> Among the issues that catalyze this higher risk are:
>>>>>>=20
>>>>>> i) these systems are gradually becoming more interconnected, ii)=20=

>>>>>> legacy systems do not have proper cybersecurity protection, iii)=20=

>>>>>> the existence of highly-skilled individuals and motivations, iv)=20=

>>>>>> some these systems are generally considered critical, v) these=20
>>>>>> are a natural extension of IT cyber-attacks, vi) the emergence of=20=

>>>>>> the Internet of Things (IOT), and vi) these attacks can be=20
>>>>>> carried out
>>>> remotely and quite inexpensively.
>>>>>> While there might exist national approaches to deal with=20
>>>>>> incidents, there's the need of a global international approach=20
>>>>>> that will engulf governments, private organizations and other
> stakeholders.
>>>>>> IETF, as a leading global Internet standards organization, seeks=20=

>>>>>> to satisfy this need through open standards that seek to=20
>>>>>> encompass issues that are critical for the global community.
>>>>>>=20
>>>>>> Feedback at two levels are welcome:
>>>>>>=20
>>>>>> 1. On the existence and inclusion either by utilizing any already
>>> existing
>>>>>> industry formats (XML-   encoded) and/or by utilizing atomic data
>>>>>> 2. Contributions on making the extension (and background
>>>>>> information) more comprehensive, accurate and principally useful=20=

>>>>>> for the community
>>>>>>=20
>>>>>> Look forward to feedback and other input!
>>>>>>=20
>>>>>> Martin Murillo
>>>>>>=20
>>>>>> A new version of I-D, draft-murillo-mile-cps-00.txt has been=20
>>>>>> successfully submitted by Martin Murillo and posted to the IETF=20=

>>>>>> repository.
>>>>>>=20
>>>>>> Name:           draft-murillo-mile-cps
>>>>>> Revision:       00
>>>>>> Title:          IODEF extension for Reporting Cyber-Physical =
System
>>>>>> Incidents
>>>>>> Document date:  2014-01-21
>>>>>> Group:          Individual Submission
>>>>>> Pages:          24
>>>>>> URL:
>>>>>> http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt
>>>>>> Status:
>>>> https://datatracker.ietf.org/doc/draft-murillo-mile-cps/
>>>>>> Htmlized:
>> http://tools.ietf.org/html/draft-murillo-mile-cps-00
>>>>>>=20
>>>>>>=20
>>>>>> Abstract:
>>>>>>    This draft document will extend the Incident Object =
Description
>>>>>>    Exchange Format (IODEF) defined in [RFC5070] to support the
>>>> reporting
>>>>>>    of incidents dealing with attacks to physical infrastructure
>>> through
>>>>>>    the utilization of IT means as a vehicle or as a tool.  These
>>> systems
>>>>>>    might also be referred as Cyber-Physical Systems (CPS),
>> Operational
>>>>>>    Technology Systems, Industrial Control Systems, Automatic
>> Control
>>>>>>    Systems, or simply Control Systems.  These names are used
>>>>>>    interchangeably in this document.  In this context, an=20
>>>>>> incident
>> is
>>>>>>    generally the result of a cybersecurity issue whose main goal=20=

>>>>>> is
>>>> to
>>>>>>    affect the operation of a CPS.  It is considered that any
>>>>>>    unauthorized alteration of the operation is always malign.  =
This
>>>>>>    extension will provide the capability of embedding structured
>>>>>>    information, such as identifier- and XML-based information. =20=

>>>>>> In
>> its
>>>>>>    current state, this document provides important=20
>>>>>> considerations
>> for
>>>>>>    further work in implementing Cyber-Physical System incident
>>>> reports,
>>>>>>    either by utilizing any already existing industry formats =
(XML-
>>>>>>    encoded) and/or by utilizing atomic data.
>>>>>>=20
>>>>>>    In addition, this document should provide appropriate=20
>>>>>> material
>> for
>>>>>>    helping making due considerations in making an appropriate
>> decision
>>>>>>    on how a CPS reporting is done: 1) through a data format=20
>>>>>> extension
>>>> to
>>>>>>    the Incident Object Description Exchange Format [RFC5070], 2)
>>>> forming
>>>>>>    part of an already existing IODEF-extension for structured
>>>>>>    cybersecurity information (currently draft
>>>>>>    draft-ietf-mile-sci-11.txt), or others.  While the format and
>>>>>>    contents of the present document fit more the earlier option,
> these
>>>>>>    can also be incorporated to the later.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Please note that it may take a couple of minutes from the time of=20=

>>>>>> submission until the htmlized version and diff are available at
>>>> tools.ietf.org.
>>>>>> The IETF Secretariat
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=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
>>>>>=20
>>>>>=20
>>>> _______________________________________________
>>>> mile mailing list
>>>> mile@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


--Apple-Mail=_69684136-5D36-4A23-BBFF-2D9789CFADB4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJTfQTGAAoJEDY/T2tCIPW3VPAP/28+q8ZoUPPwH1+1Oo/M3A2w
b9LR7eCAAkvoGc0qGGd1ATdEFeiZbub09gEHfkvoZsqytVHrAaKkgmZcL55bCidr
I/msQIknglZsAjY83iKPs/xLLFV4Gs+Hm2bgSjwUb65erOefAL42TwgNOhWKeUHS
As6Zl+GrZRm5/WymDTPApnmcBFOzVInGFepZ27pHcJQ74150JibPgRFoFpbdr2Ql
qsSeL7HMiEXtyP6eg5bVi5qqt24RMeOjDOurwABAIayHlmc4RkResqeTjs1k1z+T
W8ueCs06qdXr2f5pVsVh+PeDjuVC6AfJAcVM4uUQN3yB/01P3tmIDi77G0dUNqvL
zD6hJW7SZzsDtzRgRMK2nhiJaPx/SNKFiqg44z1P9UrTU0pH5J+vhnZYoy+jKwNn
N+ZQbGtB5cCCpmFGyu3CCV0ZYxjnZwUxkaLSABMpc2WrqrLay7hzFNdn/inaGifq
NZFVTi4BdrN9m3MJ05oWQjzXWq/mZVrfuQjaDiL9PqpvAP0NBqn0u9mvZRwMjxFJ
Er8vBBYtN+22+bLNtfRYQ63mtnoLxsBUgjVdgJPg0XkAQOYgTRZht0ouirNFsspk
iD1u+hqe7KEI7ccEV875EmeuJXd5NtSwYC2U2SpUMXrzSmPLTAuCeim+bGJk+Xbm
HsX6UCC90QBdYLx0vSh8
=aJu1
-----END PGP SIGNATURE-----

--Apple-Mail=_69684136-5D36-4A23-BBFF-2D9789CFADB4--


From nobody Thu May 22 04:45:00 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32F21A0195 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 04:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.043
X-Spam-Level: 
X-Spam-Status: No, score=-0.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 9Vo7gZyxIn3R for <mile@ietfa.amsl.com>; Thu, 22 May 2014 04:44:57 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBCA91A018A for <mile@ietf.org>; Thu, 22 May 2014 04:44:56 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id s4MBilAn005880; Thu, 22 May 2014 20:44:47 +0900 (JST)
Received: from VAIO (ssh.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp  with ESMTP id s4MBik03021179; Thu, 22 May 2014 20:44:46 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Adam Montville'" <adam@stoicsecurity.com>, "'Black, David'" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com>
In-Reply-To: <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com>
Date: Thu, 22 May 2014 20:44:45 +0900
Message-ID: <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKc7BPik8IqmT4Sp0oJUR3hLlrCgAFkNJ1kmaZm/0A=
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith2
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/ATVM8dywFZIjamhxFFev9cQv6Bo
Cc: mile@ietf.org, mile-chairs@tools.ietf.org
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 11:44:59 -0000

Hi Adam,

I remember that we had discussion on the Index field last year.
We have a field for the Index and not for version number.
That is because "the Index field in the XML unambiguously indicates which
IANA registry entry is to be used to correctly reference the enumeration
specification, which avoids interpretation of version strings that may have
specification-specific formats" (copied from the draft).
Yes, this was what I understood in the discussion last year.

Now I am reading the document again, and have stuck on one question.
Maybe I have some misunderstanding or have forgotten some discussion, but I
would appreciate if you could clarify the issue below.

If we have Index field, do we need the Abbreviation field?

Below is the example described in the draft.
<EnumRef>
  <Abbreviation>CXI</Abbreviation>
  <Index>1</Index>
  <ID>CXI-1234-XYZ</ID>
</EnumRef>

But can we simply write like this?
<EnumRef>
  <Index>1</Index>
  <ID>CXI-1234-XYZ</ID>
</EnumRef>

If we have the Index value, we can uniquely identify the specification and
version, correct?

Take


> -----Original Message-----
> From: Adam Montville [mailto:adam@stoicsecurity.com]
> Sent: Monday, May 19, 2014 10:59 PM
> To: Black, David
> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
> Subject: Re: Reference and related nits in
> draft-ietf-mile-enum-reference-format
> 
> David, thank you.  I've noted all of these and will make appropriate
> updates.
> 
> Are there other comments other than those posed by Alexey and David?
> 
> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> wrote:
> 
> > Hi Adam,
> >
> >> With respect to your first sentence above, I assert that the document
> >> does not "seem" to update ReferenceName, but actually does. :-)  Is
> >> it necessary to explicitly state the obvious in this case?  I'm happy
> >> to update the document, but I'm not sure I believe such a statement
> >> is necessary.  If it is necessary, then a single sentence can be added
> to the abstract making the statement.
> >> Thoughts here?
> >
> > In this case, it is necessary to state the obvious for the sake of
> > clarity - I've been there and had to do that ;-).  In addition to a
> > sentence in the abstract, the header on the title page needs an
"Updates:
> 5070 (if approved)"
> > line, and a section should be added entitled "Summary of Changes to RFC
> 5070"
> > that identifies the changes.
> >
> > For a somewhat longer recent example, see RFC 7146:
> > 	http://datatracker.ietf.org/doc/rfc7146/
> >
> > ----------------
> >
> > Here are some additional editorial nits that need attention ...
> >
> > a) I recently had another draft dinged by the IESG for using a
> > citation as a word in a sentence e.g., "[IODEF]" in the first sentence
> in Section 2:
> >
> >   The need is to place enumeration identifiers and their references in
> >   [IODEF]'s Reference class.
> >
> > Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
> > [IODEF]" - I suggest just doing this and not asking why :-). The whole
> > draft should be checked for other uses of citations in this fashion.
> >
> > b) In addition, references should not be cited in the abstract, so I
> > believe the appropriate changes to the two citations in the abstract
are:
> >
> >   The Incident Object Description Exchange Format [IODEF] provides a
> >
> > 		"[IODEF]" -> "(IODEF)"
> >
> >   Reference class used to reference external entities (such as
> >   enumeration identifiers).  However, the method of external entity
> >   identification has been left unstructured.  This document describes
> a
> >   method to provide structure for referencing external entities for the
> >   [IODEF] Reference class.
> >
> > 		"[IODEF]" -> "IODEF"
> >
> > Otherwise, the draft still looks good.
> >
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
> >> Sent: Sunday, May 18, 2014 7:58 PM
> >> To: Alexey Melnikov
> >> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
> >> Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-
> >> reference-format
> >>
> >>
> >> On May 11, 2014, at 2:54 PM, Alexey Melnikov
> >> <alexey.melnikov@isode.com>
> >> wrote:
> >>
> >>>
> >>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
> >>>> <takeshi_takahashi@nict.go.jp>
> >> wrote:
> >>>>
> >>>> Greetings, all,
> >>>>
> >>>> This is the Working Group Last Call for
> >>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference
> Format.
> >>>>
> >>>> The last call starts now, and ends Monday 26 May 2014.
> >>>>
> >>>> Please read the latest revision of the draft,
> >>>>
> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
> >>>> , and send your comments to the mailing list; we'd also appreciate
> >>>> a comment if you're fine with the draft as is.
> >>>
> >>> Hi,
> >>> Below is my review of the draft:
> >>>
> >>> General comment: Is this intended as Proposed Standard? The draft
> >>> header
> >> doesn't say the document type.
> >>
> >> I'll update this, thank you.
> >>
> >>>
> >>> The document seems to update ReferenceName syntax to allow for
> >>> nested XML
> >> elements. However the document doesn't say that.
> >>> In relationship to this: would this document cause any
> >>> interoperability
> >> issues with programs that can only parse the old schema?
> >>
> >> I am unsure about interoperability issues, but they should be minimal
> >> and are likely implementation specific.
> >>
> >> I tried an experiment where I generated some code (JAXB) for IODEF
> >> 1.0 and then fed it a modified recon example (Section 7.2 from RFC
> >> 5070).  The <ReferenceName> element contained an <EnumRef> element as
> >> opposed to the string "nmap".  Unmarshalling seemed to work without
> >> issue, but when examining the ReferenceName element , the only thing
> present was a newline character.
> >> In an example that doesn't use generated code but instead uses a SAX
> >> or DOM parser, we can grab the inner XML.  Using a validating
> >> DOM/SAX/other parser will, of course, break if the enumeration
> >> reference XML is embedded, so parsers will need to be updated.
> >>
> >> I'm not a professional implementor, so it would be good to hear
> >> considerations from others.  Then, should these considerations be
> >> placed in the document (I assume that was the good point of raising the
> issue)?
> >>
> >> With respect to your first sentence above, I assert that the document
> >> does not "seem" to update ReferenceName, but actually does. :-)  Is
> >> it necessary to explicitly state the obvious in this case?  I'm happy
> >> to update the document, but I'm not sure I believe such a statement
> >> is necessary.  If it is necessary, then a single sentence can be added
> to the abstract making the statement.
> >> Thoughts here?
> >>
> >>
> >>>
> >>>
> >>> 4  IANA Considerations
> >>>
> >>>     Note that certain name requests should not be permitted as either
> >>>     Full Name or Abbreviation entries for the requested IANA table.
> >>>
> >>> Do you mean restrictions imposed by the syntax described below or
> >>> something
> >> else? If you intended to exclude some specific keywords, where is the
> >> list of them defined? Either way, I think you need to clarify. If you
> >> just meant the ABNF restrictions, I suggest adding something like
> >> "The restrictions are specified in the ABNF below".
> >>>
> >>>     Allocation Policy: Expert Review [RFC5226] and Specification
> >>>     Required [RFC5226]
> >>>
> >>> Nit: I think it would be better to say "Specification Required
> >>> (which
> >> implies Expert Review)".
> >>>
> >>> _______________________________________________
> >>> mile mailing list
> >>> mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >



From nobody Thu May 22 05:51:06 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C68841A0020 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 05:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.043
X-Spam-Level: 
X-Spam-Status: No, score=-0.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 S9gdjTLFecS1 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 05:51:03 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B28331A0198 for <mile@ietf.org>; Thu, 22 May 2014 05:51:00 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id s4MCowml017200 for <mile@ietf.org>; Thu, 22 May 2014 21:50:58 +0900 (JST)
Received: from VAIO (ssh.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id s4MCov5l004570 for <mile@ietf.org>; Thu, 22 May 2014 21:50:58 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <20140501201046.797.49114.idtracker@ietfa.amsl.com> <1C9F17D1873AFA47A969C4DD98F98A750FBDABEA@xmb-rcd-x10.cisco.com> 
In-Reply-To: 
Date: Thu, 22 May 2014 21:50:56 +0900
Message-ID: <000901cf75bc$79a6a6e0$6cf3f4a0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKEgaLJpHUnE7Tb4NKZp0r5Qh/vBQHu/wJcmdLxPxCAAAw90A==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith1
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/ggI_3ZGvHA9oO9GR-QpMrbrIbUQ
Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 12:51:04 -0000

Hello Panos,

Thank you for updating the draft.
I am wondering if we could use the following texts as a starting point of
the section 4.3.

---------------------------------------
IODEF data model is designed to be extensible.
We can extend the enumerated values of the attributes by using the "ext-*"
fields, whereas we can extend the classes by using the AdditionalData and
RecordItem classes.
Please see RFC 5070 for details.
Some of these AdditionalData extensions were documented as standard
specifications.
Please see RFC5901 for the phishing extension.

On the other hand, IODEF can borrow existing schemata by using an extension
framework defined in RFC 7203.
The framework enables us to embed xml documents and identifiers whose
schemata or structure are defined by external specifications inside IODEF
document.
In this way, the capability of IODEF data model is extended, but users do
not have to extend IODEF itself. Users simply need to use schemata that were
defined outside IODEF data model.
Please see RFC 7203 for details.
---------------------------------------

This is just a basis for discussion and revision, but I hope the above
understanding is roughly aligned with you.

Take

> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Panos 
> Kampanakis
> (pkampana)
> Sent: Friday, May 2, 2014 5:20 AM
> To: mile@ietf.org
> Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
> 
> Hello,
> 
> This is the -03 version of the IODEF guidance draft incorporating 
> Roman's, Kathleen's, Trevor's and David's comments so far. The updated 
> made from
> -02 version are
>    (1)  Added "Updates" section.
>    (2)  Added details about the flow of information exchanges in "Inter-
>         vendor and Service Provider Exercise" section.  Also updated the
>         usecases with more background information.
>    (3)  Added future use-cases in the "Collective Intelligence
>         Framework" section
>    (4)  Updated Perl and Python references with the actual module names.
>         Added IODEF implementation reference "implementations".
>    (5)  Added Predicate logic section
>    (6)  Updated Logic of watchlist of indicators section to simplify the
>         logic and include examples.
>    (7)  Renamed Externally defined indicators section to Indicator
>         reference and elaborated on the use of indicator-uid and
>         indicator-set-uid attribute use.
> 
> It is still not complete and some sections need to be expanded. I will 
> now work on -04 and hopefully will have a more complete version in a 
> couple of months.
> 
> Feedback and reviews are welcome.
> 
> Regards,
> Panos
> 
> 
> 
> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of 
> internet-drafts@ietf.org
> Sent: Thursday, May 01, 2014 4:11 PM
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>  This draft is a work item of the Managed Incident Lightweight 
> Exchange Working Group of the IETF.
> 
>         Title           : IODEF Usage Guidance
>         Author          : Panos Kampanakis
> 	Filename        : draft-ietf-mile-iodef-guidance-03.txt
> 	Pages           : 26
> 	Date            : 2014-05-01
> 
> Abstract:
>    The Incident Object Description Exchange Format [RFC5070] defines a
>    data representation that provides a framework for sharing information
>    commonly exchanged by Computer Security Incident Response Teams
>    (CSIRTs) about computer security incidents.  Since the IODEF model
>    includes a wealth of available options that can be used to describe a
>    security incident or issue, it can be challenging for implementers to
>    develop tools that can Leverage IODEF for incident sharing.  This
>    document provides guidelines for IODEF implementers.  It will also
>    address how common security indicators can be represented in IODEF
>    and use-cases of how IODEF is being used so far.The goal of this
>    document is to make IODEF's adoption by vendors easier and encourage
>    faster and wider adoption of the model by Computer Security Incident
>    Response Teams (CSIRTs) around the world.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-03
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-mile-iodef-guidance-03
> 
> 
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at
tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> 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 nobody Thu May 22 06:03:58 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 560581A019A for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.857
X-Spam-Level: ***
X-Spam-Status: No, score=3.857 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 bTVCroaRGNQ3 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:03:54 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C24B41A00EF for <mile@ietf.org>; Thu, 22 May 2014 06:03:53 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id s4MD3pEA018245; Thu, 22 May 2014 22:03:51 +0900 (JST)
Received: from VAIO (ssh.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id s4MD3okD009355; Thu, 22 May 2014 22:03:50 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Eric Burger'" <eburger@standardstrack.com>, <mile@ietf.org>
References: <000001cf6b78$42243370$c66c9a50$@nict.go.jp> <63DF8BAD-3A7B-4454-8B40-AE8A9D1E1333@standardstrack.com>
In-Reply-To: <63DF8BAD-3A7B-4454-8B40-AE8A9D1E1333@standardstrack.com>
Date: Thu, 22 May 2014 22:03:48 +0900
Message-ID: <000a01cf75be$4623a190$d26ae4b0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGxQBO4+V5zEYmzFc7yxUkoAlHJeQKIqeOgm3S0GRA=
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith1
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/egf4PBetVCaI1KWUAEoZUnEz1ho
Subject: Re: [mile] New Version Notification for	draft-murillo-mile-cps-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 13:03:57 -0000

Hi Eric and Martin,

Thank you for your kind comment.
We will keep in mind that we should avoid having two things that do the same
thing.

In my humble opinion, the CPS draft hands issues that are outside the scope
of the SCI draft.
I think the next version of the CPS draft will sort out lots of this type of
questions.

Kind wishes,
Take


> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Eric Burger
> Sent: Thursday, May 22, 2014 4:56 AM
> To: mile@ietf.org
> Subject: Re: [mile] New Version Notification for
> draft-murillo-mile-cps-00.txt
> 
> And I do not think the world is eager to have two things that do the same
> thing. We already have that problem in this space. I would suggest
adopting
> one and only one way of doing this. I have no opinion as to whether it
should
> be CPS or SCI.
> 
> On May 9, 2014, at 7:17 AM, Takeshi Takahashi
> <takeshi_takahashi@nict.go.jp> wrote:
> 
> > Hi Martin,
> >
> > Thank you for your kind comments.
> >
> >> There's one question that still lingers: whether we should not
> >> re-utilize other extensions or use the IODEF-extension for structured
> >> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
> >> points above would be applicable to both scenarios.
> >
> > I like this CPS draft, but I also like IODEF-SCI's framework (well, I
> > am one of the authors).
> > I do not want to be the obstacle of developing this interesting work,
> > so I do not have any intention to stick to IODEF-SCI at all.
> > But I would like to understand the pros and cons of not using SCI
> > framework for the CPS extension more vividly.
> >
> > Section 1.7 of the CPS draft explains the reason for not using the
> > IODEF-SCI's framework, but it was not so clear to me..
> > Can we discuss this issue when we have got example XML documents of
> > the CPS extension? (I guess later version of the CPS draft will have
> > the example XML
> > documents?) Then we can compare how the XML documents will look like
> > for each case of using and not using IODEF-SCI framework on the CPS
> extension.
> >
> > Kind regards,
> > Take
> >
> >
> >> -----Original Message-----
> >> From: Martin Murillo [mailto:murillo@ieee.org]
> >> Sent: Wednesday, April 30, 2014 12:30 PM
> >> To: Takeshi Takahashi; mile@ietf.org
> >> Subject: Re: [mile] Fwd: New Version Notification for
> >> draft-murillo-mile-cps-00.txt
> >>
> >> Dear Takeshi,
> >>
> >> Thanks for the feedback and highlighting various extraneous elements
> >> which have rich IODEF equivalents. This makes the reporting lighter
> >> and decreases implementation overhead. I have answered to each item
> below.
> >>
> >> 1. The IncidentType element specifies whether the incident is
> >> accidental, on purpose, or theresult of other actions. The IncdntType
> >> attribute is missplaced. Thanks for taking notice of that. However I
> >> wonder whether the IncidentType element should be renamed. I think we
> >> agree that we need a field where whether the incident is accidental,
> >> on purpose, or undetermined can be placed. While the nature of the
> >> incident is rarely known immediately, there are instances in which
> >> the operator or other local party causes accidental instances; these
> >> instances might cause repercussions in other locations (i.e.
> >> balancing in
> > an electric grid).
> >>
> >> 2. I agree with you, the IncidentTilte element is a perfect candidate
> >> to go to a shallower level, especially when it will be the first
> >> variable that an operator or appropriate party reads.
> >>
> >> 3. Given that the IODEF:Contact class is rich enough to differentiate
> >> between a reporting party and an additional contact
> >> person/institution, I believe that we should use such class. Because
> >> the different stakeholders responsible for the Corporate Network,
> >> Control Servers, and Field Devices, this class might need to be
> >> extended. This is also relevant when the attack has taken place at
> >> any of those levels: For instance, the Corporate Network (or a false
> >> impersonator) might instruct the control room (Control servers) wrong
> >> setpoint configurations. Or the Control Network might experience a
> >> breach and setpoints altered in such servers. In extreme situations,
> >> the
> > attacks might be directly to the field devices. In each of those cases.
> >> In each of those cases the contact person might be one or more.
> >>
> >> 4, 5, 6. I think the IODEF classes can be indeed used. Thank you. The
> >> extension capabilities fo the System Class makes it quite appropriate
> >> to offer rich information.
> >>
> >> Regarding your last point, SFK should indeed be used instead of SFC.
> >>
> >> There's one question that still lingers: whether we should not
> >> re-utilize other extensions or use the IODEF-extension for structured
> >> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
> >> points above would be applicable to both scenarios.
> >>
> >> Martin
> >>
> >> On 4/23/2014 4:42 AM, Takeshi Takahashi wrote:
> >>> Hi Martin,
> >>>
> >>> I've read through the drafts. Thank you very much for sharing your
> >>> expertise here.
> >>> It was a new use case for me, and was really interesting.
> >>>
> >>> I am wondering if we can minimize the number of extension fields by
> >>> using the existing IODEF fields.
> >>> By minimizing the number of similar fields, I hope we can simplify
> >>> the draft and minimize the burden of implementations.
> >>>
> >>>> From this viewpoint, let me ask several checking questions.
> >>>
> >>> 1. IncidentType element and IncdntType Attribute
> >>>   What are the difference between them? I think your current draft
> >>> has them as place holders. I would like to hear a bit further.
> >>>
> >>> 2. The IncidentTitle element
> >>>   Can we use the Description element inside the IODEF:Incident class
> >>> for this purpose, instead of having new field here?
> >>>   It would be useful to have title or such information that can hint
> >>> the content of the IODEF document, but I feel like that it would be
> >>> helpful to have this type of information at the shallower level of
> >>> IODEF document rather than having it in the deeper level of IODEF
> >>> document (inside
> >>> additionalData)
> >>>
> >>> 3. The ReportingParty element
> >>>   Can we use the IODEF:contact class instead of having new field?
> >>> We could extend it further if needed.
> >>>
> >>> 4. The ReportReliability element
> >>>   Can we use the IODEF:confidence class instead of having new field?
> >>> We could extend it further if needed.
> >>>
> >>> 5. The TargetSystems element
> >>>   Can we extend the IODEF:system class instead of having new field?
> >>> We could extend it further if needed.
> >>>
> >>> 6. type attribute of the IODEF:Impact class
> >>>   When we use this extension, what value should be set for the type
> >>> attribute of the IODEF:Impact class?
> >>>
> >>> By the way, here are small questions.
> >>>
> >>> 1. should [SFC] be [SFK], since the acronym seems to come from the
> >>> initials of the authors of the reference (Stouffer, K., Falco, J.,
> >>> and
> >> K. Scarfonw) ?
> >>>
> >>> I might have misunderstood your draft, so please correct me if I am
> > wrong.
> >>>
> >>> Kind regards,
> >>> Take
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Martin
> >>>> Murillo
> >>>> Sent: Wednesday, January 29, 2014 10:11 AM
> >>>> To: Johnson, Blake; Jerome Athias
> >>>> Cc: mile@ietf.org
> >>>> Subject: Re: [mile] Fwd: New Version Notification for
> >>>> draft-murillo-mile-cps-00.txt
> >>>>
> >>>> Have read the links posted by Jerome and info on the Experience
> >>>> Sharing Tool (EST). It is my impression that a revision under the
> >>>> light of the EST would be very appropriate, and one of the first
> >>>> uses of the extension, given its report-based nature.  Look forward
> >>>> to seeing
> >>> the reviews in this light.
> >>>> As Jerome mentioned, focusing on referencing already existing
> >>>> taxonomies (and when necessary reusing them and referencing their
> >>>> xml implementations, if publicly available) would be the best
> >>>> approach; given the early stages in the field, I tend to think that
> >>>> atomic data will
> >>> need to be used.
> >>>> Regarding the term "Asset" vs "System", I believe system provides a
> >>>> more general connotation, while asset, seem to focus more on
> >>>> mainstream infrastructure; because the inclusion of IoT-related
> >>>> infrastructure (anywhere from centralized home control to
> >>>> self-driving cars), I wonder whether "Asset" is too an specific term.
> >>>>
> >>>> Martin
> >>>>
> >>>> Martin
> >>>>
> >>>> On 1/24/2014 2:09 PM, Johnson, Blake wrote:
> >>>>> This is an interesting application of IODEF that I had not
considered.
> >>>> Most industry sharing that takes place in this space, from my
> >>>> perspective, is in the form of in person and telephone threat
> >>>> briefings. These are facilitated by the FBI, DHS, and the ISAC's.
> >>>>> At least a handful of the ISAC's have started sharing structured
> >>>>> threat
> >>>> indicator data, and the taxonomy for this extension could cover
> >>>> what the Electric Sector ISAC currently refers to as 'Experience
> > Sharing.'
> >>>> I can review this proposal as it relates to information captured by
> >>>> the ES-ISAC's Experience Sharing tool, using IEC/ANSI 62443 (ISA99)
> >>>> as an informative reference.
> >>>>> Blake Johnson
> >>>>> Threat Intelligence Analyst
> >>>>> Alliant Energy | Infrastructure Secruity
> >>>>> Office: 608-458-6320 | Cell: 608-843-2790
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Jerome
> >>>>> Athias
> >>>>> Sent: Friday, January 24, 2014 3:18 AM
> >>>>> To: murillo@ieee.org
> >>>>> Cc: mile@ietf.org
> >>>>> Subject: Re: [mile] Fwd: New Version Notification for
> >>>>> draft-murillo-mile-cps-00.txt
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> from what I know (which is limited), and as you mention, this ICS
> >>>>> area is often also called Critical Infrastructures (CIs), or SCADA
> >>>>>
> >>>>> for a little bit of background, we could explore the Cybersecurity
> >>>>> Framework Example references
> >>>>> http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
> >>>>>
> >>>>
> >>
> http://www.ictqatar.qa/en/documents/download/National%20Industrial%20
> >>>> C
> >>>>> ontrol%20Systems%20Security%20Standard-English.pdf
> >>>>> ANSI/ISA-99.02.01-2009
> >>>>>
> >>>>> I don't have enough knowledge about the status and adoption of the
> >>>>> different efforts in term of XML representation/format/standards
> >>>>> http://xml.coverpages.org/emergencyManagement.html
> >>>>> and resilience
> >>>>>
> >>>>> It would maybe be possible to obtain information from there
> >>>>> http://ics-cert.us-cert.gov http://ics-isac.org/
> >>>>>
> >>>>> My first feedback is that it looks like an interesting extension.
> >>>>>
> >>>>> I would suggest to focus on the reuse of existing Taxonomies, or
> >>>>> references to them.
> >>>>>
> >>>>> As such, for [Industry], maybe
> >>>>> http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012
> >>>>> ISO 3166 (Country Codes)
> >>>>>
> >>>>>
> >>>>> [TargetSystems], I (personally) don't like the word "system" and
> >>>>> prefer
> >>>> "asset"
> >>>>> [CompromisedPhysicalInfrastrucute] (with a typo ;p) seems to be a
> >>>>> category of "Infrastructure" (or group of assets)
> >>>>>
> >>>>>
> >>>>> [EntryPoint] could be ok since it could be a little bit different
> >>>>> from "endpoint"
> >>>>>
> >>>>> [PerpetratingParty] seems to reference "Threat Actor" or "Threat
> >>>>> Agent" or "Attacker"
> >>>>>
> >>>>> [RecurrencePreventionMeasures] is this Security Controls? (and
> >>>>> Mitigations/Remediations)
> >>>>> Reference:
> >>>>>
> >> https://web.nvd.nist.gov/view/800-53/control?controlName=AC-3&type=1
> >>>>>
> >>>>>
> >>>>> Describing an [Exploit] is not so easy (depending on the level of
> >>>>> details wanted/needed)
> >>>>>
> >>>>> Figure 1 (or "Diagram 1") is interesting, (of course it is
> >>>>> different from, i.e. CAESARS), it MAYBE could be more layered
> >>>>>
> >>>>
> >>
> http://www.isa.org/InTechTemplate.cfm?template=/ContentManagement/Con
> >>>> t
> >>>>> entDisplay.cfm&ContentID=94401
> >>>>>
> >>>>> (To follow: ENISA CDXI)
> >>>>>
> >>>>>
> >>>>> Some typos
> >>>>>
> >>>>>
> >>>>>
> >>>>> Next step: more XML focused ;)
> >>>>>
> >>>>>
> >>>>> My 2 bitcents
> >>>>>
> >>>>> 2014/1/24 Martin Murillo <murillo@ieee.org>:
> >>>>>> Dear all,
> >>>>>>
> >>>>>> Please find below a link to a proposed draft for extending IODEF
> >>>>>> for the reporting of cyber-physical system incidents. These
> >>>>>> systems are often referred as  Operational Technology Systems,
> >>>>>> Industrial Control Systems, Automatic Control  Systems, or simply
> >>>>>> Control
> >> Systems.
> >>>>>>
> >>>>>> Cyber-Physical systems have been around for decades.  However,
> >>>>>> they are now at a higher risk to be  the target of attacks by
> >>>>>> individual highly-skilled attackers, organized groups,
> >>>>>> nation-states, or simply suffer repercussions of mainstream IT
> >>>>>> cyber-attacks. While over 90% of critical control system
> >>>>>> infrastructure is currently owned by private enterprises, these
> >>>>>> can have direct repercussions on national security of world
> >>>>>> nations.  Indeed, various of these systems are key parts of
> >>>>>> nuclear reactor facilities, transportation systems, electric
> >>>>>> power distribution, oil and natural gas distribution, health
> >>>>>> care, water
> >>>> and waste-water treatment, dam infrastructure, missile
> >>>>>> and defense systems, and others.   The disruption of these control
> >>>> systems
> >>>>>> could have a significant impact on public health, safety, and
> >>>>>> lead to large economic losses.
> >>>>>>
> >>>>>> Among the issues that catalyze this higher risk are:
> >>>>>>
> >>>>>> i) these systems are gradually becoming more interconnected, ii)
> >>>>>> legacy systems do not have proper cybersecurity protection, iii)
> >>>>>> the existence of highly-skilled individuals and motivations, iv)
> >>>>>> some these systems are generally considered critical, v) these
> >>>>>> are a natural extension of IT cyber-attacks, vi) the emergence of
> >>>>>> the Internet of Things (IOT), and vi) these attacks can be
> >>>>>> carried out
> >>>> remotely and quite inexpensively.
> >>>>>> While there might exist national approaches to deal with
> >>>>>> incidents, there's the need of a global international approach
> >>>>>> that will engulf governments, private organizations and other
> > stakeholders.
> >>>>>> IETF, as a leading global Internet standards organization, seeks
> >>>>>> to satisfy this need through open standards that seek to
> >>>>>> encompass issues that are critical for the global community.
> >>>>>>
> >>>>>> Feedback at two levels are welcome:
> >>>>>>
> >>>>>> 1. On the existence and inclusion either by utilizing any already
> >>> existing
> >>>>>> industry formats (XML-   encoded) and/or by utilizing atomic data
> >>>>>> 2. Contributions on making the extension (and background
> >>>>>> information) more comprehensive, accurate and principally useful
> >>>>>> for the community
> >>>>>>
> >>>>>> Look forward to feedback and other input!
> >>>>>>
> >>>>>> Martin Murillo
> >>>>>>
> >>>>>> A new version of I-D, draft-murillo-mile-cps-00.txt has been
> >>>>>> successfully submitted by Martin Murillo and posted to the IETF
> >>>>>> repository.
> >>>>>>
> >>>>>> Name:           draft-murillo-mile-cps
> >>>>>> Revision:       00
> >>>>>> Title:          IODEF extension for Reporting Cyber-Physical
> System
> >>>>>> Incidents
> >>>>>> Document date:  2014-01-21
> >>>>>> Group:          Individual Submission
> >>>>>> Pages:          24
> >>>>>> URL:
> >>>>>>
> http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt
> >>>>>> Status:
> >>>> https://datatracker.ietf.org/doc/draft-murillo-mile-cps/
> >>>>>> Htmlized:
> >> http://tools.ietf.org/html/draft-murillo-mile-cps-00
> >>>>>>
> >>>>>>
> >>>>>> Abstract:
> >>>>>>    This draft document will extend the Incident Object Description
> >>>>>>    Exchange Format (IODEF) defined in [RFC5070] to support the
> >>>> reporting
> >>>>>>    of incidents dealing with attacks to physical infrastructure
> >>> through
> >>>>>>    the utilization of IT means as a vehicle or as a tool.  These
> >>> systems
> >>>>>>    might also be referred as Cyber-Physical Systems (CPS),
> >> Operational
> >>>>>>    Technology Systems, Industrial Control Systems, Automatic
> >> Control
> >>>>>>    Systems, or simply Control Systems.  These names are used
> >>>>>>    interchangeably in this document.  In this context, an
> >>>>>> incident
> >> is
> >>>>>>    generally the result of a cybersecurity issue whose main goal
> >>>>>> is
> >>>> to
> >>>>>>    affect the operation of a CPS.  It is considered that any
> >>>>>>    unauthorized alteration of the operation is always malign.  This
> >>>>>>    extension will provide the capability of embedding structured
> >>>>>>    information, such as identifier- and XML-based information.
> >>>>>> In
> >> its
> >>>>>>    current state, this document provides important considerations
> >> for
> >>>>>>    further work in implementing Cyber-Physical System incident
> >>>> reports,
> >>>>>>    either by utilizing any already existing industry formats (XML-
> >>>>>>    encoded) and/or by utilizing atomic data.
> >>>>>>
> >>>>>>    In addition, this document should provide appropriate material
> >> for
> >>>>>>    helping making due considerations in making an appropriate
> >> decision
> >>>>>>    on how a CPS reporting is done: 1) through a data format
> >>>>>> extension
> >>>> to
> >>>>>>    the Incident Object Description Exchange Format [RFC5070], 2)
> >>>> forming
> >>>>>>    part of an already existing IODEF-extension for structured
> >>>>>>    cybersecurity information (currently draft
> >>>>>>    draft-ietf-mile-sci-11.txt), or others.  While the format and
> >>>>>>    contents of the present document fit more the earlier option,
> > these
> >>>>>>    can also be incorporated to the later.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Please note that it may take a couple of minutes from the time of
> >>>>>> submission until the htmlized version and diff are available at
> >>>> tools.ietf.org.
> >>>>>> The IETF Secretariat
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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



From nobody Thu May 22 06:22:53 2014
Return-Path: <adam@stoicsecurity.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47EE01A0091 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 xmJNRVk5jnLt for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:22:46 -0700 (PDT)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0C361A001A for <mile@ietf.org>; Thu, 22 May 2014 06:22:45 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id lj1so2489758pab.22 for <mile@ietf.org>; Thu, 22 May 2014 06:22:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=slPtBMx3SsesZjkhY8UZKrTXr6ft1naC1B6J0ea1QNs=; b=fp3lY8Ni2swUgPErdW+PXTTTq5l0n+NsyeNTBJqDt6RZQbIJR10KOT68OCXfpmGJn5 e1fAW3YGDcumjV7btL3xv5jg7URBpogmPhkI1Gke+uImBtoQJxOgQVFOcs5dyf+dHBYy g9DBt4mseQHpVxJUxBpyKmm2pViT8jEDDEoYKmIlnaEkDxg0gwMBWv7Ht34iufw3wBOV X8+4xfWo+spXOovr5uAcj3/UhoGfNVR/TYGSDyp/qaKrIIi8USDRFWPoizH9Kql8JBpg ONSqv7LiFfaPFEbCjO0Q9oTkOLh/0Avw2g4nBal/h29re1hiJewJ4k3zhCFXqhK2o1aB seSw==
X-Gm-Message-State: ALoCoQkqPH829njKqjhXer8O+A5Z1yUn4Dpkqj0xCFeUsldzCrskvFpm3L7ldisQik8uPa/U9LEo
X-Received: by 10.66.141.109 with SMTP id rn13mr68783218pab.117.1400764964687;  Thu, 22 May 2014 06:22:44 -0700 (PDT)
Received: from [10.149.44.143] ([166.170.41.50]) by mx.google.com with ESMTPSA id pr4sm13107176pbb.53.2014.05.22.06.22.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 May 2014 06:22:42 -0700 (PDT)
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com> <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp>
Mime-Version: 1.0 (1.0)
In-Reply-To: <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com>
X-Mailer: iPad Mail (11D201)
From: "Adam W. Montville" <adam@stoicsecurity.com>
Date: Thu, 22 May 2014 06:22:39 -0700
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/FIPv5s2k-vJq377e8JB0Z4NrNXQ
Cc: "<mile@ietf.org>" <mile@ietf.org>, "<mile-chairs@tools.ietf.org>" <mile-chairs@tools.ietf.org>
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 13:22:48 -0000

> On May 22, 2014, at 4:44 AM, "Takeshi Takahashi" <takeshi_takahashi@nict.g=
o.jp> wrote:
>=20
> Hi Adam,
>=20
> I remember that we had discussion on the Index field last year.
> We have a field for the Index and not for version number.
> That is because "the Index field in the XML unambiguously indicates which
> IANA registry entry is to be used to correctly reference the enumeration
> specification, which avoids interpretation of version strings that may hav=
e
> specification-specific formats" (copied from the draft).
> Yes, this was what I understood in the discussion last year.
>=20
> Now I am reading the document again, and have stuck on one question.
> Maybe I have some misunderstanding or have forgotten some discussion, but I=

> would appreciate if you could clarify the issue below.
>=20
> If we have Index field, do we need the Abbreviation field?
>=20
> Below is the example described in the draft.
> <EnumRef>
>  <Abbreviation>CXI</Abbreviation>
>  <Index>1</Index>
>  <ID>CXI-1234-XYZ</ID>
> </EnumRef>
>=20
> But can we simply write like this?
> <EnumRef>
>  <Index>1</Index>
>  <ID>CXI-1234-XYZ</ID>
> </EnumRef>
>=20
> If we have the Index value, we can uniquely identify the specification and=

> version, correct?

I believe you are correct, and I can't think of a reason to keep the abbrevi=
ation field.


>=20
> Take
>=20
>=20
>> -----Original Message-----
>> From: Adam Montville [mailto:adam@stoicsecurity.com]
>> Sent: Monday, May 19, 2014 10:59 PM
>> To: Black, David
>> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
>> Subject: Re: Reference and related nits in
>> draft-ietf-mile-enum-reference-format
>>=20
>> David, thank you.  I've noted all of these and will make appropriate
>> updates.
>>=20
>> Are there other comments other than those posed by Alexey and David?
>>=20
>>> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> wrote:
>>>=20
>>> Hi Adam,
>>>=20
>>>> With respect to your first sentence above, I assert that the document
>>>> does not "seem" to update ReferenceName, but actually does. :-)  Is
>>>> it necessary to explicitly state the obvious in this case?  I'm happy
>>>> to update the document, but I'm not sure I believe such a statement
>>>> is necessary.  If it is necessary, then a single sentence can be added
>> to the abstract making the statement.
>>>> Thoughts here?
>>>=20
>>> In this case, it is necessary to state the obvious for the sake of
>>> clarity - I've been there and had to do that ;-).  In addition to a
>>> sentence in the abstract, the header on the title page needs an
> "Updates:
>> 5070 (if approved)"
>>> line, and a section should be added entitled "Summary of Changes to RFC
>> 5070"
>>> that identifies the changes.
>>>=20
>>> For a somewhat longer recent example, see RFC 7146:
>>>    http://datatracker.ietf.org/doc/rfc7146/
>>>=20
>>> ----------------
>>>=20
>>> Here are some additional editorial nits that need attention ...
>>>=20
>>> a) I recently had another draft dinged by the IESG for using a
>>> citation as a word in a sentence e.g., "[IODEF]" in the first sentence
>> in Section 2:
>>>=20
>>>  The need is to place enumeration identifiers and their references in
>>>  [IODEF]'s Reference class.
>>>=20
>>> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
>>> [IODEF]" - I suggest just doing this and not asking why :-). The whole
>>> draft should be checked for other uses of citations in this fashion.
>>>=20
>>> b) In addition, references should not be cited in the abstract, so I
>>> believe the appropriate changes to the two citations in the abstract
> are:
>>>=20
>>>  The Incident Object Description Exchange Format [IODEF] provides a
>>>=20
>>>        "[IODEF]" -> "(IODEF)"
>>>=20
>>>  Reference class used to reference external entities (such as
>>>  enumeration identifiers).  However, the method of external entity
>>>  identification has been left unstructured.  This document describes
>> a
>>>  method to provide structure for referencing external entities for the
>>>  [IODEF] Reference class.
>>>=20
>>>        "[IODEF]" -> "IODEF"
>>>=20
>>> Otherwise, the draft still looks good.
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
>>>> Sent: Sunday, May 18, 2014 7:58 PM
>>>> To: Alexey Melnikov
>>>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>> Subject: Re: [mile] Working Group Last Call for draft-ietf-mile-enum-
>>>> reference-format
>>>>=20
>>>>=20
>>>> On May 11, 2014, at 2:54 PM, Alexey Melnikov
>>>> <alexey.melnikov@isode.com>
>>>> wrote:
>>>>=20
>>>>>=20
>>>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
>>>>>> <takeshi_takahashi@nict.go.jp>
>>>> wrote:
>>>>>>=20
>>>>>> Greetings, all,
>>>>>>=20
>>>>>> This is the Working Group Last Call for
>>>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration Reference
>> Format.
>>>>>>=20
>>>>>> The last call starts now, and ends Monday 26 May 2014.
>>>>>>=20
>>>>>> Please read the latest revision of the draft,
>> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
>>>>>> , and send your comments to the mailing list; we'd also appreciate
>>>>>> a comment if you're fine with the draft as is.
>>>>>=20
>>>>> Hi,
>>>>> Below is my review of the draft:
>>>>>=20
>>>>> General comment: Is this intended as Proposed Standard? The draft
>>>>> header
>>>> doesn't say the document type.
>>>>=20
>>>> I'll update this, thank you.
>>>>=20
>>>>>=20
>>>>> The document seems to update ReferenceName syntax to allow for
>>>>> nested XML
>>>> elements. However the document doesn't say that.
>>>>> In relationship to this: would this document cause any
>>>>> interoperability
>>>> issues with programs that can only parse the old schema?
>>>>=20
>>>> I am unsure about interoperability issues, but they should be minimal
>>>> and are likely implementation specific.
>>>>=20
>>>> I tried an experiment where I generated some code (JAXB) for IODEF
>>>> 1.0 and then fed it a modified recon example (Section 7.2 from RFC
>>>> 5070).  The <ReferenceName> element contained an <EnumRef> element as
>>>> opposed to the string "nmap".  Unmarshalling seemed to work without
>>>> issue, but when examining the ReferenceName element , the only thing
>> present was a newline character.
>>>> In an example that doesn't use generated code but instead uses a SAX
>>>> or DOM parser, we can grab the inner XML.  Using a validating
>>>> DOM/SAX/other parser will, of course, break if the enumeration
>>>> reference XML is embedded, so parsers will need to be updated.
>>>>=20
>>>> I'm not a professional implementor, so it would be good to hear
>>>> considerations from others.  Then, should these considerations be
>>>> placed in the document (I assume that was the good point of raising the=

>> issue)?
>>>>=20
>>>> With respect to your first sentence above, I assert that the document
>>>> does not "seem" to update ReferenceName, but actually does. :-)  Is
>>>> it necessary to explicitly state the obvious in this case?  I'm happy
>>>> to update the document, but I'm not sure I believe such a statement
>>>> is necessary.  If it is necessary, then a single sentence can be added
>> to the abstract making the statement.
>>>> Thoughts here?
>>>>=20
>>>>=20
>>>>>=20
>>>>>=20
>>>>> 4  IANA Considerations
>>>>>=20
>>>>>    Note that certain name requests should not be permitted as either
>>>>>    Full Name or Abbreviation entries for the requested IANA table.
>>>>>=20
>>>>> Do you mean restrictions imposed by the syntax described below or
>>>>> something
>>>> else? If you intended to exclude some specific keywords, where is the
>>>> list of them defined? Either way, I think you need to clarify. If you
>>>> just meant the ABNF restrictions, I suggest adding something like
>>>> "The restrictions are specified in the ABNF below".
>>>>>=20
>>>>>    Allocation Policy: Expert Review [RFC5226] and Specification
>>>>>    Required [RFC5226]
>>>>>=20
>>>>> Nit: I think it would be better to say "Specification Required
>>>>> (which
>>>> implies Expert Review)".
>>>>>=20
>>>>> _______________________________________________
>>>>> mile mailing list
>>>>> mile@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mile
>=20
>=20


From nobody Thu May 22 06:53:05 2014
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3151A01BA for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 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, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=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 C3cYBDO-1BP0 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 06:53:00 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BA361A0176 for <mile@ietf.org>; Thu, 22 May 2014 06:53:00 -0700 (PDT)
Received: by mail-yh0-f47.google.com with SMTP id z6so2979680yhz.34 for <mile@ietf.org>; Thu, 22 May 2014 06:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8kH+ViPTIhGPGQnK4KXMEGijTlYX3Yy2SJFvxL2SEtw=; b=ts7/BsTXqdASPixbHQ37xqQGGBwfe5KMyRAooTCTFtuJfU6vAD30PBpti5qGbmkbLe dg68h6vBIqyRJU/ZNPhjvCKsZ7bIBdub7nPSOKz0SMHhqTsFLZz5oJ6yKg1WcyMgCmM7 SO92ABeZygOKP+ZPj9jemTeQ+7/khga42WV6nTcK0gE3vzMAp0GQeVtp07Gk+TKdy2m5 hUY8V+Kvzi5NnM5wpo89G7EwSeWitdqQuAGUidD4MXt3o7KtTPr8LIO9spfjA7vDj0wH FHdsPoz5TmI703FSDT+33evpapwPSTHO1ymNTYyVF5kpqKXvJFepxt5DscHjM4IqjwBP 2q2w==
X-Received: by 10.236.157.40 with SMTP id n28mr30089537yhk.29.1400766778470; Thu, 22 May 2014 06:52:58 -0700 (PDT)
Received: from [10.210.130.79] (mobile-166-147-117-244.mycingular.net. [166.147.117.244]) by mx.google.com with ESMTPSA id m50sm8433123yha.8.2014.05.22.06.52.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 22 May 2014 06:52:57 -0700 (PDT)
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (11D167)
In-Reply-To: <000a01cf75be$4623a190$d26ae4b0$@nict.go.jp>
Date: Thu, 22 May 2014 09:52:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D802BE8-B9B5-4B5D-80A1-783F25BBFF5D@gmail.com>
References: <000001cf6b78$42243370$c66c9a50$@nict.go.jp> <63DF8BAD-3A7B-4454-8B40-AE8A9D1E1333@standardstrack.com> <000a01cf75be$4623a190$d26ae4b0$@nict.go.jp>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/fH5lJJzS-wPLQtpOQ6J17RZyQ3I
Cc: "<mile@ietf.org>" <mile@ietf.org>, Eric Burger <eburger@standardstrack.com>
Subject: Re: [mile] New Version Notification for	draft-murillo-mile-cps-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 13:53:04 -0000

+1

Sent from my iPhone

> On May 22, 2014, at 9:03 AM, "Takeshi Takahashi" <takeshi_takahashi@nict.g=
o.jp> wrote:
>=20
> Hi Eric and Martin,
>=20
> Thank you for your kind comment.
> We will keep in mind that we should avoid having two things that do the sa=
me
> thing.
>=20
> In my humble opinion, the CPS draft hands issues that are outside the scop=
e
> of the SCI draft.
> I think the next version of the CPS draft will sort out lots of this type o=
f
> questions.
>=20
> Kind wishes,
> Take
>=20
>=20
>> -----Original Message-----
>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Eric Burger
>> Sent: Thursday, May 22, 2014 4:56 AM
>> To: mile@ietf.org
>> Subject: Re: [mile] New Version Notification for
>> draft-murillo-mile-cps-00.txt
>>=20
>> And I do not think the world is eager to have two things that do the same=

>> thing. We already have that problem in this space. I would suggest
> adopting
>> one and only one way of doing this. I have no opinion as to whether it
> should
>> be CPS or SCI.
>>=20
>> On May 9, 2014, at 7:17 AM, Takeshi Takahashi
>> <takeshi_takahashi@nict.go.jp> wrote:
>>=20
>>> Hi Martin,
>>>=20
>>> Thank you for your kind comments.
>>>=20
>>>> There's one question that still lingers: whether we should not
>>>> re-utilize other extensions or use the IODEF-extension for structured
>>>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
>>>> points above would be applicable to both scenarios.
>>>=20
>>> I like this CPS draft, but I also like IODEF-SCI's framework (well, I
>>> am one of the authors).
>>> I do not want to be the obstacle of developing this interesting work,
>>> so I do not have any intention to stick to IODEF-SCI at all.
>>> But I would like to understand the pros and cons of not using SCI
>>> framework for the CPS extension more vividly.
>>>=20
>>> Section 1.7 of the CPS draft explains the reason for not using the
>>> IODEF-SCI's framework, but it was not so clear to me..
>>> Can we discuss this issue when we have got example XML documents of
>>> the CPS extension? (I guess later version of the CPS draft will have
>>> the example XML
>>> documents?) Then we can compare how the XML documents will look like
>>> for each case of using and not using IODEF-SCI framework on the CPS
>> extension.
>>>=20
>>> Kind regards,
>>> Take
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Martin Murillo [mailto:murillo@ieee.org]
>>>> Sent: Wednesday, April 30, 2014 12:30 PM
>>>> To: Takeshi Takahashi; mile@ietf.org
>>>> Subject: Re: [mile] Fwd: New Version Notification for
>>>> draft-murillo-mile-cps-00.txt
>>>>=20
>>>> Dear Takeshi,
>>>>=20
>>>> Thanks for the feedback and highlighting various extraneous elements
>>>> which have rich IODEF equivalents. This makes the reporting lighter
>>>> and decreases implementation overhead. I have answered to each item
>> below.
>>>>=20
>>>> 1. The IncidentType element specifies whether the incident is
>>>> accidental, on purpose, or theresult of other actions. The IncdntType
>>>> attribute is missplaced. Thanks for taking notice of that. However I
>>>> wonder whether the IncidentType element should be renamed. I think we
>>>> agree that we need a field where whether the incident is accidental,
>>>> on purpose, or undetermined can be placed. While the nature of the
>>>> incident is rarely known immediately, there are instances in which
>>>> the operator or other local party causes accidental instances; these
>>>> instances might cause repercussions in other locations (i.e.
>>>> balancing in
>>> an electric grid).
>>>>=20
>>>> 2. I agree with you, the IncidentTilte element is a perfect candidate
>>>> to go to a shallower level, especially when it will be the first
>>>> variable that an operator or appropriate party reads.
>>>>=20
>>>> 3. Given that the IODEF:Contact class is rich enough to differentiate
>>>> between a reporting party and an additional contact
>>>> person/institution, I believe that we should use such class. Because
>>>> the different stakeholders responsible for the Corporate Network,
>>>> Control Servers, and Field Devices, this class might need to be
>>>> extended. This is also relevant when the attack has taken place at
>>>> any of those levels: For instance, the Corporate Network (or a false
>>>> impersonator) might instruct the control room (Control servers) wrong
>>>> setpoint configurations. Or the Control Network might experience a
>>>> breach and setpoints altered in such servers. In extreme situations,
>>>> the
>>> attacks might be directly to the field devices. In each of those cases.
>>>> In each of those cases the contact person might be one or more.
>>>>=20
>>>> 4, 5, 6. I think the IODEF classes can be indeed used. Thank you. The
>>>> extension capabilities fo the System Class makes it quite appropriate
>>>> to offer rich information.
>>>>=20
>>>> Regarding your last point, SFK should indeed be used instead of SFC.
>>>>=20
>>>> There's one question that still lingers: whether we should not
>>>> re-utilize other extensions or use the IODEF-extension for structured
>>>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
>>>> points above would be applicable to both scenarios.
>>>>=20
>>>> Martin
>>>>=20
>>>>> On 4/23/2014 4:42 AM, Takeshi Takahashi wrote:
>>>>> Hi Martin,
>>>>>=20
>>>>> I've read through the drafts. Thank you very much for sharing your
>>>>> expertise here.
>>>>> It was a new use case for me, and was really interesting.
>>>>>=20
>>>>> I am wondering if we can minimize the number of extension fields by
>>>>> using the existing IODEF fields.
>>>>> By minimizing the number of similar fields, I hope we can simplify
>>>>> the draft and minimize the burden of implementations.
>>>>>=20
>>>>>> =46rom this viewpoint, let me ask several checking questions.
>>>>>=20
>>>>> 1. IncidentType element and IncdntType Attribute
>>>>>  What are the difference between them? I think your current draft
>>>>> has them as place holders. I would like to hear a bit further.
>>>>>=20
>>>>> 2. The IncidentTitle element
>>>>>  Can we use the Description element inside the IODEF:Incident class
>>>>> for this purpose, instead of having new field here?
>>>>>  It would be useful to have title or such information that can hint
>>>>> the content of the IODEF document, but I feel like that it would be
>>>>> helpful to have this type of information at the shallower level of
>>>>> IODEF document rather than having it in the deeper level of IODEF
>>>>> document (inside
>>>>> additionalData)
>>>>>=20
>>>>> 3. The ReportingParty element
>>>>>  Can we use the IODEF:contact class instead of having new field?
>>>>> We could extend it further if needed.
>>>>>=20
>>>>> 4. The ReportReliability element
>>>>>  Can we use the IODEF:confidence class instead of having new field?
>>>>> We could extend it further if needed.
>>>>>=20
>>>>> 5. The TargetSystems element
>>>>>  Can we extend the IODEF:system class instead of having new field?
>>>>> We could extend it further if needed.
>>>>>=20
>>>>> 6. type attribute of the IODEF:Impact class
>>>>>  When we use this extension, what value should be set for the type
>>>>> attribute of the IODEF:Impact class?
>>>>>=20
>>>>> By the way, here are small questions.
>>>>>=20
>>>>> 1. should [SFC] be [SFK], since the acronym seems to come from the
>>>>> initials of the authors of the reference (Stouffer, K., Falco, J.,
>>>>> and
>>>> K. Scarfonw) ?
>>>>>=20
>>>>> I might have misunderstood your draft, so please correct me if I am
>>> wrong.
>>>>>=20
>>>>> Kind regards,
>>>>> Take
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Martin
>>>>>> Murillo
>>>>>> Sent: Wednesday, January 29, 2014 10:11 AM
>>>>>> To: Johnson, Blake; Jerome Athias
>>>>>> Cc: mile@ietf.org
>>>>>> Subject: Re: [mile] Fwd: New Version Notification for
>>>>>> draft-murillo-mile-cps-00.txt
>>>>>>=20
>>>>>> Have read the links posted by Jerome and info on the Experience
>>>>>> Sharing Tool (EST). It is my impression that a revision under the
>>>>>> light of the EST would be very appropriate, and one of the first
>>>>>> uses of the extension, given its report-based nature.  Look forward
>>>>>> to seeing
>>>>> the reviews in this light.
>>>>>> As Jerome mentioned, focusing on referencing already existing
>>>>>> taxonomies (and when necessary reusing them and referencing their
>>>>>> xml implementations, if publicly available) would be the best
>>>>>> approach; given the early stages in the field, I tend to think that
>>>>>> atomic data will
>>>>> need to be used.
>>>>>> Regarding the term "Asset" vs "System", I believe system provides a
>>>>>> more general connotation, while asset, seem to focus more on
>>>>>> mainstream infrastructure; because the inclusion of IoT-related
>>>>>> infrastructure (anywhere from centralized home control to
>>>>>> self-driving cars), I wonder whether "Asset" is too an specific term.=

>>>>>>=20
>>>>>> Martin
>>>>>>=20
>>>>>> Martin
>>>>>>=20
>>>>>>> On 1/24/2014 2:09 PM, Johnson, Blake wrote:
>>>>>>> This is an interesting application of IODEF that I had not
> considered.
>>>>>> Most industry sharing that takes place in this space, from my
>>>>>> perspective, is in the form of in person and telephone threat
>>>>>> briefings. These are facilitated by the FBI, DHS, and the ISAC's.
>>>>>>> At least a handful of the ISAC's have started sharing structured
>>>>>>> threat
>>>>>> indicator data, and the taxonomy for this extension could cover
>>>>>> what the Electric Sector ISAC currently refers to as 'Experience
>>> Sharing.'
>>>>>> I can review this proposal as it relates to information captured by
>>>>>> the ES-ISAC's Experience Sharing tool, using IEC/ANSI 62443 (ISA99)
>>>>>> as an informative reference.
>>>>>>> Blake Johnson
>>>>>>> Threat Intelligence Analyst
>>>>>>> Alliant Energy | Infrastructure Secruity
>>>>>>> Office: 608-458-6320 | Cell: 608-843-2790
>>>>>>>=20
>>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Jerome
>>>>>>> Athias
>>>>>>> Sent: Friday, January 24, 2014 3:18 AM
>>>>>>> To: murillo@ieee.org
>>>>>>> Cc: mile@ietf.org
>>>>>>> Subject: Re: [mile] Fwd: New Version Notification for
>>>>>>> draft-murillo-mile-cps-00.txt
>>>>>>>=20
>>>>>>> Hi,
>>>>>>>=20
>>>>>>> from what I know (which is limited), and as you mention, this ICS
>>>>>>> area is often also called Critical Infrastructures (CIs), or SCADA
>>>>>>>=20
>>>>>>> for a little bit of background, we could explore the Cybersecurity
>>>>>>> Framework Example references
>>>>>>> http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
>> http://www.ictqatar.qa/en/documents/download/National%20Industrial%20
>>>>>> C
>>>>>>> ontrol%20Systems%20Security%20Standard-English.pdf
>>>>>>> ANSI/ISA-99.02.01-2009
>>>>>>>=20
>>>>>>> I don't have enough knowledge about the status and adoption of the
>>>>>>> different efforts in term of XML representation/format/standards
>>>>>>> http://xml.coverpages.org/emergencyManagement.html
>>>>>>> and resilience
>>>>>>>=20
>>>>>>> It would maybe be possible to obtain information from there
>>>>>>> http://ics-cert.us-cert.gov http://ics-isac.org/
>>>>>>>=20
>>>>>>> My first feedback is that it looks like an interesting extension.
>>>>>>>=20
>>>>>>> I would suggest to focus on the reuse of existing Taxonomies, or
>>>>>>> references to them.
>>>>>>>=20
>>>>>>> As such, for [Industry], maybe
>>>>>>> http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=3D2012
>>>>>>> ISO 3166 (Country Codes)
>>>>>>>=20
>>>>>>>=20
>>>>>>> [TargetSystems], I (personally) don't like the word "system" and
>>>>>>> prefer
>>>>>> "asset"
>>>>>>> [CompromisedPhysicalInfrastrucute] (with a typo ;p) seems to be a
>>>>>>> category of "Infrastructure" (or group of assets)
>>>>>>>=20
>>>>>>>=20
>>>>>>> [EntryPoint] could be ok since it could be a little bit different
>>>>>>> from "endpoint"
>>>>>>>=20
>>>>>>> [PerpetratingParty] seems to reference "Threat Actor" or "Threat
>>>>>>> Agent" or "Attacker"
>>>>>>>=20
>>>>>>> [RecurrencePreventionMeasures] is this Security Controls? (and
>>>>>>> Mitigations/Remediations)
>>>>>>> Reference:
>>>> https://web.nvd.nist.gov/view/800-53/control?controlName=3DAC-3&type=3D=
1
>>>>>>>=20
>>>>>>>=20
>>>>>>> Describing an [Exploit] is not so easy (depending on the level of
>>>>>>> details wanted/needed)
>>>>>>>=20
>>>>>>> Figure 1 (or "Diagram 1") is interesting, (of course it is
>>>>>>> different from, i.e. CAESARS), it MAYBE could be more layered
>> http://www.isa.org/InTechTemplate.cfm?template=3D/ContentManagement/Con
>>>>>> t
>>>>>>> entDisplay.cfm&ContentID=3D94401
>>>>>>>=20
>>>>>>> (To follow: ENISA CDXI)
>>>>>>>=20
>>>>>>>=20
>>>>>>> Some typos
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> Next step: more XML focused ;)
>>>>>>>=20
>>>>>>>=20
>>>>>>> My 2 bitcents
>>>>>>>=20
>>>>>>> 2014/1/24 Martin Murillo <murillo@ieee.org>:
>>>>>>>> Dear all,
>>>>>>>>=20
>>>>>>>> Please find below a link to a proposed draft for extending IODEF
>>>>>>>> for the reporting of cyber-physical system incidents. These
>>>>>>>> systems are often referred as  Operational Technology Systems,
>>>>>>>> Industrial Control Systems, Automatic Control  Systems, or simply
>>>>>>>> Control
>>>> Systems.
>>>>>>>>=20
>>>>>>>> Cyber-Physical systems have been around for decades.  However,
>>>>>>>> they are now at a higher risk to be  the target of attacks by
>>>>>>>> individual highly-skilled attackers, organized groups,
>>>>>>>> nation-states, or simply suffer repercussions of mainstream IT
>>>>>>>> cyber-attacks. While over 90% of critical control system
>>>>>>>> infrastructure is currently owned by private enterprises, these
>>>>>>>> can have direct repercussions on national security of world
>>>>>>>> nations.  Indeed, various of these systems are key parts of
>>>>>>>> nuclear reactor facilities, transportation systems, electric
>>>>>>>> power distribution, oil and natural gas distribution, health
>>>>>>>> care, water
>>>>>> and waste-water treatment, dam infrastructure, missile
>>>>>>>> and defense systems, and others.   The disruption of these control
>>>>>> systems
>>>>>>>> could have a significant impact on public health, safety, and
>>>>>>>> lead to large economic losses.
>>>>>>>>=20
>>>>>>>> Among the issues that catalyze this higher risk are:
>>>>>>>>=20
>>>>>>>> i) these systems are gradually becoming more interconnected, ii)
>>>>>>>> legacy systems do not have proper cybersecurity protection, iii)
>>>>>>>> the existence of highly-skilled individuals and motivations, iv)
>>>>>>>> some these systems are generally considered critical, v) these
>>>>>>>> are a natural extension of IT cyber-attacks, vi) the emergence of
>>>>>>>> the Internet of Things (IOT), and vi) these attacks can be
>>>>>>>> carried out
>>>>>> remotely and quite inexpensively.
>>>>>>>> While there might exist national approaches to deal with
>>>>>>>> incidents, there's the need of a global international approach
>>>>>>>> that will engulf governments, private organizations and other
>>> stakeholders.
>>>>>>>> IETF, as a leading global Internet standards organization, seeks
>>>>>>>> to satisfy this need through open standards that seek to
>>>>>>>> encompass issues that are critical for the global community.
>>>>>>>>=20
>>>>>>>> Feedback at two levels are welcome:
>>>>>>>>=20
>>>>>>>> 1. On the existence and inclusion either by utilizing any already
>>>>> existing
>>>>>>>> industry formats (XML-   encoded) and/or by utilizing atomic data
>>>>>>>> 2. Contributions on making the extension (and background
>>>>>>>> information) more comprehensive, accurate and principally useful
>>>>>>>> for the community
>>>>>>>>=20
>>>>>>>> Look forward to feedback and other input!
>>>>>>>>=20
>>>>>>>> Martin Murillo
>>>>>>>>=20
>>>>>>>> A new version of I-D, draft-murillo-mile-cps-00.txt has been
>>>>>>>> successfully submitted by Martin Murillo and posted to the IETF
>>>>>>>> repository.
>>>>>>>>=20
>>>>>>>> Name:           draft-murillo-mile-cps
>>>>>>>> Revision:       00
>>>>>>>> Title:          IODEF extension for Reporting Cyber-Physical
>> System
>>>>>>>> Incidents
>>>>>>>> Document date:  2014-01-21
>>>>>>>> Group:          Individual Submission
>>>>>>>> Pages:          24
>>>>>>>> URL:
>> http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt
>>>>>>>> Status:
>>>>>> https://datatracker.ietf.org/doc/draft-murillo-mile-cps/
>>>>>>>> Htmlized:
>>>> http://tools.ietf.org/html/draft-murillo-mile-cps-00
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Abstract:
>>>>>>>>   This draft document will extend the Incident Object Description
>>>>>>>>   Exchange Format (IODEF) defined in [RFC5070] to support the
>>>>>> reporting
>>>>>>>>   of incidents dealing with attacks to physical infrastructure
>>>>> through
>>>>>>>>   the utilization of IT means as a vehicle or as a tool.  These
>>>>> systems
>>>>>>>>   might also be referred as Cyber-Physical Systems (CPS),
>>>> Operational
>>>>>>>>   Technology Systems, Industrial Control Systems, Automatic
>>>> Control
>>>>>>>>   Systems, or simply Control Systems.  These names are used
>>>>>>>>   interchangeably in this document.  In this context, an
>>>>>>>> incident
>>>> is
>>>>>>>>   generally the result of a cybersecurity issue whose main goal
>>>>>>>> is
>>>>>> to
>>>>>>>>   affect the operation of a CPS.  It is considered that any
>>>>>>>>   unauthorized alteration of the operation is always malign.  This
>>>>>>>>   extension will provide the capability of embedding structured
>>>>>>>>   information, such as identifier- and XML-based information.
>>>>>>>> In
>>>> its
>>>>>>>>   current state, this document provides important considerations
>>>> for
>>>>>>>>   further work in implementing Cyber-Physical System incident
>>>>>> reports,
>>>>>>>>   either by utilizing any already existing industry formats (XML-
>>>>>>>>   encoded) and/or by utilizing atomic data.
>>>>>>>>=20
>>>>>>>>   In addition, this document should provide appropriate material
>>>> for
>>>>>>>>   helping making due considerations in making an appropriate
>>>> decision
>>>>>>>>   on how a CPS reporting is done: 1) through a data format
>>>>>>>> extension
>>>>>> to
>>>>>>>>   the Incident Object Description Exchange Format [RFC5070], 2)
>>>>>> forming
>>>>>>>>   part of an already existing IODEF-extension for structured
>>>>>>>>   cybersecurity information (currently draft
>>>>>>>>   draft-ietf-mile-sci-11.txt), or others.  While the format and
>>>>>>>>   contents of the present document fit more the earlier option,
>>> these
>>>>>>>>   can also be incorporated to the later.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Please note that it may take a couple of minutes from the time of
>>>>>>>> submission until the htmlized version and diff are available at
>>>>>> tools.ietf.org.
>>>>>>>> The IETF Secretariat
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=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
>>>>>> _______________________________________________
>>>>>> 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
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Thu May 22 13:34:46 2014
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79A511A032F for <mile@ietfa.amsl.com>; Thu, 22 May 2014 13:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level: 
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FwNa6qrYrQ69 for <mile@ietfa.amsl.com>; Thu, 22 May 2014 13:34:41 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C1621A026F for <mile@ietf.org>; Thu, 22 May 2014 13:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6830; q=dns/txt; s=iport; t=1400790880; x=1402000480; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=80JGkfupoarEvL/FjNEFB4C4P/FiqT+RgubRHMNTSp0=; b=hmFtVZtpz34jwdBWyDc0Xleg2u41PMMhkRuXGFWUgT/mEmYwHFIJCw3m zVJzFburQHK81YXWQRgZnCjcrGoXGUujpxUUkwOdK3fyK/ClzdwtFWcD9 DLeepfU8AuLErNWeV+f0eQizvVMi3fveeei2131ArD8AoNx6g16mVBH6i A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYNAMBeflOtJV2R/2dsb2JhbABZgwdSUQepZQEBAQEBAQUBkn+HPAGBDRZ0giUBAQEEAQEBNzQXBAIBCBEEAQELFAkHJwsUCQgCBAESCAGIOAgF1nkXhVWISDgGgyWBFQSFUpVckWmDOIIw
X-IronPort-AV: E=Sophos;i="4.98,889,1392163200"; d="scan'208";a="46355483"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-6.cisco.com with ESMTP; 22 May 2014 20:34:39 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id s4MKYdCW026984 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 22 May 2014 20:34:39 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.76]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Thu, 22 May 2014 15:34:39 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
Thread-Index: AQKEgaLJpHUnE7Tb4NKZp0r5Qh/vBQHu/wJcmdLxPxCAAIw+YA==
Date: Thu, 22 May 2014 20:34:38 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A750FC13AA2@xmb-rcd-x10.cisco.com>
References: <20140501201046.797.49114.idtracker@ietfa.amsl.com> <1C9F17D1873AFA47A969C4DD98F98A750FBDABEA@xmb-rcd-x10.cisco.com> <000001cf75ba$50e02f30$f2a08d90$@nict.go.jp>
In-Reply-To: <000001cf75ba$50e02f30$f2a08d90$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.150.28.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/BMtw7iSZoKxoiMaruDBwzolvglk
Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 22 May 2014 20:34:43 -0000

Thank you for the suggestion Take.=20

I rephrased it a little. It will be in the next iteration of the document a=
nd will read something like=20
------
	[...]
	The IODEF data model (RFC5070) is extensible. Many class=20
	attributes and their values can be extended using using the "ext-*" prefix=
.=20
	Additional classed can also be defined by using the AdditionalData and Rec=
ordItem=20
	classes. An extension to the AdditionalData class for reporting Phishing e=
mails=20
	is defined in RFC5901.

	Additionally, IODEF can import existing schemata by using an extension fra=
mework=20
	defined in RFC7203. The framework enables IODEF users to embed=20
	XML data inside an IODEF document using external schemata or structures de=
fined by external=20
	specifications. Examples include CVE, CVRF and OVAL. Thus, RFC7203=20
	enhances the IODEF capabilities without further extending the data model.

	IODEF implementers should consider using their own IODEF extensions only f=
or data=20
	that cannot be described using existing standards or importing them in and=
 IODEF=20
	document using RFC7203 is not a suitable option.
	[...]
------


Panos


-----Original Message-----
From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]=20
Sent: Thursday, May 22, 2014 8:35 AM
To: Panos Kampanakis (pkampana); mile@ietf.org
Subject: RE: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt

Hello Panos,

Thank you for updating the draft.
I am wondering if we could use the following texts as a starting point of t=
he section 4.3.

---------------------------------------
IODEF data model is designed to be extensible.
We can extend the enumerated values of the attributes by using the "ext-*"
fields, whereas we can extend the classes by using the AdditionalData and R=
ecordItem classes.
Please see RFC 5070 for details.
Some of these AdditionalData extensions were documented as standard specifi=
cations.
Please see RFC5901 for the phishing extension.

On the other hand, IODEF can borrow existing schemata by using an extension=
 framework defined in RFC 7203.
The framework enables us to embed xml documents and identifiers whose schem=
ata or structure are defined by external specifications inside IODEF docume=
nt.
In this way, the capability of IODEF data model is extended, but users do n=
ot have to extend IODEF itself. Users simply need to use schemata that were=
 defined outside IODEF data model.
Please see RFC 7203 for details.
---------------------------------------

This is just a basis for discussion and revision, but I hope the above unde=
rstanding is roughly aligned with you.

Take

> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Panos=20
> Kampanakis
> (pkampana)
> Sent: Friday, May 2, 2014 5:20 AM
> To: mile@ietf.org
> Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
>=20
> Hello,
>=20
> This is the -03 version of the IODEF guidance draft incorporating=20
> Roman's, Kathleen's, Trevor's and David's comments so far. The updated=20
> made from
> -02 version are
>    (1)  Added "Updates" section.
>    (2)  Added details about the flow of information exchanges in "Inter-
>         vendor and Service Provider Exercise" section.  Also updated the
>         usecases with more background information.
>    (3)  Added future use-cases in the "Collective Intelligence
>         Framework" section
>    (4)  Updated Perl and Python references with the actual module names.
>         Added IODEF implementation reference "implementations".
>    (5)  Added Predicate logic section
>    (6)  Updated Logic of watchlist of indicators section to simplify the
>         logic and include examples.
>    (7)  Renamed Externally defined indicators section to Indicator
>         reference and elaborated on the use of indicator-uid and
>         indicator-set-uid attribute use.
>=20
> It is still not complete and some sections need to be expanded. I will=20
> now work on -04 and hopefully will have a more complete version in a=20
> couple of months.
>=20
> Feedback and reviews are welcome.
>=20
> Regards,
> Panos
>=20
>=20
>=20
> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of=20
> internet-drafts@ietf.org
> Sent: Thursday, May 01, 2014 4:11 PM
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-03.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
>  This draft is a work item of the Managed Incident Lightweight=20
> Exchange Working Group of the IETF.
>=20
>         Title           : IODEF Usage Guidance
>         Author          : Panos Kampanakis
> 	Filename        : draft-ietf-mile-iodef-guidance-03.txt
> 	Pages           : 26
> 	Date            : 2014-05-01
>=20
> Abstract:
>    The Incident Object Description Exchange Format [RFC5070] defines a
>    data representation that provides a framework for sharing information
>    commonly exchanged by Computer Security Incident Response Teams
>    (CSIRTs) about computer security incidents.  Since the IODEF model
>    includes a wealth of available options that can be used to describe a
>    security incident or issue, it can be challenging for implementers to
>    develop tools that can Leverage IODEF for incident sharing.  This
>    document provides guidelines for IODEF implementers.  It will also
>    address how common security indicators can be represented in IODEF
>    and use-cases of how IODEF is being used so far.The goal of this
>    document is to make IODEF's adoption by vendors easier and encourage
>    faster and wider adoption of the model by Computer Security Incident
>    Response Teams (CSIRTs) around the world.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-03
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-iodef-guidance-03
>=20
>=20
> Please note that it may take a couple of minutes from the time of
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> 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 nobody Sun May 25 15:38:29 2014
Return-Path: <martinmurillo@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F98C1A0408 for <mile@ietfa.amsl.com>; Sun, 25 May 2014 15:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.001
X-Spam-Level: **
X-Spam-Status: No, score=2.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=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 SsKaaphxu6JX for <mile@ietfa.amsl.com>; Sun, 25 May 2014 15:38:23 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4977E1A0402 for <mile@ietf.org>; Sun, 25 May 2014 15:38:23 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id at1so7027605iec.15 for <mile@ietf.org>; Sun, 25 May 2014 15:38:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=t+DMYAuNmHkfcDf1oLrlT7W0D87Z2azY0sfLm32bPM4=; b=r2V12lqoO8ZpxOmaOnCHpzo+OuttF6nigGFsc3BuwHe9B5onMl9sC+U9Jez++UyDCB bs5JsDNYujseUifLBBCGSFoP8hUhF3RDAhgOhL6DqZf9kis3iSyJsoiT2izuqqY9Zi6y wvmkL/owibFlsptTD9QiuXD0Bq2cvGElYtw99Fclor1SU9UWGnpWm3W4IlulfGvSNEXj 5op9p+oX5kPFCyw3c8+RPbUwqUffsradpslEG631zWGdJw8IceuFxr4OtPM9X9IfbFId 5XRqgxmZkQpf+mPrKwgZ7rBQU0PgG097orQI93r97z0kReSj21rRP01OY8l85oMcjQsz Q9KA==
X-Received: by 10.50.20.97 with SMTP id m1mr21342223ige.28.1401057500401; Sun, 25 May 2014 15:38:20 -0700 (PDT)
Received: from [10.0.0.8] (c-98-228-124-121.hsd1.in.comcast.net. [98.228.124.121]) by mx.google.com with ESMTPSA id s1sm22558603igr.14.2014.05.25.15.38.18 for <mile@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 25 May 2014 15:38:19 -0700 (PDT)
Sender: "Martin J. Murillo" <martinmurillo@gmail.com>
Message-ID: <538270D9.1070501@ieee.org>
Date: Sun, 25 May 2014 18:38:17 -0400
From: "Martin J. Murillo" <murillo@ieee.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: mile@ietf.org
Content-Type: multipart/alternative; boundary="------------070406080007090105050602"
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/FxRTAu2siPS8zsAItLv-mw2Vr3A
Subject: Re: [mile] New Version Notification for draft-murillo-mile-cps-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: murillo@ieee.org
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, 25 May 2014 22:38:27 -0000

This is a multi-part message in MIME format.
--------------070406080007090105050602
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Eric, Takahashi, Kathleen,

Thanks for the ideas and opinions.  The points you raise are important 
and definitely we want to be comprehensive while at the same time not 
reinventing the wheel. I think this will become clear in the next 
revision that is incorporating all the feedbacks we have received. The 
path to either option should be a rearrangement of elements, among 
others.  I expect to get it ready in two weeks.

Thanks again for the feedback.

Martin



    ---------- Forwarded message ----------
    From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
    To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
    Cc: "<mile@ietf.org>" <mile@ietf.org>, Eric Burger
    <eburger@standardstrack.com>
    Date: Thu, 22 May 2014 09:52:56 -0400
    Subject: Re: [mile] New Version Notification for
    draft-murillo-mile-cps-00.txt
    +1

    Sent from my iPhone

     > On May 22, 2014, at 9:03 AM, "Takeshi Takahashi"
    <takeshi_takahashi@nict.go.jp <mailto:takeshi_takahashi@nict.go.jp>>
    wrote:
     >
     > Hi Eric and Martin,
     >
     > Thank you for your kind comment.
     > We will keep in mind that we should avoid having two things that
    do the same
     > thing.
     >
     > In my humble opinion, the CPS draft hands issues that are outside
    the scope
     > of the SCI draft.
     > I think the next version of the CPS draft will sort out lots of
    this type of
     > questions.
     >
     > Kind wishes,
     > Take
     >
     >
     >> -----Original Message-----
     >> From: mile [mailto:mile-bounces@ietf.org
    <mailto:mile-bounces@ietf.org>] On Behalf Of Eric Burger
     >> Sent: Thursday, May 22, 2014 4:56 AM
     >> To: mile@ietf.org <mailto:mile@ietf.org>
     >> Subject: Re: [mile] New Version Notification for
     >> draft-murillo-mile-cps-00.txt
     >>
     >> And I do not think the world is eager to have two things that do
    the same
     >> thing. We already have that problem in this space. I would suggest
     > adopting
     >> one and only one way of doing this. I have no opinion as to
    whether it
     > should
     >> be CPS or SCI.
     >>
     >> On May 9, 2014, at 7:17 AM, Takeshi Takahashi
     >> <takeshi_takahashi@nict.go.jp
    <mailto:takeshi_takahashi@nict.go.jp>> wrote:
     >>
     >>> Hi Martin,
     >>>
     >>> Thank you for your kind comments.
     >>>
     >>>> There's one question that still lingers: whether we should not
     >>>> re-utilize other extensions or use the IODEF-extension for
    structured
     >>>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
     >>>> points above would be applicable to both scenarios.
     >>>
     >>> I like this CPS draft, but I also like IODEF-SCI's framework
    (well, I
     >>> am one of the authors).
     >>> I do not want to be the obstacle of developing this interesting
    work,
     >>> so I do not have any intention to stick to IODEF-SCI at all.
     >>> But I would like to understand the pros and cons of not using SCI
     >>> framework for the CPS extension more vividly.
     >>>
     >>> Section 1.7 of the CPS draft explains the reason for not using the
     >>> IODEF-SCI's framework, but it was not so clear to me..
     >>> Can we discuss this issue when we have got example XML documents of
     >>> the CPS extension? (I guess later version of the CPS draft will
    have
     >>> the example XML
     >>> documents?) Then we can compare how the XML documents will look
    like
     >>> for each case of using and not using IODEF-SCI framework on the CPS
     >> extension.
     >>>
     >>> Kind regards,
     >>> Take
     >>>
     >>>
     >>>> -----Original Message-----
     >>>> From: Martin Murillo [mailto:murillo@ieee.org
    <mailto:murillo@ieee.org>]
     >>>> Sent: Wednesday, April 30, 2014 12:30 PM
     >>>> To: Takeshi Takahashi; mile@ietf.org <mailto:mile@ietf.org>
     >>>> Subject: Re: [mile] Fwd: New Version Notification for
     >>>> draft-murillo-mile-cps-00.txt
     >>>>
     >>>> Dear Takeshi,
     >>>>
     >>>> Thanks for the feedback and highlighting various extraneous
    elements
     >>>> which have rich IODEF equivalents. This makes the reporting
    lighter
     >>>> and decreases implementation overhead. I have answered to each
    item
     >> below.
     >>>>
     >>>> 1. The IncidentType element specifies whether the incident is
     >>>> accidental, on purpose, or theresult of other actions. The
    IncdntType
     >>>> attribute is missplaced. Thanks for taking notice of that.
    However I
     >>>> wonder whether the IncidentType element should be renamed. I
    think we
     >>>> agree that we need a field where whether the incident is
    accidental,
     >>>> on purpose, or undetermined can be placed. While the nature of the
     >>>> incident is rarely known immediately, there are instances in which
     >>>> the operator or other local party causes accidental instances;
    these
     >>>> instances might cause repercussions in other locations (i.e.
     >>>> balancing in
     >>> an electric grid).
     >>>>
     >>>> 2. I agree with you, the IncidentTilte element is a perfect
    candidate
     >>>> to go to a shallower level, especially when it will be the first
     >>>> variable that an operator or appropriate party reads.
     >>>>
     >>>> 3. Given that the IODEF:Contact class is rich enough to
    differentiate
     >>>> between a reporting party and an additional contact
     >>>> person/institution, I believe that we should use such class.
    Because
     >>>> the different stakeholders responsible for the Corporate Network,
     >>>> Control Servers, and Field Devices, this class might need to be
     >>>> extended. This is also relevant when the attack has taken place at
     >>>> any of those levels: For instance, the Corporate Network (or a
    false
     >>>> impersonator) might instruct the control room (Control
    servers) wrong
     >>>> setpoint configurations. Or the Control Network might experience a
     >>>> breach and setpoints altered in such servers. In extreme
    situations,
     >>>> the
     >>> attacks might be directly to the field devices. In each of
    those cases.
     >>>> In each of those cases the contact person might be one or more.
     >>>>
     >>>> 4, 5, 6. I think the IODEF classes can be indeed used. Thank
    you. The
     >>>> extension capabilities fo the System Class makes it quite
    appropriate
     >>>> to offer rich information.
     >>>>
     >>>> Regarding your last point, SFK should indeed be used instead
    of SFC.
     >>>>
     >>>> There's one question that still lingers: whether we should not
     >>>> re-utilize other extensions or use the IODEF-extension for
    structured
     >>>> cybersecurity (draft-ietf-mile-sci-11.txt). Ideas? I believe the
     >>>> points above would be applicable to both scenarios.
     >>>>
     >>>> Martin
     >>>>
     >>>>> On 4/23/2014 4:42 AM, Takeshi Takahashi wrote:
     >>>>> Hi Martin,
     >>>>>
     >>>>> I've read through the drafts. Thank you very much for sharing
    your
     >>>>> expertise here.
     >>>>> It was a new use case for me, and was really interesting.
     >>>>>
     >>>>> I am wondering if we can minimize the number of extension
    fields by
     >>>>> using the existing IODEF fields.
     >>>>> By minimizing the number of similar fields, I hope we can
    simplify
     >>>>> the draft and minimize the burden of implementations.
     >>>>>
     >>>>>> From this viewpoint, let me ask several checking questions.
     >>>>>
     >>>>> 1. IncidentType element and IncdntType Attribute
     >>>>>  What are the difference between them? I think your current draft
     >>>>> has them as place holders. I would like to hear a bit further.
     >>>>>
     >>>>> 2. The IncidentTitle element
     >>>>>  Can we use the Description element inside the IODEF:Incident
    class
     >>>>> for this purpose, instead of having new field here?
     >>>>>  It would be useful to have title or such information that
    can hint
     >>>>> the content of the IODEF document, but I feel like that it
    would be
     >>>>> helpful to have this type of information at the shallower
    level of
     >>>>> IODEF document rather than having it in the deeper level of IODEF
     >>>>> document (inside
     >>>>> additionalData)
     >>>>>
     >>>>> 3. The ReportingParty element
     >>>>>  Can we use the IODEF:contact class instead of having new field?
     >>>>> We could extend it further if needed.
     >>>>>
     >>>>> 4. The ReportReliability element
     >>>>>  Can we use the IODEF:confidence class instead of having new
    field?
     >>>>> We could extend it further if needed.
     >>>>>
     >>>>> 5. The TargetSystems element
     >>>>>  Can we extend the IODEF:system class instead of having new
    field?
     >>>>> We could extend it further if needed.
     >>>>>
     >>>>> 6. type attribute of the IODEF:Impact class
     >>>>>  When we use this extension, what value should be set for the
    type
     >>>>> attribute of the IODEF:Impact class?
     >>>>>
     >>>>> By the way, here are small questions.
     >>>>>
     >>>>> 1. should [SFC] be [SFK], since the acronym seems to come
    from the
     >>>>> initials of the authors of the reference (Stouffer, K.,
    Falco, J.,
     >>>>> and
     >>>> K. Scarfonw) ?
     >>>>>
     >>>>> I might have misunderstood your draft, so please correct me
    if I am
     >>> wrong.
     >>>>>
     >>>>> Kind regards,
     >>>>> Take
     >>>>>
     >>>>>
     >>>>>> -----Original Message-----
     >>>>>> From: mile [mailto:mile-bounces@ietf.org
    <mailto:mile-bounces@ietf.org>] On Behalf Of Martin
     >>>>>> Murillo
     >>>>>> Sent: Wednesday, January 29, 2014 10:11 AM
     >>>>>> To: Johnson, Blake; Jerome Athias
     >>>>>> Cc: mile@ietf.org <mailto:mile@ietf.org>
     >>>>>> Subject: Re: [mile] Fwd: New Version Notification for
     >>>>>> draft-murillo-mile-cps-00.txt
     >>>>>>
     >>>>>> Have read the links posted by Jerome and info on the Experience
     >>>>>> Sharing Tool (EST). It is my impression that a revision
    under the
     >>>>>> light of the EST would be very appropriate, and one of the first
     >>>>>> uses of the extension, given its report-based nature.  Look
    forward
     >>>>>> to seeing
     >>>>> the reviews in this light.
     >>>>>> As Jerome mentioned, focusing on referencing already existing
     >>>>>> taxonomies (and when necessary reusing them and referencing
    their
     >>>>>> xml implementations, if publicly available) would be the best
     >>>>>> approach; given the early stages in the field, I tend to
    think that
     >>>>>> atomic data will
     >>>>> need to be used.
     >>>>>> Regarding the term "Asset" vs "System", I believe system
    provides a
     >>>>>> more general connotation, while asset, seem to focus more on
     >>>>>> mainstream infrastructure; because the inclusion of IoT-related
     >>>>>> infrastructure (anywhere from centralized home control to
     >>>>>> self-driving cars), I wonder whether "Asset" is too an
    specific term.
     >>>>>>
     >>>>>> Martin
     >>>>>>
     >>>>>> Martin
     >>>>>>
     >>>>>>> On 1/24/2014 2:09 PM, Johnson, Blake wrote:
     >>>>>>> This is an interesting application of IODEF that I had not
     > considered.
     >>>>>> Most industry sharing that takes place in this space, from my
     >>>>>> perspective, is in the form of in person and telephone threat
     >>>>>> briefings. These are facilitated by the FBI, DHS, and the
    ISAC's.
     >>>>>>> At least a handful of the ISAC's have started sharing
    structured
     >>>>>>> threat
     >>>>>> indicator data, and the taxonomy for this extension could cover
     >>>>>> what the Electric Sector ISAC currently refers to as 'Experience
     >>> Sharing.'
     >>>>>> I can review this proposal as it relates to information
    captured by
     >>>>>> the ES-ISAC's Experience Sharing tool, using IEC/ANSI 62443
    (ISA99)
     >>>>>> as an informative reference.
     >>>>>>> Blake Johnson
     >>>>>>> Threat Intelligence Analyst
     >>>>>>> Alliant Energy | Infrastructure Secruity
     >>>>>>> Office: 608-458-6320 <tel:608-458-6320> | Cell:
    608-843-2790 <tel:608-843-2790>
     >>>>>>>
     >>>>>>>
     >>>>>>> -----Original Message-----
     >>>>>>> From: mile [mailto:mile-bounces@ietf.org
    <mailto:mile-bounces@ietf.org>] On Behalf Of Jerome
     >>>>>>> Athias
     >>>>>>> Sent: Friday, January 24, 2014 3:18 AM
     >>>>>>> To: murillo@ieee.org <mailto:murillo@ieee.org>
     >>>>>>> Cc: mile@ietf.org <mailto:mile@ietf.org>
     >>>>>>> Subject: Re: [mile] Fwd: New Version Notification for
     >>>>>>> draft-murillo-mile-cps-00.txt
     >>>>>>>
     >>>>>>> Hi,
     >>>>>>>
     >>>>>>> from what I know (which is limited), and as you mention,
    this ICS
     >>>>>>> area is often also called Critical Infrastructures (CIs),
    or SCADA
     >>>>>>>
     >>>>>>> for a little bit of background, we could explore the
    Cybersecurity
     >>>>>>> Framework Example references
     >>>>>>> http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx
    <http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx>
     >>
    http://www.ictqatar.qa/en/documents/download/National%20Industrial%20 <http://www.ictqatar.qa/en/documents/download/National%20Industrial%20>
     >>>>>> C
     >>>>>>> ontrol%20Systems%20Security%20Standard-English.pdf
     >>>>>>> ANSI/ISA-99.02.01-2009
     >>>>>>>
     >>>>>>> I don't have enough knowledge about the status and adoption
    of the
     >>>>>>> different efforts in term of XML
    representation/format/standards
     >>>>>>> http://xml.coverpages.org/emergencyManagement.html
    <http://xml.coverpages.org/emergencyManagement.html>
     >>>>>>> and resilience
     >>>>>>>
     >>>>>>> It would maybe be possible to obtain information from there
     >>>>>>> http://ics-cert.us-cert.gov http://ics-isac.org/
     >>>>>>>
     >>>>>>> My first feedback is that it looks like an interesting
    extension.
     >>>>>>>
     >>>>>>> I would suggest to focus on the reuse of existing
    Taxonomies, or
     >>>>>>> references to them.
     >>>>>>>
     >>>>>>> As such, for [Industry], maybe
     >>>>>>>
    http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012
    <http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012>
     >>>>>>> ISO 3166 (Country Codes)
     >>>>>>>
     >>>>>>>
     >>>>>>> [TargetSystems], I (personally) don't like the word
    "system" and
     >>>>>>> prefer
     >>>>>> "asset"
     >>>>>>> [CompromisedPhysicalInfrastrucute] (with a typo ;p) seems
    to be a
     >>>>>>> category of "Infrastructure" (or group of assets)
     >>>>>>>
     >>>>>>>
     >>>>>>> [EntryPoint] could be ok since it could be a little bit
    different
     >>>>>>> from "endpoint"
     >>>>>>>
     >>>>>>> [PerpetratingParty] seems to reference "Threat Actor" or
    "Threat
     >>>>>>> Agent" or "Attacker"
     >>>>>>>
     >>>>>>> [RecurrencePreventionMeasures] is this Security Controls? (and
     >>>>>>> Mitigations/Remediations)
     >>>>>>> Reference:
     >>>>
    https://web.nvd.nist.gov/view/800-53/control?controlName=AC-3&type=1
    <https://web.nvd.nist.gov/view/800-53/control?controlName=AC-3&type=1>
     >>>>>>>
     >>>>>>>
     >>>>>>> Describing an [Exploit] is not so easy (depending on the
    level of
     >>>>>>> details wanted/needed)
     >>>>>>>
     >>>>>>> Figure 1 (or "Diagram 1") is interesting, (of course it is
     >>>>>>> different from, i.e. CAESARS), it MAYBE could be more layered
     >>
    http://www.isa.org/InTechTemplate.cfm?template=/ContentManagement/Con <http://www.isa.org/InTechTemplate.cfm?template=/ContentManagement/Con>
     >>>>>> t
     >>>>>>> entDisplay.cfm&ContentID=94401
     >>>>>>>
     >>>>>>> (To follow: ENISA CDXI)
     >>>>>>>
     >>>>>>>
     >>>>>>> Some typos
     >>>>>>>
     >>>>>>>
     >>>>>>>
     >>>>>>> Next step: more XML focused ;)
     >>>>>>>
     >>>>>>>
     >>>>>>> My 2 bitcents
     >>>>>>>
     >>>>>>> 2014/1/24 Martin Murillo <murillo@ieee.org
    <mailto:murillo@ieee.org>>:
     >>>>>>>> Dear all,
     >>>>>>>>
     >>>>>>>> Please find below a link to a proposed draft for extending
    IODEF
     >>>>>>>> for the reporting of cyber-physical system incidents. These
     >>>>>>>> systems are often referred as  Operational Technology Systems,
     >>>>>>>> Industrial Control Systems, Automatic Control  Systems, or
    simply
     >>>>>>>> Control
     >>>> Systems.
     >>>>>>>>
     >>>>>>>> Cyber-Physical systems have been around for decades.  However,
     >>>>>>>> they are now at a higher risk to be  the target of attacks by
     >>>>>>>> individual highly-skilled attackers, organized groups,
     >>>>>>>> nation-states, or simply suffer repercussions of mainstream IT
     >>>>>>>> cyber-attacks. While over 90% of critical control system
     >>>>>>>> infrastructure is currently owned by private enterprises,
    these
     >>>>>>>> can have direct repercussions on national security of world
     >>>>>>>> nations.  Indeed, various of these systems are key parts of
     >>>>>>>> nuclear reactor facilities, transportation systems, electric
     >>>>>>>> power distribution, oil and natural gas distribution, health
     >>>>>>>> care, water
     >>>>>> and waste-water treatment, dam infrastructure, missile
     >>>>>>>> and defense systems, and others.   The disruption of these
    control
     >>>>>> systems
     >>>>>>>> could have a significant impact on public health, safety, and
     >>>>>>>> lead to large economic losses.
     >>>>>>>>
     >>>>>>>> Among the issues that catalyze this higher risk are:
     >>>>>>>>
     >>>>>>>> i) these systems are gradually becoming more
    interconnected, ii)
     >>>>>>>> legacy systems do not have proper cybersecurity
    protection, iii)
     >>>>>>>> the existence of highly-skilled individuals and
    motivations, iv)
     >>>>>>>> some these systems are generally considered critical, v) these
     >>>>>>>> are a natural extension of IT cyber-attacks, vi) the
    emergence of
     >>>>>>>> the Internet of Things (IOT), and vi) these attacks can be
     >>>>>>>> carried out
     >>>>>> remotely and quite inexpensively.
     >>>>>>>> While there might exist national approaches to deal with
     >>>>>>>> incidents, there's the need of a global international approach
     >>>>>>>> that will engulf governments, private organizations and other
     >>> stakeholders.
     >>>>>>>> IETF, as a leading global Internet standards organization,
    seeks
     >>>>>>>> to satisfy this need through open standards that seek to
     >>>>>>>> encompass issues that are critical for the global community.
     >>>>>>>>
     >>>>>>>> Feedback at two levels are welcome:
     >>>>>>>>
     >>>>>>>> 1. On the existence and inclusion either by utilizing any
    already
     >>>>> existing
     >>>>>>>> industry formats (XML- encoded) and/or by utilizing atomic
    data
     >>>>>>>> 2. Contributions on making the extension (and background
     >>>>>>>> information) more comprehensive, accurate and principally
    useful
     >>>>>>>> for the community
     >>>>>>>>
     >>>>>>>> Look forward to feedback and other input!
     >>>>>>>>
     >>>>>>>> Martin Murillo
     >>>>>>>>
     >>>>>>>> A new version of I-D, draft-murillo-mile-cps-00.txt has been
     >>>>>>>> successfully submitted by Martin Murillo and posted to the
    IETF
     >>>>>>>> repository.
     >>>>>>>>
     >>>>>>>> Name: draft-murillo-mile-cps
     >>>>>>>> Revision:       00
     >>>>>>>> Title:          IODEF extension for Reporting Cyber-Physical
     >> System
     >>>>>>>> Incidents
     >>>>>>>> Document date:  2014-01-21
     >>>>>>>> Group:          Individual Submission
     >>>>>>>> Pages:          24
     >>>>>>>> URL:
     >>
    http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt
    <http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt>
     >>>>>>>> Status:
     >>>>>> https://datatracker.ietf.org/doc/draft-murillo-mile-cps/
    <https://datatracker.ietf.org/doc/draft-murillo-mile-cps/>
     >>>>>>>> Htmlized:
     >>>> http://tools.ietf.org/html/draft-murillo-mile-cps-00
    <http://tools.ietf.org/html/draft-murillo-mile-cps-00>
     >>>>>>>>
     >>>>>>>>
     >>>>>>>> Abstract:
     >>>>>>>>   This draft document will extend the Incident Object
    Description
     >>>>>>>>   Exchange Format (IODEF) defined in [RFC5070] to support the
     >>>>>> reporting
     >>>>>>>>   of incidents dealing with attacks to physical infrastructure
     >>>>> through
     >>>>>>>>   the utilization of IT means as a vehicle or as a tool.
      These
     >>>>> systems
     >>>>>>>>   might also be referred as Cyber-Physical Systems (CPS),
     >>>> Operational
     >>>>>>>>   Technology Systems, Industrial Control Systems, Automatic
     >>>> Control
     >>>>>>>>   Systems, or simply Control Systems.  These names are used
     >>>>>>>>   interchangeably in this document.  In this context, an
     >>>>>>>> incident
     >>>> is
     >>>>>>>>   generally the result of a cybersecurity issue whose main
    goal
     >>>>>>>> is
     >>>>>> to
     >>>>>>>>   affect the operation of a CPS.  It is considered that any
     >>>>>>>>   unauthorized alteration of the operation is always
    malign.  This
     >>>>>>>>   extension will provide the capability of embedding
    structured
     >>>>>>>>   information, such as identifier- and XML-based information.
     >>>>>>>> In
     >>>> its
     >>>>>>>>   current state, this document provides important
    considerations
     >>>> for
     >>>>>>>>   further work in implementing Cyber-Physical System incident
     >>>>>> reports,
     >>>>>>>>   either by utilizing any already existing industry
    formats (XML-
     >>>>>>>>   encoded) and/or by utilizing atomic data.
     >>>>>>>>
     >>>>>>>>   In addition, this document should provide appropriate
    material
     >>>> for
     >>>>>>>>   helping making due considerations in making an appropriate
     >>>> decision
     >>>>>>>>   on how a CPS reporting is done: 1) through a data format
     >>>>>>>> extension
     >>>>>> to
     >>>>>>>>   the Incident Object Description Exchange Format
    [RFC5070], 2)
     >>>>>> forming
     >>>>>>>>   part of an already existing IODEF-extension for structured
     >>>>>>>>   cybersecurity information (currently draft
     >>>>>>>>   draft-ietf-mile-sci-11.txt), or others.  While the
    format and
     >>>>>>>>   contents of the present document fit more the earlier
    option,
     >>> these
     >>>>>>>>   can also be incorporated to the later.
     >>>>>>>>
     >>>>>>>>
     >>>>>>>>
     >>>>>>>> Please note that it may take a couple of minutes from the
    time of
     >>>>>>>> submission until the htmlized version and diff are
    available at
     >>>>>> tools.ietf.org <http://tools.ietf.org>.
     >>>>>>>> The IETF Secretariat
     >>>>>>>>
     >>>>>>>>
     >>>>>>>>
     >>>>>>>>
     >>>>>>>>
     >>>>>>>> _______________________________________________
     >>>>>>>> mile mailing list
     >>>>>>>> mile@ietf.org <mailto:mile@ietf.org>
     >>>>>>>> https://www.ietf.org/mailman/listinfo/mile
    <https://www.ietf.org/mailman/listinfo/mile>
     >>>>>>> _______________________________________________
     >>>>>>> mile mailing list
     >>>>>>> mile@ietf.org <mailto:mile@ietf.org>
     >>>>>>> https://www.ietf.org/mailman/listinfo/mile
    <https://www.ietf.org/mailman/listinfo/mile>
     >>>>>> _______________________________________________
     >>>>>> mile mailing list
     >>>>>> mile@ietf.org <mailto:mile@ietf.org>
     >>>>>> https://www.ietf.org/mailman/listinfo/mile
    <https://www.ietf.org/mailman/listinfo/mile>
     >>>
     >>> _______________________________________________
     >>> mile mailing list
     >>> mile@ietf.org <mailto:mile@ietf.org>
     >>> https://www.ietf.org/mailman/listinfo/mile
    <https://www.ietf.org/mailman/listinfo/mile>
     >
     >
     > _______________________________________________
     > mile mailing list
     > mile@ietf.org <mailto:mile@ietf.org>
     > https://www.ietf.org/mailman/listinfo/mile
    <https://www.ietf.org/mailman/listinfo/mile>



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


--------------070406080007090105050602
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Eric, Takahashi, Kathleen,<br>
    <br>
    Thanks for the ideas and opinions.  The points you raise are
    important and definitely we want to be comprehensive while at the
    same time not reinventing the wheel. I think this will become clear
    in the next revision that is incorporating all the feedbacks we have
    received. The path to either option should be a rearrangement of
    elements, among others.  I expect to get it ready in two weeks.<br>
    <br>
    Thanks again for the feedback.<br>
    <br>
    Martin<br>
    <br>
    <br>
    <div class="gmail_quote">
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
        ---------- Forwarded message ----------<br>
        From: Kathleen Moriarty <a class="moz-txt-link-rfc2396E" href="mailto:kathleen.moriarty.ietf@gmail.com">&lt;kathleen.moriarty.ietf@gmail.com&gt;</a><br>
        To: Takeshi Takahashi <a class="moz-txt-link-rfc2396E" href="mailto:takeshi_takahashi@nict.go.jp">&lt;takeshi_takahashi@nict.go.jp&gt;</a><br>
        Cc: "<a class="moz-txt-link-rfc2396E" href="mailto:mile@ietf.org">&lt;mile@ietf.org&gt;</a>" <a class="moz-txt-link-rfc2396E" href="mailto:mile@ietf.org">&lt;mile@ietf.org&gt;</a>, Eric Burger
        <a class="moz-txt-link-rfc2396E" href="mailto:eburger@standardstrack.com">&lt;eburger@standardstrack.com&gt;</a><br>
        Date: Thu, 22 May 2014 09:52:56 -0400<br>
        Subject: Re: [mile] New Version Notification for
        draft-murillo-mile-cps-00.txt<br>
        +1<br>
        <br>
        Sent from my iPhone<br>
        <br>
        &gt; On May 22, 2014, at 9:03 AM, "Takeshi Takahashi" &lt;<a
          href="mailto:takeshi_takahashi@nict.go.jp">takeshi_takahashi@nict.go.jp</a>&gt;
        wrote:<br>
        &gt;<br>
        &gt; Hi Eric and Martin,<br>
        &gt;<br>
        &gt; Thank you for your kind comment.<br>
        &gt; We will keep in mind that we should avoid having two things
        that do the same<br>
        &gt; thing.<br>
        &gt;<br>
        &gt; In my humble opinion, the CPS draft hands issues that are
        outside the scope<br>
        &gt; of the SCI draft.<br>
        &gt; I think the next version of the CPS draft will sort out
        lots of this type of<br>
        &gt; questions.<br>
        &gt;<br>
        &gt; Kind wishes,<br>
        &gt; Take<br>
        &gt;<br>
        &gt;<br>
        &gt;&gt; -----Original Message-----<br>
        &gt;&gt; From: mile [mailto:<a
          href="mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>]
        On Behalf Of Eric Burger<br>
        &gt;&gt; Sent: Thursday, May 22, 2014 4:56 AM<br>
        &gt;&gt; To: <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt; Subject: Re: [mile] New Version Notification for<br>
        &gt;&gt; draft-murillo-mile-cps-00.txt<br>
        &gt;&gt;<br>
        &gt;&gt; And I do not think the world is eager to have two
        things that do the same<br>
        &gt;&gt; thing. We already have that problem in this space. I
        would suggest<br>
        &gt; adopting<br>
        &gt;&gt; one and only one way of doing this. I have no opinion
        as to whether it<br>
        &gt; should<br>
        &gt;&gt; be CPS or SCI.<br>
        &gt;&gt;<br>
        &gt;&gt; On May 9, 2014, at 7:17 AM, Takeshi Takahashi<br>
        &gt;&gt; &lt;<a href="mailto:takeshi_takahashi@nict.go.jp">takeshi_takahashi@nict.go.jp</a>&gt;
        wrote:<br>
        &gt;&gt;<br>
        &gt;&gt;&gt; Hi Martin,<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt; Thank you for your kind comments.<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; There's one question that still lingers:
        whether we should not<br>
        &gt;&gt;&gt;&gt; re-utilize other extensions or use the
        IODEF-extension for structured<br>
        &gt;&gt;&gt;&gt; cybersecurity (draft-ietf-mile-sci-11.txt).
        Ideas? I believe the<br>
        &gt;&gt;&gt;&gt; points above would be applicable to both
        scenarios.<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt; I like this CPS draft, but I also like IODEF-SCI's
        framework (well, I<br>
        &gt;&gt;&gt; am one of the authors).<br>
        &gt;&gt;&gt; I do not want to be the obstacle of developing this
        interesting work,<br>
        &gt;&gt;&gt; so I do not have any intention to stick to
        IODEF-SCI at all.<br>
        &gt;&gt;&gt; But I would like to understand the pros and cons of
        not using SCI<br>
        &gt;&gt;&gt; framework for the CPS extension more vividly.<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt; Section 1.7 of the CPS draft explains the reason
        for not using the<br>
        &gt;&gt;&gt; IODEF-SCI's framework, but it was not so clear to
        me..<br>
        &gt;&gt;&gt; Can we discuss this issue when we have got example
        XML documents of<br>
        &gt;&gt;&gt; the CPS extension? (I guess later version of the
        CPS draft will have<br>
        &gt;&gt;&gt; the example XML<br>
        &gt;&gt;&gt; documents?) Then we can compare how the XML
        documents will look like<br>
        &gt;&gt;&gt; for each case of using and not using IODEF-SCI
        framework on the CPS<br>
        &gt;&gt; extension.<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt; Kind regards,<br>
        &gt;&gt;&gt; Take<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; -----Original Message-----<br>
        &gt;&gt;&gt;&gt; From: Martin Murillo [mailto:<a
          href="mailto:murillo@ieee.org">murillo@ieee.org</a>]<br>
        &gt;&gt;&gt;&gt; Sent: Wednesday, April 30, 2014 12:30 PM<br>
        &gt;&gt;&gt;&gt; To: Takeshi Takahashi; <a
          href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt; Subject: Re: [mile] Fwd: New Version
        Notification for<br>
        &gt;&gt;&gt;&gt; draft-murillo-mile-cps-00.txt<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; Dear Takeshi,<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; Thanks for the feedback and highlighting
        various extraneous elements<br>
        &gt;&gt;&gt;&gt; which have rich IODEF equivalents. This makes
        the reporting lighter<br>
        &gt;&gt;&gt;&gt; and decreases implementation overhead. I have
        answered to each item<br>
        &gt;&gt; below.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; 1. The IncidentType element specifies whether
        the incident is<br>
        &gt;&gt;&gt;&gt; accidental, on purpose, or theresult of other
        actions. The IncdntType<br>
        &gt;&gt;&gt;&gt; attribute is missplaced. Thanks for taking
        notice of that. However I<br>
        &gt;&gt;&gt;&gt; wonder whether the IncidentType element should
        be renamed. I think we<br>
        &gt;&gt;&gt;&gt; agree that we need a field where whether the
        incident is accidental,<br>
        &gt;&gt;&gt;&gt; on purpose, or undetermined can be placed.
        While the nature of the<br>
        &gt;&gt;&gt;&gt; incident is rarely known immediately, there are
        instances in which<br>
        &gt;&gt;&gt;&gt; the operator or other local party causes
        accidental instances; these<br>
        &gt;&gt;&gt;&gt; instances might cause repercussions in other
        locations (i.e.<br>
        &gt;&gt;&gt;&gt; balancing in<br>
        &gt;&gt;&gt; an electric grid).<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; 2. I agree with you, the IncidentTilte element
        is a perfect candidate<br>
        &gt;&gt;&gt;&gt; to go to a shallower level, especially when it
        will be the first<br>
        &gt;&gt;&gt;&gt; variable that an operator or appropriate party
        reads.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; 3. Given that the IODEF:Contact class is rich
        enough to differentiate<br>
        &gt;&gt;&gt;&gt; between a reporting party and an additional
        contact<br>
        &gt;&gt;&gt;&gt; person/institution, I believe that we should
        use such class. Because<br>
        &gt;&gt;&gt;&gt; the different stakeholders responsible for the
        Corporate Network,<br>
        &gt;&gt;&gt;&gt; Control Servers, and Field Devices, this class
        might need to be<br>
        &gt;&gt;&gt;&gt; extended. This is also relevant when the attack
        has taken place at<br>
        &gt;&gt;&gt;&gt; any of those levels: For instance, the
        Corporate Network (or a false<br>
        &gt;&gt;&gt;&gt; impersonator) might instruct the control room
        (Control servers) wrong<br>
        &gt;&gt;&gt;&gt; setpoint configurations. Or the Control Network
        might experience a<br>
        &gt;&gt;&gt;&gt; breach and setpoints altered in such servers.
        In extreme situations,<br>
        &gt;&gt;&gt;&gt; the<br>
        &gt;&gt;&gt; attacks might be directly to the field devices. In
        each of those cases.<br>
        &gt;&gt;&gt;&gt; In each of those cases the contact person might
        be one or more.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; 4, 5, 6. I think the IODEF classes can be
        indeed used. Thank you. The<br>
        &gt;&gt;&gt;&gt; extension capabilities fo the System Class
        makes it quite appropriate<br>
        &gt;&gt;&gt;&gt; to offer rich information.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; Regarding your last point, SFK should indeed be
        used instead of SFC.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; There's one question that still lingers:
        whether we should not<br>
        &gt;&gt;&gt;&gt; re-utilize other extensions or use the
        IODEF-extension for structured<br>
        &gt;&gt;&gt;&gt; cybersecurity (draft-ietf-mile-sci-11.txt).
        Ideas? I believe the<br>
        &gt;&gt;&gt;&gt; points above would be applicable to both
        scenarios.<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt; Martin<br>
        &gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; On 4/23/2014 4:42 AM, Takeshi Takahashi
        wrote:<br>
        &gt;&gt;&gt;&gt;&gt; Hi Martin,<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; I've read through the drafts. Thank you
        very much for sharing your<br>
        &gt;&gt;&gt;&gt;&gt; expertise here.<br>
        &gt;&gt;&gt;&gt;&gt; It was a new use case for me, and was
        really interesting.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; I am wondering if we can minimize the
        number of extension fields by<br>
        &gt;&gt;&gt;&gt;&gt; using the existing IODEF fields.<br>
        &gt;&gt;&gt;&gt;&gt; By minimizing the number of similar fields,
        I hope we can simplify<br>
        &gt;&gt;&gt;&gt;&gt; the draft and minimize the burden of
        implementations.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt; From this viewpoint, let me ask several
        checking questions.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 1. IncidentType element and IncdntType
        Attribute<br>
        &gt;&gt;&gt;&gt;&gt;  What are the difference between them? I
        think your current draft<br>
        &gt;&gt;&gt;&gt;&gt; has them as place holders. I would like to
        hear a bit further.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 2. The IncidentTitle element<br>
        &gt;&gt;&gt;&gt;&gt;  Can we use the Description element inside
        the IODEF:Incident class<br>
        &gt;&gt;&gt;&gt;&gt; for this purpose, instead of having new
        field here?<br>
        &gt;&gt;&gt;&gt;&gt;  It would be useful to have title or such
        information that can hint<br>
        &gt;&gt;&gt;&gt;&gt; the content of the IODEF document, but I
        feel like that it would be<br>
        &gt;&gt;&gt;&gt;&gt; helpful to have this type of information at
        the shallower level of<br>
        &gt;&gt;&gt;&gt;&gt; IODEF document rather than having it in the
        deeper level of IODEF<br>
        &gt;&gt;&gt;&gt;&gt; document (inside<br>
        &gt;&gt;&gt;&gt;&gt; additionalData)<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 3. The ReportingParty element<br>
        &gt;&gt;&gt;&gt;&gt;  Can we use the IODEF:contact class instead
        of having new field?<br>
        &gt;&gt;&gt;&gt;&gt; We could extend it further if needed.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 4. The ReportReliability element<br>
        &gt;&gt;&gt;&gt;&gt;  Can we use the IODEF:confidence class
        instead of having new field?<br>
        &gt;&gt;&gt;&gt;&gt; We could extend it further if needed.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 5. The TargetSystems element<br>
        &gt;&gt;&gt;&gt;&gt;  Can we extend the IODEF:system class
        instead of having new field?<br>
        &gt;&gt;&gt;&gt;&gt; We could extend it further if needed.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 6. type attribute of the IODEF:Impact class<br>
        &gt;&gt;&gt;&gt;&gt;  When we use this extension, what value
        should be set for the type<br>
        &gt;&gt;&gt;&gt;&gt; attribute of the IODEF:Impact class?<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; By the way, here are small questions.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; 1. should [SFC] be [SFK], since the acronym
        seems to come from the<br>
        &gt;&gt;&gt;&gt;&gt; initials of the authors of the reference
        (Stouffer, K., Falco, J.,<br>
        &gt;&gt;&gt;&gt;&gt; and<br>
        &gt;&gt;&gt;&gt; K. Scarfonw) ?<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; I might have misunderstood your draft, so
        please correct me if I am<br>
        &gt;&gt;&gt; wrong.<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt; Kind regards,<br>
        &gt;&gt;&gt;&gt;&gt; Take<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
        &gt;&gt;&gt;&gt;&gt;&gt; From: mile [mailto:<a
          href="mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>]
        On Behalf Of Martin<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Murillo<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Sent: Wednesday, January 29, 2014 10:11
        AM<br>
        &gt;&gt;&gt;&gt;&gt;&gt; To: Johnson, Blake; Jerome Athias<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [mile] Fwd: New Version
        Notification for<br>
        &gt;&gt;&gt;&gt;&gt;&gt; draft-murillo-mile-cps-00.txt<br>
        &gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Have read the links posted by Jerome
        and info on the Experience<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Sharing Tool (EST). It is my impression
        that a revision under the<br>
        &gt;&gt;&gt;&gt;&gt;&gt; light of the EST would be very
        appropriate, and one of the first<br>
        &gt;&gt;&gt;&gt;&gt;&gt; uses of the extension, given its
        report-based nature.  Look forward<br>
        &gt;&gt;&gt;&gt;&gt;&gt; to seeing<br>
        &gt;&gt;&gt;&gt;&gt; the reviews in this light.<br>
        &gt;&gt;&gt;&gt;&gt;&gt; As Jerome mentioned, focusing on
        referencing already existing<br>
        &gt;&gt;&gt;&gt;&gt;&gt; taxonomies (and when necessary reusing
        them and referencing their<br>
        &gt;&gt;&gt;&gt;&gt;&gt; xml implementations, if publicly
        available) would be the best<br>
        &gt;&gt;&gt;&gt;&gt;&gt; approach; given the early stages in the
        field, I tend to think that<br>
        &gt;&gt;&gt;&gt;&gt;&gt; atomic data will<br>
        &gt;&gt;&gt;&gt;&gt; need to be used.<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Regarding the term "Asset" vs "System",
        I believe system provides a<br>
        &gt;&gt;&gt;&gt;&gt;&gt; more general connotation, while asset,
        seem to focus more on<br>
        &gt;&gt;&gt;&gt;&gt;&gt; mainstream infrastructure; because the
        inclusion of IoT-related<br>
        &gt;&gt;&gt;&gt;&gt;&gt; infrastructure (anywhere from
        centralized home control to<br>
        &gt;&gt;&gt;&gt;&gt;&gt; self-driving cars), I wonder whether
        "Asset" is too an specific term.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Martin<br>
        &gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Martin<br>
        &gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; On 1/24/2014 2:09 PM, Johnson,
        Blake wrote:<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; This is an interesting application
        of IODEF that I had not<br>
        &gt; considered.<br>
        &gt;&gt;&gt;&gt;&gt;&gt; Most industry sharing that takes place
        in this space, from my<br>
        &gt;&gt;&gt;&gt;&gt;&gt; perspective, is in the form of in
        person and telephone threat<br>
        &gt;&gt;&gt;&gt;&gt;&gt; briefings. These are facilitated by the
        FBI, DHS, and the ISAC's.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; At least a handful of the ISAC's
        have started sharing structured<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; threat<br>
        &gt;&gt;&gt;&gt;&gt;&gt; indicator data, and the taxonomy for
        this extension could cover<br>
        &gt;&gt;&gt;&gt;&gt;&gt; what the Electric Sector ISAC currently
        refers to as 'Experience<br>
        &gt;&gt;&gt; Sharing.'<br>
        &gt;&gt;&gt;&gt;&gt;&gt; I can review this proposal as it
        relates to information captured by<br>
        &gt;&gt;&gt;&gt;&gt;&gt; the ES-ISAC's Experience Sharing tool,
        using IEC/ANSI 62443 (ISA99)<br>
        &gt;&gt;&gt;&gt;&gt;&gt; as an informative reference.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Blake Johnson<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Threat Intelligence Analyst<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Alliant Energy | Infrastructure
        Secruity<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Office: <a href="tel:608-458-6320"
          value="+16084586320">608-458-6320</a> | Cell: <a
          href="tel:608-843-2790" value="+16088432790">608-843-2790</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; From: mile [mailto:<a
          href="mailto:mile-bounces@ietf.org">mile-bounces@ietf.org</a>]
        On Behalf Of Jerome<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Athias<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Friday, January 24, 2014 3:18
        AM<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; To: <a
          href="mailto:murillo@ieee.org">murillo@ieee.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [mile] Fwd: New
        Version Notification for<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-murillo-mile-cps-00.txt<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; from what I know (which is
        limited), and as you mention, this ICS<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; area is often also called Critical
        Infrastructures (CIs), or SCADA<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; for a little bit of background, we
        could explore the Cybersecurity<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Framework Example references<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="http://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx"
          target="_blank">http://www.nerc.com/pa/Stand/<wbr>Pages/CIPStandards.aspx</a><br>
        &gt;&gt; <a
href="http://www.ictqatar.qa/en/documents/download/National%20Industrial%20"
          target="_blank">http://www.ictqatar.qa/en/<wbr>documents/download/National%<wbr>20Industrial%20</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt; C<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; ontrol%20Systems%20Security%<wbr>20Standard-English.pdf<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; ANSI/ISA-99.02.01-2009<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; I don't have enough knowledge about
        the status and adoption of the<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; different efforts in term of XML
        representation/format/<wbr>standards<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="http://xml.coverpages.org/emergencyManagement.html"
          target="_blank">http://xml.coverpages.org/<wbr>emergencyManagement.html</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; and resilience<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; It would maybe be possible to
        obtain information from there<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="http://ics-cert.us-cert.gov" target="_blank">http://ics-cert.us-cert.gov</a>
        <a href="http://ics-isac.org/" target="_blank">http://ics-isac.org/</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; My first feedback is that it looks
        like an interesting extension.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; I would suggest to focus on the
        reuse of existing Taxonomies, or<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; references to them.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; As such, for [Industry], maybe<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012"
          target="_blank">http://www.census.gov/cgi-bin/<wbr>sssd/naics/naicsrch?chart=2012</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; ISO 3166 (Country Codes)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; [TargetSystems], I (personally)
        don't like the word "system" and<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; prefer<br>
        &gt;&gt;&gt;&gt;&gt;&gt; "asset"<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; [<wbr>CompromisedPhysicalInfrastrucu<wbr>te]
        (with a typo ;p) seems to be a<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; category of "Infrastructure" (or
        group of assets)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; [EntryPoint] could be ok since it
        could be a little bit different<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; from "endpoint"<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; [PerpetratingParty] seems to
        reference "Threat Actor" or "Threat<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Agent" or "Attacker"<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; [RecurrencePreventionMeasures] is
        this Security Controls? (and<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Mitigations/Remediations)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Reference:<br>
        &gt;&gt;&gt;&gt; <a
href="https://web.nvd.nist.gov/view/800-53/control?controlName=AC-3&amp;type=1"
          target="_blank">https://web.nvd.nist.gov/view/<wbr>800-53/control?controlName=AC-<wbr>3&amp;type=1</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Describing an [Exploit] is not so
        easy (depending on the level of<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; details wanted/needed)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Figure 1 (or "Diagram 1") is
        interesting, (of course it is<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; different from, i.e. CAESARS), it
        MAYBE could be more layered<br>
        &gt;&gt; <a
href="http://www.isa.org/InTechTemplate.cfm?template=/ContentManagement/Con"
          target="_blank">http://www.isa.org/<wbr>InTechTemplate.cfm?template=/<wbr>ContentManagement/Con</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt; t<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; entDisplay.cfm&amp;ContentID=94401<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; (To follow: ENISA CDXI)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Some typos<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; Next step: more XML focused ;)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; My 2 bitcents<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; 2014/1/24 Martin Murillo &lt;<a
          href="mailto:murillo@ieee.org">murillo@ieee.org</a>&gt;:<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Dear all,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please find below a link to a
        proposed draft for extending IODEF<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; for the reporting of
        cyber-physical system incidents. These<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; systems are often referred as
         Operational Technology Systems,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Industrial Control Systems,
        Automatic Control  Systems, or simply<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Control<br>
        &gt;&gt;&gt;&gt; Systems.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cyber-Physical systems have
        been around for decades.  However,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; they are now at a higher risk
        to be  the target of attacks by<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; individual highly-skilled
        attackers, organized groups,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; nation-states, or simply suffer
        repercussions of mainstream IT<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; cyber-attacks. While over 90%
        of critical control system<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; infrastructure is currently
        owned by private enterprises, these<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; can have direct repercussions
        on national security of world<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; nations.  Indeed, various of
        these systems are key parts of<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; nuclear reactor facilities,
        transportation systems, electric<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; power distribution, oil and
        natural gas distribution, health<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; care, water<br>
        &gt;&gt;&gt;&gt;&gt;&gt; and waste-water treatment, dam
        infrastructure, missile<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; and defense systems, and
        others.   The disruption of these control<br>
        &gt;&gt;&gt;&gt;&gt;&gt; systems<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; could have a significant impact
        on public health, safety, and<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; lead to large economic losses.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Among the issues that catalyze
        this higher risk are:<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; i) these systems are gradually
        becoming more interconnected, ii)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; legacy systems do not have
        proper cybersecurity protection, iii)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; the existence of highly-skilled
        individuals and motivations, iv)<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; some these systems are
        generally considered critical, v) these<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; are a natural extension of IT
        cyber-attacks, vi) the emergence of<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; the Internet of Things (IOT),
        and vi) these attacks can be<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; carried out<br>
        &gt;&gt;&gt;&gt;&gt;&gt; remotely and quite inexpensively.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; While there might exist
        national approaches to deal with<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; incidents, there's the need of
        a global international approach<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; that will engulf governments,
        private organizations and other<br>
        &gt;&gt;&gt; stakeholders.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IETF, as a leading global
        Internet standards organization, seeks<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; to satisfy this need through
        open standards that seek to<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encompass issues that are
        critical for the global community.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Feedback at two levels are
        welcome:<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. On the existence and
        inclusion either by utilizing any already<br>
        &gt;&gt;&gt;&gt;&gt; existing<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; industry formats (XML-  
        encoded) and/or by utilizing atomic data<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. Contributions on making the
        extension (and background<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; information) more
        comprehensive, accurate and principally useful<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; for the community<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Look forward to feedback and
        other input!<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Martin Murillo<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A new version of I-D,
        draft-murillo-mile-cps-00.txt has been<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; successfully submitted by
        Martin Murillo and posted to the IETF<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; repository.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Name:          
        draft-murillo-mile-cps<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Revision:       00<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Title:          IODEF extension
        for Reporting Cyber-Physical<br>
        &gt;&gt; System<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Incidents<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Document date:  2014-01-21<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Group:          Individual
        Submission<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Pages:          24<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; URL:<br>
        &gt;&gt; <a
          href="http://www.ietf.org/internet-drafts/draft-murillo-mile-cps-00.txt"
          target="_blank">http://www.ietf.org/internet-<wbr>drafts/draft-murillo-mile-cps-<wbr>00.txt</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Status:<br>
        &gt;&gt;&gt;&gt;&gt;&gt; <a
          href="https://datatracker.ietf.org/doc/draft-murillo-mile-cps/"
          target="_blank">https://datatracker.ietf.org/<wbr>doc/draft-murillo-mile-cps/</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Htmlized:<br>
        &gt;&gt;&gt;&gt; <a
          href="http://tools.ietf.org/html/draft-murillo-mile-cps-00"
          target="_blank">http://tools.ietf.org/html/<wbr>draft-murillo-mile-cps-00</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Abstract:<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   This draft document will
        extend the Incident Object Description<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   Exchange Format (IODEF)
        defined in [RFC5070] to support the<br>
        &gt;&gt;&gt;&gt;&gt;&gt; reporting<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   of incidents dealing with
        attacks to physical infrastructure<br>
        &gt;&gt;&gt;&gt;&gt; through<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   the utilization of IT means
        as a vehicle or as a tool.  These<br>
        &gt;&gt;&gt;&gt;&gt; systems<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   might also be referred as
        Cyber-Physical Systems (CPS),<br>
        &gt;&gt;&gt;&gt; Operational<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   Technology Systems,
        Industrial Control Systems, Automatic<br>
        &gt;&gt;&gt;&gt; Control<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   Systems, or simply Control
        Systems.  These names are used<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   interchangeably in this
        document.  In this context, an<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; incident<br>
        &gt;&gt;&gt;&gt; is<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   generally the result of a
        cybersecurity issue whose main goal<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; is<br>
        &gt;&gt;&gt;&gt;&gt;&gt; to<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   affect the operation of a
        CPS.  It is considered that any<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   unauthorized alteration of
        the operation is always malign.  This<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   extension will provide the
        capability of embedding structured<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   information, such as
        identifier- and XML-based information.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; In<br>
        &gt;&gt;&gt;&gt; its<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   current state, this document
        provides important considerations<br>
        &gt;&gt;&gt;&gt; for<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   further work in implementing
        Cyber-Physical System incident<br>
        &gt;&gt;&gt;&gt;&gt;&gt; reports,<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   either by utilizing any
        already existing industry formats (XML-<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   encoded) and/or by utilizing
        atomic data.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   In addition, this document
        should provide appropriate material<br>
        &gt;&gt;&gt;&gt; for<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   helping making due
        considerations in making an appropriate<br>
        &gt;&gt;&gt;&gt; decision<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   on how a CPS reporting is
        done: 1) through a data format<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; extension<br>
        &gt;&gt;&gt;&gt;&gt;&gt; to<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   the Incident Object
        Description Exchange Format [RFC5070], 2)<br>
        &gt;&gt;&gt;&gt;&gt;&gt; forming<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   part of an already existing
        IODEF-extension for structured<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   cybersecurity information
        (currently draft<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   draft-ietf-mile-sci-11.txt),
        or others.  While the format and<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   contents of the present
        document fit more the earlier option,<br>
        &gt;&gt;&gt; these<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;   can also be incorporated to
        the later.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please note that it may take a
        couple of minutes from the time of<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; submission until the htmlized
        version and diff are available at<br>
        &gt;&gt;&gt;&gt;&gt;&gt; <a href="http://tools.ietf.org"
          target="_blank">tools.ietf.org</a>.<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IETF Secretariat<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; mile mailing list<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; mile mailing list<br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt;&gt; <a
          href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt; ______________________________<wbr>_________________<br>
        &gt;&gt;&gt;&gt;&gt;&gt; mile mailing list<br>
        &gt;&gt;&gt;&gt;&gt;&gt; <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt;&gt;&gt;&gt; <a
          href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        &gt;&gt;&gt;<br>
        &gt;&gt;&gt; ______________________________<wbr>_________________<br>
        &gt;&gt;&gt; mile mailing list<br>
        &gt;&gt;&gt; <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt;&gt;&gt; <a
          href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        &gt;<br>
        &gt;<br>
        &gt; ______________________________<wbr>_________________<br>
        &gt; mile mailing list<br>
        &gt; <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        &gt; <a href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        <br>
        <br>
        <br>
        ______________________________<wbr>_________________<br>
        mile mailing list<br>
        <a href="mailto:mile@ietf.org">mile@ietf.org</a><br>
        <a href="https://www.ietf.org/mailman/listinfo/mile"
          target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
        <br>
      </blockquote>
    </div>
  </body>
</html>

--------------070406080007090105050602--


From nobody Tue May 27 08:28:35 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 530601A0137; Tue, 27 May 2014 08:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 Rex_dVUlf8zO; Tue, 27 May 2014 08:28:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 165641A013B; Tue, 27 May 2014 08:28:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140527152833.20248.81666.idtracker@ietfa.amsl.com>
Date: Tue, 27 May 2014 08:28:33 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/1S5NQY9KPZ7rdbIUHYV133EYvSY
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-enum-reference-format-05.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 27 May 2014 15:28:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Managed Incident Lightweight Exchange Working Group of the IETF.

        Title           : IODEF Enumeration Reference Format
        Authors         : Adam W. Montville
                          David Black
	Filename        : draft-ietf-mile-enum-reference-format-05.txt
	Pages           : 9
	Date            : 2014-05-27

Abstract:
   The Incident Object Description Exchange Format (IODEF) provides a
   Reference class used to reference external entities (such as
   enumeration identifiers).  However, the method of external entity
   identification has been left unstructured.  This document describes a
   method to provide structure for referencing external entities for the
   IODEF Reference class and thus updates IODEF's ReferenceName.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mile-enum-reference-format-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed May 28 03:10:36 2014
Return-Path: <eburger@standardstrack.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A9F1A08B2 for <mile@ietfa.amsl.com>; Wed, 28 May 2014 03:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.122
X-Spam-Level: 
X-Spam-Status: No, score=-1.122 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779] autolearn=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 iAwqdv6JgYd3 for <mile@ietfa.amsl.com>; Wed, 28 May 2014 03:10:32 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [23.235.208.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 841741A08A9 for <mile@ietf.org>; Wed, 28 May 2014 03:10:32 -0700 (PDT)
Received: from ip68-100-74-215.dc.dc.cox.net ([68.100.74.215]:51197 helo=[192.168.15.103]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <eburger@standardstrack.com>) id 1WpaoJ-0007qz-Jz; Wed, 28 May 2014 03:10:25 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_AA4E87C7-3A5F-4DAB-9E92-0B80F19F1206"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com>
Date: Wed, 28 May 2014 06:10:07 -0400
Message-Id: <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com> <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp> <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
X-Mailer: Apple Mail (2.1878.2)
X-OutGoing-Spam-Status: No, score=-2.9
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-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/39TlVe894dlXWr1yyPBXrYHz9vo
Cc: "<mile@ietf.org>" <mile@ietf.org>
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 28 May 2014 10:10:34 -0000

--Apple-Mail=_AA4E87C7-3A5F-4DAB-9E92-0B80F19F1206
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

All it would do it introduce an opportunity to get it wrong. What do you =
do if the <Abbreviation/> does not match the <Index/>? If the answer is =
=93ignore it,=94 it means <Abbreviation/> has no protocol value. If the =
answer is =93fail the message with an error,=94 many implementors are =
likely to ignore it and some implementors will fail and interoperability =
will suffer.

Drop <Abbreviation/>.

On May 22, 2014, at 9:22 AM, Adam W. Montville <adam@stoicsecurity.com> =
wrote:

>=20
>=20
>> On May 22, 2014, at 4:44 AM, "Takeshi Takahashi" =
<takeshi_takahashi@nict.go.jp> wrote:
>>=20
>> Hi Adam,
>>=20
>> I remember that we had discussion on the Index field last year.
>> We have a field for the Index and not for version number.
>> That is because "the Index field in the XML unambiguously indicates =
which
>> IANA registry entry is to be used to correctly reference the =
enumeration
>> specification, which avoids interpretation of version strings that =
may have
>> specification-specific formats" (copied from the draft).
>> Yes, this was what I understood in the discussion last year.
>>=20
>> Now I am reading the document again, and have stuck on one question.
>> Maybe I have some misunderstanding or have forgotten some discussion, =
but I
>> would appreciate if you could clarify the issue below.
>>=20
>> If we have Index field, do we need the Abbreviation field?
>>=20
>> Below is the example described in the draft.
>> <EnumRef>
>> <Abbreviation>CXI</Abbreviation>
>> <Index>1</Index>
>> <ID>CXI-1234-XYZ</ID>
>> </EnumRef>
>>=20
>> But can we simply write like this?
>> <EnumRef>
>> <Index>1</Index>
>> <ID>CXI-1234-XYZ</ID>
>> </EnumRef>
>>=20
>> If we have the Index value, we can uniquely identify the =
specification and
>> version, correct?
>=20
> I believe you are correct, and I can't think of a reason to keep the =
abbreviation field.
>=20
>=20
>>=20
>> Take
>>=20
>>=20
>>> -----Original Message-----
>>> From: Adam Montville [mailto:adam@stoicsecurity.com]
>>> Sent: Monday, May 19, 2014 10:59 PM
>>> To: Black, David
>>> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
>>> Subject: Re: Reference and related nits in
>>> draft-ietf-mile-enum-reference-format
>>>=20
>>> David, thank you.  I've noted all of these and will make appropriate
>>> updates.
>>>=20
>>> Are there other comments other than those posed by Alexey and David?
>>>=20
>>>> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> =
wrote:
>>>>=20
>>>> Hi Adam,
>>>>=20
>>>>> With respect to your first sentence above, I assert that the =
document
>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>> to the abstract making the statement.
>>>>> Thoughts here?
>>>>=20
>>>> In this case, it is necessary to state the obvious for the sake of
>>>> clarity - I've been there and had to do that ;-).  In addition to a
>>>> sentence in the abstract, the header on the title page needs an
>> "Updates:
>>> 5070 (if approved)"
>>>> line, and a section should be added entitled "Summary of Changes to =
RFC
>>> 5070"
>>>> that identifies the changes.
>>>>=20
>>>> For a somewhat longer recent example, see RFC 7146:
>>>>   http://datatracker.ietf.org/doc/rfc7146/
>>>>=20
>>>> ----------------
>>>>=20
>>>> Here are some additional editorial nits that need attention ...
>>>>=20
>>>> a) I recently had another draft dinged by the IESG for using a
>>>> citation as a word in a sentence e.g., "[IODEF]" in the first =
sentence
>>> in Section 2:
>>>>=20
>>>> The need is to place enumeration identifiers and their references =
in
>>>> [IODEF]'s Reference class.
>>>>=20
>>>> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
>>>> [IODEF]" - I suggest just doing this and not asking why :-). The =
whole
>>>> draft should be checked for other uses of citations in this =
fashion.
>>>>=20
>>>> b) In addition, references should not be cited in the abstract, so =
I
>>>> believe the appropriate changes to the two citations in the =
abstract
>> are:
>>>>=20
>>>> The Incident Object Description Exchange Format [IODEF] provides a
>>>>=20
>>>>       "[IODEF]" -> "(IODEF)"
>>>>=20
>>>> Reference class used to reference external entities (such as
>>>> enumeration identifiers).  However, the method of external entity
>>>> identification has been left unstructured.  This document describes
>>> a
>>>> method to provide structure for referencing external entities for =
the
>>>> [IODEF] Reference class.
>>>>=20
>>>>       "[IODEF]" -> "IODEF"
>>>>=20
>>>> Otherwise, the draft still looks good.
>>>>=20
>>>> Thanks,
>>>> --David
>>>>=20
>>>>> -----Original Message-----
>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam =
Montville
>>>>> Sent: Sunday, May 18, 2014 7:58 PM
>>>>> To: Alexey Melnikov
>>>>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>>> Subject: Re: [mile] Working Group Last Call for =
draft-ietf-mile-enum-
>>>>> reference-format
>>>>>=20
>>>>>=20
>>>>> On May 11, 2014, at 2:54 PM, Alexey Melnikov
>>>>> <alexey.melnikov@isode.com>
>>>>> wrote:
>>>>>=20
>>>>>>=20
>>>>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
>>>>>>> <takeshi_takahashi@nict.go.jp>
>>>>> wrote:
>>>>>>>=20
>>>>>>> Greetings, all,
>>>>>>>=20
>>>>>>> This is the Working Group Last Call for
>>>>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration =
Reference
>>> Format.
>>>>>>>=20
>>>>>>> The last call starts now, and ends Monday 26 May 2014.
>>>>>>>=20
>>>>>>> Please read the latest revision of the draft,
>>> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
>>>>>>> , and send your comments to the mailing list; we'd also =
appreciate
>>>>>>> a comment if you're fine with the draft as is.
>>>>>>=20
>>>>>> Hi,
>>>>>> Below is my review of the draft:
>>>>>>=20
>>>>>> General comment: Is this intended as Proposed Standard? The draft
>>>>>> header
>>>>> doesn't say the document type.
>>>>>=20
>>>>> I'll update this, thank you.
>>>>>=20
>>>>>>=20
>>>>>> The document seems to update ReferenceName syntax to allow for
>>>>>> nested XML
>>>>> elements. However the document doesn't say that.
>>>>>> In relationship to this: would this document cause any
>>>>>> interoperability
>>>>> issues with programs that can only parse the old schema?
>>>>>=20
>>>>> I am unsure about interoperability issues, but they should be =
minimal
>>>>> and are likely implementation specific.
>>>>>=20
>>>>> I tried an experiment where I generated some code (JAXB) for IODEF
>>>>> 1.0 and then fed it a modified recon example (Section 7.2 from RFC
>>>>> 5070).  The <ReferenceName> element contained an <EnumRef> element =
as
>>>>> opposed to the string "nmap".  Unmarshalling seemed to work =
without
>>>>> issue, but when examining the ReferenceName element , the only =
thing
>>> present was a newline character.
>>>>> In an example that doesn't use generated code but instead uses a =
SAX
>>>>> or DOM parser, we can grab the inner XML.  Using a validating
>>>>> DOM/SAX/other parser will, of course, break if the enumeration
>>>>> reference XML is embedded, so parsers will need to be updated.
>>>>>=20
>>>>> I'm not a professional implementor, so it would be good to hear
>>>>> considerations from others.  Then, should these considerations be
>>>>> placed in the document (I assume that was the good point of =
raising the
>>> issue)?
>>>>>=20
>>>>> With respect to your first sentence above, I assert that the =
document
>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>> to the abstract making the statement.
>>>>> Thoughts here?
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> 4  IANA Considerations
>>>>>>=20
>>>>>>   Note that certain name requests should not be permitted as =
either
>>>>>>   Full Name or Abbreviation entries for the requested IANA table.
>>>>>>=20
>>>>>> Do you mean restrictions imposed by the syntax described below or
>>>>>> something
>>>>> else? If you intended to exclude some specific keywords, where is =
the
>>>>> list of them defined? Either way, I think you need to clarify. If =
you
>>>>> just meant the ABNF restrictions, I suggest adding something like
>>>>> "The restrictions are specified in the ABNF below".
>>>>>>=20
>>>>>>   Allocation Policy: Expert Review [RFC5226] and Specification
>>>>>>   Required [RFC5226]
>>>>>>=20
>>>>>> Nit: I think it would be better to say "Specification Required
>>>>>> (which
>>>>> implies Expert Review)".
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> mile mailing list
>>>>>> mile@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mile
>>=20
>>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


--Apple-Mail=_AA4E87C7-3A5F-4DAB-9E92-0B80F19F1206
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJThbYBAAoJEDY/T2tCIPW3gvEP/2m8JZdOGaWlf4k4XrCPaTvY
cFy0ZMuwzspyQ6tCuJugGm3SToJ6pTFv3EKRFEYL4cX+doknrdW15BLCUFRlEZFE
GIlaVxt4akCGjhonh7rvhYTw99VfpVAvhfrKoNbACYMHvNUoLa5gtkK4U5V3TfDf
ZzG/2g2dVw/YvVc3skeMmjD6BLrjF4NJSwCmqvOknKmh8zr1ztJH3turWTnDPLRD
XqEmBG3bYPyE0Zj9plMvmSFrdC++ANFZmyN8wdK3SGCyvG3ir2AlHlO0/jUOSK2n
uhEesyNr3DsNggWjo8qBOT/3dNviO0GOtsVXnUNH2HZVbJuYsiVe8r2w4TmEGinJ
qk1RJR+JEdWK3f/TKtjUiJrI5sH+GV3qGzOBqqBbNI0xsDlV0/qqLA9GbOfIa5qH
sVXdhyGWvWEQ8bfksey/vypYEjz6A9anamH9Ge/O6NQVwDNlZv8mELXzJvyXyZaQ
wGoLZObOn464NYsnehlBt86/FVpKmXEdz8VufqzcsooG5/HYLxYpdHdnEKrMMtUp
JyZKDVBINyWZHpLBUAQ5rJzDRaI31q6oDoSUQQ1VI5eVAhnH8HozI2unz0JjdF/h
yjlG2S8fHI/bIxH4OPLmTLBTbd0GUrAn0cmhZnSnau4zc4baxytJqhvQ5axo0/R6
PLnVc9hom+hyAiBMlvU5
=sE9F
-----END PGP SIGNATURE-----

--Apple-Mail=_AA4E87C7-3A5F-4DAB-9E92-0B80F19F1206--


From nobody Wed May 28 18:11:17 2014
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FF71A0125 for <mile@ietfa.amsl.com>; Wed, 28 May 2014 07:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 PmwK49OQSzca for <mile@ietfa.amsl.com>; Wed, 28 May 2014 07:01:18 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5601A011F for <mile@ietf.org>; Wed, 28 May 2014 07:01:17 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id uq10so2432610igb.14 for <mile@ietf.org>; Wed, 28 May 2014 07:01:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :message-id:references:to; bh=tA3+riK2byvggEbRr2+9sDT9gY4NO0yakaPYlWxiESM=; b=EIr5+00lOLDurDqa3w4gyH5cXM0onlfNtfR9Xx6FsI1Q30K72Hmvlgr8irrQukjAek gI4ZfRbjVHNL9RRuubGx+gNIvySNVohrfEo0btUqv+oEFrSmuqthF4EH1zVUjfqqJuOy nvY3Zu2WLUy/CefQwBGsWMonahdoAr+YHoK97Keo/08NUfEK6dROY7FRCm0FrknN0ql1 0SPAuHDjzM7Iy+VUtu6vkFC/9PS8/0txqPnkVxTn8sdZyJCCYlnGdEcnNKBMa0me1pDQ AlGvWHnOk5+Mgor79G4ibPauzj6+My6I6MW1khB8Y8V4VGHHCZv9m9W8MLT3QwKwsOM+ NK5g==
X-Received: by 10.42.84.131 with SMTP id m3mr37617877icl.18.1401285674082; Wed, 28 May 2014 07:01:14 -0700 (PDT)
Received: from [172.16.97.10] ([174.47.84.196]) by mx.google.com with ESMTPSA id hy3sm4011213igb.1.2014.05.28.07.01.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 May 2014 07:01:13 -0700 (PDT)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
X-Google-Original-From: "Adam W. Montville" <adam@stoicsecurity.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_296ECAD6-E16E-442E-BE39-862620EB71F3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
In-Reply-To: <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com>
Date: Wed, 28 May 2014 09:01:12 -0500
Message-Id: <1EB80AD6-0825-4D7E-AE2A-E71D922C5491@stoicsecurity.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com> <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp> <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com> <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/_RvHMZJxAeeeV5alTKpwFltjyJc
X-Mailman-Approved-At: Wed, 28 May 2014 18:11:16 -0700
Cc: "<mile@ietf.org>" <mile@ietf.org>
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 28 May 2014 14:01:20 -0000

--Apple-Mail=_296ECAD6-E16E-442E-BE39-862620EB71F3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On May 28, 2014, at 5:10 AM, Eric Burger <eburger@standardstrack.com> =
wrote:

> All it would do it introduce an opportunity to get it wrong. What do =
you do if the <Abbreviation/> does not match the <Index/>? If the answer =
is =93ignore it,=94 it means <Abbreviation/> has no protocol value. If =
the answer is =93fail the message with an error,=94 many implementors =
are likely to ignore it and some implementors will fail and =
interoperability will suffer.
>=20
> Drop <Abbreviation/>.

The -05 version of the draft (updated just yesterday) removes =
Abbreviation and integrates more specifically with the IODEF 1.00 schema =
(i.e. as described in RFC 5070) to create a 1.01 schema.


>=20
> On May 22, 2014, at 9:22 AM, Adam W. Montville =
<adam@stoicsecurity.com> wrote:
>=20
>>=20
>>=20
>>> On May 22, 2014, at 4:44 AM, "Takeshi Takahashi" =
<takeshi_takahashi@nict.go.jp> wrote:
>>>=20
>>> Hi Adam,
>>>=20
>>> I remember that we had discussion on the Index field last year.
>>> We have a field for the Index and not for version number.
>>> That is because "the Index field in the XML unambiguously indicates =
which
>>> IANA registry entry is to be used to correctly reference the =
enumeration
>>> specification, which avoids interpretation of version strings that =
may have
>>> specification-specific formats" (copied from the draft).
>>> Yes, this was what I understood in the discussion last year.
>>>=20
>>> Now I am reading the document again, and have stuck on one question.
>>> Maybe I have some misunderstanding or have forgotten some =
discussion, but I
>>> would appreciate if you could clarify the issue below.
>>>=20
>>> If we have Index field, do we need the Abbreviation field?
>>>=20
>>> Below is the example described in the draft.
>>> <EnumRef>
>>> <Abbreviation>CXI</Abbreviation>
>>> <Index>1</Index>
>>> <ID>CXI-1234-XYZ</ID>
>>> </EnumRef>
>>>=20
>>> But can we simply write like this?
>>> <EnumRef>
>>> <Index>1</Index>
>>> <ID>CXI-1234-XYZ</ID>
>>> </EnumRef>
>>>=20
>>> If we have the Index value, we can uniquely identify the =
specification and
>>> version, correct?
>>=20
>> I believe you are correct, and I can't think of a reason to keep the =
abbreviation field.
>>=20
>>=20
>>>=20
>>> Take
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Adam Montville [mailto:adam@stoicsecurity.com]
>>>> Sent: Monday, May 19, 2014 10:59 PM
>>>> To: Black, David
>>>> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>> Subject: Re: Reference and related nits in
>>>> draft-ietf-mile-enum-reference-format
>>>>=20
>>>> David, thank you.  I've noted all of these and will make =
appropriate
>>>> updates.
>>>>=20
>>>> Are there other comments other than those posed by Alexey and =
David?
>>>>=20
>>>>> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> =
wrote:
>>>>>=20
>>>>> Hi Adam,
>>>>>=20
>>>>>> With respect to your first sentence above, I assert that the =
document
>>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>>> to the abstract making the statement.
>>>>>> Thoughts here?
>>>>>=20
>>>>> In this case, it is necessary to state the obvious for the sake of
>>>>> clarity - I've been there and had to do that ;-).  In addition to =
a
>>>>> sentence in the abstract, the header on the title page needs an
>>> "Updates:
>>>> 5070 (if approved)"
>>>>> line, and a section should be added entitled "Summary of Changes =
to RFC
>>>> 5070"
>>>>> that identifies the changes.
>>>>>=20
>>>>> For a somewhat longer recent example, see RFC 7146:
>>>>>  http://datatracker.ietf.org/doc/rfc7146/
>>>>>=20
>>>>> ----------------
>>>>>=20
>>>>> Here are some additional editorial nits that need attention ...
>>>>>=20
>>>>> a) I recently had another draft dinged by the IESG for using a
>>>>> citation as a word in a sentence e.g., "[IODEF]" in the first =
sentence
>>>> in Section 2:
>>>>>=20
>>>>> The need is to place enumeration identifiers and their references =
in
>>>>> [IODEF]'s Reference class.
>>>>>=20
>>>>> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
>>>>> [IODEF]" - I suggest just doing this and not asking why :-). The =
whole
>>>>> draft should be checked for other uses of citations in this =
fashion.
>>>>>=20
>>>>> b) In addition, references should not be cited in the abstract, so =
I
>>>>> believe the appropriate changes to the two citations in the =
abstract
>>> are:
>>>>>=20
>>>>> The Incident Object Description Exchange Format [IODEF] provides a
>>>>>=20
>>>>>      "[IODEF]" -> "(IODEF)"
>>>>>=20
>>>>> Reference class used to reference external entities (such as
>>>>> enumeration identifiers).  However, the method of external entity
>>>>> identification has been left unstructured.  This document =
describes
>>>> a
>>>>> method to provide structure for referencing external entities for =
the
>>>>> [IODEF] Reference class.
>>>>>=20
>>>>>      "[IODEF]" -> "IODEF"
>>>>>=20
>>>>> Otherwise, the draft still looks good.
>>>>>=20
>>>>> Thanks,
>>>>> --David
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam =
Montville
>>>>>> Sent: Sunday, May 18, 2014 7:58 PM
>>>>>> To: Alexey Melnikov
>>>>>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>>>> Subject: Re: [mile] Working Group Last Call for =
draft-ietf-mile-enum-
>>>>>> reference-format
>>>>>>=20
>>>>>>=20
>>>>>> On May 11, 2014, at 2:54 PM, Alexey Melnikov
>>>>>> <alexey.melnikov@isode.com>
>>>>>> wrote:
>>>>>>=20
>>>>>>>=20
>>>>>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
>>>>>>>> <takeshi_takahashi@nict.go.jp>
>>>>>> wrote:
>>>>>>>>=20
>>>>>>>> Greetings, all,
>>>>>>>>=20
>>>>>>>> This is the Working Group Last Call for
>>>>>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration =
Reference
>>>> Format.
>>>>>>>>=20
>>>>>>>> The last call starts now, and ends Monday 26 May 2014.
>>>>>>>>=20
>>>>>>>> Please read the latest revision of the draft,
>>>> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
>>>>>>>> , and send your comments to the mailing list; we'd also =
appreciate
>>>>>>>> a comment if you're fine with the draft as is.
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> Below is my review of the draft:
>>>>>>>=20
>>>>>>> General comment: Is this intended as Proposed Standard? The =
draft
>>>>>>> header
>>>>>> doesn't say the document type.
>>>>>>=20
>>>>>> I'll update this, thank you.
>>>>>>=20
>>>>>>>=20
>>>>>>> The document seems to update ReferenceName syntax to allow for
>>>>>>> nested XML
>>>>>> elements. However the document doesn't say that.
>>>>>>> In relationship to this: would this document cause any
>>>>>>> interoperability
>>>>>> issues with programs that can only parse the old schema?
>>>>>>=20
>>>>>> I am unsure about interoperability issues, but they should be =
minimal
>>>>>> and are likely implementation specific.
>>>>>>=20
>>>>>> I tried an experiment where I generated some code (JAXB) for =
IODEF
>>>>>> 1.0 and then fed it a modified recon example (Section 7.2 from =
RFC
>>>>>> 5070).  The <ReferenceName> element contained an <EnumRef> =
element as
>>>>>> opposed to the string "nmap".  Unmarshalling seemed to work =
without
>>>>>> issue, but when examining the ReferenceName element , the only =
thing
>>>> present was a newline character.
>>>>>> In an example that doesn't use generated code but instead uses a =
SAX
>>>>>> or DOM parser, we can grab the inner XML.  Using a validating
>>>>>> DOM/SAX/other parser will, of course, break if the enumeration
>>>>>> reference XML is embedded, so parsers will need to be updated.
>>>>>>=20
>>>>>> I'm not a professional implementor, so it would be good to hear
>>>>>> considerations from others.  Then, should these considerations be
>>>>>> placed in the document (I assume that was the good point of =
raising the
>>>> issue)?
>>>>>>=20
>>>>>> With respect to your first sentence above, I assert that the =
document
>>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>>> to the abstract making the statement.
>>>>>> Thoughts here?
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> 4  IANA Considerations
>>>>>>>=20
>>>>>>>  Note that certain name requests should not be permitted as =
either
>>>>>>>  Full Name or Abbreviation entries for the requested IANA table.
>>>>>>>=20
>>>>>>> Do you mean restrictions imposed by the syntax described below =
or
>>>>>>> something
>>>>>> else? If you intended to exclude some specific keywords, where is =
the
>>>>>> list of them defined? Either way, I think you need to clarify. If =
you
>>>>>> just meant the ABNF restrictions, I suggest adding something like
>>>>>> "The restrictions are specified in the ABNF below".
>>>>>>>=20
>>>>>>>  Allocation Policy: Expert Review [RFC5226] and Specification
>>>>>>>  Required [RFC5226]
>>>>>>>=20
>>>>>>> Nit: I think it would be better to say "Specification Required
>>>>>>> (which
>>>>>> implies Expert Review)".
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> mile mailing list
>>>>>>> mile@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> 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


--Apple-Mail=_296ECAD6-E16E-442E-BE39-862620EB71F3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJThewoAAoJELhc5c4zaVWHmOoH/jQFYdLedCs1XPWuNsuLjpP/
c3FdWQAmcp8vb0zM22L4hhLXqQ+0QnPX+HkVen4xY3CWfvTFyFIALNQ8VwBhtgbD
Oz+p9x/vVmkioQ6QuDDIHpWCzfoMjAOSDuFhEN7jO14nSKMF2/1jMgppLR0HXzng
oQGZ4SA0sfl8lEI5ri1kB3d9TaKn5iQ/a78hhfJjjTtUUmivix+NsQSCBxXkdnuv
ij2K3jJ2G2ZXkmooZNZDxcXp2vFOZGXVBb0LuHh370XGkGkZxJRwWSz83afRc33x
L+haB/q7WvNlypF6Ab7450N+Vd1VllHIrStuvUanyss9OI8ywkK/O67Eg2UXmxE=
=CZYu
-----END PGP SIGNATURE-----

--Apple-Mail=_296ECAD6-E16E-442E-BE39-862620EB71F3--


From nobody Wed May 28 18:11:29 2014
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1909E1A09AD for <mile@ietfa.amsl.com>; Wed, 28 May 2014 07:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 JcKOFYfUj7it for <mile@ietfa.amsl.com>; Wed, 28 May 2014 07:06:17 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E3EA1A09B7 for <mile@ietf.org>; Wed, 28 May 2014 07:06:17 -0700 (PDT)
Received: by mail-ig0-f169.google.com with SMTP id hl10so2319869igb.4 for <mile@ietf.org>; Wed, 28 May 2014 07:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:mime-version:subject:in-reply-to:date:cc :message-id:references:to; bh=siX/+Gn2YmFWnM2AVjm8yLtL2t86gnGeK1HKdKtkPUI=; b=T6wUuAJwEPnBcW86E70SbT7Eq+7rSvEqqvkvJcEJGzkcftzbYgZdyoAgQlOw4YBYwN cUnVkCS6Yjnu7WuZKlgtv8Nk8aPuzV79hi0/oxSQTT6RF1onjErmmbQ8GcUBYfoz7q2+ piEdxyTCLzqNxcevVERONtY4HHsAwKp2c9mplUz6uR8NFF9xeiBrSuUGzEhhhXwmQsju 0q9wMPJDN+f3+u6VO59bFSXqGuSwlMmJ7mB0NNgkrt3ZqWc11mE0RWo+vtbdNedmu9/4 HzLDvNzx1Xw2WkBDM3A+MtXN0FVhAp3S8KtKCSMtjgpx+oDsxTik6nZfMvU7ooZb87Kg ZO9A==
X-Received: by 10.43.138.8 with SMTP id iq8mr37614728icc.37.1401285973351; Wed, 28 May 2014 07:06:13 -0700 (PDT)
Received: from [172.16.97.10] ([174.47.84.196]) by mx.google.com with ESMTPSA id fx1sm16073954igd.1.2014.05.28.07.06.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 May 2014 07:06:11 -0700 (PDT)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
X-Google-Original-From: "Adam W. Montville" <adam@stoicsecurity.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DBFA4F17-3528-4C36-97B1-004F435B5F15"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
In-Reply-To: <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com>
Date: Wed, 28 May 2014 09:06:11 -0500
Message-Id: <E9EE737A-F9F8-45B5-B099-DABDC4E0FE3B@stoicsecurity.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com> <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp> <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com> <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/R66Jg_Hu1l-M3pwauD0UCEfrC3I
X-Mailman-Approved-At: Wed, 28 May 2014 18:11:27 -0700
Cc: "<mile@ietf.org>" <mile@ietf.org>
Subject: Re: [mile] Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 28 May 2014 14:06:22 -0000

--Apple-Mail=_DBFA4F17-3528-4C36-97B1-004F435B5F15
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On May 28, 2014, at 5:10 AM, Eric Burger <eburger@standardstrack.com> =
wrote:

> All it would do it introduce an opportunity to get it wrong. What do =
you do if the <Abbreviation/> does not match the <Index/>? If the answer =
is =93ignore it,=94 it means <Abbreviation/> has no protocol value. If =
the answer is =93fail the message with an error,=94 many implementors =
are likely to ignore it and some implementors will fail and =
interoperability will suffer.
>=20
> Drop <Abbreviation/>.
>=20

The -05 version of the draft (updated just yesterday) removes =
Abbreviation and integrates more specifically with the IODEF 1.00 schema =
(i.e. as described in RFC 5070) to create a 1.01 schema.



> On May 22, 2014, at 9:22 AM, Adam W. Montville =
<adam@stoicsecurity.com> wrote:
>=20
>>=20
>>=20
>>> On May 22, 2014, at 4:44 AM, "Takeshi Takahashi" =
<takeshi_takahashi@nict.go.jp> wrote:
>>>=20
>>> Hi Adam,
>>>=20
>>> I remember that we had discussion on the Index field last year.
>>> We have a field for the Index and not for version number.
>>> That is because "the Index field in the XML unambiguously indicates =
which
>>> IANA registry entry is to be used to correctly reference the =
enumeration
>>> specification, which avoids interpretation of version strings that =
may have
>>> specification-specific formats" (copied from the draft).
>>> Yes, this was what I understood in the discussion last year.
>>>=20
>>> Now I am reading the document again, and have stuck on one question.
>>> Maybe I have some misunderstanding or have forgotten some =
discussion, but I
>>> would appreciate if you could clarify the issue below.
>>>=20
>>> If we have Index field, do we need the Abbreviation field?
>>>=20
>>> Below is the example described in the draft.
>>> <EnumRef>
>>> <Abbreviation>CXI</Abbreviation>
>>> <Index>1</Index>
>>> <ID>CXI-1234-XYZ</ID>
>>> </EnumRef>
>>>=20
>>> But can we simply write like this?
>>> <EnumRef>
>>> <Index>1</Index>
>>> <ID>CXI-1234-XYZ</ID>
>>> </EnumRef>
>>>=20
>>> If we have the Index value, we can uniquely identify the =
specification and
>>> version, correct?
>>=20
>> I believe you are correct, and I can't think of a reason to keep the =
abbreviation field.
>>=20
>>=20
>>>=20
>>> Take
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: Adam Montville [mailto:adam@stoicsecurity.com]
>>>> Sent: Monday, May 19, 2014 10:59 PM
>>>> To: Black, David
>>>> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>> Subject: Re: Reference and related nits in
>>>> draft-ietf-mile-enum-reference-format
>>>>=20
>>>> David, thank you.  I've noted all of these and will make =
appropriate
>>>> updates.
>>>>=20
>>>> Are there other comments other than those posed by Alexey and =
David?
>>>>=20
>>>>> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com> =
wrote:
>>>>>=20
>>>>> Hi Adam,
>>>>>=20
>>>>>> With respect to your first sentence above, I assert that the =
document
>>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>>> to the abstract making the statement.
>>>>>> Thoughts here?
>>>>>=20
>>>>> In this case, it is necessary to state the obvious for the sake of
>>>>> clarity - I've been there and had to do that ;-).  In addition to =
a
>>>>> sentence in the abstract, the header on the title page needs an
>>> "Updates:
>>>> 5070 (if approved)"
>>>>> line, and a section should be added entitled "Summary of Changes =
to RFC
>>>> 5070"
>>>>> that identifies the changes.
>>>>>=20
>>>>> For a somewhat longer recent example, see RFC 7146:
>>>>>  http://datatracker.ietf.org/doc/rfc7146/
>>>>>=20
>>>>> ----------------
>>>>>=20
>>>>> Here are some additional editorial nits that need attention ...
>>>>>=20
>>>>> a) I recently had another draft dinged by the IESG for using a
>>>>> citation as a word in a sentence e.g., "[IODEF]" in the first =
sentence
>>>> in Section 2:
>>>>>=20
>>>>> The need is to place enumeration identifiers and their references =
in
>>>>> [IODEF]'s Reference class.
>>>>>=20
>>>>> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
>>>>> [IODEF]" - I suggest just doing this and not asking why :-). The =
whole
>>>>> draft should be checked for other uses of citations in this =
fashion.
>>>>>=20
>>>>> b) In addition, references should not be cited in the abstract, so =
I
>>>>> believe the appropriate changes to the two citations in the =
abstract
>>> are:
>>>>>=20
>>>>> The Incident Object Description Exchange Format [IODEF] provides a
>>>>>=20
>>>>>      "[IODEF]" -> "(IODEF)"
>>>>>=20
>>>>> Reference class used to reference external entities (such as
>>>>> enumeration identifiers).  However, the method of external entity
>>>>> identification has been left unstructured.  This document =
describes
>>>> a
>>>>> method to provide structure for referencing external entities for =
the
>>>>> [IODEF] Reference class.
>>>>>=20
>>>>>      "[IODEF]" -> "IODEF"
>>>>>=20
>>>>> Otherwise, the draft still looks good.
>>>>>=20
>>>>> Thanks,
>>>>> --David
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam =
Montville
>>>>>> Sent: Sunday, May 18, 2014 7:58 PM
>>>>>> To: Alexey Melnikov
>>>>>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
>>>>>> Subject: Re: [mile] Working Group Last Call for =
draft-ietf-mile-enum-
>>>>>> reference-format
>>>>>>=20
>>>>>>=20
>>>>>> On May 11, 2014, at 2:54 PM, Alexey Melnikov
>>>>>> <alexey.melnikov@isode.com>
>>>>>> wrote:
>>>>>>=20
>>>>>>>=20
>>>>>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
>>>>>>>> <takeshi_takahashi@nict.go.jp>
>>>>>> wrote:
>>>>>>>>=20
>>>>>>>> Greetings, all,
>>>>>>>>=20
>>>>>>>> This is the Working Group Last Call for
>>>>>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration =
Reference
>>>> Format.
>>>>>>>>=20
>>>>>>>> The last call starts now, and ends Monday 26 May 2014.
>>>>>>>>=20
>>>>>>>> Please read the latest revision of the draft,
>>>> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
>>>>>>>> , and send your comments to the mailing list; we'd also =
appreciate
>>>>>>>> a comment if you're fine with the draft as is.
>>>>>>>=20
>>>>>>> Hi,
>>>>>>> Below is my review of the draft:
>>>>>>>=20
>>>>>>> General comment: Is this intended as Proposed Standard? The =
draft
>>>>>>> header
>>>>>> doesn't say the document type.
>>>>>>=20
>>>>>> I'll update this, thank you.
>>>>>>=20
>>>>>>>=20
>>>>>>> The document seems to update ReferenceName syntax to allow for
>>>>>>> nested XML
>>>>>> elements. However the document doesn't say that.
>>>>>>> In relationship to this: would this document cause any
>>>>>>> interoperability
>>>>>> issues with programs that can only parse the old schema?
>>>>>>=20
>>>>>> I am unsure about interoperability issues, but they should be =
minimal
>>>>>> and are likely implementation specific.
>>>>>>=20
>>>>>> I tried an experiment where I generated some code (JAXB) for =
IODEF
>>>>>> 1.0 and then fed it a modified recon example (Section 7.2 from =
RFC
>>>>>> 5070).  The <ReferenceName> element contained an <EnumRef> =
element as
>>>>>> opposed to the string "nmap".  Unmarshalling seemed to work =
without
>>>>>> issue, but when examining the ReferenceName element , the only =
thing
>>>> present was a newline character.
>>>>>> In an example that doesn't use generated code but instead uses a =
SAX
>>>>>> or DOM parser, we can grab the inner XML.  Using a validating
>>>>>> DOM/SAX/other parser will, of course, break if the enumeration
>>>>>> reference XML is embedded, so parsers will need to be updated.
>>>>>>=20
>>>>>> I'm not a professional implementor, so it would be good to hear
>>>>>> considerations from others.  Then, should these considerations be
>>>>>> placed in the document (I assume that was the good point of =
raising the
>>>> issue)?
>>>>>>=20
>>>>>> With respect to your first sentence above, I assert that the =
document
>>>>>> does not "seem" to update ReferenceName, but actually does. :-)  =
Is
>>>>>> it necessary to explicitly state the obvious in this case?  I'm =
happy
>>>>>> to update the document, but I'm not sure I believe such a =
statement
>>>>>> is necessary.  If it is necessary, then a single sentence can be =
added
>>>> to the abstract making the statement.
>>>>>> Thoughts here?
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> 4  IANA Considerations
>>>>>>>=20
>>>>>>>  Note that certain name requests should not be permitted as =
either
>>>>>>>  Full Name or Abbreviation entries for the requested IANA table.
>>>>>>>=20
>>>>>>> Do you mean restrictions imposed by the syntax described below =
or
>>>>>>> something
>>>>>> else? If you intended to exclude some specific keywords, where is =
the
>>>>>> list of them defined? Either way, I think you need to clarify. If =
you
>>>>>> just meant the ABNF restrictions, I suggest adding something like
>>>>>> "The restrictions are specified in the ABNF below".
>>>>>>>=20
>>>>>>>  Allocation Policy: Expert Review [RFC5226] and Specification
>>>>>>>  Required [RFC5226]
>>>>>>>=20
>>>>>>> Nit: I think it would be better to say "Specification Required
>>>>>>> (which
>>>>>> implies Expert Review)".
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> mile mailing list
>>>>>>> mile@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> 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


--Apple-Mail=_DBFA4F17-3528-4C36-97B1-004F435B5F15
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJThe1TAAoJELhc5c4zaVWH4fsIAIxGTQfFdm1Cnyt3phoZIWA2
waa4/04xlQg4qWp95GAjqLbpWBLvpfbYmy4bhZ8UtKo1FwYHPJ/1FmY3Plq8zyBN
atXAbMZ5MIkzH/5Hrdgg1vAb5qZQy74Js99fnqm3xtdj0NaHurJKjLfaFboKDrPG
eRlNnvnnYMNx8bTQL/mofFJrpVLJAo0D7sMhSA/D9/xqE8RZfBtZ7688fFEsEAVW
0QuVPQsre1QsENQ9tQe0p0fGIhi/WFXouzV9v6Sh7ZEaakX53CgGSKISgKVCYb21
3qjcRoGIUCYXWxNTgjRkDUS9I52emLPcV73ZQtjsUhLfpDzd/bnfumev0JNPPXQ=
=gaU2
-----END PGP SIGNATURE-----

--Apple-Mail=_DBFA4F17-3528-4C36-97B1-004F435B5F15--


From nobody Wed May 28 18:24:27 2014
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 376B11A086D for <mile@ietfa.amsl.com>; Wed, 28 May 2014 18:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.043
X-Spam-Level: 
X-Spam-Status: No, score=-0.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 HgbtI92Q4_Y3 for <mile@ietfa.amsl.com>; Wed, 28 May 2014 18:24:21 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B4C11A067F for <mile@ietf.org>; Wed, 28 May 2014 18:24:21 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id s4T1OGxx021191 for <mile@ietf.org>; Thu, 29 May 2014 10:24:16 +0900 (JST)
Received: from mail1.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp  with ESMTP id s4T1OFLd019465 for <mile@ietf.org>; Thu, 29 May 2014 10:24:16 +0900 (JST)
Received: from mail1.nict.go.jp (localhost [127.0.0.1]) by mail1.nict.go.jp (NICT Mail) with ESMTP id DCC132C8B1 for <mile@ietf.org>; Thu, 29 May 2014 10:24:15 +0900 (JST)
Received: from VAIO (unknown [133.243.119.184]) by mail1.nict.go.jp (NICT Mail) with ESMTP id D5A892C8B0 for <mile@ietf.org>; Thu, 29 May 2014 10:24:15 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712076C55BC0D@MX15A.corp.emc.com> <4CD8DDF5-ECA1-4351-90DE-D8B213788A1C@stoicsecurity.com> <00a101cf75b3$3ae4e970$b0aebc50$@nict.go.jp> <3940B00A-BC5E-41A3-9627-2111A1970B22@stoicsecurity.com> <C83BECAD-27AA-4ADC-98D1-CC7056F174B7@standardstrack.com> <1EB80AD6-0825-4D7E-AE2A-E71D922C5491@stoicsecurity.com>
In-Reply-To: <1EB80AD6-0825-4D7E-AE2A-E71D922C5491@stoicsecurity.com>
Date: Thu, 29 May 2014 10:24:18 +0900
Message-ID: <000001cf7adc$b6169200$2243b600$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0001_01CF7B28.25FF4B70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKc7BPik8IqmT4Sp0oJUR3hLlrCgAFkNJ1kAloBQ5EB2+NHaAGRoJcYAZLZpTeZder/AA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith2
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/mHqNiSRf1i3mAOImOM_BZN2xIpA
Subject: [mile] FW: Reference and related nits in draft-ietf-mile-enum-reference-format
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
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, 29 May 2014 01:24:24 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0001_01CF7B28.25FF4B70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Let me forward the email here.

> -----Original Message-----
> From: Adam W. Montville [mailto:adam.w.montville@gmail.com]
> Sent: Wednesday, May 28, 2014 11:01 PM
> To: Eric Burger
> Cc: Takeshi Takahashi; <mile@ietf.org>
> Subject: Re: [mile] Reference and related nits in
> draft-ietf-mile-enum-reference-format
> 
> 
> On May 28, 2014, at 5:10 AM, Eric Burger <eburger@standardstrack.com>
wrote:
> 
> > All it would do it introduce an opportunity to get it wrong. What do you
> do if the <Abbreviation/> does not match the <Index/>? If the answer is
> "ignore it," it means <Abbreviation/> has no protocol value. If the answer
> is "fail the message with an error," many implementors are likely to
ignore
> it and some implementors will fail and interoperability will suffer.
> >
> > Drop <Abbreviation/>.
> 
> The -05 version of the draft (updated just yesterday) removes Abbreviation
> and integrates more specifically with the IODEF 1.00 schema (i.e. as
> described in RFC 5070) to create a 1.01 schema.
> 
> 
> >
> > On May 22, 2014, at 9:22 AM, Adam W. Montville <adam@stoicsecurity.com>
> wrote:
> >
> >>
> >>
> >>> On May 22, 2014, at 4:44 AM, "Takeshi Takahashi"
> <takeshi_takahashi@nict.go.jp> wrote:
> >>>
> >>> Hi Adam,
> >>>
> >>> I remember that we had discussion on the Index field last year.
> >>> We have a field for the Index and not for version number.
> >>> That is because "the Index field in the XML unambiguously indicates
> >>> which IANA registry entry is to be used to correctly reference the
> >>> enumeration specification, which avoids interpretation of version
> >>> strings that may have specification-specific formats" (copied from the
> draft).
> >>> Yes, this was what I understood in the discussion last year.
> >>>
> >>> Now I am reading the document again, and have stuck on one question.
> >>> Maybe I have some misunderstanding or have forgotten some
> >>> discussion, but I would appreciate if you could clarify the issue
below.
> >>>
> >>> If we have Index field, do we need the Abbreviation field?
> >>>
> >>> Below is the example described in the draft.
> >>> <EnumRef>
> >>> <Abbreviation>CXI</Abbreviation>
> >>> <Index>1</Index>
> >>> <ID>CXI-1234-XYZ</ID>
> >>> </EnumRef>
> >>>
> >>> But can we simply write like this?
> >>> <EnumRef>
> >>> <Index>1</Index>
> >>> <ID>CXI-1234-XYZ</ID>
> >>> </EnumRef>
> >>>
> >>> If we have the Index value, we can uniquely identify the
> >>> specification and version, correct?
> >>
> >> I believe you are correct, and I can't think of a reason to keep the
> abbreviation field.
> >>
> >>
> >>>
> >>> Take
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Adam Montville [mailto:adam@stoicsecurity.com]
> >>>> Sent: Monday, May 19, 2014 10:59 PM
> >>>> To: Black, David
> >>>> Cc: Alexey Melnikov; <mile@ietf.org>; mile-chairs@tools.ietf.org
> >>>> Subject: Re: Reference and related nits in
> >>>> draft-ietf-mile-enum-reference-format
> >>>>
> >>>> David, thank you.  I've noted all of these and will make
> >>>> appropriate updates.
> >>>>
> >>>> Are there other comments other than those posed by Alexey and David?
> >>>>
> >>>>> On May 18, 2014, at 7:39 PM, Black, David <david.black@emc.com>
wrote:
> >>>>>
> >>>>> Hi Adam,
> >>>>>
> >>>>>> With respect to your first sentence above, I assert that the
> >>>>>> document does not "seem" to update ReferenceName, but actually
> >>>>>> does. :-)  Is it necessary to explicitly state the obvious in
> >>>>>> this case?  I'm happy to update the document, but I'm not sure I
> >>>>>> believe such a statement is necessary.  If it is necessary, then
> >>>>>> a single sentence can be added
> >>>> to the abstract making the statement.
> >>>>>> Thoughts here?
> >>>>>
> >>>>> In this case, it is necessary to state the obvious for the sake of
> >>>>> clarity - I've been there and had to do that ;-).  In addition to
> >>>>> a sentence in the abstract, the header on the title page needs an
> >>> "Updates:
> >>>> 5070 (if approved)"
> >>>>> line, and a section should be added entitled "Summary of Changes
> >>>>> to RFC
> >>>> 5070"
> >>>>> that identifies the changes.
> >>>>>
> >>>>> For a somewhat longer recent example, see RFC 7146:
> >>>>>  http://datatracker.ietf.org/doc/rfc7146/
> >>>>>
> >>>>> ----------------
> >>>>>
> >>>>> Here are some additional editorial nits that need attention ...
> >>>>>
> >>>>> a) I recently had another draft dinged by the IESG for using a
> >>>>> citation as a word in a sentence e.g., "[IODEF]" in the first
> >>>>> sentence
> >>>> in Section 2:
> >>>>>
> >>>>> The need is to place enumeration identifiers and their references
> >>>>> in [IODEF]'s Reference class.
> >>>>>
> >>>>> Believe it or not, the appropriate change is "[IODEF]" -> "IODEF
> >>>>> [IODEF]" - I suggest just doing this and not asking why :-). The
> >>>>> whole draft should be checked for other uses of citations in this
> fashion.
> >>>>>
> >>>>> b) In addition, references should not be cited in the abstract, so
> >>>>> I believe the appropriate changes to the two citations in the
> >>>>> abstract
> >>> are:
> >>>>>
> >>>>> The Incident Object Description Exchange Format [IODEF] provides a
> >>>>>
> >>>>>      "[IODEF]" -> "(IODEF)"
> >>>>>
> >>>>> Reference class used to reference external entities (such as
> >>>>> enumeration identifiers).  However, the method of external entity
> >>>>> identification has been left unstructured.  This document
> >>>>> describes
> >>>> a
> >>>>> method to provide structure for referencing external entities for
> >>>>> the [IODEF] Reference class.
> >>>>>
> >>>>>      "[IODEF]" -> "IODEF"
> >>>>>
> >>>>> Otherwise, the draft still looks good.
> >>>>>
> >>>>> Thanks,
> >>>>> --David
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam
> >>>>>> Montville
> >>>>>> Sent: Sunday, May 18, 2014 7:58 PM
> >>>>>> To: Alexey Melnikov
> >>>>>> Cc: <mile@ietf.org>; mile-chairs@tools.ietf.org
> >>>>>> Subject: Re: [mile] Working Group Last Call for
> >>>>>> draft-ietf-mile-enum- reference-format
> >>>>>>
> >>>>>>
> >>>>>> On May 11, 2014, at 2:54 PM, Alexey Melnikov
> >>>>>> <alexey.melnikov@isode.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>>> On 8 May 2014, at 12:30, "Takeshi Takahashi"
> >>>>>>>> <takeshi_takahashi@nict.go.jp>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Greetings, all,
> >>>>>>>>
> >>>>>>>> This is the Working Group Last Call for
> >>>>>>>> draft-ietf-mile-enum-reference-format, IODEF Enumeration
> >>>>>>>> Reference
> >>>> Format.
> >>>>>>>>
> >>>>>>>> The last call starts now, and ends Monday 26 May 2014.
> >>>>>>>>
> >>>>>>>> Please read the latest revision of the draft,
> >>>>
> http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-04
> >>>>>>>> , and send your comments to the mailing list; we'd also
> >>>>>>>> appreciate a comment if you're fine with the draft as is.
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>> Below is my review of the draft:
> >>>>>>>
> >>>>>>> General comment: Is this intended as Proposed Standard? The
> >>>>>>> draft header
> >>>>>> doesn't say the document type.
> >>>>>>
> >>>>>> I'll update this, thank you.
> >>>>>>
> >>>>>>>
> >>>>>>> The document seems to update ReferenceName syntax to allow for
> >>>>>>> nested XML
> >>>>>> elements. However the document doesn't say that.
> >>>>>>> In relationship to this: would this document cause any
> >>>>>>> interoperability
> >>>>>> issues with programs that can only parse the old schema?
> >>>>>>
> >>>>>> I am unsure about interoperability issues, but they should be
> >>>>>> minimal and are likely implementation specific.
> >>>>>>
> >>>>>> I tried an experiment where I generated some code (JAXB) for
> >>>>>> IODEF
> >>>>>> 1.0 and then fed it a modified recon example (Section 7.2 from
> >>>>>> RFC 5070).  The <ReferenceName> element contained an <EnumRef>
> >>>>>> element as opposed to the string "nmap".  Unmarshalling seemed to
> >>>>>> work without issue, but when examining the ReferenceName element
> >>>>>> , the only thing
> >>>> present was a newline character.
> >>>>>> In an example that doesn't use generated code but instead uses a
> >>>>>> SAX or DOM parser, we can grab the inner XML.  Using a validating
> >>>>>> DOM/SAX/other parser will, of course, break if the enumeration
> >>>>>> reference XML is embedded, so parsers will need to be updated.
> >>>>>>
> >>>>>> I'm not a professional implementor, so it would be good to hear
> >>>>>> considerations from others.  Then, should these considerations be
> >>>>>> placed in the document (I assume that was the good point of
> >>>>>> raising the
> >>>> issue)?
> >>>>>>
> >>>>>> With respect to your first sentence above, I assert that the
> >>>>>> document does not "seem" to update ReferenceName, but actually
> >>>>>> does. :-)  Is it necessary to explicitly state the obvious in
> >>>>>> this case?  I'm happy to update the document, but I'm not sure I
> >>>>>> believe such a statement is necessary.  If it is necessary, then
> >>>>>> a single sentence can be added
> >>>> to the abstract making the statement.
> >>>>>> Thoughts here?
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> 4  IANA Considerations
> >>>>>>>
> >>>>>>>  Note that certain name requests should not be permitted as
> >>>>>>> either  Full Name or Abbreviation entries for the requested IANA
> table.
> >>>>>>>
> >>>>>>> Do you mean restrictions imposed by the syntax described below
> >>>>>>> or something
> >>>>>> else? If you intended to exclude some specific keywords, where is
> >>>>>> the list of them defined? Either way, I think you need to
> >>>>>> clarify. If you just meant the ABNF restrictions, I suggest
> >>>>>> adding something like "The restrictions are specified in the ABNF
> below".
> >>>>>>>
> >>>>>>>  Allocation Policy: Expert Review [RFC5226] and Specification
> >>>>>>> Required [RFC5226]
> >>>>>>>
> >>>>>>> Nit: I think it would be better to say "Specification Required
> >>>>>>> (which
> >>>>>> implies Expert Review)".
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> 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_0001_01CF7B28.25FF4B70
Content-Type: application/pgp-signature;
	name="signature.asc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJThewoAAoJELhc5c4zaVWHmOoH/jQFYdLedCs1XPWuNsuLjpP/
c3FdWQAmcp8vb0zM22L4hhLXqQ+0QnPX+HkVen4xY3CWfvTFyFIALNQ8VwBhtgbD
Oz+p9x/vVmkioQ6QuDDIHpWCzfoMjAOSDuFhEN7jO14nSKMF2/1jMgppLR0HXzng
oQGZ4SA0sfl8lEI5ri1kB3d9TaKn5iQ/a78hhfJjjTtUUmivix+NsQSCBxXkdnuv
ij2K3jJ2G2ZXkmooZNZDxcXp2vFOZGXVBb0LuHh370XGkGkZxJRwWSz83afRc33x
L+haB/q7WvNlypF6Ab7450N+Vd1VllHIrStuvUanyss9OI8ywkK/O67Eg2UXmxE=
=CZYu
-----END PGP SIGNATURE-----

------=_NextPart_000_0001_01CF7B28.25FF4B70--

