Since we all live on standards, I can suggest RFC7946, GeoJSON
(https://tools.ietf.org/html/rfc7946) for all of your location specification
needs:
{
"type" : "Point",
"coordinates" : [
-121.556359,
39.5137752
This is an excellent suggestion and I'll do more research into use of the
geojson format from this RFC. Looks very similar to data that can be fed
through a small perl or python script to batch output google earth KML
format files, to give people a quick and easy GUI overview of an area. My
thought
This is quite a nice write up by a colleague of mine:
https://www.linkedin.com/pulse/build-your-own-anycast-network-9-steps-samir-jafferali
@natmorris did something similar 18 months to 2 years or so ago too
video below from uknof 30 ..
https://youtu.be/itEtjsauwFQ
Sent from Samsung Mobile on O2
Original message From: Franck Martin via NANOG
Date: 12/12/2016 18:39 (GMT+00:00) To: NANOG
Subject: Build an any
Wow thanks for sharing both of these. Anycast can be "black magic"
sometimes, and the more that is known about it by operators the better. I'm
somewhat surprised that ECMP
I've done a little poor-mans anycasting within a network by simply using
OSPF and some /32's. Had IPv4 space not been at such
> On Dec 12, 2016, at 1:59 PM, Theodore Baschak wrote:
>
> Wow thanks for sharing both of these. Anycast can be "black magic"
> sometimes, and the more that is known about it by operators the better.
Honestly, it’s not that difficult… Here are a few papers from quite a while
ago, when some
If you're doing ECMP w/i the DC, PMTUD does come to mind, though:
https://blog.cloudflare.com/path-mtu-discovery-in-practice/
--
Hugo Slabbert | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E | also on Signal
On Mon 2016-Dec-12 15:59:29 -0600, Theodore Baschak
wrote:
Wow tha
7 matches
Mail list logo
