Dale W. Carder

72 Followers
131 Following
110 Posts
Network Engineer at Lawrence Berkeley National Laboratory working on the Energy Sciences Network (ESnet), building networks for International science projects such as the Large Hadron Collider (LHC) and the FABRIC testbed.
LinkedInhttps://www.linkedin.com/in/dwcarder/
GitHubhttps://github.com/dwcarder
Etherkillershttp://www.fiftythree.org/etherkiller/
Call SignW9DWC
@jtk Every single time I have been at CERN.
Google takes a big step backwards in their connectivity to the rest of the Internet:

vuvuzela levels are 74% and falling

(74%) ■■■■■■■□□□

macho man randy savage levels are holding at 69%

(69%) ■■■■■■□□□□

@benjojo Local to me, Verizon is installing *new* fiber handholds serving their 5G stations which are labeled as MCI.

Experian: “Important: your Email Address was found on the Dark Web”

It's also on the “Light Web" or whatever it is we call it, so people can email me.

ESnet Announces First Trans-Atlantic Subsea Spectrum Agreement

ESnet has signed a long-term lease agreement with Aqua Comms for 25% of a fiber pair linking New York, Dublin, and London — ESnet's first trans-Atlantic spectrum acquisition.

ESnet

Soooooo...

draft-ietf-grow-bgpopsecupd-01 is online! Looking for people to take a look:

https://datatracker.ietf.org/doc/draft-ietf-grow-bgpopsecupd/

And maybe file some issues here: https://github.com/ichdasich/draft-ietf-grow-bgpopsecupd

Updated BGP Operations and Security

The Border Gateway Protocol (BGP) is the protocol almost exclusively used in the Internet to exchange routing information between network domains. Due to this central nature, it is important to understand the security and reliability measures that can and should be deployed to prevent accidental or intentional routing disturbances. Previously, security considerations for BGP have been described in [RFC7454]. Since the publications of [RFC7454], several developments and changes in operational practice took place that warrant an update of these best current practices. This document updates [RFC7454], reiterating the best practices for BGP security from that document and adding new practices and recommendations that emerged since the publication of [RFC7454]. In the current version, this document covers practices to protect the BGP sessions itself such as Time to Live (TTL), the TCP Authentication Option (TCP-AO), and control-plane filtering. It also describes measures to better control the flow of routing information, using prefix filtering and automation of prefix filters, max-prefix filtering, Autonomous System(AS) path filtering, route flap dampening, and BGP community scrubbing. Newly added information and improvements include a unification of terminology, orienting it in [RFC9234], changing recommendations regarding IXP LAN prefixes to align with operational practice, discussing ASPA and BGP roles, expanding on community scrubbing, filter generation and evaluation practices to limit performance overhead, expanding on outbound and internal filtering for defense in depth, global prefix limits, and community based filtering for downstream prefixes.

IETF Datatracker
@daniel1820815 It may be fun to dig into this a bit more, namely in that implementation of a candidate datastore and rollback-on-error are optional.
After Google killed their dns registrar and sold the dns hosting business to Squarespace, I finally got the email I had dreaded. I am of course using DNS features that they will not support, and Google helpfully recommends "you should consider looking for an alternative from another provider and configure that ahead of your domain migration." So, where to next? All I need are a few dynamic dns entires for AAAA and SSHFP records. Why is this so hard? #killedbygoogle