This is a read only archive of pad.okfn.org. See the shutdown announcement for details.

bcop-small-ipv6 ## This is draft text for a proposed BCOP about how to deploy IPv6 on small
## residential providers. Anyone contributing or interested is encouraged to
## join the bcop@ripe.net mailing list -- send an email to bcop-request@ripe.net
## with 'subscribe' in the Subject header.
##
## At this stage, do not worry about formatting, the goal
## is just to get the material here and curate and typeset
## it later.
##
## This is intended as a companion document to
## http://go6.si/docs/IPv6-troubleshooting-for-helpdesks-v01.pdf
## describing how small networks can deploy IPv6 in such a way
## as to most effectively benefit from the troubleshooting guide.

Audience

This document is intended for small providers of Internet service to end users. This
might mean wireless ISPs in rural places, xDSL resellers or new providers of whichever
description. Such providers should have a strong interest in deploying IPv6 for address
scarcity reasons but at the same time, because they are small organisations, will have
limited engineering resources. The hope is that this document will guide this kind of
organisation through the technical decisions necessary to enable IPv6 on their networks,
and in particular to do this in a way that does not impose significant additional support
burdens. So the intended audience is not large providers with dedicated groups of staff
for design, engineering and operations though perhaps it will be useful to them as well.

For this reason, this guide is purposely not exhaustive. It doesn't address the general
question of how to design and build a network. That would be impossible in a short,
practical text. It assumes that you already have an IPv4 network running, a basic
understanding of IP routing and some of the necessary supporting infrastructure for
provisioning. It is concerned with networks that are larger and more complicated
than a single site, but smaller than a national or regional provider. This is about 
networks with end-users -- so-called ``eyeball'' networks -- and not networks primarily
providing services or content networks.

General Architecture

ww: brief description of my favourite way of doing these things:

ospf3 works entirely on multicast. still important to have global addresses on each
link primarily for troubleshooting. routers need at least one global address for sourcing
icmp messages. they also need ipv4 addresses to use as router-id (need not be
global, but need to be unique).

Address Assignment

You *do* have a plan for allocating addresses, right? ipv6 not so different (only
forget scarcity and assign a /56 or /48 upon request