<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">g'day, mate. it's 1030pm
here, so likely broad daylight down under.<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:CAA=nHS+CjBxeRjNvddHy=S-n-_xcwfjGV_b_6RdKLYRX51tQrw@mail.gmail.com"
type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="ggm@apnic.net" photoname="George Michaelson"
src="cid:part1.08070109.08010003@redbarn.org"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:ggm@apnic.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">George Michaelson</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">Monday, December
01, 2014 10:18 PM</span></font></div></div></div>
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div
dir="ltr">I think the use of *must* here is non-normative. You make a
strong case that a canonicalization must understand dynamic update. But
you also chose to ignore a huge world of context where people are
presented with zones as a fait accompli. Not as participants in port 53,
but as files. <br>
</div></div>
</blockquote>
<br>
i'm sorry, friend, i didn't mean to leave those out. zones held in files
which only change when the file is edited or regenerated are a special
case of update, as in "zero updates". although BIND9 has a delicious
"ixfr-from-differences" feature that can turn successive versions of a
"primary zone file" into a stream of IXFR's, that's just gravy in this
case. for your proposed use case, where the receiving end transfers a
"zone file" and then runs posix tools to canonicalize it, extract its
hash, and compare that hash to the hash of the canonicalized (by the
way, spell check says i mean "cannibalized" and i'm not sure it's wrong)
zone zone, would be entirely possible. i regret that i did not say so
before.<br>
<blockquote style="border: 0px none;"
cite="mid:CAA=nHS+CjBxeRjNvddHy=S-n-_xcwfjGV_b_6RdKLYRX51tQrw@mail.gmail.com"
type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div dir="ltr"><div><br></div><div>I think we're silly to exclude
mechanisms which are understandable by anyone, over what are (for much
of their life) represented as files. <br>
</div></div>
</div>
</blockquote>
<br>
yes, we would be, and so i'm not. as it were.<br>
<blockquote style="border: 0px none;"
cite="mid:CAA=nHS+CjBxeRjNvddHy=S-n-_xcwfjGV_b_6RdKLYRX51tQrw@mail.gmail.com"
type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div dir="ltr"><div><br></div><div>There is a tool in bind which
reads a .jnl. So, if I take the outcome of a dynamic update, secure it
in a transactionally complete .jnl, and then apply the tool.. I have a
file of a zone state, and a given point in time, for a given serial.</div><div><br></div><div>At
which point, I can canonicalize it, and apply checks against a
published statement of the zones integrity.</div></div>
</div>
</blockquote>
<br>
yes, and yes.<br>
<br>
vixie<br>
</body></html>