Hi! Adrian mentioned this in a separate message…just repeating it here to close the loop with everyone.
rfc5575bis allows only one component of a given type to be included in the description of the FlowSpec…which means that there is no need for AND/OR operations between them. There’s no change needed in rfc5575bis…but this document needs to be cleaned up to remove the ability of multiple components of the same type. Thanks! Alvaro. On August 26, 2020 at 5:53:54 PM, Benjamin Kaduk ([email protected]) wrote: On Wed, Aug 26, 2020 at 10:48:41PM +0100, Adrian Farrel wrote: > > Responding to just the Discuss portion due to time constraints before the > > telechat... > > Understood > > Top posting: > > This really feels like a problem for 5575bis. I'm beginning to think we > overstepped by even mentioning it in this document. I wanted to draw out the > risks and confusions (almost to say "don't do that") without trampling on > existing practice or messing with BGP. This is (clearly?) not the document > to tell people how to manage their BGP FlowSpecs, yet we wanted to inherit > as much as possible from BGP, yet we don't want people to damage themselves, > yet the scissors are sharp and they enjoy running. > > You paragraph of suggestions of pointers of how/when to do AND and OR is a > reasonable starting point. But surely it is something that belongs in > 5575bis? I suspect you are right... Alvaro, what do you think? -Ben
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
