ARIN and IPv6 Requests

Thu Feb 24 06:10:41 UTC 2011

(Yeah, high reply latency...)

Is Carrier V still filtering at sub-/32 on their IPv6 peerings? Last I was in a position to check, not even Apple's /45 was visible from inside AS701.

-C

On Feb 10, 2011, at 12:25 PM, Eric Clark wrote:

> Don't remember about the v4 part, but 3 years ago they issued me a /48, specifically for my first site and indicated that a block was reserved for additional sites. I can probably dig that up.
> 
> Sent from my iPad
> 
> On Feb 10, 2011, at 12:18 PM, Jason Iannone <jason.iannone at gmail.com> wrote:
> 
>> It also looks like there isn't a policy for orgs with multiple
>> multihomed sites to get a /48 per site.  Is there an exception policy
>> somewhere?
>> 
>> On Thu, Feb 10, 2011 at 12:50 PM,  <ADWebb at dstsystems.com> wrote:
>>> Initial. Documenting IPv4 usage is in the request template.
>>> 
>>> --
>>> Adam Webb
>>> 
>>> 
>>> 
>>> 
>>> 
>>> From:
>>> "Nick Olsen" <nick at flhsi.com>
>>> To:
>>> <nanog at nanog.org>
>>> Date:
>>> 02/10/2011 01:45 PM
>>> Subject:
>>> re: ARIN and IPv6 Requests
>>> 
>>> 
>>> 
>>> We requested our initial allocation without any such questions. Is this
>>> your initial or additional?
>>> 
>>> Nick Olsen
>>> Network Operations
>>> (855) FLSPEED  x106
>>> 
>>> ----------------------------------------
>>> 
>>> From: ADWebb at dstsystems.com
>>> Sent: Thursday, February 10, 2011 2:38 PM
>>> To: nanog at nanog.org
>>> Subject: ARIN and IPv6 Requests
>>> 
>>> Why does ARIN require detailed usage of IPv4 space when requesting IPv6
>>> space? Seems completely irrelevant to me.
>>> 
>>> --
>>> Adam Webb
>>> EN & ES Team
>>> desk: 816.737.9717
>>> cell: 916.949.1345
>>> ---------------------------------------
>>> The biggest secret of innovation is that anyone can do it.
>>> ---------------------------------------
>>> 
>>> -----------------------------------------
>>> Please consider the environment before printing this email and any
>>> attachments.
>>> 
>>> This e-mail and any attachments are intended only for the
>>> individual or company to which it is addressed and may contain
>>> information which is privileged, confidential and prohibited from
>>> disclosure or unauthorized use under applicable law.  If you are
>>> not the intended recipient of this e-mail, you are hereby notified
>>> that any use, dissemination, or copying of this e-mail or the
>>> information contained in this e-mail is strictly prohibited by the
>>> sender.  If you have received this transmission in error, please
>>> return the material received to the sender and delete all copies
>>> from your system.
>>> 
>>> 
>>> 
>> 
> 