<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear working group,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 06 May 2015, at 18:14, denis <<a href="mailto:ripedenis@yahoo.co.uk" class="">ripedenis@yahoo.co.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div bgcolor="#FFFFFF" text="#000000" class=""><blockquote cite="mid:499D7D01-B473-46B0-8576-3717D580974D@ripe.net" type="cite" style="font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><div class="">If an object is submitted without any changes it will always result in an update, because when we compare the object the "last-modified:" value will typically not match.(unless the update is done at sub-second speed) In other words what should be a "no-op" now results in a "touch" operation where only the "last-modified:" attribute is changed.</div></blockquote><br style="font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" class=""><span style="font-family: Monaco; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); float: none; display: inline !important;" class="">Just an observation. This might actually be a useful side effect. It allows maintainers of objects to 'touch' their objects and show they are alive and actively maintaining their data even when nothing needs to change. I am sure some people in the community who are going to start monitoring "last-changed:" attributes to argue that data is out of date would appreciate that, or even request it.</span></div></div></blockquote></div><br class=""></div><div class="">Sure, there is something to be said for this, but the downside of this is that the version history of the object becomes very large, which may not be desired.</div><div class=""><br class=""></div><div class="">As far as I know this was not explicitly specified beforehand, so it would be good to have a clear WG consensus call on this now.</div><div class=""><br class=""></div><div class="">For the moment we feel that it's probably best to apply the planned 'fix' because the behaviour will then be consistent with no-ops until now, but we can always revert this change when we get a clear direction from the WG.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class=""><br class=""></div><div class="">Tim Bruijnzeels</div><div class=""><br class=""></div><div class="">Assistant Manager Software Engineering</div><div class="">RIPE NCC</div></body></html>