[arin-ppml] IPv6 whois/SWIP/privacy policy

[Scott Leibrand]

On 12/29/2009 3:32 PM, Steve Bertrand wrote:
> Member Services wrote:
>
>    
>> 6.3.1. Residential Customer Privacy ''(Copied from NRPM 6.5.5.1)''
>>
>> To maintain the privacy of their residential customers, an organization
>> with downstream residential customers may substitute that organization's
>> name for the customer's name, e.g. 'Private Customer - XYZ Network', and
>> the customer's street address may read 'Private Residence'. Each private
>> downstream residential reassignment must have accurate upstream Abuse
>> and Technical POCs visible on the WHOIS record for that block.
>>      
> Looking for a little clarification...
>
> If I'm either lazy, or otherwise feel that NONE of my residential
> clients require a SWIP entry, does this piece of the policy allow me to
> reserve a portion of my /32 (eg. /44) for residential clients and SWIP
> the entire thing as a whole as 'Private Customer Block - XYZ Network' as
> opposed to SWIPing each individual /56 as private?
>    

I'm trying not to propose any changes to whois/SWIP/privacy policy, as 
that is an entirely different can of worms.  Owen has already mentioned 
that he thinks we need to change existing IPv6 whois/SWIP/privacy 
policy.  Perhaps this new thread would be a good opportunity to discuss 
ideas about how to do so?  To get the discussion started, here are the 
IPv4 and IPv6 sections of the existing NRPM:

https://www.arin.net/policy/nrpm.html#four237

> 4.2.3.7. Reassignment information
> 4.2.3.7.1. Customer organization information
>
> ISPs are required to demonstrate efficient use of IP address space 
> allocations by providing appropriate documentation, including 
> assignment histories, showing their efficient use. SWIP and RWHOIS 
> reassignments should show each client's organizational information.
> 4.2.3.7.2. /29s and larger nets
>
> ISPs must provide reassignment information on the entire previously 
> allocated block(s) via SWIP or RWHOIS server for /29 or larger blocks. 
> For blocks smaller than /29 and for internal space, ISPs should 
> provide utilization data via SWIP or RWHOIS server or by using the 
> format described in Section 4.2.3.7.5.
> 4.2.3.7.3. Submit within 7 days
>
> Any time an ISP receives a new block of address space, reassignment 
> information should be submitted within 7 days of issuance of the new 
> space. This information is used to demonstrate that the address space 
> received is being efficiently utilized. Also, it will be reviewed to 
> determine an ISP's and its downstream customers' utilization 
> effectiveness if and when additional space is requested in the future.
> 4.2.3.7.4. Visible via WHOIS
>
> This information must be visible via WHOIS prior to submitting a 
> request for a new allocation. For further information on reassigning 
> IP address space, please see RFC 2050.
> 4.2.3.7.5. Accounting for additional utilization
>
> The following format should be used to provide the required 
> information for utilization of blocks smaller than /29 and for 
> describing internal networks when either SWIP or RWHOIS server is not 
> used:
> City     Which IP Addresses Assigned     No. of Ports     No. of 
> Dial-up Clients
> City     Which IP Addresses Assigned     No. of Internal Machines     
> Purpose
> Which IP Addresses Assigned     List URLs for Websites
> 4.2.3.7.6. Residential Customer Privacy
>
> To maintain the privacy of their residential customers, an 
> organization with downstream residential customers may substitute that 
> organization's name for the customer's name, e.g. 'Private Customer - 
> XYZ Network', and the customer's street address may read 'Private 
> Residence'. Each private downstream residential reassignment must have 
> accurate upstream Abuse and Technical POCs visible on the WHOIS record 
> for that block.



https://www.arin.net/policy/nrpm.html#six55

> 6.5.5. Registration
>
> When an organization holding an IPv6 address allocation makes IPv6 
> address assignments, it must register assignment information in a 
> database, accessible by RIRs as appropriate (information registered by 
> an RIR/NIR may be replaced by a distributed database for registering 
> address management information in future). Information is registered 
> in units of assigned /56 networks. When more than a /56 is assigned to 
> an organization, the assigning organization is responsible for 
> ensuring that the address space is registered in an RIR/NIR database.
>
> RIR/NIRs will use registered data to calculate the HD-Ratio at the 
> time of application for subsequent allocation and to check for changes 
> in assignments over time.
>
> IRs shall maintain systems and practices that protect the security of 
> personal and commercial information that is used in request 
> evaluation, but which is not required for public registration.
> 6.5.5.1. Residential Customer Privacy (2003-3)
>
> To maintain the privacy of their residential customers, an 
> organization with downstream residential customers may substitute that 
> organization's name for the customer's name, e.g. 'Private Customer - 
> XYZ Network', and the customer's street address may read 'Private 
> Residence'. Each private downstream residential reassignment must have 
> accurate upstream Abuse and Technical POCs visible on the WHOIS record 
> for that block.

-Scott