<html>
<head>
<meta content="text/html; charset=windows-1251"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Sergiu,<br>
</p>
<br>
<div class="moz-cite-prefix">Il 30/04/2016 19:15, Sergiu IANCIUC ha
scritto:<br>
</div>
<blockquote cite="mid:1005021206.20160430201521@itns.md" type="cite">
<title>Re[2]: [address-policy-wg] Fwd: [ncc-announce] [news] RIPE
Policy Proposals - April Update</title>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1251">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
body {
margin: 5px 5px 5px 5px;
background-color: #ffffff;
}
/* ========== Text Styles ========== */
hr { color: #000000}
span.rvts1 /* Heading */
{
font-size: 10pt;
font-family: 'Arial';
font-weight: bold;
color: #0000ff;
}
span.rvts2 /* Subheading */
{
font-size: 10pt;
font-family: 'Arial';
font-weight: bold;
color: #000080;
}
span.rvts3 /* Keywords */
{
font-size: 10pt;
font-family: 'Arial';
font-style: italic;
color: #800000;
}
a.rvts4, span.rvts4 /* Jump 1 */
{
font-size: 10pt;
font-family: 'Arial';
color: #008000;
text-decoration: underline;
}
a.rvts5, span.rvts5 /* Jump 2 */
{
font-size: 10pt;
font-family: 'Arial';
color: #008000;
text-decoration: underline;
}
a.rvts6, span.rvts6
{
color: #0000ff;
text-decoration: underline;
}
span.rvts7
{
}
a.rvts8, span.rvts8
{
font-style: italic;
color: #0000ff;
text-decoration: underline;
}
span.rvts9
{
font-style: italic;
}
span.rvts10
{
font-style: italic;
}
span.rvts11
{
font-style: italic;
font-weight: bold;
}
span.rvts12
{
font-style: italic;
font-weight: bold;
background-color: #ff0000;
}
span.rvts13
{
font-style: italic;
background-color: #ff0000;
}
/* ========== Para Styles ========== */
p,ul,ol /* Paragraph Style */
{
text-align: left;
text-indent: 0px;
padding: 0px 0px 0px 0px;
margin: 0px 0px 0px 0px;
}
.rvps1 /* Centered */
{
text-align: center;
}
--></style>
<p>salut Riccardo,</p>
<p><br>
</p>
<p>1. I propose that here -</p>
<p><br>
</p>
<p><span class="rvts9">Proposals Open for Discussion:</span></p>
<p><span class="rvts9">2015-05, "Revision of Last /8 Allocation
Criteria"</span></p>
<p><span class="rvts10"><br>
</span></p>
<p><span class="rvts9">Proposal Overviews:</span></p>
<p><span class="rvts10"><br>
</span></p>
<p><span class="rvts9">PROPOSAL: 2015-05, "Revision of Last /8
Allocation Criteria"</span></p>
<p><span class="rvts9">OVERVIEW: Aims to allow LIRs to request an
additional /22 IPv4�</span></p>
<p><span class="rvts9">allocation from the RIPE NCC every 18
months. The latest version of the�</span></p>
<p><span class="rvts9">proposal suggests several requirements,
such as the LIR cannot hold more�</span></p>
<p><span class="rvts9">than a /20 IPv4, must document their IPv6
deployment�</span><span class="rvts12">and has not�</span></p>
<p><span class="rvts12">transferred any IPv4 address space before.</span></p>
<p><span class="rvts9">STATUS: Discussion Phase</span></p>
<p><span class="rvts9">WHERE TO COMMENT: Address Policy Working
Group:�</span><a moz-do-not-send="true" class="rvts8"
href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a></p>
<p><span class="rvts9">DEADLINE: 13 May 2016</span></p>
<p><span class="rvts9">FULL PROPOSAL:�</span><a
moz-do-not-send="true" class="rvts8"
href="https://www.ripe.net/participate/policies/proposals/2015-05"><a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2015-05">https://www.ripe.net/participate/policies/proposals/2015-05</a></a></p>
<p><br>
</p>
<p>to be introduced a definition that includes in the "<span
class="rvts12">�has not�</span></p>
<p><span class="rvts12">transferred any IPv4 address space before</span>"
list the LIR that transferred a prefix to an other LIR if this
prefix was allocated to the receiving LIR when it was not the
RIPE NCC member/LIR.</p>
</blockquote>
If I understand well your point this is already a requirement in
2015-05. Please have a look to the full proposal at� <span
class="rvts9"></span><a moz-do-not-send="true" class="rvts8"
href="https://www.ripe.net/participate/policies/proposals/2015-05">https://www.ripe.net/participate/policies/proposals/2015-05</a><br>
point <span style="color: rgb(51, 51, 51); font-family: 'Open
Sans', Helvetica, Arial, sans-serif; font-size: 14.3px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: 22.88px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important; float:
none; background-color: rgb(255, 255, 255);">[...] "3.1. The LIR
has not transferred any IPv4 address space to another LIR, a
member of another RIR, or an End User." [...]<br>
</span>
<blockquote cite="mid:1005021206.20160430201521@itns.md" type="cite">
<p><br>
</p>
<p>2. explain pls what does it signify</p>
<p><br>
</p>
<p><span class="rvts9">The latest version of the proposal suggests
several requirements, such as the LIR cannot hold more than a
/20 IPv4</span></p>
<p><br>
</p>
<p>cannot hold more then /20 unused ?</p>
</blockquote>
Doesn't matter if the /20 is used or not. With current text of the
2015-05 if an LIR already holds up to a /20 could not request any
additional allocation from available pool outside 185/8.<br>
If he didn't request a last /22 from 185/8 he can request it at any
time.<br>
Feel free to give the list your opinion about supporting 2015-05 or
not.<br>
<br>
thank you for your interest<br>
kind regards<br>
Riccardo<br>
<blockquote cite="mid:1005021206.20160430201521@itns.md" type="cite">
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best Regards,</p>
<p><br>
</p>
<p>-</p>
<p>Sergiu IANCIUC</p>
<p>SC ITNS.NET SRL</p>
<p><br>
</p>
<p>MD-2068, Moldova</p>
<p>or. Chisinau, str. Miron Costin 3/1</p>
<p>tel.: +373 22 877 877</p>
<p>fax : +373 22 44 11 73</p>
<p>mobile: +373 690 22 111</p>
<p>url:�<a moz-do-not-send="true" class="rvts6"
href="http://www.itns.md">http://www.itns.md</a></p>
<p><br>
</p>
<p>Save a tree... Don't print this email unless you have to...</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Saturday, April 30, 2016, 6:41:04 PM, you wrote:</p>
<p><br>
</p>
<div>
<table style="background-color: #ffffff;" border="0"
cellpadding="1" cellspacing="2">
<tbody>
<tr valign="top">
<td style="background-color: #0000ff;" width="2"><br>
</td>
<td width="1183">
<p><span class="rvts7">Hi Sergiu,</span></p>
<p><br>
</p>
<p><span class="rvts7">thank you for your reply. I don't
get if you disagree with current policy or proposed
one.</span></p>
<p><span class="rvts7">Anyway:</span></p>
<p><span class="rvts7">The LIR that assisgned or
allocated �the first /22 to your current new LIR can
transfert the space once 24 months are passed.</span></p>
<p><span class="rvts7">This is the holding time before a
transfert can take place standing on current
policies.</span></p>
<p><span class="rvts7">2015-05 policy proposal won't
change this aspect.�</span></p>
<p><br>
</p>
<p><span class="rvts7">kind regards�</span></p>
<p><span class="rvts7">Riccardo</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Il 30/04/2016 11:29, Sergiu
IANCIUC ha scritto:</span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p><span class="rvts7">salut Riccardo,</span></p>
<p><br>
</p>
<p><span class="rvts7">I do not totally agree with you.. and I
explain why.</span></p>
<p><br>
</p>
<p><span class="rvts7">you are talking about the case in the
future.. but I give an actual example..</span></p>
<p><br>
</p>
<p><span class="rvts7">2 years ago my company has an allocated
prefix from a LIR. After 1 year we asked additional resources
and had a negative response because of the RIPE Policy
limitations. after the next year the situation was the same
and to receive an additional prefix we became LIR. Now, pls
answer... why to not permit transfer from the old LIR to the
new one if they agree on it and do it for ensure the new LIR
in continuity of the prefix use (all this with condition that
this prefix was allocated by the old LIR when the new LIR has
the status OTHER).</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Best Regards,</span></p>
<p><br>
</p>
<p><span class="rvts7">-</span></p>
<p><span class="rvts7">Sergiu IANCIUC</span></p>
<p><span class="rvts7">SC ITNS.NET SRL</span></p>
<p><br>
</p>
<p><span class="rvts7">MD-2068, Moldova</span></p>
<p><span class="rvts7">or. Chisinau, str. Miron Costin 3/1</span></p>
<p><span class="rvts7">tel.: +373 22 877 877</span></p>
<p><span class="rvts7">fax : +373 22 44 11 73</span></p>
<p><span class="rvts7">mobile: +373 690 22 111</span></p>
<p><span class="rvts7">url:�</span><a moz-do-not-send="true"
class="rvts6" href="http://www.itns.md">http://www.itns.md</a></p>
<p><br>
</p>
<p><span class="rvts7">Save a tree... Don't print this email
unless you have to...</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Saturday, April 30, 2016, 8:33:49 AM, you
wrote:</span></p>
<p><br>
</p>
<div>
<table style="background-color: #ffffff;" border="0"
cellpadding="1" cellspacing="2">
<tbody>
<tr valign="top">
<td style="background-color: #0000ff;" width="2"><br>
</td>
<td width="1062">
<p><span class="rvts7">Dear Sergiu,</span></p>
<p><span class="rvts7">about your example and its
eventual realtionship with the proposal 2015-05:</span></p>
<p><span class="rvts7">Company X would have not limit in
receive address space as described in transfert or
allocation policies.</span></p>
<p><span class="rvts7">The limit described in 2015-05
would be applied to the LIR that assigned space to
Company X and, as described in your example, later
transfered the space in Company X registry.</span></p>
<p><span class="rvts7">This LIR is supposed to not need
address space as it moved it outside its registry so
it would not be able to request an additional /22
allocation from pool outside 185/8 standing on
2015-05 proposal</span></p>
<p><br>
</p>
<p><span class="rvts7">On the other hand if Company X
after its sing up as a new LIR after 18 months need
more space and there is enough space outside 185/8
�would be able to request an additional /22 standing
on �2015-05 proposal. The LIR that offered the first
/22 to Company X as �"assigned resource" could also
request an additional /22 allocation if its registry
is holding less than a /20 IPv4.</span></p>
<p><br>
</p>
<p><span class="rvts7">hope this help</span></p>
<p><span class="rvts7">regards</span></p>
<p><span class="rvts7">Riccardo</span></p>
<p><br>
</p>
<p><span class="rvts7">Il 29/04/2016 10:38, Sergiu
IANCIUC ha scritto:</span></p>
<p><span class="rvts7">hello,</span></p>
<p><br>
</p>
<p><span class="rvts7">PLS, take in consideration the
situation</span></p>
<p><br>
</p>
<p><span class="rvts7">Company �X �has �a �/22 from its
LIR. The LIR can not offer more IPv4�</span></p>
<p><span class="rvts7">spaces � and the Company X
becomes a LIR to satisfy its needs. Now, it�</span></p>
<p><span class="rvts7">is logical that the LIR (if
agreed between these 2 LIRs) transfers the�</span></p>
<p><span class="rvts7">space �allocated �to the Company
X (now the new LIR) AND THIS have to�</span></p>
<p><span class="rvts7">not be the part from the policy -</span></p>
<p><br>
</p>
<p><span class="rvts7">"requirements, �such �as �the LIR
has not transferred any IPv4 address�</span></p>
<p><span class="rvts7">space before."</span></p>
<p><br>
</p>
<p><span class="rvts7">What are you thinking about?</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Best Regards,</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">-</span></p>
<p><span class="rvts7">Sergiu IANCIUC</span></p>
<p><span class="rvts7">SC ITNS.NET SRL</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">MD-2068, Moldova</span></p>
<p><span class="rvts7">or. Chisinau, str. Miron Costin
3/1</span></p>
<p><span class="rvts7">tel.: +373 22 877 877</span></p>
<p><span class="rvts7">fax : +373 22 44 11 73</span></p>
<p><span class="rvts7">mobile: +373 690 22 111</span></p>
<p><span class="rvts7">url:�</span><a
moz-do-not-send="true" class="rvts6"
href="http://www.itns.md"><a class="moz-txt-link-freetext" href="http://www.itns.md">http://www.itns.md</a></a></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Save a tree... Don't print this
email unless you have to...</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">This is a forwarded message</span></p>
<p><span class="rvts7">From: Marco Schmidt�</span><a
moz-do-not-send="true" class="rvts6"
href="mailto:mschmidt@ripe.net"><a class="moz-txt-link-rfc2396E" href="mailto:mschmidt@ripe.net"><mschmidt@ripe.net></a></a></p>
<p><span class="rvts7">To:�</span><a
moz-do-not-send="true" class="rvts6"
href="mailto:ncc-announce@ripe.net"><a class="moz-txt-link-abbreviated" href="mailto:ncc-announce@ripe.net">ncc-announce@ripe.net</a></a></p>
<p><span class="rvts7">Date: Friday, April 29, 2016,
11:18:23 AM</span></p>
<p><span class="rvts7">Subject: [ncc-announce] [news]
RIPE Policy Proposals - April Update</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">===8<==============Original
message text===============</span></p>
<p><span class="rvts7">Dear colleagues,</span></p>
<p><br>
</p>
<p><span class="rvts7">Here is our monthly overview of
open policy proposals and their stage in�</span></p>
<p><span class="rvts7">the RIPE Policy Development
Process (PDP).</span></p>
<p><br>
</p>
<p><span class="rvts7">If you wish to join the
discussion about a particular proposal, please�</span></p>
<p><span class="rvts7">do so on the relevant working
group mailing list.</span></p>
<p><br>
</p>
<p><span class="rvts7">Proposals Open for Discussion:</span></p>
<p><span class="rvts7">2015-05, "Revision of Last /8
Allocation Criteria"</span></p>
<p><br>
</p>
<p><span class="rvts7">Proposals Awaiting Input:</span></p>
<p><span class="rvts7">2015-04, "RIPE Resource Transfer
Policies"</span></p>
<p><span class="rvts7">2016-01, "Include Legacy Internet
Resource Holders in the Abuse-c Policy"</span></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">Proposal Overviews:</span></p>
<p><br>
</p>
<p><span class="rvts7">PROPOSAL: 2015-05, "Revision of
Last /8 Allocation Criteria"</span></p>
<p><span class="rvts7">OVERVIEW: Aims to allow LIRs to
request an additional /22 IPv4�</span></p>
<p><span class="rvts7">allocation from the RIPE NCC
every 18 months. The latest version of the�</span></p>
<p><span class="rvts7">proposal suggests several
requirements, such as the LIR cannot hold more�</span></p>
<p><span class="rvts7">than a /20 IPv4, must document
their IPv6 deployment and has not�</span></p>
<p><span class="rvts7">transferred any IPv4 address
space before.</span></p>
<p><span class="rvts7">STATUS: Discussion Phase</span></p>
<p><span class="rvts7">WHERE TO COMMENT: Address Policy
Working Group:�</span><a moz-do-not-send="true"
class="rvts6"
href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a></p>
<p><span class="rvts7">DEADLINE: 13 May 2016</span></p>
<p><span class="rvts7">FULL PROPOSAL:�</span><a
moz-do-not-send="true" class="rvts6"
href="https://www.ripe.net/participate/policies/proposals/2015-05"><a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2015-05">https://www.ripe.net/participate/policies/proposals/2015-05</a></a></p>
<p><br>
</p>
<p><span class="rvts7">=====</span></p>
<p><br>
</p>
<p><span class="rvts7">The following proposals are
awaiting input before they can go any�</span></p>
<p><span class="rvts7">further in the PDP.</span></p>
<p><br>
</p>
<p><span class="rvts7">PROPOSAL: 2015-04, "RIPE Resource
Transfer Policies"</span></p>
<p><span class="rvts7">OVERVIEW: Aims to create a single
transfer policy with all relevant�</span></p>
<p><span class="rvts7">information on the transfer of
Internet number resources, replacing text�</span></p>
<p><span class="rvts7">in several RIPE Policies. The
proposal also introduces a 24-month�</span></p>
<p><span class="rvts7">holding period for IPv4 addresses
and 16-bit ASNs after any change of�</span></p>
<p><span class="rvts7">holdership.</span></p>
<p><span class="rvts7">RIPE NCC IMPACT ANALYSIS:
Includes the point how the 24-month holding�</span></p>
<p><span class="rvts7">period for scarce resources will
be applied.</span></p>
<p><span class="rvts7">STATUS: Review Phase � Awaiting
decision from working group chair</span></p>
<p><span class="rvts7">FULL PROPOSAL:�</span><a
moz-do-not-send="true" class="rvts6"
href="https://www.ripe.net/participate/policies/proposals/2015-04"><a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2015-04">https://www.ripe.net/participate/policies/proposals/2015-04</a></a></p>
<p><br>
</p>
<p><span class="rvts7">PROPOSAL: 2016-01, "Include
Legacy Internet Resource Holders in the�</span></p>
<p><span class="rvts7">Abuse-c Policy"</span></p>
<p><span class="rvts7">OVERVIEW: Aims for a mandatory
abuse contact for Legacy Internet�</span></p>
<p><span class="rvts7">Resource holders in the RIPE
Database.</span></p>
<p><span class="rvts7">STATUS: Discussion Phase �
Awaiting decision from proposer</span></p>
<p><span class="rvts7">FULL PROPOSAL:�</span><a
moz-do-not-send="true" class="rvts6"
href="https://www.ripe.net/participate/policies/proposals/2016-01"><a class="moz-txt-link-freetext" href="https://www.ripe.net/participate/policies/proposals/2016-01">https://www.ripe.net/participate/policies/proposals/2016-01</a></a></p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">The RIPE NCC provides an overview
of current RIPE Policy Proposals on�</span><a
moz-do-not-send="true" class="rvts6"
href="http://www.ripe.net"><a class="moz-txt-link-abbreviated" href="http://www.ripe.net">www.ripe.net</a></a><span
class="rvts7">:</span><a moz-do-not-send="true"
class="rvts6"
href="https://www.ripe.net/participate/policies/current-proposals/current-policy-proposals">https://www.ripe.net/participate/policies/current-proposals/current-policy-proposals</a></p>
<p><br>
</p>
<p><span class="rvts7">We look forward to your
involvement in the PDP.</span></p>
<p><br>
</p>
<p><span class="rvts7">Kind regards,</span></p>
<p><br>
</p>
<p><span class="rvts7">Marco Schmidt</span></p>
<p><span class="rvts7">RIPE Policy Development Officer</span></p>
<p><span class="rvts7">RIPE NCC</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">===8<===========End of
original message text===========</span></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">--�</span></p>
<p><br>
</p>
<p><span class="rvts7">Ing. Riccardo Gori</span></p>
<p><span class="rvts7">e-mail:�</span><a
moz-do-not-send="true" class="rvts6"
href="mailto:rgori@wirem.net"><a class="moz-txt-link-abbreviated" href="mailto:rgori@wirem.net">rgori@wirem.net</a></a></p>
<p><span class="rvts7">Mobile: �+39 339 8925947</span></p>
<p><span class="rvts7">Mobile: �+34 602 009 437</span></p>
<p><span class="rvts7">Profile:�</span><a
moz-do-not-send="true" class="rvts6"
href="https://it.linkedin.com/in/riccardo-gori-74201943"><a class="moz-txt-link-freetext" href="https://it.linkedin.com/in/riccardo-gori-74201943">https://it.linkedin.com/in/riccardo-gori-74201943</a></a><span
class="rvts7">�</span></p>
<p><span class="rvts7">�</span></p>
<p><span class="rvts7">WIREM Fiber Revolution</span></p>
<p><span class="rvts7">Net-IT s.r.l.</span></p>
<p><span class="rvts7">Via Cesare Montanari, 2</span></p>
<p><span class="rvts7">47521 Cesena (FC)</span></p>
<p><span class="rvts7">Tel +39 0547 1955485</span></p>
<p><span class="rvts7">Fax +39 0547 1950285</span></p>
<p><br>
</p>
<p><span class="rvts7">--------------------------------------------------------------------</span></p>
<p><span class="rvts7">�CONFIDENTIALITY NOTICE</span></p>
<p><span class="rvts7">This message and its attachments
are addressed solely to the persons�</span></p>
<p><span class="rvts7">above and may contain
confidential information. If you have received�</span></p>
<p><span class="rvts7">the message in error, be informed
that any use of the content hereof�</span></p>
<p><span class="rvts7">is prohibited. Please return it
immediately to the sender and delete�</span></p>
<p><span class="rvts7">the message. Should you have any
questions, please contact us by re-</span></p>
<p><span class="rvts7">plying to�</span><a
moz-do-not-send="true" class="rvts6"
href="mailto:info@wirem.net"><a class="moz-txt-link-abbreviated" href="mailto:info@wirem.net">info@wirem.net</a></a></p>
<p><span class="rvts7">� � � � Thank you</span></p>
<p><span class="rvts7">WIREM - Net-IT s.r.l.Via Cesare
Montanari, 2 - 47521 Cesena (FC)</span></p>
<p><span class="rvts7">--------------------------------------------------------------------</span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p><br>
</p>
<p><br>
</p>
<p><span class="rvts7">--�</span></p>
<p><br>
</p>
<p><span class="rvts7">Ing. Riccardo Gori
e-mail:�</span><a moz-do-not-send="true" class="rvts6"
href="mailto:rgori@wirem.net">rgori@wirem.net</a><span
class="rvts7">
Mobile: �+39 339 8925947
Mobile: �+34 602 009 437
Profile:�</span><a moz-do-not-send="true" class="rvts6"
href="https://it.linkedin.com/in/riccardo-gori-74201943">https://it.linkedin.com/in/riccardo-gori-74201943</a><span
class="rvts7">�</span></p>
<p><img moz-do-not-send="true" alt=""
src="cid:E0260814.01D1A303.3755C6E8.4E85068C_csseditor"
height="189" hspace="1" vspace="1" width="472"><span
class="rvts7">�</span></p>
<p><span class="rvts7">WIREM Fiber Revolution
Net-IT s.r.l.
Via Cesare Montanari, 2
47521 Cesena (FC)
Tel +39 0547 1955485
Fax +39 0547 1950285
--------------------------------------------------------------------
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the
persons above and may contain confidential information. If you
have received the message in error, be informed that any use
of the content hereof is prohibited. Please return it
immediately to the sender and delete the message. Should you
have any questions, please contact us by re-
plying to�</span><a moz-do-not-send="true" class="rvts6"
href="mailto:info@wirem.net">info@wirem.net</a><span
class="rvts7"> � � � �Thank you
WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena
(FC)
--------------------------------------------------------------------</span></p>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<pre>Ing. Riccardo Gori
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:rgori@wirem.net">rgori@wirem.net</a>
Mobile: +39 339 8925947
Mobile: +34 602 009 437
Profile: <a class="moz-txt-link-freetext" href="https://it.linkedin.com/in/riccardo-gori-74201943">https://it.linkedin.com/in/riccardo-gori-74201943</a>
</pre>
<img src="cid:part22.10EBF629.DDCC0657@wirem.net" width="200">
<pre>WIREM Fiber Revolution
Net-IT s.r.l.
Via Cesare Montanari, 2
47521 Cesena (FC)
Tel +39 0547 1955485
Fax +39 0547 1950285
--------------------------------------------------------------------
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please contact us by re-
plying to <a class="moz-txt-link-abbreviated" href="mailto:info@wirem.net">info@wirem.net</a>
Thank you
WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC)
--------------------------------------------------------------------
</pre>
</div>
</body>
</html>