Re: [mile] [EXT] WGLC for CSIRT draft

A few more nits. When these and Danny's edits are addresses, this document
is ready to move forward.

Thanks,
Jess

Introduction- Expand CSIRT on first use
                  - change "ensure the security of their systems" to
"improve the security of their systems"
Section 4.3- edit MISP document section to avoid ending on a preposition
("actively being worked on")
      - link to the MISP drafts, as informative references
Section 8- edit first comma in first sentence to a semi colon or period

On Mon, Oct 21, 2019 at 4:38 PM Haynes Jr., Dan <dhaynes@mitre.org> wrote:

> Hi Nancy and Stephen,
>
>
>
> I have some minor nits and questions.
>
>
>
>    - Abstract
>       - Change “This document extends…to add the information type
>       categories…(CSIRT) use cases.” to “This document extends…to add the
>       indicator and incident information type categories…(CSIRT) use cases.”
>       - Remove “The indicator and incident information types are defined
>       as ROLIE extensions.”
>    - Section 2
>       - Should this also reference RFC 8174?
>    - Section 3.1
>       - Change “…that in is the abstract realm…” to “…that is in the
>       abstract realm…”.
>    - Section 3.1
>       - Change “Some examples of indicator information is provided
>       below,…” to “Some examples of indicator information are provided below,…”.
>    - Section 4.2.2
>       - Is “Feed” a defined term?
>    - Section 4.3
>       - Change “day-to=day” should be “day-to-day”.
>    - Section 4.3.1
>       - Bullet 4: Change “…element in the attached MISP Event .” to
>       “…element in the attached MISP Event.”.
>       - Bullet 5: Change “This ensures better compatibility…and a MISP
>       Manifest” to “This ensures better compatibility…and a MISP Manifest.”.
>    - Section 5.1
>       - Change “If a ROLIE server supports…MUST be support” to “If a
>       ROLIE server supports the incident information-type, then these link
>       relations MUST be supported.”
>    - Section 5.2
>       - Change “If a ROLIE server supports…MUST be supported.” to “If a
>       ROLIE server supports the indicator information-type, then these link
>       relations MUST be supported.”
>    - Section 8
>       - Change “When sharing IODEF 2 documents…” to “When sharing IODEF
>       Version 2 documents.”.
>
>
>
> Beyond that, I am comfortable with moving this draft forward.
>
>
>
> Thanks,
>
> Danny
>
>
>
> *From: *mile <mile-bounces@ietf.org> on behalf of "Nancy Cam-Winget
> (ncamwing)" <ncamwing@cisco.com>
> *Date: *Monday, September 23, 2019 at 4:29 PM
> *To: *"mile@ietf.org" <mile@ietf.org>
> *Subject: *[EXT] [mile] WGLC for CSIRT draft
>
>
>
> Fellow MILE participants,
>
>
>
> This is a Working Group Last Call for
> https://datatracker.ietf.org/doc/draft-ietf-mile-rolie-csirt/
>
>
>
> Please provide your review and feedback to the draft’s readiness by Oct 21
> st so that we can move it forward.
>
>
>
> Warm regards,
>
>                 Nancy
> _______________________________________________
> mile mailing list
> mile@ietf.org
> https://www.ietf.org/mailman/listinfo/mile
>