That looks good but I would recommend that the values 0 and 0xFFFF for
ar$hrd and ar$op be listed as Reserved.

Thanks,
Donald
-- 
=============================
 Donald E. Eastlake 3rd   +1-508-634-2066 (home)
 155 Beaver Street
 Milford, MA 01757 USA
 [EMAIL PROTECTED]


On Wed, Oct 22, 2008 at 5:33 AM, Jari Arkko <[EMAIL PROTECTED]> wrote:
> Since I was unable to find existing rules, I have written a proposal for the
> rules:
>
> http://www.ietf.org/internet-drafts/draft-arkko-arp-iana-rules-00.txt
>
> The motivation for writing this draft is two-fold: first, it is useful to
> "clean up" our registries and attempt to ensure that most of them have
> defined allocation procedures. Secondly, I would like the IANA to be able to
> handle allocation requests without having to ask the IESG, as they now do.
> The allocation rules in the draft have been crafted so that the common case
> is FCFS and only if something drastic happens (multiple numbers needed, new
> opcode) there's a requirement to escalate the request to the IETF.
>
> Comments appreciated.
>
> Jari
>
> _______________________________________________
> Int-area mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/int-area
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to