<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>The transcript of the RIPE NCC Services WG session at RIPE 64 (<a href="https://ripe64.ripe.net/archives/steno/16/">https://ripe64.ripe.net/archives/steno/16/</a>) records the following exchange:</div><div><br></div><blockquote type="cite">AUDIENCE SPEAKER: Nigel Titley, Chairman of the board of the RIPE NCC. Just a very quick note. The charging scheme task force has delivered its report. The board is due to consider that report starting in June of this year. Could I urge you to at least give us some idea of what your policy might say fairly early on so that we can consider that? <br><br>NIALL O'REILLY: Noted.</blockquote><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>The group of us working on drafting a policy proposal have identified most<div><span class="Apple-tab-span" style="white-space:pre"> </span>of the key elements which will be included, but a presentable proposal </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>won't be ready without some more work. In order not to miss the </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>opportunity which Nigel kindly took care to point out, here is "some idea</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>of what [the] policy [proposal] might say".<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I expect that the main elements of the forthcoming policy proposal will</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>include the following.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Current inaccuracies in the RIPE database should be corrected without</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>additional formality, and specifically without forcing a contractual</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>relationship.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Each legacy resource holder should have the choice of registering holdings</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>either directly as a "small" member or indirectly as a customer of a</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>sponsoring LIR. We understand that this matches current NCC thinking.</div><div><br></div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>Clarity is needed as to which RIR policies will apply to legacy resources.<br><span class="Apple-tab-span" style="white-space: pre; "> </span>It is not sufficient to declare these resources subject to "all" policies,<br><span class="Apple-tab-span" style="white-space: pre; "> </span>as the RIR may not have authority to apply certain policies in respect of<br><span class="Apple-tab-span" style="white-space: pre; "> </span>legacy resources. It will be necessary to itemize which policies are </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>applicable.<br></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Whenever an "obvious" potential sponsoring LIR can be identified, the NCC</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>should request this LIR to make contact with the resource holder rather</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>than do so directly. Such cases might be identified either from existing</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>RIPE DB records or from current routing information. There is specific</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>concern in the NREN community that NCC members' relationships with their</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>customers be respected in this way.</div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span></div></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We gave more detailed attention to the question of charging, as we</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>understand that this is a current priority of the RIPE NCC Board.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We are aware of two current documents relating to charging: one, the report</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>of the Charging Scheme Task Force (CSTF); the other, a limited-circulation</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>document co-authored by a group for which Daniel Karrenberg has been acting </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>as editor. The latter document may perhaps be most conveniently described</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>as a memorandum for the Board, giving an example of how the recommendations</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>of the CSTF might concretely be implemented.</div><div><br></div><div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>We welcome the specific attention given in this "Karrenberg document" to </div><div><span class="Apple-tab-span" style="white-space: pre; "> </span>the situation of legacy resource holders, and particularly the idea of</div></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>encouraging engagement of legacy resource holders by waiving the sign-up</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>fee.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We also appreciate the suggestion made at the TERENA conference in</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Reykjav�k recently by Mirjam K�hne, representing the RIPE NCC, that </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>fees would not be charged in respect of legacy resources. Some</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>clarification as to the conditions attached to this offer, including</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>an indication of how long it will continue, would be helpful.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Although it is certain to be superseded, we have used RIPE-499, which </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>documents the 2011 charging scheme, as the starting point for indicating</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>how we feel that legacy resources should be assessed in case a resource</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>accounting assessment model is to be used in the new charging scheme.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We propose that legacy address blocks are assessed with a score of</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>one eighth of the score assessed for a PA block of equal size.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We also suggest a modification to the "Karrenberg document" so that</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>a sponsoring LIR will not be inhibited from accommodating legacy</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>resource holders by concern over a possible change of charging band.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Attached are modified versions of Appendix 1 of RIPE-499 and of</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Appendix F of the "Karrenberg document" which make these suggestions</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>explicit.</div><div><br></div></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Best regards,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Niall O'Reilly</div><div><br></div><div></div></body></html>