<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I also support the spirit of this policy, but have some questions.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Would the adoption of this policy mean that leased-out addresses would meet the requirements to demonstrate efficient use of prior allocations when requesting a new transfer?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Would lease contracts with Lessees meet the requirements for demonstrating ongoing and future needs?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Could I purchase addresses on the transfer market and justify them with leases?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Should we define the terms of a lease in policy and adopt certain requirements?<o:p></o:p></p><p class=MsoNormal>I think we should, and hope this discussion continues.<o:p></o:p></p><p class=MsoNormal>I believe we should treat leases in the same manner as assignments to connected-networks in justifications, but there should be requirements for those leases developed by the community to ensure registration, for example SWIP and LOA with explicit permission for specified ASNs to advertise the leased block.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the meantime I approve Scott’s edit.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal>Mike<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>From:</b> ARIN-PPML <arin-ppml-bounces@arin.net> <b>On Behalf Of </b>Scott Leibrand<br><b>Sent:</b> Tuesday, September 24, 2019 4:58 PM<br><b>To:</b> ARIN <info@arin.net><br><b>Cc:</b> ARIN-PPML List <arin-ppml@arin.net><br><b>Subject:</b> Re: [arin-ppml] Draft Policy ARIN-2019-18: LIR/ISP Re-Assignment to Non-Connected Networks<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I support the spirit of this policy.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I'm not sure the Option 2 edits to 8.5.2 Operational Use would have the intended effect. It reads that "ARIN ... may allocate or assign number resources to organizations for other<o:p></o:p></p></div><p class=MsoNormal>purposes, including re-assignment to non-connected networks", which doesn't require ARIN to change policy in any way, nor AFAICT does it conform to the proposed 2.4 language that "LIRs may also assign address space to other organizations or customers that request it for use in an operational network."<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Perhaps something like this would accomplish the desired ends?<br><br>8.5.2 Operational Use<br><br>ARIN allocates or assigns number resources to organizations via transfer solely for the purpose of use on, or reallocation/reassignment to, operational networks.<o:p></o:p></p></div><div><p class=MsoNormal>-Scott<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Sep 24, 2019 at 1:41 PM ARIN <<a href="mailto:info@arin.net">info@arin.net</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>On 19 September 2019, the ARIN Advisory Council (AC) accepted <br>"ARIN-prop-277: LIR/ISP Re-Assignment to Non-Connected Networks" as a <br>Draft Policy.<br><br>Draft Policy ARIN-2019-18 is below and can be found at:<br><br><a href="https://www.arin.net/participate/policy/drafts/2019_18/" target="_blank">https://www.arin.net/participate/policy/drafts/2019_18/</a><br><br>You are encouraged to discuss all Draft Policies on PPML. The AC will <br>evaluate the discussion in order to assess the conformance of this draft <br>policy with ARIN's Principles of Internet number resource policy as <br>stated in the Policy Development Process (PDP). Specifically, these <br>principles are:<br><br>* Enabling Fair and Impartial Number Resource Administration<br>* Technically Sound<br>* Supported by the Community<br><br>The PDP can be found at:<br><a href="https://www.arin.net/participate/policy/pdp/" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br><br>Draft Policies and Proposals under discussion can be found at:<br><a href="https://www.arin.net/participate/policy/drafts/" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br><br>Regards,<br><br>Sean Hopkins<br>Policy Analyst<br>American Registry for Internet Numbers (ARIN)<br><br><br><br>Draft Policy ARIN-2019-18: LIR/ISP Re-Assignment to Non-Connected Networks<br><br>Problem Statement:<br><br>Businesses have a need to lease IPv4 space for limited periods of time, <br>as evidenced by a robust (technically prohibited) subleasing market. The <br>lack of legitimization of the subleasing market hinders innovation, <br>research, reporting, and the development of rules/industry best <br>practices to ensure identifiability and contactability.<br><br>Policy statement:<br><br>ORIGINAL POLICY LANGUAGE<br><br>2.4. Local Internet Registry (LIR)<br><br>A Local Internet Registry (LIR) is an IR that primarily assigns address <br>space to the users of the network services that it provides. LIRs are <br>generally Internet Service Providers (ISPs), whose customers are <br>primarily end users and possibly other ISPs.<br><br>PROPOSED POLICY LANGUAGE<br><br>A Local Internet Registry (LIR) is an IR that primarily assigns address <br>space to the users of the network services that it provides. LIRs are <br>generally Internet Service Providers (ISPs), whose customers are <br>primarily end users and possibly other ISPs.<br><br>LIRs may also assign address space to other organizations or customers <br>that request it for use in an operational network.<br><br>ORIGINAL POLICY LANGUAGE<br><br>8.5.2 Operational Use<br><br>ARIN allocates or assigns number resources to organizations via transfer <br>solely for the purpose of use on an operational network.<br><br>PROPOSED POLICY LANGUAGE<br><br>Option 1 : Remove 8.5.2 entirely<br><br>Option 2 : Edit as follows<br><br>8.5.2 Operational Use<br><br>ARIN allocates or assigns number resources to organizations via transfer <br>solely primarily for the purpose of use on an operational network, but <br>may allocate or assign number resources to organizations for other <br>purposes, including re-assignment to non-connected networks .<br><br>Comments:<br><br>Timetable for implementation: Immediate<br><br>Anything Else:<br><br>The legitimization of a subleasing market for IPv4 has numerous business <br>and community benefits, including (but not limited to):<br><br>- Allowing organizations to efficiently utilize IPv4 space without <br>transferring space permanently;<br>- Allowing organizations to obtain IPv4 space for a limited time in <br>order to facilitate transition to IPv6;<br>- Allowing organizations to develop enforceable acceptable use policies <br>in a previously lawless illegitimate space;<br>- Allowing the community to develop reporting and recording standards <br>and/or best practices to the benefit of preserving the integrity of IPv4 <br>address space.<br>- We would like to engage further with the ARIN community to discuss the <br>current state of the unauthorized subleasing market, and how this <br>proposed policy change would both update ARIN policies to reflect the <br>reality of the subleasing market, and positively address business and <br>community concerns.<br><br>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<o:p></o:p></p></blockquote></div></div></body></html>