Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Proposal Update received: Clarification on temporary resource usage

JORDI PALET MARTINEZ jordi.palet at consulintel.es
Tue May 14 11:47:32 UTC 2019


Hi Willy, all,

I still think I've disagreements with the actual text, so providing a detailed review.

---
0) You don't have this text in the proposal, so I'm guessing you keep it:

In some circumstances, organisations may require IP resources for a certain period of time, usually one month and less. This could be for exhibitions, conferences, conventions, etc.

AFRINIC will therefore assign numbering resources to entities requiring temporary IP numbers for a fixed period of time. In this document, "IP resources" refers to unicast IPv4/v6 addresses and AS numbers.

I will suggest to update it a bit and because we are talking also about experiments, make a special condition for those:

In some circumstances, end-user organisations may require numbering resources for a certain period of time, usually a month or less. This could be for exhibitions, conferences, conventions, etc. Longer assignments may be needed for well documented experiments.

AFRINIC will therefore assign numbering resources to entities requiring them for a specific period of time. In this document, number resources refers to IPv4/IPv6 addresses and AS numbers.
---

---
1) The activity requiring temporary IP resources should be publicly documented and available on a website reachable at least from the time of submission of the resource request and during the entire period of the event. A "publicly accessible document" is a document that is publicly and openly available free of charge and free of any constraints of disclosure. AFRINIC will not recognize any activity under this policy if such an activity cannot be publicly disclosed.

Entities requiring such IP resources are expected to demonstrate an understanding that when the activity or experiment for which they require the IP resources ends, the IP resources will be returned to AFRINIC.
---

I think it is perfect valid to have a close meeting with non-public information, that don't have a public web-site. I think what it is good, as the temporary resource is provided by the community, is that AFRINIC host that information in a web page for historical reasons, so not the entity that request it.

My proposal is to make it shorter (no need to explain what is a public document, either to say is free of charge, etc., all the Afrinic publications are that way):
For historical and justifications/transparency reasons, AFRINIC will publish a document reporting the temporary activity. In case of a non-open activity, the publication may be done after the activity is concluded and only with the non-confidential details.
Entities requiring such numbering resources are expected to demonstrate an understanding that when the activity or experiment for which they require the numbering resources ends, those will be returned to AFRINIC

---
2) a.  Resources are assigned on a lease basis for a maximum period of one month. The assignment can be renewed on application to AFRINIC providing the necessary information.

Suggested change:

a.  Resources are assigned on a lease basis for a maximum period of one month. The assignment can be renewed on application to AFRINIC providing the necessary information. In case of experiments, the documentation will justify the required period of time.
---

3) b.  The size of the IP resource to be assigned will be determined from the plan submitted by the requesting entity, but will not exceed /22. The requesting entity is instead advised to use IPv6-only on their networks and deploy an IPv6 transition mechanism such as 464XLAT if necessary.

Suggested (avoid repetitions of technical details which are in section 9.3):

b.  The size of the numbering resources to be assigned will be determined from the plan submitted by the requesting entity. In the case of IPv4, will not exceed /22.
---

4) 9.3 Technical recommendations

a. The requesting entity is encouraged to deploy IPv6-only networks and a transition mechanism such as 464XLAT if necessary.

b. The requesting entity could base its architecture from some RFCs such as:

i. [rfc3750] (INFORMATIONAL) Unmanaged Networks for IPv6 Transition Scenarios

ii. [rfc4213] (Standards Track) Basic Transition Mechanisms for IPv6 Hosts and Routers

iii. [rfc6180] (INFORMATIONAL) Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment

Suggested:

9.3 Technical recommendations

a. The requesting entity is encouraged to deploy IPv6-only networks and an IPv4aaS (IPv4-as-a-Service transition mechanism), such as 464XLAT if necessary.

b. The requesting entity could base its architecture from some RFCs such as:

i. [rfc3750] (INFORMATIONAL) Unmanaged Networks for IPv6 Transition Scenarios
-> Note that I think this document is not anymore useful at all and a conference network is not UNMANAGED. I will not use it as a valid reference.

ii. [rfc4213] (Standards Track) Basic Transition Mechanisms for IPv6 Hosts and Routers
-> Same as above, this is 6in4, not useful anymore if we are talking about IPv6-only!

iii. [rfc6180] (INFORMATIONAL) Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment
-> good, this document is going to be updated by https://datatracker.ietf.org/doc/draft-lmhp-v6ops-transition-comparison/ which is precisely about IPv6-only and IPv4aaS

Add this reference: RFC8585 and https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/ (passed the last call, by the time this policy is implemented, it should be an RFC already, staff can update that text once published - editorial changes can be done outside of the PDP)


Regards,
Jordi
 
 

El 20/4/19 17:43, "Dewole Ajao" <dewole at forum.org.ng> escribió:

    Dear PDWG members,
    
    This is to inform you that authors of the policy proposal named 
    "Clarification on temporary resource usage" have submitted an updated 
    version (Draft version 2) as published online at 
    https://afrinic.net/policy/proposals/2018-gen-004-d2
    
    Please take some time to go through the proposal contents and provide 
    your feedback.
    
    Thank you.
    PDWG Co-Chairs
    
    
    
    _______________________________________________
    RPD mailing list
    RPD at afrinic.net
    https://lists.afrinic.net/mailman/listinfo/rpd
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.






More information about the RPD mailing list