[nog] IPv6

[Marian Marinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/02/2014 11:18 AM, Vasil Kolev wrote:
> On Tue, 2014-09-02 at 10:50 +0300, Marian Marinov wrote:
>> Hi guys, I'm preparing to configure my Ripe Atlas Anchor in Sofia and I wish to have both IPv4 and IPv6 for it.
>> 
>> Since I don't have much experience with IPv6 I would like to ask a few questions :)
>> 
>> - If I want to use a /64 from my RIPE provided IPv6 addresses, do I need to give another /64 to my uplink ISP
>> for transport?
>> 
>> - I have received /64 from my ISP but I did not receive any transport IPs. Is this normal?
>> 
> 
>> From what I've seen, there has to be a link-specific network, and to
> route a /64 through it. In most cases there should be more than a /64 routed, e.g. a /60 or something (as people
> have more than one segment anyway).
Having a /64 for a transport seams like a huge waste of IPs. Exactly what happened to IPv4 in its early days :)

> 
> For the link network it's an open question. A lot of people say "just use /64", but I have seen /126, /112 and all
> other kinds of weirdnesses.
> 
> If you got just one /64, most probably the people who assigned it to you had no idea what they were doing :)

I was suspecting that... but I first mistrust my own judgement then others :) This is why I asked here :)

Thanks


- -- 
Marian Marinov
Founder & CEO of 1H Ltd.
Jabber/GTalk: hackman at jabber.org
ICQ: 7556201
Mobile: +359 886 660 270
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQFfvoACgkQ4mt9JeIbjJSphACgmDlkMfizo3wh2JKXfX9uhtNV
lCEAnjsg0R4O+egcnRwKet1s6Xf8E2m5
=QUHm
-----END PGP SIGNATURE-----