IETF conflict review for draft-savage-eigrp
conflict-review-savage-eigrp-00
Yes
(Alvaro Retana)
No Objection
(Alia Atlas)
(Alissa Cooper)
(Barry Leiba)
(Ben Campbell)
(Benoît Claise)
(Brian Haberman)
(Deborah Brungard)
(Jari Arkko)
(Joel Jaeggli)
(Kathleen Moriarty)
(Spencer Dawkins)
Note: This ballot was opened for revision 00 and is now closed.
Ballot question: "Is this the correct conflict review response?"
Alvaro Retana Former IESG member
Yes
Yes
()
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
()
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
()
Unknown
Barry Leiba Former IESG member
No Objection
No Objection
()
Unknown
Ben Campbell Former IESG member
No Objection
No Objection
()
Unknown
Benoît Claise Former IESG member
No Objection
No Objection
()
Unknown
Brian Haberman Former IESG member
No Objection
No Objection
()
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
()
Unknown
Joel Jaeggli Former IESG member
No Objection
No Objection
()
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
()
Unknown
Spencer Dawkins Former IESG member
No Objection
No Objection
()
Unknown
Stephen Farrell Former IESG member
No Objection
No Objection
(2015-09-02)
Unknown
I don't object, but two points.... - The title doesn't mention Cisco. The 1st sentence of the intro does. I always find including such information in the title useful - I think it means far fewer readers might end up confused about the status of the eventual RFC. I would hope (and encourage) the ISE to have that included in the title whenever possible as that is one of the ways in which we can get value from the Independent stream (I mean documenting proprietary protocols that might one day be input to the IETF stream). - Without having read the rest of the document (sorry, but it is loooooong), I really didn't find the security considerations convincing at all. I wish I had a better understanding of the kind of review the ISE calls for for such drafts. Generalising, ISE stream security considerations text seems to arrive at 5742 review at an almost random point on a continuum from really not good to great.