[arin-ppml] Opposed to 2010-9 and 2010-12
In message <AANLkTi=obst=A-mt35+gKTvpgRgLfCxjWm1izBbOihXc at mail.gmail.com>, Will
iam Herrin writes:
> On Wed, Oct 13, 2010 at 7:47 PM, Mark Andrews <marka at isc.org> wrote:
> > In message <20101013232503.E70B05B1A60 at drugs.dv.isc.org>, Mark Andrews wr=
> >> In message <AANLkTiknLC+oXF9QLTBGp=3DXrxGSgPRG8Rg-SJq-8MpSs at mail.gmail.c=
> om>, Wi
> >> > Preparing and maintaining the configuration for one 6rd prefix is easy
> >> > enough. Two is not so bad. But a hundred? I wouldn't want to be the
> >> > guy stuck with debugging that morass.
> > ISP's allocate address blocks to 1000's of commercial clients.
> > Finding a new 6rd prefix for a new IPv4 allocation is no harder
> > that finding a address block for a commercial client. =A0In fact it
> > is easier as you can (but it would not be desirable) create multiple
> > prefixes if you find there is not a existing block that is big
> > enough.
> > If ISP's can support 1000's of commercial client address blockss
> > they can support 100's of 6rd prefixes.
> Go build me a distribution protocol so I can configure the 6rd
> translations in just one place (like I do for routes) and expect them
> to dynamically propagate to all of my v6/v4 borders. Then we'll talk
> about equivalence of effort.
> Bill Herrin
I could design it in about 10 minutes as could just about anyone
on this list.
telnet 6rd-prefix-server 6rd-prefix-port | import-6rd-table
Prefix count <4 octets>.
6rdPrefix (16 octets) | IPv4MaskLen (1 octet) | 6rdPrefixLen (1 octet)
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org