<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body wsmode="reply" bgcolor="#FFFFFF" text="#000000">
I agree with Mike too. We are expanding on the commercial side of
the business, considerably, but these costs would be hammering our
clients with a very high cost for IPs. Therefore reducing our ipv6
footprint/efforts due to costs. Client adoption of the technology
requires sane pricing.<br>
<br>
Jean-Francois Laforest, M. Eng.<br>
Director of Global Network Operations<br>
TeliPhone Corp.<br>
<br>
On 12-03-14 02:16 PM, Mark Pace wrote:
<blockquote cite="mid:4F60E081.7020703@jolokianetworks.com"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<font face="Calibri">I agree with Mike. We designed our network
around our /32. Having to change that now or incurring fees
that are orders of magnitude greater would cause a lot of grief
for us and our customers.<br>
<br>
<br>
Mark Pace<br>
CTO<br>
Jolokia Networks<br>
</font>
<div class="moz-signature">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title></title>
<br>
</div>
On 2012-03-14 11:00 AM, Mike A. Salim wrote:
<blockquote
cite="mid:F529791B49ADA64A94A476B8D93BE22801C17033@EXCH-3.adtimail.com"
type="cite">
<pre wrap="">This is a good discussion. We are currently utilizing our /32 IPv6 space. If we are forced to go to a smaller allocation at this point we would be forced to renumber, and it would cause issues for us and for our customers. And I totally concur that an increase in IPv6 fees at this early stage of IPv6 adoption will be counter productive.
I suggest that if XS or smaller allocations are introduced, that existing allocations be grandfathered without a price change. There is enough IPv6 space that this should not be a problem.
Best regards
Mike
A. Michael Salim
VP and Chief Technology Officer,
American Data Technology, Inc.
PO Box 12892
Research Triangle Park, NC 27709, USA
P: (919)544-4101 x101
F: (919)544-5345
E: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:msalim@localweb.com">msalim@localweb.com</a>
W: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.localweb.com">http://www.localweb.com</a>
PRIVACY NOTIFICATION: This e-mail message, including any attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is for the sole use of the intended recipient(s). It may contain confidential and/or legally privileged information. Unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Please don't print this e-mail unless you really need to.
-----Original Message-----
From: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:arin-discuss-bounces@arin.net">arin-discuss-bounces@arin.net</a> [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:arin-discuss-bounces@arin.net">mailto:arin-discuss-bounces@arin.net</a>] On Behalf Of Randy Carpenter
Sent: Tuesday, March 13, 2012 5:47 PM
To: arin-discuss
Subject: [arin-discuss] Status of realigning the IPv6 fee structure?
What is the status of realigning the IPv6 fee structure so that it matches the current policy of allocating based on nibble boundaries? This has been discussed in the past, but I have not heard anything lately. Jumping from $2,250 right to $9,000 doesn't make much sense.
thanks,
-Randy
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to the ARIN Discussion Mailing List (<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
</body>
</html>