On Mon, Dec 18, 2017 at 03:32:13PM +0000, Nick Hilliard wrote: > Job Snijders wrote: > > I mentioned before, I suspect that the route server's lack of > > visiblity is a direct contributor to the reluctance to apply filters > > on route servers. > > Job, seriously, if you have helpful or useful comments to make, then > please make them.
You are free to disagree with my suspicions, but please ensure you maintain a degree of decorum when doing so. I've perceive advantages to transparency in many areas of business. (well, in this context 'transparency' should be interpreted as 'explicit visibility'). Oftentimes immediate improvement can be noticed when a business operation is ranked against similar business, and reports are published on performance indicators. This of course requires the business to be visible in the first place. The AS_PATH attribute serves multiple functions: its length is used as a tie-breaker in best path selection, and the contents of the AS_PATH itself serves as an (mutable) track record on what administrative domains the announcement passed through. You and Martijn appear to argue that the 'best path selection' component should not be fiddled with, which leaves me wondering whether we have any other methods to implement a track record ala 'this path announcement passed through RS AS XYZ' other than communities. Or are you of the opinion that the lack of visibility is not a problem to begin with? Respectfully, Job _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
