
From nobody Wed Jul  6 17:42:11 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDCE112D114; Wed,  6 Jul 2016 17:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjImTK7Oiwu9; Wed,  6 Jul 2016 17:42:08 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16F5712D145; Wed,  6 Jul 2016 17:42:08 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id d67so1607971vkh.1; Wed, 06 Jul 2016 17:42:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2iDWlBqvNhmGSAIsAWpVJKSKDRZPVg4pvVQotZV0ZQI=; b=kDw357Wt7twEP21ggM2GdSsLPqM3bs6JSFZ7N9F0FkKn9yOSf8XR2DQ7kGVWsPk2LT gqDUpKMgPm2YC3QL+NiDm3yMis74rZrbDz+j7JicNs4qiS/3GuN2NZLEU8QdskuV11km ytTd0mC2pKAJGphTHi+C/kXEYFZX+jGZlU1ATNTmsKr0HIeU+wKcS73LU+YjZuNfRfQf uPklni0j88BEpR5bkbKR7K7tkO7m75wy1bQukcxCMgTXtToAa5M42m8+OjaoXQbM2I6U 2rKZojtmez4bR5SJ0I8OoyF+zShgd+lPm+z5xMbnSLyKpQ30j9AEaKvY8e2f8p3bvDiL wUJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2iDWlBqvNhmGSAIsAWpVJKSKDRZPVg4pvVQotZV0ZQI=; b=j6r2meQMDZSlTk4f9TBLpB8Crt9Y8sssmwZeDwXstRvab41oE3pPq4hoOZrKZZh0sv tt5YOGBX/cMFlTscMFkcoEa/bJkUWfIDFplSoXcPOpiSAwaok3uhHy+l9eEKIWILnL0z 1wRL9rpCKyZ9qHoLfzHaFQH8zxrwxWlPjy7ti22lfPVjL2gCl8Op2hboJiKq5wna7fLJ 0vVuwKi/SRSeLnRx/EOgeY+WLhZz8ASoZJO3PkFKB0A3te+ZccalW2DW+pSdDNCwOuHv X6K3HLInLtUHZ0GnvB7rKi29a+oJahM2E1v18vresxcj0+My0RZ9hztj3nV3y2P58zId kRIQ==
X-Gm-Message-State: ALyK8tLaylFvGo4Dij1kK0pXriDjYc8FekfTV+NVYq1OQvSpJ36TV/dxgdlIN8BePtaW8zFvFszm/nAfXktO6A==
X-Received: by 10.176.6.232 with SMTP id g95mr10804171uag.95.1467852126844; Wed, 06 Jul 2016 17:42:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.37.104 with HTTP; Wed, 6 Jul 2016 17:42:06 -0700 (PDT)
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD976BB9D@marathon>
References: <20160601234150.16188.9970.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F737@marathon> <5750568A.7020302@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD97669C8@marathon> <576C2DDC.8000606@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BA35@marathon> <576D86BE.8010301@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BB9D@marathon>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 6 Jul 2016 20:42:06 -0400
Message-ID: <CAHbuEH6dAvtG=W-ogPqfktaKB-M+y-j5d1hTimvU8jXd0JWhRg@mail.gmail.com>
To: "Roman D. Danyliw" <rdd@cert.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/8iqeiF63XePI8gstUt5y4pl8c2w>
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis@ietf.org" <draft-ietf-mile-rfc5070-bis@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [mile] Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 00:42:10 -0000

Roman,

I'm looking at Stephen's updated discuss and think he may want more on
the confidence surrounding threat actors and that's reasonable.  Can
you look at his updated discuss point and respond?  It would be nice
to wrap this up soon if we can.

Alissa's discuss remains, so we can follow up on that one next.

Thanks,
Kathleen

On Fri, Jun 24, 2016 at 5:04 PM, Roman D. Danyliw <rdd@cert.org> wrote:
> Hi Stephen!
>
>> -----Original Message-----
>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>> Sent: Friday, June 24, 2016 3:15 PM
>> To: Roman D. Danyliw <rdd@cert.org>; The IESG <iesg@ietf.org>
>> Cc: mile@ietf.org; draft-ietf-mile-rfc5070-bis@ietf.org;
>> takeshi_takahashi@nict.go.jp; mile-chairs@ietf.org; mile-
>> chairs@tools.ietf.org
>> Subject: Re: Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with
>> DISCUSS and COMMENT)
>>
>>
>> Hiya,
>>
>> On 24/06/16 19:22, Roman D. Danyliw wrote:
>> >> > TBH, I wonder if the right thing here is to say that documents
>> >> > with ambiguous confidence elements MUST be treated as if the
>> >> > confidence element were omitted.
>> >> >
>> >> > Would that work?
>> > Definitely.  Would this last sentence address your concern:
>> >
>> > "... While the sender of the
>> > document may explicitly convey confidence in the data in a granular
>> > way using the Confidence class, the recipient is free to ignore or
>> > refine this information to make its own assessment.
>> > [start new text]
>> > Ambiguous Confidence elements in a document MUST be ignored by the
>> recipient.
>> > "
>> >
>> > It's a restatement of your suggestion to match the existing style of the text.
>>
>> That'd work for me. I'd word it more like:
>>
>> "Ambiguous Confidence elements (where it is unclear to which of a set
>> of other elements the Confidence element relates) in a document MUST be
>> ignored by the recipient."
>
> -25 was just posted.  It includes the exact text above.
>
> Thanks for your help in improving the draft.
>
> Roman



-- 

Best regards,
Kathleen


From nobody Thu Jul  7 02:42:03 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C2AD12D53A; Thu,  7 Jul 2016 02:42:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160707094202.23662.98754.idtracker@ietfa.amsl.com>
Date: Thu, 07 Jul 2016 02:42:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/lDax9ykS37VkZBtNTeQbkTKjxho>
Cc: mile-chairs@tools.ietf.org, mile-chairs@ietf.org, mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org
Subject: [mile] Stephen Farrell's No Objection on draft-ietf-mile-rfc5070-bis-25: (with COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 09:42:02 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-mile-rfc5070-bis-25: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


Thanks for handling my discuss.

- comments below were on -22, I didn't check if they'd been
addressed or not. (Happy to chat more if that's useful)

- My review is based on [1]
[1]
https://tools.ietf.org/rfcdiff?url1=rfc5070&url2=draft-ietf-mile-rfc5070-bis-22

- "cyber" galore - yuk! Which of the fourteen (14!) uses
of that ill-defined marketing term are useful or even
well defined?  RFC5070 had zero uses of such terms. Why
is it a good plan for us to damage the RFC series via the
use of such marketing nonsense? Someone may answer that
this is accepted in industry these days, and that is
true, but is nonetheless not a good enough reason for us
to assist with the promulgation of anti-scientific
non-concepts. My suggestion is to try s/cyber//g and then
to see what if anything is less clear - perhaps we'll
find that things are more clear. (And yes, it's a bit of
a bugbear of mine:-) The use of "cyber indicator" instead
of just "indicator" in 3.19 is a good example of how that
phrase makes the spec less clear. 

- 2.5.1, does base64 need a reference and aren't there
multiple variants (url-encoded, etc, sorry for being
vague - I have to look that stuff up afresh every time I
need to write code to handle it;-)

- 2.8: So you don't like leap-seconds? It's often good to
be clear if that bit of ABNF is expected to be enforced
along with schema validation or not. 

- 2.12: What about EAI?

- 3.13.1 - is CoA expanded somewhere? (See, I just looked
at the diff:-)

- 3.18.1 - I think it'd be good to refer to the RFC for
wriing down IPv6 addresses and prefixes. I forget it's
number though:-) And who uses ipv6-net-mask? Don't we all
use prefixes?

- 3.21 - the hash and signature data are underspecified.
You could mean any of pgp, smime or dkim. Or you could
mean this is just a crypto binary value and you don't
care about semantics, just pattern matching.

- 4.3 - I also think that recommending schema validation
of input documents is a bad plan. (Even if that was
already in 5070.)

- section 9: defining how to format privacy sensitive
data means that this spec absolutely does introduce
privacy issues.

- 9.1: you could not here the DoS and possible other
attacks (e.g. spoofed .xsd files loaded over port 80)
that follow on from on-line schema

- 9.2: Have there been any cases of people using IODEF
for bad reasons? I mean that e.g. sending info about
attacks or phish emails is good. But using this format to
send information about tracking an individual for
marketing purposes would be bad. Has the latter occurred
though?  (Just wondering, I don't know.) validation.



From nobody Thu Jul  7 02:42:19 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 EF09B12D671; Thu,  7 Jul 2016 02:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level: 
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPdrC2FtsXCl; Thu,  7 Jul 2016 02:42:01 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72BA012B013; Thu,  7 Jul 2016 02:42:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 455EABE38; Thu,  7 Jul 2016 10:41:59 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiryvLaXIGlX; Thu,  7 Jul 2016 10:41:57 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D5A88BE2F; Thu,  7 Jul 2016 10:41:56 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1467884517; bh=gEJewM1mgTdEcNmOpZ+T6DaFArd2W9TIMue+UGioOVg=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=a9wvy2LwIfMmXmFSemNjdwt5N4eSZ2///ScOiw13S5F0GWQD/006GylNm0Jp9nurk n4OQqn5AixNqoyd45dGaJ7mupkn82dPy5ZqY2ok5pbSmynonxvRAYhcC8/x+3iQEHF 5zjcp5QxuphArbValzryhkrFojme8USXIJ9eCH/0=
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "Roman D. Danyliw" <rdd@cert.org>
References: <20160601234150.16188.9970.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F737@marathon> <5750568A.7020302@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD97669C8@marathon> <576C2DDC.8000606@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BA35@marathon> <576D86BE.8010301@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BB9D@marathon> <CAHbuEH6dAvtG=W-ogPqfktaKB-M+y-j5d1hTimvU8jXd0JWhRg@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <577E23E4.90804@cs.tcd.ie>
Date: Thu, 7 Jul 2016 10:41:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAHbuEH6dAvtG=W-ogPqfktaKB-M+y-j5d1hTimvU8jXd0JWhRg@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000300040403070100010800"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/xObJ5pMsBBUWhFl61pP-2nxAPHY>
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis@ietf.org" <draft-ietf-mile-rfc5070-bis@ietf.org>
Subject: Re: [mile] Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 09:42:04 -0000

This is a cryptographically signed message in MIME format.

--------------ms000300040403070100010800
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

Sorry, ball was in my court there. The changes in -25 fix my
issue so I've cleared.

Thanks,
S.

On 07/07/16 01:42, Kathleen Moriarty wrote:
> Roman,
>=20
> I'm looking at Stephen's updated discuss and think he may want more on
> the confidence surrounding threat actors and that's reasonable.  Can
> you look at his updated discuss point and respond?  It would be nice
> to wrap this up soon if we can.
>=20
> Alissa's discuss remains, so we can follow up on that one next.
>=20
> Thanks,
> Kathleen
>=20
> On Fri, Jun 24, 2016 at 5:04 PM, Roman D. Danyliw <rdd@cert.org> wrote:=

>> Hi Stephen!
>>
>>> -----Original Message-----
>>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>>> Sent: Friday, June 24, 2016 3:15 PM
>>> To: Roman D. Danyliw <rdd@cert.org>; The IESG <iesg@ietf.org>
>>> Cc: mile@ietf.org; draft-ietf-mile-rfc5070-bis@ietf.org;
>>> takeshi_takahashi@nict.go.jp; mile-chairs@ietf.org; mile-
>>> chairs@tools.ietf.org
>>> Subject: Re: Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis=
-22: (with
>>> DISCUSS and COMMENT)
>>>
>>>
>>> Hiya,
>>>
>>> On 24/06/16 19:22, Roman D. Danyliw wrote:
>>>>>> TBH, I wonder if the right thing here is to say that documents
>>>>>> with ambiguous confidence elements MUST be treated as if the
>>>>>> confidence element were omitted.
>>>>>>
>>>>>> Would that work?
>>>> Definitely.  Would this last sentence address your concern:
>>>>
>>>> "... While the sender of the
>>>> document may explicitly convey confidence in the data in a granular
>>>> way using the Confidence class, the recipient is free to ignore or
>>>> refine this information to make its own assessment.
>>>> [start new text]
>>>> Ambiguous Confidence elements in a document MUST be ignored by the
>>> recipient.
>>>> "
>>>>
>>>> It's a restatement of your suggestion to match the existing style of=
 the text.
>>>
>>> That'd work for me. I'd word it more like:
>>>
>>> "Ambiguous Confidence elements (where it is unclear to which of a set=

>>> of other elements the Confidence element relates) in a document MUST =
be
>>> ignored by the recipient."
>>
>> -25 was just posted.  It includes the exact text above.
>>
>> Thanks for your help in improving the draft.
>>
>> Roman
>=20
>=20
>=20


--------------ms000300040403070100010800
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA3MDcw
OTQxNTZaMC8GCSqGSIb3DQEJBDEiBCDXFdrJx+afCTt38/pxfZ9voonRJEcpR8ZuMmxMeYKF
YDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQCpdgr19xu481LeJhaOQdmIXnY41qHLSWlZBaNg6UUtE0aHYun0KeIj
G4p4j0D//do+HK5im8WyHWk0ZDccbwaZQcy+hzMkWhEtBBcHs/6Q0Y+NAsYXhceJ4WvVk51e
Yi2NWcOm9RudPmlEViGC9kypxGZ5xWXWQVqNaSasb/GUYx+/tE1USP+XpNVh/kWczY/AdUhQ
l0f3xWReisq3QgCr/ZWAbXwJgd5+x7Oq+jq96AtDhy/cnhfWpmr2LTj61wxs6c/Dtl/tZmO6
3ecutBxfLAqwRHx9fOQ8OrnSZGdOcnTsAIwFtjehtZQ2Pycyqe1MIbabYxi8vdzKJrpKHO6k
AAAAAAAA
--------------ms000300040403070100010800--


