Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend Policy - What is it? #19

Open
hgn opened this issue Sep 23, 2017 · 2 comments
Open

Extend Policy - What is it? #19

hgn opened this issue Sep 23, 2017 · 2 comments

Comments

@hgn
Copy link
Member

hgn commented Sep 23, 2017

Probably a example or two should be given: highest-bandwidth, highest-bandwidth-no-costs (one with filter)

Policy
A Policy describes an order relation over a set of paths using the
link attributes of these paths. Note that to guarantee loop-free
properties this ordering function MUST be commutative and
associative.

@reisub-de
Copy link
Contributor

I thought of putting this in an Appendix, a ref to the appendix section would be good, though

@hgn
Copy link
Member Author

hgn commented Oct 13, 2017

I think we should define at least one required metric/policy for the standard. This is required to be interested op if a second router vendor will implement dmpr and will communicate with us.

Remember, metric name must not start with underscore for standardized protocol, vendor specific and experimental extension metrics must start with underscore.

So to rephrase my initial wordings: we must define at least one path metric/policy in the ID and give them a unique name.

Right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants