Reassignment of System Ports to the IESG
Active Internet-Draft (individual)
||Intended RFC status
Submitted to IESG for Publication
No shepherd assigned
Publication Requested::AD Followup
||Send notices to
Network Working Group M. Kuehlewind, Ed.
Internet-Draft ETH Zurich
Intended status: Standards Track S. Tanamal
Expires: August 5, 2019 February 1, 2019
Reassignment of System Ports to the IESG
In the IANA Service Name and Transport Protocol Port Number Registry,
a large number of System Ports is currently assigned to individuals
or companies who have registered the port for the use with a certain
protocol before RFC6335 was published. For some of these ports, RFCs
exist that describe the respective protocol; for others, RFCs are
under development that define, re-define, or assign the protocol used
for the respective port, e.g. in case of so-far unused UDP ports that
have been registered together with the respective TCP port. In these
cases the IESG has the change control about the protocol used on the
port (as described in an RFC) but does not have the change control
about the port usage itself. Currently, to transfer the change
control to the IESG, the original assignee has to be contacted to
initialize this transfer. As it is not always possible to get in
touch with the original assignee, e.g. because of out-dated contact
information or other reasons, and the current practice of case-by-
case changes does not scale well, this document instructs IANA to
perform actions with the goal to reassigns all System Ports to the
IESG that have been assigned to individuals prior to the publication
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 August 5, 2019.
Kuehlewind & Tanamal Expires August 5, 2019 [Page 1]
Internet-Draft Reassignment of System Ports February 2019
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
RFC 6335 [RFC6335] requires System Ports, also known as the Well
Known Ports, in the range from 0 to 1023, to be assigned by the "IETF
Review" or "IESG Approval" procedures [RFC8126]. For assignments
done through RFCs published via the "IETF Document Stream" [RFC4844],
the Assignee will be the IESG with the IETF Chair as the Contact.
However, ports that were assigned before the publication of RFC 6335,
are often assigned to individuals, even if they are part of the
System Port range and have a corresponding RFC. Besides the fact
that System Ports are widely used by IETF protocols where the
protocol specification is under IETF change control as defined in an
RFC but the port itself may not, this situation is especially
problematic if the assignment gets or needs to be changed. The
Assignee can change the assignment without confirmation of the IETF.
However, if the IETF process requires a change, including de-
assignment, this cannot be done without the agreement of the original
Assignee. Furthermore, no procedure is defined to change the
assignment in cases where the original Assignee is not reachable or
not available anymore.
This document instructs IANA to perform actions with the goal to re-
assign all currently assigned System Ports in the range from 0 to
1023 to the IESG, which will also help to align existing entries in
the "Service Name and Transport Protocol Port Number Registry" with
the current procedures defined in RFC 6335.
2. IANA Considerations
IANA [will perform/has performed] action to re-assign all System
Ports in the port range from 0 to 1023 that are currently assigned in
the "Service Name and Transport Protocol Port Number Registry"
Show full document text