
From nobody Mon Aug  1 09:41:36 2016
Return-Path: <ncamwing@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7687E12DCAD for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 09:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level: 
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q0XlFInZvIqx for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 09:41:34 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DBCF12D1A2 for <mile@ietf.org>; Mon,  1 Aug 2016 09:41:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1904; q=dns/txt; s=iport; t=1470069694; x=1471279294; h=from:to:subject:date:message-id:mime-version; bh=iHPANA9HL3X1j8KSengyhwLt+feRJKkUgX++sDo1tMM=; b=inQT20LfJxkCPSdjHXmNESfjQSpxazrKJJPaOoNeKfMaD6aZVQAPHAHD vs8LGd+ijPoIextFrmycXFEBf8kS8stRN0gGHkxpSu15vMNN/P70KZUcE r9D6huVOW73HujFZ2v74QKRwiiyAxgPQIP2eQK01NYxzNn51UtqN/21li w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BTAgACe59X/4QNJK1dgndOVoECtAeFB?= =?us-ascii?q?oF9JIcpOBQBAQEBAQEBXRwLhGUdUR0BDAFzJwSIRA6hH59SAQEBBwEBAQEBHQW?= =?us-ascii?q?VEgWZMwGBNYRiiGeBa4RaiHqQJgEeNoN6iAR/AQEB?=
X-IronPort-AV: E=Sophos;i="5.28,456,1464652800";  d="scan'208,217";a="304662479"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Aug 2016 16:41:33 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u71GfXrE023121 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <mile@ietf.org>; Mon, 1 Aug 2016 16:41:33 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 1 Aug 2016 12:41:32 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 1 Aug 2016 12:41:32 -0400
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
Thread-Index: AQHR7BOPuQ0OeSBg6kWugmke/WvvVA==
Date: Mon, 1 Aug 2016 16:41:32 +0000
Message-ID: <D3C4C9CA.18380B%ncamwing@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.84.110]
Content-Type: multipart/alternative; boundary="_000_D3C4C9CA18380Bncamwingciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/4PRRQU_vAKTn3stcFnNNCN4-t-o>
Subject: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2016 16:41:35 -0000

--_000_D3C4C9CA18380Bncamwingciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

At IETF 96 Berlin MILE meeting there was agreement that we should adopt  ht=
tps://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/
as a WG draft.  This is the official call for adoption for that draft.

Please reply with any comments or concerns along your support of this actio=
n to the mailing list.

Thanks,
Nancy



--_000_D3C4C9CA18380Bncamwingciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <F7E939AD945A904595CA8CB1C27562EB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hello,</div>
<div><br>
</div>
<div>At IETF 96 Berlin MILE meeting there was agreement that we should adop=
t &nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-takahashi-mile-js=
oniodef/">https://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/<=
/a></div>
<div>as a WG draft. &nbsp;This is the official call for adoption for that d=
raft.</div>
<div><br>
</div>
<div><span style=3D"font-family: Calibri; font-size: medium;">Please reply =
with any comments or concerns along your support of this action to the mail=
ing list.&nbsp;</span></div>
<div><span style=3D"font-family: Calibri; font-size: medium;"><br>
</span></div>
<div><span style=3D"font-family: Calibri; font-size: medium;">Thanks,</span=
></div>
<div><span style=3D"font-family: Calibri; font-size: medium;">Nancy</span><=
/div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_D3C4C9CA18380Bncamwingciscocom_--


From nobody Mon Aug  1 09:50:27 2016
Return-Path: <ncamwing@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E8E12DCE2; Mon,  1 Aug 2016 09:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level: 
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sTp6PDklLK7E; Mon,  1 Aug 2016 09:50:25 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7AB012DCE0; Mon,  1 Aug 2016 09:50:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1618; q=dns/txt; s=iport; t=1470070223; x=1471279823; h=from:to:subject:date:message-id:mime-version; bh=o7QXyWAlggq+RzrzXgikyTSBPlhbemeF2uDIQTnKGgs=; b=C2/fQXBWP4HOT2ck8d4bBJLgio3ElURoxyEXZa4vo1IhrsP+QgJ5a8OE lQNbELZeCXFXzJQ/EsDNrpnsugLCrrTdL/pkdR81s8j/OjOYbjmOeKEDl zm2RMNGaWbpG+aHA4WUnfebXixcU8EdwPE4bYxInVB12RTV5tyPtVdLKe Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BSAgBffJ9X/5JdJa1dgndOVoECtAeFB?= =?us-ascii?q?oF9JIcpOBQBAQEBAQEBXSeEVRCBCwELAXQnBAGIQw7AcQEBAQEGAQEBAR4Fine?= =?us-ascii?q?Jfh0Fjk+KZAGBNYRiiGeBa4RaiHqMMIN2AR42g3qIBH8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,456,1464652800";  d="scan'208,217";a="303487687"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2016 16:50:23 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u71GoMH8025190 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Aug 2016 16:50:23 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 1 Aug 2016 12:50:22 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 1 Aug 2016 12:50:22 -0400
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: "mile@ietf.org" <mile@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Thread-Topic: Reviews requested for https://datatracker.ietf.org/doc/draft-ietf-mile-rolie/
Thread-Index: AQHR7BTLAZNW3VcT+k28l1JHCXAegg==
Date: Mon, 1 Aug 2016 16:50:22 +0000
Message-ID: <D3C4CBDC.183820%ncamwing@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.84.110]
Content-Type: multipart/alternative; boundary="_000_D3C4CBDC183820ncamwingciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/XrLI4inFiD5rgT-vSI7MPCE9bHk>
Subject: [mile] Reviews requested for https://datatracker.ietf.org/doc/draft-ietf-mile-rolie/
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2016 16:50:26 -0000

--_000_D3C4CBDC183820ncamwingciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

The MILE WG is progressing with the ROLIE draft which is in WGLC, but it ha=
s received sparse review at best.
We would like to get at least 6 or 7 reviewers to provide comments beefore =
we can proceed to the next step.

Please let us know if you can review (and by when) as we'd like to get this=
 shepherded by November 2016.

Thanks,
 Nancy and Takeshi



--_000_D3C4CBDC183820ncamwingciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <1885BECCA622CC4993D9D63D396C4F37@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hello,</div>
<div><br>
</div>
<div>The MILE WG is progressing with the ROLIE draft which is in WGLC, but =
it has received sparse review at best.</div>
<div>We would like to get at least 6 or 7 reviewers to provide comments bee=
fore we can proceed to the next step.</div>
<div><br>
</div>
<div>Please let us know if you can review (and by when) as we&#8217;d like =
to get this shepherded by November 2016.</div>
<div><br>
</div>
<div>Thanks,&nbsp;</div>
<div>&nbsp;Nancy and Takeshi</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_D3C4CBDC183820ncamwingciscocom_--


From nobody Mon Aug  1 13:42:46 2016
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF34012D8CD for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 13:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level: 
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z25IkzkV0oyu for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 13:42:43 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 208FD12D8C5 for <mile@ietf.org>; Mon,  1 Aug 2016 13:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6992; q=dns/txt; s=iport; t=1470084163; x=1471293763; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=GB9t6QoiIayCZ4AT639mVo133nJGehyh5hyNGQ5E4JM=; b=SrUw34GEjxVSh5x6P5ZpM9gz0c3tN+NvFVESjjbSNQEjxayKHBk8CgoE UGjFt8sMJ/pQAxZ6+axzZw27EHKRA98J2qm3wsWGz3GPty/rHN1CmVP/P lCj4u0r1gAixinWzoR5esOBziiXX/gVWs8Bd4WK5An2OJc4+GzlBxTwm4 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A2AgC8s59X/5pdJa1dgndOVnwGtAeFB?= =?us-ascii?q?oF9JIV5AoEwOBQBAQEBAQEBXSeEXgEBBR0QQRsCAQgRBAEBKAcyFAkIAgQBEgi?= =?us-ascii?q?IKQ7AUwEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhiqETYR2hSUFmTMBhheIYIFyh?= =?us-ascii?q?FqIeowwg3YBHjaDem6HFn8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,457,1464652800";  d="scan'208,217";a="304605126"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2016 20:42:42 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u71Kgg3H009483 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <mile@ietf.org>; Mon, 1 Aug 2016 20:42:42 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 1 Aug 2016 15:42:41 -0500
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1210.000; Mon, 1 Aug 2016 15:42:41 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, "mile@ietf.org" <mile@ietf.org>
Thread-Topic: Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
Thread-Index: AQHR7BOPuQ0OeSBg6kWugmke/WvvVKA0kb1A
Date: Mon, 1 Aug 2016 20:42:41 +0000
Message-ID: <22437a2cda434a7abcb916aef93730a8@XCH-ALN-010.cisco.com>
References: <D3C4C9CA.18380B%ncamwing@cisco.com>
In-Reply-To: <D3C4C9CA.18380B%ncamwing@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.108.7]
Content-Type: multipart/alternative; boundary="_000_22437a2cda434a7abcb916aef93730a8XCHALN010ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/KoN7Jm_n4E5c7TPdhRPvFDSnIR4>
Subject: Re: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Aug 2016 20:42:45 -0000

--_000_22437a2cda434a7abcb916aef93730a8XCHALN010ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+1 on adopting it as a WG item.

The misunderstanding that XML based info sharing standards are impractical =
for today where JSON is widely preferred is pretty common and this draft ca=
n help explain that the data representation does not really pose limitation=
s to the schema itself.


From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Nancy Cam-Winget (nc=
amwing)
Sent: Monday, August 01, 2016 12:42 PM
To: mile@ietf.org
Subject: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG dra=
ft

Hello,

At IETF 96 Berlin MILE meeting there was agreement that we should adopt  ht=
tps://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/
as a WG draft.  This is the official call for adoption for that draft.

Please reply with any comments or concerns along your support of this actio=
n to the mailing list.

Thanks,
Nancy



--_000_22437a2cda434a7abcb916aef93730a8XCHALN010ciscocom_
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-micr=
osoft-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=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",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.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">&#43;1 on adopting it as a WG item.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D">The misunderstanding that XML based i=
nfo sharing standards are impractical for today where JSON is widely prefer=
red is pretty common and this draft can help explain
 that the data representation does not really pose limitations to the schem=
a itself.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> mile [mailto:mile-bounces@ietf=
.org]
<b>On Behalf Of </b>Nancy Cam-Winget (ncamwing)<br>
<b>Sent:</b> Monday, August 01, 2016 12:42 PM<br>
<b>To:</b> mile@ietf.org<br>
<b>Subject:</b> [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as=
 WG draft<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Hello,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">At IETF 96 Berlin MILE meeting there wa=
s agreement that we should adopt &nbsp;<a href=3D"https://datatracker.ietf.=
org/doc/draft-takahashi-mile-jsoniodef/">https://datatracker.ietf.org/doc/d=
raft-takahashi-mile-jsoniodef/</a><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">as a WG draft. &nbsp;This is the offici=
al call for adoption for that draft.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Please reply with any comments or conce=
rns along your support of this action to the mailing list.&nbsp;</span><spa=
n style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;colo=
r:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Thanks,</span><span style=3D"font-size:=
10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:black"><o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Nancy</span><span style=3D"font-size:10=
.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:black"><o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_22437a2cda434a7abcb916aef93730a8XCHALN010ciscocom_--


From nobody Mon Aug  1 22:30:41 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4EF12B024 for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 22:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.188
X-Spam-Level: 
X-Spam-Status: No, score=-3.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBIrlgoXmXTa for <mile@ietfa.amsl.com>; Mon,  1 Aug 2016 22:30:37 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C09212B01C for <mile@ietf.org>; Mon,  1 Aug 2016 22:30:37 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id u725UXZF023124; Tue, 2 Aug 2016 14:30:33 +0900 (JST)
Received: from DESKTOP2JPR8KD (ssh1.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id u725UW04022510; Tue, 2 Aug 2016 14:30:32 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Adam Montville'" <adam.w.montville@gmail.com>, "'Banghart, Stephen A. \(Fed\)'" <stephen.banghart@nist.gov>
Date: Tue, 2 Aug 2016 14:30:30 +0900
Message-ID: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdHsfgS4wv2XnaCZQye2rRFytLxXYA==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith1
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/z5iAfvlDyJK4zisNF2w0qwy1ovc>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 05:30:40 -0000

Hi Stephen and all,

In my understanding, we will have at least two drafts: one for general
purpose (current ROLIE core draft) and another for incident response
purpose.
If Option B talks about separate drafts that are neither of the two =
drafts,
I agree with you and Adam=92s comment.

Apart from options A and B, it could be also fine to talk about
authorization and authorization in the general purpose draft (ROLIE core
draft) without mandating any specific technique.

Kind regards,
Take



From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
Sent: Monday, August 1, 2016 12:52 AM
To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication

Hi Stephen,

If the primary purpose of ROLIE is to make public information available,
then leaving the authentication piece to separate drafts (your Option B)
seems to make sense. =A0My interest in ROLIE is centered on the ability =
to
syndicate configuration checklists, which is a class of security =
automation
information generally available to the public.=A0

I suspect that information sharing organizations may have a different
perspective.

I cannot authoritatively speak to which mechanism(s) would be best, but =
it
seems to be the case that OAUTH is widely used for many REST APIs in the
wild. =A0I have not seen XACML used in such a context. =A0I'm also not =
sure that
we should get into authorization.

Kind regards,

Adam

On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
<mailto:stephen.banghart@nist.gov> wrote:

Hello all,
=A0
Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there =
are
some issues that we wanted to bring to the mailing list for discussion. =
This
e-mail references GitHub issue #34
(https://github.com/CISecurity/ROLIE/issues/34). The text from the issue =
is
duplicated here for convenience:=A0
=A0
Authentication and authorization can be handled using a number of =
different
mechanisms, for this reason it=92s not clear if we can require a =
specific
mechanism in the ROLIE core. More discussion is needed with the working
group to determine a way forward.=A0
=A0
Proposals:
=A0
- A: Select one or more authentication and authorization mechanisms as
mandatory to implement (MTI).
- B: Address these issues in separate drafts.=A0
=A0
=A0
Support for OAUTH, http-auth, and XACML has been discussed in a limited
capacity previously. Given that deployed solutions may require different
authentication and authorization solutions based on differing deployment
requirements, we are concerned about requiring any single solution.
Furthermore, defining requirements for multiple solutions will add
significant page count to the draft. As a result, we are leaning towards
proposal B which would allow for some modularity in solutions through
additional drafts.
=A0
Are there any concerns with going this route?
=A0
If option A is desired, we could use some help from someone =
knowledgeable in
using authentication and authorization solutions with HTTP RESTful =
services.
=A0
Thanks,
Stephen Banghart
=A0
_______________________________________________
mile mailing list
mailto:mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile




From nobody Tue Aug  2 08:23:49 2016
Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE01A12D624 for <mile@ietfa.amsl.com>; Tue,  2 Aug 2016 08:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COIJGO_32Sof for <mile@ietfa.amsl.com>; Tue,  2 Aug 2016 08:23:46 -0700 (PDT)
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (mail-dm2gcc01on0105.outbound.protection.outlook.com [23.103.201.105]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43AD812D79E for <mile@ietf.org>; Tue,  2 Aug 2016 08:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VtjCmR4+/IGSzZG3tH+ICSxvT4Qg011dwd2d2Y9B+PU=; b=Ia6SZ+oj0Y3OWR02x6IOp3pMoi7hseGKkFKs5X6JfTVRLWWZmSMWXG2/45srNdeoxNvxswXLY9eO/BKO3T1aJaIbJj4iLadkn8oHRWIUTnbR/Nd+qUFBmf9imLYQXjh8DyGa/zNIxCofS2o9663iBmwODkf/YhZ4rwtcDttuiCw=
Received: from SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) by SN1PR09MB0959.namprd09.prod.outlook.com (10.162.102.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Tue, 2 Aug 2016 15:23:42 +0000
Received: from SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) by SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) with mapi id 15.01.0549.022; Tue, 2 Aug 2016 15:23:42 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
Thread-Topic: [mile] ROLIE Authorization and Authentication
Thread-Index: AdHsfgS4wotwpaMPTJ+yy7j9Kj4evQAUFghw
Date: Tue, 2 Aug 2016 15:23:42 +0000
Message-ID: <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp>
In-Reply-To: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.227.79]
x-ms-office365-filtering-correlation-id: 46a12156-9907-4500-435e-08d3bae8fced
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0959; 6:aHcU8Gs+fuADtpZt4YYkBmxQJfhNNu698d+jtmBm5xkX61PORuVlCIJxDecxpp4TbekPVrnUOtpznvPRp30XMz12ldoofJtPtQnI3tyWErD2PV7TVuY/FOgmMzyZ+FYUUQW+TPGcjMnhH9d2LBEndQSa0eAvQRkDzAoxMrH/fW5IVfzu5GId5/5dlCEXxbl3POQQtzjUgudf2k+plUt1f2nCW/PBmJ5+0SwVbAimfV9zuYGGBf7dxBGz0H8aZjFETJKpbXKRnACanZh+wbL6Q+C+fCEs1R3Af93neKggxPxutrJQnfQuD4FukxpYePoee6IV2v5RAWxwODOjHEy7RA==; 5:dMIut35fSYaeJegpyhaAkhTlMF2SFecWWkbLy4X/dmoi8lVfYXyGmyBU9EzGFawPvmmi8g37yAiEcJJneMhHSp8bhC/4/jHxYHnjuEfq2T5A8F2KN91suLQROVncEByoBLCiyy/fl6JkUQ69z3Apgw==; 24:ZA/gY/NWGTL0DwdEmfDohqtJbtbcUqsDL1KG/d0OnJiWaFbg7JhBGyFyBn015FHoL68VDS4SwIzhADenvB86OmBWU0OsawMW+tIwBgVi/0M=; 7:3J/y/xwsEjmKbBNWssXkBRg2/HXtk7EiXwLV8ayXG8RX7vxawJf4RXKG7fjYL1jcZNgDdIoxkE1mcZdVcUvM29PjwOHZK7wUB48u5GYK4bCcHtwSzuFbPW1ElEQxM7hoSqA8/8RdqE8dSom2r533e0/+9xbyS5m0edomH7LtYhXjAkIKjYe5F6vka2tDaP1oIykaV8ko+SeSgpV+7rKWfm0r+HmqMpD0/BSFrprwX/hrRVK938Wp2xCmB104NKD0
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0959;
x-microsoft-antispam-prvs: <SN1PR09MB095980CD5E065ABA1CDCB69EF0050@SN1PR09MB0959.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(65766998875637)(166708455590820)(192374486261705); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026);  SRVR:SN1PR09MB0959; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0959; 
x-forefront-prvs: 0022134A87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(53754006)(189002)(377454003)(24454002)(13464003)(71364002)(122556002)(33656002)(97736004)(9686002)(102836003)(110136002)(86362001)(101416001)(561944003)(189998001)(54356999)(50986999)(76176999)(3660700001)(7696003)(305945005)(76576001)(3846002)(15975445007)(2950100001)(2900100001)(7846002)(74316002)(19580395003)(7736002)(11100500001)(77096005)(2906002)(8936002)(81166006)(8676002)(586003)(66066001)(3280700002)(5002640100001)(10400500002)(87936001)(106356001)(6116002)(99286002)(68736007)(92566002)(19580405001)(105586002)(81156014)(4326007); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0959; H:SN1PR09MB0960.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2016 15:23:42.5326 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0959
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/5X46svrHNT7fNWDXEFDPRbnwMDY>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 15:23:48 -0000

