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

Policies are really Configurations #15

Closed
britram opened this Issue Sep 7, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@britram
Contributor

britram commented Sep 7, 2017

No description provided.

@britram britram added the question label Sep 7, 2017

@mirjak

This comment has been minimized.

Show comment
Hide comment
@mirjak

mirjak Sep 7, 2017

Contributor

No idea...

Contributor

mirjak commented Sep 7, 2017

No idea...

@tfpauly

This comment has been minimized.

Show comment
Hide comment
@tfpauly

tfpauly Sep 7, 2017

Contributor

Great question!

I think we've been using Parameters and Policy Context fairly interchangeably. Based on the definition in the draft, the Policy Content is essentially the parameters that influence the policy of what you end up using for your path, and what protocols you use. The broader term "Parameters" may include other bits that don't as naturally fit underneath Policy Context; the draft now mentions things like the certificates being parameters to create an association with, etc. Essentially any protocol-specific tuning parameters aren't as clearly part of the "policy", since the policy engine may not care about these parameters; but they are likely set at the same time as the other bits of Policy Context.

Contributor

tfpauly commented Sep 7, 2017

Great question!

I think we've been using Parameters and Policy Context fairly interchangeably. Based on the definition in the draft, the Policy Content is essentially the parameters that influence the policy of what you end up using for your path, and what protocols you use. The broader term "Parameters" may include other bits that don't as naturally fit underneath Policy Context; the draft now mentions things like the certificates being parameters to create an association with, etc. Essentially any protocol-specific tuning parameters aren't as clearly part of the "policy", since the policy engine may not care about these parameters; but they are likely set at the same time as the other bits of Policy Context.

@britram

This comment has been minimized.

Show comment
Hide comment
@britram

britram Sep 7, 2017

Contributor
Contributor

britram commented Sep 7, 2017

@chris-wood

This comment has been minimized.

Show comment
Hide comment
@chris-wood

chris-wood Sep 7, 2017

Contributor

s/Parameters/Configuration!

Contributor

chris-wood commented Sep 7, 2017

s/Parameters/Configuration!

@chris-wood chris-wood self-assigned this Sep 7, 2017

@britram britram changed the title from What's the difference between Parameters and a non-global PolicyContext? to Policies are really Configurations Sep 7, 2017

@britram britram added this to the IETF 100 Singapore milestone Oct 12, 2017

@tfpauly

This comment has been minimized.

Show comment
Hide comment
@tfpauly

tfpauly Oct 18, 2017

Contributor

Opened PR #23

Contributor

tfpauly commented Oct 18, 2017

Opened PR #23

@tfpauly tfpauly closed this Oct 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment