Clarify sla 0.

diff --git a/dhcpcd.conf.5.in b/dhcpcd.conf.5.in
index a4bb7f47afbd1c50b24474d78bbcb4e1289a5dda..1a3c676db6b2dcaa1c35627d55ede01db43e4534 100644 (file)
--- a/dhcpcd.conf.5.in
+++ b/dhcpcd.conf.5.in
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd March 30, 2016
+.Dd April 16, 2016
 .Dt DHCPCD.CONF 5
 .Os
 .Sh NAME
@@ -302,10 +302,9 @@ This option must be used in an
 block.
 Unless a
 .Ar sla_id
-of 0 is assigned, a reject route is installed for the Delegated Prefix to
+of 0 is assigned with the same resultant prefix length as the delegation,
+a reject route is installed for the Delegated Prefix to
 stop unallocated addresses being resolved upstream.
-This reject route is in essence SLA 0, thus you need space within the prefix
-to assign a SLA per interface.
 If no
 .Ar interface
 is given then we will assign a prefix to every other interface with a
@@ -340,7 +339,10 @@ is increased to the highest multiple of 8 that can accommodate the
 is an integer and is added to the prefix which must fit inside
 .Ar prefix_len
 less the length of the delegated prefix.
-.Ar sla_id can be 0 only if the Delegated Prefix is assigned to one interface.
+.Ar sla_id
+can be 0 only if the Delegated Prefix is assigned to one interface.
+This violates RFC3633 12.1 and should only be used if the Delegated Prefix
+length is 64 and you need to delegate it to a downstream interface.
 You can specify multiple
 .Ar interface /
 .Ar sla_id /