<div dir="ltr"><div>The historic artifacts are already available, there are early series of RFCs that are essentially published snapshots of the "notebook". The first series is titled "Assigned Numbers", and up to RFC960 it includes IP address assignments, as well as many other protocol assignments. Then later the series "Internet Numbers", up to RFC 1166, splits out the IP address assignments from the other protocol assignments after RFC960.</div><div><br></div><div>These should be useful to help satisfy your number nerdiness, or the need to perform early Internet number archaeology. </div><div><br></div><div>Thanks</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 16, 2021 at 8:42 PM Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br></div><div dir="auto">Makes me want to say ‘let’s see the book’. It is an historic artifact that should be scanned and posted somewhere for reference. </div><div dir="auto"><br></div><div dir="auto"><br></div><div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 15, 2021 at 8:08 PM Mark Andrews <<a href="mailto:marka@isc.org" target="_blank">marka@isc.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I got my first 4 blocks (1 class B, and 3 class C blocks (pre-CIDR) in 4 different sites in 4 cities in 4 states) of addresses in ’88 (I know the year because my NIC handle was MA88 and I had noted that both where 88, a coincidence but just the same memorable). Even then there where formal procedures. The organisation was noted in whois. You where expected to keep those records up to date. Yes, I know Jon did allocate some addresses less formally but most of the pre-ARIN allocations where formally recorded.<br>
<br>
Mark<br>
<br>
> On 16 Sep 2021, at 03:59, Martin Hannigan <<a href="mailto:hannigan@gmail.com" target="_blank">hannigan@gmail.com</a>> wrote:<br>
> <br>
> <br>
> Hi Paul,<br>
> <br>
> It was interesting reading about your problem, your take on matters, the experience and history with ARIN. Thank you for that.<br>
> <br>
> While I can appreciate ARIN's position from the perspective of 'how do they know', I can appreciate yours too. We're not talking about criminal courts and beyond reasonable doubts. Jon Postel's pre RIR legacy assignments are hand written in a notebook. If that's good enough documentation to establish legacy assignment then providing "reasonable" proof that an address was provided for legitimate use would make a lot of sense to me. However, and admittedly, it's not that simple. Mostly because we don't want it to be. To some extent, because it can't be. You are a victim of "progress".<br>
> <br>
> Warm regards, and good luck;<br>
> <br>
> -M<<br>
> <br>
> <br>
> <br>
> On Wed, Sep 15, 2021 at 1:05 PM Paul E McNary via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<br>
> I need to make a slight correction.<br>
> I am semi retired from our Internet company and my son runs the show.<br>
> He is a triple major Engineer and is PE certifiable in each of the 3 areas.<br>
> He says he has deployed IPv6 to subscribers.<br>
> But Simple and Cheap NO.<br>
> 5 years and a complete forklift to all subscribers.<br>
> The issues happens at the head end router.<br>
> My son is an University educated Enginner.<br>
> His under graduate work was in Network Engineering.<br>
> He was offered a bypass of Master's Degree and go straight into PHD Network Engineering<br>
> Graduated Summa Cum Laude, so he's not an Idiot<br>
> Well maybe he is. He choose our WISP over the PHD.<br>
> He says IPv6 does work for the last mile but on our redundant backhaul loops it has some shortcomings.<br>
> And our multi-homing has some issues with IPv6.<br>
> <br>
> Thought I would make these corrections.<br>
> Just an old, fat, grumpy guy and former Guru that has outlived his usefulness<br>
> Paul McNary<br>
> <br>
> ----- Original Message -----<br>
> From: "arin-ppml" <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
> To: <a href="mailto:scott@solarnetone.org" target="_blank">scott@solarnetone.org</a><br>
> Cc: "arin-ppml" <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
> Sent: Wednesday, September 15, 2021 11:44:09 AM<br>
> Subject: Re: [arin-ppml] Change of Use and ARIN (was: Re: AFRINIC And The Stability Of The Internet Number Registry System)<br>
> <br>
> > On Sep 14, 2021, at 22:50 , <a href="mailto:scott@solarnetone.org" target="_blank">scott@solarnetone.org</a> wrote:<br>
> > <br>
> > <br>
> > <br>
> > On Tue, 14 Sep 2021, Owen DeLong wrote:<br>
> > <br>
> >> <br>
> >> <br>
> >>> On Sep 14, 2021, at 22:42 , <a href="mailto:scott@solarnetone.org" target="_blank">scott@solarnetone.org</a> wrote:<br>
> >>> <br>
> >>>> Nobody I know has found a way to do lossless packing of 128 bits into a 32 bit field yet. Until you can achieve that, compatibility is rather limited.<br>
> >>>> <br>
> >>>> Please present your solution here.<br>
> >>> <br>
> >>> Encode it in four sequential packets, 32 bits per, and add logic to parse those malformed addresses in the routing daemons.<br>
> >> <br>
> >> Either I’m missing something, or that’s not going to be functional when those 4 packets reach the IPv4-Only end host and it has to reply.<br>
> > <br>
> > Maybe, but that is not the challenge you presented:)<br>
> <br>
> Fair enough… In context, the challenge I presented was about getting an IPv4-only host with no changes to software to be able to engage<br>
> in bidirectional communication with remote hosts that live in a 128 bit address space. Yes, you are correct the the way I abbreviated my<br>
> expression of that particular challenge was not complete in itself without the additional context.<br>
> <br>
> > Seriously, some manner of stateful 6/4 nat or header mangling is going to be required upstream of the legacy device to translate.<br>
> <br>
> Yeah, but because of the way IPv4 has been implemented (protocols that embed addresses, expectations of dealing with rendezvous<br>
> hosts, NAT traversal assumptions, etc.), it turns out that evenstateful 6/4 NAT is unnecessarily hard and unreliable at best.<br>
> <br>
> Owen<br>
> <br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to<br>
> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to<br>
> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
> _______________________________________________<br>
> ARIN-PPML<br>
> You are receiving this message because you are subscribed to<br>
> the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
> Unsubscribe or manage your mailing list subscription at:<br>
> <a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
> Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
<br>
-- <br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: +61 2 9871 4742 INTERNET: <a href="mailto:marka@isc.org" target="_blank">marka@isc.org</a><br>
<br>
</blockquote></div></div>
_______________________________________________<br>
ARIN-PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>