Re: [mile] Request for draft reviews - review of IODEF Enumeration Reference

["Panos Kampanakis (pkampana)" <[e-mail]>]

You probably have seen this http://www.ietf.org/rfc/rfc2434.txt but I am pointing it out anyway


From: Adam Montville [mailto:[e-mail]]
Sent: Thursday, June 06, 2013 1:39 PM
To: Panos Kampanakis (pkampana); Moriarty, Kathleen; [e-mail]; Adam Montville
Subject: RE: [mile] Request for draft reviews - review of IODEF Enumeration Reference

Thank you!  I'll make the changes you recommend.

Also, are there good IANA-related RFCs I can look at to tighten this draft up a bit?  What I was intending for the IANA section is to convey both what the registry contains and the format of each element therein.

If there's a better way to do this, let's do it.

Adam

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Panos Kampanakis (pkampana)
Sent: Thursday, June 06, 2013 8:33 AM
To: Moriarty, Kathleen; [e-mail]<mailto:[e-mail]>; Adam Montville ([e-mail]<mailto:[e-mail]>)
Subject: Re: [mile] Request for draft reviews - review of IODEF Enumeration Reference

Hi Adam,

I think this is close to being done. I had reviewed in the past and the registry format is as we had all agreed.
I did a fresh review and had some minor nits and suggestions, and some confusion for the IANA considerations section.


- maybe rephrase "but one that seems the most appropriate at this point is to..." to "but the most appropriate at this point is to..."



- "especially enumerations such as

   CEE, CVE, CCE" maybe put informative references for CEE, CVE and CCE?



- "Where id_type is an IANA-registered type having the form..." I am proposing to rephrase the paragraph a little to avoid the "And where..."

"The format of the ReferenceName MUST follow the form of

      id_type:version:id

   where id_type is an IANA-registered type having the form

      <Abbreviation>

   The version is an IANA-registered type having the form

      <Version>

   The id is the actual enumeration identifier string."



- In section "4  IANA Considerations", it is not very clear to me what each paragraph is trying to convey. It this section trying to describe the IANA registry or the format of a registry update request? To me it seems it is mostly the former with some info on the latter.

Should the "Name of the Registry: "Enumeration Reference Type Identifiers"" be in the "Fields to record in the registry: "?

Does the paragraph "The registry is intended to enable enumeration value additions..." describe what the IANA registry represents or should it be in the registry request for a new value?

Rgs,
Panos



From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Moriarty, Kathleen
Sent: Friday, May 17, 2013 2:13 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [mile] Request for draft reviews

Greetings!

We have had a number of documents updated since the last meeting.  Thank you to all of the editors for making the requested changes!  The current list of drafts up for review (including those that will be a part of the WG after the charter update) include:

RFC5070-bis (IODEF Revision):
http://datatracker.ietf.org/doc/draft-ietf-mile-rfc5070-bis/

Draft on IODEF Guidance:
(input from experience, real use cases, and draft review will be helpful)
http://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/

Structured Cybersecurity Information draft (close to final):
http://datatracker.ietf.org/doc/draft-ietf-mile-sci/

IODEF Enumeration Reference Format:
http://datatracker.ietf.org/doc/draft-montville-mile-enum-reference-format/

Resource-Oriented Lightweight Indicator Exchange (ROLIE):
http://datatracker.ietf.org/doc/draft-field-mile-rolie/

Please take some time to review the drafts and provide feedback to the list.  It would be helpful if we can iterate on most of them prior to the next meeting.  A couple of the drafts are very close to being done.  The list of current drafts and published RFCs can be found at the following link:
http://datatracker.ietf.org/wg/mile/

We will follow up soon on the charter update as well.

Thank you all in advance!
Kathleen



...

This message and attachments may contain confidential information. If it appears that this message was sent to you by mistake, any retention, dissemination, distribution or copying of this message and attachments is strictly prohibited. Please notify the sender immediately and permanently delete the message and any attachments.