idnits 2.17.1 draft-kuehlewind-system-ports-03.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 (June 7, 2018) is 2151 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. -------------------------------------------------------------------------------- 1 Network Working Group M. Kuehlewind, Ed. 2 Internet-Draft ETH Zurich 3 Intended status: Standards Track S. Tanamal 4 Expires: December 9, 2018 June 7, 2018 6 Reassignment of System Ports to the IESG 7 draft-kuehlewind-system-ports-03 9 Abstract 11 In the IANA Service Name and Transport Protocol Port Number Registry, 12 a large number of System Ports is currently assigned to individuals 13 or companies who have registered the port for the use with a certain 14 protocol before RFC6335 was published. For some of these ports, RFCs 15 exist that describe the respective protocol; for others, RFCs are 16 under development that define, re-define, or assign the protocol used 17 for the respective port, e.g. in case of so-far unused UDP ports that 18 have been registered together with the respective TCP port. In these 19 cases the IESG has the change control about the protocol used on the 20 port (as described in an RFC) but does not have the change control 21 about the port usage itself. Currently, to transfer the change 22 control to the IESG, the original assignee has to be contacted to 23 initialize this transfer. As it is not always possible to get in 24 touch with the original assignee, e.g. because of out-dated contact 25 information or other reasons, and the current practice of case-by- 26 case changes does not scale well, this document instructs IANA to 27 perform actions with the goal to reassigns all System Ports to the 28 IESG that have been assigned to individuals prior to the publication 29 of RFC6335. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on December 9, 2018. 48 Copyright Notice 50 Copyright (c) 2018 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 1. Introduction 65 RFC 6335 [RFC6335] requires System Ports, also known as the Well 66 Known Ports, in the range from 0 to 1023, to be assigned by the "IETF 67 Review" or "IESG Approval" procedures [RFC8126]. For assignments 68 done through RFCs published via the "IETF Document Stream" [RFC4844], 69 the Assignee will be the IESG with the IETF Chair as the Contact. 71 However, ports that were assigned before the publication of RFC 6335, 72 are often assigned to individuals, even if they are part of the 73 System Port range and have an corresponding RFC. Besides the fact 74 that System Ports are widely used by IETF protocols where the 75 protocol specification is under IETF change control as defined in an 76 RFC but the port itself may not, this situation is especially 77 problematic if the assignment gets or needs to be changed. The 78 Assignee, can change the assignment without confirmation of the IETF. 79 However, if the IETF process requires a change, including de- 80 assignment, this cannot be done without the agreement of the original 81 Assignee. Furthermore, no procedure is defined to change the 82 assignment in cases where the original Assignee is not reachable or 83 not available anymore. 85 This document instructs IANA to perform actions with the goal to re- 86 assign all currently assigned System Ports in the range from 0 to 87 1023 to the IESG, which will also help to align existing entries in 88 the "Service Name and Transport Protocol Port Number Registry" with 89 the current procedures defined in RFC 6335. 91 2. IANA Considerations 93 IANA [will perform/has performed] action to re-assign all System 94 Ports in the port range from 0 to 1023 that are currently assigned in 95 the "Service Name and Transport Protocol Port Number Registry" 96 (https://www.iana.org/assignments/service-names-port-numbers/service- 97 names-port-numbers.xhtml) to the IESG as Assignee and 98 the IETF Chair as Contact. The original Assignee 99 and respective contact information should be preserved as a 100 Assignment note "Originally assigned to $Assignee <$Contact>" where 101 $Assignee is the current value in the Assignee column and $Contact is 102 the current value in the Contact column. 104 To perform the assignment, IANA is requested to contact the current 105 Assignees by email with the registered email address to request the 106 transfer. If the provided email address is not valid anymore, IANA 107 is requested to report this to the IESG, and the IESG is requested to 108 perform actions, such as sending requests to the ietf@ietf.org 109 mailing list to determine updated contact information. If these 110 actions do not show success within 4 weeks, the IESG is requested to 111 make a decision about the re-assignment of the port in question. 113 IANA is requested to send the following request to each current 114 Assignees: 116 "Dear $Assignee, We currently have you listed as the assignee for 117 $Port in the Service Name and Transport Protocol Port Number 118 Registry. This port is part of the System Ports range which has a 119 registration policy of "IETF Review" or "IESG Approval" as defined in 120 RFC6335. To enable future documentation in the RFC series of the 121 protocol in use for this port, we would like to request a 122 confirmation for a de-assignment of $Port to enable a subsequent re- 123 assignment to the IESG. This would mean replacing your contact 124 information under the assignee and contact fields in the registry 125 with the IESG. Your contact information will still be noted in the 126 registry as the original assignee unless you prefer it removed. 127 Please let us know if you have any objections to this change or if 128 the port is known not to be used (anymore), and can be marked as 129 Reserved. If you have information about a publicly available 130 specification of the protocol in use on the respective port that is 131 not noted in the registry yet, please let us know, and we'll update 132 the notes in the registry accordingly." 134 If the current Assignee does not agree to the re-assignment or does 135 not reply within four weeks, IANA is requested to inform the IESG 136 which then is requested to make a decision about the re-assignment of 137 the port in question. 139 Before the start of this re-assignment process, IANA [will also 140 update/has further updated] the Reference column with the following 141 reference for the listed ports that have a corresponding published 142 RFC that uses this port number, as well as the Assignment Notes 143 column for historic RFCs: 145 +-----------+----------+--------------+-------------+---------------+ 146 | Service | Port | Transport | Reference | Assignment | 147 | Name | Number | protocol | | Notes | 148 +-----------+----------+--------------+-------------+---------------+ 149 | systat | 11 | tcp | RFC866 | | 150 | systat | 11 | udp | RFC866 | | 151 | qotd | 17 | tcp | RFC865 | | 152 | qotd | 17 | upd | RFC865 | | 153 | msp | 18 | tcp | RFC1312 | | 154 | msp | 18 | udp | RFC1312 | | 155 | chargen | 19 | tcp | RFC864 | | 156 | chargen | 19 | udp | RFC864 | | 157 | smtp | 25 | tcp | RFC5321 | | 158 | smtp | 25 | udp | RFC5321 | | 159 | time | 37 | tcp | RFC868 | | 160 | time | 37 | udp | RFC868 | | 161 | rap | 38 | tcp | RFC1476 | | 162 | rap | 38 | udp | RFC1476 | | 163 | rlp | 39 | tcp | RFC887 | | 164 | rlp | 39 | udp | RFC887 | | 165 | nicname | 43 | tcp | RFC3912 | | 166 | nicname | 43 | udp | RFC3912 | | 167 | tacacs | 49 | tcp | RFC1492 | | 168 | tacacs | 49 | udp | RFC1492 | | 169 | domain | 53 | tcp | RFC1035 | | 170 | domain | 53 | udp | RFC1035 | | 171 | whoispp | 63 | tcp | RFC1913 | | 172 | whoispp | 63 | udp | RFC1913 | | 173 | bootps | 67 | tcp | RFC2131 | | 174 | bootps | 67 | udp | RFC2131 | | 175 | bootpc | 68 | tcp | RFC2131 | | 176 | bootpc | 68 | udp | RFC2131 | | 177 | tftp | 69 | tcp | RFC1350 | | 178 | tftp | 69 | udp | RFC1350 | | 179 | gopher | 70 | tcp | RFC1436 | | 180 | gopher | 70 | udp | RFC1436 | | 181 | finger | 79 | tcp | RFC1288 | | 182 | finger | 79 | udp | RFC1288 | | 183 | www-http | 80 | tcp | RFC7230, | | 184 | | | | RFC7540 | | 185 | www-http | 80 | udp | RFC7230, | | 186 | | | | RFC7540 | | 187 | kerberos | 88 | tcp | RFC4120 | | 188 | kerberos | 88 | udp | RFC4120 | | 189 | dixie | 96 | tcp | RFC1249 | | 190 | dixie | 96 | udp | RFC1249 | | 191 | hostname | 101 | tcp | RFC953 | This RFC is | 192 | | | | | historic. | 193 | hostname | 101 | udp | RFC953 | This RFC is | 194 | | | | | historic. | 195 | cso | 105 | tcp | RFC2378 | | 196 | cso | 105 | udp | RFC2378 | | 197 | rtelnet | 107 | tcp | RFC818 | This RFC is | 198 | | | | | historic. | 199 | rtelnet | 107 | udp | RFC818 | This RFC is | 200 | | | | | historic. | 201 | sunrpc | 111 | tcp | RFC1833 | | 202 | sunrpc | 111 | udp | RFC1833 | | 203 | auth | 113 | tcp | RFC1413 | | 204 | auth | 113 | udp | RFC1413 | | 205 | sftp | 115 | tcp | RFC913 | This RFC is | 206 | | | | | historic. | 207 | sftp | 115 | udp | RFC913 | This RFC is | 208 | | | | | historic. | 209 | cfdptkt | 120 | tcp | RFC1235 | | 210 | cfdptkt | 120 | udp | RFC1235 | | 211 | pwdgen | 129 | tcp | RFC972 | | 212 | pwdgen | 129 | udp | RFC972 | | 213 | imap | 143 | tcp | RFC3501 | | 214 | imap | 143 | udp | RFC3501 | | 215 | bftp | 152 | tcp | RFC1068 | | 216 | bftp | 152 | udp | RFC1068 | | 217 | sgmp | 153 | tcp | RFC1028 | This RFC is | 218 | | | | | historic. | 219 | sgmp | 153 | udp | RFC1028 | This RFC is | 220 | | | | | historic. | 221 | snmp | 161 | tcp | RFC3430 | | 222 | snmp | 161 | udp | RFC3417 | | 223 | snmptrap | 162 | tcp | RFC3430 | | 224 | snmptrap | 162 | udp | RFC3417 | | 225 | bgp | 179 | tcp | RFC4271 | | 226 | bgp | 179 | udp | RFC4271 | | 227 | irc | 194 | tcp | RFC1459 | | 228 | irc | 194 | udp | RFC1459 | | 229 | smux | 199 | tcp | RFC1227 | This RFC is | 230 | | | | | historic. | 231 | smux | 199 | udp | RFC1227 | This RFC is | 232 | | | | | historic. | 233 | ipx | 213 | tcp | RFC1234 | This RFC is | 234 | | | | | historic. | 235 | ipx | 213 | upd | RFC1234 | This RFC is | 236 | | | | | historic. | 237 | mpp | 218 | tcp | RFC1204 | | 238 | mpp | 218 | udp | RFC1204 | | 239 | bgmp | 264 | tcp | RFC3913 | This RFC is | 240 | | | | | historic. | 241 | bgmp | 264 | udp | RFC3913 | This RFC is | 242 | | | | | historic. | 243 | pt-tls | 271 | tcp | RFC6876 | | 244 | pt-tls | 271 | udp | RFC6876 | | 245 | rtsps | 322 | tcp | RFC7826 | | 246 | rtsps | 322 | udp | RFC7826 | | 247 | odmr | 366 | tcp | RFC2645 | | 248 | odmr | 366 | udp | RFC2645 | | 249 | aurp | 387 | tcp | RFC1504 | | 250 | aurp | 387 | udp | RFC1504 | | 251 | ldap | 389 | tcp | RFC4516 | | 252 | ldap | 389 | udp | RFC4516 | | 253 | svrloc | 427 | tcp | RFC2608 | | 254 | svrloc | 427 | udp | RFC2608 | | 255 | https | 443 | tcp | RFC7230, | | 256 | | | | RFC7540 | | 257 | https | 443 | udp | RFC7230, | | 258 | | | | RFC7540 | | 259 | kpasswd | 464 | tcp | RFC3244 | | 260 | kpasswd | 464 | udp | RFC3244 | | 261 | photuris | 468 | tcp | RFC2522 | | 262 | photuris | 468 | udp | RFC2522 | | 263 | isakmp | 500 | tcp | RFC7296 | | 264 | isakmp | 500 | udp | RFC7296 | | 265 | syslog | 514 | tcp | RFC5426 | | 266 | syslog | 514 | udp | RFC5426 | | 267 | printer | 515 | tcp | RFC1179 | | 268 | printer | 515 | udp | RFC1179 | | 269 | router | 520 | tcp | RFC2453 | | 270 | router | 520 | udp | RFC2453 | | 271 | ripng | 521 | tcp | RFC2080 | | 272 | ripng | 521 | udp | RFC2080 | | 273 | rtsp | 554 | tcp | RFC7826 | | 274 | rtsp | 554 | udp | RFC7826 | | 275 | vemmi | 575 | tcp | RFC2122 | | 276 | vemmi | 575 | udp | RFC2122 | | 277 | ipp | 631 | tcp | RFC8010 | | 278 | ipp | 631 | udp | RFC8010 | | 279 | msdp | 639 | tcp | RFC3618 | | 280 | msdp | 639 | udp | RFC3618 | | 281 | ldp | 646 | tcp | RFC3036 | | 282 | ldp | 646 | udp | RFC3036 | | 283 | rrp | 648 | tcp | RFC2832 | | 284 | rrp | 648 | udp | RFC2832 | | 285 | aodv | 654 | tcp | RFC3561 | | 286 | aodv | 654 | udp | RFC3561 | | 287 | acap | 674 | tcp | RFC2244 | | 288 | acap | 674 | udp | RFC2244 | | 289 | olsr | 698 | tcp | RFC3626 | | 290 | olsr | 698 | udp | RFC3626 | | 291 | agentx | 705 | tcp | RFC2741 | | 292 | agentx | 705 | udp | RFC2741 | | 293 +-----------+----------+--------------+-------------+---------------+ 295 As part of this maintenance effort, IANA [will further add/has 296 further added] the following entry in addition to the existing entry 297 for port 441 with the IESG as Assignee and the IETF chair as Contact: 299 +---------+--------+-----------+-----------+------------------------+ 300 | Service | Port | Transport | Reference | Assignment Notes | 301 | Name | Number | protocol | | | 302 +---------+--------+-----------+-----------+------------------------+ 303 | rmt | 441 | tcp | RFC1202 | For historical | 304 | | | | | reasons, multiple | 305 | | | | | registrations exist | 306 | | | | | for the same port | 307 | | | | | number. Clients need | 308 | | | | | to have prior | 309 | | | | | knowledge of which | 310 | | | | | service is provided by | 311 | | | | | the server on that | 312 | | | | | port in order to make | 313 | | | | | use of it. | 314 +---------+--------+-----------+-----------+------------------------+ 316 3. Security Considerations 318 This draft instructs IANA to perform actions on the Service Name and 319 Transport Protocol Port Number Registry. It does not change the use 320 of the ports or protocols running on them. Therefore the security of 321 these protocols in not impacted by these changes to the registry. 323 4. References 325 4.1. Normative References 327 [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. 328 Cheshire, "Internet Assigned Numbers Authority (IANA) 329 Procedures for the Management of the Service Name and 330 Transport Protocol Port Number Registry", BCP 165, 331 RFC 6335, DOI 10.17487/RFC6335, August 2011, 332 . 334 4.2. Informative References 336 [RFC4844] Daigle, L., Ed. and Internet Architecture Board, "The RFC 337 Series and RFC Editor", RFC 4844, DOI 10.17487/RFC4844, 338 July 2007, . 340 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 341 Writing an IANA Considerations Section in RFCs", BCP 26, 342 RFC 8126, DOI 10.17487/RFC8126, June 2017, 343 . 345 Authors' Addresses 347 Mirja Kuehlewind (editor) 348 ETH Zurich 350 Email: ietf@kuehlewind.net 352 Sabrina Tanamal 354 Email: sabrina.tanamal@iana.org