Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)
RFC 6684

Note: This ballot was opened for revision 04 and is now closed.

(Sean Turner) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Benoît Claise) (was Discuss) No Objection

Comment (2012-06-08)
No email
send info
Thanks for addressing my DISCUSS/COMMENT

(Wesley Eddy) No Objection

(Adrian Farrel) No Objection

Comment (2012-06-01 for -04)
No email
send info
Thank you for this document I have no objeciton to its publication.

Here are a few minor and non-blocking Comments that I would appreciate you reading before publication is complete.

---
You will need to remove the citaiotn notation ([ ]) from the Abstract.
--
You should clean up the unused reference to RFC 3339.
---
I would be glad if you discussed with the Ops ADs the need to include a
section in Extensons I-Ds covering Manageability Considerations for the
extensions.
---
I found the nesting of appendixes a little perturbing, but it is 
probably easy enough to grok.

(Stephen Farrell) No Objection

(Brian Haberman) No Objection

(Russ Housley) No Objection

Comment (2012-06-01 for -04)
No email
send info
  Please consider the editorial comments in the Gen-ART Review by
  Peter Yee on 26-May-2012.  Please find the review here:
  http://www.ietf.org/mail-archive/web/gen-art/current/msg07455.html

(Barry Leiba) No Objection

(Pete Resnick) No Objection

(Robert Sparks) (was Discuss) No Objection

(Martin Stiemerling) No Objection