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

Default for interface and PvD is no preference, fixes #435 #498

Merged
merged 1 commit into from Feb 4, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 3 additions & 1 deletion draft-ietf-taps-interface.md
Expand Up @@ -861,7 +861,7 @@ congestion control in accordance with {{?RFC2914}}. Also note that reliability
is usually combined with congestion control in protocol implementations,
rendering "reliable but not congestion controlled" a request that is unlikely to
succeed.
The recommended default is to Require that the Connection is congestion controlled.
The default is to Require that the Connection is congestion controlled.


### Interface Instance or Type {#prop-interface}
Expand Down Expand Up @@ -903,6 +903,7 @@ such as metered or unmetered network access. If an application needs to prohibit
metered interfaces, this should be specified via Provisioning Domain attributes
(see {{prop-pvd}}) or another specific property.

The default is to not set a preference for any interface.

### Provisioning Domain Instance or Type {#prop-pvd}

Expand Down Expand Up @@ -939,6 +940,7 @@ particular instance. While this does restrict path selection, it is broader than
requiring specific PvD instances or interface instances, and should be preferred
over these options.

The default is to not set a preference for any PvD.

### Local Address Preference

Expand Down