Reassignment of System Ports to the IESG
draft-kuehlewind-system-ports-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05

Network Working Group                                 M. Kuehlewind, Ed.
Internet-Draft                                             Ericsson GmbH
Intended status: Standards Track                              S. Tanamal
Expires: August 13, 2020                               February 10, 2020

                Reassignment of System Ports to the IESG
                    draft-kuehlewind-system-ports-05

Abstract

   In the IANA Service Name and Transport Protocol Port Number Registry,
   a large number of System Ports are 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, such as 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 the corresponding RFC) but change
   control for the port allocation iis designated to others.  Under
   existing operational procedures, this means the original assignee
   needs to be involved in chnage to the port assignment.  As it is not
   always possible to get in touch with the original assignee,
   particularly because of out-dated contact information, this current
   practice of handling historical allocation of System Ports does not
   scale well on a case-by-case basis.  To address this, this document
   instructs IANA to perform actions with the goal to reassign System
   Ports to the IESG that were assigned to individuals prior to the
   publication of RFC6335, where appropriate.

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 13, 2020.

Kuehlewind & Tanamal     Expires August 13, 2020                [Page 1]
Internet-Draft        Reassignment of System Ports         February 2020

Copyright Notice

   Copyright (c) 2020 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.

1.  Introduction

   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 mainly aims to clarify the change control for protocols
   that are maintained by the IETF; it further also intends an update of
   currently unused or not maintained ports.  For this purpose this
   document instructs IANA to perform accumulative actions with the goal
   to re-assign currently assigned System Ports in the range from 0 to
   1023 to the IESG, where appropriate, which will also help to align