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

1 stars 0 forks source link

3. [Deployment] Given the lack of deployment of BCP 38, how do we get the new source address validation mechanism deployed? I’d suggest that deployment be part of the problem statement. From: Tony Li. #11

Open SAVNET-ProblemStatement-Architecture opened 2 years ago

SAVNET-ProblemStatement-Architecture commented 2 years ago

Dan Li: Technical limitations and misaligned incentive are two of the main reasons why BCP 38 is not widely deployed. For technical limitations, BCP 38 requires manual configuration in dynamic networks and cannot work for multi-homed or non-stub ASes. For misaligned incentive, BCP 38 protects the rest of the Internet, not the deployed network. Therefore, networks have no incentive to implement it. We will consider deployment as part of the problem statement.