
From kathleen.moriarty@emc.com  Fri Dec  2 12:11:32 2011
Return-Path: <kathleen.moriarty@emc.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 469BE11E80D3 for <mile@ietfa.amsl.com>; Fri,  2 Dec 2011 12:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xpkg3QFU9r5Y for <mile@ietfa.amsl.com>; Fri,  2 Dec 2011 12:11:31 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id AD86C11E80B0 for <mile@ietf.org>; Fri,  2 Dec 2011 12:11:31 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB2KBSIv019351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Fri, 2 Dec 2011 15:11:28 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Fri, 2 Dec 2011 15:11:07 -0500
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB2KB7Ta002858 for <mile@ietf.org>; Fri, 2 Dec 2011 15:11:07 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 2 Dec 2011 15:10:21 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Fri, 2 Dec 2011 15:11:05 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiw==
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 20:11:32 -0000

FYI - two documents wrap up Working Group Last Call (WGLC) at end of day on=
 Monday.  Please share your comments on the list or that you have read the =
documents and have no comments/issues.

Thank you and have a nice weekend!
Kathleen




From ramartin@mitre.org  Sat Dec  3 14:54:06 2011
Return-Path: <ramartin@mitre.org>
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 143B021F93B5 for <mile@ietfa.amsl.com>; Sat,  3 Dec 2011 14:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVmWA7zQX+6j for <mile@ietfa.amsl.com>; Sat,  3 Dec 2011 14:54:05 -0800 (PST)
Received: from smtptsrv1.mitre.org (smtptsrv1.mitre.org [192.52.194.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7D421F93A8 for <mile@ietf.org>; Sat,  3 Dec 2011 14:54:05 -0800 (PST)
Received: from smtptsrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id A529829E513E; Sat,  3 Dec 2011 17:54:04 -0500 (EST)
Received: from IMCCAS02.MITRE.ORG (imccas02.mitre.org [129.83.29.79]) by smtptsrv1.mitre.org (Postfix) with ESMTP id 9A98B29BFA0B; Sat,  3 Dec 2011 17:54:04 -0500 (EST)
Received: from MM169528-pc.local (129.83.31.57) by IMCCAS02.MITRE.ORG (129.83.29.79) with Microsoft SMTP Server id 14.1.339.1; Sat, 3 Dec 2011 17:54:04 -0500
Message-ID: <4EDAA87C.1050709@mitre.org>
Date: Sat, 3 Dec 2011 17:53:48 -0500
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: <kathleen.moriarty@emc.com>
References: <1E47B2AA-6C80-40C4-9CB2-30AEAD08A550@tik.ee.ethz.ch>, <7C4DFCE962635144B8FAE8CA11D0BF1E059E270AB4@MX14A.corp.emc.com> <AE31510960917D478171C79369B660FA0E18F8BE04@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E18F8BE04@MX06A.corp.emc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6045-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Dec 2011 22:54:06 -0000

Hi Kathleen,

With these corrections and revisions I think this version of RID will be 
a great addition to the suite of incident management communications 
capabilities available for interactions between organizations.

Regards,

Bob

On 11/23/11 2:46 PM, kathleen.moriarty@emc.com wrote:
> Hello David,
>
> Thank you for the review and the catch!  I actually had that on the -00 document, so I will have to check my XML file and will regenerate the document.  I'll wait to see if any other comments come in.
>
> Have a nice holiday!
> Kathleen
> ________________________________________
> From: Black, David
> Sent: Wednesday, November 23, 2011 10:38 AM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: RE: [mile] WGLC on draft-ietf-mile-rfc6045-bis-01 to 5 December 2011
>
> Hello Kathleen,
>
> I had reviewed an earlier version of this draft in August; thank you for making the changes then in response to my comments.
>
> I don't see anything additional to comment on, aside from a nit in the header:
>
>          "Updates: 6045 (if approved)" -->  "Obsoletes: 6045 (if approved)"
>
> This is needed because this draft defines a new 1.1 version of the XML schema for RID in Section 4.4 (RFC 6045 defines the 1.0 version) and reclassifies RFC 6045 as Historic in Section 1.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>

From ramartin@mitre.org  Sun Dec  4 07:36:55 2011
Return-Path: <ramartin@mitre.org>
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 7EFA321F8508 for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 07:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPPcUmNUfyoP for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 07:36:54 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2982821F8507 for <mile@ietf.org>; Sun,  4 Dec 2011 07:36:54 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id B9CA221B0294; Sun,  4 Dec 2011 10:36:50 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 8C6BE21B028F; Sun,  4 Dec 2011 10:36:50 -0500 (EST)
Received: from MM169528-pc.local (129.83.31.51) by IMCCAS03.MITRE.ORG (129.83.29.80) with Microsoft SMTP Server id 14.1.339.1; Sun, 4 Dec 2011 10:36:50 -0500
Message-ID: <4EDB9381.5040100@mitre.org>
Date: Sun, 4 Dec 2011 10:36:33 -0500
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <7C4DFCE962635144B8FAE8CA11D0BF1E059E270A98@MX14A.corp.emc.com> <2A701AB9-32F7-41BD-A9BF-193EF42E3753@tik.ee.ethz.ch>
In-Reply-To: <2A701AB9-32F7-41BD-A9BF-193EF42E3753@tik.ee.ethz.ch>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Dec 2011 15:36:55 -0000

Hello Brian,

With these updates I think this is now a very solid document.  I look 
forward to this Transportation of RID messages capability becoming 
available for those trying to share incident management information 
between their enterprises.

Regards,

Bob

On 11/23/11 11:43 AM, Brian Trammell wrote:
> Hi, David,
>
> Thanks for the comments; have accepted them without further comment into the working copy of the -02 revision of the draft.
>
> Best regards,
>
> Brian (as author of 6046-bis)
>
> On Nov 23, 2011, at 4:10 PM,<david.black@emc.com>  wrote:
>
>> Hello Brian,
>>
>> This draft looks good, which was expected, as it's mostly unchanged from RFC 6046.
>> I have a few comments.
>>
>> (1) Section 3:
>>
>>    Consistent with BCP 56, RID systems will listen for
>>    TCP connections on port 4590.  Every RID system participating in a
>>    consortium MUST listen for HTTP/TLS connections on the assigned port.
>>
>> Something should be said about use of the standard port 443.  I think use of that port should
>> be discouraged or outright prohibited in order to avoid posting of RID messages to ordinary
>> web servers that may not handle them correctly or with sufficient security.  The simplest
>> approach would be to add:
>>
>> 	RID systems MUST NOT use TCP port 443 (the standard port for HTTP over TLS/SSL) for
>> 	RID messages.
>>
>> Alternatively:
>>
>> 	RID systems SHOULD NOT use TCP port 443 (the standard port for HTTP over TLS/SSL)
>> 	for RID messages; this avoids posting RID messages to web servers that may not
>> 	handle RID messages correctly.
>>
>> (2) Also Section 3:
>>
>>    When performing RID callback, a responding system MUST
>>    connect to the network- and transport-layer addresses from which the
>>    original request was sent; there is no mechanism in RID for
>>    redirected callback.
>>
>> I read "transport-layer addresses" as implying that the callback should connect to the TCP
>> port that was used to send the original RID message.  That seems wrong, because the TCP
>> connection on which the initial RID message is sent shouldn't be using TCP port 4590 as
>> the source port, and the callback should be going to port 4590.  I'd also suggest rewriting
>> this text to explicitly say what addresses are reused from the original request.
>>
>> (3) Section 4:
>>
>>    Although TLS
>>    implementations typically support the older SSL protocol, a RID peer
>>    MUST NOT request, offer, or use SSL 2.0, due to known security
>>    vulnerabilities in this protocol; see Appendix E of [RFC5246] for
>>    more.
>>
>> This is sufficient, but given how recently RID was originally specified (2010), would it
>> be reasonable to require TLS 1.1 (2006) or a more recent version?  Requiring at least
>> TLS 1.1 removes the vulnerability caused by use of an implicit IV for CBC-mode ciphers
>> in prior versions of TLS and SSL.
>>
>> Thanks,
>> --David
>> ----------------------------------------------------
>> David L. Black, Distinguished Engineer
>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> david.black@emc.com        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>

From paul.cichonski@nist.gov  Sun Dec  4 12:39:29 2011
Return-Path: <paul.cichonski@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 3EFEE21F846A for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 12:39:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXkVpB4q2hST for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 12:39:28 -0800 (PST)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 2015321F845F for <mile@ietf.org>; Sun,  4 Dec 2011 12:39:28 -0800 (PST)
Received: from WSXGHUB1.xchange.nist.gov (129.6.18.96) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.339.1; Sun, 4 Dec 2011 15:39:25 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB1.xchange.nist.gov ([129.6.18.96]) with mapi; Sun, 4 Dec 2011 15:39:25 -0500
From: "Cichonski, Paul" <paul.cichonski@nist.gov>
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>
Date: Sun, 4 Dec 2011 15:38:04 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiwBlhl60
Message-ID: <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>
References: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Dec 2011 20:39:29 -0000

SGkgS2F0aGxlZW4sDQoNCkkganVzdCBoYXZlIGEgZmV3IG1pbm9yIGNvbW1lbnRzIGJlbG93IHJl
bGF0aW5nIHRvIHRoZSAiUmVhbC10aW1lIEludGVyLW5ldHdvcmsgRGVmZW5zZSAoUklEKSBkcmFm
dC1tb3JpYXJ0eS1taWxlLXJmYzYwNDUtYmlzLTAyLnR4dCIgZG9jdW1lbnQuIE90aGVyIHRoYW4g
dGhlc2UgY29tbWVudHMsIGJvdGggZG9jdW1lbnRzIGxvb2sgZ29vZCB0byBtZS4NCg0KU2VjdGlv
bjogSW50cm9kdWN0aW9uLCBmaWZ0aCBwYXJhZ3JhcGg6DQoNCkZvciB0aGUgc2VudGVuY2UgIlRo
ZSBSSUQgc2NoZW1hIGFjdHMgYXMgYW4gWE1MIGVudmVsb3BlIHRvIHN1cHBvcnQgdGhlIGNvbW11
bmljYXRpb24gb2YgSU9ERUYgZG9jdW1lbnRzIGZvciBleGNoYW5naW5nIG9yIHRyYWNpbmcgaW5m
b3JtYXRpb24gcmVnYXJkaW5nIGluY2lkZW50cyIuIEl0IG1heSBoZWxwIGNsYXJpZnkgdGhpbmdz
IGlmIGEgZGlmZmVyZW50IHdvcmQgdGhhbiAnZW52ZWxvcGUnIHdhcyB1c2VkIGhlcmUsIHNpbmNl
IFt0byBtZV0gaXQgc3VnZ2VzdHMgdGhhdCBSSUQgZG9jdW1lbnRzIHdpbGwgYWN0dWFsbHkgZW52
ZWxvcGUgSU9ERUYgZG9jdW1lbnRzLiBIb3dldmVyLCBiYXNlZCBvbiB0aGUgZXhhbXBsZXMgYW5k
IHNjaGVtYSwgdGhlIGludGVuZGVkIHVzYWdlIGlzIGZvciBhIFJJRCBkb2N1bWVudCB0byBiZSBh
IHBlZXIgdG8gSU9ERUYgaW4gdGhlIHRyYW5zcG9ydCBzY2VuYXJpb3MsIHNvIG5vIGVudmVsb3Bp
bmcgaXMgb2NjdXJyaW5nLiBXb3VsZCBzdWdnZXN0IGEgcGhyYXNlIGxpa2UgIlRoZSBSSUQgc2No
ZW1hIGRlZmluZXMgY29tbXVuaWNhdGlvbi1zcGVjaWZpYyBtZXRhZGF0YSB0byBzdXBwb3J0IHRo
ZSBjb21tdW5pY2F0aW9uIG9mIC4uLi4iDQoNClNlY3Rpb246IEludHJvZHVjdGlvbiwgZmlmdGgg
cGFyYWdyYXBoOg0KDQpJbiB0aGUgc2Vjb25kIHRvIGxhc3Qgc2VudGVuY2UsIHRoZSBjaXRhdGlv
biBbUkZDNjA0Ni1iaXNdIGlzIGR1cGxpY2F0ZWQuDQoNClNlY3Rpb24gMy4xLCBmaXJzdCBwYXJh
Z3JhcGg6DQoNCkkgdGhpbmsgdGhlcmUgbWF5IGJlIGEgdHlwbyBpbiB0aGUgc3RhcnQgb2YgdGhl
IHNlbnRlbmNlOiAiUklEIHByb3ZpZGVzIGEgc3RhbmRhcmQgcHJvdG9jb2wgYW5kIGZvcm1hdCBp
cyByZXF1aXJlZCB0byBlbnN1cmUiLCBwcm9iYWJseSBzaG91bGQgYmUgIlJJRCBwcm92aWRlcyBh
IHN0YW5kYXJkIHByb3RvY29sIGFuZCBmb3JtYXQgdGhhdCBpcyByZXF1aXJlZCB0byBlbnN1cmUi
LiAoYWRkZWQgJ3RoYXQnKS4NCg0KU2VjdGlvbiA0LCBmaXJzdCBwYXJhZ3JhcGg6DQoNCkluIHRo
ZSBmaXJzdCBzZW50ZW5jZSwgaXQgbWF5IGJlIGhlbHBmdWwgdG8gYWRkIGNsYXJpZmljYXRpb24g
cmVsYXRpbmcgdG8gdGhlIHBocmFzZSAiUklEIGV4dGVuc2lvbiIuIFNwZWNpZmljYWxseSwgdGhl
IHRoaW5nIHRoYXQgUklEIGlzIGV4dGVuZGluZy4gSWYgeW91IG1lYW4gdGhhdCBSSUQgaXMgZXh0
ZW5kaW5nIElPREVGLCBJIGFtIG5vdCBzdXJlIEkgbGlrZSB0aGUgdGVybSAnZXh0ZW5kJywgc2lu
Y2UgUklEIGlzIHJlYWxseSBqdXN0IGltcG9ydGluZyB0aGUgSU9ERUYgZGF0YSBtb2RlbCBhbmQg
dXNpbmcgc29tZSBvZiB0aGUgZWxlbWVudHMgdGhhdCBJT0RFRiBkZWZpbmVzLCBidXQgbm90IGV4
dGVuZGluZyBhbnkgb2YgdGhlIElPREVGIHR5cGVzLCB0aHVzIHRoZSB3b3JkICdleHRlbmQnIG1h
eSBjb25mdXNlIGRldmVsb3BlcnMgdGhhdCBhcmUgcmVhZGluZyB0aGUgc3BlYy4NCg0KU2VjdGlv
biA0LCBzZWNvbmQgcGFyYWdyYXBoOg0KDQpSZWxhdGluZyB0byB0aGUgZmlyc3Qgc2VudGVuY2Us
IGp1c3QgcmVwZWF0aW5nIG15IHByZXZpb3VzIGNvbW1lbnQgZnJvbSB0aGUgaW50cm8gc2VjdGlv
bjogIkl0IG1heSBoZWxwIGNsYXJpZnkgdGhpbmdzIGlmIGEgZGlmZmVyZW50IHdvcmQgdGhhbiAn
ZW52ZWxvcGUnIHdhcyB1c2VkIGhlcmUsIHNpbmNlIFt0byBtZV0gaXQgc3VnZ2VzdHMgdGhhdCBS
SUQgZG9jdW1lbnRzIHdpbGwgYWN0dWFsbHkgZW52ZWxvcGUgSU9ERUYgZG9jdW1lbnRzLiBIb3dl
dmVyLCBiYXNlZCBvbiB0aGUgZXhhbXBsZXMgYW5kIHNjaGVtYSwgdGhlIGludGVuZGVkIHVzYWdl
IGlzIGZvciBhIFJJRCBkb2N1bWVudCB0byBiZSBhIHBlZXIgdG8gSU9ERUYgaW4gdGhlIHRyYW5z
cG9ydCBzY2VuYXJpb3MsIHNvIG5vIGVudmVsb3BpbmcgaXMgb2NjdXJyaW5nLiAiDQoNClNlY3Rp
b24gNjoNCg0KT25lIG92ZXJhbGwgY29tbWVudCBmb3IgdGhlIGRpYWdyYW1zIGluIHRoaXMgc2Vj
dGlvbjogaXQgbWF5IGhlbHAgdG8gaW5jbHVkZSB0aGUgSVAgYWRkcmVzcyBvZiAidGhpbmdzIiAo
ZS5nLiwgQXR0YWNrIERlc3QsIFNQLTEsIFNQLTIsIGV0Yy4uKSBpZiBwb3NzaWJsZSB0byBoZWxw
IHJlYWRlcnMgdW5kZXJzdGFuZCB0aGUgZXhhbXBsZSBYTUwsIHNwZWNpZmljYWxseSB0aGUgcGxh
Y2VzIHdoZXJlIElQIGFkZHJlc3NlcyBhcmUgbGlzdGVkLg0KDQpTZWN0aW9uIDYuMiwgZGlhZ3Jh
bToNCg0KQSByZXN1bHQgbWVzc2FnZSBpcyBzaG93biBpbiB0aGUgZGlhZ3JhbSwgYnV0IG5vIHJl
c3VsdCB4bWwgaXMgcHJvdmlkZWQgaW4gdGhlIGZvbGxvd2luZyBzdWItc2VjdGlvbnMuIEEgUmVx
dWVzdEF1dGhvcml6YXRpb24gaXMgbGlzdGVkIGluc3RlYWQuIElmIHRoZSBzdWItc2VjdGlvbnMg
YXJlIGludGVuZGVkIHRvIGRlc2NyaWJlIHRoZSBkaWFncmFtIHRoaXMgc2hvdWxkIGJlIGNoYW5n
ZWQuDQoNClNlY3Rpb24gNi40LjEsIGZpcnN0IHBhcmFncmFwaCwNCg0KVGhpcyBwYXJhZ3JhcGgg
bGlzdHMgdGhlIGRpZmZlcmVudCB0eXBlcyBvZiBmb3JtYXRzIHRoZSBJbmNpZGVudFF1ZXJ5IG1h
eSBiZSBzZW50IGFzLCBidXQgZG9lcyBub3Qgc2F5IHdoYXQgdGhlIGV4YW1wbGUgeG1sIGlsbHVz
dHJhdGVzIChlLmcuLCB3aGF0IHR5cGUpLiBTdWdnZXN0IGFkZGluZyBzb21lIHRleHQgdG8gc2Vj
b25kIHNlbnRlbmNlIHNheWluZyB0aGF0IHRoZSB0eXBlIGRlc2NyaWJlZCBpbiB0aGF0IHNlbnRl
bmNlIGlzIGlsbHVzdHJhdGVkIGluIHRoZSBleGFtcGxlIFhNTCAoYXQgbGVhc3QgSSB0aGluayBp
dCBpcykuDQoNClNlY3Rpb24gNywgc2NoZW1hLg0KDQpGb3IgdGhlIGZpcnN0IGltcG9ydCAodXJu
OmlldGY6cGFyYW1zOnhtbDpuczppb2RlZi0xLjApLCBndWVzc2luZyB0aGlzIGlzIHN1cHBvc2Vk
IHRvIHBvaW50IHRvIElPREVGIHNjaGVtYSBhbmQgbm90IElPREVGLVJJRDrvv71odHRwOi8vd3d3
LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3htbC1yZWdpc3RyeS9zY2hlbWEvaW9kZWYtMS4wLnhzZC4N
Cg0KVGhhbmtzLA0KUGF1bA0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQpGcm9tOiBtaWxlLWJvdW5jZXNAaWV0Zi5vcmcgW21pbGUtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIGthdGhsZWVuLm1vcmlhcnR5QGVtYy5jb20gW2thdGhsZWVuLm1v
cmlhcnR5QGVtYy5jb21dDQpTZW50OiBGcmlkYXksIERlY2VtYmVyIDAyLCAyMDExIDM6MTEgUE0N
ClRvOiBtaWxlQGlldGYub3JnDQpTdWJqZWN0OiBbbWlsZV0gV0cgTGFzdCBjYWxsDQoNCkZZSSAt
IHR3byBkb2N1bWVudHMgd3JhcCB1cCBXb3JraW5nIEdyb3VwIExhc3QgQ2FsbCAoV0dMQykgYXQg
ZW5kIG9mIGRheSBvbiBNb25kYXkuICBQbGVhc2Ugc2hhcmUgeW91ciBjb21tZW50cyBvbiB0aGUg
bGlzdCBvciB0aGF0IHlvdSBoYXZlIHJlYWQgdGhlIGRvY3VtZW50cyBhbmQgaGF2ZSBubyBjb21t
ZW50cy9pc3N1ZXMuDQoNClRoYW5rIHlvdSBhbmQgaGF2ZSBhIG5pY2Ugd2Vla2VuZCENCkthdGhs
ZWVuDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KbWlsZSBtYWlsaW5nIGxpc3QNCm1pbGVAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vbWlsZQ0K

From paul.cichonski@nist.gov  Sun Dec  4 14:50:47 2011
Return-Path: <paul.cichonski@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 6FAB621F8B32 for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 14:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSbvDce5hbF9 for <mile@ietfa.amsl.com>; Sun,  4 Dec 2011 14:50:46 -0800 (PST)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 37E3021F86B3 for <mile@ietf.org>; Sun,  4 Dec 2011 14:50:46 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.339.1; Sun, 4 Dec 2011 17:50:44 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Sun, 4 Dec 2011 17:50:05 -0500
From: "Cichonski, Paul" <paul.cichonski@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Date: Sun, 4 Dec 2011 17:49:07 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiwBlhl60AASTu4o=
Message-ID: <D7A0423E5E193F40BE6E94126930C49308EEA85C50@MBCLUSTER.xchange.nist.gov>
References: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com>, <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Dec 2011 22:50:47 -0000

U29ycnkgdG8gZm9sbG93LXVwIG9uIG15IG93biBwb3N0LCBidXQgSSB3YXMgdGhpbmtpbmcgYSBi
aXQgbW9yZSBhYm91dCB0aGUgImVudmVsb3BpbmciIHJlbGF0aW9uc2hpcCwgYW5kIHdhcyBqdXN0
IHdvbmRlcmluZyB3aHkgYSBSSUQgaW5zdGFuY2UgZG9jdW1lbnQgZG9lcyBub3QgYWN0dWFsbHkg
aW5jbHVkZSBhbiBpb2RlZjpJT0RFRi1Eb2N1bWVudCBlbGVtZW50IGFzIG9uZSBvZiB0aGUgb3B0
aW9uYWwgZWxlbWVudHMgb2YgdGhlIHJpZDpSSUQgZWxlbWVudD8NCg0KW05vdGUgdGhhdCBJIHdh
cyBpbmZlcnJpbmcgKHBvc3NpYmx5IGluY29ycmVjdGx5KSBhIGxvdCBhYm91dCB0aGUgUklEIHVz
YWdlIHBhdHRlcm5zIHdoZW4gd3JpdGluZyB0aGUgYmVsb3cgY29tbWVudHMsIHNvIHBsZWFzZSB0
YWtlIHRoZW0gd2l0aCBhIGdyYWluIG9mIHNhbHQuXQ0KDQpJdCB3b3VsZCBzZWVtIHRoYXQgdGhp
cyB0eXBlIG9mIHRydWUgZW52ZWxvcGluZyByZWxhdGlvbnNoaXAgd291bGQgYmUgYmVuZWZpY2lh
bCB0byBSSUQgY29uc3VtZXJzIHNpbmNlIGluIG1vc3Qgb2YgdGhlIGNhc2VzIChlLmcuLCB0aG9z
ZSB0aGF0IHJlcXVpcmUgYW4gSU9ERUYgZG9jdW1lbnQgYWxvbmcgd2l0aCB0aGUgUklEIG1lc3Nh
Z2UpIGl0IHdpbGwgYmUgbmVjZXNzYXJ5IGZvciB0aGUgY29uc3VtZXIgdG8gZGV0ZXJtaW5lIHdo
aWNoIElPREVGLURvY3VtZW50IHJlbGF0ZXMgdG8gdGhlIFJJRCBtZXNzYWdlIHRoYXQgd2FzIHJl
Y2VpdmVkLiBXaXRob3V0IGFuIGV4cGxpY2l0IHNwZWNpZmljYXRpb24gb2YgaG93IHRvIHJlc29s
dmUgdGhpcyBjb3JyZWxhdGlvbiB0aGUgY29uc3VtZXIgaXMgbm90IGd1YXJhbnRlZWQgdG8gcmVz
b2x2ZSB0aGUgY29ycmVjdCBJT0RFRi1Eb2N1bWVudC4gR29pbmcgYSBzdGVwIGZ1cnRoZXIsIGl0
IHdvdWxkIGFsc28gYmUgcG9zc2libGUgdG8gaW5jbHVkZSBhIGRzaWc6U2lnbmF0dXJlIGVsZW1l
bnQgd2l0aGluIHRoZSBSaWQgZWxlbWVudCBzbyB0aGF0IGFsbCBpbmZvcm1hdGlvbiBpcyBmdWxs
eSBjb250YWluZWQgd2l0aGluIHRoZSBSSUQgZW52ZWxvcGUgKHNlZSBzZWN0aW9uIDMuMTAgb2Yg
dGhlIFNDQVAgMS4yIHNwZWNpZmljYXRpb24gdG8gc2VlIGhvdyB0aGlzIGlzIGRvbmUgd2l0aGlu
IHRoZSBjb250ZXh0IG9mIFNDQVAgMS4yIGRvY3VtZW50czogaHR0cDovL2NzcmMubmlzdC5nb3Yv
cHVibGljYXRpb25zL25pc3RwdWJzLzgwMC0xMjYtcmV2Mi9TUDgwMC0xMjZyMi5wZGYpLiANCg0K
QW5vdGhlciB3YXkgdG8gZW5zdXJlIHRoYXQgdGhlIElPREVGLURvY3VtZW50IGlzIHJlc29sdmVk
IGNvcnJlY3RseSBpcyB0byBmb3JtYWxseSBzcGVjaWZ5IHRoYXQgdGhlIGlvZGVmOkluY2lkZW50
SWQgaW4gdGhlIFJJRCBkb2N1bWVudCBwb2ludHMgdG8gdGhlIGFzc29jaWF0ZWQgaW9kZWY6SW5j
aWRlbnRJRCBpbiB0aGUgSU9ERUYgZG9jdW1lbnQuIEkgdGhpbmsgdGhpcyBsb2dpYyBpcyBpbXBs
aWNpdCBpbiB0aGUgY3VycmVudCBkcmFmdCwgYnV0IGl0IHdvdWxkIGJlIGhlbHBmdWwgdG8gY2Fs
bCBpdCBvdXQgZm9ybWFsbHkuIEFsc28sIGkgYW0gbm90IHBvc2l0aXZlIHRoaXMgd2lsbCBhbHdh
eXMgd29yayBzaW5jZSB0aGUgaW9kZWY6SW5jaWRlbnRJZCBpcyBub3QgYSByZXF1aXJlZCBlbGVt
ZW50IGluIHRoZSAgUklEUG9saWN5IGVsZW1lbnQuDQoNClRvIHByb3ZpZGVkIGEgc29tZXdoYXQg
cmVsYXRlZCBleGFtcGxlIGZyb20gdGhlIFNDQVAgc3BhY2UsIHRoZSBTQ0FQIHNwZWNpZmljYXRp
b24gc3RhcnRlZCBvdXQgd2l0aCBhbGwgb2YgdGhlIGRpc3BhcmF0ZSBjb21wb25lbnRzIChlLmcu
LCBYQ0NERiwgT1ZBTCwgQ1BFLCBldGPigKYpIGJlaW5nIGRpc3BhcmF0ZSBYTUwgZG9jdW1lbnRz
IGFuZCB0aGUgb25seSBydWxlIHdhcyB0aGF0IHRoZXkgYWxsIGhhZCB0byBiZSBpbiB0aGUgc2Ft
ZSBaSVAgYnVuZGxlIHRvIGFsbG93IGEgY29uc3VtZXIgdG8gY29tcGlsZSB0aGUgdGhlIGNyb3Nz
LWRvY3VtZW50IHJlbGF0aW9uc2hpcHMgaW4gbWVtb3J5LiBIb3dldmVyLCB0aGUgbGFjayBvZiBm
b3JtYWxpemF0aW9uIGNhdXNlZCBwcm9ibGVtcyBmb3IgY29uc3VtZXJzOyB0aGUgbmV3IHN0cmF0
ZWd5IChpbiBTQ0FQIDEuMiwgcmVmZXJlbmNlZCBhYm92ZSkgaXMgdG8gaW5jbHVkZSBhbGwgdGhl
IGRpc3BhcmF0ZSBjb21wb25lbnRzIGluIGEgaGlnaGVyLWxldmVsIGVsZW1lbnQgbmFtZWQgJ2Rh
dGEtc3RyZWFtJyB0aGF0IHdyYXBzIGV2ZXJ5dGhpbmcgaW4gb25lIGRvY3VtZW50IHRvIHByb3Zp
ZGUgbW9yZSBjb250ZXh0IGFuZCBtYWtlIHRoZSBjcm9zcy1jb21wb25lbnQgcmVsYXRpb25zaGlw
cyBtb3JlIGV4cGxpY2l0Lg0KDQpBcyBhIHNpZGUgbm90ZSwgdGhlIGV4YW1wbGVzIGluIHNlY3Rp
b24gNiBvZiB0aGUgUklEIGRyYWZ0IGluY2x1ZGUgeG1sIGNvbW1lbnRzIChpLmUuLCAiPCEtLSAt
LT4iKSBiZXR3ZWVuIHRoZSBpb2RlZi1yaWQ6UklEIGFuZCBpb2RlZjpJT0RFRi1Eb2N1bWVudCBy
b290IGVsZW1lbnRzLCB3aGljaCBsZWFkcyB0aGUgcmVhZGVyIHRvIGJlbGlldmUgdGhhdCB0aGVy
ZSBpcyBzb21lIGhpZ2hlci1sZXZlbCByb290IGVsZW1lbnQgdGhhdCB3cmFwcyB0aGVzZSBlbGVt
ZW50cyAoYW5kIHRoZSBYTUwgZHNpZyBFbnZlbG9wZSksIGJ1dCBJIGFtIGd1ZXNzaW5nIHRoYXQg
d2FzIG5vdCBpbnRlbnRpb25hbC4NCg0KVGhpcyBoYXMgcHJvYmFibHkgYWxsIGJlZW4gZGlzY3Vz
c2VkIGluIGRldGFpbCBhdCBzb21lIHBvaW50IGluIFJJRCdzIGhpc3Rvcnkgc28gSSBhcG9sb2dp
emUgaWYgSSBhbSByZXBlYXRpbmcgb2xkIGlzc3Vlcy4NCg0KLVBhdWwNCl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IG1pbGUtYm91bmNlc0BpZXRmLm9yZyBb
bWlsZS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQ2ljaG9uc2tpLCBQYXVsIFtwYXVs
LmNpY2hvbnNraUBuaXN0Lmdvdl0NClNlbnQ6IFN1bmRheSwgRGVjZW1iZXIgMDQsIDIwMTEgMzoz
OCBQTQ0KVG86IGthdGhsZWVuLm1vcmlhcnR5QGVtYy5jb207IG1pbGVAaWV0Zi5vcmcNClN1Ympl
Y3Q6IFJlOiBbbWlsZV0gV0cgTGFzdCBjYWxsDQoNCkhpIEthdGhsZWVuLA0KDQpJIGp1c3QgaGF2
ZSBhIGZldyBtaW5vciBjb21tZW50cyBiZWxvdyByZWxhdGluZyB0byB0aGUgIlJlYWwtdGltZSBJ
bnRlci1uZXR3b3JrIERlZmVuc2UgKFJJRCkgZHJhZnQtbW9yaWFydHktbWlsZS1yZmM2MDQ1LWJp
cy0wMi50eHQiIGRvY3VtZW50LiBPdGhlciB0aGFuIHRoZXNlIGNvbW1lbnRzLCBib3RoIGRvY3Vt
ZW50cyBsb29rIGdvb2QgdG8gbWUuDQoNClNlY3Rpb246IEludHJvZHVjdGlvbiwgZmlmdGggcGFy
YWdyYXBoOg0KDQpGb3IgdGhlIHNlbnRlbmNlICJUaGUgUklEIHNjaGVtYSBhY3RzIGFzIGFuIFhN
TCBlbnZlbG9wZSB0byBzdXBwb3J0IHRoZSBjb21tdW5pY2F0aW9uIG9mIElPREVGIGRvY3VtZW50
cyBmb3IgZXhjaGFuZ2luZyBvciB0cmFjaW5nIGluZm9ybWF0aW9uIHJlZ2FyZGluZyBpbmNpZGVu
dHMiLiBJdCBtYXkgaGVscCBjbGFyaWZ5IHRoaW5ncyBpZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4g
J2VudmVsb3BlJyB3YXMgdXNlZCBoZXJlLCBzaW5jZSBbdG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQg
UklEIGRvY3VtZW50cyB3aWxsIGFjdHVhbGx5IGVudmVsb3BlIElPREVGIGRvY3VtZW50cy4gSG93
ZXZlciwgYmFzZWQgb24gdGhlIGV4YW1wbGVzIGFuZCBzY2hlbWEsIHRoZSBpbnRlbmRlZCB1c2Fn
ZSBpcyBmb3IgYSBSSUQgZG9jdW1lbnQgdG8gYmUgYSBwZWVyIHRvIElPREVGIGluIHRoZSB0cmFu
c3BvcnQgc2NlbmFyaW9zLCBzbyBubyBlbnZlbG9waW5nIGlzIG9jY3VycmluZy4gV291bGQgc3Vn
Z2VzdCBhIHBocmFzZSBsaWtlICJUaGUgUklEIHNjaGVtYSBkZWZpbmVzIGNvbW11bmljYXRpb24t
c3BlY2lmaWMgbWV0YWRhdGEgdG8gc3VwcG9ydCB0aGUgY29tbXVuaWNhdGlvbiBvZiAuLi4uIg0K
DQpTZWN0aW9uOiBJbnRyb2R1Y3Rpb24sIGZpZnRoIHBhcmFncmFwaDoNCg0KSW4gdGhlIHNlY29u
ZCB0byBsYXN0IHNlbnRlbmNlLCB0aGUgY2l0YXRpb24gW1JGQzYwNDYtYmlzXSBpcyBkdXBsaWNh
dGVkLg0KDQpTZWN0aW9uIDMuMSwgZmlyc3QgcGFyYWdyYXBoOg0KDQpJIHRoaW5rIHRoZXJlIG1h
eSBiZSBhIHR5cG8gaW4gdGhlIHN0YXJ0IG9mIHRoZSBzZW50ZW5jZTogIlJJRCBwcm92aWRlcyBh
IHN0YW5kYXJkIHByb3RvY29sIGFuZCBmb3JtYXQgaXMgcmVxdWlyZWQgdG8gZW5zdXJlIiwgcHJv
YmFibHkgc2hvdWxkIGJlICJSSUQgcHJvdmlkZXMgYSBzdGFuZGFyZCBwcm90b2NvbCBhbmQgZm9y
bWF0IHRoYXQgaXMgcmVxdWlyZWQgdG8gZW5zdXJlIi4gKGFkZGVkICd0aGF0JykuDQoNClNlY3Rp
b24gNCwgZmlyc3QgcGFyYWdyYXBoOg0KDQpJbiB0aGUgZmlyc3Qgc2VudGVuY2UsIGl0IG1heSBi
ZSBoZWxwZnVsIHRvIGFkZCBjbGFyaWZpY2F0aW9uIHJlbGF0aW5nIHRvIHRoZSBwaHJhc2UgIlJJ
RCBleHRlbnNpb24iLiBTcGVjaWZpY2FsbHksIHRoZSB0aGluZyB0aGF0IFJJRCBpcyBleHRlbmRp
bmcuIElmIHlvdSBtZWFuIHRoYXQgUklEIGlzIGV4dGVuZGluZyBJT0RFRiwgSSBhbSBub3Qgc3Vy
ZSBJIGxpa2UgdGhlIHRlcm0gJ2V4dGVuZCcsIHNpbmNlIFJJRCBpcyByZWFsbHkganVzdCBpbXBv
cnRpbmcgdGhlIElPREVGIGRhdGEgbW9kZWwgYW5kIHVzaW5nIHNvbWUgb2YgdGhlIGVsZW1lbnRz
IHRoYXQgSU9ERUYgZGVmaW5lcywgYnV0IG5vdCBleHRlbmRpbmcgYW55IG9mIHRoZSBJT0RFRiB0
eXBlcywgdGh1cyB0aGUgd29yZCAnZXh0ZW5kJyBtYXkgY29uZnVzZSBkZXZlbG9wZXJzIHRoYXQg
YXJlIHJlYWRpbmcgdGhlIHNwZWMuDQoNClNlY3Rpb24gNCwgc2Vjb25kIHBhcmFncmFwaDoNCg0K
UmVsYXRpbmcgdG8gdGhlIGZpcnN0IHNlbnRlbmNlLCBqdXN0IHJlcGVhdGluZyBteSBwcmV2aW91
cyBjb21tZW50IGZyb20gdGhlIGludHJvIHNlY3Rpb246ICJJdCBtYXkgaGVscCBjbGFyaWZ5IHRo
aW5ncyBpZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4gJ2VudmVsb3BlJyB3YXMgdXNlZCBoZXJlLCBz
aW5jZSBbdG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQgUklEIGRvY3VtZW50cyB3aWxsIGFjdHVhbGx5
IGVudmVsb3BlIElPREVGIGRvY3VtZW50cy4gSG93ZXZlciwgYmFzZWQgb24gdGhlIGV4YW1wbGVz
IGFuZCBzY2hlbWEsIHRoZSBpbnRlbmRlZCB1c2FnZSBpcyBmb3IgYSBSSUQgZG9jdW1lbnQgdG8g
YmUgYSBwZWVyIHRvIElPREVGIGluIHRoZSB0cmFuc3BvcnQgc2NlbmFyaW9zLCBzbyBubyBlbnZl
bG9waW5nIGlzIG9jY3VycmluZy4gIg0KDQpTZWN0aW9uIDY6DQoNCk9uZSBvdmVyYWxsIGNvbW1l
bnQgZm9yIHRoZSBkaWFncmFtcyBpbiB0aGlzIHNlY3Rpb246IGl0IG1heSBoZWxwIHRvIGluY2x1
ZGUgdGhlIElQIGFkZHJlc3Mgb2YgInRoaW5ncyIgKGUuZy4sIEF0dGFjayBEZXN0LCBTUC0xLCBT
UC0yLCBldGMuLikgaWYgcG9zc2libGUgdG8gaGVscCByZWFkZXJzIHVuZGVyc3RhbmQgdGhlIGV4
YW1wbGUgWE1MLCBzcGVjaWZpY2FsbHkgdGhlIHBsYWNlcyB3aGVyZSBJUCBhZGRyZXNzZXMgYXJl
IGxpc3RlZC4NCg0KU2VjdGlvbiA2LjIsIGRpYWdyYW06DQoNCkEgcmVzdWx0IG1lc3NhZ2UgaXMg
c2hvd24gaW4gdGhlIGRpYWdyYW0sIGJ1dCBubyByZXN1bHQgeG1sIGlzIHByb3ZpZGVkIGluIHRo
ZSBmb2xsb3dpbmcgc3ViLXNlY3Rpb25zLiBBIFJlcXVlc3RBdXRob3JpemF0aW9uIGlzIGxpc3Rl
ZCBpbnN0ZWFkLiBJZiB0aGUgc3ViLXNlY3Rpb25zIGFyZSBpbnRlbmRlZCB0byBkZXNjcmliZSB0
aGUgZGlhZ3JhbSB0aGlzIHNob3VsZCBiZSBjaGFuZ2VkLg0KDQpTZWN0aW9uIDYuNC4xLCBmaXJz
dCBwYXJhZ3JhcGgsDQoNClRoaXMgcGFyYWdyYXBoIGxpc3RzIHRoZSBkaWZmZXJlbnQgdHlwZXMg
b2YgZm9ybWF0cyB0aGUgSW5jaWRlbnRRdWVyeSBtYXkgYmUgc2VudCBhcywgYnV0IGRvZXMgbm90
IHNheSB3aGF0IHRoZSBleGFtcGxlIHhtbCBpbGx1c3RyYXRlcyAoZS5nLiwgd2hhdCB0eXBlKS4g
U3VnZ2VzdCBhZGRpbmcgc29tZSB0ZXh0IHRvIHNlY29uZCBzZW50ZW5jZSBzYXlpbmcgdGhhdCB0
aGUgdHlwZSBkZXNjcmliZWQgaW4gdGhhdCBzZW50ZW5jZSBpcyBpbGx1c3RyYXRlZCBpbiB0aGUg
ZXhhbXBsZSBYTUwgKGF0IGxlYXN0IEkgdGhpbmsgaXQgaXMpLg0KDQpTZWN0aW9uIDcsIHNjaGVt
YS4NCg0KRm9yIHRoZSBmaXJzdCBpbXBvcnQgKHVybjppZXRmOnBhcmFtczp4bWw6bnM6aW9kZWYt
MS4wKSwgZ3Vlc3NpbmcgdGhpcyBpcyBzdXBwb3NlZCB0byBwb2ludCB0byBJT0RFRiBzY2hlbWEg
YW5kIG5vdCBJT0RFRi1SSUQ677+9aHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy94bWwt
cmVnaXN0cnkvc2NoZW1hL2lvZGVmLTEuMC54c2QuDQoNClRoYW5rcywNClBhdWwNCg0KDQoNCg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogbWlsZS1ib3Vu
Y2VzQGlldGYub3JnIFttaWxlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBrYXRobGVl
bi5tb3JpYXJ0eUBlbWMuY29tIFtrYXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tXQ0KU2VudDogRnJp
ZGF5LCBEZWNlbWJlciAwMiwgMjAxMSAzOjExIFBNDQpUbzogbWlsZUBpZXRmLm9yZw0KU3ViamVj
dDogW21pbGVdIFdHIExhc3QgY2FsbA0KDQpGWUkgLSB0d28gZG9jdW1lbnRzIHdyYXAgdXAgV29y
a2luZyBHcm91cCBMYXN0IENhbGwgKFdHTEMpIGF0IGVuZCBvZiBkYXkgb24gTW9uZGF5LiAgUGxl
YXNlIHNoYXJlIHlvdXIgY29tbWVudHMgb24gdGhlIGxpc3Qgb3IgdGhhdCB5b3UgaGF2ZSByZWFk
IHRoZSBkb2N1bWVudHMgYW5kIGhhdmUgbm8gY29tbWVudHMvaXNzdWVzLg0KDQpUaGFuayB5b3Ug
YW5kIGhhdmUgYSBuaWNlIHdlZWtlbmQhDQpLYXRobGVlbg0KDQoNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1pbGUgbWFpbGluZyBsaXN0DQptaWxl
QGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pbGUNCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQptaWxlIG1haWxp
bmcgbGlzdA0KbWlsZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9taWxlDQo=

From trammell@tik.ee.ethz.ch  Mon Dec  5 08:53:13 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 56C6121F8C74 for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 08:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwlVXFncTFTm for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 08:53:13 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id C480121F8AE9 for <mile@ietf.org>; Mon,  5 Dec 2011 08:53:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 510F7D9304 for <mile@ietf.org>; Mon,  5 Dec 2011 17:53:11 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0pX7ELCP-tZC for <mile@ietf.org>; Mon,  5 Dec 2011 17:53:11 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 24F6CD9300 for <mile@ietf.org>; Mon,  5 Dec 2011 17:53:11 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Dec 2011 17:53:10 +0100
Message-Id: <5DE5E2BE-28FC-4AD7-A01A-613F1C211FF8@tik.ee.ethz.ch>
To: mile@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [mile] WGLC concluded on draft-ietf-mile-rfc6045-bis-01
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 16:53:13 -0000

Greetings, all,

The Working Group Last Call on draft-ietf-mile-rfc6045-bis-01 has =
concluded.

The comments received would appear to require a new revision of the =
draft before sending it to the IESG.=20

Best regards,

Brian (as chair)=

From kathleen.moriarty@emc.com  Mon Dec  5 12:58:28 2011
Return-Path: <kathleen.moriarty@emc.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 CD1D421F85C7; Mon,  5 Dec 2011 12:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.88
X-Spam-Level: 
X-Spam-Status: No, score=-4.88 tagged_above=-999 required=5 tests=[AWL=-0.736,  BAYES_00=-2.599, FRT_ADOBE2=2.455, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGPTcIMQH-Xk; Mon,  5 Dec 2011 12:58:27 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 119CA21F8BD7; Mon,  5 Dec 2011 12:58:26 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5KwGKc024381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2011 15:58:16 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Mon, 5 Dec 2011 15:58:03 -0500
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5Kw2qg005346; Mon, 5 Dec 2011 15:58:02 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Mon, 5 Dec 2011 15:58:02 -0500
From: <kathleen.moriarty@emc.com>
To: <kathleen.moriarty@emc.com>, <masinter@adobe.com>, <sm+ietf@elandsys.com>,  <apps-discuss@ietf.org>, <draft-ietf-mile-rfc6045-bis.all@tools.ietf.org>
Date: Mon, 5 Dec 2011 15:58:00 -0500
Thread-Topic: Request for review: draft-ietf-mile-rfc6045-bis-01
Thread-Index: Acyx2y1gEK186n+jT7SbNHZ7d0jy1QAC1hmwAAcPEDAAXgE20AAFcQ/w
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E8C62@MX06A.corp.emc.com>
References: <6.2.5.6.2.20111203082441.0a251830@elandnews.com>, <C68CB012D9182D408CED7B884F441D4D0612042FE3@nambxv01a.corp.adobe.com> <AE31510960917D478171C79369B660FA0E1A7B33DD@MX06A.corp.emc.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] Request for review: draft-ietf-mile-rfc6045-bis-01
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 20:58:28 -0000

Copying MILE

-----Original Message-----
From: Moriarty, Kathleen
Sent: Monday, December 05, 2011 3:47 PM
To: Moriarty, Kathleen; Larry Masinter; SM; apps-discuss@ietf.org; draft-ie=
tf-mile-rfc6045-bis.all@tools.ietf.org
Subject: RE: Request for review: draft-ietf-mile-rfc6045-bis-01

Hello Larry,

Thank you again for your review.  Please let me know if the responses below=
 adequately meet your concerns.  If so, I will update the document accordin=
gly.  There are no proposed changes that are technical in nature.  I tried =
to separate out each question to make it a bit easier to read...


Minor issues:
The "Updates" will be changed to "Obsoletes" in the updated version.  It wa=
s listed this way in the 00 version, I'll make sure this is in the template=
 for the document to prevent this from happening.

The document does move from informational to standards track.  Basically, t=
his was a working group item in INCH.  We finalized the work and the workin=
g group closed before the documents were published.  Because of the delay, =
they were published as informational.  Once they were published, interest i=
ncreased and it is part of the reason driving it for the move for standards=
 track.  The ability to automate the exchange of incident information in a =
secure way with policy considerations is greatly needed and this specificat=
ion is getting the most traction to solve the problem.

As mentioned in the previous response, the changes from RFC6045 to RFC6045-=
bis are included at the end of the introduction.  Please let me know if thi=
s addresses your concern.



Details:
Mysterious labels:
ENUM is for enumerated types, building from RFC 5070 which previously defin=
es:
" 2.7.  Enumerated Types

   Enumerated types are represented by the ENUM data type, and consist
   of an ordered list of acceptable values.  Each value has a
   representative keyword.  Within the IODEF schema, the enumerated type
   keywords are used as attribute values.

   The ENUM data type is implemented as a series of "xs:NMTOKEN" in the
   schema."

For attributes that use the ENUM type, It looks like I have "One" listed wh=
ere "REQUIRED" should be.  This is correct in the schema and I will update =
the text in the appropriate subsections of 4 to correct this issue.

Would you like to see the definitions from IODEF included in this document =
or just referenced as is the case now?

Right now, there is section 3.4 that points to IODEF:
"3.4. RID Data Types

   RID is derived from the IODEF data model and inherits all of the data
   types defined in the IODEF model.  One data type is added by RID:
   BOOLEAN."


I'll take the answer for this and replicate it for other data types as need=
ed (definitions, etc.) for how you would like to see it handled.
__________

Next issue is with terms, with one example provided:
The bulk of the document contains what seem like definitions of terms in a =
vocabulary, such as:

> ClientToSP.  An enterprise initiated the request to their service provide=
r.

This does apply out to any use case where the client can be anything from a=
n individual to an enterprise.  Service provider is intended to be broad to=
 cover many use cases.  I will add more verbiage in this section to clarify=
 the intent.  The objective is really to have this used where there is a cl=
ient to provider relationship that may be bound by agreements and SLAs wher=
e there is typically some trust established through those relationships.  T=
his can also apply to a client and vendor scenario as the vendor may be pro=
viding a service.  I'll add the same text to the SPToClient definition as w=
ell.

Current text:
> ClientToSP.  An enterprise initiated the request to their service provide=
r.

Proposed text:
> ClientToSP.  A client initiated the request to their service provider (SP=
).  A client may be an individual, enterprise, or other type of entity (gov=
ernment, commercial, education, etc.).  A service provider may be a network=
, telecommunications, cloud, infrastructure, or other type of service provi=
der where a client to vendor relationship has been established.  The client=
 to vendor relationship will typically have established contracts or agreem=
ents to define expectations and trust relationships.

2.  SPToClient.  A service provider (SP) initiated a RID request or
    report to a client.  A client may be an individual, enterprise, or othe=
r type of entity (government, commercial, education, etc.).  A service prov=
ider may be a network, telecommunications, cloud, infrastructure, or other =
type of service provider where a client to vendor relationship has been est=
ablished.  The client to vendor relationship will typically have establishe=
d contracts or agreements to define expectations and trust relationships.

3.  IntraConsortium.  Incident information that should have no
          restrictions within the boundaries of a consortium with the
          agreed-upon use and abuse guidelines. A consortium is a well defi=
ned group with established members and trust relationships specific to shar=
ing within that group.  A consortium would typically define the types of da=
ta that can be shared in advance, expectations on protecting that data, as =
well as having established contractual agreements.  Examples of Consortiums=
 may include industry focused sharing communities (Financial, government, r=
esearch and education, etc.) or cross industry sharing communities (for ins=
tance, organizations within local proximity that form a sharing group).

4.  PeerToPeer.  Incident information that should have no
          restrictions between two peers but may require further
          evaluation before continuance beyond that point with the
          agreed-upon use and abuse guidelines.  PeerToPeer communications =
may involve any two individuals or entities that decide to share informatio=
n directly with each other.

5.  BetweenConsortiums.  Incident information that should have no
          restrictions between consortiums that have established agreements=
 or contracts with use and abuse guidelines.  BetweenConsortiums is used wh=
en two Consortiums (as defined in IntraConsortium above) share data.  The t=
ypes of data that can be shared BetweenConsortiums should be identified in =
their agreements and contracts along with expectations on how that data sho=
uld be handled and protected.

_______

> What is a "National Boundary"? Is it a legal jurisdiction? What about sec=
urity incidents where there is some dispute about what constitutes a "natio=
nal boundary"? How would one use this value?

Proposed additional text is in quotes.  This does not change the usage, but=
 better explains the capabilities and relationship to IODEF and extensions =
as well as agreements between entities.

     6.  AcrossNationalBoundaries.  This selection must be set if the
          message type will cross national boundaries.  "AcrossNationalBoun=
daries is used when data shared may have additional restrictions for handli=
ng and protection based on the type of data and where it resides.  The IODE=
F document included, as well as any extensions, with the RID message should=
 indicate the specific restrictions to be considered.  The national boundar=
y may be defined by existing regulations or other legal agreements specific=
 to a defined region.  The use of this AcrossNationalBoundaries is not lega=
lly binding unless contracts and agreements for entities who share data hav=
e deemed it as such through additional definitions that may include associa=
ted handling and protection requirements."  There could be
          instances of TraceRequest messages where that may not be known
          in advance, but should be known at the instance where
          boundaries are crossed during the investigation.  This must
          also be set if the security requirements of the request is
          based upon regulations of a specific nation that may not apply
          to all nations.  The stricter requirements should be upheld.
          This is different from the "BetweenConsortiums" setting since
          it may be possible to have multiple nations as members of the
          same consortium, and this option must be selected if the
          traffic is of a type that may have different restrictions in
          other nations.
_______________
Next issue was with "LawEnforcement"
>From Larry, " Again, many undefined terms, and no particular way, indicatio=
n, hint, of how to clarify them, when they apply, what constitutes a "local=
 government" across the world, etc.   What is a "National Boundary"? Is it =
a legal jurisdiction? What about security incidents where there is some dis=
pute about what constitutes a "national boundary"? How would one use this v=
alue? If you expect consistent processing of incident reports from multiple=
 sources, don't you need to insure common understanding of the terms? And i=
f you don't, why is it standards track?"

The working group discussed this very issue on the mailing list.  I think w=
hat is needed is some additional language in the draft to better explain ho=
w this is used.  This term was intentionally left ambiguous as the IODEF do=
cument included would have the specific contact information of the group th=
e sender interpreted as LawEnforcement.  This could be national or local po=
lice or even a government group like the FBI in the US.  Since this could d=
iffer around the world, the working group decided that the high level term =
that may affect how they protect the data and the extent to which it can be=
 shared was good for the RID level.  When you look at the IODEF document, t=
his will include the specific contact information of the recipient (much mo=
re granular than the type of Law Enforcement).


Current Text:
>   LawEnforcement.  This option is used when incident information is excha=
nged with LawEnforcement, local government, or other authorities assisting =
with an investigation.  If the law enforcement agency resides within a diff=
erent nation that the sending entity, the "crossNationalBoundaries" enumera=
tion MUST also be set .

Proposed Text:
>   LawEnforcement.  This option is used when incident information is excha=
nged with LawEnforcement, local government, or other authorities assisting =
with an investigation.  The usage of this value is interpreted by the sende=
r, and that interpretation may vary in regions of the world.  This value is=
 intentionally broad.  More detailed information on the receiving entity is=
 maintained in the Contact class of the IODEF document.  If the law enforce=
ment agency resides within a different nation that the sending entity, the =
"AcrossNationalBoundaries" enumeration MUST also be set.
________

The types for TrafficRegion was also raised as a concern, but not as explic=
itly as the areas above.

In looking at these again, the only change I would suggest at this point is=
 the first sentence of Attack.

Current text:
1.  Attack.  This option should only be selected if the traffic is
          related to a network-based attack.

Proposed text:
1.  Attack.  This option should only be selected if the traffic is
          related to an information security incident or attack.

________

You also raised a question on extensibility.  The WG decided that we wanted=
 to restrict this to the ability to add enumerated values, either through o=
fficial means (standards document) or to sharing communities who may extend=
 to add their own values.  Throughout the schema, there is an ext-value inc=
luded, following the established extension mechanism for IODEF.  It points =
to the definition in RFC5070, section 5.1.  Does this address your concern =
or would you prefer to see the text included in this document.

I believe this addresses the outstanding questions.  Please let me know if =
you agree on the proposed text and how each question is addressed.

Thank you,
Kathleen



-----Original Message-----
From: Moriarty, Kathleen
Sent: Saturday, December 03, 2011 4:44 PM
To: Larry Masinter; SM; apps-discuss@ietf.org; draft-ietf-mile-rfc6045-bis.=
all@tools.ietf.org
Subject: RE: Request for review: draft-ietf-mile-rfc6045-bis-01

Hello Larry,

Thank you very much for the detailed review!  I have a couple of quick ques=
tions and will address your concerns with proposed text soon (WGLC ends on =
Monday, so I can update the document then to include your suggested changes=
 along with any others received).

Can you let me know if the section at the end of the introduction adequatel=
y addresses your request for the list of changes from RFC6045?  If not, wha=
t additional detail or formatting would be helpful to clear up this request=
?

I will go back through the terminology again to clarify terms better as req=
uested and to find out if the changes address your concerns (tomorrow or Mo=
nday via email to this list).

A little background:  In this space, groups share data using high level mar=
kers to indicate what groups you can share the data with and if it is sensi=
tive.  The markers in RID are more specific than what is used for sharing v=
ia email (etc.), but a mapping is easily created.  The "Traffic Light Proto=
col" just marks incidents as "red", "yellow", "green", and "white" which in=
tends to cover both of those areas.  Organizations decide how they want to =
share and mark it as such with policy agreements.  The policy part will hap=
pen more between groups before they share data.  Sharing in practice occurs=
 when parties know each other and have built a trust relationship or there =
is a client-vendor relationship.  Hopefully this will expand in the future,=
 but that's how it works now.  It is a delicate balance where parties may w=
ant the ability to interpret the terms and map to their policy and create s=
haring agreements.  Local for instance could be a region defined by a parti=
cular sharing group.  The ISACs int he US share across a particular industr=
y, but then there are other groups like the ACSC in the greater Boston area=
 that is cross industry and will limit participation to about 30 organizati=
ons for fear that if they get too large, people won't trust (because they d=
on't know the others int he group) and hence won't share.

Thanks again!
Kathleen

________________________________________
From: Larry Masinter [masinter@adobe.com]
Sent: Saturday, December 03, 2011 2:21 PM
To: SM; Moriarty, Kathleen; apps-discuss@ietf.org; draft-ietf-mile-rfc6045-=
bis.all@tools.ietf.org
Subject: RE: Request for review: draft-ietf-mile-rfc6045-bis-01

Document:  draft-ietf-mile-rfc6045-bis-01
Title: Real-time Inter-network Defense
Reviewer: Larry Masinter
Review Date: 12/3/2011

Summary:
This draft is not ready for publication as a Proposed Standard and should b=
e revised before publication.

Major issues:
The document defines a language for describing a security incident intended=
 for exchange between services or service providers, but the terminology us=
ed for describing incidents and the extensibility and refinement of that te=
rminology is not clear and doesn't seem to be managed.
But this is a preliminary review about the status & intent...

Minor issues:
The status of the document seems to be confusing or incorrect.  The introdu=
ction says "This document moves Real-time Inter-network Defense (RID) [RFC6=
045]    to Historic status as it provides minor updates."  And the status l=
ists that it "updates" RFC 6045.

In fact, the document seems to be a revision of all of RFC 6045
 http://tools.ietf.org/rfcdiff?url1=3Drfc6045&url2=3Ddraft-ietf-mile-rfc604=
5-bis-01
which moves from "Informational"  to Standards Track.
There doesn't seem to be a summary of "Changes from RFC 6045" which explain=
s what changed, based on actual practice..


Details:

There are several namespaces of enumerated values ("TrafficType", "PolicyRe=
gion", ...) which seem to depend on a common understanding of the meaning o=
f the terminology, but which do not define the terms sufficiently (in my op=
inion) for anyone to know how to use this.

To pick a couple of examples:

PolicyRegion starts out with "region", and there are mysterious labels. "On=
e. Enum."
There is likely a convention in the document for this, but I think unless i=
t is an explicit table it is better to be more specific.

The bulk of the document contains what seem like definitions of terms in a =
vocabulary, such as:

> ClientToSP.  An enterprise initiated the request to their service provide=
r.

But the terms "enterprise" and "service provider" are defined ... where? Is=
 my home network an enterprise? What is the scope or scale of an enterprise=
?  Could different service providers define what an "enterprise" is differe=
ntly? What is the utility of this value in an incident report?

>   LawEnforcement.  This option is used when incident information is excha=
nged with LawEnforcement, local government,
>  or other authorities assisting with an investigation.  If the law enforc=
ement agency resides within a different nation that
>  the sending entity, the "crossNationalBoundaries" enumeration MUST also =
be set .

Again, many undefined terms, and no particular way, indication, hint, of ho=
w to clarify them, when they apply, what constitutes a "local government" a=
cross the world, etc.   What is a "National Boundary"? Is it a legal jurisd=
iction? What about security incidents where there is some dispute about wha=
t constitutes a "national boundary"? How would one use this value? If you e=
xpect consistent processing of incident reports from multiple sources, don'=
t you need to insure common understanding of the terms? And if you don't, w=
hy is it standards track?

The extensibility of the protocol is unclear... how are these terms clarifi=
ed, how do they evolve, what happens when different organizations interpret=
 the terms differently? Is there a registry? Can the set of terms change?

I understand the desire to pass semantic information between multiple parti=
es about security incidents, but I think the fundamental problem is in the =
management of the evolution of a common understanding of the terminology an=
d namespace supplied.

Larry
--
http://larry.masinter.net



From kathleen.moriarty@emc.com  Mon Dec  5 14:27:54 2011
Return-Path: <kathleen.moriarty@emc.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 4FCFA21F8B9B for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 14:27:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.985
X-Spam-Level: 
X-Spam-Status: No, score=-5.985 tagged_above=-999 required=5 tests=[AWL=0.614,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6aAVHg1DTHAy for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 14:27:53 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4713321F8B94 for <mile@ietf.org>; Mon,  5 Dec 2011 14:27:52 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5MRpUP016301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2011 17:27:52 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 5 Dec 2011 17:27:41 -0500
Received: from mxhub19.corp.emc.com (mxhub19.corp.emc.com [10.254.93.48]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5MRdB6032495; Mon, 5 Dec 2011 17:27:39 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub19.corp.emc.com ([10.254.93.48]) with mapi; Mon, 5 Dec 2011 17:27:39 -0500
From: <kathleen.moriarty@emc.com>
To: <paul.cichonski@nist.gov>, <mile@ietf.org>
Date: Mon, 5 Dec 2011 17:27:37 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiwBlhl60ADW1HQA=
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E8CBF@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com> <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 22:27:54 -0000

SGVsbG8gUGF1bCwNCg0KVGhhbmsgeW91IGZvciB0YWtpbmcgdGhlIHRpbWUgdG8gcmV2aWV3IHRo
ZSBkb2N1bWVudCBpbiBkZXRhaWwuICBJJ2xsIGFuc3dlciB5b3VyIHF1ZXN0aW9ucyBpbiBsaW5l
IGJlbG93IGFuZCBtYWtlIHRoZSBhcHByb3ByaWF0ZSBjaGFuZ2VzIGluIHRoZSB1cGRhdGVkIHZl
cnNpb24gb2YgdGhlIGRvY3VtZW50Lg0KDQpCZXN0IHJlZ2FyZHMsDQpLYXRobGVlbiAoYXMgZWRp
dG9yKQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQ2ljaG9uc2tpLCBQYXVs
IFttYWlsdG86cGF1bC5jaWNob25za2lAbmlzdC5nb3ZdIA0KU2VudDogU3VuZGF5LCBEZWNlbWJl
ciAwNCwgMjAxMSAzOjM4IFBNDQpUbzogTW9yaWFydHksIEthdGhsZWVuOyBtaWxlQGlldGYub3Jn
DQpTdWJqZWN0OiBSRTogV0cgTGFzdCBjYWxsDQoNCkhpIEthdGhsZWVuLA0KDQpJIGp1c3QgaGF2
ZSBhIGZldyBtaW5vciBjb21tZW50cyBiZWxvdyByZWxhdGluZyB0byB0aGUgIlJlYWwtdGltZSBJ
bnRlci1uZXR3b3JrIERlZmVuc2UgKFJJRCkgZHJhZnQtbW9yaWFydHktbWlsZS1yZmM2MDQ1LWJp
cy0wMi50eHQiIGRvY3VtZW50LiBPdGhlciB0aGFuIHRoZXNlIGNvbW1lbnRzLCBib3RoIGRvY3Vt
ZW50cyBsb29rIGdvb2QgdG8gbWUuDQoNClNlY3Rpb246IEludHJvZHVjdGlvbiwgZmlmdGggcGFy
YWdyYXBoOg0KDQpGb3IgdGhlIHNlbnRlbmNlICJUaGUgUklEIHNjaGVtYSBhY3RzIGFzIGFuIFhN
TCBlbnZlbG9wZSB0byBzdXBwb3J0IHRoZSBjb21tdW5pY2F0aW9uIG9mIElPREVGIGRvY3VtZW50
cyBmb3IgZXhjaGFuZ2luZyBvciB0cmFjaW5nIGluZm9ybWF0aW9uIHJlZ2FyZGluZyBpbmNpZGVu
dHMiLiBJdCBtYXkgaGVscCBjbGFyaWZ5IHRoaW5ncyBpZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4g
J2VudmVsb3BlJyB3YXMgdXNlZCBoZXJlLCBzaW5jZSBbdG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQg
UklEIGRvY3VtZW50cyB3aWxsIGFjdHVhbGx5IGVudmVsb3BlIElPREVGIGRvY3VtZW50cy4gSG93
ZXZlciwgYmFzZWQgb24gdGhlIGV4YW1wbGVzIGFuZCBzY2hlbWEsIHRoZSBpbnRlbmRlZCB1c2Fn
ZSBpcyBmb3IgYSBSSUQgZG9jdW1lbnQgdG8gYmUgYSBwZWVyIHRvIElPREVGIGluIHRoZSB0cmFu
c3BvcnQgc2NlbmFyaW9zLCBzbyBubyBlbnZlbG9waW5nIGlzIG9jY3VycmluZy4gV291bGQgc3Vn
Z2VzdCBhIHBocmFzZSBsaWtlICJUaGUgUklEIHNjaGVtYSBkZWZpbmVzIGNvbW11bmljYXRpb24t
c3BlY2lmaWMgbWV0YWRhdGEgdG8gc3VwcG9ydCB0aGUgY29tbXVuaWNhdGlvbiBvZiAuLi4uIg0K
DQo+IFRoYW5rIHlvdSBmb3IgdGhlIGNhdGNoLCBJJ2xsIHVzZSB5b3VyIHJld29yZGluZyBzdWdn
ZXN0aW9uLiAgSSdsbCByZXNwb25kIHRvIHlvdXIgc2Vjb25kIG1lc3NhZ2UgYXMgd2VsbCBvbiB0
aGlzIHRvcGljLCB3aGljaCBwb2ludHMgdG8gYSBwcmV2aW91cyB3b3JraW5nIGdyb3VwIGRlY2lz
aW9uIGluIElOQ0ggKHdpdGggcmVhc29ucykgYW5kIGNoYW5naW5nIGl0IG5vdyBjb3VsZCBjcmVh
dGUgaW5jb21wYXRpYmlsaXR5Lg0KDQpTZWN0aW9uOiBJbnRyb2R1Y3Rpb24sIGZpZnRoIHBhcmFn
cmFwaDoNCg0KSW4gdGhlIHNlY29uZCB0byBsYXN0IHNlbnRlbmNlLCB0aGUgY2l0YXRpb24gW1JG
QzYwNDYtYmlzXSBpcyBkdXBsaWNhdGVkLg0KDQo+IFRoYW5rIHlvdSEgIEkgd2lsbCBmaXggdGhh
dC4NCg0KU2VjdGlvbiAzLjEsIGZpcnN0IHBhcmFncmFwaDoNCg0KSSB0aGluayB0aGVyZSBtYXkg
YmUgYSB0eXBvIGluIHRoZSBzdGFydCBvZiB0aGUgc2VudGVuY2U6ICJSSUQgcHJvdmlkZXMgYSBz
dGFuZGFyZCBwcm90b2NvbCBhbmQgZm9ybWF0IGlzIHJlcXVpcmVkIHRvIGVuc3VyZSIsIHByb2Jh
Ymx5IHNob3VsZCBiZSAiUklEIHByb3ZpZGVzIGEgc3RhbmRhcmQgcHJvdG9jb2wgYW5kIGZvcm1h
dCB0aGF0IGlzIHJlcXVpcmVkIHRvIGVuc3VyZSIuIChhZGRlZCAndGhhdCcpLg0KDQo+IFRoYW5r
IHlvdSwgZ29vZCBjYXRjaCEgIEkgd2lsbCBmaXggdGhpcyBhcyB3ZWxsLg0KDQpTZWN0aW9uIDQs
IGZpcnN0IHBhcmFncmFwaDoNCg0KSW4gdGhlIGZpcnN0IHNlbnRlbmNlLCBpdCBtYXkgYmUgaGVs
cGZ1bCB0byBhZGQgY2xhcmlmaWNhdGlvbiByZWxhdGluZyB0byB0aGUgcGhyYXNlICJSSUQgZXh0
ZW5zaW9uIi4gU3BlY2lmaWNhbGx5LCB0aGUgdGhpbmcgdGhhdCBSSUQgaXMgZXh0ZW5kaW5nLiBJ
ZiB5b3UgbWVhbiB0aGF0IFJJRCBpcyBleHRlbmRpbmcgSU9ERUYsIEkgYW0gbm90IHN1cmUgSSBs
aWtlIHRoZSB0ZXJtICdleHRlbmQnLCBzaW5jZSBSSUQgaXMgcmVhbGx5IGp1c3QgaW1wb3J0aW5n
IHRoZSBJT0RFRiBkYXRhIG1vZGVsIGFuZCB1c2luZyBzb21lIG9mIHRoZSBlbGVtZW50cyB0aGF0
IElPREVGIGRlZmluZXMsIGJ1dCBub3QgZXh0ZW5kaW5nIGFueSBvZiB0aGUgSU9ERUYgdHlwZXMs
IHRodXMgdGhlIHdvcmQgJ2V4dGVuZCcgbWF5IGNvbmZ1c2UgZGV2ZWxvcGVycyB0aGF0IGFyZSBy
ZWFkaW5nIHRoZSBzcGVjLg0KDQo+IEdvb2QgY2F0Y2guICBUaGlzIHdhcyBmcm9tIHRoZSBldm9s
dXRpb24gb2YgUklEIGFuZCBJIGRpZG4ndCBjYXRjaCBpdC4gIEFUIG9uZSBwb2ludCBpbiB0aW1l
IGl0IHdhcyBnb2luZyB0byBiZSBhbiBleHRlbnNpb24sIHRoZW4gZW4gZW52ZWxvcGUsIHRoZW4g
dGhlIGN1cnJlbnQgc29sdXRpb24uICBJIHdpbGwgYWRqdXN0IHRoZSB0ZXh0IHRvIG1ha2UgdGhp
cyBjb25zaXN0ZW50LiAgUklEIGNhbiBiZSBleHRlbmRlZCAocmVhbGx5IGp1c3QgdGhlIGVudW1l
cmF0ZWQgbGlzdHMpLCBidXQgdGhhdCdzIGl0IGFuZCBub3QgdGhlIGludGVudCBvZiB0aGlzIHN0
YXRlbWVudC4NCg0KU2VjdGlvbiA0LCBzZWNvbmQgcGFyYWdyYXBoOg0KDQpSZWxhdGluZyB0byB0
aGUgZmlyc3Qgc2VudGVuY2UsIGp1c3QgcmVwZWF0aW5nIG15IHByZXZpb3VzIGNvbW1lbnQgZnJv
bSB0aGUgaW50cm8gc2VjdGlvbjogIkl0IG1heSBoZWxwIGNsYXJpZnkgdGhpbmdzIGlmIGEgZGlm
ZmVyZW50IHdvcmQgdGhhbiAnZW52ZWxvcGUnIHdhcyB1c2VkIGhlcmUsIHNpbmNlIFt0byBtZV0g
aXQgc3VnZ2VzdHMgdGhhdCBSSUQgZG9jdW1lbnRzIHdpbGwgYWN0dWFsbHkgZW52ZWxvcGUgSU9E
RUYgZG9jdW1lbnRzLiBIb3dldmVyLCBiYXNlZCBvbiB0aGUgZXhhbXBsZXMgYW5kIHNjaGVtYSwg
dGhlIGludGVuZGVkIHVzYWdlIGlzIGZvciBhIFJJRCBkb2N1bWVudCB0byBiZSBhIHBlZXIgdG8g
SU9ERUYgaW4gdGhlIHRyYW5zcG9ydCBzY2VuYXJpb3MsIHNvIG5vIGVudmVsb3BpbmcgaXMgb2Nj
dXJyaW5nLiAiDQoNCj4gSSB3aWxsIGZpeCB0aGlzIGFzIHdlbGwgYW5kIHVzZSBjb25zaXN0ZW50
IGxhbmd1YWdlIHRvIGRlc2NyaWJlIHdoYXQgaXMgYWN0dWFsbHkgaGFwcGVuaW5nLiAgVGhhbmsg
eW91IQ0KDQoNClNlY3Rpb24gNjoNCg0KT25lIG92ZXJhbGwgY29tbWVudCBmb3IgdGhlIGRpYWdy
YW1zIGluIHRoaXMgc2VjdGlvbjogaXQgbWF5IGhlbHAgdG8gaW5jbHVkZSB0aGUgSVAgYWRkcmVz
cyBvZiAidGhpbmdzIiAoZS5nLiwgQXR0YWNrIERlc3QsIFNQLTEsIFNQLTIsIGV0Yy4uKSBpZiBw
b3NzaWJsZSB0byBoZWxwIHJlYWRlcnMgdW5kZXJzdGFuZCB0aGUgZXhhbXBsZSBYTUwsIHNwZWNp
ZmljYWxseSB0aGUgcGxhY2VzIHdoZXJlIElQIGFkZHJlc3NlcyBhcmUgbGlzdGVkLg0KDQpTZWN0
aW9uIDYuMiwgZGlhZ3JhbToNCg0KQSByZXN1bHQgbWVzc2FnZSBpcyBzaG93biBpbiB0aGUgZGlh
Z3JhbSwgYnV0IG5vIHJlc3VsdCB4bWwgaXMgcHJvdmlkZWQgaW4gdGhlIGZvbGxvd2luZyBzdWIt
c2VjdGlvbnMuIEEgUmVxdWVzdEF1dGhvcml6YXRpb24gaXMgbGlzdGVkIGluc3RlYWQuIElmIHRo
ZSBzdWItc2VjdGlvbnMgYXJlIGludGVuZGVkIHRvIGRlc2NyaWJlIHRoZSBkaWFncmFtIHRoaXMg
c2hvdWxkIGJlIGNoYW5nZWQuDQoNCj4gVGhlIFJlc3VsdCBpbiA2LjEuMyBpcyBpbnRlbmRlZCB0
byBjb3ZlciB0aGUgZXhhbXBsZS4gIEknbGwgbWFrZSBhIG5vdGUgb24gdGhhdCBhbmQgc2VlIGlm
IGFueSBkaWZmZXJlbmNlcyBuZWVkIHRvIGJlIG5vdGVkIGFzIHRoZSByZXN1bHRzIG1heSBiZSBk
aWZmZXJlbnQgZnJvbSBkaWZmZXJlbnQgaW52ZXN0aWdhdGlvbnMuICBUaGFua3MhDQoNClNlY3Rp
b24gNi40LjEsIGZpcnN0IHBhcmFncmFwaCwNCg0KVGhpcyBwYXJhZ3JhcGggbGlzdHMgdGhlIGRp
ZmZlcmVudCB0eXBlcyBvZiBmb3JtYXRzIHRoZSBJbmNpZGVudFF1ZXJ5IG1heSBiZSBzZW50IGFz
LCBidXQgZG9lcyBub3Qgc2F5IHdoYXQgdGhlIGV4YW1wbGUgeG1sIGlsbHVzdHJhdGVzIChlLmcu
LCB3aGF0IHR5cGUpLiBTdWdnZXN0IGFkZGluZyBzb21lIHRleHQgdG8gc2Vjb25kIHNlbnRlbmNl
IHNheWluZyB0aGF0IHRoZSB0eXBlIGRlc2NyaWJlZCBpbiB0aGF0IHNlbnRlbmNlIGlzIGlsbHVz
dHJhdGVkIGluIHRoZSBleGFtcGxlIFhNTCAoYXQgbGVhc3QgSSB0aGluayBpdCBpcykuDQoNCj4g
IFRoYW5rIHlvdSwgSSB3aWxsIGFkZCBzb21lIHRleHQgdG8gYXNzaXN0IHJlYWRlcnMgdG8gbGlu
ayB0aGUgYXBwcm9wcmlhdGUgZXhhbXBsZSAmIHRleHQuDQoNClNlY3Rpb24gNywgc2NoZW1hLg0K
DQpGb3IgdGhlIGZpcnN0IGltcG9ydCAodXJuOmlldGY6cGFyYW1zOnhtbDpuczppb2RlZi0xLjAp
LCBndWVzc2luZyB0aGlzIGlzIHN1cHBvc2VkIHRvIHBvaW50IHRvIElPREVGIHNjaGVtYSBhbmQg
bm90IElPREVGLVJJRDrvv71odHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3htbC1yZWdp
c3RyeS9zY2hlbWEvaW9kZWYtMS4wLnhzZC4NCg0KPiBUaGFuayB5b3UsIHlvdSBhcmUgY29ycmVj
dC4gIEkgd2lsbCBtYWtlIHRoZSB1cGRhdGUuDQoNClRoYW5rcywNClBhdWwNCg0KDQoNCg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogbWlsZS1ib3VuY2Vz
QGlldGYub3JnIFttaWxlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBrYXRobGVlbi5t
b3JpYXJ0eUBlbWMuY29tIFtrYXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tXQ0KU2VudDogRnJpZGF5
LCBEZWNlbWJlciAwMiwgMjAxMSAzOjExIFBNDQpUbzogbWlsZUBpZXRmLm9yZw0KU3ViamVjdDog
W21pbGVdIFdHIExhc3QgY2FsbA0KDQpGWUkgLSB0d28gZG9jdW1lbnRzIHdyYXAgdXAgV29ya2lu
ZyBHcm91cCBMYXN0IENhbGwgKFdHTEMpIGF0IGVuZCBvZiBkYXkgb24gTW9uZGF5LiAgUGxlYXNl
IHNoYXJlIHlvdXIgY29tbWVudHMgb24gdGhlIGxpc3Qgb3IgdGhhdCB5b3UgaGF2ZSByZWFkIHRo
ZSBkb2N1bWVudHMgYW5kIGhhdmUgbm8gY29tbWVudHMvaXNzdWVzLg0KDQpUaGFuayB5b3UgYW5k
IGhhdmUgYSBuaWNlIHdlZWtlbmQhDQpLYXRobGVlbg0KDQoNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1pbGUgbWFpbGluZyBsaXN0DQptaWxlQGll
dGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pbGUNCg==

From kathleen.moriarty@emc.com  Mon Dec  5 14:48:11 2011
Return-Path: <kathleen.moriarty@emc.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 6B2541F0C4A for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 14:48:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.773
X-Spam-Level: 
X-Spam-Status: No, score=-5.773 tagged_above=-999 required=5 tests=[AWL=0.226,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbPBcYdATTlc for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 14:48:10 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 345941F0C89 for <mile@ietf.org>; Mon,  5 Dec 2011 14:48:09 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5Mm8VP000908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2011 17:48:08 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 5 Dec 2011 17:47:51 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB5MlnDc018487; Mon, 5 Dec 2011 17:47:49 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Mon, 5 Dec 2011 17:47:49 -0500
From: <kathleen.moriarty@emc.com>
To: <paul.cichonski@nist.gov>, <mile@ietf.org>
Date: Mon, 5 Dec 2011 17:47:48 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiwBlhl60AASTu4oAMYvEEA==
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E8CC9@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com>, <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov> <D7A0423E5E193F40BE6E94126930C49308EEA85C50@MBCLUSTER.xchange.nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C49308EEA85C50@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 22:48:11 -0000

SGkgUGF1bCwNCg0KVGhhbmsgeW91IGFnYWluIGZvciB0aGUgZGV0YWlsZWQgcmV2aWV3IQ0KDQpX
ZSB3ZW50IGJhY2sgYW5kIGZvcnRoIHRvIGNvbWUgdG8gYSB3b3JraW5nIGdyb3VwIGNvbnNlbnN1
cyBpbiBJTkNIIGFzIHRvIGhvdyB0aGlzIHNob3VsZCBiZSBhcHByb2FjaGVkIGFuZCBldmVudHVh
bGx5IHdvdW5kIHVwIHdpdGggdGhlIGN1cnJlbnQgc29sdXRpb24gdXNpbmcgcGVlciBkb2N1bWVu
dHMuICBJdCB3b3VsZCBiZSBlYXN5IHRvIGluY2x1ZGUgYW4gb3B0aW9uYWwgZWxlbWVudCBhcyBz
dWdnZXN0ZWQsIGJ1dCB0aGlzIHdvdWxkIGJyZWFrIGNvbXBhdGliaWxpdHkuICBBcmUgdGhlcmUg
b3BpbmlvbnMgZnJvbSB0aGUgTUlMRSBXRz8NCg0KVGhlIHJlYXNvbnMgZm9yIHRoZSBzZXBhcmF0
ZSBzY2hlbWFzIGxpc3RlZCBhcyBwZWVycyB3YXMgdG8gaGVscCBwcmV2ZW50IHNjaGVtYSB2YWxp
ZGF0aW9uIGlzc3VlcyBhbmQgcmVkdWNlIHBvdGVudGlhbCBwcm9ibGVtcy4gIA0KDQpUaGFuayB5
b3UsDQpLYXRobGVlbiAgKGFzIGRvY3VtZW50IGVkaXRvcikNCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IG1pbGUtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOm1pbGUtYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENpY2hvbnNraSwgUGF1bA0KU2VudDogU3VuZGF5LCBE
ZWNlbWJlciAwNCwgMjAxMSA1OjQ5IFBNDQpUbzogbWlsZUBpZXRmLm9yZw0KU3ViamVjdDogUmU6
IFttaWxlXSBXRyBMYXN0IGNhbGwNCg0KU29ycnkgdG8gZm9sbG93LXVwIG9uIG15IG93biBwb3N0
LCBidXQgSSB3YXMgdGhpbmtpbmcgYSBiaXQgbW9yZSBhYm91dCB0aGUgImVudmVsb3BpbmciIHJl
bGF0aW9uc2hpcCwgYW5kIHdhcyBqdXN0IHdvbmRlcmluZyB3aHkgYSBSSUQgaW5zdGFuY2UgZG9j
dW1lbnQgZG9lcyBub3QgYWN0dWFsbHkgaW5jbHVkZSBhbiBpb2RlZjpJT0RFRi1Eb2N1bWVudCBl
bGVtZW50IGFzIG9uZSBvZiB0aGUgb3B0aW9uYWwgZWxlbWVudHMgb2YgdGhlIHJpZDpSSUQgZWxl
bWVudD8NCg0KW05vdGUgdGhhdCBJIHdhcyBpbmZlcnJpbmcgKHBvc3NpYmx5IGluY29ycmVjdGx5
KSBhIGxvdCBhYm91dCB0aGUgUklEIHVzYWdlIHBhdHRlcm5zIHdoZW4gd3JpdGluZyB0aGUgYmVs
b3cgY29tbWVudHMsIHNvIHBsZWFzZSB0YWtlIHRoZW0gd2l0aCBhIGdyYWluIG9mIHNhbHQuXQ0K
DQpJdCB3b3VsZCBzZWVtIHRoYXQgdGhpcyB0eXBlIG9mIHRydWUgZW52ZWxvcGluZyByZWxhdGlv
bnNoaXAgd291bGQgYmUgYmVuZWZpY2lhbCB0byBSSUQgY29uc3VtZXJzIHNpbmNlIGluIG1vc3Qg
b2YgdGhlIGNhc2VzIChlLmcuLCB0aG9zZSB0aGF0IHJlcXVpcmUgYW4gSU9ERUYgZG9jdW1lbnQg
YWxvbmcgd2l0aCB0aGUgUklEIG1lc3NhZ2UpIGl0IHdpbGwgYmUgbmVjZXNzYXJ5IGZvciB0aGUg
Y29uc3VtZXIgdG8gZGV0ZXJtaW5lIHdoaWNoIElPREVGLURvY3VtZW50IHJlbGF0ZXMgdG8gdGhl
IFJJRCBtZXNzYWdlIHRoYXQgd2FzIHJlY2VpdmVkLiBXaXRob3V0IGFuIGV4cGxpY2l0IHNwZWNp
ZmljYXRpb24gb2YgaG93IHRvIHJlc29sdmUgdGhpcyBjb3JyZWxhdGlvbiB0aGUgY29uc3VtZXIg
aXMgbm90IGd1YXJhbnRlZWQgdG8gcmVzb2x2ZSB0aGUgY29ycmVjdCBJT0RFRi1Eb2N1bWVudC4g
R29pbmcgYSBzdGVwIGZ1cnRoZXIsIGl0IHdvdWxkIGFsc28gYmUgcG9zc2libGUgdG8gaW5jbHVk
ZSBhIGRzaWc6U2lnbmF0dXJlIGVsZW1lbnQgd2l0aGluIHRoZSBSaWQgZWxlbWVudCBzbyB0aGF0
IGFsbCBpbmZvcm1hdGlvbiBpcyBmdWxseSBjb250YWluZWQgd2l0aGluIHRoZSBSSUQgZW52ZWxv
cGUgKHNlZSBzZWN0aW9uIDMuMTAgb2YgdGhlIFNDQVAgMS4yIHNwZWNpZmljYXRpb24gdG8gc2Vl
IGhvdyB0aGlzIGlzIGRvbmUgd2l0aGluIHRoZSBjb250ZXh0IG9mIFNDQVAgMS4yIGRvY3VtZW50
czogaHR0cDovL2NzcmMubmlzdC5nb3YvcHVibGljYXRpb25zL25pc3RwdWJzLzgwMC0xMjYtcmV2
Mi9TUDgwMC0xMjZyMi5wZGYpLiANCg0KQW5vdGhlciB3YXkgdG8gZW5zdXJlIHRoYXQgdGhlIElP
REVGLURvY3VtZW50IGlzIHJlc29sdmVkIGNvcnJlY3RseSBpcyB0byBmb3JtYWxseSBzcGVjaWZ5
IHRoYXQgdGhlIGlvZGVmOkluY2lkZW50SWQgaW4gdGhlIFJJRCBkb2N1bWVudCBwb2ludHMgdG8g
dGhlIGFzc29jaWF0ZWQgaW9kZWY6SW5jaWRlbnRJRCBpbiB0aGUgSU9ERUYgZG9jdW1lbnQuIEkg
dGhpbmsgdGhpcyBsb2dpYyBpcyBpbXBsaWNpdCBpbiB0aGUgY3VycmVudCBkcmFmdCwgYnV0IGl0
IHdvdWxkIGJlIGhlbHBmdWwgdG8gY2FsbCBpdCBvdXQgZm9ybWFsbHkuIEFsc28sIGkgYW0gbm90
IHBvc2l0aXZlIHRoaXMgd2lsbCBhbHdheXMgd29yayBzaW5jZSB0aGUgaW9kZWY6SW5jaWRlbnRJ
ZCBpcyBub3QgYSByZXF1aXJlZCBlbGVtZW50IGluIHRoZSAgUklEUG9saWN5IGVsZW1lbnQuDQoN
ClRvIHByb3ZpZGVkIGEgc29tZXdoYXQgcmVsYXRlZCBleGFtcGxlIGZyb20gdGhlIFNDQVAgc3Bh
Y2UsIHRoZSBTQ0FQIHNwZWNpZmljYXRpb24gc3RhcnRlZCBvdXQgd2l0aCBhbGwgb2YgdGhlIGRp
c3BhcmF0ZSBjb21wb25lbnRzIChlLmcuLCBYQ0NERiwgT1ZBTCwgQ1BFLCBldGPigKYpIGJlaW5n
IGRpc3BhcmF0ZSBYTUwgZG9jdW1lbnRzIGFuZCB0aGUgb25seSBydWxlIHdhcyB0aGF0IHRoZXkg
YWxsIGhhZCB0byBiZSBpbiB0aGUgc2FtZSBaSVAgYnVuZGxlIHRvIGFsbG93IGEgY29uc3VtZXIg
dG8gY29tcGlsZSB0aGUgdGhlIGNyb3NzLWRvY3VtZW50IHJlbGF0aW9uc2hpcHMgaW4gbWVtb3J5
LiBIb3dldmVyLCB0aGUgbGFjayBvZiBmb3JtYWxpemF0aW9uIGNhdXNlZCBwcm9ibGVtcyBmb3Ig
Y29uc3VtZXJzOyB0aGUgbmV3IHN0cmF0ZWd5IChpbiBTQ0FQIDEuMiwgcmVmZXJlbmNlZCBhYm92
ZSkgaXMgdG8gaW5jbHVkZSBhbGwgdGhlIGRpc3BhcmF0ZSBjb21wb25lbnRzIGluIGEgaGlnaGVy
LWxldmVsIGVsZW1lbnQgbmFtZWQgJ2RhdGEtc3RyZWFtJyB0aGF0IHdyYXBzIGV2ZXJ5dGhpbmcg
aW4gb25lIGRvY3VtZW50IHRvIHByb3ZpZGUgbW9yZSBjb250ZXh0IGFuZCBtYWtlIHRoZSBjcm9z
cy1jb21wb25lbnQgcmVsYXRpb25zaGlwcyBtb3JlIGV4cGxpY2l0Lg0KDQpBcyBhIHNpZGUgbm90
ZSwgdGhlIGV4YW1wbGVzIGluIHNlY3Rpb24gNiBvZiB0aGUgUklEIGRyYWZ0IGluY2x1ZGUgeG1s
IGNvbW1lbnRzIChpLmUuLCAiPCEtLSAtLT4iKSBiZXR3ZWVuIHRoZSBpb2RlZi1yaWQ6UklEIGFu
ZCBpb2RlZjpJT0RFRi1Eb2N1bWVudCByb290IGVsZW1lbnRzLCB3aGljaCBsZWFkcyB0aGUgcmVh
ZGVyIHRvIGJlbGlldmUgdGhhdCB0aGVyZSBpcyBzb21lIGhpZ2hlci1sZXZlbCByb290IGVsZW1l
bnQgdGhhdCB3cmFwcyB0aGVzZSBlbGVtZW50cyAoYW5kIHRoZSBYTUwgZHNpZyBFbnZlbG9wZSks
IGJ1dCBJIGFtIGd1ZXNzaW5nIHRoYXQgd2FzIG5vdCBpbnRlbnRpb25hbC4NCg0KVGhpcyBoYXMg
cHJvYmFibHkgYWxsIGJlZW4gZGlzY3Vzc2VkIGluIGRldGFpbCBhdCBzb21lIHBvaW50IGluIFJJ
RCdzIGhpc3Rvcnkgc28gSSBhcG9sb2dpemUgaWYgSSBhbSByZXBlYXRpbmcgb2xkIGlzc3Vlcy4N
Cg0KLVBhdWwNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206
IG1pbGUtYm91bmNlc0BpZXRmLm9yZyBbbWlsZS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYg
T2YgQ2ljaG9uc2tpLCBQYXVsIFtwYXVsLmNpY2hvbnNraUBuaXN0Lmdvdl0NClNlbnQ6IFN1bmRh
eSwgRGVjZW1iZXIgMDQsIDIwMTEgMzozOCBQTQ0KVG86IGthdGhsZWVuLm1vcmlhcnR5QGVtYy5j
b207IG1pbGVAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbbWlsZV0gV0cgTGFzdCBjYWxsDQoNCkhp
IEthdGhsZWVuLA0KDQpJIGp1c3QgaGF2ZSBhIGZldyBtaW5vciBjb21tZW50cyBiZWxvdyByZWxh
dGluZyB0byB0aGUgIlJlYWwtdGltZSBJbnRlci1uZXR3b3JrIERlZmVuc2UgKFJJRCkgZHJhZnQt
bW9yaWFydHktbWlsZS1yZmM2MDQ1LWJpcy0wMi50eHQiIGRvY3VtZW50LiBPdGhlciB0aGFuIHRo
ZXNlIGNvbW1lbnRzLCBib3RoIGRvY3VtZW50cyBsb29rIGdvb2QgdG8gbWUuDQoNClNlY3Rpb246
IEludHJvZHVjdGlvbiwgZmlmdGggcGFyYWdyYXBoOg0KDQpGb3IgdGhlIHNlbnRlbmNlICJUaGUg
UklEIHNjaGVtYSBhY3RzIGFzIGFuIFhNTCBlbnZlbG9wZSB0byBzdXBwb3J0IHRoZSBjb21tdW5p
Y2F0aW9uIG9mIElPREVGIGRvY3VtZW50cyBmb3IgZXhjaGFuZ2luZyBvciB0cmFjaW5nIGluZm9y
bWF0aW9uIHJlZ2FyZGluZyBpbmNpZGVudHMiLiBJdCBtYXkgaGVscCBjbGFyaWZ5IHRoaW5ncyBp
ZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4gJ2VudmVsb3BlJyB3YXMgdXNlZCBoZXJlLCBzaW5jZSBb
dG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQgUklEIGRvY3VtZW50cyB3aWxsIGFjdHVhbGx5IGVudmVs
b3BlIElPREVGIGRvY3VtZW50cy4gSG93ZXZlciwgYmFzZWQgb24gdGhlIGV4YW1wbGVzIGFuZCBz
Y2hlbWEsIHRoZSBpbnRlbmRlZCB1c2FnZSBpcyBmb3IgYSBSSUQgZG9jdW1lbnQgdG8gYmUgYSBw
ZWVyIHRvIElPREVGIGluIHRoZSB0cmFuc3BvcnQgc2NlbmFyaW9zLCBzbyBubyBlbnZlbG9waW5n
IGlzIG9jY3VycmluZy4gV291bGQgc3VnZ2VzdCBhIHBocmFzZSBsaWtlICJUaGUgUklEIHNjaGVt
YSBkZWZpbmVzIGNvbW11bmljYXRpb24tc3BlY2lmaWMgbWV0YWRhdGEgdG8gc3VwcG9ydCB0aGUg
Y29tbXVuaWNhdGlvbiBvZiAuLi4uIg0KDQpTZWN0aW9uOiBJbnRyb2R1Y3Rpb24sIGZpZnRoIHBh
cmFncmFwaDoNCg0KSW4gdGhlIHNlY29uZCB0byBsYXN0IHNlbnRlbmNlLCB0aGUgY2l0YXRpb24g
W1JGQzYwNDYtYmlzXSBpcyBkdXBsaWNhdGVkLg0KDQpTZWN0aW9uIDMuMSwgZmlyc3QgcGFyYWdy
YXBoOg0KDQpJIHRoaW5rIHRoZXJlIG1heSBiZSBhIHR5cG8gaW4gdGhlIHN0YXJ0IG9mIHRoZSBz
ZW50ZW5jZTogIlJJRCBwcm92aWRlcyBhIHN0YW5kYXJkIHByb3RvY29sIGFuZCBmb3JtYXQgaXMg
cmVxdWlyZWQgdG8gZW5zdXJlIiwgcHJvYmFibHkgc2hvdWxkIGJlICJSSUQgcHJvdmlkZXMgYSBz
dGFuZGFyZCBwcm90b2NvbCBhbmQgZm9ybWF0IHRoYXQgaXMgcmVxdWlyZWQgdG8gZW5zdXJlIi4g
KGFkZGVkICd0aGF0JykuDQoNClNlY3Rpb24gNCwgZmlyc3QgcGFyYWdyYXBoOg0KDQpJbiB0aGUg
Zmlyc3Qgc2VudGVuY2UsIGl0IG1heSBiZSBoZWxwZnVsIHRvIGFkZCBjbGFyaWZpY2F0aW9uIHJl
bGF0aW5nIHRvIHRoZSBwaHJhc2UgIlJJRCBleHRlbnNpb24iLiBTcGVjaWZpY2FsbHksIHRoZSB0
aGluZyB0aGF0IFJJRCBpcyBleHRlbmRpbmcuIElmIHlvdSBtZWFuIHRoYXQgUklEIGlzIGV4dGVu
ZGluZyBJT0RFRiwgSSBhbSBub3Qgc3VyZSBJIGxpa2UgdGhlIHRlcm0gJ2V4dGVuZCcsIHNpbmNl
IFJJRCBpcyByZWFsbHkganVzdCBpbXBvcnRpbmcgdGhlIElPREVGIGRhdGEgbW9kZWwgYW5kIHVz
aW5nIHNvbWUgb2YgdGhlIGVsZW1lbnRzIHRoYXQgSU9ERUYgZGVmaW5lcywgYnV0IG5vdCBleHRl
bmRpbmcgYW55IG9mIHRoZSBJT0RFRiB0eXBlcywgdGh1cyB0aGUgd29yZCAnZXh0ZW5kJyBtYXkg
Y29uZnVzZSBkZXZlbG9wZXJzIHRoYXQgYXJlIHJlYWRpbmcgdGhlIHNwZWMuDQoNClNlY3Rpb24g
NCwgc2Vjb25kIHBhcmFncmFwaDoNCg0KUmVsYXRpbmcgdG8gdGhlIGZpcnN0IHNlbnRlbmNlLCBq
dXN0IHJlcGVhdGluZyBteSBwcmV2aW91cyBjb21tZW50IGZyb20gdGhlIGludHJvIHNlY3Rpb246
ICJJdCBtYXkgaGVscCBjbGFyaWZ5IHRoaW5ncyBpZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4gJ2Vu
dmVsb3BlJyB3YXMgdXNlZCBoZXJlLCBzaW5jZSBbdG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQgUklE
IGRvY3VtZW50cyB3aWxsIGFjdHVhbGx5IGVudmVsb3BlIElPREVGIGRvY3VtZW50cy4gSG93ZXZl
ciwgYmFzZWQgb24gdGhlIGV4YW1wbGVzIGFuZCBzY2hlbWEsIHRoZSBpbnRlbmRlZCB1c2FnZSBp
cyBmb3IgYSBSSUQgZG9jdW1lbnQgdG8gYmUgYSBwZWVyIHRvIElPREVGIGluIHRoZSB0cmFuc3Bv
cnQgc2NlbmFyaW9zLCBzbyBubyBlbnZlbG9waW5nIGlzIG9jY3VycmluZy4gIg0KDQpTZWN0aW9u
IDY6DQoNCk9uZSBvdmVyYWxsIGNvbW1lbnQgZm9yIHRoZSBkaWFncmFtcyBpbiB0aGlzIHNlY3Rp
b246IGl0IG1heSBoZWxwIHRvIGluY2x1ZGUgdGhlIElQIGFkZHJlc3Mgb2YgInRoaW5ncyIgKGUu
Zy4sIEF0dGFjayBEZXN0LCBTUC0xLCBTUC0yLCBldGMuLikgaWYgcG9zc2libGUgdG8gaGVscCBy
ZWFkZXJzIHVuZGVyc3RhbmQgdGhlIGV4YW1wbGUgWE1MLCBzcGVjaWZpY2FsbHkgdGhlIHBsYWNl
cyB3aGVyZSBJUCBhZGRyZXNzZXMgYXJlIGxpc3RlZC4NCg0KU2VjdGlvbiA2LjIsIGRpYWdyYW06
DQoNCkEgcmVzdWx0IG1lc3NhZ2UgaXMgc2hvd24gaW4gdGhlIGRpYWdyYW0sIGJ1dCBubyByZXN1
bHQgeG1sIGlzIHByb3ZpZGVkIGluIHRoZSBmb2xsb3dpbmcgc3ViLXNlY3Rpb25zLiBBIFJlcXVl
c3RBdXRob3JpemF0aW9uIGlzIGxpc3RlZCBpbnN0ZWFkLiBJZiB0aGUgc3ViLXNlY3Rpb25zIGFy
ZSBpbnRlbmRlZCB0byBkZXNjcmliZSB0aGUgZGlhZ3JhbSB0aGlzIHNob3VsZCBiZSBjaGFuZ2Vk
Lg0KDQpTZWN0aW9uIDYuNC4xLCBmaXJzdCBwYXJhZ3JhcGgsDQoNClRoaXMgcGFyYWdyYXBoIGxp
c3RzIHRoZSBkaWZmZXJlbnQgdHlwZXMgb2YgZm9ybWF0cyB0aGUgSW5jaWRlbnRRdWVyeSBtYXkg
YmUgc2VudCBhcywgYnV0IGRvZXMgbm90IHNheSB3aGF0IHRoZSBleGFtcGxlIHhtbCBpbGx1c3Ry
YXRlcyAoZS5nLiwgd2hhdCB0eXBlKS4gU3VnZ2VzdCBhZGRpbmcgc29tZSB0ZXh0IHRvIHNlY29u
ZCBzZW50ZW5jZSBzYXlpbmcgdGhhdCB0aGUgdHlwZSBkZXNjcmliZWQgaW4gdGhhdCBzZW50ZW5j
ZSBpcyBpbGx1c3RyYXRlZCBpbiB0aGUgZXhhbXBsZSBYTUwgKGF0IGxlYXN0IEkgdGhpbmsgaXQg
aXMpLg0KDQpTZWN0aW9uIDcsIHNjaGVtYS4NCg0KRm9yIHRoZSBmaXJzdCBpbXBvcnQgKHVybjpp
ZXRmOnBhcmFtczp4bWw6bnM6aW9kZWYtMS4wKSwgZ3Vlc3NpbmcgdGhpcyBpcyBzdXBwb3NlZCB0
byBwb2ludCB0byBJT0RFRiBzY2hlbWEgYW5kIG5vdCBJT0RFRi1SSUQ677+9aHR0cDovL3d3dy5p
YW5hLm9yZy9hc3NpZ25tZW50cy94bWwtcmVnaXN0cnkvc2NoZW1hL2lvZGVmLTEuMC54c2QuDQoN
ClRoYW5rcywNClBhdWwNCg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KRnJvbTogbWlsZS1ib3VuY2VzQGlldGYub3JnIFttaWxlLWJvdW5jZXNAaWV0Zi5v
cmddIE9uIEJlaGFsZiBPZiBrYXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tIFtrYXRobGVlbi5tb3Jp
YXJ0eUBlbWMuY29tXQ0KU2VudDogRnJpZGF5LCBEZWNlbWJlciAwMiwgMjAxMSAzOjExIFBNDQpU
bzogbWlsZUBpZXRmLm9yZw0KU3ViamVjdDogW21pbGVdIFdHIExhc3QgY2FsbA0KDQpGWUkgLSB0
d28gZG9jdW1lbnRzIHdyYXAgdXAgV29ya2luZyBHcm91cCBMYXN0IENhbGwgKFdHTEMpIGF0IGVu
ZCBvZiBkYXkgb24gTW9uZGF5LiAgUGxlYXNlIHNoYXJlIHlvdXIgY29tbWVudHMgb24gdGhlIGxp
c3Qgb3IgdGhhdCB5b3UgaGF2ZSByZWFkIHRoZSBkb2N1bWVudHMgYW5kIGhhdmUgbm8gY29tbWVu
dHMvaXNzdWVzLg0KDQpUaGFuayB5b3UgYW5kIGhhdmUgYSBuaWNlIHdlZWtlbmQhDQpLYXRobGVl
bg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cm1pbGUgbWFpbGluZyBsaXN0DQptaWxlQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21pbGUNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQptaWxlIG1haWxpbmcgbGlzdA0KbWlsZUBpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9taWxlDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KbWlsZSBtYWlsaW5nIGxpc3QNCm1pbGVAaWV0Zi5v
cmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWlsZQ0K

From paul.cichonski@nist.gov  Mon Dec  5 17:22:29 2011
Return-Path: <paul.cichonski@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 078D51F0C67 for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 17:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uYJTzueJC3k0 for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 17:22:28 -0800 (PST)
Received: from wsget1.nist.gov (wsget1.nist.gov [129.6.13.150]) by ietfa.amsl.com (Postfix) with ESMTP id E0C9B1F0C63 for <mile@ietf.org>; Mon,  5 Dec 2011 17:22:27 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.1.339.1; Mon, 5 Dec 2011 20:22:22 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Mon, 5 Dec 2011 20:21:44 -0500
From: "Cichonski, Paul" <paul.cichonski@nist.gov>
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "mile@ietf.org" <mile@ietf.org>
Date: Mon, 5 Dec 2011 20:21:29 -0500
Thread-Topic: WG Last call
Thread-Index: AcyxLoWcYXhwKrPUQSer8cnu2hBoiwBlhl60ADW1HQAABnt5rg==
Message-ID: <D7A0423E5E193F40BE6E94126930C49308EEA85C54@MBCLUSTER.xchange.nist.gov>
References: <AE31510960917D478171C79369B660FA0E1A6E89A1@MX06A.corp.emc.com> <D7A0423E5E193F40BE6E94126930C49308EEA85C4C@MBCLUSTER.xchange.nist.gov>, <AE31510960917D478171C79369B660FA0E1A6E8CBF@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E8CBF@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mile] WG Last call
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 01:22:29 -0000

VGhhbmtzIEthdGhsZWVuLA0KDQpUaGVzZSBjaGFuZ2VzIGFsbCBsb29rIGdvb2QgdG8gbWUuDQoN
Ci1QYXVsDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBr
YXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tIFtrYXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tXQ0KU2Vu
dDogTW9uZGF5LCBEZWNlbWJlciAwNSwgMjAxMSA1OjI3IFBNDQpUbzogQ2ljaG9uc2tpLCBQYXVs
OyBtaWxlQGlldGYub3JnDQpTdWJqZWN0OiBSRTogV0cgTGFzdCBjYWxsDQoNCkhlbGxvIFBhdWws
DQoNClRoYW5rIHlvdSBmb3IgdGFraW5nIHRoZSB0aW1lIHRvIHJldmlldyB0aGUgZG9jdW1lbnQg
aW4gZGV0YWlsLiAgSSdsbCBhbnN3ZXIgeW91ciBxdWVzdGlvbnMgaW4gbGluZSBiZWxvdyBhbmQg
bWFrZSB0aGUgYXBwcm9wcmlhdGUgY2hhbmdlcyBpbiB0aGUgdXBkYXRlZCB2ZXJzaW9uIG9mIHRo
ZSBkb2N1bWVudC4NCg0KQmVzdCByZWdhcmRzLA0KS2F0aGxlZW4gKGFzIGVkaXRvcikNCg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IENpY2hvbnNraSwgUGF1bCBbbWFpbHRvOnBh
dWwuY2ljaG9uc2tpQG5pc3QuZ292XQ0KU2VudDogU3VuZGF5LCBEZWNlbWJlciAwNCwgMjAxMSAz
OjM4IFBNDQpUbzogTW9yaWFydHksIEthdGhsZWVuOyBtaWxlQGlldGYub3JnDQpTdWJqZWN0OiBS
RTogV0cgTGFzdCBjYWxsDQoNCkhpIEthdGhsZWVuLA0KDQpJIGp1c3QgaGF2ZSBhIGZldyBtaW5v
ciBjb21tZW50cyBiZWxvdyByZWxhdGluZyB0byB0aGUgIlJlYWwtdGltZSBJbnRlci1uZXR3b3Jr
IERlZmVuc2UgKFJJRCkgZHJhZnQtbW9yaWFydHktbWlsZS1yZmM2MDQ1LWJpcy0wMi50eHQiIGRv
Y3VtZW50LiBPdGhlciB0aGFuIHRoZXNlIGNvbW1lbnRzLCBib3RoIGRvY3VtZW50cyBsb29rIGdv
b2QgdG8gbWUuDQoNClNlY3Rpb246IEludHJvZHVjdGlvbiwgZmlmdGggcGFyYWdyYXBoOg0KDQpG
b3IgdGhlIHNlbnRlbmNlICJUaGUgUklEIHNjaGVtYSBhY3RzIGFzIGFuIFhNTCBlbnZlbG9wZSB0
byBzdXBwb3J0IHRoZSBjb21tdW5pY2F0aW9uIG9mIElPREVGIGRvY3VtZW50cyBmb3IgZXhjaGFu
Z2luZyBvciB0cmFjaW5nIGluZm9ybWF0aW9uIHJlZ2FyZGluZyBpbmNpZGVudHMiLiBJdCBtYXkg
aGVscCBjbGFyaWZ5IHRoaW5ncyBpZiBhIGRpZmZlcmVudCB3b3JkIHRoYW4gJ2VudmVsb3BlJyB3
YXMgdXNlZCBoZXJlLCBzaW5jZSBbdG8gbWVdIGl0IHN1Z2dlc3RzIHRoYXQgUklEIGRvY3VtZW50
cyB3aWxsIGFjdHVhbGx5IGVudmVsb3BlIElPREVGIGRvY3VtZW50cy4gSG93ZXZlciwgYmFzZWQg
b24gdGhlIGV4YW1wbGVzIGFuZCBzY2hlbWEsIHRoZSBpbnRlbmRlZCB1c2FnZSBpcyBmb3IgYSBS
SUQgZG9jdW1lbnQgdG8gYmUgYSBwZWVyIHRvIElPREVGIGluIHRoZSB0cmFuc3BvcnQgc2NlbmFy
aW9zLCBzbyBubyBlbnZlbG9waW5nIGlzIG9jY3VycmluZy4gV291bGQgc3VnZ2VzdCBhIHBocmFz
ZSBsaWtlICJUaGUgUklEIHNjaGVtYSBkZWZpbmVzIGNvbW11bmljYXRpb24tc3BlY2lmaWMgbWV0
YWRhdGEgdG8gc3VwcG9ydCB0aGUgY29tbXVuaWNhdGlvbiBvZiAuLi4uIg0KDQo+IFRoYW5rIHlv
dSBmb3IgdGhlIGNhdGNoLCBJJ2xsIHVzZSB5b3VyIHJld29yZGluZyBzdWdnZXN0aW9uLiAgSSds
bCByZXNwb25kIHRvIHlvdXIgc2Vjb25kIG1lc3NhZ2UgYXMgd2VsbCBvbiB0aGlzIHRvcGljLCB3
aGljaCBwb2ludHMgdG8gYSBwcmV2aW91cyB3b3JraW5nIGdyb3VwIGRlY2lzaW9uIGluIElOQ0gg
KHdpdGggcmVhc29ucykgYW5kIGNoYW5naW5nIGl0IG5vdyBjb3VsZCBjcmVhdGUgaW5jb21wYXRp
YmlsaXR5Lg0KDQpTZWN0aW9uOiBJbnRyb2R1Y3Rpb24sIGZpZnRoIHBhcmFncmFwaDoNCg0KSW4g
dGhlIHNlY29uZCB0byBsYXN0IHNlbnRlbmNlLCB0aGUgY2l0YXRpb24gW1JGQzYwNDYtYmlzXSBp
cyBkdXBsaWNhdGVkLg0KDQo+IFRoYW5rIHlvdSEgIEkgd2lsbCBmaXggdGhhdC4NCg0KU2VjdGlv
biAzLjEsIGZpcnN0IHBhcmFncmFwaDoNCg0KSSB0aGluayB0aGVyZSBtYXkgYmUgYSB0eXBvIGlu
IHRoZSBzdGFydCBvZiB0aGUgc2VudGVuY2U6ICJSSUQgcHJvdmlkZXMgYSBzdGFuZGFyZCBwcm90
b2NvbCBhbmQgZm9ybWF0IGlzIHJlcXVpcmVkIHRvIGVuc3VyZSIsIHByb2JhYmx5IHNob3VsZCBi
ZSAiUklEIHByb3ZpZGVzIGEgc3RhbmRhcmQgcHJvdG9jb2wgYW5kIGZvcm1hdCB0aGF0IGlzIHJl
cXVpcmVkIHRvIGVuc3VyZSIuIChhZGRlZCAndGhhdCcpLg0KDQo+IFRoYW5rIHlvdSwgZ29vZCBj
YXRjaCEgIEkgd2lsbCBmaXggdGhpcyBhcyB3ZWxsLg0KDQpTZWN0aW9uIDQsIGZpcnN0IHBhcmFn
cmFwaDoNCg0KSW4gdGhlIGZpcnN0IHNlbnRlbmNlLCBpdCBtYXkgYmUgaGVscGZ1bCB0byBhZGQg
Y2xhcmlmaWNhdGlvbiByZWxhdGluZyB0byB0aGUgcGhyYXNlICJSSUQgZXh0ZW5zaW9uIi4gU3Bl
Y2lmaWNhbGx5LCB0aGUgdGhpbmcgdGhhdCBSSUQgaXMgZXh0ZW5kaW5nLiBJZiB5b3UgbWVhbiB0
aGF0IFJJRCBpcyBleHRlbmRpbmcgSU9ERUYsIEkgYW0gbm90IHN1cmUgSSBsaWtlIHRoZSB0ZXJt
ICdleHRlbmQnLCBzaW5jZSBSSUQgaXMgcmVhbGx5IGp1c3QgaW1wb3J0aW5nIHRoZSBJT0RFRiBk
YXRhIG1vZGVsIGFuZCB1c2luZyBzb21lIG9mIHRoZSBlbGVtZW50cyB0aGF0IElPREVGIGRlZmlu
ZXMsIGJ1dCBub3QgZXh0ZW5kaW5nIGFueSBvZiB0aGUgSU9ERUYgdHlwZXMsIHRodXMgdGhlIHdv
cmQgJ2V4dGVuZCcgbWF5IGNvbmZ1c2UgZGV2ZWxvcGVycyB0aGF0IGFyZSByZWFkaW5nIHRoZSBz
cGVjLg0KDQo+IEdvb2QgY2F0Y2guICBUaGlzIHdhcyBmcm9tIHRoZSBldm9sdXRpb24gb2YgUklE
IGFuZCBJIGRpZG4ndCBjYXRjaCBpdC4gIEFUIG9uZSBwb2ludCBpbiB0aW1lIGl0IHdhcyBnb2lu
ZyB0byBiZSBhbiBleHRlbnNpb24sIHRoZW4gZW4gZW52ZWxvcGUsIHRoZW4gdGhlIGN1cnJlbnQg
c29sdXRpb24uICBJIHdpbGwgYWRqdXN0IHRoZSB0ZXh0IHRvIG1ha2UgdGhpcyBjb25zaXN0ZW50
LiAgUklEIGNhbiBiZSBleHRlbmRlZCAocmVhbGx5IGp1c3QgdGhlIGVudW1lcmF0ZWQgbGlzdHMp
LCBidXQgdGhhdCdzIGl0IGFuZCBub3QgdGhlIGludGVudCBvZiB0aGlzIHN0YXRlbWVudC4NCg0K
U2VjdGlvbiA0LCBzZWNvbmQgcGFyYWdyYXBoOg0KDQpSZWxhdGluZyB0byB0aGUgZmlyc3Qgc2Vu
dGVuY2UsIGp1c3QgcmVwZWF0aW5nIG15IHByZXZpb3VzIGNvbW1lbnQgZnJvbSB0aGUgaW50cm8g
c2VjdGlvbjogIkl0IG1heSBoZWxwIGNsYXJpZnkgdGhpbmdzIGlmIGEgZGlmZmVyZW50IHdvcmQg
dGhhbiAnZW52ZWxvcGUnIHdhcyB1c2VkIGhlcmUsIHNpbmNlIFt0byBtZV0gaXQgc3VnZ2VzdHMg
dGhhdCBSSUQgZG9jdW1lbnRzIHdpbGwgYWN0dWFsbHkgZW52ZWxvcGUgSU9ERUYgZG9jdW1lbnRz
LiBIb3dldmVyLCBiYXNlZCBvbiB0aGUgZXhhbXBsZXMgYW5kIHNjaGVtYSwgdGhlIGludGVuZGVk
IHVzYWdlIGlzIGZvciBhIFJJRCBkb2N1bWVudCB0byBiZSBhIHBlZXIgdG8gSU9ERUYgaW4gdGhl
IHRyYW5zcG9ydCBzY2VuYXJpb3MsIHNvIG5vIGVudmVsb3BpbmcgaXMgb2NjdXJyaW5nLiAiDQoN
Cj4gSSB3aWxsIGZpeCB0aGlzIGFzIHdlbGwgYW5kIHVzZSBjb25zaXN0ZW50IGxhbmd1YWdlIHRv
IGRlc2NyaWJlIHdoYXQgaXMgYWN0dWFsbHkgaGFwcGVuaW5nLiAgVGhhbmsgeW91IQ0KDQoNClNl
Y3Rpb24gNjoNCg0KT25lIG92ZXJhbGwgY29tbWVudCBmb3IgdGhlIGRpYWdyYW1zIGluIHRoaXMg
c2VjdGlvbjogaXQgbWF5IGhlbHAgdG8gaW5jbHVkZSB0aGUgSVAgYWRkcmVzcyBvZiAidGhpbmdz
IiAoZS5nLiwgQXR0YWNrIERlc3QsIFNQLTEsIFNQLTIsIGV0Yy4uKSBpZiBwb3NzaWJsZSB0byBo
ZWxwIHJlYWRlcnMgdW5kZXJzdGFuZCB0aGUgZXhhbXBsZSBYTUwsIHNwZWNpZmljYWxseSB0aGUg
cGxhY2VzIHdoZXJlIElQIGFkZHJlc3NlcyBhcmUgbGlzdGVkLg0KDQpTZWN0aW9uIDYuMiwgZGlh
Z3JhbToNCg0KQSByZXN1bHQgbWVzc2FnZSBpcyBzaG93biBpbiB0aGUgZGlhZ3JhbSwgYnV0IG5v
IHJlc3VsdCB4bWwgaXMgcHJvdmlkZWQgaW4gdGhlIGZvbGxvd2luZyBzdWItc2VjdGlvbnMuIEEg
UmVxdWVzdEF1dGhvcml6YXRpb24gaXMgbGlzdGVkIGluc3RlYWQuIElmIHRoZSBzdWItc2VjdGlv
bnMgYXJlIGludGVuZGVkIHRvIGRlc2NyaWJlIHRoZSBkaWFncmFtIHRoaXMgc2hvdWxkIGJlIGNo
YW5nZWQuDQoNCj4gVGhlIFJlc3VsdCBpbiA2LjEuMyBpcyBpbnRlbmRlZCB0byBjb3ZlciB0aGUg
ZXhhbXBsZS4gIEknbGwgbWFrZSBhIG5vdGUgb24gdGhhdCBhbmQgc2VlIGlmIGFueSBkaWZmZXJl
bmNlcyBuZWVkIHRvIGJlIG5vdGVkIGFzIHRoZSByZXN1bHRzIG1heSBiZSBkaWZmZXJlbnQgZnJv
bSBkaWZmZXJlbnQgaW52ZXN0aWdhdGlvbnMuICBUaGFua3MhDQoNClNlY3Rpb24gNi40LjEsIGZp
cnN0IHBhcmFncmFwaCwNCg0KVGhpcyBwYXJhZ3JhcGggbGlzdHMgdGhlIGRpZmZlcmVudCB0eXBl
cyBvZiBmb3JtYXRzIHRoZSBJbmNpZGVudFF1ZXJ5IG1heSBiZSBzZW50IGFzLCBidXQgZG9lcyBu
b3Qgc2F5IHdoYXQgdGhlIGV4YW1wbGUgeG1sIGlsbHVzdHJhdGVzIChlLmcuLCB3aGF0IHR5cGUp
LiBTdWdnZXN0IGFkZGluZyBzb21lIHRleHQgdG8gc2Vjb25kIHNlbnRlbmNlIHNheWluZyB0aGF0
IHRoZSB0eXBlIGRlc2NyaWJlZCBpbiB0aGF0IHNlbnRlbmNlIGlzIGlsbHVzdHJhdGVkIGluIHRo
ZSBleGFtcGxlIFhNTCAoYXQgbGVhc3QgSSB0aGluayBpdCBpcykuDQoNCj4gIFRoYW5rIHlvdSwg
SSB3aWxsIGFkZCBzb21lIHRleHQgdG8gYXNzaXN0IHJlYWRlcnMgdG8gbGluayB0aGUgYXBwcm9w
cmlhdGUgZXhhbXBsZSAmIHRleHQuDQoNClNlY3Rpb24gNywgc2NoZW1hLg0KDQpGb3IgdGhlIGZp
cnN0IGltcG9ydCAodXJuOmlldGY6cGFyYW1zOnhtbDpuczppb2RlZi0xLjApLCBndWVzc2luZyB0
aGlzIGlzIHN1cHBvc2VkIHRvIHBvaW50IHRvIElPREVGIHNjaGVtYSBhbmQgbm90IElPREVGLVJJ
RDrvv71odHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3htbC1yZWdpc3RyeS9zY2hlbWEv
aW9kZWYtMS4wLnhzZC4NCg0KPiBUaGFuayB5b3UsIHlvdSBhcmUgY29ycmVjdC4gIEkgd2lsbCBt
YWtlIHRoZSB1cGRhdGUuDQoNClRoYW5rcywNClBhdWwNCg0KDQoNCg0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogbWlsZS1ib3VuY2VzQGlldGYub3JnIFtt
aWxlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBrYXRobGVlbi5tb3JpYXJ0eUBlbWMu
Y29tIFtrYXRobGVlbi5tb3JpYXJ0eUBlbWMuY29tXQ0KU2VudDogRnJpZGF5LCBEZWNlbWJlciAw
MiwgMjAxMSAzOjExIFBNDQpUbzogbWlsZUBpZXRmLm9yZw0KU3ViamVjdDogW21pbGVdIFdHIExh
c3QgY2FsbA0KDQpGWUkgLSB0d28gZG9jdW1lbnRzIHdyYXAgdXAgV29ya2luZyBHcm91cCBMYXN0
IENhbGwgKFdHTEMpIGF0IGVuZCBvZiBkYXkgb24gTW9uZGF5LiAgUGxlYXNlIHNoYXJlIHlvdXIg
Y29tbWVudHMgb24gdGhlIGxpc3Qgb3IgdGhhdCB5b3UgaGF2ZSByZWFkIHRoZSBkb2N1bWVudHMg
YW5kIGhhdmUgbm8gY29tbWVudHMvaXNzdWVzLg0KDQpUaGFuayB5b3UgYW5kIGhhdmUgYSBuaWNl
IHdlZWtlbmQhDQpLYXRobGVlbg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCm1pbGUgbWFpbGluZyBsaXN0DQptaWxlQGlldGYub3JnDQpodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21pbGUNCg==

From kathleen.moriarty@emc.com  Mon Dec  5 19:29:08 2011
Return-Path: <kathleen.moriarty@emc.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 E64871F0C80 for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 19:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.101
X-Spam-Level: 
X-Spam-Status: No, score=-6.101 tagged_above=-999 required=5 tests=[AWL=0.498,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxN-eBQBO2Wh for <mile@ietfa.amsl.com>; Mon,  5 Dec 2011 19:29:08 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 612B41F0C77 for <mile@ietf.org>; Mon,  5 Dec 2011 19:29:08 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB63T7XA017576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Mon, 5 Dec 2011 22:29:07 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Mon, 5 Dec 2011 22:28:49 -0500
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB63Sm6v027156 for <mile@ietf.org>; Mon, 5 Dec 2011 22:28:48 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Mon, 5 Dec 2011 22:28:48 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Mon, 5 Dec 2011 22:28:46 -0500
Thread-Topic: WGLC concluded on draft-ietf-mile-rfc6046-bis-01
Thread-Index: AcyzxynSbl4IyYHeQe629v1SZz/HNw==
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E8CDF@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] WGLC concluded on draft-ietf-mile-rfc6046-bis-01
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 03:29:09 -0000

Hello,

The Working Group Last Call on draft-ietf-mile-rfc6046-bis-01 has concluded=
.

The comments received require a new revision of the draft before sending it=
 to the IESG. There appears to be consensus and agreement from the editor a=
s to the required changes.

Thank you,

Kathleen (as chair)



From internet-drafts@ietf.org  Tue Dec  6 00:31:34 2011
Return-Path: <internet-drafts@ietf.org>
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 0AF8721F8672; Tue,  6 Dec 2011 00:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSu1b71BQD0c; Tue,  6 Dec 2011 00:31:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7796821F8492; Tue,  6 Dec 2011 00:31:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111206083133.24085.1382.idtracker@ietfa.amsl.com>
Date: Tue, 06 Dec 2011 00:31:33 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 08:31:34 -0000

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

	Title           : Transport of Real-time Inter-network Defense (RID) Messa=
ges
	Author(s)       : Brian Trammell
	Filename        : draft-ietf-mile-rfc6046-bis-02.txt
	Pages           : 7
	Date            : 2011-12-06

   The Incident Object Description Exchange Format (IODEF) defines a
   common XML format for document exchange, and Realtime Internetwork
   Defense (RID) defines extensions to IODEF intended for the
   cooperative handling of security incidents within consortia of
   network operators and enterprises.  This document specifies a
   transport protocol for RID based upon the passing of RID messages
   over HTTP/TLS.  This document updates the previous [RFC6046] to
   change the intended status to Proposed Standard, and to reference the
   updated RID specification.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt


From trammell@tik.ee.ethz.ch  Tue Dec  6 00:41:29 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 57AF321F8B4D for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 00:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0JiwRGmlIB+r for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 00:41:28 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id AC65721F8B49 for <mile@ietf.org>; Tue,  6 Dec 2011 00:41:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 3E232D9307 for <mile@ietf.org>; Tue,  6 Dec 2011 09:41:27 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Y5xA4VyNtZH6 for <mile@ietf.org>; Tue,  6 Dec 2011 09:41:27 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id F4217D9304 for <mile@ietf.org>; Tue,  6 Dec 2011 09:41:26 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Dec 2011 09:41:26 +0100
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com>
To: mile@ietf.org
Message-Id: <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 08:41:29 -0000

Greetings, all,

I have submitted rfc6046-bis-02 following WGLC; this revision addresses =
all WGLC comments, and the present draft is in my opinion ready for =
submission to the IESG for publication.

Best regards,

Brian (as author)

Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: December 6, 2011 9:31:33 AM GMT+01:00
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>=20
>=20
> 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 Working Group of the IETF.
>=20
> 	Title           : Transport of Real-time Inter-network Defense =
(RID) Messages
> 	Author(s)       : Brian Trammell
> 	Filename        : draft-ietf-mile-rfc6046-bis-02.txt
> 	Pages           : 7
> 	Date            : 2011-12-06
>=20
>   The Incident Object Description Exchange Format (IODEF) defines a
>   common XML format for document exchange, and Realtime Internetwork
>   Defense (RID) defines extensions to IODEF intended for the
>   cooperative handling of security incidents within consortia of
>   network operators and enterprises.  This document specifies a
>   transport protocol for RID based upon the passing of RID messages
>   over HTTP/TLS.  This document updates the previous [RFC6046] to
>   change the intended status to Proposed Standard, and to reference =
the
>   updated RID specification.
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From ramartin@mitre.org  Tue Dec  6 05:36:34 2011
Return-Path: <ramartin@mitre.org>
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 2E61321F8B22 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 05:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXrl9PXfpvsr for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 05:36:33 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 89C2A21F8B21 for <mile@ietf.org>; Tue,  6 Dec 2011 05:36:33 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id E983721B0C37; Tue,  6 Dec 2011 08:36:32 -0500 (EST)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpksrv1.mitre.org (Postfix) with ESMTP id D759521B0C34; Tue,  6 Dec 2011 08:36:32 -0500 (EST)
Received: from mm169528-pc.mitre.org (129.83.31.51) by IMCCAS04.MITRE.ORG (129.83.29.81) with Microsoft SMTP Server id 14.1.339.1; Tue, 6 Dec 2011 08:36:32 -0500
Message-ID: <4EDE1A60.9060509@mitre.org>
Date: Tue, 6 Dec 2011 08:36:32 -0500
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch>
In-Reply-To: <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 13:36:34 -0000

Hello Brian,

I concur with your opinion.  This is ready for submission.

Bob

On 12/6/11 3:41 AM, Brian Trammell wrote:
> Greetings, all,
>
> I have submitted rfc6046-bis-02 following WGLC; this revision addresses all WGLC comments, and the present draft is in my opinion ready for submission to the IESG for publication.
>
> Best regards,
>
> Brian (as author)
>
> Begin forwarded message:
>
>> From: internet-drafts@ietf.org
>> Date: December 6, 2011 9:31:33 AM GMT+01:00
>> To: i-d-announce@ietf.org
>> Cc: mile@ietf.org
>> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>>
>>
>> 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 Working Group of the IETF.
>>
>> 	Title           : Transport of Real-time Inter-network Defense (RID) Messages
>> 	Author(s)       : Brian Trammell
>> 	Filename        : draft-ietf-mile-rfc6046-bis-02.txt
>> 	Pages           : 7
>> 	Date            : 2011-12-06
>>
>>    The Incident Object Description Exchange Format (IODEF) defines a
>>    common XML format for document exchange, and Realtime Internetwork
>>    Defense (RID) defines extensions to IODEF intended for the
>>    cooperative handling of security incidents within consortia of
>>    network operators and enterprises.  This document specifies a
>>    transport protocol for RID based upon the passing of RID messages
>>    over HTTP/TLS.  This document updates the previous [RFC6046] to
>>    change the intended status to Proposed Standard, and to reference the
>>    updated RID specification.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>

From david.black@emc.com  Tue Dec  6 06:28:23 2011
Return-Path: <david.black@emc.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 3734721F8560 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 06:28:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.357
X-Spam-Level: 
X-Spam-Status: No, score=-106.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAR5xLJWYKeU for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 06:28:19 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id EE79721F8481 for <mile@ietf.org>; Tue,  6 Dec 2011 06:28:18 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB6ESAFL028311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Dec 2011 09:28:16 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Tue, 6 Dec 2011 09:27:59 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB6ERvrB026815; Tue, 6 Dec 2011 09:27:57 -0500
Received: from mx14a.corp.emc.com ([169.254.1.79]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Tue, 6 Dec 2011 09:27:57 -0500
From: <david.black@emc.com>
To: <trammell@tik.ee.ethz.ch>
Date: Tue, 6 Dec 2011 09:27:55 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
Thread-Index: Acy0HCbLHhAL39DERt+gloIGUl1rVAABkPyQ
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E059FEA61A7@MX14A.corp.emc.com>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <4EDE1A60.9060509@mitre.org>
In-Reply-To: <4EDE1A60.9060509@mitre.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 14:28:23 -0000

Brian

I agree, the changes in the -02 version look good to me - thank you for mak=
ing them.

Thanks,
--David

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of M=
artin, Robert A.
> Sent: Tuesday, December 06, 2011 8:37 AM
> To: Brian Trammell
> Cc: mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>=20
> Hello Brian,
>=20
> I concur with your opinion.  This is ready for submission.
>=20
> Bob
>=20
> On 12/6/11 3:41 AM, Brian Trammell wrote:
> > Greetings, all,
> >
> > I have submitted rfc6046-bis-02 following WGLC; this revision addresses=
 all WGLC comments, and the
> present draft is in my opinion ready for submission to the IESG for publi=
cation.
> >
> > Best regards,
> >
> > Brian (as author)
> >
> > Begin forwarded message:
> >
> >> From: internet-drafts@ietf.org
> >> Date: December 6, 2011 9:31:33 AM GMT+01:00
> >> To: i-d-announce@ietf.org
> >> Cc: mile@ietf.org
> >> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
> >>
> >>
> >> A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories. This draft is a
> work item of the Managed Incident Lightweight Exchange Working Group of t=
he IETF.
> >>
> >> 	Title           : Transport of Real-time Inter-network Defense (RID) =
Messages
> >> 	Author(s)       : Brian Trammell
> >> 	Filename        : draft-ietf-mile-rfc6046-bis-02.txt
> >> 	Pages           : 7
> >> 	Date            : 2011-12-06
> >>
> >>    The Incident Object Description Exchange Format (IODEF) defines a
> >>    common XML format for document exchange, and Realtime Internetwork
> >>    Defense (RID) defines extensions to IODEF intended for the
> >>    cooperative handling of security incidents within consortia of
> >>    network operators and enterprises.  This document specifies a
> >>    transport protocol for RID based upon the passing of RID messages
> >>    over HTTP/TLS.  This document updates the previous [RFC6046] to
> >>    change the intended status to Proposed Standard, and to reference t=
he
> >>    updated RID specification.
> >>
> >>
> >> A URL for this Internet-Draft is:
> >> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> This Internet-Draft can be retrieved at:
> >> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt
> >>
> >> _______________________________________________
> >> mile mailing list
> >> mile@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
> > .
> >
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From Kent_Landfield@mcafee.com  Tue Dec  6 07:09:33 2011
Return-Path: <Kent_Landfield@mcafee.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 7073921F8B80 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 07:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2UFILjexCCH5 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 07:09:32 -0800 (PST)
Received: from dalsmrelay2.nai.com (dalsmrelay2.nai.com [205.227.136.216]) by ietfa.amsl.com (Postfix) with ESMTP id CE4DC21F8B71 for <mile@ietf.org>; Tue,  6 Dec 2011 07:09:24 -0800 (PST)
Received: from (unknown [10.64.5.51]) by dalsmrelay2.nai.com with smtp id 0a78_2adf_411536ae_201c_11e1_a6c6_00219b929abd; Tue, 06 Dec 2011 09:09:11 -0600
Received: from AMERDALEXMB1.corp.nai.org ([fe80::387d:3d79:ad3b:b517]) by DALEXHT1.corp.nai.org ([::1]) with mapi; Tue, 6 Dec 2011 09:07:11 -0600
From: <Kent_Landfield@McAfee.com>
To: <ramartin@mitre.org>, <trammell@tik.ee.ethz.ch>
Date: Tue, 6 Dec 2011 09:07:10 -0600
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
Thread-Index: Acy0KLook9e1s2zJRU2ETtAPFipKVw==
Message-ID: <CB0399CE.26284%kent_landfield@mcafee.com>
In-Reply-To: <4EDE1A60.9060509@mitre.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 15:09:33 -0000

I too agree this is ready.

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee, Inc.
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

From: Bob Martin <ramartin@mitre.org<mailto:ramartin@mitre.org>>
Date: Tue, 6 Dec 2011 07:36:32 -0600
To: Brian Trammell <trammell@tik.ee.ethz.ch<mailto:trammell@tik.ee.ethz.ch>=
>
Cc: "mile@ietf.org<mailto:mile@ietf.org>" <mile@ietf.org<mailto:mile@ietf.o=
rg>>
Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt

Hello Brian,

I concur with your opinion.  This is ready for submission.

Bob

On 12/6/11 3:41 AM, Brian Trammell wrote:
Greetings, all,

I have submitted rfc6046-bis-02 following WGLC; this revision addresses all=
 WGLC comments, and the present draft is in my opinion ready for submission=
 to the IESG for publication.

Best regards,

Brian (as author)

Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Date: December 6, 2011 9:31:33 AM GMT+01:00
To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
Cc: mile@ietf.org<mailto:mile@ietf.org>
Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-02.txt


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

Title           : Transport of Real-time Inter-network Defense (RID) Messag=
es
Author(s)       : Brian Trammell
Filename        : draft-ietf-mile-rfc6046-bis-02.txt
Pages           : 7
Date            : 2011-12-06

    The Incident Object Description Exchange Format (IODEF) defines a
    common XML format for document exchange, and Realtime Internetwork
    Defense (RID) defines extensions to IODEF intended for the
    cooperative handling of security incidents within consortia of
    network operators and enterprises.  This document specifies a
    transport protocol for RID based upon the passing of RID messages
    over HTTP/TLS.  This document updates the previous [RFC6046] to
    change the intended status to Proposed Standard, and to reference the
    updated RID specification.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-02.txt

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

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

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


From sm@resistor.net  Tue Dec  6 07:32:15 2011
Return-Path: <sm@resistor.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 F376021F8BDE for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 07:32:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQo7HZatS7pN for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 07:32:09 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DE621F8BB5 for <mile@ietf.org>; Tue,  6 Dec 2011 07:32:09 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id pB6FW3tl010810 for <mile@ietf.org>; Tue, 6 Dec 2011 07:32:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1323185527; bh=zGUzQ8iBM/zBIfAyWD1qyO5KNn+lxVGH+1t2TYjemYE=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=K2PmifAPFFhyGjrww01jlqDqKzHv4i/fVHA3Kb0ZyXYAkURNKix8YG/leOeLila7J KiOniYMW4Y9DZU+IlI3tz/GbpAy4xRSwmZ/Nz1/OGzI3FIB535/7ntaWOKR3ekluy1 2iL93zPpykc435E8AkMUzcQ/OLrXoir047xChkss=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1323185527; bh=zGUzQ8iBM/zBIfAyWD1qyO5KNn+lxVGH+1t2TYjemYE=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=x5O82Z9ZCQnxlEiyau9KAgq4X/FOQ0GpgEdRiRjqeF9gDlkfhEeGN3S64/bAuuCTd n78Ff8HmptuD+gp5B1y5kLLt6EGI80KCn/Msiv1CwIWsqAPAYUaZipXw6EKwfN/ZvJ QFdDNRoZzs5qxkae9QHnM422Hrkkrn2RAuxOY7xk=
Message-Id: <6.2.5.6.2.20111206064135.09599cf0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 06 Dec 2011 07:14:41 -0800
To: mile@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 15:32:15 -0000

At 00:41 06-12-2011, Brian Trammell wrote:
>I have submitted rfc6046-bis-02 following WGLC; this revision 
>addresses all WGLC comments, and the present draft is in my opinion 
>ready for submission to the IESG for publication.

Here are a few nits.

In Section 1.1:

   "This document updates [RFC6046] in the following ways:"

That could be described as changes from RFC 6046 or an update of 
instead of "updates" as the document moves RFC 6046 to 
Historic.  Will Section 1.1 be included in the RFC?

The reference to RFC 2119 should be normative.

The reference to RFC 3492 is not needed as it is not referenced from the text.

Regards,
-sm 


From internet-drafts@ietf.org  Tue Dec  6 10:26:51 2011
Return-Path: <internet-drafts@ietf.org>
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 083AA21F8C18; Tue,  6 Dec 2011 10:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVx+9eYSbvZ3; Tue,  6 Dec 2011 10:26:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E36B21F8C13; Tue,  6 Dec 2011 10:26:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111206182650.4275.26677.idtracker@ietfa.amsl.com>
Date: Tue, 06 Dec 2011 10:26:50 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 18:26:51 -0000

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

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-02.txt
	Pages           : 73
	Date            : 2011-12-06

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-02.txt


From kathleen.moriarty@emc.com  Tue Dec  6 10:38:28 2011
Return-Path: <kathleen.moriarty@emc.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 D517D21F84BB for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 10:38:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.157
X-Spam-Level: 
X-Spam-Status: No, score=-6.157 tagged_above=-999 required=5 tests=[AWL=0.442,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoWiMxSs7Rog for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 10:38:28 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id D7C9721F84D2 for <mile@ietf.org>; Tue,  6 Dec 2011 10:38:27 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB6IcKJK015040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Tue, 6 Dec 2011 13:38:24 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Tue, 6 Dec 2011 13:38:09 -0500
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB6Ic88a010585 for <mile@ietf.org>; Tue, 6 Dec 2011 13:38:08 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub36.corp.emc.com ([::1]) with mapi; Tue, 6 Dec 2011 13:38:07 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Tue, 6 Dec 2011 13:38:07 -0500
Thread-Topic: New Version Notification for draft-ietf-mile-rfc6045-bis-02.txt
Thread-Index: Acy0RLn6ftLuU5IeSdCl2NWdy9nFxQAABB/A
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E8E32@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] FW: New Version Notification for draft-ietf-mile-rfc6045-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 18:38:29 -0000

SGVsbG8sDQoNCkkgaGF2ZSBzdWJtaXR0ZWQgZHJhZnQtaWV0Zi1taWxlLXJmYzYwNDUtYmlzLTAy
LnR4dCBpbiByZXNwb25zZSB0byBhbGwgY29tbWVudHMgcmVjZWl2ZWQgZHVyaW5nIFdHTEMuICBU
aGFuayB5b3UgZm9yIHRha2luZyB0aGUgdGltZSB0byByZXZpZXcgdGhlIGRvY3VtZW50LiAgSSBi
ZWxpZXZlIGFsbCBXR0xDIGNvbW1lbnRzIGhhdmUgYmVlbiBhZGRyZXNzZWQgYXMgcHJvcG9zZWQg
YW5kIGFncmVlZCB1cG9uIG9uIHRoZSBNSUxFIG1haWxpbmcgbGlzdC4gIFNvbWUgYWRkaXRpb25h
bCB0ZXh0IHdhcyBhZGRlZCB0byBiZXR0ZXIgZXhwbGFpbiB0aGUgZXhhbXBsZXMgYW5kIHNvbWUg
bWlub3Igbml0cyB3ZXJlIGNvcnJlY3RlZCBpbiB0aGlzIHByb2Nlc3MuICBObyB0ZWNobmljYWwg
Y2hhbmdlcyBoYXZlIGJlZW4gbWFkZSB0byB0aGUgZHJhZnQuICBJIGJlbGlldmUgdGhlIGRvY3Vt
ZW50IGlzIHJlYWR5IGZvciBJRVNHIGxhc3QgY2FsbC4NCg0KVGhlIHN1Ym1pdHRlZCB2ZXJzaW9u
IGFsc28gYWRkcmVzc2VzIHRoZSAnZGlzY3VzcycgY29tbWVudHMgZnJvbSB0aGUgYXBwLWFyZWEs
IGFsc28gcG9zdGVkIHRvIE1JTEUgeWVzdGVyZGF5LiAgVGhlc2UgY29tbWVudHMgd2lsbCByZXF1
aXJlIGFncmVlbWVudCBkdXJpbmcgdGhlIElFU0cgbGFzdCBjYWxsIHByb2Nlc3MgdG8gbWFrZSBz
dXJlIHRoZXkgbWVldCB0aGUgYXBwcy1hcmVhIGNvbmNlcm5zLg0KDQpUaGFuayB5b3UsDQpLYXRo
bGVlbiAoYXMgZWRpdG9yKQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50
ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSAN
ClNlbnQ6IFR1ZXNkYXksIERlY2VtYmVyIDA2LCAyMDExIDE6MjcgUE0NClRvOiBNb3JpYXJ0eSwg
S2F0aGxlZW4NCkNjOiBNb3JpYXJ0eSwgS2F0aGxlZW4NClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5v
dGlmaWNhdGlvbiBmb3IgZHJhZnQtaWV0Zi1taWxlLXJmYzYwNDUtYmlzLTAyLnR4dA0KDQpBIG5l
dyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtaWV0Zi1taWxlLXJmYzYwNDUtYmlzLTAyLnR4dCBoYXMg
YmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEthdGhsZWVuIE1vcmlhcnR5IGFuZCBwb3N0
ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1pZXRmLW1pbGUt
cmZjNjA0NS1iaXMNClJldmlzaW9uOgkgMDINClRpdGxlOgkJIFJlYWwtdGltZSBJbnRlci1uZXR3
b3JrIERlZmVuc2UgKFJJRCkNCkNyZWF0aW9uIGRhdGU6CSAyMDExLTEyLTA2DQpXRyBJRDoJCSBt
aWxlDQpOdW1iZXIgb2YgcGFnZXM6IDczDQoNCkFic3RyYWN0Og0KICAgU2VjdXJpdHkgaW5jaWRl
bnRzLCBzdWNoIGFzIHN5c3RlbSBjb21wcm9taXNlcywgd29ybXMsIHZpcnVzZXMsDQogICBwaGlz
aGluZyBpbmNpZGVudHMsIGFuZCBkZW5pYWwgb2Ygc2VydmljZSwgdHlwaWNhbGx5IHJlc3VsdCBp
biB0aGUNCiAgIGxvc3Mgb2Ygc2VydmljZSwgZGF0YSwgYW5kIHJlc291cmNlcyBib3RoIGh1bWFu
IGFuZCBzeXN0ZW0uICBTZXJ2aWNlDQogICBwcm92aWRlcnMgYW5kIENvbXB1dGVyIFNlY3VyaXR5
IEluY2lkZW50IFJlc3BvbnNlIFRlYW1zIG5lZWQgdG8gYmUNCiAgIGVxdWlwcGVkIGFuZCByZWFk
eSB0byBhc3Npc3QgaW4gY29tbXVuaWNhdGluZyBhbmQgdHJhY2luZyBzZWN1cml0eQ0KICAgaW5j
aWRlbnRzIHdpdGggdG9vbHMgYW5kIHByb2NlZHVyZXMgaW4gcGxhY2UgYmVmb3JlIHRoZSBvY2N1
cnJlbmNlIG9mDQogICBhbiBhdHRhY2suICBSZWFsLXRpbWUgSW50ZXItbmV0d29yayBEZWZlbnNl
IChSSUQpIG91dGxpbmVzIGENCiAgIHByb2FjdGl2ZSBpbnRlci1uZXR3b3JrIGNvbW11bmljYXRp
b24gbWV0aG9kIHRvIGZhY2lsaXRhdGUgc2hhcmluZw0KICAgaW5jaWRlbnQgaGFuZGxpbmcgZGF0
YSB3aGlsZSBpbnRlZ3JhdGluZyBleGlzdGluZyBkZXRlY3Rpb24sIHRyYWNpbmcsDQogICBzb3Vy
Y2UgaWRlbnRpZmljYXRpb24sIGFuZCBtaXRpZ2F0aW9uIG1lY2hhbmlzbXMgZm9yIGEgY29tcGxl
dGUNCiAgIGluY2lkZW50IGhhbmRsaW5nIHNvbHV0aW9uLiAgQ29tYmluaW5nIHRoZXNlIGNhcGFi
aWxpdGllcyBpbiBhDQogICBjb21tdW5pY2F0aW9uIHN5c3RlbSBwcm92aWRlcyBhIHdheSB0byBh
Y2hpZXZlIGhpZ2hlciBzZWN1cml0eSBsZXZlbHMNCiAgIG9uIG5ldHdvcmtzLiAgUG9saWN5IGd1
aWRlbGluZXMgZm9yIGhhbmRsaW5nIGluY2lkZW50cyBhcmUNCiAgIHJlY29tbWVuZGVkIGFuZCBj
YW4gYmUgYWdyZWVkIHVwb24gYnkgYSBjb25zb3J0aXVtIHVzaW5nIHRoZSBzZWN1cml0eQ0KICAg
cmVjb21tZW5kYXRpb25zIGFuZCBjb25zaWRlcmF0aW9ucy4NCg0KICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==

From paul.cichonski@nist.gov  Tue Dec  6 11:14:27 2011
Return-Path: <paul.cichonski@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 7C23F21F8B83 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 11:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IfufGafNlXT for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 11:14:26 -0800 (PST)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 9043B21F8880 for <mile@ietf.org>; Tue,  6 Dec 2011 11:14:26 -0800 (PST)
Received: from WSXGHUB1.xchange.nist.gov (129.6.18.96) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Dec 2011 14:14:20 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB1.xchange.nist.gov ([129.6.18.96]) with mapi; Tue, 6 Dec 2011 14:14:24 -0500
From: "Cichonski, Paul" <paul.cichonski@nist.gov>
To: "mile@ietf.org" <mile@ietf.org>
Date: Tue, 6 Dec 2011 14:14:23 -0500
Thread-Topic: [mile] FW: New Version Notification for draft-ietf-mile-rfc6045-bis-02.txt
Thread-Index: Acy0RLn6ftLuU5IeSdCl2NWdy9nFxQAABB/AAAGSjsA=
Message-ID: <D7A0423E5E193F40BE6E94126930C49308EEE3B183@MBCLUSTER.xchange.nist.gov>
References: <AE31510960917D478171C79369B660FA0E1A6E8E32@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E8E32@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Subject: Re: [mile] FW: New Version Notification for	draft-ietf-mile-rfc6045-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2011 19:14:27 -0000

Kathleen,

This addresses all of my comments and I agree that it is ready for the next steps in the process.

Thanks,
Paul

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> kathleen.moriarty@emc.com
> Sent: Tuesday, December 06, 2011 1:38 PM
> To: mile@ietf.org
> Subject: [mile] FW: New Version Notification for draft-ietf-mile-
> rfc6045-bis-02.txt
> 
> Hello,
> 
> I have submitted draft-ietf-mile-rfc6045-bis-02.txt in response to all
> comments received during WGLC.  Thank you for taking the time to review
> the document.  I believe all WGLC comments have been addressed as
> proposed and agreed upon on the MILE mailing list.  Some additional
> text was added to better explain the examples and some minor nits were
> corrected in this process.  No technical changes have been made to the
> draft.  I believe the document is ready for IESG last call.
> 
> The submitted version also addresses the 'discuss' comments from the
> app-area, also posted to MILE yesterday.  These comments will require
> agreement during the IESG last call process to make sure they meet the
> apps-area concerns.
> 
> Thank you,
> Kathleen (as editor)
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Tuesday, December 06, 2011 1:27 PM
> To: Moriarty, Kathleen
> Cc: Moriarty, Kathleen
> Subject: New Version Notification for draft-ietf-mile-rfc6045-bis-
> 02.txt
> 
> A new version of I-D, draft-ietf-mile-rfc6045-bis-02.txt has been
> successfully submitted by Kathleen Moriarty and posted to the IETF
> repository.
> 
> Filename:	 draft-ietf-mile-rfc6045-bis
> Revision:	 02
> Title:		 Real-time Inter-network Defense (RID)
> Creation date:	 2011-12-06
> WG ID:		 mile
> Number of pages: 73
> 
> Abstract:
>    Security incidents, such as system compromises, worms, viruses,
>    phishing incidents, and denial of service, typically result in the
>    loss of service, data, and resources both human and system.  Service
>    providers and Computer Security Incident Response Teams need to be
>    equipped and ready to assist in communicating and tracing security
>    incidents with tools and procedures in place before the occurrence
> of
>    an attack.  Real-time Inter-network Defense (RID) outlines a
>    proactive inter-network communication method to facilitate sharing
>    incident handling data while integrating existing detection,
> tracing,
>    source identification, and mitigation mechanisms for a complete
>    incident handling solution.  Combining these capabilities in a
>    communication system provides a way to achieve higher security
> levels
>    on networks.  Policy guidelines for handling incidents are
>    recommended and can be agreed upon by a consortium using the
> security
>    recommendations and considerations.
> 
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

From tony@yaanatech.com  Tue Dec  6 16:07:22 2011
Return-Path: <tony@yaanatech.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 ABC6F1F0C79 for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 16:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCOVx3Teqr8w for <mile@ietfa.amsl.com>; Tue,  6 Dec 2011 16:07:22 -0800 (PST)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1321F0C78 for <mile@ietf.org>; Tue,  6 Dec 2011 16:07:22 -0800 (PST)
Received: from [10.184.75.75] (unknown [203.121.55.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id F223B58070; Wed,  7 Dec 2011 00:07:17 +0000 (UTC)
Message-ID: <4EDEAE30.2090603@yaanatech.com>
Date: Wed, 07 Dec 2011 08:07:12 +0800
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111130 Thunderbird/9.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <AE31510960917D478171C79369B660FA0E1A6E8E32@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E8E32@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] FW: New Version Notification for draft-ietf-mile-rfc6045-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 00:07:22 -0000

Hi Kathleen,

This is a welcome mature document that will
have a broad array of applications across the
security and infrastructure protection horizon.

--tony

From internet-drafts@ietf.org  Wed Dec  7 05:54:20 2011
Return-Path: <internet-drafts@ietf.org>
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 6463421F8B9C; Wed,  7 Dec 2011 05:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PB4Z2LA+Rszv; Wed,  7 Dec 2011 05:54:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04DD621F8510; Wed,  7 Dec 2011 05:54:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111207135420.1796.43829.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2011 05:54:20 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-sci-00.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 13:54:20 -0000

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

	Title           : IODEF-extension to support structured cybersecurity info=
rmation
	Author(s)       : Takeshi Takahashi
                          Kent Landfield
                          Thomas Millar
                          Youki Kadobayashi
	Filename        : draft-ietf-mile-sci-00.txt
	Pages           : 27
	Date            : 2011-12-07

   This document extends the Incident Object Description Exchange Format
   (IODEF) defined in RFC 5070 [RFC5070] to facilitate enriched
   cybersecurity information exchange among cybersecurity entities by
   embedding structured information formatted by specifications,
   including CAPEC[TM] [CAPEC], CEE[TM] [CEE], CPE[TM] [CPE], CVE(R)
   [CVE], CVRF [CVRF], CVSS [CVSS], CWE[TM] [CWE], CWSS[TM] [CWSS], ISO/
   IEC 19770-2 [ISOIEC19770-2], OCIL [OCIL], OVAL(R) [OVAL], XCCDF
   [XCCDF], and XDAS [XDAS].


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-sci-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-sci-00.txt


From trammell@tik.ee.ethz.ch  Wed Dec  7 07:28:31 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 6DEAC21F8569 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 07:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VKLKVMPShRP for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 07:28:31 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id D56C921F84F8 for <mile@ietf.org>; Wed,  7 Dec 2011 07:28:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 778ADD930E; Wed,  7 Dec 2011 16:28:29 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0vSeMiTnWkOK; Wed,  7 Dec 2011 16:28:29 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 06608D9304; Wed,  7 Dec 2011 16:28:29 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <6.2.5.6.2.20111206064135.09599cf0@resistor.net>
Date: Wed, 7 Dec 2011 16:28:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B3220E2-7A45-47EC-8711-B0C94ECF9D08@tik.ee.ethz.ch>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 15:28:31 -0000

Hi sm,

The intention was to keep Section 1.1 in the RFC (it's the only part of =
the document that notes the move of 6046 to Historic; this doesn't fit =
anywhere else. It's also useful to have an at-a-glance set of changes =
for existing implementors.)

Thanks for the comments, I'll address these in a new revision before =
IESG submission.

Best regards,

Brian

On Dec 6, 2011, at 4:14 PM, SM wrote:

> At 00:41 06-12-2011, Brian Trammell wrote:
>> I have submitted rfc6046-bis-02 following WGLC; this revision =
addresses all WGLC comments, and the present draft is in my opinion =
ready for submission to the IESG for publication.
>=20
> Here are a few nits.
>=20
> In Section 1.1:
>=20
>  "This document updates [RFC6046] in the following ways:"
>=20
> That could be described as changes from RFC 6046 or an update of =
instead of "updates" as the document moves RFC 6046 to Historic.  Will =
Section 1.1 be included in the RFC?
>=20
> The reference to RFC 2119 should be normative.
>=20
> The reference to RFC 3492 is not needed as it is not referenced from =
the text.
>=20
> Regards,
> -sm=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Wed Dec  7 08:00:17 2011
Return-Path: <kathleen.moriarty@emc.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 2C3A621F8C3E for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level: 
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[AWL=0.398,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1gkAgtwhwT4 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:00:16 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF1E21F8C4B for <mile@ietf.org>; Wed,  7 Dec 2011 08:00:15 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7G0CAd019691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 7 Dec 2011 11:00:14 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 7 Dec 2011 11:00:04 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7G03Px014449 for <mile@ietf.org>; Wed, 7 Dec 2011 11:00:03 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Wed, 7 Dec 2011 11:00:03 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Wed, 7 Dec 2011 11:00:02 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
Thread-Index: Acy0LELtOAu0XoXeTKqUOZ/vusLclgAxkrJw
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net>
In-Reply-To: <6.2.5.6.2.20111206064135.09599cf0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:00:17 -0000

Hello Brian,

I found a couple of nits as the document relates to RFC6045-bis (as editor)=
 that would be good to correct for consistency.

In the introduction, network providers (NP) is listed.  RFC6045-bis moved t=
o the more generic term of service provider as the usage of these terms has=
 changed and service provider includes cloud, MSSPs, network, telecom, etc.=
  It is not referenced again in the document, so there is no need for the (=
SP) to follow the new term.

Please add a section that explicitly lists what is normative and informativ=
e.  This would be consistent with RFC6045-bis (section 1.1) and was require=
d during the IESG review for RFC6045.  Since the "Security Considerations" =
include security requirements, it will be important to note this as normati=
ve.  Requirements were broken out from considerations for RFC6045-bis.

The following sentence in section 3 may come up as a run-on in the Gen-ART =
review:=20
   "As the queries and replies in a RID message exchange may be
   significantly separated in time, the receiving RID system MAY return
   202 Accepted, terminate the connection, and at a later time connect
   to the requesting RID system and send the RID reply in an HTTP
   Request."

I found a typo (2nd line, 1st word should be 'an') in the following sentenc=
e:
   "If an RID system receives
   and improper RID message in an HTTP Response, or cannot process a RID
   message received in an HTTP Response due to an error on its own side,
   it MUST log the error and present it to the RID system administrator
   for handling; the error logging format is an implementation detail
   and is considered out of scope for this specification.


Thank you,
Kathleen (editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of SM
Sent: Tuesday, December 06, 2011 10:15 AM
To: mile@ietf.org
Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt

At 00:41 06-12-2011, Brian Trammell wrote:
>I have submitted rfc6046-bis-02 following WGLC; this revision=20
>addresses all WGLC comments, and the present draft is in my opinion=20
>ready for submission to the IESG for publication.

Here are a few nits.

In Section 1.1:

   "This document updates [RFC6046] in the following ways:"

That could be described as changes from RFC 6046 or an update of=20
instead of "updates" as the document moves RFC 6046 to=20
Historic.  Will Section 1.1 be included in the RFC?

The reference to RFC 2119 should be normative.

The reference to RFC 3492 is not needed as it is not referenced from the te=
xt.

Regards,
-sm=20

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


From lnunez@c3isecurity.com  Wed Dec  7 08:19:18 2011
Return-Path: <lnunez@c3isecurity.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 E3B7B21F8BBD for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F4ICKMmG4LEW for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:19:18 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D15021F8BC4 for <mile@ietf.org>; Wed,  7 Dec 2011 08:19:18 -0800 (PST)
Received: by ggnk5 with SMTP id k5so969792ggn.31 for <mile@ietf.org>; Wed, 07 Dec 2011 08:19:17 -0800 (PST)
Received: by 10.101.155.21 with SMTP id h21mr4580462ano.69.1323274757815; Wed, 07 Dec 2011 08:19:17 -0800 (PST)
Received: from [172.16.1.103] (cpe-066-057-025-190.nc.res.rr.com. [66.57.25.190]) by mx.google.com with ESMTPS id 33sm6216837ano.1.2011.12.07.08.19.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Dec 2011 08:19:17 -0800 (PST)
From: Luis Nunez <lnunez@c3isecurity.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Dec 2011 11:19:16 -0500
Message-Id: <475928F7-FB7F-4ACF-A100-84971A9E363A@c3isecurity.com>
To: mile@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [mile] Remediation (CRE)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:19:19 -0000

Remediation was something that was discussed on this list.  Below in =
update on the Common Remediation Enumeration draft specification.
This is not a recommendation for adoption by the MILE WG but for =
informational and awareness.  =20

=
http://csrc.nist.gov/publications/drafts/nistir-7831/Draft-NISTIR-7831.pdf=



-ln=

From Kent_Landfield@mcafee.com  Wed Dec  7 08:54:55 2011
Return-Path: <Kent_Landfield@mcafee.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 6DF1821F8B5D for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kt5Iilz3MmVa for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:54:54 -0800 (PST)
Received: from dalsmrelay2.nai.com (dalsmrelay2.nai.com [205.227.136.216]) by ietfa.amsl.com (Postfix) with ESMTP id 95BBB21F8B53 for <mile@ietf.org>; Wed,  7 Dec 2011 08:54:54 -0800 (PST)
Received: from (unknown [10.64.5.51]) by dalsmrelay2.nai.com with smtp id 34b6_115e_2d16aba0_20f4_11e1_a83c_00219b929abd; Wed, 07 Dec 2011 10:54:49 -0600
Received: from AMERDALEXMB1.corp.nai.org ([fe80::387d:3d79:ad3b:b517]) by DALEXHT1.corp.nai.org ([::1]) with mapi; Wed, 7 Dec 2011 10:53:33 -0600
From: <Kent_Landfield@McAfee.com>
To: <lnunez@c3isecurity.com>, <mile@ietf.org>
Date: Wed, 7 Dec 2011 10:53:54 -0600
Thread-Topic: [mile] Remediation (CRE)
Thread-Index: Acy1AMDOdyRJnW3CQ5qCY566MzuK8Q==
Message-ID: <CB0503AD.26367%kent_landfield@mcafee.com>
In-Reply-To: <475928F7-FB7F-4ACF-A100-84971A9E363A@c3isecurity.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] Remediation (CRE)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:54:55 -0000

While good for informational and awareness purposes, this draft and CRE in =
general is going nowhere at present.  Remediation as a whole within the SCA=
P communities has a lot of work to be done before anyone could seriously co=
nsider it useful.

I agree with Luis.  This is not recommended for adoption.

Kent Landfield
Director Content Strategy, Architecture and Standards

McAfee, Inc.
5000 Headquarters Dr.
Plano, Texas 75024

Direct: +1.972.963.7096
Mobile: +1.817.637.8026
Web: www.mcafee.com<http://www.mcafee.com/>

From: Luis Nunez <lnunez@c3isecurity.com<mailto:lnunez@c3isecurity.com>>
Date: Wed, 7 Dec 2011 10:19:16 -0600
To: "mile@ietf.org<mailto:mile@ietf.org>" <mile@ietf.org<mailto:mile@ietf.o=
rg>>
Subject: [mile] Remediation (CRE)

Remediation was something that was discussed on this list.  Below in update=
 on the Common Remediation Enumeration draft specification.
This is not a recommendation for adoption by the MILE WG but for informatio=
nal and awareness.

http://csrc.nist.gov/publications/drafts/nistir-7831/Draft-NISTIR-7831.pdf


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


From trammell@tik.ee.ethz.ch  Wed Dec  7 08:57:40 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 2A39721F8BBD for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5PzhIu0rPPK for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 08:57:39 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id DFD5221F8BBC for <mile@ietf.org>; Wed,  7 Dec 2011 08:57:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 42633D9307; Wed,  7 Dec 2011 17:57:36 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id llda08WxsKSR; Wed,  7 Dec 2011 17:57:36 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 13A20D9300; Wed,  7 Dec 2011 17:57:36 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com>
Date: Wed, 7 Dec 2011 17:57:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B36E7EE5-CD8F-4C3A-ACCC-A491619BDF37@tik.ee.ethz.ch>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net> <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com>
To: <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 16:57:40 -0000

Hi, Kathleen,

Thanks for the comments, will incorporate these into the (shortly =
upcoming) revision of the draft.

Best regards,

Brian (as author of 6046-bis)

On Dec 7, 2011, at 5:00 PM, <kathleen.moriarty@emc.com> wrote:

> Hello Brian,
>=20
> I found a couple of nits as the document relates to RFC6045-bis (as =
editor) that would be good to correct for consistency.
>=20
> In the introduction, network providers (NP) is listed.  RFC6045-bis =
moved to the more generic term of service provider as the usage of these =
terms has changed and service provider includes cloud, MSSPs, network, =
telecom, etc.  It is not referenced again in the document, so there is =
no need for the (SP) to follow the new term.
>=20
> Please add a section that explicitly lists what is normative and =
informative.  This would be consistent with RFC6045-bis (section 1.1) =
and was required during the IESG review for RFC6045.  Since the =
"Security Considerations" include security requirements, it will be =
important to note this as normative.  Requirements were broken out from =
considerations for RFC6045-bis.
>=20
> The following sentence in section 3 may come up as a run-on in the =
Gen-ART review:=20
>   "As the queries and replies in a RID message exchange may be
>   significantly separated in time, the receiving RID system MAY return
>   202 Accepted, terminate the connection, and at a later time connect
>   to the requesting RID system and send the RID reply in an HTTP
>   Request."
>=20
> I found a typo (2nd line, 1st word should be 'an') in the following =
sentence:
>   "If an RID system receives
>   and improper RID message in an HTTP Response, or cannot process a =
RID
>   message received in an HTTP Response due to an error on its own =
side,
>   it MUST log the error and present it to the RID system administrator
>   for handling; the error logging format is an implementation detail
>   and is considered out of scope for this specification.
>=20
>=20
> Thank you,
> Kathleen (editor)
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of SM
> Sent: Tuesday, December 06, 2011 10:15 AM
> To: mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: =
draft-ietf-mile-rfc6046-bis-02.txt
>=20
> At 00:41 06-12-2011, Brian Trammell wrote:
>> I have submitted rfc6046-bis-02 following WGLC; this revision=20
>> addresses all WGLC comments, and the present draft is in my opinion=20=

>> ready for submission to the IESG for publication.
>=20
> Here are a few nits.
>=20
> In Section 1.1:
>=20
>   "This document updates [RFC6046] in the following ways:"
>=20
> That could be described as changes from RFC 6046 or an update of=20
> instead of "updates" as the document moves RFC 6046 to=20
> Historic.  Will Section 1.1 be included in the RFC?
>=20
> The reference to RFC 2119 should be normative.
>=20
> The reference to RFC 3492 is not needed as it is not referenced from =
the text.
>=20
> Regards,
> -sm=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From internet-drafts@ietf.org  Wed Dec  7 09:01:17 2011
Return-Path: <internet-drafts@ietf.org>
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 6B2C221F8BD8; Wed,  7 Dec 2011 09:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFNN25ar-zel; Wed,  7 Dec 2011 09:01:16 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D968821F8BB0; Wed,  7 Dec 2011 09:01:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111207170116.14636.76016.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2011 09:01:16 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 17:01:17 -0000

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

	Title           : Transport of Real-time Inter-network Defense (RID) Messa=
ges
	Author(s)       : Brian Trammell
	Filename        : draft-ietf-mile-rfc6046-bis-03.txt
	Pages           : 7
	Date            : 2011-12-07

   The Incident Object Description Exchange Format (IODEF) defines a
   common XML format for document exchange, and Realtime Internetwork
   Defense (RID) defines extensions to IODEF intended for the
   cooperative handling of security incidents within consortia of
   network operators and enterprises.  This document specifies a
   transport protocol for RID based upon the passing of RID messages
   over HTTP/TLS.  This document updates the previous [RFC6046] to
   change the intended status to Proposed Standard, and to reference the
   updated RID specification.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-03.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-03.txt


From kathleen.moriarty@emc.com  Wed Dec  7 09:59:20 2011
Return-Path: <kathleen.moriarty@emc.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 B5F7C21F8C1A for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 09:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.237
X-Spam-Level: 
X-Spam-Status: No, score=-6.237 tagged_above=-999 required=5 tests=[AWL=0.362,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TiWwhkxpjxqH for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 09:59:19 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id BB66121F8C16 for <mile@ietf.org>; Wed,  7 Dec 2011 09:59:19 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7HxAhl026368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Dec 2011 12:59:16 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 7 Dec 2011 12:59:02 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7Hx1Nj024782; Wed, 7 Dec 2011 12:59:01 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Wed, 7 Dec 2011 12:59:00 -0500
From: <kathleen.moriarty@emc.com>
To: <trammell@tik.ee.ethz.ch>
Date: Wed, 7 Dec 2011 12:58:59 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
Thread-Index: Acy1As3VcQTzW9psQ/a4srQse2BwNgABnELg
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E9094@MX06A.corp.emc.com>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net> <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com> <B36E7EE5-CD8F-4C3A-ACCC-A491619BDF37@tik.ee.ethz.ch>
In-Reply-To: <B36E7EE5-CD8F-4C3A-ACCC-A491619BDF37@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 17:59:20 -0000

Hi Brian,

Thank you for making the updates.  The document looks good.

I just have a few nits we should take care of before sending it to the IESG=
.

In the introduction, you can just include "service providers" without "(SPs=
)" as it is never referenced again in the document.  This will get caught i=
n Gen-ART, so it may save corrections needed there (unless others are found=
).

The idnits complains about the abstract not stating that this document obso=
letes RFC6046.  As I understand it, this is used by the RFC Editor to make =
sure that action occurs, moving RFC6046 to Historic.  This is listed in the=
 changes, but may be too buried for the RFC Editor.

Sean - do you have an opinion on this one?  Is it OK as is?

Thank you,
Kathleen (WG Chair)

-----Original Message-----
From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]=20
Sent: Wednesday, December 07, 2011 11:58 AM
To: Moriarty, Kathleen
Cc: mile@ietf.org
Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt

Hi, Kathleen,

Thanks for the comments, will incorporate these into the (shortly upcoming)=
 revision of the draft.

Best regards,

Brian (as author of 6046-bis)

On Dec 7, 2011, at 5:00 PM, <kathleen.moriarty@emc.com> wrote:

> Hello Brian,
>=20
> I found a couple of nits as the document relates to RFC6045-bis (as edito=
r) that would be good to correct for consistency.
>=20
> In the introduction, network providers (NP) is listed.  RFC6045-bis moved=
 to the more generic term of service provider as the usage of these terms h=
as changed and service provider includes cloud, MSSPs, network, telecom, et=
c.  It is not referenced again in the document, so there is no need for the=
 (SP) to follow the new term.
>=20
> Please add a section that explicitly lists what is normative and informat=
ive.  This would be consistent with RFC6045-bis (section 1.1) and was requi=
red during the IESG review for RFC6045.  Since the "Security Considerations=
" include security requirements, it will be important to note this as norma=
tive.  Requirements were broken out from considerations for RFC6045-bis.
>=20
> The following sentence in section 3 may come up as a run-on in the Gen-AR=
T review:=20
>   "As the queries and replies in a RID message exchange may be
>   significantly separated in time, the receiving RID system MAY return
>   202 Accepted, terminate the connection, and at a later time connect
>   to the requesting RID system and send the RID reply in an HTTP
>   Request."
>=20
> I found a typo (2nd line, 1st word should be 'an') in the following sente=
nce:
>   "If an RID system receives
>   and improper RID message in an HTTP Response, or cannot process a RID
>   message received in an HTTP Response due to an error on its own side,
>   it MUST log the error and present it to the RID system administrator
>   for handling; the error logging format is an implementation detail
>   and is considered out of scope for this specification.
>=20
>=20
> Thank you,
> Kathleen (editor)
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
M
> Sent: Tuesday, December 06, 2011 10:15 AM
> To: mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>=20
> At 00:41 06-12-2011, Brian Trammell wrote:
>> I have submitted rfc6046-bis-02 following WGLC; this revision=20
>> addresses all WGLC comments, and the present draft is in my opinion=20
>> ready for submission to the IESG for publication.
>=20
> Here are a few nits.
>=20
> In Section 1.1:
>=20
>   "This document updates [RFC6046] in the following ways:"
>=20
> That could be described as changes from RFC 6046 or an update of=20
> instead of "updates" as the document moves RFC 6046 to=20
> Historic.  Will Section 1.1 be included in the RFC?
>=20
> The reference to RFC 2119 should be normative.
>=20
> The reference to RFC 3492 is not needed as it is not referenced from the =
text.
>=20
> Regards,
> -sm=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile



From turners@ieca.com  Wed Dec  7 10:27:07 2011
Return-Path: <turners@ieca.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 EB33A21F8BE4 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 10:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYcCSQcxu-Xb for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 10:27:07 -0800 (PST)
Received: from gateway11.websitewelcome.com (gateway11.websitewelcome.com [67.18.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id E1D7D21F8BD3 for <mile@ietf.org>; Wed,  7 Dec 2011 10:27:06 -0800 (PST)
Received: by gateway11.websitewelcome.com (Postfix, from userid 5011) id EBBEE6ECA11DE; Wed,  7 Dec 2011 12:27:05 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway11.websitewelcome.com (Postfix) with ESMTP id DD6676ECA119D for <mile@ietf.org>; Wed,  7 Dec 2011 12:27:05 -0600 (CST)
Received: from [71.191.11.37] (port=44297 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RYMCv-0003da-8t; Wed, 07 Dec 2011 12:27:05 -0600
Message-ID: <4EDFAFF5.7030305@ieca.com>
Date: Wed, 07 Dec 2011 13:27:01 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net> <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com> <B36E7EE5-CD8F-4C3A-ACCC-A491619BDF37@tik.ee.ethz.ch> <AE31510960917D478171C79369B660FA0E1A6E9094@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E9094@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-11-37.washdc.east.verizon.net (thunderfish.local) [71.191.11.37]:44297
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 18:27:08 -0000

On 12/7/11 12:58 PM, kathleen.moriarty@emc.com wrote:
> Hi Brian,
>
> Thank you for making the updates.  The document looks good.
>
> I just have a few nits we should take care of before sending it to the IESG.
>
> In the introduction, you can just include "service providers" without "(SPs)" as it is never referenced again in the document.  This will get caught in Gen-ART, so it may save corrections needed there (unless others are found).
>
> The idnits complains about the abstract not stating that this document obsoletes RFC6046.  As I understand it, this is used by the RFC Editor to make sure that action occurs, moving RFC6046 to Historic.  This is listed in the changes, but may be too buried for the RFC Editor.
>
> Sean - do you have an opinion on this one?  Is it OK as is?

The tool does complain, but we recently had an IESG statement on this:

http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html

As long as it's in the introduction somewhere then it's okay.  I think 
the tool just hasn't caught up yet.

spt

> Thank you,
> Kathleen (WG Chair)
>
> -----Original Message-----
> From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]
> Sent: Wednesday, December 07, 2011 11:58 AM
> To: Moriarty, Kathleen
> Cc: mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>
> Hi, Kathleen,
>
> Thanks for the comments, will incorporate these into the (shortly upcoming) revision of the draft.
>
> Best regards,
>
> Brian (as author of 6046-bis)
>
> On Dec 7, 2011, at 5:00 PM,<kathleen.moriarty@emc.com>  wrote:
>
>> Hello Brian,
>>
>> I found a couple of nits as the document relates to RFC6045-bis (as editor) that would be good to correct for consistency.
>>
>> In the introduction, network providers (NP) is listed.  RFC6045-bis moved to the more generic term of service provider as the usage of these terms has changed and service provider includes cloud, MSSPs, network, telecom, etc.  It is not referenced again in the document, so there is no need for the (SP) to follow the new term.
>>
>> Please add a section that explicitly lists what is normative and informative.  This would be consistent with RFC6045-bis (section 1.1) and was required during the IESG review for RFC6045.  Since the "Security Considerations" include security requirements, it will be important to note this as normative.  Requirements were broken out from considerations for RFC6045-bis.
>>
>> The following sentence in section 3 may come up as a run-on in the Gen-ART review:
>>    "As the queries and replies in a RID message exchange may be
>>    significantly separated in time, the receiving RID system MAY return
>>    202 Accepted, terminate the connection, and at a later time connect
>>    to the requesting RID system and send the RID reply in an HTTP
>>    Request."
>>
>> I found a typo (2nd line, 1st word should be 'an') in the following sentence:
>>    "If an RID system receives
>>    and improper RID message in an HTTP Response, or cannot process a RID
>>    message received in an HTTP Response due to an error on its own side,
>>    it MUST log the error and present it to the RID system administrator
>>    for handling; the error logging format is an implementation detail
>>    and is considered out of scope for this specification.
>>
>>
>> Thank you,
>> Kathleen (editor)
>>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of SM
>> Sent: Tuesday, December 06, 2011 10:15 AM
>> To: mile@ietf.org
>> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>>
>> At 00:41 06-12-2011, Brian Trammell wrote:
>>> I have submitted rfc6046-bis-02 following WGLC; this revision
>>> addresses all WGLC comments, and the present draft is in my opinion
>>> ready for submission to the IESG for publication.
>>
>> Here are a few nits.
>>
>> In Section 1.1:
>>
>>    "This document updates [RFC6046] in the following ways:"
>>
>> That could be described as changes from RFC 6046 or an update of
>> instead of "updates" as the document moves RFC 6046 to
>> Historic.  Will Section 1.1 be included in the RFC?
>>
>> The reference to RFC 2119 should be normative.
>>
>> The reference to RFC 3492 is not needed as it is not referenced from the text.
>>
>> Regards,
>> -sm
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>
>

From kathleen.moriarty@emc.com  Wed Dec  7 10:31:13 2011
Return-Path: <kathleen.moriarty@emc.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 BA20821F8C1A for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 10:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.267
X-Spam-Level: 
X-Spam-Status: No, score=-6.267 tagged_above=-999 required=5 tests=[AWL=0.332,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6V5DfNyzlWs1 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 10:31:13 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B904C21F8BDC for <mile@ietf.org>; Wed,  7 Dec 2011 10:31:12 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7IV9Wd007668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Dec 2011 13:31:10 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 7 Dec 2011 13:31:00 -0500
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7IUxi1030135; Wed, 7 Dec 2011 13:30:59 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Wed, 7 Dec 2011 13:30:58 -0500
From: <kathleen.moriarty@emc.com>
To: <turners@ieca.com>
Date: Wed, 7 Dec 2011 13:30:58 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
Thread-Index: Acy1DeWkjY5IHUUPSyifxBkHh0gWPgAAE3Jg
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E90B1@MX06A.corp.emc.com>
References: <20111206083133.24085.1382.idtracker@ietfa.amsl.com> <65E72942-DDB0-4386-B34A-61750B230B63@tik.ee.ethz.ch> <6.2.5.6.2.20111206064135.09599cf0@resistor.net> <AE31510960917D478171C79369B660FA0E1A6E900A@MX06A.corp.emc.com> <B36E7EE5-CD8F-4C3A-ACCC-A491619BDF37@tik.ee.ethz.ch> <AE31510960917D478171C79369B660FA0E1A6E9094@MX06A.corp.emc.com> <4EDFAFF5.7030305@ieca.com>
In-Reply-To: <4EDFAFF5.7030305@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 18:31:13 -0000

Thank you, Sean!

-----Original Message-----
From: Sean Turner [mailto:turners@ieca.com]=20
Sent: Wednesday, December 07, 2011 1:27 PM
To: Moriarty, Kathleen
Cc: trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt

On 12/7/11 12:58 PM, kathleen.moriarty@emc.com wrote:
> Hi Brian,
>
> Thank you for making the updates.  The document looks good.
>
> I just have a few nits we should take care of before sending it to the IE=
SG.
>
> In the introduction, you can just include "service providers" without "(S=
Ps)" as it is never referenced again in the document.  This will get caught=
 in Gen-ART, so it may save corrections needed there (unless others are fou=
nd).
>
> The idnits complains about the abstract not stating that this document ob=
soletes RFC6046.  As I understand it, this is used by the RFC Editor to mak=
e sure that action occurs, moving RFC6046 to Historic.  This is listed in t=
he changes, but may be too buried for the RFC Editor.
>
> Sean - do you have an opinion on this one?  Is it OK as is?

The tool does complain, but we recently had an IESG statement on this:

http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html

As long as it's in the introduction somewhere then it's okay.  I think=20
the tool just hasn't caught up yet.

spt

> Thank you,
> Kathleen (WG Chair)
>
> -----Original Message-----
> From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]
> Sent: Wednesday, December 07, 2011 11:58 AM
> To: Moriarty, Kathleen
> Cc: mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>
> Hi, Kathleen,
>
> Thanks for the comments, will incorporate these into the (shortly upcomin=
g) revision of the draft.
>
> Best regards,
>
> Brian (as author of 6046-bis)
>
> On Dec 7, 2011, at 5:00 PM,<kathleen.moriarty@emc.com>  wrote:
>
>> Hello Brian,
>>
>> I found a couple of nits as the document relates to RFC6045-bis (as edit=
or) that would be good to correct for consistency.
>>
>> In the introduction, network providers (NP) is listed.  RFC6045-bis move=
d to the more generic term of service provider as the usage of these terms =
has changed and service provider includes cloud, MSSPs, network, telecom, e=
tc.  It is not referenced again in the document, so there is no need for th=
e (SP) to follow the new term.
>>
>> Please add a section that explicitly lists what is normative and informa=
tive.  This would be consistent with RFC6045-bis (section 1.1) and was requ=
ired during the IESG review for RFC6045.  Since the "Security Consideration=
s" include security requirements, it will be important to note this as norm=
ative.  Requirements were broken out from considerations for RFC6045-bis.
>>
>> The following sentence in section 3 may come up as a run-on in the Gen-A=
RT review:
>>    "As the queries and replies in a RID message exchange may be
>>    significantly separated in time, the receiving RID system MAY return
>>    202 Accepted, terminate the connection, and at a later time connect
>>    to the requesting RID system and send the RID reply in an HTTP
>>    Request."
>>
>> I found a typo (2nd line, 1st word should be 'an') in the following sent=
ence:
>>    "If an RID system receives
>>    and improper RID message in an HTTP Response, or cannot process a RID
>>    message received in an HTTP Response due to an error on its own side,
>>    it MUST log the error and present it to the RID system administrator
>>    for handling; the error logging format is an implementation detail
>>    and is considered out of scope for this specification.
>>
>>
>> Thank you,
>> Kathleen (editor)
>>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of =
SM
>> Sent: Tuesday, December 06, 2011 10:15 AM
>> To: mile@ietf.org
>> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-02.txt
>>
>> At 00:41 06-12-2011, Brian Trammell wrote:
>>> I have submitted rfc6046-bis-02 following WGLC; this revision
>>> addresses all WGLC comments, and the present draft is in my opinion
>>> ready for submission to the IESG for publication.
>>
>> Here are a few nits.
>>
>> In Section 1.1:
>>
>>    "This document updates [RFC6046] in the following ways:"
>>
>> That could be described as changes from RFC 6046 or an update of
>> instead of "updates" as the document moves RFC 6046 to
>> Historic.  Will Section 1.1 be included in the RFC?
>>
>> The reference to RFC 2119 should be normative.
>>
>> The reference to RFC 3492 is not needed as it is not referenced from the=
 text.
>>
>> Regards,
>> -sm
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>
>


From internet-drafts@ietf.org  Wed Dec  7 11:08:59 2011
Return-Path: <internet-drafts@ietf.org>
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 A392C21F8C20; Wed,  7 Dec 2011 11:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIv6Ez+fYoBl; Wed,  7 Dec 2011 11:08:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC6F21F8BE5; Wed,  7 Dec 2011 11:08:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111207190858.26697.51494.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2011 11:08:58 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 19:08:59 -0000

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

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-03.txt
	Pages           : 73
	Date            : 2011-12-07

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-03.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-03.txt


From kathleen.moriarty@emc.com  Wed Dec  7 11:12:07 2011
Return-Path: <kathleen.moriarty@emc.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 7AB9121F8C5A for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 11:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.293
X-Spam-Level: 
X-Spam-Status: No, score=-6.293 tagged_above=-999 required=5 tests=[AWL=0.306,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aybaevNDmYvt for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 11:12:06 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 66E3621F8C52 for <mile@ietf.org>; Wed,  7 Dec 2011 11:12:06 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7JC58W010274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 7 Dec 2011 14:12:05 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 7 Dec 2011 14:11:53 -0500
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB7JBqlS014912 for <mile@ietf.org>; Wed, 7 Dec 2011 14:11:53 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Wed, 7 Dec 2011 14:11:52 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Wed, 7 Dec 2011 14:11:51 -0500
Thread-Topic: New Version Notification for draft-ietf-mile-rfc6045-bis-03.txt
Thread-Index: Acy1E71/Xz3+SRSHQEOr26fzuk+kCwAABPSQ
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E90D4@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] FW: New Version Notification for draft-ietf-mile-rfc6045-bis-03.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 19:12:07 -0000

VGhlIG5ldyB2ZXJzaW9uIGNvcnJlY3RzIGEgbml0IHdpdGggb25lIG9mIHRoZSBleGFtcGxlcyB0
aGF0IGhhZCBhIDwvc2VjdGlvbj4gaW4gaXQgZnJvbSBhIG1pc3Rha2UgaW4gdGhlIFhNTCBkb2N1
bWVudCB1c2VkIHRvIGNyZWF0ZSB0aGUgZHJhZnQuDQoNCkkgYmVsaWV2ZSBhbGwgY29tbWVudHMg
aGF2ZSBiZWVuIGFkZHJlc3NlZC4gIA0KDQpUaGFuayB5b3UgYWxsIGZvciB0aGUgcmV2aWV3cyEN
CkthdGhsZWVuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDog
V2VkbmVzZGF5LCBEZWNlbWJlciAwNywgMjAxMSAyOjA5IFBNDQpUbzogTW9yaWFydHksIEthdGhs
ZWVuDQpDYzogTW9yaWFydHksIEthdGhsZWVuDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmlj
YXRpb24gZm9yIGRyYWZ0LWlldGYtbWlsZS1yZmM2MDQ1LWJpcy0wMy50eHQNCg0KQSBuZXcgdmVy
c2lvbiBvZiBJLUQsIGRyYWZ0LWlldGYtbWlsZS1yZmM2MDQ1LWJpcy0wMy50eHQgaGFzIGJlZW4g
c3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBLYXRobGVlbiBNb3JpYXJ0eSBhbmQgcG9zdGVkIHRv
IHRoZSBJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQtaWV0Zi1taWxlLXJmYzYw
NDUtYmlzDQpSZXZpc2lvbjoJIDAzDQpUaXRsZToJCSBSZWFsLXRpbWUgSW50ZXItbmV0d29yayBE
ZWZlbnNlIChSSUQpDQpDcmVhdGlvbiBkYXRlOgkgMjAxMS0xMi0wNw0KV0cgSUQ6CQkgbWlsZQ0K
TnVtYmVyIG9mIHBhZ2VzOiA3Mw0KDQpBYnN0cmFjdDoNCiAgIFNlY3VyaXR5IGluY2lkZW50cywg
c3VjaCBhcyBzeXN0ZW0gY29tcHJvbWlzZXMsIHdvcm1zLCB2aXJ1c2VzLA0KICAgcGhpc2hpbmcg
aW5jaWRlbnRzLCBhbmQgZGVuaWFsIG9mIHNlcnZpY2UsIHR5cGljYWxseSByZXN1bHQgaW4gdGhl
DQogICBsb3NzIG9mIHNlcnZpY2UsIGRhdGEsIGFuZCByZXNvdXJjZXMgYm90aCBodW1hbiBhbmQg
c3lzdGVtLiAgU2VydmljZQ0KICAgcHJvdmlkZXJzIGFuZCBDb21wdXRlciBTZWN1cml0eSBJbmNp
ZGVudCBSZXNwb25zZSBUZWFtcyBuZWVkIHRvIGJlDQogICBlcXVpcHBlZCBhbmQgcmVhZHkgdG8g
YXNzaXN0IGluIGNvbW11bmljYXRpbmcgYW5kIHRyYWNpbmcgc2VjdXJpdHkNCiAgIGluY2lkZW50
cyB3aXRoIHRvb2xzIGFuZCBwcm9jZWR1cmVzIGluIHBsYWNlIGJlZm9yZSB0aGUgb2NjdXJyZW5j
ZSBvZg0KICAgYW4gYXR0YWNrLiAgUmVhbC10aW1lIEludGVyLW5ldHdvcmsgRGVmZW5zZSAoUklE
KSBvdXRsaW5lcyBhDQogICBwcm9hY3RpdmUgaW50ZXItbmV0d29yayBjb21tdW5pY2F0aW9uIG1l
dGhvZCB0byBmYWNpbGl0YXRlIHNoYXJpbmcNCiAgIGluY2lkZW50IGhhbmRsaW5nIGRhdGEgd2hp
bGUgaW50ZWdyYXRpbmcgZXhpc3RpbmcgZGV0ZWN0aW9uLCB0cmFjaW5nLA0KICAgc291cmNlIGlk
ZW50aWZpY2F0aW9uLCBhbmQgbWl0aWdhdGlvbiBtZWNoYW5pc21zIGZvciBhIGNvbXBsZXRlDQog
ICBpbmNpZGVudCBoYW5kbGluZyBzb2x1dGlvbi4gIENvbWJpbmluZyB0aGVzZSBjYXBhYmlsaXRp
ZXMgaW4gYQ0KICAgY29tbXVuaWNhdGlvbiBzeXN0ZW0gcHJvdmlkZXMgYSB3YXkgdG8gYWNoaWV2
ZSBoaWdoZXIgc2VjdXJpdHkgbGV2ZWxzDQogICBvbiBuZXR3b3Jrcy4gIFBvbGljeSBndWlkZWxp
bmVzIGZvciBoYW5kbGluZyBpbmNpZGVudHMgYXJlDQogICByZWNvbW1lbmRlZCBhbmQgY2FuIGJl
IGFncmVlZCB1cG9uIGJ5IGEgY29uc29ydGl1bSB1c2luZyB0aGUgc2VjdXJpdHkNCiAgIHJlY29t
bWVuZGF0aW9ucyBhbmQgY29uc2lkZXJhdGlvbnMuDQoNCiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICANCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=

From turners@ieca.com  Wed Dec  7 14:11:26 2011
Return-Path: <turners@ieca.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 2FCB721F8B0E for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:11:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jzG1bo8rlg2 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:11:25 -0800 (PST)
Received: from gateway01.websitewelcome.com (gateway01.websitewelcome.com [69.56.224.19]) by ietfa.amsl.com (Postfix) with ESMTP id 859AD21F8B08 for <mile@ietf.org>; Wed,  7 Dec 2011 14:11:25 -0800 (PST)
Received: by gateway01.websitewelcome.com (Postfix, from userid 5007) id 63F05BB28878; Wed,  7 Dec 2011 16:11:24 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway01.websitewelcome.com (Postfix) with ESMTP id 3F740BB287B5 for <mile@ietf.org>; Wed,  7 Dec 2011 16:11:24 -0600 (CST)
Received: from [71.191.11.37] (port=38652 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RYPhz-0001S6-Rb for mile@ietf.org; Wed, 07 Dec 2011 16:11:24 -0600
Message-ID: <4EDFE48C.2000606@ieca.com>
Date: Wed, 07 Dec 2011 17:11:24 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: mile@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-11-37.washdc.east.verizon.net (thunderfish.local) [71.191.11.37]:38652
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 3
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Subject: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 22:11:26 -0000

Here is my review of draft-ietf-mile-rfc6046-bis.

1) s1.1/s4: s1 contains the following:

   o The required version of TLS is upgraded to 1.1.

But, I don't see any text that says TLS 1.1 is the MUST.  There's this 
statement in s4:

   Although TLS
   implementations typically support the older SSL protocol, a RID peer
   MUST NOT request, offer, or use any version of SSL, or any version of
   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
   prior versions of the protocol; see Appendix E of [RFC5246] for more.

To me that reads like the required TLS version is at least 1.1 but could 
be 1.2.  So maybe the summarized change is:

   o  The minimum required version of TLS is upgraded to 1.1.

Note that this requirement is going to require changes to most TLS 
implementations, but I bet you knew that.

2) s3 contains the following:

  When a RID message must be sent,
  the sending RID system connects to the receiving RID system and sends
  the message, optionally receiving a message in reply.

Maybe swap must for is (must usually makes people wonder if it's 
supposed to be 2119ed and if it's not lets use another word if we can):

  When a RID message is sent,
  the sending RID system connects to the receiving RID system and sends
  the message, optionally receiving a message in reply.

3) s3: Need a pointer to s10 for the port assignment (see later comment).

  Consistent with BCP 56, RID systems listen for TCP
  connections on port 4590 (see Section 10.3).

4) s3: must or MUST?

  When a RID
  System's address changes, contact point information within the
  consortium must be updated out of band.

5) s10: Please instruct IANA to update the registry reference to point 
to this document.  I'd rather have it point to this document than RFC 
6046 because you're obsoleting it.

6) s12.1: Please refer to the mile version of 6045bis as opposed to the 
individual version.

7) s6/s7.2: Is RFC6125 really informative?  I think we want people to 
follow the rules defined therein - don't we?

8) I'm not so sure about listing which bits are informative/normative, 
but here's my initial thoughts on the choices:

- Isn't s1.2 normative - if somebody copied this but didn't follow our 
classification then what would we do?

- Isn't s2 also normative because it defines the meanings of 
MUST/SHOULD/etc?  We shouldn't let somebody decide to change the 
meanings of these words.

- Isn't s7.1 normative - it lists the normative references?

What does normative/informative mean in the context of section in an 
draft/RFC?  I understand what it means in the context of a reference, 
but not so much with sections.  Are you saying implementations that 
claim conformance with this standard MUST conform to those sections?  I 
think it makes sense to explain what you mean when you say a section is 
normative/informative. Let's not assume people know what it's supposed 
to mean ;)

spt

From turners@ieca.com  Wed Dec  7 14:37:40 2011
Return-Path: <turners@ieca.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 712B821F8713 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.266
X-Spam-Level: 
X-Spam-Status: No, score=-102.266 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZI4+iByypms for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:37:39 -0800 (PST)
Received: from gateway09.websitewelcome.com (gateway09.websitewelcome.com [67.18.10.7]) by ietfa.amsl.com (Postfix) with ESMTP id D5B0921F84CC for <mile@ietf.org>; Wed,  7 Dec 2011 14:37:39 -0800 (PST)
Received: by gateway09.websitewelcome.com (Postfix, from userid 507) id C8E557B24D260; Wed,  7 Dec 2011 16:37:38 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway09.websitewelcome.com (Postfix) with ESMTP id BAB387B24D231 for <mile@ietf.org>; Wed,  7 Dec 2011 16:37:38 -0600 (CST)
Received: from [71.191.11.37] (port=44827 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RYQ7O-0007Ic-A9 for mile@ietf.org; Wed, 07 Dec 2011 16:37:38 -0600
Message-ID: <4EDFEAAF.4010604@ieca.com>
Date: Wed, 07 Dec 2011 17:37:35 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: mile@ietf.org
References: <4EDFE48C.2000606@ieca.com>
In-Reply-To: <4EDFE48C.2000606@ieca.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-11-37.washdc.east.verizon.net (thunderfish.local) [71.191.11.37]:44827
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 7
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 22:37:40 -0000

One more:

8) Maybe we should just delete this sentence from the abstract:

  This document updates [RFC6046], and to
  change the intended status to Proposed Standard, and to reference the
  updated RID specification.

I'm concerned we'll end up discussing the fact the abstract says updates 
but the header says obsoletes and when wordsmithing everybody gets a cut 
;)  Also, references in the abstract are a no-no and the IESG tries to 
lighten their load by removing them before drafts get there.  Since this 
draft is obsoleting 6046 and there's a changes section it's probably not 
needed to list the changes in the abstract.  Or swap updates to obsoletes.

spt

On 12/7/11 5:11 PM, Sean Turner wrote:
> Here is my review of draft-ietf-mile-rfc6046-bis.
>
> 1) s1.1/s4: s1 contains the following:
>
> o The required version of TLS is upgraded to 1.1.
>
> But, I don't see any text that says TLS 1.1 is the MUST. There's this
> statement in s4:
>
> Although TLS
> implementations typically support the older SSL protocol, a RID peer
> MUST NOT request, offer, or use any version of SSL, or any version of
> TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
> prior versions of the protocol; see Appendix E of [RFC5246] for more.
>
> To me that reads like the required TLS version is at least 1.1 but could
> be 1.2. So maybe the summarized change is:
>
> o The minimum required version of TLS is upgraded to 1.1.
>
> Note that this requirement is going to require changes to most TLS
> implementations, but I bet you knew that.
>
> 2) s3 contains the following:
>
> When a RID message must be sent,
> the sending RID system connects to the receiving RID system and sends
> the message, optionally receiving a message in reply.
>
> Maybe swap must for is (must usually makes people wonder if it's
> supposed to be 2119ed and if it's not lets use another word if we can):
>
> When a RID message is sent,
> the sending RID system connects to the receiving RID system and sends
> the message, optionally receiving a message in reply.
>
> 3) s3: Need a pointer to s10 for the port assignment (see later comment).
>
> Consistent with BCP 56, RID systems listen for TCP
> connections on port 4590 (see Section 10.3).
>
> 4) s3: must or MUST?
>
> When a RID
> System's address changes, contact point information within the
> consortium must be updated out of band.
>
> 5) s10: Please instruct IANA to update the registry reference to point
> to this document. I'd rather have it point to this document than RFC
> 6046 because you're obsoleting it.
>
> 6) s12.1: Please refer to the mile version of 6045bis as opposed to the
> individual version.
>
> 7) s6/s7.2: Is RFC6125 really informative? I think we want people to
> follow the rules defined therein - don't we?
>
> 8) I'm not so sure about listing which bits are informative/normative,
> but here's my initial thoughts on the choices:
>
> - Isn't s1.2 normative - if somebody copied this but didn't follow our
> classification then what would we do?
>
> - Isn't s2 also normative because it defines the meanings of
> MUST/SHOULD/etc? We shouldn't let somebody decide to change the meanings
> of these words.
>
> - Isn't s7.1 normative - it lists the normative references?
>
> What does normative/informative mean in the context of section in an
> draft/RFC? I understand what it means in the context of a reference, but
> not so much with sections. Are you saying implementations that claim
> conformance with this standard MUST conform to those sections? I think
> it makes sense to explain what you mean when you say a section is
> normative/informative. Let's not assume people know what it's supposed
> to mean ;)
>
> spt
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

From msk@cloudmark.com  Wed Dec  7 14:42:20 2011
Return-Path: <msk@cloudmark.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 03B8011E80B4 for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQtFQcKhvixw for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:42:19 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2CB11E80A6 for <mile@ietf.org>; Wed,  7 Dec 2011 14:42:19 -0800 (PST)
Received: from malice.corp.cloudmark.com (172.22.10.71) by EXCH-HTCAS901.corp.cloudmark.com (172.22.10.73) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 7 Dec 2011 14:42:19 -0800
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Wed, 7 Dec 2011 14:42:18 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Wed, 7 Dec 2011 14:42:17 -0800
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy1LStx0ahwfLmwSs6NtPupr1+KxAAAwxeQ
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com>
References: <4EDFE48C.2000606@ieca.com>
In-Reply-To: <4EDFE48C.2000606@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 22:42:20 -0000

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
ean Turner
> Sent: Wednesday, December 07, 2011 2:11 PM
> To: mile@ietf.org
> Subject: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> What does normative/informative mean in the context of section in an
> draft/RFC?  I understand what it means in the context of a reference,
> but not so much with sections.  Are you saying implementations that
> claim conformance with this standard MUST conform to those sections?  I
> think it makes sense to explain what you mean when you say a section is
> normative/informative. Let's not assume people know what it's supposed
> to mean ;)

In this particular draft, the only non-boilerplate stuff that's not normati=
ve is the Introduction.  I would hope nobody would expect normative languag=
e in there.  Thus, I would strike Section 1.2 altogether.

Also, I would merge the Security Considerations into Section 3, but that's =
because I'm of the camp that Security Considerations should be pedagogical,=
 but not normative.  I don't know what others think or what the current IES=
G might want to see.

In general, I actually don't like this declarative normative/informative pr=
actice in documents.  We did it in DKIM, blatantly labeling some things as =
"INFORMATIVE NOTE" and "INFORMATIVE ADVICE", and I find it awkward to read.=
  Some people do like it though.  Presumably the intent is to advise the re=
ader that if somehow this document gets published where the normative stuff=
 and the informative stuff are in conflict, the normative stuff always wins=
.

My preference is to split such sections into the ones that contain the norm=
ative bits, and those that contain discussion, with the latter containing n=
o 2119 language whatsoever.  Something like:

	Section x.y.  Protocol Definition

	[blah SHOULD blah MUST blah]

	Section x.y+1.  Discussion

	[blah blah explain the protocol blah, no 2119 stuff here]

Section 3 might benefit from such a treatment.

-MSK

From sm@resistor.net  Wed Dec  7 14:58:04 2011
Return-Path: <sm@resistor.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 481B711E808B for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJVmBRoiDvpU for <mile@ietfa.amsl.com>; Wed,  7 Dec 2011 14:58:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A975211E80AC for <mile@ietf.org>; Wed,  7 Dec 2011 14:58:01 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id pB7MvtDD009684 for <mile@ietf.org>; Wed, 7 Dec 2011 14:57:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1323298680; bh=yGZtLanGv6NSH9wlXKtlMyVJG7ecHD8+Sg92f/5n4qM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=QkT83NqcNYE9RVLmOi7/5wWiU/szCRM7w+PCjiLoqenjkflqcBSoSkS2j1ipmRQYe 6pyzpprn7pRKG9feZ9PzxTe4NJxnLmnEetlDeHhLKuHKx495LssKvEnLqnI0v4hApp 8/965Jm0uhW3InVBciFhbXN+CtTh1opvgbS1maRY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1323298680; bh=yGZtLanGv6NSH9wlXKtlMyVJG7ecHD8+Sg92f/5n4qM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=fAyhLMMDAlgTK4zcplTo7i81xoQ9yMeaLEH+jUlRoRtdRs+fUPCEW+ElA8m+pORbk Zhj8nQj/Re9VJtfz2/+TYxLyG5E7iNqPY8baH0jlzTHOXpYaMsOh+CpPH39AYl4YdU k9Uf7YqT9ZWG9CSsBS3fX4uwK2Y1JdK2FHF5f9XA=
Message-Id: <6.2.5.6.2.20111207145036.0aaacfa0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 07 Dec 2011 14:57:51 -0800
To: mile@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <4EDFEAAF.4010604@ieca.com>
References: <4EDFE48C.2000606@ieca.com> <4EDFEAAF.4010604@ieca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Dec 2011 22:58:04 -0000

At 14:37 07-12-2011, Sean Turner wrote:
>says obsoletes and when wordsmithing everybody gets a cut ;)  Also, 
>references in the

I am waiting for the outcome on the following when the document is published:

   "More information on best practices in peer identity verification is
    available in [RFC6125]."

Regards,
-sm 


From kathleen.moriarty@emc.com  Thu Dec  8 06:57:23 2011
Return-Path: <kathleen.moriarty@emc.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 7E55821F8888 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 06:57:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.333
X-Spam-Level: 
X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bX+Inbce-saz for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 06:57:22 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id AA1A121F86A6 for <mile@ietf.org>; Thu,  8 Dec 2011 06:57:22 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB8EvKWU026564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Dec 2011 09:57:20 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 8 Dec 2011 09:57:05 -0500
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB8Ev02r009819; Thu, 8 Dec 2011 09:57:04 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Thu, 8 Dec 2011 09:57:02 -0500
From: <kathleen.moriarty@emc.com>
To: <turners@ieca.com>, <mile@ietf.org>
Date: Thu, 8 Dec 2011 09:57:00 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy1LT43j3KnVLgMSkqzMRMJpJISwwAhL3RA
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com>
In-Reply-To: <4EDFE48C.2000606@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 14:57:23 -0000

Thank you for the comments, Sean. =20

I'll stick to #8 and answer Murray's questions on the same topic in my next=
 message.  The rest look like they are for Brian, as editor.  The reasons b=
ehind my request to add this section is in the response to Murray's questio=
ns.

8) I'm not so sure about listing which bits are informative/normative,=20
but here's my initial thoughts on the choices:

- Isn't s1.2 normative - if somebody copied this but didn't follow our=20
classification then what would we do?

Agreed, this should be normative.  We should define what we mean as normati=
ve or informative sections here as well in response to your point below.  H=
ow about the following (please edit as you/others see fit):

A section defined as normative MUST be followed to claim conformance with t=
his standard.  The terms from [RFC2119] used within these sections MUST be =
interpreted according to their definitions, as referenced in Section 2, to =
claim conformance.  The definitions allow flexibility when the terms SHOULD=
, MAY, RECOMMENDED, and OPTIONAL are present to ensure interoperability bet=
ween implementations.  The sections declared as informative provide helpful=
 background information and considerations for implementations.

- Isn't s2 also normative because it defines the meanings of=20
MUST/SHOULD/etc?  We shouldn't let somebody decide to change the=20
meanings of these words.

Yes, agreed.

- Isn't s7.1 normative - it lists the normative references?

Yes, agreed.

What does normative/informative mean in the context of section in an=20
draft/RFC?  I understand what it means in the context of a reference,=20
but not so much with sections.  Are you saying implementations that=20
claim conformance with this standard MUST conform to those sections?  I=20
think it makes sense to explain what you mean when you say a section is=20
normative/informative. Let's not assume people know what it's supposed=20
to mean ;)

Good point, hopefully the above proposed text helps to address these concer=
ns.

Thank you!
Kathleen


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sea=
n Turner
Sent: Wednesday, December 07, 2011 5:11 PM
To: mile@ietf.org
Subject: [mile] AD review of draft-ietf-mile-rfc6046-bis

Here is my review of draft-ietf-mile-rfc6046-bis.

1) s1.1/s4: s1 contains the following:

   o The required version of TLS is upgraded to 1.1.

But, I don't see any text that says TLS 1.1 is the MUST.  There's this=20
statement in s4:

   Although TLS
   implementations typically support the older SSL protocol, a RID peer
   MUST NOT request, offer, or use any version of SSL, or any version of
   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
   prior versions of the protocol; see Appendix E of [RFC5246] for more.

To me that reads like the required TLS version is at least 1.1 but could=20
be 1.2.  So maybe the summarized change is:

   o  The minimum required version of TLS is upgraded to 1.1.

Note that this requirement is going to require changes to most TLS=20
implementations, but I bet you knew that.

2) s3 contains the following:

  When a RID message must be sent,
  the sending RID system connects to the receiving RID system and sends
  the message, optionally receiving a message in reply.

Maybe swap must for is (must usually makes people wonder if it's=20
supposed to be 2119ed and if it's not lets use another word if we can):

  When a RID message is sent,
  the sending RID system connects to the receiving RID system and sends
  the message, optionally receiving a message in reply.

3) s3: Need a pointer to s10 for the port assignment (see later comment).

  Consistent with BCP 56, RID systems listen for TCP
  connections on port 4590 (see Section 10.3).

4) s3: must or MUST?

  When a RID
  System's address changes, contact point information within the
  consortium must be updated out of band.

5) s10: Please instruct IANA to update the registry reference to point=20
to this document.  I'd rather have it point to this document than RFC=20
6046 because you're obsoleting it.

6) s12.1: Please refer to the mile version of 6045bis as opposed to the=20
individual version.

7) s6/s7.2: Is RFC6125 really informative?  I think we want people to=20
follow the rules defined therein - don't we?

8) I'm not so sure about listing which bits are informative/normative,=20
but here's my initial thoughts on the choices:

- Isn't s1.2 normative - if somebody copied this but didn't follow our=20
classification then what would we do?

- Isn't s2 also normative because it defines the meanings of=20
MUST/SHOULD/etc?  We shouldn't let somebody decide to change the=20
meanings of these words.

- Isn't s7.1 normative - it lists the normative references?

What does normative/informative mean in the context of section in an=20
draft/RFC?  I understand what it means in the context of a reference,=20
but not so much with sections.  Are you saying implementations that=20
claim conformance with this standard MUST conform to those sections?  I=20
think it makes sense to explain what you mean when you say a section is=20
normative/informative. Let's not assume people know what it's supposed=20
to mean ;)

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


From kathleen.moriarty@emc.com  Thu Dec  8 07:05:19 2011
Return-Path: <kathleen.moriarty@emc.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 54B7921F8ABD for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 07:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.35
X-Spam-Level: 
X-Spam-Status: No, score=-6.35 tagged_above=-999 required=5 tests=[AWL=0.249,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Ps4u8dhXks8 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 07:05:18 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7853F21F8ABB for <mile@ietf.org>; Thu,  8 Dec 2011 07:05:18 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB8F5F2M003140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Dec 2011 10:05:16 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 8 Dec 2011 10:04:54 -0500
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB8F4rdQ010634; Thu, 8 Dec 2011 10:04:54 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Thu, 8 Dec 2011 10:04:53 -0500
From: <kathleen.moriarty@emc.com>
To: <msk@cloudmark.com>, <mile@ietf.org>
Date: Thu, 8 Dec 2011 10:04:52 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy1LStx0ahwfLmwSs6NtPupr1+KxAAAwxeQACCUW3A=
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 15:05:19 -0000

Murray,

Thank you very much for your comments.  I'll provide more of the background=
 for my request to the list to put in the section explicitly stating whethe=
r or not sections are normative or informative.

In my initial message to the list on this topic, I stated this is what was =
done in RFC6045, per recommendation from the Security AD at the time.  This=
 advice turned out to be helpful later on, as this work (both RFC6045-bis a=
nd RFC6046-bis) is being adopted by the ITU-T.  The ITU-T is adding this do=
cument into their Cybersecurity Information Exchange (CYBEX) suite of techn=
iques and protocols (Study Group 17/Question 4).  In August, a proposal was=
 made to format the ITU-T documents, where they directly refer to the IETF =
RFCs.  In the proposal, the ITU-T document is essentially an outline that l=
ists the section headers of the IETF document.  Within the outline, there i=
s just a statement whether or not each section of the IETF document is cons=
idered normative or informative.  The interpretation at the ITU meeting (fo=
r how the drafts look now) matches our thinking - if there are RFC2119 term=
s and points essential for implementation, it is normative. =20

Having this reviewed by the WG and IETF is good to ensure the IETF agrees a=
nd can format the document as appropriate for the IETF.  The ITU may, at so=
me point, want to create a 'profile' of the referenced RFCs.  They may want=
 to change some SHOULDs to MUST or set other requirements that are still in=
teroperable with the RFC implementations.  The stricter we can be on guidan=
ce, we may have more of a chance at maintaining compatibility between imple=
mentations.  The rapporteur of the study group question is assisting, as ar=
e others to help prevent interoperability concerns.  The published version =
of this RFC-to-be will be referenced in an ITU-T recommendation.

I like your recommendations to split normative text out of the Security Con=
siderations section.  Developers may view that as an informative section be=
cause of the title and it could help avoid any ambiguity (even though the R=
FC2119 terms should say it all).  If the IETF decides to cut out the sectio=
n that states what is normative or informative, having clear delineations i=
n where there is either normative or informative text in each section will =
be very helpful.  It would be good for the ITU-T reference of this document=
 so there is no confusion in how to interpret the sections.

Thank you,
Kathleen


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mur=
ray S. Kucherawy
Sent: Wednesday, December 07, 2011 5:42 PM
To: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
ean Turner
> Sent: Wednesday, December 07, 2011 2:11 PM
> To: mile@ietf.org
> Subject: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> What does normative/informative mean in the context of section in an
> draft/RFC?  I understand what it means in the context of a reference,
> but not so much with sections.  Are you saying implementations that
> claim conformance with this standard MUST conform to those sections?  I
> think it makes sense to explain what you mean when you say a section is
> normative/informative. Let's not assume people know what it's supposed
> to mean ;)

In this particular draft, the only non-boilerplate stuff that's not normati=
ve is the Introduction.  I would hope nobody would expect normative languag=
e in there.  Thus, I would strike Section 1.2 altogether.

Also, I would merge the Security Considerations into Section 3, but that's =
because I'm of the camp that Security Considerations should be pedagogical,=
 but not normative.  I don't know what others think or what the current IES=
G might want to see.

In general, I actually don't like this declarative normative/informative pr=
actice in documents.  We did it in DKIM, blatantly labeling some things as =
"INFORMATIVE NOTE" and "INFORMATIVE ADVICE", and I find it awkward to read.=
  Some people do like it though.  Presumably the intent is to advise the re=
ader that if somehow this document gets published where the normative stuff=
 and the informative stuff are in conflict, the normative stuff always wins=
.

My preference is to split such sections into the ones that contain the norm=
ative bits, and those that contain discussion, with the latter containing n=
o 2119 language whatsoever.  Something like:

	Section x.y.  Protocol Definition

	[blah SHOULD blah MUST blah]

	Section x.y+1.  Discussion

	[blah blah explain the protocol blah, no 2119 stuff here]

Section 3 might benefit from such a treatment.

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


From tony@yaanatech.com  Thu Dec  8 11:28:36 2011
Return-Path: <tony@yaanatech.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 35B8821F8AB0 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 11:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0Pqo4dDefO9 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 11:28:35 -0800 (PST)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE7B21F8AAC for <mile@ietf.org>; Thu,  8 Dec 2011 11:28:34 -0800 (PST)
Received: from [10.5.32.57] (carl-sgc-sg-1.inter-touch.net [203.127.152.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id D23C858072; Thu,  8 Dec 2011 19:28:31 +0000 (UTC)
Message-ID: <4EE10FDD.9020601@yaanatech.com>
Date: Fri, 09 Dec 2011 03:28:29 +0800
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111130 Thunderbird/9.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <4EDFE48C.2000606@ieca.com> <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com> <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 19:28:36 -0000

Hi Kathleen,

Good description of the construct with the ITU-T.  It should
be noted that the model has significant utility on a scale beyond
just ITU-T.  Other bodies like 3GPP are also producing derivative
versions of RFCs that get driven into the global mobile
communications infrastructure.  Their "normatives" are especially
important because their specs are tightly versioned and the
capabilities get mandated by all the operators and vendors into
the global mobile communications infrastructure.

--tony

On 12/8/2011 11:04 PM, kathleen.moriarty@emc.com wrote:
> other requirements that are still interoperable with the RFC implementations.  The stricter we can be on guidance, we may have more of a chance at maintaining compatibility between implementations.  The rapporteur of the study group question is assisting, as are others to help prevent interoperability concerns.  The published version of this RFC-to-be will be referenced in an ITU-T recommendation.


From turners@ieca.com  Thu Dec  8 12:42:05 2011
Return-Path: <turners@ieca.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 84ACD11E80B9 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 12:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9uN3OrD8F2YB for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 12:42:05 -0800 (PST)
Received: from gateway02.websitewelcome.com (gateway02.websitewelcome.com [69.56.216.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1166021F8AB9 for <mile@ietf.org>; Thu,  8 Dec 2011 12:42:05 -0800 (PST)
Received: by gateway02.websitewelcome.com (Postfix, from userid 5007) id 148CCAF933F8; Thu,  8 Dec 2011 14:42:04 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway02.websitewelcome.com (Postfix) with ESMTP id 0A1D8AF933D5 for <mile@ietf.org>; Thu,  8 Dec 2011 14:42:04 -0600 (CST)
Received: from [198.180.150.234] (port=56025 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RYkn5-0001fT-94; Thu, 08 Dec 2011 14:42:03 -0600
Message-ID: <4EE1211A.90908@ieca.com>
Date: Thu, 08 Dec 2011 15:42:02 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: v234.vpn.iad.rg.net (thunderfish.local) [198.180.150.234]:56025
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 3
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 20:42:05 -0000

trimming this down to the proposed text (hoping others will jump in here 
too)

On 12/8/11 9:57 AM, kathleen.moriarty@emc.com wrote:
> Agreed, this should be normative.  We should define what we mean as normative or informative sections here as well in response to your point below.  How about the following (please edit as you/others see fit):
>
> A section defined as normative MUST be followed to claim conformance with this standard.  The terms from [RFC2119] used within these sections MUST be interpreted according to their definitions, as referenced in Section 2, to claim conformance.  The definitions allow flexibility when the terms SHOULD, MAY, RECOMMENDED, and OPTIONAL are present to ensure interoperability between implementations.  The sections declared as informative provide helpful background information and considerations for implementations.

I like the 1st and last sentences.  The middle two I think might be read 
as rephrasing/re-characterizing what's already in 2119.  And, 
SHOULD/RECOMMENDED is really MUST unless you can come up with a really 
good reason not to do it that way - it's really only MAY/OPTIONAL that 
allows implementations to do what they want.  In the olden days when 
they did interop reports they tested the MUSTs and the SHOULDs to test 
for interop.  The only other point I want to get across is that the 
definitions of the conformance terms is normative, but I wonder if I'm 
the only one worried about that.  Maybe ? :

   A section defined as normative MUST be followed to claim
   conformance with this standard.  This includes the section that
   defines the conformance words.  The sections declared as
   informative provide helpful background information
   and considerations for implementations.

spt


From sm@resistor.net  Thu Dec  8 13:29:27 2011
Return-Path: <sm@resistor.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 A527321F8669 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 13:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2t1pNBNYhIe2 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 13:29:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 76CDB21F8564 for <mile@ietf.org>; Thu,  8 Dec 2011 13:29:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id pB8LTID5024079; Thu, 8 Dec 2011 13:29:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1323379763; bh=loSXR5m53Hf9uOL6nre1jb0eLTs/miPWORd7CUTuSj4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=3o/y21ewMkxYhjNlOOiMOfqmqIYiG5n/IkdiSQgNiERmGYlxI+WLpG6inuBgKhumi uurVbqQ1cHykK8ZvwxS/TmY/DiCBKo2lNIgd3qZob32cw5uSAT6FE9N4Yt8QyKQqfo f5BUt6FI24ITeOcpKXkBVqsKgnpFVzIJuxuLZ00Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1323379763; bh=loSXR5m53Hf9uOL6nre1jb0eLTs/miPWORd7CUTuSj4=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=p+hMfrXRtJGeNhtwuc3izgCbZZD7n+VQ+zQu3C6iuUvPV/8mWleIzsHNFSEunLxpV g7ZxHdkZ79T0nmduI9dcFQWn9Qz4TDahKUzPbZ22eR5eX0qboBhyEJtXaZAnQqRniw IxqmocDCh0eb8pU54vPIz24FHWGQvapp4Fp5E16U=
Message-Id: <6.2.5.6.2.20111208125545.0b027be0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 08 Dec 2011 13:05:49 -0800
To: Sean Turner <turners@ieca.com>
From: SM <sm@resistor.net>
In-Reply-To: <4EE1211A.90908@ieca.com>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 21:29:27 -0000

Hi Sean,
At 12:42 08-12-2011, Sean Turner wrote:
>I like the 1st and last sentences.  The middle two I think might be 
>read as rephrasing/re-characterizing what's already in 2119.  And, 
>SHOULD/RECOMMENDED is really MUST unless you can come up with a 
>really good reason not to do it that way - it's really only 
>MAY/OPTIONAL that allows implementations to do what they want.  In 
>the olden days when they did interop reports they tested the MUSTs 
>and the SHOULDs to test for interop.  The only other point I want to 
>get across is that the definitions of the conformance terms is 
>normative, but I wonder if I'm the only one worried about that.  Maybe ? :
>
>   A section defined as normative MUST be followed to claim
>   conformance with this standard.  This includes the section that
>   defines the conformance words.  The sections declared as
>   informative provide helpful background information
>   and considerations for implementations.

As you mentioned above, requirement levels are about 
interoperability.  There isn't any claim of conformance or 
conformance words in a Standard-Track document.

I'll nit on this on the Last Call if there is such text about 
conformance.  For background information, see the thread about 
2119bis at http://www.ietf.org/mail-archive/web/ietf/current/msg68878.html

Regards,
-sm 


From trammell@tik.ee.ethz.ch  Thu Dec  8 13:40:33 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 0F54721F8B9B for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 13:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YsoIEb0SH5PD for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 13:40:32 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 387CD21F8B95 for <mile@ietf.org>; Thu,  8 Dec 2011 13:40:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id AEFA9D9303; Thu,  8 Dec 2011 22:40:29 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h4vwl+K3S-4c; Thu,  8 Dec 2011 22:40:29 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 4C2CDD9302; Thu,  8 Dec 2011 22:40:29 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EE1211A.90908@ieca.com>
Date: Thu, 8 Dec 2011 22:40:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <759A2E17-31E6-47D4-8393-5EE77C3EB11D@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 21:40:33 -0000

Hi, Sean, Kathleen, all,

Jumping in here on this issue specifically; will address other comments =
in a separate message.

I also think we should avoid restating what's in 2119.

Another was to approach this would be to clarify in the text (what I =
have always assumed to be) the rules about what is normative and what is =
informative in an IETF Standards Track draft:

All sections which use the key words "MUST", "MUST NOT", "REQUIRED", =
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and =
"OPTIONAL"  as defined in [RFC2119] are declared as normative unless =
specifically noted otherwise. All normative sections MUST be followed by =
implementations of this standard. Sections which are not declared as =
normative are informative; these provide helpful background information =
and considerations for implementations. Specifically, the normative =
sections in this document are Section 2 and Section 3.=20

In RFC6046, I would replace the current Section 2. Terminology with the =
above paragraph, and rename the section 2. Terminology and Normative =
Sections. Thoughts?

(The text above also assumes a move of the normative text from the =
Security Considerations section into Section 3; see a forthcoming =
message on this).

Best regards,

Brian (as author of 6046bis)

On Dec 8, 2011, at 9:42 PM, Sean Turner wrote:

> trimming this down to the proposed text (hoping others will jump in =
here too)
>=20
> On 12/8/11 9:57 AM, kathleen.moriarty@emc.com wrote:
>> Agreed, this should be normative.  We should define what we mean as =
normative or informative sections here as well in response to your point =
below.  How about the following (please edit as you/others see fit):
>>=20
>> A section defined as normative MUST be followed to claim conformance =
with this standard.  The terms from [RFC2119] used within these sections =
MUST be interpreted according to their definitions, as referenced in =
Section 2, to claim conformance.  The definitions allow flexibility when =
the terms SHOULD, MAY, RECOMMENDED, and OPTIONAL are present to ensure =
interoperability between implementations.  The sections declared as =
informative provide helpful background information and considerations =
for implementations.
>=20
> I like the 1st and last sentences.  The middle two I think might be =
read as rephrasing/re-characterizing what's already in 2119.  And, =
SHOULD/RECOMMENDED is really MUST unless you can come up with a really =
good reason not to do it that way - it's really only MAY/OPTIONAL that =
allows implementations to do what they want.  In the olden days when =
they did interop reports they tested the MUSTs and the SHOULDs to test =
for interop.  The only other point I want to get across is that the =
definitions of the conformance terms is normative, but I wonder if I'm =
the only one worried about that.  Maybe ? :
>=20
>  A section defined as normative MUST be followed to claim
>  conformance with this standard.  This includes the section that
>  defines the conformance words.  The sections declared as
>  informative provide helpful background information
>  and considerations for implementations.
>=20
> spt
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From msk@cloudmark.com  Thu Dec  8 14:57:27 2011
Return-Path: <msk@cloudmark.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 EACE321F8573 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 14:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGKB1CYOExD7 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 14:57:27 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 8653F21F8514 for <mile@ietf.org>; Thu,  8 Dec 2011 14:57:27 -0800 (PST)
Received: from spite.corp.cloudmark.com (172.22.10.72) by EXCH-HTCAS901.corp.cloudmark.com (172.22.10.73) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 8 Dec 2011 14:57:26 -0800
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Thu, 8 Dec 2011 14:57:25 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Thu, 8 Dec 2011 14:57:23 -0800
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy18Hhh7P4tiixwTv6vLDtQ6aO0mAAC6HnQ
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C154CC@EXCH-C2.corp.cloudmark.com>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net>
In-Reply-To: <6.2.5.6.2.20111208125545.0b027be0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 22:57:28 -0000

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
M
> Sent: Thursday, December 08, 2011 1:06 PM
> To: Sean Turner
> Cc: mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> >   A section defined as normative MUST be followed to claim
> >   conformance with this standard.  This includes the section that
> >   defines the conformance words.  The sections declared as
> >   informative provide helpful background information
> >   and considerations for implementations.
>=20
> As you mentioned above, requirement levels are about interoperability.
> There isn't any claim of conformance or conformance words in a
> Standard-Track document.

I think the RFC2119 already language makes it explicit: You are compliant w=
ith a specification if you adhere to 100% of the normative statements in it=
.

That said, I don't think there's anything wrong with including conformance =
requirements in a document, perhaps an appendix, especially if it's like a =
checklist of the normative stuff elsewhere in the document that an implemen=
ter could easily consult.  Sort of like a test plan.  The risk, though, is =
that the rest of the document has to match exactly the contents of that che=
cklist.

(But this is becoming a topic larger than MILE, so I'll stop now.)

From trammell@tik.ee.ethz.ch  Thu Dec  8 15:00:55 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 9563921F847C for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bj+p376k0Lo9 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:00:54 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA8E21F8477 for <mile@ietf.org>; Thu,  8 Dec 2011 15:00:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id D9CEAD9308; Fri,  9 Dec 2011 00:00:53 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1rLKY4+126qm; Fri,  9 Dec 2011 00:00:53 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 63945D9304; Fri,  9 Dec 2011 00:00:53 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EDFE48C.2000606@ieca.com>
Date: Fri, 9 Dec 2011 00:00:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 23:00:55 -0000

Hi, Sean, all,

I've made most of these changes to an eventual -04 revision of the =
document; details or questions on particular points inline, below.

Cheers,

Brian

On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:

> Here is my review of draft-ietf-mile-rfc6046-bis.
>=20
> 1) s1.1/s4: s1 contains the following:
>=20
>  o The required version of TLS is upgraded to 1.1.
>=20
> But, I don't see any text that says TLS 1.1 is the MUST.  There's this =
statement in s4:
>=20
>  Although TLS
>  implementations typically support the older SSL protocol, a RID peer
>  MUST NOT request, offer, or use any version of SSL, or any version of
>  TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
>  prior versions of the protocol; see Appendix E of [RFC5246] for more.
>=20
> To me that reads like the required TLS version is at least 1.1 but =
could be 1.2.  So maybe the summarized change is:
>=20
>  o  The minimum required version of TLS is upgraded to 1.1.
>=20
> Note that this requirement is going to require changes to most TLS =
implementations, but I bet you knew that.

This is the rationale behind 1.1; it's (much) more widely available, and =
should minimize migration effort. Indeed, we hope that implementations =
based upon a widely available TLS library would have been using 1.1 =
anyway.

> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to =
follow the rules defined therein - don't we?

I wasn't really sure the best way to handle this reference (I think SM's =
comment, earlier, addressed this point too). It seemed like a little =
much to _require_ SRV records (this gets into deployment-time =
considerations), but none of the application design points in section 3 =
of 6125 really seem to apply to RID. Given that, the intention was to =
state the requirement then point to 6125 for guidelines (informative) on =
implementing it.

Probably the right thing to do, instead, is to specify DNS-ID (as in =
6125 seciton 1.8 "identifier type"), with CN-ID as a fallback and SRV-ID =
for deployments which use SRV records, using normative language in =
6046-bis itself, and referring back to 6125 -- in that case, I think =
6125 really _would_ be informative.

> 8) I'm not so sure about listing which bits are informative/normative, =
but here's my initial thoughts on the choices:

(See the other thread on this)...

Also, I've gone ahead and cut the "updates" language out of the =
abstract.=

From trammell@tik.ee.ethz.ch  Thu Dec  8 15:13:11 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 D680321F84D4 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AufVajv8-I0A for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:13:11 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id DF71A21F84D8 for <mile@ietf.org>; Thu,  8 Dec 2011 15:13:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 84971D9303; Fri,  9 Dec 2011 00:13:09 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5656mk707QT7; Fri,  9 Dec 2011 00:13:09 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 2B4BED9302; Fri,  9 Dec 2011 00:13:09 +0100 (MET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch>
Date: Fri, 9 Dec 2011 00:13:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D4B1678-4038-47C9-BC9A-34E00F5D0F2D@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch>
To: Sean Turner <turners@ieca.com>, mile@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 23:13:12 -0000

(I forgot to explicitly note, but hope it was obvious, that the previous =
message was sent as author of 6046-bis)

On Dec 9, 2011, at 12:00 AM, Brian Trammell wrote:

> Hi, Sean, all,
>=20
> I've made most of these changes to an eventual -04 revision of the =
document; details or questions on particular points inline, below.
>=20
> Cheers,
>=20
> Brian
>=20
> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>=20
>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>=20
>> 1) s1.1/s4: s1 contains the following:
>>=20
>> o The required version of TLS is upgraded to 1.1.
>>=20
>> But, I don't see any text that says TLS 1.1 is the MUST.  There's =
this statement in s4:
>>=20
>> Although TLS
>> implementations typically support the older SSL protocol, a RID peer
>> MUST NOT request, offer, or use any version of SSL, or any version of
>> TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
>> prior versions of the protocol; see Appendix E of [RFC5246] for more.
>>=20
>> To me that reads like the required TLS version is at least 1.1 but =
could be 1.2.  So maybe the summarized change is:
>>=20
>> o  The minimum required version of TLS is upgraded to 1.1.
>>=20
>> Note that this requirement is going to require changes to most TLS =
implementations, but I bet you knew that.
>=20
> This is the rationale behind 1.1; it's (much) more widely available, =
and should minimize migration effort. Indeed, we hope that =
implementations based upon a widely available TLS library would have =
been using 1.1 anyway.
>=20
>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to =
follow the rules defined therein - don't we?
>=20
> I wasn't really sure the best way to handle this reference (I think =
SM's comment, earlier, addressed this point too). It seemed like a =
little much to _require_ SRV records (this gets into deployment-time =
considerations), but none of the application design points in section 3 =
of 6125 really seem to apply to RID. Given that, the intention was to =
state the requirement then point to 6125 for guidelines (informative) on =
implementing it.
>=20
> Probably the right thing to do, instead, is to specify DNS-ID (as in =
6125 seciton 1.8 "identifier type"), with CN-ID as a fallback and SRV-ID =
for deployments which use SRV records, using normative language in =
6046-bis itself, and referring back to 6125 -- in that case, I think =
6125 really _would_ be informative.
>=20
>> 8) I'm not so sure about listing which bits are =
informative/normative, but here's my initial thoughts on the choices:
>=20
> (See the other thread on this)...
>=20
> Also, I've gone ahead and cut the "updates" language out of the =
abstract.
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From trammell@tik.ee.ethz.ch  Thu Dec  8 15:15:34 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 2C4CE21F8541 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anbxhdIwL4xs for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 15:15:31 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 080E421F8573 for <mile@ietf.org>; Thu,  8 Dec 2011 15:15:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 5DCA2D9303; Fri,  9 Dec 2011 00:15:30 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nt5zFF-jmcaF; Fri,  9 Dec 2011 00:15:30 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id F252CD9302; Fri,  9 Dec 2011 00:15:29 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com>
Date: Fri, 9 Dec 2011 00:15:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F8CF4D1-B799-4C0B-B7BC-7C75BFD1D0C4@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com>
To: Murray S. Kucherawy <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1084)
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Dec 2011 23:15:34 -0000

Hi, Murray,

Thanks for the comments; replies inline...

On Dec 7, 2011, at 11:42 PM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Sean Turner
>> Sent: Wednesday, December 07, 2011 2:11 PM
>> To: mile@ietf.org
>> Subject: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>=20
>> What does normative/informative mean in the context of section in an
>> draft/RFC?  I understand what it means in the context of a reference,
>> but not so much with sections.  Are you saying implementations that
>> claim conformance with this standard MUST conform to those sections?  =
I
>> think it makes sense to explain what you mean when you say a section =
is
>> normative/informative. Let's not assume people know what it's =
supposed
>> to mean ;)
>=20
> In this particular draft, the only non-boilerplate stuff that's not =
normative is the Introduction.  I would hope nobody would expect =
normative language in there.  Thus, I would strike Section 1.2 =
altogether.
>=20
> Also, I would merge the Security Considerations into Section 3, but =
that's because I'm of the camp that Security Considerations should be =
pedagogical, but not normative.  I don't know what others think or what =
the current IESG might want to see.

Given the structure of 6046-bis, this makes sense; as it read, the =
"protocol specification" was essentially written as "protocol without =
security", which wasn't really the intent. I've merged these back in in =
my working copy of the next revision.

> In general, I actually don't like this declarative =
normative/informative practice in documents.  We did it in DKIM, =
blatantly labeling some things as "INFORMATIVE NOTE" and "INFORMATIVE =
ADVICE", and I find it awkward to read.  Some people do like it though.  =
Presumably the intent is to advise the reader that if somehow this =
document gets published where the normative stuff and the informative =
stuff are in conflict, the normative stuff always wins.

(I've already addressed this a bit in my earlier message on the subject, =
but...)

Indeed, this is also the limit of my personal experience with such =
language in drafts: where one part of a draft is essentially a =
restatement of the other (say, an XML schema and some text explaining =
its contents), stating which wins in case of ambiguity (whether real or =
imagined). It allows an _interoperable_ protocol even in the presence of =
imperfect language in the draft.=20

Here, though, the intent is different -- "meta-interoperability" of the =
specification with other standards processes. In that case, as long as =
the note doesn't _change_ the meaning of the normative bits of the =
document, and is phrased in such a way as to minimize confusion (as we =
seem to be converging on), I think it's worth adding.

> My preference is to split such sections into the ones that contain the =
normative bits, and those that contain discussion, with the latter =
containing no 2119 language whatsoever.  Something like:
>=20
> 	Section x.y.  Protocol Definition
>=20
> 	[blah SHOULD blah MUST blah]
>=20
> 	Section x.y+1.  Discussion
>=20
> 	[blah blah explain the protocol blah, no 2119 stuff here]

I like the approach, if only because it makes it clear that the presence =
of 2119-phrased specifications is what makes something normative, which =
I think is the de facto way sections of drafts are assumed to be =
normative or informative, anyway. However...

> Section 3 might benefit from such a treatment.

I've had a quick look, and don't really see what of section 3 could be =
pulled out into its own section, without damaging the readability of the =
specification. There's really not so much content in Section 3 that it =
deserves subsectioning, IMO.

Cheers,

Brian (as author of 6046-bis)=

From ramartin@mitre.org  Thu Dec  8 17:48:16 2011
Return-Path: <ramartin@mitre.org>
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 8D0B31F0C49 for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 17:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xEmF4Rk2XRo for <mile@ietfa.amsl.com>; Thu,  8 Dec 2011 17:48:16 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id E64611F0C43 for <mile@ietf.org>; Thu,  8 Dec 2011 17:48:15 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6ADD221B13F4; Thu,  8 Dec 2011 20:48:12 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id A61BB21B13EF; Thu,  8 Dec 2011 20:48:10 -0500 (EST)
Received: from bvb-172-31-41-245.mitre.org (129.83.31.59) by IMCCAS03.MITRE.ORG (129.83.29.80) with Microsoft SMTP Server id 14.1.339.1; Thu, 8 Dec 2011 20:48:10 -0500
Message-ID: <4EE168D2.8080803@mitre.org>
Date: Thu, 8 Dec 2011 20:48:02 -0500
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net> <F5833273385BB34F99288B3648C4F06F19C6C154CC@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C154CC@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 01:48:16 -0000

Hi everyone,

Not being as familiar with IETF's practices as most of you I'll leave 
that aspect of making sure we keep within the "IETF rails" on these 
documents for you to decide, however I do believe that we need to make 
it painfully easy for others to know what parts/portions of these 
documents they need to follow, leverage, or apply.

Given the leveraging of IETF RFCs by other groups, we need to do our 
best to make sure all of those groups correctly and completely invoke 
the right parts of the RFCs in their own work or we are going to end up 
with divergent and possibly conflicted implementations and that is not 
the goal or desire of anyone.

Some standards bodies have explicit compliance points defined in their 
specifications to help clarify for implementers the sub-sets of the work 
that need to work together and are necessary as "units" of capabilities 
so that implementers "know" what they are expected to provide.

Bob's 2cents

On 12/8/11 5:57 PM, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of SM
>> Sent: Thursday, December 08, 2011 1:06 PM
>> To: Sean Turner
>> Cc: mile@ietf.org
>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>
>>>    A section defined as normative MUST be followed to claim
>>>    conformance with this standard.  This includes the section that
>>>    defines the conformance words.  The sections declared as
>>>    informative provide helpful background information
>>>    and considerations for implementations.
>>
>> As you mentioned above, requirement levels are about interoperability.
>> There isn't any claim of conformance or conformance words in a
>> Standard-Track document.
>
> I think the RFC2119 already language makes it explicit: You are compliant with a specification if you adhere to 100% of the normative statements in it.
>
> That said, I don't think there's anything wrong with including conformance requirements in a document, perhaps an appendix, especially if it's like a checklist of the normative stuff elsewhere in the document that an implementer could easily consult.  Sort of like a test plan.  The risk, though, is that the rest of the document has to match exactly the contents of that checklist.
>
> (But this is becoming a topic larger than MILE, so I'll stop now.)
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>

From turners@ieca.com  Fri Dec  9 08:41:32 2011
Return-Path: <turners@ieca.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 A5C8821F87D9 for <mile@ietfa.amsl.com>; Fri,  9 Dec 2011 08:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bS15f0B9Yzpb for <mile@ietfa.amsl.com>; Fri,  9 Dec 2011 08:41:32 -0800 (PST)
Received: from gateway12.websitewelcome.com (gateway12.websitewelcome.com [69.93.243.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2B32C21F87FA for <mile@ietf.org>; Fri,  9 Dec 2011 08:41:32 -0800 (PST)
Received: by gateway12.websitewelcome.com (Postfix, from userid 5007) id 04BF56C6D2ADD; Fri,  9 Dec 2011 10:41:30 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway12.websitewelcome.com (Postfix) with ESMTP id EB2336C6D2AAC for <mile@ietf.org>; Fri,  9 Dec 2011 10:41:29 -0600 (CST)
Received: from [129.6.253.213] (port=57034 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZ3Vp-0005Id-IV; Fri, 09 Dec 2011 10:41:29 -0600
Message-ID: <4EE23A39.6050609@ieca.com>
Date: Fri, 09 Dec 2011 11:41:29 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch>
In-Reply-To: <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [129.6.253.213]:57034
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 3
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 16:41:32 -0000

On 12/8/11 6:00 PM, Brian Trammell wrote:
> Hi, Sean, all,
>
> I've made most of these changes to an eventual -04 revision of the document; details or questions on particular points inline, below.
>
> Cheers,
>
> Brian
>
> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>
>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>
>> 1) s1.1/s4: s1 contains the following:
>>
>>   o The required version of TLS is upgraded to 1.1.
>>
>> But, I don't see any text that says TLS 1.1 is the MUST.  There's this statement in s4:
>>
>>   Although TLS
>>   implementations typically support the older SSL protocol, a RID peer
>>   MUST NOT request, offer, or use any version of SSL, or any version of
>>   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
>>   prior versions of the protocol; see Appendix E of [RFC5246] for more.
>>
>> To me that reads like the required TLS version is at least 1.1 but could be 1.2.  So maybe the summarized change is:
>>
>>   o  The minimum required version of TLS is upgraded to 1.1.
>>
>> Note that this requirement is going to require changes to most TLS implementations, but I bet you knew that.
>
> This is the rationale behind 1.1; it's (much) more widely available, and should minimize migration effort. Indeed, we hope that implementations based upon a widely available TLS library would have been using 1.1 anyway.

Compared to 1.2, 1.1 is way more implemented.  But, if you want to pick 
1.1 then I think you need to be explicit.  That is you need a statement 
like the following: TLS 1.1 MUST be supported.

>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to follow the rules defined therein - don't we?
>
> I wasn't really sure the best way to handle this reference (I think SM's comment, earlier, addressed this point too). It seemed like a little much to _require_ SRV records (this gets into deployment-time considerations), but none of the application design points in section 3 of 6125 really seem to apply to RID. Given that, the intention was to state the requirement then point to 6125 for guidelines (informative) on implementing it.
>
> Probably the right thing to do, instead, is to specify DNS-ID (as in 6125 seciton 1.8 "identifier type"), with CN-ID as a fallback and SRV-ID for deployments which use SRV records, using normative language in 6046-bis itself, and referring back to 6125 -- in that case, I think 6125 really _would_ be informative.

okay I think that makes sense

>> 8) I'm not so sure about listing which bits are informative/normative, but here's my initial thoughts on the choices:
>
> (See the other thread on this)...
>
> Also, I've gone ahead and cut the "updates" language out of the abstract.

From david.black@emc.com  Fri Dec  9 11:02:26 2011
Return-Path: <david.black@emc.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 9026521F87E2 for <mile@ietfa.amsl.com>; Fri,  9 Dec 2011 11:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.426
X-Spam-Level: 
X-Spam-Status: No, score=-106.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrNJXF7Ihuqm for <mile@ietfa.amsl.com>; Fri,  9 Dec 2011 11:02:26 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id D2C7421F86EC for <mile@ietf.org>; Fri,  9 Dec 2011 11:02:25 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB9J2H1o019145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Dec 2011 14:02:20 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 9 Dec 2011 14:02:06 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pB9J23rZ013402; Fri, 9 Dec 2011 14:02:05 -0500
Received: from mx14a.corp.emc.com ([169.254.1.79]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Fri, 9 Dec 2011 14:02:03 -0500
From: <david.black@emc.com>
To: <turners@ieca.com>
Date: Fri, 9 Dec 2011 14:02:01 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy2kXDfLV2F6nfkT+2n5Lnsnk/WLgAEuq8w
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com>
In-Reply-To: <4EE23A39.6050609@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 19:02:26 -0000

Hi Sean,

The TLS 1.1 requirement resulted from my WGLC comment:

	... given how recently RID was originally specified (2010), would it
	be reasonable to require TLS 1.1 (2006) or a more recent version?  Requiri=
ng at least
	TLS 1.1 removes the vulnerability caused by use of an implicit IV for CBC-=
mode ciphers
	in prior versions of TLS and SSL.

I would hope that implementations are picking up "a widely available TLS li=
brary" that has TLS 1.1 support - a "MUST" requirement to implement TLS 1.1=
 does seem reasonable, IMHO.

Thanks,
--David

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
ean Turner
> Sent: Friday, December 09, 2011 11:41 AM
> To: Brian Trammell
> Cc: mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> On 12/8/11 6:00 PM, Brian Trammell wrote:
> > Hi, Sean, all,
> >
> > I've made most of these changes to an eventual -04 revision of the docu=
ment; details or questions on
> particular points inline, below.
> >
> > Cheers,
> >
> > Brian
> >
> > On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
> >
> >> Here is my review of draft-ietf-mile-rfc6046-bis.
> >>
> >> 1) s1.1/s4: s1 contains the following:
> >>
> >>   o The required version of TLS is upgraded to 1.1.
> >>
> >> But, I don't see any text that says TLS 1.1 is the MUST.  There's this=
 statement in s4:
> >>
> >>   Although TLS
> >>   implementations typically support the older SSL protocol, a RID peer
> >>   MUST NOT request, offer, or use any version of SSL, or any version o=
f
> >>   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
> >>   prior versions of the protocol; see Appendix E of [RFC5246] for more=
.
> >>
> >> To me that reads like the required TLS version is at least 1.1 but cou=
ld be 1.2.  So maybe the
> summarized change is:
> >>
> >>   o  The minimum required version of TLS is upgraded to 1.1.
> >>
> >> Note that this requirement is going to require changes to most TLS imp=
lementations, but I bet you
> knew that.
> >
> > This is the rationale behind 1.1; it's (much) more widely available, an=
d should minimize migration
> effort. Indeed, we hope that implementations based upon a widely availabl=
e TLS library would have been
> using 1.1 anyway.
>=20
> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pick
> 1.1 then I think you need to be explicit.  That is you need a statement
> like the following: TLS 1.1 MUST be supported.
>=20
> >> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to =
follow the rules defined
> therein - don't we?
> >
> > I wasn't really sure the best way to handle this reference (I think SM'=
s comment, earlier, addressed
> this point too). It seemed like a little much to _require_ SRV records (t=
his gets into deployment-time
> considerations), but none of the application design points in section 3 o=
f 6125 really seem to apply
> to RID. Given that, the intention was to state the requirement then point=
 to 6125 for guidelines
> (informative) on implementing it.
> >
> > Probably the right thing to do, instead, is to specify DNS-ID (as in 61=
25 seciton 1.8 "identifier
> type"), with CN-ID as a fallback and SRV-ID for deployments which use SRV=
 records, using normative
> language in 6046-bis itself, and referring back to 6125 -- in that case, =
I think 6125 really _would_
> be informative.
>=20
> okay I think that makes sense
>=20
> >> 8) I'm not so sure about listing which bits are informative/normative,=
 but here's my initial
> thoughts on the choices:
> >
> > (See the other thread on this)...
> >
> > Also, I've gone ahead and cut the "updates" language out of the abstrac=
t.
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From turners@ieca.com  Sun Dec 11 10:27:45 2011
Return-Path: <turners@ieca.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 89E5821F84D2 for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 10:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.441
X-Spam-Level: 
X-Spam-Status: No, score=-101.441 tagged_above=-999 required=5 tests=[AWL=-0.665, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F23kWs-3MmfL for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 10:27:43 -0800 (PST)
Received: from gateway11.websitewelcome.com (gateway11.websitewelcome.com [67.18.21.16]) by ietfa.amsl.com (Postfix) with ESMTP id 3616721F84C5 for <mile@ietf.org>; Sun, 11 Dec 2011 10:27:41 -0800 (PST)
Received: by gateway11.websitewelcome.com (Postfix, from userid 5011) id EF383738541DF; Sun, 11 Dec 2011 12:27:39 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway11.websitewelcome.com (Postfix) with ESMTP id DF419738541A6 for <mile@ietf.org>; Sun, 11 Dec 2011 12:27:39 -0600 (CST)
Received: from [71.191.6.73] (port=46191 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZo7f-0003MU-FY; Sun, 11 Dec 2011 12:27:39 -0600
Message-ID: <4EE4F61B.2000008@ieca.com>
Date: Sun, 11 Dec 2011 13:27:39 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net>
In-Reply-To: <6.2.5.6.2.20111208125545.0b027be0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-73.washdc.east.verizon.net (thunderfish.local) [71.191.6.73]:46191
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 18:27:45 -0000

On 12/8/11 4:05 PM, SM wrote:
> Hi Sean,
> At 12:42 08-12-2011, Sean Turner wrote:
>> I like the 1st and last sentences. The middle two I think might be
>> read as rephrasing/re-characterizing what's already in 2119. And,
>> SHOULD/RECOMMENDED is really MUST unless you can come up with a really
>> good reason not to do it that way - it's really only MAY/OPTIONAL that
>> allows implementations to do what they want. In the olden days when
>> they did interop reports they tested the MUSTs and the SHOULDs to test
>> for interop. The only other point I want to get across is that the
>> definitions of the conformance terms is normative, but I wonder if I'm
>> the only one worried about that. Maybe ? :
>>
>> A section defined as normative MUST be followed to claim
>> conformance with this standard. This includes the section that
>> defines the conformance words. The sections declared as
>> informative provide helpful background information
>> and considerations for implementations.
>
> As you mentioned above, requirement levels are about interoperability.
> There isn't any claim of conformance or conformance words in a
> Standard-Track document.
>
> I'll nit on this on the Last Call if there is such text about
> conformance. For background information, see the thread about 2119bis at
> http://www.ietf.org/mail-archive/web/ietf/current/msg68878.html

Yep that was a slip up.  It ought to be about interop.

spt

From turners@ieca.com  Sun Dec 11 10:36:48 2011
Return-Path: <turners@ieca.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 BDF9421F84DC for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 10:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.152
X-Spam-Level: 
X-Spam-Status: No, score=-102.152 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsptIph9kpGt for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 10:36:48 -0800 (PST)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [69.93.154.2]) by ietfa.amsl.com (Postfix) with ESMTP id 2723021F84DA for <mile@ietf.org>; Sun, 11 Dec 2011 10:36:48 -0800 (PST)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 1C2945EDE9832; Sun, 11 Dec 2011 12:36:46 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway04.websitewelcome.com (Postfix) with ESMTP id 10AB15EDE97F1 for <mile@ietf.org>; Sun, 11 Dec 2011 12:36:46 -0600 (CST)
Received: from [71.191.6.73] (port=33726 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZoGT-0006H8-HP; Sun, 11 Dec 2011 12:36:45 -0600
Message-ID: <4EE4F83D.2080603@ieca.com>
Date: Sun, 11 Dec 2011 13:36:45 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <759A2E17-31E6-47D4-8393-5EE77C3EB11D@tik.ee.ethz.ch>
In-Reply-To: <759A2E17-31E6-47D4-8393-5EE77C3EB11D@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-73.washdc.east.verizon.net (thunderfish.local) [71.191.6.73]:33726
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 4
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 18:36:48 -0000

On 12/8/11 4:40 PM, Brian Trammell wrote:
> Hi, Sean, Kathleen, all,
>
> Jumping in here on this issue specifically; will address other comments in a separate message.
>
> I also think we should avoid restating what's in 2119.
>
> Another was to approach this would be to clarify in the text (what I have always assumed to be) the rules about what is normative and what is informative in an IETF Standards Track draft:
>
> All sections which use the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"  as defined in [RFC2119] are declared as normative unless specifically noted otherwise. All normative sections MUST be followed by implementations of this standard. Sections which are not declared as normative are informative; these provide helpful background information and considerations for implementations. Specifically, the normative sections in this document are Section 2 and Section 3.
>
> In RFC6046, I would replace the current Section 2. Terminology with the above paragraph, and rename the section 2. Terminology and Normative Sections. Thoughts?

I don't think you can replace the text that's in 1.2 with this text.  I 
think this could added and it might work.  Need to add "NOT RECOMMENDED" 
after "RECOMMENDED" in the paragraph that's there and the one you're 
proposing.

I think that whatever section this appears in needs to be normative, the 
IANA considerations section needs to be normative, and the normative 
references need to be normative ;)

I think you'll need to work a normative reference to 6045-bis somewhere 
in to one of the other sections that you're calling normative.  I guess 
you should double check that any normative reference is in a section 
that is also normative.

spt

> (The text above also assumes a move of the normative text from the Security Considerations section into Section 3; see a forthcoming message on this).
>
> Best regards,
>
> Brian (as author of 6046bis)
>
> On Dec 8, 2011, at 9:42 PM, Sean Turner wrote:
>
>> trimming this down to the proposed text (hoping others will jump in here too)
>>
>> On 12/8/11 9:57 AM, kathleen.moriarty@emc.com wrote:
>>> Agreed, this should be normative.  We should define what we mean as normative or informative sections here as well in response to your point below.  How about the following (please edit as you/others see fit):
>>>
>>> A section defined as normative MUST be followed to claim conformance with this standard.  The terms from [RFC2119] used within these sections MUST be interpreted according to their definitions, as referenced in Section 2, to claim conformance.  The definitions allow flexibility when the terms SHOULD, MAY, RECOMMENDED, and OPTIONAL are present to ensure interoperability between implementations.  The sections declared as informative provide helpful background information and considerations for implementations.
>>
>> I like the 1st and last sentences.  The middle two I think might be read as rephrasing/re-characterizing what's already in 2119.  And, SHOULD/RECOMMENDED is really MUST unless you can come up with a really good reason not to do it that way - it's really only MAY/OPTIONAL that allows implementations to do what they want.  In the olden days when they did interop reports they tested the MUSTs and the SHOULDs to test for interop.  The only other point I want to get across is that the definitions of the conformance terms is normative, but I wonder if I'm the only one worried about that.  Maybe ? :
>>
>>   A section defined as normative MUST be followed to claim
>>   conformance with this standard.  This includes the section that
>>   defines the conformance words.  The sections declared as
>>   informative provide helpful background information
>>   and considerations for implementations.
>>
>> spt
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>

From turners@ieca.com  Sun Dec 11 11:23:25 2011
Return-Path: <turners@ieca.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 C833121F849B for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 11:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.158
X-Spam-Level: 
X-Spam-Status: No, score=-102.158 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XvPPyatvm-c for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 11:23:25 -0800 (PST)
Received: from gateway01.websitewelcome.com (gateway01.websitewelcome.com [67.18.80.19]) by ietfa.amsl.com (Postfix) with ESMTP id 29C9321F8495 for <mile@ietf.org>; Sun, 11 Dec 2011 11:23:25 -0800 (PST)
Received: by gateway01.websitewelcome.com (Postfix, from userid 5007) id 222D91033DE9B; Sun, 11 Dec 2011 13:23:23 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway01.websitewelcome.com (Postfix) with ESMTP id 17C621033DE7B for <mile@ietf.org>; Sun, 11 Dec 2011 13:23:23 -0600 (CST)
Received: from [71.191.6.73] (port=46696 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZoza-0000mH-IA; Sun, 11 Dec 2011 13:23:22 -0600
Message-ID: <4EE5032A.1090705@ieca.com>
Date: Sun, 11 Dec 2011 14:23:22 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: david.black@emc.com
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-73.washdc.east.verizon.net (thunderfish.local) [71.191.6.73]:46696
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 2
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 19:23:25 -0000

David,

Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I 
became an AD I tried to knock over SSL 3.0, TLS 1.0, and TLS 1.1.  The 
argument for only knocking off SSL 3.0 was that there were so few 
servers actually implementing TLS 1.1 or 1.2.  At one point there were 
only two 1.2 server and I think they were both test servers.  Now, the 
tests conducted by Opera with their TLS prober show that there are many 
more TLS 1.2 servers.  Assuming an implementation of 6046 isn't a 
generic web server, why can't we go all the way to 1.2?

spt

On 12/9/11 2:02 PM, david.black@emc.com wrote:
> Hi Sean,
>
> The TLS 1.1 requirement resulted from my WGLC comment:
>
> 	... given how recently RID was originally specified (2010), would it
> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  Requiring at least
> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV for CBC-mode ciphers
> 	in prior versions of TLS and SSL.
>
> I would hope that implementations are picking up "a widely available TLS library" that has TLS 1.1 support - a "MUST" requirement to implement TLS 1.1 does seem reasonable, IMHO.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sean Turner
>> Sent: Friday, December 09, 2011 11:41 AM
>> To: Brian Trammell
>> Cc: mile@ietf.org
>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>
>> On 12/8/11 6:00 PM, Brian Trammell wrote:
>>> Hi, Sean, all,
>>>
>>> I've made most of these changes to an eventual -04 revision of the document; details or questions on
>> particular points inline, below.
>>>
>>> Cheers,
>>>
>>> Brian
>>>
>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>>>
>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>>>
>>>> 1) s1.1/s4: s1 contains the following:
>>>>
>>>>    o The required version of TLS is upgraded to 1.1.
>>>>
>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's this statement in s4:
>>>>
>>>>    Although TLS
>>>>    implementations typically support the older SSL protocol, a RID peer
>>>>    MUST NOT request, offer, or use any version of SSL, or any version of
>>>>    TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
>>>>    prior versions of the protocol; see Appendix E of [RFC5246] for more.
>>>>
>>>> To me that reads like the required TLS version is at least 1.1 but could be 1.2.  So maybe the
>> summarized change is:
>>>>
>>>>    o  The minimum required version of TLS is upgraded to 1.1.
>>>>
>>>> Note that this requirement is going to require changes to most TLS implementations, but I bet you
>> knew that.
>>>
>>> This is the rationale behind 1.1; it's (much) more widely available, and should minimize migration
>> effort. Indeed, we hope that implementations based upon a widely available TLS library would have been
>> using 1.1 anyway.
>>
>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pick
>> 1.1 then I think you need to be explicit.  That is you need a statement
>> like the following: TLS 1.1 MUST be supported.
>>
>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to follow the rules defined
>> therein - don't we?
>>>
>>> I wasn't really sure the best way to handle this reference (I think SM's comment, earlier, addressed
>> this point too). It seemed like a little much to _require_ SRV records (this gets into deployment-time
>> considerations), but none of the application design points in section 3 of 6125 really seem to apply
>> to RID. Given that, the intention was to state the requirement then point to 6125 for guidelines
>> (informative) on implementing it.
>>>
>>> Probably the right thing to do, instead, is to specify DNS-ID (as in 6125 seciton 1.8 "identifier
>> type"), with CN-ID as a fallback and SRV-ID for deployments which use SRV records, using normative
>> language in 6046-bis itself, and referring back to 6125 -- in that case, I think 6125 really _would_
>> be informative.
>>
>> okay I think that makes sense
>>
>>>> 8) I'm not so sure about listing which bits are informative/normative, but here's my initial
>> thoughts on the choices:
>>>
>>> (See the other thread on this)...
>>>
>>> Also, I've gone ahead and cut the "updates" language out of the abstract.
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>

From kathleen.moriarty@emc.com  Sun Dec 11 11:40:44 2011
Return-Path: <kathleen.moriarty@emc.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 366FF21F84B0 for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 11:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.378
X-Spam-Level: 
X-Spam-Status: No, score=-6.378 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pb3ef9H1Ahgo for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 11:40:43 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5C69821F84B7 for <mile@ietf.org>; Sun, 11 Dec 2011 11:40:43 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBBJedlK027324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Dec 2011 14:40:40 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 11 Dec 2011 14:40:25 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBBJePVd010667; Sun, 11 Dec 2011 14:40:25 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Sun, 11 Dec 2011 14:40:25 -0500
From: <kathleen.moriarty@emc.com>
To: <turners@ieca.com>, <david.black@emc.com>
Date: Sun, 11 Dec 2011 14:40:20 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy4Omd75WYR3L5USRSlKbwuDjJrGwAAjfxQ
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E96E6@MX06A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com>
In-Reply-To: <4EE5032A.1090705@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 19:40:44 -0000

Thanks Sean & David,

My .02 - I think 1.2 sounds reasonable.

Thank you,
Kathleen =20

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sea=
n Turner
Sent: Sunday, December 11, 2011 2:23 PM
To: Black, David
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis

David,

Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I=20
became an AD I tried to knock over SSL 3.0, TLS 1.0, and TLS 1.1.  The=20
argument for only knocking off SSL 3.0 was that there were so few=20
servers actually implementing TLS 1.1 or 1.2.  At one point there were=20
only two 1.2 server and I think they were both test servers.  Now, the=20
tests conducted by Opera with their TLS prober show that there are many=20
more TLS 1.2 servers.  Assuming an implementation of 6046 isn't a=20
generic web server, why can't we go all the way to 1.2?

spt

On 12/9/11 2:02 PM, david.black@emc.com wrote:
> Hi Sean,
>
> The TLS 1.1 requirement resulted from my WGLC comment:
>
> 	... given how recently RID was originally specified (2010), would it
> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  Requi=
ring at least
> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV for CB=
C-mode ciphers
> 	in prior versions of TLS and SSL.
>
> I would hope that implementations are picking up "a widely available TLS =
library" that has TLS 1.1 support - a "MUST" requirement to implement TLS 1=
.1 does seem reasonable, IMHO.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of =
Sean Turner
>> Sent: Friday, December 09, 2011 11:41 AM
>> To: Brian Trammell
>> Cc: mile@ietf.org
>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>
>> On 12/8/11 6:00 PM, Brian Trammell wrote:
>>> Hi, Sean, all,
>>>
>>> I've made most of these changes to an eventual -04 revision of the docu=
ment; details or questions on
>> particular points inline, below.
>>>
>>> Cheers,
>>>
>>> Brian
>>>
>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>>>
>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>>>
>>>> 1) s1.1/s4: s1 contains the following:
>>>>
>>>>    o The required version of TLS is upgraded to 1.1.
>>>>
>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's this=
 statement in s4:
>>>>
>>>>    Although TLS
>>>>    implementations typically support the older SSL protocol, a RID pee=
r
>>>>    MUST NOT request, offer, or use any version of SSL, or any version =
of
>>>>    TLS prior to 1.1 [RFC4346], due to known security vulnerabilities i=
n
>>>>    prior versions of the protocol; see Appendix E of [RFC5246] for mor=
e.
>>>>
>>>> To me that reads like the required TLS version is at least 1.1 but cou=
ld be 1.2.  So maybe the
>> summarized change is:
>>>>
>>>>    o  The minimum required version of TLS is upgraded to 1.1.
>>>>
>>>> Note that this requirement is going to require changes to most TLS imp=
lementations, but I bet you
>> knew that.
>>>
>>> This is the rationale behind 1.1; it's (much) more widely available, an=
d should minimize migration
>> effort. Indeed, we hope that implementations based upon a widely availab=
le TLS library would have been
>> using 1.1 anyway.
>>
>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pick
>> 1.1 then I think you need to be explicit.  That is you need a statement
>> like the following: TLS 1.1 MUST be supported.
>>
>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to =
follow the rules defined
>> therein - don't we?
>>>
>>> I wasn't really sure the best way to handle this reference (I think SM'=
s comment, earlier, addressed
>> this point too). It seemed like a little much to _require_ SRV records (=
this gets into deployment-time
>> considerations), but none of the application design points in section 3 =
of 6125 really seem to apply
>> to RID. Given that, the intention was to state the requirement then poin=
t to 6125 for guidelines
>> (informative) on implementing it.
>>>
>>> Probably the right thing to do, instead, is to specify DNS-ID (as in 61=
25 seciton 1.8 "identifier
>> type"), with CN-ID as a fallback and SRV-ID for deployments which use SR=
V records, using normative
>> language in 6046-bis itself, and referring back to 6125 -- in that case,=
 I think 6125 really _would_
>> be informative.
>>
>> okay I think that makes sense
>>
>>>> 8) I'm not so sure about listing which bits are informative/normative,=
 but here's my initial
>> thoughts on the choices:
>>>
>>> (See the other thread on this)...
>>>
>>> Also, I've gone ahead and cut the "updates" language out of the abstrac=
t.
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile


From trammell@tik.ee.ethz.ch  Sun Dec 11 12:24:22 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 3FB0121F8467 for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 12:24:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CuRhudJik5y for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 12:24:21 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id ECFCB21F845F for <mile@ietf.org>; Sun, 11 Dec 2011 12:24:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 1EBDCD9305; Sun, 11 Dec 2011 21:24:19 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kYNv-qHnfE6D; Sun, 11 Dec 2011 21:24:18 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 96B5AD9307; Sun, 11 Dec 2011 21:24:18 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EE5032A.1090705@ieca.com>
Date: Sun, 11 Dec 2011 21:24:17 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 20:24:22 -0000

Hi, Sean, David,

On the one hand, purely from a security and correctness-of-protocol =
standpoint, I agree.=20

On the other hand, I'd hesitate to mandate =
not-yet-ubiquitously-implemented security technologies, as this may =
hinder deployment. This has been an issue in IPFIX, which mandated DTLS =
over SCTP as the default method for confidentiality and integrity in =
2008, and which has never (to my knowledge) been interop'd -- AFAIK =
everyone who needs to run IPFIX on the open Internet uses TLS1.1 over =
TCP, which has the advantage that it's _really easy_ to get running. =
Granted, DTLS over SCTP was (and still is) way less widely supported =
than TLS1.2 is, but my experiences there would lead me to reformulate =
the question as follows:

Do the advantages of knowing you _never_ have to deal with TLS1.1 =
outweigh the difficulty of implementing 6046 over TLS1.2 right now?

I don't have an _answer_ to the question. It may be yes. I think it's =
worth asking though.

Best regards,

Brian (author hat)

On Dec 11, 2011, at 8:23 PM, Sean Turner wrote:

> David,
>=20
> Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I =
became an AD I tried to knock over SSL 3.0, TLS 1.0, and TLS 1.1.  The =
argument for only knocking off SSL 3.0 was that there were so few =
servers actually implementing TLS 1.1 or 1.2.  At one point there were =
only two 1.2 server and I think they were both test servers.  Now, the =
tests conducted by Opera with their TLS prober show that there are many =
more TLS 1.2 servers.  Assuming an implementation of 6046 isn't a =
generic web server, why can't we go all the way to 1.2?
>=20
> spt
>=20
> On 12/9/11 2:02 PM, david.black@emc.com wrote:
>> Hi Sean,
>>=20
>> The TLS 1.1 requirement resulted from my WGLC comment:
>>=20
>> 	... given how recently RID was originally specified (2010), =
would it
>> 	be reasonable to require TLS 1.1 (2006) or a more recent =
version?  Requiring at least
>> 	TLS 1.1 removes the vulnerability caused by use of an implicit =
IV for CBC-mode ciphers
>> 	in prior versions of TLS and SSL.
>>=20
>> I would hope that implementations are picking up "a widely available =
TLS library" that has TLS 1.1 support - a "MUST" requirement to =
implement TLS 1.1 does seem reasonable, IMHO.
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Sean Turner
>>> Sent: Friday, December 09, 2011 11:41 AM
>>> To: Brian Trammell
>>> Cc: mile@ietf.org
>>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>>=20
>>> On 12/8/11 6:00 PM, Brian Trammell wrote:
>>>> Hi, Sean, all,
>>>>=20
>>>> I've made most of these changes to an eventual -04 revision of the =
document; details or questions on
>>> particular points inline, below.
>>>>=20
>>>> Cheers,
>>>>=20
>>>> Brian
>>>>=20
>>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>>>>=20
>>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>>>>=20
>>>>> 1) s1.1/s4: s1 contains the following:
>>>>>=20
>>>>>   o The required version of TLS is upgraded to 1.1.
>>>>>=20
>>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's =
this statement in s4:
>>>>>=20
>>>>>   Although TLS
>>>>>   implementations typically support the older SSL protocol, a RID =
peer
>>>>>   MUST NOT request, offer, or use any version of SSL, or any =
version of
>>>>>   TLS prior to 1.1 [RFC4346], due to known security =
vulnerabilities in
>>>>>   prior versions of the protocol; see Appendix E of [RFC5246] for =
more.
>>>>>=20
>>>>> To me that reads like the required TLS version is at least 1.1 but =
could be 1.2.  So maybe the
>>> summarized change is:
>>>>>=20
>>>>>   o  The minimum required version of TLS is upgraded to 1.1.
>>>>>=20
>>>>> Note that this requirement is going to require changes to most TLS =
implementations, but I bet you
>>> knew that.
>>>>=20
>>>> This is the rationale behind 1.1; it's (much) more widely =
available, and should minimize migration
>>> effort. Indeed, we hope that implementations based upon a widely =
available TLS library would have been
>>> using 1.1 anyway.
>>>=20
>>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to =
pick
>>> 1.1 then I think you need to be explicit.  That is you need a =
statement
>>> like the following: TLS 1.1 MUST be supported.
>>>=20
>>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people =
to follow the rules defined
>>> therein - don't we?
>>>>=20
>>>> I wasn't really sure the best way to handle this reference (I think =
SM's comment, earlier, addressed
>>> this point too). It seemed like a little much to _require_ SRV =
records (this gets into deployment-time
>>> considerations), but none of the application design points in =
section 3 of 6125 really seem to apply
>>> to RID. Given that, the intention was to state the requirement then =
point to 6125 for guidelines
>>> (informative) on implementing it.
>>>>=20
>>>> Probably the right thing to do, instead, is to specify DNS-ID (as =
in 6125 seciton 1.8 "identifier
>>> type"), with CN-ID as a fallback and SRV-ID for deployments which =
use SRV records, using normative
>>> language in 6046-bis itself, and referring back to 6125 -- in that =
case, I think 6125 really _would_
>>> be informative.
>>>=20
>>> okay I think that makes sense
>>>=20
>>>>> 8) I'm not so sure about listing which bits are =
informative/normative, but here's my initial
>>> thoughts on the choices:
>>>>=20
>>>> (See the other thread on this)...
>>>>=20
>>>> Also, I've gone ahead and cut the "updates" language out of the =
abstract.
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>=20
>>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From turners@ieca.com  Sun Dec 11 14:21:22 2011
Return-Path: <turners@ieca.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 E400C21F84BA for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:21:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.867
X-Spam-Level: 
X-Spam-Status: No, score=-101.867 tagged_above=-999 required=5 tests=[AWL=-0.202, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7P3fR+eBrLT2 for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:21:22 -0800 (PST)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.55.14]) by ietfa.amsl.com (Postfix) with ESMTP id 0813721F84B9 for <mile@ietf.org>; Sun, 11 Dec 2011 14:21:21 -0800 (PST)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id F06351064D370; Sun, 11 Dec 2011 16:21:18 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway05.websitewelcome.com (Postfix) with ESMTP id E5C1C1064D350 for <mile@ietf.org>; Sun, 11 Dec 2011 16:21:18 -0600 (CST)
Received: from [71.191.6.73] (port=41159 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZrlm-0001k2-3N for mile@ietf.org; Sun, 11 Dec 2011 16:21:18 -0600
Message-ID: <4EE52CDE.60306@ieca.com>
Date: Sun, 11 Dec 2011 17:21:18 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: mile@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-73.washdc.east.verizon.net (thunderfish.local) [71.191.6.73]:41159
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Subject: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 22:21:23 -0000

Here is my AD review of draft-ietf-mile-rfc6046-bis.

1) s1: I think saying this document updates while the header says 
obsoletes is going to confuse folks:

OLD:

   This specification updates [RFC6045].

NEW:

   This specification obsoletes [RFC6045].

2) s1: Instead of saying this is an updated version of RFC X maybe just 
say RID:

OLD:

  Edits reflected in this updated version of RFC6045 ...

NEW:

  Edits reflected in this updated version of RID ...

3) s1: I think you need to add a new 1st bullet for the changes:

  o This document is on standards track while [RFC6045] was 
informational, but now it's historic.

or something like that.

4) s1: In the summary about schema changes, you should note that the 
schema version was updated.

5) s1.1/s1.2: I think any section that has a normative reference and any 
section that has a 2119 keyword MUST be an normative section.  This 
includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119). 
  I'm also thinking s9 might also be normative (it's got SHOULDs in it)? 
  Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.

6) s2: expand NP or is it supposed to be SP?  Also maybe do a global 
replace on NP/network provider with SP/service provider?

7) s3: I think you should re-jiggle the sections to move the normative 
reference to 6046-bis.   Then you can delete this paragraph because it 
would be redundant with the paragraph in s1.1/s1.2.  Maybe have a 
subsection that is about transport or work it in to s3.3:

OLD:

  A RID message uses both
  the IODEF document and RID document, which is encapsulated for
  transport [RFC6046-bis].

NEW:

  A RID message uses both
  the IODEF document and RID document, which MUST be encapsulated for
  transport as specified in [RFC6046-bis].

8) s3s/4.1: I'd strike all the references to the "cloud."  If it had of 
been in 6045 I could see it staying, but it's new.  It's a great 
buzzword that is going to result is whole lotta comments about what is 
it and give me some references.  All of the times it's used it's an 
example so it's not needed because they're really not needed:
-  (Internet backbones or cloud infrastructures)
- An example of a consortium might include the cloud service providers.
- (network, cloud, etc.)
- s4.1: cloud from ClientToSP and SPToClient

9) s3: The reference for X.ridd out to be to 6046-bis - no?

10) s3: I guess this is okay, but it's a mouthful:

  One goal of RID is to prevent the need to permit access to other
  networks' equipment through the use of a standard messaging mechanism
  to enable the communication of incident handling information to other
  providers in a consortium or in neighboring networks.

11) s3: Is it worth adding an informative reference to RFC 6302 in the 
last paragraph?  It's a BCP for internet facing server logging 
recommendations?

12) s?: Is it worth adding an informative reference to 
draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG 
telechat?

13) s3.1: nit-picking:

OLD:

RID provides a standard protocol and format that is required to ensure 
inter-operability between vendors for the implementation of an incident 
messaging mechanism.

NEW:

RID provides a protocol and format that ensures inter-operability 
between vendors for the implementation of an incident messaging mechanism.

14) s3.5: Which of the message types MUST an implementation support?  Is 
it all of them or just some of them?

15) s4 3rd para: not sure how this fits in with the requirement to use 
TLS.  I assume you're talking about message security here?

16) REQUIRED: Do you want to use required or MUST?  The ITU document 
I've seen makes no mention of mapping REQUIRED (IETF) to SHALL (ITU). 
If ITU is only going to use MUST then maybe you need to change all 
instances of REQUIRED to MUST?

17) s4.1: region: r/Required/REQUIRED
           TrafficType: r/One or many./One or more.  ?
           type.Attack: r/This option should only/This option SHOULD
                          only   (all the other ones are 2119-ed)

18) s4.2: Justification - shouldn't the numbering start at 1?

19) s5.*: Need a reference for XML encryption.  You got one for XMLDsig 
but not XMLEnc.  Why are s5.1 and s5.2:

    Standards for encryption and digital signatures [RFC3275], [XMLsig]:

while s5.3-6 is:

     Standards for encryption and digital signatures [RFC3275]:

20) s5.*: Contains the following:

    The following information is required for Investigation request
    messages and is provided through:

should this be REQUIRED as opposed to required?  I'm taking that 
everything in there MUST be included in the message type?

21) s5.3: contains the following:

      Trace number - used for multiple traces of a single
      incident; must be noted.

What's the must be noted bit about? noted by whom?

22) s5.5: Contains:

    The following data is recommended if available and can be provided
    through:

Should this be RECOMMENDED?

23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194 
suggests strongly considering another hash alg.  Note that it also 
suggests pointing to RFC 6194 if you're specifying SHA-1.  THis should 
probably be in the security considerations.

24) s7: I didn't validate the schema - let me know what tool you used ;)

25) s12.1: Is the June 2008 version considered stable enough to be a 
normative reference?  It's not a W3c recommendation yet.  I think this 
would need to be called out as a DOWNREF.  You got away with it in 6045 
because that RFC was informational.  If you're going to have this 
DOWNREF is there any reason to point to v1 of XMLDsig at all?

26) s8.1: need a reference for the NTP timestamp.

27) s8.1: Could throw in a reference to [RFC3647] for certificate policy 
and certification practices in this sentence:

  The method used SHOULD adhere to any
  certificate policy and practices agreements between entities
  for the use of RID.

I guess I see there's a reference later.

28) s8.3, s.8.4, s8.5: There seems to be some duplication amongst these 
sections.  If s8.3 is about TCP then all you need is the first 
paragraph.  The other two paragraphs are repeated later (or could be 
moved to s8.2).  And, shoudn't this section then be called "Transport 
Protocol" being that TCP is about transport?  And you're not talking 
about security of TCP like TCP-AO so maybe drop the Integrity and 
Authentication?  s8.4 is about dedicated connections but then seems to 
repeat some text from s8.3.  s8.5 is about the Authentication of RID
but then it talks about TLS.  Couldn't you just have one section that 
talked about PKIs and point all the sections there?

29) s8.3: Need a reference to BEEP.

30) s8.3: Note using the RIR's PKI, which they're using for SIDR, would 
be require a pretty big change to their CP.

31) s8.3: I think approved could be removed from the following (also 
ARIN is an RIR):

OLD:

  the American Registry for Internet
  Numbers (ARIN) and the Regional Internet Registry's (RIR's) PKI
  hierarchy, vendor issued certificates, or approved issuers of
  Extended Validation (EV) Certificates.

NEW:

  the Regional Internet Registry's (RIR's) PKI
  hierarchy, vendor issued certificates, or Extended
  Validation (EV) certificate issuers.

32) s8.4: Contains the following:

  In order to address the integrity and authenticity of messages,
  transport encryption MUST be used to secure the traffic sent between
  RID systems.

Are you saying encryption is providing integrity and authentication of 
messages?  I just think this needs to be reworded.

33) s8.4: Wouldn't a better name for this section be "Dedicated 
Connections" or something like that?  It talks about having a dedicated 
connection and how good that is.  Move the 2nd and 3rd paragraphs to s8.2?

34) I went all googlie-eyed in s8.4-8.5.  So I might have more but don't 
wait on them.

35) s8.6: maybe rephrase one of the bullets:

OLD:

  o  A PKI and policy to provide authentication, integrity, and
       privacy.

NEW:

  o A PKI, certificate policy, and certification practice statement
    to provide authentication, integrity, and privacy.

36) s8.6: what does this sentence mean:

  The PKI may be a subordinate CA or in
  the CA hierarchy from the SP's consortium to establish the trust
  relationships necessary as the request is made to other connected
  networks.

If you don't need it I'd just remove it.

37) s8.7: Expand IDSs.

38) s8.7: contains:

    o  Customers MUST know

That's a pretty tall order, maybe all that's really needed is that they 
be informed:

    o  Customers MUST be informed of

same for the next bullet?

39) s9: should the availability be replaced by authentication?
         r/Authenticated encrypted/Protected
         r/of the document contents./of the document contents at the
           application layer.

OLD:

  Trust relationships are based on consortiums and established trust
  relationships of public key infrastructure (PKI) cross-certifications
  of consortiums.

NEW:

  Trust relationships are based on public key infrastructure (PKI).

If you've got a requirement in this section then it's a normative 
section.  THere's one SHOULD here.

spt

From david.black@emc.com  Sun Dec 11 14:35:59 2011
Return-Path: <david.black@emc.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 9900921F848C for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:35:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.464
X-Spam-Level: 
X-Spam-Status: No, score=-106.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBgJGOszjF-X for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:35:58 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id AD58D21F8481 for <mile@ietf.org>; Sun, 11 Dec 2011 14:35:58 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBBMZtlh011160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Dec 2011 17:35:56 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sun, 11 Dec 2011 17:35:41 -0500
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBBMZdGq032325; Sun, 11 Dec 2011 17:35:40 -0500
Received: from mx14a.corp.emc.com ([169.254.1.79]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Sun, 11 Dec 2011 17:35:39 -0500
From: <david.black@emc.com>
To: <trammell@tik.ee.ethz.ch>, <turners@ieca.com>
Date: Sun, 11 Dec 2011 17:35:38 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy4QukHW/GxQb27SF6e4vDFZE8TcwAEbuQg
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CDA5@MX14A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com> <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch>
In-Reply-To: <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 22:35:59 -0000

Brian and Sean,

I wanted to get to at least TLS 1.1 as the minimum version for its improved=
 security.  TLS 1.2 as the minimum version is fine with me, as long as it d=
oesn't cause serious implementation problems - I'll defer to Kathleen on th=
at, as she's more familiar with RID implementation efforts.

Thanks,
--David

> -----Original Message-----
> From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]
> Sent: Sunday, December 11, 2011 3:24 PM
> To: Sean Turner
> Cc: Black, David; mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> Hi, Sean, David,
>=20
> On the one hand, purely from a security and correctness-of-protocol stand=
point, I agree.
>=20
> On the other hand, I'd hesitate to mandate not-yet-ubiquitously-implement=
ed security technologies, as
> this may hinder deployment. This has been an issue in IPFIX, which mandat=
ed DTLS over SCTP as the
> default method for confidentiality and integrity in 2008, and which has n=
ever (to my knowledge) been
> interop'd -- AFAIK everyone who needs to run IPFIX on the open Internet u=
ses TLS1.1 over TCP, which
> has the advantage that it's _really easy_ to get running. Granted, DTLS o=
ver SCTP was (and still is)
> way less widely supported than TLS1.2 is, but my experiences there would =
lead me to reformulate the
> question as follows:
>=20
> Do the advantages of knowing you _never_ have to deal with TLS1.1 outweig=
h the difficulty of
> implementing 6046 over TLS1.2 right now?
>=20
> I don't have an _answer_ to the question. It may be yes. I think it's wor=
th asking though.
>=20
> Best regards,
>=20
> Brian (author hat)
>=20
> On Dec 11, 2011, at 8:23 PM, Sean Turner wrote:
>=20
> > David,
> >
> > Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I b=
ecame an AD I tried to knock
> over SSL 3.0, TLS 1.0, and TLS 1.1.  The argument for only knocking off S=
SL 3.0 was that there were so
> few servers actually implementing TLS 1.1 or 1.2.  At one point there wer=
e only two 1.2 server and I
> think they were both test servers.  Now, the tests conducted by Opera wit=
h their TLS prober show that
> there are many more TLS 1.2 servers.  Assuming an implementation of 6046 =
isn't a generic web server,
> why can't we go all the way to 1.2?
> >
> > spt
> >
> > On 12/9/11 2:02 PM, david.black@emc.com wrote:
> >> Hi Sean,
> >>
> >> The TLS 1.1 requirement resulted from my WGLC comment:
> >>
> >> 	... given how recently RID was originally specified (2010), would it
> >> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  Re=
quiring at least
> >> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV for=
 CBC-mode ciphers
> >> 	in prior versions of TLS and SSL.
> >>
> >> I would hope that implementations are picking up "a widely available T=
LS library" that has TLS 1.1
> support - a "MUST" requirement to implement TLS 1.1 does seem reasonable,=
 IMHO.
> >>
> >> Thanks,
> >> --David
> >>
> >>> -----Original Message-----
> >>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Sean Turner
> >>> Sent: Friday, December 09, 2011 11:41 AM
> >>> To: Brian Trammell
> >>> Cc: mile@ietf.org
> >>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
> >>>
> >>> On 12/8/11 6:00 PM, Brian Trammell wrote:
> >>>> Hi, Sean, all,
> >>>>
> >>>> I've made most of these changes to an eventual -04 revision of the d=
ocument; details or questions
> on
> >>> particular points inline, below.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Brian
> >>>>
> >>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
> >>>>
> >>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
> >>>>>
> >>>>> 1) s1.1/s4: s1 contains the following:
> >>>>>
> >>>>>   o The required version of TLS is upgraded to 1.1.
> >>>>>
> >>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's t=
his statement in s4:
> >>>>>
> >>>>>   Although TLS
> >>>>>   implementations typically support the older SSL protocol, a RID p=
eer
> >>>>>   MUST NOT request, offer, or use any version of SSL, or any versio=
n of
> >>>>>   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities=
 in
> >>>>>   prior versions of the protocol; see Appendix E of [RFC5246] for m=
ore.
> >>>>>
> >>>>> To me that reads like the required TLS version is at least 1.1 but =
could be 1.2.  So maybe the
> >>> summarized change is:
> >>>>>
> >>>>>   o  The minimum required version of TLS is upgraded to 1.1.
> >>>>>
> >>>>> Note that this requirement is going to require changes to most TLS =
implementations, but I bet
> you
> >>> knew that.
> >>>>
> >>>> This is the rationale behind 1.1; it's (much) more widely available,=
 and should minimize
> migration
> >>> effort. Indeed, we hope that implementations based upon a widely avai=
lable TLS library would have
> been
> >>> using 1.1 anyway.
> >>>
> >>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pi=
ck
> >>> 1.1 then I think you need to be explicit.  That is you need a stateme=
nt
> >>> like the following: TLS 1.1 MUST be supported.
> >>>
> >>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people =
to follow the rules defined
> >>> therein - don't we?
> >>>>
> >>>> I wasn't really sure the best way to handle this reference (I think =
SM's comment, earlier,
> addressed
> >>> this point too). It seemed like a little much to _require_ SRV record=
s (this gets into deployment-
> time
> >>> considerations), but none of the application design points in section=
 3 of 6125 really seem to
> apply
> >>> to RID. Given that, the intention was to state the requirement then p=
oint to 6125 for guidelines
> >>> (informative) on implementing it.
> >>>>
> >>>> Probably the right thing to do, instead, is to specify DNS-ID (as in=
 6125 seciton 1.8 "identifier
> >>> type"), with CN-ID as a fallback and SRV-ID for deployments which use=
 SRV records, using normative
> >>> language in 6046-bis itself, and referring back to 6125 -- in that ca=
se, I think 6125 really
> _would_
> >>> be informative.
> >>>
> >>> okay I think that makes sense
> >>>
> >>>>> 8) I'm not so sure about listing which bits are informative/normati=
ve, but here's my initial
> >>> thoughts on the choices:
> >>>>
> >>>> (See the other thread on this)...
> >>>>
> >>>> Also, I've gone ahead and cut the "updates" language out of the abst=
ract.
> >>> _______________________________________________
> >>> mile mailing list
> >>> mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >>
> >>
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20


From turners@ieca.com  Sun Dec 11 14:37:18 2011
Return-Path: <turners@ieca.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 D154F21F84B1 for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.163
X-Spam-Level: 
X-Spam-Status: No, score=-102.163 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vtr+dWKSKFjm for <mile@ietfa.amsl.com>; Sun, 11 Dec 2011 14:37:18 -0800 (PST)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.55.14]) by ietfa.amsl.com (Postfix) with ESMTP id 20E8321F8481 for <mile@ietf.org>; Sun, 11 Dec 2011 14:37:18 -0800 (PST)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id 404FF1066E688; Sun, 11 Dec 2011 16:37:16 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 35D061066E667 for <mile@ietf.org>; Sun, 11 Dec 2011 16:37:16 -0600 (CST)
Received: from [71.191.6.73] (port=38680 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RZs1D-0006Cj-LW for mile@ietf.org; Sun, 11 Dec 2011 16:37:16 -0600
Message-ID: <4EE5309B.5050308@ieca.com>
Date: Sun, 11 Dec 2011 17:37:15 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: mile@ietf.org
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com> <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch>
In-Reply-To: <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-6-73.washdc.east.verizon.net (thunderfish.local) [71.191.6.73]:38680
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 12
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 22:37:18 -0000

I'm curious to see what others think about this issue.

spt

On 12/11/11 3:24 PM, Brian Trammell wrote:
> Hi, Sean, David,
>
> On the one hand, purely from a security and correctness-of-protocol standpoint, I agree.
>
> On the other hand, I'd hesitate to mandate not-yet-ubiquitously-implemented security technologies, as this may hinder deployment. This has been an issue in IPFIX, which mandated DTLS over SCTP as the default method for confidentiality and integrity in 2008, and which has never (to my knowledge) been interop'd -- AFAIK everyone who needs to run IPFIX on the open Internet uses TLS1.1 over TCP, which has the advantage that it's _really easy_ to get running. Granted, DTLS over SCTP was (and still is) way less widely supported than TLS1.2 is, but my experiences there would lead me to reformulate the question as follows:
>
> Do the advantages of knowing you _never_ have to deal with TLS1.1 outweigh the difficulty of implementing 6046 over TLS1.2 right now?
>
> I don't have an _answer_ to the question. It may be yes. I think it's worth asking though.
>
> Best regards,
>
> Brian (author hat)
>
> On Dec 11, 2011, at 8:23 PM, Sean Turner wrote:
>
>> David,
>>
>> Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I became an AD I tried to knock over SSL 3.0, TLS 1.0, and TLS 1.1.  The argument for only knocking off SSL 3.0 was that there were so few servers actually implementing TLS 1.1 or 1.2.  At one point there were only two 1.2 server and I think they were both test servers.  Now, the tests conducted by Opera with their TLS prober show that there are many more TLS 1.2 servers.  Assuming an implementation of 6046 isn't a generic web server, why can't we go all the way to 1.2?
>>
>> spt
>>
>> On 12/9/11 2:02 PM, david.black@emc.com wrote:
>>> Hi Sean,
>>>
>>> The TLS 1.1 requirement resulted from my WGLC comment:
>>>
>>> 	... given how recently RID was originally specified (2010), would it
>>> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  Requiring at least
>>> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV for CBC-mode ciphers
>>> 	in prior versions of TLS and SSL.
>>>
>>> I would hope that implementations are picking up "a widely available TLS library" that has TLS 1.1 support - a "MUST" requirement to implement TLS 1.1 does seem reasonable, IMHO.
>>>
>>> Thanks,
>>> --David
>>>
>>>> -----Original Message-----
>>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sean Turner
>>>> Sent: Friday, December 09, 2011 11:41 AM
>>>> To: Brian Trammell
>>>> Cc: mile@ietf.org
>>>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>>>>
>>>> On 12/8/11 6:00 PM, Brian Trammell wrote:
>>>>> Hi, Sean, all,
>>>>>
>>>>> I've made most of these changes to an eventual -04 revision of the document; details or questions on
>>>> particular points inline, below.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Brian
>>>>>
>>>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
>>>>>
>>>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
>>>>>>
>>>>>> 1) s1.1/s4: s1 contains the following:
>>>>>>
>>>>>>    o The required version of TLS is upgraded to 1.1.
>>>>>>
>>>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's this statement in s4:
>>>>>>
>>>>>>    Although TLS
>>>>>>    implementations typically support the older SSL protocol, a RID peer
>>>>>>    MUST NOT request, offer, or use any version of SSL, or any version of
>>>>>>    TLS prior to 1.1 [RFC4346], due to known security vulnerabilities in
>>>>>>    prior versions of the protocol; see Appendix E of [RFC5246] for more.
>>>>>>
>>>>>> To me that reads like the required TLS version is at least 1.1 but could be 1.2.  So maybe the
>>>> summarized change is:
>>>>>>
>>>>>>    o  The minimum required version of TLS is upgraded to 1.1.
>>>>>>
>>>>>> Note that this requirement is going to require changes to most TLS implementations, but I bet you
>>>> knew that.
>>>>>
>>>>> This is the rationale behind 1.1; it's (much) more widely available, and should minimize migration
>>>> effort. Indeed, we hope that implementations based upon a widely available TLS library would have been
>>>> using 1.1 anyway.
>>>>
>>>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pick
>>>> 1.1 then I think you need to be explicit.  That is you need a statement
>>>> like the following: TLS 1.1 MUST be supported.
>>>>
>>>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people to follow the rules defined
>>>> therein - don't we?
>>>>>
>>>>> I wasn't really sure the best way to handle this reference (I think SM's comment, earlier, addressed
>>>> this point too). It seemed like a little much to _require_ SRV records (this gets into deployment-time
>>>> considerations), but none of the application design points in section 3 of 6125 really seem to apply
>>>> to RID. Given that, the intention was to state the requirement then point to 6125 for guidelines
>>>> (informative) on implementing it.
>>>>>
>>>>> Probably the right thing to do, instead, is to specify DNS-ID (as in 6125 seciton 1.8 "identifier
>>>> type"), with CN-ID as a fallback and SRV-ID for deployments which use SRV records, using normative
>>>> language in 6046-bis itself, and referring back to 6125 -- in that case, I think 6125 really _would_
>>>> be informative.
>>>>
>>>> okay I think that makes sense
>>>>
>>>>>> 8) I'm not so sure about listing which bits are informative/normative, but here's my initial
>>>> thoughts on the choices:
>>>>>
>>>>> (See the other thread on this)...
>>>>>
>>>>> Also, I've gone ahead and cut the "updates" language out of the abstract.
>>>> _______________________________________________
>>>> mile mailing list
>>>> mile@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mile
>>>
>>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
>

From kathleen.moriarty@emc.com  Mon Dec 12 06:20:54 2011
Return-Path: <kathleen.moriarty@emc.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 7E0D521F8B3C for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 06:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.4
X-Spam-Level: 
X-Spam-Status: No, score=-6.4 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yExPMapTDg4P for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 06:20:52 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFA621F8B14 for <mile@ietf.org>; Mon, 12 Dec 2011 06:20:52 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCEKlFh032598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 09:20:48 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 09:20:31 -0500
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCEKUmI025327; Mon, 12 Dec 2011 09:20:30 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Mon, 12 Dec 2011 09:20:31 -0500
From: <kathleen.moriarty@emc.com>
To: <david.black@emc.com>, <trammell@tik.ee.ethz.ch>, <turners@ieca.com>
Date: Mon, 12 Dec 2011 09:20:28 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy4QukHW/GxQb27SF6e4vDFZE8TcwAEbuQgAB/IqjA=
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E9741@MX06A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com> <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CDA5@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CDA5@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 14:20:54 -0000

Hello,

I thought the following might help to get opinions on whether or not to req=
uire TLS 1.2 support.

Are there any opinions from a development standpoint if it is reasonable to=
 require TLS 1.2?  Is the support in toolkits (included below) adequate eno=
ugh to require TLS 1.2 for the additional security gains?


SSL/TLS Toolkits:
The following has a comparison chart of TLS/SSL implementations (see second=
 chart, most are listed as yes for TLS 1.2 support).
http://en.wikipedia.org/wiki/Comparison_of_TLS_Implementations

Open SSL does not have official support yet (the latest official version is=
 1.0.0e), but it is there is some support starting from release version 1.0=
.1-stable from the 'snapshot' section of their webpage.  From the OpenSSL c=
hangelog, it appears additional support was added between 1.0.1 and 1.1.0:
http://www.openssl.org/news/changelog.html


RID Implementations:
In terms of RID implementations, there is one available on the Internet.  I=
 am not sure what version of IODEF/RID they are compatible with as there is=
 no date on the one from Japan.  Changes would be required to match the new=
 versions, RFC6045-bis and RFC6046-bis at a minimum.  If someone on the lis=
t is familiar with this development of IODEF/RID, could you let us know if =
it is believed to be compliant with RFC6045 and RFC6046 or later?

Japan Implementation of IODEF and RID:
http://www.ipa.go.jp/security/fy16/development/IODEF/api/index.html

I am aware of 3-4 different project where IODEF/RID is being implemented.  =
As far as I am aware, they are early enough that if TLS 1.2 is accessible, =
it could be used.
 =20
Thank you,
Kathleen

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of dav=
id.black@emc.com
Sent: Sunday, December 11, 2011 5:36 PM
To: trammell@tik.ee.ethz.ch; turners@ieca.com
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis

Brian and Sean,

I wanted to get to at least TLS 1.1 as the minimum version for its improved=
 security.  TLS 1.2 as the minimum version is fine with me, as long as it d=
oesn't cause serious implementation problems - I'll defer to Kathleen on th=
at, as she's more familiar with RID implementation efforts.

Thanks,
--David

> -----Original Message-----
> From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]
> Sent: Sunday, December 11, 2011 3:24 PM
> To: Sean Turner
> Cc: Black, David; mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> Hi, Sean, David,
>=20
> On the one hand, purely from a security and correctness-of-protocol stand=
point, I agree.
>=20
> On the other hand, I'd hesitate to mandate not-yet-ubiquitously-implement=
ed security technologies, as
> this may hinder deployment. This has been an issue in IPFIX, which mandat=
ed DTLS over SCTP as the
> default method for confidentiality and integrity in 2008, and which has n=
ever (to my knowledge) been
> interop'd -- AFAIK everyone who needs to run IPFIX on the open Internet u=
ses TLS1.1 over TCP, which
> has the advantage that it's _really easy_ to get running. Granted, DTLS o=
ver SCTP was (and still is)
> way less widely supported than TLS1.2 is, but my experiences there would =
lead me to reformulate the
> question as follows:
>=20
> Do the advantages of knowing you _never_ have to deal with TLS1.1 outweig=
h the difficulty of
> implementing 6046 over TLS1.2 right now?
>=20
> I don't have an _answer_ to the question. It may be yes. I think it's wor=
th asking though.
>=20
> Best regards,
>=20
> Brian (author hat)
>=20
> On Dec 11, 2011, at 8:23 PM, Sean Turner wrote:
>=20
> > David,
> >
> > Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I b=
ecame an AD I tried to knock
> over SSL 3.0, TLS 1.0, and TLS 1.1.  The argument for only knocking off S=
SL 3.0 was that there were so
> few servers actually implementing TLS 1.1 or 1.2.  At one point there wer=
e only two 1.2 server and I
> think they were both test servers.  Now, the tests conducted by Opera wit=
h their TLS prober show that
> there are many more TLS 1.2 servers.  Assuming an implementation of 6046 =
isn't a generic web server,
> why can't we go all the way to 1.2?
> >
> > spt
> >
> > On 12/9/11 2:02 PM, david.black@emc.com wrote:
> >> Hi Sean,
> >>
> >> The TLS 1.1 requirement resulted from my WGLC comment:
> >>
> >> 	... given how recently RID was originally specified (2010), would it
> >> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  Re=
quiring at least
> >> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV for=
 CBC-mode ciphers
> >> 	in prior versions of TLS and SSL.
> >>
> >> I would hope that implementations are picking up "a widely available T=
LS library" that has TLS 1.1
> support - a "MUST" requirement to implement TLS 1.1 does seem reasonable,=
 IMHO.
> >>
> >> Thanks,
> >> --David
> >>
> >>> -----Original Message-----
> >>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Sean Turner
> >>> Sent: Friday, December 09, 2011 11:41 AM
> >>> To: Brian Trammell
> >>> Cc: mile@ietf.org
> >>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
> >>>
> >>> On 12/8/11 6:00 PM, Brian Trammell wrote:
> >>>> Hi, Sean, all,
> >>>>
> >>>> I've made most of these changes to an eventual -04 revision of the d=
ocument; details or questions
> on
> >>> particular points inline, below.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Brian
> >>>>
> >>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
> >>>>
> >>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
> >>>>>
> >>>>> 1) s1.1/s4: s1 contains the following:
> >>>>>
> >>>>>   o The required version of TLS is upgraded to 1.1.
> >>>>>
> >>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's t=
his statement in s4:
> >>>>>
> >>>>>   Although TLS
> >>>>>   implementations typically support the older SSL protocol, a RID p=
eer
> >>>>>   MUST NOT request, offer, or use any version of SSL, or any versio=
n of
> >>>>>   TLS prior to 1.1 [RFC4346], due to known security vulnerabilities=
 in
> >>>>>   prior versions of the protocol; see Appendix E of [RFC5246] for m=
ore.
> >>>>>
> >>>>> To me that reads like the required TLS version is at least 1.1 but =
could be 1.2.  So maybe the
> >>> summarized change is:
> >>>>>
> >>>>>   o  The minimum required version of TLS is upgraded to 1.1.
> >>>>>
> >>>>> Note that this requirement is going to require changes to most TLS =
implementations, but I bet
> you
> >>> knew that.
> >>>>
> >>>> This is the rationale behind 1.1; it's (much) more widely available,=
 and should minimize
> migration
> >>> effort. Indeed, we hope that implementations based upon a widely avai=
lable TLS library would have
> been
> >>> using 1.1 anyway.
> >>>
> >>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to pi=
ck
> >>> 1.1 then I think you need to be explicit.  That is you need a stateme=
nt
> >>> like the following: TLS 1.1 MUST be supported.
> >>>
> >>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want people =
to follow the rules defined
> >>> therein - don't we?
> >>>>
> >>>> I wasn't really sure the best way to handle this reference (I think =
SM's comment, earlier,
> addressed
> >>> this point too). It seemed like a little much to _require_ SRV record=
s (this gets into deployment-
> time
> >>> considerations), but none of the application design points in section=
 3 of 6125 really seem to
> apply
> >>> to RID. Given that, the intention was to state the requirement then p=
oint to 6125 for guidelines
> >>> (informative) on implementing it.
> >>>>
> >>>> Probably the right thing to do, instead, is to specify DNS-ID (as in=
 6125 seciton 1.8 "identifier
> >>> type"), with CN-ID as a fallback and SRV-ID for deployments which use=
 SRV records, using normative
> >>> language in 6046-bis itself, and referring back to 6125 -- in that ca=
se, I think 6125 really
> _would_
> >>> be informative.
> >>>
> >>> okay I think that makes sense
> >>>
> >>>>> 8) I'm not so sure about listing which bits are informative/normati=
ve, but here's my initial
> >>> thoughts on the choices:
> >>>>
> >>>> (See the other thread on this)...
> >>>>
> >>>> Also, I've gone ahead and cut the "updates" language out of the abst=
ract.
> >>> _______________________________________________
> >>> mile mailing list
> >>> mile@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/mile
> >>
> >>
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20

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


From trammell@tik.ee.ethz.ch  Mon Dec 12 07:15:56 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 19B4321F8B64 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 07:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KfsmCFnPSJe for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 07:15:55 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 459DF21F8B5B for <mile@ietf.org>; Mon, 12 Dec 2011 07:15:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 1B4D3D9309; Mon, 12 Dec 2011 16:15:53 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dL+d3EhBalHG; Mon, 12 Dec 2011 16:15:52 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id BA65ED9305; Mon, 12 Dec 2011 16:15:52 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EE4F61B.2000008@ieca.com>
Date: Mon, 12 Dec 2011 16:15:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC41A9FB-BEE8-4E5A-AABC-12F6F09F1A7C@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net> <4EE4F61B.2000008@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: [mile] Language on normative vs informative sections (was Re: AD review of draft-ietf-mile-rfc6046-bis)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 15:15:56 -0000

Hi, Sean, all,

Would the following suggested text address the concerns about pointing =
out normative vs. informative sections, while avoiding language about =
conformance?

All sections which use the key words "MUST", "MUST NOT", "REQUIRED", =
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and =
"OPTIONAL" as defined in [RFC2119] are declared as normative, unless =
specifically noted otherwise. All normative sections MUST be followed by =
implementations of this standard. Sections which are not declared as =
normative are informative; these provide helpful background information =
and considerations for implementations. Specifically, the normative =
sections in this document are Section 2 and Section 3.=20

Thanks, best regards,

Brian (author hat)



On Dec 11, 2011, at 7:27 PM, Sean Turner wrote:

> On 12/8/11 4:05 PM, SM wrote:
>> Hi Sean,
>> At 12:42 08-12-2011, Sean Turner wrote:
>>> I like the 1st and last sentences. The middle two I think might be
>>> read as rephrasing/re-characterizing what's already in 2119. And,
>>> SHOULD/RECOMMENDED is really MUST unless you can come up with a =
really
>>> good reason not to do it that way - it's really only MAY/OPTIONAL =
that
>>> allows implementations to do what they want. In the olden days when
>>> they did interop reports they tested the MUSTs and the SHOULDs to =
test
>>> for interop. The only other point I want to get across is that the
>>> definitions of the conformance terms is normative, but I wonder if =
I'm
>>> the only one worried about that. Maybe ? :
>>>=20
>>> A section defined as normative MUST be followed to claim
>>> conformance with this standard. This includes the section that
>>> defines the conformance words. The sections declared as
>>> informative provide helpful background information
>>> and considerations for implementations.
>>=20
>> As you mentioned above, requirement levels are about =
interoperability.
>> There isn't any claim of conformance or conformance words in a
>> Standard-Track document.
>>=20
>> I'll nit on this on the Last Call if there is such text about
>> conformance. For background information, see the thread about 2119bis =
at
>> http://www.ietf.org/mail-archive/web/ietf/current/msg68878.html
>=20
> Yep that was a slip up.  It ought to be about interop.
>=20
> spt
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From david.black@emc.com  Mon Dec 12 07:20:46 2011
Return-Path: <david.black@emc.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 3E46021F8B64 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 07:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.489
X-Spam-Level: 
X-Spam-Status: No, score=-106.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIGtG+jIIOl5 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 07:20:45 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 305EA21F8B63 for <mile@ietf.org>; Mon, 12 Dec 2011 07:20:44 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCFKfNV000979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 10:20:43 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 10:20:25 -0500
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCFKNRk021780; Mon, 12 Dec 2011 10:20:24 -0500
Received: from mx14a.corp.emc.com ([169.254.1.79]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Mon, 12 Dec 2011 10:20:23 -0500
From: <david.black@emc.com>
To: <turners@ieca.com>
Date: Mon, 12 Dec 2011 10:20:20 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy4QukHW/GxQb27SF6e4vDFZE8TcwAEbuQgACLO7XA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CE9D@MX14A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <E75FC78B-34DB-454C-94AB-F6A3A7AD63E7@tik.ee.ethz.ch> <4EE23A39.6050609@ieca.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CC5D@MX14A.corp.emc.com> <4EE5032A.1090705@ieca.com> <6828C5B0-DEAA-4BF5-9FB3-FA75AFC0D1FD@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CDA5@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A000CDA5@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 15:20:46 -0000

Hi Sean,

Here are some more details and thoughts ...

The improved security from TLS 1.0 to TLS 1.1 included removing "the vulner=
ability caused by use of an implicit IV for CBC-mode ciphers in prior versi=
ons of TLS and SSL."  That was a visible security improvement - in contrast=
, a quick scan of the TLS 1.2 change summary in RFC 5246 didn't turn up any=
 security improvements that rise to that level, although there are a lot of=
 functionality additions and design improvements.

One possible reason to go to TLS 1.2 is that TLS 1.1 is still using an MD5/=
SHA-1 hash pair internally for its PRF and handshake digital signatures.  T=
hat's a fixed algorithm pair, as there's no crypto agility for either of th=
ose functions in TLS 1.1, whereas TLS 1.2 is crypto-agile in both areas. Ne=
edless to say, those two hash functions don't have long lives ahead of them=
 ;-).  OTOH, the PRF is not a concern, as both MD5 and SHA-1 are fine bit-m=
ixers, and the handshake signatures shouldn't be a current concern because =
for a collision to cause problems there, the same collision has to collide =
for *both* MD5 and SHA-1 (not impossible, but definitely more difficult tha=
n colliding for just one of the hashes)

On balance, I'd be inclined to leave movement away from SHA-1 (currently ha=
s the stronger collision resistance of the two secure hashes) to other cont=
exts/forums, but it could be encouraged here.  Hence, I'd be happy with:

	- MUST NOT use TLS 1.0 or any version of SSL
	- MUST implement TLS 1.1
	- SHOULD implement TLS 1.2
	- SHOULD prefer TLS 1.2 to TLS 1.1 when there is a choice

Thanks,
--David


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of d=
avid.black@emc.com
> Sent: Sunday, December 11, 2011 5:36 PM
> To: trammell@tik.ee.ethz.ch; turners@ieca.com
> Cc: mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20
> Brian and Sean,
>=20
> I wanted to get to at least TLS 1.1 as the minimum version for its improv=
ed security.  TLS 1.2 as the
> minimum version is fine with me, as long as it doesn't cause serious impl=
ementation problems - I'll
> defer to Kathleen on that, as she's more familiar with RID implementation=
 efforts.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]
> > Sent: Sunday, December 11, 2011 3:24 PM
> > To: Sean Turner
> > Cc: Black, David; mile@ietf.org
> > Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
> >
> > Hi, Sean, David,
> >
> > On the one hand, purely from a security and correctness-of-protocol sta=
ndpoint, I agree.
> >
> > On the other hand, I'd hesitate to mandate not-yet-ubiquitously-impleme=
nted security technologies,
> as
> > this may hinder deployment. This has been an issue in IPFIX, which mand=
ated DTLS over SCTP as the
> > default method for confidentiality and integrity in 2008, and which has=
 never (to my knowledge) been
> > interop'd -- AFAIK everyone who needs to run IPFIX on the open Internet=
 uses TLS1.1 over TCP, which
> > has the advantage that it's _really easy_ to get running. Granted, DTLS=
 over SCTP was (and still is)
> > way less widely supported than TLS1.2 is, but my experiences there woul=
d lead me to reformulate the
> > question as follows:
> >
> > Do the advantages of knowing you _never_ have to deal with TLS1.1 outwe=
igh the difficulty of
> > implementing 6046 over TLS1.2 right now?
> >
> > I don't have an _answer_ to the question. It may be yes. I think it's w=
orth asking though.
> >
> > Best regards,
> >
> > Brian (author hat)
> >
> > On Dec 11, 2011, at 8:23 PM, Sean Turner wrote:
> >
> > > David,
> > >
> > > Hi.  I'm thinking that maybe we should require 1.2 not 1.1.  Before I=
 became an AD I tried to
> knock
> > over SSL 3.0, TLS 1.0, and TLS 1.1.  The argument for only knocking off=
 SSL 3.0 was that there were
> so
> > few servers actually implementing TLS 1.1 or 1.2.  At one point there w=
ere only two 1.2 server and I
> > think they were both test servers.  Now, the tests conducted by Opera w=
ith their TLS prober show
> that
> > there are many more TLS 1.2 servers.  Assuming an implementation of 604=
6 isn't a generic web server,
> > why can't we go all the way to 1.2?
> > >
> > > spt
> > >
> > > On 12/9/11 2:02 PM, david.black@emc.com wrote:
> > >> Hi Sean,
> > >>
> > >> The TLS 1.1 requirement resulted from my WGLC comment:
> > >>
> > >> 	... given how recently RID was originally specified (2010), would i=
t
> > >> 	be reasonable to require TLS 1.1 (2006) or a more recent version?  =
Requiring at least
> > >> 	TLS 1.1 removes the vulnerability caused by use of an implicit IV f=
or CBC-mode ciphers
> > >> 	in prior versions of TLS and SSL.
> > >>
> > >> I would hope that implementations are picking up "a widely available=
 TLS library" that has TLS
> 1.1
> > support - a "MUST" requirement to implement TLS 1.1 does seem reasonabl=
e, IMHO.
> > >>
> > >> Thanks,
> > >> --David
> > >>
> > >>> -----Original Message-----
> > >>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behal=
f Of Sean Turner
> > >>> Sent: Friday, December 09, 2011 11:41 AM
> > >>> To: Brian Trammell
> > >>> Cc: mile@ietf.org
> > >>> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
> > >>>
> > >>> On 12/8/11 6:00 PM, Brian Trammell wrote:
> > >>>> Hi, Sean, all,
> > >>>>
> > >>>> I've made most of these changes to an eventual -04 revision of the=
 document; details or
> questions
> > on
> > >>> particular points inline, below.
> > >>>>
> > >>>> Cheers,
> > >>>>
> > >>>> Brian
> > >>>>
> > >>>> On Dec 7, 2011, at 11:11 PM, Sean Turner wrote:
> > >>>>
> > >>>>> Here is my review of draft-ietf-mile-rfc6046-bis.
> > >>>>>
> > >>>>> 1) s1.1/s4: s1 contains the following:
> > >>>>>
> > >>>>>   o The required version of TLS is upgraded to 1.1.
> > >>>>>
> > >>>>> But, I don't see any text that says TLS 1.1 is the MUST.  There's=
 this statement in s4:
> > >>>>>
> > >>>>>   Although TLS
> > >>>>>   implementations typically support the older SSL protocol, a RID=
 peer
> > >>>>>   MUST NOT request, offer, or use any version of SSL, or any vers=
ion of
> > >>>>>   TLS prior to 1.1 [RFC4346], due to known security vulnerabiliti=
es in
> > >>>>>   prior versions of the protocol; see Appendix E of [RFC5246] for=
 more.
> > >>>>>
> > >>>>> To me that reads like the required TLS version is at least 1.1 bu=
t could be 1.2.  So maybe the
> > >>> summarized change is:
> > >>>>>
> > >>>>>   o  The minimum required version of TLS is upgraded to 1.1.
> > >>>>>
> > >>>>> Note that this requirement is going to require changes to most TL=
S implementations, but I bet
> > you
> > >>> knew that.
> > >>>>
> > >>>> This is the rationale behind 1.1; it's (much) more widely availabl=
e, and should minimize
> > migration
> > >>> effort. Indeed, we hope that implementations based upon a widely av=
ailable TLS library would
> have
> > been
> > >>> using 1.1 anyway.
> > >>>
> > >>> Compared to 1.2, 1.1 is way more implemented.  But, if you want to =
pick
> > >>> 1.1 then I think you need to be explicit.  That is you need a state=
ment
> > >>> like the following: TLS 1.1 MUST be supported.
> > >>>
> > >>>>> 7) s6/s7.2: Is RFC6125 really informative?  I think we want peopl=
e to follow the rules defined
> > >>> therein - don't we?
> > >>>>
> > >>>> I wasn't really sure the best way to handle this reference (I thin=
k SM's comment, earlier,
> > addressed
> > >>> this point too). It seemed like a little much to _require_ SRV reco=
rds (this gets into
> deployment-
> > time
> > >>> considerations), but none of the application design points in secti=
on 3 of 6125 really seem to
> > apply
> > >>> to RID. Given that, the intention was to state the requirement then=
 point to 6125 for guidelines
> > >>> (informative) on implementing it.
> > >>>>
> > >>>> Probably the right thing to do, instead, is to specify DNS-ID (as =
in 6125 seciton 1.8
> "identifier
> > >>> type"), with CN-ID as a fallback and SRV-ID for deployments which u=
se SRV records, using
> normative
> > >>> language in 6046-bis itself, and referring back to 6125 -- in that =
case, I think 6125 really
> > _would_
> > >>> be informative.
> > >>>
> > >>> okay I think that makes sense
> > >>>
> > >>>>> 8) I'm not so sure about listing which bits are informative/norma=
tive, but here's my initial
> > >>> thoughts on the choices:
> > >>>>
> > >>>> (See the other thread on this)...
> > >>>>
> > >>>> Also, I've gone ahead and cut the "updates" language out of the ab=
stract.
> > >>> _______________________________________________
> > >>> mile mailing list
> > >>> mile@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/mile
> > >>
> > >>
> > > _______________________________________________
> > > mile mailing list
> > > mile@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mile
> >
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From trammell@tik.ee.ethz.ch  Mon Dec 12 08:59:29 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 71C7221F8AF4; Mon, 12 Dec 2011 08:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptc3+W7fcc62; Mon, 12 Dec 2011 08:59:28 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 8943C21F8AAF; Mon, 12 Dec 2011 08:59:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C7ED3D9309; Mon, 12 Dec 2011 17:59:27 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id b9+JpEABrNbW; Mon, 12 Dec 2011 17:59:27 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 95D81D9305; Mon, 12 Dec 2011 17:59:27 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EE50109.2030201@gmx.de>
Date: Mon, 12 Dec 2011 17:59:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D7916C1-93EB-4660-B4AB-D6605CBB09E0@tik.ee.ethz.ch>
References: <4EE50109.2030201@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>, mile@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: draft-ietf-mile-rfc6046-bis@tools.ietf.org, The IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [mile] APPSDIR review of draft-ietf-mile-rfc6046-bis-03
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 16:59:29 -0000

Hi, Julian,

Thank you for the detailed review; answers to questions which can be =
simply addressed in the document will be incorporated into the next =
revision.=20

I'm copying comments on specific points for discussion to mile and =
apps-area, inline.

Best regards,

Brian

On Dec 11, 2011, at 8:14 PM, Julian Reschke wrote:

> What I'm missing here are a few things that would probably make it =
easier to understand what's actually required:
>=20
> 1) Does a RID endpoint need to implement all REQUIRED HTTP/1.1 =
features? For instance, does it need to understand Expect: 100-continue, =
and does it have to support GET and HEAD on "/"? Are there requirements =
for request URIs other than "/"?

As (1) the probable implementation path in most cases is to build a RID =
implementation atop an existing web server and (2) there is probably =
more to lose than to gain in attempting to define a coherent subset of =
the REQUIRED features, I would tend to think that all HTTP/1.1 REQUIRED =
features are REQUIRED for RID transport over HTTP/1.1. This goes for =
proper handling of potentially cached content and "proxy-friendliness", =
as well as handling of 100 Continue... (Is there a list of REQUIRED =
features in 1.1? seems like this would be a useful thing to have in a =
BCP56-bis...)

On specific points:

I presume that any access to non / URIs should return 404, since those =
resources in essence do not exist on the server; this should be noted.

The question as to what to do in case of GET / and HEAD / should be =
addressed, and I'm not sure what the right thing to do here is. =
Logically, this should be the same as what happens as POST with an empty =
body, which is also presently undefined. Allowing a text/html reply =
explaining that this is a RID system and what that is might be the most =
"user-friendly" solution (for people who aren't actually users of the =
system) but having the semantics and the media type of the reply depend =
on the method seems a little wrong, too. I presume a 405 Method Not =
Allowed violates a MUST in 2616? In any case, it would probably be =
difficult to implement based on many/most existing web servers.

> Nits:
>=20
>   RID systems SHOULD NOT use TCP port 443 (the standard port for HTTP
>   over TLS/SSL) for RID messages; this avoids posting RID messages to
>   web servers that may not handle RID messages correctly.
>=20
> Actually, it does not, because a web server may run on the RID port =
(4590) as well. If there's a security concern with the protocol with =
respect to generic web servers, it should be pointed out (and =
potentially fixed).

There's no security problem (at least, accidental connection to the =
wrong server should be prevented by proper verification of =
certificates). The intention here is simply that a RID System be easily =
distinguishable from a "normal" web server.



From trammell@tik.ee.ethz.ch  Mon Dec 12 09:14:04 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 140E521F8B75 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 09:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1Kwv-WG-uyI for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 09:14:03 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 70B9F21F8B73 for <mile@ietf.org>; Mon, 12 Dec 2011 09:14:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C62BED9307 for <mile@ietf.org>; Mon, 12 Dec 2011 18:14:02 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HjhdPGBw2TIS for <mile@ietf.org>; Mon, 12 Dec 2011 18:14:02 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 9D996D9305 for <mile@ietf.org>; Mon, 12 Dec 2011 18:14:02 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Dec 2011 18:14:02 +0100
Message-Id: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch>
To: mile@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [mile] Binding/containment of RID and IODEF in 6046
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 17:14:04 -0000

Greetings, all,

In answering a question from the appsdir review on 6046, I've discovered =
what might an issue with the transport of RID that may have an impact on =
6045, as well.

The question is "what is the media type of a RID message"; the (obvious =
enough that I didn't notice it was missing from 6046) answer is =
"text/xml".

However, as defined right now that's not the case. What is sent instead =
is multiple XML bodies: the <RID> element followed by the =
<IODEF-Document> element followed by an XML signature. The extension of =
RID as foreseen in the GRC charter item would add other elements to =
this.

Should this be handled in the context of RFC6045, or RFC6046? In the =
former case, we would allow the <RID> element to contain arbitrary =
elements, as I think was alluded to in an earlier either directly or =
through a <Content> element, so that <RID> becomes the root element of =
all RID messages, something like:

<RID>
 ... other RID elements
 <Content>
  <IODEF-Document/>
 </Content>
</RID>
=20
In the latter, RFC6046 would have to define a new schema, containing RID =
and IODEF as well as other information which could be annotated by RID =
in the future, like:

<RID-Transport-Envelope>
  <RID/>
  <IODEF-Document/>
</RID-TransportEnvelope>

If we expect RID documents to coexist with the data they carry anywhere =
_except on the wire_, it probably makes sense to update 6045 to use the =
former. In both of these cases, it's kind of painful to express the type =
of "extensible" containment we need for future GRC-like cases using xsd, =
so I don't think there's an ease of implementation argument either way. =
IIRC, this is one of the reasons the RID element didn't contain its =
content in the first place... but if we want a text/xml body with one =
root element -- which I think we do -- clearly we need some container.

Thoughts?

Best regards,

Brian (author hat)=

From kathleen.moriarty@emc.com  Mon Dec 12 09:22:46 2011
Return-Path: <kathleen.moriarty@emc.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 1719D21F8BA0 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 09:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.409
X-Spam-Level: 
X-Spam-Status: No, score=-6.409 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52dp1XyyZlhk for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 09:22:45 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 57EE321F8AF4 for <mile@ietf.org>; Mon, 12 Dec 2011 09:22:45 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCHMgN3010915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 12:22:44 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 12:22:25 -0500
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCHMOLv007308; Mon, 12 Dec 2011 12:22:25 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Mon, 12 Dec 2011 12:22:21 -0500
From: <kathleen.moriarty@emc.com>
To: <trammell@tik.ee.ethz.ch>, <mile@ietf.org>
Date: Mon, 12 Dec 2011 12:22:22 -0500
Thread-Topic: [mile] Binding/containment of RID and IODEF in 6046
Thread-Index: Acy48ZbFL1M/Svx4RkuHSE8THgbwvQAADzIA
Message-ID: <AE31510960917D478171C79369B660FA0E1A6E9800@MX06A.corp.emc.com>
References: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch>
In-Reply-To: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 17:22:46 -0000

Hi Brian,

The solution proposed below came up in Paul Cichonski's review where he sug=
gested we go back to IODEF being encapsulated in RID as an optional element=
.  I think that is the cleanest option.  I agree that it makes sense to hav=
e this, but gave a response based on prior WG decisions.  I did ask for opi=
nions, but didn't get any.  This was right at the end of WGLC.  I think it =
is messy to have another layer at transport.  It does change implementation=
s and that was one of the reasons cited for not making the change.

FYI- The GRC extension would not add to this as it would not be used with I=
ODEF documents or RID.  It is intended as a generalization of RID to be use=
d with other XML schemas for their transport.  Handling it in the same way =
makes sense.

Can we have some more opinions?

Thanks,
Kathleen (I think as an editor)


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Bri=
an Trammell
Sent: Monday, December 12, 2011 12:14 PM
To: mile@ietf.org
Subject: [mile] Binding/containment of RID and IODEF in 6046

Greetings, all,

In answering a question from the appsdir review on 6046, I've discovered wh=
at might an issue with the transport of RID that may have an impact on 6045=
, as well.

The question is "what is the media type of a RID message"; the (obvious eno=
ugh that I didn't notice it was missing from 6046) answer is "text/xml".

However, as defined right now that's not the case. What is sent instead is =
multiple XML bodies: the <RID> element followed by the <IODEF-Document> ele=
ment followed by an XML signature. The extension of RID as foreseen in the =
GRC charter item would add other elements to this.

Should this be handled in the context of RFC6045, or RFC6046? In the former=
 case, we would allow the <RID> element to contain arbitrary elements, as I=
 think was alluded to in an earlier either directly or through a <Content> =
element, so that <RID> becomes the root element of all RID messages, someth=
ing like:

<RID>
 ... other RID elements
 <Content>
  <IODEF-Document/>
 </Content>
</RID>
=20
In the latter, RFC6046 would have to define a new schema, containing RID an=
d IODEF as well as other information which could be annotated by RID in the=
 future, like:

<RID-Transport-Envelope>
  <RID/>
  <IODEF-Document/>
</RID-TransportEnvelope>

If we expect RID documents to coexist with the data they carry anywhere _ex=
cept on the wire_, it probably makes sense to update 6045 to use the former=
. In both of these cases, it's kind of painful to express the type of "exte=
nsible" containment we need for future GRC-like cases using xsd, so I don't=
 think there's an ease of implementation argument either way. IIRC, this is=
 one of the reasons the RID element didn't contain its content in the first=
 place... but if we want a text/xml body with one root element -- which I t=
hink we do -- clearly we need some container.

Thoughts?

Best regards,

Brian (author hat)
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile


From sm@resistor.net  Mon Dec 12 11:31:50 2011
Return-Path: <sm@resistor.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 27F5721F8AFF for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 11:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0b9tt4BItCNm for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 11:31:48 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2825C21F8783 for <mile@ietf.org>; Mon, 12 Dec 2011 11:31:48 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) by mx.elandsys.com (8.14.4/8.14.5) with ESMTP id pBCJVe3E001185; Mon, 12 Dec 2011 11:31:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1323718306; bh=oGV64ziWjEC7s7PHCjeOqfZgOLOBZxCmGu2mtieIJsM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=J/OU/IUbUWZdNvxgV3oo2A2+21KJgQkHYFrAr9AdQuM3c0XGJlqWJGzNodT9wZUvv ohOwl7YGb2p0HUztIchdmF26rcqLGOUkGqcetnl273Fo5uw2eOaRSfQd0m2mc//mmj uWNc7L/R4vobywAWi6I9/1IeRv8+PzAIQO1tpE8U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1323718306; bh=oGV64ziWjEC7s7PHCjeOqfZgOLOBZxCmGu2mtieIJsM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=kFoC2kHHqqzv+B+Fdet4tW0Fym7ebWNZ93hB24J/MykrmSzkulbL6/QXGSn2untrr zvNlOD+elK71FY/2wuKVlhFoHeUqCkiwQWrniaXeFTnLveQ8p2/fyBE4FDc/ujnTHU SBDp55i3VRNUPvmRQkS1qy6hu4gGihJGjg8wFFtA=
Message-Id: <6.2.5.6.2.20111212103840.0a305bd8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 12 Dec 2011 11:30:10 -0800
To: Brian Trammell <trammell@tik.ee.ethz.ch>
From: SM <sm@resistor.net>
In-Reply-To: <DC41A9FB-BEE8-4E5A-AABC-12F6F09F1A7C@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net> <4EE4F61B.2000008@ieca.com> <DC41A9FB-BEE8-4E5A-AABC-12F6F09F1A7C@tik.ee.ethz.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: mile@ietf.org
Subject: Re: [mile] Language on normative vs informative sections (was Re: AD review of draft-ietf-mile-rfc6046-bis)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 19:31:50 -0000

Hi Brain,
At 07:15 12-12-2011, Brian Trammell wrote:
>Would the following suggested text address the concerns about 
>pointing out normative vs. informative sections, while avoiding 
>language about conformance?
>
>All sections which use the key words "MUST", "MUST NOT", "REQUIRED", 
>"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 
>and "OPTIONAL" as defined in [RFC2119] are declared as normative, 
>unless specifically noted otherwise. All normative sections MUST be 
>followed by implementations of this standard. Sections which are not 
>declared as normative are informative; these provide helpful 
>background information and considerations for implementations. 
>Specifically, the normative sections in this document are Section 2 
>and Section 3.

Julian Reschke commented on the normative vs informative sections ( 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg03936.html ).

I consider my comment as addressed.  Please read the comments below 
as editorial.

It's unusual to see wording similar you proposed above in 
RFCs.  Basically, if you want to see something implemented in a 
specific way, use a "MUST".  Fro example:

   "Consistent with BCP 56, RID systems listen for TCP connections
    on port 4590."

doesn't say that all RID systems will listen on tcp/4590.

  "Every RID system participating in a consortium MUST listen for
   HTTP/TLS connections on the assigned port."

In the above sentence, there is a requirement that every RID system 
must listen on tcp/4590.

RFC 2119 defines what are absolute requirements.  The following is 
not an absolete requirement:

  "For security purposes, RID systems SHOULD NOT return 3xx Redirection
   response codes"

However, your "normative sections MUST be followed by 
implementations" could be read as a "MUST NOT return 3xx Redirection".

Kathleen provided some background information about this document ( 
http://www.ietf.org/mail-archive/web/mile/current/msg00268.html 
).   Based on that, I'll suggest the following text in the Terminology section:

   Section 1 provides helpful background information.  RID systems
   participating in a consortium are required to fully implement
   Section 3 and Section 4 to prevent interoperability concerns.

Regards,
-sm 


From msk@cloudmark.com  Mon Dec 12 11:50:57 2011
Return-Path: <msk@cloudmark.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 8365B21F8541 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 11:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oW6aoxxfz+m7 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 11:50:56 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 094B821F84DC for <mile@ietf.org>; Mon, 12 Dec 2011 11:50:56 -0800 (PST)
Received: from spite.corp.cloudmark.com (172.22.10.72) by EXCH-HTCAS901.corp.cloudmark.com (172.22.10.73) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 12 Dec 2011 11:50:55 -0800
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Mon, 12 Dec 2011 11:50:55 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "mile@ietf.org" <mile@ietf.org>
Date: Mon, 12 Dec 2011 11:50:54 -0800
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy1LStx0ahwfLmwSs6NtPupr1+KxAAAwxeQACCUW3AA1QBdgA==
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C15520@EXCH-C2.corp.cloudmark.com>
References: <4EDFE48C.2000606@ieca.com> <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com> <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 19:50:57 -0000

> -----Original Message-----
> From: kathleen.moriarty@emc.com [mailto:kathleen.moriarty@emc.com]
> Sent: Thursday, December 08, 2011 7:05 AM
> To: Murray S. Kucherawy; mile@ietf.org
> Subject: RE: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20

Hi Kathleen,

> In my initial message to the list on this topic, I stated this is what
> was done in RFC6045, per recommendation from the Security AD at the
> time.  This advice turned out to be helpful later on, as this work
> (both RFC6045-bis and RFC6046-bis) is being adopted by the ITU-T.  The
> ITU-T is adding this document into their Cybersecurity Information
> Exchange (CYBEX) suite of techniques and protocols (Study Group
> 17/Question 4).  In August, a proposal was made to format the ITU-T
> documents, where they directly refer to the IETF RFCs.  In the
> proposal, the ITU-T document is essentially an outline that lists the
> section headers of the IETF document.  Within the outline, there is
> just a statement whether or not each section of the IETF document is
> considered normative or informative.  The interpretation at the ITU
> meeting (for how the drafts look now) matches our thinking - if there
> are RFC2119 terms and points essential for implementation, it is
> normative.

I find myself cringing a bit at the idea that we need to start adding this =
to our documents just because it makes life easier for other standards orga=
nizations, especially when it feels seriously redundant to me.  I suspect i=
t feels redundant because perhaps ITU-T documents don't have RFC2119 or any=
thing like it, so they have to make explicit statements like that.  Rather,=
 they should do something like an Applicability Statement, which allows the=
m to reference our RFCs but make normative adjustments as they see fit into=
 their own contexts.

Naturally, I think our way is better.  :-)

Thanks for the background.  I guess I'd better get used to seeing this.

-MSK

From david.waltermire@nist.gov  Mon Dec 12 12:02:39 2011
Return-Path: <david.waltermire@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 D578921F8AF7 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUg2adJfedJO for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:02:39 -0800 (PST)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id D3C6621F8B04 for <mile@ietf.org>; Mon, 12 Dec 2011 12:02:38 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.339.1; Mon, 12 Dec 2011 15:02:30 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::41df:f63f:c718:e08]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Mon, 12 Dec 2011 15:01:39 -0500
From: "Waltermire, David A." <david.waltermire@nist.gov>
To: "kathleen.moriarty@emc.com" <kathleen.moriarty@emc.com>, "trammell@tik.ee.ethz.ch" <trammell@tik.ee.ethz.ch>, "mile@ietf.org" <mile@ietf.org>
Date: Mon, 12 Dec 2011 15:02:21 -0500
Thread-Topic: [mile] Binding/containment of RID and IODEF in 6046
Thread-Index: Acy48ZbFL1M/Svx4RkuHSE8THgbwvQAADzIAAAWmowA=
Message-ID: <D7A0423E5E193F40BE6E94126930C49308EEF6CAA0@MBCLUSTER.xchange.nist.gov>
References: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch> <AE31510960917D478171C79369B660FA0E1A6E9800@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A6E9800@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 20:02:39 -0000

Kathleen,

I'd like to understand your thinking regarding why adding a layer at transport is more messy.  How do you envision RID, IODEF and transport fitting together with the GRC extension?

Thanks,
Dave Waltermire

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of kathleen.moriarty@emc.com
Sent: Monday, December 12, 2011 12:22 PM
To: trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046

Hi Brian,

The solution proposed below came up in Paul Cichonski's review where he suggested we go back to IODEF being encapsulated in RID as an optional element.  I think that is the cleanest option.  I agree that it makes sense to have this, but gave a response based on prior WG decisions.  I did ask for opinions, but didn't get any.  This was right at the end of WGLC.  I think it is messy to have another layer at transport.  It does change implementations and that was one of the reasons cited for not making the change.

FYI- The GRC extension would not add to this as it would not be used with IODEF documents or RID.  It is intended as a generalization of RID to be used with other XML schemas for their transport.  Handling it in the same way makes sense.

Can we have some more opinions?

Thanks,
Kathleen (I think as an editor)


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Brian Trammell
Sent: Monday, December 12, 2011 12:14 PM
To: mile@ietf.org
Subject: [mile] Binding/containment of RID and IODEF in 6046

Greetings, all,

In answering a question from the appsdir review on 6046, I've discovered what might an issue with the transport of RID that may have an impact on 6045, as well.

The question is "what is the media type of a RID message"; the (obvious enough that I didn't notice it was missing from 6046) answer is "text/xml".

However, as defined right now that's not the case. What is sent instead is multiple XML bodies: the <RID> element followed by the <IODEF-Document> element followed by an XML signature. The extension of RID as foreseen in the GRC charter item would add other elements to this.

Should this be handled in the context of RFC6045, or RFC6046? In the former case, we would allow the <RID> element to contain arbitrary elements, as I think was alluded to in an earlier either directly or through a <Content> element, so that <RID> becomes the root element of all RID messages, something like:

<RID>
 ... other RID elements
 <Content>
  <IODEF-Document/>
 </Content>
</RID>
 
In the latter, RFC6046 would have to define a new schema, containing RID and IODEF as well as other information which could be annotated by RID in the future, like:

<RID-Transport-Envelope>
  <RID/>
  <IODEF-Document/>
</RID-TransportEnvelope>

If we expect RID documents to coexist with the data they carry anywhere _except on the wire_, it probably makes sense to update 6045 to use the former. In both of these cases, it's kind of painful to express the type of "extensible" containment we need for future GRC-like cases using xsd, so I don't think there's an ease of implementation argument either way. IIRC, this is one of the reasons the RID element didn't contain its content in the first place... but if we want a text/xml body with one root element -- which I think we do -- clearly we need some container.

Thoughts?

Best regards,

Brian (author hat)
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile

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

From kathleen.moriarty@emc.com  Mon Dec 12 12:05:16 2011
Return-Path: <kathleen.moriarty@emc.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 B04AE21F8AFD for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCakrquLsNDg for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:05:16 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 05DE721F850E for <mile@ietf.org>; Mon, 12 Dec 2011 12:05:15 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCK4l5G016618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 15:04:47 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 15:04:37 -0500
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com [10.254.92.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCK4Oqm024199; Mon, 12 Dec 2011 15:04:36 -0500
Received: from mxhub38.corp.emc.com (128.222.70.105) by mxhub10.corp.emc.com (10.254.92.105) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 12 Dec 2011 15:04:23 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub38.corp.emc.com ([128.222.70.105]) with mapi; Mon, 12 Dec 2011 15:04:23 -0500
From: <kathleen.moriarty@emc.com>
To: <msk@cloudmark.com>, <mile@ietf.org>
Date: Mon, 12 Dec 2011 15:04:22 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6046-bis
Thread-Index: Acy1LStx0ahwfLmwSs6NtPupr1+KxAAAwxeQACCUW3AA1QBdgAAAdAyQ
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9832@MX06A.corp.emc.com>
References: <4EDFE48C.2000606@ieca.com> <F5833273385BB34F99288B3648C4F06F19C6C15489@EXCH-C2.corp.cloudmark.com> <AE31510960917D478171C79369B660FA0E1A6E924C@MX06A.corp.emc.com> <F5833273385BB34F99288B3648C4F06F19C6C15520@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C15520@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 20:05:16 -0000

Hi Murray,

We would like our interpretation to set the standard for the ITU-T when the=
y list each section as normative/informative.  This is really so that we ha=
ve a better chance of winding up with interoperable implementations (the IE=
TF agreed as to what is normative/informative - the ITU goes through this e=
valuation as well).  As an FYI, the ITU does have an equivalent of RFC2119.=
  They use similar terms, but in documents prefer using shall instead of MU=
ST and have some slight differences.  In the cases of the MILE documents, w=
e have agreement to use the IETF terms since they are referencing the full =
document and not using the text from the RFCs in the body of the ITU recomm=
endation.

Ideally, we will come up with something that works in each of our documents=
 through this discussion.  I appreciate your help!

Thank you,
Kathleen

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Mur=
ray S. Kucherawy
Sent: Monday, December 12, 2011 2:51 PM
To: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6046-bis

> -----Original Message-----
> From: kathleen.moriarty@emc.com [mailto:kathleen.moriarty@emc.com]
> Sent: Thursday, December 08, 2011 7:05 AM
> To: Murray S. Kucherawy; mile@ietf.org
> Subject: RE: [mile] AD review of draft-ietf-mile-rfc6046-bis
>=20

Hi Kathleen,

> In my initial message to the list on this topic, I stated this is what
> was done in RFC6045, per recommendation from the Security AD at the
> time.  This advice turned out to be helpful later on, as this work
> (both RFC6045-bis and RFC6046-bis) is being adopted by the ITU-T.  The
> ITU-T is adding this document into their Cybersecurity Information
> Exchange (CYBEX) suite of techniques and protocols (Study Group
> 17/Question 4).  In August, a proposal was made to format the ITU-T
> documents, where they directly refer to the IETF RFCs.  In the
> proposal, the ITU-T document is essentially an outline that lists the
> section headers of the IETF document.  Within the outline, there is
> just a statement whether or not each section of the IETF document is
> considered normative or informative.  The interpretation at the ITU
> meeting (for how the drafts look now) matches our thinking - if there
> are RFC2119 terms and points essential for implementation, it is
> normative.

I find myself cringing a bit at the idea that we need to start adding this =
to our documents just because it makes life easier for other standards orga=
nizations, especially when it feels seriously redundant to me.  I suspect i=
t feels redundant because perhaps ITU-T documents don't have RFC2119 or any=
thing like it, so they have to make explicit statements like that.  Rather,=
 they should do something like an Applicability Statement, which allows the=
m to reference our RFCs but make normative adjustments as they see fit into=
 their own contexts.

Naturally, I think our way is better.  :-)

Thanks for the background.  I guess I'd better get used to seeing this.

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


From kathleen.moriarty@emc.com  Mon Dec 12 12:17:03 2011
Return-Path: <kathleen.moriarty@emc.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 245D421F8753 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.426
X-Spam-Level: 
X-Spam-Status: No, score=-6.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HfqFaLK66WVD for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 12:17:02 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4952221F8713 for <mile@ietf.org>; Mon, 12 Dec 2011 12:17:02 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCKGuaJ030368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 15:17:00 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 15:16:38 -0500
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBCKGbvC001902; Mon, 12 Dec 2011 15:16:37 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Mon, 12 Dec 2011 15:16:38 -0500
From: <kathleen.moriarty@emc.com>
To: <david.waltermire@nist.gov>, <trammell@tik.ee.ethz.ch>, <mile@ietf.org>
Date: Mon, 12 Dec 2011 15:16:36 -0500
Thread-Topic: [mile] Binding/containment of RID and IODEF in 6046
Thread-Index: Acy48ZbFL1M/Svx4RkuHSE8THgbwvQAADzIAAAWmowAAAHKmIA==
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9840@MX06A.corp.emc.com>
References: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch> <AE31510960917D478171C79369B660FA0E1A6E9800@MX06A.corp.emc.com> <D7A0423E5E193F40BE6E94126930C49308EEF6CAA0@MBCLUSTER.xchange.nist.gov>
In-Reply-To: <D7A0423E5E193F40BE6E94126930C49308EEF6CAA0@MBCLUSTER.xchange.nist.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 20:17:03 -0000

Hi Dave,

I don't see the GRC piece as an extension to IODEF and RID, but rather a ge=
neralization of RID, where the included XML is some other XML schema.  The =
request for this came from the GRC-XML and LI-XML communities that wanted a=
 way to securely transfer XML documents.

RID (IODEF)   generalized to GRC-Exchange(XML schema)

I think the last proposal is messy as we then need a wrapper at a layer up =
instead of just having RID do this.  Why have a wrapper that has a schema t=
hat optionally includes an IODEF and RID document when RID can do that for =
IODEF?  Please show other points if I am missing something, discussion is g=
ood as this changes things and we need to know if that is OK for developers=
 and to have people weigh in on what they think is the right solution.  I j=
ust think the approach of RID being the envelope is simpler.

Thanks,
Kathleen


-----Original Message-----
From: Waltermire, David A. [mailto:david.waltermire@nist.gov]=20
Sent: Monday, December 12, 2011 3:02 PM
To: Moriarty, Kathleen; trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: RE: [mile] Binding/containment of RID and IODEF in 6046

Kathleen,

I'd like to understand your thinking regarding why adding a layer at transp=
ort is more messy.  How do you envision RID, IODEF and transport fitting to=
gether with the GRC extension?

Thanks,
Dave Waltermire

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of kat=
hleen.moriarty@emc.com
Sent: Monday, December 12, 2011 12:22 PM
To: trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046

Hi Brian,

The solution proposed below came up in Paul Cichonski's review where he sug=
gested we go back to IODEF being encapsulated in RID as an optional element=
.  I think that is the cleanest option.  I agree that it makes sense to hav=
e this, but gave a response based on prior WG decisions.  I did ask for opi=
nions, but didn't get any.  This was right at the end of WGLC.  I think it =
is messy to have another layer at transport.  It does change implementation=
s and that was one of the reasons cited for not making the change.

FYI- The GRC extension would not add to this as it would not be used with I=
ODEF documents or RID.  It is intended as a generalization of RID to be use=
d with other XML schemas for their transport.  Handling it in the same way =
makes sense.

Can we have some more opinions?

Thanks,
Kathleen (I think as an editor)


-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Bri=
an Trammell
Sent: Monday, December 12, 2011 12:14 PM
To: mile@ietf.org
Subject: [mile] Binding/containment of RID and IODEF in 6046

Greetings, all,

In answering a question from the appsdir review on 6046, I've discovered wh=
at might an issue with the transport of RID that may have an impact on 6045=
, as well.

The question is "what is the media type of a RID message"; the (obvious eno=
ugh that I didn't notice it was missing from 6046) answer is "text/xml".

However, as defined right now that's not the case. What is sent instead is =
multiple XML bodies: the <RID> element followed by the <IODEF-Document> ele=
ment followed by an XML signature. The extension of RID as foreseen in the =
GRC charter item would add other elements to this.

Should this be handled in the context of RFC6045, or RFC6046? In the former=
 case, we would allow the <RID> element to contain arbitrary elements, as I=
 think was alluded to in an earlier either directly or through a <Content> =
element, so that <RID> becomes the root element of all RID messages, someth=
ing like:

<RID>
 ... other RID elements
 <Content>
  <IODEF-Document/>
 </Content>
</RID>
=20
In the latter, RFC6046 would have to define a new schema, containing RID an=
d IODEF as well as other information which could be annotated by RID in the=
 future, like:

<RID-Transport-Envelope>
  <RID/>
  <IODEF-Document/>
</RID-TransportEnvelope>

If we expect RID documents to coexist with the data they carry anywhere _ex=
cept on the wire_, it probably makes sense to update 6045 to use the former=
. In both of these cases, it's kind of painful to express the type of "exte=
nsible" containment we need for future GRC-like cases using xsd, so I don't=
 think there's an ease of implementation argument either way. IIRC, this is=
 one of the reasons the RID element didn't contain its content in the first=
 place... but if we want a text/xml body with one root element -- which I t=
hink we do -- clearly we need some container.

Thoughts?

Best regards,

Brian (author hat)
_______________________________________________
mile mailing list
mile@ietf.org
https://www.ietf.org/mailman/listinfo/mile

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


From trammell@tik.ee.ethz.ch  Mon Dec 12 13:27:49 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 C616C21F85FF for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 13:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndFnwFH27zbx for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 13:27:49 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id C3B2821F858C for <mile@ietf.org>; Mon, 12 Dec 2011 13:27:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id C27A3D930B; Mon, 12 Dec 2011 22:27:46 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ft2eB+pKwyp3; Mon, 12 Dec 2011 22:27:46 +0100 (MET)
Received: from [129.132.211.58] (vpn-global-058-dhcp.ethz.ch [129.132.211.58]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 547E3D9323; Mon, 12 Dec 2011 22:27:45 +0100 (MET)
References: <3291CF56-430B-47D8-A524-7ADFEAAF0BB7@tik.ee.ethz.ch> <AE31510960917D478171C79369B660FA0E1A6E9800@MX06A.corp.emc.com> <D7A0423E5E193F40BE6E94126930C49308EEF6CAA0@MBCLUSTER.xchange.nist.gov> <AE31510960917D478171C79369B660FA0E1A8C9840@MX06A.corp.emc.com>
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9840@MX06A.corp.emc.com>
Message-Id: <89AFD5B6-48EE-408D-8D60-5747C807D7EB@tik.ee.ethz.ch>
Date: Mon, 12 Dec 2011 22:27:18 +0100
To: "<kathleen.moriarty@emc.com>" <kathleen.moriarty@emc.com>
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (9A405)
Cc: "<mile@ietf.org>" <mile@ietf.org>
Subject: Re: [mile] Binding/containment of RID and IODEF in 6046
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2011 21:27:49 -0000

hi, Kathleen,

on review and further consideration, I'm convinced -- the RID as envelope ap=
proach seems to be the cleaner way to do this, especially in light of future=
 plans wrt GRC...

cheers, Brian (author hat)

Sent from my iPhone

On 12.12.2011, at 21:16, <kathleen.moriarty@emc.com> wrote:

> Hi Dave,
>=20
> I don't see the GRC piece as an extension to IODEF and RID, but rather a g=
eneralization of RID, where the included XML is some other XML schema.  The r=
equest for this came from the GRC-XML and LI-XML communities that wanted a w=
ay to securely transfer XML documents.
>=20
> RID (IODEF)   generalized to GRC-Exchange(XML schema)
>=20
> I think the last proposal is messy as we then need a wrapper at a layer up=
 instead of just having RID do this.  Why have a wrapper that has a schema t=
hat optionally includes an IODEF and RID document when RID can do that for I=
ODEF?  Please show other points if I am missing something, discussion is goo=
d as this changes things and we need to know if that is OK for developers an=
d to have people weigh in on what they think is the right solution.  I just t=
hink the approach of RID being the envelope is simpler.
>=20
> Thanks,
> Kathleen
>=20
>=20
> -----Original Message-----
> From: Waltermire, David A. [mailto:david.waltermire@nist.gov]=20
> Sent: Monday, December 12, 2011 3:02 PM
> To: Moriarty, Kathleen; trammell@tik.ee.ethz.ch; mile@ietf.org
> Subject: RE: [mile] Binding/containment of RID and IODEF in 6046
>=20
> Kathleen,
>=20
> I'd like to understand your thinking regarding why adding a layer at trans=
port is more messy.  How do you envision RID, IODEF and transport fitting to=
gether with the GRC extension?
>=20
> Thanks,
> Dave Waltermire
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of ka=
thleen.moriarty@emc.com
> Sent: Monday, December 12, 2011 12:22 PM
> To: trammell@tik.ee.ethz.ch; mile@ietf.org
> Subject: Re: [mile] Binding/containment of RID and IODEF in 6046
>=20
> Hi Brian,
>=20
> The solution proposed below came up in Paul Cichonski's review where he su=
ggested we go back to IODEF being encapsulated in RID as an optional element=
.  I think that is the cleanest option.  I agree that it makes sense to have=
 this, but gave a response based on prior WG decisions.  I did ask for opini=
ons, but didn't get any.  This was right at the end of WGLC.  I think it is m=
essy to have another layer at transport.  It does change implementations and=
 that was one of the reasons cited for not making the change.
>=20
> FYI- The GRC extension would not add to this as it would not be used with I=
ODEF documents or RID.  It is intended as a generalization of RID to be used=
 with other XML schemas for their transport.  Handling it in the same way ma=
kes sense.
>=20
> Can we have some more opinions?
>=20
> Thanks,
> Kathleen (I think as an editor)
>=20
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Br=
ian Trammell
> Sent: Monday, December 12, 2011 12:14 PM
> To: mile@ietf.org
> Subject: [mile] Binding/containment of RID and IODEF in 6046
>=20
> Greetings, all,
>=20
> In answering a question from the appsdir review on 6046, I've discovered w=
hat might an issue with the transport of RID that may have an impact on 6045=
, as well.
>=20
> The question is "what is the media type of a RID message"; the (obvious en=
ough that I didn't notice it was missing from 6046) answer is "text/xml".
>=20
> However, as defined right now that's not the case. What is sent instead is=
 multiple XML bodies: the <RID> element followed by the <IODEF-Document> ele=
ment followed by an XML signature. The extension of RID as foreseen in the G=
RC charter item would add other elements to this.
>=20
> Should this be handled in the context of RFC6045, or RFC6046? In the forme=
r case, we would allow the <RID> element to contain arbitrary elements, as I=
 think was alluded to in an earlier either directly or through a <Content> e=
lement, so that <RID> becomes the root element of all RID messages, somethin=
g like:
>=20
> <RID>
> ... other RID elements
> <Content>
>  <IODEF-Document/>
> </Content>
> </RID>
>=20
> In the latter, RFC6046 would have to define a new schema, containing RID a=
nd IODEF as well as other information which could be annotated by RID in the=
 future, like:
>=20
> <RID-Transport-Envelope>
>  <RID/>
>  <IODEF-Document/>
> </RID-TransportEnvelope>
>=20
> If we expect RID documents to coexist with the data they carry anywhere _e=
xcept on the wire_, it probably makes sense to update 6045 to use the former=
. In both of these cases, it's kind of painful to express the type of "exten=
sible" containment we need for future GRC-like cases using xsd, so I don't t=
hink there's an ease of implementation argument either way. IIRC, this is on=
e of the reasons the RID element didn't contain its content in the first pla=
ce... but if we want a text/xml body with one root element -- which I think w=
e do -- clearly we need some container.
>=20
> Thoughts?
>=20
> Best regards,
>=20
> Brian (author hat)
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

From kathleen.moriarty@emc.com  Mon Dec 12 19:00:57 2011
Return-Path: <kathleen.moriarty@emc.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 56B651F0C40 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 19:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.133
X-Spam-Level: 
X-Spam-Status: No, score=-6.133 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nCcZTCbPa5gn for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 19:00:54 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 554FA1F0C3F for <mile@ietf.org>; Mon, 12 Dec 2011 19:00:53 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBD30psN003525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 22:00:52 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 22:00:31 -0500
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBD30Tn1032589; Mon, 12 Dec 2011 22:00:30 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Mon, 12 Dec 2011 22:00:30 -0500
From: <kathleen.moriarty@emc.com>
To: <turners@ieca.com>, <mile@ietf.org>
Date: Mon, 12 Dec 2011 22:00:28 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6045-bis
Thread-Index: Acy4U02VxoiKEc9GSCmKCpNOekAtHwAhrmjA
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com>
References: <4EE52CDE.60306@ieca.com>
In-Reply-To: <4EE52CDE.60306@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 03:00:57 -0000

Hi Sean,

Thank you for the detailed review!  Your comments and suggestions have been=
 put into the next revision of RFC6045-bis.  I responded in line to each of=
 the suggestions and put a few up front that either still needs to be done =
or where there is an outstanding question.

5) s1.1/s1.2: I think any section that has a normative reference and any
section that has a 2119 keyword MUST be an normative section.  This
includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
  I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
  Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.

The text for normative/informative will match that decided in RFC6046 for c=
onsistency once decided.

11) s3: Is it worth adding an informative reference to RFC 6302 in the
last paragraph?  It's a BCP for internet facing server logging
recommendations?

KM: I think this is more appropriate for RFC6046-bis since it deals with th=
e IP addresses, port numbers, etc. for logging based on Internet facing hos=
ts.  Let me know if you think otherwise?

12) s?: Is it worth adding an informative reference to
draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
telechat?

KM: I could add a reference or they could add on to RID/RID Transport?  Cou=
ld this hold up getting the RFC issued if we have to wait for their numbers=
 (if the document doesn't get published first) before our docs referencing =
it can be published?

23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
suggests strongly considering another hash alg.  Note that it also
suggests pointing to RFC 6194 if you're specifying SHA-1.  This should
probably be in the security considerations.


Updating the examples to use another algorithm would take care of this issu=
e.  Let me see what I can do here... this should not be a hard fix as long =
as I can generate the examples.  I have different tools now, so I just need=
 to figure out what I need to do this.  This is the only place SHA-1 shows =
up, do you want to see a statement in the security considerations section e=
xplaining that SHA-1 should not be used, pointing to RFC 6194 if this refer=
ence is removed?

28)  Need to fix this one still.  And look at rearranging section 3.

The changes have been made and will be reflected in the next revision.  I h=
ave not made a change to have RID envelope IODEF as that is still being dis=
cussed and would require all of the examples to be updated in addition to t=
he schema.

Thanks,
Kathleen

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sea=
n Turner
Sent: Sunday, December 11, 2011 5:21 PM
To: mile@ietf.org
Subject: [mile] AD review of draft-ietf-mile-rfc6045-bis

Here is my AD review of draft-ietf-mile-rfc6046-bis.

1) s1: I think saying this document updates while the header says
obsoletes is going to confuse folks:

OLD:

   This specification updates [RFC6045].

NEW:

   This specification obsoletes [RFC6045].


KM: DONE

2) s1: Instead of saying this is an updated version of RFC X maybe just
say RID:

OLD:

  Edits reflected in this updated version of RFC6045 ...

NEW:

  Edits reflected in this updated version of RID ...

KM: DONE

3) s1: I think you need to add a new 1st bullet for the changes:

  o This document is on standards track while [RFC6045] was
informational, but now it's historic.

or something like that.

KM: DONE

4) s1: In the summary about schema changes, you should note that the
schema version was updated.

KM: DONE

5) s1.1/s1.2: I think any section that has a normative reference and any
section that has a 2119 keyword MUST be an normative section.  This
includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
  I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
  Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.

6) s2: expand NP or is it supposed to be SP?  Also maybe do a global
replace on NP/network provider with SP/service provider?

KM: Fixed, now SP.

7) s3: I think you should re-jiggle the sections to move the normative
reference to 6046-bis.   Then you can delete this paragraph because it
would be redundant with the paragraph in s1.1/s1.2.  Maybe have a
subsection that is about transport or work it in to s3.3:

OLD:

  A RID message uses both
  the IODEF document and RID document, which is encapsulated for
  transport [RFC6046-bis].

NEW:

  A RID message uses both
  the IODEF document and RID document, which MUST be encapsulated for
  transport as specified in [RFC6046-bis].

KM: DONE

8) s3s/4.1: I'd strike all the references to the "cloud."  If it had of
been in 6045 I could see it staying, but it's new.  It's a great
buzzword that is going to result is whole lotta comments about what is
it and give me some references.  All of the times it's used it's an
example so it's not needed because they're really not needed:
-  (Internet backbones or cloud infrastructures)
- An example of a consortium might include the cloud service providers.
- (network, cloud, etc.)
- s4.1: cloud from ClientToSP and SPToClient

KM: DONE: All instances of the word cloud have been removed.

9) s3: The reference for X.ridd out to be to 6046-bis - no?

KM: DONE.  Thanks for catching that, I thought all of these references were=
 removed.

10) s3: I guess this is okay, but it's a mouthful:

  One goal of RID is to prevent the need to permit access to other
  networks' equipment through the use of a standard messaging mechanism
  to enable the communication of incident handling information to other
  providers in a consortium or in neighboring networks.

KM: Two sentences:
  One goal of RID is to prevent the need to permit access to other
  networks' equipment.  RID provides a standard messaging mechanism
  to enable the communication of incident handling information to other
  providers in a consortium or in neighboring networks.

11) s3: Is it worth adding an informative reference to RFC 6302 in the
last paragraph?  It's a BCP for internet facing server logging
recommendations?

KM: I think this is more appropriate for RFC6046-bis since it deals with th=
e IP addresses, port numbers, etc. for logging based on Internet facing hos=
ts.

12) s?: Is it worth adding an informative reference to
draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
telechat?

KM: I could add a reference or they could add on to RID/RID Transport?  Cou=
ld this hold up getting the RFC issued if we have to wait for their numbers=
 (if the document doesn't get published first) before our docs referencing =
it can be published?

13) s3.1: nit-picking:

OLD:

RID provides a standard protocol and format that is required to ensure
inter-operability between vendors for the implementation of an incident
messaging mechanism.

NEW:

RID provides a protocol and format that ensures inter-operability
between vendors for the implementation of an incident messaging mechanism.

KM: DONE - also changed inter-operability to one word.

14) s3.5: Which of the message types MUST an implementation support?  Is
it all of them or just some of them?

KM: All, I adjusted the text at the introduction to make this clear.  Now s=
ays:
The six message types that MUST be implemented are as follows:

15) s4 3rd para: not sure how this fits in with the requirement to use
TLS.  I assume you're talking about message security here?

KM: This is the XML security at the XML document layer.  I see how the firs=
t sentence is confusing that point.
The paragraph now reads as follows.

Current text: The security requirements of sending incident information acr=
oss the
   network include the use of encryption.  The RIDPolicy information is
   not required to be encrypted, so separating out this data from the
   IODEF XML document removes the need for decrypting and parsing the
   IODEF document to determine how it should be handled
   at each RID host.
Proposed text: The security requirements of sending incident information be=
tween
   entities  include the use of encryption.  The RIDPolicy information is
   not required to be encrypted, so separating out this data from the
   IODEF extension removes the need for decrypting and parsing the
   entire IODEF and RID document to determine how it should be handled
   at each RID host.

16) REQUIRED: Do you want to use required or MUST?  The ITU document
I've seen makes no mention of mapping REQUIRED (IETF) to SHALL (ITU).
If ITU is only going to use MUST then maybe you need to change all
instances of REQUIRED to MUST?

KM: At the last discussion on this topic, SG 17 said they would use RFC2119=
 language (as referenced in the RFC) and those definitions.  This would kee=
p the UML terminology consistent with RFC5070.  I *think* we should keep it=
 at REQUIRED, but will change it if you think that is preferred.

17) s4.1: region: r/Required/REQUIRED
           TrafficType: r/One or many./One or more.  ?
           type.Attack: r/This option should only/This option SHOULD
                          only   (all the other ones are 2119-ed)

KM: Fixed REQUIRED
Yes, the second should and has been changed to 'more'
Fixed to SHOULD - thanks, good catches!


18) s4.2: Justification - shouldn't the numbering start at 1?

KM: Urg!  This is an error with the XML and it has been intermittent.  I wi=
ll pull up the document in vi to see if anything is hidden that is causing =
this issue.  Otherwise, I will manually fix before submitting and warn the =
RFC editor when I send in the XML for the document.

19) s5.*: Need a reference for XML encryption.  You got one for XMLDsig
but not XMLEnc.  Why are s5.1 and s5.2:

    Standards for encryption and digital signatures [RFC3275], [XMLsig]:

while s5.3-6 is:

     Standards for encryption and digital signatures [RFC3275]:

KM: Changed all similar statements (6):
Standards for encryption and digital signatures [RFC3275], [XMLsig], [XMLen=
crypt]:

Thanks for the catch!

20) s5.*: Contains the following:

    The following information is required for Investigation request
    messages and is provided through:

should this be REQUIRED as opposed to required?  I'm taking that
everything in there MUST be included in the message type?


KM: Yes, fixed for all message types.  REQUIRED is now used in each.

21) s5.3: contains the following:

      Trace number - used for multiple traces of a single
      incident; must be noted.

What's the must be noted bit about? noted by whom?

KM:     Appeared in 4 message types each adjusted as listed below:

        Changed in Result message description to read:
      Trace number - used for multiple traces of a single
      incident; MUST be included if the response is specific to an instance=
 of an incident.

        Investigation Request message:
        Changed to:        Trace number - used for multiple traces of a sin=
gle
      incident; MUST be included if the InvestigationRequest is an instance=
 of an incident.

      Changed in Result message description to read:
      Trace number - used for multiple traces of a single
      incident; MUST be included if the Report is specific to an instance o=
f an incident.

        IncidentQuery message:
        Changed to:        Trace number - used for multiple traces of a sin=
gle
      incident; MUST be included if the IncidentQuery is an instance of an =
incident.


22) s5.5: Contains:

    The following data is recommended if available and can be provided
    through:

Should this be RECOMMENDED?

KM: FIXED.  Thanks!

23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
suggests strongly considering another hash alg.  Note that it also
suggests pointing to RFC 6194 if you're specifying SHA-1.  THis should
probably be in the security considerations.

KM:     Updating the examples to use another algorithm would take care of t=
his issue.  Let me see what I can do here... this should not be a hard fix =
as long as I can generate the examples.  I have different tools now, so I j=
ust need to figure out what I need to do this.  This is the only place SHA-=
1 shows up, do you want to see a statement in the security considerations s=
ection explaining that SHA-1 should not be used, pointing to RFC 6194 if th=
is reference is removed?

24) s7: I didn't validate the schema - let me know what tool you used ;)


KM:     Developed in XMLSpy
        Recently validated in several tools, one was
        http://www.w3.org/2001/03/webdata/xsv

        We (I had colleagues help confirm in addition to WG chair validatio=
n) did run into an issue with XMLDigSig validating because of slow response=
s to their web server.  This was confirmed to be the issue, no problems now=
.

25) s12.1: Is the June 2008 version considered stable enough to be a
normative reference?  It's not a W3c recommendation yet.  I think this
would need to be called out as a DOWNREF.  You got away with it in 6045
because that RFC was informational.  If you're going to have this
DOWNREF is there any reason to point to v1 of XMLDsig at all?

KM:     The link out of RFC6045-bis says it became a W3C recommendation 10 =
June 2008.  This is the latest version.  They also provide information on 1=
0 implementations and interoperability testing: http://www.w3.org/TR/xmldsi=
g-core/


26) s8.1: need a reference for the NTP timestamp.

KM:     This is in IODEF, using the DateTime element of the RecordItem clas=
s which references RFC3339.  I changed the text to make sure this is clear =
as follows:

If an Investigation or TraceRequest does not include a RecordItem entry, a =
timestamp MUST be used to ensure there is data to be signed for the multi-h=
op authentication use case.  The DateTime element of the IODEF RecordItem c=
lass, [RFC5070] Section 3.19.1, is used for this purpose.

27) s8.1: Could throw in a reference to [RFC3647] for certificate policy
and certification practices in this sentence:

  The method used SHOULD adhere to any
  certificate policy and practices agreements between entities
  for the use of RID.

I guess I see there's a reference later.

KM:     Since it the reference does not come up for a while, I added here -=
 the first place a CP and CPS are mentioned.

28) s8.3, s.8.4, s8.5: There seems to be some duplication amongst these
sections.  If s8.3 is about TCP then all you need is the first
paragraph.  The other two paragraphs are repeated later (or could be
moved to s8.2).  And, shoudn't this section then be called "Transport
Protocol" being that TCP is about transport?  And you're not talking
about security of TCP like TCP-AO so maybe drop the Integrity and
Authentication?  s8.4 is about dedicated connections but then seems to
repeat some text from s8.3.  s8.5 is about the Authentication of RID
but then it talks about TLS.  Couldn't you just have one section that
talked about PKIs and point all the sections there?

KM: Need to fix this one still.

29) s8.3: Need a reference to BEEP.

KM: Added reference to RFC3080, informative.

30) s8.3: Note using the RIR's PKI, which they're using for SIDR, would
be require a pretty big change to their CP.

KM: Thank you for the heads up.  This was just meant as an example...

31) s8.3: I think approved could be removed from the following (also
ARIN is an RIR):

OLD:

  the American Registry for Internet
  Numbers (ARIN) and the Regional Internet Registry's (RIR's) PKI
  hierarchy, vendor issued certificates, or approved issuers of
  Extended Validation (EV) Certificates.

NEW:

  the Regional Internet Registry's (RIR's) PKI
  hierarchy, vendor issued certificates, or Extended
  Validation (EV) certificate issuers.

KM: DONE, thanks.

32) s8.4: Contains the following:

  In order to address the integrity and authenticity of messages,
  transport encryption MUST be used to secure the traffic sent between
  RID systems.

Are you saying encryption is providing integrity and authentication of
messages?  I just think this needs to be reworded.

KM: No this paragraph is talking about the Transport covered in RFC6046-bis=
 or other possible transports.  I think about this more with reworking sect=
ion 8.

33) s8.4: Wouldn't a better name for this section be "Dedicated
Connections" or something like that?  It talks about having a dedicated
connection and how good that is.  Move the 2nd and 3rd paragraphs to s8.2?

KM: I'll look at this as well with the changes to section 8.

34) I went all googlie-eyed in s8.4-8.5.  So I might have more but don't
wait on them.

KM: Please let me know if you do have comments.  This came up as a solution=
 to a problem pointed out by Randy Bush, I believe... a long time ago.  I d=
id update it recently.

35) s8.6: maybe rephrase one of the bullets:

OLD:

  o  A PKI and policy to provide authentication, integrity, and
       privacy.

NEW:

  o A PKI, certificate policy, and certification practice statement
    to provide authentication, integrity, and privacy.

KM: DONE, thanks.

36) s8.6: what does this sentence mean:

  The PKI may be a subordinate CA or in
  the CA hierarchy from the SP's consortium to establish the trust
  relationships necessary as the request is made to other connected
  networks.

If you don't need it I'd just remove it.

KM: Removed.

37) s8.7: Expand IDSs.

KM: added on first occurrence of IDSs

38) s8.7: contains:

    o  Customers MUST know

That's a pretty tall order, maybe all that's really needed is that they
be informed:

    o  Customers MUST be informed of

same for the next bullet?

KM: DONE: Updated.

39) s9: should the availability be replaced by authentication?
         r/Authenticated encrypted/Protected
         r/of the document contents./of the document contents at the
           application layer.

OLD:

  Trust relationships are based on consortiums and established trust
  relationships of public key infrastructure (PKI) cross-certifications
  of consortiums.

NEW:

  Trust relationships are based on public key infrastructure (PKI).

KM: DONE.

If you've got a requirement in this section then it's a normative
section.  THere's one SHOULD here.

KM: DONE.  When I rework section 8, I can try moving this into that section=
 if it makes sense to keep this informative.

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


From inacio@cert.org  Mon Dec 12 20:17:55 2011
Return-Path: <inacio@cert.org>
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 C6EF91F0C40 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLq42ysYFTlD for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:17:55 -0800 (PST)
Received: from plainfield.sei.cmu.edu (plainfield.sei.cmu.edu [192.58.107.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0AC1F0C3F for <mile@ietf.org>; Mon, 12 Dec 2011 20:17:54 -0800 (PST)
Received: from timber.sei.cmu.edu (timber.sei.cmu.edu [10.64.21.23]) by plainfield.sei.cmu.edu (8.14.4/8.14.4/1294) with ESMTP id pBD4HnnL004523; Mon, 12 Dec 2011 23:17:49 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cert.org; s=jthatj15xw2j; t=1323749869; bh=antj/RXnxQGBwBWEbmrgnwrt3RscCocjk3HUY7OrmX8=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version:Sender: Reply-To; b=YP/JnOjVV3d2V9UGEYLh3kY/Z1NIqkNMGgCAVuFH1EbOJv3B8dTxxLFWcrdEE7Eu2 ePYZ9hay3GQP/pgh5urnJrn6t9Q36OJwmo6vNzNkNkrlHQrbGBUynrsUjSHSzuNfv9 whEKfwRIX2dlBsnavC4STby/iII/M8sDjICdBrJc=
Received: from owa.sei.cmu.edu (vader.sei.cmu.edu [10.64.28.14]) by timber.sei.cmu.edu (8.14.4/8.14.4/1348) with ESMTP id pBD4Hn9f032239; Mon, 12 Dec 2011 23:17:49 -0500
Received: from EXCHANGE.sei.cmu.edu ([10.64.28.12]) by vader.sei.cmu.edu ([10.64.28.14]) with mapi; Mon, 12 Dec 2011 23:16:38 -0500
From: Chris Inacio <inacio@cert.org>
To: "<kathleen.moriarty@emc.com> <kathleen.moriarty@emc.com>" <kathleen.moriarty@emc.com>
Date: Mon, 12 Dec 2011 23:17:53 -0500
Thread-Topic: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
Thread-Index: Acy5TgHacbxhK7dBRSevWuDeJjS+vg==
Message-ID: <509FF779-8378-48D9-BD77-591236625E0B@cert.org>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mile@ietf.org" <mile@ietf.org>
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 04:17:55 -0000

I would really like the title to be changed to=20

"Transport of Real-time Inter-network Defense (RID) Messages over HTTPS"

unless we intend for HTTPS to be the exclusive transport of RID.


Chris



On Nov 21, 2011, at 9:01 AM, <kathleen.moriarty@emc.com> <kathleen.moriarty=
@emc.com> wrote:

> Hello,
>=20
> I'd like to start a two-week working group last call (WGLC) on the RFC604=
6-bis document (draft-ietf-mile-rfc6046-bis-01).
>=20
> Please make your comments on the document to the mile@ietf.org list by 5 =
December 2011. The more reviews, the better, so please take time to read th=
e document if you've not done so yet.
>=20
> Many thanks, and best regards,
>=20
> Kathleen (as chair of the MILE WG)
>=20
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Mon Dec 12 20:47:33 2011
Return-Path: <kathleen.moriarty@emc.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 7B9B721F84C9 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.428
X-Spam-Level: 
X-Spam-Status: No, score=-6.428 tagged_above=-999 required=5 tests=[AWL=0.171,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4Ad6Y0BkMRV for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:47:33 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id E0ECB21F8880 for <mile@ietf.org>; Mon, 12 Dec 2011 20:47:32 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBD4lNBK010757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Dec 2011 23:47:28 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 12 Dec 2011 23:47:06 -0500
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBD4l6al021921; Mon, 12 Dec 2011 23:47:06 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Mon, 12 Dec 2011 23:47:05 -0500
From: <kathleen.moriarty@emc.com>
To: <inacio@cert.org>
Date: Mon, 12 Dec 2011 23:47:05 -0500
Thread-Topic: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
Thread-Index: Acy5TgHacbxhK7dBRSevWuDeJjS+vgAA35bg
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org>
In-Reply-To: <509FF779-8378-48D9-BD77-591236625E0B@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 04:47:33 -0000

Hello Chris,

HTTPS is not intended to be the exclusive transport of RID.  I am fine with=
 the document name change, any opinions/objections?

Thank you,
Kathleen (as WG chair)

-----Original Message-----
From: Chris Inacio [mailto:inacio@cert.org]=20
Sent: Monday, December 12, 2011 11:18 PM
To: Moriarty, Kathleen
Cc: trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 20=
11

I would really like the title to be changed to=20

"Transport of Real-time Inter-network Defense (RID) Messages over HTTPS"

unless we intend for HTTPS to be the exclusive transport of RID.


Chris



On Nov 21, 2011, at 9:01 AM, <kathleen.moriarty@emc.com> <kathleen.moriarty=
@emc.com> wrote:

> Hello,
>=20
> I'd like to start a two-week working group last call (WGLC) on the RFC604=
6-bis document (draft-ietf-mile-rfc6046-bis-01).
>=20
> Please make your comments on the document to the mile@ietf.org list by 5 =
December 2011. The more reviews, the better, so please take time to read th=
e document if you've not done so yet.
>=20
> Many thanks, and best regards,
>=20
> Kathleen (as chair of the MILE WG)
>=20
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile



From trammell@tik.ee.ethz.ch  Mon Dec 12 20:56:36 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 554AE11E8098 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRtlpL08tg0i for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 20:56:35 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id BB43311E807F for <mile@ietf.org>; Mon, 12 Dec 2011 20:56:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 91865D9304; Tue, 13 Dec 2011 05:56:33 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Dasn0M8IeKGh; Tue, 13 Dec 2011 05:56:33 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 497EAD9302; Tue, 13 Dec 2011 05:56:33 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com>
Date: Tue, 13 Dec 2011 05:56:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC50BE1A-FFB8-4206-9DE3-B4BB65175AE6@tik.ee.ethz.ch>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org> <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com>
To: <kathleen.moriarty@emc.com> <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 04:56:36 -0000

Hi, Kathleen, Chris,

Sounds good to me.

Brian (author hat)

On Dec 13, 2011, at 5:47 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:

> Hello Chris,
>=20
> HTTPS is not intended to be the exclusive transport of RID.  I am fine =
with the document name change, any opinions/objections?
>=20
> Thank you,
> Kathleen (as WG chair)
>=20
> -----Original Message-----
> From: Chris Inacio [mailto:inacio@cert.org]=20
> Sent: Monday, December 12, 2011 11:18 PM
> To: Moriarty, Kathleen
> Cc: trammell@tik.ee.ethz.ch; mile@ietf.org
> Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 =
December 2011
>=20
> I would really like the title to be changed to=20
>=20
> "Transport of Real-time Inter-network Defense (RID) Messages over =
HTTPS"
>=20
> unless we intend for HTTPS to be the exclusive transport of RID.
>=20
>=20
> Chris
>=20
>=20
>=20
> On Nov 21, 2011, at 9:01 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:
>=20
>> Hello,
>>=20
>> I'd like to start a two-week working group last call (WGLC) on the =
RFC6046-bis document (draft-ietf-mile-rfc6046-bis-01).
>>=20
>> Please make your comments on the document to the mile@ietf.org list =
by 5 December 2011. The more reviews, the better, so please take time to =
read the document if you've not done so yet.
>>=20
>> Many thanks, and best regards,
>>=20
>> Kathleen (as chair of the MILE WG)
>>=20
>>=20
>>=20
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>=20


From trammell@tik.ee.ethz.ch  Mon Dec 12 21:03:43 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 E02FB21F84A7 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 21:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efBHhQnT-Nak for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 21:03:42 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id CBBBD21F84A0 for <mile@ietf.org>; Mon, 12 Dec 2011 21:03:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 13A84D9304; Tue, 13 Dec 2011 06:03:41 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9nuMWdZzfdCS; Tue, 13 Dec 2011 06:03:40 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id CCABED9302; Tue, 13 Dec 2011 06:03:40 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com>
Date: Tue, 13 Dec 2011 06:03:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C14A263-CA54-4E7B-B1BB-C322A2B7250C@tik.ee.ethz.ch>
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com>
To: <kathleen.moriarty@emc.com> <kathleen.moriarty@emc.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 05:03:44 -0000

Hi, Kathleen, Sean,

One point inline, below,

Cheers,

Brian (6046 author hat)

On Dec 13, 2011, at 4:00 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:

> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
> last paragraph?  It's a BCP for internet facing server logging
> recommendations?
>=20
> KM: I think this is more appropriate for RFC6046-bis since it deals =
with the IP addresses, port numbers, etc. for logging based on Internet =
facing hosts.  Let me know if you think otherwise?

I agree -- I believe this should be referenced from 6046.


From ramartin@mitre.org  Mon Dec 12 21:29:32 2011
Return-Path: <ramartin@mitre.org>
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 6A0C521F84B3 for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 21:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PR6ga0nfC2ri for <mile@ietfa.amsl.com>; Mon, 12 Dec 2011 21:29:31 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2319121F84A8 for <mile@ietf.org>; Mon, 12 Dec 2011 21:29:31 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 3007921B109A; Tue, 13 Dec 2011 00:29:30 -0500 (EST)
Received: from IMCCAS01.MITRE.ORG (imccas01.mitre.org [129.83.29.78]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 1CF6121B108D; Tue, 13 Dec 2011 00:29:30 -0500 (EST)
Received: from bvb-172-31-42-154.mitre.org (129.83.31.53) by IMCCAS01.MITRE.ORG (129.83.29.78) with Microsoft SMTP Server id 14.1.339.1; Tue, 13 Dec 2011 00:29:29 -0500
Message-ID: <4EE6E2B3.5000208@mitre.org>
Date: Tue, 13 Dec 2011 00:29:23 -0500
From: "Martin, Robert A." <ramartin@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org> <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com> <EC50BE1A-FFB8-4206-9DE3-B4BB65175AE6@tik.ee.ethz.ch>
In-Reply-To: <EC50BE1A-FFB8-4206-9DE3-B4BB65175AE6@tik.ee.ethz.ch>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 05:29:32 -0000

Works for me.

Bob

On 12/12/11 11:56 PM, Brian Trammell wrote:
> Hi, Kathleen, Chris,
>
> Sounds good to me.
>
> Brian (author hat)
>
> On Dec 13, 2011, at 5:47 AM,<kathleen.moriarty@emc.com>  <kathleen.moriarty@emc.com>  wrote:
>
>> Hello Chris,
>>
>> HTTPS is not intended to be the exclusive transport of RID.  I am fine with the document name change, any opinions/objections?
>>
>> Thank you,
>> Kathleen (as WG chair)
>>
>> -----Original Message-----
>> From: Chris Inacio [mailto:inacio@cert.org]
>> Sent: Monday, December 12, 2011 11:18 PM
>> To: Moriarty, Kathleen
>> Cc: trammell@tik.ee.ethz.ch; mile@ietf.org
>> Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
>>
>> I would really like the title to be changed to
>>
>> "Transport of Real-time Inter-network Defense (RID) Messages over HTTPS"
>>
>> unless we intend for HTTPS to be the exclusive transport of RID.
>>
>>
>> Chris
>>
>>
>>
>> On Nov 21, 2011, at 9:01 AM,<kathleen.moriarty@emc.com>  <kathleen.moriarty@emc.com>  wrote:
>>
>>> Hello,
>>>
>>> I'd like to start a two-week working group last call (WGLC) on the RFC6046-bis document (draft-ietf-mile-rfc6046-bis-01).
>>>
>>> Please make your comments on the document to the mile@ietf.org list by 5 December 2011. The more reviews, the better, so please take time to read the document if you've not done so yet.
>>>
>>> Many thanks, and best regards,
>>>
>>> Kathleen (as chair of the MILE WG)
>>>
>>>
>>>
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
> .
>

From kathleen.moriarty@emc.com  Tue Dec 13 04:51:36 2011
Return-Path: <kathleen.moriarty@emc.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 E6E5D21F8ABD for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 04:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.434
X-Spam-Level: 
X-Spam-Status: No, score=-6.434 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sfc7Kogb4Ug2 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 04:51:35 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 31EC021F8A97 for <mile@ietf.org>; Tue, 13 Dec 2011 04:51:34 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBDCpVgt008061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Dec 2011 07:51:31 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Tue, 13 Dec 2011 07:51:20 -0500
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBDCpJ4p019860; Tue, 13 Dec 2011 07:51:19 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Tue, 13 Dec 2011 07:51:19 -0500
From: <kathleen.moriarty@emc.com>
To: <tony@yaanatech.com>
Date: Tue, 13 Dec 2011 07:51:18 -0500
Thread-Topic: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
Thread-Index: Acy5lYvtZql1Uk8VQWGvpPJqh8mkFAAADAtQ
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9918@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org> <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com> <4EE74967.6000709@netmagic.com>
In-Reply-To: <4EE74967.6000709@netmagic.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 12:51:36 -0000

Hi Tony,

EV CERTS are mentioned in RID.  Take a look at RFC6045-bis and let me know =
if the mention in that document satisfies the question.

Thank you,
Kathleen

-----Original Message-----
From: Tony Rutkowski [mailto:trutkowski@netmagic.com]=20
Sent: Tuesday, December 13, 2011 7:48 AM
To: Moriarty, Kathleen
Cc: inacio@cert.org; mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 20=
11

Hi Kathleen,

As a liaison to the CA/Browser Forum, one obvious question
that seems begged here is why EVcerts or their ETSI TS102042
equivalent are not mentioned as a desirable https trust mechanism?

--tony


On 12/12/2011 11:47 PM, kathleen.moriarty@emc.com wrote:
> HTTPS is not intended to be the exclusive transport of RID.  I am fine wi=
th the document name change, any opinions/objections?
>
> Thank you,
> Kathleen (as WG chair)



From tony@yaanatech.com  Tue Dec 13 05:17:51 2011
Return-Path: <tony@yaanatech.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 5203021F87D6 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTcXF2DaIdmy for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:17:50 -0800 (PST)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id DCD6621F85A1 for <mile@ietf.org>; Tue, 13 Dec 2011 05:17:50 -0800 (PST)
Received: from [192.168.0.4] (pool-173-72-136-146.clppva.fios.verizon.net [173.72.136.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id E46D758070; Tue, 13 Dec 2011 13:17:47 +0000 (UTC)
Message-ID: <4EE7507A.4020307@yaanatech.com>
Date: Tue, 13 Dec 2011 08:17:46 -0500
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111208 Thunderbird/9.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org> <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 13:17:51 -0000

Hi Kathleen,

As a liaison to the CA/B Forum and ETSI ESI, one
question begged by the draft is the lack of any mention
of either the EVcert spec or its ETSI equivalent, TS102042,
as enhanced trust mechanisms.  Is there an explicit rationale?

--tony


On 12/12/2011 11:47 PM, kathleen.moriarty@emc.com wrote:
> HTTPS is not intended to be the exclusive transport of RID.  I am fine with the document name change, any opinions/objections?


From tony@yaanatech.com  Tue Dec 13 05:28:56 2011
Return-Path: <tony@yaanatech.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 9599021F8A70 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:28:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kgD8UMI2Fvu for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:28:56 -0800 (PST)
Received: from extmail1.prd.yaanatech.com (extmail1.prd.yaanatech.com [205.140.198.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1450B21F889A for <mile@ietf.org>; Tue, 13 Dec 2011 05:28:56 -0800 (PST)
Received: from [192.168.0.4] (pool-173-72-136-146.clppva.fios.verizon.net [173.72.136.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by extmail1.prd.yaanatech.com (Postfix) with ESMTP id 93F1B58070; Tue, 13 Dec 2011 13:28:55 +0000 (UTC)
Message-ID: <4EE75316.9070805@yaanatech.com>
Date: Tue, 13 Dec 2011 08:28:54 -0500
From: Tony Rutkowski <tony@yaanatech.com>
Organization: Yaana Technologies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111208 Thunderbird/9.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <AE31510960917D478171C79369B660FA0E18F8BDCF@MX06A.corp.emc.com> <509FF779-8378-48D9-BD77-591236625E0B@cert.org> <AE31510960917D478171C79369B660FA0E1A8C9906@MX06A.corp.emc.com> <4EE74967.6000709@netmagic.com> <AE31510960917D478171C79369B660FA0E1A8C9918@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9918@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mile@ietf.org
Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 December 2011
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tony@yaanatech.com
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 13:28:56 -0000

Was looking in the wrong document.  I think it's covered
in sec. 8.3 mention.  Ideally, it would be a plus to provide
references.

[EVcert] = http://www.cabforum.org/documents.html

Both the CA/B's and ETSI's specs get revised frequently.
The above URL covers both with an extensible pointer.

But this is no reason to delay finalization.

--tony


On 12/13/2011 7:51 AM, kathleen.moriarty@emc.com wrote:
> EV CERTS are mentioned in RID.  Take a look at RFC6045-bis and let me know if the mention in that document satisfies the question.


From turners@ieca.com  Tue Dec 13 05:59:15 2011
Return-Path: <turners@ieca.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 7F9FF21F8500 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.644
X-Spam-Level: 
X-Spam-Status: No, score=-101.644 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7ayYHjPiujc for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 05:59:14 -0800 (PST)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [67.18.68.4]) by ietfa.amsl.com (Postfix) with ESMTP id E615721F8AF7 for <mile@ietf.org>; Tue, 13 Dec 2011 05:59:13 -0800 (PST)
Received: by gateway13.websitewelcome.com (Postfix, from userid 5007) id 6076E6D744557; Tue, 13 Dec 2011 07:59:13 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway13.websitewelcome.com (Postfix) with ESMTP id 4B4346D74452B for <mile@ietf.org>; Tue, 13 Dec 2011 07:59:13 -0600 (CST)
Received: from [96.231.118.183] (port=48378 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RaSsw-0003qR-Gd; Tue, 13 Dec 2011 07:59:13 -0600
Message-ID: <4EE75A2B.9050600@ieca.com>
Date: Tue, 13 Dec 2011 08:59:07 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-96-231-118-183.washdc.east.verizon.net (thunderfish.local) [96.231.118.183]:48378
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 9
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 13:59:15 -0000

On 12/12/11 10:00 PM, kathleen.moriarty@emc.com wrote:
> Hi Sean,
>
> Thank you for the detailed review!  Your comments and suggestions have been put into the next revision of RFC6045-bis.  I responded in line to each of the suggestions and put a few up front that either still needs to be done or where there is an outstanding question.
>
> 5) s1.1/s1.2: I think any section that has a normative reference and any
> section that has a 2119 keyword MUST be an normative section.  This
> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>    I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>    Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>
> The text for normative/informative will match that decided in RFC6046 for consistency once decided.

ack

> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
> last paragraph?  It's a BCP for internet facing server logging
> recommendations?
>
> KM: I think this is more appropriate for RFC6046-bis since it deals with the IP addresses, port numbers, etc. for logging based on Internet facing hosts.  Let me know if you think otherwise?

see earlier message

> 12) s?: Is it worth adding an informative reference to
> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
> telechat?
>
> KM: I could add a reference or they could add on to RID/RID Transport?  Could this hold up getting the RFC issued if we have to wait for their numbers (if the document doesn't get published first) before our docs referencing it can be published?

It might, but it's on the telechat for this week so it'll have a month 
head start on RID/RID transport.  I really can't see it holding things up.

> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
> suggests strongly considering another hash alg.  Note that it also
> suggests pointing to RFC 6194 if you're specifying SHA-1.  This should
> probably be in the security considerations.
>
>
> Updating the examples to use another algorithm would take care of this issue.  Let me see what I can do here... this should not be a hard fix as long as I can generate the examples.  I have different tools now, so I just need to figure out what I need to do this.  This is the only place SHA-1 shows up, do you want to see a statement in the security considerations section explaining that SHA-1 should not be used, pointing to RFC 6194 if this reference is removed?

I'd say SHOULD NOT SHA-1 and point to 6194.

> 28)  Need to fix this one still.  And look at rearranging section 3.
>
> The changes have been made and will be reflected in the next revision.  I have not made a change to have RID envelope IODEF as that is still being discussed and would require all of the examples to be updated in addition to the schema.

I'll wait to see how the next version looks.

On #16: leaving it as REQUIRED is okay

On #25: My bad it's a recommendation.  This makes me ask: if XMLDsig 
v1.1 adds new algs and supports the nested envelope structures, then do 
you need to refer to RFC3275 at all?  If you don't, then I'd just 
replace [RFC3275] with [XMLSig] everywhere.

spt

> Thanks,
> Kathleen
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sean Turner
> Sent: Sunday, December 11, 2011 5:21 PM
> To: mile@ietf.org
> Subject: [mile] AD review of draft-ietf-mile-rfc6045-bis
>
> Here is my AD review of draft-ietf-mile-rfc6046-bis.
>
> 1) s1: I think saying this document updates while the header says
> obsoletes is going to confuse folks:
>
> OLD:
>
>     This specification updates [RFC6045].
>
> NEW:
>
>     This specification obsoletes [RFC6045].
>
>
> KM: DONE
>
> 2) s1: Instead of saying this is an updated version of RFC X maybe just
> say RID:
>
> OLD:
>
>    Edits reflected in this updated version of RFC6045 ...
>
> NEW:
>
>    Edits reflected in this updated version of RID ...
>
> KM: DONE
>
> 3) s1: I think you need to add a new 1st bullet for the changes:
>
>    o This document is on standards track while [RFC6045] was
> informational, but now it's historic.
>
> or something like that.
>
> KM: DONE
>
> 4) s1: In the summary about schema changes, you should note that the
> schema version was updated.
>
> KM: DONE
>
> 5) s1.1/s1.2: I think any section that has a normative reference and any
> section that has a 2119 keyword MUST be an normative section.  This
> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>    I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>    Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>
> 6) s2: expand NP or is it supposed to be SP?  Also maybe do a global
> replace on NP/network provider with SP/service provider?
>
> KM: Fixed, now SP.
>
> 7) s3: I think you should re-jiggle the sections to move the normative
> reference to 6046-bis.   Then you can delete this paragraph because it
> would be redundant with the paragraph in s1.1/s1.2.  Maybe have a
> subsection that is about transport or work it in to s3.3:
>
> OLD:
>
>    A RID message uses both
>    the IODEF document and RID document, which is encapsulated for
>    transport [RFC6046-bis].
>
> NEW:
>
>    A RID message uses both
>    the IODEF document and RID document, which MUST be encapsulated for
>    transport as specified in [RFC6046-bis].
>
> KM: DONE
>
> 8) s3s/4.1: I'd strike all the references to the "cloud."  If it had of
> been in 6045 I could see it staying, but it's new.  It's a great
> buzzword that is going to result is whole lotta comments about what is
> it and give me some references.  All of the times it's used it's an
> example so it's not needed because they're really not needed:
> -  (Internet backbones or cloud infrastructures)
> - An example of a consortium might include the cloud service providers.
> - (network, cloud, etc.)
> - s4.1: cloud from ClientToSP and SPToClient
>
> KM: DONE: All instances of the word cloud have been removed.
>
> 9) s3: The reference for X.ridd out to be to 6046-bis - no?
>
> KM: DONE.  Thanks for catching that, I thought all of these references were removed.
>
> 10) s3: I guess this is okay, but it's a mouthful:
>
>    One goal of RID is to prevent the need to permit access to other
>    networks' equipment through the use of a standard messaging mechanism
>    to enable the communication of incident handling information to other
>    providers in a consortium or in neighboring networks.
>
> KM: Two sentences:
>    One goal of RID is to prevent the need to permit access to other
>    networks' equipment.  RID provides a standard messaging mechanism
>    to enable the communication of incident handling information to other
>    providers in a consortium or in neighboring networks.
>
> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
> last paragraph?  It's a BCP for internet facing server logging
> recommendations?
>
> KM: I think this is more appropriate for RFC6046-bis since it deals with the IP addresses, port numbers, etc. for logging based on Internet facing hosts.
>
> 12) s?: Is it worth adding an informative reference to
> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
> telechat?
>
> KM: I could add a reference or they could add on to RID/RID Transport?  Could this hold up getting the RFC issued if we have to wait for their numbers (if the document doesn't get published first) before our docs referencing it can be published?
>
> 13) s3.1: nit-picking:
>
> OLD:
>
> RID provides a standard protocol and format that is required to ensure
> inter-operability between vendors for the implementation of an incident
> messaging mechanism.
>
> NEW:
>
> RID provides a protocol and format that ensures inter-operability
> between vendors for the implementation of an incident messaging mechanism.
>
> KM: DONE - also changed inter-operability to one word.
>
> 14) s3.5: Which of the message types MUST an implementation support?  Is
> it all of them or just some of them?
>
> KM: All, I adjusted the text at the introduction to make this clear.  Now says:
> The six message types that MUST be implemented are as follows:
>
> 15) s4 3rd para: not sure how this fits in with the requirement to use
> TLS.  I assume you're talking about message security here?
>
> KM: This is the XML security at the XML document layer.  I see how the first sentence is confusing that point.
> The paragraph now reads as follows.
>
> Current text: The security requirements of sending incident information across the
>     network include the use of encryption.  The RIDPolicy information is
>     not required to be encrypted, so separating out this data from the
>     IODEF XML document removes the need for decrypting and parsing the
>     IODEF document to determine how it should be handled
>     at each RID host.
> Proposed text: The security requirements of sending incident information between
>     entities  include the use of encryption.  The RIDPolicy information is
>     not required to be encrypted, so separating out this data from the
>     IODEF extension removes the need for decrypting and parsing the
>     entire IODEF and RID document to determine how it should be handled
>     at each RID host.
>
> 16) REQUIRED: Do you want to use required or MUST?  The ITU document
> I've seen makes no mention of mapping REQUIRED (IETF) to SHALL (ITU).
> If ITU is only going to use MUST then maybe you need to change all
> instances of REQUIRED to MUST?
>
> KM: At the last discussion on this topic, SG 17 said they would use RFC2119 language (as referenced in the RFC) and those definitions.  This would keep the UML terminology consistent with RFC5070.  I *think* we should keep it at REQUIRED, but will change it if you think that is preferred.
>
> 17) s4.1: region: r/Required/REQUIRED
>             TrafficType: r/One or many./One or more.  ?
>             type.Attack: r/This option should only/This option SHOULD
>                            only   (all the other ones are 2119-ed)
>
> KM: Fixed REQUIRED
> Yes, the second should and has been changed to 'more'
> Fixed to SHOULD - thanks, good catches!
>
>
> 18) s4.2: Justification - shouldn't the numbering start at 1?
>
> KM: Urg!  This is an error with the XML and it has been intermittent.  I will pull up the document in vi to see if anything is hidden that is causing this issue.  Otherwise, I will manually fix before submitting and warn the RFC editor when I send in the XML for the document.
>
> 19) s5.*: Need a reference for XML encryption.  You got one for XMLDsig
> but not XMLEnc.  Why are s5.1 and s5.2:
>
>      Standards for encryption and digital signatures [RFC3275], [XMLsig]:
>
> while s5.3-6 is:
>
>       Standards for encryption and digital signatures [RFC3275]:
>
> KM: Changed all similar statements (6):
> Standards for encryption and digital signatures [RFC3275], [XMLsig], [XMLencrypt]:
>
> Thanks for the catch!
>
> 20) s5.*: Contains the following:
>
>      The following information is required for Investigation request
>      messages and is provided through:
>
> should this be REQUIRED as opposed to required?  I'm taking that
> everything in there MUST be included in the message type?
>
>
> KM: Yes, fixed for all message types.  REQUIRED is now used in each.
>
> 21) s5.3: contains the following:
>
>        Trace number - used for multiple traces of a single
>        incident; must be noted.
>
> What's the must be noted bit about? noted by whom?
>
> KM:     Appeared in 4 message types each adjusted as listed below:
>
>          Changed in Result message description to read:
>        Trace number - used for multiple traces of a single
>        incident; MUST be included if the response is specific to an instance of an incident.
>
>          Investigation Request message:
>          Changed to:        Trace number - used for multiple traces of a single
>        incident; MUST be included if the InvestigationRequest is an instance of an incident.
>
>        Changed in Result message description to read:
>        Trace number - used for multiple traces of a single
>        incident; MUST be included if the Report is specific to an instance of an incident.
>
>          IncidentQuery message:
>          Changed to:        Trace number - used for multiple traces of a single
>        incident; MUST be included if the IncidentQuery is an instance of an incident.
>
>
> 22) s5.5: Contains:
>
>      The following data is recommended if available and can be provided
>      through:
>
> Should this be RECOMMENDED?
>
> KM: FIXED.  Thanks!
>
> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
> suggests strongly considering another hash alg.  Note that it also
> suggests pointing to RFC 6194 if you're specifying SHA-1.  THis should
> probably be in the security considerations.
>
> KM:     Updating the examples to use another algorithm would take care of this issue.  Let me see what I can do here... this should not be a hard fix as long as I can generate the examples.  I have different tools now, so I just need to figure out what I need to do this.  This is the only place SHA-1 shows up, do you want to see a statement in the security considerations section explaining that SHA-1 should not be used, pointing to RFC 6194 if this reference is removed?
>
> 24) s7: I didn't validate the schema - let me know what tool you used ;)
>
>
> KM:     Developed in XMLSpy
>          Recently validated in several tools, one was
>          http://www.w3.org/2001/03/webdata/xsv
>
>          We (I had colleagues help confirm in addition to WG chair validation) did run into an issue with XMLDigSig validating because of slow responses to their web server.  This was confirmed to be the issue, no problems now.
>
> 25) s12.1: Is the June 2008 version considered stable enough to be a
> normative reference?  It's not a W3c recommendation yet.  I think this
> would need to be called out as a DOWNREF.  You got away with it in 6045
> because that RFC was informational.  If you're going to have this
> DOWNREF is there any reason to point to v1 of XMLDsig at all?
>
> KM:     The link out of RFC6045-bis says it became a W3C recommendation 10 June 2008.  This is the latest version.  They also provide information on 10 implementations and interoperability testing: http://www.w3.org/TR/xmldsig-core/
>
>
> 26) s8.1: need a reference for the NTP timestamp.
>
> KM:     This is in IODEF, using the DateTime element of the RecordItem class which references RFC3339.  I changed the text to make sure this is clear as follows:
>
> If an Investigation or TraceRequest does not include a RecordItem entry, a timestamp MUST be used to ensure there is data to be signed for the multi-hop authentication use case.  The DateTime element of the IODEF RecordItem class, [RFC5070] Section 3.19.1, is used for this purpose.
>
> 27) s8.1: Could throw in a reference to [RFC3647] for certificate policy
> and certification practices in this sentence:
>
>    The method used SHOULD adhere to any
>    certificate policy and practices agreements between entities
>    for the use of RID.
>
> I guess I see there's a reference later.
>
> KM:     Since it the reference does not come up for a while, I added here - the first place a CP and CPS are mentioned.
>
> 28) s8.3, s.8.4, s8.5: There seems to be some duplication amongst these
> sections.  If s8.3 is about TCP then all you need is the first
> paragraph.  The other two paragraphs are repeated later (or could be
> moved to s8.2).  And, shoudn't this section then be called "Transport
> Protocol" being that TCP is about transport?  And you're not talking
> about security of TCP like TCP-AO so maybe drop the Integrity and
> Authentication?  s8.4 is about dedicated connections but then seems to
> repeat some text from s8.3.  s8.5 is about the Authentication of RID
> but then it talks about TLS.  Couldn't you just have one section that
> talked about PKIs and point all the sections there?
>
> KM: Need to fix this one still.
>
> 29) s8.3: Need a reference to BEEP.
>
> KM: Added reference to RFC3080, informative.
>
> 30) s8.3: Note using the RIR's PKI, which they're using for SIDR, would
> be require a pretty big change to their CP.
>
> KM: Thank you for the heads up.  This was just meant as an example...
>
> 31) s8.3: I think approved could be removed from the following (also
> ARIN is an RIR):
>
> OLD:
>
>    the American Registry for Internet
>    Numbers (ARIN) and the Regional Internet Registry's (RIR's) PKI
>    hierarchy, vendor issued certificates, or approved issuers of
>    Extended Validation (EV) Certificates.
>
> NEW:
>
>    the Regional Internet Registry's (RIR's) PKI
>    hierarchy, vendor issued certificates, or Extended
>    Validation (EV) certificate issuers.
>
> KM: DONE, thanks.
>
> 32) s8.4: Contains the following:
>
>    In order to address the integrity and authenticity of messages,
>    transport encryption MUST be used to secure the traffic sent between
>    RID systems.
>
> Are you saying encryption is providing integrity and authentication of
> messages?  I just think this needs to be reworded.
>
> KM: No this paragraph is talking about the Transport covered in RFC6046-bis or other possible transports.  I think about this more with reworking section 8.
>
> 33) s8.4: Wouldn't a better name for this section be "Dedicated
> Connections" or something like that?  It talks about having a dedicated
> connection and how good that is.  Move the 2nd and 3rd paragraphs to s8.2?
>
> KM: I'll look at this as well with the changes to section 8.
>
> 34) I went all googlie-eyed in s8.4-8.5.  So I might have more but don't
> wait on them.
>
> KM: Please let me know if you do have comments.  This came up as a solution to a problem pointed out by Randy Bush, I believe... a long time ago.  I did update it recently.
>
> 35) s8.6: maybe rephrase one of the bullets:
>
> OLD:
>
>    o  A PKI and policy to provide authentication, integrity, and
>         privacy.
>
> NEW:
>
>    o A PKI, certificate policy, and certification practice statement
>      to provide authentication, integrity, and privacy.
>
> KM: DONE, thanks.
>
> 36) s8.6: what does this sentence mean:
>
>    The PKI may be a subordinate CA or in
>    the CA hierarchy from the SP's consortium to establish the trust
>    relationships necessary as the request is made to other connected
>    networks.
>
> If you don't need it I'd just remove it.
>
> KM: Removed.
>
> 37) s8.7: Expand IDSs.
>
> KM: added on first occurrence of IDSs
>
> 38) s8.7: contains:
>
>      o  Customers MUST know
>
> That's a pretty tall order, maybe all that's really needed is that they
> be informed:
>
>      o  Customers MUST be informed of
>
> same for the next bullet?
>
> KM: DONE: Updated.
>
> 39) s9: should the availability be replaced by authentication?
>           r/Authenticated encrypted/Protected
>           r/of the document contents./of the document contents at the
>             application layer.
>
> OLD:
>
>    Trust relationships are based on consortiums and established trust
>    relationships of public key infrastructure (PKI) cross-certifications
>    of consortiums.
>
> NEW:
>
>    Trust relationships are based on public key infrastructure (PKI).
>
> KM: DONE.
>
> If you've got a requirement in this section then it's a normative
> section.  THere's one SHOULD here.
>
> KM: DONE.  When I rework section 8, I can try moving this into that section if it makes sense to keep this informative.
>
> spt
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
>

From turners@ieca.com  Tue Dec 13 06:05:08 2011
Return-Path: <turners@ieca.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 5DE8F21F8B20 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.946
X-Spam-Level: 
X-Spam-Status: No, score=-101.946 tagged_above=-999 required=5 tests=[AWL=0.319, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qM4NuDwsVqMK for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:05:07 -0800 (PST)
Received: from gateway01.websitewelcome.com (gateway01.websitewelcome.com [69.41.248.19]) by ietfa.amsl.com (Postfix) with ESMTP id 6C42721F8B1E for <mile@ietf.org>; Tue, 13 Dec 2011 06:05:07 -0800 (PST)
Received: by gateway01.websitewelcome.com (Postfix, from userid 5007) id D50EE12A872A9; Tue, 13 Dec 2011 08:05:06 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway01.websitewelcome.com (Postfix) with ESMTP id BAAD312A8721A for <mile@ietf.org>; Tue, 13 Dec 2011 08:05:06 -0600 (CST)
Received: from [96.231.118.183] (port=48873 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RaSyg-0005H6-7B; Tue, 13 Dec 2011 08:05:06 -0600
Message-ID: <4EE75B91.7040000@ieca.com>
Date: Tue, 13 Dec 2011 09:05:05 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <4EDFE48C.2000606@ieca.com> <AE31510960917D478171C79369B660FA0E1A6E9243@MX06A.corp.emc.com> <4EE1211A.90908@ieca.com> <6.2.5.6.2.20111208125545.0b027be0@resistor.net> <4EE4F61B.2000008@ieca.com> <DC41A9FB-BEE8-4E5A-AABC-12F6F09F1A7C@tik.ee.ethz.ch> <6.2.5.6.2.20111212103840.0a305bd8@resistor.net>
In-Reply-To: <6.2.5.6.2.20111212103840.0a305bd8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-96-231-118-183.washdc.east.verizon.net (thunderfish.local) [96.231.118.183]:48873
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] Language on normative vs informative sections (was Re: AD review of draft-ietf-mile-rfc6046-bis)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 14:05:08 -0000

On 12/12/11 2:30 PM, SM wrote:
> Hi Brain,
> At 07:15 12-12-2011, Brian Trammell wrote:
>> Would the following suggested text address the concerns about pointing
>> out normative vs. informative sections, while avoiding language about
>> conformance?
>>
>> All sections which use the key words "MUST", "MUST NOT", "REQUIRED",
>> "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
>> and "OPTIONAL" as defined in [RFC2119] are declared as normative,
>> unless specifically noted otherwise. All normative sections MUST be
>> followed by implementations of this standard. Sections which are not
>> declared as normative are informative; these provide helpful
>> background information and considerations for implementations.
>> Specifically, the normative sections in this document are Section 2
>> and Section 3.
>
> Julian Reschke commented on the normative vs informative sections (
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg03936.html ).
>
> I consider my comment as addressed. Please read the comments below as
> editorial.
>
> It's unusual to see wording similar you proposed above in RFCs.
> Basically, if you want to see something implemented in a specific way,
> use a "MUST". Fro example:
>
> "Consistent with BCP 56, RID systems listen for TCP connections
> on port 4590."
>
> doesn't say that all RID systems will listen on tcp/4590.
>
> "Every RID system participating in a consortium MUST listen for
> HTTP/TLS connections on the assigned port."
>
> In the above sentence, there is a requirement that every RID system must
> listen on tcp/4590.
>
> RFC 2119 defines what are absolute requirements. The following is not an
> absolete requirement:
>
> "For security purposes, RID systems SHOULD NOT return 3xx Redirection
> response codes"
>
> However, your "normative sections MUST be followed by implementations"
> could be read as a "MUST NOT return 3xx Redirection".
>
> Kathleen provided some background information about this document (
> http://www.ietf.org/mail-archive/web/mile/current/msg00268.html ). Based
> on that, I'll suggest the following text in the Terminology section:
>
> Section 1 provides helpful background information. RID systems
> participating in a consortium are required to fully implement
> Section 3 and Section 4 to prevent interoperability concerns.

I think I like this better.  Maybe we should make required/REQUIRED. 
Using this means we don't have to make the terminology and references 
sections "normative" in this bit and we really only talk about interop.

spt

From kathleen.moriarty@emc.com  Tue Dec 13 06:18:48 2011
Return-Path: <kathleen.moriarty@emc.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 DB55A21F8AF7 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.14
X-Spam-Level: 
X-Spam-Status: No, score=-6.14 tagged_above=-999 required=5 tests=[AWL=-0.141,  BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9XVlA2JCe+iS for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:18:47 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id DC0CB21F8513 for <mile@ietf.org>; Tue, 13 Dec 2011 06:18:46 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBDEIgVo003383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Dec 2011 09:18:45 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 13 Dec 2011 09:18:30 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBDEIUBJ021673; Tue, 13 Dec 2011 09:18:30 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Tue, 13 Dec 2011 09:18:30 -0500
From: <kathleen.moriarty@emc.com>
To: <turners@ieca.com>
Date: Tue, 13 Dec 2011 09:18:28 -0500
Thread-Topic: [mile] AD review of draft-ietf-mile-rfc6045-bis
Thread-Index: Acy5n4TzDwcC3qy/SLWMIVJBu7ay9wAAU40w
Message-ID: <AE31510960917D478171C79369B660FA0E1A8C9952@MX06A.corp.emc.com>
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com> <4EE75A2B.9050600@ieca.com>
In-Reply-To: <4EE75A2B.9050600@ieca.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 14:18:49 -0000

Hi Sean,

For #23, do you want the examples to all be updated or just a statement?

I will look through RFC3275 again to see if it is necessary with XML Digita=
l Signatures 1.1 and replace if appropriate (if nothing is added by the RFC=
).  There is supposed to be a new version within the year to handle some re=
cent issues.  I think it will be safe to replace as RFC3275 is most likely =
aligned with the W3C XML Digital Signature version from 2002.

I am in an all day meeting, so my updates will hopefully be ready sometime =
tonight if possible.  I still need time to focus on the rearranging for sec=
tions 3 and 8 as requested.  We also have an issues being discussed as to w=
hether or not RID should envelope IODEF.  This would require all new exampl=
es anyway and a schema update to include the optional element for the IODEF=
 schema.

Thanks,
Kathleen

-----Original Message-----
From: Sean Turner [mailto:turners@ieca.com]
Sent: Tuesday, December 13, 2011 8:59 AM
To: Moriarty, Kathleen
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis

On 12/12/11 10:00 PM, kathleen.moriarty@emc.com wrote:
> Hi Sean,
>
> Thank you for the detailed review!  Your comments and suggestions have be=
en put into the next revision of RFC6045-bis.  I responded in line to each =
of the suggestions and put a few up front that either still needs to be don=
e or where there is an outstanding question.
>
> 5) s1.1/s1.2: I think any section that has a normative reference and any
> section that has a 2119 keyword MUST be an normative section.  This
> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>    I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>    Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>
> The text for normative/informative will match that decided in RFC6046 for=
 consistency once decided.

ack

> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
> last paragraph?  It's a BCP for internet facing server logging
> recommendations?
>
> KM: I think this is more appropriate for RFC6046-bis since it deals with =
the IP addresses, port numbers, etc. for logging based on Internet facing h=
osts.  Let me know if you think otherwise?

see earlier message

> 12) s?: Is it worth adding an informative reference to
> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
> telechat?
>
> KM: I could add a reference or they could add on to RID/RID Transport?  C=
ould this hold up getting the RFC issued if we have to wait for their numbe=
rs (if the document doesn't get published first) before our docs referencin=
g it can be published?

It might, but it's on the telechat for this week so it'll have a month
head start on RID/RID transport.  I really can't see it holding things up.

> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
> suggests strongly considering another hash alg.  Note that it also
> suggests pointing to RFC 6194 if you're specifying SHA-1.  This should
> probably be in the security considerations.
>
>
> Updating the examples to use another algorithm would take care of this is=
sue.  Let me see what I can do here... this should not be a hard fix as lon=
g as I can generate the examples.  I have different tools now, so I just ne=
ed to figure out what I need to do this.  This is the only place SHA-1 show=
s up, do you want to see a statement in the security considerations section=
 explaining that SHA-1 should not be used, pointing to RFC 6194 if this ref=
erence is removed?

I'd say SHOULD NOT SHA-1 and point to 6194.

> 28)  Need to fix this one still.  And look at rearranging section 3.
>
> The changes have been made and will be reflected in the next revision.  I=
 have not made a change to have RID envelope IODEF as that is still being d=
iscussed and would require all of the examples to be updated in addition to=
 the schema.

I'll wait to see how the next version looks.

On #16: leaving it as REQUIRED is okay

On #25: My bad it's a recommendation.  This makes me ask: if XMLDsig
v1.1 adds new algs and supports the nested envelope structures, then do
you need to refer to RFC3275 at all?  If you don't, then I'd just
replace [RFC3275] with [XMLSig] everywhere.

spt

> Thanks,
> Kathleen
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of S=
ean Turner
> Sent: Sunday, December 11, 2011 5:21 PM
> To: mile@ietf.org
> Subject: [mile] AD review of draft-ietf-mile-rfc6045-bis
>
> Here is my AD review of draft-ietf-mile-rfc6046-bis.
>
> 1) s1: I think saying this document updates while the header says
> obsoletes is going to confuse folks:
>
> OLD:
>
>     This specification updates [RFC6045].
>
> NEW:
>
>     This specification obsoletes [RFC6045].
>
>
> KM: DONE
>
> 2) s1: Instead of saying this is an updated version of RFC X maybe just
> say RID:
>
> OLD:
>
>    Edits reflected in this updated version of RFC6045 ...
>
> NEW:
>
>    Edits reflected in this updated version of RID ...
>
> KM: DONE
>
> 3) s1: I think you need to add a new 1st bullet for the changes:
>
>    o This document is on standards track while [RFC6045] was
> informational, but now it's historic.
>
> or something like that.
>
> KM: DONE
>
> 4) s1: In the summary about schema changes, you should note that the
> schema version was updated.
>
> KM: DONE
>
> 5) s1.1/s1.2: I think any section that has a normative reference and any
> section that has a 2119 keyword MUST be an normative section.  This
> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>    I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>    Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>
> 6) s2: expand NP or is it supposed to be SP?  Also maybe do a global
> replace on NP/network provider with SP/service provider?
>
> KM: Fixed, now SP.
>
> 7) s3: I think you should re-jiggle the sections to move the normative
> reference to 6046-bis.   Then you can delete this paragraph because it
> would be redundant with the paragraph in s1.1/s1.2.  Maybe have a
> subsection that is about transport or work it in to s3.3:
>
> OLD:
>
>    A RID message uses both
>    the IODEF document and RID document, which is encapsulated for
>    transport [RFC6046-bis].
>
> NEW:
>
>    A RID message uses both
>    the IODEF document and RID document, which MUST be encapsulated for
>    transport as specified in [RFC6046-bis].
>
> KM: DONE
>
> 8) s3s/4.1: I'd strike all the references to the "cloud."  If it had of
> been in 6045 I could see it staying, but it's new.  It's a great
> buzzword that is going to result is whole lotta comments about what is
> it and give me some references.  All of the times it's used it's an
> example so it's not needed because they're really not needed:
> -  (Internet backbones or cloud infrastructures)
> - An example of a consortium might include the cloud service providers.
> - (network, cloud, etc.)
> - s4.1: cloud from ClientToSP and SPToClient
>
> KM: DONE: All instances of the word cloud have been removed.
>
> 9) s3: The reference for X.ridd out to be to 6046-bis - no?
>
> KM: DONE.  Thanks for catching that, I thought all of these references we=
re removed.
>
> 10) s3: I guess this is okay, but it's a mouthful:
>
>    One goal of RID is to prevent the need to permit access to other
>    networks' equipment through the use of a standard messaging mechanism
>    to enable the communication of incident handling information to other
>    providers in a consortium or in neighboring networks.
>
> KM: Two sentences:
>    One goal of RID is to prevent the need to permit access to other
>    networks' equipment.  RID provides a standard messaging mechanism
>    to enable the communication of incident handling information to other
>    providers in a consortium or in neighboring networks.
>
> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
> last paragraph?  It's a BCP for internet facing server logging
> recommendations?
>
> KM: I think this is more appropriate for RFC6046-bis since it deals with =
the IP addresses, port numbers, etc. for logging based on Internet facing h=
osts.
>
> 12) s?: Is it worth adding an informative reference to
> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
> telechat?
>
> KM: I could add a reference or they could add on to RID/RID Transport?  C=
ould this hold up getting the RFC issued if we have to wait for their numbe=
rs (if the document doesn't get published first) before our docs referencin=
g it can be published?
>
> 13) s3.1: nit-picking:
>
> OLD:
>
> RID provides a standard protocol and format that is required to ensure
> inter-operability between vendors for the implementation of an incident
> messaging mechanism.
>
> NEW:
>
> RID provides a protocol and format that ensures inter-operability
> between vendors for the implementation of an incident messaging mechanism=
.
>
> KM: DONE - also changed inter-operability to one word.
>
> 14) s3.5: Which of the message types MUST an implementation support?  Is
> it all of them or just some of them?
>
> KM: All, I adjusted the text at the introduction to make this clear.  Now=
 says:
> The six message types that MUST be implemented are as follows:
>
> 15) s4 3rd para: not sure how this fits in with the requirement to use
> TLS.  I assume you're talking about message security here?
>
> KM: This is the XML security at the XML document layer.  I see how the fi=
rst sentence is confusing that point.
> The paragraph now reads as follows.
>
> Current text: The security requirements of sending incident information a=
cross the
>     network include the use of encryption.  The RIDPolicy information is
>     not required to be encrypted, so separating out this data from the
>     IODEF XML document removes the need for decrypting and parsing the
>     IODEF document to determine how it should be handled
>     at each RID host.
> Proposed text: The security requirements of sending incident information =
between
>     entities  include the use of encryption.  The RIDPolicy information i=
s
>     not required to be encrypted, so separating out this data from the
>     IODEF extension removes the need for decrypting and parsing the
>     entire IODEF and RID document to determine how it should be handled
>     at each RID host.
>
> 16) REQUIRED: Do you want to use required or MUST?  The ITU document
> I've seen makes no mention of mapping REQUIRED (IETF) to SHALL (ITU).
> If ITU is only going to use MUST then maybe you need to change all
> instances of REQUIRED to MUST?
>
> KM: At the last discussion on this topic, SG 17 said they would use RFC21=
19 language (as referenced in the RFC) and those definitions.  This would k=
eep the UML terminology consistent with RFC5070.  I *think* we should keep =
it at REQUIRED, but will change it if you think that is preferred.
>
> 17) s4.1: region: r/Required/REQUIRED
>             TrafficType: r/One or many./One or more.  ?
>             type.Attack: r/This option should only/This option SHOULD
>                            only   (all the other ones are 2119-ed)
>
> KM: Fixed REQUIRED
> Yes, the second should and has been changed to 'more'
> Fixed to SHOULD - thanks, good catches!
>
>
> 18) s4.2: Justification - shouldn't the numbering start at 1?
>
> KM: Urg!  This is an error with the XML and it has been intermittent.  I =
will pull up the document in vi to see if anything is hidden that is causin=
g this issue.  Otherwise, I will manually fix before submitting and warn th=
e RFC editor when I send in the XML for the document.
>
> 19) s5.*: Need a reference for XML encryption.  You got one for XMLDsig
> but not XMLEnc.  Why are s5.1 and s5.2:
>
>      Standards for encryption and digital signatures [RFC3275], [XMLsig]:
>
> while s5.3-6 is:
>
>       Standards for encryption and digital signatures [RFC3275]:
>
> KM: Changed all similar statements (6):
> Standards for encryption and digital signatures [RFC3275], [XMLsig], [XML=
encrypt]:
>
> Thanks for the catch!
>
> 20) s5.*: Contains the following:
>
>      The following information is required for Investigation request
>      messages and is provided through:
>
> should this be REQUIRED as opposed to required?  I'm taking that
> everything in there MUST be included in the message type?
>
>
> KM: Yes, fixed for all message types.  REQUIRED is now used in each.
>
> 21) s5.3: contains the following:
>
>        Trace number - used for multiple traces of a single
>        incident; must be noted.
>
> What's the must be noted bit about? noted by whom?
>
> KM:     Appeared in 4 message types each adjusted as listed below:
>
>          Changed in Result message description to read:
>        Trace number - used for multiple traces of a single
>        incident; MUST be included if the response is specific to an insta=
nce of an incident.
>
>          Investigation Request message:
>          Changed to:        Trace number - used for multiple traces of a =
single
>        incident; MUST be included if the InvestigationRequest is an insta=
nce of an incident.
>
>        Changed in Result message description to read:
>        Trace number - used for multiple traces of a single
>        incident; MUST be included if the Report is specific to an instanc=
e of an incident.
>
>          IncidentQuery message:
>          Changed to:        Trace number - used for multiple traces of a =
single
>        incident; MUST be included if the IncidentQuery is an instance of =
an incident.
>
>
> 22) s5.5: Contains:
>
>      The following data is recommended if available and can be provided
>      through:
>
> Should this be RECOMMENDED?
>
> KM: FIXED.  Thanks!
>
> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
> suggests strongly considering another hash alg.  Note that it also
> suggests pointing to RFC 6194 if you're specifying SHA-1.  THis should
> probably be in the security considerations.
>
> KM:     Updating the examples to use another algorithm would take care of=
 this issue.  Let me see what I can do here... this should not be a hard fi=
x as long as I can generate the examples.  I have different tools now, so I=
 just need to figure out what I need to do this.  This is the only place SH=
A-1 shows up, do you want to see a statement in the security considerations=
 section explaining that SHA-1 should not be used, pointing to RFC 6194 if =
this reference is removed?
>
> 24) s7: I didn't validate the schema - let me know what tool you used ;)
>
>
> KM:     Developed in XMLSpy
>          Recently validated in several tools, one was
>          http://www.w3.org/2001/03/webdata/xsv
>
>          We (I had colleagues help confirm in addition to WG chair valida=
tion) did run into an issue with XMLDigSig validating because of slow respo=
nses to their web server.  This was confirmed to be the issue, no problems =
now.
>
> 25) s12.1: Is the June 2008 version considered stable enough to be a
> normative reference?  It's not a W3c recommendation yet.  I think this
> would need to be called out as a DOWNREF.  You got away with it in 6045
> because that RFC was informational.  If you're going to have this
> DOWNREF is there any reason to point to v1 of XMLDsig at all?
>
> KM:     The link out of RFC6045-bis says it became a W3C recommendation 1=
0 June 2008.  This is the latest version.  They also provide information on=
 10 implementations and interoperability testing: http://www.w3.org/TR/xmld=
sig-core/
>
>
> 26) s8.1: need a reference for the NTP timestamp.
>
> KM:     This is in IODEF, using the DateTime element of the RecordItem cl=
ass which references RFC3339.  I changed the text to make sure this is clea=
r as follows:
>
> If an Investigation or TraceRequest does not include a RecordItem entry, =
a timestamp MUST be used to ensure there is data to be signed for the multi=
-hop authentication use case.  The DateTime element of the IODEF RecordItem=
 class, [RFC5070] Section 3.19.1, is used for this purpose.
>
> 27) s8.1: Could throw in a reference to [RFC3647] for certificate policy
> and certification practices in this sentence:
>
>    The method used SHOULD adhere to any
>    certificate policy and practices agreements between entities
>    for the use of RID.
>
> I guess I see there's a reference later.
>
> KM:     Since it the reference does not come up for a while, I added here=
 - the first place a CP and CPS are mentioned.
>
> 28) s8.3, s.8.4, s8.5: There seems to be some duplication amongst these
> sections.  If s8.3 is about TCP then all you need is the first
> paragraph.  The other two paragraphs are repeated later (or could be
> moved to s8.2).  And, shoudn't this section then be called "Transport
> Protocol" being that TCP is about transport?  And you're not talking
> about security of TCP like TCP-AO so maybe drop the Integrity and
> Authentication?  s8.4 is about dedicated connections but then seems to
> repeat some text from s8.3.  s8.5 is about the Authentication of RID
> but then it talks about TLS.  Couldn't you just have one section that
> talked about PKIs and point all the sections there?
>
> KM: Need to fix this one still.
>
> 29) s8.3: Need a reference to BEEP.
>
> KM: Added reference to RFC3080, informative.
>
> 30) s8.3: Note using the RIR's PKI, which they're using for SIDR, would
> be require a pretty big change to their CP.
>
> KM: Thank you for the heads up.  This was just meant as an example...
>
> 31) s8.3: I think approved could be removed from the following (also
> ARIN is an RIR):
>
> OLD:
>
>    the American Registry for Internet
>    Numbers (ARIN) and the Regional Internet Registry's (RIR's) PKI
>    hierarchy, vendor issued certificates, or approved issuers of
>    Extended Validation (EV) Certificates.
>
> NEW:
>
>    the Regional Internet Registry's (RIR's) PKI
>    hierarchy, vendor issued certificates, or Extended
>    Validation (EV) certificate issuers.
>
> KM: DONE, thanks.
>
> 32) s8.4: Contains the following:
>
>    In order to address the integrity and authenticity of messages,
>    transport encryption MUST be used to secure the traffic sent between
>    RID systems.
>
> Are you saying encryption is providing integrity and authentication of
> messages?  I just think this needs to be reworded.
>
> KM: No this paragraph is talking about the Transport covered in RFC6046-b=
is or other possible transports.  I think about this more with reworking se=
ction 8.
>
> 33) s8.4: Wouldn't a better name for this section be "Dedicated
> Connections" or something like that?  It talks about having a dedicated
> connection and how good that is.  Move the 2nd and 3rd paragraphs to s8.2=
?
>
> KM: I'll look at this as well with the changes to section 8.
>
> 34) I went all googlie-eyed in s8.4-8.5.  So I might have more but don't
> wait on them.
>
> KM: Please let me know if you do have comments.  This came up as a soluti=
on to a problem pointed out by Randy Bush, I believe... a long time ago.  I=
 did update it recently.
>
> 35) s8.6: maybe rephrase one of the bullets:
>
> OLD:
>
>    o  A PKI and policy to provide authentication, integrity, and
>         privacy.
>
> NEW:
>
>    o A PKI, certificate policy, and certification practice statement
>      to provide authentication, integrity, and privacy.
>
> KM: DONE, thanks.
>
> 36) s8.6: what does this sentence mean:
>
>    The PKI may be a subordinate CA or in
>    the CA hierarchy from the SP's consortium to establish the trust
>    relationships necessary as the request is made to other connected
>    networks.
>
> If you don't need it I'd just remove it.
>
> KM: Removed.
>
> 37) s8.7: Expand IDSs.
>
> KM: added on first occurrence of IDSs
>
> 38) s8.7: contains:
>
>      o  Customers MUST know
>
> That's a pretty tall order, maybe all that's really needed is that they
> be informed:
>
>      o  Customers MUST be informed of
>
> same for the next bullet?
>
> KM: DONE: Updated.
>
> 39) s9: should the availability be replaced by authentication?
>           r/Authenticated encrypted/Protected
>           r/of the document contents./of the document contents at the
>             application layer.
>
> OLD:
>
>    Trust relationships are based on consortiums and established trust
>    relationships of public key infrastructure (PKI) cross-certifications
>    of consortiums.
>
> NEW:
>
>    Trust relationships are based on public key infrastructure (PKI).
>
> KM: DONE.
>
> If you've got a requirement in this section then it's a normative
> section.  THere's one SHOULD here.
>
> KM: DONE.  When I rework section 8, I can try moving this into that secti=
on if it makes sense to keep this informative.
>
> spt
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
>


From turners@ieca.com  Tue Dec 13 06:31:07 2011
Return-Path: <turners@ieca.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 20A0321F8A7E for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.67
X-Spam-Level: 
X-Spam-Status: No, score=-101.67 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWyQDXQKRRAA for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:31:05 -0800 (PST)
Received: from gateway11.websitewelcome.com (gateway11.websitewelcome.com [67.18.22.71]) by ietfa.amsl.com (Postfix) with ESMTP id 8204B21F858C for <mile@ietf.org>; Tue, 13 Dec 2011 06:31:05 -0800 (PST)
Received: by gateway11.websitewelcome.com (Postfix, from userid 5011) id 33D2F7608C035; Tue, 13 Dec 2011 08:31:04 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway11.websitewelcome.com (Postfix) with ESMTP id 139457608BFF1 for <mile@ietf.org>; Tue, 13 Dec 2011 08:31:04 -0600 (CST)
Received: from [96.231.118.183] (port=40654 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RaTNm-0002xE-9F; Tue, 13 Dec 2011 08:31:03 -0600
Message-ID: <4EE761A5.80207@ieca.com>
Date: Tue, 13 Dec 2011 09:31:01 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com> <4EE75A2B.9050600@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9952@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8C9952@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-96-231-118-183.washdc.east.verizon.net (thunderfish.local) [96.231.118.183]:40654
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 5
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 14:31:07 -0000

On 12/13/11 9:18 AM, kathleen.moriarty@emc.com wrote:
> Hi Sean,
>
> For #23, do you want the examples to all be updated or just a statement?

I'd prefer the examples be updated and the statement be made that SHA-1 
is a SHOULD NOT.

> I will look through RFC3275 again to see if it is necessary with XML Digital Signatures 1.1 and replace if appropriate (if nothing is added by the RFC).  There is supposed to be a new version within the year to handle some recent issues.  I think it will be safe to replace as RFC3275 is most likely aligned with the W3C XML Digital Signature version from 2002.

Unfortunately, the issue they're fixing isn't recent :(

> I am in an all day meeting, so my updates will hopefully be ready sometime tonight if possible.  I still need time to focus on the rearranging for sections 3 and 8 as requested.  We also have an issues being discussed as to whether or not RID should envelope IODEF.  This would require all new examples anyway and a schema update to include the optional element for the IODEF schema.

no worries

> Thanks,
> Kathleen
>
> -----Original Message-----
> From: Sean Turner [mailto:turners@ieca.com]
> Sent: Tuesday, December 13, 2011 8:59 AM
> To: Moriarty, Kathleen
> Cc: mile@ietf.org
> Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
>
> On 12/12/11 10:00 PM, kathleen.moriarty@emc.com wrote:
>> Hi Sean,
>>
>> Thank you for the detailed review!  Your comments and suggestions have been put into the next revision of RFC6045-bis.  I responded in line to each of the suggestions and put a few up front that either still needs to be done or where there is an outstanding question.
>>
>> 5) s1.1/s1.2: I think any section that has a normative reference and any
>> section that has a 2119 keyword MUST be an normative section.  This
>> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>>     I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>>     Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>>
>> The text for normative/informative will match that decided in RFC6046 for consistency once decided.
>
> ack
>
>> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
>> last paragraph?  It's a BCP for internet facing server logging
>> recommendations?
>>
>> KM: I think this is more appropriate for RFC6046-bis since it deals with the IP addresses, port numbers, etc. for logging based on Internet facing hosts.  Let me know if you think otherwise?
>
> see earlier message
>
>> 12) s?: Is it worth adding an informative reference to
>> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
>> telechat?
>>
>> KM: I could add a reference or they could add on to RID/RID Transport?  Could this hold up getting the RFC issued if we have to wait for their numbers (if the document doesn't get published first) before our docs referencing it can be published?
>
> It might, but it's on the telechat for this week so it'll have a month
> head start on RID/RID transport.  I really can't see it holding things up.
>
>> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
>> suggests strongly considering another hash alg.  Note that it also
>> suggests pointing to RFC 6194 if you're specifying SHA-1.  This should
>> probably be in the security considerations.
>>
>>
>> Updating the examples to use another algorithm would take care of this issue.  Let me see what I can do here... this should not be a hard fix as long as I can generate the examples.  I have different tools now, so I just need to figure out what I need to do this.  This is the only place SHA-1 shows up, do you want to see a statement in the security considerations section explaining that SHA-1 should not be used, pointing to RFC 6194 if this reference is removed?
>
> I'd say SHOULD NOT SHA-1 and point to 6194.
>
>> 28)  Need to fix this one still.  And look at rearranging section 3.
>>
>> The changes have been made and will be reflected in the next revision.  I have not made a change to have RID envelope IODEF as that is still being discussed and would require all of the examples to be updated in addition to the schema.
>
> I'll wait to see how the next version looks.
>
> On #16: leaving it as REQUIRED is okay
>
> On #25: My bad it's a recommendation.  This makes me ask: if XMLDsig
> v1.1 adds new algs and supports the nested envelope structures, then do
> you need to refer to RFC3275 at all?  If you don't, then I'd just
> replace [RFC3275] with [XMLSig] everywhere.
>
> spt
>
>> Thanks,
>> Kathleen
>>
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Sean Turner
>> Sent: Sunday, December 11, 2011 5:21 PM
>> To: mile@ietf.org
>> Subject: [mile] AD review of draft-ietf-mile-rfc6045-bis
>>
>> Here is my AD review of draft-ietf-mile-rfc6046-bis.
>>
>> 1) s1: I think saying this document updates while the header says
>> obsoletes is going to confuse folks:
>>
>> OLD:
>>
>>      This specification updates [RFC6045].
>>
>> NEW:
>>
>>      This specification obsoletes [RFC6045].
>>
>>
>> KM: DONE
>>
>> 2) s1: Instead of saying this is an updated version of RFC X maybe just
>> say RID:
>>
>> OLD:
>>
>>     Edits reflected in this updated version of RFC6045 ...
>>
>> NEW:
>>
>>     Edits reflected in this updated version of RID ...
>>
>> KM: DONE
>>
>> 3) s1: I think you need to add a new 1st bullet for the changes:
>>
>>     o This document is on standards track while [RFC6045] was
>> informational, but now it's historic.
>>
>> or something like that.
>>
>> KM: DONE
>>
>> 4) s1: In the summary about schema changes, you should note that the
>> schema version was updated.
>>
>> KM: DONE
>>
>> 5) s1.1/s1.2: I think any section that has a normative reference and any
>> section that has a 2119 keyword MUST be an normative section.  This
>> includes s1 (for [XML1.0]), s1.1 (for [XMLschema]), and s1.2 (for 2119).
>>     I'm also thinking s9 might also be normative (it's got SHOULDs in it)?
>>     Maybe 1.2 should be aligned with the similar paragraph in 6046-bis.
>>
>> 6) s2: expand NP or is it supposed to be SP?  Also maybe do a global
>> replace on NP/network provider with SP/service provider?
>>
>> KM: Fixed, now SP.
>>
>> 7) s3: I think you should re-jiggle the sections to move the normative
>> reference to 6046-bis.   Then you can delete this paragraph because it
>> would be redundant with the paragraph in s1.1/s1.2.  Maybe have a
>> subsection that is about transport or work it in to s3.3:
>>
>> OLD:
>>
>>     A RID message uses both
>>     the IODEF document and RID document, which is encapsulated for
>>     transport [RFC6046-bis].
>>
>> NEW:
>>
>>     A RID message uses both
>>     the IODEF document and RID document, which MUST be encapsulated for
>>     transport as specified in [RFC6046-bis].
>>
>> KM: DONE
>>
>> 8) s3s/4.1: I'd strike all the references to the "cloud."  If it had of
>> been in 6045 I could see it staying, but it's new.  It's a great
>> buzzword that is going to result is whole lotta comments about what is
>> it and give me some references.  All of the times it's used it's an
>> example so it's not needed because they're really not needed:
>> -  (Internet backbones or cloud infrastructures)
>> - An example of a consortium might include the cloud service providers.
>> - (network, cloud, etc.)
>> - s4.1: cloud from ClientToSP and SPToClient
>>
>> KM: DONE: All instances of the word cloud have been removed.
>>
>> 9) s3: The reference for X.ridd out to be to 6046-bis - no?
>>
>> KM: DONE.  Thanks for catching that, I thought all of these references were removed.
>>
>> 10) s3: I guess this is okay, but it's a mouthful:
>>
>>     One goal of RID is to prevent the need to permit access to other
>>     networks' equipment through the use of a standard messaging mechanism
>>     to enable the communication of incident handling information to other
>>     providers in a consortium or in neighboring networks.
>>
>> KM: Two sentences:
>>     One goal of RID is to prevent the need to permit access to other
>>     networks' equipment.  RID provides a standard messaging mechanism
>>     to enable the communication of incident handling information to other
>>     providers in a consortium or in neighboring networks.
>>
>> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
>> last paragraph?  It's a BCP for internet facing server logging
>> recommendations?
>>
>> KM: I think this is more appropriate for RFC6046-bis since it deals with the IP addresses, port numbers, etc. for logging based on Internet facing hosts.
>>
>> 12) s?: Is it worth adding an informative reference to
>> draft-oreirdan-mody-bot-remediation-18, which is on this weeks IESG
>> telechat?
>>
>> KM: I could add a reference or they could add on to RID/RID Transport?  Could this hold up getting the RFC issued if we have to wait for their numbers (if the document doesn't get published first) before our docs referencing it can be published?
>>
>> 13) s3.1: nit-picking:
>>
>> OLD:
>>
>> RID provides a standard protocol and format that is required to ensure
>> inter-operability between vendors for the implementation of an incident
>> messaging mechanism.
>>
>> NEW:
>>
>> RID provides a protocol and format that ensures inter-operability
>> between vendors for the implementation of an incident messaging mechanism.
>>
>> KM: DONE - also changed inter-operability to one word.
>>
>> 14) s3.5: Which of the message types MUST an implementation support?  Is
>> it all of them or just some of them?
>>
>> KM: All, I adjusted the text at the introduction to make this clear.  Now says:
>> The six message types that MUST be implemented are as follows:
>>
>> 15) s4 3rd para: not sure how this fits in with the requirement to use
>> TLS.  I assume you're talking about message security here?
>>
>> KM: This is the XML security at the XML document layer.  I see how the first sentence is confusing that point.
>> The paragraph now reads as follows.
>>
>> Current text: The security requirements of sending incident information across the
>>      network include the use of encryption.  The RIDPolicy information is
>>      not required to be encrypted, so separating out this data from the
>>      IODEF XML document removes the need for decrypting and parsing the
>>      IODEF document to determine how it should be handled
>>      at each RID host.
>> Proposed text: The security requirements of sending incident information between
>>      entities  include the use of encryption.  The RIDPolicy information is
>>      not required to be encrypted, so separating out this data from the
>>      IODEF extension removes the need for decrypting and parsing the
>>      entire IODEF and RID document to determine how it should be handled
>>      at each RID host.
>>
>> 16) REQUIRED: Do you want to use required or MUST?  The ITU document
>> I've seen makes no mention of mapping REQUIRED (IETF) to SHALL (ITU).
>> If ITU is only going to use MUST then maybe you need to change all
>> instances of REQUIRED to MUST?
>>
>> KM: At the last discussion on this topic, SG 17 said they would use RFC2119 language (as referenced in the RFC) and those definitions.  This would keep the UML terminology consistent with RFC5070.  I *think* we should keep it at REQUIRED, but will change it if you think that is preferred.
>>
>> 17) s4.1: region: r/Required/REQUIRED
>>              TrafficType: r/One or many./One or more.  ?
>>              type.Attack: r/This option should only/This option SHOULD
>>                             only   (all the other ones are 2119-ed)
>>
>> KM: Fixed REQUIRED
>> Yes, the second should and has been changed to 'more'
>> Fixed to SHOULD - thanks, good catches!
>>
>>
>> 18) s4.2: Justification - shouldn't the numbering start at 1?
>>
>> KM: Urg!  This is an error with the XML and it has been intermittent.  I will pull up the document in vi to see if anything is hidden that is causing this issue.  Otherwise, I will manually fix before submitting and warn the RFC editor when I send in the XML for the document.
>>
>> 19) s5.*: Need a reference for XML encryption.  You got one for XMLDsig
>> but not XMLEnc.  Why are s5.1 and s5.2:
>>
>>       Standards for encryption and digital signatures [RFC3275], [XMLsig]:
>>
>> while s5.3-6 is:
>>
>>        Standards for encryption and digital signatures [RFC3275]:
>>
>> KM: Changed all similar statements (6):
>> Standards for encryption and digital signatures [RFC3275], [XMLsig], [XMLencrypt]:
>>
>> Thanks for the catch!
>>
>> 20) s5.*: Contains the following:
>>
>>       The following information is required for Investigation request
>>       messages and is provided through:
>>
>> should this be REQUIRED as opposed to required?  I'm taking that
>> everything in there MUST be included in the message type?
>>
>>
>> KM: Yes, fixed for all message types.  REQUIRED is now used in each.
>>
>> 21) s5.3: contains the following:
>>
>>         Trace number - used for multiple traces of a single
>>         incident; must be noted.
>>
>> What's the must be noted bit about? noted by whom?
>>
>> KM:     Appeared in 4 message types each adjusted as listed below:
>>
>>           Changed in Result message description to read:
>>         Trace number - used for multiple traces of a single
>>         incident; MUST be included if the response is specific to an instance of an incident.
>>
>>           Investigation Request message:
>>           Changed to:        Trace number - used for multiple traces of a single
>>         incident; MUST be included if the InvestigationRequest is an instance of an incident.
>>
>>         Changed in Result message description to read:
>>         Trace number - used for multiple traces of a single
>>         incident; MUST be included if the Report is specific to an instance of an incident.
>>
>>           IncidentQuery message:
>>           Changed to:        Trace number - used for multiple traces of a single
>>         incident; MUST be included if the IncidentQuery is an instance of an incident.
>>
>>
>> 22) s5.5: Contains:
>>
>>       The following data is recommended if available and can be provided
>>       through:
>>
>> Should this be RECOMMENDED?
>>
>> KM: FIXED.  Thanks!
>>
>> 23) s6.1.1: SHA-1 :( Is there anyway you can point to 1.1?  RFC 6194
>> suggests strongly considering another hash alg.  Note that it also
>> suggests pointing to RFC 6194 if you're specifying SHA-1.  THis should
>> probably be in the security considerations.
>>
>> KM:     Updating the examples to use another algorithm would take care of this issue.  Let me see what I can do here... this should not be a hard fix as long as I can generate the examples.  I have different tools now, so I just need to figure out what I need to do this.  This is the only place SHA-1 shows up, do you want to see a statement in the security considerations section explaining that SHA-1 should not be used, pointing to RFC 6194 if this reference is removed?
>>
>> 24) s7: I didn't validate the schema - let me know what tool you used ;)
>>
>>
>> KM:     Developed in XMLSpy
>>           Recently validated in several tools, one was
>>           http://www.w3.org/2001/03/webdata/xsv
>>
>>           We (I had colleagues help confirm in addition to WG chair validation) did run into an issue with XMLDigSig validating because of slow responses to their web server.  This was confirmed to be the issue, no problems now.
>>
>> 25) s12.1: Is the June 2008 version considered stable enough to be a
>> normative reference?  It's not a W3c recommendation yet.  I think this
>> would need to be called out as a DOWNREF.  You got away with it in 6045
>> because that RFC was informational.  If you're going to have this
>> DOWNREF is there any reason to point to v1 of XMLDsig at all?
>>
>> KM:     The link out of RFC6045-bis says it became a W3C recommendation 10 June 2008.  This is the latest version.  They also provide information on 10 implementations and interoperability testing: http://www.w3.org/TR/xmldsig-core/
>>
>>
>> 26) s8.1: need a reference for the NTP timestamp.
>>
>> KM:     This is in IODEF, using the DateTime element of the RecordItem class which references RFC3339.  I changed the text to make sure this is clear as follows:
>>
>> If an Investigation or TraceRequest does not include a RecordItem entry, a timestamp MUST be used to ensure there is data to be signed for the multi-hop authentication use case.  The DateTime element of the IODEF RecordItem class, [RFC5070] Section 3.19.1, is used for this purpose.
>>
>> 27) s8.1: Could throw in a reference to [RFC3647] for certificate policy
>> and certification practices in this sentence:
>>
>>     The method used SHOULD adhere to any
>>     certificate policy and practices agreements between entities
>>     for the use of RID.
>>
>> I guess I see there's a reference later.
>>
>> KM:     Since it the reference does not come up for a while, I added here - the first place a CP and CPS are mentioned.
>>
>> 28) s8.3, s.8.4, s8.5: There seems to be some duplication amongst these
>> sections.  If s8.3 is about TCP then all you need is the first
>> paragraph.  The other two paragraphs are repeated later (or could be
>> moved to s8.2).  And, shoudn't this section then be called "Transport
>> Protocol" being that TCP is about transport?  And you're not talking
>> about security of TCP like TCP-AO so maybe drop the Integrity and
>> Authentication?  s8.4 is about dedicated connections but then seems to
>> repeat some text from s8.3.  s8.5 is about the Authentication of RID
>> but then it talks about TLS.  Couldn't you just have one section that
>> talked about PKIs and point all the sections there?
>>
>> KM: Need to fix this one still.
>>
>> 29) s8.3: Need a reference to BEEP.
>>
>> KM: Added reference to RFC3080, informative.
>>
>> 30) s8.3: Note using the RIR's PKI, which they're using for SIDR, would
>> be require a pretty big change to their CP.
>>
>> KM: Thank you for the heads up.  This was just meant as an example...
>>
>> 31) s8.3: I think approved could be removed from the following (also
>> ARIN is an RIR):
>>
>> OLD:
>>
>>     the American Registry for Internet
>>     Numbers (ARIN) and the Regional Internet Registry's (RIR's) PKI
>>     hierarchy, vendor issued certificates, or approved issuers of
>>     Extended Validation (EV) Certificates.
>>
>> NEW:
>>
>>     the Regional Internet Registry's (RIR's) PKI
>>     hierarchy, vendor issued certificates, or Extended
>>     Validation (EV) certificate issuers.
>>
>> KM: DONE, thanks.
>>
>> 32) s8.4: Contains the following:
>>
>>     In order to address the integrity and authenticity of messages,
>>     transport encryption MUST be used to secure the traffic sent between
>>     RID systems.
>>
>> Are you saying encryption is providing integrity and authentication of
>> messages?  I just think this needs to be reworded.
>>
>> KM: No this paragraph is talking about the Transport covered in RFC6046-bis or other possible transports.  I think about this more with reworking section 8.
>>
>> 33) s8.4: Wouldn't a better name for this section be "Dedicated
>> Connections" or something like that?  It talks about having a dedicated
>> connection and how good that is.  Move the 2nd and 3rd paragraphs to s8.2?
>>
>> KM: I'll look at this as well with the changes to section 8.
>>
>> 34) I went all googlie-eyed in s8.4-8.5.  So I might have more but don't
>> wait on them.
>>
>> KM: Please let me know if you do have comments.  This came up as a solution to a problem pointed out by Randy Bush, I believe... a long time ago.  I did update it recently.
>>
>> 35) s8.6: maybe rephrase one of the bullets:
>>
>> OLD:
>>
>>     o  A PKI and policy to provide authentication, integrity, and
>>          privacy.
>>
>> NEW:
>>
>>     o A PKI, certificate policy, and certification practice statement
>>       to provide authentication, integrity, and privacy.
>>
>> KM: DONE, thanks.
>>
>> 36) s8.6: what does this sentence mean:
>>
>>     The PKI may be a subordinate CA or in
>>     the CA hierarchy from the SP's consortium to establish the trust
>>     relationships necessary as the request is made to other connected
>>     networks.
>>
>> If you don't need it I'd just remove it.
>>
>> KM: Removed.
>>
>> 37) s8.7: Expand IDSs.
>>
>> KM: added on first occurrence of IDSs
>>
>> 38) s8.7: contains:
>>
>>       o  Customers MUST know
>>
>> That's a pretty tall order, maybe all that's really needed is that they
>> be informed:
>>
>>       o  Customers MUST be informed of
>>
>> same for the next bullet?
>>
>> KM: DONE: Updated.
>>
>> 39) s9: should the availability be replaced by authentication?
>>            r/Authenticated encrypted/Protected
>>            r/of the document contents./of the document contents at the
>>              application layer.
>>
>> OLD:
>>
>>     Trust relationships are based on consortiums and established trust
>>     relationships of public key infrastructure (PKI) cross-certifications
>>     of consortiums.
>>
>> NEW:
>>
>>     Trust relationships are based on public key infrastructure (PKI).
>>
>> KM: DONE.
>>
>> If you've got a requirement in this section then it's a normative
>> section.  THere's one SHOULD here.
>>
>> KM: DONE.  When I rework section 8, I can try moving this into that section if it makes sense to keep this informative.
>>
>> spt
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>>
>>
>
>

From turners@ieca.com  Tue Dec 13 06:35:51 2011
Return-Path: <turners@ieca.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 8037D21F8B14 for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.97
X-Spam-Level: 
X-Spam-Status: No, score=-101.97 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ubfg-N+z8RRA for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 06:35:50 -0800 (PST)
Received: from gateway11.websitewelcome.com (gateway11.websitewelcome.com [67.18.22.71]) by ietfa.amsl.com (Postfix) with ESMTP id B7AF621F8B12 for <mile@ietf.org>; Tue, 13 Dec 2011 06:35:50 -0800 (PST)
Received: by gateway11.websitewelcome.com (Postfix, from userid 5011) id 803D775F859F1; Tue, 13 Dec 2011 07:42:55 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway11.websitewelcome.com (Postfix) with ESMTP id 6DE5975F859B3 for <mile@ietf.org>; Tue, 13 Dec 2011 07:42:55 -0600 (CST)
Received: from [96.231.118.183] (port=33543 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RaSdD-0007pG-2P; Tue, 13 Dec 2011 07:42:55 -0600
Message-ID: <4EE7565D.3050309@ieca.com>
Date: Tue, 13 Dec 2011 08:42:53 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "<kathleen.moriarty@emc.com>" <kathleen.moriarty@emc.com>
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com> <0C14A263-CA54-4E7B-B1BB-C322A2B7250C@tik.ee.ethz.ch>
In-Reply-To: <0C14A263-CA54-4E7B-B1BB-C322A2B7250C@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-96-231-118-183.washdc.east.verizon.net (thunderfish.local) [96.231.118.183]:33543
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 7
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 14:35:51 -0000

On 12/13/11 12:03 AM, Brian Trammell wrote:
> Hi, Kathleen, Sean,
>
> One point inline, below,
>
> Cheers,
>
> Brian (6046 author hat)
>
> On Dec 13, 2011, at 4:00 AM,<kathleen.moriarty@emc.com>  <kathleen.moriarty@emc.com>  wrote:
>
>> 11) s3: Is it worth adding an informative reference to RFC 6302 in the
>> last paragraph?  It's a BCP for internet facing server logging
>> recommendations?
>>
>> KM: I think this is more appropriate for RFC6046-bis since it deals with the IP addresses, port numbers, etc. for logging based on Internet facing hosts.  Let me know if you think otherwise?
>
> I agree -- I believe this should be referenced from 6046.

That'd work for me.

spt

From trammell@tik.ee.ethz.ch  Tue Dec 13 07:09:40 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 8E50121F8AFC for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 07:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YQakzMJMUuKN for <mile@ietfa.amsl.com>; Tue, 13 Dec 2011 07:09:40 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED1D21F8AFB for <mile@ietf.org>; Tue, 13 Dec 2011 07:09:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 282FFD9303 for <mile@ietf.org>; Tue, 13 Dec 2011 16:09:37 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AGbl4dEDdnSl for <mile@ietf.org>; Tue, 13 Dec 2011 16:09:37 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id F10CFD9302 for <mile@ietf.org>; Tue, 13 Dec 2011 16:09:36 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Dec 2011 16:09:36 +0100
References: <3B809256-030C-4B31-891A-F43BB39F79CD@tik.ee.ethz.ch>
To: mile@ietf.org
Message-Id: <1AE83A7B-9E7C-4B35-9006-EFC1D54353FC@tik.ee.ethz.ch>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [mile] Matching requests and responses during RID callback
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 15:09:40 -0000

Greetings, all,

One last 6046 issue, I promise.

While considering the answer to one of the appsdir questions with =
respect to matching a request to a response during RID callback, I =
remember thinking when 6046 was initially written, that the =
RIDPolicy/IncidentID element should be used to match a callback response =
to the request that generated it.

However, it's become clear that this is not sufficient; first, =
RIDPolicy/IncidentID is optional; second, it is not guaranteed to be =
unique to a RID message (consider multiple messages sent regarding the =
same incident, all receiving callbacks).

Since this issue only arises during callback, I believe this makes more =
sense to handle with an entity header in 6046, as opposed to adding =
content to the RID message itself. This entity header would be generated =
by the receiving RID system on the 200 Accepted HTTP response to the =
request generating the callback, and also added to the HTTP Request =
containing the callback reply. I presume 'RID-Callback-ID:' would be a =
reasonable name for this entity header.

Thoughts?

Cheers,

Brian (author hat)

> On Dec 13, 2011, at 6:00 AM, <kathleen.moriarty@emc.com> wrote:
>=20
>> Are you pulling another all-nighter?!?!?  Wow, it is even late for me =
here... or are you waking up?
>>=20
>> I hope you get some sleep!!!
>>=20
>> Take care,
>> Kathleen=20
>>=20
>> -----Original Message-----
>> From: Brian Trammell [mailto:trammell@tik.ee.ethz.ch]=20
>> Sent: Monday, December 12, 2011 11:57 PM
>> To: Moriarty, Kathleen
>> Cc: inacio@cert.org; mile@ietf.org
>> Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 =
December 2011
>>=20
>> Hi, Kathleen, Chris,
>>=20
>> Sounds good to me.
>>=20
>> Brian (author hat)
>>=20
>> On Dec 13, 2011, at 5:47 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:
>>=20
>>> Hello Chris,
>>>=20
>>> HTTPS is not intended to be the exclusive transport of RID.  I am =
fine with the document name change, any opinions/objections?
>>>=20
>>> Thank you,
>>> Kathleen (as WG chair)
>>>=20
>>> -----Original Message-----
>>> From: Chris Inacio [mailto:inacio@cert.org]=20
>>> Sent: Monday, December 12, 2011 11:18 PM
>>> To: Moriarty, Kathleen
>>> Cc: trammell@tik.ee.ethz.ch; mile@ietf.org
>>> Subject: Re: [mile] WGLC on draft-ietf-mile-rfc6046-bis-01 to 5 =
December 2011
>>>=20
>>> I would really like the title to be changed to=20
>>>=20
>>> "Transport of Real-time Inter-network Defense (RID) Messages over =
HTTPS"
>>>=20
>>> unless we intend for HTTPS to be the exclusive transport of RID.
>>>=20
>>>=20
>>> Chris
>>>=20
>>>=20
>>>=20
>>> On Nov 21, 2011, at 9:01 AM, <kathleen.moriarty@emc.com> =
<kathleen.moriarty@emc.com> wrote:
>>>=20
>>>> Hello,
>>>>=20
>>>> I'd like to start a two-week working group last call (WGLC) on the =
RFC6046-bis document (draft-ietf-mile-rfc6046-bis-01).
>>>>=20
>>>> Please make your comments on the document to the mile@ietf.org list =
by 5 December 2011. The more reviews, the better, so please take time to =
read the document if you've not done so yet.
>>>>=20
>>>> Many thanks, and best regards,
>>>>=20
>>>> Kathleen (as chair of the MILE WG)
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> mile mailing list
>>>> mile@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>=20
>=20


From internet-drafts@ietf.org  Thu Dec 15 16:42:08 2011
Return-Path: <internet-drafts@ietf.org>
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 1C25B11E80C5; Thu, 15 Dec 2011 16:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWKkgAXKn8vI; Thu, 15 Dec 2011 16:42:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAFE611E80BC; Thu, 15 Dec 2011 16:42:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111216004207.22941.32306.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2011 16:42:07 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 00:42:08 -0000

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

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-04.txt
	Pages           : 73
	Date            : 2011-12-15

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt


From kathleen.moriarty@emc.com  Thu Dec 15 16:48:07 2011
Return-Path: <kathleen.moriarty@emc.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 0A4DD21F877F for <mile@ietfa.amsl.com>; Thu, 15 Dec 2011 16:48:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.441
X-Spam-Level: 
X-Spam-Status: No, score=-6.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6-G-N8BMcGY for <mile@ietfa.amsl.com>; Thu, 15 Dec 2011 16:48:06 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3673021F86EC for <mile@ietf.org>; Thu, 15 Dec 2011 16:48:05 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBG0m12H002528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 15 Dec 2011 19:48:03 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 15 Dec 2011 19:47:49 -0500
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBG0lmSJ002084 for <mile@ietf.org>; Thu, 15 Dec 2011 19:47:48 -0500
Received: from mx06a.corp.emc.com ([169.254.1.238]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Thu, 15 Dec 2011 19:47:48 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Thu, 15 Dec 2011 19:47:47 -0500
Thread-Topic: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
Thread-Index: Acy7i7GMNgIpNt8LS8qdShJkdguIcQAAAfDg
Message-ID: <AE31510960917D478171C79369B660FA0E1A8CA0C5@MX06A.corp.emc.com>
References: <20111216004207.22941.32306.idtracker@ietfa.amsl.com>
In-Reply-To: <20111216004207.22941.32306.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 00:48:07 -0000

Hello,

The updated version includes many of the recommended changes, the following=
 are still pending:

The schema and examples MAY need to be updated depending on the final decis=
ion as to whether or not RID should envelope IODEF (looking like that will =
be the answer, unless there is a reason to keep as is).

The examples need to be updated to use something other than SHA-1 for the d=
igital signatures.

The Normative and Informative section includes 2 options for text.  I was n=
ot 100% sure what this will wind up as, so both are included for comparison=
 & discussion.

Thank you,
Kathleen (as editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of int=
ernet-drafts@ietf.org
Sent: Thursday, December 15, 2011 7:42 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt


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

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-04.txt
	Pages           : 73
	Date            : 2011-12-15

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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


From trammell@tik.ee.ethz.ch  Mon Dec 19 14:12:45 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 3CB7D21F84DD for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 14:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id duJcg4O0zrbs for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 14:12:44 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id EEBC521F84DB for <mile@ietf.org>; Mon, 19 Dec 2011 14:12:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 19E4DD9309; Mon, 19 Dec 2011 23:12:39 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3sduE3DZRJgk; Mon, 19 Dec 2011 23:12:38 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id AA421D9304; Mon, 19 Dec 2011 23:12:38 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <4EE7565D.3050309@ieca.com>
Date: Mon, 19 Dec 2011 23:12:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C86E482-546D-462A-9487-B6F42DEF5333@tik.ee.ethz.ch>
References: <4EE52CDE.60306@ieca.com> <AE31510960917D478171C79369B660FA0E1A8C9901@MX06A.corp.emc.com> <0C14A263-CA54-4E7B-B1BB-C322A2B7250C@tik.ee.ethz.ch> <4EE7565D.3050309@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] AD review of draft-ietf-mile-rfc6045-bis
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 22:12:45 -0000

Hi, Sean, all,

On review, I'm not sure recommending 6302-style logging is appropriate =
in 6046-bis, as the specification as written is essentially NAT-hostile. =
Specifically, RID has no mechanism for supporting callbacks other than =
to tcp/4590 on the network-layer address from which the original request =
came. Given the nature of RID systems within the consortium, I don't =
necessarily think this is a bad thing (feelings on =
PNAT-as-transition-mechanism aside): RID is basically a server-to-server =
protocol, and the servers need to have well known endpoints for identity =
verification.

So, from the point of view of a RID system, the peer RID system should =
always have the same address, anyway, which solves the same problem 6302 =
does.

Cheers,

Brian (author hat)


On Dec 13, 2011, at 2:42 PM, Sean Turner wrote:

> On 12/13/11 12:03 AM, Brian Trammell wrote:
>> Hi, Kathleen, Sean,
>>=20
>> One point inline, below,
>>=20
>> Cheers,
>>=20
>> Brian (6046 author hat)
>>=20
>> On Dec 13, 2011, at 4:00 AM,<kathleen.moriarty@emc.com>  =
<kathleen.moriarty@emc.com>  wrote:
>>=20
>>> 11) s3: Is it worth adding an informative reference to RFC 6302 in =
the
>>> last paragraph?  It's a BCP for internet facing server logging
>>> recommendations?
>>>=20
>>> KM: I think this is more appropriate for RFC6046-bis since it deals =
with the IP addresses, port numbers, etc. for logging based on Internet =
facing hosts.  Let me know if you think otherwise?
>>=20
>> I agree -- I believe this should be referenced from 6046.
>=20
> That'd work for me.
>=20
> spt
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From internet-drafts@ietf.org  Mon Dec 19 14:37:06 2011
Return-Path: <internet-drafts@ietf.org>
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 3CC2F11E80B4; Mon, 19 Dec 2011 14:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDdsYF3O-LNE; Mon, 19 Dec 2011 14:37:05 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 167BE21F84BB; Mon, 19 Dec 2011 14:37:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219223704.24164.38769.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 14:37:04 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 22:37:06 -0000

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

	Title           : Transport of Real-time Inter-network Defense (RID) Messa=
ges over HTTP/ TLS
	Author(s)       : Brian Trammell
	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
	Pages           : 8
	Date            : 2011-12-19

   The Incident Object Description Exchange Format (IODEF) defines a
   common XML format for document exchange, and Realtime Internetwork
   Defense (RID) defines extensions to IODEF intended for the
   cooperative handling of security incidents within consortia of
   network operators and enterprises.  This document specifies a
   transport protocol for RID based upon the passing of RID messages
   over HTTP/TLS.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt


From trammell@tik.ee.ethz.ch  Mon Dec 19 14:41:17 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 98F5011E80B1 for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 14:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1x8vtqfQDL5j for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 14:41:16 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 7368311E8080 for <mile@ietf.org>; Mon, 19 Dec 2011 14:41:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id A50BED9304 for <mile@ietf.org>; Mon, 19 Dec 2011 23:41:14 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8FozPJDFO8Im for <mile@ietf.org>; Mon, 19 Dec 2011 23:41:14 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 674BBD9303 for <mile@ietf.org>; Mon, 19 Dec 2011 23:41:14 +0100 (MET)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Dec 2011 23:41:13 +0100
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com>
To: mile@ietf.org
Message-Id: <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 22:41:17 -0000

Greetings, all,

rfc6046-bis-04 is now available, and (I believe) addresses all comments =
to date, including those in the AD and appsarea reviews.=20

Seeing no further discussion on the two open points, I've decided in =
this version to follow SM's "lightweight" suggestion for normative =
section language, and the last comment in the TLS version thread (MUST =
1.1, SHOULD 1.2); please comment if you have a strong objection to =
either of these.

Best regards,

Brian (as author of 6046-bis)

Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: December 19, 2011 11:37:04 PM GMT+01:00
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>=20
>=20
> 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 Working Group of the IETF.
>=20
> 	Title           : Transport of Real-time Inter-network Defense =
(RID) Messages over HTTP/ TLS
> 	Author(s)       : Brian Trammell
> 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
> 	Pages           : 8
> 	Date            : 2011-12-19
>=20
>   The Incident Object Description Exchange Format (IODEF) defines a
>   common XML format for document exchange, and Realtime Internetwork
>   Defense (RID) defines extensions to IODEF intended for the
>   cooperative handling of security incidents within consortia of
>   network operators and enterprises.  This document specifies a
>   transport protocol for RID based upon the passing of RID messages
>   over HTTP/TLS.
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From david.black@emc.com  Mon Dec 19 15:31:27 2011
Return-Path: <david.black@emc.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 770DF11E80B1 for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 15:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psLIkrAK9F+H for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 15:31:26 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B999B11E80B0 for <mile@ietf.org>; Mon, 19 Dec 2011 15:31:26 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBJNVPQH026623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Dec 2011 18:31:25 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.226]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 19 Dec 2011 18:31:06 -0500
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBJNV5DN030599; Mon, 19 Dec 2011 18:31:06 -0500
Received: from mx14a.corp.emc.com ([169.254.1.216]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Mon, 19 Dec 2011 18:31:05 -0500
From: <david.black@emc.com>
To: <trammell@tik.ee.ethz.ch>, <mile@ietf.org>
Date: Mon, 19 Dec 2011 18:31:04 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
Thread-Index: Acy+n85oAW71v29YTGqfXUwVD9d+bAAAq+eg
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch>
In-Reply-To: <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 23:31:27 -0000

Hello Brian,

I think this may have been written slightly too quickly:

   RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
   use TLS version 1.2 or higher, with mutual authentication for
   transport confidentiality, identification, and authentication, as in
   [RFC2818]. =20

I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at the
same time, and I don't see a mandatory-to-implement requirement.  Also,
[RFC5246] is TLS 1.2.  I suggest the following (two sentences for clarity):=
=20

   RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
   authentication for transport confidentiality, identification, and
   authentication, as in [RFC2818].  RID systems MUST support TLS
   version 1.1 and SHOULD support TLS version 1.2 [RFC5246].

The remaining text in that paragraph is fine:

   The session MUST use non-NULL ciphersuites for
   authentication, integrity, and confidentiality; sessions MAY be
   renegotiated within these constraints.  Although TLS implementations
   typically support the older SSL protocol, a RID peer MUST NOT
   request, offer, or use any version of SSL, or any version of TLS
   prior to 1.1, due to known security vulnerabilities in prior versions
   of the protocol; see Appendix E of [RFC5246] for more.

As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already specifies that
preference as a SHOULD (client_version in ClientHello message, and required
server response), so that preference does not need to be repeated here.  =20

Thanks,
--David


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of B=
rian Trammell
> Sent: Monday, December 19, 2011 5:41 PM
> To: mile@ietf.org
> Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>=20
> Greetings, all,
>=20
> rfc6046-bis-04 is now available, and (I believe) addresses all comments t=
o date, including those in
> the AD and appsarea reviews.
>=20
> Seeing no further discussion on the two open points, I've decided in this=
 version to follow SM's
> "lightweight" suggestion for normative section language, and the last com=
ment in the TLS version
> thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong object=
ion to either of these.
>=20
> Best regards,
>=20
> Brian (as author of 6046-bis)
>=20
> Begin forwarded message:
>=20
> > From: internet-drafts@ietf.org
> > Date: December 19, 2011 11:37:04 PM GMT+01:00
> > To: i-d-announce@ietf.org
> > Cc: mile@ietf.org
> > Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories. This draft is a work
> item of the Managed Incident Lightweight Exchange Working Group of the IE=
TF.
> >
> > 	Title           : Transport of Real-time Inter-network Defense (RID) M=
essages over HTTP/ TLS
> > 	Author(s)       : Brian Trammell
> > 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
> > 	Pages           : 8
> > 	Date            : 2011-12-19
> >
> >   The Incident Object Description Exchange Format (IODEF) defines a
> >   common XML format for document exchange, and Realtime Internetwork
> >   Defense (RID) defines extensions to IODEF intended for the
> >   cooperative handling of security incidents within consortia of
> >   network operators and enterprises.  This document specifies a
> >   transport protocol for RID based upon the passing of RID messages
> >   over HTTP/TLS.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From trammell@tik.ee.ethz.ch  Mon Dec 19 22:46:00 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 9291E11E80CA for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 22:46:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RZ23tczWmH59 for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 22:45:59 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 65A0611E809D for <mile@ietf.org>; Mon, 19 Dec 2011 22:45:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 8D0F5D9304; Tue, 20 Dec 2011 07:45:43 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AGygPpiuDcf5; Tue, 20 Dec 2011 07:45:43 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 3DC58D9303; Tue, 20 Dec 2011 07:45:43 +0100 (MET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com>
Date: Tue, 20 Dec 2011 07:45:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B2F94D1-B7EC-4A06-86E7-F362571434EE@tik.ee.ethz.ch>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com>
To: <david.black@emc.com> <david.black@emc.com>
X-Mailer: Apple Mail (2.1084)
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 06:46:00 -0000

Hi, David, all,

Thanks; yes, the new language is clearer, and better captures the intent =
of what I was trying to say. Will add to an -05 revision.

Best regards,

Brian (author hat)

On Dec 20, 2011, at 12:31 AM, <david.black@emc.com> =
<david.black@emc.com> wrote:

> Hello Brian,
>=20
> I think this may have been written slightly too quickly:
>=20
>   RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
>   use TLS version 1.2 or higher, with mutual authentication for
>   transport confidentiality, identification, and authentication, as in
>   [RFC2818]. =20
>=20
> I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at =
the
> same time, and I don't see a mandatory-to-implement requirement.  =
Also,
> [RFC5246] is TLS 1.2.  I suggest the following (two sentences for =
clarity):=20
>=20
>   RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
>   authentication for transport confidentiality, identification, and
>   authentication, as in [RFC2818].  RID systems MUST support TLS
>   version 1.1 and SHOULD support TLS version 1.2 [RFC5246].
>=20
> The remaining text in that paragraph is fine:
>=20
>   The session MUST use non-NULL ciphersuites for
>   authentication, integrity, and confidentiality; sessions MAY be
>   renegotiated within these constraints.  Although TLS implementations
>   typically support the older SSL protocol, a RID peer MUST NOT
>   request, offer, or use any version of SSL, or any version of TLS
>   prior to 1.1, due to known security vulnerabilities in prior =
versions
>   of the protocol; see Appendix E of [RFC5246] for more.
>=20
> As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already specifies =
that
> preference as a SHOULD (client_version in ClientHello message, and =
required
> server response), so that preference does not need to be repeated =
here.  =20
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Brian Trammell
>> Sent: Monday, December 19, 2011 5:41 PM
>> To: mile@ietf.org
>> Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>=20
>> Greetings, all,
>>=20
>> rfc6046-bis-04 is now available, and (I believe) addresses all =
comments to date, including those in
>> the AD and appsarea reviews.
>>=20
>> Seeing no further discussion on the two open points, I've decided in =
this version to follow SM's
>> "lightweight" suggestion for normative section language, and the last =
comment in the TLS version
>> thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong =
objection to either of these.
>>=20
>> Best regards,
>>=20
>> Brian (as author of 6046-bis)
>>=20
>> Begin forwarded message:
>>=20
>>> From: internet-drafts@ietf.org
>>> Date: December 19, 2011 11:37:04 PM GMT+01:00
>>> To: i-d-announce@ietf.org
>>> Cc: mile@ietf.org
>>> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>>=20
>>>=20
>>> 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 Working Group of =
the IETF.
>>>=20
>>> 	Title           : Transport of Real-time Inter-network Defense =
(RID) Messages over HTTP/ TLS
>>> 	Author(s)       : Brian Trammell
>>> 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
>>> 	Pages           : 8
>>> 	Date            : 2011-12-19
>>>=20
>>>  The Incident Object Description Exchange Format (IODEF) defines a
>>>  common XML format for document exchange, and Realtime Internetwork
>>>  Defense (RID) defines extensions to IODEF intended for the
>>>  cooperative handling of security incidents within consortia of
>>>  network operators and enterprises.  This document specifies a
>>>  transport protocol for RID based upon the passing of RID messages
>>>  over HTTP/TLS.
>>>=20
>>>=20
>>> A URL for this Internet-Draft is:
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> This Internet-Draft can be retrieved at:
>>> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>>=20
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile


From trammell@tik.ee.ethz.ch  Mon Dec 19 22:48:06 2011
Return-Path: <trammell@tik.ee.ethz.ch>
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 7A38611E80CB for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 22:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yko16WWAzhXO for <mile@ietfa.amsl.com>; Mon, 19 Dec 2011 22:48:05 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 79B9311E80CA for <mile@ietf.org>; Mon, 19 Dec 2011 22:48:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id D0343D9304; Tue, 20 Dec 2011 07:48:04 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9jn5fMXSunKD; Tue, 20 Dec 2011 07:48:04 +0100 (MET)
Received: from [10.0.1.2] (cust-integra-121-161.antanet.ch [80.75.121.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 7B35CD9303; Tue, 20 Dec 2011 07:48:04 +0100 (MET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <1B2F94D1-B7EC-4A06-86E7-F362571434EE@tik.ee.ethz.ch>
Date: Tue, 20 Dec 2011 07:48:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DF32A33-90B7-4DEF-92CD-EE2B03CC698B@tik.ee.ethz.ch>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com> <1B2F94D1-B7EC-4A06-86E7-F362571434EE@tik.ee.ethz.ch>
To: "david.black@emc.com> <david.black@emc.com" <david.black@emc.com>, mile@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 06:48:06 -0000

Hi, David, all,

Except... referencing 4346 like this would lead to a downref, since it's =
obsoleted by 5246. Isn't the right thing to do here to use 5246 as the =
reference for 1.1 as well?

Cheers,

Brian (author hat)

On Dec 20, 2011, at 7:45 AM, Brian Trammell wrote:

> Hi, David, all,
>=20
> Thanks; yes, the new language is clearer, and better captures the =
intent of what I was trying to say. Will add to an -05 revision.
>=20
> Best regards,
>=20
> Brian (author hat)
>=20
> On Dec 20, 2011, at 12:31 AM, <david.black@emc.com> =
<david.black@emc.com> wrote:
>=20
>> Hello Brian,
>>=20
>> I think this may have been written slightly too quickly:
>>=20
>>  RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
>>  use TLS version 1.2 or higher, with mutual authentication for
>>  transport confidentiality, identification, and authentication, as in
>>  [RFC2818]. =20
>>=20
>> I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at =
the
>> same time, and I don't see a mandatory-to-implement requirement.  =
Also,
>> [RFC5246] is TLS 1.2.  I suggest the following (two sentences for =
clarity):=20
>>=20
>>  RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
>>  authentication for transport confidentiality, identification, and
>>  authentication, as in [RFC2818].  RID systems MUST support TLS
>>  version 1.1 and SHOULD support TLS version 1.2 [RFC5246].
>>=20
>> The remaining text in that paragraph is fine:
>>=20
>>  The session MUST use non-NULL ciphersuites for
>>  authentication, integrity, and confidentiality; sessions MAY be
>>  renegotiated within these constraints.  Although TLS implementations
>>  typically support the older SSL protocol, a RID peer MUST NOT
>>  request, offer, or use any version of SSL, or any version of TLS
>>  prior to 1.1, due to known security vulnerabilities in prior =
versions
>>  of the protocol; see Appendix E of [RFC5246] for more.
>>=20
>> As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already =
specifies that
>> preference as a SHOULD (client_version in ClientHello message, and =
required
>> server response), so that preference does not need to be repeated =
here.  =20
>>=20
>> Thanks,
>> --David
>>=20
>>=20
>>> -----Original Message-----
>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf =
Of Brian Trammell
>>> Sent: Monday, December 19, 2011 5:41 PM
>>> To: mile@ietf.org
>>> Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>>=20
>>> Greetings, all,
>>>=20
>>> rfc6046-bis-04 is now available, and (I believe) addresses all =
comments to date, including those in
>>> the AD and appsarea reviews.
>>>=20
>>> Seeing no further discussion on the two open points, I've decided in =
this version to follow SM's
>>> "lightweight" suggestion for normative section language, and the =
last comment in the TLS version
>>> thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong =
objection to either of these.
>>>=20
>>> Best regards,
>>>=20
>>> Brian (as author of 6046-bis)
>>>=20
>>> Begin forwarded message:
>>>=20
>>>> From: internet-drafts@ietf.org
>>>> Date: December 19, 2011 11:37:04 PM GMT+01:00
>>>> To: i-d-announce@ietf.org
>>>> Cc: mile@ietf.org
>>>> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>>>=20
>>>>=20
>>>> 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 Working Group of =
the IETF.
>>>>=20
>>>> 	Title           : Transport of Real-time Inter-network Defense =
(RID) Messages over HTTP/ TLS
>>>> 	Author(s)       : Brian Trammell
>>>> 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
>>>> 	Pages           : 8
>>>> 	Date            : 2011-12-19
>>>>=20
>>>> The Incident Object Description Exchange Format (IODEF) defines a
>>>> common XML format for document exchange, and Realtime Internetwork
>>>> Defense (RID) defines extensions to IODEF intended for the
>>>> cooperative handling of security incidents within consortia of
>>>> network operators and enterprises.  This document specifies a
>>>> transport protocol for RID based upon the passing of RID messages
>>>> over HTTP/TLS.
>>>>=20
>>>>=20
>>>> A URL for this Internet-Draft is:
>>>> =
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>>=20
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>=20
>>>> This Internet-Draft can be retrieved at:
>>>> =
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>>=20
>>>> _______________________________________________
>>>> mile mailing list
>>>> mile@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mile
>>>=20
>>> _______________________________________________
>>> mile mailing list
>>> mile@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Tue Dec 20 06:26:05 2011
Return-Path: <kathleen.moriarty@emc.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 B4B4821F8B09 for <mile@ietfa.amsl.com>; Tue, 20 Dec 2011 06:26:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bnD29vulA9G for <mile@ietfa.amsl.com>; Tue, 20 Dec 2011 06:26:04 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 978E821F8B06 for <mile@ietf.org>; Tue, 20 Dec 2011 06:26:04 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBKEQ3Qe032621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2011 09:26:03 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Tue, 20 Dec 2011 09:25:52 -0500
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBKEPp0b010692; Tue, 20 Dec 2011 09:25:52 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub36.corp.emc.com ([::1]) with mapi; Tue, 20 Dec 2011 09:25:51 -0500
From: <kathleen.moriarty@emc.com>
To: <david.black@emc.com>, <trammell@tik.ee.ethz.ch>, <mile@ietf.org>
Date: Tue, 20 Dec 2011 09:25:50 -0500
Thread-Topic: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
Thread-Index: Acy+n85oAW71v29YTGqfXUwVD9d+bAAAq+egACAkSTA=
Message-ID: <AE31510960917D478171C79369B660FA0E2A66E7F2@MX06A.corp.emc.com>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 14:26:05 -0000

Someone lurking (it does help if you post directly) on the list agreed with=
 the current assessment and stated:


http://www.isg.rhul.ac.uk/~kp/mee-comp.pdf

for confirmation that the record protocol in TLS 1.1 and 1.2 does indeed do=
 a better job than in TLS 1.0 (assuming we avoid short MACs).

AND:

The problem with mandating TLS 1.2 is that it is not yet widely supported i=
n clients or servers. One might hope that, with the recent BEAST attack on =
TLS 1.0, there would now be a push towards adopting TLS 1.1 and TLS 1.2. Bu=
t this does not seem to be the case; instead, vendors seem instead to be ad=
ding ad hoc countermeasures to their existing TLS 1.0 implementations.

So if you want to see rapid adoption of MILE, you probably don't want to ma=
ndate TLS 1.2 only; on the other hand, it's definitely an improvement on TL=
S 1.0. Probably requiring (TLS 1.1 OR TLS 1.2) is a reasonable compromise -=
 TLS 1.2 is better than TLS 1.1 mostly because it offers better algorithm a=
gility, but they do offer roughly equal levels of security (when configured=
 in the same way).

Thus I broadly agree with the analysis provided by David Black in your e-ma=
il below.





-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of dav=
id.black@emc.com
Sent: Monday, December 19, 2011 6:31 PM
To: trammell@tik.ee.ethz.ch; mile@ietf.org
Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt

Hello Brian,

I think this may have been written slightly too quickly:

   RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
   use TLS version 1.2 or higher, with mutual authentication for
   transport confidentiality, identification, and authentication, as in
   [RFC2818]. =20

I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at the
same time, and I don't see a mandatory-to-implement requirement.  Also,
[RFC5246] is TLS 1.2.  I suggest the following (two sentences for clarity):=
=20

   RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
   authentication for transport confidentiality, identification, and
   authentication, as in [RFC2818].  RID systems MUST support TLS
   version 1.1 and SHOULD support TLS version 1.2 [RFC5246].

The remaining text in that paragraph is fine:

   The session MUST use non-NULL ciphersuites for
   authentication, integrity, and confidentiality; sessions MAY be
   renegotiated within these constraints.  Although TLS implementations
   typically support the older SSL protocol, a RID peer MUST NOT
   request, offer, or use any version of SSL, or any version of TLS
   prior to 1.1, due to known security vulnerabilities in prior versions
   of the protocol; see Appendix E of [RFC5246] for more.

As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already specifies that
preference as a SHOULD (client_version in ClientHello message, and required
server response), so that preference does not need to be repeated here.  =20

Thanks,
--David


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of B=
rian Trammell
> Sent: Monday, December 19, 2011 5:41 PM
> To: mile@ietf.org
> Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>=20
> Greetings, all,
>=20
> rfc6046-bis-04 is now available, and (I believe) addresses all comments t=
o date, including those in
> the AD and appsarea reviews.
>=20
> Seeing no further discussion on the two open points, I've decided in this=
 version to follow SM's
> "lightweight" suggestion for normative section language, and the last com=
ment in the TLS version
> thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong object=
ion to either of these.
>=20
> Best regards,
>=20
> Brian (as author of 6046-bis)
>=20
> Begin forwarded message:
>=20
> > From: internet-drafts@ietf.org
> > Date: December 19, 2011 11:37:04 PM GMT+01:00
> > To: i-d-announce@ietf.org
> > Cc: mile@ietf.org
> > Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories. This draft is a work
> item of the Managed Incident Lightweight Exchange Working Group of the IE=
TF.
> >
> > 	Title           : Transport of Real-time Inter-network Defense (RID) M=
essages over HTTP/ TLS
> > 	Author(s)       : Brian Trammell
> > 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
> > 	Pages           : 8
> > 	Date            : 2011-12-19
> >
> >   The Incident Object Description Exchange Format (IODEF) defines a
> >   common XML format for document exchange, and Realtime Internetwork
> >   Defense (RID) defines extensions to IODEF intended for the
> >   cooperative handling of security incidents within consortia of
> >   network operators and enterprises.  This document specifies a
> >   transport protocol for RID based upon the passing of RID messages
> >   over HTTP/TLS.
> >
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile

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


From david.black@emc.com  Tue Dec 20 06:49:40 2011
Return-Path: <david.black@emc.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 B6F2521F8ACA for <mile@ietfa.amsl.com>; Tue, 20 Dec 2011 06:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4txmVCwT5dR for <mile@ietfa.amsl.com>; Tue, 20 Dec 2011 06:49:39 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B490221F84A7 for <mile@ietf.org>; Tue, 20 Dec 2011 06:49:39 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBKEnZ4Z000583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Tue, 20 Dec 2011 09:49:37 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Tue, 20 Dec 2011 09:49:19 -0500
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBKEnJYU032746 for <mile@ietf.org>; Tue, 20 Dec 2011 09:49:19 -0500
Received: from mx14a.corp.emc.com ([169.254.1.216]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Tue, 20 Dec 2011 09:49:19 -0500
From: <david.black@emc.com>
To: <kathleen.moriarty@emc.com>, <mile@ietf.org>
Date: Tue, 20 Dec 2011 09:49:18 -0500
Thread-Topic: TLS short MACs and RID
Thread-Index: Acy+n85oAW71v29YTGqfXUwVD9d+bAAAq+egACAkSTAAAGJKgA==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A48114E6@MX14A.corp.emc.com>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com> <AE31510960917D478171C79369B660FA0E2A66E7F2@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E2A66E7F2@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] TLS short MACs and RID
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 14:49:40 -0000

> Someone lurking (it does help if you post directly) on the list agreed wi=
th the current assessment and
> stated:
>=20
> http://www.isg.rhul.ac.uk/~kp/mee-comp.pdf
>=20
> for confirmation that the record protocol in TLS 1.1 and 1.2 does indeed =
do a better job than in TLS
> 1.0 (assuming we avoid short MACs).

Actually, RID doesn't even need to avoid short MACs, because that attack is=
 inapplicable to RID, even if short MACs are used as specified in RFC 6066.=
  The attack involves an relatively new feature of TLS that allows truncati=
on of the integrity HMAC output to 80 bits (the truncated_hmac extension in=
 RFC 6066).  The PDF referenced above states that the attack is inapplicabl=
e when:

                      message length + MAC tag length > cipher block size -=
 8 (all in bits).

For AES, the cipher block size is 128 bits.  Plug in 80 bits for the shorte=
st MAC tag length, and the attack is inapplicable when:

                      message length > 40 bits, i.e., 5 bytes (yes, *5* !).

I believe the shortest RID message is an HTTP 202 Accepted response, which =
is longer than 5 bytes, and by comparison to that, the XML used for RID tra=
nsport of actual incidents is positively verbose ;-).

Nonetheless, the TLS WG should look at this attack.  I also don't see any c=
ompelling reason to use short MACs with RID.

Thanks,
--David

> -----Original Message-----
> From: Moriarty, Kathleen
> Sent: Tuesday, December 20, 2011 9:26 AM
> To: Black, David; trammell@tik.ee.ethz.ch; mile@ietf.org
> Subject: RE: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>=20
> Someone lurking (it does help if you post directly) on the list agreed wi=
th the current assessment and
> stated:
>=20
>=20
> http://www.isg.rhul.ac.uk/~kp/mee-comp.pdf
>=20
> for confirmation that the record protocol in TLS 1.1 and 1.2 does indeed =
do a better job than in TLS
> 1.0 (assuming we avoid short MACs).
>=20
> AND:
>=20
> The problem with mandating TLS 1.2 is that it is not yet widely supported=
 in clients or servers. One
> might hope that, with the recent BEAST attack on TLS 1.0, there would now=
 be a push towards adopting
> TLS 1.1 and TLS 1.2. But this does not seem to be the case; instead, vend=
ors seem instead to be adding
> ad hoc countermeasures to their existing TLS 1.0 implementations.
>=20
> So if you want to see rapid adoption of MILE, you probably don't want to =
mandate TLS 1.2 only; on the
> other hand, it's definitely an improvement on TLS 1.0. Probably requiring=
 (TLS 1.1 OR TLS 1.2) is a
> reasonable compromise - TLS 1.2 is better than TLS 1.1 mostly because it =
offers better algorithm
> agility, but they do offer roughly equal levels of security (when configu=
red in the same way).
>=20
> Thus I broadly agree with the analysis provided by David Black in your e-=
mail below.
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of d=
avid.black@emc.com
> Sent: Monday, December 19, 2011 6:31 PM
> To: trammell@tik.ee.ethz.ch; mile@ietf.org
> Subject: Re: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>=20
> Hello Brian,
>=20
> I think this may have been written slightly too quickly:
>=20
>    RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
>    use TLS version 1.2 or higher, with mutual authentication for
>    transport confidentiality, identification, and authentication, as in
>    [RFC2818].
>=20
> I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at the
> same time, and I don't see a mandatory-to-implement requirement.  Also,
> [RFC5246] is TLS 1.2.  I suggest the following (two sentences for clarity=
):
>=20
>    RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
>    authentication for transport confidentiality, identification, and
>    authentication, as in [RFC2818].  RID systems MUST support TLS
>    version 1.1 and SHOULD support TLS version 1.2 [RFC5246].
>=20
> The remaining text in that paragraph is fine:
>=20
>    The session MUST use non-NULL ciphersuites for
>    authentication, integrity, and confidentiality; sessions MAY be
>    renegotiated within these constraints.  Although TLS implementations
>    typically support the older SSL protocol, a RID peer MUST NOT
>    request, offer, or use any version of SSL, or any version of TLS
>    prior to 1.1, due to known security vulnerabilities in prior versions
>    of the protocol; see Appendix E of [RFC5246] for more.
>=20
> As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already specifies th=
at
> preference as a SHOULD (client_version in ClientHello message, and requir=
ed
> server response), so that preference does not need to be repeated here.
>=20
> Thanks,
> --David
>=20
>=20
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of=
 Brian Trammell
> > Sent: Monday, December 19, 2011 5:41 PM
> > To: mile@ietf.org
> > Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
> >
> > Greetings, all,
> >
> > rfc6046-bis-04 is now available, and (I believe) addresses all comments=
 to date, including those in
> > the AD and appsarea reviews.
> >
> > Seeing no further discussion on the two open points, I've decided in th=
is version to follow SM's
> > "lightweight" suggestion for normative section language, and the last c=
omment in the TLS version
> > thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong obje=
ction to either of these.
> >
> > Best regards,
> >
> > Brian (as author of 6046-bis)
> >
> > Begin forwarded message:
> >
> > > From: internet-drafts@ietf.org
> > > Date: December 19, 2011 11:37:04 PM GMT+01:00
> > > To: i-d-announce@ietf.org
> > > Cc: mile@ietf.org
> > > Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts di=
rectories. This draft is a
> work
> > item of the Managed Incident Lightweight Exchange Working Group of the =
IETF.
> > >
> > > 	Title           : Transport of Real-time Inter-network Defense (RID)=
 Messages over HTTP/ TLS
> > > 	Author(s)       : Brian Trammell
> > > 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
> > > 	Pages           : 8
> > > 	Date            : 2011-12-19
> > >
> > >   The Incident Object Description Exchange Format (IODEF) defines a
> > >   common XML format for document exchange, and Realtime Internetwork
> > >   Defense (RID) defines extensions to IODEF intended for the
> > >   cooperative handling of security incidents within consortia of
> > >   network operators and enterprises.  This document specifies a
> > >   transport protocol for RID based upon the passing of RID messages
> > >   over HTTP/TLS.
> > >
> > >
> > > A URL for this Internet-Draft is:
> > > http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.tx=
t
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > This Internet-Draft can be retrieved at:
> > > ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
> > >
> > > _______________________________________________
> > > mile mailing list
> > > mile@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mile
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Wed Dec 21 20:34:07 2011
Return-Path: <kathleen.moriarty@emc.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 2B1F411E80EE for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7s8xYE4FLlKU for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:34:06 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 873C011E8096 for <mile@ietf.org>; Wed, 21 Dec 2011 20:34:06 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBM4Y5YX019116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 21 Dec 2011 23:34:05 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 21 Dec 2011 23:33:46 -0500
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBM4XkFL012813 for <mile@ietf.org>; Wed, 21 Dec 2011 23:33:46 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub27.corp.emc.com ([10.254.110.183]) with mapi; Wed, 21 Dec 2011 23:33:46 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Wed, 21 Dec 2011 23:33:44 -0500
Thread-Topic: Structured cyber security information extension 
Thread-Index: AczAYuOG4OIrBg7hQ6KIEgaqXC4ZIA==
Message-ID: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] Structured cyber security information extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 04:34:07 -0000

Hello Take,

Thank you for posting the updated draft.

I was looking through the SCI draft and noticed that EM_XML is defined in t=
he UML definition section, but is not used in the defined schema extension =
(xsd).  It looks like the dtype=3Dxml from IODEF sufficiently defines the d=
atatype within the schema, so the EM_XML may not be necessary.  Is there a =
reason why we need to define EM_XML?  Or can the UML representation leverag=
e the iodef dtype=3D"xml" definition for including an XML schema?

Also, I see the use of Record in the SCI extension, is this intended to be =
the same Record as is defined in IODEF as it appears to be a separate defin=
ition?  If it is the same, that is fine.  If it is a separate definition, c=
ould we use another term as not to confuse the two?  It looks like the XML =
schema included is directly in the iodef-sci:Record which is embedded in th=
e Record class from IODEF through RecordItem.

Thank you,
Kathleen

Kathleen M. Moriarty, CISSP | GRC Strategy | Office of the CTO | 617-851-58=
07 | Kathleen.Moriarty@emc.com  | EMC Corporation




From takeshi_takahashi@nict.go.jp  Wed Dec 21 20:52:19 2011
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 3114B21F84C2 for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.755
X-Spam-Level: 
X-Spam-Status: No, score=-0.755 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, J_CHICKENPOX_53=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8b1hYVH1SKjr for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:52:18 -0800 (PST)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A09721F84BD for <mile@ietf.org>; Wed, 21 Dec 2011 20:52:18 -0800 (PST)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id pBM4qDS5029634; Thu, 22 Dec 2011 13:52:13 +0900 (JST)
Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp  with ESMTP id pBM4qD47020723; Thu, 22 Dec 2011 13:52:13 +0900 (JST)
Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp  with ESMTP id pBM4qD7w020720; Thu, 22 Dec 2011 13:52:13 +0900 (JST)
Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 65DD11695F; Thu, 22 Dec 2011 13:52:13 +0900 (JST)
Received: from TakeVAIO (unknown [133.243.119.203]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 5F02E16940; Thu, 22 Dec 2011 13:52:13 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <kathleen.moriarty@emc.com>, <mile@ietf.org>
References: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com>
Date: Thu, 22 Dec 2011 13:52:14 +0900
Message-ID: <000001ccc065$79503030$6bf09090$@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: AQDuYVoBM5U/035LSxXHQddmHFrfCJekBjnw
Content-Language: ja
Subject: Re: [mile] Structured cyber security information extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 04:52:19 -0000

Hello Kathleen,

Thank you for the kind email.

Regarding the EM_XML issue, thank you for the information.
I first thought I cannot use the "xml" value (prepared for dtype) to define
the type of "Record" element.
It seems to be that we can use the "xml" value as the datatype of the
"Record" element.
Thank you for letting me know about that.
I will get rid of the EM_XML declaration from the draft.

Regarding the Record class, I agree.
Thank you for pointing it out here.
Let me change the name into "RawData" to distinguish the Record class of the
IODEF.

I appreciate these kind comments.

Thank you.
Take


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> kathleen.moriarty@emc.com
> Sent: Thursday, December 22, 2011 1:34 PM
> To: mile@ietf.org
> Subject: [mile] Structured cyber security information extension
> 
> Hello Take,
> 
> Thank you for posting the updated draft.
> 
> I was looking through the SCI draft and noticed that EM_XML is defined
> in the UML definition section, but is not used in the defined schema
> extension (xsd).  It looks like the dtype=xml from IODEF sufficiently
> defines the datatype within the schema, so the EM_XML may not be
necessary.
> Is there a reason why we need to define EM_XML?  Or can the UML
> representation leverage the iodef dtype="xml" definition for including
> an XML schema?
> 
> Also, I see the use of Record in the SCI extension, is this intended to
> be the same Record as is defined in IODEF as it appears to be a separate
> definition?  If it is the same, that is fine.  If it is a separate
> definition, could we use another term as not to confuse the two?  It looks
> like the XML schema included is directly in the iodef-sci:Record which
> is embedded in the Record class from IODEF through RecordItem.
> 
> Thank you,
> Kathleen
> 
> Kathleen M. Moriarty, CISSP | GRC Strategy | Office of the CTO |
> 617-851-5807 | Kathleen.Moriarty@emc.com  | EMC Corporation
> 
> 
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Wed Dec 21 20:54:39 2011
Return-Path: <kathleen.moriarty@emc.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 7076511E80F4 for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EHhU7EQ6BQ4x for <mile@ietfa.amsl.com>; Wed, 21 Dec 2011 20:54:38 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id B8E1411E80F3 for <mile@ietf.org>; Wed, 21 Dec 2011 20:54:38 -0800 (PST)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBM4sW5H013779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2011 23:54:36 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Wed, 21 Dec 2011 23:54:18 -0500
Received: from mxhub22.corp.emc.com (mxhub22.corp.emc.com [128.222.70.134]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBM4sGEY019247; Wed, 21 Dec 2011 23:54:16 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub22.corp.emc.com ([128.222.70.134]) with mapi; Wed, 21 Dec 2011 23:54:16 -0500
From: <kathleen.moriarty@emc.com>
To: <takeshi_takahashi@nict.go.jp>, <mile@ietf.org>
Date: Wed, 21 Dec 2011 23:54:15 -0500
Thread-Topic: [mile] Structured cyber security information extension
Thread-Index: AQDuYVoBM5U/035LSxXHQddmHFrfCJekBjnwgAACfXA=
Message-ID: <AE31510960917D478171C79369B660FA0E2A66EC34@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com> <000001ccc065$79503030$6bf09090$@nict.go.jp>
In-Reply-To: <000001ccc065$79503030$6bf09090$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Structured cyber security information extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 04:54:39 -0000

Thank you, Take!

-----Original Message-----
From: Takeshi Takahashi [mailto:takeshi_takahashi@nict.go.jp]=20
Sent: Wednesday, December 21, 2011 11:52 PM
To: Moriarty, Kathleen; mile@ietf.org
Subject: RE: [mile] Structured cyber security information extension

Hello Kathleen,

Thank you for the kind email.

Regarding the EM_XML issue, thank you for the information.
I first thought I cannot use the "xml" value (prepared for dtype) to define
the type of "Record" element.
It seems to be that we can use the "xml" value as the datatype of the
"Record" element.
Thank you for letting me know about that.
I will get rid of the EM_XML declaration from the draft.

Regarding the Record class, I agree.
Thank you for pointing it out here.
Let me change the name into "RawData" to distinguish the Record class of th=
e
IODEF.

I appreciate these kind comments.

Thank you.
Take


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> kathleen.moriarty@emc.com
> Sent: Thursday, December 22, 2011 1:34 PM
> To: mile@ietf.org
> Subject: [mile] Structured cyber security information extension
>=20
> Hello Take,
>=20
> Thank you for posting the updated draft.
>=20
> I was looking through the SCI draft and noticed that EM_XML is defined
> in the UML definition section, but is not used in the defined schema
> extension (xsd).  It looks like the dtype=3Dxml from IODEF sufficiently
> defines the datatype within the schema, so the EM_XML may not be
necessary.
> Is there a reason why we need to define EM_XML?  Or can the UML
> representation leverage the iodef dtype=3D"xml" definition for including
> an XML schema?
>=20
> Also, I see the use of Record in the SCI extension, is this intended to
> be the same Record as is defined in IODEF as it appears to be a separate
> definition?  If it is the same, that is fine.  If it is a separate
> definition, could we use another term as not to confuse the two?  It look=
s
> like the XML schema included is directly in the iodef-sci:Record which
> is embedded in the Record class from IODEF through RecordItem.
>=20
> Thank you,
> Kathleen
>=20
> Kathleen M. Moriarty, CISSP | GRC Strategy | Office of the CTO |
> 617-851-5807 | Kathleen.Moriarty@emc.com  | EMC Corporation
>=20
>=20
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile



From david.black@emc.com  Thu Dec 22 06:39:31 2011
Return-Path: <david.black@emc.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 B9DF421F8A91 for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 06:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6wgxp8sW+Qr for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 06:39:31 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id ED27221F89BA for <mile@ietf.org>; Thu, 22 Dec 2011 06:39:30 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMEdT5Z015252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Dec 2011 09:39:29 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Thu, 22 Dec 2011 09:39:10 -0500
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMEd5Ou002811; Thu, 22 Dec 2011 09:39:08 -0500
Received: from mx14a.corp.emc.com ([169.254.1.216]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Thu, 22 Dec 2011 09:39:04 -0500
From: <david.black@emc.com>
To: <takeshi_takahashi@nict.go.jp>, <kathleen.moriarty@emc.com>, <mile@ietf.org>
Date: Thu, 22 Dec 2011 09:39:03 -0500
Thread-Topic: [mile] Structured cyber security information extension
Thread-Index: AQDuYVoBM5U/035LSxXHQddmHFrfCJekBjnwgACc1SA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05A5CC8F7C@MX14A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com> <000001ccc065$79503030$6bf09090$@nict.go.jp>
In-Reply-To: <000001ccc065$79503030$6bf09090$@nict.go.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Structured cyber security information extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 14:39:31 -0000

Hi Take and Kathleen,

This is a good discussion, but there's a subtle distinction between the two
approaches for embedding XML content defined by another specification (e.g.=
, CPE):

1) The IODEF dtype=3Dxml allows embedding of XML content from a second XML =
document
(e.g., a CPE document) into an IODEF XML document using the namespace from =
the schema
for the second document (e.g. embed CPE content using the XML namespace for=
 CPE), but
the only XML document is the IODEF document.

2) The EM_XML type in the -00 SCI draft embeds the entire second XML docume=
nt,
including the XML header.

If all the systems involved are based on IODEF and expect IODEF documents, =
the
dtype=3Dxml approach is simpler, but there could be systems that want to ge=
nerate or
consume an XML document defined by another specification (e.g., an XML docu=
ment
for CPE).

I think the question here is for implementers - which of these options make=
s more sense:
- Strip the XML header from the second XML document and embed just its cont=
ent
	(preserving the namespace) so that the IODEF document parses as a single I=
ODEF
	document.
- Preserve the entire second XML document so that it can be extracted and t=
reated
	as an XML document without change, but at the cost of complicating the par=
se
	of the IODEF document because there's a complete second XML document embed=
ded.
??

Something to consider is whether it's ok for the encoding to be different b=
etween
the IODEF document and the embedded XML (e.g., CPE).  If not, dtype=3DXML i=
s probably
better because it forces use of the IODEF document's XML encoding for all o=
f the
embedded content (if any of the XML content to be embedded was generated wi=
th a
different encoding, it has to be converted to the encoding used for the IOD=
EF
document before being embedded).

Thanks,
--David

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of T=
akeshi Takahashi
> Sent: Wednesday, December 21, 2011 11:52 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: Re: [mile] Structured cyber security information extension
>=20
> Hello Kathleen,
>=20
> Thank you for the kind email.
>=20
> Regarding the EM_XML issue, thank you for the information.
> I first thought I cannot use the "xml" value (prepared for dtype) to defi=
ne
> the type of "Record" element.
> It seems to be that we can use the "xml" value as the datatype of the
> "Record" element.
> Thank you for letting me know about that.
> I will get rid of the EM_XML declaration from the draft.
>=20
> Regarding the Record class, I agree.
> Thank you for pointing it out here.
> Let me change the name into "RawData" to distinguish the Record class of =
the
> IODEF.
>=20
> I appreciate these kind comments.
>=20
> Thank you.
> Take
>=20
>=20
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> > kathleen.moriarty@emc.com
> > Sent: Thursday, December 22, 2011 1:34 PM
> > To: mile@ietf.org
> > Subject: [mile] Structured cyber security information extension
> >
> > Hello Take,
> >
> > Thank you for posting the updated draft.
> >
> > I was looking through the SCI draft and noticed that EM_XML is defined
> > in the UML definition section, but is not used in the defined schema
> > extension (xsd).  It looks like the dtype=3Dxml from IODEF sufficiently
> > defines the datatype within the schema, so the EM_XML may not be
> necessary.
> > Is there a reason why we need to define EM_XML?  Or can the UML
> > representation leverage the iodef dtype=3D"xml" definition for includin=
g
> > an XML schema?
> >
> > Also, I see the use of Record in the SCI extension, is this intended to
> > be the same Record as is defined in IODEF as it appears to be a separat=
e
> > definition?  If it is the same, that is fine.  If it is a separate
> > definition, could we use another term as not to confuse the two?  It lo=
oks
> > like the XML schema included is directly in the iodef-sci:Record which
> > is embedded in the Record class from IODEF through RecordItem.
> >
> > Thank you,
> > Kathleen
> >
> > Kathleen M. Moriarty, CISSP | GRC Strategy | Office of the CTO |
> > 617-851-5807 | Kathleen.Moriarty@emc.com  | EMC Corporation
> >
> >
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Thu Dec 22 08:03:24 2011
Return-Path: <kathleen.moriarty@emc.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 4FD2621F8AAC for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 08:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.499
X-Spam-Level: 
X-Spam-Status: No, score=-5.499 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, J_CHICKENPOX_27=0.6, J_CHICKENPOX_37=0.6, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBW+z7b3xDkL for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 08:03:23 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6F62121F86A0 for <mile@ietf.org>; Thu, 22 Dec 2011 08:03:23 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMG3L8U014694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Dec 2011 11:03:22 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 22 Dec 2011 11:02:56 -0500
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMG2uvH024802; Thu, 22 Dec 2011 11:02:56 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Thu, 22 Dec 2011 11:02:56 -0500
From: <kathleen.moriarty@emc.com>
To: <david.black@emc.com>, <takeshi_takahashi@nict.go.jp>, <mile@ietf.org>
Date: Thu, 22 Dec 2011 11:02:55 -0500
Thread-Topic: [mile] Structured cyber security information extension
Thread-Index: AQDuYVoBM5U/035LSxXHQddmHFrfCJekBjnwgACc1SCAAA1+QA==
Message-ID: <AE31510960917D478171C79369B660FA0E2A66ECDA@MX06A.corp.emc.com>
References: <AE31510960917D478171C79369B660FA0E2A66EC33@MX06A.corp.emc.com> <000001ccc065$79503030$6bf09090$@nict.go.jp> <7C4DFCE962635144B8FAE8CA11D0BF1E05A5CC8F7C@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A5CC8F7C@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] Structured cyber security information extension
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 16:03:24 -0000

David & MILE participants,

Could others on the list chime in to provide opinions on how to handle the =
discrepancy between the UML and schema definition?  Take was aware of this =
and had been thinking about it already, opinions would be helpful from the =
list. =20

The UML definition includes the use of EM_XML and a definition for this pur=
pose, which is fine, but it is not used in the actual defined schema.  The =
defined schema uses the dtype=3D"xml" from RecordItem and AdditionalData ap=
propriately, but then  1) the schema for the iodef-sci:Record is set to xs:=
anyType, not XML right now or using the UML defined EM_XML.  Xsd:anyType is=
 not defined in iodef-sci or iodef (not mentioned in the UML descriptions) =
and a mapping would be needed if this were to be used as the solution to en=
sure compatibility in implementations.

2)  It would be good to hear from others on the list as to how they would l=
ike to see this handled, which will help guide how to consistently represen=
t the inclusion of other XML documents.

The co-editors are discussing how they want to approach the issue and will =
post again once they have thought about how they would like to handle this.=
  Input from others may help.

Thank you,
Kathleen

-----Original Message-----
From: Black, David=20
Sent: Thursday, December 22, 2011 9:39 AM
To: Takeshi Takahashi; Moriarty, Kathleen; mile@ietf.org
Subject: RE: [mile] Structured cyber security information extension

Hi Take and Kathleen,

This is a good discussion, but there's a subtle distinction between the two
approaches for embedding XML content defined by another specification (e.g.=
, CPE):

1) The IODEF dtype=3Dxml allows embedding of XML content from a second XML =
document
(e.g., a CPE document) into an IODEF XML document using the namespace from =
the schema
for the second document (e.g. embed CPE content using the XML namespace for=
 CPE), but
the only XML document is the IODEF document.

2) The EM_XML type in the -00 SCI draft embeds the entire second XML docume=
nt,
including the XML header.

If all the systems involved are based on IODEF and expect IODEF documents, =
the
dtype=3Dxml approach is simpler, but there could be systems that want to ge=
nerate or
consume an XML document defined by another specification (e.g., an XML docu=
ment
for CPE).

I think the question here is for implementers - which of these options make=
s more sense:
- Strip the XML header from the second XML document and embed just its cont=
ent
	(preserving the namespace) so that the IODEF document parses as a single I=
ODEF
	document.
- Preserve the entire second XML document so that it can be extracted and t=
reated
	as an XML document without change, but at the cost of complicating the par=
se
	of the IODEF document because there's a complete second XML document embed=
ded.
??

Something to consider is whether it's ok for the encoding to be different b=
etween
the IODEF document and the embedded XML (e.g., CPE).  If not, dtype=3DXML i=
s probably
better because it forces use of the IODEF document's XML encoding for all o=
f the
embedded content (if any of the XML content to be embedded was generated wi=
th a
different encoding, it has to be converted to the encoding used for the IOD=
EF
document before being embedded).

Thanks,
--David

> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of T=
akeshi Takahashi
> Sent: Wednesday, December 21, 2011 11:52 PM
> To: Moriarty, Kathleen; mile@ietf.org
> Subject: Re: [mile] Structured cyber security information extension
>=20
> Hello Kathleen,
>=20
> Thank you for the kind email.
>=20
> Regarding the EM_XML issue, thank you for the information.
> I first thought I cannot use the "xml" value (prepared for dtype) to defi=
ne
> the type of "Record" element.
> It seems to be that we can use the "xml" value as the datatype of the
> "Record" element.
> Thank you for letting me know about that.
> I will get rid of the EM_XML declaration from the draft.
>=20
> Regarding the Record class, I agree.
> Thank you for pointing it out here.
> Let me change the name into "RawData" to distinguish the Record class of =
the
> IODEF.
>=20
> I appreciate these kind comments.
>=20
> Thank you.
> Take
>=20
>=20
> > -----Original Message-----
> > From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> > kathleen.moriarty@emc.com
> > Sent: Thursday, December 22, 2011 1:34 PM
> > To: mile@ietf.org
> > Subject: [mile] Structured cyber security information extension
> >
> > Hello Take,
> >
> > Thank you for posting the updated draft.
> >
> > I was looking through the SCI draft and noticed that EM_XML is defined
> > in the UML definition section, but is not used in the defined schema
> > extension (xsd).  It looks like the dtype=3Dxml from IODEF sufficiently
> > defines the datatype within the schema, so the EM_XML may not be
> necessary.
> > Is there a reason why we need to define EM_XML?  Or can the UML
> > representation leverage the iodef dtype=3D"xml" definition for includin=
g
> > an XML schema?
> >
> > Also, I see the use of Record in the SCI extension, is this intended to
> > be the same Record as is defined in IODEF as it appears to be a separat=
e
> > definition?  If it is the same, that is fine.  If it is a separate
> > definition, could we use another term as not to confuse the two?  It lo=
oks
> > like the XML schema included is directly in the iodef-sci:Record which
> > is embedded in the Record class from IODEF through RecordItem.
> >
> > Thank you,
> > Kathleen
> >
> > Kathleen M. Moriarty, CISSP | GRC Strategy | Office of the CTO |
> > 617-851-5807 | Kathleen.Moriarty@emc.com  | EMC Corporation
> >
> >
> >
> > _______________________________________________
> > mile mailing list
> > mile@ietf.org
> > https://www.ietf.org/mailman/listinfo/mile
>=20
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Thu Dec 22 12:09:49 2011
Return-Path: <kathleen.moriarty@emc.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 8E95721F85AE for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 12:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level: 
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJ71kgGKwYKM for <mile@ietfa.amsl.com>; Thu, 22 Dec 2011 12:09:48 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 75FA121F85A8 for <mile@ietf.org>; Thu, 22 Dec 2011 12:09:48 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMK9k6Y018088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Thu, 22 Dec 2011 15:09:46 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Thu, 22 Dec 2011 15:09:24 -0500
Received: from mxhub19.corp.emc.com (mxhub19.corp.emc.com [10.254.93.48]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBMK9NHx029676 for <mile@ietf.org>; Thu, 22 Dec 2011 15:09:23 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub19.corp.emc.com ([10.254.93.48]) with mapi; Thu, 22 Dec 2011 15:09:23 -0500
From: <kathleen.moriarty@emc.com>
To: <kathleen.moriarty@emc.com>, <mile@ietf.org>
Date: Thu, 22 Dec 2011 15:09:21 -0500
Thread-Topic: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
Thread-Index: Acy7i7GMNgIpNt8LS8qdShJkdguIcQAAAfDgAVZtZbA=
Message-ID: <AE31510960917D478171C79369B660FA0E2A66EDCE@MX06A.corp.emc.com>
References: <20111216004207.22941.32306.idtracker@ietfa.amsl.com> <AE31510960917D478171C79369B660FA0E1A8CA0C5@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E1A8CA0C5@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 20:09:49 -0000

Hello,

Please post any views on the outstanding question for enveloping IODEF in R=
ID.  It seems like the right direction, but it would be good to hear some c=
omments on the list.

Thank you & happy holidays!
Kathleen (as editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of kat=
hleen.moriarty@emc.com
Sent: Thursday, December 15, 2011 7:48 PM
To: mile@ietf.org
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt

Hello,

The updated version includes many of the recommended changes, the following=
 are still pending:

The schema and examples MAY need to be updated depending on the final decis=
ion as to whether or not RID should envelope IODEF (looking like that will =
be the answer, unless there is a reason to keep as is).

The examples need to be updated to use something other than SHA-1 for the d=
igital signatures.

The Normative and Informative section includes 2 options for text.  I was n=
ot 100% sure what this will wind up as, so both are included for comparison=
 & discussion.

Thank you,
Kathleen (as editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of int=
ernet-drafts@ietf.org
Sent: Thursday, December 15, 2011 7:42 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt


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

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-04.txt
	Pages           : 73
	Date            : 2011-12-15

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

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


From turners@ieca.com  Tue Dec 27 13:31:31 2011
Return-Path: <turners@ieca.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 5399821F8AA9 for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 13:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.52
X-Spam-Level: 
X-Spam-Status: No, score=-101.52 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uvSlM3X6T84T for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 13:31:30 -0800 (PST)
Received: from gateway06.websitewelcome.com (gateway06.websitewelcome.com [67.18.16.74]) by ietfa.amsl.com (Postfix) with ESMTP id 6B85E21F8A57 for <mile@ietf.org>; Tue, 27 Dec 2011 13:31:30 -0800 (PST)
Received: by gateway06.websitewelcome.com (Postfix, from userid 5007) id 39823721A2FC2; Tue, 27 Dec 2011 15:31:29 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway06.websitewelcome.com (Postfix) with ESMTP id 2CD4D721A2F6A for <mile@ietf.org>; Tue, 27 Dec 2011 15:31:29 -0600 (CST)
Received: from [71.191.4.217] (port=47336 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RfecK-0001I3-JO; Tue, 27 Dec 2011 15:31:29 -0600
Message-ID: <4EFA3930.7090304@ieca.com>
Date: Tue, 27 Dec 2011 16:31:28 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
References: <20111219223704.24164.38769.idtracker@ietfa.amsl.com> <3F0DAECE-7D07-40F7-A6B4-7A16AE942795@tik.ee.ethz.ch> <7C4DFCE962635144B8FAE8CA11D0BF1E05A48113F5@MX14A.corp.emc.com> <1B2F94D1-B7EC-4A06-86E7-F362571434EE@tik.ee.ethz.ch> <3DF32A33-90B7-4DEF-92CD-EE2B03CC698B@tik.ee.ethz.ch>
In-Reply-To: <3DF32A33-90B7-4DEF-92CD-EE2B03CC698B@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-4-217.washdc.east.verizon.net (thunderfish.local) [71.191.4.217]:47336
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 11
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] Fwd:  I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Dec 2011 21:31:31 -0000

Brian,

I'd not worry about the DOWNREF.  As long as you and the shepherd remind 
me to include it in the LC text, it'll be fine.  I doubt anybody is 
really going to object.  Note that if RFC 4346 was obsoleted and moved 
to historic then I suspect people would object, but RFC 4346 is just 
obsoleted.

I'll wait for -05 before issuing the LC.

spt

On 12/20/11 1:48 AM, Brian Trammell wrote:
> Hi, David, all,
>
> Except... referencing 4346 like this would lead to a downref, since it's obsoleted by 5246. Isn't the right thing to do here to use 5246 as the reference for 1.1 as well?
>
> Cheers,
>
> Brian (author hat)
>
> On Dec 20, 2011, at 7:45 AM, Brian Trammell wrote:
>
>> Hi, David, all,
>>
>> Thanks; yes, the new language is clearer, and better captures the intent of what I was trying to say. Will add to an -05 revision.
>>
>> Best regards,
>>
>> Brian (author hat)
>>
>> On Dec 20, 2011, at 12:31 AM,<david.black@emc.com>  <david.black@emc.com>  wrote:
>>
>>> Hello Brian,
>>>
>>> I think this may have been written slightly too quickly:
>>>
>>>   RID systems MUST use TLS version 1.1 [RFC5246] or higher, and SHOULD
>>>   use TLS version 1.2 or higher, with mutual authentication for
>>>   transport confidentiality, identification, and authentication, as in
>>>   [RFC2818].
>>>
>>> I read that as strongly recommending (SHOULD) use of 1.1 and 1.2 at the
>>> same time, and I don't see a mandatory-to-implement requirement.  Also,
>>> [RFC5246] is TLS 1.2.  I suggest the following (two sentences for clarity):
>>>
>>>   RID systems MUST use TLS version 1.1 [RFC4346] or higher with mutual
>>>   authentication for transport confidentiality, identification, and
>>>   authentication, as in [RFC2818].  RID systems MUST support TLS
>>>   version 1.1 and SHOULD support TLS version 1.2 [RFC5246].
>>>
>>> The remaining text in that paragraph is fine:
>>>
>>>   The session MUST use non-NULL ciphersuites for
>>>   authentication, integrity, and confidentiality; sessions MAY be
>>>   renegotiated within these constraints.  Although TLS implementations
>>>   typically support the older SSL protocol, a RID peer MUST NOT
>>>   request, offer, or use any version of SSL, or any version of TLS
>>>   prior to 1.1, due to known security vulnerabilities in prior versions
>>>   of the protocol; see Appendix E of [RFC5246] for more.
>>>
>>> As for preference for TLS 1.2 over TLS 1.1, RFC 5246 already specifies that
>>> preference as a SHOULD (client_version in ClientHello message, and required
>>> server response), so that preference does not need to be repeated here.
>>>
>>> Thanks,
>>> --David
>>>
>>>
>>>> -----Original Message-----
>>>> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of Brian Trammell
>>>> Sent: Monday, December 19, 2011 5:41 PM
>>>> To: mile@ietf.org
>>>> Subject: [mile] Fwd: I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>>>
>>>> Greetings, all,
>>>>
>>>> rfc6046-bis-04 is now available, and (I believe) addresses all comments to date, including those in
>>>> the AD and appsarea reviews.
>>>>
>>>> Seeing no further discussion on the two open points, I've decided in this version to follow SM's
>>>> "lightweight" suggestion for normative section language, and the last comment in the TLS version
>>>> thread (MUST 1.1, SHOULD 1.2); please comment if you have a strong objection to either of these.
>>>>
>>>> Best regards,
>>>>
>>>> Brian (as author of 6046-bis)
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: internet-drafts@ietf.org
>>>>> Date: December 19, 2011 11:37:04 PM GMT+01:00
>>>>> To: i-d-announce@ietf.org
>>>>> Cc: mile@ietf.org
>>>>> Subject: [mile] I-D Action: draft-ietf-mile-rfc6046-bis-04.txt
>>>>>
>>>>>
>>>>> 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 Working Group of the IETF.
>>>>>
>>>>> 	Title           : Transport of Real-time Inter-network Defense (RID) Messages over HTTP/ TLS
>>>>> 	Author(s)       : Brian Trammell
>>>>> 	Filename        : draft-ietf-mile-rfc6046-bis-04.txt
>>>>> 	Pages           : 8
>>>>> 	Date            : 2011-12-19
>>>>>
>>>>> The Incident Object Description Exchange Format (IODEF) defines a
>>>>> common XML format for document exchange, and Realtime Internetwork
>>>>> Defense (RID) defines extensions to IODEF intended for the
>>>>> cooperative handling of security incidents within consortia of
>>>>> network operators and enterprises.  This document specifies a
>>>>> transport protocol for RID based upon the passing of RID messages
>>>>> over HTTP/TLS.
>>>>>
>>>>>
>>>>> A URL for this Internet-Draft is:
>>>>> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> This Internet-Draft can be retrieved at:
>>>>> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6046-bis-04.txt
>>>>>
>>>>> _______________________________________________
>>>>> mile mailing list
>>>>> mile@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mile
>>>>
>>>> _______________________________________________
>>>> mile mailing list
>>>> mile@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mile
>>
>> _______________________________________________
>> mile mailing list
>> mile@ietf.org
>> https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

From turners@ieca.com  Tue Dec 27 14:14:51 2011
Return-Path: <turners@ieca.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 BFAAF21F8880 for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 14:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.782
X-Spam-Level: 
X-Spam-Status: No, score=-101.782 tagged_above=-999 required=5 tests=[AWL=0.818, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NnpDqMmHUosg for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 14:14:51 -0800 (PST)
Received: from gateway01.websitewelcome.com (gateway01.websitewelcome.com [74.52.222.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2369621F877F for <mile@ietf.org>; Tue, 27 Dec 2011 14:14:51 -0800 (PST)
Received: by gateway01.websitewelcome.com (Postfix, from userid 5007) id F3CA82491A30C; Tue, 27 Dec 2011 16:14:49 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway01.websitewelcome.com (Postfix) with ESMTP id E915C2491A2D2 for <mile@ietf.org>; Tue, 27 Dec 2011 16:14:49 -0600 (CST)
Received: from [71.191.4.217] (port=39978 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RffIH-0004z4-DZ; Tue, 27 Dec 2011 16:14:49 -0600
Message-ID: <4EFA4358.6090401@ieca.com>
Date: Tue, 27 Dec 2011 17:14:48 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: kathleen.moriarty@emc.com
References: <20111216004207.22941.32306.idtracker@ietfa.amsl.com> <AE31510960917D478171C79369B660FA0E1A8CA0C5@MX06A.corp.emc.com> <AE31510960917D478171C79369B660FA0E2A66EDCE@MX06A.corp.emc.com>
In-Reply-To: <AE31510960917D478171C79369B660FA0E2A66EDCE@MX06A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-71-191-4-217.washdc.east.verizon.net (thunderfish.local) [71.191.4.217]:39978
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 5
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: mile@ietf.org
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Dec 2011 22:14:51 -0000

On the normative/informative section I much prefer the 1st option.  If 
you're going to leave both in then you should probably add a note that 
only one is going to be retained.

Also curious what others think about the enveloping issue.

spt

On 12/22/11 3:09 PM, kathleen.moriarty@emc.com wrote:
> Hello,
>
> Please post any views on the outstanding question for enveloping IODEF in RID.  It seems like the right direction, but it would be good to hear some comments on the list.
>
> Thank you&  happy holidays!
> Kathleen (as editor)
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of kathleen.moriarty@emc.com
> Sent: Thursday, December 15, 2011 7:48 PM
> To: mile@ietf.org
> Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
>
> Hello,
>
> The updated version includes many of the recommended changes, the following are still pending:
>
> The schema and examples MAY need to be updated depending on the final decision as to whether or not RID should envelope IODEF (looking like that will be the answer, unless there is a reason to keep as is).
>
> The examples need to be updated to use something other than SHA-1 for the digital signatures.
>
> The Normative and Informative section includes 2 options for text.  I was not 100% sure what this will wind up as, so both are included for comparison&  discussion.
>
> Thank you,
> Kathleen (as editor)
>
> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Thursday, December 15, 2011 7:42 PM
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
>
>
> 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 Working Group of the IETF.
>
> 	Title           : Real-time Inter-network Defense (RID)
> 	Author(s)       : Kathleen M. Moriarty
> 	Filename        : draft-ietf-mile-rfc6045-bis-04.txt
> 	Pages           : 73
> 	Date            : 2011-12-15
>
>     Security incidents, such as system compromises, worms, viruses,
>     phishing incidents, and denial of service, typically result in the
>     loss of service, data, and resources both human and system.  Service
>     providers and Computer Security Incident Response Teams need to be
>     equipped and ready to assist in communicating and tracing security
>     incidents with tools and procedures in place before the occurrence of
>     an attack.  Real-time Inter-network Defense (RID) outlines a
>     proactive inter-network communication method to facilitate sharing
>     incident handling data while integrating existing detection, tracing,
>     source identification, and mitigation mechanisms for a complete
>     incident handling solution.  Combining these capabilities in a
>     communication system provides a way to achieve higher security levels
>     on networks.  Policy guidelines for handling incidents are
>     recommended and can be agreed upon by a consortium using the security
>     recommendations and considerations.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>

From internet-drafts@ietf.org  Tue Dec 27 21:40:02 2011
Return-Path: <internet-drafts@ietf.org>
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 7A7CD21F8B12; Tue, 27 Dec 2011 21:40:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w1BXWxrx1rjK; Tue, 27 Dec 2011 21:40:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 076E921F8B0C; Tue, 27 Dec 2011 21:40:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111228054002.11528.53128.idtracker@ietfa.amsl.com>
Date: Tue, 27 Dec 2011 21:40:02 -0800
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-sci-01.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Dec 2011 05:40:03 -0000

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

	Title           : IODEF-extension to support structured cybersecurity info=
rmation
	Author(s)       : Takeshi Takahashi
                          Kent Landfield
                          Thomas Millar
                          Youki Kadobayashi
	Filename        : draft-ietf-mile-sci-01.txt
	Pages           : 34
	Date            : 2011-12-27

   This document extends the Incident Object Description Exchange Format
   (IODEF) defined in RFC 5070 [RFC5070] to facilitate enriched
   cybersecurity information exchange among cybersecurity entities by
   embedding structured information formatted by specifications,
   including CAPEC[TM] [CAPEC], CEE[TM] [CEE], CPE[TM] [CPE], CVE(R)
   [CVE], CVRF [CVRF], CVSS [CVSS], CWE[TM] [CWE], CWSS[TM] [CWSS], OCIL
   [OCIL], OVAL(R) [OVAL], and XCCDF [XCCDF].


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-sci-01.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-sci-01.txt


From takeshi_takahashi@nict.go.jp  Tue Dec 27 21:52:14 2011
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 6E6F221F854E for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 21:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.055
X-Spam-Level: 
X-Spam-Status: No, score=-1.055 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_JP=1.244]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wv6e1+Rvwjgq for <mile@ietfa.amsl.com>; Tue, 27 Dec 2011 21:52:13 -0800 (PST)
Received: from ns1.nict.go.jp (ns1.nict.go.jp [IPv6:2001:df0:232:300::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C01E21F854D for <mile@ietf.org>; Tue, 27 Dec 2011 21:52:12 -0800 (PST)
Received: from gw1.nict.go.jp (gw1 [133.243.18.250]) by ns1.nict.go.jp  with ESMTP id pBS5q7qH007273; Wed, 28 Dec 2011 14:52:07 +0900 (JST)
Received: from gw1.nict.go.jp (localhost [127.0.0.1]) by gw1.nict.go.jp  with ESMTP id pBS5q7qv018106; Wed, 28 Dec 2011 14:52:07 +0900 (JST)
Received: from mail2.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw1.nict.go.jp  with ESMTP id pBS5q762018103; Wed, 28 Dec 2011 14:52:07 +0900 (JST)
Received: from mail2.nict.go.jp (localhost [127.0.0.1]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 386D82C336; Wed, 28 Dec 2011 14:52:07 +0900 (JST)
Received: from TakeVAIO (unknown [133.243.119.203]) by mail2.nict.go.jp (NICT Mail) with ESMTP id 315342C301; Wed, 28 Dec 2011 14:52:07 +0900 (JST)
From: "Takeshi Takahashi" <takeshi_takahashi@nict.go.jp>
To: <mile@ietf.org>
References: <20111228054002.11528.53128.idtracker@ietfa.amsl.com>
In-Reply-To: <20111228054002.11528.53128.idtracker@ietfa.amsl.com>
Date: Wed, 28 Dec 2011 14:52:14 +0900
Message-ID: <000301ccc524$d981f8d0$8c85ea70$@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: AQGULmByYCUpvH5kVtZUifIc/i5AwJZh6blw
Content-Language: ja
Subject: Re: [mile] I-D Action: draft-ietf-mile-sci-01.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Dec 2011 05:52:14 -0000

Hello all,

I've just posted the new version of the mile-sci draft.
Though the text has changed a lot, we basically have only two changes, as
listed below:

1. table is changed (see section 4.1)
2. IANA description was totally changed

The discussion on EM_XML is still an issue, so I'd appreciate if you could
kindly share your opinion on that.
(I personally like the idea Kathleen kindly proposed.)
The new version tentatively deleted the description of EM_XML, and use the
xml defined by the IODEF dtype.

Thank you very much for those of you who kindly gave me lots of useful
comments and supports.
I wish you a happy new year.

Sincerely,
Take


> -----Original Message-----
> From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Wednesday, December 28, 2011 2:40 PM
> To: i-d-announce@ietf.org
> Cc: mile@ietf.org
> Subject: [mile] I-D Action: draft-ietf-mile-sci-01.txt
> 
> 
> 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 Working Group of the IETF.
> 
> 	Title           : IODEF-extension to support structured
> cybersecurity information
> 	Author(s)       : Takeshi Takahashi
>                           Kent Landfield
>                           Thomas Millar
>                           Youki Kadobayashi
> 	Filename        : draft-ietf-mile-sci-01.txt
> 	Pages           : 34
> 	Date            : 2011-12-27
> 
>    This document extends the Incident Object Description Exchange Format
>    (IODEF) defined in RFC 5070 [RFC5070] to facilitate enriched
>    cybersecurity information exchange among cybersecurity entities by
>    embedding structured information formatted by specifications,
>    including CAPEC[TM] [CAPEC], CEE[TM] [CEE], CPE[TM] [CPE], CVE(R)
>    [CVE], CVRF [CVRF], CVSS [CVSS], CWE[TM] [CWE], CWSS[TM] [CWSS], OCIL
>    [OCIL], OVAL(R) [OVAL], and XCCDF [XCCDF].
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mile-sci-01.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-sci-01.txt
> 
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile


From kathleen.moriarty@emc.com  Wed Dec 28 09:40:49 2011
Return-Path: <kathleen.moriarty@emc.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 9223021F8AB9 for <mile@ietfa.amsl.com>; Wed, 28 Dec 2011 09:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyKrZQIQzx5P for <mile@ietfa.amsl.com>; Wed, 28 Dec 2011 09:40:48 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 88ED321F8A6F for <mile@ietf.org>; Wed, 28 Dec 2011 09:40:48 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBSHecVQ005862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mile@ietf.org>; Wed, 28 Dec 2011 12:40:46 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <mile@ietf.org>; Wed, 28 Dec 2011 12:40:23 -0500
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id pBSHeMOc015154 for <mile@ietf.org>; Wed, 28 Dec 2011 12:40:23 -0500
Received: from mx06a.corp.emc.com ([169.254.1.218]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Wed, 28 Dec 2011 12:40:22 -0500
From: <kathleen.moriarty@emc.com>
To: <mile@ietf.org>
Date: Wed, 28 Dec 2011 12:40:20 -0500
Thread-Topic: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
Thread-Index: Acy7i7GMNgIpNt8LS8qdShJkdguIcQAAAfDgAVZtZbAAC4dpoAEdCbMQ
Message-ID: <AE31510960917D478171C79369B660FA0E2A66F2C2@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [mile] FW:  I-D Action: draft-ietf-mile-rfc6045-bis-04.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mile>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Dec 2011 17:40:49 -0000

It looks like this message from Richard Struse did not get posted to the li=
st:

-----Original Message-----
From: Struse, Richard [mailto:Richard.Struse@HQ.DHS.GOV]=20
Sent: Thursday, December 22, 2011 8:41 PM
To: Moriarty, Kathleen; mile@ietf.org
Subject: RE: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt

I'd like to see RID envelope IODEF with the ability for RID to envelope
other related schema in the future (e.g. CVRF for vulnerability
reports).

Rich

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
kathleen.moriarty@emc.com
Sent: Thursday, December 22, 2011 3:09 PM
To: kathleen.moriarty@emc.com; mile@ietf.org
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt

Hello,

Please post any views on the outstanding question for enveloping IODEF
in RID.  It seems like the right direction, but it would be good to hear
some comments on the list.

Thank you & happy holidays!
Kathleen (as editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
kathleen.moriarty@emc.com
Sent: Thursday, December 15, 2011 7:48 PM
To: mile@ietf.org
Subject: Re: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt

Hello,

The updated version includes many of the recommended changes, the
following are still pending:

The schema and examples MAY need to be updated depending on the final
decision as to whether or not RID should envelope IODEF (looking like
that will be the answer, unless there is a reason to keep as is).

The examples need to be updated to use something other than SHA-1 for
the digital signatures.

The Normative and Informative section includes 2 options for text.  I
was not 100% sure what this will wind up as, so both are included for
comparison & discussion.

Thank you,
Kathleen (as editor)

-----Original Message-----
From: mile-bounces@ietf.org [mailto:mile-bounces@ietf.org] On Behalf Of
internet-drafts@ietf.org
Sent: Thursday, December 15, 2011 7:42 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-rfc6045-bis-04.txt


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 Working Group of the IETF.

	Title           : Real-time Inter-network Defense (RID)
	Author(s)       : Kathleen M. Moriarty
	Filename        : draft-ietf-mile-rfc6045-bis-04.txt
	Pages           : 73
	Date            : 2011-12-15

   Security incidents, such as system compromises, worms, viruses,
   phishing incidents, and denial of service, typically result in the
   loss of service, data, and resources both human and system.  Service
   providers and Computer Security Incident Response Teams need to be
   equipped and ready to assist in communicating and tracing security
   incidents with tools and procedures in place before the occurrence of
   an attack.  Real-time Inter-network Defense (RID) outlines a
   proactive inter-network communication method to facilitate sharing
   incident handling data while integrating existing detection, tracing,
   source identification, and mitigation mechanisms for a complete
   incident handling solution.  Combining these capabilities in a
   communication system provides a way to achieve higher security levels
   on networks.  Policy guidelines for handling incidents are
   recommended and can be agreed upon by a consortium using the security
   recommendations and considerations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mile-rfc6045-bis-04.txt

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

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

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


