
From nobody Tue Oct 21 18:15:59 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 7F5631A88FA for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 18:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.497
X-Spam-Level: **
X-Spam-Status: No, score=2.497 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 f75yrKPrHKNo for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 18:15:55 -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 1A79A1A88F5 for <mile@ietf.org>; Tue, 21 Oct 2014 18:15:54 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id s9M1Fr8o015304 for <mile@ietf.org>; Wed, 22 Oct 2014 10:15:53 +0900 (JST)
Received: from mail3.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp  with ESMTP id s9M1FrKx026781 for <mile@ietf.org>; Wed, 22 Oct 2014 10:15:53 +0900 (JST)
Received: from mail3.nict.go.jp (localhost [127.0.0.1]) by mail3.nict.go.jp (NICT Mail) with ESMTP id EE42116AF0 for <mile@ietf.org>; Wed, 22 Oct 2014 10:15:52 +0900 (JST)
Received: from VAIO (unknown [133.243.119.70]) by mail3.nict.go.jp (NICT Mail) with ESMTP id E2413169F2 for <mile@ietf.org>; Wed, 22 Oct 2014 10:15:52 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Wed, 22 Oct 2014 10:15:52 +0900
Message-ID: <001d01cfed95$b92651c0$2b72f540$@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: Ac/tlbF1wvEhXHJvTRaq/4DgizwjPw==
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/vYTmI7F1YOjcHRHx64JGjv5vNds
Subject: [mile] IETF-91: call for agenda items
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, 22 Oct 2014 01:15:56 -0000

Hello all,

The MILE session in IETF 91 will be held on Monday, 1300-1500 in the room
"Hibiscus".

We would like to build the agenda for the session.
Please send your requests including the topic, requested time, and relevant
Internet-Draft(s). 

Thanks and Regards,

Take

PS:
Time files so fast. Let me catch up each of the MILE-related activities
asap.




