6. [Suggestion] Suggest to reconcile by treating intra-domain and inter-domain as the sort of ideal cases, and trying to map solutions onto one or the other, rather than trying to pursue these much more complex and varied organizational structures that don't necessarily align well to either one or both. From: John O'Brien.

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

1 stars 0 forks source link

6. [Suggestion] Suggest to reconcile by treating intra-domain and inter-domain as the sort of ideal cases, and trying to map solutions onto one or the other, rather than trying to pursue these much more complex and varied organizational structures that don't necessarily align well to either one or both. From: John O'Brien. #14

Open SAVNET-ProblemStatement-Architecture opened 2 years ago

SAVNET-ProblemStatement-Architecture commented 2 years ago

Dan Li: Because the deployment scenarios of intra-domain SAV and inter-domain SAV are different, we use varied scenarios in the Gap Analysis. But in the Problem Statement and Requirements, we try to align intra-domain SAV and inter-domain SAV. Particularly, in our preliminary idea, the new intra-domain SAV mechanism and the new inter-domain SAV mechanism share the same high-level idea.

SAVNET-ProblemStatement-Architecture commented 2 years ago

Jared Mauch (IETF114 meeting): Agree with John. To the extent that internal organization things look like external organization things. We should align based on that.