FWIW, there are many registries with such “dead” entries. RFC6335 talks about the issue in trying to recover such entries.
In general, it recommends that even if they are recovered, at best they would be marked as “RESERVED” until other values have been assigned and the space requires reuse of those dead entries. So the net effect is: a) the list will never actually reflect what is deployed (as Bob notes below) b) garbage-collecting will at best mark some subset as dead c) but the available entries won’t be reused until we run out anyway Given the number of remaining entries, the task of garbage collection seems of little value. Joe > On Sep 20, 2019, at 1:31 PM, Bob Hinden <[email protected]> wrote: > > Andy, > >> On Sep 20, 2019, at 10:37 AM, Andrew G. Malis <[email protected]> wrote: >> >> Behcet, >> >> That was a historical list. The current assignments are in >> https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml . >> If you want to go garbage collecting, that's the place to start. > > It's difficult to tell which are no longer used. For example, I was recently > asked about the Reliable Data Protocol, it’s IANA assignment: > > 27 RDP Reliable Data Protocol [RFC908][Bob_Hinden] > > I assumed it was no longer used. Later by happenstance, I learned it is > specified by ETSI as mandatory to implement in eSIMs. I had no idea. > > Bob > > > _______ > internet-history mailing list > [email protected] > http://mailman.postel.org/mailman/listinfo/internet-history > Contact [email protected] for assistance. _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
