[sig-policy] Idea for 22.214.171.124/24
- To: "sig-policy at lists dot apnic dot net" <sig-policy at lists dot apnic dot net>
- Subject: [sig-policy] Idea for 126.96.36.199/24
- From: David Huberman <David.Huberman at microsoft dot com>
- Date: Thu, 21 May 2015 19:00:26 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=David.Huberman@microsoft.com;
- Delivered-to: sig-policy at mailman dot apnic dot net
- List-archive: <http://mailman.apnic.net/mailing-lists/sig-policy/>
- List-help: <mailto:firstname.lastname@example.org?subject=help>
- List-id: APNIC SIG on resource management policy <sig-policy.lists.apnic.net>
- List-post: <mailto:email@example.com>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/sig-policy>, <mailto:firstname.lastname@example.org?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/options/sig-policy>, <mailto:email@example.com?subject=unsubscribe>
- Thread-index: AdCT90QUAxhh1oSDQxe8G2th5hGRtQ==
Hello Policy SIG,
I have an idea for 188.8.131.52/24 I would like to share with you before submitting a policy proposal.
Prop-109 properly directed APNIC to use 184.108.40.206/24 and 220.127.116.11/24 for research purposes. That leaves one more significant prefix to deal with: 18.104.22.168/24. It is significant because it contains the IP address 22.214.171.124.
126.96.36.199 is a desirable IP address. It can be used in all sorts of very interesting applications. It also receives an enormous amount of “junk” traffic every day, so it requires a fairly hefty infrastructure just to start routing it.
This is a new idea, and is not fully thought out. So I wanted to post it, get some reactions, and improve the idea. (Or abandon it if people do not like it.)
David R Huberman