nanog mailing list archives

Re: Creating an IPv6 addressing plan for end users


From: Joel Jaeggli <joelja () bogus com>
Date: Mon, 28 Mar 2011 04:20:23 -0700

On 3/23/11 6:14 AM, Hammer wrote:
Nathalie,
      As an end customer (not a carrier) over in ARIN land I purchased a /48
about a year ago for our future IPv6 needs. We have 4 different Internet
touchpoints (two per carrier) all rated at about 1Gbps. Recently, both
carriers told us that the minimum advertisement they would accept PER
CIRCUIT would be a /48. I was surprised to say the least. Basically a /48
would not be enough for us. The arguement was that this was to support all
the summarization efforts and blah blah blah. Even though my space would be
unique to either carrier. So now I'm contemplating a much larger block.
Seems wasteful but I have to for the carriers. Have you heard of this
elsewhere or is this maybe just an ARIN/American thing? Both carriers told
me that in discussions with their peers that they were all doing this.

there are providers that will accept more specific prefixes from the
customers for internal use. since /48 is the minimum arin allocation
there is observed to be general consensus on not accepting prefixes
longer than /48 into the dfz.

http://www.verizonbusiness.com/Products/networking/internet/ipv6/policy.xml

is one such example of a transit provider that will carry longer
prefixes internally.

 -Hammer-

"I was a normal American nerd."
-Jack Herer





On Wed, Mar 16, 2011 at 1:52 PM, Schiller, Heather A <
heather.schiller () verizonbusiness com> wrote:


For those who don't like clicking on random bit.ly links:

http://www.ripe.net/training/material/IPv6-for-LIRs-Training-Course/IPv6
_addr_plan4.pdf

 --Heather

-----Original Message-----
From: Nathalie Trenaman [mailto:nathalie () ripe net]
Sent: Wednesday, March 16, 2011 5:05 AM
To: nanog () nanog org
Subject: Creating an IPv6 addressing plan for end users

Hi all,

In our IPv6 courses, we often get the question: I give my customers a
/48 (or a /56 or a /52) but they have no idea how to distribute that
space in their network.
In December Sander Steffann and Surfnet wrote a manual explaining
exactly that, in clear language with nice graphics. A very useful
document but it was in Dutch, so RIPE NCC decided to translate that
document to English.

Yesterday, we have published that document on our website and we hope
this document is able to take away some of the fear that end users seem
to have for these huge blocks.
You can find this document here:

http://bit.ly/IPv6addrplan (PDF)

I look forward to your feedback, tips and comments.

With kind regards,

Nathalie Trenaman
RIPE NCC Trainer






Current thread: