<div dir="ltr"><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:large;color:rgb(0,0,0)">In support of the new policy wording re: swip requirements.</div><div class="gmail_default" style="font-family:"comic sans ms",sans-serif;font-size:large;color:rgb(0,0,0)"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small"> </span><a href="https://www.arin.net/policy/proposals/2017_5.html" rel="noreferrer" target="_blank" style="font-family:arial,sans-serif;font-size:small">https://www.arin.net/policy/<wbr>proposals/2017_5.html</a><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div dir="ltr"><br><div><font size="4"><span style="font-family:"comic sans ms",sans-serif">Rudi Daniel</span></font><br><div><font color="#006600"><span style="font-size:large"><b><br></b></span></font><div><span style="font-size:large"><br></span></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Aug 30, 2017 at 1:16 PM, <span dir="ltr"><<a href="mailto:arin-ppml-request@arin.net" target="_blank">arin-ppml-request@arin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send ARIN-PPML mailing list submissions to<br>
<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of ARIN-PPML digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: ARIN-PPML 2017-6 draft policy (Mike Burns)<br>
2. Re: ARIN-PPML 2017-6 draft policy (Andrew Sullivan)<br>
3. Fwd: Advisory Council Meeting Results - August 2017 (ARIN)<br>
4. Re: Revised/Retitled: Draft Policy ARIN-2017-5: Improved IPv6<br>
Registration Requirements (<a href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a>)<br>
5. Re: Revised/Retitled: Draft Policy ARIN-2017-5: Improved IPv6<br>
Registration Requirements (Jason Schiller)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 28 Aug 2017 14:14:33 -0400<br>
From: "Mike Burns" <<a href="mailto:mike@iptrading.com">mike@iptrading.com</a>><br>
To: "'Owen DeLong'" <<a href="mailto:owen@delong.com">owen@delong.com</a>><br>
Cc: "'Rudolph Daniel'" <<a href="mailto:rudi.daniel@gmail.com">rudi.daniel@gmail.com</a>>, <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] ARIN-PPML 2017-6 draft policy<br>
Message-ID: <001e01d32029$802458d0$<wbr>806d0a70$@<a href="http://iptrading.com" rel="noreferrer" target="_blank">iptrading.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Let?s not. This is a really bad idea and if we don?t put a stop to it now, it will likely never get corrected.<br>
<br>
<br>
<br>
Owen<br>
<br>
<br>
<br>
<br>
<br>
Hi Owen,<br>
<br>
<br>
<br>
In almost 5 years of inter-regional transfers, David Farmer identified two transfers of /22s from ARIN into a one-way situation.<br>
<br>
<br>
<br>
At this rate, if it doesn?t ?get corrected?, in just 32 years a whole ARIN /16 will have disappeared!<br>
<br>
Not really that bad.<br>
<br>
<br>
<br>
On the other hand, blocking all transfers to APNIC *is* a really bad idea, as is strong-arming that registry *again* through the threat of preventing access to ARIN address space.<br>
<br>
<br>
<br>
Regards,<br>
<br>
Mike<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20170828/902e6e0c/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.arin.net/<wbr>pipermail/arin-ppml/<wbr>attachments/20170828/902e6e0c/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 28 Aug 2017 14:51:58 -0400<br>
From: Andrew Sullivan <<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] ARIN-PPML 2017-6 draft policy<br>
Message-ID: <<a href="mailto:20170828185158.pdu5pp4zjwgn7ijy@mx4.yitter.info">20170828185158.<wbr>pdu5pp4zjwgn7ijy@mx4.yitter.<wbr>info</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
On Mon, Aug 28, 2017 at 02:14:33PM -0400, Mike Burns wrote:<br>
> Let?s not. This is a really bad idea and if we don?t put a stop to it now, it will likely never get corrected.<br>
<br>
What exactly needs to get corrected, then? You are arguing from a<br>
slippery slope, but nobody seems to be slipping.<br>
<br>
A<br>
<br>
<br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 29 Aug 2017 15:20:53 -0400<br>
From: ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] Fwd: Advisory Council Meeting Results - August<br>
2017<br>
Message-ID: <<a href="mailto:2ae92228-c1ad-6d03-5a37-15e08573b72b@arin.net">2ae92228-c1ad-6d03-5a37-<wbr>15e08573b72b@arin.net</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
> The AC has abandoned the following Draft Policy:<br>
><br>
> ARIN-2017-2: Removal of Community Networks<br>
><br>
> The AC provided the following statement:<br>
><br>
> "The ARIN Advisory Council has chosen to abandon Policy Proposal 2017-2, "Removal of Community Networks," due to lack of community support and the introduction of an alternative policy proposal to amend the definition of "community network."<br>
><br>
> Anyone dissatisfied with this decision may initiate a petition. The deadline to begin a petition will be five business days after the AC's draft meeting minutes are published.<br>
<br>
><br>
> The AC has abandoned the following Draft Policy:<br>
><br>
> ARIN-2017-7: Retire Obsolete Section 4 from the NRPM<br>
><br>
> The AC provided the following statement:<br>
><br>
> "The ARIN Advisory Council has chosen to abandon Policy Proposal 2017-7, ?Retire Obsolete Section 4 from the NRPM?. This proposal did not gain sufficient community support to justify continuing to move this policy forward, and as such, we have requested that the policy be abandoned."<br>
><br>
> Anyone dissatisfied with this decision may initiate a petition. The deadline to begin a petition will be five business days after the AC's draft meeting minutes are published.<br>
<br>
<br>
The minutes from the ARIN Advisory Council's 17 August 2017 meeting have<br>
been published:<br>
<br>
<a href="https://www.arin.net/about_us/ac/ac2017_0817.html" rel="noreferrer" target="_blank">https://www.arin.net/about_us/<wbr>ac/ac2017_0817.html</a><br>
<br>
The petition deadline for both Draft Policy ARIN-2017-2 and Draft Policy<br>
ARIN-2017-7 is 3 September 2017 (in five calendar days).<br>
<br>
For more information on starting and participating in petitions, see PDP<br>
Petitions at: <a href="https://www.arin.net/policy/pdp_petitions.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>pdp_petitions.html</a><br>
<br>
The ARIN Policy Development Process can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>pdp.html</a><br>
<br>
Draft Policy and Proposal texts are available at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/index.html</a><br>
<br>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: Advisory Council Meeting Results - August 2017<br>
Date: Tue, 22 Aug 2017 12:38:43 -0400<br>
From: ARIN <<a href="mailto:info@arin.net">info@arin.net</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
<br>
In accordance with the Policy Development Process (PDP), the Advisory<br>
Council (AC) met on 17 August 2017.<br>
<br>
<br>
<br>
The AC has abandoned the following Draft Policy:<br>
<br>
ARIN-2017-2: Removal of Community Networks<br>
<br>
The AC provided the following statement:<br>
<br>
"The ARIN Advisory Council has chosen to abandon Policy Proposal 2017-2,<br>
"Removal of Community Networks," due to lack of community support and<br>
the introduction of an alternative policy proposal to amend the<br>
definition of "community network."<br>
<br>
Anyone dissatisfied with this decision may initiate a petition. The<br>
deadline to begin a petition will be five business days after the AC's<br>
draft meeting minutes are published.<br>
<br>
<br>
<br>
The AC has abandoned the following Draft Policy:<br>
<br>
ARIN-2017-7: Retire Obsolete Section 4 from the NRPM<br>
<br>
The AC provided the following statement:<br>
<br>
"The ARIN Advisory Council has chosen to abandon Policy Proposal 2017-7,<br>
?Retire Obsolete Section 4 from the NRPM?. This proposal did not gain<br>
sufficient community support to justify continuing to move this policy<br>
forward, and as such, we have requested that the policy be abandoned."<br>
<br>
Anyone dissatisfied with this decision may initiate a petition. The<br>
deadline to begin a petition will be five business days after the AC's<br>
draft meeting minutes are published.<br>
<br>
<br>
<br>
The AC has advanced the following Proposal to Draft Policy status (will<br>
be posted separately for discussion):<br>
<br>
ARIN-prop-243: Amend the Definition of Community Network<br>
<br>
The AC advances Proposals to Draft Policy status once they are found to<br>
be within the scope of the PDP, and contain a clear problem statement<br>
and suggested changes to Internet number resource policy text.<br>
<br>
<br>
<br>
The AC is continuing to work on:<br>
<br>
* ARIN-2017-3: Update to NPRM 3.6: Annual Whois POC Validation<br>
* ARIN-2017-4: Remove Reciprocity Requirement for Inter-RIR Transfers<br>
* ARIN-2017-5: Improved IPv6 Registration Requirements<br>
* ARIN-2017-6: Improve Reciprocity Requirement for Inter-RIR Transfers<br>
<br>
The PDP can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>pdp.html</a><br>
<br>
Draft Policies and Proposals under discussion can be found at:<br>
<a href="https://www.arin.net/policy/proposals/index.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/index.html</a><br>
<br>
Regards,<br>
<br>
Sean Hopkins<br>
Policy Analyst<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 29 Aug 2017 21:02:46 -0400 (EDT)<br>
From: <a href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Revised/Retitled: Draft Policy ARIN-2017-5:<br>
Improved IPv6 Registration Requirements<br>
Message-ID: <Pine.LNX.4.64.1708292059250.<wbr>12663@localhost.localdomain><br>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed<br>
<br>
I think we got it this time.<br>
<br>
I support.<br>
<br>
Albert Erdmann<br>
Network Administrator<br>
Paradise On Line Inc.<br>
<br>
<br>
On Tue, 22 Aug 2017, ARIN wrote:<br>
<br>
> The following has been revised:<br>
><br>
> * Draft Policy ARIN-2017-5: Improved IPv6 Registration Requirements<br>
><br>
> Revised text is below and can be found at:<br>
> <a href="https://www.arin.net/policy/proposals/2017_5.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/2017_5.html</a><br>
><br>
> Note that the Draft Policy title has changed from "Equalization of Assignment<br>
> Registration requirements between IPv4 and IPv6"<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 stated in<br>
> the Policy Development Process (PDP). Specifically, these 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/policy/pdp.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>pdp.html</a><br>
><br>
> Draft Policies and Proposals under discussion can be found at:<br>
> <a href="https://www.arin.net/policy/proposals/index.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/index.html</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-2017-5: Improved IPv6 Registration Requirements<br>
><br>
> Problem Statement:<br>
><br>
> Current ARIN policy has different WHOIS directory registration requirements<br>
> for IPv4 vs IPv6 address assignments. IPv4 registration is triggered for an<br>
> assignment of any address block equal to or greater than a /29 (i.e., eight<br>
> IPv4 addresses). In the case of IPv6, registration occurs for an assignment<br>
> of any block equal to or greater than a /64, which constitutes one entire<br>
> IPv6 subnet and is the minimum block size for an allocation. Accordingly,<br>
> there is a significant disparity between IPv4 and IPv6 WHOIS registration<br>
> thresholds in the case of assignments, resulting in more work in the case of<br>
> IPv6 than is the case for IPv4. There is no technical or policy rationale for<br>
> the disparity, which could serve as a deterrent to more rapid IPv6 adoption.<br>
> The purpose of this proposal is to eliminate the disparity and corresponding<br>
> adverse consequences.<br>
><br>
> Policy statement:<br>
><br>
> 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to strike<br>
> "/64 or more addresses" and change to "/47 or more addresses, or<br>
> subdelegation of any size that will be individually announced,"<br>
><br>
> and<br>
><br>
> 2) Alter section 6.5.5.2. "Assignments visible within 7 days" of the NRPM to<br>
> strike the text "4.2.3.7.1" and change to "6.5.5.1"<br>
><br>
> and<br>
><br>
> 3) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM by<br>
> deleting the phrase "holding /64 and larger blocks"<br>
><br>
> and<br>
><br>
> 4) Add new section 6.5.5.4 "Registration Requested by Recipient" of the<br>
> NRPM, to read: "If the downstream recipient of a static assignment of /64 or<br>
> more addresses requests publishing of that assignment in ARIN's registration<br>
> database, the ISP must register that assignment as described in section<br>
> 6.5.5.1."<br>
><br>
> Comments:<br>
><br>
> a. Timetable for implementation:<br>
><br>
> Policy should be adopted as soon as possible.<br>
><br>
><br>
> b. Anything else:<br>
><br>
> Author Comments: IPv6 should not be more burdensome than the equivalent IPv4<br>
> network size. Currently, assignments of /29 or more of IPv4 space (8<br>
> addresses) require registration. The greatest majority of ISP customers who<br>
> have assignments of IPv4 space are of a single IPv4 address which do not<br>
> trigger any ARIN registration requirement when using IPv4. This is NOT true<br>
> when these same exact customers use IPv6, as assignments of /64 or more of<br>
> IPv6 space require registration. Beginning with RFC 3177, it has been<br>
> standard practice to assign a minimum assignment of /64 to every customer end<br>
> user site, and less is never used. This means that ALL IPv6 assignments,<br>
> including those customers that only use a single IPv4 address must be<br>
> registered with ARIN if they are given the minimum assignment of /64 of IPv6<br>
> space. This additional effort may prevent ISP's from giving IPv6 addresses<br>
> because of the additional expense of registering those addresses with ARIN,<br>
> which is not required for IPv4. The administrative burden of 100% customer<br>
> registration of IPv6 customers is unreasonable, when such is not required for<br>
> those customers receiving only IPv4 connections.<br>
> ______________________________<wbr>_________________<br>
> 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">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
><br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 30 Aug 2017 13:15:41 -0400<br>
From: Jason Schiller <<a href="mailto:jschiller@google.com">jschiller@google.com</a>><br>
To: <a href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a><br>
Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Revised/Retitled: Draft Policy ARIN-2017-5:<br>
Improved IPv6 Registration Requirements<br>
Message-ID:<br>
<<a href="mailto:CAC4yj2VHVaLzjyLxJ7%2BF67AL7_MaTy%2B%2BFyrDUR%2B_6iN0y6GHzw@mail.gmail.com">CAC4yj2VHVaLzjyLxJ7+F67AL7_<wbr>MaTy++FyrDUR+_6iN0y6GHzw@mail.<wbr>gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
The new policy (along with pre-existing text) will read as follows:<br>
<br>
6.5.5.1. Reassignment information<br>
Each static IPv6 assignment containing a /47 or more addresses, or<br>
subdelegation<br>
of any size that will be individually announced, shall be registered in the<br>
WHOIS<br>
directory via SWIP or a distributed service which meets the standards set<br>
forth in section 3.2. Reassignment registrations shall include each<br>
client's<br>
organizational information, except where specifically exempted by this<br>
policy.<br>
<br>
6.5.5.2. Assignments visible within 7 days<br>
All assignments shall be made visible as required in section 6.5.5.1 within<br>
seven<br>
calendar days of assignment.<br>
<br>
6.5.5.3. Residential Subscribers<br>
6.5.5.3.1. Residential Customer Privacy<br>
To maintain the privacy of their residential customers, an organization<br>
with downstream<br>
residential customers may substitute that organization's name for the<br>
customer's name,<br>
e.g. 'Private Customer - XYZ Network', and the customer's street address<br>
may read<br>
'Private Residence'. Each private downstream residential reassignment must<br>
have<br>
accurate upstream Abuse and Technical POCs visible on the WHOIS record for<br>
that<br>
block.<br>
<br>
6.5.5.4 Registration Requested by Recipient<br>
If the downstream recipient of a static assignment of /64 or more addresses<br>
requests<br>
publishing of that assignment in ARIN's registration database, the ISP must<br>
register<br>
that assignment as described in section 6.5.5.1.<br>
<br>
<br>
<br>
On Tue, Aug 29, 2017 at 9:02 PM, <<a href="mailto:hostmaster@uneedus.com">hostmaster@uneedus.com</a>> wrote:<br>
<br>
> I think we got it this time.<br>
><br>
> I support.<br>
><br>
> Albert Erdmann<br>
> Network Administrator<br>
> Paradise On Line Inc.<br>
><br>
><br>
><br>
> On Tue, 22 Aug 2017, ARIN wrote:<br>
><br>
> The following has been revised:<br>
>><br>
>> * Draft Policy ARIN-2017-5: Improved IPv6 Registration Requirements<br>
>><br>
>> Revised text is below and can be found at:<br>
>> <a href="https://www.arin.net/policy/proposals/2017_5.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/2017_5.html</a><br>
>><br>
>> Note that the Draft Policy title has changed from "Equalization of<br>
>> Assignment Registration requirements between IPv4 and IPv6"<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 stated<br>
>> in the Policy Development Process (PDP). Specifically, these 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/policy/pdp.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>pdp.html</a><br>
>><br>
>> Draft Policies and Proposals under discussion can be found at:<br>
>> <a href="https://www.arin.net/policy/proposals/index.html" rel="noreferrer" target="_blank">https://www.arin.net/policy/<wbr>proposals/index.html</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-2017-5: Improved IPv6 Registration Requirements<br>
>><br>
>> Problem Statement:<br>
>><br>
>> Current ARIN policy has different WHOIS directory registration<br>
>> requirements for IPv4 vs IPv6 address assignments. IPv4 registration is<br>
>> triggered for an assignment of any address block equal to or greater than a<br>
>> /29 (i.e., eight IPv4 addresses). In the case of IPv6, registration occurs<br>
>> for an assignment of any block equal to or greater than a /64, which<br>
>> constitutes one entire IPv6 subnet and is the minimum block size for an<br>
>> allocation. Accordingly, there is a significant disparity between IPv4 and<br>
>> IPv6 WHOIS registration thresholds in the case of assignments, resulting in<br>
>> more work in the case of IPv6 than is the case for IPv4. There is no<br>
>> technical or policy rationale for the disparity, which could serve as a<br>
>> deterrent to more rapid IPv6 adoption. The purpose of this proposal is to<br>
>> eliminate the disparity and corresponding adverse consequences.<br>
>><br>
>> Policy statement:<br>
>><br>
>> 1) Alter section 6.5.5.1 "Reassignment information" of the NRPM to strike<br>
>> "/64 or more addresses" and change to "/47 or more addresses, or<br>
>> subdelegation of any size that will be individually announced,"<br>
>><br>
>> and<br>
>><br>
>> 2) Alter section 6.5.5.2. "Assignments visible within 7 days" of the NRPM<br>
>> to strike the text "4.2.3.7.1" and change to "6.5.5.1"<br>
>><br>
>> and<br>
>><br>
>> 3) Alter section 6.5.5.3.1. "Residential Customer Privacy" of the NRPM by<br>
>> deleting the phrase "holding /64 and larger blocks"<br>
>><br>
>> and<br>
>><br>
>> 4) Add new section 6.5.5.4 "Registration Requested by Recipient" of the<br>
>> NRPM, to read: "If the downstream recipient of a static assignment of /64<br>
>> or more addresses requests publishing of that assignment in ARIN's<br>
>> registration database, the ISP must register that assignment as described<br>
>> in section 6.5.5.1."<br>
>><br>
>> Comments:<br>
>><br>
>> a. Timetable for implementation:<br>
>><br>
>> Policy should be adopted as soon as possible.<br>
>><br>
>><br>
>> b. Anything else:<br>
>><br>
>> Author Comments: IPv6 should not be more burdensome than the equivalent<br>
>> IPv4 network size. Currently, assignments of /29 or more of IPv4 space (8<br>
>> addresses) require registration. The greatest majority of ISP customers who<br>
>> have assignments of IPv4 space are of a single IPv4 address which do not<br>
>> trigger any ARIN registration requirement when using IPv4. This is NOT true<br>
>> when these same exact customers use IPv6, as assignments of /64 or more of<br>
>> IPv6 space require registration. Beginning with RFC 3177, it has been<br>
>> standard practice to assign a minimum assignment of /64 to every customer<br>
>> end user site, and less is never used. This means that ALL IPv6<br>
>> assignments, including those customers that only use a single IPv4 address<br>
>> must be registered with ARIN if they are given the minimum assignment of<br>
>> /64 of IPv6 space. This additional effort may prevent ISP's from giving<br>
>> IPv6 addresses because of the additional expense of registering those<br>
>> addresses with ARIN, which is not required for IPv4. The administrative<br>
>> burden of 100% customer registration of IPv6 customers is unreasonable,<br>
>> when such is not required for those customers receiving only IPv4<br>
>> connections.<br>
>> ______________________________<wbr>_________________<br>
>> 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">ARIN-PPML@arin.net</a>).<br>
>> Unsubscribe or manage your mailing list subscription at:<br>
>> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
>> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
>><br>
>> ______________________________<wbr>_________________<br>
> 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">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
><br>
<br>
<br>
<br>
--<br>
______________________________<wbr>_________________________<br>
Jason Schiller|NetOps|<a href="mailto:jschiller@google.com">jschiller@<wbr>google.com</a>|<a href="tel:571-266-0006" value="+15712660006">571-266-0006</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20170830/4b635cb3/attachment.html" rel="noreferrer" target="_blank">http://lists.arin.net/<wbr>pipermail/arin-ppml/<wbr>attachments/20170830/4b635cb3/<wbr>attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/arin-ppml</a><br>
<br>
------------------------------<br>
<br>
End of ARIN-PPML Digest, Vol 146, Issue 25<br>
******************************<wbr>************<br>
</blockquote></div><br></div></div>