Hi Jared,
Easiest thing would be breaking into sub-100G channels (e.g. 4x 25G) and
using DWDM optics + Amp + Compensation + Pre-Amp to transport it across the
100km.
Same parts for all configs:
*) 1x Amplifier => 1 slot
*) 1x 100km dispersion compensation => separate 1U
*) 1x Pre-Amplifier => 1
> cc.rg.net was unavailable over rsync for several days this week as
> well.
sorry. it was cb and cc. it seems some broken RPs did not have the
ROA needed to get to our westin pop. cf this whole thread.
luckily such things never happen in real operations. :)
randy
Outlook is a client. Microsoft e-mail servers run Sex-Change and the
outlook.com domain refers to the servers, not the clients. The Outlook client
can "connect" to just about any server ever written but has nothing to do with
Microsoft Sex-Change servers.
--
Be decisive. Make a decision,
Hi Tony,
I realise there are quite some moving parts so I'll try to summarise our design
choices and reasoning as clearly as possible.
Rsync was the original transport for RPKI and is still mandatory to implement.
RRDP (which uses HTTPS) was introduced to overcome some of the shortcomings of
> r0.sea#sh ip bgp rpki table | i 3130
> 147.28.0.0/2020 3130 0 147.28.0.84/323
> 147.28.0.0/1919 3130 0 147.28.0.84/323
> 147.28.64.0/19 19 3130 0 147.28.0.84/323
> 147.28.96.0/19 19 3130 0
On 10/30/20 23:57, Doug Barton wrote:
I would hesitate to blame BT. I have a macbook pro from ~1 year ago,
on Catalina, and I use BT extensively ... mouse, keyboard, and
headset. I do have location services trimmed down to just find my mac.
I ran: ping -c 1000 -i 0.1
1000 packets
As I've pointed out to Randy and others and I'll share here.
We planned, but hadn't yet upgraded our Routinator RP (Relying Party)
software to the latest v0.8 which I knew had some improvements.
I assumed the problems we were seeing would be fixed by the upgrade.
Indeed, when I pulled down the new
7 matches
Mail list logo
