make leftmost child default for ChildSelector if field not present
Change-Id: I4ae92c31a39bc70606a3cbfc1d904a8b39f23d8e
diff --git a/changelog.rst b/changelog.rst
index 1f5dd27..871d7d1 100644
--- a/changelog.rst
+++ b/changelog.rst
@@ -9,6 +9,7 @@
- **Interest**
+ Add specification of Link and SelectedDelegation fields
+ + Add default of leftmost child if ChildSelector field not present
- **Data**
diff --git a/interest.rst b/interest.rst
index fa5de11..70271e3 100644
--- a/interest.rst
+++ b/interest.rst
@@ -122,6 +122,7 @@
If 1, the rightmost child is preferred.
Here leftmost and rightmost refer to the least and greatest components according to the canonical NDN name component ordering (:ref:`Name Section<name>`).
This ordering is only done at the level of the name hierarchy one past the name prefix.
+If the ``ChildSelector`` field is not present, the leftmost child is preferred (a value of 0).
For example, assuming in the name hierarchy the component immediately after the name prefix is the version number, whose next level is the segment number, then setting ChildSelector to be 1 will retrieve the rightmost version number (i.e., the latest version) and the leftmost segment number (i.e., the first segment). However, this selection is only done with respect to a single content store, not globally. Additional rounds that exclude the earlier versions may be used to explore other content stores for newer versions.
In this case, the use of ChildSelector does not change the multi-round outcome, but it decreases the number of rounds needed to converge to an answer.