From nobody Thu Jul  7 06:24:33 2016
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2047412D7B4; Thu,  7 Jul 2016 06:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tXTMbNo_PPod; Thu,  7 Jul 2016 06:24:23 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F6612D781; Thu,  7 Jul 2016 06:24:15 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id b192so19780674vke.0; Thu, 07 Jul 2016 06:24:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qCkBthP6SxNJr75evnfiZ10zpXsReJsYJZSppxngrwA=; b=0PQNlfyTkTYXUKQlxdnJfWwtTMR8leJ1QMPkzP9b8Yx7khoycTb25ZeLFe6wGCrL2G Zakj8Feg1hqNbQplt22KU9p94+zs9Crv70icus2wfkdEmISFSwD3+a5KmJ/TlRfPD33G YjrjaYOqgbuWoN547bOBFFXs4Fab4VW1wRhVYCs5KrcN13ALr/lG6Hg2U8rbr/84lH9m IRKYhXxvN1/XzzR1LbJpLqXbT3u9jxM6C9ZqytelHAsQNGAWYVAIv29G+5mCLmLvdygu lb8R9/Tvc9qzorNGSbCrxzq+32nRdBJVA8d1u5cqUkKFu7gdWuz91/IRx4uUUQo5dOi1 NReg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qCkBthP6SxNJr75evnfiZ10zpXsReJsYJZSppxngrwA=; b=BxeEJNGzCtt86oYT0m22mOhr64DjcZG/Wdjb2wL+8sVY30XW/SA2HWWxOHii/85rUB Z35V+d7iIfia8O/ZJkG7Vu3OaEKJ47Iwc2fuhqftR4ha2erDSgpvmClIiFC9cKRW/xW8 OaNt2e/F5WzmplXgkFBbJt7iTDDWwMvH/hNPq9HL28t43tAQi3OWwkT7kpQE2dnK/XUn N9UG2rerJFlIEim8A2iOuNlRthIt18R+4ABbBUTLL9IEWgYYyK8PTZ7/5BIZ/ZSr/h3/ gE95yTCW/qewmu82EbBrsGeO6MfT7CvCoXOF/Sn6a7vhx+3x7HHAX1XmXFgQjEUx0GA6 Tuxw==
X-Gm-Message-State: ALyK8tJSnv3oeFz5sOf9yrZ0MDsIYrAwvUdSn9oB7IYR1Xa2FnFoGP3bcEWBRPZ8ZJG9WwvWDTkga2VAsfsBPg==
X-Received: by 10.176.0.66 with SMTP id 60mr82916uai.15.1467897854186; Thu, 07 Jul 2016 06:24:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.37.104 with HTTP; Thu, 7 Jul 2016 06:24:13 -0700 (PDT)
In-Reply-To: <577E23E4.90804@cs.tcd.ie>
References: <20160601234150.16188.9970.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F737@marathon> <5750568A.7020302@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD97669C8@marathon> <576C2DDC.8000606@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BA35@marathon> <576D86BE.8010301@cs.tcd.ie> <359EC4B99E040048A7131E0F4E113AFCD976BB9D@marathon> <CAHbuEH6dAvtG=W-ogPqfktaKB-M+y-j5d1hTimvU8jXd0JWhRg@mail.gmail.com> <577E23E4.90804@cs.tcd.ie>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 7 Jul 2016 09:24:13 -0400
Message-ID: <CAHbuEH6mHvM_cN=0g9y3EjJswhaCJzA92qcyJedLyrcEnjN23A@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/CipJHk_vgA3ULLwDpnssAynQUms>
Cc: "mile-chairs@tools.ietf.org" <mile-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-rfc5070-bis@ietf.org" <draft-ietf-mile-rfc5070-bis@ietf.org>
Subject: Re: [mile] Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2016 13:24:25 -0000

On Thu, Jul 7, 2016 at 5:41 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>
> Hiya,
>
> Sorry, ball was in my court there. The changes in -25 fix my
> issue so I've cleared.

Great, thanks!
>
> Thanks,
> S.
>
> On 07/07/16 01:42, Kathleen Moriarty wrote:
>> Roman,
>>
>> I'm looking at Stephen's updated discuss and think he may want more on
>> the confidence surrounding threat actors and that's reasonable.  Can
>> you look at his updated discuss point and respond?  It would be nice
>> to wrap this up soon if we can.
>>
>> Alissa's discuss remains, so we can follow up on that one next.
>>
>> Thanks,
>> Kathleen
>>
>> On Fri, Jun 24, 2016 at 5:04 PM, Roman D. Danyliw <rdd@cert.org> wrote:
>>> Hi Stephen!
>>>
>>>> -----Original Message-----
>>>> From: Stephen Farrell [mailto:stephen.farrell@cs.tcd.ie]
>>>> Sent: Friday, June 24, 2016 3:15 PM
>>>> To: Roman D. Danyliw <rdd@cert.org>; The IESG <iesg@ietf.org>
>>>> Cc: mile@ietf.org; draft-ietf-mile-rfc5070-bis@ietf.org;
>>>> takeshi_takahashi@nict.go.jp; mile-chairs@ietf.org; mile-
>>>> chairs@tools.ietf.org
>>>> Subject: Re: Stephen Farrell's Discuss on draft-ietf-mile-rfc5070-bis-22: (with
>>>> DISCUSS and COMMENT)
>>>>
>>>>
>>>> Hiya,
>>>>
>>>> On 24/06/16 19:22, Roman D. Danyliw wrote:
>>>>>>> TBH, I wonder if the right thing here is to say that documents
>>>>>>> with ambiguous confidence elements MUST be treated as if the
>>>>>>> confidence element were omitted.
>>>>>>>
>>>>>>> Would that work?
>>>>> Definitely.  Would this last sentence address your concern:
>>>>>
>>>>> "... While the sender of the
>>>>> document may explicitly convey confidence in the data in a granular
>>>>> way using the Confidence class, the recipient is free to ignore or
>>>>> refine this information to make its own assessment.
>>>>> [start new text]
>>>>> Ambiguous Confidence elements in a document MUST be ignored by the
>>>> recipient.
>>>>> "
>>>>>
>>>>> It's a restatement of your suggestion to match the existing style of the text.
>>>>
>>>> That'd work for me. I'd word it more like:
>>>>
>>>> "Ambiguous Confidence elements (where it is unclear to which of a set
>>>> of other elements the Confidence element relates) in a document MUST be
>>>> ignored by the recipient."
>>>
>>> -25 was just posted.  It includes the exact text above.
>>>
>>> Thanks for your help in improving the draft.
>>>
>>> Roman
>>
>>
>>
>



-- 

Best regards,
Kathleen


