<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">One work around for this would be
define a custom option:<br>
<br>
"Dhcp4":<br>
{<br>
:<br>
"option-def": [<br>
{<br>
"name": "newtextstring",<br>
"code": 222,<br>
"type": "string"<br>
} ]<br>
:<br>
:<br>
"subnet4": [{<br>
"subnet": "175.16.1.0/24",<br>
"pools": [ { "pool": "175.16.1.100 - 175.16.1.200" } ],<br>
"option-data": [<br>
{ "name": "newtextstring", "data": "internal server
pool" }<br>
:<br>
]<br>
:<br>
<br>
Maybe not that pretty but you could do it. The option wouldn't
get sent to clients unless they asked for it. The bigger question
is what you want to do with this value?<br>
<br>
Regards,<br>
<br>
Thomas Markwalder<br>
ISC Software Engineering<br>
<br>
On 8/18/17 9:02 AM, James Sumners wrote:<br>
</div>
<blockquote type="cite"
cite="mid:etPan.5996e573.3fc0b03f.cdcd@clayton.edu">
<meta http-equiv="Context-Type" content="text/html; charset=utf-8">
<div class="bloop_markdown">
<p>That’s definitely a strong argument for a strict parser.
Maybe adding support for a “comment” property would be a good
compromise. The property could be any valued (i.e. string,
object, array, whatever).</p>
<p>With such a property allowed it would be possible to write
completely valid JSON such that editors and can work with it.</p>
</div>
<div class="bloop_original_html">
<div id="bloop_customfont">
<br>
</div>
<br>
<div class="airmail_ext_on"><br>
From: <span>Francis Dupont</span> <a
href="mailto:fdupont@isc.org" moz-do-not-send="true">
<fdupont@isc.org></a><br>
Date: <span>August 18, 2017 at 8:11:00 AM</span><br>
To: <span>James Sumners</span> <a
href="mailto:jamessumners@clayton.edu"
moz-do-not-send="true">
<jamessumners@clayton.edu></a><br>
Cc: <span><a class="moz-txt-link-abbreviated" href="mailto:kea-users@lists.isc.org">kea-users@lists.isc.org</a></span> <a
href="mailto:kea-users@lists.isc.org" moz-do-not-send="true">
<kea-users@lists.isc.org></a>, <span>itay cohen</span>
<a href="mailto:icohen9987@gmail.com" moz-do-not-send="true">
<icohen9987@gmail.com></a><br>
Subject: <span> Re: [Kea-users] free text parameter under each
subnet
<br>
</span></div>
<br>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div>James Sumners writes: <br>
> Unfortunately the parser doesn't ignore unknown
properties. <br>
<br>
=> not unfortunately: it is by design and I am sure
you'd like the <br>
parser to catch a trivial spelling error than to
silently ignore it. <br>
<br>
Regards <br>
<br>
Francis Dupont <a class="moz-txt-link-rfc2396E" href="mailto:fdupont@isc.org"><fdupont@isc.org></a> <br>
<br>
PS: as you expect to add a new subnet property you need
to patch the <br>
parser. Note in pools you have the user-context property
which can be used <br>
for the same goal and can be extended (i.e., post a
request) to subnets <br>
or other syntax elements (only host reservations will be
complex because <br>
of external host databases). <br>
</div>
</div>
</span></blockquote>
</div>
<div class="bloop_markdown">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kea-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>