Re: [sig-policy] prop-110v001: Designate 1.2.3.0/24 as Anycast to suppor

Subject: Re: [sig-policy] prop-110v001: Designate 1.2.3.0/24 as Anycast to support DNS Infrastructure

From: Aftab Siddiqui <aftab.siddiqui at gmail dot com>

Date: Mon, 27 Jan 2014 10:10:46 +0500

Cc: "sig-policy at apnic dot net SIG List" <sig-policy at apnic dot net>

Delivered-to: sig-policy at mailman dot apnic dot net

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:dkim-signature:mime-version:x-received:received:in-reply-to: references:date:message-id:subject:from:to:cc:content-type; bh=c+XZPXQ+R3RlUTWu0xx8aa/Ndce+mesuYZMiuN5suOA=; b=rZffpIj7FbkJi9LIUX1Y2Ymu2ZgeT4zIjaC0ncDQbwgpc+ppZIlDyd/uWHsdeUWHtkV1O1bifKox0 IfDOlRZuTXYkG2TWCP6y4q65jjbFWrAJ0zmJSjqMFjLAxchX+8zO+umvoxKKo7cMHxhyO50W/PNTOf YkgJbDcdOgHgmOL0=

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=c+XZPXQ+R3RlUTWu0xx8aa/Ndce+mesuYZMiuN5suOA=; b=DWJmR9ZBbqper3VLYo336cv/oviWz2D8qwdJFUKAam//m2UXTrwbS2NiiidkM1scnJ l6Q5cLjf8Y5+Qz1CieNJYILID+ID2Vhn9b49QReit1wptAuTgSEEiBw9ApuM1rT1Cq0Z +GuBbTFehI0sSMo2ux+of6jwHkhqy+PCNPkpp9sBGdEQAhEi4WPB+tH6cDTqOrSFC/25 bB2Bfo+OGfcIGWfwEnPKIq/DWy7yE/WifwPbuZi30aK1ZSTy7SGXeneJSZhB5x38eYaX lhwD+Tn/K3+Lja2BePSfOMkLRBqvW6kJSmmNE1C5z7EukNgd2R03rRKzK09lwovdougW SkcA==

In-reply-to: <48702F0C-C33D-4AFF-AA13-3A334901CF00 at apnic dot net>

List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy/>

List-help: <mailto:sig-policy-request@lists.apnic.net?subject=help>

List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>

List-post: <mailto:sig-policy@lists.apnic.net>

List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=subscribe>

List-unsubscribe: <http://mailman.apnic.net/mailman/options/sig-policy>, <mailto:sig-policy-request@lists.apnic.net?subject=unsubscribe>

References: <CALS-_OpDgBHuAiaXD1AfS3F+UWnfcePXC3yCrnCHHZYKiDPmDg@mail.gmail.com> <m2txcrpmat.wl%randy@psg.com> <CAK5YLgfx=Jn4X+Ge+UOjPx6iSRbS4=vsfrEVNggcK7=7CpUFeg@mail.gmail.com> <CAEUfUGPVN18AMhet=kd-4krtcYoV+=Eaz+UfU5EBt04gN=_vUA@mail.gmail.com> <CAG5EbHJAWOnVUg=SWekAp9m-9z=rLS1L7FgzfMS1VDjOsB=qJw@mail.gmail.com> <48702F0C-C33D-4AFF-AA13-3A334901CF00@apnic.net>

Hi Geoff,

Do we have any stats showing how many times 1.2.3.4/24 was hijacked in past 1 month.

Regards,

Aftab A. Siddiqui

On Mon, Jan 27, 2014 at 2:11 AM, Geoff Huston <gih at apnic dot net> wrote:

On 27 Jan 2014, at 4:04 am, Jahangir Hossain <jrjahangir at gmail dot com> wrote:

> Is it not possible to minimize this unsolicited incoming traffic ?

Nope - thats the problem with unsolicited incoming traffic!

The way in which you can limit this incoming dross is to limit the scope of the advertisement of the prefix.

I'd certainly recommend to anyone contemplating using this prefix in the manner proposed here is that they use BGP's NOEXPORT community and similar means to limit the extent to which the route advertisement is propagated.

regards,

Geoff

* sig-policy: APNIC SIG on resource management policy *
_______________________________________________
sig-policy mailing list
sig-policy at lists dot apnic dot net
http://mailman.apnic.net/mailman/listinfo/sig-policy