<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div dir="auto">{<i>...much arguments => long mail :-/</i>}
<div dir="auto"><br>
<div dir="auto">Hi all,</div>
<div dir="auto">Hoping that this mail finds y'all in good
health, please see my comments inline...<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr">Le ven. 21 déc. 2018 8:20 AM, Ernest
Byaruhanga <<a href="mailto:ernest@afrinic.net"
rel="noreferrer noreferrer noreferrer noreferrer
noreferrer noreferrer noreferrer" target="_blank">ernest@afrinic.net</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A new policy proposal has been received:<br>
<br>
Title: Clarification on temporary resource usage<br>
ID:AFPUB-2018-GEN-004-DRAFT01<br>
Author: Manga Willy Ted<br>
URL: <a
href="https://afrinic.net/policy/2018-gen-004-d1#proposal"
rel="noreferrer noreferrer noreferrer noreferrer
noreferrer noreferrer noreferrer noreferrer noreferrer"
target="_blank">https://afrinic.net/policy/2018-gen-004-d1#proposal</a><br>
<br>
The proposal introduces modifications to CPM 9.0 which
deals with issuance of number resources for temporary use
(such as for conferences and experiments).<br>
<br>
The proposal has been published at : <br>
<a
href="https://afrinic.net/policy/2018-gen-004-d1#proposal"
rel="noreferrer noreferrer noreferrer noreferrer
noreferrer noreferrer noreferrer noreferrer noreferrer"
target="_blank">https://afrinic.net/policy/2018-gen-004-d1#proposal</a>
<br>
(Text in orange color depicts changes to current policy
text)<br>
<br>
<br>
Plain text version:<br>
<br>
————————————<br>
Clarification on temporary resource usage <br>
————————————<br>
<br>
1.0 Summary of the problem being addressed by this
proposal<br>
<br>
With IPv4 exhaustion coming, IPv4 resource assignments
need better management because of scarcity. For instance,
what happens if some entities request a /20 worth of IPv4
for temporary usage during soft landing phase 2? </blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">...it seems as the softlanding policy [1] is
already covering this situation...or not ? :-/</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">With
current IPv6 evolution, we think entities requesting
temporary resources should deploy more IPv6 prefixes than
IPv4 prefixes.<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">...i may be wrong, but i don't really understand
why RPD activities (or an IP policy) could|should deal with
(or focus on) IPv6 operational deployment :-/</div>
<div dir="auto"><br>
</div>
<div dir="auto">...because that is what it seems to me.</div>
<div dir="auto"><br>
</div>
<div dir="auto">IMHO the problem statement must be in line with
RPD possibilities|missions. </div>
<div dir="auto">So i recommend to rephrase it ; in order to
first remove *operational* considerations here... </div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
2.0 Summary of how this proposal addresses the problem<br>
<br>
This proposal aims to restrict the size of IPv4 resource
requests for temporary use such as conferences and
meetings and in addition, </blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I tend to aggree, but there is a remaining
question : Is the proposed restriction, of IPv4 prefix, really
needed ? as we already have a softlanding policy [1] as
mentionned by the actual text of CPM (v1.3) [2] section 9.0...</div>
<div dir="auto"><br>
</div>
<div dir="auto">...convince me please :-)</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">encourages
IPv6 usage for those purposes. We believe that IPv6 is now
mature enough to be deployed for this kind of usage.<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Ok ! now, the challenge, here, should be first
to stay on the scope [3] of RPD's good practices for policy
writing...</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Any IPv4
space requested for temporary usage should not be more
than /22 - especially for meetings and events.</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">...the actual section 9.0 of the CPM (v1.3)
clearly states that there are other types of usages (<i>experiments</i>)
for temporary resources. You can think of a R&D project,
or a serie of tests for network application, to figure which
kind of experiments such organization can wish to realize...</div>
<div dir="auto"><br>
</div>
<div dir="auto">...then try to answer this question : </div>
<div dir="auto">Why must we especially restrict the prefix of
temporary ressource usages ? in other words</div>
<div dir="auto"><br>
</div>
<div dir="auto">Why are we really needing to restrict the IPv4
prefix that could be assigned for temporary usage ? or</div>
<div dir="auto"><br>
</div>
<div dir="auto">Is it really necessary to restrict the IPv4
prefix an entity can request for temporary usage ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Even if yes : how could we better achieve that
when considering other usages like experiments from researches
entities including temporary Internet measurements activities
(for example) ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> The
requesting entity should use IPv6-only on their networks
and deploy IPv4 at the edge of the network using an IPv6
transition mechanism.<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">...i see this as an interference with BCOPs
style recommandations then out of the RPD scope [3] IMHO :-/</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Lastly, we believe the title of this section of the CPM
should reflect exactly the fact that we are dealing with
assignments only and not allocations too.<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks for this useful clarification.</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
3.0 Proposal<br>
<br>
CPM 9.0 to be modified as follows:<br>
<br>
9.0 Temporary Resource Assignments<br>
<br>
9.1 Documenting the temporary activity<br>
<br>
The activity requiring temporary IP resources should be
publicly documented and available on a website reachable
at least during the entire period of the event. 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. 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.<br>
<br>
9.2 Assignments of IP resources<br>
Resources are assigned on a lease basis for a period of
one month. The assignment can be renewed on application to
AFRINIC providing the necessary information. The size of
the assigned IP resource will be determined from the plan
submitted by the requesting entity. In the particular case
of IPv4, the size cannot exceed a /22.<br>
<br>
9.2.1 Required Documentation:<br>
The requesting organisation should contact AFRINIC with
the following information:<br>
a. Details of Organisation: Legal Organisation name,
Country Where Registered, Postal Address, Physical
Address, Telephone and Fax Numbers, website (this is a
must).<br>
b. Details of activity requiring the temporary
assignment: Website detailing the activity or Website with
a link to similar previous activities, Links from other
(relevant) sites about this activity, and the date when
the above activity ends.<br>
c. The planned use of these IP resources: List subnet
size required, and for what it will be used plus any AS
numbers and reverse delegation, if required.<br>
d. The intended date of return of the IP resources above.<br>
<br>
9.3 Technical recommendations<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">...since i'm not for adding these kind of
operational recommendations in IP policies, i propose a
different approach.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Concretely, i suggest to remove all lines below
and replace it by this *drafting text* or something more
*neutral* in the sens of operationality :</div>
<div dir="auto"><br>
</div>
<div dir="auto">[<i>After that the AFRINIC Staff has taken the
decision to temporary allocate some ressources to an entity,
the AFRINIC Staff *must* also provide that entity with
appropriate technicals recommendations in line with related
existing BCOPs and RFCs Standards ; for conformance.</i>]</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
a. The requesting entity is encouraged to deploy
IPv6-only networks and push IPv4 at the edge according to
an IPv6 transition mechanism (such as NAT64+DNS64 or
464XLAT)<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Question : <i>is it applicable for all types of
usages ? </i></div>
<div dir="auto"><br>
</div>
<div dir="auto">Again, can we really|logically recommend it to a
given entity which needs some temporary resources to realize a
*particular* experiment ?</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
b. The requesting entity could base its architecture from
some RFCs such as:<br>
c. [rfc3750] (INFORMATIONAL) Unmanaged Networks for IPv6
Transition Scenarios<br>
d. [rfc4213] (Standards Track) Basic Transition
Mechanisms for IPv6 Hosts and Routers<br>
e. [rfc6180] (INFORMATIONAL) Guidelines for Using IPv6
Transition Mechanisms during IPv6 Deployment<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">My personal thought and huge will is that the
AFRINIC Community has its BCOPs repository where a BCOP for
“Operational|Practical Uses of Temporary Resources Assigned”
might contain some of the above recommendations. </div>
<div dir="auto"><br>
</div>
<div dir="auto">...so, to achieve the goal of more IPv6[-only]
deployment in AFRINIC region, we should not bring operational,
even legitimate, orientations on IP Policies, but let's try to
do other things including to produce more Best Current
Operational Practice (BCOPs) with our NOG communities... </div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">[...]</blockquote>
</div>
</div>
<div dir="auto"><br>
I think that this policy draft should use the approach of the
section 6.6 [4] of the CPM (v1.3) for more coherence. It is
about assignments for internet experiments only when it belong
to IPv6. Then the duration of the lease is twelve months. If
you want a technical event organiser to use more IPv6 during
theirs meetings, you can precise that the minimum of the
temporary term is different for IPv4 and for IPv6 resources.
So they will be able to organize more than one event before
coming back to AFRINIC for a new lease. <br>
<br>
Even the sectioon 6.6 [4] of the CPM (v1.3) needs some
improvements, but we should begin by correcting what we can
here and trying to prevent any overlap with the said sectioon
6.6 [4] ;-) <br>
<br>
...three things to considere :<br>
* Limitation of the number of times an entity can request for
extension of the same lease ?<br>
* Differenciation on the conditions of the lease for IPv4 and
IPv6 ?<br>
* Differenciation on the type of resources to temporary
assign ?<br>
__<br>
[1]:
<a class="moz-txt-link-freetext" href="https://www.afrinic.net/library/policies/697-ipv4-soft-landing-policy">https://www.afrinic.net/library/policies/697-ipv4-soft-landing-policy</a><br>
[2]: <a class="moz-txt-link-freetext" href="https://afrinic.net/policy/manual">https://afrinic.net/policy/manual</a><br>
[3]: <a class="moz-txt-link-freetext" href="https://afrinic.net/policy/manual#Scope-PDP">https://afrinic.net/policy/manual#Scope-PDP</a><br>
[4]:
<a class="moz-txt-link-freetext" href="https://afrinic.net/policy/manual#Assignments-Internet-Experiments">https://afrinic.net/policy/manual#Assignments-Internet-Experiments</a><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards,</div>
<div dir="auto">--sb.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<pre class="moz-signature" cols="72">--
Regards,
Sylvain B.
<a class="moz-txt-link-rfc2396E" href="http://www.chretiennement.org"><http://www.chretiennement.org></a>
__
Website : <a class="moz-txt-link-rfc2396E" href="https://www.cmnog.cm"><https://www.cmnog.cm></a>
Wiki : <a class="moz-txt-link-rfc2396E" href="https://www.cmnog.cm/dokuwiki"><https://www.cmnog.cm/dokuwiki></a>
Surveys : <a class="moz-txt-link-rfc2396E" href="https://survey.cmnog.cm"><https://survey.cmnog.cm></a>
Subscribe to Mailing List : <a class="moz-txt-link-rfc2396E" href="https://lists.cmnog.cm/mailman/listinfo/cmnog/"><https://lists.cmnog.cm/mailman/listinfo/cmnog/></a>
Mailing List's Archives : <a class="moz-txt-link-rfc2396E" href="https://lists.cmnog.cm/pipermail/cmnog/"><https://lists.cmnog.cm/pipermail/cmnog/></a>
Last Event's Feed : <a class="moz-txt-link-rfc2396E" href="https://twitter.com/hashtag/cmNOGlab3"><https://twitter.com/hashtag/cmNOGlab3></a>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/cmN0G"><https://twitter.com/cmN0G></a>
<a class="moz-txt-link-rfc2396E" href="https://facebook.com/cmNOG"><https://facebook.com/cmNOG></a>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/hashtag/REBOOTcmNOG"><https://twitter.com/hashtag/REBOOTcmNOG></a>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/hashtag/cmNOG"><https://twitter.com/hashtag/cmNOG></a>
<a class="moz-txt-link-rfc2396E" href="https://cmnog.wordpress.com/"><https://cmnog.wordpress.com/></a></pre>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>