Re: [mile] ROLIE draft

"Takeshi Takahashi" <takeshi_takahashi@nict.go.jp> Thu, 06 March 2014 20:44 UTC

Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 536E11A018D for <mile@ietfa.amsl.com>; Thu, 6 Mar 2014 12:44:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.228
X-Spam-Level: **
X-Spam-Status: No, score=2.228 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FF_IHOPE_YOU_SINK=2.166, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aq9jke7Z43qk for <mile@ietfa.amsl.com>; Thu, 6 Mar 2014 12:43:58 -0800 (PST)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id E81591A0160 for <mile@ietf.org>; Thu, 6 Mar 2014 12:43:57 -0800 (PST)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp with ESMTP id s26Khjta027551; Fri, 7 Mar 2014 05:43:45 +0900 (JST)
Received: from VAIO (ssh.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp with ESMTP id s26KhffS027030; Fri, 7 Mar 2014 05:43:42 +0900 (JST)
From: Takeshi Takahashi <takeshi_takahashi@nict.go.jp>
To: "'Waltermire, David A.'" <david.waltermire@nist.gov>, "'Panos Kampanakis (pkampana)'" <pkampana@cisco.com>, jfield@gopivotal.com, mile@ietf.org
References: <CAO8WYFDn5z1-pBJhCLFVLTb0K_N6kkwqqfcas_yPzuFZt7AiPw@mail.gmail.com> <CF3B8928.60A37%kent_landfield@mcafee.com>, <1C9F17D1873AFA47A969C4DD98F98A750FAFC9BF@xmb-rcd-x10.cisco.com> <08d2c52644c340bf89b9e48f5c5af896@BLUPR09MB038.namprd09.prod.outlook.com>
In-Reply-To: <08d2c52644c340bf89b9e48f5c5af896@BLUPR09MB038.namprd09.prod.outlook.com>
Date: Fri, 07 Mar 2014 05:43:42 +0900
Message-ID: <002401cf397c$c441d390$4cc57ab0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_0025_01CF39C8.342BC580"
X-Mailer: Microsoft Outlook 14.0
thread-index: AQHuC8iURfEOchwPDw51V4LBnkaK1wF2dy5rARb+gg8CWuuNAJpvnenA
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.97.8 at zenith2
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/mile/VtMRkIFneW0Lt95Pk4Za7Fi5G7A
Subject: Re: [mile] ROLIE draft
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 20:44:01 -0000

I like the RESTful approach, so +1.

 

Take

 

 

From: mile [mailto:mile-bounces@ietf.org] On Behalf Of Waltermire, David A.
Sent: Friday, March 7, 2014 2:17 AM
To: Panos Kampanakis (pkampana); jfield@gopivotal.com; mile@ietf.org
Subject: Re: [mile] ROLIE draft

 

+1 and implimenting something related in open source.

 

As I have mentioned before, I believe this type of approach addresses one of
the chartered areas of work in SACM around "content repositories." I am
interested in looking at how we can break up this work into multiple drafts
(e.g., core, MILE use, SACM use) to make it applicable to both WGs, since
parts of the draft is applicable to both WGs, but other aspects are specific
to specialized use cases in each WG. I am willing to work on this if we can
find a way to address both MILE and SACM use cases collectively through
multiple drafts.

 
An

Thanks,

Dave

 

  _____  

From: mile <mile-bounces@ietf.org> on behalf of Panos Kampanakis (pkampana)
<pkampana@cisco.com>
Sent: Wednesday, March 05, 2014 9:51 PM
To: jfield@gopivotal.com; mile@ietf.org
Subject: Re: [mile] ROLIE draft 

 

I think rolie has advantages, so +1.

Panos

 

From: mile [mailto:mile-bounces@ietf.org] On Behalf Of
Kent_Landfield@McAfee.com
Sent: Tuesday, March 04, 2014 2:45 PM
To: jfield@gopivotal.com; mile@ietf.org
Subject: Re: [mile] ROLIE draft

 

+1

 

Kent Landfield

Mobile: +1.817.637.8026

 

From: John Field <jfield@gopivotal.com>
Date: Tuesday, March 4, 2014 at 1:03 PM
To: "mile@ietf.org" <mile@ietf.org>
Subject: [mile] ROLIE draft

 


 

Dear All,

The ROLIE draft (  <http://tools.ietf.org/html/draft-field-mile-rolie-02>
http://tools.ietf.org/html/draft-field-mile-rolie-02 ) whichproposed a
RESTful approach to cyber security information sharing has not seen any
activity in the last six months.   When the -00 draft was first posted,
there was some definite interest in the idea, and there were subsequently
-01 and -02 draft revisions.  However, in recent months the team has clearly
been very busy pursuing other important work.

Unfortunately, due to other commitments I was not able to attend the WG
meeting in London this week, and so I did not request time on the agenda.
But, given that many participants will be focused on MILE-related activities
over the next few days, I thought this might be a good time to send a
reminder and poll the team.  I'd like to know for planning purposes if the
team thinks it will make sense to revisit the RESTful binding discussion at
some point.  It would also be helpful to know if anyone has implemented, or
might be considering an implementation.  

 

Please indicate via, e.g. a simple  +1  if implementing or otherwise
interested.

Thanks,
John

-- 

John P. Field | Security Architect | Pivotal

Direct: (908) 962-3394 | jfield@gopivotal.com  

cid:332B1A9B-BFB1-42CC-8C13-5949BB4B8266 

 <http://www.gopivotal.com/> goPivotal.com