Internet-Draft Legacy IANA IPv4 Registries May 2026
Vyncke Expires 8 November 2026 [Page]
Workgroup:
int-area
Internet-Draft:
draft-vyncke-intarea-legacy-registries-latest
Published:
Intended Status:
Standards Track
Expires:
Author:
É. Vyncke
Cisco

Updates to Legacy IPv4-related IANA Registries

Abstract

IANA maintains several registries that were created for IPv4 extensions. As the IPv4 core specification is no longer being extended, the associated IANA registries need to be updated to reflect the current practice and reflect that defining such extensions is not recommended.

Discussion Venues

This note is to be removed before publishing as an RFC.

Discussion of this document takes place on the Internet Area Working Group Working Group mailing list (int-area@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/int-area/.

Source for this draft and an issue tracker can be found at https://github.com/evyncke/draft-vyncke-intarea-legacy-registries.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 8 November 2026.

Table of Contents

1. Introduction

Several registries were created for IPv4-related protocol elements [RFC791]. These regisries were created by [RFC1700], which in turn was obsoleted by [RFC3232] which handed these registries to IANA.

As the IPv4 core specification (RFC 791) is no longer being extended (see also [IAB_IPV4]) and that more modern mechanisms are defined to manage names, this document closes some relevant IANA registries and changes the registration procedures of others. See more in Section 1.1.

1.1. Justification

The justifications for the changes to IANA registries listed in Section 4) are as follows:

[DHC_NETWARE]:

Registrations are to be closed as Netware is not extended anymore.

[IP_OPTIONS]:

It is commonly understood that the use of IPv4 option is broken [NOT_AN_OPTION]. As such, the registration for new IPv4 options is closed.

[IP_TTL]: :This registry should not have been created as the IPv4 Time to Live (TTL) (Section 3.1 of [RFC791]) header field can be freely selected by the source node.

[MACHINE_NAMES] and [TERMINAL_TYPES]:

There are no registration procedures for these two registries. Moreover, there were no registrations made to these registries in the last two decades. This document specifies the registration procedure as "First Come First Served" ([RFC8126], Section 4.4).

2. Operational Considerations

As some registries are closed, they cannot be extended but the existing values are still valid, i.e., they are not deprecated and can still be used. These changes do not impact existing operations that use already registered values.

The use of IPv4 options on the public Internet is broken. The changes in this document provides a clear signal that solutions that rely on defining such options are not reliable. More robust alternative means should be explored.

3. Security Considerations

There is no new security considerations introduced by this document except for the registries whose registration policy is changed to "First Come First Served". Concretely, registration is still possible to such registries with the risk of having unusable non-sensible data added to it, but the IANA policy is to apply common sense filtering on the content and amount of registrations.

4. IANA Considerations

This document requests IANA to set the registration procedure to "Registration no longer accepted" with a reference to this document for the following registries:

This document requests IANA to set the registration procedure to "First Come First Served" ([RFC8126], Section 4.4) with a reference to this document for the following registries:

This document also requests IANA to completely remove the "IP Time to Live Parameter" registry under the "Internet Protocol Version 4 (IPv4) Parameters" registry group [IP_TTL]. If not possible, then IANA is requested to replace the existing note with the following note:

5. References

5.1. Normative References

[RFC1122]
Braden, R., Ed., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, DOI 10.17487/RFC1122, , <https://www.rfc-editor.org/rfc/rfc1122>.
[RFC791]
Postel, J., "Internet Protocol", STD 5, RFC 791, DOI 10.17487/RFC0791, , <https://www.rfc-editor.org/rfc/rfc791>.
[RFC8126]
Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, , <https://www.rfc-editor.org/rfc/rfc8126>.

5.2. Informative References

[DHC_NETWARE]
IANA, "NetWare/IP Option Type 63 Sub-Option Codes", <https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml#type-63-sub-options>.
[IAB_IPV4]
"IAB Statement on IPv6", , <https://datatracker.ietf.org/doc/statement-iab-statement-on-ipv6/>.
[IP_OPTIONS]
IANA, "IP Option Numbers", <https://www.iana.org/assignments/ip-parameters/ip-parameters.xhtml#ip-parameters-1>.
[IP_TTL]
IANA, "IP Time to Live Parameter", <https://www.iana.org/assignments/ip-parameters/ip-parameters.xhtml#ip-parameters-2>.
[MACHINE_NAMES]
IANA, "Machine Names", <https://www.iana.org/assignments/machine-names/machine-names.xhtml>.
[NOT_AN_OPTION]
Fonseca, R., Porter, G. M., Katz, R. H., Shenker, S., and I. Stoica, "IP Options are not an option", , <https://www2.eecs.berkeley.edu/Pubs/TechRpts/2005/EECS-2005-24.pdf>.
[RFC1700]
Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, DOI 10.17487/RFC1700, , <https://www.rfc-editor.org/rfc/rfc1700>.
[RFC3232]
Reynolds, J., Ed., "Assigned Numbers: RFC 1700 is Replaced by an On-line Database", RFC 3232, DOI 10.17487/RFC3232, , <https://www.rfc-editor.org/rfc/rfc3232>.
[TERMINAL_TYPES]
IANA, "Terminal Type Names", <https://www.iana.org/assignments/terminal-type-names/terminal-type-names.xhtml>.

Acknowledgments

Thanks to Mohamed Boucadair for the initial idea and deep review. Thanks also to Amanda Baber for the initial list of legacy registries or registries without any specified registration procedures. Other thanks for reviewers: Tommy Jensen.

Author's Address

Éric Vyncke
Cisco
De Kleetlaan, 6A
Diegem
Belgium