Re: minimum IPv6 announcement size

2013-10-01 Thread Rob Seastrom
William Herrin b...@herrin.us writes: IPv4 jumped from 8 bits to 32 bits. Which when you think about it is the same ratio as jumping from 32 bits to 128 bits. Sorry for the late reply, Bill, but you were snoozing when they taught logarithms in high school weren't you? Jumping from 8 bits to

Re: minimum IPv6 announcement size

2013-10-01 Thread William Herrin
On Tue, Oct 1, 2013 at 12:04 PM, Rob Seastrom r...@seastrom.com wrote: William Herrin b...@herrin.us writes: IPv4 jumped from 8 bits to 32 bits. Which when you think about it is the same ratio as jumping from 32 bits to 128 bits. Jumping from 8 bits to 32 bits (1:16mm) is the same ratio as

Re: minimum IPv6 announcement size

2013-10-01 Thread Owen DeLong
On Oct 1, 2013, at 11:11 , William Herrin b...@herrin.us wrote: On Tue, Oct 1, 2013 at 12:04 PM, Rob Seastrom r...@seastrom.com wrote: William Herrin b...@herrin.us writes: IPv4 jumped from 8 bits to 32 bits. Which when you think about it is the same ratio as jumping from 32 bits to 128

RE: minimum IPv6 announcement size

2013-10-01 Thread Leo Vegoda
William Herrin wrote: [...] And yet we're allocating /19's If the stats published at http://www.nro.net/pub/stats/nro/delegated-extended are to be believed then the only two /19s were allocated in 2005 when the HD-ratio value in the policy was lower. Looking at all the RIRs together another

TWC / MTC broadband

2013-10-01 Thread Tim Durack
Anyone alive at TWC and/or MTC broadband? Looks like AS36100 (MTC Broadband) is incorrectly announcing 72.43.125.0/24. This is causing problems for TWC users who are in 72.43.125.0/24 -- Tim:

Re: minimum IPv6 announcement size

2013-10-01 Thread Ryan McIntosh
I'd love to be able to turn the microwave and oven on with my phone.. maybe ten years from now lol.. In all seriousness though (and after skimming some of the other responses), I absolutely understand the ideals and needs amongst conserving memory on our routers for the sake of the future of bgp

semi-ot: network monitoring tools

2013-10-01 Thread John Levine
I was talking to a bunch of people who run ISPs and other networks in LDCs (yes, including Nigeria) and someone asked about monitoring tools to watch traffic on his network so he can get advance warning of dodgy customers and prevent complaints and blacklisting. These people are plenty smart, but

Re: minimum IPv6 announcement size

2013-10-01 Thread bmanning
back in the good o'l days when we would hand out 24 bits for the number of hosts in a network. It was too many bits then and is too many bits now a /64 is just overkill. /bill On Tue, Oct 01, 2013 at 03:11:39PM -0400, Ryan McIntosh wrote: I'd love to be able to turn the microwave

Re: minimum IPv6 announcement size

2013-10-01 Thread Owen DeLong
The original plan was to go from 32 to 64 bits total. The additional 64 bits were added purely for the sake of EUI-64 based addressing, and really, 64 bits of network number is way more than enough. The /64 a are not what justify the larger blocks. That's IPv4 think. In IPv6, it is far

Re: minimum IPv6 announcement size

2013-10-01 Thread Scott Weeks
--- o...@delong.com wrote: From: Owen DeLong o...@delong.com we will have plenty of address space to number the internet for many many years. -- You can't know the future and what addressing requirements it'll bring: I have to say that in 1981,

Re: minimum IPv6 announcement size

2013-10-01 Thread Cutler James R
I try not to think about sinners too much when planning networks. Subnets are more interesting. Maybe many of you like spending time maintaining NAT configurations and creatively masking as determined by today's end system count on each subnet. This all, of course, in the interest of maximum

Re: semi-ot: network monitoring tools

2013-10-01 Thread Michael Shuler
On 10/01/2013 02:29 PM, John Levine wrote: I was talking to a bunch of people who run ISPs and other networks in LDCs (yes, including Nigeria) and someone asked about monitoring tools to watch traffic on his network so he can get advance warning of dodgy customers and prevent complaints and

Facebook NOC Contact

2013-10-01 Thread Daniel Hood
Hi, Having some issues with traffic to Facebook. Is there anyone here from Facebook lurking on the list? Or does anyone have a better contact then their help form? Regards, Daniel

Re: Facebook NOC Contact

2013-10-01 Thread Justin M. Streiner
On Tue, 1 Oct 2013, Daniel Hood wrote: Having some issues with traffic to Facebook. Is there anyone here from Facebook lurking on the list? Or does anyone have a better contact then their help form? Try o...@facebook.com jms

Re: semi-ot: network monitoring tools

2013-10-01 Thread Dobbins, Roland
On Oct 2, 2013, at 2:29 AM, John Levine wrote: These people are plenty smart, but don't have a lot of money. Enable NetFlow, and use some open-source NetFlow collection/analysis system like nfdump/nfsen, etc. dnstop and the like for DNS can be pretty revealing, as well.

Re: semi-ot: network monitoring tools

2013-10-01 Thread Ryan Dooley
Coworkers of mine introduced me to Observium: http://www.observium.org/wiki/Main_Page Cheers, Ryan On Tue, Oct 1, 2013 at 8:55 PM, Dobbins, Roland rdobb...@arbor.net wrote: On Oct 2, 2013, at 2:29 AM, John Levine wrote: These people are plenty smart, but don't have a lot of money.