Hi, Thank you so much for your comments.
2016-09-21 16:30 GMT+09:00 Nitin Sharma <[email protected]>: > Why we are so specific (last /8). In my view, that is because how to use the last /8 block was discussed here, and decided to use for special purpose. Yours Sincerely, --- Tomohiro Fujisaki 2016-09-21 16:30 GMT+09:00 Nitin Sharma <[email protected]>: > Hi All, > > Why we are so specific (last /8). > > As per my view there should be no market transfer other than M&A. > > Nitin > > On Wed, Sep 21, 2016 at 12:41 PM, 藤崎智宏 <[email protected]> wrote: >> >> Hi Yu-ya, >> >> Thank you so much for your comment. >> >> Mike also mentioned about M&A in his first mail (thank you, Mike), >> I'll revise my proposal to consider that. >> >> Yours Sincerely, >> --- >> Tomohiro Fujisaki >> >> >> 2016-09-21 9:28 GMT+09:00 Yuya KAWAKAMI <[email protected]>: >> > I'd like to support the purpose of this proposal itself but I'm afraid >> > that >> > anyone who want to obtain more IPv4 addresses seriously will try to do >> > M&A, >> > as Mike mentioned. I wonder if there can be better way to prevent such >> > kind >> > of transfer. >> > >> > Paul and George, >> > Thank you for providing helpful statistics! >> > >> > Regards, >> > Yuya >> > >> > On 2016/09/21 05:11, Masato Yamanishi wrote: >> >> >> >> Dear Colleagues, >> >> >> >> Regardding this prop-116, I have not yet seen any support, opposition, >> >> or >> >> comment, except one clarification made by Mike Jager. >> >> So, let me ask you to express your views for this proposal on the list >> >> more since the meeting is reaching within 2 weeks. >> >> >> >> Mike> Can you advise your opinion for prop-116 after seeing the number >> >> of >> >> tranfers in 103/8 by market and M&A? >> >> >> >> Regards, >> >> Matt >> >> >> >> >> >> 2016-09-08 15:53 GMT+09:00 George Kuo <[email protected] >> >> <mailto:[email protected]>>: >> >> >> >> Hi Mike, >> >> >> >> >> >> On 7/09/2016 8:09 AM, Mike Jager wrote: >> >> >> >> This proposal does not prohibit transfers due to M&A. >> >> Transfers of 103/8 >> >> >> >> block due to M&A continues to be allowed, based on the M&A >> >> transfer >> >> >> >> procedures. >> >> >> >> >> >> I had always assumed that anyone trying to get more than one >> >> allocation of 103/8 was creating a separate entity, obtaining APNIC >> >> membership, receiving the 103/8 allocation, and then using the M&A >> >> process >> >> to transfer it to their original entity. >> >> >> >> If this is the case, the proposal will be ineffective at >> >> stopping >> >> this. >> >> >> >> Does APNIC have any information on the relative number of >> >> transfers within 103/8 that have happened as part of M&As? >> >> >> >> >> >> I have included two tables here for your reference. The numbers for >> >> Market transfers are available as part of the public transfer logs. >> >> (ftp://ftp.apnic.net/public/transfers/ >> >> <ftp://ftp.apnic.net/public/transfers/>) >> >> >> >> >> >> >> >> 1) M&A transfers containing 103/8 space >> >> >> >> +------+-----------+-----------+- >> >> | | Total | Number of | >> >> | Year | Transfers | /24s | >> >> +------+-----------+-----------+- >> >> | 2011 | 3 | 12 | >> >> | 2012 | 10 | 46 | >> >> | 2013 | 18 | 66 | >> >> | 2014 | 126 | 498 | >> >> | 2015 | 147 | 573 | >> >> | 2016 | 45 | 177 | >> >> +------+-----------+------------+- >> >> >> >> 2) Market transfers containing 103/8 space >> >> >> >> +------+-----------+-----------+ >> >> | | Total | Number of | >> >> | Year | Transfers | /24s | >> >> +------+-----------+-----------+ >> >> | 2011 | 2 | 2 | >> >> | 2012 | 21 | 68 | >> >> | 2013 | 16 | 61 | >> >> | 2014 | 25 | 95 | >> >> | 2015 | 67 | 266 | >> >> | 2016 | 56 | 206 | >> >> +------+-----------+-----------+ >> >> >> >> Thanks, >> >> >> >> George K >> >> >> >> >> >> >> >> >> >> Cheers >> >> -Mike >> >> * sig-policy: APNIC SIG on resource management >> >> policy * >> >> _______________________________________________ >> >> sig-policy mailing list >> >> [email protected] <mailto:[email protected]> >> >> https://mailman.apnic.net/mailman/listinfo/sig-policy >> >> <https://mailman.apnic.net/mailman/listinfo/sig-policy> >> >> >> >> >> >> >> >> * sig-policy: APNIC SIG on resource management policy >> >> * >> >> _______________________________________________ >> >> sig-policy mailing list >> >> [email protected] <mailto:[email protected]> >> >> https://mailman.apnic.net/mailman/listinfo/sig-policy >> >> <https://mailman.apnic.net/mailman/listinfo/sig-policy> >> >> >> >> >> >> >> >> >> >> * sig-policy: APNIC SIG on resource management policy >> >> * >> >> _______________________________________________ >> >> sig-policy mailing list >> >> [email protected] >> >> https://mailman.apnic.net/mailman/listinfo/sig-policy >> >> >> > >> > >> > -- >> > Yuya KAWAKAMI >> > JPNAP Network/Software Engineer >> > Internet Multifeed Co. >> > +81-3-6262-0960 >> > [email protected] >> > >> > >> > * sig-policy: APNIC SIG on resource management policy >> > * >> > _______________________________________________ >> > sig-policy mailing list >> > [email protected] >> > https://mailman.apnic.net/mailman/listinfo/sig-policy >> * sig-policy: APNIC SIG on resource management policy >> * >> _______________________________________________ >> sig-policy mailing list >> [email protected] >> https://mailman.apnic.net/mailman/listinfo/sig-policy > > > > > -- > Thanks and Regards > Nitin Sharma > Mobile No: 9968693424 > > * sig-policy: APNIC SIG on resource management policy > * > _______________________________________________ > sig-policy mailing list > [email protected] > https://mailman.apnic.net/mailman/listinfo/sig-policy * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/sig-policy
