<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Marco,</div><div><br></div><div>remember we've worked together, I think I know exactly what you meant, no need to appologise :-)</div>
<div>I think it's a great idea to have Comms proofread the document. There may be some typoes or missing words.. just like below, an 'is' is also missing.</div><div><br></div><div>Please do ask Comms to give us an estimate on the proofreading and if it doesn't take too much time.. I say let's just go for it and not waste time :-) If we are going to use any or _all_ of their recommendations, we'll see.�</div>
<div>Do take into consideration that my last edit of this document was being done at 4AM after a 10 hours flight ;) so, I am sure they will find typoes, missing words, better wording :)</div><div><br></div><div>Regarding the rationale, I've done my best and even if I've been hearing a lot of pro's and conn's here in China, I would like not to list them all just for the sake of the discussions on the mailing list.</div>
<div><br></div><div>I am sure we will have a revision after the RIPE Meeting anyway.</div><div><br></div><div>cheers,</div><div>elvis</div><div><br>Excuse the briefness of this mail, it was sent from a mobile device.</div>
<div><br>On 29 aug. 2013, at 22:15, Marco Schmidt <<a href="mailto:mschmidt@ripe.net">mschmidt@ripe.net</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Elvis,<br>
<br>
On 8/29/13 3:50 PM, Elvis Daniel Velea wrote:<br>
</div>
<blockquote cite="mid:-3590829091858545786@unknownmsgid" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div style>Hi Marco, just noticed a typo:</div>
<div style><br>
</div>
<div><span style>'</span><span style="background-color:rgba(255,255,255,0)">Where this
extension not possible, the organisations has', please fix
this with 'the organisation has'</span></div>
</blockquote>
Will do :)<br>
<br>
<blockquote cite="mid:-3590829091858545786@unknownmsgid" type="cite">
<div><span style><br>
</span></div>
<div><span style>regarding COMMS' offer to help, I'd really
appreciate if they could have a look at the document and tell
us what they would change regarding better English.</span></div>
</blockquote>
Just to make sure: I hope you didn't get me wrong on the term
"better English" as your text looks very good and nothing must be
really written "better". Still it doesn't harm to have a neutral
editor looking at the text.<br>
<br>
If Olaf and Daniel agree then I will pass the the current policy
text to Comms.<br>
<br>
I was referring more to the rationale were the things still seems
developing (I just saw Daniel's email). If there is more to come
then please let me know.<br>
<br>
<blockquote cite="mid:-3590829091858545786@unknownmsgid" type="cite">
<div><span style><br>
</span></div>
<div><span style>However, this is a long document so if they
expect it to take longer than a week , let's just push it now,
as it is, and we'll probably be revising it before it gets
approved... we may use their help with the revision :-)</span></div>
<div><span style><br>
</span></div>
</blockquote>
Okay, after I get the okay from you I will pass the text to Comms
asking for an estimation how much time they would need. Again, this
proofreading is just something optional.<br>
<br>
<br>
Kind Regards,<br>
Marco<br>
<br>
<blockquote cite="mid:-3590829091858545786@unknownmsgid" type="cite">
<div><span style>I think we need at least a few weeks of
discussion before the RIPE Meeting.</span></div>
<div><span style><br>
</span></div>
<div><span style>cheers,</span></div>
<div><span style>elvis<br>
</span><br>
<span style>Excuse the briefness of this mail, it was sent
from a mobile device.</span></div>
<div style><br>
On 29 aug. 2013, at 20:53, Marco Schmidt <<a href="mailto:mschmidt@ripe.net">mschmidt@ripe.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite" style>
<div>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hello,<br>
<div class="moz-forward-container">
<div class="moz-cite-prefix"> <br>
I just read through the whole mailing list archive to get
a picture of this proposal and firstly please let me say
I'm impressed about all the (team)work that you did to get
this proposal running :)<br>
<br>
I used the word-document that Elvis send me earlier with
the latest version of the policy text and on the first
page I added details that I found in the mailing list
archive (details to the authors, rationale).<br>
<br>
Please let me know if everything is as you wish.<br>
<br>
If I overlooked something or misunderstood something then
please don't get mad on me - as you might know I'm quite
new on this job :)<br>
<br>
<br>
Some comments:<br>
<br>
1)<br>
I adjusted the organisation details for the authors but
did not include the the job position yet as I'm not aware
that this was included in previous proposals.<br>
<br>
2)<br>
Do you plan some future work on the arguments supporting/
<meta http-equiv="CONTENT-TYPE" content="text/html;
charset=ISO-8859-1">
opposing
<title></title>
<meta name="GENERATOR" content="OpenOffice 4.0.0 (Unix)">
the proposal? As this policy proposal is big it might be
good to anticipate as much arguments as possible.<br>
<br>
<br>
3)<br>
Do you wish any support from our Comms department
regarding better English or editing the summary, the
rationale and/or the policy text? This is just something
optional, I think especially the policy text looks very
good.<br>
<br>
<br>
<br>
Best regards,<br>
Marco Schmidt<br>
PDO office<br>
<br>
<br>
On 8/28/13 10:07 AM, Sonderegger Olaf ABRAXAS INFORMATIK
AG wrote:<br>
</div>
<blockquote cite="mid:7C49C19C69319E4FB1279CA15A84D18B61DC0DB6@SAX20244.bia.abraxas.ch" type="cite">
<pre>Hi everyone,
My signature should be: Sonderegger Olaf, Abraxas Informatik AG, ICT Architect, <a class="moz-txt-link-abbreviated" href="mailto:olaf.sonderegger@abraxas.ch">olaf.sonderegger@abraxas.ch</a>
About arguments:
Should we prepare a list of pro and cons, so that we could add some arguments/ideas/solutions per list item?
As Gert mentioned, it's better to provide some ideas/solutions for cons.
Kind regards, Olaf
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:apwg-ipv6-papi-bounces@ripe.net">apwg-ipv6-papi-bounces@ripe.net</a> [<a class="moz-txt-link-freetext" href="mailto:apwg-ipv6-papi-bounces@ripe.net">mailto:apwg-ipv6-papi-bounces@ripe.net</a>] On Behalf Of Elvis Velea
Sent: Dienstag, 27. August 2013 20:03
To: <a class="moz-txt-link-abbreviated" href="mailto:apwg-ipv6-papi@ripe.net">apwg-ipv6-papi@ripe.net</a>; <a class="moz-txt-link-abbreviated" href="mailto:pdo@ripe.net">pdo@ripe.net</a>
Subject: Re: [Apwg-ipv6-papi] policy proposal done?
Hi everyone,
I'm very happy everyone responded today ;) that's a first :P
To answer everyone in a row:
1. @Sander - I also explained the idea to Andrew and he was interested in listening to all the pro's and con's. I think it will have quite some impact on the RIPE NCC so I wanted the board to have a look at it as well.
2. @Gert - I am sure it will have some good response, we will see over time.
3. @Andrea & Marco - please let me know if it's clear what I did in that document. I can provide access to the shared google document if you can not copy the data from the attachments I've provided in my previous email.
Marco, when you have a second, do let us know when you think the proposal could be advanced to the mailing list.
Please note that the three proposers are:
me - Elvis Daniel Velea, V4Escrow LLC, Chief Business Analyst, <a class="moz-txt-link-abbreviated" href="mailto:elvis@v4escrow.net">elvis@v4escrow.net</a>
Daniel Stolpe, Resilans AB, position?, <a class="moz-txt-link-abbreviated" href="mailto:stolpe@resilans.se">stolpe@resilans.se</a>
Sonderegger Olaf, ABRAXAS INFORMATIK AG, position?, <a class="moz-txt-link-abbreviated" href="mailto:Olaf.Sonderegger@abraxas.ch">Olaf.Sonderegger@abraxas.ch</a>
4. @Daniel - Ingrid is still part of the Registration Services as far as I know, and as far as I understand, she, Andrea and Marco will take over the PDO function that Emilio had. So we will have 3 people helping us instead of just one. That must be good news, right? :-)
Regarding the presentations during the RIPE Meeting, what I want us to do is:
- present the current 'problems' of the IPv6 policy during the Plenary
- possibly present the idea to the IPv6-WG, but keep the discussion in the AP-WG
- discuss the proposal during the AP-WG
- possibly present at the GM an idea on how this may influence the whole community and the impact it may have to the charging scheme and the RIPE NCC
@Everyone: we still need to figure out what we will be writing on the Rationale, arguments pro and con.
cheers,
elvis
(happy on the feedback received today)
_______________________________________________
Apwg-ipv6-papi mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Apwg-ipv6-papi@ripe.net">Apwg-ipv6-papi@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://www.ripe.net/mailman/listinfo/apwg-ipv6-papi">https://www.ripe.net/mailman/listinfo/apwg-ipv6-papi</a>
</pre>
</blockquote>
<br>
<br>
</div>
<br>
</div>
</blockquote>
<blockquote type="cite" style>
<div><IPv6policyproposal.doc></div>
</blockquote>
<blockquote type="cite" style>
<div><span>_______________________________________________</span><br>
<span>Apwg-ipv6-papi mailing list</span><br>
<span><a href="mailto:Apwg-ipv6-papi@ripe.net">Apwg-ipv6-papi@ripe.net</a></span><br>
<span><a href="https://www.ripe.net/mailman/listinfo/apwg-ipv6-papi">https://www.ripe.net/mailman/listinfo/apwg-ipv6-papi</a></span><br>
</div>
</blockquote>
</blockquote>
<br>
</div></blockquote></body></html>