From nobody Thu Jul  7 20:43:00 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C9F12D520 for <mile@ietfa.amsl.com>; Thu,  7 Jul 2016 20:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level: 
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KwAh0_NYEXJQ for <mile@ietfa.amsl.com>; Thu,  7 Jul 2016 20:42:57 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF6112B03C for <mile@ietf.org>; Thu,  7 Jul 2016 20:42:57 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id u683gu1N078635 for <mile@ietf.org>; Fri, 8 Jul 2016 12:42:56 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw1.nict.go.jp  with ESMTP id u683guVD078631 for <mile@ietf.org>; Fri, 8 Jul 2016 12:42:56 +0900 (JST)
Received: from VAIO (unknown [133.243.30.149]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTPS id 601B66BC8 for <mile@ietf.org>; Fri,  8 Jul 2016 12:42:56 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Fri, 8 Jul 2016 12:42:57 +0900
Message-ID: <001201d1d8ca$d0f781d0$72e68570$@nict.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AdHYyoYpnqvthIo4TFCjoY2oRFNo3w==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith1
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/KihE80kXVwf6MQc6UC7WbM5gnZ0>
Subject: [mile] MILE session at IETF 96: on the meeting schedule, agenda, volunteer request, and minutes of the previous meeting
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 03:43:00 -0000

Hello all,

The IETF 96 meeting is approaching.
Lots of works have been progressed as you can see in the mailing list,
thanks to the authors.

This email is about the meeting schedule, agenda, volunteer requests, and
the minutes of the previous meeting.

1. meeting schedule

Thursday, July 21, 2016 (GMT+2) 10:00-11:30 (1.5 hours)
Room: Charlottenburg I

2. agenda

If you have any items you wish to present in MILE, please feel free to
contact co-chairs.

Here is the tentative agenda.
https://datatracker.ietf.org/meeting/96/agenda/mile/

3. volunteer request for note take and jabber scribe

We would like to have two note takes and one jabber scribe.
We appreciate your kind volunteers.

4. minutes of the previous meeting

https://www.ietf.org/proceedings/95/minutes/minutes-95-mile
Once again, thank you very much to Chris Inacio and Adam Montville who have
kindly volunteered to be the note take and jabber scribe in Buenos Aires.

Regards,
Take



From nobody Fri Jul  8 10:55:56 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A55E212D56E; Fri,  8 Jul 2016 10:55:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708175550.32205.99575.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 10:55:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/IT6n-fT-5eHWZEPKlPg9Eii2H1I>
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-06.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 17:55:51 -0000

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

        Title           : IODEF Usage Guidance
        Authors         : Panos Kampanakis
                          Mio Suzuki
	Filename        : draft-ietf-mile-iodef-guidance-06.txt
	Pages           : 30
	Date            : 2016-07-08

Abstract:
   The Incident Object Description Exchange Format v2
   [I-D.ietf-mile-rfc5070-bis] defines a data representation that
   provides a framework for sharing information commonly exchanged by
   Computer Security Incident Response Teams (CSIRTs) about computer
   security incidents.  Since the IODEF model includes a wealth of
   available options that can be used to describe a security incident or
   issue, it can be challenging for security practicioners to develop
   tools that can leverage IODEF for incident sharing.  This document
   provides guidelines for IODEF practicioners.  It also addresses how
   common security indicators can be represented in IODEF and use-cases
   of how IODEF is being used so far.  The goal of this document is to
   make IODEF's adoption by vendors easier and encourage faster and
   wider adoption of the model by Computer Security Incident Response
   Teams (CSIRTs) around the world.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-06

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


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

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


From nobody Fri Jul  8 10:56:28 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 60CE712D591; Fri,  8 Jul 2016 10:56:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708175627.32201.61111.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 10:56:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/iRpDqqgA4vFxv7o_Tgj5XQfw7v0>
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rolie-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 17:56:27 -0000

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

        Title           : Resource-Oriented Lightweight Information Exchange
        Authors         : John P. Field
                          Stephen A. Banghart
                          David Waltermire
	Filename        : draft-ietf-mile-rolie-03.txt
	Pages           : 39
	Date            : 2016-07-08

Abstract:
   This document defines a resource-oriented approach for security
   automation information publication, discovery, and sharing.  Using
   this approach, producers may publish, share and exchange
   representations of security incidents, attack indicators, software
   vulnerabilities, configuration checklists, and other security
   automation information as Web-addressable resources.  Furthermore,
   consumers and other stakeholders may access and search this security
   information as needed, establishing a rapid and on-demand information
   exchange network for restricted internal use or public access
   repositories.  This specification extends the Atom Publishing
   Protocol and Atom Syndication Format to transport and share security
   automation resource representations.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mile-rolie-03

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


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

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


From nobody Fri Jul  8 10:56:39 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F4F12D77D; Fri,  8 Jul 2016 10:56:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <mile@ietf.org>, <mile-chairs@tools.ietf.org>, "Nancy Cam-Winget" <ncamwing@cisco.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160708175627.32201.76260.idtracker@ietfa.amsl.com>
Date: Fri, 08 Jul 2016 10:56:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/bXgKjws87T186vjSRgKD2wi4D8k>
Subject: [mile] New Version Notification - draft-ietf-mile-rolie-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 17:56:27 -0000

A new version (-03) has been submitted for draft-ietf-mile-rolie:
https://www.ietf.org/internet-drafts/draft-ietf-mile-rolie-03.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-rolie/

Diff from previous version:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mile-rolie-03

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

IETF Secretariat.


From nobody Tue Jul 19 10:34:49 2016
Return-Path: <pkampana@cisco.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D776712D76F; Tue, 19 Jul 2016 10:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level: 
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4rdpiB4MHSJ; Tue, 19 Jul 2016 10:34:45 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E6F12D74D; Tue, 19 Jul 2016 10:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7580; q=dns/txt; s=iport; t=1468949685; x=1470159285; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=xsIug1Brow4nYRA280h8xX/NOfKd1EVWjkXgmtiREe4=; b=R7GK2ZOdYUymeNY+Gz13Y2pDPdoiknhKp6lKL3zONLFqocIp4MkyFGpG cN8naBs7gdfKvQGFE2ZZuilitGWOWbrQukrrbSzCaITYKqgjhVFBPDsr2 PR2la/56KjTjpXBJ5qsEPZM79CPt6zHXd7pCps48cwAPzV1Tc9S61/aE0 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AuAgCNY45X/4oNJK1dgz9WfAa4ZoF6I?= =?us-ascii?q?oYWgRM4FAEBAQEBAQFlJ4RjHQYRNAMCHgEiAiYCBDAVEQEEARIIiCgOrmuOBQE?= =?us-ascii?q?BAQEBBQEBAQEBAQEbBYEBhSmIaYMlgloFjguLGQGGEohIgXKEWYMvhUSQHQEeN?= =?us-ascii?q?oNzboZhRX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,390,1464652800"; d="scan'208";a="125815069"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jul 2016 17:34:44 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u6JHYiIs002898 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 19 Jul 2016 17:34:44 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 19 Jul 2016 12:34:43 -0500
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1210.000; Tue, 19 Jul 2016 12:34:43 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "sacm@ietf.org" <sacm@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>
Thread-Topic: 3rd ACM Workshop on Information Sharing and Collaborative Security CFP
Thread-Index: AdHh43wukgQtKYQvRu2zAdfJTHNPwAAACEPw
Date: Tue, 19 Jul 2016 17:34:43 +0000
Message-ID: <09426c982ff045549dbe6994c3c5f50f@XCH-ALN-010.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.108.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/rChoBTZ27eCTqopWXxjbSwW6_JU>
Subject: [mile] 3rd ACM Workshop on Information Sharing and Collaborative Security CFP
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2016 17:34:48 -0000

WyBTb3JyeSBmb3IgdGhlIHdpZGUgZGlzdHJpYnV0aW9uIF0NCg0KQ0FMTCBGT1IgUEFQRVJTDQoN
CjNyZCBBQ00gV09SS1NIT1AgT04gSU5GT1JNQVRJT04gU0hBUklORyBBTkQgQ09MTEFCT1JBVElW
RSBTRUNVUklUWSAoV0lTQ1MgMjAxNikgaHR0cHM6Ly9zaXRlcy5nb29nbGUuY29tL3NpdGUvd2lz
Y3MyMDE2Lw0KSGVsZCBpbiBjb25qdW5jdGlvbiB3aXRoIDIzcmQgQUNNIENvbmZlcmVuY2Ugb24g
Q29tcHV0ZXIgYW5kIENvbW11bmljYXRpb25zIFNlY3VyaXR5IChDQ1MpIEhvZmJ1cmcgUGFsYWNl
LCBWaWVubmEsIEF1c3RyaWEgT2N0LiAyNCwgMjAxNg0KDQpERUFETElORSBFWFRFTkRFRCBUTyBB
VUcgMDUsIDIwMTYuDQoNClNoYXJpbmcgb2YgY3liZXItc2VjdXJpdHkgcmVsYXRlZCBpbmZvcm1h
dGlvbiBpcyBiZWxpZXZlZCB0byBncmVhdGx5IGVuaGFuY2UgdGhlIGFiaWxpdHkgb2Ygb3JnYW5p
emF0aW9ucyB0byBkZWZlbmQgdGhlbXNlbHZlcyBhZ2FpbnN0IHNvcGhpc3RpY2F0ZWQgYXR0YWNr
cy4gSWYgb25lIG9yZ2FuaXphdGlvbiBkZXRlY3RzIGEgYnJlYWNoIHNoYXJpbmcgYXNzb2NpYXRl
ZCBzZWN1cml0eSBpbmRpY2F0b3JzIChzdWNoIGFzIGF0dGFja2VyIElQIGFkZHJlc3NlcywgZG9t
YWluIG5hbWVzLCBmaWxlIGhhc2hlcyBldGMuKSBwcm92aWRlcyB2YWx1YWJsZSwgYWN0aW9uYWJs
ZSBpbmZvcm1hdGlvbiB0byBvdGhlciBvcmdhbml6YXRpb25zLiBUaGUgYW5hbHlzaXMgb2Ygc2hh
cmVkIHNlY3VyaXR5IGRhdGEgcHJvbWlzZXMgbm92ZWwgaW5zaWdodHMgaW50byBlbWVyZ2luZyBh
dHRhY2tzLiBTaGFyaW5nIGhpZ2hlciBsZXZlbCBpbnRlbGxpZ2VuY2UgYWJvdXQgdGhyZWF0IGFj
dG9ycywgdGhlIHRvb2xzIHRoZXkgdXNlIGFuZCBtaXRpZ2F0aW9ucyBwcm92aWRlcyBkZWZlbmRl
cnMgd2l0aCBtdWNoIG5lZWRlZCBjb250ZXh0IGZvciBiZXR0ZXIgcHJlcGFyaW5nIGFuZCByZXNw
b25kaW5nIHRvIGF0dGFja3MuIEluIHRoZSBVUyBhbmQgdGhlIEVVIG1ham9yIGVmZm9ydHMgYXJl
IHVuZGVyd2F5IHRvIHN0cmVuZ3RoZW4gaW5mb3JtYXRpb24gc2hhcmluZy4NCg0KWWV0LCB0aGVy
ZSBhcmUgYSBudW1iZXIgb2YgdGVjaG5pY2FsIGFuZCBwb2xpY3kgY2hhbGxlbmdlcyB0byByZWFs
aXppbmcgdGhpcyB2aXNpb24uIFdoaWNoIGluZm9ybWF0aW9uIGV4YWN0bHkgc2hvdWxkIGJlIHNo
YXJlZD8gSG93IGNhbiBwcml2YWN5IGFuZCBjb25maWRlbnRpYWxpdHkgYmUgcHJvdGVjdGVkPyBI
b3cgY2FuIHdlIGNyZWF0ZSBoaWdoLWZpZGVsaXR5IGludGVsbGlnZW5jZSBmcm9tIHNoYXJlZCBk
YXRhIHdpdGhvdXQgZ2V0dGluZyBvdmVyd2hlbG1lZCBieSBmYWxzZSBwb3NpdGl2ZXM/DQoNClRo
ZSAzcmQgV29ya3Nob3Agb24gSW5mb3JtYXRpb24gU2hhcmluZyBhbmQgQ29sbGFib3JhdGl2ZSBT
ZWN1cml0eSAoV0lTQ1MgMjAxNikgYWltcyB0byBicmluZyB0b2dldGhlciBleHBlcnRzIGFuZCBw
cmFjdGl0aW9uZXJzIGZyb20gYWNhZGVtaWEsIGluZHVzdHJ5IGFuZCBnb3Zlcm5tZW50IHRvIHBy
ZXNlbnQgaW5ub3ZhdGl2ZSByZXNlYXJjaCwgY2FzZSBzdHVkaWVzLCBhbmQgbGVnYWwgYW5kIHBv
bGljeSBpc3N1ZXMuIFRoZSB3b3Jrc2hvcCBzb2xpY2l0cyBvcmlnaW5hbCByZXNlYXJjaCBwYXBl
cnMgaW4gdGhlc2UgYXJlYXMsIGJvdGggZnVsbCBhbmQgc2hvcnQgcGFwZXJzLiBXb3Jrc2hvcCBw
cm9jZWVkaW5ncyB3aWxsIGJlIHB1Ymxpc2hlZCBpbiB0aGUgQUNNIERpZ2l0YWwgTGlicmFyeS4N
Cg0KVG9waWNzIG9mIGludGVyZXN0IGZvciB0aGUgd29ya3Nob3AgaW5jbHVkZSwgYnV0IGFyZSBu
b3QgbGltaXRlZCB0bzoNCg0KICAgQ29sbGFib3JhdGl2ZSBpbnRydXNpb24gZGV0ZWN0aW9uDQog
ICBNYWNoaW5lIGxlYXJuaW5nIG9uIHNoYXJlZCBpbmZvcm1hdGlvbg0KICAgQmlnIGRhdGEgZm9y
IGN5YmVyLXNlY3VyaXR5DQogICBDYXNlIHN0dWRpZXMgb2YgaW5mb3JtYXRpb24gc2hhcmluZw0K
ICAgRG9tYWluIG5hbWUgYW5kIElQIGFkZHJlc3MgYmxhY2tsaXN0cw0KICAgQ29sbGFib3JhdGl2
ZSBhcHByb2FjaGVzIHRvIHNwZWFy4oCQcGhpc2hpbmcsIEREb1MgYW5kIG90aGVyIGF0dGFja3MN
CiAgIFByaXZhY3kgYW5kIGNvbmZpZGVudGlhbGl0eQ0KICAgRGF0YSBkZWlkZW50aWZpY2F0aW9u
DQogICBDcnlwdG9ncmFwaGljIHByb3RvY29scyBmb3IgY29sbGFib3JhdGl2ZSBzZWN1cml0eQ0K
ICAgQWNjZXNzIGNvbnRyb2wgZm9yIHNoYXJlZCBpbmZvcm1hdGlvbg0KICAgU2NhbGFibGUgc2Vj
dXJpdHkgYW5hbHlzaXMgb24gc2hhcmVkIGRhdGENCiAgIE9udG9sb2dpZXMgYW5kIHN0YW5kYXJk
cyBmb3Igc2hhcmluZyBzZWN1cml0eSBkYXRhDQogICBVWCBhbmQgYmVoYXZpb3JhbCBhc3BlY3Rz
IG9mIGNvbGxhYm9yYXRpb24NCiAgIFBvbGljeSBhbmQgbGVnYWwgaXNzdWVzDQogICBTdXJ2ZWls
bGFuY2UgaXNzdWVzDQogICBUcnVzdCBtb2RlbHMNCiAgIEF0dGFja3Mgb24gaW5mb3JtYXRpb24g
c2hhcmluZw0KICAgRWNvbm9taWNzIG9mIHNlY3VyaXR5IGNvbGxhYm9yYXRpb24NCg0KSU1QT1JU
QU5UIERBVEVTDQpQYXBlciBzdWJtaXNzaW9uIGR1ZTogIEF1ZyA1LCAyMDE2IChleHRlbmRlZCBm
cm9tIEp1bHkgMjIsIDIwMTYpIEF1dGhvciBub3RpZmljYXRpb246ICBTZXB0ZW1iZXIgMDUsIDIw
MTYgQ2FtZXJhIHJlYWR5IGNvcGllcyBkdWU6ICBTZXB0ZW1iZXIgMTEsIDIwMTYNCldvcmtzaG9w
OiAgT2N0b2JlciAyNCwgMjAxNiANCg0KU1RFRVJJTkcgQ09NTUlUVEVFDQpGcmVkZHkgRGV6ZXVy
ZSwgQ0VSVC1FVQ0KVG9tYXMgU2FuZGVyLCBIZXdsZXR0IFBhY2thcmQgRW50ZXJwcmlzZSBSaWNo
YXJkIFN0cnVzZSwgREhTIE1vdGkgWXVuZywgQ29sdW1iaWEgVW5pdmVyc2l0eSBhbmQgIFNuYXBj
aGF0DQoNClBST0dSQU0gQ08tQ0hBSVJTDQpGbG9yaWFuIEtlcnNjaGJhdW0sIFNBUA0KRXJpay1P
bGl2ZXIgQmxhc3MsIEFpcmJ1cyBHcm91cCBJbm5vdmF0aW9ucyANCg0KUFJPR1JBTSBDT01NSVRU
RUUNCkdhaWwtSm9vbiBBaG4sIEFyaXpvbmEgU3RhdGUgVW5pdmVyc2l0eQ0KUmFpbmVyIEJvZWht
ZSwgVW5pdmVyc2l0eSBvZiBJbm5zYnJ1Y2sNCkp1bGllbiBCcmluZ2VyLCBNb3JwaG8NClNhcmFo
IEJyb3duLCBTZWN1cml0eUxpbmtzDQpFcmljIEJ1cmdlciwgR2VvcmdldG93biBVbml2ZXJzaXR5
DQpTY290dCBDb3VsbCwgUmVkamFjaw0KTWFyYyBEYWNpZXIsIFFhdGFyIENvbXB1dGluZyBSZXNl
YXJjaCBJbnN0aXR1dGUgUm9iZXJ0byBEaSBQaWV0cm8sIE5va2lhIEJlbGwgTGFicyBQYW5vcyBL
YW1wYW5pa2lzLCBDaXNjbyBNaWNoYWVsIEUuIExvY2FzdG8sIFNSSSBUcmF2aXMgTWF5YmVycnks
IE5hdmFsIEFjYWRlbXkgVG9tIE1pbGxhciwgVVMgQ0VSVCBSZWZpayBNb2x2YSwgRVVSRUNPTSBH
dWV2YXJhIE5vdWJpciwgTm9ydGhlYXN0ZXJuIFVuaXZlcnNpdHkgTWFuaXNoYSBQYXJtYXIsIE5B
VE8gQ29tbXVuaWNhdGlvbiBhbmQgSW5mb3JtYXRpb24gQWdlbmN5IFBhd2VsIFBhd2xpbnNraSwg
Q0VSVCBQb2xza2EgUm9iZXJ0byBQZXJkaXNjaSwgVW5pdmVyc2l0eSBvZiBHZW9yZ2lhIFRob21h
cyBTY2hyZWNrLCBTaWVtZW5zIE9zY2FyIFNlcnJhbm8sIE5BVE8gQ29tbXVuaWNhdGlvbiBhbmQg
SW5mb3JtYXRpb24gQWdlbmN5IFN0dWFydCBTaGFwaXJvLCBNSVRSRSBQYXVsIFZpeGllLCBGYXJz
aWdodCBTZWN1cml0eQ0KDQpQQVBFUiBTVUJNSVNTSU9OUw0KU3VibWl0dGVkIHBhcGVycyBtdXN0
IG5vdCBzdWJzdGFudGlhbGx5IG92ZXJsYXAgd2l0aCBwYXBlcnMgdGhhdCBoYXZlIGJlZW4gcHVi
bGlzaGVkIG9yIHRoYXQgYXJlIHNpbXVsdGFuZW91c2x5IHN1Ym1pdHRlZCB0byBhIGpvdXJuYWwg
b3IgYSBjb25mZXJlbmNlIHdpdGggcHJvY2VlZGluZ3MuIFJlZ3VsYXIgc3VibWlzc2lvbnMgc2hv
dWxkIGJlIGF0IG1vc3QgMTAgcGFnZXMgaW4gdGhlIEFDTSBkb3VibGUtY29sdW1uIGZvcm1hdCBp
bmNsdWRpbmcgYmlibGlvZ3JhcGh5LCBidXQgZXhjbHVkaW5nIHdlbGwtbWFya2VkIGFwcGVuZGlj
ZXMsIGFuZCBhdCBtb3N0IDEyIHBhZ2VzIHRvdGFsLiBDb21taXR0ZWUgbWVtYmVycyBhcmUgbm90
IHJlcXVpcmVkIHRvIHJlYWQgdGhlIGFwcGVuZGljZXMsIGFuZCBzbyB0aGUgcGFwZXIgc2hvdWxk
IGJlIGludGVsbGlnaWJsZSB3aXRob3V0IHRoZW0uIFN1Ym1pc3Npb25zIHNob3VsZCBub3QgYmUg
YW5vbnltaXplZC4gVGhlIHdvcmtzaG9wIHdpbGwgYWxzbyBjb25zaWRlciBzaG9ydCBzdWJtaXNz
aW9ucyBvZiB1cCB0byA0IHBhZ2VzIGZvciBjYXNlIHN0dWRpZXMsIHJlc3VsdHMgdGhhdCBhcmUg
cHJlbGltaW5hcnkgb3IgdGhhdCByZXF1aXJlIG9ubHkgYSBmZXcgcGFnZXMgdG8gZGVzY3JpYmUu
IEF1dGhvcnMgb2YgcmVndWxhciBzdWJtaXR0ZWQgcGFwZXJzIHdpbGwgaW5kaWNhdGUgYXQgdGhl
IHRpbWUgb2Ygc3VibWlzc2lvbiB3aGV0aGVyIHRoZXkgd291bGQgbGlrZSB0aGVpciBwYXBlciB0
byBhbHNvIGJlIGNvbnNpZGVyZWQgZm9yIHB1YmxpY2F0aW9uIGFzIGEgc2hvcnQgcGFwZXIgKDQg
cHJvY2VlZGluZ3MgcGFnZXMpLg0KDQpTdWJtaXNzaW9ucyBhcmUgdG8gYmUgbWFkZSB0byB0aGUg
c3VibWlzc2lvbiB3ZWIgc2l0ZSBhdCBodHRwczovL2Vhc3ljaGFpci5vcmcvY29uZmVyZW5jZXMv
P2NvbmY9d2lzY3MxNiAuICBZb3Ugd2lsbCBiZSByZXF1ZXN0ZWQgdG8gdXBsb2FkIHRoZSBmaWxl
IG9mIHlvdXIgcGFwZXIgKGluIFBERiBmb3JtYXQgb25seSkuIFN1Ym1pc3Npb25zIG5vdCBtZWV0
aW5nIHRoZXNlIGd1aWRlbGluZXMgcmlzayByZWplY3Rpb24gd2l0aG91dCBjb25zaWRlcmF0aW9u
IG9mIHRoZWlyIG1lcml0cy4gUGFwZXJzIG11c3QgYmUgcmVjZWl2ZWQgYnkgQXVnIDUsIDIwMTYg
KGV4dGVuZGVkIGRlYWRsaW5lKSB0byBiZSBjb25zaWRlcmVkLiBOb3RpZmljYXRpb24gb2YgYWNj
ZXB0YW5jZSBvciByZWplY3Rpb24gd2lsbCBiZSBzZW50IHRvIGF1dGhvcnMgYnkgU2VwdGVtYmVy
IDA1LCAyMDE2LiBUaGUgY2FtZXJhIHJlYWR5IHZlcnNpb25zIG11c3QgYmUgcHJlcGFyZWQgYnkg
U2VwdGVtYmVyIDExLCAyMDE2IChmaXJtKS4gUHJvY2VlZGluZ3Mgb2YgdGhlIHdvcmtzaG9wIHdp
bGwgYmUgcHVibGlzaGVkIGJ5IEFDTSBvbiBhIENELCBhdmFpbGFibGUgdG8gdGhlIHdvcmtzaG9w
IGF0dGVuZGVlcy4gUGFwZXJzIHdpbGwgYmUgaW5jbHVkZWQgaW4gdGhlIEFDTSBEaWdpdGFsIExp
YnJhcnksIHdpdGggYSBzcGVjaWZpYyBJU0JOLiBFYWNoIGFjY2VwdGVkIHBhcGVyIG11c3QgYmUg
cHJlc2VudGVkIGJ5IGFuIGF1dGhvciwgd2hvIHdpbGwgaGF2ZSB0byBiZSByZWdpc3RlcmVkIGJ5
IHRoZSBlYXJseS1iaXJkIHJlZ2lzdHJhdGlvbiBkZWFkbGluZS4NCg0KQ09OVEFDVA0KUGxlYXNl
IGNvbnRhY3QgdGhlIHByb2dyYW0gY28tY2hhaXJzIEZsb3JpYW4gS2Vyc2NoYmF1bSBhbmQgRXJp
ay1PbGl2ZXIgQmxhc3MgICh3aXNjczIwMTZAZWFzeWNoYWlyLm9yZykgd2l0aCBhbnkgcXVlc3Rp
b25zLg0KDQo=


From nobody Wed Jul 20 01:58:42 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9FA12B061 for <mile@ietfa.amsl.com>; Wed, 20 Jul 2016 01:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.487
X-Spam-Level: 
X-Spam-Status: No, score=-0.487 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id out7gtau3u0Z for <mile@ietfa.amsl.com>; Wed, 20 Jul 2016 01:58:38 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8345C12B037 for <mile@ietf.org>; Wed, 20 Jul 2016 01:58:38 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id u6K8wbql007563 for <mile@ietf.org>; Wed, 20 Jul 2016 17:58:37 +0900 (JST)
Received: from DESKTOP2JPR8KD (ssh1.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp  with ESMTP id u6K8wZXQ007542 for <mile@ietf.org>; Wed, 20 Jul 2016 17:58:36 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Wed, 20 Jul 2016 17:58:35 +0900
Message-ID: <039c01d1e264$e6c56c40$b45044c0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_039D_01D1E2B0.56AD1440"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdHiZNSS72jAQud/Q0eKWBcnHGaphg==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/-UBx4PvJfNAI1FkqXTXgJL6pJQY>
Subject: [mile] ROLIE poc
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2016 08:58:41 -0000

This is a multipart message in MIME format.

------=_NextPart_000_039D_01D1E2B0.56AD1440
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

If you remember, Mr. Kaoru Maeda has done a nice demonstration of the ROLIE
tool at the MILE session in IETF 94.

 

The proof-of-concept tool is available online under the MIT License.

https://github.com/TakeshiTakahashi/ROLIE-tool

 

Kind regards,

Take

 


------=_NextPart_000_039D_01D1E2B0.56AD1440
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:\6E38\30B4\30B7\30C3\30AF;
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@\6E38\30B4\30B7\30C3\30AF";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:\6E38\30B4\30B7\30C3\30AF;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.17
	{mso-style-type:personal-compose;
	font-family:\6E38\30B4\30B7\30C3\30AF;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:\6E38\30B4\30B7\30C3\30AF;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026">
<v:textbox inset=3D"5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DJA =
link=3D"#0563C1" vlink=3D"#954F72" =
style=3D'text-justify-trim:punctuation'><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Hi =
all,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>If you =
remember, Mr. Kaoru Maeda has done a nice demonstration of the ROLIE =
tool at the MILE session in IETF 94.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>The =
proof-of-concept tool is available online under the MIT =
License.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><a =
href=3D"https://github.com/TakeshiTakahashi/ROLIE-tool">https://github.co=
m/TakeshiTakahashi/ROLIE-tool</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Kind =
regards,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'>Take<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>
------=_NextPart_000_039D_01D1E2B0.56AD1440--


From nobody Wed Jul 20 22:22:09 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEAF812D9FD for <mile@ietfa.amsl.com>; Wed, 20 Jul 2016 22:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.588
X-Spam-Level: 
X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xp0qGEPqZAat for <mile@ietfa.amsl.com>; Wed, 20 Jul 2016 22:22:06 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id 19C2812D65F for <mile@ietf.org>; Wed, 20 Jul 2016 22:22:04 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp  with ESMTP id u6L5M2kO042241 for <mile@ietf.org>; Thu, 21 Jul 2016 14:22:02 +0900 (JST)
Received: from DESKTOP2JPR8KD (ssh1.nict.go.jp [133.243.3.49]) by gw2.nict.go.jp  with ESMTP id u6L5M0Tp042202 for <mile@ietf.org>; Thu, 21 Jul 2016 14:22:01 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Thu, 21 Jul 2016 14:21:59 +0900
Message-ID: <022501d1e30f$cf486da0$6dd948e0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0226_01D1E35B.3F3349F0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdHjD5PcgeOaeM5ZRv+xLQ+hYS/egQ==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/n0ixcDA-oPudbHUk-pHU4ue7znA>
Subject: [mile] MILE meeting information today
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 05:22:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0226_01D1E35B.3F3349F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all,

 

Our session begins at 10:00 am in the room "Charlottenburg I".

 

The agenda: https://datatracker.ietf.org/meeting/96/agenda/mile/

The meeting materials: https://datatracker.ietf.org/meeting/96/session/mile

Location of the room:
https://datatracker.ietf.org/meeting/96/floor-plan?room=charlottenburg-i#ber
lin-intercontinental-floor-1

 

If you could kindly volunteer to be the jabber scribe and/or note taker,
please let co-chairs know.

We will appreciate that very much.

 

Thanks and regards,

Take

 


------=_NextPart_000_0226_01D1E35B.3F3349F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Yu Gothic";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.17
	{mso-style-type:personal-compose;
	font-family:"Yu Gothic";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Yu Gothic";}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026">
<v:textbox inset=3D"5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DJA =
link=3D"#0563C1" vlink=3D"#954F72" =
style=3D'text-justify-trim:punctuation'><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Hello =
all,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Our =
session begins at 10:00 am in the room &#8220;Charlottenburg =
I&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>The =
agenda: <a =
href=3D"https://datatracker.ietf.org/meeting/96/agenda/mile/">https://dat=
atracker.ietf.org/meeting/96/agenda/mile/</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>The =
meeting materials: <a =
href=3D"https://datatracker.ietf.org/meeting/96/session/mile">https://dat=
atracker.ietf.org/meeting/96/session/mile</a><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Location =
of the room: <a =
href=3D"https://datatracker.ietf.org/meeting/96/floor-plan?room=3Dcharlot=
tenburg-i#berlin-intercontinental-floor-1">https://datatracker.ietf.org/m=
eeting/96/floor-plan?room=3Dcharlottenburg-i#berlin-intercontinental-floo=
r-1</a><o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>If you =
could kindly volunteer to be the jabber scribe and/or note taker, please =
let co-chairs know.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>We will appreciate that very =
much.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Thanks =
and regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>Take<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>
------=_NextPart_000_0226_01D1E35B.3F3349F0--


From nobody Thu Jul 21 06:41:50 2016
Return-Path: <takeshi_takahashi@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4288912D5C9 for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 06:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uLKEuCyY-n-B for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 06:41:42 -0700 (PDT)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0170512D53C for <mile@ietf.org>; Thu, 21 Jul 2016 06:41:41 -0700 (PDT)
Received: from gw1.nict.go.jp (gw1.nict.go.jp [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id u6LDfeKP043956 for <mile@ietf.org>; Thu, 21 Jul 2016 22:41:40 +0900 (JST)
Received: from DESKTOP2JPR8KD (ssh1.nict.go.jp [133.243.3.49]) by gw1.nict.go.jp  with ESMTP id u6LDfcuu043929 for <mile@ietf.org>; Thu, 21 Jul 2016 22:41:39 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
Date: Thu, 21 Jul 2016 22:41:36 +0900
Message-ID: <80d001d1e355$9ad5e750$d081b5f0$@nict.go.jp>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_80D1_01D1E3A1.0ABFD940"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdHjVZnLiZ+uABEwTaG/BVLPA8yEGQ==
Content-Language: ja
X-Virus-Scanned: clamav-milter 0.98.7 at zenith1
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/vhBd8ftKkkQstVFRkrED60nM-B8>
Subject: [mile] minute (tentative) is available online
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 13:41:49 -0000

This is a multipart message in MIME format.

------=_NextPart_000_80D1_01D1E3A1.0ABFD940
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all,

 

The minute (tentative) is available online.

https://www.ietf.org/proceedings/96/minutes/minutes-96-mile

 

If you would like to change some part of the minutes, please kindly let
co-chairs know.

We would like to thank Charles M. Schmidt and Chris Inacio for their kind
and generous volunteers.

 

Thank you, and regards,

Take

 


------=_NextPart_000_80D1_01D1E3A1.0ABFD940
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Yu Gothic";
	panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Yu Gothic";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.17
	{mso-style-type:personal-compose;
	font-family:"Yu Gothic";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Yu Gothic";}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:99.25pt 30.0mm 30.0mm 30.0mm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026">
<v:textbox inset=3D"5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DJA =
link=3D"#0563C1" vlink=3D"#954F72" =
style=3D'text-justify-trim:punctuation'><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Hello =
all,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>The =
minute (tentative) is available online.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'><a =
href=3D"https://www.ietf.org/proceedings/96/minutes/minutes-96-mile">http=
s://www.ietf.org/proceedings/96/minutes/minutes-96-mile</a><o:p></o:p></s=
pan></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>If you =
would like to change some part of the minutes, please kindly let =
co-chairs know.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>We would like to thank Charles =
M. Schmidt and Chris Inacio for their kind and generous =
volunteers.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt'>Thank =
you, and regards,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:11.0pt'>Take<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></body></htm=
l>
------=_NextPart_000_80D1_01D1E3A1.0ABFD940--


From nobody Thu Jul 21 06:51:35 2016
Return-Path: <dave@cridland.net>
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 0EA2D12D516 for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 06:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mScbJQTG5CL7 for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 06:51:21 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6260512D623 for <mile@ietf.org>; Thu, 21 Jul 2016 06:51:21 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id q128so22688508wma.1 for <mile@ietf.org>; Thu, 21 Jul 2016 06:51:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=yHQSO80zqlgYtHj4W461GMrKpQW+Mv90yg3gX4jd3pw=; b=kXVPZXGRRBmuCbo0uDlEKs5qW6wiW8SkzJ+MWGNCWtIO7uYdL3szBbT5Qzg4s/agTH l3vBeI8JZqx1T+dbKI6QPdixG1/kdSX5tB2EYHjAEsVQR8yl9br/mkaCnJVvxqVM1g2T YMghp6x91HRyEJa/xoeHfehdmqwTIsTT60cV8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=yHQSO80zqlgYtHj4W461GMrKpQW+Mv90yg3gX4jd3pw=; b=c6fBq0gOfHK9H/y8sB/lAuf0CpAX+k7SMyOSOruIKPY+ADQCvfkdIW0h7IguoFyB2M Du0wD4Jp/2nmYGkfVFP/nIOBm9gTo9j/9NHYds66Mc8x1iOTIKdoeAj8b5UQlkJw71/W X7uR7OqA99YjNCfBUA6D9DeFUm1qE3FxqdNp3pc98RSCEk3/pzWZSxkUjqRU2OOKk8Bs z0T6RXuMzSo5J9OKsiiwANxpsoqB54G64LMgdNugpfqe0Kl2ItnNUAs2tETeeeRcfNWp WkAwyWrOUUEMQ84ZJIM51TbfvxZQvAHGZ4ALLFiFqXC0G8cUacFBOaG6p0hp9ptKGwVl /BLw==
X-Gm-Message-State: ALyK8tKI3hJLt4KwwvlouEdicrnRCLV6jWOg9rYNBfUDO8Wa2ybgN13x3ycr3hy8nYRbyYPD3DT3S2eU/+XTjKXJ
X-Received: by 10.28.13.1 with SMTP id 1mr17575322wmn.60.1469109079829; Thu, 21 Jul 2016 06:51:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.127.204 with HTTP; Thu, 21 Jul 2016 06:51:19 -0700 (PDT)
From: Dave Cridland <dave@cridland.net>
Date: Thu, 21 Jul 2016 14:51:19 +0100
Message-ID: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com>
To: mile@ietf.org
Content-Type: multipart/alternative; boundary=001a11443734d706ab0538259cd3
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/13q8Fnmdf7PoH4ELBMlKBUVxMaI>
Subject: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jul 2016 13:51:34 -0000

--001a11443734d706ab0538259cd3
Content-Type: text/plain; charset=UTF-8

Folks,

I've been aware of the XMPP Grid work for a while, but I've only recently
read through the draft.

It's not clear to me if this provides anything above and beyond the
pre-existing capabilities provided by the XSF specifications such as
XEP-0060, XEP-0030, and so on.

XEP-0060 in particular provides a complete protocol for publish-subscribe
within XMPP which has widespread adoption. Specialist services can and have
been created on top of the primitives it offers, although it can also be
used "as-is".

Pushing IODEF, or any other XML payload, through XEP-0060 is trivial, and
it offers discoverability and so on as part of the basic feature set.

I'm curious as to why this isn't being used, and if it were, what would be
the feature gaps.

Dave.

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

<div dir=3D"ltr">Folks,<div><br></div><div>I&#39;ve been aware of the XMPP =
Grid work for a while, but I&#39;ve only recently read through the draft.</=
div><div><br></div><div>It&#39;s not clear to me if this provides anything =
above and beyond the pre-existing capabilities provided by the XSF specific=
ations such as XEP-0060, XEP-0030, and so on.</div><div><br></div><div>XEP-=
0060 in particular provides a complete protocol for publish-subscribe withi=
n XMPP which has widespread adoption. Specialist services can and have been=
 created on top of the primitives it offers, although it can also be used &=
quot;as-is&quot;.</div><div><br></div><div>Pushing IODEF, or any other XML =
payload, through XEP-0060 is trivial, and it offers discoverability and so =
on as part of the basic feature set.</div><div><br></div><div>I&#39;m curio=
us as to why this isn&#39;t being used, and if it were, what would be the f=
eature gaps.</div><div><br></div><div>Dave.</div></div>

--001a11443734d706ab0538259cd3--


From nobody Thu Jul 21 23:45:07 2016
Return-Path: <athiasjerome@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACA2F12B04B for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 23:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60l9yidMCW4C for <mile@ietfa.amsl.com>; Thu, 21 Jul 2016 23:45:04 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE57012B03D for <mile@ietf.org>; Thu, 21 Jul 2016 23:45:03 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id s189so144728054vkh.1 for <mile@ietf.org>; Thu, 21 Jul 2016 23:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7/t3ihpR2crm0tWXqs8YpoJoPSiEH2kIwBUl4Wu6CpM=; b=nWGwseclHdwktROz7617XUEZ8DG4DSEgy0GgLQ305cStFPwLHC6e1xxGKNA/Xd9O2z m9Nz8AVpgiO8XNJIvvTa7woEO20ld+nTcm//Ui5ZEI2JrR9ahRQAddZmAXifec9/8A0B z77BtQjtsP1AzEL7R5N5YV9qoVTpqOxWyxxp34CaCrtTQjR8TjJ0YCodgzP4R9gfEgk9 QcTrnWaNY1AHLbJ3ERRUsH6xDa3HBFhV0yzlz5zug+GMSt9ba2/1DC2l4wR4ouw6AM28 6vWJ3Zp2ezgjFSQEbTHszuAVLcW93Mvy5DotOIfF2TVcTFdIXwrSS8xAQpSn+mks60ji Mklg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7/t3ihpR2crm0tWXqs8YpoJoPSiEH2kIwBUl4Wu6CpM=; b=V7GT722MwvFSrIoTy+OPMbpdC8tkJsvYX4r3gnSDEP34o1efsmPzFs1XQmECFN2Foh /EQiVekZHeOD6vlboLEtBYWemVzJuSvcnv0O4GgZ+HHiKzbeafxZr/392HYqmx0IWXXo 3YFbrx8b61Q8y64/qAp4xDQAdYepIlJqmhlDTjxrCKvDrZv5pGZ6Xw3/QPGibFi9m7ma 259sZi8R/Jk6k/FWXYFenh5/uZhH7gpTDAm3OLGtua+mU5QNGUIZ99++d2XEYuiQ8cw7 80yTHVado6N25VCNUqgvNgVjYLHbQkkFf39f3t2ThPyjWNPcgQyqHE6umfXwLigenO6o aVnw==
X-Gm-Message-State: AEkoousbIq9RjFdOjINS6lD/1yJEvSG5mAgCTKecS2JJHcuJ3sACKY2Bf2V3VTnuJJdNXmgWhtiD9dFkTBDA+A==
X-Received: by 10.31.58.198 with SMTP id h189mr1126620vka.74.1469169902973; Thu, 21 Jul 2016 23:45:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.47.78 with HTTP; Thu, 21 Jul 2016 23:45:02 -0700 (PDT)
In-Reply-To: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
Date: Fri, 22 Jul 2016 09:45:02 +0300
Message-ID: <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/1F-JRudB0OmW0EwObxvyy9VLW2c>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 06:45:06 -0000

Hi,

Not sure what you mean by "why this isn't being used".
>From a 'pure standard point of view', it seems that XEP-0060 would
play more into the Implementation area.
With that said, I can see how/why it could be pointed out, or
'recommend' in a Standard or Guidelines around a Standard.

My 2c
/JA


On Thu, Jul 21, 2016 at 4:51 PM, Dave Cridland <dave@cridland.net> wrote:
> Folks,
>
> I've been aware of the XMPP Grid work for a while, but I've only recently
> read through the draft.
>
> It's not clear to me if this provides anything above and beyond the
> pre-existing capabilities provided by the XSF specifications such as
> XEP-0060, XEP-0030, and so on.
>
> XEP-0060 in particular provides a complete protocol for publish-subscribe
> within XMPP which has widespread adoption. Specialist services can and have
> been created on top of the primitives it offers, although it can also be
> used "as-is".
>
> Pushing IODEF, or any other XML payload, through XEP-0060 is trivial, and it
> offers discoverability and so on as part of the basic feature set.
>
> I'm curious as to why this isn't being used, and if it were, what would be
> the feature gaps.
>
> Dave.
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>


From nobody Fri Jul 22 00:46:59 2016
Return-Path: <dave@cridland.net>
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 C5C8812D9B5 for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 00:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mCGo9W_xsQjY for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 00:46:57 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3BEC12D5EB for <mile@ietf.org>; Fri, 22 Jul 2016 00:46:56 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id i5so53419389wmg.0 for <mile@ietf.org>; Fri, 22 Jul 2016 00:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=16Ms2v5S+bMwBRF66o130uCTjlfn6nWhvX1lrb7XM6Q=; b=bx7qO2r0sXWsX2GCx/ZqgwSLSsGXl+drB9Xc8qBYKZL6awQFvInnFe1jA/b/o3/iaq IzBVRI7zzlT5hBPAsXAXgqxvkIdqVlZ5+GLBoqcDaumT4Kp15qP0pEWjbeFp8jW1/JKt 0fsBswYrxi2f3Rgop9jZH0KAczxj7Is0BvJfA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=16Ms2v5S+bMwBRF66o130uCTjlfn6nWhvX1lrb7XM6Q=; b=IKjXeEo11WEDh6TkfwGcDl0DmOQ35Va77CtOGum7BCu6s3R9BvZI1AEooXw648p0jP VecWvrdRAZYLH6ttdYZpfXK34wSV4wEbTmrk/h7hxteVvWO0g9vuxfD4t6/TS0q6Pwqg 9nxKe15yeSKGm2cUH9mejWDFaoqj7ZSWzP86RUsrjvENKbj2u1VnmZUaCBwCdjGTK0++ PbJpoTUd717jvTgWV19bg6jjuD8ZMmJxCdOyoyPtbp4Rjv/vjScWV2jUxETY8Ggcxg3k 5r6lz0fNtI2x6UzzT4iNW7hNIaYUT0xnIbe1LHfgvchSLB4xfWk6oU9fB9647JvtSHnw /HUQ==
X-Gm-Message-State: AEkoouvFkS6LchdquQbEiMcX87EsFeUVDNpkUWWW01DSYpFxUwAKyJvhdqMEx3Pow+jWwf3dHjKxm7kwQe1RLqdB
X-Received: by 10.28.172.197 with SMTP id v188mr4586225wme.60.1469173615227; Fri, 22 Jul 2016 00:46:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.127.204 with HTTP; Fri, 22 Jul 2016 00:46:54 -0700 (PDT)
In-Reply-To: <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com> <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Fri, 22 Jul 2016 08:46:54 +0100
Message-ID: <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com>
To: Jerome Athias <athiasjerome@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141ed86732df5053834a3cb
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/KQU7jcCkltLtrXcJOMgn6wvKp6M>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 07:46:59 -0000

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

Jerome,

On 22 July 2016 at 07:45, Jerome Athias <athiasjerome@gmail.com> wrote:

> Not sure what you mean by "why this isn't being used".
>

I meant that XEP-0060 is not being used as the pub-sub mechanism within
XMPP-Grid, and instead a new generic publish-subscribe mechanism has been
defined.

For example, the flows in =C2=A72.4.3 all exist within XEP-0060:

Figures 5 and 7 are equivalent to a pubsub node with an access-model of
authorize, where the Controller is an owner. See for example:

http://www.xmpp.org/extensions/xep-0060.html#subscriber-subscribe-approval
http://www.xmpp.org/extensions/xep-0060.html#owner-subreq

Figure 6 is equivalent to
http://www.xmpp.org/extensions/xep-0060.html#publisher-publish

Figure 8 might be new (although it looks like a session establishment to my
eyes, so XMPP has protocol for those too).


> From a 'pure standard point of view', it seems that XEP-0060 would
> play more into the Implementation area.
>

I'm not sure what you mean here. XEP-0060 is very much a standards-track
specification, and not any particular implementation. There are, however, a
number of existing implementations of XEP-0060. It's a Draft specification
within the XSF, which is (roughly) equivalent to Proposed Standard within
the IETF.

Dave.

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

<div dir=3D"ltr">Jerome,<br><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On 22 July 2016 at 07:45, Jerome Athias <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:athiasjerome@gmail.com" target=3D"_blank">athiasjerome@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;borde=
r-left-color:rgb(204,204,204);padding-left:1ex">Not sure what you mean by &=
quot;why this isn&#39;t being used&quot;.<br></blockquote><div><br></div><d=
iv>I meant that XEP-0060 is not being used as the pub-sub mechanism within =
XMPP-Grid, and instead a new generic publish-subscribe mechanism has been d=
efined.</div><div><br></div><div>For example, the flows in =C2=A72.4.3 all =
exist within XEP-0060:</div><div><br></div><div>Figures 5 and 7 are equival=
ent to a pubsub node with an access-model of authorize, where the Controlle=
r is an owner. See for example:</div><div><br></div><div><a href=3D"http://=
www.xmpp.org/extensions/xep-0060.html#subscriber-subscribe-approval">http:/=
/www.xmpp.org/extensions/xep-0060.html#subscriber-subscribe-approval</a><br=
></div><div><a href=3D"http://www.xmpp.org/extensions/xep-0060.html#owner-s=
ubreq">http://www.xmpp.org/extensions/xep-0060.html#owner-subreq</a><br></d=
iv><div><br></div><div>Figure 6 is equivalent to=C2=A0<a href=3D"http://www=
.xmpp.org/extensions/xep-0060.html#publisher-publish">http://www.xmpp.org/e=
xtensions/xep-0060.html#publisher-publish</a></div><div><br></div><div>Figu=
re 8 might be new (although it looks like a session establishment to my eye=
s, so XMPP has protocol for those too).</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1=
ex">
>From a &#39;pure standard point of view&#39;, it seems that XEP-0060 would<=
br>
play more into the Implementation area.<br></blockquote><div><br></div><div=
>I&#39;m not sure what you mean here. XEP-0060 is very much a standards-tra=
ck specification, and not any particular implementation. There are, however=
, a number of existing implementations of XEP-0060. It&#39;s a Draft specif=
ication within the XSF, which is (roughly) equivalent to Proposed Standard =
within the IETF.</div><div><br></div><div>Dave.</div></div></div></div>

--001a1141ed86732df5053834a3cb--


From nobody Fri Jul 22 01:29:03 2016
Return-Path: <athiasjerome@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C5D12D5EB for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5_UdQg6fvD6 for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:28:59 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E79912D1A4 for <mile@ietf.org>; Fri, 22 Jul 2016 01:28:59 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id s189so147546952vkh.1 for <mile@ietf.org>; Fri, 22 Jul 2016 01:28:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=CiKBj3GywM8/f7aPX5TuY20x04YDFOF8L95Izh090mk=; b=rtC5il+85jG5dbbA6EZvT1VAzj9RSgQGhWwn6Mte227ftNQeMbySgmh1jEaKu0RRBS FHy8FlNhdPofK/GHtMtaspLEcol56tOopOupFIMPEUyImq6fgle0elcSxrtO2TDIbEe4 DkR1HdqceZTYwDtVz/IxWg/SfKaex+hAkvJ6uZYtXD5+Ofg8XTb0hqxtbsYwVbOG+x0s xN7o7L6DddyzP+nzMBFZjVRSP7GIVnYBAvwo0h2gdZ32YmBJieztFIwAWrp3sqqqn8Yc LT87keipMpIHJxlKVCNcBmmtQxgrQk6Vmim32ouTHwaNETgr9WqKmdoJZI5dk3Ls6b3G qv4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=CiKBj3GywM8/f7aPX5TuY20x04YDFOF8L95Izh090mk=; b=Dp5rrYr6Xlay9HTr7/mXWNcFOwiPK/V0CBSAAjlsrBQ0+MEp+c9eGRYjXMGK+r7aZy 8e86s86bl6jHkUYt+iINDGzJAyQuMHBqinT8sKyTn8x5KwOVq/lYLAJUKjsolvjJg+G+ zweNOqPFAOXNipheEKaXTWgg6XWk7VoqQYIhzdtNf7Hobx2+T9inP6g1xqGs72Lm58Ju Gp0s5p288WakJs4LefOZEFshg+1ShBz9kE7zmYnPRzuFKIWv8SBLNUmN1Jt3If+aE+2b a5LL6Adl+mPY2qrwPBJ+lRiv9vQOhSZHIooKJpIRlW9orXFmcIH0P6NladA4iNbu9NMc fPww==
X-Gm-Message-State: AEkoousluoncjOJNDaQzke1xavMJyfGgOPTulOI7KEH/1HC6sSDejbXxLWbUhVhwgynKbmv/9OwVS+LbbVnbVg==
X-Received: by 10.31.14.15 with SMTP id 15mr954128vko.137.1469176138521; Fri, 22 Jul 2016 01:28:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.47.78 with HTTP; Fri, 22 Jul 2016 01:28:58 -0700 (PDT)
In-Reply-To: <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com> <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com> <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
Date: Fri, 22 Jul 2016 11:28:58 +0300
Message-ID: <CAA=AuEfc2NBvrbO6-t7viXLTBxZwXPROcSfbs_vS+YvT7ZbNeA@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/1dCOT1ZAuiYJUTYkEPS9vxQZCJQ>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 08:29:01 -0000

clear now
I don't know...

Meantime, one (not-related) question: is it content-agnostic, meaning
would it work, i.e., with JSON in place of XML?


On Fri, Jul 22, 2016 at 10:46 AM, Dave Cridland <dave@cridland.net> wrote:
> Jerome,
>
> On 22 July 2016 at 07:45, Jerome Athias <athiasjerome@gmail.com> wrote:
>>
>> Not sure what you mean by "why this isn't being used".
>
>
> I meant that XEP-0060 is not being used as the pub-sub mechanism within
> XMPP-Grid, and instead a new generic publish-subscribe mechanism has been
> defined.
>
> For example, the flows in =C2=A72.4.3 all exist within XEP-0060:
>
> Figures 5 and 7 are equivalent to a pubsub node with an access-model of
> authorize, where the Controller is an owner. See for example:
>
> http://www.xmpp.org/extensions/xep-0060.html#subscriber-subscribe-approva=
l
> http://www.xmpp.org/extensions/xep-0060.html#owner-subreq
>
> Figure 6 is equivalent to
> http://www.xmpp.org/extensions/xep-0060.html#publisher-publish
>
> Figure 8 might be new (although it looks like a session establishment to =
my
> eyes, so XMPP has protocol for those too).
>
>>
>> From a 'pure standard point of view', it seems that XEP-0060 would
>> play more into the Implementation area.
>
>
> I'm not sure what you mean here. XEP-0060 is very much a standards-track
> specification, and not any particular implementation. There are, however,=
 a
> number of existing implementations of XEP-0060. It's a Draft specificatio=
n
> within the XSF, which is (roughly) equivalent to Proposed Standard within
> the IETF.
>
> Dave.


From nobody Fri Jul 22 01:42:53 2016
Return-Path: <dave@cridland.net>
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 5FD6E12DA24 for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNzAARJpaL5z for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:42:50 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6558112D1A4 for <mile@ietf.org>; Fri, 22 Jul 2016 01:42:50 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id i5so56026071wmg.0 for <mile@ietf.org>; Fri, 22 Jul 2016 01:42:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Xfe1cYbqIPY9xJJe8xMAdBFEyxAx/UlpKCV/PSoTHwc=; b=aqfRGodlMrF/hygSGH1ZC/BHMqq5jdZv0G9deqbm4IQoCnwz+lEZz/S2D1u27hkyv0 ZyWSs453xKEXngtaJ3sSyoSsokUgXyjXJ2nE18dX5ZNAuqnnSQCiFDB/ypN4z3cqKZle EJpdxt+M7JVq2ecoDRny7PfSd1OBLWGaWBsmc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Xfe1cYbqIPY9xJJe8xMAdBFEyxAx/UlpKCV/PSoTHwc=; b=Xmen93DCsVS9ZNvV4nXGm1J92rSjkbh+TDYlBChRPbjKfM5vVY/0LIY5Zgjj27/+mG vS2I60Z896VeSnxR+gfYExKm+SDCbrw3JiEYpqfwo6XAwlSx6GGFpJYciFlZF8t9choL x8wtBJx96jjIIf9PeeT6kK12n0R2ZfX6/a83MoSfsE9l+c+7Y0OG1AZTgPrmpp0jNIvZ VwRNfcf4SGNa79OuQ0j/7XHXZf7jw0Q/mAcb/FwV7TnVZCd6tRwBR+9gLEPTrsBUg0fi 9uHw/gzKQH+QoiS71TR8ZSMmVqg4XlEvN3eqz2uqXNVB1xwjzbo1WjwaxVqaLcwR4jXA lYdA==
X-Gm-Message-State: ALyK8tLlArqSlUQsWTYlSkhyRa8Lgr1cvrMDugmSadjB1Q1y4iYBjpOL2eIZhgT+2xjllATkseo6Omj5yhGzKzr0
X-Received: by 10.28.46.204 with SMTP id u195mr23194917wmu.57.1469176968901; Fri, 22 Jul 2016 01:42:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.127.204 with HTTP; Fri, 22 Jul 2016 01:42:48 -0700 (PDT)
In-Reply-To: <CAA=AuEfc2NBvrbO6-t7viXLTBxZwXPROcSfbs_vS+YvT7ZbNeA@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com> <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com> <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com> <CAA=AuEfc2NBvrbO6-t7viXLTBxZwXPROcSfbs_vS+YvT7ZbNeA@mail.gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Fri, 22 Jul 2016 09:42:48 +0100
Message-ID: <CAKHUCzwE71HPEscibsd1uui+Qdr0TA3Dkt8am2yPzRdadPUdGQ@mail.gmail.com>
To: Jerome Athias <athiasjerome@gmail.com>
Content-Type: multipart/alternative; boundary=001a11423a7a5819b50538356bea
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/I2_mrw09IykHsNK0N4jD2EyXeLE>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 08:42:52 -0000

--001a11423a7a5819b50538356bea
Content-Type: text/plain; charset=UTF-8

On 22 July 2016 at 09:28, Jerome Athias <athiasjerome@gmail.com> wrote:

> Meantime, one (not-related) question: is it content-agnostic, meaning
> would it work, i.e., with JSON in place of XML?


You're presumably thinking in terms of STIX 2.0? Yes and no.

There's no absolute requirement that the payload format be anything in
particular - it has to be an XML element (ie, DOM subtree) for syntax's
sake, but that XML could easily be a container element with a textual value
in JSON format, like:

<stix xmlns='some:stix:namespace'><![CDATA[{"type":"malware", ...
}]]></stix>

An alternative would be throwing the JSON into an attribute value, but that
would probably need more escaping than a CDATA block.

As a general note, XMPP treats XML as a pragmatic syntax, rather than
buying into the complete XML ecosystem of document and schema, so the
result tends to be much more palatable than, say, typical JAXB output, and
the community is less prone to purism about mixing JSON and XML than might
be expected.

Dave.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 22 July 2016 at 09:28, Jerome Athias <span dir=3D"ltr">&lt;<a href=
=3D"mailto:athiasjerome@gmail.com" target=3D"_blank">athiasjerome@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Meantime, one (not=
-related) question: is it content-agnostic, meaning<br>
would it work, i.e., with JSON in place of XML?</blockquote><div>=C2=A0</di=
v><div>You&#39;re presumably thinking in terms of STIX 2.0? Yes and no.</di=
v><div><br></div><div>There&#39;s no absolute requirement that the payload =
format be anything in particular - it has to be an XML element (ie, DOM sub=
tree) for syntax&#39;s sake, but that XML could easily be a container eleme=
nt with a textual value in JSON format, like:</div><div><br></div><div>&lt;=
stix xmlns=3D&#39;some:stix:namespace&#39;&gt;&lt;![CDATA[{&quot;type&quot;=
:&quot;malware&quot;, ... }]]&gt;&lt;/stix&gt;</div><div><br></div><div>An =
alternative would be throwing the JSON into an attribute value, but that wo=
uld probably need more escaping than a CDATA block.</div><div><br></div><di=
v>As a general note, XMPP treats XML as a pragmatic syntax, rather than buy=
ing into the complete XML ecosystem of document and schema, so the result t=
ends to be much more palatable than, say, typical JAXB output, and the comm=
unity is less prone to purism about mixing JSON and XML than might be expec=
ted.</div><div><br></div><div>Dave.</div></div></div></div>

--001a11423a7a5819b50538356bea--


From nobody Fri Jul 22 01:46:49 2016
Return-Path: <athiasjerome@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA0B12DAAC for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWEOnM3u9GHL for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:46:39 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C078912DAAB for <mile@ietf.org>; Fri, 22 Jul 2016 01:46:37 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id w127so148396920vkh.2 for <mile@ietf.org>; Fri, 22 Jul 2016 01:46:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uvzu1Knwwxa/662XRcymBLpQNBRC0Dv8aSWvk3xZlxA=; b=jTn7SnKspsInDucEPm+ZM6+OU4QUZVsSt2AbHpiGZRJk/umYOLti/ga1ggyxgz4Zbz rqAgoRXJuWfKiuv4QkgGXJ9xK/XdjBt3MlNGZsephAvz1ExG7IJ4qh3c3wPfFiQX5FGO cnUiSOMNVIIH2yOUYN5bAESqyckuniO1pvab+vXx0f2rCstF3Kz+E6WRXI27M40o2EgK 5Q9831vtZVCrThDHhva/GGHtT4FhhAMl0kKUk0i8Tb7yYIJ6vf02n2XjZyvEa399BAoh 1lQZSgZD7Z3HRQYomjitwuD2HrnfmWii4JHOogIFjyx8ZjS+tiSesQkuoDNdChVD76Yz /EDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uvzu1Knwwxa/662XRcymBLpQNBRC0Dv8aSWvk3xZlxA=; b=kpMFRDWtfYqoHiJXpeYBr3IlMIdgTpJt3bGEz9q9qpWfmjM/LADDlfN3BTMlhhslYn gvE/iJ4MmjtA6pAOCExCAxBZ21uC2Xy6T3RzlWl7FPoj3JckJnst45S5GghJoAO3ea5h 5EiGSSkdJNhVMrhJQh2FjOthlq8sIzVLhhLEiQ1H2S4PZzUnzatvxlsXShWfOE0FiceG LsUATitlCYJFcNYWDB5QyuMm9BZFjPJAtiF42v/0t7W21SaAPNqFR3stFiamiJ36H8Fk vjzGo3E7rTtIZ8hNJiIUrFtMXSEVF0H4iPtwvVFo2uuydp+5kNyAZgZ0agGDpV66ko/l l4kQ==
X-Gm-Message-State: AEkoouvU6Ds7MeEJdn254MMhRLZ2oNc+Y54eysP37OJxs6UjPkfbZrXifQpFqsROvxW8XB5cmYRU8Uv3zC4zxA==
X-Received: by 10.159.35.40 with SMTP id 37mr1254277uae.118.1469177196475; Fri, 22 Jul 2016 01:46:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.47.78 with HTTP; Fri, 22 Jul 2016 01:46:36 -0700 (PDT)
In-Reply-To: <CAKHUCzwE71HPEscibsd1uui+Qdr0TA3Dkt8am2yPzRdadPUdGQ@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com> <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com> <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com> <CAA=AuEfc2NBvrbO6-t7viXLTBxZwXPROcSfbs_vS+YvT7ZbNeA@mail.gmail.com> <CAKHUCzwE71HPEscibsd1uui+Qdr0TA3Dkt8am2yPzRdadPUdGQ@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
Date: Fri, 22 Jul 2016 11:46:36 +0300
Message-ID: <CAA=AuEd+XqOUd7K_cvacqJdnt7MAeGyCnePGUxXu5HVxVxd5ww@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/SFksYC27-S6IOiPuMIfTPGIbmlU>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 08:46:47 -0000

Yep, I admit, I was thinking in context of STIX -in general- (mainly
v1 vs v2 in TAXII context)

Thanks for the answer. Crystal clear

On Fri, Jul 22, 2016 at 11:42 AM, Dave Cridland <dave@cridland.net> wrote:
>
>
> On 22 July 2016 at 09:28, Jerome Athias <athiasjerome@gmail.com> wrote:
>>
>> Meantime, one (not-related) question: is it content-agnostic, meaning
>> would it work, i.e., with JSON in place of XML?
>
>
> You're presumably thinking in terms of STIX 2.0? Yes and no.
>
> There's no absolute requirement that the payload format be anything in
> particular - it has to be an XML element (ie, DOM subtree) for syntax's
> sake, but that XML could easily be a container element with a textual value
> in JSON format, like:
>
> <stix xmlns='some:stix:namespace'><![CDATA[{"type":"malware", ...
> }]]></stix>
>
> An alternative would be throwing the JSON into an attribute value, but that
> would probably need more escaping than a CDATA block.
>
> As a general note, XMPP treats XML as a pragmatic syntax, rather than buying
> into the complete XML ecosystem of document and schema, so the result tends
> to be much more palatable than, say, typical JAXB output, and the community
> is less prone to purism about mixing JSON and XML than might be expected.
>
> Dave.


From nobody Fri Jul 22 01:53:28 2016
Return-Path: <athiasjerome@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E89912DAAF for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VpHH4tYKkMm for <mile@ietfa.amsl.com>; Fri, 22 Jul 2016 01:53:12 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 183B612DAAB for <mile@ietf.org>; Fri, 22 Jul 2016 01:53:12 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id x130so148718112vkc.0 for <mile@ietf.org>; Fri, 22 Jul 2016 01:53:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yPihqoWTRm/CwbedvUX5K3bXymE8leDekq6CjQ5zewA=; b=o5/f4VU0DdYBt7kXPl1SlMQfLAJD1LkayyKnLnBSK80cN+AIriMYPeQpXd/vKGMqeA Oo6r3tom/vZKns+11Jak5avjaPyE3JtK7iEy2d68hhE/JLKPnnBzBMWSzToDe6Kx6dxa 4ZnvXO6wNTX4G6TY5yC9bTR8H1pPgKpok1E+I5+Wr0z4F8hPfQFK15/7125LSzc/ki7q 8i2ykhHSOX27UCfAfZZqnRL9utXy3EeHm1UDYHc82WzrxnCi2Rd5gOr80hXVfUF+9kfk 9K7sP+TB21T6h8yhOiL5KuqsoONzfc6Him8Z+x+rvz/rWUnS2+poW6mBvanKXcqH5B8J j6zA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yPihqoWTRm/CwbedvUX5K3bXymE8leDekq6CjQ5zewA=; b=R5JqCk5ckqwiB21pgMa5lGvpX0jGSBbdL/2uOjOV18N4fAZCsYaTm0vPt6uw8p/b6U a+Sok5C+m1qxmgc4hnlV6EZ1SUjYGWcoRp6TS+vR8dP+uWN+aP4t8daF78U77P8w7VqT PV6fQzshQHgvaUpyuf9mP/SEi9fefOqZaF5doVDu/CjkJ3+denGNfu8GciBYtboUS1Rj /iAybRuISPvNgsiFeEOe61ggIMf+x20PW4ohE+FifD2RUMjRW4wrngDqvA2/KPAXO+m2 9bHsW/P2sD6j0B7ZkLuelGO/7o+WAVKp3ISeW3IW/VoGJeDjbCN6bm1GyUYtHWkXqQEK smlA==
X-Gm-Message-State: AEkoouvPx5xbTMGRzDAtgmjblJWrFs3V3KJo/5xGSACdYFyp8L4niCNoS9JmoiuDrqpX0d8K89tfa+p0Tijy/w==
X-Received: by 10.31.148.198 with SMTP id w189mr1199101vkd.127.1469177591238;  Fri, 22 Jul 2016 01:53:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.47.78 with HTTP; Fri, 22 Jul 2016 01:53:10 -0700 (PDT)
In-Reply-To: <CAA=AuEd+XqOUd7K_cvacqJdnt7MAeGyCnePGUxXu5HVxVxd5ww@mail.gmail.com>
References: <CAKHUCzwSBjj9RjT2Lfm4TJwLPn_TKzxCRenVzKdFRNa9QhQmNg@mail.gmail.com> <CAA=AuEexcOkJSEywf=CHeHC0oWX++FiXx8nVSa0T0zE5ahkxug@mail.gmail.com> <CAKHUCzyocJYDCyKFe3wQ7EeUh+F_EefG0SsRkscmtaOhSMyrug@mail.gmail.com> <CAA=AuEfc2NBvrbO6-t7viXLTBxZwXPROcSfbs_vS+YvT7ZbNeA@mail.gmail.com> <CAKHUCzwE71HPEscibsd1uui+Qdr0TA3Dkt8am2yPzRdadPUdGQ@mail.gmail.com> <CAA=AuEd+XqOUd7K_cvacqJdnt7MAeGyCnePGUxXu5HVxVxd5ww@mail.gmail.com>
From: Jerome Athias <athiasjerome@gmail.com>
Date: Fri, 22 Jul 2016 11:53:10 +0300
Message-ID: <CAA=AuEcwnkS1s400ajq_Dx54WyHMc_25+byZ5YfHGBAboCT5iw@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/nVUqN95sBWxBoqcdh9l6T5nzPNw>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] XMPP Grid
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jul 2016 08:53:14 -0000

PS: question would apply similarly in the context of
https://datatracker.ietf.org/doc/draft-takahashi-mile-jsoniodef/

On Fri, Jul 22, 2016 at 11:46 AM, Jerome Athias <athiasjerome@gmail.com> wrote:
> Yep, I admit, I was thinking in context of STIX -in general- (mainly
> v1 vs v2 in TAXII context)
>
> Thanks for the answer. Crystal clear
>
> On Fri, Jul 22, 2016 at 11:42 AM, Dave Cridland <dave@cridland.net> wrote:
>>
>>
>> On 22 July 2016 at 09:28, Jerome Athias <athiasjerome@gmail.com> wrote:
>>>
>>> Meantime, one (not-related) question: is it content-agnostic, meaning
>>> would it work, i.e., with JSON in place of XML?
>>
>>
>> You're presumably thinking in terms of STIX 2.0? Yes and no.
>>
>> There's no absolute requirement that the payload format be anything in
>> particular - it has to be an XML element (ie, DOM subtree) for syntax's
>> sake, but that XML could easily be a container element with a textual value
>> in JSON format, like:
>>
>> <stix xmlns='some:stix:namespace'><![CDATA[{"type":"malware", ...
>> }]]></stix>
>>
>> An alternative would be throwing the JSON into an attribute value, but that
>> would probably need more escaping than a CDATA block.
>>
>> As a general note, XMPP treats XML as a pragmatic syntax, rather than buying
>> into the complete XML ecosystem of document and schema, so the result tends
>> to be much more palatable than, say, typical JAXB output, and the community
>> is less prone to purism about mixing JSON and XML than might be expected.
>>
>> Dave.


From nobody Fri Jul 29 10:52:18 2016
Return-Path: <stephen.banghart@nist.gov>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 301B212DA00 for <mile@ietfa.amsl.com>; Fri, 29 Jul 2016 10:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nistgov.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQtqaxUPM5xI for <mile@ietfa.amsl.com>; Fri, 29 Jul 2016 10:52:14 -0700 (PDT)
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (mail-dm2gcc01on0133.outbound.protection.outlook.com [23.103.201.133]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3DF012DA2E for <mile@ietf.org>; Fri, 29 Jul 2016 10:52:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nistgov.onmicrosoft.com; s=selector1-nist-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZxbCbZWoPL1UKcOip7jjNBdrZME6vXyzCW9ojRWN+cs=; b=i+7m7Ol4eL9XMZOW3PEV5MR+RAks1Scii62T0agWfZDdvtg5NCdr210R0S4TZm+aPocVOkrNgTI3UkEuQN1sl+x2sacpOdDe095vfhPhKePp7likMcsjnEUt5dSdIq50RUgb5K+f9lh1U9/rnsKoza1m6n/pkkgj9c8TaRWhMNs=
Received: from SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) by SN1PR09MB0960.namprd09.prod.outlook.com (10.162.102.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Fri, 29 Jul 2016 17:52:11 +0000
Received: from SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) by SN1PR09MB0960.namprd09.prod.outlook.com ([10.162.102.148]) with mapi id 15.01.0549.016; Fri, 29 Jul 2016 17:52:11 +0000
From: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Thread-Topic: ROLIE Authorization and Authentication
Thread-Index: AdHpvwFCwotwpaMPTJ+yy7j9Kj4evQ==
Date: Fri, 29 Jul 2016 17:52:11 +0000
Message-ID: <SN1PR09MB09600CB8FE94CDEF9A91A6ACF0010@SN1PR09MB0960.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephen.banghart@nist.gov; 
x-originating-ip: [129.6.227.79]
x-ms-office365-filtering-correlation-id: 627a67a5-3cb5-4fe8-5d4b-08d3b7d9117a
x-microsoft-exchange-diagnostics: 1; SN1PR09MB0960; 6:mEJYEF9KdMI2AbplmwYYkiadihq/QrmB0PZtp4m79PQ05DvOETBxuPqV4VA3zyp/hRuhyRaKmoQxyI93HH3lPmW++dD7wLYH9Bx9I3vkk0BWTPNJqu9Ud5zrfnaOvBevlNPJUkepkx1sEQYHOBtUvl5HMfWQsKZgIfWpYgJTYwJHvfLPtT6AtSGGPjhuN3qF62JgtJui0FsUyjvDe/7PSYQ9DtiNsAZ/JAzPCtIpKjIZGRHa94hv1uhcQaxYer4Ni4K66k9/uBOEoW1ME5BmvcDMuNlMfkzKsouX3vFLwzZA51NayXzhf5aZctqcwywCh5n1XtWjsfyRgRNh46AYVQ==; 5:rnipVHU6XOiSFbxRS3/zrCQ0zZpeBb7fD0NC729yJ1S+gpEFzl2tl+6FEDjsd9W+XJcTU6QocC4HpMaH7aWqvfMuHwmJBfxO1J6D4lRMHzknl+6n/hsDhyVTMSLay3+e9VLL6hcBkTNJMGxo2wp2ow==; 24:uy3a6dxX+Mg2923Xv7qqMufLq9sgaXY4vqx0YqPwdorjYnZCS2niCJ7vFvCSqqO182TShkjFbHpmKFE8b4CHm8hYFlInYuMbgMp27pINJk4=; 7:l7uXHG1fbX+XF0qJurq5D1sZKFjdPOI4ndY9hYBPZQzqtEs6vDQ1RduGfhB73/Rc1yG3aVnHtw/MooODUdcxdnBHfGsnyrh8O6sZeqH4OvgGdYLcY4SBxvcpm1GQFEC1CAaTMigLYb+FovLu6n1z6DKtwAL5AW/B3thkSMBBB+W0v4ZxidofqjquPRelEOAwGTO30mtrkiIAUvTp28/na8NqopzoDTuO7sWG/GyRR6QJy/XnkfzhCVNmvUrV5riC
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR09MB0960;
x-microsoft-antispam-prvs: <SN1PR09MB0960CE5E90E3A94D4558C70DF0010@SN1PR09MB0960.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026);  SRVR:SN1PR09MB0960; BCL:0; PCL:0; RULEID:; SRVR:SN1PR09MB0960; 
x-forefront-prvs: 0018A2705B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(53754006)(199003)(74316002)(99286002)(76576001)(101416001)(19617315012)(19625215002)(3846002)(102836003)(7696003)(7736002)(6116002)(790700001)(122556002)(3280700002)(3660700001)(15975445007)(19580395003)(8936002)(1730700003)(81156014)(81166006)(229853001)(3480700004)(2351001)(68736007)(450100001)(2501003)(97736004)(106356001)(50986999)(2906002)(8676002)(11100500001)(189998001)(87936001)(5002640100001)(110136002)(107886002)(5630700001)(586003)(77096005)(105586002)(33656002)(7846002)(7906003)(92566002)(54356999)(66066001)(561944003)(19300405004)(9686002)(2900100001)(86362001)(10400500002)(16236675004)(5640700001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR09MB0960; H:SN1PR09MB0960.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: nist.gov does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR09MB09600CB8FE94CDEF9A91A6ACF0010SN1PR09MB0960namp_"
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2016 17:52:11.5837 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR09MB0960
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/yAQs8CpSv-HsT_yDJ6UN2cgjaG0>
Subject: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2016 17:52:17 -0000

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

Hello all,

Following the discussion at IETF 96 on draft-ietf-mile-rolie-03, there are =
some issues that we wanted to bring to the mailing list for discussion. Thi=
s e-mail references GitHub issue #34 (https://github.com/CISecurity/ROLIE/i=
ssues/34). The text from the issue is duplicated here for convenience:

Authentication and authorization can be handled using a number of different=
 mechanisms, for this reason it's not clear if we can require a specific me=
chanism in the ROLIE core. More discussion is needed with the working group=
 to determine a way forward.

Proposals:

- A: Select one or more authentication and authorization mechanisms as mand=
atory to implement (MTI).
- B: Address these issues in separate drafts.


Support for OAUTH, http-auth, and XACML has been discussed in a limited cap=
acity previously. Given that deployed solutions may require different authe=
ntication and authorization solutions based on differing deployment require=
ments, we are concerned about requiring any single solution. Furthermore, d=
efining requirements for multiple solutions will add significant page count=
 to the draft. As a result, we are leaning towards proposal B which would a=
llow for some modularity in solutions through additional drafts.

Are there any concerns with going this route?

If option A is desired, we could use some help from someone knowledgeable i=
n using authentication and authorization solutions with HTTP RESTful servic=
es.

Thanks,
Stephen Banghart


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Following the discussion at IETF 96 on draft-ietf-mi=
le-rolie-03, there are some issues that we wanted to bring to the mailing l=
ist for discussion. This e-mail references GitHub issue #34 (<a href=3D"htt=
ps://github.com/CISecurity/ROLIE/issues/34">https://github.com/CISecurity/R=
OLIE/issues/34</a>).
 The text from the issue is duplicated here for convenience: <o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Authentication and authorization can be handled usin=
g a number of different mechanisms, for this reason it&#8217;s not clear if=
 we can require a specific mechanism in the ROLIE core. More discussion is =
needed with the working group to determine
 a way forward. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Proposals:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">- A: Select one or more authentication and authoriza=
tion mechanisms as mandatory to implement (MTI).<o:p></o:p></p>
<p class=3D"MsoNormal">- B: Address these issues in separate drafts. <o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Support for OAUTH, http-auth, and XACML has been dis=
cussed in a limited capacity previously. Given that deployed solutions may =
require different authentication and authorization solutions based on diffe=
ring deployment requirements, we are
 concerned about requiring any single solution. Furthermore, defining requi=
rements for multiple solutions will add significant page count to the draft=
. As a result, we are leaning towards proposal B which would allow for some=
 modularity in solutions through
 additional drafts.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Are there any concerns with going this route?<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If option A is desired, we could use some help from =
someone knowledgeable in using authentication and authorization solutions w=
ith HTTP RESTful services.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Stephen Banghart<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_SN1PR09MB09600CB8FE94CDEF9A91A6ACF0010SN1PR09MB0960namp_--


From nobody Sun Jul 31 08:52:06 2016
Return-Path: <adam.w.montville@gmail.com>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD19712D09A for <mile@ietfa.amsl.com>; Sun, 31 Jul 2016 08:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5fVNfIFFK8q for <mile@ietfa.amsl.com>; Sun, 31 Jul 2016 08:52:03 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E2B712B046 for <mile@ietf.org>; Sun, 31 Jul 2016 08:52:02 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id j124so149408317ith.1 for <mile@ietf.org>; Sun, 31 Jul 2016 08:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=WEARvKopjCyyQikJWF30ZoqbgqexjOigAozXHbIRge0=; b=h5rtviGiq4U/72GEnpAjssU1ritdfc9bCEtvsAPgRDxLvFproaQcCG2dIFzQOcE2X4 s7d2WB/fLgVjNW3eCt4PKCuE0xqtjDEh0qZFYCJ4qnmDIQiyc6qxM7MAxorqS8zFd7hG ujjn6zmA/448n1KSSasNCVKKUqOx6w/CIbndVupEwvNhQ3PHN1Vk4YkBj75NZIUjh3t6 L8nw1G3vd6G//XkYyfnxaT6nlFhrL5ZDiDQowU6k2+t1A0c29+4qvq2fU85GNvTqBQz7 4PjykuRdp3GQctfCWiRPc4V6kD3Zwyv+L+5Z/qvPkoDWwXBm9raGBlQ2CgOK+z9hogw1 lofA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=WEARvKopjCyyQikJWF30ZoqbgqexjOigAozXHbIRge0=; b=gwPifyitW+vgLXdqd8VjBUPV0T42OpjKPggq0ExFObcxGgqn+R1mRct+h0INDtb0It LX++mkS+mpjQar/JuPohiaBRauDxjoMcPhKAkhDNy4ZK66NGurmJo2BmFxX9vRG4PkdP sDdLnEFpruJTmZg3ZPPas3I1XA3Z2KhKO/HckgPjGusi2SPMVSciFmgRIngnMpUVgerB QYzcluO4j3o9g/THrXRSsbrkyGKpUx6x9HvE6Z/28HRYCRtfYcRdwviHwwXMy5Mq2Et+ x9Suv7dWXVooxaIx/FVQg5VOcbfO3q3IEQGylfXWsgVrkxBy8hz1QnDP3nr/e83eHpNf 4Qtg==
X-Gm-Message-State: AEkoouulL1qACtkrg3PcGFLLy776ObFp+5rlmj1PNS+BKrP09TzOyBy+08NISGOIa6+zWQ==
X-Received: by 10.36.196.133 with SMTP id v127mr9589482itf.84.1469980321549; Sun, 31 Jul 2016 08:52:01 -0700 (PDT)
Received: from [172.20.10.5] ([166.170.23.171]) by smtp.gmail.com with ESMTPSA id 140sm5891892itl.4.2016.07.31.08.51.59 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 31 Jul 2016 08:52:00 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6421258A-69AC-4A76-806A-DD828C5A3DB1"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Adam Montville <adam.w.montville@gmail.com>
In-Reply-To: <SN1PR09MB09600CB8FE94CDEF9A91A6ACF0010@SN1PR09MB0960.namprd09.prod.outlook.com>
Date: Sun, 31 Jul 2016 10:51:56 -0500
Message-Id: <96BCF06B-ACA0-4176-9557-D8CBA6604F8D@gmail.com>
References: <SN1PR09MB09600CB8FE94CDEF9A91A6ACF0010@SN1PR09MB0960.namprd09.prod.outlook.com>
To: "Banghart, Stephen A. (Fed)" <stephen.banghart@nist.gov>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/y_V7AmqG-03NEdXjp2ZnTKkZ2Ls>
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] ROLIE Authorization and Authentication
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jul 2016 15:52:05 -0000

--Apple-Mail=_6421258A-69AC-4A76-806A-DD828C5A3DB1
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_13E359E9-149D-49B1-990F-6246CD0056FF"


--Apple-Mail=_13E359E9-149D-49B1-990F-6246CD0056FF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Stephen,

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

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

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

Kind regards,

Adam

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

--Apple-Mail=_13E359E9-149D-49B1-990F-6246CD0056FF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Stephen,<div class=3D""><br class=3D""></div><div =
class=3D"">If the primary purpose of ROLIE is to make public information =
available, then leaving the authentication piece to separate drafts =
(your Option B) seems to make sense. &nbsp;My interest in ROLIE is =
centered on the ability to syndicate configuration checklists, which is =
a class of security automation information generally available to the =
public.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">I =
suspect that information sharing organizations may have a different =
perspective.</div><div class=3D""><br class=3D""></div><div class=3D"">I =
cannot authoritatively speak to which mechanism(s) would be best, but it =
seems to be the case that OAUTH is widely used for many REST APIs in the =
wild. &nbsp;I have not seen XACML used in such a context. &nbsp;I'm also =
not sure that we should get into authorization.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Kind regards,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Adam</div><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jul 29, 2016, at 12:52 PM, Banghart, Stephen A. (Fed) &lt;<a =
href=3D"mailto:stephen.banghart@nist.gov" =
class=3D"">stephen.banghart@nist.gov</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Hello all,<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Following =
the discussion at IETF 96 on draft-ietf-mile-rolie-03, there are some =
issues that we wanted to bring to the mailing list for discussion. This =
e-mail references GitHub issue #34 (<a =
href=3D"https://github.com/CISecurity/ROLIE/issues/34" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline;" =
class=3D"">https://github.com/CISecurity/ROLIE/issues/34</a>). The text =
from the issue is duplicated here for convenience:<span =
class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Authentication and authorization can be handled using a =
number of different mechanisms, for this reason it=E2=80=99s not clear =
if we can require a specific mechanism in the ROLIE core. More =
discussion is needed with the working group to determine a way =
forward.<span class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Proposals:<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">- A: Select one or more authentication and authorization =
mechanisms as mandatory to implement (MTI).<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">- B: =
Address these issues in separate drafts.<span =
class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Support =
for OAUTH, http-auth, and XACML has been discussed in a limited capacity =
previously. Given that deployed solutions may require different =
authentication and authorization solutions based on differing deployment =
requirements, we are concerned about requiring any single solution. =
Furthermore, defining requirements for multiple solutions will add =
significant page count to the draft. As a result, we are leaning towards =
proposal B which would allow for some modularity in solutions through =
additional drafts.<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Are there any concerns with going this route?<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">If option =
A is desired, we could use some help from someone knowledgeable in using =
authentication and authorization solutions with HTTP RESTful =
services.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Thanks,<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Stephen Banghart<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">mile mailing =
list</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"mailto:mile@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">mile@ietf.org</a><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/mile" =
style=3D"color: rgb(149, 79, 114); text-decoration: underline; =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/mile</a></div></blockquot=
e></div><br class=3D""></div></body></html>=

