[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[c-nsp] DNS amplification

Subject: [c-nsp] DNS amplification
From: mohta at necom830.hpcl.titech.ac.jp (Masataka Ohta)
Date: Mon, 18 Mar 2013 14:01:34 +0900
In-reply-to: <[email protected]>
References: <CAB_zYdLuMntEdyU=UJgz8saGyA_Cq2-Y-UrM5=XnOPmvJ9=X6w@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Arturo Servin wrote:

> 	Yes, BCP38 is the solution.

It is not a solution at all, because it, instead, will promote
multihomed sites bloats the global routing table.

To really solve the problem in an end to end fashion, it is
necessary to require IGPs carry information for the proper
source address corresponding to each routing table entry in a
*FULL* routing table, which must be delivered to almost, if
not all, all the end systems.

						Masataka Ohta

Follow-Ups:
- [c-nsp] DNS amplification
  - From: marka at isc.org (Mark Andrews)

References:
- [c-nsp] DNS amplification
  - From: jlewis at lewis.org (Jon Lewis)
- [c-nsp] DNS amplification
  - From: arturo.servin at gmail.com (Arturo Servin)

Prev by Date: [c-nsp] DNS amplification
Next by Date: [c-nsp] DNS amplification
Previous by thread: [c-nsp] DNS amplification
Next by thread: [c-nsp] DNS amplification
Index(es):
- Date
- Thread