Hi Bill, On Tue, 24 Jul 2018 at 23:03 William Herrin <b...@herrin.us> wrote:
> On Tue, Jul 24, 2018 at 7:24 AM, Aftab Siddiqui > <aftab.siddi...@gmail.com> wrote: > > Q - Generally, Private or Reserved ASNs are considered as Bogon ASN but > > what about unallocated ASNs? > > Hi Aftab, > > You can reasonably think of a bogon as any Internet number resource > which according to the registration authority should not appear on > whatever network is at issue. > Perfect definition. I have the same opinion. BUT > Q - Is there any RFC (or even draft) which classify unallocated ASNs as > > Bogon as well? > > The RFCs offer guidelines and conventions in this, not hard rules. It > would be an error to treat them as hard rules. > Recently, during a discussion with few decent size service providers who pointed me to RFC3871 suggesting that the word Bogon is for "IP resources" only. Hence, I asked this question here. > > Q - In the above scenario when an RIR deregister a resource (IPv4/v6 or > > ASN) due to any disagreement (sometimes deregistration happens because of > > non-payment and can be resolved in a few days/weeks). How long should a > > service provider wait to mark them as bogon and stop advertising or > > accepting it? > > In my opinion: until the customer stops paying you or the authority > assigns the resource to someone else. As long as the resource was > properly assigned to the customer when they started advertising it, > there's no real angle to forcibly ending it sooner. This is the current practice though it isn't the best one.