idnits 2.17.1 draft-kuehlewind-system-ports-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 10, 2020) is 1509 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 4844 (Obsoleted by RFC 8729) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Kuehlewind, Ed. 3 Internet-Draft Ericsson GmbH 4 Intended status: Standards Track S. Tanamal 5 Expires: August 13, 2020 February 10, 2020 7 Reassignment of System Ports to the IESG 8 draft-kuehlewind-system-ports-05 10 Abstract 12 In the IANA Service Name and Transport Protocol Port Number Registry, 13 a large number of System Ports are currently assigned to individuals 14 or companies who have registered the port for the use with a certain 15 protocol before RFC6335 was published. For some of these ports, RFCs 16 exist that describe the respective protocol; for others, RFCs are 17 under development that define, re-define, or assign the protocol used 18 for the respective port, such as in case of so-far unused UDP ports 19 that have been registered together with the respective TCP port. In 20 these cases the IESG has the change control about the protocol used 21 on the port (as described in the corresponding RFC) but change 22 control for the port allocation iis designated to others. Under 23 existing operational procedures, this means the original assignee 24 needs to be involved in chnage to the port assignment. As it is not 25 always possible to get in touch with the original assignee, 26 particularly because of out-dated contact information, this current 27 practice of handling historical allocation of System Ports does not 28 scale well on a case-by-case basis. To address this, this document 29 instructs IANA to perform actions with the goal to reassign System 30 Ports to the IESG that were assigned to individuals prior to the 31 publication of RFC6335, where appropriate. 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at https://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on August 13, 2020. 50 Copyright Notice 52 Copyright (c) 2020 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (https://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 1. Introduction 67 RFC 6335 [RFC6335] requires System Ports, also known as the Well 68 Known Ports, in the range from 0 to 1023, to be assigned by the "IETF 69 Review" or "IESG Approval" procedures [RFC8126]. For assignments 70 done through RFCs published via the "IETF Document Stream" [RFC4844], 71 the Assignee will be the IESG with the IETF Chair as the Contact. 73 However, ports that were assigned before the publication of RFC 6335, 74 are often assigned to individuals, even if they are part of the 75 System Port range and have a corresponding RFC. Besides the fact 76 that System Ports are widely used by IETF protocols where the 77 protocol specification is under IETF change control as defined in an 78 RFC but the port itself may not, this situation is especially 79 problematic if the assignment gets or needs to be changed. The 80 Assignee can change the assignment without confirmation of the IETF. 81 However, if the IETF process requires a change, including de- 82 assignment, this cannot be done without the agreement of the original 83 Assignee. Furthermore, no procedure is defined to change the 84 assignment in cases where the original Assignee is not reachable or 85 not available anymore. 87 This document mainly aims to clarify the change control for protocols 88 that are maintained by the IETF; it further also intends an update of 89 currently unused or not maintained ports. For this purpose this 90 document instructs IANA to perform accumulative actions with the goal 91 to re-assign currently assigned System Ports in the range from 0 to 92 1023 to the IESG, where appropriate, which will also help to align 93 existing entries in the "Service Name and Transport Protocol Port 94 Number Registry" with the current procedures defined in RFC 6335. 96 2. IANA Considerations 98 IANA [will perform/has performed] actions with the goal to re-assign 99 System Ports in the port range from 0 to 1023 that are currently 100 assigned in the "Service Name and Transport Protocol Port Number 101 Registry" (https://www.iana.org/assignments/service-names-port- 102 numbers/service-names-port-numbers.xhtml) to clarify the IESG's 103 responisibility in managing those allocations. When the re- 104 assignment is performd, the contact data for these assignments should 105 be adjusted to refelct the IESG as assignee and the 106 IETF Chair as point of contact. The original 107 assignee and respective contact information should be preserved as a 108 note against the revised assignment data. 110 To perform the re-assignment, IANA is requested to contact the 111 current Assignees by email with the registered email address to 112 request the transfer. If the provided email address is not valid 113 anymore, IANA is requested to report this to the IESG, and the IESG 114 is requested to perform actions, such as sending requests to the 115 ietf@ietf.org mailing list to determine updated contact information. 116 If these actions do not show success within 4 weeks, the IESG is 117 requested to make a decision about the re-assignment of the port in 118 question. 120 If the current assignee does not agree to the re-assignment or does 121 not reply within four weeks, IANA is requested to inform the IESG 122 which then is requested to make a decision about the re-assignment of 123 the port in question. 125 Before the start of this re-assignment process, IANA [will also 126 update/has further updated] the Reference column with the following 127 reference for the listed ports that have a corresponding published 128 RFC that uses this port number, as well as the Assignment Notes 129 column for historic RFCs: 131 +-----------+----------+--------------+-------------+---------------+ 132 | Service | Port | Transport | Reference | Assignment | 133 | Name | Number | protocol | | Notes | 134 +-----------+----------+--------------+-------------+---------------+ 135 | systat | 11 | tcp | RFC866 | | 136 | systat | 11 | udp | RFC866 | | 137 | qotd | 17 | tcp | RFC865 | | 138 | qotd | 17 | upd | RFC865 | | 139 | msp | 18 | tcp | RFC1312 | | 140 | msp | 18 | udp | RFC1312 | | 141 | chargen | 19 | tcp | RFC864 | | 142 | chargen | 19 | udp | RFC864 | | 143 | smtp | 25 | tcp | RFC5321 | | 144 | smtp | 25 | udp | RFC5321 | | 145 | time | 37 | tcp | RFC868 | | 146 | time | 37 | udp | RFC868 | | 147 | rap | 38 | tcp | RFC1476 | | 148 | rap | 38 | udp | RFC1476 | | 149 | rlp | 39 | tcp | RFC887 | | 150 | rlp | 39 | udp | RFC887 | | 151 | nicname | 43 | tcp | RFC3912 | | 152 | nicname | 43 | udp | RFC3912 | | 153 | tacacs | 49 | tcp | RFC1492 | | 154 | tacacs | 49 | udp | RFC1492 | | 155 | domain | 53 | tcp | RFC1035 | | 156 | domain | 53 | udp | RFC1035 | | 157 | whoispp | 63 | tcp | RFC1913 | | 158 | whoispp | 63 | udp | RFC1913 | | 159 | bootps | 67 | tcp | RFC2131 | | 160 | bootps | 67 | udp | RFC2131 | | 161 | bootpc | 68 | tcp | RFC2131 | | 162 | bootpc | 68 | udp | RFC2131 | | 163 | tftp | 69 | tcp | RFC1350 | | 164 | tftp | 69 | udp | RFC1350 | | 165 | gopher | 70 | tcp | RFC1436 | | 166 | gopher | 70 | udp | RFC1436 | | 167 | finger | 79 | tcp | RFC1288 | | 168 | finger | 79 | udp | RFC1288 | | 169 | www-http | 80 | tcp | RFC7230, | | 170 | | | | RFC7540 | | 171 | www-http | 80 | udp | RFC7230, | | 172 | | | | RFC7540 | | 173 | kerberos | 88 | tcp | RFC4120 | | 174 | kerberos | 88 | udp | RFC4120 | | 175 | dixie | 96 | tcp | RFC1249 | | 176 | dixie | 96 | udp | RFC1249 | | 177 | hostname | 101 | tcp | RFC953 | This RFC is | 178 | | | | | historic. | 179 | hostname | 101 | udp | RFC953 | This RFC is | 180 | | | | | historic. | 181 | cso | 105 | tcp | RFC2378 | | 182 | cso | 105 | udp | RFC2378 | | 183 | rtelnet | 107 | tcp | RFC818 | This RFC is | 184 | | | | | historic. | 185 | rtelnet | 107 | udp | RFC818 | This RFC is | 186 | | | | | historic. | 187 | pop2 | 109 | tcp | RFC937 | This RFC is | 188 | | | | | historic. | 189 | pop2 | 109 | udp | RFC937 | This RFC is | 190 | | | | | historic. | 191 | pop3 | 110 | tcp | RFC1939 | | 192 | pop3 | 110 | udp | | | 193 | sunrpc | 111 | tcp | RFC1833 | | 194 | sunrpc | 111 | udp | RFC1833 | | 195 | auth | 113 | tcp | RFC1413 | | 196 | auth | 113 | udp | RFC1413 | | 197 | sftp | 115 | tcp | RFC913 | This RFC is | 198 | | | | | historic. | 199 | sftp | 115 | udp | RFC913 | This RFC is | 200 | | | | | historic. | 201 | cfdptkt | 120 | tcp | RFC1235 | | 202 | cfdptkt | 120 | udp | RFC1235 | | 203 | pwdgen | 129 | tcp | RFC972 | | 204 | pwdgen | 129 | udp | RFC972 | | 205 | bftp | 152 | tcp | RFC1068 | | 206 | bftp | 152 | udp | RFC1068 | | 207 | sgmp | 153 | tcp | RFC1028 | This RFC is | 208 | | | | | historic. | 209 | sgmp | 153 | udp | RFC1028 | This RFC is | 210 | | | | | historic. | 211 | snmp | 161 | tcp | RFC3430 | | 212 | snmp | 161 | udp | RFC3417 | | 213 | snmptrap | 162 | tcp | RFC3430 | | 214 | snmptrap | 162 | udp | RFC3417 | | 215 | bgp | 179 | tcp | RFC4271 | | 216 | bgp | 179 | udp | RFC4271 | | 217 | irc | 194 | tcp | RFC1459 | | 218 | irc | 194 | udp | RFC1459 | | 219 | smux | 199 | tcp | RFC1227 | This RFC is | 220 | | | | | historic. | 221 | smux | 199 | udp | RFC1227 | This RFC is | 222 | | | | | historic. | 223 | ipx | 213 | tcp | RFC1234 | This RFC is | 224 | | | | | historic. | 225 | ipx | 213 | upd | RFC1234 | This RFC is | 226 | | | | | historic. | 227 | mpp | 218 | tcp | RFC1204 | | 228 | mpp | 218 | udp | RFC1204 | | 229 | bgmp | 264 | tcp | RFC3913 | This RFC is | 230 | | | | | historic. | 231 | bgmp | 264 | udp | RFC3913 | This RFC is | 232 | | | | | historic. | 233 | pt-tls | 271 | tcp | RFC6876 | | 234 | pt-tls | 271 | udp | RFC6876 | | 235 | rtsps | 322 | tcp | RFC7826 | | 236 | rtsps | 322 | udp | RFC7826 | | 237 | odmr | 366 | tcp | RFC2645 | | 238 | odmr | 366 | udp | RFC2645 | | 239 | aurp | 387 | tcp | RFC1504 | | 240 | aurp | 387 | udp | RFC1504 | | 241 | ldap | 389 | tcp | RFC4516 | | 242 | ldap | 389 | udp | RFC4516 | | 243 | svrloc | 427 | tcp | RFC2608 | | 244 | svrloc | 427 | udp | RFC2608 | | 245 | https | 443 | tcp | RFC7230, | | 246 | | | | RFC7540 | | 247 | https | 443 | udp | RFC7230, | | 248 | | | | RFC7540 | | 249 | kpasswd | 464 | tcp | RFC3244 | | 250 | kpasswd | 464 | udp | RFC3244 | | 251 | photuris | 468 | tcp | RFC2522 | | 252 | photuris | 468 | udp | RFC2522 | | 253 | isakmp | 500 | tcp | RFC7296 | | 254 | isakmp | 500 | udp | RFC7296 | | 255 | syslog | 514 | tcp | RFC5426 | | 256 | syslog | 514 | udp | RFC5426 | | 257 | printer | 515 | tcp | RFC1179 | | 258 | printer | 515 | udp | RFC1179 | | 259 | router | 520 | tcp | RFC2453 | | 260 | router | 520 | udp | RFC2453 | | 261 | ripng | 521 | tcp | RFC2080 | | 262 | ripng | 521 | udp | RFC2080 | | 263 | rtsp | 554 | tcp | RFC7826 | | 264 | rtsp | 554 | udp | RFC7826 | | 265 | vemmi | 575 | tcp | RFC2122 | | 266 | vemmi | 575 | udp | RFC2122 | | 267 | ipp | 631 | tcp | RFC8010 | | 268 | ipp | 631 | udp | RFC8010 | | 269 | msdp | 639 | tcp | RFC3618 | | 270 | msdp | 639 | udp | RFC3618 | | 271 | ldp | 646 | tcp | RFC3036 | | 272 | ldp | 646 | udp | RFC3036 | | 273 | rrp | 648 | tcp | RFC2832 | | 274 | rrp | 648 | udp | RFC2832 | | 275 | aodv | 654 | tcp | RFC3561 | | 276 | aodv | 654 | udp | RFC3561 | | 277 | acap | 674 | tcp | RFC2244 | | 278 | acap | 674 | udp | RFC2244 | | 279 | olsr | 698 | tcp | RFC3626 | | 280 | olsr | 698 | udp | RFC3626 | | 281 | agentx | 705 | tcp | RFC2741 | | 282 | agentx | 705 | udp | RFC2741 | | 283 +-----------+----------+--------------+-------------+---------------+ 285 As part of this maintenance effort, IANA [will further add/has 286 further added] the following entry in addition to the existing entry 287 for port 441 with the IESG as Assignee and the IETF chair as Contact: 289 +---------+--------+-----------+-----------+------------------------+ 290 | Service | Port | Transport | Reference | Assignment Notes | 291 | Name | Number | protocol | | | 292 +---------+--------+-----------+-----------+------------------------+ 293 | rmt | 441 | tcp | RFC1202 | For historical | 294 | | | | | reasons, multiple | 295 | | | | | registrations exist | 296 | | | | | for the same port | 297 | | | | | number. Clients need | 298 | | | | | to have prior | 299 | | | | | knowledge of which | 300 | | | | | service is provided by | 301 | | | | | the server on that | 302 | | | | | port in order to make | 303 | | | | | use of it. | 304 +---------+--------+-----------+-----------+------------------------+ 306 3. Security Considerations 308 This draft instructs IANA to perform actions on the Service Name and 309 Transport Protocol Port Number Registry. It does not change the use 310 of the ports or protocols running on them. Therefore the security of 311 these protocols is not impacted by these changes to the registry. 313 4. References 315 4.1. Normative References 317 [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. 318 Cheshire, "Internet Assigned Numbers Authority (IANA) 319 Procedures for the Management of the Service Name and 320 Transport Protocol Port Number Registry", BCP 165, 321 RFC 6335, DOI 10.17487/RFC6335, August 2011, 322 . 324 4.2. Informative References 326 [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC 327 Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, 328 July 2007, . 330 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 331 Writing an IANA Considerations Section in RFCs", BCP 26, 332 RFC 8126, DOI 10.17487/RFC8126, June 2017, 333 . 335 Authors' Addresses 337 Mirja Kuehlewind (editor) 338 Ericsson GmbH 340 Email: ietf@kuehlewind.net 342 Sabrina Tanamal 344 Email: sabrina.tanamal@iana.org