[NANOG-announce] NANOG 71 Call for Presentations is Open

NANOG Community, The NANOG Program Committee is excited to announce that we are now accepting proposals for all sessions at NANOG 71 in San Jose, CA, October 2-4 2017. Below is a summary of key details from the Call for Presentations

Re: Point 2 point IPs between ASes

> if you don't need SLAAC, do whatever makes sense for you. And never be > greedy: give your end-users a /48 i say give them a /129 just to piss off a certin bigot :)

Re: Point 2 point IPs between ASes

> I wouldn't use link-local in context of Inter-Domain Routing. indeed randy

Re: strange routing anomalies

Hahahaha -- Onward!, Jason Hellenthal, Systems & Network Admin, Mobile: 0x9CA0BD58, JJH48-ARIN On Jun 29, 2017, at 18:01, Ken Chase wrote: https://stat.ripe.net/widget/routing-history#w.resource=as15562&w.starttime=2017-01-15T00%3A00%3A00&w.endtime=2017-06-23T00%3A00%3A00&show=Maxmize

Re: Point 2 point IPs between ASes

In message <20170629150630.glfvte2ures27p2n@Vurt.local>, Job Snijders writes: > On Wed, Jun 28, 2017 at 11:09:25PM +0200, Thomas Bellman wrote: > > On 2017-06-28 17:03, William Herrin wrote: > > > The common recommendations for IPv6 point to point interface numbering > > > are: > > > > > > /64 >

strange routing anomalies

https://stat.ripe.net/widget/routing-history#w.resource=as15562&w.starttime=2017-01-15T00%3A00%3A00&w.endtime=2017-06-23T00%3A00%3A00&show=Maxmized :D Nice job, Job. /kc -- Ken Chase - m...@sizone.org Guelph Canada

Re: Point 2 point IPs between ASes

On Thu, 29 Jun 2017, William Herrin wrote: Heck, I’m gonna do whatever it takes to NOT subnet on bits with my v6 deployment. Hopefully with v6, gone are the days of binary subnetting math. I hedged my bets when I laid out our v6 space at my previous $dayjob. We used /126s for point-to-poin

Re: Point 2 point IPs between ASes

On Thu, Jun 29, 2017 at 12:51 AM, Aaron Gould wrote: > Thanks Bill, I thought with ipv6 it was a sin to subnet on bit boundaries > and not on nibble boundaries. > Hi Aaron, Not a sin but you're making more work for yourself if you subnet on other-than four-bit nibble boundaries. Each character

Re: Point 2 point IPs between ASes

On Wed, Jun 28, 2017 at 11:09:25PM +0200, Thomas Bellman wrote: > On 2017-06-28 17:03, William Herrin wrote: > > The common recommendations for IPv6 point to point interface numbering are: > > > > /64 > > /124 > > /126 > > /127 > > I thought the only allowed subnet prefix lengths for IPv6 were /6

Re: Russian diplomats lingering near fiber optic cables

I pretended to be a Russian diplomat today. Tim On 6/3/17 12:13 PM, Matthew Petach wrote: > On Fri, Jun 2, 2017 at 11:40 AM, wrote: > [...] >> >> Well, I'd be willing to buy that logic, except the specific buildings called >> out look pretty damned big for just drying off a cable. For example,

RE: Internetpulse.net is dead

Also the dropdown for network, can you add search capability so no scrolling need? Looking good so far, I'll use this daily. Thanks, Kyle Weller Kyle Weller Quality Control Administrator Office 610.678.7002 | Service Desk 484.772.1110 Managed Services Cloud Services Disaster Recovery website

RE: Internetpulse.net is dead

Good work, However the constant captcha sucks allot, can you add a few shorter frequencies? Maybe 1-10 seconds rather than one minute intervals? I'd also like to see perhaps a graph view of Comcast, Level3, Verizon, etc to see if any latency between networks perhaps done via traceroutes? Thanks

Re: Point 2 point IPs between ASes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2017-06-28 17:03, William Herrin wrote: > The common recommendations for IPv6 point to point interface numbering are: > > /64 > /124 > /126 > /127 I thought the only allowed subnet prefix lengths for IPv6 were /64 and /127. RFC 4291 states:

Re: Internetpulse.net is dead

I guess one way is to compile list of Looking Glass servers on those providers and also list of IPs that belong to those and start pinging each other to produce the matrix. You can also try RIPE Atlas or www.maplatency.com. RIPE and Maplatency can be automated using API so the matrix could be buil