Skip to main content

Exporting Type Information for IP Flow Information Export (IPFIX) Information Elements
draft-ietf-ipfix-exporting-type-05

Yes

(Dan Romascanu)

No Objection

(Adrian Farrel)
(Alexey Melnikov)
(Cullen Jennings)
(Jari Arkko)
(Lisa Dusseault)
(Magnus Westerlund)
(Pasi Eronen)
(Ralph Droms)
(Ron Bonica)
(Ross Callon)
(Tim Polk)

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

Dan Romascanu Former IESG member
Yes
Yes (2009-04-22) Unknown

                            
Adrian Farrel Former IESG member
No Objection
No Objection () Unknown

                            
Alexey Melnikov Former IESG member
(was Discuss) No Objection
No Objection (2009-05-20) Unknown

                            
Cullen Jennings Former IESG member
No Objection
No Objection () Unknown

                            
Jari Arkko Former IESG member
No Objection
No Objection () Unknown

                            
Lars Eggert Former IESG member
No Objection
No Objection (2009-04-20) Unknown
Section 1., paragraph 3:
>    This document proposes a general mechanism to encode the full set of
  s/proposes/defines/

Section 3., paragraph 2:
>    privateEnterprseNumber Information Element
  Nit: s/privateEnterprseNumber/privateEnterpriseNumber/

Section 3.9., paragraph 7:
>    | informationElementID          | The Information Element           |
  Nit: s/informationElementID/informationElementId/
Lisa Dusseault Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
(was Discuss) No Objection
No Objection () Unknown

                            
Pasi Eronen Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection () Unknown

                            
Robert Sparks Former IESG member
No Objection
No Objection (2009-04-20) Unknown
Each element's status in this draft is currently "Proposed" - a value rfc 5102 doesn't allow. I'm guessing the intent on approval is for this to become "current"? If so, an RFC/IANA note might be nice so they don't have to guess too.
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Russ Housley Former IESG member
No Objection
No Objection (2009-04-20) Unknown
  The Gen-ART Review by Miguel Garcia on 20 April 2009 provides some
  editorial suggestions.

  Section 1.1, last paragraph. There is an unfinished sentence:

   It draws data type definitions and data type semantics
   definitions from the Information Model; the encodings of these data
   types

  Section 3, last paragraph. There is  an unfinished sentence:

   This Information Element supports
   references only to IANA-defined Information Elements; the
   privateEnterprseNumber Information Element

  A nit revealed by idnits: RFC 2434 has been obsoleted by RFC 5226.

  The draft contains a number of tables. It would be nice to add a
  table number and a caption under each of them, so that the text (or
  text from other drafts and RFC) can safely refer to "Table nn in
  RFC xxxx". This is similar to what the draft does with Figures.
Tim Polk Former IESG member
No Objection
No Objection () Unknown