
From nobody Mon Feb  2 15:17:14 2015
Return-Path: <ietf-secretariat-reply@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 EAF781A1B4B for <mile@ietfa.amsl.com>; Mon,  2 Feb 2015 15:17:09 -0800 (PST)
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 jSAwbr3ROGJD; Mon,  2 Feb 2015 15:17:05 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFC51A1B30; Mon,  2 Feb 2015 15:17:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: mile-chairs@tools.ietf.org, draft-ietf-mile-enum-reference-format@tools.ietf.org, mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150202231705.11658.7034.idtracker@ietfa.amsl.com>
Date: Mon, 02 Feb 2015 15:17:05 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/BAs2aKpU_4GyLOZRE4l8rlkfsOc>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.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, 02 Feb 2015 23:17:10 -0000

IESG has approved the document and state has been changed to Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Mon Feb  2 15:17:36 2015
Return-Path: <iesg-secretary@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 7C8141A1B30; Mon,  2 Feb 2015 15:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTPWaaoOOaQ2; Mon,  2 Feb 2015 15:17:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6B81A1B45; Mon,  2 Feb 2015 15:17:05 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150202231705.11658.69928.idtracker@ietfa.amsl.com>
Date: Mon, 02 Feb 2015 15:17:05 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/kEJKaNXHxb_PvEvePEYqTzu4O10>
Cc: mile mailing list <mile@ietf.org>, mile chair <mile-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [mile] Protocol Action: 'IODEF Enumeration Reference Format' to Proposed Standard (draft-ietf-mile-enum-reference-format-14.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, 02 Feb 2015 23:17:17 -0000

The IESG has approved the following document:
- 'IODEF Enumeration Reference Format'
  (draft-ietf-mile-enum-reference-format-14.txt) as Proposed Standard

This document is the product of the Managed Incident Lightweight Exchange
Working Group.

The IESG contact persons are Kathleen Moriarty and Stephen Farrell.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/





Technical Summary

   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 IODEF v1 in RFC 5070) does not indicate how to
   include both of these important pieces of information.

   This memo establishes a stand-alone data format to include both the
   external specification and specific enumeration identification value,
   and establishes an IANA registry to manage external enumeration
   specifications.  While this memo does not update IODEV v1, this
   enumeration reference format is used in IODEF v2 and is applicable to
   other formats that support this class of enumeration references.

Working Group Summary

   This update is straightforward, and there was no difficulty coming to consensus
   on all points. The document received extensive review by the MILE working
   group since its first draft (published on September 1, 2012). The format of the
   identifier has been discussed and revised. Consequently, the structure of IANA
   registry has also been revised over time. All the discussion comments were
   reflected to the current version of the draft. The draft has completed WGLC
   and represents the consensus of the WG with no controversy. We believe the
   working group is solidly behind this. 

Document Quality

   The draft is pretty straightforward way of including references for 
   existing enumeration formats, like CVE in a consistent way within
   an IODEF report and has received adequate review by the working group.

   Expert review has been requested and provided from the 
   AppsDir with a focus on the XML schema changes.

Personnel

  The document shepherd is David Waltermire. 
  The responsible Area Director is Kathleen Moriarty.   

   The document creates an IANA registry for identifiers to be
   referenced from IODEFF's Reference class subject to expert
   review and specification required.


IANA Note

  'The registries use the 5226 'Specification Required' with expert review
   registration policy.


From nobody Mon Feb  2 23:07:27 2015
Return-Path: <ietf-secretariat-reply@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 A0C931A6FEB for <mile@ietfa.amsl.com>; Mon,  2 Feb 2015 23:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 L66zA0vZDiIt; Mon,  2 Feb 2015 23:07:22 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 310811A6F39; Mon,  2 Feb 2015 23:07:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: mile-chairs@tools.ietf.org, draft-ietf-mile-enum-reference-format@tools.ietf.org, mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150203070721.15812.48891.idtracker@ietfa.amsl.com>
Date: Mon, 02 Feb 2015 23:07:21 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/fkWmfPCtJ8uFEvS7TXr4l9NeqdA>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2015 07:07:24 -0000

IANA action state changed to In Progress
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Mon Feb  2 23:16:30 2015
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 C955C1A7006 for <mile@ietfa.amsl.com>; Mon,  2 Feb 2015 23:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level: 
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, 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 Vb033SvURnlX for <mile@ietfa.amsl.com>; Mon,  2 Feb 2015 23:16:26 -0800 (PST)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52FD61A6FF6 for <mile@ietf.org>; Mon,  2 Feb 2015 23:16:26 -0800 (PST)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id t137GOcc001071 for <mile@ietf.org>; Tue, 3 Feb 2015 16:16:24 +0900 (JST)
Received: from mail1.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp  with ESMTP id t137GOuX001068 for <mile@ietf.org>; Tue, 3 Feb 2015 16:16:24 +0900 (JST)
Received: from mail1.nict.go.jp (localhost [127.0.0.1]) by mail1.nict.go.jp (NICT Mail) with ESMTP id 58EC3163B3 for <mile@ietf.org>; Tue,  3 Feb 2015 16:16:24 +0900 (JST)
Received: from VAIO (unknown [133.243.119.37]) by mail1.nict.go.jp (NICT Mail) with ESMTP id 50DA95348 for <mile@ietf.org>; Tue,  3 Feb 2015 16:16:24 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Tue, 3 Feb 2015 16:16:31 +0900
Message-ID: <000d01d03f81$5605b4d0$02111e70$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01D03FCC.C5EF0A80"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdA/gVAVvwRq3HDgQcWa+r9CRrfwcA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.5 at zenith1
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/9tc_NZC_yo-odD_3zb3zFh4enKw>
Subject: Re: [mile] Protocol Action: 'IODEF Enumeration Reference Format' to Proposed Standard (draft-ietf-mile-enum-reference-format-14.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: Tue, 03 Feb 2015 07:16:29 -0000

This is a multipart message in MIME format.

------=_NextPart_000_000E_01D03FCC.C5EF0A80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Congratulation.

I would like to thank the authors for the continuous efforts to bring the
draft to this stage.

 

Kind regards,

Take



2015-02-03 8:17 GMT+09:00 The IESG <iesg-secretary@ietf.org>:
> The IESG has approved the following document:
> - 'IODEF Enumeration Reference Format'
>   (draft-ietf-mile-enum-reference-format-14.txt) as Proposed Standard
>
> This document is the product of the Managed Incident Lightweight Exchange
> Working Group.
>
> The IESG contact persons are Kathleen Moriarty and Stephen Farrell.
>
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/
>
>
>
>
>
> Technical Summary
>
>    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 IODEF v1 in RFC 5070) does not indicate how to
>    include both of these important pieces of information.
>
>    This memo establishes a stand-alone data format to include both the
>    external specification and specific enumeration identification value,
>    and establishes an IANA registry to manage external enumeration
>    specifications.  While this memo does not update IODEV v1, this
>    enumeration reference format is used in IODEF v2 and is applicable to
>    other formats that support this class of enumeration references.
>
> Working Group Summary
>
>    This update is straightforward, and there was no difficulty coming to
consensus
>    on all points. The document received extensive review by the MILE
working
>    group since its first draft (published on September 1, 2012). The
format of the
>    identifier has been discussed and revised. Consequently, the structure
of IANA
>    registry has also been revised over time. All the discussion comments
were
>    reflected to the current version of the draft. The draft has completed
WGLC
>    and represents the consensus of the WG with no controversy. We believe
the
>    working group is solidly behind this.
>
> Document Quality
>
>    The draft is pretty straightforward way of including references for
>    existing enumeration formats, like CVE in a consistent way within
>    an IODEF report and has received adequate review by the working group.
>
>    Expert review has been requested and provided from the
>    AppsDir with a focus on the XML schema changes.
>
> Personnel
>
>   The document shepherd is David Waltermire.
>   The responsible Area Director is Kathleen Moriarty.
>
>    The document creates an IANA registry for identifiers to be
>    referenced from IODEFF's Reference class subject to expert
>    review and specification required.
>
>
> IANA Note
>
>   'The registries use the 5226 'Specification Required' with expert review
>    registration policy.
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile



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