From nobody Tue Oct 21 18:56:43 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 882E51A897C for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 18:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.298
X-Spam-Level: ***
X-Spam-Status: No, score=3.298 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 3nrcDuvOKio2 for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 18:56:38 -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 81BA51A8978 for <mile@ietf.org>; Tue, 21 Oct 2014 18:56:38 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id s9M1uUZj027202; Wed, 22 Oct 2014 10:56:30 +0900 (JST)
Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp  with ESMTP id s9M1uUW3003455; Wed, 22 Oct 2014 10:56:30 +0900 (JST)
Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 787632C201; Wed, 22 Oct 2014 10:56:30 +0900 (JST)
Received: from VAIO (unknown [133.243.119.70]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 6FF3C2C1B7; Wed, 22 Oct 2014 10:56:30 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Wed, 22 Oct 2014 10:56:30 +0900
Message-ID: <003201cfed9b$65ff7cf0$31fe76d0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/tm0fv5aT3UNCbQ5+ki0ti6TjngA==
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/2ZtG3lPN-4MUaeGYEcxfYIHVhV4
Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
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, 22 Oct 2014 01:56:42 -0000

Hello Adam, David, and all,

I agree with the direction you have developed (developing separate =
schema
would be a good idea.)
I apologize my late response.

I can see several supportive comments on this draft change, and I can =
see no
negative comments on this.
So, I believe the community is happy to develop the draft to the =
direction
the authors did.

The last concern is the schema, IMHO.
We have already asked App area experts to review the newly changed =
schema,
but I think we have not received clear confirmation yet.

At the same time, I myself have a concern on the schema since it does =
not
extend any of the IODEF-related classes.
IODEF extension works usually extends extending IODEF ciass, so I wonder
whether the current schema of the enum draft is ok or not.

It could be that we cannot embed the ReferenceName element inside =
IODEF's
Reference class if we use the current schema.
I might be wrong, so confirmation would be appreciated.
One way I would think is extending the existing IODEF's Reference class.

Take



2014-08-19 2:27 GMT+09:00 Black, David <david.black@emc.com>:
> On XML snippet vs. schema:
>
>> If we encourage pasting the above [XML snippet] into other schemas, =
is
there
>> then a policing
>> effort to ensure that documentation references are correct and that =
the
schema
>> is correct? =A0It seems better for wider adoption to go with the =
inbuilt
XML
>> constructs of namespaces to allow IODEFv2 to simply reference an enum =
ref
>> namespace at the appropriate location, then define the enum ref =
schema
once,
>> which will be associated with just one document detailing the IANA
registry
>> and the expert review, etc.
>
> Well, the IANA registry and its associated review procedures get =
defined
once in
> one document, independent of what we do.
>
> OTOH, the namespace separation and related discipline of using a =
separate
schema
> for the enumeration references are useful and the proverbial "right =
thing
to do,"
> plus Roman's provided much (if not all of the text) needed, so I'm =
fine
with that
> approach.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Adam W. Montville [mailto:adam.w.montville@gmail.com]
>> Sent: Wednesday, August 06, 2014 11:00 AM
>> To: Black, David
>> Cc: Roman D. Danyliw; MILE IETF
>> Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
>>
>>
>> On Aug 5, 2014, at 6:28 PM, Black, David <david.black@emc.com> wrote:
>>
>> > Hello Roman,
>> >
>> > This is helpful (thanks):
>> >
>> >> I hadn't been thinking along these lines. =A0To use a software =
analogy,
I didn't
>> >> envision that we'd back-port the fix to a legacy version of the
software
>> >> (IODEFv1, RFC 5070). =A0Instead I figured we should make a library =
(an
iodef
>> >> enum extension) that the new version (IODEF v2, 5070bis) and =
alternate
>> >> software (SACM) could use. =A0My thinking was if v1 is broken, =
upgrade
to v2,
>> >> not v1.01.
>> >
>> > Well, the current draft is an incompatible back-port because it =
updates
>> > the IODEFv1 schema version to "1.01". =A0I understand both you and =
Panos
to
>> > be characterizing that as a bad idea (on which I defer to your
expertise),
>> > so I'd like to explore alternatives.
>> >
>> > My next question is "what sort of library?". =A0The email below =
proposes
what
>> > is effectively a reusable XML (sub-schema) that can be included in
other
>> > XML schemas.
>> >
>> > I wonder whether instead of supplying the (sub-)schema as a =
"library"
that
>> > can be used at runtime, can we supply the XML schema snippet for =
enum
>> > reference formats for use in XML schema design along with the IANA
registry.
>> >
>> > One more question:
>> >
>> > Is there a case to be made for use of the same XML (sub-)schema
(iodef-enum
>> > below) in multiple containing schemas, e.g., IODEFv2, SACM, etc., =
or is
it
>> > sufficient to use the same XML syntax to represent the enumeration
values?
>> >
>> > For "same XML syntax", the draft could recommend that anyone who =
wants
to use
>> > an enumeration reference value put the following XML snippet in =
their
schema:
>> >
>> > =A0 =A0 =A0<xs:element name=3D"SpecReferenceName">
>> > =A0 =A0 =A0 <xs:complexType>
>> > =A0 =A0 =A0 <xs:sequence>
>> > =A0 =A0 =A0 =A0 <xs:element name=3D"ID" type=3D"xs:NCName"/>
>> > =A0 =A0 =A0 </xs:sequence>
>> > =A0 =A0 =A0 <xs:attribute name=3D"specIndex" type=3D"xs:integer" =
use=3D"required"/>
>> > =A0 =A0 =A0 </xs:complexType>
>> > =A0 =A0 =A0</xs:element>
>> >
>> > [NB: I changed "ReferenceName" to "SpecReferenceName" with the =
intent
of
>> > enabling use of an unconstrained "ReferenceName" element for other
>> purposes.]
>> >
>> > The enum-reference-format draft could further recommend that
documentation
>> > of any schema that includes that snippet include a reference to the
IANA
>> > registry (created by the enum-reference-format draft) that defines =
the
>> > specIndex values.
>> >
>> > That ought to simplify adding this to the IODEFv2 (5070bis) schema.
>> >
>> > Thoughts?
>>
>> If we encourage pasting the above into other schemas, is there then a
policing
>> effort to ensure that documentation references are correct and that =
the
schema
>> is correct? =A0It seems better for wider adoption to go with the =
inbuilt
XML
>> constructs of namespaces to allow IODEFv2 to simply reference an enum =
ref
>> namespace at the appropriate location, then define the enum ref =
schema
once,
>> which will be associated with just one document detailing the IANA
registry
>> and the expert review, etc.
>>
>>
>> >
>> > Thanks,
>> > --David
>> >
>> >
>> >> -----Original Message-----
>> >> From: Roman D. Danyliw [mailto:rdd@cert.org]
>> >> Sent: Thursday, July 31, 2014 3:34 PM
>> >> To: Black, David; MILE IETF
>> >> Subject: RE: [mile] EnumRef Format to IODEF Extension Suggestion
>> >>
>> >> Hello David!
>> >>
>> >>> -----Original Message-----
>> >>> From: Black, David [mailto:david.black@emc.com]
>> >>> Sent: Sunday, July 27, 2014 1:47 PM
>> >>> To: Roman D. Danyliw; MILE IETF
>> >>> Cc: Black, David
>> >>> Subject: RE: [mile] EnumRef Format to IODEF Extension Suggestion
>> >>>
>> >>> Hello Roman,
>> >>>
>> >>> This approach is interesting, although it looks like it would =
still
>> require
>> >> a
>> >>> change to the IODEF Schema version. =A0I wonder whether we can go
further
>> >>> than arrange for the 5070bis draft to contain the only new =
version of
the
>> >>> IODEF schema beyond RFC 5070. =A0Towards that end, I have a =
couple of
>> >>> questions:
>> >>
>> >> I hadn't been thinking along these lines. =A0To use a software =
analogy,
I
>> didn't
>> >> envision that we'd back-port the fix to a legacy version of the
software
>> >> (IODEFv1, RFC 5070). =A0Instead I figured we should make a library =
(an
iodef
>> >> enum extension) that the new version (IODEF v2, 5070bis) and =
alternate
>> >> software (SACM) could use. =A0My thinking was if v1 is broken, =
upgrade
to v2,
>> >> not v1.01.
>> >>
>> >>> (1) Could the SpecIndex attribute be added to the ReferenceName =
class
in
>> >>> the IODEF v2 schema in 5070bis, as an optional attribute? =A0My
thinking is
>> >> that
>> >>> having this new attribute be optional allows the IODEF v2 =
Reference
class
>> to
>> >>> continue to be used for everything that it's used for in IODEF =
v1,
but
>> when
>> >>> the SpecIndex attribute is present, it constrains the =
ReferenceName
to
>> >>> follow the format in the enumeration reference draft - the latter
>> >>> requirement would be imposed by additional text in the 5070bis =
draft.
>> >>
>> >> That does provide maximum flexibility. =A0The thinking would be if =
you
see
>> the
>> >> SpecIndex reference the enum draft to understand the semantics. =
=A0If
there
>> is
>> >> not SpecIndex reference 5070. =A0This switch could also be handle =
with
>> >> namespaces by defining a schema of "choice ( iodef-1.0:Reference,
iodef-
>> >> enum:Reference)".
>> >>
>> >> We have to decide whether to specify a stand-alone schema, an =
IODEF
>> extension,
>> >> or both? =A0Would SACM only use the newer SpecIndex-based =
Reference
class?
>> >>
>> >> I feel that the implementers need to tell us how much backward
>> compatibility
>> >> needs to be maintained. =A0We've already broken compatibility in =
5070bis
on
>> >> Node/Name, Node/DateTime, and Service@ip_protocol. =A0My feeling =
is that
we
>> >> should break it here again and force the "new improved" Reference =
in
v2.
>> >> Perhaps we can add some escape value into SpecIndex to make the =
new
>> >> ReferenceName/ID behave like a Description class.
>> >>
>> >>> (2) The Reference class in the IODEF v1 schema (RFC 5070) is not
>> extensible
>> >> in
>> >>> that schema, but that Reference class is contained in the Method
class
>> which
>> >>> can be extended via use of the (optional) AdditionalData class. =
=A0Is
there
>> a
>> >>> reasonably acceptable/usable approach to use of AdditionalData =
with
>> >>> Method to pull the enumeration references into IODEF v1 without
creating a
>> >>> new schema version, or is this just asking for confusion?
>> >>
>> >> If the enum draft was published to include an iodef extension no
change at
>> >> would be required to RFC5070. =A0An implementer would simply drop =
in the
enum
>> >> extension into Method/AdditionalData. =A0The only challenge would =
be
that a
>> >> Reference or Description child class are required. =A0Therefore to =
use
>> >> AdditionalData you would have to
"<Method><Description/><AdditionalData
>> >> ...></Method>".
>> >>
>> >> Roman
>> >>
>> >>>> -----Original Message-----
>> >>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman D.
>> >>>> Danyliw
>> >>>> Sent: Friday, July 25, 2014 10:51 PM
>> >>>> To: 'Adam W. Montville'; MILE IETF
>> >>>> Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
>> >>>>
>> >>>> Hello!
>> >>>>
>> >>>> To be more specific about what was proposed at IETF 90, please =
find
>> >>>> inline a rough draft of modifications agathe -07 draft. =
=A0Beyond the
>> >>>> boiler-plate, only sections with modified text are listed.
>> >>>>
>> >>>> ---[ snip ]--
>> >>>>
>> >>>> MILE Working Group =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0A.
Montville
>> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0Tripwire
>> >>>> Obsoletes: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 D.
Black
>> >>>> Intended status: Standards Track =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
EMC
>> >>>> Expires: January 31, 2015 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0August
2014
>> >>>>
>> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 IODEF Enumeration Reference =
Format
>> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =
=A0draft-ietf-mile-enum-reference-format-07-bis
>> >>>>
>> >>>> Abstract
>> >>>>
>> >>>> =A0 [Keep first paragraph]
>> >>>>
>> >>>> =A0 [Modified second paragraph] This memo provides an extension =
to RFC
>> >>>> =A0 5070 to include both the external specification and specific
>> >>>> =A0 enumeration value in the IODEF Reference class. =A0This memo =
also
>> >>>> =A0 establishes an IANA registry to manage external enumeration
>> >>>> =A0 specifications for use by IODEF.
>> >>>>
>> >>>> =A0 The IETF has been notified of intellectual property rights =
claimed
in
>> >>>> =A0 regard to some or all of the specification contained in this
>> >>>> =A0 document. =A0For more information consult the online list of =
claimed
>> >>>> =A0 rights.
>> >>>>
>> >>>> Status of this Memo
>> >>>>
>> >>>> =A0 This Internet-Draft is submitted in full conformance with =
the
>> >>>> =A0 provisions of BCP 78 and BCP 79.
>> >>>>
>> >>>> =A0 Internet-Drafts are working documents of the Internet =
Engineering
>> >>>> =A0 Task Force (IETF). =A0Note that other groups may also =
distribute
>> >>>> =A0 working documents as Internet-Drafts. =A0The list of current
Internet-
>> >>>> =A0 Drafts is at http://datatracker.ietf.org/drafts/current/.
>> >>>>
>> >>>> =A0 Internet-Drafts are draft documents valid for a maximum of =
six
months
>> >>>> =A0 and may be updated, replaced, or obsoleted by other =
documents at
any
>> >>>> =A0 time. =A0It is inappropriate to use Internet-Drafts as =
reference
>> >>>> =A0 material or to cite them other than as "work in progress."
>> >>>>
>> >>>> =A0 This Internet-Draft will expire on January 31, 2015.
>> >>>>
>> >>>> Copyright Notice
>> >>>>
>> >>>> =A0 Copyright (c) 2014 IETF Trust and the persons identified as =
the
>> >>>> =A0 document authors. =A0All rights reserved.
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0
=A0[Page 1]
>> >>>>
>> >>>>
>> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 August
2014
>> >>>>
>> >>>>
>> >>>> =A0 This document is subject to BCP 78 and the IETF Trust's =
Legal
>> >>>> =A0 Provisions Relating to IETF Documents =
(http://trustee.ietf.org/
>> >>>> =A0 license-info) in effect on the date of publication of this
document.
>> >>>> =A0 Please review these documents carefully, as they describe =
your
rights
>> >>>> =A0 and restrictions with respect to this document. =A0Code =
Components
>> >>>> =A0 extracted from this document must include Simplified BSD =
License
text
>> >>>> =A0 as described in Section 4.e of the Trust Legal Provisions =
and are
>> >>>> =A0 provided without warranty as described in the Simplified BSD
License.
>> >>>>
>> >>>> =A0 This document may contain material from IETF Documents or =
IETF
>> >>>> =A0 Contributions published or made publicly available before =
November
>> >>>> =A0 10, 2008. =A0The person(s) controlling the copyright in some =
of this
>> >>>> =A0 material may not have granted the IETF Trust the right to =
allow
>> >>>> =A0 modifications of such material outside the IETF Standards =
Process.
>> >>>> =A0 Without obtaining an adequate license from the person(s)
controlling
>> >>>> =A0 the copyright in such materials, this document may not be =
modified
>> >>>> =A0 outside the IETF Standards Process, and derivative works of =
it may
>> >>>> =A0 not be created outside the IETF Standards Process, except to
format
>> >>>> =A0 it for publication as an RFC or to translate it into =
languages
other
>> >>>> =A0 than English.
>> >>>>
>> >>>> Table of Contents
>> >>>>
>> >>>> =A0 1. =A0Introduction . . . . . . . . . . . . . . . . . . . . . =
. . . .
=A02
>> >>>> =A0 =A0 1.1. =A0Terminology =A0. . . . . . . . . . . . . . . . . =
. . . . . .
=A02
>> >>>> =A0 2. =A0Referencing External Enumerations =A0. . . . . . . . . =
. . . . .
=A02
>> >>>> =A0 =A0 2.1. =A0ReferenceName Class =A0. . . . . . . . . . . . . =
. . . . . .
=A02
>> >>>> =A0 =A0 2.2. =A0Reference Method Applicability . . . . . . . . . =
. . . . .
=A03
>> >>>> =A0 3. =A0Security Considerations =A0. . . . . . . . . . . . . . =
. . . . .
=A03
>> >>>> =A0 4. =A0IANA Considerations =A0. . . . . . . . . . . . . . . . =
. . . . .
=A04
>> >>>> =A0 5. =A0The ReferenceName Schema . . . . . . . . . . . . . . . =
. . . .
=A04
>> >>>> =A0 6. =A0References . . . . . . . . . . . . . . . . . . . . . . =
. . . .
=A05
>> >>>> =A0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . =
. . .
>> >>>> 5
>> >>>>
>> >>>> 1. =A0Introduction
>> >>>>
>> >>>> =A0 No change.
>> >>>>
>> >>>> 1.1. =A0Terminology
>> >>>>
>> >>>> =A0 No change.
>> >>>>
>> >>>> 2. =A0Referencing External Enumerations
>> >>>>
>> >>>> =A0 No change.
>> >>>>
>> >>>> 2.1. =A0ReferenceName Class
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0
=A0[Page 2]
>> >>>>
>> >>>>
>> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 August
2014
>> >>>>
>> >>>>
>> >>>> =A0 The ReferenceName class provides the XML representation for
>> >>>> =A0 identifying an enumeration and specifying a value from it. =
=A0A
given
>> >>>> =A0 enumeration is uniquely identified by the specIndex =
attribute.
=A0Each
>> >>>> =A0 specIndex value corresponds to an entry in the "Enumeration
Reference
>> >>>> =A0 Type Identifiers" IANA registry (see Section 4). =A0The =
child ID
>> >>>> =A0 element represents a particular value from the corresponding
>> >>>> =A0 enumeration identified by the specIndex attribute. =A0The =
format of
the
>> >>>> =A0 ID element is described in the IANA registry entry of the
>> >>>> =A0 enumeration.
>> >>>>
>> >>>> =A0 +-------------------------+
>> >>>> =A0 | ReferenceName =A0 =A0 =A0 =A0 =A0 |
>> >>>> =A0 +-------------------------+
>> >>>> =A0 | INTEGER specIndex =A0 =A0 =A0 |<>----------[ ID =A0 =A0]
>> >>>> =A0 +-------------------------+
>> >>>>
>> >>>> =A0 The aggregate classes that constitute ReferenceName:
>> >>>>
>> >>>> =A0 ID
>> >>>> =A0 =A0 =A0One. =A0ID. =A0Name of the reference.
>> >>>>
>> >>>> =A0 The ReferenceName class has 1 attribute.
>> >>>>
>> >>>> =A0 specIndex
>> >>>> =A0 =A0 =A0Required. =A0INTEGER. =A0Enumeration identifier. =
=A0This value
>> >>>> =A0 =A0 =A0corresponds to an entry in the =A0"Enumeration =
Reference Type
>> >>>> =A0 =A0 =A0Identifiers" IANA registry with an identical =
SpecIndex value.
>> >>>>
>> >>>> =A0 An example of such a reference is as follows:
>> >>>>
>> >>>> =A0 =A0 =A0<iodef:Reference>
>> >>>> =A0 =A0 =A0 =A0 <iodef-enum:ReferenceName specIndex=3D"1">
>> >>>> =A0 =A0 =A0 =A0 =A0 =
=A0<iodef-enum:ID>CXI-1234-XYZ</iodef-enum:ID>
>> >>>> =A0 =A0 =A0 =A0 </iodef-enum:ReferenceName>
>> >>>> =A0 =A0 =A0 =A0 <iodef:URL>http://cxi.example.com</iodef:URL>
>> >>>> =A0 =A0 =A0 =A0 <iodef:Description>Foo</iodef:Description>
>> >>>> =A0 =A0 =A0</iodef:Reference>
>> >>>>
>> >>>> =A0 The corresponding information in the IANA table (see Section =
4)
would
>> >>>> =A0 include:
>> >>>>
>> >>>> =A0 =A0 =A0Full Name: Concept X Identifier
>> >>>> =A0 =A0 =A0SpecIndex: 1
>> >>>> =A0 =A0 =A0Version: any
>> >>>> =A0 =A0 =A0Specification URI: http://cxi.example.com/spec_url
>> >>>>
>> >>>> 2.2. =A0Reference Method Applicability
>> >>>>
>> >>>> =A0 No change, but this should should be numbered 2.2 not 2.3 as =
in
the
>> >>>> =A0 -07 draft.
>> >>>>
>> >>>> 3. =A0Security Considerations
>> >>>>
>> >>>>
>> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0
=A0[Page 3]
>> >>>>
>> >>>>
>> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 August
2014
>> >>>>
>> >>>>
>> >>>> =A0 No change.
>> >>>>
>> >>>> 4. =A0IANA Considerations
>> >>>>
>> >>>> =A0 [after the existing text, the following should be added ...]
>> >>>>
>> >>>> =A0 This document uses URNs to describe XML namespaces and XML =
schemas
>> >>>> =A0 conforming to a registry mechanism described in [RFC3688].
>> >>>>
>> >>>> =A0 Registration request for the IODEF enumeration reference =
format
>> >>>> =A0 namespace:
>> >>>>
>> >>>> =A0 URI : urn:ietf:params:xml:ns:iodef-enum-1.0
>> >>>>
>> >>>> =A0 Registrant Contact : See the "Authors' Addresses" section of =
this
>> >>>> =A0 =A0 =A0document.
>> >>>>
>> >>>> =A0 XML : None.
>> >>>>
>> >>>> =A0 Registration request for the IODEF enumeration reference =
format
XML
>> >>>> =A0 schema:
>> >>>>
>> >>>> =A0 URI : urn:ietf:params:xml:schema:iodef-enum-1.0
>> >>>>
>> >>>> =A0 Registrant Contact See the "Authors' Addresses" section of =
this
>> >>>> =A0 =A0 =A0document.
>> >>>>
>> >>>> =A0 XML : See Section 6, "XML Schema", of this =A0 =A0document.
>> >>>>
>> >>>> 5. =A0The ReferenceName Schema
>> >>>>
>> >>>> =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>> >>>> =A0 <xs:schema attributeFormDefault=3D"unqualified"
>> >>>> =A0 =A0 =A0 =A0 =A0elementFormDefault=3D"qualified"
>> >>>> =A0 =A0 =A0 =A0 =
=A0targetNamespace=3D"urn:ietf:params:xml:ns:iodef-enum-1.0"
>> >>>> =A0 =A0 =A0 =A0 =A0xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
>> >>>> =A0 =A0 =A0 =A0 =
=A0xmlns:enum=3D"urn:ietf:params:xml:ns:iodef-enum-1.0">
>> >>>>
>> >>>> =A0 =A0 <!--
>> >>>>
>> >>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>> >>>> =A0 =A0 =3D=3D=3D =A0ReferenceName =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D=3D=3D
>> >>>>
>> >>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>> >>>> =A0 =A0 =A0-->
>> >>>> =A0 =A0 <xs:element name=3D"ReferenceName">
>> >>>> =A0 =A0 =A0 <xs:complexType>
>> >>>> =A0 =A0 =A0 =A0 <xs:sequence>
>> >>>> =A0 =A0 =A0 =A0 =A0 <xs:element name=3D"ID" type=3D"xs:NCName"/>
>> >>>> =A0 =A0 =A0 =A0 </xs:sequence>
>> >>>> =A0 =A0 =A0 =A0 <xs:attribute name=3D"specIndex"
>> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 type=3D"xs:integer" =
use=3D"required"/>
>> >>>> =A0 =A0 =A0 </xs:complexType>
>> >>>> =A0 =A0 </xs:element>
>> >>>> =A0 </xs:schema>
>> >>>>
>> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0
=A0[Page 4]
>> >>>>
>> >>>>
>> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 August
2014
>> >>>>
>> >>>>
>> >>>> 6. =A0References
>> >>>>
>> >>>> Authors' Addresses
>> >>>>
>> >>>> =A0 Adam W. Montville
>> >>>> =A0 Tripwire
>> >>>> =A0 USA
>> >>>>
>> >>>> =A0 Email: Adam's email
>> >>>>
>> >>>>
>> >>>> =A0 David Black
>> >>>> =A0 EMC
>> >>>> =A0 USA
>> >>>>
>> >>>> =A0 Email: David's email
>> >>>>
>> >>>>
>> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0
=A0[Page 5]
>> >>>>
>> >>>> --[ end ]--
>> >>>>
>> >>>> Roman
>> >>>>
>> >>>> -----Original Message-----
>> >>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam W.
>> >>>> Montville
>> >>>> Sent: Friday, July 25, 2014 7:30 AM
>> >>>> To: MILE IETF
>> >>>> Subject: [mile] EnumRef Format to IODEF Extension Suggestion
>> >>>>
>> >>>> Hello,
>> >>>>
>> >>>> During MILE's session this week at IETF 90, Roman suggested that =
the
>> >>>> enum reference format be changed from an update to 5070 to an =
IODEF
>> >>> extension.
>> >>>> This would require that the enum reference format draft be =
updated
>> >>>> accordingly and that a full schema and namespace be considered =
for
the
>> >>>> format itself, rather than simply updating the IODEF schema.
>> >>>>
>> >>>> The obvious drawback is that the enum reference document =
backpedals
a
>> >>>> bit and will take longer to complete. =A0A benefit is that this =
method
>> >>>> of referencing enumeration identifier formats can be reused by =
other
>> >>>> efforts (I'm confident that SACM could make use of the draft if =
we
change
>> >>> it, for example).
>> >>>>
>> >>>> What are your thoughts/reactions to this proposal?
>> >>>>
>> >>>> Regards,
>> >>>>
>> >>>> Adam
>> >>>>
>> >>>> _______________________________________________
>> >>>> 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



--=A0
--
Takeshi Takahashi, Ph.D.
+81 80 3490 2971
http://www.taketaka.com/
=A0