--Apple-Mail=_13E359E9-149D-49B1-990F-6246CD0056FF--

--Apple-Mail=_6421258A-69AC-4A76-806A-DD828C5A3DB1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXnh6fAAoJEDEhyx7etgABY1cQAJvPSTbWuKhBnBIekpkTQ71E
fwFBxxjD3L1CnYga03IUKm94pU+McQbAoNk5eoPORPysXDS4DJBjZmQOQ1hj+5fV
QWxu2Ag33kCW/2eQfiUA6J2ynaQ7VuNVMdJQ2eR3aLkdaQY3xEMKbMd+CVf6Z9QA
stMvBn1IQ5G5+w2xk8rU37Mpax165ZjuWtLFVEovmRoTFd/eHE40iDShG3CEfa4i
O2NExAvDEM2n3NN+OOTDl1kBCZ4kC+lSZDxz20rcbTvkDpQVvCA+GjeyY+bry4n+
Zxm9m3ieaXq6qQ+DT+QIZoD/TiBcB/x5GQf6yA3jfGI+AHG8DDIErTEOlpl6b9hi
6WXAwA+Z31UCSVOTM36iCZUduH7mqwjv8cXLDD98Bg4fq3F3WzNQnSGWUrBL/eCq
hf/5k4jHBLi+VTgIe7zGkkzZdOdR8w14Ku0FXeh/piqBMHS4rz0WOYrdYHwWLk8M
aOOJ9IhBAykSUZYQ0HxdGhKGxpsDLNWryep/cYSxONRG8sFGsLMP+rwTc1CgR93b
Mg2XEIMCsjR5e0yJTB+ymztiubm3IpwrPJzyyCNiR9EnkC3ad7vSfIRbYkkbkMtx
woCXdjTuqDga8rt4tlGHU0yU32CB1t7t8eodAPLQ2Dlwywixk0g4CUWa9xw32YBT
tdKjmrgr+nk48K/X4ikI
=l6KH
-----END PGP SIGNATURE-----

--Apple-Mail=_6421258A-69AC-4A76-806A-DD828C5A3DB1--

