Establishing Local DNS Authority in Validated Split-Horizon Environments
draft-ietf-add-split-horizon-authority-14
Yes
Éric Vyncke
No Objection
Jim Guichard
(Francesca Palombini)
(Orie Steele)
Abstain
Note: This ballot was opened for revision 12 and is now closed.
Éric Vyncke
Yes
Deb Cooley
No Objection
Comment
(2024-06-17 for -13)
Not sent
Thanks to Watson Ladd for the Security Review. This draft reads well, and the Security Considerations appear to be correct (thanks for the addition of a paragraph for the salt construction).
Jim Guichard
No Objection
Roman Danyliw
No Objection
Comment
(2024-06-19 for -13)
Sent
Thank you to Mallory Knodel for the GENART review. ** Section 5. This design supports a “high entropy salt, up to 255 octets." Is there a recommended minimum value? It looks like the salt length can be zero. What is the security implication of that?
Mahesh Jethanandani
Abstain
Comment
(2024-06-18 for -13)
Sent
I support Paul's ABSTAIN on this document, and suggest that authors address his comments.
Erik Kline Former IESG member
No Objection
No Objection
(2024-06-17 for -13)
Sent
# Internet AD comments for draft-ietf-add-split-horizon-authority-13 CC @ekline * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md * "Handling Ballot Positions": - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ ## Comments ### S11 * My recollection is that DHCP reconfigure is not mandatory to implement. If this is the case, it should probably be noted here lest readers obtain a false sense of the utility of this. The Reconfigure Accept Option suggests that it's optional for a client: - https://www.rfc-editor.org/rfc/rfc8415.html#section-21.20 - https://datatracker.ietf.org/doc/html/draft-ietf-dhc-rfc8415bis-04#section-21.20
Francesca Palombini Former IESG member
No Objection
No Objection
(for -13)
Not sent
John Scudder Former IESG member
(was Discuss)
No Objection
No Objection
(2024-06-20)
Sent
Thanks for the update!
Murray Kucherawy Former IESG member
(was Discuss)
No Objection
No Objection
(2024-06-20)
Sent for earlier
Thanks to Jiankang Yao for his ARTART review. I support John's DISCUSS. I am concerned about the collection of ABSTAINs here. However, it would take me too long to synthesize an opinion of my own, so I'm moving to No Objection from here.
Orie Steele Former IESG member
No Objection
No Objection
(for -13)
Not sent
Zaheduzzaman Sarker Former IESG member
No Objection
No Objection
(2024-06-19 for -13)
Sent
Thanks for working on this specification. I don't have issues from transport protocol point of view. However, I am deeply concerned about the number of abstaines on the same issue. I feels like this specification to address the concerns before getting published. I also support John's discuss. I think the exception criteria for should be explained and effect of the exception to the SHOULD needs more description.
Paul Wouters Former IESG member
Abstain
Abstain
(2024-06-17 for -13)
Sent
I do not think this proposed protocol is deployable. I have there for balloted Abstain. I've explained this in the past: https://mailarchive.ietf.org/arch/msg/add/7AjzPN1rPLzbWXvxm9l2pdlF2PE/ The recent updates do not address my concerns.
Warren Kumari Former IESG member
Abstain
Abstain
(2024-06-18 for -13)
Sent
I am balloting Abstain for the same reasons as Paul Wouters. In addition, I believe that changes this integral to the resolution path should have been coordinated with the DNSOP WG, with the WGLC copied to them at a bare minimum.