IETF conflict review for draft-jabley-dnssec-trust-anchor
conflict-review-jabley-dnssec-trust-anchor-01
Yes
(Joel Jaeggli)
No Objection
(Alissa Cooper)
(Alvaro Retana)
(Benoît Claise)
(Deborah Brungard)
(Mirja Kühlewind)
(Suresh Krishnan)
Note: This ballot was opened for revision 00 and is now closed.
Ballot question: "Is this the correct conflict review response?"
Jari Arkko Former IESG member
Yes
Yes
(2016-06-16)
Unknown
I agree with Terry though.
Joel Jaeggli Former IESG member
Yes
Yes
(for -00)
Unknown
Alia Atlas Former IESG member
No Objection
No Objection
(2016-07-06)
Unknown
Terry's very popular on this one; I too agree with his Discuss.
Alissa Cooper Former IESG member
No Objection
No Objection
()
Unknown
Alvaro Retana Former IESG member
No Objection
No Objection
()
Unknown
Ben Campbell Former IESG member
No Objection
No Objection
(2016-07-06)
Unknown
I agree with Terry's discuss and Stephen's wondering why this isn't in the IETF stream.
Benoît Claise Former IESG member
No Objection
No Objection
()
Unknown
Deborah Brungard Former IESG member
No Objection
No Objection
()
Unknown
Kathleen Moriarty Former IESG member
No Objection
No Objection
(2016-06-16)
Unknown
I agree with Terry's discuss as well.
Mirja Kühlewind Former IESG member
No Objection
No Objection
()
Unknown
Spencer Dawkins Former IESG member
No Objection
No Objection
(2016-07-05)
Unknown
I agree with everyone who's agreeing with Terry's Discuss ...
Stephen Farrell Former IESG member
No Objection
No Objection
(2016-06-16)
Unknown
Terry's discuss sounds right to me. And while I've no other issue with the content of the document I do wonder why it'd not be better to process this as an IETF stream document, just in case.
Suresh Krishnan Former IESG member
No Objection
No Objection
()
Unknown
Terry Manderson Former IESG member
(was Discuss, No Record, Recuse)
No Objection
No Objection
(2016-07-10)
Unknown
Changing my position to No Objection after the IANA Considerations section was updated. Thank you for addressing this.