NFD

This problem is identified on 20170719 because ASF is not working well with NDN-RTC.
In NDN-RTC, each video frame is encoded as a variable number of data segments. The consumer may send more Interests than available segments, and the producer (incorrectly) does not use application-generated Nack but leaves the Interests to timeout.

20170719 NFD call discussed several ways to count timeouts:

• An absolute number of consecutive timeouts.
• A percentage of recent Interests (but it's unclear what does the percentage count against).
• Multiple timeouts within a round-trip time can count as one timeout event.
• The switching of paths should be gradual. For example, the Interest right after a timeout can be sent to two paths.

4480,15 gives the following strategy name syntax: /localhost/nfd/strategy/asf/%FD%02/probing-interval/30000/n-silent-timeouts/5.
There are two wasted components. It's better to use a more compact format: /localhost/nfd/strategy/asf/%FD%02/probing-interval%3D30000%20n-silent-timeouts%3D5.

Junxiao Shi wrote:

I'd suggest a small bash or Python script to construct the strategy name, so that the above commands can be invoked like:

I very much disagree with this.

The script can accept both long form (as shown above) and short form (eg -p30000 -s5) flags, if desired.

The strategy itself can do the same. Or better, nfdc should natively include this functionality. But I don't see it as particularly urgent.

Strategy parameters can use a more compact form, without worrying about human readability which shouldn't be a concern in the first place

Why is compactness a concern while human readability isn't? I'd say the opposite is true.

In any case, it seems like this discussion will become mostly irrelevant once we have typed name components. So let's just implement something "good enough" for the time being.

Why is compactness a concern while human readability isn't? I'd say the opposite is true.

In any case, it seems like this discussion will become mostly irrelevant once we have typed name components. So let's just implement something "good enough" for the time being.

Fine. ASF may define any syntax they want as long as URIs are valid.

Since you choose to use ~ as delimiter, this issue is now blocked by #4484. You may clear this block relation by using a different unaffected delimiter.

Junxiao Shi wrote:

Since you choose to use ~ as delimiter, this issue is now blocked by #4484.

No it's not. Unreserved characters should not be encoded, but it's not illegal to do so, i.e. a fully encoded URI would still be valid. Therefore, decoding percent-encoded characters in the unreserved set can always be done and doesn't change the interpretation of the URI.

One change has been merged. What's left to do here?

I think we would like to explore other suggestions in note-1 to make ASF less sensitive. Maybe it should be another issue?

Ashlesh Gawande wrote:

I think we would like to explore other suggestions in note-1 to make ASF less sensitive. Maybe it should be another issue?

I was asking based on the issue description, which seems to have been fulfilled. I have no preference. If you intend to do more work under this issue, please update the description to clearly state what has been done and what hasn't.