<p></p><p><strong>Dear all,</strong><br /></p><p>As we know,RIPE NCC and ARIN 
have the similar 2 years limit for transfer.</p><p>We think 2 years limit is 
more reasonable.</p>It will make the policy more compatible with other 
RIRs.<p><br /></p><p>Best&nbsp;Regards,</p><p>Steven</p><br /><p><br 
/></p><p><br /></p><p><br /></p><p><br /></p><p><br /></p><p><br /></p><p><br 
/></p><p><br /></p><p>Dear Sirs,</p><p><br /></p><p>I would also suggest that 2 
years is a reasonable time frame for transfer.</p><p>Many members are still 
don`t know this limit will apply to their account soon.<br /></p><div 
class="x-axi-signature"><br /><div class="x-axi-signature" style="font-family:; 
font-size: 10pt;"><div><br /></div><p style="font-size: 13.33px;"><span 
style="font-family:arial;font-size:10px;"><span style="border-collapse: 
separate;"><span style="color:#888888;border-collapse: collapse;"><span 
style="color:#000000;">Best&nbsp;</span></span></span>Regards,</span></p><p 
style="font-size: 13.33px;"><span 
style="font-family:arial;font-size:10px;color:#000000;">Ernest 
Tse</span></p><div style="font-size: 13.33px;"><br /></div></div></div><br />On 
Thu, 12/10/2017 18.15, xswdesert&nbsp;&lt;[email protected]&gt; wrote:<br 
/><blockquote style="padding-left: 4px; margin-left: 16px; border-left-color: 
rgb(0, 0, 204); border-left-width: 2px; border-left-style: solid;"><div 
style="color: rgb(0, 0, 0); line-height: 1.7; font-family: Arial; font-size: 
14px;"><div style="color: rgb(0, 0, 0); line-height: 1.7; font-family: Arial; 
font-size: 14px;"><div><strong>Dear community</strong>,</div><div>We support 
the previous version that 103/8 can't be transfered in 2 years. 2 years limit 
is reasonable.</div><div>Changing the time limit from 2 years to 5 years was a 
big change to the proposal 116. Many community members didn't know the change 
if they didn't attent this meeting. After this big change, We didn't understand 
why not return it to the mailing list to discusse before gauge consensus 
onsite. </div><div><strong>Regards</strong>,</div><div><br /></div><div><br 
/></div><div>发件人: <a rel="nofollow" 
href="mailto:[email protected]";>sig-policy-bounces@lists.<wbr>apnic.net</wbr></a>
 [mailto:<a rel="nofollow" 
href="mailto:sig-policy-bounces@lists";>sig-policy-bounces@<wbr>lists</wbr></a>.<br
 /><a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=aAuOPZo5ld-2BNS59PbpCgCWXwQvt0j38ESoLeAeSLM7w-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c9zGyXXN9EGIUWZngJUPnbMPyx0sbg7Pkin6TJ3RthbA7xCBKvVnwH-2BbX-2Fztj3eM4RbeNFfslAeUJSZiJT90bsiuEAZKz-2BlNg-2BvvHqMqqYmMkX5-2B4AbGRbnBVVjDLbwHuNKp6bDKxEVCJxIXu5s1426Q-3D";
 target="_blank">apnic.net</a>] 代表 <a rel="nofollow" 
href="mailto:[email protected]";>sig-policy-request@lists.<wbr>apnic.net</wbr></a><br
 /> 发送时间: 2017年9月18日 15:45<br /> 收件人: <a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a><br /> 
主题: sig-policy Digest, Vol 160, Issue 27<br /><br /> Send sig-policy mailing 
list submissions to<br /> &nbsp; &nbsp; &nbsp; &nbsp; <a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a><br 
/><br /> To subscribe or unsubscribe via the World Wide Web, visit<br /> &nbsp; 
&nbsp; &nbsp; &nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUmipBN84-2BmQ2TjZWRnzKphdJ0-2BKxcniH6DgValcOC2GuxhPMQtuW0tiU5TPMpCEiaQ-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c96pQzENb2bzDFxdGS32MC-2FTe915xO-2BsNfM2mp2aExaaxqk3etCpO7AgXCkT8MeciFm4jsw7ElQV1PxB5wyXJ7M7S71clBS1O51wrmio-2BoouMhxe1uoAmljBvDht-2BfGv0NHr4uYW-2BOyPiGBpvWk6umUk-3D";
 
target="_blank">https://mailman.apnic.net/<wbr>mailman/listinfo/sig-policy</wbr></a><br
 /> or, via email, send a message with subject or body 'help' to<br /> &nbsp; 
&nbsp; &nbsp; &nbsp; <a rel="nofollow" 
href="mailto:[email protected]";>sig-policy-request@lists.<wbr>apnic.net</wbr></a><br
 /><br /> You can reach the person managing the list at<br /> &nbsp; &nbsp; 
&nbsp; &nbsp; <a rel="nofollow" 
href="mailto:[email protected]";>[email protected].<wbr>net</wbr></a><br
 /><br /> When replying, please edit your Subject line so it is more specific 
than<br /> &quot;Re: Contents of sig-policy digest...&quot;<br /><br /><br /> 
Today's Topics:<br /><br /> &nbsp; &nbsp;1.&nbsp; Moratorium on 103/8 transfers 
(Secretariat)<br /> &nbsp; &nbsp;2.&nbsp; Final Comment Period for prop-116: 
Prohibit to&nbsp; &nbsp;transfer IPv4<br /> &nbsp; &nbsp; &nbsp; add&nbsp; 
&nbsp; &nbsp; &nbsp;resses in the final /8 block (chku)<br /> &nbsp; 
&nbsp;3.&nbsp; prop-118: No need policy in APNIC region returned to&nbsp; 
&nbsp; &nbsp;author<br /> &nbsp; &nbsp; &nbsp; (chku)<br /><br /><br /> 
------------------------------<wbr>------------------------------<wbr>----------<br
 /><br /> Message: 1<br /> Date: Mon, 18 Sep 2017 14:38:07 +1000<br /> From: 
Secretariat &lt;<a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a>&gt;<br /> To: 
&lt;<a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a>&gt;<br 
/> Subject: [sig-policy] Moratorium on 103/8 transfers<br /> Message-ID: &lt;<a 
rel="nofollow" 
href="mailto:[email protected]";>85f26a94-19b2-1071-3cd5-<wbr>[email protected]</wbr></a>&gt;<br
 /> Content-Type: text/plain; charset=&quot;utf-8&quot;; format=flowed<br /><br 
/> 
______________________________<wbr>______________________________<wbr>____________<br
 /><br /> Moratorium on 103/8 transfers<br /> 
______________________________<wbr>______________________________<wbr>____________<br
 /><br /><br /> At APNIC 44 in Taichung last week, policy proposal prop-116 
?Prohibit to<br /> transfer IPv4 addresses in the final /8 block? reached 
consensus.<br /><br /> &nbsp; &nbsp; &nbsp;<a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUmsLlmJqHvjRpb27Tm7mdCR2UjZJJcmHWl7IhmhK3LF4EQNYtw1eiGt2Iab0AvSa-2FRjPEPwIKyOGZT-2Bjs-2B8U98Y-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c96UpD0HsYQh-2Fzo44cIo3wFqnTdoAHzSuu3-2B9NmsCwHpvNoLQfj8oyfEICELHuOsMA-2Bp34WaXjqZSorxpetTKX55RSqXVNdlKccsl0McpMoJDlmxgP2x5Ep6YbARFsu-2BAYrEQ5JC00t652cgxAiUL21o-3D";
 
target="_blank">https://www.apnic.net/wp-<wbr>content/uploads/2017/09/prop-<wbr>116-v006.txt</wbr></wbr></a><br
 /><br /> At the APNIC Member Meeting on Thursday, 14 September, the APNIC 
Executive<br /> Council (EC) placed an immediate moratorium on all transfers 
from the 103/8<br /> block.<br /><br /> This moratorium is now in place and any 
transfer request from 103/8 received<br /> by APNIC on or after 14 September 
2017 will be deferred until such time that<br /> the moratorium is lifted by 
the APNIC EC.<br /><br /> When prop-116 completes the remaining steps in the 
Policy Development<br /> Process, the APNIC Secretariat will advise the EC and 
community. The APNIC<br /> EC intends to lift the moratorium once the proposal 
either fails, or is<br /> implemented.<br /><br /> 
______________________________<wbr>______________________________<wbr>____________<br
 /><br /> APNIC Secretariat???????????????????<wbr>????????????? <a 
rel="nofollow" href="mailto:[email protected]";>[email protected]</a> 
Asia<br /> Pacific Network Information Centre (APNIC)?? Tel:? 61 7 3858 3100 PO 
Box<br /> 3646 South Brisbane, QLD 4101 Australia??? Fax:? 61 7 3858 3199<br /> 
6 Cordelia Street, South Brisbane, QLD??????????? <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=xF2otKml8FKK0iLyO1O8hgi3CRL5kYM3RBYOh6zx3-2FE-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c94pBPtQgjm7jgroVr493ervbNayBssaI99IJI5qYKx7MT5mkuEivHedUm8VBPQqIxWKJABLpPHzppOzTyMBWi5-2Fzjzh7MD9OLBKYoZPf0FlwnLM-2BUeFcHdbO0dW8R23TdtCKwZsGYSJs4wCbE5-2FvDaE-3D";
 target="_blank">http://www.apnic.net</a><br /> 
______________________________<wbr>______________________________<wbr>____________<br
 /><br /><br /> ------------------------------<br /><br /> Message: 2<br /> 
Date: Mon, 18 Sep 2017 15:43:32 +0800 (CST)<br /> From: &quot;chku&quot; &lt;<a 
rel="nofollow" href="mailto:[email protected]";>[email protected]</a>&gt;<br /> 
To: &quot;sig-policy&quot; &lt;<a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a>&gt;<br /> Subject: 
[sig-policy] Final Comment Period for prop-116: Prohibit to<br /> &nbsp; &nbsp; 
&nbsp; &nbsp; transfer IPv4 add&nbsp; &nbsp; &nbsp; &nbsp;resses in the final 
/8 block<br /> Message-ID: &lt;<a rel="nofollow" 
href="mailto:[email protected]";>1505720612.174740.chku@twnic.<wbr>net.tw</wbr></a>&gt;<br
 /> Content-Type: text/plain; charset=&quot;utf-8&quot;<br /><br /> Dear 
colleagues<br /><br /> A revised version &quot;prop-116-v006: Prohibit to 
transfer IPv4 addresses in the<br /> final /8 block&quot; reached consensus at 
the APNIC 44 Policy SIG and then later<br /> at the APNIC Member Meeting 
(AMM).<br /><br /> Synopsis:<br /> ---------<br /> The proposed policy solution 
reaching consensus is:<br /><br /> Prohibit transfer IPv4 addresses under final 
/8 address block (103/8) which<br /> have not passed five years after its 
allocation/assignment. If the address<br /> block allocated to a LIR in five 
years is not needed any more, it must<br /> return to APNIC to allocate to 
another organization using final<br /> /8 policy. This five years requirement 
will apply both market and M&amp;A<br /> transfers.<br /><br /> This proposal 
will now move to the next step in the APNIC Policy Development<br /> Process 
and is being returned to the Policy SIG mailing list for the final<br /> 
Comment Period.<br /><br /> &nbsp; &nbsp;- Deadline for comments:&nbsp; 23:59 
(UTC +10) Wednesday, 18 October 2017<br /><br /> Proposal details, including 
the full text of the proposal, history, and<br /> links to previous versions 
are available at:<br /><br /> &nbsp; &nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUvoUN-2BdJmPDhZZTdUjYSylRTzPubGXFfdECo31dnC5KUl4BbSUKeFBkIgnNCcET28ixbaE4zPNNNgDeImQ9Y8GQ-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c974Zg6axaH-2FPX3p0R38SRzV5iKxU-2BOkYzsf4PjQDt34YkvcfA7B0evmfQ9WrYWTAoOnasDDFTokDjM7gLkBtY1R91jXBjnLHoIy7zzzpR7LqXYJIjxAbAWBXiC-2Bt98mNvpahOR-2B-2BYFLZb3tJ8zcwUqU-3D";
 
target="_blank">https://www.apnic.net/<wbr>community/policy/proposals/<wbr>prop-116/</wbr></wbr></a><br
 /><br /> Regards<br /><br /> Sumon, Bertrand, Ching-Heng<br /> Policy SIG 
Chairs<br /><br /><br /> 
------------------------------<wbr>-------------------------<br /><br /> 
prop-116-v006: Prohibit to transfer IPv4 addresses in the final /8 block<br 
/><br /> ------------------------------<wbr>-------------------------<br /><br 
/> Proposer:&nbsp; &nbsp; &nbsp; &nbsp;Tomohiro Fujisaki<br /> &nbsp; &nbsp; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a><br /><br /><br /> 1. 
Problem statement<br /> --------------------<br /><br /> There are a lot of 
transfers of IPv4 address blocks from 103/8 happening,<br /> both within the 
APNIC region and among RIRs.<br /><br /> Then number of transfers from 103/8 
block are 352, which is about 14% of the<br /> total number of transfers as of 
10 Septermber 2017.<br /> This is the highest number of transfers in all APNIC 
managed /8s.<br /><br /> And based on the information provided by APNIC 
Secretariat, number of<br /> transfers from the 103/8 block are increasing year 
by year.<br /><br /> Updated by APNIC Secretariat on 27 January 2017:<br /><br 
/> 1) M&amp;A transfers containing 103/8 space<br /><br /> 
+------+-----------+----------<wbr>-+-<br /> |&nbsp; &nbsp; &nbsp; |&nbsp; 
&nbsp;Total&nbsp; &nbsp;| Number of |<br /> | Year | Transfers |&nbsp; 
&nbsp;/24s&nbsp; &nbsp; |<br /> +------+-----------+----------<wbr>-+-<br /> | 
2011 |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3 |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;12 
|<br /> | 2012 |&nbsp; &nbsp; &nbsp; &nbsp; 10 |&nbsp; &nbsp; &nbsp; &nbsp; 
&nbsp;46 |<br /> | 2013 |&nbsp; &nbsp; &nbsp; &nbsp; 18 |&nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp;66 |<br /> | 2014 |&nbsp; &nbsp; &nbsp; &nbsp;126 |&nbsp; &nbsp; 
&nbsp; &nbsp; 498 |<br /> | 2015 |&nbsp; &nbsp; &nbsp; &nbsp;147 |&nbsp; &nbsp; 
&nbsp; &nbsp; 573 |<br /> | 2016 |&nbsp; &nbsp; &nbsp; &nbsp; 63 |&nbsp; &nbsp; 
&nbsp; &nbsp; 239 |<br /> | 2017 |&nbsp; &nbsp; &nbsp; &nbsp; 45 |&nbsp; &nbsp; 
&nbsp; &nbsp; 178 |<br /> +------+-----------+----------<wbr>--+-<br /><br /> 
2) Market transfers containing 103/8 space<br /><br /> 
+------+-----------+----------<wbr>-+<br /> |&nbsp; &nbsp; &nbsp; |&nbsp; 
&nbsp;Total&nbsp; &nbsp;| Number of |<br /> | Year | Transfers |&nbsp; 
&nbsp;/24s&nbsp; &nbsp; |<br /> +------+-----------+----------<wbr>-+<br /> | 
2011 |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2 |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2 
|<br /> | 2012 |&nbsp; &nbsp; &nbsp; &nbsp; 21 |&nbsp; &nbsp; &nbsp; &nbsp; 68 
|<br /> | 2013 |&nbsp; &nbsp; &nbsp; &nbsp; 16 |&nbsp; &nbsp; &nbsp; &nbsp; 61 
|<br /> | 2014 |&nbsp; &nbsp; &nbsp; &nbsp; 25 |&nbsp; &nbsp; &nbsp; &nbsp; 95 
|<br /> | 2015 |&nbsp; &nbsp; &nbsp; &nbsp; 67 |&nbsp; &nbsp; &nbsp; &nbsp;266 
|<br /> | 2016 |&nbsp; &nbsp; &nbsp; &nbsp;103 |&nbsp; &nbsp; &nbsp; &nbsp;394 
|<br /> | 2017 |&nbsp; &nbsp; &nbsp; &nbsp; 70 |&nbsp; &nbsp; &nbsp; &nbsp;288 
|<br /> +------+-----------+----------<wbr>-+<br /><br /> And also, transfers 
from the 103/8 block include:<br /> &nbsp; - Take place within 1 year of 
distribution, or<br /> &nbsp; - Multiple blocks to a single organization in 
case of beyond 1 year.<br /><br /> Further, there is a case where a single 
organization have received 12 blocks<br /> transfers from 103 range.<br /><br 
/> see:&nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUg8gVLuW61BSR2eB8RsQYdH8zD7GXy6jhlTyK5G3dMIUGHT9gdk4VkDuKrAW1lF6NA-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c94p1mrccqAkVTcaPBiUJ3o-2BXSyytVarJVjCP8LuaSQJpWUGyQc0py3VqM1gT970aGDbatACBX4Pugf3dhHNbAeG2vJyu-2BhVB00881pDZCae-2Fo90j6SRlyo1ZZCN5YH-2FpF3U8JUAQjTx9luQ4wI5VyVs-3D";
 
target="_blank">https://www.apnic.net/<wbr>transfer-resources/transfer-<wbr>logs</wbr></wbr></a><br
 /><br /> From these figures, it is quite likely that substantial number of 
103/8<br /> blocks are being used for transfer purpose.<br /><br /> This 
conflicts with the concept of distribution of 103/8 block (prop-062),<br /> 
which is intended to accommodate minimum IPv4 address blocks for new comers.<br 
/><br /> prop-062: Use of final /8<br /> &nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUpZ2MNT0Jh9riZ8Aw0jq3-2BBKFT98-2BB8q5RClctPGmvsE4BXqvGUawDCW-2Bgfn5Jn7-2Bw-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c95zTzsWhVqm408ArM4ZBOmZFm2n693XFIdjTG-2BPseBIYhjbDit3OHzK68rPQPQoyCu1UggCvipmHUDo-2FD8Fm-2FM6QkTHFS86zG1HVb-2BYRMy85a0qRBqJ5uwgycaspXm0Z-2F1PgEUneBJ8iam7-2FS5yA0Vg-3D";
 
target="_blank">https://www.apnic.net/policy/<wbr>proposals/prop-062</wbr></a><br
 /><br /><br /> 2. Objective of policy change<br /> 
-----------------------------<br /><br /> When stated problem is solved, 
distribution from 103/8 block will be<br /> consistent with its original 
purpose, for distribution for new entrants to<br /> the industry. Without the 
policy change, substantial portion of 103/8 blocks<br /> will be consumed for 
transfer purpose.<br /><br /><br /> 3. Situation in other regions<br /> 
-----------------------------<br /> &quot;RIPE Resource Transfer Policies&quot; 
says:<br /><br /> &nbsp; &nbsp;2.2 Transfer Restrictions<br /><br /> &nbsp; 
&nbsp; Scarce resources, which are understood as those resources that are<br /> 
&nbsp; &nbsp; allocated or assigned by the RIPE NCC on a restricted basis (such 
as<br /> &nbsp; &nbsp; IPv4 or 16-bit ASNs), cannot be transferred for 24 
months from the<br /> &nbsp; &nbsp; date the resource was received by the 
resource holder. This<br /> &nbsp; &nbsp; restriction also applies if the 
resource was received due to a change<br /> &nbsp; &nbsp; in the 
organisation??s business (such as a merger or acquisition).<br /><br /><br /> 
4. Proposed policy solution<br /> ---------------------------<br /><br /> 
Prohibit transfer IPv4 addresses under final /8 address block (103/8) which<br 
/> have not passed five years after its allocation/assignment. If the 
address<br /> block allocated to a LIR in five years is not needed any more, it 
must<br /> return to APNIC to allocate to another organization using final /8 
policy.<br /> This five years requirement will apply both market and M&amp;A 
transfers.<br /><br /><br /> 5. Advantages / Disadvantages<br /> 
-----------------------------<br /><br /> Advantages:<br /> &nbsp; - It makes 
103/8 blocks available according to the original purpose,<br /> &nbsp; &nbsp; 
as distribution for new entrants (rather than being consumed for<br /> &nbsp; 
&nbsp; transfer purpose)<br /><br /> &nbsp; - IPv4 addresses under final /8 are 
not transferred to outside APNIC.<br /><br /> &nbsp; - By prohibiting transfer, 
them, it is possible to keep one /22 for<br /> &nbsp; &nbsp; each LIRs state, 
which is fair for all LIRs.<br /><br /> Disadvantages:<br /><br /> None.<br 
/><br /><br /> 6. Impact on resource holders<br /> 
------------------------------<br /><br /> &nbsp; - LIRs cannot transfer 
address blocks under 103/8. No big impact while<br /> &nbsp; &nbsp; they use 
it.<br /><br /> &nbsp; - Organizations which needs to receive transferred IPv4 
can continue<br /> &nbsp; &nbsp; to do so, outside 103/8 blocks (which should 
be made available for<br /> &nbsp; &nbsp; new entrants)<br /><br /><br /> 7. 
References<br /> -------------<br /> RIPE Resource Transfer Policies<br /><a 
rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=xF2otKml8FKK0iLyO1O8hovsqCyGPCffWxWRVmzZKc-2F22UMCMsKH3f0jgbfy5GNOxYaZjrjiaqFN8wxTSqxs7Q-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c9yM4gZomY3Dx-2FDVDy-2FL5AXIh-2Bg7X5QhMANS93gYvmaf07EMQ-2BG-2F2mRA12jk295krzl7lbiCPfUxe-2BS6cw66SfBgaxNqvd0SZFCnpFmkcJVFOBnT16u3C9XpoJAXfaQNv3kAp5M9-2F3Ax6-2FRTTomaFEI4-3D";
 
target="_blank">http://www.ripe.net/<wbr>publications/docs/transfer-<wbr>policies</wbr></wbr></a><br
 /> -------------- next part --------------<br /> An embedded and 
charset-unspecified text was scrubbed...<br /> Name: 00.txt<br /> URL:<br 
/>&lt; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=eXqVszIyTkvBB-2BKbaNE0Ub-2BohxwkyayMebeYGK0IPnVLyIUj-2Bbuautj10XzOaapBlAURtFDsVKSFZj0d4RhIDXllKyOOTBBXQ7wlHlfjqoCRhvtmgYlMyQGHAc8gCwyDe5KUoN8KrKz2cOwQkdJNDw-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c9yxMPT447enAqW8LaVl-2F77kNUToSScB5LE8isYNZkjUzL54bIi50L-2BGRvFw6ICtb2T21g-2B7W-2FY-2FbmI02V74igtKfdMSr4o85SX94398Y1z7j45nu5gPlCI2VbYlkrkebyenw5lg10Hg27Sk0T6H3ekk-3D";
 
target="_blank">http://mailman.apnic.net/<wbr>mailing-lists/sig-policy/<wbr>attachments/20170918/0e64<br
 /> 5384/attachment.txt</wbr></wbr></a>&gt;<br /><br /> 
------------------------------<br /><br /> Message: 3<br /> Date: Mon, 18 Sep 
2017 15:44:52 +0800 (CST)<br /> From: &quot;chku&quot; &lt;<a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a>&gt;<br /> To: 
&quot;sig-policy&quot; &lt;<a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a>&gt;<br /> Subject: 
[sig-policy] prop-118: No need policy in APNIC region<br /> &nbsp; &nbsp; 
&nbsp; &nbsp; returned to&nbsp; &nbsp; &nbsp;author<br /> Message-ID: &lt;<a 
rel="nofollow" 
href="mailto:[email protected]";>1505720692.175013.chku@twnic.<wbr>net.tw</wbr></a>&gt;<br
 /> Content-Type: text/plain; charset=&quot;big5&quot;<br /><br /> Dear 
colleagues<br /><br /> Version 1 of prop-118: No need policy in APNIC region, 
did not reach<br /> consensus at the APNIC 44 Open Policy Meeting.<br /><br /> 
The Policy SIG Chairs returned the proposal to the author for further<br /> 
consideration and invited him to submit an amended version based on the<br /> 
community's feedback.<br /><br /> Proposal details, including the full text of 
the proposal, history, and<br /> links to previous versions are available 
at:<br /><br /> &nbsp; &nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUvoUN-2BdJmPDhZZTdUjYSylRTzPubGXFfdECo31dnC5KUl4BbSUKeFBkIgnNCcET28tK3lWsqKV-2BwD6xg5qvslUA-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c92D9ssV2eP6qrhzDejmZc2qk6lqzFPa0dd6zz6yznqmAD3p4PhhhH-2FBRGlfavSeuu1P0N94LFW-2BXZmPUp7v8l-2Fpzk-2BSjw0hScpAW4gZKCKz5Pnu1kJAfRrlmImszszsVr4GBlJwMfqGPkM0e2RKv5cs-3D";
 
target="_blank">https://www.apnic.net/<wbr>community/policy/proposals/<wbr>prop-118/</wbr></wbr></a><br
 /><br /><br /> Regards<br /><br /> Sumon, Bertrand, Ching-Heng<br /> Policy 
SIG Chairs<br /><br /><br /> 
------------------------------<wbr>-------------------------<br /><br /> 
prop-118-v001: No need policy in APNIC region<br /><br /> 
------------------------------<wbr>-------------------------<br /><br /> 
Proposer:&nbsp; &nbsp; &nbsp; &nbsp;David Hilario<br /> &nbsp; &nbsp; &nbsp; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a rel="nofollow" 
href="mailto:[email protected]";>d.hilario@laruscloudservice.<wbr>net</wbr></a><br
 /><br /><br /> 1. Problem statement<br /> 
------------------------------<wbr>-------------------------<br /><br /> 
Whenever a transfer of IPv4 is taking place within the APNIC region, the<br /> 
recipient needs to demonstrate the &quot;need&quot; for the IPv4 space they 
intend to<br /> transfer.<br /><br /> Companies transferring IPv4 space to 
their pool do this in ordcer to enable<br /> further growth in their network, 
since the space is not coming from the free<br /> public pool, regular policies 
that are intended to protect the limited pool<br /> of IPv4 space can be 
removed in transfers.<br /><br /><br /> 2. Objective of policy change<br /> 
------------------------------<wbr>-------------------------<br /><br /> 
Simplify transfer of IPv4 space between resource holders.<br /> Ease some 
administration on APNIC staff.<br /><br /><br /> 3. Situation in other 
regions<br /> ------------------------------<wbr>-------------------------<br 
/><br /> RIPE region has an all around no need policy in IPv4, even for 
first<br /> allocation, transfers do not require the recipient to demonstrate 
their<br /> intended use of the resources .<br /><br /> ARIN, need base for 
both transfers and resources issued by ARIN.<br /><br /> AFRINIC, need based 
policy on transfers (not active yet) and resource<br /> request from AFRINIC 
based on needs.<br /><br /> LACNIC, no transfers, need based request.<br /><br 
/> Out of all these RIR, only ARIN and RIPE NCC have inter-RIR transfer<br /> 
policies,&nbsp; ARIN has made clear in the past that the &quot;no need&quot; 
policy from<br /> the RIPE region would break inter-RIR transfers from ARIN to 
RIPE region.<br /><br /><br /> 4. Proposed policy solution<br /> 
------------------------------<wbr>-------------------------<br /><br /> Simply 
copy the RIPE policy to solve the ARIN transfer incompatibility:<br /><br /> 
&nbsp;- APNIC shall accept all transfers of Internet number resources to its<br 
/> &nbsp; &nbsp;service region, provided that they comply with the policies 
relating<br /> &nbsp; &nbsp;to transfers within its service region.<br /><br /> 
&nbsp;- For transfers from RIR regions that require the receiving region to<br 
/> &nbsp; &nbsp;have needs-based policies, recipients must provide a plan to 
the<br /> &nbsp; &nbsp;APNIC for the use of at least 50% of the transferred 
resources within<br /> &nbsp; &nbsp;5 years.<br /><br /> source:<br /> &nbsp; 
&nbsp; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUrALMsHil-2BpVmNTNd6yDOuFusAIW7wV7s3bVF4S4QfQhmE-2FurmywiubVNS9Y1KHJMw-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c9yXVi38eQf-2FYWzRbFDFpFckth5aKzcvoS7NQzML309xPOtIz94SFGtGmSBEXRJQ-2BOalLhDMLilpOBVPCaeOSvMLMi2tEddczVqJnN6TIascvQipfT-2FFAW1WH8u3yLJF-2F4gyeuLe6BYImNMn9lSorjGE-3D";
 
target="_blank">https://www.ripe.net/<wbr>publications/docs/ripe-644</wbr></a><br
 /><br /><br /> 5. Advantages / Disadvantages<br /> 
------------------------------<wbr>-------------------------<br /><br /> 
Advantages:<br /><br /> &nbsp;- Harmonisation with RIPE region.<br /> &nbsp;- 
Makes transfer simpler and smoother within APNIC and between APNIC<br /> &nbsp; 
&nbsp;and RIPE.<br /> &nbsp;- maintains a compatibility with ARIN.<br /> 
&nbsp;- Removes the uncertainty that a transfer may be rejected based on<br /> 
&nbsp; &nbsp;potentially badly documented needs.<br /> &nbsp;- Lowers the 
overall administrative burden on APNIC staff.<br /><br /> Disadvantages:<br 
/><br /> none.<br /><br /><br /> 6. Impact on resource holders<br /> 
------------------------------<wbr>-------------------------<br /> None<br 
/><br /><br /> 7. References<br /> 
------------------------------<wbr>-------------------------<br /> 
-------------- next part --------------<br /> An embedded and 
charset-unspecified text was scrubbed...<br /> Name: 00.txt<br /> URL:<br 
/>&lt; <a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=eXqVszIyTkvBB-2BKbaNE0Ub-2BohxwkyayMebeYGK0IPnVLyIUj-2Bbuautj10XzOaapBlAURtFDsVKSFZj0d4RhIDWCflJCNQh1TXCTzmOeOcW49WkBdA-2Blj4G-2BcovIeigr-2BOCWp2i5J9PW9aYUz-2F1rQWw-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c92r5JI37tQfs9qgWwSNyQuXNjjrwzu8tnD38z10GHdFI3otRubcPxIJo3vdqaYP6PFGiOkVXAW1K5hEJtO22wTOQFPSBZmU1XKdYkENV-2FOtlmzamlJs0Cqytnonsqvka-2FnqydsZtGvMxlkFn4sO14KU-3D";
 
target="_blank">http://mailman.apnic.net/<wbr>mailing-lists/sig-policy/<wbr>attachments/20170918/11b9<br
 /> df79/attachment.txt</wbr></wbr></a>&gt;<br /><br /> 
------------------------------<br /><br /> 
______________________________<wbr>_________________<br /> sig-policy mailing 
list<br /><a rel="nofollow" 
href="mailto:[email protected]";>[email protected]</a><br /><a 
rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUmipBN84-2BmQ2TjZWRnzKphdJ0-2BKxcniH6DgValcOC2GuxhPMQtuW0tiU5TPMpCEiaQ-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c93vptVlejfjhB09IqOWW3jUXOWQSykD9Mrw-2BrEn9u7LzAYNjQGHOHc886i2JfCu3KQ-2BNyiC1GP3CgaQkMlZQAp-2BLILDovJjrQhrHfxe1vUkeMRb-2B4n4HKkxnQn34dVN6Ci44x0-2FnH08xb-2FdKESMce4U-3D";
 
target="_blank">https://mailman.apnic.net/<wbr>mailman/listinfo/sig-policy</wbr></a><br
 /><br /> End of sig-policy Digest, Vol 160, Issue 27<br /> 
******************************<wbr>*************<br /><br 
/></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></wbr></div><div><br
 /></div></div></div><br /><br /><span title="neteasefooter"></span>        *   
           sig-policy:  APNIC SIG on resource management policy           *<br 
/>_______________________________________________<br />sig-policy mailing 
list<br /><a rel="nofollow" href="mailto:[email protected]"; 
target="_blank">[email protected]</a><br /><a rel="nofollow" 
href="https://u5763498.ct.sendgrid.net/wf/click?upn=16bEysF9x2jUX1XY2ZMKUmipBN84-2BmQ2TjZWRnzKphdJ0-2BKxcniH6DgValcOC2GuxhPMQtuW0tiU5TPMpCEiaQ-3D-3D_UAkvnIPiyHBK93gJxXZbN-2Fw2XdEjiYo-2Fj5-2BumIaqa25KiRH9xQntuNVWFHATlEzS6H1y-2BH9UOqq5REZcca9c96CTFpvdsUJNSivQ7vXijcMQ3dDIBVNRv6xiLclCATNsoWb88yaOXkUdzaCNLyJxusdnIobAY9yM4FSOPY-2FkOTNeWIm60vFx5onA2HFf4odXmRRf8F-2Bpb7QX7P8E5U4FkXuek7BR0YInSR7xZREJASM-3D";
 
target="_blank">https://mailman.apnic.net/mailman/listinfo/sig-policy</a></blockquote><div
 style="height:30px;"></div><div 
style="height:2px;width:298px;border-bottom:solid 2px #e5e5e5"></div><div 
style="height:20px;"></div><a target="_blank" 
style="background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);background-repeat:no-repeat;background-position:left
 center;font-size:14px;background-size: 20px;height: 39px;line-height: 
39px;padding-left: 25px;display:block;color:#333333;text-decoration: none;" 
href="http://mail.tom.com/webmail-static/welcomesxy.html";  
onmouseover="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);background-repeat:no-repeat;background-position:left
 center;font-size:14px;background-size: 20px;height: 39px;line-height: 
39px;padding-left: 27px;display:block;color:#4c4c4c; 
text-decoration:underline;'" 
onmouseout="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);background-repeat:no-repeat;background-position:left
 center;font-size:14px;background-size: 20px;height: 39px;line-height: 
39px;padding-left: 
27px;display:block;color:#4c4c4c;text-decoration:none'">随心邮-在微信里收发邮件,及时省电又安心</a>
*              sig-policy:  APNIC SIG on resource management policy           *
_______________________________________________
sig-policy mailing list
[email protected]
https://mailman.apnic.net/mailman/listinfo/sig-policy

Reply via email to