Take and all,

Your understanding is correct, there will be a core ROLIE draft and a numbe=
r of additional drafts for specific purposes (CSIRT, checklists, SWID, etc.=
). Option B would be to create an additional document that discusses author=
ization and authentication of ROLIE in more detail.

It looks like we're leaning towards option B at the moment, with at most a =
brief mention of authentication and authorization in the core, but no MTI o=
r in-depth discussion. Is there any other input?

There are a few more issues raised at IETF 96 around ROLIE that Dave or I w=
ill address to the list in the coming days, and as always, we'd appreciate =
any feedback on those specific issues, or on ROLIE in general.

Thanks,
Stephen

-----Original Message-----
From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]=20
Sent: Tuesday, August 02, 2016 1:31 AM
To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen A. (Fe=
d) <stephen.banghart@nist.gov>
Cc: mile@ietf.org
Subject: RE: [mile] ROLIE Authorization and Authentication

Hi Stephen and all,

In my understanding, we will have at least two drafts: one for general purp=
ose (current ROLIE core draft) and another for incident response purpose.
If Option B talks about separate drafts that are neither of the two drafts,=
 I agree with you and Adam's comment.

Apart from options A and B, it could be also fine to talk about authorizati=
on and authorization in the general purpose draft (ROLIE core
draft) without mandating any specific technique.

Kind regards,
Take



From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
Sent: Monday, August 1, 2016 12:52 AM
To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication

Hi Stephen,

If the primary purpose of ROLIE is to make public information available, th=
en leaving the authentication piece to separate drafts (your Option B) seem=
s to make sense. =A0My interest in ROLIE is centered on the ability to synd=
icate configuration checklists, which is a class of security automation inf=
ormation generally available to the public.=A0

I suspect that information sharing organizations may have a different persp=
ective.

I cannot authoritatively speak to which mechanism(s) would be best, but it =
seems to be the case that OAUTH is widely used for many REST APIs in the wi=
ld. =A0I have not seen XACML used in such a context. =A0I'm also not sure t=
hat we should get into authorization.

Kind regards,

Adam

On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed) <mailto:stephen.ba=
nghart@nist.gov> wrote:

Hello all,
=A0
Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there are =
some issues that we wanted to bring to the mailing list for discussion. Thi=
s e-mail references GitHub issue #34 (https://github.com/CISecurity/ROLIE/i=
ssues/34). The text from the issue is duplicated here for convenience:=A0
=A0
Authentication and authorization can be handled using a number of different=
 mechanisms, for this reason it's not clear if we can require a specific me=
chanism in the ROLIE core. More discussion is needed with the working group=
 to determine a way forward.=A0
=A0
Proposals:
=A0
- A: Select one or more authentication and authorization mechanisms as mand=
atory to implement (MTI).
- B: Address these issues in separate drafts.=A0
=A0
=A0
Support for OAUTH, http-auth, and XACML has been discussed in a limited cap=
acity previously. Given that deployed solutions may require different authe=
ntication and authorization solutions based on differing deployment require=
ments, we are concerned about requiring any single solution.
Furthermore, defining requirements for multiple solutions will add signific=
ant page count to the draft. As a result, we are leaning towards proposal B=
 which would allow for some modularity in solutions through additional draf=
ts.
=A0
Are there any concerns with going this route?
=A0
If option A is desired, we could use some help from someone knowledgeable i=
n using authentication and authorization solutions with HTTP RESTful servic=
es.
=A0
Thanks,
Stephen Banghart
=A0
_______________________________________________
mile mailing list
mailto:mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile




From nobody Wed Aug  3 07:34:21 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C9412DCD0; Wed,  3 Aug 2016 07:34:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160803143419.6148.28971.idtracker@ietfa.amsl.com>
Date: Wed, 03 Aug 2016 07:34:19 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/myz3S-Pp4fTshaublgeSstXDB3s>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 14:34:20 -0000

IESG state changed to Approved-announcement to be sent from IESG Evaluation::AD Followup
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/


From nobody Thu Aug  4 10:39:21 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CCC7512D67E; Wed,  3 Aug 2016 08:02:00 -0700 (PDT)
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: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160803150200.6140.9419.idtracker@ietfa.amsl.com>
Date: Wed, 03 Aug 2016 08:02:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/vOgE9PODGATWS4UiNY2W-hJg4uU>
X-Mailman-Approved-At: Thu, 04 Aug 2016 10:39:20 -0700
Cc: mile-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, mile-chairs@ietf.org, mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org, rfc-editor@rfc-editor.org
Subject: [mile] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 15:02:01 -0000

The IESG has approved the following document:
- 'The Incident Object Description Exchange Format v2'
  (draft-ietf-mile-rfc5070-bis-25.txt) as Proposed Standard

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

The IESG contact persons are Stephen Farrell and Kathleen Moriarty.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/





Technical Summary

   The Incident Object Description Exchange Format (IODEF) defines a
   data representation for security incident reports and cyber
   indicators commonly exchanged by operational security teams for
   mitigation and watch and warning.  This document describes an updated
   information model for the IODEF and provides an associated data model
   specified with XML Schema.  This new information and data model
   obsoletes [RFC5070]

Working Group Summary

   There was good consensus on the draft from the WG.  The updates were managed using the datatracker ticketing system and updates were confirmed on list.   

Document Quality

   There are several implementations which are documented in an implementation report to follow.  The XML expert for IODEF performed their review already and others checked the XML to UML, myself included.  The internationalization was checked as well.

Personnel

  Takeshi Takahashi is the Document Shepherd and Kathleen Moriarty is 
  the Responsible Area Director
'The IANA Expert(s) for the registries in this document are Takeshi Takahashi and Roman Danyliw.'

IANA Note

  Registry updates require expert review per RFC5226.


From nobody Fri Aug  5 07:20:55 2016
Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0264D12D875 for <mile@ietfa.amsl.com>; Fri,  5 Aug 2016 07:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XthXmPPtxq58 for <mile@ietfa.amsl.com>; Fri,  5 Aug 2016 07:20:48 -0700 (PDT)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0111.outbound.protection.outlook.com [23.103.200.111]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8C0F12D86A for <mile@ietf.org>; Fri,  5 Aug 2016 07:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=f8OZeA1AcsfhZT3S8lhnJM7kvlnMoG69nkAhw3Qg+Rc=; b=wUr0NVuL7Vj4hjMeEJPOKKErDXKg3l1XUP0idf1cdA2PJtu26uzu1bKYDikkDHvZvWMtbps4puaURvMJ3SKYvZ6Guk7pu1FU+CFmVhLdCk1A1yhh4+G03wZYekBZ73nst+u0lps8EKS0bQNhqyo3UpYawMDWXPg8K7zrbWY2Uwg=
Received: from SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) by SN1PR09MB0958.namprd09.prod.outlook.com (10.162.102.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Fri, 5 Aug 2016 14:20:45 +0000
Received: from SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) by SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) with mapi id 15.01.0549.023; Fri, 5 Aug 2016 14:20:45 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: [mile] ROLIE Authorization and Authentication
Thread-Index: AdHsfgS4wotwpaMPTJ+yy7j9Kj4evQAUFghwAJQPFSA=
Date: Fri, 5 Aug 2016 14:20:44 +0000
Message-ID: <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com>
In-Reply-To: <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.227.79]
x-ms-office365-filtering-correlation-id: eed1ec58-895a-4ba4-5969-08d3bd3bb093
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0958; 6:PKTmffQpQNM9wDiNLWVJfgpBZOOCDMhoBa9f7khCeX7m75n65ITqybOiQWpIRuS6Zp497TzZUaMWdhRKiu/zM03Qq5mVhaWZ6CNscFToAyhQtNyB0Q4X51vVexXN1qmBwd8S+tWr6gscR6SOP9N46dqX13WmqrvEZWXhLbu09As55kYCdmjEyryx1hFN2Hxr483XsAPAB5GB0jnBgRHrK85Bl9fnM3a20dD3hKr/v5yYn+LibgVUM3aqhYx+e7vsLX8mk5B7ojmxFHVJuEojB7U6EmSPoQypQzhKrk2wxqrnvp3YkO0ovUHLh6YsJZQ557WOADKo8xE5182Ln91Hrw==; 5:jjdG1rjiUebCFmu+Wy37oPvESUu9+0P+iEpMlIC6HnUV6LdoYPmWoMM6LOvcHio5hkhPGaH4LGdywXdiewpiixISuKryuNqslGwyjAhIy0oUNOO2GUZAqWQAaM2DfaDpQ+KPYA1jR9yNU6OnsC0d0Q==; 24:uUf2m0iGesBcLOsHwyg8jm73wmPzXcVzZco6geCleo7qVjH4iZ/QzNMfAmJlOlF44OoN4mEDckaXDqIzyaaeQee4iDjsFaUuYnhCV3ac8RQ=; 7:JvSMm8abfjAo6KVS4oXO263e5EfZqPcmZZzyJ3YBCBj4zdCpxH1TF4sGVPFNgRdEXuokLy5XGMBpuPezBW9WNRLvQORFKsfVXY9Itj8DOZ0VCTxF2lKqDJom/KQ7SXEJ320n7QSMxWGgeibweCPKiTF1rysEy+tduuNXjTroFLTZqGQ2bpHV2vJDy0hIEugXnWgmnTXbffoIpNSbmtVQ5iSZZ1XWTNrme6bqyKyQOdWTUsgtOMj4FXAsD0ReAlTF
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0958;
x-microsoft-antispam-prvs: <SN1PR09MB09586E111D0213CE5F7682C1F0180@SN1PR09MB0958.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(65766998875637)(166708455590820)(192374486261705)(100405760836317); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026);  SRVR:SN1PR09MB0958; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0958; 
x-forefront-prvs: 0025434D2D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(53754006)(13464003)(377454003)(199003)(71364002)(24454002)(189002)(97736004)(3280700002)(105586002)(561944003)(87936001)(11100500001)(81166006)(450100001)(81156014)(2950100001)(74316002)(102836003)(19580395003)(92566002)(1730700003)(19580405001)(2906002)(3846002)(6116002)(305945005)(99286002)(8936002)(122556002)(106356001)(7736002)(189998001)(2351001)(7696003)(586003)(76576001)(8676002)(77096005)(54356999)(7846002)(66066001)(68736007)(10400500002)(107886002)(76176999)(110136002)(3660700001)(5002640100001)(86362001)(33656002)(2900100001)(15975445007)(5640700001)(2501003)(101416001)(9686002)(50986999); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0958; H:SN1PR09MB0960.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2016 14:20:44.8264 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0958
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/wDSJg-fK87oB332KLFQMKE5fyRs>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 14:20:54 -0000

All,

Overall consensus has landed on option B: a brief discussion for the needs =
for authentication and authorization in the core ROLIE document, then speci=
fic solutions presented in separate drafts. If there is no objection I'll c=
lose the issue.

Thanks,
Stephen

-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, Stephen A.=
 (Fed)
Sent: Tuesday, August 02, 2016 11:24 AM
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication

Take and all,

Your understanding is correct, there will be a core ROLIE draft and a numbe=
r of additional drafts for specific purposes (CSIRT, checklists, SWID, etc.=
). Option B would be to create an additional document that discusses author=
ization and authentication of ROLIE in more detail.

It looks like we're leaning towards option B at the moment, with at most a =
brief mention of authentication and authorization in the core, but no MTI o=
r in-depth discussion. Is there any other input?

There are a few more issues raised at IETF 96 around ROLIE that Dave or I w=
ill address to the list in the coming days, and as always, we'd appreciate =
any feedback on those specific issues, or on ROLIE in general.

Thanks,
Stephen

-----Original Message-----
From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]=20
Sent: Tuesday, August 02, 2016 1:31 AM
To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen A. (Fe=
d) <stephen.banghart@nist.gov>
Cc: mile@ietf.org
Subject: RE: [mile] ROLIE Authorization and Authentication

Hi Stephen and all,

In my understanding, we will have at least two drafts: one for general purp=
ose (current ROLIE core draft) and another for incident response purpose.
If Option B talks about separate drafts that are neither of the two drafts,=
 I agree with you and Adam's comment.

Apart from options A and B, it could be also fine to talk about authorizati=
on and authorization in the general purpose draft (ROLIE core
draft) without mandating any specific technique.

Kind regards,
Take



From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
Sent: Monday, August 1, 2016 12:52 AM
To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication

Hi Stephen,

If the primary purpose of ROLIE is to make public information available, th=
en leaving the authentication piece to separate drafts (your Option B) seem=
s to make sense. =A0My interest in ROLIE is centered on the ability to synd=
icate configuration checklists, which is a class of security automation inf=
ormation generally available to the public.=A0

I suspect that information sharing organizations may have a different persp=
ective.

I cannot authoritatively speak to which mechanism(s) would be best, but it =
seems to be the case that OAUTH is widely used for many REST APIs in the wi=
ld. =A0I have not seen XACML used in such a context. =A0I'm also not sure t=
hat we should get into authorization.

Kind regards,

Adam

On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed) <mailto:stephen.ba=
nghart@nist.gov> wrote:

Hello all,
=A0
Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there are =
some issues that we wanted to bring to the mailing list for discussion. Thi=
s e-mail references GitHub issue #34 (https://github.com/CISecurity/ROLIE/i=
ssues/34). The text from the issue is duplicated here for convenience:=A0
=A0
Authentication and authorization can be handled using a number of different=
 mechanisms, for this reason it's not clear if we can require a specific me=
chanism in the ROLIE core. More discussion is needed with the working group=
 to determine a way forward.=A0
=A0
Proposals:
=A0
- A: Select one or more authentication and authorization mechanisms as mand=
atory to implement (MTI).
- B: Address these issues in separate drafts.=A0
=A0
=A0
Support for OAUTH, http-auth, and XACML has been discussed in a limited cap=
acity previously. Given that deployed solutions may require different authe=
ntication and authorization solutions based on differing deployment require=
ments, we are concerned about requiring any single solution.
Furthermore, defining requirements for multiple solutions will add signific=
ant page count to the draft. As a result, we are leaning towards proposal B=
 which would allow for some modularity in solutions through additional draf=
ts.
=A0
Are there any concerns with going this route?
=A0
If option A is desired, we could use some help from someone knowledgeable i=
n using authentication and authorization solutions with HTTP RESTful servic=
es.
=A0
Thanks,
Stephen Banghart
=A0
_______________________________________________
mile mailing list
mailto: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 Fri Aug  5 08:36:19 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2190C12D58A for <mile@ietfa.amsl.com>; Fri,  5 Aug 2016 08:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZD7XBJ8NNeB for <mile@ietfa.amsl.com>; Fri,  5 Aug 2016 08:36:15 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 97ACA12D550 for <mile@ietf.org>; Fri,  5 Aug 2016 08:36:15 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id p74so266417558qka.0 for <mile@ietf.org>; Fri, 05 Aug 2016 08:36:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bNHMRgCLr+i+LxSU/i/N5tIzxu2l2oha1uf5XYomdrI=; b=j++9B4V/lvyyY7IvRfb0YTlKPgQMwg8Z05waKyCq1p/zWfJQ3KPk0uCYezOOJds9Xz OHAycqSjSCQ72onWJdxqr2tNsXug1QiXr0zzYcL69wi2HcDIvcnYm1U9Xx8O4mmrqtB+ neQArwl9uLZBo/O6UqrsXuItC0MnK6d2InjOj7sR9OJ4SbJGI/mJc+zH7AuJ/2h88IV6 AjtJKkr9HaA9uy8ZQ4YxIotKcUEhpL8PA0i5vAL627BbmUJc9F3qnm1eW3tYsXwZ68ni +nR0HlZlcn+rDvmuxkxPRE5BGfoEAK4G2Ai2fMSRymDq+TdVA/8kvZVFaFZNA1NTnOVr dFHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bNHMRgCLr+i+LxSU/i/N5tIzxu2l2oha1uf5XYomdrI=; b=eggAyE8Ln17E3HRjWW2dBqOBC6i6I4uQNpOIsQRN39ysn1fjf1+kh2QbjQ8CPfYQZ9 uZP+H5UP0OEwObBZEW37dQ9xiyPF9PVLDAxJeXyts0cYfDMNQJNCz5Siyy4TLGBMoWyV J7ZSRpbr4ULyePHKmXc7/e2/B8dZAK/xnAsvuWm3UWUM7hP/Qr5T41PC6QduM1opKpD0 /QlC/9nPKbAZ3S0VpMfuNbkCocW4BzO7hRDX+wXX4y3WJR7wOT18DVFgZKBbcZRZLp6l 9QXRyeGHGe4BfXALDWMAIxHd4U043qKCBYtcnwla30nWPY99ZlOEsE+46fIJMk7FQRiv y/iA==
X-Gm-Message-State: AEkoout7PnegmWIVjXZjKqoB3AJDMmvHxuvpSMPC3ybqQy0x4n8VTbUgrRkvpC7CcgZOHw==
X-Received: by 10.55.191.193 with SMTP id p184mr13182869qkf.67.1470411374586;  Fri, 05 Aug 2016 08:36:14 -0700 (PDT)
Received: from [192.168.1.6] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id d38sm9871058qte.17.2016.08.05.08.36.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Aug 2016 08:36:13 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com>
Date: Fri, 5 Aug 2016 11:36:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com>
To: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/gUwrMxmV5CZuGqkeMqQE0BhY4eo>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 15:36:18 -0000

Hello,

Were there more responses off list in addition to Take & Adam's?  Is there e=
nough support to review multiple documents?  The chairs may have a better se=
nse of that.

Thank you,
Kathleen

Sent from my iPhone

> On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed) <stephen.banghart@=
nist.gov> wrote:
>=20
> All,
>=20
> Overall consensus has landed on option B: a brief discussion for the needs=
 for authentication and authorization in the core ROLIE document, then speci=
fic solutions presented in separate drafts. If there is no objection I'll cl=
ose the issue.
>=20
> Thanks,
> Stephen
>=20
> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, Stephen A=
. (Fed)
> Sent: Tuesday, August 02, 2016 11:24 AM
> To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
>=20
> Take and all,
>=20
> Your understanding is correct, there will be a core ROLIE draft and a numb=
er of additional drafts for specific purposes (CSIRT, checklists, SWID, etc.=
). Option B would be to create an additional document that discusses authori=
zation and authentication of ROLIE in more detail.
>=20
> It looks like we're leaning towards option B at the moment, with at most a=
 brief mention of authentication and authorization in the core, but no MTI o=
