<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="bloop_markdown">
<p>That isn’t really a work around. The issue is that a comment cannot be added in such a fashion that the configuration file is valid JSON from start to finish. The desire is to be able to add a property in any configuration object that is there for the configuration
writer to read, not for the parser to care about.</p>
<p></p>
</div>
<div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<br>
<div id="bloop_sign_1503062393081074944" class="bloop_sign"></div>
<div class="airmail_ext_on" style="color:black"><br>
From: <span style="color:black">Thomas Markwalder</span> <a href="mailto:tmark@isc.org">
<tmark@isc.org></a><br>
Date: <span style="color:black">August 18, 2017 at 9:18:15 AM</span><br>
To: <span style="color:black">kea-users@lists.isc.org</span> <a href="mailto:kea-users@lists.isc.org">
<kea-users@lists.isc.org></a><br>
Subject: <span style="color:black"> Re: [Kea-users] free text parameter under each subnet
<br>
</span></div>
<br>
<blockquote type="cite" class="clean_bq"><span>
<div text="#000000" bgcolor="#FFFFFF">
<div></div>
<div>
<title></title>
<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">
<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">
<div>
<div><span>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>
</span></div>
</div>
</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>
_______________________________________________ <br>
Kea-users mailing list <br>
Kea-users@lists.isc.org <br>
https://lists.isc.org/mailman/listinfo/kea-users <br>
</div>
</div>
</span></blockquote>
</div>
<div class="bloop_markdown">
<p></p>
</div>
</body>
</html>