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

INT identification after L4 headers #9

Open
jklr opened this issue Jan 4, 2018 · 0 comments
Open

INT identification after L4 headers #9

jklr opened this issue Jan 4, 2018 · 0 comments

Comments

@jklr
Copy link
Contributor

jklr commented Jan 4, 2018

The spec currently suggests two ways to indicate the existence of INT after TCP/UDP/ICMP.

  • DSCP
  • Destination L4 port

Each has certain drawbacks, for example DSCP approach limits the available DSCP code points from 64 to 32. Changing the destination port will change ECMP behavior and complicate ACL.

Another options are

We can discuss pros/cons of the overall approaches in the following meetings and include in the spec.

@jklr jklr closed this as completed Jan 19, 2018
@jklr jklr reopened this Jan 19, 2018
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

1 participant