r in-depth discussion. Is there any other input?
>=20
> There are a few more issues raised at IETF 96 around ROLIE that Dave or I w=
ill address to the list in the coming days, and as always, we'd appreciate a=
ny feedback on those specific issues, or on ROLIE in general.
>=20
> Thanks,
> Stephen
>=20
> -----Original Message-----
> From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]=20
> Sent: Tuesday, August 02, 2016 1:31 AM
> To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen A. (Fe=
d) <stephen.banghart@nist.gov>
> Cc: mile@ietf.org
> Subject: RE: [mile] ROLIE Authorization and Authentication
>=20
> Hi Stephen and all,
>=20
> In my understanding, we will have at least two drafts: one for general pur=
pose (current ROLIE core draft) and another for incident response purpose.
> If Option B talks about separate drafts that are neither of the two drafts=
, I agree with you and Adam's comment.
>=20
> Apart from options A and B, it could be also fine to talk about authorizat=
ion and authorization in the general purpose draft (ROLIE core
> draft) without mandating any specific technique.
>=20
> Kind regards,
> Take
>=20
>=20
>=20
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
> Sent: Monday, August 1, 2016 12:52 AM
> To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
>=20
> Hi Stephen,
>=20
> If the primary purpose of ROLIE is to make public information available, t=
hen leaving the authentication piece to separate drafts (your Option B) seem=
s to make sense.  My interest in ROLIE is centered on the ability to syndica=
te configuration checklists, which is a class of security automation informa=
tion generally available to the public.=20
>=20
> I suspect that information sharing organizations may have a different pers=
pective.
>=20
> I cannot authoritatively speak to which mechanism(s) would be best, but it=
 seems to be the case that OAUTH is widely used for many REST APIs in the wi=
ld.  I have not seen XACML used in such a context.  I'm also not sure that w=
e should get into authorization.
>=20
> Kind regards,
>=20
> Adam
>=20
> On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed) <mailto:stephen.b=
anghart@nist.gov> wrote:
>=20
> Hello all,
> =20
> Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there are=
 some issues that we wanted to bring to the mailing list for discussion. Thi=
s e-mail references GitHub issue #34 (https://github.com/CISecurity/ROLIE/is=
sues/34). The text from the issue is duplicated here for convenience:=20
> =20
> Authentication and authorization can be handled using a number of differen=
t mechanisms, for this reason it's not clear if we can require a specific me=
chanism in the ROLIE core. More discussion is needed with the working group t=
o determine a way forward.=20
> =20
> Proposals:
> =20
> - A: Select one or more authentication and authorization mechanisms as man=
datory to implement (MTI).
> - B: Address these issues in separate drafts.=20
> =20
> =20
> Support for OAUTH, http-auth, and XACML has been discussed in a limited ca=
pacity previously. Given that deployed solutions may require different authe=
ntication and authorization solutions based on differing deployment requirem=
ents, we are concerned about requiring any single solution.
> Furthermore, defining requirements for multiple solutions will add signifi=
cant page count to the draft. As a result, we are leaning towards proposal B=
 which would allow for some modularity in solutions through additional draft=
s.
> =20
> Are there any concerns with going this route?
> =20
> If option A is desired, we could use some help from someone knowledgeable i=
n using authentication and authorization solutions with HTTP RESTful service=
s.
> =20
> Thanks,
> Stephen Banghart
> =20
> _______________________________________________
> mile mailing list
> mailto:mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Mon Aug  8 00:16:41 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A468912D63C for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 00:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdctjezAnGtL for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 00:16:37 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE0A127058 for <mile@ietf.org>; Mon,  8 Aug 2016 00:16:36 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id u787GWpd047553; Mon, 8 Aug 2016 16:16:32 +0900 (JST)
Received: from VAIO (ssh1.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp  with ESMTP id u787GWu2047550; Mon, 8 Aug 2016 16:16:32 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <kathleen.moriarty.ietf@gmail.com>, "'Banghart, Stephen A. \(Fed\)'" <stephen.banghart@nist.gov>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com> <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com>
In-Reply-To: <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com>
Date: Mon, 8 Aug 2016 16:16:35 +0900
Message-ID: <25d201d1f144$cc5aade0$651009a0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHfK/jNFlOkRObF2pIEFN2dwFloUAJaJ8z8Aa23yscDdu+hwp/oLG8w
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/OX5nPz1imkLyzSVGMP26n2LdY1k>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 07:16:39 -0000

Hi all,

Right, we had better solicit more comments.

All, please give us any comment or feedback on this issue.
Comments such as "I do not care either way", or "I cannot say anything at
this moment, because" are also welcomed.

We could wait for 2 weeks to get consensus.
Since Stephen has sent the question to the mailing list on 29th July, we
could wait for further comments by 12th August.

Also, if you are willing to review these drafts, please let us know. We
appreciate that very much.

Cheers,
Take


> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of
> kathleen.moriarty.ietf@gmail.com
> Sent: Saturday, August 6, 2016 12:36 AM
> To: Banghart, Stephen A. (Fed)
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
> 
> Hello,
> 
> Were there more responses off list in addition to Take & Adam's?  Is there
> enough support to review multiple documents?  The chairs may have a better
> sense of that.
> 
> Thank you,
> Kathleen
> 
> Sent from my iPhone
> 
> > On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)
> <stephen.banghart@nist.gov> wrote:
> >
> > All,
> >
> > Overall consensus has landed on option B: a brief discussion for the
needs
> for authentication and authorization in the core ROLIE document, then
> specific solutions presented in separate drafts. If there is no objection
> I'll close the issue.
> >
> > Thanks,
> > Stephen
> >
> > -----Original Message-----
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, Stephen
> A. (Fed)
> > Sent: Tuesday, August 02, 2016 11:24 AM
> > To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
> > Cc: mile@ietf.org
> > Subject: Re: [mile] ROLIE Authorization and Authentication
> >
> > Take and all,
> >
> > Your understanding is correct, there will be a core ROLIE draft and a
number
> of additional drafts for specific purposes (CSIRT, checklists, SWID,
etc.).
> Option B would be to create an additional document that discusses
> authorization and authentication of ROLIE in more detail.
> >
> > It looks like we're leaning towards option B at the moment, with at most
> a brief mention of authentication and authorization in the core, but no
MTI
> or in-depth discussion. Is there any other input?
> >
> > There are a few more issues raised at IETF 96 around ROLIE that Dave or
> I will address to the list in the coming days, and as always, we'd
appreciate
> any feedback on those specific issues, or on ROLIE in general.
> >
> > Thanks,
> > Stephen
> >
> > -----Original Message-----
> > From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
> > Sent: Tuesday, August 02, 2016 1:31 AM
> > To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen A.
> (Fed) <stephen.banghart@nist.gov>
> > Cc: mile@ietf.org
> > Subject: RE: [mile] ROLIE Authorization and Authentication
> >
> > Hi Stephen and all,
> >
> > In my understanding, we will have at least two drafts: one for general
> purpose (current ROLIE core draft) and another for incident response
> purpose.
> > If Option B talks about separate drafts that are neither of the two
drafts,
> I agree with you and Adam's comment.
> >
> > Apart from options A and B, it could be also fine to talk about
authorization
> and authorization in the general purpose draft (ROLIE core
> > draft) without mandating any specific technique.
> >
> > Kind regards,
> > Take
> >
> >
> >
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
> > Sent: Monday, August 1, 2016 12:52 AM
> > To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
> > Cc: mile@ietf.org
> > Subject: Re: [mile] ROLIE Authorization and Authentication
> >
> > Hi Stephen,
> >
> > If the primary purpose of ROLIE is to make public information available,
> then leaving the authentication piece to separate drafts (your Option B)
> seems to make sense.  My interest in ROLIE is centered on the ability to
> syndicate configuration checklists, which is a class of security
automation
> information generally available to the public.
> >
> > I suspect that information sharing organizations may have a different
> perspective.
> >
> > I cannot authoritatively speak to which mechanism(s) would be best, but
> it seems to be the case that OAUTH is widely used for many REST APIs in
the
> wild.  I have not seen XACML used in such a context.  I'm also not sure
that
> we should get into authorization.
> >
> > Kind regards,
> >
> > Adam
> >
> > On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
> <mailto:stephen.banghart@nist.gov> wrote:
> >
> > Hello all,
> >
> > Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there
> are some issues that we wanted to bring to the mailing list for
discussion.
> This e-mail references GitHub issue #34
> (https://github.com/CISecurity/ROLIE/issues/34). The text from the issue
> is duplicated here for convenience:
> >
> > Authentication and authorization can be handled using a number of
different
> mechanisms, for this reason it's not clear if we can require a specific
> mechanism in the ROLIE core. More discussion is needed with the working
group
> to determine a way forward.
> >
> > Proposals:
> >
> > - A: Select one or more authentication and authorization mechanisms as
> mandatory to implement (MTI).
> > - B: Address these issues in separate drafts.
> >
> >
> > Support for OAUTH, http-auth, and XACML has been discussed in a limited
> capacity previously. Given that deployed solutions may require different
> authentication and authorization solutions based on differing deployment
> requirements, we are concerned about requiring any single solution.
> > Furthermore, defining requirements for multiple solutions will add
> significant page count to the draft. As a result, we are leaning towards
> proposal B which would allow for some modularity in solutions through
> additional drafts.
> >
> > Are there any concerns with going this route?
> >
> > If option A is desired, we could use some help from someone
knowledgeable
> in using authentication and authorization solutions with HTTP RESTful
> services.
> >
> > Thanks,
> > Stephen Banghart
> >
> > _______________________________________________
> > mile mailing list
> > mailto:mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> >
> >
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Mon Aug  8 04:52:59 2016
Return-Path: <mio@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3E312D68B for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 04:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXiVsc1U9WY9 for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 04:52:56 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id C346812B051 for <mile@ietf.org>; Mon,  8 Aug 2016 04:52:55 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id u78BqrPS026754; Mon, 8 Aug 2016 20:52:53 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw2.nict.go.jp  with ESMTP id u78BqqRu026751; Mon, 8 Aug 2016 20:52:52 +0900 (JST)
Received: from [127.0.0.1] (ssh1.nict.go.jp [133.243.3.49]) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTP id 7C0F3776C; Mon,  8 Aug 2016 20:52:52 +0900 (JST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=utf-8
From: Mio SUZUKI <mio@nict.go.jp>
In-Reply-To: <25d201d1f144$cc5aade0$651009a0$@nict.go.jp>
Date: Mon, 8 Aug 2016 20:52:52 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <54B0BC86-6898-4BBD-B13B-D0E436AA30F7@nict.go.jp>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com> <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com> <25d201d1f144$cc5aade0$651009a0$@nict.go.jp>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
X-Mailer: Apple Mail (2.3124)
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/ZcRVISpauIBjwVCMn9J0J396in4>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 11:52:58 -0000

Hello,

I agree the option B, with one condition.
The condition is that we will surely have the authentication draft.
Protocol without security mechanism is scary to me.
=20
Mio

> 2016/08/08 16:16=E3=80=81Takeshi Takahashi =
<takeshi_takahashi@nict.go.jp> :
>=20
> Hi all,
>=20
> Right, we had better solicit more comments.
>=20
> All, please give us any comment or feedback on this issue.
> Comments such as "I do not care either way", or "I cannot say anything =
at
> this moment, because" are also welcomed.
>=20
> We could wait for 2 weeks to get consensus.
> Since Stephen has sent the question to the mailing list on 29th July, =
we
> could wait for further comments by 12th August.
>=20
> Also, if you are willing to review these drafts, please let us know. =
We
> appreciate that very much.
>=20
> Cheers,
> Take
>=20
>=20
>> -----Original Message-----
>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of
>> kathleen.moriarty.ietf@gmail.com
>> Sent: Saturday, August 6, 2016 12:36 AM
>> To: Banghart, Stephen A. (Fed)
>> Cc: mile@ietf.org
>> Subject: Re: [mile] ROLIE Authorization and Authentication
>>=20
>> Hello,
>>=20
>> Were there more responses off list in addition to Take & Adam's?  Is =
there
>> enough support to review multiple documents?  The chairs may have a =
better
>> sense of that.
>>=20
>> Thank you,
>> Kathleen
>>=20
>> Sent from my iPhone
>>=20
>>> On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)
>> <stephen.banghart@nist.gov> wrote:
>>>=20
>>> All,
>>>=20
>>> Overall consensus has landed on option B: a brief discussion for the
> needs
>> for authentication and authorization in the core ROLIE document, then
>> specific solutions presented in separate drafts. If there is no =
objection
>> I'll close the issue.
>>>=20
>>> Thanks,
>>> Stephen
>>>=20
>>> -----Original Message-----
>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, =
Stephen
>> A. (Fed)
>>> Sent: Tuesday, August 02, 2016 11:24 AM
>>> To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
>>> Cc: mile@ietf.org
>>> Subject: Re: [mile] ROLIE Authorization and Authentication
>>>=20
>>> Take and all,
>>>=20
>>> Your understanding is correct, there will be a core ROLIE draft and =
a
> number
>> of additional drafts for specific purposes (CSIRT, checklists, SWID,
> etc.).
>> Option B would be to create an additional document that discusses
>> authorization and authentication of ROLIE in more detail.
>>>=20
>>> It looks like we're leaning towards option B at the moment, with at =
most
>> a brief mention of authentication and authorization in the core, but =
no
> MTI
>> or in-depth discussion. Is there any other input?
>>>=20
>>> There are a few more issues raised at IETF 96 around ROLIE that Dave =
or
>> I will address to the list in the coming days, and as always, we'd
> appreciate
>> any feedback on those specific issues, or on ROLIE in general.
>>>=20
>>> Thanks,
>>> Stephen
>>>=20
>>> -----Original Message-----
>>> From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
>>> Sent: Tuesday, August 02, 2016 1:31 AM
>>> To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen =
A.
>> (Fed) <stephen.banghart@nist.gov>
>>> Cc: mile@ietf.org
>>> Subject: RE: [mile] ROLIE Authorization and Authentication
>>>=20
>>> Hi Stephen and all,
>>>=20
>>> In my understanding, we will have at least two drafts: one for =
general
>> purpose (current ROLIE core draft) and another for incident response
>> purpose.
>>> If Option B talks about separate drafts that are neither of the two
> drafts,
>> I agree with you and Adam's comment.
>>>=20
>>> Apart from options A and B, it could be also fine to talk about
> authorization
>> and authorization in the general purpose draft (ROLIE core
>>> draft) without mandating any specific technique.
>>>=20
>>> Kind regards,
>>> Take
>>>=20
>>>=20
>>>=20
>>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam =
Montville
>>> Sent: Monday, August 1, 2016 12:52 AM
>>> To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
>>> Cc: mile@ietf.org
>>> Subject: Re: [mile] ROLIE Authorization and Authentication
>>>=20
>>> Hi Stephen,
>>>=20
>>> If the primary purpose of ROLIE is to make public information =
available,
>> then leaving the authentication piece to separate drafts (your Option =
B)
>> seems to make sense.  My interest in ROLIE is centered on the ability =
to
>> syndicate configuration checklists, which is a class of security
> automation
>> information generally available to the public.
>>>=20
>>> I suspect that information sharing organizations may have a =
different
>> perspective.
>>>=20
>>> I cannot authoritatively speak to which mechanism(s) would be best, =
but
>> it seems to be the case that OAUTH is widely used for many REST APIs =
in
> the
>> wild.  I have not seen XACML used in such a context.  I'm also not =
sure
> that
>> we should get into authorization.
>>>=20
>>> Kind regards,
>>>=20
>>> Adam
>>>=20
>>> On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
>> <mailto:stephen.banghart@nist.gov> wrote:
>>>=20
>>> Hello all,
>>>=20
>>> Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, =
there
>> are some issues that we wanted to bring to the mailing list for
> discussion.
>> This e-mail references GitHub issue #34
>> (https://github.com/CISecurity/ROLIE/issues/34). The text from the =
issue
>> is duplicated here for convenience:
>>>=20
>>> Authentication and authorization can be handled using a number of
> different
>> mechanisms, for this reason it's not clear if we can require a =
specific
>> mechanism in the ROLIE core. More discussion is needed with the =
working
> group
>> to determine a way forward.
>>>=20
>>> Proposals:
>>>=20
>>> - A: Select one or more authentication and authorization mechanisms =
as
>> mandatory to implement (MTI).
>>> - B: Address these issues in separate drafts.
>>>=20
>>>=20
>>> Support for OAUTH, http-auth, and XACML has been discussed in a =
limited
>> capacity previously. Given that deployed solutions may require =
different
>> authentication and authorization solutions based on differing =
deployment
>> requirements, we are concerned about requiring any single solution.
>>> Furthermore, defining requirements for multiple solutions will add
>> significant page count to the draft. As a result, we are leaning =
towards
>> proposal B which would allow for some modularity in solutions through
>> additional drafts.
>>>=20
>>> Are there any concerns with going this route?
>>>=20
>>> If option A is desired, we could use some help from someone
> knowledgeable
>> in using authentication and authorization solutions with HTTP RESTful
>> services.
>>>=20
>>> Thanks,
>>> Stephen Banghart
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mailto:mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>=20
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From nobody Mon Aug  8 07:48:04 2016
Return-Path: <jfield@pivotal.io>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 147C412D618 for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 07:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pivotal-io.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQPViep2l__Z for <mile@ietfa.amsl.com>; Mon,  8 Aug 2016 07:47:59 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 2621512B03C for <mile@ietf.org>; Mon,  8 Aug 2016 07:47:59 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id q128so123841003wma.1 for <mile@ietf.org>; Mon, 08 Aug 2016 07:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=povzVbdKwV27IhMeDg3M8ncvIHLFIn0Ft6tDdCgFvzg=; b=h28Zu9FEaw9s2ApEmkVN11/7DxnE1djN/u1XjF6TPldp6zFPEnXtIgc493jptA2cSg WPOWwK2EFMMnj7x5+Tjj7Iz1P8Hm9FRt8zujFik2VCR4T/z38/My0E+vFwrYYK9mmITB Suq0rhRnUNW1TIu3trohrYfxF4piW5Vw4Zg21rEPuPZROBvsg0X5KaRbKBDPCLRF8G/c DnIYXw8j/FyAl7OhmJzzH76A5qQL1b4jaEQVhCNlrFRWL78MNvqwM8A+Tz02M5amBIH0 zBkyLF9ih8bSSO4kMNyyCblGWPzUN8FkuK4pInHYOa6QP5HhV0i/xDRD267Kt/93fDIA 39wg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=povzVbdKwV27IhMeDg3M8ncvIHLFIn0Ft6tDdCgFvzg=; b=mCljfBRxhKkCo8qVgRJDVwyrCE5O+4hIvLMIDYF3gtJYBi7o/iKq9p7IWsNXN9I/cM dE/+0kHKgZF2ku0FFid4kqIfB1518wJeEe4COY360zP+1OGQx0cU3IPK3A6VCiFda+FE OC7WHlqIBZDB1k+C+qiZTVR+sXlgwmYBvdQfLdK1A3GwJbgbclGzTGXAFn/XH6XROBr8 tH4zejyTtWlYspnGEJ8kr+ZGOupf8pAUIm274W/IiKtCgYUv5GkGVhUG27/VkWFQw7Ub buBPWtICE/8AikFvc1f7sJtFXXkNeKZ9Z7UGAy2seGduNKMWt3W46ubUefcPhk7aVJcE W7Uw==
X-Gm-Message-State: AEkooutAgJ14KFVWA+ZqtfdXKfVSuB7AJvlot8JLTKBfM5egUPokqW6Im4TbZUz9fEFCQpi4GU18cYe0RaEG70/k
X-Received: by 10.194.47.206 with SMTP id f14mr91372046wjn.98.1470667677515; Mon, 08 Aug 2016 07:47:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.33.161 with HTTP; Mon, 8 Aug 2016 07:47:56 -0700 (PDT)
In-Reply-To: <54B0BC86-6898-4BBD-B13B-D0E436AA30F7@nict.go.jp>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com> <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com> <25d201d1f144$cc5aade0$651009a0$@nict.go.jp> <54B0BC86-6898-4BBD-B13B-D0E436AA30F7@nict.go.jp>
From: John Field <jfield@pivotal.io>
Date: Mon, 8 Aug 2016 10:47:56 -0400
Message-ID: <CAC0wChHGVH_bD5Wsw-mJ9zxuURt2fTAM1eyH=YiTpwbVY5UiRw@mail.gmail.com>
To: Mio SUZUKI <mio@nict.go.jp>
Content-Type: multipart/alternative; boundary=047d7b86e4f8805d1205399080a9
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/U-X8CuNbCszqMPvLa4eRfvnnhIE>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 14:48:02 -0000

--047d7b86e4f8805d1205399080a9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I also support the notion of a separate draft for authentication and
authorization issues.  It makes sense to factor this out as it will be a
deployment-dependent decision.  We should probably state that doing some
sort of AuthN is a "SHOULD," but then delegate details to another
draft(s).  That is, using RFC 2119 compliant language of "SHOULD
authenticate" but leave it to the implementer to choose how, could be
appropriate here, since in certain circumstances, one could validly choose
not to do any authentication, as long as the implications of that choice
are fully understood.  I've added a comment on the git issue.

FWIW, I've had some experience with specifying/profiling AuthN mechanisms,
and so might be able to help there, once we get to that point.

Regards,
John




On Mon, Aug 8, 2016 at 7:52 AM, Mio SUZUKI <mio@nict.go.jp> wrote:

> Hello,
>
> I agree the option B, with one condition.
> The condition is that we will surely have the authentication draft.
> Protocol without security mechanism is scary to me.
>
> Mio
>
> > 2016/08/08 16:16=E3=80=81Takeshi Takahashi <takeshi_takahashi@nict.go.j=
p> :
> >
> > Hi all,
> >
> > Right, we had better solicit more comments.
> >
> > All, please give us any comment or feedback on this issue.
> > Comments such as "I do not care either way", or "I cannot say anything =
at
> > this moment, because" are also welcomed.
> >
> > We could wait for 2 weeks to get consensus.
> > Since Stephen has sent the question to the mailing list on 29th July, w=
e
> > could wait for further comments by 12th August.
> >
> > Also, if you are willing to review these drafts, please let us know. We
> > appreciate that very much.
> >
> > Cheers,
> > Take
> >
> >
> >> -----Original Message-----
> >> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of
> >> kathleen.moriarty.ietf@gmail.com
> >> Sent: Saturday, August 6, 2016 12:36 AM
> >> To: Banghart, Stephen A. (Fed)
> >> Cc: mile@ietf.org
> >> Subject: Re: [mile] ROLIE Authorization and Authentication
> >>
> >> Hello,
> >>
> >> Were there more responses off list in addition to Take & Adam's?  Is
> there
> >> enough support to review multiple documents?  The chairs may have a
> better
> >> sense of that.
> >>
> >> Thank you,
> >> Kathleen
> >>
> >> Sent from my iPhone
> >>
> >>> On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)
> >> <stephen.banghart@nist.gov> wrote:
> >>>
> >>> All,
> >>>
> >>> Overall consensus has landed on option B: a brief discussion for the
> > needs
> >> for authentication and authorization in the core ROLIE document, then
> >> specific solutions presented in separate drafts. If there is no
> objection
> >> I'll close the issue.
> >>>
> >>> Thanks,
> >>> Stephen
> >>>
> >>> -----Original Message-----
> >>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart,
> Stephen
> >> A. (Fed)
> >>> Sent: Tuesday, August 02, 2016 11:24 AM
> >>> To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
> >>> Cc: mile@ietf.org
> >>> Subject: Re: [mile] ROLIE Authorization and Authentication
> >>>
> >>> Take and all,
> >>>
> >>> Your understanding is correct, there will be a core ROLIE draft and a
> > number
> >> of additional drafts for specific purposes (CSIRT, checklists, SWID,
> > etc.).
> >> Option B would be to create an additional document that discusses
> >> authorization and authentication of ROLIE in more detail.
> >>>
> >>> It looks like we're leaning towards option B at the moment, with at
> most
> >> a brief mention of authentication and authorization in the core, but n=
o
> > MTI
> >> or in-depth discussion. Is there any other input?
> >>>
> >>> There are a few more issues raised at IETF 96 around ROLIE that Dave =
or
> >> I will address to the list in the coming days, and as always, we'd
> > appreciate
> >> any feedback on those specific issues, or on ROLIE in general.
> >>>
> >>> Thanks,
> >>> Stephen
> >>>
> >>> -----Original Message-----
> >>> From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
> >>> Sent: Tuesday, August 02, 2016 1:31 AM
> >>> To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen
> A.
> >> (Fed) <stephen.banghart@nist.gov>
> >>> Cc: mile@ietf.org
> >>> Subject: RE: [mile] ROLIE Authorization and Authentication
> >>>
> >>> Hi Stephen and all,
> >>>
> >>> In my understanding, we will have at least two drafts: one for genera=
l
> >> purpose (current ROLIE core draft) and another for incident response
> >> purpose.
> >>> If Option B talks about separate drafts that are neither of the two
> > drafts,
> >> I agree with you and Adam's comment.
> >>>
> >>> Apart from options A and B, it could be also fine to talk about
> > authorization
> >> and authorization in the general purpose draft (ROLIE core
> >>> draft) without mandating any specific technique.
> >>>
> >>> Kind regards,
> >>> Take
> >>>
> >>>
> >>>
> >>> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam Montville
> >>> Sent: Monday, August 1, 2016 12:52 AM
> >>> To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
> >>> Cc: mile@ietf.org
> >>> Subject: Re: [mile] ROLIE Authorization and Authentication
> >>>
> >>> Hi Stephen,
> >>>
> >>> If the primary purpose of ROLIE is to make public information
> available,
> >> then leaving the authentication piece to separate drafts (your Option =
B)
> >> seems to make sense.  My interest in ROLIE is centered on the ability =
to
> >> syndicate configuration checklists, which is a class of security
> > automation
> >> information generally available to the public.
> >>>
> >>> I suspect that information sharing organizations may have a different
> >> perspective.
> >>>
> >>> I cannot authoritatively speak to which mechanism(s) would be best, b=
ut
> >> it seems to be the case that OAUTH is widely used for many REST APIs i=
n
> > the
> >> wild.  I have not seen XACML used in such a context.  I'm also not sur=
e
> > that
> >> we should get into authorization.
> >>>
> >>> Kind regards,
> >>>
> >>> Adam
> >>>
> >>> On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
> >> <mailto:stephen.banghart@nist.gov> wrote:
> >>>
> >>> Hello all,
> >>>
> >>> Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, ther=
e
> >> are some issues that we wanted to bring to the mailing list for
> > discussion.
> >> This e-mail references GitHub issue #34
> >> (https://github.com/CISecurity/ROLIE/issues/34). The text from the
> issue
> >> is duplicated here for convenience:
> >>>
> >>> Authentication and authorization can be handled using a number of
> > different
> >> mechanisms, for this reason it's not clear if we can require a specifi=
c
> >> mechanism in the ROLIE core. More discussion is needed with the workin=
g
> > group
> >> to determine a way forward.
> >>>
> >>> Proposals:
> >>>
> >>> - A: Select one or more authentication and authorization mechanisms a=
s
> >> mandatory to implement (MTI).
> >>> - B: Address these issues in separate drafts.
> >>>
> >>>
> >>> Support for OAUTH, http-auth, and XACML has been discussed in a limit=
ed
> >> capacity previously. Given that deployed solutions may require differe=
nt
> >> authentication and authorization solutions based on differing deployme=
nt
> >> requirements, we are concerned about requiring any single solution.
> >>> Furthermore, defining requirements for multiple solutions will add
> >> significant page count to the draft. As a result, we are leaning towar=
ds
> >> proposal B which would allow for some modularity in solutions through
> >> additional drafts.
> >>>
> >>> Are there any concerns with going this route?
> >>>
> >>> If option A is desired, we could use some help from someone
> > knowledgeable
> >> in using authentication and authorization solutions with HTTP RESTful
> >> services.
> >>>
> >>> Thanks,
> >>> Stephen Banghart
> >>>
> >>> _______________________________________________
> >>> mile mailing list
> >>> mailto:mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> mile mailing list
> >>> mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >>>
> >>> _______________________________________________
> >>> mile mailing list
> >>> mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >>
> >> _______________________________________________
> >> mile mailing list
> >> mile@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>



--=20

John P. Field | Security PM | Pivotal

Direct: (908) 962-3394 | jfield@ <jfield@gopivotal.com>pivotal.io

--047d7b86e4f8805d1205399080a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I also support the notion of a separate draft for authenti=
cation and authorization issues.=C2=A0 It makes sense to factor this out as=
 it will be a deployment-dependent decision.=C2=A0 We should probably state=
 that doing some sort of AuthN is a &quot;SHOULD,&quot; but then delegate d=
etails to another draft(s).=C2=A0 That is, using RFC 2119 compliant languag=
e of &quot;SHOULD authenticate&quot; but leave it to the implementer to cho=
ose how, could be appropriate here, since in certain circumstances, one cou=
ld validly choose not to do any authentication, as long as the implications=
 of that choice are fully understood.=C2=A0=C2=A0I&#39;ve added a comment o=
n the git issue.<div><br></div><div>FWIW, I&#39;ve had some experience with=
 specifying/profiling AuthN mechanisms, and so might be able to help there,=
 once we get to that point.=C2=A0</div><div><br></div><div>Regards,</div><d=
iv>John</div><div><br></div><div><br></div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Aug 8, 2016 at 7:52=
 AM, Mio SUZUKI <span dir=3D"ltr">&lt;<a href=3D"mailto:mio@nict.go.jp" tar=
get=3D"_blank">mio@nict.go.jp</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">Hello,<br>
<br>
I agree the option B, with one condition.<br>
The condition is that we will surely have the authentication draft.<br>
Protocol without security mechanism is scary to me.<br>
<br>
Mio<br>
<br>
&gt; 2016/08/08 16:16=E3=80=81Takeshi Takahashi &lt;<a href=3D"mailto:takes=
hi_takahashi@nict.go.jp">takeshi_takahashi@nict.go.jp</a>&gt; :<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; Right, we had better solicit more comments.<br>
&gt;<br>
&gt; All, please give us any comment or feedback on this issue.<br>
&gt; Comments such as &quot;I do not care either way&quot;, or &quot;I cann=
ot say anything at<br>
&gt; this moment, because&quot; are also welcomed.<br>
&gt;<br>
&gt; We could wait for 2 weeks to get consensus.<br>
&gt; Since Stephen has sent the question to the mailing list on 29th July, =
we<br>
&gt; could wait for further comments by 12th August.<br>
&gt;<br>
&gt; Also, if you are willing to review these drafts, please let us know. W=
e<br>
&gt; appreciate that very much.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Take<br>
&gt;<br>
&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: mile [mailto:<a href=3D"mailto:mile-bounces@ietf.org">mile-b=
ounces@ietf.org</a>] On Behalf Of<br>
&gt;&gt; <a href=3D"mailto:kathleen.moriarty.ietf@gmail.com">kathleen.moria=
rty.ietf@gmail.<wbr>com</a><br>
&gt;&gt; Sent: Saturday, August 6, 2016 12:36 AM<br>
&gt;&gt; To: Banghart, Stephen A. (Fed)<br>
&gt;&gt; Cc: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt; Subject: Re: [mile] ROLIE Authorization and Authentication<br>
&gt;&gt;<br>
&gt;&gt; Hello,<br>
&gt;&gt;<br>
&gt;&gt; Were there more responses off list in addition to Take &amp; Adam&=
#39;s?=C2=A0 Is there<br>
&gt;&gt; enough support to review multiple documents?=C2=A0 The chairs may =
have a better<br>
&gt;&gt; sense of that.<br>
&gt;&gt;<br>
&gt;&gt; Thank you,<br>
&gt;&gt; Kathleen<br>
&gt;&gt;<br>
&gt;&gt; Sent from my iPhone<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)<br>
&gt;&gt; &lt;<a href=3D"mailto:stephen.banghart@nist.gov">stephen.banghart@=
nist.gov</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; All,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Overall consensus has landed on option B: a brief discussion f=
or the<br>
&gt; needs<br>
&gt;&gt; for authentication and authorization in the core ROLIE document, t=
hen<br>
&gt;&gt; specific solutions presented in separate drafts. If there is no ob=
jection<br>
&gt;&gt; I&#39;ll close the issue.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt; Stephen<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt; From: mile [mailto:<a href=3D"mailto:mile-bounces@ietf.org">mi=
le-bounces@ietf.org</a>] On Behalf Of Banghart, Stephen<br>
&gt;&gt; A. (Fed)<br>
&gt;&gt;&gt; Sent: Tuesday, August 02, 2016 11:24 AM<br>
&gt;&gt;&gt; To: Takeshi Takahashi &lt;<a href=3D"mailto:takeshi_takahashi@=
nict.go.jp">takeshi_takahashi@nict.go.jp</a>&gt;<br>
&gt;&gt;&gt; Cc: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; Subject: Re: [mile] ROLIE Authorization and Authentication<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Take and all,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Your understanding is correct, there will be a core ROLIE draf=
t and a<br>
&gt; number<br>
&gt;&gt; of additional drafts for specific purposes (CSIRT, checklists, SWI=
D,<br>
&gt; etc.).<br>
&gt;&gt; Option B would be to create an additional document that discusses<=
br>
&gt;&gt; authorization and authentication of ROLIE in more detail.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; It looks like we&#39;re leaning towards option B at the moment=
, with at most<br>
&gt;&gt; a brief mention of authentication and authorization in the core, b=
ut no<br>
&gt; MTI<br>
&gt;&gt; or in-depth discussion. Is there any other input?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There are a few more issues raised at IETF 96 around ROLIE tha=
t Dave or<br>
&gt;&gt; I will address to the list in the coming days, and as always, we&#=
39;d<br>
&gt; appreciate<br>
&gt;&gt; any feedback on those specific issues, or on ROLIE in general.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt; Stephen<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt; From: Takeshi Takahashi [mailto:<a href=3D"mailto:takeshi_taka=
hashi@nict.go.jp">takeshi_takahashi@<wbr>nict.go.jp</a>]<br>
&gt;&gt;&gt; Sent: Tuesday, August 02, 2016 1:31 AM<br>
&gt;&gt;&gt; To: &#39;Adam Montville&#39; &lt;<a href=3D"mailto:adam.w.mont=
ville@gmail.com">adam.w.montville@gmail.com</a>&gt;; Banghart, Stephen A.<b=
r>
&gt;&gt; (Fed) &lt;<a href=3D"mailto:stephen.banghart@nist.gov">stephen.ban=
ghart@nist.gov</a>&gt;<br>
&gt;&gt;&gt; Cc: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; Subject: RE: [mile] ROLIE Authorization and Authentication<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi Stephen and all,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; In my understanding, we will have at least two drafts: one for=
 general<br>
&gt;&gt; purpose (current ROLIE core draft) and another for incident respon=
se<br>
&gt;&gt; purpose.<br>
&gt;&gt;&gt; If Option B talks about separate drafts that are neither of th=
e two<br>
&gt; drafts,<br>
&gt;&gt; I agree with you and Adam&#39;s comment.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Apart from options A and B, it could be also fine to talk abou=
t<br>
&gt; authorization<br>
&gt;&gt; and authorization in the general purpose draft (ROLIE core<br>
&gt;&gt;&gt; draft) without mandating any specific technique.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Kind regards,<br>
&gt;&gt;&gt; Take<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; From: mile [mailto:<a href=3D"mailto:mile-bounces@ietf.org">mi=
le-bounces@ietf.org</a>] On Behalf Of Adam Montville<br>
&gt;&gt;&gt; Sent: Monday, August 1, 2016 12:52 AM<br>
&gt;&gt;&gt; To: Banghart, Stephen A. (Fed) &lt;<a href=3D"mailto:stephen.b=
anghart@nist.gov">stephen.banghart@nist.gov</a>&gt;<br>
&gt;&gt;&gt; Cc: <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; Subject: Re: [mile] ROLIE Authorization and Authentication<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi Stephen,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If the primary purpose of ROLIE is to make public information =
available,<br>
&gt;&gt; then leaving the authentication piece to separate drafts (your Opt=
ion B)<br>
&gt;&gt; seems to make sense.=C2=A0 My interest in ROLIE is centered on the=
 ability to<br>
&gt;&gt; syndicate configuration checklists, which is a class of security<b=
r>
&gt; automation<br>
&gt;&gt; information generally available to the public.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I suspect that information sharing organizations may have a di=
fferent<br>
&gt;&gt; perspective.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I cannot authoritatively speak to which mechanism(s) would be =
best, but<br>
&gt;&gt; it seems to be the case that OAUTH is widely used for many REST AP=
Is in<br>
&gt; the<br>
&gt;&gt; wild.=C2=A0 I have not seen XACML used in such a context.=C2=A0 I&=
#39;m also not sure<br>
&gt; that<br>
&gt;&gt; we should get into authorization.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Kind regards,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Adam<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)<br>
&gt;&gt; &lt;mailto:<a href=3D"mailto:stephen.banghart@nist.gov">stephen.ba=
nghart@nist.<wbr>gov</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hello all,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Following the discussion at IETF 96 on draft-ietf-mile-rolie-0=
3, there<br>
&gt;&gt; are some issues that we wanted to bring to the mailing list for<br=
>
&gt; discussion.<br>
&gt;&gt; This e-mail references GitHub issue #34<br>
&gt;&gt; (<a href=3D"https://github.com/CISecurity/ROLIE/issues/34" rel=3D"=
noreferrer" target=3D"_blank">https://github.com/<wbr>CISecurity/ROLIE/issu=
es/34</a>). The text from the issue<br>
&gt;&gt; is duplicated here for convenience:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Authentication and authorization can be handled using a number=
 of<br>
&gt; different<br>
&gt;&gt; mechanisms, for this reason it&#39;s not clear if we can require a=
 specific<br>
&gt;&gt; mechanism in the ROLIE core. More discussion is needed with the wo=
rking<br>
&gt; group<br>
&gt;&gt; to determine a way forward.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Proposals:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; - A: Select one or more authentication and authorization mecha=
nisms as<br>
&gt;&gt; mandatory to implement (MTI).<br>
&gt;&gt;&gt; - B: Address these issues in separate drafts.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Support for OAUTH, http-auth, and XACML has been discussed in =
a limited<br>
&gt;&gt; capacity previously. Given that deployed solutions may require dif=
ferent<br>
&gt;&gt; authentication and authorization solutions based on differing depl=
oyment<br>
&gt;&gt; requirements, we are concerned about requiring any single solution=
.<br>
&gt;&gt;&gt; Furthermore, defining requirements for multiple solutions will=
 add<br>
&gt;&gt; significant page count to the draft. As a result, we are leaning t=
owards<br>
&gt;&gt; proposal B which would allow for some modularity in solutions thro=
ugh<br>
&gt;&gt; additional drafts.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Are there any concerns with going this route?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If option A is desired, we could use some help from someone<br=
>
&gt; knowledgeable<br>
&gt;&gt; in using authentication and authorization solutions with HTTP REST=
ful<br>
&gt;&gt; services.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt; Stephen Banghart<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mile mailing list<br>
&gt;&gt;&gt; mailto:<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mi=
le</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mile mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mi=
le</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt;&gt; mile mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"=
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mi=
le</a><br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; mile mailing list<br>
&gt;&gt; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</=
a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; mile mailing list<br>
&gt; <a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><b=
r>
<br>
______________________________<wbr>_________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr"><p><span style=3D"font=
-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1f4=
97d">John P. Field </span><span style=3D"font-size:9.0pt;font-family:&quot;=
Arial&quot;,&quot;sans-serif&quot;;color:#1f497d">|=C2=A0Security PM |=C2=
=A0Pivotal=C2=A0</span><span style=3D"font-size:9.0pt;font-family:&quot;Ari=
al&quot;,&quot;sans-serif&quot;;color:#1f497d"><br></span></p><p><span styl=
e=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;c=
olor:#1f497d">Direct: (908) 962-3394 | <a href=3D"mailto:jfield@gopivotal.c=
om" target=3D"_blank">jfield@</a><a href=3D"http://pivotal.io" target=3D"_b=
lank">pivotal.io</a>=C2=A0=C2=A0</span></p></div></div></div></div></div></=
div>
</div>

--047d7b86e4f8805d1205399080a9--


From nobody Mon Aug  8 13:05:13 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6BA612B03F; Mon,  8 Aug 2016 13:05:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147068670680.30421.13555505057883053116.idtracker@ietfa.amsl.com>
Date: Mon, 08 Aug 2016 13:05:06 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/-q7b3OAR5dmcg6vRqSccPBQACYk>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 20:05:07 -0000

IANA action state changed to In Progress
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/


From nobody Tue Aug  9 08:03:01 2016
Return-Path: <jfield@pivotal.io>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5986112D8BD for <mile@ietfa.amsl.com>; Tue,  9 Aug 2016 08:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pivotal-io.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9vzP_o8TkNI for <mile@ietfa.amsl.com>; Tue,  9 Aug 2016 08:02:57 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 8606B12D8A5 for <mile@ietf.org>; Tue,  9 Aug 2016 08:02:56 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id o80so41231884wme.1 for <mile@ietf.org>; Tue, 09 Aug 2016 08:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jCWiNtzQvegzd8/JAj7xo8dqu1TepfupbeEhsZD9wrA=; b=LThc/PJHem43lyMI/BEQfk8xIIohMIEQMxybH9z9i5LakRu1A6HDxzj2DigaGQBjKA za6JEVvaaHqvgRoxJB2nwpv5va6KuLVtci/Vr9EFeMhx8yt/0aTVixZebbmFU2y8gfSK fdVLitmznnN7gdKWZsd1gmcyXnE5e0aPQL7dx8iqXsHRLck8yrPxOf3hu/XDZknF+S5p N0wG5YMQUsv7JpXUvAcO5K+ppPvVbkRhhGP13nTUb24YV+AvRTA8T+03i4YUpXf3rDmW Vl3CxaBZ80pb09K8adzMDfnEghFgNyL5WqxWWqXV4MJlbR7dkb7eQZXJwGb8Xf0sHPXI 0/tQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jCWiNtzQvegzd8/JAj7xo8dqu1TepfupbeEhsZD9wrA=; b=UurG3G+IY5KBM4TXCac3aMkFiKQ4cyVN7l8yVB72xAMzmgXiYowDPw+iaQcXPEN+d3 /oJD+DAVcdxXqL9Ju9ta0aUbhUjtlZRPR/KDMaFnlMk48oNb5eOEiqmlRPfADMK6oNgL qZ5dS/Wy4V29Sas/CCfW3UNu07+iwprk3hQsyk017u7dSZJEYKGSmWDI7yiLoDqSpe4e 19s9nehzmlylEQNs2AcEVAnHSgoG2myi8bizUJ3vwKUa9LTBvqOY7g5fR4VnIMC3J5/P z1ANXO5R8MnrYbpPJtdkUkxt4JfvyMDdcLTnnIpWSLa656/UwdbMM/VqDCHJOcLgdC2G DTgg==
X-Gm-Message-State: AEkoouvpb7wg9xSWN9mfaOxKsokkoLNg7rLo5qJcnrFPXuPy9XgFUqfvRLkYX5Zcqa0aYg30RPcHAo8la+1/xn6V
X-Received: by 10.194.120.129 with SMTP id lc1mr90185628wjb.131.1470754974823;  Tue, 09 Aug 2016 08:02:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.33.161 with HTTP; Tue, 9 Aug 2016 08:02:54 -0700 (PDT)
In-Reply-To: <22437a2cda434a7abcb916aef93730a8@XCH-ALN-010.cisco.com>
References: <D3C4C9CA.18380B%ncamwing@cisco.com> <22437a2cda434a7abcb916aef93730a8@XCH-ALN-010.cisco.com>
From: John Field <jfield@pivotal.io>
Date: Tue, 9 Aug 2016 11:02:54 -0400
Message-ID: <CAC0wChHQ3zYwYNHv6VhLd7tBUf6q2pKSr5K7xR1mVzOtWYSZdA@mail.gmail.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Content-Type: multipart/alternative; boundary=089e01227b12d3a0c70539a4d356
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/kcPJHj8uLQ1T9qkW64sFErJj6yk>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 15:02:59 -0000

--089e01227b12d3a0c70539a4d356
Content-Type: text/plain; charset=UTF-8

+1

While support for XML is being maintained in the installed base, it is
clear that JSON is the mainstream / preferred format for new development.


Thanks,
John

On Mon, Aug 1, 2016 at 4:42 PM, Panos Kampanakis (pkampana) <
pkampana@cisco.com> wrote:

> +1 on adopting it as a WG item.
>
>
>
> The misunderstanding that XML based info sharing standards are impractical
> for today where JSON is widely preferred is pretty common and this draft
> can help explain that the data representation does not really pose
> limitations to the schema itself.
>
>
>
>
>
> *From:* mile [mailto:mile-bounces@ietf.org] *On Behalf Of *Nancy
> Cam-Winget (ncamwing)
> *Sent:* Monday, August 01, 2016 12:42 PM
> *To:* mile@ietf.org
> *Subject:* [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG
> draft
>
>
>
> Hello,
>
>
>
> At IETF 96 Berlin MILE meeting there was agreement that we should adopt
> https://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/
>
> as a WG draft.  This is the official call for adoption for that draft.
>
>
>
> Please reply with any comments or concerns along your support of this
> action to the mailing list.
>
>
>
> Thanks,
>
> Nancy
>
>
>
>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
>


-- 

John P. Field | Security PM | Pivotal

Direct: (908) 962-3394 | jfield@ <jfield@gopivotal.com>pivotal.io

--089e01227b12d3a0c70539a4d356
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">+1=C2=A0<div><br></div><div>While support for XML is being=
 maintained in the installed base, it is clear that JSON is the mainstream =
/ preferred format for new development.</div><div><br></div><div><br>Thanks=
,</div><div>John=C2=A0</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Aug 1, 2016 at 4:42 PM, Panos Kampanakis (pkampana=
) <span dir=3D"ltr">&lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_bl=
ank">pkampana@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">+1 on adopting it as a WG item.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">The misunderstanding that XML based i=
nfo sharing standards are impractical for today where JSON is widely prefer=
red is pretty common and this draft can help explain
 that the data representation does not really pose limitations to the schem=
a itself.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> mile [mailto:<a href=3D"mailto=
:mile-bounces@ietf.org" target=3D"_blank">mile-bounces@ietf.org</a>]
<b>On Behalf Of </b>Nancy Cam-Winget (ncamwing)<br>
<b>Sent:</b> Monday, August 01, 2016 12:42 PM<br>
<b>To:</b> <a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org=
</a><br>
<b>Subject:</b> [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as=
 WG draft<u></u><u></u></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Hello,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">At IETF 96 Berlin MILE meeting there wa=
s agreement that we should adopt =C2=A0<a href=3D"https://datatracker.ietf.=
org/doc/draft-takahashi-mile-jsoniodef/" target=3D"_blank">https://datatrac=
ker.ietf.org/<wbr>doc/draft-takahashi-mile-<wbr>jsoniodef/</a><u></u><u></u=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">as a WG draft.=C2=A0 This is the offici=
al call for adoption for that draft.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Please reply with any comments or conce=
rns along your support of this action to the mailing list.=C2=A0</span><spa=
n style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans-serif;colo=
r:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Thanks,</span><span style=3D"font-size:=
10.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:black"><u></u><u></=
u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">Nancy</span><span style=3D"font-size:10=
.5pt;font-family:&quot;Calibri&quot;,sans-serif;color:black"><u></u><u></u>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black"><u></u>=C2=A0<u></u></span></p>
</div>
</div></div></div>
</div>

<br>______________________________<wbr>_________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><div dir=3D"ltr"><p><span style=3D"font-size:9.0=
pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1f497d">John=
 P. Field </span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quo=
t;,&quot;sans-serif&quot;;color:#1f497d">|=C2=A0Security PM |=C2=A0Pivotal=
=C2=A0</span><span style=3D"font-size:9.0pt;font-family:&quot;Arial&quot;,&=
quot;sans-serif&quot;;color:#1f497d"><br></span></p><p><span style=3D"font-=
size:9.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:#1f49=
7d">Direct: (908) 962-3394 | <a href=3D"mailto:jfield@gopivotal.com" target=
=3D"_blank">jfield@</a><a href=3D"http://pivotal.io" target=3D"_blank">pivo=
tal.io</a>=C2=A0=C2=A0</span></p></div></div></div></div></div></div>
</div>

--089e01227b12d3a0c70539a4d356--


From nobody Tue Aug  9 11:20:29 2016
Return-Path: <ncamwing@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D8B12D0D1 for <mile@ietfa.amsl.com>; Tue,  9 Aug 2016 11:20:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.767
X-Spam-Level: 
X-Spam-Status: No, score=-15.767 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZV9ZQWyXiIag for <mile@ietfa.amsl.com>; Tue,  9 Aug 2016 11:20:27 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCF2812B03D for <mile@ietf.org>; Tue,  9 Aug 2016 11:20:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10383; q=dns/txt; s=iport; t=1470766826; x=1471976426; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bHx7QMX5G35aROchcgPzJ+nQ4wko4LLaqb+utRFaTaQ=; b=IWQ6XAeaozciR4M8JEZYMyPf7t1wd8bS/PpDKRcO3sFcTQ1uQRB/TKqI +VPhVFZTwmH2RrC3Eqah9eSDm0GBp9VWF/C2Z1/UTdR1NgTo+kypNv9tS bQHqqlmGP19wYL5HeqC5jc78MZUJpj7PkSmS1Lu6rPBKUuo+yYixlLuF4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0COAgDtHapX/4sNJK1aA4J3TlZ8B7QWh?= =?us-ascii?q?QeBfSSFeQKBTDgUAQEBAQEBAV0nhF4BAQUBARtRCxACAQgOAwMBAQEoBycLFAk?= =?us-ascii?q?IAgQBDQWIMQ7BLQEBAQEBAQEBAQEBAQEBAQEBAQEBARyKd4RgARUICYUUBY5Ri?= =?us-ascii?q?mgBhhyIbYFrToQNiH2MNIN3AR42g3puhi1/AQEB?=
X-IronPort-AV: E=Sophos;i="5.28,495,1464652800";  d="scan'208,217";a="306958822"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Aug 2016 18:20:26 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u79IKPq3031205 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 Aug 2016 18:20:25 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 9 Aug 2016 14:20:25 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Tue, 9 Aug 2016 14:20:24 -0400
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: John Field <jfield@pivotal.io>, "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Thread-Topic: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
Thread-Index: AQHR7BOPuQ0OeSBg6kWugmke/WvvVKA0kb1AgAx3YAD//8HTAA==
Date: Tue, 9 Aug 2016 18:20:24 +0000
Message-ID: <D3CF6CC1.184615%ncamwing@cisco.com>
References: <D3C4C9CA.18380B%ncamwing@cisco.com> <22437a2cda434a7abcb916aef93730a8@XCH-ALN-010.cisco.com> <CAC0wChHQ3zYwYNHv6VhLd7tBUf6q2pKSr5K7xR1mVzOtWYSZdA@mail.gmail.com>
In-Reply-To: <CAC0wChHQ3zYwYNHv6VhLd7tBUf6q2pKSr5K7xR1mVzOtWYSZdA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.85.144]
Content-Type: multipart/alternative; boundary="_000_D3CF6CC1184615ncamwingciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/OapS9OGy6bseT_4iTNxefGBIra4>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:20:28 -0000

--_000_D3CF6CC1184615ncamwingciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Speaking as an individual.....I also support adopting this as a WG item.

Thanks, nancy

From: John Field <jfield@pivotal.io<mailto:jfield@pivotal.io>>
Date: Tuesday, August 9, 2016 at 8:02 AM
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com<mailto:pkampana@cisco=
.com>>
Cc: "ncamwing@cisco.com<mailto:ncamwing@cisco.com>" <ncamwing@cisco.com<mai=
lto:ncamwing@cisco.com>>, "mile@ietf.org<mailto:mile@ietf.org>" <mile@ietf.=
org<mailto:mile@ietf.org>>
Subject: Re: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG=
 draft

+1

While support for XML is being maintained in the installed base, it is clea=
r that JSON is the mainstream / preferred format for new development.


Thanks,
John

On Mon, Aug 1, 2016 at 4:42 PM, Panos Kampanakis (pkampana) <pkampana@cisco=
.com<mailto:pkampana@cisco.com>> wrote:
+1 on adopting it as a WG item.

The misunderstanding that XML based info sharing standards are impractical =
for today where JSON is widely preferred is pretty common and this draft ca=
n help explain that the data representation does not really pose limitation=
s to the schema itself.


From: mile [mailto:mile-bounces@ietf.org<mailto:mile-bounces@ietf.org>] On =
Behalf Of Nancy Cam-Winget (ncamwing)
Sent: Monday, August 01, 2016 12:42 PM
To: mile@ietf.org<mailto:mile@ietf.org>
Subject: [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as WG dra=
ft

Hello,

At IETF 96 Berlin MILE meeting there was agreement that we should adopt  ht=
tps://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/
as a WG draft.  This is the official call for adoption for that draft.

Please reply with any comments or concerns along your support of this actio=
n to the mailing list.

Thanks,
Nancy



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




--

John P. Field | Security PM | Pivotal

Direct: (908) 962-3394 | jfield@<mailto:jfield@gopivotal.com>pivotal.io<htt=
p://pivotal.io>

--_000_D3CF6CC1184615ncamwingciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <1B5F1F248DE8EF4A8206E011EEB27575@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Speaking as an individual&#8230;..I also support adopting this as a WG=
 item.</div>
<div><br>
</div>
<div>Thanks, nancy</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>John Field &lt;<a href=3D"mai=
lto:jfield@pivotal.io">jfield@pivotal.io</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, August 9, 2016 at 8:=
02 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;Panos Kampanakis (pkampan=
a)&quot; &lt;<a href=3D"mailto:pkampana@cisco.com">pkampana@cisco.com</a>&g=
t;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:ncamwin=
g@cisco.com">ncamwing@cisco.com</a>&quot; &lt;<a href=3D"mailto:ncamwing@ci=
sco.com">ncamwing@cisco.com</a>&gt;, &quot;<a href=3D"mailto:mile@ietf.org"=
>mile@ietf.org</a>&quot; &lt;<a href=3D"mailto:mile@ietf.org">mile@ietf.org=
</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [mile] Consensus to ad=
opt draft-takahashi-mile-jsoniodef as WG draft<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">&#43;1&nbsp;
<div><br>
</div>
<div>While support for XML is being maintained in the installed base, it is=
 clear that JSON is the mainstream / preferred format for new development.<=
/div>
<div><br>
</div>
<div><br>
Thanks,</div>
<div>John&nbsp;</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Mon, Aug 1, 2016 at 4:42 PM, Panos Kampanakis=
 (pkampana)
<span dir=3D"ltr">&lt;<a href=3D"mailto:pkampana@cisco.com" target=3D"_blan=
k">pkampana@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&#43;1 on adopting it as a WG item.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">The misunderstanding that XML based=
 info sharing standards are impractical for today where JSON is widely pref=
erred is pretty common and this draft
 can help explain that the data representation does not really pose limitat=
ions to the schema itself.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 11pt; font-family: Cali=
bri, sans-serif;">From:</span></b><span style=3D"font-size: 11pt; font-fami=
ly: Calibri, sans-serif;"> mile [mailto:<a href=3D"mailto:mile-bounces@ietf=
.org" target=3D"_blank">mile-bounces@ietf.org</a>]
<b>On Behalf Of </b>Nancy Cam-Winget (ncamwing)<br>
<b>Sent:</b> Monday, August 01, 2016 12:42 PM<br>
<b>To:</b> <a href=3D"mailto:mile@ietf.org" target=3D"_blank">mile@ietf.org=
</a><br>
<b>Subject:</b> [mile] Consensus to adopt draft-takahashi-mile-jsoniodef as=
 WG draft<u></u><u></u></span></p>
</div>
</div>
<div>
<div class=3D"h5">
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">Hello,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">At IETF 96 Berlin MILE meeting there was agr=
eement that we should adopt &nbsp;<a href=3D"https://datatracker.ietf.org/d=
oc/draft-takahashi-mile-jsoniodef/" target=3D"_blank">https://datatracker.i=
etf.org/<wbr>doc/draft-takahashi-mile-<wbr>jsoniodef/</a><u></u><u></u></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;">as a WG draft.&nbsp; This is the official ca=
ll for adoption for that draft.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 13.5pt; font-family: Calib=
ri, sans-serif; color: black;">Please reply with any comments or concerns a=
long your support of this action to the mailing list.&nbsp;</span><span sty=
le=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><=
u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 13.5pt; font-family: Calib=
ri, sans-serif; color: black;">Thanks,</span><span style=3D"font-size: 10.5=
pt; font-family: Calibri, sans-serif; color: black;"><u></u><u></u></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 13.5pt; font-family: Calib=
ri, sans-serif; color: black;">Nancy</span><span style=3D"font-size: 10.5pt=
; font-family: Calibri, sans-serif; color: black;"><u></u><u></u></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><u></u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 10.5pt; font-family: Calib=
ri, sans-serif; color: black;"><u></u>&nbsp;<u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
mile mailing list<br>
<a href=3D"mailto:mile@ietf.org">mile@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mile" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mile</a><br>
<br>
</blockquote>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">
<div dir=3D"ltr">
<div>
<div dir=3D"ltr">
<div>
<div dir=3D"ltr">
<p><span style=3D"font-size: 9pt; font-family: Arial, sans-serif; color: rg=
b(31, 73, 125);">John P. Field
</span><span style=3D"font-size: 9pt; font-family: Arial, sans-serif; color=
: rgb(31, 73, 125);">|&nbsp;Security PM |&nbsp;Pivotal&nbsp;</span><span st=
yle=3D"font-size: 9pt; font-family: Arial, sans-serif; color: rgb(31, 73, 1=
25);"><br>
</span></p>
<p><span style=3D"font-size: 9pt; font-family: Arial, sans-serif; color: rg=
b(31, 73, 125);">Direct: (908) 962-3394 |
<a href=3D"mailto:jfield@gopivotal.com" target=3D"_blank">jfield@</a><a hre=
f=3D"http://pivotal.io" target=3D"_blank">pivotal.io</a>&nbsp;&nbsp;</span>=
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D3CF6CC1184615ncamwingciscocom_--


From nobody Wed Aug 10 06:33:31 2016
Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CAC512D16B for <mile@ietfa.amsl.com>; Wed, 10 Aug 2016 06:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oto3ikGg_Iqo for <mile@ietfa.amsl.com>; Wed, 10 Aug 2016 06:33:28 -0700 (PDT)
Received: from gcc01-CY1-obe.outbound.protection.outlook.com (mail-cy1gcc01on0114.outbound.protection.outlook.com [23.103.200.114]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2087012D0C1 for <mile@ietf.org>; Wed, 10 Aug 2016 06:25:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=05CizP2lZgCw+E2MUKhTzX7znYxu9Mb1wT2ZIiXUlRU=; b=lyRLITmcbdNax3myj4q8zbXoxpE3eep5LpIziJ+5IWr5D9hwUutZmAW9vwF4WkbDUfqQmNV2+Vn7CPCJM0R/jT3YnFoPoE3/6TQ5y/Yb6CK1t/HPVzvRI8QcCSkmVPGvQn/2ZYIGFOAoEMYMwG8oad41cXAVUWg3BBUmo0mcPrQ=
Received: from SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) by SN1PR09MB0959.namprd09.prod.outlook.com (10.162.102.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Wed, 10 Aug 2016 13:25:51 +0000
Received: from SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) by SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) with mapi id 15.01.0549.025; Wed, 10 Aug 2016 13:25:51 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: ROLIE Data Model Attributes
Thread-Index: AdHzBy9mrZJcJW/CQg6PTqCMRoXGbg==
Date: Wed, 10 Aug 2016 13:25:51 +0000
Message-ID: <SN1PR09MB09604462FAA0C5706FED286DF01D0@SN1PR09MB0960.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.227.79]
x-ms-office365-filtering-correlation-id: a9b231dc-7faa-4522-7377-08d3c121d966
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0959; 6:fNBqpe9LI5rOl+zU1Beb77N5QAAY/VEOimS8ZlvL6nNHR2JrMIYqVhG/WEZfDkgSqhinELdogmIsjFklQYlLEGO0CFUQb+lKmHGiDwSIF/EIEWV8ze44bXveguvQ6bbe0khGQ7Fhv83L3O0AoI5X4fzbBzr0eDY8FJssebm3EZ2kIOo0ZDqag3JCsqNbjVsAKQIGQf6rf3E6/CiGpbS1E8qsFtjx60wfEHU26UfKhvSGB89mYHhhDhpj0F7N2IGW5BLwXFYiPn2Nk8wP+73NldsELQHKKS3D11ZGwB+f93N2IeeP6dGTdUiEI79DASPdQwl+vFbQGBttH/owNLKuxQ==; 5:/5bkdcuWqHqHuhrdAdZykr40N51AV1VIt54ZaIEMlE6JEG6c5h0LVHtAkaXfkdAaLnAHE1uQBBOcfeQ3XblZTYrdSjNZtQLyqR7WV3K3j5jwckSYayCCmd6OcBDJ1II9/krCzFtb5lVza3P7F15opA==; 24:UdKRmy7fFBT4vwo9znihHMBD4RyoaRlJvm6QSwm6fW4YRlyThZBFN8GC154ugnmKSIhkczd6Xlz+veQga4zuDPytfxqbjbtsZlZsaHsHsHE=; 7:yfIEb96xuATRvdYQuLPYtXYuYJkSxfuVTM++D8y/vKQJQah1yV8+Gu5GJ60b0Vm3O5H1GoetgAVffffkBujSq/cc5LegiYDAkUeWOkS53rbt8w6pvN1oPilfQExHL5K/HrN9MC3q+MJhH262oNpZBfh5QGTMV3VwldLbiLX7bC4lPO+sW19MM3AI024IFCs4juYNv9CNtFZbmA914fjHKSTj+D33q79Ef3un7ovO51CDj6DAYrjKFQVsG/SVAi76
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0959;
x-microsoft-antispam-prvs: <SN1PR09MB095915E323648E572E4805FEF01D0@SN1PR09MB0959.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026);  SRVR:SN1PR09MB0959; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0959; 
x-forefront-prvs: 0030839EEE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(199003)(35754003)(86362001)(790700001)(6116002)(87936001)(2900100001)(102836003)(77096005)(11100500001)(189998001)(15975445007)(3846002)(9686002)(68736007)(97736004)(5002640100001)(10400500002)(33656002)(16236675004)(99286002)(19617315012)(450100001)(107886002)(110136002)(105586002)(66066001)(3280700002)(50986999)(2351001)(229853001)(122556002)(54356999)(3480700004)(81156014)(561944003)(76576001)(101416001)(106356001)(92566002)(7906003)(19625215002)(3660700001)(8936002)(19300405004)(5630700001)(1730700003)(2906002)(74316002)(5640700001)(586003)(7736002)(2501003)(7696003)(7846002)(8676002)(81166006)(19580395003); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0959; H:SN1PR09MB0960.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR09MB09604462FAA0C5706FED286DF01D0SN1PR09MB0960namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Aug 2016 13:25:51.0319 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0959
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/AFz1U9Nx0cqViZztySGgDrTHbXk>
Subject: [mile] ROLIE Data Model Attributes
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 13:33:30 -0000

