<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="">
<div class="">Thanks for your feedback, Brian.</div>
<div class=""><br class="">
</div>
<div class="">Andy Newton,</div>
<div class="">Chief Engineer, ARIN</div>
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On Jun 29, 2015, at 9:54 AM, Brian Rak <<a href="mailto:brak@gameservers.com" class="">brak@gameservers.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">Well, I can tell you that the "Find Networks Method" would not be terribly helpful for us.<br class="">
<br class="">
Our process for keeping SWIP up to date looks something like this:<br class="">
<br class="">
1) Obtain reassignment report<br class="">
2) Obtain our internal list of what subnets we have active<br class="">
3) For each item in the reassignment report, see if we have an active subnet. If the information no longer matches, delete the SWIP entry. If we don't have a subnet, delete the SWIP entry.<br class="">
4) For each subnet in our internal list, see if a SWIP entry exists (by checking the data returned by the reassignment report). If not, issue a create<br class="">
<br class="">
The proposed "Find Networks Method" only seems like it would help for error checking in step 4 (allowing us to verify the reassignment we're attempting doesn't conflict)<br class="">
<br class="">
"Update Network Registrations Method" looks like it would be far more helpful to us. It seems like the intent here is to allow us to just upload a big request with all of our registration data (and not have to worry about what's already there). That definitely
would eliminate a lot of the pain we have with the whole SWIP process.<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">On 6/15/2015 3:50 PM, Andy Newton wrote:<br class="">
</div>
<blockquote cite="mid:C4799573-1397-4CE8-BBA2-8DE5FDCEDA12@arin.net" type="cite" class="">
<pre wrap="" class="">All,
Some months back there were discussions on this mailing list regarding the difficulty of using Reg-RWS. Here is what I wrote at the time:
"So that we can address these issues, here is what I propose. I will create specification document outlining new methods and payloads for Reg-RWS, and I will send it to this list for discussion and to get your collective input. Once we have a document we agree will address these issues, it can be put forward as a request for ARIN implementation.”
I am attaching a document that is the proposal as mentioned above. Your feedback on it would be greatly appreciated. And please note that this is just a proposal and not a commitment to change Reg-RWS.
Thanks for you time and patience.
Andy Newton,
Chief Engineer, ARIN
</pre>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset> <br class="">
<pre wrap="" class="">_______________________________________________
arin-tech-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:arin-tech-discuss@arin.net">arin-tech-discuss@arin.net</a>
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-tech-discuss">http://lists.arin.net/mailman/listinfo/arin-tech-discuss</a>
</pre>
</blockquote>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>