[prev in list] [next in list] [prev in thread] [next in thread]
List: afrinic-rpd
Subject: Re: [rpd] Perspective of Variance & Policy for Timely Impact Analysis Reports (was: impact analysis
From: JORDI PALET MARTINEZ via RPD <rpd () afrinic ! net>
Date: 2019-06-30 12:06:15
Message-ID: 94176014-F515-4C33-9A3E-7DFA7D61AF98 () consulintel ! es
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
El 29/6/19 15:21, "Sylvain BAYA" <abscoco@gmail.com> escribió:
{i'm starting a new thread. Source : \
<https://lists.afrinic.net/pipermail/rpd/2019/009601.html>}
Hi all,
...Please see below (inline).
Le 6/25/2019 à 9:09 AM, JORDI PALET MARTINEZ a écrit :
See below, in-line.
Regards,
Jordi
@jordipalet
El 25/6/19 1:21, "Sylvain BAYA" <abscoco@gmail.com> escribió:
[...]
...not sure if we can do it so simple as you want it ; but...we should try ;-)
· I think we may use this one, which is a very simple change, and I hope \
everybody in the community will be happy to accept as a "trial". I'm not suggesting \
at this time to use it for other policy proposals. If it works, in the future we can \
consider a PDP change to allow policies to go thru the mailing list without the need \
to wait for the meeting (as we do in IETF and RIPE). It is up to the chairs at this \
time to accept it and the community to decide on this small change then.
Jordi, thanks for your very kick response :-)
...as it was, i still believe it can not *correctly* fix our problem (i may be \
wrong), and of course it's not just about the *simplicity* ; it's first about having \
a workable solution which could address most of the known issues. I have observed \
that it appears to try to get thing done by simply officialising the *agreement* the \
Chairs concluded with the Staff.
I mean, changing a lot of text in any part of the PDP is complex, takes time. But \
using the variance process to change just something that I believe everybody agree \
"we need the staff to complete the impact analysis on time", should be a simple \
thing.
But what do i think that was missing :
- I think, as it was, it does not guarantee us to have a timely Impact Analysis \
Report (IAR) for all versions (particulary intermediary ones) of any policy proposal \
{not really a big issue for me ; because it would be acceptable to have at least an \
IAR, even only, for the first version and for the last version of a proposal \
published before the PPM (Public Policy Meeting) and at least a week before the \
deadline (TBD | To Be Defined to better fit) of the publication of all IARs}.
- It also miss to provide the possibility, for the Chairs, to request for an IAR (as \
the CPM section 3.4.1 actually allows it), for an intermediary new version of a given \
policy proposal ; where the community agrees there is a need for an IAR.
- That text was giving to the Staff the rights to provide only one IAR, even if an \
author publish more than three (very impacting) versions of a proposal in five month \
between two PPM. {this could be a good point depending on which side you stand : \
Staff or Community.}
I'm proposing you the following and I'm doing it openly in the list, so others can \
provide inputs as well.
I agree, let's discuss openly to collect any available input :-)
According "3.6 Varying the Process", for that we need a *co-chair* to accept it. Any \
taker?
This is the variance that I'm proposing:
1) Publish officially the policy proposal and start a 4-weeks for community \
discussion.
2) If after that, the chairs believe there is consensus, last-call for 4-weeks.
3) If there is no-consensus, allow to repeat the process, maximum up to one \
month before the next meeting (then there is no need for the variance of the \
process).
4. This Variance decision shall take effect one month after its publication on the \
PDP list.
-> not sure what do you mean here. Once the chairs accept it, the policy proposal can \
be submitted and published in a few days. There will be 4-weeks (I think is \
sufficient for this case but I'm happy for more) for discussing. So why 4 more weeks \
are needed? We want to keep it simple, if we start discussing about the variance \
itself, we may never have go thru it …
5. That first month after the publication of the Variance decision shall serve to \
prepare the commuty before the effective start point of the cycle of variance.
-> Now I see it, but I don't think is needed. We are already talking about it, \
community should be reading (those not reading now will not read later … according \
to my experience, and anyway, they have several weeks to discuss), and it may take \
several days for the chairs to decide, then to prepare a policy proposal document, \
then to publish it, and finally for a formal announcement of the process. The chairs \
may decide to just use 6 weeks or 8 instead of 4. Whatever they decide I'm ok with \
that.
Thanks, for your explanation, i understand now why it's not necessary to delay the \
starting point of the variance period.
*Question* : where to store this Variance decision and its future successors ?
...to what i understand, when published it becomes part of the PDP and supersides all \
existent concurrent texts which might conflict with it.
-> there is no difference between how a policy proposal is handled, same process \
versus a normal one (web page, presentation in the next meeting if reached consensus, \
minutes, etc.).
> -/ not sure if you are speaking about the *variance decision* taken by the Chairs \
> or about the policy proposal (IAR Timely Disponibility) under the *variance of the \
> process*. I'm ok with the PDP for the latter, but my question was about the first.
*A Proposed Answer*
With the CPM section 3.6, can we conclude that it's not possible to alter the CPM to \
insert|store the variance decision ? (perhaps we should also prepare a policy \
proposal to amend the CPM section 3.6 :-/)
I have an idea, i'm not sure it could work fine. But let's give it a try please :-)
...so when the Chairs annonce a new variance of the CPM, we can tag the title of all \
the section affected by the new variance decision by something like [SUPERSIDED by \
Variance in Place ; see Section 3.6.1] :
+ We leave the actual texts of any affected sections as it is :
+ Just add a special tag with a small text to the title ?
Like this : [SUPERSIDED by the Varying in Place ; see section 3.6.1]
+ Title the section 3.6.1 by : Active Variance Process Decisions
+ Paste the variance decision at the section 3.6.1. (new sub-section)
+ Remove the content of the section when the Variance Decision expires.
I don't think this is needed and this makes it very complex, as it means we must \
change the PDP before processing this variance …
...i also hope it is not needed, Jordi. But please also considere that the Staff has \
less than six months (CPM section 3.4.5) to implement a new policy, then they would \
be able to insert the new change (to the CPM, if needed) once the ratification from \
the BoD (CPM section 3.4.4).
As we have the opportunity to use the *variance* for the first time, i wanted to \
share my concerns and i added a possible solution. But i'm ok to use it (as you \
proposed it) first ; then come back at the end of the *variance period* for a \
thorough appraisal.
Exactly if we discover any flaw when we use the variance, we should correct, it, but \
meanwhile, I think is just ok.
***
ACTUAL text (at 3.4.1):
The Working Group Chair(s) may request AFRINIC to provide an analysis (technical, \
financial, legal or other), of the impact of the draft policy proposal.
DRAFT proposed text (replace the previous text):
AFRINIC will publish an impact analysis (technical, financial, legal or other) at \
least 10 days before the next Public Policy Meeting. If justified, in case of \
extremely complex new policy proposals, AFRINIC will publish at least a draft version \
of the impact analysis.
***
As discussed before, the problem to solve is too complex. To handle most of the \
complexity, i propose this text instead :
*** DRAFT proposed text (replace the previous text):
* The AFRINIC Staff publish (website and RPD mailinglist) an impact analysis report \
during the first week after a new policy proposal is published.
* When a new version of a policy proposal is published, on request of the Chair(s) or \
the Author(s), the Staff publish a new impact analysis report, during the first week \
after the publication of that policy proposal version.
* No impact analysis report should be published ten (10) days before the next Public \
Policy Meeting.
* If justified, in case of extremely complex new policy proposals, AFRINIC Staff \
publish at least a draft version of the impact analysis report.
* An impact analysis report shall be of one or both following types : technical, \
financial, legal or other.
*** END
-> I think you're making it extremely complex without a real need for that. Keep it \
simple and "short". Some impact analysis need much more time than a week. Just let's \
make sure we have it ahead of the meeting. 10 days allows the authors, if they are \
quick, to publish immediately a new version (within the 1-week deadline before the \
meeting), in case minor issues discovered by the impact analysis (I've done that in a \
couple of cases!). The impact analysis already includes all that, no need to mention \
it.
...again, i have no problem with simplicity (yes it still a difficult exercise for me \
to write short texts which would take into account complex considerations. I admit to \
need some help here) ; however i don't see (IMHO) simplicity and shortness as the \
similar things. Your explanation is awaiting.
A small change, a simple one, is easier to agree with the community than longer ones.
When I started writing policy proposals, I was making long texts. For example, I \
recall one in APNIC. The staff suggested me to break it in 5 policy proposals. Much \
easier to agree on individual, short and consequently "simple" changes. Of course, \
not always is possible, but in this case, I think it is.
-> This will only work if we make it extremely simple and acceptable for all the \
community. I'm happy to change the 10-days before the meeting to 2-weeks, for \
example. See a new version below.
...now i ask you to explain me how your actual text can deal with all these points i \
listed on top of this mail. As soon as you confirm me that it taking into account \
these basic requirements it will be seen as a sustainable draft policy proposal which \
can correct the problem we actually faced with the IARs.
· DRAFT proposed text (replace the previous text):
AFRINIC will publish an impact analysis (including technical, financial, legal and \
other aspects) as soon as possible for each policy proposal submitted (as a maximum 2 \
weeks before the next Public Policy Meeting). When duly justified, in case of \
extremely complex new policy proposals, AFRINIC will publish meanwhile a draft \
version of the impact analysis.
...i can live with this version, better than the previous. But, please, can you check \
it once more against the basics requirements i listed on the near top of this mail ? \
;-)
I'm lost now … Take it this way. What is the problem? Ensuring that we have the \
impact analysis on time, within reasonable limits for the staff to work on it. We can \
do it in a very complex way, with a policy proposal to change all the PDP, or just \
trying to have a quick fix. We can use the normal PDP, or we can request the chairs \
for using the variance. The variance is "more feasible" if we have a simple change \
(which provides the same results to our problem).
Thanks & Shalom,
--sb.
This small change in our PDP will prove ourselves that AFRINIC community is able to \
pro-actively discuss and pass policy proposals in the list.
What do you think?
I agree that we are doing a good job (thank GOD), together, and hopefully some other \
will follow this challenging approach.
Regards,
Jordi
@jordipalet
[...]
--
Regards,
Sylvain B.
<http://www.chretiennement.org>
__
Website : <https://www.cmnog.cm>
Wiki : <https://www.cmnog.cm/dokuwiki>
Surveys : <https://survey.cmnog.cm>
Subscribe to Mailing List : <https://lists.cmnog.cm/mailman/listinfo/cmnog/>
Mailing List's Archives : <https://lists.cmnog.cm/pipermail/cmnog/>
Last Event's Feed : <https://twitter.com/hashtag/cmNOGlab3>
<https://twitter.com/cmN0G>
<https://facebook.com/cmNOG>
<https://twitter.com/hashtag/REBOOTcmNOG>
<https://twitter.com/hashtag/cmNOG>
<https://cmnog.wordpress.com/>
_______________________________________________ RPD mailing list RPD@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.
[Attachment #5 (text/html)]
<html xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type \
content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 \
(filtered medium)"><style><!-- /* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML con formato previo Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.moz-txt-link-rfc2396e
{mso-style-name:moz-txt-link-rfc2396e;}
span.tlid-translation
{mso-style-name:tlid-translation;}
span.HTMLconformatoprevioCar
{mso-style-name:"HTML con formato previo Car";
mso-style-priority:99;
mso-style-link:"HTML con formato previo";
font-family:Consolas;}
span.EstiloCorreo24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:968240851;
mso-list-template-ids:11587606;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1461650323;
mso-list-template-ids:-1261895718;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:ï‚·;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p \
class=MsoNormal><span lang=ES-TRAD \
style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p \
class=MsoNormal style='margin-left:35.4pt'>El 29/6/19 15:21, "Sylvain BAYA" \
<<a href="mailto:abscoco@gmail.com">abscoco@gmail.com</a>> \
escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal \
style='margin-left:35.4pt'><o:p> </o:p></p></div><p \
style='margin-left:35.4pt'>{i'm starting a new thread. Source : <span \
class=moz-txt-link-rfc2396e><a \
href="https://lists.afrinic.net/pipermail/rpd/2019/009601.html"><https://lists.afrinic.net/pipermail/rpd/2019/009601.html></a></span>} \
<o:p></o:p></p><p style='margin-left:35.4pt'>Hi all,<o:p></o:p></p><p \
style='mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>...Please \
see below (inline).<o:p></o:p></p><div><p class=MsoNormal \
style='margin-left:35.4pt'>Le 6/25/2019 Ã 9:09 AM, JORDI PALET MARTINEZ a \
écrit :<o:p></o:p></p></div><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;color:black'>See below, \
in-line.</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;color:black'> </span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;color:black'>Regards,</span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>Jordi</span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet</span><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'> \
</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'> </span><o:p></o:p></p><div><div><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'>El \
25/6/19 1:21, "Sylvain BAYA" <<a \
href="mailto:abscoco@gmail.com">abscoco@gmail.com</a>> \
escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'> <o:p></o:p></p></div><p \
style='margin-left:70.8pt'>[...]<o:p></o:p></p><p style='margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>...not sure if we can \
do it so simple as you want it ; but...we should try ;-) </span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:71.4pt;text-indent:-18.0pt;mso-list:l0 \
level1 lfo1'><![if !supportLists]><span \
style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'> ·<span \
style='font:7.0pt "Times New Roman"'> \
</span></span></span><![endif]><span lang=EN-US>I think we may use this one, which is \
a very simple change, and I hope everybody in the community will be happy to accept \
as a "trial". I'm not suggesting at this time to use it for other policy proposals. \
If it works, in the future we can consider a PDP change to allow policies to go thru \
the mailing list without the need to wait for the meeting (as we do in IETF and \
RIPE). It is up to the chairs at this time to accept it and the community to decide \
on this small change then.</span><o:p></o:p></p></div></blockquote><p \
style='margin-left:35.4pt'><br>Jordi, thanks for your very kick response \
:-)<o:p></o:p></p><p style='margin-left:35.4pt'>...as it was, i still believe it can \
not *correctly* fix our problem (i may be wrong), and of course it's not just about \
the *simplicity* ; it's first about having a workable solution which could address \
most of the known issues. I have observed that it appears to try to get thing done by \
simply officialising the *agreement* the Chairs concluded with the Staff. \
<o:p></o:p></p><p><span lang=EN-US style='font-size:12.0pt'>I mean, changing a lot of \
text in any part of the PDP is complex, takes time. But using the variance process to \
change just something that I believe everybody agree "we need the staff to complete \
the impact analysis on time", should be a simple thing.<o:p></o:p></span></p><p \
style='margin-left:35.4pt'><span lang=EN-US>But what do i think that was missing \
:<o:p></o:p></span></p><p style='margin-left:35.4pt'>- I think, as it was, it does \
not guarantee us to have a timely Impact Analysis Report (IAR) for all versions \
(particulary intermediary ones) of any policy proposal {not really a big issue for me \
; because it would be acceptable to have at least an IAR, even only, for the first \
version and for the last version of a proposal published before the PPM (Public \
Policy Meeting) and at least a week before the deadline (TBD | To Be Defined to \
better fit) of the publication of all IARs}.<o:p></o:p></p><p \
style='margin-left:35.4pt'>- It also miss to provide the possibility, for the Chairs, \
to request for an IAR (as the CPM section 3.4.1 actually allows it), for an \
intermediary new version of a given policy proposal ; where the community agrees \
there is a need for an IAR. <o:p></o:p></p><p \
style='mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>- \
That text was giving to the Staff the rights to provide only one IAR, even if an \
author publish more than three (very impacting) versions of a proposal in five month \
between two PPM. {this could be a good point depending on which side you stand : \
Staff or Community.}<o:p></o:p></p><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><div><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>I'm proposing you the \
following and I'm doing it openly in the list, so others can provide inputs as \
well.</span><o:p></o:p></p></blockquote><p style='margin-left:70.8pt'><span \
lang=EN-US> </span><o:p></o:p></p><p style='margin-left:70.8pt'>I agree, let's \
discuss openly to collect any available input :-)<o:p></o:p></p><p \
style='margin-left:70.8pt'> <o:p></o:p></p><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>According "3.6 Varying \
the Process", for that we need a *<b>co-chair</b>* to accept it. Any \
taker?</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'> </span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>This is the variance \
that I'm proposing:</span><o:p></o:p></p><p class=MsoListParagraph \
style='margin-left:106.8pt;text-indent:-18.0pt'>1)<span \
style='font-size:7.0pt;font-family:"Times New \
Roman",serif'> </span><span lang=EN-US \
style='font-size:12.0pt;mso-fareast-language:EN-US'>Publish officially the policy \
proposal and start a 4-weeks for community discussion.</span><o:p></o:p></p><p \
class=MsoListParagraph style='margin-left:106.8pt;text-indent:-18.0pt'>2)<span \
style='font-size:7.0pt;font-family:"Times New \
Roman",serif'> </span><span lang=EN-US \
style='font-size:12.0pt;mso-fareast-language:EN-US'>If after that, the chairs believe \
there is consensus, last-call for 4-weeks.</span><o:p></o:p></p><p \
class=MsoListParagraph style='margin-left:106.8pt;text-indent:-18.0pt'>3)<span \
style='font-size:7.0pt;font-family:"Times New \
Roman",serif'> </span><span lang=EN-US \
style='font-size:12.0pt;mso-fareast-language:EN-US'>If there is no-consensus, allow \
to repeat the process, maximum up to one month before the next meeting (then there is \
no need for the variance of the process).</span><o:p></o:p></p></blockquote><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'> <o:p></o:p></p><p \
style='margin-left:70.8pt'>4. This Variance decision shall take effect one month \
after its publication on the PDP list.<o:p></o:p></p><p \
style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>-> not sure \
what do you mean here. Once the chairs accept it, the policy proposal can be \
submitted and published in a few days. There will be 4-weeks (I think is sufficient \
for this case but I'm happy for more) for discussing. So why 4 more weeks are needed? \
We want to keep it simple, if we start discussing about the variance itself, we may \
never have go thru it …</span><o:p></o:p></p><p style='margin-left:70.8pt'><span \
lang=EN-US>5. That first month after the publication of the Variance decision shall \
serve to prepare the commuty before the effective start point of the cycle of \
variance.</span><o:p></o:p></p><p style='margin-left:35.4pt'><span lang=EN-US \
style='font-size:12.0pt'>-> Now I see it, but I don't think is needed. We are \
already talking about it, community should be reading (those not reading now will not \
read later … according to my experience, and anyway, they have several weeks to \
discuss), and it may take several days for the chairs to decide, then to prepare a \
policy proposal document, then to publish it, and finally for a formal announcement \
of the process. The chairs may decide to just use 6 weeks or 8 instead of 4. Whatever \
they decide I'm ok with that.</span><o:p></o:p></p></div></blockquote><p \
class=MsoNormal style='margin-left:35.4pt'><br>Thanks, for your explanation, i \
understand now why it's not necessary to delay the starting point of the variance \
period.<br><br><br><o:p></o:p></p><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p \
style='margin-left:70.8pt'>*Question* : where to store this Variance decision and its \
future successors ?<o:p></o:p></p><p style='margin-left:70.8pt'>...to what i \
understand, when published it becomes part of the PDP and supersides all existent \
concurrent texts which might conflict with it. <o:p></o:p></p><p \
style='margin-left:35.4pt'><span lang=EN-US style='font-size:12.0pt'>-> there is \
no difference between how a policy proposal is handled, same process versus a normal \
one (web page, presentation in the next meeting if reached consensus, minutes, \
etc.).</span><o:p></o:p></p></div></blockquote><p class=MsoNormal \
style='margin-left:35.4pt'><br>:-/ not sure if you are speaking about the *variance \
decision* taken by the Chairs or about the policy proposal (IAR Timely Disponibility) \
under the *variance of the process*. I'm ok with the PDP for the latter, but my \
question was about the first.<br><br><br><o:p></o:p></p><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p style='margin-left:70.8pt'>*A \
Proposed Answer*<o:p></o:p></p><p style='margin-left:70.8pt'>With the CPM section \
3.6, can we conclude that it's not possible to alter the CPM to insert|store the \
variance decision ? (perhaps we should also prepare a policy proposal to amend the \
CPM section 3.6 :-/)<o:p></o:p></p><p style='margin-left:70.8pt'>I have an idea, i'm \
not sure it could work fine. But let's give it a try please :-)<o:p></o:p></p><p \
style='margin-left:70.8pt'>...so when the Chairs annonce a new variance of the CPM, \
we can tag the title of all the section affected by the new variance decision by \
something like [SUPERSIDED by Variance in Place ; see Section 3.6.1] \
:<o:p></o:p></p><p style='margin-left:70.8pt'>+ We leave the actual texts of any \
affected sections as it is :<o:p></o:p></p><p style='margin-left:70.8pt'>+ Just add a \
special tag with a small text to the title ?<o:p></o:p></p><p \
style='margin-left:70.8pt'>Like this : [SUPERSIDED by the Varying in Place ; see \
section 3.6.1]<o:p></o:p></p><p style='margin-left:70.8pt'>+ Title the section 3.6.1 \
by : Active Variance Process Decisions<o:p></o:p></p><p style='margin-left:70.8pt'>+ \
Paste the variance decision at the section 3.6.1. (new sub-section)<o:p></o:p></p><p \
style='margin-left:70.8pt'>+ Remove the content of the section when the Variance \
Decision expires.<o:p></o:p></p><p style='margin-left:35.4pt'><span lang=EN-US>I \
don't think this is needed and this makes it very complex, as it means we must change \
the PDP before processing this variance \
…</span><o:p></o:p></p></div></blockquote><p style='margin-left:35.4pt'><br>...i \
also hope it is not needed, Jordi. But please also considere that the Staff has less \
than six months (CPM section 3.4.5) to implement a new policy, then they would be \
able to insert the new change (to the CPM, if needed) once the ratification from the \
BoD (CPM section 3.4.4). <o:p></o:p></p><p \
style='mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>As \
we have the opportunity to use the *variance* for the first time, i wanted to share \
my concerns and i added a possible solution. But i'm ok to use it (as you proposed \
it) first ; then come back at the end of the *variance period* for a thorough \
appraisal.<o:p></o:p></p><p style='margin-bottom:12.0pt'><span lang=EN-US \
style='font-size:12.0pt'>Exactly if we discover any flaw when we use the variance, we \
should correct, it, but meanwhile, I think is just \
ok.<o:p></o:p></span></p><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><div><blockquote \
style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>***</span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>ACTUAL text (at \
3.4.1):</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:10.0pt'>The Working Group Chair(s) may request AFRINIC to \
provide an analysis (technical, financial, legal or other), of the impact of the \
draft policy proposal.</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'> </span><o:p></o:p></p><p \
class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>DRAFT proposed text \
(replace the previous text):</span><o:p></o:p></p><p class=MsoNormal \
style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:70.8pt'><span \
lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>AFRINIC will publish \
an impact analysis (technical, financial, legal or other) at least 10 days before the \
next Public Policy Meeting. If justified, in case of extremely complex new policy \
proposals, AFRINIC will publish at least a draft version of the impact \
analysis.</span><o:p></o:p></p><p class=MsoNormal \
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
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.<br> <br>
</body></html>
_______________________________________________
RPD mailing list
RPD@afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic