Hello All,
This post is to address Fernando Frediani's concerns he has identified on v001 of the proposal on the mailing list, which in my view aren't specifically related to the version itself, rather to the proposal as a whole (and aren't affected by the changes applied incorporating the Secretariat Impact Assessment). it doesn't sound something that deserves a special condition At the moment, there is nothing that allows for the temporary assignment for the purposes specified in the proposal. APNIC are restricted as to what they can and cannot do when it comes to assigning resources so if the policy does not permit it they aren't allowed to do it. Also all the stuff related to allocating ASN, IP space, update IRR, Geolocation, etc for a short terms things doesn't seem to justify having a policy just for that. Members can apply for the temporary assignments for a time period of up to 6 months, which would be ample time for these issues to be addressed. To my knowledge, the only thing that would take some time to resolve would be geolocation, which the member may not consider to be an issue. If I understand correctly this would apply to APNIC run events Nothing in this proposal indicates that this is for APNIC events as it talks about assignments to members. APRICOT and APNIC already have a total of a /20 v4 prefix and /32 v6 prefix assigned (see https://apricot.net/ops/network.html) for use during conferences and workshops. it is mentioned NOG events as well which goes outside the scope of the RIR While you are correct that the operations of NOG events are outside the scope of RIR operations, this has no bearing on the proposal itself or its intentions. NOG events are simply an example as to where resource assignments under this policy can be used. I like the idea of RIRs having critical infrastructure pool APNIC already has a policy for critical infrastructure assignments, see https://www.apnic.net/community/policy/resources#a_h_6_2_3 and https://www.apnic.net/community/policy/resources#a_h_9_1_2 which details these policies. for very special and well defined usages and RIR own usage can be one of them, but anything else, including events, conferences, etc The purposes under this policy, and what you've defined, would not be considered "critical infrastructure". non-profit should should count with commercial (paid or for free) solutions available in the market Non-profit organisations may not have the financial capacity to pay out $1000's (if not $100's) for services that may only be used for a few weeks. Similar situation for smaller training events which may have less than 50 users which may be the case in LDCs. In general event broadband doesn't require much IPv4 Public addresses It would be good to know how you came to this conclusion. If you take a look at the APRICOT Technical Requirements page, you'll note that they use a total of a /20 v4 and /32 v6. Some smaller conferences and such may not require as many resources which is why this policy only allows for a /21 v4 to be reserved, and members can apply for an assignment shorter than a /24 with justification. can well be served by a solution like CGNAT + IPv6 or 464XLAT which require much fewer IPv4 that can be supplied by any commercial provider in temporary basis, even during these IPv4 exhaustion times. In many cases, CGNAT or 464XLAT isn't viable for larger conferences. Many attendees who provide support for their networks back home while attending the conference (I believe) would agree it's not wise or smart to whitelist an IP address that is in use by 100's of people, whereas by allocating public addresses directly to end devices it allows them to whitelist their specific device addresses. It is akin to whitelisting the public IP address of the WiFi network at your favourite cafe, which IMO is a big no-no. Hopefully my reply addresses your concerns. I look forward to hearing from you. Regards, Christopher Hawker
_______________________________________________ SIG-policy - https://mailman.apnic.net/[email protected]/ To unsubscribe send an email to [email protected]
