content so long as it does not also use an element labled "ISC". In other
words, user-context is intended to be a flexible container serving mulitple
purposes. As long as no other purpose also writes an "ISC" element to
- user-contex there should not be a conflict.
+ user-context there should not be a conflict.
.. _host-reservation-v4:
any other user-context content so long as it does not also use an element
labled "ISC". In other words, user-context is intended to be a flexible
container serving mulitple purposes. As long as no other purpose also
- writes an "ISC" element to user-contex there should not be a conflict.
+ writes an "ISC" element to user-context there should not be a conflict.
.. _host-reservation-v6:
if (!t2_percent_.unspecified()) {
map->set("t2-percent", Element::create(t2_percent_));
}
-if (!ddns_send_updates_.unspecified()) {
+
+ if (!ddns_send_updates_.unspecified()) {
map->set("ddns-send-updates", Element::create(ddns_send_updates_));
}
/// The parsed parameters are:
/// - renew-timer,
/// - rebind-timer,
- /// - valid-lifetime
+ /// - valid-lifetime,
/// - store-extended-info
///
/// @param network_data Data element holding shared network