
From nobody Mon Apr  1 00:45:02 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 095EA12008B; Mon,  1 Apr 2019 00:44:53 -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>
Cc: mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: mile@ietf.org
Message-ID: <155410469293.17190.493306635564508642@ietfa.amsl.com>
Date: Mon, 01 Apr 2019 00:44:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/c08bD9eI39d6viVN3eiRx7QAUpw>
Subject: [mile] I-D Action: draft-ietf-mile-jsoniodef-08.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 07:44:53 -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 WG of the IETF.

        Title           : CBOR/JSON binding of IODEF
        Authors         : Takeshi Takahashi
                          Roman Danyliw
                          Mio Suzuki
	Filename        : draft-ietf-mile-jsoniodef-08.txt
	Pages           : 70
	Date            : 2019-04-01

Abstract:
   RFC7970 specified an information model and a corresponding XML data
   model for exchanging incident and indicator information.  This draft
   provides an alternative data model implementation in CBOR/JSON.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mile-jsoniodef-08
https://datatracker.ietf.org/doc/html/draft-ietf-mile-jsoniodef-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mile-jsoniodef-08


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 Apr  1 00:47:18 2019
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 179B0120086 for <mile@ietfa.amsl.com>; Mon,  1 Apr 2019 00:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anQyMGvr5xtv for <mile@ietfa.amsl.com>; Mon,  1 Apr 2019 00:47:13 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id 080A812008B for <mile@ietf.org>; Mon,  1 Apr 2019 00:47:12 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTPS id x317lBi1006052 for <mile@ietf.org>; Mon, 1 Apr 2019 16:47:11 +0900 (JST)
Received: from mail2.nict.go.jp (mail2.nict.go.jp [133.243.18.15]) by gw2.nict.go.jp  with ESMTP id x317lAef006048 for <mile@ietf.org>; Mon, 1 Apr 2019 16:47:10 +0900 (JST)
Received: from LAPTOP9DLCDU5S (ssh1.nict.go.jp [133.243.3.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.nict.go.jp (NICT Mail Spool Server2) with ESMTPSA id E3A0711AF6 for <mile@ietf.org>; Mon,  1 Apr 2019 16:47:10 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <155410469293.17190.493306635564508642@ietfa.amsl.com>
In-Reply-To: <155410469293.17190.493306635564508642@ietfa.amsl.com>
Date: Mon, 1 Apr 2019 16:47:10 +0900
Message-ID: <c5d801d4e85f$1cde12c0$569a3840$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI0OWcVwZ/mjEg+VnXSxmnneXG6NKVoSyKQ
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.101.1 at zenith2m8
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/DRf3FT_UNkVvnzZeDgMwP66lNKg>
Subject: Re: [mile] I-D Action: draft-ietf-mile-jsoniodef-08.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 07:47:16 -0000

Hi all,

Based on the discussion during the MILE session in Prague, the IANA section
of the draft was changed.
Hopefully we can move forward.
If you find some issues, please kindly let me know.
We appreciate your kind feedback.

Thank you.
Take



-----Original Message-----
From: mile <mile-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: Monday, April 1, 2019 4:45 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-jsoniodef-08.txt


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

        Title           : CBOR/JSON binding of IODEF
        Authors         : Takeshi Takahashi
                          Roman Danyliw
                          Mio Suzuki
	Filename        : draft-ietf-mile-jsoniodef-08.txt
	Pages           : 70
	Date            : 2019-04-01

Abstract:
   RFC7970 specified an information model and a corresponding XML data
   model for exchanging incident and indicator information.  This draft
   provides an alternative data model implementation in CBOR/JSON.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mile-jsoniodef-08
https://datatracker.ietf.org/doc/html/draft-ietf-mile-jsoniodef-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mile-jsoniodef-08


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

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

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


From nobody Sat Apr  6 23:41:37 2019
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562201201AF for <mile@ietfa.amsl.com>; Sat,  6 Apr 2019 23:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.107
X-Spam-Level: 
X-Spam-Status: No, score=-4.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_10_20=0.093, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9ZYwB_RFwef for <mile@ietfa.amsl.com>; Sat,  6 Apr 2019 23:41:34 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3636212019C for <mile@ietf.org>; Sat,  6 Apr 2019 23:41:34 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTPS id x376fXLo082065 for <mile@ietf.org>; Sun, 7 Apr 2019 15:41:33 +0900 (JST)
Received: from mail2.nict.go.jp (mail2.nict.go.jp [133.243.18.15]) by gw1.nict.go.jp  with ESMTP id x376fWmr082039 for <mile@ietf.org>; Sun, 7 Apr 2019 15:41:32 +0900 (JST)
Received: from LAPTOP9DLCDU5S (ssh1.nict.go.jp [133.243.3.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.nict.go.jp (NICT Mail Spool Server2) with ESMTPSA id 5024E12728 for <mile@ietf.org>; Sun,  7 Apr 2019 15:41:32 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Sun, 7 Apr 2019 15:41:31 +0900
Message-ID: <00a301d4ed0c$f1b2bbc0$d5183340$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A4_01D4ED58.619B2710"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdTtDMcDffZbVJr3TyWpHpICA9yR1Q==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.101.1 at zenith1m8
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/5RP95VBLAepFeYzuIoixQxkSDRQ>
Subject: [mile] comments on the draft-ietf-mile-rolie-vuln-00 draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2019 06:41:36 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A4_01D4ED58.619B2710
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Stephen,

 

I have read the draft-ietf-mile-rolie-vuln-00 draft and I generally like the
draft.

Here are some comments.

 

1.	"There must be one rolie:property with the name attribute equal to
urn.content-id" seems to be a common requirements for both XML CVE and JSON
CVE. Currently, it is written as a XML CVE requirement and as a JSON CVE
requirement, but it could be written as a common requirement.
2.	Regarding VDO, it is not a spec yet. How will you cope with VDO once
it becomes a spec (approved by NIST)?
3.	According to the current text, I could not find any field that
indicates that the content is "cve". By looking at the information-type, we
can see the content is a vulnerability information. But we cannot know the
content is a cve note or not until we see the content itself. Is my
understanding correct? Where can we know that the content is a cve note or
not?
4.	According to the current text, I understood that we will treat a VDO
as a plain text at this moment. Then, do we indicate that the content is a
vulnerability information or not? It seems to be that we do not indicate so
according to the current text. Is that so?
5.	Section 4 is concisely represented. I like it. However, having some
examples will help readers to understand the content properly. How about
adding some examples in its appendix or in this section?
6.	According to section5.1, we MUST send a severity information when
sending a vulnerability note. That means, we cannot send an early
vulnerability information without a score, correct? Just a clarification.
7.	I guess you will make this vulnerability rolie extensible enough.
Can you add some sentences how we could cope with the other vulnerability
notes that may emerge in the future?
8.	Is it going to be an informational RFC? It has several definitive
parts. So, I am just asking your intention.

 

Editorial comments are not important at this stage, but it won't harm to
list here.

 

"support Vulnerability use cases" -> "support vulnerability use cases".

"a automated and efficient fashion" -> "an automated and efficient fashion".

"a XML" -> "an XML"

In the reference, vdo cannot be a normative reference at this moment, due to
its document status.

 

Thank you, and kind regards,

Take

 


------=_NextPart_000_00A4_01D4ED58.619B2710
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Yu Gothic";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0mm;
	margin-right:0mm;
	margin-bottom:0mm;
	margin-left:42.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0mm;
	mso-para-margin-right:0mm;
	mso-para-margin-bottom:0mm;
	mso-para-margin-left:4.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Yu Gothic";}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0mm;
	mso-margin-bottom-alt:auto;
	margin-left:0mm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.19
	{mso-style-type:personal-compose;
	font-family:"Yu Gothic";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1839492501;
	mso-list-template-ids:-1862257280;}
@list l1
	{mso-list-id:1917669990;
	mso-list-type:hybrid;
	mso-list-template-ids:892098970 1696903080 67698711 67698705 67698703 =
67698711 67698705 67698703 67698711 67698705;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:aiueo-full-width;
	mso-level-text:"\(%2\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:42.0pt;
	text-indent:-21.0pt;}
@list l1:level3
	{mso-level-number-format:decimal-enclosed-circle;
	mso-level-text:%3;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:63.0pt;
	text-indent:-21.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:84.0pt;
	text-indent:-21.0pt;}
@list l1:level5
	{mso-level-number-format:aiueo-full-width;
	mso-level-text:"\(%5\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:105.0pt;
	text-indent:-21.0pt;}
@list l1:level6
	{mso-level-number-format:decimal-enclosed-circle;
	mso-level-text:%6;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:126.0pt;
	text-indent:-21.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:147.0pt;
	text-indent:-21.0pt;}
@list l1:level8
	{mso-level-number-format:aiueo-full-width;
	mso-level-text:"\(%8\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:168.0pt;
	text-indent:-21.0pt;}
@list l1:level9
	{mso-level-number-format:decimal-enclosed-circle;
	mso-level-text:%9;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:189.0pt;
	text-indent:-21.0pt;}
ol
	{margin-bottom:0mm;}
ul
	{margin-bottom:0mm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026">
<v:textbox inset=3D"5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DJA =
link=3D"#0563C1" vlink=3D"#954F72" =
style=3D'text-justify-trim:punctuation'><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Hi =
Stephen,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>I have =
read the draft-ietf-mile-rolie-vuln-00 draft and I generally like the =
draft.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'>Here are some =
comments.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0mm' start=3D1 type=3D1><li class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span style=3D'font-size:11.0pt'>&#8220;<span lang=3DEN-US>There =
must be one rolie:property with the name attribute equal to =
urn</span>&#8230;<span lang=3DEN-US>content-id</span>&#8221;<span =
lang=3DEN-US> seems to be a common requirements for both XML CVE and =
JSON CVE. Currently, it is written as a XML CVE requirement and as a =
JSON CVE requirement, but it could be written as a common =
requirement.<o:p></o:p></span></span></li><li class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>Regarding VDO, it is =
not a spec yet. How will you cope with VDO once it becomes a spec =
(approved by NIST)?<o:p></o:p></span></li><li class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>According to the =
current text, I could not find any field that indicates that the content =
is </span><span style=3D'font-size:11.0pt'>&#8220;<span =
lang=3DEN-US>cve</span>&#8221;<span lang=3DEN-US>. By looking at the =
information-type, we can see the content is a vulnerability information. =
But we cannot know the content is a cve note or not until we see the =
content itself. Is my understanding correct? Where can we know that the =
content is a cve note or not?<o:p></o:p></span></span></li><li =
class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>According to the =
current text, I understood that we will treat a VDO as a plain text at =
this moment. Then, do we indicate that the content is a vulnerability =
information or not? It seems to be that we do not indicate so according =
to the current text. Is that so?<o:p></o:p></span></li><li =
class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>Section 4 is =
concisely represented. I like it. However, having some examples will =
help readers to understand the content properly. How about adding some =
examples in its appendix or in this section?<o:p></o:p></span></li><li =
class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>According to =
section5.1, we MUST send a severity information when sending a =
vulnerability note. That means, we cannot send an early vulnerability =
information without a score, correct? Just a =
clarification.<o:p></o:p></span></li><li class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>I guess you will =
make this vulnerability rolie extensible enough. Can you add some =
sentences how we could cope with the other vulnerability notes that may =
emerge in the future?<o:p></o:p></span></li><li class=3DMsoListParagraph =
style=3D'margin-left:-18.0pt;mso-para-margin-left:0gd;mso-list:l1 level1 =
lfo3'><span lang=3DEN-US style=3D'font-size:11.0pt'>Is it going to be an =
informational RFC? It has several definitive parts. So, I am just asking =
your intention.<o:p></o:p></span></li></ol><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'>Editorial comments are not important at this =
stage, but it won</span><span style=3D'font-size:11.0pt'>&#8217;<span =
lang=3DEN-US>t harm to list here.<o:p></o:p></span></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>&#8220;<span =
lang=3DEN-US>support Vulnerability use cases</span>&#8221;<span =
lang=3DEN-US> -&gt; </span>&#8220;<span lang=3DEN-US>support =
vulnerability use cases</span>&#8221;<span =
lang=3DEN-US>.<o:p></o:p></span></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt'>&#8220;<span lang=3DEN-US>a automated and =
efficient fashion</span>&#8221;<span lang=3DEN-US> -&gt; =
</span>&#8220;<span lang=3DEN-US>an automated and efficient =
fashion</span>&#8221;<span lang=3DEN-US>.<o:p></o:p></span></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt'>&#8220;<span =
lang=3DEN-US>a XML</span>&#8221;<span lang=3DEN-US> -&gt; =
</span>&#8220;<span lang=3DEN-US>an XML</span>&#8221;<span =
lang=3DEN-US><o:p></o:p></span></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>In the reference, vdo cannot be =
a normative reference at this moment, due to its document =
status.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Thank =
you, and kind regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>Take<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>
------=_NextPart_000_00A4_01D4ED58.619B2710--


From nobody Mon Apr  8 10:07:18 2019
Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A84E21200B7 for <mile@ietfa.amsl.com>; Mon,  8 Apr 2019 10:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.741
X-Spam-Level: 
X-Spam-Status: No, score=-1.741 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nist.gov
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 60tdpEJ9XyuE for <mile@ietfa.amsl.com>; Mon,  8 Apr 2019 10:07:13 -0700 (PDT)
Received: from GCC01-DM2-obe.outbound.protection.outlook.com (mail-eopbgr840092.outbound.protection.outlook.com [40.107.84.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F405112002F for <mile@ietf.org>; Mon,  8 Apr 2019 10:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nist.gov; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oZfcjIFp08KfAFZXPZmnQPWhsHNm1Ww6qJ5tGqgnnTc=; b=M8A5CpHj4qOvt3Pag60eAa5vm6q3NahgBl1WCC5yQFs+ctzWWk8m+2Rh95POeNNE5WNVupEHMR7UZpw6IgJmZwOgm8eI5w6ggivQO0vO8azZEQPwtwR2O8K304fNyws3E29nxenBEuDFYXueKRaCi3XuPM5Z1bpgJugLHj8E+NY=
Received: from BN3PR09MB0609.namprd09.prod.outlook.com (10.160.120.12) by BN3PR09MB0612.namprd09.prod.outlook.com (10.160.120.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.13; Mon, 8 Apr 2019 17:07:10 +0000
Received: from BN3PR09MB0609.namprd09.prod.outlook.com ([fe80::1ce5:2c44:3260:75d3]) by BN3PR09MB0609.namprd09.prod.outlook.com ([fe80::1ce5:2c44:3260:75d3%7]) with mapi id 15.20.1771.014; Mon, 8 Apr 2019 17:07:10 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] comments on the draft-ietf-mile-rolie-vuln-00 draft
Thread-Index: AdTtDMcDffZbVJr3TyWpHpICA9yR1QBHmUXN
Date: Mon, 8 Apr 2019 17:07:10 +0000
Message-ID: <BN3PR09MB0609E3FFC190D170D90076C4F02C0@BN3PR09MB0609.namprd09.prod.outlook.com>
References: <00a301d4ed0c$f1b2bbc0$d5183340$@nict.go.jp>
In-Reply-To: <00a301d4ed0c$f1b2bbc0$d5183340$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.229.198]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 454aabb9-6092-47e1-e2ec-08d6bc44a372
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:BN3PR09MB0612; 
x-ms-traffictypediagnostic: BN3PR09MB0612:
x-microsoft-antispam-prvs: <BN3PR09MB061273D31A8529F7863FF3CDF02C0@BN3PR09MB0612.namprd09.prod.outlook.com>
x-forefront-prvs: 0001227049
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(396003)(136003)(366004)(346002)(51914003)(189003)(199004)(5660300002)(2906002)(110136005)(14454004)(55016002)(6436002)(52536014)(53936002)(7696005)(86362001)(8936002)(6246003)(76176011)(229853002)(9686003)(54896002)(66066001)(97736004)(478600001)(25786009)(486006)(7736002)(6116002)(105004)(476003)(71200400001)(446003)(71190400001)(19627405001)(3846002)(106356001)(186003)(33656002)(8676002)(2501003)(102836004)(26005)(6506007)(74316002)(68736007)(81156014)(53546011)(81166006)(99286004)(19627235002)(316002)(256004)(105586002)(11346002)(14444005); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR09MB0612; H:BN3PR09MB0609.namprd09.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: s6NPfiCwesw4qP6SFgB6GeuSfVEIpapcbTLWVZdKwKsruFZc0I8sOQkK8m4zpbjMX4VAPb7M4FyfoZ9gS5B7mu/hVf3NehMSeC4Zv/Uj7oBPDD2lX9RnTbp0y/v97REm3N0wv5k7aCf/jOSO9q4M0CrI7412jwFjqXrpauBPeMNPv+GlX3OtH2+lkelJOtDykJ35IybnAtysXzLO2j1QG+dmtiyNIPueR7D2IgPFx/I9hOWNEv3Y6x1TfXRqa5XJ+Z6dyPOSX3fzJsN3cHOiJ59vX0boraKTBJF1guBQCf3hY+uFSjbhVtrQ6h3ewIsDOMRHOJ/cdDp+hO+cXnkAspAHu4pwpPuMwe1dBu1q42MbunZGPEV7HLC8tEPz1XWh391DGs3Hi97jjCHBLKyKWbc7efTem2TdmDBaZKLcEkk=
Content-Type: multipart/alternative; boundary="_000_BN3PR09MB0609E3FFC190D170D90076C4F02C0BN3PR09MB0609namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-Network-Message-Id: 454aabb9-6092-47e1-e2ec-08d6bc44a372
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Apr 2019 17:07:10.3205 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR09MB0612
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/0N0zi7dkRfHrZaFTzCrW7g3xP4U>
Subject: Re: [mile] comments on the draft-ietf-mile-rolie-vuln-00 draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 17:07:17 -0000

--_000_BN3PR09MB0609E3FFC190D170D90076C4F02C0BN3PR09MB0609namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Take,

Thank you for the review, I've responded below.


  1.  That is a good idea, thank you. I will make the content id a shared r=
equirement.
  2.  I plan on either releasing an update to this document or creating a n=
ew extension on it. I will add a sentence on that in the VDO section.
  3.  Thanks for catching this. I need to add a requirement to use a "rolie=
:format" element that will point to the CVE XML/JSON Schema. That will iden=
tify the entry as a CVE document.
  4.  My intention is that the entry would still have an information-type o=
f "vulnerability" even if you are using plain text VDO. I will clarify this=
 in the document.
  5.  Examples are a good idea. I have examples in the other ROLIE extensio=
ns already, I just need to create some for the vulnerability entries.
  6.  The intent is that such a link MUST be supported by the implementatio=
n, but it does not need to actually appear in a vulnerability entry. I'll a=
dd a sentence clarifying this requirement.
  7.  Generally, if there are new vulnerability formats in the future, it w=
ould be possible to simply publish a new document with requirements and gui=
dance for that format. They can reference this document for the information=
-type.
  8.  Given the current level of requirements in the document, I think it w=
ould be best to publish as standards track. However, I'd be willing to talk=
 about it if the chairs/AD have any issues.

Thanks for the editorial comments as well, I've accepted all of your edits.


Thanks again for the review!

Stephen

  1.

________________________________
From: mile <mile-bounces@ietf.org> on behalf of Takeshi Takahashi <takeshi_=
takahashi@nict.go.jp>
Sent: Sunday, April 7, 2019 2:41 AM
To: mile@ietf.org
Subject: [mile] comments on the draft-ietf-mile-rolie-vuln-00 draft


Hi Stephen,



I have read the draft-ietf-mile-rolie-vuln-00 draft and I generally like th=
e draft.

Here are some comments.



  1.  =93There must be one rolie:property with the name attribute equal to =
urn=85content-id=94 seems to be a common requirements for both XML CVE and =
JSON CVE. Currently, it is written as a XML CVE requirement and as a JSON C=
VE requirement, but it could be written as a common requirement.
  2.  Regarding VDO, it is not a spec yet. How will you cope with VDO once =
it becomes a spec (approved by NIST)?
  3.  According to the current text, I could not find any field that indica=
tes that the content is =93cve=94. By looking at the information-type, we c=
an see the content is a vulnerability information. But we cannot know the c=
ontent is a cve note or not until we see the content itself. Is my understa=
nding correct? Where can we know that the content is a cve note or not?
  4.  According to the current text, I understood that we will treat a VDO =
as a plain text at this moment. Then, do we indicate that the content is a =
vulnerability information or not? It seems to be that we do not indicate so=
 according to the current text. Is that so?
  5.  Section 4 is concisely represented. I like it. However, having some e=
xamples will help readers to understand the content properly. How about add=
ing some examples in its appendix or in this section?
  6.  According to section5.1, we MUST send a severity information when sen=
ding a vulnerability note. That means, we cannot send an early vulnerabilit=
y information without a score, correct? Just a clarification.
  7.  I guess you will make this vulnerability rolie extensible enough. Can=
 you add some sentences how we could cope with the other vulnerability note=
s that may emerge in the future?
  8.  Is it going to be an informational RFC? It has several definitive par=
ts. So, I am just asking your intention.



Editorial comments are not important at this stage, but it won=92t harm to =
list here.



=93support Vulnerability use cases=94 -> =93support vulnerability use cases=
=94.

=93a automated and efficient fashion=94 -> =93an automated and efficient fa=
shion=94.

=93a XML=94 -> =93an XML=94

In the reference, vdo cannot be a normative reference at this moment, due t=
o its document status.



Thank you, and kind regards,

Take



--_000_BN3PR09MB0609E3FFC190D170D90076C4F02C0BN3PR09MB0609namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri,Arial,Helvetica,sans-serif; font-size: 1=
2pt; color: rgb(0, 0, 0);">
Take,<br>
<br>
Thank you for the review, I've responded below.<br>
<br>
<ol>
<li style=3D"font-family: calibri,arial,helvetica,sans-serif; font-size: 12=
pt; color: rgb(0, 0, 0);">
That is a good idea, thank you. I will make the content id a shared require=
ment.</li><li style=3D"font-family: calibri,arial,helvetica,sans-serif; fon=
t-size: 12pt; color: rgb(0, 0, 0);">
I plan on either releasing an update to this document or creating a new ext=
ension on it. I will add a sentence on that in the VDO section.</li><li sty=
le=3D"font-family: calibri,arial,helvetica,sans-serif; font-size: 12pt; col=
or: rgb(0, 0, 0);">
Thanks for catching this. I need to add a requirement to use a &quot;rolie:=
format&quot; element that will point to the CVE XML/JSON Schema. That will =
identify the entry as a CVE document.</li><li style=3D"font-family: calibri=
,arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
My intention is that the entry would still have an information-type of &quo=
t;vulnerability&quot; even if you are using plain text VDO. I will clarify =
this in the document.</li><li style=3D"font-family: calibri,arial,helvetica=
,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Examples are a good idea. I have examples in the other ROLIE extensions alr=
eady, I just need to create some for the vulnerability entries.</li><li sty=
le=3D"font-family: calibri,arial,helvetica,sans-serif; font-size: 12pt; col=
or: rgb(0, 0, 0);">
The intent is that such a link MUST be supported by the implementation, but=
 it does not need to actually appear in a vulnerability entry. I'll add a s=
entence clarifying this requirement.</li><li style=3D"font-family: calibri,=
arial,helvetica,sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Generally, if there are new vulnerability formats in the future, it would b=
e possible to simply publish a new document with requirements and guidance =
for that format. They can reference this document for the information-type.=
</li><li style=3D"font-family: calibri,arial,helvetica,sans-serif; font-siz=
e: 12pt; color: rgb(0, 0, 0);">
Given the current level of requirements in the document, I think it would b=
e best to publish as standards track. However, I'd be willing to talk about=
 it if the chairs/AD have any issues.</li></ol>
<p>Thanks for the editorial comments as well, I've accepted all of your edi=
ts.</p>
<p><br>
</p>
<p>Thanks again for the review!</p>
<p>Stephen<br>
</p>
<ol>
<li style=3D"font-family: calibri,arial,helvetica,sans-serif; font-size: 12=
pt; color: rgb(0, 0, 0);">
<br>
</li></ol>
</div>
<div id=3D"appendonsend"></div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> mile &lt;mile-bounces=
@ietf.org&gt; on behalf of Takeshi Takahashi &lt;takeshi_takahashi@nict.go.=
jp&gt;<br>
<b>Sent:</b> Sunday, April 7, 2019 2:41 AM<br>
<b>To:</b> mile@ietf.org<br>
<b>Subject:</b> [mile] comments on the draft-ietf-mile-rolie-vuln-00 draft<=
/font>
<div>&nbsp;</div>
</div>
<style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:"Yu Gothic"}
@font-face
	{font-family:Calibri}
@font-face
	{font-family:"Yu Gothic"}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Yu Gothic"}
a:link, span.x_MsoHyperlink
	{color:#0563C1;
	text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
	{color:#954F72;
	text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
	{margin-top:0mm;
	margin-right:0mm;
	margin-bottom:0mm;
	margin-left:42.0pt;
	margin-bottom:.0001pt;
	text-align:justify;
	font-size:10.5pt;
	font-family:"Yu Gothic"}
p.x_msonormal0, li.x_msonormal0, div.x_msonormal0
	{margin-right:0mm;
	margin-left:0mm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
@page WordSection1
	{margin:99.25pt 30.0mm 30.0mm 30.0mm}
div.x_WordSection1
	{}
ol
	{margin-bottom:0mm}
ul
	{margin-bottom:0mm}
-->
</style>
<div lang=3D"JA" link=3D"#0563C1" vlink=3D"#954F72" style=3D"">
<div class=3D"x_WordSection1">
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Hi=
 Stephen,</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">I =
have read the draft-ietf-mile-rolie-vuln-00 draft and I generally like the =
draft.</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">He=
re are some comments.</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
<ol start=3D"1" type=3D"1" style=3D"margin-top:0mm">
<li class=3D"x_MsoListParagraph" style=3D""><span style=3D"font-size:11.0pt=
">=93<span lang=3D"EN-US">There must be one rolie:property with the name at=
tribute equal to urn</span>=85<span lang=3D"EN-US">content-id</span>=94<spa=
n lang=3D"EN-US"> seems to be a common requirements
 for both XML CVE and JSON CVE. Currently, it is written as a XML CVE requi=
rement and as a JSON CVE requirement, but it could be written as a common r=
equirement.</span></span></li><li class=3D"x_MsoListParagraph" style=3D""><=
span lang=3D"EN-US" style=3D"font-size:11.0pt">Regarding VDO, it is not a s=
pec yet. How will you cope with VDO once it becomes a spec (approved by NIS=
T)?</span></li><li class=3D"x_MsoListParagraph" style=3D""><span lang=3D"EN=
-US" style=3D"font-size:11.0pt">According to the current text, I could not =
find any field that indicates that the content is
</span><span style=3D"font-size:11.0pt">=93<span lang=3D"EN-US">cve</span>=
=94<span lang=3D"EN-US">. By looking at the information-type, we can see th=
e content is a vulnerability information. But we cannot know the content is=
 a cve note or not until we see the content
 itself. Is my understanding correct? Where can we know that the content is=
 a cve note or not?</span></span></li><li class=3D"x_MsoListParagraph" styl=
e=3D""><span lang=3D"EN-US" style=3D"font-size:11.0pt">According to the cur=
rent text, I understood that we will treat a VDO as a plain text at this mo=
ment. Then, do we indicate that the content is a vulnerability information =
or
 not? It seems to be that we do not indicate so according to the current te=
xt. Is that so?</span></li><li class=3D"x_MsoListParagraph" style=3D""><spa=
n lang=3D"EN-US" style=3D"font-size:11.0pt">Section 4 is concisely represen=
ted. I like it. However, having some examples will help readers to understa=
nd the content properly. How about adding some examples in its appendix
 or in this section?</span></li><li class=3D"x_MsoListParagraph" style=3D""=
><span lang=3D"EN-US" style=3D"font-size:11.0pt">According to section5.1, w=
e MUST send a severity information when sending a vulnerability note. That =
means, we cannot send an early vulnerability information without a score,
 correct? Just a clarification.</span></li><li class=3D"x_MsoListParagraph"=
 style=3D""><span lang=3D"EN-US" style=3D"font-size:11.0pt">I guess you wil=
l make this vulnerability rolie extensible enough. Can you add some sentenc=
es how we could cope with the other vulnerability notes that may emerge in =
the future?</span></li><li class=3D"x_MsoListParagraph" style=3D""><span la=
ng=3D"EN-US" style=3D"font-size:11.0pt">Is it going to be an informational =
RFC? It has several definitive parts. So, I am just asking your intention.<=
/span></li></ol>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Ed=
itorial comments are not important at this stage, but it won</span><span st=
yle=3D"font-size:11.0pt">=92<span lang=3D"EN-US">t harm to list here.</span=
></span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
<p class=3D"x_MsoNormal"><span style=3D"font-size:11.0pt">=93<span lang=3D"=
EN-US">support Vulnerability use cases</span>=94<span lang=3D"EN-US"> -&gt;
</span>=93<span lang=3D"EN-US">support vulnerability use cases</span>=94<sp=
an lang=3D"EN-US">.</span></span></p>
<p class=3D"x_MsoNormal"><span style=3D"font-size:11.0pt">=93<span lang=3D"=
EN-US">a automated and efficient fashion</span>=94<span lang=3D"EN-US"> -&g=
t;
</span>=93<span lang=3D"EN-US">an automated and efficient fashion</span>=94=
<span lang=3D"EN-US">.</span></span></p>
<p class=3D"x_MsoNormal"><span style=3D"font-size:11.0pt">=93<span lang=3D"=
EN-US">a XML</span>=94<span lang=3D"EN-US"> -&gt;
</span>=93<span lang=3D"EN-US">an XML</span>=94<span lang=3D"EN-US"></span>=
</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">In=
 the reference, vdo cannot be a normative reference at this moment, due to =
its document status.</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Th=
ank you, and kind regards,</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">Ta=
ke</span></p>
<p class=3D"x_MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt">&n=
bsp;</span></p>
</div>
</div>
</body>
</html>

--_000_BN3PR09MB0609E3FFC190D170D90076C4F02C0BN3PR09MB0609namp_--


From nobody Mon Apr 15 08:40:23 2019
Return-Path: <noreply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9871203A1; Mon, 15 Apr 2019 08:40:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nancy Cam-Winget via Datatracker <noreply@ietf.org>
To: <alexey.melnikov@isode.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: mile@ietf.org, ncamwing@cisco.com, Nancy Cam-Winget <ncamwing@cisco.com>,  iesg-secretary@ietf.org, mile-chairs@ietf.org
Message-ID: <155534282249.10844.16876543874160336438.idtracker@ietfa.amsl.com>
Date: Mon, 15 Apr 2019 08:40:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/kFw35RjFB0T708UvDmJyX-a0oh4>
Subject: [mile] Publication has been requested for draft-ietf-mile-jsoniodef-08
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2019 15:40:23 -0000

Nancy Cam-Winget has requested publication of draft-ietf-mile-jsoniodef-08 as Proposed Standard on behalf of the MILE working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-mile-jsoniodef/


From nobody Mon Apr 22 18:18:01 2019
Return-Path: <session-request@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 244851200D5; Mon, 22 Apr 2019 18:17:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: mile@ietf.org, takeshi_takahashi@ieee.org, mile-chairs@ietf.org, aamelnikov@fastmail.fm
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155598227914.21208.18069225174590584491.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2019 18:17:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/BzLDs6VAeyk264D8uugaz2sKKgM>
Subject: [mile] mile - New Meeting Session Request for IETF 105
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2019 01:17:59 -0000

A new meeting session request has just been submitted by Takeshi Takahashi, a Chair of the mile working group.


---------------------------------------------------------
Working Group Name: Managed Incident Lightweight Exchange
Area Name: Security Area
Session Requester: Takeshi Takahashi

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority: sacm saag ipsecme suit ipwave i2nsf dots core anima teep cfrg
 Second Priority: 6tisch httpbis tls hip
 Third Priority: 6lo roll ace lwig t2trg


People who must be present:
  Alexey Melnikov
  Nancy Cam-Winget
  David Waltermire
  Takeshi Takahashi

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Mon Apr 22 18:31:42 2019
Return-Path: <session-request@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B1E120120; Mon, 22 Apr 2019 18:31:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: mile@ietf.org, takeshi_takahashi@ieee.org, mile-chairs@ietf.org, aamelnikov@fastmail.fm
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155598309926.21212.4299500578734336064.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2019 18:31:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/DALrYdW9iz0Fpc61-VPup4o1B8A>
Subject: [mile] mile - Update to a Meeting Session Request for IETF 105
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2019 01:31:40 -0000

An update to a meeting session request has just been submitted by Takeshi Takahashi, a Chair of the mile working group.


---------------------------------------------------------
Working Group Name: Managed Incident Lightweight Exchange
Area Name: Security Area
Session Requester: Takeshi Takahashi

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority: sacm saag ipsecme suit i2nsf dots core anima teep cfrg rats tls
 Second Priority: 6tisch httpbis hip ipwave
 Third Priority: 6lo roll ace lwig t2trg


People who must be present:
  Alexey Melnikov
  Nancy Cam-Winget
  David Waltermire
  Takeshi Takahashi

Resources Requested:

Special Requests:
  We would like to add &quot;smart&quot; in the second proiority group (&quot;smart&quot; is currently not an allowed value, thus let me comment this here.)
---------------------------------------------------------


From nobody Fri Apr 26 08:15:10 2019
Return-Path: <jmfmckay@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13DC112051B for <mile@ietfa.amsl.com>; Fri, 26 Apr 2019 08:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20ubEGAzmebB for <mile@ietfa.amsl.com>; Fri, 26 Apr 2019 08:14:57 -0700 (PDT)
Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E28D1205CC for <mile@ietf.org>; Fri, 26 Apr 2019 08:14:57 -0700 (PDT)
Received: by mail-it1-x12a.google.com with SMTP id q19so6321718itk.3 for <mile@ietf.org>; Fri, 26 Apr 2019 08:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=oeMp9OzrxXGNpsQLA5vYI6nVGofVrIhqwFgc9bkFP4I=; b=sXzzxaTyYXt1tdljuP9AVBA97A4zdeJFyYLsSnaaSgAhFQUhV0NsaMVHRPjg1xhSxK XJq3ZdLwQ1g0rRnUzcAFRJEQQih6QWMkAaH57bd3DFUdAC68wqw/M8sWrmFY6aLLwlTv mC2JGWezX6sUl8srF99fxE5qTmj+QyfKKsBkIxOE6mXJJuR48t946V2OX4L5ftbLF+Ts CipDIXjXh1Xa5WHB1usR5SFPhQwcskiPs/KU9gyGB8CHVmhckZLuXiaD4HoNjJmSZsVC s4Awm0+iLWdn4SLXbDeVsrLn3qkQwmykjLHrWplXvfxm4ww4AVldVnnS1y7fbC9Z36F6 U/7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oeMp9OzrxXGNpsQLA5vYI6nVGofVrIhqwFgc9bkFP4I=; b=cqOz6Gj6gPWizMYhQYoER2qGCTReFfQpTUwji6xXer2LDEt3coNq2w9r2Q9nZCr6l9 MID4VCcB+ifHWtRjBGQhRuKtIeMgRf31l0CYvDa9YbTdIFNtlRQ1i0sN6Xqu3yZUbzcy 3GbvpgMBfkQWwqySQ+ptuukzNESBdrTut4NhSww5v0DV1XK9jeuHhZUsurGtTIkc5oU7 pYGQ1AoHyB7cgLTzVNXEYq7SfS2m8qIZPRfH+RDQXKKXAR4p0XdBHyBLNG0oqEhKKs3N XTQmHrxLCa8h/+kmTBJvt187w46I6NBiTcGkQGrTBkGeHvy4BNX8bhmDV2RQFwKpiSXX UhsQ==
X-Gm-Message-State: APjAAAVgsLG7mqqm+BxWzGxzvvxRMAuO/vbPMdk5ALLZYDSs30mfIb7r 2bL3g+osymxEz0lmueCDOjEmmFr1ow75cER4eHE=
X-Google-Smtp-Source: APXvYqx12kW8RjpEVCz92eYewP7OkhbjAqtiatFdDR91u3E8eZ/0+nwGl3V60CS7YaxuaWboK/K/79p6+F8DbfMPTsA=
X-Received: by 2002:a05:660c:350:: with SMTP id b16mr8130969itl.29.1556291696676;  Fri, 26 Apr 2019 08:14:56 -0700 (PDT)
MIME-Version: 1.0
From: Jessica Fitzgerald-McKay <jmfmckay@gmail.com>
Date: Fri, 26 Apr 2019 11:14:45 -0400
Message-ID: <CAM+R6NUCaEiQ9SAz_-iFP3YLqpCdioDwcp3kvb0Vw9V70dyAWQ@mail.gmail.com>
To: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>, mile@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bf520a05877065a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/WHoAdq0xrNz75vr8MeX3_yomCWI>
Subject: [mile] review-- ROLIE Vulnerability Extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2019 15:15:08 -0000

--000000000000bf520a05877065a9
Content-Type: text/plain; charset="UTF-8"

I promised to review the ROLIE Vulnerability Extension during the MILE
meeting in Prague. Comments are below. Please let me know if you have any
questions.

Thanks,
Jess
--------------------------------------------------------------

Section 1--
    The sentence beginning "Today, a number of formats" is a run on
sentence.

    Ditto the sentence beginning "This extension does not attempt".

Section 3--

    Paragraph 1-- change "as per" to "per"

    Paragraph 2-- s/"Provided below is a non-exhaustive list of information
that may be considered to be of a vulnerability information type."/Below is
a non-exhaustive list of information that may be considered vulnerability
information."

    Last sentence of section 3 ("Note again that. . . ") is a run on
sentence.

Section 4--
    Data Format Requirements-- you say "software descriptor" when I think
you mean " vulnerability descriptor". Maybe a copy/paste error?

    Section 4.2.2- s/"utilize"/"used"

Section 6.2-- will you be asking for any new rolie:property names? If so, I
would at least create a TBD section here, as a placeholder.

Section 8-- this is super nitpicky, even for me, but is there a reason to
use lower case references? It stuck me as unconventional, particularly
since you capitalize the RFC references.

--000000000000bf520a05877065a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr" style=
=3D"text-align:left"><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)=
">I promised to review the ROLIE Vulnerability Extension during the MILE me=
eting in Prague. Comments are below. Please let me know if you have=C2=A0an=
y questions.<br><br>Thanks,<br>Jess<br>------------------------------------=
--------------------------<br><br>Section 1--<br>=C2=A0=C2=A0=C2=A0 The sen=
tence beginning <span style=3D"font-family:arial,helvetica,sans-serif"><fon=
t color=3D"rgb(34, 34, 34)">&quot;</font>Today, a number of formats&quot; i=
s a run on sentence. <br>=C2=A0=C2=A0=C2=A0 <br>=C2=A0=C2=A0=C2=A0 Ditto th=
e sentence beginning &quot;This extension does not attempt&quot;.<br><br></=
span></div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)"><span st=
yle=3D"font-family:arial,helvetica,sans-serif">Section 3--<br><br></span></=
div><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)"><span style=3D"=
font-family:arial,helvetica,sans-serif">=C2=A0=C2=A0=C2=A0 Paragraph 1-- ch=
ange &quot;as per&quot; to &quot;per&quot;<br><br></span></div><div class=
=3D"gmail_default" style=3D"color:rgb(0,0,0)"><span style=3D"font-family:ar=
ial,helvetica,sans-serif">=C2=A0=C2=A0=C2=A0 Paragraph 2-- s/&quot;</span><=
span style=3D"font-family:arial,helvetica,sans-serif">Provided below is a n=
on-exhaustive list of information that may be considered to be of a vulnera=
bility information type.&quot;/</span><span style=3D"font-family:arial,helv=
etica,sans-serif">Below is a non-exhaustive list of information that may be=
 considered vulnerability information.&quot;<br><br></span></div><div class=
=3D"gmail_default" style=3D"color:rgb(0,0,0)"><span style=3D"font-family:ar=
ial,helvetica,sans-serif">=C2=A0=C2=A0=C2=A0 Last sentence of section 3 (&q=
uot;Note again that. . . &quot;) is a run on sentence.<br><br></span><span =
style=3D"font-family:arial,helvetica,sans-serif"></span></div><div class=3D=
"gmail_default" style=3D"color:rgb(0,0,0)"><span style=3D"font-family:arial=
,helvetica,sans-serif">Section 4-- <br></span></div><div class=3D"gmail_def=
ault" style=3D"color:rgb(0,0,0)"><span style=3D"font-family:arial,helvetica=
,sans-serif">=C2=A0=C2=A0=C2=A0 Data Format Requirements-- you say &quot;so=
ftware descriptor&quot; when I think you mean &quot; vulnerability descript=
or&quot;. Maybe a copy/paste error?<br><br></span></div><div class=3D"gmail=
_default" style=3D"color:rgb(0,0,0)"><span style=3D"font-family:arial,helve=
tica,sans-serif">=C2=A0=C2=A0=C2=A0 Section 4.2.2- s/&quot;utilize&quot;/&q=
uot;used&quot;<br><br></span></div><div class=3D"gmail_default" style=3D"co=
lor:rgb(0,0,0)"><span style=3D"font-family:arial,helvetica,sans-serif">Sect=
ion 6.2-- will you be asking for any new rolie:property names? If so, I wou=
ld at least create a TBD section here, as a placeholder.<br><br></span></di=
v><div class=3D"gmail_default" style=3D"color:rgb(0,0,0)"><span style=3D"fo=
nt-family:arial,helvetica,sans-serif">Section 8-- this is super nitpicky, e=
ven for me, but is there a reason to use lower case references? It stuck me=
 as unconventional, particularly since you capitalize the RFC references. <=
br></span></div></div></div></div></div>

--000000000000bf520a05877065a9--

