My 2 cents > From: Job Snijders > [...] > 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. Good point. I'm wondering if decoupling both would not be cleaner, and would avoid the incentive to "tweak" the AS Path. One option would be to keep the AS Path for loop detection, administrative record, and policies. Inter domain metric used for best path selection could be left for another field/data/extension. Yet given the incentive to tweak such data, we could even realize that since we can't trust it, we don't really need it. We could only let the end user (originator) express some high level policy (nominal, backup1, backup2) using well known communities. (which indeed may also be removed/changed by transit AS, but the end user could see it and negotiate transparency though a contract).
Best regards, --Bruno > > 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
