IETF conflict review for draft-trossen-sfc-name-based-sff
conflict-review-trossen-sfc-name-based-sff-00
Yes
(Alvaro Retana)
(Martin Vigoureux)
No Objection
Roman Danyliw
(Adam Roach)
(Alissa Cooper)
(Barry Leiba)
(Deborah Brungard)
(Magnus Westerlund)
(Mirja Kühlewind)
Note: This ballot was opened for revision 00 and is now closed.
Ballot question: "Is this the correct conflict review response?"
Roman Danyliw
No Objection
Alvaro Retana Former IESG member
Yes
Yes
()
Not sent
Martin Vigoureux Former IESG member
Yes
Yes
()
Unknown
Adam Roach Former IESG member
No Objection
No Objection
()
Not sent
Alissa Cooper Former IESG member
No Objection
No Objection
()
Not sent
Barry Leiba Former IESG member
No Objection
No Objection
()
Not sent
Benjamin Kaduk Former IESG member
No Objection
No Objection
(2019-06-26)
Sent
No objection on the conflict review. The document itself has a fairly thin security considerations section, that would probably benefit from a reference to the RFC 3986 security considerations ("what a URI resolves to is not necessarily stable", etc.) and some discussion about the extra risk that having a separate Name Resolver component might introduce, what new attack surface that entails, etc.. The writing style also seems rather far removed at times from the prevailing style in the RFC series, though I guess that's mostly the RSE's role to enforce.
Deborah Brungard Former IESG member
No Objection
No Objection
()
Not sent
Magnus Westerlund Former IESG member
No Objection
No Objection
()
Not sent
Mirja Kühlewind Former IESG member
No Objection
No Objection
()
Not sent