[sig-policy] prop-132-v002: AS0 for Bogons

Dear SIG members A new version of the proposal "prop-132: AS0 for Bogons" has been sent to the Policy SIG for review. Information about earlier versions is available from: http://www.apnic.net/policy/proposals/prop-132 You are encouraged to express your views on the proposal: - Do you

Re: [sig-policy] prop-132-v001 AS0 for Bogons

Ok I get your point now. During my ops days I used to manage "Martians" (reserved blocks/special use blocks) and "Bogons" (unallocated address blocks) prefix filters :) Regards, Aftab A. Siddiqui On Thu, Aug 22, 2019 at 9:09 AM Owen DeLong wrote: > Fair enough. I tend to think of Bogons as

Re: [sig-policy] prop-132-v001 AS0 for Bogons

Fair enough. I tend to think of Bogons as “Those addresses which shouldn’t be advertised _EVER_” (e.g. 10.0.0.0/8) while I tend to think of Unallocated as being more transient in nature. I realize that makes 224.0.0.0/4 classification as a bogon a bit of a grey area, while including all

Re: [sig-policy] prop-132-v001 AS0 for Bogons

Hi Owen, On Thu, Aug 22, 2019 at 7:10 AM Owen DeLong wrote: > I don’t tend to regard unallocated as “bogons”, > Why is that? RFC3871 - Bogon: A "Bogon" (plural: "bogons") is a packet with an IP source address in an address block not yet allocated by IANA

Re: [sig-policy] prop-132-v001 AS0 for Bogons

I don’t tend to regard unallocated as “bogons”, but sure, if this proposal is strictly about unallocated space in the APNIC free pool(s), then I have no problem with that. Owen > On Aug 15, 2019, at 17:15 , Aftab Siddiqui wrote: > > Hi Owen, > Just to give you an example, all unallocated