<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 2, 2017, at 11:59 AM, Noah <<a href="mailto:noah@neo.co.tz" class="">noah@neo.co.tz</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">Owen,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">IMHO<br class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class="">As far as i am concerned, the internet routing table still indicates that IPv4 (basically NAT) is still the superior source address until networks (esp CGN folk) upgrade.</div></div></div></div></blockquote><div><br class=""></div>I’m not sure what is meant by “superior source address”.</div><div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class="">No content provider the likes of Facebook, Google etc will pull a Y2K and risk the traffic they generate into their business today by shutting IPv4 which mostly comes from Telecoms/CGN.</div></div></div></div></div></blockquote><div><br class=""></div>Facebook is nearly 100% IPv6 today. Very little of their infrastructure even has an IPv4 address and they’d very much like to shut that little IPv4 that remains off as quickly as possible. They are maintaining it not because it is a superior source address, but because due to laggards in the eyeball network land, they are forced to maintain backward compatibility to support some (ever diminishing) subset of their users.</div><div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class="">Fact is the availability of the v4 transfer market makes it even worse and the very reason I am in support of tightening soft-landing restrictions in our region unlike those who call for softening and depleting IPv4 at this stage and even go head to further advocate for more inbound tranfers instead of promoting IPv6 adoption.</div></div></div></div></div></blockquote><div><br class=""></div>I think you are mischaracterizing my position rather substantially here, or, perhaps you are speaking of others whose positions I can’t speak to. It’s hard to tell, but since you are responding to me, I will assume for the moment that it is my position you are mischaracterizing and rebut your statement accordingly…</div><div><br class=""></div><div>The availability of the IPv4 transfer market is a fact. I don’t think it necessarily makes anything worse or better, it simply is. Whether it is acknowledged by the RIRs and whois data is maintained accurately, or, whether the address are transferred in effect if not in registration, addresses will be transferred where there is need and/or potential profit in doing so. While there is a free pool in the region, the motivation to do an unregistered transfer remains low and the risks remain relatively high. Once the free pool is depleted, this equation changes substantially. Note that restrictions on allocations/assignments create an artificial form of depletion prior to actual depletion increasing the motivation for transfers (whether or not they can be documented through the RIR in question).</div><div><br class=""></div><div>I am not calling for softening and depleting IPv4 at this stage, but I don’t see any advantage to tightening it, either.</div><div><br class=""></div><div>I do advocate that I think it would be wise for AfriNIC to implement a transfer policy, but I do oppose a unilateral inbound-only inter-RIR transfer policy. Not because I favor the transfer of resources out of the AfriNIC region, but because I believe that number resource policy should be fair and impartial and an inbound-only policy is neither. If AfriNIC as a community does not want to engage in transferring space to other RIRs, then AfriNIC should not be seeking to engage in transferring space from other RIRs, either.</div><div><br class=""></div><div>If the community is concerned about protecting their remaining free pool, then the solution is to put a trigger into the inter-RIR transfer policy which states it is not active until the AfriNIC free pool is depleted.</div><div><br class=""></div><div><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class="">Then you have cloud business proponents who cant resist the urge of IPv$ so they can cash in without any proof of physical infrastucture in this continent. </div></div></div></div></div></blockquote><div><br class=""></div>Not sure if IPv$ was an accidental typo or a deliberate way of expressing the sale of IPv4 addresses. If AfriNIC staff is issuing addresses to networks without physical infrastructure in the continent or without adequate proof of same, then I believe that is a problem either in terms of inadequate policy as expressed in the number resource policies created by the AfriNIC community or a problem of improper action by the AfriNIC staff. Neither of those issues is solved or improved in any way by creating an artificial shortage of IPv4 resources in the free pool now to members that need them in favor of some mythical future need of members that don’t yet exist.</div><div><br class=""></div><div>In fact, I would argue that by insisting on holding resources in the free pool for “possible future newcomers” you are, in effect, assigning them to organizations without any current proof of physical infrastructure in the AfriNIC service region to the disadvantage of organizations that do currently have proof of infrastructure and a documented need for the addresses within the region today.</div><div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class="">PS: Am not an co-author of any new proposal on softlanding, you must have mistaken me for Douglas.</div></div></div></div></div></blockquote><div><br class=""></div>Fair enough. My apologies.</div><div><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Noah</div></div></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 2 Apr 2017 7:55 p.m., "Owen DeLong" <<a href="mailto:owen@delong.com" target="_blank" class="">owen@delong.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 31, 2017, at 12:18 PM, Noah <<a href="mailto:noah@neo.co.tz" target="_blank" class="">noah@neo.co.tz</a>> wrote:</div><br class="m_-5955770504876170628Apple-interchange-newline"><div class=""><div dir="auto" class="">McTim,<div dir="auto" class=""><br class=""></div><div dir="auto" class="">The fact is that most of what we seek is still out there seated on some iron that still runs IPv4. </div></div></div></blockquote><div class=""><br class=""></div>This doesn’t parse well. Could you try clarifying your exact meaning here?</div><div class=""><br class=""></div><div class="">If you mean “Most of what we see is still running on hardware that is incapable of IPv6 support”, then I find that hard to believe. I can believe that some of what we see fits that statement, but not most.</div><div class=""><br class=""></div><div class="">If you mean that many providers still don’t support IPv6, then yes, that’s reality, but that’s a very problematic reality and I think we, as a community need to look long and hard at ways to alter that reality soon lest it become an additional form of isolation between the rest of the world and this community.</div><div class=""><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class="">The remaining space can still help those without or new late entrants into the game as they will need source addresses for the routes what they will be developing as Internet expansion sponteneously expand across the continent.</div></div></blockquote><div class=""><br class=""></div>IPv4 has become like an addiction at this point. We all know that failing to deploy IPv6 is bad for us in a big way, yet we are so tied to IPv4 for a variety of reasons that we are loathe to consider the fact that at some point there simply isn’t enough address space in IPv4 and there really will be IPv4 have-nots. In fact, there really already are many IPv4 have-nots. Look at the number of people in India behind double NATs for years and the other places where CGN is now beginning to be deployed. Look at the number of universities in Africa that are using NAT rather than getting real address space to meet their needs even though real address space is still readily available to them.</div><div class=""><br class=""></div><div class="">I’m at a point where I have to question whether blocking access to IPv4 addresses to users that need it now in favor of some possible need for late-entrants or newcomers later is truly a service to those late-entrants or newcomers vs. a disservice to the entire community.</div><div class=""><br class=""></div><div class="">IPv4 is already painful. The reality is that the longer we allow it to persist as the lingua franca of the internet, the longer and more severe the pain will become. Yes, an abrupt transition today is non-feasible, but do we really need to work to further artificially extend the transition beyond even the level of delay which is already inherent in the process?</div><div class=""><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class="">Eventually, competition and scramble for more subscribers will motivate Afro-Centric Telecoms to come out of their cave and rapidly deploy IPv6 on their iron.</div></div></blockquote><div class=""><br class=""></div>Will it? I think that extending the life of IPv4 address space will only delay this process without providing any real benefit to the community.</div><div class=""><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class="">Until then, I still see a lot of relevance in restricting the Softlanding space and we have a SL-BIS policy before us that we can further improve.</div></div></blockquote><div class=""><br class=""></div>I agree with McTim. I do not feel there is a compelling reason to amend the existing soft landing policy at this time. I don’t feel that the -bis</div><div class="">proposal benefits the community and I see a number of drawbacks to it. I’m not enthusiastic about the other proposal either.</div><div class=""><br class=""></div><div class="">The latest proposal from you and Seun is a substantial improvement, but I still do not believe that it provides benefit that exceeds the unintended consequences, so I remain opposed to it as well.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><blockquote type="cite" class=""><div dir="auto" class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Noah</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Noah</div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On 31 Mar 2017 2:42 p.m., "McTim" <<a href="mailto:dogwallah@gmail.com" target="_blank" class="">dogwallah@gmail.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Barack,<br class="">
<br class="">
While rough consensus may be easier to achieve, I do not think even<br class="">
that is possible in this situation.<br class="">
<br class="">
The Big Picture is that we spent may years crafting and editing the<br class="">
finer points of the current SL policy.<br class="">
<br class="">
Now, there seems to be 2 groups who whose views are in direct<br class="">
opposition to each other about how to change this policy.<br class="">
<br class="">
Reviewing both "problem statements", I don't find any problems that<br class="">
absolutely need fixing from my perspective.<br class="">
<br class="">
Andrew's a, b, c, d from above were all well known and assumed when we<br class="">
wrote the policy. The same is true of the bis- "problem statement", I<br class="">
can't really find any "problems" that are compelling (enough for me)<br class="">
to open up the SL to amendments.<br class="">
<br class="">
One common area of agreement from both parties is "get v6 deployed",<br class="">
maybe we should be focusing on that?<br class="">
<br class="">
I do think that we will be UNable to find even rough consensus on -bis<br class="">
and that seemed to be the case with overhaul before it was withdrawn.<br class="">
<br class="">
In short, I do not support -bis, nor would I support an overhaul<br class="">
unless Arsene and Mark can give us a problem statement that identifies<br class="">
a real problem that can be readily addressed (pun intended) via policy<br class="">
change.<br class="">
<br class="">
Best Regards,<br class="">
<br class="">
McTim<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
Andrew<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On Fri, Mar 31, 2017 at 4:01 AM, Barrack Otieno<br class="">
<<a href="mailto:otieno.barrack@gmail.com" target="_blank" class="">otieno.barrack@gmail.com</a>> wrote:<br class="">
> Dear all,<br class="">
><br class="">
> Many thanks Andrew, if consensus is complicated we could try rough<br class="">
> consensus, i think every proponent is right in one way or the other, we just<br class="">
> need a middle ground that is acceptable to all of us. I agree with the<br class="">
> co-chairs that we can have consensus if we choose to do so. Can the other<br class="">
> proposal be sent in the same spirit? The status quo is good but we should<br class="">
> not give up on engaging each other. Let us accept or refuse the proposals<br class="">
> based on the merits and shortcomings. Happy to contribute in this effort<br class="">
> alongside Arsene.<br class="">
><br class="">
> Regards<br class="">
><br class="">
> On Mar 31, 2017 9:56 AM, "Andrew Alston" <<a href="mailto:Andrew.Alston@liquidtelecom.com" target="_blank" class="">Andrew.Alston@liquidtelecom.c<wbr class="">om</a>><br class="">
> wrote:<br class="">
>><br class="">
>> Let me state our problem statement from the authors of the withdrawn<br class="">
>> proposal.<br class="">
>><br class="">
>> The problem is that restricting the amount of space that can be allocated<br class="">
>> in this late stage has the following effects:<br class="">
>><br class="">
>> a.) It disadvantages the areas that have already got networks and are<br class="">
>> ready to connect consumers but can't do so because they can't get adequate<br class="">
>> space<br class="">
>> b.) It disadvantages the consumer who is in an area with network coverage<br class="">
>> but ends up stuck behind NAT and other mechanisms which hurt him because<br class="">
>> space allocation is being artificially constrained<br class="">
>> c.) It increases the digital divide by creating a false sense that v4 is<br class="">
>> still current and will continue to last - while the rest of the world moves<br class="">
>> to V6<br class="">
>> d.) It assists only people who have not yet invested in and build their<br class="">
>> own networks - at the expense of people who have already done the work<br class="">
>><br class="">
>> Furthermore:<br class="">
>><br class="">
>> a.) Any tie back to v6 "plans" has proven to be totally and utterly<br class="">
>> ineffective in actually getting people to do v6 - all it results in is<br class="">
>> people putting an allocation on one router for announcement purpose and<br class="">
>> saying look, we are doing v6, while the consumer never sees a v6 address<br class="">
>> b.) Tying up resources for critical infrastructure at this point makes<br class="">
>> zero sense - critical infrastructure is by and large already catered for in<br class="">
>> other policies - with the exception of TLD's, and how much space are you<br class="">
>> reserving for them? A TLD should not require more than a /24, and there are<br class="">
>> only 54 countries on the continent - that amounts to no more than a /17<br class="">
>> worth of space - why are we trying to tie up /12s?<br class="">
>> c.) Restrictions on allocations without being willing to implement an<br class="">
>> inbound transfer policy that allows people to get space they need when they<br class="">
>> cannot get it via AfriNIC is nothing short of insanity, it puts the larger<br class="">
>> operators who need space at risk of being able to get NONE, while giving<br class="">
>> zero benefit to anyone - and the alternative to this is that it forces those<br class="">
>> entities to go and join another RIR, at additional expense to the operator<br class="">
>> and at the expense of revenue to AfriNIC<br class="">
>><br class="">
>> The withdrawn policy effectively called for the repeal of the soft landing<br class="">
>> policy - the bis policy effectively calls for a tightening of the policy -<br class="">
>> these are diametrically opposed viewpoints and diametrically opposed<br class="">
>> philosophies. This is the reason why I do not believe that there will be<br class="">
>> consensus on this and why I believe we are wasting our time - because there<br class="">
>> is a large segment of the community that will simply not accept the<br class="">
>> tightening of restrictions in soft landing, and there is an equal segment of<br class="">
>> the community that will not accept the repeal of the soft landing or a<br class="">
>> loosening of the restrictions. Which segment of the community has the right<br class="">
>> philosophy and the right approach, well, time will tell on this, but its<br class="">
>> immaterial to the discussion - the fact is - we're deadlocked on this and<br class="">
>> that’s ok, lets accept it, accept the status quo and move on. Anything else<br class="">
>> is a waste of time and distracting from other far more important issues in<br class="">
>> my view... like the lack of inbound transfer policy for when we truly do<br class="">
>> need space and don't have any.<br class="">
>><br class="">
>> Restricting the allocation sizes in the soft landing is not the answer -<br class="">
>> and certainly not if you do not give the members the ability to get what<br class="">
>> space they need from alternate sources.<br class="">
>><br class="">
>> So - we can continue down this path, and I'm ok with that - however, I<br class="">
>> believe we're wasting our time because I do not believe we will see any<br class="">
>> consensus on this - not on the floor, not in last call, and not before all<br class="">
>> the space is gone. But the PDP Is clear, anyone has the right to have<br class="">
>> policy put before the floor and to be heard, and that must be respected,<br class="">
>> however much we oppose what is being said, and however much we believe that<br class="">
>> no consensus will be found. It is, under the PDP process, the decision of<br class="">
>> the authors to decide if they want to continue wasting the time of this<br class="">
>> community or not, and the decision is theirs and should be respected - but<br class="">
>> in turn, the opposition to what is being said must also be heard and<br class="">
>> respected - it goes both ways.<br class="">
>><br class="">
>> I remain opposed to anything that tightens restrictions<br class="">
>><br class="">
>> Andrew<br class="">
>><br class="">
>> -----Original Message-----<br class="">
>> From: McTim [mailto:<a href="mailto:dogwallah@gmail.com" target="_blank" class="">dogwallah@gmail.com</a>]<br class="">
>> Sent: 31 March 2017 05:37<br class="">
>> To: SamiSalih <<a href="mailto:sami@ntc.gov.sd" target="_blank" class="">sami@ntc.gov.sd</a>><br class="">
>> Cc: rpd <<a href="mailto:rpd@afrinic.net" target="_blank" class="">rpd@afrinic.net</a>><br class="">
>> Subject: Re: [rpd] Report of the Soft Landing isuue<br class="">
>><br class="">
>> Hi Sami,<br class="">
>><br class="">
>> To be honest, I can't even recall the problem statements of these 2<br class="">
>> proposals.<br class="">
>><br class="">
>> Perhaps we could have them posted to the list to see if there is any area<br class="">
>> of commonality at that level?<br class="">
>><br class="">
>> After all, if there is zero common ground between the 2 problems that<br class="">
>> these proposals aim to fix, and instead diametric opposition, then there is<br class="">
>> little point in carrying on a stalemate.<br class="">
>><br class="">
>> Regards,<br class="">
>><br class="">
>> McTim<br class="">
>><br class="">
>><br class="">
>><br class="">
>> On Wed, Mar 29, 2017 at 11:16 PM, SamiSalih <<a href="mailto:sami@ntc.gov.sd" target="_blank" class="">sami@ntc.gov.sd</a>> wrote:<br class="">
>> > Thanks McTim for the reminder<br class="">
>> > However, as co-chairs our mandate is to condider every single propsal<br class="">
>> > comming from the community and work to foster a condtructive discussion,<br class="">
>> > this necessitates all members to objectivly discuss the ideas and only good<br class="">
>> > ideas can be further developed to a policy.<br class="">
>> > I think ourandate is also to find a middle group to BUILD the<br class="">
>> > consensus so we have to be positive and innovative rather than just<br class="">
>> > rapporteurs- you know better than me in this regards<br class="">
>> ><br class="">
>> > Sicerely<br class="">
>> ><br class="">
>> > Dr. Sami Salih | Assistant Professor<br class="">
>> > Sudan University of Science and Technology Eastern Dum, P.O Box<br class="">
>> > 11111-407<br class="">
>> > email: <a href="mailto:sami.salih@sustech.edu" target="_blank" class="">sami.salih@sustech.edu</a><br class="">
>> > Mob: <a href="tel:%2B249122045707" value="+249122045707" target="_blank" class="">+249122045707</a><br class="">
>> ><br class="">
>> > ----- McTim <<a href="mailto:dogwallah@gmail.com" target="_blank" class="">dogwallah@gmail.com</a>> wrote:<br class="">
>> >> Sami, all,<br class="">
>> >><br class="">
>> >> I just want to remind everyone that "no consensus, status quo remains"<br class="">
>> >> is a perfectly valid outcome of the PDP.<br class="">
>> >><br class="">
>> >> Not every policy proposal needs to pass in some form or other. That<br class="">
>> >> a proposal fails to gain consensus is not an indictment of the PDP,<br class="">
>> >> rather a validation of the PDP.<br class="">
>> >><br class="">
>> >> Regards,<br class="">
>> >><br class="">
>> >> McTim<br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >> On Wed, Mar 29, 2017 at 1:02 PM, SamiSalih <<a href="mailto:sami@ntc.gov.sd" target="_blank" class="">sami@ntc.gov.sd</a>> wrote:<br class="">
>> >> > Dear Marcus,<br class="">
>> >> ><br class="">
>> >> > First of all YES we really sure what we are trying to organize !<br class="">
>> >> > Second, Mark Elkins is on of the co-authors of many other proposals<br class="">
>> >> > - as he claimed -, the one you particularly mention is not an<br class="">
>> >> > active proposal for the time being Third, as we stated we welcome<br class="">
>> >> > any volunteer to contribute to solve the issues we addressed in our<br class="">
>> >> > justifications to our call,<br class="">
>> >> ><br class="">
>> >> > Please help us to focus only on ideas and proposals.<br class="">
>> >> ><br class="">
>> >> > Best Regards,<br class="">
>> >> ><br class="">
>> >> > Dr. Sami Salih | Assistant Professor Sudan University of Science<br class="">
>> >> > and Technology Eastern Dum, P.O Box 11111-407<br class="">
>> >> > email: <a href="mailto:sami.salih@sustech.edu" target="_blank" class="">sami.salih@sustech.edu</a><br class="">
>> >> > Mob: <a href="tel:%2B249122045707" value="+249122045707" target="_blank" class="">+249122045707</a><br class="">
>> >> ><br class="">
>> >> > ______________________________<wbr class="">__<br class="">
>> >> ><br class="">
>> >> > From: "Marcus K. G. Adomey" <<a href="mailto:madomey@hotmail.com" target="_blank" class="">madomey@hotmail.com</a>><br class="">
>> >> > To: "SamiSalih" <<a href="mailto:sami@ntc.gov.sd" target="_blank" class="">sami@ntc.gov.sd</a>>, "rpd" <<a href="mailto:rpd@afrinic.net" target="_blank" class="">rpd@afrinic.net</a>><br class="">
>> >> > Sent: Wednesday, March 29, 2017 7:19:25 PM<br class="">
>> >> > Subject: Re: Report of the Soft Landing isuue<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > Dear Co-chairs,<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > While reading your email, I am wondering whether you are really<br class="">
>> >> > sure of what you are trying to organize. Have you considered the<br class="">
>> >> > following points?<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > 1 - Mark Elkins is one of the co-authors of the softlanding<br class="">
>> >> > overhaul<br class="">
>> >> ><br class="">
>> >> > 2- The co-authors of the softlanding-bis proposal which is still in<br class="">
>> >> > the PDWG track said ".... we are available for any further<br class="">
>> >> > actions required from us" in their response to your 7 days call.<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > Some thoughts for reflection!!!<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > Marcus<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > ______________________________<wbr class="">__<br class="">
>> >> > From: SamiSalih <<a href="mailto:sami@ntc.gov.sd" target="_blank" class="">sami@ntc.gov.sd</a>><br class="">
>> >> > Sent: Tuesday, March 28, 2017 7:03:11 AM<br class="">
>> >> > To: rpd<br class="">
>> >> > Subject: Re: [rpd] Report of the Soft Landing isuue<br class="">
>> >> ><br class="">
>> >> > Dear PDWG,<br class="">
>> >> ><br class="">
>> >> > We appreciate your active discussion regarding the soft landing<br class="">
>> >> > policy.<br class="">
>> >> ><br class="">
>> >> > This is to declare the end of the Seven Days comment period on<br class="">
>> >> > developing a common proposal according to the points commonly<br class="">
>> >> > agreed before whether in the RPD or at PPMs.<br class="">
>> >> ><br class="">
>> >> > So far we have Mark Elkins and Arsène Tungali as the only<br class="">
>> >> > volunteers. We hope they can edit the commonly agreed view in a new<br class="">
>> >> > policy update proposal document and work with other community<br class="">
>> >> > members including authors of previous proposals that wish to lend<br class="">
>> >> > their experience.<br class="">
>> >> ><br class="">
>> >> > Best Regards,<br class="">
>> >> ><br class="">
>> >> > PDWG Co-Chairs<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > ______________________________<wbr class="">__<br class="">
>> >> ><br class="">
>> >> > From: "Honest Ornella GANKPA" <<a href="mailto:honest1989@gmail.com" target="_blank" class="">honest1989@gmail.com</a>><br class="">
>> >> > To: "Dewole Ajao" <<a href="mailto:dewole@forum.org.ng" target="_blank" class="">dewole@forum.org.ng</a>><br class="">
>> >> > Cc: "rpd" <<a href="mailto:rpd@afrinic.net" target="_blank" class="">rpd@afrinic.net</a>><br class="">
>> >> > Sent: Monday, March 27, 2017 4:49:22 PM<br class="">
>> >> > Subject: Re: [rpd] Report of the Soft Landing isuue<br class="">
>> >> ><br class="">
>> >> > Hello Dewole<br class="">
>> >> ><br class="">
>> >> > It has been suggested to take the points which have consensus on<br class="">
>> >> > the wide variety and get an editor to come up with a new version<br class="">
>> >> > if we really do not want the current authors to do it.<br class="">
>> >> ><br class="">
>> >> > Best regards<br class="">
>> >> ><br class="">
>> >> > Honest Ornella GANKPA<br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > 2017-03-27 8:52 GMT+01:00 Dewole Ajao <<a href="mailto:dewole@forum.org.ng" target="_blank" class="">dewole@forum.org.ng</a>>:<br class="">
>> >> >><br class="">
>> >> >> The proposal "already in the PDP" (as you put it) deals with a<br class="">
>> >> >> wide variety of areas. That collection of areas has not found<br class="">
>> >> >> consensus. If the authors choose to whittle the proposal down to<br class="">
>> >> >> those areas that the community largely agrees on, the co-chairs<br class="">
>> >> >> would not need to point out areas that volunteers can adopt and put<br class="">
>> >> >> forward.<br class="">
>> >> >><br class="">
>> >> >> Although proposals (once submitted to the RPD list) are supposed<br class="">
>> >> >> to be owned by the community and not the authors, the current<br class="">
>> >> >> definition/implementation of the AFRINIC PDP does not promote that<br class="">
>> >> >> enough. I stand to be corrected but I think that is why we find<br class="">
>> >> >> ourselves in this logjam today.<br class="">
>> >> >><br class="">
>> >> >> The submission presented by co-chairs a week ago was to allow a<br class="">
>> >> >> chance to do things the collaborative way. A chance to disconnect<br class="">
>> >> >> from whatever sentiments exist and tackle policy issues (which is<br class="">
>> >> >> why we are here).<br class="">
>> >> >><br class="">
>> >> >> I fail to see what makes you think the co-chairs are focusing on<br class="">
>> >> >> authors rather than policy.<br class="">
>> >> >><br class="">
>> >> >> Dewole.<br class="">
>> >> >><br class="">
>> >> >> Sent from a mobile device. Please excuse typos and autocorrect<br class="">
>> >> >> strangeness.<br class="">
>> >> >><br class="">
>> >> >> On 26 Mar 2017, at 8:52 PM, Honest Ornella GANKPA<br class="">
>> >> >> <<a href="mailto:honest1989@gmail.com" target="_blank" class="">honest1989@gmail.com</a>><br class="">
>> >> >> wrote:<br class="">
>> >> >><br class="">
>> >> >> Hi Dewole,<br class="">
>> >> >><br class="">
>> >> >> 2017-03-26 18:37 GMT+01:00 Dewole Ajao <<a href="mailto:dewole@forum.org.ng" target="_blank" class="">dewole@forum.org.ng</a>>:<br class="">
>> >> >>><br class="">
>> >> >>> There is more to benefit from collaborating on a single draft<br class="">
>> >> >>> rather than spewing out multiple proposals.<br class="">
>> >> >><br class="">
>> >> >> Agreed! So why are you asking for new proposals when there is<br class="">
>> >> >> already one in PDP. Co-chairs need to focus on policy not authors.<br class="">
>> >> >><br class="">
>> >> >><br class="">
>> >> >> Honest Ornella GANKPA<br class="">
>> >> >><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > ______________________________<wbr class="">_________________<br class="">
>> >> > RPD mailing list<br class="">
>> >> > <a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class="">
>> >> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank" class="">https://lists.afrinic.net/mail<wbr class="">man/listinfo/rpd</a><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> ><br class="">
>> >> > ______________________________<wbr class="">_________________<br class="">
>> >> > RPD mailing list<br class="">
>> >> > <a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class="">
>> >> > <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank" class="">https://lists.afrinic.net/mail<wbr class="">man/listinfo/rpd</a><br class="">
>> >> ><br class="">
>> >><br class="">
>> >><br class="">
>> >><br class="">
>> >> --<br class="">
>> >> Cheers,<br class="">
>> >><br class="">
>> >> McTim<br class="">
>> >> "A name indicates what we seek. An address indicates where it is. A<br class="">
>> >> route indicates how we get there." Jon Postel<br class="">
>> ><br class="">
>><br class="">
>><br class="">
>><br class="">
>> --<br class="">
>> Cheers,<br class="">
>><br class="">
>> McTim<br class="">
>> "A name indicates what we seek. An address indicates where it is. A route<br class="">
>> indicates how we get there." Jon Postel<br class="">
>><br class="">
>> ______________________________<wbr class="">_________________<br class="">
>> RPD mailing list<br class="">
>> <a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class="">
>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank" class="">https://lists.afrinic.net/mail<wbr class="">man/listinfo/rpd</a><br class="">
>> ______________________________<wbr class="">_________________<br class="">
>> RPD mailing list<br class="">
>> <a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class="">
>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank" class="">https://lists.afrinic.net/mail<wbr class="">man/listinfo/rpd</a><br class="">
<br class="">
<br class="">
<br class="">
--<br class="">
Cheers,<br class="">
<br class="">
McTim<br class="">
"A name indicates what we seek. An address indicates where it is. A<br class="">
route indicates how we get there." Jon Postel<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
RPD mailing list<br class="">
<a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class="">
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank" class="">https://lists.afrinic.net/mail<wbr class="">man/listinfo/rpd</a><br class="">
</blockquote></div></div>
______________________________<wbr class="">_________________<br class="">RPD mailing list<br class=""><a href="mailto:RPD@afrinic.net" target="_blank" class="">RPD@afrinic.net</a><br class=""><a href="https://lists.afrinic.net/mailman/listinfo/rpd" target="_blank" class="">https://lists.afrinic.net/<wbr class="">mailman/listinfo/rpd</a><br class=""></blockquote></div><br class=""></div></blockquote></div></div>
</blockquote></div><br class=""></body></html>