[147113] in North American Network Operators' Group
Re: IPv6 prefixes longer then /64: are they possible in DOCSIS
daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Dec 2 10:21:30 2011
From: Mark Tinka <mtinka@globaltransit.net>
To: nanog@nanog.org
Date: Fri, 2 Dec 2011 23:19:28 +0800
In-Reply-To: <CALFTrnPbNEOyRrPpqUTGqfRR3YK7-hp8A+U=BM=+kqpepHnRhg@mail.gmail.com>
Cc: Bill Stewart <nonobvious@gmail.com>
Reply-To: mtinka@globaltransit.net
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--nextPart5095990.J7jAO3Rtm0
Content-Type: Text/Plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Thursday, December 01, 2011 08:19:51 AM Ray Soucy wrote:
> There is a lot of talk about "buggy" systems that are
> unable to handle prefixes longer than 64; but I've yet
> to encounter one. I imagine if I did it would be
> treated as a bug and fixed. So to the question of
> supporting different prefix lengths: Yes. You should
> support any valid IPv6 prefix length; it takes a few
> extra lines of code in the beginning; but will save you
> a lot of re-coding in the end.
Exactly.
/126's for point-to-points, and /112's for router LAN's=20
here, 6 years and counting.
Mark.
--nextPart5095990.J7jAO3Rtm0
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iQIcBAABAgAGBQJO2OyEAAoJEGcZuYTeKm+Gzy0P/i53J91Zhn/2IynNVcj8XfUd
YmaipL0u+yNKt5xOQVCXJfNilFKK11Oze4POobfQ6aLQ5tR9CGZ2rUlf3pe4/16I
xf4A5jwp2L7+QRf/QPija08NViwzAAAJWSUEzG6bNkA2EsbCkLMgSsG8DSCEeUtH
kKtXXN7KVt+pXfcMUC2YR4YQ6dSHox1YTtAnW3V3ma3bYDuSi/RubiGhUwPXB+Vh
qtW+HIey04+FAa+Plx0rR+DkJOBThfkwxAYcPbC4bHoPL1i9E+Ik30Omt1yu3N7E
Wj1cRDSqSsQqn98fzLzzyPteVLSM2j6BNq5dKJVJ3CAbwfpRYV+jPq9JekrJRZ6p
/Js9Bay8rwiqC8U4WF4Z+C513YDQ70NKOmpjwW9mPAkSYQr4G/u5zVztD5HLe1o0
pJJ248Ns8WdCsBA/x17iXTFGx+v+E9Sj4P6rzgXzuLyQabgc+DqgodEJoc+p4C+q
GkgLwm+niJlEaKoqkGwfu7fU3/+w4doaFPVYIKm/9EtLiDPjyxB2hfZXRVw2xGM8
jNrFOHl6nl+VYF4FH3ej5MhE/m0/HGOmElmVJjHAE7duhptKvzTCmE3okgNBRufK
3ceIKdwVMViHxgDu6evpksF2LyAynhLkZ0Q4bg2ZAYHMZaxUBo3Iy+rsNNMBWdkz
mbf9sIvIuiF6QoSuGzIZ
=oiHp
-----END PGP SIGNATURE-----
--nextPart5095990.J7jAO3Rtm0--
