Alternatively, if ARIN starts billing LRSA+RSA organizations on the basis of MAX(IPv4, IPv6), I will also stop calling this double billing.

Mr. Delong – 

Organizations with legacy IPv4 resources and IPv6 number resources under a registration services plan are already being invoiced one amount based on the highest category of IPv4 / IPv6  - i.e. “on the basis of MAX(IPv4, IPv6)” as you put it. 

However, the “Fee Cap on IPv4 maintenance fees” provided to IPv4 legacy resource holders does not apply to such an amount invoiced because the customer is being invoiced for a registration services plan that contains multiple items [services for IPv4, IPv6, and ASN resources] that are more than just "IPv4 maintenance fees”.    Customers can keep their IPv4 resources in a separate billing relationship and then the “Fee Cap on IPv4 maintenance fees” will continue to be applied to their “IPv4 registry maintenance fees”, exactly as expected. 

At this point I’d suggest that we take this off the nanog mailing list - if you have further questions feel free to contact ARIN's Registration Services Helpdesk (Hours: 7 AM to 7 PM ET, Phone: +1.703.227.0660. https://www.arin.net/resources/guide/helpdesk/) 

Thanks! 

/John