Exact Definition of numbers-match bitmask-match and fragmentation-type

[Matt Corallo]

Hmm, actually, I take that back, sorting them would require re-serializing the wire format, which I've thus far entirely 
avoided. I suppose I could drop the whole birdc thing, spin up a BGP daemon and use that, but that's a lot more work. Is 
there an easy way/patch to get birdc to output flowspec rules sorted according to the RFC?

Thanks,
Matt

On 4/6/21 17:52, Matt Corallo wrote:
> Ah, I admit I hadn't read the RFC in enough detail, I was kinda hoping birdc was printing the rules in sorted order (see 
> RFC 5575 5.1.  Order of Traffic Filtering Rules), but looks like I'll need to sort them myself.
> 
> Matt
> 
> On 4/6/21 17:41, Ondrej Zajicek wrote:
>> On Tue, Apr 06, 2021 at 04:55:16PM -0400, Matt Corallo wrote:
>>> Ah, indeed, I have not upgraded.
>>>
>>> One more (hopefully last) question - it does seem that the order of the
>>> flowspec rules isn't 100% consistent on the far side of a BIRD<->BIRD BGP
>>> connection. Is that a known bug or reason for that, or should I try to dig
>>> more into why that might be?
>>
>> Not sure what 'order of flowspec rules' you mean. BGP just propagates a
>> set of routes (or flowspec rules) to sync tables on both sides. No order
>> is defined or preserved, as far as BGP is concerned.
>>