Um, did IETF delegate 240/4 to IANA to manage at all?

Seems to me that we would first need an RFC to do that (or one which amends 
RFC-1918 to add 240/4 to it, taking IANA out of the loop).

Since I don’ t think there’s a benefit to having IANA in the loop and I think 
we’d need IETF action on the matter to proceed anyway, I don’t see an advantage 
to adding IANA to the mix.

Owen


> On May 16, 2019, at 7:34 PM, David Farmer <[email protected]> wrote:
> 
> I suppose we could try a global policy that would have to pass in all 5 RIRs 
> requesting IANA and the IETF to allocate 240/4 for Private Use. If that were 
> to actually occur, it seems difficult for the IETF to ignore such a request. 
> While on the other hand, I'm not sure there would be a consensus within the 
> ARIN community, let alone the other RIRs, to do such a thing anyway. 
> Nevertheless, there is no way for ARIN to unilaterally allocate 240/4 for any 
> purpose.
> 
> On Thu, May 16, 2019 at 21:09 Mark Andrews <[email protected] 
> <mailto:[email protected]>> wrote:
> 240/4 isn’t ARIN’s to allocate or do you think ARIN should squat on the 
> space? :-)
> 
> > On 17 May 2019, at 11:48 am, Michel Py <[email protected] 
> > <mailto:[email protected]>> wrote:
> > 
> >> Joe Provo wrote :
> >> By all means, go tilt at the class e windmill if you like;
> >> it will only be the fourth time or so, I can't recall.
> > 
> > I was trying to convince Owen to co-author with me ;-)
> > 
> >> But it isn't anything for ARIN policy, so feel free to take it up at the 
> >> IETF...
> > 
> > I would not waste more time there.
> > ARIN is the entity having the squatting problem : we have members who use 
> > the resources of another member and they should not.
> > 
> > There is precedent, Owen will remember that I'm sure. During the early 
> > days, there was no IPv6 multi-homing solution. The RIRs, not the IETF, 
> > started to allocate IPv6 PI addresses to organizations who wanted to 
> > multi-home, while there was no such thing as IPv6 PI. I remember that the 
> > IETF was not happy with that, but it worked : since then, we have IPv6 
> > multi-homing, the good old way that works, not any of the dirty hacks that 
> > were on the table at the time.
> > 
> > ARIN allocates 240/4 for private unicast to ARIN members.
> > Maybe we could convince Geoff and APNIC to try the alternative way.
> > Long shot, I know.
> > 
> > Owen, you allow your vision of "all IPv6" to cloud your judgment. Turning 
> > IPv4 off is not going to happen for decades.
> > 
> > Michel.
> > 
> > _______________________________________________
> > ARIN-PPML
> > You are receiving this message because you are subscribed to
> > the ARIN Public Policy Mailing List ([email protected] 
> > <mailto:[email protected]>).
> > Unsubscribe or manage your mailing list subscription at:
> > https://lists.arin.net/mailman/listinfo/arin-ppml 
> > <https://lists.arin.net/mailman/listinfo/arin-ppml>
> > Please contact [email protected] <mailto:[email protected]> if you experience any 
> > issues.
> 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: [email protected] 
> <mailto:[email protected]>
> 
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected] 
> <mailto:[email protected]>).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml 
> <https://lists.arin.net/mailman/listinfo/arin-ppml>
> Please contact [email protected] <mailto:[email protected]> if you experience any 
> issues.
> -- 
> ===============================================
> David Farmer               Email:[email protected] 
> <mailto:email%[email protected]>
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota   
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
> _______________________________________________
> ARIN-PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.

_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to