From amontville@tripwire.com Sat Sep 1 06:54:28 2012 Return-Path: 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 3191F11E80FC for ; Sat, 1 Sep 2012 06:54:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.932 X-Spam-Level: X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3WpVQyGXO8yr for ; Sat, 1 Sep 2012 06:54:27 -0700 (PDT) Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 97F5211E80BA for ; Sat, 1 Sep 2012 06:54:27 -0700 (PDT) Received: from mail41-co1-R.bigfish.com (10.243.78.232) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Sat, 1 Sep 2012 13:54:26 +0000 Received: from mail41-co1 (localhost [127.0.0.1]) by mail41-co1-R.bigfish.com (Postfix) with ESMTP id 87320A60211 for ; Sat, 1 Sep 2012 13:54:26 +0000 (UTC) X-Forefront-Antispam-Report: CIP:174.47.84.215; KIP:(null); UIP:(null); IPV:NLI; H:zgw01.tripwire.com; RD:174-47-84-215.static.twtelecom.net; EFVD:NLI X-SpamScore: -25 X-BigFish: VPS-25(zzbb2dI98dI9371I936eI1432Izz1202hzz1033IL8275dhz2dh2a8h668h839h944he5bhf0ah107ah1220h1155h) Received: from mail41-co1 (localhost.localdomain [127.0.0.1]) by mail41-co1 (MessageSwitch) id 1346507663982360_22322; Sat, 1 Sep 2012 13:54:23 +0000 (UTC) Received: from CO1EHSMHS017.bigfish.com (unknown [10.243.78.250]) by mail41-co1.bigfish.com (Postfix) with ESMTP id DC04C240058 for ; Sat, 1 Sep 2012 13:54:23 +0000 (UTC) Received: from zgw01.tripwire.com (174.47.84.215) by CO1EHSMHS017.bigfish.com (10.243.66.27) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 1 Sep 2012 13:54:21 +0000 Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.tripwire.com (Proprietary) with SMTP id 82BFD2321209 for ; Sat, 1 Sep 2012 06:51:55 -0700 (PDT) Received: from PDXED01.tripwire.com (unknown [192.168.192.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by zgw01.tripwire.com (Proprietary) with ESMTPS id E8C6223211F9 for ; Sat, 1 Sep 2012 06:51:54 -0700 (PDT) Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.379.0; Sat, 1 Sep 2012 06:56:48 -0700 Received: from PDXMB03.tripwire.com ([fe80::284f:fde0:d82f:4223]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0379.000; Sat, 1 Sep 2012 06:54:19 -0700 From: Adam Montville To: "mile@ietf.org" Thread-Topic: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWQ== Date: Sat, 1 Sep 2012 13:54:18 +0000 Message-ID: In-Reply-To: <20120901134631.30953.45877.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [172.30.0.234] x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f Content-Type: text/plain; charset="us-ascii" Content-ID: <7E529ECA4CB9904381501CD34E47924D@tripwire.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-VPM-MSG-ID: 2825eceb-cd18-4845-99bc-aef9857d1673 X-VPM-HOST: zgw01.tripwire.com X-VPM-ENC-REGIME: Plaintext X-VPM-CERT-FLAG: 0 X-VPM-IS-HYBRID: 0 X-OriginatorOrg: tripwire.com Subject: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 13:54:28 -0000 On 9/1/12 6:46 AM, "internet-drafts@ietf.org" wrote: > >A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >has been successfully submitted by Adam W. Montville and posted to the >IETF repository. > >Filename: draft-montville-mile-enum-reference-format >Revision: 00 >Title: IODEF Enumeration Reference Format >Creation date: 2012-09-01 >WG ID: Individual Submission >Number of pages: 6 >URL: =20 >http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-fo >rmat-00.txt >Status: =20 >http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-format >Htmlized: =20 >http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 > > >Abstract: > Some standards, such as the Incident Object Description Exchange > Format [IODEF], provide classes used to reference external entities > (such as enumeration identifiers). At the time of standardization, > however, needed references may not be known, and the method of > external entity identification is often left unstructured. This > document describes, using [IODEF] as an example, a method to provide > structure after the fact. > > > =20 > =20 > > >The IETF Secretariat > > > From kathleen.moriarty@emc.com Wed Sep 5 07:38:03 2012 Return-Path: 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 3E8FE21F846A for ; Wed, 5 Sep 2012 07:38:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ybbi+hkdVCr for ; Wed, 5 Sep 2012 07:38:02 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 972FA21F84C8 for ; Wed, 5 Sep 2012 07:38:01 -0700 (PDT) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q85EbxQl009746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Sep 2012 10:38:00 -0400 Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 5 Sep 2012 10:37:40 -0400 Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q85Ebci4024270; Wed, 5 Sep 2012 10:37:39 -0400 Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Wed, 5 Sep 2012 10:37:38 -0400 From: "Moriarty, Kathleen" To: Adam Montville , "mile@ietf.org" Date: Wed, 5 Sep 2012 10:35:57 -0400 Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1 Message-ID: References: <20120901134631.30953.45877.idtracker@ietfa.amsl.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2012 14:38:03 -0000 Adam, Thank you very much for your work on this draft! =20 MILE members: Please review and comment on the draft. =20 Thank you! Kathleen ________________________________________ From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam Montv= ille [amontville@tripwire.com] Sent: Saturday, September 01, 2012 9:54 AM To: mile@ietf.org Subject: [mile] FW: New Version Notification for draft-montville-mile-enum-= reference-format-00.txt On 9/1/12 6:46 AM, "internet-drafts@ietf.org" wrote: > >A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >has been successfully submitted by Adam W. Montville and posted to the >IETF repository. > >Filename: draft-montville-mile-enum-reference-format >Revision: 00 >Title: IODEF Enumeration Reference Format >Creation date: 2012-09-01 >WG ID: Individual Submission >Number of pages: 6 >URL: >http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-fo >rmat-00.txt >Status: >http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-format >Htmlized: >http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 > > >Abstract: > Some standards, such as the Incident Object Description Exchange > Format [IODEF], provide classes used to reference external entities > (such as enumeration identifiers). At the time of standardization, > however, needed references may not be known, and the method of > external entity identification is often left unstructured. This > document describes, using [IODEF] as an example, a method to provide > structure after the fact. > > > > > > >The IETF Secretariat > > > _______________________________________________ mile mailing list mile@ietf.org https://www.ietf.org/mailman/listinfo/mile From amontville@tripwire.com Thu Sep 6 06:54:39 2012 Return-Path: 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 1E24B21F8522 for ; Thu, 6 Sep 2012 06:54:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CkUGpGv1ei7 for ; Thu, 6 Sep 2012 06:54:38 -0700 (PDT) Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 5071021F851E for ; Thu, 6 Sep 2012 06:54:38 -0700 (PDT) Received: from mail61-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Thu, 6 Sep 2012 13:54:37 +0000 Received: from mail61-tx2 (localhost [127.0.0.1]) by mail61-tx2-R.bigfish.com (Postfix) with ESMTP id 568313800B2 for ; Thu, 6 Sep 2012 13:54:37 +0000 (UTC) X-Forefront-Antispam-Report: CIP:174.47.84.215; KIP:(null); UIP:(null); IPV:NLI; H:zgw01.tripwire.com; RD:174-47-84-215.static.twtelecom.net; EFVD:NLI X-SpamScore: -32 X-BigFish: VPS-32(zzbb2dI98dI9371I936eI1432I11f6N1415Izz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944he5bhf0ah107ah1220h1155h) Received: from mail61-tx2 (localhost.localdomain [127.0.0.1]) by mail61-tx2 (MessageSwitch) id 134693967522033_9754; Thu, 6 Sep 2012 13:54:35 +0000 (UTC) Received: from TX2EHSMHS042.bigfish.com (unknown [10.9.14.253]) by mail61-tx2.bigfish.com (Postfix) with ESMTP id ED35C4C0049 for ; Thu, 6 Sep 2012 13:54:34 +0000 (UTC) Received: from zgw01.tripwire.com (174.47.84.215) by TX2EHSMHS042.bigfish.com (10.9.99.142) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 6 Sep 2012 13:54:33 +0000 Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.tripwire.com (Proprietary) with SMTP id 9EA9323211DB for ; Thu, 6 Sep 2012 06:51:27 -0700 (PDT) Received: from PDXED01.tripwire.com (unknown [192.168.192.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by zgw01.tripwire.com (Proprietary) with ESMTPS id 0C55823211D3; Thu, 6 Sep 2012 06:51:27 -0700 (PDT) Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.379.0; Thu, 6 Sep 2012 06:56:53 -0700 Received: from PDXMB03.tripwire.com ([fe80::284f:fde0:d82f:4223]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0379.000; Thu, 6 Sep 2012 06:54:31 -0700 From: Adam Montville To: "Moriarty, Kathleen" , "mile@ietf.org" Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gAGGw4A= Date: Thu, 6 Sep 2012 13:54:30 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.3.120616 x-originating-ip: [172.30.0.234] x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-VPM-MSG-ID: c5f7891d-4d78-4ce9-94c2-7d0506946cc7 X-VPM-HOST: zgw01.tripwire.com X-VPM-ENC-REGIME: Plaintext X-VPM-CERT-FLAG: 0 X-VPM-IS-HYBRID: 0 X-OriginatorOrg: tripwire.com Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2012 13:54:39 -0000 On 9/5/12 7:35 AM, "Moriarty, Kathleen" wrote: >Adam, > >Thank you very much for your work on this draft! You're welcome, Kathleen! > >MILE members: Please review and comment on the draft. I already have at least one improvement in the security considerations section. I need to add information relative to protective measures to take such that references are not tampered with in transit, at least. I look forward to the community's comments. > >Thank you! >Kathleen >________________________________________ >From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam >Montville [amontville@tripwire.com] >Sent: Saturday, September 01, 2012 9:54 AM >To: mile@ietf.org >Subject: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >On 9/1/12 6:46 AM, "internet-drafts@ietf.org" >wrote: > >> >>A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >>has been successfully submitted by Adam W. Montville and posted to the >>IETF repository. >> >>Filename: draft-montville-mile-enum-reference-format >>Revision: 00 >>Title: IODEF Enumeration Reference Format >>Creation date: 2012-09-01 >>WG ID: Individual Submission >>Number of pages: 6 >>URL: >>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-f >>o >>rmat-00.txt >>Status: >>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-forma >>t >>Htmlized: >>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 >> >> >>Abstract: >> Some standards, such as the Incident Object Description Exchange >> Format [IODEF], provide classes used to reference external entities >> (such as enumeration identifiers). At the time of standardization, >> however, needed references may not be known, and the method of >> external entity identification is often left unstructured. This >> document describes, using [IODEF] as an example, a method to provide >> structure after the fact. >> >> >> >> >> >> >>The IETF Secretariat >> >> >> > > > > >_______________________________________________ >mile mailing list >mile@ietf.org >https://www.ietf.org/mailman/listinfo/mile > > > From johnp.field@emc.com Thu Sep 6 07:53:29 2012 Return-Path: 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 735D921F869F for ; Thu, 6 Sep 2012 07:53:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIOPmpIFFKiQ for ; Thu, 6 Sep 2012 07:53:29 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E068721F866E for ; Thu, 6 Sep 2012 07:53:28 -0700 (PDT) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q86ErOqi023366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Sep 2012 10:53:26 -0400 Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for ; Thu, 6 Sep 2012 10:53:13 -0400 Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q86Er8Jm005457 for ; Thu, 6 Sep 2012 10:53:13 -0400 Received: from mx14a.corp.emc.com ([169.254.1.151]) by mxhub35.corp.emc.com ([::1]) with mapi; Thu, 6 Sep 2012 10:52:39 -0400 From: "Field, John" To: "" Date: Thu, 6 Sep 2012 10:52:38 -0400 Thread-Topic: New draft for review and comment: draft-field-mile-rolie-00.txt Thread-Index: Ac2L0435yvJAa7AZSl2Jmq3LdSAuWgAaFVGw Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: [mile] New draft for review and comment: draft-field-mile-rolie-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2012 14:53:29 -0000 QWxsLA0KDQpQbGVhc2Ugbm90ZSB0aGF0IEkgaGF2ZSBqdXN0IHBvc3RlZCBhIG5ldyBkcmFmdCBm b3IgcmV2aWV3IGFuZCBjb21tZW50LiAgQXMgc3RhdGVkIGluIHRoZSBhYnN0cmFjdCwgdGhlIGRy YWZ0IGRlc2NyaWJlcyBhIFJFU1RmdWwgSFRUUCBiaW5kaW5nIGZvciBzaGFyaW5nIGluY2lkZW50 LCBpbmRpY2F0b3IsIGFuZCBvdGhlciBjeWJlciBzZWN1cml0eS1yZWxhdGVkIGluZm9ybWF0aW9u LiAgSSBob3BlIHlvdSdsbCBmaW5kIHRoaXMgZG9jdW1lbnQgdG8gYmUgb2YgaW50ZXJlc3QsIGFu ZCBJIGxvb2sgZm9yd2FyZCB0byBkaXNjdXNzaW5nIGFueSBxdWVzdGlvbnMgYW5kL29yIGNvbW1l bnRzIHRoYXQgdGhlIGdyb3VwIG1heSBoYXZlLg0KDQpSZWdhcmRzLA0KSm9obg0KDQovLyBKb2hu IFAuIEZpZWxkIA0KLy8gU2VjdXJpdHkgQXJjaGl0ZWN0IA0KLy8gRU1DIE9mZmljZSBvZiB0aGUg Q1RPIA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFm dHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogV2Vk bmVzZGF5LCBTZXB0ZW1iZXIgMDUsIDIwMTIgOTo1OSBQTQ0KVG86IEZpZWxkLCBKb2huDQpTdWJq ZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWZpZWxkLW1pbGUtcm9saWUt MDAudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWZpZWxkLW1pbGUtcm9saWUt MDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEpvaG4gUC4gRmllbGQg YW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1m aWVsZC1taWxlLXJvbGllDQpSZXZpc2lvbjoJIDAwDQpUaXRsZToJCSBSZXNvdXJjZS1PcmllbnRl ZCBMaWdodHdlaWdodCBJbmRpY2F0b3IgRXhjaGFuZ2UNCkNyZWF0aW9uIGRhdGU6CSAyMDEyLTA5 LTA1DQpXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogNDEN ClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh ZnQtZmllbGQtbWlsZS1yb2xpZS0wMC50eHQNClN0YXR1czogICAgICAgICAgaHR0cDovL2RhdGF0 cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1maWVsZC1taWxlLXJvbGllDQpIdG1saXplZDogICAg ICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWZpZWxkLW1pbGUtcm9saWUtMDAN Cg0KDQpBYnN0cmFjdDoNCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhIHJlc291cmNlLW9yaWVu dGVkIGFwcHJvYWNoIHRvIGN5YmVyIHNlY3VyaXR5DQogICBpbmZvcm1hdGlvbiBzaGFyaW5nLiAg VXNpbmcgdGhpcyBhcHByb2FjaCwgYSBDU0lSVCBvciBvdGhlcg0KICAgc3Rha2Vob2xkZXIgbWF5 IHNoYXJlIGFuZCBleGNoYW5nZSByZXByZXNlbnRhdGlvbnMgb2YgY3liZXIgc2VjdXJpdHkNCiAg IGluY2lkZW50cywgaW5kaWNhdG9ycywgYW5kIG90aGVyIHJlbGF0ZWQgaW5mb3JtYXRpb24gYXMg V2ViLQ0KICAgYWRkcmVzc2FibGUgcmVzb3VyY2VzLiAgVGhlIHRyYW5zcG9ydCBwcm90b2NvbCBi aW5kaW5nIGlzIHNwZWNpZmllZA0KICAgYXMgSFRUUChTKSB3aXRoIGEgTUlNRSBtZWRpYSB0eXBl IG9mIEF0b20rWE1MLiAgQW4gYXBwcm9wcmlhdGUgc2V0IG9mDQogICBsaW5rIHJlbGF0aW9uIHR5 cGVzIHNwZWNpZmljIHRvIGN5YmVyIHNlY3VyaXR5IGluZm9ybWF0aW9uIHNoYXJpbmcgaXMNCiAg IGRlZmluZWQuICBUaGUgcmVzb3VyY2UgcmVwcmVzZW50YXRpb25zIGxldmVyYWdlIHRoZSBleGlz dGluZyBJT0RFRg0KICAgW1JGQzUwNzBdIGFuZCBSSUQgW1JGQzY1NDVdIHNwZWNpZmljYXRpb25z IGFzIGFwcHJvcHJpYXRlLg0KICAgQ29leGlzdGVuY2Ugd2l0aCBkZXBsb3ltZW50cyB0aGF0IGNv bmZvcm0gdG8gZXhpc3Rpbmcgc3BlY2lmaWNhdGlvbnMNCiAgIGluY2x1ZGluZyBSSUQgW1JGQzY1 NDVdIGFuZCBUcmFuc3BvcnQgb2YgUmVhbC10aW1lIEludGVyLW5ldHdvcmsNCiAgIERlZmVuc2Ug KFJJRCkgTWVzc2FnZXMgb3ZlciBIVFRQL1RMUyBbUkZDNjU0Nl0gaXMgc3VwcG9ydGVkIHZpYQ0K ICAgYXBwcm9wcmlhdGUgdXNlIG9mIEhUVFAgc3RhdHVzIGNvZGVzLg0KDQogICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQo= From lnunez@c3isecurity.com Thu Sep 6 08:36:32 2012 Return-Path: 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 BC10521F8726 for ; Thu, 6 Sep 2012 08:36:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzFsGt6UYNIJ for ; Thu, 6 Sep 2012 08:36:31 -0700 (PDT) Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C19A121F86F9 for ; Thu, 6 Sep 2012 08:36:31 -0700 (PDT) Received: by ggnh4 with SMTP id h4so326133ggn.31 for ; Thu, 06 Sep 2012 08:36:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=euOO+15EX0mwU1wRvT4S+DJNuQ2exV9g9uJUSputhhg=; b=Cy2+MgBVW62YJGQQv14/puzDmZaW2bq4BdIa7KGTLYoeYqj1OZnaU1h+326cvC4jmc 9B7lpXrpWDaaLVL39lzQfIMG547L+l+wZ0kIUqgoHT1H7A9WOXd/MOpRYG0H3oQdQfvk k/zCPs0PoRvwMnpp54oYbWDacXG5Bh/PA7PRjWldK3Vv30sOxAhrj80UWTwyPb47UF9E wQ26UznW9l0QUAcj+IGmlqi0DpvmOuceYswozMCTvMvPHyJeuIHivLZnxgQvXfez/OhG MlAIms4ktC9cDIiZrqYwn/XVfz8SenuKBbq4AhXX+vU39/SsLvCZxZA5PbLSdz32OP4f LY1A== Received: by 10.236.197.5 with SMTP id s5mr2107493yhn.114.1346945791200; Thu, 06 Sep 2012 08:36:31 -0700 (PDT) Received: from [192.168.1.25] (cpe-066-057-081-254.nc.res.rr.com. [66.57.81.254]) by mx.google.com with ESMTPS id d66sm4335731yhe.1.2012.09.06.08.36.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 06 Sep 2012 08:36:27 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Luis Nunez In-Reply-To: Date: Thu, 6 Sep 2012 11:36:25 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Field, John" X-Mailer: Apple Mail (2.1278) X-Gm-Message-State: ALoCoQmlGwQ8qdzOZ4pdr8CYHC0iOQLCpShC19eFdXMIfirPQVD1TzmTnv+kfC9Rokndr/Xhuxrj Cc: mile@ietf.org, sacm@ietf.org Subject: Re: [mile] [sacm] New draft for review and comment: draft-field-mile-rolie-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2012 15:36:32 -0000 John, this definitely is of interest and could be related to past discussions = around content repositories. =20 I know of two publicly accessible (REST) repositories that could = potential host this type of content. http://scaprepo.com/SCAPRepoWebService http://scapsync.com/api/ NIST is also working on a repository with webservices. It would be interesting to prototype a sample document and flesh out = issues. -ln On Sep 6, 2012, at 11:10 AM, Field, John wrote: > All, >=20 > Cross posting this announcement from MILE to SACM, as I think this may = be of interest within the SCAP community as well. =20 >=20 > The new draft referenced below describes a RESTful HTTP binding for = sharing incident, indicator, and other cyber security-related = information. In particular, the draft includes a suggested approach to = retrieving a related benchmark resource. =20 >=20 > I hope you'll find this draft to be of interest. =20 >=20 > Please post any questions or comments to the MILE list. >=20 > Regards, > John >=20 > // John P. Field=20 > // Security Architect=20 > // EMC Office of the CTO=20 >=20 >=20 >=20 >=20 >=20 > -----Original Message----- > From: Field, John=20 > Sent: Thursday, September 06, 2012 10:53 AM > To: > Subject: New draft for review and comment: = draft-field-mile-rolie-00.txt >=20 > All, >=20 > Please note that I have just posted a new draft for review and = comment. As stated in the abstract, the draft describes a RESTful HTTP = binding for sharing incident, indicator, and other cyber = security-related information. I hope you'll find this document to be of = interest, and I look forward to discussing any questions and/or comments = that the group may have. >=20 > Regards, > John >=20 > // John P. Field=20 > // Security Architect=20 > // EMC Office of the CTO=20 >=20 >=20 > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20 > Sent: Wednesday, September 05, 2012 9:59 PM > To: Field, John > Subject: New Version Notification for draft-field-mile-rolie-00.txt >=20 >=20 > A new version of I-D, draft-field-mile-rolie-00.txt > has been successfully submitted by John P. Field and posted to the > IETF repository. >=20 > Filename: draft-field-mile-rolie > Revision: 00 > Title: Resource-Oriented Lightweight Indicator = Exchange > Creation date: 2012-09-05 > WG ID: Individual Submission > Number of pages: 41 > URL: = http://www.ietf.org/internet-drafts/draft-field-mile-rolie-00.txt > Status: = http://datatracker.ietf.org/doc/draft-field-mile-rolie > Htmlized: http://tools.ietf.org/html/draft-field-mile-rolie-00 >=20 >=20 > Abstract: > This document defines a resource-oriented approach to cyber security > information sharing. Using this approach, a CSIRT or other > stakeholder may share and exchange representations of cyber security > incidents, indicators, and other related information as Web- > addressable resources. The transport protocol binding is specified > as HTTP(S) with a MIME media type of Atom+XML. An appropriate set = of > link relation types specific to cyber security information sharing = is > defined. The resource representations leverage the existing IODEF > [RFC5070] and RID [RFC6545] specifications as appropriate. > Coexistence with deployments that conform to existing specifications > including RID [RFC6545] and Transport of Real-time Inter-network > Defense (RID) Messages over HTTP/TLS [RFC6546] is supported via > appropriate use of HTTP status codes. >=20 >=20 >=20 >=20 > The IETF Secretariat >=20 >=20 > _______________________________________________ > sacm mailing list > sacm@ietf.org > https://www.ietf.org/mailman/listinfo/sacm From kathleen.moriarty@emc.com Tue Sep 11 07:23:07 2012 Return-Path: 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 6A20B21F861A for ; Tue, 11 Sep 2012 07:23:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cT+X6gs800AG for ; Tue, 11 Sep 2012 07:23:04 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id AAA9521F8639 for ; Tue, 11 Sep 2012 07:23:03 -0700 (PDT) Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8BEN2aA004676 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Sep 2012 10:23:02 -0400 Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for ; Tue, 11 Sep 2012 10:22:51 -0400 Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8BEMoC2018632 for ; Tue, 11 Sep 2012 10:22:51 -0400 Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub35.corp.emc.com ([::1]) with mapi; Tue, 11 Sep 2012 10:22:50 -0400 From: "Moriarty, Kathleen" To: "mile@ietf.org" Date: Tue, 11 Sep 2012 10:22:48 -0400 Thread-Topic: SCI document and WG decision Thread-Index: Ac1+2VlhBTQIdwl7SaqzSzRvyN6ZRAAHwZEQBEt6WKA= Message-ID: References: <1C9F17D1873AFA47A969C4DD98F98A75057C6A@xmb-rcd-x10.cisco.com> In-Reply-To: <1C9F17D1873AFA47A969C4DD98F98A75057C6A@xmb-rcd-x10.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F2409291CF7MX15Acorpemccom_" MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [mile] SCI document and WG decision X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 14:23:07 -0000 --_000_F5063677821E3B4F81ACFB7905573F2409291CF7MX15Acorpemccom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, The list is in agreement with the decision from the IETF meeting in Vancouv= er and this message ends the call for opinions. This means that we as a group have some work to do. We will start with the= SCI draft not having any included schemas, then decide what are the needed= schemas to incorporate in the draft prior to WGLC and publication. The SC= I draft does create IANA tables where additional schemas can be added to th= e SCI method of extending IODEF. The SCI draft will incorporate developed schemas (not extensions specific t= o IODEF as those can be drafts on their own) that add value by enabling the= IODEF schema to be extended and creating relationships to these schema sta= ndards. The format Take chose in the SCI draft categorizes schemas to crea= te those relationships and creates patterns for the schemas to be added. I think the most useful approach here would be to have use case driven disc= ussions. We need at least ONE schema to be agreed upon for the entire draft to meet = the IETF definition and purpose for having a Mandatory To Implement (MTI) s= chema for the SCI draft. One MTI is beneficial for vendors to be able to c= laim interoperability, but not necessarily to require full support for all = the schemas in the eventual tables as the vendors may be supporting differe= nt use cases and we do not want to make it too hard to implement as that co= uld delay implementations or stop them altogether. Let's not get into the MTI discussion yet, but discuss schemas that are nee= ded to compliment IODEF is a standard way to enable business use cases to b= e met. I'll start a new thread asking for use case driven examples and the schemas= that best fit those use cases. Thank you, Kathleen From: Panos Kampanakis (pkampana) [mailto:pkampana@cisco.com] Sent: Monday, August 20, 2012 1:24 PM To: Moriarty, Kathleen; mile@ietf.org Subject: RE: SCI document and WG decision +1 Panos From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mor= iarty, Kathleen Sent: Monday, August 20, 2012 9:40 AM To: mile@ietf.org Subject: [mile] SCI document and WG decision Hello, At the IETF meeting in Vancouver, the WG consensus was to remove the refere= nced specifications from the SCI draft so that the document could progress = without IP issues. In this model, the draft would have empty tables and th= e WG would then decide which specifications or standards references would g= et added into the document. The thought was that the WG could think more c= arefully about what specifications were important to reference to meet rele= vant use cases for the community. The process would include a review of th= e specification to ensure we could reference it, including that the specifi= cation or standard is a document that the IETF can normatively reference. Does the WG agree on this approach? (consensus needs to be shown on the li= st in one direction or another to formalize and move forward). We will give this a two week period for responses, finishing the morning of= September 3rd. Thank you in advance! Kathleen --_000_F5063677821E3B4F81ACFB7905573F2409291CF7MX15Acorpemccom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

=

The list is in agreement with the decision from= the IETF meeting in Vancouver and this message ends the call for opinions.=  

 <= /span>

This means that we as a group have so= me work to do.  We will start with the SCI draft not having any includ= ed schemas, then decide what are the needed schemas to incorporate in the d= raft prior to WGLC and publication.  The SCI draft does create IANA ta= bles where additional schemas can be added to the SCI method of extending I= ODEF.

 

The SCI draft will incorporate develope= d schemas (not extensions specific to IODEF as those can be drafts on their= own) that add value by enabling the IODEF schema to be extended and creati= ng relationships to these schema standards.  The format Take chose in = the SCI draft categorizes schemas to create those relationships and creates= patterns for the schemas to be added.

 

I th= ink the most useful approach here would be to have use case driven discussi= ons. 

 

We need at least ONE schema to be= agreed upon for the entire draft to meet the IETF definition and purpose f= or having a Mandatory To Implement (MTI) schema for the SCI draft.  On= e MTI is beneficial for vendors to be able to claim interoperability, but n= ot necessarily to require full support for all the schemas in the eventual = tables as the vendors may be supporting different use cases and we do not w= ant to make it too hard to implement as that could delay implementations or= stop them altogether.

 

Let’s not get in= to the MTI discussion yet, but discuss schemas that are needed to complimen= t IODEF is a standard way to enable business use cases to be met.

 

I’ll start a new thread asking for use case driv= en examples and the schemas that best fit those use cases.

 

Thank you,

K= athleen

 <= /span>

 

 

From: Panos Kampanakis (pkampana) [mailto:pkampana@cisco.com]
= Sent: Monday, August 20, 2012 1:24 PM
To: Moriarty, Kathleen;= mile@ietf.org
Subject: RE: SCI document and WG decision

 

+1

Pan= os

 

 

=

From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.or= g] On Behalf Of Moriarty, Kathleen
Sent: Monday, August 20= , 2012 9:40 AM
To: mile@ietf.org
Subject: [mile] SCI do= cument and WG decision

 

Hello,

 

At= the IETF meeting in Vancouver, the WG consensus was to remove the referenc= ed specifications from the SCI draft so that the document could progress wi= thout IP issues.  In this model, the draft would have empty tables and= the WG would then decide which specifications or standards references woul= d get added into the document.  The thought was that the WG could thin= k more carefully about what specifications were important to reference to m= eet relevant use cases for the community.  The process would include a= review of the specification to ensure we could reference it, including tha= t the specification or standard is a document that the IETF can normatively= reference.

 =

Does the WG agree on this approach?&nbs= p; (consensus needs to be shown on the list in one direction or another to = formalize and move forward).

=  

We will give this a tw= o week period for responses, finishing the morning of September 3rd.

 <= /p>

Thank you in advance!  <= /p>

Kathleen

 

 

= --_000_F5063677821E3B4F81ACFB7905573F2409291CF7MX15Acorpemccom_-- From kathleen.moriarty@emc.com Tue Sep 11 07:23:57 2012 Return-Path: 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 8C1EB21F87AA for ; Tue, 11 Sep 2012 07:23:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57BJYDOL2otU for ; Tue, 11 Sep 2012 07:23:57 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6153921F87F7 for ; Tue, 11 Sep 2012 07:23:50 -0700 (PDT) Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8BENl5l028876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Sep 2012 10:23:48 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for ; Tue, 11 Sep 2012 10:23:30 -0400 Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8BENTFP001265 for ; Tue, 11 Sep 2012 10:23:30 -0400 Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Tue, 11 Sep 2012 10:23:29 -0400 From: "Moriarty, Kathleen" To: "mile@ietf.org" Date: Tue, 11 Sep 2012 10:23:28 -0400 Thread-Topic: Call for Use Cases discussions to determine Schemas for the SCI draft Thread-Index: Ac2QKQNf8l27Go8UT9KJxQQgRUOe6g== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F2409291CF9MX15Acorpemccom_" MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: [mile] Call for Use Cases discussions to determine Schemas for the SCI draft X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 14:23:57 -0000 --_000_F5063677821E3B4F81ACFB7905573F2409291CF9MX15Acorpemccom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, As mentioned in my previous message to the list, the WG needs to drive what= schemas should be included in the SCI draft. These should be use case dri= ven, where the use case would be tied to specific schemas that fill those u= se cases. This will help us as a group decide what schemas are needed in t= he base SCI draft. Schemas may be added after publication via the IANA tab= les. PLEASE voice your opinions and discuss use cases relevant to your organizat= ion or customers to guide the work. The IETF is a transparent process wher= e your opinion matters, so please contribute to the list discussions. Thank you! Kathleen --_000_F5063677821E3B4F81ACFB7905573F2409291CF9MX15Acorpemccom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello,
 
As mentioned in my previous message to the list, the WG needs to drive= what schemas should be included in the SCI draft.  These should be us= e case driven, where the use case would be tied to specific schemas that fi= ll those use cases.  This will help us as a group decide what schemas are needed in the base SCI draft.  Sche= mas may be added after publication via the IANA tables.
 
PLEASE voice your opinions and discuss use cases relevant to your orga= nization or customers to guide the work.  The IETF is a transparent pr= ocess where your opinion matters, so please contribute to the list discussi= ons.
 
Thank you!
Kathleen
 
 --_000_F5063677821E3B4F81ACFB7905573F2409291CF9MX15Acorpemccom_-- From john.banghart@nist.gov Mon Sep 24 11:01:52 2012 Return-Path: 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 4E06621F8803; Mon, 24 Sep 2012 11:01:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.846 X-Spam-Level: X-Spam-Status: No, score=-4.846 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lr-AeYYt+RoY; Mon, 24 Sep 2012 11:01:51 -0700 (PDT) Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id E470621F87FE; Mon, 24 Sep 2012 11:01:50 -0700 (PDT) Received: from WSXGHUB1.xchange.nist.gov (129.6.18.96) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.379.0; Mon, 24 Sep 2012 14:01:39 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB1.xchange.nist.gov ([129.6.18.96]) with mapi; Mon, 24 Sep 2012 14:01:49 -0400 From: "Banghart, John" To: "sacm@ietf.org" , "mile@ietf.org" Date: Mon, 24 Sep 2012 14:01:45 -0400 Thread-Topic: Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2afm7Z7K4Rsa/6QIqh6G/YPMl5VA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CC8618484F76johnbanghartnistgov_" MIME-Version: 1.0 Subject: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 18:01:52 -0000 --_000_CC8618484F76johnbanghartnistgov_ Content-Type: text/plain; charset="us-ascii" Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards. The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts. Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend. Participants are encouraged to share their use cases and requirements for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the room number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov --_000_CC8618484F76johnbanghartnistgov_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13 ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1z cGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAxNHB4OyBmb250LWZhbWlseTog Q2FsaWJyaSwgc2Fucy1zZXJpZjsgIj48ZGl2PjxkaXY+SGVsbG8gYWxsLDwvZGl2PjxkaXY+PGJy PjwvZGl2PjxkaXY+VGhlcmUgd2lsbCBiZSBhIGJpcmRzLW9mLWEtZmVhdGhlciAoQm9GKSBzZXNz aW9uIGF0IHRoZSB1cGNvbWluZyBJVCBTZWN1cml0eSBBdXRvbWF0aW9uIENvbmZlcmVuY2UgKElU U0FDKSBpbiBCYWx0aW1vcmUgb24gV2VkbmVzZGF5LCBPY3RvYmVyIDR0aCwgZnJvbSA1OjMwcG0g dG8gNjozMHBtLCBmb2N1c2luZyBvbiBpbnRlcm5hdGlvbmFsIGVmZm9ydHMgdG8gZGV2ZWxvcCBz ZWN1cml0eSBhdXRvbWF0aW9uIHN0YW5kYXJkcy4gJm5ic3A7VGhlIEJvRiB3aWxsIGZvY3VzIG9u IHJldmlld2luZyBjdXJyZW50IGVmZm9ydHMgdG8gc3RhbmRhcmRpemUgc2VjdXJpdHkgYXV0b21h dGlvbiBjYXBhYmlsaXRpZXMgYW5kIGhvdyB0byBlbmdhZ2UgaW4gdGhlc2UgZWZmb3J0cy4gJm5i c3A7QW55b25lIGFjdGl2ZWx5IG9yIGludGVyZXN0ZWQgaW4gcGFydGljaXBhdGluZyBpbiBvciB1 c2luZyBzdGFuZGFyZHMgZGV2ZWxvcGVkIGJ5IGludGVybmF0aW9uYWwgc3RhbmRhcmRzIGRldmVs b3BtZW50IG9yZ2FuaXphdGlvbnMgKFNET3MpIHNob3VsZCBhdHRlbmQuICZuYnNwO1BhcnRpY2lw YW50cyBhcmUgZW5jb3VyYWdlZCB0byBzaGFyZSB0aGVpciB1c2UgY2FzZXMgYW5kIHJlcXVpcmVt ZW50cyBmb3Igc2VjdXJpdHkgYXV0b21hdGlvbiBzdGFuZGFyZHMuPC9kaXY+PGRpdj4mbmJzcDs8 L2Rpdj48ZGl2PkZvciBtb3JlIGluZm9ybWF0aW9uIG9uIHRoZSBJVFNBQywgcGxlYXNlIHZpc2l0 OiBodHRwczovL2l0c2FjLmcycGxhbmV0LmNvbS9pdHNhYzIwMTIuICZuYnNwOzwvZGl2PjxkaXY+ PGJyPjwvZGl2PjxkaXY+UGxlYXNlIG5vdGUgdGhhdCByZW1vdGUgYWNjZXNzIGNhcGFiaWxpdGll cyB3aWxsIG5vdCBiZSBwb3NzaWJsZS48L2Rpdj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pklm IHRoZXJlIGlzIHN1ZmZpY2llbnQgaW50ZXJlc3QsIEkgd2lsbCBwcm92aWRlIGFkZGl0aW9uYWwg ZGV0YWlscyBvbiB0aGUgcm9vbSBudW1iZXIgYW5kIG90aGVyIGxvZ2lzdGljcy48L2Rpdj48ZGl2 Pjxicj48L2Rpdj48ZGl2PlRoYW5rIHlvdS48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pi1Kb2hu PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48ZGl2PjxkaXY+LS08L2Rpdj48ZGl2PkpvaG4gQmFu Z2hhcnQ8L2Rpdj48ZGl2PlByb2dyYW0gQW5hbHlzdDwvZGl2PjxkaXY+UHJvZ3JhbSBDb29yZGlu YXRpb24gT2ZmaWNlPC9kaXY+PGRpdj5PZmZpY2Ugb2YgdGhlIFVuZGVyIFNlY3JldGFyeSBvZiBD b21tZXJjZSBmb3IgU3RhbmRhcmRzIGFuZCBUZWNobm9sb2d5PC9kaXY+PGRpdj5OYXRpb25hbCBJ bnN0aXR1dGUgb2YgU3RhbmRhcmRzIGFuZCBUZWNobm9sb2d5PC9kaXY+PGRpdj48YnI+PC9kaXY+ PGRpdj4oMzAxKSA5NzUtODA4NTwvZGl2PjxkaXY+Sm9obi5iYW5naGFydEBuaXN0LmdvdjwvZGl2 PjwvZGl2PjwvZGl2PjwvYm9keT48L2h0bWw+DQo= --_000_CC8618484F76johnbanghartnistgov_-- From tony@yaanatech.com Mon Sep 24 11:33:27 2012 Return-Path: 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 ACFBB21F8683; Mon, 24 Sep 2012 11:33:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqGApxXRmZoz; Mon, 24 Sep 2012 11:33:27 -0700 (PDT) Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2922621F8686; Mon, 24 Sep 2012 11:33:26 -0700 (PDT) Received: from [192.168.0.4] (pool-96-247-209-46.clppva.fios.verizon.net [96.247.209.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id E22D058081; Mon, 24 Sep 2012 18:33:25 +0000 (UTC) Message-ID: <5060A774.1040605@yaanatech.com> Date: Mon, 24 Sep 2012 14:33:24 -0400 From: Tony Rutkowski Organization: Yaana Technologies User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20120905 Thunderbird/16.0 MIME-Version: 1.0 To: "Banghart, John" References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------060604050302080306090008" Cc: "mile@ietf.org" , "sacm@ietf.org" Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: tony@yaanatech.com List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 18:33:27 -0000 This is a multi-part message in MIME format. --------------060604050302080306090008 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi John, How are going to provide notice of the room to those of us there? --tony On 9/24/2012 2:01 PM, Banghart, John wrote: > Hello all, > > There will be a birds-of-a-feather (BoF) session at the upcoming IT > Security Automation Conference (ITSAC) in Baltimore on Wednesday, > October 4th, from 5:30pm to 6:30pm, focusing on international efforts > to develop security automation standards. The BoF will focus on > reviewing current efforts to standardize security automation > capabilities and how to engage in these efforts. Anyone actively or > interested in participating in or using standards developed by > international standards development organizations (SDOs) should > attend. Participants are encouraged to share their use cases and > requirements for security automation standards. > For more information on the ITSAC, please visit: > https://itsac.g2planet.com/itsac2012. > > Please note that remote access capabilities will not be possible. > > If there is sufficient interest, I will provide additional details on > the room number and other logistics. > > Thank you. > > -John > > -- > John Banghart > Program Analyst > Program Coordination Office > Office of the Under Secretary of Commerce for Standards and Technology > National Institute of Standards and Technology > > (301) 975-8085 > John.banghart@nist.gov > > > _______________________________________________ > mile mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile --------------060604050302080306090008 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi John,

How are going to provide notice of the room
to those of us there?

--tony

On 9/24/2012 2:01 PM, Banghart, John wrote:
Hello all,

There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards.  The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts.  Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend.  Participants are encouraged to share their use cases and requirements for security automation standards.
 
For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012.  

Please note that remote access capabilities will not be possible.

If there is sufficient interest, I will provide additional details on the room number and other logistics.

Thank you.

-John

--
John Banghart
Program Analyst
Program Coordination Office
Office of the Under Secretary of Commerce for Standards and Technology
National Institute of Standards and Technology

(301) 975-8085


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

--------------060604050302080306090008-- From john.banghart@nist.gov Mon Sep 24 11:47:57 2012 Return-Path: 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 DD56821F884D; Mon, 24 Sep 2012 11:47:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.845 X-Spam-Level: X-Spam-Status: No, score=-4.845 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yCZSf-uFQYZE; Mon, 24 Sep 2012 11:47:57 -0700 (PDT) Received: from wsget1.nist.gov (wsget1.nist.gov [129.6.13.150]) by ietfa.amsl.com (Postfix) with ESMTP id CE49821F888F; Mon, 24 Sep 2012 11:47:56 -0700 (PDT) Received: from WSXGHUB1.xchange.nist.gov (129.6.18.96) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.1.379.0; Mon, 24 Sep 2012 14:47:42 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB1.xchange.nist.gov ([129.6.18.96]) with mapi; Mon, 24 Sep 2012 14:47:55 -0400 From: "Banghart, John" To: "tony@yaanatech.com" Date: Mon, 24 Sep 2012 14:47:52 -0400 Thread-Topic: [mile] Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2ahN+1/dYx5YsvQxO6kHqP9MVPYQ== Message-ID: In-Reply-To: <5060A774.1040605@yaanatech.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CC8622F34F8Fjohnbanghartnistgov_" MIME-Version: 1.0 Cc: "mile@ietf.org" , "sacm@ietf.org" Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 18:47:58 -0000 --_000_CC8622F34F8Fjohnbanghartnistgov_ Content-Type: text/plain; charset="us-ascii" Tony, Great question. Once we are confirmed, there will be a notice board in the registration area indicating what sessions are taking place in what room. -John From: Tony Rutkowski > Organization: Yaana Technologies Reply-To: "tony@yaanatech.com" > Date: Monday, September 24, 2012 2:33 PM To: "Banghart, John" > Cc: "sacm@ietf.org" >, "mile@ietf.org" > Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Hi John, How are going to provide notice of the room to those of us there? --tony On 9/24/2012 2:01 PM, Banghart, John wrote: Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards. The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts. Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend. Participants are encouraged to share their use cases and requirements for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the room number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov _______________________________________________ mile mailing list mile@ietf.orghttps://www.ietf.org/mailman/listinfo/mile --_000_CC8622F34F8Fjohnbanghartnistgov_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13 ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1z cGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAxNHB4OyBmb250LWZhbWlseTog Q2FsaWJyaSwgc2Fucy1zZXJpZjsgIj48ZGl2PlRvbnksPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRp dj5HcmVhdCBxdWVzdGlvbi48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pk9uY2Ugd2UgYXJlIGNv bmZpcm1lZCwgdGhlcmUgd2lsbCBiZSBhIG5vdGljZSBib2FyZCBpbiB0aGUgcmVnaXN0cmF0aW9u IGFyZWEgaW5kaWNhdGluZyB3aGF0IHNlc3Npb25zIGFyZSB0YWtpbmcgcGxhY2UgaW4gd2hhdCBy b29tLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+LUpvaG48L2Rpdj48ZGl2Pjxicj48L2Rpdj48 c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNh bGlicmk7IGZvbnQtc2l6ZToxMXB0OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9yOmJsYWNrOyBCT1JE RVItQk9UVE9NOiBtZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5H LUJPVFRPTTogMGluOyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBCT1JE RVItVE9QOiAjYjVjNGRmIDFwdCBzb2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFE RElORy1UT1A6IDNwdCI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkZyb206IDwvc3Bh bj4gVG9ueSBSdXRrb3dza2kgJmx0OzxhIGhyZWY9Im1haWx0bzp0b255QHlhYW5hdGVjaC5jb20i PnRvbnlAeWFhbmF0ZWNoLmNvbTwvYT4mZ3Q7PGJyPjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpi b2xkIj5Pcmdhbml6YXRpb246IDwvc3Bhbj4gWWFhbmEgVGVjaG5vbG9naWVzPGJyPjxzcGFuIHN0 eWxlPSJmb250LXdlaWdodDpib2xkIj5SZXBseS1UbzogPC9zcGFuPiAiPGEgaHJlZj0ibWFpbHRv OnRvbnlAeWFhbmF0ZWNoLmNvbSI+dG9ueUB5YWFuYXRlY2guY29tPC9hPiIgJmx0OzxhIGhyZWY9 Im1haWx0bzp0b255QHlhYW5hdGVjaC5jb20iPnRvbnlAeWFhbmF0ZWNoLmNvbTwvYT4mZ3Q7PGJy PjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+IE1vbmRheSwgU2Vw dGVtYmVyIDI0LCAyMDEyIDI6MzMgUE08YnI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi PlRvOiA8L3NwYW4+ICJCYW5naGFydCwgSm9obiIgJmx0OzxhIGhyZWY9Im1haWx0bzpqb2huLmJh bmdoYXJ0QG5pc3QuZ292Ij5qb2huLmJhbmdoYXJ0QG5pc3QuZ292PC9hPiZndDs8YnI+PHNwYW4g c3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+ICI8YSBocmVmPSJtYWlsdG86c2Fj bUBpZXRmLm9yZyI+c2FjbUBpZXRmLm9yZzwvYT4iICZsdDs8YSBocmVmPSJtYWlsdG86c2FjbUBp ZXRmLm9yZyI+c2FjbUBpZXRmLm9yZzwvYT4mZ3Q7LCAiPGEgaHJlZj0ibWFpbHRvOm1pbGVAaWV0 Zi5vcmciPm1pbGVAaWV0Zi5vcmc8L2E+IiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1pbGVAaWV0Zi5v cmciPm1pbGVAaWV0Zi5vcmc8L2E+Jmd0Ozxicj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9s ZCI+U3ViamVjdDogPC9zcGFuPiBSZTogW21pbGVdIFVwY29taW5nIEJvRiBhdCB0aGUgSVQgU2Vj dXJpdHkgQXV0b21hdGlvbiBDb25mZXJlbmNlPGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+ PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJz ZXQ9dXRmLTgiPjxkaXYgYmdjb2xvcj0iI0ZGRkZGRiIgdGV4dD0iIzAwMDAwMCI+PGRpdiBjbGFz cz0ibW96LWNpdGUtcHJlZml4Ij5IaSBKb2huLDxicj48YnI+DQpIb3cgYXJlIGdvaW5nIHRvIHBy b3ZpZGUgbm90aWNlIG9mIHRoZSByb29tPGJyPg0KdG8gdGhvc2Ugb2YgdXMgdGhlcmU/PGJyPjxi cj4NCi0tdG9ueTxicj48YnI+DQpPbiA5LzI0LzIwMTIgMjowMSBQTSwgQmFuZ2hhcnQsIEpvaG4g d3JvdGU6PGJyPjwvZGl2PjxibG9ja3F1b3RlIGNpdGU9Im1pZDpDQzg2MTg0OC40Rjc2JTI1am9o bi5iYW5naGFydEBuaXN0LmdvdiIgdHlwZT0iY2l0ZSI+PGRpdj48ZGl2PkhlbGxvIGFsbCw8L2Rp dj48ZGl2Pjxicj48L2Rpdj48ZGl2PlRoZXJlIHdpbGwgYmUgYSBiaXJkcy1vZi1hLWZlYXRoZXIg KEJvRikgc2Vzc2lvbiBhdCB0aGUgdXBjb21pbmcgSVQgU2VjdXJpdHkgQXV0b21hdGlvbiBDb25m ZXJlbmNlIChJVFNBQykgaW4gQmFsdGltb3JlIG9uIFdlZG5lc2RheSwgT2N0b2JlciA0dGgsIGZy b20gNTozMHBtIHRvIDY6MzBwbSwgZm9jdXNpbmcgb24gaW50ZXJuYXRpb25hbCBlZmZvcnRzIHRv IGRldmVsb3Agc2VjdXJpdHkgYXV0b21hdGlvbiBzdGFuZGFyZHMuICZuYnNwO1RoZSBCb0YNCiB3 aWxsIGZvY3VzIG9uIHJldmlld2luZyBjdXJyZW50IGVmZm9ydHMgdG8gc3RhbmRhcmRpemUgc2Vj dXJpdHkgYXV0b21hdGlvbiBjYXBhYmlsaXRpZXMgYW5kIGhvdyB0byBlbmdhZ2UgaW4gdGhlc2Ug ZWZmb3J0cy4gJm5ic3A7QW55b25lIGFjdGl2ZWx5IG9yIGludGVyZXN0ZWQgaW4gcGFydGljaXBh dGluZyBpbiBvciB1c2luZyBzdGFuZGFyZHMgZGV2ZWxvcGVkIGJ5IGludGVybmF0aW9uYWwgc3Rh bmRhcmRzIGRldmVsb3BtZW50IG9yZ2FuaXphdGlvbnMNCiAoU0RPcykgc2hvdWxkIGF0dGVuZC4g Jm5ic3A7UGFydGljaXBhbnRzIGFyZSBlbmNvdXJhZ2VkIHRvIHNoYXJlIHRoZWlyIHVzZSBjYXNl cyBhbmQgcmVxdWlyZW1lbnRzIGZvciBzZWN1cml0eSBhdXRvbWF0aW9uIHN0YW5kYXJkcy48L2Rp dj48ZGl2PiZuYnNwOzwvZGl2PjxkaXY+Rm9yIG1vcmUgaW5mb3JtYXRpb24gb24gdGhlIElUU0FD LCBwbGVhc2UgdmlzaXQ6IDxhIGNsYXNzPSJtb3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0 dHBzOi8vaXRzYWMuZzJwbGFuZXQuY29tL2l0c2FjMjAxMiI+DQpodHRwczovL2l0c2FjLmcycGxh bmV0LmNvbS9pdHNhYzIwMTI8L2E+LiAmbmJzcDs8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PlBs ZWFzZSBub3RlIHRoYXQgcmVtb3RlIGFjY2VzcyBjYXBhYmlsaXRpZXMgd2lsbCBub3QgYmUgcG9z c2libGUuPC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5JZiB0aGVyZSBpcyBzdWZmaWNp ZW50IGludGVyZXN0LCBJIHdpbGwgcHJvdmlkZSBhZGRpdGlvbmFsIGRldGFpbHMgb24gdGhlIHJv b20gbnVtYmVyIGFuZCBvdGhlciBsb2dpc3RpY3MuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5U aGFuayB5b3UuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4tSm9objwvZGl2PjxkaXY+PGJyPjwv ZGl2PjxkaXY+PGRpdj48ZGl2Pi0tPC9kaXY+PGRpdj5Kb2huIEJhbmdoYXJ0PC9kaXY+PGRpdj5Q cm9ncmFtIEFuYWx5c3Q8L2Rpdj48ZGl2PlByb2dyYW0gQ29vcmRpbmF0aW9uIE9mZmljZTwvZGl2 PjxkaXY+T2ZmaWNlIG9mIHRoZSBVbmRlciBTZWNyZXRhcnkgb2YgQ29tbWVyY2UgZm9yIFN0YW5k YXJkcyBhbmQgVGVjaG5vbG9neTwvZGl2PjxkaXY+TmF0aW9uYWwgSW5zdGl0dXRlIG9mIFN0YW5k YXJkcyBhbmQgVGVjaG5vbG9neTwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+KDMwMSkgOTc1LTgw ODU8L2Rpdj48ZGl2PjxhIGNsYXNzPSJtb3otdHh0LWxpbmstYWJicmV2aWF0ZWQiIGhyZWY9Im1h aWx0bzpKb2huLmJhbmdoYXJ0QG5pc3QuZ292Ij5Kb2huLmJhbmdoYXJ0QG5pc3QuZ292PC9hPjwv ZGl2PjwvZGl2PjwvZGl2Pjxicj48ZmllbGRzZXQgY2xhc3M9Im1pbWVBdHRhY2htZW50SGVhZGVy Ij48L2ZpZWxkc2V0PiA8YnI+PHByZSB3cmFwPSIiPl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fDQptaWxlIG1haWxpbmcgbGlzdA0KPGEgY2xhc3M9Im1vei10 eHQtbGluay1hYmJyZXZpYXRlZCIgaHJlZj0ibWFpbHRvOm1pbGVAaWV0Zi5vcmciPm1pbGVAaWV0 Zi5vcmc8L2E+PGEgY2xhc3M9Im1vei10eHQtbGluay1mcmVldGV4dCIgaHJlZj0iaHR0cHM6Ly93 d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9taWxlIj5odHRwczovL3d3dy5pZXRmLm9yZy9t YWlsbWFuL2xpc3RpbmZvL21pbGU8L2E+PC9wcmU+PC9ibG9ja3F1b3RlPjxicj48L2Rpdj48L2Rp dj48L3NwYW4+PC9ib2R5PjwvaHRtbD4NCg== --_000_CC8622F34F8Fjohnbanghartnistgov_-- From john.banghart@nist.gov Mon Sep 24 12:26:34 2012 Return-Path: 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 A76C521F88AE; Mon, 24 Sep 2012 12:26:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.845 X-Spam-Level: X-Spam-Status: No, score=-4.845 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWVG7BLe4PcU; Mon, 24 Sep 2012 12:26:30 -0700 (PDT) Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id AE5F021F88AD; Mon, 24 Sep 2012 12:26:30 -0700 (PDT) Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.379.0; Mon, 24 Sep 2012 15:26:20 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Mon, 24 Sep 2012 15:24:48 -0400 From: "Banghart, John" To: "Banghart, John" , "sacm@ietf.org" , "mile@ietf.org" Date: Mon, 24 Sep 2012 15:26:27 -0400 Thread-Topic: [mile] Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2aikL6gV4NdUTRQnyFuOkJdGgRYg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CC862BD74F9Fjohnbanghartnistgov_" MIME-Version: 1.0 Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 19:26:34 -0000 --_000_CC862BD74F9Fjohnbanghartnistgov_ Content-Type: text/plain; charset="us-ascii" Minor correction. I meant Wednesday the 3rd, which is the first day of the conference. -John From: , "Banghart, John" > Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" >, "mile@ietf.org" > Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards. The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts. Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend. Participants are encouraged to share their use cases and requirements for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the room number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov --_000_CC862BD74F9Fjohnbanghartnistgov_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13 ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1z cGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAxNHB4OyBmb250LWZhbWlseTog Q2FsaWJyaSwgc2Fucy1zZXJpZjsgIj48ZGl2Pk1pbm9yIGNvcnJlY3Rpb24uICZuYnNwO0kgbWVh bnQgV2VkbmVzZGF5IHRoZSAzcmQsIHdoaWNoIGlzIHRoZSBmaXJzdCBkYXkgb2YgdGhlIGNvbmZl cmVuY2UuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4tSm9objwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6 Q2FsaWJyaTsgZm9udC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVmdDsgY29sb3I6YmxhY2s7IEJP UkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJ TkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGluOyBQQURESU5HLVJJR0hUOiAwaW47IEJP UkRFUi1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQ QURESU5HLVRPUDogM3B0Ij48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTogPC9z cGFuPiAmbHQ7QmFuZ2hhcnQmZ3Q7LCAiQmFuZ2hhcnQsIEpvaG4iICZsdDs8YSBocmVmPSJtYWls dG86am9obi5iYW5naGFydEBuaXN0LmdvdiI+am9obi5iYW5naGFydEBuaXN0LmdvdjwvYT4mZ3Q7 PGJyPjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+IE1vbmRheSwg U2VwdGVtYmVyIDI0LCAyMDEyIDI6MDEgUE08YnI+PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJv bGQiPlRvOiA8L3NwYW4+ICI8YSBocmVmPSJtYWlsdG86c2FjbUBpZXRmLm9yZyI+c2FjbUBpZXRm Lm9yZzwvYT4iICZsdDs8YSBocmVmPSJtYWlsdG86c2FjbUBpZXRmLm9yZyI+c2FjbUBpZXRmLm9y ZzwvYT4mZ3Q7LCAiPGEgaHJlZj0ibWFpbHRvOm1pbGVAaWV0Zi5vcmciPm1pbGVAaWV0Zi5vcmc8 L2E+IiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1pbGVAaWV0Zi5vcmciPm1pbGVAaWV0Zi5vcmc8L2E+ Jmd0Ozxicj48c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPiBb bWlsZV0gVXBjb21pbmcgQm9GIGF0IHRoZSBJVCBTZWN1cml0eSBBdXRvbWF0aW9uIENvbmZlcmVu Y2U8YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48bWV0YSBodHRwLWVxdWl2PSJDb250ZW50 LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+PGRpdiBzdHlsZT0id29y ZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGlu ZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6 ZTogMTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7ICI+PGRpdj48ZGl2Pkhl bGxvIGFsbCw8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PlRoZXJlIHdpbGwgYmUgYSBiaXJkcy1v Zi1hLWZlYXRoZXIgKEJvRikgc2Vzc2lvbiBhdCB0aGUgdXBjb21pbmcgSVQgU2VjdXJpdHkgQXV0 b21hdGlvbiBDb25mZXJlbmNlIChJVFNBQykgaW4gQmFsdGltb3JlIG9uIFdlZG5lc2RheSwgT2N0 b2JlciA0dGgsIGZyb20gNTozMHBtIHRvIDY6MzBwbSwgZm9jdXNpbmcgb24gaW50ZXJuYXRpb25h bCBlZmZvcnRzIHRvIGRldmVsb3Agc2VjdXJpdHkgYXV0b21hdGlvbiBzdGFuZGFyZHMuICZuYnNw O1RoZSBCb0YNCiB3aWxsIGZvY3VzIG9uIHJldmlld2luZyBjdXJyZW50IGVmZm9ydHMgdG8gc3Rh bmRhcmRpemUgc2VjdXJpdHkgYXV0b21hdGlvbiBjYXBhYmlsaXRpZXMgYW5kIGhvdyB0byBlbmdh Z2UgaW4gdGhlc2UgZWZmb3J0cy4gJm5ic3A7QW55b25lIGFjdGl2ZWx5IG9yIGludGVyZXN0ZWQg aW4gcGFydGljaXBhdGluZyBpbiBvciB1c2luZyBzdGFuZGFyZHMgZGV2ZWxvcGVkIGJ5IGludGVy bmF0aW9uYWwgc3RhbmRhcmRzIGRldmVsb3BtZW50IG9yZ2FuaXphdGlvbnMNCiAoU0RPcykgc2hv dWxkIGF0dGVuZC4gJm5ic3A7UGFydGljaXBhbnRzIGFyZSBlbmNvdXJhZ2VkIHRvIHNoYXJlIHRo ZWlyIHVzZSBjYXNlcyBhbmQgcmVxdWlyZW1lbnRzIGZvciBzZWN1cml0eSBhdXRvbWF0aW9uIHN0 YW5kYXJkcy48L2Rpdj48ZGl2PiZuYnNwOzwvZGl2PjxkaXY+Rm9yIG1vcmUgaW5mb3JtYXRpb24g b24gdGhlIElUU0FDLCBwbGVhc2UgdmlzaXQ6IDxhIGhyZWY9Imh0dHBzOi8vaXRzYWMuZzJwbGFu ZXQuY29tL2l0c2FjMjAxMiI+aHR0cHM6Ly9pdHNhYy5nMnBsYW5ldC5jb20vaXRzYWMyMDEyPC9h Pi4gJm5ic3A7PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5QbGVhc2Ugbm90ZSB0aGF0IHJlbW90 ZSBhY2Nlc3MgY2FwYWJpbGl0aWVzIHdpbGwgbm90IGJlIHBvc3NpYmxlLjwvZGl2PjwvZGl2Pjxk aXY+PGJyPjwvZGl2PjxkaXY+SWYgdGhlcmUgaXMgc3VmZmljaWVudCBpbnRlcmVzdCwgSSB3aWxs IHByb3ZpZGUgYWRkaXRpb25hbCBkZXRhaWxzIG9uIHRoZSByb29tIG51bWJlciBhbmQgb3RoZXIg bG9naXN0aWNzLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+VGhhbmsgeW91LjwvZGl2PjxkaXY+ PGJyPjwvZGl2PjxkaXY+LUpvaG48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PjxkaXY+PGRpdj4t LTwvZGl2PjxkaXY+Sm9obiBCYW5naGFydDwvZGl2PjxkaXY+UHJvZ3JhbSBBbmFseXN0PC9kaXY+ PGRpdj5Qcm9ncmFtIENvb3JkaW5hdGlvbiBPZmZpY2U8L2Rpdj48ZGl2Pk9mZmljZSBvZiB0aGUg VW5kZXIgU2VjcmV0YXJ5IG9mIENvbW1lcmNlIGZvciBTdGFuZGFyZHMgYW5kIFRlY2hub2xvZ3k8 L2Rpdj48ZGl2Pk5hdGlvbmFsIEluc3RpdHV0ZSBvZiBTdGFuZGFyZHMgYW5kIFRlY2hub2xvZ3k8 L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PigzMDEpIDk3NS04MDg1PC9kaXY+PGRpdj48YSBocmVm PSJtYWlsdG86Sm9obi5iYW5naGFydEBuaXN0LmdvdiI+Sm9obi5iYW5naGFydEBuaXN0Lmdvdjwv YT48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L3NwYW4+PC9ib2R5PjwvaHRtbD4NCg== --_000_CC862BD74F9Fjohnbanghartnistgov_-- From prvs=1614f1dcfb=radams@ewa-canada.com Mon Sep 24 13:45:59 2012 Return-Path: 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 4EFDD21F88E8; Mon, 24 Sep 2012 13:45:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.264 X-Spam-Level: X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id my7wdFxApoBU; Mon, 24 Sep 2012 13:45:57 -0700 (PDT) Received: from ewa-canada.com (def087.ewa-canada.com [67.210.169.87]) by ietfa.amsl.com (Postfix) with ESMTP id A268021F88DA; Mon, 24 Sep 2012 13:45:57 -0700 (PDT) Received: from ext-mail.int.ewa-canada.com ([172.16.230.4]) by FortiMail.int.ewa-canada.com with ESMTP id q8OKjrFW025632-q8OKjrFX025632; Mon, 24 Sep 2012 16:45:53 -0400 Received: from radams (ewa230-179.ewa-canada.com [172.16.230.179]) by ext-mail.int.ewa-canada.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id TK8SVDJW; Mon, 24 Sep 2012 16:45:53 -0400 Received: from radams by radams (PGP Universal service); Mon, 24 Sep 2012 16:45:53 -0500 X-PGP-Universal: processed; by radams on Mon, 24 Sep 2012 16:45:53 -0500 From: "Richard Adams" To: "'Banghart, John'" , , References: In-Reply-To: Date: Mon, 24 Sep 2012 16:45:53 -0400 Organization: EWAC Message-ID: <00a401cd9a95$96e6dfd0$c4b49f70$@ewa-canada.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQLEqhmY+UeV8bqg61BoWr4vn25TsJWr0aCA Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01CD9A74.0FD53FD0" Content-Language: en-ca Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 20:45:59 -0000 This is a multipart message in MIME format. ------=_NextPart_000_00A5_01CD9A74.0FD53FD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi John, I have a quick question regarding this; do you know how specific the talk will be? Will there be any mention of the "new" ITSG-33 that we Canadians are about to put out? I apologize if this question is out of sorts, I haven't been keeping up with the lists as much as I'd like. Thanks. Richee From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, John Sent: September-24-12 3:26 PM To: Banghart, John; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Minor correction. I meant Wednesday the 3rd, which is the first day of the conference. -John From: , "Banghart, John" Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" , "mile@ietf.org" Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards. The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts. Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend. Participants are encouraged to share their use cases and requirements for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the room number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov ------=_NextPart_000_00A5_01CD9A74.0FD53FD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi John,

 

I have a quick question regarding this; do you know how specific the = talk will be?  Will there be any mention of the “new” = ITSG-33 that we Canadians are about to put out?  I apologize if = this question is out of sorts, I haven’t been keeping up with the = lists as much as I’d like.

 

Thanks.

 

Richee

 

From:= = mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of = Banghart, John
Sent: September-24-12 3:26 PM
To: = Banghart, John; sacm@ietf.org; mile@ietf.org
Subject: Re: = [mile] Upcoming BoF at the IT Security Automation = Conference

 

Minor correction.  I meant Wednesday the 3rd, which is the first = day of the conference.

 

-John

 

From: <Banghart>, "Banghart, John" <john.banghart@nist.gov>
= Date: Monday, September 24, 2012 2:01 PM
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
Subject: = [mile] Upcoming BoF at the IT Security Automation = Conference

 

Hello all,

 

There will be a birds-of-a-feather (BoF) session at the upcoming IT = Security Automation Conference (ITSAC) in Baltimore on Wednesday, = October 4th, from 5:30pm to 6:30pm, focusing on international efforts to = develop security automation standards.  The BoF will focus on = reviewing current efforts to standardize security automation = capabilities and how to engage in these efforts.  Anyone actively = or interested in participating in or using standards developed by = international standards development organizations (SDOs) should attend. =  Participants are encouraged to share their use cases and = requirements for security automation = standards.

 

For more information on the ITSAC, please visit: https://itsac.g2planet.com/= itsac2012.  

 

Please note that remote access capabilities will not be = possible.

 

If there is sufficient interest, I will provide additional details on = the room number and other logistics.

 

Thank you.

 

-John

 

--

John Banghart

Program Analyst

Program Coordination Office

Office of the Under Secretary of Commerce for Standards and = Technology

National Institute of Standards and = Technology

 

(301) 975-8085

------=_NextPart_000_00A5_01CD9A74.0FD53FD0-- From john.banghart@nist.gov Tue Sep 25 05:22:12 2012 Return-Path: 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 2C64A21F88A0; Tue, 25 Sep 2012 05:22:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.722 X-Spam-Level: X-Spam-Status: No, score=-5.722 tagged_above=-999 required=5 tests=[AWL=0.876, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sA-sQh+5N+2Q; Tue, 25 Sep 2012 05:22:10 -0700 (PDT) Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 8886521F8871; Tue, 25 Sep 2012 05:22:10 -0700 (PDT) Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.379.0; Tue, 25 Sep 2012 08:21:58 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Tue, 25 Sep 2012 08:20:25 -0400 From: "Banghart, John" To: Richard Adams , "sacm@ietf.org" , "mile@ietf.org" Date: Tue, 25 Sep 2012 08:22:04 -0400 Thread-Topic: [mile] Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2bGCQv0d9uRVOrRJmtOBdeRZ3DmQ== Message-ID: In-Reply-To: <00a401cd9a95$96e6dfd0$c4b49f70$@ewa-canada.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_CC871A0D5009johnbanghartnistgov_" MIME-Version: 1.0 Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 12:22:12 -0000 --_000_CC871A0D5009johnbanghartnistgov_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Richard, No problem at all. I think the discussion can be as broad as the group lik= es, assuming it is cybersecurity related. -John From: Richard Adams > Organization: EWAC Date: Monday, September 24, 2012 4:45 PM To: "Banghart, John" = >, "sacm@ietf.org" >, "mile@ietf.org" > Subject: RE: [mile] Upcoming BoF at the IT Security Automation Conference Hi John, I have a quick question regarding this; do you know how specific the talk w= ill be? Will there be any mention of the =93new=94 ITSG-33 that we Canadia= ns are about to put out? I apologize if this question is out of sorts, I h= aven=92t been keeping up with the lists as much as I=92d like. Thanks. Richee From: mile-bounces@ietf.org [mailto:mile-boun= ces@ietf.org] On Behalf Of Banghart, John Sent: September-24-12 3:26 PM To: Banghart, John; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Minor correction. I meant Wednesday the 3rd, which is the first day of the= conference. -John From: , "Banghart, John" > Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" >, "mile@ietf.org" > Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Securit= y Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, fro= m 5:30pm to 6:30pm, focusing on international efforts to develop security a= utomation standards. The BoF will focus on reviewing current efforts to st= andardize security automation capabilities and how to engage in these effor= ts. Anyone actively or interested in participating in or using standards d= eveloped by international standards development organizations (SDOs) should= attend. Participants are encouraged to share their use cases and requirem= ents for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com= /itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the r= oom number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov --_000_CC871A0D5009johnbanghartnistgov_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Richard,

No problem at all.  I think the discussion can be as broad as the g= roup likes, assuming it is cybersecurity related.

= -John

From: Richard Adams <radams@ewa-ca= nada.com>
Organization: = EWAC
Date: Monday, September 24= , 2012 4:45 PM
To: "Bangha= rt, John" <john.banghart@= nist.gov>, "sacm@ietf.org&= quot; <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
S= ubject: RE: [mile] Upcoming BoF at the IT Security Automation Confe= rence

Hi John,

 

I have a quick question regarding this; do you know how spe= cific the talk will be?  Will there be any mention of the =93new=94 IT= SG-33 that we Canadians are about to put out?  I apologize if this question is out of sorts, I ha= ven=92t been keeping up with the lists as much as I=92d like.

 <= /span>

Thanks.

&nb= sp;

Richee=

<= span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans-ser= if; ">From: mile= -bounces@ietf.org [mailto:mile= -bounces@ietf.org] On Behalf Of Banghart, John
Sent: September-24-12 3:26 PM<= br>To: Banghart, John; sacm@ietf.or= g; mile@ietf.org
Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference

 

<= p class=3D"MsoNormal">Minor correction.  I meant Wednesday th= e 3rd, which is the first day of the conference.

 

-John

 

<= p class=3D"MsoNormal">From: <Banghart>, "Banghart, John" <john.banghart@nist.gov>
Dat= e: Monday, September 24, 2012 2:01 PM
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ie= tf.org" <mile@ietf.org>=
Subject: [mile] Upcoming BoF at the IT Security Automation Confe= rence

=  

Hello all,

 

 =

For more information = on the ITSAC, please visit: https://itsac.g2planet.com= /itsac2012.  

 

<= span style=3D"font-size: 10.5pt; color: black; font-family: Calibri, sans-s= erif; ">Please note that remote access capabilities will not be possible.

&= nbsp;

If there i= s sufficient interest, I will provide additional details on the room number= and other logistics.

 

Thank you.

 

 

--

Jo= hn Banghart

Program Analyst

Program Coordination Office

Office of the Under Secretary of Commerce for Stand= ards and Technology

= National Institute of Standards and Technology

 

(301) 975-8085

 --_000_CC871A0D5009johnbanghartnistgov_-- From prvs=1615afa993=radams@ewa-canada.com Tue Sep 25 07:56:45 2012 Return-Path: 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 58D5A21F87FC; Tue, 25 Sep 2012 07:56:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.264 X-Spam-Level: X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1P784hnQMR4; Tue, 25 Sep 2012 07:56:43 -0700 (PDT) Received: from ewa-canada.com (def087.ewa-canada.com [67.210.169.87]) by ietfa.amsl.com (Postfix) with ESMTP id 309D221F87F9; Tue, 25 Sep 2012 07:56:42 -0700 (PDT) Received: from ext-mail.int.ewa-canada.com ([172.16.230.4]) by FortiMail.int.ewa-canada.com with ESMTP id q8PEudeV032640-q8PEudeW032640; Tue, 25 Sep 2012 10:56:39 -0400 Received: from radams (ewa230-179.ewa-canada.com [172.16.230.179]) by ext-mail.int.ewa-canada.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id TK8SV1A4; Tue, 25 Sep 2012 10:56:39 -0400 Received: from radams by radams (PGP Universal service); Tue, 25 Sep 2012 10:56:39 -0500 X-PGP-Universal: processed; by radams on Tue, 25 Sep 2012 10:56:39 -0500 From: "Richard Adams" To: "'Banghart, John'" , , References: <00a401cd9a95$96e6dfd0$c4b49f70$@ewa-canada.com> In-Reply-To: Date: Tue, 25 Sep 2012 10:56:39 -0400 Organization: EWAC Message-ID: <005401cd9b2d$f781e090$e685a1b0$@ewa-canada.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKY/R07r2fCsn/sjAYQJmvHjbQjlpYEYLnA Content-Type: multipart/alternative; boundary="----=_NextPart_000_0055_01CD9B0C.70704090" Content-Language: en-ca Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 14:56:45 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0055_01CD9B0C.70704090 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit John, Is it possible to get the name of the individual that will be moderating this meeting? Thanks. Richee From: Banghart, John [mailto:john.banghart@nist.gov] Sent: September-25-12 8:22 AM To: Richard Adams; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Richard, No problem at all. I think the discussion can be as broad as the group likes, assuming it is cybersecurity related. -John From: Richard Adams Organization: EWAC Date: Monday, September 24, 2012 4:45 PM To: "Banghart, John" , "sacm@ietf.org" , "mile@ietf.org" Subject: RE: [mile] Upcoming BoF at the IT Security Automation Conference Hi John, I have a quick question regarding this; do you know how specific the talk will be? Will there be any mention of the "new" ITSG-33 that we Canadians are about to put out? I apologize if this question is out of sorts, I haven't been keeping up with the lists as much as I'd like. Thanks. Richee From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, John Sent: September-24-12 3:26 PM To: Banghart, John; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Minor correction. I meant Wednesday the 3rd, which is the first day of the conference. -John From: , "Banghart, John" Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" , "mile@ietf.org" Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Security Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, from 5:30pm to 6:30pm, focusing on international efforts to develop security automation standards. The BoF will focus on reviewing current efforts to standardize security automation capabilities and how to engage in these efforts. Anyone actively or interested in participating in or using standards developed by international standards development organizations (SDOs) should attend. Participants are encouraged to share their use cases and requirements for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com/itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the room number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov ------=_NextPart_000_0055_01CD9B0C.70704090 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

John,

 

Is it possible to get the name of the individual that will be = moderating this meeting?

 

Thanks.

 

Richee

 

From:= Banghart, = John [mailto:john.banghart@nist.gov]
Sent: September-25-12 = 8:22 AM
To: Richard Adams; sacm@ietf.org; = mile@ietf.org
Subject: Re: [mile] Upcoming BoF at the IT = Security Automation Conference

 

Richard,

 

No problem at all.  I think the discussion can be as broad as the = group likes, assuming it is cybersecurity = related.

 

-John

 

From: Richard Adams <radams@ewa-canada.com>
Organization: EWAC
Date: Monday, September 24, 2012 4:45 = PM
To: "Banghart, John" <john.banghart@nist.gov>, = "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
Subject: = RE: [mile] Upcoming BoF at the IT Security Automation = Conference

 

Hi John,

 

I have a quick question regarding this; do you know how specific the = talk will be?  Will there be any mention of the “new” = ITSG-33 that we Canadians are about to put out?  I apologize if = this question is out of sorts, I haven’t been keeping up with the = lists as much as I’d like.

 

Thanks.

 

Richee

 

= From:= mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] = On Behalf Of Banghart, John
Sent: September-24-12 3:26 = PM
To: Banghart, John; sacm@ietf.org; mile@ietf.org
Subject: Re: = [mile] Upcoming BoF at the IT Security Automation Conference

 

Minor correction.  I meant Wednesday the 3rd, which is the first = day of the conference.

 

-John

 

From: <Banghart>, "Banghart, John" <john.banghart@nist.gov>
= Date: Monday, September 24, 2012 2:01 PM
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>
Subject: = [mile] Upcoming BoF at the IT Security Automation = Conference

 

Hello all,

 

There will be a birds-of-a-feather (BoF) session at the upcoming IT = Security Automation Conference (ITSAC) in Baltimore on Wednesday, = October 4th, from 5:30pm to 6:30pm, focusing on international efforts to = develop security automation standards.  The BoF will focus on = reviewing current efforts to standardize security automation = capabilities and how to engage in these efforts.  Anyone actively = or interested in participating in or using standards developed by = international standards development organizations (SDOs) should attend. =  Participants are encouraged to share their use cases and = requirements for security automation standards.

 

For more information on the ITSAC, please visit: https://itsac.g2planet.com/= itsac2012.  

 

Please note that remote access capabilities will not be = possible.

 

If there is sufficient interest, I will provide additional details on = the room number and other logistics.

 

Thank you.

 

-John

 

--

John Banghart

Program Analyst

Program Coordination Office

Office of the Under Secretary of Commerce for Standards and = Technology

National Institute of Standards and Technology

 

(301) 975-8085

John.banghart@nist.gov<= span = style=3D'color:black'>

------=_NextPart_000_0055_01CD9B0C.70704090-- From john.banghart@nist.gov Tue Sep 25 07:59:43 2012 Return-Path: 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 C572E21F884F; Tue, 25 Sep 2012 07:59:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.897 X-Spam-Level: X-Spam-Status: No, score=-5.897 tagged_above=-999 required=5 tests=[AWL=0.701, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMagGaQmzjhy; Tue, 25 Sep 2012 07:59:42 -0700 (PDT) Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 4133E21F8841; Tue, 25 Sep 2012 07:59:36 -0700 (PDT) Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.379.0; Tue, 25 Sep 2012 10:59:03 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Tue, 25 Sep 2012 10:57:29 -0400 From: "Banghart, John" To: Richard Adams Date: Tue, 25 Sep 2012 10:59:13 -0400 Thread-Topic: [mile] Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2bLhXFkrWUoQaXQ96WSX5hPL10+w== Message-ID: References: <00a401cd9a95$96e6dfd0$c4b49f70$@ewa-canada.com> <005401cd9b2d$f781e090$e685a1b0$@ewa-canada.com> In-Reply-To: <005401cd9b2d$f781e090$e685a1b0$@ewa-canada.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_A9D339F8A4AF4144A7767B1E3AF025EDnistgov_" MIME-Version: 1.0 Cc: "mile@ietf.org" , "sacm@ietf.org" Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 14:59:43 -0000 --_000_A9D339F8A4AF4144A7767B1E3AF025EDnistgov_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Richee, Well, I guess it's me unless someone else wants to volunteer. :) -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov On Sep 25, 2012, at 10:56 AM, Richard Adams wrote: John, Is it possible to get the name of the individual that will be moderating th= is meeting? Thanks. Richee From: Banghart, John [mailto:john.banghart@nist.gov] Sent: September-25-12 8:22 AM To: Richard Adams; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Richard, No problem at all. I think the discussion can be as broad as the group lik= es, assuming it is cybersecurity related. -John From: Richard Adams > Organization: EWAC Date: Monday, September 24, 2012 4:45 PM To: "Banghart, John" = >, "sacm@ietf.org" >, "mile@ietf.org" > Subject: RE: [mile] Upcoming BoF at the IT Security Automation Conference Hi John, I have a quick question regarding this; do you know how specific the talk w= ill be? Will there be any mention of the =93new=94 ITSG-33 that we Canadia= ns are about to put out? I apologize if this question is out of sorts, I h= aven=92t been keeping up with the lists as much as I=92d like. Thanks. Richee From: mile-bounces@ietf.org [mailto:mile-boun= ces@ietf.org] On Behalf Of Banghart, John Sent: September-24-12 3:26 PM To: Banghart, John; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Minor correction. I meant Wednesday the 3rd, which is the first day of the= conference. -John From: , "Banghart, John" > Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" >, "mile@ietf.org" > Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Securit= y Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, fro= m 5:30pm to 6:30pm, focusing on international efforts to develop security a= utomation standards. The BoF will focus on reviewing current efforts to st= andardize security automation capabilities and how to engage in these effor= ts. Anyone actively or interested in participating in or using standards d= eveloped by international standards development organizations (SDOs) should= attend. Participants are encouraged to share their use cases and requirem= ents for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com= /itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the r= oom number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov --_000_A9D339F8A4AF4144A7767B1E3AF025EDnistgov_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Richee,

Well, I guess it's me unless someone else wants to volunteer.  :)

--
John Banghart
Program Analyst
Program Coordination Of= fice
Natio= nal Institute of Standards and Technology

(301) 975-8085

On Sep 25, 2012, at 10:56 AM, Richard Adams wrote:

John,
 
Is it possible to get the name of the individual that will= be moderating this meeting?
 
Thanks.
 
Richee
=  
Fr= om: Ban= ghart, John [mailto:john.banghart@nist.gov] 
Sent:&n= bsp;September-25-12 8:22 AM
To: Richard Adams; sacm@ietf.org; mile@ietf.org
Subject: Re: [mile] Upcoming BoF at the IT S= ecurity Automation Conference
&nbs= p;
Richard,
 
No problem at all= .  I think the discussion can be as broad as the group likes, assuming= it is cybersecurity related.
=  
-John<= /div>
 
 Richard Adams <radams@ewa-canada.com>
Or= ganization: EWAC
<= b>Date: Monday, Septe= mber 24, 2012 4:45 PM
To: = "Banghart, John" <john.banghart@nist.gov>, "sacm@ietf.org" <sacm@ietf.org>, = "mile@ietf.org" <mile@ietf.org>
Sub= ject: RE: [mile] Upco= ming BoF at the IT Security Automation Conference
 
Hi John,<= /span>
 
I have a quick quest= ion regarding this; do you know how specific the talk will be?  Will t= here be any mention of the =93new=94 ITSG-33 that we Canadians are about to= put out?  I apologize if this question is out of sorts, I haven=92t b= een keeping up with the lists as much as I=92d like.
 
Thanks.
 
Richee=
 =
From: mile= -bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, John
Sent: September-24-12 3:26 PM
To: Banghart, John; sacm@ietf.org; mile@ietf.org
Subj= ect: Re: [mile] Upcom= ing BoF at the IT Security Automation Conference
 
Minor correction.  I = meant Wednesday the 3rd, which is the first day of the conference.
=  
<= div>
-John=
 
From: <Banghart>, "Banghart, John" = <john.banghart@nist.gov>
Date: Monday, September 24, 2012 2:0= 1 PM
To: "sacm@ietf.org" <sacm@ietf.org>, "mil= e@ietf.org" <mile@ietf.org>
Subject: [mile] Upcoming BoF at the IT= Security Automation Conference<= /o:p>
 
Hello a= ll,
 
There will be a birds-of-a-feather (BoF) session a= t the upcoming IT Security Automation Conference (ITSAC) in Baltimore on We= dnesday, October 4th, from 5:30pm to 6:30pm, focusing on international effo= rts to develop security automation standards.  The BoF will focus on r= eviewing current efforts to standardize security automation capabilities an= d how to engage in these efforts.  Anyone actively or interested in pa= rticipating in or using standards developed by international standards deve= lopment organizations (SDOs) should attend.  Participants are encourag= ed to share their use cases and requirements for security automation standa= rds.
 <= /div>
For more information on the ITSAC, please visit:<= span class=3D"Apple-converted-space"> https://itsac.g2planet.com/itsac2012.  
 
Pl= ease note that remote access capabilities will not be possible.
If there is sufficient interest, I will provide additional = details on the room number and other logistics.
 
Thank = you.
 <= /div>
-John<= /o:p>
 
--
= John Banghart
=
Program Coordination Office
Office of the Under Secretary of Commerce for Standards and Technology<= /span>
National Institute of Standards and Technology
 <= span style=3D"color: black; ">
= (301) 975-8085
John.banghart@nist.gov<= span style=3D"color: black; ">

= = --_000_A9D339F8A4AF4144A7767B1E3AF025EDnistgov_-- From john.banghart@nist.gov Tue Sep 25 08:02:10 2012 Return-Path: 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 700F521F88E6; Tue, 25 Sep 2012 08:02:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.014 X-Spam-Level: X-Spam-Status: No, score=-6.014 tagged_above=-999 required=5 tests=[AWL=0.584, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2EYK3cSp5KZ; Tue, 25 Sep 2012 08:02:09 -0700 (PDT) Received: from wsget1.nist.gov (wsget1.nist.gov [129.6.13.150]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC4A21F887B; Tue, 25 Sep 2012 08:02:07 -0700 (PDT) Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.1.379.0; Tue, 25 Sep 2012 11:01:30 -0400 Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Tue, 25 Sep 2012 11:00:00 -0400 From: "Banghart, John" To: Richard Adams Date: Tue, 25 Sep 2012 11:01:44 -0400 Thread-Topic: [sacm] [mile] Upcoming BoF at the IT Security Automation Conference Thread-Index: Ac2bLm+QgU0ejbTETJevvvKrckUfxw== Message-ID: <3C4B0547-AFB4-408D-B308-61828C153E67@nist.gov> References: <00a401cd9a95$96e6dfd0$c4b49f70$@ewa-canada.com> <005401cd9b2d$f781e090$e685a1b0$@ewa-canada.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_3C4B0547AFB4408DB30861828C153E67nistgov_" MIME-Version: 1.0 Cc: "mile@ietf.org" , "sacm@ietf.org" Subject: Re: [mile] [sacm] Upcoming BoF at the IT Security Automation Conference X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2012 15:02:10 -0000 --_000_3C4B0547AFB4408DB30861828C153E67nistgov_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable All, Not picking on Richard, but to save everyone's Inbox, let's stop cross-post= ing unless you want to discuss topic relevant things for the BoF. Any admi= nistrative questions can be directed to me. Thanks! -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov On Sep 25, 2012, at 10:59 AM, Banghart, John wrote: Richee, Well, I guess it's me unless someone else wants to volunteer. :) -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov On Sep 25, 2012, at 10:56 AM, Richard Adams wrote: John, Is it possible to get the name of the individual that will be moderating th= is meeting? Thanks. Richee From: Banghart, John [mailto:john.banghart@nist.gov] Sent: September-25-12 8:22 AM To: Richard Adams; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Richard, No problem at all. I think the discussion can be as broad as the group lik= es, assuming it is cybersecurity related. -John From: Richard Adams > Organization: EWAC Date: Monday, September 24, 2012 4:45 PM To: "Banghart, John" = >, "sacm@ietf.org" >, "mile@ietf.org" > Subject: RE: [mile] Upcoming BoF at the IT Security Automation Conference Hi John, I have a quick question regarding this; do you know how specific the talk w= ill be? Will there be any mention of the =93new=94 ITSG-33 that we Canadia= ns are about to put out? I apologize if this question is out of sorts, I h= aven=92t been keeping up with the lists as much as I=92d like. Thanks. Richee From: mile-bounces@ietf.org [mailto:mile-boun= ces@ietf.org] On Behalf Of Banghart, John Sent: September-24-12 3:26 PM To: Banghart, John; sacm@ietf.org; mile@ietf.org Subject: Re: [mile] Upcoming BoF at the IT Security Automation Conference Minor correction. I meant Wednesday the 3rd, which is the first day of the= conference. -John From: , "Banghart, John" > Date: Monday, September 24, 2012 2:01 PM To: "sacm@ietf.org" >, "mile@ietf.org" > Subject: [mile] Upcoming BoF at the IT Security Automation Conference Hello all, There will be a birds-of-a-feather (BoF) session at the upcoming IT Securit= y Automation Conference (ITSAC) in Baltimore on Wednesday, October 4th, fro= m 5:30pm to 6:30pm, focusing on international efforts to develop security a= utomation standards. The BoF will focus on reviewing current efforts to st= andardize security automation capabilities and how to engage in these effor= ts. Anyone actively or interested in participating in or using standards d= eveloped by international standards development organizations (SDOs) should= attend. Participants are encouraged to share their use cases and requirem= ents for security automation standards. For more information on the ITSAC, please visit: https://itsac.g2planet.com= /itsac2012. Please note that remote access capabilities will not be possible. If there is sufficient interest, I will provide additional details on the r= oom number and other logistics. Thank you. -John -- John Banghart Program Analyst Program Coordination Office Office of the Under Secretary of Commerce for Standards and Technology National Institute of Standards and Technology (301) 975-8085 John.banghart@nist.gov --_000_3C4B0547AFB4408DB30861828C153E67nistgov_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable All,

No= t picking on Richard, but to save everyone's Inbox, let's stop cross-postin= g unless you want to discuss topic relevant things for the BoF.  Any a= dministrative questions can be directed to me.

Tha= nks!

 
--
John Banghart
Program Analyst
Program Coordination Of= fice
Natio= nal Institute of Standards and Technology

(301) 975-8085

On Sep 25, 2012, at 10:59 AM, Banghart, John wrote:

Richee,

Well, I guess it's me unless som= eone else wants to volunteer.  :)

--
John Banghart
Program Analyst
Program Coordination Office
Office of the Unde= r Secretary of Commerce for Standards and Technology
National Institute of Sta= ndards and Technology

(301) 975-8085

No problem at all= .  I think the discussion can be as broad as the group likes, assuming= it is cybersecurity related.
=  
-John<= /div>
 
 Richard Adams <radams@ewa-canada.com>
Or= ganization: EWAC
<= b>Date: Monday, Septe= mber 24, 2012 4:45 PM
To: = "Banghart, John" <john.banghart@nist.gov>, "sacm@ietf.org" <sacm@ietf.org>, = "mile@ietf.org" <mile@ietf.org>
Sub= ject: RE: [mile] Upco= ming BoF at the IT Security Automation Conference
 
Hi John,<= /span>
 
I have a quick quest= ion regarding this; do you know how specific the talk will be?  Will t= here be any mention of the =93new=94 ITSG-33 that we Canadians are about to= put out?  I apologize if this question is out of sorts, I haven=92t b= een keeping up with the lists as much as I=92d like.
 
Thanks.
 
Richee=
 =
From: mile= -bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Banghart, John
Sent: September-24-12 3:26 PM
To: Banghart, John; sacm@ietf.org; mile@ietf.org
Subj= ect: Re: [mile] Upcom= ing BoF at the IT Security Automation Conference
 
Minor correction.  I = meant Wednesday the 3rd, which is the first day of the conference.
=  
<= div>
-John=
 
From: <Banghart>, "Banghart, John" = <john.banghart@nist.gov>
Date: Monday, September 24, 2012 2:0= 1 PM
To: "sacm@ietf.org" <sacm@ietf.org>, "mil= e@ietf.org" <mile@ietf.org>
Subject: [mile] Upcoming BoF at the IT= Security Automation Conference<= /o:p>
 
Hello a= ll,
 
There will be a birds-of-a-feather (BoF) session a= t the upcoming IT Security Automation Conference (ITSAC) in Baltimore on We= dnesday, October 4th, from 5:30pm to 6:30pm, focusing on international effo= rts to develop security automation standards.  The BoF will focus on r= eviewing current efforts to standardize security automation capabilities an= d how to engage in these efforts.  Anyone actively or interested in pa= rticipating in or using standards developed by international standards deve= lopment organizations (SDOs) should attend.  Participants are encourag= ed to share their use cases and requirements for security automation standa= rds.
 <= /div>
For more information on the ITSAC, please visit:<= span class=3D"Apple-converted-space"> https://itsac.g2planet.com/itsac2012.  
 
Pl= ease note that remote access capabilities will not be possible.
If there is sufficient interest, I will provide additional = details on the room number and other logistics.
 
Thank = you.
 <= /div>
-John<= /o:p>
 
--
= John Banghart
=
Program Coordination Office
Office of the Under Secretary of Commerce for Standards and Technology<= /span>
National Institute of Standards and Technology
 <= span style=3D"color: black; ">
= (301) 975-8085
John.banghart@nist.gov<= span style=3D"color: black; ">

= <ATT00001..c>
<= /html>= --_000_3C4B0547AFB4408DB30861828C153E67nistgov_-- From kathleen.moriarty@emc.com Thu Sep 27 06:20:01 2012 Return-Path: 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 BD9EB21F8527 for ; Thu, 27 Sep 2012 06:20:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.391 X-Spam-Level: X-Spam-Status: No, score=-2.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBq1CU+v+hjE for ; Thu, 27 Sep 2012 06:20:00 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 87B3821F8525 for ; Thu, 27 Sep 2012 06:20:00 -0700 (PDT) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8RDJwBp022389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2012 09:19:59 -0400 Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 27 Sep 2012 09:19:38 -0400 Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8RDJbeE030823; Thu, 27 Sep 2012 09:19:38 -0400 Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Thu, 27 Sep 2012 09:19:37 -0400 From: "Moriarty, Kathleen" To: "Moriarty, Kathleen" , Adam Montville , "mile@ietf.org" Date: Thu, 27 Sep 2012 09:17:24 -0400 Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gCJ9WXM= Message-ID: References: <20120901134631.30953.45877.idtracker@ietfa.amsl.com>, , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2012 13:20:01 -0000 Adam & MILE members, I read through the draft and think it looks great! I did notice that the i= dentifier format after the id: is not specified. An example is provided, b= ut am wondering if it would be helpful to provide an explicit format to hel= p developers when formatting and parsing the content. Any thoughts - Adam or others on the MILE list? Thank you! Kathleen ________________________________________ From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Moriarty, = Kathleen [kathleen.moriarty@emc.com] Sent: Wednesday, September 05, 2012 10:35 AM To: Adam Montville; mile@ietf.org Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-e= num-reference-format-00.txt Adam, Thank you very much for your work on this draft! MILE members: Please review and comment on the draft. Thank you! Kathleen ________________________________________ From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam Montv= ille [amontville@tripwire.com] Sent: Saturday, September 01, 2012 9:54 AM To: mile@ietf.org Subject: [mile] FW: New Version Notification for draft-montville-mile-enum-= reference-format-00.txt On 9/1/12 6:46 AM, "internet-drafts@ietf.org" wrote: > >A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >has been successfully submitted by Adam W. Montville and posted to the >IETF repository. > >Filename: draft-montville-mile-enum-reference-format >Revision: 00 >Title: IODEF Enumeration Reference Format >Creation date: 2012-09-01 >WG ID: Individual Submission >Number of pages: 6 >URL: >http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-fo >rmat-00.txt >Status: >http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-format >Htmlized: >http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 > > >Abstract: > Some standards, such as the Incident Object Description Exchange > Format [IODEF], provide classes used to reference external entities > (such as enumeration identifiers). At the time of standardization, > however, needed references may not be known, and the method of > external entity identification is often left unstructured. This > document describes, using [IODEF] as an example, a method to provide > structure after the fact. > > > > > > >The IETF Secretariat > > > _______________________________________________ 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 amontville@tripwire.com Thu Sep 27 15:28:27 2012 Return-Path: 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 4095921F8448 for ; Thu, 27 Sep 2012 15:28:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.117 X-Spam-Level: X-Spam-Status: No, score=-5.117 tagged_above=-999 required=5 tests=[AWL=1.482, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMTxg29khxjm for ; Thu, 27 Sep 2012 15:28:26 -0700 (PDT) Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD8821F8442 for ; Thu, 27 Sep 2012 15:28:26 -0700 (PDT) Received: from mail268-tx2-R.bigfish.com (10.9.14.237) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.23; Thu, 27 Sep 2012 22:28:25 +0000 Received: from mail268-tx2 (localhost [127.0.0.1]) by mail268-tx2-R.bigfish.com (Postfix) with ESMTP id 94A081F0014A for ; Thu, 27 Sep 2012 22:28:25 +0000 (UTC) X-Forefront-Antispam-Report: CIP:174.47.84.215; KIP:(null); UIP:(null); IPV:NLI; H:zgw01.tripwire.com; RD:174-47-84-215.static.twtelecom.net; EFVD:NLI X-SpamScore: -31 X-BigFish: VPS-31(zzbb2dI98dI9371I936eI148cI1432I11f6Nd6f1izz1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h944he5bhf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1155h) Received: from mail268-tx2 (localhost.localdomain [127.0.0.1]) by mail268-tx2 (MessageSwitch) id 1348784903473740_27748; Thu, 27 Sep 2012 22:28:23 +0000 (UTC) Received: from TX2EHSMHS044.bigfish.com (unknown [10.9.14.247]) by mail268-tx2.bigfish.com (Postfix) with ESMTP id 7108E600045 for ; Thu, 27 Sep 2012 22:28:23 +0000 (UTC) Received: from zgw01.tripwire.com (174.47.84.215) by TX2EHSMHS044.bigfish.com (10.9.99.144) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 27 Sep 2012 22:28:22 +0000 Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.tripwire.com (Proprietary) with SMTP id 792532321222 for ; Thu, 27 Sep 2012 15:23:07 -0700 (PDT) Received: from PDXED01.tripwire.com (unknown [192.168.192.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by zgw01.tripwire.com (Proprietary) with ESMTPS id D617C23211EA; Thu, 27 Sep 2012 15:23:06 -0700 (PDT) Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.379.0; Thu, 27 Sep 2012 15:31:27 -0700 Received: from PDXMB02.tripwire.com ([fe80::f997:7b65:8e64:438e]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0379.000; Thu, 27 Sep 2012 15:28:20 -0700 From: Adam Montville To: "Moriarty, Kathleen" , "mile@ietf.org" Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gCJ9WXOAAJnqAA== Date: Thu, 27 Sep 2012 22:28:19 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [172.30.0.234] x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f Content-Type: text/plain; charset="us-ascii" Content-ID: <27F8AB68B102EF4CA21FC47592F7DC2B@tripwire.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-VPM-MSG-ID: a5fccd56-36b7-4105-ab8f-89cc5c2f0e11 X-VPM-HOST: zgw01.tripwire.com X-VPM-ENC-REGIME: Plaintext X-VPM-CERT-FLAG: 0 X-VPM-IS-HYBRID: 0 X-OriginatorOrg: tripwire.com Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2012 22:28:27 -0000 On 9/27/12 6:17 AM, "Moriarty, Kathleen" wrote: >Adam & MILE members, > >I read through the draft and think it looks great! I did notice that the >identifier format after the id: is not specified. An example is >provided, but am wondering if it would be helpful to provide an explicit >format to help developers when formatting and parsing the content. > >Any thoughts - Adam or others on the MILE list? Kathleen, thanks for reviewing the specification. I think there's a misunderstanding. I'm looking at the id_type:id item described in 2.1. The id in that item *is* the identifier, and it's format should be explicitly defined by a document or available specification that would be attainable from the registry (Specification URI). Does that help or are we talking about two different things? Adam > >Thank you! >Kathleen >________________________________________ >From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of >Moriarty, Kathleen [kathleen.moriarty@emc.com] >Sent: Wednesday, September 05, 2012 10:35 AM >To: Adam Montville; mile@ietf.org >Subject: Re: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >Adam, > >Thank you very much for your work on this draft! > >MILE members: Please review and comment on the draft. > >Thank you! >Kathleen >________________________________________ >From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam >Montville [amontville@tripwire.com] >Sent: Saturday, September 01, 2012 9:54 AM >To: mile@ietf.org >Subject: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >On 9/1/12 6:46 AM, "internet-drafts@ietf.org" >wrote: > >> >>A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >>has been successfully submitted by Adam W. Montville and posted to the >>IETF repository. >> >>Filename: draft-montville-mile-enum-reference-format >>Revision: 00 >>Title: IODEF Enumeration Reference Format >>Creation date: 2012-09-01 >>WG ID: Individual Submission >>Number of pages: 6 >>URL: >>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-f >>o >>rmat-00.txt >>Status: >>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-forma >>t >>Htmlized: >>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 >> >> >>Abstract: >> Some standards, such as the Incident Object Description Exchange >> Format [IODEF], provide classes used to reference external entities >> (such as enumeration identifiers). At the time of standardization, >> however, needed references may not be known, and the method of >> external entity identification is often left unstructured. This >> document describes, using [IODEF] as an example, a method to provide >> structure after the fact. >> >> >> >> >> >> >>The IETF Secretariat >> >> >> > > > > >_______________________________________________ >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 kathleen.moriarty@emc.com Fri Sep 28 06:23:48 2012 Return-Path: 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 53C7521F8471 for ; Fri, 28 Sep 2012 06:23:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.417 X-Spam-Level: X-Spam-Status: No, score=-2.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0kIvQl5Gdyg for ; Fri, 28 Sep 2012 06:23:47 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 82C7921F8523 for ; Fri, 28 Sep 2012 06:23:43 -0700 (PDT) Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8SDNfeB006126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2012 09:23:42 -0400 Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 28 Sep 2012 09:23:27 -0400 Received: from mxhub19.corp.emc.com (mxhub19.corp.emc.com [10.254.93.48]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8SDNQai018521; Fri, 28 Sep 2012 09:23:26 -0400 Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub19.corp.emc.com ([10.254.93.48]) with mapi; Fri, 28 Sep 2012 09:23:26 -0400 From: "Moriarty, Kathleen" To: Adam Montville , "mile@ietf.org" Date: Fri, 28 Sep 2012 09:19:39 -0400 Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gCJ9WXOAAJnqAIAA+QtL Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EMM-MHVC: 1 Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 13:23:48 -0000 Hi Adam, I am sorry for the confusion! I was referring to the full value contained = in the "ReferenceName". The example shows: CXI:CXI-1234-XYZ http://cxi.example.com Foo Information in the IANA table (see Section 4) would include: Name: Concept X Identifier Version: x.y Specification URI: http://cxi.example.com/spec_url Reference: Foo. How would you get from the IANA table entry to what is included in the exam= ple? The name gets abbreviated. Is the version part of the name and a n= ew version would be a new name? How is the structure after the colon forme= d? What characters are permitted. Thank you, Kathleen ________________________________________ From: Adam Montville [amontville@tripwire.com] Sent: Thursday, September 27, 2012 6:28 PM To: Moriarty, Kathleen; mile@ietf.org Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-e= num-reference-format-00.txt On 9/27/12 6:17 AM, "Moriarty, Kathleen" wrote: >Adam & MILE members, > >I read through the draft and think it looks great! I did notice that the >identifier format after the id: is not specified. An example is >provided, but am wondering if it would be helpful to provide an explicit >format to help developers when formatting and parsing the content. > >Any thoughts - Adam or others on the MILE list? Kathleen, thanks for reviewing the specification. I think there's a misunderstanding. I'm looking at the id_type:id item described in 2.1. The id in that item *is* the identifier, and it's format should be explicitly defined by a document or available specification that would be attainable from the registry (Specification URI). Does that help or are we talking about two different things? Adam > >Thank you! >Kathleen >________________________________________ >From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of >Moriarty, Kathleen [kathleen.moriarty@emc.com] >Sent: Wednesday, September 05, 2012 10:35 AM >To: Adam Montville; mile@ietf.org >Subject: Re: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >Adam, > >Thank you very much for your work on this draft! > >MILE members: Please review and comment on the draft. > >Thank you! >Kathleen >________________________________________ >From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam >Montville [amontville@tripwire.com] >Sent: Saturday, September 01, 2012 9:54 AM >To: mile@ietf.org >Subject: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >On 9/1/12 6:46 AM, "internet-drafts@ietf.org" >wrote: > >> >>A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >>has been successfully submitted by Adam W. Montville and posted to the >>IETF repository. >> >>Filename: draft-montville-mile-enum-reference-format >>Revision: 00 >>Title: IODEF Enumeration Reference Format >>Creation date: 2012-09-01 >>WG ID: Individual Submission >>Number of pages: 6 >>URL: >>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference-f >>o >>rmat-00.txt >>Status: >>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-forma >>t >>Htmlized: >>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 >> >> >>Abstract: >> Some standards, such as the Incident Object Description Exchange >> Format [IODEF], provide classes used to reference external entities >> (such as enumeration identifiers). At the time of standardization, >> however, needed references may not be known, and the method of >> external entity identification is often left unstructured. This >> document describes, using [IODEF] as an example, a method to provide >> structure after the fact. >> >> >> >> >> >> >>The IETF Secretariat >> >> >> > > > > >_______________________________________________ >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 amontville@tripwire.com Fri Sep 28 06:31:28 2012 Return-Path: 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 1F73321F8504 for ; Fri, 28 Sep 2012 06:31:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.704 X-Spam-Level: X-Spam-Status: No, score=-3.704 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Txn1ogmR4VYU for ; Fri, 28 Sep 2012 06:31:27 -0700 (PDT) Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id DC50021F84FD for ; Fri, 28 Sep 2012 06:31:26 -0700 (PDT) Received: from mail106-ch1-R.bigfish.com (10.43.68.234) by CH1EHSOBE011.bigfish.com (10.43.70.61) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Sep 2012 13:31:25 +0000 Received: from mail106-ch1 (localhost [127.0.0.1]) by mail106-ch1-R.bigfish.com (Postfix) with ESMTP id ADA711401B6 for ; Fri, 28 Sep 2012 13:31:25 +0000 (UTC) X-Forefront-Antispam-Report: CIP:174.47.84.215; KIP:(null); UIP:(null); IPV:NLI; H:zgw01.tripwire.com; RD:174-47-84-215.static.twtelecom.net; EFVD:NLI X-SpamScore: -32 X-BigFish: VPS-32(zzbb2dI98dI9371I936eI148cI1432I11f6N111aId6f1izz1202h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h944he5bhf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1155h) Received: from mail106-ch1 (localhost.localdomain [127.0.0.1]) by mail106-ch1 (MessageSwitch) id 1348839083673576_31464; Fri, 28 Sep 2012 13:31:23 +0000 (UTC) Received: from CH1EHSMHS009.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.250]) by mail106-ch1.bigfish.com (Postfix) with ESMTP id A1FF62400B7 for ; Fri, 28 Sep 2012 13:31:23 +0000 (UTC) Received: from zgw01.tripwire.com (174.47.84.215) by CH1EHSMHS009.bigfish.com (10.43.70.9) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Sep 2012 13:31:22 +0000 Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.tripwire.com (Proprietary) with SMTP id 20A632321242 for ; Fri, 28 Sep 2012 06:26:04 -0700 (PDT) Received: from PDXED01.tripwire.com (unknown [192.168.192.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by zgw01.tripwire.com (Proprietary) with ESMTPS id 7D45123211DE; Fri, 28 Sep 2012 06:26:03 -0700 (PDT) Received: from PDXHB01.tripwire.com (172.30.0.53) by PDXED01.tripwire.com (192.168.192.5) with Microsoft SMTP Server (TLS) id 14.1.379.0; Fri, 28 Sep 2012 06:34:26 -0700 Received: from PDXMB02.tripwire.com ([fe80::f997:7b65:8e64:438e]) by PDXHB01.tripwire.com ([fe80::d495:98d2:7df4:2154%11]) with mapi id 14.01.0379.000; Fri, 28 Sep 2012 06:31:20 -0700 From: Adam Montville To: "Moriarty, Kathleen" , "mile@ietf.org" Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gCJ9WXOAAJnqAIAA+QtLgAADRQA= Date: Fri, 28 Sep 2012 13:31:19 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [172.30.0.234] x-exclaimer-md-config: 79afcaa7-fdf4-4fa6-abe0-afeaa4640a4f Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-VPM-MSG-ID: 97462ec6-5518-42cc-a5a7-ae8ca68cb958 X-VPM-HOST: zgw01.tripwire.com X-VPM-ENC-REGIME: Plaintext X-VPM-CERT-FLAG: 0 X-VPM-IS-HYBRID: 0 X-OriginatorOrg: tripwire.com Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 13:31:28 -0000 On 9/28/12 6:19 AM, "Moriarty, Kathleen" wrote: >Hi Adam, > >I am sorry for the confusion! I was referring to the full value >contained in the "ReferenceName". That makes more sense to me, sorry. This is a great point, Kathleen. >The example shows: > > > CXI:CXI-1234-XYZ > http://cxi.example.com > Foo > > > Information in the IANA table (see Section 4) would include: > > Name: Concept X Identifier > Version: x.y > Specification URI: http://cxi.example.com/spec_url > Reference: Foo. > > >How would you get from the IANA table entry to what is included in the >example? The name gets abbreviated. Is the version part of the name >and a new version would be a new name? How is the structure after the >colon formed? What characters are permitted. I think I was taking the "Name" in the IANA table to be the identifier, rather than the full name (so, for example, "CPE" rather than "Common Platform Enumeration"). So, we could simply add an abbreviation to the IANA table, where the abbreviation would consist of lowercase alphabetical characters for the type identifier ("CXI" in the example above). The character limitations should be none, such that this method would not encumber any enumeration specification. That said, I think it would be reasonable to make it alphanumeric with some punctuation (but I'd like to hear from the list as to what they think) - so essentially a string with some character restrictions. As I mention above, I'd really like to hear from others on the list as to what they feel is best. Thanks again for pointing this out. > > >Thank you, >Kathleen > >________________________________________ >From: Adam Montville [amontville@tripwire.com] >Sent: Thursday, September 27, 2012 6:28 PM >To: Moriarty, Kathleen; mile@ietf.org >Subject: Re: [mile] FW: New Version Notification for >draft-montville-mile-enum-reference-format-00.txt > >On 9/27/12 6:17 AM, "Moriarty, Kathleen" >wrote: > >>Adam & MILE members, >> >>I read through the draft and think it looks great! I did notice that the >>identifier format after the id: is not specified. An example is >>provided, but am wondering if it would be helpful to provide an explicit >>format to help developers when formatting and parsing the content. >> >>Any thoughts - Adam or others on the MILE list? > > >Kathleen, thanks for reviewing the specification. I think there's a >misunderstanding. I'm looking at the id_type:id item described in 2.1. >The id in that item *is* the identifier, and it's format should be >explicitly defined by a document or available specification that would be >attainable from the registry (Specification URI). > >Does that help or are we talking about two different things? > >Adam > > >> >>Thank you! >>Kathleen >>________________________________________ >>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of >>Moriarty, Kathleen [kathleen.moriarty@emc.com] >>Sent: Wednesday, September 05, 2012 10:35 AM >>To: Adam Montville; mile@ietf.org >>Subject: Re: [mile] FW: New Version Notification for >>draft-montville-mile-enum-reference-format-00.txt >> >>Adam, >> >>Thank you very much for your work on this draft! >> >>MILE members: Please review and comment on the draft. >> >>Thank you! >>Kathleen >>________________________________________ >>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam >>Montville [amontville@tripwire.com] >>Sent: Saturday, September 01, 2012 9:54 AM >>To: mile@ietf.org >>Subject: [mile] FW: New Version Notification for >>draft-montville-mile-enum-reference-format-00.txt >> >>On 9/1/12 6:46 AM, "internet-drafts@ietf.org" >>wrote: >> >>> >>>A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >>>has been successfully submitted by Adam W. Montville and posted to the >>>IETF repository. >>> >>>Filename: draft-montville-mile-enum-reference-format >>>Revision: 00 >>>Title: IODEF Enumeration Reference Format >>>Creation date: 2012-09-01 >>>WG ID: Individual Submission >>>Number of pages: 6 >>>URL: >>>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference- >>>f >>>o >>>rmat-00.txt >>>Status: >>>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-form >>>a >>>t >>>Htmlized: >>>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-00 >>> >>> >>>Abstract: >>> Some standards, such as the Incident Object Description Exchange >>> Format [IODEF], provide classes used to reference external entities >>> (such as enumeration identifiers). At the time of standardization, >>> however, needed references may not be known, and the method of >>> external entity identification is often left unstructured. This >>> document describes, using [IODEF] as an example, a method to provide >>> structure after the fact. >>> >>> >>> >>> >>> >>> >>>The IETF Secretariat >>> >>> >>> >> >> >> >> >>_______________________________________________ >>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 jhowie@cloudsecurityalliance.org Fri Sep 28 10:00:35 2012 Return-Path: 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 6D75D21F8534 for ; Fri, 28 Sep 2012 10:00:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_FORM=2.3, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2Q-EITr4Mve for ; Fri, 28 Sep 2012 10:00:34 -0700 (PDT) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id AA4A421F84EB for ; Fri, 28 Sep 2012 10:00:34 -0700 (PDT) Received: by pbbro8 with SMTP id ro8so5419804pbb.31 for ; Fri, 28 Sep 2012 10:00:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=user-agent:date:subject:from:to:message-id:thread-topic:in-reply-to :mime-version:content-type:content-transfer-encoding :x-gm-message-state; bh=5LlFlb+KTUUW8/hh1JyqwewwO2qJJO20IDA4C5DYhD4=; b=iLdhFVUSTWAGfhiTvQ+g+TslOEVfhPRLPMZxRrjGZ5HwedexJEGuhUtAHfTKXc04od fDC89lfANouL4UlCxwPnBJ2Ddc1sp5KJk3I+AQzCPAr+o6WFWf69MAThApACLD7+00IN U7CSXQwqwaoGifNVmbXhFvZBw/H5D34GEFpJI5nfjcLYCNavzW7fC8QxQ6JdE7h4h6oQ qKiO8Rwd0+lXLGzGbGkSnn1K4Q2IAUYpPnQQaOz/p7sciKV/hKa2oDgIOw5ngkQL9Sow bzNhLV+aktPBqA4CTebzm+wpeVWnVkbbe1kz+LtJlsT3KmwfDxqHTVUZLiQLhu3bLlPp 1rpQ== Received: by 10.68.239.5 with SMTP id vo5mr21753386pbc.102.1348851634046; Fri, 28 Sep 2012 10:00:34 -0700 (PDT) Received: from [192.168.1.42] (c-67-170-52-163.hsd1.wa.comcast.net. [67.170.52.163]) by mx.google.com with ESMTPS id gj9sm5859689pbc.16.2012.09.28.10.00.31 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Sep 2012 10:00:33 -0700 (PDT) User-Agent: Microsoft-MacOutlook/14.2.4.120824 Date: Fri, 28 Sep 2012 10:00:26 -0700 From: John Howie To: Adam Montville , "Moriarty, Kathleen" , "mile@ietf.org" Message-ID: Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Gm-Message-State: ALoCoQlFUxWLJzxMsZH1R5Kea4AAGNBb7/wlKXDxTGIZ2F8ToNIYodTf0Qm5DFpMHFEOkt5EdEaW Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 17:00:35 -0000 Hi all, DISCLAIMER: This is a personal observation here, and not necessarily endorsed by the organization I work for. I think I have reached a tipping point with respect to a key direction this and other efforts (both related and unrelated) are taking. Can we please have a discussion about the suitability of HTTP/HTTPS/XML for this type of information exchange. The HTTP/HTTPS protocol was never designed for this type of data exchange, and is a wordy, fat protocol that consumes a heck of a lot of bandwidth. If you are exchanging just a few bytes of data the protocol overhead can dwarf the actual meaningful data being exchanged, especially when using HTTPS and authentication. The packet exchanges between client and server are numerous before even a byte of meaningful data is exchanged. XML just makes the situation worse. In the example below we are exchanging 177 characters with only 44 characters actually being meaningful. There are better options such as JSON. The overhead in parsing XML is a real problem, and, let's face it, different implementations of XML generators and parsers often cause compatibility issues even before versioning is factored in. When we use HTTP/HTTPS/XML we also use, by necessity, web servers and XML parsers and a cursory look as US-CERT and other notification lists shows that these are hardly vulnerability free, and we are simply building a potentially critical infrastructure on commodity components that are the cause of many security and privacy issues today. I would really like to see information exchange be secure, fast and lightweight, and a new protocol could well be preferable here. Regards, John On 9/28/12 6:31 AM, "Adam Montville" wrote: >On 9/28/12 6:19 AM, "Moriarty, Kathleen" >wrote: > >>Hi Adam, >> >>I am sorry for the confusion! I was referring to the full value >>contained in the "ReferenceName". > >That makes more sense to me, sorry. This is a great point, Kathleen. > >>The example shows: >> >> >> CXI:CXI-1234-XYZ >> http://cxi.example.com >> Foo >> >> >> Information in the IANA table (see Section 4) would include: >> >> Name: Concept X Identifier >> Version: x.y >> Specification URI: http://cxi.example.com/spec_url >> Reference: Foo. >> >> >>How would you get from the IANA table entry to what is included in the >>example? The name gets abbreviated. Is the version part of the name >>and a new version would be a new name? How is the structure after the >>colon formed? What characters are permitted. > > >I think I was taking the "Name" in the IANA table to be the identifier, >rather than the full name (so, for example, "CPE" rather than "Common >Platform Enumeration"). So, we could simply add an abbreviation to the >IANA table, where the abbreviation would consist of lowercase alphabetical >characters for the type identifier ("CXI" in the example above). > > >The character limitations should be none, such that this method would not >encumber any enumeration specification. That said, I think it would be >reasonable to make it alphanumeric with some punctuation (but I'd like to >hear from the list as to what they think) - so essentially a string with >some character restrictions. > >As I mention above, I'd really like to hear from others on the list as to >what they feel is best. > >Thanks again for pointing this out. > > >> >> >>Thank you, >>Kathleen >> >>________________________________________ >>From: Adam Montville [amontville@tripwire.com] >>Sent: Thursday, September 27, 2012 6:28 PM >>To: Moriarty, Kathleen; mile@ietf.org >>Subject: Re: [mile] FW: New Version Notification for >>draft-montville-mile-enum-reference-format-00.txt >> >>On 9/27/12 6:17 AM, "Moriarty, Kathleen" >>wrote: >> >>>Adam & MILE members, >>> >>>I read through the draft and think it looks great! I did notice that >>>the >>>identifier format after the id: is not specified. An example is >>>provided, but am wondering if it would be helpful to provide an explicit >>>format to help developers when formatting and parsing the content. >>> >>>Any thoughts - Adam or others on the MILE list? >> >> >>Kathleen, thanks for reviewing the specification. I think there's a >>misunderstanding. I'm looking at the id_type:id item described in 2.1. >>The id in that item *is* the identifier, and it's format should be >>explicitly defined by a document or available specification that would be >>attainable from the registry (Specification URI). >> >>Does that help or are we talking about two different things? >> >>Adam >> >> >>> >>>Thank you! >>>Kathleen >>>________________________________________ >>>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of >>>Moriarty, Kathleen [kathleen.moriarty@emc.com] >>>Sent: Wednesday, September 05, 2012 10:35 AM >>>To: Adam Montville; mile@ietf.org >>>Subject: Re: [mile] FW: New Version Notification for >>>draft-montville-mile-enum-reference-format-00.txt >>> >>>Adam, >>> >>>Thank you very much for your work on this draft! >>> >>>MILE members: Please review and comment on the draft. >>> >>>Thank you! >>>Kathleen >>>________________________________________ >>>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam >>>Montville [amontville@tripwire.com] >>>Sent: Saturday, September 01, 2012 9:54 AM >>>To: mile@ietf.org >>>Subject: [mile] FW: New Version Notification for >>>draft-montville-mile-enum-reference-format-00.txt >>> >>>On 9/1/12 6:46 AM, "internet-drafts@ietf.org" >>>wrote: >>> >>>> >>>>A new version of I-D, draft-montville-mile-enum-reference-format-00.txt >>>>has been successfully submitted by Adam W. Montville and posted to the >>>>IETF repository. >>>> >>>>Filename: draft-montville-mile-enum-reference-format >>>>Revision: 00 >>>>Title: IODEF Enumeration Reference Format >>>>Creation date: 2012-09-01 >>>>WG ID: Individual Submission >>>>Number of pages: 6 >>>>URL: >>>>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference >>>>- >>>>f >>>>o >>>>rmat-00.txt >>>>Status: >>>>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-for >>>>m >>>>a >>>>t >>>>Htmlized: >>>>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-0 >>>>0 >>>> >>>> >>>>Abstract: >>>> Some standards, such as the Incident Object Description Exchange >>>> Format [IODEF], provide classes used to reference external entities >>>> (such as enumeration identifiers). At the time of standardization, >>>> however, needed references may not be known, and the method of >>>> external entity identification is often left unstructured. This >>>> document describes, using [IODEF] as an example, a method to provide >>>> structure after the fact. >>>> >>>> >>>> >>>> >>>> >>>> >>>>The IETF Secretariat >>>> >>>> >>>> >>> >>> >>> >>> >>>_______________________________________________ >>>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 stpeter@stpeter.im Fri Sep 28 10:10:10 2012 Return-Path: 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 D610921F8523 for ; Fri, 28 Sep 2012 10:10:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.572 X-Spam-Level: X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqCIF6uXg2Sm for ; Fri, 28 Sep 2012 10:10:08 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5A32D21F8504 for ; Fri, 28 Sep 2012 10:10:08 -0700 (PDT) Received: from [64.101.72.41] (unknown [64.101.72.41]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D908040062; Fri, 28 Sep 2012 11:11:41 -0600 (MDT) Message-ID: <5065D9ED.9020801@stpeter.im> Date: Fri, 28 Sep 2012 11:10:05 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: John Howie References: In-Reply-To: X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "mile@ietf.org" Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 17:10:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/28/12 11:00 AM, John Howie wrote: > I would really like to see information exchange be secure, fast > and lightweight, and a new protocol could well be preferable here. If you didn't have a bias against XML, XMPP would be a good solution to the requirements you've outlined. (With regard to the "bloat" of XML, note that XMPP uses long-lived XML streams so the compression ratios are significant.) Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBl2e0ACgkQNL8k5A2w/vwQ/ACfQ/JoLf08je6WoBkk9A+OpqTo 09wAoOoCRYp1ImSAJMKMWClDKL26qlJ4 =DJzM -----END PGP SIGNATURE----- From trammell@tik.ee.ethz.ch Fri Sep 28 10:36:10 2012 Return-Path: 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 D345C21F84F6 for ; Fri, 28 Sep 2012 10:36:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.099 X-Spam-Level: X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i3wZ-nnvH2cy for ; Fri, 28 Sep 2012 10:36:10 -0700 (PDT) Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 9CED821F846E for ; Fri, 28 Sep 2012 10:36:09 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id B86A7D9309; Fri, 28 Sep 2012 19:36:08 +0200 (MEST) X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id buwdfmfTeWGU; Fri, 28 Sep 2012 19:36:08 +0200 (MEST) Received: from [10.0.27.100] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 31960D9304; Fri, 28 Sep 2012 19:36:08 +0200 (MEST) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Brian Trammell In-Reply-To: Date: Fri, 28 Sep 2012 19:36:07 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <861211C1-36CA-479D-BCD0-AF7F2DE2D699@tik.ee.ethz.ch> References: To: John Howie X-Mailer: Apple Mail (2.1283) Cc: "mile@ietf.org" Subject: Re: [mile] New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 17:36:10 -0000 Hi, John, We can certainly have that discussion. Indeed, RID may be transported = over alternate protocols (that one's easy, just write a document with = the bindings) and the IODEF data model may be represented using = alternate formats as well (this one would take a little more work, but = not much, and we hope to have a 5070bis document soon, so alternate = formats might be on the table for that effort). I'll reserve comment for now on the goodness, badness, or ugliness of = any particular technology or protocol, though I will admit to being a = little skeptical that the solution to vulnerabilities in existing = software is brand new software from scratch implementing a brand new = protocol from scratch, especially if that new protocol needs to provide = security guarantees. Best regards, Brian On Sep 28, 2012, at 7:00 PM, John Howie wrote: > Hi all, >=20 > DISCLAIMER: This is a personal observation here, and not necessarily > endorsed by the organization I work for. >=20 > I think I have reached a tipping point with respect to a key direction > this and other efforts (both related and unrelated) are taking. Can we > please have a discussion about the suitability of HTTP/HTTPS/XML for = this > type of information exchange. >=20 > The HTTP/HTTPS protocol was never designed for this type of data = exchange, > and is a wordy, fat protocol that consumes a heck of a lot of = bandwidth. > If you are exchanging just a few bytes of data the protocol overhead = can > dwarf the actual meaningful data being exchanged, especially when = using > HTTPS and authentication. The packet exchanges between client and = server > are numerous before even a byte of meaningful data is exchanged. >=20 > XML just makes the situation worse. In the example below we are = exchanging > 177 characters with only 44 characters actually being meaningful. = There > are better options such as JSON. The overhead in parsing XML is a real > problem, and, let's face it, different implementations of XML = generators > and parsers often cause compatibility issues even before versioning is > factored in. >=20 > When we use HTTP/HTTPS/XML we also use, by necessity, web servers and = XML > parsers and a cursory look as US-CERT and other notification lists = shows > that these are hardly vulnerability free, and we are simply building a > potentially critical infrastructure on commodity components that are = the > cause of many security and privacy issues today. >=20 > I would really like to see information exchange be secure, fast and > lightweight, and a new protocol could well be preferable here. >=20 > Regards, >=20 > John >=20 >=20 >=20 >=20 > On 9/28/12 6:31 AM, "Adam Montville" wrote: >=20 >> On 9/28/12 6:19 AM, "Moriarty, Kathleen" >> wrote: >>=20 >>> Hi Adam, >>>=20 >>> I am sorry for the confusion! I was referring to the full value >>> contained in the "ReferenceName". >>=20 >> That makes more sense to me, sorry. This is a great point, Kathleen. >>=20 >>> The example shows: >>>=20 >>> >>> CXI:CXI-1234-XYZ >>> http://cxi.example.com >>> Foo >>> >>>=20 >>> Information in the IANA table (see Section 4) would include: >>>=20 >>> Name: Concept X Identifier >>> Version: x.y >>> Specification URI: http://cxi.example.com/spec_url >>> Reference: Foo. >>>=20 >>>=20 >>> How would you get from the IANA table entry to what is included in = the >>> example? The name gets abbreviated. Is the version part of the = name >>> and a new version would be a new name? How is the structure after = the >>> colon formed? What characters are permitted. >>=20 >>=20 >> I think I was taking the "Name" in the IANA table to be the = identifier, >> rather than the full name (so, for example, "CPE" rather than "Common >> Platform Enumeration"). So, we could simply add an abbreviation to = the >> IANA table, where the abbreviation would consist of lowercase = alphabetical >> characters for the type identifier ("CXI" in the example above). >>=20 >>=20 >> The character limitations should be none, such that this method would = not >> encumber any enumeration specification. That said, I think it would = be >> reasonable to make it alphanumeric with some punctuation (but I'd = like to >> hear from the list as to what they think) - so essentially a string = with >> some character restrictions. >>=20 >> As I mention above, I'd really like to hear from others on the list = as to >> what they feel is best. >>=20 >> Thanks again for pointing this out. >>=20 >>=20 >>>=20 >>>=20 >>> Thank you, >>> Kathleen >>>=20 >>> ________________________________________ >>> From: Adam Montville [amontville@tripwire.com] >>> Sent: Thursday, September 27, 2012 6:28 PM >>> To: Moriarty, Kathleen; mile@ietf.org >>> Subject: Re: [mile] FW: New Version Notification for >>> draft-montville-mile-enum-reference-format-00.txt >>>=20 >>> On 9/27/12 6:17 AM, "Moriarty, Kathleen" >>> wrote: >>>=20 >>>> Adam & MILE members, >>>>=20 >>>> I read through the draft and think it looks great! I did notice = that >>>> the >>>> identifier format after the id: is not specified. An example is >>>> provided, but am wondering if it would be helpful to provide an = explicit >>>> format to help developers when formatting and parsing the content. >>>>=20 >>>> Any thoughts - Adam or others on the MILE list? >>>=20 >>>=20 >>> Kathleen, thanks for reviewing the specification. I think there's a >>> misunderstanding. I'm looking at the id_type:id item described in = 2.1. >>> The id in that item *is* the identifier, and it's format should be >>> explicitly defined by a document or available specification that = would be >>> attainable from the registry (Specification URI). >>>=20 >>> Does that help or are we talking about two different things? >>>=20 >>> Adam >>>=20 >>>=20 >>>>=20 >>>> Thank you! >>>> Kathleen >>>> ________________________________________ >>>> From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of >>>> Moriarty, Kathleen [kathleen.moriarty@emc.com] >>>> Sent: Wednesday, September 05, 2012 10:35 AM >>>> To: Adam Montville; mile@ietf.org >>>> Subject: Re: [mile] FW: New Version Notification for >>>> draft-montville-mile-enum-reference-format-00.txt >>>>=20 >>>> Adam, >>>>=20 >>>> Thank you very much for your work on this draft! >>>>=20 >>>> MILE members: Please review and comment on the draft. >>>>=20 >>>> Thank you! >>>> Kathleen >>>> ________________________________________ >>>> From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of = Adam >>>> Montville [amontville@tripwire.com] >>>> Sent: Saturday, September 01, 2012 9:54 AM >>>> To: mile@ietf.org >>>> Subject: [mile] FW: New Version Notification for >>>> draft-montville-mile-enum-reference-format-00.txt >>>>=20 >>>> On 9/1/12 6:46 AM, "internet-drafts@ietf.org" = >>>> wrote: >>>>=20 >>>>>=20 >>>>> A new version of I-D, = draft-montville-mile-enum-reference-format-00.txt >>>>> has been successfully submitted by Adam W. Montville and posted to = the >>>>> IETF repository. >>>>>=20 >>>>> Filename: draft-montville-mile-enum-reference-format >>>>> Revision: 00 >>>>> Title: IODEF Enumeration Reference Format >>>>> Creation date: 2012-09-01 >>>>> WG ID: Individual Submission >>>>> Number of pages: 6 >>>>> URL: >>>>> = http://www.ietf.org/internet-drafts/draft-montville-mile-enum-reference >>>>> - >>>>> f >>>>> o >>>>> rmat-00.txt >>>>> Status: >>>>> = http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-for >>>>> m >>>>> a >>>>> t >>>>> Htmlized: >>>>> = http://tools.ietf.org/html/draft-montville-mile-enum-reference-format-0 >>>>> 0 >>>>>=20 >>>>>=20 >>>>> Abstract: >>>>> Some standards, such as the Incident Object Description Exchange >>>>> Format [IODEF], provide classes used to reference external = entities >>>>> (such as enumeration identifiers). At the time of = standardization, >>>>> however, needed references may not be known, and the method of >>>>> external entity identification is often left unstructured. This >>>>> document describes, using [IODEF] as an example, a method to = provide >>>>> structure after the fact. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> The IETF Secretariat >>>>>=20 >>>>>=20 >>>>>=20 >>>>=20 >>>>=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 >>>>=20 >>>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>=20 >>=20 >>=20 >>=20 >> _______________________________________________ >> mile mailing list >> mile@ietf.org >> https://www.ietf.org/mailman/listinfo/mile >=20 >=20 > _______________________________________________ > mile mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile From stpeter@stpeter.im Fri Sep 28 10:43:09 2012 Return-Path: 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 5C1E621F84FF for ; Fri, 28 Sep 2012 10:43:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.573 X-Spam-Level: X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCVEq62duWaJ for ; Fri, 28 Sep 2012 10:43:08 -0700 (PDT) Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id AD44D21F84F6 for ; Fri, 28 Sep 2012 10:43:08 -0700 (PDT) Received: from [64.101.72.41] (unknown [64.101.72.41]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 37DD440062; Fri, 28 Sep 2012 11:44:43 -0600 (MDT) Message-ID: <5065E1AB.6020206@stpeter.im> Date: Fri, 28 Sep 2012 11:43:07 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Brian Trammell References: <861211C1-36CA-479D-BCD0-AF7F2DE2D699@tik.ee.ethz.ch> In-Reply-To: <861211C1-36CA-479D-BCD0-AF7F2DE2D699@tik.ee.ethz.ch> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "mile@ietf.org" Subject: Re: [mile] New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 17:43:09 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9/28/12 11:36 AM, Brian Trammell wrote: > Hi, John, > > We can certainly have that discussion. Indeed, RID may be > transported over alternate protocols (that one's easy, just write a > document with the bindings) and the IODEF data model may be > represented using alternate formats as well (this one would take a > little more work, but not much, and we hope to have a 5070bis > document soon, so alternate formats might be on the table for that > effort). I'll volunteer to write an XMPP binding for RID, but I can't promise it immediately. > I'll reserve comment for now on the goodness, badness, or ugliness > of any particular technology or protocol, though I will admit to > being a little skeptical that the solution to vulnerabilities in > existing software is brand new software from scratch implementing a > brand new protocol from scratch, especially if that new protocol > needs to provide security guarantees. I tend to agree, which is why using HTTP or XMPP makes sense to me. They are stable technologies that have undergone lots of real-world deployment, intensive security review, etc. Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBl4asACgkQNL8k5A2w/vzLtACeLclzM2JIWwqWqVl9jAUT0a0f piMAoO6wRgVXE8HpOVJyhl00kFhZiyDI =qInl -----END PGP SIGNATURE----- From francis@aspl.es Fri Sep 28 10:45:47 2012 Return-Path: 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 EA1EB21F84F6 for ; Fri, 28 Sep 2012 10:45:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.884 X-Spam-Level: **** X-Spam-Status: No, score=4.884 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, HOST_MISMATCH_NET=0.311] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZCL9MyXlFwH for ; Fri, 28 Sep 2012 10:45:47 -0700 (PDT) Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id 1731121F848B for ; Fri, 28 Sep 2012 10:45:47 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id 43DFF312002; Fri, 28 Sep 2012 19:45:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at aspl.es Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7SrC4G2hg55; Fri, 28 Sep 2012 19:45:44 +0200 (CEST) Received: from [192.168.0.132] (unknown [192.168.0.132]) by mail.aspl.es (Postfix) with ESMTP id 76E7E312001; Fri, 28 Sep 2012 19:45:44 +0200 (CEST) From: Francis Brosnan Blazquez To: Peter Saint-Andre In-Reply-To: <5065D9ED.9020801@stpeter.im> References: <5065D9ED.9020801@stpeter.im> Content-Type: text/plain; charset="ISO-8859-15" Organization: ASPL Date: Fri, 28 Sep 2012 19:45:44 +0200 Message-ID: <1348854344.3622.177.camel@vulcan.aspl.local> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Cc: "mile@ietf.org" Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 17:45:48 -0000 Hi, The working group could also consider BEEP. It is lightweight, extensible and it allows any format for your message (since it sees the payload as a bunch of octets). Specifically, we are using it in a real-time monitoring solution where hundred of nodes are watched and queried, without having to use a polling solutions to get those events... Best Regards, > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 9/28/12 11:00 AM, John Howie wrote: > > > I would really like to see information exchange be secure, fast > > and lightweight, and a new protocol could well be preferable here. > > If you didn't have a bias against XML, XMPP would be a good solution > to the requirements you've outlined. > > (With regard to the "bloat" of XML, note that XMPP uses long-lived XML > streams so the compression ratios are significant.) > > Peter > > - -- > Peter Saint-Andre > https://stpeter.im/ > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > iEYEARECAAYFAlBl2e0ACgkQNL8k5A2w/vwQ/ACfQ/JoLf08je6WoBkk9A+OpqTo > 09wAoOoCRYp1ImSAJMKMWClDKL26qlJ4 > =DJzM > -----END PGP SIGNATURE----- > _______________________________________________ > mile mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile -- Francis Brosnan Blázquez ASPL 91 134 14 22 - 91 134 14 45 - 91 116 07 57 AVISO LEGAL Este mensaje se dirige exclusivamente a su destinatario. Los datos incluidos en el presente correo son confidenciales y sometidos a secreto profesional, se prohíbe divulgarlos, en virtud de las leyes vigentes. Si usted no lo es y lo ha recibido por error o tiene conocimiento del mismo por cualquier motivo, le rogamos que nos lo comunique por este medio y proceda a destruirlo o borrarlo. En virtud de lo dispuesto en la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, le informamos de que sus datos de carácter personal, recogidos de fuentes accesibles al público o datos que usted nos ha facilitado previamente, proceden de bases de datos propiedad de Advanced Software Production Line, S.L. (ASPL). No obstante, usted puede ejercitar sus derechos de acceso, rectificación, cancelación y oposición dispuestos en la mencionada Ley Orgánica, notificándolo por escrito a: ASPL - Protección Datos, C/Antonio Suárez 10 A-102, 28802, Alcalá de Henares (Madrid). From kathleen.moriarty@emc.com Fri Sep 28 11:04:59 2012 Return-Path: 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 BB8D521F84F3 for ; Fri, 28 Sep 2012 11:04:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.365 X-Spam-Level: X-Spam-Status: No, score=-2.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yCxhmLqyb6o for ; Fri, 28 Sep 2012 11:04:59 -0700 (PDT) Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D376E21F852A for ; Fri, 28 Sep 2012 11:04:58 -0700 (PDT) Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8SI4rkb029544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2012 14:04:55 -0400 Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 28 Sep 2012 14:04:42 -0400 Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8SI4eUi007218; Fri, 28 Sep 2012 14:04:40 -0400 Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Fri, 28 Sep 2012 14:04:38 -0400 From: "Moriarty, Kathleen" To: Francis Brosnan Blazquez Date: Fri, 28 Sep 2012 14:04:34 -0400 Thread-Topic: Transport discussion was: New draft notification ... Thread-Index: Ac2do7lx0jtcGuQlTE+/+yBWu6phZw== Message-ID: References: <5065D9ED.9020801@stpeter.im> <1348854344.3622.177.camel@vulcan.aspl.local> In-Reply-To: <1348854344.3622.177.camel@vulcan.aspl.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-EMM-MHVC: 1 Cc: "mile@ietf.org" Subject: [mile] Transport discussion was: New draft notification ... X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 18:04:59 -0000 SW50ZXJlc3RpbmcuLi4gIFJJRCB1c2VkIEJFRVAgaW4gYW4gZWFybGllciB2ZXJzaW9uIGJlY2F1 c2Ugb2YgdGhlIHN1aXRhYmlsaXR5IHRvIHRoZSBwcm90b2NvbCBuZWVkcywgYnV0IGJlY2F1c2Ug b2YgbG93IGRlcGxveW1lbnQgb2YgQkVFUCwgd2Ugc3dpdGNoZWQgdG8gSFRUUFMuDQoNCkkgYW0g Y3VyaW91cyB0byBzZWUgaWYgZGlmZmVyZW50IGV4Y2hhbmdlIHR5cGVzIG1heSB1c2UgZGlmZmVy ZW50IGJpbmRpbmdzLiAgVGhlIFJFU1RmdWwgYmluZGluZyBpbiB0aGUgUk9MSUUgZHJhZnQgbWF5 IGJlIHdlbGwgc3VpdGVkIGZvciByZXBvc2l0b3J5IGFjY2VzcyBhbmQgSU9ERUYgKyBSSUQgKyB0 cmFuc3BvcnQgd2hlcmUgb2JqZWN0IHNlY3VyaXR5IGlzIG5lZWRlZC4gIFdoYXQgYXJlIHRoZSB1 c2UgY2FzZXMgZm9yIGVhY2ggaWYgdGhleSBkaWZmZXIgYW5kIHdoYXQgZG8gZm9sa3MgcHJlZmVy IGFuZCB0aGluayB3aWxsIGhlbHAgYWRvcHRpb24uDQoNCkFzIEJyaWFuIHNhaWQsIG90aGVyIGZv cm1hdHMgYXJlIHBvc3NpYmxlLiAgSU9ERUYgaGFzIGJlZW4gaW1wbGVtZW50ZWQgaW4gSlNPTiBm cm9tIHRoZSBkYXRhIG1vZGVsIGRlc2NyaXB0aW9uIGFscmVhZHkuDQoNCkkgd291bGQgbG92ZSB0 byBzZWUgbW9yZSB2aWV3cyBvbiB0aGlzIGRpc2N1c3Npb24hDQoNClRoYW5rcywNCkthdGhsZWVu DQoNCg0KU2VudCBmcm9tIG15IGlQaG9uZQ0KDQpPbiBTZXAgMjgsIDIwMTIsIGF0IDE6NDYgUE0s ICJGcmFuY2lzIEJyb3NuYW4gQmxhenF1ZXoiIDxmcmFuY2lzQGFzcGwuZXM+IHdyb3RlOg0KDQo+ IEhpLA0KPiANCj4gVGhlIHdvcmtpbmcgZ3JvdXAgY291bGQgYWxzbyBjb25zaWRlciBCRUVQLiBJ dCBpcyBsaWdodHdlaWdodCwNCj4gZXh0ZW5zaWJsZSBhbmQgaXQgYWxsb3dzIGFueSBmb3JtYXQg Zm9yIHlvdXIgbWVzc2FnZSAoc2luY2UgaXQgc2VlcyB0aGUNCj4gcGF5bG9hZCBhcyBhIGJ1bmNo IG9mIG9jdGV0cykuIA0KPiANCj4gU3BlY2lmaWNhbGx5LCB3ZSBhcmUgdXNpbmcgaXQgaW4gYSBy ZWFsLXRpbWUgbW9uaXRvcmluZyBzb2x1dGlvbiB3aGVyZQ0KPiBodW5kcmVkIG9mIG5vZGVzIGFy ZSB3YXRjaGVkIGFuZCBxdWVyaWVkLCB3aXRob3V0IGhhdmluZyB0byB1c2UgYQ0KPiBwb2xsaW5n IHNvbHV0aW9ucyB0byBnZXQgdGhvc2UgZXZlbnRzLi4uDQo+IA0KPiBCZXN0IFJlZ2FyZHMsDQo+ IA0KPj4gLS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KPj4gSGFzaDogU0hBMQ0K Pj4gDQo+PiBPbiA5LzI4LzEyIDExOjAwIEFNLCBKb2huIEhvd2llIHdyb3RlOg0KPj4gDQo+Pj4g SSB3b3VsZCByZWFsbHkgbGlrZSB0byBzZWUgaW5mb3JtYXRpb24gZXhjaGFuZ2UgYmUgc2VjdXJl LCBmYXN0DQo+Pj4gYW5kIGxpZ2h0d2VpZ2h0LCBhbmQgYSBuZXcgcHJvdG9jb2wgY291bGQgd2Vs bCBiZSBwcmVmZXJhYmxlIGhlcmUuDQo+PiANCj4+IElmIHlvdSBkaWRuJ3QgaGF2ZSBhIGJpYXMg YWdhaW5zdCBYTUwsIFhNUFAgd291bGQgYmUgYSBnb29kIHNvbHV0aW9uDQo+PiB0byB0aGUgcmVx dWlyZW1lbnRzIHlvdSd2ZSBvdXRsaW5lZC4NCj4+IA0KPj4gKFdpdGggcmVnYXJkIHRvIHRoZSAi YmxvYXQiIG9mIFhNTCwgbm90ZSB0aGF0IFhNUFAgdXNlcyBsb25nLWxpdmVkIFhNTA0KPj4gc3Ry ZWFtcyBzbyB0aGUgY29tcHJlc3Npb24gcmF0aW9zIGFyZSBzaWduaWZpY2FudC4pDQo+PiANCj4+ IFBldGVyDQo+PiANCj4+IC0gLS0gDQo+PiBQZXRlciBTYWludC1BbmRyZQ0KPj4gaHR0cHM6Ly9z dHBldGVyLmltLw0KPj4gDQo+PiANCj4+IC0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQo+ PiBWZXJzaW9uOiBHbnVQRy9NYWNHUEcyIHYyLjAuMTggKERhcndpbikNCj4+IENvbW1lbnQ6IFVz aW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly93d3cuZW5pZ21haWwubmV0Lw0KPj4gDQo+ PiBpRVlFQVJFQ0FBWUZBbEJsMmUwQUNna1FOTDhrNUEydy92d1EvQUNmUS9Kb0xmMDhqZTZXb0Jr azlBK09wcVRvDQo+PiAwOXdBb09vQ1JZcDFJbVNBSk1LTVdDbERLTDI2cWxKNA0KPj4gPURKek0N Cj4+IC0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0KPj4gX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IG1pbGUgbWFpbGluZyBsaXN0DQo+PiBtaWxl QGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pbGUN Cj4gDQo+IC0tIA0KPiBGcmFuY2lzIEJyb3NuYW4gQmzDoXpxdWV6IDxmcmFuY2lzLmJyb3NuYW5A YXNwbC5lcz4NCj4gQVNQTA0KPiA5MSAxMzQgMTQgMjIgLSA5MSAxMzQgMTQgNDUgLSA5MSAxMTYg MDcgNTcNCj4gDQo+IEFWSVNPIExFR0FMDQo+IA0KPiBFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4 Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBMb3MgZGF0b3MNCj4gaW5jbHVpZG9zIGVu IGVsIHByZXNlbnRlIGNvcnJlbyBzb24gY29uZmlkZW5jaWFsZXMgeSBzb21ldGlkb3MgYSBzZWNy ZXRvDQo+IHByb2Zlc2lvbmFsLCBzZSBwcm9ow61iZSBkaXZ1bGdhcmxvcywgZW4gdmlydHVkIGRl IGxhcyBsZXllcyB2aWdlbnRlcy4gU2kNCj4gdXN0ZWQgbm8gbG8gZXMgeSBsbyBoYSByZWNpYmlk byBwb3IgZXJyb3IgbyB0aWVuZSBjb25vY2ltaWVudG8gZGVsIG1pc21vDQo+IHBvciBjdWFscXVp ZXIgbW90aXZvLCBsZSByb2dhbW9zIHF1ZSBub3MgbG8gY29tdW5pcXVlIHBvciBlc3RlIG1lZGlv IHkNCj4gcHJvY2VkYSBhIGRlc3RydWlybG8gbyBib3JyYXJsby4NCj4gDQo+IEVuIHZpcnR1ZCBk ZSBsbyBkaXNwdWVzdG8gZW4gbGEgTGV5IE9yZ8OhbmljYSAxNS8xOTk5LCBkZSAxMyBkZQ0KPiBk aWNpZW1icmUsIGRlIFByb3RlY2Npw7NuIGRlIERhdG9zIGRlIENhcsOhY3RlciBQZXJzb25hbCwg bGUgaW5mb3JtYW1vcyBkZQ0KPiBxdWUgc3VzIGRhdG9zIGRlIGNhcsOhY3RlciBwZXJzb25hbCwg cmVjb2dpZG9zIGRlIGZ1ZW50ZXMgYWNjZXNpYmxlcyBhbA0KPiBww7pibGljbyBvIGRhdG9zIHF1 ZSB1c3RlZCBub3MgaGEgZmFjaWxpdGFkbyBwcmV2aWFtZW50ZSwgcHJvY2VkZW4gZGUNCj4gYmFz ZXMgZGUgZGF0b3MgcHJvcGllZGFkIGRlIEFkdmFuY2VkIFNvZnR3YXJlIFByb2R1Y3Rpb24gTGlu ZSwgUy5MLg0KPiAoQVNQTCkuIE5vIG9ic3RhbnRlLCB1c3RlZCBwdWVkZSBlamVyY2l0YXIgc3Vz IGRlcmVjaG9zIGRlIGFjY2VzbywNCj4gcmVjdGlmaWNhY2nDs24sIGNhbmNlbGFjacOzbiB5IG9w b3NpY2nDs24gZGlzcHVlc3RvcyBlbiBsYSBtZW5jaW9uYWRhIExleQ0KPiBPcmfDoW5pY2EsIG5v dGlmaWPDoW5kb2xvIHBvciBlc2NyaXRvIGE6DQo+IEFTUEwgLSBQcm90ZWNjacOzbiBEYXRvcywg Qy9BbnRvbmlvIFN1w6FyZXogMTAgQS0xMDIsIDI4ODAyLCBBbGNhbMOhIGRlDQo+IEhlbmFyZXMg KE1hZHJpZCkuDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXw0KPiBtaWxlIG1haWxpbmcgbGlzdA0KPiBtaWxlQGlldGYub3JnDQo+IGh0dHBzOi8v d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWlsZQ0KPiANCg== From pkampana@cisco.com Fri Sep 28 11:15:37 2012 Return-Path: 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 1BFD921F848F for ; Fri, 28 Sep 2012 11:15:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.299 X-Spam-Level: X-Spam-Status: No, score=-8.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_FORM=2.3, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyIp0KupOoeC for ; Fri, 28 Sep 2012 11:15:35 -0700 (PDT) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 56E8B21F842B for ; Fri, 28 Sep 2012 11:15:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6485; q=dns/txt; s=iport; t=1348856135; x=1350065735; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=MXP1wx38wHhO8Z/+FCnCXTfliYimrpXSkYXHGEk7ba8=; b=VqoMVG5gSSfWl1QXJlv+CZn1hxgwA2Hs+S4nZJzKzlQm7TLO9xo3yQ0p 7aSej3v0ZqG69huwh60AfLPUFPVKHUeyMU93IwOxff/fccr6Tl6wk9gZn lLuzurPY4rXMDrbUuKG5QnsJi+Z/1y4prfI/usELYYhJXxO/YHozVQw5B A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAProZVCtJXG9/2dsb2JhbABFvhaBCIIgAQEBBAEBAQ8BJzQJDgQCAQgOAwQBAQsUCQcnCxQIAQgCBAESCAEZh2MLmBaXcog9ixiFR2ADln6KDoMfgWmCZ4IX X-IronPort-AV: E=Sophos;i="4.80,503,1344211200"; d="scan'208";a="126472083" Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 28 Sep 2012 18:15:19 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8SIFJUk009216 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Sep 2012 18:15:19 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.216]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0298.004; Fri, 28 Sep 2012 13:15:18 -0500 From: "Panos Kampanakis (pkampana)" To: Adam Montville , "Moriarty, Kathleen" , "mile@ietf.org" Thread-Topic: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt Thread-Index: AQHNiElIw5oJvf8NrEC0oPQmVUmvWZd71vP1gCJ9WXOAAJnqAIAA+QtLgAADRQCAAE01gA== Date: Fri, 28 Sep 2012 18:15:18 +0000 Message-ID: <1C9F17D1873AFA47A969C4DD98F98A750742D6@xmb-rcd-x10.cisco.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [64.102.89.103] x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19216.004 x-tm-as-result: No--52.425500-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 18:15:37 -0000 Defining the abbreviation to be used in the name of the reference (before t= he ":") in the IANA table that has the reference entries seems like a simpl= e and good idea. As for the character restriction of the ID after the ":", I think a restric= tion like [A-Za-z0-9_\-\.]+ would cover all cases, or at least that is what= I think. Panos -----Original Message----- From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Ada= m Montville Sent: Friday, September 28, 2012 9:31 AM To: Moriarty, Kathleen; mile@ietf.org Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-e= num-reference-format-00.txt On 9/28/12 6:19 AM, "Moriarty, Kathleen" wrote: >Hi Adam, > >I am sorry for the confusion! I was referring to the full value=20 >contained in the "ReferenceName". That makes more sense to me, sorry. This is a great point, Kathleen. >The example shows: > > > CXI:CXI-1234-XYZ > http://cxi.example.com > Foo > > > Information in the IANA table (see Section 4) would include: > > Name: Concept X Identifier > Version: x.y > Specification URI: http://cxi.example.com/spec_url > Reference: Foo. > > >How would you get from the IANA table entry to what is included in the >example? The name gets abbreviated. Is the version part of the name >and a new version would be a new name? How is the structure after the=20 >colon formed? What characters are permitted. I think I was taking the "Name" in the IANA table to be the identifier, rat= her than the full name (so, for example, "CPE" rather than "Common Platform= Enumeration"). So, we could simply add an abbreviation to the IANA table,= where the abbreviation would consist of lowercase alphabetical characters = for the type identifier ("CXI" in the example above). The character limitations should be none, such that this method would not e= ncumber any enumeration specification. That said, I think it would be reas= onable to make it alphanumeric with some punctuation (but I'd like to hear = from the list as to what they think) - so essentially a string with some ch= aracter restrictions. As I mention above, I'd really like to hear from others on the list as to w= hat they feel is best. Thanks again for pointing this out. > > >Thank you, >Kathleen > >________________________________________ >From: Adam Montville [amontville@tripwire.com] >Sent: Thursday, September 27, 2012 6:28 PM >To: Moriarty, Kathleen; mile@ietf.org >Subject: Re: [mile] FW: New Version Notification for=20 >draft-montville-mile-enum-reference-format-00.txt > >On 9/27/12 6:17 AM, "Moriarty, Kathleen" >wrote: > >>Adam & MILE members, >> >>I read through the draft and think it looks great! I did notice that=20 >>the identifier format after the id: is not specified. An example is=20 >>provided, but am wondering if it would be helpful to provide an=20 >>explicit format to help developers when formatting and parsing the conten= t. >> >>Any thoughts - Adam or others on the MILE list? > > >Kathleen, thanks for reviewing the specification. I think there's a=20 >misunderstanding. I'm looking at the id_type:id item described in 2.1. >The id in that item *is* the identifier, and it's format should be=20 >explicitly defined by a document or available specification that would=20 >be attainable from the registry (Specification URI). > >Does that help or are we talking about two different things? > >Adam > > >> >>Thank you! >>Kathleen >>________________________________________ >>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of=20 >>Moriarty, Kathleen [kathleen.moriarty@emc.com] >>Sent: Wednesday, September 05, 2012 10:35 AM >>To: Adam Montville; mile@ietf.org >>Subject: Re: [mile] FW: New Version Notification for=20 >>draft-montville-mile-enum-reference-format-00.txt >> >>Adam, >> >>Thank you very much for your work on this draft! >> >>MILE members: Please review and comment on the draft. >> >>Thank you! >>Kathleen >>________________________________________ >>From: mile-bounces@ietf.org [mile-bounces@ietf.org] On Behalf Of Adam=20 >>Montville [amontville@tripwire.com] >>Sent: Saturday, September 01, 2012 9:54 AM >>To: mile@ietf.org >>Subject: [mile] FW: New Version Notification for=20 >>draft-montville-mile-enum-reference-format-00.txt >> >>On 9/1/12 6:46 AM, "internet-drafts@ietf.org"=20 >> >>wrote: >> >>> >>>A new version of I-D,=20 >>>draft-montville-mile-enum-reference-format-00.txt >>>has been successfully submitted by Adam W. Montville and posted to=20 >>>the IETF repository. >>> >>>Filename: draft-montville-mile-enum-reference-format >>>Revision: 00 >>>Title: IODEF Enumeration Reference Format >>>Creation date: 2012-09-01 >>>WG ID: Individual Submission >>>Number of pages: 6 >>>URL: >>>http://www.ietf.org/internet-drafts/draft-montville-mile-enum-referen >>>ce- >>>f >>>o >>>rmat-00.txt >>>Status: >>>http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-f >>>orm >>>a >>>t >>>Htmlized: >>>http://tools.ietf.org/html/draft-montville-mile-enum-reference-format >>>-00 >>> >>> >>>Abstract: >>> Some standards, such as the Incident Object Description Exchange >>> Format [IODEF], provide classes used to reference external entities >>> (such as enumeration identifiers). At the time of standardization, >>> however, needed references may not be known, and the method of >>> external entity identification is often left unstructured. This >>> document describes, using [IODEF] as an example, a method to provide >>> structure after the fact. >>> >>> >>> >>> >>> >>> >>>The IETF Secretariat >>> >>> >>> >> >> >> >> >>_______________________________________________ >>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 francis@aspl.es Fri Sep 28 11:36:54 2012 Return-Path: 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 B49C721F84F2 for ; Fri, 28 Sep 2012 11:36:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.584 X-Spam-Level: ** X-Spam-Status: No, score=2.584 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_ALMOST_IP=1.889, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAR+yfmX206Z for ; Fri, 28 Sep 2012 11:36:53 -0700 (PDT) Received: from mail.aspl.es (196.Red-212-170-101.staticIP.rima-tde.net [212.170.101.196]) by ietfa.amsl.com (Postfix) with ESMTP id 5C40321F84E7 for ; Fri, 28 Sep 2012 11:36:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.aspl.es (Postfix) with ESMTP id 1CF4D312002 for ; Fri, 28 Sep 2012 20:36:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at aspl.es Received: from mail.aspl.es ([127.0.0.1]) by localhost (dolphin.aspl.es [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-k+UFjUh2B7 for ; Fri, 28 Sep 2012 20:36:48 +0200 (CEST) Received: from [192.168.0.153] (unknown [77.227.22.84]) (Authenticated sender: acinom) by mail.aspl.es (Postfix) with ESMTPA id 207D3312001 for ; Fri, 28 Sep 2012 20:36:48 +0200 (CEST) From: Francis Brosnan =?ISO-8859-1?Q?Bl=E1zquez?= To: "mile@ietf.org" In-Reply-To: <1348854344.3622.177.camel@vulcan.aspl.local> References: <5065D9ED.9020801@stpeter.im> <1348854344.3622.177.camel@vulcan.aspl.local> Content-Type: text/plain; charset="ISO-8859-15" Organization: Advanced Software Production Line, S.L. Date: Fri, 28 Sep 2012 20:36:47 +0200 Message-ID: <1348857407.29689.18.camel@tot.local> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [mile] FW: New Version Notification for draft-montville-mile-enum-reference-format-00.txt X-BeenThere: mile@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2012 18:36:54 -0000 Hi, In the case it is required, I'll be glad to define a BEEP profile to transport RID over BEEP. Best Regards, > Hi, > > The working group could also consider BEEP. It is lightweight, > extensible and it allows any format for your message (since it sees the > payload as a bunch of octets). > > Specifically, we are using it in a real-time monitoring solution where > hundred of nodes are watched and queried, without having to use a > polling solutions to get those events... > > Best Regards, > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 9/28/12 11:00 AM, John Howie wrote: > > > > > I would really like to see information exchange be secure, fast > > > and lightweight, and a new protocol could well be preferable here. > > > > If you didn't have a bias against XML, XMPP would be a good solution > > to the requirements you've outlined. > > > > (With regard to the "bloat" of XML, note that XMPP uses long-lived XML > > streams so the compression ratios are significant.) > > > > Peter > > > > - -- > > Peter Saint-Andre > > https://stpeter.im/ > > > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG/MacGPG2 v2.0.18 (Darwin) > > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > > > iEYEARECAAYFAlBl2e0ACgkQNL8k5A2w/vwQ/ACfQ/JoLf08je6WoBkk9A+OpqTo > > 09wAoOoCRYp1ImSAJMKMWClDKL26qlJ4 > > =DJzM > > -----END PGP SIGNATURE----- > > _______________________________________________ > > mile mailing list > > mile@ietf.org > > https://www.ietf.org/mailman/listinfo/mile >