--_000_SN1PR09MB09604462FAA0C5706FED286DF01D0SN1PR09MB0960namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

Following discussion around ROLIE at IETF 96, there were some issues that w=
e wanted to resolve on list. This email references github issue #33<https:/=
/github.com/CISecurity/ROLIE/issues/33>, duplicated here:


Determine rolie:datamodel Attributes


The following proposal was discussed at IETF 96 MILE WG meeting:



Proposal: Create a new extension element with the following attributes:

  *   ns: Provides a globally unique identifier for the namespace of the da=
ta model.
  *   version (Optional) : The version of the data model.
  *   schema (Optional) : An IRI to the relevant schema resource.
  *   schema-type (Optional): The type of the schema (e.g. XML Schema, Rela=
xNG, JSON-LD).
  *

Resolve the following questions on the list:

  *   Will all content models have an associated namespace?
  *   Should we create an IANA registry linking allowed namespaces to infor=
mation types? See issue #30<https://github.com/CISecurity/ROLIE/issues/30>
  *   Some data model versions are encoded in the namespace. What if the ve=
rsion is not?
  *   If the data model is constrained by a schema, is there value in refer=
encing the schema used?
  *   Most schema formats do not have an associated media type. What vocabu=
lary should we use?
  *   How do we address the encoding of the schema (e.g. UTF-8)? (Suggested=
 by Roman Danyliw).
     *   Perhaps this could be addressed using the mime type for the schema=
 serialization format? This would include the encoding.


Is there any feedback on the proposal or comments regarding the questions? =
Once we've settled on the attributes we can create a Relax NG schema for th=
e rolie:datamodel element. Any and all feedback would be appreciated.

Thanks,
Stephen Banghart


--_000_SN1PR09MB09604462FAA0C5706FED286DF01D0SN1PR09MB0960namp_
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-micr=
osoft-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=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:24.0pt;
	font-family:"Times New Roman",serif;
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman",serif;
	font-weight:bold;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:90129093;
	mso-list-template-ids:1637916668;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:2059082496;
	mso-list-template-ids:-93684540;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</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=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Following discussion around ROLIE at IETF 96, there =
were some issues that we wanted to resolve on list. This email references
<a href=3D"https://github.com/CISecurity/ROLIE/issues/33">github issue #33<=
/a>, duplicated here:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:14.0pt;font-family:&quot;Ti=
mes New Roman&quot;,serif">Determine rolie:datamodel Attributes<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:16.0pt;font-family:&quot;Ti=
mes New Roman&quot;,serif"><o:p>&nbsp;</o:p></span></p>
<p style=3D"margin:0in;margin-bottom:.0001pt">The following proposal was di=
scussed at IETF 96 MILE WG meeting:<o:p></o:p></p>
<p style=3D"margin:0in;margin-bottom:.0001pt"><o:p>&nbsp;</o:p></p>
<p style=3D"margin:0in;margin-bottom:.0001pt">Proposal: Create a new extens=
ion element with the following attributes:<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l0 level1 lfo1">ns: Provides a gl=
obally unique identifier for the namespace of the data model.<o:p></o:p></l=
i><li class=3D"MsoNormal" style=3D"mso-list:l0 level1 lfo1">version (Option=
al) : The version of the data model.<o:p></o:p></li><li class=3D"MsoNormal"=
 style=3D"mso-list:l0 level1 lfo1">schema (Optional) : An IRI to the releva=
nt schema resource.<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-lis=
t:l0 level1 lfo1">schema-type (Optional): The type of the schema (e.g. XML =
Schema, RelaxNG, JSON-LD).<o:p></o:p></li><li class=3D"MsoNormal" style=3D"=
mso-list:l0 level1 lfo1"><o:p>&nbsp;</o:p></li></ul>
<p style=3D"margin:0in;margin-bottom:.0001pt">Resolve the following questio=
ns on the list:
<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo2">Will all content =
models have an associated namespace?<o:p></o:p></li><li class=3D"MsoNormal"=
 style=3D"mso-list:l1 level1 lfo2">Should we create an IANA registry linkin=
g allowed namespaces to information types? See issue
<a href=3D"https://github.com/CISecurity/ROLIE/issues/30" title=3D"Data Mod=
el Enumeration">
#30</a> <o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-list:l1 level1=
 lfo2">Some data model versions are encoded in the namespace. What if the v=
ersion is not?<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-list:l1 =
level1 lfo2">If the data model is constrained by a schema, is there value i=
n referencing the schema used?<o:p></o:p></li><li class=3D"MsoNormal" style=
=3D"mso-list:l1 level1 lfo2">Most schema formats do not have an associated =
media type. What vocabulary should we use?<o:p></o:p></li><li class=3D"MsoN=
ormal" style=3D"mso-list:l1 level1 lfo2">How do we address the encoding of =
the schema (e.g. UTF-8)? (Suggested by Roman Danyliw).
<o:p></o:p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level2 lfo2">Perhaps this coul=
d be addressed using the mime type for the schema serialization format? Thi=
s would include the encoding.<o:p></o:p></li></ul>
</li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is there any feedback on the proposal or comments re=
garding the questions? Once we&#8217;ve settled on the attributes we can cr=
eate a Relax NG schema for the rolie:datamodel element. Any and all feedbac=
k would be appreciated.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Stephen Banghart <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_SN1PR09MB09604462FAA0C5706FED286DF01D0SN1PR09MB0960namp_--


From nobody Wed Aug 10 06:47:19 2016
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39BD12D57B for <mile@ietfa.amsl.com>; Wed, 10 Aug 2016 06:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.769
X-Spam-Level: 
X-Spam-Status: No, score=-15.769 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JDtoFuh1FNS for <mile@ietfa.amsl.com>; Wed, 10 Aug 2016 06:47:11 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D391F12D51A for <mile@ietf.org>; Wed, 10 Aug 2016 06:47:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8041; q=dns/txt; s=iport; t=1470836830; x=1472046430; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QboCe1ynphseRI6b2U8FG612A5p+1iFwlbYYqeqyzb4=; b=AUr1sYxyM6xh8CdN19lFJW5Zg2DKJHzk8FZ9Dhm4NFr+jwdrd1nmJgYp 3053DkG9SHEGhsF3WqzPyOF0QXTCKGSXh51wrw515VY9etUC3C2t6+5Eg Ufmyz497+kFnCKOIaDUIkX7pAzwMdb3hTVneKGCKZwTKoqfuFAQSxtq7u 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAgAwL6tX/40NJK1dg0VWfAesd4wog?= =?us-ascii?q?X0khXkCgVw4FAEBAQEBAQFdJ4ReAQEEAQEBODQLBQcEAgEIEQQBAQEeCQchBgs?= =?us-ascii?q?UCQgCBAENBQgTh3wDDwgOvSYNhDIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYYqg?= =?us-ascii?q?0qBA4JDgVmFfwWZCDQBhhyGOYI1gXKEW4h9iC2EB4N3AR42ghIcgUxuAYVaRn8?= =?us-ascii?q?BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,500,1464652800"; d="scan'208";a="139815355"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Aug 2016 13:47:09 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u7ADl9jB002772 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Aug 2016 13:47:09 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 10 Aug 2016 08:47:08 -0500
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1210.000; Wed, 10 Aug 2016 08:47:08 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, "kathleen.moriarty.ietf@gmail.com" <kathleen.moriarty.ietf@gmail.com>
Thread-Topic: [mile] ROLIE Authorization and Authentication
Thread-Index: AQHfK/jNFlOkRObF2pIEFN2dwFloUAJaJ8z8Aa23yscDdu+hwp/oLG8wgAOgR5A=
Date: Wed, 10 Aug 2016 13:47:08 +0000
Message-ID: <a2e26fa5bc3e46f99ca036104a8c350c@XCH-ALN-010.cisco.com>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com> <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com> <25d201d1f144$cc5aade0$651009a0$@nict.go.jp>
In-Reply-To: <25d201d1f144$cc5aade0$651009a0$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.108.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/f0nGEyqJShWJcJQgETKfZ0xxU24>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 13:47:17 -0000

+1 for option B and John's comment:=20
=20
> We should probably state that doing some sort of AuthN is a "SHOULD," but=
 then delegate details to another draft(s).  That is, using RFC 2119 compli=
ant language of "SHOULD authenticate" but leave it to the implementer to ch=
oose how, could be appropriate here, since in certain circumstances, one co=
uld validly choose not to do any authentication, as long as the implication=
s of that choice are fully understood.



-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Takeshi Takahashi
Sent: Monday, August 08, 2016 3:17 AM
To: kathleen.moriarty.ietf@gmail.com; 'Banghart, Stephen A. (Fed)' <stephen=
.banghart@nist.gov>
Cc: mile@ietf.org
Subject: Re: [mile] ROLIE Authorization and Authentication

Hi all,

Right, we had better solicit more comments.

All, please give us any comment or feedback on this issue.
Comments such as "I do not care either way", or "I cannot say anything at t=
his moment, because" are also welcomed.

We could wait for 2 weeks to get consensus.
Since Stephen has sent the question to the mailing list on 29th July, we co=
uld wait for further comments by 12th August.

Also, if you are willing to review these drafts, please let us know. We app=
reciate that very much.

Cheers,
Take


> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of=20
> kathleen.moriarty.ietf@gmail.com
> Sent: Saturday, August 6, 2016 12:36 AM
> To: Banghart, Stephen A. (Fed)
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
>=20
> Hello,
>=20
> Were there more responses off list in addition to Take & Adam's?  Is=20
> there enough support to review multiple documents?  The chairs may=20
> have a better sense of that.
>=20
> Thank you,
> Kathleen
>=20
> Sent from my iPhone
>=20
> > On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)
> <stephen.banghart@nist.gov> wrote:
> >
> > All,
> >
> > Overall consensus has landed on option B: a brief discussion for the
needs
> for authentication and authorization in the core ROLIE document, then=20
> specific solutions presented in separate drafts. If there is no=20
> objection I'll close the issue.
> >
> > Thanks,
> > Stephen
> >
> > -----Original Message-----
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart,=20
> > Stephen
> A. (Fed)
> > Sent: Tuesday, August 02, 2016 11:24 AM
> > To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
> > Cc: mile@ietf.org
> > Subject: Re: [mile] ROLIE Authorization and Authentication
> >
> > Take and all,
> >
> > Your understanding is correct, there will be a core ROLIE draft and=20
> > a
number
> of additional drafts for specific purposes (CSIRT, checklists, SWID,
etc.).
> Option B would be to create an additional document that discusses=20
> authorization and authentication of ROLIE in more detail.
> >
> > It looks like we're leaning towards option B at the moment, with at=20
> > most
> a brief mention of authentication and authorization in the core, but=20
> no
MTI
> or in-depth discussion. Is there any other input?
> >
> > There are a few more issues raised at IETF 96 around ROLIE that Dave=20
> > or
> I will address to the list in the coming days, and as always, we'd
appreciate
> any feedback on those specific issues, or on ROLIE in general.
> >
> > Thanks,
> > Stephen
> >
> > -----Original Message-----
> > From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
> > Sent: Tuesday, August 02, 2016 1:31 AM
> > To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen A.
> (Fed) <stephen.banghart@nist.gov>
> > Cc: mile@ietf.org
> > Subject: RE: [mile] ROLIE Authorization and Authentication
> >
> > Hi Stephen and all,
> >
> > In my understanding, we will have at least two drafts: one for=20
> > general
> purpose (current ROLIE core draft) and another for incident response=20
> purpose.
> > If Option B talks about separate drafts that are neither of the two
drafts,
> I agree with you and Adam's comment.
> >
> > Apart from options A and B, it could be also fine to talk about
authorization
> and authorization in the general purpose draft (ROLIE core
> > draft) without mandating any specific technique.
> >
> > Kind regards,
> > Take
> >
> >
> >
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam=20
> > Montville
> > Sent: Monday, August 1, 2016 12:52 AM
> > To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
> > Cc: mile@ietf.org
> > Subject: Re: [mile] ROLIE Authorization and Authentication
> >
> > Hi Stephen,
> >
> > If the primary purpose of ROLIE is to make public information=20
> > available,
> then leaving the authentication piece to separate drafts (your Option=20
> B) seems to make sense.  My interest in ROLIE is centered on the=20
> ability to syndicate configuration checklists, which is a class of=20
> security
automation
> information generally available to the public.
> >
> > I suspect that information sharing organizations may have a=20
> > different
> perspective.
> >
> > I cannot authoritatively speak to which mechanism(s) would be best,=20
> > but
> it seems to be the case that OAUTH is widely used for many REST APIs=20
> in
the
> wild.  I have not seen XACML used in such a context.  I'm also not=20
> sure
that
> we should get into authorization.
> >
> > Kind regards,
> >
> > Adam
> >
> > On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
> <mailto:stephen.banghart@nist.gov> wrote:
> >
> > Hello all,
> >
> > Following the discussion at IETF 96 on draft-ietf-mile-rolie-03,=20
> > there
> are some issues that we wanted to bring to the mailing list for
discussion.
> This e-mail references GitHub issue #34=20
> (https://github.com/CISecurity/ROLIE/issues/34). The text from the=20
> issue is duplicated here for convenience:
> >
> > Authentication and authorization can be handled using a number of
different
> mechanisms, for this reason it's not clear if we can require a=20
> specific mechanism in the ROLIE core. More discussion is needed with=20
> the working
group
> to determine a way forward.
> >
> > Proposals:
> >
> > - A: Select one or more authentication and authorization mechanisms=20
> > as
> mandatory to implement (MTI).
> > - B: Address these issues in separate drafts.
> >
> >
> > Support for OAUTH, http-auth, and XACML has been discussed in a=20
> > limited
> capacity previously. Given that deployed solutions may require=20
> different authentication and authorization solutions based on=20
> differing deployment requirements, we are concerned about requiring any s=
ingle solution.
> > Furthermore, defining requirements for multiple solutions will add
> significant page count to the draft. As a result, we are leaning=20
> towards proposal B which would allow for some modularity in solutions=20
> through additional drafts.
> >
> > Are there any concerns with going this route?
> >
> > If option A is desired, we could use some help from someone
knowledgeable
> in using authentication and authorization solutions with HTTP RESTful=20
> services.
> >
> > Thanks,
> > Stephen Banghart
> >
> > _______________________________________________
> > mile mailing list
> > mailto:mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> >
> >
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

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


From nobody Tue Aug 16 03:05:08 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C27B612B04C; Tue, 16 Aug 2016 03:05:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147134190679.31052.16891679259321291316.idtracker@ietfa.amsl.com>
Date: Tue, 16 Aug 2016 03:05:06 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/LwMYDT488_JkToFxU6Y7mQJMcI0>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2016 10:05:07 -0000

IANA action state changed to Waiting on Authors
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/


From nobody Wed Aug 17 12:09:10 2016
Return-Path: <iana-shared@icann.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id DA6E912B039; Wed, 17 Aug 2016 12:09:08 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE59012B04F for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Wed, 17 Aug 2016 12:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.446
X-Spam-Level: 
X-Spam-Status: No, score=-4.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJlFeVWuwZIW for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Wed, 17 Aug 2016 12:09:04 -0700 (PDT)
Received: from smtp02.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0B9512B039 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Wed, 17 Aug 2016 12:09:03 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp02.icann.org (Postfix) with ESMTP id 4522AE33E7 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Wed, 17 Aug 2016 19:09:03 +0000 (UTC)
Received: by request3.lax.icann.org (Postfix, from userid 48) id 0BE40C20550; Wed, 17 Aug 2016 19:09:03 +0000 (UTC)
RT-Owner: amanda.baber
From: "Amanda Baber via RT" <drafts-approval@iana.org>
In-Reply-To: <20160803150200.6140.54785.idtracker@ietfa.amsl.com>
References: <RT-Ticket-921487@icann.org> <20160803150200.6140.54785.idtracker@ietfa.amsl.com>
Message-ID: <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #921487
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 17 Aug 2016 19:09:03 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Resent-From: <alias-bounces@ietf.org>
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160817190908.DA6E912B039@ietfa.amsl.com>
Resent-Date: Wed, 17 Aug 2016 12:09:08 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/qfLgiDCJzYNuenvJBFiD40Bbjdw>
Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
Subject: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: drafts-approval@iana.org
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 19:09:09 -0000

Dear Roman,

The actions for this document are complete. The designated expert for the XML registries, however, has comments:

"It looks good. Two nits:

schemaLocation attributes are a bad idea
the definition of TimeZone allows for seconds, which is unnecessary (I think)"

If you want to make changes during AUTH48, the RFC Editor will contact us and tell us which updates to make. Alternatively, if you want to make changes now, just let us know.

Please review the actions below and let us know whether we've completed them correctly. When we receive your confirmation, we'll tell the RFC Editor the IANA actions are complete.

ACTION 1:

IANA has added the following entry to the IETF XML ns registry:

iodef-2.0	
urn:ietf:params:xml:ns:iodef-2.0	
http://www.iana.org/assignments/xml-registry/ns/iodef-2.0.txt	
[RFC-ietf-mile-rfc5070-bis-25]  

Please see
http://www.iana.org/assignments/xml-registry


ACTION 2:

IANA has added the following entry to the IESG XML schema registry:

iodef-2.0	
urn:ietf:params:xml:schema:iodef-2.0	
http://www.iana.org/assignments/xml-registry/schema/iodef-2.0.xsd	
[RFC-ietf-mile-rfc5070-bis-25]

Please see
http://www.iana.org/assignments/xml-registry


ACTION 3:

IANA has created 34 registries under the "Incident Object Description Exchange Format v2 (IODEF)" heading at 

http://www.iana.org/assignments/iodef2


Can we tell the RFC Editor these are complete?

Best regards,

Amanda Baber
IANA Lead Specialist
ICANN


From nobody Wed Aug 17 20:10:18 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF54012D834 for <mile@ietfa.amsl.com>; Wed, 17 Aug 2016 20:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtT_ZZ0U8EPs for <mile@ietfa.amsl.com>; Wed, 17 Aug 2016 20:10:14 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA74412D593 for <mile@ietf.org>; Wed, 17 Aug 2016 20:10:13 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id u7I3A65J047568; Thu, 18 Aug 2016 12:10:08 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw1.nict.go.jp  with ESMTP id u7I3A6Hc047561; Thu, 18 Aug 2016 12:10:06 +0900 (JST)
Received: from VAIO (unknown [133.243.28.206]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTPS id 338AC7FB7; Thu, 18 Aug 2016 12:10:06 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: "'Banghart, Stephen A. \(Fed\)'" <stephen.banghart@nist.gov>, <mile@ietf.org>
References: <SN1PR09MB09604462FAA0C5706FED286DF01D0@SN1PR09MB0960.namprd09.prod.outlook.com>
In-Reply-To: <SN1PR09MB09604462FAA0C5706FED286DF01D0@SN1PR09MB0960.namprd09.prod.outlook.com>
Date: Thu, 18 Aug 2016 12:10:08 +0900
Message-ID: <005e01d1f8fe$068360f0$138a22d0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQBc56RPIa/EGSciEWNSnGARwhx0GKM4Izyg
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith1
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/hIfmv3-ewxWZmy5M3VRkPFzKHzU>
Subject: Re: [mile] ROLIE Data Model Attributes
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 03:10:17 -0000

Hi,

> Should we create an IANA registry linking allowed namespaces to
information types? See issue #30 

In the github, you have summarized like this: "This was discussed at the
IETF 96 MILE WG meeting. Roman Danyliw suggested that we enumerate the data
models supported by a given information type. An open-world approach should
be taken, allowing private extensions to be used. We need to work out a
mechanism to support this, and propose the solution to the list."

+1.

Clarification question.

Here is my understanding: Once we register the categories to the IANA
registry, I guess we will put a restriction on the value of the "term"
attribute inside "category" element (when scheme =
"urn:ietf:params:rolie:information-type"), but we allow private extensions
by allowing people to define their own Category Document.
If so, will the notional examples of information types mentioned in Section
8.1 become the initial list of IANA table values?

Thank you.

Take


From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, Stephen A.
(Fed)
Sent: Wednesday, August 10, 2016 10:26 PM
To: mile@ietf.org
Subject: [mile] ROLIE Data Model Attributes

All,

Following discussion around ROLIE at IETF 96, there were some issues that we
wanted to resolve on list. This email references github issue #33,
duplicated here:


Determine rolie:datamodel Attributes

The following proposal was discussed at IETF 96 MILE WG meeting:

Proposal: Create a new extension element with the following attributes:
. ns: Provides a globally unique identifier for the namespace of the data
model.
. version (Optional) : The version of the data model.
. schema (Optional) : An IRI to the relevant schema resource.
. schema-type (Optional): The type of the schema (e.g. XML Schema, RelaxNG,
JSON-LD).
. 
Resolve the following questions on the list: 
. Will all content models have an associated namespace?
. Should we create an IANA registry linking allowed namespaces to
information types? See issue #30 
. Some data model versions are encoded in the namespace. What if the version
is not?
. If the data model is constrained by a schema, is there value in
referencing the schema used?
. Most schema formats do not have an associated media type. What vocabulary
should we use?
. How do we address the encoding of the schema (e.g. UTF-8)? (Suggested by
Roman Danyliw). 
o Perhaps this could be addressed using the mime type for the schema
serialization format? This would include the encoding.


Is there any feedback on the proposal or comments regarding the questions?
Once we've settled on the attributes we can create a Relax NG schema for the
rolie:datamodel element. Any and all feedback would be appreciated.

Thanks,
Stephen Banghart 



From nobody Thu Aug 18 00:39:19 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7A112B011 for <mile@ietfa.amsl.com>; Thu, 18 Aug 2016 00:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYdVhkdYv_26 for <mile@ietfa.amsl.com>; Thu, 18 Aug 2016 00:39:14 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id F2E9412D0ED for <mile@ietf.org>; Thu, 18 Aug 2016 00:39:13 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id u7I7dDDG084857 for <mile@ietf.org>; Thu, 18 Aug 2016 16:39:13 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw2.nict.go.jp  with ESMTP id u7I7dCpK084854 for <mile@ietf.org>; Thu, 18 Aug 2016 16:39:12 +0900 (JST)
Received: from VAIO (unknown [133.243.28.206]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTPS id BF82B7828 for <mile@ietf.org>; Thu, 18 Aug 2016 16:39:12 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <0ecd01d1ec7e$fc80f800$f582e800$@nict.go.jp> <SN1PR09MB096079DF68C98B4E0A05C3D1F0050@SN1PR09MB0960.namprd09.prod.outlook.com> <SN1PR09MB09609270A079E4BA9E696DAFF0180@SN1PR09MB0960.namprd09.prod.outlook.com> <5000C137-2A66-4C28-AA36-8B312B5D5B59@gmail.com> <25d201d1f144$cc5aade0$651009a0$@nict.go.jp> <a2e26fa5bc3e46f99ca036104a8c350c@XCH-ALN-010.cisco.com>
In-Reply-To: <a2e26fa5bc3e46f99ca036104a8c350c@XCH-ALN-010.cisco.com>
Date: Thu, 18 Aug 2016 16:39:14 +0900
Message-ID: <008f01d1f923$9e611870$db234950$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHfK/jNFlOkRObF2pIEFN2dwFloUAJaJ8z8Aa23yscDdu+hwgD9C68aAYtmpdGf46oS8A==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/Mz3kqJ6oP-vAq3b21YyGWv5RDcA>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 07:39:17 -0000

All,

Thank you very much for the comments.
As you can see from the discussion, the MILE community wishes to take the
option B.

Note that you can see the list of discussion issues on github.
Please feel free to join the discussion.
https://github.com/CISecurity/ROLIE/issues/

Best regards,
Take


> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Panos Kampanakis
> (pkampana)
> Sent: Wednesday, August 10, 2016 10:47 PM
> To: Takeshi Takahashi; kathleen.moriarty.ietf@gmail.com
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
> 
> +1 for option B and John's comment:
> 
> > We should probably state that doing some sort of AuthN is a "SHOULD,"
but
> then delegate details to another draft(s).  That is, using RFC 2119
> compliant language of "SHOULD authenticate" but leave it to the
implementer
> to choose how, could be appropriate here, since in certain circumstances,
> one could validly choose not to do any authentication, as long as the
> implications of that choice are fully understood.
> 
> 
> 
> -----Original Message-----
> From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Takeshi Takahashi
> Sent: Monday, August 08, 2016 3:17 AM
> To: kathleen.moriarty.ietf@gmail.com; 'Banghart, Stephen A. (Fed)'
> <stephen.banghart@nist.gov>
> Cc: mile@ietf.org
> Subject: Re: [mile] ROLIE Authorization and Authentication
> 
> Hi all,
> 
> Right, we had better solicit more comments.
> 
> All, please give us any comment or feedback on this issue.
> Comments such as "I do not care either way", or "I cannot say anything at
> this moment, because" are also welcomed.
> 
> We could wait for 2 weeks to get consensus.
> Since Stephen has sent the question to the mailing list on 29th July, we
> could wait for further comments by 12th August.
> 
> Also, if you are willing to review these drafts, please let us know. We
> appreciate that very much.
> 
> Cheers,
> Take
> 
> 
> > -----Original Message-----
> > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of
> > kathleen.moriarty.ietf@gmail.com
> > Sent: Saturday, August 6, 2016 12:36 AM
> > To: Banghart, Stephen A. (Fed)
> > Cc: mile@ietf.org
> > Subject: Re: [mile] ROLIE Authorization and Authentication
> >
> > Hello,
> >
> > Were there more responses off list in addition to Take & Adam's?  Is
> > there enough support to review multiple documents?  The chairs may
> > have a better sense of that.
> >
> > Thank you,
> > Kathleen
> >
> > Sent from my iPhone
> >
> > > On Aug 5, 2016, at 10:20 AM, Banghart, Stephen A. (Fed)
> > <stephen.banghart@nist.gov> wrote:
> > >
> > > All,
> > >
> > > Overall consensus has landed on option B: a brief discussion for the
> needs
> > for authentication and authorization in the core ROLIE document, then
> > specific solutions presented in separate drafts. If there is no
> > objection I'll close the issue.
> > >
> > > Thanks,
> > > Stephen
> > >
> > > -----Original Message-----
> > > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Banghart,
> > > Stephen
> > A. (Fed)
> > > Sent: Tuesday, August 02, 2016 11:24 AM
> > > To: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
> > > Cc: mile@ietf.org
> > > Subject: Re: [mile] ROLIE Authorization and Authentication
> > >
> > > Take and all,
> > >
> > > Your understanding is correct, there will be a core ROLIE draft and
> > > a
> number
> > of additional drafts for specific purposes (CSIRT, checklists, SWID,
> etc.).
> > Option B would be to create an additional document that discusses
> > authorization and authentication of ROLIE in more detail.
> > >
> > > It looks like we're leaning towards option B at the moment, with at
> > > most
> > a brief mention of authentication and authorization in the core, but
> > no
> MTI
> > or in-depth discussion. Is there any other input?
> > >
> > > There are a few more issues raised at IETF 96 around ROLIE that Dave
> > > or
> > I will address to the list in the coming days, and as always, we'd
> appreciate
> > any feedback on those specific issues, or on ROLIE in general.
> > >
> > > Thanks,
> > > Stephen
> > >
> > > -----Original Message-----
> > > From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]
> > > Sent: Tuesday, August 02, 2016 1:31 AM
> > > To: 'Adam Montville' <adam.w.montville@gmail.com>; Banghart, Stephen
> A.
> > (Fed) <stephen.banghart@nist.gov>
> > > Cc: mile@ietf.org
> > > Subject: RE: [mile] ROLIE Authorization and Authentication
> > >
> > > Hi Stephen and all,
> > >
> > > In my understanding, we will have at least two drafts: one for
> > > general
> > purpose (current ROLIE core draft) and another for incident response
> > purpose.
> > > If Option B talks about separate drafts that are neither of the two
> drafts,
> > I agree with you and Adam's comment.
> > >
> > > Apart from options A and B, it could be also fine to talk about
> authorization
> > and authorization in the general purpose draft (ROLIE core
> > > draft) without mandating any specific technique.
> > >
> > > Kind regards,
> > > Take
> > >
> > >
> > >
> > > From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Adam
> > > Montville
> > > Sent: Monday, August 1, 2016 12:52 AM
> > > To: Banghart, Stephen A. (Fed) <stephen.banghart@nist.gov>
> > > Cc: mile@ietf.org
> > > Subject: Re: [mile] ROLIE Authorization and Authentication
> > >
> > > Hi Stephen,
> > >
> > > If the primary purpose of ROLIE is to make public information
> > > available,
> > then leaving the authentication piece to separate drafts (your Option
> > B) seems to make sense.  My interest in ROLIE is centered on the
> > ability to syndicate configuration checklists, which is a class of
> > security
> automation
> > information generally available to the public.
> > >
> > > I suspect that information sharing organizations may have a
> > > different
> > perspective.
> > >
> > > I cannot authoritatively speak to which mechanism(s) would be best,
> > > but
> > it seems to be the case that OAUTH is widely used for many REST APIs
> > in
> the
> > wild.  I have not seen XACML used in such a context.  I'm also not
> > sure
> that
> > we should get into authorization.
> > >
> > > Kind regards,
> > >
> > > Adam
> > >
> > > On Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed)
> > <mailto:stephen.banghart@nist.gov> wrote:
> > >
> > > Hello all,
> > >
> > > Following the discussion at IETF 96 on draft-ietf-mile-rolie-03,
> > > there
> > are some issues that we wanted to bring to the mailing list for
> discussion.
> > This e-mail references GitHub issue #34
> > (https://github.com/CISecurity/ROLIE/issues/34). The text from the
> > issue is duplicated here for convenience:
> > >
> > > Authentication and authorization can be handled using a number of
> different
> > mechanisms, for this reason it's not clear if we can require a
> > specific mechanism in the ROLIE core. More discussion is needed with
> > the working
> group
> > to determine a way forward.
> > >
> > > Proposals:
> > >
> > > - A: Select one or more authentication and authorization mechanisms
> > > as
> > mandatory to implement (MTI).
> > > - B: Address these issues in separate drafts.
> > >
> > >
> > > Support for OAUTH, http-auth, and XACML has been discussed in a
> > > limited
> > capacity previously. Given that deployed solutions may require
> > different authentication and authorization solutions based on
> > differing deployment requirements, we are concerned about requiring any
> single solution.
> > > Furthermore, defining requirements for multiple solutions will add
> > significant page count to the draft. As a result, we are leaning
> > towards proposal B which would allow for some modularity in solutions
> > through additional drafts.
> > >
> > > Are there any concerns with going this route?
> > >
> > > If option A is desired, we could use some help from someone
> knowledgeable
> > in using authentication and authorization solutions with HTTP RESTful
> > services.
> > >
> > > Thanks,
> > > Stephen Banghart
> > >
> > > _______________________________________________
> > > mile mailing list
> > > mailto:mile@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mile
> > >
> > >
> > >
> > > _______________________________________________
> > > mile mailing list
> > > mile@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mile
> > >
> > > _______________________________________________
> > > mile mailing list
> > > mile@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> 
> _______________________________________________
> 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 Mon Aug 22 13:10:34 2016
Return-Path: <rdd@cert.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 5D7A512D7F7; Mon, 22 Aug 2016 13:10:31 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C9F12D80C for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 13:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 8urhzydAIAoO for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 13:10:29 -0700 (PDT)
Received: from shetland.sei.cmu.edu (shetland.sei.cmu.edu [192.58.107.44]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E795912D7F7 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 13:10:25 -0700 (PDT)
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/1543) with ESMTP id u7MK8dfI002039; Mon, 22 Aug 2016 16:08:39 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1471896519; bh=ftsDVnuOK0ra9l/gsEtd8Ggbb1OACbaJUwdmABpBH28=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=gjX0jrgywzdlgo0StT+bX6tmmnSJP8xhMiN69I8wP4S77bD+B8rbui6wDLT+6iG+l nUVK5eZ3O4Loriv+rOWhajOhui5X2UYK4ruq6LEZ8EtHDoDqW9vcprSvumvYqvMGpX 1Q90zK7K6e4rxmw7cqfnUKGitkk9P6MIyKhrWtD8=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by timber.sei.cmu.edu (8.14.4/8.14.4/1543) with ESMTP id u7MK8cAG020477; Mon, 22 Aug 2016 16:08:38 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0279.002; Mon, 22 Aug 2016 16:08:38 -0400
From: "Roman D. Danyliw" <rdd@cert.org>
To: "drafts-approval@iana.org" <drafts-approval@iana.org>
Thread-Topic: [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
Thread-Index: AQHR+LypxT+z9uAV0E6+i4uYGkmJ76BVby2A
Date: Mon, 22 Aug 2016 20:08:38 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC0104E3AFB6@marathon>
References: <RT-Ticket-921487@icann.org> <20160803150200.6140.54785.idtracker@ietfa.amsl.com> <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org>
In-Reply-To: <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Resent-From: <alias-bounces@ietf.org>
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160822201032.5D7A512D7F7@ietfa.amsl.com>
Resent-Date: Mon, 22 Aug 2016 13:10:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/sZ4_Qr-nLarADUtI6JJ3H5TgN3Q>
Cc: "draft-ietf-mile-rfc5070-bis.all@ietf.org" <draft-ietf-mile-rfc5070-bis.all@ietf.org>
Subject: Re: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 20:10:32 -0000

R29vZCBhZnRlcm5vb24gQW1hbmRhIQ0KDQpDb21pbmcgYmFjayBmcm9tIHZhY2F0aW9uLg0KDQpB
Y2sgb24gdGhpcyBlbWFpbCBhbmQgdGhhbmsgeW91IGZvciB0aGUgcmV2aWV3IQ0KDQooMSkgTGV0
IG1lIGNoZWNrIG9uIHRoZSBUaW1lWm9uZSBpc3N1ZS4gIFRoaXMgd2FzIGEgcmVxdWVzdGVkIGNo
YW5nZSBmcm9tIElFU0cgcmV2aWV3Lg0KDQooMikgQ291bGQgdGhlIHJldmlld2VyIHNoYXJlIGEg
Yml0IG1vcmUgY29udGV4dCBvbiAic2NoZW1hTG9jYXRpb24iIG5vdCBiZWluZyBhIGdvb2QgaWRl
YS4gIElzIHRoZXJlIGEgYmV0dGVyIHdheT8NCg0KSSdkIHByZWZlciB0byBjaGFuZ2Ugbm93IHJh
dGhlciB0aGFuIEFVVEg0OCBpZiB0aGVyZSBpcyBhbnl0aGluZyB0byBkby4NCg0KUm9tYW4NCg0K
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbWFuZGEgQmFiZXIgdmlhIFJU
IFttYWlsdG86ZHJhZnRzLWFwcHJvdmFsQGlhbmEub3JnXQ0KPiBTZW50OiBXZWRuZXNkYXksIEF1
Z3VzdCAxNywgMjAxNiAzOjA5IFBNDQo+IENjOiBkcmFmdC1pZXRmLW1pbGUtcmZjNTA3MC1iaXMu
YWxsQGlldGYub3JnDQo+IFN1YmplY3Q6IFtJQU5BICM5MjE0ODddIFByb3RvY29sIEFjdGlvbjog
J1RoZSBJbmNpZGVudCBPYmplY3QgRGVzY3JpcHRpb24NCj4gRXhjaGFuZ2UgRm9ybWF0IHYyJyB0
byBQcm9wb3NlZCBTdGFuZGFyZCAoZHJhZnQtaWV0Zi1taWxlLXJmYzUwNzAtYmlzLQ0KPiAyNS50
eHQpDQo+IA0KPiBEZWFyIFJvbWFuLA0KPiANCj4gVGhlIGFjdGlvbnMgZm9yIHRoaXMgZG9jdW1l
bnQgYXJlIGNvbXBsZXRlLiBUaGUgZGVzaWduYXRlZCBleHBlcnQgZm9yIHRoZQ0KPiBYTUwgcmVn
aXN0cmllcywgaG93ZXZlciwgaGFzIGNvbW1lbnRzOg0KPiANCj4gIkl0IGxvb2tzIGdvb2QuIFR3
byBuaXRzOg0KPiANCj4gc2NoZW1hTG9jYXRpb24gYXR0cmlidXRlcyBhcmUgYSBiYWQgaWRlYSB0
aGUgZGVmaW5pdGlvbiBvZiBUaW1lWm9uZSBhbGxvd3MNCj4gZm9yIHNlY29uZHMsIHdoaWNoIGlz
IHVubmVjZXNzYXJ5IChJIHRoaW5rKSINCj4gDQo+IElmIHlvdSB3YW50IHRvIG1ha2UgY2hhbmdl
cyBkdXJpbmcgQVVUSDQ4LCB0aGUgUkZDIEVkaXRvciB3aWxsIGNvbnRhY3QgdXMNCj4gYW5kIHRl
bGwgdXMgd2hpY2ggdXBkYXRlcyB0byBtYWtlLiBBbHRlcm5hdGl2ZWx5LCBpZiB5b3Ugd2FudCB0
byBtYWtlDQo+IGNoYW5nZXMgbm93LCBqdXN0IGxldCB1cyBrbm93Lg0KPiANCj4gUGxlYXNlIHJl
dmlldyB0aGUgYWN0aW9ucyBiZWxvdyBhbmQgbGV0IHVzIGtub3cgd2hldGhlciB3ZSd2ZSBjb21w
bGV0ZWQNCj4gdGhlbSBjb3JyZWN0bHkuIFdoZW4gd2UgcmVjZWl2ZSB5b3VyIGNvbmZpcm1hdGlv
biwgd2UnbGwgdGVsbCB0aGUgUkZDIEVkaXRvcg0KPiB0aGUgSUFOQSBhY3Rpb25zIGFyZSBjb21w
bGV0ZS4NCj4gDQo+IEFDVElPTiAxOg0KPiANCj4gSUFOQSBoYXMgYWRkZWQgdGhlIGZvbGxvd2lu
ZyBlbnRyeSB0byB0aGUgSUVURiBYTUwgbnMgcmVnaXN0cnk6DQo+IA0KPiBpb2RlZi0yLjANCj4g
dXJuOmlldGY6cGFyYW1zOnhtbDpuczppb2RlZi0yLjANCj4gaHR0cDovL3d3dy5pYW5hLm9yZy9h
c3NpZ25tZW50cy94bWwtcmVnaXN0cnkvbnMvaW9kZWYtMi4wLnR4dA0KPiBbUkZDLWlldGYtbWls
ZS1yZmM1MDcwLWJpcy0yNV0NCj4gDQo+IFBsZWFzZSBzZWUNCj4gaHR0cDovL3d3dy5pYW5hLm9y
Zy9hc3NpZ25tZW50cy94bWwtcmVnaXN0cnkNCj4gDQo+IA0KPiBBQ1RJT04gMjoNCj4gDQo+IElB
TkEgaGFzIGFkZGVkIHRoZSBmb2xsb3dpbmcgZW50cnkgdG8gdGhlIElFU0cgWE1MIHNjaGVtYSBy
ZWdpc3RyeToNCj4gDQo+IGlvZGVmLTIuMA0KPiB1cm46aWV0ZjpwYXJhbXM6eG1sOnNjaGVtYTpp
b2RlZi0yLjANCj4gaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy94bWwtcmVnaXN0cnkv
c2NoZW1hL2lvZGVmLTIuMC54c2QNCj4gW1JGQy1pZXRmLW1pbGUtcmZjNTA3MC1iaXMtMjVdDQo+
IA0KPiBQbGVhc2Ugc2VlDQo+IGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMveG1sLXJl
Z2lzdHJ5DQo+IA0KPiANCj4gQUNUSU9OIDM6DQo+IA0KPiBJQU5BIGhhcyBjcmVhdGVkIDM0IHJl
Z2lzdHJpZXMgdW5kZXIgdGhlICJJbmNpZGVudCBPYmplY3QgRGVzY3JpcHRpb24NCj4gRXhjaGFu
Z2UgRm9ybWF0IHYyIChJT0RFRikiIGhlYWRpbmcgYXQNCj4gDQo+IGh0dHA6Ly93d3cuaWFuYS5v
cmcvYXNzaWdubWVudHMvaW9kZWYyDQo+IA0KPiANCj4gQ2FuIHdlIHRlbGwgdGhlIFJGQyBFZGl0
b3IgdGhlc2UgYXJlIGNvbXBsZXRlPw0KPiANCj4gQmVzdCByZWdhcmRzLA0KPiANCj4gQW1hbmRh
IEJhYmVyDQo+IElBTkEgTGVhZCBTcGVjaWFsaXN0DQo+IElDQU5ODQoNCg==


From nobody Mon Aug 22 14:27:12 2016
Return-Path: <iana-shared@icann.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 6928C12D12E; Mon, 22 Aug 2016 14:27:11 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5D512D1A3 for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 14:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.728
X-Spam-Level: 
X-Spam-Status: No, score=-3.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dylcb8NCi6_o for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 14:27:09 -0700 (PDT)
Received: from smtp02.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6B3112D12E for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 14:27:09 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp02.icann.org (Postfix) with ESMTP id F0E23E3159 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 21:27:08 +0000 (UTC)
Received: by request3.lax.icann.org (Postfix, from userid 48) id BBAA8C20566; Mon, 22 Aug 2016 21:27:08 +0000 (UTC)
RT-Owner: amanda.baber
From: "Amanda Baber via RT" <drafts-approval-comment@iana.org>
In-Reply-To: <rt-4.2.9-9560-1471897478-185.921487-9-0@icann.org>
References: <RT-Ticket-921487@icann.org> <20160803150200.6140.54785.idtracker@ietfa.amsl.com> <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org> <359EC4B99E040048A7131E0F4E113AFC0104E3AFB6@marathon> <rt-4.2.9-9560-1471897478-185.921487-9-0@icann.org>
Message-ID: <rt-4.2.9-9560-1471901228-1634.921487-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #921487
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 22 Aug 2016 21:27:08 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Resent-From: <alias-bounces@ietf.org>
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160822212711.6928C12D12E@ietfa.amsl.com>
Resent-Date: Mon, 22 Aug 2016 14:27:11 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/TBjwamcykqqWT102j_4pUqTvpwo>
Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
Subject: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: drafts-approval-comment@iana.org
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 21:27:11 -0000

I'll check with him. Thanks!

Amanda

On Mon Aug 22 20:24:38 2016, rdd@cert.org wrote:
> Good afternoon Amanda!
> 
> Coming back from vacation.
> 
> Ack on this email and thank you for the review!
> 
> (1) Let me check on the TimeZone issue.  This was a requested change
> from IESG review.
> 
> (2) Could the reviewer share a bit more context on "schemaLocation"
> not being a good idea.  Is there a better way?
> 
> I'd prefer to change now rather than AUTH48 if there is anything to
> do.
> 
> Roman
> 
> > -----Original Message-----
> > From: Amanda Baber via RT [mailto:drafts-approval@iana.org]
> > Sent: Wednesday, August 17, 2016 3:09 PM
> > Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
> > Subject: [IANA #921487] Protocol Action: 'The Incident Object
> > Description
> > Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-
> > bis-
> > 25.txt)
> >
> > Dear Roman,
> >
> > The actions for this document are complete. The designated expert for
> > the
> > XML registries, however, has comments:
> >
> > "It looks good. Two nits:
> >
> > schemaLocation attributes are a bad idea the definition of TimeZone
> > allows
> > for seconds, which is unnecessary (I think)"
> >
> > If you want to make changes during AUTH48, the RFC Editor will
> > contact us
> > and tell us which updates to make. Alternatively, if you want to make
> > changes now, just let us know.
> >
> > Please review the actions below and let us know whether we've
> > completed
> > them correctly. When we receive your confirmation, we'll tell the RFC
> > Editor
> > the IANA actions are complete.
> >
> > ACTION 1:
> >
> > IANA has added the following entry to the IETF XML ns registry:
> >
> > iodef-2.0
> > urn:ietf:params:xml:ns:iodef-2.0
> > http://www.iana.org/assignments/xml-registry/ns/iodef-2.0.txt
> > [RFC-ietf-mile-rfc5070-bis-25]
> >
> > Please see
> > http://www.iana.org/assignments/xml-registry
> >
> >
> > ACTION 2:
> >
> > IANA has added the following entry to the IESG XML schema registry:
> >
> > iodef-2.0
> > urn:ietf:params:xml:schema:iodef-2.0
> > http://www.iana.org/assignments/xml-registry/schema/iodef-2.0.xsd
> > [RFC-ietf-mile-rfc5070-bis-25]
> >
> > Please see
> > http://www.iana.org/assignments/xml-registry
> >
> >
> > ACTION 3:
> >
> > IANA has created 34 registries under the "Incident Object Description
> > Exchange Format v2 (IODEF)" heading at
> >
> > http://www.iana.org/assignments/iodef2
> >
> >
> > Can we tell the RFC Editor these are complete?
> >
> > Best regards,
> >
> > Amanda Baber
> > IANA Lead Specialist
> > ICANN
> 




From nobody Mon Aug 22 15:05:09 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F317212D594; Mon, 22 Aug 2016 15:05:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147190350686.21353.6713821772378134272.idtracker@ietfa.amsl.com>
Date: Mon, 22 Aug 2016 15:05:06 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/BX9-sh64t1PAEGKzdz1rgHk64ZU>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 22:05:08 -0000

IANA action state changed to In Progress
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/


From nobody Mon Aug 22 15:05:17 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA5F12D7C9; Mon, 22 Aug 2016 15:05:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147190350905.21353.18181428740077256762.idtracker@ietfa.amsl.com>
Date: Mon, 22 Aug 2016 15:05:09 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/6baDsi515uCRGQXtfSE6FVfcMTg>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 22:05:09 -0000

IANA action state changed to On Hold
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/


From nobody Mon Aug 22 15:47:15 2016
Return-Path: <iana-shared@icann.org>
X-Original-To: expand-draft-ietf-mile-rfc5070-bis.all@virtual.ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 9D4C512D12D; Mon, 22 Aug 2016 15:47:14 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8EE12D539 for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 15:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.728
X-Spam-Level: 
X-Spam-Status: No, score=-3.728 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4xhdxV5uNp2 for <xfilter-draft-ietf-mile-rfc5070-bis.all@ietfa.amsl.com>; Mon, 22 Aug 2016 15:47:12 -0700 (PDT)
Received: from smtp02.icann.org (smtp01.icann.org [192.0.46.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6B2912D12D for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 15:47:12 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp02.icann.org (Postfix) with ESMTP id 83CBAE31A1 for <draft-ietf-mile-rfc5070-bis.all@ietf.org>; Mon, 22 Aug 2016 22:47:11 +0000 (UTC)
Received: by request3.lax.icann.org (Postfix, from userid 48) id 4F8DCC2041F; Mon, 22 Aug 2016 22:47:11 +0000 (UTC)
RT-Owner: amanda.baber
From: "Amanda Baber via RT" <drafts-approval@iana.org>
In-Reply-To: <rt-4.2.9-9560-1471897478-185.921487-7-0@icann.org>
References: <RT-Ticket-921487@icann.org> <20160803150200.6140.54785.idtracker@ietfa.amsl.com> <rt-4.2.9-15788-1471460942-1043.921487-7-0@icann.org> <359EC4B99E040048A7131E0F4E113AFC0104E3AFB6@marathon> <rt-4.2.9-9560-1471897478-185.921487-7-0@icann.org>
Message-ID: <rt-4.2.9-9288-1471906031-1022.921487-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #921487
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Mon, 22 Aug 2016 22:47:11 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Resent-From: <alias-bounces@ietf.org>
Resent-To: rdd@cert.org, ncamwing@cisco.com, takeshi_takahashi@nict.go.jp, david.waltermire@nist.gov, Kathleen.Moriarty.ietf@gmail.com, stephen.farrell@cs.tcd.ie, mile-chairs@tools.ietf.org, mile@ietf.org
Resent-Message-Id: <20160822224714.9D4C512D12D@ietfa.amsl.com>
Resent-Date: Mon, 22 Aug 2016 15:47:14 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/LHFCQXy1Y21TF1U9YfGMNn49TXI>
Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
Subject: [mile] [IANA #921487] Protocol Action: 'The Incident Object Description Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-bis-25.txt)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: drafts-approval@iana.org
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 22:47:14 -0000

Hi Roman,

The reviewer writes, "Fixing schemaLocation in a spec makes the spec harder to consume. Implementations that want local copies to be used have to modify the doc to use it."

thanks,
Amanda

On Mon Aug 22 20:24:38 2016, rdd@cert.org wrote:
> Good afternoon Amanda!
> 
> Coming back from vacation.
> 
> Ack on this email and thank you for the review!
> 
> (1) Let me check on the TimeZone issue.  This was a requested change
> from IESG review.
> 
> (2) Could the reviewer share a bit more context on "schemaLocation"
> not being a good idea.  Is there a better way?
> 
> I'd prefer to change now rather than AUTH48 if there is anything to
> do.
> 
> Roman
> 
> > -----Original Message-----
> > From: Amanda Baber via RT [mailto:drafts-approval@iana.org]
> > Sent: Wednesday, August 17, 2016 3:09 PM
> > Cc: draft-ietf-mile-rfc5070-bis.all@ietf.org
> > Subject: [IANA #921487] Protocol Action: 'The Incident Object
> > Description
> > Exchange Format v2' to Proposed Standard (draft-ietf-mile-rfc5070-
> > bis-
> > 25.txt)
> >
> > Dear Roman,
> >
> > The actions for this document are complete. The designated expert for
> > the
> > XML registries, however, has comments:
> >
> > "It looks good. Two nits:
> >
> > schemaLocation attributes are a bad idea the definition of TimeZone
> > allows
> > for seconds, which is unnecessary (I think)"
> >
> > If you want to make changes during AUTH48, the RFC Editor will
> > contact us
> > and tell us which updates to make. Alternatively, if you want to make
> > changes now, just let us know.
> >
> > Please review the actions below and let us know whether we've
> > completed
> > them correctly. When we receive your confirmation, we'll tell the RFC
> > Editor
> > the IANA actions are complete.
> >
> > ACTION 1:
> >
> > IANA has added the following entry to the IETF XML ns registry:
> >
> > iodef-2.0
> > urn:ietf:params:xml:ns:iodef-2.0
> > http://www.iana.org/assignments/xml-registry/ns/iodef-2.0.txt
> > [RFC-ietf-mile-rfc5070-bis-25]
> >
> > Please see
> > http://www.iana.org/assignments/xml-registry
> >
> >
> > ACTION 2:
> >
> > IANA has added the following entry to the IESG XML schema registry:
> >
> > iodef-2.0
> > urn:ietf:params:xml:schema:iodef-2.0
> > http://www.iana.org/assignments/xml-registry/schema/iodef-2.0.xsd
> > [RFC-ietf-mile-rfc5070-bis-25]
> >
> > Please see
> > http://www.iana.org/assignments/xml-registry
> >
> >
> > ACTION 3:
> >
> > IANA has created 34 registries under the "Incident Object Description
> > Exchange Format v2 (IODEF)" heading at
> >
> > http://www.iana.org/assignments/iodef2
> >
> >
> > Can we tell the RFC Editor these are complete?
> >
> > Best regards,
> >
> > Amanda Baber
> > IANA Lead Specialist
> > ICANN
> 




From nobody Mon Aug 22 16:05:08 2016
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55C0012D84E; Mon, 22 Aug 2016 16:05:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rdd@cert.org>, <mile-chairs@tools.ietf.org>, <takeshi_takahashi@nict.go.jp>, <Kathleen.Moriarty.ietf@gmail.com>, <mile-chairs@ietf.org>, <mile@ietf.org>, <draft-ietf-mile-rfc5070-bis@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147190710734.29353.17603010669066310053.idtracker@ietfa.amsl.com>
Date: Mon, 22 Aug 2016 16:05:07 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/8OpCQ_5mUINtX_HY6PeYD08gnUQ>
Subject: [mile] ID Tracker State Update Notice: <draft-ietf-mile-rfc5070-bis-25.txt>
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 23:05:07 -0000

IANA action state changed to Waiting on Authors
ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/

