44/8

[beecher at beecher.cc (Tom Beecher)]

So wall of text, but here is the RFC chain.

Hank Magnuski was the original person marked as the 'reference', which is
interpreted as 'responsible individual' in these documents.  This changed
in 1987, when Philip R. Karn was now reflected in that field.

The last RFC I can find that explicitly calls out 44.0.0.0/8 was 1166 ,
July 1990, again with Phil Karn as the reference, or responsible
individual.


==========

Original assignment of 44 in RFC 790 : Sept 1981

https://tools.ietf.org/html/rfc790

...
044.rrr.rrr.rrr   AMPRNET       Amature Radio Experiment Net  [HM]
044.rrr.rrr.rrr-126.rrr.rrr.rrr Unassigned                   [JBP]
...

[HM]      Hank Magnuski       ---       JOSE at PARC-MAXC

==========

Ambiguity corrected in RFC 820:

https://tools.ietf.org/html/rfc820

...
R 044.rrr.rrr.rrr   AMPRNET       Amateur Radio Experiment Net[HM]
R 045.rrr.rrr.rrr T C3-PR         Testbed Development PRNET  [BG5]
...

[HM]      Hank Magnuski       ---       JOSE at PARC-MAXC

==========

Maintains references to "Amateur Radio Experiment Net" through multiple
RFCs:

870
900
923
943
960
990
997

==========

Reference field changes from [HM] to [PK28] in RFC 1020 : Nov 1987
https://tools.ietf.org/html/rfc1020

[PK28]    Philip R. Karn, Jr. BCR       Karn at FLASH.BELLCORE.COM

==========

"Amateur Radio Experiment Net" disappears, only AMPRNET listed in RFC 1166 :

https://tools.ietf.org/html/rfc1166

...
R*43.rrr.rrr.rrr                     JAPAN-A           [JM292]
R 44.rrr.rrr.rrr                     AMPRNET           [PK28]
 45.rrr.rrr.rrr                     Reserved          [NIC]
...

==========

RFC 1166 Updated by RFC 5737, creation of documentation blocks. No
references to 44/8.

https://tools.ietf.org/html/rfc5737

==========



On Mon, Jul 22, 2019 at 3:49 PM John Curran <jcurran at arin.net> wrote:

> On 22 Jul 2019, at 3:35 PM, William Herrin <bill at herrin.us> wrote:
>
>
> On Mon, Jul 22, 2019 at 12:24 PM John Curran <jcurran at arin.net> wrote:
>
>> > Nothing in the publicly vetted policies demanded that you attach
>> organizations to the purpose-based allocations
>>
>> Youâ??ve suggested that this network was some special â??purpose-basedâ??
>> allocation, but failed to point to any actual policy guidance that
>> distinguishes it in that manner.
>
>
> John,
>
> As admitted at https://www.ampr.org/amprnet/, Hank Magnuski and Jon
> Postel thought it was a swell idea and simply did it.
>
>
> Bill -
>
> In which case, Iâ??d recommend contacting Hank Magnuski to obtain
> documentation of your particular interpretation, as there are no published
> policy documents which indicate anything other than an allocation from the
> general purpose IPv4 space for an "amateur packet radio" research network
> (and in particular nothing that would indicate that stewardship over the
> allocation should rest with any party other than the assigned contact for
> the block.)
>
> Thanks!
> /John
>
> John Curran
> President and CEO
> American Registry for Internet Numbers
>
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190722/b7773d07/attachment.html>