<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>Just to confirm Leo's observation.</p>
<p>For each RIPE document, you can find on our website in the
metadata on the righthand side in chronological order which
previous versions were updated by that version. <br>
If the document was obsoleted by another document, the metadata
will also show that. In addition, the document itself will show
"This document is obsoleted by ripe-xxx".<br>
See for example:<br>
<a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-708">https://www.ripe.net/publications/docs/ripe-708</a><br>
<br>
In the related pdf-version you can find the information which RIPE
document has been obsoleted by that document:<br>
<a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs/ripe-708/at_download/pdf">https://www.ripe.net/publications/docs/ripe-708/at_download/pdf</a></p>
<p>If you would find in any RIPE document some information missing,
please let me know in a direct message and I will follow up.<br>
</p>
<p>The RIPE Policy page has a chronological order. Other order
mechanism are available in the document store, for example to see
all IPv6 related documents.<br>
<a class="moz-txt-link-freetext" href="https://www.ripe.net/publications/docs">https://www.ripe.net/publications/docs</a></p>
<p>I hope this clarifies.</p>
<p>Kind regards,<br>
Marco Schmidt<br>
Policy Officer<br>
RIPE NCC<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 16/07/2019 21:45, Leo Vegoda wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B39A5833-E553-4819-B145-0B1FAC4F5E94@icann.org">
<pre wrap="">On 7/16/19, 11:02 AM, "Owen DeLong" <a class="moz-txt-link-rfc2396E" href="mailto:owen@delong.com"><owen@delong.com></a> wrote:
[...]
</pre>
<blockquote type="cite">
<pre wrap=""> Leo, Open many RIPE-NNN documents which are old. You will not find anything in it stating “Obsoleted by RIPE-XXX”.
Open similar RIPE-XXX document which obsoletes RIPE-NNN. You will not find anything in it stating “Obsoletes RIPE-NNN”.
I’m happy you were able to find an example where that works, but there are many examples where it doesn’t.
</pre>
</blockquote>
<pre wrap="">I have been looking through a selection of newer and older documents and haven't yet found one without a meticulous history in the metadata panel on the righthand side of the page. There might well be the occasional omission, although I haven't seen any. If you have found some, letting the RIPE NCC staff know so that they can fix them is the right thing to do. Just asserting that there are many examples where there isn't a history is unhelpful.
Kind regards,
Leo Vegoda
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<br>
</body>
</html>