Eli Lindsey
Eli Lindsey
Unfortunately I need to send flowspec redirect routes to Juniper gear, so I'll have to patch my exa to support the ietf draft. Given the RFC (still ☹️) hasn't been...
> I can however see a 20 byte ipv6 ext community forged, but with wrong type and subtype. It is the correct type and subtype, but you're looking for a...
As for rfc5701 specifically - support for it was added to be able to send the ipv6 extended community for the 0x000c next hop action. I don't believe anything else...
I don't speak for exa or Thomas, so anything he says overrides me - but I'll voice my thoughts > what about the following : `redirect-to-nexthop-vrf-rt-ipv6 :` I would first...
Ahh, thanks for the fix. 🙂 I think the 0x0002 in the patch is incorrect. RFC 5701 specifies a route target format of type 0x0002, but draft-ietf-idr-flow-spec-v6-08 is the actual...
Previously https://github.com/MaterializeInc/materialize/issues/7115
> mz_source_info needs a better name. "info" is a pet peeve of mine. #7230 is a +1 for this, plus possibly layering a view on top of mz_sources/mz_source_info if that...
@petrosagg know if this is still valid after separation landed?
Will need to determine if these are one-shot sinks, streaming sinks, or both and tackle those as separate work items. The clearest path and likely first step is one-shot sinks,...
Out of curiosity, have any suitable Date::Manip alternatives popped up in the past couple of years? I'm back around to using recs, but the fatpack is fairly hefty - seeing...