<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I Opposed</blockquote><div>A more positive approach would be a Arin cartoon animation on the demise of IPv4 and the resulting rescue by super hero ipv6 screened on CNN. :) 7 days as already mentioned is lost in the blink of an eye.<br>
RD<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a> [mailto:<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>]<br>
On<br>
> Behalf Of Member Services<br>
> Sent: Wednesday, May 20, 2009 9:06 AM<br>
> To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
> Subject: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
><br>
> ARIN received the following policy proposal and is posting it to the<br>
> Public Policy Mailing List (PPML) in accordance with Policy<br>
Development<br>
> Process.<br>
><br>
> This proposal is in the first stage of the Policy Development Process.<br>
> ARIN staff will perform the Clarity and Understanding step. Staff does<br>
> not evaluate the proposal at this time, their goal is to make sure<br>
that<br>
> they understand the proposal and believe the community will as well.<br>
> Staff will report their results to the ARIN Advisory Council (AC)<br>
> within<br>
> 10 days.<br>
><br>
> The AC will review the proposal at their next regularly scheduled<br>
> meeting (if the period before the next regularly scheduled meeting is<br>
> less than 10 days, then the period may be extended to the subsequent<br>
> regularly scheduled meeting). The AC will decide how to utilize the<br>
> proposal and announce the decision to the PPML.<br>
><br>
> In the meantime, the AC invites everyone to comment on the proposal on<br>
> the PPML, particularly their support or non-support and the reasoning<br>
> behind their opinion. Such participation contributes to a thorough<br>
> vetting and provides important guidance to the AC in their<br>
> deliberations.<br>
><br>
> The ARIN Policy Development Process can be found at:<br>
> <a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
><br>
> Mailing list subscription information can be found<br>
> at:<a href="https://www.arin.net/mailing_lists/" target="_blank">https://www.arin.net/mailing_lists/</a><br>
><br>
> Regards,<br>
><br>
> Member Services<br>
> American Registry for Internet Numbers (ARIN)<br>
><br>
><br>
> ## * ##<br>
><br>
><br>
> Policy Proposal Name: IPv4 Example Shortages<br>
><br>
> Proposal Originator:Martin J. Levy<br>
><br>
> Proposal Version: 1.0<br>
><br>
> Date: 20 May 2009<br>
><br>
> Proposal type: new<br>
><br>
> Policy term: permanent<br>
><br>
> Policy statement:<br>
><br>
> Add section 4.1.8 to the NRPM to state:<br>
><br>
> 4.1.8 IPv4 Example Shortages<br>
><br>
> Beginning on January 1, 2010, and on the first of each January and<br>
July<br>
> thereafter, for a period of 7 calendar days, ARIN will not process<br>
> requests from existing IPv4 holders for additional IPv4 space.<br>
><br>
> Rationale:<br>
><br>
> The IANA is expected to issue the last of the available IPv4 address<br>
> space to RIRs some time in 2011. RIRs are expected to run out<br>
> approximately one year later. These brief delays should be minimal<br>
> (no)<br>
> impact to organizations with existing space wanting more, but, can<br>
> provide a brief but visible glimpse into the future that awaits after<br>
> runout.<br>
><br>
> Organizations which fail to plan for these delays will have the option<br>
> of waiting for ARIN to issue their space, or, can avail themselves of<br>
> the transfer policy contained in section 8.3 of the NRPM (resulting<br>
> from<br>
> policy proposals 2008-6 and 2009-1). The cost of these delays will be<br>
> minimal compared to what will happen when space simply is no longer<br>
> available.<br>
><br>
> This policy has no impact on IPv6 assignments or allocations and has<br>
no<br>
> impact on new organizations making their first IPv4 request.<br>
><br>
> Timetable for implementation: 1 January 2010<br>
><br>
> _______________________________________________<br>
> PPML<br>
> You are receiving this message because you are subscribed to<br>
> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 20 May 2009 11:17:46 -0500<br>
From: "George, Wes E [NTK]" <<a href="mailto:Wesley.E.George@sprint.com">Wesley.E.George@sprint.com</a>><br>
To: Member Services <<a href="mailto:info@arin.net">info@arin.net</a>>, "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>"<br>
<<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID:<br>
<<a href="mailto:F7EB0A7C707E39409A73CD0353242551A7F1131A02@PLSWM01C.ad.sprint.com">F7EB0A7C707E39409A73CD0353242551A7F1131A02@PLSWM01C.ad.sprint.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I oppose this policy. As has been stated, 7 days doesn't make enough of a difference to get anyone's attention, and it's certainly not enough of a delay to drive people to look to alternatives like a transfer under the transfer policy, which would likely take months.<br>
<br>
Thanks,<br>
Wes<br>
-----Original Message-----<br>
From: <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a> [mailto:<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>] On Behalf Of Member Services<br>
Sent: Wednesday, May 20, 2009 10:06 AM<br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
<br>
ARIN received the following policy proposal and is posting it to the<br>
Public Policy Mailing List (PPML) in accordance with Policy Development<br>
Process.<br>
<br>
This proposal is in the first stage of the Policy Development Process.<br>
ARIN staff will perform the Clarity and Understanding step. Staff does<br>
not evaluate the proposal at this time, their goal is to make sure that<br>
they understand the proposal and believe the community will as well.<br>
Staff will report their results to the ARIN Advisory Council (AC) within<br>
10 days.<br>
<br>
The AC will review the proposal at their next regularly scheduled<br>
meeting (if the period before the next regularly scheduled meeting is<br>
less than 10 days, then the period may be extended to the subsequent<br>
regularly scheduled meeting). The AC will decide how to utilize the<br>
proposal and announce the decision to the PPML.<br>
<br>
In the meantime, the AC invites everyone to comment on the proposal on<br>
the PPML, particularly their support or non-support and the reasoning<br>
behind their opinion. Such participation contributes to a thorough<br>
vetting and provides important guidance to the AC in their deliberations.<br>
<br>
The ARIN Policy Development Process can be found at:<br>
<a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
<br>
Mailing list subscription information can be found<br>
at:<a href="https://www.arin.net/mailing_lists/" target="_blank">https://www.arin.net/mailing_lists/</a><br>
<br>
Regards,<br>
<br>
Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
## * ##<br>
<br>
<br>
Policy Proposal Name: IPv4 Example Shortages<br>
<br>
Proposal Originator:Martin J. Levy<br>
<br>
Proposal Version: 1.0<br>
<br>
Date: 20 May 2009<br>
<br>
Proposal type: new<br>
<br>
Policy term: permanent<br>
<br>
Policy statement:<br>
<br>
Add section 4.1.8 to the NRPM to state:<br>
<br>
4.1.8 IPv4 Example Shortages<br>
<br>
Beginning on January 1, 2010, and on the first of each January and July<br>
thereafter, for a period of 7 calendar days, ARIN will not process<br>
requests from existing IPv4 holders for additional IPv4 space.<br>
<br>
Rationale:<br>
<br>
The IANA is expected to issue the last of the available IPv4 address<br>
space to RIRs some time in 2011. RIRs are expected to run out<br>
approximately one year later. These brief delays should be minimal (no)<br>
impact to organizations with existing space wanting more, but, can<br>
provide a brief but visible glimpse into the future that awaits after<br>
runout.<br>
<br>
Organizations which fail to plan for these delays will have the option<br>
of waiting for ARIN to issue their space, or, can avail themselves of<br>
the transfer policy contained in section 8.3 of the NRPM (resulting from<br>
policy proposals 2008-6 and 2009-1). The cost of these delays will be<br>
minimal compared to what will happen when space simply is no longer<br>
available.<br>
<br>
This policy has no impact on IPv6 assignments or allocations and has no<br>
impact on new organizations making their first IPv4 request.<br>
<br>
Timetable for implementation: 1 January 2010<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
<br>
<br>
This e-mail may contain Sprint Nextel Company proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 20 May 2009 11:21:34 -0500<br>
From: Chris Boyd <<a href="mailto:cboyd@gizmopartners.com">cboyd@gizmopartners.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID: <<a href="mailto:F4BBE0C3-AACA-44AA-9D33-72ECDD418DC9@gizmopartners.com">F4BBE0C3-AACA-44AA-9D33-72ECDD418DC9@gizmopartners.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes<br>
<br>
Interesting idea, but I doubt that it will help much.<br>
<br>
Organizations that plan and participate in ARIN will know what's going<br>
on and just make their requests earlier or later as their needs dictate.<br>
<br>
Organizations that don't participate (or even read the easy to find<br>
documents) will just see this as another way that ARIN is being<br>
difficult to work with, obtuse, obscure, and probably several other<br>
things that should not be said on a public list.<br>
<br>
We're a service organization, and should provide those services even<br>
to groups that don't understand how things (should) work.<br>
<br>
--Chris<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 20 May 2009 10:12:47 -0700<br>
From: "Ted Mittelstaedt" <<a href="mailto:tedm@ipinc.net">tedm@ipinc.net</a>><br>
To: "'Member Services'" <<a href="mailto:info@arin.net">info@arin.net</a>>, <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID: <B822CFE064A44B39B8FCDC7608B532B8@tedsdesk><br>
Content-Type: text/plain; charset="US-ASCII"<br>
<br>
<br>
We (my org) opposes this proposal.<br>
<br>
May I recommend the following,<br>
<br>
Instead of this policy, submit an operational suggestion to the<br>
ARIN suggestion box that would have ARIN staff supply educational<br>
information regarding what IPv4 runout is, when the current projection<br>
of runout will occur, etc. to every organization that submits an<br>
IPv4 allocation request. This would be in addition to the normal<br>
processing of IPv4 allocation requests.<br>
<br>
There has been some discussion already about sending this info<br>
to all e-mail addresses in the whois database.<br>
<br>
Ted<br>
<br>
<br>
> -----Original Message-----<br>
> From: <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a><br>
> [mailto:<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>] On Behalf Of Member Services<br>
> Sent: Wednesday, May 20, 2009 7:06 AM<br>
> To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
> Subject: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
><br>
> ARIN received the following policy proposal and is posting it<br>
> to the Public Policy Mailing List (PPML) in accordance with<br>
> Policy Development Process.<br>
><br>
> This proposal is in the first stage of the Policy Development Process.<br>
> ARIN staff will perform the Clarity and Understanding step.<br>
> Staff does not evaluate the proposal at this time, their goal<br>
> is to make sure that they understand the proposal and believe<br>
> the community will as well.<br>
> Staff will report their results to the ARIN Advisory Council<br>
> (AC) within 10 days.<br>
><br>
> The AC will review the proposal at their next regularly<br>
> scheduled meeting (if the period before the next regularly<br>
> scheduled meeting is less than 10 days, then the period may<br>
> be extended to the subsequent regularly scheduled meeting).<br>
> The AC will decide how to utilize the proposal and announce<br>
> the decision to the PPML.<br>
><br>
> In the meantime, the AC invites everyone to comment on the<br>
> proposal on the PPML, particularly their support or<br>
> non-support and the reasoning behind their opinion. Such<br>
> participation contributes to a thorough vetting and provides<br>
> important guidance to the AC in their deliberations.<br>
><br>
> The ARIN Policy Development Process can be found at:<br>
> <a href="https://www.arin.net/policy/pdp.html" target="_blank">https://www.arin.net/policy/pdp.html</a><br>
><br>
> Mailing list subscription information can be found<br>
> at:<a href="https://www.arin.net/mailing_lists/" target="_blank">https://www.arin.net/mailing_lists/</a><br>
><br>
> Regards,<br>
><br>
> Member Services<br>
> American Registry for Internet Numbers (ARIN)<br>
><br>
><br>
> ## * ##<br>
><br>
><br>
> Policy Proposal Name: IPv4 Example Shortages<br>
><br>
> Proposal Originator:Martin J. Levy<br>
><br>
> Proposal Version: 1.0<br>
><br>
> Date: 20 May 2009<br>
><br>
> Proposal type: new<br>
><br>
> Policy term: permanent<br>
><br>
> Policy statement:<br>
><br>
> Add section 4.1.8 to the NRPM to state:<br>
><br>
> 4.1.8 IPv4 Example Shortages<br>
><br>
> Beginning on January 1, 2010, and on the first of each<br>
> January and July thereafter, for a period of 7 calendar days,<br>
> ARIN will not process requests from existing IPv4 holders for<br>
> additional IPv4 space.<br>
><br>
> Rationale:<br>
><br>
> The IANA is expected to issue the last of the available IPv4<br>
> address space to RIRs some time in 2011. RIRs are expected<br>
> to run out approximately one year later. These brief delays<br>
> should be minimal (no) impact to organizations with existing<br>
> space wanting more, but, can provide a brief but visible<br>
> glimpse into the future that awaits after runout.<br>
><br>
> Organizations which fail to plan for these delays will have<br>
> the option of waiting for ARIN to issue their space, or, can<br>
> avail themselves of the transfer policy contained in section<br>
> 8.3 of the NRPM (resulting from policy proposals 2008-6 and<br>
> 2009-1). The cost of these delays will be minimal compared to<br>
> what will happen when space simply is no longer available.<br>
><br>
> This policy has no impact on IPv6 assignments or allocations<br>
> and has no impact on new organizations making their first<br>
> IPv4 request.<br>
><br>
> Timetable for implementation: 1 January 2010<br>
><br>
> _______________________________________________<br>
> PPML<br>
> You are receiving this message because you are subscribed to<br>
> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 20 May 2009 12:19:54 -0500<br>
From: Chris Boyd <<a href="mailto:cboyd@gizmopartners.com">cboyd@gizmopartners.com</a>><br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID: <<a href="mailto:808A2308-9458-4256-80ED-8D5EDA786C89@gizmopartners.com">808A2308-9458-4256-80ED-8D5EDA786C89@gizmopartners.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
<br>
On May 20, 2009, at 12:12 PM, Ted Mittelstaedt wrote:<br>
<br>
> Instead of this policy, submit an operational suggestion to the<br>
> ARIN suggestion box that would have ARIN staff supply educational<br>
> information regarding what IPv4 runout is, when the current projection<br>
> of runout will occur, etc. to every organization that submits an<br>
> IPv4 allocation request. This would be in addition to the normal<br>
> processing of IPv4 allocation requests.<br>
<br>
Good idea.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 20 May 2009 12:23:39 -0500<br>
From: "Alex H. Ryu" <<a href="mailto:alex.ryu@kdlinc.com">alex.ryu@kdlinc.com</a>><br>
To: Chris Boyd <<a href="mailto:cboyd@gizmopartners.com">cboyd@gizmopartners.com</a>>, "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>"<br>
<<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID:<br>
<<a href="mailto:278B5E4BCD5E654385A9F83C7CA6D51799B91709D9@MAILBOX-01.qcommcorp.ad">278B5E4BCD5E654385A9F83C7CA6D51799B91709D9@MAILBOX-01.qcommcorp.ad</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Yes, instead of this proposal, ARIN staff can add "warning for IPv4 address depletion" and "IPv6 info" into top of message for every IPv4 address approval notice.<br>
That doesn't require any policy writing, and it can be done within ARIN staff's ability.<br>
<br>
I don't think one-week freeze for IPv4 address processing do much for the purpose.<br>
<br>
Alex<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a> [mailto:<a href="mailto:arin-ppml-bounces@arin.net">arin-ppml-bounces@arin.net</a>] On Behalf Of Chris Boyd<br>
Sent: Wednesday, May 20, 2009 12:20 PM<br>
To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
<br>
<br>
On May 20, 2009, at 12:12 PM, Ted Mittelstaedt wrote:<br>
<br>
> Instead of this policy, submit an operational suggestion to the<br>
> ARIN suggestion box that would have ARIN staff supply educational<br>
> information regarding what IPv4 runout is, when the current projection<br>
> of runout will occur, etc. to every organization that submits an<br>
> IPv4 allocation request. This would be in addition to the normal<br>
> processing of IPv4 allocation requests.<br>
<br>
Good idea.<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 20 May 2009 19:57:44 -0400<br>
From: Steve Bertrand <<a href="mailto:steve@ibctech.ca">steve@ibctech.ca</a>><br>
To: "Alex H. Ryu" <<a href="mailto:alex.ryu@kdlinc.com">alex.ryu@kdlinc.com</a>><br>
Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>><br>
Subject: Re: [arin-ppml] Policy Proposal: IPv4 Example Shortages<br>
Message-ID: <<a href="mailto:4A1498F8.2060007@ibctech.ca">4A1498F8.2060007@ibctech.ca</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Alex H. Ryu wrote:<br>
> Yes, instead of this proposal, ARIN staff can add "warning for IPv4 address depletion" and "IPv6 info" into top of message for every IPv4 address approval notice.<br>
> That doesn't require any policy writing, and it can be done within ARIN staff's ability.<br>
<br>
I oppose this policy.<br>
<br>
As far as the "warning", I have discussed this with numerous people<br>
off-list. There are two sides to that coin:<br>
<br>
- tell everyone via email or a warning with new allocation requests<br>
about the IPv4 runout<br>
<br>
- there are always going to be other pressing issues, so which ones do<br>
we pick-and-choose to warn people about<br>
<br>
Granted, this is quite the pickle of an issue, but to some, there may be<br>
larger issues that warrant warnings, and if ARIN decides to warn about<br>
runout and not another, someone is bound to get upset.<br>
<br>
With that said, I'm still going to post the request to the suggestion<br>
box (notification included in email upon 2008-7 ratification). Just<br>
because *I'm* not worried about it and am pretty much prepared, doesn't<br>
mean that other ops/businesses aren't...particularly new ones that may<br>
enter the playing field at or near the breaking point of the critical path.<br>
<br>
> I don't think one-week freeze for IPv4 address processing do much for the purpose.<br>
<br>
Of course it won't. If anything, it will cause a panic-type surge for<br>
requests just prior, or just after that week. Besides, I'm on holidays<br>
for those weeks ;)<br>
<br>
Steve<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/x-pkcs7-signature<br>
Size: 3233 bytes<br>
Desc: S/MIME Cryptographic Signature<br>
URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20090520/d42ceb3c/attachment.bin" target="_blank">http://lists.arin.net/pipermail/arin-ppml/attachments/20090520/d42ceb3c/attachment.bin</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ARIN-PPML mailing list<br>
<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
<br>
End of ARIN-PPML Digest, Vol 47, Issue 57<br>
*****************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br>Rudi Daniel<br>Independent Consultant<br>e Business<br><a href="http://www.svgpso.org">www.svgpso.org</a><br>1 784 533 7321<br>