From nobody Tue Oct 21 19:35:35 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 41CAC1A8A48 for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 19:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.298
X-Spam-Level: ***
X-Spam-Status: No, score=3.298 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 rSxL79nQgTq6 for <mile@ietfa.amsl.com>; Tue, 21 Oct 2014 19:35:29 -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 D475B1A8A3E for <mile@ietf.org>; Tue, 21 Oct 2014 19:35:28 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id s9M2ZK1e020108; Wed, 22 Oct 2014 11:35:21 +0900 (JST)
Received: from mail1.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp  with ESMTP id s9M2ZKAK024093; Wed, 22 Oct 2014 11:35:20 +0900 (JST)
Received: from mail1.nict.go.jp (localhost [127.0.0.1]) by mail1.nict.go.jp (NICT Mail) with ESMTP id AAFF6167FC; Wed, 22 Oct 2014 11:35:20 +0900 (JST)
Received: from VAIO (unknown [133.243.119.70]) by mail1.nict.go.jp (NICT Mail) with ESMTP id A174A167AE; Wed, 22 Oct 2014 11:35:20 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: 
In-Reply-To: 
Date: Wed, 22 Oct 2014 11:35:20 +0900
Message-ID: <004501cfeda0$d2dfb420$789f1c60$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac/tm0fv5aT3UNCbQ5+ki0ti6TjngAABFaMQ
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/NqwJS5-nPag-RN3sKsgitc7ajMg
Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
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, 22 Oct 2014 02:35:33 -0000

Ah, sorry, I have found the Apssdir review result against the v08 =
version.
http://www.ietf.org/mail-archive/web/mile/current/msg01522.html

My concern was also addressed there, so please ignore my previous email.
I am sorry for that.

Take


> -----Original Message-----
> From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
> Sent: Wednesday, October 22, 2014 10:57 AM
> To: 'mile@ietf.org'
> Cc: Adam W. Montville (adam.w.montville@gmail.com); Black, David
> (david.black@emc.com)
> Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
>=20
> Hello Adam, David, and all,
>=20
> I agree with the direction you have developed (developing separate =
schema
> would be a good idea.) I apologize my late response.
>=20
> I can see several supportive comments on this draft change, and I can =
see
> no negative comments on this.
> So, I believe the community is happy to develop the draft to the =
direction
> the authors did.
>=20
> The last concern is the schema, IMHO.
> We have already asked App area experts to review the newly changed =
schema,
> but I think we have not received clear confirmation yet.
>=20
> At the same time, I myself have a concern on the schema since it does =
not
> extend any of the IODEF-related classes.
> IODEF extension works usually extends extending IODEF ciass, so I =
wonder
> whether the current schema of the enum draft is ok or not.
>=20
> It could be that we cannot embed the ReferenceName element inside =
IODEF's
> Reference class if we use the current schema.
> I might be wrong, so confirmation would be appreciated.
> One way I would think is extending the existing IODEF's Reference =
class.
>=20
> Take
>=20
>=20
>=20
> 2014-08-19 2:27 GMT+09:00 Black, David <david.black@emc.com>:
> > On XML snippet vs. schema:
> >
> >> If we encourage pasting the above [XML snippet] into other schemas,
> >> is there then a policing effort to ensure that documentation
> >> references are correct and that the schema is correct? =A0It seems
> >> better for wider adoption to go with the inbuilt XML constructs of
> >> namespaces to allow IODEFv2 to simply reference an enum ref =
namespace
> >> at the appropriate location, then define the enum ref schema once,
> >> which will be associated with just one document detailing the IANA
> >> registry and the expert review, etc.
> >
> > Well, the IANA registry and its associated review procedures get
> > defined once in one document, independent of what we do.
> >
> > OTOH, the namespace separation and related discipline of using a
> > separate schema for the enumeration references are useful and the
> proverbial "right thing to do,"
> > plus Roman's provided much (if not all of the text) needed, so I'm
> > fine with that approach.
> >
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Adam W. Montville [mailto:adam.w.montville@gmail.com]
> >> Sent: Wednesday, August 06, 2014 11:00 AM
> >> To: Black, David
> >> Cc: Roman D. Danyliw; MILE IETF
> >> Subject: Re: [mile] EnumRef Format to IODEF Extension Suggestion
> >>
> >>
> >> On Aug 5, 2014, at 6:28 PM, Black, David <david.black@emc.com> =
wrote:
> >>
> >> > Hello Roman,
> >> >
> >> > This is helpful (thanks):
> >> >
> >> >> I hadn't been thinking along these lines. =A0To use a software
> >> >> analogy, I didn't envision that we'd back-port the fix to a =
legacy
> >> >> version of the software (IODEFv1, RFC 5070). =A0Instead I =
figured we
> >> >> should make a library (an iodef enum extension) that the new
> >> >> version (IODEF v2, 5070bis) and alternate software (SACM) could
> >> >> use. =A0My thinking was if v1 is broken, upgrade to v2, not =
v1.01.
> >> >
> >> > Well, the current draft is an incompatible back-port because it
> >> > updates the IODEFv1 schema version to "1.01". =A0I understand =
both
> >> > you and Panos to be characterizing that as a bad idea (on which I
> >> > defer to your expertise), so I'd like to explore alternatives.
> >> >
> >> > My next question is "what sort of library?". =A0The email below
> >> > proposes what is effectively a reusable XML (sub-schema) that can
> >> > be included in other XML schemas.
> >> >
> >> > I wonder whether instead of supplying the (sub-)schema as a
> >> > "library" that can be used at runtime, can we supply the XML =
schema
> >> > snippet for enum reference formats for use in XML schema design =
along
> with the IANA registry.
> >> >
> >> > One more question:
> >> >
> >> > Is there a case to be made for use of the same XML (sub-)schema
> >> > (iodef-enum
> >> > below) in multiple containing schemas, e.g., IODEFv2, SACM, etc.,
> >> > or is it sufficient to use the same XML syntax to represent the
> enumeration values?
> >> >
> >> > For "same XML syntax", the draft could recommend that anyone who
> >> > wants to use an enumeration reference value put the following XML
> snippet in their schema:
> >> >
> >> > =A0 =A0 =A0<xs:element name=3D"SpecReferenceName">
> >> > =A0 =A0 =A0 <xs:complexType>
> >> > =A0 =A0 =A0 <xs:sequence>
> >> > =A0 =A0 =A0 =A0 <xs:element name=3D"ID" type=3D"xs:NCName"/>
> >> > =A0 =A0 =A0 </xs:sequence>
> >> > =A0 =A0 =A0 <xs:attribute name=3D"specIndex" type=3D"xs:integer"
> >> > use=3D"required"/>
> >> > =A0 =A0 =A0 </xs:complexType>
> >> > =A0 =A0 =A0</xs:element>
> >> >
> >> > [NB: I changed "ReferenceName" to "SpecReferenceName" with the
> >> > intent of enabling use of an unconstrained "ReferenceName" =
element
> >> > for other
> >> purposes.]
> >> >
> >> > The enum-reference-format draft could further recommend that
> >> > documentation of any schema that includes that snippet include a
> >> > reference to the IANA registry (created by the
> >> > enum-reference-format draft) that defines the specIndex values.
> >> >
> >> > That ought to simplify adding this to the IODEFv2 (5070bis) =
schema.
> >> >
> >> > Thoughts?
> >>
> >> If we encourage pasting the above into other schemas, is there then =
a
> >> policing effort to ensure that documentation references are correct
> >> and that the schema is correct? =A0It seems better for wider =
adoption
> >> to go with the inbuilt XML constructs of namespaces to allow =
IODEFv2
> >> to simply reference an enum ref namespace at the appropriate
> >> location, then define the enum ref schema once, which will be
> >> associated with just one document detailing the IANA registry and =
the
> expert review, etc.
> >>
> >>
> >> >
> >> > Thanks,
> >> > --David
> >> >
> >> >
> >> >> -----Original Message-----
> >> >> From: Roman D. Danyliw [mailto:rdd@cert.org]
> >> >> Sent: Thursday, July 31, 2014 3:34 PM
> >> >> To: Black, David; MILE IETF
> >> >> Subject: RE: [mile] EnumRef Format to IODEF Extension Suggestion
> >> >>
> >> >> Hello David!
> >> >>
> >> >>> -----Original Message-----
> >> >>> From: Black, David [mailto:david.black@emc.com]
> >> >>> Sent: Sunday, July 27, 2014 1:47 PM
> >> >>> To: Roman D. Danyliw; MILE IETF
> >> >>> Cc: Black, David
> >> >>> Subject: RE: [mile] EnumRef Format to IODEF Extension =
Suggestion
> >> >>>
> >> >>> Hello Roman,
> >> >>>
> >> >>> This approach is interesting, although it looks like it would
> >> >>> still
> >> require
> >> >> a
> >> >>> change to the IODEF Schema version. =A0I wonder whether we can =
go
> >> >>> further than arrange for the 5070bis draft to contain the only
> >> >>> new version of the IODEF schema beyond RFC 5070. =A0Towards =
that
> >> >>> end, I have a couple of
> >> >>> questions:
> >> >>
> >> >> I hadn't been thinking along these lines. =A0To use a software
> >> >> analogy, I
> >> didn't
> >> >> envision that we'd back-port the fix to a legacy version of the
> >> >> software (IODEFv1, RFC 5070). =A0Instead I figured we should =
make a
> >> >> library (an iodef enum extension) that the new version (IODEF =
v2,
> >> >> 5070bis) and alternate software (SACM) could use. =A0My thinking =
was
> >> >> if v1 is broken, upgrade to v2, not v1.01.
> >> >>
> >> >>> (1) Could the SpecIndex attribute be added to the ReferenceName
> >> >>> class in the IODEF v2 schema in 5070bis, as an optional
> >> >>> attribute? =A0My thinking is
> >> >> that
> >> >>> having this new attribute be optional allows the IODEF v2
> >> >>> Reference class
> >> to
> >> >>> continue to be used for everything that it's used for in IODEF
> >> >>> v1, but
> >> when
> >> >>> the SpecIndex attribute is present, it constrains the
> >> >>> ReferenceName to follow the format in the enumeration reference
> >> >>> draft - the latter requirement would be imposed by additional =
text
> in the 5070bis draft.
> >> >>
> >> >> That does provide maximum flexibility. =A0The thinking would be =
if
> >> >> you see
> >> the
> >> >> SpecIndex reference the enum draft to understand the semantics.
> >> >> If there
> >> is
> >> >> not SpecIndex reference 5070. =A0This switch could also be =
handle
> >> >> with namespaces by defining a schema of "choice (
> >> >> iodef-1.0:Reference, iodef- enum:Reference)".
> >> >>
> >> >> We have to decide whether to specify a stand-alone schema, an
> >> >> IODEF
> >> extension,
> >> >> or both? =A0Would SACM only use the newer SpecIndex-based =
Reference
> class?
> >> >>
> >> >> I feel that the implementers need to tell us how much backward
> >> compatibility
> >> >> needs to be maintained. =A0We've already broken compatibility in
> >> >> 5070bis on Node/Name, Node/DateTime, and Service@ip_protocol. =
=A0My
> >> >> feeling is that we should break it here again and force the "new
> improved" Reference in v2.
> >> >> Perhaps we can add some escape value into SpecIndex to make the
> >> >> new ReferenceName/ID behave like a Description class.
> >> >>
> >> >>> (2) The Reference class in the IODEF v1 schema (RFC 5070) is =
not
> >> extensible
> >> >> in
> >> >>> that schema, but that Reference class is contained in the =
Method
> >> >>> class
> >> which
> >> >>> can be extended via use of the (optional) AdditionalData class.
> >> >>> Is there
> >> a
> >> >>> reasonably acceptable/usable approach to use of AdditionalData
> >> >>> with Method to pull the enumeration references into IODEF v1
> >> >>> without creating a new schema version, or is this just asking =
for
> confusion?
> >> >>
> >> >> If the enum draft was published to include an iodef extension no
> >> >> change at would be required to RFC5070. =A0An implementer would
> >> >> simply drop in the enum extension into Method/AdditionalData. =
=A0The
> >> >> only challenge would be that a Reference or Description child
> >> >> class are required. =A0Therefore to use AdditionalData you would
> >> >> have to "<Method><Description/><AdditionalData
> >> >> ...></Method>".
> >> >>
> >> >> Roman
> >> >>
> >> >>>> -----Original Message-----
> >> >>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman =
D.
> >> >>>> Danyliw
> >> >>>> Sent: Friday, July 25, 2014 10:51 PM
> >> >>>> To: 'Adam W. Montville'; MILE IETF
> >> >>>> Subject: Re: [mile] EnumRef Format to IODEF Extension =
Suggestion
> >> >>>>
> >> >>>> Hello!
> >> >>>>
> >> >>>> To be more specific about what was proposed at IETF 90, please
> >> >>>> find inline a rough draft of modifications agathe -07 draft.
> >> >>>> Beyond the boiler-plate, only sections with modified text are
> listed.
> >> >>>>
> >> >>>> ---[ snip ]--
> >> >>>>
> >> >>>> MILE Working
> Group =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0A.
> >> >>>> Montville
> Internet-Draft
> >> >>>> Tripwire
> >> >>>>
> Obsoletes:
> >> >>>> D. Black Intended status: Standards
> Track
> >> >>>> EMC
> >> >>>> Expires: January 31, 2015
> >> >>>> August 2014
> >> >>>>
> >> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 IODEF Enumeration =
Reference Format
> >> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =
=A0draft-ietf-mile-enum-reference-format-07-bis
> >> >>>>
> >> >>>> Abstract
> >> >>>>
> >> >>>> =A0 [Keep first paragraph]
> >> >>>>
> >> >>>> =A0 [Modified second paragraph] This memo provides an =
extension to
> >> >>>> RFC
> >> >>>> =A0 5070 to include both the external specification and =
specific
> >> >>>> =A0 enumeration value in the IODEF Reference class. =A0This =
memo
> >> >>>> also
> >> >>>> =A0 establishes an IANA registry to manage external =
enumeration
> >> >>>> =A0 specifications for use by IODEF.
> >> >>>>
> >> >>>> =A0 The IETF has been notified of intellectual property rights
> >> >>>> claimed in
> >> >>>> =A0 regard to some or all of the specification contained in =
this
> >> >>>> =A0 document. =A0For more information consult the online list =
of
> >> >>>> claimed
> >> >>>> =A0 rights.
> >> >>>>
> >> >>>> Status of this Memo
> >> >>>>
> >> >>>> =A0 This Internet-Draft is submitted in full conformance with =
the
> >> >>>> =A0 provisions of BCP 78 and BCP 79.
> >> >>>>
> >> >>>> =A0 Internet-Drafts are working documents of the Internet
> >> >>>> Engineering
> >> >>>> =A0 Task Force (IETF). =A0Note that other groups may also =
distribute
> >> >>>> =A0 working documents as Internet-Drafts. =A0The list of =
current
> >> >>>> Internet-
> >> >>>> =A0 Drafts is at http://datatracker.ietf.org/drafts/current/.
> >> >>>>
> >> >>>> =A0 Internet-Drafts are draft documents valid for a maximum of =
six
> >> >>>> months
> >> >>>> =A0 and may be updated, replaced, or obsoleted by other =
documents
> >> >>>> at any
> >> >>>> =A0 time. =A0It is inappropriate to use Internet-Drafts as =
reference
> >> >>>> =A0 material or to cite them other than as "work in progress."
> >> >>>>
> >> >>>> =A0 This Internet-Draft will expire on January 31, 2015.
> >> >>>>
> >> >>>> Copyright Notice
> >> >>>>
> >> >>>> =A0 Copyright (c) 2014 IETF Trust and the persons identified =
as
> >> >>>> the
> >> >>>> =A0 document authors. =A0All rights reserved.
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015
> >> >>>> [Page 1]
> >> >>>>
> >> >>>>
> >> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM
> >> >>>> August 2014
> >> >>>>
> >> >>>>
> >> >>>> =A0 This document is subject to BCP 78 and the IETF Trust's =
Legal
> >> >>>> =A0 Provisions Relating to IETF Documents
> >> >>>> (http://trustee.ietf.org/
> >> >>>> =A0 license-info) in effect on the date of publication of this
> document.
> >> >>>> =A0 Please review these documents carefully, as they describe =
your
> >> >>>> rights
> >> >>>> =A0 and restrictions with respect to this document. =A0Code
> >> >>>> Components
> >> >>>> =A0 extracted from this document must include Simplified BSD
> >> >>>> License text
> >> >>>> =A0 as described in Section 4.e of the Trust Legal Provisions =
and
> >> >>>> are
> >> >>>> =A0 provided without warranty as described in the Simplified =
BSD
> License.
> >> >>>>
> >> >>>> =A0 This document may contain material from IETF Documents or =
IETF
> >> >>>> =A0 Contributions published or made publicly available before
> >> >>>> November
> >> >>>> =A0 10, 2008. =A0The person(s) controlling the copyright in =
some of
> >> >>>> this
> >> >>>> =A0 material may not have granted the IETF Trust the right to
> >> >>>> allow
> >> >>>> =A0 modifications of such material outside the IETF Standards
> Process.
> >> >>>> =A0 Without obtaining an adequate license from the person(s)
> >> >>>> controlling
> >> >>>> =A0 the copyright in such materials, this document may not be
> >> >>>> modified
> >> >>>> =A0 outside the IETF Standards Process, and derivative works =
of it
> >> >>>> may
> >> >>>> =A0 not be created outside the IETF Standards Process, except =
to
> >> >>>> format
> >> >>>> =A0 it for publication as an RFC or to translate it into =
languages
> >> >>>> other
> >> >>>> =A0 than English.
> >> >>>>
> >> >>>> Table of Contents
> >> >>>>
> >> >>>> =A0 1. =A0Introduction . . . . . . . . . . . . . . . . . . . . =
. . .
> >> >>>> . . =A02
> >> >>>> =A0 =A0 1.1. =A0Terminology =A0. . . . . . . . . . . . . . . . =
. . . . .
> >> >>>> . . =A02
> >> >>>> =A0 2. =A0Referencing External Enumerations =A0. . . . . . . . =
. . . .
> >> >>>> . . =A02
> >> >>>> =A0 =A0 2.1. =A0ReferenceName Class =A0. . . . . . . . . . . . =
. . . . .
> >> >>>> . . =A02
> >> >>>> =A0 =A0 2.2. =A0Reference Method Applicability . . . . . . . . =
. . . .
> >> >>>> . . =A03
> >> >>>> =A0 3. =A0Security Considerations =A0. . . . . . . . . . . . . =
. . . .
> >> >>>> . . =A03
> >> >>>> =A0 4. =A0IANA Considerations =A0. . . . . . . . . . . . . . . =
. . . .
> >> >>>> . . =A04
> >> >>>> =A0 5. =A0The ReferenceName Schema . . . . . . . . . . . . . . =
. . .
> >> >>>> . . =A04
> >> >>>> =A0 6. =A0References . . . . . . . . . . . . . . . . . . . . . =
. . .
> >> >>>> . . =A05
> >> >>>> =A0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . =
. . .
.
> >> >>>> 5
> >> >>>>
> >> >>>> 1. =A0Introduction
> >> >>>>
> >> >>>> =A0 No change.
> >> >>>>
> >> >>>> 1.1. =A0Terminology
> >> >>>>
> >> >>>> =A0 No change.
> >> >>>>
> >> >>>> 2. =A0Referencing External Enumerations
> >> >>>>
> >> >>>> =A0 No change.
> >> >>>>
> >> >>>> 2.1. =A0ReferenceName Class
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015
> >> >>>> [Page 2]
> >> >>>>
> >> >>>>
> >> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM
> >> >>>> August 2014
> >> >>>>
> >> >>>>
> >> >>>> =A0 The ReferenceName class provides the XML representation =
for
> >> >>>> =A0 identifying an enumeration and specifying a value from it. =
=A0A
> >> >>>> given
> >> >>>> =A0 enumeration is uniquely identified by the specIndex =
attribute.
> >> >>>> Each
> >> >>>> =A0 specIndex value corresponds to an entry in the =
"Enumeration
> >> >>>> Reference
> >> >>>> =A0 Type Identifiers" IANA registry (see Section 4). =A0The =
child ID
> >> >>>> =A0 element represents a particular value from the =
corresponding
> >> >>>> =A0 enumeration identified by the specIndex attribute. =A0The =
format
> >> >>>> of the
> >> >>>> =A0 ID element is described in the IANA registry entry of the
> >> >>>> =A0 enumeration.
> >> >>>>
> >> >>>> =A0 +-------------------------+
> >> >>>> =A0 | ReferenceName =A0 =A0 =A0 =A0 =A0 |
> >> >>>> =A0 +-------------------------+
> >> >>>> =A0 | INTEGER specIndex =A0 =A0 =A0 |<>----------[ ID =A0 =A0]
> >> >>>> =A0 +-------------------------+
> >> >>>>
> >> >>>> =A0 The aggregate classes that constitute ReferenceName:
> >> >>>>
> >> >>>> =A0 ID
> >> >>>> =A0 =A0 =A0One. =A0ID. =A0Name of the reference.
> >> >>>>
> >> >>>> =A0 The ReferenceName class has 1 attribute.
> >> >>>>
> >> >>>> =A0 specIndex
> >> >>>> =A0 =A0 =A0Required. =A0INTEGER. =A0Enumeration identifier. =
=A0This value
> >> >>>> =A0 =A0 =A0corresponds to an entry in the =A0"Enumeration =
Reference Type
> >> >>>> =A0 =A0 =A0Identifiers" IANA registry with an identical =
SpecIndex value.
> >> >>>>
> >> >>>> =A0 An example of such a reference is as follows:
> >> >>>>
> >> >>>> =A0 =A0 =A0<iodef:Reference>
> >> >>>> =A0 =A0 =A0 =A0 <iodef-enum:ReferenceName specIndex=3D"1">
> >> >>>> =A0 =A0 =A0 =A0 =A0 =
=A0<iodef-enum:ID>CXI-1234-XYZ</iodef-enum:ID>
> >> >>>> =A0 =A0 =A0 =A0 </iodef-enum:ReferenceName>
> >> >>>> =A0 =A0 =A0 =A0 <iodef:URL>http://cxi.example.com</iodef:URL>
> >> >>>> =A0 =A0 =A0 =A0 <iodef:Description>Foo</iodef:Description>
> >> >>>> =A0 =A0 =A0</iodef:Reference>
> >> >>>>
> >> >>>> =A0 The corresponding information in the IANA table (see =
Section
> >> >>>> 4) would
> >> >>>> =A0 include:
> >> >>>>
> >> >>>> =A0 =A0 =A0Full Name: Concept X Identifier
> >> >>>> =A0 =A0 =A0SpecIndex: 1
> >> >>>> =A0 =A0 =A0Version: any
> >> >>>> =A0 =A0 =A0Specification URI: http://cxi.example.com/spec_url
> >> >>>>
> >> >>>> 2.2. =A0Reference Method Applicability
> >> >>>>
> >> >>>> =A0 No change, but this should should be numbered 2.2 not 2.3 =
as
> >> >>>> in the
> >> >>>> =A0 -07 draft.
> >> >>>>
> >> >>>> 3. =A0Security Considerations
> >> >>>>
> >> >>>>
> >> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015
> >> >>>> [Page 3]
> >> >>>>
> >> >>>>
> >> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM
> >> >>>> August 2014
> >> >>>>
> >> >>>>
> >> >>>> =A0 No change.
> >> >>>>
> >> >>>> 4. =A0IANA Considerations
> >> >>>>
> >> >>>> =A0 [after the existing text, the following should be added =
...]
> >> >>>>
> >> >>>> =A0 This document uses URNs to describe XML namespaces and XML
> >> >>>> schemas
> >> >>>> =A0 conforming to a registry mechanism described in [RFC3688].
> >> >>>>
> >> >>>> =A0 Registration request for the IODEF enumeration reference
> >> >>>> format
> >> >>>> =A0 namespace:
> >> >>>>
> >> >>>> =A0 URI : urn:ietf:params:xml:ns:iodef-enum-1.0
> >> >>>>
> >> >>>> =A0 Registrant Contact : See the "Authors' Addresses" section =
of
> >> >>>> this
> >> >>>> =A0 =A0 =A0document.
> >> >>>>
> >> >>>> =A0 XML : None.
> >> >>>>
> >> >>>> =A0 Registration request for the IODEF enumeration reference
> >> >>>> format XML
> >> >>>> =A0 schema:
> >> >>>>
> >> >>>> =A0 URI : urn:ietf:params:xml:schema:iodef-enum-1.0
> >> >>>>
> >> >>>> =A0 Registrant Contact See the "Authors' Addresses" section of
> >> >>>> this
> >> >>>> =A0 =A0 =A0document.
> >> >>>>
> >> >>>> =A0 XML : See Section 6, "XML Schema", of this =A0 =
=A0document.
> >> >>>>
> >> >>>> 5. =A0The ReferenceName Schema
> >> >>>>
> >> >>>> =A0 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> >> >>>> =A0 <xs:schema attributeFormDefault=3D"unqualified"
> >> >>>> =A0 =A0 =A0 =A0 =A0elementFormDefault=3D"qualified"
> >>
> >>>> =A0 =A0 =A0 =A0 =
=A0targetNamespace=3D"urn:ietf:params:xml:ns:iodef-enum-1.0"
> >> >>>> =A0 =A0 =A0 =A0 =
=A0xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
> >> >>>> =A0 =A0 =A0 =A0 =
=A0xmlns:enum=3D"urn:ietf:params:xml:ns:iodef-enum-1.0">
> >> >>>>
> >> >>>> =A0 =A0 <!--
> >> >>>>
> >> >>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >>>> =A0 =A0 =3D=3D=3D =A0ReferenceName =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D=3D=3D
> >> >>>>
> >> >>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> >> >>>> =A0 =A0 =A0-->
> >> >>>> =A0 =A0 <xs:element name=3D"ReferenceName">
> >> >>>> =A0 =A0 =A0 <xs:complexType>
> >> >>>> =A0 =A0 =A0 =A0 <xs:sequence>
> >> >>>> =A0 =A0 =A0 =A0 =A0 <xs:element name=3D"ID" =
type=3D"xs:NCName"/>
> >> >>>> =A0 =A0 =A0 =A0 </xs:sequence>
> >> >>>> =A0 =A0 =A0 =A0 <xs:attribute name=3D"specIndex"
> >> >>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
type=3D"xs:integer" use=3D"required"/>
> >> >>>> =A0 =A0 =A0 </xs:complexType>
> >> >>>> =A0 =A0 </xs:element>
> >> >>>> =A0 </xs:schema>
> >> >>>>
> >> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015
> >> >>>> [Page 4]
> >> >>>>
> >> >>>>
> >> >>>> Internet-Draft =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0IODEFv2 ENUM
> >> >>>> August 2014
> >> >>>>
> >> >>>>
> >> >>>> 6. =A0References
> >> >>>>
> >> >>>> Authors' Addresses
> >> >>>>
> >> >>>> =A0 Adam W. Montville
> >> >>>> =A0 Tripwire
> >> >>>> =A0 USA
> >> >>>>
> >> >>>> =A0 Email: Adam's email
> >> >>>>
> >> >>>>
> >> >>>> =A0 David Black
> >> >>>> =A0 EMC
> >> >>>> =A0 USA
> >> >>>>
> >> >>>> =A0 Email: David's email
> >> >>>>
> >> >>>>
> >> >>>> Montville & Black =A0 =A0 =A0 Expires January 31, 2015
> >> >>>> [Page 5]
> >> >>>>
> >> >>>> --[ end ]--
> >> >>>>
> >> >>>> Roman
> >> >>>>
> >> >>>> -----Original Message-----
> >> >>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam W.
> >> >>>> Montville
> >> >>>> Sent: Friday, July 25, 2014 7:30 AM
> >> >>>> To: MILE IETF
> >> >>>> Subject: [mile] EnumRef Format to IODEF Extension Suggestion
> >> >>>>
> >> >>>> Hello,
> >> >>>>
> >> >>>> During MILE's session this week at IETF 90, Roman suggested =
that
> >> >>>> the enum reference format be changed from an update to 5070 to
> >> >>>> an IODEF
> >> >>> extension.
> >> >>>> This would require that the enum reference format draft be
> >> >>>> updated accordingly and that a full schema and namespace be
> >> >>>> considered for the format itself, rather than simply updating =
the
> IODEF schema.
> >> >>>>
> >> >>>> The obvious drawback is that the enum reference document
> >> >>>> backpedals a bit and will take longer to complete. =A0A =
benefit is
> >> >>>> that this method of referencing enumeration identifier formats
> >> >>>> can be reused by other efforts (I'm confident that SACM could
> >> >>>> make use of the draft if we change
> >> >>> it, for example).
> >> >>>>
> >> >>>> What are your thoughts/reactions to this proposal?
> >> >>>>
> >> >>>> Regards,
> >> >>>>
> >> >>>> Adam
> >> >>>>
> >> >>>> _______________________________________________
> >> >>>> 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
>=20
>=20
> --
> --
> Takeshi Takahashi, Ph.D.
> +81 80 3490 2971
> http://www.taketaka.com/
>=20