------=_NextPart_000_000E_01D03FCC.C5EF0A80
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"\FF2D\FF33 \30B4\30B7\30C3\30AF";
	panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
	{font-family:"\FF2D\FF33 \30B4\30B7\30C3\30AF";
	panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
	{font-family:"\@\FF2D\FF33 \30B4\30B7\30C3\30AF";
	panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Arial","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.17
	{mso-style-type:personal-compose;
	font-family:"Arial","sans-serif";
	color:windowtext;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Arial","sans-serif";}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
--></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=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#222222'>Congratulation.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#222222'>I would =
like to thank the authors for the continuous efforts to bring the draft =
to this stage.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#222222'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#222222'>Kind =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#222222'>Take<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#222222'><br><br><span =
style=3D'background:white'>2015-02-03 8:17 GMT+09:00 The IESG =
&lt;iesg-secretary@ietf.org&gt;:</span><br><span =
style=3D'background:white'>&gt; The IESG has approved the following =
document:</span><br><span style=3D'background:white'>&gt; - 'IODEF =
Enumeration Reference Format'</span><br><span =
style=3D'background:white'>&gt; &nbsp; =
(draft-ietf-mile-enum-reference-format-14.txt) as Proposed =
Standard</span><br><span style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; This document is the product of the =
Managed Incident Lightweight Exchange</span><br><span =
style=3D'background:white'>&gt; Working Group.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; The IESG contact persons are Kathleen =
Moriarty and Stephen Farrell.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; A URL of this Internet Draft =
is:</span><br><span style=3D'background:white'>&gt; =
http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/</s=
pan><br><span style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; Technical Summary</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;The Incident Object =
Description Exchange Format (IODEF) is an XML</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;data representation =
framework for sharing information about computer</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;security incidents. =
&nbsp;In IODEF, the Reference class provides</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;references to externally =
specified information such as a</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;vulnerability, IDS alert, =
malware sample, advisory, or attack</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;technique. &nbsp;In =
practice, these references are based on external</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;enumeration specifications =
that define both the enumeration format</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;and the specific =
enumeration values, but the IODEF Reference class</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;(as specified in IODEF v1 =
in RFC 5070) does not indicate how to</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;include both of these =
important pieces of information.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;This memo establishes a =
stand-alone data format to include both the</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;external specification and =
specific enumeration identification value,</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;and establishes an IANA =
registry to manage external enumeration</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;specifications. &nbsp;While =
this memo does not update IODEV v1, this</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;enumeration reference =
format is used in IODEF v2 and is applicable to</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;other formats that support =
this class of enumeration references.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; Working Group Summary</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;This update is =
straightforward, and there was no difficulty coming to =
consensus</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;on all points. The document received extensive review by the MILE =
working</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;group since its first draft (published on September 1, 2012). The =
format of the</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;identifier has been discussed and revised. Consequently, the =
structure of IANA</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;registry has also been revised over time. All the discussion =
comments were</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;reflected to the current version of the draft. The draft has =
completed WGLC</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;and represents the consensus of the WG with no controversy. We =
believe the</span><br><span style=3D'background:white'>&gt; &nbsp; =
&nbsp;working group is solidly behind this.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; Document Quality</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;The draft is pretty =
straightforward way of including references for</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;existing enumeration =
formats, like CVE in a consistent way within</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;an IODEF report and has =
received adequate review by the working group.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;Expert review has been =
requested and provided from the</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;AppsDir with a focus on the =
XML schema changes.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; Personnel</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; The document shepherd is David =
Waltermire.</span><br><span style=3D'background:white'>&gt; &nbsp; The =
responsible Area Director is Kathleen Moriarty.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;The document creates an =
IANA registry for identifiers to be</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;referenced from IODEFF's =
Reference class subject to expert</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;review and specification =
required.</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; IANA Note</span><br><span =
style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; &nbsp; 'The registries use the 5226 =
'Specification Required' with expert review</span><br><span =
style=3D'background:white'>&gt; &nbsp; &nbsp;registration =
policy.</span><br><span style=3D'background:white'>&gt;</span><br><span =
style=3D'background:white'>&gt; =
_______________________________________________</span><br><span =
style=3D'background:white'>&gt; mile mailing list</span><br><span =
style=3D'background:white'>&gt; mile@ietf.org</span><br><span =
style=3D'background:white'>&gt; =
https://www.ietf.org/mailman/listinfo/mile</span><br><br><br><br><span =
style=3D'background:white'>--<span =
class=3Dapple-converted-space>&nbsp;</span></span><br><span =
style=3D'background:white'>--</span><br><span =
style=3D'background:white'>Takeshi Takahashi, Ph.D.</span><br><span =
style=3D'background:white'>+81 80 3490 2971</span><br><span =
style=3D'background:white'>http://www.taketaka.com/</span><br><span =
style=3D'background:white'>&nbsp;</span></span><span lang=3DEN-US =
style=3D'font-size:10.0pt'><o:p></o:p></span></p></div></body></html>
------=_NextPart_000_000E_01D03FCC.C5EF0A80--


From nobody Tue Feb  3 01:26:44 2015
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 3C6621A0062 for <mile@ietfa.amsl.com>; Tue,  3 Feb 2015 01:26:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0waLcHH0JJf for <mile@ietfa.amsl.com>; Tue,  3 Feb 2015 01:26:41 -0800 (PST)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D1F01A0040 for <mile@ietf.org>; Tue,  3 Feb 2015 01:26:41 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id hz20so49500391lab.6 for <mile@ietf.org>; Tue, 03 Feb 2015 01:26:39 -0800 (PST)
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; bh=5juwi40hruv37WyBCIrB+UZasWrepEF7LN82x3UyB0c=; b=QjgpwECqyNDJy7dEKoqHrDjTZdw4DX8orR63bnA68AAjhN9O0LSIo6Tv1rMot04dcA Mw7uVr4la9+J6TtTMsb5u4Xt24EmS2YYUWhb2Hj9GTtHXBDXIoYsEOPK2245F2oHeHHB Am/NpWIF8v/lk8faGX9PMgZoxATOFn+4/tYbYeFDJYtClk2PgCtXFbw061Klv0Whk4F8 DWj0+G/NHk1MY7g9+VLODxjBK0ilwBzznIKMiWGV96gIpE3T/gP1FvRM8jaR7teWZCUS 4ruSTILpyb7W/zm8UZR1RmmCcqFHIqFJklhIbbahcPVC0/RRZpNStuEFtzwHWzeeo0Pt 9u6g==
MIME-Version: 1.0
X-Received: by 10.112.243.12 with SMTP id wu12mr23735919lbc.91.1422955599602;  Tue, 03 Feb 2015 01:26:39 -0800 (PST)
Received: by 10.25.209.5 with HTTP; Tue, 3 Feb 2015 01:26:39 -0800 (PST)
In-Reply-To: <000d01d03f81$5605b4d0$02111e70$@nict.go.jp>
References: <000d01d03f81$5605b4d0$02111e70$@nict.go.jp>
Date: Tue, 3 Feb 2015 10:26:39 +0100
Message-ID: <CAA=AuEeg8M9f1GPthVJaKP152Yqr96a6evr7CB74kod6+jOdsw@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/A7u-9QzYZpR_i7llWxS4JwPB2Lc>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Protocol Action: 'IODEF Enumeration Reference Format' to Proposed Standard (draft-ietf-mile-enum-reference-format-14.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: Tue, 03 Feb 2015 09:26:43 -0000

Congratulations and thank you
Well done

2015-02-03 8:16 GMT+01:00 Takeshi Takahashi <takeshi_takahashi@nict.go.jp>:
> Congratulation.
>
> I would like to thank the authors for the continuous efforts to bring the
> draft to this stage.
>
>
>
> Kind regards,
>
> Take
>
>
>
> 2015-02-03 8:17 GMT+09:00 The IESG <iesg-secretary@ietf.org>:
>> The IESG has approved the following document:
>> - 'IODEF Enumeration Reference Format'
>>   (draft-ietf-mile-enum-reference-format-14.txt) as Proposed Standard
>>
>> This document is the product of the Managed Incident Lightweight Exchange
>> Working Group.
>>
>> The IESG contact persons are Kathleen Moriarty and Stephen Farrell.
>>
>> A URL of this Internet Draft is:
>> http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/
>>
>>
>>
>>
>>
>> Technical Summary
>>
>>    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 IODEF v1 in RFC 5070) does not indicate how to
>>    include both of these important pieces of information.
>>
>>    This memo establishes a stand-alone data format to include both the
>>    external specification and specific enumeration identification value,
>>    and establishes an IANA registry to manage external enumeration
>>    specifications.  While this memo does not update IODEV v1, this
>>    enumeration reference format is used in IODEF v2 and is applicable to
>>    other formats that support this class of enumeration references.
>>
>> Working Group Summary
>>
>>    This update is straightforward, and there was no difficulty coming to
>> consensus
>>    on all points. The document received extensive review by the MILE
>> working
>>    group since its first draft (published on September 1, 2012). The
>> format of the
>>    identifier has been discussed and revised. Consequently, the structure
>> of IANA
>>    registry has also been revised over time. All the discussion comments
>> were
>>    reflected to the current version of the draft. The draft has completed
>> WGLC
>>    and represents the consensus of the WG with no controversy. We believe
>> the
>>    working group is solidly behind this.
>>
>> Document Quality
>>
>>    The draft is pretty straightforward way of including references for
>>    existing enumeration formats, like CVE in a consistent way within
>>    an IODEF report and has received adequate review by the working group.
>>
>>    Expert review has been requested and provided from the
>>    AppsDir with a focus on the XML schema changes.
>>
>> Personnel
>>
>>   The document shepherd is David Waltermire.
>>   The responsible Area Director is Kathleen Moriarty.
>>
>>    The document creates an IANA registry for identifiers to be
>>    referenced from IODEFF's Reference class subject to expert
>>    review and specification required.
>>
>>
>> IANA Note
>>
>>   'The registries use the 5226 'Specification Required' with expert review
>>    registration policy.
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>
>
> --
> --
> Takeshi Takahashi, Ph.D.
> +81 80 3490 2971
> http://www.taketaka.com/
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>


From nobody Tue Feb  3 16:33:03 2015
Return-Path: <ietf-secretariat-reply@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 96FA51A1B71 for <mile@ietfa.amsl.com>; Tue,  3 Feb 2015 16:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 zPc_QIZthnVB; Tue,  3 Feb 2015 16:33:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF8D1A1B5D; Tue,  3 Feb 2015 16:33:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: mile-chairs@tools.ietf.org, draft-ietf-mile-enum-reference-format@tools.ietf.org, mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150204003300.31459.62995.idtracker@ietfa.amsl.com>
Date: Tue, 03 Feb 2015 16:33:00 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/WOjNIZEzA0RSL8egeNu681QJk8Q>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 00:33:01 -0000

IESG state changed to RFC Ed Queue from Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Wed Feb 11 13:06:13 2015
Return-Path: <ietf-secretariat-reply@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 2D87C1A1A79; Wed, 11 Feb 2015 13:06:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 0v5cr4Yw5zdi; Wed, 11 Feb 2015 13:06:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0981A0451; Wed, 11 Feb 2015 13:06:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <mile-chairs@ietf.org>, <draft-ietf-mile-enum-reference-format@ietf.org>, <mile@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211210608.11224.39195.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 13:06:08 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/pxmTj9xzB8JB40wQSt26PuQWxgQ>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 21:06:10 -0000

IANA action state changed to On Hold
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Mon Feb 23 12:38:40 2015
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 361651A6F02 for <mile@ietfa.amsl.com>; Mon, 23 Feb 2015 12:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 6fsr4QHY6RTF for <mile@ietfa.amsl.com>; Mon, 23 Feb 2015 12:38:37 -0800 (PST)
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 5D64A1A6F03 for <mile@ietf.org>; Mon, 23 Feb 2015 12:38:37 -0800 (PST)
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 t1NKcaCT026736 for <mile@ietf.org>; Mon, 23 Feb 2015 15:38:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1424723916; bh=dlhkkYv06DkLfvJsuC6llCfnTlkkan1maa+edd0ql3U=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=CLGp4CpS9eFyZWr+GsS7ghJlVasetzt5Y9RUAKSG/xwnDJQjsYGjJwZYo/osOd78G R3W8gylgdQhX25G+vgAXM7VlU8I/IMQxblt85fZgT08AFsZiSXaFMshL5X0Vj5jc92 zrsXSINNCNQv2grb2xPe9QBD4+K2Ijxk+Y0X7FmI=
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 t1NKcZM7013774 for <mile@ietf.org>; Mon, 23 Feb 2015 15:38:35 -0500
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.0210.002; Mon, 23 Feb 2015 15:38:32 -0500
From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Reconsidering enumerated attribute extensions
Thread-Index: AdBPqIu8pwSMIL44TWiXW7SzqEDCzA==
Date: Mon, 23 Feb 2015 20:38:32 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@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/9Kh_URwRFevbErmQrOiKkKGr5aA>
Subject: [mile] Reconsidering enumerated attribute extensions
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, 23 Feb 2015 20:38:39 -0000

Hello!

In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute extension m=
echanism was introduced per Issue #3 [1] using an IANA registry.  This draf=
t updated Section 5.1 and deprecated the old technique that used "@ext-*" a=
ttributes.  This planned change triggered discussion in Hawaii [2] which ne=
cessitated further discussion on the list.

There are at least three options to adding enumerated values not specified =
in the schema.  The possible courses of action with some analysis are as fo=
llows:

(1) Extend attributes using ONLY the @ext-* attribute
** Where is the text? See version -00 to -09 of the draft and the original =
RFC5070
** Background: came from RFC5070
** Pros: private extensions are possible
** Cons: commonly accepted extensions never get standardized

(2) Extend the attributes using ONLY an IANA registry
** Where is the text? See version -10 (current draft)
** Background: came from formative discussions during MILE chartering; cons=
istent with other IETF mechanisms
** Pros: commonly accepted extensions get standardized through a well defin=
ed mechanism
** Pros: XML validation is can check all of the values
** Cons: private extensions are not possible
** Cons: need to periodically rebuild the schema from IANA registry

(3) Extend the attributes with BOTH the @ext-* and the IANA registry
** Where is the text? Combine Section 5.1 of the -09 and -10 drafts=20
** Pros: private extensions are possible
** Pros: commonly accepted extensions are standardized
** Cons: need to periodically rebuild the schema from IANA registry
** Cons: more optional attributes in the schema

What does the working group think?  Are there more options to consider?

Option #3 seems to present the most flexibility.

Roman

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
[2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile


From nobody Tue Feb 24 00:58:18 2015
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 14E241A8725 for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 00:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Er48OLYj2Gkt for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 00:58:13 -0800 (PST)
Received: from nudmzsv0007.nc3a.nato.int (sm01nl.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 50A051A871E for <mile@ietf.org>; Tue, 24 Feb 2015 00:58:12 -0800 (PST)
Received: from nrdmzmg01.nr.ncia.nato.int (clear01nl [172.31.48.153]) by nudmzsv0007.nc3a.nato.int (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t1O8w6eH032499; Tue, 24 Feb 2015 09:58:08 +0100
Received: from NRNCIEX0012.NR.NC3A (nrnciex0012.nr.nc3a [172.31.36.68] (may be forged)) by nrdmzmg01.nr.ncia.nato.int (8.14.7/8.14.7) with ESMTP id t1O8nUcg007674; Tue, 24 Feb 2015 09:49:31 +0100
Received: from NRNCIEX0011.NR.NC3A (172.31.36.67) by NRNCIEX0012.NR.NC3A (172.31.36.68) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Tue, 24 Feb 2015 09:57:02 +0100
Received: from NRNCIEX0011.NR.NC3A ([fe80::d593:112a:b87f:87f8]) by NRNCIEX0011.NR.NC3A ([fe80::d593:112a:b87f:87f8%12]) with mapi id 15.00.1044.021; Tue, 24 Feb 2015 09:57:02 +0100
From: Lagadec Philippe <Philippe.Lagadec@ncia.nato.int>
To: "Roman D. Danyliw" <rdd@cert.org>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Reconsidering enumerated attribute extensions
Thread-Index: AdBPqIu8pwSMIL44TWiXW7SzqEDCzAAZtuEw
Date: Tue, 24 Feb 2015 08:57:02 +0000
Message-ID: <62e55caa30e2498caf91c8d8cafc8eb8@NRNCIEX0011.NR.NC3A>
References: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.79.212.245]
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/JCgD_FIoqFgQFHbaSg-g1xolQuw>
Subject: Re: [mile] Reconsidering enumerated attribute extensions
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, 24 Feb 2015 08:58:17 -0000

Hello,

I vote for option #3:=20
I think it is useful to keep the possibility of adding private extensions t=
o all enumerations, and also to keep as much backwards compatibility with I=
ODEFv1 as possible for existing implementations.

Regards,

Philippe.

-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman D. Danyliw
Sent: 23 February 2015 21:39
To: mile@ietf.org
Subject: [mile] Reconsidering enumerated attribute extensions

Hello!

In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute extension m=
echanism was introduced per Issue #3 [1] using an IANA registry.  This draf=
t updated Section 5.1 and deprecated the old technique that used "@ext-*" a=
ttributes.  This planned change triggered discussion in Hawaii [2] which ne=
cessitated further discussion on the list.

There are at least three options to adding enumerated values not specified =
in the schema.  The possible courses of action with some analysis are as fo=
llows:

(1) Extend attributes using ONLY the @ext-* attribute
** Where is the text? See version -00 to -09 of the draft and the original =
RFC5070
** Background: came from RFC5070
** Pros: private extensions are possible
** Cons: commonly accepted extensions never get standardized

(2) Extend the attributes using ONLY an IANA registry
** Where is the text? See version -10 (current draft)
** Background: came from formative discussions during MILE chartering; cons=
istent with other IETF mechanisms
** Pros: commonly accepted extensions get standardized through a well defin=
ed mechanism
** Pros: XML validation is can check all of the values
** Cons: private extensions are not possible
** Cons: need to periodically rebuild the schema from IANA registry

(3) Extend the attributes with BOTH the @ext-* and the IANA registry
** Where is the text? Combine Section 5.1 of the -09 and -10 drafts=20
** Pros: private extensions are possible
** Pros: commonly accepted extensions are standardized
** Cons: need to periodically rebuild the schema from IANA registry
** Cons: more optional attributes in the schema

What does the working group think?  Are there more options to consider?

Option #3 seems to present the most flexibility.

Roman

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
[2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile

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


From nobody Tue Feb 24 05:34:50 2015
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 44CD61A1A88 for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 05:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id duCWFHTATtka for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 05:34:47 -0800 (PST)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (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 462C21A1A82 for <mile@ietf.org>; Tue, 24 Feb 2015 05:34:47 -0800 (PST)
Received: by wggx12 with SMTP id x12so5291875wgg.11 for <mile@ietf.org>; Tue, 24 Feb 2015 05:34:46 -0800 (PST)
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=oM9GFhsYbyq2reDe6wu3dit6xyKruXusiXdVRdF1BT4=; b=zegBJHAd1NiuPrisW0n1wK1spYXvx6vq+PpotfpOuSne2HDF2347ig10f1Jj/+58Gy 4VjCO4o76szDO4S5toORa1PxWsPHxS0ECklUcxT5foLDyq5k8bpVp1+F5FnYpz62Nw76 5L7wcIw4xZyPB+XH3c05XR6kagxOwE9uDH04lH9kreIGREB6W3XepoD4LIlA9fDltOpd Z7HsTfY0MJa9Ul0IiPpPi0utvLdUGra/MrDeiqQKAZNgPvH0RatNThraN21nXRLu/VIL kB0FZXeAt/VLWSX/eYEOwzVvslKdFpcjmWpNkAYZEslbAulBL4mKWWpxDngVcKJU30Fr Wa/A==
MIME-Version: 1.0
X-Received: by 10.194.92.9 with SMTP id ci9mr32199895wjb.142.1424784885962; Tue, 24 Feb 2015 05:34:45 -0800 (PST)
Received: by 10.28.158.3 with HTTP; Tue, 24 Feb 2015 05:34:45 -0800 (PST)
In-Reply-To: <62e55caa30e2498caf91c8d8cafc8eb8@NRNCIEX0011.NR.NC3A>
References: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon> <62e55caa30e2498caf91c8d8cafc8eb8@NRNCIEX0011.NR.NC3A>
Date: Tue, 24 Feb 2015 14:34:45 +0100
Message-ID: <CAA=AuEf7CZL=LpVZkbjMxUiY+Cot=GrA+hSi7KTZ+TsWnCx=Zw@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: Lagadec Philippe <Philippe.Lagadec@ncia.nato.int>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/qIgbuf6nsrccQ0x8obEgge3Stgg>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Reconsidering enumerated attribute extensions
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, 24 Feb 2015 13:34:49 -0000

Hi,

I would concur for option #3
Meantime, could the IODEF Enumeration Reference Format
(draft-ietf-mile-enum-reference-format) be reused somehow?

Best regards



2015-02-24 9:57 GMT+01:00 Lagadec Philippe <Philippe.Lagadec@ncia.nato.int>=
:
> Hello,
>
> I vote for option #3:
> I think it is useful to keep the possibility of adding private extensions=
 to all enumerations, and also to keep as much backwards compatibility with=
 IODEFv1 as possible for existing implementations.
>
> Regards,
>
> Philippe.
>
> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman D. Danyliw
> Sent: 23 February 2015 21:39
> To: mile@ietf.org
> Subject: [mile] Reconsidering enumerated attribute extensions
>
> Hello!
>
> In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute extension=
 mechanism was introduced per Issue #3 [1] using an IANA registry.  This dr=
aft updated Section 5.1 and deprecated the old technique that used "@ext-*"=
 attributes.  This planned change triggered discussion in Hawaii [2] which =
necessitated further discussion on the list.
>
> There are at least three options to adding enumerated values not specifie=
d in the schema.  The possible courses of action with some analysis are as =
follows:
>
> (1) Extend attributes using ONLY the @ext-* attribute
> ** Where is the text? See version -00 to -09 of the draft and the origina=
l RFC5070
> ** Background: came from RFC5070
> ** Pros: private extensions are possible
> ** Cons: commonly accepted extensions never get standardized
>
> (2) Extend the attributes using ONLY an IANA registry
> ** Where is the text? See version -10 (current draft)
> ** Background: came from formative discussions during MILE chartering; co=
nsistent with other IETF mechanisms
> ** Pros: commonly accepted extensions get standardized through a well def=
ined mechanism
> ** Pros: XML validation is can check all of the values
> ** Cons: private extensions are not possible
> ** Cons: need to periodically rebuild the schema from IANA registry
>
> (3) Extend the attributes with BOTH the @ext-* and the IANA registry
> ** Where is the text? Combine Section 5.1 of the -09 and -10 drafts
> ** Pros: private extensions are possible
> ** Pros: commonly accepted extensions are standardized
> ** Cons: need to periodically rebuild the schema from IANA registry
> ** Cons: more optional attributes in the schema
>
> What does the working group think?  Are there more options to consider?
>
> Option #3 seems to present the most flexibility.
>
> Roman
>
> [1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
> [2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Tue Feb 24 07:11:12 2015
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 AAF8B1A87CA for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 07:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.598
X-Spam-Level: 
X-Spam-Status: No, score=0.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 aHX7XVmrw05v for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 07:11:08 -0800 (PST)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2D31A87A5 for <mile@ietf.org>; Tue, 24 Feb 2015 07:11:08 -0800 (PST)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id t1OFAwQL026583; Wed, 25 Feb 2015 00:10:58 +0900 (JST)
Received: from TakeVaioVJP13 (ssh.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp  with ESMTP id t1OFAvYP026579; Wed, 25 Feb 2015 00:10:57 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Roman D. Danyliw'" <rdd@cert.org>, "'Jerome Athias'" <athiasjerome@gmail.com>, "'Lagadec Philippe'" <Philippe.Lagadec@ncia.nato.int>
References: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon> <62e55caa30e2498caf91c8d8cafc8eb8@NRNCIEX0011.NR.NC3A> <CAA=AuEf7CZL=LpVZkbjMxUiY+Cot=GrA+hSi7KTZ+TsWnCx=Zw@mail.gmail.com>
In-Reply-To: <CAA=AuEf7CZL=LpVZkbjMxUiY+Cot=GrA+hSi7KTZ+TsWnCx=Zw@mail.gmail.com>
Date: Wed, 25 Feb 2015 00:11:19 +0900
Message-ID: <007b01d05044$24f13490$6ed39db0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJaksvBTG2XYDDyhADxL5T8ftOQjQGbTevRAS+sKlWb1QoXwA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.5 at zenith2
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/7SCMz6pjnmWvKzFIInYWn1S20rw>
Cc: mile@ietf.org
Subject: Re: [mile] Reconsidering enumerated attribute extensions
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, 24 Feb 2015 15:11:10 -0000

Hi,

+1 to the option #3

Thank you.

Take


> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Jerome Athias
> Sent: Tuesday, February 24, 2015 10:35 PM
> To: Lagadec Philippe
> Cc: mile@ietf.org
> Subject: Re: [mile] Reconsidering enumerated attribute extensions
> 
> Hi,
> 
> I would concur for option #3
> Meantime, could the IODEF Enumeration Reference Format
> (draft-ietf-mile-enum-reference-format) be reused somehow?
> 
> Best regards
> 
> 
> 
> 2015-02-24 9:57 GMT+01:00 Lagadec Philippe
<Philippe.Lagadec@ncia.nato.int>:
> > Hello,
> >
> > I vote for option #3:
> > I think it is useful to keep the possibility of adding private
extensions
> to all enumerations, and also to keep as much backwards compatibility with
> IODEFv1 as possible for existing implementations.
> >
> > Regards,
> >
> > Philippe.
> >
> > -----Original Message-----
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman D. Danyliw
> > Sent: 23 February 2015 21:39
> > To: mile@ietf.org
> > Subject: [mile] Reconsidering enumerated attribute extensions
> >
> > Hello!
> >
> > In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute
extension
> mechanism was introduced per Issue #3 [1] using an IANA registry.  This
draft
> updated Section 5.1 and deprecated the old technique that used "@ext-*"
> attributes.  This planned change triggered discussion in Hawaii [2] which
> necessitated further discussion on the list.
> >
> > There are at least three options to adding enumerated values not
specified
> in the schema.  The possible courses of action with some analysis are as
> follows:
> >
> > (1) Extend attributes using ONLY the @ext-* attribute
> > ** Where is the text? See version -00 to -09 of the draft and the
original
> RFC5070
> > ** Background: came from RFC5070
> > ** Pros: private extensions are possible
> > ** Cons: commonly accepted extensions never get standardized
> >
> > (2) Extend the attributes using ONLY an IANA registry
> > ** Where is the text? See version -10 (current draft)
> > ** Background: came from formative discussions during MILE chartering;
> consistent with other IETF mechanisms
> > ** Pros: commonly accepted extensions get standardized through a well
defined
> mechanism
> > ** Pros: XML validation is can check all of the values
> > ** Cons: private extensions are not possible
> > ** Cons: need to periodically rebuild the schema from IANA registry
> >
> > (3) Extend the attributes with BOTH the @ext-* and the IANA registry
> > ** Where is the text? Combine Section 5.1 of the -09 and -10 drafts
> > ** Pros: private extensions are possible
> > ** Pros: commonly accepted extensions are standardized
> > ** Cons: need to periodically rebuild the schema from IANA registry
> > ** Cons: more optional attributes in the schema
> >
> > What does the working group think?  Are there more options to consider?
> >
> > Option #3 seems to present the most flexibility.
> >
> > Roman
> >
> > [1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
> > [2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Tue Feb 24 13:17:03 2015
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98F2A1A892A for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 13:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fxy6AkNUYn67 for <mile@ietfa.amsl.com>; Tue, 24 Feb 2015 13:17:00 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0797B1A891A for <mile@ietf.org>; Tue, 24 Feb 2015 13:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2289; q=dns/txt; s=iport; t=1424812620; x=1426022220; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=RVdhtO+sFbVoBQTcgcXiYbPJT1eFsuA1HPEwXN0dU8I=; b=QD4hxXt0vPRnP9jSNIyi5VKqXyebGqSDoOLe5o6gvtgcIAtA/LR08F4x GvUlXnTYCauobQbwjCIrsMz71+uDqukIKKL0QVti/AL7G46i1MCtwlaQP v1DbKN1I5xdbLfFNT0U8vcf+91ZhQtD5xqjT11SR0eCtj8kI/CCtobH5O I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtBQA06exU/4cNJK1bgwZSWgTAc4IgCoVwAoEvQwEBAQEBAXyEDwEBAQQBAQE3NBcEAgEIEQQBAQsUCQcnCxQJCAEBBAESCAGIJg3UewEBAQEBAQEBAQEBAQEBAQEBAQEBAReLE4QpFDgGgxGBFAWNaYFyg2CHOZFnIoNubwGBAyQcfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,641,1418083200"; d="scan'208";a="126567322"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP; 24 Feb 2015 21:16:59 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1OLGxkG014013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Feb 2015 21:16:59 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.156]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0195.001; Tue, 24 Feb 2015 15:16:59 -0600
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Roman D. Danyliw" <rdd@cert.org>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Reconsidering enumerated attribute extensions
Thread-Index: AdBPqIu8pwSMIL44TWiXW7SzqEDCzAAzoYWg
Date: Tue, 24 Feb 2015 21:16:58 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A751534C299@xmb-rcd-x10.cisco.com>
References: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.108.5]
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/4ZLmrTfQH33IHLkbznQukxzjRSA>
Subject: Re: [mile] Reconsidering enumerated attribute extensions
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, 24 Feb 2015 21:17:01 -0000

+1 for (3)


-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Roman D. Danyliw
Sent: Monday, February 23, 2015 3:39 PM
To: mile@ietf.org
Subject: [mile] Reconsidering enumerated attribute extensions

Hello!

In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute extension m=
echanism was introduced per Issue #3 [1] using an IANA registry.  This draf=
t updated Section 5.1 and deprecated the old technique that used "@ext-*" a=
ttributes.  This planned change triggered discussion in Hawaii [2] which ne=
cessitated further discussion on the list.

There are at least three options to adding enumerated values not specified =
in the schema.  The possible courses of action with some analysis are as fo=
llows:

(1) Extend attributes using ONLY the @ext-* attribute
** Where is the text? See version -00 to -09 of the draft and the original =
RFC5070
** Background: came from RFC5070
** Pros: private extensions are possible
** Cons: commonly accepted extensions never get standardized

(2) Extend the attributes using ONLY an IANA registry
** Where is the text? See version -10 (current draft)
** Background: came from formative discussions during MILE chartering; cons=
istent with other IETF mechanisms
** Pros: commonly accepted extensions get standardized through a well defin=
ed mechanism
** Pros: XML validation is can check all of the values
** Cons: private extensions are not possible
** Cons: need to periodically rebuild the schema from IANA registry

(3) Extend the attributes with BOTH the @ext-* and the IANA registry
** Where is the text? Combine Section 5.1 of the -09 and -10 drafts=20
** Pros: private extensions are possible
** Pros: commonly accepted extensions are standardized
** Cons: need to periodically rebuild the schema from IANA registry
** Cons: more optional attributes in the schema

What does the working group think?  Are there more options to consider?

Option #3 seems to present the most flexibility.

Roman

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
[2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile

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


From nobody Tue Feb 24 18:06:18 2015
Return-Path: <ietf-secretariat-reply@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 CFB191A907B; Tue, 24 Feb 2015 18:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 FvV2ZAEwFjFk; Tue, 24 Feb 2015 18:06:15 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A751A9077; Tue, 24 Feb 2015 18:06:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <mile-chairs@ietf.org>, <draft-ietf-mile-enum-reference-format@ietf.org>, <mile@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150225020615.20052.10256.idtracker@ietfa.amsl.com>
Date: Tue, 24 Feb 2015 18:06:15 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/aUUiL4f2WR6cankFpwYVHh_VAzY>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 02:06:17 -0000

IANA action state changed to In Progress
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Tue Feb 24 20:06:18 2015
Return-Path: <ietf-secretariat-reply@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 D31E61A1A04; Tue, 24 Feb 2015 20:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=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 Or-dLhOXvVWB; Tue, 24 Feb 2015 20:06:14 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C63A1A907B; Tue, 24 Feb 2015 20:06:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <mile-chairs@ietf.org>, <draft-ietf-mile-enum-reference-format@ietf.org>, <mile@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150225040613.21835.82195.idtracker@ietfa.amsl.com>
Date: Tue, 24 Feb 2015 20:06:13 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/w6aM_0-MeL59-DkKRC1pfqbO9Bs>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-enum-reference-format-14.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Feb 2015 04:06:16 -0000

IANA action state changed to Waiting on Authors
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-mile-enum-reference-format/


From nobody Wed Feb 25 00:18:28 2015
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 5696A1A6EE9 for <mile@ietfa.amsl.com>; Wed, 25 Feb 2015 00:18:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level: 
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, 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 1qFP-kquXQ84 for <mile@ietfa.amsl.com>; Wed, 25 Feb 2015 00:18:25 -0800 (PST)
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 3B2A51A6EE0 for <mile@ietf.org>; Wed, 25 Feb 2015 00:18:24 -0800 (PST)
Received: from [IPv6:2001:200:180:299:3553:7530:7005:2c4e] (unknown [IPv6:2001:200:180:299:3553:7530:7005:2c4e]) (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 BEF99B6E1E5F; Wed, 25 Feb 2015 17:18:23 +0900 (JST)
Message-ID: <54ED853E.7010005@nc.u-tokyo.ac.jp>
Date: Wed, 25 Feb 2015 17:18:06 +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.4.0
MIME-Version: 1.0
To: "Roman D. Danyliw" <rdd@cert.org>, "mile@ietf.org" <mile@ietf.org>
References: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93A72CB@marathon>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/Uzgflriqwk_FUessp0UqsqWqI2k>
Subject: Re: [mile] Reconsidering enumerated attribute extensions
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, 25 Feb 2015 08:18:27 -0000

Option (3) is the best for me. Thank you for your clarifying pros and cons!

On 2015/02/24 5:38, Roman D. Danyliw wrote:
> Hello!
>
> In the -10 draft of draft-ietf-mile-rfc5070bis, a new attribute extension mechanism was introduced per Issue #3 [1] using an IANA registry.  This draft updated Section 5.1 and deprecated the old technique that used "@ext-*" attributes.  This planned change triggered discussion in Hawaii [2] which necessitated further discussion on the list.
>
> There are at least three options to adding enumerated values not specified in the schema.  The possible courses of action with some analysis are as follows:
>
> (1) Extend attributes using ONLY the @ext-* attribute
> ** Where is the text? See version -00 to -09 of the draft and the original RFC5070
> ** Background: came from RFC5070
> ** Pros: private extensions are possible
> ** Cons: commonly accepted extensions never get standardized
>
> (2) Extend the attributes using ONLY an IANA registry
> ** Where is the text? See version -10 (current draft)
> ** Background: came from formative discussions during MILE chartering; consistent with other IETF mechanisms
> ** Pros: commonly accepted extensions get standardized through a well defined mechanism
> ** Pros: XML validation is can check all of the values
> ** Cons: private extensions are not possible
> ** Cons: need to periodically rebuild the schema from IANA registry
>
> (3) Extend the attributes with BOTH the @ext-* and the IANA registry
> ** Where is the text? Combine Section 5.1 of the -09 and -10 drafts
> ** Pros: private extensions are possible
> ** Pros: commonly accepted extensions are standardized
> ** Cons: need to periodically rebuild the schema from IANA registry
> ** Cons: more optional attributes in the schema
>
> What does the working group think?  Are there more options to consider?
>
> Option #3 seems to present the most flexibility.
>
> Roman
>
> [1] http://trac.tools.ietf.org/wg/mile/trac/ticket/3
> [2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>


From nobody Fri Feb 27 12:47:46 2015
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 C94981A015F for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 12:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level: 
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 2EUsR55CCa16 for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 12:47:42 -0800 (PST)
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 092841A00C5 for <mile@ietf.org>; Fri, 27 Feb 2015 12:47:41 -0800 (PST)
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 t1RKleqt017794 for <mile@ietf.org>; Fri, 27 Feb 2015 15:47:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1425070061; bh=82q4iBWVHUafRCK98h/MOFylQWDX1pK9i49kHfg3024=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=Qa7vuKTJPrOxQ5Y+9BIHufgfwIu2Q+sFcBLkkBKsJJx+oayik8kxSz548JcU9lhtH McIbMgz0NpUAPXl21xsFNt6zcVhdi9fZBkKJz0IMuHf9XL6o6tTEMc4pN9HlA8mTtQ XeoC+AHfIOKxC/IYoWRSbR/5sRN6lialKUF1Avs4=
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 t1RKlfLE026648 for <mile@ietf.org>; Fri, 27 Feb 2015 15:47:41 -0500
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.0210.002; Fri, 27 Feb 2015 15:47:37 -0500
From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Defining RelatedDNS
Thread-Index: AdBSwc9s3wtgDiaDSEqpk4CdhQcpTw==
Date: Fri, 27 Feb 2015 20:47:37 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD93AC2B4@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/_Qf5wBlflbQHpP71eqYqMq7qHIc>
Subject: [mile] Defining RelatedDNS
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, 27 Feb 2015 20:47:44 -0000

Hello!

RelatedDNS in 5070bis is intended to describe arbitrary DNS records.  While=
 the intent of class is understanding the specified representation has not =
been clarified.  The issue is tracked in Issue #39 [1] and there is prior d=
iscussion on the list [2].  At the Honolulu meeting [3], this topic generat=
ed sufficient discussion requiring it to be brought back to the list for fu=
rther discussion.

Possible options include:

(1) At the Honolulu meeting, Paul Hoffman suggested a draft providing a JSO=
N notation for DNS records.
Background: draft-hoffman-dns-in-json-02
Options: reference outright, convert from JSON to XML
Pro: well-defined format elsewhere
Con: is JSON inside XML a kludge?
Con: experimental draft as a normative reference to standards track documen=
t

(2) A comma separated value list of DNS fields
Background: http://www.ietf.org/mail-archive/web/mile/current/msg01329.html
Pro: simple
Con: not sufficiently descriptive as currently suggested

(3) Defining RelatedDNS as iodef:AdditionalData and requiring an extension
Pro: no extra work required
Con: defers action on a need previously articulated in the community

(4) Define an alternative representation for RelatedDNS
Pro: opportunity to create an appropriately tailored solution
Con: requires new work/documentation

Are there other options?  What do you think?

Roman

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/39
[2] http://www.ietf.org/mail-archive/web/mile/current/msg01325.html
[3] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile


From nobody Fri Feb 27 13:39:13 2015
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 1C9101A0204 for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 13:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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 GZN_gM25jON2 for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 13:39:10 -0800 (PST)
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 8536E1A0235 for <mile@ietf.org>; Fri, 27 Feb 2015 13:39:00 -0800 (PST)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by shetland.sei.cmu.edu (8.14.4/8.14.4/1408) with ESMTP id t1RLcxqZ003592 for <mile@ietf.org>; Fri, 27 Feb 2015 16:38:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1425073139; bh=M/OlLqOpSyWftCc58VN2+8GFc+9Qz18pWM0uUoacmY0=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version:Sender:Reply-To:Cc: In-Reply-To:References; b=ArqTcwVJ39a/Rw66wAFVeikQbPZnas/v4KLvZtIVYjvifwWIXSGLq7scZyeBR7Fe2 nbfnLTtb6mJ9mvQ4a6sVXCSvKDCgbcLu9S5xd7tO71GMbcwNkE3cGVnqvxyviBCTRa BUILZPteQEvXuK+GkQXjJRryaZcZAGAsyFwg3z3g=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by timber.sei.cmu.edu (8.14.4/8.14.4/1456) with ESMTP id t1RLcwqr020096 for <mile@ietf.org>; Fri, 27 Feb 2015 16:38:58 -0500
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.0210.002; Fri, 27 Feb 2015 16:38:58 -0500
From: "Roman D. Danyliw" <rdd@cert.org>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Keeping the HashData@valid attribute?
Thread-Index: AdBS1DY/CSlNaoePTSeP3X3hajQwmQ==
Date: Fri, 27 Feb 2015 21:38:58 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFCD93AC555@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/EWKgR-KqQv4fSQ6qJiWHs182wQQ>
Subject: [mile] Keeping the HashData@valid attribute?
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, 27 Feb 2015 21:39:12 -0000

Hello!

The -10 version of 5070bis introduced rewrote the existing ambiguous text t=
o address Issue #29 [1], clarifying the scope of HashData@valid.  This new =
text in Section 3.27 is as follows:

   valid
      Optional.  Indicates whether a given certificate has a valid
      signature.  An invalid signature may be due to an invalid
      certificate chain, a signature not decoding properly, or a
      certificate contents not matching the hash.

      1.  yes.  The certificate is valid.
      2.  no.  The certificate is not valid.

At the Honolulu meeting this change prompted discussion summarized as follo=
ws in the meeting minutes [2]:

As to the HashData@valid attribute:
Q1: (Jim Shot) Why is it there?
A: (Roman Danyliw) Not sure.
A: (Jim Shot) Perhaps it should be removed
A: (Chris Inacio) Might be useful in pDNS because capturing DNS signatures =
is expensive and wasteful
A: (Paul Hoffman) It's an "invalid bit".  Get rid of it.
A: (David Waltermire) It was intended to convey that a certificate was foun=
d to be invalid.  Concur to drop.
A: A question as to whether to drop this attribute will be put on the list.

There has been limited discussion of this issue on the mailing list as well=
 [3] which requested a better definition.

What does the group want to do?  Could advocacy for keeping the @valid attr=
ibute please respond to the list with better language.  For those that thin=
k we should remove it, can you also let your perspective be known on the li=
st. =20

Roman

[1] http://trac.tools.ietf.org/wg/mile/trac/ticket/29
[2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
[3] http://www.ietf.org/mail-archive/web/mile/current/msg01161.html




From nobody Fri Feb 27 17:45:51 2015
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 9E7121A1AA7 for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 17:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.598
X-Spam-Level: 
X-Spam-Status: No, score=0.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4Tm4HpPBLALY for <mile@ietfa.amsl.com>; Fri, 27 Feb 2015 17:45:49 -0800 (PST)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EACE51A0066 for <mile@ietf.org>; Fri, 27 Feb 2015 17:45:48 -0800 (PST)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id t1S1jlse005044; Sat, 28 Feb 2015 10:45:47 +0900 (JST)
Received: from TakeVaioVJP13 (ssh.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id t1S1jk0G004987; Sat, 28 Feb 2015 10:45:46 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Sat, 28 Feb 2015 10:46:11 +0900
Message-ID: <000101d052f8$554ea990$ffebfcb0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdBS9wifGH9njJKsQoWNrKTUZFzpKw==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.5 at zenith1
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/WnQKY8O2lSxCqE5Q144xCkzLsxM>
Cc: mile-chairs@tools.ietf.org
Subject: [mile] IETF 92 - 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: Sat, 28 Feb 2015 01:45:50 -0000

Hello all,

The MILE session in Dallas is scheduled on Wednesday from 9:00 to 11:30.
https://datatracker.ietf.org/meeting/92/agenda.html

If you have any agenda to discuss, please kindly let us know.

Regards,
Take


> -----Original Message-----
> From: "IETF Secretariat" [mailto:agenda@ietf.org]
> Sent: Saturday, February 28, 2015 7:27 AM
> To: takeshi_takahashi@nict.go.jp
> Cc: mile-ads@tools.ietf.org; alexey.melnikov@isode.com;
> takeshi_takahashi@nict.go.jp
> Subject: mile - Requested session has been scheduled for IETF 92
>=20
> Dear Takeshi Takahashi,
>=20
> The session(s) that you have requested have been scheduled.
> Below is the scheduled session information followed by the original =
request.
>=20
> mile Session 1 (1:30:00)
>     Wednesday, Morning Session I 0900-1130
>     Room Name: Continental size: 90
>     ---------------------------------------------
>=20
>=20
>=20
> Request Information:
>=20
>=20
> ---------------------------------------------------------
> Working Group Name: Managed Incident Lightweight Exchange Area Name: =
Security
> Area Session Requester: Takeshi Takahashi
>=20
> Number of Sessions: 1
> Length of Session(s):  1.5 Hours
> Number of Attendees: 25
> Conflicts to Avoid:
>  First Priority: saag sacm radext dime tls dane kitten appsawg httpbis =
netmod
> Second Priority: oauth httpauth ace
>=20
>=20
>=20
> Special Requests:
>=20
> ---------------------------------------------------------


From nobody Sat Feb 28 00:21:50 2015
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 932741A00ED for <mile@ietfa.amsl.com>; Sat, 28 Feb 2015 00:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1isW1-ifup62 for <mile@ietfa.amsl.com>; Sat, 28 Feb 2015 00:21:47 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (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 A7A4C1A0199 for <mile@ietf.org>; Sat, 28 Feb 2015 00:21:46 -0800 (PST)
Received: by widex7 with SMTP id ex7so4576514wid.1 for <mile@ietf.org>; Sat, 28 Feb 2015 00:21:45 -0800 (PST)
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; bh=Jh1dhEn0UZ/09G5thefi035WJYnubLhKkPmi+xN//vg=; b=GqW0C8u9DcOpz93R4SUZsVQakGLtBmuks28NMVDlULzi7neeZSltjuDtNia/fLPOjz RgKPpMWLtZclIEUEX8/EhDDPwzhHDbL5uqw9lDxGP9aERveZhD/0izFUvQGNftGfnwAD EYzwANsi2/19HXdDYgpj8IhrwtqzdrZoKy71db/aQTMPM7Fn3ELXaMM88o4eu+OPcEYP 9qOjeRS4j/h/Zs8pG+uo4mPnV1B06TikciLv91mq0jo1flHo4lJOcbY56h6k6EzwPUBx kDbqxrh7GiK1lw+IPpKpYkNCrN6r+F949GZoYWRs3vYSoZFonRn9X3YlY27+yiMmJR+N 3fXw==
MIME-Version: 1.0
X-Received: by 10.194.93.134 with SMTP id cu6mr35384457wjb.79.1425111705066; Sat, 28 Feb 2015 00:21:45 -0800 (PST)
Received: by 10.28.158.10 with HTTP; Sat, 28 Feb 2015 00:21:45 -0800 (PST)
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93AC555@marathon>
References: <359EC4B99E040048A7131E0F4E113AFCD93AC555@marathon>
Date: Sat, 28 Feb 2015 09:21:45 +0100
Message-ID: <CAA=AuEd4TmYzbB60b+3ssJqyzHhwrUMYr3ykwOL=GWuFMQ3uSQ@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Roman D. Danyliw" <rdd@cert.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/H_5OcT1fdR_dWv_2S_cF0_24wi0>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Keeping the HashData@valid attribute?
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: Sat, 28 Feb 2015 08:21:48 -0000

+1 to drop
(used and useful in 3.27.1. Certificate Class)
NB: in 3.27.1. Certificate Class, "certificate chain" could be
"certificate chain of trust"

2015-02-27 22:38 GMT+01:00 Roman D. Danyliw <rdd@cert.org>:
> Hello!
>
> The -10 version of 5070bis introduced rewrote the existing ambiguous text to address Issue #29 [1], clarifying the scope of HashData@valid.  This new text in Section 3.27 is as follows:
>
>    valid
>       Optional.  Indicates whether a given certificate has a valid
>       signature.  An invalid signature may be due to an invalid
>       certificate chain, a signature not decoding properly, or a
>       certificate contents not matching the hash.
>
>       1.  yes.  The certificate is valid.
>       2.  no.  The certificate is not valid.
>
> At the Honolulu meeting this change prompted discussion summarized as follows in the meeting minutes [2]:
>
> As to the HashData@valid attribute:
> Q1: (Jim Shot) Why is it there?
> A: (Roman Danyliw) Not sure.
> A: (Jim Shot) Perhaps it should be removed
> A: (Chris Inacio) Might be useful in pDNS because capturing DNS signatures is expensive and wasteful
> A: (Paul Hoffman) It's an "invalid bit".  Get rid of it.
> A: (David Waltermire) It was intended to convey that a certificate was found to be invalid.  Concur to drop.
> A: A question as to whether to drop this attribute will be put on the list.
>
> There has been limited discussion of this issue on the mailing list as well [3] which requested a better definition.
>
> What does the group want to do?  Could advocacy for keeping the @valid attribute please respond to the list with better language.  For those that think we should remove it, can you also let your perspective be known on the list.
>
> Roman
>
> [1] http://trac.tools.ietf.org/wg/mile/trac/ticket/29
> [2] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
> [3] http://www.ietf.org/mail-archive/web/mile/current/msg01161.html
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Sat Feb 28 00:40:00 2015
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 2085B1A033B for <mile@ietfa.amsl.com>; Sat, 28 Feb 2015 00:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvLF-DXr3dW7 for <mile@ietfa.amsl.com>; Sat, 28 Feb 2015 00:39:58 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (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 088751A004C for <mile@ietf.org>; Sat, 28 Feb 2015 00:39:58 -0800 (PST)
Received: by wesw55 with SMTP id w55so24409336wes.4 for <mile@ietf.org>; Sat, 28 Feb 2015 00:39:56 -0800 (PST)
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=t/PJnGtuOzTsJq+BnUlmaz0JW2uTPH0ZhVsdMOCPPpI=; b=ptSr4WwQiNvrwHAkliB3fxC/IEFvQ4qeVaCWMWmk6Vri8FbHTa5OqVukxcGTNypKvL i55XvHTGXmUIzzGVAEd3X/fXWIJp0V6RZM0LhVS0PFnLQyAQF70BVyzkrHcfENvy8sEs YSrNfexOG4F+twBv/ng2o+u9PvBoM2rRk2IdFWLmEBcbKBoaPXxK8WyB8cjF2XZsYvNL hCSqNrBOBNj+Z54MzF0qvQTRHzpTDlEnEcvykYVRTzzKmRzbd4crtaCRrspQxCa8+LDm dWm+/PFziVKQICAcYGanPmcaJGOSzb/mk5PCfrcuTqMo0Jiyu6fIX3+p9qjV+4NCQazf TlXw==
MIME-Version: 1.0
X-Received: by 10.180.214.99 with SMTP id nz3mr14883273wic.82.1425112796760; Sat, 28 Feb 2015 00:39:56 -0800 (PST)
Received: by 10.28.158.10 with HTTP; Sat, 28 Feb 2015 00:39:56 -0800 (PST)
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD93AC2B4@marathon>
References: <359EC4B99E040048A7131E0F4E113AFCD93AC2B4@marathon>
Date: Sat, 28 Feb 2015 09:39:56 +0100
Message-ID: <CAA=AuEdMnJT3TjvEXwPizphSYJsbPG+6zH0GBP6VRC=Dm5peGw@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
To: "Roman D. Danyliw" <rdd@cert.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/CtKKUieTRa7sUnrl5SqoD4dlNa4>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Defining RelatedDNS
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: Sat, 28 Feb 2015 08:40:00 -0000

1) In short, I would prefer XML for Description, JSON for implementation.
2) not sufficiently descriptive as currently suggested
3) 4) consider:
http://cybox.mitre.org/XMLSchema/objects/DNS_Query/2.1/DNS_Query_Object.xsd
http://cybox.mitre.org/XMLSchema/objects/DNS_Record/2.1/DNS_Record_Object.x=
sd



2015-02-27 21:47 GMT+01:00 Roman D. Danyliw <rdd@cert.org>:
> Hello!
>
> RelatedDNS in 5070bis is intended to describe arbitrary DNS records.  Whi=
le the intent of class is understanding the specified representation has no=
t been clarified.  The issue is tracked in Issue #39 [1] and there is prior=
 discussion on the list [2].  At the Honolulu meeting [3], this topic gener=
ated sufficient discussion requiring it to be brought back to the list for =
further discussion.
>
> Possible options include:
>
> (1) At the Honolulu meeting, Paul Hoffman suggested a draft providing a J=
SON notation for DNS records.
> Background: draft-hoffman-dns-in-json-02
> Options: reference outright, convert from JSON to XML
> Pro: well-defined format elsewhere
> Con: is JSON inside XML a kludge?
> Con: experimental draft as a normative reference to standards track docum=
ent
>
> (2) A comma separated value list of DNS fields
> Background: http://www.ietf.org/mail-archive/web/mile/current/msg01329.ht=
ml
> Pro: simple
> Con: not sufficiently descriptive as currently suggested
>
> (3) Defining RelatedDNS as iodef:AdditionalData and requiring an extensio=
n
> Pro: no extra work required
> Con: defers action on a need previously articulated in the community
>
> (4) Define an alternative representation for RelatedDNS
> Pro: opportunity to create an appropriately tailored solution
> Con: requires new work/documentation
>
> Are there other options?  What do you think?
>
> Roman
>
> [1] http://trac.tools.ietf.org/wg/mile/trac/ticket/39
> [2] http://www.ietf.org/mail-archive/web/mile/current/msg01325.html
> [3] http://www.ietf.org/proceedings/91/minutes/minutes-91-mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

