SAVNET-ProblemStatement-Architecture / Inter-domain-problem-statement

3 stars 0 forks source link

20. Should park the existing work and focus on a new joint authored “state of SAV” today. From Barry Greene [after ietf 115] #20

Open XiaoTianCan opened 1 year ago

XiaoTianCan commented 1 year ago

Nan Geng: The question is - what kind of “intra- and inter-domain problem statement” drafts do we want? 1) To analyze the practical problems of any SAV tools? If so, the technical gaps, deployment gaps, operational gaps and some other gaps may need to be included in the drafts. Then, the drafts will look like a survey on the existing SAV practice. 2) Or, only give some analysis on automated sav rule generation mechanisms and find the technical gaps/problems that can be likely or partially to be solved. And this is what the current drafts do. The drafts are describing the motivations of SAVNET architectures and BAR-SAV.