From nobody Thu Oct 23 17:12:01 2014
Return-Path: <daisu-mi@nc.u-tokyo.ac.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 381001AD5A9 for <mile@ietfa.amsl.com>; Thu, 23 Oct 2014 17:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.899
X-Spam-Level: ***
X-Spam-Status: No, score=3.899 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_64=0.6, T_RP_MATCHES_RCVD=-0.01] 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 MUhA8GmL7mDS for <mile@ietfa.amsl.com>; Thu, 23 Oct 2014 17:11:52 -0700 (PDT)
Received: from skyblue2.nc.u-tokyo.ac.jp (skyblue2.nc.u-tokyo.ac.jp [133.11.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id 3D4A61AD59F for <mile@ietf.org>; Thu, 23 Oct 2014 17:11:52 -0700 (PDT)
Received: from [IPv6:2001:200:180:299:ec25:8c2d:5994:9928] (unknown [IPv6:2001:200:180:299:ec25:8c2d:5994:9928]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by skyblue2.nc.u-tokyo.ac.jp (Postfix) with ESMTPSA id 8E519B6A10DC; Fri, 24 Oct 2014 09:11:51 +0900 (JST)
Message-ID: <54499958.60908@nc.u-tokyo.ac.jp>
Date: Fri, 24 Oct 2014 09:12:08 +0900
From: Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Roman D. Danyliw" <rdd@cert.org>,  'Lagadec Philippe' <Philippe.Lagadec@ncia.nato.int>, "mile@ietf.org" <mile@ietf.org>
References: <1ce5bf83715a4d32b002de0d942d1222@nrnciex1011.NR.NC3A> <359EC4B99E040048A7131E0F4E113AFCA4235131@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCA4235131@marathon>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/7OG5wCnSaLMeuwRj0BA2q4EOnN4
Subject: Re: [mile] IODEFv2 suggestions
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, 24 Oct 2014 00:11:57 -0000

Hello,

  From July, my university's incident management system supports 
IODEFv1. (Thank all of you joined the discussion!)

  Currently, outputting my internal data records to IODEF works well. 
But, when I tried to import IODEFv1 request/response into my 
university's system, it found some difficulty that Legadec and Roman 
pointed as follows.

On 2014/07/30 11:19, Roman D. Danyliw wrote:
>> 16. Last but not least, IODEFv1 does not provide a native way to specify the
>> incident type. We can use Impact.type to describe the type of impact, but
>> that is different from the type of the incident itself. For example a denial of
>> service can be caused by different types of incidents (e.g. a DDoS, the
>> exploitation of a vulnerability, a worm, a surge in legitimate requests, a
>> physical outage, a unhandled bug, etc).
>> Even if it is hard to find a proper/generic way to categorize incidents that
>> everybody agrees upon, I think it would be good to add an attribute with an
>> enumeration for it in the Incident class.
>> Potential sources of inspiration:
>> https://www.us-cert.gov/government-users/reporting-requirements
>> http://veriscommunity.net/enums.html#section-actions
>> https://alienvault.bloomfire.com/posts/653702-open-source-security-event-
>> taxonomy/public
>> https://capec.mitre.org/about/index.html (although this might be too
>> detailed) And surely many others.
>> I think it should be possible to assign several categories to an incident,
>> because it is often a combination of several types (e.g. malware and social
>> engineering).
>
> Agreed.  Issue #46, sub-bullet #2 is tracking that some approach to categorize the incidents is necessary.  Your point is well taken that whatever taxonomy or free-form approach that is taken, multiple categories for a given incident should be possible.

　I welcome "Incident type" in IODEFv2, but the enumeration of
the type would be difficult by following reasons.
　(1) the number of type is still increasing.
   (2) variety of the existing types.
    - JPCERT/CC uses phishing, web hijack, malware propagation, scan,
      DoS/DDoS, control system, and other.
    - My univ.’s CERT also needs “spam” for containing spam senders
      as well as JPCERT/CC’s category.
    - Other CERT in different country may use different category.
      For instance, CNCERT may use phishing, DoS, Abnormal domain,
      Defacement, Backdoor, Malware, and Vulnerability.
    - In short, there are much variations.

  Regardless of the enumeration, "Incident type" field is useful.
  Not only for my CERT, but many CERT usually publish periodical 
incident status reports, so this field is useful for statistical
aspect.

  Instead of "Incident type", multiple selections of "Impact type"
is also helpful for us. In such case, I will use "ext-value"
for recording specific incident type as follows.

  <Assessment>
   <Impact type="file" completion="succeeded" />
   <Impact type="ext-value" ext-type="web-hijack-jpcert">
  </Assessment>

Kind regards,
Daisuke


From nobody Fri Oct 24 00:24:21 2014
Return-Path: <Philippe.Lagadec@ncia.nato.int>
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 6089C1AD6C9 for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 00:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level: 
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 iW7KcaFW1gv7 for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 00:24:15 -0700 (PDT)
Received: from nudmzsv0007.nc3a.nato.int (nudmzsv0007.nc3a.nato.int [192.41.140.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83E0A1A19F6 for <mile@ietf.org>; Fri, 24 Oct 2014 00:24:14 -0700 (PDT)
Received: from NUMIMESWEEPER.nu.nc3a (numimesweeper [192.168.1.100]) by nudmzsv0007.nc3a.nato.int (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s9O7MsPL016942 for <mile@ietf.org>; Fri, 24 Oct 2014 09:22:54 +0200
Received: from NRNC3EX1001.NR.NC3A (nrnc3ex1001.nr.nc3a) by NUMIMESWEEPER.nu.nc3a (Clearswift SMTPRS 5.4.0) with ESMTP id <Tb64de0c162c0a801641af8@NUMIMESWEEPER.nu.nc3a>;  Fri, 24 Oct 2014 09:23:43 +0200
Received: from NRNCIEX1011.NR.NC3A (172.31.4.7) by NRNC3EX1001.NR.NC3A (172.31.4.11) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 24 Oct 2014 09:23:12 +0200
Received: from NRNCIEX1011.NR.NC3A (2001:67c:1a11:4:c86d:f66e:3d3:2cc0) by nrnciex1011.NR.NC3A (2001:67c:1a11:4:c86d:f66e:3d3:2cc0) with Microsoft SMTP Server (TLS) id 15.0.913.22; Fri, 24 Oct 2014 09:22:53 +0200
Received: from NRNCIEX1011.NR.NC3A ([fe80::c86d:f66e:3d3:2cc0]) by nrnciex1011.NR.NC3A ([fe80::c86d:f66e:3d3:2cc0%12]) with mapi id 15.00.0913.011; Fri, 24 Oct 2014 09:22:35 +0200
From: Lagadec Philippe <Philippe.Lagadec@ncia.nato.int>
To: Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>, "Roman D. Danyliw" <rdd@cert.org>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] IODEFv2 suggestions
Thread-Index: Ac+n0pj8F6aqQ2TjTeq9PSi8uTdtvADYo/1AEPZOagAAEsXiYA==
Date: Fri, 24 Oct 2014 07:22:35 +0000
Message-ID: <b24bc743e7ef491e8211a03c981e934d@nrnciex1011.NR.NC3A>
References: <1ce5bf83715a4d32b002de0d942d1222@nrnciex1011.NR.NC3A> <359EC4B99E040048A7131E0F4E113AFCA4235131@marathon> <54499958.60908@nc.u-tokyo.ac.jp>
In-Reply-To: <54499958.60908@nc.u-tokyo.ac.jp>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:67c:1a11:4:811b:90a5:9a:592a]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/aOTXoOhhw0e7XF9FllncmMIJHr4
Subject: Re: [mile] IODEFv2 suggestions
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, 24 Oct 2014 07:24:19 -0000

SGVsbG8gRGFpc3VrZSBhbmQgUm9tYW4sDQoNClNpbmNlIG15IGluaXRpYWwgbWVzc2FnZSBJIGhh
dmUgYmVlbiB3b3JraW5nIG9uIGEgbGlzdCBvZiBpbmNpZGVudCBjYXRlZ29yaWVzLCBjb21waWxl
ZCBmcm9tIHNldmVyYWwgc291cmNlcyBhbmQgc3RhbmRhcmRzLiBJIHBsYW4gdG8gbWFrZSBhIHBy
b3Bvc2FsIGZvciBJT0RFRnYyIHNvb24uDQpJbmRlZWQsICB0aGVyZSBhcmUgbWFueSB3YXlzIHRv
IGNhdGVnb3JpemUgaW5jaWRlbnRzIGFuZCB0ZXJtaW5vbG9neSBpcyBhbHdheXMgYW4gaXNzdWUu
IEJ1dCBpZiB3ZSB1c2UgYSBxdWl0ZSBleHRlbnNpdmUgbGlzdCBvZiBjYXRlZ29yaWVzLCBhbmQg
aWYgd2UgYWxsb3cgc2V2ZXJhbCBjYXRlZ29yaWVzIHRvIGJlIHNlbGVjdGVkIGZvciBhbiBpbmNp
ZGVudCAoaS5lLiBsaWtlIHRhZ3MgaW5zdGVhZCBvZiBleGNsdXNpdmUgY2F0ZWdvcmllcyksIHRo
ZW4gSSBiZWxpZXZlIHdlIGNhbiBjb3ZlciBtb3N0IHVzZSBjYXNlcyBpbiBhIGdlbmVyaWMgd2F5
LCBhbmQgb2J0YWluIGEgc3RydWN0dXJlZCBkZXNjcmlwdGlvbiBvZiB0aGUgbWFpbiBjaGFyYWN0
ZXJpc3RpY3Mgb2YgYW4gaW5jaWRlbnQuDQoNClRoZW4gdGhlc2UgY2F0ZWdvcmllcyBjYW4gYmUg
dXNlZCBmb3IgdmFyaW91cyB0YXNrcyBpbmNsdWRpbmc6DQotIHJlcG9ydGluZywgc3RhdGlzdGlj
cywgc2l0dWF0aW9uYWwgYXdhcmVuZXNzDQotIHN1Z2dlc3QgcG90ZW50aWFsIGluY2lkZW50IHJl
c3BvbnNlcyBmb3IgZWFjaCBjYXRlZ29yeQ0KLSBhdXRvbWF0ZSBpbXBhY3QgYW5kIHJpc2sgYXNz
ZXNzbWVudA0KDQpSZWdhcmRzLA0KDQpQaGlsaXBwZS4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCkZyb206IERhaXN1a2UgTUlZQU1PVE8gW21haWx0bzpkYWlzdS1taUBuYy51LXRva3lv
LmFjLmpwXSANClNlbnQ6IDI0IE9jdG9iZXIgMjAxNCAwMjoxMg0KVG86IFJvbWFuIEQuIERhbnls
aXc7ICdMYWdhZGVjIFBoaWxpcHBlJzsgbWlsZUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFttaWxl
XSBJT0RFRnYyIHN1Z2dlc3Rpb25zDQoNCkhlbGxvLA0KDQogIEZyb20gSnVseSwgbXkgdW5pdmVy
c2l0eSdzIGluY2lkZW50IG1hbmFnZW1lbnQgc3lzdGVtIHN1cHBvcnRzIElPREVGdjEuIChUaGFu
ayBhbGwgb2YgeW91IGpvaW5lZCB0aGUgZGlzY3Vzc2lvbiEpDQoNCiAgQ3VycmVudGx5LCBvdXRw
dXR0aW5nIG15IGludGVybmFsIGRhdGEgcmVjb3JkcyB0byBJT0RFRiB3b3JrcyB3ZWxsLiANCkJ1
dCwgd2hlbiBJIHRyaWVkIHRvIGltcG9ydCBJT0RFRnYxIHJlcXVlc3QvcmVzcG9uc2UgaW50byBt
eSB1bml2ZXJzaXR5J3Mgc3lzdGVtLCBpdCBmb3VuZCBzb21lIGRpZmZpY3VsdHkgdGhhdCBMZWdh
ZGVjIGFuZCBSb21hbiBwb2ludGVkIGFzIGZvbGxvd3MuDQoNCk9uIDIwMTQvMDcvMzAgMTE6MTks
IFJvbWFuIEQuIERhbnlsaXcgd3JvdGU6DQo+PiAxNi4gTGFzdCBidXQgbm90IGxlYXN0LCBJT0RF
RnYxIGRvZXMgbm90IHByb3ZpZGUgYSBuYXRpdmUgd2F5IHRvIA0KPj4gc3BlY2lmeSB0aGUgaW5j
aWRlbnQgdHlwZS4gV2UgY2FuIHVzZSBJbXBhY3QudHlwZSB0byBkZXNjcmliZSB0aGUgDQo+PiB0
eXBlIG9mIGltcGFjdCwgYnV0IHRoYXQgaXMgZGlmZmVyZW50IGZyb20gdGhlIHR5cGUgb2YgdGhl
IGluY2lkZW50IA0KPj4gaXRzZWxmLiBGb3IgZXhhbXBsZSBhIGRlbmlhbCBvZiBzZXJ2aWNlIGNh
biBiZSBjYXVzZWQgYnkgZGlmZmVyZW50IA0KPj4gdHlwZXMgb2YgaW5jaWRlbnRzIChlLmcuIGEg
RERvUywgdGhlIGV4cGxvaXRhdGlvbiBvZiBhIHZ1bG5lcmFiaWxpdHksIA0KPj4gYSB3b3JtLCBh
IHN1cmdlIGluIGxlZ2l0aW1hdGUgcmVxdWVzdHMsIGEgcGh5c2ljYWwgb3V0YWdlLCBhIHVuaGFu
ZGxlZCBidWcsIGV0YykuDQo+PiBFdmVuIGlmIGl0IGlzIGhhcmQgdG8gZmluZCBhIHByb3Blci9n
ZW5lcmljIHdheSB0byBjYXRlZ29yaXplIA0KPj4gaW5jaWRlbnRzIHRoYXQgZXZlcnlib2R5IGFn
cmVlcyB1cG9uLCBJIHRoaW5rIGl0IHdvdWxkIGJlIGdvb2QgdG8gYWRkIA0KPj4gYW4gYXR0cmli
dXRlIHdpdGggYW4gZW51bWVyYXRpb24gZm9yIGl0IGluIHRoZSBJbmNpZGVudCBjbGFzcy4NCj4+
IFBvdGVudGlhbCBzb3VyY2VzIG9mIGluc3BpcmF0aW9uOg0KPj4gaHR0cHM6Ly93d3cudXMtY2Vy
dC5nb3YvZ292ZXJubWVudC11c2Vycy9yZXBvcnRpbmctcmVxdWlyZW1lbnRzDQo+PiBodHRwOi8v
dmVyaXNjb21tdW5pdHkubmV0L2VudW1zLmh0bWwjc2VjdGlvbi1hY3Rpb25zDQo+PiBodHRwczov
L2FsaWVudmF1bHQuYmxvb21maXJlLmNvbS9wb3N0cy82NTM3MDItb3Blbi1zb3VyY2Utc2VjdXJp
dHktZXYNCj4+IGVudC0NCj4+IHRheG9ub215L3B1YmxpYw0KPj4gaHR0cHM6Ly9jYXBlYy5taXRy
ZS5vcmcvYWJvdXQvaW5kZXguaHRtbCAoYWx0aG91Z2ggdGhpcyBtaWdodCBiZSB0b28NCj4+IGRl
dGFpbGVkKSBBbmQgc3VyZWx5IG1hbnkgb3RoZXJzLg0KPj4gSSB0aGluayBpdCBzaG91bGQgYmUg
cG9zc2libGUgdG8gYXNzaWduIHNldmVyYWwgY2F0ZWdvcmllcyB0byBhbiANCj4+IGluY2lkZW50
LCBiZWNhdXNlIGl0IGlzIG9mdGVuIGEgY29tYmluYXRpb24gb2Ygc2V2ZXJhbCB0eXBlcyAoZS5n
LiANCj4+IG1hbHdhcmUgYW5kIHNvY2lhbCBlbmdpbmVlcmluZykuDQo+DQo+IEFncmVlZC4gIElz
c3VlICM0Niwgc3ViLWJ1bGxldCAjMiBpcyB0cmFja2luZyB0aGF0IHNvbWUgYXBwcm9hY2ggdG8g
Y2F0ZWdvcml6ZSB0aGUgaW5jaWRlbnRzIGlzIG5lY2Vzc2FyeS4gIFlvdXIgcG9pbnQgaXMgd2Vs
bCB0YWtlbiB0aGF0IHdoYXRldmVyIHRheG9ub215IG9yIGZyZWUtZm9ybSBhcHByb2FjaCB0aGF0
IGlzIHRha2VuLCBtdWx0aXBsZSBjYXRlZ29yaWVzIGZvciBhIGdpdmVuIGluY2lkZW50IHNob3Vs
ZCBiZSBwb3NzaWJsZS4NCg0K44CASSB3ZWxjb21lICJJbmNpZGVudCB0eXBlIiBpbiBJT0RFRnYy
LCBidXQgdGhlIGVudW1lcmF0aW9uIG9mIHRoZSB0eXBlIHdvdWxkIGJlIGRpZmZpY3VsdCBieSBm
b2xsb3dpbmcgcmVhc29ucy4NCuOAgCgxKSB0aGUgbnVtYmVyIG9mIHR5cGUgaXMgc3RpbGwgaW5j
cmVhc2luZy4NCiAgICgyKSB2YXJpZXR5IG9mIHRoZSBleGlzdGluZyB0eXBlcy4NCiAgICAtIEpQ
Q0VSVC9DQyB1c2VzIHBoaXNoaW5nLCB3ZWIgaGlqYWNrLCBtYWx3YXJlIHByb3BhZ2F0aW9uLCBz
Y2FuLA0KICAgICAgRG9TL0REb1MsIGNvbnRyb2wgc3lzdGVtLCBhbmQgb3RoZXIuDQogICAgLSBN
eSB1bml2LuKAmXMgQ0VSVCBhbHNvIG5lZWRzIOKAnHNwYW3igJ0gZm9yIGNvbnRhaW5pbmcgc3Bh
bSBzZW5kZXJzDQogICAgICBhcyB3ZWxsIGFzIEpQQ0VSVC9DQ+KAmXMgY2F0ZWdvcnkuDQogICAg
LSBPdGhlciBDRVJUIGluIGRpZmZlcmVudCBjb3VudHJ5IG1heSB1c2UgZGlmZmVyZW50IGNhdGVn
b3J5Lg0KICAgICAgRm9yIGluc3RhbmNlLCBDTkNFUlQgbWF5IHVzZSBwaGlzaGluZywgRG9TLCBB
Ym5vcm1hbCBkb21haW4sDQogICAgICBEZWZhY2VtZW50LCBCYWNrZG9vciwgTWFsd2FyZSwgYW5k
IFZ1bG5lcmFiaWxpdHkuDQogICAgLSBJbiBzaG9ydCwgdGhlcmUgYXJlIG11Y2ggdmFyaWF0aW9u
cy4NCg0KICBSZWdhcmRsZXNzIG9mIHRoZSBlbnVtZXJhdGlvbiwgIkluY2lkZW50IHR5cGUiIGZp
ZWxkIGlzIHVzZWZ1bC4NCiAgTm90IG9ubHkgZm9yIG15IENFUlQsIGJ1dCBtYW55IENFUlQgdXN1
YWxseSBwdWJsaXNoIHBlcmlvZGljYWwgaW5jaWRlbnQgc3RhdHVzIHJlcG9ydHMsIHNvIHRoaXMg
ZmllbGQgaXMgdXNlZnVsIGZvciBzdGF0aXN0aWNhbCBhc3BlY3QuDQoNCiAgSW5zdGVhZCBvZiAi
SW5jaWRlbnQgdHlwZSIsIG11bHRpcGxlIHNlbGVjdGlvbnMgb2YgIkltcGFjdCB0eXBlIg0KaXMg
YWxzbyBoZWxwZnVsIGZvciB1cy4gSW4gc3VjaCBjYXNlLCBJIHdpbGwgdXNlICJleHQtdmFsdWUi
DQpmb3IgcmVjb3JkaW5nIHNwZWNpZmljIGluY2lkZW50IHR5cGUgYXMgZm9sbG93cy4NCg0KICA8
QXNzZXNzbWVudD4NCiAgIDxJbXBhY3QgdHlwZT0iZmlsZSIgY29tcGxldGlvbj0ic3VjY2VlZGVk
IiAvPg0KICAgPEltcGFjdCB0eXBlPSJleHQtdmFsdWUiIGV4dC10eXBlPSJ3ZWItaGlqYWNrLWpw
Y2VydCI+DQogIDwvQXNzZXNzbWVudD4NCg0KS2luZCByZWdhcmRzLA0KRGFpc3VrZQ0K


From nobody Fri Oct 24 04:49:30 2014
Return-Path: <daisu-mi@nc.u-tokyo.ac.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 99C941A8AAB for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 04:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.199
X-Spam-Level: *
X-Spam-Status: No, score=1.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_64=0.6, T_RP_MATCHES_RCVD=-0.01] 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 Rh19wPAHIBkV for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 04:49:26 -0700 (PDT)
Received: from skyblue2.nc.u-tokyo.ac.jp (skyblue2.nc.u-tokyo.ac.jp [133.11.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2A41A8AA8 for <mile@ietf.org>; Fri, 24 Oct 2014 04:49:26 -0700 (PDT)
Received: from [IPv6:2001:200:180:299:ec25:8c2d:5994:9928] (unknown [IPv6:2001:200:180:299:ec25:8c2d:5994:9928]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by skyblue2.nc.u-tokyo.ac.jp (Postfix) with ESMTPSA id C4DA1B6A7DE1; Fri, 24 Oct 2014 20:49:25 +0900 (JST)
Message-ID: <544A3CD9.5020303@nc.u-tokyo.ac.jp>
Date: Fri, 24 Oct 2014 20:49:45 +0900
From: Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Lagadec Philippe <Philippe.Lagadec@ncia.nato.int>,  "Roman D. Danyliw" <rdd@cert.org>, "mile@ietf.org" <mile@ietf.org>
References: <1ce5bf83715a4d32b002de0d942d1222@nrnciex1011.NR.NC3A> <359EC4B99E040048A7131E0F4E113AFCA4235131@marathon> <54499958.60908@nc.u-tokyo.ac.jp> <b24bc743e7ef491e8211a03c981e934d@nrnciex1011.NR.NC3A>
In-Reply-To: <b24bc743e7ef491e8211a03c981e934d@nrnciex1011.NR.NC3A>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/Bh5tT9fWbDjfNsRABl0iC1nnpIM
Subject: Re: [mile] IODEFv2 suggestions
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, 24 Oct 2014 11:49:28 -0000

Hello Philippe and all,

  Thank you for your response. The category is useful for varous tasks, 
and I'm happy to hear your contributions for supporting it.

 > suggest potential incident responses for each category

  I concur with your opinion. It will be useful for CERT/CSIRT to 
complete incident response. I've got an idea for use of
CAPEC enumeration (along with RFC7203 format), but it was not
easy to input the values until CERT/CSIRT finished the incident
response.

Regards,
Daisuke

On 2014/10/24 16:22, Lagadec Philippe wrote:
> Hello Daisuke and Roman,
>
> Since my initial message I have been working on a list of incident categories, compiled from several sources and standards. I plan to make a proposal for IODEFv2 soon.
> Indeed,  there are many ways to categorize incidents and terminology is always an issue. But if we use a quite extensive list of categories, and if we allow several categories to be selected for an incident (i.e. like tags instead of exclusive categories), then I believe we can cover most use cases in a generic way, and obtain a structured description of the main characteristics of an incident.
>
> Then these categories can be used for various tasks including:
> - reporting, statistics, situational awareness
> - suggest potential incident responses for each category
> - automate impact and risk assessment
>
> Regards,
>
> Philippe.
>
> -----Original Message-----
> From: Daisuke MIYAMOTO [mailto:daisu-mi@nc.u-tokyo.ac.jp]
> Sent: 24 October 2014 02:12
> To: Roman D. Danyliw; 'Lagadec Philippe'; mile@ietf.org
> Subject: Re: [mile] IODEFv2 suggestions
>
> Hello,
>
>    From July, my university's incident management system supports IODEFv1. (Thank all of you joined the discussion!)
>
>    Currently, outputting my internal data records to IODEF works well.
> But, when I tried to import IODEFv1 request/response into my university's system, it found some difficulty that Legadec and Roman pointed as follows.
>
> On 2014/07/30 11:19, Roman D. Danyliw wrote:
>>> 16. Last but not least, IODEFv1 does not provide a native way to
>>> specify the incident type. We can use Impact.type to describe the
>>> type of impact, but that is different from the type of the incident
>>> itself. For example a denial of service can be caused by different
>>> types of incidents (e.g. a DDoS, the exploitation of a vulnerability,
>>> a worm, a surge in legitimate requests, a physical outage, a unhandled bug, etc).
>>> Even if it is hard to find a proper/generic way to categorize
>>> incidents that everybody agrees upon, I think it would be good to add
>>> an attribute with an enumeration for it in the Incident class.
>>> Potential sources of inspiration:
>>> https://www.us-cert.gov/government-users/reporting-requirements
>>> http://veriscommunity.net/enums.html#section-actions
>>> https://alienvault.bloomfire.com/posts/653702-open-source-security-ev
>>> ent-
>>> taxonomy/public
>>> https://capec.mitre.org/about/index.html (although this might be too
>>> detailed) And surely many others.
>>> I think it should be possible to assign several categories to an
>>> incident, because it is often a combination of several types (e.g.
>>> malware and social engineering).
>>
>> Agreed.  Issue #46, sub-bullet #2 is tracking that some approach to categorize the incidents is necessary.  Your point is well taken that whatever taxonomy or free-form approach that is taken, multiple categories for a given incident should be possible.
>
> 　I welcome "Incident type" in IODEFv2, but the enumeration of the type would be difficult by following reasons.
> 　(1) the number of type is still increasing.
>     (2) variety of the existing types.
>      - JPCERT/CC uses phishing, web hijack, malware propagation, scan,
>        DoS/DDoS, control system, and other.
>      - My univ.’s CERT also needs “spam” for containing spam senders
>        as well as JPCERT/CC’s category.
>      - Other CERT in different country may use different category.
>        For instance, CNCERT may use phishing, DoS, Abnormal domain,
>        Defacement, Backdoor, Malware, and Vulnerability.
>      - In short, there are much variations.
>
>    Regardless of the enumeration, "Incident type" field is useful.
>    Not only for my CERT, but many CERT usually publish periodical incident status reports, so this field is useful for statistical aspect.
>
>    Instead of "Incident type", multiple selections of "Impact type"
> is also helpful for us. In such case, I will use "ext-value"
> for recording specific incident type as follows.
>
>    <Assessment>
>     <Impact type="file" completion="succeeded" />
>     <Impact type="ext-value" ext-type="web-hijack-jpcert">
>    </Assessment>
>
> Kind regards,
> Daisuke


From nobody Fri Oct 24 05:30:42 2014
Return-Path: <athiasjerome@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 8D3CA1A8AE1 for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 05:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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_64=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 UTKM0qBrhc9C for <mile@ietfa.amsl.com>; Fri, 24 Oct 2014 05:30:37 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 009F81A8AE4 for <mile@ietf.org>; Fri, 24 Oct 2014 05:30:34 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id f15so1153896lbj.41 for <mile@ietf.org>; Fri, 24 Oct 2014 05:30:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5CpBMdZxcx2ZWlelp8eQ7bkej6QrjzOrBylJPNro+Og=; b=T3Cmxj2T+6zTFZESdz/JtRWSesbRxfQyNmNO+h0mz1tTWTiwjxYIMoZE8Te+lXu73R HONBqrXYH6TRNovh92FxhmupUFoMvLdgHUKcGXHUAegc79PZeCa8Cm8vqzegVVdK8xPh J/9Xnk+V5XpvkWaQ1H0yWYqAgwQmuU0ig/kdDo2yuAf/33gkOWd4Q+uLOHZzh/97YiMZ IoGZG1Q2JgEUXmX3kNwy9gCCqv/49dbmjTCj1A/Ffy5YWQJjaVIbE1yrV8GErj+gaYH3 cgUZBAWR62SKRQnbHjeNFF6cei8L5p0ECv+I+k1yhFGB4Y0bdTHW21Hx1XHs6AKL9pFz KneA==
MIME-Version: 1.0
X-Received: by 10.152.87.171 with SMTP id az11mr2509114lab.97.1414153833146; Fri, 24 Oct 2014 05:30:33 -0700 (PDT)
Received: by 10.25.5.204 with HTTP; Fri, 24 Oct 2014 05:30:32 -0700 (PDT)
In-Reply-To: <544A3CD9.5020303@nc.u-tokyo.ac.jp>
References: <1ce5bf83715a4d32b002de0d942d1222@nrnciex1011.NR.NC3A> <359EC4B99E040048A7131E0F4E113AFCA4235131@marathon> <54499958.60908@nc.u-tokyo.ac.jp> <b24bc743e7ef491e8211a03c981e934d@nrnciex1011.NR.NC3A> <544A3CD9.5020303@nc.u-tokyo.ac.jp>
Date: Fri, 24 Oct 2014 14:30:32 +0200
Message-ID: <CAA=AuEcdkUeYAPgvf2Gbt4drBBzy7Rr1EhppnMSnd-MXRnuKnQ@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/ObQ_1SXeu0uHUOygNqK1I7Eux_4
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] IODEFv2 suggestions
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, 24 Oct 2014 12:30:40 -0000

ETSI GS ISI could be useful as high level before breaking down to
(STIX) CAPEC/CWE

2014-10-24 13:49 GMT+02:00 Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>:
> Hello Philippe and all,
>
>  Thank you for your response. The category is useful for varous tasks, an=
d
> I'm happy to hear your contributions for supporting it.
>
>> suggest potential incident responses for each category
>
>  I concur with your opinion. It will be useful for CERT/CSIRT to complete
> incident response. I've got an idea for use of
> CAPEC enumeration (along with RFC7203 format), but it was not
> easy to input the values until CERT/CSIRT finished the incident
> response.
>
> Regards,
> Daisuke
>
>
> On 2014/10/24 16:22, Lagadec Philippe wrote:
>>
>> Hello Daisuke and Roman,
>>
>> Since my initial message I have been working on a list of incident
>> categories, compiled from several sources and standards. I plan to make =
a
>> proposal for IODEFv2 soon.
>> Indeed,  there are many ways to categorize incidents and terminology is
>> always an issue. But if we use a quite extensive list of categories, and=
 if
>> we allow several categories to be selected for an incident (i.e. like ta=
gs
>> instead of exclusive categories), then I believe we can cover most use c=
ases
>> in a generic way, and obtain a structured description of the main
>> characteristics of an incident.
>>
>> Then these categories can be used for various tasks including:
>> - reporting, statistics, situational awareness
>> - suggest potential incident responses for each category
>> - automate impact and risk assessment
>>
>> Regards,
>>
>> Philippe.
>>
>> -----Original Message-----
>> From: Daisuke MIYAMOTO [mailto:daisu-mi@nc.u-tokyo.ac.jp]
>> Sent: 24 October 2014 02:12
>> To: Roman D. Danyliw; 'Lagadec Philippe'; mile@ietf.org
>> Subject: Re: [mile] IODEFv2 suggestions
>>
>> Hello,
>>
>>    From July, my university's incident management system supports IODEFv=
1.
>> (Thank all of you joined the discussion!)
>>
>>    Currently, outputting my internal data records to IODEF works well.
>> But, when I tried to import IODEFv1 request/response into my university'=
s
>> system, it found some difficulty that Legadec and Roman pointed as follo=
ws.
>>
>> On 2014/07/30 11:19, Roman D. Danyliw wrote:
>>>>
>>>> 16. Last but not least, IODEFv1 does not provide a native way to
>>>> specify the incident type. We can use Impact.type to describe the
>>>> type of impact, but that is different from the type of the incident
>>>> itself. For example a denial of service can be caused by different
>>>> types of incidents (e.g. a DDoS, the exploitation of a vulnerability,
>>>> a worm, a surge in legitimate requests, a physical outage, a unhandled
>>>> bug, etc).
>>>> Even if it is hard to find a proper/generic way to categorize
>>>> incidents that everybody agrees upon, I think it would be good to add
>>>> an attribute with an enumeration for it in the Incident class.
>>>> Potential sources of inspiration:
>>>> https://www.us-cert.gov/government-users/reporting-requirements
>>>> http://veriscommunity.net/enums.html#section-actions
>>>> https://alienvault.bloomfire.com/posts/653702-open-source-security-ev
>>>> ent-
>>>> taxonomy/public
>>>> https://capec.mitre.org/about/index.html (although this might be too
>>>> detailed) And surely many others.
>>>> I think it should be possible to assign several categories to an
>>>> incident, because it is often a combination of several types (e.g.
>>>> malware and social engineering).
>>>
>>>
>>> Agreed.  Issue #46, sub-bullet #2 is tracking that some approach to
>>> categorize the incidents is necessary.  Your point is well taken that
>>> whatever taxonomy or free-form approach that is taken, multiple categor=
ies
>>> for a given incident should be possible.
>>
>>
>> =E3=80=80I welcome "Incident type" in IODEFv2, but the enumeration of th=
e type
>> would be difficult by following reasons.
>> =E3=80=80(1) the number of type is still increasing.
>>     (2) variety of the existing types.
>>      - JPCERT/CC uses phishing, web hijack, malware propagation, scan,
>>        DoS/DDoS, control system, and other.
>>      - My univ.=E2=80=99s CERT also needs =E2=80=9Cspam=E2=80=9D for con=
taining spam senders
>>        as well as JPCERT/CC=E2=80=99s category.
>>      - Other CERT in different country may use different category.
>>        For instance, CNCERT may use phishing, DoS, Abnormal domain,
>>        Defacement, Backdoor, Malware, and Vulnerability.
>>      - In short, there are much variations.
>>
>>    Regardless of the enumeration, "Incident type" field is useful.
>>    Not only for my CERT, but many CERT usually publish periodical incide=
nt
>> status reports, so this field is useful for statistical aspect.
>>
>>    Instead of "Incident type", multiple selections of "Impact type"
>> is also helpful for us. In such case, I will use "ext-value"
>> for recording specific incident type as follows.
>>
>>    <Assessment>
>>     <Impact type=3D"file" completion=3D"succeeded" />
>>     <Impact type=3D"ext-value" ext-type=3D"web-hijack-jpcert">
>>    </Assessment>
>>
>> Kind regards,
>> Daisuke
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Sun Oct 26 19:37:02 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 7B6781A6F30; Sun, 26 Oct 2014 19:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.088
X-Spam-Level: **
X-Spam-Status: No, score=2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_STOCK2=3.988] 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 1LznPzQ_WYdc; Sun, 26 Oct 2014 19:36:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5701A6F22; Sun, 26 Oct 2014 19:36:59 -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.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141027023659.31459.93423.idtracker@ietfa.amsl.com>
Date: Sun, 26 Oct 2014 19:36:59 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/lqoZM2faiNG0KG0fOrPX67BFWqQ
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-09.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: Mon, 27 Oct 2014 02:37:00 -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           : The Incident Object Description Exchange Format v2
        Authors         : Roman Danyliw
                          Paul Stoecker
	Filename        : draft-ietf-mile-rfc5070-bis-09.txt
	Pages           : 140
	Date            : 2014-10-26

Abstract:
   The Incident Object Description Exchange Format (IODEF) defines a
   data representation for sharing information commonly exchanged by
   Computer Security Incident Response Teams (CSIRTs) about computer
   security incidents.  This document describes the information model
   for the IODEF and provides an associated data model specified with
   XML Schema.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mile-rfc5070-bis-09

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mile-rfc5070-bis-09


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 Sun Oct 26 19:39:42 2014
Return-Path: <rdd@cert.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 C6D751A6F3D for <mile@ietfa.amsl.com>; Sun, 26 Oct 2014 19:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.313
X-Spam-Level: 
X-Spam-Status: No, score=-0.313 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-2.3, 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 rlcyBGmXT0Fn for <mile@ietfa.amsl.com>; Sun, 26 Oct 2014 19:39:35 -0700 (PDT)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA0DE1A6F63 for <mile@ietf.org>; Sun, 26 Oct 2014 19:39:28 -0700 (PDT)
Received: from pawpaw.sei.cmu.edu (pawpaw.sei.cmu.edu [10.64.21.22]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id s9R2dRKC017690 for <mile@ietf.org>; Sun, 26 Oct 2014 22:39:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1414377567; bh=IKm/jwIiz06BD3EflaCHDRq4A2Tr0GN3UwGLY0OUTqM=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To:Cc; b=Hpn9hqTIK5jk4R3npN2VWQ0ARiQNha5jjam3EOFSnh5XKL8q33bLAM2W+qbNs0njg JPyEjOjqYkEoDzntphNNw7dm7wlt2qtd4cKhzQVh4451W46KLf6cqb/3/tBhChsteu sZUa/4yZxzTIO3sRH7Vw93dALidxsuzS3o3FCqdU=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by pawpaw.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id s9R2dY4t016701 for <mile@ietf.org>; Sun, 26 Oct 2014 22:39:34 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0123.003; Sun, 26 Oct 2014 22:39:27 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-09.txt
Thread-Index: AQHP8Y78k9b+NRXfpUqoIoa4JlUS65xDOufA
Date: Mon, 27 Oct 2014 02:39:27 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD9311184@marathon>
References: <20141027023659.31459.93423.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027023659.31459.93423.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
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/zzkSVdr0zY-ERNp57SpSGo5r_Mo
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-09.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: Mon, 27 Oct 2014 02:39:37 -0000

The following is the Changelog for -09:

** (schema) Removed @user-agent from iodef:SoftwareType (Issue #43)
** (schema) Added NodeRole@category=3D{assessment, source-control, config-m=
anagement, monitoring}
** (schema) Removed @attacktype from NodeRole and moved the values to @cate=
gory; Moved Node/NodeRole to System/NodeRole (Issue #40)
** (schema) Added Incident/GenerationTime, {Incident, EventData}/{RecoveryT=
ime}, and EventData/ReportTime (Issue #46, sub-issue #4,6)
** (schema) Removed local definition Reference and replaced it by normative=
 reference to draft-ietf-mile-enum-reference-format (Issue #6)
** (schema) Remove a few legacy comments

NOTE: With the normative reference to draft-ietf-mile-enum-reference-format=
, the -09 schema is no longer valid.  It contains a currently invalid impor=
t of the "urn:ietf:params:xml:ns:iodef-enum-1.0" namespace.

Roman

> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Sunday, October 26, 2014 10:37 PM
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-rfc5070-bis-09.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>  This draft is a work item of the Managed Incident Lightweight Exchange
> Working Group of the IETF.
>=20
>         Title           : The Incident Object Description Exchange Format=
 v2
>         Authors         : Roman Danyliw
>                           Paul Stoecker
> 	Filename        : draft-ietf-mile-rfc5070-bis-09.txt
> 	Pages           : 140
> 	Date            : 2014-10-26
>=20
> Abstract:
>    The Incident Object Description Exchange Format (IODEF) defines a
>    data representation for sharing information commonly exchanged by
>    Computer Security Incident Response Teams (CSIRTs) about computer
>    security incidents.  This document describes the information model
>    for the IODEF and provides an associated data model specified with
>    XML Schema.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mile-rfc5070-bis-09
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-rfc5070-bis-09
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> 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


From nobody Mon Oct 27 10:20: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 767F91A0154; Mon, 27 Oct 2014 10:20:42 -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 2wlfyafW3oSv; Mon, 27 Oct 2014 10:20:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E32A41A016A; Mon, 27 Oct 2014 10:20:39 -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.7.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141027172039.22908.96756.idtracker@ietfa.amsl.com>
Date: Mon, 27 Oct 2014 10:20:39 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/oIUV7hRX8h_i-uFdPmc9j1_258Y
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-enum-reference-format-09.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: Mon, 27 Oct 2014 17:20:42 -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-09.txt
	Pages           : 10
	Date            : 2014-10-27

Abstract:
   The Incident Object Description Exchange Format (IODEF) is an XML
   data representation framework for sharing information about computer
   security incidents.  In IODEF, the Reference class provides
   references to externally specified information such as a
   vulnerability, IDS alert, malware sample, advisory, or attack
   technique.  In practice, these references are based on external
   enumeration specifications that define both the enumeration format
   and the specific enumeration values, but the IODEF Reference class
   (as specified in RFC 5070) does not indicate how to include both of
   these important pieces of information.

   This memo provides an extension to RFC 5070 to include both the
   external specification and specific enumeration value in the IODEF
   Reference class.  This memo also establishes an IANA registry to
   manage external enumeration specifications for use by IODEF.



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

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


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 Mon Oct 27 10:28:04 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 A132D1A7022; Mon, 27 Oct 2014 10:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 dXMUQ73dThU9; Mon, 27 Oct 2014 10:27:39 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A923C1A0187; Mon, 27 Oct 2014 10:27:39 -0700 (PDT)
Received: by mail-oi0-f45.google.com with SMTP id i138so3718161oig.18 for <multiple recipients>; Mon, 27 Oct 2014 10:27:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:message-id:mime-version:subject:date:references :cc:to; bh=RReos6z0I8xPLx1dmdXMk0RX83UWBkENC+21PrRsdcg=; b=LHbf2jih8UqIUiwlgrLIbnAUil8EPUs5qPK86XBYMUEPrvWey2w30GqNYJ/SYOWG1P 13NEYuflUdqCi7w4BBIEyjPKexYYWQUMjIUAHwQwiK9cH1byZJsIqp1DHFBGAboJ9cyE OAHECbOkwqlook8dVs+HgQ7YjgccKiBIqmnRi3DFEXtoE6lWY8Wv3M0tH1FRSl6b+Hx5 0sGI/7DtijdA19drwUwmhx3EFqKWABrsGbB9oQnwrwxwgGJQhEnXLEO7HTbago0M2Djt 9y1hjEu7D+/LxspMKm8uN2WtF8hKlzDKS3mLjvVLaD+3djRqJE215AQVXuJx1RwXJBOt OtxA==
X-Received: by 10.60.57.41 with SMTP id f9mr21390758oeq.17.1414430859054; Mon, 27 Oct 2014 10:27:39 -0700 (PDT)
Received: from [10.0.0.6] (99-64-100-240.lightspeed.austtx.sbcglobal.net. [99.64.100.240]) by mx.google.com with ESMTPSA id n2sm5160219oel.17.2014.10.27.10.27.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Oct 2014 10:27:35 -0700 (PDT)
From: "Adam W. Montville" <adam.w.montville@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0EF69CDE-AA60-4B7B-A821-CFFE915379ED"
Message-Id: <BAB006E5-A717-4CE1-A231-5FDC2C48200B@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Date: Mon, 27 Oct 2014 12:27:34 -0500
References: <20141027172040.22908.7076.idtracker@ietfa.amsl.com>
To: MILE IETF <mile@ietf.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/FGRBgYiXrzHpt7ZlEMijmcIOWng
Cc: ht@inf.ed.ac.uk, apps-discuss@ietf.org
Subject: [mile] Fwd: New Version Notification for draft-ietf-mile-enum-reference-format-09.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: Mon, 27 Oct 2014 17:27:44 -0000

--Apple-Mail=_0EF69CDE-AA60-4B7B-A821-CFFE915379ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

All:

I=E2=80=99ve made two minor updates to the enumeration reference draft =
(link in the forwarded message below).  Both changes are found in the =
IANA Considerations section.  The first change makes it explicit that =
all fields are mandatory, including abbreviation.  The second change =
further clarifies that the =E2=80=9Cversion=E2=80=9D field is the =
version of the referenced specification.

There was a third issue raised by an early appsdir review.  The appsdir =
review included: =E2=80=9Cthe lack of any specified mapping from the (to =
my mind) unnecessary level of indirection from integers via registry =
entries to URIs which would actually give _access_ to such entries is =
irritating at least.  Can=E2=80=99t we at least _ask_ that IANA provide =
such a mapping along the lines of =
http://www.iana.org/assignments/enumeration-reference-type/abbrev_version =
<http://www.iana.org/assignments/enumeration-reference-type/abbrev_version=
> ?=E2=80=9D

An example was provided in response, and we heard no further reply.  =
David and I believe that the URI described above would look something =
like this for version 2.5 of the =E2=80=9CCXI=E2=80=9D specification: =
http://www.iana.org/assignments/enumeration-reference-type/CXI_2.5 =
<http://www.iana.org/assignments/enumeration-reference-type/CXI_2.5>.

Regards,

Adam

> Begin forwarded message:
>=20
> From: internet-drafts@ietf.org
> To: "David L. Black" <david.black@emc.com>, "Adam W. Montville" =
<adam.w.montville@gmail.com>, Adam W. Montville =
<adam.w.montville@gmail.com>, David Black <david.black@emc.com>
> Subject: New Version Notification for =
draft-ietf-mile-enum-reference-format-09.txt
> Date: October 27, 2014 at 12:20:40 PM CDT
>=20
>=20
> A new version of I-D, draft-ietf-mile-enum-reference-format-09.txt
> has been successfully submitted by Adam W. Montville and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-mile-enum-reference-format
> Revision:	09
> Title:		IODEF Enumeration Reference Format
> Document date:	2014-10-27
> Group:		mile
> Pages:		10
> URL:            =
http://www.ietf.org/internet-drafts/draft-ietf-mile-enum-reference-format-=
09.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/
> Htmlized:       =
http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-09
> Diff:           =
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-enum-reference-format-0=
9
>=20
> Abstract:
>   The Incident Object Description Exchange Format (IODEF) is an XML
>   data representation framework for sharing information about computer
>   security incidents.  In IODEF, the Reference class provides
>   references to externally specified information such as a
>   vulnerability, IDS alert, malware sample, advisory, or attack
>   technique.  In practice, these references are based on external
>   enumeration specifications that define both the enumeration format
>   and the specific enumeration values, but the IODEF Reference class
>   (as specified in RFC 5070) does not indicate how to include both of
>   these important pieces of information.
>=20
>   This memo provides an extension to RFC 5070 to include both the
>   external specification and specific enumeration value in the IODEF
>   Reference class.  This memo also establishes an IANA registry to
>   manage external enumeration specifications for use by IODEF.
>=20
>=20
>=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.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_0EF69CDE-AA60-4B7B-A821-CFFE915379ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">All:<div class=3D""><br class=3D""></div><div class=3D"">I=E2=80=
=99ve made two minor updates to the enumeration reference draft (link in =
the forwarded message below). &nbsp;Both changes are found in the IANA =
Considerations section. &nbsp;The first change makes it explicit that =
all fields are mandatory, including abbreviation. &nbsp;The second =
change further clarifies that the =E2=80=9Cversion=E2=80=9D field is the =
version of the referenced specification.</div><div class=3D""><br =
class=3D""></div><div class=3D"">There was a third issue raised by an =
early appsdir review. &nbsp;The appsdir review included: =E2=80=9Cthe =
lack of any specified mapping from the (to my mind) unnecessary level of =
indirection from integers via registry entries to URIs which would =
actually give _access_ to such entries is irritating at least. =
&nbsp;Can=E2=80=99t we at least _ask_ that IANA provide such a mapping =
along the lines of <a =
href=3D"http://www.iana.org/assignments/enumeration-reference-type/abbrev_=
version" =
class=3D"">http://www.iana.org/assignments/enumeration-reference-type/abbr=
ev_version</a>&nbsp;?=E2=80=9D</div><div class=3D""><br =
class=3D""></div><div class=3D"">An example was provided in response, =
and we heard no further reply. &nbsp;David and I believe that the URI =
described above would look something like this for version 2.5 of the =
=E2=80=9CCXI=E2=80=9D specification: <a =
href=3D"http://www.iana.org/assignments/enumeration-reference-type/CXI_2.5=
" =
class=3D"">http://www.iana.org/assignments/enumeration-reference-type/CXI_=
2.5</a>.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Regards,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Adam<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D"">"David L. Black" &lt;<a =
href=3D"mailto:david.black@emc.com" =
class=3D"">david.black@emc.com</a>&gt;, "Adam W. Montville" &lt;<a =
href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt;, Adam W. Montville &lt;<a =
href=3D"mailto:adam.w.montville@gmail.com" =
class=3D"">adam.w.montville@gmail.com</a>&gt;, David Black &lt;<a =
href=3D"mailto:david.black@emc.com" =
class=3D"">david.black@emc.com</a>&gt;<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">New Version =
Notification for draft-ietf-mile-enum-reference-format-09.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">October 27, 2014 at 12:20:40 PM =
CDT<br class=3D""></span></div><br class=3D""><div class=3D""><br =
class=3D"">A new version of I-D, =
draft-ietf-mile-enum-reference-format-09.txt<br class=3D"">has been =
successfully submitted by Adam W. Montville and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>draft-ietf-mile-enum-reference-format<br class=3D"">Revision:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>09<br =
class=3D"">Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>IODEF Enumeration Reference Format<br class=3D"">Document =
date:<span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>2014-10-27<br class=3D"">Group:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>mile<br class=3D"">Pages:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>10<br =
class=3D"">URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-mile-enum-reference=
-format-09.txt" =
class=3D"">http://www.ietf.org/internet-drafts/draft-ietf-mile-enum-refere=
nce-format-09.txt</a><br class=3D"">Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-fo=
rmat/" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference=
-format/</a><br class=3D"">Htmlized: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-mile-enum-reference-format-0=
9" =
class=3D"">http://tools.ietf.org/html/draft-ietf-mile-enum-reference-forma=
t-09</a><br class=3D"">Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-enum-reference-=
format-09" =
class=3D"">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mile-enum-referen=
ce-format-09</a><br class=3D""><br class=3D"">Abstract:<br class=3D""> =
&nbsp;&nbsp;The Incident Object Description Exchange Format (IODEF) is =
an XML<br class=3D""> &nbsp;&nbsp;data representation framework for =
sharing information about computer<br class=3D""> &nbsp;&nbsp;security =
incidents. &nbsp;In IODEF, the Reference class provides<br class=3D""> =
&nbsp;&nbsp;references to externally specified information such as a<br =
class=3D""> &nbsp;&nbsp;vulnerability, IDS alert, malware sample, =
advisory, or attack<br class=3D""> &nbsp;&nbsp;technique. &nbsp;In =
practice, these references are based on external<br class=3D""> =
&nbsp;&nbsp;enumeration specifications that define both the enumeration =
format<br class=3D""> &nbsp;&nbsp;and the specific enumeration values, =
but the IODEF Reference class<br class=3D""> &nbsp;&nbsp;(as specified =
in RFC 5070) does not indicate how to include both of<br class=3D""> =
&nbsp;&nbsp;these important pieces of information.<br class=3D""><br =
class=3D""> &nbsp;&nbsp;This memo provides an extension to RFC 5070 to =
include both the<br class=3D""> &nbsp;&nbsp;external specification and =
specific enumeration value in the IODEF<br class=3D""> =
&nbsp;&nbsp;Reference class. &nbsp;This memo also establishes an IANA =
registry to<br class=3D""> &nbsp;&nbsp;manage external enumeration =
specifications for use by IODEF.<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D""><br class=3D"">Please note that =
it may take a couple of minutes from the time of submission<br =
class=3D"">until the htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org" class=3D"">tools.ietf.org</a>.<br =
class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_0EF69CDE-AA60-4B7B-A821-CFFE915379ED--


From nobody Tue Oct 28 13:04:19 2014
Return-Path: <rdd@cert.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 E23EE1ACE18 for <mile@ietfa.amsl.com>; Tue, 28 Oct 2014 13:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 2qRju-syKxx3 for <mile@ietfa.amsl.com>; Tue, 28 Oct 2014 13:04:07 -0700 (PDT)
Received: from shetland.sei.cmu.edu (shetland.sei.cmu.edu [192.58.107.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 022A51ACDFF for <mile@ietf.org>; Tue, 28 Oct 2014 13:03:29 -0700 (PDT)
Received: from pawpaw.sei.cmu.edu (pawpaw.sei.cmu.edu [10.64.21.22]) by shetland.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id s9SK3Sn1024992 for <mile@ietf.org>; Tue, 28 Oct 2014 16:03:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1414526608; bh=1Okw+VXmE+hxHa4fw907LViPMgghjhrKW4QqhwNML3w=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=GKG8BeyN+5IWbD74fkzNa7xr3t+FSF9j1kakjloLAdHqAGLckcCnDnAvmbkuHZVb0 yhTV3D13slxn87KDlbWpgmSs8qny4ObrANMqf1DOM7Plj5q2fPhgz83sOgqDYuapVb wBinewCpm9BacMIg44ycAOvtYhR46DN4nU5wz4ts=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by pawpaw.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id s9SK3Xaq012575 for <mile@ietf.org>; Tue, 28 Oct 2014 16:03:33 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0123.003; Tue, 28 Oct 2014 16:03:26 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Splitting the Impact class
Thread-Index: Ac/y6ZH8QBGGMt4/QeOUJhQ3aOpxAg==
Date: Tue, 28 Oct 2014 20:03:25 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD93194AF@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
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/J4ptyWP7T155LOSPl_26ra_zt1Y
Subject: [mile] Splitting the Impact class
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: Tue, 28 Oct 2014 20:04:15 -0000

Hello!

Issue #10 [1] is tracking the need to review the completeness of the Impact=
@type attribute.  Examining the current write-up and the discussions on the=
 mailing list [2] [3], it seems to me that this attribute is serving two pu=
rposes -- (a) as the incident category and (b) as a description of the tech=
nical impact to a given system based on the tactics/attack vector described=
 in the Method class.  Should we perhaps encode distinct classes of informa=
tion into separate elements/attributes?

The feedback on using Impact@type attribute for purpose (a), as an incident=
 category, is that everyone has a different scheme of categorization.  My p=
roposal to this use is that we should make a new class or attribute named I=
ncidentCategory and it would just be a text field, not an enumerated value.

To address use (b), a class to describe the technical impact to system base=
d on the tactics/attack vector described in the Method class, I would propo=
sed a new set of enumerated values.  For simplicity, perhaps also renamed t=
he Impact class to be SystemImpact.  The values I would envision would be:=
=20

<t>takeover-account.  Control was taken of a given account (e.g., a social =
media account).</t>
<t>takeover-service.  Control was taken of a given service (e.g., xxx).</t>
<t>takeover-system.  Control was taken of a given system.</t>
<t>cps-manipulation. A cyber physical system was manipulated. </t>
<t>cps-damage. A cyber physical system was damaged. </t>
<t>availability-data. Access to particular data was degraded or denied.</t>
<t>availability-account.  Access to an account was degraded or denied.</t>
<t>availability-service. Access to a service was degraded or denied.</t>
<t>availability-system.  Access to a system was degraded or denied.</t>=20
<t>damaged-system.  Hardware on a system was irreparably damaged.</t>
<t>damaged-data. Data on a system was deleted.</t>
<t>breach-proprietary.  Sensitive or proprietary information was accessed o=
r exfiltrated.</t>
<t>breach-privacy.  Personally identifiable information was accessed or exf=
iltrated.</t>
<t>breach-credential.  Credential information was accessed or exfiltrated.<=
/t>
<t>breach-configuration.  System configuration or data inventory was access=
 or exfiltrated.</t>
<t>integrity-data.  Data on the system was modified.</t>
<t>integrity-configuration. Application or system configuration was modifie=
d.</t>
<t>integrity-hardware.  Firmware of a hardware component was modified.</t>
<t>traffic-redirection. Network traffic on the system was redirected</t>
<t>monitoring-traffic. Network traffic emerging from a host was monitored.<=
/t>
<t>monitoring-host.  System activity (e.g., running processes, keystrokes) =
were monitored.</t>
<t>policy. Activity violated the system owner's acceptable use policy.</t>

Would this approach be more useful for the community?  Is there backward co=
mpatibility issues we need to consider as this will break the IODEF v1 mode=
l?=20

If the community likes this approach, what additional enumerated values sho=
uld be included?

Roman=20

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/10
[2] http://www.ietf.org/mail-archive/web/mile/current/msg01526.html
[3] http://www.ietf.org/mail-archive/web/mile/current/msg01509.html

