Dear Ben, Thanks for your comments. As I replied in another email, the fundamental value of this draft is "formalizing the problem of intra-domain source address validation". We believe it's worth of being published as an RFC because: 1) the thorough discussion on the problem is important, in some sense more important than solutions; 2) its value may go beyond the WG and benefit future people working on this area. Besides, any "gap" will be finally closed. So we cannot say that a gap analysis document is "incorrect" after solutions are designed, just like RFC 7010, 7429, 7439, 7576, etc. Best, Dan -----邮件原件----- 发件人: forwardingalgorithm@xxxxxxxx <forwardingalgorithm@xxxxxxxx> 代表 Benjamin Schwartz via Datatracker 发送时间: 2025年1月22日 7:19 收件人: secdir@xxxxxxxx 抄送: draft-ietf-savnet-intra-domain-problem-statement.all@xxxxxxxx; last-call@xxxxxxxx; savnet@xxxxxxxx 主题: [savnet] Secdir last call review of draft-ietf-savnet-intra-domain-problem-statement-10 Reviewer: Benjamin Schwartz Review result: Ready This draft is clearly written (barring some minor sentence structure and word choice issues) and covers the topic well. However, I do not see any value in publishing it as an RFC. As a "gap analysis", its value was principally in motivating the formation of a working group (i.e. SAVNET) and helping the participants to agree on their own terminology. This purpose has already been achieved, and is not enhanced by publication. Publishing the document in its current form might even have negative value, since the content will immediately be incorrect when draft-ietf-savnet-inter-domain-architecture is published and the "gap" is closed. My preference would be to fold this content into that draft, or retitle it "Purpose of the SAVNET Architecture" and adjust the content to present an explicitly historical note on why draft-ietf-savnet-inter-domain-architecture was needed. Nit: > it is difficult to require all access networks to deploy SAV > simultaneously Please remove "simultaneously". The difficulty here is not in _synchronizing_ the deployment; it is merely in achieving it. -- savnet mailing list -- savnet@xxxxxxxx To unsubscribe send an email to savnet-leave@xxxxxxxx -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
